diff --git a/marked/Rel-18/25_series/25113/30a26f2d17ca95672702bf50fb4f0242_img.jpg b/marked/Rel-18/25_series/25113/30a26f2d17ca95672702bf50fb4f0242_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6ff709151e7cfedc7d5362760d96df3f3c9b22f --- /dev/null +++ b/marked/Rel-18/25_series/25113/30a26f2d17ca95672702bf50fb4f0242_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24d036488b888b43439969ac8e9c6fd0e164036d8d45be6a94920d752049463b +size 5148 diff --git a/marked/Rel-18/25_series/25113/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/25_series/25113/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa046f17e44d05d0f3ff36db6a0628df7c5f4705 --- /dev/null +++ b/marked/Rel-18/25_series/25113/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2edb076fc92420df2cde182ac8fe64b5456fdb45f4bd30a3fe834b2e88e45830 +size 9482 diff --git a/marked/Rel-18/25_series/25113/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Rel-18/25_series/25113/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d29e366ffd0327b64b8fa7cf2f0b614e57cb4dad --- /dev/null +++ b/marked/Rel-18/25_series/25113/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8f5b00d996437c3295f52ac76fc58a09a6e6df298bde8b9341a23b0abc38651 +size 29013 diff --git a/marked/Rel-18/25_series/25113/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-18/25_series/25113/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1163332d9500f9c353559f3bd357ea450aabdd7 --- /dev/null +++ b/marked/Rel-18/25_series/25113/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03c74c2d3d55be72158d7175f7e84cffcd132222c37b616ea566482d48cbc671 +size 23655 diff --git a/marked/Rel-18/25_series/25113/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-18/25_series/25113/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecfde5d924606e065c6899615a3e50d20527be88 --- /dev/null +++ b/marked/Rel-18/25_series/25113/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8537d70e20c27a3ccff3bc982be09ce8236055088ed189bfeed9ca5e1f89d10 +size 11431 diff --git a/marked/Rel-18/25_series/25113/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-18/25_series/25113/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..224d0bac49b675d71d717c87b8d8f1d6166c4692 --- /dev/null +++ b/marked/Rel-18/25_series/25113/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdd2e90e7e1c8ce5fdf99bdf61c160edb8c79258a81d32625bdea781926618e1 +size 22655 diff --git a/marked/Rel-18/25_series/25171/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/Rel-18/25_series/25171/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec92bf6f015b406788f73529768e4db427331c4c --- /dev/null +++ b/marked/Rel-18/25_series/25171/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cba7719bceea74159edc64ede21351733ed52442cd7743d4d43733c0c018a05e +size 63551 diff --git a/marked/Rel-18/25_series/25171/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/25_series/25171/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..050a4e3cf153138bc9b9265d2b534903dd05afd9 --- /dev/null +++ b/marked/Rel-18/25_series/25171/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:525cd511b7275dfc1f24137e86bee90b32cc42d6e7a056a1a8569a8ace587431 +size 8101 diff --git a/marked/Rel-18/25_series/25171/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/25_series/25171/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99cdfe8f970d26a49ecca50f2d5da0c5bebd351c --- /dev/null +++ b/marked/Rel-18/25_series/25171/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9ee8908ba48df501a4a60da58a8cce7d6b50df3451b4d261ab74efa8bfc0ef4 +size 5189 diff --git a/marked/Rel-18/25_series/25171/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-18/25_series/25171/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e22e617c02ea363b08789efd0a3a5bbe9556067 --- /dev/null +++ b/marked/Rel-18/25_series/25171/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4558641033b3116245ca4fc4a5de9721b260504c034b314a8baf128b17ff71f2 +size 97459 diff --git a/marked/Rel-18/25_series/25171/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-18/25_series/25171/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e161c3e661b6d500341928841d183f68ca248a6 --- /dev/null +++ b/marked/Rel-18/25_series/25171/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5247731a3df352fb9c271a74886775dc7bd07d98bfd74d77d529726d430ea642 +size 170596 diff --git a/marked/Rel-18/25_series/25171/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-18/25_series/25171/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a27472b29369ed627dfc13527b6bca21cc8861c9 --- /dev/null +++ b/marked/Rel-18/25_series/25171/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9ee88d34081adb65e716c0c13034a07cc32db1081ea4e9dfa91da9b545c9097 +size 74672 diff --git a/marked/Rel-18/25_series/25171/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-18/25_series/25171/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97053711117909dd0593c27469a9279d2894053f --- /dev/null +++ b/marked/Rel-18/25_series/25171/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e934fa396fa2ca2f9319a44854110f5cdc56edfe0249bcc464bd52718944ab0 +size 161794 diff --git a/marked/Rel-18/25_series/25171/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/25_series/25171/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..304ebade144fd7add02fb6238bcb342e05bd7371 --- /dev/null +++ b/marked/Rel-18/25_series/25171/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c85c47adace04e152caa6c5539ba0c1f7b6d28114f63a5ddb99becc4dc4b0981 +size 26638 diff --git a/marked/Rel-18/25_series/25300/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/Rel-18/25_series/25300/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af210d54f5b224aca60ad3f90ff10f763445b2ab --- /dev/null +++ b/marked/Rel-18/25_series/25300/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bdfa60ff0052f7bd8387709b80fa56021f18d2e0c8ff1bf0a034965bf7aa2ed +size 17558 diff --git a/marked/Rel-18/25_series/25300/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/25_series/25300/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58b66dc68d9a0137695530e8f43e1a432c4f3375 --- /dev/null +++ b/marked/Rel-18/25_series/25300/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9101c2e66dfcf7e8b160fc053fe515431852116fcb2bdc9980111f7eff8238b0 +size 36473 diff --git a/marked/Rel-18/25_series/25300/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/25_series/25300/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f389ce62cb650aa960ffaf78cbfd5eb117bd9832 --- /dev/null +++ b/marked/Rel-18/25_series/25300/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa74f93f1c0650eee9cf1af05f396235faa846a218d5f43bfeb1d757b9432ecc +size 7575 diff --git a/marked/Rel-18/25_series/25300/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-18/25_series/25300/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..933160a024f247a93f592affd5118b5056082f84 --- /dev/null +++ b/marked/Rel-18/25_series/25300/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb8c26e7065fdedf97ae678ad82fad32c36be68daa25105469a45f7a9bfa4e17 +size 32269 diff --git a/marked/Rel-18/25_series/25300/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/Rel-18/25_series/25300/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bd38dafa7d6a33ddc66be537160f67342b52d23 --- /dev/null +++ b/marked/Rel-18/25_series/25300/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff32f613627c6ddf9bdf0c25a3223eb24bba5662bfa50b0d8a7375765cfe92d6 +size 29542 diff --git a/marked/Rel-18/25_series/25307/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/25_series/25307/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1f69cc7b0965f09e34079057b9bd4ce934a890e --- /dev/null +++ b/marked/Rel-18/25_series/25307/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f12516074b8d90dede165795a29676500dd769148e669051b5a58f28b9e90124 +size 8735 diff --git a/marked/Rel-18/25_series/25327/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/25_series/25327/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b5d3c69188a610f911a95b8cce8fd4fc6427691 --- /dev/null +++ b/marked/Rel-18/25_series/25327/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:375b2e8bd44894e45839805267b6f566324eee8394026b9f244fcacdd3281b6d +size 7587 diff --git a/marked/Rel-18/25_series/25414/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Rel-18/25_series/25414/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b0ffd7402512e6666a4b109aa689910fcb1702f --- /dev/null +++ b/marked/Rel-18/25_series/25414/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d700903019a1e05a201741ab932aea03e9d3a76b93d9d0878f5c8186e2c5593 +size 46664 diff --git a/marked/Rel-18/25_series/25414/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/25_series/25414/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e027e0f84975dcb4761cb5b6c3143df967b5869 --- /dev/null +++ b/marked/Rel-18/25_series/25414/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5543341caa32b4c0dac9cfe4f1a490e54386d139dbb7c82c200f2bef7f7e299f +size 9865 diff --git a/marked/Rel-18/25_series/25414/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/25_series/25414/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..093b729ae1c8e3e13582986aa7f2719f2181c511 --- /dev/null +++ b/marked/Rel-18/25_series/25414/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17fc582b9766ed76bf838899ac85851f49d4ca2262ccd98cd25206f5a429f856 +size 5658 diff --git a/marked/Rel-18/25_series/25450/536951b2bbd94325ae266d8d1363df8f_img.jpg b/marked/Rel-18/25_series/25450/536951b2bbd94325ae266d8d1363df8f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..defa9d740a601e1db6cd1718680dbfd38532674b --- /dev/null +++ b/marked/Rel-18/25_series/25450/536951b2bbd94325ae266d8d1363df8f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36b2de466a77ccef3c2af0274bdbcdf2239b3651a500940f8aaf36f761b6c920 +size 22671 diff --git a/marked/Rel-18/25_series/25450/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/25_series/25450/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..165ec946988ce2360c0fa6ada52ffbb0e1b26625 --- /dev/null +++ b/marked/Rel-18/25_series/25450/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f50a7fba5f898973c2360a288ffa4320d27f8587b8485cc94744c0b91f39ead +size 7703 diff --git a/marked/Rel-18/25_series/25450/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/25_series/25450/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..061edce3b36d4e6b97c314de48bfd205c519b56e --- /dev/null +++ b/marked/Rel-18/25_series/25450/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb8006027f4e9720be7404c952672535cae06bb653edd8ba49b74818475f4d84 +size 5693 diff --git a/marked/Rel-18/25_series/25450/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg b/marked/Rel-18/25_series/25450/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f54eca9c520825f3f6a014a146e6829c221adfd8 --- /dev/null +++ b/marked/Rel-18/25_series/25450/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e920d737e25e1703d17528607158ffe2c811098f0cfb8cc74fef7412b79b42c +size 55758 diff --git a/marked/Rel-18/25_series/25466/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/25_series/25466/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e027e0f84975dcb4761cb5b6c3143df967b5869 --- /dev/null +++ b/marked/Rel-18/25_series/25466/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5543341caa32b4c0dac9cfe4f1a490e54386d139dbb7c82c200f2bef7f7e299f +size 9865 diff --git a/marked/Rel-18/25_series/25468/0019f09403376d6444ee323591fa2e98_img.jpg b/marked/Rel-18/25_series/25468/0019f09403376d6444ee323591fa2e98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea4224486d42a5792f15c3cec923558b7033df09 --- /dev/null +++ b/marked/Rel-18/25_series/25468/0019f09403376d6444ee323591fa2e98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:533c0274a516a12a83a7f6b9bb71221c0e1ba76481685b06767396a6bb233d3f +size 14931 diff --git a/marked/Rel-18/25_series/25468/04cefd2bf9de5948b15bea2d0bdc04f4_img.jpg b/marked/Rel-18/25_series/25468/04cefd2bf9de5948b15bea2d0bdc04f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c1ab28e0cc5a891ab1ecb83ba38c93e2e300502 --- /dev/null +++ b/marked/Rel-18/25_series/25468/04cefd2bf9de5948b15bea2d0bdc04f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:219e97510a60f1d3c1b7c36ddf023c4bed8bcfb59c4fc077284045d0e29e84e0 +size 14158 diff --git a/marked/Rel-18/25_series/25468/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Rel-18/25_series/25468/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..032eb6f01ed01e463723342ea6ba6f6489feae2a --- /dev/null +++ b/marked/Rel-18/25_series/25468/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9a1842d53c0b4867d467e9982dd915c5e7e4e91d2ac551ff6f890ff5a7531c7 +size 16102 diff --git a/marked/Rel-18/25_series/25468/2ba086df3506f81bae3a9b53725dcfea_img.jpg b/marked/Rel-18/25_series/25468/2ba086df3506f81bae3a9b53725dcfea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab6c0be9befd7e7f451054a8dc7b20503de1ed4a --- /dev/null +++ b/marked/Rel-18/25_series/25468/2ba086df3506f81bae3a9b53725dcfea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c18d53f34f31e62f3bf4c1ff67e6d02c7419c480579bad81d6fd6f3cbad3bff2 +size 10632 diff --git a/marked/Rel-18/25_series/25468/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Rel-18/25_series/25468/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e5e6805f6d6af07c53c77f025182302420f1940 --- /dev/null +++ b/marked/Rel-18/25_series/25468/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5442711e9335ea62aea4c9f1a9dcb08d04081abfe5aafcf4d7a3aa0d8b836bf9 +size 11030 diff --git a/marked/Rel-18/25_series/25468/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/25_series/25468/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e027e0f84975dcb4761cb5b6c3143df967b5869 --- /dev/null +++ b/marked/Rel-18/25_series/25468/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5543341caa32b4c0dac9cfe4f1a490e54386d139dbb7c82c200f2bef7f7e299f +size 9865 diff --git a/marked/Rel-18/25_series/25468/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/25_series/25468/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..503275adafc18789580515e126cffdd521e1fd6c --- /dev/null +++ b/marked/Rel-18/25_series/25468/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b47e37c37381653e731c0fa5afcd30c7e5c1ddf0e5f4d1e780d74e27c9d92ce +size 6242 diff --git a/marked/Rel-18/25_series/25468/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-18/25_series/25468/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..262f59499d093315c54e4768345ce4082dbdbc70 --- /dev/null +++ b/marked/Rel-18/25_series/25468/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bebf88a75789cb4dc54fdb69f77f0f31b6e035dd524caed1c5be7d3b1b4bed4f +size 12498 diff --git a/marked/Rel-18/25_series/25468/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/Rel-18/25_series/25468/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca2714e2de274c495be31b6268bc2277af067f1c --- /dev/null +++ b/marked/Rel-18/25_series/25468/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20345b508ca8048a132a6cf2d93ae3a35e89d86778603c666aa110bcf2fa842e +size 11790 diff --git a/marked/Rel-18/25_series/25468/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg b/marked/Rel-18/25_series/25468/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b58e4977a6912fa9002fab5f8558fb9d147c1b25 --- /dev/null +++ b/marked/Rel-18/25_series/25468/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:230a6cb4de7ff0268331ca6fdee3f3d84b30d1ab8421c90b08885055d7dfbb2f +size 13999 diff --git a/marked/Rel-18/25_series/25468/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-18/25_series/25468/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12a3c6c454750e4a88415d4de295a285fcf619f5 --- /dev/null +++ b/marked/Rel-18/25_series/25468/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35ffbd2f1f61eab0d03a73d99bd8f6ff9f19da46311bd389bbd6eded97bb839f +size 13149 diff --git a/marked/Rel-18/25_series/25468/f1091147d93cee4dfa88498610e395a7_img.jpg b/marked/Rel-18/25_series/25468/f1091147d93cee4dfa88498610e395a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..305bcea876bf73a0abfcec7b84966e9988abd0e8 --- /dev/null +++ b/marked/Rel-18/25_series/25468/f1091147d93cee4dfa88498610e395a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ba2db6ba7b22e2182104e88ec640c194293a7e35d04ec41c52e65cdffe8f474 +size 22817 diff --git a/marked/Rel-18/25_series/25468/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg b/marked/Rel-18/25_series/25468/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3da84ca92d7fb260e50292a3f712d10353406e59 --- /dev/null +++ b/marked/Rel-18/25_series/25468/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4fd18507fc93d5488f4b65b8c5ee26e3251f7df447586e21d797d2130b28c2e +size 11319 diff --git a/marked/Rel-18/29_series/29002/raw.md b/marked/Rel-18/29_series/29002/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..71ec98a583c6167255ae598d1184b024e715cc96 --- /dev/null +++ b/marked/Rel-18/29_series/29002/raw.md @@ -0,0 +1,58081 @@ + + +# 3GPP TS 29.002 V18.0.0 (2023-09) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mobile Application Part (MAP) specification (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- 1 Contents + +| | | | +|----|------------------------------------------------------------------------|----| +| 2 | Foreword..... | 28 | +| 3 | 1 Scope..... | 29 | +| 4 | 2 References..... | 29 | +| 5 | 3 Abbreviations..... | 35 | +| 6 | 4 Void..... | 36 | +| 7 | 5 Overload and compatibility overview..... | 36 | +| 8 | 5.1 Overload control..... | 36 | +| 9 | 5.1.1 Overload control for MSC (outside MAP)..... | 36 | +| 10 | 5.1.2 Overload control for MAP entities..... | 36 | +| 11 | 5.1.3 Congestion control for Signalling System No. 7..... | 40 | +| 12 | 5.2 Compatibility..... | 40 | +| 13 | 5.2.1 General..... | 40 | +| 14 | 5.2.2 Strategy for selecting the Application Context (AC) version..... | 40 | +| 15 | 5.2.2.1 Proposed method..... | 40 | +| 16 | 5.2.2.2 Managing the version look-up table..... | 41 | +| 17 | 5.2.2.3 Optimising the method..... | 42 | +| 18 | 6 Requirements concerning the use of SCCP and TC..... | 42 | +| 19 | 6.1 Use of SCCP..... | 42 | +| 20 | 6.1.1 SCCP Class..... | 42 | +| 21 | 6.1.2 Sub-System Number (SSN)..... | 42 | +| 22 | 6.1.3 SCCP addressing..... | 43 | +| 23 | 6.1.3.1 Introduction..... | 43 | +| 24 | 6.1.3.2 The Mobile-services Switching Centre (MSC)..... | 45 | +| 25 | 6.1.3.2.1 MSC interaction during handover or relocation..... | 45 | +| 26 | 6.1.3.2.2 MSC for short message routing..... | 45 | +| 27 | 6.1.3.2.3 MSC for location request routing..... | 45 | +| 28 | 6.1.3.2.4 MSC for LMU Control..... | 45 | +| 29 | 6.1.3.3 The Home Location Register (HLR)..... | 46 | +| 30 | 6.1.3.3.1 During call set-up..... | 46 | +| 31 | 6.1.3.3.2 Before location updating completion..... | 46 | +| 32 | 6.1.3.3.3 After location updating completion..... | 46 | +| 33 | 6.1.3.3.4 VLR restoration..... | 47 | +| 34 | 6.1.3.3.5 During Network-Requested PDP Context Activation..... | 47 | +| 35 | 6.1.3.3.6 Before GPRS location updating completion..... | 47 | +| 36 | 6.1.3.3.7 After GPRS location updating completion..... | 48 | +| 37 | 6.1.3.3.8 Query for a Location Request..... | 48 | +| 38 | 6.1.3.4 The Visitor Location Register (VLR)..... | 48 | +| 39 | 6.1.3.4.0 General..... | 48 | +| 40 | 6.1.3.4.1 Inter-VLR information retrieval..... | 48 | +| 41 | 6.1.3.4.2 HLR request..... | 48 | +| 42 | 6.1.3.4.3 CSS request..... | 49 | +| 43 | 6.1.3.5 The Interworking MSC (IWMSC) for Short Message Service..... | 49 | +| 44 | 6.1.3.6 The Equipment Identity Register (EIR)..... | 49 | +| 45 | 6.1.3.7 Void..... | 49 | +| 46 | 6.1.3.8 The Serving GPRS Support Node (SGSN)..... | 49 | +| 47 | 6.1.3.8.0 General..... | 49 | +| 48 | 6.1.3.8.1 HLR request..... | 49 | +| 49 | 6.1.3.8.2 GMSC request..... | 49 | +| 50 | 6.1.3.8.3 CSS request..... | 49 | +| 51 | 6.1.3.9 The Gateway GPRS Support Node (GGSN)..... | 49 | +| 52 | 6.1.3.10 The Gateway MSC (GMSC) for Short Message Service..... | 50 | +| 53 | 6.1.3.10A Void..... | 50 | +| 54 | 6.1.3.10A.1 Void..... | 50 | +| 55 | 6.1.3.10A.2 Void..... | 50 | + +| | | | | +|-----|-----------|----------------------------------------------------|----| +| 56 | 6.1.3.10B | The Gateway Mobile Location Centre (GMLC)..... | 50 | +| 57 | 6.1.3.10C | The CSG Subscriber Server (CSS)..... | 50 | +| 58 | 6.1.3.11 | Summary table..... | 50 | +| 59 | 6.2 | Use of TC..... | 54 | +| 60 | 7 | General on MAP services..... | 54 | +| 61 | 7.1 | Terminology and definitions..... | 54 | +| 62 | 7.2 | Modelling principles..... | 54 | +| 63 | 7.3 | Common MAP services..... | 55 | +| 64 | 7.3.1 | MAP-OPEN service..... | 56 | +| 65 | 7.3.2 | MAP-CLOSE service..... | 59 | +| 66 | 7.3.3 | MAP-DELIMITER service..... | 59 | +| 67 | 7.3.4 | MAP-U-ABORT service..... | 59 | +| 68 | 7.3.5 | MAP-P-ABORT service..... | 60 | +| 69 | 7.3.6 | MAP-NOTICE service..... | 61 | +| 70 | 7.3.7 | Void..... | 62 | +| 71 | 7.3.8 | Void..... | 62 | +| 72 | 7.3.9 | Void..... | 62 | +| 73 | 7.3.10 | Void..... | 62 | +| 74 | 7.4 | Sequencing of services..... | 62 | +| 75 | 7.5 | General rules for mapping of services onto TC..... | 63 | +| 76 | 7.5.1 | Mapping of common services..... | 63 | +| 77 | 7.5.2 | Mapping of user specific services..... | 64 | +| 78 | 7.6 | Definition of parameters..... | 65 | +| 79 | 7.6.1 | Common parameters..... | 65 | +| 80 | 7.6.1.1 | Invoke Id..... | 65 | +| 81 | 7.6.1.2 | Linked Id..... | 65 | +| 82 | 7.6.1.3 | Provider error..... | 65 | +| 83 | 7.6.1.4 | User error..... | 65 | +| 84 | 7.6.2 | Numbering and identification parameters..... | 69 | +| 85 | 7.6.2.1 | IMSI..... | 69 | +| 86 | 7.6.2.2 | TMSI..... | 69 | +| 87 | 7.6.2.3 | IMEI..... | 69 | +| 88 | 7.6.2.3a | IMEISV..... | 69 | +| 89 | 7.6.2.4 | Previous location area Id..... | 69 | +| 90 | 7.6.2.5 | Stored location area Id..... | 69 | +| 91 | 7.6.2.6 | Current location area Id..... | 69 | +| 92 | 7.6.2.7 | Target location area Id..... | 69 | +| 93 | 7.6.2.8 | Target cell Id..... | 69 | +| 94 | 7.6.2.8A | Target RNC Id..... | 69 | +| 95 | 7.6.2.9 | Void..... | 69 | +| 96 | 7.6.2.10 | Originating entity number..... | 70 | +| 97 | 7.6.2.11 | MSC number..... | 70 | +| 98 | 7.6.2.12 | Target MSC number..... | 70 | +| 99 | 7.6.2.13 | HLR number..... | 70 | +| 100 | 7.6.2.14 | VLR number..... | 70 | +| 101 | 7.6.2.15 | HLR Id..... | 70 | +| 102 | 7.6.2.16 | LMSI..... | 70 | +| 103 | 7.6.2.17 | MS ISDN..... | 70 | +| 104 | 7.6.2.17A | Additional MSISDN..... | 70 | +| 105 | 7.6.2.18 | OMC Id..... | 70 | +| 106 | 7.6.2.19 | Roaming number..... | 70 | +| 107 | 7.6.2.19A | Relocation Number List..... | 70 | +| 108 | 7.6.2.20 | Void..... | 70 | +| 109 | 7.6.2.21 | Handover number..... | 70 | +| 110 | 7.6.2.22 | Forwarded-to number..... | 71 | +| 111 | 7.6.2.22A | Long forwarded-to number..... | 71 | +| 112 | 7.6.2.22B | Long FTN Supported..... | 71 | +| 113 | 7.6.2.23 | Forwarded-to subaddress..... | 71 | +| 114 | 7.6.2.24 | Called number..... | 71 | +| 115 | 7.6.2.25 | Calling number..... | 71 | +| 116 | 7.6.2.26 | Originally dialled number..... | 71 | + +| | | | | +|-----|-----------|-------------------------------------------------------|----| +| 117 | 7.6.2.27 | Service centre address..... | 71 | +| 118 | 7.6.2.28 | Zone Code..... | 71 | +| 119 | 7.6.2.29 | MSISdn-Alert..... | 71 | +| 120 | 7.6.2.30 | Location Information..... | 71 | +| 121 | 7.6.2.30a | Location Information for GPRS..... | 71 | +| 122 | 7.6.2.30b | Location Information for EPS..... | 71 | +| 123 | 7.6.2.31 | GMSC Address..... | 71 | +| 124 | 7.6.2.32 | VMS Address..... | 72 | +| 125 | 7.6.2.33 | Group Id..... | 72 | +| 126 | 7.6.2.34 | North American Equal Access preferred Carrier Id..... | 72 | +| 127 | 7.6.2.35 | Void..... | 72 | +| 128 | 7.6.2.36 | Void..... | 72 | +| 129 | 7.6.2.37 | Serving cell Id..... | 72 | +| 130 | 7.6.2.38 | SGSN number..... | 72 | +| 131 | 7.6.2.39 | SGSN address..... | 72 | +| 132 | 7.6.2.40 | GGSN address..... | 72 | +| 133 | 7.6.2.41 | GGSN number..... | 72 | +| 134 | 7.6.2.42 | APN..... | 72 | +| 135 | 7.6.2.43 | Network Node number..... | 73 | +| 136 | 7.6.2.43A | Network Node Diameter Address..... | 73 | +| 137 | 7.6.2.44 | PDP-Type..... | 73 | +| 138 | 7.6.2.44A | Extension PDP-Type..... | 73 | +| 139 | 7.6.2.45 | PDP-Address..... | 73 | +| 140 | 7.6.2.45A | Extension PDP-Address..... | 73 | +| 141 | 7.6.2.46 | Additional number..... | 73 | +| 142 | 7.6.2.46A | Additional Network Node Diameter Address..... | 73 | +| 143 | 7.6.2.46B | Third Number..... | 73 | +| 144 | 7.6.2.46C | Third Network Node Diameter Address..... | 73 | +| 145 | 7.6.2.47 | P-TMSI..... | 73 | +| 146 | 7.6.2.48 | B-subscriber number..... | 74 | +| 147 | 7.6.2.49 | B-subscriber subaddress..... | 74 | +| 148 | 7.6.2.50 | LMU Number..... | 74 | +| 149 | 7.6.2.51 | MLC Number..... | 74 | +| 150 | 7.6.2.52 | Multicall Bearer Information..... | 74 | +| 151 | 7.6.2.53 | Multiple Bearer Requested..... | 74 | +| 152 | 7.6.2.54 | Multiple Bearer Not Supported..... | 74 | +| 153 | 7.6.2.55 | PDP-Charging Characteristics..... | 74 | +| 154 | 7.6.2.56 | Selected RAB ID..... | 74 | +| 155 | 7.6.2.57 | RAB ID..... | 74 | +| 156 | 7.6.2.58 | gsmSCF Address..... | 74 | +| 157 | 7.6.2.59 | V-GMLC Address..... | 74 | +| 158 | 7.6.2.60 | Void..... | 74 | +| 159 | 7.6.2.61 | H-GMLC Address..... | 74 | +| 160 | 7.6.2.62 | PPR Address..... | 75 | +| 161 | 7.6.2.63 | Routeing Number..... | 75 | +| 162 | 7.6.2.64 | Additional V-GMLC Address..... | 75 | +| 163 | 7.6.2.65 | MME Name..... | 75 | +| 164 | 7.6.2.66 | 3GPP AAA Server Name..... | 75 | +| 165 | 7.6.2.67 | CSS number..... | 75 | +| 166 | 7.6.2.68 | SGSN Name..... | 75 | +| 167 | 7.6.2.69 | SGSN Realm..... | 75 | +| 168 | 7.6.3 | Subscriber management parameters..... | 75 | +| 169 | 7.6.3.1 | Category..... | 75 | +| 170 | 7.6.3.2 | Equipment status..... | 75 | +| 171 | 7.6.3.2a | BMUEF..... | 75 | +| 172 | 7.6.3.3 | Extensible Bearer service..... | 75 | +| 173 | 7.6.3.4 | Extensible Teleservice..... | 75 | +| 174 | 7.6.3.5 | Extensible Basic Service Group..... | 76 | +| 175 | 7.6.3.6 | GSM bearer capability..... | 76 | +| 176 | 7.6.3.7 | Subscriber Status..... | 76 | +| 177 | 7.6.3.8 | CUG Outgoing Access indicator..... | 76 | + +| | | | | +|-----|-----------|----------------------------------------------------------------|----| +| 178 | 7.6.3.9 | Operator Determined Barring General Data..... | 76 | +| 179 | 7.6.3.10 | ODB HPLMN Specific Data..... | 78 | +| 180 | 7.6.3.11 | Regional Subscription Data..... | 78 | +| 181 | 7.6.3.12 | Regional Subscription Response..... | 79 | +| 182 | 7.6.3.13 | Roaming Restriction Due To Unsupported Feature..... | 79 | +| 183 | 7.6.3.14 | Extensible SS-Info..... | 79 | +| 184 | 7.6.3.15 | Extensible forwarding information..... | 79 | +| 185 | 7.6.3.16 | Extensible forwarding feature..... | 79 | +| 186 | 7.6.3.17 | Extensible SS-Status..... | 79 | +| 187 | 7.6.3.18 | Extensible Forwarding Options..... | 80 | +| 188 | 7.6.3.19 | Extensible No reply condition timer..... | 80 | +| 189 | 7.6.3.20 | Extensible Call barring information..... | 80 | +| 190 | 7.6.3.21 | Extensible Call barring feature..... | 80 | +| 191 | 7.6.3.22 | CUG info..... | 80 | +| 192 | 7.6.3.23 | CUG subscription..... | 80 | +| 193 | 7.6.3.24 | CUG interlock..... | 81 | +| 194 | 7.6.3.25 | CUG index..... | 81 | +| 195 | 7.6.3.26 | CUG feature..... | 81 | +| 196 | 7.6.3.27 | Inter CUG options..... | 81 | +| 197 | 7.6.3.28 | Intra CUG restrictions..... | 81 | +| 198 | 7.6.3.29 | Extensible SS-Data..... | 81 | +| 199 | 7.6.3.30 | Subscriber State..... | 82 | +| 200 | 7.6.3.31 | Requested Info..... | 82 | +| 201 | 7.6.3.31A | Requested Domain..... | 82 | +| 202 | 7.6.3.32 | Suppression of Announcement..... | 82 | +| 203 | 7.6.3.33 | Suppress T-CSI..... | 82 | +| 204 | 7.6.3.34 | GMSC CAMEL Subscription Info..... | 82 | +| 205 | 7.6.3.35 | VLR CAMEL Subscription Info..... | 82 | +| 206 | 7.6.3.36 | Supported CAMEL Phases in the VLR..... | 82 | +| 207 | 7.6.3.36A | Supported CAMEL Phases in the SGSN..... | 82 | +| 208 | 7.6.3.36B | Offered CAMEL4 CSIs in the VLR..... | 82 | +| 209 | 7.6.3.36C | Offered CAMEL4 CSIs in the SGSN..... | 82 | +| 210 | 7.6.3.36D | Offered CAMEL4 CSIs..... | 82 | +| 211 | 7.6.3.36E | Offered CAMEL4 CSIs in interrogating node..... | 82 | +| 212 | 7.6.3.36F | Offered CAMEL4 CSIs in VMSC..... | 82 | +| 213 | 7.6.3.36G | Offered CAMEL4 Functionalities..... | 83 | +| 214 | 7.6.3.36H | Supported CAMEL Phases..... | 83 | +| 215 | 7.6.3.36I | Supported CAMEL Phases in interrogating node..... | 83 | +| 216 | 7.6.3.37 | CUG Subscription Flag..... | 83 | +| 217 | 7.6.3.38 | CAMEL Subscription Info Withdraw..... | 83 | +| 218 | 7.6.3.39 | Voice Group Call Service (VGCS) Data..... | 83 | +| 219 | 7.6.3.40 | Voice Broadcast Service (VBS) Data..... | 83 | +| 220 | 7.6.3.41 | ISDN bearer capability..... | 83 | +| 221 | 7.6.3.42 | Lower layer Compatibility..... | 83 | +| 222 | 7.6.3.43 | High Layer Compatibility..... | 83 | +| 223 | 7.6.3.44 | Alerting Pattern..... | 83 | +| 224 | 7.6.3.45 | GPRS Subscription Data Withdraw..... | 83 | +| 225 | 7.6.3.45A | EPS Subscription Data Withdraw..... | 83 | +| 226 | 7.6.3.46 | GPRS Subscription Data..... | 84 | +| 227 | 7.6.3.46A | EPS Subscription Data..... | 84 | +| 228 | 7.6.3.47 | QoS-Subscribed..... | 84 | +| 229 | 7.6.3.48 | VPLMN address allowed..... | 84 | +| 230 | 7.6.3.49 | Roaming Restricted In SGSN/MME Due To Unsupported Feature..... | 84 | +| 231 | 7.6.3.50 | Network Access Mode..... | 84 | +| 232 | 7.6.3.51 | Mobile Not Reachable Reason..... | 84 | +| 233 | 7.6.3.52 | Cancellation Type..... | 84 | +| 234 | 7.6.3.53 | All GPRS Data..... | 84 | +| 235 | 7.6.3.54 | Complete Data List Included..... | 84 | +| 236 | 7.6.3.55 | PDP Context Identifier..... | 84 | +| 237 | 7.6.3.56 | LSA Information..... | 84 | +| 238 | 7.6.3.57 | SoLSA support indicator..... | 85 | + +| | | | | +|-----|--------------------|--------------------------------------------------------|----| +| 239 | 7.6.3.58 | LSA Information Withdraw..... | 85 | +| 240 | 7.6.3.59 | LMU Indicator..... | 85 | +| 241 | 7.6.3.60 | LCS Information..... | 85 | +| 242 | 7.6.3.61 | GMLC List..... | 85 | +| 243 | 7.6.3.62 | LCS Privacy Exception List..... | 85 | +| 244 | 7.6.3.62A | Additional LCS Privacy Exception List..... | 85 | +| 245 | 7.6.3.63 | LCS Privacy Exception Parameters..... | 85 | +| 246 | 7.6.3.64 | External Client List..... | 86 | +| 247 | 7.6.3.65 | Internal Client List..... | 86 | +| 248 | 7.6.3.65A | MO-LR List..... | 86 | +| 249 | 7.6.3.65B | Privacy Notification to MS User..... | 86 | +| 250 | 7.6.3.65C | GMLC List Withdraw..... | 86 | +| 251 | 7.6.3.65D | Service Type List..... | 86 | +| 252 | 7.6.3.66 | IST Alert Timer..... | 86 | +| 253 | 7.6.3.67 | Call Termination Indicator..... | 86 | +| 254 | 7.6.3.68 | IST Information Withdraw..... | 86 | +| 255 | 7.6.3.69 | IST Support Indicator..... | 86 | +| 256 | 7.6.3.70 | Super-Charger Supported In HLR..... | 87 | +| 257 | 7.6.3.71 | Super-Charger Supported In Serving Network Entity..... | 87 | +| 258 | 7.6.3.72 | Age Indicator..... | 87 | +| 259 | 7.6.3.73 | GPRS enhancements support indicator..... | 87 | +| 260 | 7.6.3.74 | Extension QoS-Subscribed..... | 87 | +| 261 | 7.6.3.75 | SGSN CAMEL Subscription Info..... | 87 | +| 262 | 7.6.3.75A | Extension-2 QoS-Subscribed..... | 87 | +| 263 | 7.6.3.75B | Extension-3 QoS-Subscribed..... | 87 | +| 264 | 7.6.3.75C | Extension-4 QoS-Subscribed..... | 87 | +| 265 | 7.6.3.76 | MO-SMS-CSI..... | 87 | +| 266 | 7.6.3.76a | MT-SMS-CSI..... | 88 | +| 267 | 7.6.3.77 | GPRS-CSI..... | 88 | +| 268 | 7.6.3.78 | CAMEL subscription info..... | 88 | +| 269 | 7.6.3.83 | Call Barring Data..... | 88 | +| 270 | 7.6.3.84 | Call Forwarding Data..... | 88 | +| 271 | 7.6.3.85 | ODB Data..... | 89 | +| 272 | 7.6.3.86 | Requested Subscription Info..... | 89 | +| 273 | 7.6.3.87 | CS Allocation/Retention priority..... | 89 | +| 274 | 7.6.3.88 | ODB Info..... | 89 | +| 275 | 7.6.3.89 | Suppress VT-CSI..... | 89 | +| 276 | 7.6.3.90 | Suppress Incoming Call Barring..... | 89 | +| 277 | 7.6.3.91 | gsmSCF Initiated Call..... | 89 | +| 278 | 7.6.3.91a | SuppressMTSS..... | 89 | +| 279 | 7.6.3.92 | Call barring support indicator..... | 89 | +| 280 | 7.6.3.93 | MNP Info Result..... | 89 | +| 281 | 7.6.3.94 | Allowed Services..... | 89 | +| 282 | 7.6.3.95 | Unavailability Cause..... | 90 | +| 283 | 7.6.3.96 | MNP Requested Info..... | 90 | +| 284 | 7.6.3.97 | Access Restriction Data..... | 90 | +| 285 | 7.6.3.98 | Supported RAT types indicator..... | 90 | +| 286 | 7.6.3.99 | UE SRVCC Capability..... | 90 | +| 287 | 7.6.3.100 | Temporary Empty CSG Subscription data Indicator..... | 90 | +| 288 | 7.6.3.101 | WLAN-offloadability..... | 90 | +| 289 | 7.6.3.102 | IMSI-Group-Id..... | 90 | +| 290 | 7.6.4 | Supplementary services parameters..... | 90 | +| 291 | 7.6.4.1 | SS-Code..... | 90 | +| 292 | 7.6.4.1A | SS-Code 2..... | 91 | +| 293 | 7.6.4.2 | SS-Status..... | 91 | +| 294 | 7.6.4.3 | SS-Data..... | 91 | +| 295 | 7.6.4.4 | Override Category..... | 91 | +| 296 | 7.6.4.5 | CLI Restriction Option..... | 91 | +| 297 | 7.6.4.6 | Forwarding Options..... | 92 | +| 298 | 7.6.4.7 | No reply condition timer..... | 92 | +| 299 | 7.6.4.8 - 7.6.4.14 | Void..... | 92 | + +| | | | | +|-----|---------------------|--------------------------------------------------|----| +| 300 | 7.6.4.15 | Forwarding information..... | 92 | +| 301 | 7.6.4.16 | Forwarding feature..... | 92 | +| 302 | 7.6.4.17 | Void..... | 92 | +| 303 | 7.6.4.18 | Call barring information..... | 92 | +| 304 | 7.6.4.19 | Call barring feature..... | 93 | +| 305 | 7.6.4.20 | New password..... | 93 | +| 306 | 7.6.4.21 | Current password..... | 93 | +| 307 | 7.6.4.22 | Guidance information..... | 93 | +| 308 | 7.6.4.23 | Void..... | 93 | +| 309 | 7.6.4.24 | SS-Info..... | 93 | +| 310 | 7.6.4.25 - 7.6.4.35 | Void..... | 93 | +| 311 | 7.6.4.36 | USSD Data Coding Scheme..... | 94 | +| 312 | 7.6.4.37 | USSD String..... | 94 | +| 313 | 7.6.4.38 | Bearer service..... | 94 | +| 314 | 7.6.4.38A | Bearer Service 2..... | 94 | +| 315 | 7.6.4.39 | Teleservice..... | 94 | +| 316 | 7.6.4.39A | Teleservice 2..... | 94 | +| 317 | 7.6.4.40 | Basic Service Group..... | 94 | +| 318 | 7.6.4.41 | eMLPP information..... | 94 | +| 319 | 7.6.4.42 | SS-event..... | 94 | +| 320 | 7.6.4.43 | SS-event data..... | 95 | +| 321 | 7.6.4.44 | LCS Privacy Exceptions..... | 95 | +| 322 | 7.6.4.45 | Mobile Originating Location Request (MO-LR)..... | 95 | +| 323 | 7.6.4.46 | NbrUser..... | 95 | +| 324 | 7.6.4.47 | MC Subscription Data..... | 95 | +| 325 | 7.6.4.48 | MC Information..... | 95 | +| 326 | 7.6.4.49 | CCBS Request State..... | 96 | +| 327 | 7.6.4.50 | Basic Service Group 2..... | 96 | +| 328 | 7.6.5 | Call parameters..... | 96 | +| 329 | 7.6.5.1 | Call reference number..... | 96 | +| 330 | 7.6.5.2 | Interrogation type..... | 96 | +| 331 | 7.6.5.3 | OR interrogation..... | 96 | +| 332 | 7.6.5.4 | OR capability..... | 96 | +| 333 | 7.6.5.5 | Forwarding reason..... | 96 | +| 334 | 7.6.5.6 | Forwarding interrogation required..... | 97 | +| 335 | 7.6.5.7 | O-CSI..... | 97 | +| 336 | 7.6.5.7A | D-CSI..... | 97 | +| 337 | 7.6.5.7B | T-CSI..... | 97 | +| 338 | 7.6.5.7C | VT-CSI..... | 97 | +| 339 | 7.6.5.7D | O-IM-CSI..... | 97 | +| 340 | 7.6.5.7E | D-IM-CSI..... | 97 | +| 341 | 7.6.5.7F | VT-IM-CSI..... | 97 | +| 342 | 7.6.5.8 | Void..... | 97 | +| 343 | 7.6.5.9 | Void..... | 97 | +| 344 | 7.6.5.10 | Void..... | 97 | +| 345 | 7.6.5.11 | CCBS Feature..... | 97 | +| 346 | 7.6.5.12 | UU Data..... | 98 | +| 347 | 7.6.5.14 | Number Portability Status..... | 98 | +| 348 | 7.6.5.15 | Pre-paging supported..... | 98 | +| 349 | 7.6.5.16 | MT Roaming Retry Supported..... | 98 | +| 350 | 7.6.5.17 | MT Roaming Retry..... | 98 | +| 351 | 7.6.5.18 | Paging Area..... | 98 | +| 352 | 7.6.5.19 | Call Priority..... | 98 | +| 353 | 7.6.5.20 | MTRF Supported..... | 98 | +| 354 | 7.6.5.21 | LCLS Global Call Reference (LCLS GCR)..... | 98 | +| 355 | 7.6.5.22 | LCLS-Negotiation..... | 98 | +| 356 | 7.6.5.23 | LCLS-Configuration-Preference..... | 98 | +| 357 | 7.6.6 | Radio parameters..... | 98 | +| 358 | 7.6.6.1 - 7.6.6.3 | Void..... | 99 | +| 359 | 7.6.6.4 | GERAN Classmark..... | 99 | +| 360 | 7.6.6.5 | BSSMAP Service Handover..... | 99 | + +| | | | | +|-----|-----------|-------------------------------------------------|-----| +| 361 | 7.6.6.5A | BSSMAP Service Handover List..... | 99 | +| 362 | 7.6.6.6 | RANAP Service Handover..... | 99 | +| 363 | 7.6.6.7 | HO-Number Not Required..... | 99 | +| 364 | 7.6.6.8 | Integrity Protection Information..... | 99 | +| 365 | 7.6.6.9 | Encryption Information..... | 99 | +| 366 | 7.6.6.10 | Radio Resource Information..... | 99 | +| 367 | 7.6.6.10A | Radio Resource List..... | 99 | +| 368 | 7.6.6.10B | Chosen Radio Resource Information..... | 99 | +| 369 | 7.6.6.11 | Key Status..... | 99 | +| 370 | 7.6.6.12 | Selected UMTS Algorithms..... | 99 | +| 371 | 7.6.6.13 | Allowed GSM Algorithms..... | 99 | +| 372 | 7.6.6.14 | Allowed UMTS Algorithms..... | 100 | +| 373 | 7.6.6.15 | Selected GSM Algorithm..... | 100 | +| 374 | 7.6.6.16 | Iu-Currently Used Codec..... | 100 | +| 375 | 7.6.6.17 | Iu-Supported Codecs List..... | 100 | +| 376 | 7.6.6.17A | Iu-Available Codecs List..... | 100 | +| 377 | 7.6.6.18 | Iu-Selected Codec..... | 100 | +| 378 | 7.6.6.19 | RAB Configuration Indicator..... | 100 | +| 379 | 7.6.6.20 | UESBI-Iu..... | 100 | +| 380 | 7.6.6.21 | Alternative Channel Type..... | 100 | +| 381 | 7.6.6.22 | AoIP-Supported Codecs List Anchor..... | 100 | +| 382 | 7.6.6.23 | AoIP-Available Codecs List Map..... | 100 | +| 383 | 7.6.6.24 | AoIP-Selected Codec Target..... | 100 | +| 384 | 7.6.7 | Authentication parameters..... | 101 | +| 385 | 7.6.7.1 | Authentication set list..... | 101 | +| 386 | 7.6.7.2 | Rand..... | 101 | +| 387 | 7.6.7.3 | Sres..... | 101 | +| 388 | 7.6.7.4 | Kc..... | 101 | +| 389 | 7.6.7.5 | Xres..... | 101 | +| 390 | 7.6.7.5A | Ck..... | 101 | +| 391 | 7.6.7.5B | Ik..... | 101 | +| 392 | 7.6.7.5C | Autn..... | 101 | +| 393 | 7.6.7.5D | KASME..... | 101 | +| 394 | 7.6.7.6 | Cksn..... | 101 | +| 395 | 7.6.7.6A | Ksi..... | 101 | +| 396 | 7.6.7.6B | Auts..... | 101 | +| 397 | 7.6.7.7 | Ciphering mode..... | 102 | +| 398 | 7.6.7.8 | Current Security Context..... | 102 | +| 399 | 7.6.7.9 | Failure cause..... | 102 | +| 400 | 7.6.7.10 | Re-attempt..... | 102 | +| 401 | 7.6.7.11 | Access Type..... | 102 | +| 402 | 7.6.8 | Short message parameters..... | 102 | +| 403 | 7.6.8.1 | SM-RP-DA..... | 102 | +| 404 | 7.6.8.2 | SM-RP-OA..... | 102 | +| 405 | 7.6.8.3 | MWD status..... | 102 | +| 406 | 7.6.8.4 | SM-RP-UI..... | 103 | +| 407 | 7.6.8.5 | SM-RP-PRI..... | 103 | +| 408 | 7.6.8.6 | SM Delivery Outcome..... | 103 | +| 409 | 7.6.8.7 | More Messages To Send..... | 103 | +| 410 | 7.6.8.8 | Alert Reason..... | 103 | +| 411 | 7.6.8.9 | Absent Subscriber Diagnostic SM..... | 103 | +| 412 | 7.6.8.10 | Alert Reason Indicator..... | 103 | +| 413 | 7.6.8.10A | Additional Alert Reason Indicator..... | 103 | +| 414 | 7.6.8.11 | Additional SM Delivery Outcome..... | 103 | +| 415 | 7.6.8.12 | Additional Absent Subscriber Diagnostic SM..... | 103 | +| 416 | 7.6.8.13 | Delivery Outcome Indicator..... | 104 | +| 417 | 7.6.8.14 | GPRS Node Indicator..... | 104 | +| 418 | 7.6.8.14A | IMS Node Indicator..... | 104 | +| 419 | 7.6.8.15 | GPRS Support Indicator..... | 104 | +| 420 | 7.6.8.16 | SM-RP-MTI..... | 104 | +| 421 | 7.6.8.17 | SM-RP-SMEA..... | 104 | + +| | | | | +|-----|-----------|------------------------------------------------------|-----| +| 422 | 7.6.8.18 | IP-SM-GW SM Delivery Outcome..... | 104 | +| 423 | 7.6.8.19 | IP-SM-GW Absent Subscriber Diagnostic SM..... | 104 | +| 424 | 7.6.8.20 | IP-SM-GW Indicator..... | 104 | +| 425 | 7.6.8.21 | SM Delivery Timer..... | 104 | +| 426 | 7.6.8.22 | SM Delivery Start Time..... | 104 | +| 427 | 7.6.8.23 | Maximum Retransmission Time..... | 104 | +| 428 | 7.6.8.24 | Requested Retransmission Time..... | 104 | +| 429 | 7.6.8.25 | Maximum UE Availability Time..... | 105 | +| 430 | 7.6.8.26 | SMS-GMSC Alert Event..... | 105 | +| 431 | 7.6.8.27 | SMS-GMSC Address..... | 105 | +| 432 | 7.6.8.28 | SMS-GMSC Diameter Address..... | 105 | +| 433 | 7.6.8.29 | New SGSN Number..... | 105 | +| 434 | 7.6.8.30 | New MME Number..... | 105 | +| 435 | 7.6.8.31 | New SGSN Diameter Address..... | 105 | +| 436 | 7.6.8.32 | New MME Diameter Address..... | 105 | +| 437 | 7.6.8.33 | New MSC Number..... | 105 | +| 438 | 7.6.8.34 | SMSF 3GPP Absent Subscriber Diagnostic SM..... | 105 | +| 439 | 7.6.8.35 | SMSF Non 3GPP Absent Subscriber Diagnostic SM..... | 105 | +| 440 | 7.6.8.36 | SMSF 3GPP Delivery Outcome Indicator..... | 105 | +| 441 | 7.6.8.37 | SMSF Non-3GPP Delivery Outcome Indicator..... | 106 | +| 442 | 7.6.8.38 | SMSF 3GPP SM Delivery Outcome..... | 106 | +| 443 | 7.6.8.39 | SMSF Non-3GPP SM Delivery Outcome..... | 106 | +| 444 | 7.6.8.40 | SMSF 3GPP Absent Subscriber Diagnostic SM..... | 106 | +| 445 | 7.6.8.41 | SMSF Non 3GPP Absent Subscriber Diagnostic SM..... | 106 | +| 446 | 7.6.9 | Access and signalling system related parameters..... | 106 | +| 447 | 7.6.9.1 | AN-apdu..... | 106 | +| 448 | 7.6.9.2 | CM service type..... | 106 | +| 449 | 7.6.9.3 | Access connection status..... | 106 | +| 450 | 7.6.9.4 | External Signal Information..... | 107 | +| 451 | 7.6.9.5 | Access signalling information..... | 107 | +| 452 | 7.6.9.6 | Location update type..... | 107 | +| 453 | 7.6.9.7 | Protocol ID..... | 107 | +| 454 | 7.6.9.8 | Network signal information..... | 107 | +| 455 | 7.6.9.8A | Network signal information 2..... | 108 | +| 456 | 7.6.9.9 | Call Info..... | 108 | +| 457 | 7.6.9.10 | Additional signal info..... | 108 | +| 458 | 7.6.10 | System operations parameters..... | 108 | +| 459 | 7.6.10.1 | Network resources..... | 109 | +| 460 | 7.6.10.2 | Trace reference..... | 109 | +| 461 | 7.6.10.2A | Trace reference 2..... | 109 | +| 462 | 7.6.10.3 | Trace type..... | 109 | +| 463 | 7.6.10.4 | Additional network resources..... | 109 | +| 464 | 7.6.10.5 | Trace depth list..... | 109 | +| 465 | 7.6.10.6 | Trace NE type list..... | 109 | +| 466 | 7.6.10.7 | Trace interface list..... | 109 | +| 467 | 7.6.10.8 | Trace event list..... | 109 | +| 468 | 7.6.10.9 | Trace support indicator..... | 110 | +| 469 | 7.6.10.10 | Trace Propagation List..... | 110 | +| 470 | 7.6.10.11 | MDT-Configuration..... | 110 | +| 471 | 7.6.10.12 | MDT User Consent..... | 110 | +| 472 | 7.6.11 | Location Service Parameters..... | 110 | +| 473 | 7.6.11.1 | Age of Location Estimate..... | 110 | +| 474 | 7.6.11.2 | Deferred MT-LR Response Indicator..... | 110 | +| 475 | 7.6.11.3 | Deferred MT-LR Data..... | 110 | +| 476 | 7.6.11.4 | LCS Client ID..... | 110 | +| 477 | 7.6.11.5 | LCS Event..... | 110 | +| 478 | 7.6.11.7 | LCS Priority..... | 110 | +| 479 | 7.6.11.8 | LCS QoS..... | 110 | +| 480 | 7.6.11.9 | CS LCS Not Supported by UE..... | 111 | +| 481 | 7.6.11.10 | PS LCS Not Supported by UE..... | 111 | +| 482 | 7.6.11.11 | Location Estimate..... | 111 | + +| | | | | +|-----|------------|--------------------------------------------------------------------------|-----| +| 483 | 7.6.11.11A | GERAN Positioning Data..... | 111 | +| 484 | 7.6.11.11B | UTRAN Positioning Data..... | 111 | +| 485 | 7.6.11.11C | GERAN GANSS Positioning Data..... | 112 | +| 486 | 7.6.11.11D | UTRAN GANSS Positioning Data..... | 112 | +| 487 | 7.6.11.11E | UTRAN Additional Positioning Data..... | 112 | +| 488 | 7.6.11.11F | UTRAN Barometric Pressure Measurement..... | 112 | +| 489 | 7.6.11.11G | UTRAN Civic Address..... | 112 | +| 490 | 7.6.11.12 | Location Type..... | 112 | +| 491 | 7.6.11.13 | NA-ESRD..... | 112 | +| 492 | 7.6.11.14 | NA-ESRK..... | 112 | +| 493 | 7.6.11.15 | LCS Service Type Id..... | 112 | +| 494 | 7.6.11.16 | Privacy Override..... | 112 | +| 495 | 7.6.11.17 | Supported LCS Capability Sets..... | 113 | +| 496 | 7.6.11.18 | LCS Codeword..... | 113 | +| 497 | 7.6.11.19 | NA-ESRK Request..... | 113 | +| 498 | 7.6.11.20 | Supported GAD Shapes..... | 113 | +| 499 | 7.6.11.21 | Additional Location Estimate..... | 113 | +| 500 | 7.6.11.22 | Cell Id Or SAI..... | 113 | +| 501 | 7.6.11.23 | LCS-Reference Number..... | 113 | +| 502 | 7.6.11.24 | LCS Privacy Check..... | 113 | +| 503 | 7.6.11.25 | Additional LCS Capability Sets..... | 114 | +| 504 | 7.6.11.26 | Area Event Info..... | 114 | +| 505 | 7.6.11.27 | Velocity Estimate..... | 114 | +| 506 | 7.6.11.28 | Accuracy Fulfilment Indicator..... | 114 | +| 507 | 7.6.11.29 | MO-LR Short Circuit Indicator..... | 114 | +| 508 | 7.6.11.30 | Reporting PLMN List..... | 114 | +| 509 | 7.6.11.31 | Periodic LDR information..... | 114 | +| 510 | 7.6.11.32 | Sequence Number..... | 114 | +| 511 | 7.6.12 | Void..... | 114 | +| 512 | 7.7 | Representation of a list of a basic parameter in service-primitives..... | 114 | +| 513 | 8 | Mobility services..... | 115 | +| 514 | 8.1 | Location management services..... | 115 | +| 515 | 8.1.1 | Void..... | 115 | +| 516 | 8.1.1.1 | Void..... | 115 | +| 517 | 8.1.1.2 | Void..... | 115 | +| 518 | 8.1.1.3 | Void..... | 115 | +| 519 | 8.1.2 | MAP_UPDATE_LOCATION service..... | 115 | +| 520 | 8.1.2.1 | Definition..... | 115 | +| 521 | 8.1.2.2 | Service primitives..... | 115 | +| 522 | 8.1.2.3 | Parameter definitions and use..... | 116 | +| 523 | 8.1.3 | MAP_CANCEL_LOCATION service..... | 119 | +| 524 | 8.1.3.1 | Definition..... | 119 | +| 525 | 8.1.3.2 | Service primitives..... | 119 | +| 526 | 8.1.3.3 | Parameter definitions and use..... | 119 | +| 527 | 8.1.4 | MAP_SEND_IDENTIFICATION service..... | 120 | +| 528 | 8.1.4.1 | Definition..... | 120 | +| 529 | 8.1.4.2 | Service primitives..... | 120 | +| 530 | 8.1.4.3 | Parameter definitions and use..... | 121 | +| 531 | 8.1.5 | Void..... | 122 | +| 532 | 8.1.5.1 | Void..... | 122 | +| 533 | 8.1.5.2 | Void..... | 122 | +| 534 | 8.1.5.3 | Void..... | 122 | +| 535 | 8.1.6 | MAP_PURGE_MS service..... | 122 | +| 536 | 8.1.6.1 | Definition..... | 122 | +| 537 | 8.1.6.2 | Service primitives..... | 123 | +| 538 | 8.1.6.3 | Parameter definitions and use..... | 123 | +| 539 | 8.1.7 | MAP_UPDATE_GPRS_LOCATION service..... | 124 | +| 540 | 8.1.7.1 | Definition..... | 124 | +| 541 | 8.1.7.2 | Service primitives..... | 124 | +| 542 | 8.1.7.3 | Parameter definitions and use..... | 125 | +| 543 | 8.1.8 | MAP-NOTE-MM-EVENT..... | 129 | + +| | | | | +|-----|----------|----------------------------------------------|-----| +| 544 | 8.1.8.1 | Definition..... | 129 | +| 545 | 8.1.8.2 | Service primitives..... | 129 | +| 546 | 8.1.8.3 | Parameter use..... | 130 | +| 547 | 8.1.9 | MAP_UPDATE_VCSG_LOCATION service..... | 131 | +| 548 | 8.1.9.1 | Definition..... | 131 | +| 549 | 8.1.9.2 | Service primitives..... | 131 | +| 550 | 8.1.9.3 | Parameter definitions and use..... | 131 | +| 551 | 8.1.10 | MAP_CANCEL_VCSG_LOCATION service..... | 132 | +| 552 | 8.1.10.1 | Definition..... | 132 | +| 553 | 8.1.10.2 | Service primitives..... | 132 | +| 554 | 8.1.10.3 | Parameter definitions and use..... | 132 | +| 555 | 8.2 | Paging and search..... | 133 | +| 556 | 8.2.1 | MAP_PAGE service..... | 133 | +| 557 | 8.2.1.1 | Definition..... | 133 | +| 558 | 8.2.1.2 | Service primitives..... | 133 | +| 559 | 8.2.1.3 | Parameter definitions and use..... | 133 | +| 560 | 8.2.2 | MAP_SEARCH_FOR_MS service..... | 134 | +| 561 | 8.2.2.1 | Definition..... | 134 | +| 562 | 8.2.2.2 | Service primitives..... | 134 | +| 563 | 8.2.2.3 | Parameter definitions and use..... | 134 | +| 564 | 8.3 | Access management services..... | 135 | +| 565 | 8.3.1 | MAP_PROCESS_ACCESS_REQUEST service..... | 135 | +| 566 | 8.3.1.1 | Definition..... | 135 | +| 567 | 8.3.1.2 | Service primitives..... | 135 | +| 568 | 8.3.1.3 | Parameter definitions and use..... | 135 | +| 569 | 8.4 | Handover services..... | 136 | +| 570 | 8.4.1 | MAP_PREPARE_HANDOVER service..... | 136 | +| 571 | 8.4.1.1 | Definition..... | 137 | +| 572 | 8.4.1.2 | Service primitives..... | 137 | +| 573 | 8.4.1.3 | Parameter use..... | 137 | +| 574 | 8.4.2 | MAP_SEND_END_SIGNAL service..... | 141 | +| 575 | 8.4.2.1 | Definition..... | 141 | +| 576 | 8.4.2.2 | Service primitives..... | 142 | +| 577 | 8.4.2.3 | Parameter use..... | 142 | +| 578 | 8.4.3 | MAP_PROCESS_ACCESS_SIGNALLING service..... | 142 | +| 579 | 8.4.3.1 | Definition..... | 142 | +| 580 | 8.4.3.2 | Service primitives..... | 142 | +| 581 | 8.4.3.3 | Parameter use..... | 142 | +| 582 | 8.4.4 | MAP_FORWARD_ACCESS_SIGNALLING service..... | 144 | +| 583 | 8.4.4.1 | Definition..... | 144 | +| 584 | 8.4.4.2 | Service primitives..... | 144 | +| 585 | 8.4.4.3 | Parameter use..... | 144 | +| 586 | 8.4.5 | MAP_PREPARE_SUBSEQUENT_HANDOVER service..... | 147 | +| 587 | 8.4.5.1 | Definition..... | 147 | +| 588 | 8.4.5.2 | Service primitives..... | 147 | +| 589 | 8.4.5.3 | Parameter use..... | 147 | +| 590 | 8.4.6 | MAP_ALLOCATE_HANDOVER_NUMBER service..... | 148 | +| 591 | 8.4.6.1 | Definition..... | 148 | +| 592 | 8.4.6.2 | Service primitives..... | 148 | +| 593 | 8.4.6.3 | Parameter use..... | 148 | +| 594 | 8.4.7 | MAP_SEND_HANDOVER_REPORT service..... | 148 | +| 595 | 8.4.7.1 | Definition..... | 148 | +| 596 | 8.4.7.2 | Service primitives..... | 149 | +| 597 | 8.4.7.3 | Parameter use..... | 149 | +| 598 | 8.5 | Authentication management services..... | 149 | +| 599 | 8.5.1 | MAP_AUTHENTICATE service..... | 149 | +| 600 | 8.5.1.1 | Definition..... | 149 | +| 601 | 8.5.1.2 | Service primitives..... | 149 | +| 602 | 8.5.1.3 | Parameter use..... | 150 | +| 603 | 8.5.2 | MAP_SEND_AUTHENTICATION_INFO service..... | 150 | +| 604 | 8.5.2.1 | Definition..... | 150 | + +| | | | | +|-----|----------|--------------------------------------------------------------------|-----| +| 605 | 8.5.2.2 | Service primitives..... | 151 | +| 606 | 8.5.2.3 | Parameter use..... | 151 | +| 607 | 8.5.3 | MAP_AUTHENTICATION_FAILURE_REPORT service..... | 153 | +| 608 | 8.5.3.1 | Definition..... | 153 | +| 609 | 8.5.3.2 | Service primitives..... | 153 | +| 610 | 8.5.3.3 | Parameter use..... | 153 | +| 611 | 8.6 | Security management services..... | 154 | +| 612 | 8.6.1 | MAP_SET_CIPHERING_MODE service..... | 154 | +| 613 | 8.6.1.1 | Definitions..... | 154 | +| 614 | 8.6.1.2 | Service primitives..... | 154 | +| 615 | 8.6.1.3 | Parameter use..... | 154 | +| 616 | 8.7 | International mobile equipment identities management services..... | 154 | +| 617 | 8.7.1 | MAP_CHECK_IMEI service..... | 154 | +| 618 | 8.7.1.1 | Definition..... | 154 | +| 619 | 8.7.1.2 | Service primitives..... | 155 | +| 620 | 8.7.1.3 | Parameter use..... | 155 | +| 621 | 8.7.2 | MAP_OBTAIN_IMEI service..... | 156 | +| 622 | 8.7.2.1 | Definition..... | 156 | +| 623 | 8.7.2.2 | Service primitives..... | 156 | +| 624 | 8.7.2.3 | Parameter use..... | 156 | +| 625 | 8.8 | Subscriber management services..... | 156 | +| 626 | 8.8.1 | MAP-INSERT-SUBSCRIBER-DATA service..... | 156 | +| 627 | 8.8.1.1 | Definition..... | 156 | +| 628 | 8.8.1.2 | Service primitives..... | 157 | +| 629 | 8.8.1.3 | Parameter use..... | 158 | +| 630 | 8.8.1.4 | Basic service information related to supplementary services..... | 172 | +| 631 | 8.8.2 | MAP-DELETE-SUBSCRIBER-DATA service..... | 173 | +| 632 | 8.8.2.1 | Definition..... | 173 | +| 633 | 8.8.2.2 | Service primitives..... | 173 | +| 634 | 8.8.2.3 | Parameter use..... | 174 | +| 635 | 8.9 | Identity management services..... | 178 | +| 636 | 8.9.1 | MAP-PROVIDE-IMSI service..... | 178 | +| 637 | 8.9.1.1 | Definition..... | 179 | +| 638 | 8.9.1.2 | Service primitives..... | 179 | +| 639 | 8.9.1.3 | Parameter use..... | 179 | +| 640 | 8.9.2 | MAP-FORWARD-NEW-TMSI service..... | 179 | +| 641 | 8.9.2.1 | Definition..... | 179 | +| 642 | 8.9.2.2 | Service primitives..... | 179 | +| 643 | 8.9.2.3 | Parameter use..... | 179 | +| 644 | 8.10 | Fault recovery services..... | 179 | +| 645 | 8.10.1 | MAP_RESET service..... | 179 | +| 646 | 8.10.1.1 | Definition..... | 180 | +| 647 | 8.10.1.2 | Service primitives..... | 180 | +| 648 | 8.10.1.3 | Parameter definition and use..... | 180 | +| 649 | 8.10.2 | MAP_FORWARD_CHECK_SS_INDICATION service..... | 181 | +| 650 | 8.10.2.1 | Definition..... | 181 | +| 651 | 8.10.2.2 | Service primitives..... | 181 | +| 652 | 8.10.2.3 | Parameter definition and use..... | 181 | +| 653 | 8.10.3 | MAP_RESTORE_DATA service..... | 182 | +| 654 | 8.10.3.1 | Definition..... | 182 | +| 655 | 8.10.3.2 | Service primitives..... | 182 | +| 656 | 8.10.3.3 | Parameter definitions and use..... | 182 | +| 657 | 8.11 | Subscriber Information services..... | 184 | +| 658 | 8.11.1 | MAP-ANY-TIME-INTERROGATION service..... | 184 | +| 659 | 8.11.1.1 | Definition..... | 184 | +| 660 | 8.11.1.2 | Service primitives..... | 184 | +| 661 | 8.11.1.3 | Parameter definition and use..... | 185 | +| 662 | 8.11.2 | MAP-PROVIDE-SUBSCRIBER-INFO service..... | 186 | +| 663 | 8.11.2.1 | Definition..... | 186 | +| 664 | 8.11.2.2 | Service primitives..... | 186 | +| 665 | 8.11.2.3 | Parameter definition and use..... | 186 | + +| | | | | +|-----|----------|------------------------------------------------------|-----| +| 666 | 8.11.3 | MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION service..... | 187 | +| 667 | 8.11.3.1 | Definition..... | 187 | +| 668 | 8.11.3.2 | Service primitives..... | 187 | +| 669 | 8.11.3.3 | Parameter definition and use..... | 188 | +| 670 | 8.11.4 | MAP-ANY-TIME-MODIFICATION service..... | 189 | +| 671 | 8.11.4.1 | Definition..... | 189 | +| 672 | 8.11.4.2 | Service primitives..... | 189 | +| 673 | 8.11.4.3 | Parameter definition and use..... | 189 | +| 674 | 8.11.5 | MAP-NOTE-SUBSCRIBER-DATA-MODIFIED service..... | 190 | +| 675 | 8.11.5.1 | Definition..... | 190 | +| 676 | 8.11.5.2 | Service primitives..... | 190 | +| 677 | 8.11.5.3 | Parameter definition and use..... | 191 | +| 678 | 9 | Operation and maintenance services..... | 192 | +| 679 | 9.1 | Subscriber tracing services..... | 192 | +| 680 | 9.1.1 | MAP-ACTIVATE-TRACE-MODE service..... | 192 | +| 681 | 9.1.1.1 | Definition..... | 192 | +| 682 | 9.1.1.2 | Service primitives..... | 193 | +| 683 | 9.1.1.3 | Parameter use..... | 193 | +| 684 | 9.1.2 | MAP-DEACTIVATE-TRACE-MODE service..... | 194 | +| 685 | 9.1.2.1 | Definition..... | 194 | +| 686 | 9.1.2.2 | Service primitives..... | 194 | +| 687 | 9.1.2.3 | Parameter use..... | 194 | +| 688 | 9.1.3 | MAP-TRACE-SUBSCRIBER-ACTIVITY service..... | 195 | +| 689 | 9.1.3.1 | Definition..... | 195 | +| 690 | 9.1.3.2 | Service primitives..... | 195 | +| 691 | 9.1.3.3 | Parameter use..... | 195 | +| 692 | 9.2 | Other operation and maintenance services..... | 196 | +| 693 | 9.2.1 | MAP-SEND-IMSI service..... | 196 | +| 694 | 9.2.1.1 | Definition..... | 196 | +| 695 | 9.2.1.2 | Service primitives..... | 196 | +| 696 | 9.2.1.3 | Parameter use..... | 196 | +| 697 | 10 | Call handling services..... | 196 | +| 698 | 10.1 | MAP_SEND_ROUTING_INFORMATION service..... | 196 | +| 699 | 10.1.1 | Definition..... | 196 | +| 700 | 10.1.2 | Service primitives..... | 196 | +| 701 | 10.1.3 | Parameter use..... | 197 | +| 702 | 10.2 | MAP_PROVIDE_ROAMING_NUMBER service..... | 203 | +| 703 | 10.2.1 | Definition..... | 203 | +| 704 | 10.2.2 | Service primitives..... | 203 | +| 705 | 10.2.3 | Parameter use..... | 204 | +| 706 | 10.3 | MAP_RESUME_CALL_HANDLING service..... | 206 | +| 707 | 10.3.1 | Definition..... | 206 | +| 708 | 10.3.2 | Service primitives..... | 206 | +| 709 | 10.3.3 | Parameter use..... | 207 | +| 710 | 10.4 | MAP_PREPARE_GROUP_CALL service..... | 208 | +| 711 | 10.4.1 | Definition..... | 208 | +| 712 | 10.4.2 | Service primitives..... | 208 | +| 713 | 10.4.3 | Parameter definitions and use..... | 209 | +| 714 | 10.5 | MAP_PROCESS_GROUP_CALL_SIGNALLING service..... | 210 | +| 715 | 10.5.1 | Definitions..... | 210 | +| 716 | 10.5.2 | Service primitives..... | 210 | +| 717 | 10.5.3 | Parameter definitions and use..... | 210 | +| 718 | 10.6 | MAP_FORWARD_GROUP_CALL_SIGNALLING service..... | 211 | +| 719 | 10.6.1 | Definitions..... | 211 | +| 720 | 10.6.2 | Service primitives..... | 211 | +| 721 | 10.6.3 | Parameter definitions and use..... | 211 | +| 722 | 10.7 | MAP_SEND_GROUP_CALL_END_SIGNAL service..... | 212 | +| 723 | 10.7.1 | Definitions..... | 212 | +| 724 | 10.7.2 | Service primitives..... | 213 | +| 725 | 10.7.3 | Parameter definitions and use..... | 213 | + +| | | | | +|-----|---------|--------------------------------------------------|-----| +| 726 | 10.7A | MAP_SEND_GROUP_CALL_INFO service..... | 213 | +| 727 | 10.7A.1 | Definitions..... | 213 | +| 728 | 10.7A.2 | Service primitives..... | 213 | +| 729 | 10.7A.3 | Parameter definitions and use..... | 214 | +| 730 | 10.8 | Void..... | 215 | +| 731 | 10.9 | Void..... | 215 | +| 732 | 10.10 | MAP_SET_REPORTING_STATE service..... | 215 | +| 733 | 10.10.1 | Definition..... | 215 | +| 734 | 10.10.2 | Service primitives..... | 215 | +| 735 | 10.10.3 | Parameter use..... | 215 | +| 736 | 10.11 | MAP_STATUS_REPORT service..... | 216 | +| 737 | 10.11.1 | Definition..... | 216 | +| 738 | 10.11.2 | Service primitives..... | 216 | +| 739 | 10.11.3 | Parameter use..... | 216 | +| 740 | 10.12 | MAP_REMOTE_USER_FREE service..... | 217 | +| 741 | 10.12.1 | Definition..... | 217 | +| 742 | 10.12.2 | Service primitives..... | 217 | +| 743 | 10.12.3 | Parameter use..... | 217 | +| 744 | 10.13 | MAP_IST_ALERT service..... | 218 | +| 745 | 10.13.1 | Definition..... | 218 | +| 746 | 10.13.2 | Service primitives..... | 218 | +| 747 | 10.13.3 | Parameter use..... | 218 | +| 748 | 10.14 | MAP_IST_COMMAND service..... | 219 | +| 749 | 10.14.1 | Definition..... | 219 | +| 750 | 10.14.2 | Service primitives..... | 219 | +| 751 | 10.14.3 | Parameter use..... | 219 | +| 752 | 10.15 | MAP_RELEASE_RESOURCES service..... | 220 | +| 753 | 10.15.1 | Definition..... | 220 | +| 754 | 10.15.2 | Service primitives..... | 220 | +| 755 | 10.15.3 | Parameter use..... | 220 | +| 756 | 11 | Supplementary services related services..... | 220 | +| 757 | 11.1 | MAP_REGISTER_SS service..... | 220 | +| 758 | 11.1.1 | Definition..... | 220 | +| 759 | 11.1.2 | Service primitives..... | 220 | +| 760 | 11.1.3 | Parameter use..... | 221 | +| 761 | 11.2 | MAP_ERASE_SS service..... | 222 | +| 762 | 11.2.1 | Definition..... | 222 | +| 763 | 11.2.2 | Service primitives..... | 222 | +| 764 | 11.2.3 | Parameter use..... | 222 | +| 765 | 11.3 | MAP_ACTIVATE_SS service..... | 223 | +| 766 | 11.3.1 | Definition..... | 223 | +| 767 | 11.3.2 | Service primitives..... | 223 | +| 768 | 11.3.3 | Parameter use..... | 223 | +| 769 | 11.4 | MAP_DEACTIVATE_SS service..... | 224 | +| 770 | 11.4.1 | Definitions..... | 224 | +| 771 | 11.4.2 | Service primitives..... | 225 | +| 772 | 11.4.3 | Parameter use..... | 225 | +| 773 | 11.5 | MAP_INTERROGATE_SS service..... | 226 | +| 774 | 11.5.1 | Definitions..... | 226 | +| 775 | 11.5.2 | Service primitives..... | 226 | +| 776 | 11.5.3 | Parameter use..... | 226 | +| 777 | 11.6 | Void..... | 228 | +| 778 | 11.7 | MAP_REGISTER_PASSWORD service..... | 228 | +| 779 | 11.7.1 | Definitions..... | 228 | +| 780 | 11.7.2 | Service primitives..... | 228 | +| 781 | 11.7.3 | Parameter use..... | 228 | +| 782 | 11.8 | MAP_GET_PASSWORD service..... | 229 | +| 783 | 11.8.1 | Definitions..... | 229 | +| 784 | 11.8.2 | Service primitives..... | 229 | +| 785 | 11.8.3 | Parameter use..... | 229 | +| 786 | 11.9 | MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service..... | 229 | + +| | | | | +|-----|---------|------------------------------------------------|-----| +| 787 | 11.9.1 | Definitions..... | 230 | +| 788 | 11.9.2 | Service primitives..... | 230 | +| 789 | 11.9.3 | Parameter use..... | 230 | +| 790 | 11.10 | MAP_UNSTRUCTURED_SS_REQUEST service..... | 231 | +| 791 | 11.10.1 | Definitions..... | 231 | +| 792 | 11.10.2 | Service primitives..... | 231 | +| 793 | 11.10.3 | Parameter use..... | 231 | +| 794 | 11.11 | MAP_UNSTRUCTURED_SS_NOTIFY service..... | 232 | +| 795 | 11.11.1 | Definitions..... | 232 | +| 796 | 11.11.2 | Service primitives..... | 232 | +| 797 | 11.11.3 | Parameter use..... | 232 | +| 798 | 11.12 | MAP_SS_INVOCATION_NOTIFY..... | 233 | +| 799 | 11.12.1 | Definition..... | 233 | +| 800 | 11.12.2 | Service primitives..... | 233 | +| 801 | 11.12.3 | Parameter use..... | 233 | +| 802 | 11.13 | MAP_REGISTER_CC_ENTRY service..... | 234 | +| 803 | 11.13.1 | Definition..... | 234 | +| 804 | 11.13.2 | Service primitives..... | 234 | +| 805 | 11.13.3 | Parameter use..... | 234 | +| 806 | 11.14 | MAP_ERASE_CC_ENTRY service..... | 235 | +| 807 | 11.14.1 | Definition..... | 235 | +| 808 | 11.14.2 | Service primitives..... | 235 | +| 809 | 11.14.3 | Parameter use..... | 235 | +| 810 | 12 | Short message service management services..... | 236 | +| 811 | 12.1 | MAP-SEND-ROUTING-INFO-FOR-SM service..... | 236 | +| 812 | 12.1.1 | Definition..... | 236 | +| 813 | 12.1.2 | Service primitives..... | 236 | +| 814 | 12.1.3 | Parameter use..... | 237 | +| 815 | 12.1.4 | Identities of MT-SMS Target Nodes..... | 240 | +| 816 | 12.2 | MAP-MO-FORWARD-SHORT-MESSAGE service..... | 241 | +| 817 | 12.2.1 | Definition..... | 241 | +| 818 | 12.2.2 | Service primitives..... | 241 | +| 819 | 12.2.3 | Parameter use..... | 241 | +| 820 | 12.3 | MAP-REPORT-SM-DELIVERY-STATUS service..... | 242 | +| 821 | 12.3.1 | Definition..... | 242 | +| 822 | 12.3.2 | Service primitives..... | 242 | +| 823 | 12.3.3 | Parameter use..... | 243 | +| 824 | 12.4 | MAP-READY-FOR-SM service..... | 245 | +| 825 | 12.4.1 | Definition..... | 245 | +| 826 | 12.4.2 | Service primitives..... | 245 | +| 827 | 12.4.3 | Parameter use..... | 246 | +| 828 | 12.5 | MAP-ALERT-SERVICE-CENTRE service..... | 246 | +| 829 | 12.5.1 | Definition..... | 246 | +| 830 | 12.5.2 | Service primitives..... | 247 | +| 831 | 12.5.3 | Parameter use..... | 247 | +| 832 | 12.6 | MAP-INFORM-SERVICE-CENTRE service..... | 249 | +| 833 | 12.6.1 | Definition..... | 249 | +| 834 | 12.6.2 | Service primitives..... | 250 | +| 835 | 12.6.3 | Parameter use..... | 250 | +| 836 | 12.7 | MAP-SEND-INFO-FOR-MT-SMS service..... | 250 | +| 837 | 12.7.1 | Definition..... | 250 | +| 838 | 12.7.2 | Service primitives..... | 251 | +| 839 | 12.7.3 | Parameter use..... | 251 | +| 840 | 12.8 | MAP-SEND-INFO-FOR-MO-SMS service..... | 251 | +| 841 | 12.8.1 | Definition..... | 252 | +| 842 | 12.8.2 | Service primitives..... | 252 | +| 843 | 12.8.3 | Parameter use..... | 252 | +| 844 | 12.9 | MAP-MT-FORWARD-SHORT-MESSAGE service..... | 252 | +| 845 | 12.9.1 | Definition..... | 252 | +| 846 | 12.9.2 | Service primitives..... | 252 | +| 847 | 12.9.3 | Parameter use..... | 253 | + +| | | | | +|-----|---------|--------------------------------------------------------|-----| +| 848 | 12.10 | MAP-MT-FORWARD-SM-FOR-VGCS service..... | 255 | +| 849 | 12.10.1 | Definition..... | 255 | +| 850 | 12.10.2 | Service primitives..... | 255 | +| 851 | 12.10.3 | Parameter use..... | 255 | +| 852 | 13 | Network-Requested PDP Context Activation services..... | 256 | +| 853 | 13.1 | MAP_SEND_ROUTING_INFO_FOR_GPRS service..... | 256 | +| 854 | 13.1.1 | Definition..... | 256 | +| 855 | 13.1.2 | Service primitives..... | 256 | +| 856 | 13.1.3 | Parameter definition and use..... | 256 | +| 857 | 13.2 | MAP_FAILURE_REPORT service..... | 257 | +| 858 | 13.2.1 | Definition..... | 257 | +| 859 | 13.2.2 | Service primitives..... | 257 | +| 860 | 13.2.3 | Parameter definition and use..... | 257 | +| 861 | 13.3 | MAP_NOTE_MS_PRESENT_FOR_GPRS service..... | 258 | +| 862 | 13.3.1 | Definition..... | 258 | +| 863 | 13.3.2 | Service primitives..... | 258 | +| 864 | 13.3.3 | Parameter definition and use..... | 258 | +| 865 | 13A | Location Service Management Services..... | 259 | +| 866 | 13A.1 | MAP-SEND-ROUTING-INFO-FOR-LCS Service..... | 259 | +| 867 | 13A.1.1 | Definition..... | 259 | +| 868 | 13A.1.2 | Service Primitives..... | 259 | +| 869 | 13A.1.3 | Parameter Use..... | 260 | +| 870 | 13A.2 | MAP-PROVIDE-SUBSCRIBER-LOCATION Service..... | 261 | +| 871 | 13A.2.1 | Definition..... | 261 | +| 872 | 13A.2.2 | Service Primitives..... | 261 | +| 873 | 13A.2.3 | Parameter Definition and Use..... | 262 | +| 874 | 13A.3 | MAP-SUBSCRIBER-LOCATION-REPORT Service..... | 265 | +| 875 | 13A.3.1 | Definition..... | 265 | +| 876 | 13A.3.2 | Service Primitives..... | 265 | +| 877 | 13A.3.3 | Parameter Definition and Use..... | 266 | +| 878 | 13A.4 | Void..... | 269 | +| 879 | 13A.4.1 | Void..... | 269 | +| 880 | 13A.4.2 | Void..... | 269 | +| 881 | 13A.4.3 | Void..... | 269 | +| 882 | 13A.5 | Void..... | 269 | +| 883 | 13A.5.1 | Void..... | 269 | +| 884 | 13A.5.2 | Void..... | 269 | +| 885 | 13A.5.3 | Void..... | 269 | +| 886 | 13A.6 | Void..... | 269 | +| 887 | 13A.6.1 | Void..... | 270 | +| 888 | 13A.6.2 | Void..... | 270 | +| 889 | 13A.6.3 | Void..... | 270 | +| 890 | 13A.7 | Void..... | 270 | +| 891 | 13A.7.1 | Void..... | 270 | +| 892 | 13A.7.2 | Void..... | 270 | +| 893 | 13A.7.3 | Void..... | 270 | +| 894 | 13A.8 | Void..... | 270 | +| 895 | 13A.8.1 | Void..... | 270 | +| 896 | 13A.8.2 | Void..... | 270 | +| 897 | 13A.8.3 | Void..... | 270 | +| 898 | 13A.9 | Void..... | 270 | +| 899 | 13A.9.1 | Void..... | 270 | +| 900 | 13A.9.2 | Void..... | 270 | +| 901 | 13A.9.3 | Void..... | 270 | +| 902 | 14 | General..... | 270 | +| 903 | 14.1 | Overview..... | 270 | +| 904 | 14.2 | Underlying services..... | 270 | +| 905 | 14.3 | Model..... | 271 | +| 906 | 14.4 | Conventions..... | 271 | + +| | | | | +|-----|------------|------------------------------------------------------------------|-----| +| 907 | 15 | Elements of procedure..... | 271 | +| 908 | 15.1 | Handling of unknown operations..... | 271 | +| 909 | 15.2 | Dialogue establishment..... | 272 | +| 910 | 15.2.1 | Behaviour at the initiating side..... | 272 | +| 911 | 15.2.2 | Behaviour at the responding side..... | 273 | +| 912 | 15.3 | Dialogue continuation..... | 274 | +| 913 | 15.4 | Load control..... | 274 | +| 914 | 15.5 | Procedures for MAP specific services..... | 274 | +| 915 | 15.5.1 | Service invocation..... | 274 | +| 916 | 15.5.2 | Void..... | 275 | +| 917 | 15.5.3 | Service invocation receipt..... | 275 | +| 918 | 15.5.4 | Void..... | 275 | +| 919 | 15.5.5 | Handling of components received from TC..... | 275 | +| 920 | 15.6 | SDL descriptions..... | 275 | +| 921 | 16 | Mapping on to TC services..... | 308 | +| 922 | 16.1 | Dialogue control..... | 308 | +| 923 | 16.1.1 | Directly mapped parameters..... | 308 | +| 924 | 16.1.2 | Use of other parameters of dialogue handling primitives..... | 308 | +| 925 | 16.1.2.1 | Dialogue Id..... | 308 | +| 926 | 16.1.2.2 | Application-context-name..... | 308 | +| 927 | 16.1.2.3 | User information..... | 308 | +| 928 | 16.1.2.4 | Component present..... | 308 | +| 929 | 16.1.2.5 | Termination..... | 308 | +| 930 | 16.1.2.6 | P-Abort-Cause..... | 308 | +| 931 | 16.1.2.7 | Quality of service..... | 308 | +| 932 | 16.2 | Service specific procedures..... | 309 | +| 933 | 16.2.1 | Directly mapped parameters..... | 309 | +| 934 | 16.2.2 | Use of other parameters of component handling primitives..... | 309 | +| 935 | 16.2.2.1 | Dialogue Id..... | 309 | +| 936 | 16.2.2.2 | Class..... | 309 | +| 937 | 16.2.2.3 | Linked Id..... | 309 | +| 938 | 16.2.2.4 | Operation..... | 310 | +| 939 | 16.2.2.5 | Error..... | 311 | +| 940 | 16.2.2.6 | Parameters..... | 311 | +| 941 | 16.2.2.7 | Time out..... | 311 | +| 942 | 16.2.2.8 | Last component..... | 311 | +| 943 | 16.2.2.9 | Problem code..... | 311 | +| 944 | 16.2.2.9.1 | Mapping to MAP User Error..... | 311 | +| 945 | 16.2.2.9.2 | Mapping to MAP Provider Error parameter..... | 312 | +| 946 | 16.2.2.9.3 | Mapping to diagnostic parameter..... | 312 | +| 947 | 17 | Abstract syntax of the MAP protocol..... | 313 | +| 948 | 17.1 | General..... | 313 | +| 949 | 17.1.1 | Encoding rules..... | 313 | +| 950 | 17.1.2 | Use of TC..... | 313 | +| 951 | 17.1.2.1 | Use of Global Operation and Error codes defined outside MAP..... | 314 | +| 952 | 17.1.3 | Use of information elements defined outside MAP..... | 314 | +| 953 | 17.1.4 | Compatibility considerations..... | 314 | +| 954 | 17.1.5 | Structure of the Abstract Syntax of MAP..... | 315 | +| 955 | 17.1.6 | Application Contexts..... | 317 | +| 956 | 17.2 | Operation packages..... | 318 | +| 957 | 17.2.1 | General aspects..... | 318 | +| 958 | 17.2.2 | Packages specifications..... | 319 | +| 959 | 17.2.2.1 | Location updating..... | 319 | +| 960 | 17.2.2.2 | Location cancellation..... | 319 | +| 961 | 17.2.2.3 | Roaming number enquiry..... | 320 | +| 962 | 17.2.2.4 | Information retrieval..... | 320 | +| 963 | 17.2.2.5 | Inter-VLR information retrieval..... | 320 | +| 964 | 17.2.2.6 | IMSI retrieval..... | 320 | +| 965 | 17.2.2.7 | Call control transfer..... | 321 | +| 966 | 17.2.2.8 | Void..... | 321 | + +| | | | | +|------|------------|----------------------------------------------------|-----| +| 967 | 17.2.2.9 | Void..... | 321 | +| 968 | 17.2.2.10 | Interrogation..... | 321 | +| 969 | 17.2.2.11 | Void..... | 321 | +| 970 | 17.2.2.12 | Handover Control..... | 321 | +| 971 | 17.2.2.13 | Subscriber Data management stand alone..... | 322 | +| 972 | 17.2.2.14 | Equipment management..... | 322 | +| 973 | 17.2.2.15 | Subscriber data management..... | 322 | +| 974 | 17.2.2.16 | Location register restart..... | 322 | +| 975 | 17.2.2.17 | Tracing stand-alone..... | 323 | +| 976 | 17.2.2.18 | Functional SS handling..... | 323 | +| 977 | 17.2.2.19 | Tracing..... | 323 | +| 978 | 17.2.2.20 | Binding..... | 323 | +| 979 | 17.2.2.21 | Unstructured SS handling..... | 324 | +| 980 | 17.2.2.22 | MO Short message relay services..... | 324 | +| 981 | 17.2.2.23 | Short message gateway services..... | 324 | +| 982 | 17.2.2.24 | MT Short message relay services..... | 325 | +| 983 | 17.2.2.25 | Void..... | 325 | +| 984 | 17.2.2.26 | Message waiting data management..... | 325 | +| 985 | 17.2.2.27 | Alerting..... | 325 | +| 986 | 17.2.2.28 | Data restoration..... | 325 | +| 987 | 17.2.2.29 | Purging..... | 326 | +| 988 | 17.2.2.30 | Subscriber information enquiry..... | 326 | +| 989 | 17.2.2.31 | Any time information enquiry..... | 326 | +| 990 | 17.2.2.32 | Group Call Control..... | 326 | +| 991 | 17.2.2.32A | Group Call Info Retrieval..... | 326 | +| 992 | 17.2.2.33 | Void..... | 327 | +| 993 | 17.2.2.34 | Void..... | 327 | +| 994 | 17.2.2.35 | Gprs location updating..... | 327 | +| 995 | 17.2.2.36 | Gprs Interrogation..... | 327 | +| 996 | 17.2.2.37 | Failure reporting..... | 327 | +| 997 | 17.2.2.38 | GPRS notifying..... | 327 | +| 998 | 17.2.2.39 | Supplementary Service invocation notification..... | 328 | +| 999 | 17.2.2.40 | Set Reporting State..... | 328 | +| 1000 | 17.2.2.41 | Status Report..... | 328 | +| 1001 | 17.2.2.42 | Remote User Free..... | 328 | +| 1002 | 17.2.2.43 | Call Completion..... | 328 | +| 1003 | 17.2.2.44 | Location service gateway services..... | 328 | +| 1004 | 17.2.2.45 | Location service enquiry..... | 329 | +| 1005 | 17.2.2.45A | Location service reporting..... | 329 | +| 1006 | 17.2.2.46 | Void..... | 329 | +| 1007 | 17.2.2.47 | Void..... | 329 | +| 1008 | 17.2.2.48 | Void..... | 329 | +| 1009 | 17.2.2.49 | IST Alerting..... | 329 | +| 1010 | 17.2.2.50 | Service Termination..... | 329 | +| 1011 | 17.2.2.51 | Mobility Management event notification..... | 330 | +| 1012 | 17.2.2.53 | Subscriber Data modification notification..... | 330 | +| 1013 | 17.2.2.54 | Authentication Failure Report..... | 330 | +| 1014 | 17.2.2.55 | Resource Management..... | 330 | +| 1015 | 17.2.2.56 | MT Short message relay VGCS services..... | 331 | +| 1016 | 17.2.2.57 | Vcsg location updating..... | 331 | +| 1017 | 17.2.2.58 | Vcsg location cancellation..... | 331 | +| 1018 | 17.3 | Application contexts..... | 331 | +| 1019 | 17.3.1 | General aspects..... | 331 | +| 1020 | 17.3.2 | Application context definitions..... | 332 | +| 1021 | 17.3.2.1 | Void..... | 332 | +| 1022 | 17.3.2.2 | Location Updating..... | 332 | +| 1023 | 17.3.2.3 | Location Cancellation..... | 332 | +| 1024 | 17.3.2.4 | Roaming number enquiry..... | 333 | +| 1025 | 17.3.2.5 | Void..... | 333 | +| 1026 | 17.3.2.6 | Location Information Retrieval..... | 333 | +| 1027 | 17.3.2.7 | Call control transfer..... | 333 | + +| | | | | +|------|------------|----------------------------------------------------|-----| +| 1028 | 17.3.2.8 | Void..... | 334 | +| 1029 | 17.3.2.9 | Void..... | 334 | +| 1030 | 17.3.2.10 | Void..... | 334 | +| 1031 | 17.3.2.11 | Location registers restart..... | 334 | +| 1032 | 17.3.2.12 | Handover control..... | 334 | +| 1033 | 17.3.2.13 | IMSI Retrieval..... | 334 | +| 1034 | 17.3.2.14 | Equipment Management..... | 335 | +| 1035 | 17.3.2.15 | Information retrieval..... | 335 | +| 1036 | 17.3.2.16 | Inter-VLR information retrieval..... | 335 | +| 1037 | 17.3.2.17 | Stand Alone Subscriber Data Management..... | 336 | +| 1038 | 17.3.2.18 | Tracing..... | 336 | +| 1039 | 17.3.2.19 | Network functional SS handling..... | 336 | +| 1040 | 17.3.2.20 | Network unstructured SS handling..... | 337 | +| 1041 | 17.3.2.21 | Short Message Gateway..... | 337 | +| 1042 | 17.3.2.22 | Mobile originating Short Message Relay..... | 337 | +| 1043 | 17.3.2.23 | Void..... | 338 | +| 1044 | 17.3.2.24 | Short message alert..... | 338 | +| 1045 | 17.3.2.25 | Short message waiting data management..... | 338 | +| 1046 | 17.3.2.26 | Mobile terminating Short Message Relay..... | 338 | +| 1047 | 17.3.2.27 | MS purging..... | 339 | +| 1048 | 17.3.2.28 | Subscriber information enquiry..... | 339 | +| 1049 | 17.3.2.29 | Any time information enquiry..... | 339 | +| 1050 | 17.3.2.30 | Group Call Control..... | 339 | +| 1051 | 17.3.2.30A | Group Call Info Retrieval..... | 339 | +| 1052 | 17.3.2.31 | Void..... | 340 | +| 1053 | 17.3.2.32 | Gprs Location Updating..... | 340 | +| 1054 | 17.3.2.33 | Gprs Location Information Retrieval..... | 340 | +| 1055 | 17.3.2.34 | Failure Reporting..... | 340 | +| 1056 | 17.3.2.35 | GPRS Notifying..... | 340 | +| 1057 | 17.3.2.36 | Supplementary Service invocation notification..... | 341 | +| 1058 | 17.3.2.37 | Reporting..... | 341 | +| 1059 | 17.3.2.38 | Call Completion..... | 341 | +| 1060 | 17.3.2.39 | Location Service Gateway..... | 342 | +| 1061 | 17.3.2.40 | Location Service Enquiry..... | 342 | +| 1062 | 17.3.2.41 | Void..... | 342 | +| 1063 | 17.3.2.42 | Void..... | 342 | +| 1064 | 17.3.2.43 | Void..... | 342 | +| 1065 | 17.3.2.44 | IST Alerting..... | 342 | +| 1066 | 17.3.2.45 | Service Termination..... | 342 | +| 1067 | 17.3.2.46 | Mobility Management event notification..... | 343 | +| 1068 | 17.3.2.48 | Subscriber Data modification notification..... | 343 | +| 1069 | 17.3.2.49 | Authentication Failure Report..... | 343 | +| 1070 | 17.3.2.50 | Resource Management..... | 343 | +| 1071 | 17.3.2.51 | Mobile terminating Short Message Relay VGCS..... | 344 | +| 1072 | 17.3.2.52 | Vcsg Location Updating..... | 344 | +| 1073 | 17.3.2.53 | Vcsg Location Cancellation..... | 344 | +| 1074 | 17.3.3 | ASN.1 Module for application-context-names..... | 344 | +| 1075 | 17.4 | MAP Dialogue Information..... | 347 | +| 1076 | 17.5 | MAP operation and error codes..... | 349 | +| 1077 | 17.6 | MAP operations and errors..... | 351 | +| 1078 | 17.6.1 | Mobile Service Operations..... | 351 | +| 1079 | 17.6.2 | Operation and Maintenance Operations..... | 358 | +| 1080 | 17.6.3 | Call Handling Operations..... | 359 | +| 1081 | 17.6.4 | Supplementary service operations..... | 362 | +| 1082 | 17.6.5 | Short message service operations..... | 366 | +| 1083 | 17.6.6 | Errors..... | 369 | +| 1084 | 17.6.7 | Group Call operations..... | 375 | +| 1085 | 17.6.8 | Location service operations..... | 377 | +| 1086 | 17.6.9 | Void..... | 378 | +| 1087 | 17.7 | MAP constants and data types..... | 378 | +| 1088 | 17.7.1 | Mobile Service data types..... | 378 | + +| | | | | +|------|-----------|-----------------------------------------------------|-----| +| 1089 | 17.7.2 | Operation and maintenance data types..... | 427 | +| 1090 | 17.7.3 | Call handling data types..... | 434 | +| 1091 | 17.7.4 | Supplementary service data types..... | 440 | +| 1092 | 17.7.5 | Supplementary service codes..... | 444 | +| 1093 | 17.7.6 | Short message data types..... | 447 | +| 1094 | 17.7.7 | Error data types..... | 453 | +| 1095 | 17.7.8 | Common data types..... | 459 | +| 1096 | 17.7.9 | Teleservice Codes..... | 468 | +| 1097 | 17.7.10 | Bearer Service Codes..... | 469 | +| 1098 | 17.7.11 | Extension data types..... | 471 | +| 1099 | 17.7.12 | Group Call data types..... | 472 | +| 1100 | 17.7.13 | Location service data types..... | 475 | +| 1101 | 17.7.14 | Void..... | 485 | +| 1102 | 18 | General on MAP user procedures..... | 486 | +| 1103 | 18.1 | Introduction..... | 486 | +| 1104 | 18.2 | Common aspects of user procedure descriptions..... | 486 | +| 1105 | 18.2.1 | General conventions..... | 486 | +| 1106 | 18.2.2 | Naming conventions..... | 486 | +| 1107 | 18.2.3 | Convention on primitives parameters..... | 487 | +| 1108 | 18.2.3.1 | Open service..... | 487 | +| 1109 | 18.2.3.2 | Close service..... | 488 | +| 1110 | 18.2.4 | Version handling at dialogue establishment..... | 488 | +| 1111 | 18.2.4.1 | Behaviour at the initiating side..... | 488 | +| 1112 | 18.2.4.2 | Behaviour at the responding side..... | 488 | +| 1113 | 18.2.5 | Abort Handling..... | 488 | +| 1114 | 18.2.6 | SDL conventions..... | 488 | +| 1115 | 18.3 | Interaction between MAP Provider and MAP Users..... | 489 | +| 1116 | 19 | Mobility procedures..... | 490 | +| 1117 | 19.1 | Location management Procedures..... | 490 | +| 1118 | 19.1.1 | Location updating..... | 491 | +| 1119 | 19.1.1.1 | General..... | 491 | +| 1120 | 19.1.1.2 | Procedures in the VLR..... | 496 | +| 1121 | 19.1.1.3 | Procedure in the PVLR..... | 496 | +| 1122 | 19.1.1.4 | Procedure in the SGSN..... | 496 | +| 1123 | 19.1.1.5 | Procedures in the HLR..... | 497 | +| 1124 | 19.1.1A | Location updating for VCSG..... | 517 | +| 1125 | 19.1.1A.1 | General..... | 517 | +| 1126 | 19.1.1A.2 | Procedures in the VLR..... | 517 | +| 1127 | 19.1.1A.3 | Procedures in the SGSN..... | 517 | +| 1128 | 19.1.1A.4 | Procedures in the CSS..... | 517 | +| 1129 | 19.1.2 | Location Cancellation..... | 525 | +| 1130 | 19.1.2.1 | General..... | 525 | +| 1131 | 19.1.2.2 | Procedure in the HLR..... | 525 | +| 1132 | 19.1.2.3 | Procedure in the VLR..... | 526 | +| 1133 | 19.1.2.4 | Procedure in the SGSN..... | 526 | +| 1134 | 19.1.2A | Location Cancellation for VCSG..... | 533 | +| 1135 | 19.1.2A.1 | General..... | 533 | +| 1136 | 19.1.2A.2 | Procedure in the CSS..... | 533 | +| 1137 | 19.1.2A.3 | Procedure in the VLR..... | 533 | +| 1138 | 19.1.2A.4 | Procedure in the SGSN..... | 533 | +| 1139 | 19.1.3 | Void..... | 537 | +| 1140 | 19.1.4 | MS Purging..... | 537 | +| 1141 | 19.1.4.1 | General..... | 538 | +| 1142 | 19.1.4.2 | Procedure in the VLR..... | 538 | +| 1143 | 19.1.4.3 | Procedure in the SGSN..... | 538 | +| 1144 | 19.1.4.4 | Procedure in the HLR..... | 539 | +| 1145 | 19.2 | Handover procedures..... | 544 | +| 1146 | 19.2.1 | General..... | 544 | +| 1147 | 19.2.2 | Procedure in MSC-A..... | 547 | +| 1148 | 19.2.2.1 | Basic handover..... | 547 | + +| | | | | +|------|-----------|-----------------------------------------------------------|-----| +| 1149 | 19.2.2.2 | Handling of access signalling..... | 548 | +| 1150 | 19.2.2.3 | Subsequent handover..... | 548 | +| 1151 | 19.2.3 | Procedure in MSC-B..... | 548 | +| 1152 | 19.2.3.1 | Basic handover..... | 549 | +| 1153 | 19.2.3.2 | Handling of access signalling..... | 549 | +| 1154 | 19.2.3.3 | Subsequent handover..... | 549 | +| 1155 | 19.2.4 | Macro Receive_Error_From_HO_CA..... | 549 | +| 1156 | 19.2.5 | Procedure in VLR-B..... | 549 | +| 1157 | 19.3 | Fault recovery procedures..... | 568 | +| 1158 | 19.3.1 | VLR fault recovery procedures..... | 568 | +| 1159 | 19.3.1.1 | General 568 | | +| 1160 | 19.3.1.2 | Procedure in the VLR..... | 569 | +| 1161 | 19.3.1.3 | Procedure in the HLR..... | 569 | +| 1162 | 19.3.2 | HLR fault recovery procedures..... | 571 | +| 1163 | 19.3.2.1 | General..... | 571 | +| 1164 | 19.3.2.2 | Procedure in the HLR..... | 572 | +| 1165 | 19.3.2.3 | Procedure in the VLR..... | 573 | +| 1166 | 19.3.2.4 | Procedure in the SGSN..... | 573 | +| 1167 | 19.3.3 | CSS fault recovery procedures..... | 579 | +| 1168 | 19.3.3.1 | General..... | 579 | +| 1169 | 19.3.3.2 | Procedure in the CSS..... | 580 | +| 1170 | 19.3.3.3 | Procedure in the VLR..... | 580 | +| 1171 | 19.3.3.4 | Procedure in the SGSN..... | 580 | +| 1172 | 19.4 | Mobility Management event notification procedure..... | 585 | +| 1173 | 19.4.1 | General..... | 585 | +| 1174 | 19.4.2 | Procedure in the VLR or SGSN..... | 586 | +| 1175 | 19.4.3 | Procedure in the gsmSCF..... | 586 | +| 1176 | 19.5 | HLR Insert Subscriber Data macros..... | 589 | +| 1177 | 19.5.1 | Macro Insert_Subs_Data_Framed_HLR..... | 589 | +| 1178 | 19.5.2 | Macro Insert_GPRS_Subs_Data_Framed_HLR..... | 589 | +| 1179 | 19.5A | CSS Insert Subscriber Data macros..... | 592 | +| 1180 | 19.5A.1 | Macro Insert_VCSG_Subs_Data_Framed_CSS..... | 592 | +| 1181 | 20 | Operation and maintenance procedures..... | 594 | +| 1182 | 20.1 | General..... | 594 | +| 1183 | 20.1.1 | Tracing Co-ordinator for the VLR..... | 594 | +| 1184 | 20.1.2 | Tracing Co-ordinator for the SGSN..... | 594 | +| 1185 | 20.1.3 | Subscriber Data Management Co-ordinator for the VLR..... | 594 | +| 1186 | 20.1.4 | Subscriber Data Management Co-ordinator for the SGSN..... | 594 | +| 1187 | 20.2 | Tracing procedures..... | 601 | +| 1188 | 20.2.1 | Subscriber tracing activation procedure..... | 604 | +| 1189 | 20.2.1.1 | Procedures in the HLR..... | 604 | +| 1190 | 20.2.1.2 | Procedure in the VLR..... | 604 | +| 1191 | 20.2.1.3 | Procedure in the SGSN..... | 604 | +| 1192 | 20.2.2 | Subscriber tracing deactivation procedure..... | 604 | +| 1193 | 20.2.2.1 | Procedures in the HLR..... | 604 | +| 1194 | 20.2.2.2 | Procedure in the VLR..... | 605 | +| 1195 | 20.2.2.3 | Procedure in the SGSN..... | 605 | +| 1196 | 20.3 | Subscriber data management procedures for HLR..... | 618 | +| 1197 | 20.3.1 | Subscriber deletion procedure..... | 619 | +| 1198 | 20.3.1.1 | Procedure in the HLR..... | 619 | +| 1199 | 20.3.1.2 | Procedure in the VLR..... | 619 | +| 1200 | 20.3.1.3 | Procedure in the SGSN..... | 620 | +| 1201 | 20.3.2 | Subscriber data modification procedure..... | 620 | +| 1202 | 20.3.2.1 | Procedure in the HLR..... | 620 | +| 1203 | 20.3.2.2 | Procedures in the VLR..... | 621 | +| 1204 | 20.3.2.3 | Procedures in the SGSN..... | 621 | +| 1205 | 20.3A | Subscriber Data Management procedures for CSS..... | 633 | +| 1206 | 20.3A.1 | Subscriber deletion procedure..... | 634 | +| 1207 | 20.3A.1.1 | Procedure in the CSS..... | 634 | +| 1208 | 20.3A.1.2 | Procedure in the VLR..... | 634 | +| 1209 | 20.3A.1.3 | Procedure in the SGSN..... | 634 | + +| | | | | +|------|-----------|-----------------------------------------------------------------------------|-----| +| 1210 | 20.3A.2 | Subscriber data modification procedure..... | 635 | +| 1211 | 20.3A.2.1 | Procedure in the CSS..... | 635 | +| 1212 | 20.3A.2.2 | Procedures in the VLR..... | 635 | +| 1213 | 20.3A.2.3 | Procedures in the SGSN..... | 635 | +| 1214 | 20.4 | Subscriber Identity procedure..... | 647 | +| 1215 | 20.4.1 | Procedure in the VLR..... | 647 | +| 1216 | 20.4.2 | Procedure in the HLR..... | 647 | +| 1217 | 21 | Call handling procedures..... | 650 | +| 1218 | 21.1 | General..... | 650 | +| 1219 | 21.2 | Retrieval of routing information..... | 650 | +| 1220 | 21.2.1 | General..... | 650 | +| 1221 | 21.2.2 | Procedure in the GMSC..... | 654 | +| 1222 | 21.2.9 | Process in the gsmSCF..... | 654 | +| 1223 | 21.2.4 | Procedure in the HLR..... | 654 | +| 1224 | 21.2.5 | Procedure in the VLR to provide a roaming number..... | 655 | +| 1225 | 21.2.6 | Procedure in the VLR to restore subscriber data..... | 655 | +| 1226 | 21.2.7 | Procedure in the VLR to provide subscriber information..... | 655 | +| 1227 | 21.2.8 | Procedure in the old VLR to request a Roaming Number (MTRF)..... | 655 | +| 1228 | 21.3 | Transfer of call handling..... | 665 | +| 1229 | 21.3.1 | General..... | 665 | +| 1230 | 21.3.2 | Process in the VMSC..... | 665 | +| 1231 | 21.3.3 | Process in the GMSC..... | 666 | +| 1232 | 21.4 | Inter MSC Group Call Procedures..... | 669 | +| 1233 | 21.4.1 | General..... | 669 | +| 1234 | 21.4.2 | Process in the Anchor MSC..... | 669 | +| 1235 | 21.4.3 | Process in the Relay MSC..... | 670 | +| 1236 | 21.4A | Inter MSC Group Call Info Retrieval..... | 675 | +| 1237 | 21.4A.1 | General..... | 675 | +| 1238 | 21.4A.2 | Process in the MSC..... | 675 | +| 1239 | 21.5 | Void..... | 678 | +| 1240 | 21.6 | CCBS: monitoring and reporting the status of the subscriber..... | 678 | +| 1241 | 21.6.1 | Reporting co-ordinator process in the VLR..... | 678 | +| 1242 | 21.6.2 | Setting the reporting state – stand-alone..... | 678 | +| 1243 | 21.6.2.1 | Process in the HLR..... | 678 | +| 1244 | 21.6.2.2 | Process in the VLR..... | 678 | +| 1245 | 21.6.3 | Status Reporting..... | 678 | +| 1246 | 21.6.3.1 | Process in the VLR..... | 679 | +| 1247 | 21.6.3.2 | Process in the HLR..... | 680 | +| 1248 | 21.6.4 | CCBS: Remote User Free..... | 680 | +| 1249 | 21.6.4.1 | Process in the HLR..... | 681 | +| 1250 | 21.6.3.2 | Process in the VLR..... | 681 | +| 1251 | 21.7 | Void..... | 694 | +| 1252 | 21.8 | Void..... | 694 | +| 1253 | 21.9 | Immediate Service Termination (IST)..... | 694 | +| 1254 | 21.9.1 | IST Alert..... | 694 | +| 1255 | 21.9.1.1 | Procedure in the MSC..... | 694 | +| 1256 | 21.9.1.2 | Procedure in the HLR..... | 694 | +| 1257 | 21.9.2 | IST Command..... | 694 | +| 1258 | 21.9.2.1 | Procedure in the HLR..... | 695 | +| 1259 | 21.9.2.2 | Procedure in the MSC..... | 695 | +| 1260 | 21.10 | Resource Management..... | 700 | +| 1261 | 21.10.1 | General..... | 700 | +| 1262 | 21.3.2 | Process in the GMSC..... | 700 | +| 1263 | 21.3.3 | Process in the VMSC..... | 700 | +| 1264 | 22 | Supplementary services procedures..... | 703 | +| 1265 | 22.1 | Supplementary service co-ordinator processes..... | 703 | +| 1266 | 22.1.1 | Supplementary service co-ordinator process for the MSC..... | 703 | +| 1267 | 22.1.2 | Void..... | 703 | +| 1268 | 22.1.3 | Functional supplementary service co-ordinator process for the HLR..... | 703 | +| 1269 | 22.1.4 | Call completion supplementary service co-ordinator process for the HLR..... | 703 | + +| | | | | +|------|---------|-----------------------------------------------------------------------|-----| +| 1270 | 22.2 | Registration procedure..... | 708 | +| 1271 | 22.2.1 | General..... | 708 | +| 1272 | 22.2.2 | Procedure in the MSC..... | 709 | +| 1273 | 22.2.3 | Procedure in the VLR..... | 709 | +| 1274 | 22.2.4 | Procedure in the HLR..... | 709 | +| 1275 | 22.3 | Erasure procedure..... | 715 | +| 1276 | 22.3.1 | General..... | 715 | +| 1277 | 22.3.2 | Procedure in the MSC..... | 716 | +| 1278 | 22.3.3 | Procedure in the VLR..... | 716 | +| 1279 | 22.3.4 | Procedure in the HLR..... | 716 | +| 1280 | 22.4 | Activation procedure..... | 716 | +| 1281 | 22.4.1 | General..... | 716 | +| 1282 | 22.4.2 | Procedure in the MSC..... | 717 | +| 1283 | 22.4.3 | Procedure in the VLR..... | 718 | +| 1284 | 22.4.4 | Procedure in the HLR..... | 718 | +| 1285 | 22.5 | Deactivation procedure..... | 724 | +| 1286 | 22.5.1 | General..... | 724 | +| 1287 | 22.5.2 | Procedure in the MSC..... | 725 | +| 1288 | 22.5.3 | Procedures in the VLR..... | 725 | +| 1289 | 22.5.4 | Procedures in the HLR..... | 725 | +| 1290 | 22.6 | Interrogation procedure..... | 725 | +| 1291 | 22.6.1 | General..... | 725 | +| 1292 | 22.6.2 | Procedure in the MSC..... | 726 | +| 1293 | 22.6.3 | Procedures in the VLR..... | 726 | +| 1294 | 22.6.4 | Procedure in the HLR..... | 727 | +| 1295 | 22.7 | Void..... | 731 | +| 1296 | 22.8 | Password registration procedure..... | 732 | +| 1297 | 22.8.1 | General..... | 732 | +| 1298 | 22.8.2 | Procedure in the MSC..... | 734 | +| 1299 | 22.8.3 | Procedure in the VLR..... | 734 | +| 1300 | 22.8.4 | Procedure in the HLR..... | 734 | +| 1301 | 22.9 | Mobile Initiated USSD procedure..... | 737 | +| 1302 | 22.9.1 | General..... | 737 | +| 1303 | 22.9.2 | Procedure in the MSC..... | 737 | +| 1304 | 22.9.3 | Procedure in the VLR..... | 737 | +| 1305 | 22.9.4 | Procedure in the HLR..... | 738 | +| 1306 | 22.9.5 | Procedures in the gsmSCF/secondary HLR..... | 738 | +| 1307 | 22.10 | Network initiated USSD procedure..... | 752 | +| 1308 | 22.10.1 | General..... | 752 | +| 1309 | 22.10.2 | Procedure in the MSC..... | 752 | +| 1310 | 22.10.3 | Procedure in the VLR..... | 752 | +| 1311 | 22.10.4 | Procedure in the HLR..... | 753 | +| 1312 | 22.10.5 | Procedure in the gsmSCF or secondary HLR..... | 753 | +| 1313 | 22.11 | Common macros for clause 22..... | 773 | +| 1314 | 22.11.1 | SS Password handling macros..... | 773 | +| 1315 | 22.11.2 | Void..... | 773 | +| 1316 | 22.12 | Supplementary Service Invocation Notification procedure..... | 777 | +| 1317 | 22.12.1 | General..... | 777 | +| 1318 | 22.12.2 | Procedure in the MSC..... | 777 | +| 1319 | 22.12.3 | Procedure in the gsmSCF..... | 777 | +| 1320 | 22.13 | Activation of a CCBS request..... | 780 | +| 1321 | 22.13.1 | General..... | 780 | +| 1322 | 22.13.2 | Procedure in the VLR..... | 780 | +| 1323 | 22.13.3 | Procedure in the HLR..... | 780 | +| 1324 | 22.14 | Deactivation of a CCBS request..... | 783 | +| 1325 | 22.14.1 | General..... | 783 | +| 1326 | 22.14.2 | Procedure in the VLR..... | 783 | +| 1327 | 22.14.3 | Procedure in the HLR..... | 783 | +| 1328 | 23 | Short message service procedures..... | 786 | +| 1329 | 23.1 | General..... | 786 | +| 1330 | 23.1.1 | Mobile originated short message service Co-ordinator for the MSC..... | 786 | + +| | | | | +|------|----------|-----------------------------------------------------------------------------------|-----| +| 1331 | 23.1.2 | Short message Gateway Co-ordinator for the HLR..... | 786 | +| 1332 | 23.2 | The mobile originated short message transfer procedure..... | 791 | +| 1333 | 23.2.1 | Procedure in the serving MSC..... | 792 | +| 1334 | 23.2.2 | Procedure in the VLR..... | 792 | +| 1335 | 23.2.3 | Procedure in the SGSN..... | 792 | +| 1336 | 23.2.4 | Procedure in the SMS Interworking MSC (SMS-IWMSC)..... | 793 | +| 1337 | 23.3 | The mobile terminated short message transfer procedure..... | 805 | +| 1338 | 23.3.1 | Procedure in the SMS-GMSC..... | 812 | +| 1339 | 23.3.2 | Procedure in the HLR..... | 814 | +| 1340 | 23.3.3 | Procedure in the Serving MSC..... | 814 | +| 1341 | 23.3.4 | Procedure in the VLR..... | 815 | +| 1342 | 23.3.5 | Procedure in the SGSN..... | 815 | +| 1343 | 23.3.6 | Procedure in the SMS Router..... | 816 | +| 1344 | 23.3.7 | Procedure in the IP-SM-GW..... | 817 | +| 1345 | 23.4 | The Short Message Alert procedure..... | 863 | +| 1346 | 23.4.1 | Procedure in the Serving MSC – the MS has memory available..... | 865 | +| 1347 | 23.4.2 | Procedures in the VLR..... | 865 | +| 1348 | 23.4.2.1 | The Mobile Subscriber is present..... | 865 | +| 1349 | 23.4.2.2 | The MS has memory available..... | 865 | +| 1350 | 23.4.3 | Procedures in the SGSN..... | 866 | +| 1351 | 23.4.3.1 | The Mobile Subscriber is present..... | 866 | +| 1352 | 23.4.3.2 | The Mobile Equipment has memory available..... | 866 | +| 1353 | 23.4.4 | Procedure in the HLR..... | 866 | +| 1354 | 23.4.5 | Procedure in the SMS Interworking MSC..... | 866 | +| 1355 | 23.5 | The SM delivery status report procedure..... | 875 | +| 1356 | 23.5.1 | Procedure in the SMS-GMSC..... | 875 | +| 1357 | 23.5.2 | Procedure in the HLR..... | 875 | +| 1358 | 23.5.3 | Procedure in the IP-SM-GW..... | 876 | +| 1359 | 23.6 | The macro Report_SM_Delivery_Stat_HLR..... | 881 | +| 1360 | 23.7 | The mobile terminated short message transfer procedure for VGCS..... | 884 | +| 1361 | 23.7.1 | Procedure in the SMS-GMSC..... | 885 | +| 1362 | 23.7.2 | Procedure in the Anchor MSC..... | 885 | +| 1363 | 24 | GPRS process description..... | 889 | +| 1364 | 24.1 | Procedure for retrieval of routeing information for GPRS..... | 890 | +| 1365 | 24.1.1 | Process in the GGSN..... | 890 | +| 1366 | 24.1.2 | Process in the HLR..... | 890 | +| 1367 | 24.2 | Procedure for reporting failure to establish a network requested PDP context..... | 893 | +| 1368 | 24.2.1 | Process in the GGSN..... | 893 | +| 1369 | 24.2.2 | Process in the HLR..... | 893 | +| 1370 | 24.3 | Procedure for reporting that an MS has become reachable for GPRS..... | 896 | +| 1371 | 24.3.1 | Process in the HLR..... | 896 | +| 1372 | 24.3.2 | Process in the GGSN for Note Ms Present For Gprs..... | 896 | +| 1373 | 24A | CSE interrogation and control of subscriber data..... | 899 | +| 1374 | 24A.1 | General..... | 899 | +| 1375 | 24A.2 | Any Time Subscription Interrogation procedure..... | 901 | +| 1376 | 24A.2.1 | General..... | 901 | +| 1377 | 24A.2.2 | Process in the gsmSCF..... | 901 | +| 1378 | 24A.2.3 | Process in the HLR..... | 901 | +| 1379 | 24A.3 | Any Time Modification procedure..... | 904 | +| 1380 | 24A.3.1 | General..... | 904 | +| 1381 | 24A.3.2 | Process in the gsmSCF..... | 904 | +| 1382 | 24A.3.3 | Process in the HLR..... | 904 | +| 1383 | 24A.4 | Subscriber Data Modification Notification procedure..... | 907 | +| 1384 | 24A.4.1 | General..... | 907 | +| 1385 | 24A.4.2 | Process in the HLR..... | 907 | +| 1386 | 24A.4.3 | Process in the gsmSCF..... | 907 | +| 1387 | 24A.5 | Any Time Interrogation procedure..... | 912 | +| 1388 | 24A.5.1 | General..... | 912 | +| 1389 | 24A.5.2 | Procedures in the gsmSCF..... | 913 | +| 1390 | 24A.5.3 | Procedure in the HLR..... | 913 | + +| | | | | +|------|----------|----------------------------------------------------------------------------|-----| +| 1391 | 24A.5.4 | Procedure in the GMLC..... | 913 | +| 1392 | 24B | Location Services process description..... | 919 | +| 1393 | 24B.1 | Routeing information retrieval procedure for LCS..... | 919 | +| 1394 | 24B.1.1 | General..... | 919 | +| 1395 | 24B.1.2 | Process in the GMLC..... | 919 | +| 1396 | 24B.1.3 | Process in the HLR..... | 919 | +| 1397 | 24B.2 | Provide Subscriber Location procedure..... | 922 | +| 1398 | 24B.2.1 | General..... | 922 | +| 1399 | 24B.2.2 | Process in the GMLC..... | 922 | +| 1400 | 24B.2.3 | Process in the MSC..... | 922 | +| 1401 | 24B.2.4 | Process in the SGSN..... | 922 | +| 1402 | 24B.3 | Subscriber Location Report procedure..... | 926 | +| 1403 | 24B.3.1 | General..... | 926 | +| 1404 | 24B.3.2 | Process in the MSC..... | 926 | +| 1405 | 24B.3.3 | Process in the SGSN..... | 926 | +| 1406 | 24B.3.4 | Process in the GMLC..... | 926 | +| 1407 | 25 | General macro description..... | 930 | +| 1408 | 25.1 | MAP_OPEN handling macros..... | 930 | +| 1409 | 25.1.1 | Macro Receive_Open_Ind..... | 930 | +| 1410 | 25.1.2 | Macro Receive_Open_Cnf..... | 930 | +| 1411 | 25.2 | Macros to check the content of indication and confirmation primitives..... | 935 | +| 1412 | 25.2.1 | Macro Check_Indication..... | 935 | +| 1413 | 25.2.2 | Macro Check_Confirmation..... | 935 | +| 1414 | 25.3 | The page and search macros..... | 938 | +| 1415 | 25.3.1 | Macro PAGE_MSC..... | 938 | +| 1416 | 25.3.2 | Macro Search_For_MS_MSC..... | 938 | +| 1417 | 25.4 | Macros for handling an Access Request..... | 941 | +| 1418 | 25.4.1 | Macro Process_Access_Request_MSC..... | 941 | +| 1419 | 25.4.2 | Macro Process_Access_Request_VLR..... | 941 | +| 1420 | 25.4.3 | Macro Obtain_Identity_VLR..... | 941 | +| 1421 | 25.4.4 | Process Update_Location_Child_VLR..... | 941 | +| 1422 | 25.5 | Authentication macros and processes..... | 951 | +| 1423 | 25.5.1 | Macro Authenticate_MSC..... | 951 | +| 1424 | 25.5.2 | Macro Authenticate_VLR..... | 951 | +| 1425 | 25.5.3 | Macro Obtain_Authent_Params_VLR..... | 951 | +| 1426 | 25.5.4 | Process Obtain_Authentication_Sets_VLR..... | 951 | +| 1427 | 25.5.5 | Process Obtain_Authent_Sets_SGSN..... | 951 | +| 1428 | 25.5.6 | Process Obtain_Authent_Sets_HLR..... | 951 | +| 1429 | 25.5.7 | Authentication Failure Reporting..... | 952 | +| 1430 | 25.5.7.1 | General..... | 952 | +| 1431 | 25.5.7.2 | Process in the VLR..... | 952 | +| 1432 | 25.5.7.3 | Process in the SGSN..... | 952 | +| 1433 | 25.5.7.4 | Process in the HLR..... | 952 | +| 1434 | 25.6 | IMEI Handling Macros..... | 968 | +| 1435 | 25.6.1 | Macro Check_IMEI_MSC..... | 968 | +| 1436 | 25.6.2 | Macro Check_IMEI_VLR..... | 968 | +| 1437 | 25.6.3 | Process Check_IMEI_SGSN..... | 968 | +| 1438 | 25.6.4 | Process Check_IMEI_EIR..... | 968 | +| 1439 | 25.6.5 | Macro Obtain_IMEI_MSC..... | 968 | +| 1440 | 25.6.6 | Macro Obtain_IMEI_VLR..... | 968 | +| 1441 | 25.7 | Insert Subscriber Data macros and processes..... | 977 | +| 1442 | 25.7.1 | Macro Insert_Subs_Data_VLR..... | 977 | +| 1443 | 25.7.2 | Macro Insert_Subs_Data_SGSN..... | 977 | +| 1444 | 25.7.3 | Process Insert_Subs_Data_Stand_Alone_HLR..... | 977 | +| 1445 | 25.7.4 | Process Insert_GPRS_Subs_Data_Stand_Alone_HLR..... | 977 | +| 1446 | 25.7.5 | Macro Wait_for_Insert_Subs_Data_Cnf..... | 978 | +| 1447 | 25.7.6 | Macro Wait_for_Insert_GPRS_Subs_Data_Cnf..... | 978 | +| 1448 | 25.7.7 | Process Send_Insert_Subs_Data_HLR..... | 978 | +| 1449 | 25.7.8 | Process Insert_VCSG_Subs_Data_Stand_Alone_CSS..... | 978 | +| 1450 | 25.7.9 | Macro Wait_for_Insert_VCSG_Subs_Data_Cnf..... | 978 | + +| | | | | +|------|---------|---------------------------------------------------------------------------------------------|-------------| +| 1451 | 25.7.10 | Process Send_Insert_VCSG_Subs_Data_CSS..... | 978 | +| 1452 | 25.8 | Request IMSI Macros..... | 992 | +| 1453 | 25.8.1 | Macro Obtain_IMSI_MSC..... | 992 | +| 1454 | 25.8.2 | Macro Obtain_IMSI_VLR..... | 992 | +| 1455 | 25.9 | Tracing macros..... | 995 | +| 1456 | 25.9.1 | Macro Trace_Subscriber_Activity_MSC..... | 995 | +| 1457 | 25.9.2 | Macro Trace_Subscriber_Activity_VLR..... | 995 | +| 1458 | 25.9.3 | Macro Trace_Subscriber_Activity_SGSN..... | 995 | +| 1459 | 25.9.4 | Macro Activate_Tracing_VLR..... | 995 | +| 1460 | 25.9.5 | Macro Activate_Tracing_SGSN..... | 995 | +| 1461 | 25.9.6 | Macro Control_Tracing_With_VLR_HLR..... | 995 | +| 1462 | 25.9.7 | Macro Control_Tracing_With_SGSN_HLR..... | 995 | +| 1463 | 25.10 | Short Message Alert procedures..... | 1003 | +| 1464 | 25.10.1 | Process Subscriber_Present_VLR..... | 1003 | +| 1465 | 25.10.2 | Process SubscriberPresent_SGSN..... | 1003 | +| 1466 | 25.10.3 | Macro Alert_Service_Centre_HLR..... | 1003 | +| 1467 | 25.10.4 | Process Alert_SC_HLR..... | 1003 | +| 1468 | | Annex A (informative): ASN.1 Cross-reference listing and fully expanded sources..... | 1007 | +| 1469 | | Annex B (informative): Void..... | 1008 | +| 1470 | | Annex C (informative): Message Segmentation Mechanisms..... | 1009 | +| 1471 | C.1 | SCCP segmentation..... | 1009 | +| 1472 | C.2 | TCAP segmentation..... | 1009 | +| 1473 | C.2.1 | Empty Begin..... | 1009 | +| 1474 | C.2.2 | Empty Continue..... | 1009 | +| 1475 | C.2.3 | TC-Result-NL..... | 1009 | +| 1476 | C.3 | MAP Segmentation..... | 1010 | +| 1477 | C.3.1 | Invoke without explicit indication..... | 1010 | +| 1478 | C.3.2 | Invoke with explicit indication..... | 1010 | +| 1479 | C.3.3 | Result..... | 1010 | +| 1480 | | Annex D (informative): Void..... | 1014 | +| 1481 | | Annex E (informative): Change History..... | 1015 | + +--- + +## 1483 Foreword + +1484 This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +1485 The contents of the present document are subject to continuing work within the TSG and may change following formal +1486 TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an +1487 identifying change of release date and an increase in version number as follows: + +1488 Version x.y.z + +1489 where: + +1490 x the first digit: + +1491 1 presented to TSG for information; + +1492 2 presented to TSG for approval; + +1493 3 or greater indicates TSG approved document under change control. + +1494 y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, +1495 updates, etc. + +1496 z the third digit is incremented when editorial only changes have been incorporated in the document. + +1497 In the present document, modal verbs have the following meanings: + +1498 **shall** indicates a mandatory requirement to do something + +1499 **shall not** indicates an interdiction (prohibition) to do something + +1500 The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in +1501 Technical Reports. + +1502 The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided +1503 insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, +1504 non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a +1505 referenced document. + +1506 **should** indicates a recommendation to do something + +1507 **should not** indicates a recommendation not to do something + +1508 **may** indicates permission to do something + +1509 **need not** indicates permission not to do something + +1510 The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions +1511 "might not" or "shall not" are used instead, depending upon the meaning intended. + +1512 **can** indicates that something is possible + +1513 **cannot** indicates that something is impossible + +1514 The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +1515 **will** indicates that something is certain or expected to happen as a result of action taken by an agency +1516 the behaviour of which is outside the scope of the present document + +1517 **will not** indicates that something is certain or expected not to happen as a result of action taken by an +1518 agency the behaviour of which is outside the scope of the present document + +1519 **might** indicates a likelihood that something will happen as a result of action taken by some agency the +1520 behaviour of which is outside the scope of the present document + +1521 **might not** indicates a likelihood that something will not happen as a result of action taken by some agency +1522 the behaviour of which is outside the scope of the present document + +1523 In addition: + +1524 **is** (or any other verb in the indicative mood) indicates a statement of fact + +1525 **is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +1526 The constructions "is" and "is not" do not indicate requirements. + +--- + +## 1527 1 Scope + +1528 It is necessary to transfer between entities of a Public Land Mobile Network (PLMN) information specific to the PLMN +1529 in order to deal with the specific behaviour of roaming Mobile Stations (MS)s. The Signalling System No. 7 specified +1530 by CCITT is used to transfer this information. + +1531 The present document describes the requirements for the signalling system and the procedures needed at the application +1532 level in order to fulfil these signalling needs. + +1533 Clauses 1 to 6 are related to general aspects such as terminology, mobile network configuration and other protocols +1534 required by MAP. + +1535 MAP consists of a set of MAP services that are provided to MAP service-users by a MAP service-provider. + +![Diagram illustrating the modelling principles of MAP. It shows two 'MAP service-user' boxes at the top, each connected by a vertical line to a central 'Service Interface' box. Both 'Service Interface' boxes are then connected by vertical lines to a single, larger 'MAP Service-provider' box at the bottom. The connections are marked with small crosses.](84e5b251aa38db522f76f5cc3afcb853_img.jpg) + +``` +graph TD; subgraph TopRow [ ]; direction LR; S1[MAP service-user] --- SI1[Service Interface]; S2[MAP service-user] --- SI2[Service Interface]; end; SI1 --- SP[MAP Service-provider]; SI2 --- SP[MAP Service-provider]; +``` + +Diagram illustrating the modelling principles of MAP. It shows two 'MAP service-user' boxes at the top, each connected by a vertical line to a central 'Service Interface' box. Both 'Service Interface' boxes are then connected by vertical lines to a single, larger 'MAP Service-provider' box at the bottom. The connections are marked with small crosses. + +1536 + +1537 + +**Figure 1.1/1: Modelling principles** + +1538 Clauses 7 to 13A of the present document describe the MAP services. + +1539 Clauses 14 to 17 define the MAP protocol specification and the behaviour of service provider (protocol elements to be +1540 used to provide MAP services, mapping on to TC service primitives, abstract syntaxes, etc.). + +1541 Clauses 18 to 25 describe the MAP user procedures that make use of MAP services. + +1542 The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, +1543 functionality related to GERAN Iu mode is neither maintained nor enhanced. + +--- + +## 1544 2 References + +1545 The following documents contain provisions which, through reference in this text, constitute provisions of the present +1546 document. + +1547 - References are either specific (identified by date of publication, edition number, version number, etc.) or +1548 non-specific. + +1549 - For a specific reference, subsequent revisions do not apply. + +1550 - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including +1551 a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same +1552 Release as the present document. + +| | | | +|------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1553 | [1] | 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". | +| 1554 | [2] | 3GPP TS 22.001: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunication services supported by a Public Land Mobile Network (PLMN)". | +| 1555 | | | +| 1556 | [3] | 3GPP TS 22.002: "Bearer Services Supported by a Public Land Mobile Network (PLMN)". | +| 1557 | [4] | 3GPP TS 22.003: "Circuit Teleservices Supported by a Public Land Mobile Network (PLMN)". | +| 1558 | [5] | 3GPP TS 22.004: "General on Supplementary Services". | +| 1559 | [6] | 3GPP TS 42.009: "Digital cellular telecommunications system (Phase 2+); Security aspects". | +| 1560 | [7] | 3GPP TS 22.016: "International Mobile station Equipment Identities (IMEI)". | +| 1561 | [8] | 3GPP TS 22.041: "Operator Determined Barring". | +| 1562 | [9] | 3GPP TS 22.081: "Line identification supplementary services - Stage 1". | +| 1563 | [10] | 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1". | +| 1564 | [11] | 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 1". | +| 1565 | [12] | 3GPP TS 22.084: "Multi Party (MPTY) Supplementary Services - Stage 1". | +| 1566 | [13] | 3GPP TS 22.085: "Closed User Group (CUG) supplementary services - Stage 1". | +| 1567 | [14] | 3GPP TS 22.086: "Advice of charge (AoC) Supplementary Services - Stage 1". | +| 1568 | [15] | 3GPP TS 22.088: "Call Barring (CB) supplementary services - Stage 1". | +| 1569 | [16] | 3GPP TS 22.090: "Unstructured Supplementary Service Data (USSD); - Stage 1". | +| 1570 | [17] | 3GPP TS 23.003: "Numbering, addressing and identification". | +| 1571 | [18] | Void | +| 1572 | [19] | 3GPP TS 23.007: "Restoration procedures". | +| 1573 | [20] | 3GPP TS 23.008: "Organisation of subscriber data". | +| 1574 | [21] | 3GPP TS 23.009: "Handover procedures". | +| 1575 | [22] | 3GPP TS 23.011: "Technical realization of Supplementary Services - General Aspects". | +| 1576 | [23] | 3GPP TS 23.012: "Location management procedures". | +| 1577 | [24] | 3GPP TS 43.020: "Security related network functions". | +| 1578 | [25] | 3GPP TS 23.038: "Alphabets and language". | +| 1579 | [25a] | 3GPP TS 23.039: "Interface protocols for the connection of Short Message Service Centres (SMSCs) to Short Message Entities (SMEs)". | +| 1580 | | | +| 1581 | [26] | 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)". | +| 1582 | [26a] | 3GPP TS 23.271: "Functional stage2 description of LCS". | +| 1583 | [27] | 3GPP TS 23.081: "Line Identification Supplementary Services - Stage 2". | +| 1584 | [28] | 3GPP TS 23.082: "Call Forwarding (CF) Supplementary Services - Stage 2". | +| 1585 | [29] | 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 2". | +| 1586 | [30] | 3GPP TS 23.084: "Multi Party (MPTY) Supplementary Services - Stage 2". | +| 1587 | [31] | 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Services - Stage 2". | +| 1588 | [32] | 3GPP TS 23.086: "Advice of Charge (AoC) Supplementary Services - Stage 2". | + +| | | | +|------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1589 | [33] | 3GPP TS 23.088: "Call Barring (CB) Supplementary Services - Stage 2". | +| 1590 | [34] | 3GPP TS 23.090: "Unstructured Supplementary Services Data (USSD) - Stage 2". | +| 1591 | [34a] | 3GPP TS 33.204: "3G Security; Network domain security; TCAP user security". | +| 1592 | [35] | 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols - Stage 3". | +| 1593 | | | +| 1594 | [36] | 3GPP TS 24.010: "Mobile radio interface layer 3 Supplementary Services specification - General aspects". | +| 1595 | | | +| 1596 | [37] | 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". | +| 1597 | | | +| 1598 | [37a] | 3GPP TS 44.071: "Location Services (LCS) – stage 3". | +| 1599 | [38] | 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification - Formats and coding". | +| 1600 | | | +| 1601 | [39] | 3GPP TS 24.081: "Line identification supplementary services - Stage 3". | +| 1602 | [40] | 3GPP TS 24.082: "Call Forwarding (CF) Supplementary Services - Stage 3". | +| 1603 | [41] | 3GPP TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". | +| 1604 | [42] | 3GPP TS 24.084: "Multi Party (MPTY) Supplementary Services - Stage 3". | +| 1605 | [43] | 3GPP TS 24.085: "Closed User Group (CUG) Supplementary Services - Stage 3". | +| 1606 | [44] | 3GPP TS 24.086: "Advice of Charge (AoC) Supplementary Services - Stage 3". | +| 1607 | [45] | 3GPP TS 24.088: "Call Barring (CB) Supplementary Services - Stage 3". | +| 1608 | [46] | 3GPP TS 24.090: "Unstructured Supplementary Services Data - Stage 3". | +| 1609 | [47] | 3GPP TS 48.002: " Base Station System - Mobile-services Switching Centre (BSS - MSC) interface principles". | +| 1610 | | | +| 1611 | [48] | 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". | +| 1612 | | | +| 1613 | [49] | 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". | +| 1614 | | | +| 1615 | [49a1] | 3GPP TS 48.031: "Location Services (LCS); Serving Mobile Location Centre (SMLC) – Serving Mobile Location Centre (SMLC); SMLC Peer Protocol (SMLCPP)". | +| 1616 | | | +| 1617 | [49b] | 3GPP TS 48.071: "Location Services (LCS); Serving Mobile Location Centre - Base Station System (SMLC - BSS) interface Layer 3 specification". | +| 1618 | | | +| 1619 | [50] | 3GPP TS 49.001: "General network interworking scenarios". | +| 1620 | [51] | 3GPP TS 29.002: "Mobile Application Part (MAP) specification". | +| 1621 | [52] | Void | +| 1622 | [53] | Void | +| 1623 | [54] | Void | +| 1624 | [55] | 3GPP TS 29.006: "Interworking between a Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of Packet Switched data transmission services". | +| 1625 | | | +| 1626 | | | + +| | | | +|------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1627 | [56] | 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". | +| 1628 | | | +| 1629 | | | +| 1630 | [57] | 3GPP TS 29.008: "Application of the Base Station System Application Part (BSSAP) on the E-interface". | +| 1631 | | | +| 1632 | [58] | 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station System and BSS - Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)". | +| 1633 | | | +| 1634 | | | +| 1635 | [59] | 3GPP TS 29.011: "Signalling interworking for Supplementary Services". | +| 1636 | [59a] | 3GPP TS 49.031: "Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)". | +| 1637 | | | +| 1638 | [60] | Void | +| 1639 | [61] | 3GPP TS 52.008: "GSM Subscriber and Equipment Trace". | +| 1640 | [62] | ETS 300 102-1 (1990): "Integrated Services Digital Network (ISDN); User-network interface layer 3 specifications for basic call control". | +| 1641 | | | +| 1642 | [63] | ETS 300 136 (1992): "Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service description". | +| 1643 | | | +| 1644 | [64] | ETS 300 138 (1992): "Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service Digital Subscriber Signalling System No.one (DSS1) protocol". | +| 1645 | | | +| 1646 | [65] | ETS 300 287: "Integrated Services Digital Network (ISDN); Signalling System No.7; Transaction Capabilities (TC) version 2". | +| 1647 | | | +| 1648 | [66] | ETR 060: "Signalling Protocols and Switching (SPS); Guide-lines for using Abstract Syntax Notation One (ASN.1) in telecommunication application protocols". | +| 1649 | | | +| 1650 | [66b] | ETR 091: "ETSI object identifier tree; Common domain Mobile domain" | +| 1651 | [67] | ITU-T Recommendation E.164: "The international public telecommunication numbering plan". | +| 1652 | [68] | ITU-T Recommendation E.212: "The international identification plan for mobile terminals and mobile users". | +| 1653 | | | +| 1654 | [69] | ITU-T Recommendation E.213: "Telephone and ISDN numbering plan for land mobile stations in public land mobile networks (PLMN) ". | +| 1655 | | | +| 1656 | [70] | ITU-T Recommendation E.214: "Structure of the land mobile global title for the signalling connection control part (SCCP) ". | +| 1657 | | | +| 1658 | [71] | ITU-T Recommendation Q.699: "Interworking between ISDN access and non-ISDN access over ISDN User Part of Signalling System No. 7 ". | +| 1659 | | | +| 1660 | [72] | ITU-T Recommendation Q.711: "Specifications of Signalling System No.7; Functional description of the Signalling Connection Control Part". | +| 1661 | | | +| 1662 | [73] | ITU-T Recommendation Q.712: "Definition and function of SCCP messages". | +| 1663 | [74] | ITU-T Recommendation Q.713: "Specifications of Signalling System No.7; SCCP formats and codes". | +| 1664 | | | +| 1665 | [75] | ITU-T Recommendation Q.714: "Specifications of Signalling System No.7; Signalling Connection Control Part procedures". | +| 1666 | | | +| 1667 | [76] | ITU-T Recommendation Q.716: "Specifications of Signalling System No.7; Signalling connection control part (SCCP) performances". | +| 1668 | | | + +1669 [77] ITU-T Recommendation Q.721 (1988): "Specifications of Signalling System No.7; Functional +1670 description of the Signalling System No.7 Telephone user part". + +1671 [78] ITU-T Recommendation Q.722 (1988): "Specifications of Signalling System No.7; General +1672 function of Telephone messages and signals". + +1673 [79] ITU-T Recommendation Q.723 (1988): "Specifications of Signalling System No.7; Formats and +1674 codes". + +1675 [80] ITU-T Recommendation Q.724 (1988): "Specifications of Signalling System No.7; Signalling +1676 procedures". + +1677 [81] ITU-T Recommendation Q.725 (1988): "Specifications of Signalling System No.7; Signalling +1678 performance in the telephone application". + +1679 [82] ITU-T Recommendation Q.761 (1988): "Specifications of Signalling System No.7; Functional +1680 description of the ISDN user part of Signalling System No.7". + +1681 [83] ITU-T Recommendation Q.762 (1988): "Specifications of Signalling System No.7; General +1682 function of messages and signals". + +1683 [84] ITU-T Recommendation Q.763 (1988): "Specifications of Signalling System No.7; Formats and +1684 codes". + +1685 [85] ITU-T Recommendation Q.764 (1988): "Specifications of Signalling System No.7; Signalling +1686 procedures". + +1687 [86] ITU-T Recommendation Q.767: "Specifications of Signalling System No.7; Application of the +1688 ISDN user part of CCITT signalling System No.7 for international ISDN interconnections". + +1689 [87] ITU-T Recommendation Q.771: "Specifications of Signalling System No.7; Functional description +1690 of transaction capabilities". + +1691 [88] ITU-T Recommendation Q.772: "Specifications of Signalling System No.7; Transaction +1692 capabilities information element definitions". + +1693 [89] ITU-T Recommendation Q.773: "Specifications of Signalling System No.7; Transaction +1694 capabilities formats and encoding". + +1695 [90] ITU-T Recommendation Q.774: "Specifications of Signalling System No.7; Transaction +1696 capabilities procedures". + +1697 [91] ITU-T Recommendation Q.775: "Specifications of Signalling System No.7; Guide-lines for using +1698 transaction capabilities". + +1699 [92] ITU-T Recommendation X.200: "Reference Model of Open systems interconnection for CCITT +1700 Applications". + +1701 [93] ITU-T Recommendation X.680: "Information technology – Abstract Syntax Notation One +1702 (ASN.1): Specification of basic notation". + +1703 [93b] ITU-T Recommendation X.681: "Information technology – Abstract Syntax Notation One +1704 (ASN.1): Information object specification". + +1705 [94] ITU-T Recommendation X.690: "Information technology – ASN.1 encoding rules: Specification +1706 of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding +1707 Rules (DER)". + +1708 [95] ITU-T Recommendation X.210: "Open systems interconnection layer service definition +1709 conventions". + +1710 [97] 3GPP TS 23.018: "Basic Call Handling". + +1711 [98] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) +1712 Phase 4 - Stage 2". + +| | | | +|------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1713 | [99] | 3GPP TS 23.079: "Support of Optimal Routeing (SOR) - Stage 2". | +| 1714 | [100] | 3GPP TS 43.068: "Voice Group Call Service (VGCS) - Stage 2". | +| 1715 | [101] | 3GPP TS 43.069: "Voice Broadcast service (VBS) - Stage 2". | +| 1716 | [102] | ANSI T1.113: "Signaling System No. 7 (SS7) - ISDN User Part". | +| 1717 | [103] | Void | +| 1718 | [104] | 3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2". | +| 1719 | [105] | 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". | +| 1720 | | | +| 1721 | [106] | 3GPP TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification". | +| 1722 | | | +| 1723 | [107] | 3GPP TS 23.093: "Technical Realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2". | +| 1724 | | | +| 1725 | [108] | 3GPP TS 23.066: "Support of Mobile Number Portability (MNP); Technical Realisation Stage 2". | +| 1726 | [109] | ANSI T1.112 (1996): "Telecommunication – Signalling No. 7 - Signaling Connection Control Part (SCCP)". | +| 1727 | | | +| 1728 | [110] | 3GPP TS 23.116: "Super-Charger Technical Realisation; Stage 2". | +| 1729 | [111] | Void. | +| 1730 | [112] | Void | +| 1731 | [113] | Void | +| 1732 | [114] | Void | +| 1733 | [115] | Void | +| 1734 | [116] | ITU-T Recommendation Q.850 (May 1998): "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part". | +| 1735 | | | +| 1736 | [117] | 3GPP TS 22.135: "Multicall; Service description; Stage 1". | +| 1737 | [118] | 3GPP TS 23.135: "Multicall supplementary service; Stage 2". | +| 1738 | [119] | 3GPP TS 24.135: "Multicall supplementary service; Stage 3". | +| 1739 | [120] | 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling". | +| 1740 | | | +| 1741 | [121] | 3GPP TS 29.202: "SS7 signalling transport in core network". | +| 1742 | [122] | 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". | +| 1743 | [123] | 3GPP TS 22.071: "Location Services (LCS); Service description, Stage 1". | +| 1744 | [124] | ITU-T Recommendation X.880: "Data networks and open system communication - Open System Interconnection - Service definitions - Remote operations: Concepts, model and notation". | +| 1745 | | | +| 1746 | [125] | 3GPP TS 23.278: "Customised Applications for Mobile Network Enhanced Logic (CAMEL) Phase 4 – Stage 2 IM CN Interworking (Rel-5)". | +| 1747 | | | +| 1748 | [126] | 3GPP TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service; UDI/RDI fallback and service modification". | +| 1749 | | | +| 1750 | [127] | 3GPP TS 26.103: "Speech codec list for GSM and UMTS". | +| 1751 | [128] | 3GPP TS 23.141: "Presence Service; Architecture and Functional Description". | + +| | | | +|------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1752 | [129] | 3GPP TS 23.094: "Follow Me (FM) – Stage 2". | +| 1753 | [130] | Void | +| 1754 | [131] | 3GPP TS 32.421: "Subscriber and equipment trace: Trace concepts and requirements". | +| 1755 | [132] | 3GPP TS 32.422: "Subscriber and equipment trace; Trace control and Configuration Management". | +| 1756 | | | +| 1757 | [133] | 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". | +| 1758 | | | +| 1759 | [134] | 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access". | +| 1760 | | | +| 1761 | [135] | 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services". | +| 1762 | [136] | 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) - Stage 2". | +| 1763 | | | +| 1764 | [137] | 3GPP TS 24.067: "Enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3". | +| 1765 | [138] | 3GPP TS 22.011: "Service accessibility". | +| 1766 | [139] | IETF RFC 3588: "Diameter Base Protocol". | +| 1767 | [140] | Void | +| 1768 | [141] | 3GPP TS 29.173: "Locations Services; Diameter-based SLh interface for Control Plane LCS". | +| 1769 | [142] | Void | +| 1770 | [143] | 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2". | +| 1771 | [144] | 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Service GPRS Support Node (SGSN) related interfaces based on Diameter protocol". | +| 1772 | | | +| 1773 | [145] | 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". | +| 1774 | | | +| 1775 | [146] | 3GPP TS 29.205: "Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture; Stage 3". | +| 1776 | | | +| 1777 | [147] | 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". | +| 1778 | | | +| 1779 | [148] | 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". | +| 1780 | | | +| 1781 | [149] | 3GPP TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C)". | +| 1782 | | | +| 1783 | [150] | 3GPP TS 23.380: "IMS Restoration Procedures". | +| 1784 | [151] | 3GPP TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces". | +| 1785 | [152] | 3GPP TS 29.118: "Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification". | +| 1786 | | | +| 1787 | [153] | 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". | +| 1788 | [154] | 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture". | + +1790 ADD Automatic Device Detection + +1791 GANSS Galileo and Additional Navigation Satellite Systems + +1792 All other abbreviations used in the present document are listed in 3GPP TS 21.905. + +--- + +## 1793 4 Void + +## 1794 5 Overload and compatibility overview + +### 1795 5.1 Overload control + +1796 There is a requirement for an overload/congestion control for all entities of the Public Land Mobile Network and the +1797 underlying Signalling System No. 7. + +#### 1798 5.1.1 Overload control for MSC (outside MAP) + +1799 For the entity MSC the following two procedures (outside MAP) may be applied to control the processor load: + +- 1800 - ISDN +- 1801 CCITT Recommendation Q.764 (Automatic Congestion Control), applicable to reduce the mobile terminating +- 1802 traffic; +- 1803 - BSSAP +- 1804 3GPP TS 48.008 [49] (A-interface Flow Control), applicable to reduce the mobile originating traffic. + +#### 1805 5.1.2 Overload control for MAP entities + +1806 For all MAP entities, especially the HLR, the following overload control method is applied. + +1807 If overload of a MAP entity is detected requests for certain MAP operations (see tables 5.1/1, 5.1/2, 5.1/3 and 5.1/4) +1808 may be ignored by the responder. The decision as to which MAP Operations may be ignored is made by the MAP +1809 service provider and is based upon the priority of the application context. + +1810 Since most of the affected MAP operations are supervised in the originating entity by TC timers (medium) an additional +1811 delay effect is achieved for the incoming traffic. + +1812 If overload levels are applicable in the Location Registers the MAP operations should be discarded taking into account +1813 the priority of their application context (see table 5.1/1 for HLR, table 5.1/2 for MSC/VLR, table 5.1/3 for the SGSN +1814 and table 5.1/4 for the SMLC; the lowest priority is discarded first). + +1815 The ranking of priorities given in the tables 5.1/1, 5.1/2, 5.1/3 and 5.1/4 is not normative. The tables can only be seen as +1816 a proposal that might be changed due to network operator/implementation matters. + +1817 + +**Table 5.1/1: Priorities of Application Contexts for HLR as Responder** + +| | | | +|------|--------------------------------------------------------------|-----------| +| 1818 | Responder = HLRInitiating Entity | | +| 1819 | Priority high | | +| 1820 | Mobility Management | | +| 1821 | networkLocUp VLR | | +| 1822 | (updateLocation), | | +| 1823 | (restoreData/v2), | | +| 1824 | (sendParameters/v1) | | +| 1825 | gprsLocationUpdate | SGSN | +| 1826 | (updateGPRSLocation/v3), | | +| 1827 | infoRetrieval VLR/SGSN | | +| 1828 | (sendAuthenticationInfo/v2/v3), | | +| 1829 | (sendParameters/v1) | | +| 1830 | istAlerting MSC | | +| 1831 | (istAlert/v3) msPurging | VLR | +| 1832 | (purgeMS/v2/v3) | | +| 1833 | msPurging SGSN | | +| 1834 | (purgeMS/v3) | | +| 1835 | Short Message Service | | +| 1836 | shortMsgGateway GMSC | | +| 1837 | (sendRoutingInfoforSM), | | +| 1838 | (reportSM-DeliveryStatus) | | +| 1839 | mwdMngt VLR/SGSN | | +| 1840 | (readyForSM/v2/v3), | | +| 1841 | (noteSubscriberPresent/v1) | | +| 1842 | Mobile Terminating Traffic | | +| 1843 | locInfoRetrieval GMSC | | +| 1844 | (sendRoutingInfo) | | +| 1845 | anyTimeEnquiry gsmSCF | | +| 1846 | (anyTimeInterrogation/v3) | | +| 1847 | reporting VLR | | +| 1848 | (statusReport) | | +| 1849 | Location Services | | +| 1850 | locationSvcGateway | GMLC | +| 1851 | (sendRoutingInfoforLCS/v3) | | +| 1852 | Subscriber Controlled Inputs (Supplementary Services) | | +| 1853 | networkFunctionalSs | VLR | +| 1854 | (registerSS), | | +| 1855 | (eraseSS), | | +| 1856 | (activateSS), | | +| 1857 | (deactivateSS), | | +| 1858 | (interrogateSS), | | +| 1859 | (registerPassword), | | +| 1860 | (processUnstructuredSS-Data/v1), | | +| 1861 | (beginSubscriberActivity/v1) | | +| 1862 | callCompletion VLR | | +| 1863 | (registerCCEntry), | | +| 1864 | (eraseCCEntry) | | +| 1865 | networkUnstructuredSs | VLR | +| 1866 | (processUnstructuredSS-Request/v2) | | +| 1867 | imsiRetrieval VLR | | +| 1868 | (sendIMSI/v2) | | +| 1869 | gprsLocationInfoRetrieval | GGSN/SGSN | +| 1870 | (sendRoutingInfoForGprs/v3/v4) | | +| 1871 | failureReport GGSN/SGSN | | +| 1872 | (failureReport/v3) | | +| 1873 | authenticationFailureReport | VLR/SGSN | +| 1874 | (authenticationFailureReport/v3) | | + +1875 ***Priority low*** + +1876 NOTE: The application context name is the last component but one of the object identifier. +1877 Operation names are given in brackets for information with "/vn" appended to vn only operations. + +1878 + +**Table 5.1/3: Priorities of Application Contexts for SGSN as Responder** + +| 1879 | Responder = SGSN | Initiating Entity | +|------|------------------------------------------------------|--------------------------| +| 1880 | Priority high | | +| 1881 | Mobility and Location Register Management | | +| 1882 | locationCancel HLR | | +| 1883 | (cancelLocation v3) | | +| 1884 | reset HLR | | +| 1885 | (reset) | | +| 1886 | subscriberDataMngt | HLR | +| 1887 | (insertSubscriberData v3), | | +| 1888 | (deleteSubscriberData v3) | | +| 1889 | tracing HLR | | +| 1890 | (activateTraceMode), | | +| 1891 | (deactivateTraceMode) | | +| 1892 | | | +| 1893 | Short Message Service | | +| 1894 | shortMsgMT-Relay | MSC | +| 1895 | (MT-ForwardSM v3), | | +| 1896 | (forwardSM v1/v2) | | +| 1897 | | | +| 1898 | Location Services | | +| 1899 | | | +| 1900 | locationSvcEnquiry | GMLC | +| 1901 | (provideSubscriberLocation v3) | | +| 1902 | | | +| 1903 | Network-Requested PDP context activation | | +| 1904 | gprsNotify HLR | | +| 1905 | (noteMsPresentForGprs v3), | | +| 1906 | | | +| 1907 | ( Subscriber Location & State retrieval ) | | +| 1908 | subscriberInfoEnquiry | HLR | +| 1909 | (provideSubscriberInformation/v3) | | +| 1910 | | | +| 1911 | Priority low | | + +1912 NOTE: The application context name is the last component but one of the object identifier. +1913 Operation names are given in brackets for information with "/vn" appended to vn. + +**Table 5.1/2: Priorities of Application Contexts for MSC/VLR as Responder** + +| Responder = MSC/VLR | Initiating Entity | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| Priority high | | +| Handover
handoverControl MSC
(prepareHandover/v2/v3),
(performHandover/v1) | | +| Group call and Broadcast call
groupCallControlMSC
(prepareGroupCall/v3)
groupCallInfoRetrieval
(sendGroupCallInfo/v3) | MSC | +| Mobility and Location Register Management
locationCancel HLR
(cancelLocation)
reset HLR
(reset)
immediateTermination
(istCommand/v3)
interVlrInfoRetrieval
(sendIdentification/v2/v3),
(sendParameters/v1)
subscriberDataMngt
(insertSubscriberData),
(deleteSubscriberData)
tracing HLR
(activateTraceMode),
(deactivateTraceMode) | HLR
VLR
HLR | +| Short Message Service
shortMsgMO-Relay
(MO-ForwardSM v3),
(forwardSM v1/v2)
shortMsgMT-Relay
(MT-ForwardSM v3),
(forwardSM v1/v2)
shortMsgAlert HLR
(alertServiceCentre/v2),
(alertServiceCentreWithoutResult/v1) | MSC/SGSN
MSC | +| Mobile Terminating Traffic
resourceMngt GMSC
(releaseResources)
roamingNbEnquiry HLR
(provideRoamingNumber)
callControlTransfer
(resumeCallHandling)
subscriberInfoEnquiry
(provideSubscriberInformation/v3)
reporting HLR
(remoteUserFree),
(SetReportingState) | MSC
HLR | +| Location Services
locationSveEnquiry
(provideSubscriberLocation/v3) | GMLC | +| Network-Initiated USSD
networkUnstructuredSs
(unstructuredSS-Request/v2),
(unstructuredSS-Notify/v2) | HLR | +| Priority low | | + +1916 NOTE: The application context name is the last component but one of the object identifier. +1917 Operation names are given in brackets for information with "/vn" appended to vn only operations. + +### 1918 5.1.3 Congestion control for Signalling System No. 7 + +1919 The requirements of SS7 Congestion control have to be taken into account as far as possible. + +1920 Means that could be applied to achieve the required traffic reductions are described in clauses 5.1.1 and 5.1.2. + +## 1921 5.2 Compatibility + +### 1922 5.2.1 General + +1923 The present document of the Mobile Application Part is designed in such a way that an implementation which conforms +1924 to it can also conform to the Mobile Application Part operational version 1 specifications, except on the MSC-VLR +1925 interface. + +1926 A version negotiation mechanism based on the use of an application-context-name is used to negotiate the protocol +1927 version used between two entities for supporting a MAP-user signalling procedure. + +1928 When starting a signalling procedure, the MAP-user supplies an application-context-name to the MAP-provider. This +1929 name refers to the set of application layer communication capabilities required for this dialogue. This refers to the +1930 required TC facilities (e.g. version 1 or 2) and the list of operation packages (i.e. set of operations) from which +1931 operations can be invoked during the dialogue. + +1932 A version one application-context-name may only be transferred to the peer user in a MAP-U-ABORT to an entity of +1933 version two or higher (i.e. to trigger a dialogue which involves only communication capabilities defined for MAP +1934 operational version 1). + +1935 If the proposed application-context-name can be supported by the responding entity the dialogue continues on this basis +1936 otherwise the dialogue is refused and the initiating user needs to start a new dialogue, which involves another +1937 application-context-name which requires less communication capabilities but provides similar functionality (if +1938 possible). + +1939 When a signalling procedure can be supported by several application contexts that differ by their version number, the +1940 MAP-User needs to select a name. It can either select the name that corresponds to the highest version it supports or +1941 follow a more specific strategy so that the number of protocol fallbacks due to version compatibility problems is +1942 minimised. + +### 1943 5.2.2 Strategy for selecting the Application Context (AC) version + +1944 A method should be used to minimise the number of protocol fall-backs which would occur sometimes if the highest +1945 supported AC-Name were always the one selected by GSM entities when initiating a dialogue. The following method is +1946 an example that can be used mainly at transitory phase stage when the network is one of mixed phase entities. + +#### 1947 5.2.2.1 Proposed method + +1948 A table (table 1) may be set up by administrative action to define the highest application context (AC) version supported +1949 by each destination; a destination may be another node within the same or a different PLMN, or another PLMN +1950 considered as a single entity. The destination may be defined by an E.164 number or an E.214 number derived from an +1951 IMSI or in North America (World Zone 1) by an E.164 number or an IMSI (E.212 number). The table also includes the +1952 date when each destination is expected to be able to handle at least one AC of the latest version of the MAP protocol. +1953 When this date is reached, the application context supported by the node is marked as "unknown", which will trigger the +1954 use of table 2. + +1955 A second table (table 2) contains an entry for each destination that has an entry in table 1. For a given entity, the entry +1956 in table 2 may be a single application context version or a vector of different versions applying to different application +1957 contexts for that entity. Table 2 is managed as described in clause 5.2.2.2. + +1958 The data for each destination will go through the following states: + +- 1959 a) the version shown in table 1 is "version n-1", where 'n' is the highest version existing in this specification; table 2 +1960 is not used; +- 1961 b) the version shown in table 1 is "unknown"; table 2 is used, and maintained as described in clause 5.2.2.2; +- 1962 c) when the PLMN operator declares that an entity (single node or entire PLMN) has been upgraded to support all +1963 the MAP version n ACs defined for the relevant interface, the version shown in table 1 is set to "version n" by +1964 administrative action; table 2 is no longer used, and the storage space may be recovered. + +## 1965 5.2.2.2 Managing the version look-up table + +1966 **WHEN** it receives a MAP-OPEN and the MAP-User determines the originating entity number either using the +1967 originating address parameter or the originating reference parameter or retrieving it from the subscriber data using the +1968 IMSI or the MSISDN. + +1969 **IF** the entity number is known: + +1970 **THEN** + +1971 It updates (if required) the associated list of highest supported ACs. + +1972 **ELSE** + +1973 It creates an entry for this entity and includes the received AC-name in the list of highest supported ACs. + +1974 **WHEN** starting a procedure, the originating MAP-user looks up its version control table. + +1975 **IF** the destination address is known and not timed-out. + +1976 **THEN** + +1977 It retrieves the appropriate AC-name and uses it + +1978 **IF** the dialogue is accepted by the peer + +1979 **THEN** + +1980 It does not modify the version control table + +1981 **ELSE** (this should never occur) + +1982 It starts a new dialogue with the common highest version supported (based on information implicitly +1983 or explicitly provided by the peer). + +1984 It replaces the old AC-name by the new one in the list of associated highest AC supported. + +1985 **ELSE** + +1986 It uses the AC-name that corresponds to the highest version it supports. + +1987 **IF** the dialogue is accepted by the peer. + +1988 **THEN** + +1989 It adds the destination node in its version control table and includes the AC-Name in the list of +1990 associated highest AC supported. + +1991 **ELSE** + +1992 It starts a new dialogue with the common highest version supported (based on information implicitly or +1993 explicitly provided by the peer). + +1994 **IF** the destination node was not known + +1995 **THEN** + +1996 It adds the destination node in its version control table and includes the new AC-Name in the list of +1997 associated highest AC supported. + +1998 **ELSE** + +1999 It replaces the old AC-name by the new one in the list of highest supported AC and reset the timer. + +### 2000 5.2.2.3 Optimising the method + +2001 A table look-up may be avoided in some cases if both the HLR and the VLR or both the HLR and the SGSN store for +2002 each subscriber the version of the AC-name used at location updating. Then: + +2003 - for procedures which make use of the same application-context, the same AC-name (thus the same version) can +2004 be selected (without any table look-up) when the procedure is triggered; + +2005 - for procedures which make use of a different application-context but which includes one of the packages used by +2006 the location updating AC, the same version can be selected (without any table look-up) when the procedure is +2007 triggered; + +2008 **for HLR:** + +2009 - Subscriber data modification (stand alone); + +2010 **for VLR:** + +2011 - Data Restoration. + +--- + +## 2012 6 Requirements concerning the use of SCCP and TC + +### 2013 6.1 Use of SCCP + +2014 The Mobile Application Part (MAP) makes use of the services offered by the Signalling Connection Control Part +2015 (SCCP). + +2016 MAP supports the following SCCP versions: + +2017 - Signalling Connection Control Part, Signalling System no. 7 CCITT ('Blue Book SCCP'); + +2018 - Signalling Connection Control Part, Signalling System no. 7 ITU-T Recommendation (07/96) Q.711 to Q.716 +2019 ('White Book SCCP'). Support of White Book SCCP at the receiving side shall be mandated from 00:01hrs, 1st +2020 July 2002(UTC). However, for signalling over the MAP E-interface to support inter-MSC handover/relocation, +2021 the support of White Book SCCP shall be mandated with immediate effect. + +2022 A White Book SCCP message will fail if any signalling point used in the transfer of the message does not support +2023 White Book SCCP. Therefore it is recommended that the originator of the White Book SCCP message supports a drop +2024 back mechanism or route capability determination mechanism to interwork with signalling points that are beyond the +2025 control of GSM/UMTS network operators. + +2026 In North America (World Zone 1) the national version of SCCP is used as specified in ANSI T1.112. Interworking +2027 between a PLMN in North America and a PLMN outside North America will involve an STP to translate between +2028 ANSI SCCP and ITU-T/CCITT SCCP. + +2029 The SCCP is identified as an MTP3-user and the transport of SCCP messages between two entities shall be +2030 accomplished according to the 3GPP TS 29.202 [121]. + +#### 2031 6.1.1 SCCP Class + +2032 MAP will only make use of the connectionless classes (0 or 1) of the SCCP. + +#### 2033 6.1.2 Sub-System Number (SSN) + +2034 The Application Entities (AEs) defined for MAP consist of several Application Service Elements (ASEs) and are + 2035 addressed by sub-system numbers (SSNs). The SSNs for MAP are specified in 3GPP TS 23.003 [17]. + +2036 When the SGSN emulates MSC behaviour for processing messages (MAP-MO-FORWARD-SHORT-MESSAGE, + 2037 MAP\_CHECK\_IMEI, MAP\_SUBSCRIBER\_LOCATION\_REPORT) towards entities which do not support + 2038 interworking to SGSNs, it shall use the MSC SSN in the calling party address instead of the SGSN SSN. + +2039 When present in the network, the Presence Network Agent emulates the behaviour of the GSM Service Control + 2040 Function (gsm SCF) for processing of messages (MAP-NOTE-MM-EVENT, MAP-ANY-TIME-INTERROGATION + 2041 and MAP-ANY-TIME-MODIFICATION). + +2042 When a FFN (Follow Me Functional Node, see TS 23.094 [129]) is implemented in a network entity different from + 2043 HLR, this network entity shall emulate HLR behaviour, i.e. it shall accept MAP-PROCESS-UNSTRUCTURED-SS- + 2044 REQUEST messages addressed with SSN for HLR. + +2045 In an EPS, an Interworking Function (IWF) may be used to convert Diameter S6a messages to MAP Gr messages and + 2046 vice versa; also an IWF may be used to convert Diameter S13 messages to MAP Gf messages and vice versa. An SSN + 2047 value for the IWF does not exist. Instead the IWF shall use the SGSN SSN value when serving an MME and use the + 2048 HLR SSN when serving an HSS. An IWF is said to serve an MME (or HSS) when Diameter messages are exchanged + 2049 between the IWF and the MME (or HSS). + +2050 In a 5GS, a UDM may support a MAP interface towards the SMS-GMSC/SMS-Router by emulating HLR behaviour, + 2051 i.e. the UDM may have an integrated/collocated HLR component serving the MAP communication to the SMS- + 2052 GMSC/SMS-Router. An SSN value for UDM does not exist. Instead the UDM (with an integrated/collocated HLR) + 2053 shall use the HLR SSN value. + +2054 + +## 2055 6.1.3 SCCP addressing + +### 2056 6.1.3.1 Introduction + +2057 Within the GSM System there will be a need to communicate between entities within the same PLMN and in different + 2058 PLMNs. Using the Mobile Application Part (MAP) for this function implies the use of Transaction Capabilities (TC) + 2059 and the Signalling Connection Control Part (SCCP) of CCITT Signalling System No. 7. + +2060 Only the entities that should be addressed are described below. If the CCITT or ITU-T SCCP is used, the format and + 2061 coding of address parameters carried by the SCCP for that purpose shall comply with CCITT Recommendation Q.713 + 2062 with the following restrictions: + +#### 2063 1) Intra-PLMN addressing + +2064 For communication between entities within the same PLMN, a MAP SSN shall always be included in the + 2065 called and calling party addresses. All other aspects of SCCP addressing are network specific. + +#### 2066 2) Inter-PLMN addressing + +##### 2067 a) Called Party Address + +- 2068 - SSN indicator = 1 (MAP SSN always included); +- 2069 - Global title indicator = 0100 (Global title includes translation type, numbering plan, encoding scheme and + 2070 nature of address indicator); +- 2071 - the translation type field will be coded "00000000" (Not used). For call related messages for non-optimal + 2072 routed calls (as described in 3GPP TS 23.066 [108]) directed to another PLMN the translation type field + 2073 may be coded "10000000" (CRMNP); +- 2074 - Routing indicator = 0 (Routing on global title); + +##### 2075 b) Calling Party Address + +- 2076 - SSN indicator = 1 (MAP SSNs always included); + +2077 - Point code indicator = 0; + +2078 - Global title indicator = 0100 (Global title includes translation type, numbering plan, encoding scheme and +2079 nature of address indicator); + +2080 - Numbering Plan = 0001 (ISDN Numbering Plan, E.164; In Case of Inter-PLMN Signalling, the dialogue +2081 initiating entity and dialogue responding entity shall always include its own E.164 Global Title as Calling +2082 Party Address); + +2083 - the translation type field will be coded "00000000" (Not used); + +2084 - Routing indicator = 0 (Routing on Global Title). + +2085 If ANSI T1.112 SCCP is used, the format and coding of address parameters carried by the SCCP for that purpose shall +2086 comply with ANSI specification T1.112 with the following restrictions: + +2087 1) Intra-PLMN addressing + +2088 For communication between entities within the same PLMN, a MAP SSN shall always be included in the +2089 called and calling party addresses. All other aspects of SCCP addressing are network specific. + +2090 2) Inter-PLMN addressing + +2091 a) Called Party Address + +2092 - SSN indicator = 1 (MAP SSN always included); + +2093 - Global title indicator = 0010 (Global title includes translation type); + +2094 - the Translation Type (TT) field will be coded as follows: + +2095 TT = 9, if IMSI is included; + +2096 TT = 14, if MSISDN is included; + +2097 Or TT = 10, if Network Element is included. (If TT=10, then Number Portability GTT is not invoked, +2098 if TT=14, then Number Portability GTT may be invoked). + +2099 - Routing indicator = 0 (Routing on global title); + +2100 b) Calling Party Address + +2101 - SSN indicator = 1 (MAP SSNs always included); + +2102 - Point code indicator = 0; + +2103 - Global Title indicator = 0010 (Global title includes translation type); + +2104 TT = 9, if IMSI is included; + +2105 TT = 14, if MSISDN is included; + +2106 Or TT = 10, if Network Element is included. (If TT=10, then Number Portability GTT is not invoked, +2107 if TT=14, then Number Portability GTT may be invoked). + +2108 Routing indicator = 0 (Routing on Global Title). + +2109 If a Global Title translation is required for obtaining routeing information, one of the numbering plans E.164, E.212 and +2110 E.214 is applicable. + +2111 - E.212 numbering plan. + +2112 When CCITT or ITU-T SCCP is used, an E.212 number must not be included as Global Title in an SCCP +2113 UNITDATA message. The translation of an E.212 number into a Mobile Global Title is applicable in a +2114 dialogue initiating VLR, SGSN or GGSN if the routeing information towards the HLR is derived from the +2115 subscriber's IMSI. In World Zone 1 when ANSI SCCP is used, the IMSI (E.212 number) is used as a Global +2116 Title to address the HLR. When an MS moves from one VLR service area to another, the new VLR may + +2117            derive the address of the previous VLR from the Location Area Identification provided by the MS in the +2118            location registration request. The PLMN where the previous VLR is located is identified by the E.212 +2119            numbering plan elements of the Location Area Identification, i.e. the Mobile Country Code (MCC) and the +2120            Mobile Network Code (MNC). + +2121    -   E.214 and E.164 numbering plans. + +2122            When CCITT or ITU-T SCCP is used, only address information belonging to either E.214 or E.164 +2123            numbering plan is allowed to be included as Global Title in the Called and Calling Party Address. In World +2124            Zone 1 when ANSI SCCP is used, the IMSI (E.212 number) is used as a Global Title to address the HLR. + +2125            If the Calling Party Address associated with the dialogue initiating message contains a Global Title, the +2126            sending network entity shall include its E.164 entity number. + +2127            When receiving an SCCP UNITDATA message, SCCP shall accept either of the valid numbering plans in +2128            the Called Party Address and in the Calling Party Address. + +2129            When CCITT or ITU-T SCCP is used and an N-UNITDATA-REQUEST primitive from TC is received, +2130            SCCP shall accept an E.164 number or an E.214 number in the Called Address and in the Calling Address. In +2131            World Zone 1 when ANSI SCCP is used, the IMSI (E.212 number) is used instead of E.214 number. + +2132 The following clauses describe the method of SCCP addressing appropriate for each entity both for the simple +2133 intra-PLMN case and where an inter-PLMN communication is required. The following entities are considered: + +- 2134    -   the Mobile-services Switching Centre (MSC); +- 2135    -   the Home location Register (HLR); +- 2136    -   the Visitor Location Register (VLR); +- 2137    -   the Gateway Mobile-services Switching Centre (GMSC); +- 2138    -   the GSM Service Control Function (gsmSCF); +- 2139    -   the Interworking Mobile-services Switching Centre (IWMSC); +- 2140    -   the Serving GPRS Support Node (SGSN); +- 2141    -   the Gateway GPRS Support Node (GGSN); +- 2142    -   the Gateway Mobile Location Centre (GMLC); +- 2143    -   the CSG Subscriber Server (CSS). + +### 2144 6.1.3.2            The Mobile-services Switching Centre (MSC) + +2145 There are several cases where it is necessary to address the MSC. + +#### 2146 6.1.3.2.1            MSC interaction during handover or relocation + +2147 The address is derived from the target Cell id or from the target RNC id. + +#### 2148 6.1.3.2.2            MSC for short message routing + +2149 When a short message has to be routed to an MS, the GMSC addresses the VMSC by an MSC identity received from +2150 the HLR that complies with E.164 rules. + +2151 For MS originating short message, the IWMSC address is derived from the Service Centre address. + +#### 2152 6.1.3.2.3            MSC for location request routing + +2153 When a location request for a particular MS needs to be sent to the MS's VMSC, the GMLC addresses the VMSC using +2154 an E.164 address received from the MS's HLR. + +#### 2155 6.1.3.2.4 MSC for LMU Control + +2156 When a control message has to be routed to an LMU from an SMLC, the SMLC addresses the serving MSC for the +2157 LMU using an E.164 address. + +#### 2158 6.1.3.3 The Home Location Register (HLR) + +2159 There are several cases where the HLR has to be addressed. + +##### 2160 6.1.3.3.1 During call set-up + +2161 When a call is initiated the HLR of the called mobile subscriber will be interrogated to discover the whereabouts of the +2162 MS. The addressing required by the SCCP will be derived from the MSISDN dialled by the calling subscriber. The +2163 dialled number will be translated into either an SPC, in the case of communications within a PLMN, or a Global Title if +2164 other networks are involved (i.e. if the communication is across a PLMN boundary). + +2165 If the calling subscriber is a fixed network subscriber, the interrogation can be initiated from the Gateway MSC of the +2166 home PLMN in the general case. If the topology of the network allows it, the interrogation could be initiated from any +2167 Signalling Point that has MAP capabilities, e.g. local exchange, outgoing International Switching Centre (ISC), etc. + +##### 2168 6.1.3.3.2 Before location updating completion + +2169 When an MS registers for the first time in a VLR, the VLR has to initiate the update location dialogue with the MS's +2170 HLR and a preceding dialogue for authentication information retrieval if the authentication information must be +2171 retrieved from the HLR. When initiating either of these dialogues, the only data for addressing the HLR that the VLR +2172 has available is contained in the IMSI, and addressing information for SCCP must be derived from it. When continuing +2173 the established update location dialogue (as with any other dialogue), the VLR must derive the routeing information +2174 towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the +2175 dialogue terminating message is received. This means that the VLR must be able to address the HLR based on: + +- 2176 - an E.214 Mobile Global Title originally derived by the VLR from the IMSI (when CCITT or ITU-T SCCP is +2177 used), or an E.212 number originally derived from IMSI (when ANSI SCCP is used, an IMSI); or +- 2178 - an E.164 HLR address; or +- 2179 - in the case of intra-PLMN signalling, an SPC. + +2180 When answering with Global Title to the VLR, the HLR shall insert its E.164 address in the Calling Party Address of +2181 the SCCP message containing the first responding CONTINUE message. + +2182 If the HLR is in the same PLMN as the VLR, local translation tables may exist to derive an SPC. For authentication +2183 information retrieval and location updating via the international PSTN/ISDN signalling network that requires the use of +2184 CCITT or ITU-T SCCP, the Global Title must be derived from the IMSI, using the principles contained in CCITT +2185 Recommendation E.214 and the Numbering Plan Indicator (NPI) value referenced by the SCCP Specifications. In +2186 World Zone 1 where the ANSI SCCP is used, IMSI (E.212 number) is used as Global Title. A summary of the +2187 translation from the IMSI (CCITT Recommendation E.212) to Mobile Global Title (described in CCITT +2188 Recommendation E.214) is shown below: + +- 2189 - E.212 Mobile Country Code translates to E.164 Country Code; +- 2190 - E.212 Mobile Network Code translates to E.164 National Destination Code; +- 2191 - E.212 Mobile Subscriber Identification Number (MSIN) is carried unchanged if within the E.164 number +2192 maximum length (15 digits). If the Mobile Global Title is more than 15 digits the number is truncated to 15 by +2193 deleting the least significant digits. + +2194 This translation will be done either at the application or at SCCP level in the VLR. The Mobile Global Title thus +2195 derived will be used to address the HLR. + +2196 If location updating is triggered by an MS that roams from one MSC Area into a different MSC Area served by the +2197 same VLR, the VLR shall address the HLR in the same way as if the MS registers for the first time in the VLR. + +##### 2198 6.1.3.3.3 After location updating completion + +2199 In this case, the subscriber's basic MSISDN has been received from the HLR during the subscriber data retrieval +2200 procedure as well as the HLR number constituting a parameter of the MAP message indicating successful completion of +2201 the update location dialogue. From either of these E.164 numbers the address information for initiating dialogues with +2202 the roaming subscriber's HLR can be derived. Also the subscriber's IMSI may be used for establishing the routeing +2203 information towards the HLR. This may apply in particular if the dialogue with the HLR is triggered by subscriber +2204 controlled input. + +2205 Thus the SCCP address of the roaming subscriber's HLR may be an SPC, or it may be a Global title consisting of the +2206 E.164 MSISDN or the E.164 number allocated to the HLR or either the E.214 Mobile Global Title derived from the +2207 IMSI if CCITT or ITU-T SCCP is used, or the IMSI if ANSI SCCP is used (ANSI SCCP is used in World Zone 1). + +#### 2208 6.1.3.3.4 VLR restoration + +2209 If a roaming number is requested by the HLR for an IMSI that has no data record in the interrogated VLR, the VLR +2210 provides the roaming number in the dialogue terminating message. Subsequently the VLR must retrieve the +2211 authentication data from the MS's HLR, if required, and must then trigger the restore data procedure. For this purpose, +2212 the VLR has to initiate in succession two independent dialogues with the MS's HLR. The MTP and SCCP address +2213 information needed for routeing towards the HLR can be derived from the IMSI received as a parameter of the MAP +2214 message requesting the roaming number. In this case, the IMSI received from the HLR in the roaming number request +2215 shall be processed in the same way as the IMSI that is received from an MS that registers for the first time within a +2216 VLR. Alternatively to the IMSI, the Calling Party Address associated with the roaming number request may be used to +2217 obtain the routeing information towards the HLR. + +#### 2218 6.1.3.3.5 During Network-Requested PDP Context Activation + +2219 When receiving a PDP PDU the GGSN may interrogate the HLR of the MS for information retrieval. When initiating +2220 such a dialogue, the only data for addressing the HLR that the GGSN has available is contained in the IMSI, and +2221 addressing information must be derived from it. The IMSI is obtained from the IP address or the X.25 address in the +2222 incoming IP message by means of a translation table. This means that the GGSN shall be able to address the HLR based +2223 on an E.214, (if CCITT or ITU-T SCCP is used), or E.212 (if ANSI SCCP is used), Mobile Global Title originally +2224 derived by the GGSN from the IMSI in the case of inter-PLMN signalling. In the case of intra-PLMN signalling, an +2225 SPC may also be used. + +2226 If the HLR is in the same PLMN as the GGSN, local translation tables may exist to derive an SPC. For information +2227 retrieval via the international PSTN/ISDN signalling network, the Global title must be derived from the IMSI, using the +2228 principles contained in CCITT Recommendation E.214 and the Numbering Plan Indicator (NPI) value referenced by the +2229 SCCP Specifications. A summary of the translation from the IMSI (CCITT Recommendation E.212) to Mobile Global +2230 Title (described in CCITT Recommendation E.214) is shown below: + +- 2231 - E.212 Mobile Country Code translates to E.164 Country Code; +- 2232 - E.212 Mobile Network Code translates to E.164 National Destination Code; +- 2233 - E.212 Mobile Subscriber Identification Number (MSIN) is carried unchanged if within the E.164 number +2234 maximum length (15 digits). If the Mobile Global Title is more than 15 digits the number is truncated to 15 by +2235 deleting the least significant digits. + +2236 This translation will be done either at the application or at SCCP level in the GGSN. The Mobile Global Title thus +2237 derived will be used to address the HLR. + +#### 2238 6.1.3.3.6 Before GPRS location updating completion + +2239 When an MS registers for the first time in an SGSN, the SGSN has to initiate the update location dialogue with the +2240 MS's HLR and a preceding dialogue for authentication information retrieval if the authentication information must be +2241 retrieved from the HLR. When initiating either of these dialogues, the only data for addressing the HLR that the SGSN +2242 has available is contained in the IMSI, and addressing information for SCCP must be derived from it. When continuing +2243 the established update location dialogue (as with any other dialogue), the SGSN must derive the routeing information +2244 towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the +2245 dialogue terminating message is received. This means that the SGSN must be able to address the HLR based on: + +- 2246 - an E.214 (if CCITT or ITU-T SCCP is used) or E.212 (if ANSI SCCP is used) Mobile Global Title originally +2247 derived by the SGSN from the IMSI; or + +2248 - an E.164 HLR address; or + +2249 - in the case of intra-PLMN signalling, an SPC. + +2250 If the HLR is in the same PLMN as the SGSN, local translation tables may exist to derive an SPC. For authentication +2251 information retrieval and location updating via the international PSTN/ISDN signalling network, the Global title must +2252 be derived from the IMSI, using the principles contained in CCITT Recommendation E.214 and the Numbering Plan +2253 Indicator (NPI) value referenced by the SCCP Specifications. A summary of the translation from the IMSI (CCITT +2254 Recommendation E.212) to Mobile Global Title (described in CCITT Recommendation E.214) is shown below: + +2255 - E.212 Mobile Country Code translates to E.164 Country Code; + +2256 - E.212 Mobile Network Code translates to E.164 National Destination Code; + +2257 - E.212 Mobile Subscriber Identification Number (MSIN) is carried unchanged if within the E.164 number +2258 maximum length (15 digits). If the Mobile Global Title is more than 15 digits the number is truncated to 15 by +2259 deleting the least significant digits. + +2260 This translation will be done either at the application or at SCCP level in the SGSN. The Mobile Global Title thus +2261 derived will be used to address the HLR. + +#### 2262 6.1.3.3.7 After GPRS location updating completion + +2263 In this case, the subscriber's Basic MSISDN has been received from the HLR during the subscriber data retrieval +2264 procedure as well as the HLR number constituting a parameter of the MAP message indicating successful completion of +2265 the update location dialogue. From either of these E.164 numbers the address information for initiating dialogues with +2266 the roaming subscriber's HLR can be derived. Also the subscriber's IMSI may be used for establishing the routeing +2267 information towards the HLR. + +2268 Thus the SCCP address of the roaming subscriber's HLR may be an SPC, or it may be a Global title consisting of the +2269 E.164 MSISDN or the E.164 number allocated to the HLR or the E.214 Mobile Global Title derived from the IMSI. + +#### 2270 6.1.3.3.8 Query for a Location Request + +2271 For a location request from an external client, the GMLC needs to address the home HLR of the target MS to obtain the +2272 address of the target MS's serving MSC. The GMLC uses either the international E.164 MSISDN, the international +2273 E.214 number (if CCITT or ITU-T SCCP is used) or the international E.212 number (if ANSI SCCP is used) of the MS +2274 as means to route a query to the HLR. + +### 2275 6.1.3.4 The Visitor Location Register (VLR) + +#### 2276 6.1.3.4.0 General + +2277 There are several cases when the VLR needs to be addressed. + +#### 2278 6.1.3.4.1 Inter-VLR information retrieval + +2279 When an MS moves from one VLR service area to another, the new VLR may request the IMSI and authentication sets +2280 from the previous VLR. The new VLR derives the address of the previous VLR from the Location Area Identification +2281 provided by the MS in the location registration request. + +#### 2282 6.1.3.4.2 HLR request + +2283 The HLR will only request information from a VLR if it is aware that one of its subscribers is in the VLR service area. +2284 This means that a location updating dialogue initiated by the VLR has been successfully completed, i.e. the HLR has +2285 indicated successful completion of the update location procedure to the VLR. + +2286 When initiating dialogues towards the VLR after successful completion of location updating, the routeing information +2287 used by the HLR is derived from the E.164 VLR number received as a parameter of the MAP message initiating the +2288 update location dialogue. If the VLR is in the same PLMN as the HLR, the VLR may be addressed directly by an SPC +2289 derived from the E.164 VLR number. For dialogues via the international PSTN/ISDN signalling network, presence of +2290 the E.164 VLR number in the Called Party Address is required. + +#### 2291 6.1.3.4.3 CSS request + +2292 The CSS will only request information from a VLR if it is aware that one of its subscribers is in the VLR service area. +2293 This means that a VCSG location updating dialogue initiated by the VLR has been successfully completed, i.e. the CSS +2294 has indicated successful completion of the update VCSG location procedure to the VLR. + +2295 When initiating dialogues towards the VLR after successful completion of VCSG location updating, the routeing +2296 information used by the CSS is derived from the E.164 VLR number received as a parameter of the MAP message +2297 initiating the update VCSG location dialogue. The VLR may be addressed either by the E.164 VLR number or directly +2298 by an SPC derived from the E.164 VLR number due to the VLR is in the same PLMN as the CSS. + +#### 2299 6.1.3.5 The Interworking MSC (IWMSC) for Short Message Service + +2300 The IWMSC is the interface between the mobile network and the network to access to the Short Message Service +2301 Centre. This exchange has an E.164 address known in the SGSN or in the MSC. + +#### 2302 6.1.3.6 The Equipment Identity Register (EIR) + +2303 The EIR address is either unique or could be derived from the IMEI. The type of address is not defined. + +#### 2304 6.1.3.7 Void + +#### 2305 6.1.3.8 The Serving GPRS Support Node (SGSN) + +##### 2306 6.1.3.8.0 General + +2307 There are several cases when the SGSN needs to be addressed. + +##### 2308 6.1.3.8.1 HLR request + +2309 The HLR will initiate dialogues towards the SGSN if it is aware that one of its subscribers is in the SGSN serving area. +2310 This means that a GPRS location updating has been successfully completed, i.e., the HLR has indicated successful +2311 completion of the GPRS location update to the SGSN. The routeing information used by the HLR is derived from the +2312 E.164 SGSN number received as parameter of the MAP message initiating the GPRS update location procedure. If the +2313 SGSN is in the same PLMN as the HLR, the SGSN may be addressed directly by an SPC derived from the E.164 SGSN +2314 number. For dialogues via the international PSTN/ISDN signalling network, the presence of the E.164 SGSN number in +2315 the Called Party Address is required. + +##### 2316 6.1.3.8.2 GMSC request + +2317 When the GMSC initiates dialogues towards the SGSN the SGSN (MAP) SSN (See 3GPP TS 23.003 [17]) shall be +2318 included in the called party address. The routeing information used by the GMSC is derived from the E.164 SGSN +2319 number received as a parameter of the MAP message initiating the forward short message procedure. If the GMSC does +2320 not support the GPRS functionality the MSC (MAP) SSN value shall be included in the called party address. + +2321 NOTE: Every VMSC and SGSN shall have uniquely identifiable application using E.164 numbers, for the +2322 purpose of SMS over GPRS when the GMSC does not support the GPRS functionality. + +##### 2323 6.1.3.8.3 CSS request + +2324 The CSS will initiate dialogues towards the SGSN if it is aware that one of its subscribers is in the SGSN serving area. +2325 This means that a VCSG location updating has been successfully completed, i.e., the CSS has indicated successful +2326 completion of the VCSG location update to the SGSN. The routeing information used by the CSS is derived from the +2327 E.164 SGSN number received as parameter of the MAP message initiating the update VCSG location procedure. The +2328 SGSN may be addressed either by the E.164 SGSN number or directly by an SPC derived from the E.164 SGSN +2329 number due to the SGSN is in the same PLMN as the CSS. + +#### 2330 6.1.3.9 The Gateway GPRS Support Node (GGSN) + +2331 The GGSN provides interworking with external packet-switched networks, network screens and routing of the +2332 Network-Requested PDP Context activation. If a Network-Requested PDP Context activation fails, the HLR will alert +2333 the GGSN when the subscriber becomes reachable. The HLR will use the E.164 GGSN number received as parameter +2334 of the MAP message reporting the failure. + +### 2335 6.1.3.10 The Gateway MSC (GMSC) for Short Message Service + +2336 The GMSC provides interworking with the network to access the Short Message Service Centre, the mobile network +2337 and routing of Send Routing Info For SM. The GMSC has an E.164 address known in the HLR, SGSN or MSC. + +2338 6.1.3.10A Void + +2339 6.1.3.10A.1 Void + +2340 6.1.3.10A.2 Void + +### 2341 6.1.3.10B The Gateway Mobile Location Centre (GMLC) + +2342 The GMLC initiates location requests on behalf of external clients. The E.164 address of the GMLC is provided to an +2343 HLR when the GMLC requests a serving MSC address or SGSN address from the HLR for a target MS. The E.164 +2344 address of the GMLC is also provided to a serving MSC or SGSN when the GMLC requests the location of a target MS +2345 served by this MSC or SGSN. + +### 2346 6.1.3.10C The CSG Subscriber Server (CSS) + +2347 The CSS address is either unique or could be derived from the IMSI. **The type of address is not defined.** + +### 2348 6.1.3.11 Summary table + +2349 The following tables summarise the SCCP address used for invoke operations. As a principle, within a PLMN either an +2350 SPC or a GT may be used (network operation option), whereas when addressing an entity outside the PLMN the GT +2351 must be used. The address type mentioned in the table (e.g. MSISDN) is used as GT or to derive the SPC. + +2352 For a response, the originating address passed in the invoke is used as SCCP Called Party Address. For extra-PLMN +2353 addressing the own E.164 entity address is used as SCCP Calling Party Address; for intra-PLMN addressing an SPC +2354 derived from the entity number may be used instead. When using an SPC, the SPC may be taken directly from MTP. + + + +| to
from | fixed
net
work | HLR | VLR | MSC | EIR | gsmSCF | SGSN | GGSN | CSS | +|------------------------------------------------------|----------------------|---------------------------------------------------------------------------------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|----------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------| +| fixed
network | --- | E:GT
T:MSISDN | --- | --- | --- | --- | --- | --- | --- | +| Home
Location
Register | --- | --- | I:SPC/GT
E:GT
T:VLR
NUMBER | --- | --- | I:SPC/GT
E:GT
T:gsmSCF
NUMBER | I:SPC/GT
E:GT
T:SGSN
NUMBER | I:SPC/GT
E:GT
T:GGSN
NUMBER | --- | +| Visitor
Location
Register | --- | I:SPC/GT
E:GT
T:MGT
(outside
World Zone
1)/MSISDN
(World Zone
1)/HLR
NUMBER
(note) | I:SPC/GT
E:GT
T:VLR
NUMBER | --- | --- | I:SPC/GT
E:GT
T:gsmSCF
NUMBER | --- | --- | I: SPC/GT
E:GT
T:CSS
NUMBER | +| mobile-
services
switching
centre | --- | I:SPC/GT
E:GT
T:MSISDN | I:SPC/GT
E:GT
T:VLR
NUMBER | I:SPC/GT
E:GT
T:MSC
NUMBER | I:SPC/GT
E:GT
T:EIR
NUMBER | I:SPC/GT
E:GT
T:gsmSCF
NUMBER | I:SPC/GT
E:GT
T:SGSN
NUMBER | --- | --- | +| gsm
Service
Control
Function | --- | I:SPC/GT
E:GT
T:MSISDN | --- | --- | --- | --- | --- | --- | --- | +| Serving
GPRS
Support
Node | --- | I:SPC/GT
E:GT
T:MGT/
MSISDN/
HLR
NUMBER | --- | I:SPC/GT
E:GT
T:MSC
NUMBER | I:SPC/GT
E:GT
T:EIR
NUMBER | I:SPC/GT
E:GT
T:gsmSCF
NUMBER | --- | --- | I:SPC/GT
E:GT
T:CSS
NUMBER | +| Gateway
GPRS
Support
Node | --- | I:SPC/GT
E:GT
T:MGT | --- | --- | --- | --- | --- | --- | --- | +| Gateway
Mobile
Location
Centre | --- | I:SPC/GT
E:GT
T:MSISDN,
MGT
(outside
World Zone
1) or IMSI
(World Zone
1)
(note) | --- | I:SPC/GT
E:GT
T:MSC
NUMBER | --- | --- | I:SPC/GT
E:GT
T:SGSN
NUMBER | --- | --- | +| CSG
Subscriber
Server | --- | --- | I:SPC/GT
E:GT
T:VLR
NUMBER | --- | --- | --- | I:SPC/GT
E:GT
T:SGSN
NUMBER | --- | --- | + +| | | +|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| I: | Intra-PLMN. | +| E: | Extra (Inter)-PLMN. | +| T: | Address Type. | +| GT: | Global Title. | +| MGT: | E.214 Mobile Global Title. | +| SPC: | Signalling Point Code. | +| NOTE: |

For initiating the location updating procedure and an authentication information retrieval from the HLR preceding it, the VLR has to derive the HLR address from the IMSI of the MS. The result can be an SPC or an E.214 Mobile Global Title if CCITT or ITU-T SCCP is used, or IMSI itself if ANSI SCCP is used (ANSI SCCP is used in World Zone 1). When continuing the established update location dialogue (as with any other dialogue) the VLR must derive the routeing information towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the dialogue terminating message is received.

For transactions invoked by the VLR after update location completion, the VLR may derive the information for addressing the HLR from addresses received in the course of the update location procedure (MSISDN or HLR number) or from the IMSI.

When invoking the Restore Data procedure and an authentication information retrieval from the HLR preceding it, the VLR must derive the information for addressing the HLR from the address information received in association with the roaming number request. This may be either the IMSI received as a parameter of the MAP message requesting the Roaming Number or the Calling Party Address associated with the MAP message requesting the Roaming Number.

The gsmSCF shall be addressed using more than one Global Title number. The first Global Title number is used to address a gsmSCF for MAP. The second Global Title number is used to address a gsmSCF for CAP.

For querying the HLR to obtain the VMSC address to support location services, the GMLC has to derive the HLR address from either the MSISDN or IMSI of the target MS. When using the IMSI, the result can be an SPC or an E.214 Mobile Global Title if CCITT or ITU-T SCCP is used, or IMSI itself if ANSI SCCP is used (ANSI SCCP is used in World Zone 1).

| + +2356 + +2357 + +**Table 6.1/2** + +| to
from | | GMLC | +|-----------------------------------------|----------------------------|----------------------------------| +| fixed network | | --- | +| Home Location Register | | --- | +| Visitor Location Register | | --- | +| Mobile-services Switching Centre | | I:SPC/GT
E:GT
T:MLC Number | +| gsm Service Control Function | | I:SPC/GT
E:GT
T:MSISDN | +| Serving GPRS Support Node | | I:SPC/GT
E:GT
T:MLC Number | +| Gateway GPRS Support Node | | --- | +| Gateway Mobile Location Centre | | | +| I: | Intra-PLMN. | | +| E: | Extra (Inter)-PLMN. | | +| T: | Address Type. | | +| GT: | Global Title. | | +| MGT: | E.214 Mobile Global Title. | | +| SPC: | Signalling Point Code. | | + +2358 + +## 2359 6.2 Use of TC + +2360 The Mobile Application part makes use of the services offered by the Transaction Capabilities (TC) of Signalling +2361 System No. 7. ETS 300 287, which is based on CCITT White Book Recommendations Q.771 to Q.775, should be +2362 consulted for the full specification of TC. + +2363 The MAP uses all the services provided by TC except the ones related to the unstructured dialogue facility. + +2364 From a modelling perspective, the MAP is viewed as a single Application Service Element. Further structuring of it is +2365 for further study. + +2366 Transaction Capabilities refers to a protocol structure above the network layer interface (i.e., the SCCP service +2367 interface) up to the application layer including common application service elements but not the specific application +2368 service elements using them. + +2369 TC is structured as a Component sub-layer above a Transaction sub-layer. + +2370 The Component sub-layer provides two types of application services: services for the control of end-to-end dialogues +2371 and services for Remote Operation handling. These services are accessed using the TC-Dialogue handling primitives +2372 and TC-Component handling primitives respectively. + +2373 Services for dialogue control include the ability to exchange information related to application-context negotiation as +2374 well as initialisation data. + +2375 Services for Remote Operation handling provide for the exchange of protocol data units invoking tasks (operations), +2376 and reporting their outcomes (results or errors) plus any non-application-specific protocol errors detected by the +2377 component sub-layer. The reporting of application-specific protocol errors by the TC user, as distinct from application +2378 process errors, is also provided. The Transaction sub-layer provides a simple end-to-end connection association service +2379 over which several related protocol data units (i.e. built by the Component Sub-Layer) can be exchanged. A Transaction +2380 termination can be prearranged (no indication provided to the TC user) or basic (indication provided). + +2381 + +--- + +## 2382 7 General on MAP services + +### 2383 7.1 Terminology and definitions + +2384 The term service is used in clauses 7 to 12 as defined in CCITT Recommendation X.200. The service definition +2385 conventions of CCITT Recommendation X.210 are also used. + +2386 MAP services that are defined for use between HLR and SGSN are also used in an Evolved Packet System (EPS) +2387 between two IWFs and between HSS and IWF, where the IWF is an Interworking Function that converts MAP +2388 messages to Diameter messages and vice versa. + +2389 MAP services that are defined for use between SGSN and EIR are also used in an Evolved Packet System (EPS) +2390 between IWF and EIR. + +2391 IWFs may be connected via Diameter to MMEs and HSSs and they may be connected via MAP to HSSs, IWFs, and +2392 EIRs. + +2393 + +### 2394 7.2 Modelling principles + +2395 MAP provides its users with a specified set of services and can be viewed by its users as a "black box" or abstract +2396 machine representing the MAP service-provider. The service interface can then be depicted as shown in figure 7.2/1. + +![Diagram illustrating the modelling principles of MAP. Two boxes labeled 'MAP service-user' are at the top, each connected by a vertical line to a central horizontal line labeled 'Service Interface'. Below the 'Service Interface' line, a single box labeled 'MAP Service-provider' is shown, connected to the interface by a vertical line.](89f8aefc01866631793087542316cef2_img.jpg) + +Diagram illustrating the modelling principles of MAP. Two boxes labeled 'MAP service-user' are at the top, each connected by a vertical line to a central horizontal line labeled 'Service Interface'. Below the 'Service Interface' line, a single box labeled 'MAP Service-provider' is shown, connected to the interface by a vertical line. + +2397 + +2398 + +**Figure 7.2/1: Modelling principles** + +2399 The MAP service-users interact with the MAP service-provider by issuing or receiving MAP service-primitives at the +2400 service interface. + +2401 A MAP service-user may receive services from several instances of the MAP service-provider at the same time. In such +2402 cases the overall procedure is synchronised by the service-user. + +2403 The MAP service-primitives are named using the following notation: + +| | +|--------------------------------------| +| MAP-ServicePrimitiveName type | +|--------------------------------------| + +2405 where **type** can be any of: request (req), indication (ind), response (rsp) or confirm (cnf). (In the user arrow diagrams +2406 type is not indicated in the case of req/ind and indicated as "ack" in the case of rsp/cnf). + +2407 The services are further classified as unconfirmed-service, confirmed-service and provider-initiated-service where the +2408 first two categories refer to whether or not the service is confirmed by the service-provider. The confirmation may or +2409 may not correspond to a response provided by the other service-user. + +2410 MAP services are also classified as common MAP services that are available to all MAP service-users, and MAP +2411 service-user specific services, which are services available to one or several, but not all, MAP service-users. + +2412 A MAP dialogue is defined as an exchange of information between two MAP users in order to perform a common task. +2413 A MAP dialogue will consist of one or several MAP services. + +## 2414 7.3 Common MAP services + +2415 All MAP service-users require access to services for performing basic application layer functions: + +- 2416 - for establishing and clearing MAP dialogues between peer MAP service-users; + +- 2417 - for accessing functions supported by layers below the applications layer; + +- 2418 - for reporting abnormal situations; + +- 2419 - for handling of different MAP versions; + +- 2420 - for testing whether or not a persistent MAP dialogue is still active at each side. + +2421 For these purposes the following common services are defined: + +- 2422 - MAP-OPEN service; + +- 2423 - MAP-CLOSE service; + +- 2424 - MAP-DELIMITER service; + +- 2425 - MAP-U-ABORT service; + +- 2426 - MAP-P-ABORT service; + +- 2427 - MAP-NOTICE service. + +2428 In defining the service-primitives the following convention is used for categorising parameters: + +- 2429 M the inclusion of the parameter is mandatory. The M category can be used for any primitive type and specifies +2430 that the corresponding parameter must be present in the indicated primitive type; +- 2431 O the inclusion of the parameter is a service-provider option. The O category can be used in indication and +2432 confirm type primitives and is used for parameters that may optionally be included by the service-provider; +- 2433 U the inclusion of the parameter is a service-user option. The U category can be used in request and response +2434 type primitives. The inclusion of the corresponding parameter is the choice of the service-user; +- 2435 C the inclusion of the parameter is conditional. The C category can be used for the following purposes: +- 2436 - to indicate that if the parameter is received from another entity it must be included for the service being +2437 considered; + - 2438 - to indicate that the service user must decide whether to include the parameter, based on the context on +2439 which the service is used; + - 2440 - to indicate that one of a number of mutually exclusive parameters must be included (e.g. parameters +2441 indicating a positive result versus parameters indicating a negative result); + - 2442 - to indicate that a service user optional parameter (marked "U") or a conditional parameter (marked "C") +2443 presented by the service user in a request or response type primitive is to be presented to the service user in +2444 the corresponding indication or confirm type primitive; +- 2445 (=) when appended to one of the above, this symbol means that the parameter takes the same value as the +2446 parameter appearing immediately to its left; +- 2447 blank the parameter is not present. +- 2448 A primitive type may also be without parameters, i.e. no parameter is required with the primitive type; in this case the +2449 corresponding column of the table is empty. + +### 2450 7.3.1 MAP-OPEN service + +2451 This service is used for establishing a MAP dialogue between two MAP service-users. The service is a confirmed +2452 service with service primitives as shown in table 7.3/1. + +2453 **Table 7.3/1: Service-primitives for the MAP-OPEN service** + +| Parameters | Request | Indication | Response | Confirm | +|--------------------------|---------|------------|----------|---------| +| Application context name | M | M(=) | U | C(=) | +| Destination address | M | M(=) | | | +| Destination reference | U | C(=) | | | +| Originating address | U | O | | | +| Originating reference | U | C(=) | | | +| Specific information | U | C(=) | U | C(=) | +| Responding address | | | U | C(=) | +| Result | | | M | M(=) | +| Refuse-reason | | | C | C(=) | +| Provider error | | | | O | + +2454 + +#### 2455 Application context name: + +2456 This parameter identifies the type of application context being established. If the dialogue is accepted the received +2457 application context name shall be echoed. In case of refusal of dialogue this parameter shall indicate the highest version +2458 supported. + +#### 2459 Destination address: + +2460 A valid SCCP address identifying the destination peer entity (see also clause 6). As an implementation option, this +2461 parameter may also, in the indication, be implicitly associated with the service access point at which the primitive is +2462 issued. + +#### 2463 Destination-reference: + +2464 This parameter is a reference that refines the identification of the called process. It may be identical to Destination + 2465 address but its value is to be carried at MAP level. Table 7.3/2 describes the MAP services using this parameter. Only + 2466 these services are allowed to use it. + +2467 + +**Table 7.3/2: Use of the destination reference** + +| MAP service | Reference type | Use of the parameter | +|-------------------------------------|----------------|----------------------| +| MAP-REGISTER-SS | IMSI | Subscriber identity | +| MAP-ERASE-SS | IMSI | Subscriber identity | +| MAP-ACTIVATE-SS | IMSI | Subscriber identity | +| MAP-DEACTIVATE-SS | IMSI | Subscriber identity | +| MAP-INTERROGATE-SS | IMSI | Subscriber identity | +| MAP-REGISTER-PASSWORD | IMSI | Subscriber identity | +| MAP-PROCESS-UNSTRUCTURED-SS-REQUEST | IMSI (note 1) | Subscriber identity | +| MAP-UNSTRUCTURED-SS-REQUEST | IMSI (note 2) | Subscriber identity | +| MAP-UNSTRUCTURED-SS-NOTIFY | IMSI (note 2) | Subscriber identity | +| MAP-FORWARD-SHORT-MESSAGE | IMSI (note 3) | Subscriber identity | +| MAP-REGISTER-CC-ENTRY | IMSI | Subscriber identity | +| MAP-ERASE-CC-ENTRY | IMSI | Subscriber identity | + +2468 + +2469 NOTE 1: On the HLR - HLR interface and on the HLR - gsmSCF interface the Destination reference shall be either + 2470 IMSI or MSISDN. + +2471 NOTE 2: On the gsmSCF - HLR interface and on the HLR - HLR interface the Destination reference shall be either + 2472 IMSI or MSISDN. + +2473 + +2474 NOTE 3: Only when the IMSI and the LMSI are received together from the HLR in the mobile terminated short + 2475 message transfer. + +2476 Originating address: + +2477 A valid SCCP address identifying the requestor of a MAP dialogue (see also clause 6). As an implementation option, + 2478 this parameter may also, in the request, be implicitly associated with the service access point at which the primitive is + 2479 issued. + +2480 Originating-reference: + +2481 This parameter is a reference that refines the identification of the calling process. It may be identical to the Originating + 2482 address but its value is to be carried at MAP level. Table 7.3/3 describes the MAP services using the parameter. Only + 2483 these services are allowed to use it. Processing of the Originating-reference shall be performed according to the + 2484 supplementary service descriptions and other service descriptions, e.g. operator determined barring. Furthermore the + 2485 receiving entity may be able to use the value of the Originating-reference to screen the service indication. + +**Table 7.3/3: Use of the originating reference** + +| MAP service | Reference type | Use of the parameter | +|-------------------------------------|----------------------------|-----------------------------| +| MAP-REGISTER-SS | ISDN-Address-String | Originated entity address | +| MAP-ERASE-SS | ISDN-Address-String | Originated entity address | +| MAP-ACTIVATE-SS | ISDN-Address-String | Originated entity address | +| MAP-DEACTIVATE-SS | ISDN-Address-String | Originated entity address | +| MAP-INTERROGATE-SS | ISDN-Address-String | Originated entity address | +| MAP-REGISTER-PASSWORD | ISDN-Address-String | Originated entity address | +| MAP-PROCESS-UNSTRUCTURED-SS-REQUEST | ISDN-Address-String | Originated entity address | +| MAP-UNSTRUCTURED-SS-REQUEST | ISDN-Address-String (note) | Originated entity address | +| MAP-UNSTRUCTURED-SS-NOTIFY | ISDN-Address-String (note) | Originated entity address | +| MAP-REGISTER-CC-ENTRY | ISDN-Address-String | Originated entity address | +| MAP-ERASE-CC-ENTRY | ISDN-Address-String | Originated entity address | + +2487 + +2488 NOTE: The Originating reference may be omitted. + +2489 Specific information: + +2490 This parameter may be used for passing any user specific information. Establishment and processing of the Specific +2491 information is not specified by GSM and shall be performed according to operator specific requirements. + +2492 Responding address: + +2493 An address identifying the responding entity. The responding address is included if required by the context (e.g. if it is +2494 different from the destination address). + +2495 Result: + +2496 This parameter indicates whether the peer accepts the dialogue. + +2497 Refuse reason: + +2498 This parameter is present only if the Result parameter indicates that the dialogue is refused. It takes one of the following +2499 values: + +- 2500 - Application-context-not-supported; +- 2501 - Invalid-destination-reference; +- 2502 - Invalid-originating-reference; +- 2503 - No-reason-given; +- 2504 - Remote node not reachable; +- 2505 - Potential version incompatibility. + +## 7.3.2 MAP-CLOSE service + +This service is used for releasing a previously established MAP dialogue. The service may be invoked by either MAP service-user depending on rules defined within the service-user. The service is an unconfirmed service with parameters as shown in table 7.3/4. + +**Table 7.3/4: Service-primitives for the MAP-CLOSE service** + +| Parameters | Request | Indication | +|----------------------|---------|------------| +| Release method | M | | +| Specific Information | U | C(=) | + +2511 + +### Release method: + +This parameter can take the following two values: + +- normal release; in this case the primitive is mapped onto the protocol and sent to the peer; +- prearranged end; in this case the primitive is not mapped onto the protocol. Prearranged end is managed independently by the two users, i.e. only the request type primitive is required in this case. + +### Specific information: + +This parameter may be used for passing any user specific information. Establishment and processing of the Specific information is not specified by GSM GSM and shall be performed according to operator specific requirements. + +## 7.3.3 MAP-DELIMITER service + +This service is used to explicitly request the transfer of the MAP protocol data units to the peer entities. + +See also clause 7.4 and 7.5 for the detailed use of the MAP-DELIMITER service. + +The service is an unconfirmed service with service-primitives as shown in table 7.3/5. + +**Table 7.3/5: Service-primitives for the MAP-DELIMITER service** + +| Parameters | Request | Indication | +|------------|---------|------------| +| | | | +| | | | + +2525 + +## 7.3.4 MAP-U-ABORT service + +This service enables the service-user to request the MAP dialogue to be aborted. The service is an unconfirmed service with service-primitives as shown in table 7.3/6. + +**Table 7.3/6: Service-primitives for the MAP-U-ABORT service** + +| Parameters | Request | Indication | +|------------------------|---------|------------| +| User reason | M | M(=) | +| Diagnostic information | U | C(=) | +| Specific information | U | C(=) | + +2530 + +### User reason: + +This parameter can take the following values: + +- resource limitation (congestion); +the requested user resource is unavailable due to congestion; +- resource unavailable; + +- 2536 the requested user resource is unavailable for reasons other than congestion; +- 2537 - application procedure cancellation; +- 2538 the procedure is cancelled for reasons detailed in the diagnostic information parameter; +- 2539 - procedure error; +- 2540 processing of the procedure is terminated for procedural reasons. + +2541 Diagnostic information: + +2542 This parameter may be used to give additional information for some of the values of the user-reason parameter: + +2543 **Table 7.3/7: User reason and diagnostic information** + +| User reason | Diagnostic information | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Resource limitation (congestion) | - | +| Resource unavailable | Short term/long term problem | +| Application procedure cancellation | Handover cancellation/
Radio Channel release/
Network path release/
Call release/
Associated procedure failure/
Tandem dialogue released/
Remote operations failure | +| Procedure error | - | + +2544 + +2545 Specific information: + +2546 This parameter may be used for passing any user specific information. Establishment and processing of the Specific +2547 information is not specified by GSM and shall be performed according to operator specific requirements. + +## 2548 7.3.5 MAP-P-ABORT service + +2549 This service enables the MAP service-provider to abort a MAP dialogue. The service is a provider-initiated service with +2550 service-primitives as shown in table 7.3/8. + +2551 **Table 7.3/8: Service-primitives for the MAP-P-ABORT service** + +| Parameters | | Indication | +|-----------------|--|------------| +| Provider reason | | M | +| Source | | M | + +2552 + +2553 Provider reason: + +2554 This parameter indicates the reason for aborting the MAP dialogue: + +- 2555 - provider malfunction; +- 2556 - supporting dialogue/transaction released; +- 2557 - resource limitation; +- 2558 - maintenance activity; +- 2559 - version incompatibility; +- 2560 - abnormal MAP dialogue. + +2561 Source: + +2562 This parameter indicates the source of the abort. For Transaction Capabilities (TC) applications the parameter may take +2563 the following values: + +- 2564 - MAP problem; + 2565 - TC problem; + 2566 - network service problem. + +2567 **Table 7.3/9: Values of provider reason and source parameters** + 2568 **and examples of corresponding events** + +| Provider reason | Source | Corresponding event | +|----------------------------------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Provider | MAP | Malfunction at MAP level at peer entity | +| malfunction | TC | "Unrecognised message type" or
"Badly formatted transaction portion" or
"Incorrect transaction portion" received in TC-P-ABORT
"Abnormal dialogue" | +| | Network service | Malfunction at network service level at peer entity | +| Supporting dialogue/
transaction released | TC | "Unrecognised transaction ID" received in TC-ABORT | +| Resource | MAP | Congestion towards MAP peer service-user | +| limitation | TC | "Resource limitation" received in TC-P-ABORT | +| Maintenance | MAP | Maintenance at MAP peer service-user | +| activity | Network service | Maintenance at network peer service level | +| Abnormal MAP
dialogue | MAP | MAP dialogue is not in accordance with specified
application context | +| Version
incompatibility | TC | A Provider Abort indicating "No common dialogue portion"
is received in the dialogue initiated state | + +2569 + +### 2570 7.3.6 MAP-NOTICE service + +2571 This service is used to notify the MAP service-user about protocol problems related to a MAP dialogue not affecting the + 2572 state of the protocol machines. + +2573 The service is a provider-initiated service with service-primitive as shown in table 7.3/10. + +2574 **Table 7.3/10: Service-primitive for the MAP-NOTICE service** + +| Parameters | Indication | +|--------------------|------------| +| Problem diagnostic | M | + +2575 + +2576 Problem diagnostic: + +2577 This parameter can take one of the following values: + +- 2578 - abnormal event detected by the peer; + 2579 - response rejected by the peer; + 2580 - abnormal event received from the peer; + 2581 - message cannot be delivered to the peer. + +2582 7.3.7 Void + +2583 7.3.8 Void + +2584 7.3.9 Void + +2585 7.3.10 Void + +## 2586 7.4 Sequencing of services + +2587 The sequencing of services is shown in figure 7.4/1 and is as follows: + +### 2588 Opening: + +2589 The MAP-OPEN service is invoked before any user specific service-primitive is accepted. The sequence may +2590 contain none, one or several user specific service-primitives. If no user specific service-primitive is contained +2591 between the MAP-OPEN and the MAP-DELIMITER primitives, then this will correspond to sending an +2592 empty Begin message in TC. If more than one user specific service-primitive is included, all are to be sent in +2593 the same Begin message. The sequence ends with a MAP-DELIMITER primitive. + +### 2594 Continuing: + +2595 This sequence may not be present in some MAP dialogues. If it is present, it ends with a MAP-DELIMITER +2596 primitive. If more than one user specific service-primitive is included, all are to be included in the same +2597 Continue message. + +### 2598 Closing: + +2599 The sequence can only appear after an opening sequence or a continuing sequence. The sequence may +2600 contain none, one or several user specific service-primitives if the MAP-CLOSE primitive specifies normal +2601 release. If no user specific service-primitive is included, then this will correspond to sending an empty End +2602 message in TC. If more than one user specific service-primitive is included, all are to be sent in the same End +2603 message. If prearranged end is specified, the sequence cannot contain any user specific service-primitive. The +2604 MAP-CLOSE primitive must be sent after all user specific service-primitives have been delivered to the +2605 MAP service-provider. + +### 2606 Aborting: + +2607 A MAP service-user can issue a MAP-U-ABORT primitive at any time after the MAP dialogue has been +2608 opened or as a response to an attempt to open a MAP dialogue. + +2609 The MAP service-provider may issue at any time a MAP-P-ABORT primitive towards a MAP service-user for which a +2610 MAP dialogue exists. + +2611 MAP-U-ABORT primitives and MAP-P-ABORT primitives terminate the MAP dialogue. + +![Diagram showing the sequencing of services for the 'Opening' phase. It consists of three boxes: 'MAP-OPEN' on the left, 'User specific service-primitive' in the center, and 'MAP-DELIMITER' on the right. Lines connect 'MAP-OPEN' to the central box, and the central box to 'MAP-DELIMITER'. Below the central box, a long line with a left-pointing arrow indicates a return or response path from the 'MAP-DELIMITER' back towards the 'MAP-OPEN' side.](0629ebd517a3f52337d7d1087e06e07b_img.jpg) + +``` + +graph LR + A[MAP-OPEN] --> B[User specific service-primitive] + B --> C[MAP-DELIMITER] + C --> D[ ] + style D fill:none,stroke:none + D -.-> A + +``` + +Diagram showing the sequencing of services for the 'Opening' phase. It consists of three boxes: 'MAP-OPEN' on the left, 'User specific service-primitive' in the center, and 'MAP-DELIMITER' on the right. Lines connect 'MAP-OPEN' to the central box, and the central box to 'MAP-DELIMITER'. Below the central box, a long line with a left-pointing arrow indicates a return or response path from the 'MAP-DELIMITER' back towards the 'MAP-OPEN' side. + +2612 + +2613 + +**a) Opening** + +2614 +2615 + +![Diagram showing the sequencing of services for 'Continuing'. A 'User specific service-primitive' box is shown with a return arrow pointing to it from a 'MAP-DELIMITER' box. Above the 'User specific service-primitive' box, there are two nested boxes representing previous service primitives.](feae5a5b6e128162dbced0860fd97b9b_img.jpg) + +Diagram showing the sequencing of services for 'Continuing'. A 'User specific service-primitive' box is shown with a return arrow pointing to it from a 'MAP-DELIMITER' box. Above the 'User specific service-primitive' box, there are two nested boxes representing previous service primitives. + +**b) Continuing** + +2616 +2617 + +![Diagram showing the sequencing of services for 'Closing'. A 'User specific service-primitive' box is shown with a return arrow pointing to it from a 'MAP-CLOSE' box. Above the 'User specific service-primitive' box, there is one nested box representing a previous service primitive.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +Diagram showing the sequencing of services for 'Closing'. A 'User specific service-primitive' box is shown with a return arrow pointing to it from a 'MAP-CLOSE' box. Above the 'User specific service-primitive' box, there is one nested box representing a previous service primitive. + +**c) Closing** + +2618 +2619 + +![Diagram showing the sequencing of services for 'Aborting'. Two boxes, 'MAP-U-ABORT' and 'MAP-P-ABORT', are shown side-by-side with horizontal lines leading to them from the left and right respectively.](9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg) + +Diagram showing the sequencing of services for 'Aborting'. Two boxes, 'MAP-U-ABORT' and 'MAP-P-ABORT', are shown side-by-side with horizontal lines leading to them from the left and right respectively. + +**d) Aborting** + +2620 + +**Figure 7.4/1: Sequencing of services** + +2621 If the reason "resource unavailable (short term problem)" is indicated in the MAP-U-ABORT indication primitive, the +2622 MAP service-user may decide to attempt a new MAP dialogue establishment immediately. + +2623 Sequencing of user specific service-primitives is done by the MAP service-user and based on rules applicable for each +2624 MAP service-user instance. + +2625 A MAP-NOTICE indication primitive may be received at any time during the active period of a MAP dialogue. + +## 2626 7.5 General rules for mapping of services onto TC + +### 2627 7.5.1 Mapping of common services + +2628 Table 7.5/1 gives an overview of the mapping rules for mapping of common services onto TC-services. Table 7.5/2 +2629 gives the mapping rules for mapping of TC-services onto common services. + +2630 Protocol machine description is given in clauses 14 to 17. + +2631 + +**Table 7.5/1: Mapping of common services onto TC services** + +| MAP service-primitive | TC service-primitive | +|------------------------------------------------------------------------------------------|-----------------------------------------------------------------| +| MAP-OPEN request
(+ any user specific service primitives)
+ MAP-DELIMITER request | TC-BEGIN request
(+ component handling primitives) | +| MAP-OPEN response
(+ any user specific service primitives)
+ MAP-DELIMITER request | TC-CONTINUE request (note)
(+ component handling primitives) | +| (any user specific service primitives)
+ MAP-DELIMITER request | TC-CONTINUE request
(+ component handling primitives) | +| (any user specific service primitives)
+ MAP-CLOSE request | TC-END request
(+ component handling primitives) | + +| | | +|----------------------------------------------------------------------------------------------|--------------------| +| MAP-U-ABORT request | TC-U-ABORT request | +| NOTE: Or TC-END if the MAP-CLOSE request has been received before the MAP-DELIMITER request. | | + +2632 + +2633 + +**Table 7.5/2: Mapping of TC services onto common service** + +| TC service-primitive | MAP service-primitive | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TC-BEGIN indication
(+ component handling primitives) | MAP-OPEN indication
(+ user specific service primitives)
+ MAP-DELIMITER indication (note 1) | +| TC-CONTINUE indication
(+ component handling primitives) | First time:
MAP-OPEN confirm
(+ user specific service primitives)
+ MAP-DELIMITER indication (note 1)

Subsequent times:
(user specific service primitives)
+ MAP-DELIMITER indication (note 1) | +| TC-END indication
(+ component handling primitives) | MAP-OPEN confirm (note 6)
(user specific service primitives)
+ MAP-CLOSE indication | +| TC-U-ABORT indication | MAP-U-ABORT indication or
MAP-P-ABORT indication (note 2)
MAP-OPEN confirmation (note 3) | +| TC-P-ABORT indication | MAP-P-ABORT indication (note 4)
MAP-OPEN confirmation (note 5) | +| NOTE 1: It may not be necessary to present this primitive to the user for MAP version 2 applications. | | +| NOTE 2: The mapping depends on whether the TC-U-ABORT indication primitive contains a MAP-abort-PDU from the remote MAP service-provider or a MAP-user-abort-PDU from the remote MAP service-user. | | +| NOTE 3: Only if the opening sequence is pending and if the "Abort Reason" in the TC-U-ABORT indication is set to "Application Context Not Supported". | | +| NOTE 4: If the "Abort Reason" in the TC-P-ABORT indication is set to a value different from "Incorrect Transaction Portion". | | +| NOTE 5: Only if the opening sequence is pending and if the "Abort Reason" in the TC-P-ABORT indication is set to "Incorrect Transaction Portion". | | +| NOTE 6: Only if opening sequence is pending. | | + +2634 + +## 2635 7.5.2 Mapping of user specific services + +2636 Table 7.5/3 gives the general mapping rules which apply to mapping of MAP user specific services onto TC services +2637 and table 7.5/4 gives the similar rules for mapping of TC services onto MAP user specific services. Detailed mapping is +2638 given in clauses 14 to 17. + +2639 + +**Table 7.5/3: Mapping of MAP user specific services onto TC services** + +| MAP service-primitive | TC-service-primitive | +|-----------------------------|------------------------------------------------------------------------------------------------| +| MAP-xx request | TC-INVOKE request | +| MAP-xx response
(note 1) | TC-RESULT-L request
TC-U-ERROR request
TC-U-REJECT request
TC-INVOKE request (note 2) | + +2640 + +2641 + +**Table 7.5/4: Mapping of TC services onto MAP user specific services** + +| TC-service-primitive | MAP service-primitive | +|-------------------------------------------------------------------------------------------|-----------------------| +| TC-INVOKE indication | MAP-xx indication | +| TC-RESULT-L indication (note 4)
TC-U-ERROR indication
TC-INVOKE indication (note 2) | MAP-xx confirm | + +| | | +|------------------------|--------------------------------| +| TC-L-CANCEL indication | | +| TC-U-REJECT indication | MAP-xx confirm or | +| TC-L-REJECT indication | MAP-NOTICE indication (note 3) | +| TC-R-REJECT indication | | + +2642 + +2643 Notes to tables 7.5/3 and 7.5/4: + +2644 NOTE 1: The mapping is determined by parameters contained in the MAP-xx response primitive. + +2645 NOTE 2: This applies only to TC class 4 operations where the operation is used to pass a result of another class 2 + 2646 or class 4 operation. + +2647 NOTE 3: The detailed mapping rules are given in clause 16. + +2648 NOTE 4: If RESULT-NL components are present they are mapped onto the same MAP-xx confirm. + +## 2649 7.6 Definition of parameters + +### 2650 7.6.1 Common parameters + +2651 The following set of parameters is used in several MAP service-primitives. + +#### 2652 7.6.1.1 Invoke Id + +2653 This parameter identifies corresponding service primitives. The parameter is supplied by the MAP service-user and + 2654 must be unique over each service-user/service-provider interface. + +#### 2655 7.6.1.2 Linked Id + +2656 This parameter is used for linked services and it takes the value of the invoke Id of the service linked to. + +#### 2657 7.6.1.3 Provider error + +2658 This parameter is used to indicate a protocol related type of error: + +- 2659 - duplicated invoke Id; +- 2660 - not supported service; +- 2661 - mistyped parameter; +- 2662 - resource limitation; +- 2663 - initiating release, i.e. the peer has already initiated release of the dialogue and the service has to be released; +- 2664 - unexpected response from the peer; +- 2665 - service completion failure; +- 2666 - no response from the peer; +- 2667 - invalid response received. + +#### 2668 7.6.1.4 User error + +2669 This parameter can take values as follows: + +2670 NOTE: The values are grouped in order to improve readability; the grouping has no other significance. + +2671 a) Generic error: + +- 2672 - system failure, i.e. a task cannot be performed because of a problem in the entity reporting the error or in +2673 another entity. The type of entity or network resource may be indicated by use of the network resource +2674 parameter or additional network resource parameter. If and only if the problem is in the entity reporting the +2675 error, a cause of failure (FailureCauseParam) shall be included; +- 2676 - data missing, i.e. an optional parameter required by the context is missing; +- 2677 - unexpected data value, i.e. the data type is formally correct but its value or presence is unexpected in the +2678 current context; +- 2679 - resource limitation; +- 2680 - initiating release, i.e. the receiving entity has started the release procedure; +- 2681 - facility not supported, i.e. the requested facility is not supported by the PLMN with detailed reasons as +2682 follows: + - 2683 - Shape of location estimate not supported; + - 2684 - Needed LCS capability not supported in serving node; +- 2685 - incompatible terminal, i.e. the requested facility is not supported by the terminal. +- 2686 b) Identification or numbering problem: + - 2687 - unknown subscriber, i.e. no such subscription exists; + - 2688 - number changed, i.e. the subscription does not exist for that number any more; + - 2689 - unknown MSC; + - 2690 - unidentified subscriber, i.e. if the subscriber is not contained in the database and it has not or cannot be +2691 established whether or not a subscription exists; + - 2692 - unallocated roaming number; + - 2693 - unknown equipment; + - 2694 - unknown location area. +- 2695 c) Subscription problem: + - 2696 - roaming not allowed, i.e. a location updating attempt is made in an area not covered by the subscription; + - 2697 - illegal subscriber, i.e. illegality of the access has been established by use of authentication procedure; + - 2698 - bearer service not provisioned; + - 2699 - teleservice not provisioned; + - 2700 - illegal equipment, i.e. the IMEI check procedure has shown that the IMEI is prohibited-listed or not +2701 permitted-listed. +- 2702 d) Handover problem: + - 2703 - no handover number available, i.e. the VLR cannot allocate a number for handover or cannot allocate the +2704 required amount of numbers for relocation; + - 2705 - subsequent handover failure, i.e. handover to a third MSC failed for some reason; + - 2706 - target cell outside group call area. +- 2707 e) Operation and maintenance problem: + - 2708 - tracing buffer full, i.e. tracing cannot be performed because the tracing capacity is exceeded. +- 2709 f) Call set-up problem: + +- 2710 - no roaming number available, i.e. a roaming number cannot be allocated because all available numbers are in +2711 use; +- absent subscriber, i.e. the subscriber has activated the detach service or the system detects the absence condition. This error may be qualified to indicate whether the subscriber was IMSI detached, in a restricted area or did not respond to paging; +- 2712 - busy subscriber. This error may be qualified to indicate that the subscriber was busy due to CCBS and that +2713 CCBS is possible; +- 2714 - no subscriber reply; +- 2715 - forwarding violation, i.e. the call has already been forwarded the maximum number of times that is allowed; +- 2716 - CUG reject, i.e. the call does not pass a CUG check; additional information may also be given in order to +2717 indicate rejection due to e.g. incoming call barred or non-CUG membership; +- 2718 - call barred. Optionally, additional information may be included for indicating either that the call meets a +2719 barring condition set by the subscriber or that the call is barred for operator reasons. In the case of barring of +2720 Mobile Terminating Short Message, the additional information may indicate a barring condition due to +2721 "Unauthorised Message Originator"; if the call is rejected due to the application of the ACR supplementary +2722 service, the additional information shall indicate a barring condition due to "Anonymous Call Rejection"; +- 2723 - optimal routeing not allowed, i.e. the entity which sends the error does not support optimal routeing, or the +2724 HLR will not accept an optimal routeing interrogation from the GMSC, or the call cannot be optimally routed +2725 because it would contravene optimal routeing constraints; +- 2726 - forwarding failed, i.e. the GMSC interrogated the HLR for forwarding information but the HLR returned an +2727 error. + +2728 g) Supplementary services problem: + +- 2729 - call barred; +- 2730 - illegal SS operation; +- 2731 - SS error status; +- 2732 - SS not available; +- 2733 - SS subscription violation; +- 2734 - SS incompatibility; +- 2735 - negative password check; +- 2736 - password registration failure; +- 2737 - Number of Password Attempts; +- 2738 - USSD Busy; +- 2739 - Unknown Alphabet; +- 2740 - short term denial; +- 2741 - long term denial. + +2742 For definition of these errors see 3GPP TS 24.080 [38]. + +2743 h) Short message problem: + +- 2744 - SM delivery failure with detailed reason as follows: +- 2745 - memory capacity exceeded; +- 2746 - MS protocol error; + +- 2747 - MS not equipped; +- 2748 - unknown service centre (SC); +- 2749 - SC congestion; +- 2750 - invalid SME address; +- 2751 - subscriber is not an SC subscriber; +- 2752 - and possibly detailed diagnostic information, coded as specified in 3GPP TS 23.040, under SMS- +- 2753 SUBMIT-REPORT and SMS-DELIVERY-REPORT. If the SM entity that returns the SM Delivery +- 2754 Failure error includes detailed diagnostic information, it shall be forwarded in the +- 2755 MAP\_MO\_FORWARD\_SHORT\_MESSAGE and in the MAP\_MT\_FORWARD\_SHORT\_MESSAGE +- 2756 response. +- 2757 - message waiting list full, i.e. no further SC address can be added to the message waiting list. +- 2758 - Subscriber busy for MT SMS, i.e. the mobile terminated short message transfer cannot be completed +- 2759 because: +- 2760 - another mobile terminated short message transfer is going on and the delivery node does not support +- 2761 message buffering; or +- 2762 - another mobile terminated short message transfer is going on and it is not possible to buffer the message +- 2763 for later delivery; or +- 2764 - the message was buffered but it is not possible to deliver the message before the expiry of the buffering +- 2765 time defined in 3GPP TS 23.040; +- Absent Subscriber SM, i.e. the mobile terminated short message transfer cannot be completed because the network cannot contact the subscriber. Diagnostic information regarding the reason for the subscriber's absence may be included with this error. +- 2766 i) Location services problem: +- 2767 - Unauthorised Requesting Network +- 2768 - Unauthorised LCS Client with detailed reasons as follows: +- 2769 - NoAdditional Information +- 2770 - Client not in MS Privacy Exception List +- 2771 - Call to Client not setup +- 2772 - Disallowed by Local Regulatory Requirements +- 2773 - Unauthorised Privacy Class +- 2774 - Unauthorised Call/Session Unrelated External Client +- 2775 - Unauthorised Call/Session Related External Client +- 2776 - Privacy override not applicable +- 2777 - Position method failure with detailed reasons as follows: +- 2778 - Congestion +- 2779 - Insufficient resources +- 2780 - Insufficient Measurement Data +- 2781 - Inconsistent Measurement Data +- 2782 - Location procedure not completed + +- 2783 - QoS not attainable +- 2784 - Position Method Not Available in Network +- 2785 - Position Method Not Available in Location Area +- 2786 - Unknown or unreachable LCS Client. + +#### 2787 7.6.1.5 All Information Sent + +2788 This parameter indicates to the receiving entity when the sending entity has sent all necessary information. + +### 2789 7.6.2 Numbering and identification parameters + +#### 2790 7.6.2.1 IMSI + +2791 This parameter is the International Mobile Subscriber Identity defined in 3GPP TS 23.003 [17]. + +#### 2792 7.6.2.2 TMSI + +2793 This parameter is the Temporary Mobile Subscriber Identity defined in 3GPP TS 23.003 [17]. + +#### 2794 7.6.2.3 IMEI + +2795 This parameter is the International Mobile Equipment Identity defined in 3GPP TS 23.003 [17]. + +#### 2796 7.6.2.3a IMEISV + +2797 This parameter is the International Mobile Equipment Identity and Software Version Number defined in 3GPP TS +2798 23.003 [17]. + +#### 2799 7.6.2.4 Previous location area Id + +2800 This parameter refers to the identity of the location area from which the subscriber has roamed. + +#### 2801 7.6.2.5 Stored location area Id + +2802 This parameter refers to the location area where the subscriber is assumed to be located. + +#### 2803 7.6.2.6 Current location area Id + +2804 This parameter is used to indicate the location area in which the subscriber is currently located. + +#### 2805 7.6.2.7 Target location area Id + +2806 This parameter refers to the location area into which the subscriber intends to roam. + +#### 2807 7.6.2.8 Target cell Id + +2808 This parameter refers to the identity of the cell to which a call has to be handed over. + +#### 2809 7.6.2.8A Target RNC Id + +2810 This parameter refers to the identity of the RNC to which a call has to be relocated. + +#### 2811 7.6.2.9 Void + +2812 **7.6.2.10        Originating entity number** + +2813 This parameter refers to an application layer identification of a system component in terms of its associated ISDN +2814 number. + +2815 **7.6.2.11        MSC number** + +2816 This parameter refers to the ISDN number of an MSC. + +2817 **7.6.2.12        Target MSC number** + +2818 This parameter refers to the ISDN number of an MSC to which a call has to be handed over. + +2819 **7.6.2.13        HLR number** + +2820 This parameter refers to the ISDN number of an HLR. + +2821 **7.6.2.14        VLR number** + +2822 This parameter refers to the ISDN number of a VLR. + +2823 **7.6.2.15        HLR Id** + +2824 This parameter refers to the identity of an HLR derived from the IMSI defined in CCITT Recommendation E.212. + +2825 **7.6.2.16        LMSI** + +2826 This parameter refers to a local identity allocated by the VLR to a given subscriber for internal management of data in +2827 the VLR. LMSI shall not be sent to the SGSN. + +2828 **7.6.2.17        MS ISDN** + +2829 This parameter refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with CCITT +2830 Recommendation E.213. + +2831 **7.6.2.17A      Additional MSISDN** + +2832 This parameter refers to an ISDN number assigned on top of the existing MSISDN, to a user with a connection to the +2833 PS domain (see 3GPP TS 23.003 [17]). If the Additional MSISDN is available its value shall be used as C-MSISDN on +2834 the Sv interface. + +2835 **7.6.2.18        OMC Id** + +2836 This parameter refers to the identity of an Operation and Maintenance Centre. + +2837 **7.6.2.19        Roaming number** + +2838 This parameter refers to the roaming number as defined in CCITT Recommendation E.213. + +2839 **7.6.2.19A      Relocation Number List** + +2840 This parameter refers to the number(s) used for routing one call or several calls between MSCs during relocation. + +2841 **7.6.2.20        Void** + +2842 **7.6.2.21        Handover number** + +2843 This parameter refers to the number used for routing a call between MSCs during handover. + +2844 **7.6.2.22 Forwarded-to number** + +2845 This parameter refers to the address to which a call is to be forwarded. A subaddress may be appended. For subscribers +2846 having an originating CAMEL Phase 2 or higher subscription, this address need not be in E.164 international format. + +2847 **7.6.2.22A Long forwarded-to number** + +2848 This parameter refers to the address to which a call is to be forwarded. A subaddress may be appended. For subscribers +2849 having an originating CAMEL Phase 2 or higher subscription this address need not be in international format. + +2850 **7.6.2.22B Long FTN Supported** + +2851 This parameter indicates that the sending entity supports Long Forwarded-to Numbers. + +2852 **7.6.2.23 Forwarded-to subaddress** + +2853 This parameter refers to the sub-address attached to the address to which a call is to be forwarded. + +2854 **7.6.2.24 Called number** + +2855 This parameter refers to a called party number as defined in CCITT Recommendation Q.767. + +2856 **7.6.2.25 Calling number** + +2857 This parameter refers to a calling party number as defined in CCITT Recommendation Q.767. + +2858 **7.6.2.26 Originally dialled number** + +2859 This parameter refers to the number dialled by the calling party in order to reach a mobile subscriber. + +2860 **7.6.2.27 Service centre address** + +2861 This parameter represents the address of a Short Message Service Centre. + +2862 **7.6.2.28 Zone Code** + +2863 This parameter is used to define location areas into which the subscriber is allowed or not allowed to roam (regional +2864 subscription). With a complete list of Zone Codes the VLR or the SGSN or MME is able to determine for all its location +2865 areas, routing areas or tracking areas whether roaming is allowed or not. + +2866 **7.6.2.29 MSISdn-Alert** + +2867 This parameter refers to the MSISDN stored in a Message Waiting Data File in the HLR. It is used to alert the Service +2868 Centre when the MS is again attainable. + +2869 **7.6.2.30 Location Information** + +2870 The VLR indicates in this parameter the location of the served subscriber as defined in 3GPP TS 23.018 [97]. + +2871 **7.6.2.30a Location Information for GPRS** + +2872 The SGSN indicates in this parameter the location of the served subscriber as defined in 3GPP TS 23.078 [98]. + +2873 **7.6.2.30b Location Information for EPS** + +2874 The MME (via an IWF) indicates in this parameter the location of the served subscriber. + +2875 **7.6.2.31 GMSC Address** + +2876 This parameter refers to the E.164 address of a GMSC. + +2877 **7.6.2.32 VMSC Address** + +2878 This parameter refers to the E.164 address of a VMSC. + +2879 **7.6.2.33 Group Id** + +2880 This parameter is used to describe groups a subscriber can be a member of. A subscriber can partake in all group calls +2881 (VBS/VGCS) where he subscribed to the respective groups. + +2882 **7.6.2.34 North American Equal Access preferred Carrier Id** + +2883 This parameter refers to the carrier identity preferred by the subscriber for calls requiring routing via an inter-exchange +2884 carrier. This identity is used at: + +- 2885 - outgoing calls: when the subscriber does not specify at call set-up a carrier identity; +- 2886 - forwarded calls: when a call is forwarded by the subscriber; +- 2887 - incoming calls: applicable to the roaming leg of the call. + +2888 **7.6.2.35 Void** + +2889 **7.6.2.36 Void** + +2890 **7.6.2.37 Serving cell Id** + +2891 This parameter indicates the cell currently being used by the served subscriber. + +2892 **7.6.2.38 SGSN number** + +2893 This parameter refers to the ISDN number of a SGSN. + +2894 **7.6.2.39 SGSN address** + +2895 This parameter refers to the IP-address of a SGSN. This parameter is defined in 3GPP TS 23.003 [17]. + +2896 **7.6.2.40 GGSN address** + +2897 This parameter refers to the IP-address of a GGSN. This parameter is defined in 3GPP TS 23.003 [17]. + +2898 **7.6.2.41 GGSN number** + +2899 This parameter refers to the ISDN number of a GGSN or the ISDN number of the protocol-converter if a +2900 protocol-converting GSN is used between the GGSN and the HLR. + +2901 **7.6.2.42 APN** + +2902 This parameter refers to the DNS name of a GGSN. This parameter is defined in 3GPP TS 23.060 [104]. + +#### 2903 7.6.2.43 Network Node number + +2904 This parameter refers to the ISDN number of an MT-SMS target node (MSC or MME, SGSN, or IP-SM-GW) or of an +2905 SMS Router. + +#### 2906 7.6.2.43A Network Node Diameter Address + +2907 This parameter refers to the Diameter Name and Realm of the same MT-SMS target node or SMS Router of which the +2908 ISDN number is within the Network Node number parameter. + +#### 2909 7.6.2.44 PDP-Type + +2910 This parameter indicates which type of protocol is used by the MS as defined in 3GPP TS 23.060 [104]. The allowed +2911 values are one of IPv4 encoded as HEX (21) or IPv6 encoded as HEX (57), or Non-IP encoded as HEX (02). + +2912 NOTE: To indicate both IPv4 and IPv6 PDP types are allowed, but not IPv4v6, two PDP contexts need to be +2913 present in the subscription for the same APN, one indicating IPv4 PDP type and one indicating IPv6 PDP +2914 type. + +2915 + +#### 2916 7.6.2.44A Extension PDP-Type + +2917 This parameter indicates the support of the dual-stack PDP-type (IPv4v6) encoded as HEX (8D) by a certain PDP, as +2918 defined in 3GPP TS 23.060 [104], and it is an extension to PDP-Type. + +#### 2919 7.6.2.45 PDP-Address + +2920 This parameter indicates the address of the data protocol as defined in 3GPP TS 23.060 [104]. + +#### 2921 7.6.2.45A Extension PDP-Address + +2922 This parameter indicates an additional address of the data protocol, and it is included when the PDP supports dual-stack +2923 (IPv4v6). + +2924 It is an extension to PDP-Address and it is encoded in the same way. IPv4 or IPv6 address types can be used in this +2925 parameter but, when both parameters are present, each of them shall contain different address types. + +#### 2926 7.6.2.46 Additional number + +2927 This parameter refers to the ISDN number of an additional MT-SMS target node (MSC or MME or SGSN) or of an +2928 SMS Router. + +#### 2929 7.6.2.46A Additional Network Node Diameter Address + +2930 This parameter refers to an additional Diameter Name and Realm of the same MT-SMS target node or SMS Router of +2931 which the ISDN number is within the Additional number parameter. + +#### 2932 7.6.2.46B Third Number + +2933 This parameter refers to the ISDN number of a third MT-SMS target node (MSC or MME or SGSN). + +#### 2934 7.6.2.46C Third Network Node Diameter Address + +2935 This parameter refers to the third Diameter Name and Realm of the same MT-SMS target node of which the ISDN +2936 number is within the Third number parameter. + +#### 2937 7.6.2.47 P-TMSI + +2938 This parameter is the Packet Temporary Mobile Subscriber Identity defined in 3GPP TS 23.003 [17]. + +2939 **7.6.2.48 B-subscriber number** + +2940 This parameter refers to the number of the destination B dialled by the A user. This may include a subaddress. + +2941 **7.6.2.49 B-subscriber subaddress** + +2942 This parameter refers to the sub-address attached to the destination B dialled by the A user. + +2943 **7.6.2.50 LMU Number** + +2944 This parameter refers to a local number assigned to an LMU by an SMLC. + +2945 **7.6.2.51 MLC Number** + +2946 This parameter refers to the ISDN (E.164) number of an MLC. + +2947 **7.6.2.52 Multicall Bearer Information** + +2948 This parameter refers to the number of simultaneous bearers supported per user by the serving network. + +2949 **7.6.2.53 Multiple Bearer Requested** + +2950 This parameter indicates whether multiple bearers are requested for a relocation. + +2951 **7.6.2.54 Multiple Bearer Not Supported** + +2952 This parameter indicates whether multiple bearers are supported. + +2953 **7.6.2.55 PDP-Charging Characteristics** + +2954 This parameter indicates the charging characteristics associated with a specific PDP context as defined in 3GPP +2955 TS 32.215. + +2956 **7.6.2.56 Selected RAB ID** + +2957 The selected radio access bearer to be kept at subsequent inter-MSC handover from UMTS to GSM. + +2958 **7.6.2.57 RAB ID** + +2959 This parameter indicates the radio access bearer identifier as defined in 3GPP TS 25.413. This parameter is used to +2960 relate the radio resources with the radio access bearers. + +2961 **7.6.2.58 gsmSCF Address** + +2962 This parameter refers to the ISDN number assigned to the gsmSCF address. In an IP Multimedia Core Network, the +2963 gsmSCF-address shall contain the IM-SSF address when the IM-SSF takes the role of the gsmSCF. + +2964 **7.6.2.59 V-GMLC Address** + +2965 This parameter refers to the IP address of a V-GMLC. + +2966 **7.6.2.60 Void** + +2967 **7.6.2.61 H-GMLC Address** + +2968 This parameter refers to the IP address of a H-GMLC. + +#### 2969 **7.6.2.62 PPR Address** + +2970 This parameter refers to the IP address of a Privacy Profile Register. + +#### 2971 **7.6.2.63 Routeing Number** + +2972 This parameter refers to a number used for routeing purpose and identifying a network operator. See 3GPP TS 23.066 +2973 [108]. + +#### 2974 **7.6.2.64 Additional V-GMLC Address** + +2975 This parameter refers to the IP address of a V-GMLC. + +#### 2976 **7.6.2.65 MME Name** + +2977 This parameter refers to the Diameter Identity of an MME as defined in 3GPP TS 23.003 [17]. + +#### 2978 **7.6.2.66 3GPP AAA Server Name** + +2979 This parameter refers to the Diameter Identity of a 3GPP AAA server as defined in 3GPP TS 29.273 [151]. + +#### 2980 **7.6.2.67 CSS number** + +2981 This parameter refers to the ISDN number of a CSS as defined in 3GPP TS 23.003[17]. + +#### 2982 **7.6.2.68 SGSN Name** + +2983 This parameter refers to the Diameter Identity of an SGSN as defined in 3GPP TS 23.003 [17]. + +#### 2984 **7.6.2.69 SGSN Realm** + +2985 This parameter refers to the Diameter Identity of an SGSN as defined in 3GPP TS 23.003 [17]. + +### 2986 **7.6.3 Subscriber management parameters** + +#### 2987 **7.6.3.1 Category** + +2988 This parameter refers to the calling party category as defined in CCITT Recommendation Q.767. + +#### 2989 **7.6.3.2 Equipment status** + +2990 This parameter refers to the status of the mobile equipment as defined in 3GPP TS 22.016 [7]. + +#### 2991 **7.6.3.2a BMUEF** + +2992 This parameter refers to the Bit Map of UE Faults and corresponds to the UESBI-Iu parameter defined in 3GPP TS +2993 25.413 [120]. + +#### 2994 **7.6.3.3 Extensible Bearer service** + +2995 This parameter may refer to a single bearer service, a set of bearer services or to all bearer services as defined in 3GPP +2996 TS 22.002 [3]. This parameter is used only for subscriber profile management. Extensible Bearer service values include +2997 all values defined for a Bearer service parameter (7.6.4.38). + +#### 2998 **7.6.3.4 Extensible Teleservice** + +2999 This parameter may refer to a single teleservice, a set of teleservices or to all teleservices as defined in 3GPP TS 22.003 + 3000 [4]. This parameter is used only for subscriber profile management. Extensible Teleservice values include all values + 3001 defined for a Teleservice parameter (7.6.4.39). + +3002 **7.6.3.5 Extensible Basic Service Group** + +3003 This parameter refers to the Basic Service Group either as an extensible bearer service (see clause 7.6.3.3) or an + 3004 extensible teleservice (see clause 7.6.3.4). This parameter is used only for subscriber profile management. The null + 3005 value (i.e. neither extensible bearer service nor extensible teleservice) is used to denote the group containing all + 3006 extensible bearer services and all extensible teleservices. + +3007 **7.6.3.6 GSM bearer capability** + +3008 This parameter refers to the GSM bearer capability information element defined in 3GPP TS 24.008 [35]. + +3009 **7.6.3.7 Subscriber Status** + +3010 This parameter refers to the barring status of the subscriber: + +- 3011 - service granted; +- 3012 - Operator Determined Barring. + +3013 **7.6.3.8 CUG Outgoing Access indicator** + +3014 This parameter represents the Outgoing Access as defined in ETS 300 136. + +3015 **7.6.3.9 Operator Determined Barring General Data** + +3016 This parameter refers to the set of subscriber features that the network operator or the service provider can regulate. + 3017 This set only includes those limitations that can be + +- 3018 a) controlled in the VLR, +- 3019 b) controlled in the SGSN or MME, +- 3020 c) controlled in the SGSN applied for short message transfer only, +- 3021 d) interrogated or modified by the gsmSCF: + +3022 + +| ODB category | Controlled in the VLR | Controlled in the SGSN or MME | Controlled in the SGSN applied for short message transfer only | Interrogatable and modifiable by the gsmSCF | +|---------------------------------------------------------------------------|-----------------------|-------------------------------|----------------------------------------------------------------|---------------------------------------------| +| All outgoing calls barred | X | | X | X | +| International outgoing calls barred | X | | X | X | +| International outgoing calls except those to the home PLMN country barred | X | | X | X | +| Interzonal outgoing calls barred | X | | X | X | +| Interzonal outgoing calls except those to the home PLMN country | X | | X | X | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| barred | | | | | +| Interzonal outgoing calls AND international outgoing calls except those directed to the home PLMN country barred | X | | X | X | +| Premium rate (information) outgoing calls barred | X | | | X | +| Premium rate (entertainment) outgoing calls barred | X | | | X | +| Supplementary service access barred | X | | | X | +| Invocation of call transfer barred | X | | | X | +| Invocation of chargeable call transfer barred | X | | | X | +| Invocation of internationally chargeable call transfer barred | X | | | X | +| Invocation of interzonally chargeable call transfer barred | X | | | X | +| Invocation of call transfer where both legs are chargeable barred | X | | | X | +| Invocation of call transfer if there is already an ongoing transferred call for the served subscriber in the serving MSC/VLR barred | X | | | X | +| All packet Oriented Services barred | | X | | X | +| Roamer Access to HPLMN-AP barred | | X | | X | +| Roamer Access to VPLMN-AP barred | | X | | X | +| Outgoing calls when roaming outside the home PLMN country | | | | X | +| All incoming calls | | | | X | + +| | | | | | +|--------------------------------------------------------------------------------------------------------|--|--|--|---| +| Incoming calls when roaming outside the home PLMN country | | | | X | +| Incoming calls when roaming outside the zone of the home PLMN country | | | | X | +| Roaming outside the home PLMN | | | | X | +| Roaming outside the home PLMN country | | | | X | +| Registration of any call forwarded-to number | | | | X | +| Registration of any international call forwarded-to number | | | | X | +| Registration of any international call forwarded-to number except to a number within the HPLMN country | | | | X | +| Registration of any inter-zone call forwarded-to number | | | | X | +| Registration of any inter-zone call forwarded-to number except to a number within the HPLMN country | | | | X | + +3023 + +3024 + +3025 **7.6.3.10 ODB HPLMN Specific Data** + +3026 This parameter refers to the set of subscriber features that the network operator or the service provider can regulate only + 3027 when the subscriber is registered in the HPLMN. This set only includes those limitations that can be controlled in the + 3028 VLR or in the SGSN or MME: + +- 3029 - Operator Determined Barring Type 1; +- 3030 - Operator Determined Barring Type 2; +- 3031 - Operator Determined Barring Type 3; +- 3032 - Operator Determined Barring Type 4. + +3033 **7.6.3.11 Regional Subscription Data** + +3034 This parameter defines the regional subscription area in which the subscriber is allowed to roam. It consists of a list of + 3035 Zone Codes (see clause 7.6.2.28). + +### 3036 7.6.3.12 Regional Subscription Response + +3037 This parameter indicates either that the regional subscription data cannot be handled or that the current MSC or SGSN +3038 or MME area is entirely restricted because of regional subscription. + +### 3039 7.6.3.13 Roaming Restriction Due To Unsupported Feature + +3040 This parameter defines that a subscriber is not allowed to roam in the current MSC area. It may be used by the HLR if a +3041 feature or service is indicated as unsupported by the VLR. + +### 3042 7.6.3.14 Extensible SS-Info + +3043 This parameter refers to all the information related to a supplementary service and is a choice between: + +- 3044 - extensible forwarding information (see clause 7.6.3.15); +- 3045 - extensible call barring information (see clause 7.6.3.20); +- 3046 - CUG info (see clause 7.6.3.22); +- 3047 - extensible SS-Data (see clause 7.6.3.29). + +### 3048 7.6.3.15 Extensible forwarding information + +3049 This parameter represents the information related to each call forwarding service: + +- 3050 - the SS-Code of the relevant call forwarding service (see clause 7.6.4.1); +- 3051 - if required, a list of extensible forwarding feature parameters (see clause 7.6.3.16). + +3052 The list may contain one item per Basic Service Group. + +### 3053 7.6.3.16 Extensible forwarding feature + +3054 This parameter applies to each combination of call forwarding service and Basic Service Group and contains the +3055 following information, as required: + +- 3056 - extensible Basic Service Group (see clause 7.6.3.5); +- 3057 - extensible SS-Status (see clause 7.6.3.17); +- 3058 - forwarded-to number (see clause 7.6.2.22); +- 3059 - forwarded-to subaddress (see clause 7.6.2.23); +- 3060 - extensible forwarding options (see clause 7.6.3.18); +- 3061 - extensible no reply condition timer (see clause 7.6.4.19); +- 3062 - long forwarded-to number (see clause 7.6.2.22A). + +3063 If a number is required to define the forwarded-to destination then: + +- 3064 - If the VLR supports Long Forwarded-to Numbers then the long forwarded-to number shall be present and the +3065 forwarded-to number shall be absent; +- 3066 - If the VLR does not support Long Forwarded-to Numbers then the forwarded-to number shall be present and the +3067 long forwarded-to number shall be absent. + +### 3068 7.6.3.17 Extensible SS-Status + +3069 This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011 [22]. + +### 3070 7.6.3.18 Extensible Forwarding Options + +3071 This parameter refers to a set of forwarding options attached to a supplementary service. It contains the following +3072 information: + +- 3073 - notification to forwarding party (see 3GPP TS 22.082 [10] for the meaning of this +3074 parameter); +- 3075 - redirection notification to the forwarded-to party (see 3GPP TS 22.082 [10] for the meaning of this +3076 parameter); +- 3077 - notification to calling party (see 3GPP TS 22.082 [10] for the meaning of this +3078 parameter); +- 3079 - redirecting presentation (see 3GPP TS 22.082 [10] for the meaning of this +3080 parameter); +- 3081 - forwarding reason (see 3GPP TS 22.082 [10] for the meaning of this +3082 parameter). + +### 3083 7.6.3.19 Extensible No reply condition timer + +3084 This parameter refers to the extensible no reply condition timer for call forwarding on no reply. + +### 3085 7.6.3.20 Extensible Call barring information + +3086 This parameter contains for each call barring service: + +- 3087 - SS-Code (see clause 7.6.4.1); +- 3088 - a list of extensible call barring feature parameters (see clause 7.6.3.21). + +3089 The list may contain one item per Basic Service Group. + +### 3090 7.6.3.21 Extensible Call barring feature + +3091 This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter +3092 contains the following information: + +- 3093 - Extensible Basic Service Group (see clause 7.6.3.5); +- 3094 - provisioned SS-Status (see clause 7.6.3.17). + +### 3095 7.6.3.22 CUG info + +3096 This parameter refers to the overall information required for operation for each CUG: + +- 3097 - CUG subscriptionList; +- 3098 - CUG featureList. + +### 3099 7.6.3.23 CUG subscription + +3100 This parameter refers to the set of basic information for each CUG defined in that subscription. The following +3101 information is stored: + +- 3102 - CUG index; +- 3103 - CUG interlock; +- 3104 - Intra CUG restrictions; +- 3105 - Basic Service Group List. + +#### 3106 7.6.3.24 CUG interlock + +3107 This parameter represents the CUG interlock code defined in ETS 300 138. + +#### 3108 7.6.3.25 CUG index + +3109 This parameter represents the CUG index defined in ETS 300 138. + +#### 3110 7.6.3.26 CUG feature + +3111 This parameter contains two parameters that are associated with the Basic Service Group. If the Basic Service Group +3112 Code is not present the feature applies to all Basic Services. The following parameters are included: + +- 3113 - Preferential CUG indicator: + - 3114 - indicates which CUG index is to be used at outgoing call set-up using the associated Basic Service Group; +- 3115 - Inter CUG Option: + - 3116 - describes whether it for the associated Basic Service Group is allowed to make calls outside the CUG and +3117 whether incoming calls are allowed; +- 3118 - Basic Service Group. + +3119 See 3GPP TS 22.085 [13] for meaning of this parameter. + +#### 3120 7.6.3.27 Inter CUG options + +3121 This parameter indicates the subscribers' ability to make and receive calls outside a specific closed user group. It takes +3122 any of the following values: + +- 3123 - CUG only facility (only calls within CUG are allowed); +- 3124 - CUG with outgoing access (calls outside CUG allowed); +- 3125 - CUG with incoming access (calls from outside CUG into CUG allowed); +- 3126 - CUG with both incoming and outgoing access (all calls allowed). + +#### 3127 7.6.3.28 Intra CUG restrictions + +3128 This parameter describes whether or not the subscriber is allowed to originate calls to or to receive calls from within the +3129 CUG. It can take any of the following values: + +- 3130 - no CUG restrictions; +- 3131 - CUG incoming calls barred; +- 3132 - CUG outgoing calls barred. + +#### 3133 7.6.3.29 Extensible SS-Data + +3134 This parameter refers to the necessary set of information required in order to characterise one supplementary service: + +- 3135 - SS-Code (see clause 7.6.4.1); +- 3136 - Extensible SS-Status (if applicable) (see clause 7.6.3.17); +- 3137 - Extensible Override subscription option (if applicable) (see clause 7.6.3.30); +- 3138 - Extensible CLI Restriction (if applicable) (see clause 7.6.3.31); +- 3139 - Extensible Basic Service Group Code (see clause 7.6.3.5). + +3140 **7.6.3.30 Subscriber State** + +3141 This parameter indicates the state of the MS as defined in 3GPP TS 23.018 [97]. + +3142 **7.6.3.31 Requested Info** + +3143 This parameter indicates the subscriber information being requested as defined in 3GPP TS 23.018 [97] and 3GPP +3144 TS 23.078 [98]. + +3145 **7.6.3.31A Requested Domain** + +3146 This parameter indicates the domain (circuit switched, i.e. from the MSC/VLR, or packet switched, i.e. from the SGSN) +3147 from which the requested information should be retrieved. + +3148 **7.6.3.32 Suppression of Announcement** + +3149 This parameter indicates if the announcement or tones shall be suppressed as defined in 3GPP TS 23.078 [98]. + +3150 **7.6.3.33 Suppress T-CSI** + +3151 This parameter is used to suppress the invocation of terminating CAMEL services. + +3152 **7.6.3.34 GMSC CAMEL Subscription Info** + +3153 This parameter contains CAMEL subscription information, i.e. O-CSI and/or D-CSI and/or T-CSI, which indicates to +3154 the GMSC that originating and/or terminating CAMEL services shall be invoked for the incoming call. + +3155 **7.6.3.35 VLR CAMEL Subscription Info** + +3156 This parameter identifies the subscriber as having CAMEL services that are invoked in the MSC or VLR. + +3157 **7.6.3.36 Supported CAMEL Phases in the VLR** + +3158 This parameter indicates which phases of CAMEL are supported in the VLR. + +3159 **7.6.3.36A Supported CAMEL Phases in the SGSN** + +3160 This parameter indicates which phases of CAMEL are supported in the SGSN. + +3161 **7.6.3.36B Offered CAMEL4 CSIs in the VLR** + +3162 This parameter indicates which CSIs of CAMEL phase 4 are offered in the VLR as defined in 3GPP TS 23.078. + +3163 **7.6.3.36C Offered CAMEL4 CSIs in the SGSN** + +3164 This parameter indicates which CSIs of CAMEL phase 4 are offered in the SGSN as defined in 3GPP TS 23.078. + +3165 **7.6.3.36D Offered CAMEL4 CSIs** + +3166 This parameter indicates which CSIs of CAMEL phase 4 are offered as defined in 3GPP TS 23.078. + +3167 **7.6.3.36E Offered CAMEL4 CSIs in interrogating node** + +3168 This parameter indicates which CSIs of CAMEL phase 4 are offered in the GMSC or in the gsmSCF as defined in +3169 3GPP TS 23.078. + +3170 **7.6.3.36F Offered CAMEL4 CSIs in VMSC** + +3171 This parameter indicates which CSIs of CAMEL phase 4 are offered in the VMSC as defined in 3GPP TS 23.078. + +#### 3172 **7.6.3.36G Offered CAMEL4 Functionalities** + +#### 3173 **7.6.3.36H Supported CAMEL Phases** + +3174 This parameter indicates which phases of CAMEL are supported as defined in 3GPP TS 23.078. + +#### 3175 **7.6.3.36I Supported CAMEL Phases in interrogating node** + +3176 This parameter indicates which phases of CAMEL are supported as defined in 3GPP TS 23.078. The interrogating node +3177 may be a GMSC or a gsmSCF. + +3178 This parameter indicates which functionalities of CAMEL phase 4 are offered as defined in 3GPP TS 23.078. + +#### 3179 **7.6.3.37 CUG Subscription Flag** + +3180 This parameter indicates that a subscriber with a T-CSI also has a CUG subscription. It is defined in 3GPP TS 23.078. + +#### 3181 **7.6.3.38 CAMEL Subscription Info Withdraw** + +3182 This parameter indicates that CAMEL Subscription Info shall be deleted from the VLR or SGSN. + +#### 3183 **7.6.3.39 Voice Group Call Service (VGCS) Data** + +3184 This parameter refers to one or more groups a subscriber may be a member of for voice group calls. + +#### 3185 **7.6.3.40 Voice Broadcast Service (VBS) Data** + +3186 This parameter refers to one or more groups a subscriber may be a member of for the voice broadcast service. Per group +3187 it is further indicated whether the subscriber is only allowed to listen to respective group calls or whether he is in +3188 addition entitled to initiate respective voice broadcast calls. + +#### 3189 **7.6.3.41 ISDN bearer capability** + +3190 This parameter refers to the ISDN bearer capability information element defined in 3GPP TS 29.007 [56]. + +#### 3191 **7.6.3.42 Lower layer Compatibility** + +3192 This parameter refers to the lower layer compatibility information element defined in 3GPP TS 24.008 [35]. + +#### 3193 **7.6.3.43 High Layer Compatibility** + +3194 This parameter refers to the high layer compatibility information element defined in 3GPP TS 24.008 [35]. + +#### 3195 **7.6.3.44 Alerting Pattern** + +3196 This parameter is an indication that can be used by the MS to alert the user in a specific manner in case of mobile +3197 terminating traffic (switched call or USSD). That indication can be an alerting level or an alerting category. + +#### 3198 **7.6.3.45 GPRS Subscription Data Withdraw** + +3199 This parameter indicates that GPRS Subscription Data shall be deleted from the SGSN. + +#### 3200 **7.6.3.45A EPS Subscription Data Withdraw** + +3201 This parameter indicates that EPS Subscription Data shall be deleted from the MME. + +#### 3202 7.6.3.46 GPRS Subscription Data + +3203 This parameter refers to the list of PDP-Contexts the subscriber has subscribed to. + +#### 3204 7.6.3.46A EPS Subscription Data + +3205 This parameter refers to the list of APN-Configurations the subscriber has subscribed to. + +#### 3206 7.6.3.47 QoS-Subscribed + +3207 This parameter indicates the quality of service subscribed for a certain service. It is defined in 3GPP TS 23.060 [104]. + +#### 3208 7.6.3.48 VPLMN address allowed + +3209 This parameter specifies whether the MS is allowed to use a dynamic address allocated in the VPLMN. It is defined in +3210 3GPP TS 23.060 [104]. + +#### 3211 7.6.3.49 Roaming Restricted In SGSN/MME Due To Unsupported Feature + +3212 This parameter defines that a subscriber is not allowed to roam in the current SGSN or MME area. It may be used by +3213 the HLR if a feature or service is indicated as unsupported by the SGSN or MME. + +#### 3214 7.6.3.50 Network Access Mode + +3215 This parameter is defined in 3GPP TS 23.008 [20]. + +#### 3216 7.6.3.51 Mobile Not Reachable Reason + +3217 This parameter stores the reason for the MS being absent when an attempt to deliver a short message to an MS fails at +3218 the MSC, SGSN or both. It is defined in 3GPP TS 23.040. + +#### 3219 7.6.3.52 Cancellation Type + +3220 This parameter indicates the reason of location cancellation. It is defined in 3GPP TS 23.060 [104]. The HLR shall not +3221 send Cancel Location with a Cancellation Type of "initialAttachProcedure" to the SGSN unless the SGSN has indicated +3222 support of this cancellation type within UpdateGprsLocation or the HLR has enough knowledge that the SGSN supports +3223 "initialAttachProcedure". If the HLR needs to send a cancellation type of "initialAttachProcedure" but cannot do so due +3224 to non-support by the SGSN, the HLR shall send Cancel Location with a Cancellation Type of "updateProcedure" and +3225 delete the stored SGSN-Number. + +#### 3226 7.6.3.53 All GPRS Data + +3227 This parameter indicates to the SGSN that all GPRS Subscription Data shall be deleted for the subscriber. + +#### 3228 7.6.3.54 Complete Data List Included + +3229 This parameter indicates to the SGSN or MME that the complete GPRS Subscription Data/EPS Subscription Data +3230 stored for the Subscriber shall be replaced with the GPRS Subscription Data/EPS Subscription Data received. + +#### 3231 7.6.3.55 PDP Context Identifier + +3232 This parameter is used to identify a PDP context for the subscriber. + +#### 3233 7.6.3.56 LSA Information + +3234 This parameter refers to one or more localised service areas a subscriber may be a member of, together with the priority, +3235 the preferential access indicator, the active mode support indicator and active mode indication of each localised service +3236 area. The access right outside these localised service areas is also indicated. + +### 3237 7.6.3.57 SoLSA support indicator + +3238 This parameter indicates that the VLR or the SGSN supports SoLSA subscription. + +### 3239 7.6.3.58 LSA Information Withdraw + +3240 This parameter indicates that LSA information shall be deleted from the VLR or the SGSN. + +### 3241 7.6.3.59 LMU Indicator + +3242 This parameter indicates the presence of an LMU. + +### 3243 7.6.3.60 LCS Information + +3244 This parameter defines the LCS related information for an MS subscriber and contains the following components: + +- 3245 - GMLC List (see clause 7.6.3.61). +- 3246 - LCS Privacy Exception List (see clause 7.6.3.62). +- 3247 - MO-LR List (see clause 7.6.3.65A). +- 3248 - Additional LCS Privacy Exception List (see clause 7.6.3.62A). + +3249 + +### 3250 7.6.3.61 GMLC List + +3251 This parameter contains the addresses of all GMLCs that are permitted to issue a call/session unrelated or call/session +3252 related MT-LR location request for this MS. Usage of this parameter is defined in 3GPP TS 23.271. + +### 3253 7.6.3.62 LCS Privacy Exception List + +3254 This parameter defines the classes of LCS Client that are allowed to locate any target MS. For each class, the following +3255 information is provided: + +- 3256 - SS-Code (see clause 7.6.4.1); +- 3257 - a list of LCS privacy exception parameters (see clause 7.6.3.63). + +### 3258 7.6.3.62A Additional LCS Privacy Exception List + +3259 This parameter defines the classes of LCS Client that are allowed to locate any target MS. For each class, the following +3260 information is provided: + +- 3261 - SS-Code (see clause 7.6.4.1); +- 3262 - a list of LCS privacy exception parameters (see clause 7.6.3.63). + +3263 The Additional LCS Privacy Exception List shall be present only if the LCS Privacy Exception List is present and +3264 contains LCS privacy exception parameters for 4 privacy exception classes. + +### 3265 7.6.3.63 LCS Privacy Exception Parameters + +3266 This parameter gives the status of each LCS privacy exception class and any additional parameters relevant to this class. +3267 The parameter contains the following information: + +- 3268 - provisioned SS-Status (see clause 7.6.3.17); +- 3269 - privacy notification to MS user (see clause 7.6.3.65B); +- 3270 - external client List (see clause 7.6.3.64); + +- 3271 - internal client List (see clause 7.6.3.65). +3272 - service type List (see clause 7.6.3.65D); +3273 + +#### 3274 7.6.3.64 External Client List + +3275 This parameter is only applicable to the call/session unrelated privacy class and call/session related privacy class, and +3276 gives the identities of the external clients that are allowed to locate a target MS for a MT-LR. Each identity is an +3277 international (e.g.E.164) address. For each identified external client, GMLC restrictions may be defined. It may also be +3278 indicated if the MS shall be notified of a non-restricted MT-LR from each identified LCS client and, if so, whether +3279 notification only or notification with privacy verification shall apply. Usage of this parameter is defined in 3GPP TS +3280 23.271. + +#### 3281 7.6.3.65 Internal Client List + +3282 This parameter is only applicable to the PLMN operator privacy class and gives the identities of the internal PLMN +3283 operator clients that are allowed to locate a target MS for an NI-LR or MT-LR. Usage of this parameter is defined in +3284 3GPP TS 23.271. + +#### 3285 7.6.3.65A MO-LR List + +3286 This parameter defines the classes of MO-LR for which a subscription exists for a particular MS. For each class, the +3287 following information is provided: + +- 3288 - SS-Code (see clause 7.6.4.1). + +#### 3289 7.6.3.65B Privacy Notification to MS User + +3290 This parameter is applicable to the call/session unrelated privacy class and call/session related privacy class. For non- +3291 call/call related privacy class it indicates whether the MS user shall be notified for that class MT-LR from any value +3292 added LCS client when the MT-LR is restricted and be enabled to accept or override the restriction. Usage of this +3293 parameter is defined in 3GPP TS 23.271. + +#### 3294 7.6.3.65C GMLC List Withdraw + +3295 This parameter indicates whether the subscriber's LCS GMLC list shall be deleted from the VLR or SGSN. + +#### 3296 7.6.3.65D Service Type List + +3297 This parameter is only applicable to the Service type privacy class and gives the identities of the service type of the +3298 clients that are allowed to locate a target MS for an MT-LR. Usage of this parameter is defined in 3GPP TS 23.271. + +#### 3299 7.6.3.66 IST Alert Timer + +3300 This parameter indicates the IST Alert Timer value that must be used in the MSC to inform the HLR about the call +3301 activities that the subscriber performs. Units are minutes. + +#### 3302 7.6.3.67 Call Termination Indicator + +3303 This parameter indicates whether the MSC shall terminate a specific ongoing call, or all the call activities related to a +3304 specified subscriber. + +#### 3305 7.6.3.68 IST Information Withdraw + +3306 This parameter indicates that IST information shall be deleted from the VMSC. + +#### 3307 7.6.3.69 IST Support Indicator + +3308 This parameter indicates the degree of IST functionality supported by the MSC (Visited MSC or Gateway MSC). It can +3309 take one of the following values: + +- 3310 - Basic IST functionality; +- 3311 - IST command service (in addition to the basic IST functionality and including the ability to terminate all calls +3312 being carried for the identified subscriber). + +#### 3313 **7.6.3.70 Super-Charger Supported In HLR** + +3314 This parameter is used by the HLR to indicate support of the Super-Charger functionality and an indication of the age of +3315 the subscription data stored in the HLR. + +#### 3316 **7.6.3.71 Super-Charger Supported In Serving Network Entity** + +3317 This parameter is used to indicate support of the Super-Charger functionality by the originating entity and to indicate +3318 either that subscription data is required or the date and time of the last know subscriber data modification. + +#### 3319 **7.6.3.72 Age Indicator** + +3320 This parameter is used by the HLR to determine the validity of the subscription data retained by the serving network +3321 entity in a Super-Charged network. + +#### 3322 **7.6.3.73 GPRS enhancements support indicator** + +3323 This parameter indicates to the HLR that the SGSN supports GPRS enhancements. + +#### 3324 **7.6.3.74 Extension QoS-Subscribed** + +3325 This parameter indicates the enhanced QoS subscribed for a certain service. It is defined in 3GPP TS 23.060. This +3326 parameter is an extension to QoS-Subscribed. + +#### 3327 **7.6.3.75 SGSN CAMEL Subscription Info** + +3328 This parameter identifies the subscriber as having CAMEL services that are invoked in the SGSN. + +#### 3329 **7.6.3.75A Extension-2 QoS-Subscribed** + +3330 This parameter indicates the additional QoS information to the Extension QoS-subscribed parameter. It is a further +3331 extension to Extension QoS-Subscribed. This parameter shall be used when the maximum bit rate exceeds 8640 kbps. +3332 For more details, refer to 3GPP TS 24.008 [35]. + +#### 3333 **7.6.3.75B Extension-3 QoS-Subscribed** + +3334 This parameter indicates the additional QoS information to the Extension QoS-subscribed parameter. It is a further +3335 extension to Extension QoS-Subscribed. This parameter shall be used when the maximum/guaranteed bit rate for uplink +3336 exceeds 8640 kbps. For more details, refer to 3GPP TS 24.008 [35]. + +#### 3337 **7.6.3.75C Extension-4 QoS-Subscribed** + +3338 This parameter indicates the additional QoS information to the Extension QoS-subscribed parameter. It is a further +3339 extension to Extension QoS-Subscribed. This parameter shall be used to define the Evolved Allocation/Retention +3340 Priority parameter, which includes the Priority Level, the Preemption Capability value and the Preemption vulnerability +3341 value, as described in 3GPP TS 29.060 [105]. + +#### 3342 **7.6.3.76 MO-SMS-CSI** + +3343 This parameter identifies the subscriber as having mobile originating SMS CAMEL services as defined in 3GPP TS +3344 23.078. For the CAMEL phase 3 the MO-SMS-CSI is the same as the SMS-CSI. + +3345 **7.6.3.76a MT-SMS-CSI** + +3346 This parameter identifies the subscriber as having mobile terminating SMS CAMEL services as defined in 3GPP TS +3347 23.078. + +3348 **7.6.3.77 GPRS-CSI** + +3349 This parameter identifies the subscriber as having GPRS CAMEL services as defined in 3GPP TS 23.078. + +3350 **7.6.3.78 CAMEL subscription info** + +3351 This parameter indicates the CSI that can be controlled by CSE. + +3352 **7.6.3.79 Extensible Call barring information for CSE** + +3353 This parameter contains for each call barring service for CSE: + +- 3354 - SS-Code; +- 3355 - a list of extensible call barring feature parameters. +3356 The list may contain one item per Basic Service Group. +- 3357 - password; +- 3358 - wrong password attempt counter; +- 3359 - notification-to-CSE flag. + +3360 **7.6.3.80 Extensible Forwarding information for CSE** + +3361 This parameter represents the information for CSE related to each call forwarding service: + +- 3362 - the SS-Code of the relevant call forwarding service; +- 3363 - if required, a list of extensible forwarding feature parameters; +- 3364 - the list may contain one item per Basic Service Group; +- 3365 - notification-to-CSE flag. + +3366 **7.6.3.81 Modification Request for CSI** + +3367 This parameter indicates the CAMEL subscription information to be modified by CSE. + +3368 **7.6.3.81a Modification Request for ODB data** + +3369 This parameter indicates the operator determined barring data to be modified by CSE. + +3370 **7.6.3.82 Modification Request for SS Information** + +3371 This parameter indicates the call forwarding, call barring, call hold, call waiting, explicit call transfer, calling line +3372 identification presentation and calling line identification restriction supplementary service data to be modified by CSE. + +3373 **7.6.3.83 Call Barring Data** + +3374 This parameter contains the extensible call barring feature list (see clause 7.6.3.21) and Notification to CSE flag. + +3375 **7.6.3.84 Call Forwarding Data** + +3376 This parameter contains the extensible call forwarding feature list (see clause 7.6.3.16) and Notification to CSE flag. + +3377 **7.6.3.85 ODB Data** + +3378 This parameter contains the ODB general data, ODB HPLMN specific data. + +3379 **7.6.3.86 Requested Subscription Info** + +3380 This parameter indicates the subscription information being requested. + +3381 **7.6.3.87 CS Allocation/Retention priority** + +3382 This parameter indicates the allocation/retention priority for Circuit Switched (CS). It corresponds to the +3383 allocation/retention priority that is defined in 3GPP TS 23.107 [154]. + +3384 **7.6.3.88 ODB Info** + +3385 This parameter contains the ODB data and Notification to CSE flag. + +3386 **7.6.3.89 Suppress VT-CSI** + +3387 This parameter is used to suppress the invocation of terminating CAMEL services at the VMSC. + +3388 **7.6.3.90 Suppress Incoming Call Barring** + +3389 This parameter is used to suppress the invocation of Incoming Call Barrings. + +3390 **7.6.3.91 gsmSCF Initiated Call** + +3391 This parameter is used to indicate that the call was initiated by the gsmSCF. + +3392 **7.6.3.91a SuppressMTSS** + +3393 This parameter is used to suppress the invocation of terminating supplementary services + +3394 **7.6.3.92 Call barring support indicator** + +3395 This parameter is used to indicate that the SGSN supports the call barring services for SMS. + +3396 **7.6.3.93 MNP Info Result** + +3397 This parameter refers to the Mobile Number Portability (MNP) information result (see 3GPP TS 23.078 [98] and 3GPP +3398 TS 23.066 [108]). This parameter may contain the following information: + +- 3399 - Routeing Number (see clause 7.6.2.63). +- 3400 - IMSI (see 3GPP TS 23.078[98], see also clause 7.6.2.1). +- 3401 - MSISDN (see clause 7.6.2.17). +- 3402 - Number Portability Status (see clause 7.6.5.14). + +3403 **7.6.3.94 Allowed Services** + +3404 This parameter is used by the HLR to indicate which service is available for a call when two services have been +3405 requested, for the SCUDIF feature described in 3GPP TS 23.172 [126]. + +### 3406 7.6.3.95 Unavailability Cause + +3407 This parameter is used to indicate the reason for the unavailability of one of the services as indicated by the Allowed +3408 Services IE (see 7.6.3.94) when two services have been requested, for the SCUDIF feature described in 3GPP TS +3409 23.172 [126]. + +### 3410 7.6.3.96 MNP Requested Info + +3411 This parameter indicates by its presence that Mobile Number Portability (MNP) information is requested for the +3412 subscriber, as defined in 3GPP TS 23.078 [98]. + +### 3413 7.6.3.97 Access Restriction Data + +3414 This parameter refers to the radio access technologies that are possibly restricted to a subscriber via subscription data. +3415 For the use of the parameter, see 3GPP TS 23.012 [23] for the CS domain and 3GPP TS 23.060[104], 3GPP TS 29.060 +3416 [105] clause 7.5.3 and 3GPP TS 29.274 [149] clause 7.3.6 for the PS domain. + +### 3417 7.6.3.98 Supported RAT types indicator + +3418 This parameter indicates which RAT types are supported/served by the MSC/VLR or SGSN or MME + +### 3419 7.6.3.99 UE SRVCC Capability + +3420 This parameter indicates, if present, the support of SRVCC capability by the UE. + +### 3421 7.6.3.100 Temporary Empty CSG Subscription data Indicator + +3422 This parameter indicates that the CSS has currently no CSG subscription data for this roaming user but registers the +3423 VLR or SGSN, so to inform them if later changes in CSG subscription data occur. + +### 3424 7.6.3.101 WLAN-offloadability + +3425 This parameter refers to the WLAN offloadability for E-UTRAN or UTRAN. This parameter is defined in 3GPP TS +3426 29.272 [144]. + +### 3427 7.6.3.102 IMSI-Group-Id + +3428 This parameter refers to the IMSI-Group identifier. This parameter is defined in 3GPP TS 29.272 [144]. + +3429 + +## 3430 7.6.4 Supplementary services parameters + +### 3431 7.6.4.1 SS-Code + +3432 This parameter may refer to one supplementary service or a set of supplementary services as defined in 3GPP TS +3433 22.004. For MAP this includes: + +- 3434 - Calling Line Identification Presentation service (CLIP); +- 3435 - Calling Line Identification Restriction service (CLIR); +- 3436 - Connected Line Identification Presentation service (COLP); +- 3437 - Connected Line Identification Restriction service (COLR); +- 3438 - Calling Name Presentation (CNAP); +- 3439 - All Call Forwarding services, including Call Deflection; + +- 3440 - Call Waiting (CW); +- 3441 - Call Hold (HOLD); +- 3442 - Multi-Party service (MPTY); +- 3443 - Closed User Group (CUG); +- 3444 - All Charging services; +- 3445 - All Call Restriction services; +- 3446 - Explicit Call Transfer service (ECT); +- 3447 - enhanced Multi-Level Precedence and Pre-emption service (eMLPP); +- 3448 - Completion of Calls to Busy Subscriber, originating side (CCBS-A); +- 3449 - Completion of Calls to Busy Subscriber, destination side (CCBS-B); +- 3450 - All LCS privacy exceptions (see clause 7.6.4.44); +- 3451 - Mobile Originating Location Request (MO-LR) (see clause 7.6.4.45); +- 3452 - Multicall (MC). + +#### 3453 7.6.4.1A SS-Code 2 + +3454 This parameter is used to refer to one or a set of supplementary services (as 7.6.4.1 "SS-Code") related to Network + 3455 Signal Info 2 for SCUDIF calls (see 3GPP TS 23.172 [126]). + +#### 3456 7.6.4.2 SS-Status + +3457 This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. + +#### 3458 7.6.4.3 SS-Data + +3459 This parameter refers to the necessary set of information required in order to characterise one supplementary service: + +- 3460 - SS-Code (see clause 7.6.4.1); +- 3461 - SS-Status (if applicable) (see clause 7.6.4.2); +- 3462 - Override subscription option (see clause 7.6.4.4); +- 3463 - CLI Restriction (see clause 7.6.4.5); +- 3464 - Basic Service Group Code (see clause 7.6.4.40). + +#### 3465 7.6.4.4 Override Category + +3466 This parameter refers to the subscription option Override Category attached to a supplementary service. It can take the + 3467 following two values: + +- 3468 - Enabled; +- 3469 - Disabled. + +#### 3470 7.6.4.5 CLI Restriction Option + +3471 This parameter refers to the subscription option Restriction mode attached to the CLIR supplementary service. It can + 3472 take the following three values: + +- 3473 - Permanent; + +- 3474 - Temporary (Default Restricted); +- 3475 - Temporary (Default Allowed). + +#### 3476 7.6.4.6 Forwarding Options + +3477 This parameter refers to a forwarding option attached to a supplementary service. It can take one of the following +3478 values: + +- 3479 - notification to forwarding party (see 3GPP TS 22.082 [10] for the meaning of this parameter); +- 3480 - notification to calling party (see 3GPP TS 22.082 [10] for the meaning of this parameter); +- 3481 - redirecting presentation (see 3GPP TS 22.082 [10] for the meaning of this parameter); +- 3482 - Forwarding reason (see 3GPP TS 22.082 [10] for the meaning of this parameter). + +#### 3483 7.6.4.7 No reply condition timer + +3484 This parameter refers to the no reply condition timer for call forwarding on no reply. + +#### 3485 7.6.4.8 - 7.6.4.14 Void + +#### 3486 7.6.4.15 Forwarding information + +3487 This parameter represents the information related to each call forwarding service: + +- 3488 - the SS-Code of the relevant call forwarding service (see clause 7.6.4.1); + - 3489 - if required, a list of forwarding feature parameters (see clause 7.6.4.16). +- 3490 the list may contain one item per Basic Service Group. + +#### 3491 7.6.4.16 Forwarding feature + +3492 This parameter applies to each combination of call forwarding service and Basic Service Group and contains the +3493 following information, as required: + +- 3494 - Basic Service Group (see clause 7.6.4.40); +- 3495 - SS-Status (see clause 7.6.4.2); +- 3496 - forwarded-to number (see clause 7.6.2.22); +- 3497 - forwarded-to subaddress (see clause 7.6.2.23); +- 3498 - forwarding options (see clause 7.6.4.6); +- 3499 - no reply condition timer (see clause 7.6.4.7); +- 3500 - long forwarded-to number (see clause 7.6.2.22A). + +3501 If a number is required to define the forwarded-to destination then: + +- 3502 - If the VLR supports Long Forwarded-to Numbers then the long forwarded-to number shall be present and the +3503 forwarded-to number shall be absent. +- 3504 - If the VLR does not support Long Forwarded-to Numbers then the forwarded-to number shall be present and the +3505 long forwarded-to number shall be absent. + +#### 3506 7.6.4.17 Void + +#### 3507 7.6.4.18 Call barring information + +3508 This parameter contains for each call barring service: + +- 3509 - SS-Code (see clause 7.6.4.1); +- 3510 - a list of call barring feature parameters (see clause 7.6.4.19). +- 3511 The list may contain one item per Basic Service Group. + +#### 3512 7.6.4.19 Call barring feature + +3513 This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter +3514 contains the following information: + +- 3515 - Basic Service Group (see clause 7.6.4.40); +- 3516 - SS-Status (see clause 7.6.4.2). + +#### 3517 7.6.4.20 New password + +3518 This parameter refers to the password which the subscriber just registered in the network. + +3519 This parameter refers to a password used by the subscriber for supplementary service control. + +#### 3520 7.6.4.21 Current password + +3521 This parameter refers to a password used by the subscriber for supplementary service control. + +#### 3522 7.6.4.22 Guidance information + +3523 This parameter refers to guidance information given to a subscriber who is requested to provide a password. One of the +3524 following information may be given: + +- 3525 - "enter password"; +3526 this information is used for checking of the old password; +- 3527 - "enter new password"; +3528 this information is used during password registration for the request of the first new password; +- 3529 - "enter new password again"; +3530 this information is used during password registration for the request of the new password again for verification. + +#### 3531 7.6.4.23 Void + +#### 3532 7.6.4.24 SS-Info + +3533 This parameter refers to all the information related to a supplementary service and is a choice between: + +- 3534 - forwarding information (see clause 7.6.4.15); +- 3535 - call barring information (see clause 7.6.4.18); +- 3536 - CUG info (see clause 7.6.4.8); +- 3537 - SS-Data (see clause 7.6.4.3). +- 3538 - eMLPP information (see clause 7.6.4.41). + +#### 3539 7.6.4.25 - 7.6.4.35 Void + +#### 3540 7.6.4.36 USSD Data Coding Scheme + +3541 This parameter contains the information of the alphabet and the language used for the unstructured information in an +3542 Unstructured Supplementary Service Data operation. The coding of this parameter is according to the Cell Broadcast +3543 Data Coding Scheme as specified in 3GPP TS 23.038 [25]. + +#### 3544 7.6.4.37 USSD String + +3545 This parameter contains a string of unstructured information in an Unstructured Supplementary Service Data operation. +3546 The string is sent either by the mobile user or the network. The contents of a string sent by the MS are interpreted by the +3547 network as specified in 3GPP TS 22.090 [16]. + +#### 3548 7.6.4.38 Bearer service + +3549 This parameter may refer to a single bearer service, a set of bearer services or to all bearer services as defined in 3GPP +3550 TS 22.002 [3]. This parameter is used only for supplementary service management. + +#### 3551 7.6.4.38A Bearer Service 2 + +3552 This parameter is used to indicate the bearer service or set of bearer services (as 7.6.4.38 "Bearer service") related to +3553 Network Signal Info 2 for SCUDIF calls (see 3GPP TS 23.172 [126]). + +#### 3554 7.6.4.39 Teleservice + +3555 This parameter may refer to a single teleservice, a set of teleservices or to all teleservices as defined in 3GPP TS 22.003 +3556 [4]. This parameter is used only for supplementary service management. + +#### 3557 7.6.4.39A Teleservice 2 + +3558 This parameter is used to indicate the teleservice or set of teleservices (as 7.6.4.39 "Teleservice") related to Network +3559 Signal Info 2 for SCUDIF calls (see 3GPP TS 23.172 [126]). + +#### 3560 7.6.4.40 Basic Service Group + +3561 This parameter refers to the Basic Service Group either as a bearer service (see clause 7.6.4.38) or a teleservice (see +3562 clause 7.6.4.39). This parameter is used only for supplementary service management. The null value (i.e. neither bearer +3563 service nor teleservice) is used to denote the group containing all bearer services and all teleservices. + +#### 3564 7.6.4.41 eMLPP information + +3565 This parameter contains two parameters which are associated with the eMLPP service. The following two parameters +3566 are included: + +- 3567 - maximum entitled priority: + - 3568 - indicates the highest priority level the subscriber is allowed to apply for an outgoing call set-up; +- 3569 - default priority: + - 3570 - defines the priority level which shall be assigned to a call if no explicit priority is indicated during call set-up. + +#### 3571 7.6.4.42 SS-event + +3572 This parameter indicates the Supplementary Service for which an invocation notification is sent towards the gsmSCF. It +3573 can indicate one of the following services: + +- 3574 - Explicit Call Transfer (ECT) +- 3575 - Call Deflection (CD) +- 3576 - Multi-Party call (MPTY) + +3577 - Completion of Calls to Busy Subscriber (CCBS) + +#### 3578 7.6.4.43 SS-event data + +3579 This parameter contains additional information related to Supplementary Service invocation. Depending on the service +3580 invoked it can contain the following information: + +3581 ECT A list with all Called Party Numbers involved. + +3582 CD The called Party number involved. + +#### 3583 7.6.4.44 LCS Privacy Exceptions + +3584 Distinct SS codes are assigned to the following classes of LCS client in a target MS subscriber's privacy exception list. + +3585 - Universal Class; + +3586 - Call/session related value added class; + +3587 - Call/session unrelated value added class; + +3588 - PLMN operator class. + +3589 - Service type class. + +3590 + +#### 3591 7.6.4.45 Mobile Originating Location Request (MO-LR) + +3592 Distinct SS codes are assigned to the following classes of MO-LR: + +3593 - Basic Self Location; + +3594 - Autonomous Self Location; + +3595 - Transfer to Third Party. + +#### 3596 7.6.4.46 NbrUser + +3597 This parameter indicates the maximum number of parallel bearers that may be used as defined by the user at registration +3598 of the MC SS. + +#### 3599 7.6.4.47 MC Subscription Data + +3600 This parameter contains two parameters which are associated with the MC service. The following two parameters are +3601 included: + +3602 - NbrUser: + +3603 indicates the maximum number of parallel bearers that may be used as defined by the user at registration of +3604 the MC SS + +3605 - NbrSB: + +3606 indicates the maximum number of parallel bearers that may be used as defined by the user's subscription. + +#### 3607 7.6.4.48 MC Information + +3608 This parameter contains three parameters which are associated with the MC service. The following parameters are +3609 included: + +3610 - NbrSB; + +3611 - NbrUser; + +3612 - NbrSN. + +3613 Definitions of these parameters are provided in 3GPP TS 23.135. + +#### 3614 **7.6.4.49 CCBS Request State** + +3615 This parameter indicates the current state of the CCBS request. It can take one of seven values: + +3616 - request; + +3617 - recall; + +3618 - active; + +3619 - completed; + +3620 - suspended; + +3621 - frozen; + +3622 - deleted. + +#### 3623 **7.6.4.50 Basic Service Group 2** + +3624 This parameter refers to the Basic Service Group either as a bearer service (see clause 7.6.4.38) or a teleservice (see +3625 clause 7.6.4.39). This parameter is used only for supplementary service management. + +### 3626 **7.6.5 Call parameters** + +#### 3627 **7.6.5.1 Call reference number** + +3628 This parameter refers to a call reference number allocated by a call control MSC. + +#### 3629 **7.6.5.2 Interrogation type** + +3630 This parameter refers to the type of interrogation for routing information which is sent from a GMSC to an HLR. It can +3631 take either of two values: + +3632 - basic call (for information to route a call before the call has been extended to the VMSC of the called party); + +3633 - forwarding (for information to route the call to the forwarded-to destination after the VMSC of the forwarding +3634 party has requested the GMSC to resume handling of the call. + +#### 3635 **7.6.5.3 OR interrogation** + +3636 This parameter indicates that the GMSC which interrogated the HLR for routeing information is not in the same PLMN +3637 as the HLR, and therefore that the call will potentially be optimally routed. + +#### 3638 **7.6.5.4 OR capability** + +3639 This parameter indicates the phase of OR which the GMSC supports. + +#### 3640 **7.6.5.5 Forwarding reason** + +3641 This parameter indicates the reason for which the call is to be forwarded. It can take one of three values: + +3642 - busy subscriber; + +3643 - mobile subscriber not reachable; + +3644 - no subscriber reply. + +#### 3645 7.6.5.6 Forwarding interrogation required + +3646 This parameter indicates that if the VMSC of the forwarding subscriber requests the GMSC to resume handling of the +3647 call the GMSC shall interrogate the HLR for forwarding information. + +#### 3648 7.6.5.7 O-CSI + +3649 This parameter identifies the subscriber as having originating CAMEL services as defined in 3GPP TS 23.078. + +#### 3650 7.6.5.7A D-CSI + +3651 This parameter identifies the subscriber as having originating CAMEL dialled services as defined in 3GPP TS 23.078. + +#### 3652 7.6.5.7B T-CSI + +3653 This parameter identifies the subscriber as having terminating CAMEL services in the GMSC, as defined in 3GPP +3654 TS 23.078. + +#### 3655 7.6.5.7C VT-CSI + +3656 This parameter identifies the subscriber as having terminating CAMEL services in the VMSC, as defined in +3657 3GPP TS 23.078. + +#### 3658 7.6.5.7D O-IM-CSI + +3659 This parameter identifies the subscriber as having originating IP Multimedia Core Network CAMEL services as defined +3660 in 3GPP TS 23.278. + +#### 3661 7.6.5.7E D-IM-CSI + +3662 This parameter identifies the subscriber as having originating IP Multimedia Core Network CAMEL dialled services as +3663 defined in 3GPP TS 23.278. + +#### 3664 7.6.5.7F VT-IM-CSI + +3665 This parameter identifies the subscriber as having terminating IP Multimedia Core Network CAMEL services as +3666 defined in 3GPP TS 23.278. + +#### 3667 7.6.5.8 Void + +#### 3668 7.6.5.9 Void + +#### 3669 7.6.5.10 Void + +#### 3670 7.6.5.11 CCBS Feature + +3671 This parameter corresponds to the 'CCBS Description' parameter in 3GPP TS 23.093. It refers to the necessary set of +3672 information required in order to characterise a certain CCBS request. The parameter may contain the following +3673 information: + +- 3674 - CCBS Index (see 3GPP TS 23.093 for the use of this parameter); +- 3675 - B-subscriber number (see clause 7.6.2.48); +- 3676 - B-subscriber subaddress (see clause 7.6.2.49); + +3677 - Basic Service Group Code (see clause 7.6.4.40). + +#### 3678 7.6.5.12 UU Data + +3679 This parameter includes User-To-User Data. It is defined in 3GPP TS 23.087. + +#### 3680 7.6.5.13 UUS CF Interaction + +3681 This parameter indicates if the call forwarding or call deflection has been activated after UUS1 request has been +3682 accepted . It is defined in 3GPP TS 23.087. + +#### 3683 7.6.5.14 Number Portability Status + +3684 This parameter indicates the number portability status of subscriber. See 3GPP TS 23.066 [108]. + +#### 3685 7.6.5.15 Pre-paging supported + +3686 This parameter indicates that the entity which sent it supports pre-paging. + +#### 3687 7.6.5.16 MT Roaming Retry Supported + +3688 The parameter indicates that the entity which sent it supports MT Roaming Retry. When sent by the HLR, it further +3689 indicates that the GMSC also supports MT Roaming Retry. + +#### 3690 7.6.5.17 MT Roaming Retry + +3691 The parameter indicates that the GMSC receiving the IE shall start MT roaming retry (see 3GPP TS 23.018 [97] and +3692 3GPP TS 23.012 [23]). + +#### 3693 7.6.5.18 Paging Area + +3694 The parameter indicates the paging area where the MS is currently located (see 3GPP TS 23.012 [23] and 3GPP TS +3695 23.018 [97]). + +#### 3696 7.6.5.19 Call Priority + +3697 The parameter indicates the eMLPP priority of the call (see 3GPP TS 23.067 [136]). + +#### 3698 7.6.5.20 MTRF Supported + +3699 The parameter indicates that the entity which sends it supports MT Roaming Forwarding. + +#### 3700 7.6.5.21 LCLS Global Call Reference (LCLS GCR) + +3701 This parameter refers to a globally unique call identifier for the duration of the call (see 3GPP TS 29.205 [146]). This +3702 parameter is used to identify a call and to correlate the call legs of a call to determine if the call is a local call within the +3703 BSS. + +#### 3704 7.6.5.22 LCLS-Negotiation + +3705 This parameter is used to request MSC-B to indicate LCLS, see 3GPP TS 29.205 [146] clause B.2.1.4 LCLS +3706 Negotiation Request. + +#### 3707 7.6.5.23 LCLS-Configuration-Preference + +3708 This parameter contains information to indicate the negotiated LCLS configuration preference, see 3GPP TS 29.205 +3709 [146] clause B.2.1.10 LCLS Configuration Preference. + +## 3710 7.6.6 Radio parameters + +### 3711 7.6.6.1 - 7.6.6.3 Void + +### 3712 7.6.6.4 GERAN Classmark + +3713 This information element is sent from one MSC to the other MSC in the signalling for inter MSC handover. It is used +3714 to convey information related to cell capabilities, as defined in 3GPP TS 48.008. + +### 3715 7.6.6.5 BSSMAP Service Handover + +3716 This parameter refers to the Service Handover information element defined in 3GPP TS 48.008 + +### 3717 7.6.6.5A BSSMAP Service Handover List + +3718 This parameter refers to the list of Service Handover information elements defined in 3GPP TS 48.008. This parameter +3719 shall be used when there are multiple bearers and at least one of the bearers has an associated BSSMAP Service +3720 Handover parameter. + +### 3721 7.6.6.6 RANAP Service Handover + +3722 This parameter refers to the Service Handover information element defined in 3GPP TS 25.413. + +### 3723 7.6.6.7 HO-Number Not Required + +3724 This parameter indicates that no handover or relocation number allocation is necessary. + +### 3725 7.6.6.8 Integrity Protection Information + +3726 This parameter refers to the Integrity Protection Information element defined in 3GPP TS 25.413. + +### 3727 7.6.6.9 Encryption Information + +3728 This parameter refers to the Encryption Information element defined in 3GPP TS 25.413. + +### 3729 7.6.6.10 Radio Resource Information + +3730 This parameter refers to the Channel Type information element defined in 3GPP TS 48.008 [49]. + +### 3731 7.6.6.10A Radio Resource List + +3732 This parameter refers to list of RAB-id's and their associated Channel Type information elements defined in 3GPP TS +3733 48.008. This parameter shall be used when there are multiple bearers and at least one of the bearers has an associated +3734 Radio Resource Information parameter. + +### 3735 7.6.6.10B Chosen Radio Resource Information + +3736 This parameter refers to the Chosen Channel and Speech Version information elements defined in 3GPP TS 48.008. + +### 3737 7.6.6.11 Key Status + +3738 This parameter refers to the Key Status element defined in 3GPP TS 25.413. + +### 3739 7.6.6.12 Selected UMTS Algorithms + +3740 This parameters identifies the UMTS integrity and optionally encryption algorithms selected by MSC-B. Coding of this +3741 parameter is defined in 3GPP TS 25.413. + +#### 3742 7.6.6.13 Allowed GSM Algorithms + +3743 This parameter identifies the allowed GSM algorithms in MSC-B. Coding of this parameter is defined in 3GPP TS +3744 48.008. + +#### 3745 7.6.6.14 Allowed UMTS Algorithms + +3746 This parameter identifies the allowed UMTS algorithms in MSC-B. Coding of this parameter is defined in 3GPP TS +3747 25.413. + +#### 3748 7.6.6.15 Selected GSM Algorithm + +3749 This parameter identifies the GSM algorithm selected by GSM BSC controlled by MSC-B. Coding of this parameter is +3750 defined in 3GPP TS 48.008. + +#### 3751 7.6.6.16 Iu-Currently Used Codec + +3752 This parameter indicates the codec used at the Iu interface before handover. + +#### 3753 7.6.6.17 Iu-Supported Codecs List + +3754 This parameter indicates the codecs supported by the UE and by MSC-A and the associated modes in priority order (the +3755 first entry being the highest priority codec). MSC-B uses this information to select the associated transcoder resources. + +#### 3756 7.6.6.17A Iu-Available Codecs List + +3757 This parameter indicates the codecs available at the Iu interface in MSC-B and the associated modes. MSC-A uses this +3758 information to decide whether a change to a different codec at the Iu interface is possible. + +#### 3759 7.6.6.18 Iu-Selected Codec + +3760 When sent by MSC-B, this parameter indicates the codec selected by MSC-B for the Iu interface. When sent by MSC- +3761 A, this parameter indicates the codec to be used by MSC-B at the Iu interface. + +#### 3762 7.6.6.19 RAB Configuration Indicator + +3763 This parameter indicates by its presence that MSC-A (or MSC-B in case of subsequent handover) has generated the +3764 RAB parameters according to the preferred codec (first entry in the Iu-Supported Codecs List). + +#### 3765 7.6.6.20 UESBI-Iu + +3766 This parameter refers to the UESBI-Iu (UE Specific Behaviour Information over the Iu interface) information element +3767 defined in 3GPP TS 25.413. + +#### 3768 7.6.6.21 Alternative Channel Type + +3769 This parameter refers to the Channel Type information element defined in 3GPP TS 48.008 [49] for the alternative radio +3770 access bearer. This parameter is used for SCUDIF calls (see 3GPP TS 23.172 [126]). + +#### 3771 7.6.6.22 AoIP-Supported Codecs List Anchor + +3772 This parameter is used for inter- MSC handover with AoIP access and the procedures and contents of the parameter are +3773 as defined in AoIP-Supported Codecs List (Anchor) in 3GPP TS 23.009 [21]. + +#### 3774 7.6.6.23 AoIP-Available Codecs List Map + +3775 This parameter is used for inter- MSC handover with AoIP access and the procedures and contents of the parameter +3776 are as defined in AoIP-Available Codecs List (Map) in 3GPP TS 23.009 [21]. + +#### 3777 7.6.6.24 AoIP-Selected Codec Target + +3778 This parameter is used for inter-MSC handover with AoIP access and the procedures and contents of the parameter are +3779 as defined in AoIP-Selected Codec (Target) in 3GPP TS 23.009 [21]. + +### 3780 7.6.7 Authentication parameters + +#### 3781 7.6.7.1 Authentication set list + +3782 This parameter represents a list of sets of authentication parameters for a given subscriber. + +3783 The list either contains Authentication Triplets (Rand, Sres, Kc) or Authentication Quintuplets (Rand, Xres, Ck, Ik, +3784 Autn). If the list contains Authentication Quintuplets, the order of sequence in this list is chronological, the first +3785 quintuplet in the list is the oldest one. + +#### 3786 7.6.7.2 Rand + +3787 This parameter represents a random number used for authentication. + +#### 3788 7.6.7.3 Sres + +3789 This parameter represents the response to an authentication request. + +#### 3790 7.6.7.4 Kc + +3791 This parameter refers to a key used for ciphering purposes. + +#### 3792 7.6.7.5 Xres + +3793 This parameter represents the response to an UMTS authentication request. + +#### 3794 7.6.7.5A Ck + +3795 This parameter refers to a key used for UMTS ciphering purposes. + +#### 3796 7.6.7.5B Ik + +3797 This parameter refers to the Integrity Key. + +#### 3798 7.6.7.5C Autn + +3799 This parameter refers to the Authentication Token. + +#### 3800 7.6.7.5D KASME + +3801 This parameter refers to the Key for the Access Security Management Entity. + +#### 3802 7.6.7.6 Cksn + +3803 This parameter refers to a ciphering key sequence number. + +#### 3804 7.6.7.6A Ksi + +3805 This parameter refers to a key set identifier. + +#### 3806 7.6.7.6B Auts + +3807 This parameter refers to the resynchronisation token. + +### 3808 7.6.7.7 Ciphering mode + +3809 This parameter refers to the ciphering mode which is associated with a radio channel. It may take values as follows: + +- 3810 - no encryption; +- 3811 - identification of specific ciphering algorithm. + +### 3812 7.6.7.8 Current Security Context + +3813 This parameter represents a list of security context parameters for a given subscriber. + +3814 The list either contains GSM Security Context data (Kc, Cksn) or UMTS Security Context Data (Ck, Ik, Ksi). + +### 3815 7.6.7.9 Failure cause + +3816 This parameter refers to an authentication failure which has occurred. It may take values as follows: + +- 3817 - wrong user response; +- 3818 - wrong network signature. + +### 3819 7.6.7.10 Re-attempt + +3820 It indicates whether the failure occurred in a normal authentication attempt or in an authentication reattempt (there was a +3821 previous unsuccessful authentication). + +### 3822 7.6.7.11 Access Type + +3823 It indicates whether the authentication procedure was initiated due to a call, an emergency call, a location updating, a +3824 supplementary service procedure, a short message transfer, a GPRS attach procedure, a routing area updating, a service +3825 request, a MS initiated Detach in GPRS, a PDP context activation or a PDP context deactivation procedure. + +## 3826 7.6.8 Short message parameters + +### 3827 7.6.8.1 SM-RP-DA + +3828 This parameter represents the destination address used by the short message service relay sub-layer protocol. It can be +3829 either of the following: + +- 3830 - IMSI (see clause 7.6.2.1); +- 3831 - LMSI (see clause 7.6.2.16); +- 3832 - MS-ISDN (see clause 7.6.2.17); +- 3833 - roaming number (see clause 7.6.2.19); +- 3834 - service centre address (see clause 7.6.2.27). + +### 3835 7.6.8.2 SM-RP-OA + +3836 This parameter refers to the originating address used by the short message service relay sub-layer protocol. It can be +3837 either of the following: + +- 3838 - MS-ISDN (see clause 7.6.2.17); +- 3839 - service centre address (see clause 7.6.2.27). + +### 3840 7.6.8.3 MWD status + +3841 This parameter indicates whether or not the address of the originator service centre is already contained in the Message +3842 Waiting Data file. In addition, it contains the status of the Memory Capacity Exceeded Flag (MCEF), the status of the +3843 Mobile subscriber Not Reachable Flag (MNRF), the status of the Mobile station Not Reachable for GPRS flag +3844 (MNRG), the status of the Mobile station Not Reachable for 5G-3GPP access flag (MNR5G) and the status of the +3845 Mobile station Not Reachable for 5G-Non-3GPP access flag (MNR5GN3G). + +#### 3846 **7.6.8.4 SM-RP-UI** + +3847 This parameter represents the user data field carried by the short message service relay sub-layer protocol. + +#### 3848 **7.6.8.5 SM-RP-PRI** + +3849 This parameter is used to indicate whether or not delivery of the short message shall be attempted when a service centre +3850 address is already contained in the Message Waiting Data file. + +#### 3851 **7.6.8.6 SM Delivery Outcome** + +3852 This parameter indicates the cause for setting the message waiting data. It can take one of the following values: + +- 3853 - Absent subscriber; +- 3854 - MS memory capacity exceeded; +- 3855 - Successful transfer. + +#### 3856 **7.6.8.7 More Messages To Send** + +3857 This parameter is used to indicate whether or not the service centre has more short messages to send. + +#### 3858 **7.6.8.8 Alert Reason** + +3859 This parameter is used to indicate the reason why the service centre is alerted. It can take one of the following values: + +- 3860 - MS present; +- 3861 - Memory Available. + +#### 3862 **7.6.8.9 Absent Subscriber Diagnostic SM** + +3863 This parameter is used to indicate the reason why the subscriber is absent. For the values for this parameter see 3GPP +3864 TS 23.040. + +#### 3865 **7.6.8.10 Alert Reason Indicator** + +3866 This parameter indicates that the alert reason is sent to the HLR due to GPRS activity. + +#### 3867 **7.6.8.10A Additional Alert Reason Indicator** + +3868 This parameter indicates that the alert reason is sent to the HLR due to IMS activity. + +#### 3869 **7.6.8.11 Additional SM Delivery Outcome** + +3870 This parameter is used to indicate the GPRS delivery outcome in case a combination between delivery outcome for +3871 GPRS and non-GPRS are sent to the HLR. + +#### 3872 **7.6.8.12 Additional Absent Subscriber Diagnostic SM** + +3873 This parameter indicates the reason of the additional SM Delivery Outcome. + +#### 3874 7.6.8.13 Delivery Outcome Indicator + +3875 This parameter indicates that the delivery outcome sent to the HLR is for GPRS. + +#### 3876 7.6.8.14 GPRS Node Indicator + +3877 This parameter indicates by its presence that the Network Node Number sent by the HLR, SMS-Router or IP-SM-GW +3878 is to be considered as the SGSN number (although it may actually be an SMS-Router Number or IP-SM-GW Number). + +#### 3879 7.6.8.14A IMS Node Indicator + +3880 This parameter indicates by its presence that the Network Node Number sent by the HLR is an IP-SM-GW number. + +#### 3881 7.6.8.15 GPRS Support Indicator + +3882 This parameter indicates that the SMS-GMSC supports GPRS specific procedure of combine delivery of Short Message +3883 via MSC and/or via the SGSN. + +#### 3884 7.6.8.16 SM-RP-MTI + +3885 This parameter represents the RP-Message Type Indicator of the Short Message. It is used to distinguish a SM sent to +3886 the mobile station in order to acknowledge an MO-SM initiated by the mobile from a normal MT-SM. This parameter is +3887 formatted according to the formatting rules of address fields as described in 3GPP TS 23.040. + +#### 3888 7.6.8.17 SM-RP-SMEA + +3889 This parameter represents the RP-Originating SME-address of the Short Message Entity that has originated the SM. +3890 This parameter is used by the short message service relay sub-layer protocol and is formatted according to the +3891 formatting rules of address fields as described in 3GPP TS 23.040. + +#### 3892 7.6.8.18 IP-SM-GW SM Delivery Outcome + +3893 This parameter is used to indicate the delivery outcome for the IMS domain. + +#### 3894 7.6.8.19 IP-SM-GW Absent Subscriber Diagnostic SM + +3895 This parameter indicates the reason of the IP-SM-GW SM Delivery Outcome. + +#### 3896 7.6.8.20 IP-SM-GW Indicator + +3897 This parameter indicates by its presence that sm-deliveryOutcome is for delivery via IMS. + +#### 3898 7.6.8.21 SM Delivery Timer + +3899 This parameter indicates the SM Delivery Timer value set in the SMS-GMSC to the IP-SM-GW, SGSN or MSC/VLR. +3900 It may be taken into account by the domain selection procedure in the IP-SM-GW. Units are in seconds. + +#### 3901 7.6.8.22 SM Delivery Start Time + +3902 This parameter indicates the timestamp (in UTC) at which the SM Delivery Supervision Timer was started in the SMS- +3903 GMSC. + +#### 3904 7.6.8.23 Maximum Retransmission Time + +3905 This parameter indicates the maximum retransmission time (in UTC) until which the SMS-GMSC is capable to +3906 retransmit the MT Short Message. + +#### 3907 7.6.8.24 Requested Retransmission Time + +3908 This parameter indicates the retransmission time (in UTC) at which the SMS-GMSC is requested to retransmit the MT +3909 Short Message. + +#### 3910 **7.6.8.25 Maximum UE Availability Time** + +3911 This parameter indicates the timestamp (in UTC) until which a UE using a power saving mechanism (such as extended +3912 idle mode DRX) is expected to be reachable for SM Delivery. + +3913 This information may be used by the SMS Center to prioritize the retransmission of Short Message to UEs using a +3914 power saving mechanism. + +#### 3915 **7.6.8.26 SMS-GMSC Alert Event** + +3916 This parameter indicates the event that causes the MME (via an IWF) or the SGSN to alert the SMS-GMSC for +3917 retransmitting an MT Short Message. + +#### 3918 **7.6.8.27 SMS-GMSC Address** + +3919 This parameter contains the E.164 number of the SMS-GMSC or SMS Router, in international number format as +3920 described in ITU-T Recommendation E.164 [67]. + +#### 3921 **7.6.8.28 SMS-GMSC Diameter Address** + +3922 This parameter contains the Diameter Identity of the SMS-GMSC or SMS Router. + +#### 3923 **7.6.8.29 New SGSN Number** + +3924 This parameter contains the E.164 number of the new SGSN serving the MS. + +#### 3925 **7.6.8.30 New MME Number** + +3926 This parameter contains the E.164 number of the new MME serving the MS. + +#### 3927 **7.6.8.31 New SGSN Diameter Address** + +3928 This parameter contains the Diameter Identity of the new SGSN serving the MS. + +#### 3929 **7.6.8.32 New MME Diameter Address** + +3930 This parameter contains the Diameter Identity of the new MME serving the MS. + +#### 3931 **7.6.8.33 New MSC Number** + +3932 This parameter contains the E.164 number of the new MSC serving the MS. + +#### 3933 **7.6.8.34 SMSF 3GPP Absent Subscriber Diagnostic SM** + +3934 This parameter is used to indicate the reason why the subscriber is absent for 5G 3GPP access. For the values for this +3935 parameter see 3GPP TS 23.040. + +#### 3936 **7.6.8.35 SMSF Non 3GPP Absent Subscriber Diagnostic SM** + +3937 This parameter is used to indicate the reason why the subscriber is absent for 5G Non 3GPP access. For the values for +3938 this parameter see 3GPP TS 23.040. + +#### 3939 **7.6.8.36 SMSF 3GPP Delivery Outcome Indicator** + +3940 This parameter indicates that the delivery outcome IE is associated to the SM delivery via the SMSF for 3GPP access. + +#### 3941 7.6.8.37 SMSF Non-3GPP Delivery Outcome Indicator + +3942 This parameter indicates that the delivery outcome IE is associated to the SM delivery via the SMSF for Non-3GPP +3943 access. + +#### 3944 7.6.8.38 SMSF 3GPP SM Delivery Outcome + +3945 This parameter is used to indicate the delivery outcome at the SMSF for 3GPP access. + +#### 3946 7.6.8.39 SMSF Non-3GPP SM Delivery Outcome + +3947 This parameter is used to indicate the delivery outcome at the SMSF for non-3GPP access. + +#### 3948 7.6.8.40 SMSF 3GPP Absent Subscriber Diagnostic SM + +3949 This parameter is used to indicate the reason why the subscriber is absent for 5G 3GPP access. For the values for this +3950 parameter see 3GPP TS 23.040. + +#### 3951 7.6.8.41 SMSF Non 3GPP Absent Subscriber Diagnostic SM + +3952 This parameter is used to indicate the reason why the subscriber is absent for 5G Non 3GPP access. For the values for +3953 this parameter see 3GPP TS 23.040. + +### 3954 7.6.9 Access and signalling system related parameters + +#### 3955 7.6.9.1 AN-apdu + +3956 This parameter includes one or two concatenated complete 3GPP TS 25.413 or 3GPP TS 48.006 [48] messages, as +3957 described in 3GPP TS 23.009 and 3GPP TS 29.010. The access network protocol ID indicates that the message or +3958 messages are according to either 3GPP TS 48.006 [48] or 3GPP TS 25.413. For the coding of the messages see 3GPP +3959 TS 25.413, 3GPP TS 48.006 [48] and 3GPP TS 48.008 [49]. + +#### 3960 7.6.9.2 CM service type + +3961 This parameter identifies the service category being requested by the subscriber: + +- 3962 - mobile originating call; +- 3963 - emergency call establishment; +- 3964 - short message service; +- 3965 - mobile originating call re-establishment; +- 3966 - mobile terminating call; +- 3967 - SS request; +- 3968 - Voice group call set-up; +- 3969 - Voice broadcast set-up. + +#### 3970 7.6.9.3 Access connection status + +3971 This parameter represents the following access connection status information: + +- 3972 - RR-connection status (established/not established); +- 3973 - ciphering mode (on/off); +- 3974 - authentication status (authenticated/not authenticated). + +#### 3975 7.6.9.4 External Signal Information + +3976 This parameter contains concatenated information elements (including tag and length) which are defined by a common +3977 protocol version, preceded by the associated protocol ID. It is used to transport information of the indicated protocol via +3978 MAP interfaces. + +#### 3979 7.6.9.5 Access signalling information + +3980 This parameter refers to any set of information elements imported from 3GPP TS 24.008 [35]. + +#### 3981 7.6.9.6 Location update type + +3982 This parameter refers to the location update type (normal, periodic or IMSI attach) contained in the 3GPP TS 24.008 +3983 [35] LOCATION REGISTRATION REQUEST message. + +#### 3984 7.6.9.7 Protocol ID + +3985 This parameter refers to the protocol to which the coding of the content of the associated External Signal Information +3986 conforms. + +3987 The following values are defined: + +3988 - 04.08; + +3989 - 08.06; + +3990 - ETS 300 102-1. + +3991 This value indicates the protocol defined by ETS 300 102-1 (EDSS1). + +#### 3992 7.6.9.8 Network signal information + +3993 This parameter is transported as external signal information. The protocol ID shall be set to "ETS 300 102-1". + +3994 The network signal information may include the following information elements as defined in 3GPP TS 29.007 [56]: + +3995 - ISDN BC; the tag and length are defined by ETS 300 102-1. + +3996 For the content, see 3GPP TS 29.007 [56]. + +3997 - HLC; the tag and length are defined by ETS 300 102-1. + +3998 For the content, see 3GPP TS 29.007 [56]. + +3999 - LLC; the tag and length are defined by ETS 300 102-1. + +4000 For the content, see 3GPP TS 29.007 [56]. + +4001 They are contained in the Signal Information parameter according to figure 7.6/1 (irrespective of the order): + +![Diagram of Network signal information parameter structure showing three stacked blocks for ISDN BC TAG, HLC TAG, and LLC TAG, each with LENGTH and CONTENT fields.](b8d855a06aad434aeafa2739bf62e7de_img.jpg) + +| | +|-------------| +| ISDN BC TAG | +| LENGTH | +| CONTENT | +| HLC TAG | +| LENGTH | +| CONTENT | +| LLC TAG | +| LENGTH | +| CONTENT | + +Diagram of Network signal information parameter structure showing three stacked blocks for ISDN BC TAG, HLC TAG, and LLC TAG, each with LENGTH and CONTENT fields. + +4002 + +4003 + +**Figure 7.6/1: Network signal information parameter** + +4004 **7.6.9.8A Network signal information 2** + +4005 This parameter is transported as additional external signal information for SCUDIF calls, described in 3GPP TS 23.172 + 4006 [126]. The protocol ID and possibly included information elements are identical to Network Signal Information, defined + 4007 in 7.6.9.8, "Network signal information". + +4008 **7.6.9.9 Call Info** + +4009 This parameter is transported as external signal information. The protocol ID shall be set to "3GPP TS 24.008 [35]". + +4010 The Call Info includes the set of information elements from the original SETUP message and is imported from 3GPP + 4011 TS 24.008 [35]. + +4012 **7.6.9.10 Additional signal info** + +4013 This parameter is transported as external signal information. The protocol ID shall be set to "ETS 300 356". + +4014 The additional signal information may include the following information elements: + +4015 - Calling Party Number as defined by ETS 300 356. + +4016 - Generic Number as defined by ETS 300 356. + +4017 They are contained in the Signal Information parameter according to figure 7.6/2 (irrespective of the order): + +![Diagram of Additional signal information parameter structure showing two stacked blocks, each with three empty rows.](9400925a53bd0c7e071258c54cb15c15_img.jpg) + +| | +|--| +| | +| | +| | +| | +| | +| | + +Diagram of Additional signal information parameter structure showing two stacked blocks, each with three empty rows. + +4018 + +4019 + +**Figure 7.6/2: Additional signal information parameter** + +4020 **7.6.10 System operations parameters** + +#### 4021 7.6.10.1 Network resources + +4022 This parameter refers to a class or type of network resource: + +- 4023 - PLMN; +- 4024 - HLR; +- 4025 - VLR (current or previous); +- 4026 - MSC (controlling or current); +- 4027 - EIR; +- 4028 - radio sub-system. + +#### 4029 7.6.10.2 Trace reference + +4030 This parameter represents a reference associated with a GSM only tracing request as defined in 3GPP TS 52.008 [61]. + +4031 The parameter is managed by OMC/EM. + +#### 4032 7.6.10.2A Trace reference 2 + +4033 This parameter represents a reference associated with a tracing request as defined in 3GPP TS 32.421 [131] and 3GPP +4034 TS 32.422 [132]. The parameter is managed by EM. + +#### 4035 7.6.10.3 Trace type + +4036 This parameter identifies the type of trace for GSM only tracing request. Trace types are fully defined in 3GPP +4037 TS 52.008 [61]. If the activation of the tracing is requested only for UMTS, then this parameter shall contain value "No +4038 MSC Trace" for MSC Record Type and value "No BSS Trace" for BSS Record Type. + +#### 4039 7.6.10.4 Additional network resources + +4040 This parameter refers to a class or type of network resource: + +- 4041 - SGSN; +- 4042 - GGSN; +- 4043 - GMLC; +- 4044 - gsmSCF; +- 4045 - NPLR; +- 4046 - AuC. + +#### 4047 7.6.10.5 Trace depth list + +4048 This parameter identifies the list of depths of trace per network element. See 3GPP TS 32.422 [132]. + +#### 4049 7.6.10.6 Trace NE type list + +4050 This parameter identifies the list of network elements to be traced. See 3GPP TS 32.422 [132]. + +#### 4051 7.6.10.7 Trace interface list + +4052 This parameter identifies the list of interfaces or protocols per network element to be traced. See 3GPP TS 32.422 +4053 [132]. + +#### 4054 7.6.10.8 Trace event list + +4055 This parameter identifies the list of events per network element, which trigger a Trace Recording Session. See 3GPP TS +4056 32.422 [132]. + +#### 4057 **7.6.10.9 Trace support indicator** + +4058 This parameter indicates that UMTS trace parameters are supported in the VLR or in the SGSN. + +#### 4059 **7.6.10.10 Trace Propagation List** + +4060 This parameter indicates UMTS trace propagation parameters sent from one MSC to the other MSC in the signalling +4061 for inter MSC handover/relocation. See 3GPP TS 32.422 [132]. + +#### 4062 **7.6.10.11 MDT-Configuration** + +4063 This parameter contains Minimization of Drive Test Configuration Data as defined in 3GPP TS 32.422 [132]. + +#### 4064 **7.6.10.12 MDT User Consent** + +4065 This parameter contains an indicator whether user consent for MDT activation is available or not as defined in 3GPP TS +4066 32.422 [132]. + +### 4067 **7.6.11 Location Service Parameters** + +#### 4068 **7.6.11.1 Age of Location Estimate** + +4069 This parameter indicates how long ago the location estimate was obtained. + +#### 4070 **7.6.11.2 Deferred MT-LR Response Indicator** + +4071 This parameter shows that this is a response to a deferred mt-lr request. + +#### 4072 **7.6.11.3 Deferred MT-LR Data** + +4073 This parameter is used to report the deferred location event type, the location information and reason why the serving +4074 node aborted monitoring the event to the GMLC. The termination cause mt-lrRestart shall be used to trigger the GMLC +4075 to restart the location procedure in all the cases where the sending node detects that the location procedure cannot be +4076 successfully performed anymore by the sending node and that it could be successfully performed by another node (as +4077 for example when Cancel Location or Send Identification has been received). The location information shall be +4078 included only if the termination cause is mt-lrRestart. The network node number contained in the location information +4079 refers to the node where the MS/UE has moved to and shall be included if available, like in case Send Identification has +4080 been received. + +#### 4081 **7.6.11.4 LCS Client ID** + +4082 This parameter provides information related to the identity of an LCS client. + +#### 4083 **7.6.11.5 LCS Event** + +4084 This parameter identifies an event associated with the triggering of a location estimate. + +#### 4085 **7.6.11.6 Void** + +#### 4086 **7.6.11.7 LCS Priority** + +4087 This parameter gives the priority of the location request. + +#### 4088 **7.6.11.8 LCS QoS** + +4089 This parameter defines the Quality of Service (QoS) for any location request. It is composed of the following elements. + +4090 1) Response Time + +4091 Indicates the category of response time – "low delay" or "delay tolerant". + +4092 2) Horizontal Accuracy + +4093 Indicates the required horizontal accuracy of the location estimate. + +4094 3) Vertical Coordinate + +4095 Indicates if a vertical coordinate is required (in addition to horizontal coordinates). + +4096 4) Vertical Accuracy + +4097 Indicates the required vertical accuracy of the location estimate (inclusion is optional). + +4098 5) Velocity Request + +4099 Indicates that velocity should be returned if available (inclusion is optional). + +4100 6) LCS QoS Class + +4101 Indicates that LCS QoS Class should be applied if available - "best effort" or "assured" (inclusion is optional). + +#### 4102 7.6.11.9 CS LCS Not Supported by UE + +4103 This parameter is used by the VLR to indicate to the HLR that the UE does not support neither UE Based nor UE + +4104 Assisted positioning methods for Circuit Switched Location Services. VLR defines the presence of this parameter on the + +4105 basis of the Classmark 3 information. + +#### 4106 7.6.11.10 PS LCS Not Supported by UE + +4107 This parameter is used by the SGSN to indicate to the HLR that the UE does not support neither UE Based nor UE + +4108 Assisted positioning methods for Packet Switched Location Services. SGSN defines the presence of this parameter on + +4109 the basis of the UE capability information and the access technology supported by the SGSN. + +#### 4110 7.6.11.11 Location Estimate + +4111 This parameter gives an estimate of the location of an MS in universal coordinates and the accuracy of the estimate. The + +4112 estimate is expressed in terms of the geographical shapes defined by 3GPP TS 23.032. and is composed of the type of + +4113 shape plus the encoding of the shape itself. Any type of shape defined in 3GPP TS 23.032 can be filled in in the + +4114 Location Estimate parameter, but only the encoding of the following shapes shall be carried by Location Estimate: + +4115 - Ellipsoid point with uncertainty circle + +4116 - Ellipsoid point with uncertainty ellipse + +4117 - Ellipsoid point with altitude and uncertainty ellipsoid + +4118 - Ellipsoid arc + +4119 - Ellipsoid point + +4120 The encoding for the remaining types of shape, defined in the 3GPP TS 23.032, shall be filled in in the Additional + +4121 Location Estimate parameter. + +#### 4122 7.6.11.11A GERAN Positioning Data + +4123 This parameter provides positioning data associated with a successful or unsuccessful location attempt for a target MS + +4124 described in 3GPP TS 49.031 [59a]. + +#### 4125 7.6.11.11B UTRAN Positioning Data + +4126 This parameter provides positioning data associated with a successful location attempt for a target MS as described in +4127 3GPP TS 25.413 [120]. It contains the positioningDataDiscriminator and positioningDataSet parts of the RANAP +4128 PositionData element only. + +#### 4129 7.6.11.11C GERAN GANSS Positioning Data + +4130 This parameter provides GANSS positioning data associated with a successful or unsuccessful location attempt for a +4131 target MS as described in 3GPP TS 49.031 [59a] if GANSS has been used. + +#### 4132 7.6.11.11D UTRAN GANSS Positioning Data + +4133 This parameter provides GANSS positioning data associated with a successful location attempt for a target MS as +4134 described in 3GPP TS 25.413 [120] if GANSS has been used. It contains the GANSS-PositioningDataSet part of the +4135 RANAP PositionData element only. + +#### 4136 7.6.11.11E UTRAN Additional Positioning Data + +4137 This parameter provides additional positioning data associated with a successful location attempt for a target MS as +4138 described in 3GPP TS 25.413 [120] if Additional Positioning has been used. It contains the Additional- +4139 PositioningDataSet part of the RANAP PositionData element only. + +#### 4140 7.6.11.11F UTRAN Barometric Pressure Measurement + +4141 This parameter provides barometric pressure measurement associated with a successful location attempt for a target MS +4142 as described in 3GPP TS 25.413 [120]. + +#### 4143 7.6.11.11G UTRAN Civic Address + +4144 This parameter provides civic address associated with a successful location attempt for a target MS as described in +4145 3GPP TS 25.413 [120]. + +#### 4146 7.6.11.12 Location Type + +4147 This parameter indicates the type of location estimate required by the LCS client. Possible location estimate types include: + +- 4148 - current location; +- 4149 - current or last known location; +- 4150 - initial location for an emergency services call; +- 4151 - deferred location event type; +- 4152 - notification verification only. + +#### 4153 7.6.11.13 NA-ESRD + +4154 This parameter only applies to location for an emergency services call in North America and gives the North American +4155 Emergency Services Routing Digits. + +#### 4156 7.6.11.14 NA-ESRK + +4157 This parameter only applies to location for an emergency services call in North America and gives the North American +4158 Emergency Services Routing Key. + +#### 4159 7.6.11.15 LCS Service Type Id + +4160 This parameter defines the LCS Service Type of the current positioning request. The possible values are defined in +4161 3GPP TS 22.071 [123] + +#### 4162 7.6.11.16 Privacy Override + +4163 This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC/SGSN for an MT- +4164 LR are in the same country. + +#### 4165 7.6.11.17 Supported LCS Capability Sets + +4166 This parameter indicates which capability sets of LCS are supported in the VLR or SGSN. + +#### 4167 7.6.11.18 LCS Codeword + +4168 This parameter contains the codeword associated to current positioning request as described in 3GPP TS 23.271 [26a]. + +#### 4169 7.6.11.19 NA-ESRK Request + +4170 This parameter allows the MSC to indicate that it requires the GMLC to allocate a NA-ESRK based on the target MS +4171 location estimate. This parameter only applies to emergency services calls in North America. + +#### 4172 7.6.11.20 Supported GAD Shapes + +4173 This parameter indicates which of the shapes defined in 3GPP TS 23.032 are supported. If the parameter is not provided +4174 then the receiving node shall assume that the sending entity supports the following shapes: + +- 4175 - Ellipsoid point with uncertainty circle +- 4176 - Ellipsoid point with uncertainty ellipse +- 4177 - Ellipsoid point with altitude and uncertainty ellipsoid +- 4178 - Ellipsoid arc +- 4179 - Ellipsoid point + +#### 4180 7.6.11.21 Additional Location Estimate + +4181 This parameter gives an estimate of the location of an MS/UE in universal coordinates and the accuracy of the estimate. +4182 This parameter allows the location estimate to be expressed in any of the geographical shapes defined in 3GPP TS +4183 23.032 + +#### 4184 7.6.11.22 Cell Id Or SAI + +4185 For GERAN access, this parameter contains the Global Cell Identifier for the cell that the subscriber is currently +4186 attached to. For UTRAN access, this parameter contains the Service Area Identifier for the cell that the subscriber is +4187 currently attached to. + +#### 4188 7.6.11.23 LCS-Reference Number + +4189 This parameter represents a reference between a request and a response of a deferred mt-lr procedure as described in +4190 3GPP TS 23.271 [26a]. + +#### 4191 7.6.11.24 LCS Privacy Check + +4192 This parameter refers to the requested privacy check related actions (call/session unrelated and/or call/session related) +4193 from MSC or SGSN provided by H-GMLC. Possible requested actions are: + +- 4194 - positioning allowed without notifying the UE user; +- 4195 - positioning allowed with notification to the UE user; +- 4196 - positioning requires notification and verification by the UE user; positioning is allowed only if granted by the +4197 UE user or if there is no response to the notification; + +- 4198 - positioning requires notification and verification by the UE user; positioning is allowed only if granted by the +4199 UE user; +4200 - positioning not allowed. + +#### 4201 7.6.11.25 Additional LCS Capability Sets + +4202 This parameter indicates which capability sets of LCS are supported in the VLR or SGSN. + +#### 4203 7.6.11.26 Area Event Info + +4204 This parameter defines the requested deferred MT-LR area event information. The parameter consists of +4205 area definition, type of area event, occurrence info and minimum interval time. + +#### 4206 7.6.11.27 Velocity Estimate + +4207 This parameter gives an estimate of the velocity of an MS and the accuracy of the estimate. The estimate is expressed in +4208 terms of speed and bearing as defined by 3GPP TS 23.032 [122], and is composed of the velocity terms plus the +4209 encoding of the velocity itself. Only the encoding of the following velocity definitions shall be carried by the Velocity +4210 Estimate: + +- 4211 - Horizontal Velocity +- 4212 - Horizontal with Vertical Velocity +- 4213 - Horizontal Velocity with Uncertainty +- 4214 - Horizontal with Vertical Velocity and Uncertainty + +#### 4215 7.6.11.28 Accuracy Fulfilment Indicator + +4216 This parameter indicates the fulfilled accuracy of the positioning procedure. For details see 3GPP TS +4217 23.271 [26a]. + +#### 4218 7.6.11.29 MO-LR Short Circuit Indicator + +4219 This parameter indicates whether MO-LR short circuit feature is permitted. For details see 3GPP TS +4220 23.271 [26a]. + +#### 4221 7.6.11.30 Reporting PLMN List + +4222 This parameter provides a list of PLMNs in which subsequent periodic MO-LR TTTP requests will be +4223 made. For details see 3GPP TS 23.271 [26a]. + +#### 4224 7.6.11.31 Periodic LDR information + +4225 This parameter refers to the periodic reporting interval and reporting amount of the deferred periodic +4226 location. For details see 3GPP TS 23.271 [26a]. + +#### 4227 7.6.11.32 Sequence Number + +4228 This parameter refers to the number of the periodic location reports completed. The sequence number +4229 would be set to 1 in the first location report and increment by 1 for each new report. When the number +4230 reaches the reporting amount value, the H-GMLC (for a periodic MT-LR or a periodic MO-LR transfer to +4231 third party) will know the procedure is complete. For details see 3GPP TS 23.271 [26a]. + +#### 4232 7.6.12 Void + +4233 + +4234 **7.7 Representation of a list of a basic parameter in service-primitives** +4235 + +4236 In some service-primitives several instances of a basic parameter of clause 7.6 are required. In the service descriptions +4237 such cases will be represented as + +4238 + +| | +|-------------------| +| ParameterNameLIST | +|-------------------| + +4239 in the tables where ParameterName refers to one of the parameters defined in clause 7.6. This corresponds to the +4240 following construction rule: + +![Diagram showing the construction of lists. A horizontal line has a box labeled 'Parameter' in the center. Above this box, a line extends to the left and right, with a right-pointing arrowhead on the right side, indicating a list construction rule.](54159e6d8f5ecc73ad262758e3a60677_img.jpg) + +4241 + +Diagram showing the construction of lists. A horizontal line has a box labeled 'Parameter' in the center. Above this box, a line extends to the left and right, with a right-pointing arrowhead on the right side, indicating a list construction rule. + +4242 **Figure 7.7/1: Construction of Lists** + +4243 **8 Mobility services** + +4244 **8.1 Location management services** + +4245 **8.1.1 Void** + +4246 **8.1.1.1 Void** + +4247 **8.1.1.2 Void** + +4248 **8.1.1.3 Void** + +4249 **8.1.2 MAP\_UPDATE\_LOCATION service** + +4250 **8.1.2.1 Definition** + +4251 This service is used by the VLR to update the location information stored in the HLR. + +4252 This service is also used by an IWF that registers an MME as MSC for MT-SMS. + +4253 The MAP\_UPDATE\_LOCATION service is a confirmed service using the service primitives given in table 8.1/2. + +4254 **8.1.2.2 Service primitives** + +4255 **Table 8.1/2: MAP\_UPDATE\_LOCATION** + +| Parameter name | Request | Indication | Response | Confirm | +|---------------------------------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| MSC Address | M | M(=) | | | +| VLR number | M | M(=) | | | +| LMSI | U | C(=) | | | +| Supported CAMEL Phases | C | C(=) | | | +| SoLSA Support Indicator | C | C(=) | | | +| IST Support Indicator | C | C(=) | | | +| Super-Charger Supported in Serving Network Entity | C | C(=) | | | +| Long FTN Supported | C | C(=) | | | +| Supported LCS Capability Sets | C | C(=) | | | + +| | | | | | +|---------------------------------|---|------|---|------| +| Offered CAMEL 4 CSIs | C | C(=) | | | +| Inform Previous Network Entity | C | C(=) | | | +| CS LCS Not Supported by UE | C | C(=) | | | +| V-GMLC Address | U | C(=) | | | +| IMEISV | C | C(=) | | | +| Skip Subscriber Data Update | U | C(=) | | | +| Supported RAT Types Indicator | U | C(=) | | | +| Paging Area | U | C(=) | | | +| Restoration Indicator | U | C(=) | | | +| MTRF Supported | U | C(=) | | | +| Equivalent PLMN List | C | C(=) | | | +| MSISDN-less Operation Supported | C | C(=) | | | +| MME-Diameter-Address-For MT-SMS | C | C(=) | | | +| Reset-IDs Supported | C | C(=) | | | +| ADD Capability | | | U | C(=) | +| Paging Area Capability | | | U | C(=) | +| HLR number | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +4256 + +### 4257 8.1.2.3 Parameter definitions and use + +#### 4258 Invoke Id + +4259 See definition in clause 7.6.1. + +#### 4260 IMSI + +4261 See definition in clause 7.6.2. + +#### 4262 MSC Address + +4263 See definition for MSC number in clause 7.6.2. The MSC address is used for short message delivery only and for each +4264 incoming call set-up attempt the MSRN will be requested from the VLR. + +#### 4265 VLR number + +4266 See definition in clause 7.6.2. + +#### 4267 LMSI + +4268 See definition in clause 7.6.2. It is an operator option to provide the LMSI from the VLR; it is mandatory for the HLR +4269 to support the LMSI handling procedures. + +#### 4270 Supported CAMEL Phases + +4271 This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from +4272 phase 1 is supported. Otherwise may be absent. + +#### 4273 HLR number + +4274 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating. + +#### 4275 SoLSA Support Indicator + +4276 This parameter is used by the VLR to indicate to the HLR in the Update Location indication that SoLSA is supported. If +4277 this parameter is not included in the Update Location indication and the Subscriber is marked as only allowed to roam +4278 in Subscribed LSAs, then the HLR shall reject the roaming and indicate to the VLR that roaming is not allowed to that +4279 Subscriber in the VLR. + +4280 This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a +4281 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support +4282 indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted. + +#### 4283 IST Support Indicator + +4284 This parameter is used to indicate to the HLR that the VMSC supports basic IST functionality, that is, the VMSC is able +4285 to terminate the Subscriber Call Activity that originated the IST Alert when it receives the IST alert response indicating +4286 that the call(s) shall be terminated. If this parameter is not included in the Update Location indication and the +4287 Subscriber is marked as an IST Subscriber, then the HLR may limit the service for the subscriber (by inducing an +4288 Operator Determined barring of Roaming, Incoming or Outgoing calls), or allow service assuming the associated risk of +4289 not having the basic IST mechanism available. + +4290 This parameter can also indicate that the VMSC supports the IST Command service, including the ability to terminate +4291 all calls being carried for the identified subscriber by using the IMSI as a key. If this additional capability is not +4292 included in the Update Location indication and the HLR supports the IST Command capability, then the HLR may limit +4293 the service for the subscriber (by inducing an Operator Determined barring of Roaming, Incoming or Outgoing calls), or +4294 allow service assuming the associated risk of not having the IST Command mechanism available. + +4295 Long FTN Supported + +4296 This parameter indicates that the VLR supports Long Forwarded-to Numbers. + +4297 Super-Charger Supported in Serving Network Entity + +4298 This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality and +4299 whether subscription data has been retained by the VLR. If subscription data has been retained by the VLR the age +4300 indicator shall be included. Otherwise the VLR shall indicate that subscriber data is required. + +4301 If this parameter is absent then the VLR does not support the Super-Charger functionality. + +4302 Supported LCS Capability Sets + +4303 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no +4304 capability set is marked as supported then the VLR does not support LCS at all. + +4305 If this parameter is absent then the VLR may support at most LCS capability set 1, that is LCS Release98 or Release99 +4306 version. + +4307 Offered CAMEL 4 CSIs + +4308 This parameter indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR (see clause 7.6.3.36D). + +4309 Inform Previous Network Entity + +4310 This parameter is used by the VLR to ask the HLR to inform the previous network entity about the update by sending +4311 the previous network entity a Cancel Location message. It is used if Super-Charger is supported in the network and +4312 either the serving network entity has not been able to inform the previous network entity that MS has moved (i.e. if it +4313 has not sent Send Identification to the previous serving entity) or the MTRF Supported flag is set in the MAP\_UPDATE +4314 LOCATION request. + +4315 CS LCS Not Supported by UE + +4316 See definition in clause 7.6.11. + +4317 V-GMLC address + +4318 See definition in clause 7.6.2. + +4319 IMEISV + +4320 For definition of the parameter see clause 7.6.2. For the use of this parameter see 3GPP TS 23.012. IMEISV shall be +4321 present if ADD function is supported and a new IMEISV is to be notified to the HLR (The functional requirements for +4322 the presence of IMEISV due to ADD are described in 3GPP TS 22.101 clause 7.4). + +4323 Skip Subscriber Data Update + +4324 The presence of the parameter is optional and if present it indicates that the service is solely used to inform the HLR +4325 about change of IMEISV or Paging Area. The parameter is used to optimise signalling load during Location Update +4326 procedure. + +4327 Supported RAT Types Indicator + +4328 This parameter indicates, if present, which access technologies (e.g. GERAN and / or UTRAN) are served by the +4329 MSC/VLR (see clause 7.6.3) + +4330 Paging Area + +4331 This parameter indicates, if present, the paging area where the MS is currently located (see clause 7.6.5.18) + +4332 Restoration Indicator + +4333 This parameter indicates, if present, that the HLR shall send in the MAP-INSERT-SUBSCRIBER-DATA the MME +4334 Name if the subscriber is registered to EPS, or the SGSN Number if available and if the subscriber is registered to +4335 GPRS. The VLR may set this indicator during a CSFB mobile originated call if the VLR performs an implicit location +4336 update (see 3GPP TS 23.272 [143]). + +4337 MTRF Supported + +4338 See 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence. + +4339 Equivalent PLMN List + +4340 This parameter indicates the equivalent PLMN list of which the VLR requests the corresponding CSG Subscription +4341 data. + +4342 MSISDN-less Operation Supported + +4343 See clause 3.6.1.5 of 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence. + +4344 MME-Diameter-Address-For-MT-SMS + +4345 This parameter may be sent by an IWF that registers an MME for MT-SMS. The MME-Diameter-Address-For-MT- +4346 SMS may be stored in the HLR and may be sent in SMS interrogation responses to SMS-GMSCs. + +4347 Reset-IDs Supported + +4348 This parameter indicates, if present, the support of Reset-IDs by the MSC. + +4349 ADD Capability + +4350 This parameter indicates, if present, the support of ADD function by the HLR. + +4351 Paging Area Capability + +4352 This parameter indicates, if present, the support of Paging Area function by the HLR. The HLR shall report the same +4353 capability for all subscribers. + +4354 User error + +4355 In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in +4356 clause 7.6.1 may be used, depending on the nature of the fault: + +4357 - unknown subscriber; + +4358 - roaming not allowed; + +4359 This cause will be sent if the MS is not allowed to roam into the PLMN indicated by the VLR number. The +4360 cause is qualified by the roaming restriction reason "PLMN Not Allowed", "Supported RAT Types Not +4361 Allowed" or "Operator Determined Barring". If no qualification is received (HLR with MAP Version 1), +4362 "PLMN Not Allowed" is taken as default. + +4363 This cause shall be used when the HLR rejects a MAP Update Location request received for an MSISDN- +4364 less subscription from a VLR not supporting MSISDN-less operation (see clause 3.6.1.5 of 3GPP TS 23.012 +4365 [23]). + +4366 - system failure; + +4367 - unexpected data value. + +4368 Provider error + +4369 For definition of provider errors see clause 7.6.1. + +### 4370 8.1.3 MAP\_CANCEL\_LOCATION service + +#### 4371 8.1.3.1 Definition + +4372 This service is used between HLR and VLR to delete a subscriber record from the VLR. It may be invoked +4373 automatically when an MS moves from one VLR area to another, to remove the subscriber record from the old VLR, or +4374 by the HLR operator to enforce a location updating from the VLR to the HLR, e.g. on withdrawal of a subscription. + +4375 Also this service is used between HLR and SGSN to delete a subscriber record from the SGSN. It may be invoked +4376 automatically when an MS moves from one SGSN area to another, to remove the subscriber record from the old SGSN, +4377 or by the HLR operator to enforce a location updating from the SGSN to the HLR. This service is also used to request +4378 the SGSN to indicate to the MS to initiate an immediate re-attach procedure. + +4379 In an EPS this service is used between HSS and IWF and between IWF and IWF to delete the subscriber record from +4380 the MME or SGSN or to release bearer resources without deleting the subscriber record. This service is also used to +4381 request the MME or SGSN to indicate to the UE to initiate an immediate re-attach procedure. + +4382 The MAP\_CANCEL\_LOCATION service is a confirmed service using the primitives defined in table 8.1/3. + +#### 4383 8.1.3.2 Service primitives + +4384 **Table 8.1/3: MAP\_CANCEL\_LOCATION** + +| Parameter name | Request | Indication | Response | Confirm | +|-----------------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| LMSI | C | C(=) | | | +| Cancellation Type | C | C(=) | | | +| MTRF Supported And Authorized | U | C(=) | | | +| MTRF Supported And Not Authorized | U | C(=) | | | +| New MSC Number | U | C(=) | | | +| New VLR Number | U | C(=) | | | +| New LMSI | U | C(=) | | | +| Reattach Required | U | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +4385 + +#### 4386 8.1.3.3 Parameter definitions and use + +4387 Invoke Id + +4388 See definition in clause 7.6.1. + +4389 IMSI + +4390 See definition in clause 7.6.2. + +4391 LMSI + +4392 See definition in clause 7.6.2. The LMSI shall be included if it has been received from VLR. LMSI is not applicable +4393 between SGSN and HLR. + +4394 Value 0000 0000 can be used to indicate that the LMSI is not in use. + +4395 Cancellation Type + +4396 See definition in clause 7.6.3. The presence of this parameter is mandatory when the Cancel Location is sent to the +4397 SGSN or IWF. The parameter may also be sent during an inter-VLR location update If the VLR receives this parameter +4398 and does not understand it the VLR shall ignore it and should by default assume an Update procedure. If the SGSN +4399 receives this parameter indicating initial attach procedure, the SGSN shall do as specified in 3GPP TS 23.060 [104], and +4400 shall not delete the subscription data. + +4401 MTRF Supported And Authorized + +4402 See 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence. + +4403 MTRF Supported And Not Authorized + +4404 See 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence. + +4405 New MSC Number + +4406 This parameter refers to the E.164 address of the new VMSC. The use and conditions of presence of this parameter are +4407 specified in 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23]. This parameter shall be present if the MTRF Supported +4408 And Authorized flag is present. + +4409 New VLR Number + +4410 This parameter contains the new VLR Number. See definition in clause 7.6.2. The use and conditions of presence of +4411 this parameter are specified in 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23]. This parameter shall be present if the +4412 MTRF Supported And Authorized flag is present. + +4413 New LMSI + +4414 See definition in clause 7.6.2 for LMSI. This parameter shall be present if the MTRF Supported And Authorized flag is +4415 present and the HLR has received the LMSI in Update Location from the new VLR. + +4416 Reattach Required + +4417 When present and when the Cancellation Type indicates a subscription withdraw, this parameter indicates that the +4418 MME (informed via the IWF) or the SGSN shall delete the subscription data and request the UE or MS to initiate an +4419 immediate re-attach procedure as described in 3GPP TS 23.401 [145] and in 3GPP TS 23.060 [12]. + +4420 User error + +4421 If the cancellation fails, an error cause is to be returned by the VLR or by the SGSN or IWF. One of the following error +4422 causes defined in clause 7.6.1 shall be used: + +- 4423 - unexpected data value; +- 4424 - data missing. + +4425 Provider error + +4426 For definition of provider errors see clause 7.6.1. + +## 4427 8.1.4 MAP\_SEND\_IDENTIFICATION service + +### 4428 8.1.4.1 Definition + +4429 The MAP\_SEND\_IDENTIFICATION service is used between a VLR and a previous VLR to retrieve IMSI and +4430 authentication data for a subscriber registering afresh in that VLR. + +4431 It may also be used to send the MSC number from a VLR to a previous VLR. + +4432 The MAP\_SEND\_IDENTIFICATION service is a confirmed service using the service primitives defined in table 8.1/4. + +### 4433 8.1.4.2 Service primitives + +4434 **Table 8.1/4: MAP\_SEND\_IDENTIFICATION** + +| Parameter name | Request | Indication | Response | Confirm | +|-----------------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| TMSI | M | M(=) | | | +| Number of requested vectors | M | M(=) | | | +| Segmentation prohibited indicator | C | C(=) | | | +| MSC Number | U | C(=) | | | +| Previous Location Area Id | U | C(=) | | | +| Hop Counter | U | C(=) | | | +| MTRF Supported | U | C(=) | | | +| VLR Number | U | C(=) | | | +| New LMSI | U | C(=) | | | +| IMSI | | | C | C(=) | +| Authentication set | | | U | C(=) | +| Current Security Context | | | U | C(=) | +| MT call pending flag | | | U | C(=) | +| Last used LTE PLMN ID | | | U | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +4435 + +#### 4436 8.1.4.3 Parameter definitions and use + +##### 4437 Invoke Id + +4438 See definition in clause 7.6.1. + +##### 4439 TMSI + +4440 See definition in clause 7.6.2. + +4441 If multiple service requests are present in a dialogue then this parameter shall be present in every service request. + +##### 4442 Number of requested vectors + +4443 A number indicating how many authentication vectors the new VLR is prepared to receive. The previous VLR shall not +4444 return more vectors than indicated by this parameter. + +4445 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a +4446 dialogue then this parameter shall not be present in any service request other than the first one + +##### 4447 Segmentation prohibited indicator + +4448 This parameter indicates if the new VLR or SGSN allows segmentation of the response at MAP user level. + +4449 This parameter may be present only in the first request of the dialogue. + +##### 4450 IMSI + +4451 See definition in clause 7.6.2. The IMSI is to be returned if the service succeeds. + +4452 If multiple service requests are present in a dialogue and the service succeeds then this parameter shall not be present in +4453 any service response other than the first one + +##### 4454 MSC Number + +4455 This is the ISDN number assigned to the MSC currently serving the MS. This parameter shall be present if the MTRF +4456 Supported flag is present. + +##### 4457 Previous Location Area Id + +4458 See definition in clause 7.6.2. Together with the TMSI the Previous Location Area Id can be used to derive the IMSI. + +4459 Authentication set + +4460 See definition in clause 7.6.7. If the service succeeds a list of up to five authentication sets is returned, if there are any +4461 available. + +4462 Current Security Context + +4463 See definition in clause 7.6.7. If the service succeeds, a list of either GSM or UMTS Security Context parameters can be +4464 returned. + +4465 This parameter shall not be included if the Key Status associated to the current security context indicates this is a new +4466 keyset that has not been used yet. If this parameter is present in the message, the new VLR shall consider that the keyset +4467 has already been used (i.e. the key status is "old"). + +4468 MT call pending flag + +4469 This flag indicates by its presence that there is a Mobile Terminating call pending in the old MSC/VLR. See 3GPP TS +4470 23.018 [97] for the use of this parameter and the conditions for its presence. + +4471 Hop Counter + +4472 For the use of this parameter see 3GPP TS 23.012 [23]. + +4473 MTRF Supported + +4474 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. + +4475 VLR Number + +4476 This is the ISDN number assigned to the VLR currently serving the MS. See definition in clause 7.6.2. The use and +4477 conditions of presence of this parameter are specified in 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23]. This +4478 parameter shall be present if the MTRF Supported flag is present. + +4479 New LMSI + +4480 See definition in clause 7.6.2 for LMSI. This parameter may be present if the MTRF Supported flag is present. + +4481 Last used LTE PLMN ID + +4482 See 3GPP TS 23.272 [143] for the use of this parameter and the conditions for its presence. + +4483 User error + +4484 This parameter is mandatory if the service fails. The following error cause defined in clause 7.6.1 may be used, +4485 depending on the nature of the fault: + +4486 - unidentified subscriber. + +4487 Provider error + +4488 For definition of provider errors see clause 7.6.1. + +4489 **8.1.5 Void** + +4490 **8.1.5.1 Void** + +4491 **8.1.5.2 Void** + +4492 **8.1.5.3 Void** + +4493 **8.1.6 MAP\_PURGE\_MS service** + +4494 **8.1.6.1 Definition** + +4495 This service is used between the VLR and the HLR to cause the HLR to mark its data for an MS so that any request for + 4496 routing information for a mobile terminated call or a mobile terminated short message will be treated as if the MS is not + 4497 reachable. It is invoked when the subscriber record for the MS is to be deleted in the VLR, either by MMI interaction or + 4498 automatically, e.g. because the MS has been inactive for several days. This service shall not be used if both the VLR + 4499 and HLR support the Super-Charger functionality. + +4500 Also this service is used between the SGSN and the HLR to cause the HLR to mark its data for an MS so that any + 4501 request for routing information for a mobile terminated short message or a network requested PDP-context activation + 4502 will be treated as if the MS is not reachable. It is invoked when the subscriber record for the MS is to be deleted in the + 4503 SGSN, either by MMI interaction or automatically, e.g. because the MS has been inactive for several days. This service + 4504 shall not be used if both the SGSN and HLR support the Super-Charger functionality. + +4505 In an EPS this service is used between IWF and IWF and between IWF and HSS. + +4506 The MAP\_PURGE\_MS service is a confirmed service using the primitives defined in table 8.1/6. + +### 4507 8.1.6.2 Service primitives + +4508 + +**Table 8.1/6: MAP\_PURGE\_MS** + +| Parameter name | Request | Indication | Response | Confirm | +|---------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| VLR number | C | C(=) | | | +| Freeze TMSI | | | C | C(=) | +| Freeze P-TMSI | | | C | C(=) | +| Freeze M-TMSI | | | C | C(=) | +| SGSN number | C | C(=) | | | +| Last known location | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +4509 + +### 4510 8.1.6.3 Parameter definitions and use + +4511 Invoke ID + +4512 See definition in clause 7.6.1. + +4513 IMSI + +4514 See definition in clause 7.6.2. + +4515 VLR number + +4516 Shall be present if the sender is VLR. See definition in clause 7.6.2. + +4517 SGSN number + +4518 Shall be present if the sender is SGSN. See definition in clause 7.6.2. + +4519 In an EPS, this parameter may contain the IWF number. + +4520 Freeze TMSI + +4521 This parameter is sent to the VLR to indicate that the TMSI has to be frozen. It shall be present if the received VLR + 4522 number matches the stored VLR number. + +4523 Freeze P-TMSI + +4524 This parameter is sent to the SGSN to indicate that the P-TMSI has to be frozen. It shall be present if the received + 4525 SGSN number matches the stored SGSN number. + +4526 Freeze M-TMSI + +4527 This parameter is sent to the IWF to indicate that the M-TMSI has to be frozen. It shall be present if the received node + 4528 number matches the stored IWF number. + +4529 Last known location + +4530 This parameter contains the last known location of the purged UE. + +4531 User error + +4532 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +- 4533 - Data Missing; +- 4534 - Unexpected Data Value; +- 4535 - Unknown Subscriber. + +4536 Provider error + +4537 See definition of provider errors in clause 7.6.1. + +## 4538 8.1.7 MAP\_UPDATE\_GPRS\_LOCATION service + +### 4539 8.1.7.1 Definition + +4540 This service is used by the SGSN to update the location information stored in the HLR. + +4541 In an EPS, this service is used between IWF and IWF and between IWF and HSS. + +4542 The MAP\_UPDATE\_GPRS\_LOCATION service is a confirmed service using the service primitives given in + 4543 table 8.1/7. + +### 4544 8.1.7.2 Service primitives + +4545 **Table 8.1/7: MAP\_UPDATE\_GPRS\_LOCATION** + +| Parameter name | Request | Indication | Response | Confirm | +|---------------------------------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| SGSN number | M | M(=) | | | +| SGSN address | M | M(=) | | | +| Supported CAMEL Phases | C | C(=) | | | +| SoLSA Support Indicator | C | C(=) | | | +| Super-Charger Supported in Serving Network Entity | C | C(=) | | | +| GPRS enhancements support indicator | C | C(=) | | | +| Supported LCS Capability Sets | C | C(=) | | | +| Offered CAMEL 4 CSIs | C | C(=) | | | +| Inform Previous Network Entity | C | C(=) | | | +| PS LCS Not Supported by UE | C | C(=) | | | +| V-GMLC Address | U | C(=) | | | +| Call barring support indicator | C | C(=) | | | +| IMEISV | C | C(=) | | | +| Skip Subscriber Data Update | U | C(=) | | | +| Supported RAT Types Indicator | U | C(=) | | | +| EPS Info | C | C(=) | | | +| Serving Node Type Indicator | C | C(=) | | | +| Supported Features | U | C(=) | | | +| Used RAT Type | U | C(=) | | | +| GPRS Subscription Data not needed Indicator | C | C(=) | | | +| EPS Subscription Data Not Needed Indicator | C | C(=) | | | +| Node-Type-Indicator | U | C(=) | | | +| Area Restricted Indicator | C | C(=) | | | +| UE Reachable Indicator | C | C(=) | | | +| T-ADS Data Retrieval Support Indicator | C | C(=) | | | + +| Parameter name | Request | Indication | Response | Confirm | +|-------------------------------------------------------------|---------|------------|----------|---------| +| Homogeneous Support Of IMS Voice Over PS Sessions | C | C(=) | | | +| Update of Homogeneous Support Of IMS Voice Over PS Sessions | C | C(=) | | | +| UE SRVCC Capability | C | C(=) | | | +| Equivalent PLMN List | C | C(=) | | | +| MME Number for MT SMS | C | C(=) | | | +| SMS-Only | C | C(=) | | | +| SMS Register Request | C | C(=) | | | +| Removal of MME Registration for SMS | C | C(=) | | | +| MSISDN-less Operation Supported | C | C(=) | | | +| SGSN Name | C | C(=) | | | +| SGSN Realm | C | C(=) | | | +| Lgd Support Indicator | C | C(=) | | | +| Adjacent-PLMNs | C | C(=) | | | +| Reset-IDs Supported | C | C(=) | | | +| ADD Capability | | | U | C(=) | +| SGSN-MME Separation Support Indicator | | | C | C(=) | +| HLR number | | | C | C(=) | +| MME Registered for SMS | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +4546 + +### 4547 8.1.7.3 Parameter definitions and use + +#### 4548 Invoke Id + +4549 See definition in clause 7.6.1. + +#### 4550 IMSI + +4551 See definition in clause 7.6.2. + +#### 4552 SGSN number + +4553 See definition in clause 7.6.2. + +4554 In an EPS, this parameter is populated with an IWF number if received from an IWF. + +#### 4555 SGSN address + +4556 See definition in clause 7.6.2. + +4557 In an EPS, this parameter is populated with an IWF address if received from an IWF. + +#### 4558 Supported CAMEL Phases + +4559 This parameter indicates which phases of CAMEL are supported. The SGSN can only support CAMEL phase 3 or greater. + +#### 4561 SoLSA Support Indicator + +4562 This parameter is used by the SGSN to indicate to the HLR in the Update GPRS Location indication that SoLSA is +4563 supported. If this parameter is not included in the Update GPRS Location indication and the Subscriber is marked as +4564 only allowed to roam in Subscribed LSAs, then the HLR shall reject the roaming and indicate to the SGSN that roaming +4565 is not allowed to that Subscriber in the SGSN. + +4566 This SoLSA Support Indicator shall be stored by the HLR per SGSN where there are Subscribers roaming. If a +4567 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a SGSN and no SoLSA Support +4568 indicator is stored for that SGSN, the location status of that Subscriber has to be set to Restricted. + +#### 4569 Super-Charger Supported in Serving Network Entity + +4570 This parameter is used by the SGSN to indicate to the HLR that the SGSN supports the Super-Charger functionality and +4571 whether subscription data has been retained by the SGSN. If subscription data has been retained by the SGSN the age +4572 indicator shall be included. Otherwise the SGSN shall indicate that subscriber data is required. + +4573 If this parameter is absent then the SGSN does not support the Super-Charger functionality. + +4574 GPRS enhancements support indicator + +4575 This parameter is used by the SGSN to indicate to the HLR in the Update GPRS Location indication that GPRS +4576 enhancements are supported. If this parameter is included in the Update GPRS Location indication the HLR may send +4577 the extension QoS parameter in the PDP contexts to the SGSN. The HLR may send the extension-2 QoS, the +4578 extension-3 QoS and the extension-4 QoS parameters with the extension QoS parameter. + +4579 HLR number + +4580 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating. + +4581 Supported LCS Capability Sets + +4582 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no +4583 capability set is marked as supported then the SGSN does not support LCS at all. + +4584 The SGSN is not allowed to indicate support for LCS capability set 1. + +4585 If this parameter is absent then the SGSN does not support LCS at all. + +4586 Offered CAMEL 4 CSIs + +4587 This parameter indicates the CAMEL phase 4 CSIs offered in the SGSN (see clause 7.6.3.36D). + +4588 Inform Previous Network Entity + +4589 This parameter is used by the SGSN to ask the HLR to inform the previous network entity about the update by sending +4590 the previous network entity a Cancel Location message. It is used in case Super-Charger is supported in the +4591 network and the serving network entity has not been able to inform the previous network entity that MS has moved, that +4592 is if it has not sent SGSN Context Request to the previous serving entity. + +4593 PS LCS Not Supported by UE + +4594 See definition in clause 7.6.11. + +4595 V-GMLC address + +4596 See definition in clause 7.6.2. + +4597 Call Barring support indicator + +4598 See definition in clause 7.6.3.92. + +4599 IMEISV + +4600 For definition of the parameter see clause 7.6.2. For the use of this parameter see 3GPP TS 23.060. IMEISV shall be +4601 present if ADD function is supported and the IMEISV is new in SGSN (The functional requirements for the presence of +4602 IMEISV due to ADD are described in 3GPP TS 22.101 clause 7.4). + +4603 Skip Subscriber Data Update + +4604 The presence of the parameter is optional and if present it indicates that subscriber data download during the +4605 updateGprsLocation procedure may be skipped by the HLR e.g. because the service is solely used to inform the HLR +4606 about change of IMEISV. The parameter is used to optimise signalling load during Location Update procedure. + +4607 Supported RAT Types Indicator + +4608 This parameter indicates, if present, which access technologies (e.g. GERAN and/or UTRAN and/or E-UTRAN) are +4609 served by the SGSN or MME (see clause 7.6.3) + +4610 EPS Info + +4611 This parameter may indicate that the MME or SGSN has selected a new PDN GW for an APN. If so, the HSS shall skip +4612 subscriber data update (insert subscriber data) and only note the new PDN GW. + +4613 Otherwise this parameter may indicate the appropriate instruction to be performed by the HSS which is one or more of + +- 4614 a) Update Location; i.e. send CancelLocation to the old MME and replace the stored MME id (if Serving Node +4615 Type Indicator is present and the stored MME id is different from the received MME id), or send +4616 CancelLocation to the old SGSN and replace the stored SGSN id (if Serving Node Type Indicator is absent and +4617 the stored SGSN id is different from the received SGSN id); +- 4618 b) Cancel SGSN; i.e. send CancelLocation to the SGSN and delete the stored SGSN id. +- 4619 c) Initial Attach; i.e. send CancelLocation to the MME (if Serving Node Type Indicator is absent) or to the SGSN +4620 (if Serving Node Type Indicator is present) with cancellation type set to "initial attach procedure" + +#### 4621 Serving Node Type Indicator + +4622 This parameter indicates by its presence that the subscriber's serving node is an MME (which is either stand alone or +4623 combined with an SGSN) and it indicates by its absence that the subscriber's serving node is an SGSN (which is either +4624 stand alone or combined with an MME). + +#### 4625 Supported Features + +4626 This parameter shall be used by an IWF to forward feature support indications as received from the MME or SGSN via +4627 S6a/S6d. It shall also be used by the SGSN to indicate support of the Dedicated Core Network functionality to the HLR. + +#### 4628 Used RAT Type + +4629 This parameter may indicate the RAT type currently used by the serving node. + +#### 4630 GPRS Subscription Data not needed Indicator + +4631 This parameter indicates by its presence that the SGSN (or MME/IWF) does not request GPRS Subscription Data in +4632 addition to EPS Subscription Data. + +#### 4633 EPS Subscription Data Not Needed Indicator + +4634 This parameter indicates by its presence that the SGSN does not request EPS Subscription Data in addition to GPRS +4635 Subscription Data. + +4636 NOTE: The indicator is only applicable to an SGSN which only supports Gn and Gp interfaces and does not +4637 support S4 interface. + +#### 4638 Node-Type Indicator + +4639 This parameter indicates by its presence that the requesting node is a combined MME/SGSN. Absence of this Indicator +4640 indicates that the requesting node is a single MME or SGSN. + +4641 When Node-Type Indicator is absent and Serving Node Type Indicator is present, the HSS may skip checking +4642 SMS/LCS supported features and skip the download of SMS/LCS-related subscription data to a standalone MME. + +#### 4643 Area Restricted Indicator + +4644 This parameter indicates by its presence that the network node area is restricted due to regional subscription. This +4645 parameter is used by the IWF only. + +#### 4646 UE-Reachable Indicator + +4647 This parameter indicates by its presence that the UE is reachable. + +4648 NOTE: In general any UpdateGPRS-Location request message (with or without UE-Reachable Indicator) +4649 implicitly conveys the information that the UE is now reachable. + +4650 This explicit indicator shall be set only when UpdateGPRS-Location is used for the only and no other purpose than +4651 indicating UE reachability. The HLR shall skip subscriber data downloading and any mobility management +4652 functionality other than reporting the UE's reachability to relevant core network entities. + +4653 T-ADS Data Retrieval Support Indicator + +4654 This parameter indicates by its presence that the SGSN supports retrieval of T-ADS data with the Provide-Subscriber- +4655 Info service. + +4656 Homogeneous Support Of IMS Voice Over PS Sessions + +4657 This parameter when present indicates that IMS voice over PS sessions is homogeneously supported in the complete +4658 SGSN area or that IMS voice over PS sessions is homogeneously not supported in the complete SGSN area. + +4659 Update of Homogeneous Support Of IMS Voice Over PS Sessions + +4660 This parameter when present indicates that Homogeneous Support of IMS Voice Over PS Sessions is updated. If the +4661 Homogeneous Support of IMS Voice Over PS Session is not present, the value of the Homogeneous Support of IMS +4662 Voice Over PS Sessions shall be updated as unknown to the serving node. + +4663 UE SRVCC Capability + +4664 See definition in clause 7.6.3.99. + +4665 Equivalent PLMN List + +4666 This parameter indicates the equivalent PLMN list of which the MME/SGSN requests the corresponding CSG +4667 Subscription data. + +4668 MME Number for MT SMS + +4669 This parameter contains the ISDN number of the MME allocated for MT SMS (see 3GPP TS 23.003 [17]). It is present +4670 when the MME requests to be registered for SMS. + +4671 SMS-Only + +4672 This parameter indicates to the HSS that the UE needs only PS domain services and SMS services. + +4673 SMS Register Request + +4674 This parameter indicates to the HSS that if the MME (via IWF) needs to be registered for SMS, prefers not to be +4675 registered for SMS or has no preference to be registered for SMS, see 3GPP TS 23.272 [143]. + +4676 This parameter indicates to the HSS that if the SGSN needs to be registered for SMS, prefers not to be registered for +4677 SMS or has no preference to be registered for SMS, see 3GPP TS 23.060 [104]. + +4678 Removal of MME Registration for SMS + +4679 This parameter indicates by its presence that the MME requests to remove its registration for SMS. + +4680 MSISDN-less Operation Supported + +4681 This parameter indicates by its presence that the SGSN supports MSISDN-less operation (see clause 5.3.17 of 3GPP TS +4682 23.060 [23]). An SGSN which supports MSISDN-less operation shall set this parameter. + +4683 SGSN Name + +4684 See definition in clause 7.6.2. This parameter is provided in a request when the serving node is an SGSN and the SGSN +4685 supports Lgd interface for LCS and/or Gdd interface for SMS. + +4686 SGSN Realm + +4687 See definition in clause 7.6.2. This parameter is provided in a request when the serving node is an SGSN and the SGSN +4688 supports Lgd interface for LCS and/or Gdd interface for SMS. + +4689 Lgd Support Indicator + +4690 This parameter, by its presence, indicates to the HSS that the SGSN supports Lgd interface for LCS. When absent the +4691 SGSN supports only Lg interface for LCS, if LCS is supported. + +4692 Adjacent PLMNs + +4693 This parameter indicates the list of PLMNs where an UE served by the SGSN is likely to make a handover from the +4694 PLMN where the SGSN is located. This list is statically configured by the operator in the SGSN, according to the +4695 geographical disposition of the different PLMNs in that area, the roaming agreements, etc... + +4696 Reset-IDs Supported + +4697 This parameter indicates, if present, the support of Reset-IDs by the SGSN. + +4698 ADD Capability + +4699 This parameter indicates, if present, the support of ADD function by the HLR. + +4700 SGSN-MME Separation Support Indicator + +4701 This parameter indicates by its presence that the HSS separately stores SGSN Id and MME Id. A combined +4702 MME/SGSN shall not send Update-GPRS-Location at intra node inter RAT routing area update if a Separation +4703 Indicator was not received previously. + +4704 MME Registered for SMS + +4705 This parameter indicates by its presence that the HSS has registered the MME for SMS. + +4706 User error + +4707 In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in +4708 clause 7.6.1 may be used, depending on the nature of the fault: + +4709 - unknown subscriber; + +4710 - roaming not allowed. + +4711 This cause will be sent if the MS is not allowed to roam into the PLMN indicated by the SGSN number. The +4712 cause is qualified by the roaming restriction reason "PLMN Not Allowed", "Supported RAT Types Not +4713 Allowed" or "Operator Determined Barring". + +4714 This cause shall be used when the HLR rejects a MAP Update Gprs Location request received for an +4715 MSISDN-less subscription from a SGSN not supporting MSISDN-less operation. + +4716 - system failure; + +4717 - unexpected data value. + +4718 The diagnostic in the Unknown Subscriber may indicate "Imsi Unknown" or "Gprs or EPS Subscription Unknown". + +4719 Provider error + +4720 For definition of provider errors see clause 7.6.1. + +## 4721 8.1.8 MAP-NOTE-MM-EVENT + +### 4722 8.1.8.1 Definition + +4723 This service is used between the VLR and the gsmSCF or between the SGSN and the gsmSCF when a mobility +4724 management event for a subscriber has been processed successfully, that subscriber is provisioned with M-CSI or MG- +4725 CSI and the relevant mobility management event is marked for reporting. + +4726 This service is also used between the VLR and the Presence Network Agent or between the SGSN and the Presence +4727 Network Agent to notify the Presence Network Agent when a mobility management event for a subscriber has been +4728 processed successfully, that subscriber is provisioned with M-CSI or MG-CSI and the relevant mobility management +4729 event is marked for reporting (see 3GPP TS 23.141 [128]). + +### 4730 8.1.8.2 Service primitives + +4731 The service primitives are shown in table 8.1/8. + +4732 + +**Table 8.1/8: MAP\_NOTE\_MM\_EVENT parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|---------------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| Event Met | M | M(=) | | | +| Service Key | M | M(=) | | | +| IMSI | M | M(=) | | | +| Basic MSISDN | M | M(=) | | | +| Location Information for GPRS | C | C(=) | | | +| Location Information | C | C(=) | | | +| LSA Identity | C | C(=) | | | +| Supported CAMEL Phases | M | M(=) | | | +| Offered CAMEL 4 Functionalities | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +4733 + +### 4734 8.1.8.3 Parameter use + +4735 Event Met + +4736 This parameter indicates the mobility management event that has lead to the notification. It shall have one of the + 4737 following values for a mobility management event reported by the VLR: + +- 4738 - Location update in the same VLR service area; +- 4739 - Location update to another VLR service area; +- 4740 - IMSI attach; +- 4741 - MS initiated IMSI detach (explicit detach); +- 4742 - Network initiated IMSI detach (implicit detach). + +4743 It shall have one of the following values for a mobility management event reported by the SGSN: + +- 4744 - Routeing area update in the same SGSN service area; +- 4745 - Routeing area update to another SGSN service area; +- 4746 - GPRS attach; +- 4747 - MS initiated GPRS detach; +- 4748 - Network initiated GPRS detach; +- 4749 - Network initiated transfer to the "not reachable for paging" state. + +4750 Service Key + +4751 See clause 7.6.x. + +4752 IMSI + +4753 See clause 7.6.x. + +4754 Basic MSISDN + +4755 See clause 7.6.x. + +4756 Location Information + +4757 See clause 7.6.2.30. This information shall be sent when the event is reported by a VLR, if available. If the event is + 4758 reported as part of an SGs location update procedure, this information shall include the LAI and the Location + 4759 Information for EPS if available. + +4760 Location Information for GPRS + +4761 See clause 7.6.2.30a. This information shall be sent when the event is reported by an SGSN, if available. + +4762 LSA Identity + +4763 See clause 7.6.x. This information shall be sent, if available. + +4764 Supported CAMEL Phases + +4765 See clause 7.6.x. This information shall always be sent. + +4766 Offered CAMEL 4 Functionalities + +4767 This parameter indicates the CAMEL phase 4 functionalities offered by the sending entity, VMSC/VLR or SGSN (see +4768 clause 7.6.3.36G). + +4769 User error + +4770 This parameter is sent by the receiving entity when an error is detected. It shall have one of the following values: + +- 4771 - Data Missing; +- 4772 - Unexpected Data Value; +- 4773 - Unknown Subscriber; +- 4774 - MM-EventNotSupported. + +4775 Provider error + +4776 This is defined in clause 7.6.1. + +## 4777 8.1.9 MAP\_UPDATE\_VCSG\_LOCATION service + +### 4778 8.1.9.1 Definition + +4779 This procedure is used by the VLR or SGSN to register the MS in the CSS when + +- 4780 - the VPLMN supports Autonomous CSG Roaming +- 4781 - and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN +- 4782 - and the MS has requested an initial attach or a location area procedure or a routing area procedure to a CSG cell +- 4783 - and the VLR or SGSN has not yet registered the MS in the CSS. + +4784 The MAP\_UPDATE\_VCSG\_LOCATION service is a confirmed service using the service primitives given in table +4785 8.1/9. + +### 4786 8.1.9.2 Service primitives + +4787 **Table 8.1/9: MAP\_UPDATE\_VCSG\_LOCATION** + +| Parameter name | Request | Indication | Response | Confirm | +|-------------------------------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| VLR number | C | C(=) | | | +| SGSN number | C | C(=) | | | +| MSISDN | C | C(=) | | | +| Temporary Empty CSG Subscription data Indicator | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +4788 + +### 8.1.9.3 Parameter definitions and use + +#### Invoke Id + +See definition in clause 7.6.1. + +#### IMSI + +See definition in clause 7.6.2. + +#### VLR number + +See definition in clause 7.6.2. The presence of this parameter is mandatory when the service is used by the VLR. + +#### SGSN number + +See definition in clause 7.6.2. The presence of this parameter is mandatory when the service is used by the SGSN. + +#### MSISDN + +See definition in clause 7.6.2. Shall be present if this parameter is available. + +#### Temporary Empty CSG Subscription data Indicator + +See definition in clause 7.6.3.100. This parameter shall be present if the CSS accepts the request and there is no CSG Subscription data (empty CSG-ID list) for the roaming MS in the CSS. + +#### User error + +The following error causes defined in clause 7.6.1 may be used: + +- unknown subscriber; +- system failure; +- unexpected data value. + +#### Provider error + +For definition of provider errors see clause 7.6.1 + +### 8.1.10 MAP\_CANCEL\_VCSG\_LOCATION service + +#### 8.1.10.1 Definition + +This service is used between CSS and VLR to delete a roaming user record including the CSG subscription data and the CSS number from the VLR. The service is also used between CSS and SGSN to delete a roaming user record including the CSG subscription data and the CSS number from the SGSN. It may be invoked when there is removal of the CSG subscription data in CSS and of the MS registration including the case where a MS was registered in CSS but without CSG data. + +The MAP\_CANCEL\_VCSG\_LOCATION service is a confirmed service using the primitives defined in table 8.1/10. + +#### 8.1.10.2 Service primitives + +**Table 8.1/10: MAP\_CANCEL\_VCSG\_LOCATION** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +4820 + +4821 8.1.10.3 Parameter definitions and use + +4822 Invoke Id + +4823 See definition in clause 7.6.1. + +4824 IMSI + +4825 See definition in clause 7.6.2. + +4826 User error + +4827 If the cancellation fails, an error cause is to be returned by the VLR or by the SGSN. One of the following error causes +4828 defined in clause 7.6.1 shall be used: + +4829 - unexpected data value; + +4830 - data missing. + +4831 Provider error + +4832 For definition of provider errors see clause 7.6.1. + +4833 8.2 Paging and search + +4834 8.2.1 MAP\_PAGE service + +4835 8.2.1.1 Definition + +4836 This service is used between VLR and MSC to initiate paging of an MS for mobile terminated short message or +4837 unstructured SS notification. + +4838 The MAP\_PAGE service is a confirmed service using the primitives from table 8.2/1. + +4839 8.2.1.2 Service primitives + +4840 **Table 8.2/1: MAP\_PAGE** + +| Parameter name | Request | Indication | Response | Confirm | +|-------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| Stored location area Id | M | M(=) | | | +| TMSI | U | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +4841 + +4842 8.2.1.3 Parameter definitions and use + +4843 Invoke Id + +4844 See definition in clause 7.6.1. + +4845 IMSI + +4846 See definition in clause 7.6.2. The IMSI is used to define the paging subgroup. If the TMSI is not supplied, paging on +4847 the radio path uses the IMSI as an identifier. + +4848 Stored location area Id + +4849 See definition in clause 7.6.2. + +4850 TMSI + +4851 See definition in clause 7.6.2. The TMSI is included if paging on the radio channel is to use the TMSI as an identifier. + +4852 User error + +4853 The following error causes defined in clause 7.6.1 may be sent by the user in case of a paging error, depending on the +4854 failure reason: + +- 4855 - absent subscriber; +- 4856 - unknown location area; +- 4857 - busy subscriber; +- 4858 - system failure; +- 4859 - this corresponds to the case where there is no call associated with the MAP\_PAGE service, i.e. if the call has +4860 been released but the dialogue to the VLR has not been aborted; +- 4861 - unexpected data value. + +4862 Provider error + +4863 See definition in clause 7.6.1. + +## 4864 8.2.2 MAP\_SEARCH\_FOR\_MS service + +### 4865 8.2.2.1 Definition + +4866 This service is used between VLR and MSC to initiate paging of an MS in all location areas of that VLR. It is used if +4867 the VLR does not hold location area information confirmed by radio contact. + +4868 The MAP\_SEARCH\_FOR\_MS service is a confirmed service using the primitives from table 8.2/2. + +### 4869 8.2.2.2 Service primitives + +4870 **Table 8.2/2: MAP\_SEARCH\_FOR\_MS** + +| Parameter name | Request | Indication | Response | Confirm | +|--------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| Current location area Id | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +4871 + +### 4872 8.2.2.3 Parameter definitions and use + +4873 Invoke Id + +4874 See definition in clause 7.6.1. + +4875 IMSI + +4876 See definition in clause 7.6.2. The IMSI is used to identify the subscriber when paging on the radio path. + +4877 Current location area Id + +4878 See definition in clause 7.6.2. In case of successful outcome of the service, i.e. if the MS responds to paging, the +4879 Location Area Id of the area in which the MS responded is given in the response. + +4880 User error + +4881 The following error causes defined in clause 7.6.1 shall be sent by the user if the search procedure fails, depending on + 4882 the failure reason: + +- 4883 - absent subscriber; + 4884 this error cause is returned by the MSC if the MS does not respond to the paging request; +- 4885 - system failure; +- 4886 - this corresponds to the case where there is no call associated with the MAP\_SEARCH\_FOR\_MS service, i.e. if + 4887 the call has been released but the dialogue to the VLR has not been aborted; +- 4888 - busy subscriber; +- 4889 - unexpected data value. + +4890 Provider error + +4891 See definition in clause 7.6.1. + +## 4892 8.3 Access management services + +### 4893 8.3.1 MAP\_PROCESS\_ACCESS\_REQUEST service + +#### 4894 8.3.1.1 Definition + +4895 This service is used between MSC and VLR to initiate processing of an MS access to the network, e.g. for mobile + 4896 originated short message submission or after being paged by the network. + +4897 The MAP\_PROCESS\_ACCESS\_REQUEST service is a confirmed service using the primitives from table 8.3/1. + +#### 4898 8.3.1.2 Service primitives + +4899 **Table 8.3/1: MAP\_PROCESS\_ACCESS\_REQUEST** + +| Parameter name | Request | Indication | Response | Confirm | +|--------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| CM service type | M | M(=) | | | +| Access connection status | M | M(=) | | | +| Current Location Area Id | M | M(=) | | | +| Serving cell Id | M | M(=) | | | +| TMSI | C | C(=) | | | +| Cksn | C | C(=) | | | +| IMSI | C | C(=) | C | C(=) | +| IMEI | C | C(=) | C | C(=) | +| MSISDN | | | U | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +4900 + +#### 4901 8.3.1.3 Parameter definitions and use + +4902 Invoke Id + +4903 See definition in clause 7.6.1. + +4904 CM service type + +4905 See definition in clause 7.6.9. + +4906 Access connection status + +4907 See definition in clause 7.6.9. + +4908 Current Location Area Id + +4909 See definition in clause 7.6.2. This parameter is used to update the VLR in case of previous VLR failure. + +4910 Serving cell Id + +4911 See definition in clause 7.6.2. + +4912 TMSI + +4913 See definition in clause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, but +4914 one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace IMSI/TMSI. + +4915 Cksn + +4916 See definition in clause 7.6.7. In case of access with TMSI, the Cksn shall be present. + +4917 IMSI + +4918 See definition in clause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, but +4919 one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace IMSI/TMSI. + +4920 In the Response/Confirmation, the IMSI is to be sent in case of successful outcome of the service. In case of CM +4921 Service Type "Emergency Call Establishment", IMEI may replace IMSI. + +4922 IMEI + +4923 See definition in clause 7.6.2. The IMEI may replace IMSI/TMSI in the Request/Indication and IMSI in the +4924 Response/Confirmation only in case the CM Service Type indicates "Emergency Call Establishment". + +4925 MSISDN + +4926 See definition in clause 7.6.2. The MSISDN is included in case of successful outcome of the service as an operator +4927 option, e.g. if it is needed at the MSC for charging purposes in case of call forwarding. + +4928 User error + +4929 One of the following error causes defined in clause 7.6.1 shall be sent by the user if the access request fails, depending +4930 on the failure reason: + +4931 - unidentified subscriber; + +4932 - illegal subscriber; + +4933 this error is sent if a correlated authentication procedure has not authenticated the subscriber; + +4934 - illegal equipment; + +4935 this error is sent if an IMEI check failed, i.e. the IMEI is prohibited-listed or not permitted-listed; + +4936 - roaming not allowed; + +4937 - this cause is used after VLR restart if the subscriber has no subscription for the current location area, e.g. due to +4938 regional subscription. The cause will be qualified by "location area not allowed" or "national roaming not +4939 allowed", respectively; + +4940 - unknown location area; + +4941 - system failure; + +4942 - unexpected data value. + +4943 Provider error + +4944 For definition of provider errors see clause 7.6.1. + +## 4945 8.4 Handover services + +4946 It should be noted that the handover services used on the B-interface have not been updated for Release 99. The B- +4947 interface is not fully operational specified. It is strongly recommended not to implement the B-interface as an external +4948 interface. + +### 4949 8.4.1 MAP\_PREPARE\_HANDOVER service + +#### 4950 8.4.1.1 Definition + +4951 This service is used between MSC-A and MSC-B (E-interface) when a call is to be handed over or relocated from +4952 MSC-A to MSC-B. + +4953 The MAP\_PREPARE\_HANDOVER service is a confirmed service using the primitives from table 8.4/1. + +#### 4954 8.4.1.2 Service primitives + +4955 **Table 8.4/1: MAP\_PREPARE\_HANDOVER** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| Target Cell Id | C | C(=) | | | +| Target RNC Id | C | C(=) | | | +| HO-NumberNotRequired | C | C(=) | | | +| IMSI | C | C(=) | | | +| Integrity Protection Information | C | C(=) | | | +| Encryption Information | C | C(=) | | | +| Radio Resource Information | C | C(=) | | | +| AN-APDU | C | C(=) | C | C(=) | +| Allowed GSM Algorithms | C | C(=) | | | +| Allowed UMTS Algorithms | C | C(=) | | | +| Radio Resource List | C | C(=) | | | +| RAB ID | C | C(=) | | | +| GERAN Classmark | C | C(=) | | | +| BSSMAP Service Handover | C | C(=) | | | +| BSSMAP Service Handover List | C | C(=) | | | +| RANAP Service Handover | C | C(=) | | | +| Iu-Currently Used Codec | C | C(=) | | | +| Iu-Supported Codecs List | C | C(=) | | | +| RAB Configuration Indicator | C | C(=) | | | +| ASCI Call Reference | C | C(=) | | | +| UESBI-Iu | C | C(=) | | | +| IMEISV | C | C(=) | | | +| Alternative Channel Type | C | C(=) | | | +| Trace Propagation List | C | C(=) | | | +| AoIP-Supported Codecs List | C | C(=) | | | +| Anchor | | | | | +| Regional Subscription Data | U | (C=) | | | +| CSG Subscription Data | U | (C=) | | | +| LCLS Global Call Reference | C | C(=) | | | +| LCLS-Negotiation | C | C(=) | | | +| LCLS-Configuration-Preference | C | C(=) | | | +| Multiple Bearer Requested | C | C(=) | | | +| Handover Number | | | C | C(=) | +| Relocation Number List | | | C | C(=) | +| Multicall Bearer Information | | | C | C(=) | +| Multiple Bearer Not Supported | | | C | C(=) | +| Selected UMTS Algorithms | | | C | C(=) | + +| | | | | | +|-----------------------------------|--|--|---|------| +| Chosen Radio Resource Information | | | C | C(=) | +| Iu-Selected Codec | | | C | C(=) | +| Iu-Available Codecs List | | | C | C(=) | +| AoIP-Selected Codec Target | | | C | C(=) | +| AoIP-Available Codecs List Map | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +4956 + +### 4957 8.4.1.3 Parameter use + +#### 4958 Invoke Id + +4959 For definition of this parameter see clause 7.6.1. + +#### 4960 Target Cell Id + +4961 For definition of this parameter see clause 7.6.2. This parameter is only included if the service is not in an ongoing +4962 transaction. This parameter shall also be excluded if the service is a part of the Inter-MSC SRNS Relocation procedure +4963 or the inter-system handover GSM to UMTS procedure described in 3GPP TS 23.009. + +#### 4964 Target RNC Id + +4965 For definition of this parameter see clause 7.6.2. This parameter shall be included if the service is a part of the Inter- +4966 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS +4967 23.009. + +#### 4968 HO-Number Not Required + +4969 For definition of this parameter see clause 7.6.6. + +#### 4970 IMSI + +4971 For definition of this parameter see clause 7.6.2. This UMTS parameter shall be included if: + +- 4972 - available and +- 4973 - if the access network protocol is BSSAP and +- 4974 - there is an indication that the MS also supports UMTS. + +#### 4975 Integrity Protection Information + +4976 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the access +4977 network protocol is BSSAP. + +#### 4978 Encryption Information + +4979 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the access +4980 network protocol is BSSAP. + +#### 4981 Radio Resource Information + +4982 For definition of this parameter see clause 7.6.6. This GSM parameter shall be included if the access network protocol +4983 is RANAP and there is an indication that the UE also supports GSM. If the parameter Radio Resource List is sent , the +4984 parameter Radio Resource Information shall not be sent. + +#### 4985 AN-APDU + +4986 For definition of this parameter see clause 7.6.9. + +#### 4987 Allowed GSM Algorithms + +4988 For definition of this parameter see clause 7.6.6. This parameter includes allowed GSM algorithms. This GSM +4989 parameter shall be included if: + +- 4990 - the service is a part of the Inter-MSC SRNS Relocation procedure and +- 4991 - Ciphering or Security Mode Setting procedure has been performed. and +- 4992 - there is an indication that the UE also supports GSM. + +#### 4993 Allowed UMTS Algorithms + +4994 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if all of the following +4995 conditions apply: + +- 4996 - access network protocol is BSSAP and +- 4997 - Integrity Protection Information and Encryption Information are not available and +- 4998 - Ciphering or Security Mode Setting procedure has been performed. + +#### 4999 Radio Resource List + +5000 For definition of this parameter see clause 7.6.6. This parameter shall be included if the access network protocol is +5001 RANAP and there is an indication that the UE also supports GSM. This parameter shall be sent when MSC-A requests +5002 multiple bearers to MSC-B. If the parameter Radio Resource Information is sent, the parameter Radio Resource List +5003 shall not be sent. + +#### 5004 RAB ID + +5005 For definition of this parameter see clause 7.6.2. This parameter shall be included when MSC-A supports multiple +5006 bearers and access network protocol is BSSAP and the RAB ID has a value other than 1. + +#### 5007 GERAN Classmark + +5008 For definition of this parameter see clause 7.6.6 This parameter shall be included if available. + +#### 5009 BSSMAP Service Handover + +5010 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is +5011 RANAP. If the parameter BSSMAP Service Handover List is sent, the parameter BSSMAP Service Handover shall not +5012 be sent. + +#### 5013 BSSMAP Service Handover List + +5014 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is +5015 RANAP. This parameter shall be sent when MSC-A requests multiple bearers to MSC-B. If the parameter BSSMAP +5016 Service Handover is sent, the parameter BSSMAP Service Handover List shall not be sent. + +#### 5017 RANAP Service Handover + +5018 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is +5019 BSSAP. + +#### 5020 Iu-Currently Used Codec + +5021 For definition of this parameter see clause 7.6.6. This parameter shall be included if the handover is requested for a +5022 speech bearer and the MS is in UMTS or GERAN Iu-mode access. This parameter shall not be included if the Iu- +5023 Supported Codecs List is not included. + +#### 5024 Iu-Supported Codecs List + +5025 For definition of this parameter see clause 7.6.6. This parameter shall be included by MSC-A, if the handover is +5026 requested for a speech bearer. + +#### 5027 RAB Configuration Indicator + +5028 For definition of this parameter see clause 7.6.6. This parameter may be included if the handover is requested for a +5029 speech bearer and MSC-A knows by means of configuration information that MSC-B supports the use of the Iu- +5030 Supported Codecs List parameter. This parameter shall not be included if the Iu-Supported Codecs List is not included. + +5031 ASCI Call Reference + +5032 This parameter contains either the broadcast call reference or group call reference. It shall be included if a subscriber is +5033 undergoing handover during a VGCS or VBS call, where MSC-B already has a Bearer established, so that MSC-B can +5034 determine the Group or Broadcast Call to which it shall attach the subscriber, see 3GPP TS 48.008 [49]. +5035 + +5036 UESBI-Iu + +5037 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is +5038 BSSAP. + +5039 IMEISV + +5040 For definition of the parameter see clause 7.6.2. This parameter shall be present, if available. This is used e.g. for +5041 Management based Trace Activation (see 3GPP TS 32.422). + +5042 Alternative Channel Type + +5043 For definition of this parameter see clause 7.6.6 It shall be present for a SCUDIF call if the access network protocol is +5044 BSSAP. + +5045 Trace Propagation List + +5046 See definition in clause 7.6.10. This parameter shall be included when MSC-A requests trace invocation. + +5047 AoIP-Supported Codecs List Anchor + +5048 For definition of this parameter see clause 7.6.6. This parameter may be included by MSC-A, if the handover is +5049 requested for a speech bearer and mobile terminal supports GSM codec types. + +5050 Regional Subscription Data + +5051 The list of subscribed Zone Codes as received from the HLR may be included by MSC-A at intra PLMN inter MSC +5052 handover and may be stored at MSC-B for use at subsequent intra MSC handover. + +5053 CSG Subscription Data + +5054 The subscribed CSG Subscription Information as received from the HLR may be included by MSC-A at intra PLMN +5055 inter MSC handover and at inter PLMN inter MSC handover when the target PLMN is an ePLMN, and may be stored at +5056 MSC-B for use at subsequent intra MSC handover. + +5057 LCLS Global Call Reference + +5058 For definition of this parameter see clause 7.6.5.21. This parameter shall be included when MSC-A supports LCLS. + +5059 LCLS-Negotiation + +5060 For definition of this parameter see clause 7.6.5.22. This parameter shall be included when MSC-A supports LCLS. + +5061 LCLS-Configurations-Preference + +5062 For definition of this parameter see clause 7.6.5.23. This parameter shall be included when MSC-A supports LCLS. + +5063 Multiple Bearer Requested + +5064 For a definition of this parameter see clause 7.6.2. This parameter shall be sent when MSC-A requests multiple bearers +5065 to MSC-B. + +5066 Handover Number + +5067 For definition of this parameter see clause 7.6.2. This parameter shall be returned at handover, unless the parameter +5068 HO-NumberNotRequired is sent. If the parameter Handover Number is returned, the parameter Relocation Number List +5069 shall not be returned. + +5070 Relocation Number List + +5071 For definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation, unless the parameter +5072 HO-NumberNotRequired is sent. If the parameter Relocation Number List is returned, the parameter Handover Number +5073 shall not be returned. + +5074 Multicall Bearer Information + +5075 For a definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation in the case that MSC-B +5076 supports multiple bearers. + +5077 Multiple Bearer Not Supported + +5078 For a definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation when MSC-B receives +5079 Multiple Bearer Requested parameter and MSC-B does not support multiple bearers. + +5080 Selected UMTS Algorithms + +5081 For definition of this parameter see clause 7.6.6. This parameter includes the UMTS integrity and optionally +5082 encryption algorithms selected by RNC under the control of MSC-B. This UMTS parameter shall be included if the +5083 service is a part of the inter MSC inter system handover from GSM to UMTS. + +5084 Chosen Radio Resource Information + +5085 For definition of this parameter see clause 7.6.6. This parameter shall be returned at relocation if the encapsulated PDU +5086 is RANAP RAB Assignment Response and MS is in GSM access. + +5087 Iu-Selected Codec + +5088 For definition of this parameter see clause 7.6.6. This parameter shall be included if an Iu-Supported Codecs List was +5089 received in the service request and MSC-B supports the selection of codec based on the Iu-Supported Codecs List and +5090 the target radio access network is connected to MSC-B via the Iu interface, even if the Iu-Selected Codec is equal to the +5091 Iu-Currently Used Codec received in the service request. This parameter shall not be included if the Iu-Supported +5092 Codecs List was not received in the service request. + +5093 Iu-Available Codecs List + +5094 For definition of this parameter see clause 7.6.6. This parameter shall be included by an MSC-B supporting TrFO, if the +5095 Iu-Supported Codecs List was included by MSC-A and the target radio access is UMTS or GERAN Iu-mode. + +5096 AoIP-Selected Codec Target + +5097 For definition of this parameter see clause 7.6.6. This parameter may be included by an MSC-B supporting TrFO, if the +5098 AoIP-Supported Codecs List Anchor was included by MSC-A and if AoIP is used on the target A interface with +5099 transcoder inserted in the MGW. + +5100 AoIP-Available Codecs List Map + +5101 For definition of this parameter see clause 7.6.6. This parameter may be included by an MSC-B supporting TrFO, if the +5102 AoIP-Supported Codecs List Anchor was included by MSC-A and if AoIP is used on the target A interface with +5103 transcoder inserted in the MGW. + +5104 User error + +5105 For definition of this parameter see clause 7.6.1. The following errors defined in clause 7.6.1 may be used, depending +5106 on the nature of the fault: + +- 5107 - No handover number available. +- 5108 - Target cell outside group call area; +- 5109 - System failure. + +5110 - Unexpected data value. + +5111 - Data Missing. + +5112 Provider error + +5113 See definition of provider errors in clause 7.6.1. + +## 5114 8.4.2 MAP\_SEND\_END\_SIGNAL service + +### 5115 8.4.2.1 Definition + +5116 This service is used between MSC-B and MSC-A (E-interface) indicating that the radio path has been established by +5117 MSC-B to the MS. MSC-A retains then the main control of the call until it clears. + +5118 The response is used by MSC-A to inform MSC-B that all resources for the call can be released in MSC-B, either +5119 because the call has been released in MSC-A or because the call has been successfully handed over or relocated from +5120 MSC-B to another MSC. + +5121 The MAP\_SEND\_END\_SIGNAL service is a confirmed service using the primitives from table 8.4/2. + +### 5122 8.4.2.2 Service primitives + +5123 **Table 8.4/2: MAP\_SEND\_END\_SIGNAL** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| AN-APDU | M | M(=) | | | +| Provider error | | | | O | + +5124 + +### 5125 8.4.2.3 Parameter use + +5126 Invoke Id + +5127 For definition of this parameter see clause 7.6.1. + +5128 AN-APDU + +5129 For definition of this parameter see clause 7.6.9. + +5130 Provider error + +5131 For definition of this parameter see clause 7.6.1. + +## 5132 8.4.3 MAP\_PROCESS\_ACCESS\_SIGNALLING service + +### 5133 8.4.3.1 Definition + +5134 This service is used between MSC-B and MSC-A (E-interface) to pass information received on the A-interface or Iu- +5135 interface in MSC-B to MSC-A. + +5136 The MAP\_PROCESS\_ACCESS\_SIGNALLING service is a non-confirmed service using the primitives from +5137 table 8.4/3. + +### 5138 8.4.3.2 Service primitives + +5139 **Table 8.4/3: MAP\_PROCESS\_ACCESS\_SIGNALLING** + +| Parameter name | Request | Indication | +|----------------|---------|------------| +| Invoke Id | M | M(=) | + +| | | | +|-----------------------------------|---|------| +| AN-APDU | M | M(=) | +| Selected GSM Algorithm | C | C(=) | +| Selected UMTS Algorithms | C | C(=) | +| Chosen Radio Resource Information | C | C(=) | +| Selected RAB id | C | C(=) | +| Iu-Selected Codec | C | C(=) | +| Iu-Available Codecs List | C | C(=) | +| AoIP-Selected Codec Target | C | C(=) | +| AoIP-Available Codecs List Map | C | C(=) | + +5140 + +### 5141 8.4.3.3 Parameter use + +#### 5142 Invoke Id + +5143 For definition of this parameter see clause 7.6.1. + +#### 5144 AN-APDU + +5145 For definition of this parameter see clause 7.6.9. + +#### 5146 Selected GSM algorithm + +5147 For definition of this parameter see clause 7.6.6. This parameter shall be present if the encapsulated PDU is Security +5148 Mode Complete and MS is in GSM access. + +#### 5149 Selected UMTS Algorithms + +5150 For definition of this parameter see clause 7.6.6. This parameter includes the UMTS integrity and optionally +5151 encryption algorithms selected by RNC under the control of MSC-B. This UMTS parameter shall be included if the +5152 encapsulated PDU is BSSMAP Cipher Mode Complete and the MS is in UMTS, or an intersystem handover to UMTS is +5153 performed in MSC-B, or in the case of intra MSC-B intra UMTS relocation. + +#### 5154 Chosen Radio Resource Information + +5155 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB +5156 Assignment Response and MS is in GSM access. + +#### 5157 Selected RAB ID + +5158 The selected radio access bearer that was kept at subsequent intra-MSC handover from UMTS to GSM after multiple +5159 bearers were used. + +#### 5160 Iu-Selected Codec + +5161 For definition of this parameter see clause 7.6.6. This parameter shall be included + +5162 - if MSC-B changes the selected codec and the MS is in UMTS or GERAN Iu-mode access; + +5163 - if intersystem handover to UMTS or GERAN Iu-mode is performed in MSC-B; or + +5164 - if MSC-B received a Forward Access Signalling service request including an Iu-Supported Codecs List and the +5165 MS is in UMTS or GERAN Iu-mode access. + +5166 This parameter shall not be included if the Iu-Supported Codecs List was not received either in the Prepare Handover +5167 service request or in the Forward Access Signalling service request. + +#### 5168 Iu-Available Codecs List + +5169 For definition of this parameter see clause 7.6.6. This parameter shall be included by an MSC-B supporting TrFO + +5170 - if the Iu-Available Codecs List has changed in MSC-B; + +5171 - if intersystem handover to UMTS or GERAN Iu-mode is performed in MSC-B; or + +5172 - if MSC-B received a Forward Access Signalling service request including an Iu-Supported Codecs List and the +5173 MS is in UMTS or GERAN Iu-mode access. + +5174 AoIP-Selected Codec Target + +5175 For definition of this parameter see clause 7.6.6. This parameter may be included + +5176 - if A interface codec is changed in MSC-B; or + +5177 - if intersystem handover to AoIP capable BSC is performed in MSC-B and if AoIP is used on the target A +5178 interface with transcoder inserted in the MGW; or + +5179 - if MSC-B received a Forward Access Signalling service request including an AoIP-Supported Codecs List and +5180 the MS is in AoIP capable GSM access where AoIP is used on the target A interface with transcoder inserted in +5181 the MGW. + +5182 This parameter shall not be included if the AoIP-Supported Codecs List Anchor was not received either in the Prepare +5183 Handover service request or in the Forward Access Signalling service request. + +5184 AoIP-Available Codecs List Map + +5185 For definition of this parameter see clause 7.6.6. This parameter may be included by an MSC-B supporting TrFO + +5186 - if the AoIP-Available Codecs List has changed in MSC-B; or + +5187 - if intersystem handover to AoIP capable BSC is performed in MSC-B where AoIP is used on the target A +5188 interface with transcoder inserted in the MGW; or + +5189 - if MSC-B received a Forward Access Signalling service request including an AoIP-Supported Codecs List +5190 Anchor and the MS is in AoIP capable GSM access where AoIP is used on the target A interface with transcoder +5191 inserted in the MGW. + +## 5192 8.4.4 MAP\_FORWARD\_ACCESS\_SIGNALLING service + +### 5193 8.4.4.1 Definition + +5194 This service is used between MSC-A and MSC-B (E-interface) to pass information to be forwarded to the A-interface +5195 or Iu-interface of MSC-B. + +5196 The MAP\_FORWARD\_ACCESS\_SIGNALLING service is a non-confirmed service using the primitives from +5197 table 8.4/4. + +### 5198 8.4.4.2 Service primitives + +5199 **Table 8.4/4: MAP\_FORWARD\_ACCESS\_SIGNALLING** + +| Parameter name | Request | Indication | +|----------------------------------|---------|------------| +| Invoke Id | M | M(=) | +| Integrity Protection Information | C | C(=) | +| Encryption Information | C | C(=) | +| Key Status | C | C(=) | +| AN-APDU | M | M(=) | +| Allowed GSM Algorithms | C | C(=) | +| Allowed UMTS Algorithms | C | C(=) | +| Radio Resource Information | C | C(=) | +| Radio Resource List | C | C(=) | +| BSSMAP Service Handover | C | C(=) | +| BSSMAP Service Handover List | C | C(=) | +| RANAP Service Handover | C | C(=) | +| Iu-Currently Used Codec | C | C(=) | +| Iu-Supported Codecs List | C | C(=) | +| RAB Configuration Indicator | C | C(=) | +| Iu-Selected Codec | C | C(=) | + +| | | | +|----------------------------|---|------| +| Alternative Channel Type | C | C(=) | +| Trace Propagation List | C | C(=) | +| AoIP-Supported Codecs List | C | C(=) | +| Anchor | | | +| AoIP-Selected Codec Target | C | C(=) | +| UESBI-lu | C | C(=) | +| IMEISV | C | C(=) | + +5200 + +#### 5201 8.4.4.3 Parameter use + +5202 For the definition and use of all parameters and errors, see clause 7.6.1. + +##### 5203 Invoke Id + +5204 For definition of this parameter see clause 7.6.1. + +##### 5205 Integrity Protection Information + +5206 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the +5207 encapsulated PDU is BSSMAP Cipher Mode Command. + +##### 5208 Encryption Information + +5209 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the +5210 encapsulated PDU is BSSMAP Cipher Mode Command. + +##### 5211 Key Status + +5212 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the +5213 encapsulated PDU is BSSMAP Cipher Mode Command. + +##### 5214 AN-APDU + +5215 For definition of this parameter see clause 7.6.9. + +##### 5216 Allowed GSM Algorithms + +5217 This parameter includes allowed GSM algorithms. This GSM parameter shall be included if the encapsulated PDU is +5218 RANAP Security Mode Command and there is an indication that the UE also supports GSM. + +##### 5219 Allowed UMTS Algorithms + +5220 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if Integrity Protection +5221 Information and Encryption Information are not available and the encapsulated PDU is BSSMAP Cipher Mode +5222 Command. + +##### 5223 Radio Resource Information + +5224 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB +5225 Assignment Request. If the parameter Radio Resource List is sent, the parameter Radio Resource Information shall not +5226 be sent. + +##### 5227 Radio Resource List + +5228 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB +5229 Assignment Request and MSC-A requests modification of multiple bearers. If the parameter Radio Resource +5230 Information is sent, the parameter Radio Resource List shall not be sent. + +##### 5231 BSSMAP Service Handover + +5232 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is +5233 RANAP RAB Assignment Request. If the parameter BSSMAP Service Handover List is sent, the parameter BSSMAP +5234 Service Handover shall not be sent. + +##### 5235 BSSMAP Service Handover List + +5236 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is +5237 RANAP RAB Assignment Request and MSC-A requests modification of multiple bearers. If the parameter BSSMAP +5238 Service Handover is sent, the parameter BSSMAP Service Handover List shall not be sent. + +5239 RANAP Service Handover + +5240 For definition of this parameter see clause 7.6.6.. It shall be present if it is available and the encapsulated PDU is +5241 BSSMAP Assignment Request. + +5242 Iu-Currently Used Codec + +5243 For definition of this parameter see clause 7.6.6. This parameter shall be included if the encapsulated PDU is a RANAP +5244 RAB Assignment Request or BSSMAP Assignment Request for a speech bearer and the MS is in UMTS or GERAN +5245 Iu-mode access. This parameter shall not be included if the Iu-Supported Codecs List is not included. + +5246 Iu-Supported Codecs List + +5247 For definition of this parameter see clause 7.6.6. This parameter shall be included if the encapsulated PDU is a RANAP +5248 RAB Assignment Request or BSSMAP Assignment Request and + +- 5249 - a new bearer is allocated for speech; +- 5250 - an existing bearer is modified from data to speech; or +- 5251 - for an existing speech bearer the order of priority in the Iu-Supported Codecs List needs to be modified. + +5252 This parameter shall not be included if the Iu-Selected Codec is included. + +5253 RAB Configuration Indicator + +5254 For definition of this parameter see clause 7.6.6. This parameter may be included if the encapsulated PDU is a RANAP +5255 RAB Assignment Request for a speech bearer, and MSC-A knows by means of configuration information that MSC-B +5256 supports the use of the Iu-Supported Codecs List parameter. This parameter shall not be included if the Iu-Supported +5257 Codecs List is not included. + +5258 Iu-Selected Codec + +5259 For definition of this parameter see clause 7.6.6. This parameter shall be included if + +- 5260 - the encapsulated PDU is a RANAP RAB Assignment Request or BSSMAP Assignment Request for an existing +5261 speech bearer; and +- 5262 - the MS is in UMTS or GERAN Iu-mode access; and +- 5263 - an Iu-Available Codecs List was received by MSC-A for this speech bearer before, either in the Prepare +5264 Handover service response or in the Process Access Signalling service request. + +5265 This parameter shall not be included if the Iu-Supported Codecs List is included. + +5266 Alternative Channel Type + +5267 For definition of this parameter see clause 7.6.6. This parameter shall be present for a SCUDIF call if the encapsulated +5268 PDU is BSSMAP Assignment Request. + +5269 Trace Propagation List + +5270 See definition in clause 7.6.10. This parameter shall be included when MSC-A requests trace invocation. + +5271 AoIP-Supported Codecs List Anchor + +5272 For definition of this parameter see clause 7.6.6. This parameter may be included if the encapsulated PDU is a +5273 BSSMAP Assignment Request and + +- 5274 - a new bearer is allocated for speech; +- 5275 - an existing bearer is modified from data to speech; or + +5276 - for an existing speech bearer the order of priority in the AoIP-Supported Codecs List needs to be modified. + +5277 This parameter shall not be included if the AoIP-Selected Codec Target is included. + +5278 AoIP-Selected Codec Target + +5279 For definition of this parameter see clause 7.6.6. This parameter may be included if + +5280 - the encapsulated PDU is a BSSMAP Assignment Request for an existing speech bearer; and + +5281 - the MS is in AoIP capable GSM access where AoIP is used on the target A interface with transcoder inserted in +5282 the MGW; and + +5283 - an AoIP-Available Codecs List was received by MSC-A for this speech bearer before, either in the Prepare +5284 Handover service response or in the Process Access Signalling service request. + +5285 This parameter shall not be included if the AoIP-Supported Codecs List Anchor is included. + +5286 UESBI-Iu + +5287 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is +5288 BSSAP and the parameter has not already been sent to the target MSC. + +5289 IMEISV + +5290 For definition of the parameter see clause 7.6.2. This parameter shall be present if available and if not already sent to +5291 the target MSC. This is used e.g. for Management based Trace Activation (see 3GPP TS 32.422). + +## 5292 8.4.5 MAP\_PREPARE\_SUBSEQUENT\_HANDOVER service + +### 5293 8.4.5.1 Definition + +5294 This service is used between MSC-B and MSC-A (E-interface) to inform MSC-A that it has been decided that a +5295 handover or relocation to either MSC-A or a third MSC (MSC-B') is required. + +5296 The MAP\_PREPARE\_SUBSEQUENT\_HANDOVER service is a confirmed service using the primitives from +5297 table 8.4/5. + +### 5298 8.4.5.2 Service primitives + +5299 **Table 8.4/5: MAP\_PREPARE\_SUBSEQUENT\_HANDOVER** + +| Parameter name | Request | Indication | Response | Confirm | +|-----------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| Target Cell Id | C | C(=) | | | +| Target RNC Id | C | C(=) | | | +| Target MSC Number | M | M(=) | | | +| Selected RAB ID | C | C(=) | | | +| GERAN Classmark | C | C(=) | | | +| RAB Configuration Indicator | C | C(=) | | | +| AN-APDU | M | M(=) | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +5300 + +### 5301 8.4.5.3 Parameter use + +5302 Invoke Id + +5303 For definition of this parameter see clause 7.6.1. + +5304 Target Cell Id + +5305 For definition of this parameter see clause 7.6.2. This parameter shall be excluded if the service is a part of the Inter- + 5306 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS + 5307 23.009. + +5308 Target RNC Id + +5309 For definition of this parameter see clause 7.6.2. This parameter shall be included if the service is a part of the Inter- + 5310 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS + 5311 23.009. + +5312 Target MSC Number + +5313 For definition of this parameter see clause 7.6.2. + +5314 Selected RAB ID + +5315 For definition of this parameter see clause 7.6.2. + +5316 GERAN Classmark + +5317 For definition of this parameter see clause 7.6.6 This parameter shall be included if available. + +5318 RAB Configuration Indicator + +5319 For definition of this parameter see clause 7.6.6. This parameter may be included if the call is a speech call and MSC-B + 5320 knows by means of configuration information that MSC-B' (and MSC-A) supports the use of the Iu-Supported Codecs + 5321 List parameter. + +5322 AN-APDU + +5323 For definition of this parameter see clause 7.6.9. + +5324 User error + +5325 For definition of this parameter see clause 7.6.1. The following error causes defined in clause 7.6.1 may be used, + 5326 depending on the nature of the fault: + +- 5327 - Unknown MSC; +- 5328 - Subsequent handover failure; +- 5329 - Unexpected data value; +- 5330 - Data Missing. + +5331 Provider error + +5332 For definition of this parameter see clause 7.6.1. + +## 5333 8.4.6 MAP\_ALLOCATE\_HANDOVER\_NUMBER service + +### 5334 8.4.6.1 Definition + +5335 This service is used between MSC and VLR (B-interface) to request a handover number. + +5336 The MAP\_ALLOCATE\_HANDOVER\_NUMBER service is a confirmed service using the primitives from table 8.4/6. + +### 5337 8.4.6.2 Service primitives + +5338 **Table 8.4/6: MAP\_ALLOCATE\_HANDOVER\_NUMBER** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +5339 + +### 5340 8.4.6.3 Parameter use + +#### 5341 Invoke Id + +5342 For definition of this parameter see clause 7.6.1. + +#### 5343 User error + +5344 For definition of this parameter see clause 7.6.1. The following errors defined in clause 7.6.1 may be used, depending +5345 on the nature of the fault: + +5346 - No handover number available. + +#### 5347 Provider error + +5348 For definition of this parameter see clause 7.6.1. + +## 5349 8.4.7 MAP\_SEND\_HANDOVER\_REPORT service + +### 5350 8.4.7.1 Definition + +5351 This service is used between VLR and MSC-B (B-interface) to transfer the handover number to be forwarded to and +5352 used by MSC-A. + +5353 The MAP\_SEND\_HANDOVER\_REPORT service is a confirmed service using the primitives from table 8.4/7. + +### 5354 8.4.7.2 Service primitives + +5355 **Table 8.4/7: MAP\_SEND\_HANDOVER\_REPORT** + +| Parameter name | Request | Indication | Response | Confirm | +|-----------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| Handover Number | M | M(=) | | | +| Linked Id | M | M(=) | | | +| Provider error | | | | O | + +5356 + +### 5357 8.4.7.3 Parameter use + +#### 5358 Invoke Id + +5359 For definition of this parameter see clause 7.6.1. + +#### 5360 Handover Number + +5361 For definition of this parameter see clause 7.6.2. + +#### 5362 Linked Id + +5363 For definition of this parameter see clause 7.6.1. This service is linked with +5364 MAP\_ALLOCATE\_HANDOVER\_NUMBER. + +#### 5365 Provider error + +5366 For definition of this parameter see clause 7.6.1. + +## 5367 8.5 Authentication management services + +### 5368 8.5.1 MAP\_AUTHENTICATE service + +5369 The MAP\_AUTHENTICATE service is used on the MAP B interface. This interface is not fully operational specified. +5370 It is strongly recommended not to implement the B-interface as an external interface. + +### 5371 8.5.1.1 Definition + +5372 This service is used between the VLR and the MSC when the VLR receives a MAP service indication from the MSC +5373 concerning a location registration, call set-up, operation on a supplementary service or a request from the MSC to +5374 initiate authentication. + +5375 The service is a confirmed service and consists of four service primitives. + +### 5376 8.5.1.2 Service primitives + +5377 The service primitives are shown in table 8.5/1. + +5378 **Table 8.5/1: MAP\_AUTHENTICATE parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| RAND | M | M(=) | | | +| CKSN | M | M(=) | | | +| SRES | | | M | M(=) | +| Provider error | | | | O | + +5379 + +### 5380 8.5.1.3 Parameter use + +#### 5381 Invoke id + +5382 See clause 7.6.1 for the use of this parameter. + +#### 5383 RAND + +5384 See clause 7.6.7 for the use of this parameter. + +#### 5385 CKSN + +5386 See clause 7.6.7 for the use of this parameter. + +#### 5387 SRES + +5388 See clause 7.6.7 for the use of this parameter. + +#### 5389 Provider error + +5390 See clause 7.6.1 for the use of this parameter. + +## 5391 8.5.2 MAP\_SEND\_AUTHENTICATION\_INFO service + +### 5392 8.5.2.1 Definition + +5393 This service is used between the VLR and the HLR for the VLR to retrieve authentication information from the HLR. +5394 The VLR requests up to five authentication vectors. + +5395 Also this service is used between the SGSN and the HLR for the SGSN to retrieve authentication information and/or +5396 UE Usage Type from the HLR. The SGSN requests up to five authentication vectors. + +5397 Also this service is used between the BSF and the HLR for the BSF to retrieve authentication information from the +5398 HLR. The BSF shall only request one authentication vector at a time. + +5399 In an EPS, this service is used between IWF and IWF and between IWF and HSS. + +- 5400 If the requesting node type is different from "MME" and the user is a UMTS subscriber, the HLR shall return +5401 authentication quintuplets. If the requesting node type is different from MME and the user is a GSM subscriber, the +5402 HLR shall return authentication triplets. +- 5403 If the requesting node type is "MME", the HSS shall return EPS authentication vectors. +- 5404 If the requesting node type is a combined MME/SGSN, the HSS shall return requested authentication vectors for the +5405 actual RAT and may return additional authentication vectors for the other RAT. +- 5406 If the HLR cannot provide the VLR, the SGSN or the BSF with triplets, an empty response is returned. The VLR, the +5407 SGSN, or the BSF may then re-use old authentication triplets, except where this is forbidden under the conditions +5408 specified in 3GPP TS 43.020 [24]. +- 5409 If the HLR cannot provide the VLR, the SGSN or the BSF with quintuplets, an empty response is returned. The VLR, +5410 the SGSN or the BSF shall not re-use old authentication quintuplets. +- 5411 If the HSS cannot provide the IWF with EPS authentication vectors, an empty response is returned. +- 5412 If the VLR or SGSN or IWF or BSF receives a MAP\_SEND\_AUTHENTICATION\_INFO response containing a User +5413 Error parameter as part of the handling of an authentication procedure, the authentication procedure in the VLR or +5414 SGSN or MME or BSF shall fail. +- 5415 Security related network functions are further described in 3GPP TS 43.020 [24] and 3GPP TS 33.200. +- 5416 The service is a confirmed service and consists of four service primitives. + +### 5417 8.5.2.2 Service primitives + +5418 The service primitives are shown in table 8.5/2. + +5419 **Table 8.5/2: MAP\_SEND\_AUTHENTICATION\_INFO parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|------------------------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMSI | C | C(=) | | | +| Number of requested vectors | C | C(=) | | | +| Requesting node type | C | C(=) | | | +| Re-synchronisation Info | C | C(=) | | | +| Segmentation prohibited indicator | C | C(=) | | | +| Immediate response preferred indicator | U | C(=) | | | +| Requesting PLMN ID | C | C(=) | | | +| Number of additional requested vectors | C | C(=) | | | +| Additional requested Vectors are for EPS | C | C(=) | | | +| UE Usage Type Request Indication | C | C(=) | | | +| AuthenticationSetList | | | C | C(=) | +| UE Usage Type | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +5420 + +### 5421 8.5.2.3 Parameter use + +5422 Invoke id + +5423 See clause 7.6.1 for the use of this parameter. + +5424 IMSI + +5425 See clause 7.6.2 for the use of this parameter. + +5426 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a +5427 dialogue then this parameter shall not be present in any service request other than the first one. + +5428 Number of requested vectors + +5429 A number indicating how many authentication vectors the VLR, the SGSN, the MME or the BSF is prepared to receive. +5430 The HLR shall not return more vectors than indicated by this parameter. + +5431 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a +5432 dialogue then this parameter shall not be present in any service request other than the first one. + +5433 Requesting node type + +5434 The type of the requesting node (SGSN, MME, combined MME/SGSN, VLR, or BSF). + +5435 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a +5436 dialogue then this parameter shall not be present in any service request other than the first one. + +5437 Re-synchronisation Info + +5438 For definition and use of this parameter see 3GPP TS 33.200. + +5439 If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other +5440 than the first one.. + +5441 Segmentation prohibited indicator + +5442 This parameter indicates if the VLR, the SGSN or the IWF allows segmentation of the response at MAP user level. + +5443 This parameter may be present only in the first request of the dialogue. + +5444 Immediate response preferred indicator + +5445 This parameter indicates that one of the requested authentication vectors is requested for immediate use in the VLR, the +5446 SGSN, the MME or the BSF. It may be used by the HLR together with the number of requested vectors and the number +5447 of vectors stored in the HLR to determine the number of vectors to be obtained from the AuC. It shall be ignored if the +5448 number of available vectors is greater than the number of requested vectors. + +5449 If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other +5450 than the first one. + +5451 Requesting PLMN ID + +5452 The PLMN-ID of the requesting node. See 3GPP TS 23.003. + +5453 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a +5454 dialogue then this parameter shall not be present in any service request other than the first one. + +5455 Number of additional requested vectors + +5456 A number indicating how many additional authentication vectors the combined MME/SGSN or IWF is prepared to +5457 receive. The HLR shall not return more vectors than indicated by this parameter. This parameter shall be present only if +5458 the requesting node type is a combined MME/SGSN. A combined MME/SGSN that wants to request only EPS-Vectors +5459 (only non-EPS-Vectors) shall set the requesting node type to "MME" ("SGSN"). + +5460 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a +5461 dialogue then this parameter shall not be present in any service request other than the first one. + +5462 Additional vectors are for EPS + +5463 This parameter shall be absent if Number of additional vectors is absent. The parameter indicates by its presence that +5464 additional vectors (i.e. not for immediate use) are for EPS. + +5465 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a +5466 dialogue then this parameter shall not be present in any service request other than the first one. + +5467 UE Usage Type Request Indication + +5468 This parameter indicates by its presence that the HLR (if it supports the Dedicated Core Network functionality) shall +5469 include the UE Usage Type in the response to the SGSN. This parameter is not applicable for VLRs. + +5470 AuthenticationSetList + +5471 A set of one to five authentication vectors are transferred from the HLR to the VLR, from the HLR to the SGSN or IWF + 5472 or from the HLR to the BSF, if the outcome of the service was successful. + +5473 UE Usage Type + +5474 This parameter shall be present if UE Usage Type Request Indication was present in the request and the HLR supports + 5475 the Dedicated Core Networks functionality (see 3GPP TS 23.060 [104]) and a UE Usage Type is available in the + 5476 subscription data of the user. In this case, if the Immediate Response Preferred parameter is not set, the HLR may return + 5477 no authentication vectors in the response. + +5478 User error + +5479 One of the following error causes defined in clause 7.6.1 shall be sent by the user in case of unsuccessful outcome of + 5480 the service, depending on the respective failure reason: + +- 5481 - unknown subscriber; +- 5482 - unexpected data value; +- 5483 - system failure; +- 5484 - data missing. + +5485 Provider error + +5486 See clause 7.6.1 for the use of this parameter. + +## 5487 8.5.3 MAP\_AUTHENTICATION\_FAILURE\_REPORT service + +### 5488 8.5.3.1 Definition + +5489 This service is used between the VLR and the HLR or between the SGSN or HLR for reporting of authentication + 5490 failures. + +### 5491 8.5.3.2 Service primitives + +5492 The service primitives are shown in table 8.5/3. + +5493 **Table 8.5/3: MAP\_AUTHENTICATION\_FAILURE\_REPORT parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| Failure cause | M | M(=) | | | +| Re-attempt | M | M(=) | | | +| Access Type | M | M(=) | | | +| Rand | M | M(=) | | | +| VLR number | C | C(=) | | | +| SGSN number | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +5494 + +### 5495 8.5.3.3 Parameter use + +5496 Invoke id + +5497 See clause 7.6.1 for the use of this parameter. + +5498 IMSI + +5499 See clause 7.6.2 for the use of this parameter. + +5500 Failure Cause + +5501 See clause 7.6.7 for use of this parameter. + +5502 + +5503 Re-attempt + +5504 See clause 7.6.7 for use of this parameter. + +5505 Access Type + +5506 See clause 7.6.7 for use of this parameter. + +5507 Rand + +5508 This parameter identifies the specific AV that failed authentication. + +5509 See clause 7.6.7 for use of this parameter. + +5510 VLR number + +5511 Shall be present if the sender is VLR. See definition in clause 7.6.2. + +5512 SGSN number + +5513 Shall be present if the sender is SGSN. See definition in clause 7.6.2. + +5514 User error + +5515 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following +5516 values defined in clause 7.6.1: + +- 5517 - Unknown Subscriber; +- 5518 - System Failure; +- 5519 - Unexpected Data Value. + +5520 Provider error + +5521 These are defined in clause 7.6. + +## 5522 8.6 Security management services + +### 5523 8.6.1 MAP\_SET\_CIPHERING\_MODE service + +#### 5524 8.6.1.1 Definitions + +5525 This service is used between the VLR and the MSC to set the ciphering mode and to start ciphering if applicable. It is +5526 called when another service requires that information is to be sent on the radio path in encrypted form. + +5527 The service is a non-confirmed service and consists of two service primitives. + +#### 5528 8.6.1.2 Service primitives + +5529 The service primitives are shown in table 8.6/1. + +5530 + +**Table 8.6/1: MAP\_SET\_CIPHERING\_MODE parameters** + +| Parameter name | Request | Indication | +|----------------|---------|------------| +| Invoke id | M | M(=) | +| Ciphering mode | M | M(=) | +| Kc | C | C(=) | + +5531 + +### 8.6.1.3 Parameter use + +#### Invoke id + +See clause 7.6.1 for the use of this parameter. + +#### Ciphering mode + +See clause 7.6.7 for the use of this parameter. + +#### Kc + +The Kc parameter should be included when the ciphering mode parameter indicates that ciphering must be performed. + +## 8.7 International mobile equipment identities management services + +### 8.7.1 MAP\_CHECK\_IMEI service + +#### 8.7.1.1 Definition + +This service is used between the VLR and the MSC, between the MSC and the EIR, between the SGSN and EIR, and between IWF and EIR to request check of IMEI. If the IMEI is not available in the MSC or in the SGSN, it is requested from the MS and transferred to the EIR in the service request. + +This service may also be used to request the BMUEF from the EIR. + +The service is a confirmed service and consists of four service primitives. + +#### 8.7.1.2 Service primitives + +The service primitives are shown in table 8.7/1. + +**Table 8.7/1: MAP\_CHECK\_IMEI parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|--------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMEI | C | C(=) | C | C(=) | +| IMEISV | C | C(=) | C(=) | C(=) | +| Requested Equipment Info | M | M(=) | | | +| Equipment status | | | C | C(=) | +| BMUEF | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +### 8.7.1.3 Parameter use + +#### Invoke id + +See clause 7.6.1 for the use of this parameter. + +#### Requested Equipment Info + +This parameter indicates whether Equipment Status or BMUEF or both is requested. + +5557 IMEI + +5558 See clause 7.6.2 for the use of this parameter. The parameter shall not be included in the service request between the +5559 VLR and the MSC, but one of IMEI and IMEISV is mandatory in the service request from the MSC to the EIR, from +5560 the SGSN to the EIR and from the IWF to the EIR. It is not included in the service response from the EIR to the MSC, +5561 the SGSN or the IWF, but one of IMEI and IMEISV is mandatory in the service response from the MSC to the VLR on +5562 successful outcome. + +5563 IMEISV + +5564 See clause 7.6.2 for the use of this parameter. IMEISV shall be present if BMUEF is requested. + +5565 Equipment status + +5566 See clause 7.6.3 for the use of this parameter. This parameter is sent by the responder in case of successful outcome of +5567 the service if Equipment status was requested. + +5568 BMUEF + +5569 See clause 7.6.4 for the use of this parameter. This parameter is sent by the responder in case of successful outcome of +5570 the service if BMUEF was requested. + +5571 User error + +5572 One of the following error causes defined in clause 7.6.1 shall be sent by the user in case of unsuccessful outcome of +5573 the service, depending on the respective failure reason: + +- 5574 - unknown equipment; +5575 this error is returned by the responder when the IMEI is not known in the EIR; +- 5576 - system failure; +- 5577 - data missing. + +5578 Provider error + +5579 See clause 7.6.1 for the use of this parameter. + +## 5580 8.7.2 MAP\_OBTAIN\_IMEI service + +### 5581 8.7.2.1 Definition + +5582 This service is used between the VLR and the MSC to request the IMEI. If the IMEI is not available in the MSC, it is +5583 requested from the MS. + +5584 The service is a confirmed service and consists of four service primitives. + +### 5585 8.7.2.2 Service primitives + +5586 The service primitives are shown in table 8.7/2. + +5587 **Table 8.7/2: MAP\_OBTAIN\_IMEI parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMEI | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +5588 + +### 5589 8.7.2.3 Parameter use + +5590 Invoke id + +5591 See clause 7.6.1 for the use of this parameter. + +5592 IMEI + +5593 See clause 7.6.2 for the use of this parameter. The parameter is included in the service response from the MSC to the + +5594 VLR on successful outcome of the service. + +5595 User error + +5596 If the service fails, the VLR sends the user error System Failure (see clause 7.6.1) to the MSC. + +5597 Provider error + +5598 See clause 7.6.1 for the use of this parameter. + +## 5599 8.8 Subscriber management services + +### 5600 8.8.1 MAP-INSERT-SUBSCRIBER-DATA service + +#### 5601 8.8.1.1 Definition + +5602 This service is used by an HLR to update a VLR with certain subscriber data in the following occasions: + +- 5603 - the operator has changed the subscription of one or more supplementary services, basic services or data of a +- 5604 subscriber. Note that in case of withdrawal of a Basic or Supplementary service this primitive shall not be used; +- 5605 - the operator has applied, changed or removed Operator Determined Barring; +- 5606 - the subscriber has changed data concerning one or more supplementary services by using a subscriber procedure; +- 5607 - the HLR provides the VLR with subscriber parameters at location updating of a subscriber or at restoration. In +- 5608 this case, this service is used to indicate explicitly that a supplementary service is not provisioned, if the +- 5609 supplementary service specification requires it. The only supplementary services which have this requirement +- 5610 are the CLIR and COLR services. Network access mode is provided only in restoration. If the Super-Charger +- 5611 functionality is supported the HLR may not need to provide the VLR with subscriber parameters at location +- 5612 updating of a subscriber. See TS 23.116. + +5613 Also this service is used by an HLR to update an SGSN with certain subscriber data in the following occasions: + +- 5614 - if the GPRS subscription has changed; +- 5615 - if the network access mode is changed; +- 5616 - the operator has applied, changed or removed Operator Determined Barring; +- 5617 - the subscriber has changed data concerning one or more supplementary services by using a subscriber procedure; +- 5618 - the HLR provides the SGSN with subscriber parameters at GPRS location updating of a subscriber. If the +- 5619 Super-Charger functionality is supported the HLR may not need to provide the SGSN with subscriber parameters. See +- 5620 3GPP TS 23.116. + +5621 Also this service is used by a CSS to update an SGSN or a VLR with VPLMN-CSG-Subscription data in the following + +5622 occasions: + +- 5623 - if the VPLMN-CSG subscription data has changed; +- 5624 - the CSS provides the VLR or SGSN with VPLMN-CSG subscription data at VCSG location updating of a +- 5625 subscriber. + +5626 + +5627 In an EPS, this service is used by an HSS to update an MME via IWF with certain subscriber data in the following + +5628 occasions: + +- 5629 - the EPS subscription has changed; +- 5630 - the operator has applied, changed or removed Operator Determined Barring; +- 5631 - the HSS provides the MME via IWF(MME) with subscriber parameters at EPS location updating of a subscriber +- 5632 unless an explicit indication to skip subscriber data update has been received. + +5633 In an EPS, this service is used by an IWF to indicate to the MME via IWF that the HSS has requested to be notified + +5634 when the UE has become reachable. + +5635 It is a confirmed service and consists of the primitives shown in table 8.8/1. + +## 5636 8.8.1.2 Service primitives + +5637 + +**Table 8.8/1: MAP-INSERT-SUBSCRIBER-DATA** + +| Parameter name | Request | Indication | Response | Confirm | +|-----------------------------------------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | C | C(=) | | | +| MSISDN | C | C(=) | | | +| Additional MSISDN | C | C(=) | | | +| Category | C | C(=) | | | +| Subscriber Status | C | C(=) | | | +| Bearer service List | C | C(=) | C | C(=) | +| Teleservice List | C | C(=) | C | C(=) | +| Forwarding information List | C | C(=) | | | +| Call barring information List | C | C(=) | | | +| CUG information List | C | C(=) | | | +| SS-Data List | C | C(=) | | | +| eMLPP Subscription Data | C | C(=) | | | +| MC-Subscription Data | C | C(=) | | | +| Operator Determined Barring General data | C | C(=) | C | C(=) | +| Operator Determined Barring HPLMN data | C | C(=) | | | +| Roaming Restriction Due To Unsupported Feature | C | C(=) | | | +| Regional Subscription Data | C | C(=) | | | +| VLR CAMEL Subscription Info | C | C(=) | | | +| Voice Broadcast Data | C | C(=) | | | +| Voice Group Call Data | C | C(=) | | | +| Network access mode | C | C(=) | | | +| GPRS Subscription Data | C | C(=) | | | +| EPS Subscription Data | C | C(=) | | | +| VPLMN LIPA Allowed | C | C(=) | | | +| Roaming Restricted In SGSN/MME Due To Unsupported Feature | C | C(=) | | | +| North American Equal Access preferred Carrier Id List | U | C(=) | | | +| SGSN CAMEL Subscription Info | C | C(=) | | | +| LSA Information | C | C(=) | | | +| IST Alert Timer | C | C(=) | | | +| SS-Code List | | | C | C(=) | +| LMU Identifier | C | C(=) | | | +| LCS Information | C | C(=) | | | +| CS Allocation/Retention priority | C | C(=) | | | +| Super-Charger Supported In HLR | C | C(=) | | | +| Subscribed Charging Characteristics | C | C(=) | | | +| Access Restriction Data | C | C(=) | | | +| ICS Indicator | U | C(=) | | | +| CSG Subscription Data | C | C(=) | | | +| VPLMN CSG Subscription Data | C | C(=) | | | +| UE Reachability Request Indicator | C | C(=) | | | +| SGSN Number | C | C(=) | | | +| MME-Name | C | C(=) | | | +| Subscribed Periodic RAU-TAU Timer | C | C(=) | | | + +| Parameter name | Request | Indication | Response | Confirm | +|-------------------------------------------|---------|------------|----------|---------| +| Subscribed Periodic LAU Timer | C | C(=) | | | +| MDT User Consent | C | C(=) | | | +| PS and SMS-Only Service Provision | C | C(=) | | | +| SMS in SGSN Allowed | C | C(=) | | | +| CS-to-PS-SRVCC-Allowed-Indicator | C | C(=) | | | +| P-CSCF Restoration Request | C | C(=) | | | +| Adjacent Access Restriction Data | C | C(=) | | | +| IMSI-Group-Id List | C | C(=) | | | +| UE Usage Type | C | C(=) | | | +| User Plane Integrity Protection Indicator | C | C(=) | | | +| DL-Buffering Suggested Packet Count | C | C(=) | | | +| Reset-IDs | C | C(=) | | | +| eDRX-Cycle-Length List | C | C(=) | | | +| IAB-Operation-Allowed-Indicator | C | C(==) | | | +| Regional Subscription Response | | | C | C(=) | +| Supported CAMEL Phases | | | C | C(=) | +| Offered CAMEL 4 CSIs | | | C | C(=) | +| Supported Features | | | U | C(=) | +| User error | | | U | C(=) | +| Provider error | | | | O | + +5638 + +### 5639 8.8.1.3 Parameter use + +5640 All parameters are described in clause 7.6. The following clarifications are applicable: + +#### 5641 Network access mode + +5642 This parameter defines if the subscriber has access to MSC/VLR and/or to SGSN/MME. This parameter is used by +5643 SGSN/MME and MSC/VLR. In VLR, the parameter is used only as part of Restore Data Procedure and the parameter is +5644 not stored in the VLR. This parameter shall always be sent to the SGSN and via IWF to the MME as part of the GPRS +5645 subscriber data at GPRS/MME location updating. It shall be sent to the SGSN and via IWF to the MME if it is changed +5646 as a result of administrative action. + +5647 This parameter shall not be used by the CSS. + +5648 + +#### 5649 IMSI + +5650 It is only included if the service is not used in an ongoing transaction (e.g. location updating). This parameter is used by +5651 the VLR and the SGSN and IWF. + +#### 5652 MSISDN + +5653 For subscriptions with MSISDN: +5654 It is included at location updating and when it is changed. The MSISDN sent shall be the basic MSISDN. This +5655 parameter is used by the VLR and the SGSN and IWF. + +5656 For a subscription without MSISDN: +5657 The HLR shall not populate this parameter if the VLR or SGSN explicitly indicated support of MSISDN-less +5658 operation. + +5659 NOTE 1: See clauses 8.1.2.3 and 8.1.7.3 for the case where the VLR or SGSN does not support MSISDN-less +5660 operation. + +#### 5661 Additional MSISDN + +5662 If subscribed, the Additional MSISDN is included at location updating and when it is changed. This parameter is used +5663 by the SGSN and IWF. This parameter shall be ignored by the VLR if received. + +5664 If the SGSN does not indicate support of the feature the HSS shall not send the parameter. + +#### 5665 Category + +5666 It is included either at location updating or when it is changed. This parameter is used only by the VLR and if the SGSN +5667 or IWF receives this parameter it shall ignore it. + +5668 Subscriber Status + +5669 It is included either at location updating or when it is changed. + +5670 To apply, remove or update Operator Determined Barring Categories the Subscriber Status is set to Operator +5671 Determined Barring. In this case ODB General Data shall also be present. If the Operator Determined Barring applies +5672 and the subscriber is registered in the HPLMN and HPLMN specific Operator Determined Barring applies then ODB +5673 HPLMN Specific Data shall also be present. + +5674 To remove all Operator Determined Barring Categories the Subscriber Status shall be set to "Service Granted". This +5675 parameter is used by the VLR and the SGSN and IWF. + +5676 This parameter shall not be used by the CSS. + +5677 + +5678 Bearer service List + +5679 A list of Extensible Bearer service parameters (Extensible Bearer service is defined in clause 7.6). An Extensible Bearer +5680 service parameter must be the code for an individual Bearer service, except in the cases described below. + +5681 The codes for the Bearer service groups "allAlternateSpeech-DataCDA" and "allAlternateSpeech-DataCDS" shall, if +5682 applicable, be sent from the HLR to the VLR as a pair. The codes for the Bearer service groups +5683 "allSpeechFollowedByDataCDA" and "allSpeechFollowedByDataCDS" shall, if applicable, be sent from the HLR to +5684 the VLR as a pair. + +5685 If it is included in the Request/Indication, it includes either all Extensible Bearer services subscribed (at location +5686 updating or at restoration) or only the ones added (at subscriber data modification). + +5687 If the VLR receives an Indication containing any Extensible Bearer service parameters which it does not +5688 support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Bearer services (no +5689 error is sent back), except in the cases described below. + +5690 If the VLR receives the codes for the Bearer service groups "allSpeechFollowedByDataCDA" and +5691 "allSpeechFollowedByDataCDS" and supports one or more of the circuit-switched synchronous or asynchronous data +5692 rates specified for simple data bearer services, it shall accept the bearer service codes, and not return them in the +5693 response to the HLR. If the VLR does not support any of the circuit-switched synchronous or asynchronous data rates +5694 specified for simple data bearer services, and receives the pair of codes for "allAlternateSpeech-DataCDA" and +5695 "allAlternateSpeech-DataCDS" or the pair of codes for "allSpeechFollowedByDataCDA" and +5696 "allSpeechFollowedByDataCDS", it shall reject the pair of codes by returning them in the response to the HLR. This +5697 parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it. + +5698 This parameter shall not be used by the CSS. + +5699 + +5700 Teleservice List + +5701 A list of Extensible Teleservice parameters (Extensible Teleservice is defined in clause 7.6). An Extensible Teleservice +5702 parameter must be the code for an individual Teleservice. + +5703 If it is included in the Request/Indication, it contains either all Extensible Teleservices subscribed (at location updating +5704 or at restoration) or the ones added (at subscriber data modification). Only the Extensible Teleservices that are relevant +5705 to the node at which the message is received should be included in the Teleservice List. + +5706 If the VLR or the SGSN or the IWF receives an Indication containing any Extensible Teleservice parameters which it +5707 does not support/allocate it returns them in the response to the HLR and discards the unsupported Extensible +5708 Teleservices (no error is sent back). This parameter is used by the VLR and the SGSN and the IWF. + +5709 This parameter shall not be used by the CSS. + +5710 + +#### 5711 Forwarding information List + +5712 A list of Extensible Forwarding information parameters (Extensible Forwarding information is defined in clause 7.6). It +5713 includes Call Forwarding services either at location updating or at restoration or when they are changed. Each +5714 Extensible Forwarding information parameter shall be treated independently of all other parameters in the primitive. + +5715 The Extensible Forwarding information shall include the SS-Code for an individual call forwarding supplementary +5716 service. The Extensible Forwarding information shall contain one or more Extensible Forwarding Features (Extensible +5717 Forwarding Feature is defined in clause 7.6). + +5718 The Extensible Forwarding Feature may include an Extensible Basic Service Group. This shall be interpreted according +5719 to the rules in clause 8.8.1.4. + +5720 The Extensible Forwarding Feature shall contain an Extensible SS-Status parameter. + +5721 If the Extensible SS-Status indicates that call forwarding is registered then (except for call forwarding unconditional) +5722 the Extensible Forwarding Feature shall contain a number to define the forwarded-to destination and, if available, the +5723 forwarded-to subaddress. In other states the forwarded-to number and, if applicable, the forwarded-to subaddress shall +5724 not be included. For call forwarding unconditional the forwarded-to number and, if applicable, the forwarded-to +5725 subaddress shall not be included. If the VLR does not receive a forwarded-to subaddress then it shall assume that a +5726 forwarded-to subaddress has not been registered. + +5727 The Extensible Forwarding Feature shall contain the extensible forwarding options (except for call forwarding +5728 unconditional where the extensible forwarding options shall not be included). Bits 3 and 4 of the extensible forwarding +5729 options shall be ignored by the VLR, and may be set to any value by the HLR. + +5730 For call forwarding on no reply: If the extensible SS-Status indicates that call forwarding is registered then the +5731 Extensible Forwarding Feature shall contain an extensible no reply condition timer. In other states the no reply +5732 condition timer shall not be included. + +5733 For call forwarding services other than call forwarding on no reply: The Extensible Forwarding Feature shall not +5734 contain a no reply condition timer. + +5735 If the VLR receives an Indication containing any Call Forwarding service codes which it does not support/allocate it +5736 returns them to the HLR in the parameter SS-Code List and discards the unsupported Call Forwarding service codes +5737 (no error is sent back). This parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall +5738 ignore it. + +5739 This parameter shall not be used by the CSS. + +5740 + +#### 5741 Call barring information List + +5742 A list of Extensible Call barring information parameters (Extensible Call barring information is defined in clause 7.6). It +5743 includes Call Barring services either at location updating or at restoration or when they are changed. Each Extensible +5744 Call barring information parameter shall be treated independently of all other parameters in the primitive. + +5745 The Extensible Call barring information shall include the SS-Code for an individual call barring supplementary service. +5746 The Extensible Call barring information shall contain one or more Extensible Call Barring Features (Extensible Call +5747 Barring Feature is defined in clause 7.6). + +5748 The Extensible Call Barring Feature may include an Extensible Basic Service Group. This shall be interpreted +5749 according to the rules in clause 8.8.1.4. + +5750 The Extensible Call Barring Feature shall contain an extensible SS-Status parameter. + +5751 If the VLR or the SGSN or the IWF receives an Indication containing any Extensible Call Barring service codes which +5752 it does not support/allocate it returns them to the HLR in the parameter SS-Code List and discards the unsupported +5753 Extensible Call Barring service codes (no error is sent back). + +5754 This parameter shall not be used by the CSS. + +#### 5755 CUG information List + +5756 A list of CUG information list parameters (CUG information is defined in clause 7.6). It includes CUG information +5757 either at location updating or at restoration or when it is changed. + +5758 At location updating, restoration or when there is a change in CUG data, the HLR shall include the complete +5759 CUG-SubscriptionList and, if there are options per basic group, it shall also include the complete CUG-FeatureList. If +5760 there are not options per extensible basic service group the CUG-FeatureList shall not be included. + +5761 In any dialogue, the first insertSubscriberData message which contains CUG information shall include a non-empty +5762 CUG-SubscriptionList. + +5763 When the VLR receives CUG data it shall replace the stored CUG data with the received data set. + +5764 If CUG-FeatureList is omitted in the Insert Subscriber Data operation VLR shall interpret that no options per extensible +5765 basic service group exist, and then it shall apply the default values i.e. no outgoing access, no incoming access, no +5766 preferential CUG exists. + +5767 If CUG-Feature is received without preferential CUG, the VLR shall interpret that no preferential CUG applies. + +5768 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error +5769 Unexpected Data Value. + +5770 Note that data consistency between CUG subscription data and CUG feature data is the responsibility of the HLR. + +5771 If the VLR does not support the CUG service it returns its code to the HLR in the parameter SS-Code List and discards +5772 the received information (no error is sent back). This parameter is used only by the VLR and if the SGSN or IWF +5773 receives this parameter it shall ignore it. + +5774 This parameter shall not be used by the CSS. + +#### 5775 SS-Data List + +5776 A list of Extensible SS-Data parameters (Extensible SS-Data is defined in clause 7.6). It is sent for any other +5777 supplementary service than Call Forwarding, Call Barring, CUG and eMLPP either at location updating or at restoration +5778 or when they are changed. Each SS-Data parameter shall be treated independently of all other parameters in the +5779 primitive. + +5780 The Extensible SS-Data shall include the SS-Code for an individual supplementary service. + +5781 The Extensible SS-Data shall contain an Extensible SS-Status parameter and any subscription options that are +5782 applicable to the service defined by the SS-Code. + +5783 The SS-Data may include a Basic Service Group List. This shall be interpreted according to the rules in clause 8.8.1.4. + +5784 If the VLR receives an Indication containing any supplementary service codes which it does not support/allocate it +5785 returns them to the HLR in the parameter SS-Code List and therefore discards the unsupported service codes received +5786 (no error is sent back). + +5787 This parameter is used by the SGSN only for LCS. If the SGSN receives an Indication containing any LCS related +5788 supplementary service codes which it does not support/allocate it returns them to the HLR in the parameter SS-Code +5789 List and therefore discards the unsupported service codes received (no error is sent back). SS-codes not related to the +5790 supported LCS capability set shall be discarded. + +5791 If the IWF receives an Indication containing any LCS related supplementary service codes, it returns them to the HSS in +5792 the parameter SS-Code List and therefore discards the service codes received (no error is sent back). SS-codes not +5793 related to the supported LCS capability set shall be discarded. + +5794 This parameter shall not be used by the CSS. + +#### 5795 Operator Determined Barring General data + +5796 If it is included in a Request/Indication, it includes all the Operator Determined Barring categories that may be applied +5797 to a subscriber registered in any PLMN. This parameter is only included in a Request/Indication when the parameter +5798 Subscriber Status is set to the value Operator Determined Barring. Note that all General Operator Determined Barring +5799 Categories shall be set to their actual status. + +5800 If the VLR or the SGSN or IWF receives an Indication containing Operator Determined Barring General Data which +5801 shows that the subscriber is subject to barring not supported / not allocated by the VLR or by the SGSN, it returns +5802 Operator Determined Barring General Data in the response to the HLR to show the barring categories which are not +5803 supported / not allocated by the VLR or by the SGSN. This parameter is used by the VLR and the SGSN and IWF. + +5804 This parameter shall not be used by the CSS. + +5805 Operator Determined Barring HPLMN data + +5806 It includes all the Operator Determined Barring categories that may be applied only to a subscriber registered in the +5807 HPLMN. Therefore, it shall only be transferred to the VLR or to the SGSN or IWF when the subscriber is roaming into +5808 the HPLMN and when the parameter Subscriber Status is set to the value Operator Determined Barring. Note that all +5809 HPLMN Operator Determined Barring Categories shall be set to their actual status. + +5810 If Subscriber Status is set to the value Operator Determined Barring and no Operator Determined Barring HPLMN data +5811 is present then the VLR or the SGSN or IWF shall not apply any HPLMN specific ODB services to the subscriber. This +5812 parameter is used by the VLR and the SGSN and IWF. + +5813 This parameter shall not be used by the CSS. + +5814 eMLPP Subscription Data + +5815 If included in the Insert Subscriber Data request this parameter defines the priorities the subscriber might apply for a +5816 call (as defined in clause 7.6). It contains both subparameters of eMLPP. + +5817 If the VLR does not support the eMLPP service it returns its code to the HLR in the parameter SS-Code List and +5818 therefore discards the received information (no error is sent back). + +5819 eMLPP subscription data that have been stored previously in a subscriber data record in the VLR are completely +5820 replaced by the new eMLPP subscription data received in a MAP\_INSERT\_SUBSCRIBER\_DATA during either an +5821 Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure. This parameter is used +5822 only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it. + +5823 This parameter shall not be used by the CSS. + +5824 MC Subscription Data + +5825 If included in the Insert Subscriber Data request, this parameter provides the MC Subscription Data as defined in +5826 clause 7.6. + +5827 If the VLR does not support the MC service, it returns its code to the HLR in the parameter SS-Code List and therefore +5828 discards the received information (no error is sent back). + +5829 MC subscription data that have been stored previously in a subscriber data record in the VLR are completely replaced +5830 by the new MC subscription data received in a MAP\_INSERT\_SUBSCRIBER\_DATA during either an Update +5831 Location or Restore Data procedure or a stand alone Insert Subscriber data procedure. This parameter is used only by +5832 the VLR and if the SGSN or IWF receives this parameter it shall ignore it. + +5833 This parameter shall not be used by the CSS. + +5834 Roaming Restriction Due To Unsupported Feature + +5835 The HLR may decide to include this parameter in the request if certain services or features are indicated as not +5836 supported by the MSC/VLR (e.g. Advice of Charge Charging Level). + +5837 If this parameter is sent to the VLR the MSC area is restricted by the HLR and the VLR. This parameter is used only by +5838 the VLR and if the SGSN or the IWF receives this parameter it shall ignore it. + +5839 This parameter shall not be used by the CSS. + +5840 Regional Subscription Data + +5841 If included in the Insert Subscriber Data request this parameter defines the subscriber's subscription area for the +5842 addressed VLR, for the addressed SGSN or for the addressed MME (as defined in clause 7.6). It contains the complete +5843 list of up to 10 Zone Codes that apply to a subscriber in the currently visited PLMN. The HLR shall send only those +5844 Zone Codes which are stored against the CC and NDC of the VLR, the SGSN or the MME to be updated. + +5845 NOTE 2: Support of this parameter is a network operator option and it will not be sent to networks which do not +5846 support Regional Subscription. + +5847 Regional subscription data that have been stored previously in a subscriber data record in the VLR, in the SGSN or in +5848 the MME are completely replaced by the regional subscription data received in an Insert Subscriber Data indication +5849 during either an Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure. + +5850 After the regional subscription data are inserted the VLR or the SGSN shall derive whether its location areas are +5851 allowed or not. If the whole MSC or SGSN area is restricted it will be reported to HLR by returning the Regional +5852 Subscription Response. + +5853 The VLR or the SGSN returns a Regional Subscription Response indicating that a problem with the Zone Code has +5854 been detected in one of the following cases: + +- 5855 - Too Many Zone Codes: more than 10 Zone Codes are to be stored in the VLR or in the SGSN. +- 5856 - Regional Subscription Not Supported by the VLR or the SGSN. +- 5857 - Zone Codes Conflict: the VLR or the SGSN detects that the zone codes indicate conflicting service permission +5858 for a location area. + +5859 Zone codes which have no mapping to location areas shall be ignored. + +5860 If a sequence of MAP\_INSERT\_SUBSCRIBER\_DATA services is used during a dialogue, Regional Subscription Data +5861 shall be accepted only in one service. Regional Subscription Data received in a subsequent service shall be rejected with +5862 the error Unexpected Data Value. + +5863 If Regional Subscription Data are not included in any MAP\_INSERT\_SUBSCRIBER\_DATA service, there is no +5864 restriction of roaming due to Regional Subscription. This parameter is used by the VLR, the SGSN and the IWF. + +5865 This parameter shall not be used by the CSS. + +#### 5866 Voice Broadcast Data + +5867 This parameter contains a list of group id's a user might have subscribed to; (VBS-Data is defined in clause 7.6). It +5868 includes VBS information either at location updating or at restoration or when it is changed. + +5869 At location updating, restoration or when there is a change in VBS data, the HLR shall include the complete VBS-Data. + +5870 When the VLR receives VBS-Data within a dialogue it shall replace the stored VBS-data with the received data set. All +5871 subsequent VBS-data received within this dialogue shall be interpreted as add-on data. + +5872 If VBS-data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VBS data. + +5873 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error +5874 Unexpected Data Value. This parameter is used only by the VLR and if the SGSN or the IWF receives this parameter it +5875 shall ignore it. + +5876 This parameter shall not be used by the CSS. + +#### 5877 Voice Group Call Data + +5878 This parameter contains a list of group id's a user might have subscribed to; see clause 7.6. + +5879 At location updating, restoration or when there is a change in VGCS data, the HLR shall include the complete +5880 VGCS-Data. + +5881 When the VLR receives VGCS-Data within a dialogue it shall replace the stored VGCS-Data with the received data set. +5882 All VGCS-Data received within this dialogue shall be interpreted as add-on data. + +5883 If VGCS-Data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VGCS-Data. + +5884 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error +5885 Unexpected Data Value. This parameter is used only by the VLR and if the SGSN or the IWF receives this parameter it +5886 shall ignore it. + +5887 This parameter shall not be used by the CSS. + +5888 North American Equal Access preferred Carrier Id List + +5889 A list of the preferred carrier identity codes that are subscribed to. + +5890 When the VLR receives this parameter from the HLR, it shall replace the previously stored preferred carrier identity +5891 codes with the received ones. It is not possible to delete all the preferred carrier identity codes from the VLR using this +5892 service. To delete all the preferred carrier identity codes from the VLR, the HLR shall use the +5893 MAP\_CANCEL\_LOCATION service. + +5894 This parameter shall not be used by the CSS. + +5895 LSA Information + +5896 If included in the ISD request, this parameter contains a list of localised service area identities a user might have +5897 subscribed to together with the priority, the preferential access indicator, the active mode support indicator and active +5898 mode indication of each localised service area; see clause 7.6. The access right outside these localised service areas is +5899 also indicated. In all cases mentioned below, the LSA information shall only include LSA Data applicable to the +5900 VPLMN where the Subscriber is located. The VLR number, received in the MAP-UPDATE\_LOCATION primitive, or +5901 the SGSN number, received in the MAP\_UPDATE\_GPRS\_LOCATION primitive, can be used, alongside data stored +5902 in the HLR, to determine the LSA Data applicable to the VPLMN. + +5903 At restoration, location updating or GPRS location updating the HLR shall include the complete set of applicable LSA +5904 Information. + +5905 When there is a change in LSA data the HLR shall include at least the new and/or modified LSA data. + +5906 When there is a change in the access right outside the localised service areas the HLR shall include the LSA only access +5907 indicator. + +5908 When the SGSN or the VLR receives LSA information within a dialogue it shall check if the received data has to be +5909 considered as the entire LSA information. If so, it shall replace the stored LSA information with the received data set, +5910 otherwise it shall replace the data only for the modified LSA data (if any) and/or access right, and add the new LSA +5911 data (if any) to the stored LSA Information. + +5912 If the entire LSA information is received, it shall always include the LSA only access indicator value together with the +5913 LSA data applicable for the PLMN (if any). + +5914 If LSA Information is omitted in the Insert Subscriber Data operation the SGSN or the VLR shall keep the previously +5915 stored LSA Information. + +5916 If the SGSN or the VLR detects that there is overlapping in the information received within a dialogue, it shall send the +5917 error Unexpected Data Value. This parameter is used by the VLR and the SGSN, and if the IWF receives this parameter +5918 it shall ignore it. + +5919 This parameter shall not be used by the CSS. + +5920 IST Alert Timer + +5921 This parameter contains the IST Alert timer value that must be used to inform the HLR about the call activities that the +5922 subscriber performs. + +5923 At Location Updating, restoration, or when there is a change in the IST data defined for the Subscriber, the HLR shall +5924 include the IST Alert timer. + +5925 This parameter shall not be used by the CSS. + +5926 LMU Identifier + +5927 This parameter indicates the presence of an LMU. This parameter is used only by the VLR and shall be ignored if +5928 received by an SGSN or an IWF. + +5929 This parameter shall not be used by the CSS. + +5930 LCS Information + +5931 This parameter provides the following LCS related information for an MS subscriber: + +5932 - list of GMLCs in the HPLMN; + +5933 - privacy exception list; + +5934 - MO-LR list. + +5935 At restoration and location updating, the HLR shall include the complete LCS data of the subscriber. + +5936 When there is a change in LCS subscriber data the HLR shall include at least the new and/or modified LCS data. LCS +5937 data that is not modified need not be included. + +5938 The VLR/SGSN shall keep any previously stored LCS Information that is not included in an Insert Subscriber Data +5939 operation. + +5940 If the VLR/SGSN detects that there is overlapping in the LCS information received within a dialogue, it shall send the +5941 error Unexpected Data Value. However, if the VLR receives the LCS code in both the LCS Information and the +5942 SS-Data List, then the VLR shall not interpret this as overlapping data. This parameter is used by the VLR and the +5943 SGSN and the IWF. + +5944 This parameter shall not be used by the CSS. + +#### 5945 Super-Charger Supported In HLR + +5946 This parameter is used by the HLR to indicate support for the Super-Charger functionality. If this parameter is present it +5947 shall include an indication of the age of the subscription data stored in the HLR. + +5948 If this parameter is absent then the HLR does not support the Super-Charger functionality. + +5949 This parameter shall not be used by the CSS. + +#### 5950 SS-Code List + +5951 The list of SS-Code parameters for the services that are provided to a subscriber but are not supported/allocated by the +5952 VLR/SGSN/IWF (SS-Code is defined in clause 7.6). The list can only include individual SS-Codes that were sent in the +5953 service request. For the VLR, this list can also include SS-Codes for the eMLPP and/or CUG services if the above +5954 mentioned conditions, as described in eMLPP Subscription Data and/or CUG information List, are met (that is, eMLPP +5955 Subscription Data and/or CUG information List are received). + +5956 This parameter shall not be used by the CSS. + +#### 5957 ICS-Indicator + +5958 This optional flag indicates to the MSC Server enhanced for ICS (see 3GPP TS 23.292 [135]) whether the MSC Server +5959 shall attempt the IMS registration. + +5960 This parameter is used by the VLR and the SGSN. + +5961 This parameter shall not be used by the CSS. + +#### 5962 CSG-Subscription Data + +5963 This parameter contains a list of CSG-Ids, the associated expiration dates (see 3GPP TS 22.011 [138]) and a list of +5964 corresponding APNs (see 3GPP TS 29.272 [144]). When the VLR or SGSN or MME receives CSG-Subscription Data +5965 from the HLR/HSS it shall replace the stored CSG-Subscription Data from the HLR/HSS (if any) with the received +5966 data. This parameter is used by the VLR and the SGSN and IWF, except the list of corresponding APNs is not +5967 applicable to the VLR, and the VLR shall ignore this list if it is received. + +5968 This parameter shall not be used by the CSS. + +#### 5969 VPLMN CSG Subscription Data + +5970 This parameter contains a list of CSG-Ids, the associated expiration dates (see 3GPP TS 22.011 [138]). When the VLR +5971 or SGSN or MME receives VPLMN CSG Subscription Data from the CSS, it shall replace the stored VPLMN-CSG +5972 Subscription Data from the CSS (if any) with the received VPLMN CSG Subscription data. This parameter is used by +5973 the VLR, the SGSN and MME. + +5974 This parameter is not applicable for the HLR/HSS, and the VLR or SGSN or IWF shall ignore this parameter if it is +5975 received from the HLR/HSS. + +5976 CSG Subscription Data from the HLR/HSS and VPLMN CSG Subscription Data from the CSS are managed +5977 independently in the VLR or SGSN or MME. If the same CSG Id exists in both CSG subscription data from the CSS +5978 and CSG subscription data from the HLR/HSS, the CSG subscription data from the HLR/HSS shall take precedence +5979 over the CSG subscription data from the CSS in further use. + +5980 UE Reachability Request Indicator + +5981 This parameter indicates by its presence that the HSS is awaiting a Notification of UE Reachability. This parameter is +5982 used by the IWF only. + +5983 This parameter shall not be used by the CSS. + +5984 MME Name + +5985 This parameter contains the MME identity used over the SGs interface (see 3GPP TS 23.003 [17] clause 19.4.2.4) when +5986 stored in the HSS. Otherwise this parameter contains the Diameter Identity of the MME (see 3GPP TS 23.003 [17]). If +5987 the subscriber is registered to EPS and the length of the MME Name does not exceed 55 octets, the HLR shall send the +5988 MME Name to the VLR during the data restoration procedure if the 'Restoration Indicator' is set in the +5989 MAP\_RESTORE\_DATA request, and during an Update Location procedure if the 'Restoration Indicator' is set in the +5990 MAP\_UPDATE\_LOCATION request. This parameter may be used by the MSC/VLR, e.g. to page the UE via SGs. + +5991 This parameter shall not be used by the CSS. + +5992 Subscribed Periodic RAU-TAU Timer + +5993 This parameter contains the subscribed periodic RAU/TAU timer (see 3GPP TS 23.401 [145] and 3GPP TS 23.060 +5994 [104]) and is used by the SGSN and MME (via IWF). The SGSN and MME shall handle the Subscribed Periodic RAU- +5995 TAU Timer as specified in clause 5.2.1.1.2 of 3GPP TS 29.272 [144]. + +5996 If the VLR receives this parameter it shall ignore it. + +5997 This parameter shall not be used by the CSS. + +5998 Subscribed Periodic LAU Timer + +5999 This parameter contains the subscribed periodic LAU timer value (see 3GPP TS 23.012 [23]) and is used by the +6000 MSC/VLR. The MSC/VLR shall handle the Subscribed Periodic LAU Timer as specified in clause 3.7.3 of 3GPP TS +6001 23.012 [23]. + +6002 If the SGSN receives this parameter it shall ignore it. + +6003 This parameter shall not be used by the CSS. + +6004 SGSN Number + +6005 This parameter contains the Identity of the SGSN (see 3GPP TS 23.003 [17]). If the subscriber is registered to GPRS, +6006 the HLR shall send the SGSN Number if available to the VLR during the data restoration procedure if the 'Restoration +6007 Indicator' is set in the MAP\_RESTORE\_DATA request, and during an Update Location procedure if the 'Restoration +6008 Indicator' is set in the MAP\_UPDATE\_LOCATION request. This parameter may be used by the MSC/VLR, e.g. to +6009 page the UE via Gs. + +6010 This parameter shall not be used by the CSS. + +6011 MDT User Consent + +6012 This parameter indicates the user consent availability for MDT activation, see 3GPP TS 32.422 [132]. This parameter is +6013 used by the VLR, the SGSN and the IWF. + +6014 This parameter shall not be used by the CSS. + +6015 PS and SMS-only Service Provision + +6016 This parameter indicates whether the subscription is for PS Only and permits CS service access only for SMS. + +6017 SMS in SGSN Allowed + +6018 This parameter indicates whether the HSS allows SMS to be provided by SGSN over NAS. + +6019 User Plane Integrity Protection Indicator + +6020 This parameter indicates by its presence that the SGSN may decide to activate integrity protection of the user plane +6021 when GERAN is used (see 3GPP TS 43.020 [24]). + +6022 If the VLR receives this parameter it shall ignore it. + +6023 DL-Buffering Suggested Packet Count + +6024 This parameter indicates a suggested DL-Buffering Packet Count. The MME (via IWF) and SGSN may take it into +6025 account in addition to local policies, to determine whether to invoke extended buffering of downlink packets at the +6026 SGW for High Latency Communication. Otherwise, the MME or SGSN shall make this determination based on local +6027 policies only (see 3GPP TS 29.272 [144]). + +6028 If the VLR receives this parameter it shall ignore it. + +6029 Reset-IDs + +6030 This parameter contains a list of subscribed Reset-IDs. + +6031 eDRX-Cycle-Length List + +6032 This list shall contain the subscribed eDRX cycle length, along with the RAT type to which it is applicable. + +6033 IAB-Operation-Allowed-Indicator + +6034 This parameter indicates by its presence that IAB operation is authorized for the UE. See 3GPP TS 401 [145]. + +6035 Regional Subscription Response + +6036 If included in the response this parameter indicates one of: + +- 6037 - Network Node Area Restricted entirely because of regional subscription; +- 6038 - Too Many Zone Codes to be inserted; +- 6039 - Zone Codes Conflict; +- 6040 - Regional Subscription not Supported by the VLR or by the SGSN or MME. + +6041 If the VLR determines after insertion of Regional Subscription Data that the entire MSC area is restricted, the VLR +6042 shall respond with a Regional Subscription Response indicating MSC Area Restricted. Otherwise MSC Area Restricted +6043 is not sent. The HLR shall check whether the current MSC area is no longer restricted. + +6044 If the SGSN determines after insertion of Regional Subscription Data that the entire SGSN area is restricted, the SGSN +6045 shall respond with a Regional Subscription Response indicating SGSN Area Restricted. Otherwise SGSN Area +6046 Restricted is not sent. The HLR shall check whether the current SGSN area is no longer restricted. This parameter is +6047 used by the VLR, the SGSN and the IWF. + +6048 This parameter shall not be used by the CSS. + +6049 VLR CAMEL Subscription Info + +6050 This parameter is sent for subscribers who have CAMEL services which are invoked in the MSC. + +- 6051 - In CAMEL phase 1, this parameter contains only the O-CSI. +- 6052 - In CAMEL Phase 2, this parameter may contain O-CSI, SS-CSI and TIF-CSI. In CAMEL Phase 2 and onwards, +6053 TDP-Criteria for O-CSI may be associated with O-CSI. +- 6054 - In CAMEL Phase 3, this parameter may contain O-CSI, D-CSI, SS-CSI, VT-CSI, MO-SMS-CSI, M-CSI and +6055 TIF-CSI. In CAMEL Phase 3 and onwards, TDP-Criteria for VT-CSI may be associated with VT-CSI. + +6056 - In CAMEL Phase 4, this parameter may contain O-CSI, D-CSI, SS-CSI, VT-CSI, MO-SMS-CSI, MT-SMS-CSI, +6057 M-CSI and TIF-CSI. In CAMEL Phase 4, TDP-Criteria for MT-SMS-CSI may be associated with MT-SMS- +6058 CSI. + +6059 The VLR CAMEL Subscription Info is sent at location updating or when any information in the applicable CAMEL +6060 Subscription Info in the HLR has been changed. + +6061 At location updating, the complete set of VLR CAMEL Subscription Info is sent in one dialogue. + +6062 When CAMEL Subscription Information is changed in the HLR and changed data have to be sent to the VLR, then: + +6063 - for CAMEL Phase 1 and CAMEL Phase 2, the complete set of VLR CAMEL Subscription Info is sent in one +6064 dialogue; + +6065 - for CAMEL Phase 3 or higher, one or more specific elements of VLR CAMEL Subscription Info are sent in one +6066 dialogue. + +6067 When the VLR receives a specific element of VLR CAMEL Subscription Info, it shall overwrite the corresponding +6068 specific element of VLR CAMEL Subscription Info (if any) which it has stored for that subscriber. + +6069 For CAMEL Phase 1 and CAMEL Phase 2 , the VLR CAMEL Subscription Info consists of any one or more of: + +6070 - O-CSI (irrespective of the value of the "CAMEL Capability Handling" inside O-CSI),TDP-Criteria for O- +6071 CSI,SS-CSI and TIF-CSI. + +6072 (The complete set of above shall be sent even if only one CSI has changed in case of stand alone ISD. The +6073 omitted elements of above list will be withdrawn in the VLR.) + +6074 From CAMEL phase 3 onwards, the specific elements of VLR CAMEL Subscription Info which may be sent are: + +6075 O-CSI (irrespective of the value of the "CAMEL Capability Handling" inside O-CSI), TDP criteria for O-CSI, SS- +6076 CSI and TIF-CSI; + +6077 (The complete set of above shall be sent even if only one CSI has changed in case of stand alone ISD. The +6078 omitted elements of above list will be withdrawn in the VLR.) + +6079 - D-CSI; + +6080 - VT-CSI; + +6081 - TDP-Criteria for VT-CSI; + +6082 - MO-SMS-CSI; + +6083 - MT-SMS-CSI; + +6084 - TDP-Criteria for MT-SMS-CSI; + +6085 - M-CSI. + +6086 If the VLR CAMEL Subscription Info is omitted in the Insert Subscriber Data operation the VLR shall keep the +6087 previously stored VLR CAMEL Subscription Info. Within one dialogue subsequent received data are interpreted as +6088 add-on data. If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the +6089 error Unexpected Data Value. This parameter is used only by the VLR and if the SGSN or IWF receives this parameter +6090 it shall ignore it. + +6091 The VLR CAMEL Subscription Info may contain the TIF-CSI (Translation Information Flag) for CAMEL Phase 2 and +6092 higher. See 3GPP TS 23.072 for the use of this parameter and the conditions for its presence. + +6093 This parameter shall not be used by the CSS. + +6094 Supported CAMEL Phases + +6095 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. This parameter is used +6096 by the VLR and SGSN. + +6097 A VLR or SGSN not supporting any CAMEL Phase may omit this parameter. An IWF shall omit this parameter. + +6098 This parameter shall not be used by the CSS. + +#### 6099 GPRS Subscription Data + +6100 This parameter contains a list of PDP-contexts a user has subscribed to; see clause 7.6. + +6101 At GPRS location updating the HLR shall include the complete GPRS Subscription Data. + +6102 When there is a change in GPRS subscriber data the HLR shall include only the new and/or modified PDP contexts. + +6103 When the SGSN receives GPRS Subscription Data within a dialogue it shall check if the received data has to be +6104 considered as the entire GPRS subscription data. If so, it shall replace the stored GPRS Subscription Data with the +6105 received data set, otherwise it shall replace the data only for the modified PDP contexts (if any) and add the new PDP +6106 contexts (if any) to the stored GPRS Subscription Data. + +6107 If GPRS Subscription Data is omitted in the Insert Subscriber Data operation the SGSN shall keep the previously stored +6108 GPRS Subscription Data. + +6109 If the SGSN detects that there is overlapping in the information received within a dialogue, it shall send the error +6110 Unexpected Data Value. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore +6111 it. + +6112 The SGSN shall handle the SIPTO-Permission information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2. + +6113 The SGSN shall handle the SIPTO-Local-Network-Permission information as specified in 3GPP TS 29.272 [144] +6114 clause 5.2.1.1.2. + +6115 The SGSN shall handle the LIPA Permission information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2. + +6116 The SGSN shall handle the Restoration-Priority information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2. + +6117 This parameter shall not be used by the CSS. + +#### 6118 EPS Subscription Data + +6119 This parameter contains: + +- 6120 - the UE level APN-OI Replacement (see 3GPP TS 23.401 [145]), and +- 6121 - the Subscriber Profile ID for RAT/Frequency Priority (RFSP-ID) (see 3GPP TS 23.401 [145], 3GPP TS 36.413 +6122 [147] and 3GPP TS 23.060 [104]), and +- 6123 - the AMBR (see 3GPP TS 23.401 [145] and 3GPP TS 23.060 [104]), and +- 6124 - a list of APN Configurations, +- 6125 - a session transfer number for SRVCC (STN-SR) (see 3GPP TS 23.003 [17]). +- 6126 - MPS CS Priority, which by its presence indicates the UE is subscribed to the eMLPP in the CS domain. +- 6127 - MPS EPS Priority, which by its presence indicates the UE is subscribed to the MPS in the EPS domain. +- 6128 - Subscribed vSRVCC (see 3GPP 29.272 [144]). + +6129 This parameter is used only by the MME via IWF and SGSN. If the VLR receives this parameter it shall ignore it. + +6130 The MPS CS Priority and MPS EPS Priority inside the parameter are used only by the MME via IWF. If the SGSN +6131 receives them it shall ignore them. + +6132 The SGSN shall handle the SIPTO-Permission information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2. + +6133 The SGSN shall handle the SIPTO-Local-Network-Permission information as specified in 3GPP TS 29.272 [144] +6134 clause 5.2.1.1.2. + +6135 The SGSN shall handle the LIPA Permission information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2. + +6136 The SGSN shall handle the Restoration-Priority information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2. + +6137 The SGSN shall handle the WLAN-offloadability information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2. + +6138 This parameter shall not be used by the CSS. + +6139 VPLMN LIPA Allowed + +6140 This parameter by its presence indicates that the UE is allowed to use LIPA in the PLMN where the UE is attached (see +6141 3GPP TS 23.401 [145] and 3GPP TS 23.060 [104]). + +6142 This parameter is used only by the IWF and SGSN. If the VLR receives this parameter it shall ignore it. + +6143 This parameter shall not be used by the CSS. + +6144 SGSN CAMEL Subscription Info + +6145 The SGSN CAMEL Subscription Info is sent at GPRS location updating or when any information in the applicable +6146 SGSN CAMEL Subscription Info in the HLR has been changed. + +6147 - In CAMEL Phase 3, this parameter may contain one or both of GPRS-CSI and MO-SMS-CSI. + +6148 - In CAMEL Phase 4, this parameter may contain GPRS-CSI, MO-SMS-CSI and MT-SMS-CSI and TDP-Criteria +6149 for MT-SMS-CSI. + +6150 At GPRS location updating the complete set of SGSN CAMEL Subscription Info is sent. + +6151 When CAMEL Subscription Information is changed in the HLR and changed data have to be sent to the SGSN, then +6152 one or more specific elements of SGSN CAMEL Subscription Info are sent in one dialogue. + +6153 When the SGSN receives a specific element of SGSN CAMEL Subscription Info, it shall overwrite the corresponding +6154 specific element of SGSN CAMEL Subscription Info (if any) which it has stored for that subscriber. + +6155 The specific elements of SGSN CAMEL Subscription Info which may be sent are: + +6156 - MO-SMS-CSI; + +6157 - MT-SMS-CSI; + +6158 - TDP-Criteria for MT-SMS-CSI; + +6159 - GPRS-CSI; + +6160 - MC-CSI. + +6161 This parameter is used only by the SGSN and if the VLR or IWF receives this parameter it shall ignore it. + +6162 This parameter shall not be used by the CSS. + +6163 Roaming Restricted In SGSN/MME Due To Unsupported Feature + +6164 The HSS/HLR may decide to include this parameter in the request if certain services or features are indicated as not +6165 supported by the SGSN/IWF. This parameter is used only by the SGSN and IWF and if the VLR receives this parameter +6166 it shall ignore it. + +6167 This parameter shall not be used by the CSS. + +6168 CS Allocation/Retention priority + +6169 The CS Allocation/Retention priority is used only for Circuit Switched (CS). This parameter specifies relative +6170 importance to compare with other bearers about allocation and retention of bearer. This parameter is used only by the +6171 VLR and if the SGSN or IWF receives this parameter it shall ignore it. + +6172 This parameter shall not be used by the CSS. + +6173 Offered CAMEL 4 CSIs + +6174 This parameter indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR or SGSN (see clause 7.6.3.36D). An +6175 IWF shall omit this parameter. + +6176 This parameter shall not be used by the CSS. + +6177 Subscribed Charging Characteristics + +6178 This parameter refers to the Subscribed Charging Characteristics as defined in 3GPP TS 32.251. + +6179 For a detailed description of the use of the parameter, see 3GPP TS 32.251. + +6180 This parameter is used only by the SGSN and IWF and if the VLR receives this parameter it shall ignore it. + +6181 This parameter shall not be used by the CSS. + +6182 Access Restriction Data + +6183 This parameter indicates the allowed RAT for the PLMN where the UE is attached according to subscription data. (see +6184 clause 7.6.3.97) + +6185 If the VLR/SGSN/MME supports the Access Restriction feature but does not receive the Access Restriction Data +6186 parameter from the HSS/HLR at location updating or restoration, the VLR/SGSN/MME shall assume that the +6187 subscriber's profile does not have any restrictions enabled. + +6188 For a detailed description of the use of the parameter, see 3GPP TS 23.012 [23] for the CS domain and 3GPP TS +6189 23.060[104], 3GPP TS 29.060 [105] clause 7.5.3 and 3GPP TS 29.274 [149] clause 7.3.6 for the PS domain. + +6190 This parameter shall not be used by the CSS. + +6191 Supported Features + +6192 This parameter shall be used by an IWF to forward feature support indications as received from the MME or SGSN via +6193 S6a/S6d. + +6194 This parameter shall not be used by the CSS. + +6195 CS-to-PS-SRVCC-Allowed-Indicator + +6196 This parameter indicates by its presence to the MSC Server enhanced for ICS (see 3GPP TS 23.292 [135]) that CS to +6197 PS SRVCC is subscribed. + +6198 This parameter is used by the VLR. + +6199 P-CSCF Restoration Request + +6200 This parameter indicates by its presence that the HSS requests to the SGSN or the MME (via the IWF) the execution of +6201 the HSS-based P-CSCF restoration procedures, as described in 3GPP TS 23.380 [150], clause 5.4. + +6202 This parameter shall not be used by the CSS. + +6203 Adjacent Access Restriction Data + +6204 This parameter indicates the allowed RAT in each one of the indicated PLMN IDs, according to subscription data. + +6205 This parameter shall not be used by the CSS. + +6206 IMSI-Group-Id List + +6207 A list of IMSI-Group-Id parameters each of which identifies an IMSI-Group the subscriber belongs to. + +6208 UE Usage Type + +6209 This parameter indicates the usage characteristics of the UE that enables the selection of a specific Dedicated Core +6210 Network . It shall not be sent to VLRs and shall not be sent to SGSNs that did not indicate support of the Dedicated +6211 Core Network functionality within GPRS-Location Update. When the Insert-Subscriber-Data operation is used within +6212 an Update-GPRS-Location Dialogue, the HLR shall include this parameter if the SGSN indicated support of the +6213 Dedicated Core Network functionality and a UE Usage Type is available in the subscription data of the user. Outside +6214 the Update-Gprs-Location Dialogue the HLR shall include this parameter towards the SGSN that supports the +6215 Dedicated Core Network functionality if the value changed. + +6216 User error + +6217 Only one of the following values is applicable: + +- 6218 - Unidentified subscriber; +- 6219 - Data missing; +- 6220 - Unexpected data value. + +#### 6221 8.8.1.4 Basic service information related to supplementary services + +6222 A number of parameters that relate to supplementary services can be qualified by a Basic Service Group (or a Basic Service Group List). This clause explains how this information is to be interpreted. Supplementary service parameters to which this clause is applicable only apply to the basic service groups described in this clause, and only those basic service groups shall be overwritten at the VLR or the SGSN. + +6226 The Basic Service Group (or Basic Service Group List) is optional. + +6227 If present the Basic Service Group (or each element of the Basic Service Group List) shall be one of: + +- 6228 - an Elementary Basic Service Group for which the supplementary service is applicable to at least one basic service in the group and for which the subscriber has a subscription to at least one basic service in the group; +- 6230 - the group "All Teleservices" provided that the service is applicable to at least one teleservice and that the subscriber has a subscription to at least one teleservice which is in the same Elementary Basic Service Group as a teleservice to which the service is applicable; +- 6233 - the group "All Bearer Services" provided that the service is applicable to at least one bearer service and that the subscriber has a subscription to at least one bearer service which is in the same Elementary Basic Service Group as a basic service to which the service is applicable. + +6236 If the Basic Service Group (or Basic Service Group List) is not present then the parameter shall apply to all Basic Service Groups. + +6238 If the basic service information is not a single Elementary Basic Service Group then the parameter shall be taken as applying individually to all the Elementary Basic Service Groups for which: + +- 6240 - the supplementary service is applicable to at least one basic service in the Basic Service Group; and +- 6241 - the subscriber has a subscription to at least one basic service in the Basic Service Group. + +6242 The VLR and the SGSN are not required to store supplementary services data for Basic Service Groups which are not supported at the VLR or the SGSN respectively. + +#### 6244 8.8.2 MAP-DELETE-SUBSCRIBER-DATA service + +##### 6245 8.8.2.1 Definition + +6246 This service is used by an HLR to remove certain subscriber data from a VLR or SGSN if the subscription of one or more supplementary services or basic services is withdrawn. Note that this service is not used in case of erasure or deactivation of supplementary services. + +6249 This service is also used by an HLR to remove GPRS subscription data from an SGSN. + +6250 This service is also used by an HSS via IWF to remove EPS subscription data from an MME. + +6251 This service is also used by a CSS to remove the CSG subscription data from an MME via IWF or a VLR/SGSN. + +6252 + +6253 It is a confirmed service and consists of the primitives shown in table 8.8/2. + +##### 6254 8.8.2.2 Service primitives + +**Table 8.8/2: MAP-DELETE-SUBSCRIBER-DATA** + +| Parameter name | Request | Indication | Response | Confirm | +|------------------------------------------|----------------|-------------------|-----------------|----------------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| Basic service List | C | C(=) | | | +| SS-Code List | C | C(=) | | | +| Roaming Restriction Due To | | | | | +| Unsupported Feature | C | C(=) | | | +| Camel Subscription Info Withdraw | C | C(=) | | | +| Specific CSI Withdraw | C | C(=) | | | +| Regional Subscription Data | C | C(=) | | | +| VBS Group Indication | C | C(=) | | | +| VGCS Group Indication | C | C(=) | | | +| GPRS Subscription Data Withdraw | C | C(=) | | | +| EPS Subscription Data Withdraw | C | C(=) | | | +| Roaming Restricted In SGSN/MME Due To | C | C(=) | | | +| Unsupported Feature | | | | | +| LSA Information Withdraw | C | C(=) | | | +| IST Information Withdraw | C | C(=) | | | +| Regional Subscription Response | | | C | C(=) | +| GMLC List Withdraw | C | C(=) | | | +| Subscribed Charging Characteristics | C | C(=) | | | +| Withdraw | | | | | +| CSG Information Deleted | C | C(=) | | | +| VPLMN CSG Information Deleted | C | C(=) | | | +| APN-OI-Replacement Withdraw | C | C(=) | | | +| STN-SR Withdraw | C | C(=) | | | +| Subscribed vSRVCC Withdraw | C | C(=) | | | +| Subscribed Periodic RAU-TAU Timer | C | C(=) | | | +| Withdraw | | | | | +| Subscribed Periodic LAU Timer Withdraw | C | C(=) | | | +| Additional MSISDN Withdraw | C | C(=) | | | +| CS-to-PS-SRVCC Withdraw | C | C(=) | | | +| User Plane Integrity Protection Withdraw | C | C(=) | | | +| DL-Buffering Suggested Packet Count | C | C(=) | | | +| Withdraw | | | | | +| UE-Usage-Type Withdraw | C | C(=) | | | +| Reset-IDs Withdraw | C | C(=) | | | +| IAB-Operation-Withdraw | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +6256 + +6257 **8.8.2.3 Parameter use** + +6258 All parameters are described in clause 7.6. The following clarifications are applicable: + +6259 Basic service List + +6260 A list of Extensible Basic service parameters (Extensible Basic service is defined in clause 7.6). It is used when one, +6261 several or all basic services are to be withdrawn from the subscriber. If the VLR or the SGSN receives a value for an +6262 Extensible Basic Service which it does not support, it shall ignore that value. This parameter is used by the VLR and by +6263 the SGSN; if the IWF receives this parameter it shall ignore it. + +6264 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6265 from the CSS. + +6266 SS-Code List + +6267 A list of SS-Code parameters (SS-Code is defined in clause 7.6). It is used when several or all supplementary services +6268 are to be withdrawn from the subscriber. + +6269 There are three possible options: + +6270 - deletion of basic service(s); + +6271 The parameter Basic service List is only included. + +6272 - deletion of supplementary service(s); + +6273 The parameter SS-Code List is only included. + +6274 - deletion of basic and supplementary services; + +6275 Both Basic service List and SS-Code List are included. + +6276 This parameter is used by the VLR and SGSN and IWF for Call Barring and LCS. Otherwise, this parameter is used +6277 only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it. + +6278 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6279 from the CSS. + +#### 6280 Roaming Restriction Due To Unsupported Feature + +6281 This parameter is used if Roaming Restriction Due To Unsupported Feature is deleted from the subscriber data. This +6282 may occur if unsupported features or services are removed from the subscriber data in the HLR. + +6283 If this parameter is sent the VLR shall check if the current Location Area is possibly allowed now. This parameter is +6284 used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it. + +6285 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6286 from the CSS. + +#### 6287 CAMEL Subscription Info Withdraw + +6288 This parameter is used to indicate that CAMEL Subscription Info shall be deleted from the VLR or from the SGSN. All +6289 CAMEL Subscription Info for the subscriber shall be deleted. This parameter is used by the VLR and by the SGSN. +6290 This parameter should not be sent in the same message as the Specific CSI Withdraw parameter; if the IWF receives +6291 this parameter it shall ignore it. + +6292 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6293 from the CSS. + +#### 6294 Specific CSI Withdraw + +6295 This parameter is used to indicate that one or more specific elements of CAMEL Subscription Info shall be deleted from +6296 the VLR or from the SGSN. + +6297 The specific elements of CAMEL Subscription Info which may be withdrawn are: + +6298 - O-CSI with TDP criteria for O-CSI; + +6299 - SS-CSI; + +6300 - TIF-CSI; + +6301 - D-CSI; + +6302 - VT-CSI with TDP criteria for VT-CSI; + +6303 - MO-SMS-CSI; + +6304 - MT-SMS-CSI with TDP-Criteria for MT-SMS-CSI; + +6305 - M-CSI; + +6306 - MG-CSI; + +6307 - GPRS-CSI. + +6308 This parameter is used by the VLR and by the SGSN; if the IWF receives this parameter it shall ignore it. It shall not be +6309 sent to VLRs that do not support CAMEL phase 3 or higher. This parameter should not be sent in the same message as +6310 the CAMEL Subscription Info Withdraw parameter. + +6311 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6312 from the CSS. + +#### 6313 Regional Subscription Identifier + +6314 Contains one single Zone Code (as defined in clause 7.6) and is used if all Zone Codes shall be deleted from the +6315 subscriber data. When all the Zone Codes are deleted, the VLR, the SGSN or the MME shall check for its location areas +6316 whether they are allowed or not. If the whole Network Node area is restricted, the VLR, the SGSN or the MME (via the +6317 IWF) will report it to HLR by returning the Regional Subscription Response "Network Node Area Restricted". + +6318 The binary coding of the Zone Code value received in a Delete Subscriber Data request shall not be checked by the +6319 VLR, the SGSN or the MME. + +6320 Note that support of this parameter is a network operator option and it shall not be sent to networks which do not +6321 support Regional Subscription. + +6322 If Regional Subscription is not supported by the VLR, the SGSN or the MME, the request for deletion of Zone Codes is +6323 refused by sending the Regional Subscription Response "Regional Subscription Not Supported" to the HLR. + +6324 If no Zone Codes are stored in the respective subscriber data record, the request for deleting all Zone Code information +6325 shall be ignored and no Regional Subscription Response shall be returned. This parameter is used by the VLR, the +6326 SGSN and the MME. + +6327 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6328 from the CSS. + +#### 6329 VBS Group Indication + +6330 Contains an indication (flag) which is used if all Group Ids shall be deleted from the subscriber data for the Voice +6331 Broadcast teleservice. + +6332 If VBS is not supported in the VLR or no Group Ids are stored for VBS in the respective subscriber record, the request +6333 for deletion of all Group Ids shall be ignored. This parameter is used only by the VLR and if the SGSN or the IWF +6334 receives this parameter it shall ignore it. + +6335 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6336 from the CSS. + +#### 6337 VGCS Group Indication + +6338 Contains an indication (flag) which is used if all Group Id's shall be deleted from the subscriber data for the Voice +6339 Group Call teleservice. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore +6340 it. + +6341 If VGCS is not supported in the VLR or no Group Ids are stored for VGCS in the respective subscriber record, the +6342 request for deletion of all Group Ids shall be ignored. + +6343 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6344 from the CSS. + +#### 6345 GPRS Subscription Data Withdraw + +6346 This parameter is used to indicate whether all GPRS Subscription Data for the subscriber shall be deleted or if only a +6347 subset of the stored GPRS Subscription Data for the subscriber shall be deleted. In the latter case only those PDP +6348 contexts whose identifiers are included in the subsequent identifier list will be deleted. This parameter is used only by +6349 the SGSN and if the VLR receives this parameter it shall ignore it. + +6350 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6351 from the CSS. + +#### 6352 EPS Subscription Data Withdraw + +6353 This parameter is used to indicate whether all EPS Subscription Data for the subscriber shall be deleted or if only a +6354 subset of the stored EPS Subscription Data for the subscriber shall be deleted. In the latter case, only those APN +6355 Configurations whose identifiers are included in the subsequent identifier list will be deleted. This parameter is used +6356 only by the SGSN and the MME and if the VLR receives this parameter it shall ignore it. + +6357 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6358 from the CSS. + +#### 6359 Roaming Restricted In SGSN/MME Due To Unsupported Feature + +6360 This parameter is used if Roaming Restricted In SGSN/MME Due To Unsupported Feature is deleted from the +6361 GPRS/EPS subscriber data. This may occur if unsupported features or services are removed from the GPRS/EPS +6362 subscriber data in the HLR. + +6363 If this parameter is sent the SGSN shall check if the current Location Area is possibly allowed now. This parameter is +6364 used only by the SGSN and the IWF and if the VLR receives this parameter it shall ignore it. + +6365 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6366 from the CSS. + +#### 6367 LSA Information Withdraw + +6368 This parameter is used to indicate whether all LSA Information for the subscriber shall be deleted or if only a subset of +6369 the stored LSA Information for the subscriber shall be deleted. In the latter case only the LSA data whose LSA +6370 identities are included in the subsequent LSA data list will be deleted. This parameter is used by the VLR and the +6371 SGSN. + +6372 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6373 from the CSS. + +#### 6374 IST Information Withdraw + +6375 This parameter is used to indicate that the IST condition has been removed for the subscriber. See 3GPP TS 43.035 for +6376 the use of this parameter. + +6377 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6378 from the CSS. + +#### 6379 Regional Subscription Response + +6380 If included in the Delete Subscriber Data response this parameter indicates one of: + +6381 - Network Node Area Restricted; + +6382 - Regional Subscription Not Supported. + +6383 This parameter is used by the VLR, the SGSN and the IWF. + +6384 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6385 from the CSS. + +#### 6386 GMLC List Withdraw + +6387 This parameter indicates that the subscriber's LCS GMLC List shall be deleted from the VLR or SGSN. This parameter +6388 is used by the VLR and the SGSN and IWF. + +6389 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6390 from the CSS. + +#### 6391 Subscribed Charging Characteristics Withdraw + +6392 This parameter indicates that the Subscribed Charging Characteristics shall be replaced with a local default value in the +6393 SGSN or in the MME (see 3GPP TS 32.251). + +6394 This parameter is used only by the SGSN and the IWF and if the VLR receives this parameter it shall ignore it. + +6395 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6396 from the CSS. + +6397 CSG Information Deleted + +6398 This parameter indicates that CSG Subscription Information received from the HLR/HSS shall be deleted from VLR, +6399 SGSN, or MME. + +6400 This parameter is used by the VLR, SGSN and the IWF. This parameter is not applicable for the CSS and the VLR or +6401 SGSN or IWF shall ignore this parameter if it is received from the CSS. + +6402 VPLMN CSG Information Deleted + +6403 This parameter indicates that CSG Subscription Information received from the CSS shall be deleted from VLR, SGSN. +6404 This parameter is used by the VLR and SGSN. This parameter is not applicable for the HLR/HSS and the VLR or +6405 SGSN or IWF shall ignore this parameter if it is received from the HLR/HSS. + +6406 APN-OI-Replacement Withdraw + +6407 This parameter indicates that APN-OI-Replacement shall be deleted from the SGSN or the MME. + +6408 This parameter is used by the SGSN and the IWF and if the VLR receives this parameter it shall ignore it. This +6409 parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from +6410 the CSS. + +6411 STN-SR Withdraw + +6412 This parameter indicates that STN-SR shall be deleted from the SGSN or the MME. + +6413 This parameter is used by the SGSN and the IWF and if the VLR receives this parameter it shall ignore it. This +6414 parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from +6415 the CSS. + +6416 Subscribed vSRVCC Withdraw + +6417 This parameter indicates that Subscribed vSRVCC shall be deleted from the MME. + +6418 This parameter is used by the MME and the IWF and if the SGSN or VLR receives this parameter it shall ignore it. + +6419 This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received +6420 from the CSS. + +6421 Subscribed Periodic RAU-TAU Timer Withdraw + +6422 This parameter indicates that Subscribed Periodic RAU-TAU Timer value shall be deleted from the SGSN or the MME. + +6423 This parameter is used by the SGSN and the IWF and if the VLR receives this parameter it shall ignore it. This + +6424 parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from +6425 the CSS. + +6426 Subscribed Periodic LAU Timer Withdraw + +6427 This parameter indicates that Subscribed Periodic LAU Timer value shall be deleted from the VLR. + +6428 This parameter is used by the VLR and if the MME or SGSN receives this parameter it shall ignore it. This parameter +6429 is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS. + +6430 Additional MSISDN Withdraw + +6431 This parameter indicates that Additional MSISDN shall be deleted from the SGSN or MME. + +6432 This parameter is used by the SGSN and the IWF. + +6433 CS-to-PS-SRVCC Withdraw + +6434 This parameter indicates by its presence that CS to PS SRVCC is no longer subscribed. + +6435 User Plane Integrity Protection Withdraw + +6436 This parameter indicates by its presence that User Plane Integrity Protection may no longer be required. + +6437 DL-Buffering Suggested Packet Count Withdraw + +6438 This parameter indicates by its presence that a suggested DL-Buffering Packet Count is no longer subscribed. + +6439 UE-Usage-Type Withdraw + +6440 This parameter indicates by its presence that a UE-Usage-Type is no longer subscribed. + +6441 This parameter is not applicable for VLRs. + +6442 The HLR shall include this parameter towards the SGSN or MME (via IWF) that supports the Dedicated Core Network + +6443 functionality if the subscription to a UE-Usage-Type is removed. + +6444 Reset-IDs Withdraw + +6445 This parameter indicates by its presence that Reset-IDs are no longer subscribed. + +6446 IAB-Operation-Withdraw + +6447 This parameter indicates by its presence that IAB operation is no longer authorized for the UE. + +6448 User error + +6449 Only one of the following values is applicable: + +6450 - Unidentified subscriber; + +6451 - Data missing; + +6452 - Unexpected data value. + +6453 **8.9 Identity management services** + +6454 **8.9.1 MAP-PROVIDE-IMSI service** + +6455 **8.9.1.1 Definition** + +6456 This service is used by a VLR in order to get, via the MSC, the IMSI of a subscriber (e.g. when a subscriber has + +6457 identified itself with a TMSI not allocated to any subscriber in the VLR). + +6458 It is a confirmed service and consists of the primitives shown in table 8.9/1. + +6459 **8.9.1.2 Service primitives** + +6460 **Table 8.9/1: MAP-PROVIDE-IMSI** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +6461 + +6462 **8.9.1.3 Parameter use** + +6463 All parameters are described in clause 7.6. The following clarifications are applicable: + +6464 IMSI + +6465 This parameter is received when the request is successfully carried out. It contains the requested IMSI. + +6466 User error + +6467 Only one of the following values is applicable: + +6468 - Absent subscriber. + +6469 **8.9.2 MAP-FORWARD-NEW-TMSI service** + +### 6470 8.9.2.1 Definition + +6471 This service is used by a VLR to allocate, via MSC, a new TMSI to a subscriber during an ongoing transaction (e.g. call +6472 set-up, location updating or supplementary services operation). + +6473 It is a confirmed service and consists of the primitives shown in table 8.9/2. + +### 6474 8.9.2.2 Service primitives + +6475 **Table 8.9/2: MAP-FORWARD-NEW-TMSI** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| TMSI | M | M(=) | | | +| Provider error | | | | O | + +6476 + +### 6477 8.9.2.3 Parameter use + +6478 The parameter TMSI is described in clause 7.6. + +## 6479 8.10 Fault recovery services + +### 6480 8.10.1 MAP\_RESET service + +#### 6481 8.10.1.1 Definition + +6482 This service is used by the HSS/HLR or CSS, after a restart, to indicate to a list of VLRs, SGSNs or MMEs (via IWF) +6483 that a failure occurred. + +6484 This service may also be used by the HSS/HLR as part of operation and maintenance actions e.g. to allow planned +6485 HLR/HSS outage without service interruption, or to update subscription data shared by multiple subscribers. + +6486 The MAP\_RESET service is a non-confirmed service using the service primitives defined in table 8.10/1. + +#### 6487 8.10.1.2 Service primitives + +6488 **Table 8.10/1: MAP\_RESET** + +| Parameter name | Request | Indication | +|-------------------------------|---------|------------| +| Invoke Id | M | M(=) | +| Sending Node
Number | M | M(=) | +| HLR Id LIST | U | C(=) | +| Reset-ID LIST | C | C(=) | +| Subscription Data | C | C(=) | +| Subscription Data
Deletion | C | C(=) | + +6489 + +#### 6490 8.10.1.3 Parameter definition and use + +##### 6491 Invoke Id + +6492 See definition in clause 7.6.1. + +##### 6493 SendingNode Number + +6494 For a restart of the HLR/HSS, this parameter shall contain the HLR number. See definition in clause 7.6.2. + +6495 For a restart of the CSS, this parameter shall contain the CSS number. See definition in clause 7.6.2. + +6496 HLR Id LIST + +6497 The HLR Id List is a list of HLR Ids. If the parameter is present in the indication, the VLR, the SGSN or the MME may +6498 base the retrieval of subscribers to be restored on their IMSI: the subscribers affected by the reset are those whose IMSI +6499 leading digits are equal to one of these numbers. If the parameter and the Reset-ID List is absent, subscribers to be +6500 restored are those for which the OriginatingEntityNumber received at location updating time matches the equivalent +6501 parameter of the Reset Indication. + +6502 This parameter shall only be applicable for a restart of the HLR/HSS. It shall not be present if Reset-ID LIST is present. + +6503 Reset-ID LIST + +6504 The Reset-ID LIST is a list of Reset-IDs. It shall not be present if Reset-IDs are not supported by the HLR/HSS and by +6505 the VLR or SGSN or MME (via IWF). If the parameter is present in the indication, the VLR, the SGSN or the MME +6506 may base the retrieval of affected subscribers (i.e. those impacted by the restoration or by the shared data update) on +6507 their subscribed Reset-IDs: The subscribers affected by the reset are those whose subscription contains at least one of +6508 these Reset-IDs. + +6509 Subscription Data + +6510 If the Reset Procedure is used to add/ modify subscription data shared by multiple subscribers, this Information Element +6511 shall contain the part of the subscription profile that either is to be added to the subscription profile stored in the VLR, +6512 MME or SGSN or combined MME/SGSN or is replacing a part of the subscription profiles of the impacted subscribers +6513 stored in the VLR, MME or SGSN. + +6514 Shall be absent if Subscription Data Deletion is present. + +6515 Shall be absent if Reset-ID LIST is absent + +6516 Subscription Data Deletion + +6517 If the Reset Procedure is used to delete subscription data shared by multiple subscribers, this Information Element shall +6518 contain the identifications of the part of the subscription profile that is to be deleted from the subscription profiles of the +6519 impacted subscribers stored in the VLR, MME or SGSN. + +6520 Shall be absent if Subscription Data is present. + +6521 Shall be absent if Reset-ID LIST is absent + +6522 + +## 6523 8.10.2 MAP\_FORWARD\_CHECK\_SS\_INDICATION service + +### 6524 8.10.2.1 Definition + +6525 This service may be used by an HLR as an implementation option, to indicate to a mobile subscriber that supplementary +6526 services parameters may have been altered, e.g. due to a restart. If received from the HLR, the VLR shall forward this +6527 indication to the MSC, which in turn forwards it to the MS. The HLR only sends this indication after successful +6528 completion of the subscriber data retrieval from HLR to VLR that ran embedded in a MAP\_UPDATE\_LOCATION +6529 procedure. + +6530 The MAP\_FORWARD\_CHECK\_SS\_INDICATION service is a non-confirmed service using the service primitives +6531 defined in table 8.10/2. + +### 6532 8.10.2.2 Service primitives + +6533 **Table 8.10/2: MAP\_FORWARD\_CHECK\_SS\_INDICATION** + +| Parameter name | Request | Indication | +|----------------|---------|------------| +| Invoke Id | M | M(=) | + +6534 + +### 6535 8.10.2.3 Parameter definition and use + +6536 Invoke Id + +6537 See definition in clause 7.6.1. + +## 6538 8.10.3 MAP\_RESTORE\_DATA service + +### 6539 8.10.3.1 Definition + +6540 This service is invoked by the VLR on receipt of a MAP\_PROVIDE\_ROAMING\_NUMBER indication for an + +6541 unknown IMSI, or for a known IMSI with the indicator "Subscriber Data Confirmed by HLR" set to "Not confirmed". + +6542 The service is used to update the LMSI in the HLR, if provided, and to request the HLR to send all data to the VLR that + +6543 are to be stored in the subscriber's IMSI record. + +6544 This service may be invoked by the VLR on receipt of a "MAP-MT-FORWARD-SHORT-MESSAGE" message for an + +6545 unknown IMSI, or for a known IMSI with the indicator "Subscriber Data Confirmed by HLR" set to "Not confirmed". + +6546 The service is used to update the LMSI in the HLR, if provided, and to request the HLR to send all data to the VLR that + +6547 are to be stored in the subscriber's IMSI record. + +6548 The HLR shall return the error "system failure" to the VLR if the subscriber is not registered on the VLR. + +6549 The MAP\_RESTORE\_DATA service is a confirmed service using the service primitives defined in table 8.10/3. + +### 6550 8.10.3.2 Service primitives + +6551 + +**Table 8.10/3: MAP\_RESTORE\_DATA** + +| Parameter name | Request | Indication | Response | Confirm | +|---------------------------------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| LMSI | U | C(=) | | | +| Supported CAMEL phases | C | C(=) | | | +| SoLSA Support Indicator | C | C(=) | | | +| IST Support Indicator | C | C(=) | | | +| Super-Charger Supported in Serving Network Entity | C | C(=) | | | +| Long FTN Supported | C | C(=) | | | +| Supported LCS Capability Sets | C | C(=) | | | +| Offered CAMEL 4 CSIs | C | C(=) | | | +| Restoration Indicator | U | C(=) | | | +| Supported RAT Types Indicator | U | C(=) | | | +| MTRF Supported | U | C(=) | | | +| MSISDN-less Operation Supported | C | C(=) | | | +| HLR number | | | C | C(=) | +| MS Not Reachable Flag | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +6552 + +### 6553 8.10.3.3 Parameter definitions and use + +6554 Invoke Id + +6555 See definition in clause 7.6.1. + +6556 IMSI + +6557 See definition in clause 7.6.2. + +6558 LMSI + +6559 See definition in clause 7.6.2. It is an operator option to provide the LMSI from the VLR; it is mandatory for the HLR +6560 to support the LMSI handling procedures. + +6561 Supported CAMEL Phases + +6562 This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from +6563 phase 1 is supported. Otherwise may be absent. + +6564 SoLSA Support Indicator + +6565 This parameter is used by the VLR to indicate to the HLR in the Restore Data indication that SoLSA is supported. If +6566 this parameter is not included in the Restore Data indication then the HLR shall not perform any specific error handling. + +6567 This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a +6568 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support +6569 indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted. + +6570 IST Support Indicator + +6571 This parameter is used to indicate to the HLR that the VMSC supports basic IST functionality, that is, the VMSC is able +6572 to terminate the Subscriber Call Activity that originated the IST Alert when it receives the IST alert response indicating +6573 that the call(s) shall be terminated. If this parameter is not included in the Restore Data indication and the Subscriber is +6574 marked as an IST Subscriber, then the HLR may limit the service for the subscriber (by inducing an Operator +6575 Determined barring of Outgoing calls), or allow service assuming the associated risk of not having the basic IST +6576 mechanism available. + +6577 This parameter can also indicate that the VMSC supports the IST Command service, including the ability to terminate +6578 all calls being carried for the identified subscriber by using the IMSI as a key. If this additional capability is not +6579 included in the Restore Data indication and the HLR supports the IST Command capability, then the HLR may limit the +6580 service for the subscriber (by inducing an Operator Determined barring of Outgoing calls), or allow service assuming +6581 the associated risk of not having the IST Command mechanism available. + +6582 Long FTN Supported + +6583 This parameter indicates that the VLR supports Long Forwarded-to Numbers. + +6584 Super-Charger Supported in Serving Network Entity + +6585 This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality and +6586 that subscriber data is required. + +6587 If this parameter is absent then the VLR does not support the Super-Charger functionality. + +6588 Supported LCS Capability Sets + +6589 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no +6590 capability set is marked as supported then the VLR does not support LCS at all. + +6591 If this parameter is absent then the VLR may support at most LCS capability set 1, that is LCS Release98 or Release99 +6592 version. + +6593 Offered CAMEL 4 CSIs + +6594 This parameter indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR (see clause 7.6.3.36D). + +6595 Restoration Indicator + +6596 This parameter indicates, if present, that the HLR shall send in the MAP-INSERT-SUBSCRIBER-DATA the MME +6597 Name if the subscriber is registered to EPS, or the SGSN Number if available and if the subscriber is registered to +6598 GPRS. The VLR may set this indicator if it supports Gs or SG interfaces. + +6599 Supported RAT Types Indicator + +6600 This parameter indicates, if present, which access technologies (e.g. GERAN and / or UTRAN) are served by the +6601 MSC/VLR (see clause 7.6.3) + +6602 MTRF Supported + +6603 See 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence. + +6604 MSISDN-less Operation Supported + +6605 See clause 3.6.1.5 of 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence. + +6606 HLR number + +6607 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful outcome of the service. + +6608 MS Not Reachable Flag + +6609 See definition in clause 7.6.8. This parameter shall be present in case of successful outcome of the service, if the "MS +6610 Not Reachable flag" was set in the HLR. + +6611 User error + +6612 In case of unsuccessful outcome of the service, an error cause shall be returned by the HLR. The following error causes +6613 defined in clause 7.6.1 may be used, depending on the nature of the fault: + +- 6614 - unknown subscriber; +- 6615 - system failure; +- 6616 - unexpected data value; +- 6617 - data missing. + +6618 Provider error + +6619 For definition of provider errors see clause 7.6.1. + +## 6620 8.11 Subscriber Information services + +### 6621 8.11.1 MAP-ANY-TIME-INTERROGATION service + +#### 6622 8.11.1.1 Definition + +6623 This service is used by the gsmSCF, to request information (e.g. subscriber state and location) from the HLR or the +6624 GMLC at any time. This service may also be used by the gsmSCF to request the Mobile Number Portability (MNP) +6625 information from the NPLR. + +6626 This service is also used by the Presence Network Agent to request information, (e.g. subscriber state and location) +6627 about the subscriber (associated with a presentity) from the HLR at any time (see 3GPP TS 23.141 [128]). + +6628 When this service is used to the HLR, the subscriber state, location, Time Zone, or T-ADS data may be requested. + +6629 When this service is used to the GMLC, only the location may be requested. + +6630 When this service is used to the NPLR, only the MNP information may be requested. + +6631 The MAP-ANY-TIME-INTERROGATION service is a confirmed service using the service primitives defined in +6632 table 8.11/1. + +#### 6633 8.11.1.2 Service primitives + +6634 **Table 8.11/1: Any\_Time\_Interrogation** + +| Parameter name | Request | Indication | Response | Confirm | +|------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| Requested Info | M | M(=) | | | +| Requested domain | C | C(=) | | | + +| | | | | | +|----------------------------------------------|---|------|---|------| +| MNP Requested Info | C | C(=) | | | +| gsmSCF-Address | M | M(=) | | | +| IMSI | C | C(=) | | | +| MSISDN | C | C(=) | | | +| Location Information | | | C | C(=) | +| Location Information for GPRS | | | C | C(=) | +| Location Information for EPS | | | C | C(=) | +| Subscriber State | | | C | C(=) | +| PS Subscriber State | | | C | C(=) | +| EPS Subscriber State | | | C | C(=) | +| IMEI | | | C | C(=) | +| MS Classmark 2 | | | C | C(=) | +| GPRS MS Class | | | C | C(=) | +| MNP info Result | | | C | C(=) | +| IMS Voice Over PS Sessions Support Indicator | | | C | C(=) | +| Last UE Activity Time | | | C | C(=) | +| Last RAT Type | | | C | C(=) | +| Time Zone | | | C | C(=) | +| Daylight Saving Time | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +6635 + +### 6636 8.11.1.3 Parameter definition and use + +6637 All parameters are described in clause 7.6. The use of these parameters and the requirements for their presence are +6638 specified in 3GPP TS 23.018 [97] and 3GPP TS 23.078 [98]. + +6639 The HLR or GMLC may be able to use the value of the parameter gsmSCF-address to screen a +6640 MAP\_Any\_Time\_Interrogation indication. + +6641 The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078 [98]. + +#### 6642 IMS Voice Over PS Sessions Support Indicator + +6643 This parameter indicates the most recent IMS-Voice-Over-PS-Sessions support (based on the Last UE Activity Time), +6644 as received from the serving nodes. This parameter shall be present if Requested Info indicates that T-ADS Data are +6645 requested. + +#### 6646 Last UE Activity Time + +6647 This parameter indicates the most recent available point in time of the UE's last radio contact, as received from the +6648 serving nodes. This value may not represent the absolute last instant of radio activity of the UE, when any of the serving +6649 nodes has not answered to the T-ADS query. This parameter may be present if requested Info indicates that T-ADS +6650 Data are requested. This value may not be available when all the serving nodes have indicated an homogeneous support +6651 or an homogeneous non support of IMS Voice Over PS Sessions, since in that case, the serving nodes do not need to be +6652 explicitly asked for T-ADS Data. + +#### 6653 Last RAT Type + +6654 This parameter indicates the most recent available RAT Type of the access (based on the Last UE Activity Time), as +6655 received from the serving nodes. This parameter shall be present if requested Info indicates that T-ADS Data are +6656 requested and the IMS Voice Over PS Sessions Support Indicator does not take the value "unknown". This value may +6657 not represent the absolute last RAT Type of the UE, when any of the serving nodes has not answered to the T-ADS +6658 query. This parameter may be present if requested Info indicates that T-ADS Data are requested. This value may not be +6659 available when all the serving nodes have indicated an homogeneous support or an homogeneous non support of IMS +6660 Voice Over PS Sessions, since in that case, the serving nodes do not need to be explicitly asked for T-ADS Data. + +#### 6661 Time Zone + +6662 This parameter indicates the Time Zone of the location in the visited network where the UE is attached, including any +6663 adjustment for summertime (daylight saving time). + +6664 Daylight Saving Time + +6665 This parameter indicates the Daylight Saving Time (in steps of 1 hour) used to adjust for summertime the time zone of +6666 the location where the UE is attached in the visited network. + +6667 User error + +6668 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +- 6669 - System Failure; +- 6670 - Any Time Interrogation Not Allowed; +- 6671 - Data Missing; +- 6672 - Unexpected Data Value; +- 6673 - Unknown Subscriber. + +6674 Provider error + +6675 These are defined in clause 7.6.1. + +## 6676 8.11.2 MAP-PROVIDE-SUBSCRIBER-INFO service + +### 6677 8.11.2.1 Definition + +6678 This service is used to request information (e.g. subscriber state and location) from the VLR, SGSN or MME (via an +6679 IWF) at any time. + +6680 The MAP-PROVIDE-SUBSCRIBER-INFO service is a confirmed service using the primitives defined in table 8.11/2. + +### 6681 8.11.2.2 Service primitives + +6682 **Table 8.11/2: Provide\_Subscriber\_Information** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------------------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| Requested Info | M | M(=) | | | +| IMSI | M | M(=) | | | +| LMSI | U | O | | | +| Call Priority | U | O | | | +| Location Information | | | C | C(=) | +| Location Information for GPRS | | | C | C(=) | +| Subscriber State | | | C | C(=) | +| PS Subscriber State | | | C | C(=) | +| IMEI | | | C | C(=) | +| MS Classmark 2 | | | C | C(=) | +| GPRS MS Class | | | C | C(=) | +| IMS Voice Over PS Sessions Support Indicator | | | C | C(=) | +| Last UE Activity Time | | | C | C(=) | +| Last RAT Type | | | C | C(=) | +| Location Information for EPS | | | C | C(=) | +| Time Zone | | | C | C(=) | +| Daylight Saving Time | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +6683 + +### 6684 8.11.2.3 Parameter definition and use + +6685 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are +6686 specified in 3GPP TS 23.018 [97] and 3GPP TS 23.078 [98]. + +#### 6687 Call Priority + +6688 This parameter indicates the eMLPP priority of the call (see 3GPP TS 24.067 [137]). This parameter should be present +6689 if the HLR supports this parameter and if the Call Priority was received in the +6690 MAP\_SEND\_ROUTING\_INFORMATION request. + +#### 6691 IMS Voice Over PS Sessions Support Indicator + +6692 This parameter indicates whether IMS Voice Over PS Sessions is supported at the UE's current Routing Area. This +6693 parameter shall be present if the UE's current Routing Area is known to the SGSN and the Requested Info indicates that +6694 T-ADS Data are requested; otherwise it shall be absent. + +#### 6695 Last UE Activity Time + +6696 This parameter indicates the point in time of the UE's last radio contact. This parameter shall be present if requested +6697 Info indicates that T-ADS Data are request. + +#### 6698 Last RAT Type + +6699 This parameter indicates the RAT Type of the access where the UE was present at the time of the last radio contact. +6700 This parameter shall be present if requested Info indicates that T-ADS Data are request. + +#### 6701 Time Zone + +6702 This parameter indicates the Time Zone of the location in the visited network where the UE is attached, including any +6703 adjustment for summertime (daylight saving time). + +#### 6704 Daylight Saving Time + +6705 This parameter indicates the Daylight Saving Time (in steps of 1 hour) used to adjust for summertime the time zone of +6706 the location where the UE is attached in the visited network. + +#### 6707 User error + +6708 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +6709 - Data Missing; + +6710 - Unexpected Data Value. + +6711 If the subscriber is not found on the VLR, SGSN or MME, this may be indicated to the requester with the "Unexpected +6712 Subscriber" value inside the Unexpected Data Value error + +#### 6713 Provider error + +6714 These are defined in clause 7.6.1. + +### 6715 8.11.3 MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION service + +#### 6716 8.11.3.1 Definition + +6717 This service is used by the gsmSCF, to request subscription information (e.g. call forwarding supplementary service +6718 data or CSI) from the HLR at any time. In an IP Multimedia Core Network, an IM-SSF can take on the role of a +6719 gsmSCF for this service. + +6720 + +6721 8.11.3.2 Service primitives + +6722 + +**Table 8.11/3: Any\_Time\_Subscription\_Interrogation** + +| Parameter name | Request | Indication | Response | Confirm | +|-----------------------------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| Requested Subscription Info | M | M(=) | | | +| GsmSCF-Address | M | M(=) | | | +| IMSI | C | C(=) | | | +| MSISDN | C | C(=) | | | +| Long FTN Supported | C | C(=) | | | +| Call Forwarding Data | | | C | C(=) | +| Call Barring Data | | | C | C(=) | +| ODB Info | | | C | C(=) | +| CAMEL Subscription Info | | | C | C(=) | +| Supported CAMEL phases in VLR | | | C | C(=) | +| Supported CAMEL phases in SGSN | | | C | C(=) | +| Offered CAMEL 4 CSIs in VLR | | | C | C(=) | +| Offered CAMEL 4 CSIs in SGSN | | | C | C(=) | +| MSISDN-BS-List | | | C | C(=) | +| CSG Subscription Data | | | C | C(=) | +| Call Hold Data | | | C | C(=) | +| Call Waiting Data | | | C | C(=) | +| Explicit Call Transfer Data | | | C | C(=) | +| Calling Line Identification Presentation Data | | | C | C(=) | +| Calling Line Identification Restriction Data | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +6723 + +6724 8.11.3.3 Parameter definition and use + +6725 All parameters are described in clause 7.6. + +6726 The HLR may be able to use the value of the parameter gsmSCF-address to screen a + +6727 MAP\_Any\_Time\_Subscription\_Interrogation indication. The gsmSCF-address shall contain the IM-SSF address when +6728 the IM-SSF takes the role of the gsmSCF. + +6729 + +6730 The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078 [98] and 3GPP TS +6731 23.278 [125]. + +6732 User error + +6733 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +- 6734 - Unexpected Data Value; +- 6735 - Unknown Subscriber; +- 6736 - BearerServiceNotProvisioned; +- 6737 - TeleserviceNotProvisioned; +- 6738 - CallBarred; +- 6739 - IllegalSS-Operation; +- 6740 - SS-NotAvailable; +- 6741 - InformationNotAvailable; +- 6742 - Any Time Subscription Interrogation Not Allowed; + +6743 - Data Missing. + +6744 Provider error + +6745 These are defined in clause 7.6.1. + +## 6746 8.11.4 MAP-ANY-TIME-MODIFICATION service + +### 6747 8.11.4.1 Definition + +6748 This service is used by the gsmSCF, to modify information of the HLR at any time. + +6749 This service is also used by the Presence Network Agent to activate or deactivate reporting of mobility management +6750 events (associated with a presentity) from the VLR or SGSN (see 3GPP TS 23.141 [128]). + +6751 This service is also used by a Service Related Entity (e.g. the IP-SM-GW) to activate a one-time subscription of UE- +6752 reachability in the MME (see 3GPP TS 23.204 [134]) and SGSN (see 3GPP TS 23.060 [104]). + +6753 This service is also used by external Short Message Gateway (IP-SM-GW) for updating the IP-SM-GW Number stored +6754 in the HLR, and for retrieving SC Address from the HLR. + +### 6755 8.11.4.2 Service primitives + +6756 **Table 8.11/4: Any\_Time\_Modification** + +| Parameter name | Request | Indication | Response | Confirm | +|-----------------------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| gsmSCF-Address | M | M(=) | | | +| Subscriber Identity | M | M(=) | | | +| Modification request for ODB data | C | C(=) | | | +| Modification request for SS information | C | C(=) | | | +| Modification request for CSI | C | C(=) | | | +| Modification request for CSG | C | C(=) | | | +| Long FTN Supported | C | C(=) | | | +| Modification request for IP-SM-GW data | C | C(=) | | | +| Activation request for UE-Reachability | C | C(=) | | | +| Ext Forwarding information-for-CSE | | | C | C(=) | +| Ext Call barring information-for-CSE | | | C | C(=) | +| ODB Info | | | C | C(=) | +| CAMEL subscription info | | | C | C(=) | +| Service Centre Address | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +6757 + +### 6758 8.11.4.3 Parameter definition and use + +6759 All parameters are described in clause 7.6. + +6760 The HLR may be able to use the value of the parameter gsmSCF-address to screen a MAP\_Any\_Time\_Modification +6761 indication. + +6762 The use of parameters other than described below and the requirements for their presence are specified in 3GPP TS +6763 23.078 [98] and 3GPP TS 23.278 [125]. + +#### 6764 gsmSCF-Address + +6765 This parameter indicates the address of the interrogating gsmSCF. The gsmSCF Address shall be in international E.164 +6766 format. If the service is used by IP-SM-GW, the parameter contains the address of the IP-SM-GW. See also 3GPP TS +6767 23.078 [98] and 3GPP TS 23.278 [125]. + +#### 6768 Modification request for CSG + +6769 This parameter is used by the gsmSCF to request notification of modification of CSG subscription data. + +6770 Modification request for IP-SM-GW data + +6771 This parameter is used by the external IP-SM-GW for updating the IP-SM-GW Number and IP-SM-GW Diameter + +6772 Address stored in the HLR. If this parameter is present then other modification requests shall not be present. + +6773 Activation request for UE Reachability + +6774 This parameter is used by the Service Related Entity (e.g. IP-SM-GW) to activate the one-time subscription for UE- + +6775 Reachability. If this parameter is present then other modification requests shall not be present. + +6776 Service Centre Address + +6777 See definition in clause 7.6.2. + +6778 User error + +6779 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +6780 - Any Time Modification Not Allowed; + +6781 - Data Missing; + +6782 - Unexpected Data Value; + +6783 - Unknown Subscriber; + +6784 - Bearer service not provisioned; + +6785 This error is returned only if not even a subset of the requested bearer service group has been subscribed to; + +6786 - Teleservice not provisioned; + +6787 This error is returned only if not even a subset of the requested teleservice group has been subscribed to; + +6788 - Call Barred; + +6789 - Illegal SS operation; + +6790 - SS error status; + +6791 - SS incompatibility; + +6792 - SS subscription violation; + +6793 - Information Not Available. + +6794 Provider error + +6795 These are defined in clause 7.6.1. + +## 6796 8.11.5 MAP-NOTE-SUBSCRIBER-DATA-MODIFIED service + +### 8.11.5.1 Definition + +This service is used by the HLR to inform the gsmSCF that subscriber data have been modified. In an IP Multimedia Core Network, an IM-SSF can take on the role of a gsmSCF for this service. + +This service is also used by the HLR to inform the Service Related Entity (e.g. IP-SM-GW) that the UE has become reachable (see 3GPP TS 23.204 [134]). + +### 8.11.5.2 Service primitives + +**Table 8.11/5: Note\_Subscriber\_Data\_Modified** + +| Parameter name | Request | Indication | Response | Confirm | +|--------------------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| MSISDN | M | M(=) | | | +| Ext Forwarding information-for-CSE | C | C(=) | | | +| Ext Call barring information-for-CSE | C | C(=) | | | +| ODB Info | C | C(=) | | | +| CAMEL subscription info | C | C(=) | | | +| CSG Subscription Data | C | C | | | +| CW info | C | C(=) | | | +| CH info | C | C(=) | | | +| CLIP Info | C | C(=) | | | +| CLIR Info | C | C(=) | | | +| ECT Info | C | C(=) | | | +| All Information Sent | C | C(=) | | | +| UE reachable | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +### 8.11.5.3 Parameter definition and use + +#### Invoke id + +See clause 7.6.1 for the use of this parameter. + +#### IMSI + +See clause 7.6.2 for the use of this parameter. + +#### MSISDN + +See clause 7.6.2 for the use of this parameter. In an IP Multimedia Core Network, if no MSISDN is available, the HLR shall populate this parameter with the dummy MSISDN value (see clause 3 of 3GPP TS 23.003 [17]). + +#### Ext Forwarding information-for-CSE + +See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98]. + +#### Ext Call barring information-for-CSE + +See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98]. + +#### ODB Info + +See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98]. + +#### CAMEL subscription info + +See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.278 [125]. + +#### CSG Subscription Data + +This parameter contains a list of CSG-Ids and the associated expiration dates (see 3GPP TS 22.011 [138]). The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98]. + +#### CW Info + +This parameter contains the status of the call waiting supplementary service. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98] + +#### CH Info + +This parameter contains the status of the call hold supplementary service. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98] + +#### ECT Info + +This parameter contains the status of the explicit call transfer supplementary service. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98] + +#### CLIP Info + +This parameter contains the status of the calling line identification presentation supplementary service. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98] + +#### CLIR Info + +This parameter contains the status of the calling line identification restriction supplementary service. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98] + +#### 6797 All Information Sent + +6798 This parameter is set when the HLR has sent all information to gsmSCF. + +#### 6799 UE Reachable + +6800 This parameter is used when the HLR indicates to the Service related entity (e.g. IP-SM-GW) that the UE is reachable +6801 again. + +#### User error + +This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +6802 - Data Missing; + +6803 - Unexpected Data Value; + +6804 - Unknown Subscriber. + +#### Provider error + +These are defined in clause 7.6.1. + +The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.278 [125]. + +--- + +## 6805 9 Operation and maintenance services + +### 6806 9.1 Subscriber tracing services + +#### 6807 9.1.1 MAP-ACTIVATE-TRACE-MODE service + +##### 6808 9.1.1.1 Definition + +6809 This service is used between the HLR and the VLR to activate subscriber tracing in the VLR. + +6810 Also this service is used between the HLR and the SGSN to activate subscriber tracing in the SGSN. + +6811 The MAP-ACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/1. + +### 6812 9.1.1.2 Service primitives + +6813 **Table 9.1/1: MAP-ACTIVATE-TRACE-MODE** + +| Parameter name | Request | Indication | Response | Confirm | +|-------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMSI | C | C(=) | | | +| Trace reference | M | M(=) | | | +| Trace type | M | M(=) | | | +| Trace reference 2 | C | C(=) | | | +| Trace depth list | C | C(=) | | | +| Trace NE type list | C | C(=) | | | +| Trace interface list | C | C(=) | | | +| Trace event list | C | C(=) | | | +| Trace support indicator | | | C | C(=) | +| OMC Id | U | C(=) | | | +| MDT-Configuration | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +6814 + +### 6815 9.1.1.3 Parameter use + +#### 6816 Invoke id + +6817 See definition in clause 7.6.1. + +#### 6818 IMSI + +6819 See definition in clause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation. + +#### 6820 Trace reference + +6821 See definition in clause 7.6.10. This parameter contains trace reference for GSM only tracing request. + +#### 6822 Trace type + +6823 See definition in clause 7.6.10. This parameter contains trace type for GSM only tracing request. + +#### 6824 OMC Id + +6825 See definition in clause 7.6.2. The use of this parameter is an operator option. + +#### 6826 Trace reference 2 + +6827 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. + +#### 6828 Trace depth list + +6829 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. + +#### 6830 Trace NE type list + +6831 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. + +#### 6832 Trace interface list + +6833 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. + +#### 6834 Trace event list + +6835 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. + +6836 Trace support indicator + +6837 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. + +6838 MDT-Configuration + +6839 See definition in clause 7.6.10. + +6840 User error + +6841 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: + +6842 - Unidentified Subscriber; + +6843 - Facility Not Supported; + +6844 - Tracing Buffer Full; + +6845 - System Failure; + +6846 - Unexpected Data Value; + +6847 - Data missing. + +6848 Provider error + +6849 For definition of provider errors see clause 7.6.1. + +## 6850 9.1.2 MAP-DEACTIVATE-TRACE-MODE service + +### 6851 9.1.2.1 Definition + +6852 This service is used between the VLR and the HLR for deactivating subscriber tracing in the VLR. + +6853 Also this service is used between the SGSN and the HLR for deactivating subscriber tracing in the SGSN. + +6854 The MAP-DEACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/2. + +### 6855 9.1.2.2 Service primitives + +6856 **Table 9.1/2: MAP-DEACTIVATE-TRACE-MODE** + +| Parameter name | Request | Indication | Response | Confirm | +|-------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMSI | C | C(=) | | | +| Trace reference | M | M(=) | | | +| Trace reference 2 | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +6857 + +### 6858 9.1.2.3 Parameter use + +6859 Invoke id + +6860 See definition in clause 7.6.1. + +6861 IMSI + +6862 See definition in clause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation. + +6863 Trace reference + +6864 See definition in clause 7.6.10. + +6865 Trace reference 2 + +6866 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. + +6867 User error + +6868 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: + +- 6869 - Unidentified Subscriber; +- 6870 - Facility Not Supported; +- 6871 - System Failure; +- 6872 - Unexpected Data Value; +- 6873 - Data missing. + +6874 Provider error + +6875 For definition of provider errors see clause 7.6.1. + +## 6876 9.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service + +### 6877 9.1.3.1 Definition + +6878 This service is used between the VLR and the MSC to activate the subscriber tracing in the MSC. + +6879 The MAP-TRACE-SUBSCRIBER-ACTIVITY service is a non-confirmed service using the primitives from table 9.1/3. + +### 6880 9.1.3.2 Service primitives + +6881 **Table 9.1/3: MAP-TRACE-SUBSCRIBER-ACTIVITY** + +| Parameter name | Request | Indication | +|-----------------|---------|------------| +| Invoke id | M | M(=) | +| IMSI | C | C(=) | +| Trace reference | M | M(=) | +| Trace type | M | M(=) | +| OMC Id | U | C(=) | + +6882 + +### 6883 9.1.3.3 Parameter use + +6884 Invoke id + +6885 See definition in clause 7.6.1. + +6886 IMSI + +6887 See definition in clause 7.6.2. The controlling MSC shall provide either the IMSI or the IMEI to the servicing MSC. + +6888 Trace reference + +6889 See definition in clause 7.6.10. + +6890 Trace type + +6891 See definition in clause 7.6.10. + +6892 OMC Id + +6893 See definition in clause 7.6.2. The use of this parameter is an operator option. + +## 9.2 Other operation and maintenance services + +### 9.2.1 MAP-SEND-IMSI service + +#### 9.2.1.1 Definition + +This service is used by a VLR in order to fetch the IMSI of a subscriber in case of some Operation & Maintenance procedure where subscriber data are needed in the Visited PLMN and MSISDN is the only subscriber's identity known. + +It is a confirmed service and consists of the primitives shown in table 9.2/1. + +#### 9.2.1.2 Service primitives + +**Table 9.2/1: MAP-SEND-IMSI** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| MSISDN | M | M(=) | | | +| IMSI | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +6902 + +#### 9.2.1.3 Parameter use + +All parameters are described in clause 7.6. The following clarifications are applicable. + +##### User error + +Only one of the following values is applicable: + +- Unknown subscriber; +- Unexpected data value; +- Data missing. + +--- + +## 10 Call handling services + +### 10.1 MAP\_SEND\_ROUTING\_INFORMATION service + +#### 10.1.1 Definition + +This service is used between the Gateway MSC and the HLR. The service is invoked by the Gateway MSC to perform the interrogation of the HLR in order to route a call towards the called MS. + +This is a confirmed service using the primitives listed in table 10.1/1. + +This service is also used between the GMSC and the NPLR and between the gsmSCF and the HLR. + +#### 10.1.2 Service primitives + +**Table 10.1/1: MAP\_SEND\_ROUTING\_INFORMATION parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| Interrogation Type | M | M(=) | | | +| GMSC or gsmSCF Address | M | M(=) | | | + +| Parameter name | Request | Indication | Response | Confirm | +|---------------------------------------|---------|------------|----------|---------| +| MSISDN | M | M(=) | C | C(=) | +| OR Interrogation | C | C(=) | | | +| OR Capability | C | C(=) | | | +| CUG Interlock | C | C(=) | C | C(=) | +| CUG Outgoing Access | C | C(=) | C | C(=) | +| Number of Forwarding | C | C(=) | | | +| Network Signal Info | C | C(=) | | | +| Supported CAMEL Phases | C | C(=) | C | C(=) | +| Suppress T-CSI | C | C(=) | | | +| Offered CAMEL 4 CSIs | C | C(=) | | | +| Suppression of Announcement | C | C(=) | | | +| Call Reference Number | C | C(=) | | | +| Forwarding Reason | C | C(=) | | | +| Basic Service Group | C | C(=) | | | +| Basic Service Group 2 | C | C(=) | | | +| Alerting Pattern | C | C(=) | | | +| CCBS Call | C | C(=) | | | +| Supported CCBS Phase | C | C(=) | | | +| Additional Signal Info | C | C(=) | | | +| IST Support Indicator | C | C(=) | | | +| Pre-paging supported | C | C(=) | | | +| Call Diversion Treatment Indicator | C | C(=) | | | +| Long FTN Supported | C | C(=) | | | +| Suppress VT-CSI | C | C(=) | | | +| Suppress Incoming Call Barring | C | C(=) | | | +| SuppressMTSS | C | C(=) | | | +| gsmSCF Initiated Call | C | C(=) | | | +| Network Signal Info 2 | C | C(=) | | | +| MT Roaming Retry Supported | U | C(=) | | | +| Call Priority | U | C(=) | | | +| IMSI | | | C | C(=) | +| MSRN | | | C | C(=) | +| Forwarding Data | | | C | C(=) | +| Forwarding Interrogation Required | | | C | C(=) | +| VMSC address | | | C | C(=) | +| ReleaseResourcesSupported | | | C | C(=) | +| GMSC Camel Subscription Info | | | C | C(=) | +| Location Information | | | C | C(=) | +| Subscriber State | | | C | C(=) | +| Basic Service Code | | | C | C(=) | +| CUG Subscription Flag | | | C | C(=) | +| North American Equal Access preferred | | | U | C(=) | +| Carrier Id | | | | | +| User error | | | C | C(=) | +| SS-List | | | U | C(=) | +| CCBS Target | | | C | C(=) | +| Keep CCBS Call Indicator | | | C | C(=) | +| IST Alert Timer | | | C | C(=) | +| Number Portability Status | | | U | C(=) | +| Supported CAMEL Phases in VMSC | | | C | | +| Offered CAMEL 4 CSIs in VMSC | | | C | C(=) | +| MSRN 2 | | | C | C(=) | +| Forwarding Data 2 | | | C | C(=) | +| SS-List 2 | | | C | C(=) | +| Basic Service Code 2 | | | C | C(=) | +| Allowed Services | | | C | C(=) | +| Unavailability Cause | | | C | C(=) | +| Provider error | | | | O | +| GSM Bearer Capability | | | U | C(=) | + +6919 + +### 6920 10.1.3 Parameter use + +6921 See clause 7.6 for a definition of the parameters used in addition to the following. Note that: + +- 6922 - a conditional parameter whose use is defined only in 3GPP TS 23.078 shall be absent if the sending entity does +6923 not support CAMEL; +- 6924 - a conditional parameter whose use is defined only in 3GPP TS 23.079 [99] shall be absent if the sending entity +6925 does not support optimal routeing; +- 6926 - a conditional parameter whose use is defined only in 3GPP TS 23.078 & 3GPP TS 23.079 [99] shall be absent if +6927 the sending entity supports neither CAMEL nor optimal routeing. + +6928 Interrogation Type + +6929 See 3GPP TS 23.079 [99] for the use of this parameter. + +6930 GMSC or gsmSCF address + +6931 The E.164 address of the GMSC or the gsmSCF. This parameter contains the gsmSCF address if the gsmSCF initiated +6932 call parameter is present, otherwise it is the GMSC address. + +6933 MSISDN + +6934 This is the Mobile Subscriber ISDN number assigned to the called subscriber. In the Request & Indication it is the +6935 number received by the GMSC in the ISUP IAM. If the call is to be forwarded and the HLR supports determination of +6936 the redirecting number, the HLR inserts the basic MSISDN in the Response. + +6937 See 3GPP TS 23.066 [108] for the use of this parameter and the conditions for its presence in the response. + +6938 OR Interrogation + +6939 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. + +6940 OR Capability + +6941 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. + +6942 CUG Interlock + +6943 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. + +6944 CUG Outgoing Access + +6945 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. + +6946 Number of Forwarding + +6947 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. + +6948 Network Signal Info + +6949 See 3GPP TS 23.018 [97] for the conditions for the presence of the components of this parameter. + +6950 Supported CAMEL Phases + +6951 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +6952 T-CSI Suppression + +6953 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +6954 Offered CAMEL 4 CSIs + +6955 This parameter indicates the CAMEL phase 4 CSIs offered in the GMSC/VLR (see clause 7.6.3.36D). + +6956 + +6957 Suppression Of Announcement + +6958 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +6959 Call Reference Number + +6960 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98], 3GPP TS 23.079 +6961 [99] and 3GPP TS 23.018 [97]. + +6962 Forwarding Reason + +6963 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. + +6964 Basic Service Group + +6965 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. + +6966 Basic Service Group 2 + +6967 See 3GPP TS 23.079[99] for the use of this parameter and the conditions for its presence. + +6968 Alerting Pattern + +6969 See 3GPP TS 23.018 [97] and 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence. + +6970 CCBS Call + +6971 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +6972 Supported CCBS Phase + +6973 This parameter indicates by its presence that CCBS is supported and the phase of CCBS which is supported. + +6974 Additional Signal Info + +6975 See 3GPP TS 23.081 [27] and 3GPP TS 23.088 [33] for the conditions for the presence of the components of this +6976 parameter. + +6977 IST Support Indicator + +6978 This parameter is used to indicate to the HLR that the GMSC supports basic IST functionality, that is, the GMSC is able +6979 to terminate the subscriber call activity that originated the IST Alert when it receives the IST Alert response indicating +6980 that the call(s) shall be terminated. If this parameter is not included in the Send Routing Information indication and the +6981 subscriber is marked as an IST subscriber, then the HLR may limit the service for the call (by barring the incoming call +6982 if it is not subject to forwarding, or suppressing Call Forwarding from the GMSC), or allow the call assuming the +6983 associated risk of not having the basic IST mechanism available. + +6984 This parameter can also indicate that the GMSC supports the IST Command, including the ability to terminate all calls +6985 being carried for the identified subscriber by using the IMSI as a key. If this additional capability is not included in the +6986 Send Routing Information indication and the subscriber is marked as an IST subscriber, then the HLR may limit the +6987 service for the subscriber (by barring the incoming calls if they are not subject to forwarding, or suppressing Call +6988 Forwarding from the GMSC), or allow the incoming calls assuming the associated risk of not having the IST Command +6989 mechanism available. + +6990 Pre-paging supported + +6991 See 3GPP TS 23.018 for the use of this parameter and the conditions for its presence. + +6992 Call Diversion Treatment Indicator + +6993 This parameter indicates whether or not call diversion is allowed. + +6994 Network Signal Info 2 + +6995 See 3GPP TS 23.172 [126] for the conditions for the presence of the components of this parameter. + +6996 MT Roaming Retry Supported + +6997 See 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence. + +6998 Call Priority + +6999 This parameter indicates the eMLPP priority of the call (see 3GPP TS 24.067 [137]). This parameter should be present +7000 if the GMSC supports the eMLPP feature and if the call is an eMLPP call. The eMLPP priority levels A and B shall be +7001 mapped to the Call Priority level 0. + +7002 IMSI + +7003 See 3GPP TS 23.018 [97] and 3GPP TS 23.066 [108] for the use of this parameter and the conditions for its presence. + +7004 MSRN + +7005 See 3GPP TS 23.018 [97], 3GPP TS 23.066 [108] and 3GPP TS 23.079 [99] for the use of this parameter and the +7006 conditions for its presence. If the NPLR returns only the MSISDN-number without Routeing Number to the GMSC, the +7007 MSISDN-number shall be returned as MSRN. + +7008 Forwarding Data + +7009 This parameter includes a number to define the forwarded-to destination, the forwarding reason and the forwarding +7010 options Notification to calling party and Redirecting presentation, and can include the forwarded-to subaddress. See +7011 3GPP TS 23.018 [97] and 3GPP TS 23.079 [99] for the conditions for the presence of its components. + +7012 Forwarding Interrogation Required + +7013 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. + +7014 Long FTN Supported + +7015 This parameter indicates that the GMSC supports Long Forwarded-to Numbers. + +7016 Suppress VT-CSI + +7017 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +7018 Suppress Incoming Call Barring + +7019 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +7020 gsmSCF Initiated Call + +7021 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +7022 SuppressMTSS + +7023 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +7024 VMSC address + +7025 See 3GPP TS 23.079 [99] and 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence. +7026 In addition this parameter shall be present if the ReleaseResourcesSupported parameter is present. + +7027 Release Resources Supported + +7028 This parameter indicates by its presence that the MAP\_RELEASE\_RESOURCES service is supported at the VMSC. It +7029 shall be present if so indicated by the VMSC with MAP\_PROVIDE\_ROAMING\_NUMBER confirm. + +7030 GMSC CAMEL Subscription Info + +7031 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +7032 Location Information + +7033 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +7034 Subscriber State + +7035 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +7036 CUG Subscription Flag + +7037 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +7038 North American Equal Access preferred Carrier Id + +7039 This parameter is returned to indicate the preferred carrier identity to be used to set-up the call (i.e. forwarding the call +7040 or establishing the roaming leg). + +7041 SS-List + +7042 This parameter includes SS-codes and will be returned as an operator option. The HLR shall not send PLMN-specific +7043 SS-codes across PLMN boundaries. However if the GMSC receives PLMN-specific SS-codes from a foreign PLMN's +7044 HLR the GMSC may ignore it. If the GMSC attempts to process the PLMN- specific SS- codes, this may lead to +7045 unpredictable behaviour but the GMSC shall continue call processing. + +7046 Basic Service Code + +7047 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +7048 If the CAMEL service is not involved, this parameter includes the basic service code and will be returned as an operator +7049 option. The HLR shall not send a PLMN-specific Basic Service Code across PLMN boundaries. However if the GMSC +7050 receives a PLMN-specific Basic Service Code from a foreign PLMN's HLR the GMSC may ignore it. If the GMSC +7051 attempts to process the PLMN specific Basic Service codes, this may lead to unpredictable behaviour but the GMSC +7052 shall continue call processing. + +7053 CCBS Target + +7054 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +7055 Keep CCBS Call Indicator + +7056 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +7057 IST Alert Timer + +7058 It includes the IST Alert timer value that must be used to inform the HLR about the call activities that the subscriber +7059 performs. This parameter is only sent to the GMSC in response to a Send Routing Information request which indicates +7060 the the GMSC supports IST. + +7061 Number Portability Status + +7062 This parameter indicates the number portability status of the subscriber. This parameter may be present if the sender of +7063 SRIack is NPLR. + +7064 Supported CAMEL Phases in VMSC + +7065 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. + +7066 Offered CAMEL 4 CSIs in VMSC + +7067 This parameter is defined in clause 7.6.3.36F. + +7068 MSRN 2 + +7069 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. + +7070 Forwarding Data 2 + +7071 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. + +7072 SS-List 2 + +7073 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. + +7074 Basic Service Code 2 + +7075 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. + +7076 Allowed Services + +7077 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. + +7078 Unavailability Cause + +7079 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. + +7080 User error + +7081 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +7082 - Unknown Subscriber; + +7083 The diagnostic for the Unknown Subscriber error may indicate "NPDB Mismatch". + +7084 - Number changed; + +7085 - Call Barred; + +7086 This error will indicate that either incoming calls are barred for this MS or that calls are barred due to Operator + +7087 Determined Barring (see 3GPP TS 22.041 [8] for a definition of this network feature); + +7088 - CUG Reject; + +7089 The value of this error cause will indicate the reason for CUG Reject; + +7090 - Bearer Service Not Provisioned; + +7091 - Teleservice Not Provisioned; + +7092 A subscription check has been performed and the call has not passed the check due to incompatibility with + +7093 regard to the requested service. Depending on the nature of the incompatibility, either of these messages will be + +7094 returned; + +7095 - Facility Not Supported; + +7096 - Absent Subscriber; + +7097 This indicates that the location of the MS is not known (either the station is not registered and there is no + +7098 location information available or the Provide Roaming Number procedure fails due to IMSI detached flag being + +7099 set), or the GMSC requested forwarding information with a forwarding reason of not reachable, and the call + +7100 forwarding on MS not reachable service is not active; this may also indicate that the MS has moved to a new + +7101 MSC/VLR and that MT Roaming Retry is requested (see 3GPP TS 23.018 [97]); + +7102 - Busy Subscriber; + +7103 This indicates that Call Forwarding on Busy was not active for the specified basic service group when the + +7104 GMSC requested forwarding information with a forwarding reason of busy; + +7105 The error may also indicate that the subscriber is busy due to an outstanding CCBS recall. In the error data it + +7106 may then be specified that CCBS is possible for the busy encountered call; + +7107 - No Subscriber Reply; + +7108 This indicates that Call Forwarding on No Reply was not active for the specified basic service group when the + +7109 GMSC requested forwarding information with a forwarding reason of no reply; + +7110 - OR Not Allowed; + +7111 This indicates that the HLR is not prepared to accept an OR interrogation from the GMSC, or that calls to the + +7112 specified subscriber are not allowed to be optimally routed; + +7113 - Forwarding Violation; + +7114 - System Failure; + +7115 - Data Missing; + +7116 - Unexpected Data Value. + +7117 See clause 7.6.1.4 for a definition of these errors. + +7118 Provider error + +7119 These are defined in clause 7.6. + +7120 GSM Bearer Capability + +7121 This information is passed according to the rules specified in 3GPP TS 29.007 [56]. There may be two GSM Bearer +7122 Capabilities supplied. + +7123 + +## 7124 10.2 MAP\_PROVIDE\_ROAMING\_NUMBER service + +### 7125 10.2.1 Definition + +7126 This service is used between the HLR and VLR. The service is invoked by the HLR to request a VLR to send back a +7127 roaming number to enable the HLR to instruct the GMSC to route an incoming call to the called MS. + +7128 This service is also used between old VLR and new VLR during the MT Roaming Forwarding procedure. The service is +7129 invoked by the old VLR to request a roaming number from the new VLR to be able to route an incoming call to the +7130 called UE. + +7131 This is a confirmed service which uses the primitives described in table 10.2/1. + +### 7132 10.2.2 Service primitives + +7133 + +**Table 10.2/1: MAP\_PROVIDE\_ROAMING\_NUMBER parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------------------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| MSC Number | M | M(=) | | | +| MSISDN | U | C(=) | | | +| LMSI | C | C(=) | | | +| GSM Bearer Capability | C | C(=) | | | +| Network Signal Info | C | C(=) | | | +| Suppression Of Announcement | C | C(=) | | | +| Call Reference Number | C | C(=) | | | +| GMSC Address | C | C(=) | | | +| OR Interrogation | C | C(=) | | | +| OR Not Supported in GMSC | C | C(=) | | | +| Alerting Pattern | C | C(=) | | | +| CCBS Call | C | C(=) | | | +| Supported CAMEL Phases in interrogating node | C | C(=) | | | +| Additional Signal Info | C | C(=) | | | +| Pre-paging supported | C | C(=) | | | +| Long FTN Supported | C | C(=) | | | +| Suppress VT-CSI | C | C(=) | | | +| Offered CAMEL 4 CSIs in interrogating node | C | C(=) | | | +| MT Roaming Retry Supported | U | C(=) | | | +| Paging Area | U | C(=) | | | +| Call Priority | U | C(=) | | | +| MTRF Indicator | U | C(=) | | | +| Old MSC Number | U | C(=) | | | +| Last used LTE PLMN ID | U | C(=) | | | +| Roaming Number | | | C | C(=) | +| VMSC address | | | U | C(=) | +| ReleaseResourcesSupported | | | U | C(=) | +| User error | | | C | C(=) | + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Provider error | | | | O | + +7134 + +### 7135 10.2.3 Parameter use + +7136 See clause 7.6 for a definition of the parameters used, in addition to the following. Note that: + +- 7137 - a conditional parameter whose use is defined only in 3GPP TS 23.078 [98] shall be absent if the sending entity +- 7138 does not support CAMEL; +- 7139 - a conditional parameter whose use is defined only in 3GPP TS 23.079 [99] shall be absent if the sending entity +- 7140 does not support optimal routeing; +- 7141 - a conditional parameter whose use is defined only in 3GPP TS 23.078 [98] & 3GPP TS 23.079 [99] shall be +- 7142 absent if the sending entity supports neither CAMEL nor optimal routeing. + +#### 7143 IMSI + +7144 This is the IMSI of the called Subscriber. + +#### 7145 MSC Number + +7146 This is the ISDN number assigned to the MSC currently serving the MS. When the service is used between HLR and + +7147 VLR, the MSC number will have been stored in the HLR as provided at location updating. When used between old + +7148 VLR and new VLR during an MT Roaming Forwarding procedure, the MSC number will have been provided at + +7149 location cancelling or within Send Identification. + +#### 7150 MSISDN + +7151 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. + +#### 7152 LMSI + +7153 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. In addition, for the mobile + +7154 terminating roaming forwarding procedure between the old VLR and the new VLR, this parameter shall be present if + +7155 the MTRF Indicator is present and the old VLR has received the new LMSI in Cancel Location from the HLR or in + +7156 Send Identification from the new VLR. + +#### 7157 GSM Bearer Capability + +7158 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. + +7159 This information is passed according to the rules specified in TS 3GPP TS 29.007 [56]. + +7160 There may be two GSM Bearer Capabilities supplied. + +#### 7161 Network Signal Info + +7162 See 3GPP TS 23.018 [97] for the conditions for the presence of the components of this parameter. + +#### 7163 Suppression Of Announcement + +7164 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078 [98]. + +#### 7165 Call Reference Number + +7166 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98], 3GPP TS 23.079 + +7167 [99] and 3GPP TS 23.018 [97]. + +#### 7168 GMSC Address + +7169 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98], 3GPP TS 23.079 + +7170 [99] and 3GPP TS 23.018 [97]. + +#### 7171 OR Interrogation + +7172 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. + +7173 OR Not Supported in GMSC + +7174 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. + +7175 Supported CAMEL Phases in interrogating node + +7176 This parameter is defined in clause 7.6.3.36I.Alerting Pattern + +7177 See 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence. + +7178 CCBS Call + +7179 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +7180 Additional Signal Info + +7181 See 3GPP TS 23.081 [27] for the conditions for the presence of the components of this parameter. + +7182 Pre-paging supported + +7183 See 3GPP TS 23.018 for the use of this parameter and the conditions for its presence. This information element is not +7184 applicable for MTRF, and shall be ignored if received while the MTRF Indicator is present. + +7185 Long FTN supported + +7186 See 3GPP TS 23.082 for the use of this parameter and the conditions for its presence. + +7187 Suppress VT-CSI + +7188 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. + +7189 Offered CAMEL 4 CSIs in interrogating node + +7190 This parameter is defined in clause 7.6.3.36E. + +7191 MT Roaming Retry Supported + +7192 See 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence. +7193 This information element is not applicable for MTRF, and shall be ignored if received while the MTRF Indicator is +7194 present. + +7195 Paging Area + +7196 See 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence. +7197 This information element is not applicable for MTRF, and shall be ignored if received while the MTRF Indicator is +7198 present. + +7199 Call Priority + +7200 This parameter indicates the eMLPP priority of the call (see 3GPP TS 24.067 [137]). This parameter should be present +7201 if the HLR supports this parameter and if the Call Priority was received in the +7202 MAP\_SEND\_ROUTING\_INFORMATION request. + +7203 MTRF Indicator + +7204 This indicator indicates by its presence that the service is used between old VLR and new VLR during an MT Roaming +7205 Forwarding procedure. See 3GPP TS 23.018 [97]. + +7206 Old MSC Number + +7207 This parameter refers to the E.164 address of the old MSC. The use of this parameter is specified in 3GPP TS 23.018 +7208 [97]. This information element is applicable only if the MTRF Indicator is set. + +7209 Last used LTE PLMN ID + +7210 See 3GPP TS 23.272 [143] for the use of this parameter and the conditions for its presence. This information element is +7211 applicable only if the MTRF Indicator is set. + +7212 Roaming Number + +7213 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. + +7214 VMSC address + +7215 See 3GPP TS 23.079 [99], 3GPP TS 23.078 [98] and 3GPP TS 23.018 [97] for the use of this parameter and the +7216 conditions for its presence. This parameter shall be present during the Mobile Terminating Roaming Forwarding Call +7217 during Retrieval of Routeing Information procedure if an MSRN is allocated by the new MSC/VLR. + +7218 ReleaseResourcesSupported + +7219 This parameter indicates by its presence that the MAP\_RELEASE\_RESOURCES service is supported at the VMSC. + +7220 User error + +7221 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +7222 - Absent Subscriber; + +7223 This error will be returned if the IMSI detach flag is set. + +7224 - No Roaming Number Available; + +7225 - OR Not Allowed; + +7226 This indicates that the MAP\_PROVIDE\_ROAMING\_NUMBER indication included the OR interrogation +7227 indicator, but the VLR does not support optimal routeing. + +7228 - Facility Not Supported; + +7229 - System Failure; + +7230 - Data Missing; + +7231 - Unexpected Data Value. + +7232 See clause 7.6 for a definition of these reasons. + +7233 Provider error + +7234 These are defined in clause 7.6. + +## 7235 10.3 MAP\_RESUME\_CALL\_HANDLING service + +### 7236 10.3.1 Definition + +7237 This service is used between the terminating VMSC and the GMSC. The service is invoked by the terminating VMSC +7238 to request the GMSC to resume handling the call and forward it to the specified destination. + +7239 This is a confirmed service which uses the Primitives listed in table 10.3/1. + +### 7240 10.3.2 Service primitives + +7241 **Table 10.3/1: MAP\_RESUME\_CALL\_HANDLING parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|-----------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| Call Reference Number | C | C(=) | | | +| Basic Service Group | C | C(=) | | | +| Basic Service Group 2 | C | C(=) | | | + +| | | | | | +|----------------------|---|------|---|------| +| IMSI | C | C(=) | | | +| Forwarding Data | C | C(=) | | | +| CUG Interlock | C | C(=) | | | +| CUG Outgoing Access | C | C(=) | | | +| O-CSI | C | C(=) | | | +| D-CSI | C | C(=) | | | +| CCBS Target | C | C(=) | | | +| UU Data | C | C(=) | | | +| UUS CF Interaction | C | C(=) | | | +| All Information Sent | C | C(=) | | | +| MSISDN | C | C(=) | | | +| MT Roaming Retry | U | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7242 + +### 7243 10.3.3 Parameter use + +7244 Information received in subsequent segment of a segmented dialogue shall not overwrite information received in an +7245 earlier segment. + +7246 See clause 7.6 for a definition of the parameters used, in addition to the following. + +#### 7247 Call Reference Number + +7248 See 3GPP TS 23.079 [99] for the use of this parameter. This parameter shall be present in the first segment of the +7249 dialogue. + +#### 7250 Basic Service Group + +7251 See 3GPP TS 23.079 [99] for the use of this parameter. This parameter shall be present in the first segment of the +7252 dialogue. + +#### 7253 Basic Service Group 2 + +7254 See 3GPP TS 23.079[99] for the use of this parameter. If this parameter is present, it shall be in the first segment of the +7255 dialogue. + +#### 7256 IMSI + +7257 This is the IMSI of the forwarding Subscriber. This parameter shall be present in the first segment of the dialogue. + +#### 7258 Forwarding Data + +7259 This parameter includes a number to define the forwarded-to destination, the forwarding reason and the forwarding +7260 options Notification to calling party and Redirecting presentation, and can include the forwarded-to subaddress. See +7261 3GPP TS 23.079 [99] for the conditions for the presence of its components. This parameter shall be present in a first +7262 segment of the dialogue. + +#### 7263 CUG Interlock + +7264 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. + +#### 7265 CUG Outgoing Access + +7266 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. + +#### 7267 O-CSI + +7268 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. + +7269 For CAMEL phases 1 & 2, the O-CSI shall contain only one set of O-BCSM TDP data. + +#### 7270 D-CSI + +7271 The Dialled Services-CSI. + +7272 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. + +7273 CCBS Target + +7274 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +7275 UU Data + +7276 See 3GPP TS 23.087 for the use of this parameter and the conditions for its presence. + +7277 UUS CF Interaction + +7278 See 3GPP TS 23.087 for the use of this parameter and the conditions for its presence. + +7279 All Information Sent + +7280 This parameter is set when the VMSC has sent all information to GMSC. + +7281 MT Roaming Retry + +7282 See 3GPP TS 23.018 [97], 3GPP TS 23.012 [23] and 3GPP TS 23.079 [99] for the use of this parameter and the +7283 conditions for its presence. When this parameter is present, only the Call Reference Number and All Information Sent +7284 IEs shall be present; the other IEs shall be ignored by the GMSC if received. + +7285 MSISDN + +7286 This parameter is the basic MSISDN of the forwarding subscriber. It shall be present if the VMSC supports +7287 determination of the redirecting number. + +7288 User error + +7289 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +7290 - Optimal Routeing not allowed; + +7291 - Forwarding failed; + +7292 - Unexpected Data Value; + +7293 - Data Missing. + +7294 Provider error + +7295 These are defined in clause 7.6. + +## 7296 10.4 MAP\_PREPARE\_GROUP\_CALL service + +### 7297 10.4.1 Definition + +7298 This service is used by the Anchor\_MSC to inform the Relay\_MSC about a group call set-up. + +7299 The MAP\_PREPARE\_GROUP\_CALL service is a confirmed service using the service primitives given in table 10.4/1. + +### 7300 10.4.2 Service primitives + +7301 **Table 10.4/1: MAP\_PREPARE\_GROUP\_CALL service** + +| Parameter name | Request | Indication | Response | Confirm | +|------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| Teleservice | M | M(=) | | | +| ASCI Call Reference | M | M(=) | | | +| Ciphering Algorithm | M | M(=) | | | +| Group Key Number VK-Id | C | C(=) | | | +| VSTK Key | C | C(=) | | | + +| | | | | | +|--------------------------|---|------|---|------| +| VSTK-RAND | C | C(=) | | | +| Priority | C | C(=) | | | +| CODEC-Information | M | M(=) | | | +| Uplink Free Indicator | M | M(=) | | | +| Talker Channel Parameter | C | C(=) | | | +| Uplink Reply Indicator | C | C(=) | | | +| Group Call Number | | | M | M(=) | +| User Error | | | C | C(=) | +| Provider Error | | | | O | + +7302 + +### 7303 10.4.3 Parameter definitions and use + +#### 7304 Invoke Id + +7305 See definition in clause 7.6.1. + +#### 7306 Teleservice + +7307 Voice Broadcast Service or Voice Group Call Service. + +#### 7308 ASCI Call Reference + +7309 Broadcast call reference or group call reference. This item is used to access the VBS-GCR or VGCS-GCR within the +7310 Relay\_MSC. + +#### 7311 Ciphering Algorithm + +7312 The ciphering algorithm to be used for the group call. + +#### 7313 Group Key Number VK-Id + +7314 This Group Key Number has to be broadcast and is used by the mobile station to derive the key for ciphering on the +7315 radio interface (see 3GPP TS 43.020 [24]). Values 2 to 15 are reserved for future use. + +7316 Shall be present if the ciphering applies. + +#### 7317 VSTK + +7318 The VGCS/VBS Short Term Key is used to derive the key for ciphering on the radio interface (see 3GPP TS 43.020 +7319 [24]). + +7320 Shall be present if the ciphering applies. + +#### 7321 VSTK-RAND + +7322 This random number has to be broadcast and is used by the mobile station to derive the group key for ciphering on the +7323 radio interface (see 3GPP TS 43.020 [24]). + +7324 Shall be present if the ciphering applies. + +#### 7325 Priority + +7326 Default priority level related to the call if eMLPP applies. + +#### 7327 CODEC-Information + +7328 Information on the codecs allowed for this call. + +#### 7329 Uplink Free Indicator + +7330 A flag indicating whether the call is initiated from a dispatcher. + +#### 7331 Talker Channel Parameter + +7332 A flag indicating by its presence that a dedicated channel shall be established and maintained for the talking service +7333 subscriber. + +7334 Uplink Reply Indicator + +7335 A flag indicating by its presence that the uplink reply procedure is applicable for the voice group call or voice broadcast +7336 call. + +7337 Group Call Number + +7338 This temporary allocated E.164 number is used for routing the call from the Anchor MSC to the Relay MSC. + +7339 User Error + +7340 For definition of this parameter see clause 7.6.1 The following errors defined in clause 7.6.1 may be used, depending on +7341 the nature of the fault: + +- 7342 - No Group Call Number available; +- 7343 - System Failure; +- 7344 - Unexpected Data Value. + +7345 Provider Error + +7346 See definition of provider error in clause 7.6.1. + +## 7347 10.5 MAP\_PROCESS\_GROUP CALL\_SIGNALLING service + +### 7348 10.5.1 Definitions + +7349 This service is used between Relay MSC and Anchor MSC for transmission of Group Call notifications. + +7350 The MAP\_PROCESS\_GROUP\_CALL\_SIGNALLING service is a non-confirmed service using the service primitives +7351 given in table 10.5/1. + +### 7352 10.5.2 Service primitives + +7353 **Table 10.5/1: MAP\_PROCESS\_GROUP\_CALL\_SIGNALLING service** + +| Parameter name | Request | Indication | +|--------------------------------------|---------|------------| +| Invoke Id | M | M(=) | +| Uplink Request | C | C(=) | +| Uplink Release Indication | C | C(=) | +| AN-APDU | C | C(=) | +| Release Group Call | C | C(=) | +| Talker Priority | C | C(=) | +| Additional Info | C | C(=) | +| Emergency Mode Reset
Command Flag | C | C(=) | + +7354 + +### 7355 10.5.3 Parameter definitions and use + +7356 Invoke Id + +7357 See definition in clause 7.6.1 + +7358 Uplink Request + +7359 This information element indicates to the anchor MSC that a service subscriber roaming in the relay MSC area requests +7360 access to the uplink. + +7361 Uplink Release Indication + +7362 This information element if included by the Relay MSC indicates to the Anchor MSC that the uplink has become free. + +7363 AN-APDU + +7364 This parameter contains the Notification Data message as defined in 3GPP TS 48.008 [49]. + +7365 Release Group Call + +7366 This information element if included by the Relay MSC indicates to the Anchor MSC that the service subscriber who +7367 has initiated the call and who currently has access to the uplink terminates the call. + +7368 Talker Priority + +7369 For the definition and use of this parameter see 3GPP TS 43.068 [100] + +7370 Additional Info + +7371 For the definition and use of this parameter see 3GPP TS 43.068 [100] + +7372 Emergency Mode Reset Command Flag + +7373 For the definition and use of this parameter see 3GPP TS 43.068 [100] + +## 7374 10.6 MAP\_FORWARD\_GROUP\_CALL\_SIGNALLING service + +### 7375 10.6.1 Definitions + +7376 This service is used between Anchor MSC and Relay MSC for transmission of Group Call notifications. + +7377 The MAP\_FORWARD\_GROUP\_CALL\_SIGNALLING service is a non-confirmed service using the service +7378 primitives given in table 10.6/1. + +### 7379 10.6.2 Service primitives + +7380 **Table 10.6/1: MAP\_FORWARD\_GROUP\_CALL\_SIGNALLING service** + +| Parameter name | Request | Indication | +|-----------------------------------|---------|------------| +| Invoke Id | M | M(=) | +| IMSI | C | C(=) | +| Uplink Request Acknowledgement | C | C(=) | +| Uplink Release Indication | C | C(=) | +| Uplink Reject Command | C | C(=) | +| Uplink Seized Command | C | C(=) | +| Uplink Release Command | C | C(=) | +| AN-APDU | C | C(=) | +| State Attributes | C | C(=) | +| Talker Priority | C | C(=) | +| Additional Info | C | C(=) | +| Emergency Mode Reset Command Flag | C | C(=) | +| SM RP UI | C | C(=) | + +7381 + +### 7382 10.6.3 Parameter definitions and use + +7383 IMSI + +7384 Identity of the service subscriber who has established the call and who is allowed to terminate the call. + +7385 Invoke Id + +7386 See definition in clause 7.6.1. + +7387 Uplink Request Acknowledgement + +7388 This information element is used for positive acknowledgement of an uplink request. + +7389 Uplink Release Indication + +7390 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink has become free. + +7391 Uplink Reject Command + +7392 This information element is used for negative acknowledgement of an uplink request. + +7393 Uplink Seized Command + +7394 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink is no longer free. + +7395 Uplink Release Command + +7396 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink which is granted +7397 to a MS in the relay MSC area shall be released. + +7398 AN-APDU + +7399 This parameter contains the Notification Data message as defined in 3GPP TS 48.008 [49] + +7400 State Attributes + +7401 This information element is used to allow service logic running in an Anchor MSC to mute a VGCS talker even when +7402 the talker is served on a Relay MSC. The IE is used to build a GCC message that provides a mechanism to induce the +7403 VGCS talker terminal to mute/unmute the downlink at the Anchor MSC, as defined in 3GPP TS 44.068. + +7404 Talker Priority + +7405 For the definition and use of this parameter see 3GPP TS 43.068 [100] + +7406 Additional Info + +7407 For the definition and use of this parameter see 3GPP TS 43.068 [100] + +7408 Emergency Mode Reset Command Flag + +7409 For the definition and use of this parameter see 3GPP TS 43.068 [100] + +7410 SM RP UI + +7411 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted +7412 in this parameter. + +7413 + +## 7414 10.7 MAP\_SEND\_GROUP\_CALL\_END\_SIGNAL service + +### 7415 10.7.1 Definitions + +7416 This service is used between the Relay MSC and the Anchor MSC. When the VGCS/ VBS calling service subscriber is +7417 in the Relay MSC area the MAP\_SEND\_GROUP\_CALL\_END\_SIGNAL indicates that at least the downlink channel +7418 in the originating cell is established. For all other VGCS/ VBS call set-up scenarios (i.e. calling service subscriber in +7419 Anchor MSC area, calling service subscriber in other Relay MSC area, dispatcher originated call) the +7420 MAP\_SEND\_GROUP\_CALL\_END\_SIGNAL indicates that at least the downlink channel in any one cell within the +7421 VGCS/ VBS call area in the Relay MSC is established. The response is used by the Anchor MSC to inform the Relay +7422 MSC that all resources for the call can be released in the Relay MSC because the call has been released in the Anchor +7423 MSC. + +7424 The MAP\_SEND\_GROUP\_CALL\_END\_SIGNAL service is a confirmed service using the service primitives given in +7425 table 10.7/1. + +## 10.7.2 Service primitives + +Table 10.7/1: MAP\_SEND\_GROUP\_CALL\_END\_SIGNAL service + +| Parameter name | Request | Indication | Response | Confirm | +|-----------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | C | C(=) | | | +| Talker Priority | C | C(=) | | | +| Additional Info | C | C(=) | | | +| Provider Error | | | | O | + +7428 + +## 10.7.3 Parameter definitions and use + +### Invoke Id + +See definition in clause 7.6.1 + +### IMSI + +Identity of the service subscriber who has established the call and who is allowed to terminate the call. + +Shall be present if the call was established by a service subscriber roaming in the relay MSC area. + +### Talker Priority + +For the definition and use of this parameter see 3GPP TS 43.068 [100] + +### Additional Info + +For the definition and use of this parameter see 3GPP TS 43.068 [100] + +### Provider Error + +See definition of provider error in clause 7.6.1. + +## 10.7A MAP\_SEND\_GROUP\_CALL\_INFO service + +### 10.7A.1 Definitions + +This service is used in a RANflex configuration (see 3GPP TS 23.236 [133]) between the subscriber's visited MSC and group call serving MSC of the subscriber's location area. + +The MAP\_SEND\_GROUP\_CALL\_INFO service is a confirmed service using the service primitives given in table 10.7A/1. + +## 10.7A.2 Service primitives + +Table 10.7A/1: MAP\_SEND\_GROUP\_CALL\_INFO service + +| Parameter name | Request | Indication | Response | Confirm | +|--------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| Requested Info | M | M(=) | | | +| Teleservice | M | M(=) | | | +| Cell Id | C | C(=) | | | +| Group Id | M | M(=) | | | +| IMSI | C | C(=) | C | C(=) | +| Talker Priority | C | C(=) | | | +| Additional Info | C | C(=) | C | C(=) | +| TMSI | C | C(=) | | | +| CKSN | C | C(=) | | | +| Anchor MSC Address | | | C | C(=) | + +| | | | | | +|--------------------------|--|--|---|------| +| ASCI Call Reference | | | C | C(=) | +| Additional Subscriptions | | | C | C(=) | +| Kc | | | C | C(=) | +| User Error | | | C | C(=) | +| Provider Error | | | | O | + +7449 + +### 7450 10.7A.3 Parameter definitions and use + +#### 7451 Invoke Id + +7452 See definition in clause 7.6.1 + +#### 7453 Requested Info + +7454 For the definition and use of this parameter see 3GPP TS 43.068 [100] + +#### 7455 Teleservice + +7456 Voice Broadcast Service or Voice Group Call Service. + +#### 7457 Cell Id + +7458 Identity of the initiating service subscriber's current cell. + +#### 7459 Group Id + +7460 For the definition and use of this parameter see 3GPP TS 43.068 [100] and 3GPP TS 43.069 [101]. + +7461 If prefixes are used together with group IDs, the most significant digit of the Group Id contains the prefix. + +#### 7462 IMSI + +7463 If sent in the request: Identity of the service subscriber who has established the call and who is allowed to terminate the + +7464 call. + +7465 If sent in the response: Identity of the uplink requesting service subscriber. + +#### 7466 Talker Priority + +7467 For the definition and use of this parameter see 3GPP TS 43.068 [100] + +#### 7468 Additional Info + +7469 For the definition and use of this parameter see 3GPP TS 43.068 [100] + +#### 7470 TMSI + +7471 See definition in clause 7.6.2. + +#### 7472 CKSN + +7473 See clause 7.6.7 for the use of this parameter. + +#### 7474 Anchor MSC Address + +7475 For the definition and use of this parameter see 3GPP TS 43.068 [100] and 3GPP TS 43.069 [101] + +#### 7476 ASCI Call Reference + +7477 For the definition and use of this parameter see 3GPP TS 43.068 [100] and 3GPP TS 43.069 [101] + +#### 7478 Additional Subscriptions + +7479 For the definition and use of this parameter see 3GPP TS 43.068 [100] + +#### 7480 Kc + +7481 See clause 7.6.7 for the use of this parameter. + +#### 7482 User Error + +7483 For definition of this parameter see clause 7.6.1 The following errors defined in clause 7.6.1 may be used, depending on +7484 the nature of the fault: + +- 7485 - System Failure; +- 7486 - Unexpected Data Value; +- 7487 - Data Missing +- 7488 - TeleserviceNotProvisioned; +- 7489 - Unknown Subscriber; +- 7490 - Ongoing Call. + +#### 7491 Provider Error + +7492 See definition of provider error in clause 7.6.1. + +### 7493 10.8 Void + +### 7494 10.9 Void + +### 7495 10.10 MAP\_SET\_REPORTING\_STATE service + +#### 7496 10.10.1 Definition + +7497 This service is used between the HLR and the VLR to set the reporting state for a requested service. It is a confirmed +7498 service using the service primitives shown in table 10.10/1. + +#### 7499 10.10.2 Service primitives + +7500 **Table 10.10/1: MAP\_SET\_REPORTING\_STATE parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMSI | C | C(=) | | | +| LMSI | C | C(=) | | | +| CCBS Monitoring | C | C(=) | | | +| CCBS Subscriber Status | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7501 + +#### 7502 10.10.3 Parameter use + +7503 See clause 7.6 for a definition of the parameters used, in addition to the following. + +##### 7504 IMSI + +7505 The IMSI is a mandatory parameter if the service is used as the only one in a dialogue. + +##### 7506 CCBS Monitoring + +7507 This parameter indicates whether monitoring for CCBS shall be started or stopped. If it indicates that monitoring shall + 7508 be started this service corresponds to the message 'Start Reporting' in 3GPP TS 23.093 [107]; if it indicates that + 7509 monitoring shall be stopped this service corresponds to the message 'Stop Reporting' in 3GPP TS 23.093 [107]. + +7510 CCBS Subscriber Status + +7511 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +7512 User error + +7513 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following + 7514 values defined in clause 7.6.1: + +- 7515 - System Failure; +- 7516 - Unidentified Subscriber; +- 7517 - Unexpected Data Value; +- 7518 - Data Missing; +- 7519 - Resource Limitation; +- 7520 - Facility Not Supported. + +7521 NOTE: This error is reserved for future use. + +7522 Provider error + +7523 These are defined in clause 7.6. + +## 7524 10.11 MAP\_STATUS\_REPORT service + +### 7525 10.11.1 Definition + +7526 This service is used by the VLR to report an event or call outcome to the HLR. It is a confirmed service using the + 7527 service primitives shown in table 10.11/1. + +### 7528 10.11.2 Service primitives + +7529 **Table 10.11/1: MAP\_STATUS\_REPORT parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| CCBS Subscriber Status | C | C(=) | | | +| Monitoring Mode | C | C(=) | | | +| Call Outcome | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7530 + +### 7531 10.11.3 Parameter use + +7532 See clause 7.6 for a definition of the parameters used, in addition to the following. + +7533 CCBS Subscriber Status + +7534 If this parameter is present without Monitoring Mode and Call Outcome this service corresponds to the message 'Event + 7535 Report' in 3GPP TS 23.093 [107]. See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its + 7536 presence. + +7537 Monitoring Mode + +7538 If this parameter is present with CCBS Call Outcome this service corresponds to the message 'CCBS Call Report' in +7539 3GPP TS 23.093 [107]. See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +#### 7540 Call Outcome + +7541 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +#### 7542 User error + +7543 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following +7544 values defined in clause 7.6.1: + +- 7545 - Unknown Subscriber; +- 7546 - System Failure; +- 7547 - Unexpected Data Value; +- 7548 - Data Missing. + +#### 7549 Provider error + +7550 These are defined in clause 7.6. + +## 7551 10.12 MAP\_REMOTE\_USER\_FREE service + +### 7552 10.12.1 Definition + +7553 This service is used between the HLR and the VLR to report that the B subscriber is now idle and that the A subscriber +7554 can be notified. It is a confirmed service using the service primitives shown in table 10.12/1. + +### 7555 10.12.2 Service primitives + +7556 **Table 10.12/1: MAP\_REMOTE\_USER\_FREE parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|---------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| Call Info | M | M(=) | | | +| CCBS Feature | M | M(=) | | | +| Translated B Number | M | M(=) | | | +| Replace B Number | C | C(=) | | | +| Alerting Pattern | C | C(=) | | | +| RUF Outcome | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7557 + +### 7558 10.12.3 Parameter use + +7559 See clause 7.6 for a definition of the parameters used, in addition to the following. + +#### 7560 Call Info + +7561 See 3GPP TS 23.093 [107] for the use of this parameter. + +#### 7562 CCBS Feature + +7563 See 3GPP TS 23.093 [107] for the conditions for the presence of the parameters included in the CCBS feature. + +#### 7564 Translated B Number + +7565 See 3GPP TS 23.093 [107] for the use of this parameter. + +7566 Replace B Number + +7567 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +7568 Alerting Pattern + +7569 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +7570 RUF Outcome + +7571 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +7572 User error + +7573 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following +7574 values defined in clause 7.6.1: + +- 7575 - Unexpected Data Value; +- 7576 - Data Missing; +- 7577 - Incompatible Terminal; +- 7578 - This error is returned by the responder when the terminal used for CCBS activation is not compatible with the +7579 terminal used for the CCBS recall. For details refer to 3GPP TS 24.008 [35]; +- 7580 - Absent Subscriber (IMSI Detach; Restricted Area; No Page Response); +- 7581 - System Failure; +- 7582 - Busy Subscriber (CCBS Busy). + +7583 Provider error + +7584 These are defined in clause 7.6. + +7585 **10.13 MAP\_IST\_ALERT service** + +7586 **10.13.1 Definition** + +7587 This service is used between the MSC (Visited MSC or Gateway MSC) and the HLR, to report that the IST timer +7588 running for a call for the Subscriber has expired. It is a confirmed service using the service primitives shown in +7589 table 10.13/1. + +7590 **10.13.2 Service primitives** + +7591 **Table 10.13/1: MAP\_IST\_ALERT parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| IST Alert Timer | | | C | C(=) | +| IST Information Withdraw | | | C | C(=) | +| Call termination Indicator | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7592 + +7593 **10.13.3 Parameter use** + +7594 All parameters are described in clause 7.6. The following clarifications are applicable: + +7595 IST Alert Timer + +7596 If included in the IST Alert response, it includes the new IST Alert timer value that must be used to inform the HLR +7597 about the call activities that the subscriber performs. + +7598 IST Information Withdraw + +7599 If included in the IST Alert response, this parameter is used to indicate that the IST condition has been removed for the +7600 subscriber. When the MSC receives this parameter, IST control for that call shall be terminated. + +7601 Call termination Indicator + +7602 If included in the IST Alert response, this parameter is used to indicate whether the MSC shall terminate the call activity +7603 that had previously triggered the IST Alert procedure, or it shall also release all other call activities for the specified +7604 subscriber (outgoing call activities if the IST Alert is initiated by the VMSC, or incoming call activities if the IST Alert +7605 is initiated by the GMSC). Release of all other call activities is possible only if the MSC has the capability to link the +7606 call activities for the Subscriber by using the IMSI as key. + +7607 User error + +7608 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +- 7609 - System Failure; +- 7610 - Unexpected Data Value; +- 7611 - Resource Limitation; +- 7612 - Facility Not Supported; +- 7613 - Unknown Subscriber. + +## 7614 10.14 MAP\_IST\_COMMAND service + +### 7615 10.14.1 Definition + +7616 This service is used by the HLR to instruct the MSC (Visited MSC or Gateway MSC) to terminate ongoing call +7617 activities for a specific subscriber. It is a confirmed service using the service primitives shown in table 10.14/1. + +### 7618 10.14.2 Service primitives + +7619 **Table 10.14/1: MAP\_IST\_COMMAND parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7620 + +### 7621 10.14.3 Parameter use + +7622 All parameters are described in clause 7.6. The following clarifications are applicable: + +7623 User error + +7624 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +- 7625 - System Failure; +- 7626 - Unexpected Data Value; +- 7627 - Resource Limitation; +- 7628 - Facility Not Supported; + +7629 - Unknown Subscriber. + +## 7630 10.15 MAP\_RELEASE\_RESOURCES service + +### 7631 10.15.1 Definition + +7632 This service is used between the GMSC and the terminating VMSC. The service is invoked by the GMSC to request the +7633 VMSC to release the resources associated with the specified MSRN. + +7634 This is a confirmed service which uses the Primitives listed in table 10.15/1. + +### 7635 10.15.2 Service primitives + +7636 **Table 10.15/1: MAP\_RELEASE\_RESOURCES parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| MSRN | M | M(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7637 + +### 7638 10.15.3 Parameter use + +#### 7639 MSRN + +7640 See 3GPP TS 23.018 [97] for the use of this parameter. + +#### 7641 User error + +7642 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +- 7643 - System Failure; +- 7644 - Unexpected Data Value; + +#### 7645 Provider error + +7646 These are defined in clause 7.6. + +--- + +## 7647 11 Supplementary services related services + +### 7648 11.1 MAP\_REGISTER\_SS service + +#### 7649 11.1.1 Definition + +7650 This service is used between the MSC and the VLR and between the VLR and the HLR to register data related to a +7651 supplementary service. The VLR will relay the message to the HLR. + +7652 The service is a confirmed service and uses the service primitives shown in table 11.1/1. + +#### 7653 11.1.2 Service primitives + +7654 **Table 11.1/1: MAP\_REGISTER\_SS parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | + +| | | | | | +|-------------------------------------|---|------|---|------| +| SS-Code | M | M(=) | | | +| Basic service | C | C(=) | | | +| Forwarded-to number with subaddress | C | C(=) | | | +| No reply condition time | C | C(=) | | | +| EMLPP default priority | C | C(=) | C | C(=) | +| Long FTN Supported | C | C(=) | | | +| NbrUser | C | C(=) | C | C(=) | +| Forwarding information | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7655 + +### 7656 11.1.3 Parameter use + +7657 Invoke id + +7658 See clause 7.6.1 for the use of this parameter. + +7659 SS-Code + +7660 This parameter indicates the supplementary service which the mobile subscriber wants to register. + +7661 Basic service + +7662 This parameter indicates for which basic service group the supplementary service is to be registered. If it is not +7663 included, the registration request applies to all basic services. + +7664 Forwarded-to number with subaddress + +7665 This parameter is obligatory if the registration applies to one or more call forwarding supplementary services. It can +7666 optionally include a sub-address. + +7667 No reply condition time + +7668 This parameter is included if the registration applies to the Call Forwarding on No Reply supplementary service (or a +7669 superset of this service) and the mobile subscriber supplies a value for this time. + +7670 EMLPP default priority + +7671 This parameter is sent by the initiator to register the eMLPP default priority level and is returned by the responder at +7672 successful outcome of the service. + +7673 Long FTN Supported + +7674 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. + +7675 NbrUser + +7676 This parameter is sent by the initiator to register the MC maximum number of user defined circuit switched bearers to +7677 be used. + +7678 Forwarding information + +7679 This parameter is returned by the responder at successful outcome of the service, if the registration request concerned +7680 one or a group of Call Forwarding supplementary services. + +7681 User error + +7682 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following +7683 values defined in clause 7.6.1: + +7684 - System failure; + +7685 - Data missing; + +7686 - Unexpected data value; + +- 7687 - Call Barred; +- 7688 - Bearer service not provisioned; +- 7689 - This error is returned only if not even a subset of the requested bearer service group has been subscribed to; +- 7690 - Teleservice not provisioned; +- 7691 This error is returned only if not even a subset of the requested teleservice group has been subscribed to; +- 7692 - Illegal SS operation; +- 7693 - SS error status; +- 7694 - SS incompatibility. + +7695 Provider error + +7696 See clause 7.6.1 for the use of this parameter. + +## 7697 11.2 MAP\_ERASE\_SS service + +### 7698 11.2.1 Definition + +7699 This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a +7700 supplementary service. The VLR will relay the message to the HLR. + +7701 The service is a confirmed service and uses the service primitives shown in table 11.2/1. + +### 7702 11.2.2 Service primitives + +7703 **Table 11.2/1: MAP\_ERASE\_SS parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| SS-Code | M | M(=) | | | +| Basic service | C | C(=) | | | +| Forwarding information | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7704 + +### 7705 11.2.3 Parameter use + +7706 Invoke id + +7707 See clause 7.6.1 for the use of this parameter. + +7708 SS-Code + +7709 This parameter indicates the supplementary service which the mobile subscriber wants to erase. + +7710 Basic service + +7711 This parameter indicates for which basic service group the supplementary service should be erased. If it is not included, +7712 the erasure request applies to all basic services. + +7713 Forwarding information + +7714 This parameter is returned by the responder at successful outcome of the service, if the erasure request concerned one or +7715 a group of Call Forwarding supplementary services. + +7716 User error + +7717 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following +7718 values, defined in clause 7.6.1: + +- 7719 - System failure; +- 7720 - Data Missing; +- 7721 - Unexpected data value; +- 7722 - Bearer service not provisioned; +7723 This error is returned only if not even a subset of the requested bearer service group has been subscribed to; +- 7724 - Teleservice not provisioned; +7725 This error is returned only if not even a subset of the requested teleservice group has been subscribed to; +- 7726 - Call Barred; +- 7727 - Illegal SS operation; +- 7728 - SS error status. + +7729 Provider error + +7730 See clause 7.6.1 for the use of this parameter. + +## 7731 11.3 MAP\_ACTIVATE\_SS service + +### 7732 11.3.1 Definition + +7733 This service is used between the MSC and the VLR and between the VLR and the HLR to activate a supplementary +7734 service. The VLR will relay the message to the HLR. + +7735 The service is a confirmed service and uses the service primitives shown in table 11.3/1. + +### 7736 11.3.2 Service primitives + +7737 **Table 11.3/1: MAP\_ACTIVATE\_SS parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|--------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| SS-Code | M | M(=) | | | +| Long FTN Supported | C | C(=) | | | +| Basic service | C | C(=) | | | +| Forwarding information | | | C | C(=) | +| Call barring information | | | C | C(=) | +| SS-Data | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7738 + +### 7739 11.3.3 Parameter use + +7740 Invoke id + +7741 See clause 7.6.1 for the use of this parameter. + +7742 SS-Code + +7743 This parameter indicates the supplementary service which the mobile subscriber wants to activate. + +7744 Basic service + +7745 This parameter indicates for which basic service groups the requested supplementary service(s) should be activated. If it +7746 is not included, the activation request applies to all basic services. + +7747 Forwarding information + +7748 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned +7749 Call Forwarding. + +7750 Long FTN Supported + +7751 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. + +7752 Call barring information + +7753 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned +7754 Call Barring. + +7755 SS-Data + +7756 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned for +7757 example Call Waiting. + +7758 User error + +7759 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following +7760 values, defined in clause 7.6.1: + +- 7761 - System failure; +- 7762 - Data Missing; +- 7763 - Unexpected data value; +- 7764 - Bearer service not provisioned; +- 7765 - This error is returned only if not even a subset of the requested bearer service group has been subscribed to. +- 7766 - Teleservice not provisioned; +- 7767 - This error is returned only if not even a subset of the requested teleservice group has been subscribed to. +- 7768 - Call Barred; +- 7769 - Illegal SS operation; +- 7770 - SS error status; +- 7771 - SS subscription violation; +- 7772 - SS incompatibility; +- 7773 - Negative PW check; +- 7774 - Number Of PW Attempts Violation. + +7775 Provider error + +7776 See clause 7.6.1 for the use of this parameter. + +## 7777 11.4 MAP\_DEACTIVATE\_SS service + +### 7778 11.4.1 Definitions + +7779 This service is used between the MSC and the VLR and between the VLR and the HLR to deactivate a supplementary +7780 service. The VLR will relay the message to the HLR. + +7781 The service is a confirmed service and uses the service primitives shown in table 11.4/1. + +## 7782 11.4.2 Service primitives + +7783 **Table 11.4/1: MAP\_DEACTIVATE\_SS parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|--------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| SS-Code | M | M(=) | | | +| Basic service | C | C(=) | | | +| Forwarding information | | | C | C(=) | +| Call barring information | | | C | C(=) | +| SS-Data | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7784 + +## 7785 11.4.3 Parameter use + +### 7786 Invoke id + +7787 See clause 7.6.1 for the use of this parameter. + +### 7788 SS-Code + +7789 This parameter indicates the supplementary service which the mobile subscriber wants to deactivate. + +### 7790 Basic service + +7791 This parameter indicates for which basic service group the requested supplementary service(s) should be deactivated. If +7792 it is not included the deactivation request applies to all basic services. + +### 7793 Forwarding information + +7794 This parameter is returned by the responder at successful outcome of the service, if the deactivation request concerned +7795 one or a group of Call Forwarding supplementary services. + +### 7796 Call barring information + +7797 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned one +7798 or a group of Call Barring supplementary services. + +### 7799 SS-Data + +7800 This parameter is returned by the responder at successful outcome of the service, for example if the deactivation request +7801 concerned the Call Waiting supplementary service. + +### 7802 User error + +7803 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following +7804 values, defined in clause 7.6.1: + +- 7805 - System failure; +- 7806 - Data Missing; +- 7807 - Unexpected data value; +- 7808 - Bearer service not provisioned; +7809 This error is returned only if not even a subset of the requested bearer service group has been subscribed to; +- 7810 - Teleservice not provisioned; +7811 This error is returned only if not even a subset of the requested teleservice group has been subscribed to; + +- 7812 - Call Barred; +- 7813 - Illegal SS operation; +- 7814 - SS error status; +- 7815 - SS subscription violation; +- 7816 - Negative PW check; +- 7817 - Number Of PW Attempts Violation. + +7818 Provider error + +7819 See clause 7.6.1 for the use of this parameter. + +## 7820 11.5 MAP\_INTERROGATE\_SS service + +### 7821 11.5.1 Definitions + +7822 This service is used between the MSC and the VLR and between the VLR and the HLR to retrieve information related + 7823 to a supplementary service. The VLR will relay the message to the HLR if necessary. + +7824 The service is a confirmed service and consists of four service primitives. + +### 7825 11.5.2 Service primitives + +7826 The service primitives are shown in table 11.5/1. + +7827 **Table 11.5/1: MAP\_INTERROGATE\_SS parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|--------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| SS-Code | M | M(=) | | | +| Basic service | C | C(=) | | | +| Long FTN Supported | C | C(=) | | | +| SS-Status | | | C | C(=) | +| Basic service Group LIST | | | C | C(=) | +| Forwarding feature LIST | | | C | C(=) | +| CLI restriction Info | | | C | C(=) | +| EMLPP Info | | | C | C(=) | +| MC Information | | | C | C(=) | +| CCBS Feature LIST | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7828 + +### 7829 11.5.3 Parameter use + +7830 For additional information on parameter use refer to the GSM 04.8x and 04.9x-series of technical specifications. + +7831 Invoke id + +7832 See clause 7.6.1 for the use of this parameter. + +7833 SS-Code + +7834 The mobile subscriber can only interrogate a single supplementary service per service request. + +7835 Basic service + +7836 This parameter indicates for which basic service group the given supplementary service is interrogated. If it is not + 7837 included, the interrogation request applies to all basic services. + +7838 SS-Status + +7839 This parameter is included by the responder if: + +- 7840 - the interrogated supplementary service can only be subscribed for all applicable basic services simultaneously; +- 7841 or +- 7842 - the interrogated supplementary service is not active for any of the interrogated basic services, or +- 7843 - the interrogation was for the CCBS supplementary service and no CCBS request is active or the service is not +- 7844 provisioned. + +7845 Basic service group LIST + +7846 This parameter LIST is used to include one or a series of basic service groups for which the interrogated supplementary + +7847 service is active. If the interrogated supplementary service is not active for any of the interrogated (and provisioned) + +7848 basic service groups, the SS-Status parameter is returned. + +7849 Long FTN Supported + +7850 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. + +7851 Forwarding feature LIST + +7852 The forwarding feature parameter is described in clause 7.6.4. A list of one or more forwarding features is returned by + +7853 the responder when the interrogation request applied to Call Forwarding supplementary service. + +7854 If no basic service code parameter is provided within this sequence, the forwarding feature parameter applies to all + +7855 provisioned basic services. + +7856 CLI restriction Info + +7857 The CLI-RestrictionInfo parameter is returned by the responder when the interrogation request applies to the CLIR + +7858 supplementary service. + +7859 EMLPP Info + +7860 The eMLPP info (maximum entitled priority and default priority) is returned by the responder if the interrogation + +7861 request applies to the eMLPP supplementary service. + +7862 MC Information + +7863 The MC information (NbrSB, NbrUser and NbrSN) is returned by the responder if the interrogation request applies to + +7864 the MC supplementary service. For a definition of these 3 components, refer to 3GPP TS 23.135 and 3GPP TS 24.135. + +7865 CCBS Feature LIST + +7866 The CCBS feature parameter is described in clause 7.6. A list of one or more CCBS features is returned by the + +7867 responder when the interrogation request applied to the CCBS supplementary service. See 3GPP TS 23.093 [107] for + +7868 the conditions for the presence of the parameters included in the CCBS feature. + +7869 User error + +7870 This error is sent by the responder upon unsuccessful outcome of the interrogation service, and then takes one of the + +7871 following values, defined in clause 7.6.1: + +- 7872 - System failure; +- 7873 - Data Missing; +- 7874 - Unexpected data value; +- 7875 - Bearer Service not provisioned; +- 7876 This error is returned only if not even a subset of the interrogated bearer services are provided; +- 7877 - Teleservice not provisioned; + +7878 This error is returned only if not even a subset of the interrogated teleservices are provided; + +7879 - Call Barred; + +7880 - Illegal SS operation; + +7881 - SS not available. + +7882 Provider error + +7883 See clause 7.6.1 for the use of this parameter. + +## 7884 11.6 Void + +## 7885 11.7 MAP\_REGISTER\_PASSWORD service + +### 7886 11.7.1 Definitions + +7887 This service is used between the MSC and the VLR and between the VLR and the HLR if the mobile subscriber +7888 requests to register a new password. The VLR will relay the message to the HLR. + +7889 The service is a confirmed service and consists of four service primitives. + +### 7890 11.7.2 Service primitives + +7891 The service primitives are shown in table 11.7/1. + +7892 **Table 11.7/1: MAP\_REGISTER\_PASSWORD parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| SS-Code | M | M(=) | | | +| New password | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7893 + +### 7894 11.7.3 Parameter use + +7895 Invoke id + +7896 See clause 7.6.1 for the use of this parameter. + +7897 SS-Code + +7898 This parameter indicates for which supplementary service(s) the password should be registered. + +7899 New Password + +7900 See clause 7.6.4 for the use of this parameter. + +7901 User error + +7902 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following +7903 values, defined in clause 7.6.1: + +7904 - System failure; + +7905 - Data Missing; + +7906 - Unexpected data value; + +- 7907 - Call Barred; +- 7908 - SS subscription violation; +- 7909 - Password registration failure; +- 7910 - Negative PW check; +- 7911 - Number Of PW Attempts Violation. + +7912 Provider error + +7913 See clause 7.6.1 for the use of this parameter. + +## 7914 11.8 MAP\_GET\_PASSWORD service + +### 7915 11.8.1 Definitions + +7916 This service is used between the HLR and the VLR and between the VLR and the MSC when the HLR receives a + 7917 request from the mobile subscriber for an operation on a supplementary service which requires a password from the + 7918 subscriber. The VLR will relay the message to the MSC. + +7919 The service is a confirmed service and uses the service primitives shown in table 11.8/1. + +### 7920 11.8.2 Service primitives + +7921 **Table 11.8/1: MAP\_GET\_PASSWORD parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| Linked id | C | C(=) | | | +| Guidance info | M | M(=) | | | +| Current password | | | M | M(=) | +| Provider error | | | | O | + +7922 + +### 7923 11.8.3 Parameter use + +7924 Invoke id + +7925 See clause 7.6.1 for the use of this parameter. + +7926 Linked Id + +7927 See clause 7.6.1 for the use of this parameter. If the MAP\_GET\_PASSWORD service is used in conjunction with the + 7928 MAP\_REGISTER\_PASSWORD service, this parameter must be present; otherwise it must be absent. + +7929 Guidance info + +7930 See clause 7.6.4 for the use of this parameter. + +7931 Current password + +7932 See clause 7.6.4 for the use of this parameter. + +7933 Provider error + +7934 See clause 7.6.1 for the use of this parameter. + +## 7935 11.9 MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST 7936 service + +## 11.9.1 Definitions + +This service is used between the MSC and the VLR, between the VLR and the HLR, between the HLR and gsmSCF and between the HLR and HLR to relay information in order to allow unstructured supplementary service operation. + +The MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST service is a confirmed service using the primitives from table 11.9/1. + +## 11.9.2 Service primitives + +**Table 11.9/1: MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|-------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| USSD Data Coding Scheme | M | M(=) | C | C(=) | +| USSD String | M | M(=) | C | C(=) | +| MSISDN | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +## 11.9.3 Parameter use + +### Invoke id + +See clause 7.6.1 for the use of this parameter. + +### USSD Data Coding Scheme + +See clause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the unstructured supplementary service application. If this parameter is present, then the USSD String parameter has to be present. + +### USSD String + +See clause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the unstructured supplementary service application. If this parameter is present, then the USSD Data Coding Scheme parameter has to be present. + +### MSISDN + +The subscriber's basic MSISDN. + +See definition in clause 7.6.2. For Follow Me when the service request is sent from the HLR of the A subscriber, the parameter shall contain the MSISDN of the A subscriber, see 3GPP TS 23.094 [129]. For other purposes the MSISDN may be included as an operator option, e.g. to allow addressing the subscriber's data in the gsmSCF with the MSISDN. + +### User error + +This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values defined in clause 7.6.1: + +- System failure; + +- Data missing; + +- Unexpected data value; + +This error is returned by the responder if it is not able to deal with the contents of the USSD string. + +- Call Barred; + +- Unknown Alphabet. + +### Provider error + +7971 See clause 7.6.1 for the use of this parameter. + +## 7972 11.10 MAP\_UNSTRUCTURED\_SS\_REQUEST service + +### 7973 11.10.1 Definitions + +7974 This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC +7975 when the invoking entity requires information from the mobile user, in connection with unstructured supplementary +7976 service handling. + +7977 The MAP\_UNSTRUCTURED\_SS\_REQUEST service is a confirmed service using the primitives from table 11.10/1. + +### 7978 11.10.2 Service primitives + +7979 **Table 11.10/1: MAP\_UNSTRUCTURED\_SS\_REQUEST parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|-------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| USSD Data Coding Scheme | M | M(=) | C | C(=) | +| USSD String | M | M(=) | C | C(=) | +| Alerting Pattern | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +7980 + +### 7981 11.10.3 Parameter use + +#### 7982 Invoke id + +7983 See clause 7.6.1 for the use of this parameter. + +#### 7984 USSD Data Coding Scheme + +7985 See clause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the mobile +7986 user's MMI input. If this parameter is present, then the USSD String parameter has to be present. + +#### 7987 USSD String + +7988 See clause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the mobile +7989 user's MMI input. If this parameter is present, then the USSD Data Coding Scheme parameter has to be present. + +#### 7990 Alerting Pattern + +7991 See clause 7.6.3 for the use of this parameter. + +#### 7992 User error + +7993 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following +7994 values defined in clause 7.6.1: + +- 7995 - System failure; +- 7996 - Data missing; +- 7997 - Unexpected data value; +- 7998 This error is returned by the responder if it is not able to deal with the contents of the USSD string; +- 7999 - Absent Subscriber; +- 8000 - Illegal Subscriber; + +8001 This error indicates that delivery of the unstructured supplementary service data failed because the MS failed +8002 authentication; +8003 - Illegal Equipment; +8004 - USSD Busy; +8005 - Unknown Alphabet. +8006 Provider error +8007 See clause 7.6.1 for the use of this parameter. + +## 8008 11.11 MAP\_UNSTRUCTURED\_SS\_NOTIFY service + +### 8009 11.11.1 Definitions + +8010 This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC +8011 when the invoking entity requires a notification to be sent to the mobile user, in connection with unstructured +8012 supplementary services handling. + +8013 The MAP\_UNSTRUCTURED\_SS\_NOTIFY service is a confirmed service using the primitives from table 11.11/1. + +### 8014 11.11.2 Service primitives + +8015 **Table 11.11/1: MAP\_UNSTRUCTURED\_SS\_NOTIFY parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|-------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| USSD Data Coding Scheme | M | M(=) | | | +| USSD String | M | M(=) | | | +| Alerting Pattern | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8016 + +### 8017 11.11.3 Parameter use + +8018 Invoke id + +8019 See clause 7.6.1 for the use of this parameter. + +8020 USSD Data Coding Scheme: + +8021 See clause 7.6.4 for the use of this parameter. + +8022 USSD String: + +8023 See clause 7.6.1 for the use of this parameter. + +8024 Alerting Pattern + +8025 See clause 7.6.3 for the use of this parameter. + +8026 User error + +8027 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following +8028 values defined in clause 7.6.1: + +8029 - System failure; + +8030 - Data missing; + +- 8031 - Unexpected data value; +- 8032 This error is returned by the responder if it is not able to deal with the contents of the USSD string. +- 8033 - Absent Subscriber; +- 8034 - Illegal Subscriber; +- 8035 This error indicates that delivery of the unstructured supplementary service data failed because the MS failed +8036 authentication. +- 8037 - Illegal Equipment; +- 8038 - USSD Busy; +- 8039 - Unknown Alphabet. +- 8040 Provider error +- 8041 See clause 7.6.1 for the use of this parameter. + +## 8042 11.12 MAP\_SS\_INVOCATION\_NOTIFY + +### 8043 11.12.1 Definition + +- 8044 This service is used between the MSC and the gsmSCF when the subscriber invokes one of the following +8045 supplementary services; Call Deflection (CD), Explicit Call Transfer (ECT) or Multi Party (MPTY). +- 8046 This service is used between the HLR and the gsmSCF when the subscriber invokes the CCBS supplementary service. + +### 8047 11.12.2 Service primitives + +- 8048 The service primitives are shown in table 11.12/1. + +8049 **Table 11.12/1: SS\_INVOCATION\_NOTIFY parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|---------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| MSISDN | M | M(=) | | | +| IMSI | M | M(=) | | | +| SS- event | M | M(=) | | | +| SS- event data | C | C(=) | | | +| B-subscriber Number | C | C(=) | | | +| CCBS Request State | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8050 + +### 8051 11.12.3 Parameter use + +- 8052 All parameters are described in clause 7.6. The use of these parameters and the requirements for their presence are +8053 specified in 3GPP TS 23.078. + +#### 8054 User error + +- 8055 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: +- 8056 - Data Missing; +- 8057 - Unexpected Data Value; +- 8058 - Unknown Subscriber. + +8059 Provider error + +8060 This is defined in clause 7.6.1. + +## 8061 11.13 MAP\_REGISTER\_CC\_ENTRY service + +### 8062 11.13.1 Definition + +8063 This service is used between the MSC and the VLR and between the VLR and the HLR to register data for a requested +8064 call completion supplementary service. The VLR will relay the message to the HLR. + +8065 The service is a confirmed service and uses the service primitives shown in table 11.13/1. + +### 8066 11.13.2 Service primitives + +8067 **Table 11.13/1: MAP\_REGISTER\_CC\_ENTRY parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|---------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| SS Code | M | M(=) | | | +| CCBS Feature | C | C(=) | C | C(=) | +| Translated B number | C | C(=) | | | +| Service Indicator | C | C(=) | | | +| Call Info | C | C(=) | | | +| Network Signal Info | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8068 + +### 8069 11.13.3 Parameter use + +8070 See clause 7.6 for a definition of the parameters used, in addition to the following. + +#### 8071 SS-Code + +8072 This parameter indicates the call completion supplementary service for which the mobile subscriber wants to register an +8073 entry. + +#### 8074 CCBS Feature + +8075 See 3GPP TS 23.093 [107] for the conditions for the presence of the parameters included in the CCBS feature. + +#### 8076 Translated B Number + +8077 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +#### 8078 Service Indicator + +8079 This parameter corresponds to the parameters 'Presentation Indicator' and 'CAMEL Invoked' in 3GPP TS 23.093 [107]. +8080 It indicates which services have been invoked for the original call (e.g. CLIR, CAMEL). See 3GPP TS 23.093 [107] for +8081 the use of this parameter and the conditions for its presence. + +#### 8082 Call Info + +8083 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +#### 8084 Network Signal Info + +8085 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. + +#### 8086 User error + +8087 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following +8088 values, defined in clause 7.6.1: + +- 8089 - System failure; +- 8090 - Data missing; +- 8091 - Unexpected data value; +- 8092 - Call Barred; +- 8093 - Illegal SS operation; +- 8094 - SS error status; +- 8095 - SS incompatibility. +- 8096 - Short Term Denial; +- 8097 - Long Term Denial; +- 8098 - Facility Not Supported; + +8099 NOTE: This error is reserved for future use. + +8100 Private Extensions shall not be sent with these user errors for this operation. + +8101 Provider error + +8102 See clause 7.6.1 for the use of this parameter. + +## 8103 11.14 MAP\_ERASE\_CC\_ENTRY service + +### 8104 11.14.1 Definition + +8105 This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a call +8106 completion supplementary service. The VLR will relay the message to the HLR. + +8107 The service is a confirmed service and uses the service primitives shown in table 11.14/1. + +### 8108 11.14.2 Service primitives + +8109 **Table 11.14/1: MAP\_ERASE\_CC\_ENTRY parameters** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| SS-Code | M | M(=) | C(=) | C(=) | +| CCBS Index | C | C(=) | | | +| SS-Status | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8110 + +### 8111 11.14.3 Parameter use + +8112 See clause 7.6 for a definition of the parameters used, in addition to the following. + +8113 SS-Code + +8114 This parameter indicates the call completion supplementary service for which the mobile subscriber wants to erase an +8115 entry/entries. + +8116 CCBS Index + +8117 See 3GPP TS 23.093 [107] for the use of this parameter and the condition for its presence. + +8118 SS-Status + +8119 Depending on the outcome of the service request this parameter may indicate either provisioned and active or not +8120 provisioned. + +8121 User error + +8122 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following +8123 values, defined in clause 7.6.1: + +- 8124 - System failure; +- 8125 - Data Missing; +- 8126 - Unexpected data value; +- 8127 - Call Barred; +- 8128 - Illegal SS operation; +- 8129 - SS error status. + +8130 Private Extensions shall not be sent with these user errors for this operation. + +8131 Provider error + +8132 See clause 7.6.1 for the use of this parameter. + +--- + +## 8133 12 Short message service management services + +### 8134 12.1 MAP-SEND-ROUTING-INFO-FOR-SM service + +#### 8135 12.1.1 Definition + +8136 This service is used between the gateway MSC and the HLR to retrieve the routing information needed for routing the +8137 short message to the servicing MSC or MME but not both, or SGSN, or (for T4-device triggering via the IMS) IP-SM- +8138 GW, or SMSF. This service is also used between the gateway MSC and SMS Router, and SMS Router and HLR in +8139 order to enforce routing of the SM delivery via the HPLMN of the receiving MS. This service is also used between +8140 HLR and IP-SM-GW, and between IP-SM-GW and HLR in order to allow MT-SM delivery (other than T4-device +8141 triggering) via the IMS. + +8142 This service is also used with an IWF interfacing the S6c interface. + +8143 The MAP-SEND-ROUTING-INFO-FOR-SM is a confirmed service using the primitives from table 12.1/1. + +#### 8144 12.1.2 Service primitives + +8145 **Table 12.1/1: MAP-SEND-ROUTING-INFO-FOR-SM** + +| Parameter name | Request | Indication | Response | Confirm | +|--------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| MSISDN | M | M(=) | | | +| SM-RP-PRI | M | M(=) | | | +| Service Centre Address | M | M(=) | | | +| SM-RP-MTI | C | C(=) | | | +| SM-RP-SMEA | C | C(=) | | | +| GPRS Support Indicator | C | C(=) | | | +| SM-Delivery Not Intended | U | C(=) | | | +| IP-SM-GW Guidance | U | C(=) | | | + +| | | | | | +|------------------------------------------|---|------|---|------| +| Support Indicator | | | | | +| Single Attempt Delivery | C | C(=) | | | +| IMSI | C | C(=) | C | C(=) | +| Correlation ID | C | C(=) | | | +| T4 Trigger Indicator | C | C(=) | | | +| SMSF Support Indicator | C | C(=) | | | +| Network Node Number | | | C | C(=) | +| Network Node Diameter Address | | | C | C(=) | +| LMSI | | | C | C(=) | +| GPRS Node Indicator | | | C | C(=) | +| Additional Number | | | C | C(=) | +| Additional Network Node Diameter Address | | | C | C(=) | +| IP-SM-GW Guidance | | | U | C(=) | +| Third Number | | | C | C(=) | +| Third Network Node Diameter Address | | | C | C(=) | +| IMS Node Indicator | | | C | C(=) | +| SMSF 3GPP Number | | | C | C(=) | +| SMSF 3GPP Diameter Address | | | C | C(=) | +| SMSF Non-3GPP Number | | | C | C(=) | +| SMSF Non-3GPP Diameter Address | | | C | C(=) | +| SMSF 3GPP Address Indicator | | | C | C(=) | +| SMSF Non 3GPP Address Indicator | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8146 + +### 8147 12.1.3 Parameter use + +#### 8148 Invoke id + +8149 See definition in clause 7.6.1. + +#### 8150 MSISDN + +8151 See definition in clause 7.6.2. + +8152 When SEND-ROUTING-INFO-FOR-SM is sent by the SMS-GMSC to the HLR following an T4 Submit Trigger (see +8153 3GPP TS 23.682 [148]), MSISDN may not be available. In this case the UE shall be identified by the IMSI and the +8154 MSISDN shall take the dummy MSISDN value (see clause 3 of 3GPP TS 23.003 [17]). + +8155 When SEND-ROUTING-INFO-FOR-SM is sent by the SMS-GMSC to the HLR in a retry context of SMS for IMS UE +8156 to IMS UE without MSISDN (see 3GPP TS 23.204 [134]), MSISDN may not be available. In this case the UE shall be +8157 identified by a Correlation ID (SIP-URI-B) and the MSISDN shall take the dummy MSISDN value (see clause 3 of +8158 3GPP TS 23.003 [17]). + +#### 8159 SM-RP-PRI + +8160 See definition in clause 7.6.8. + +#### 8161 Service Centre Address + +8162 See definition in clause 7.6.2. + +#### 8163 SM-RP-MTI + +8164 See definition in clause 7.6.8. This parameter shall be present when the feature « SM filtering by the HPLMN » is +8165 supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub- +8166 layer protocol. + +8167 SM-RP-SMEA + +8168 See definition in clause 7.6.8. This parameter shall be present when the feature « SM filtering by the HPLMN » is +8169 supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub- +8170 layer protocol. + +8171 GPRS Support Indicator + +8172 See definition in clause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports receiving of the +8173 two numbers from the HLR. + +8174 SM-Delivery Not Intended + +8175 This parameter indicates by its presence that delivery of a short message is not intended. It further indicates whether +8176 only IMSI or only MCC+MNC are requested. + +8177 This parameter may be set by entities that request the service without intending to deliver a short message (e.g. MMS +8178 Relay/Server), and shall be evaluated by the SMS Router and may be evaluated by the HLR. + +8179 IP-SM-GW Guidance Support Indicator + +8180 This parameter indicates whether or not the SMS-GMSC is prepared to receive IP-SM-GW Guidance in the response. + +8181 Single Attempt Delivery + +8182 This parameter indicates the short message is only valid for delivering once, and the HLR/HSS does not need to add the +8183 received SC address into MWD list in the case there is no serving node available to provide SMS to the user. + +8184 IMSI + +8185 See definition in clause 7.6.2. + +8186 In Request and Indication: + +8187 IMSI shall be present if MSISDN is not available. When SEND-ROUTING-INFO-FOR-SM is sent by the SMS-GMSC +8188 to the HLR in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [134]), IMSI may +8189 not be available. In this case the IMSI parameter shall be populated with the HLR-ID value. + +8190 In Response and Confirm: If enforcement of routing an SM via the HPLMN of the receiving MS is deployed, this +8191 parameter contains an MT Correlation ID instead of an IMSI when the service is used between SMS-GMSC and SMS +8192 Router (see 3GPP TS 23.040 [26] for more information). If the "SM-Delivery Not Intended" parameter was present in +8193 the Indication with a value of "only MCC+MNC requested", then this parameter may contain MCC+MNC+dummy +8194 MSIN. + +8195 The presence of this parameter is mandatory in a successful case. + +8196 T4 Trigger Indicator + +8197 This indicator indicates by its presence that the request is sent in the context of T4 device triggering (see 3GPP TS +8198 23.682 [148]). When received, the HLR may return up to three serving node numbers and shall not forward the request +8199 to an IP-SM-GW or SMS Router. + +8200 SMSF Support Indicator + +8201 It indicates that the requesting node is capable of receiving ISDN numbers and/or Diameter addresses of the SMSF as +8202 target of MT-SMS. + +8203 Correlation ID + +8204 The Correlation ID parameter contains the SIP-URI-B identifying the (MSISDN-less) destination user. SIP-URI-A and +8205 HLR-ID shall be absent from this parameter. + +8206 The Correlation ID indicates by its presence that the request is sent in the context of MSISDN-less SMS delivery in +8207 IMS (see 3GPP TS 23.204 [134]). When received, the HLR shall return the IP-SM-GW number and shall not forward +8208 the request to an IP-SM-GW. + +8209 Network Node Number + +8210 See definition in clause 7.6.2. This parameter is provided in a successful response. If the "SM-Delivery Not Intended" +8211 parameter was present in the Indication a dummy address (encoded in the same manner as the dummy MSISDN defined +8212 in clause 3.3 of 3GPP TS 23.003 [17]) may be provided. See clause 12.1.4. + +8213 Network Node Diameter Address + +8214 See definition in clause 7.6.2. See clause 12.1.4. + +8215 LMSI + +8216 See definition in clause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for the +8217 HLR to include the LMSI in a successful response, if the VLR has used the LMSI. + +8218 GPRS Node Indicator + +8219 See definition in clause 7.6.8. + +8220 Outside the context of T4 device triggering: The presence of this parameter is mandatory if only the SGSN number is +8221 sent in the Network Node Number (i.e. if the value within Network Node Number is to be considered as SGSN-Number +8222 and Additional Number is absent). + +8223 Within the context of T4 device triggering: The presence of this parameter is mandatory if the value within Network +8224 Node Number is to be considered as SGSN-Number and Third Number is absent. + +8225 Additional Number + +8226 See definition in clause 7.6.2. See clause 12.1.4. + +8227 Additional Network Node Diameter Address + +8228 See definition in clause 7.6.2. See clause 12.1.4. + +8229 IP-SM-GW Guidance + +8230 This parameter contains the recommended and the minimum timer values for supervision of MT-Forward-Short- +8231 Message response. Shall be absent if the IP-SM-GW-Guidance Support Indicator in the request is absent. This +8232 parameter is only used by IP-SM-GW and SMS-GMSC. + +8233 Third Number + +8234 See definition in clause 7.6.2. See clause 12.1.4. + +8235 Third Network Node Diameter Address + +8236 See definition in clause 7.6.2. See clause 12.1.4. + +8237 IMS Node Indicator + +8238 See definition in clause 7.6.8. + +8239 Outside the context of T4 device triggering: The parameter is not applicable and shall be absent. + +8240 Within the context of T4 device triggering: The presence of this parameter is mandatory if the value within Network +8241 Node Number is to be considered as IP-SM-GW-Number and Third Number is absent. + +8242 SMSF 3GPP Number + +8243 This parameter contains the ISDN number of the SMSF target node for MT-SMS over 3GPP access. + +8244 SMSF 3GPP Diameter Address + +8245 This parameter contains the Diameter Name and Realm of the SMSF target node for MT-SMS over 3GPP access. + +8246 SMSF Non-3GPP Number + +8247 This parameter contains the ISDN number of the SMSF target node for MT-SMS over non-3GPP access. + +8248 SMSF Non-3GPP Diameter Address + +8249 This parameter contains the Diameter Name and Realm of the SMSF target node for MT-SMS over non-3GPP access. + +#### 8250 SMSF 3GPP Address Indicator + +8251 It indicates that the parameter Network Node Number (and Network Node Diameter Address, if present) contains the +8252 address of an SMSF for 3GPP access. + +#### 8253 SMSF Non-3GPP Address Indicator + +8254 It indicates that the parameter Network Node Number (and Network Node Diameter Address, if present) contains the +8255 address of an SMSF for non-3GPP access. + +#### 8256 User error + +8257 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: + +- 8258 - Unknown subscriber; +- 8259 - Call Barred; +- 8260 - Teleservice Not Provisioned; +- 8261 - Absent Subscriber\_SM; +- 8262 - Facility Not Supported; +- 8263 - System failure; +- 8264 - Unexpected Data Value; +- 8265 - Data missing. + +#### 8266 Provider error + +8267 For definition of provider errors see clause 7.6.1. + +### 8268 **12.1.4 Identities of MT-SMS Target Nodes** + +8269 In a successful MAP-Send-Routing-Info-For-SM response at least one MT-SMS Target Node identity or an SMS +8270 Router identity shall be present and this shall be an E.164 number within the Network Node Number parameter. + +8271 In addition, optionally a second Target Node identity or an SMS Router identity may be present as E.164 number within +8272 the Additional Number Parameter. + +8273 In T4 device trigger scenarios in addition to a second Target Node identity, a third Target Node Identity may be present +8274 as E.164 number within the Third Number parameter. + +8275 In addition to the E.164 identity of an MT-SMS Target Node or an SMSRouter, the presence of the Diameter +8276 Name/Realm of the corresponding target node or SMS Router follows the hereafter rules: + +- 8277 - If Network Node Number contains an MME number for SMS, Network Node Diameter Address shall be present +8278 and contain the Diameter address of the MME. +- 8279 - If Network Node Number contains an MSC number, Network Node Diameter Address may be present and shall +8280 contain the Diameter address of the MME. +- 8281 - If Network Node Number contains an SGSN number, Network Node Diameter Address shall be present only if +8282 the HSS has received the information that SGSN supports the Gdd interface. +- 8283 - If Network Node Number contains an SMS Router number, Network Node Diameter Address may be present +8284 and shall contain the SMS Router Diameter address. +- 8285 - If Network Node Number contains an IP-SM-GW number, Network Node Diameter Address may be present and +8286 shall contain the IP-SM-GW Diameter address. + +8287 Similar for Additional Number - Additional Network Node Diameter Address; + +8288 Similar for Third Number - Third Network Node Diameter Address. + +8289 In scenarios supporting interworking with 5G System, an E.164 Number and a Diameter Address of the SMSF may be + 8290 present, for both 3GPP and non-3GPP accesses. In addition: + +- 8291 - If Network Node Number contains an SMSF 3GPP number, Network Node Diameter Address may be present + 8292 and shall contain the SMSF 3GPP Diameter address. +- 8293 - If Network Node Number contains an SMSF Non-3GPP number, Network Node Diameter Address may be + 8294 present and shall contain the SMSF Non-3GPP Diameter address. + +8295 + +## 8296 12.2 MAP-MO-FORWARD-SHORT-MESSAGE service + +### 8297 12.2.1 Definition + +8298 This service is used between the serving MSC or the SGSN or IP-SM-GW and the SMS Interworking MSC to forward + 8299 mobile originated short messages. + +8300 The MAP-MO-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in + 8301 table 12.2/1. + +### 8302 12.2.2 Service primitives + +8303 + +**Table 12.2/1: MAP-MO-FORWARD-SHORT-MESSAGE** + +| Parameter name | Request | Indication | Response | Confirm | +|---------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| SM RP DA | M | M(=) | | | +| SM RP OA | M | M(=) | | | +| SM RP UI | M | M(=) | C | C(=) | +| IMSI | C | C(=) | | | +| Correlation ID | C | C(=) | | | +| SM Delivery Outcome | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8304 + +### 8305 12.2.3 Parameter use + +8306 Invoke id + +8307 See definition in clause 7.6.1. + +8308 SM RP DA + +8309 See definition in clause 7.6.8. + +8310 In the mobile originated SM transfer this parameter contains the Service Centre address received from the mobile + 8311 station. + +8312 SM RP OA + +8313 See definition in clause 7.6.8. + +8314 The MSISDN received from the VLR or from the SGSN is inserted in this parameter in the mobile originated SM + 8315 transfer. + +8316 A Dummy MSISDN value is used for MSISDN-less SMS in IMS. In this case the originating user is identified by SIP- + 8317 URI-A (see Correlation ID). + +8318 SM RP UI + +8319 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted +8320 in this parameter. + +8321 IMSI + +8322 See definition in clause 7.6.2.1. The IMSI of the originating subscriber shall be inserted in this parameter in the mobile +8323 originated SM transfer. + +8324 Correlation ID + +8325 The Correlation ID is composed of an HLR-Id identifying the destination user's HLR, a SIP-URI-B identifying the +8326 MSISDN-less destination user, and a SIP-URI-A identifying the originating user. + +8327 The Correlation ID indicates by its presence that the request is sent in the context of MSISDN-less SMS delivery in +8328 IMS (see 3GPP TS 23.204 [134]), and that a Report-SM-Delivery status needs to be sent to the HLR to add the SC +8329 address to the MWD. + +8330 SM Delivery Outcome + +8331 See definition in clause 7.6.8. This parameter indicates the status of the mobile terminated SM delivery. + +8332 Shall be present if Correlation ID is present and shall take one of the unsuccessful outcome values. + +8333 User error + +8334 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: + +- 8335 - Facility Not Supported; +- 8336 - System Failure; +- 8337 - SM Delivery Failure; + - 8338 - The reason of the SM Delivery Failure can be one of the following in the mobile originated SM: + - 8339 - unknown Service Centre address; + - 8340 - Service Centre congestion; + - 8341 - invalid Short Message Entity address; + - 8342 - subscriber not Service Centre subscriber; + - 8343 - protocol error. +- 8344 - Unexpected Data Value + +8345 Provider error + +8346 For definition of provider errors see clause 7.6.1. + +## 8347 12.3 MAP-REPORT-SM-DELIVERY-STATUS service + +### 8348 12.3.1 Definition + +8349 This service is used between the gateway MSC and the HLR or the external Short Message Gateway (IP-SM-GW) and +8350 the HLR. The MAP-REPORT-SM-DELIVERY-STATUS service is used to set the Message Waiting Data into the HLR +8351 or to inform the HLR of successful SM transfer after polling. This service is invoked by the gateway MSC or the +8352 external Short Message Gateway (IP-SM-GW). + +8353 The MAP-REPORT-SM-DELIVERY-STATUS service is a confirmed service using the service primitives given in +8354 table 12.3/1. + +### 8355 12.3.2 Service primitives + +8356 + +**Table 12.3/1: MAP-REPORT-SM-DELIVERY-STATUS** + +| Parameter name | Request | Indication | Response | Confirm | +|-----------------------------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| MSISDN | M | M(=) | | | +| IMSI | C | C(=) | | | +| Service Centre Address | M | M(=) | | | +| SM Delivery Outcome | M | M(=) | | | +| Absent Subscriber Diagnostic SM | C | C(=) | | | +| GPRS Support Indicator | C | C(=) | | | +| Delivery Outcome Indicator | C | C(=) | | | +| Additional SM Delivery Outcome | C | C(=) | | | +| Additional Absent Subscriber Diagnostic SM | C | C(=) | | | +| IP-SM-GW-Indicator | C | C(=) | | | +| IP-SM-GW SM Delivery Outcome | C | C(=) | | | +| IP-SM-GW Absent Subscriber Diagnostic SM | C | C(=) | | | +| Single Attempt Delivery | C | C(=) | | | +| Correlation ID | C | C(=) | | | +| SMSF 3GPP Delivery Outcome Indicator | C | C(=) | | | +| SMSF 3GPP SM Delivery Outcome | C | C(=) | | | +| SMSF 3GPP Absent Subscriber Diagnostic SM | C | C(=) | | | +| SMSF non-3GPP Delivery Outcome Indicator | C | C(=) | | | +| SMSF non-3GPP SM Delivery Outcome | C | C(=) | | | +| SMSF non-3GPP Absent Subscriber Diagnostic SM | C | C(=) | | | +| MSISdn-Alert | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8357 + +### 8358 12.3.3 Parameter use + +8359 Invoke id + +8360 See definition in clause 7.6.1. + +8361 MSISDN + +8362 See definition in clause 7.6.2. + +8363 When REPORT-SM-DELIVERY-STATUS is sent by the SMS-GMSC to the HLR following an T4 Submit Trigger +8364 (see 3GPP TS 23.682 [148]), MSISDN may not be available. In this case the UE shall be identified by the IMSI and the +8365 MSISDN shall take the dummy MSISDN value (see clause 3 of 3GPP TS 23.003 [17]). + +8366 When REPORT-SM-DELIVERY-STATUS is sent by the SMS-GMSC to the HLR in a retry context of SMS for IMS +8367 UE to IMS UE without MSISDN (see 3GPP TS 23.204 [134]), MSISDN may not be available. In this case the UE shall +8368 be identified by a Correlation ID (SIP-URI-B) and the MSISDN shall take the dummy MSISDN value (see clause 3 of +8369 3GPP TS 23.003 [17]). + +8370 IMSI + +8371 See definition in clause 7.6.2. When REPORT-SM-DELIVERY-STATUS is sent by the SMS-GMSC to the HLR in a +8372 retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [134]), IMSI may not be +8373 available. In this case the IMSI parameter shall be populated with an HLR-ID). + +8374 Service Centre Address + +8375 See definition in clause 7.6.2. + +8376 SM Delivery Outcome + +8377 See definition in clause 7.6.8. This parameter indicates the status of the mobile terminated SM delivery. + +8378 Absent Subscriber Diagnostic SM + +8379 See definition in clause 7.6.8. + +8380 GPRS Support Indicator + +8381 See definition in clause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports handling of two +8382 delivery outcomes. + +8383 Delivery Outcome Indicator + +8384 See definition in clause 7.6.8. + +8385 Additional SM Delivery Outcome + +8386 See definition in clause 7.6.8. + +8387 Additional Absent Subscriber Diagnostic SM + +8388 See definition in clause 7.6.8. + +8389 IP-SM-GW Indicator + +8390 See definition in clause 7.6.8. + +8391 IP-SM-GW SM Delivery Outcome + +8392 See definition in clause 7.6.8. + +8393 IP-SM-GW Absent Subscriber Diagnostic SM + +8394 See definition in clause 7.6.8. + +8395 Single Attempt Delivery + +8396 This parameter indicates the short message is only valid for delivering once, and the HLR/HSS does not need to add the +8397 received SC address into MWD list. It may only be present in the case the delivery of the short message failed due to +8398 absent subscriber or MS memory capacity exceeded. + +8399 **Editor's Note: Description of the use of this parameter might be needed in 3GPP TS 23.040.** + +8400 Correlation ID + +8401 The Correlation ID parameter contains the SIP-URI-B identifying the (MSISDN-less) destination user. SIP-URI-A and +8402 HLR-ID shall be absent from this parameter. + +8403 SMSF 3GPP Delivery Outcome Indicator + +8404 See definition in clause 7.6.8. + +8405 SMSF 3GPP SM Delivery Outcome + +8406 See definition in clause 7.6.8. + +8407 SMSF 3GPP Absent Subscriber Diagnostic SM + +8408 See definition in clause 7.6.8. + +8409 SMSF Non-3GPP Delivery Outcome Indicator + +8410 See definition in clause 7.6.8. + +8411 SMSF Non-3GPP SM Delivery Outcome + +8412 See definition in clause 7.6.8. + +8413 SMSF Non-3GPP Absent Subscriber Diagnostic SM + +8414 See definition in clause 7.6.8. + +8415 MSIsdn-Alert + +8416 See definition in clause 7.6.2. This parameter shall be present in case of unsuccessful delivery, when the MSISDN +8417 received in the operation is different from the stored MSIsdn-Alert; the stored MSIsdn-Alert is the value that is returned +8418 to the gateway MSC. + +8419 User error + +8420 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: + +- 8421 - Unknown Subscriber; +- 8422 - Message Waiting List Full; +- 8423 - Unexpected Data Value; +- 8424 - Data missing. + +8425 Provider error + +8426 For definition of provider errors see clause 7.6.1. + +## 8427 12.4 MAP-READY-FOR-SM service + +### 8428 12.4.1 Definition + +8429 This service is used between the MSC and VLR as well as between the VLR and the HLR. The MSC initiates this +8430 service if a subscriber indicates memory available situation. The VLR uses the service to indicate this to the HLR. + +8431 The VLR initiates this service if a subscriber, whose message waiting flag is active in the VLR, has radio contact in the +8432 MSC. + +8433 Also this service is used between the SGSN and the HLR. The SGSN initiates this service if a subscriber indicates +8434 memory available situation. The SGSN uses the service to indicate this to the HLR. + +8435 Also this service is used between the HSS and the MME via an IWF. The MME initiates this service if a subscriber +8436 indicates memory available situation. The MME uses the service to indicate this to the HLR. + +8437 The SGSN initiates this service if a subscriber, whose message waiting flag is active in the SGSN, has radio contact in +8438 the GPRS. + +8439 The MME initiates this service if a subscriber, whose message waiting flag is active in the MME, has radio contact via +8440 LTE. + +8441 Also this service is used between the external Short Message Gateway (IP-SM-GW) and the HLR. The IP-SM-GW +8442 initiates this service if a subscriber indicates memory available situation. The IP-SM-GW uses the service to indicate +8443 this to the HLR. + +8444 The IP-SM-GW initiates this service if a subscriber, whose message waiting flag is active in the IP-SM-GW, is +8445 reachable in IMS. + +8446 The MAP-READY-FOR-SM service is a confirmed service using the primitives from table 12.4/1. + +### 8447 12.4.2 Service primitives + +8448 + +**Table 12.4/1: MAP-READY-FOR-SM** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| IMSI | C | C(=) | | | + +| | | | | | +|--------------------------------------|---|------|---|------| +| TMSI | C | C(=) | | | +| Alert Reason | M | M(=) | | | +| Alert Reason Indicator | C | C(=) | | | +| Additional Alert
Reason Indicator | C | C(=) | | | +| Maximum UE
Availability Time | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8449 + +### 8450 12.4.3 Parameter use + +8451 Invoke id + +8452 See definition in clause 7.6.1. + +8453 IMSI + +8454 See definition in clause 7.6.2. The IMSI is used always between the VLR and the HLR and between the SGSN and the +8455 HLR and between the HSS and the IWF. Between the MSC and the VLR the identification can be either IMSI or TMSI. + +8456 TMSI + +8457 See definition in clause 7.6.2. The identification can be either IMSI or TMSI between MSC and VLR. + +8458 Alert Reason + +8459 See definition in clause 7.6.8. This parameter indicates if the mobile subscriber is present or the MS has memory +8460 available. + +8461 Alert Reason Indicator + +8462 See definition in clause 7.6.8. This parameter by its presence indicates the message is sent from SGSN, and by its +8463 absence indicates the message is sent from VLR or MME via IWF. + +8464 Additional Alert Reason Indicator + +8465 See definition in clause 7.6.8. + +8466 Maximum UE Availability Time + +8467 See definition in clause 7.6.8. This information element may be included by the SGSN or MSC when notifying the HLR +8468 that the MS is reachable. + +8469 User error + +8470 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: + +- 8471 - Unknown Subscriber; +- 8472 - Facility Not Supported; +- 8473 - System Failure; +- 8474 - Unexpected Data Value; +- 8475 - Data missing. + +8476 Provider error + +8477 For definition of provider errors see clause 7.6.1. + +### 8478 12.5 MAP-ALERT-SERVICE-CENTRE service + +## 8479 12.5.1 Definition + +8480 This service is used between the HLR and the interworking MSC. The HLR initiates this service, if the HLR detects +8481 that a subscriber, whose MSISDN is in the Message Waiting Data file, is active or the MS has memory available. + +8482 This service is also used between an MME (via an IWF), SGSN or an MSC using Deployment Option 2 (see clause +8483 8.2.4a.1 of 3GPP TS 23.272 [143] and 3GPP TS 23.040 [6]) and the SMS-GMSC (possibly via an SMS Router), to +8484 indicate that a MS, for which one or more MT SMS have been requested to be retransmitted at a later time, is now +8485 available for MT SMS delivery or has moved under the coverage of another MME, SGSN or MSC. This procedure is +8486 used according to the call flows described in clause 10.1 of 3GPP TS 23.040 [26]. + +8487 The MAP-ALERT-SERVICE-CENTRE service is a confirmed service using the primitives from table 12.5/1. + +## 8488 12.5.2 Service primitives + +8489 **Table 12.5/1: MAP-ALERT-SERVICE-CENTRE** + +| Parameter name | Request | Indication | Response | Confirm | +|---------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| MSIsdn-Alert | M | M(=) | | | +| IMSI | C | C(=) | | | +| Correlation ID | C | C(=) | | | +| Service Centre Address | M | M(=) | | | +| Maximum UE Availability | C | C(=) | | | +| Time | | | | | +| SMS-GMSC Alert Event | C | C(=) | | | +| SMS-GMSC Diameter Address | C | C(=) | | | +| New SGSN Number | C | C(=) | | | +| New SGSN Diameter Address | C | C(=) | | | +| New MME Number | C | C(=) | | | +| New MME Diameter Address | C | C(=) | | | +| New MSC Number | C | C(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8490 + +## 8491 12.5.3 Parameter use + +### 8492 Invoke id + +8493 See definition in clause 7.6.1. + +### 8494 MSIsdn-Alert + +8495 See definition in clause 7.6.2. + +8496 When the service is used between the HLR and the SMS-IWMSC, the provided MSISDN shall be the one which is +8497 stored in the Message Waiting Data file. If no MSISDN is available, the dummy MSISDN value (see clause 3 of 3GPP +8498 TS 23.003 [17]) shall be sent and an IMSI or Correlation ID (SIP-URI-B) shall be present. + +8499 When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, the dummy MSISDN +8500 value (see clause 3 of 3GPP TS 23.003 [17]) shall be sent and an IMSI shall be present. + +### 8501 IMSI + +8502 When the service is used between the HLR and the SMS-IWMSC, the provided IMSI shall be the identifier which is +8503 stored in the Message Waiting Data file if no MSISDN is available in the context of T4 device triggering (see 3GPP TS +8504 23.682 [148]). + +8505 When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, this information element +8506 shall contain the IMSI in the request sent from the MME (via an IWF), SGSN or MSC, or the User Identifier Alert + +8507 previously sent in the MT Forward Short Message response, when the request is sent from the SMS Router to the SMS- +8508 GMSC. + +8509 Correlation ID + +8510 When the service is used between the HLR and the SMS-IWMSC, the provided SIP-URI-B within the Correlation ID +8511 parameter shall be the identifier which is stored in the Message Waiting Data file if no MSISDN is available in a retry +8512 context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [134]). HLR-ID and SIP-URI-A shall +8513 be absent. + +8514 When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, this information element +8515 shall not be included. + +8516 Service Centre Address + +8517 See definition in clause 7.6.2. + +8518 When the service is used between the HLR and the SMS-IWMSC, this information element shall contain the E.164 +8519 number of the Service Center. + +8520 When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, this information element +8521 shall contain the E.164 number of the SMS-GMSC (or SMS Router) previously received in the SMS-GMSC Address IE +8522 in the MT Forward Short Message Request. + +8523 Maximum UE Availability Time + +8524 See definition in clause 7.6.8. + +8525 When the service is used between the HLR and the SMS-IWMSC, this information element shall be included, if +8526 available. + +8527 When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, this information element +8528 shall not be included. + +8529 SMS-GMSC Alert Event + +8530 See definition in clause 7.6.8. + +8531 When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included. + +8532 When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, this information element +8533 shall either indicate that the MS is now available for MT SMS or that the MS has moved under the coverage of another +8534 MME, SGSN or MSC. + +8535 New SGSN Number + +8536 See definition in clause 7.6.8. + +8537 When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included. + +8538 When the service is used between an MME (via an IWF) or SGSN and the SMS-GMSC, this information element may +8539 be included if the SMS-GMSC Alert Event indicates that the MS has moved under the coverage of another SGSN. +8540 When present, it shall contain the E.164 number of the new SGSN serving the MS. + +8541 New MME Number + +8542 See definition in clause 7.6.8. + +8543 When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included. + +8544 When the service is used between an MME (via an IWF) or SGSN and the SMS-GMSC, this information element may +8545 be included if the SMS-GMSC Alert Event indicates that the MS has moved under the coverage of another MME. +8546 When present, it shall contain the E.164 number of the new MME serving the MS. + +8547 New SGSN Diameter Address + +8548 See definition in clause 7.6.8. + +8549 When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included. + +8550 When the service is used between an MME (via an IWF) or SGSN and the SMS-GMSC, this information element shall + 8551 be included if available and if the SMS-GMSC Alert Event indicates that the MS has moved under the coverage of + 8552 another SGSN. When present, it shall contain the Diameter Identity of the new SGSN serving the MS. + +8553 New MME Diameter Address + +8554 See definition in clause 7.6.8. + +8555 When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included. + +8556 When the service is used between an MME (via an IWF) or SGSN and the SMS-GMSC, this information element shall + 8557 be included if available and if the SMS-GMSC Alert Event indicates that the MS has moved under the coverage of + 8558 another MME. When present, it shall contain the Diameter Identity of the new MME serving the MS. + +8559 SMS-GMSC Diameter Address + +8560 See definition in clause 7.6.2. + +8561 When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included. + +8562 When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, this information element + 8563 shall contain, if available, the Diameter Identity of the SMS-GMSC (or SMS Router) previously received in the SMS- + 8564 GMSC Diameter Address IE in the MT Forward Short Message Request. + +8565 New MSC Number + +8566 See definition in clause 7.6.8.33. + +8567 When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included. + +8568 When the service is used between an MSC and the SMS-GMSC, this information element may be included if the SMS- + 8569 GMSC Alert Event indicates that the MS has moved under the coverage of another MSC. When present, it shall contain + 8570 the E.164 number of the new MSC serving the MS. + +8571 + +8572 User error + +8573 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: + +8574 - System Failure; + +8575 - Unexpected Data Value; + +8576 - Data missing. + +8577 Provider error + +8578 For definition of provider errors see clause 7.6.1. + +## 8579 12.6 MAP-INFORM-SERVICE-CENTRE service + +### 8580 12.6.1 Definition + +8581 This service is used between the HLR and the gateway MSC (transiting an SMS Router, if present) to inform the + 8582 Service Centre which MSISDN number is stored in the Message Waiting Data file. If the stored MSISDN number is not + 8583 the same as the one received from the gateway MSC in the MAP-SEND-ROUTING-INFO-FOR-SM service primitive + 8584 the stored MSISDN number is included in the message. + +8585 Additionally the status of MCEF, MNRF, MNRG, MNR5G and MNR5GN3G flags and the inclusion of the particular + 8586 Service Centre address in the Message Waiting Data list is informed to the gateway MSC when appropriate. + +8587 If the HLR has stored a single MNRR, the value is included in the Absent Subscriber Diagnostic SM parameter. + +8588 If the HLR has stored a second MNRR, the value of the MNRR for the MSC is included in the Absent Subscriber + 8589 Diagnostic SM parameter and the value of the MNRR for the SGSN is included in the Additional Absent Subscriber + 8590 Diagnostic SM parameter. + +8591 The MAP-INFORM-SERVICE-CENTRE service is a non-confirmed service using the primitives from table 12.6/1. + +## 8592 12.6.2 Service primitives + +8593 + +**Table 12.6/1: MAP-INFORM-SERVICE-CENTRE** + +| Parameter name | Request | Indication | +|-----------------------------------------------------|---------|------------| +| Invoke Id | M | M(=) | +| MSIsdn-Alert | C | C(=) | +| MWD Status | C | C(=) | +| Absent Subscriber
Diagnostic SM | C | C(=) | +| Additional Absent
Subscriber Diagnostic
SM | C | C(=) | +| SMSF 3GPP Absent
Subscriber Diagnostic
SM | C | C(=) | +| SMSF Non 3GPP
Absent Subscriber
Diagnostic SM | C | C(=) | + +8594 + +## 8595 12.6.3 Parameter use + +8596 Invoke id + +8597 See definition in clause 7.6.1. + +8598 MSIsdn-Alert + +8599 See definition in clause 7.6.2. This parameter refers to the MSISDN stored in a Message Waiting Data file in the HLR. + +8600 MWD Status + +8601 See definition in clause 7.6.8. This parameter indicates the status of the MCEF, MNRF, MNRG, MNR5G and + 8602 MNR5GN3G flags and the status of the particular SC address presence in the Message Waiting Data list. + +8603 Absent Subscriber Diagnostic SM + +8604 See definition in clause 7.6.8. + +8605 Additional Absent Subscriber Diagnostic SM + +8606 See definition in clause 7.6.8. + +8607 SMSF 3GPP Absent Subscriber Diagnostic SM + +8608 See definition in clause 7.6.8. + +8609 SMSF Non 3GPP Absent Subscriber Diagnostic SM + +8610 See definition in clause 7.6.8. + +## 8611 12.7 MAP-SEND-INFO-FOR-MT-SMS service + +### 8612 12.7.1 Definition + +8613 This service is used between the MSC and the VLR. The service is invoked by the MSC receiving a mobile terminated + 8614 short message to request subscriber related information from the VLR. + +8615 The MAP-SEND-INFO-FOR-MT-SMS service is a confirmed service using the primitives from table 12.7/1. + +## 8616 12.7.2 Service primitives + +8617 + +**Table 12.7/1: MAP-SEND-INFO-FOR-MT-SMS** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| SM RP DA | M | M(=) | | | +| IMSI | C | C(=) | | | +| MSISDN | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8618 + +## 8619 12.7.3 Parameter use + +8620 Invoke id + +8621 See definition in clause 7.6.1. + +8622 SM RP DA + +8623 See definition in clause 7.6.8. This parameter shall contain either an IMSI or an LMSI. + +8624 IMSI + +8625 See definition in clause 7.6.2. This parameter shall be present if the SM RP DA parameter contains an LMSI; otherwise + 8626 it shall be absent. + +8627 MSISDN + +8628 See definition in clause 7.6.2. + +8629 User error + +8630 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: + +- 8631 - Unknown subscriber; +- 8632 - Unidentified Subscriber; +- 8633 - Absent subscriber; +- 8634 - Unexpected Data Value; +- 8635 - Data Missing; +- 8636 - Illegal subscriber; +- 8637 - Illegal equipment; +- 8638 - Subscriber busy for MT SMS; +- 8639 - System Failure. + +8640 Provider error + +8641 For definition of provider errors see clause 7.6.1. + +## 8642 12.8 MAP-SEND-INFO-FOR-MO-SMS service + +## 8643 12.8.1 Definition + +8644 This service is used between the MSC and the VLR. The service is invoked by the MSC which has to handle a mobile +8645 originated short message request to request the subscriber related information from the VLR. + +8646 The MAP-SEND-INFO-FOR-MO-SMS service is a confirmed service using the primitives from table 12.8/1. + +## 8647 12.8.2 Service primitives + +8648 **Table 12.8/1: MAP-SEND-INFO-FOR-MO-SMS** + +| Parameter name | Request | Indication | Response | Confirm | +|------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| Service Centre Address | M | M(=) | | | +| MSISDN | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8649 + +## 8650 12.8.3 Parameter use + +### 8651 Invoke id + +8652 See definition in clause 7.6.1. + +### 8653 Service Centre Address + +8654 See definition in clause 7.6.2. + +### 8655 MSISDN + +8656 See definition in clause 7.6.2. + +### 8657 User error + +8658 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: + +8659 - Teleservice Not Provisioned; + +8660 - Call Barred; + +8661 - Unexpected Data Value; + +8662 - Data Missing. + +### 8663 Provider error + +8664 For definition of provider errors see clause 7.6.1. + +## 8665 12.9 MAP-MT-FORWARD-SHORT-MESSAGE service + +### 8666 12.9.1 Definition + +8667 This service is used between the gateway MSC and the serving MSC or the SGSN (transiting an SMS Router, if +8668 present) or the IP-SM-GW to forward mobile terminated short messages. + +8669 The MAP-MT-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in +8670 table 12.9/1. + +### 8671 12.9.2 Service primitives + +8672 + +**Table 12.9/1: MAP-MT-FORWARD-SHORT-MESSAGE** + +| Parameter name | Request | Indication | Response | Confirm | +|-------------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| SM RP DA | M | M(=) | | | +| SM RP OA | M | M(=) | | | +| SM RP UI | M | M(=) | C | C(=) | +| More Messages To Send | C | C(=) | | | +| SM Delivery Timer | C | C(=) | | | +| SM Delivery Start Time | C | C(=) | | | +| SMS Over IP Only Indicator | C | C(=) | | | +| Correlation ID | C | C(=) | | | +| Maximum Retransmission Time | C | C(=) | | | +| SMS-GMSC Address | C | C(=) | | | +| SMS-GMSC Diameter Address | C | C(=) | | | +| Requested Retransmission Time | | | C | C(=) | +| User Identifier Alert | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8673 + +### 8674 12.9.3 Parameter use + +#### 8675 Invoke id + +8676 See definition in clause 7.6.1. + +#### 8677 SM RP DA + +8678 See definition in clause 7.6.8. This parameter can contain either an IMSI or a LMSI. The use of the LMSI is an operator +8679 option. The LMSI can be provided if it is received from the HLR. The IMSI is used if the use of the LMSI is not +8680 available. + +8681 This parameter is omitted (i.e. is present and takes the value "noSM-RP-DA") in the mobile terminated subsequent SM +8682 transfers. + +8683 When a Correlation ID is present, the IMSI parameter within SM RP DA shall be populated with the HLR-ID and the +8684 destination user is identified by the SIP-URI-B within the Correlation ID. + +#### 8685 SM RP OA + +8686 See definition in clause 7.6.8. The Service Centre address received from the originating Service Centre is inserted in +8687 this parameter. + +8688 This parameter is omitted in the mobile terminated subsequent SM transfers. + +#### 8689 SM RP UI + +8690 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted +8691 in this parameter. A short message transfer protocol data unit may also be inserted in this parameter in the message +8692 delivery acknowledgement from the MSC or from the SGSN to the Service Centre. + +#### 8693 More Messages To Send + +8694 See definition in clause 7.6.8. The information from the MMS indication received from the Service Centre is inserted in +8695 this parameter. + +#### 8696 SM Delivery Timer + +8697 See definition in clause 7.6.8. + +#### 8698 SM Delivery Start Time + +8699 See definition in clause 7.6.8. + +8700 SMS Over IP Only Indicator + +8701 This indicator indicates by its presence that the IP-SM-GW shall try to deliver the short message via IMS without +8702 retrying to other domains. It shall be present in messages sent to the IP-SM-GW following a T4-Submit Trigger +8703 message (see 3GPP TS 23.682 [148]) but not in messages sent to MSC or SGSN (possibly transiting an SMS-Router). + +8704 The indicator also indicates to the IP-SM-GW by its presence that the IMSI within the message is a real IMSI and not a +8705 MT-Correlation ID allocated by the IP-SM-GW. + +8706 Correlation ID + +8707 The Correlation ID parameter contains the SIP-URI-B identifying the (MSISDN-less) destination user and the SIP-URI- +8708 A identifying the (MSISDN-less) originating user. HLR-ID shall be absent from this parameter. + +8709 Maximum Retransmission Time + +8710 See definition in clause 7.6.8. + +8711 SMS-GMSC Address + +8712 See definition in clause 7.6.8. + +8713 This information element shall be present if the Maximum Retransmission Time IE is present in the message. When +8714 present, it shall contain the E.164 number of the SMS-GMSC in the request sent by the SMS-GMSC or the E.164 +8715 number of the SMS Router in the request sent by the SMS Router. + +8716 SMS-GMSC Diameter Address + +8717 See definition in clause 7.6.8. + +8718 This information element shall be present if available and if the Maximum Retransmission Time IE is present in the +8719 message. When present, it shall contain the Diameter Identity of the SMS-GMSC in the request sent by the SMS- +8720 GMSC or the Diameter Identity of the SMS Router in the request sent by the SMS Router. + +8721 Requested Retransmission Time + +8722 See definition in clause 7.6.8. This information element may only be present if the MT Forward Short Message +8723 Response contains the User error set to Absent Subscriber\_SM and if the Maximum Retransmission Time information +8724 element is present in the MT Forward Short Message Request. It may be included by an MSC using Deployment Option +8725 2 (see clause 8.2.4a.1 of 3GPP TS 23.272 [143] and 3GPP TS 23.040 [6]) or the SGSN if the UE is using a power +8726 saving mechanism (such as extended idle mode DRX) and the UE is currently not reachable. + +8727 The Requested Retransmission Time shall not exceed the Maximum Retransmission Time received from the SMS- +8728 GMSC. + +8729 User-Identifier-Alert + +8730 See definition in clause 7.6.8. + +8731 This information element shall be present in the message from the SMS Router to the SMS-GMSC, if the Requested +8732 Retransmission Time IE is present in the message. When present, this information shall contain an MT Correlation ID. + +8733 User error + +8734 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: + +- 8735 - Unidentified subscriber; +- Absent Subscriber\_SM; +- 8736 - Subscriber busy for MT SMS; +- 8737 - Facility Not Supported; + +- 8738 - Illegal Subscriber indicates that delivery of the mobile terminated short message failed because the mobile +- 8739 station failed authentication; +- 8740 - Illegal equipment indicates that delivery of the mobile terminated short message failed because an IMEI check +- 8741 failed, i.e. the IMEI was prohibited-listed or not permitted-listed; +- 8742 - System Failure; +- 8743 - SM Delivery Failure: + - 8744 - The reason of the SM Delivery Failure can be one of the following in the mobile terminated SM: + - 8745 - memory capacity exceeded in the mobile equipment; + - 8746 - protocol error; + - 8747 - mobile equipment does not support the mobile terminated short message service. +- 8748 - Unexpected Data Value; +- 8749 - Data Missing. + +8750 Provider error + +8751 For definition of provider errors see clause 7.6.1. + +## 8752 12.10 MAP-MT-FORWARD-SM-FOR-VGCS service + +### 8753 12.10.1 Definition + +8754 This service is used between the SMS gateway MSC and the Group Call Anchor MSC to forward mobile terminated + +8755 short messages into an ongoing voice group call. + +8756 The MAP-MT-FORWARD-SM-FOR-VGCS service is a confirmed service using the service primitives given in + +8757 table 12.10/1. + +### 8758 12.10.2 Service primitives + +8759 **Table 12.10/1: MAP-MT-FORWARD-SM-VGCS** + +| Parameter name | Request | Indication | Response | Confirm | +|------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| ASCI Call Reference | M | M(=) | | | +| SM RP OA | M | M(=) | | | +| SM RP UI | M | M(=) | C | C(=) | +| Dispatcher List | | | C | C(=) | +| Ongoing Call Indicator | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8760 + +### 8761 12.10.3 Parameter use + +8762 Invoke id + +8763 See definition in clause 7.6.1. + +8764 ASCI Call Reference + +8765 Group call reference. This item is used to access the VGCS-GCR within the Anchor\_MSC. + +8766 SM RP OA + +8767 See definition in clause 7.6.8. The Service Centre address received from the originating Service Centre is inserted in +8768 this parameter. + +8769 SM RP UI + +8770 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted +8771 in this parameter. A short message transfer protocol data unit may also be inserted in this parameter in the message +8772 delivery acknowledgement from the MSC to the Service Centre. + +8773 Dispatcher List + +8774 A list of identities (international E.164 phone numbers) identifying the dispatchers of the VGCS call. It shall be present +8775 if received from the GCR; otherwise shall be absent. + +8776 Ongoing Call Indicator + +8777 Indicates by its presence that the VGCS call is ongoing. + +8778 User error + +8779 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: + +- 8780 - System Failure; +- 8781 - Unexpected Data Value. + +8782 Provider error + +8783 For definition of provider errors see clause 7.6.1. + +--- + +## 8784 13 Network-Requested PDP Context Activation services + +### 8785 13.1 MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service + +#### 8786 13.1.1 Definition + +8787 This service is used by the GGSN to request GPRS routing information from the HLR. + +#### 8788 13.1.2 Service primitives + +8789 **Table 13.1/1: MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS** + +| Parameter name | Request | Indication | Response | Confirm | +|-----------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| GGSN address | C | C(=) | C | C(=) | +| GGSN number | M | M(=) | | | +| SGSN address | | | C | C(=) | +| Mobile Not Reachable Reason | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8790 + +#### 8791 13.1.3 Parameter definition and use + +8792 Invoke Id + +8793 See definition in clause 7.6.1. + +8794 IMSI + +8795 See definition in clause 7.6.2. + +8796 GGSN address + +8797 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. + +8798 GGSN number + +8799 See definition in clause 7.6.2. + +8800 SGSN address + +8801 This parameter shall be present if the outcome of the Send Routing Info For GPRS request to the GPRS application +8802 process in the HLR is positive. + +8803 Mobile Not Reachable Reason + +8804 This parameter shall be present if the outcome of the Send Routing Info For GPRS request to the GPRS application +8805 process in the HLR is positive and the MNRG flag in the HLR is set. See definition in clause 7.6.3.51. + +8806 User error + +8807 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +8808 - Absent Subscriber; + +8809 - System Failure; + +8810 - Data Missing; + +8811 - Unexpected Data Value; + +8812 - Unknown Subscriber. + +8813 The diagnostic in the Unknown Subscriber may indicate "Imsi Unknown" or "Gprs Subscription Unknown". + +8814 - Call Barred; + +8815 This error will indicate that the received PDP PDUs in the GGSN shall be barred for this MS due to Operator +8816 Determined Barring. (The CallBarringCause must be the operatorBarring.) + +8817 Provider error + +8818 These are defined in clause 7.6.1. + +## 8819 13.2 MAP\_FAILURE\_REPORT service + +### 8820 13.2.1 Definition + +8821 This service is used by the GGSN to inform the HLR that network requested PDP-context activation has failed. + +### 8822 13.2.2 Service primitives + +8823 + +**Table 13.2/1: MAP\_FAILURE\_REPORT** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| GGSN address | C | C(=) | C | C(=) | +| GGSN number | M | M(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8824 + +### 13.2.3 Parameter definition and use + +#### Invoke Id + +See definition in clause 7.6.1. + +#### IMSI + +See definition in clause 7.6.2. + +#### GGSN address + +This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. + +#### GGSN number + +See definition in clause 7.6.2. + +#### User error + +This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +- System Failure; +- Data Missing; +- Unexpected Data Value; +- Unknown Subscriber. + +#### Provider error + +These are defined in clause 7.6.1. + +### 13.3 MAP\_NOTE\_MS\_PRESENT\_FOR\_GPRS service + +#### 13.3.1 Definition + +This service is used by the HLR to inform the GGSN that the MS is present for GPRS again. + +#### 13.3.2 Service primitives + +8846 + +**Table 13.3/1: MAP\_NOTE\_MS\_PRESENT\_FOR\_GPRS** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| IMSI | M | M(=) | | | +| GGSN address | C | C(=) | | | +| SGSN address | M | M(=) | | | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8847 + +### 13.3.3 Parameter definition and use + +#### Invoke Id + +See definition in clause 7.6.1. + +#### IMSI + +See definition in clause 7.6.2. + +8853 GGSN address + +8854 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. + +8855 SGSN address + +8856 See definition in clause 7.6.2. + +8857 User error + +8858 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: + +8859 - System Failure; + +8860 - Data Missing; + +8861 - Unexpected Data Value; + +8862 - Unknown Subscriber. + +8863 Provider error + +8864 These are defined in clause 7.6.1. + +--- + +## 8865 13A Location Service Management Services + +### 8866 13A.1 MAP-SEND-ROUTING-INFO-FOR-LCS Service + +#### 8867 13A.1.1 Definition + +8868 This service is used between the GMLC and the HLR to retrieve the routing information needed for routing a location +8869 service request to the servicing VMSC, SGSN, MME or 3GPP AAA server. The MAP-SEND-ROUTING-INFO-FOR- +8870 LCS is a confirmed service using the primitives from table 13A.1/1. + +#### 8871 13A.1.2 Service Primitives + +8872 + +**Table 13A.1/1: MAP-SEND-ROUTING-INFO-FOR-LCS** + +| Parameter name | Request | Indication | Response | Confirm | +|--------------------------------|---------|------------|----------|---------| +| Invoke Id | M | M(=) | M(=) | M(=) | +| MLC Number | M | M(=) | | | +| MSISDN | C | C(=) | C | C(=) | +| IMSI | C | C(=) | C | C(=) | +| LMSI | | | C | C(=) | +| Network Node Number | | | C | C(=) | +| GPRS Node Indicator | | | C | C(=) | +| Additional Number | | | C | C(=) | +| Supported LCS Capability Sets | | | C | C(=) | +| Additional LCS Capability Sets | | | C | C(=) | +| MME Name | | | C | C(=) | +| SGSN Name | | | C | C(=) | +| SGSN Realm | | | C | C(=) | +| AAA Server Name | | | C | C(=) | +| V-GMLC Address | | | U | C(=) | +| Additional V-GMLC Address | | | U | C(=) | +| H-GMLC Address | | | C | C(=) | +| PPR Address | | | U | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8873 + +### 8874 13A.1.3 Parameter Use + +8875 Invoke id + +8876 See definition in clause 7.6.1. + +8877 MLC Number + +8878 See definition in clause 7.6.2. + +8879 MSISDN + +8880 See definition in clause 7.6.2. The request shall carry either the IMSI or MSISDN. The response shall carry whichever +8881 of these was not included in the request (see 3GPP TS 23.271 for details). + +8882 IMSI + +8883 See definition in clause 7.6.2. + +8884 LMSI + +8885 See definition in clause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for the +8886 HLR to include the LMSI in a successful response, if the VLR has used the LMSI. + +8887 Network Node Number + +8888 See definition in clause 7.6.2. This parameter is provided in a successful response. If the Network Node Number and +8889 Additional Number are received in the GMLC, the Network Node Number is used in preference to the Additional +8890 Number. If the serving node has no ISDN number, the HLR shall populate the Network Node Number parameter with a +8891 dummy ISDN number of "0". + +8892 GPRS Node Indicator + +8893 See definition in clause 7.6.8. The presence of this parameter is mandatory only if the SGSN number is sent in the +8894 Network Node Number. + +8895 Additional Number + +8896 See definition in clause 7.6.2. This parameter is provided in a successful response. If the Network Node Number and +8897 Additional Number are received in the GMLC, the Network Node Number is used in preference to the Additional +8898 Number. + +8899 Supported LCS Capability Sets + +8900 See definition in clause 7.6.11. This parameter indicates the LCS capability of the serving node that is indicated by the +8901 Network Node Number. This parameter is provided only if LCS capability sets are available in HLR and Network Node +8902 Number is present in this message. + +8903 Additional LCS Capability Sets + +8904 See definition in clause 7.6.11. This parameter indicates the LCS capability of the serving node that is indicated by the +8905 Additional Number. This parameter is provided only if LCS capability sets are available in HLR and Additional +8906 Number is present in this message. + +8907 MME Name + +8908 See definition in clause 7.6.2. This parameter is provided in a successful response when the serving node is an MME. + +8909 SGSN Name + +8910 See definition in clause 7.6.2. This parameter is provided in a successful response when the serving node is an SGSN +8911 and the SGSN has indicated its support for Lgd interface. + +8912 SGSN Realm + +8913 See definition in clause 7.6.2. This parameter is provided in a successful response when the serving node is an SGSN +8914 and the SGSN has indicated its support for Lgd interface. + +8915 AAA Server Name + +8916 See definition in clause 7.6.2. This parameter is provided in a successful response when the serving node is a +8917 3GPP AAA server. + +8918 V-GMLC address + +8919 See definition in clause 7.6.2. . This parameter indicates the V-GMLC address of the serving node that is indicated by +8920 the Network Node Number. + +8921 Additional V-GMLC address + +8922 See definition in clause 7.6.2. This parameter indicates the V-GMLC address of the serving node that is indicated by the +8923 Additional Number. This parameter is provided only if additional LCS capability sets are available in HLR and +8924 Additional Number is present in this message. + +8925 H-GMLC address + +8926 See definition in clause 7.6.2. The requirements for its presence are specified in 3GPP TS 23.271 [26a]. + +8927 PPR address + +8928 See definition in clause 7.6.2. + +8929 User error + +8930 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: + +- 8931 - Unknown subscriber; +- 8932 - Absent Subscriber; +- 8933 - Facility Not Supported; +- 8934 - System failure; +- 8935 - Unexpected Data Value; +- 8936 - Data missing; +- 8937 - Unauthorised requesting network. + +8938 Provider error + +8939 For definition of provider errors see clause 7.6.1. + +## 8940 13A.2 MAP-PROVIDE-SUBSCRIBER-LOCATION Service + +### 8941 13A.2.1 Definition + +8942 This service is used by a GMLC to request the location of a target MS from the visited MSC or SGSN at any time. This +8943 is a confirmed service using the primitives from table 13A.2/1. + +### 8944 13A.2.2 Service Primitives + +8945 **Table 13A.2/1: Provide\_Subscriber\_Location** + +| Parameter name | Request | Indication | Response | Confirm | +|----------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| Location Type | M | M(=) | | | +| MLC Number | M | M(=) | | | + +| | | | | | +|---------------------------------------|---|------|---|------| +| LCS Client ID | M | M(=) | | | +| Privacy Override | U | C(=) | | | +| IMSI | C | C(=) | | | +| MSISDN | C | C(=) | | | +| LMSI | C | C(=) | | | +| LCS Priority | C | C(=) | | | +| LCS QoS | C | C(=) | | | +| IMEI | U | C(=) | | | +| Supported GAD Shapes | C | C(=) | | | +| LCS-Reference Number | C | C(=) | | | +| LCS Codeword | C | C(=) | | | +| LCS Service Type Id | C | C(=) | | | +| LCS Privacy Check | C | C(=) | | | +| Area Event Info | C | C(=) | | | +| H-GMLC Address | C | C(=) | | | +| Reporting PLMN List | C | C(=) | | | +| PeriodicLDRInfo | C | C(=) | | | +| MO-LR Short Circuit Indicator | C | C(=) | C | C(=) | +| Location Estimate | | | M | M(=) | +| GERAN Positioning Data | | | C | C(=) | +| UTRAN Positioning Data | | | C | C(=) | +| GERAN GANSS Positioning Data | | | C | C(=) | +| UTRAN GANSS Positioning Data | | | C | C(=) | +| UTRAN Additional Positioning Data | | | C | C(=) | +| UTRAN Barometric Pressure Measurement | | | C | C(=) | +| UTRAN Civic Address | | | C | C(=) | +| Age of Location Estimate | | | C | C(=) | +| Additional Location Estimate | | | C | C(=) | +| Deferred MT-LR Response Indicator | | | C | C(=) | +| Cell Id Or SAI | | | C | C(=) | +| Accuracy Fulfilment Indicator | | | C | C(=) | +| Target Serving Node for Handover | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +8946 + +### 8947 13A.2.3 Parameter Definition and Use + +8948 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are +8949 specified in 3GPP TS 23.271 [26a]. + +#### 8950 Location Type + +8951 This parameter identifies the type of location information requested. + +#### 8952 MLC Number + +8953 This is the E.164 number of the requesting GMLC. + +#### 8954 LCS Client ID + +8955 This parameter provides information related to the identity of an LCS client. + +#### 8956 Privacy Override + +8957 This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC or SGSN for an +8958 MT-LR are in the same country. + +8959 IMSI + +8960 The IMSI is provided to identify the target MS. At least one of the IMSI or MSISDN is mandatory. + +8961 MSISDN + +8962 The MSISDN is provided to identify the target MS. At least one of the IMSI or MSISDN is mandatory. + +8963 LMSI + +8964 The LMSI shall be provided if previously supplied by the HLR. This parameter is only used in the case of the MT-LR +8965 for CS domain. + +8966 LCS Priority + +8967 This parameter indicates the priority of the location request. + +8968 LCS QoS + +8969 This parameter indicates the required quality of service in terms of response time, accuracy and lcs qos class. + +8970 IMEI + +8971 The requirements for its presence are specified in 3GPP TS 23.271 [26a]. + +8972 Supported GAD Shapes + +8973 This parameter indicates which of the shapes defined in 3GPP TS 23.032 [122] are supported. + +8974 LCS-Reference Number + +8975 This parameter shall be included if a deferred MT-LR procedure is performed for a UE available event, an area event or +8976 a periodic positioning event. + +8977 LCS Codeword + +8978 See definition in clause 7.6.11.18. The requirements for its presence are specified in 3GPP TS 23.271 [26a]. + +8979 LCS Service Type Id + +8980 See definition in clause 7.6.11.15. The requirements for its presence are specified in 3GPP TS 23.271 [26a]. + +8981 LCS Privacy Check + +8982 See definition in clause 7.6.11. The requirements for its and its components presence are specified in 3GPP TS 23.271 +8983 [26a]. + +8984 Area Event Info + +8985 See definition in clause 7.6.11. The parameter shall be included if a deferred MT-LR procedure is performed for an area +8986 event. + +8987 H-GMLC address + +8988 See definition in clause 7.6.2. The parameter shall be included if a deferred MT-LR procedure is performed for a UE +8989 available event, an area event or a periodic positioning event. + +8990 Location Estimate + +8991 This parameter provides the location estimate if this is encoded in one of the supported geographical shapes. Otherwise +8992 this parameter shall consist of one octet, which shall be discarded by the receiving node. + +8993 GERAN Positioning Data + +8994 This parameter indicates the usage of each positioning method that was attempted to determine the location estimate +8995 either successfully or unsuccessfully. If Positioning Data received from the RAN contains no Positioning Methods, +8996 Positioning Data is excluded from the MAP message. It may be included in the message only if the access network is +8997 GERAN, see 3GPP TS 23.271 [26a]. + +8998 UTRAN Positioning Data + +8999 This parameter indicates the usage of each positioning method that was successfully attempted to determine the location +9000 estimate. If Position Data received from the RAN contains no Positioning Methods, UTRAN Positioning Data is +9001 excluded from the MAP message. It may be included in the message only if the access network is UTRAN, see 3GPP +9002 TS 23.271 [26a]. + +9003 GERAN GANSS Positioning Data + +9004 This parameter indicates the usage of each GANSS positioning method that was attempted to determine the location +9005 estimate either successfully or unsuccessfully. If GANSS Positioning Data received from the RAN contains no GANSS +9006 method, GERAN GANSS Positioning Data is excluded from the MAP message. It may be included in the message only +9007 if the access network is GERAN, see 3GPP TS 23.271 [26a]. + +9008 UTRAN GANSS Positioning Data + +9009 This parameter indicates the usage of each GANSS positioning method that was successfully attempted to determine the +9010 location estimate. If Position Data received from the RAN contains no GANSS Positioning Data Set, UTRAN GANSS +9011 Positioning Data is excluded from the MAP message. It may be included in the message only if the access network is +9012 UTRAN, see 3GPP TS 23.271 [26a]. + +9013 UTRAN Additional Positioning Data + +9014 This parameter indicates the usage of each Additional positioning method that was successfully attempted to determine +9015 the location estimate. If Position Data received from the RAN contains no Additional Positioning Data Set, UTRAN +9016 Additional Positioning Data is excluded from the MAP message. It may be included in the message only if the access +9017 network is UTRAN, see 3GPP TS 23.271 [26a]. + +9018 UTRAN Barometric Pressure Measurement + +9019 This parameter indicates the uncompensated barometric pressure measurement at the MS. The absence of this parameter +9020 implies that a barometric pressure measurement was not available or could not be successfully obtained. It may be +9021 included in the message only if the access network is UTRAN, see 3GPP TS 23.271 [26a]. + +9022 UTRAN Civic Address + +9023 This parameter indicates the civic address of the MS. The absence of this parameter implies that a civic address was not +9024 available or could not be successfully obtained. It may be included in the message only if the access network is +9025 UTRAN, see 3GPP TS 23.271 [26a]. + +9026 Age of Location Estimate + +9027 This parameter indicates how long ago the location estimate was obtained. + +9028 Additional Location Estimate + +9029 This parameter provides the location estimate when not provided by the Location Estimate parameter. It may be sent +9030 only if the parameter Supported GAD Shapes has been received in the Provide Subscriber Location indication and the +9031 shape to be included is supported by the GMLC. + +9032 Deferred MT-LR Response Indicator + +9033 See definition in clause 7.6.11.2. + +9034 Cell Id Or SAI + +9035 For GERAN access, this parameter indicates Global Cell Identifier of the cell that the served subscriber is currently +9036 attached to. For UTRAN access, this parameter contains the Service Area Identifier for the cell that the subscriber is +9037 currently attached to. This parameter is included only for North American Emergency Calls as described in 3GPP TS +9038 23.271 [26a]. + +9039 Accuracy Fulfilment Indicator + +9040 See definition in clause 7.6.11.28. + +9041 MO-LR Short Circuit Indicator + +9042 This parameter indicates whether MO-LR Short Circuit is permitted for periodic location. + +9043 Reporting PLMN List + +9044 This parameter indicates a list of PLMNs in which subsequent periodic MO-LR TTTP requests will be made. + +9045 Periodic LDR information + +9046 This parameter indicates the reporting amount and reporting interval of deferred periodic location. + +9047 Target Serving Node for Handover + +9048 This parameter provides the address of the target side serving node for handover of an IMS Emergency Call. + +9049 User error + +9050 This parameter is sent by the responder when the location request has failed or cannot proceed and if present, takes one +9051 of the following values defined in clause 7.6.1. + +- 9052 - System Failure; +- 9053 - Data Missing; +- 9054 - Unexpected Data Value; +- 9055 - Facility Not Supported; +- 9056 - Unidentified Subscriber; +- 9057 - Illegal Subscriber; +- 9058 - Illegal Equipment; +- 9059 - Absent Subscriber (diagnostic information may also be provided); +- 9060 - Unauthorised requesting network; +- 9061 - Unauthorised LCS Client with detailed reason; +- 9062 - Position method failure with detailed reason. + +9063 Provider error + +9064 These are defined in clause 7.6.1. + +## 9065 13A.3 MAP-SUBSCRIBER-LOCATION-REPORT Service + +### 9066 13A.3.1 Definition + +9067 This service is used by a VMSC or SGSN to provide the location of a target MS to a GMLC when a request for location is +9068 either implicitly administered or made at some earlier time. This is a confirmed service using the primitives from +9069 table 13A.3/1. + +9070 13A.3.2 Service Primitives + +9071 + +Table 13A.3/1: Subscriber\_Location\_Report + +| Parameter name | Request | Indication | Response | Confirm | +|---------------------------------------|---------|------------|----------|---------| +| Invoke id | M | M(=) | M(=) | M(=) | +| LCS Event | M | M(=) | | | +| LCS Client ID | M | M(=) | | | +| Network Node Number | M | M(=) | | | +| IMSI | C | C(=) | | | +| MSISDN | C | C(=) | | | +| NA-ESRD | C | C(=) | C | C(=) | +| NA-ESRK | C | C(=) | C | C(=) | +| IMEI | U | C(=) | | | +| Location Estimate | C | C(=) | | | +| GERAN Positioning Data | C | C(=) | | | +| UTRAN Positioning Data | C | C(=) | | | +| GERAN GANSS Positioning Data | C | C(=) | | | +| UTRAN GANSS Positioning Data | C | C(=) | | | +| UTRAN Additional Positioning Data | C | C(=) | | | +| UTRAN Barometric Pressure Measurement | C | C(=) | | | +| UTRAN Civic Address | C | C(=) | | | +| Age of Location Estimate | C | C(=) | | | +| LMSI | U | C(=) | | | +| GPRS Node Indicator | C | C(=) | | | +| Additional Location Estimate | C | C(=) | | | +| Deferred MT-LR Data | C | C(=) | | | +| LCS-Reference Number | C | C(=) | C | C(=) | +| NA-ESRK Request | C | C(=) | | | +| Cell Id Or SAI | C | C(=) | | | +| H-GMLC Address | C | C(=) | C | C(=) | +| LCS Service Type Id | C | C(=) | | | +| Pseudonym Indicator | C | C(=) | | | +| Accuracy Fulfilment Indicator | C | C(=) | | | +| Sequence Number | C | C(=) | | | +| Periodic LDR Info | C | C(=) | | | +| MO-LR Short Circuit Indicator | C | C(=) | C | C(=) | +| Target Serving Node for Handover | C | C(=) | | | +| Reporting PLMN List | | | C | C(=) | +| User error | | | C | C(=) | +| Provider error | | | | O | + +9072 + +9073 13A.3.3 Parameter Definition and Use + +9074 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are + 9075 specified in. 3GPP TS 23.271 [26a]. + +9076 LCS Event + +9077 This parameter indicates the event that triggered the Subscriber Location Report. + +9078 LCS Client ID + +9079 This parameter provides information related to the identity of the recipient LCS client. + +9080 Network Node Number + +9081 See definition in clause 7.6.2. This parameter provides the address of the sending node. + +9082 IMSI + +9083 The IMSI shall be provided if available to the VMSC or SGSN. + +9084 MSISDN + +9085 The MSISDN shall be provided if available to the VMSC or SGSN. + +9086 NA-ESRD + +9087 If the target MS has originated an emergency service call in North America, the NA-ESRD shall be provided by the +9088 VMSC if available. + +9089 If the target MS has originated an emergency service call in North America and NA-ESRK Request is included in +9090 Subscriber\_Location\_Report-Arg, an NA-ESRK or NA-ESRD, but not both, may also be included in the response to the +9091 MSC, see 3GPP TS 23.271 [26a]. + +9092 NA-ESRK + +9093 If the target MS has originated an emergency service call in North America, the NA-ESRK shall be provided by the +9094 VMSC if assigned. + +9095 If the target MS has originated an emergency service call in North America and NA-ESRK Request is included in +9096 Subscriber\_Location\_Report-Arg, an NA-ESRK or NA-ESRD, but not both, may also be included in the response to the +9097 MSC, see 3GPP TS 23.271 [26a]. + +9098 IMEI + +9099 The requirements for its presence are specified in 3GPP TS 23.271 [26a]. + +9100 Location Estimate + +9101 This parameter provides the location estimate. The absence of this parameter implies that a location estimate was not +9102 available or could not be successfully obtained. If the obtained location estimate is not encoded in one of the supported +9103 geographical shapes then this parameter shall consist of one octet, which shall be discarded by the receiving node. + +9104 GERAN Positioning Data + +9105 This parameter indicates the usage of each positioning method that was attempted to determine the location estimate +9106 either successfully or unsuccessfully. If Positioning Data received from the RAN contains no Positioning Methods, +9107 Positioning Data is excluded from the MAP message. It may be included in the message only if the access network is +9108 GERAN, see 3GPP TS 23.271 [26a]. + +9109 UTRAN Positioning Data + +9110 This parameter indicates the usage of each positioning method that was successfully attempted to determine the location +9111 estimate. If Position Data received from the RAN contains no Positioning Methods, UTRAN Positioning Data is +9112 excluded from the MAP message. It may be included in the message only if the access network is UTRAN, see 3GPP +9113 TS 23.271 [26a]. + +9114 GERAN GANSS Positioning Data + +9115 This parameter indicates the usage of each GANSS positioning method that was attempted to determine the location +9116 estimate either successfully or unsuccessfully. If GANSS Positioning Data received from the RAN contains no GANSS +9117 method, GERAN GANSS Positioning Data is excluded from the MAP message. It may be included in the message only +9118 if the access network is GERAN, see 3GPP TS 23.271 [26a]. + +9119 UTRAN GANSS Positioning Data + +9120 This parameter indicates the usage of each GANSS positioning method that was successfully attempted to determine the +9121 location estimate. If Position Data received from the RAN contains no GANSS Positioning Data Set, UTRAN GANSS +9122 Positioning Data is excluded from the MAP message. It may be included in the message only if the access network is +9123 UTRAN, see 3GPP TS 23.271 [26a]. + +9124 UTRAN Additional Positioning Data + +9125 This parameter indicates the usage of each Additional positioning method that was successfully attempted to determine +9126 the location estimate. If Position Data received from the RAN contains no Additional Positioning Data Set, UTRAN +9127 Additional Positioning Data is excluded from the MAP message. It may be included in the message only if the access +9128 network is UTRAN, see 3GPP TS 23.271 [26a]. + +9129 UTRAN Barometric Pressure Measurement + +9130 This parameter indicates the uncompensated barometric pressure measurement at the MS. The absence of this parameter +9131 implies that a barometric pressure measurement was not available or could not be successfully obtained. It may be +9132 included in the message only if the access network is UTRAN, see 3GPP TS 23.271 [26a]. + +9133 UTRAN Civic Address + +9134 This parameter indicates the civic address of the MS. The absence of this parameter implies that a civic address was not +9135 available or could not be successfully obtained. It may be included in the message only if the access network is +9136 UTRAN, see 3GPP TS 23.271 [26a]. + +9137 Age of Location Estimate + +9138 This parameter indicates how long ago the location estimate was obtained. + +9139 LMSI + +9140 The LMSI may be provided if assigned by the VLR. + +9141 GPRS Node Indicator + +9142 See definition in clause 7.6.8. This presence of this parameter is mandatory only if the SGSN number is sent in the +9143 Network Node Number. + +9144 Additional Location Estimate + +9145 This parameter provides the location estimate when not provided by the Location Estimate parameter.. + +9146 Deferred MT-LR Data + +9147 See definition in clause 7.6.11.3. + +9148 LCS-Reference Number + +9149 This parameter shall be included if the Subscriber Location Report is the response to a deferred MT location request. + +9150 NA-ESRK Request + +9151 If the target MS has originated an emergency service call in North America, NA-ESRK Request may be included to +9152 indicate that the MSC is able to accept NA-ESRK in the Response message, see clause 7.6.11.19. + +9153 Cell Id Or SAI + +9154 For GERAN access, this parameter indicates Global Cell Identifier of the cell that the served subscriber is currently +9155 attached to. For UTRAN access, this parameter contains the Service Area Identifier for the cell that the subscriber is +9156 currently attached to. This parameter is included only for Emergency Calls as described in 3GPP TS 23.271 [26a]. + +9157 H-GMLC address + +9158 See definition in clause 7.6.2. The parameter shall be included if the Subscriber Location Report is the response to a +9159 deferred MT location request for a UE available event, an area event or a periodic positioning event. This parameter +9160 shall be included in a Subscriber Location Report response if a deferred MO-LR TTTP procedure is initiated for a +9161 periodic positioning event. + +9162 LCS Service Type Id + +9163 See definition in clause 7.6.11.15. The requirements for its presence are specified in 3GPP TS 23.271 [26a]. + +9164 Pseudonym Indicator + +9165 This parameter indicates by its presence that the pseudonym is required. Refer to 3GPP TS 23.271 [26a]. + +9166 Accuracy Fulfilment Indicator + +9167 For a mobile terminated periodic LDR, this parameter indicates whether the obtained location estimate satisfies the +9168 requested accuracy or not, provided that this indication is obtained from RAN or the UE with the location estimate. + +9169 Periodic LDR Information + +9170 This parameter refers to the periodic reporting interval and reporting amount of the deferred periodic location. + +9171 MO-LR Short Circuit Indicator + +9172 This parameter indicates whether MO-LR Short Circuit is permitted for periodic location. + +9173 Reporting PLMN List + +9174 This parameter indicates a list of PLMNs in which subsequent periodic MO-LR TTTP requests will be made. + +9175 Sequence Number + +9176 This parameter refers to the number of the periodic location reports completed. The sequence number would be set to 1 +9177 in the first location report and increment by 1 for each new report. When the number reaches the reporting +9178 amount value, the H-GMLC (for a periodic MT-LR or a periodic MO-LR transfer to third party) will know the +9179 procedure is complete. For details see 3GPP TS 23.271 [26a]. + +9180 Target Serving Node for Handover + +9181 This parameter provides the address of the target side serving node for handover of an IMS Emergency Call. + +9182 User error + +9183 This parameter is sent by the responder when the received message contains an error, cannot be forwarded or stored for +9184 an LCS client or cannot be accepted for some other reason and if present, takes one of the following values defined in +9185 clause 7.6.1. + +- 9186 - System Failure; +- 9187 - Data Missing; +- 9188 - Unexpected Data Value; +- 9189 - Resource Limitation; +- 9190 - Unknown Subscriber; +- 9191 - Unauthorised requesting network; +- 9192 - Unknown or unreachable LCS Client. + +9193 Provider error + +9194 These are defined in clause 7.6.1. + +## 9195 13A.4 Void + +### 9196 13A.4.1 Void + +### 9197 13A.4.2 Void + +### 9198 13A.4.3 Void + +9199 **13A.5** Void + +9200 **13A.5.1** Void + +9201 **13A.5.2** Void + +9202 **13A.5.3** Void + +9203 **13A.6** Void + +9204 **13A.6.1** Void + +9205 **13A.6.2** Void + +9206 **13A.6.3** Void + +9207 **13A.7** Void + +9208 **13A.7.1** Void + +9209 **13A.7.2** Void + +9210 **13A.7.3** Void + +9211 **13A.8** Void + +9212 **13A.8.1** Void + +9213 **13A.8.2** Void + +9214 **13A.8.3** Void + +9215 **13A.9** Void + +9216 **13A.9.1** Void + +9217 **13A.9.2** Void + +9218 **13A.9.3** Void + +--- + +9219 **14** General + +9220 **14.1** Overview + +9221 Clauses 14 to 17 specify the protocol elements to be used to provide the MAP services described in clause 7. + +9222 Clause 15 specifies the elements of procedures for the MAP protocol. Clause 16 specifies the mapping onto TC service +9223 primitives. Clause 17 specifies the application contexts, operation packages and abstract syntaxes for the MAP protocol +9224 as well as the encoding rules to be applied. + +## 9225 14.2 Underlying services + +9226 The MAP protocol relies on the services provided by the Transaction Capabilities (TC) of Signalling System Number +9227 No. 7, as referenced in clause 6. + +## 9228 14.3 Model + +9229 The MAP Protocol Machine (MAP PM) can be modelled as a collection of service state machines (SSMs) - one per +9230 MAP specific service invoked - coordinated by a MAP dialogue control function with its one state machine: MAP +9231 dialogue state machine (DSM). There are two types of Service State Machines: Requesting Service State Machines +9232 (RSM) and Performing Service State Machines (PSM). + +9233 A new invocation of a MAP PM is employed on the receipt of a MAP-OPEN request primitive or a TC-BEGIN +9234 indication primitive. Each invocation controls exactly one MAP dialogue. For each MAP specific service invoked +9235 during a dialogue, a MAP RSM is created at the requestor's side and a MAP PSM is created at the performer's side. + +9236 This modelling is used only to facilitate understanding and the MAP behaviour descriptions and is not intended to +9237 suggest any implementation. SDL descriptions are organised according to this model. + +9238 How the MAP-service-user and the MAP refer to a MAP dialogue (i.e. a MAP PM invocation) is a local +9239 implementation matter. + +9240 How TC dialogue identifiers are assigned to a MAP PM invocation is also a local implementation matter. + +## 9241 14.4 Conventions + +9242 The behaviour of the MAP PM depends on the application-context-name associated with the dialogue. One major +9243 difference is that the MAP requests the transfer of the application-context-name by TC only for those contexts which do +9244 not belong to the so-called "version one context set". + +9245 The "version one context set" is a set of application-contexts which model the behaviour of a MAP V1 implementation +9246 according to the latest phase 1 version of GSM 09.02. This set is defined in clause 15. + +9247 The procedures described in clause 15 are used when the application-context-name does not refer to a dialogue between +9248 an MSC and its VLR. When the application-context-name refers to a dialogue between an MSC and its VLR the MAP +9249 PM procedures are a local implementation matter. + +--- + +## 9250 15 Elements of procedure + +### 9251 15.1 Handling of unknown operations + +9252 Unknown operations (i.e. a standard operation introduced in a later version of the MAP specification, or a private +9253 operation) can be introduced into MAP in a backwards compatible way. This means that the receiver of an unknown +9254 operation shall, if the dialogue state allows it, send a TC-REJECT component to the sender of the operation indicating +9255 'unrecognised operation' and continue with the processing of further components or messages exchanged within the +9256 dialogue as if the unknown operation had not been received. + +9257 The standardised structure of a MAP dialogue shall not be affected by the invocation of unknown operations, i.e. if a +9258 dialogue uses only a TC-BEGIN message which is acknowledged by a TC-END message, a TC-CONTINUE message +9259 shall not be used to invoke an unknown operation. However the standardised structure of a MAP dialogue may be +9260 affected by the rejection of unknown operations, i.e. if a dialogue uses only a TC-BEGIN message which is + +9261 acknowledged by a TC-END message, a TC-CONTINUE message followed by a TC-END message may be used to +9262 carry the rejection of an unknown operation and the response to the standardised operation. The entity which initiated a +9263 dialogue whose standardised structure is a TC-BEGIN message which is acknowledged by a TC-END message shall +9264 not send any messages in that dialogue after the TC-BEGIN. Note that if the dialogue structure is affected as described +9265 in this paragraph the TC-CONTINUE shall include the dialogue portion required to confirm the acceptance of the +9266 dialogue. + +9267 Unknown operations may be invoked in the following types of message (there is no restriction as to how many +9268 unknown operations can be invoked in a message): + +9269 - TC-BEGIN: the component to invoke the unknown operation shall follow the component of the standard +9270 operation which is included in this message. + +9271 - TC-CONTINUE: the component to invoke the unknown operation may be transported as the only component +9272 in a stand-alone message or may be grouped with existing operations. In the latter case a specific sequencing +9273 of components is not required. + +9274 - TC-END: if the component to invoke the unknown operation is grouped with an existing operation a specific +9275 sequencing of components is not required + +9276 The TC-REJECT component may be sent in the following messages: + +9277 - TC-CONTINUE or TC-END: either as the only component of the message or grouped with an existing +9278 component. The choice is up to the MAP-Service User. + +9279 If the received message contains only unknown operations the MAP-Service User shall send the TC-REJECT +9280 components in a TC-CONTINUE message to the peer entity, if the dialogue state allows it. + +9281 If the received message contains unknown operations and standard operations and the standardised structure +9282 of the dialogue requires the response to the standard operation to be sent within a TC-END message, then the +9283 MAP-Service User may send the response to the standard operations and the TC-REJECT components for +9284 the unknown operations in a TC-CONTINUE message followed by a TC-END message. Neither a specific +9285 distribution of the components to the TC messages nor a specific sequencing of components is required. + +9286 Note that the SDL diagrams of clauses 19 - 25 do not show the report to the MAP-Service User about the reception of +9287 the unknown operation. This has been done for simplicity of description; the MAP PM may inform the MAP-Service +9288 User. + +9289 The sender of the unknown operation shall ensure that there is enough room in the used message for the unknown +9290 operation. + +## 9291 15.2 Dialogue establishment + +9292 The establishment of a MAP dialogue involves two MAP-service-users: the dialogue-initiator and the dialogue- +9293 responder. + +9294 This procedure is driven by the following signals: + +9295 - a MAP-OPEN request primitive from the dialogue-initiator; + +9296 - a TC-BEGIN indication primitive occurring at the responding side; + +9297 - a MAP-OPEN response primitive from the dialogue-responder; + +9298 - the first TC-CONTINUE indication primitive occurring at the initiating side; + +9299 and under specific conditions: + +9300 - a TC-END indication primitive occurring at the initiating side; + +9301 - a TC-U-ABORT indication primitive occurring at the initiating side; + +9302 - a TC-P-ABORT indication primitive occurring at the initiating side. + +9303 One instance of the MAP dialogue state machine runs at the initiating side, and one at the responding side. + +## 9304 15.2.1 Behaviour at the initiating side + +9305 The behaviour of the MAP dialogue state machine at the initiating side is defined in sheets 1 – 8 of the process +9306 MAP\_DSM (figure 15.6/3). + +9307 Sheet 3: When the MAP dialogue state machine at the initiating side is waiting for a response from the responding side, +9308 a TC-END indication which echoes the AC name which was sent in the TC-BEGIN indicates acceptance of the +9309 dialogue. + +9310 Sheet 3: If the dialogue opening is accepted, any components included in the TC-END are processed and passed to the +9311 MAP-Service User. The dialogue is closed by sending a MAP-CLOSE to the MAP-Service User. + +9312 Sheet 3, sheet 4, sheet 5, sheet 6, sheet 7, sheet 8: when a dialogue is terminated, the MAP dialogue state machine +9313 terminates all instances of the Requesting\_MAP\_SSM which are active for this dialogue. + +9314 Sheet 4: A TC-P-ABORT with an abort parameter Incorrect\_Transaction\_Portion indicates that the responding side +9315 does not support a MAP version higher than 1. This triggers a MAP-OPEN confirm indicating that the dialogue is +9316 refused, with a refuse reason potential version incompatibility. The MAP-Service User may then decide to retry the +9317 dialogue at MAP version 1. + +9318 Sheet 8: When the MAP dialogue state machine at the initiating side is waiting for a response from the responding side, +9319 a TC-CONTINUE indication which echoes the AC name which was sent in the TC-BEGIN indicates acceptance of the +9320 dialogue. + +9321 Sheet 8: If the dialogue opening is accepted, any components included in the TC-CONTINUE are processed and passed +9322 to the MAP-Service User. The dialogue has then reached the established state. + +## 9323 15.2.2 Behaviour at the responding side + +9324 The behaviour of the MAP dialogue state machine at the responding side is defined in sheets 0 – 14 of the process +9325 MAP\_DSM (figure 15.6/3). + +9326 Sheet 9: If no application context information is included in the TC-BEGIN indication, this implies a MAP version 1 +9327 dialogue. An explicit application context indicating version 1 is treated as abnormal behaviour. + +9328 Sheet 11: The v1 application context name which corresponds to a v1 operation is derived using the information in table +9329 15.2/1. + +9330 **Table 15.2/1: Mapping of V1 operation codes on to application-context-names** + +| Operation | Application-context-name (note 1) | +|---------------------------------|------------------------------------------------------------| +| updateLocation | networkLocUpContext-v1 | +| cancelLocation | locationCancellationContext-v1 | +| provideRoamingNumber | roamingNumberEnquiryContext-v1 | +| insertSubscriberData | subscriberDataMngtContext-v1 | +| deleteSubscriberData | subscriberDataMngtContext-v1 | +| sendParameters | infoRetrievalContext-v1
networkLocUpContext-v1 (note 2) | +| beginSubscriberActivity | networkFunctionalSsContext-v1 | +| sendRoutingInfo | locationInfoRetrievalContext-v1 | +| performHandover | handoverControlContext-v1 | +| reset | resetContext-v1 | +| activateTraceMode | tracingContext-v1 | +| deactivateTraceMode | tracingContext-v1 | +| sendRoutingInfoForSM | shortMsgGatewayContext-v1 | +| forwardSM | shortMsgRelayContext-v1 | +| reportSM-deliveryStatus | shortMsgGatewayContext-v1 | +| noteSubscriberPresent | mwdMngtContext-v1 | +| alertServiceCentreWithoutResult | shortMsgAlertContext-v1 | +| checkIMEI | EquipmentMngtContext-v1 | + +9331 + +9332 NOTE 1: These symbolic names refer to the object identifier value defined in clause 17 and allocated to each +9333 application-context used for the MAP. + +9334 NOTE 2: The choice between the application contexts is based on the parameters received in the operation. + +9335 +9336 Sheet 12: If the dialogue is accepted, each component present in the TC-BEGIN is forwarded to an instance of a +9337 Performing\_MAP\_SSM, by executing the procedure Process\_Components. + +9338 Sheet 13: If the MAP dialogue state machine receives a MAP-OPEN response with a result accepted, it waits for any +9339 MAP specific service request or response primitives or a MAP-DELIMITER request. + +9340 Sheet 13, sheet 14: When a dialogue is terminated, the MAP dialogue state machine terminates all instances of the +9341 Requesting\_MAP\_SSM or Performing\_MAP\_SSM which are active for this dialogue. + +9342 Sheet 14: A MAP-DELIMITER request triggers a TC-CONTINUE request to accept the dialogue. The dialogue has +9343 then reached the established state. + +## 9344 15.3 Dialogue continuation + +9345 Once established the dialogue is said to be in a continuation phase. The behaviour of the MAP dialogue state machine in +9346 this phase is defined in sheets 15 – 17 of the process MAP\_DSM (figure 15.6/3). + +9347 Both MAP users can request the transfer of MAP APDUs until one of them requests the termination of the dialogue. + +9348 Normal closure of an established dialogue is shown on sheet 16; abnormal termination is shown on sheet 17. + +## 9349 15.4 Load control + +9350 If an entity which should respond to a MAP dialogue opening request is overloaded, it uses the AC of the request to +9351 determine whether to discard the request. + +9352 The priority level allocated to each application-context is described in clause 5, tables 5.1/1, 5.1/2, and 5.1/3. + +## 9353 15.5 Procedures for MAP specific services + +9354 This clause describes the MAP procedures for MAP specific services. These procedures are driven by the following +9355 types of event: + +9356 - a MAP specific request or a MAP specific response primitive; + +9357 - a component handling primitive from TC. + +9358 A Service State Machine is activated when of one of the following signals is received: + +9359 - a MAP request primitive, which activates a requesting SSM; + +9360 - a TC-INVOKED indication primitive without a linked identifier, which activates a performing SSM. + +9361 For component handling primitives there are two types of event: + +9362 - events which activate a Service State Machine or which can be related to an existing one; + +9363 - events which cannot be related to a Service State Machine. + +### 9364 15.5.1 Service invocation + +9365 The behaviour of the requesting SSM which handles a service is defined by the SDL for the process +9366 Requesting\_MAP\_SSM. The requesting SSM receives a MAP service request from the MAP-Service User via the MAP +9367 dialogue state machine and sends a TC-INVOKED request to TCAP. When a confirm is received from TCAP via the +9368 MAP dialogue state machine, the requesting SSM forwards a MAP service confirm to the MAP-Service User. + +9369 The response to a MAP service invocation may come in the form of a linked request. If the linked request corresponds +9370 to a class 4 operation, this is handled by the requesting SSM. If the linked request corresponds to a class 1, 2 or 3 + +9371 operation, the MAP dialogue state machine sends a notification to the requesting SSM and creates an instance of a +9372 performing SSM to handle the linked request. The test "Linked\_Operation\_Allowed" on sheet 3 of the process +9373 Requesting\_MAP\_SSM takes the (TRUE) exit if the definition of the parent operation includes the received linked +9374 operation as a permitted linked operation; otherwise the test takes the (FALSE) exit. + +9375 The mapping of MAP specific services on to remote operations is given in table 16.2/1. + +## 9376 15.5.2 Void + +## 9377 15.5.3 Service invocation receipt + +9378 The behaviour of the performing SSM which handles a service is defined by the SDL for the process +9379 Performing\_MAP\_SSM. The performing SSM receives a TC-INVOKE component from TCAP via the MAP dialogue +9380 state machine and sends a MAP service indication to the MAP-Service User. When a MAP service response is received +9381 from the MAP-Service User via the MAP dialogue state machine, the performing SSM forwards a TC-RESULT or TC- +9382 U-ERROR component to TCAP. + +## 9383 15.5.4 Void + +## 9384 15.5.5 Handling of components received from TC + +9385 The procedure Process\_Components shows the handling of components received in a TC-BEGIN, TC-CONTINUE or +9386 TC-END message. + +9387 Sheet 2: If a linked invoke component corresponds to a class 4 operation, the MAP dialogue state machine sends it to +9388 the requesting SSM instance identified by the linked invoke ID. If a linked invoke component corresponds to any other +9389 class of operation, the MAP dialogue state machine sends a notification to the requesting SSM instance identified by the +9390 linked invoke ID, creates an instance of a performing SSM and sends the invoke component to it. + +## 9391 15.6 SDL descriptions + +9392 The following SDL specification describes a system which includes three blocks: MAP-user, MAP-provider and TC. + +9393 Such a system resides in each network component supporting MAP and communicates with its peers via the lower +9394 layers of the signalling network which are part of the environment. + +9395 Only the MAP-provider is fully described in this clause. The various types of processes which form the MAP-User +9396 block and the TC block are described respectively in clauses 18 to 25 of the present document and in CCITT +9397 Recommendation Q.774. + +9398 The MAP-Provider block communicates with the MAP\_USER via two channels U1 and U2. Via U1 the MAP-provider +9399 receives the MAP request and response primitives. Via U2 it sends the MAP indication and confirm primitives. + +9400 The MAP-Provider block communicates with TC via two channels P1 and P2. Via P1 the MAP-Provider sends all the +9401 TC request primitives. Via P2 it receives all the TC indication primitives. + +9402 The MAP-Provider block is composed of the four following types of process: + +9403 a) MAP\_DSM: This type of process handles a dialogue for transport of MAP messages. There exists one +9404 process instance per MAP dialogue. + +9405 b) Load\_Ctrl: This type of process is in charge of load control. There is only one instance of this process in each +9406 system. + +9407 c) Requesting\_MAP\_SSM: This type of process handles a MAP service requested during a dialogue. An +9408 instance of this process is created by the instance of the MAP\_DSM process for each requested MAP service. + +9409 d) Performing\_MAP\_SSM: This type of process handles a MAP service performed during a dialogue. An +9410 instance of this process is created by the instance of the MAP\_DSM process for each MAP service to be +9411 performed. + +9412 A process MAP\_DSM exchanges external signals with other blocks as well as internal signals with the other processes +9413 of the MAP-Provider block. The external signals are either MAP service primitives or TC service primitives. + +9414 The signal routes used by the various processes are organised as follows: + +9415 a) A process MAP\_DSM receives and sends events from/to the MAP\_user via signal route User1/User2. These +9416 routes use channels U1 and U2 respectively. + +9417 b) A process MAP\_DSM receives and sends events from/to the TCAP via signal route TC1/TC2. These routes +9418 use channels P1 and P2 respectively. + +9419 c) A process MAP\_DSM receives and sends events from/to the LOAD\_CTRL process via signal route +9420 Load1/Load2. These routes are internal. + +9421 d) A process MAP\_DSM sends events to the Performing\_MAP\_SSM processes via signal route Intern1. This +9422 route is internal. + +9423 e) A process MAP\_DSM sends events to the Requesting\_MAP\_SSM processes via signal route Intern2. This +9424 route is internal. + +9425 f) A process Performing\_MAP\_SSM sends events to the MAP\_USER via signal route User3. This route uses +9426 channel U2. + +9427 g) A process Performing\_MAP\_SSM sends events to the TCAP via signal route TC3. This route uses channel +9428 P1. + +9429 h) A process Requesting\_MAP\_SSM sends events to the MAP\_USER via signal route User4. This route uses +9430 channel U2. + +9431 i) A process Requesting\_MAP\_SSM sends events to the TCAP via signal route TC4. This route uses channel +9432 P1. + +System MAP\_Stack + +Map\_Stack1(1) + +![Sequence diagram of System MAP_Stack showing interactions between MAP_USER, MAP Provider, and TCAP.](1fa646088a731bde9ff4c9af87f93d3c_img.jpg) + +``` +sequenceDiagram + participant MAP_USER + participant MAP_Provider as MAP Provider + participant TCAP + + Note left of MAP_USER: [u1] + MAP_USER->>MAP_Provider: (MAP_REQ_SM) + Note right of MAP_Provider: [u2] + MAP_Provider-->>MAP_USER: MAP_IND_SP + Note left of TCAP: [P1] + MAP_Provider->>TCAP: TC_REQ_SP + Note right of TCAP: [P2] + TCAP-->>MAP_Provider: TC_IND_SP +``` + +The diagram illustrates the interaction within the System MAP\_Stack. It features three main components: MAP\_USER, MAP Provider, and TCAP. The sequence of interactions is as follows: 1. MAP\_USER sends a request (MAP\_REQ\_SM) to the MAP Provider, labeled with [u1]. 2. The MAP Provider responds with an indication (MAP\_IND\_SP), labeled with [u2]. 3. The MAP Provider then sends a request (TC\_REQ\_SP) to the TCAP, labeled with [P1]. 4. Finally, the TCAP returns an indication (TC\_IND\_SP) to the MAP Provider, labeled with [P2]. + +Sequence diagram of System MAP\_Stack showing interactions between MAP\_USER, MAP Provider, and TCAP. + +Figure 15.6/1: System MAP\_Stack + +![Block diagram of MAPProvider (MAP_Provider1(1)) showing internal components: MAP_DSM, Load_Ctrl, Requesting_MAP_SSM, and Performing_MAP_SSM with their respective inputs and outputs.](e9b0c54f494f276491a59ab381f2e5b2_img.jpg) + +The diagram illustrates the internal structure of the **Block MAPProvider** (labeled **MAP\_Provider1(1)** in the top right). A small note icon is present in the top left corner. + +The main components and their connections are as follows: + +- MAP\_DSM** (top center): + - Inputs: **TC2** and **TC1** from the left; **User1** and **User2** from the right. + - Outputs: **TC1** to the left; **User2** to the right. + - Internal connections: **Load2** output to **Load\_Ctrl**; **Load1** input from **Load\_Ctrl**. + - External connections: **Intern2** output to **Requesting\_MAP\_SSM**; **Intern1** output to **Performing\_MAP\_SSM**. +- Load\_Ctrl** (middle center): + - Input: **Load2** from **MAP\_DSM**. + - Output: **Load1** to **MAP\_DSM**. +- Requesting\_MAP\_SSM** (bottom left): + - Input: **Intern2** from **MAP\_DSM**. + - Output: **TC4** to the left. + - Internal connection: **TC3** input from the bottom. +- Performing\_MAP\_SSM** (bottom right): + - Input: **Intern1** from **MAP\_DSM**. + - Output: **User3** to the right. + - Internal connection: **TC3** output to the bottom. +- External Connections:** + - TC3** (bottom left) connects to **User4** (bottom right). + - TC4** (bottom left) connects to **User3** (bottom right). + +Each signal line has a small empty box **[ ]** associated with it, likely for parameterization or configuration. + +Block diagram of MAPProvider (MAP\_Provider1(1)) showing internal components: MAP\_DSM, Load\_Ctrl, Requesting\_MAP\_SSM, and Performing\_MAP\_SSM with their respective inputs and outputs. + +9435 + +9436 + +Figure 15.6/2: Block MAP\_Provider + +# Process MAP\_DSM + +MAP\_DSM1(17) + +Process to manage a MAP dialogue + +Comment 'MAP Dialogue State Machine'; +DCL +Components\_Present, AC\_Name\_Unchanged, +AC\_Included, AC\_Supported, Invoke\_ID\_Active, Last\_Component, Operation\_Exists, +Alternative\_Name\_Exists, User\_Info\_Included BOOLEAN, +Op\_Code INTEGER; + +![State transition diagram for Process MAP_DSM](fb00a9ea622a6fe32404236fbf9b1b6a_img.jpg) + +``` +graph TD; Start([ ]) --> IDLE([IDLE]); IDLE --> MAP_OPEN_req{{MAP_OPEN_req}}; MAP_OPEN_req --> Store_AC_and_user_data[Store_AC_and_user_data]; Store_AC_and_user_data --> WAIT_FOR_USER_REQUESTS([WAIT_FOR_USER_REQUESTS]); Store_AC_and_user_data -.-> Note[For dialogue portion of TC-BEGIN]; +``` + +The diagram illustrates the state transitions for the Process MAP\_DSM. It begins with an initial state (oval), leading to the IDLE state (rounded rectangle). From IDLE, a transition labeled 'MAP\_OPEN\_req' (chevron) leads to the 'Store\_AC\_and\_user\_data' state (rectangle). This state is associated with a note 'For dialogue portion of TC-BEGIN'. Finally, a transition leads to the 'WAIT\_FOR\_USER\_REQUESTS' state (rounded rectangle). + +State transition diagram for Process MAP\_DSM + +9437 + +9438 + +Figure 15.6/3a: Process MAP\_DSM (sheet 1) + +Process MAP\_DSM + +MAP\_DSM2(17) + +Process to manage a MAP dialogue + +![State transition diagram for Process MAP_DSM. It starts at WAIT_FOR_USER_REQUESTS and branches into three paths: MAP_req (leading to Requesting_MAP_SSM, Service_Invoked_VIA_Intern2, and back to WAIT_FOR_USER_REQUESTS), MAP_DELIMITER_req (leading to TC_BEGIN_req_VIA_TC1 and DIALOGUE_INITIATED), and MAP_U_ABORT_req (leading to Set_Abort_Reason, Set_User_Info, TC_U_ABORT_req_VIA_TC1, Terminated_VIA_Intern2, IDLE, and To all active RSSMs).](bf9abec3605f1a8d00ae6524a9af02ed_img.jpg) + +``` +stateDiagram-v2 + [*] --> WAIT_FOR_USER_REQUESTS + WAIT_FOR_USER_REQUESTS --> MAP_req + WAIT_FOR_USER_REQUESTS --> MAP_DELIMITER_req + WAIT_FOR_USER_REQUESTS --> MAP_U_ABORT_req + MAP_req --> Requesting_MAP_SSM + Requesting_MAP_SSM --> Service_Invoked_VIA_Intern2 + Service_Invoked_VIA_Intern2 --> WAIT_FOR_USER_REQUESTS + MAP_DELIMITER_req --> TC_BEGIN_req_VIA_TC1 + TC_BEGIN_req_VIA_TC1 --> DIALOGUE_INITIATED + MAP_U_ABORT_req --> Set_Abort_Reason:User_Specific + Set_Abort_Reason:User_Specific --> Set_User_Info:MAP_User_Abort_PDU + Set_User_Info:MAP_User_Abort_PDU --> TC_U_ABORT_req_VIA_TC1 + TC_U_ABORT_req_VIA_TC1 --> Terminated_VIA_Intern2 + Terminated_VIA_Intern2 --> IDLE + Terminated_VIA_Intern2 --> To_all_active_RSSMs: To all active RSSMs +``` + +State transition diagram for Process MAP\_DSM. It starts at WAIT\_FOR\_USER\_REQUESTS and branches into three paths: MAP\_req (leading to Requesting\_MAP\_SSM, Service\_Invoked\_VIA\_Intern2, and back to WAIT\_FOR\_USER\_REQUESTS), MAP\_DELIMITER\_req (leading to TC\_BEGIN\_req\_VIA\_TC1 and DIALOGUE\_INITIATED), and MAP\_U\_ABORT\_req (leading to Set\_Abort\_Reason, Set\_User\_Info, TC\_U\_ABORT\_req\_VIA\_TC1, Terminated\_VIA\_Intern2, IDLE, and To all active RSSMs). + +9439 + +9440 + +Figure 15.6/3b: Process MAP\_DSM (sheet 2) + +Process MAP\_DSM + +MAP\_DSM3(17) + +Process to manage a MAP dialogue + +![State transition diagram for Process MAP_DSM. It starts at DIALOGUE_INITIATED and branches based on TC_END_ind and TC_NOTICE_ind signals. The main path involves setting results, opening via User2, checking components, closing via User2, and terminating via internal signals to reach an IDLE state. A sub-path handles 'Dialogue_Refused' and 'Node_Not_Reachable' cases.](933a097f8f087e901730352801e25555_img.jpg) + +``` + +stateDiagram-v2 + [*] --> DIALOGUE_INITIATED + DIALOGUE_INITIATED --> TC_END_ind + DIALOGUE_INITIATED --> TC_NOTICE_ind + TC_END_ind --> AC_Name_Unchanged + AC_Name_Unchanged -- (FALSE) --> 1 + AC_Name_Unchanged -- (TRUE) --> Set_Result_Accepted + Set_Result_Accepted --> MAP_OPEN_cnf_VIA_User2 + MAP_OPEN_cnf_VIA_User2 --> Components_Present + Components_Present -- (FALSE) --> MAP_CLOSE_ind_VIA_User2 + Components_Present -- (TRUE) --> Process_Components + Process_Components --> MAP_CLOSE_ind_VIA_User2 + MAP_CLOSE_ind_VIA_User2 --> Terminated_VIA_Intern1 + Terminated_VIA_Intern1 --> Terminated_VIA_Intern2 + Terminated_VIA_Intern2 --> IDLE + 1 --> Set_Provider_Reason + Set_Provider_Reason --> MAP_P_ABORT_ind_VIA_User2 + TC_NOTICE_ind --> Set_Result_Refused + Set_Result_Refused --> Set_Refuse_Reason + Set_Refuse_Reason --> MAP_OPEN_cnf_VIA_User2 + MAP_P_ABORT_ind_VIA_User2 --> IDLE + MAP_OPEN_cnf_VIA_User2 --> Terminated_VIA_Intern2 + Terminated_VIA_Intern2 --> IDLE + Terminated_VIA_Intern1 --> To_all_active_PSSMs + Terminated_VIA_Intern2 --> To_all_active_RSSMs + Terminated_VIA_Intern2 --> To_all_active_RSSMs + +``` + +State transition diagram for Process MAP\_DSM. It starts at DIALOGUE\_INITIATED and branches based on TC\_END\_ind and TC\_NOTICE\_ind signals. The main path involves setting results, opening via User2, checking components, closing via User2, and terminating via internal signals to reach an IDLE state. A sub-path handles 'Dialogue\_Refused' and 'Node\_Not\_Reachable' cases. + +9441 + +9442 + +Figure 15.6/3c: Process MAP\_DSM (sheet 3) + +Process MAP\_DSM + +MAP\_DSM4(17) + +Process to manage a MAP dialogue + +![State transition diagram for Process MAP_DSM. It starts at DIALOGUE_INITIATED, goes through TC_P_ABORT_ind, then a P-Abort_Parameter decision. The decision has three paths: 'Incorrect_Transaction_Portion' leads to Set_Result: Dialogue_Refused; 'No_Common_Dialogue_Portion' leads to Set_Provider_Reason: Version_Incompatibility; 'Else' also leads to Set_Provider_Reason: Version_Incompatibility. Both Set_Result and Set_Provider_Reason lead to MAP_P_ABORT_ind_VIA_User2. From there, the flow goes to Terminated_VIA_Intern2, which then leads to IDLE. There are also callouts 'To all active RSSMs' from both Terminated_VIA_Intern2 blocks.](a9858b877d4da8ec2e81be7a7a50dd00_img.jpg) + +``` + +stateDiagram-v2 + [*] --> DIALOGUE_INITIATED + DIALOGUE_INITIATED --> TC_P_ABORT_ind + TC_P_ABORT_ind --> P-Abort_Parameter + P-Abort_Parameter --> Set_Result: Dialogue_Refused : Incorrect_Transaction_Portion + P-Abort_Parameter --> Set_Provider_Reason: Version_Incompatibility : No_Common_Dialogue_Portion + P-Abort_Parameter --> Set_Provider_Reason: Version_Incompatibility : Else + Set_Result: Dialogue_Refused --> Set_Refuse_Reason: Potential_Version_Incompatibility + Set_Refuse_Reason: Potential_Version_Incompatibility --> MAP_OPEN_cnf_VIA_User2 + MAP_OPEN_cnf_VIA_User2 --> Terminated_VIA_Intern2 + Terminated_VIA_Intern2 --> IDLE + Set_Provider_Reason: Version_Incompatibility --> MAP_P_ABORT_ind_VIA_User2 + MAP_P_ABORT_ind_VIA_User2 --> Terminated_VIA_Intern2 + Terminated_VIA_Intern2 --> IDLE + +``` + +State transition diagram for Process MAP\_DSM. It starts at DIALOGUE\_INITIATED, goes through TC\_P\_ABORT\_ind, then a P-Abort\_Parameter decision. The decision has three paths: 'Incorrect\_Transaction\_Portion' leads to Set\_Result: Dialogue\_Refused; 'No\_Common\_Dialogue\_Portion' leads to Set\_Provider\_Reason: Version\_Incompatibility; 'Else' also leads to Set\_Provider\_Reason: Version\_Incompatibility. Both Set\_Result and Set\_Provider\_Reason lead to MAP\_P\_ABORT\_ind\_VIA\_User2. From there, the flow goes to Terminated\_VIA\_Intern2, which then leads to IDLE. There are also callouts 'To all active RSSMs' from both Terminated\_VIA\_Intern2 blocks. + +9443 + +9444 + +Figure 15.6/3d: Process MAP\_DSM (sheet 4) + +Process MAP\_DSM + +MAP\_DSM5(17) + +Process to manage a MAP dialogue + +![State transition diagram for Process MAP_DSM. It starts at DIALOGUE_INITIATED and branches into TC_U_ABORT_ind and TC_L_CANCEL_ind. The TC_U_ABORT_ind path leads to an Abort_Reason decision, which can lead to state 4, a dialogue refusal sequence, or back to DIALOGUE_INITIATED. The TC_L_CANCEL_ind path leads to MAP_OPEN_cnf_VIA_User2, then to an invoke_ID_Active decision, which can lead to a timer expiry or back to DIALOGUE_INITIATED.](a2763753bfc5fc69f0694c695973cd40_img.jpg) + +``` + +stateDiagram-v2 + [*] --> DIALOGUE_INITIATED + DIALOGUE_INITIATED --> TC_U_ABORT_ind + DIALOGUE_INITIATED --> TC_L_CANCEL_ind + TC_U_ABORT_ind --> Abort_Reason + Abort_Reason --> 4 : User_Specific + Abort_Reason --> Set_Result : AC_Not_Supported + Set_Result --> Set_Refuse_Reason : Dialogue_Refused + Set_Refuse_Reason --> MAP_OPEN_cnf_VIA_User2 + MAP_OPEN_cnf_VIA_User2 --> Terminated : To all active RSSMs + Terminated --> IDLE + TC_L_CANCEL_ind --> MAP_OPEN_cnf_VIA_User2 + MAP_OPEN_cnf_VIA_User2 --> invoke_ID_Active + invoke_ID_Active --> Timer_Expiry : (TRUE) + invoke_ID_Active --> DIALOGUE_INITIATED : (FALSE) + Timer_Expiry --> DIALOGUE_INITIATED + +``` + +Accepted. The dialogue is considered implicitly accepted when something is received + +State transition diagram for Process MAP\_DSM. It starts at DIALOGUE\_INITIATED and branches into TC\_U\_ABORT\_ind and TC\_L\_CANCEL\_ind. The TC\_U\_ABORT\_ind path leads to an Abort\_Reason decision, which can lead to state 4, a dialogue refusal sequence, or back to DIALOGUE\_INITIATED. The TC\_L\_CANCEL\_ind path leads to MAP\_OPEN\_cnf\_VIA\_User2, then to an invoke\_ID\_Active decision, which can lead to a timer expiry or back to DIALOGUE\_INITIATED. + +9445 + +9446 + +Figure 15.6/3e: Process MAP\_DSM (sheet 5) + +Process MAP\_DSM + +MAP\_DSM6(17) + +Process to manage a MAP dialogue + +![State transition diagram for Process MAP_DSM. It starts at a circle labeled '4', leading to a decision diamond 'User_Information'. From 'User_Information', four paths emerge: 'User_Abort_PDU' (leading to 'MAP_P_ABORT_ind_VIA_User2'), 'Provider_Abort_PDU' (leading to 'MAP_P_ABORT_ind_VIA_User2'), 'Dialogue_Refused' (leading to 'Set_Result: Dialogue_Refused' then 'MAP Refuse_PDU_Error'), and 'No_User_Info' (leading to 'Set_Result: Dialogue_Refused'). 'MAP Refuse_PDU_Error' has three sub-paths: 'Invalid_Destination_Reference' (leading to 'Set_Refuse_Reason: Invalid_Destination_Reference'), 'Invalid_Originating_Reference' (leading to 'Set_Refuse_Reason: Invalid_Originating_Reference'), and 'No_Reason_Given' (leading to 'Set_Refuse_Reason: No_Reason_Given'). These three paths merge at a junction. From this junction, one path leads to 'MAP_OPEN_cnf_VIA_User2' and another leads to 'Set_Refuse_Reason: Potential_Version_Incompatibility'. All three paths ('MAP_OPEN_cnf_VIA_User2', 'Set_Refuse_Reason: Potential_Version_Incompatibility', and the merged path from the junction) lead to a decision diamond 'Terminated_VIA_Intern2'. 'Terminated_VIA_Intern2' has a dashed box 'To all active RSSMs' and leads to an oval 'IDLE' state.](d1203e87a330a98abf08c99d65e5a24b_img.jpg) + +``` + +stateDiagram-v2 + [*] --> User_Information + User_Information --> User_Abort_PDU + User_Information --> Provider_Abort_PDU + User_Information --> Dialogue_Refused + User_Information --> No_User_Info + User_Abort_PDU --> MAP_P_ABORT_ind_VIA_User2 + Provider_Abort_PDU --> MAP_P_ABORT_ind_VIA_User2 + Dialogue_Refused --> Set_Result_Dialogue_Refused + No_User_Info --> Set_Result_Dialogue_Refused + Set_Result_Dialogue_Refused --> MAP_Refuse_PDU_Error + MAP_Refuse_PDU_Error --> Invalid_Destination_Reference + MAP_Refuse_PDU_Error --> Invalid_Originating_Reference + MAP_Refuse_PDU_Error --> No_Reason_Given + Invalid_Destination_Reference --> Set_Refuse_Reason_Invalid_Destination_Reference + Invalid_Originating_Reference --> Set_Refuse_Reason_Invalid_Originating_Reference + No_Reason_Given --> Set_Refuse_Reason_No_Reason_Given + Set_Refuse_Reason_Invalid_Destination_Reference --> Junction + Set_Refuse_Reason_Invalid_Originating_Reference --> Junction + Set_Refuse_Reason_No_Reason_Given --> Junction + Junction --> MAP_OPEN_cnf_VIA_User2 + Junction --> Set_Refuse_Reason_Potential_Version_Incompatibility + Set_Refuse_Reason_Potential_Version_Incompatibility --> Junction + MAP_OPEN_cnf_VIA_User2 --> Terminated_VIA_Intern2 + Set_Refuse_Reason_Potential_Version_Incompatibility --> Terminated_VIA_Intern2 + Terminated_VIA_Intern2 --> To_all_active_RSSMs + Terminated_VIA_Intern2 --> IDLE + +``` + +State transition diagram for Process MAP\_DSM. It starts at a circle labeled '4', leading to a decision diamond 'User\_Information'. From 'User\_Information', four paths emerge: 'User\_Abort\_PDU' (leading to 'MAP\_P\_ABORT\_ind\_VIA\_User2'), 'Provider\_Abort\_PDU' (leading to 'MAP\_P\_ABORT\_ind\_VIA\_User2'), 'Dialogue\_Refused' (leading to 'Set\_Result: Dialogue\_Refused' then 'MAP Refuse\_PDU\_Error'), and 'No\_User\_Info' (leading to 'Set\_Result: Dialogue\_Refused'). 'MAP Refuse\_PDU\_Error' has three sub-paths: 'Invalid\_Destination\_Reference' (leading to 'Set\_Refuse\_Reason: Invalid\_Destination\_Reference'), 'Invalid\_Originating\_Reference' (leading to 'Set\_Refuse\_Reason: Invalid\_Originating\_Reference'), and 'No\_Reason\_Given' (leading to 'Set\_Refuse\_Reason: No\_Reason\_Given'). These three paths merge at a junction. From this junction, one path leads to 'MAP\_OPEN\_cnf\_VIA\_User2' and another leads to 'Set\_Refuse\_Reason: Potential\_Version\_Incompatibility'. All three paths ('MAP\_OPEN\_cnf\_VIA\_User2', 'Set\_Refuse\_Reason: Potential\_Version\_Incompatibility', and the merged path from the junction) lead to a decision diamond 'Terminated\_VIA\_Intern2'. 'Terminated\_VIA\_Intern2' has a dashed box 'To all active RSSMs' and leads to an oval 'IDLE' state. + +9447 + +9448 + +Figure 15.6/3f: Process MAP\_DSM (sheet 6) + +Process MAP\_DSM + +MAP\_DSM7(17) + +Process to manage a MAP dialogue + +![State transition diagram for Process MAP_DSM. It starts at DIALOGUE_INITIATED and branches into two paths: one for MAP_U_ABORT_req (Local) and one for MAP_CLOSE_req (Pre-arranged). Both paths lead to TC_*_req_VIA_TC1, which then lead to Terminated_VIA_Intern2 and finally to IDLE. The MAP_U_ABORT_req path includes Set_Abort_Reason: User_Specific and Set_User_Info: MAP_User_Abort_Info.](00bb8c9fd2ec7fa7da34a98f824468b6_img.jpg) + +``` +graph TD; DIALOGUE_INITIATED([DIALOGUE_INITIATED]) --> MAP_U_ABORT_req{{MAP_U_ABORT_req}}; DIALOGUE_INITIATED --> MAP_CLOSE_req{{MAP_CLOSE_req}}; MAP_U_ABORT_req --> Set_Abort_Reason[Set_Abort_Reason: User_Specific]; Set_Abort_Reason --> Set_User_Info[Set_User_Info: MAP_User_Abort_Info]; Set_User_Info --> TC_U_ABORT_req_VIA_TC1{{TC_U_ABORT_req_VIA_TC1}}; TC_U_ABORT_req_VIA_TC1 --> Terminated_VIA_Intern2{{Terminated_VIA_Intern2}}; Terminated_VIA_Intern2 --> IDLE([IDLE]); MAP_CLOSE_req --> TC_END_req_VIA_TC1{{TC_END_req_VIA_TC1}}; TC_END_req_VIA_TC1 --> Terminated_VIA_Intern2; Local[Local] -.-> TC_U_ABORT_req_VIA_TC1; Pre-arranged[Pre-arranged] -.-> TC_END_req_VIA_TC1; To_all_active_RSSMs[To all active RSSMs] -.-> Terminated_VIA_Intern2 +``` + +State transition diagram for Process MAP\_DSM. It starts at DIALOGUE\_INITIATED and branches into two paths: one for MAP\_U\_ABORT\_req (Local) and one for MAP\_CLOSE\_req (Pre-arranged). Both paths lead to TC\_\*\_req\_VIA\_TC1, which then lead to Terminated\_VIA\_Intern2 and finally to IDLE. The MAP\_U\_ABORT\_req path includes Set\_Abort\_Reason: User\_Specific and Set\_User\_Info: MAP\_User\_Abort\_Info. + +9449 + +9450 + +Figure 15.6/3g: Process MAP\_DSM (sheet 7) + +Process MAP\_DSM + +MAP\_DSM8(17) + +Process to manage +a MAP dialogue + +![SDL process diagram for MAP_DSM showing the flow from DIALOGUE_INITIATED to either DIALOGUE_ESTABLISHED or IDLE based on AC_Name_Unchanged and Components_Present decisions.](524bf86b6b42612b7ec0d0a04b04a708_img.jpg) + +``` + +graph TD + Start([DIALOGUE_INITIATED]) --> TC_Ind[/TC_CONTINUE_ind/] + TC_Ind --- Comment1[The first one] + TC_Ind --> Decision1{AC_Name_Unchanged} + + Decision1 -- "(TRUE)" --> Task1[Set_Result: +Dialogue_ +Accepted] + Task1 --> Output1[/MAP_OPEN_ +cnf_VIA_User2/] + Output1 --> Decision2{Components_ +Present} + + Decision2 -- "(TRUE)" --> Proc1[[Process_ +Components]] + Proc1 --> Output2[/MAP_ +DELIMITER_ +req_VIA_User2/] + Output2 --> End1([DIALOGUE_ +ESTABLISHED]) + + Decision2 -- "(FALSE)" --> End1 + + Decision1 -- "(FALSE)" --> Conn2((2)) + Conn2 --> Task2[Set_MAP_Provider_ +Abort_Reason: +Abnormal_Dialogue] + Task2 --> Output3[/MAP_P_ABORT_ +ind_VIA_User2/] + Output3 --> Task3[Set_Abort_Reason_ +User_Specific] + Task3 --> Task4[Set_User_Information: +MAP_Provider_ +Abort_Info] + Task4 --- Comment2[MAP_Provider_ +Abort_Reason:= +Abnormal_Dialogue] + Task4 --> Output4[/TC_U_ABORT_ +req_VIA_TC1/] + Output4 --> Output5[/Terminated_ +VIA_Intern2/] + Output5 --- Comment3[To all active +RSSMs] + Output5 --> End2([IDLE]) + +``` + +SDL process diagram for MAP\_DSM showing the flow from DIALOGUE\_INITIATED to either DIALOGUE\_ESTABLISHED or IDLE based on AC\_Name\_Unchanged and Components\_Present decisions. + +9451 + +9452 + +Figure 15.6/3h: Process MAP\_DSM (sheet 8) + +Process MAP\_DSM + +MAP\_DSM9(17) + +Process to manage a MAP dialogue + +![Flowchart for Process MAP_DSM starting from IDLE state, through TC_BEGIN_ind, AC_included, AC_Vession, MAP_Dialogue_PDU included, Extract_User_Information, MAP-OPEN dialogue PDU?, User_Info required for AC?, Invalid Parameter?, Check_Load_VIA_Load1, TC_U_ABORT req_VIA_TC1, and ending in various states like WAIT_FOR_LOAD_CHECK_RESULT1, IDLE, and WAIT_FOR_INIT_DATA.](ca2740c55eeb32272b09a48cdfb7ee4d_img.jpg) + +``` + +graph TD + IDLE1([IDLE]) --> TC_BEGIN_ind[/TC_BEGIN_ind/] + TC_BEGIN_ind --> AC_included{AC_included} + AC_included -- (FALSE) --> Components_Present{Components_Present} + AC_included -- (TRUE) --> AC_Vession{AC_Vession = 1} + AC_Vession -- (FALSE) --> MAP_Dialogue_PDU_included{MAP_Dialogue_PDU_included} + AC_Vession -- (TRUE) --> Components_Present + MAP_Dialogue_PDU_included -- (FALSE) --> User_Info_required{User_Info required for AC?} + MAP_Dialogue_PDU_included -- (TRUE) --> Extract_User_Information[Extract_User_Information] + Extract_User_Information --> MAP_OPEN_dialogue_PDU{MAP-OPEN dialogue PDU?} + MAP_OPEN_dialogue_PDU -- No --> Junction(( )) + MAP_OPEN_dialogue_PDU -- Yes --> Invalid_Parameter{Invalid Parameter?} + Invalid_Parameter -- No --> Check_Load_VIA_Load1[/Check_Load_VIA_Load1/] + Invalid_Parameter -- Yes --> Junction + User_Info_required -- Yes --> Connector3((3)) + User_Info_required -- No --> Junction + Components_Present -- (FALSE) --> TC_U_ABORT_req_VIA_TC1[/TC_U_ABORT req_VIA_TC1/] + Components_Present -- (TRUE) --> WAIT_FOR_INIT_DATA([WAIT_FOR_INIT_DATA]) + TC_U_ABORT_req_VIA_TC1 --> IDLE2([IDLE]) + Check_Load_VIA_Load1 --> WAIT_FOR_LOAD_CHECK_RESULT1([WAIT_FOR_LOAD_CHECK_RESULT1]) + Junction --> Connector3 + +``` + +Flowchart for Process MAP\_DSM starting from IDLE state, through TC\_BEGIN\_ind, AC\_included, AC\_Vession, MAP\_Dialogue\_PDU included, Extract\_User\_Information, MAP-OPEN dialogue PDU?, User\_Info required for AC?, Invalid Parameter?, Check\_Load\_VIA\_Load1, TC\_U\_ABORT req\_VIA\_TC1, and ending in various states like WAIT\_FOR\_LOAD\_CHECK\_RESULT1, IDLE, and WAIT\_FOR\_INIT\_DATA. + +9453 + +9454 + +Figure 15.6/3i: Process MAP\_DSM (sheet 9) + +# Process MAP\_DSM + +MAP\_DSM10(17) + +Process to manage a MAP dialogue + +![Flowchart for Process MAP_DSM](07ccb21f70641797dd02a891ced72b7e_img.jpg) + +``` +graph TD; Start((3)) --> Step1[Set_MAP_Provider_ Abort_Reason: Abnormal_Dialogue]; Step1 --> Step2[Set_User_Info: MAP_Provider_ Abort_Info]; Step2 --> Step3[Set_Abort_Reason: User_Specific]; Step3 --> Decision{TC_U_ABORT req_VIA_TC1}; Decision --> End([IDLE]); +``` + +The flowchart illustrates the process for managing a MAP dialogue. It begins with a start node labeled '3'. The first step is 'Set\_MAP\_Provider\_ Abort\_Reason: Abnormal\_Dialogue'. This is followed by 'Set\_User\_Info: MAP\_Provider\_ Abort\_Info'. The next step is 'Set\_Abort\_Reason: User\_Specific'. A decision node follows, labeled 'TC\_U\_ABORT req\_VIA\_TC1'. The final state is 'IDLE'. + +Flowchart for Process MAP\_DSM + +9455 + +9456 + +Figure 15.6/3j: Process MAP\_DSM (sheet 10) + +# Process MAP\_DSM + +MAP\_DSM11(17) + +Process to manage a MAP dialogue + +![State transition diagram for Process MAP_DSM. It shows two main state machines. The left one starts at WAIT_FOR_INIT_DATA and transitions based on TC_INVOKE_ind, TC_L_REJECT_ind, or Any_OTHER_ind. The right one starts at WAIT_FOR_LOAD_CHECK_RESULT2 and transitions based on Load_OK or Overload. Both lead to IDLE states.](e4b6ed98fad76b79cb9f85783e13086a_img.jpg) + +``` + +stateDiagram-v2 + [*] --> WAIT_FOR_INIT_DATA + WAIT_FOR_INIT_DATA --> TC_INVOKE_ind {Op_Code} + WAIT_FOR_INIT_DATA --> TC_L_REJECT_ind + WAIT_FOR_INIT_DATA --> Any_OTHER_ind + TC_INVOKE_ind --> Operation_Exists {Operation_Exists} + Operation_Exists -- (TRUE) --> Derive_V1_AC + Derive_V1_AC --> Check_Load_VIA_Load1 + Check_Load_VIA_Load1 --> WAIT_FOR_LOAD_CHECK_RESULT2 + Operation_Exists -- (FALSE) --> Any_OTHER_ind + TC_L_REJECT_ind --> Any_OTHER_ind + Any_OTHER_ind --> TC_U_ABORT_req_VIA_TC1 + TC_U_ABORT_req_VIA_TC1 --> IDLE + + [*] --> WAIT_FOR_LOAD_CHECK_RESULT2 + WAIT_FOR_LOAD_CHECK_RESULT2 --> Load_OK + WAIT_FOR_LOAD_CHECK_RESULT2 --> Overload + Overload --> IDLE + Load_OK --> Op_Code {Op_Code} + Op_Code -- ELSE --> begin_subscriber_activity + Op_Code -- begin_subscriber_activity --> Last_Component {Last_Component} + Last_Component -- (TRUE) --> TC_U_ABORT_req_VIA_TC1 + Last_Component -- (FALSE) --> Build_MAP_OPEN_ind_Primitive + TC_U_ABORT_req_VIA_TC1 --> IDLE + Build_MAP_OPEN_ind_Primitive --> MAP_OPEN_ind_VIA_User2 + MAP_OPEN_ind_VIA_User2 --> Perform_version_1_protocol + Perform_version_1_protocol --> IDLE + +``` + +State transition diagram for Process MAP\_DSM. It shows two main state machines. The left one starts at WAIT\_FOR\_INIT\_DATA and transitions based on TC\_INVOKE\_ind, TC\_L\_REJECT\_ind, or Any\_OTHER\_ind. The right one starts at WAIT\_FOR\_LOAD\_CHECK\_RESULT2 and transitions based on Load\_OK or Overload. Both lead to IDLE states. + +9457 + +9458 + +Figure 15.6/3k: Process MAP\_DSM (sheet 11) + +Process MAP\_DSM + +MAP\_DSM12(17) + +Process to manage a MAP dialogue + +![State transition diagram for Process MAP_DSM. It starts with WAIT_FOR_LOAD_CHECK_RESULT1, leading to Load_OK and Overload. Overload leads to IDLE. Load_OK leads to AC_Supported decision. AC_Supported (TRUE) leads to AC_Name:= Received_AC_Name, then Set_User_Data, then MAP_OPEN_ind_VIA_User2. AC_Supported (FALSE) leads to Alternative_Name_Exists decision. Alternative_Name_Exists (TRUE) leads to AC_Name:= Alternative_AC_Name, then TC_U_ABORT_req_VIA_TC1, then IDLE. Alternative_Name_Exists (FALSE) leads to AC_Name:= Received_AC_Name, then MAP_OPEN_ind_VIA_User2. MAP_OPEN_ind_VIA_User2 leads to Components_Present decision. Components_Present (TRUE) leads to Process_Components, then MAP_DELIMITER_ind_VIA_User2, then DIALOGUE_PENDING. Components_Present (FALSE) leads to MAP_DELIMITER_ind_VIA_User2.](9997ce2599510a8912ccac15865ae602_img.jpg) + +``` + +stateDiagram-v2 + [*] --> WAIT_FOR_LOAD_CHECK_RESULT1 + WAIT_FOR_LOAD_CHECK_RESULT1 --> Load_OK + WAIT_FOR_LOAD_CHECK_RESULT1 --> Overload + Overload --> IDLE + Load_OK --> AC_Supported + AC_Supported --> AC_Name_1[AC_Name:= Received_AC_Name] : (TRUE) + AC_Supported --> Alternative_Name_Exists : (FALSE) + AC_Name_1 --> Set_User_Data + Set_User_Data --> MAP_OPEN_ind_VIA_User2 + Alternative_Name_Exists --> AC_Name_2[AC_Name:= Received_AC_Name] : (FALSE) + Alternative_Name_Exists --> AC_Name_3[AC_Name:= Alternative_AC_Name] : (TRUE) + AC_Name_2 --> MAP_OPEN_ind_VIA_User2 + AC_Name_3 --> TC_U_ABORT_req_VIA_TC1 + TC_U_ABORT_req_VIA_TC1 --> IDLE + MAP_OPEN_ind_VIA_User2 --> Components_Present + Components_Present --> Process_Components : (TRUE) + Components_Present --> MAP_DELIMITER_ind_VIA_User2 : (FALSE) + Process_Components --> MAP_DELIMITER_ind_VIA_User2 + MAP_DELIMITER_ind_VIA_User2 --> DIALOGUE_PENDING + +``` + +State transition diagram for Process MAP\_DSM. It starts with WAIT\_FOR\_LOAD\_CHECK\_RESULT1, leading to Load\_OK and Overload. Overload leads to IDLE. Load\_OK leads to AC\_Supported decision. AC\_Supported (TRUE) leads to AC\_Name:= Received\_AC\_Name, then Set\_User\_Data, then MAP\_OPEN\_ind\_VIA\_User2. AC\_Supported (FALSE) leads to Alternative\_Name\_Exists decision. Alternative\_Name\_Exists (TRUE) leads to AC\_Name:= Alternative\_AC\_Name, then TC\_U\_ABORT\_req\_VIA\_TC1, then IDLE. Alternative\_Name\_Exists (FALSE) leads to AC\_Name:= Received\_AC\_Name, then MAP\_OPEN\_ind\_VIA\_User2. MAP\_OPEN\_ind\_VIA\_User2 leads to Components\_Present decision. Components\_Present (TRUE) leads to Process\_Components, then MAP\_DELIMITER\_ind\_VIA\_User2, then DIALOGUE\_PENDING. Components\_Present (FALSE) leads to MAP\_DELIMITER\_ind\_VIA\_User2. + +9459 + +9460 + +Figure 15.6/31: Process MAP\_DSM (sheet 12) + +Process MAP\_DSM + +MAP\_DSM13(17) + +Process to manage a MAP dialogue + +![State transition diagram for Process MAP_DSM. It starts at DIALOGUE_PENDING, branches into MAP_OPEN_rsp and MAP_U_ABORT_req. MAP_OPEN_rsp leads to a Result decision (Accepted to DIALOGUE_ACCEPTED, Refused to Set_Abort_Reason). MAP_U_ABORT_req leads to Set_Abort_Reason and Set_User_Info, then to TC_U_ABORT_req_VIA_TC1. Both paths lead to Terminated_VIA_Intern1 and then to IDLE.](d1aa8db844a6bb8519d74e48d1cf5343_img.jpg) + +``` +stateDiagram-v2 + [*] --> DIALOGUE_PENDING + DIALOGUE_PENDING --> MAP_OPEN_rsp + DIALOGUE_PENDING --> MAP_U_ABORT_req + MAP_OPEN_rsp --> Result + Result -- Accepted --> DIALOGUE_ACCEPTED + Result -- Refused --> Set_Abort_Reason_1[Set_Abort_Reason: User_Specific] + MAP_U_ABORT_req --> Set_Abort_Reason_2[Set_Abort_Reason: User_Specific] + Set_Abort_Reason_2 --> Set_User_Info[Set_User_Info: MAP_User_Abort_Info] + Set_Abort_Reason_1 --> Build_MAP_Refuse_PDU[Build_MAP_Refuse_PDU] + Set_User_Info --> TC_U_ABORT_req_VIA_TC1{TC_U_ABORT_req_VIA_TC1} + Build_MAP_Refuse_PDU --> TC_U_ABORT_req_VIA_TC1 + TC_U_ABORT_req_VIA_TC1 --> Terminated_VIA_Intern1[Terminated_VIA_Intern1] + Terminated_VIA_Intern1 --> IDLE + Terminated_VIA_Intern1 -- To all active PSSMs +``` + +State transition diagram for Process MAP\_DSM. It starts at DIALOGUE\_PENDING, branches into MAP\_OPEN\_rsp and MAP\_U\_ABORT\_req. MAP\_OPEN\_rsp leads to a Result decision (Accepted to DIALOGUE\_ACCEPTED, Refused to Set\_Abort\_Reason). MAP\_U\_ABORT\_req leads to Set\_Abort\_Reason and Set\_User\_Info, then to TC\_U\_ABORT\_req\_VIA\_TC1. Both paths lead to Terminated\_VIA\_Intern1 and then to IDLE. + +9461 + +9462 + +Figure 15.6/3m: Process MAP\_DSM (sheet 13) + +Process MAP\_DSM + +MAP\_DSM14(17) + +Process to manage a MAP dialogue + +![State transition diagram for Process MAP_DSM. It starts at DIALOGUE_ACCEPTED and branches into three paths: MAP_req (leading to Requesting_MAP_SSM, Service_Invoked_VIA_Intern2, and then DIALOGUE_ACCEPTED), MAP_rsp (leading to Response_Issued_VIA_Intern1 and then DIALOGUE_ACCEPTED), and MAP_DELIMITER_req (leading to TC_CONTINUE_req_VIA_TC1 and then DIALOGUE_ESTABLISHED). From the second DIALOGUE_ACCEPTED state, it branches into MAP_CLOSE_req (leading to TC_END_req_VIA_TC1) and MAP_U_ABORT_req (leading to Set_Abort_Reason: User_Specific, User_Info:= MAP-UserAbortInfo, and then TC_U_ABORT_req_VIA_TC1). Both TC_END_req_VIA_TC1 and TC_U_ABORT_req_VIA_TC1 lead to a common path of Terminated_VIA_Intern1 (To all active PSSMs) and Terminated_VIA_Intern2 (To all active RSSMs), which finally leads to the IDLE state.](d33209b2cda1d21b3db2a2b0382a4c05_img.jpg) + +``` + +stateDiagram-v2 + [*] --> DIALOGUE_ACCEPTED + DIALOGUE_ACCEPTED --> MAP_req + DIALOGUE_ACCEPTED --> MAP_rsp + DIALOGUE_ACCEPTED --> MAP_DELIMITER_req + MAP_req --> Requesting_MAP_SSM + Requesting_MAP_SSM --> Service_Invoked_VIA_Intern2 + Service_Invoked_VIA_Intern2 --> DIALOGUE_ACCEPTED + MAP_rsp --> Response_Issued_VIA_Intern1 + Response_Issued_VIA_Intern1 --> DIALOGUE_ACCEPTED + MAP_DELIMITER_req --> TC_CONTINUE_req_VIA_TC1 + TC_CONTINUE_req_VIA_TC1 --> DIALOGUE_ESTABLISHED + DIALOGUE_ESTABLISHED --> DIALOGUE_ACCEPTED + DIALOGUE_ACCEPTED --> MAP_CLOSE_req + DIALOGUE_ACCEPTED --> MAP_U_ABORT_req + MAP_CLOSE_req --> TC_END_req_VIA_TC1 + MAP_U_ABORT_req --> Set_Abort_Reason: User_Specific + Set_Abort_Reason: User_Specific --> User_Info:= MAP-UserAbortInfo + User_Info:= MAP-UserAbortInfo --> TC_U_ABORT_req_VIA_TC1 + TC_END_req_VIA_TC1 --> Terminated_VIA_Intern1 + TC_U_ABORT_req_VIA_TC1 --> Terminated_VIA_Intern1 + Terminated_VIA_Intern1 --> Terminated_VIA_Intern2 + Terminated_VIA_Intern2 --> IDLE + Terminated_VIA_Intern1 --> To_all_active_PSSMs + Terminated_VIA_Intern2 --> To_all_active_RSSMs + +``` + +State transition diagram for Process MAP\_DSM. It starts at DIALOGUE\_ACCEPTED and branches into three paths: MAP\_req (leading to Requesting\_MAP\_SSM, Service\_Invoked\_VIA\_Intern2, and then DIALOGUE\_ACCEPTED), MAP\_rsp (leading to Response\_Issued\_VIA\_Intern1 and then DIALOGUE\_ACCEPTED), and MAP\_DELIMITER\_req (leading to TC\_CONTINUE\_req\_VIA\_TC1 and then DIALOGUE\_ESTABLISHED). From the second DIALOGUE\_ACCEPTED state, it branches into MAP\_CLOSE\_req (leading to TC\_END\_req\_VIA\_TC1) and MAP\_U\_ABORT\_req (leading to Set\_Abort\_Reason: User\_Specific, User\_Info:= MAP-UserAbortInfo, and then TC\_U\_ABORT\_req\_VIA\_TC1). Both TC\_END\_req\_VIA\_TC1 and TC\_U\_ABORT\_req\_VIA\_TC1 lead to a common path of Terminated\_VIA\_Intern1 (To all active PSSMs) and Terminated\_VIA\_Intern2 (To all active RSSMs), which finally leads to the IDLE state. + +9463 + +9464 + +Figure 15.6/3n: Process MAP\_DSM (sheet 14) + +Process MAP\_DSM + +MAP\_DSM15(17) + +Process to manage a MAP dialogue + +![State transition diagram for Process MAP_DSM. The diagram shows two main sections. The top section starts with DIALOGUE_ESTABLISHED and branches into MAP_req (leading to Requesting_MAP_SSM and Service_Invoked_VIA_Intern2), MAP_rsp (leading to Response_Issued_VIA_Intern1), and MAP_DELIMITER_req (leading to TC_CONTINUE_req_VIA_TC1). These paths merge into another DIALOGUE_ESTABLISHED state. The bottom section starts with DIALOGUE_ESTABLISHED and branches into TC_L_CANCEL_ind (leading to Invoke_ID_Active decision), TC_NOTICE_ind (leading to MAP_NOTICE_ind_VIA_User2), and TC_CONTINUE_ind (leading to Components_Present decision). The Invoke_ID_Active decision has (TRUE) leading to Timer_Expiry_VIA_Intern2 and (FALSE) leading to And SSM active. The Components_Present decision has (TRUE) leading to Process_Components and MAP_DELIMITER_ind_VIA_User2, and (FALSE) leading to the final merge. All paths merge into a final DIALOGUE_ESTABLISHED state.](69e2cabe4d7ea5d5fb8f98661cacdda3_img.jpg) + +``` + +stateDiagram-v2 + [*] --> DIALOGUE_ESTABLISHED_1 : DIALOGUE_ESTABLISHED + DIALOGUE_ESTABLISHED_1 --> MAP_req + DIALOGUE_ESTABLISHED_1 --> MAP_rsp + DIALOGUE_ESTABLISHED_1 --> MAP_DELIMITER_req + MAP_req --> Requesting_MAP_SSM + Requesting_MAP_SSM --> Service_Invoked_VIA_Intern2 + MAP_rsp --> Response_Issued_VIA_Intern1 + MAP_DELIMITER_req --> TC_CONTINUE_req_VIA_TC1 + Service_Invoked_VIA_Intern2 --> Merge1 + Response_Issued_VIA_Intern1 --> Merge1 + TC_CONTINUE_req_VIA_TC1 --> Merge1 + Merge1 --> DIALOGUE_ESTABLISHED_2 : DIALOGUE_ESTABLISHED + DIALOGUE_ESTABLISHED_2 --> TC_L_CANCEL_ind + DIALOGUE_ESTABLISHED_2 --> TC_NOTICE_ind + DIALOGUE_ESTABLISHED_2 --> TC_CONTINUE_ind + TC_L_CANCEL_ind --> Invoke_ID_Active + Invoke_ID_Active --> Timer_Expiry_VIA_Intern2 : (TRUE) + Invoke_ID_Active --> And_SSM_active : (FALSE) + TC_NOTICE_ind --> MAP_NOTICE_ind_VIA_User2 + TC_CONTINUE_ind --> Components_Present + Components_Present --> Process_Components : (TRUE) + Components_Present --> Merge2 : (FALSE) + Process_Components --> MAP_DELIMITER_ind_VIA_User2 + Timer_Expiry_VIA_Intern2 --> Merge2 + MAP_NOTICE_ind_VIA_User2 --> Merge2 + MAP_DELIMITER_ind_VIA_User2 --> Merge2 + Merge2 --> DIALOGUE_ESTABLISHED_3 : DIALOGUE_ESTABLISHED + +``` + +State transition diagram for Process MAP\_DSM. The diagram shows two main sections. The top section starts with DIALOGUE\_ESTABLISHED and branches into MAP\_req (leading to Requesting\_MAP\_SSM and Service\_Invoked\_VIA\_Intern2), MAP\_rsp (leading to Response\_Issued\_VIA\_Intern1), and MAP\_DELIMITER\_req (leading to TC\_CONTINUE\_req\_VIA\_TC1). These paths merge into another DIALOGUE\_ESTABLISHED state. The bottom section starts with DIALOGUE\_ESTABLISHED and branches into TC\_L\_CANCEL\_ind (leading to Invoke\_ID\_Active decision), TC\_NOTICE\_ind (leading to MAP\_NOTICE\_ind\_VIA\_User2), and TC\_CONTINUE\_ind (leading to Components\_Present decision). The Invoke\_ID\_Active decision has (TRUE) leading to Timer\_Expiry\_VIA\_Intern2 and (FALSE) leading to And SSM active. The Components\_Present decision has (TRUE) leading to Process\_Components and MAP\_DELIMITER\_ind\_VIA\_User2, and (FALSE) leading to the final merge. All paths merge into a final DIALOGUE\_ESTABLISHED state. + +9465 + +9466 + +Figure 15.6/30: Process MAP\_DSM (sheet 15) + +# Process MAP\_DSM + +MAP\_DSM16(17) + +Process to manage a MAP dialogue + +![State transition diagram for Process MAP_DSM](b10773c5223053f543c2f978197d4882_img.jpg) + +``` +stateDiagram-v2 + [*] --> DIALOGUE_ESTABLISHED + DIALOGUE_ESTABLISHED --> TC_END_ind + DIALOGUE_ESTABLISHED --> MAP_CLOSE_req + TC_END_ind --> Components_Present + Components_Present --> Process_Components : (TRUE) + Components_Present --> MAP_CLOSE_ind_VIA_User2 : (FALSE) + Process_Components --> MAP_CLOSE_ind_VIA_User2 + MAP_CLOSE_req --> TC_END_req_VIA_TC1 + TC_END_req_VIA_TC1 --> MAP_CLOSE_ind_VIA_User2 + MAP_CLOSE_ind_VIA_User2 --> Terminated_VIA_Intern1 + Terminated_VIA_Intern1 --> To_all_active_PSSMs + Terminated_VIA_Intern1 --> Terminated_VIA_Intern2 + Terminated_VIA_Intern2 --> To_all_active_RSSMs + Terminated_VIA_Intern2 --> IDLE +``` + +The diagram illustrates the state transitions for the Process MAP\_DSM. It begins with an initial state leading to **DIALOGUE\_ESTABLISHED**. From this state, two transitions are possible: **TC\_END\_ind** and **MAP\_CLOSE\_req**. The **TC\_END\_ind** transition leads to a decision diamond **Components\_Present**. If **(TRUE)**, it leads to **Process\_Components**, which then leads to **MAP\_CLOSE\_ind\_VIA\_User2**. If **(FALSE)**, it leads directly to **MAP\_CLOSE\_ind\_VIA\_User2**. The **MAP\_CLOSE\_req** transition leads to **TC\_END\_req\_VIA\_TC1**, which then leads to **MAP\_CLOSE\_ind\_VIA\_User2**. From **MAP\_CLOSE\_ind\_VIA\_User2**, the process proceeds to **Terminated\_VIA\_Intern1**, which then leads to **To\_all\_active\_PSSMs**. This is followed by **Terminated\_VIA\_Intern2**, which leads to **To\_all\_active\_RSSMs** and finally to the **IDLE** state. + +State transition diagram for Process MAP\_DSM + +9467 + +9468 + +Figure 15.6/3p: Process MAP\_DSM (sheet 16) + +## Process MAP\_DSM + +MAP\_DSM17(17) + +![SDL process diagram for MAP_DSM showing abort procedures from DIALOGUE ESTABLISHED to IDLE state.](c9e3572a1d0a3fd946db179079f95fcb_img.jpg) + +Process to manage +a MAP dialogue + +``` + +stateDiagram-v2 + state "DIALOGUE\nESTABLISHED" as DE + state "IDLE" as IDLE + state "User_Info" as UI <> + + [*] --> DE + DE --> TC_U_ABORT_ind + DE --> TC_P_ABORT_ind + DE --> MAP_U_ABORT_req + + TC_U_ABORT_ind --> UI + UI --> MAP_U_ABORT_ind_VIA_User2 : User_Abort_PDU + UI --> MAP_P_ABORT_ind_VIA_User2 : Provider_Abort_PDU + + TC_P_ABORT_ind --> MAP_P_ABORT_ind_VIA_User2 + + MAP_U_ABORT_req --> Set_Abort_Reason + note right of Set_Abort_Reason : User_Specific + Set_Abort_Reason --> Set_User_Info + note right of Set_User_Info : MAP_User_Abort_Info + Set_User_Info --> TC_U_ABORT_req_VIA_TC1 + + MAP_U_ABORT_ind_VIA_User2 --> Terminated_VIA_Intern1 + MAP_P_ABORT_ind_VIA_User2 --> Terminated_VIA_Intern1 + TC_U_ABORT_req_VIA_TC1 --> Terminated_VIA_Intern1 + + Terminated_VIA_Intern1 --> Terminated_VIA_Intern2 + note right of Terminated_VIA_Intern1 : To all active PSSMs + Terminated_VIA_Intern2 --> IDLE + note right of Terminated_VIA_Intern2 : To all active RSSMs + +``` + +SDL process diagram for MAP\_DSM showing abort procedures from DIALOGUE ESTABLISHED to IDLE state. + +9469 + +9470 + +**Figure 15.6/3q: Process MAP\_DSM (sheet 17)** + +9471 + +![Flowchart for Procedure Process_Components. It starts with a connector, followed by WAIT_FOR_COMPONENTS, TC_INVOKE_ind(Op_Code), and a decision diamond 'Invoke_ID_Assigned'. The flow branches based on (TRUE) and (FALSE) paths, leading to various processing steps like 'Set_Problem_Code: Duplicated_Invoke_ID', 'TC_U_REJECT_req_VIA_TC1', 'Set_Diagnostic: Abnormal_Event_Received_From_Peer', 'MAP_NOTICE_ind_VIA_User2', and 'Last_Component' decision. It ends with a connector and another WAIT_FOR_COMPONENTS block.](945bdd5b440b3ed5bc0fcf1ac3b7d5b4_img.jpg) + +### Procedure Process\_Components + +Proc\_Comp1(5) + +Procedure to process components received in a TC message + +Comment: 'Components from TCAP' +DCL +Op\_Code, Operation\_Class INTEGER; +Operation\_Exists, Last\_Component, Invoke\_ID\_Present, Invoke\_ID\_Assigned, Linked\_ID\_Present, Linked\_ID\_Assigned, Linked\_Operation\_Allowed, v3\_Or\_Higher\_Dialogue BOOLEAN; + +``` +graph TD; Start([ ]) --> WFC1(WAIT_FOR_COMPONENTS); WFC1 --> TC_INVOKE[TC_INVOKE_ind(Op_Code)]; TC_INVOKE --> D1{Invoke_ID_Assigned}; D1 -- (FALSE) --> D1_False[ ]; D1 -- (TRUE) --> D2{Operation_Exists}; D2 -- (TRUE) --> D3{Linked_ID_Present}; D2 -- (FALSE) --> Set_Problem_Code_1[Set_Problem_Code: Unrecognised_Operation]; Set_Problem_Code_1 --> TC_U_REJECT_1[TC_U_REJECT_req_VIA_TC1]; D3 -- (TRUE) --> Connector1((1)); D3 -- (FALSE) --> Performing_MAP_SSM[Performing_MAP_SSM]; Performing_MAP_SSM --> Service_Invocation[Service_Invocation_Received_VIA_Intern1]; TC_U_REJECT_1 --> D4{v3_Or_Higher_Dialogue}; D4 -- (TRUE) --> D5{Last_Component}; D4 -- (FALSE) --> Set_Diagnostic[Set_Diagnostic: Abnormal_Event_Received_From_Peer]; Set_Diagnostic --> MAP_NOTICE[MAP_NOTICE_ind_VIA_User2]; MAP_NOTICE --> D5; D5 -- (TRUE) --> Connector2(( )); D5 -- (FALSE) --> WFC2(WAIT_FOR_COMPONENTS); +``` + +Flowchart for Procedure Process\_Components. It starts with a connector, followed by WAIT\_FOR\_COMPONENTS, TC\_INVOKE\_ind(Op\_Code), and a decision diamond 'Invoke\_ID\_Assigned'. The flow branches based on (TRUE) and (FALSE) paths, leading to various processing steps like 'Set\_Problem\_Code: Duplicated\_Invoke\_ID', 'TC\_U\_REJECT\_req\_VIA\_TC1', 'Set\_Diagnostic: Abnormal\_Event\_Received\_From\_Peer', 'MAP\_NOTICE\_ind\_VIA\_User2', and 'Last\_Component' decision. It ends with a connector and another WAIT\_FOR\_COMPONENTS block. + +9472 + +9473 + +Figure 15.6/4a: Procedure Process\_Components (sheet 1) + +Procedure Process\_Components + +Proc\_Comp2(5) + +Procedure to process components received in a TC message + +![Flowchart for Procedure Process_Components. It starts at connector '1', goes to decision 'Linked_ID_Assigned'. If (FALSE), it goes to 'Set_Problem_Code: Linked_ID_Not Assigned' then 'TC_U_REJECT_req_VIA_TC1'. If (TRUE), it goes to decision 'Operation_Class'. 'Operation_Class' has branches (1,2,3) leading to 'Linked_Service_Invoked_VIA_Intern2' and (4) leading to 'Linked_Request_Received_VIA_Intern2'. Both branches lead to 'Performing_MAP_SSM'. From 'Performing_MAP_SSM', it goes to 'Service_Invocation_Received_VIA_Intern1'. Both 'MAP_NOTICE_ind_VIA_User2' (from TC_U_REJECT) and 'Service_Invocation_Received_VIA_Intern1' lead to decision 'Last_Component'. If (TRUE), it ends at a circle with an X. If (FALSE), it goes to 'WAIT_FOR_COMPONENTS' and loops back to the start of the 'Operation_Class' decision.](1ef5623b9afe103c2e5bb1e19977dcd4_img.jpg) + +Flowchart for Procedure Process\_Components. It starts at connector '1', goes to decision 'Linked\_ID\_Assigned'. If (FALSE), it goes to 'Set\_Problem\_Code: Linked\_ID\_Not Assigned' then 'TC\_U\_REJECT\_req\_VIA\_TC1'. If (TRUE), it goes to decision 'Operation\_Class'. 'Operation\_Class' has branches (1,2,3) leading to 'Linked\_Service\_Invoked\_VIA\_Intern2' and (4) leading to 'Linked\_Request\_Received\_VIA\_Intern2'. Both branches lead to 'Performing\_MAP\_SSM'. From 'Performing\_MAP\_SSM', it goes to 'Service\_Invocation\_Received\_VIA\_Intern1'. Both 'MAP\_NOTICE\_ind\_VIA\_User2' (from TC\_U\_REJECT) and 'Service\_Invocation\_Received\_VIA\_Intern1' lead to decision 'Last\_Component'. If (TRUE), it ends at a circle with an X. If (FALSE), it goes to 'WAIT\_FOR\_COMPONENTS' and loops back to the start of the 'Operation\_Class' decision. + +9474 + +9475 + +Figure 15.6/4b: Procedure Process\_Components (sheet 2) + +Procedure Process\_Components + +Proc\_Comp3(5) + +Procedure to process components received in a TC message + +![Flowchart for Procedure Process_Components. It starts with WAIT_FOR_COMPONENTS, branches into TC_RESULT_L_ind, TC_RESULT_NL_ind, and TC_U_ERROR_ind. Each branch has an Invoke_ID_Assigned decision. TC_RESULT_L_ind and TC_RESULT_NL_ind lead to connectors '2' on FALSE and result messages on TRUE. TC_U_ERROR_ind leads to connector '2' on FALSE and a series of error handling steps on TRUE. All result messages lead to a Last_Component decision. If FALSE, it loops back to WAIT_FOR_COMPONENTS. If TRUE, it ends at a connector with an 'X'.](4391cd8ac8f58d1b46439ea0cb130782_img.jpg) + +``` + +graph TD + Start([WAIT_FOR_COMPONENTS]) --> TC_RESULT_L_ind[/TC_RESULT_L_ind/] + Start --> TC_RESULT_NL_ind[/TC_RESULT_NL_ind/] + Start --> TC_U_ERROR_ind[/TC_U_ERROR_ind/] + + TC_RESULT_L_ind --> Invoke_ID_Assigned_L{Invoke_ID_Assigned} + Invoke_ID_Assigned_L -- (FALSE) --> C2_L((2)) + Invoke_ID_Assigned_L -- (TRUE) --> Result_Received_VIA_Intern2[/Result_Received_VIA_Intern2/] + + TC_RESULT_NL_ind --> Invoke_ID_Assigned_NL{Invoke_ID_Assigned} + Invoke_ID_Assigned_NL -- (FALSE) --> C2_NL((2)) + Invoke_ID_Assigned_NL -- (TRUE) --> Partial_Result_Received_VIA_Intern2[/Partial_Result_Received_VIA_Intern2/] + + TC_U_ERROR_ind --> Invoke_ID_Assigned_U{Invoke_ID_Assigned} + Invoke_ID_Assigned_U -- (FALSE) --> C2_U((2)) + Invoke_ID_Assigned_U -- (TRUE) --> Set_Problem_Code[Set_Problem_Code: +Invoke_ID +Not Assigned] + Set_Problem_Code --> TC_U_REJECT_req_VIA_TC1[/TC_U_REJECT_req_VIA_TC1/] + TC_U_REJECT_req_VIA_TC1 --> Set_Diagnostic[Set_Diagnostic: +Abnormal_Event_Received +From Peer] + Set_Diagnostic --> MAP_NOTICE_ind_VIA_User2[/MAP_NOTICE_ind_VIA_User2/] + + Result_Received_VIA_Intern2 --> Last_Component{Last_Component} + Partial_Result_Received_VIA_Intern2 --> Last_Component + Negative_Result_Received_VIA_Intern2[/Negative_Result_Received_VIA_Intern2/] --> Last_Component + MAP_NOTICE_ind_VIA_User2 --> Last_Component + + Last_Component -- (FALSE) --> Start + Last_Component -- (TRUE) --> End((X)) + +``` + +Flowchart for Procedure Process\_Components. It starts with WAIT\_FOR\_COMPONENTS, branches into TC\_RESULT\_L\_ind, TC\_RESULT\_NL\_ind, and TC\_U\_ERROR\_ind. Each branch has an Invoke\_ID\_Assigned decision. TC\_RESULT\_L\_ind and TC\_RESULT\_NL\_ind lead to connectors '2' on FALSE and result messages on TRUE. TC\_U\_ERROR\_ind leads to connector '2' on FALSE and a series of error handling steps on TRUE. All result messages lead to a Last\_Component decision. If FALSE, it loops back to WAIT\_FOR\_COMPONENTS. If TRUE, it ends at a connector with an 'X'. + +9476 + +9477 + +Figure 15.6/4c: Procedure Process\_Components (sheet 3) + +# Procedure Process\_Components + +Proc\_Comp4(5) + +Procedure to process components received in a TC message + +![Flowchart for Procedure Process_Components. It starts with WAIT_FOR_COMPONENTS, branches into TC_L_REJECT_ind and TC_R_REJECT_ind paths, includes decision diamonds for Invoke_ID_Present, Problem Type, and Invoke_ID_Assigned, and ends with a Last_Component decision leading to either an end symbol or back to WAIT_FOR_COMPONENTS.](a4dfbebcb37369374ba8d65c7a9bd887_img.jpg) + +``` + +graph TD + Start([WAIT_FOR_COMPONENTS]) --> TC_L[TC_L_REJECT_ind] + Start --> TC_R[TC_R_REJECT_ind] + + TC_L --> L1{Invoke_ID_Present} + L1 -- (FALSE) --> L4[MAP NOTICE_ind_VIA_User2] + L1 -- (TRUE) --> L2{Problem Type +rr_problem, re_problem, general_problem} + L2 -- invoke_problem --> L4 + + L2 --> L3{Invoke_ID_Assigned} + L3 -- (FALSE) --> L4 + L3 -- (TRUE) --> L5[Provider_Reject_Received_VIA_Intern2] + + TC_R --> R2{Problem Type +rr_problem, re_problem, general_problem} + R2 -- invoke_problem --> R4[MAP NOTICE_ind_VIA_User2] + + R2 --> R3{Invoke_ID_Assigned} + R3 -- (FALSE) --> R4 + R3 -- (TRUE) --> R5[Provider_Reject_Received_VIA_Intern2] + + L5 --> Join(( )) + L4 --> Join + R5 --> Join + R4 --> Join + + Join --> Last{Last_Component} + Last -- (TRUE) --> End((X)) + Last -- (FALSE) --> End([WAIT_FOR_COMPONENTS]) + +``` + +Flowchart for Procedure Process\_Components. It starts with WAIT\_FOR\_COMPONENTS, branches into TC\_L\_REJECT\_ind and TC\_R\_REJECT\_ind paths, includes decision diamonds for Invoke\_ID\_Present, Problem Type, and Invoke\_ID\_Assigned, and ends with a Last\_Component decision leading to either an end symbol or back to WAIT\_FOR\_COMPONENTS. + +9478 + +9479 + +Figure 15.6/4d: Procedure Process\_Components (sheet 4) + +Procedure Process\_Components + +Proc\_Comp5(5) + +Procedure to process components received in a TC message + +![Flowchart for Procedure Process_Components](5a0427b4033881484e387d85b8d8fa77_img.jpg) + +``` +graph TD; Start([WAIT_FOR_COMPONENTS]) --> TC_U[TC_U REJECT_ind]; Start --> Asterisk[/*/]; TC_U --> Problem_Type{Problem Type}; Problem_Type -- "rr_problem, re_problem" --> Asterisk; Problem_Type -- invoke_problem --> Invoke_ID{Invoke_ID Assigned}; Invoke_ID -- (FALSE) --> Asterisk; Invoke_ID -- (TRUE) --> User_Reject[User_Reject Received VIA_Intern2]; User_Reject --> Last_Component{Last Component}; MAP_NOTICE[MAP NOTICE_ind VIA_User2] --> Last_Component; Last_Component -- (FALSE) --> Asterisk; Last_Component -- (TRUE) --> End(( )); Last_Component -- (TRUE) --> End_Wait([WAIT_FOR_COMPONENTS]); +``` + +The flowchart illustrates the 'Process\_Components' procedure. It begins with a 'WAIT\_FOR\_COMPONENTS' state, leading to a 'TC\_U REJECT\_ind' input. From this input, the flow can lead to an asterisk symbol (representing an exit or continuation) or to a 'Problem Type' decision. The 'Problem Type' decision has two outputs: 'rr\_problem, re\_problem' which leads to the asterisk, and 'invoke\_problem' which leads to an 'Invoke\_ID Assigned' decision. The 'Invoke\_ID Assigned' decision has two outputs: '(FALSE)' which leads to the asterisk, and '(TRUE)' which leads to a 'User\_Reject Received VIA\_Intern2' output. Both the 'User\_Reject' output and a 'MAP NOTICE\_ind VIA\_User2' output lead to a 'Last Component' decision. The 'Last Component' decision has two outputs: '(FALSE)' which leads to the asterisk, and '(TRUE)' which leads to an end symbol (circle with an X) and a 'WAIT\_FOR\_COMPONENTS' state. + +Flowchart for Procedure Process\_Components + +9480 + +9481 + +Figure 15.6/4e: Procedure Process\_Components (sheet 5) + +Process Load\_Ctrl + +Load\_Ctrl1(1) + +Process to verify whether offered dialogue should be discarded because of overload + +Comment 'LOAD CONTROL'; +DCL +Congestion, Dialogue\_Acceptable BOOLEAN + +![Flowchart for Process Load_Ctrl showing logic for load control based on Congestion and Dialogue_Acceptable boolean flags.](fb4503cfc4abdcdf439a898cde5bab68_img.jpg) + +``` +graph TD; Start([ ]) --> IDLE1([IDLE]); IDLE1 --> CheckLoad{{Check_Load}}; CheckLoad --> Congestion{Congestion}; Congestion -- TRUE --> DialogueAcceptable{Dialogue_Acceptable}; Congestion -- FALSE --> LoadOK1{{Load_OK_VIA_Load2}}; DialogueAcceptable -- TRUE --> LoadOK2{{Load_OK_VIA_Load2}}; DialogueAcceptable -- FALSE --> Overload{{Overload_VIA_Load2}}; LoadOK1 --> IDLE2([IDLE]); LoadOK2 --> IDLE2; Overload --> IDLE2; +``` + +The flowchart illustrates the 'Process Load\_Ctrl' logic. It begins with an initial state leading to an 'IDLE' state. From 'IDLE', the process moves to a 'Check\_Load' step. A decision diamond 'Congestion' follows. If 'TRUE', it proceeds to another decision diamond 'Dialogue\_Acceptable'. If 'Dialogue\_Acceptable' is 'TRUE', it leads to a 'Load\_OK\_VIA\_Load2' state. If 'FALSE', it leads to an 'Overload\_VIA\_Load2' state. If 'Congestion' is 'FALSE', it leads directly to a 'Load\_OK\_VIA\_Load2' state. All three states ('Load\_OK\_VIA\_Load2', 'Overload\_VIA\_Load2', and the direct path) converge to a final 'IDLE' state. + +Flowchart for Process Load\_Ctrl showing logic for load control based on Congestion and Dialogue\_Acceptable boolean flags. + +9482 +9483 + +Figure 15.6/5: Process Load\_Ctrl + +# Process Requesting\_MAP\_SSM + +MAP\_RSSM1(4) + +Process to handle MAP service requests and the responses from the distant entity + +Comment 'Requesting MAP Service State Machine': +DCL +Argument\_Correct, Error\_Code\_Correct, Linked\_Request\_Defined, Syntax\_Correct, MAP\_initiated, +Unexpected\_Data, Implicit\_Cnf, Linked\_Operation\_Allowed, Wait\_For\_Cnf, Service\_Parameter\_Available BOOLEAN, +Operation\_Class INTEGER; + +![State transition diagram for Process Requesting_MAP_SSM](e5b4cfceaf317b48009d22b45b0c6340_img.jpg) + +``` +graph TD; Start([ ]) --> IDLE{{IDLE}}; IDLE --> Service_Invoked[/Service_Invoked/]; Service_Invoked -.-> Note1[A service has been invoked by the MAP user]; Service_Invoked --> Set_Operation[Set_Operation_Code_and_TCAP_Parameters]; Set_Operation --> TC_INVOKE{TC_INVOKE_req_VIA_TC4}; TC_INVOKE --> Wait_For_Cnf{Wait_For_Cnf}; Wait_For_Cnf -- TRUE --> WAIT_FOR_CONFIRM{{WAIT_FOR_CONFIRM}}; Wait_For_Cnf -- FALSE --> End((X)); +``` + +The diagram is a state transition diagram for the 'Process Requesting\_MAP\_SSM'. It begins with an oval connector symbol pointing down to a double-bordered oval state labeled 'IDLE'. From 'IDLE', a vertical line leads to a chevron-shaped transition symbol labeled 'Service\_Invoked'. To the right of this transition is a dashed box containing the text 'A service has been invoked by the MAP user'. Below the transition, a vertical line leads to a rectangular process symbol labeled 'Set\_Operation\_Code\_and\_TCAP\_Parameters'. Below this process, a vertical line leads to a diamond-shaped decision symbol labeled 'TC\_INVOKE\_req\_VIA\_TC4'. Below this decision, a vertical line leads to another diamond-shaped decision symbol labeled 'Wait\_For\_Cnf'. From 'Wait\_For\_Cnf', a vertical line labeled '(TRUE)' leads down to a double-bordered oval state labeled 'WAIT\_FOR\_CONFIRM'. A horizontal line labeled '(FALSE)' extends to the right from 'Wait\_For\_Cnf' and ends at a circle with an 'X' inside, representing an error or termination state. + +State transition diagram for Process Requesting\_MAP\_SSM + +9484 + +9485 + +Figure 15.6/6a: Process Requesting\_MAP\_SSM (sheet 1) + +# Process Requesting\_MAP\_SSM + +MAP\_RSSM2(4) + +Process to handle MAP service requests and the responses from the distant entity + +![State transition diagram for Process Requesting_MAP_SSM. It starts with WAIT_FOR_CONFIRM and branches into Result_Received, 1, Partial_Result_Received, and Negative_Result_Received. Each branch contains decision diamonds for Syntax_Correct, Partial_Result_Correct, Service_Parameter_Available, and Unexpected_Data_Value, leading to various actions like Append_Partial_Info, Set_Provider_Error, MAP_cnf, and TC_U_REJECT.](81e0bc85cbb6bdb4779d4af6d86e80cd_img.jpg) + +``` + +stateDiagram-v2 + [*] --> WAIT_FOR_CONFIRM + WAIT_FOR_CONFIRM --> Result_Received + WAIT_FOR_CONFIRM --> 1 + WAIT_FOR_CONFIRM --> Partial_Result_Received + WAIT_FOR_CONFIRM --> Negative_Result_Received + + Result_Received --> Syntax_Correct_1{Syntax_Correct} + Syntax_Correct_1 --> 1 : (FALSE) + Syntax_Correct_1 --> Partial_Result_Correct_1{Partial_Result_Correct} : (TRUE) + Partial_Result_Correct_1 --> 1 : (FALSE) + Partial_Result_Correct_1 --> Append_Partial_Info : (TRUE) + Append_Partial_Info --> Service_Parameter_Available_1{Service_Parameter_Available} + Service_Parameter_Available_1 --> 1 : (FALSE) + Service_Parameter_Available_1 --> Unexpected_Data_Value_1{Unexpected_Data_Value} : (TRUE) + Unexpected_Data_Value_1 --> 1 : (FALSE) + Unexpected_Data_Value_1 --> Set_Provider_Error_1[Set_Provider_Error: Invalid_Response_Received] : (TRUE) + Set_Provider_Error_1 --> MAP_cnf_1[MAP_cnf VIA_User4] + MAP_cnf_1 --> [*] + + 1 --> Set_Provider_Error_2[Set_Provider_Error: Invalid_Response_Received] + Set_Provider_Error_2 --> MAP_cnf_2[MAP_cnf VIA_User4] + MAP_cnf_2 --> Set_Problem_Code_2[Set_Problem_Code: Mistyped_Parameter] + Set_Problem_Code_2 --> TC_U_REJECT_2[TC_U_REJECT req_VIA_TC4] + TC_U_REJECT_2 --> [*] + + Partial_Result_Received --> Syntax_Correct_3{Syntax_Correct} + Syntax_Correct_3 --> TC_U_CANCEL_req_3[TC_U_CANCEL req_VIA_TC4] : (FALSE) + Syntax_Correct_3 --> Store_Partial_Info : (TRUE) + Store_Partial_Info --> WAIT_FOR_CONFIRM + + Negative_Result_Received --> Error_Code_Correct{Error_Code_Correct} + Error_Code_Correct --> 1 : (FALSE) + Error_Code_Correct --> Syntax_Correct_4{Syntax_Correct} : (TRUE) + Syntax_Correct_4 --> 1 : (FALSE) + Syntax_Correct_4 --> Service_Parameters_Available_4{Service_Parameters_Available} : (TRUE) + Service_Parameters_Available_4 --> 1 : (FALSE) + Service_Parameters_Available_4 --> Unexpected_Data_Value_4{Unexpected_Data_Value} : (TRUE) + Unexpected_Data_Value_4 --> 1 : (FALSE) + Unexpected_Data_Value_4 --> Set_User_Error_4[Set_User_Error] : (TRUE) + Set_User_Error_4 --> MAP_cnf_4[MAP_cnf VIA_User4] + MAP_cnf_4 --> [*] + +``` + +State transition diagram for Process Requesting\_MAP\_SSM. It starts with WAIT\_FOR\_CONFIRM and branches into Result\_Received, 1, Partial\_Result\_Received, and Negative\_Result\_Received. Each branch contains decision diamonds for Syntax\_Correct, Partial\_Result\_Correct, Service\_Parameter\_Available, and Unexpected\_Data\_Value, leading to various actions like Append\_Partial\_Info, Set\_Provider\_Error, MAP\_cnf, and TC\_U\_REJECT. + +9486 + +9487 + +Figure 15.6/6b: Process Requesting\_MAP\_SSM (sheet 2) + +# Process Requesting\_MAP\_SSM + +MAP\_RSSM3(4) + +Process to handle MAP service requests and the responses from the distant entity + +![State transition diagram for Process Requesting_MAP_SSM. It starts with WAIT_FOR_CONFIRM and branches into four states: Linked_Request_Received, Terminated, User_Reject_Received, and Linked_Service_Invoked. The diagram includes decision diamonds for Linked_Operation_Allowed, Argument_Correct, Service_Parameters_Available, and MAP_Initiated, leading to various actions like Find_Parent_Operation_Code, Set_Problem_Code, Set_Provider_Error, and Set_User_Error, eventually leading to MAP_cnf_VIA_User4 or WAIT_FOR_CONFIRM.](0c373f7645ae57a94d9107bb41043cfe_img.jpg) + +``` + +stateDiagram-v2 + [*] --> WAIT_FOR_CONFIRM + WAIT_FOR_CONFIRM --> Linked_Request_Received + WAIT_FOR_CONFIRM --> Terminated + WAIT_FOR_CONFIRM --> User_Reject_Received + WAIT_FOR_CONFIRM --> Linked_Service_Invoked + + Linked_Request_Received --> Find_Parent_Operation_Code + Find_Parent_Operation_Code --> Linked_Operation_Allowed{Linked_Operation_Allowed} + Linked_Operation_Allowed -- (FALSE) --> 1 + Linked_Operation_Allowed -- (TRUE) --> Argument_Correct{Argument_Correct} + Argument_Correct -- (FALSE) --> Set_Problem_Code + Argument_Correct -- (TRUE) --> Service_Parameters_Available{Service_Parameters_Available} + Service_Parameters_Available -- (FALSE) --> Set_Provider_Error_1[Set_Provider_Error: Data_Missing] + Service_Parameters_Available -- (TRUE) --> MAP_cnf_VIA_User4_1{{MAP_cnf_VIA_User4}} + Set_Problem_Code --> TC_U_REJECT_req_VIA_TC4{{TC_U_REJECT req_VIA_TC4}} + TC_U_REJECT_req_VIA_TC4 --> MAP_cnf_VIA_User4_1 + Set_Provider_Error_1 --> MAP_cnf_VIA_User4_1 + MAP_cnf_VIA_User4_1 --> [*] + + User_Reject_Received --> MAP_Initiated{MAP_Initiated} + MAP_Initiated -- (FALSE) --> Set_Provider_Error_2[Set_Provider_Error] + MAP_Initiated -- (TRUE) --> Set_User_Error + Set_Provider_Error_2 --> MAP_cnf_VIA_User4_2{{MAP_cnf_VIA_User4}} + Set_User_Error --> MAP_cnf_VIA_User4_2 + MAP_cnf_VIA_User4_2 --> [*] + + Linked_Service_Invoked --> Implicit_Cnf_TRUE[Implicit_Cnf:= TRUE] + Implicit_Cnf_TRUE --> WAIT_FOR_CONFIRM + +``` + +State transition diagram for Process Requesting\_MAP\_SSM. It starts with WAIT\_FOR\_CONFIRM and branches into four states: Linked\_Request\_Received, Terminated, User\_Reject\_Received, and Linked\_Service\_Invoked. The diagram includes decision diamonds for Linked\_Operation\_Allowed, Argument\_Correct, Service\_Parameters\_Available, and MAP\_Initiated, leading to various actions like Find\_Parent\_Operation\_Code, Set\_Problem\_Code, Set\_Provider\_Error, and Set\_User\_Error, eventually leading to MAP\_cnf\_VIA\_User4 or WAIT\_FOR\_CONFIRM. + +Figure 15.6/6c: Process Requesting\_MAP\_SSM (sheet 3) + +# Process Requesting\_MAP\_SSM + +MAP\_RSSM4(4) + +Process to handle MAP service requests and the responses from the distant entity + +![State transition diagram for Process Requesting_MAP_SSM. It starts at WAIT_FOR_CONFIRM, leading to a merge point. From the merge point, it can go to Provider_Reject_Received or Timer_Expiry. Both lead to Operation_Class decision (4). Operation_Class (2) leads to Linked_Request_Defined (TRUE/FALSE). Operation_Class (1,3) leads to Implicit_Cnf (TRUE/FALSE). Both decisions lead to Set_Provider_Error and then MAP_cnf VIA_User4. Operation_Class (4) also leads to an exit.](aed3396820a10fad2d1554d72c525982_img.jpg) + +``` + +stateDiagram-v2 + [*] --> WAIT_FOR_CONFIRM + WAIT_FOR_CONFIRM --> Merge + state "Provider_Reject_Received" as Provider_Reject_Received + state "Timer_Expiry" as Timer_Expiry + state "Operation_Class" as Operation_Class + state "Linked_Request_Defined" as Linked_Request_Defined + state "Implicit_Cnf" as Implicit_Cnf + state "Set_Provider_Error" as Set_Provider_Error + state "MAP_cnf VIA_User4" as MAP_cnf_VIA_User4 + + Merge --> Provider_Reject_Received + Merge --> Timer_Expiry + Provider_Reject_Received --> Set_Provider_Error + Timer_Expiry --> Operation_Class + Operation_Class --> Set_Provider_Error + Operation_Class --> Implicit_Cnf + Operation_Class --> [*] + Linked_Request_Defined --> Implicit_Cnf + Implicit_Cnf --> Set_Provider_Error + Implicit_Cnf --> MAP_cnf_VIA_User4 + Implicit_Cnf --> [*] + Set_Provider_Error --> MAP_cnf_VIA_User4 + MAP_cnf_VIA_User4 --> [*] + +``` + +Associated with the service + +'A linked operation should have been invoked' + +State transition diagram for Process Requesting\_MAP\_SSM. It starts at WAIT\_FOR\_CONFIRM, leading to a merge point. From the merge point, it can go to Provider\_Reject\_Received or Timer\_Expiry. Both lead to Operation\_Class decision (4). Operation\_Class (2) leads to Linked\_Request\_Defined (TRUE/FALSE). Operation\_Class (1,3) leads to Implicit\_Cnf (TRUE/FALSE). Both decisions lead to Set\_Provider\_Error and then MAP\_cnf VIA\_User4. Operation\_Class (4) also leads to an exit. + +9490 + +9491 + +Figure 15.6/6d: Process Requesting\_MAP\_SSM (sheet 4) + +9492 +9493 +9494 +9495 + +# Process Performing\_MAP\_SSM + +MAP\_PSSM1(2) + +Process to handle an invoke component received from the peer and the response from the user + +Comment 'Performing MAP Service State Machine': +DCL +Argument\_Correct, Service\_Identifiable, Service\_Parameters\_Available, Unexpected\_Data, +Length\_OK, User\_Error\_Present, Linked\_Request, Specific\_Error, More\_Data, +Cnf\_Required BOOLEAN, +Operation\_Class INTEGER, +TIMER Guard\_Timer COMMENT 'expires if MAP user does not respond'; + +![State transition diagram for Process Performing_MAP_SSM. It starts at IDLE, goes to Service_Invocation_Received, then checks Argument_Correct. If FALSE, it goes to Set_Problem_Code: Mistyped_Parameter. If TRUE, it checks Service_Identifiable. If FALSE, it goes to Discard_Invocation. If TRUE, it checks Service_Parameters_Available. If FALSE, it goes to Discard_Invocation. If TRUE, it checks Unexpected_Data. If TRUE, it goes to Discard_Invocation. If FALSE, it checks Cnf_Required. If TRUE, it goes to Set_(Guard_Timer) then WAIT_FOR_RESPONSE. If FALSE, it goes to Discard_Invocation. From Service_Identifiable TRUE, it checks Operation_Class. If (1,2), it goes to Set_Error: Unexpected_Data_Value. If (3,4), it goes to Discard_Invocation. From Operation_Class (Associated with the service) in the Service_Identifiable path, it goes to Set_Error: Data_Missing. Both Set_Error: Unexpected_Data_Value and Set_Error: Data_Missing lead to TC_U_ERROR req_VIA_TC3. From TC_U_ERROR req_VIA_TC3, it goes to MAP_NOTICE_ind_VIA_User3. From Set_Problem_Code: Mistyped_Parameter, it goes to TC_U_REJECT_req_VIA_TC3, then MAP_NOTICE_ind_VIA_User3. There are also exit points (crosses) from Discard_Invocation, Set_(Guard_Timer), and MAP_NOTICE_ind_VIA_User3 states. A connector '1' is used between the Operation_Class (Associated with the service) in the Service_Identifiable path and the Set_Error: Unexpected_Data_Value state.](a0e4d56066bf089079b9b4d24f666b01_img.jpg) + +``` + +stateDiagram-v2 + [*] --> IDLE + IDLE --> Service_Invocation_Received + Service_Invocation_Received --> Argument_Correct + Argument_Correct --> Service_Identifiable + Argument_Correct --> Set_Problem_Code: Mistyped_Parameter (FALSE) + Service_Identifiable --> Service_Parameters_Available + Service_Identifiable --> Discard_Invocation (FALSE) + Service_Identifiable --> Operation_Class (TRUE) + Service_Parameters_Available --> Discard_Invocation (FALSE) + Service_Parameters_Available --> Unexpected_Data (TRUE) + Unexpected_Data --> Discard_Invocation (TRUE) + Unexpected_Data --> Cnf_Required (FALSE) + Cnf_Required --> Set_(Guard_Timer) (TRUE) + Cnf_Required --> Discard_Invocation (FALSE) + Set_(Guard_Timer) --> WAIT_FOR_RESPONSE + Operation_Class --> Set_Error: Unexpected_Data_Value (1,2) + Operation_Class --> Discard_Invocation (3,4) + Operation_Class --> Set_Error: Data_Missing (Associated with the service) + Set_Error: Unexpected_Data_Value --> TC_U_ERROR req_VIA_TC3 + Set_Error: Data_Missing --> TC_U_ERROR req_VIA_TC3 + TC_U_ERROR req_VIA_TC3 --> MAP_NOTICE_ind_VIA_User3 + Set_Problem_Code: Mistyped_Parameter --> TC_U_REJECT_req_VIA_TC3 + TC_U_REJECT_req_VIA_TC3 --> MAP_NOTICE_ind_VIA_User3 + Discard_Invocation --> [*] + Set_(Guard_Timer) --> [*] + MAP_NOTICE_ind_VIA_User3 --> [*] + +``` + +State transition diagram for Process Performing\_MAP\_SSM. It starts at IDLE, goes to Service\_Invocation\_Received, then checks Argument\_Correct. If FALSE, it goes to Set\_Problem\_Code: Mistyped\_Parameter. If TRUE, it checks Service\_Identifiable. If FALSE, it goes to Discard\_Invocation. If TRUE, it checks Service\_Parameters\_Available. If FALSE, it goes to Discard\_Invocation. If TRUE, it checks Unexpected\_Data. If TRUE, it goes to Discard\_Invocation. If FALSE, it checks Cnf\_Required. If TRUE, it goes to Set\_(Guard\_Timer) then WAIT\_FOR\_RESPONSE. If FALSE, it goes to Discard\_Invocation. From Service\_Identifiable TRUE, it checks Operation\_Class. If (1,2), it goes to Set\_Error: Unexpected\_Data\_Value. If (3,4), it goes to Discard\_Invocation. From Operation\_Class (Associated with the service) in the Service\_Identifiable path, it goes to Set\_Error: Data\_Missing. Both Set\_Error: Unexpected\_Data\_Value and Set\_Error: Data\_Missing lead to TC\_U\_ERROR req\_VIA\_TC3. From TC\_U\_ERROR req\_VIA\_TC3, it goes to MAP\_NOTICE\_ind\_VIA\_User3. From Set\_Problem\_Code: Mistyped\_Parameter, it goes to TC\_U\_REJECT\_req\_VIA\_TC3, then MAP\_NOTICE\_ind\_VIA\_User3. There are also exit points (crosses) from Discard\_Invocation, Set\_(Guard\_Timer), and MAP\_NOTICE\_ind\_VIA\_User3 states. A connector '1' is used between the Operation\_Class (Associated with the service) in the Service\_Identifiable path and the Set\_Error: Unexpected\_Data\_Value state. + +9496 + +Figure 15.6/8a: Process Performing\_MAP\_SSM (sheet 1) + +![State transition diagram for Process Performing_MAP_SSM (sheet 1). The process starts at WAIT_FOR_RESPONSE and branches based on Guard_Timer_Expired, Response_Issued, or Terminated. Response_Issued leads to User_Error_Present, which then branches to Linked_Request or Specific_Error. These lead to various processing steps like Length_O.K., Split_info, TC_RESULT_NL_req_VIA_TC3, more_data, Set_Operation_Code_and_TCAP_Param, Set_Error_Code, Set_Problem_Code, and finally TC_INVOKE_req_VIA_TC3, TC_U_ERROR_req_VIA_TC3, or TC_U_REJECT_req_VIA_TC3.](083e35cb1266483c58c5b483d57b4219_img.jpg) + +**Process Performing\_MAP\_SSM** MAP\_PSSM2(2) + +Process to handle an invoke component received from the peer and the response from the user + +``` + +stateDiagram-v2 + [*] --> WAIT_FOR_RESPONSE + WAIT_FOR_RESPONSE --> Guard_Timer_Expired + WAIT_FOR_RESPONSE --> Response_Issued + WAIT_FOR_RESPONSE --> Terminated + Guard_Timer_Expired --> [*] + Terminated --> [*] + Response_Issued --> User_Error_Present + User_Error_Present -- TRUE --> Specific_Error + User_Error_Present -- FALSE --> Linked_Request + Specific_Error -- TRUE --> Set_Error_Code + Specific_Error -- FALSE --> Set_Problem_Code + Linked_Request -- TRUE --> Set_Operation_Code_and_TCAP_Param + Linked_Request -- FALSE --> Length_O.K. + Length_O.K. -- TRUE --> TC_RESULT_L_req_VIA_TC3 + Length_O.K. -- FALSE --> Split_info + Split_info --> 2 + 2 --> TC_RESULT_NL_req_VIA_TC3 + TC_RESULT_NL_req_VIA_TC3 --> more_data + more_data -- TRUE --> 2 + more_data -- FALSE --> TC_RESULT_L_req_VIA_TC3 + Set_Operation_Code_and_TCAP_Param --> TC_INVOKE_req_VIA_TC3 + Set_Error_Code --> TC_U_ERROR_req_VIA_TC3 + Set_Problem_Code --> TC_U_REJECT_req_VIA_TC3 + TC_INVOKE_req_VIA_TC3 --> [*] + TC_U_ERROR_req_VIA_TC3 --> [*] + TC_U_REJECT_req_VIA_TC3 --> [*] + TC_RESULT_L_req_VIA_TC3 --> [*] + TC_RESULT_NL_req_VIA_TC3 --> [*] + Note right of Response_Issued: by the MAP user or the Secure_Performing_MAP_SSM + +``` + +State transition diagram for Process Performing\_MAP\_SSM (sheet 1). The process starts at WAIT\_FOR\_RESPONSE and branches based on Guard\_Timer\_Expired, Response\_Issued, or Terminated. Response\_Issued leads to User\_Error\_Present, which then branches to Linked\_Request or Specific\_Error. These lead to various processing steps like Length\_O.K., Split\_info, TC\_RESULT\_NL\_req\_VIA\_TC3, more\_data, Set\_Operation\_Code\_and\_TCAP\_Param, Set\_Error\_Code, Set\_Problem\_Code, and finally TC\_INVOKE\_req\_VIA\_TC3, TC\_U\_ERROR\_req\_VIA\_TC3, or TC\_U\_REJECT\_req\_VIA\_TC3. + +Figure 15.6/8b: Process Performing\_MAP\_SSM (sheet 2) + +9500 + +9501 + +--- + +## 9502 16 Mapping on to TC services + +### 9503 16.1 Dialogue control + +9504 Dialogue control services are mapped to TC dialogue handling services. The TC-UNI service is not used by the MAP +9505 PM. + +#### 9506 16.1.1 Directly mapped parameters + +9507 The following parameters of the MAP-OPEN request and indication primitives are directly mapped on to the +9508 corresponding parameters of the TC-BEGIN primitives: + +- 9509 - destination address; +- 9510 - originating address. + +#### 9511 16.1.2 Use of other parameters of dialogue handling primitives + +##### 9512 16.1.2.1 Dialogue Id + +9513 The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner. + +##### 9514 16.1.2.2 Application-context-name + +9515 The application-context-name parameter of a MAP primitive is mapped to the application-context-name parameter of +9516 TC dialogue handling primitives according to the rules described in clause 15.1. + +##### 9517 16.1.2.3 User information + +9518 The user information parameter of TC dialogue primitives is used to carry the MAP dialogue APDUs. + +##### 9519 16.1.2.4 Component present + +9520 This parameter is used by the MAP PM as described in CCITT Recommendation Q.771. It is not visible to the MAP +9521 user. + +##### 9522 16.1.2.5 Termination + +9523 The value of this parameter of the TC-END request primitive is set by the MAP PM on the basis of the release method +9524 parameter of the MAP-CLOSE request primitive, except when the dialogue state machine is in the state DIALOGUE +9525 INITIATED, in which case the Termination parameter shall always indicate "pre-arranged end". + +##### 9526 16.1.2.6 P-Abort-Cause + +9527 Values of the P-abort-cause parameter are mapped to the values of the provider-reason parameter of the +9528 MAP-P-ABORT indication primitive according to table 16.1/1, except in the dialogue initiated phase for the +9529 "incorrectTransactionPortion" and "noCommonDialoguePortion" values which are mapped to the "potential +9530 incompatibility problem" value of the refuse-reason parameter of the MAP-OPEN cnf primitive. The source parameter +9531 in the MAP-P-ABORT ind takes the value "TC problem". + +##### 9532 16.1.2.7 Quality of service + +9533 The quality of service of TC request primitives is set by the MAP as shown below. + +- 9534 - Return option: "Return message on error" or "Discard message on error" as required by the network operator; +- 9535 - Sequence control: "Sequence guaranteed" or "Sequence result not guaranteed" as required by the network operator; +- 9536 +- 9537 - "Sequence guaranteed" shall be used when a segmented result is to be transferred (e.g. subscriber data in +- 9538 response to SendParameters). It may also be appropriate to use Sequence guaranteed when a series of +- 9539 InsertSubscriberData, ProcessAccessSignalling or ForwardAccessSignalling operations is used. + +9540 It is essential that the TC message which indicates acceptance of a dialogue opening request is received by the dialogue +9541 initiator before any subsequent message in that dialogue; otherwise the dialogue opening will fail. The dialogue +9542 responder shall ensure that this requirement is met by: + +- 9543 - Sending the dialogue acceptance message in a TC-END, if the dialogue structure requires it; or +- 9544 - Using "Sequence guaranteed", if the dialogue acceptance message is sent in a TC-CONTINUE; or +- 9545 - Waiting until the dialogue acceptance message has been acknowledged by the dialogue initiator before sending a +- 9546 subsequent message, if the dialogue acceptance message is sent in a TC-CONTINUE. + +9547 **Table 16.1/1: Mapping of P-Abort cause in TC-P-ABORT indication** +9548 **on to provider-reason in MAP-P-ABORT indication** + +| TC P-Abort cause | MAP provider-reason | +|-------------------------------------------------------------------|------------------------------| +| unrecognised message type | provider malfunction | +| unrecognised transaction Id | supporting dialogue released | +| badlyFormattedTransactionPotion | provider malfunction | +| incorrectTransactionPotion | provider malfunction (note) | +| resourceLimitation | resource limitation | +| abnormalDialogue | provider malfunction | +| noCommonDialoguePotion | version incompatibility | +| NOTE: Or version incompatibility in the dialogue initiated phase. | | + +9549 + +## 9550 16.2 Service specific procedures + +9551 Specific services are mapped to TC component handling services. + +### 9552 16.2.1 Directly mapped parameters + +9553 The Invoke Id parameter of the MAP request and indication primitive is directly mapped on to the Invoke Id parameter +9554 of the component handling primitives. + +### 9555 16.2.2 Use of other parameters of component handling primitives + +#### 9556 16.2.2.1 Dialogue Id + +9557 The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner. + +#### 9558 16.2.2.2 Class + +9559 The value of this parameter is set by the MAP PM according to the type of the operation to be invoked. + +#### 9560 16.2.2.3 Linked Id + +9561 When a service response is mapped to a class 4 operation, the value of this parameter is set by the MAP PM and +9562 corresponds to the value assigned by the user to the initial service request (i.e. the value of the invoke ID parameter of + +9563 the request primitive). Otherwise if such a parameter is included in MAP request/indication primitives it is directly + 9564 mapped to the linked ID parameter of the associated TC-INVOK request/indication primitives. + +## 9565 16.2.2.4 Operation + +9566 When mapping a request primitive on to a Remote Operations PDU (invoke), the MAP PM shall set the operation code + 9567 according to the mapping described in table 16.2/1. + +9568 When mapping a response primitive on to a Remote Operations service, the MAP PM shall set the operation code of the + 9569 TC-RESULT-L/NL primitive (if required) to the same value as the one received at invocation time. + +9570 **Table 16.2/1: Mapping of MAP specific services on to MAP operations** + +| | | +|-----------------------------------------|----------------------------------| +| MAP-SERVICE | operation | +| MAP-ACTIVATE-SS | activateSS | +| MAP-ACTIVATE-TRACE-MODE | activateTraceMode | +| MAP-ALERT-SERVICE-CENTRE | alertServiceCentre | +| MAP-ANY-TIME-INTERROGATION | anyTimeInterrogaton | +| MAP_AUTHENTICATION_FAILURE_REPORT | authenticationFailureReport | +| MAP-ANY-TIME-MODIFICATION | anyTimeModification | +| MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION | anyTimeSubscriptionInterrogation | +| MAP-CANCEL-LOCATION | cancelLocation | +| MAP-CHECK-IMEI | checkIMEI | +| MAP-DEACTIVATE-SS | deactivateSS | +| MAP-DEACTIVATE-TRACE-MODE | deactivateTraceMode | +| MAP-DELETE-SUBSCRIBER-DATA | deleteSubscriberData | +| MAP-ERASE-CC-ENTRY | eraseCC-Entry | +| MAP-ERASE-SS | eraseSS | +| MAP-FAILURE-REPORT | failureReport | +| MAP-FORWARD-ACCESS-SIGNALLING | forwardAccessSignalling | +| MAP-FORWARD-CHECK-SS-INDICATION | forwardCheckSsIndication | +| MAP-FORWARD-GROUP-CALL-SIGNALLING | forwardGroupCallSignalling | +| MAP-MT-FORWARD-SHORT-MESSAGE | mt-forwardSM | +| MAP-MO-FORWARD-SHORT-MESSAGE | mo-forwardSM | +| MAP-GET-PASSWORD | getPassword | +| MAP-INFORM-SERVICE-CENTRE | informServiceCentre | +| MAP-INSERT-SUBSCRIBER-DATA | insertSubscriberData | +| MAP-INTERROGATE-SS | interrogateSs | +| MAP-IST-ALERT | istAlert | +| MAP-IST-COMMAND | istCommand | +| MAP-NOTE-MS-PRESENT-FOR-GPRS | noteMsPresentForGprs | +| MAP-NOTE-SUBSCRIBER-DATA-MODIFIED | noteSubscriberDataModified | +| MAP-PREPARE-GROUP-CALL | prepareGroupCall | +| MAP-PREPARE-HANDOVER | prepareHandover | +| MAP-PREPARE-SUBSEQUENT-HANDOVER | prepareSubsequentHandover | +| MAP-PROCESS-ACCESS-SIGNALLING | processAccessSignalling | +| MAP-PROCESS-GROUP-CALL-SIGNALLING | processGroupCallSignalling | +| MAP-PROCESS-UNSTRUCTURED-SS-REQUEST | processUnstructuredSS-Request | +| MAP-PROVIDE-ROAMING-NUMBER | provideRoamingNumber | +| MAP-PROVIDE-SUBSCRIBER-LOCATION | provideSubscriberLocation | +| MAP-PROVIDE-SUBSCRIBER-INFO | provideSubscriberInfo | +| MAP-PURGE-MS | purgeMS | +| MAP-READY-FOR-SM | readyForSM | +| MAP-REGISTER-CC-ENTRY | registerCC-Entry | +| MAP-REGISTER-PASSWORD | registerPassword | +| MAP-REGISTER-SS | registerSS | +| MAP-REMOTE-USER-FREE | remoteUserFree | +| MAP-REPORT-SM-DELIVERY-STATUS | reportSmDeliveryStatus | +| MAP-RESET | reset | +| MAP-RESTORE-DATA | restoreData | +| MAP-SEND_GROUP_CALL_END_SIGNAL | sendGroupCallEndSignal | +| MAP-SEND-GROUP-CALL-INFO | sendGroupCallInfo | +| MAP-SEND-END-SIGNAL | sendEndSignal | + +| | | +|---------------------------------------------------|----------------------------| +| MAP-SEND-AUTHENTICATION-INFO | sendAuthenticationInfo | +| MAP-SEND-IMSI | sendIMSI | +| MAP-SEND-IDENTIFICATION | sendIdentification | +| MAP-SEND-ROUTING-INFO-FOR-SM | sendRoutingInfoForSM | +| MAP-SEND-ROUTING-INFO-FOR-GPRS | sendRoutingInfoForGprs | +| MAP-SEND-ROUTING-INFO-FOR-LCS | sendRoutingInfoForLCS | +| MAP-SEND-ROUTING-INFORMATION | sendRoutingInfo | +| MAP-SET-REPORTING-STATE | setReportingState | +| MAP-STATUS-REPORT | statusReport | +| MAP-SUBSCRIBER-LOCATION-REPORT | subscriberLocationReport | +| MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION | ss-Invocation-Notification | +| MAP-UNSTRUCTURED-SS-NOTIFY | unstructuredSS-Notify | +| MAP-UNSTRUCTURED-SS-REQUEST | unstructuredSS-Request | +| MAP-UPDATE-GPRS-LOCATION | updateGprsLocation | +| MAP-UPDATE-LOCATION | updateLocation | +| MAP-NOTE-MM-EVENT | NoteMM-Event | +| MAP-UPDATE-VCSG-LOCATION | updateVcsgLocation | +| MAP-CANCEL-VCSG-LOCATION | cancelVcsgLocation | + +9571 + +## 9572 16.2.2.5 Error + +9573 The error parameter in a TC-U-ERROR indication primitive is mapped to the user error parameter in the MAP confirm +9574 primitive of the service associated with the operation to which the error is attached. + +9575 The user error parameter in MAP response primitives is mapped to the error parameter of the TC-U-ERROR request +9576 primitive, except for "initiating-release" and "resource-limitation" which are mapped to the problem code parameter of +9577 the TC-U-REJECT request primitive. + +## 9578 16.2.2.6 Parameters + +9579 The parameters of MAP specific request and indication primitives are mapped to the argument parameter of TC- +9580 INVOKE primitives. + +9581 The parameters of MAP specific response and confirm primitives are mapped to the result parameter of TC-RESULT-L +9582 primitives, the parameter of TC-U-ERROR primitives or the argument of TC-INVOKE primitives when mapping on +9583 linked class 4 operations is used. + +## 9584 16.2.2.7 Time out + +9585 The value of this parameter is set by the MAP PM according to the type of operation invoked. + +## 9586 16.2.2.8 Last component + +9587 This parameter is used by the MAP PM as described in CCITT Recommendation Q.711. It is not visible from the MAP +9588 user. + +## 9589 16.2.2.9 Problem code + +### 9590 16.2.2.9.1 Mapping to MAP User Error + +9591 The following values of the user error parameter are mapped as follows to values of the TC problem code parameter. +9592 These values are generated by the MAP user. This mapping is valid from the TC-U-REJECT indication primitive to the +9593 MAP confirm service primitive and from the MAP response service primitive to the TC-U-REJECT request primitive. + +9594 **Table 16.2/2: Mapping of MAP User Error parameter on to TC problem code** +9595 **in TC-U-REJECT primitives** + +| MAP User Error | TC problem code | +|---------------------|---------------------| +| resource limitation | resource limitation | +| initiating release | initiating release | + +9596 + +9597 16.2.2.9.2 Mapping to MAP Provider Error parameter + +9598 The following values of the TC problem code parameter of the TC-U-REJECT indication primitive are mapped as +9599 follows to values of the MAP Provider Error parameter of the MAP confirm primitive. + +9600 **Table 16.2/3: Mapping of TC problem code in TC-U-REJECT on to MAP Provider Error parameter** + +| TC problem code | MAP Provider Error | +|------------------------|-----------------------| +| duplicated invoke Id | duplicated invoke id | +| unrecognised operation | service not supported | +| mistyped parameter | mistyped parameter | + +9601 + +9602 The following values of the problem code parameters of the TC-L-REJECT primitive are mapped to values of the +9603 provider error parameter of the MAP confirm primitive as follows. + +9604 **Table 16.2/4: Mapping of TC problem code in TC-L-REJECT on to MAP Provider Error parameter** + +| TC problem code | MAP Provider Error | +|--------------------------|-----------------------------------| +| return result unexpected | unexpected response from the peer | +| return error unexpected | unexpected response from the peer | + +9605 + +9606 16.2.2.9.3 Mapping to diagnostic parameter + +9607 The following values of the problem code parameter of the TC-R-REJECT and TC-U-REJECT primitive are mapped to +9608 values of the diagnostic parameter of the MAP-NOTICE indication primitive as follows: + +9609 **Table 16.2/5: Mapping of TC problem code of TC-R-REJECT and TC-U-REJECT** +9610 **on to diagnostic parameter** + +| TC problem code | MAP diagnostic | +|-------------------------------|---------------------------------------| +| General problem | - abnormal event detected by the peer | +| Invoke problem | | +| - unrecognised linked ID | - abnormal event detected by the peer | +| - linked response unexpected | - response rejected by the peer | +| - unexpected linked operation | - response rejected by the peer | +| Return result problem | | +| - unrecognised invoke ID | - response rejected by the peer | +| - return result unexpected | - response rejected by the peer | +| - mistyped parameter | - response rejected by the peer | +| Return error problem | | +| - unrecognised invoke ID | - response rejected by the peer | +| - return error unexpected | - response rejected by the peer | +| - unrecognised error | - response rejected by the peer | +| - unexpected error | - response rejected by the peer | +| - mistyped parameter | - response rejected by the peer | + +9611 + +9612 The following values of the problem code parameter of the TC-L-REJECT primitive are mapped to values of the +9613 diagnostic parameter of the MAP-NOTICE indication primitive as follows. + +9614 **Table 16.2/6: Mapping of TC problem code of TC-L-REJECT on to diagnostic parameter** + +| TC problem code | MAP diagnostic | +|--------------------------|-----------------------------------------| +| General problems | - abnormal event received from the peer | +| Invoke problem | | +| - unrecognised linked ID | - abnormal event received from the peer | +| Return result problem | | +| - unrecognised invoke ID | - abnormal event received from the peer | +| Return error problem | | +| - unrecognised invoke ID | - abnormal event received from the peer | + +9615 + +--- + +# 9616 17 Abstract syntax of the MAP protocol + +## 9617 17.1 General + +9618 This clause specifies the Abstract Syntaxes for the Mobile Application Part as well as the associated set of Operations +9619 and Errors, using the Abstract Syntax Notation One (ASN.1), defined in ITU-T Recommendations X.680 and X.681 +9620 with additions as defined in clause 17.1.4 on Compatibility Considerations and the OPERATION and ERROR external +9621 information object classes, defined in ITU-T Recommendation X.880. + +9622 The Abstract Syntax is defined for all interfaces specified in clause 4.4 except for the A- and B-interfaces. + +9623 The Mobile Application Part protocol is defined by two Abstract Syntaxes: + +9624 - one Abstract Syntax which encompass all Operations and Errors identified by the various MAP subsystem +9625 numbers. + +9626 This Abstract Syntax represents the set of values each of which is a value of the ASN.1 type TCAPMessages. +9627 TCMessage as defined in ITU-T Recommendation Q.773 with the component relationconstraint clauses resolved by the +9628 operation and error codes included in the ASN.1 modules MAP-\*Operations and MAP-Errors. However, only the +9629 subset of this abstract syntax which is required by the procedures defined for an entity needs to be supported. + +9630 - one Abstract Syntax identified by the OBJECT IDENTIFIER value MAP-DialogueInformation.map- +9631 DialogueAS. + +9632 This Abstract Syntax represents the set of values each of which is a value of the ASN.1 type MAP- +9633 DialogueInformation.MAP-DialoguePDU. Such a value of the ASN.1 single-ASN.1-type element is contained within +9634 the user-information element of the TCAPMessages.DialoguePortion ASN.1 type. This Abstract Syntax name is to be +9635 used as a direct reference. + +## 9636 17.1.1 Encoding rules + +9637 The encoding rules which are applicable to the defined Abstract Syntaxes are the Basic Encoding Rules for Abstract +9638 Syntax Notation One, defined in ITU-T Recommendation X.690 with the same exceptions as in ITU-T +9639 Recommendation Q.773, clause 4 Message Representation. + +9640 When the definite form is used for length encoding, a data value of length less than 128 octets must have the length +9641 encoded in the short form. + +9642 When the long form is employed to code a length, the minimum number of octets shall be used to code the length field. + +9643 OCTET STRING values and BIT STRING values must be encoded in a primitive form. + +9644 There is no restriction to the use of empty constructors (e.g. an empty SEQUENCE type). That is, the encoding of the +9645 content of any data value shall consist of zero, one or more octets. + +## 9646 17.1.2 Use of TC + +9647 The mapping of OPERATION and ERROR to TC components is defined in ETS 300 287 (version 2) which is based on +9648 ITU-T Recommendation Q.773. + +9649 NOTE 1: The class of an operation is not stated explicitly but is specified as well in the ASN.1 operation definition. + +9650 Class 1: RESULT and ERROR appear in ASN.1 operation definition. + +9651 Class 2: only ERROR appears in ASN.1 operation definition. + +9652 Class 3: only RESULT appears in ASN.1 operation definition. + +9653 Class 4: both RESULT and ERROR do not appear in ASN.1 operation definition. + +9654 The field "ARGUMENT", "PARAMETER" or "RESULT" (for information objects of class OPERATION and +9655 ERROR) is always optional from a syntactic point of view. However, except when specifically mentioned with the + +9656 ASN.1 comment "-- optional" , the "parameter" part of a component has to be considered as mandatory from a semantic +9657 point of view. + +9658 When an optional element is missing in an invoke component or in an inner data structure while it is required by the +9659 context, an error component is returned if specified in the information object associated with the operation ; the +9660 associated type of error is "DataMissing". This holds also when the entire parameter of an invoke component is missing +9661 while it is required by the context. + +9662 NOTE 2: When a mandatory element is missing in the parameter or inner data structure of any component, a reject +9663 component is returned (if the dialogue still exists). The problem code to be used is "Mistyped parameter". + +9664 The Timer Values used in the operation definitions are indicated as ASN.1 comments. The Timer Value Ranges are: + +9665 s = from 3 seconds to 10 seconds; + +9666 m = from 15 seconds to 30 seconds; + +9667 ml = from 1 minute to 10 minutes; + +9668 l = from 28 hours to 38 hours. + +### 9669 17.1.2.1 Use of Global Operation and Error codes defined outside MAP + +9670 An entity supporting an application context greater than 2 shall be capable of receiving an operation or error code, +9671 within an application context defined in GSM 29.002, encoded as either an Object Identifier (as defined in ITU-T +9672 Recommendation X.690 ) or an integer value (as defined in clause 17.5). Related restrictions regarding the use of +9673 Object Identifiers are as follows: + +9674 - The length of the Object Identifier shall not exceed 16 octets and the number of components of the Object +9675 Identifier shall not exceed 16. + +9676 - Object Identifiers shall be used only for operations or errors defined outside of GSM 29.002. + +9677 - Global error codes may be sent only in response to a global operation. If a standard operation is received then +9678 a global error code shall not be sent in response. + +9679 Handling of an unknown operation codes by the receiving entity is defined in clause 15.1.1. + +### 9680 17.1.3 Use of information elements defined outside MAP + +9681 An information element or a set of information elements (messages) transparently carried in the Mobile Application +9682 Part but defined in other recommendations/technical specifications are handled in one of the following ways: + +9683 i) The contents of each information element (without the octets encoding the identifier and the length in the +9684 recommendation/technical specification where it is defined unless explicitly stated otherwise) is carried as the +9685 value of an ASN.1 type derived from the OCTET STRING data type. Additionally, the internal structure may be +9686 explained by means of comments. In case of misalignment the referred to recommendation/technical +9687 specification takes precedence. + +9688 ii) The complete information element (including the octets encoding the identifier and the length in the +9689 recommendation/technical specification where it is defined) or set of information elements and the identity of the +9690 associated protocol are carried as the value of the ExternalSignalInfo data type defined in the present document. +9691 Where more than one information element is carried, the information elements are sent contiguously with no +9692 filler octets between them. + +### 9693 17.1.4 Compatibility considerations + +9694 The following ASN.1 modules conform to ITU-T Recommendation X.680 and X.681 . An extension marker ("...") is +9695 used wherever future protocol extensions are foreseen. + +9696 The "..." construct applies only to SEQUENCE and ENUMERATED data types. An entity supporting a version greater +9697 than 1 shall not reject an unsupported extension following "..." of that SEQUENCE or ENUMERATED data type. The + +9698 Encoding Rules from clause 17.1.1 apply to every element of the whole Transfer Syntax especially to the ASN.1 type +9699 EXTERNAL. + +9700 The extension container "privateExtensionList" is defined in this specification in order to carry extensions which are +9701 defined outside this specification. Private extensions can be defined by, for example, network operators, manufacturers, +9702 and regional standardisation bodies. + +9703 Private extensions shall: + +9704 1) if included in operations of an AC of V2, follow the extension marker and be tagged using PRIVATE tags up +9705 to and including 29. + +9706 NOTE: This type of extension is in most cases used only within a PLMN. + +9707 2) if included in operations of an AC of V3 or higher: be included only in the Private Extension Container that +9708 is defined in the specification. + +9709 NOTE: This type of extension can be used between PLMNs. + +9710 Private extensions shall not be included in v2 supplementary service operations. + +9711 Private extensions shall not be included within user error for RegisterCCEntry and EraseCCEntry operations. + +9712 PCS extensions shall be included in the PCS Extension Container that is defined in this specification. + +9713 In order to improve extensibility, a few error parameters have been defined as a CHOICE between the version 2 +9714 description and a SEQUENCE including the version 2 description and an extension container. Operations used in a v2- +9715 application-context must consider only the first alternative while operations used in a vn-application-context (n>2) must +9716 consider only the second alternative. + +## 9717 17.1.5 Structure of the Abstract Syntax of MAP + +9718 For each MAP parameter which has to be transferred by a MAP Protocol Data Unit (MAP message), there is a PDU +9719 field (an ASN.1 type) which has the same name as the corresponding parameter, except for the differences required by +9720 the ASN.1 notation (blanks between words are removed or replaced by hyphen, the first letter of the first word is capital +9721 and the first letter of each of the following words is capitalised, e.g. "no reply condition time" is mapped to +9722 "NoReplyConditionTime"). Additionally some words may be abbreviated as follows: + +9723 bs basic service +9724 ch call handling +9725 cug closed user group +9726 ho handover +9727 ic incoming call +9728 id identity +9729 info information +9730 mm mobility management +9731 lcs location services +9732 ms mobile service +9733 oc outgoing call +9734 om operation & maintenance +9735 pw Password +9736 sm short message service +9737 ss supplementary service + +9738 The MAP protocol is composed of several ASN.1 modules dealing with either operations, errors, data types, and, if +9739 applicable, split into those dealing with mobile services, call handling services, supplementary services and short +9740 message services. For operations and errors the code values are given as parameters, in order to allow use of the +9741 defined information objects also by other protocols (e.g. 3GPP TS 24.080 [38]). The ASN.1 source lines are preceded +9742 by line-numbers at the left margin in order to enable the usage of the cross-reference in annex A. + +9743 The module containing the definition of the operation packages for MAP is: + +9744 1. MAP-OperationPackages. + +9745 The module containing the definition of the application contexts for MAP is: + +9746 2. MAP-ApplicationContexts. + +9747 The module containing the data types for the Abstract Syntax to be used for TCAPMessages.DialoguePortion for MAP +9748 is: + +9749 3. MAP-DialogueInformation. + +9750 The module containing the supported operations is: + +9751 4. MAP-Protocol. + +9752 The modules containing all operation definitions for MAP are: + +9753 5. MAP-MobileServiceOperations; + +9754 6. MAP-OperationAndMaintenanceOperations; + +9755 7. MAP-CallHandlingOperations; + +9756 8. MAP-SupplementaryServiceOperations; + +9757 9. MAP-ShortMessageServiceOperations; + +9758 10. MAP-Group-Call-Operations; + +9759 11. MAP-LocationServiceOperations. + +9760 The module containing all error definitions for MAP is: + +9761 12. MAP-Errors. + +9762 Modules containing all data type definitions for MAP are: + +9763 13. MAP-MS-DataTypes; + +9764 14. MAP-OM-DataTypes; + +9765 15. MAP-CH-DataTypes; + +9766 16. MAP-SS-DataTypes; + +9767 17. MAP-SS-Code; + +9768 18. MAP-SM-DataTypes; + +9769 19. MAP-ER-DataTypes; + +9770 20. MAP-CommonDataTypes; + +9771 21. MAP-TS-Code; + +9772 22. MAP-BS-Code; + +9773 23. MAP-ExtensionDataTypes; + +9774 24. MAP-GR-DataTypes; + +9775 25. MAP-LCS-DataTypes. + +9776 References are made also to modules defined outside of the present document. They are defined in the technical +9777 specification Mobile Services Domain, technical specification Transaction Capability and ITU-T Recommendation +9778 X.880 respectively: + +9779 MobileDomainDefinitions; + +9780 TCAPMessages, DialoguePDUs ; + +9781 Remote-Operations-Information-Objects. + +## 9782 17.1.6 Application Contexts + +9783 The following informative table lists the latest versions of the Application Contexts used in this specification, with the +9784 operations used by them and, where applicable, whether or not the operation description is exactly the same as for +9785 previous versions. Information in 17.6 & 17.7 relates only to the ACs in this table. + +9786 + +| AC Name | AC Version | Operations Used | Comments | +|------------------------------|------------|---------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------| +| locationCancellationContext | v3 | cancelLocation | | +| equipmentMngtContext | V3 | checkIMEI | | +| imsiRetrievalContext | v2 | sendIMSI | | +| infoRetrievalContext | v3 | sendAuthenticationInfo | | +| interVlrInfoRetrievalContext | v3 | sendIdentification | | +| handoverControlContext | v3 | prepareHandover
forwardAccessSignalling
sendEndSignal
processAccessSignalling
prepareSubsequentHandover | the syntax of this operation has been extended in comparison with release 98 version | +| mwdMngtContext | v3 | readyForSM | | +| msPurgingContext | v3 | purgeMS | | +| shortMsgAlertContext | v2 | alertServiceCentre | | +| resetContext | v3 | reset | | +| networkUnstructuredSsContext | v2 | processUnstructuredSS-Request
unstructuredSS-Request
unstructuredSS-Notify | | +| tracingContext | v3 | activateTraceMode
deactivateTraceMode | | +| networkFunctionalSsContext | v2 | registerSS
eraseSS
activateSS
deactivateSS
registerPassword
interrogateSS
getPassword | | +| shortMsgMO-RelayContext | v3 | mo-forwardSM | | +| shortMsgMT-RelayContext | v3 | mt-forwardSM | | +| shortMsgMT-VGCS-RelayContext | v3 | mt-forwardSM-VGCS | | +| shortMsgGatewayContext | v3 | sendRoutingInfoForSM
reportSM-DeliveryStatus
InformServiceCentre | the syntax of this operation has been extended in comparison with release 96 version | +| networkLocUpContext | v3 | updateLocation
forwardCheckSs-Indication
restoreData
insertSubscriberData
activateTraceMode | the syntax is the same in v1 & v2 | +| gprsLocationUpdateContext | v3 | updateGprsLocation
insertSubscriberData
activateTraceMode | | +| subscriberDataMngtContext | v3 | insertSubscriberData | | + +| AC Name | AC Version | Operations Used | Comments | +|-----------------------------------------------|------------|--------------------------------------------------------------------------------------------------------|----------| +| | | deleteSubscriberData | | +| roamingNumberEnquiryContext | v3 | provideRoamingNumber | | +| locationInfoRetrievalContext | v3 | sendRoutingInfo | | +| gprsNotifyContext | v3 | noteMsPresentForGprs | | +| gprsLocationInfoRetrievalContext | v4 | sendRoutingInfoForGprs | | +| failureReportContext | v3 | failureReport | | +| callControlTransferContext | v4 | resumeCallHandling | | +| subscriberInfoEnquiryContext | v3 | provideSubscriberInfo | | +| anyTimeEnquiryContext | v3 | anyTimeInterrogation | | +| anyTimeInfoHandlingContext | v3 | anyTimeSubscriptionInterrogation
anyTimeModification | | +| ss-InvocationNotificationContext | v3 | ss-InvocationNotification | | +| groupCallControlContext | v3 | prepareGroupCall
processGroupCallSignalling
forwardGroupCallSignalling
sendGroupCallEndSignal | | +| reportingContext | v3 | setReportingState
statusReport
remoteUserFree | | +| callCompletionContext | v3 | registerCC-Entry
eraseCC-Entry | | +| istAlertingContext | v3 | istAlert | | +| ServiceTerminationContext | v3 | istCommand | | +| locationSvcEnquiryContext | v3 | provideSubscriberLocation
subscriberLocationReport | | +| locationSvcGatewayContext | v3 | sendRoutingInfoForLCS | | +| mm-EventReportingContext | v3 | noteMM-Event | | +| subscriberDataModificationNotificationContext | v3 | noteSubscriberDataModified | | +| authenticationFailureReportContext | v3 | authenticationFailureReport | | +| resourceManagementContext | v3 | releaseResources | | +| groupCallInfoRetrievalContext | v3 | sendGroupCallInfo | | +| vcsgLocationUpdateContext | v3 | updateVcsgLocation
insertSubscriberData | | +| vcsgLocationCancelContext | v3 | cancelVcsgLocation | | + +9787 + +9788 NOTE (\*): The syntax of the operations is not the same as in previous versions unless explicitly stated + +## 9789 17.2 Operation packages + +### 9790 17.2.1 General aspects + +9791 This clause describes the operation-packages which are used to build the application-contexts defined in clause 17.3. + +9792 Each operation-package is a specification of the roles of a pair of communicating objects (i.e. a pair of MAP-Providers), +9793 in terms of operations which they can invoke of each other. + +9794 The grouping of operations into one or several packages does not necessarily imply any grouping in terms of +9795 Application Service Elements. + +9796 The following ASN.1 information object class is used to describe operation-packages in this clause: + +``` + +9797 OPERATION-PACKAGE ::= CLASS { +9798 &Both OPERATION OPTIONAL, +9799 &Consumer OPERATION OPTIONAL, +9800 &Supplier OPERATION OPTIONAL, +9801 &id OBJECT IDENTIFIER UNIQUE OPTIONAL } +9802 WITH SYNTAX { +9803 [ OPERATIONS &Both ] +9804 [ CONSUMER INVOKES &Supplier ] +9805 [ SUPPLIER INVOKES &Consumer ] +9806 [ ID &id ] } +9807 + +``` + +9808 Since the application-context definitions provided in clause 17.3 use only an informal description technique, only the +9809 type notation is used in the following clauses to define operation-packages. + +9810 The following definitions are used throughout this clause (n>=2): + +- 9811 - v1-only operation: An operation which shall be used only in v1 application-contexts; +- 9812 - vn-only operation: An operation which shall be used only in vn application-contexts; +- 9813 - v(n-1)-operation: An operation whose specification has not been modified since the MAP v(n-1) specifications +9814 or if the modifications are considered as not affecting v(n-1) implementations; +- 9815 - v(n-1)-equivalent operation: The version of an operation which excludes all the information elements and errors +9816 which have been added since the MAP v(n-1) specification; +- 9817 - vn-only package: An operation package which contains only vn-only operations; +- 9818 - v(n-1)-package: An operation package which contains only v(n-1)- operations. + +9819 The names of vn-packages are suffixed by "-vn" where n>=2. + +9820 For each operation package which is not vn-only (n>=2) and which does not include only v(n-1)-operations, there is a +9821 v(n-1)-equivalent package. Except when a definition is explicitly provided in the following clauses, the +9822 v(n-1)-equivalent package includes the v(n-1)-equivalent operations of the operations which belong to this package. + +## 9823 17.2.2 Packages specifications + +### 9824 17.2.2.1 Location updating + +9825 This operation package includes the operations required for location management procedures between HLR and VLR. + +``` + +9826 LocationUpdatingPackage-v3 OPERATION-PACKAGE ::= { +9827 -- Supplier is HLR if Consumer is VLR +9828 CONSUMER INVOKES { +9829 updateLocation} +9830 SUPPLIER INVOKES { +9831 forwardCheckSs-Indication} } +9832 + +``` + +9833 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1. + +### 9834 17.2.2.2 Location cancellation + +9835 This operation package includes the operations required for location cancellation and MS purging procedures between +9836 HLR and VLR and between HLR and SGSN. + +``` + +9837 LocationCancellationPackage-v3 OPERATION-PACKAGE ::= { +9838 -- Supplier is VLR or SGSN if Consumer is HLR +9839 CONSUMER INVOKES { +9840 cancelLocation} } +9841 + +``` + +9842 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1. + +### 9843 17.2.2.3 Roaming number enquiry + +9844 This operation package includes the operations required for roaming number enquiry procedures between HLR or old +9845 VLR and VLR. + +``` +9846 roamingNumberEnquiryPackage-v3 OPERATION-PACKAGE ::= { +9847 -- Supplier is VLR if Consumer is HLR or old VLR +9848 CONSUMER INVOKES { +9849 provideRoamingNumber} } +``` + +9850 +9851 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1. + +### 9852 17.2.2.4 Information retrieval + +9853 This operation package includes the operation required for the authentication information retrieval procedure between +9854 HLR and VLR and between HLR and SGSN. + +``` +9855 infoRetrievalPackage-v3 OPERATION-PACKAGE ::= { +9856 -- Supplier is HLR if Consumer is VLR +9857 -- Supplier is HLR if Consumer is SGSN +9858 CONSUMER INVOKES { +9859 sendAuthenticationInfo} } +``` + +9860 +9861 The v2-equivalent package is defined as follows: + +``` +9862 infoRetrievalPackage-v2 OPERATION-PACKAGE ::= { +9863 -- Supplier is HLR if Consumer is VLR +9864 -- Supplier is HLR if Consumer is SGSN +9865 CONSUMER INVOKES { +9866 sendAuthenticationInfo} } +``` + +9867 +9868 The v1-equivalent package is defined as follows: + +``` +9869 infoRetrievalPackage-v1 OPERATION-PACKAGE ::= { +9870 -- Supplier is HLR or VLR if Consumer is VLR +9871 -- Supplier is HLR if Consumer is SGSN +9872 CONSUMER INVOKES { +9873 sendParameters} } +``` + +### 9875 17.2.2.5 Inter-VLR information retrieval + +9876 This operation package includes the operations required for inter VLR information retrieval procedures. + +``` +9877 interVlrInfoRetrievalPackage-v3 OPERATION-PACKAGE ::= { +9878 -- Supplier is VLR if Consumer is VLR +9879 CONSUMER INVOKES { +9880 sendIdentification} } +``` + +9881 +9882 The v2-equivalent package is defined as follows: + +``` +9883 interVlrInfoRetrievalPackage-v2 OPERATION-PACKAGE ::= { +9884 -- Supplier is VLR if Consumer is VLR +9885 CONSUMER INVOKES { +9886 sendIdentification} } +``` + +9887 +9888 The v1-equivalent package is : infoRetrievalPackage-v1. + +### 9889 17.2.2.6 IMSI retrieval + +9890 This operation package includes the operation required for the IMSI retrieval procedure between HLR and VLR. + +``` +9891 imsiRetrievalPackage-v2 OPERATION-PACKAGE ::= { +9892 -- Supplier is HLR if Consumer is VLR +9893 CONSUMER INVOKES { +9894 sendIMSI} } +``` + +9895 +9896 This package is v2 only. + +### 9897 17.2.2.7 Call control transfer + +9898 This operation package includes the operation required for the call control transfer procedure between VMSC and +9899 GMSC. + +``` +9900 callControlTransferPackage-v4 OPERATION-PACKAGE ::= { +9901 -- Supplier is GMSC if Consumer is VMSC +9902 CONSUMER INVOKES { +9903 resumeCallHandling} } +``` + +9904 +9905 The v3-equivalent package can be determined according to the rules described in clause 17.2.1. + +### 9906 17.2.2.8 Void + +### 9907 17.2.2.9 Void + +### 9908 17.2.2.10 Interrogation + +9909 This operation package includes the operations required for interrogation procedures between MSC and HLR or NPLR +9910 or between HLR and gsmSCF. + +``` +9911 interrogationPackage-v3 OPERATION-PACKAGE ::= { +9912 -- Supplier is HLR or NPLR if Consumer is MSC +9913 -- Supplier is HLR if Consumer is gsmSCF +9914 CONSUMER INVOKES { +9915 sendRoutingInfo} } +``` + +9916 +9917 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1. + +### 9918 17.2.2.11 Void + +### 9919 17.2.2.12 Handover Control + +9920 This operation package includes the operations required for handover procedures between MSCs. + +``` +9921 handoverControlPackage-v3 OPERATION-PACKAGE ::= { +9922 -- Supplier is MSCB if Consumer is MSCA +9923 CONSUMER INVOKES { +9924 prepareHandover | +9925 forwardAccessSignalling} +9926 SUPPLIER INVOKES { +9927 sendEndSignal | +9928 processAccessSignalling | +9929 prepareSubsequentHandover} } +``` + +9930 +9931 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. + +9932 The v1-equivalent package is defined as follows. + +``` +9933 handoverControlPackage-v1 OPERATION-PACKAGE ::= { +9934 -- Supplier is MSCB if Consumer is MSCA +9935 CONSUMER INVOKES { +9936 performHandover | +9937 forwardAccessSignalling | +9938 traceSubscriberActivity} +9939 SUPPLIER INVOKES { +9940 sendEndSignal | +9941 noteInternalHandover | +9942 processAccessSignalling | +9943 performSubsequentHandover} } +``` + +9944 + +### 9945 17.2.2.13 Subscriber Data management stand alone + +9946 This operation package includes the operations required for stand alone subscriber data management procedures +9947 between HLR and VLR or between HLR and SGSN. Also this operation package includes the operations required for +9948 stand alone subscriber data management procedures between CSS and VLR or between CSS and SGSN. For the CSS – +9949 VLR interface and CSS – SGSN interface only version 3 of this operation package is applicable. + +``` +9950 subscriberDataMngtStandAlonePackage-v3 OPERATION-PACKAGE ::= { +9951 -- Supplier is VLR or SGSN if Consumer is HLR or CSS +9952 CONSUMER INVOKES { +9953 insertSubscriberData | +9954 deleteSubscriberData} } +``` + +9956 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1. + +### 9957 17.2.2.14 Equipment management + +9958 This operation package includes the operations required for equipment management procedures between EIR and MSC +9959 or between EIR and SGSN. + +``` +9960 equipmentMngtPackage-v3 OPERATION-PACKAGE ::= { +9961 -- Supplier is EIR if Consumer is MSC +9962 -- Supplier is EIR if Consumer is SGSN +9963 CONSUMER INVOKES { +9964 checkIMEI} } +``` + +9966 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1. + +### 9967 17.2.2.15 Subscriber data management + +9968 This operation package includes the operations required for subscriber data management procedures between HLR and +9969 VLR or between HLR and SGSN. Also this operation package includes the operations required for subscriber data +9970 management procedures between CSS and VLR or between CSS and SGSN. For the CSS – VLR interface and CSS – +9971 SGSN interface only version 3 of this operation package is applicable. + +``` +9972 subscriberDataMngtPackage-v3 OPERATION-PACKAGE ::= { +9973 -- Supplier is VLR or SGSN if Consumer is HLR or CSS +9974 CONSUMER INVOKES { +9975 insertSubscriberData} } +``` + +9977 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1. + +### 9978 17.2.2.16 Location register restart + +9979 This operation package includes the operations required for location register restart procedures between HLR and VLR +9980 or between HLR and SGSN and also between CSS and VLR or between CSS and SGSN. + +``` +9981 resetPackage-v3 OPERATION-PACKAGE ::= { +9982 -- Supplier is VLR or SGSN if Consumer is HLR or CSS +9983 CONSUMER INVOKES { +9984 reset} } +``` + +9986 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1. + +9987 For CSS-VLR interface and CSS-SGSN interface, only version 3 of this operation package is applicable. + +### 9988 17.2.2.17 Tracing stand-alone + +9989 This operation package includes the operations required for stand alone tracing procedures between HLR and VLR or +9990 between HLR and SGSN. + +``` +9991 tracingStandAlonePackage-v3 OPERATION-PACKAGE ::= { +9992 -- Supplier is VLR or SGSN if Consumer is HLR +9993 CONSUMER INVOKE { +9994 activateTraceMode | +9995 deactivateTraceMode } } +``` + +9996 +9997 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1. + +### 9998 17.2.2.18 Functional SS handling + +9999 This operation package includes the operations required for functional supplementary services procedures between VLR +10000 and HLR. + +``` +10001 functionalSsPackage-v2 OPERATION-PACKAGE ::= { +10002 -- Supplier is HLR if Consumer is VLR +10003 CONSUMER INVOKE { +10004 registerSS | +10005 eraseSS | +10006 activateSS | +10007 deactivateSS | +10008 registerPassword | +10009 interrogateSS } +10010 SUPPLIER INVOKE { +10011 getPassword } } +``` + +10012 +10013 The v1-equivalent package can be determined according to the rules described in clause 17.2.1. + +### 10014 17.2.2.19 Tracing + +10015 This operation package includes the operations required for tracing procedures between HLR and VLR or between HLR +10016 and SGSN. + +``` +10017 tracingPackage-v3 OPERATION-PACKAGE ::= { +10018 -- Supplier is VLR or SGSN if Consumer is HLR +10019 CONSUMER INVOKE { +10020 activateTraceMode } } +``` + +10021 +10022 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1. + +### 10023 17.2.2.20 Binding + +10024 This operation package includes the operation required to initialise a supplementary service procedure between VLR +10025 and HLR or between gsmSCF and HLR. + +``` +10026 bindingPackage-v1 OPERATION-PACKAGE ::= { +10027 -- Supplier is HLR if Consumer is VLR +10028 -- Supplier is gsmSCF if Consumer is HLR +10029 CONSUMER INVOKE { +10030 beginSubscriberActivity } } +``` + +10031 This package is v1 only. + +### 10032 17.2.2.21 Unstructured SS handling + +10033 This operation package includes the operations required for unstructured supplementary services procedures between +10034 VLR and HLR, between the HLR and the gsmSCF, and between HLR and HLR. + +``` +10035 unstructuredSsPackage-v2 OPERATION-PACKAGE ::= { +10036 -- Supplier is HLR if Consumer is VLR +10037 -- Supplier is gsmSCF or HLR if Consumer is HLR +10038 CONSUMER INVOKES { +10039 processUnstructuredSS-Request} +10040 SUPPLIER INVOKES { +10041 unstructuredSS-Request | +10042 unstructuredSS-Notify } +10043 } +``` + +10044 The v1-equivalent package is defined as follows: + +``` +10045 unstructuredSsPackage-v1 OPERATION-PACKAGE ::= { +10046 -- Supplier is HLR if Consumer is VLR +10047 -- Supplier is gsmSCF if Consumer is HLR +10048 CONSUMER INVOKES { +10049 processUnstructuredSS-Data } +10050 } +``` + +### 10051 17.2.2.22 MO Short message relay services + +10052 This operation package includes the operations required for short message relay service procedures between IWMSC +10053 and VMSC or between GMSC and MSC or between SGSN and IWMSC. + +``` +10054 mo-ShortMsgRelayPackage-v3 OPERATION-PACKAGE ::= { +10055 -- Supplier is IWMSC if Consumer is MSC +10056 -- Supplier is IWMSC if Consumer is SGSN +10057 CONSUMER INVOKES { +10058 mo-forwardSM } +10059 } +``` + +10060 The v2-equivalent package is defined as follows: + +``` +10061 shortMsgRelayPackage-v2 OPERATION-PACKAGE ::= { +10062 -- Supplier is IWMSC if Consumer is MSC +10063 -- Supplier is MSC or SGSN if Consumer is GMSC +10064 -- Supplier is IWMSC if Consumer is SGSN +10065 CONSUMER INVOKES { +10066 forwardSM } +10067 } +``` + +10068 The v1-equivalent package can be determined according to the rules described in clause 17.2.1. + +### 10069 17.2.2.23 Short message gateway services + +10070 This operation package includes the operations required for short message service gateway procedures between MSC +10071 and HLR. + +``` +10072 shortMsgGatewayPackage-v3 OPERATION-PACKAGE ::= { +10073 -- Supplier is HLR if Consumer is GMSC +10074 CONSUMER INVOKES { +10075 sendRoutingInfoForSM | +10076 reportSM-DeliveryStatus} +10077 SUPPLIER INVOKES { +10078 informServiceCentre } +10079 } +``` + +10080 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. + +10081 The v1-equivalent package is defined as follows: + +``` +10082 shortMsgGatewayPackage-v1 OPERATION-PACKAGE ::= { +10083 -- Supplier is HLR if Consumer is GMSC +10084 CONSUMER INVOKES { +10085 sendRoutingInfoForSM | +10086 reportSMDeliveryStatus } +10087 } +``` + +### 10088 17.2.2.24 MT Short message relay services + +10089 This operation package includes the operations required for short message relay service procedures between GMSC and +10090 MSC or between GMSC and SGSN. + +``` +10091 mt-ShortMsgRelayPackage-v3 OPERATION-PACKAGE ::= { +10092 -- Supplier is MSC or SGSN or SMS-Router or IP-SM-GW if Consumer is GMSC +10093 CONSUMER INVOKES { +10094 mt-forwardSM} } +``` + +10095 +10096 The v2-equivalent package is: **shortMsgRelayPackage-v2** + +### 10097 17.2.2.25 Void + +### 10098 17.2.2.26 Message waiting data management + +10099 This operation package includes the operations required for short message waiting data procedures between HLR and +10100 VLR, between HLR and SGSN. + +``` +10101 mwdMngtPackage-v3 OPERATION-PACKAGE ::= { +10102 -- Supplier is HLR if Consumer is SGSN +10103 -- Supplier is HLR if Consumer is VLR +10104 CONSUMER INVOKES { +10105 readyForSM} } +``` + +10106 +10107 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. + +10108 +10109 The v1-equivalent package is defined as follows: + +``` +10110 mwdMngtPackage-v1 OPERATION-PACKAGE ::= { +10111 -- Supplier is HLR if Consumer is VLR +10112 CONSUMER INVOKES { +10113 noteSubscriberPresent} } +``` + +### 10115 17.2.2.27 Alerting + +10116 This operation package includes the operations required for alerting between HLR and IWMSC. + +``` +10117 alertingPackage-v2 OPERATION-PACKAGE ::= { +10118 -- Supplier is IWMSC if Consumer is HLR +10119 CONSUMER INVOKES { +10120 alertServiceCentre} } +``` + +10121 +10122 The v1-equivalent package is defined as follows. + +``` +10123 alertingPackage-v1 OPERATION-PACKAGE ::= { +10124 -- Supplier is IWMSC if Consumer is HLR +10125 CONSUMER INVOKES { +10126 alertServiceCentreWithoutResult} } +``` + +### 10128 17.2.2.28 Data restoration + +10129 This operation package includes the operations required for VLR data restoration between HLR and VLR. + +``` +10130 dataRestorationPackage-v3 OPERATION-PACKAGE ::= { +10131 -- Supplier is HLR if Consumer is VLR +10132 CONSUMER INVOKES { +10133 restoreData} } +``` + +10134 +10135 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. + +10136 The v1-equivalent package is: **infoRetrievalPackage-v1** + +### 10137 17.2.2.29 Purging + +10138 This operation package includes the operations required for purging between HLR and VLR or between HLR and +10139 SGSN. + +``` +10140 purgingPackage-v3 OPERATION-PACKAGE ::= { +10141 -- Supplier is HLR if Consumer is VLR +10142 -- Supplier is HLR if Consumer is SGSN +10143 CONSUMER INVOKES { +10144 purgeMS } } +``` + +10146 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. + +### 10147 17.2.2.30 Subscriber information enquiry + +10148 This operation package includes the operations required for subscriber information enquiry procedures between HLR +10149 and VLR or between HLR and SGSN. + +``` +10150 subscriberInformationEnquiryPackage-v3 OPERATION-PACKAGE ::= { +10151 -- Supplier is VLR or SGSN if Consumer is HLR +10152 CONSUMER INVOKES { +10153 provideSubscriberInfo } } +``` + +10155 This package is v3 only. + +### 10156 17.2.2.31 Any time information enquiry + +10157 This operation package includes the operations required for any time information enquiry procedures between gsmSCF +10158 and HLR or between gsmSCF and GMLC or between gsmSCF and NPLR. + +``` +10159 anyTimeInformationEnquiryPackage-v3 OPERATION-PACKAGE ::= { +10160 -- Supplier is HLR or GMLC or NPLR if Consumer is gsmSCF +10161 CONSUMER INVOKES { +10162 anyTimeInterrogation } } +``` + +10164 This package is v3 only. + +### 10165 17.2.2.32 Group Call Control + +10166 This operation package includes the operations required for group call and broadcast call procedures between MSCs. + +``` +10167 groupCallControlPackage-v3 OPERATION-PACKAGE ::= { +10168 -- Supplier is relay MSC if Consumer is anchor MSC +10169 CONSUMER INVOKES { +10170 prepareGroupCall | +10171 forwardGroupCallSignalling } +10172 SUPPLIER INVOKES { +10173 sendGroupCallEndSignal | +10174 processGroupCallSignalling } } +``` + +10176 This package is v3 only. + +### 10177 17.2.2.32A Group Call Info Retrieval + +10178 This operation package includes the operations required for group call and broadcast call info retrieval between MSCs. + +``` +10179 groupCallInfoRetrievalPackage-v3 OPERATION-PACKAGE ::= { +10180 -- Supplier is group call serving MSC if Consumer is visited MSC +10181 -- Supplier is visited MSC if Consumer is group call serving MSC +10182 CONSUMER INVOKES { +10183 sendGroupCallInfo } } +``` + +10185 This package is v3 only. + +10186 17.2.2.33 Void + +10187 17.2.2.34 Void + +10188 17.2.2.35 Gprs location updating + +10189 This operation package includes the operations required for the gprs location management procedures between HLR +10190 and SGSN. + +``` +10191 gprsLocationUpdatingPackage-v3 OPERATION-PACKAGE ::= { +10192 -- Supplier is HLR if Consumer is SGSN +10193 CONSUMER INVOKES { +10194 updateGprsLocation} } +``` + +10195 + +10196 This package is v3 only. + +10197 17.2.2.36 Gprs Interrogation + +10198 This operation package includes the operations required for interrogation procedures between HLR and GGSN. + +``` +10199 gprsInterrogationPackage-v4 OPERATION-PACKAGE ::= { +10200 -- Supplier is HLR if Consumer is GGSN +10201 CONSUMER INVOKES { +10202 sendRoutingInfoForGprs} } +``` + +10203 + +10204 The v3-equivalent package is defined as follows. + +10205 + +``` +10206 gprsInterrogationPackage-v3 OPERATION-PACKAGE ::= { +10207 -- Supplier is HLR if Consumer is GGSN +10208 CONSUMER INVOKES { +10209 sendRoutingInfoForGprs} } +``` + +10210 + +10211 17.2.2.37 Failure reporting + +10212 This operation package includes the operations required for failure reporting between HLR and GGSN. + +``` +10213 failureReportingPackage-v3 OPERATION-PACKAGE ::= { +10214 -- Supplier is HLR if Consumer is GGSN +10215 CONSUMER INVOKES { +10216 failureReport} } +``` + +10217 + +10218 This package is v3 only. + +10219 17.2.2.38 GPRS notifying + +10220 This operation package includes the operations required for notifying that GPRS subscriber is present between HLR and +10221 GGSN. + +``` +10222 gprsNotifyingPackage-v3 OPERATION-PACKAGE ::= { +10223 -- Supplier is GGSN if Consumer is HLR +10224 CONSUMER INVOKES { +10225 noteMsPresentForGprs} } +``` + +10226 + +10227 This package is v3 only. + +### 10228 17.2.2.39 Supplementary Service invocation notification + +10229 This operation package includes the operations required for Supplementary Service invocation notification procedures +10230 between the MSC and the gsmSCF and between the HLR and the gsmSCF. + +``` +10231 ss-InvocationNotificationPackage-v3 OPERATION-PACKAGE ::= { +10232 -- Supplier is gsmSCF if Consumer is MSC +10233 -- Supplier is gsmSCF if Consumer is HLR +10234 CONSUMER INVOKES { +10235 ss-InvocationNotification } } +``` + +10236 +10237 This package is v3 only. + +### 10238 17.2.2.40 Set Reporting State + +10239 This operation package includes the operation required for procedures between HLR and VLR to set the reporting state. + +``` +10240 setReportingStatePackage-v3 OPERATION-PACKAGE ::= { +10241 -- Supplier is VLR if Consumer is HLR +10242 CONSUMER INVOKES { +10243 setReportingState } } +``` + +10244 +10245 This package is v3 only. + +### 10246 17.2.2.41 Status Report + +10247 This operation package includes the operation required for procedures between VLR and HLR to report call results and +10248 events. + +``` +10249 statusReportPackage-v3 OPERATION-PACKAGE ::= { +10250 -- Supplier is HLR if Consumer is VLR +10251 CONSUMER INVOKES { +10252 statusReport } } +``` + +10253 +10254 This package is v3 only. + +### 10255 17.2.2.42 Remote User Free + +10256 This operation package includes the operation required by the HLR to indicate to the VLR that the remote user is free. + +``` +10257 remoteUserFreePackage-v3 OPERATION-PACKAGE ::= { +10258 -- Supplier is VLR if Consumer is HLR +10259 CONSUMER INVOKES { +10260 remoteUserFree } } +``` + +10261 +10262 This package is v3 only. + +### 10263 17.2.2.43 Call Completion + +10264 This operation package includes the operations required for procedures between VLR and HLR for subscriber control of +10265 call completion services. + +``` +10266 callCompletionPackage-v3 OPERATION-PACKAGE ::= { +10267 -- Supplier is HLR if Consumer is VLR +10268 CONSUMER INVOKES { +10269 registerCC-Entry | +10270 eraseCC-Entry } } +``` + +10271 +10272 This package is v3 only. + +### 10273 17.2.2.44 Location service gateway services + +10274 This operation package includes the operations required for location service gateway procedures between GMLC and +10275 HLR. + +``` +10276 LocationSvcGatewayPackage-v3 OPERATION-PACKAGE ::= { +10277 -- Supplier is HLR if Consumer is GMLC +10278 CONSUMER INVOKES { +10279 sendRoutingInfoForLCS} } +``` + +10281 This package is v3 only. + +## 10282 17.2.2.45 Location service enquiry + +10283 This operation package includes the operations required for the location service enquiry procedures between GMLC and +10284 MSC and between GMLC and SGSN. + +``` +10285 LocationSvcEnquiryPackage-v3 OPERATION-PACKAGE ::= { +10286 -- Supplier is MSC or SGSN if Consumer is GMLC +10287 CONSUMER INVOKES { +10288 provideSubscriberLocation} } +``` + +10290 This package is v3 only. + +## 10291 17.2.2.45A Location service reporting + +10292 This operation package includes the operations required for the location service enquiry procedures between MSC and +10293 GMLC and between SGSN and GMLC. + +``` +10294 LocationSvcReportingPackage-v3 OPERATION-PACKAGE ::= { +10295 -- Supplier is GMLC if Consumer is MSC +10296 -- Supplier is GMLC if Consumer is SGSN +10297 CONSUMER INVOKES { +10298 subscriberLocationReport} } +``` + +10299 + +10300 17.2.2.46 Void + +10301 17.2.2.47 Void + +10302 17.2.2.48 Void + +## 10303 17.2.2.49 IST Alerting + +10304 This operation package includes the operation required for alerting procedures between the MSC (Visited MSC or +10305 Gateway MSC) and HLR. + +``` +10306 ist-AlertingPackage-v3 OPERATION-PACKAGE ::= { +10307 -- Supplier is HLR if Consumer is VMSC +10308 -- Supplier is HLR if Consumer is GMSC +10309 CONSUMER INVOKES { +10310 istAlert} } +``` + +10311 + +10312 This package is v3 only. + +## 10313 17.2.2.50 Service Termination + +10314 This operation package includes the operation required for immediate service termination procedures between the HLR +10315 and the Visited MSC or between the HLR and the Gateway MSC. + +``` +10316 serviceTerminationPackage-v3 OPERATION-PACKAGE ::= { +10317 -- Supplier is VMSC or GMSC if Consumer is HLR +10318 CONSUMER INVOKES { +10319 istCommand} } +``` + +10320 + +10321 This package is v3 only. + +### 10322 17.2.2.5.1 Mobility Management event notification + +10323 This operation package includes the operations required for Mobility Management event notification procedures +10324 between VLR and gsmSCF. + +``` +10325 mm-EventReportingPackage-v3 OPERATION-PACKAGE ::= { +10326 -- Supplier is gsmSCF if Consumer is VLR +10327 CONSUMER INVOKES { +10328 noteMM-Event} } +``` + +10329 This package is v3 only. + +### 10330 17.2.2.5.2 Any time information handling + +10331 This operation package includes the operations required for any time information handling procedures between gsmSCF +10332 and HLR. + +``` +10333 anyTimeInformationHandlingPackage-v3 OPERATION-PACKAGE ::= { +10334 -- Supplier is HLR if Consumer is gsmSCF +10335 CONSUMER INVOKES { +10336 anyTimeSubscriptionInterrogation | +10337 anyTimeModification} } +``` + +10338 +10339 This package is v3 only. + +### 17.2.2.5.3 Subscriber Data modification notification + +This operation package includes the operations required for Subscriber Data modification notification procedures between HLR and gsmSCF. + +``` +subscriberDataModificationNotificationPackage-v3 OPERATION-PACKAGE ::= { + -- Supplier is gsmSCF if Consumer is HLR + CONSUMER INVOKES { + noteSubscriberDataModified} } +``` + +This package is v3 only. + +### 10340 17.2.2.5.4 Authentication Failure Report + +10341 This operation package includes the operation required for procedures between VLR and HLR or the SGSN and the +10342 HLR for reporting of authentication failures. + +``` +10343 authenticationFailureReportPackage-v3 OPERATION-PACKAGE ::= { +10344 -- Supplier is HLR if Consumer is VLR +10345 -- Supplier is HLR if Consumer is SGSN +10346 CONSUMER INVOKES { +10347 authenticationFailureReport} } +``` + +10348 +10349 This package is v3 only. + +### 10350 17.2.2.5.5 Resource Management + +10351 This operation package includes the operation required for procedures between GMSC and VMSC for resource +10352 management purpose. + +``` +10353 resourceManagementPackage-v3 OPERATION-PACKAGE ::= { +10354 -- Supplier is VMSC if Consumer is GMSC +10355 CONSUMER INVOKES { +10356 releaseResources} } +``` + +10357 +10358 This package is v3 only. + +## 10359 17.2.2.56 MT Short message relay VGCS services + +10360 This operation package includes the operations required for short message relay service procedures between SMS +10361 GMSC and MSC. + +``` +10362 mt-ShortMsgRelay-VGCS-Package-v3 OPERATION-PACKAGE ::= { +10363 -- Supplier is MSC if Consumer is GMSC +10364 CONSUMER INVOKES { +10365 mt-forwardSM-VGCS } } +``` + +10366 +10367 This package is v3 only. + +## 10368 17.2.2.57 Vcsg location updating + +10369 This operation package includes the operations required for the vcsg location management procedures between CSS and +10370 VLR or between CSS and SGSN. + +``` +10371 vcsgLocationUpdatingPackage-v3 OPERATION-PACKAGE ::= { +10372 -- Supplier is CSS if Consumer is VLR or SGSN +10373 CONSUMER INVOKES { +10374 updateVcsgLocation } } +``` + +10375 + +10376 This operation package is v3 only. + +## 10377 17.2.2.58 Vcsg location cancellation + +10378 This operation package includes the operations required for the vcsg location cancellation procedures between CSS and +10379 VLR or between CSS and SGSN. + +``` +10380 vcsgLocationCancellationPackage-v3 OPERATION-PACKAGE ::= { +10381 -- Supplier is VLR or SGSN if Consumer is CSS +10382 CONSUMER INVOKES { +10383 cancelVcsgLocation } } +``` + +10384 + +10385 This operation package is v3 only. + +10386 + +# 10387 17.3 Application contexts + +## 10388 17.3.1 General aspects + +10389 An application-context is assigned for each dialogue established by a MAP-user. In the present document each +10390 application-context is assigned a name which is supplied in the MAP-OPEN Req primitive by the MAP-User and +10391 transmitted to the peer under certain circumstances. + +10392 The following ASN.1 information object class is used to describe the main aspects of application-contexts in the +10393 following clauses: + +``` +10394 APPLICATION-CONTEXT ::= CLASS { +10395 &Symmetric OPERATION-PACKAGE OPTIONAL, +10396 &InitiatorConsumerOf OPERATION-PACKAGE OPTIONAL, +10397 &ResponderConsumerOf OPERATION-PACKAGE OPTIONAL, +10398 &code OBJECT IDENTIFIER } +10399 WITH SYNTAX { +10400 [ OPERATIONS OF &Symmetric ] +10401 [ INITIATOR CONSUMER OF &InitiatorConsumerOf +10402 RESPONDER CONSUMER OF &ResponderConsumerOf +10403 ID &code ] +10404 } +``` + +10405 + +10406 The following definitions are used throughout this clause: + +- 10407 - v1-application-context: An application-context which contains only v1-packages and uses only TC v1 facilities; +- 10408 - v1 context set: the set of v1-application-contexts defined in the present document. +- 10409 - vn-application-context (n>=2): An application-context which contains only vn-packages; + +10410 The names of v1-application-contexts are suffixed by "-v1" while other names are suffixed by "-vn" where n>=2. + +10411 Application-contexts which do not belong to the v1 context set use v2 TC facilities. + +10412 The last component of each application-context-name (i.e. the last component of the object identifier value) assigned to +10413 an application-context which belongs to the v1 context set indicates explicitly "version1". + +10414 For each application-context which does not belong to the "v1 context set" there is a v1-equivalent application context. +10415 This is a v1-application-context which includes the v1-equivalents of the packages included in the original context. + +10416 Each application-context uses the abstract-syntax associated with the operation-packages it includes and uses the +10417 transfer-syntax derived from it by applying the encoding rules defined in clause 17.1.1. + +10418 ACs which do not belong to the v1 context set require the support of the abstract-syntax identified by the object +10419 identifier value: MAP-DialogueInformation.map-Dialogue-AS defined in clause 17.4. + +## 10420 17.3.2 Application context definitions + +### 10421 17.3.2.1 Void + +### 10422 17.3.2.2 Location Updating + +10423 This application context is used between HLR and VLR for location updating procedures. + +``` +10424 networkLocUpContext-v3 APPLICATION-CONTEXT ::= { +10425 -- Responder is HLR if Initiator is VLR +10426 INITIATOR CONSUMER OF { +10427 locationUpdatingPackage-v3 | +10428 dataRestorationPackage-v3} +10429 RESPONDER CONSUMER OF { +10430 subscriberDataMngtPackage-v3 | +10431 tracingPackage-v3} +10432 ID {map-ac networkLocUp(1) version3(3)} } +``` + +10434 The following application-context-name is assigned to the v2-equivalent application-context: + +| | | +|-------|-----------------------------------------| +| 10435 | ID {map-ac networkLocUp(1) version2(2)} | +|-------|-----------------------------------------| + +10437 The following application-context-name is assigned to the v1-equivalent application-context: + +| | | +|-------|-----------------------------------------| +| 10438 | ID {map-ac networkLocUp(1) version1(1)} | +|-------|-----------------------------------------| + +### 10440 17.3.2.3 Location Cancellation + +10441 This application context is used between HLR and VLR or between HLR and SGSN for location cancellation +10442 procedures. For the HLR - SGSN interface only version 3 of this application context is applicable. + +``` +10443 locationCancellationContext-v3 APPLICATION-CONTEXT ::= { +10444 -- Responder is VLR or SGSN if Initiator is HLR +10445 INITIATOR CONSUMER OF { +10446 locationCancellationPackage-v3} +10447 ID {map-ac locationCancel(2) version3(3)} } +``` + +10449 The following application-context-name is assigned to the v2-equivalent application-context: + +| | | +|-------|-------------------------------------------| +| 10450 | ID {map-ac locationCancel(2) version2(2)} | +|-------|-------------------------------------------| + +10451 + +10452 The following application-context-name is assigned to the v1-equivalent application-context: + +| | | | +|-------|----|-----------------------------------------------| +| 10453 | ID | map-ac locationCancel (2) version1 (1) | +| 10454 | | | + +### 10455 17.3.2.4 Roaming number enquiry + +10456 This application context is used between HLR and VLR for roaming number enquiry procedures. + +| | | | +|-------|-----------------------------------------------|---------------------------| +| 10457 | roamingNumberEnquiryContext-v3 | APPLICATION-CONTEXT ::= { | +| 10458 | -- Responder is VLR if Initiator is HLR | | +| 10459 | INITIATOR CONSUMER OF { | | +| 10460 | roamingNumberEnquiryPackage-v3} | | +| 10461 | ID {map-ac roamingNbEnquiry (3) version3 (3)} | } | +| 10462 | | | + +10463 The following application-context-name is assigned to the v2-equivalent application-context: + +| | | | +|-------|----|---------------------------------------------------| +| 10464 | ID | {map-ac roamingNbEnquiry (3) version2 (2)} | +| 10465 | | | + +10466 The following application-context-name is assigned to the v1-equivalent application-context: + +| | | | +|-------|----|---------------------------------------------------| +| 10467 | ID | {map-ac roamingNbEnquiry (3) version1 (1)} | +| 10468 | | | + +### 10469 17.3.2.5 Void + +### 10470 17.3.2.6 Location Information Retrieval + +10471 This application-context is used between GMSC and HLR or between GMSC and NPLR or between gsmSCF and HLR +10472 when retrieving location information. For the GMSC - NPLR interface version 1, version 2 and version 3 of this +10473 application context are applicable. + +| | | | +|-------|--------------------------------------------------|---------------------------| +| 10474 | locationInfoRetrievalContext-v3 | APPLICATION-CONTEXT ::= { | +| 10475 | -- Responder is HLR or NPLR if Initiator is GMSC | | +| 10476 | -- Responder is HLR if Initiator is gsmSCF | | +| 10477 | INITIATOR CONSUMER OF { | | +| 10478 | interrogationPackage-v3} | | +| 10479 | ID {map-ac locInfoRetrieval (5) version3 (3)} | } | +| 10480 | | | + +10481 The following application-context-name is assigned to the v2-equivalent application-context: + +| | | | +|-------|----|---------------------------------------------------| +| 10482 | ID | {map-ac locInfoRetrieval (5) version2 (2)} | +| 10483 | | | +| 10484 | | | + +10485 The following application-context-name is assigned to the v1-equivalent application-context: + +| | | | +|-------|----|---------------------------------------------------| +| 10486 | ID | {map-ac locInfoRetrieval (5) version1 (1)} | +| 10487 | | | + +### 10488 17.3.2.7 Call control transfer + +10489 This application context is used for the call control transfer procedure between the VMSC and the GMSC. + +| | | | +|-------|--------------------------------------------------|---------------------------| +| 10490 | callControlTransferContext-v4 | APPLICATION-CONTEXT ::= { | +| 10491 | -- Responder is GMSC if Initiator is VMSC | | +| 10492 | INITIATOR CONSUMER OF { | | +| 10493 | callControlTransferPackage-v4} | | +| 10494 | ID {map-ac callControlTransfer (6) version4 (4)} | } | +| 10495 | | | + +10496 The following application-context-name is assigned to the v3-equivalent application-context: + +| | | | +|-------|----|------------------------------------------------------| +| 10497 | ID | {map-ac callControlTransfer (6) version3 (3)} | +|-------|----|------------------------------------------------------| + +10498 17.3.2.8 Void + +10499 17.3.2.9 Void + +10500 17.3.2.10 Void + +10501 17.3.2.11 Location registers restart + +10502 This application context is used between HLR and VLR or between HLR and SGSN for location register restart +10503 procedures or between CSS and VLR or between CSS and SGSN for CSG Subscriber Server restart procedures. For the +10504 HLR - VLR interface and for the HLR - SGSN interface version 1, version 2 and version 3 of this application context +10505 are applicable For the CSS - VLR interface and the CSS - SGSN interface version 3 of this application context is +10506 applicable. + +``` +10507 resetContext-v3 APPLICATION-CONTEXT ::= { +10508 -- Responder is VLR or SGSN if Initiator is HLR or CSS +10509 INITIATOR CONSUMER OF { +10510 resetPackage-v3} +10511 ID {map-ac reset(10) version3(3)} } +``` + +10513 The following application-context-name is assigned to the v2-equivalent application-context: + +``` +10514 ID {map-ac reset(10) version2(2)} +``` + +10516 The following application-context-name is assigned to the v1-equivalent application-context: + +``` +10517 ID {map-ac reset(10) version1(1)} +``` + +10519 17.3.2.12 Handover control + +10520 This application context is used for handover procedures between MSCs. + +``` +10521 handoverControlContext-v3 APPLICATION-CONTEXT ::= { +10522 -- Responder is MSCB if Initiator is MSCA +10523 INITIATOR CONSUMER OF { +10524 handoverControlPackage-v3} +10525 ID {map-ac handoverControl(11) version3(3)} } +``` + +10526 + +10527 The following application-context-name is assigned to the v2-equivalent application-context: + +``` +10528 ID {map-ac handoverControl(11) version2(2)} +``` + +10529 + +10530 + +10531 The following application-context-name is assigned to the v1-equivalent application-context: + +``` +10532 ID {map-ac handoverControl(11) version1(1)} +``` + +10533 + +10534 17.3.2.13 IMSI Retrieval + +10535 This application context is used for IMSI retrieval between HLR and VLR. + +``` +10536 imsiRetrievalContext-v2 APPLICATION-CONTEXT ::= { +10537 -- Responder is HLR if Initiator is VLR +10538 INITIATOR CONSUMER OF { +10539 imsi-RetrievalPackage-v2} +10540 ID {map-ac imsiRetrieval(26) version2(2)} } +``` + +10541 + +10542 This application-context is v2 only. + +### 10543 17.3.2.14 Equipment Management + +10544 This application context is used for equipment checking between MSC and EIR or between SGSN and EIR. For the +10545 SGSN - EIR interface version 1 and version 2 and version 3 of this application context are applicable: + +``` +10546 equipmentMngtContext-v3 APPLICATION-CONTEXT ::= { +10547 -- Responder is EIR if Initiator is MSC +10548 -- Responder is EIR if Initiator is SGSN +10549 INITIATOR CONSUMER OF { +10550 equipmentMngtPackage-v3} +10551 ID {map-ac equipmentMngt(13) version3(3)} } +``` + +10553 The following application-context-name is assigned to the v2-equivalent application-context: + +``` +10554 equipmentMngtContext-v2 APPLICATION-CONTEXT ::= { +10555 -- Responder is EIR if Initiator is MSC +10556 -- Responder is EIR if Initiator is SGSN +10557 INITIATOR CONSUMER OF { +10558 equipmentMngtPackage-v2} +10559 ID {map-ac equipmentMngt(13) version2(2)} } +``` + +10561 The following application-context-name is assigned to the v1-equivalent application-context: + +``` +10562 ID {map-ac equipmentMngt(13) version1(1)} +``` + +### 10564 17.3.2.15 Information retrieval + +10565 This application context is used for authentication information retrieval between HLR and VLR or between HLR and +10566 SGSN. For the HLR - SGSN interface version 1 and version 2 and version 3 of this application context are applicable. + +``` +10567 infoRetrievalContext-v3 APPLICATION-CONTEXT ::= { +10568 -- Responder is HLR if Initiator is VLR +10569 -- Responder is HLR if Initiator is SGSN +10570 INITIATOR CONSUMER OF { +10571 infoRetrievalPackage-v3} +10572 ID {map-ac infoRetrieval(14) version3(3)} } +``` + +10574 The following application-context-name is assigned to the v2-equivalent application-context: + +``` +10575 infoRetrievalContext-v2 APPLICATION-CONTEXT ::= { +10576 -- Responder is HLR if Initiator is VLR +10577 -- Responder is HLR if Initiator is SGSN +10578 INITIATOR CONSUMER OF { +10579 infoRetrievalPackage-v2} +10580 ID {map-ac infoRetrieval(14) version2(2)} } +``` + +10582 The following application-context-name is assigned to the v1-equivalent application-context: + +``` +10583 ID {map-ac infoRetrieval(14) version1(1)} +``` + +### 10585 17.3.2.16 Inter-VLR information retrieval + +10586 This application context is used for information retrieval between VLRs. + +``` +10587 interVlrInfoRetrievalContext-v3 APPLICATION-CONTEXT ::= { +10588 -- Responder is VLR if Initiator is VLR +10589 INITIATOR CONSUMER OF { +10590 interVlrInfoRetrievalPackage-v3} +10591 ID {map-ac interVlrInfoRetrieval(15) version3(3)} } +``` + +10593 The v2-equivalent application-context is: + +``` +10594 interVlrInfoRetrievalContext-v2 APPLICATION-CONTEXT ::= { +10595 -- Responder is VLR if Initiator is VLR +10596 INITIATOR CONSUMER OF { +10597 interVlrInfoRetrievalPackage-v2} +10598 ID {map-ac interVlrInfoRetrieval(15) version2(2)} } +``` + +10600 The v1-equivalent application-context is: + +``` +10601 ID {map-ac infoRetrieval(14) version1(1)} +``` + +10602 + +### 10603 17.3.2.17 Stand Alone Subscriber Data Management + +10604 This application context is used for stand alone subscriber data management between HLR and VLR or between HLR +10605 and SGSN. For the HLR - SGSN interface only version 3 of this application context is applicable. Also this application +10606 context is used for stand alone subscriber data management between CSS and VLR or between CSS and SGSN. For the +10607 CSS – VLR interface and CSS – SGSN interface only version 3 of this application context is applicable: + +``` +10608 subscriberDataMngtContext-v3 APPLICATION-CONTEXT ::= { +10609 -- Responder is VLR or SGSN if Initiator is HLR or CSS +10610 INITIATOR CONSUMER OF { +10611 subscriberDataMngtStandAlonePackage-v3} +10612 ID {map-ac subscriberDataMngt(16) version3(3)} } +``` + +10613 +10614 The following application-context-name is assigned to the v2-equivalent application-context: + +``` +10615 ID {map-ac subscriberDataMngt(16) version2(2)} +``` + +10616 +10617 The following application-context-name is assigned to the v1-equivalent application-context: + +``` +10618 ID {map-ac subscriberDataMngt(16) version1(1)} +``` + +### 10620 17.3.2.18 Tracing + +10621 This application context is used between HLR and VLR or between HLR and SGSN for stand alone tracing control +10622 procedures. For the HLR - SGSN interface version 1, version 2 and version 3 of this application context are applicable. + +``` +10623 tracingContext-v3 APPLICATION-CONTEXT ::= { +10624 -- Responder is VLR or SGSN if Initiator is HLR +10625 INITIATOR CONSUMER OF { +10626 tracingStandAlonePackage-v3} +10627 ID {map-ac tracing(17) version3(3)} } +``` + +10628 + +10629 The following application-context-name is assigned to the v2-equivalent application-context: + +``` +10630 ID {map-ac tracing(17) version2(2)} +``` + +10631 +10632 The following application-context-name is assigned to the v1-equivalent application-context: + +``` +10633 ID {map-ac tracing(17) version1(1)} +``` + +### 10635 17.3.2.19 Network functional SS handling + +10636 This application context is used for functional-like SS handling procedures between VLR and HLR. + +``` +10637 networkFunctionalSsContext-v2 APPLICATION-CONTEXT ::= { +10638 -- Responder is HLR, Initiator is VLR +10639 INITIATOR CONSUMER OF { +10640 functionalSsPackage-v2} +10641 ID {map-ac networkFunctionalSs(18) version2(2)} } +``` + +10642 + +10643 The v1-equivalent application-context is defined as follows: + +``` +10644 networkFunctionalSsContext-v1 APPLICATION-CONTEXT ::= { +10645 -- Responder is HLR, Initiator is VLR +10646 INITIATOR CONSUMER OF { +10647 functionalSsPackage-v1 | +10648 unstructuredSsPackage-v1 | +10649 bindingPackage-v1} +10650 ID {map-ac networkFunctionalSs(18) version1(1)} } +``` + +10651 + +### 10652 17.3.2.20 Network unstructured SS handling + +10653 This application context is used for handling stimuli-like procedures between HLR and VLR, between the HLR and +10654 gsmSCF, and between HLR and HLR. + +``` +10655 networkUnstructuredSsContext-v2 APPLICATION-CONTEXT ::= { +10656 -- Responder is HLR, Initiator is VLR +10657 -- Responder is VLR, Initiator is HLR +10658 -- Responder is gsmSCF, Initiator is HLR +10659 -- Responder is HLR, Initiator is gsmSCF +10660 -- Responder is HLR, Initiator is HLR +10661 OPERATIONS OF { +10662 unstructuredSsPackage-v2} +10663 ID {map-ac networkUnstructuredSs(19) version2(2)} } +``` + +10665 The following application-context-name is assigned to the v1-equivalent application-context: + +``` +10666 ID {map-ac networkFunctionalSs(18) version1(1)} +``` + +### 10668 17.3.2.21 Short Message Gateway + +10669 This application context is used for short message gateway procedures. + +``` +10670 shortMsgGatewayContext-v3 APPLICATION-CONTEXT ::= { +10671 -- Responder is HLR if Initiator is GMSC +10672 INITIATOR CONSUMER OF { +10673 shortMsgGatewayPackage-v3} +10674 ID {map-ac shortMsgGateway(20) version3(3)} } +``` + +10676 The following application-context-name is assigned to the v2-equivalent application-context: + +``` +10677 ID {map-ac shortMsgGateway(20) version2(2)} +``` + +10679 The following application-context-name is assigned to the v1-equivalent application-context: + +``` +10680 ID {map-ac shortMsgGateway(20) version1(1)} +``` + +### 10682 17.3.2.22 Mobile originating Short Message Relay + +10683 This application context is used between MSC and IWMSC or between SGSN and IWMSC for mobile originating short +10684 message relay procedures. For the SGSN - IWMSC interface version 1, version 2 and version 3 of this application +10685 context are applicable. + +``` +10686 shortMsgMO-RelayContext-v3 APPLICATION-CONTEXT ::= { +10687 -- Responder is IWMSC if Initiator is MSC +10688 -- Responder is IWMSC if Initiator is SGSN +10689 INITIATOR CONSUMER OF { +10690 mo-ShortMsgRelayPackage-v3} +10691 ID {map-ac shortMsgMO-Relay(21) version3(3)} } +``` + +10693 The following application-context-name is assigned to the v2-equivalent application-context: + +``` +10694 ID {map-ac shortMsgMO-Relay(21) version2(2)} +``` + +10696 The following application-context-name is assigned to the v1-equivalent application-context: + +``` +10697 ID {map-ac shortMsg-Relay(21) version1(1)} +``` + +10699 17.3.2.23 Void + +10700 17.3.2.24 Short message alert + +10701 This application context is used for short message alerting procedures. + +``` +10702 shortMsgAlertContext-v2 APPLICATION-CONTEXT ::= { +10703 -- Responder is IWMSC if Initiator is HLR +10704 INITIATOR CONSUMER OF { +10705 alertingPackage-v2} +10706 ID {map-ac shortMsgAlert(23) version2(2)} } +``` + +10708 The following application-context-name is symbolically assigned to the v1-equivalent application-context: + +``` +10709 ID {map-ac shortMsgAlert(23) version1(1)} +10710 +``` + +10711 17.3.2.25 Short message waiting data management + +10712 This application context is used between VLR and HLR or between SGSN and HLR for short message waiting data +10713 management procedures. For the SGSN - HLR interface only version 3 of this application context is applicable. + +``` +10714 mwdMngtContext-v3 APPLICATION-CONTEXT ::= { +10715 -- Responder is HLR if Initiator is SGSN +10716 -- Responder is HLR if Initiator is VLR +10717 INITIATOR CONSUMER OF { +10718 mwdMngtPackage-v3} +10719 ID {map-ac mwdMngt(24) version3(3)} } +``` + +10720 + +10721 The following application-context-name is assigned to the v2-equivalent application-context: + +``` +10722 ID {map-ac mwdMngt(24) version2(2)} +10723 +``` + +10723 + +10724 The following application-context-name is assigned to the v1-equivalent application-context: + +``` +10725 ID {map-ac mwdMngt(24) version1(1)} +10726 +``` + +10726 + +10727 17.3.2.26 Mobile terminating Short Message Relay + +10728 This application context is used between GMSC and MSC or between GMSC and SGSN for mobile terminating short +10729 message relay procedures. For the GMSC - SGSN interface version 2 and version 3 of this application context and the +10730 equivalent version 1 application context are applicable. + +``` +10731 shortMsgMT-RelayContext-v3 APPLICATION-CONTEXT ::= { +10732 -- Responder is MSC or SGSN if Initiator is GMSC +10733 INITIATOR CONSUMER OF { +10734 mt-ShortMsgRelayPackage-v3} +10735 ID {map-ac shortMsgMT-Relay(25) version3(3)} } +``` + +10736 + +10737 The following application-context-name is assigned to the v2-equivalent application-context: + +``` +10738 ID {map-ac shortMsgMT-Relay(25) version2(2)} +10739 +``` + +10739 + +10740 The following application-context-name is assigned to the v1-equivalent application-context: + +``` +10741 ID {map-ac shortMsg-Relay(21) version1(1)} +10742 +``` + +10742 + +### 10743 17.3.2.27 MS purging + +10744 This application context is used between HLR and VLR or between HLR and SGSN for MS purging procedures. For +10745 the SGSN - HLR interface only version 3 of this application context is applicable. + +``` +10746 msPurgingContext-v3 APPLICATION-CONTEXT ::= { +10747 -- Responder is HLR if Initiator is VLR +10748 -- Responder is HLR if Initiator is SGSN +10749 INITIATOR CONSUMER OF { +10750 purgingPackage-v3} +10751 ID {map-ac msPurging(27) version3(3)} } +``` + +10752 +10753 The following application-context-name is assigned to the v2-equivalent application-context: + +``` +10754 ID {map-ac msPurging(27) version2(2)} +``` + +10755 + +### 10756 17.3.2.28 Subscriber information enquiry + +10757 This application context is used between HLR and VLR or between HLR and SGSN for subscriber information enquiry +10758 procedures. + +``` +10759 subscriberInfoEnquiryContext-v3 APPLICATION-CONTEXT ::= { +10760 -- Responder is VLR or SGSN if Initiator is HLR +10761 INITIATOR CONSUMER OF { +10762 subscriberInformationEnquiryPackage-v3} +10763 ID {map-ac subscriberInfoEnquiry(28) version3(3)} } +``` + +10764 +10765 This application-context is v3 only. + +### 10766 17.3.2.29 Any time information enquiry + +10767 This application context is used between gsmSCF and HLR or between gsmSCF and GMLC or between gsmSCF and +10768 NPLR for any time information enquiry procedures. + +``` +10769 anyTimeInfoEnquiryContext-v3 APPLICATION-CONTEXT ::= { +10770 -- Responder is HLR or GMLC or NPLR if Initiator is gsmSCF +10771 INITIATOR CONSUMER OF { +10772 anyTimeInformationEnquiryPackage-v3} +10773 ID {map-ac anyTimeInfoEnquiry(29) version3(3)} } +``` + +10774 +10775 This application-context is v3 only. + +### 10776 17.3.2.30 Group Call Control + +10777 This application context is used between anchor MSC and relay MSC for group call and broadcast call procedures. + +``` +10778 groupCallControlContext-v3 APPLICATION-CONTEXT ::= { +10779 -- Responder is relay MSC if Initiator is anchor MSC +10780 INITIATOR CONSUMER OF { +10781 groupCallControlPackage-v3} +10782 ID {map-ac groupCallControl(31) version3(3)} } +``` + +10783 +10784 This application-context is v3 only. + +### 10785 17.3.2.30A Group Call Info Retrieval + +10786 This application context is used between group call serving MSC and visited MSC for group call and broadcast call +10787 procedures. + +``` +10788 groupCallInfoRetControlContext-v3 APPLICATION-CONTEXT ::= { +10789 -- Responder is group call serving MSC if Initiator is visited MSC +10790 -- Responder is visited MSC if Initiator is group call serving MSC +10791 INITIATOR CONSUMER OF { +10792 groupCallInfoRetrievalPackage-v3} +10793 ID {map-ac groupCallInfoRetrieval(45) version3(3)} } +``` + +10794 +10795 This application-context is v3 only. + +10796 17.3.2.31 Void + +10797 17.3.2.32 Gprs Location Updating + +10798 This application context is used between HLR and SGSN for gprs location updating procedures. + +``` +10799 gprsLocationUpdateContext-v3 APPLICATION-CONTEXT ::= { +10800 -- Responder is HLR if Initiator is SGSN +10801 INITIATOR CONSUMER OF { +10802 gprsLocationUpdatingPackage-v3} +10803 RESPONDER CONSUMER OF { +10804 subscriberDataMngtPackage-v3 | +10805 tracingPackage-v3} +10806 ID {map-ac gprsLocationUpdate(32) version3(3)} } +``` + +10807 +10808 This application-context is v3 only. + +10809 17.3.2.33 Gprs Location Information Retrieval + +10810 This application context is used between HLR and GGSN when retrieving gprs location information. + +``` +10811 gprsLocationInfoRetrievalContext-v4 APPLICATION-CONTEXT ::= { +10812 -- Responder is HLR if Initiator is GGSN +10813 INITIATOR CONSUMER OF { +10814 gprsInterrogationPackage-v4} +10815 ID {map-ac gprsLocationInfoRetrieval(33) version4(4)} } +``` + +10816 + +10817 The following application-context-name is assigned to the v3-equivalent application-context: + +``` +10818 ID {map-ac gprsLocationInfoRetrieval(33) version3(3)} +``` + +10819 +10820 + +10821 17.3.2.34 Failure Reporting + +10822 This application context is used between HLR and GGSN to inform that network requested PDP-context activation has +10823 failed. + +``` +10824 failureReportContext-v3 APPLICATION-CONTEXT ::= { +10825 -- Responder is HLR if Initiator is GGSN +10826 INITIATOR CONSUMER OF { +10827 failureReportingPackage-v3} +10828 ID {map-ac failureReport(34) version3(3)} } +``` + +10829 + +10830 This application-context is v3 only. + +10831 17.3.2.35 GPRS Notifying + +10832 This application context is used between HLR and GGSN for notifying that GPRS subscriber is present again. + +``` +10833 gprsNotifyContext-v3 APPLICATION-CONTEXT ::= { +10834 -- Responder is GGSN if Initiator is HLR +10835 INITIATOR CONSUMER OF { +10836 gprsNotifyingPackage-v3} +10837 ID {map-ac gprsNotify(35) version3(3)} } +``` + +10838 + +10839 This application-context is v3 only. + +10840 17.3.2.36 Supplementary Service invocation notification + +10841 This application context is used between the MSC and the gsmSCF and between the HLR and the gsmSCF for +10842 Supplementary Service invocation notification procedures. + +``` +10843 ss-InvocationNotificationContext-v3 APPLICATION-CONTEXT ::= { +10844 -- Responder is gsmSCF, Initiator is MSC +10845 -- Responder is gsmSCF, Initiator is HLR +10846 INITIATOR CONSUMER OF { +10847 ss-InvocationNotificationPackage-v3} +10848 ID {map-ac ss-InvocationNotification(36) version3(3)} } +``` + +10849 +10850 This application-context is v3 only. + +10851 17.3.2.37 Reporting + +10852 This application context is used between HLR and VLR for reporting procedures. + +``` +10853 reportingContext-v3 APPLICATION-CONTEXT ::= { +10854 -- Responder is VLR if Initiator is HLR +10855 -- Responder is HLR if Initiator is VLR +10856 INITIATOR CONSUMER OF { +10857 setReportingStatePackage-v3 | +10858 statusReportPackage-v3 | +10859 remoteUserFreePackage-v3} +10860 RESPONDER CONSUMER OF { +10861 setReportingStatePackage-v3 | +10862 statusReportPackage-v3} +10863 ID {map-ac reporting(7) version3(3)} } +``` + +10864 +10865 This application-context is v3 only. + +10866 17.3.2.38 Call Completion + +10867 This application context is used between VLR and the HLR for subscriber control of call completion services. + +``` +10868 callCompletionContext-v3 APPLICATION-CONTEXT ::= { +10869 -- Responder is HLR if Initiator is VLR +10870 INITIATOR CONSUMER OF { +10871 callCompletionPackage-v3} +10872 ID {map-ac callCompletion(8) version3(3)} } +``` + +10873 +10874 This application-context is v3 only. + +10875 17.3.2.39 Location Service Gateway + +10876 This application context is used for location service gateway procedures. + +``` +10877 locationSvcGatewayContext-v3 APPLICATION-CONTEXT ::= { +10878 -- Responder is HLR if Initiator is GMLC +10879 INITIATOR CONSUMER OF { +10880 locationSvcGatewayPackage-v3} +10881 ID {map-ac locationSvcGateway(37) version3(3)} } +``` + +10882 + +10883 17.3.2.40 Location Service Enquiry + +10884 This application context is used for location service enquiry procedures. + +``` +10885 locationSvcEnquiryContext-v3 APPLICATION-CONTEXT ::= { +10886 -- Responder is MSC or SGSN if Initiator is GMLC +10887 -- Responder is GMLC if Initiator is MSC +10888 -- Responder is GMLC if Initiator is SGSN +10889 INITIATOR CONSUMER OF { +10890 locationSvcEnquiryPackage-v3 | +10891 locationSvcReportingPackage-v3} +10892 ID {map-ac locationSvcEnquiry(38) version3(3)} } +``` + +10893 + +10894 17.3.2.41 Void + +10895 17.3.2.42 Void + +10896 17.3.2.43 Void + +10897 17.3.2.44 IST Alerting + +10898 This application context is used between MSC (Visited MSC or Gateway MSC) and HLR for alerting services within +10899 IST procedures. + +``` +10900 istAlertingContext-v3 APPLICATION-CONTEXT ::= { +10901 -- Responder is HLR if Initiator is VMSC +10902 -- Responder is HLR if Initiator is GMSC +10903 INITIATOR CONSUMER OF { +10904 ist-AlertingPackage-v3} +10905 ID {map-ac alerting(4) version3(3)} } +``` + +10906 + +10907 This application-context is v3 only. + +10908 17.3.2.45 Service Termination + +10909 This application context is used between HLR and MSC (Visited MSC or Gateway MSC) for service termination +10910 services within IST procedures. + +``` +10911 serviceTerminationContext-v3 APPLICATION-CONTEXT ::= { +10912 -- Responder is VMSC or GMSC if Initiator is HLR +10913 INITIATOR CONSUMER OF { +10914 serviceTerminationPackage-v3} +10915 ID {map-ac serviceTermination(9) version3(3)} } +``` + +10916 + +10917 This application-context is v3 only. + +### 10918 17.3.2.46 Mobility Management event notification + +10919 This application context is used between VLR and gsmSCF for Mobility Management event notification procedures. + +``` +10920 mm-EventReportingContext-v3 APPLICATION-CONTEXT ::= { +10921 -- Responder is gsmSCF, Initiator is VLR +10922 INITIATOR CONSUMER OF { +10923 mm-EventReportingPackage-v3} +10924 ID {map-ac mm-EventReporting(42) version3(3)} } +``` + +10926 This application-context is v3 only. + +### 10927 17.3.2.47 Any time information handling + +10928 This application context is used between gsmSCF and HLR for any time information handling procedures. + +``` +10929 anyTimeInfohandlingContext-v3 APPLICATION-CONTEXT ::= { +10930 -- Responder is HLR if Initiator is gsmSCF +10931 INITIATOR CONSUMER OF { +10932 anyTimeInformationHandlingPackage-v3} +10933 ID {map-ac anyTimeInfoHandling(43) version3(3)} } +``` + +10935 This application-context is v3 only. + +### 10936 17.3.2.48 Subscriber Data modification notification + +This application context is used between HLR and gsmSCF for Subscriber Data modification notification procedures. + +``` +subscriberDataModificationNotificationContext-v3 APPLICATION-CONTEXT ::= { + -- Responder is gsmSCF, Initiator is HLR + INITIATOR CONSUMER OF { + subscriberDataModificationNotificationPackage-v3} + ID {map-ac subscriberDataModificationNotification(22) version3(3)} } +``` + +This application-context is v3 only. + +### 10937 17.3.2.49 Authentication Failure Report + +10938 This application context is used between VLR and HLR or SGSN and HLR for reporting of authentication failures. + +``` +10939 authenticationFailureReportContext-v3 APPLICATION-CONTEXT ::= { +10940 -- Responder is HLR if Initiator is VLR +10941 -- Responder is HLR if Initiator is SGSN +10942 INITIATOR CONSUMER OF { +10943 authenticationFailureReportPackage-v3 } +10944 ID {map-ac authenticationFailureReport(39) version3(3)} } +``` + +10946 This application-context is v3 only. + +### 10947 17.3.2.50 Resource Management + +10948 This application context is used between GMSC and VMSC for resource management purpose. + +``` +10949 resourceManagementContext-v3 APPLICATION-CONTEXT ::= { +10950 -- Responder is VMSC if Initiator is GMSC +10951 INITIATOR CONSUMER OF { +10952 resourceManagementPackage-v3 } +10953 ID {map-ac resourceManagement(44) version3(3)} } +``` + +10955 This application-context is v3 only. + +### 10956 17.3.2.51 Mobile terminating Short Message Relay VGCS + +10957 This application context is used between SMS-GMSC and MSC for mobile terminating short message relay procedures +10958 for VGCS. + +``` +10959 shortMsgMT-Relay-VGCS-Context-v3 APPLICATION-CONTEXT ::= { +10960 -- Responder is MSC if Initiator is SMS-GMSC +10961 INITIATOR CONSUMER OF { +10962 mt-ShortMsgRelay-VGCS-Package-v3} +10963 ID {map-ac shortMsgMT-Relay-VGCS(41) version3(3)} } +``` + +10965 This application-context is v3 only. + +### 10966 17.3.2.52 Vcsg Location Updating + +10967 This application context is used between CSS and VLR or between CSS and SGSN for vcsg location updating +10968 procedures. + +``` +10969 vcsgLocationUpdateContext-v3 APPLICATION-CONTEXT ::= { +10970 -- Responder is CSS if Initiator is VLR or SGSN +10971 INITIATOR CONSUMER OF { +10972 vcsgLocationUpdatingPackage-v3} +10973 RESPONDER CONSUMER OF { +10974 subscriberDataMngtPackage-v3} +10975 ID {map-ac vcsgLocationUpdate(46) version3(3)} } +``` + +10977 This application-context is v3 only. + +### 10978 17.3.2.53 Vcsg Location Cancellation + +10979 This application context is used between CSS and VLR or between CSS and SGSN for vcsg location cancellation +10980 procedures. + +``` +10981 vcsgLocationCancellationContext-v3 APPLICATION-CONTEXT ::= { +10982 -- Responder is VLR or SGSN if Initiator is CSS +10983 INITIATOR CONSUMER OF { +10984 vcsgLocationCancellationPackage-v3} +10985 ID {map-ac vcsgLocationCancel(47) version3(3)} } +``` + +10987 This application-context is v3 only. + +10988 + +10989 + +## 10990 17.3.3 ASN.1 Module for application-context-names + +The following ASN.1 module summarises the application-context-name assigned to MAP application-contexts. + +``` +10991 MAP-ApplicationContexts { +10992 itu-t identified-organization (4) etsi (0) mobileDomain (0) +10993 gsm-Network (1) modules (3) map-ApplicationContexts (2) version21 (21)} +10994 DEFINITIONS +10995 BEGIN +10996 ::= +10997 BEGIN +11000 +11001 +11002 -- EXPORTS everything +11003 +11004 +11005 IMPORTS +11006 gsm-NetworkId, +11007 ac-Id +11008 FROM MobileDomainDefinitions { +11009 itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +11010 mobileDomainDefinitions (0) version1 (1)} +11011 ; +11012 +``` + +``` +11013 -- application-context-names +11014 +11015 map-ac OBJECT IDENTIFIER ::= {gsm-NetworkId ac-Id} +11016 +11017 networkLocUpContext-v3 OBJECT IDENTIFIER ::= +11018 {map-ac networkLocUp(1) version3(3)} +11019 +11020 locationCancellationContext-v3 OBJECT IDENTIFIER ::= +11021 {map-ac locationCancel(2) version3(3)} +11022 +11023 roamingNumberEnquiryContext-v3 OBJECT IDENTIFIER ::= +11024 {map-ac roamingNbEnquiry(3) version3(3)} +11025 +11026 authenticationFailureReportContext-v3 OBJECT IDENTIFIER ::= +11027 {map-ac authenticationFailureReport(39) version3(3)} +11028 +11029 locationInfoRetrievalContext-v3 OBJECT IDENTIFIER ::= +11030 {map-ac locInfoRetrieval(5) version3(3)} +11031 +11032 resetContext-v3 OBJECT IDENTIFIER ::= +11033 {map-ac reset(10) version3(3)} +11034 +11035 handoverControlContext-v3 OBJECT IDENTIFIER ::= +11036 {map-ac handoverControl(11) version3(3)} +11037 +11038 equipmentMngtContext-v3 OBJECT IDENTIFIER ::= +11039 {map-ac equipmentMngt(13) version3(3)} +11040 +11041 infoRetrievalContext-v3 OBJECT IDENTIFIER ::= +11042 {map-ac infoRetrieval(14) version3(3)} +11043 +11044 interVlrInfoRetrievalContext-v3 OBJECT IDENTIFIER ::= +11045 {map-ac interVlrInfoRetrieval(15) version3(3)} +11046 +11047 subscriberDataMngtContext-v3 OBJECT IDENTIFIER ::= +11048 {map-ac subscriberDataMngt(16) version3(3)} +11049 +11050 tracingContext-v3 OBJECT IDENTIFIER ::= +11051 {map-ac tracing(17) version3(3)} +11052 +11053 networkFunctionalSsContext-v2 OBJECT IDENTIFIER ::= +11054 {map-ac networkFunctionalSs(18) version2(2)} +11055 +11056 networkUnstructuredSsContext-v2 OBJECT IDENTIFIER ::= +11057 {map-ac networkUnstructuredSs(19) version2(2)} +11058 +11059 shortMsgGatewayContext-v3 OBJECT IDENTIFIER ::= +11060 {map-ac shortMsgGateway(20) version3(3)} +11061 +11062 shortMsgMO-RelayContext-v3 OBJECT IDENTIFIER ::= +11063 {map-ac shortMsgMO-Relay(21) version3(3)} +11064 +11065 shortMsgAlertContext-v2 OBJECT IDENTIFIER ::= +11066 {map-ac shortMsgAlert(23) version2(2)} +11067 +11068 mwdMngtContext-v3 OBJECT IDENTIFIER ::= +11069 {map-ac mwdMngt(24) version3(3)} +11070 +11071 shortMsgMT-RelayContext-v3 OBJECT IDENTIFIER ::= +11072 {map-ac shortMsgMT-Relay(25) version3(3)} +11073 +11074 shortMsgMT-Relay-VGCS-Context-v3 OBJECT IDENTIFIER ::= +11075 {map-ac shortMsgMT-Relay-VGCS(41) version3(3)} +11076 +11077 imsiRetrievalContext-v2 OBJECT IDENTIFIER ::= +11078 {map-ac imsiRetrieval(26) version2(2)} +11079 +11080 msPurgingContext-v3 OBJECT IDENTIFIER ::= +11081 {map-ac msPurging(27) version3(3)} +11082 +11083 subscriberInfoEnquiryContext-v3 OBJECT IDENTIFIER ::= +11084 {map-ac subscriberInfoEnquiry(28) version3(3)} +11085 +11086 anyTimeInfoEnquiryContext-v3 OBJECT IDENTIFIER ::= +11087 {map-ac anyTimeInfoEnquiry(29) version3(3)} +``` + +``` + +11088 +11089 callControlTransferContext-v4 OBJECT IDENTIFIER ::= +11090 {map-ac callControlTransfer(6) version4(4)} +11091 +11092 ss-InvocationNotificationContext-v3 OBJECT IDENTIFIER ::= +11093 {map-ac ss-InvocationNotification(36) version3(3)} +11094 +11095 groupCallControlContext-v3 OBJECT IDENTIFIER ::= +11096 {map-ac groupCallControl(31) version3(3)} +11097 +11098 groupCallInfoRetrievalContext-v3 OBJECT IDENTIFIER ::= +11099 {map-ac groupCallInfoRetrieval(45) version3(3)} +11100 +11101 gprsLocationUpdateContext-v3 OBJECT IDENTIFIER ::= +11102 {map-ac gprsLocationUpdate(32) version3(3)} +11103 +11104 gprsLocationInfoRetrievalContext-v4 OBJECT IDENTIFIER ::= +11105 {map-ac gprsLocationInfoRetrieval(33) version4(4)} +11106 +11107 failureReportContext-v3 OBJECT IDENTIFIER ::= +11108 {map-ac failureReport(34) version3(3)} +11109 +11110 gprsNotifyContext-v3 OBJECT IDENTIFIER ::= +11111 {map-ac gprsNotify(35) version3(3)} +11112 +11113 reportingContext-v3 OBJECT IDENTIFIER ::= +11114 {map-ac reporting(7) version3(3)} +11115 +11116 callCompletionContext-v3 OBJECT IDENTIFIER ::= +11117 {map-ac callCompletion(8) version3(3)} +11118 +11119 istAlertingContext-v3 OBJECT IDENTIFIER ::= +11120 {map-ac istAlerting(4) version3(3)} +11121 +11122 serviceTerminationContext-v3 OBJECT IDENTIFIER ::= +11123 {map-ac immediateTermination(9) version3(3)} +11124 +11125 locationSvcGatewayContext-v3 OBJECT IDENTIFIER ::= +11126 {map-ac locationSvcGateway(37) version3(3)} +11127 +11128 locationSvcEnquiryContext-v3 OBJECT IDENTIFIER ::= +11129 {map-ac locationSvcEnquiry(38) version3(3)} +11130 +11131 mm-EventReportingContext-v3 OBJECT IDENTIFIER ::= +11132 {map-ac mm-EventReporting(42) version3(3)} +11133 +11134 anyTimeInfoHandlingContext-v3 OBJECT IDENTIFIER ::= +11135 {map-ac anyTimeInfoHandling(43) version3(3)} +11136 +11137 subscriberDataModificationNotificationContext-v3 OBJECT IDENTIFIER ::= +11138 {map-ac subscriberDataModificationNotification(22) version3(3)} +11139 +11140 resourceManagementContext-v3 OBJECT IDENTIFIER ::= +11141 {map-ac resourceManagement(44) version3(3)} +11142 +11143 vcsgLocationUpdateContext-v3 OBJECT IDENTIFIER ::= +11144 {map-ac vcsgLocationUpdate(46) version3(3)} +11145 +11146 vcsgLocationCancellationContext-v3 OBJECT IDENTIFIER ::= +11147 {map-ac vcsgLocationCancel(47) version3(3)} + +``` + +``` + +11148 +11149 +11150 -- The following Object Identifiers are reserved for application-contexts +11151 -- existing in previous versions of the protocol +11152 + +``` + +| 11153 | -- AC Name & Version | Object Identifier | | +|-------|-----------------------------------------|----------------------------------------------|---------------------| +| 11154 | -- | | | +| 11155 | -- networkLocUpContext-v1 | map-ac networkLocUp (1) | version1 (1) | +| 11156 | -- networkLocUpContext-v2 | map-ac networkLocUp (1) | version2 (2) | +| 11157 | -- locationCancellationContext-v1 | map-ac locationCancellation (2) | version1 (1) | +| 11158 | -- locationCancellationContext-v2 | map-ac locationCancellation (2) | version2 (2) | +| 11159 | -- roamingNumberEnquiryContext-v1 | map-ac roamingNumberEnquiry (3) | version1 (1) | +| 11160 | -- roamingNumberEnquiryContext-v2 | map-ac roamingNumberEnquiry (3) | version2 (2) | +| 11161 | -- locationInfoRetrievalContext-v1 | map-ac locationInfoRetrieval (5) | version1 (1) | +| 11162 | -- locationInfoRetrievalContext-v2 | map-ac locationInfoRetrieval (5) | version2 (2) | +| 11163 | -- resetContext-v1 | map-ac reset (10) | version1 (1) | +| 11164 | -- resetContext-v2 | map-ac reset (10) | version2 (2) | +| 11165 | -- handoverControlContext-v1 | map-ac handoverControl (11) | version1 (1) | +| 11166 | -- handoverControlContext-v2 | map-ac handoverControl (11) | version2 (2) | +| 11167 | -- slWFSAllocationContext-v3 | map-ac slWFSAllocation (12) | version3 (3) | +| 11168 | -- equipmentMngtContext-v1 | map-ac equipmentMngt (13) | version1 (1) | +| 11169 | -- equipmentMngtContext-v2 | map-ac equipmentMngt (13) | version2 (2) | +| 11170 | -- infoRetrievalContext-v1 | map-ac infoRetrieval (14) | version1 (1) | +| 11171 | -- infoRetrievalContext-v2 | map-ac infoRetrieval (14) | version2 (2) | +| 11172 | -- interVlrInfoRetrievalContext-v2 | map-ac interVlrInfoRetrieval (15) | version2 (2) | +| 11173 | -- subscriberDataMngtContext-v1 | map-ac subscriberDataMngt (16) | version1 (1) | +| 11174 | -- subscriberDataMngtContext-v2 | map-ac subscriberDataMngt (16) | version2 (2) | +| 11175 | -- tracingContext-v1 | map-ac tracing (17) | version1 (1) | +| 11176 | -- tracingContext-v2 | map-ac tracing (17) | version2 (2) | +| 11177 | -- networkFunctionalSsContext-v1 | map-ac networkFunctionalSs (18) | version1 (1) | +| 11178 | -- shortMsgGatewayContext-v1 | map-ac shortMsgGateway (20) | version1 (1) | +| 11179 | -- shortMsgGatewayContext-v2 | map-ac shortMsgGateway (20) | version2 (2) | +| 11180 | -- shortMsgRelayContext-v1 | map-ac shortMsgRelay (21) | version1 (1) | +| 11181 | -- shortMsgAlertContext-v1 | map-ac shortMsgAlert (23) | version1 (1) | +| 11182 | -- mwdMngtContext-v1 | map-ac mwdMngt (24) | version1 (1) | +| 11183 | -- mwdMngtContext-v2 | map-ac mwdMngt (24) | version2 (2) | +| 11184 | -- shortMsgMT-RelayContext-v2 | map-ac shortMsgMT-Relay (25) | version2 (2) | +| 11185 | -- msPurgingContext-v2 | map-ac msPurging (27) | version2 (2) | +| 11186 | -- callControlTransferContext-v3 | map-ac callControlTransferContext (6) | version3 (3) | +| 11187 | -- gprsLocationInfoRetrievalContext-v3 | map-ac gprsLocationInfoRetrievalContext (33) | version3 (3) | + +11188 + +11189 + +11190 END + +## 11191 17.4 MAP Dialogue Information + +``` + +11192 MAP-DialogueInformation { +11193 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11194 gsm-Network (1) modules (3) map-DialogueInformation (3) version21 (21)} +11195 +11196 DEFINITIONS +11197 +11198 IMPLICIT TAGS +11199 +11200 ::= +11201 +11202 BEGIN +11203 +11204 EXPORTS +11205 map-DialogueAS, +11206 MAP-DialoguePDU +11207 +11208 ; +11209 +11210 IMPORTS +11211 gsm-NetworkId, +11212 as-Id +11213 FROM MobileDomainDefinitions { +11214 itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +11215 mobileDomainDefinitions (0) version1 (1)} +11216 +11217 AddressString +11218 FROM MAP-CommonDataTypes { +11219 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11220 gsm-Network(1) modules (3) map-CommonDataTypes (18) version21 (21)} +11221 +11222 ExtensionContainer +11223 FROM MAP-ExtensionDataTypes { +11224 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11225 gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version21 (21)} +11226 +11227 + +``` + +``` + +11228 ; +11229 +11230 +11231 -- abstract syntax name for MAP-DialoguePDU +11232 +11233 map-DialogueAS OBJECT IDENTIFIER ::= +11234 {gsm-NetworkId as-Id map-DialoguePDU (1) version1 (1)} +11235 +11236 MAP-DialoguePDU ::= CHOICE { +11237 map-open [0] MAP-OpenInfo, +11238 map-accept [1] MAP-AcceptInfo, +11239 map-close [2] MAP-CloseInfo, +11240 map-refuse [3] MAP-RefuseInfo, +11241 map-userAbort [4] MAP-UserAbortInfo, +11242 map-providerAbort [5] MAP-ProviderAbortInfo} +11243 +11244 MAP-OpenInfo ::= SEQUENCE { +11245 destinationReference [0] AddressString OPTIONAL, +11246 originationReference [1] AddressString OPTIONAL, +11247 ..., +11248 extensionContainer ExtensionContainer OPTIONAL +11249 -- extensionContainer must not be used in version 2 +11250 } +11251 +11252 MAP-AcceptInfo ::= SEQUENCE { +11253 ..., +11254 extensionContainer ExtensionContainer OPTIONAL +11255 -- extensionContainer must not be used in version 2 +11256 } +11257 +11258 MAP-CloseInfo ::= SEQUENCE { +11259 ..., +11260 extensionContainer ExtensionContainer OPTIONAL +11261 -- extensionContainer must not be used in version 2 +11262 } +11263 +11264 MAP-RefuseInfo ::= SEQUENCE { +11265 reason Reason, +11266 ..., +11267 extensionContainer ExtensionContainer OPTIONAL, +11268 -- extensionContainer must not be used in version 2 +11269 alternativeApplicationContext OBJECT IDENTIFIER OPTIONAL +11270 -- alternativeApplicationContext must not be used in version 2 +11271 } +11272 +11273 Reason ::= ENUMERATED { +11274 noReasonGiven (0), +11275 invalidDestinationReference (1), +11276 invalidOriginatingReference (2)} +11277 +11278 MAP-UserAbortInfo ::= SEQUENCE { +11279 map-UserAbortChoice MAP-UserAbortChoice, +11280 ..., +11281 extensionContainer ExtensionContainer OPTIONAL +11282 -- extensionContainer must not be used in version 2 +11283 } +11284 +11285 MAP-UserAbortChoice ::= CHOICE { +11286 userSpecificReason [0] NULL, +11287 userResourceLimitation [1] NULL, +11288 resourceUnavailable [2] ResourceUnavailableReason, +11289 applicationProcedureCancellation [3] ProcedureCancellationReason} +11290 +11291 ResourceUnavailableReason ::= ENUMERATED { +11292 shortTermResourceLimitation (0), +11293 longTermResourceLimitation (1)} +11294 +11295 ProcedureCancellationReason ::= ENUMERATED { +11296 handoverCancellation (0), +11297 radioChannelRelease (1), +11298 networkPathRelease (2), +11299 callRelease (3), +11300 associatedProcedureFailure (4), +11301 tandemDialogueRelease (5), +11302 remoteOperationsFailure (6)} +11303 + +``` + +``` + +11304 MAP-ProviderAbortInfo ::= SEQUENCE { +11305 map-ProviderAbortReason MAP-ProviderAbortReason, +11306 ..., +11307 extensionContainer ExtensionContainer OPTIONAL +11308 -- extensionContainer must not be used in version 2 +11309 } +11310 +11311 MAP-ProviderAbortReason ::= ENUMERATED { +11312 abnormalDialogue (0), +11313 invalidPDU (1)} +11314 +11315 END + +``` + +## 11316 17.5 MAP operation and error codes + +``` + +11317 MAP-Protocol { +11318 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11319 gsm-Network (1) modules (3) map-Protocol (4) version21 (21)} +11320 +11321 DEFINITIONS +11322 +11323 ::= +11324 +11325 BEGIN +11326 +11327 IMPORTS +11328 OPERATION +11329 FROM Remote-Operations-Information-Objects { +11330 joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)} +11331 +11332 updateLocation, +11333 cancelLocation, +11334 cancelVcsgLocation, +11335 purgeMS, +11336 sendIdentification, +11337 updateGprsLocation, +11338 updateVcsgLocation, +11339 prepareHandover, +11340 sendEndSignal, +11341 processAccessSignalling, +11342 forwardAccessSignalling, +11343 prepareSubsequentHandover, +11344 sendAuthenticationInfo, +11345 authenticationFailureReport, +11346 checkIMEI, +11347 insertSubscriberData, +11348 deleteSubscriberData, +11349 reset, +11350 forwardCheckSS-Indication, +11351 restoreData, +11352 provideSubscriberInfo, +11353 anyTimeInterrogation, +11354 anyTimeSubscriptionInterrogation, +11355 anyTimeModification, +11356 sendRoutingInfoForGprs, +11357 failureReport, +11358 noteMsPresentForGprs, +11359 noteMM-Event, +11360 noteSubscriberDataModified +11361 +11362 +11363 FROM MAP-MobileServiceOperations { +11364 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11365 gsm-Network (1) modules (3) map-MobileServiceOperations (5) +11366 version21 (21)} +11367 +11368 activateTraceMode, +11369 deactivateTraceMode, +11370 sendIMSI +11371 FROM MAP-OperationAndMaintenanceOperations { +11372 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11373 gsm-Network (1) modules (3) map-OperationAndMaintenanceOperations (6) +11374 version21 (21)} +11375 +11376 sendRoutingInfo, +11377 provideRoamingNumber, +11378 resumeCallHandling, + +``` + +``` + +11379 setReportingState, +11380 statusReport, +11381 remoteUserFree, +11382 ist-Alert, +11383 ist-Command, +11384 releaseResources +11385 FROM MAP-CallHandlingOperations { +11386 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11387 gsm-Network (1) modules (3) map-CallHandlingOperations (7) +11388 version21 (21)} +11389 +11390 registerSS, +11391 eraseSS, +11392 activateSS, +11393 deactivateSS, +11394 interrogateSS, +11395 processUnstructuredSS-Request, +11396 unstructuredSS-Request, +11397 unstructuredSS-Notify, +11398 registerPassword, +11399 getPassword, +11400 ss-InvocationNotification, +11401 registerCC-Entry, +11402 eraseCC-Entry +11403 FROM MAP-SupplementaryServiceOperations { +11404 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11405 gsm-Network (1) modules (3) map-SupplementaryServiceOperations (8) +11406 version21 (21)} +11407 +11408 sendRoutingInfoForSM, +11409 mo-ForwardSM, +11410 mt-ForwardSM, +11411 reportSM-DeliveryStatus, +11412 alertServiceCentre, +11413 informServiceCentre, +11414 readyForSM, +11415 mt-ForwardSM-VGCS +11416 FROM MAP-ShortMessageServiceOperations { +11417 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11418 gsm-Network (1) modules (3) map-ShortMessageServiceOperations (9) +11419 version21 (21)} +11420 +11421 prepareGroupCall, +11422 processGroupCallSignalling, +11423 forwardGroupCallSignalling, +11424 sendGroupCallEndSignal, +11425 sendGroupCallInfo +11426 FROM MAP-Group-Call-Operations { +11427 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11428 gsm-Network (1) modules (3) map-Group-Call-Operations (22) +11429 version21 (21)} +11430 +11431 provideSubscriberLocation, +11432 sendRoutingInfoForLCS, +11433 subscriberLocationReport +11434 FROM MAP-LocationServiceOperations { +11435 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11436 gsm-Network (1) modules (3) map-LocationServiceOperations (24) +11437 version21 (21)} +11438 +11439 +11440 ; +11441 Supported-MAP-Operations OPERATION ::= {updateLocation | cancelLocation | cancelVcsgLocation | +11442 purgeMS | +11443 sendIdentification | updateGprsLocation | updateVcsgLocation | prepareHandover | sendEndSignal | +11444 processAccessSignalling | forwardAccessSignalling | prepareSubsequentHandover | +11445 sendAuthenticationInfo | authenticationFailureReport | checkIMEI | insertSubscriberData | +11446 deleteSubscriberData | reset | forwardCheckSS-Indication | restoreData | provideSubscriberInfo | +11447 anyTimeInterrogation | anyTimeSubscriptionInterrogation | anyTimeModification | +11448 sendRoutingInfoForGprs | failureReport | noteMsPresentForGprs | noteMM-Event | +11449 noteSubscriberDataModified | activateTraceMode | deactivateTraceMode | sendIMSI | +11450 sendRoutingInfo | provideRoamingNumber | resumeCallHandling | setReportingState | statusReport | +11451 remoteUserFree | ist-Alert | +11452 ist-Command | registerSS | eraseSS | activateSS | deactivateSS | interrogateSS | +11453 processUnstructuredSS-Request | unstructuredSS-Request | unstructuredSS-Notify | +11454 registerPassword | getPassword | ss-InvocationNotification | registerCC-Entry | eraseCC-Entry | +11455 sendRoutingInfoForSM | mo-ForwardSM | mt-ForwardSM | reportSM-DeliveryStatus | +11456 alertServiceCentre | informServiceCentre | readyForSM | prepareGroupCall | +11457 processGroupCallSignalling | forwardGroupCallSignalling | sendGroupCallEndSignal | + +``` + +``` + +11458 provideSubscriberLocation | sendRoutingInfoForLCS | subscriberLocationReport | +11459 releaseResources | mt-ForwardSM-VGCS | sendGroupCallInfo } +11460 +11461 +11462 +11463 -- The following operation codes are reserved for operations +11464 -- existing in previous versions of the protocol +11465 +11466 -- Operation Name AC used Oper. Code +11467 -- +11468 -- sendParameters map-ac infoRetrieval (14) version1 (1) local:9 +11469 -- processUnstructuredSS-Data map-ac networkFunctionalSs (18) version1 (1) local:19 +11470 -- performHandover map-ac handoverControl (11) version1 (1) local:28 +11471 -- performSubsequentHandover map-ac handoverControl (11) version1 (1) local:30 +11472 -- provideSIWFSNumber map-ac siWFSAllocation (12) version3 (3) local:31 +11473 -- siwfs-SignallingModify map-ac siWFSAllocation (12) version3 (3) local:32 +11474 -- noteInternalHandover map-ac handoverControl (11) version1 (1) local:35 +11475 -- noteSubscriberPresent map-ac mwdMngt (24) version1 (1) local:48 +11476 -- alertServiceCentreWithoutResult map-ac shortMsgAlert (23) version1 (1) local:49 +11477 -- traceSubscriberActivity map-ac handoverControl (11) version1 (1) local:52 +11478 -- beginSubscriberActivity map-ac networkFunctionalSs (18) version1 (1) local:54 +11479 +11480 -- The following error codes are reserved for errors +11481 -- existing in previous versions of the protocol +11482 +11483 -- Error Name AC used Error Code +11484 -- +11485 -- unknownBaseStation map-ac handoverControl (11) version1 (1) local:2 +11486 -- invalidTargetBaseStation map-ac handoverControl (11) version1 (1) local:23 +11487 -- noRadioResourceAvailable map-ac handoverControl (11) version1 (1) local:24 +11488 +11489 +11490 END + +``` + +## 11491 17.6 MAP operations and errors + +### 11492 17.6.1 Mobile Service Operations + +``` + +11493 MAP-MobileServiceOperations { +11494 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11495 gsm-Network (1) modules (3) map-MobileServiceOperations (5) +11496 version21 (21)} +11497 +11498 DEFINITIONS +11499 +11500 ::= +11501 +11502 BEGIN +11503 +11504 EXPORTS +11505 +11506 -- location registration operations +11507 updateLocation, +11508 cancelLocation, +11509 purgeMS, +11510 sendIdentification, +11511 +11512 -- gprs location registration operations +11513 updateGprsLocation, +11514 +11515 -- vcsg location registration operations +11516 updateVcsgLocation, +11517 cancelVcsgLocation, +11518 +11519 -- subscriber information enquiry operations +11520 provideSubscriberInfo, +11521 +11522 -- any time information enquiry operations +11523 anyTimeInterrogation, +11524 +11525 -- any time information handling operations +11526 anyTimeSubscriptionInterrogation, +11527 anyTimeModification, +11528 +11529 -- subscriber data modification notification operations +11530 noteSubscriberDataModified, + +``` + +``` + +11531 +11532 +11533 -- handover operations +11534 prepareHandover, +11535 sendEndSignal, +11536 processAccessSignalling, +11537 forwardAccessSignalling, +11538 prepareSubsequentHandover, +11539 +11540 -- authentication management operations +11541 sendAuthenticationInfo, +11542 authenticationFailureReport, +11543 +11544 -- IMEI management operations +11545 checkIMEI, +11546 +11547 -- subscriber management operations +11548 insertSubscriberData, +11549 deleteSubscriberData, +11550 +11551 -- fault recovery operations +11552 reset, +11553 forwardCheckSS-Indication, +11554 restoreData, +11555 +11556 -- gprs location information retrieval operations +11557 sendRoutingInfoForGprs, +11558 +11559 -- failure reporting operations +11560 failureReport, +11561 +11562 -- gprs notification operations +11563 noteMsPresentForGprs, +11564 +11565 -- Mobility Management operations +11566 noteMM-Event +11567 +11568 ; +11569 +11570 IMPORTS +11571 OPERATION +11572 FROM Remote-Operations-Information-Objects { +11573 joint-iso-itu-t remote-operations(4) +11574 informationObjects(5) version1(0) } +11575 +11576 systemFailure, +11577 dataMissing, +11578 unexpectedDataValue, +11579 unknownSubscriber, +11580 unknownMSC, +11581 unidentifiedSubscriber, +11582 unknownEquipment, +11583 roamingNotAllowed, +11584 ati-NotAllowed, +11585 noHandoverNumberAvailable, +11586 subsequentHandoverFailure, +11587 absentSubscriber, +11588 mm-EventNotSupported, +11589 atsi-NotAllowed, +11590 atm-NotAllowed, +11591 bearerServiceNotProvisioned, +11592 teleserviceNotProvisioned, +11593 callBarred, +11594 illegalSS-Operation, +11595 ss-ErrorStatus, +11596 ss-NotAvailable, +11597 ss-Incompatibility, +11598 ss-SubscriptionViolation, +11599 informationNotAvailable, +11600 targetCellOutsideGroupCallArea +11601 +11602 +11603 FROM MAP-Errors { +11604 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11605 gsm-Network (1) modules (3) map-Errors (10) version21 (21) } +11606 +11607 UpdateLocationArg, +11608 UpdateLocationRes, +11609 CancelLocationArg, + +``` + +``` + +11610 CancelLocationRes, +11611 PurgeMS-Arg, +11612 PurgeMS-Res, +11613 SendIdentificationArg, +11614 SendIdentificationRes, +11615 UpdateGprsLocationArg, +11616 UpdateGprsLocationRes, +11617 UpdateVcsgLocationArg, +11618 UpdateVcsgLocationRes, +11619 CancelVcsgLocationArg, +11620 CancelVcsgLocationRes, +11621 PrepareHO-Arg, +11622 PrepareHO-Res, +11623 ForwardAccessSignalling-Arg, +11624 ProcessAccessSignalling-Arg, +11625 SendEndSignal-Arg, +11626 SendEndSignal-Res, +11627 PrepareSubsequentHO-Res, +11628 PrepareSubsequentHO-Arg, +11629 SendAuthenticationInfoArg, +11630 SendAuthenticationInfoRes, +11631 AuthenticationFailureReportArg, +11632 AuthenticationFailureReportRes, +11633 CheckIMEI-Arg, +11634 CheckIMEI-Res, +11635 InsertSubscriberDataArg, +11636 InsertSubscriberDataRes, +11637 DeleteSubscriberDataArg, +11638 DeleteSubscriberDataRes, +11639 ResetArg, +11640 RestoreDataArg, +11641 RestoreDataRes, +11642 ProvideSubscriberInfoArg, +11643 ProvideSubscriberInfoRes, +11644 AnyTimeSubscriptionInterrogationArg, +11645 AnyTimeSubscriptionInterrogationRes, +11646 AnyTimeModificationArg, +11647 AnyTimeModificationRes, +11648 NoteSubscriberDataModifiedArg, +11649 NoteSubscriberDataModifiedRes, +11650 AnyTimeInterrogationArg, +11651 AnyTimeInterrogationRes, +11652 SendRoutingInfoForGprsArg, +11653 SendRoutingInfoForGprsRes, +11654 FailureReportArg, +11655 FailureReportRes, +11656 NoteMsPresentForGprsArg, +11657 NoteMsPresentForGprsRes, +11658 NoteMM-EventArg, +11659 NoteMM-EventRes +11660 +11661 +11662 FROM MAP-MS-DataTypes { +11663 itu-t identified-organization (4) etsi (0) mobileDomain (0) +11664 gsm-Network (1) modules (3) map-MS-DataTypes (11) version21 (21)} +11665 +11666 ; +11667 +11668 +11669 -- location registration operations +11670 +11671 updateLocation OPERATION ::= { +11672 ARGUMENT +11673 UpdateLocationArg +11674 RESULT +11675 UpdateLocationRes +11676 ERRORS { +11677 systemFailure | +11678 dataMissing | +11679 unexpectedDataValue | +11680 unknownSubscriber | +11681 roamingNotAllowed} +11682 CODE local:2 } +11683 + +``` + +--Timer m + +``` +11684 cancelLocation OPERATION ::= { --Timer m +11685 ARGUMENT +11686 CancelLocationArg +11687 RESULT +11688 CancelLocationRes +11689 -- optional +11690 ERRORS { +11691 dataMissing | +11692 unexpectedDataValue} +11693 CODE local:3 } +``` + +``` +11694 +11695 purgeMS OPERATION ::= { --Timer m +11696 ARGUMENT +11697 PurgeMS-Arg +11698 RESULT +11699 PurgeMS-Res +11700 -- optional +11701 ERRORS{ +11702 dataMissing | +11703 unexpectedDataValue| +11704 unknownSubscriber} +11705 CODE local:67 } +``` + +``` +11706 +11707 sendIdentification OPERATION ::= { --Timer s +11708 ARGUMENT +11709 SendIdentificationArg +11710 RESULT +11711 SendIdentificationRes +11712 ERRORS { +11713 dataMissing | +11714 unidentifiedSubscriber} +11715 CODE local:55 } +``` + +``` +11716 +11717 -- gprs location registration operations +11718 +``` + +``` +11719 updateGprsLocation OPERATION ::= { --Timer m +11720 ARGUMENT +11721 UpdateGprsLocationArg +11722 RESULT +11723 UpdateGprsLocationRes +11724 ERRORS { +11725 systemFailure | +11726 unexpectedDataValue | +11727 unknownSubscriber | +11728 roamingNotAllowed} +11729 CODE local:23 } +``` + +``` +11730 +11731 -- subscriber information enquiry operations +11732 +``` + +``` +11733 provideSubscriberInfo OPERATION ::= { --Timer m +11734 ARGUMENT +11735 ProvideSubscriberInfoArg +11736 RESULT +11737 ProvideSubscriberInfoRes +11738 ERRORS { +11739 dataMissing | +11740 unexpectedDataValue} +11741 CODE local:70 } +``` + +``` +11742 +11743 -- any time information enquiry operations +11744 +``` + +``` +11745 anyTimeInterrogation OPERATION ::= { --Timer m +11746 ARGUMENT +11747 AnyTimeInterrogationArg +11748 RESULT +11749 AnyTimeInterrogationRes +11750 ERRORS { +11751 systemFailure | +11752 ati-NotAllowed | +11753 dataMissing | +11754 unexpectedDataValue | +11755 unknownSubscriber} +11756 CODE local:71 } +``` + +``` +11757 +11758 -- any time information handling operations +11759 +``` + +``` + +11760 anyTimeSubscriptionInterrogation OPERATION ::= { --Timer m +11761 ARGUMENT +11762 AnyTimeSubscriptionInterrogationArg +11763 RESULT +11764 AnyTimeSubscriptionInterrogationRes +11765 ERRORS { +11766 atsi-NotAllowed | +11767 dataMissing | +11768 unexpectedDataValue | +11769 unknownSubscriber | +11770 bearerServiceNotProvisioned | +11771 teleserviceNotProvisioned | +11772 callBarred | +11773 illegalSS-Operation | +11774 ss-NotAvailable | +11775 informationNotAvailable} +11776 CODE local:62 } +11777 +11778 anyTimeModification OPERATION ::= { --Timer m +11779 ARGUMENT +11780 AnyTimeModificationArg +11781 RESULT +11782 AnyTimeModificationRes +11783 ERRORS { +11784 atm-NotAllowed | +11785 dataMissing | +11786 unexpectedDataValue | +11787 unknownSubscriber | +11788 bearerServiceNotProvisioned | +11789 teleserviceNotProvisioned | +11790 callBarred | +11791 illegalSS-Operation | +11792 ss-SubscriptionViolation | +11793 ss-ErrorStatus | +11794 ss-Incompatibility | +11795 informationNotAvailable} +11796 CODE local:65 } +11797 +11798 -- subscriber data modification notification operations +11799 +11800 noteSubscriberDataModified OPERATION ::= { --Timer m +11801 ARGUMENT +11802 NoteSubscriberDataModifiedArg +11803 RESULT +11804 NoteSubscriberDataModifiedRes +11805 -- optional +11806 ERRORS { +11807 dataMissing | +11808 unexpectedDataValue | +11809 unknownSubscriber} +11810 CODE local:5 } +11811 +11812 -- handover operations +11813 +11814 prepareHandover OPERATION ::= { --Timer m +11815 ARGUMENT +11816 PrepareHO-Arg +11817 RESULT +11818 PrepareHO-Res +11819 ERRORS { +11820 systemFailure | +11821 dataMissing | +11822 unexpectedDataValue | +11823 noHandoverNumberAvailable | +11824 targetCellOutsideGroupCallArea } +11825 CODE local:68 } +11826 +11827 sendEndSignal OPERATION ::= { --Timer l +11828 ARGUMENT +11829 SendEndSignal-Arg +11830 RESULT +11831 SendEndSignal-Res +11832 CODE local:29 } +11833 + +``` + +``` + +11834 processAccessSignalling OPERATION ::= { --Timer s +11835 ARGUMENT +11836 ProcessAccessSignalling-Arg +11837 CODE local:33 } +11838 +11839 forwardAccessSignalling OPERATION ::= { --Timer s +11840 ARGUMENT +11841 ForwardAccessSignalling-Arg +11842 CODE local:34 } +11843 +11844 prepareSubsequentHandover OPERATION ::= { --Timer m +11845 ARGUMENT +11846 PrepareSubsequentHO-Arg +11847 RESULT +11848 PrepareSubsequentHO-Res +11849 ERRORS { +11850 unexpectedDataValue | +11851 dataMissing | +11852 unknownMSC | +11853 subsequentHandoverFailure} +11854 CODE local:69 } +11855 +11856 -- authentication management operations +11857 +11858 sendAuthenticationInfo OPERATION ::= { --Timer m +11859 ARGUMENT +11860 SendAuthenticationInfoArg +11861 -- optional +11862 -- within a dialogue sendAuthenticationInfoArg shall not be present in +11863 -- subsequent invoke components. If received in a subsequent invoke component +11864 -- it shall be discarded. +11865 +11866 RESULT +11867 SendAuthenticationInfoRes +11868 -- optional +11869 ERRORS { +11870 systemFailure | +11871 dataMissing | +11872 unexpectedDataValue | +11873 unknownSubscriber} +11874 CODE local:56 } +11875 +11876 authenticationFailureReport OPERATION ::= { --Timer m +11877 ARGUMENT +11878 AuthenticationFailureReportArg +11879 RESULT +11880 AuthenticationFailureReportRes +11881 -- optional +11882 ERRORS { +11883 systemFailure | +11884 unexpectedDataValue | +11885 unknownSubscriber} +11886 CODE local:15 } +11887 +11888 -- IMEI management operations +11889 +11890 checkIMEI OPERATION ::= { --Timer m +11891 ARGUMENT +11892 CheckIMEI-Arg +11893 RESULT +11894 CheckIMEI-Res +11895 ERRORS { +11896 systemFailure | +11897 dataMissing | +11898 unknownEquipment} +11899 CODE local:43 } +11900 +11901 -- subscriber management operations +11902 + +``` + +``` + +11903 insertSubscriberData OPERATION ::= { --Timer m +11904 ARGUMENT +11905 InsertSubscriberDataArg +11906 RESULT +11907 InsertSubscriberDataRes +11908 -- optional +11909 ERRORS { +11910 dataMissing | +11911 unexpectedDataValue | +11912 unidentifiedSubscriber} +11913 CODE local:7 } +11914 +11915 deleteSubscriberData OPERATION ::= { --Timer m +11916 ARGUMENT +11917 DeleteSubscriberDataArg +11918 RESULT +11919 DeleteSubscriberDataRes +11920 -- optional +11921 ERRORS { +11922 dataMissing | +11923 unexpectedDataValue | +11924 unidentifiedSubscriber} +11925 CODE local:8 } +11926 +11927 -- fault recovery operations +11928 +11929 reset OPERATION ::= { --Timer m +11930 ARGUMENT +11931 ResetArg +11932 CODE local:37 } +11933 +11934 forwardCheckSS-Indication OPERATION ::= { --Timer s +11935 CODE local:38 } +11936 +11937 restoreData OPERATION ::= { --Timer m +11938 ARGUMENT +11939 RestoreDataArg +11940 RESULT +11941 RestoreDataRes +11942 ERRORS { +11943 systemFailure | +11944 dataMissing | +11945 unexpectedDataValue | +11946 unknownSubscriber} +11947 CODE local:57 } +11948 +11949 -- gprs location information retrieval operations +11950 +11951 sendRoutingInfoForGprs OPERATION ::= { --Timer m +11952 ARGUMENT +11953 SendRoutingInfoForGprsArg +11954 RESULT +11955 SendRoutingInfoForGprsRes +11956 ERRORS { +11957 absentSubscriber | +11958 systemFailure | +11959 dataMissing | +11960 unexpectedDataValue | +11961 unknownSubscriber | +11962 callBarred } +11963 CODE local:24 } +11964 +11965 -- failure reporting operations +11966 +11967 failureReport OPERATION ::= { --Timer m +11968 ARGUMENT +11969 FailureReportArg +11970 RESULT +11971 FailureReportRes +11972 -- optional +11973 ERRORS { +11974 systemFailure | +11975 dataMissing | +11976 unexpectedDataValue | +11977 unknownSubscriber} +11978 CODE local:25 } +11979 +11980 -- gprs notification operations + +``` + +``` + +11981 +11982 noteMsPresentForGprs OPERATION ::= { --Timer m +11983 ARGUMENT +11984 NoteMsPresentForGprsArg +11985 RESULT +11986 NoteMsPresentForGprsRes +11987 -- optional +11988 ERRORS { +11989 systemFailure | +11990 dataMissing | +11991 unexpectedDataValue | +11992 unknownSubscriber} +11993 CODE local:26 } +11994 +11995 noteMM-Event OPERATION ::= { --Timer m +11996 ARGUMENT +11997 NoteMM-EventArgs +11998 RESULT +11999 NoteMM-EventRes +12000 ERRORS { +12001 dataMissing | +12002 unexpectedDataValue | +12003 unknownSubscriber | +12004 mm-EventNotSupported} +12005 CODE local:89 } +12006 +12007 -- vcsf location registration operations +12008 +12009 updateVcsfLocation OPERATION ::= { --Timer m +12010 ARGUMENT +12011 UpdateVcsfLocationArg +12012 RESULT +12013 UpdateVcsfLocationRes +12014 ERRORS { +12015 systemFailure | +12016 unexpectedDataValue | +12017 unknownSubscriber} +12018 CODE local:53 } +12019 +12020 cancelVcsfLocation OPERATION ::= { --Timer m +12021 ARGUMENT +12022 CancelVcsfLocationArg +12023 RESULT +12024 CancelVcsfLocationRes +12025 -- optional +12026 ERRORS { +12027 dataMissing | +12028 unexpectedDataValue} +12029 CODE local:36 } +12030 +12031 END + +``` + +## 17.6.2 Operation and Maintenance Operations + +``` + +12033 MAP-OperationAndMaintenanceOperations { +12034 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12035 gsm-Network (1) modules (3) map-OperationAndMaintenanceOperations (6) +12036 version21 (21)} +12037 +12038 DEFINITIONS +12039 +12040 ::= +12041 +12042 BEGIN +12043 +12044 EXPORTS +12045 activateTraceMode, +12046 deactivateTraceMode, +12047 sendIMSI +12048 ; +12049 +12050 IMPORTS +12051 OPERATION +12052 FROM Remote-Operations-Information-Objects { +12053 joint-iso-itu-t remote-operations (4) +12054 informationObjects (5) version1 (0)} +12055 +12056 systemFailure, + +``` + +``` + +12057 dataMissing, +12058 unexpectedDataValue, +12059 facilityNotSupported, +12060 unknownSubscriber, +12061 unidentifiedSubscriber, +12062 tracingBufferFull +12063 FROM MAP-Errors { +12064 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12065 gsm-Network (1) modules (3) map-Errors (10) version21 (21)} +12066 +12067 ActivateTraceModeArg, +12068 ActivateTraceModeRes, +12069 DeactivateTraceModeArg, +12070 DeactivateTraceModeRes +12071 FROM MAP-OM-DataTypes { +12072 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12073 gsm-Network (1) modules (3) map-OM-DataTypes (12) version21 (21)} +12074 +12075 ISDN-AddressString, +12076 IMSI +12077 FROM MAP-CommonDataTypes { +12078 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12079 gsm-Network (1) modules (3) map-CommonDataTypes (18) version21 (21)} +12080 ; +12081 +12082 + +``` + +``` + +12083 activateTraceMode OPERATION ::= { --Timer m +12084 ARGUMENT +12085 ActivateTraceModeArg +12086 RESULT +12087 ActivateTraceModeRes +12088 -- optional +12089 ERRORS { +12090 systemFailure | +12091 dataMissing | +12092 unexpectedDataValue | +12093 facilityNotSupported | +12094 unidentifiedSubscriber | +12095 tracingBufferFull} +12096 CODE local:50 } +12097 + +``` + +``` + +12098 deactivateTraceMode OPERATION ::= { --Timer m +12099 ARGUMENT +12100 DeactivateTraceModeArg +12101 RESULT +12102 DeactivateTraceModeRes +12103 -- optional +12104 ERRORS { +12105 systemFailure | +12106 dataMissing | +12107 unexpectedDataValue | +12108 facilityNotSupported | +12109 unidentifiedSubscriber} +12110 CODE local:51 } +12111 + +``` + +``` + +12112 sendIMSI OPERATION ::= { --Timer m +12113 ARGUMENT +12114 ISDN-AddressString +12115 RESULT +12116 IMSI +12117 ERRORS { +12118 dataMissing | +12119 unexpectedDataValue | +12120 unknownSubscriber} +12121 CODE local:58 } +12122 + +``` + +``` + +12123 END + +``` + +## 17.6.3 Call Handling Operations + +``` + +12125 MAP-CallHandlingOperations { +12126 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12127 gsm-Network (1) modules (3) map-CallHandlingOperations (7) +12128 version21 (21)} +12129 +12130 DEFINITIONS +12131 +12132 ::= + +``` + +``` + +12133 +12134 BEGIN +12135 +12136 EXPORTS +12137 sendRoutingInfo, +12138 provideRoamingNumber, +12139 resumeCallHandling, +12140 setReportingState, +12141 statusReport, +12142 remoteUserFree, +12143 ist-Alert, +12144 ist-Command, +12145 releaseResources +12146 ; +12147 +12148 IMPORTS +12149 OPERATION +12150 FROM Remote-Operations-Information-Objects { +12151 joint-iso-itu-t remote-operations(4) +12152 informationObjects(5) version1(0) } +12153 +12154 systemFailure, +12155 dataMissing, +12156 unexpectedDataValue, +12157 facilityNotSupported, +12158 or-NotAllowed, +12159 unknownSubscriber, +12160 numberChanged, +12161 bearerServiceNotProvisioned, +12162 teleserviceNotProvisioned, +12163 noRoamingNumberAvailable, +12164 absentSubscriber, +12165 busySubscriber, +12166 noSubscriberReply, +12167 callBarred, +12168 forwardingViolation, +12169 forwardingFailed, +12170 cug-Reject, +12171 resourceLimitation, +12172 incompatibleTerminal, +12173 unidentifiedSubscriber +12174 +12175 FROM MAP-Errors { +12176 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12177 gsm-Network (1) modules (3) map-Errors (10) version21 (21) } +12178 SendRoutingInfoArg, +12179 SendRoutingInfoRes, +12180 ProvideRoamingNumberArg, +12181 ProvideRoamingNumberRes, +12182 ResumeCallHandlingArg, +12183 ResumeCallHandlingRes, +12184 SetReportingStateArg, +12185 SetReportingStateRes, +12186 StatusReportArg, +12187 StatusReportRes, +12188 RemoteUserFreeArg, +12189 RemoteUserFreeRes, +12190 IST-AlertArg, +12191 IST-AlertRes, +12192 IST-CommandArg, +12193 IST-CommandRes, +12194 ReleaseResourcesArg, +12195 ReleaseResourcesRes +12196 FROM MAP-CH-DataTypes { +12197 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12198 gsm-Network (1) modules (3) map-CH-DataTypes (13) version21 (21) } +12199 +12200 ; +12201 + +``` + +``` + +12202 sendRoutingInfo OPERATION ::= { --Timer m +12203 -- The timer is set to the upper limit of the range if the GMSC supports pre-paging. +12204 ARGUMENT +12205 SendRoutingInfoArg +12206 RESULT +12207 SendRoutingInfoRes +12208 ERRORS { +12209 systemFailure | +12210 dataMissing | +12211 unexpectedDataValue | +12212 facilityNotSupported | +12213 or-NotAllowed | +12214 unknownSubscriber | +12215 numberChanged | +12216 bearerServiceNotProvisioned | +12217 teleserviceNotProvisioned | +12218 absentSubscriber | +12219 busySubscriber | +12220 noSubscriberReply | +12221 callBarred | +12222 cug-Reject | +12223 forwardingViolation} +12224 CODE local:22 } +12225 +12226 provideRoamingNumber OPERATION ::= { --Timer m +12227 -- The timer is set to the upper limit of the range if the HLR supports pre-paging. +12228 ARGUMENT +12229 ProvideRoamingNumberArg +12230 RESULT +12231 ProvideRoamingNumberRes +12232 ERRORS { +12233 systemFailure | +12234 dataMissing | +12235 unexpectedDataValue | +12236 facilityNotSupported | +12237 or-NotAllowed | +12238 absentSubscriber | +12239 noRoamingNumberAvailable} +12240 CODE local:4 } +12241 +12242 resumeCallHandling OPERATION ::= { --Timer m +12243 ARGUMENT +12244 ResumeCallHandlingArg +12245 RESULT +12246 ResumeCallHandlingRes +12247 -- optional +12248 ERRORS { +12249 forwardingFailed | +12250 or-NotAllowed | +12251 unexpectedDataValue | +12252 dataMissing } +12253 CODE local:6 } +12254 +12255 setReportingState OPERATION ::= { --Timer m +12256 ARGUMENT +12257 SetReportingStateArg +12258 RESULT +12259 SetReportingStateRes +12260 -- optional +12261 ERRORS { +12262 systemFailure | +12263 unidentifiedSubscriber | +12264 unexpectedDataValue | +12265 dataMissing | +12266 resourceLimitation | +12267 facilityNotSupported} +12268 CODE local:73 } +12269 + +``` + +``` + +12270 statusReport OPERATION ::= { --Timer m +12271 ARGUMENT +12272 StatusReportArg +12273 RESULT +12274 StatusReportRes +12275 -- optional +12276 ERRORS { +12277 unknownSubscriber | +12278 systemFailure | +12279 unexpectedDataValue | +12280 dataMissing} +12281 CODE local:74 } +12282 +12283 remoteUserFree OPERATION ::= { --Timer m1 +12284 ARGUMENT +12285 RemoteUserFreeArg +12286 RESULT +12287 RemoteUserFreeRes +12288 ERRORS { +12289 unexpectedDataValue | +12290 dataMissing | +12291 incompatibleTerminal | +12292 absentSubscriber | +12293 systemFailure | +12294 busySubscriber} +12295 CODE local:75 } +12296 +12297 ist-Alert OPERATION ::= { --Timer m +12298 ARGUMENT +12299 IST-AlertArg +12300 RESULT +12301 IST-AlertRes +12302 -- optional +12303 ERRORS { +12304 unexpectedDataValue | +12305 resourceLimitation | +12306 unknownSubscriber | +12307 systemFailure | +12308 facilityNotSupported} +12309 CODE local:87 } +12310 +12311 ist-Command OPERATION ::= { --Timer m +12312 ARGUMENT +12313 IST-CommandArg +12314 RESULT +12315 IST-CommandRes +12316 -- optional +12317 ERRORS { +12318 unexpectedDataValue | +12319 resourceLimitation | +12320 unknownSubscriber | +12321 systemFailure | +12322 facilityNotSupported} +12323 CODE local:88 } +12324 +12325 releaseResources OPERATION ::= { --Timer m +12326 ARGUMENT +12327 ReleaseResourcesArg +12328 RESULT +12329 ReleaseResourcesRes +12330 -- optional +12331 ERRORS { +12332 unexpectedDataValue | +12333 systemFailure } +12334 CODE local:20 } +12335 +12336 END + +``` + +## 12337 17.6.4 Supplementary service operations + +``` + +12338 MAP-SupplementaryServiceOperations { +12339 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12340 gsm-Network (1) modules (3) map-SupplementaryServiceOperations (8) +12341 version21 (21)} +12342 +12343 DEFINITIONS +12344 +12345 ::= + +``` + +``` + +12346 +12347 BEGIN +12348 +12349 EXPORTS +12350 registerSS, +12351 eraseSS, +12352 activateSS, +12353 deactivateSS, +12354 interrogateSS, +12355 processUnstructuredSS-Request, +12356 unstructuredSS-Request, +12357 unstructuredSS-Notify, +12358 registerPassword, +12359 getPassword, +12360 ss-InvocationNotification, +12361 registerCC-Entry, +12362 eraseCC-Entry +12363 ; +12364 +12365 IMPORTS +12366 OPERATION +12367 FROM Remote-Operations-Information-Objects { +12368 joint-iso-itu-t remote-operations(4) +12369 informationObjects(5) version1(0)} +12370 +12371 systemFailure, +12372 dataMissing, +12373 unexpectedDataValue, +12374 unknownSubscriber, +12375 bearerServiceNotProvisioned, +12376 teleserviceNotProvisioned, +12377 callBarred, +12378 illegalSS-Operation, +12379 ss-ErrorStatus, +12380 ss-NotAvailable, +12381 ss-SubscriptionViolation, +12382 ss-Incompatibility, +12383 pw-RegistrationFailure, +12384 negativePW-Check, +12385 numberOfPW-AttemptsViolation, +12386 unknownAlphabet, +12387 ussd-Busy, +12388 absentSubscriber, +12389 illegalSubscriber, +12390 illegalEquipment, +12391 shortTermDenial, +12392 longTermDenial, +12393 facilityNotSupported +12394 FROM MAP-Errors { +12395 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12396 gsm-Network (1) modules (3) map-Errors (10) version21 (21)} +12397 +12398 RegisterSS-Arg, +12399 SS-Info, +12400 SS-ForBS-Code, +12401 InterrogateSS-Res, +12402 USSD-Arg, +12403 USSD-Res, +12404 Password, +12405 GuidanceInfo, +12406 SS-InvocationNotificationArg, +12407 SS-InvocationNotificationRes, +12408 RegisterCC-EntryArg, +12409 RegisterCC-EntryRes, +12410 EraseCC-EntryArg, +12411 EraseCC-EntryRes +12412 FROM MAP-SS-DataTypes { +12413 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12414 gsm-Network (1) modules (3) map-SS-DataTypes (14) version21 (21)} +12415 +12416 SS-Code +12417 FROM MAP-SS-Code { +12418 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12419 gsm-Network (1) modules (3) map-SS-Code (15) version21 (21)} +12420 ; +12421 +12422 +12423 -- supplementary service handling operations +12424 + +``` + +``` +12425 registerSS OPERATION ::= { --Timer m +12426 ARGUMENT +12427 RegisterSS-Arg +12428 RESULT +12429 SS-Info +12430 -- optional +12431 ERRORS { +12432 systemFailure | +12433 dataMissing | +12434 unexpectedDataValue | +12435 bearerServiceNotProvisioned | +12436 teleserviceNotProvisioned | +12437 callBarred | +12438 illegalSS-Operation | +12439 ss-ErrorStatus | +12440 ss-Incompatibility} +12441 CODE local:10 } +``` + +``` +12442 +12443 eraseSS OPERATION ::= { --Timer m +12444 ARGUMENT +12445 SS-ForBS-Code +12446 RESULT +12447 SS-Info +12448 -- optional +12449 ERRORS { +12450 systemFailure | +12451 dataMissing | +12452 unexpectedDataValue | +12453 bearerServiceNotProvisioned | +12454 teleserviceNotProvisioned | +12455 callBarred | +12456 illegalSS-Operation | +12457 ss-ErrorStatus +12458 } +12459 CODE local:11 } +``` + +``` +12460 +12461 activateSS OPERATION ::= { --Timer m +12462 ARGUMENT +12463 SS-ForBS-Code +12464 RESULT +12465 SS-Info +12466 -- optional +12467 ERRORS { +12468 systemFailure | +12469 dataMissing | +12470 unexpectedDataValue | +12471 bearerServiceNotProvisioned | +12472 teleserviceNotProvisioned | +12473 callBarred | +12474 illegalSS-Operation | +12475 ss-ErrorStatus | +12476 ss-SubscriptionViolation | +12477 ss-Incompatibility | +12478 negativePW-Check | +12479 numberOfPW-AttemptsViolation} +12480 CODE local:12 } +``` + +``` +12481 +12482 deactivateSS OPERATION ::= { --Timer m +12483 ARGUMENT +12484 SS-ForBS-Code +12485 RESULT +12486 SS-Info +12487 -- optional +12488 ERRORS { +12489 systemFailure | +12490 dataMissing | +12491 unexpectedDataValue | +12492 bearerServiceNotProvisioned | +12493 teleserviceNotProvisioned | +12494 callBarred | +12495 illegalSS-Operation | +12496 ss-ErrorStatus | +12497 ss-SubscriptionViolation | +12498 negativePW-Check | +12499 numberOfPW-AttemptsViolation} +12500 CODE local:13 } +``` + +``` +12501 +``` + +``` + +12502 interrogateSS OPERATION ::= { --Timer m +12503 ARGUMENT +12504 SS-ForBS-Code +12505 RESULT +12506 InterrogateSS-Res +12507 ERRORS { +12508 systemFailure | +12509 dataMissing | +12510 unexpectedDataValue | +12511 bearerServiceNotProvisioned | +12512 teleserviceNotProvisioned | +12513 callBarred | +12514 illegalSS-Operation | +12515 ss-NotAvailable} +12516 CODE local:14 } +12517 +12518 processUnstructuredSS-Request OPERATION ::= {--Timer 10 minutes +12519 ARGUMENT +12520 USSD-Arg +12521 RESULT +12522 USSD-Res +12523 ERRORS { +12524 systemFailure | +12525 dataMissing | +12526 unexpectedDataValue | +12527 unknownAlphabet | +12528 callBarred} +12529 CODE local:59 } +12530 +12531 unstructuredSS-Request OPERATION ::= { --Timer ml +12532 ARGUMENT +12533 USSD-Arg +12534 RESULT +12535 USSD-Res +12536 -- optional +12537 ERRORS { +12538 systemFailure | +12539 dataMissing | +12540 unexpectedDataValue | +12541 absentSubscriber | +12542 illegalSubscriber | +12543 illegalEquipment | +12544 unknownAlphabet | +12545 ussd-Busy} +12546 CODE local:60 } +12547 +12548 unstructuredSS-Notify OPERATION ::= { --Timer ml +12549 ARGUMENT +12550 USSD-Arg +12551 RETURN RESULT TRUE +12552 ERRORS { +12553 systemFailure | +12554 dataMissing | +12555 unexpectedDataValue | +12556 absentSubscriber | +12557 illegalSubscriber | +12558 illegalEquipment | +12559 unknownAlphabet | +12560 ussd-Busy} +12561 CODE local:61 } +12562 + +``` + +``` + +12563 registerPassword OPERATION ::= { --Timer ml +12564 ARGUMENT +12565 SS-Code +12566 RESULT +12567 Password +12568 ERRORS { +12569 systemFailure | +12570 dataMissing | +12571 unexpectedDataValue | +12572 callBarred | +12573 ss-SubscriptionViolation | +12574 pw-RegistrationFailure | +12575 negativePW-Check | +12576 numberOfPW-AttemptsViolation} +12577 LINKED { +12578 getPassword} +12579 CODE local:17 } +12580 +12581 getPassword OPERATION ::= { --Timer m +12582 ARGUMENT +12583 GuidanceInfo +12584 RESULT +12585 Password +12586 CODE local:18 } +12587 +12588 ss-InvocationNotification OPERATION ::= { --Timer m +12589 ARGUMENT +12590 SS-InvocationNotificationArg +12591 RESULT +12592 SS-InvocationNotificationRes +12593 -- optional +12594 ERRORS { +12595 dataMissing | +12596 unexpectedDataValue | +12597 unknownSubscriber} +12598 CODE local:72 } +12599 +12600 registerCC-Entry OPERATION ::= { --Timer m +12601 ARGUMENT +12602 RegisterCC-EntryArg +12603 RESULT +12604 RegisterCC-EntryRes +12605 ERRORS { +12606 systemFailure | +12607 dataMissing | +12608 unexpectedDataValue | +12609 callBarred | +12610 illegalSS-Operation | +12611 ss-ErrorStatus | +12612 ss-Incompatibility | +12613 shortTermDenial | +12614 longTermDenial | +12615 facilityNotSupported} +12616 CODE local:76 } +12617 +12618 eraseCC-Entry OPERATION ::= { --Timer m +12619 ARGUMENT +12620 EraseCC-EntryArg +12621 RESULT +12622 EraseCC-EntryRes +12623 ERRORS { +12624 systemFailure | +12625 dataMissing | +12626 unexpectedDataValue | +12627 callBarred | +12628 illegalSS-Operation | +12629 ss-ErrorStatus} +12630 CODE local:77 } +12631 +12632 END + +``` + +## 12633 17.6.5 Short message service operations + +``` + +12634 MAP-ShortMessageServiceOperations { +12635 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12636 gsm-Network (1) modules (3) map-ShortMessageServiceOperations (9) +12637 version21 (21)} +12638 + +``` + +``` + +12639 DEFINITIONS +12640 +12641 ::= +12642 +12643 BEGIN +12644 +12645 EXPORTS +12646 sendRoutingInfoForSM, +12647 mo-ForwardSM, +12648 mt-ForwardSM, +12649 reportSM-DeliveryStatus, +12650 alertServiceCentre, +12651 informServiceCentre, +12652 readyForSM, +12653 mt-ForwardSM-VGCS +12654 ; +12655 +12656 IMPORTS +12657 OPERATION +12658 FROM Remote-Operations-Information-Objects { +12659 joint-iso-itu-t remote-operations(4) +12660 informationObjects(5) version1(0)} +12661 +12662 systemFailure, +12663 dataMissing, +12664 unexpectedDataValue, +12665 facilityNotSupported, +12666 unknownSubscriber, +12667 unidentifiedSubscriber, +12668 illegalSubscriber, +12669 illegalEquipment, +12670 teleserviceNotProvisioned, +12671 callBarred, +12672 subscriberBusyForMT-SMS, +12673 sm-DeliveryFailure, +12674 messageWaitingListFull, +12675 absentSubscriberSM +12676 FROM MAP-Errors { +12677 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12678 gsm-Network (1) modules (3) map-Errors (10) version21 (21)} +12679 +12680 RoutingInfoForSM-Arg, +12681 RoutingInfoForSM-Res, +12682 MO-ForwardSM-Arg, +12683 MO-ForwardSM-Res, +12684 MT-ForwardSM-Arg, +12685 MT-ForwardSM-Res, +12686 ReportSM-DeliveryStatusArg, +12687 ReportSM-DeliveryStatusRes, +12688 AlertServiceCentreArg, +12689 InformServiceCentreArg, +12690 ReadyForSM-Arg, +12691 ReadyForSM-Res, +12692 MT-ForwardSM-VGCS-Arg, +12693 MT-ForwardSM-VGCS-Res +12694 FROM MAP-SM-DataTypes { +12695 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12696 gsm-Network (1) modules (3) map-SM-DataTypes (16) version21 (21)} +12697 +12698 ; +12699 +12700 sendRoutingInfoForSM OPERATION ::= { --Timer m +12701 ARGUMENT +12702 RoutingInfoForSM-Arg +12703 RESULT +12704 RoutingInfoForSM-Res +12705 ERRORS { +12706 systemFailure | +12707 dataMissing | +12708 unexpectedDataValue | +12709 facilityNotSupported | +12710 unknownSubscriber | +12711 teleserviceNotProvisioned | +12712 callBarred | +12713 absentSubscriberSM} +12714 CODE local:45 } +12715 + +``` + +``` + +12716 mo-ForwardSM OPERATION ::= { --Timer ml +12717 ARGUMENT +12718 MO-ForwardSM-Arg +12719 RESULT +12720 MO-ForwardSM-Res +12721 -- optional +12722 ERRORS { +12723 systemFailure | +12724 unexpectedDataValue | +12725 facilityNotSupported | +12726 sm-DeliveryFailure} +12727 CODE local:46 } +12728 +12729 mt-ForwardSM OPERATION ::= { --Timer ml +12730 -- the timer value may be subject to negotiation between GMSC and IP-SM-GW +12731 ARGUMENT +12732 MT-ForwardSM-Arg +12733 RESULT +12734 MT-ForwardSM-Res +12735 -- optional +12736 ERRORS { +12737 systemFailure | +12738 dataMissing | +12739 unexpectedDataValue | +12740 facilityNotSupported | +12741 unidentifiedSubscriber | +12742 illegalSubscriber | +12743 illegalEquipment | +12744 subscriberBusyForMT-SMS | +12745 sm-DeliveryFailure | +12746 absentSubscriberSM} +12747 CODE local:44 } +12748 +12749 reportSM-DeliveryStatus OPERATION ::= { --Timer s +12750 ARGUMENT +12751 ReportSM-DeliveryStatusArg +12752 RESULT +12753 ReportSM-DeliveryStatusRes +12754 -- optional +12755 ERRORS { +12756 dataMissing | +12757 unexpectedDataValue | +12758 unknownSubscriber | +12759 messageWaitingListFull} +12760 CODE local:47 } +12761 +12762 alertServiceCentre OPERATION ::= { --Timer s +12763 ARGUMENT +12764 AlertServiceCentreArg +12765 RETURN RESULT TRUE +12766 ERRORS { +12767 systemFailure | +12768 dataMissing | +12769 unexpectedDataValue} +12770 CODE local:64 } +12771 +12772 informServiceCentre OPERATION ::= { --Timer s +12773 ARGUMENT +12774 InformServiceCentreArg +12775 CODE local:63 } +12776 +12777 readyForSM OPERATION ::= { --Timer m +12778 ARGUMENT +12779 ReadyForSM-Arg +12780 RESULT +12781 ReadyForSM-Res +12782 -- optional +12783 ERRORS { +12784 dataMissing | +12785 unexpectedDataValue | +12786 facilityNotSupported | +12787 unknownSubscriber} +12788 CODE local:66 } +12789 + +``` + +``` + +12790 mt-ForwardSM-VGCS OPERATION ::= { --Timer ml +12791 ARGUMENT +12792 MT-ForwardSM-VGCS-Arg +12793 RESULT +12794 MT-ForwardSM-VGCS-Res +12795 -- optional +12796 ERRORS { +12797 systemFailure | +12798 unexpectedDataValue } +12799 CODE local:21 } +12800 +12801 +12802 END + +``` + +## 12803 17.6.6 Errors + +``` + +12804 MAP-Errors { +12805 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12806 gsm-Network (1) modules (3) map-Errors (10) version21 (21)} +12807 +12808 DEFINITIONS +12809 +12810 ::= +12811 +12812 BEGIN +12813 +12814 EXPORTS +12815 +12816 -- generic errors +12817 systemFailure, +12818 dataMissing, +12819 unexpectedDataValue, +12820 facilityNotSupported, +12821 incompatibleTerminal, +12822 resourceLimitation, +12823 +12824 -- identification and numbering errors +12825 unknownSubscriber, +12826 numberChanged, +12827 unknownMSC, +12828 unidentifiedSubscriber, +12829 unknownEquipment, +12830 +12831 -- subscription errors +12832 roamingNotAllowed, +12833 illegalSubscriber, +12834 illegalEquipment, +12835 bearerServiceNotProvisioned, +12836 teleserviceNotProvisioned, +12837 +12838 -- handover errors +12839 noHandoverNumberAvailable, +12840 subsequentHandoverFailure, +12841 targetCellOutsideGroupCallArea, +12842 +12843 -- operation and maintenance errors +12844 tracingBufferFull, +12845 +12846 -- call handling errors +12847 or-NotAllowed, +12848 noRoamingNumberAvailable, +12849 busySubscriber, +12850 noSubscriberReply, +12851 absentSubscriber, +12852 callBarred, +12853 forwardingViolation, +12854 forwardingFailed, +12855 cug-Reject, +12856 +12857 -- any time interrogation errors +12858 ati-NotAllowed, +12859 +12860 -- any time information handling errors +12861 atsi-NotAllowed, +12862 atm-NotAllowed, +12863 informationNotAvailable, +12864 + +``` + +``` + +12865 -- supplementary service errors +12866 illegalSS-Operation, +12867 ss-ErrorStatus, +12868 ss-NotAvailable, +12869 ss-SubscriptionViolation, +12870 ss-Incompatibility, +12871 unknownAlphabet, +12872 ussd-Busy, +12873 pw-RegistrationFailure, +12874 negativePW-Check, +12875 numberOfPW-AttemptsViolation, +12876 shortTermDenial, +12877 longTermDenial, +12878 +12879 -- short message service errors +12880 subscriberBusyForMT-SMS, +12881 sm-DeliveryFailure, +12882 messageWaitingListFull, +12883 absentSubscriberSM, +12884 +12885 -- Group Call errors +12886 noGroupCallNumberAvailable, +12887 ongoingGroupCall, +12888 +12889 -- location service errors +12890 unauthorizedRequestingNetwork, +12891 unauthorizedLCSCClient, +12892 positionMethodFailure, +12893 unknownOrUnreachableLCSCClient, +12894 +12895 -- Mobility Management errors +12896 mm-EventNotSupported +12897 +12898 +12899 ; +12900 +12901 IMPORTS +12902 ERROR +12903 FROM Remote-Operations-Information-Objects {joint-iso-itu-t remote-operations(4) +12904 informationObjects(5) version1(0) } +12905 +12906 SS-Status +12907 FROM MAP-SS-DataTypes { +12908 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12909 gsm-Network (1) modules (3) map-SS-DataTypes (14) version21 (21)} +12910 +12911 SS-IncompatibilityCause, +12912 PW-RegistrationFailureCause, +12913 SM-DeliveryFailureCause, +12914 SystemFailureParam, +12915 DataMissingParam, +12916 UnexpectedDataParam, +12917 FacilityNotSupParam, +12918 UnknownSubscriberParam, +12919 NumberChangedParam, +12920 UnidentifiedSubParam, +12921 RoamingNotAllowedParam, +12922 IllegalSubscriberParam, +12923 IllegalEquipmentParam, +12924 BearerServNotProvParam, +12925 TeleservNotProvParam, +12926 TracingBufferFullParam, +12927 NoRoamingNbParam, +12928 OR-NotAllowedParam, +12929 AbsentSubscriberParam, +12930 BusySubscriberParam, +12931 NoSubscriberReplyParam, +12932 CallBarredParam, +12933 ForwardingViolationParam, +12934 ForwardingFailedParam, +12935 CUG-RejectParam, +12936 ATI-NotAllowedParam, +12937 SubBusyForMT-SMS-Param, +12938 MessageWaitListFullParam, +12939 AbsentSubscriberSM-Param, +12940 ResourceLimitationParam, +12941 NoGroupCallNbParam, +12942 IncompatibleTerminalParam, +12943 ShortTermDenialParam, + +``` + +``` + +12944 LongTermDenialParam, +12945 UnauthorizedRequestingNetwork-Param, +12946 UnauthorizedLCSCClient-Param, +12947 PositionMethodFailure-Param, +12948 UnknownOrUnreachableLCSCClient-Param, +12949 MM-EventNotSupported-Param, +12950 ATSI-NotAllowedParam, +12951 ATM-NotAllowedParam, +12952 IllegalSS-OperationParam, +12953 SS-NotAvailableParam, +12954 SS-SubscriptionViolationParam, +12955 InformationNotAvailableParam, +12956 TargetCellOutsideGCA-Param, +12957 OngoingGroupCallParam +12958 FROM MAP-ER-DataTypes { +12959 itu-t identified-organization (4) etsi (0) mobileDomain (0) +12960 gsm-Network (1) modules (3) map-ER-DataTypes (17) version21 (21)} +12961 ; +12962 +12963 -- generic errors +12964 +12965 systemFailure ERROR ::= { +12966 PARAMETER +12967 SystemFailureParam +12968 -- optional +12969 CODE local:34 } +12970 +12971 dataMissing ERROR ::= { +12972 PARAMETER +12973 DataMissingParam +12974 -- optional +12975 -- DataMissingParam must not be used in version <3 +12976 CODE local:35 } +12977 +12978 unexpectedDataValue ERROR ::= { +12979 PARAMETER +12980 UnexpectedDataParam +12981 -- optional +12982 -- UnexpectedDataParam must not be used in version <3 +12983 CODE local:36 } +12984 +12985 facilityNotSupported ERROR ::= { +12986 PARAMETER +12987 FacilityNotSupParam +12988 -- optional +12989 -- FacilityNotSupParam must not be used in version <3 +12990 CODE local:21 } +12991 +12992 incompatibleTerminal ERROR ::= { +12993 PARAMETER +12994 IncompatibleTerminalParam +12995 -- optional +12996 CODE local:28 } +12997 +12998 resourceLimitation ERROR ::= { +12999 PARAMETER +13000 ResourceLimitationParam +13001 -- optional +13002 CODE local:51 } +13003 +13004 -- identification and numbering errors +13005 +13006 unknownSubscriber ERROR ::= { +13007 PARAMETER +13008 UnknownSubscriberParam +13009 -- optional +13010 -- UnknownSubscriberParam must not be used in version <3 +13011 CODE local:1 } +13012 +13013 numberChanged ERROR ::= { +13014 PARAMETER +13015 NumberChangedParam +13016 -- optional +13017 CODE local:44 } +13018 +13019 unknownMSC ERROR ::= { +13020 CODE local:3 } + +``` + +``` + +13021 +13022 unidentifiedSubscriber ERROR ::= { +13023 PARAMETER +13024 UnidentifiedSubParam +13025 -- optional +13026 -- UnidentifiedSubParam must not be used in version <3 +13027 CODE local:5 } +13028 +13029 unknownEquipment ERROR ::= { +13030 CODE local:7 } +13031 +13032 -- subscription errors +13033 +13034 roamingNotAllowed ERROR ::= { +13035 PARAMETER +13036 RoamingNotAllowedParam +13037 CODE local:8 } +13038 +13039 illegalSubscriber ERROR ::= { +13040 PARAMETER +13041 IllegalSubscriberParam +13042 -- optional +13043 -- IllegalSubscriberParam must not be used in version <3 +13044 CODE local:9 } +13045 +13046 illegalEquipment ERROR ::= { +13047 PARAMETER +13048 IllegalEquipmentParam +13049 -- optional +13050 -- IllegalEquipmentParam must not be used in version <3 +13051 CODE local:12 } +13052 +13053 bearerServiceNotProvisioned ERROR ::= { +13054 PARAMETER +13055 BearerServNotProvParam +13056 -- optional +13057 -- BearerServNotProvParam must not be used in version <3 +13058 CODE local:10 } +13059 +13060 teleserviceNotProvisioned ERROR ::= { +13061 PARAMETER +13062 TeleservNotProvParam +13063 -- optional +13064 -- TeleservNotProvParam must not be used in version <3 +13065 CODE local:11 } +13066 +13067 -- handover errors +13068 +13069 noHandoverNumberAvailable ERROR ::= { +13070 CODE local:25 } +13071 +13072 subsequentHandoverFailure ERROR ::= { +13073 CODE local:26 } +13074 +13075 targetCellOutsideGroupCallArea ERROR ::= { +13076 PARAMETER +13077 TargetCellOutsideGCA-Param +13078 -- optional +13079 CODE local:42 } +13080 +13081 -- operation and maintenance errors +13082 +13083 tracingBufferFull ERROR ::= { +13084 PARAMETER +13085 TracingBufferFullParam +13086 -- optional +13087 CODE local: 40 } +13088 +13089 -- call handling errors +13090 +13091 noRoamingNumberAvailable ERROR ::= { +13092 PARAMETER +13093 NoRoamingNbParam +13094 -- optional +13095 CODE local:39 } +13096 + +``` + +``` +13097 absentSubscriber ERROR ::= { +13098 PARAMETER +13099 AbsentSubscriberParam +13100 -- optional +13101 -- AbsentSubscriberParam must not be used in version <3 +13102 CODE local:27 } +``` + +13103 + +``` +13104 busySubscriber ERROR ::= { +13105 PARAMETER +13106 BusySubscriberParam +13107 -- optional +13108 CODE local:45 } +``` + +13109 + +``` +13110 noSubscriberReply ERROR ::= { +13111 PARAMETER +13112 NoSubscriberReplyParam +13113 -- optional +13114 CODE local:46 } +``` + +13115 + +``` +13116 callBarred ERROR ::= { +13117 PARAMETER +13118 CallBarredParam +13119 -- optional +13120 CODE local:13 } +``` + +13121 + +``` +13122 forwardingViolation ERROR ::= { +13123 PARAMETER +13124 ForwardingViolationParam +13125 -- optional +13126 CODE local:14 } +``` + +13127 + +``` +13128 forwardingFailed ERROR ::= { +13129 PARAMETER +13130 ForwardingFailedParam +13131 -- optional +13132 CODE local:47 } +``` + +13133 + +``` +13134 cug-Reject ERROR ::= { +13135 PARAMETER +13136 CUG-RejectParam +13137 -- optional +13138 CODE local:15 } +``` + +13139 + +``` +13140 or-NotAllowed ERROR ::= { +13141 PARAMETER +13142 OR-NotAllowedParam +13143 -- optional +13144 CODE local:48 } +``` + +13145 + +13146 -- any time interrogation errors + +``` +13147 ati-NotAllowed ERROR ::= { +13148 PARAMETER +13149 ATI-NotAllowedParam +13150 -- optional +13151 CODE local:49 } +``` + +13152 + +13153 -- any time information handling errors + +``` +13154 atsi-NotAllowed ERROR ::= { +13155 PARAMETER +13156 ATSI-NotAllowedParam +13157 -- optional +13158 CODE local:60 } +``` + +13159 + +``` +13160 atm-NotAllowed ERROR ::= { +13161 PARAMETER +13162 ATM-NotAllowedParam +13163 -- optional +13164 CODE local:61 } +``` + +13165 + +``` +13166 informationNotAvailable ERROR ::= { +13167 PARAMETER +13168 InformationNotAvailableParam +13169 -- optional +13170 CODE local:62 } +``` + +13171 + +13172 -- supplementary service errors + +13173 + +``` + +13174 illegalSS-Operation ERROR ::= { +13175 PARAMETER +13176 IllegalSS-OperationParam +13177 -- optional +13178 -- IllegalSS-OperationParam must not be used in version <3 +13179 CODE local:16 } +13180 +13181 ss-ErrorStatus ERROR ::= { +13182 PARAMETER +13183 SS-Status +13184 -- optional +13185 CODE local:17 } +13186 +13187 ss-NotAvailable ERROR ::= { +13188 PARAMETER +13189 SS-NotAvailableParam +13190 -- optional +13191 -- SS-NotAvailableParam must not be used in version <3 +13192 CODE local:18 } +13193 +13194 ss-SubscriptionViolation ERROR ::= { +13195 PARAMETER +13196 SS-SubscriptionViolationParam +13197 -- optional +13198 -- SS-SubscriptionViolationParam must not be used in version <3 +13199 CODE local:19 } +13200 +13201 ss-Incompatibility ERROR ::= { +13202 PARAMETER +13203 SS-IncompatibilityCause +13204 -- optional +13205 CODE local:20 } +13206 +13207 unknownAlphabet ERROR ::= { +13208 CODE local:71 } +13209 +13210 ussd-Busy ERROR ::= { +13211 CODE local:72 } +13212 +13213 pw-RegistrationFailure ERROR ::= { +13214 PARAMETER +13215 PW-RegistrationFailureCause +13216 CODE local:37 } +13217 +13218 negativePW-Check ERROR ::= { +13219 CODE local:38 } +13220 +13221 numberOfPW-AttemptsViolation ERROR ::= { +13222 CODE local:43 } +13223 +13224 shortTermDenial ERROR ::= { +13225 PARAMETER +13226 ShortTermDenialParam +13227 -- optional +13228 CODE local:29 } +13229 +13230 longTermDenial ERROR ::= { +13231 PARAMETER +13232 LongTermDenialParam +13233 -- optional +13234 CODE local:30 } +13235 +13236 -- short message service errors +13237 +13238 subscriberBusyForMT-SMS ERROR ::= { +13239 PARAMETER +13240 SubBusyForMT-SMS-Param +13241 -- optional +13242 CODE local:31 } +13243 +13244 sm-DeliveryFailure ERROR ::= { +13245 PARAMETER +13246 SM-DeliveryFailureCause +13247 CODE local:32 } +13248 + +``` + +``` + +13249 messageWaitingListFull ERROR ::= { +13250 PARAMETER +13251 MessageWaitListFullParam +13252 -- optional +13253 CODE local:33 } +13254 +13255 absentSubscriberSM ERROR ::= { +13256 PARAMETER +13257 AbsentSubscriberSM-Param +13258 -- optional +13259 CODE local:6 } +13260 +13261 -- Group Call errors +13262 +13263 noGroupCallNumberAvailable ERROR ::= { +13264 PARAMETER +13265 NoGroupCallNbParam +13266 -- optional +13267 CODE local:50 } +13268 +13269 ongoingGroupCall ERROR ::= { +13270 PARAMETER +13271 OngoingGroupCallParam +13272 -- optional +13273 CODE local:22 } +13274 +13275 -- location service errors +13276 +13277 unauthorizedRequestingNetwork ERROR ::= { +13278 PARAMETER +13279 UnauthorizedRequestingNetwork-Param +13280 -- optional +13281 CODE local:52 } +13282 +13283 unauthorizedLCSCClient ERROR ::= { +13284 PARAMETER +13285 UnauthorizedLCSCClient-Param +13286 -- optional +13287 CODE local:53 } +13288 +13289 positionMethodFailure ERROR ::= { +13290 PARAMETER +13291 PositionMethodFailure-Param +13292 -- optional +13293 CODE local:54 } +13294 +13295 unknownOrUnreachableLCSCClient ERROR ::= { +13296 PARAMETER +13297 UnknownOrUnreachableLCSCClient-Param +13298 -- optional +13299 CODE local:58 } +13300 +13301 mm-EventNotSupported ERROR ::= { +13302 PARAMETER +13303 MM-EventNotSupported-Param +13304 -- optional +13305 CODE local:59 } +13306 +13307 +13308 END + +``` + +## 13309 17.6.7 Group Call operations + +``` + +13310 MAP-Group-Call-Operations { +13311 itu-t identified-organization (4) etsi (0) mobileDomain (0) +13312 gsm-Network (1) modules (3) map-Group-Call-Operations (22) +13313 version21 (21)} +13314 +13315 DEFINITIONS +13316 +13317 ::= +13318 +13319 BEGIN +13320 +13321 EXPORTS +13322 prepareGroupCall, +13323 sendGroupCallEndSignal, + +``` + +``` + +13324 forwardGroupCallSignalling, +13325 processGroupCallSignalling, +13326 sendGroupCallInfo +13327 ; +13328 +13329 IMPORTS +13330 OPERATION +13331 FROM Remote-Operations-Information-Objects { +13332 joint-iso-itu-t remote-operations(4) +13333 informationObjects(5) version1(0)} +13334 +13335 systemFailure, +13336 unexpectedDataValue, +13337 noGroupCallNumberAvailable, +13338 ongoingGroupCall, +13339 unknownSubscriber, +13340 teleserviceNotProvisioned, +13341 dataMissing +13342 FROM MAP-Errors { +13343 itu-t identified-organization (4) etsi (0) mobileDomain (0) +13344 gsm-Network (1) modules (3) map-Errors (10) version21 (21)} +13345 +13346 PrepareGroupCallArg, +13347 PrepareGroupCallRes, +13348 SendGroupCallEndSignalArg, +13349 SendGroupCallEndSignalRes, +13350 ForwardGroupCallSignallingArg, +13351 ProcessGroupCallSignallingArg, +13352 SendGroupCallInfoArg, +13353 SendGroupCallInfoRes +13354 FROM MAP-GR-DataTypes { +13355 itu-t identified-organization (4) etsi (0) mobileDomain (0) +13356 gsm-Network (1) modules (3) map-GR-DataTypes (23) version21 (21)} +13357 +13358 ; +13359 +13360 prepareGroupCall OPERATION ::= { --Timer m +13361 ARGUMENT +13362 PrepareGroupCallArg +13363 RESULT +13364 PrepareGroupCallRes +13365 ERRORS { +13366 systemFailure | +13367 noGroupCallNumberAvailable | +13368 unexpectedDataValue} +13369 CODE local:39 } +13370 +13371 sendGroupCallEndSignal OPERATION ::= { --Timer l +13372 ARGUMENT +13373 SendGroupCallEndSignalArg +13374 RESULT +13375 SendGroupCallEndSignalRes +13376 CODE local:40 } +13377 +13378 processGroupCallSignalling OPERATION ::= { --Timer s +13379 ARGUMENT +13380 ProcessGroupCallSignallingArg +13381 CODE local:41 } +13382 +13383 forwardGroupCallSignalling OPERATION ::= { --Timer s +13384 ARGUMENT +13385 ForwardGroupCallSignallingArg +13386 CODE local:42 } +13387 +13388 sendGroupCallInfo OPERATION ::= { --Timer m +13389 ARGUMENT +13390 SendGroupCallInfoArg +13391 RESULT +13392 SendGroupCallInfoRes +13393 ERRORS { +13394 systemFailure | +13395 ongoingGroupCall | +13396 unexpectedDataValue | +13397 dataMissing | +13398 teleserviceNotProvisioned | +13399 unknownSubscriber} +13400 CODE local:84 } +13401 + +``` + +13402 +13403 END + +## 17.6.8 Location service operations + +``` +13404 MAP-LocationServiceOperations { +13405 itu-t identified-organization (4) etsi (0) mobileDomain (0) +13406 gsm-Network (1) modules (3) map-LocationServiceOperations (24) +13407 version21 (21)} +13408 +13409 DEFINITIONS +13410 +13411 ::= +13412 +13413 BEGIN +13414 +13415 EXPORTS +13416 provideSubscriberLocation, +13417 sendRoutingInfoForLCS, +13418 subscriberLocationReport +13419 ; +13420 +13421 IMPORTS +13422 OPERATION +13423 FROM Remote-Operations-Information-Objects { +13424 joint-iso-itu-t remote-operations(4) +13425 informationObjects(5) version1(0)} +13426 +13427 systemFailure, +13428 dataMissing, +13429 unexpectedDataValue, +13430 facilityNotSupported, +13431 unknownSubscriber, +13432 absentSubscriber, +13433 unauthorizedRequestingNetwork, +13434 unauthorizedLCSClient, +13435 positionMethodFailure, +13436 resourceLimitation, +13437 unknownOrUnreachableLCSClient, +13438 unidentifiedSubscriber, +13439 illegalEquipment, +13440 illegalSubscriber +13441 FROM MAP-Errors { +13442 itu-t identified-organization (4) etsi (0) mobileDomain (0) +13443 gsm-Network (1) modules (3) map-Errors (10) version21 (21)} +13444 +13445 RoutingInfoForLCS-Arg, +13446 RoutingInfoForLCS-Res, +13447 ProvideSubscriberLocation-Arg, +13448 ProvideSubscriberLocation-Res, +13449 SubscriberLocationReport-Arg, +13450 SubscriberLocationReport-Res +13451 FROM MAP-LCS-DataTypes { +13452 itu-t identified-organization (4) etsi (0) mobileDomain (0) +13453 gsm-Network (1) modules (3) map-LCS-DataTypes (25) version21 (21)} +13454 ; +13455 +13456 sendRoutingInfoForLCS OPERATION ::= { --Timer m +13457 ARGUMENT +13458 RoutingInfoForLCS-Arg +13459 RESULT +13460 RoutingInfoForLCS-Res +13461 ERRORS { +13462 systemFailure | +13463 dataMissing | +13464 unexpectedDataValue | +13465 facilityNotSupported | +13466 unknownSubscriber | +13467 absentSubscriber | +13468 unauthorizedRequestingNetwork } +13469 CODE local:85 } +``` + +``` + +13471 provideSubscriberLocation OPERATION ::= { --Timer ml +13472 ARGUMENT +13473 ProvideSubscriberLocation-Arg +13474 RESULT +13475 ProvideSubscriberLocation-Res +13476 ERRORS { +13477 systemFailure | +13478 dataMissing | +13479 unexpectedDataValue | +13480 facilityNotSupported | +13481 unidentifiedSubscriber | +13482 illegalSubscriber | +13483 illegalEquipment | +13484 absentSubscriber | +13485 unauthorizedRequestingNetwork | +13486 unauthorizedLCSClient | +13487 positionMethodFailure } +13488 CODE local:83 } + +``` + +``` + +13489 +13490 subscriberLocationReport OPERATION ::= { --Timer m +13491 ARGUMENT +13492 SubscriberLocationReport-Arg +13493 RESULT +13494 SubscriberLocationReport-Res +13495 ERRORS { +13496 systemFailure | +13497 dataMissing | +13498 resourceLimitation | +13499 unexpectedDataValue | +13500 unknownSubscriber | +13501 unauthorizedRequestingNetwork | +13502 unknownOrUnreachableLCSClient } +13503 CODE local:86 } + +``` + +``` + +13504 +13505 +13506 END + +``` + +1 + +## 17.6.9 Void + +2 + +## 3 17.7 MAP constants and data types + +### 4 17.7.1 Mobile Service data types + +``` + +5 MAP-MS-DataTypes { +6 itu-t identified-organization (4) etsi (0) mobileDomain (0) +7 gsm-Network (1) modules (3) map-MS-DataTypes (11) version21 (21)} +8 +9 DEFINITIONS +10 +11 IMPLICIT TAGS +12 +13 ::= +14 +15 BEGIN +16 +17 EXPORTS +18 +19 -- location registration types +20 UpdateLocationArg, +21 UpdateLocationRes, +22 CancelLocationArg, +23 CancelLocationRes, +24 PurgeMS-Arg, +25 PurgeMS-Res, +26 SendIdentificationArg, +27 SendIdentificationRes, +28 UpdateGprsLocationArg, +29 UpdateGprsLocationRes, +30 IST-SupportIndicator, +31 SupportedLCS-CapabilitySets, +32 UpdateVcsgLocationArg, + +``` + +``` +33 UpdateVcsgLocationRes, +34 CancelVcsgLocationArg, +35 CancelVcsgLocationRes, +36 +37 +38 -- handover types +39 ForwardAccessSignalling-Arg, +40 PrepareHO-Arg, +41 PrepareHO-Res, +42 PrepareSubsequentHO-Arg, +43 PrepareSubsequentHO-Res, +44 ProcessAccessSignalling-Arg, +45 SendEndSignal-Arg, +46 SendEndSignal-Res, +47 +48 -- authentication management types +49 SendAuthenticationInfoArg, +50 SendAuthenticationInfoRes, +51 AuthenticationFailureReportArg, +52 AuthenticationFailureReportRes, +53 +54 -- security management types +55 Kc, +56 Cksn, +57 +58 -- equipment management types +59 CheckIMEI-Arg, +60 CheckIMEI-Res, +61 +62 -- subscriber management types +63 InsertSubscriberDataArg, +64 InsertSubscriberDataRes, +65 LSAIdentity, +66 DeleteSubscriberDataArg, +67 DeleteSubscriberDataRes, +68 Ext-QoS-Subscribed, +69 Ext2-QoS-Subscribed, +70 Ext3-QoS-Subscribed, +71 Ext4-QoS-Subscribed, +72 SubscriberData, +73 ODB-Data, +74 SubscriberStatus, +75 ZoneCodeList, +76 maxNumOfZoneCodes, +77 O-CSI, +78 D-CSI, +79 O-BcsmCamelTDPCriteriaList, +80 T-BCSM-CAMEL-TDP-CriteriaList, +81 SS-CSI, +82 ServiceKey, +83 DefaultCallHandling, +84 DefaultSMS-Handling, +85 DefaultGPRS-Handling, +86 CamelCapabilityHandling, +87 BasicServiceCriteria, +88 SupportedCamelPhases, +89 OfferedCamel4CSIs, +90 OfferedCamel4Functionalities, +91 maxNumOfCamelTDPData, +92 CUG-Index, +93 CUG-Info, +94 CUG-Interlock, +95 InterCUG-Restrictions, +96 IntraCUG-Options, +97 NotificationToMSUser, +98 QoS-Subscribed, +99 IST-AlertTimerValue, +100 T-CSI, +101 T-BcsmTriggerDetectionPoint, +102 APN, +103 AdditionalInfo, +104 +105 -- fault recovery types +106 ResetArg, +107 RestoreDataArg, +108 RestoreDataRes, +109 +``` + +``` + +110 -- provide subscriber info types +111 GeographicalInformation, +112 MS-Classmark2, +113 GPRSMSClass, +114 +115 -- subscriber information enquiry types +116 ProvideSubscriberInfoArg, +117 ProvideSubscriberInfoRes, +118 SubscriberInfo, +119 LocationInformation, +120 LocationInformationGPRS, +121 SubscriberState, +122 GPRSChargingID, +123 MNPInfoRes, +124 RouteingNumber, +125 +126 -- any time information enquiry types +127 AnyTimeInterrogationArg, +128 AnyTimeInterrogationRes, +129 +130 -- any time information handling types +131 AnyTimeSubscriptionInterrogationArg, +132 AnyTimeSubscriptionInterrogationRes, +133 AnyTimeModificationArg, +134 AnyTimeModificationRes, +135 +136 -- subscriber data modification notification types +137 NoteSubscriberDataModifiedArg, +138 NoteSubscriberDataModifiedRes, +139 +140 -- gprs location information retrieval types +141 SendRoutingInfoForGprsArg, +142 SendRoutingInfoForGprsRes, +143 +144 -- failure reporting types +145 FailureReportArg, +146 FailureReportRes, +147 +148 -- gprs notification types +149 NoteMsPresentForGprsArg, +150 NoteMsPresentForGprsRes, +151 +152 -- Mobility Management types +153 NoteMM-EventArg, +154 NoteMM-EventRes, +155 NumberPortabilityStatus, +156 PagingArea, +157 +158 -- VGCS / VBS types types +159 GroupId, +160 Long-GroupId, +161 AdditionalSubscriptions +162 +163 ; +164 +165 IMPORTS +166 maxNumOfSS, +167 SS-SubscriptionOption, +168 SS-List, +169 SS-ForBS-Code, +170 Password, +171 OverrideCategory, +172 CliRestrictionOption +173 FROM MAP-SS-DataTypes { +174 itu-t identified-organization (4) etsi (0) mobileDomain (0) +175 gsm-Network (1) modules (3) map-SS-DataTypes (14) version21 (21)} +176 +177 SS-Code +178 FROM MAP-SS-Code { +179 itu-t identified-organization (4) etsi (0) mobileDomain (0) +180 gsm-Network (1) modules (3) map-SS-Code (15) version21 (21)} +181 +182 Ext-BearerServiceCode +183 FROM MAP-BS-Code { +184 itu-t identified-organization (4) etsi (0) mobileDomain (0) +185 gsm-Network (1) modules (3) map-BS-Code (20) version21 (21)} +186 +187 Ext-TeleserviceCode +188 FROM MAP-TS-Code { + +``` + +``` + +189 itu-t identified-organization (4) etsi (0) mobileDomain (0) +190 gsm-Network (1) modules (3) map-TS-Code (19) version21 (21)} +191 +192 AddressString, +193 ISDN-AddressString, +194 ISDN-SubaddressString, +195 FTN-AddressString, +196 AccessNetworkSignalInfo, +197 IMSI, +198 IMEI, +199 TMSI, +200 HLR-List, +201 LMSI, +202 Identity, +203 GlobalCellId, +204 CellGlobalIdOrServiceAreaIdOrLAI, +205 Ext-BasicServiceCode, +206 NAEA-PreferredCI, +207 EMLPP-Info, +208 MC-SS-Info, +209 SubscriberIdentity, +210 AgeOfLocationInformation, +211 LCSCClientExternalID, +212 LCSCClientInternalID, +213 Ext-SS-Status, +214 LCSServiceTypeID, +215 ASCI-CallReference, +216 TBCD-STRING, +217 LAIFixedLength, +218 PLMN-Id, +219 EMLPP-Priority, +220 GSN-Address, +221 DiameterIdentity, +222 Time, +223 E-UTRAN-CGI, +224 NR-CGI, +225 TA-Id, +226 NR-TA-Id, +227 RAIdentity, +228 NetworkNodeDiameterAddress +229 FROM MAP-CommonDataTypes { +230 itu-t identified-organization (4) etsi (0) mobileDomain (0) +231 gsm-Network (1) modules (3) map-CommonDataTypes (18) version21 (21)} +232 +233 ExtensionContainer +234 FROM MAP-ExtensionDataTypes { +235 itu-t identified-organization (4) etsi (0) mobileDomain (0) +236 gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version21 (21)} +237 +238 AbsentSubscriberDiagnosticSM +239 FROM MAP-ER-DataTypes { +240 itu-t identified-organization (4) etsi (0) mobileDomain (0) +241 gsm-Network (1) modules (3) map-ER-DataTypes (17) version21 (21)} +242 +243 TracePropagationList +244 FROM MAP-OM-DataTypes { +245 itu-t identified-organization (4) etsi (0) mobileDomain (0) +246 gsm-Network (1) modules (3) map-OM-DataTypes (12) version21 (21)} +247 +248 ; +249 +250 -- location registration types +251 + +``` + +``` + +252 UpdateLocationArg ::= SEQUENCE { +253 imsi IMSI, +254 msc-Number [1] ISDN-AddressString, +255 vlr-Number ISDN-AddressString, +256 lmsi [10] LMSI OPTIONAL, +257 extensionContainer ExtensionContainer OPTIONAL, +258 ... , +259 vlr-Capability [6] VLR-Capability OPTIONAL, +260 informPreviousNetworkEntity [11] NULL OPTIONAL, +261 cs-LCS-NotSupportedByUE [12] NULL OPTIONAL, +262 v-gmlc-Address [2] GSN-Address OPTIONAL, +263 add-info [13] ADD-Info OPTIONAL, +264 pagingArea [14] PagingArea OPTIONAL, +265 skipSubscriberDataUpdate [15] NULL OPTIONAL, +266 -- The skipSubscriberDataUpdate parameter in the UpdateLocationArg and the ADD-Info +267 -- structures carry the same semantic. +268 restorationIndicator [16] NULL OPTIONAL, +269 eplmn-List [3] EPLMN-List OPTIONAL, +270 mme-DiameterAddress [4] NetworkNodeDiameterAddress OPTIONAL +271 } +272 +273 VLR-Capability ::= SEQUENCE{ +274 supportedCamelPhases [0] SupportedCamelPhases OPTIONAL, +275 extensionContainer ExtensionContainer OPTIONAL, +276 ... , +277 solsaSupportIndicator [2] NULL OPTIONAL, +278 istSupportIndicator [1] IST-SupportIndicator OPTIONAL, +279 superChargerSupportedInServingNetworkEntity [3] SuperChargerInfo OPTIONAL, +280 longFTN-Supported [4] NULL OPTIONAL, +281 supportedLCS-CapabilitySets [5] SupportedLCS-CapabilitySets OPTIONAL, +282 offeredCamel4CSIs [6] OfferedCamel4CSIs OPTIONAL, +283 supportedRAT-TypesIndicator [7] SupportedRAT-Types OPTIONAL, +284 longGroupID-Supported [8] NULL OPTIONAL, +285 mtRoamingForwardingSupported [9] NULL OPTIONAL, +286 msisdn-lessOperation-Supported [10] NULL OPTIONAL, +287 reset-ids-Supported [11] NULL OPTIONAL } +288 +289 SupportedRAT-Types ::= BIT STRING { +290 utran (0), +291 geran (1), +292 gan (2), +293 i-hspa-evolution (3), +294 e-utran (4), +295 nb-iot (5)} (SIZE (2..8)) +296 -- exception handling: bits 6 to 7 shall be ignored if received and not understood +297 +298 +299 +300 SuperChargerInfo ::= CHOICE { +301 sendSubscriberData [0] NULL, +302 subscriberDataStored [1] AgeIndicator } +303 +304 AgeIndicator ::= OCTET STRING (SIZE (1..6)) +305 -- The internal structure of this parameter is implementation specific. +306 +307 IST-SupportIndicator ::= ENUMERATED { +308 basicISTSupported (0), +309 istCommandSupported (1), +310 ...} +311 -- exception handling: +312 -- reception of values > 1 shall be mapped to ' istCommandSupported ' +313 + +``` + +``` + +314 SupportedLCS-CapabilitySets ::= BIT STRING { +315 lcsCapabilitySet1 (0), +316 lcsCapabilitySet2 (1), +317 lcsCapabilitySet3 (2), +318 lcsCapabilitySet4 (3) , +319 lcsCapabilitySet5 (4) } (SIZE (2..16)) +320 -- Core network signalling capability set1 indicates LCS Release98 or Release99 version. +321 -- Core network signalling capability set2 indicates LCS Release4. +322 -- Core network signalling capability set3 indicates LCS Release5. +323 -- Core network signalling capability set4 indicates LCS Release6. +324 -- Core network signalling capability set5 indicates LCS Release7 or later version. +325 -- A node shall mark in the BIT STRING all LCS capability sets it supports. +326 -- If no bit is set then the sending node does not support LCS. +327 -- If the parameter is not sent by an VLR then the VLR may support at most capability set1. +328 -- If the parameter is not sent by an SGSN then no support for LCS is assumed. +329 -- An SGSN is not allowed to indicate support of capability set1. +330 -- Other bits than listed above shall be discarded. +331 +332 UpdateLocationRes ::= SEQUENCE { +333 hlr-Number ISDN-AddressString, +334 extensionContainer ExtensionContainer OPTIONAL, +335 ..., +336 add-Capability NULL OPTIONAL, +337 pagingArea-Capability [0]NULL OPTIONAL } +338 +339 ADD-Info ::= SEQUENCE { +340 imeisv [0] IMEI, +341 skipSubscriberDataUpdate [1] NULL OPTIONAL, +342 -- The skipSubscriberDataUpdate parameter in the UpdateLocationArg and the ADD-Info +343 -- structures carry the same semantic. +344 ...} +345 +346 +347 PagingArea ::= SEQUENCE SIZE (1..5) OF LocationArea +348 +349 +350 LocationArea ::= CHOICE { +351 laiFixedLength [0] LAIFixedLength, +352 lac [1] LAC} +353 +354 +355 LAC ::= OCTET STRING (SIZE (2)) +356 -- Refers to Location Area Code of the Location Area Identification defined in +357 -- 3GPP TS 23.003 [17]. +358 -- Location Area Code according to 3GPP TS 24.008 [35] +359 +360 CancelLocationArg ::= [3] SEQUENCE { +361 identity Identity, +362 cancellationType CancellationType OPTIONAL, +363 extensionContainer ExtensionContainer OPTIONAL, +364 ..., +365 typeOfUpdate [0] TypeOfUpdate OPTIONAL, +366 mtrf-SupportedAndAuthorized [1] NULL OPTIONAL, +367 mtrf-SupportedAndNotAuthorized [2] NULL OPTIONAL, +368 newMSC-Number [3] ISDN-AddressString OPTIONAL, +369 newVLR-Number [4] ISDN-AddressString OPTIONAL, +370 new-lmsi [5] LMSI OPTIONAL, +371 reattach-Required [6] NULL OPTIONAL +372 } +373 --mtrf-SupportedAndAuthorized and mtrf-SupportedAndNotAuthorized shall not +374 -- both be present +375 +376 TypeOfUpdate ::= ENUMERATED { +377 sgsn-change (0), +378 mme-change (1), +379 ...} +380 -- TypeOfUpdate shall be absent if CancellationType is different from updateProcedure +381 -- and initialAttachProcedure +382 +383 CancellationType ::= ENUMERATED { +384 updateProcedure (0), +385 subscriptionWithdraw (1), +386 ..., +387 initialAttachProcedure (2) } +388 -- The HLR shall not send values other than listed above +389 + +``` + +``` + +390 CancelLocationRes ::= SEQUENCE { +391 extensionContainer ExtensionContainer OPTIONAL, +392 ... } +393 +394 PurgeMS-Arg ::= [3] SEQUENCE { +395 imsi IMSI, +396 vlr-Number [0] ISDN-AddressString OPTIONAL, +397 sgsn-Number [1] ISDN-AddressString OPTIONAL, +398 extensionContainer ExtensionContainer OPTIONAL, +399 ..., +400 locationInformation [2] LocationInformation OPTIONAL, +401 locationInformationGPRS [3] LocationInformationGPRS OPTIONAL, +402 locationInformationEPS [4] LocationInformationEPS OPTIONAL } +403 +404 PurgeMS-Res ::= SEQUENCE { +405 freezeTMSI [0] NULL OPTIONAL, +406 freezeP-TMSI [1] NULL OPTIONAL, +407 extensionContainer ExtensionContainer OPTIONAL, +408 ..., +409 freezeM-TMSI [2] NULL OPTIONAL } +410 +411 SendIdentificationArg ::= SEQUENCE { +412 tmsi TMSI, +413 numberOfRequestedVectors NumberOfRequestedVectors OPTIONAL, +414 -- within a dialogue numberOfRequestedVectors shall be present in +415 -- the first service request and shall not be present in subsequent service requests. +416 -- If received in a subsequent service request it shall be discarded. +417 segmentationProhibited NULL OPTIONAL, +418 extensionContainer ExtensionContainer OPTIONAL, +419 ..., +420 msc-Number ISDN-AddressString OPTIONAL, +421 previous-LAI [0] LAIFixedLength OPTIONAL, +422 hopCounter [1] HopCounter OPTIONAL, +423 mtRoamingForwardingSupported [2] NULL OPTIONAL, +424 newVLR-Number [3] ISDN-AddressString OPTIONAL, +425 new-imsi [4] LMSI OPTIONAL } +426 +427 HopCounter ::= INTEGER (0..3) +428 +429 SendIdentificationRes ::= [3] SEQUENCE { +430 imsi IMSI OPTIONAL, +431 -- IMSI shall be present in the first (or only) service response of a dialogue. +432 -- If multiple service requests are present in a dialogue then IMSI +433 -- shall not be present in any service response other than the first one. +434 authenticationSetList AuthenticationSetList OPTIONAL, +435 currentSecurityContext [2] CurrentSecurityContext OPTIONAL, +436 extensionContainer [3] ExtensionContainer OPTIONAL, +437 ..., +438 lastUsedLtePLMN-Id [4] PLMN-Id OPTIONAL, +439 mtCallPendingFlag [5] NULL OPTIONAL } +440 +441 -- authentication management types +442 +443 AuthenticationSetList ::= CHOICE { +444 tripletList [0] TripletList, +445 quintupletList [1] QuintupletList } +446 +447 TripletList ::= SEQUENCE SIZE (1..5) OF +448 AuthenticationTriplet +449 +450 QuintupletList ::= SEQUENCE SIZE (1..5) OF +451 AuthenticationQuintuplet +452 +453 AuthenticationTriplet ::= SEQUENCE { +454 rand RAND, +455 sres SRES, +456 kc Kc, +457 ... } +458 +459 AuthenticationQuintuplet ::= SEQUENCE { +460 rand RAND, +461 xres XRES, +462 ck CK, +463 ik IK, +464 autn AUTN, +465 ... } +466 + +``` + +``` + +467 CurrentSecurityContext ::= CHOICE { +468 gsm-SecurityContextData [0] GSM-SecurityContextData, +469 umts-SecurityContextData [1] UMTS-SecurityContextData } +470 +471 GSM-SecurityContextData ::= SEQUENCE { +472 kc Kc, +473 cksn Cksn, +474 ... } +475 +476 UMTS-SecurityContextData ::= SEQUENCE { +477 ck CK, +478 ik IK, +479 ksi KSI, +480 ... } +481 +482 RAND ::= OCTET STRING (SIZE (16)) +483 +484 SRES ::= OCTET STRING (SIZE (4)) +485 +486 Kc ::= OCTET STRING (SIZE (8)) +487 +488 XRES ::= OCTET STRING (SIZE (4..16)) +489 +490 CK ::= OCTET STRING (SIZE (16)) +491 +492 IK ::= OCTET STRING (SIZE (16)) +493 +494 AUTN ::= OCTET STRING (SIZE (16)) +495 +496 AUTS ::= OCTET STRING (SIZE (14)) +497 +498 Cksn ::= OCTET STRING (SIZE (1)) +499 -- The internal structure is defined in 3GPP TS 24.008 +500 +501 KSI ::= OCTET STRING (SIZE (1)) +502 -- The internal structure is defined in 3GPP TS 24.008 +503 +504 AuthenticationFailureReportArg ::= SEQUENCE { +505 imsi IMSI, +506 failureCause FailureCause, +507 extensionContainer ExtensionContainer OPTIONAL, +508 ... , +509 re-attempt BOOLEAN OPTIONAL, +510 accessType AccessType OPTIONAL, +511 rand RAND OPTIONAL, +512 vlr-Number [0] ISDN-AddressString OPTIONAL, +513 sgsn-Number [1] ISDN-AddressString OPTIONAL } +514 +515 AccessType ::= ENUMERATED { +516 call (0), +517 emergencyCall (1), +518 locationUpdating (2), +519 supplementaryService (3), +520 shortMessage (4), +521 gprsAttach (5), +522 routingAreaUpdating (6), +523 serviceRequest (7), +524 pdpContextActivation (8), +525 pdpContextDeactivation (9), +526 ..., +527 gprsDetach (10) } +528 -- exception handling: +529 -- received values greater than 10 shall be ignored. +530 +531 AuthenticationFailureReportRes ::= SEQUENCE { +532 extensionContainer ExtensionContainer OPTIONAL, +533 ... } +534 +535 FailureCause ::= ENUMERATED { +536 wrongUserResponse (0), +537 wrongNetworkSignature (1) } +538 +539 -- gprs location registration types +540 + +``` + +``` + +541 UpdateGprsLocationArg ::= SEQUENCE { +542 imsi IMSI, +543 sgsn-Number ISDN-AddressString, +544 gsn-Address GSN-Address, +545 extensionContainer ExtensionContainer OPTIONAL, +546 ... , +547 sgsn-Capability [0] SGSN-Capability OPTIONAL, +548 informPreviousNetworkEntity [1] NULL OPTIONAL, +549 ps-LCS-NotSupportedByUE [2] NULL OPTIONAL, +550 v-gmlc-Address [3] GSN-Address OPTIONAL, +551 add-info [4] ADD-Info OPTIONAL, +552 eps-info [5] EPS-Info OPTIONAL, +553 servingNodeTypeIndicator [6] NULL OPTIONAL, +554 skipSubscriberDataUpdate [7] NULL OPTIONAL, +555 usedRAT-Type [8] Used-RAT-Type OPTIONAL, +556 gprsSubscriptionDataNotNeeded [9] NULL OPTIONAL, +557 nodeTypeIndicator [10] NULL OPTIONAL, +558 areaRestricted [11] NULL OPTIONAL, +559 ue-reachableIndicator [12] NULL OPTIONAL, +560 epsSubscriptionDataNotNeeded [13] NULL OPTIONAL, +561 ue-srvcc-Capability [14] UE-SRVCC-Capability OPTIONAL, +562 eplmn-List [15] EPLMN-List OPTIONAL, +563 mmeNumberforMTSMS [16] ISDN-AddressString OPTIONAL, +564 smsRegisterRequest [17] SMSRegisterRequest OPTIONAL, +565 sms-Only [18] NULL OPTIONAL, +566 removalofMMERegistrationforSMS [22] NULL OPTIONAL, +567 sgsn-Name [19] DiameterIdentity OPTIONAL, +568 sgsn-Realm [20] DiameterIdentity OPTIONAL, +569 lgd-supportIndicator [21] NULL OPTIONAL, +570 adjacentPLMN-List [23] AdjacentPLMN-List OPTIONAL } +571 +572 SMSRegisterRequest ::= ENUMERATED { +573 sms-registration-required (0), +574 sms-registration-not-preferred (1), +575 no-preference (2), +576 ...} +577 +578 Used-RAT-Type ::= ENUMERATED { +579 utran (0), +580 geran (1), +581 gan (2), +582 i-hspa-evolution (3), +583 e-utran (4), +584 ..., +585 nb-iot (5) } +586 -- The value e-utran indicates wide-band e-utran +587 +588 EPS-Info ::= CHOICE{ +589 pdn-gw-update [0] PDN-GW-Update, +590 isr-information [1] ISR-Information } +591 +592 PDN-GW-Update ::= SEQUENCE{ +593 apn [0] APN OPTIONAL, +594 pdn-gw-Identity [1] PDN-GW-Identity OPTIONAL, +595 contextId [2] ContextId OPTIONAL, +596 extensionContainer [3] ExtensionContainer OPTIONAL, +597 ... } +598 -- The pdn-gw-update IE shall include the pdn-gw-Identity, and the apn or/and the contextID. +599 -- The HSS shall ignore the eps-info IE if it includes a pdn-gw-update IE which does not +600 -- include pdn-gw-Identity. +601 -- The pdn-gw-Identity is defined as OPTIONAL for backward compatibility reason with +602 -- outdated earlier versions of this specification. +603 +604 +605 ISR-Information ::= BIT STRING { +606 updateLocation (0), +607 cancelSGSN (1), +608 initialAttachIndicator (2)} (SIZE (3..8)) +609 -- exception handling: reception of unknown bit assignments in the +610 -- ISR-Information data type shall be discarded by the receiver +611 + +``` + +``` + +612 SGSN-Capability ::= SEQUENCE{ +613 solsaSupportIndicator NULL OPTIONAL, +614 extensionContainer [1] ExtensionContainer OPTIONAL, +615 ... , +616 superChargerSupportedInServingNetworkEntity [2] SuperChargerInfo OPTIONAL , +617 gprsEnhancementsSupportIndicator [3] NULL OPTIONAL, +618 supportedCamelPhases [4] SupportedCamelPhases OPTIONAL, +619 supportedLCS-CapabilitySets [5] SupportedLCS-CapabilitySets OPTIONAL, +620 offeredCamel4CSIs [6] OfferedCamel4CSIs OPTIONAL, +621 smsCallBarringSupportIndicator [7] NULL OPTIONAL, +622 TypesIndicator [8] SupportedRAT-Types OPTIONAL, +623 supportedFeatures [9] SupportedFeatures OPTIONAL, +624 t-adsDataRetrieval [10] NULL OPTIONAL, +625 homogeneousSupportOfIMSVoiceOverPSSessions [11] BOOLEAN OPTIONAL, +626 -- "true" indicates homogeneous support, "false" indicates homogeneous non-support +627 -- in the complete SGSN or MME area +628 cancellationTypeInitialAttach [12] NULL OPTIONAL, +629 msisdn-lessOperation-Supported [14] NULL OPTIONAL, +630 updateOfHomogeneousSupportOfIMSVoiceOverPSSessions [15] NULL OPTIONAL, +631 reset-ids-Supported [16] NULL OPTIONAL, +632 ext-SupportedFeatures [17] Ext-SupportedFeatures OPTIONAL +633 } +634 -- the supportedFeatures , t-adsDataRetrieval, +635 -- homogeneousSupportOfIMSVoiceOverPSSessions +636 -- /updateOfHomogeneousSupportOfIMSVoiceOverPSSessions and +637 -- ext-SupportedFeatures are also applied to the MME/IWF +638 + +``` + +``` + +639 SupportedFeatures ::= BIT STRING { +640 odb-all-apn (0), +641 odb-HPLMN-APN (1), +642 odb-VPLMN-APN (2), +643 odb-all-og (3), +644 odb-all-international-og (4), +645 odb-all-int-og-not-to-HPLMN-country (5), +646 odb-all-interzonal-og (6), +647 odb-all-interzonal-og-not-to-HPLMN-country (7), +648 odb-all-interzonal-og-and-internat-og-not-to-HPLMN-country (8), +649 regSub (9), +650 trace (10), +651 lcs-all-PrivExcep (11), +652 lcs-universal (12), +653 lcs-CallSessionRelated (13), +654 lcs-CallSessionUnrelated (14), +655 lcs-PLMN-operator (15), +656 lcs-ServiceType (16), +657 lcs-all-MOLR-SS (17), +658 lcs-basicSelfLocation (18), +659 lcs-autonomousSelfLocation (19), +660 lcs-transferToThirdParty (20), +661 sm-mo-pp (21), +662 barring-OutgoingCalls (22), +663 baoc (23), +664 boic (24), +665 boicExHC (25), +666 localTimeZoneRetrieval (26), +667 additionalMsisdn (27), +668 smsInMME (28), +669 smsInSGSN (29), +670 ue-Reachability-Notification (30), +671 state-Location-Information-Retrieval (31), +672 partialPurge (32), +673 gddInSGSN (33), +674 sgsnCAMELCapability (34), +675 pscf-Restoration (35), +676 dedicatedCoreNetworks (36), +677 non-IP-PDN-Type-APNs (37), +678 non-IP-PDP-Type-APNs (38), +679 nrAsSecondaryRAT (39) } (SIZE (26..40)) +680 -- for the definition and usage of the above features see the 3GPP TS 29.272 [144]. +681 -- Additional supported features are encoded in Ext-SupportedFeatures bit string. +682 + +``` + +``` + +683 +684 Ext-SupportedFeatures ::= BIT STRING { +685 unlicensedSpectrumAsSecondaryRAT (0) } (SIZE (1..40)) +686 + +``` + +``` + +687 UE-SRVCC-Capability ::= ENUMERATED { +688 ue-srvcc-not-supported (0), +689 ue-srvcc-supported (1), +690 ...} +691 +692 UpdateGprsLocationRes ::= SEQUENCE { +693 hlr-Number ISDN-AddressString, +694 extensionContainer ExtensionContainer OPTIONAL, +695 ..., +696 add-Capability NULL OPTIONAL, +697 sgsn-mmeSeparationSupported [0] NULL OPTIONAL, +698 mmeRegisteredforSMS [1] NULL OPTIONAL } +699 +700 EPLMN-List ::= SEQUENCE SIZE (1..50) OF +701 PLMN-Id +702 +703 AdjacentPLMN-List ::= SEQUENCE SIZE (1..50) OF +704 PLMN-Id +705 +706 +707 -- handover types +708 +709 ForwardAccessSignalling-Arg ::= [3] SEQUENCE { +710 an-APDU AccessNetworkSignalInfo, +711 integrityProtectionInfo [0] IntegrityProtectionInformation OPTIONAL, +712 encryptionInfo [1] EncryptionInformation OPTIONAL, +713 keyStatus [2] KeyStatus OPTIONAL, +714 allowedGSM-Algorithms [4] AllowedGSM-Algorithms OPTIONAL, +715 allowedUMTS-Algorithms [5] AllowedUMTS-Algorithms OPTIONAL, +716 radioResourceInformation [6] RadioResourceInformation OPTIONAL, +717 extensionContainer [3] ExtensionContainer OPTIONAL, +718 ..., +719 radioResourceList [7] RadioResourceList OPTIONAL, +720 bssmap-ServiceHandover [9] BSSMAP-ServiceHandover OPTIONAL, +721 ranap-ServiceHandover [8] RANAP-ServiceHandover OPTIONAL, +722 bssmap-ServiceHandoverList [10] BSSMAP-ServiceHandoverList OPTIONAL, +723 currentlyUsedCodec [11] Codec OPTIONAL, +724 iuSupportedCodecsList [12] SupportedCodecsList OPTIONAL, +725 rab-ConfigurationIndicator [13] NULL OPTIONAL, +726 iuSelectedCodec [14] Codec OPTIONAL, +727 alternativeChannelType [15] RadioResourceInformation OPTIONAL, +728 tracePropagationList [17] TracePropagationList OPTIONAL, +729 aoipSupportedCodecsListAnchor [18] AoIPCodecsList OPTIONAL, +730 aoipSelectedCodecTarget [19] AoIPCodec OPTIONAL, +731 uesbi-Iu [20] UESBI-Iu OPTIONAL, +732 imeisv [21] IMEI OPTIONAL } +733 +734 AllowedGSM-Algorithms ::= OCTET STRING (SIZE (1)) +735 -- internal structure is coded as Algorithm identifier octet from +736 -- Permitted Algorithms defined in 3GPP TS 48.008 +737 -- A node shall mark all GSM algorithms that are allowed in MSC-B +738 +739 AllowedUMTS-Algorithms ::= SEQUENCE { +740 integrityProtectionAlgorithms [0] PermittedIntegrityProtectionAlgorithms +741 OPTIONAL, +742 encryptionAlgorithms [1] PermittedEncryptionAlgorithms OPTIONAL, +743 extensionContainer [2] ExtensionContainer OPTIONAL, +744 ...} +745 +746 PermittedIntegrityProtectionAlgorithms ::= +747 OCTET STRING (SIZE (1..maxPermittedIntegrityProtectionAlgorithmsLength)) +748 -- Octets contain a complete PermittedIntegrityProtectionAlgorithms data type +749 -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme +750 -- mandated by 3GPP TS 25.413. +751 -- Padding bits are included, if needed, in the least significant bits of the +752 -- last octet of the octet string. +753 +754 +755 maxPermittedIntegrityProtectionAlgorithmsLength INTEGER ::= 9 +756 + +``` + +``` + +757 PermittedEncryptionAlgorithms := +758 OCTET STRING (SIZE (1..maxPermittedEncryptionAlgorithmsLength)) +759 -- Octets contain a complete PermittedEncryptionAlgorithms data type +760 -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme +761 -- mandated by 3GPP TS 25.413 +762 -- Padding bits are included, if needed, in the least significant bits of the +763 -- last octet of the octet string. +764 +765 +766 maxPermittedEncryptionAlgorithmsLength INTEGER := 9 +767 +768 KeyStatus := ENUMERATED { +769 old (0), +770 new (1), +771 ...} +772 -- exception handling: +773 -- received values in range 2-31 shall be treated as "old" +774 -- received values greater than 31 shall be treated as "new" +775 +776 PrepareHO-Arg := [3] SEQUENCE { +777 targetCellId [0] GlobalCellId OPTIONAL, +778 ho-NumberNotRequired NULL OPTIONAL, +779 targetRNCId [1] RNCId OPTIONAL, +780 an-APDU [2] AccessNetworkSignalInfo OPTIONAL, +781 multipleBearerRequested [3] NULL OPTIONAL, +782 imsi [4] IMSI OPTIONAL, +783 integrityProtectionInfo [5] IntegrityProtectionInformation OPTIONAL, +784 encryptionInfo [6] EncryptionInformation OPTIONAL, +785 radioResourceInformation [7] RadioResourceInformation OPTIONAL, +786 allowedGSM-Algorithms [9] AllowedGSM-Algorithms OPTIONAL, +787 allowedUMTS-Algorithms [10] AllowedUMTS-Algorithms OPTIONAL, +788 radioResourceList [11] RadioResourceList OPTIONAL, +789 extensionContainer [8] ExtensionContainer OPTIONAL, +790 ... , +791 rab-Id [12] RAB-Id OPTIONAL, +792 bssmap-ServiceHandover [13] BSSMAP-ServiceHandover OPTIONAL, +793 ranap-ServiceHandover [14] RANAP-ServiceHandover OPTIONAL, +794 bssmap-ServiceHandoverList [15] BSSMAP-ServiceHandoverList OPTIONAL, +795 asciiCallReference [20] ASCII-CallReference OPTIONAL, +796 geran-classmark [16] GERAN-Classmark OPTIONAL, +797 iuCurrentlyUsedCodec [17] Codec OPTIONAL, +798 iuSupportedCodecsList [18] SupportedCodecsList OPTIONAL, +799 rab-ConfigurationIndicator [19] NULL OPTIONAL, +800 uesbi-Iu [21] UESBI-Iu OPTIONAL, +801 imeisv [22] IMEI OPTIONAL, +802 alternativeChannelType [23] RadioResourceInformation OPTIONAL, +803 tracePropagationList [25] TracePropagationList OPTIONAL, +804 aoipSupportedCodecsListAnchor [26] AoIPCodecsList OPTIONAL, +805 regionalSubscriptionData [27] ZoneCodeList OPTIONAL, +806 lclsGlobalCallReference [28] LCLS-GlobalCallReference OPTIONAL, +807 lcls-Negotiation [29] LCLS-Negotiation OPTIONAL, +808 lcls-Configuration-Preference [30] LCLS-ConfigurationPreference OPTIONAL, +809 csg-SubscriptionDataList [31] CSG-SubscriptionDataList OPTIONAL, +810 } +811 +812 LCLS-GlobalCallReference := OCTET STRING (SIZE (13..15)) +813 -- Octets are coded as specified in 3GPP TS 29.205 [146] +814 +815 +816 LCLS-Negotiation := BIT STRING { +817 permission-indicator-not-allowed-bit (0), +818 permission-indicator-spare-bit (1)} (SIZE (2..8)) +819 --for definition and allowed combination of bits 0 and 1 see 3GPP TS 29.205 +820 -- exception handling: bits 2 to 7 shall be ignored if received and not understood +821 +822 +823 LCLS-ConfigurationPreference := BIT STRING { +824 forward-data-sending-indicator (0), +825 backward-data-sending-indicator (1), +826 forward-data-reception-indicator (2), +827 backward-data-reception-indicator (3)} (SIZE (4..8)) +828 -- exception handling: bits 4 to 7 shall be ignored if received and not understood +829 +830 +831 BSSMAP-ServiceHandoverList := SEQUENCE SIZE (1.. maxNumOfServiceHandovers) OF +832 BSSMAP-ServiceHandoverInfo +833 + +``` + +``` + +834 BSSMAP-ServiceHandoverInfo ::= SEQUENCE { +835 bssmap-ServiceHandover BSSMAP-ServiceHandover, +836 rab-Id RAB-Id, +837 -- RAB Identity is needed to relate the service handovers with the radio access bearers. +838 ...} +839 +840 maxNumOfServiceHandovers INTEGER ::= 7 +841 +842 BSSMAP-ServiceHandover ::= OCTET STRING (SIZE (1)) +843 -- Octets are coded according the Service Handover information element in +844 -- 3GPP TS 48.008. +845 +846 RANAP-ServiceHandover ::= OCTET STRING (SIZE (1)) +847 -- Octet contains a complete Service-Handover data type +848 -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme +849 -- mandated by 3GPP TS 25.413 +850 -- Padding bits are included in the least significant bits. +851 +852 +853 RadioResourceList ::= SEQUENCE SIZE (1.. maxNumOfRadioResources) OF +854 RadioResource +855 +856 RadioResource ::= SEQUENCE { +857 radioResourceInformation RadioResourceInformation, +858 rab-Id RAB-Id, +859 -- RAB Identity is needed to relate the radio resources with the radio access bearers. +860 ...} +861 +862 maxNumOfRadioResources INTEGER ::= 7 +863 +864 PrepareHO-Res ::= [3] SEQUENCE { +865 handoverNumber [0] ISDN-AddressString OPTIONAL, +866 relocationNumberList [1] RelocationNumberList OPTIONAL, +867 an-APDU [2] AccessNetworkSignalInfo OPTIONAL, +868 multicallBearerInfo [3] MulticallBearerInfo OPTIONAL, +869 multipleBearerNotSupported NULL OPTIONAL, +870 selectedUMTS-Algorithms [5] SelectedUMTS-Algorithms OPTIONAL, +871 chosenRadioResourceInformation [6] ChosenRadioResourceInformation OPTIONAL, +872 extensionContainer [4] ExtensionContainer OPTIONAL, +873 ..., +874 iuSelectedCodec [7] Codec OPTIONAL, +875 iuAvailableCodecsList [8] CodecList OPTIONAL, +876 aoipSelectedCodecTarget [9] AoIPCodec OPTIONAL, +877 aoipAvailableCodecsListMap [10] AoIPCodecsList OPTIONAL } +878 +879 SelectedUMTS-Algorithms ::= SEQUENCE { +880 integrityProtectionAlgorithm [0] ChosenIntegrityProtectionAlgorithm OPTIONAL, +881 encryptionAlgorithm [1] ChosenEncryptionAlgorithm OPTIONAL, +882 extensionContainer [2] ExtensionContainer OPTIONAL, +883 ...} +884 +885 ChosenIntegrityProtectionAlgorithm ::= OCTET STRING (SIZE (1)) +886 -- Octet contains a complete IntegrityProtectionAlgorithm data type +887 -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme +888 -- mandated by 3GPP TS 25.413 +889 -- Padding bits are included in the least significant bits. +890 +891 ChosenEncryptionAlgorithm ::= OCTET STRING (SIZE (1)) +892 -- Octet contains a complete EncryptionAlgorithm data type +893 -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme +894 -- mandated by 3GPP TS 25.413 +895 -- Padding bits are included in the least significant bits. +896 +897 ChosenRadioResourceInformation ::= SEQUENCE { +898 chosenChannelInfo [0] ChosenChannelInfo OPTIONAL, +899 chosenSpeechVersion [1] ChosenSpeechVersion OPTIONAL, +900 ...} +901 +902 ChosenChannelInfo ::= OCTET STRING (SIZE (1)) +903 -- Octets are coded according the Chosen Channel information element in 3GPP TS 48.008 +904 +905 ChosenSpeechVersion ::= OCTET STRING (SIZE (1)) +906 -- Octets are coded according the Speech Version (chosen) information element in 3GPP TS +907 -- 48.008 +908 +``` + +``` + +909 PrepareSubsequentHO-Arg ::= [3] SEQUENCE { +910 targetCellId [0] GlobalCellId OPTIONAL, +911 targetMSC-Number [1] ISDN-AddressString, +912 targetRNCId [2] RNCId OPTIONAL, +913 an-APDU [3] AccessNetworkSignalInfo OPTIONAL, +914 selectedRab-Id [4] RAB-Id OPTIONAL, +915 extensionContainer [5] ExtensionContainer OPTIONAL, +916 ..., +917 geran-classmark [6] GERAN-Classmark OPTIONAL, +918 rab-ConfigurationIndicator [7] NULL OPTIONAL } +919 +920 PrepareSubsequentHO-Res ::= [3] SEQUENCE { +921 an-APDU AccessNetworkSignalInfo, +922 extensionContainer [0] ExtensionContainer OPTIONAL, +923 ...} +924 +925 ProcessAccessSignalling-Arg ::= [3] SEQUENCE { +926 an-APDU AccessNetworkSignalInfo, +927 selectedUMTS-Algorithms [1] SelectedUMTS-Algorithms OPTIONAL, +928 selectedGSM-Algorithm [2] SelectedGSM-Algorithm OPTIONAL, +929 chosenRadioResourceInformation [3] ChosenRadioResourceInformation OPTIONAL, +930 selectedRab-Id [4] RAB-Id OPTIONAL, +931 extensionContainer [0] ExtensionContainer OPTIONAL, +932 ..., +933 iUSSelectedCodec [5] Codec OPTIONAL, +934 iuAvailableCodecsList [6] CodecList OPTIONAL, +935 aoipSelectedCodecTarget [7] AoIPCodec OPTIONAL, +936 aoipAvailableCodecsListMap [8] AoIPCodecsList OPTIONAL } +937 +938 AoIPCodecsList ::= SEQUENCE { +939 codec1 [1] AoIPCodec, +940 codec2 [2] AoIPCodec OPTIONAL, +941 codec3 [3] AoIPCodec OPTIONAL, +942 codec4 [4] AoIPCodec OPTIONAL, +943 codec5 [5] AoIPCodec OPTIONAL, +944 codec6 [6] AoIPCodec OPTIONAL, +945 codec7 [7] AoIPCodec OPTIONAL, +946 codec8 [8] AoIPCodec OPTIONAL, +947 extensionContainer [9] ExtensionContainer OPTIONAL, +948 ...} +949 -- Codecs are sent in priority order where codec1 has highest priority +950 +951 AoIPCodec ::= OCTET STRING (SIZE (1..3)) +952 +953 -- The internal structure is defined as follows: +954 -- octet 1 Coded as Speech Codec Elements in 3GPP TS 48.008 +955 -- with the exception that FI, PI, PT and TF bits shall +956 -- be set to 0 +957 -- octets 2,3 Optional; in case of AMR codec types it defines +958 -- the supported codec configurations as defined in +959 -- 3GPP TS 48.008 +960 +961 SupportedCodecsList ::= SEQUENCE { +962 utranCodecList [0] CodecList OPTIONAL, +963 geranCodecList [1] CodecList OPTIONAL, +964 extensionContainer [2] ExtensionContainer OPTIONAL, +965 ...} +966 +967 CodecList ::= SEQUENCE { +968 codec1 [1] Codec, +969 codec2 [2] Codec OPTIONAL, +970 codec3 [3] Codec OPTIONAL, +971 codec4 [4] Codec OPTIONAL, +972 codec5 [5] Codec OPTIONAL, +973 codec6 [6] Codec OPTIONAL, +974 codec7 [7] Codec OPTIONAL, +975 codec8 [8] Codec OPTIONAL, +976 extensionContainer [9] ExtensionContainer OPTIONAL, +977 ...} +978 -- Codecs are sent in priority order where codec1 has highest priority +979 + +``` + +``` + +980 Codec ::= OCTET STRING (SIZE (1..4)) +981 +982 -- The internal structure is defined as follows: +983 -- octet 1 Coded as Codec Identification code in 3GPP TS 26.103 +984 -- octets 2,3,4 Parameters for the Codec as defined in 3GPP TS +985 -- 26.103, if available, length depending on the codec +986 +987 GERAN-Classmark ::= OCTET STRING (SIZE (2..87)) +988 -- Octets are coded according the GERAN Classmark information element in 3GPP TS 48.008 +989 +990 SelectedGSM-Algorithm ::= OCTET STRING (SIZE (1)) +991 -- internal structure is coded as Algorithm identifier octet from Chosen Encryption +992 -- Algorithm defined in 3GPP TS 48.008 +993 -- A node shall mark only the selected GSM algorithm +994 +995 SendEndSignal-Arg ::= [3] SEQUENCE { +996 an-APDU AccessNetworkSignalInfo, +997 extensionContainer [0] ExtensionContainer OPTIONAL, +998 ...} +999 +1000 SendEndSignal-Res ::= SEQUENCE { +1001 extensionContainer [0] ExtensionContainer OPTIONAL, +1002 ...} +1003 +1004 RNCId ::= OCTET STRING (SIZE (7)) +1005 -- The internal structure is defined as follows: +1006 -- octet 1 bits 4321 Mobile Country Code 1st digit +1007 -- bits 8765 Mobile Country Code 2nd digit +1008 -- octet 2 bits 4321 Mobile Country Code 3rd digit +1009 -- bits 8765 Mobile Network Code 3rd digit +1010 -- or filler (1111) for 2 digit MNCs +1011 -- octet 3 bits 4321 Mobile Network Code 1st digit +1012 -- bits 8765 Mobile Network Code 2nd digit +1013 -- octets 4 and 5 Location Area Code according to 3GPP TS 24.008 +1014 -- octets 6 and 7 RNC Id or Extended RNC Id value according to +1015 -- 3GPP TS 25.413 +1016 +1017 RelocationNumberList ::= SEQUENCE SIZE (1..maxNumOfRelocationNumber) OF +1018 RelocationNumber +1019 +1020 MulticallBearerInfo ::= INTEGER (1..maxNumOfRelocationNumber) +1021 +1022 RelocationNumber ::= SEQUENCE { +1023 handoverNumber ISDN-AddressString, +1024 rab-Id RAB-Id, +1025 -- RAB Identity is needed to relate the calls with the radio access bearers. +1026 ...} +1027 +1028 RAB-Id ::= INTEGER (1..maxNrOfRABs) +1029 +1030 maxNrOfRABs INTEGER ::= 255 +1031 +1032 maxNumOfRelocationNumber INTEGER ::= 7 +1033 +1034 RadioResourceInformation ::= OCTET STRING (SIZE (3..13)) +1035 -- Octets are coded according the Channel Type information element in 3GPP TS 48.008 +1036 +1037 IntegrityProtectionInformation ::= OCTET STRING (SIZE (18..maxNumOfIntegrityInfo)) +1038 -- Octets contain a complete IntegrityProtectionInformation data type +1039 -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme +1040 -- mandated by 3GPP TS 25.413 +1041 -- Padding bits are included, if needed, in the least significant bits of the +1042 -- last octet of the octet string. +1043 +1044 maxNumOfIntegrityInfo INTEGER ::= 100 +1045 +1046 EncryptionInformation ::= OCTET STRING (SIZE (18..maxNumOfEncryptionInfo)) +1047 -- Octets contain a complete EncryptionInformation data type +1048 -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme +1049 -- mandated by 3GPP TS 25.413 +1050 -- Padding bits are included, if needed, in the least significant bits of the +1051 -- last octet of the octet string. +1052 +1053 maxNumOfEncryptionInfo INTEGER ::= 100 +1054 + +``` + +1055 -- authentication management types + +1056 +1057 SendAuthenticationInfoArg ::= SEQUENCE { +1058 imsi [0] IMSI, +1059 numberOfRequestedVectors NumberOfRequestedVectors, +1060 segmentationProhibited NULL OPTIONAL, +1061 immediateResponsePreferred [1] NULL OPTIONAL, +1062 re-synchronisationInfo Re-synchronisationInfo OPTIONAL, +1063 extensionContainer [2] ExtensionContainer OPTIONAL, +1064 ..., +1065 requestingNodeType [3] RequestingNodeType OPTIONAL, +1066 requestingPLMN-Id [4] PLMN-Id OPTIONAL, +1067 numberOfRequestedAdditional-Vectors [5] NumberOfRequestedVectors OPTIONAL, +1068 additionalVectorsAreForEPS [6] NULL OPTIONAL, +1069 ueUsageTypeRequestIndication [7] NULL OPTIONAL } + +1070 +1071 +1072 NumberOfRequestedVectors ::= INTEGER (1..5) + +1073 +1074 Re-synchronisationInfo ::= SEQUENCE { +1075 rand RAND, +1076 auts AUTS, +1077 ... } + +1078 +1079 SendAuthenticationInfoRes ::= [3] SEQUENCE { +1080 authenticationSetList AuthenticationSetList OPTIONAL, +1081 extensionContainer ExtensionContainer OPTIONAL, +1082 ..., +1083 eps-AuthenticationSetList [2] EPS-AuthenticationSetList OPTIONAL, +1084 ueUsageType [3] UE-UsageType OPTIONAL } + +1085 +1086 EPS-AuthenticationSetList ::= SEQUENCE SIZE (1..5) OF +1087 EPC-AV + +1088 +1089 UE-UsageType ::= OCTET STRING (SIZE (4)) +1090 -- octets are coded as defined in 3GPP TS 29.272 [144] + +1091 +1092 EPC-AV ::= SEQUENCE { +1093 rand RAND, +1094 xres XRES, +1095 autn AUTN, +1096 kasme KASME, +1097 extensionContainer ExtensionContainer OPTIONAL, +1098 ... } + +1099 +1100 KASME ::= OCTET STRING (SIZE (32)) + +1101 +1102 RequestingNodeType ::= ENUMERATED { +1103 vlr (0), +1104 sgsn (1), +1105 ..., +1106 s-cscf (2), +1107 bsf (3), +1108 gan-aaa-server (4), +1109 wlan-aaa-server (5), +1110 mme (16), +1111 mme-sgsn (17) +1112 } +1113 -- the values 2, 3, 4 and 5 shall not be used on the MAP-D or Gr interfaces +1114 -- exception handling: +1115 -- received values in the range (6-15) shall be treated as "vlr" +1116 -- received values greater than 17 shall be treated as "sgsn" + +1117 +1118 -- equipment management types + +1119 +1120 CheckIMEI-Arg ::= SEQUENCE { +1121 imei IMEI, +1122 requestedEquipmentInfo RequestedEquipmentInfo, +1123 extensionContainer ExtensionContainer OPTIONAL, +1124 ... } + +1125 +1126 CheckIMEI-Res ::= SEQUENCE { +1127 equipmentStatus EquipmentStatus OPTIONAL, +1128 bmuef UESBI-Iu OPTIONAL, +1129 extensionContainer [0] ExtensionContainer OPTIONAL, +1130 ... } + +1131 + +``` + +1132 RequestedEquipmentInfo ::= BIT STRING { +1133 equipmentStatus (0), +1134 bmuef (1)} (SIZE (2..8)) +1135 -- exception handling: reception of unknown bit assignments in the +1136 -- RequestedEquipmentInfo data type shall be discarded by the receiver +1137 +1138 UESBI-Iu ::= SEQUENCE { +1139 uesbi-IuA [0] UESBI-IuA OPTIONAL, +1140 uesbi-IuB [1] UESBI-IuB OPTIONAL, +1141 ...} +1142 +1143 UESBI-IuA ::= BIT STRING (SIZE(1..128)) +1144 -- See 3GPP TS 25.413 +1145 +1146 UESBI-IuB ::= BIT STRING (SIZE(1..128)) +1147 -- See 3GPP TS 25.413 +1148 +1149 EquipmentStatus ::= ENUMERATED { +1150 permittedListed (0), +1151 prohibitedListed (1), +1152 trackingListed (2)} +1153 +1154 -- subscriber management types +1155 +1156 InsertSubscriberDataArg ::= SEQUENCE { +1157 imsi [0] IMSI OPTIONAL, +1158 COMPONENTS OF SubscriberData, +1159 extensionContainer [14] ExtensionContainer OPTIONAL, +1160 ... , +1161 naea-PreferredCI [15] NAEA-PreferredCI OPTIONAL, +1162 -- naea-PreferredCI is included at the discretion of the HLR operator. +1163 gprsSubscriptionData [16] GPRSSubscriptionData OPTIONAL, +1164 roamingRestrictedInSgsnDueToUnsupportedFeature [23] NULL +1165 OPTIONAL, +1166 networkAccessMode [24] NetworkAccessMode OPTIONAL, +1167 lsaInformation [25] LSAInformation OPTIONAL, +1168 lmu-Indicator [21] NULL OPTIONAL, +1169 lcsInformation [22] LCSInformation OPTIONAL, +1170 istAlertTimer [26] IST-AlertTimerValue OPTIONAL, +1171 superChargerSupportedInHLR [27] AgeIndicator OPTIONAL, +1172 mc-SS-Info [28] MC-SS-Info OPTIONAL, +1173 cs-AllocationRetentionPriority [29] CS-AllocationRetentionPriority OPTIONAL, +1174 sgsn-CAMEL-SubscriptionInfo [17] SGSN-CAMEL-SubscriptionInfo OPTIONAL, +1175 chargingCharacteristics [18] ChargingCharacteristics OPTIONAL, +1176 accessRestrictionData [19] AccessRestrictionData OPTIONAL, +1177 ics-Indicator [20] BOOLEAN OPTIONAL, +1178 eps-SubscriptionData [31] EPS-SubscriptionData OPTIONAL, +1179 csg-SubscriptionDataList [32] CSG-SubscriptionDataList OPTIONAL, +1180 ue-ReachabilityRequestIndicator [33] NULL OPTIONAL, +1181 sgsn-Number [34] ISDN-AddressString OPTIONAL, +1182 mme-Name [35] DiameterIdentity OPTIONAL, +1183 subscribedPeriodicRAUTAutimer [36] SubscribedPeriodicRAUTAutimer OPTIONAL, +1184 vplmnLIPAAllowed [37] NULL OPTIONAL, +1185 mdtUserConsent [38] BOOLEAN OPTIONAL, +1186 subscribedPeriodicLAUTautimer [39] SubscribedPeriodicLAUTautimer OPTIONAL, +1187 vplmn-Csg-SubscriptionDataList [40] VPLMN-CSG-SubscriptionDataList OPTIONAL, +1188 additionalMSISDN [41] ISDN-AddressString OPTIONAL, +1189 psAndSMS-OnlyServiceProvision [42] NULL OPTIONAL, +1190 smsInSGSNAllowed [43] NULL OPTIONAL, +1191 cs-to-ps-SRVCC-Allowed-Indicator [44] NULL OPTIONAL, +1192 pscf-Restoration-Request [45] NULL OPTIONAL, +1193 adjacentAccessRestrictionDataList [46] AdjacentAccessRestrictionDataList OPTIONAL, +1194 imsi-Group-Id-List [47] IMSI-GroupIdList OPTIONAL, +1195 ueUsageType [48] UE-UsageType OPTIONAL, +1196 userPlaneIntegrityProtectionIndicator [49] NULL OPTIONAL, +1197 dl-Buffering-Suggested-Packet-Count [50] DL-Buffering-Suggested-Packet-Count OPTIONAL, +1198 reset-Id-List [51] Reset-Id-List OPTIONAL, +1199 edrx-Cycle-Length-List [52] EDRX-Cycle-Length-List OPTIONAL, +1200 ext-AccessRestrictionData [53] Ext-AccessRestrictionData OPTIONAL, +1201 iab-Operation-Allowed-Indicator [54] NULL OPTIONAL } +1202 -- If the Network Access Mode parameter is sent, it shall be present only in +1203 -- the first sequence if segmentation is used +1204 +1205 EDRX-Cycle-Length-List ::= SEQUENCE SIZE (1..8) OF +1206 EDRX-Cycle-Length +1207 + +``` + +``` + +1208 EDRX-Cycle-Length ::= SEQUENCE { +1209 rat-Type [0] Used-RAT-Type, +1210 eDRX-Cycle-Length-Value [1] EDRX-Cycle-Length-Value, +1211 ... } +1212 -- The eDRX-Cycle-Length contains the subscribed eDRX-Cycle-Length applicable to a +1213 -- a specific RAT Type. +1214 +1215 +1216 EDRX-Cycle-Length-Value ::= OCTET STRING (SIZE (1)) +1217 -- The EDRX-Cycle-Length-Value shall be encoded as specified in clause 7.3.216 of +1218 -- 3GPP TS 29.272 [144]. +1219 +1220 +1221 Reset-Id-List ::= SEQUENCE SIZE (1..50) OF +1222 Reset-Id +1223 +1224 Reset-Id ::= OCTET STRING (SIZE (1..4)) +1225 -- Reset-Ids shall be unique within the HPLMN. +1226 +1227 +1228 DL-Buffering-Suggested-Packet-Count ::= INTEGER (-1..2147483647) +1229 -- values are defined in 3GPP TS 29.272 [144] +1230 +1231 +1232 Group-Service-ID ::= INTEGER (0..4294967295) +1233 -- values are defined in 3GPP TS 29.272 [144] +1234 +1235 +1236 Local-GroupID ::= OCTET STRING (SIZE (1..10)) +1237 -- Refers to Local group ID defined by an operator identified by the PLMN-ID. +1238 -- for details see 3GPP TS 29.272 [144] +1239 +1240 IMSI-GroupIdList ::= SEQUENCE SIZE (1..50) OF +1241 IMSI-GroupId +1242 +1243 IMSI-GroupId ::= SEQUENCE { +1244 group-Service-Id [0] Group-Service-ID, +1245 plmnId [1] PLMN-Id, +1246 local-Group-ID [2] Local-GroupID, +1247 ... } +1248 +1249 SubscribedPeriodicRAUTAtimer ::= INTEGER (0..4294967295) +1250 -- This parameter carries the subscribed periodic TAU/RAU timer value in seconds as +1251 -- specified in 3GPP TS 24.008 [35]. +1252 +1253 SubscribedPeriodicLAUtimer ::= INTEGER (0..4294967295) +1254 -- This parameter carries the subscribed periodic LAU timer value in seconds as +1255 -- specified in 3GPP TS 24.008 [35]. +1256 +1257 CSG-SubscriptionDataList ::= SEQUENCE SIZE (1..50) OF +1258 CSG-SubscriptionData +1259 +1260 CSG-SubscriptionData ::= SEQUENCE { +1261 csg-Id CSG-Id, +1262 expirationDate Time OPTIONAL, +1263 extensionContainer ExtensionContainer OPTIONAL, +1264 ..., +1265 lipa-AllowedAPNList [0] LIPA-AllowedAPNList OPTIONAL, +1266 plmn-Id [1] PLMN-Id OPTIONAL +1267 } +1268 +1269 VPLMN-CSG-SubscriptionDataList ::= SEQUENCE SIZE (1..50) OF +1270 CSG-SubscriptionData +1271 +1272 CSG-Id ::= BIT STRING (SIZE (27)) +1273 -- coded according to 3GPP TS 23.003 [17]. +1274 +1275 LIPA-AllowedAPNList ::= SEQUENCE SIZE (1..maxNumOfLIPAAllowedAPN) OF +1276 APN +1277 +1278 maxNumOfLIPAAllowedAPN INTEGER ::= 50 +1279 +1280 + +``` + +``` + +1281 EPS-SubscriptionData ::= SEQUENCE { +1282 apn-oi-Replacement [0] APN-OI-Replacement OPTIONAL, +1283 -- this apn-oi-Replacement refers to the UE level apn-oi-Replacement. +1284 rfsp-id [2] RFSP-ID OPTIONAL, +1285 ambr [3] AMBR OPTIONAL, +1286 apn-ConfigurationProfile [4] APN-ConfigurationProfile OPTIONAL, +1287 stn-sr [6] ISDN-AddressString OPTIONAL, +1288 extensionContainer [5] ExtensionContainer OPTIONAL, +1289 ..., +1290 mps-CSPriority [7] NULL OPTIONAL, +1291 mps-EPSPriority [8] NULL OPTIONAL, +1292 subscribed-vsrvcc [9] NULL OPTIONAL } +1293 -- mps-CSPriority by its presence indicates that the UE is subscribed to the eMLPP in +1294 -- the CS domain, referring to the 3GPP TS 29.272 [144] for details. +1295 -- mps-EPSPriority by its presence indicates that the UE is subscribed to the MPS in +1296 -- the EPS domain, referring to the 3GPP TS 29.272 [144] for details. +1297 -- +1298 -- subscribed-vsrvcc by its presence indicates that the UE is subscribed to the vSRVCC in +1299 -- the EPS domain, referring to the 3GPP TS 29.272 [144] for details. +1300 +1301 APN-OI-Replacement ::= OCTET STRING (SIZE (9..100)) +1302 -- Octets are coded as APN Operator Identifier according to TS 3GPP TS 23.003 [17] +1303 +1304 RFSP-ID ::= INTEGER (1..256) +1305 +1306 APN-ConfigurationProfile ::= SEQUENCE { +1307 defaultContext ContextId, +1308 completeDataListIncluded NULL OPTIONAL, +1309 -- If segmentation is used, completeDataListIncluded may only be present in the +1310 -- first segment of APN-ConfigurationProfile. +1311 epsDataList [1] EPS-DataList, +1312 extensionContainer [2] ExtensionContainer OPTIONAL, +1313 ... , +1314 additionalDefaultContext [3] ContextId OPTIONAL +1315 -- for details see the 3GPP TS 29.272 [144]. +1316 } +1317 +1318 EPS-DataList ::= SEQUENCE SIZE (1..maxNumOfAPN-Configurations) OF +1319 APN-Configuration +1320 +1321 +1322 maxNumOfAPN-Configurations INTEGER ::= 50 +1323 +1324 +1325 APN-Configuration ::= SEQUENCE { +1326 contextId [0] ContextId, +1327 pdn-Type [1] PDN-Type, +1328 servedPartyIP-IPv4-Address [2] PDP-Address OPTIONAL, +1329 apn [3] APN, +1330 eps-qos-Subscribed [4] EPS-QoS-Subscribed, +1331 pdn-gw-Identity [5] PDN-GW-Identity OPTIONAL, +1332 pdn-gw-AllocationType [6] PDN-GW-AllocationType OPTIONAL, +1333 vplmnAddressAllowed [7] NULL OPTIONAL, +1334 chargingCharacteristics [8] ChargingCharacteristics OPTIONAL, +1335 ambr [9] AMBR OPTIONAL, +1336 specificAPNInfoList [10] SpecificAPNInfoList OPTIONAL, +1337 extensionContainer [11] ExtensionContainer OPTIONAL, +1338 servedPartyIP-IPv6-Address [12] PDP-Address OPTIONAL, +1339 ..., +1340 apn-oi-Replacement [13] APN-OI-Replacement OPTIONAL, +1341 -- this apn-oi-Replacement refers to the APN level apn-oi-Replacement. +1342 sipto-Permission [14] SIPTO-Permission OPTIONAL, +1343 lipa-Permission [15] LIPA-Permission OPTIONAL, +1344 restoration-Priority [16] Restoration-Priority OPTIONAL, +1345 sipto-local-network-Permission [17] SIPTO-Local-Network-Permission OPTIONAL, +1346 wlan-offloadability [18] WLAN-Offloadability OPTIONAL, +1347 non-IP-PDN-Type-Indicator [19] NULL OPTIONAL, +1348 nIDD-Mechanism [20] NIDD-Mechanism OPTIONAL, +1349 sCEF-ID [21] FQDN OPTIONAL, +1350 pdn-ConnectionContinuity [22] PDN-ConnectionContinuity OPTIONAL +1351 -- absence of pdn-ConnectionContinuity indicates that the handling is left to +1352 -- local VPLMN policy +1353 } +1354 + +``` + +``` + +1355 PDN-ConnectionContinuity ::= ENUMERATED { +1356 maintainPDN-Connection (0), +1357 disconnectPDN-ConnectionWithReactivationRequest (1), +1358 disconnectPDN-ConnectionWithoutReactivationRequest (2) +1359 } +1360 +1361 NIDD-Mechanism ::= ENUMERATED { +1362 sGi-based-data-delivery (0), +1363 sCEF-based-data-delivery (1) +1364 -- The default value, when this information element is not present, is +1365 -- sGi-based-data-delivery (0) +1366 } +1367 +1368 PDN-Type ::= OCTET STRING (SIZE (1)) +1369 -- Octet is coded as follows: +1370 -- Bits +1371 -- 3 2 1 +1372 -- 0 0 1 IPv4 +1373 -- 0 1 0 IPv6 +1374 -- 0 1 1 IPv4v6 +1375 -- 1 0 0 IPv4 or IPv6 +1376 -- Bits 8-4 shall be coded as zero. +1377 -- for details see 3GPP TS 29.272 [144] +1378 +1379 EPS-QoS-Subscribed ::= SEQUENCE { +1380 qos-Class-Identifier [0] QoS-Class-Identifier, +1381 allocation-Retention-Priority [1] Allocation-Retention-Priority, +1382 extensionContainer [2] ExtensionContainer OPTIONAL, +1383 ... } +1384 +1385 AMBR ::= SEQUENCE { +1386 max-RequestedBandwidth-UL [0] Bandwidth, +1387 max-RequestedBandwidth-DL [1] Bandwidth, +1388 extensionContainer [2] ExtensionContainer OPTIONAL, +1389 ..., +1390 extended-Max-RequestedBandwidth-UL [3] BandwidthExt OPTIONAL, +1391 extended-Max-RequestedBandwidth-DL [4] BandwidthExt OPTIONAL +1392 -- extended-Max-RequestedBandwidth-UL/DL shall be populated according to the +1393 -- description of the corresponding parameters in 3GPP TS 29.272 [144] +1394 } +1395 +1396 +1397 SpecificAPNInfoList ::= SEQUENCE SIZE (1..maxNumOfSpecificAPNInfos) OF +1398 SpecificAPNInfo +1399 +1400 maxNumOfSpecificAPNInfos INTEGER ::= 50 +1401 +1402 SpecificAPNInfo ::= SEQUENCE { +1403 apn [0] APN, +1404 pdn-gw-Identity [1] PDN-GW-Identity, +1405 extensionContainer [2] ExtensionContainer OPTIONAL, +1406 ... } +1407 +1408 Bandwidth ::= INTEGER +1409 -- bits per second +1410 +1411 BandwidthExt ::= INTEGER +1412 -- kilobits per second +1413 +1414 QoS-Class-Identifier ::= INTEGER (1..9) +1415 -- values are defined in 3GPP TS 29.212 +1416 +1417 +1418 +1419 Allocation-Retention-Priority ::= SEQUENCE { +1420 priority-level [0] INTEGER, +1421 pre-emption-capability [1] BOOLEAN OPTIONAL, +1422 pre-emption-vulnerability [2] BOOLEAN OPTIONAL, +1423 extensionContainer [3] ExtensionContainer OPTIONAL, +1424 ... } +1425 + +``` + +``` + +1426 PDN-GW-Identity ::= SEQUENCE { +1427 pdn-gw-ipv4-Address [0] PDP-Address OPTIONAL, +1428 pdn-gw-ipv6-Address [1] PDP-Address OPTIONAL, +1429 pdn-gw-name [2] FQDN OPTIONAL, +1430 extensionContainer [3] ExtensionContainer OPTIONAL, +1431 ... } +1432 +1433 FQDN ::= OCTET STRING (SIZE (9..255)) +1434 +1435 +1436 PDN-GW-AllocationType ::= ENUMERATED { +1437 static (0), +1438 dynamic (1) } +1439 +1440 +1441 WLAN-Offloadability ::= SEQUENCE { +1442 wlan-offloadability-EUTRAN [0] WLAN-Offloadability-Indication OPTIONAL, +1443 wlan-offloadability-UTRAN [1] WLAN-Offloadability-Indication OPTIONAL, +1444 extensionContainer [2] ExtensionContainer OPTIONAL, +1445 ... } +1446 +1447 WLAN-Offloadability-Indication ::= ENUMERATED { +1448 notAllowed (0), +1449 allowed (1) } +1450 +1451 +1452 +1453 AccessRestrictionData ::= BIT STRING { +1454 utranNotAllowed (0), +1455 geranNotAllowed (1), +1456 ganNotAllowed (2), +1457 i-hspa-evolutionNotAllowed (3), +1458 wb-e-utranNotAllowed (4), +1459 ho-toNon3GPP-AccessNotAllowed (5), +1460 nb-iotNotAllowed (6), +1461 enhancedCoverageNotAllowed (7) } (SIZE (2..8)) +1462 -- exception handling: +1463 -- The VLR shall ignore the access restriction data related to an access type not +1464 -- supported by the node. +1465 -- The handling of the access restriction data by the SGSN is described in clause +1466 -- 5.3.19 of TS 23.060, in clause 7.5.3 of TS 29.060 and clause 7.3.6 of TS 29.274. +1467 -- Additional access restrictions are encoded in Ext-AccessRestrictionData bit string. +1468 +1469 +1470 Ext-AccessRestrictionData ::= BIT STRING { +1471 nrAsSecondaryRATNotAllowed (0), +1472 unlicensedSpectrumAsSecondaryRATNotAllowed (1) } (SIZE (1..32)) +1473 +1474 +1475 AdjacentAccessRestrictionDataList ::= SEQUENCE SIZE (1..50) OF +1476 AdjacentAccessRestrictionData +1477 +1478 +1479 AdjacentAccessRestrictionData ::= SEQUENCE { +1480 plmnId [0] PLMN-Id, +1481 accessRestrictionData [1] AccessRestrictionData, +1482 ... , +1483 ext-AccessRestrictionData [2] Ext-AccessRestrictionData OPTIONAL } +1484 +1485 +1486 CS-AllocationRetentionPriority ::= OCTET STRING (SIZE (1)) +1487 -- This data type encodes each priority level defined in 3GPP TS 23.107 [154] as the +1488 -- binary value of the priority level. +1489 +1490 +1491 IST-AlertTimerValue ::= INTEGER (15..255) +1492 +1493 +1494 LCSInformation ::= SEQUENCE { +1495 gmlc-List [0] GMLC-List OPTIONAL, +1496 lcs-PrivacyExceptionList [1] LCS-PrivacyExceptionList OPTIONAL, +1497 molr-List [2] MOLR-List OPTIONAL, +1498 ..., +1499 add-lcs-PrivacyExceptionList [3] LCS-PrivacyExceptionList OPTIONAL } +1500 -- add-lcs-PrivacyExceptionList may be sent only if lcs-PrivacyExceptionList is +1501 -- present and contains four instances of LCS-PrivacyClass. If the mentioned condition +1502 -- is not satisfied the receiving node shall discard add-lcs-PrivacyExceptionList. +1503 -- If an LCS-PrivacyClass is received both in lcs-PrivacyExceptionList and in +1504 -- add-lcs-PrivacyExceptionList with the same SS-Code, then the error unexpected +1505 -- data value shall be returned. + +``` + +``` + +1502 GMLC-List ::= SEQUENCE SIZE (1..maxNumOfGMLC) OF +1503 ISDN-AddressString +1504 -- if segmentation is used, the complete GMLC-List shall be sent in one segment +1505 +1506 maxNumOfGMLC INTEGER ::= 5 +1507 +1508 NetworkAccessMode ::= ENUMERATED { +1509 packetAndCircuit (0), +1510 onlyCircuit (1), +1511 onlyPacket (2), +1512 ...} +1513 -- if unknown values are received in NetworkAccessMode +1514 -- they shall be discarded. +1515 +1516 GPRSDatalist ::= SEQUENCE SIZE (1..maxNumOfPDP-Contexts) OF +1517 PDP-Context +1518 +1519 maxNumOfPDP-Contexts INTEGER ::= 50 +1520 +1521 PDP-Context ::= SEQUENCE { +1522 pdp-ContextId ContextId, +1523 pdp-Type [16] PDP-Type, +1524 pdp-Address [17] PDP-Address OPTIONAL, +1525 qos-Subscribed [18] QoS-Subscribed, +1526 vplmnAddressAllowed [19] NULL OPTIONAL, +1527 apn [20] APN, +1528 extensionContainer [21] ExtensionContainer OPTIONAL, +1529 ... , +1530 ext-QoS-Subscribed [0] Ext-QoS-Subscribed OPTIONAL, +1531 pdp-ChargingCharacteristics [1] ChargingCharacteristics OPTIONAL, +1532 ext2-QoS-Subscribed [2] Ext2-QoS-Subscribed OPTIONAL, +1533 -- ext2-QoS-Subscribed may be present only if ext-QoS-Subscribed is present. +1534 ext3-QoS-Subscribed [3] Ext3-QoS-Subscribed OPTIONAL, +1535 -- ext3-QoS-Subscribed may be present only if ext2-QoS-Subscribed is present. +1536 ext4-QoS-Subscribed [4] Ext4-QoS-Subscribed OPTIONAL, +1537 -- ext4-QoS-Subscribed may be present only if ext3-QoS-Subscribed is present. +1538 apn-oi-Replacement [5] APN-OI-Replacement OPTIONAL, +1539 -- this apn-oi-Replacement refers to the APN level apn-oi-Replacement and has +1540 -- higher priority than UE level apn-oi-Replacement. +1541 ext-pdp-Type [6] Ext-PDP-Type OPTIONAL, +1542 -- contains the value IPv4v6 defined in 3GPP TS 29.060 [105], if the PDP can be +1543 -- accessed by dual-stack UEs +1544 ext-pdp-Address [7] PDP-Address OPTIONAL, +1545 -- contains an additional IP address in case of dual-stack static IP address assignment +1546 -- for the UE. +1547 -- it may contain an IPv4 or an IPv6 address/prefix, and it may be present +1548 -- only if pdp-Address is present; if both are present, each parameter shall +1549 -- contain a different type of address (IPv4 or IPv6). +1550 ambr [10] AMBR OPTIONAL, +1551 -- this ambr contains the AMBR associated to the APN included in the +1552 -- PDP-Context (APN-AMBR). +1553 sipto-Permission [8] SIPTO-Permission OPTIONAL, +1554 lipa-Permission [9] LIPA-Permission OPTIONAL, +1555 restoration-Priority [11] Restoration-Priority OPTIONAL, +1556 sipto-local-network-Permission [12] SIPTO-Local-Network-Permission OPTIONAL, +1557 nIDD-Mechanism [13] NIDD-Mechanism OPTIONAL, +1558 sCEF-ID [14] FQDN OPTIONAL +1559 } +1560 +1561 Restoration-Priority ::= OCTET STRING (SIZE (1)) +1562 -- Octet 1: +1563 -- Restoration Priority. This octet encodes the Restoration Priority, +1564 -- as the binary value of the Restoration-Priority described in 3GPP TS 29.272 [144]. +1565 +1566 SIPTO-Permission ::= ENUMERATED { +1567 siptoAboveRanAllowed (0), +1568 siptoAboveRanNotAllowed (1) +1569 } +1570 +1571 SIPTO-Local-Network-Permission ::= ENUMERATED { +1572 siptoAtLocalNetworkAllowed (0), +1573 siptoAtLocalNetworkNotAllowed (1) +1574 } +1575 + +``` + +``` + +1576 LIPA-Permission ::= ENUMERATED { +1577 lipaProhibited (0), +1578 lipaOnly (1), +1579 lipaConditional (2) +1580 } +1581 +1582 ContextId ::= INTEGER (1..maxNumOfPDP-Contexts) +1583 +1584 GPRSSubscriptionData ::= SEQUENCE { +1585 completeDataListIncluded NULL OPTIONAL, +1586 -- If segmentation is used, completeDataListIncluded may only be present in the +1587 -- first segment of GPRSSubscriptionData. +1588 gprsDataList [1] GPRSDataList, +1589 extensionContainer [2] ExtensionContainer OPTIONAL, +1590 ..., +1591 apn-oi-Replacement [3] APN-OI-Replacement OPTIONAL +1592 -- this apn-oi-Replacement refers to the UE level apn-oi-Replacement. +1593 } +1594 +1595 SGSN-CAMEL-SubscriptionInfo ::= SEQUENCE { +1596 gprs-CSI [0] GPRS-CSI OPTIONAL, +1597 mo-sms-CSI [1] SMS-CSI OPTIONAL, +1598 extensionContainer [2] ExtensionContainer OPTIONAL, +1599 ..., +1600 mt-sms-CSI [3] SMS-CSI OPTIONAL, +1601 mt-smsCAMELTDP-CriteriaList [4] MT-smsCAMELTDP-CriteriaList OPTIONAL, +1602 mg-csi [5] MG-CSI OPTIONAL +1603 } +1604 +1605 GPRS-CSI ::= SEQUENCE { +1606 gprs-CamelTDPDataList [0] GPRS-CamelTDPDataList OPTIONAL, +1607 camelCapabilityHandling [1] CamelCapabilityHandling OPTIONAL, +1608 extensionContainer [2] ExtensionContainer OPTIONAL, +1609 notificationToCSE [3] NULL OPTIONAL, +1610 csi-Active [4] NULL OPTIONAL, +1611 ...} +1612 -- notificationToCSE and csi-Active shall not be present when GPRS-CSI is sent to SGSN. +1613 -- They may only be included in ATSI/ATM ack/NSDC message. +1614 -- GPRS-CamelTDPData and camelCapabilityHandling shall be present in +1615 -- the GPRS-CSI sequence. +1616 -- If GPRS-CSI is segmented, gprs-CamelTDPDataList and camelCapabilityHandling shall be +1617 -- present in the first segment +1618 +1619 GPRS-CamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF +1620 GPRS-CamelTDPData +1621 -- GPRS-CamelTDPDataList shall not contain more than one instance of +1622 -- GPRS-CamelTDPData containing the same value for gprs-TriggerDetectionPoint. +1623 +1624 GPRS-CamelTDPData ::= SEQUENCE { +1625 gprs-TriggerDetectionPoint [0] GPRS-TriggerDetectionPoint, +1626 serviceKey [1] ServiceKey, +1627 gsmSCF-Address [2] ISDN-AddressString, +1628 defaultSessionHandling [3] DefaultGPRS-Handling, +1629 extensionContainer [4] ExtensionContainer OPTIONAL, +1630 ... +1631 } +1632 +1633 DefaultGPRS-Handling ::= ENUMERATED { +1634 continueTransaction (0) , +1635 releaseTransaction (1) , +1636 ...} +1637 -- exception handling: +1638 -- reception of values in range 2-31 shall be treated as "continueTransaction" +1639 -- reception of values greater than 31 shall be treated as "releaseTransaction" +1640 +1641 GPRS-TriggerDetectionPoint ::= ENUMERATED { +1642 attach (1), +1643 attachChangeOfPosition (2), +1644 pdp-ContextEstablishment (11), +1645 pdp-ContextEstablishmentAcknowledgement (12), +1646 pdp-ContextChangeOfPosition (14), +1647 ... } +1648 -- exception handling: +1649 -- For GPRS-CamelTDPData sequences containing this parameter with any +1650 -- other value than the ones listed the receiver shall ignore the whole +1651 -- GPRS-CamelTDPData sequence. +1652 + +``` + +``` + +1653 APN ::= OCTET STRING (SIZE (2..63)) +1654 -- Octets are coded according to TS 3GPP TS 23.003 [17] +1655 +1656 PDP-Type ::= OCTET STRING (SIZE (2)) +1657 -- Octets are coded according to TS 3GPP TS 29.060 [105] +1658 -- Only the values PPP, IPv4, IPv6 and Non-IP are allowed for this parameter. +1659 +1660 Ext-PDP-Type ::= OCTET STRING (SIZE (2)) +1661 -- Octets are coded, similarly to PDP-Type, according to TS 3GPP TS 29.060 [105]. +1662 -- Only the value IPv4v6 is allowed for this parameter. +1663 +1664 PDP-Address ::= OCTET STRING (SIZE (1..16)) +1665 -- Octets are coded according to TS 3GPP TS 29.060 [105] +1666 +1667 -- The possible size values are: +1668 -- 1-7 octets X.25 address type +1669 -- 4 octets IPv4 address type +1670 -- 16 octets IPv6 address type +1671 +1672 QoS-Subscribed ::= OCTET STRING (SIZE (3)) +1673 -- Octets are coded according to TS 3GPP TS 24.008 [35] Quality of Service Octets +1674 -- 3-5. +1675 +1676 Ext-QoS-Subscribed ::= OCTET STRING (SIZE (1..9)) +1677 -- OCTET 1: +1678 -- Allocation/Retention Priority (This octet encodes each priority level defined in +1679 -- 3GPP TS 23.107 [154] as the binary value of the priority level, declaration in +1680 -- 3GPP TS 29.060 [105]) +1681 -- Octets 2-9 are coded according to 3GPP TS 24.008 [35] Quality of Service Octets +1682 -- 6-13. +1683 +1684 Ext2-QoS-Subscribed ::= OCTET STRING (SIZE (1..3)) +1685 -- Octets 1-3 are coded according to 3GPP TS 24.008 [35] Quality of Service Octets 14-16. +1686 -- If Quality of Service information is structured with 14 octet length, then +1687 -- Octet 1 is coded according to 3GPP TS 24.008 [35] Quality of Service Octet 14. +1688 +1689 Ext3-QoS-Subscribed ::= OCTET STRING (SIZE (1..2)) +1690 -- Octets 1-2 are coded according to 3GPP TS 24.008 [35] Quality of Service Octets 17-18. +1691 +1692 Ext4-QoS-Subscribed ::= OCTET STRING (SIZE (1)) +1693 -- Octet 1: +1694 -- Evolved Allocation/Retention Priority. This octet encodes the Priority Level (PL), +1695 -- the Preemption Capability (PCI) and Preemption Vulnerability (PVI) values, as +1696 -- described in 3GPP TS 29.060 [105]. +1697 +1698 ChargingCharacteristics ::= OCTET STRING (SIZE (2)) +1699 -- Octets are coded according to 3GPP TS 32.215. +1700 +1701 LSAPOnlyAccessIndicator ::= ENUMERATED { +1702 accessOutsideLSAsAllowed (0), +1703 accessOutsideLSAsRestricted (1) } +1704 +1705 LSADatalist ::= SEQUENCE SIZE (1..maxNumOfLSAs) OF +1706 LSADatA +1707 +1708 maxNumOfLSAs INTEGER ::= 20 +1709 +1710 LSADatA ::= SEQUENCE { +1711 lsaIdentity [0] LSADatAIdentity, +1712 lsaAttributes [1] LSADatAAttributes, +1713 lsaActiveModeIndicator [2] NULL OPTIONAL, +1714 extensionContainer [3] ExtensionContainer OPTIONAL, +1715 ... } +1716 +1717 LSADatAInformation ::= SEQUENCE { +1718 completeDataListIncluded NULL OPTIONAL, +1719 +1720 -- If segmentation is used, completeDataListIncluded may only be present in the +1721 -- first segment. +1722 lsaOnlyAccessIndicator [1] LSAPOnlyAccessIndicator OPTIONAL, +1723 lsaDataList [2] LSADatalist OPTIONAL, +1724 extensionContainer [3] ExtensionContainer OPTIONAL, +1725 ... } +1726 + +``` + +``` + +1727 LSAIdentity := OCTET STRING (SIZE (3)) +1728 -- Octets are coded according to TS 3GPP TS 23.003 [17] +1729 +1730 LSAAttributes := OCTET STRING (SIZE (1)) +1731 -- Octets are coded according to TS 3GPP TS 48.008 [49] +1732 +1733 SubscriberData := SEQUENCE { +1734 msisdn [1] ISDN-AddressString OPTIONAL, +1735 category [2] Category OPTIONAL, +1736 subscriberStatus [3] SubscriberStatus OPTIONAL, +1737 bearerServiceList [4] BearerServiceList OPTIONAL, +1738 -- The exception handling for reception of unsupported / not allocated +1739 -- bearerServiceCodes is defined in clause 8.8.1 +1740 teleserviceList [6] TeleserviceList OPTIONAL, +1741 -- The exception handling for reception of unsupported / not allocated +1742 -- teleserviceCodes is defined in clause 8.8.1 +1743 provisionedSS [7] Ext-SS-InfoList OPTIONAL, +1744 odb-Data [8] ODB-Data OPTIONAL, +1745 roamingRestrictionDueToUnsupportedFeature [9] NULL OPTIONAL, +1746 regionalSubscriptionData [10] ZoneCodeList OPTIONAL, +1747 vbssSubscriptionData [11] VBSDatalist OPTIONAL, +1748 vgcsSubscriptionData [12] VGCSDataList OPTIONAL, +1749 vlrCamelSubscriptionInfo [13] VlrCamelSubscriptionInfo OPTIONAL +1750 } +1751 +1752 Category := OCTET STRING (SIZE (1)) +1753 -- The internal structure is defined in ITU-T Rec Q.763. +1754 +1755 SubscriberStatus := ENUMERATED { +1756 serviceGranted (0), +1757 operatorDeterminedBarring (1)} +1758 +1759 BearerServiceList := SEQUENCE SIZE (1..maxNumOfBearerServices) OF +1760 Ext-BearerServiceCode +1761 +1762 maxNumOfBearerServices INTEGER := 50 +1763 +1764 TeleserviceList := SEQUENCE SIZE (1..maxNumOfTeleservices) OF +1765 Ext-TeleserviceCode +1766 +1767 maxNumOfTeleservices INTEGER := 20 +1768 +1769 ODB-Data := SEQUENCE { +1770 odb-GeneralData ODB-GeneralData, +1771 odb-HPLMN-Data ODB-HPLMN-Data OPTIONAL, +1772 extensionContainer ExtensionContainer OPTIONAL, +1773 ...} +1774 + +``` + +``` + +1775 ODB-GeneralData ::= BIT STRING { +1776 allOG-CallsBarred (0), +1777 internationalOGCallsBarred (1), +1778 internationalOGCallsNotToHPLMN-CountryBarred (2), +1779 interzonalOGCallsBarred (6), +1780 interzonalOGCallsNotToHPLMN-CountryBarred (7), +1781 interzonalOGCallsAndInternationalOGCallsNotToHPLMN-CountryBarred (8), +1782 premiumRateInformationOGCallsBarred (3), +1783 premiumRateEntertainmentOGCallsBarred (4), +1784 ss-AccessBarred (5), +1785 allECT-Barred (9), +1786 chargeableECT-Barred (10), +1787 internationalECT-Barred (11), +1788 interzonalECT-Barred (12), +1789 doublyChargeableECT-Barred (13), +1790 multipleECT-Barred (14), +1791 allPacketOrientedServicesBarred (15), +1792 roamerAccessToHPLMN-AP-Barred (16), +1793 roamerAccessToVPLMN-AP-Barred (17), +1794 roamingOutsidePLMNOG-CallsBarred (18), +1795 allIC-CallsBarred (19), +1796 roamingOutsidePLMNIC-CallsBarred (20), +1797 roamingOutsidePLMNCountryIC-CallsBarred (21), +1798 roamingOutsidePLMN-Barred (22), +1799 roamingOutsidePLMN-CountryBarred (23), +1800 registrationAllCF-Barred (24), +1801 registrationCFNotToHPLMN-Barred (25), +1802 registrationInterzonalCF-Barred (26), +1803 registrationInterzonalCFNotToHPLMN-Barred (27), +1804 registrationInternationalCF-Barred (28)} (SIZE (15..32)) +1805 -- exception handling: reception of unknown bit assignments in the +1806 -- ODB-GeneralData type shall be treated like unsupported ODB-GeneralData +1807 -- When the ODB-GeneralData type is removed from the HLR for a given subscriber, +1808 -- in NoteSubscriberDataModified operation sent toward the gsmSCF +1809 -- all bits shall be set to "0". +1810 +1811 ODB-HPLMN-Data ::= BIT STRING { +1812 plmn-SpecificBarringType1 (0), +1813 plmn-SpecificBarringType2 (1), +1814 plmn-SpecificBarringType3 (2), +1815 plmn-SpecificBarringType4 (3)} (SIZE (4..32)) +1816 -- exception handling: reception of unknown bit assignments in the +1817 -- ODB-HPLMN-Data type shall be treated like unsupported ODB-HPLMN-Data +1818 -- When the ODB-HPLMN-Data type is removed from the HLR for a given subscriber, +1819 -- in NoteSubscriberDataModified operation sent toward the gsmSCF +1820 -- all bits shall be set to "0". +1821 +1822 Ext-SS-InfoList ::= SEQUENCE SIZE (1..maxNumOfSS) OF +1823 Ext-SS-Info +1824 +1825 Ext-SS-Info ::= CHOICE { +1826 forwardingInfo [0] Ext-ForwInfo, +1827 callBarringInfo [1] Ext-CallBarInfo, +1828 cug-Info [2] CUG-Info, +1829 ss-Data [3] Ext-SS-Data, +1830 emlpp-Info [4] EMLPP-Info} +1831 +1832 Ext-ForwInfo ::= SEQUENCE { +1833 ss-Code SS-Code, +1834 forwardingFeatureList Ext-ForwFeatureList, +1835 extensionContainer [0] ExtensionContainer OPTIONAL, +1836 ...} +1837 +1838 Ext-ForwFeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF +1839 Ext-ForwFeature +1840 + +``` + +``` + +1841 Ext-ForwFeature ::= SEQUENCE { +1842 basicService Ext-BasicServiceCode OPTIONAL, +1843 ss-Status [4] Ext-SS-Status, +1844 forwardedToNumber [5] ISDN-AddressString OPTIONAL, +1845 -- When this data type is sent from an HLR which supports CAMEL Phase 2 +1846 -- to a VLR that supports CAMEL Phase 2 the VLR shall not check the +1847 -- format of the number +1848 forwardedToSubaddress [8] ISDN-SubaddressString OPTIONAL, +1849 forwardingOptions [6] Ext-ForwOptions OPTIONAL, +1850 noReplyConditionTime [7] Ext-NoRepCondTime OPTIONAL, +1851 extensionContainer [9] ExtensionContainer OPTIONAL, +1852 ..., +1853 longForwardedToNumber [10] FTN-AddressString OPTIONAL } +1854 +1855 Ext-ForwOptions ::= OCTET STRING (SIZE (1..5)) +1856 +1857 -- OCTET 1: +1858 +1859 -- bit 8: notification to forwarding party +1860 -- 0 no notification +1861 -- 1 notification +1862 +1863 -- bit 7: redirecting presentation +1864 -- 0 no presentation +1865 -- 1 presentation +1866 +1867 -- bit 6: notification to calling party +1868 -- 0 no notification +1869 -- 1 notification +1870 +1871 -- bit 5: 0 (unused) +1872 +1873 -- bits 43: forwarding reason +1874 -- 00 ms not reachable +1875 -- 01 ms busy +1876 -- 10 no reply +1877 -- 11 unconditional +1878 +1879 -- bits 21: 00 (unused) +1880 +1881 -- OCTETS 2-5: reserved for future use. They shall be discarded if +1882 -- received and not understood. +1883 +1884 Ext-NoRepCondTime ::= INTEGER (1..100) +1885 -- Only values 5-30 are used. +1886 -- Values in the ranges 1-4 and 31-100 are reserved for future use +1887 -- If received: +1888 -- values 1-4 shall be mapped on to value 5 +1889 -- values 31-100 shall be mapped on to value 30 +1890 +1891 Ext-CallBarInfo ::= SEQUENCE { +1892 ss-Code SS-Code, +1893 callBarringFeatureList Ext-CallBarFeatureList, +1894 extensionContainer ExtensionContainer OPTIONAL, +1895 ...} +1896 +1897 Ext-CallBarFeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF +1898 Ext-CallBarringFeature +1899 +1900 Ext-CallBarringFeature ::= SEQUENCE { +1901 basicService Ext-BasicServiceCode OPTIONAL, +1902 ss-Status [4] Ext-SS-Status, +1903 extensionContainer ExtensionContainer OPTIONAL, +1904 ...} +1905 +1906 CUG-Info ::= SEQUENCE { +1907 cug-SubscriptionList CUG-SubscriptionList, +1908 cug-FeatureList CUG-FeatureList OPTIONAL, +1909 extensionContainer [0] ExtensionContainer OPTIONAL, +1910 ...} +1911 +1912 CUG-SubscriptionList ::= SEQUENCE SIZE (0..maxNumOfCUG) OF +1913 CUG-Subscription +1914 + +``` + +``` + +1915 CUG-Subscription ::= SEQUENCE { +1916 cug-Index CUG-Index, +1917 CUG-Interlock, +1918 intraCUG-Options IntraCUG-Options, +1919 basicServiceGroupList Ext-BasicServiceGroupList OPTIONAL, +1920 extensionContainer [0] ExtensionContainer OPTIONAL, +1921 ...} +1922 +1923 CUG-Index ::= INTEGER (0..32767) +1924 -- The internal structure is defined in ETS 300 138. +1925 +1926 CUG-Interlock ::= OCTET STRING (SIZE (4)) +1927 +1928 IntraCUG-Options ::= ENUMERATED { +1929 noCUG-Restrictions (0), +1930 cugIC-CallBarred (1), +1931 cugOG-CallBarred (2) } +1932 +1933 maxNumOfCUG INTEGER ::= 10 +1934 +1935 CUG-FeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF +1936 CUG-Feature +1937 +1938 Ext-BasicServiceGroupList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF +1939 Ext-BasicServiceCode +1940 +1941 maxNumOfExt-BasicServiceGroups INTEGER ::= 32 +1942 +1943 CUG-Feature ::= SEQUENCE { +1944 basicService Ext-BasicServiceCode OPTIONAL, +1945 preferentialCUG-Indicator CUG-Index OPTIONAL, +1946 interCUG-Restrictions InterCUG-Restrictions, +1947 extensionContainer ExtensionContainer OPTIONAL, +1948 ...} +1949 +1950 InterCUG-Restrictions ::= OCTET STRING (SIZE (1)) +1951 +1952 -- bits 876543: 000000 (unused) +1953 -- Exception handling: +1954 -- bits 876543 shall be ignored if received and not understood +1955 +1956 -- bits 21 +1957 -- 00 CUG only facilities +1958 -- 01 CUG with outgoing access +1959 -- 10 CUG with incoming access +1960 -- 11 CUG with both outgoing and incoming access +1961 +1962 Ext-SS-Data ::= SEQUENCE { +1963 ss-Code SS-Code, +1964 ss-Status [4] Ext-SS-Status, +1965 ss-SubscriptionOption SS-SubscriptionOption OPTIONAL, +1966 basicServiceGroupList Ext-BasicServiceGroupList OPTIONAL, +1967 extensionContainer [5] ExtensionContainer OPTIONAL, +1968 ...} +1969 +1970 LCS-PrivacyExceptionList ::= SEQUENCE SIZE (1..maxNumOfPrivacyClass) OF +1971 LCS-PrivacyClass +1972 +1973 maxNumOfPrivacyClass INTEGER ::= 4 + +``` + +``` + +1974 +1975 LCS-PrivacyClass ::= SEQUENCE { +1976 ss-Code SS-Code, +1977 ss-Status Ext-SS-Status, +1978 notificationToMSUser [0] NotificationToMSUser OPTIONAL, +1979 -- notificationToMSUser may be sent only for SS-codes callSessionRelated +1980 -- and callSessionUnrelated. If not received for SS-codes callSessionRelated +1981 -- and callSessionUnrelated, +1982 -- the default values according to 3GPP TS 23.271 shall be assumed. +1983 externalClientList [1] ExternalClientList OPTIONAL, +1984 -- externalClientList may be sent only for SS-code callSessionUnrelated to a +1985 -- visited node that does not support LCS Release 4 or later versions. +1986 -- externalClientList may be sent only for SS-codes callSessionUnrelated and +1987 -- callSessionRelated to a visited node that supports LCS Release 4 or later versions. +1988 plmnClientList [2] PLMNClientList OPTIONAL, +1989 -- plmnClientList may be sent only for SS-code plmnoperator. +1990 extensionContainer [3] ExtensionContainer OPTIONAL, +1991 ..., +1992 ext-externalClientList [4] Ext-ExternalClientList OPTIONAL, +1993 -- Ext-externalClientList may be sent only if the visited node supports LCS Release 4 or +1994 -- later versions, the user did specify more than 5 clients, and White Book SCCP is used. +1995 serviceTypeList [5] ServiceTypeList OPTIONAL +1996 -- serviceTypeList may be sent only for SS-code serviceType and if the visited node +1997 -- supports LCS Release 5 or later versions. +1998 -- +1999 -- if segmentation is used, the complete LCS-PrivacyClass shall be sent in one segment +2000 } +2001 +2002 ExternalClientList ::= SEQUENCE SIZE (0..maxNumOfExternalClient) OF +2003 ExternalClient +2004 +2005 maxNumOfExternalClient INTEGER ::= 5 +2006 +2007 PLMNClientList ::= SEQUENCE SIZE (1..maxNumOfPLMNClient) OF +2008 LCSCClientInternalID +2009 +2010 maxNumOfPLMNClient INTEGER ::= 5 +2011 +2012 Ext-ExternalClientList ::= SEQUENCE SIZE (1..maxNumOfExt-ExternalClient) OF +2013 ExternalClient +2014 +2015 maxNumOfExt-ExternalClient INTEGER ::= 35 +2016 +2017 ExternalClient ::= SEQUENCE { +2018 clientIdentity LCSCClientExternalID, +2019 gmlc-Restriction [0] GMLC-Restriction OPTIONAL, +2020 notificationToMSUser [1] NotificationToMSUser OPTIONAL, +2021 -- If notificationToMSUser is not received, the default value according to +2022 -- 3GPP TS 23.271 shall be assumed. +2023 extensionContainer [2] ExtensionContainer OPTIONAL, +2024 ... } +2025 +2026 GMLC-Restriction ::= ENUMERATED { +2027 gmlc-List (0), +2028 home-Country (1) , +2029 ... } +2030 -- exception handling: +2031 -- At reception of any other value than the ones listed the receiver shall ignore +2032 -- GMLC-Restriction. +2033 +2034 NotificationToMSUser ::= ENUMERATED { +2035 notifyLocationAllowed (0), +2036 notifyAndVerify-LocationAllowedIfNoResponse (1), +2037 notifyAndVerify-LocationNotAllowedIfNoResponse (2), +2038 ..., +2039 locationNotAllowed (3) } +2040 -- exception handling: +2041 -- At reception of any other value than the ones listed the receiver shall ignore +2042 -- NotificationToMSUser. +2043 +2044 ServiceTypeList ::= SEQUENCE SIZE (1..maxNumOfServiceType) OF +2045 ServiceType +2046 +2047 maxNumOfServiceType INTEGER ::= 32 +2048 + +``` + +``` + +2049 ServiceType ::= SEQUENCE { +2050 serviceTypeIdentity LCSServiceTypeID, +2051 gmlc-Restriction [0] GMLC-Restriction OPTIONAL, +2052 notificationToMSUser [1] NotificationToMSUser OPTIONAL, +2053 -- If notificationToMSUser is not received, the default value according to +2054 -- 3GPP TS 23.271 shall be assumed. +2055 extensionContainer [2] ExtensionContainer OPTIONAL, +2056 ... } +2057 +2058 MOLR-List ::= SEQUENCE SIZE (1..maxNumOfMOLR-Class) OF +2059 MOLR-Class +2060 +2061 maxNumOfMOLR-Class INTEGER ::= 3 +2062 +2063 MOLR-Class ::= SEQUENCE { +2064 ss-Code SS-Code, +2065 ss-Status Ext-SS-Status, +2066 extensionContainer [0] ExtensionContainer OPTIONAL, +2067 ... } +2068 +2069 ZoneCodeList ::= SEQUENCE SIZE (1..maxNumOfZoneCodes) +2070 OF ZoneCode +2071 +2072 ZoneCode ::= OCTET STRING (SIZE (2)) +2073 -- internal structure is defined in TS 3GPP TS 23.003 [17] +2074 +2075 maxNumOfZoneCodes INTEGER ::= 10 +2076 +2077 InsertSubscriberDataRes ::= SEQUENCE { +2078 teleserviceList [1] TeleserviceList OPTIONAL, +2079 bearerServiceList [2] BearerServiceList OPTIONAL, +2080 ss-List [3] SS-List OPTIONAL, +2081 odb-GeneralData [4] ODB-GeneralData OPTIONAL, +2082 regionalSubscriptionResponse [5] RegionalSubscriptionResponse OPTIONAL, +2083 supportedCamelPhases [6] SupportedCamelPhases OPTIONAL, +2084 extensionContainer [7] ExtensionContainer OPTIONAL, +2085 ... , +2086 offeredCamel4CSIs [8] OfferedCamel4CSIs OPTIONAL, +2087 supportedFeatures [9] SupportedFeatures OPTIONAL, +2088 ext-SupportedFeatures [10] Ext-SupportedFeatures OPTIONAL } +2089 +2090 RegionalSubscriptionResponse ::= ENUMERATED { +2091 networkNode-AreaRestricted (0), +2092 tooManyZoneCodes (1), +2093 zoneCodesConflict (2), +2094 regionalSubscNotSupported (3) } +2095 +2096 DeleteSubscriberDataArg ::= SEQUENCE { +2097 imsi [0] IMSI, +2098 basicServiceList [1] BasicServiceList OPTIONAL, +2099 -- The exception handling for reception of unsupported/not allocated +2100 -- basicServiceCodes is defined in clause 6.8.2 +2101 ss-List [2] SS-List OPTIONAL, +2102 roamingRestrictionDueToUnsupportedFeature [4] NULL OPTIONAL, +2103 regionalSubscriptionIdentifier [5] ZoneCode OPTIONAL, +2104 vbsGroupIndication [7] NULL OPTIONAL, +2105 vgcsGroupIndication [8] NULL OPTIONAL, +2106 camelSubscriptionInfoWithdraw [9] NULL OPTIONAL, +2107 extensionContainer [6] ExtensionContainer OPTIONAL, +2108 ..., +2109 gprsSubscriptionDataWithdraw [10] GPRSSubscriptionDataWithdraw OPTIONAL, +2110 roamingRestrictedInSgsnDueToUnsupportedFeature [11] NULL OPTIONAL, +2111 lsaInformationWithdraw [12] LSAInformationWithdraw OPTIONAL, +2112 gmlc-ListWithdraw [13] NULL OPTIONAL, +2113 istInformationWithdraw [14] NULL OPTIONAL, +2114 specificCSI-Withdraw [15] SpecificCSI-Withdraw OPTIONAL, +2115 chargingCharacteristicsWithdraw [16] NULL OPTIONAL, +2116 stn-srWithdraw [17] NULL OPTIONAL, +2117 epsSubscriptionDataWithdraw [18] EPS-SubscriptionDataWithdraw OPTIONAL, +2118 apn-oi-replacementWithdraw [19] NULL OPTIONAL, +2119 csg-SubscriptionDeleted [20] NULL OPTIONAL, +2120 subscribedPeriodicTAU-RAU-TimerWithdraw [22] NULL OPTIONAL, +2121 subscribedPeriodicLAU-TimerWithdraw [23] NULL OPTIONAL, +2122 subscribed-vsrvccWithdraw [21] NULL OPTIONAL, +2123 vplmn-Csg-SubscriptionDeleted [24] NULL OPTIONAL, +2124 additionalMSISDN-Withdraw [25] NULL OPTIONAL, +2125 cs-to-ps-SRVCC-Withdraw [26] NULL OPTIONAL, + +``` + +``` + +2126 imsiGroupIdList-Withdraw [27] NULL OPTIONAL, +2127 userPlaneIntegrityProtectionWithdraw [28] NULL OPTIONAL, +2128 dl-Buffering-Suggested-Packet-Count-Withdraw [29] NULL OPTIONAL, +2129 ue-UsageTypeWithdraw [30] NULL OPTIONAL, +2130 reset-idsWithdraw [31] NULL OPTIONAL, +2131 iab-OperationWithdraw [32] NULL OPTIONAL } +2132 +2133 SpecificCSI-Withdraw ::= BIT STRING { +2134 o-csi (0), +2135 ss-csi (1), +2136 tif-csi (2), +2137 d-csi (3), +2138 vt-csi (4), +2139 mo-sms-csi (5), +2140 m-csi (6), +2141 gprs-csi (7), +2142 t-csi (8), +2143 mt-sms-csi (9), +2144 mg-csi (10), +2145 o-IM-CSI (11), +2146 d-IM-CSI (12), +2147 vt-IM-CSI (13) } (SIZE(8..32)) +2148 -- exception handling: +2149 -- bits 11 to 31 shall be ignored if received by a non-IP Multimedia Core Network entity. +2150 -- bits 0-10 and 14-31 shall be ignored if received by an IP Multimedia Core Network entity. +2151 -- bits 11-13 are only applicable in an IP Multimedia Core Network. +2152 -- Bit 8 and bits 11-13 are only applicable for the NoteSubscriberDataModified operation. +2153 +2154 GPRSSubscriptionDataWithdraw ::= CHOICE { +2155 allGPRSData NULL, +2156 contextIdList ContextIdList} +2157 +2158 EPS-SubscriptionDataWithdraw ::= CHOICE { +2159 allEPS-Data NULL, +2160 contextIdList ContextIdList} +2161 +2162 ContextIdList ::= SEQUENCE SIZE (1..maxNumOfPDP-Contexts) OF +2163 ContextId +2164 +2165 LSAInformationWithdraw ::= CHOICE { +2166 allLSAData NULL, +2167 lsaIdentityList LSAIdentityList } +2168 +2169 LSAIdentityList ::= SEQUENCE SIZE (1..maxNumOfLSAs) OF +2170 LSAIdentity +2171 +2172 BasicServiceList ::= SEQUENCE SIZE (1..maxNumOfBasicServices) OF +2173 Ext-BasicServiceCode +2174 +2175 maxNumOfBasicServices INTEGER ::= 70 +2176 +2177 DeleteSubscriberDataRes ::= SEQUENCE { +2178 regionalSubscriptionResponse [0] RegionalSubscriptionResponse OPTIONAL, +2179 extensionContainer [1] ExtensionContainer OPTIONAL, +2180 ...} +2181 +2182 VlrCamelSubscriptionInfo ::= SEQUENCE { +2183 o-CSI [0] O-CSI OPTIONAL, +2184 extensionContainer [1] ExtensionContainer OPTIONAL, +2185 ..., +2186 ss-CSI [2] SS-CSI OPTIONAL, +2187 o-BcsmCamelTDP-CriteriaList [4] O-BcsmCamelTDP-CriteriaList OPTIONAL, +2188 tif-CSI [3] NULL OPTIONAL, +2189 m-CSI [5] M-CSI OPTIONAL, +2190 mo-sms-CSI [6] SMS-CSI OPTIONAL, +2191 vt-CSI [7] T-CSI OPTIONAL, +2192 t-BCSM-CAMEL-TDP-CriteriaList [8] T-BCSM-CAMEL-TDP-CriteriaList OPTIONAL, +2193 d-CSI [9] D-CSI OPTIONAL, +2194 mt-sms-CSI [10] SMS-CSI OPTIONAL, +2195 mt-smsCAMELTDP-CriteriaList [11] MT-smsCAMELTDP-CriteriaList OPTIONAL +2196 } +2197 +2198 MT-smsCAMELTDP-CriteriaList ::= SEQUENCE SIZE (1.. maxNumOfCamelTDPData) OF +2199 MT-smsCAMELTDP-Criteria +2200 + +``` + +``` + +2201 MT-smsCAMELTPD-Criteria ::= SEQUENCE { +2202 sms-TriggerDetectionPoint SMS-TriggerDetectionPoint, +2203 tpdu-TypeCriterion [0] TPDU-TypeCriterion OPTIONAL, +2204 ... } +2205 +2206 TPDU-TypeCriterion ::= SEQUENCE SIZE (1..maxNumOfTPDUTypes) OF +2207 MT-SMS-TPDU-Type +2208 +2209 +2210 maxNumOfTPDUTypes INTEGER ::= 5 +2211 +2212 MT-SMS-TPDU-Type ::= ENUMERATED { +2213 sms-DELIVER (0), +2214 sms-SUBMIT-REPORT (1), +2215 sms-STATUS-REPORT (2), +2216 ... } +2217 +2218 -- exception handling: +2219 -- For TPDU-TypeCriterion sequences containing this parameter with any +2220 -- other value than the ones listed above the receiver shall ignore +2221 -- the whole TPDU-TypeCriterion sequence. +2222 -- In CAMEL phase 4, sms-SUBMIT-REPORT shall not be used and a received TPDU-TypeCriterion +2223 -- sequence containing sms-SUBMIT-REPORT shall be wholly ignored. +2224 +2225 D-CSI ::= SEQUENCE { +2226 dp-AnalysedInfoCriteriaList [0] DP-AnalysedInfoCriteriaList OPTIONAL, +2227 camelCapabilityHandling [1] CamelCapabilityHandling OPTIONAL, +2228 extensionContainer [2] ExtensionContainer OPTIONAL, +2229 notificationToCSE [3] NULL OPTIONAL, +2230 csi-Active [4] NULL OPTIONAL, +2231 ...} +2232 -- notificationToCSE and csi-Active shall not be present when D-CSI is sent to VLR/GMSC. +2233 -- They may only be included in ATSI/ATM ack/NSDC message. +2234 -- DP-AnalysedInfoCriteria and camelCapabilityHandling shall be present in +2235 -- the D-CSI sequence. +2236 -- If D-CSI is segmented, then the first segment shall contain dp-AnalysedInfoCriteriaList +2237 -- and camelCapabilityHandling. Subsequent segments shall not contain +2238 -- camelCapabilityHandling, but may contain dp-AnalysedInfoCriteriaList. +2239 +2240 DP-AnalysedInfoCriteriaList ::= SEQUENCE SIZE (1..maxNumOfDP-AnalysedInfoCriteria) OF +2241 DP-AnalysedInfoCriterium +2242 +2243 maxNumOfDP-AnalysedInfoCriteria INTEGER ::= 10 +2244 +2245 DP-AnalysedInfoCriterium ::= SEQUENCE { +2246 dialledNumber ISDN-AddressString, +2247 serviceKey ServiceKey, +2248 gsmSCF-Address ISDN-AddressString, +2249 defaultCallHandling DefaultCallHandling, +2250 extensionContainer ExtensionContainer OPTIONAL, +2251 ...} +2252 +2253 SS-CSI ::= SEQUENCE { +2254 ss-CamelData SS-CamelData, +2255 extensionContainer ExtensionContainer OPTIONAL, +2256 ..., +2257 notificationToCSE [0] NULL OPTIONAL, +2258 csi-Active [1] NULL OPTIONAL +2259 -- notificationToCSE and csi-Active shall not be present when SS-CSI is sent to VLR. +2260 -- They may only be included in ATSI/ATM ack/NSDC message. +2261 } +2262 +2263 SS-CamelData ::= SEQUENCE { +2264 ss-EventList SS-EventList, +2265 gsmSCF-Address ISDN-AddressString, +2266 extensionContainer [0] ExtensionContainer OPTIONAL, +2267 ...} +2268 +2269 + +``` + +``` + +2269 SS-EventList ::= SEQUENCE SIZE (1..maxNumOfCamelSSEvents) OF SS-Code +2270 -- Actions for the following SS-Code values are defined in CAMEL Phase 3: +2271 -- ect SS-Code ::= '00110001'B +2272 -- multiPTY SS-Code ::= '01010001'B +2273 -- cd SS-Code ::= '00100100'B +2274 -- cobs SS-Code ::= '01000100'B +2275 -- all other SS codes shall be ignored +2276 -- When SS-CSI is sent to the VLR, it shall not contain a marking for cobs. +2277 -- If the VLR receives SS-CSI containing a marking for cobs, the VLR shall discard the +2278 -- cobs marking in SS-CSI. +2279 +2280 maxNumOfCamelSSEvents INTEGER ::= 10 +2281 +2282 O-CSI ::= SEQUENCE { +2283 o-BcsmCamelTDPDataList O-BcsmCamelTDPDataList, +2284 extensionContainer ExtensionContainer OPTIONAL, +2285 ..., +2286 camelCapabilityHandling [0] CamelCapabilityHandling OPTIONAL, +2287 notificationToCSE [1] NULL OPTIONAL, +2288 csiActive [2] NULL OPTIONAL} +2289 -- notificationToCSE and csiActive shall not be present when O-CSI is sent to VLR/GMSC. +2290 -- They may only be included in ATSI/ATM ack/NSDC message. +2291 -- O-CSI shall not be segmented. +2292 +2293 O-BcsmCamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF +2294 O-BcsmCamelTDPData +2295 -- O-BcsmCamelTDPDataList shall not contain more than one instance of +2296 -- O-BcsmCamelTDPData containing the same value for o-BcsmTriggerDetectionPoint. +2297 -- For CAMEL Phase 2, this means that only one instance of O-BcsmCamelTDPData is allowed +2298 -- with o-BcsmTriggerDetectionPoint being equal to DP2. +2299 +2300 maxNumOfCamelTDPData INTEGER ::= 10 +2301 +2302 O-BcsmCamelTDPData ::= SEQUENCE { +2303 o-BcsmTriggerDetectionPoint O-BcsmTriggerDetectionPoint, +2304 serviceKey ServiceKey, +2305 gsmSCF-Address [0] ISDN-AddressString, +2306 defaultCallHandling [1] DefaultCallHandling, +2307 extensionContainer [2] ExtensionContainer OPTIONAL, +2308 ... +2309 } +2310 +2311 ServiceKey ::= INTEGER (0..2147483647) +2312 +2313 O-BcsmTriggerDetectionPoint ::= ENUMERATED { +2314 collectedInfo (2), +2315 ..., +2316 routeSelectFailure (4) } +2317 -- exception handling: +2318 -- For O-BcsmCamelTDPData sequences containing this parameter with any +2319 -- other value than the ones listed the receiver shall ignore the whole +2320 -- O-BcsmCamelTDPData sequence. +2321 -- For O-BcsmCamelTDP-Criteria sequences containing this parameter with any +2322 -- other value than the ones listed the receiver shall ignore the whole +2323 -- O-BcsmCamelTDP-Criteria sequence. +2324 +2325 O-BcsmCamelTDPCriteriaList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF +2326 O-BcsmCamelTDP-Criteria +2327 +2328 T-BCSM-CAMEL-TDP-CriteriaList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF +2329 T-BCSM-CAMEL-TDP-Criteria +2330 +2331 O-BcsmCamelTDP-Criteria ::= SEQUENCE { +2332 o-BcsmTriggerDetectionPoint O-BcsmTriggerDetectionPoint, +2333 destinationNumberCriteria [0] DestinationNumberCriteria OPTIONAL, +2334 basicServiceCriteria [1] BasicServiceCriteria OPTIONAL, +2335 callTypeCriteria [2] CallTypeCriteria OPTIONAL, +2336 ..., +2337 o-CauseValueCriteria [3] O-CauseValueCriteria OPTIONAL, +2338 extensionContainer [4] ExtensionContainer OPTIONAL } +2339 +2340 T-BCSM-CAMEL-TDP-Criteria ::= SEQUENCE { +2341 t-BCSM-TriggerDetectionPoint T-BcsmTriggerDetectionPoint, +2342 basicServiceCriteria [0] BasicServiceCriteria OPTIONAL, +2343 t-CauseValueCriteria [1] T-CauseValueCriteria OPTIONAL, +2344 ... } +2345 + +``` + +``` + +2346 DestinationNumberCriteria ::= SEQUENCE { +2347 matchType [0] MatchType, +2348 destinationNumberList [1] DestinationNumberList OPTIONAL, +2349 destinationNumberLengthList [2] DestinationNumberLengthList OPTIONAL, +2350 -- one or both of destinationNumberList and destinationNumberLengthList +2351 -- shall be present +2352 ...} +2353 +2354 DestinationNumberList ::= SEQUENCE SIZE (1..maxNumOfCamelDestinationNumbers) OF +2355 ISDN-AddressString +2356 -- The receiving entity shall not check the format of a number in +2357 -- the dialled number list +2358 +2359 DestinationNumberLengthList ::= SEQUENCE SIZE (1..maxNumOfCamelDestinationNumberLengths) OF +2360 +2361 INTEGER(1..maxNumOfISDN-AddressDigits) +2362 +2363 BasicServiceCriteria ::= SEQUENCE SIZE(1..maxNumOfCamelBasicServiceCriteria) OF +2364 Ext-BasicServiceCode +2365 +2366 maxNumOfISDN-AddressDigits INTEGER ::= 15 +2367 +2368 maxNumOfCamelDestinationNumbers INTEGER ::= 10 +2369 +2370 maxNumOfCamelDestinationNumberLengths INTEGER ::= 3 +2371 +2372 maxNumOfCamelBasicServiceCriteria INTEGER ::= 5 +2373 +2374 CallTypeCriteria ::= ENUMERATED { +2375 forwarded (0), +2376 notForwarded (1)} +2377 +2378 MatchType ::= ENUMERATED { +2379 inhibiting (0), +2380 enabling (1)} +2381 +2382 O-CauseValueCriteria ::= SEQUENCE SIZE(1..maxNumOfCAMEL-O-CauseValueCriteria) OF +2383 CauseValue +2384 +2385 T-CauseValueCriteria ::= SEQUENCE SIZE(1..maxNumOfCAMEL-T-CauseValueCriteria) OF +2386 CauseValue +2387 +2388 maxNumOfCAMEL-O-CauseValueCriteria INTEGER ::= 5 +2389 +2390 maxNumOfCAMEL-T-CauseValueCriteria INTEGER ::= 5 +2391 +2392 CauseValue ::= OCTET STRING (SIZE(1)) +2393 -- Type extracted from Cause parameter in ITU-T Recommendation Q.763. +2394 -- For the use of cause value refer to ITU-T Recommendation Q.850. +2395 +2396 DefaultCallHandling ::= ENUMERATED { +2397 continueCall (0) , +2398 releaseCall (1) , +2399 ...} +2400 -- exception handling: +2401 -- reception of values in range 2-31 shall be treated as "continueCall" +2402 -- reception of values greater than 31 shall be treated as "releaseCall" +2403 +2404 CamelCapabilityHandling ::= INTEGER(1..16) +2405 -- value 1 = CAMEL phase 1, +2406 -- value 2 = CAMEL phase 2, +2407 -- value 3 = CAMEL Phase 3, +2408 -- value 4 = CAMEL phase 4: +2409 -- reception of values greater than 4 shall be treated as CAMEL phase 4. +2410 +2411 SupportedCamelPhases ::= BIT STRING { +2412 phase1 (0), +2413 phase2 (1), +2414 phase3 (2), +2415 phase4 (3)} (SIZE (1..16)) +2416 -- A node shall mark in the BIT STRING all CAMEL Phases it supports. +2417 -- Other values than listed above shall be discarded. +2418 + +``` + +``` + +2419 OfferedCamel4CSIs ::= BIT STRING { +2420 o-csi (0), +2421 d-csi (1), +2422 vt-csi (2), +2423 t-csi (3), +2424 mt-sms-csi (4), +2425 mg-csi (5), +2426 psi-enhancements (6) +2427 } (SIZE (7..16)) +2428 -- A node supporting Camel phase 4 shall mark in the BIT STRING all Camel4 CSIs +2429 -- it offers. +2430 -- Other values than listed above shall be discarded. +2431 +2432 OfferedCamel4Functionalities ::= BIT STRING { +2433 initiateCallAttempt (0), +2434 splitLeg (1), +2435 moveLeg (2), +2436 disconnectLeg (3), +2437 entityReleased (4), +2438 dfc-WithArgument (5), +2439 playTone (6), +2440 dtmf-MidCall (7), +2441 chargingIndicator (8), +2442 alertingDP (9), +2443 locationAtAlerting (10), +2444 changeOfPositionDP (11), +2445 or-Interactions (12), +2446 warningToneEnhancements (13), +2447 cf-Enhancements (14), +2448 subscribedEnhancedDialledServices (15), +2449 servingNetworkEnhancedDialledServices (16), +2450 criteriaForChangeOfPositionDP (17), +2451 serviceChangeDP (18), +2452 collectInformation (19) +2453 } (SIZE (15..64)) +2454 -- A node supporting Camel phase 4 shall mark in the BIT STRING all CAMEL4 +2455 -- functionalities it offers. +2456 -- Other values than listed above shall be discarded. +2457 +2458 SMS-CSI ::= SEQUENCE { +2459 sms-CAMEL-TDP-DataList [0] SMS-CAMEL-TDP-DataList OPTIONAL, +2460 camelCapabilityHandling [1] CamelCapabilityHandling OPTIONAL, +2461 extensionContainer [2] ExtensionContainer OPTIONAL, +2462 notificationToCSE [3] NULL OPTIONAL, +2463 csi-Active [4] NULL OPTIONAL, +2464 ...} +2465 -- notificationToCSE and csi-Active shall not be present +2466 -- when MO-SMS-CSI or MT-SMS-CSI is sent to VLR or SGSN. +2467 -- They may only be included in ATSI/ATM ack/NSDC message. +2468 -- SMS-CAMEL-TDP-Data and camelCapabilityHandling shall be present in +2469 -- the SMS-CSI sequence. +2470 -- If SMS-CSI is segmented, sms-CAMEL-TDP-DataList and camelCapabilityHandling shall be +2471 -- present in the first segment +2472 +2473 SMS-CAMEL-TDP-DataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF +2474 SMS-CAMEL-TDP-Data +2475 -- SMS-CAMEL-TDP-DataList shall not contain more than one instance of +2476 -- SMS-CAMEL-TDP-Data containing the same value for sms-TriggerDetectionPoint. +2477 +2478 SMS-CAMEL-TDP-Data ::= SEQUENCE { +2479 sms-TriggerDetectionPoint [0] SMS-TriggerDetectionPoint, +2480 serviceKey [1] ServiceKey, +2481 gsmSCF-Address [2] ISDN-AddressString, +2482 defaultSMS-Handling [3] DefaultSMS-Handling, +2483 extensionContainer [4] ExtensionContainer OPTIONAL, +2484 ... +2485 } +2486 + +``` + +``` + +2487 SMS-TriggerDetectionPoint ::= ENUMERATED { +2488 sms-CollectedInfo (1), +2489 ..., +2490 sms-DeliveryRequest (2) +2491 } +2492 -- exception handling: +2493 -- For SMS-CAMEL-TDP-Data and MT-smsCAMELTDP-Criteria sequences containing this +2494 -- parameter with any other value than the ones listed the receiver shall ignore +2495 -- the whole sequence. +2496 -- +2497 -- If this parameter is received with any other value than sms-CollectedInfo +2498 -- in an SMS-CAMEL-TDP-Data sequence contained in mo-sms-CSI, then the receiver shall +2499 -- ignore the whole SMS-CAMEL-TDP-Data sequence. +2500 -- +2501 -- If this parameter is received with any other value than sms-DeliveryRequest +2502 -- in an SMS-CAMEL-TDP-Data sequence contained in mt-sms-CSI then the receiver shall +2503 -- ignore the whole SMS-CAMEL-TDP-Data sequence. +2504 -- +2505 -- If this parameter is received with any other value than sms-DeliveryRequest +2506 -- in an MT-smsCAMELTDP-Criteria sequence then the receiver shall +2507 -- ignore the whole MT-smsCAMELTDP-Criteria sequence. +2508 +2509 DefaultSMS-Handling ::= ENUMERATED { +2510 continueTransaction (0) , +2511 releaseTransaction (1) , +2512 ...} +2513 -- exception handling: +2514 -- reception of values in range 2-31 shall be treated as "continueTransaction" +2515 -- reception of values greater than 31 shall be treated as "releaseTransaction" +2516 +2517 M-CSI ::= SEQUENCE { +2518 mobilityTriggers MobilityTriggers, +2519 serviceKey ServiceKey, +2520 gsmSCF-Address [0] ISDN-AddressString, +2521 extensionContainer [1] ExtensionContainer OPTIONAL, +2522 notificationToCSE [2] NULL OPTIONAL, +2523 csi-Active [3] NULL OPTIONAL, +2524 ...} +2525 -- notificationToCSE and csi-Active shall not be present when M-CSI is sent to VLR. +2526 -- They may only be included in ATSI/ATM ack/NSDC message. +2527 +2528 MG-CSI ::= SEQUENCE { +2529 mobilityTriggers MobilityTriggers, +2530 serviceKey ServiceKey, +2531 gsmSCF-Address [0] ISDN-AddressString, +2532 extensionContainer [1] ExtensionContainer OPTIONAL, +2533 notificationToCSE [2] NULL OPTIONAL, +2534 csi-Active [3] NULL OPTIONAL, +2535 ...} +2536 -- notificationToCSE and csi-Active shall not be present when MG-CSI is sent to SGSN. +2537 -- They may only be included in ATSI/ATM ack/NSDC message. +2538 +2539 MobilityTriggers ::= SEQUENCE SIZE (1..maxNumOfMobilityTriggers) OF +2540 MM-Code +2541 +2542 maxNumOfMobilityTriggers INTEGER ::= 10 +2543 + +``` + +``` + +2544 MM-Code ::= OCTET STRING (SIZE (1)) +2545 -- This type is used to indicate a Mobility Management event. +2546 -- Actions for the following MM-Code values are defined in CAMEL Phase 4: +2547 -- +2548 -- CS domain MM events: +2549 -- Location-update-in-same-VLR MM-Code ::= '00000000'B +2550 -- Location-update-to-other-VLR MM-Code ::= '00000001'B +2551 -- IMSI-Attach MM-Code ::= '00000010'B +2552 -- MS-initiated-IMSI-Detach MM-Code ::= '00000011'B +2553 -- Network-initiated-IMSI-Detach MM-Code ::= '00000100'B +2554 -- +2555 -- PS domain MM events: +2556 -- Routeing-Area-update-in-same-SGSN MM-Code ::= '10000000'B +2557 -- Routeing-Area-update-to-other-SGSN-update-from-new-SGSN +2558 -- MM-Code ::= '10000001'B +2559 -- Routeing-Area-update-to-other-SGSN-disconnect-by-detach +2560 -- MM-Code ::= '10000010'B +2561 -- GPRS-Attach MM-Code ::= '10000011'B +2562 -- MS-initiated-GPRS-Detach MM-Code ::= '10000100'B +2563 -- Network-initiated-GPRS-Detach MM-Code ::= '10000101'B +2564 -- Network-initiated-transfer-to-MS-not-reachable-for-paging +2565 -- MM-Code ::= '10000110'B +2566 -- +2567 -- If the MSC receives any other MM-code than the ones listed above for the +2568 -- CS domain, then the MSC shall ignore that MM-code. +2569 -- If the SGSN receives any other MM-code than the ones listed above for the +2570 -- PS domain, then the SGSN shall ignore that MM-code. +2571 +2572 T-CSI ::= SEQUENCE { +2573 t-BcsmCamelTDPDataList T-BcsmCamelTDPDataList, +2574 extensionContainer ExtensionContainer OPTIONAL, +2575 ..., +2576 camelCapabilityHandling [0] CamelCapabilityHandling OPTIONAL, +2577 notificationToCSE [1] NULL OPTIONAL, +2578 csi-Active [2] NULL OPTIONAL} +2579 -- notificationToCSE and csi-Active shall not be present when VT-CSI/T-CSI is sent +2580 -- to VLR/GMSC. +2581 -- They may only be included in ATSI/ATM ack/NSDC message. +2582 -- T-CSI shall not be segmented. +2583 +2584 T-BcsmCamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF +2585 T-BcsmCamelTDPData +2586 --- T-BcsmCamelTDPDataList shall not contain more than one instance of +2587 --- T-BcsmCamelTDPData containing the same value for t-BcsmTriggerDetectionPoint. +2588 --- For CAMEL Phase 2, this means that only one instance of T-BcsmCamelTDPData is +2589 allowed +2590 --- with t-BcsmTriggerDetectionPoint being equal to DP12. +2591 --- For CAMEL Phase 3, more TDP's are allowed. +2592 +2593 T-BcsmCamelTDPData ::= SEQUENCE { +2594 t-BcsmTriggerDetectionPoint T-BcsmTriggerDetectionPoint, +2595 serviceKey ServiceKey, +2596 gsmSCF-Address [0] ISDN-AddressString, +2597 defaultCallHandling [1] DefaultCallHandling, +2598 extensionContainer [2] ExtensionContainer OPTIONAL, +2599 ...} +2600 +2601 T-BcsmTriggerDetectionPoint ::= ENUMERATED { +2602 termAttemptAuthorized (12), +2603 ... , +2604 tBusy (13), +2605 tNoAnswer (14)} +2606 -- exception handling: +2607 -- For T-BcsmCamelTDPData sequences containing this parameter with any other +2608 -- value than the ones listed above, the receiver shall ignore the whole +2609 -- T-BcsmCamelTDPData sequence. +2610 +2611 -- gprs location information retrieval types +2612 +2613 SendRoutingInfoForGprsArg ::= SEQUENCE { +2614 imsi [0] IMSI, +2615 ggsn-Address [1] GSN-Address OPTIONAL, +2616 ggsn-Number [2] ISDN-AddressString, +2617 extensionContainer [3] ExtensionContainer OPTIONAL, +2618 ...} +2619 + +``` + +``` + +2620 SendRoutingInfoForGprsRes ::= SEQUENCE { +2621 sgsn-Address [0] GSN-Address, +2622 ggsn-Address [1] GSN-Address OPTIONAL, +2623 mobileNotReachableReason [2] AbsentSubscriberDiagnosticSM OPTIONAL, +2624 extensionContainer [3] ExtensionContainer OPTIONAL, +2625 ...} +2626 +2627 -- failure report types +2628 +2629 FailureReportArg ::= SEQUENCE { +2630 imsi [0] IMSI, +2631 ggsn-Number [1] ISDN-AddressString , +2632 ggsn-Address [2] GSN-Address OPTIONAL, +2633 extensionContainer [3] ExtensionContainer OPTIONAL, +2634 ...} +2635 +2636 FailureReportRes ::= SEQUENCE { +2637 ggsn-Address [0] GSN-Address OPTIONAL, +2638 extensionContainer [1] ExtensionContainer OPTIONAL, +2639 ...} +2640 +2641 -- gprs notification types +2642 +2643 NoteMsPresentForGprsArg ::= SEQUENCE { +2644 imsi [0] IMSI, +2645 sgsn-Address [1] GSN-Address, +2646 ggsn-Address [2] GSN-Address OPTIONAL, +2647 extensionContainer [3] ExtensionContainer OPTIONAL, +2648 ...} +2649 +2650 NoteMsPresentForGprsRes ::= SEQUENCE { +2651 extensionContainer [0] ExtensionContainer OPTIONAL, +2652 ...} +2653 +2654 -- fault recovery types +2655 +2656 ResetArg ::= SEQUENCE { +2657 sendingNodeNumber SendingNode-Number, +2658 hlr-List HLR-List OPTIONAL, +2659 -- The hlr-List parameter shall only be applicable for a restart of the HSS/HLR. +2660 extensionContainer [0] ExtensionContainer OPTIONAL, +2661 ..., +2662 reset-Id-List [1] Reset-Id-List OPTIONAL, +2663 subscriptionData [2] InsertSubscriberDataArg OPTIONAL, +2664 subscriptionDataDeletion [3] DeleteSubscriberDataArg OPTIONAL} +2665 +2666 SendingNode-Number ::= CHOICE { +2667 hlr-Number ISDN-AddressString, +2668 css-Number [1] ISDN-AddressString} +2669 +2670 RestoreDataArg ::= SEQUENCE { +2671 imsi IMSI, +2672 lmsi LMSI OPTIONAL, +2673 extensionContainer ExtensionContainer OPTIONAL, +2674 ... , +2675 vlr-Capability [6] VLR-Capability OPTIONAL, +2676 restorationIndicator [7] NULL OPTIONAL +2677 } +2678 +2679 RestoreDataRes ::= SEQUENCE { +2680 hlr-Number ISDN-AddressString, +2681 msNotReachable NULL OPTIONAL, +2682 extensionContainer ExtensionContainer OPTIONAL, +2683 ...} +2684 +2685 -- VBS/VGCS types +2686 VBSDataList ::= SEQUENCE SIZE (1..maxNumOfVBSGroupIds) OF +2687 VoiceBroadcastData +2688 +2689 VGCSDataList ::= SEQUENCE SIZE (1..maxNumOfVGCSGroupIds) OF +2690 VoiceGroupCallData +2691 +2692 maxNumOfVBSGroupIds INTEGER ::= 50 +2693 +2694 maxNumOfVGCSGroupIds INTEGER ::= 50 +2695 + +``` + +``` + +2696 VoiceGroupCallData := SEQUENCE { +2697 groupId GroupId, +2698 -- groupId shall be filled with six TBCD fillers (1111) if the longGroupId is present +2699 extensionContainer ExtensionContainer OPTIONAL, +2700 ..., +2701 additionalSubscriptions AdditionalSubscriptions OPTIONAL, +2702 additionalInfo [0] AdditionalInfo OPTIONAL, +2703 longGroupId [1] Long-GroupId OPTIONAL } +2704 +2705 -- VoiceGroupCallData containing a longGroupId shall not be sent to VLRs that did not +2706 -- indicate support of long Group IDs within the Update Location or Restore Data +2707 -- request message +2708 +2709 AdditionalInfo := BIT STRING (SIZE (1..136)) +2710 -- Refers to Additional Info as specified in 3GPP TS 43.068 +2711 +2712 AdditionalSubscriptions := BIT STRING { +2713 privilegedUplinkRequest (0), +2714 emergencyUplinkRequest (1), +2715 emergencyReset (2)} (SIZE (3..8)) +2716 -- Other bits than listed above shall be discarded. +2717 +2718 VoiceBroadcastData := SEQUENCE { +2719 groupId GroupId, +2720 -- groupId shall be filled with six TBCD fillers (1111) if the longGroupId is present +2721 broadcastInitEntitlement NULL OPTIONAL, +2722 extensionContainer ExtensionContainer OPTIONAL, +2723 ..., +2724 longGroupId [0] Long-GroupId OPTIONAL } +2725 +2726 -- VoiceBroadcastData containing a longGroupId shall not be sent to VLRs that did not +2727 -- indicate support of long Group IDs within the Update Location or Restore Data +2728 -- request message +2729 +2730 GroupId := TBCD-STRING (SIZE (3)) +2731 -- When Group-Id is less than six characters in length, the TBCD filler (1111) +2732 -- is used to fill unused half octets. +2733 -- Refers to the Group Identification as specified in 3GPP TS 23.003 +2734 -- and 3GPP TS 43.068/ 43.069 +2735 +2736 Long-GroupId := TBCD-STRING (SIZE (4)) +2737 -- When Long-Group-Id is less than eight characters in length, the TBCD filler (1111) +2738 -- is used to fill unused half octets. +2739 -- Refers to the Group Identification as specified in 3GPP TS 23.003 +2740 -- and 3GPP TS 43.068/ 43.069 +2741 +2742 +2743 -- provide subscriber info types +2744 +2745 ProvideSubscriberInfoArg := SEQUENCE { +2746 imsi [0] IMSI, +2747 lmsi [1] LMSI OPTIONAL, +2748 requestedInfo [2] RequestedInfo, +2749 extensionContainer [3] ExtensionContainer OPTIONAL, +2750 ..., +2751 callPriority [4] EMLPP-Priority OPTIONAL +2752 } +2753 +2754 ProvideSubscriberInfoRes := SEQUENCE { +2755 subscriberInfo SubscriberInfo, +2756 extensionContainer ExtensionContainer OPTIONAL, +2757 ...} +2758 + +``` + +``` + +2759 SubscriberInfo ::= SEQUENCE { +2760 locationInformation [0] LocationInformation OPTIONAL, +2761 subscriberState [1] SubscriberState OPTIONAL, +2762 extensionContainer [2] ExtensionContainer OPTIONAL, +2763 ... , +2764 locationInformationGPRS [3] LocationInformationGPRS OPTIONAL, +2765 ps-SubscriberState [4] PS-SubscriberState OPTIONAL, +2766 imei [5] IMEI OPTIONAL, +2767 ms-Classmark2 [6] MS-Classmark2 OPTIONAL, +2768 gprs-MS-Class [7] GPRSMSClass OPTIONAL, +2769 mnpInfoRes [8] MNPInfoRes OPTIONAL, +2770 imsVoiceOverPS-SessionsIndication [9] IMS-VoiceOverPS-SessionsInd OPTIONAL, +2771 lastUE-ActivityTime [10] Time OPTIONAL, +2772 lastRAT-Type [11] Used-RAT-Type OPTIONAL, +2773 eps-SubscriberState [12] PS-SubscriberState OPTIONAL, +2774 locationInformationEPS [13] LocationInformationEPS OPTIONAL, +2775 timeZone [14] TimeZone OPTIONAL, +2776 daylightSavingTime [15] DaylightSavingTime OPTIONAL, +2777 locationInformation5GS [16] LocationInformation5GS OPTIONAL } +2778 +2779 -- If the HLR receives locationInformation, subscriberState or ms-Classmark2 from an SGSN or +2780 -- MME (via an IWF), it shall discard them. +2781 -- If the HLR receives locationInformationGPRS, ps-SubscriberState, gprs-MS-Class or +2782 -- locationInformationEPS (outside the locationInformation IE) from a VLR, it shall +2783 -- discard them. +2784 -- If the HLR receives parameters which it has not requested, it shall discard them. +2785 -- The locationInformation5GS IE should be absent if UE did not access via 5GS and IM-SSF. +2786 +2787 IMS-VoiceOverPS-SessionsInd ::= ENUMERATED { +2788 imsVoiceOverPS-SessionsNotSupported (0), +2789 imsVoiceOverPS-SessionsSupported (1), +2790 unknown (2) +2791 } +2792 -- "unknown" shall not be used within ProvideSubscriberInfoRes +2793 +2794 TimeZone ::= OCTET STRING (SIZE (2..3)) +2795 -- Refer to the 3GPP TS 29.272 [144] for details. +2796 +2797 DaylightSavingTime ::= ENUMERATED { +2798 noAdjustment (0), +2799 plusOneHourAdjustment (1), +2800 plusTwoHoursAdjustment (2) +2801 } +2802 -- Refer to the 3GPP TS 29.272 [144] for details. +2803 +2804 MNPInfoRes ::= SEQUENCE { +2805 routeingNumber [0] RouteingNumber OPTIONAL, +2806 imsi [1] IMSI OPTIONAL, +2807 msisdn [2] ISDN-AddressString OPTIONAL, +2808 numberPortabilityStatus [3] NumberPortabilityStatus OPTIONAL, +2809 extensionContainer [4] ExtensionContainer OPTIONAL, +2810 ... } +2811 -- The IMSI parameter contains a generic IMSI, i.e. it is not tied necessarily to the +2812 -- Subscriber. MCC and MNC values in this IMSI shall point to the Subscription Network of +2813 -- the Subscriber. See 3GPP TS 23.066 [108]. +2814 +2815 RouteingNumber ::= TBCD-STRING (SIZE (1..5)) +2816 +2817 +2818 NumberPortabilityStatus ::= ENUMERATED { +2819 notKnownToBePorted (0), +2820 ownNumberPortedOut (1), +2821 foreignNumberPortedToForeignNetwork (2), +2822 ... , +2823 ownNumberNotPortedOut (4), +2824 foreignNumberPortedIn (5) +2825 } +2826 -- exception handling: +2827 -- reception of other values than the ones listed the receiver shall ignore the +2828 -- whole NumberPortabilityStatus; +2829 -- ownNumberNotPortedOut or foreignNumberPortedIn may only be included in Any Time +2830 -- Interrogation message. +2831 +2832 MS-Classmark2 ::= OCTET STRING (SIZE (3)) +2833 -- This parameter carries the value part of the MS Classmark 2 IE defined in +2834 -- 3GPP TS 24.008 [35]. +2835 + +``` + +``` + +2836 GPRSMSClass := SEQUENCE { +2837 mSNetworkCapability [0] MSNetworkCapability, +2838 mSRadioAccessCapability [1] MSRadioAccessCapability OPTIONAL +2839 } +2840 +2841 MSNetworkCapability := OCTET STRING (SIZE (1..8)) +2842 -- This parameter carries the value part of the MS Network Capability IE defined in +2843 -- 3GPP TS 24.008 [35]. +2844 +2845 MSRadioAccessCapability := OCTET STRING (SIZE (1..50)) +2846 -- This parameter carries the value part of the MS Radio Access Capability IE defined in +2847 -- 3GPP TS 24.008 [35]. +2848 +2849 RequestedInfo := SEQUENCE { +2850 locationInformation [0] NULL OPTIONAL, +2851 subscriberState [1] NULL OPTIONAL, +2852 extensionContainer [2] ExtensionContainer OPTIONAL, +2853 ..., +2854 currentLocation [3] NULL OPTIONAL, +2855 requestedDomain [4] DomainType OPTIONAL, +2856 imei [6] NULL OPTIONAL, +2857 ms-classmark [5] NULL OPTIONAL, +2858 mnpRequestedInfo [7] NULL OPTIONAL, +2859 locationInformationEPS-Supported [11] NULL OPTIONAL, +2860 t-adsData [8] NULL OPTIONAL, +2861 requestedNodes [9] RequestedNodes OPTIONAL, +2862 servingNodeIndication [10] NULL OPTIONAL, +2863 localTimeZoneRequest [12] NULL OPTIONAL +2864 } +2865 +2866 -- currentLocation and locationInformationEPS-Supported shall be absent if +2867 -- locationInformation is absent +2868 -- t-adsData shall be absent in messages sent to the VLR +2869 -- requestedNodes shall be absent if requestedDomain is "cs-Domain" +2870 -- servingNodeIndication shall be absent if locationInformation is absent; +2871 -- servingNodeIndication shall be absent if current location is present; +2872 -- servingNodeIndication indicates by its presence that only the serving node's +2873 -- address (MME-Name or SGSN-Number or VLR-Number) is requested. +2874 +2875 DomainType := ENUMERATED { +2876 cs-Domain (0), +2877 ps-Domain (1), +2878 ...} +2879 -- exception handling: +2880 -- reception of values > 1 shall be mapped to 'cs-Domain' +2881 +2882 RequestedNodes := BIT STRING { +2883 mme (0), +2884 sgsn (1)} (SIZE (1..8)) +2885 -- Other bits than listed above shall be discarded. +2886 + +``` + +``` + +2887 LocationInformation ::= SEQUENCE { +2888 ageOfLocationInformation AgeOfLocationInformation OPTIONAL, +2889 geographicalInformation [0] GeographicalInformation OPTIONAL, +2890 vlr-number [1] ISDN-AddressString OPTIONAL, +2891 locationNumber [2] LocationNumber OPTIONAL, +2892 cellGlobalIdOrServiceAreaIdOrLAI [3] CellGlobalIdOrServiceAreaIdOrLAI OPTIONAL, +2893 extensionContainer [4] ExtensionContainer OPTIONAL, +2894 ... , +2895 selectedLSA-Id [5] LSAIdentity OPTIONAL, +2896 msc-Number [6] ISDN-AddressString OPTIONAL, +2897 geodeticInformation [7] GeodeticInformation OPTIONAL, +2898 currentLocationRetrieved [8] NULL OPTIONAL, +2899 sai-Present [9] NULL OPTIONAL, +2900 locationInformationEPS [10] LocationInformationEPS OPTIONAL, +2901 userCSGInformation [11] UserCSGInformation OPTIONAL } +2902 -- sai-Present indicates that the cellGlobalIdOrServiceAreaIdOrLAI parameter contains +2903 -- a Service Area Identity. +2904 -- currentLocationRetrieved shall be present +2905 -- if the location information were retrieved after a successful paging. +2906 -- if the locationInformationEPS IE is present then the cellGlobalIdOrServiceAreaIdOrLAI IE, +2907 -- the ageOfLocationInformation IE, the geographicalInformation IE, the geodeticInformation IE +2908 -- and the currentLocationRetrieved IE (outside the locationInformationEPS IE) shall be +2909 -- absent. As an exception, both the cellGlobalIdOrServiceAreaIdOrLAI IE including an LAI and +2910 -- the locationInformationEPS IE may be present in a MAP-NOTE-MM-EVENT. +2911 -- UserCSGInformation contains the CSG ID, Access mode, and the CSG Membership Indication in +2912 -- the case the Access mode is Hybrid Mode. +2913 -- The locationInformationEPS IE should be absent if locationInformationEPS-Supported was not +2914 -- received in the RequestedInfo IE. + +``` + +``` + +2915 +2916 LocationInformationEPS ::= SEQUENCE { +2917 e-utranCellGlobalIdentity [0] E-UTRAN-CGI OPTIONAL, +2918 trackingAreaIdentity [1] TA-Id OPTIONAL, +2919 extensionContainer [2] ExtensionContainer OPTIONAL, +2920 geographicalInformation [3] GeographicalInformation OPTIONAL, +2921 geodeticInformation [4] GeodeticInformation OPTIONAL, +2922 currentLocationRetrieved [5] NULL OPTIONAL, +2923 ageOfLocationInformation [6] AgeOfLocationInformation OPTIONAL, +2924 ..., +2925 mme-Name [7] DiameterIdentity OPTIONAL } +2926 -- currentLocationRetrieved shall be present if the location information +2927 -- was retrieved after successful paging. + +``` + +``` + +2928 +2929 +2930 LocationInformationGPRS ::= SEQUENCE { +2931 cellGlobalIdOrServiceAreaIdOrLAI [0] CellGlobalIdOrServiceAreaIdOrLAI OPTIONAL, +2932 routeingAreaIdentity [1] RAIdentity OPTIONAL, +2933 geographicalInformation [2] GeographicalInformation OPTIONAL, +2934 sgsn-Number [3] ISDN-AddressString OPTIONAL, +2935 selectedLSAIdentity [4] LSAIdentity OPTIONAL, +2936 extensionContainer [5] ExtensionContainer OPTIONAL, +2937 ..., +2938 sai-Present [6] NULL OPTIONAL, +2939 geodeticInformation [7] GeodeticInformation OPTIONAL, +2940 currentLocationRetrieved [8] NULL OPTIONAL, +2941 ageOfLocationInformation [9] AgeOfLocationInformation OPTIONAL, +2942 userCSGInformation [10] UserCSGInformation OPTIONAL } +2943 -- sai-Present indicates that the cellGlobalIdOrServiceAreaIdOrLAI parameter contains +2944 -- a Service Area Identity. +2945 -- currentLocationRetrieved shall be present if the location information +2946 -- was retrieved after successful paging. +2947 -- UserCSGInformation contains the CSG ID, Access mode, and the CSG Membership Indication in +2948 -- the case the Access mode is Hybrid Mode. + +``` + +``` + +2949 +2950 + +``` + +``` + +2951 LocationInformation5GS ::= SEQUENCE { +2952 nrCellGlobalIdentity [0] NR-CGI OPTIONAL, +2953 e-utranCellGlobalIdentity [1] E-UTRAN-CGI OPTIONAL, +2954 geographicalInformation [2] GeographicalInformation OPTIONAL, +2955 geodeticInformation [3] GeodeticInformation OPTIONAL, +2956 amf-address [4] FQDN OPTIONAL, +2957 trackingAreaIdentity [5] TA-Id OPTIONAL, +2958 currentLocationRetrieved [6] NULL OPTIONAL, +2959 ageOfLocationInformation [7] AgeOfLocationInformation OPTIONAL, +2960 vplmnId [8] PLMN-Id OPTIONAL, +2961 localTimeZone [9] TimeZone OPTIONAL, +2962 rat-Type [10] Used-RAT-Type OPTIONAL, +2963 extensionContainer [11] ExtensionContainer OPTIONAL, +2964 ..., +2965 nrTrackingAreaIdentity [12] NR-TA-Id OPTIONAL +2966 } +2967 -- currentLocationRetrieved shall be present if the location information +2968 -- was retrieved after successful paging. +2969 +2970 +2971 UserCSGInformation ::= SEQUENCE { +2972 csg-Id [0] CSG-Id, +2973 extensionContainer [1] ExtensionContainer OPTIONAL, +2974 ..., +2975 accessMode [2] OCTET STRING (SIZE(1)) OPTIONAL, +2976 cmi [3] OCTET STRING (SIZE(1)) OPTIONAL } +2977 -- The encoding of the accessMode and cmi parameters are as defined in 3GPP TS 29.060 [105]. +2978 +2979 GeographicalInformation ::= OCTET STRING (SIZE (8)) +2980 -- Refers to geographical Information defined in 3GPP TS 23.032. +2981 -- Only the description of an ellipsoid point with uncertainty circle +2982 -- as specified in 3GPP TS 23.032 is allowed to be used +2983 -- The internal structure according to 3GPP TS 23.032 is as follows: +2984 -- Type of shape (ellipsoid point with uncertainty circle) 1 octet +2985 -- Degrees of Latitude 3 octets +2986 -- Degrees of Longitude 3 octets +2987 -- Uncertainty code 1 octet +2988 +2989 GeodeticInformation ::= OCTET STRING (SIZE (10)) +2990 -- Refers to Calling Geodetic Location defined in Q.763 (1999). +2991 -- Only the description of an ellipsoid point with uncertainty circle +2992 -- as specified in Q.763 (1999) is allowed to be used +2993 -- The internal structure according to Q.763 (1999) is as follows: +2994 -- Screening and presentation indicators 1 octet +2995 -- Type of shape (ellipsoid point with uncertainty circle) 1 octet +2996 -- Degrees of Latitude 3 octets +2997 -- Degrees of Longitude 3 octets +2998 -- Uncertainty code 1 octet +2999 -- Confidence 1 octet +3000 +3001 LocationNumber ::= OCTET STRING (SIZE (2..10)) +3002 -- the internal structure is defined in ITU-T Rec Q.763 +3003 +3004 +3005 SubscriberState ::= CHOICE { +3006 assumedIdle [0] NULL, +3007 camelBusy [1] NULL, +3008 netDetNotReachable NotReachableReason, +3009 notProvidedFromVLR [2] NULL} +3010 +3011 +3012 PS-SubscriberState ::= CHOICE { +3013 notProvidedFromSGSNorMME [0] NULL, +3014 ps-Detached [1] NULL, +3015 ps-AttachedNotReachableForPaging [2] NULL, +3016 ps-AttachedReachableForPaging [3] NULL, +3017 ps-PDP-ActiveNotReachableForPaging [4] PDP-ContextInfoList, +3018 ps-PDP-ActiveReachableForPaging [5] PDP-ContextInfoList, +3019 netDetNotReachable NotReachableReason } +3020 +3021 +3022 PDP-ContextInfoList ::= SEQUENCE SIZE (1..maxNumOfPDP-Contexts) OF +3023 PDP-ContextInfo +3024 +3025 +3026 +3027 +3028 +3029 +3030 + +``` + +``` + +3011 PDP-ContextInfo ::= SEQUENCE { +3012 pdp-ContextIdentifier [0] ContextId, +3013 pdp-ContextActive [1] NULL OPTIONAL, +3014 pdp-Type [2] PDP-Type, +3015 pdp-Address [3] PDP-Address OPTIONAL, +3016 apn-Subscribed [4] APN OPTIONAL, +3017 apn-InUse [5] APN OPTIONAL, +3018 nsapi [6] NSAPI OPTIONAL, +3019 transactionId [7] TransactionId OPTIONAL, +3020 teid-ForGnAndGp [8] TEID OPTIONAL, +3021 teid-ForIu [9] TEID OPTIONAL, +3022 ggsn-Address [10] GSN-Address OPTIONAL, +3023 qos-Subscribed [11] Ext-QoS-Subscribed OPTIONAL, +3024 qos-Requested [12] Ext-QoS-Subscribed OPTIONAL, +3025 qos-Negotiated [13] Ext-QoS-Subscribed OPTIONAL, +3026 chargingId [14] GPRSChargingID OPTIONAL, +3027 chargingCharacteristics [15] ChargingCharacteristics OPTIONAL, +3028 rnc-Address [16] GSN-Address OPTIONAL, +3029 extensionContainer [17] ExtensionContainer OPTIONAL, +3030 ..., +3031 qos2-Subscribed [18] Ext2-QoS-Subscribed OPTIONAL, +3032 -- qos2-Subscribed may be present only if qos-Subscribed is present. +3033 qos2-Requested [19] Ext2-QoS-Subscribed OPTIONAL, +3034 -- qos2-Requested may be present only if qos-Requested is present. +3035 qos2-Negotiated [20] Ext2-QoS-Subscribed OPTIONAL, +3036 -- qos2-Negotiated may be present only if qos-Negotiated is present. +3037 qos3-Subscribed [21] Ext3-QoS-Subscribed OPTIONAL, +3038 -- qos3-Subscribed may be present only if qos2-Subscribed is present. +3039 qos3-Requested [22] Ext3-QoS-Subscribed OPTIONAL, +3040 -- qos3-Requested may be present only if qos2-Requested is present. +3041 qos3-Negotiated [23] Ext3-QoS-Subscribed OPTIONAL, +3042 -- qos3-Negotiated may be present only if qos2-Negotiated is present. +3043 qos4-Subscribed [25] Ext4-QoS-Subscribed OPTIONAL, +3044 -- qos4-Subscribed may be present only if qos3-Subscribed is present. +3045 qos4-Requested [26] Ext4-QoS-Subscribed OPTIONAL, +3046 -- qos4-Requested may be present only if qos3-Requested is present. +3047 qos4-Negotiated [27] Ext4-QoS-Subscribed OPTIONAL, +3048 -- qos4-Negotiated may be present only if qos3-Negotiated is present. +3049 ext-pdp-Type [28] Ext-PDP-Type OPTIONAL, +3050 -- contains the value IPv4v6 defined in 3GPP TS 29.060 [105], if the PDP can be +3051 -- accessed by dual-stack UEs. +3052 ext-pdp-Address [29] PDP-Address OPTIONAL +3053 -- contains an additional IP address in case of dual-stack static IP address assignment +3054 -- for the UE. +3055 -- it may contain an IPv4 or an IPv6 address/prefix, and it may be present +3056 -- only if pdp-Address is present; if both are present, each parameter shall +3057 -- contain a different type of address (IPv4 or IPv6). +3058 +3059 } +3060 +3061 NSAPI ::= INTEGER (0..15) +3062 -- This type is used to indicate the Network layer Service Access Point +3063 +3064 TransactionId ::= OCTET STRING (SIZE (1..2)) +3065 -- This type carries the value part of the transaction identifier which is used in the +3066 -- session management messages on the access interface. The encoding is defined in +3067 -- 3GPP TS 24.008 +3068 +3069 TEID ::= OCTET STRING (SIZE (4)) +3070 -- This type carries the value part of the Tunnel Endpoint Identifier which is used to +3071 -- distinguish between different tunnels between the same pair of entities which communicate +3072 -- using the GPRS Tunneling Protocol The encoding is defined in 3GPP TS 29.060. +3073 +3074 GPRSChargingID ::= OCTET STRING (SIZE (4)) +3075 -- The Charging ID is a unique four octet value generated by the GGSN when +3076 -- a PDP Context is activated. A Charging ID is generated for each activated context. +3077 -- The encoding is defined in 3GPP TS 29.060. +3078 +3079 NotReachableReason ::= ENUMERATED { +3080 msPurged (0), +3081 imsiDetached (1), +3082 restrictedArea (2), +3083 notRegistered (3) } +3084 +3085 -- any time interrogation info types +3086 + +``` + +``` + +3087 AnyTimeInterrogationArg ::= SEQUENCE { +3088 subscriberIdentity [0] SubscriberIdentity, +3089 requestedInfo [1] RequestedInfo, +3090 gsmSCF-Address [3] ISDN-AddressString, +3091 extensionContainer [2] ExtensionContainer OPTIONAL, +3092 ... } +3093 +3094 AnyTimeInterrogationRes ::= SEQUENCE { +3095 subscriberInfo SubscriberInfo, +3096 extensionContainer ExtensionContainer OPTIONAL, +3097 ... } +3098 +3099 -- any time information handling types +3100 +3101 AnyTimeSubscriptionInterrogationArg ::= SEQUENCE { +3102 subscriberIdentity [0] SubscriberIdentity, +3103 requestedSubscriptionInfo [1] RequestedSubscriptionInfo, +3104 gsmSCF-Address [2] ISDN-AddressString, +3105 extensionContainer [3] ExtensionContainer OPTIONAL, +3106 longFTN-Supported [4] NULL OPTIONAL, +3107 ... } +3108 +3109 AnyTimeSubscriptionInterrogationRes ::= SEQUENCE { +3110 callForwardingData [1] CallForwardingData OPTIONAL, +3111 callBarringData [2] CallBarringData OPTIONAL, +3112 odb-Info [3] ODB-Info OPTIONAL, +3113 camel-SubscriptionInfo [4] CAMEL-SubscriptionInfo OPTIONAL, +3114 supportedVLR-CAMEL-Phases [5] SupportedCamelPhases OPTIONAL, +3115 supportedSGSN-CAMEL-Phases [6] SupportedCamelPhases OPTIONAL, +3116 extensionContainer [7] ExtensionContainer OPTIONAL, +3117 ... , +3118 offeredCamel4CSIsInVLR [8] OfferedCamel4CSIs OPTIONAL, +3119 offeredCamel4CSIsInSGSN [9] OfferedCamel4CSIs OPTIONAL, +3120 msisdn-BS-List [10] MSISDN-BS-List OPTIONAL, +3121 csg-SubscriptionDataList [11] CSG-SubscriptionDataList OPTIONAL, +3122 cw-Data [12] CallWaitingData OPTIONAL, +3123 ch-Data [13] CallHoldData OPTIONAL, +3124 clip-Data [14] ClipData OPTIONAL, +3125 clir-Data [15] ClirData OPTIONAL, +3126 ect-data [16] EctData OPTIONAL } +3127 +3128 CallWaitingData ::= SEQUENCE { +3129 cwFeatureList [1] Ext-CwFeatureList, +3130 notificationToCSE [2] NULL OPTIONAL, +3131 ... } +3132 +3133 Ext-CwFeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF +3134 Ext-CwFeature +3135 +3136 Ext-CwFeature ::= SEQUENCE { +3137 basicService [1] Ext-BasicServiceCode, +3138 ss-Status [2] Ext-SS-Status, +3139 ... } +3140 +3141 ClipData ::= SEQUENCE { +3142 ss-Status [1] Ext-SS-Status, +3143 overrideCategory [2] OverrideCategory, +3144 notificationToCSE [3] NULL OPTIONAL, +3145 ... } +3146 +3147 ClirData ::= SEQUENCE { +3148 ss-Status [1] Ext-SS-Status, +3149 cliRestrictionOption [2] CliRestrictionOption OPTIONAL, +3150 notificationToCSE [3] NULL OPTIONAL, +3151 ... } +3152 +3153 CallHoldData ::= SEQUENCE { +3154 ss-Status [1] Ext-SS-Status, +3155 notificationToCSE [2] NULL OPTIONAL, +3156 ... } +3157 +3158 EctData ::= SEQUENCE { +3159 ss-Status [1] Ext-SS-Status, +3160 notificationToCSE [2] NULL OPTIONAL, +3161 ... } +3162 + +``` + +``` + +3163 RequestedSubscriptionInfo ::= SEQUENCE { +3164 requestedSS-Info [1] SS-ForBS-Code OPTIONAL, +3165 odb [2] NULL OPTIONAL, +3166 requestedCAMEL-SubscriptionInfo [3] RequestedCAMEL-SubscriptionInfo OPTIONAL, +3167 supportedVLR-CAMEL-Phases [4] NULL OPTIONAL, +3168 supportedSGSN-CAMEL-Phases [5] NULL OPTIONAL, +3169 extensionContainer [6] ExtensionContainer OPTIONAL, +3170 ..., +3171 additionalRequestedCAMEL-SubscriptionInfo +3172 [7] AdditionalRequestedCAMEL-SubscriptionInfo +3173 OPTIONAL, +3174 msisdn-BS-List [8] NULL OPTIONAL, +3175 csg-SubscriptionDataRequested [9] NULL OPTIONAL, +3176 cw-Info [10] NULL OPTIONAL, +3177 clip-Info [11] NULL OPTIONAL, +3178 clir-Info [12] NULL OPTIONAL, +3179 hold-Info [13] NULL OPTIONAL, +3180 ect-Info [14] NULL OPTIONAL } +3181 +3182 MSISDN-BS-List ::= SEQUENCE SIZE (1..maxNumOfMSISDN) OF +3183 MSISDN-BS +3184 +3185 maxNumOfMSISDN INTEGER ::= 50 +3186 +3187 +3188 MSISDN-BS ::= SEQUENCE { +3189 msisdn ISDN-AddressString, +3190 basicServiceList [0] BasicServiceList OPTIONAL, +3191 extensionContainer [1] ExtensionContainer OPTIONAL, +3192 ...} +3193 +3194 RequestedCAMEL-SubscriptionInfo ::= ENUMERATED { +3195 o-CSI (0), +3196 t-CSI (1), +3197 vt-CSI (2), +3198 tif-CSI (3), +3199 gprs-CSI (4), +3200 mo-sms-CSI (5), +3201 ss-CSI (6), +3202 m-CSI (7), +3203 d-csi (8) } +3204 +3205 AdditionalRequestedCAMEL-SubscriptionInfo ::= ENUMERATED { +3206 mt-sms-CSI (0), +3207 mg-csi (1), +3208 o-IM-CSI (2), +3209 d-IM-CSI (3), +3210 vt-IM-CSI (4), +3211 ...} +3212 -- exception handling: unknown values shall be discarded by the receiver. +3213 +3214 CallForwardingData ::= SEQUENCE { +3215 forwardingFeatureList Ext-ForwFeatureList, +3216 notificationToCSE NULL OPTIONAL, +3217 extensionContainer [0] ExtensionContainer OPTIONAL, +3218 ...} +3219 +3220 CallBarringData ::= SEQUENCE { +3221 callBarringFeatureList Ext-CallBarFeatureList, +3222 password Password OPTIONAL, +3223 wrongPasswordAttemptsCounter WrongPasswordAttemptsCounter OPTIONAL, +3224 notificationToCSE NULL OPTIONAL, +3225 extensionContainer ExtensionContainer OPTIONAL, +3226 ...} +3227 +3228 WrongPasswordAttemptsCounter ::= INTEGER (0..4) +3229 +3230 ODB-Info ::= SEQUENCE { +3231 odb-Data ODB-Data, +3232 notificationToCSE NULL OPTIONAL, +3233 extensionContainer ExtensionContainer OPTIONAL, +3234 ...} +3235 + +``` + +``` + +3236 CAMEL-SubscriptionInfo ::= SEQUENCE { +3237 o-CSI [0] O-CSI OPTIONAL, +3238 o-BcsuCamelTDP-CriteriaList [1] O-BcsuCamelTDP-CriteriaList OPTIONAL, +3239 d-CSI [2] D-CSI OPTIONAL, +3240 t-CSI [3] T-CSI OPTIONAL, +3241 t-BCSM-CAMEL-TDP-CriteriaList [4] T-BCSM-CAMEL-TDP-CriteriaList OPTIONAL, +3242 vt-CSI [5] T-CSI OPTIONAL, +3243 vt-BCSM-CAMEL-TDP-CriteriaList [6] T-BCSM-CAMEL-TDP-CriteriaList OPTIONAL, +3244 tif-CSI [7] NULL OPTIONAL, +3245 tif-CSI-NotificationToCSE [8] NULL OPTIONAL, +3246 gprs-CSI [9] GPRS-CSI OPTIONAL, +3247 mo-sms-CSI [10] SMS-CSI OPTIONAL, +3248 ss-CSI [11] SS-CSI OPTIONAL, +3249 m-CSI [12] M-CSI OPTIONAL, +3250 extensionContainer [13] ExtensionContainer OPTIONAL, +3251 ..., +3252 specificCSIDeletedList [14] SpecificCSI-Withdraw OPTIONAL, +3253 mt-sms-CSI [15] SMS-CSI OPTIONAL, +3254 mt-smsCAMELTDP-CriteriaList [16] MT-smsCAMELTDP-CriteriaList OPTIONAL, +3255 mg-CSI [17] MG-CSI OPTIONAL, +3256 o-IM-CSI [18] O-CSI OPTIONAL, +3257 o-IM-BcsuCamelTDP-CriteriaList [19] O-BcsuCamelTDP-CriteriaList OPTIONAL, +3258 d-IM-CSI [20] D-CSI OPTIONAL, +3259 vt-IM-CSI [21] T-CSI OPTIONAL, +3260 vt-IM-BCSM-CAMEL-TDP-CriteriaList [22] T-BCSM-CAMEL-TDP-CriteriaList OPTIONAL +3261 } +3262 +3263 AnyTimeModificationArg ::= SEQUENCE { +3264 subscriberIdentity [0] SubscriberIdentity, +3265 gsmSCF-Address [1] ISDN-AddressString, +3266 modificationRequestFor-CF-Info [2] ModificationRequestFor-CF-Info OPTIONAL, +3267 modificationRequestFor-CB-Info [3] ModificationRequestFor-CB-Info OPTIONAL, +3268 modificationRequestFor-CSI [4] ModificationRequestFor-CSI OPTIONAL, +3269 extensionContainer [5] ExtensionContainer OPTIONAL, +3270 longFTN-Supported [6] NULL OPTIONAL, +3271 ..., +3272 modificationRequestFor-ODB-data [7] ModificationRequestFor-ODB-data OPTIONAL, +3273 modificationRequestFor-IP-SM-GW-Data [8] ModificationRequestFor-IP-SM-GW-Data OPTIONAL, +3274 activationRequestForUE-reachability [9] RequestedServingNode OPTIONAL, +3275 modificationRequestFor-CSG [10] ModificationRequestFor-CSG OPTIONAL, +3276 modificationRequestFor-CW-Data [11] ModificationRequestFor-CW-Info OPTIONAL, +3277 modificationRequestFor-CLIP-Data [12] ModificationRequestFor-CLIP-Info OPTIONAL, +3278 modificationRequestFor-CLIR-Data [13] ModificationRequestFor-CLIR-Info OPTIONAL, +3279 modificationRequestFor-HOLD-Data [14] ModificationRequestFor-CH-Info OPTIONAL, +3280 modificationRequestFor-ECT-Data [15] ModificationRequestFor-ECT-Info OPTIONAL } +3281 +3282 ModificationRequestFor-CW-Info ::= SEQUENCE { +3283 basicService [0] Ext-BasicServiceCode OPTIONAL, +3284 ss-Status [1] Ext-SS-Status OPTIONAL, +3285 modifyNotificationToCSE [2] ModificationInstruction OPTIONAL, +3286 extensionContainer [3] ExtensionContainer OPTIONAL, +3287 ...} +3288 +3289 ModificationRequestFor-CH-Info ::= SEQUENCE { +3290 ss-Status [0] Ext-SS-Status OPTIONAL, +3291 modifyNotificationToCSE [1] ModificationInstruction OPTIONAL, +3292 extensionContainer [2] ExtensionContainer OPTIONAL, +3293 ...} +3294 +3295 ModificationRequestFor-ECT-Info ::= SEQUENCE { +3296 ss-Status [0] Ext-SS-Status OPTIONAL, +3297 modifyNotificationToCSE [1] ModificationInstruction OPTIONAL, +3298 extensionContainer [2] ExtensionContainer OPTIONAL, +3299 ...} +3300 +3301 ModificationRequestFor-CLIR-Info ::= SEQUENCE { +3302 ss-Status [0] Ext-SS-Status OPTIONAL, +3303 cliRestrictionOption [1] CliRestrictionOption OPTIONAL, +3304 modifyNotificationToCSE [2] ModificationInstruction OPTIONAL, +3305 extensionContainer [3] ExtensionContainer OPTIONAL, +3306 ...} +3307 + +``` + +``` + +3308 ModificationRequestFor-CLIP-Info ::= SEQUENCE { +3309 ss-Status [0] Ext-SS-Status OPTIONAL, +3310 overrideCategory [1] OverrideCategory OPTIONAL, +3311 modifyNotificationToCSE [2] ModificationInstruction OPTIONAL, +3312 extensionContainer [3] ExtensionContainer OPTIONAL, +3313 ...} +3314 +3315 +3316 ModificationRequestFor-CSG ::= SEQUENCE { +3317 modifyNotificationToCSE [0] ModificationInstruction OPTIONAL, +3318 extensionContainer [1] ExtensionContainer OPTIONAL, +3319 ...} +3320 +3321 RequestedServingNode ::= BIT STRING { +3322 mmeAndSgsn (0) (SIZE (1..8)) +3323 +3324 ServingNode ::= BIT STRING { +3325 mme (0), +3326 sgsn (1) (SIZE (2..8)) +3327 -- Other bits than listed above shall be discarded. +3328 +3329 AnyTimeModificationRes ::= SEQUENCE { +3330 ss-InfoFor-CSE [0] Ext-SS-InfoFor-CSE OPTIONAL, +3331 camel-SubscriptionInfo [1] CAMEL-SubscriptionInfo OPTIONAL, +3332 extensionContainer [2] ExtensionContainer OPTIONAL, +3333 ..., +3334 odb-Info [3] ODB-Info OPTIONAL, +3335 cw-Data [4] CallWaitingData OPTIONAL, +3336 ch-Data [5] CallHoldData OPTIONAL, +3337 clip-Data [6] ClipData OPTIONAL, +3338 clir-Data [7] ClirData OPTIONAL, +3339 ect-data [8] EctData OPTIONAL, +3340 serviceCentreAddress [9] AddressString OPTIONAL +3341 } +3342 +3343 ModificationRequestFor-CF-Info ::= SEQUENCE { +3344 ss-Code [0] SS-Code, +3345 basicService [1] Ext-BasicServiceCode OPTIONAL, +3346 ss-Status [2] Ext-SS-Status OPTIONAL, +3347 forwardedToNumber [3] AddressString OPTIONAL, +3348 forwardedToSubaddress [4] ISDN-SubaddressString OPTIONAL, +3349 noReplyConditionTime [5] Ext-NoRepCondTime OPTIONAL, +3350 modifyNotificationToCSE [6] ModificationInstruction OPTIONAL, +3351 extensionContainer [7] ExtensionContainer OPTIONAL, +3352 ...} +3353 +3354 ModificationRequestFor-CB-Info ::= SEQUENCE { +3355 ss-Code [0] SS-Code, +3356 basicService [1] Ext-BasicServiceCode OPTIONAL, +3357 ss-Status [2] Ext-SS-Status OPTIONAL, +3358 password [3] Password OPTIONAL, +3359 wrongPasswordAttemptsCounter [4] WrongPasswordAttemptsCounter OPTIONAL, +3360 modifyNotificationToCSE [5] ModificationInstruction OPTIONAL, +3361 extensionContainer [6] ExtensionContainer OPTIONAL, +3362 ...} +3363 +3364 ModificationRequestFor-ODB-data ::= SEQUENCE { +3365 odb-data [0] ODB-Data OPTIONAL, +3366 modifyNotificationToCSE [1] ModificationInstruction OPTIONAL, +3367 extensionContainer [2] ExtensionContainer OPTIONAL, +3368 ...} +3369 +3370 ModificationRequestFor-CSI ::= SEQUENCE { +3371 requestedCamel-SubscriptionInfo [0] RequestedCAMEL-SubscriptionInfo, +3372 modifyNotificationToCSE [1] ModificationInstruction OPTIONAL, +3373 modifyCSI-State [2] ModificationInstruction OPTIONAL, +3374 extensionContainer [3] ExtensionContainer OPTIONAL, +3375 ..., +3376 additionalRequestedCAMEL-SubscriptionInfo +3377 [4] AdditionalRequestedCAMEL-SubscriptionInfo +3378 OPTIONAL } +3379 -- requestedCamel-SubscriptionInfo shall be discarded if +3380 -- additionalRequestedCAMEL-SubscriptionInfo is received +3381 + +``` + +``` + +3382 ModificationRequestFor-IP-SM-GW-Data ::= SEQUENCE { +3383 modifyRegistrationStatus [0] ModificationInstruction OPTIONAL, +3384 extensionContainer [1] ExtensionContainer OPTIONAL, +3385 ..., +3386 ip-sm-gw-DiameterAddress [2] NetworkNodeDiameterAddress OPTIONAL +3387 -- ip-sm-gw-DiameterAddress may be present when ModificationInstruction is "activate" +3388 } +3389 +3390 ModificationInstruction ::= ENUMERATED { +3391 deactivate (0), +3392 activate (1)} +3393 +3394 -- subscriber data modification notification types +3395 +3396 NoteSubscriberDataModifiedArg ::= SEQUENCE { +3397 imsi IMSI, +3398 msisdn ISDN-AddressString, +3399 forwardingInfoFor-CSE [0] Ext-ForwardingInfoFor-CSE OPTIONAL, +3400 callBarringInfoFor-CSE [1] Ext-CallBarringInfoFor-CSE OPTIONAL, +3401 odb-Info [2] ODB-Info OPTIONAL, +3402 camel-SubscriptionInfo [3] CAMEL-SubscriptionInfo OPTIONAL, +3403 allInformationSent [4] NULL OPTIONAL, +3404 extensionContainer ExtensionContainer OPTIONAL, +3405 ..., +3406 ue-reachable [5] ServingNode OPTIONAL, +3407 csg-SubscriptionDataList [6] CSG-SubscriptionDataList OPTIONAL, +3408 cw-Data [7] CallWaitingData OPTIONAL, +3409 ch-Data [8] CallHoldData OPTIONAL, +3410 clip-Data [9] ClipData OPTIONAL, +3411 clir-Data [10] ClirData OPTIONAL, +3412 ect-data [11] EctData OPTIONAL } +3413 +3414 NoteSubscriberDataModifiedRes ::= SEQUENCE { +3415 extensionContainer ExtensionContainer OPTIONAL, +3416 ...} +3417 +3418 -- mobility management event notification info types +3419 +3420 NoteMM-EventArg ::= SEQUENCE { +3421 serviceKey ServiceKey, +3422 eventMet [0] MM-Code, +3423 imsi [1] IMSI, +3424 msisdn [2] ISDN-AddressString, +3425 locationInformation [3] LocationInformation OPTIONAL, +3426 supportedCAMELPhases [5] SupportedCamelPhases OPTIONAL, +3427 extensionContainer [6] ExtensionContainer OPTIONAL, +3428 ..., +3429 locationInformationGPRS [7] LocationInformationGPRS OPTIONAL, +3430 offeredCamel4Functionalities [8] OfferedCamel4Functionalities OPTIONAL +3431 } +3432 +3433 NoteMM-EventRes ::= SEQUENCE { +3434 extensionContainer ExtensionContainer OPTIONAL, +3435 ...} +3436 +3437 Ext-SS-InfoFor-CSE ::= CHOICE { +3438 forwardingInfoFor-CSE [0] Ext-ForwardingInfoFor-CSE, +3439 callBarringInfoFor-CSE [1] Ext-CallBarringInfoFor-CSE +3440 } +3441 +3442 Ext-ForwardingInfoFor-CSE ::= SEQUENCE { +3443 ss-Code [0] SS-Code, +3444 forwardingFeatureList [1] Ext-ForwFeatureList, +3445 notificationToCSE [2] NULL OPTIONAL, +3446 extensionContainer [3] ExtensionContainer OPTIONAL, +3447 ...} +3448 +3449 Ext-CallBarringInfoFor-CSE ::= SEQUENCE { +3450 ss-Code [0] SS-Code, +3451 callBarringFeatureList [1] Ext-CallBarFeatureList, +3452 password [2] Password OPTIONAL, +3453 wrongPasswordAttemptsCounter [3] WrongPasswordAttemptsCounter OPTIONAL, +3454 notificationToCSE [4] NULL OPTIONAL, +3455 extensionContainer [5] ExtensionContainer OPTIONAL, +3456 ...} +3457 + +``` + +3458 -- vcsg location registration types + +3459 **UpdateVcsgLocationArg** ::= SEQUENCE { +3460     imsi IMSI, +3461     msisdn [2] ISDN-AddressString OPTIONAL, +3462     vlr-Number [0] ISDN-AddressString OPTIONAL, +3463     sgsn-Number [1] ISDN-AddressString OPTIONAL, +3464     extensionContainer ExtensionContainer OPTIONAL, +3465     ... } + +3466 +3467 **UpdateVcsgLocationRes** ::= SEQUENCE { +3468     temporaryEmptySubscriptiondataIndicator NULL OPTIONAL, +3469     extensionContainer ExtensionContainer OPTIONAL, +3470     ... } + +3471 +3472 **CancelVcsgLocationArg** ::= SEQUENCE { +3473     identity Identity, +3474     extensionContainer ExtensionContainer OPTIONAL, +3475     ... +3476 } + +3477 +3478 **CancelVcsgLocationRes** ::= SEQUENCE { +3479     extensionContainer ExtensionContainer OPTIONAL, +3480     ... } + +3481 +3482 +3483 +3484 END + +## 3485 17.7.2 Operation and maintenance data types + +3486 **MAP-OM-DataTypes** { +3487     itu-t identified-organization (4) etsi (0) mobileDomain (0) +3488     gsm-Network (1) modules (3) map-OM-DataTypes (12) version21 (21)} + +3489 +3490 DEFINITIONS + +3491 +3492 IMPLICIT TAGS + +3493 +3494 ::= + +3495 +3496 BEGIN + +3497 +3498 EXPORTS + +3499     ActivateTraceModeArg, +3500     ActivateTraceModeRes, +3501     DeactivateTraceModeArg, +3502     DeactivateTraceModeRes, +3503     TracePropagationList +3504 ; + +3505 +3506 IMPORTS + +3507     AddressString, +3508     IMSI, +3509     GSN-Address, +3510     GlobalCellId, +3511     E-UTRAN-CGI, +3512     TA-Id, +3513     RAIdentity, +3514     LAIFixedLength, +3515     PLMN-Id + +3516 FROM MAP-CommonDataTypes { +3517     itu-t identified-organization (4) etsi (0) mobileDomain (0) +3518     gsm-Network (1) modules (3) map-CommonDataTypes (18) version21 (21)} + +3519 +3520     ExtensionContainer + +3521 FROM MAP-ExtensionDataTypes { +3522     itu-t identified-organization (4) etsi (0) mobileDomain (0) +3523     gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version21 (21)} + +3524 +3525 ; + +3526 + +``` + +3527 ActivateTraceModeArg ::= SEQUENCE { +3528 imsi [0] IMSI OPTIONAL, +3529 traceReference [1] TraceReference, +3530 traceType [2] TraceType, +3531 omc-Id [3] AddressString OPTIONAL, +3532 extensionContainer [4] ExtensionContainer OPTIONAL, +3533 ..., +3534 traceReference2 [5] TraceReference2 OPTIONAL, +3535 traceDepthList [6] TraceDepthList OPTIONAL, +3536 traceNE-TypeList [7] TraceNE-TypeList OPTIONAL, +3537 traceInterfaceList [8] TraceInterfaceList OPTIONAL, +3538 traceEventList [9] TraceEventList OPTIONAL, +3539 traceCollectionEntity [10] GSN-Address OPTIONAL, +3540 mdt-Configuration [11] MDT-Configuration OPTIONAL +3541 } +3542 +3543 MDT-Configuration ::= SEQUENCE { +3544 jobType JobType, +3545 areaScope AreaScope OPTIONAL, +3546 listOfMeasurements ListOfMeasurements OPTIONAL, +3547 reportingTrigger [0] ReportingTrigger OPTIONAL, +3548 reportInterval ReportInterval OPTIONAL, +3549 reportAmount [1] ReportAmount OPTIONAL, +3550 eventThresholdRSRP EventThresholdRSRP OPTIONAL, +3551 eventThresholdRSRQ [2] EventThresholdRSRQ OPTIONAL, +3552 loggingInterval [3] LoggingInterval OPTIONAL, +3553 loggingDuration [4] LoggingDuration OPTIONAL, +3554 extensionContainer [5] ExtensionContainer OPTIONAL, +3555 ..., +3556 measurementPeriodUMTS [6] PeriodUMTS OPTIONAL, +3557 measurementPeriodLTE [7] PeriodLTE OPTIONAL, +3558 collectionPeriodRRM-UMTS [8] PeriodUMTS OPTIONAL, +3559 collectionPeriodRRM-LTE [9] PeriodLTE OPTIONAL, +3560 positioningMethod [10] PositioningMethod OPTIONAL, +3561 measurementQuantity [11] MeasurementQuantity OPTIONAL, +3562 eventThreshold1F [12] EventThreshold1F OPTIONAL, +3563 eventThreshold1I [13] EventThreshold1I OPTIONAL, +3564 mdt-Allowed-PLMN-List [14] MDT-Allowed-PLMNId-List OPTIONAL } +3565 +3566 MDT-Allowed-PLMNId-List ::= SEQUENCE SIZE (1..16) OF +3567 PLMN-Id +3568 PeriodUMTS ::= ENUMERATED { +3569 d250ms (0), +3570 d500ms (1), +3571 d1000ms (2), +3572 d2000ms (3), +3573 d3000ms (4), +3574 d4000ms (5), +3575 d6000ms (6), +3576 d8000ms (7), +3577 d12000ms (8), +3578 d16000ms (9), +3579 d20000ms (10), +3580 d24000ms (11), +3581 d28000ms (12), +3582 d32000ms (13), +3583 d64000ms (14) } +3584 +3585 PeriodLTE ::= ENUMERATED { +3586 d1024ms (0), +3587 d1280ms (1), +3588 d2048ms (2), +3589 d2560ms (3), +3590 d5120ms (4), +3591 d10240ms (5), +3592 d1min (6) } +3593 +3594 PositioningMethod ::= OCTET STRING (SIZE (1)) +3595 -- Octet is coded as described in 3GPP TS 32.422 [132]. +3596 +3597 MeasurementQuantity ::= OCTET STRING (SIZE (1)) +3598 -- Octet is coded as described in 3GPP TS 32.422 [132]. +3599 +3600 EventThreshold1F ::= INTEGER +3601 (-120..165) +3602 + +``` + +``` + +3603 EventThresholdII := INTEGER +3604 (-120..-25) +3605 +3606 JobType := ENUMERATED { +3607 immediate-MDT-only (0), +3608 logged-MDT-only (1), +3609 trace-only (2), +3610 immediate-MDT-and-trace (3)} +3611 +3612 AreaScope := SEQUENCE { +3613 cgi-List [0] CGI-List OPTIONAL, +3614 e-utran-cgi-List [1] E-UTRAN-CGI-List OPTIONAL, +3615 routingAreaId-List [2] RoutingAreaId-List OPTIONAL, +3616 locationAreaId-List [3] LocationAreaId-List OPTIONAL, +3617 trackingAreaId-List [4] TrackingAreaId-List OPTIONAL, +3618 extensionContainer [5] ExtensionContainer OPTIONAL, +3619 ... } +3620 +3621 CGI-List := SEQUENCE SIZE (1..32) OF +3622 GlobalCellId +3623 +3624 E-UTRAN-CGI-List := SEQUENCE SIZE (1..32) OF +3625 E-UTRAN-CGI +3626 +3627 RoutingAreaId-List := SEQUENCE SIZE (1..8) OF +3628 RAIdentity +3629 +3630 LocationAreaId-List := SEQUENCE SIZE (1..8) OF +3631 LAIFixedLength +3632 +3633 TrackingAreaId-List := SEQUENCE SIZE (1..8) OF +3634 TA-Id +3635 +3636 ListOfMeasurements := OCTET STRING (SIZE (4)) +3637 -- Octets are coded as described in 3GPP TS 32.422. +3638 +3639 ReportingTrigger := OCTET STRING (SIZE (1)) +3640 -- Octet is coded as described in 3GPP TS 32.422. +3641 +3642 ReportInterval := ENUMERATED { +3643 umts250ms (0), +3644 umts500ms (1), +3645 umts1000ms (2), +3646 umts2000ms (3), +3647 umts3000ms (4), +3648 umts4000ms (5), +3649 umts6000ms (6), +3650 umts8000ms (7), +3651 umts12000ms (8), +3652 umts16000ms (9), +3653 umts20000ms (10), +3654 umts24000ms (11), +3655 umts28000ms (12), +3656 umts32000ms (13), +3657 umts64000ms (14), +3658 lte120ms (15), +3659 lte240ms (16), +3660 lte480ms (17), +3661 lte640ms (18), +3662 lte1024ms (19), +3663 lte2048ms (20), +3664 lte5120ms (21), +3665 lte10240ms (22), +3666 lte1min (23), +3667 lte6min (24), +3668 lte12min (25), +3669 lte30min (26), +3670 lte60min (27)} +3671 +3672 + +``` + +``` + +3673 ReportAmount ::= ENUMERATED { +3674 d1 (0), +3675 d2 (1), +3676 d4 (2), +3677 d8 (3), +3678 d16 (4), +3679 d32 (5), +3680 d64 (6), +3681 infinity (7) } +3682 +3683 EventThresholdRSRP ::= INTEGER +3684 (0..97) +3685 +3686 EventThresholdRSRQ ::= INTEGER +3687 (0..34) +3688 +3689 LoggingInterval ::= ENUMERATED { +3690 d1dot28 (0), +3691 d2dot56 (1), +3692 d5dot12 (2), +3693 d10dot24 (3), +3694 d20dot48 (4), +3695 d30dot72 (5), +3696 d40dot96 (6), +3697 d61dot44 (7) } +3698 +3699 LoggingDuration ::= ENUMERATED { +3700 d600sec (0), +3701 d1200sec (1), +3702 d2400sec (2), +3703 d3600sec (3), +3704 d5400sec (4), +3705 d7200sec (5) } +3706 +3707 TraceReference ::= OCTET STRING (SIZE (1..2)) +3708 +3709 TraceReference2 ::= OCTET STRING (SIZE (3)) +3710 +3711 TraceRecordingSessionReference ::= OCTET STRING (SIZE (2)) +3712 +3713 TraceType ::= INTEGER +3714 (0..255) +3715 -- Trace types are fully defined in 3GPP TS 52.008. [61] +3716 +3717 TraceDepthList ::= SEQUENCE { +3718 msc-s-TraceDepth [0] TraceDepth OPTIONAL, +3719 mgw-TraceDepth [1] TraceDepth OPTIONAL, +3720 sgsn-TraceDepth [2] TraceDepth OPTIONAL, +3721 ggsn-TraceDepth [3] TraceDepth OPTIONAL, +3722 rnc-TraceDepth [4] TraceDepth OPTIONAL, +3723 bmsc-TraceDepth [5] TraceDepth OPTIONAL, +3724 ... , +3725 mme-TraceDepth [6] TraceDepth OPTIONAL, +3726 sgw-TraceDepth [7] TraceDepth OPTIONAL, +3727 pgw-TraceDepth [8] TraceDepth OPTIONAL, +3728 eNB-TraceDepth [9] TraceDepth OPTIONAL, +3729 msc-s-TraceDepthExtension [10] TraceDepthExtension OPTIONAL, +3730 mgw-TraceDepthExtension [11] TraceDepthExtension OPTIONAL, +3731 sgsn-TraceDepthExtension [12] TraceDepthExtension OPTIONAL, +3732 ggsn-TraceDepthExtension [13] TraceDepthExtension OPTIONAL, +3733 rnc-TraceDepthExtension [14] TraceDepthExtension OPTIONAL, +3734 bmsc-TraceDepthExtension [15] TraceDepthExtension OPTIONAL, +3735 mme-TraceDepthExtension [16] TraceDepthExtension OPTIONAL, +3736 sgw-TraceDepthExtension [17] TraceDepthExtension OPTIONAL, +3737 pgw-TraceDepthExtension [18] TraceDepthExtension OPTIONAL, +3738 eNB-TraceDepthExtension [19] TraceDepthExtension OPTIONAL } +3739 +3740 -- If one of the TraceDepthExtension types is sent, the corresponding TraceDepth type +3741 -- shall also be sent with the same enumeration value to allow the receiver not supporting +3742 -- the Extension to fall back to the non extended type. +3743 -- If one of the TraceDepthExtension types is received and supported, the corresponding +3744 -- TraceDepth type shall be ignored. +3745 + +``` + +``` +3746 TraceDepth ::= ENUMERATED { +3747 minimum (0), +3748 medium (1), +3749 maximum (2), +3750 ...} +3751 -- The value medium is applicable only for RNC. For other network elements, if value medium +3752 -- is received, value minimum shall be applied. +``` + +``` +3753 +3754 TraceDepthExtension ::= ENUMERATED { +3755 minimumWithoutVendorSpecificExtension (0), +3756 mediumWithoutVendorSpecificExtension (1), +3757 maximumWithoutVendorSpecificExtension (2), +3758 ...} +3759 -- The value mediumWithoutVendorSpecificExtension is applicable only for RNC. For other +3760 -- network elements, if value mediumWithoutVendorSpecificExtension is received, value +3761 -- minimumWithoutVendorSpecificExtension shall be applied. +``` + +``` +3762 +3763 TraceNE-TypeList ::= BIT STRING { +3764 msc-s (0), +3765 mgw (1), +3766 sgsn (2), +3767 ggsn (3), +3768 rnc (4), +3769 bm-sc (5) , +3770 mme (6), +3771 sgw (7), +3772 pgw (8), +3773 eNB (9)} (SIZE (6..16)) +3774 -- Other bits than listed above shall be discarded. +``` + +``` +3775 +3776 TraceInterfaceList ::= SEQUENCE { +3777 msc-s-List [0] MSC-S-InterfaceList OPTIONAL, +3778 mgw-List [1] MGW-InterfaceList OPTIONAL, +3779 sgsn-List [2] SGSN-InterfaceList OPTIONAL, +3780 ggsn-List [3] GGSN-InterfaceList OPTIONAL, +3781 rnc-List [4] RNC-InterfaceList OPTIONAL, +3782 bmsc-List [5] BMSC-InterfaceList OPTIONAL, +3783 ..., +3784 mme-List [6] MME-InterfaceList OPTIONAL, +3785 sgw-List [7] SGW-InterfaceList OPTIONAL, +3786 pgw-List [8] PGW-InterfaceList OPTIONAL, +3787 eNB-List [9] ENB-InterfaceList OPTIONAL} +``` + +``` +3788 +3789 MSC-S-InterfaceList ::= BIT STRING { +3790 a (0), +3791 iu (1), +3792 mc (2), +3793 map-g (3), +3794 map-b (4), +3795 map-e (5), +3796 map-f (6), +3797 cap (7), +3798 map-d (8), +3799 map-c (9)} (SIZE (10..16)) +3800 -- Other bits than listed above shall be discarded. +``` + +``` +3801 +3802 MGW-InterfaceList ::= BIT STRING { +3803 mc (0), +3804 nb-up (1), +3805 iu-up (2)} (SIZE (3..8)) +3806 -- Other bits than listed above shall be discarded. +``` + +``` +3807 +3808 SGSN-InterfaceList ::= BIT STRING { +3809 gb (0), +3810 iu (1), +3811 gn (2), +3812 map-gr (3), +3813 map-gd (4), +3814 map-gf (5), +3815 gs (6), +3816 ge (7), +3817 s3 (8), +3818 s4 (9), +3819 s6d (10)} (SIZE (8..16)) +3820 -- Other bits than listed above shall be discarded. +``` + +``` +3821 +``` + +``` + +3822 GGSN-InterfaceList ::= BIT STRING { +3823 gn (0), +3824 gi (1), +3825 gmb (2)} (SIZE (3..8)) +3826 -- Other bits than listed above shall be discarded. +3827 +3828 RNC-InterfaceList ::= BIT STRING { +3829 iu (0), +3830 iur (1), +3831 iub (2), +3832 uu (3)} (SIZE (4..8)) +3833 -- Other bits than listed above shall be discarded. +3834 +3835 BMSC-InterfaceList ::= BIT STRING { +3836 gmb (0)} (SIZE (1..8)) +3837 -- Other bits than listed above shall be discarded. +3838 +3839 MME-InterfaceList ::= BIT STRING { +3840 s1-mme (0), +3841 s3 (1), +3842 s6a (2), +3843 s10 (3), +3844 s11 (4)} (SIZE (5..8)) +3845 -- Other bits than listed above shall be discarded. +3846 +3847 SGW-InterfaceList ::= BIT STRING { +3848 s4 (0), +3849 s5 (1), +3850 s8b (2), +3851 s11 (3), +3852 gxc (4)} (SIZE (5..8)) +3853 -- Other bits than listed above shall be discarded. +3854 +3855 PGW-InterfaceList ::= BIT STRING { +3856 s2a (0), +3857 s2b (1), +3858 s2c (2), +3859 s5 (3), +3860 s6b (4), +3861 gx (5), +3862 s8b (6), +3863 sgi (7)} (SIZE (8..16)) +3864 -- Other bits than listed above shall be discarded. +3865 +3866 ENB-InterfaceList ::= BIT STRING { +3867 s1-mme (0), +3868 x2 (1), +3869 uu (2)} (SIZE (3..8)) +3870 -- Other bits than listed above shall be discarded. +3871 +3872 TraceEventList ::= SEQUENCE { +3873 msc-s-List [0] MSC-S-EventList OPTIONAL, +3874 mgw-List [1] MGW-EventList OPTIONAL, +3875 sgsn-List [2] SGSN-EventList OPTIONAL, +3876 ggsn-List [3] GGSN-EventList OPTIONAL, +3877 bmsc-List [4] BMSC-EventList OPTIONAL, +3878 ..., +3879 mme-List [5] MME-EventList OPTIONAL, +3880 sgw-List [6] SGW-EventList OPTIONAL, +3881 pgw-List [7] PGW-EventList OPTIONAL} +3882 +3883 MSC-S-EventList ::= BIT STRING { +3884 mo-mtCall (0), +3885 mo-mt-sms (1), +3886 lu-imsiAttach-imsiDetach (2), +3887 handovers (3), +3888 ss (4)} (SIZE (5..16)) +3889 -- Other bits than listed above shall be discarded. +3890 +3891 MGW-EventList ::= BIT STRING { +3892 context (0)} (SIZE (1..8)) +3893 -- Other bits than listed above shall be discarded. +3894 + +``` + +``` + +3895 SGSN-EventList ::= BIT STRING { +3896 pdpContext (0), +3897 mo-mt-sms (1), +3898 rau-gprsAttach-gprsDetach (2), +3899 mbmsContext (3)} (SIZE (4..16)) +3900 -- Other bits than listed above shall be discarded. +3901 +3902 GGSN-EventList ::= BIT STRING { +3903 pdpContext (0), +3904 mbmsContext (1)} (SIZE (2..8)) +3905 -- Other bits than listed above shall be discarded. +3906 +3907 BMSC-EventList ::= BIT STRING { +3908 mbmsMulticastServiceActivation (0)} (SIZE (1..8)) +3909 -- Other bits than listed above shall be discarded. +3910 +3911 MME-EventList ::= BIT STRING { +3912 ue-initiatedPDNconnectivityRequest (0), +3913 serviceRequestts (1), +3914 initialAttachTrackingAreaUpdateDetach (2), +3915 ue-initiatedPDNdisconnection (3), +3916 bearerActivationModificationDeletion (4), +3917 handover (5)} (SIZE (6..8)) +3918 -- Other bits than listed above shall be discarded. +3919 +3920 SGW-EventList ::= BIT STRING { +3921 pdn-connectionCreation (0), +3922 pdn-connectionTermination (1), +3923 bearerActivationModificationDeletion (2)} (SIZE (3..8)) +3924 -- Other bits than listed above shall be discarded. +3925 +3926 PGW-EventList ::= BIT STRING { +3927 pdn-connectionCreation (0), +3928 pdn-connectionTermination (1), +3929 bearerActivationModificationDeletion (2)} (SIZE (3..8)) +3930 -- Other bits than listed above shall be discarded. +3931 +3932 TracePropagationList ::= SEQUENCE { +3933 traceReference [0] TraceReference OPTIONAL, +3934 traceType [1] TraceType OPTIONAL, +3935 traceReference2 [2] TraceReference2 OPTIONAL, +3936 traceRecordingSessionReference [3] TraceRecordingSessionReference OPTIONAL, +3937 rnc-TraceDepth [4] TraceDepth OPTIONAL, +3938 rnc-InterfaceList [5] RNC-InterfaceList OPTIONAL, +3939 msc-s-TraceDepth [6] TraceDepth OPTIONAL, +3940 msc-s-InterfaceList [7] MSC-S-InterfaceList OPTIONAL, +3941 msc-s-EventList [8] MSC-S-EventList OPTIONAL, +3942 mgw-TraceDepth [9] TraceDepth OPTIONAL, +3943 mgw-InterfaceList [10] MGW-InterfaceList OPTIONAL, +3944 mgw-EventList [11] MGW-EventList OPTIONAL, +3945 ..., +3946 rnc-TraceDepthExtension [12] TraceDepthExtension OPTIONAL, +3947 msc-s-TraceDepthExtension [13] TraceDepthExtension OPTIONAL, +3948 mgw-TraceDepthExtension [14] TraceDepthExtension OPTIONAL +3949 } +3950 -- If one of the TraceDepthExtension types is sent, the corresponding TraceDepth type +3951 -- shall also be sent with the same enumeration value to allow the receiver not supporting +3952 -- the Extension to fall back to the non extended type. +3953 -- If one of the TraceDepthExtension types is received and supported, the corresponding +3954 -- TraceDepth type shall be ignored. +3955 +3956 ActivateTraceModeRes ::= SEQUENCE { +3957 extensionContainer [0] ExtensionContainer OPTIONAL, +3958 ..., +3959 traceSupportIndicator [1] NULL OPTIONAL +3960 } +3961 +3962 DeactivateTraceModeArg ::= SEQUENCE { +3963 imsi [0] IMSI OPTIONAL, +3964 traceReference [1] TraceReference, +3965 extensionContainer [2] ExtensionContainer OPTIONAL, +3966 ..., +3967 traceReference2 [3] TraceReference2 OPTIONAL +3968 } +3969 + +``` + +``` + +3970 DeactivateTraceModeRes ::= SEQUENCE { +3971 extensionContainer [0] ExtensionContainer OPTIONAL, +3972 ...} +3973 +3974 END + +``` + +## 3975 17.7.3 Call handling data types + +``` + +3976 MAP-CH-DataTypes { +3977 itu-t identified-organization (4) etsi (0) mobileDomain (0) +3978 gsm-Network (1) modules (3) map-CH-DataTypes (13) version21 (21)} +3979 +3980 DEFINITIONS +3981 +3982 IMPLICIT TAGS +3983 +3984 ::= +3985 +3986 BEGIN +3987 +3988 EXPORTS +3989 SendRoutingInfoArg, +3990 SendRoutingInfoRes, +3991 ProvideRoamingNumberArg, +3992 ProvideRoamingNumberRes, +3993 ResumeCallHandlingArg, +3994 ResumeCallHandlingRes, +3995 NumberOfForwarding, +3996 SuppressionOfAnnouncement, +3997 CallReferenceNumber, +3998 SetReportingStateArg, +3999 SetReportingStateRes, +4000 StatusReportArg, +4001 StatusReportRes, +4002 RemoteUserFreeArg, +4003 RemoteUserFreeRes, +4004 IST-AlertArg, +4005 IST-AlertRes, +4006 IST-CommandArg, +4007 IST-CommandRes, +4008 UU-Data, +4009 ReleaseResourcesArg, +4010 ReleaseResourcesRes +4011 ; +4012 +4013 IMPORTS +4014 SubscriberInfo, +4015 SupportedCamelPhases, +4016 OfferedCamel4CSIs, +4017 CUG-Interlock, +4018 O-CSI, +4019 D-CSI, +4020 O-BcsmCamelTDPCriteriaList, +4021 T-BCSM-CAMEL-TDP-CriteriaList, +4022 IST-SupportIndicator, +4023 IST-AlertTimerValue, +4024 T-CSI, +4025 NumberPortabilityStatus, +4026 PagingArea +4027 FROM MAP-MS-DataTypes { +4028 itu-t identified-organization (4) etsi (0) mobileDomain (0) +4029 gsm-Network (1) modules (3) map-MS-DataTypes (11) version21 (21)} +4030 +4031 ForwardingOptions, +4032 SS-List, +4033 CCBS-Feature +4034 FROM MAP-SS-DataTypes { +4035 itu-t identified-organization (4) etsi (0) mobileDomain (0) +4036 gsm-Network (1) modules (3) map-SS-DataTypes (14) version21 (21)} +4037 +4038 ISDN-AddressString, +4039 ISDN-SubaddressString, +4040 FTN-AddressString, +4041 ExternalSignalInfo, +4042 Ext-ExternalSignalInfo, +4043 IMSI, +4044 LMSI, +4045 Ext-BasicServiceCode, + +``` + +``` + +4046 AlertingPattern, +4047 NAEA-PreferredCI, +4048 EMLPP-Priority, +4049 PLMN-Id +4050 FROM MAP-CommonDataTypes { +4051 itu-t identified-organization (4) etsi (0) mobileDomain (0) +4052 gsm-Network (1) modules (3) map-CommonDataTypes (18) version21 (21)} +4053 +4054 ExtensionContainer +4055 FROM MAP-ExtensionDataTypes { +4056 itu-t identified-organization (4) etsi (0) mobileDomain (0) +4057 gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version21 (21)} +4058 ; +4059 +4060 +4061 CUG-CheckInfo ::= SEQUENCE { +4062 cug-Interlock CUG-Interlock, +4063 cug-OutgoingAccess NULL OPTIONAL, +4064 extensionContainer ExtensionContainer OPTIONAL, +4065 ...} +4066 +4067 NumberOfForwarding ::= INTEGER (1..5) +4068 +4069 SendRoutingInfoArg ::= SEQUENCE { +4070 msisdn [0] ISDN-AddressString, +4071 cug-CheckInfo [1] CUG-CheckInfo OPTIONAL, +4072 numberOfForwarding [2] NumberOfForwarding OPTIONAL, +4073 interrogationType [3] InterrogationType, +4074 or-Interrogation [4] NULL OPTIONAL, +4075 or-Capability [5] OR-Phase OPTIONAL, +4076 gmsc-OrGsmSCF-Address [6] ISDN-AddressString, +4077 callReferenceNumber [7] CallReferenceNumber OPTIONAL, +4078 forwardingReason [8] ForwardingReason OPTIONAL, +4079 basicServiceGroup [9] Ext-BasicServiceCode OPTIONAL, +4080 networkSignalInfo [10] ExternalSignalInfo OPTIONAL, +4081 camelInfo [11] CamelInfo OPTIONAL, +4082 suppressionOfAnnouncement [12] SuppressionOfAnnouncement OPTIONAL, +4083 extensionContainer [13] ExtensionContainer OPTIONAL, +4084 ..., +4085 alertingPattern [14] AlertingPattern OPTIONAL, +4086 ccbs-Call [15] NULL OPTIONAL, +4087 supportedCCBS-Phase [16] SupportedCCBS-Phase OPTIONAL, +4088 additionalSignalInfo [17] Ext-ExternalSignalInfo OPTIONAL, +4089 istSupportIndicator [18] IST-SupportIndicator OPTIONAL, +4090 pre-pagingSupported [19] NULL OPTIONAL, +4091 callDiversionTreatmentIndicator [20] CallDiversionTreatmentIndicator OPTIONAL, +4092 longFTN-Supported [21] NULL OPTIONAL, +4093 suppress-VT-CSI [22] NULL OPTIONAL, +4094 suppressIncomingCallBarring [23] NULL OPTIONAL, +4095 gsmSCF-InitiatedCall [24] NULL OPTIONAL, +4096 basicServiceGroup2 [25] Ext-BasicServiceCode OPTIONAL, +4097 networkSignalInfo2 [26] ExternalSignalInfo OPTIONAL, +4098 suppressMTSS [27] SuppressMTSS OPTIONAL, +4099 mtRoamingRetrySupported [28] NULL OPTIONAL, +4100 callPriority [29] EMLPP-Priority OPTIONAL +4101 } +4102 +4103 SuppressionOfAnnouncement ::= NULL +4104 +4105 SuppressMTSS ::= BIT STRING { +4106 suppressCUG (0), +4107 suppressCCBS (1) } (SIZE (2..16)) +4108 -- Other bits than listed above shall be discarded +4109 +4110 InterrogationType ::= ENUMERATED { +4111 basicCall (0), +4112 forwarding (1)} +4113 +4114 OR-Phase ::= INTEGER (1..127) +4115 +4116 CallReferenceNumber ::= OCTET STRING (SIZE (1..8)) +4117 +4118 ForwardingReason ::= ENUMERATED { +4119 notReachable (0), +4120 busy (1), +4121 noReply (2)} +4122 + +``` + +``` + +4123 SupportedCCBS-Phase ::= INTEGER (1..127) +4124 -- exception handling: +4125 -- Only value 1 is used. +4126 -- Values in the ranges 2-127 are reserved for future use. +4127 -- If received values 2-127 shall be mapped on to value 1. +4128 +4129 CallDiversionTreatmentIndicator ::= OCTET STRING (SIZE(1)) +4130 -- callDiversionAllowed (xxxx xx01) +4131 -- callDiversionNotAllowed (xxxx xx10) +4132 -- network default is call diversion allowed +4133 +4134 SendRoutingInfoRes ::= [3] SEQUENCE { +4135 imsi [9] IMSI OPTIONAL, +4136 -- IMSI must be present if SendRoutingInfoRes is not segmented. +4137 -- If the TC-Result-NL segmentation option is taken the IMSI must be +4138 -- present in one segmented transmission of SendRoutingInfoRes. +4139 extendedRoutingInfo ExtendedRoutingInfo OPTIONAL, +4140 cug-CheckInfo [3] CUG-CheckInfo OPTIONAL, +4141 cugSubscriptionFlag [6] NULL OPTIONAL, +4142 subscriberInfo [7] SubscriberInfo OPTIONAL, +4143 ss-List [1] SS-List OPTIONAL, +4144 basicService [5] Ext-BasicServiceCode OPTIONAL, +4145 forwardingInterrogationRequired [4] NULL OPTIONAL, +4146 vmsc-Address [2] ISDN-AddressString OPTIONAL, +4147 extensionContainer [0] ExtensionContainer OPTIONAL, +4148 ... , +4149 naea-PreferredCI [10] NAEA-PreferredCI OPTIONAL, +4150 -- naea-PreferredCI is included at the discretion of the HLR operator. +4151 ccbs-Indicators [11] CCBS-Indicators OPTIONAL, +4152 msisdn [12] ISDN-AddressString OPTIONAL, +4153 numberPortabilityStatus [13] NumberPortabilityStatus OPTIONAL, +4154 istAlertTimer [14] IST-AlertTimerValue OPTIONAL, +4155 supportedCamelPhasesInVMSC [15] SupportedCamelPhases OPTIONAL, +4156 offeredCamel4CSIsInVMSC [16] OfferedCamel4CSIs OPTIONAL, +4157 routingInfo2 [17] RoutingInfo OPTIONAL, +4158 ss-List2 [18] SS-List OPTIONAL, +4159 basicService2 [19] Ext-BasicServiceCode OPTIONAL, +4160 allowedServices [20] AllowedServices OPTIONAL, +4161 unavailabilityCause [21] UnavailabilityCause OPTIONAL, +4162 releaseResourcesSupported [22] NULL OPTIONAL, +4163 gsm-BearerCapability [23] ExternalSignalInfo OPTIONAL +4164 } +4165 +4166 AllowedServices ::= BIT STRING { +4167 firstServiceAllowed (0), +4168 secondServiceAllowed (1) } (SIZE (2..8)) +4169 -- firstService is the service indicated in the networkSignalInfo +4170 -- secondService is the service indicated in the networkSignalInfo2 +4171 -- Other bits than listed above shall be discarded +4172 +4173 UnavailabilityCause ::= ENUMERATED { +4174 bearerServiceNotProvisioned (1), +4175 teleserviceNotProvisioned (2), +4176 absentSubscriber (3), +4177 busySubscriber (4), +4178 callBarred (5), +4179 cug-Reject (6), +4180 ...} +4181 -- exception handling: +4182 -- Reception of other values than the ones listed shall result in the service +4183 -- being unavailable for that call. +4184 +4185 CCBS-Indicators ::= SEQUENCE { +4186 ccbs-Possible [0] NULL OPTIONAL, +4187 keepCCBS-CallIndicator [1] NULL OPTIONAL, +4188 extensionContainer [2] ExtensionContainer OPTIONAL, +4189 ...} +4190 +4191 RoutingInfo ::= CHOICE { +4192 roamingNumber ISDN-AddressString, +4193 forwardingData ForwardingData} +4194 + +``` + +``` + +4195 ForwardingData ::= SEQUENCE { +4196 forwardedToNumber [5] ISDN-AddressString OPTIONAL, +4197 -- When this datatype is sent from an HLR which supports CAMEL Phase 2 +4198 -- to a GMSC which supports CAMEL Phase 2 the GMSC shall not check the +4199 -- format of the number +4200 forwardedToSubaddress [4] ISDN-SubaddressString OPTIONAL, +4201 forwardingOptions [6] ForwardingOptions OPTIONAL, +4202 extensionContainer [7] ExtensionContainer OPTIONAL, +4203 ..., +4204 longForwardedToNumber [8] FTN-AddressString OPTIONAL} +4205 +4206 ProvideRoamingNumberArg ::= SEQUENCE { +4207 imsi [0] IMSI, +4208 msc-Number [1] ISDN-AddressString, +4209 msisdn [2] ISDN-AddressString OPTIONAL, +4210 lmsi [4] LMSI OPTIONAL, +4211 gsm-BearerCapability [5] ExternalSignalInfo OPTIONAL, +4212 networkSignalInfo [6] ExternalSignalInfo OPTIONAL, +4213 suppressionOfAnnouncement [7] SuppressionOfAnnouncement OPTIONAL, +4214 gmsc-Address [8] ISDN-AddressString OPTIONAL, +4215 callReferenceNumber [9] CallReferenceNumber OPTIONAL, +4216 or-Interrogation [10] NULL OPTIONAL, +4217 extensionContainer [11] ExtensionContainer OPTIONAL, +4218 ... , +4219 alertingPattern [12] AlertingPattern OPTIONAL, +4220 ccbs-Call [13] NULL OPTIONAL, +4221 supportedCamelPhasesInInterrogatingNode [15] SupportedCamelPhases OPTIONAL, +4222 additionalSignalInfo [14] Ext-ExternalSignalInfo OPTIONAL, +4223 orNotSupportedInGMSC [16] NULL OPTIONAL, +4224 pre-pagingSupported [17] NULL OPTIONAL, +4225 longFTN-Supported [18] NULL OPTIONAL, +4226 suppress-VT-CSI [19] NULL OPTIONAL, +4227 offeredCamel4CSIsInInterrogatingNode [20] OfferedCamel4CSIs OPTIONAL, +4228 mtRoamingRetrySupported [21] NULL OPTIONAL, +4229 pagingArea [22] PagingArea OPTIONAL, +4230 callPriority [23] EMLPP-Priority OPTIONAL, +4231 mtrf-Indicator [24] NULL OPTIONAL, +4232 oldMSC-Number [25] ISDN-AddressString OPTIONAL, +4233 lastUsedLtePLMN-Id [26] PLMN-Id OPTIONAL +4234 } +4235 +4236 ProvideRoamingNumberRes ::= SEQUENCE { +4237 roamingNumber ISDN-AddressString, +4238 extensionContainer ExtensionContainer OPTIONAL, +4239 ..., +4240 releaseResourcesSupported NULL OPTIONAL, +4241 vmsc-Address ISDN-AddressString OPTIONAL } +4242 +4243 ResumeCallHandlingArg ::= SEQUENCE { +4244 callReferenceNumber [0] CallReferenceNumber OPTIONAL, +4245 basicServiceGroup [1] Ext-BasicServiceCode OPTIONAL, +4246 forwardingData [2] ForwardingData OPTIONAL, +4247 imsi [3] IMSI OPTIONAL, +4248 cug-CheckInfo [4] CUG-CheckInfo OPTIONAL, +4249 o-CSI [5] O-CSI OPTIONAL, +4250 extensionContainer [7] ExtensionContainer OPTIONAL, +4251 ccbs-Possible [8] NULL OPTIONAL, +4252 msisdn [9] ISDN-AddressString OPTIONAL, +4253 uu-Data [10] UU-Data OPTIONAL, +4254 allInformationSent [11] NULL OPTIONAL, +4255 ..., +4256 d-csi [12] D-CSI OPTIONAL, +4257 o-BcsuCamelTDPCriteriaList [13] O-BcsuCamelTDPCriteriaList OPTIONAL, +4258 basicServiceGroup2 [14] Ext-BasicServiceCode OPTIONAL, +4259 mtRoamingRetry [15] NULL OPTIONAL +4260 } +4261 +4262 UU-Data ::= SEQUENCE { +4263 uuIndicator [0] UUIndicator OPTIONAL, +4264 uui [1] UUI OPTIONAL, +4265 uusCFInteraction [2] NULL OPTIONAL, +4266 extensionContainer [3] ExtensionContainer OPTIONAL, +4267 ...} +4268 +4269 UUIndicator ::= OCTET STRING (SIZE (1)) +4270 -- Octets are coded according to ETS 300 356 +4271 +4272 UUI ::= OCTET STRING (SIZE (1..131)) + +``` + +``` + +4273 -- Octets are coded according to ETS 300 356 +4274 +4275 ResumeCallHandlingRes ::= SEQUENCE { +4276 extensionContainer ExtensionContainer OPTIONAL, +4277 ... } +4278 +4279 CamelInfo ::= SEQUENCE { +4280 supportedCamelPhases SupportedCamelPhases, +4281 suppress-T-CSI NULL OPTIONAL, +4282 extensionContainer ExtensionContainer OPTIONAL, +4283 ... , +4284 offeredCamel4CSIs [0] OfferedCamel4CSIs OPTIONAL } +4285 +4286 ExtendedRoutingInfo ::= CHOICE { +4287 routingInfo RoutingInfo, +4288 camelRoutingInfo [8] CamelRoutingInfo} +4289 +4290 CamelRoutingInfo ::= SEQUENCE { +4291 forwardingData ForwardingData OPTIONAL, +4292 gmscCamelSubscriptionInfo [0] GmscCamelSubscriptionInfo, +4293 extensionContainer [1] ExtensionContainer OPTIONAL, +4294 ... } +4295 +4296 GmscCamelSubscriptionInfo ::= SEQUENCE { +4297 t-CSI [0] T-CSI OPTIONAL, +4298 o-CSI [1] O-CSI OPTIONAL, +4299 extensionContainer [2] ExtensionContainer OPTIONAL, +4300 ... , +4301 o-BcsmCamelTDP-CriteriaList [3] O-BcsmCamelTDP-CriteriaList OPTIONAL, +4302 t-BCSM-CAMEL-TDP-CriteriaList [4] T-BCSM-CAMEL-TDP-CriteriaList OPTIONAL, +4303 d-csi [5] D-CSI OPTIONAL} +4304 +4305 SetReportingStateArg ::= SEQUENCE { +4306 imsi [0] IMSI OPTIONAL, +4307 lmsi [1] LMSI OPTIONAL, +4308 ccbs-Monitoring [2] ReportingState OPTIONAL, +4309 extensionContainer [3] ExtensionContainer OPTIONAL, +4310 ... } +4311 +4312 ReportingState ::= ENUMERATED { +4313 stopMonitoring (0), +4314 startMonitoring (1), +4315 ... } +4316 -- exception handling: +4317 -- reception of values 2-10 shall be mapped to 'stopMonitoring' +4318 -- reception of values > 10 shall be mapped to 'startMonitoring' +4319 +4320 SetReportingStateRes ::= SEQUENCE{ +4321 ccbs-SubscriberStatus [0] CCBS-SubscriberStatus OPTIONAL, +4322 extensionContainer [1] ExtensionContainer OPTIONAL, +4323 ... } +4324 +4325 CCBS-SubscriberStatus ::= ENUMERATED { +4326 ccbsNotIdle (0), +4327 ccbsIdle (1), +4328 ccbsNotReachable (2), +4329 ... } +4330 -- exception handling: +4331 -- reception of values 3-10 shall be mapped to 'ccbsNotIdle' +4332 -- reception of values 11-20 shall be mapped to 'ccbsIdle' +4333 -- reception of values > 20 shall be mapped to 'ccbsNotReachable' +4334 +4335 StatusReportArg ::= SEQUENCE{ +4336 imsi [0] IMSI, +4337 eventReportData [1] EventReportData OPTIONAL, +4338 callReportdata [2] CallReportData OPTIONAL, +4339 extensionContainer [3] ExtensionContainer OPTIONAL, +4340 ... } +4341 +4342 EventReportData ::= SEQUENCE{ +4343 ccbs-SubscriberStatus [0] CCBS-SubscriberStatus OPTIONAL, +4344 extensionContainer [1] ExtensionContainer OPTIONAL, +4345 ... } +4346 + +``` + +``` + +4347 CallReportData ::= SEQUENCE{ +4348 monitoringMode [0] MonitoringMode OPTIONAL, +4349 callOutcome [1] CallOutcome OPTIONAL, +4350 extensionContainer [2] ExtensionContainer OPTIONAL, +4351 ...} +4352 +4353 MonitoringMode ::= ENUMERATED { +4354 a-side (0), +4355 b-side (1), +4356 ...} +4357 -- exception handling: +4358 -- reception of values 2-10 shall be mapped 'a-side' +4359 -- reception of values > 10 shall be mapped to 'b-side' +4360 +4361 CallOutcome ::= ENUMERATED { +4362 success (0), +4363 failure (1), +4364 busy (2), +4365 ...} +4366 -- exception handling: +4367 -- reception of values 3-10 shall be mapped to 'success' +4368 -- reception of values 11-20 shall be mapped to 'failure' +4369 -- reception of values > 20 shall be mapped to 'busy' +4370 +4371 StatusReportRes ::= SEQUENCE { +4372 extensionContainer [0] ExtensionContainer OPTIONAL, +4373 ...} +4374 +4375 RemoteUserFreeArg ::= SEQUENCE{ +4376 imsi [0] IMSI, +4377 callInfo [1] ExternalSignalInfo, +4378 ccbs-Feature [2] CCBS-Feature, +4379 translatedB-Number [3] ISDN-AddressString, +4380 replaceB-Number [4] NULL OPTIONAL, +4381 alertingPattern [5] AlertingPattern OPTIONAL, +4382 extensionContainer [6] ExtensionContainer OPTIONAL, +4383 ...} +4384 +4385 RemoteUserFreeRes ::= SEQUENCE{ +4386 ruf-Outcome [0] RUF-Outcome, +4387 extensionContainer [1] ExtensionContainer OPTIONAL, +4388 ...} +4389 +4390 RUF-Outcome ::= ENUMERATED{ +4391 accepted (0), +4392 rejected (1), +4393 noResponseFromFreeMS (2), -- T4 Expiry +4394 noResponseFromBusyMS (3), -- T10 Expiry +4395 udubFromFreeMS (4), +4396 udubFromBusyMS (5), +4397 ...} +4398 -- exception handling: +4399 -- reception of values 6-20 shall be mapped to 'accepted' +4400 -- reception of values 21-30 shall be mapped to 'rejected' +4401 -- reception of values 31-40 shall be mapped to 'noResponseFromFreeMS' +4402 -- reception of values 41-50 shall be mapped to 'noResponseFromBusyMS' +4403 -- reception of values 51-60 shall be mapped to 'udubFromFreeMS' +4404 -- reception of values > 60 shall be mapped to 'udubFromBusyMS' +4405 +4406 IST-AlertArg ::= SEQUENCE{ +4407 imsi [0] IMSI, +4408 extensionContainer [1] ExtensionContainer OPTIONAL, +4409 ...} +4410 +4411 IST-AlertRes ::= SEQUENCE{ +4412 istAlertTimer [0] IST-AlertTimerValue OPTIONAL, +4413 istInformationWithdraw [1] NULL OPTIONAL, +4414 callTerminationIndicator [2] CallTerminationIndicator OPTIONAL, +4415 extensionContainer [3] ExtensionContainer OPTIONAL, +4416 ...} +4417 +4418 IST-CommandArg ::= SEQUENCE{ +4419 imsi [0] IMSI, +4420 extensionContainer [1] ExtensionContainer OPTIONAL, +4421 ...} +4422 + +``` + +``` + +4423 IST-CommandRes ::= SEQUENCE{ +4424 extensionContainer ExtensionContainer OPTIONAL, +4425 ...} +4426 +4427 CallTerminationIndicator ::= ENUMERATED { +4428 terminateCallActivityReferred (0), +4429 terminateAllCallActivities (1), +4430 ...} +4431 -- exception handling: +4432 -- reception of values 2-10 shall be mapped to ' terminateCallActivityReferred ' +4433 -- reception of values > 10 shall be mapped to ' terminateAllCallActivities ' +4434 +4435 -- In MSCs not supporting linkage of all call activities, any value received shall +4436 -- be interpreted as ' terminateCallActivityReferred ' +4437 +4438 ReleaseResourcesArg ::= SEQUENCE{ +4439 msrn ISDN-AddressString, +4440 extensionContainer ExtensionContainer OPTIONAL, +4441 ...} +4442 +4443 ReleaseResourcesRes ::= SEQUENCE{ +4444 extensionContainer ExtensionContainer OPTIONAL, +4445 ...} +4446 +4447 +4448 END + +``` + +## 4449 17.7.4 Supplementary service data types + +``` + +4450 MAP-SS-DataTypes { +4451 itu-t identified-organization (4) etsi (0) mobileDomain (0) +4452 gsm-Network (1) modules (3) map-SS-DataTypes (14) version21 (21)} +4453 +4454 DEFINITIONS +4455 +4456 IMPLICIT TAGS +4457 +4458 ::= +4459 +4460 BEGIN +4461 +4462 EXPORTS +4463 RegisterSS-Arg, +4464 SS-Info, +4465 SS-Status, +4466 SS-SubscriptionOption, +4467 SS-ForBS-Code, +4468 InterrogateSS-Res, +4469 USSD-Arg, +4470 USSD-Res, +4471 USSD-DataCodingScheme, +4472 USSD-String, +4473 Password, +4474 GuidanceInfo, +4475 SS-List, +4476 SS-InfoList, +4477 OverrideCategory, +4478 CliRestrictionOption, +4479 NoReplyConditionTime, +4480 ForwardingOptions, +4481 maxNumOfSS, +4482 SS-Data, +4483 SS-InvocationNotificationArg, +4484 SS-InvocationNotificationRes, +4485 CCBS-Feature, +4486 RegisterCC-EntryArg, +4487 RegisterCC-EntryRes, +4488 EraseCC-EntryArg, +4489 EraseCC-EntryRes +4490 ; +4491 +4492 IMPORTS +4493 AddressString, +4494 ISDN-AddressString, +4495 ISDN-SubaddressString, +4496 FTN-AddressString, +4497 IMSI, +4498 BasicServiceCode, + +``` + +``` + +4499 AlertingPattern, +4500 EMLPP-Priority, +4501 MaxMC-Bearers, +4502 MC-Bearers, +4503 ExternalSignalInfo +4504 FROM MAP-CommonDataTypes { +4505 itu-t identified-organization (4) etsi (0) mobileDomain (0) +4506 gsm-Network (1) modules (3) map-CommonDataTypes (18) version21 (21)} +4507 +4508 ExtensionContainer +4509 FROM MAP-ExtensionDataTypes { +4510 itu-t identified-organization (4) etsi (0) mobileDomain (0) +4511 gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version21 (21)} +4512 +4513 SS-Code +4514 FROM MAP-SS-Code { +4515 itu-t identified-organization (4) etsi (0) mobileDomain (0) +4516 gsm-Network (1) modules (3) map-SS-Code (15) version21 (21)} +4517 ; + +``` + +``` + +4518 +4519 +4520 RegisterSS-Arg ::= SEQUENCE { +4521 ss-Code SS-Code, +4522 basicService BasicServiceCode OPTIONAL, +4523 forwardedToNumber [4] AddressString OPTIONAL, +4524 forwardedToSubaddress [6] ISDN-SubaddressString OPTIONAL, +4525 noReplyConditionTime [5] NoReplyConditionTime OPTIONAL, +4526 ..., +4527 defaultPriority [7] EMLPP-Priority OPTIONAL, +4528 nbrUser [8] MC-Bearers OPTIONAL, +4529 longFTN-Supported [9] NULL OPTIONAL } + +``` + +``` + +4530 +4531 NoReplyConditionTime ::= INTEGER (5..30) + +``` + +``` + +4532 +4533 SS-Info ::= CHOICE { +4534 forwardingInfo [0] ForwardingInfo, +4535 callBarringInfo [1] CallBarringInfo, +4536 ss-Data [3] SS-Data} + +``` + +``` + +4537 +4538 ForwardingInfo ::= SEQUENCE { +4539 ss-Code SS-Code OPTIONAL, +4540 forwardingFeatureList ForwardingFeatureList, +4541 ...} + +``` + +``` + +4542 +4543 ForwardingFeatureList ::= +4544 SEQUENCE SIZE (1..maxNumOfBasicServiceGroups) OF +4545 ForwardingFeature + +``` + +``` + +4546 +4547 ForwardingFeature ::= SEQUENCE { +4548 basicService BasicServiceCode OPTIONAL, +4549 ss-Status [4] SS-Status OPTIONAL, +4550 forwardedToNumber [5] ISDN-AddressString OPTIONAL, +4551 forwardedToSubaddress [8] ISDN-SubaddressString OPTIONAL, +4552 forwardingOptions [6] ForwardingOptions OPTIONAL, +4553 noReplyConditionTime [7] NoReplyConditionTime OPTIONAL, +4554 ..., +4555 longForwardedToNumber [9] FTN-AddressString OPTIONAL } + +``` + +``` + +4556 +4557 SS-Status ::= OCTET STRING (SIZE (1)) +4558 +4559 -- bits 8765: 0000 (unused) +4560 -- bits 4321: Used to convey the "P bit", "R bit", "A bit" and "Q bit", +4561 -- representing supplementary service state information +4562 -- as defined in TS 3GPP TS 23.011 [22] +4563 +4564 -- bit 4: "Q bit" +4565 +4566 -- bit 3: "P bit" +4567 +4568 -- bit 2: "R bit" +4569 +4570 -- bit 1: "A bit" + +``` + +``` + +4571 + +``` + +``` + +4572 ForwardingOptions ::= OCTET STRING (SIZE (1)) +4573 +4574 -- bit 8: notification to forwarding party +4575 -- 0 no notification +4576 -- 1 notification +4577 +4578 -- bit 7: redirecting presentation +4579 -- 0 no presentation +4580 -- 1 presentation +4581 +4582 -- bit 6: notification to calling party +4583 -- 0 no notification +4584 -- 1 notification +4585 +4586 -- bit 5: 0 (unused) +4587 +4588 -- bits 43: forwarding reason +4589 -- 00 ms not reachable +4590 -- 01 ms busy +4591 -- 10 no reply +4592 -- 11 unconditional when used in a SRI Result, +4593 -- or call deflection when used in a RCH Argument +4594 -- bits 21: 00 (unused) +4595 +4596 CallBarringInfo ::= SEQUENCE { +4597 ss-Code SS-Code OPTIONAL, +4598 callBarringFeatureList CallBarringFeatureList, +4599 ...} +4600 +4601 CallBarringFeatureList ::= SEQUENCE SIZE (1..maxNumOfBasicServiceGroups) OF +4602 CallBarringFeature +4603 +4604 CallBarringFeature ::= SEQUENCE { +4605 basicService BasicServiceCode OPTIONAL, +4606 ss-Status [4] SS-Status OPTIONAL, +4607 ...} +4608 +4609 SS-Data ::= SEQUENCE { +4610 ss-Code SS-Code OPTIONAL, +4611 ss-Status [4] SS-Status OPTIONAL, +4612 ss-SubscriptionOption SS-SubscriptionOption OPTIONAL, +4613 basicServiceGroupList BasicServiceGroupList OPTIONAL, +4614 ..., +4615 defaultPriority EMLPP-Priority OPTIONAL, +4616 nbrUser [5] MC-Bearers OPTIONAL +4617 } +4618 +4619 SS-SubscriptionOption ::= CHOICE { +4620 cliRestrictionOption [2] CliRestrictionOption, +4621 overrideCategory [1] OverrideCategory} +4622 +4623 CliRestrictionOption ::= ENUMERATED { +4624 permanent (0), +4625 temporaryDefaultRestricted (1), +4626 temporaryDefaultAllowed (2)} +4627 +4628 OverrideCategory ::= ENUMERATED { +4629 overrideEnabled (0), +4630 overrideDisabled (1)} +4631 +4632 SS-ForBS-Code ::= SEQUENCE { +4633 ss-Code SS-Code, +4634 basicService BasicServiceCode OPTIONAL, +4635 ..., +4636 longFTN-Supported [4] NULL OPTIONAL } +4637 +4638 GenericServiceInfo ::= SEQUENCE { +4639 ss-Status SS-Status, +4640 cliRestrictionOption CliRestrictionOption OPTIONAL, +4641 ..., +4642 maximumEntitledPriority [0] EMLPP-Priority OPTIONAL, +4643 defaultPriority [1] EMLPP-Priority OPTIONAL, +4644 ccbs-FeatureList [2] CCBS-FeatureList OPTIONAL, +4645 nbrSB [3] MaxMC-Bearers OPTIONAL, +4646 nbrUser [4] MC-Bearers OPTIONAL, +4647 nbrSN [5] MC-Bearers OPTIONAL } +4648 + +``` + +``` + +4649 CCBS-FeatureList := SEQUENCE SIZE (1..maxNumOfCCBS-Requests) OF +4650 CCBS-Feature +4651 +4652 maxNumOfCCBS-Requests INTEGER := 5 +4653 +4654 CCBS-Feature := SEQUENCE { +4655 ccbs-Index [0] CCBS-Index OPTIONAL, +4656 b-subscriberNumber [1] ISDN-AddressString OPTIONAL, +4657 b-subscriberSubaddress [2] ISDN-SubaddressString OPTIONAL, +4658 basicServiceGroup [3] BasicServiceCode OPTIONAL, +4659 ... } +4660 +4661 CCBS-Index := INTEGER (1..maxNumOfCCBS-Requests) +4662 +4663 InterrogateSS-Res := CHOICE { +4664 ss-Status [0] SS-Status, +4665 basicServiceGroupList [2] BasicServiceGroupList, +4666 forwardingFeatureList [3] ForwardingFeatureList, +4667 genericServiceInfo [4] GenericServiceInfo } +4668 +4669 USSD-Arg := SEQUENCE { +4670 ussd-DataCodingScheme USSD-DataCodingScheme, +4671 ussd-String USSD-String, +4672 ... , +4673 alertingPattern AlertingPattern OPTIONAL, +4674 msisdn [0] ISDN-AddressString OPTIONAL } +4675 +4676 USSD-Res := SEQUENCE { +4677 ussd-DataCodingScheme USSD-DataCodingScheme, +4678 ussd-String USSD-String, +4679 ... } +4680 +4681 USSD-DataCodingScheme := OCTET STRING (SIZE (1)) +4682 -- The structure of the USSD-DataCodingScheme is defined by +4683 -- the Cell Broadcast Data Coding Scheme as described in +4684 -- TS 3GPP TS 23.038 [25] +4685 +4686 USSD-String := OCTET STRING (SIZE (1..maxUSSD-StringLength)) +4687 -- The structure of the contents of the USSD-String is dependent +4688 -- on the USSD-DataCodingScheme as described in TS 3GPP TS 23.038 [25]. +4689 +4690 maxUSSD-StringLength INTEGER := 160 +4691 +4692 Password := NumericString +4693 (FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9")) +4694 (SIZE (4)) +4695 +4696 GuidanceInfo := ENUMERATED { +4697 enterPW (0), +4698 enterNewPW (1), +4699 enterNewPW-Again (2) } +4700 -- How this information is really delivered to the subscriber +4701 -- (display, announcement, ...) is not part of this +4702 -- specification. +4703 +4704 SS-List := SEQUENCE SIZE (1..maxNumOfSS) OF +4705 SS-Code +4706 +4707 maxNumOfSS INTEGER := 30 +4708 +4709 SS-InfoList := SEQUENCE SIZE (1..maxNumOfSS) OF +4710 SS-Info +4711 +4712 BasicServiceGroupList := SEQUENCE SIZE (1..maxNumOfBasicServiceGroups) OF +4713 BasicServiceCode +4714 +4715 maxNumOfBasicServiceGroups INTEGER := 13 +4716 + +``` + +``` + +4717 SS-InvocationNotificationArg ::= SEQUENCE { +4718 imsi [0] IMSI, +4719 msisdn [1] ISDN-AddressString, +4720 ss-Event [2] SS-Code, +4721 -- The following SS-Code values are allowed : +4722 -- ect SS-Code ::= '00110001'B +4723 -- multiPTY SS-Code ::= '01010001'B +4724 -- cd SS-Code ::= '00100100'B +4725 -- ccbs SS-Code ::= '01000100'B +4726 ss-EventSpecification [3] SS-EventSpecification OPTIONAL, +4727 extensionContainer [4] ExtensionContainer OPTIONAL, +4728 ..., +4729 b-subscriberNumber [5] ISDN-AddressString OPTIONAL, +4730 ccbs-RequestState [6] CCBS-RequestState OPTIONAL +4731 } +4732 +4733 CCBS-RequestState ::= ENUMERATED { +4734 request (0), +4735 recall (1), +4736 active (2), +4737 completed (3), +4738 suspended (4), +4739 frozen (5), +4740 deleted (6) +4741 } +4742 +4743 SS-InvocationNotificationRes ::= SEQUENCE { +4744 extensionContainer ExtensionContainer OPTIONAL, +4745 ... +4746 } +4747 +4748 SS-EventSpecification ::= SEQUENCE SIZE (1..maxEventSpecification) OF +4749 AddressString +4750 +4751 maxEventSpecification INTEGER ::= 2 +4752 +4753 RegisterCC-EntryArg ::= SEQUENCE { +4754 ss-Code [0] SS-Code, +4755 ccbs-Data [1] CCBS-Data OPTIONAL, +4756 ...} +4757 +4758 CCBS-Data ::= SEQUENCE { +4759 ccbs-Feature [0] CCBS-Feature, +4760 translatedB-Number [1] ISDN-AddressString, +4761 serviceIndicator [2] ServiceIndicator OPTIONAL, +4762 callInfo [3] ExternalSignalInfo, +4763 networkSignalInfo [4] ExternalSignalInfo, +4764 ...} +4765 +4766 ServiceIndicator ::= BIT STRING { +4767 clir-invoked (0), +4768 camel-invoked (1)} (SIZE(2..32)) +4769 -- exception handling: +4770 -- bits 2 to 31 shall be ignored if received and not understood +4771 +4772 RegisterCC-EntryRes ::= SEQUENCE { +4773 ccbs-Feature [0] CCBS-Feature OPTIONAL, +4774 ...} +4775 +4776 EraseCC-EntryArg ::= SEQUENCE { +4777 ss-Code [0] SS-Code, +4778 ccbs-Index [1] CCBS-Index OPTIONAL, +4779 ...} +4780 +4781 EraseCC-EntryRes ::= SEQUENCE { +4782 ss-Code [0] SS-Code, +4783 ss-Status [1] SS-Status OPTIONAL, +4784 ...} +4785 +4786 END + +``` + +## 4787 17.7.5 Supplementary service codes + +``` + +4788 MAP-SS-Code { +4789 itu-t identified-organization (4) etsi (0) mobileDomain (0) +4790 gsm-Network (1) modules (3) map-SS-Code (15) version21 (21)} +4791 + +``` + +4792 DEFINITIONS + +4793 + +4794 ::= + +4795 + +4796 BEGIN + +4797 + +4798 **SS-Code** ::= OCTET STRING (SIZE (1)) + +4799 -- This type is used to represent the code identifying a single + +4800 -- supplementary service, a group of supplementary services, or + +4801 -- all supplementary services. The services and abbreviations + +4802 -- used are defined in TS 3GPP TS 22.004 [5]. The internal structure is + +4803 -- defined as follows: + +4804 -- + +4805 -- bits 87654321: group (bits 8765), and specific service + +4806 -- (bits 4321) + +4807 + +4808 **allSS** SS-Code ::= '00000000'B + +4809 -- reserved for possible future use + +4810 -- all SS + +4811 + +4812 **allLineIdentificationSS** SS-Code ::= '00010000'B + +4813 -- reserved for possible future use + +4814 -- all line identification SS + +4815 **clip** SS-Code ::= '00010001'B + +4816 -- calling line identification presentation + +4817 **clir** SS-Code ::= '00010010'B + +4818 -- calling line identification restriction + +4819 **colp** SS-Code ::= '00010011'B + +4820 -- connected line identification presentation + +4821 **colr** SS-Code ::= '00010100'B + +4822 -- connected line identification restriction + +4823 **mci** SS-Code ::= '00010101'B + +4824 -- reserved for possible future use + +4825 -- malicious call identification + +4826 + +4827 **allNameIdentificationSS** SS-Code ::= '00011000'B + +4828 -- all name identification SS + +4829 **cnap** SS-Code ::= '00011001'B + +4830 -- calling name presentation + +4831 + +4832 -- SS-Codes '00011010'B to '00011111'B are reserved for future + +4833 -- NameIdentification Supplementary Service use. + +4834 + +4835 **allForwardingSS** SS-Code ::= '00100000'B + +4836 -- all forwarding SS + +4837 **cfu** SS-Code ::= '00100001'B + +4838 -- call forwarding unconditional + +4839 **allCondForwardingSS** SS-Code ::= '00101000'B + +4840 -- all conditional forwarding SS + +4841 **cfb** SS-Code ::= '00101001'B + +4842 -- call forwarding on mobile subscriber busy + +4843 **cfnry** SS-Code ::= '00101010'B + +4844 -- call forwarding on no reply + +4845 **cfnrc** SS-Code ::= '00101011'B + +4846 -- call forwarding on mobile subscriber not reachable + +4847 **cd** SS-Code ::= '00100100'B + +4848 -- call deflection + +4849 + +4850 **allCallOfferingSS** SS-Code ::= '00110000'B + +4851 -- reserved for possible future use + +4852 -- all call offering SS includes also all forwarding SS + +4853 **ect** SS-Code ::= '00110001'B + +4854 -- explicit call transfer + +4855 **mah** SS-Code ::= '00110010'B + +4856 -- reserved for possible future use + +4857 -- mobile access hunting + +4858 + +``` + +4859 allCallCompletionSS SS-Code ::= '01000000'B +4860 -- reserved for possible future use +4861 -- all Call completion SS +4862 cw SS-Code ::= '01000001'B +4863 -- call waiting +4864 hold SS-Code ::= '01000010'B +4865 -- call hold +4866 ccbs-A SS-Code ::= '01000011'B +4867 -- completion of call to busy subscribers, originating side +4868 -- this SS-Code is used only in InsertSubscriberData, DeleteSubscriberData +4869 -- and InterrogateSS +4870 ccbs-B SS-Code ::= '01000100'B +4871 -- completion of call to busy subscribers, destination side +4872 -- this SS-Code is used only in InsertSubscriberData and DeleteSubscriberData +4873 mc SS-Code ::= '01000101'B +4874 -- multicall +4875 +4876 allMultiPartySS SS-Code ::= '01010000'B +4877 -- reserved for possible future use +4878 -- all multiparty SS +4879 multiPTY SS-Code ::= '01010001'B +4880 -- multiparty +4881 +4882 allCommunityOfInterest-SS SS-Code ::= '01100000'B +4883 -- reserved for possible future use +4884 -- all community of interest SS +4885 cug SS-Code ::= '01100001'B +4886 -- closed user group +4887 +4888 allChargingSS SS-Code ::= '01110000'B +4889 -- reserved for possible future use +4890 -- all charging SS +4891 aoci SS-Code ::= '01110001'B +4892 -- advice of charge information +4893 aocc SS-Code ::= '01110010'B +4894 -- advice of charge charging +4895 +4896 allAdditionalInfoTransferSS SS-Code ::= '10000000'B +4897 -- reserved for possible future use +4898 -- all additional information transfer SS +4899 uus1 SS-Code ::= '10000001'B +4900 -- UUS1 user-to-user signalling +4901 uus2 SS-Code ::= '10000010'B +4902 -- UUS2 user-to-user signalling +4903 uus3 SS-Code ::= '10000011'B +4904 -- UUS3 user-to-user signalling +4905 +4906 allBarringSS SS-Code ::= '10010000'B +4907 -- all barring SS +4908 barringOfOutgoingCalls SS-Code ::= '10010001'B +4909 -- barring of outgoing calls +4910 baoc SS-Code ::= '10010010'B +4911 -- barring of all outgoing calls +4912 boic SS-Code ::= '10010011'B +4913 -- barring of outgoing international calls +4914 boicExHC SS-Code ::= '10010100'B +4915 -- barring of outgoing international calls except those directed +4916 -- to the home PLMN Country +4917 barringOfIncomingCalls SS-Code ::= '10011001'B +4918 -- barring of incoming calls +4919 baic SS-Code ::= '10011010'B +4920 -- barring of all incoming calls +4921 bicRoam SS-Code ::= '10011011'B +4922 -- barring of incoming calls when roaming outside home PLMN +4923 -- Country +4924 + +``` + +``` + +4925 allPLMN-specificSS SS-Code ::= '11110000'B +4926 plmn-specificSS-1 SS-Code ::= '11110001'B +4927 plmn-specificSS-2 SS-Code ::= '11110010'B +4928 plmn-specificSS-3 SS-Code ::= '11110011'B +4929 plmn-specificSS-4 SS-Code ::= '11110100'B +4930 plmn-specificSS-5 SS-Code ::= '11110101'B +4931 plmn-specificSS-6 SS-Code ::= '11110110'B +4932 plmn-specificSS-7 SS-Code ::= '11110111'B +4933 plmn-specificSS-8 SS-Code ::= '11111000'B +4934 plmn-specificSS-9 SS-Code ::= '11111001'B +4935 plmn-specificSS-A SS-Code ::= '11111010'B +4936 plmn-specificSS-B SS-Code ::= '11111011'B +4937 plmn-specificSS-C SS-Code ::= '11111100'B +4938 plmn-specificSS-D SS-Code ::= '11111101'B +4939 plmn-specificSS-E SS-Code ::= '11111110'B +4940 plmn-specificSS-F SS-Code ::= '11111111'B +4941 +4942 allCallPrioritySS SS-Code ::= '10100000'B +4943 -- reserved for possible future use +4944 -- all call priority SS +4945 emlpp SS-Code ::= '10100001'B +4946 -- enhanced Multilevel Precedence Pre-emption (EMLPP) service +4947 +4948 allLCSPrivacyException SS-Code ::= '10110000'B +4949 -- all LCS Privacy Exception Classes +4950 universal SS-Code ::= '10110001'B +4951 -- allow location by any LCS client +4952 callSessionRelated SS-Code ::= '10110010'B +4953 -- allow location by any value added LCS client to which a call/session +4954 -- is established from the target MS +4955 callSessionUnrelated SS-Code ::= '10110011'B +4956 -- allow location by designated external value added LCS clients +4957 plmnoperator SS-Code ::= '10110100'B +4958 -- allow location by designated PLMN operator LCS clients +4959 serviceType SS-Code ::= '10110101'B +4960 -- allow location by LCS clients of a designated LCS service type +4961 +4962 allMOLR-SS SS-Code ::= '11000000'B +4963 -- all Mobile Originating Location Request Classes +4964 basicSelfLocation SS-Code ::= '11000001'B +4965 -- allow an MS to request its own location +4966 autonomousSelfLocation SS-Code ::= '11000010'B +4967 -- allow an MS to perform self location without interaction +4968 -- with the PLMN for a predetermined period of time +4969 transferToThirdParty SS-Code ::= '11000011'B +4970 -- allow an MS to request transfer of its location to another LCS client +4971 +4972 END + +``` + +## 4973 17.7.6 Short message data types + +``` + +4974 MAP-SM-DataTypes { +4975 itu-t identified-organization (4) etsi (0) mobileDomain (0) +4976 gsm-Network (1) modules (3) map-SM-DataTypes (16) version21 (21)} +4977 +4978 DEFINITIONS +4979 +4980 IMPLICIT TAGS +4981 +4982 ::= +4983 +4984 BEGIN +4985 +4986 EXPORTS +4987 RoutingInfoForSM-Arg, +4988 RoutingInfoForSM-Res, +4989 MO-ForwardSM-Arg, +4990 MO-ForwardSM-Res, +4991 MT-ForwardSM-Arg, +4992 MT-ForwardSM-Res, +4993 ReportSM-DeliveryStatusArg, +4994 ReportSM-DeliveryStatusRes, +4995 AlertServiceCentreArg, +4996 InformServiceCentreArg, +4997 ReadyForSM-Arg, +4998 ReadyForSM-Res, +4999 SM-DeliveryOutcome, +5000 AlertReason, + +``` + +``` + +5001 Additional-Number, +5002 MT-ForwardSM-VGCS-Arg, +5003 MT-ForwardSM-VGCS-Res +5004 ; +5005 +5006 IMPORTS +5007 AddressString, +5008 ISDN-AddressString, +5009 SignalInfo, +5010 IMSI, +5011 LMSI, +5012 ASCII-CallReference, +5013 Time, +5014 NetworkNodeDiameterAddress, +5015 HLR-Id +5016 +5017 FROM MAP-CommonDataTypes { +5018 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5019 gsm-Network (1) modules (3) map-CommonDataTypes (18) version21 (21)} +5020 +5021 AbsentSubscriberDiagnosticSM +5022 FROM MAP-ER-DataTypes { +5023 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5024 gsm-Network (1) modules (3) map-ER-DataTypes (17) version21 (21)} +5025 +5026 ExtensionContainer +5027 FROM MAP-ExtensionDataTypes { +5028 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5029 gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version21 (21)} +5030 ; +5031 +5032 +5033 RoutingInfoForSM-Arg ::= SEQUENCE { +5034 msisdn [0] ISDN-AddressString, +5035 sm-RP-PRI [1] BOOLEAN, +5036 serviceCentreAddress [2] AddressString, +5037 extensionContainer [6] ExtensionContainer OPTIONAL, +5038 ... , +5039 gprsSupportIndicator [7] NULL OPTIONAL, +5040 -- gprsSupportIndicator is set only if the SMS-GMSC supports +5041 -- receiving of two numbers from the HLR +5042 sm-RP-MTI [8] SM-RP-MTI OPTIONAL, +5043 sm-RP-SMEA [9] SM-RP-SMEA OPTIONAL, +5044 sm-deliveryNotIntended [10] SM-DeliveryNotIntended OPTIONAL, +5045 ip-sm-gwGuidanceIndicator [11] NULL OPTIONAL, +5046 imsi [12] IMSI OPTIONAL, +5047 t4-Trigger-Indicator [14] NULL OPTIONAL, +5048 singleAttemptDelivery [13] NULL OPTIONAL, +5049 correlationID [15] CorrelationID OPTIONAL, +5050 smsf-supportIndicator [16] NULL OPTIONAL } +5051 +5052 SM-DeliveryNotIntended ::= ENUMERATED { +5053 onlyIMSI-requested (0), +5054 onlyMCC-MNC-requested (1), +5055 ...} +5056 +5057 SM-RP-MTI ::= INTEGER (0..10) +5058 -- 0 SMS Deliver +5059 -- 1 SMS Status Report +5060 -- other values are reserved for future use and shall be discarded if +5061 -- received +5062 +5063 SM-RP-SMEA ::= OCTET STRING (SIZE (1..12)) +5064 -- this parameter contains an address field which is encoded +5065 -- as defined in 3GPP TS 23.040. An address field contains 3 elements : +5066 -- address-length +5067 -- type-of-address +5068 -- address-value +5069 +5070 RoutingInfoForSM-Res ::= SEQUENCE { +5071 imsi IMSI, +5072 locationInfoWithLMSI [0] LocationInfoWithLMSI, +5073 extensionContainer [4] ExtensionContainer OPTIONAL, +5074 ..., +5075 ip-sm-gwGuidance [5] IP-SM-GW-Guidance OPTIONAL } +5076 + +``` + +``` + +5077 IP-SM-GW-Guidance ::= SEQUENCE { +5078 minimumDeliveryTimeValue SM-DeliveryTimerValue, +5079 recommendedDeliveryTimeValue SM-DeliveryTimerValue, +5080 extensionContainer ExtensionContainer OPTIONAL, +5081 ... } +5082 +5083 LocationInfoWithLMSI ::= SEQUENCE { +5084 networkNode-Number [1] ISDN-AddressString, +5085 lmsi LMSI OPTIONAL, +5086 extensionContainer ExtensionContainer OPTIONAL, +5087 ..., +5088 gprsNodeIndicator [5] NULL OPTIONAL, +5089 -- gprsNodeIndicator is set only if the SGSN number is sent as the +5090 -- Network Node Number +5091 additional-Number [6] Additional-Number OPTIONAL, +5092 networkNodeDiameterAddress [7] NetworkNodeDiameterAddress OPTIONAL, +5093 additionalNetworkNodeDiameterAddress [8] NetworkNodeDiameterAddress OPTIONAL, +5094 thirdNumber [9] Additional-Number OPTIONAL, +5095 thirdNetworkNodeDiameterAddress [10] NetworkNodeDiameterAddress OPTIONAL, +5096 imsNodeIndicator [11] NULL OPTIONAL, +5097 -- gprsNodeIndicator and imsNodeIndicator shall not both be present. +5098 -- additionalNumber and thirdNumber shall not both contain the same type of number. +5099 smsf-3gpp-Number [12] ISDN-AddressString OPTIONAL, +5100 smsf-3gpp-DiameterAddress [13] NetworkNodeDiameterAddress OPTIONAL, +5101 smsf-non-3gpp-Number [14] ISDN-AddressString OPTIONAL, +5102 smsf-non-3gpp-DiameterAddress [15] NetworkNodeDiameterAddress OPTIONAL, +5103 smsf-3gpp-address-indicator [16] NULL OPTIONAL, +5104 smsf-non-3gpp-address-indicator [17] NULL OPTIONAL +5105 -- +5106 -- If smsf-supportIndicator was not included in the request, in RoutingInfoForSM-Arg, +5107 -- then smsf-3gpp Number/DiameterAddress, smsf-non-3gpp Number/DiameterAddress and +5108 -- smsf-address-indicator and smsf-non-3gpp-address-indicator shall be absent. +5109 -- +5110 -- If smsf-3gpp-address-indicator is present, it indicates that the networkNode-Number +5111 -- (and networkNodeDiameterAddress, if present) contains the address of an SMSF for +5112 -- 3GPP access. +5113 -- +5114 -- If smsf-non-3gpp-address-indicator is present, it indicates that the +5115 -- networkNode-Number (and networkNodeDiameterAddress, if present) contains the +5116 -- address of an SMSF for non 3GPP access. +5117 -- +5118 -- At most one of gprsNodeIndicator, imsNodeIndicator, smsf-3gpp-address-indicator +5119 -- and smsf-non-3gpp-address-indicator shall be present. Absence of all these +5120 -- indicators indicate that the networkNode-Number (and networkNodeDiameterAddress, +5121 -- if present) contains the address of an MSC/MME. +5122 +5123 } +5124 +5125 Additional-Number ::= CHOICE { +5126 msc-Number [0] ISDN-AddressString, +5127 sgsn-Number [1] ISDN-AddressString} +5128 -- msc-number can be the MSC number or +5129 -- the SMS Router number or the MME number for MT SMS +5130 -- sgsn-number can be the SGSN number or the SMS Router number +5131 +5132 MO-ForwardSM-Arg ::= SEQUENCE { +5133 sm-RP-DA SM-RP-DA, +5134 sm-RP-OA SM-RP-OA, +5135 sm-RP-UI SignalInfo, +5136 extensionContainer ExtensionContainer OPTIONAL, +5137 ... , +5138 imsi IMSI OPTIONAL, +5139 correlationID [0] CorrelationID OPTIONAL, +5140 sm-DeliveryOutcome [1] SM-DeliveryOutcome OPTIONAL +5141 } +5142 +5143 MO-ForwardSM-Res ::= SEQUENCE { +5144 sm-RP-UI SignalInfo OPTIONAL, +5145 extensionContainer ExtensionContainer OPTIONAL, +5146 ... } +5147 + +``` + +``` + +5148 MT-ForwardSM-Arg ::= SEQUENCE { +5149 sm-RP-DA SM-RP-DA, +5150 sm-RP-OA SM-RP-OA, +5151 sm-RP-UI SignalInfo, +5152 moreMessagesToSend NULL OPTIONAL, +5153 extensionContainer ExtensionContainer OPTIONAL, +5154 ..., +5155 smDeliveryTimerValue SM-DeliveryTimerValue OPTIONAL, +5156 smDeliveryStartTime Time OPTIONAL, +5157 smsOverIP-OnlyIndicator [0] NULL OPTIONAL, +5158 correlationID [1] CorrelationID OPTIONAL, +5159 maximumRetransmissionTime [2] Time OPTIONAL, +5160 smsGmscAddress [3] ISDN-AddressString OPTIONAL, +5161 smsGmscDiameterAddress [4] NetworkNodeDiameterAddress OPTIONAL } +5162 -- SM-DeliveryTimerValue contains the value used by the SMS-GMSC +5163 +5164 CorrelationID ::= SEQUENCE { +5165 hlr-id [0] HLR-Id OPTIONAL, +5166 sip-uri-A [1] SIP-URI OPTIONAL, +5167 sip-uri-B [2] SIP-URI} +5168 +5169 SIP-URI ::= OCTET STRING +5170 -- octets are coded as defined in IETF RFC 3261 +5171 +5172 MT-ForwardSM-Res ::= SEQUENCE { +5173 sm-RP-UI SignalInfo OPTIONAL, +5174 extensionContainer ExtensionContainer OPTIONAL, +5175 ... } +5176 +5177 SM-RP-DA ::= CHOICE { +5178 imsi [0] IMSI, +5179 lmsi [1] LMSI, +5180 serviceCentreAddressDA [4] AddressString, +5181 noSM-RP-DA [5] NULL} +5182 +5183 SM-RP-OA ::= CHOICE { +5184 msisdn [2] ISDN-AddressString, +5185 serviceCentreAddressOA [4] AddressString, +5186 noSM-RP-OA [5] NULL} +5187 +5188 SM-DeliveryTimerValue ::= INTEGER (30..600) +5189 + +``` + +``` + +5190 ReportSM-DeliveryStatusArg ::= SEQUENCE { +5191 msisdn ISDN-AddressString, +5192 serviceCentreAddress AddressString, +5193 sm-DeliveryOutcome SM-DeliveryOutcome, +5194 absentSubscriberDiagnosticSM [0] AbsentSubscriberDiagnosticSM +5195 OPTIONAL, +5196 extensionContainer [1] ExtensionContainer OPTIONAL, +5197 ..., +5198 gprsSupportIndicator [2] NULL OPTIONAL, +5199 -- gprsSupportIndicator is set only if the SMS-GMSC supports +5200 -- handling of two delivery outcomes +5201 deliveryOutcomeIndicator [3] NULL OPTIONAL, +5202 -- DeliveryOutcomeIndicator is set when the SM-DeliveryOutcome +5203 -- is for GPRS +5204 additionalSM-DeliveryOutcome [4] SM-DeliveryOutcome OPTIONAL, +5205 -- If received, additionalSM-DeliveryOutcome is for GPRS +5206 -- If DeliveryOutcomeIndicator is set, then AdditionalSM-DeliveryOutcome shall be absent +5207 additionalAbsentSubscriberDiagnosticSM [5] AbsentSubscriberDiagnosticSM OPTIONAL, +5208 -- If received additionalAbsentSubscriberDiagnosticSM is for GPRS +5209 -- If DeliveryOutcomeIndicator is set, then AdditionalAbsentSubscriberDiagnosticSM +5210 -- shall be absent +5211 ip-sm-gw-indicator [6] NULL OPTIONAL, +5212 -- the ip-sm-gw indicator indicates by its presence that sm-deliveryOutcome +5213 -- is for delivery via IMS +5214 -- If present, deliveryOutcomeIndicator shall be absent. +5215 ip-sm-gw-sm-deliveryOutcome [7] SM-DeliveryOutcome OPTIONAL, +5216 -- If received ip-sm-gw-sm-deliveryOutcome is for delivery via IMS +5217 -- If ip-sm-gw-indicator is set, then ip-sm-gw-sm-deliveryOutcome shall be absent +5218 ip-sm-gw-absentSubscriberDiagnosticSM [8] AbsentSubscriberDiagnosticSM OPTIONAL, +5219 -- If received ip-sm-gw-sm-absentSubscriberDiagnosticSM is for delivery via IMS +5220 -- If ip-sm-gw-indicator is set, then ip-sm-gw-sm-absentSubscriberDiagnosticSM +5221 -- shall be absent +5222 imsi [9] IMSI OPTIONAL, +5223 singleAttemptDelivery [10] NULL OPTIONAL, +5224 correlationID [11] CorrelationID OPTIONAL, +5225 smsf-3gpp-deliveryOutcomeIndicator [12] NULL OPTIONAL, +5226 -- smsf-3gpp-deliveryOutcome is set when the SM-DeliveryOutcome +5227 -- is for 3GPP-SMSF +5228 smsf-3gpp-deliveryOutcome [13] SM-DeliveryOutcome OPTIONAL, +5229 -- If smsf-3gpp-deliveryOutcomeIndicator is set, then smsf-3gpp-deliveryOutcome +5230 -- shall be absent +5231 smsf-3gpp-absentSubscriberDiagSM [14] AbsentSubscriberDiagnosticSM OPTIONAL, +5232 -- If smsf-3gpp-deliveryOutcomeIndicator is set, then +5233 -- smsf-3gpp-absentSubscriberDiagSM shall be absent +5234 smsf-non-3gpp-deliveryOutcomeIndicator [15] NULL OPTIONAL, +5235 -- smsf-non-3gpp-deliveryOutcomeIndicator is set when the SM-DeliveryOutcome +5236 -- is for non-3GPP-SMSF +5237 smsf-non-3gpp-deliveryOutcome [16] SM-DeliveryOutcome OPTIONAL, +5238 -- If smsf-non-3gpp-deliveryOutcomeIndicator is set, then smsf-non-3gpp-deliveryOutcome +5239 -- shall be absent +5240 smsf-non-3gpp-absentSubscriberDiagSM [17] AbsentSubscriberDiagnosticSM OPTIONAL +5241 -- If smsf-non-3gpp-deliveryOutcomeIndicator is set, then +5242 -- smsf-non-3gpp-absentSubscriberDiagSM shall be absent +5243 +5244 } + +``` + +``` + +5245 +5246 SM-DeliveryOutcome ::= ENUMERATED { +5247 memoryCapacityExceeded (0), +5248 absentSubscriber (1), +5249 successfulTransfer (2) } + +``` + +``` + +5250 +5251 ReportSM-DeliveryStatusRes ::= SEQUENCE { +5252 storedMSISDN ISDN-AddressString OPTIONAL, +5253 extensionContainer ExtensionContainer OPTIONAL, +5254 ... } + +``` + +``` + +5255 + +``` + +``` + +5256 AlertServiceCentreArg ::= SEQUENCE { +5257 msisdn ISDN-AddressString, +5258 serviceCentreAddress AddressString, +5259 ..., +5260 imsi IMSI OPTIONAL, +5261 correlationID CorrelationID OPTIONAL, +5262 maximumUeAvailabilityTime [0] Time OPTIONAL, +5263 smsGmscAlertEvent [1] SmsGmsc-Alert-Event OPTIONAL, +5264 smsGmscDiameterAddress [2] NetworkNodeDiameterAddress OPTIONAL, +5265 newSGSNNumber [3] ISDN-AddressString OPTIONAL, +5266 newSGSNDiameterAddress [4] NetworkNodeDiameterAddress OPTIONAL, +5267 newMMENumber [5] ISDN-AddressString OPTIONAL, +5268 newMMDiameterAddress [6] NetworkNodeDiameterAddress OPTIONAL, +5269 newMSCNumber [7] ISDN-AddressString OPTIONAL } +5270 +5271 SmsGmsc-Alert-Event ::= ENUMERATED { +5272 msAvailableForMtSms (0), +5273 msUnderNewServingNode (1) } +5274 +5275 InformServiceCentreArg ::= SEQUENCE { +5276 storedMSISDN ISDN-AddressString OPTIONAL, +5277 mw-Status MW-Status OPTIONAL, +5278 extensionContainer ExtensionContainer OPTIONAL, +5279 ..., +5280 absentSubscriberDiagnosticSM AbsentSubscriberDiagnosticSM OPTIONAL, +5281 additionalAbsentSubscriberDiagnosticSM [0] AbsentSubscriberDiagnosticSM OPTIONAL, +5282 -- additionalAbsentSubscriberDiagnosticSM may be present only if +5283 -- absentSubscriberDiagnosticSM is present. +5284 -- if included, additionalAbsentSubscriberDiagnosticSM is for GPRS and +5285 -- absentSubscriberDiagnosticSM is for non-GPRS +5286 smsf3gppAbsentSubscriberDiagnosticSM [1] AbsentSubscriberDiagnosticSM OPTIONAL, +5287 smsfNon3gppAbsentSubscriberDiagnosticSM [2] AbsentSubscriberDiagnosticSM OPTIONAL } +5288 +5289 MW-Status ::= BIT STRING { +5290 sc-AddressNotIncluded (0), +5291 mnrf-Set (1), +5292 mcef-Set (2), +5293 mnrg-Set (3), +5294 mnr5g-Set (4), +5295 mnr5gn3g-Set (5)} (SIZE (6..16)) +5296 -- exception handling: +5297 -- bits 6 to 15 shall be ignored if received and not understood +5298 +5299 ReadyForSM-Arg ::= SEQUENCE { +5300 imsi [0] IMSI, +5301 alertReason AlertReason, +5302 alertReasonIndicator NULL OPTIONAL, +5303 -- alertReasonIndicator is set only when the alertReason +5304 -- sent to HLR is for GPRS +5305 extensionContainer ExtensionContainer OPTIONAL, +5306 ..., +5307 additionalAlertReasonIndicator [1] NULL OPTIONAL, +5308 -- additionalAlertReasonIndicator is set only when the alertReason +5309 -- sent to HLR is for IP-SM-GW +5310 maximumUeAvailabilityTime Time OPTIONAL } +5311 +5312 ReadyForSM-Res ::= SEQUENCE { +5313 extensionContainer ExtensionContainer OPTIONAL, +5314 ...} +5315 +5316 AlertReason ::= ENUMERATED { +5317 ms-Present (0), +5318 memoryAvailable (1)} +5319 +5320 MT-ForwardSM-VGCS-Arg ::= SEQUENCE { +5321 asciCallReference ASCI-CallReference, +5322 sm-RP-OA SM-RP-OA, +5323 sm-RP-UI SignalInfo, +5324 extensionContainer ExtensionContainer OPTIONAL, +5325 ...} +5326 + +``` + +``` + +5327 MT-ForwardSM-VGCS-Res ::= SEQUENCE { +5328 sm-RP-UI [0] SignalInfo OPTIONAL, +5329 dispatcherList [1] DispatcherList OPTIONAL, +5330 ongoingCall NULL OPTIONAL, +5331 extensionContainer [2] ExtensionContainer OPTIONAL, +5332 ..., +5333 additionalDispatcherList [3] AdditionalDispatcherList OPTIONAL } +5334 -- additionalDispatcherList shall be absent if dispatcherList is absent or +5335 -- contains less than 5 ISDN-AddressStrings +5336 +5337 DispatcherList ::= +5338 SEQUENCE SIZE (1..maxNumOfDispatchers) OF +5339 ISDN-AddressString +5340 +5341 maxNumOfDispatchers INTEGER ::= 5 +5342 +5343 AdditionalDispatcherList ::= +5344 SEQUENCE SIZE (1..maxNumOfAdditionalDispatchers) OF +5345 ISDN-AddressString +5346 +5347 maxNumOfAdditionalDispatchers INTEGER ::= 15 +5348 +5349 +5350 END + +``` + +## 5351 17.7.7 Error data types + +``` + +5352 MAP-ER-DataTypes { +5353 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5354 gsm-Network (1) modules (3) map-ER-DataTypes (17) version21 (21)} +5355 +5356 DEFINITIONS +5357 +5358 IMPLICIT TAGS +5359 +5360 ::= +5361 +5362 BEGIN +5363 +5364 EXPORTS +5365 RoamingNotAllowedParam, +5366 CallBarredParam, +5367 CUG-RejectParam, +5368 SS-IncompatibilityCause, +5369 PW-RegistrationFailureCause, +5370 SM-DeliveryFailureCause, +5371 SystemFailureParam, +5372 DataMissingParam, +5373 UnexpectedDataParam, +5374 FacilityNotSupParam, +5375 OR-NotAllowedParam, +5376 UnknownSubscriberParam, +5377 NumberChangedParam, +5378 UnidentifiedSubParam, +5379 IllegalSubscriberParam, +5380 IllegalEquipmentParam, +5381 BearerServNotProvParam, +5382 TeleservNotProvParam, +5383 TracingBufferFullParam, +5384 NoRoamingNbParam, +5385 AbsentSubscriberParam, +5386 BusySubscriberParam, +5387 NoSubscriberReplyParam, +5388 ForwardingViolationParam, +5389 ForwardingFailedParam, +5390 ATI-NotAllowedParam, +5391 SubBusyForMT-SMS-Param, +5392 MessageWaitListFullParam, +5393 AbsentSubscriberSM-Param, +5394 AbsentSubscriberDiagnosticSM, +5395 ResourceLimitationParam, +5396 NoGroupCallNbParam, +5397 IncompatibleTerminalParam, +5398 ShortTermDenialParam, +5399 LongTermDenialParam, +5400 UnauthorizedRequestingNetwork-Param, +5401 UnauthorizedLCSClient-Param, +5402 PositionMethodFailure-Param, + +``` + +``` + +5403 UnknownOrUnreachableLCSCliet-Param, +5404 MM-EventNotSupported-Param, +5405 ATSI-NotAllowedParam, +5406 ATM-NotAllowedParam, +5407 IllegalSS-OperationParam, +5408 SS-NotAvailableParam, +5409 SS-SubscriptionViolationParam, +5410 InformationNotAvailableParam, +5411 TargetCellOutsideGCA-Param, +5412 OngoingGroupCallParam, +5413 PositionMethodFailure-Diagnostic, +5414 UnauthorizedLCSCliet-Diagnostic +5415 +5416 ; +5417 +5418 IMPORTS +5419 SS-Status +5420 FROM MAP-SS-DataTypes { +5421 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5422 gsm-Network (1) modules (3) map-SS-DataTypes (14) version21 (21)} +5423 +5424 SignalInfo, +5425 BasicServiceCode, +5426 NetworkResource, +5427 AdditionalNetworkResource, +5428 IMSI, +5429 Time +5430 FROM MAP-CommonDataTypes { +5431 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5432 gsm-Network (1) modules (3) map-CommonDataTypes (18) version21 (21)} +5433 +5434 +5435 SS-Code +5436 FROM MAP-SS-Code { +5437 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5438 gsm-Network (1) modules (3) map-SS-Code (15) version21 (21)} +5439 +5440 ExtensionContainer +5441 FROM MAP-ExtensionDataTypes { +5442 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5443 gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version21 (21)} +5444 ; +5445 +5446 RoamingNotAllowedParam ::= SEQUENCE { +5447 roamingNotAllowedCause RoamingNotAllowedCause, +5448 extensionContainer ExtensionContainer OPTIONAL, +5449 ..., +5450 additionalRoamingNotAllowedCause [0] AdditionalRoamingNotAllowedCause OPTIONAL } +5451 +5452 -- if the additionalRoamingNotAllowedCause is received by the MSC/VLR or SGSN then the +5453 -- roamingNotAllowedCause shall be discarded. +5454 +5455 AdditionalRoamingNotAllowedCause ::= ENUMERATED { +5456 supportedRAT-TypesNotAllowed (0), +5457 ...} +5458 +5459 RoamingNotAllowedCause ::= ENUMERATED { +5460 plmnRoamingNotAllowed (0), +5461 operatorDeterminedBarring (3)} +5462 +5463 CallBarredParam ::= CHOICE { +5464 callBarringCause CallBarringCause, +5465 -- call BarringCause must not be used in version 3 and higher +5466 extensibleCallBarredParam ExtensibleCallBarredParam +5467 -- extensibleCallBarredParam must not be used in version <3 +5468 } +5469 +5470 CallBarringCause ::= ENUMERATED { +5471 barringServiceActive (0), +5472 operatorBarring (1)} +5473 + +``` + +``` + +5474 ExtensibleCallBarredParam ::= SEQUENCE { +5475 callBarringCause CallBarringCause OPTIONAL, +5476 extensionContainer ExtensionContainer OPTIONAL, +5477 ... , +5478 unauthorisedMessageOriginator [1] NULL OPTIONAL, +5479 anonymousCallRejection [2] NULL OPTIONAL } +5480 +5481 -- unauthorisedMessageOriginator and anonymousCallRejection shall be mutually exclusive. +5482 +5483 +5484 CUG-RejectParam ::= SEQUENCE { +5485 cug-RejectCause CUG-RejectCause OPTIONAL, +5486 extensionContainer ExtensionContainer OPTIONAL, +5487 ... } +5488 +5489 CUG-RejectCause ::= ENUMERATED { +5490 incomingCallsBarredWithinCUG (0), +5491 subscriberNotMemberOfCUG (1), +5492 requestedBasicServiceViolatesCUG-Constraints (5), +5493 calledPartySS-InteractionViolation (7) } +5494 +5495 SS-IncompatibilityCause ::= SEQUENCE { +5496 ss-Code [1] SS-Code OPTIONAL, +5497 basicService BasicServiceCode OPTIONAL, +5498 ss-Status [4] SS-Status OPTIONAL, +5499 ... } +5500 +5501 PW-RegistrationFailureCause ::= ENUMERATED { +5502 undetermined (0), +5503 invalidFormat (1), +5504 newPasswordsMismatch (2) } +5505 +5506 SM-EnumeratedDeliveryFailureCause ::= ENUMERATED { +5507 memoryCapacityExceeded (0), +5508 equipmentProtocolError (1), +5509 equipmentNotSM-Equipped (2), +5510 unknownServiceCentre (3), +5511 sc-Congestion (4), +5512 invalidSME-Address (5), +5513 subscriberNotSC-Subscriber (6) } +5514 +5515 SM-DeliveryFailureCause ::= SEQUENCE { +5516 sm-EnumeratedDeliveryFailureCause SM-EnumeratedDeliveryFailureCause, +5517 diagnosticInfo SignalInfo OPTIONAL, +5518 extensionContainer ExtensionContainer OPTIONAL, +5519 ... } +5520 +5521 AbsentSubscriberSM-Param ::= SEQUENCE { +5522 absentSubscriberDiagnosticSM AbsentSubscriberDiagnosticSM OPTIONAL, +5523 -- AbsentSubscriberDiagnosticSM can be either for non-GPRS +5524 -- or for GPRS +5525 extensionContainer ExtensionContainer OPTIONAL, +5526 ..., +5527 additionalAbsentSubscriberDiagnosticSM [0] AbsentSubscriberDiagnosticSM OPTIONAL, +5528 -- if received, additionalAbsentSubscriberDiagnosticSM +5529 -- is for GPRS and absentSubscriberDiagnosticSM is +5530 -- for non-GPRS +5531 imsi [1] IMSI OPTIONAL, +5532 -- when sent from HLR to IP-SM-GW, IMSI shall be present if UNRI is not set +5533 -- to indicate that the absent condition is met for CS and PS but not for IMS. +5534 requestedRetransmissionTime [2] Time OPTIONAL, +5535 userIdentifierAlert [3] IMSI OPTIONAL } +5536 +5537 AbsentSubscriberDiagnosticSM ::= INTEGER (0..255) +5538 -- AbsentSubscriberDiagnosticSM values are defined in 3GPP TS 23.040 +5539 +5540 SystemFailureParam ::= CHOICE { +5541 networkResource NetworkResource, +5542 -- networkResource must not be used in version 3 +5543 extensibleSystemFailureParam ExtensibleSystemFailureParam +5544 -- extensibleSystemFailureParam must not be used in version <3 +5545 } +5546 + +``` + +``` + +5547 ExtensibleSystemFailureParam ::= SEQUENCE { +5548 networkResource NetworkResource OPTIONAL, +5549 extensionContainer ExtensionContainer OPTIONAL, +5550 ..., +5551 additionalNetworkResource [0] AdditionalNetworkResource OPTIONAL, +5552 failureCauseParam [1] FailureCauseParam OPTIONAL } +5553 +5554 FailureCauseParam ::= ENUMERATED { +5555 limitReachedOnNumberOfConcurrentLocationRequests (0), +5556 ... } +5557 -- if unknown value is received in FailureCauseParam it shall be ignored +5558 +5559 +5560 DataMissingParam ::= SEQUENCE { +5561 extensionContainer ExtensionContainer OPTIONAL, +5562 ...} +5563 +5564 UnexpectedDataParam ::= SEQUENCE { +5565 extensionContainer ExtensionContainer OPTIONAL, +5566 ..., +5567 unexpectedSubscriber [0] NULL OPTIONAL} +5568 -- the unexpectedSubscriber indication in the unexpectedDataValue error shall not be used +5569 -- for operations that allow the unidentifiedSubscriber error. +5570 +5571 FacilityNotSupParam ::= SEQUENCE { +5572 extensionContainer ExtensionContainer OPTIONAL, +5573 ..., +5574 shapeOfLocationEstimateNotSupported [0] NULL OPTIONAL, +5575 neededLcsCapabilityNotSupportedInServingNode [1] NULL OPTIONAL } +5576 +5577 OR-NotAllowedParam ::= SEQUENCE { +5578 extensionContainer ExtensionContainer OPTIONAL, +5579 ...} +5580 +5581 UnknownSubscriberParam ::= SEQUENCE { +5582 extensionContainer ExtensionContainer OPTIONAL, +5583 ..., +5584 unknownSubscriberDiagnostic UnknownSubscriberDiagnostic OPTIONAL} +5585 +5586 UnknownSubscriberDiagnostic ::= ENUMERATED { +5587 imsiUnknown (0), +5588 gprs-eps-SubscriptionUnknown (1), +5589 ..., +5590 npdbMismatch (2)} +5591 -- if unknown values are received in +5592 -- UnknownSubscriberDiagnostic they shall be discarded +5593 +5594 NumberChangedParam ::= SEQUENCE { +5595 extensionContainer ExtensionContainer OPTIONAL, +5596 ...} +5597 +5598 UnidentifiedSubParam ::= SEQUENCE { +5599 extensionContainer ExtensionContainer OPTIONAL, +5600 ...} +5601 +5602 IllegalSubscriberParam ::= SEQUENCE { +5603 extensionContainer ExtensionContainer OPTIONAL, +5604 ...} +5605 +5606 IllegalEquipmentParam ::= SEQUENCE { +5607 extensionContainer ExtensionContainer OPTIONAL, +5608 ...} +5609 +5610 BearerServNotProvParam ::= SEQUENCE { +5611 extensionContainer ExtensionContainer OPTIONAL, +5612 ...} +5613 +5614 TeleservNotProvParam ::= SEQUENCE { +5615 extensionContainer ExtensionContainer OPTIONAL, +5616 ...} +5617 +5618 TracingBufferFullParam ::= SEQUENCE { +5619 extensionContainer ExtensionContainer OPTIONAL, +5620 ...} +5621 + +``` + +``` + +5622 NoRoamingNbParam ::= SEQUENCE { +5623 extensionContainer ExtensionContainer OPTIONAL, +5624 ...} +5625 +5626 AbsentSubscriberParam ::= SEQUENCE { +5627 extensionContainer ExtensionContainer OPTIONAL, +5628 ..., +5629 absentSubscriberReason [0] AbsentSubscriberReason OPTIONAL} +5630 +5631 AbsentSubscriberReason ::= ENUMERATED { +5632 imsiDetach (0), +5633 restrictedArea (1), +5634 noPageResponse (2), +5635 ... , +5636 purgedMS (3), +5637 mtRoamingRetry (4), +5638 busySubscriber (5)} +5639 -- exception handling: at reception of other values than the ones listed the +5640 -- AbsentSubscriberReason shall be ignored. +5641 -- The AbsentSubscriberReason: purgedMS is defined for the Super-Charger feature +5642 -- (see TS 23.116). If this value is received in a Provide Roaming Number response +5643 -- it shall be mapped to the AbsentSubscriberReason: imsiDetach in the Send Routeing +5644 -- Information response +5645 -- The AbsentSubscriberReason: mtRoamingRetry is used during MT Roaming Retry, +5646 -- see 3GPP TS 23.018[97]. +5647 -- The AbsentSubscriberReason: busySubscriber is used during MT Roaming Forwarding, +5648 -- see 3GPP TS 23.018[97]. +5649 +5650 BusySubscriberParam ::= SEQUENCE { +5651 extensionContainer ExtensionContainer OPTIONAL, +5652 ..., +5653 ccbs-Possible [0] NULL OPTIONAL, +5654 ccbs-Busy [1] NULL OPTIONAL} +5655 +5656 NoSubscriberReplyParam ::= SEQUENCE { +5657 extensionContainer ExtensionContainer OPTIONAL, +5658 ...} +5659 +5660 ForwardingViolationParam ::= SEQUENCE { +5661 extensionContainer ExtensionContainer OPTIONAL, +5662 ...} +5663 +5664 ForwardingFailedParam ::= SEQUENCE { +5665 extensionContainer ExtensionContainer OPTIONAL, +5666 ...} +5667 +5668 ATI-NotAllowedParam ::= SEQUENCE { +5669 extensionContainer ExtensionContainer OPTIONAL, +5670 ...} +5671 +5672 ATSI-NotAllowedParam ::= SEQUENCE { +5673 extensionContainer ExtensionContainer OPTIONAL, +5674 ...} +5675 +5676 ATM-NotAllowedParam ::= SEQUENCE { +5677 extensionContainer ExtensionContainer OPTIONAL, +5678 ...} +5679 +5680 IllegalSS-OperationParam ::= SEQUENCE { +5681 extensionContainer ExtensionContainer OPTIONAL, +5682 ...} +5683 +5684 SS-NotAvailableParam ::= SEQUENCE { +5685 extensionContainer ExtensionContainer OPTIONAL, +5686 ...} +5687 +5688 SS-SubscriptionViolationParam ::= SEQUENCE { +5689 extensionContainer ExtensionContainer OPTIONAL, +5690 ...} +5691 +5692 InformationNotAvailableParam ::= SEQUENCE { +5693 extensionContainer ExtensionContainer OPTIONAL, +5694 ...} +5695 + +``` + +``` + +5696 SubBusyForMT-SMS-Param ::= SEQUENCE { +5697 extensionContainer ExtensionContainer OPTIONAL, +5698 ... , +5699 gprsConnectionSuspended NULL OPTIONAL } +5700 -- If GprsConnectionSuspended is not understood it shall +5701 -- be discarded +5702 +5703 MessageWaitListFullParam ::= SEQUENCE { +5704 extensionContainer ExtensionContainer OPTIONAL, +5705 ... } +5706 +5707 ResourceLimitationParam ::= SEQUENCE { +5708 extensionContainer ExtensionContainer OPTIONAL, +5709 ... } +5710 +5711 NoGroupCallNbParam ::= SEQUENCE { +5712 extensionContainer ExtensionContainer OPTIONAL, +5713 ... } +5714 +5715 IncompatibleTerminalParam ::= SEQUENCE { +5716 extensionContainer ExtensionContainer OPTIONAL, +5717 ... } +5718 +5719 ShortTermDenialParam ::= SEQUENCE { +5720 ... } +5721 +5722 LongTermDenialParam ::= SEQUENCE { +5723 ... } +5724 +5725 UnauthorizedRequestingNetwork-Param ::= SEQUENCE { +5726 extensionContainer ExtensionContainer OPTIONAL, +5727 ... } +5728 +5729 UnauthorizedLCSCliet-Param ::= SEQUENCE { +5730 unauthorizedLCSCliet-Diagnostic [0] UnauthorizedLCSCliet-Diagnostic OPTIONAL, +5731 extensionContainer [1] ExtensionContainer OPTIONAL, +5732 ... } +5733 +5734 UnauthorizedLCSCliet-Diagnostic ::= ENUMERATED { +5735 noAdditionalInformation (0), +5736 clientNotInMSPrivacyExceptionList (1), +5737 callToClientNotSetup (2), +5738 privacyOverrideNotApplicable (3), +5739 disallowedByLocalRegulatoryRequirements (4), +5740 ..., +5741 unauthorizedPrivacyClass (5), +5742 unauthorizedCallSessionUnrelatedExternalClient (6), +5743 unauthorizedCallSessionRelatedExternalClient (7) } +5744 -- exception handling: +5745 -- any unrecognized value shall be ignored +5746 +5747 PositionMethodFailure-Param ::= SEQUENCE { +5748 positionMethodFailure-Diagnostic [0] PositionMethodFailure-Diagnostic OPTIONAL, +5749 extensionContainer [1] ExtensionContainer OPTIONAL, +5750 ... } +5751 +5752 PositionMethodFailure-Diagnostic ::= ENUMERATED { +5753 congestion (0), +5754 insufficientResources (1), +5755 insufficientMeasurementData (2), +5756 inconsistentMeasurementData (3), +5757 locationProcedureNotCompleted (4), +5758 locationProcedureNotSupportedByTargetMS (5), +5759 qosNotAttainable (6), +5760 positionMethodNotAvailableInNetwork (7), +5761 positionMethodNotAvailableInLocationArea (8), +5762 ... } +5763 -- exception handling: +5764 -- any unrecognized value shall be ignored +5765 +5766 UnknownOrUnreachableLCSCliet-Param ::= SEQUENCE { +5767 extensionContainer ExtensionContainer OPTIONAL, +5768 ... } +5769 +5770 MM-EventNotSupported-Param ::= SEQUENCE { + +``` + +``` + +5771 extensionContainer ExtensionContainer OPTIONAL, +5772 ...} +5773 +5774 TargetCellOutsideGCA-Param ::= SEQUENCE { +5775 extensionContainer ExtensionContainer OPTIONAL, +5776 ...} +5777 +5778 OngoingGroupCallParam ::= SEQUENCE { +5779 extensionContainer ExtensionContainer OPTIONAL, +5780 ...} +5781 +5782 +5783 END + +``` + +## 5784 17.7.8 Common data types + +``` + +5785 MAP-CommonDataTypes { +5786 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5787 gsm-Network (1) modules (3) map-CommonDataTypes (18) version21 (21)} +5788 +5789 DEFINITIONS +5790 +5791 IMPLICIT TAGS +5792 +5793 ::= +5794 +5795 BEGIN +5796 +5797 EXPORTS +5798 +5799 -- general data types and values +5800 AddressString, +5801 ISDN-AddressString, +5802 maxISDN-AddressLength, +5803 FTN-AddressString, +5804 ISDN-SubaddressString, +5805 ExternalSignalInfo, +5806 Ext-ExternalSignalInfo, +5807 AccessNetworkSignalInfo, +5808 SignalInfo, +5809 maxSignalInfoLength, +5810 AlertingPattern, +5811 TBCD-STRING, +5812 DiameterIdentity, +5813 Time, +5814 HLR-Id, +5815 +5816 -- data types for numbering and identification +5817 IMSI, +5818 TMSI, +5819 Identity, +5820 SubscriberId, +5821 IMEI, +5822 HLR-List, +5823 LMSI, +5824 GlobalCellId, +5825 NetworkResource, +5826 AdditionalNetworkResource, +5827 NAEA-PreferredCI, +5828 NAEA-CIC, +5829 ASCI-CallReference, +5830 SubscriberIdentity, +5831 PLMN-Id, +5832 E-UTRAN-CGI, +5833 NR-CGI, +5834 TA-Id, +5835 NR-TA-Id, +5836 RAIdentity, +5837 NetworkNodeDiameterAddress, +5838 +5839 -- data types for CAMEL +5840 CellGlobalIdOrServiceAreaIdOrLAI, +5841 CellGlobalIdOrServiceAreaIdFixedLength, +5842 LAIFixedLength, +5843 +5844 -- data types for subscriber management +5845 BasicServiceCode, +5846 Ext-BasicServiceCode, + +``` + +``` + +5847 EMLPP-Info, +5848 EMLPP-Priority, +5849 MC-SS-Info, +5850 MaxMC-Bearers, +5851 MC-Bearers, +5852 Ext-SS-Status, +5853 +5854 -- data types for geographic location +5855 AgeOfLocationInformation, +5856 LCSCClientExternalID, +5857 LCSCClientInternalID, +5858 LCSServiceTypeID, +5859 +5860 -- gprs location registration types +5861 GSN-Address +5862 +5863 ; +5864 +5865 IMPORTS +5866 TeleserviceCode, +5867 Ext-TeleserviceCode +5868 FROM MAP-TS-Code { +5869 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5870 gsm-Network (1) modules (3) map-TS-Code (19) version21 (21)} +5871 +5872 BearerServiceCode, +5873 Ext-BearerServiceCode +5874 FROM MAP-BS-Code { +5875 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5876 gsm-Network (1) modules (3) map-BS-Code (20) version21 (21)} +5877 +5878 SS-Code +5879 FROM MAP-SS-Code { +5880 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5881 gsm-Network (1) modules (3) map-SS-Code (15) version21 (21)} +5882 +5883 ExtensionContainer +5884 FROM MAP-ExtensionDataTypes { +5885 itu-t identified-organization (4) etsi (0) mobileDomain (0) +5886 gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version21 (21)} +5887 ; +5888 +5889 +5890 -- general data types +5891 +5892 TBCD-STRING ::= OCTET STRING +5893 -- This type (Telephony Binary Coded Decimal String) is used to +5894 -- represent several digits from 0 through 9, *, #, a, b, c, two +5895 -- digits per octet, each digit encoded 0000 to 1001 (0 to 9), +5896 -- 1010 (*), 1011 (#), 1100 (a), 1101 (b) or 1110 (c); 1111 used +5897 -- as filler when there is an odd number of digits. +5898 +5899 -- bits 8765 of octet n encoding digit 2n +5900 -- bits 4321 of octet n encoding digit 2(n-1) +1 +5901 +5902 DiameterIdentity ::= OCTET STRING (SIZE(9..255)) +5903 -- content of DiameterIdentity is defined in IETF RFC 3588 [139] +5904 + +``` + +``` + +5905 AddressString ::= OCTET STRING (SIZE (1..maxAddressLength)) +5906 -- This type is used to represent a number for addressing +5907 -- purposes. It is composed of +5908 -- a) one octet for nature of address, and numbering plan +5909 -- indicator. +5910 -- b) digits of an address encoded as TBCD-String. +5911 +5912 -- a) The first octet includes a one bit extension indicator, a +5913 -- 3 bits nature of address indicator and a 4 bits numbering +5914 -- plan indicator, encoded as follows: +5915 +5916 -- bit 8: 1 (no extension) +5917 +5918 -- bits 765: nature of address indicator +5919 -- 000 unknown +5920 -- 001 international number +5921 -- 010 national significant number +5922 -- 011 network specific number +5923 -- 100 subscriber number +5924 -- 101 reserved +5925 -- 110 abbreviated number +5926 -- 111 reserved for extension +5927 +5928 -- bits 4321: numbering plan indicator +5929 -- 0000 unknown +5930 -- 0001 ISDN/Telephony Numbering Plan (Rec ITU-T E.164) +5931 -- 0010 spare +5932 -- 0011 data numbering plan (ITU-T Rec X.121) +5933 -- 0100 telex numbering plan (ITU-T Rec F.69) +5934 -- 0101 spare +5935 -- 0110 land mobile numbering plan (ITU-T Rec E.212) +5936 -- 0111 spare +5937 -- 1000 national numbering plan +5938 -- 1001 private numbering plan +5939 -- 1111 reserved for extension +5940 +5941 -- all other values are reserved. +5942 +5943 -- b) The following octets representing digits of an address +5944 -- encoded as a TBCD-STRING. + +``` + +5945 + +| | +|---------------------------------------------| +| 5946 maxAddressLength INTEGER ::= 20 | +|---------------------------------------------| + +5947 + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------| +| 5948 ISDN-AddressString ::= 5949 AddressString (SIZE (1..maxISDN-AddressLength)) 5950 -- This type is used to represent ISDN numbers. | +|----------------------------------------------------------------------------------------------------------------------------------------------| + +5951 + +| | +|-------------------------------------------------| +| 5952 maxISDN-AddressLength INTEGER ::= 9 | +|-------------------------------------------------| + +5953 + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5954 FTN-AddressString ::= 5955 AddressString (SIZE (1..maxFTN-AddressLength)) 5956 -- This type is used to represent forwarded-to numbers. 5957 -- If NAI = international the first digits represent the country code (CC) 5958 -- and the network destination code (NDC) as for E.164. | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +5959 + +| | +|-------------------------------------------------| +| 5960 maxFTN-AddressLength INTEGER ::= 15 | +|-------------------------------------------------| + +5961 + +``` + +5962 ISDN-SubaddressString ::= +5963 OCTET STRING (SIZE (1..maxISDN-SubaddressLength)) +5964 -- This type is used to represent ISDN subaddresses. +5965 -- It is composed of +5966 -- a) one octet for type of subaddress and odd/even indicator. +5967 -- b) 20 octets for subaddress information. +5968 +5969 -- a) The first octet includes a one bit extension indicator, a +5970 -- 3 bits type of subaddress and a one bit odd/even indicator, +5971 -- encoded as follows: +5972 +5973 -- bit 8: 1 (no extension) +5974 +5975 -- bits 765: type of subaddress +5976 -- 000 NSAP (X.213/ISO 8348 AD2) +5977 -- 010 User Specified +5978 -- All other values are reserved +5979 +5980 -- bit 4: odd/even indicator +5981 -- 0 even number of address signals +5982 -- 1 odd number of address signals +5983 -- The odd/even indicator is used when the type of subaddress +5984 -- is "user specified" and the coding is BCD. +5985 +5986 -- bits 321: 000 (unused) +5987 +5988 -- b) Subaddress information. +5989 -- The NSAP X.213/ISO8348AD2 address shall be formatted as specified +5990 -- by octet 4 which contains the Authority and Format Identifier +5991 -- (AFI). The encoding is made according to the "preferred binary +5992 -- encoding" as defined in X.213/ISO8348AD2. For the definition +5993 -- of this type of subaddress, see ITU-T Rec I.334. +5994 +5995 -- For User-specific subaddress, this field is encoded according +5996 -- to the user specification, subject to a maximum length of 20 +5997 -- octets. When interworking with X.25 networks BCD coding should +5998 -- be applied. +5999 +6000 maxISDN-SubaddressLength INTEGER ::= 21 +6001 +6002 ExternalSignalInfo ::= SEQUENCE { +6003 protocolId ProtocolId, +6004 signalInfo SignalInfo, +6005 -- Information about the internal structure is given in +6006 -- clause 7.6.9. +6007 extensionContainer ExtensionContainer OPTIONAL, +6008 -- extensionContainer must not be used in version 2 +6009 ...} +6010 +6011 SignalInfo ::= OCTET STRING (SIZE (1..maxSignalInfoLength)) +6012 +6013 maxSignalInfoLength INTEGER ::= 200 +6014 -- This NamedValue represents the theoretical maximum number of octets which is +6015 -- available to carry a single instance of the SignalInfo data type, +6016 -- without requiring segmentation to cope with the network layer service. +6017 -- However, the actual maximum size available for an instance of the data +6018 -- type may be lower, especially when other information elements +6019 -- have to be included in the same component. +6020 +6021 ProtocolId ::= ENUMERATED { +6022 gsm-0408 (1), +6023 gsm-0806 (2), +6024 gsm-BSSMAP (3), +6025 -- Value 3 is reserved and must not be used +6026 ets-300102-1 (4) } +6027 +6028 Ext-ExternalSignalInfo ::= SEQUENCE { +6029 ext-ProtocolId Ext-ProtocolId, +6030 signalInfo SignalInfo, +6031 -- Information about the internal structure is given in +6032 -- clause 7.6.9.10 +6033 extensionContainer ExtensionContainer OPTIONAL, +6034 ...} +6035 + +``` + +``` + +6036 Ext-ProtocolId ::= ENUMERATED { +6037 ets-300356 (1), +6038 ... +6039 } +6040 -- exception handling: +6041 -- For Ext-ExternalSignalInfo sequences containing this parameter with any +6042 -- other value than the ones listed the receiver shall ignore the whole +6043 -- Ext-ExternalSignalInfo sequence. +6044 +6045 AccessNetworkSignalInfo ::= SEQUENCE { +6046 accessNetworkProtocolId AccessNetworkProtocolId, +6047 signalInfo LongSignalInfo, +6048 -- Information about the internal structure is given in clause 7.6.9.1 +6049 +6050 extensionContainer ExtensionContainer OPTIONAL, +6051 ...} +6052 +6053 LongSignalInfo ::= OCTET STRING (SIZE (1..maxLongSignalInfoLength)) +6054 +6055 maxLongSignalInfoLength INTEGER ::= 2560 +6056 -- This Named Value represents the maximum number of octets which is available +6057 -- to carry a single instance of the LongSignalInfo data type using +6058 -- White Book SCCP with the maximum number of segments. +6059 -- It takes account of the octets used by the lower layers of the protocol, and +6060 -- other information elements which may be included in the same component. +6061 +6062 AccessNetworkProtocolId ::= ENUMERATED { +6063 ts3G-48006 (1), +6064 ts3G-25413 (2), +6065 ...} +6066 -- exception handling: +6067 -- For AccessNetworkSignalInfo sequences containing this parameter with any +6068 -- other value than the ones listed the receiver shall ignore the whole +6069 -- AccessNetworkSignalInfo sequence. +6070 +6071 AlertingPattern ::= OCTET STRING (SIZE (1) ) +6072 -- This type is used to represent Alerting Pattern +6073 +6074 -- bits 8765 : 0000 (unused) +6075 +6076 -- bits 43 : type of Pattern +6077 -- 00 level +6078 -- 01 category +6079 -- 10 category +6080 -- all other values are reserved. +6081 +6082 -- bits 21 : type of alerting +6083 +6084 alertingLevel-0 AlertingPattern ::= '00000000'B +6085 alertingLevel-1 AlertingPattern ::= '00000001'B +6086 alertingLevel-2 AlertingPattern ::= '00000010'B +6087 -- all other values of Alerting level are reserved +6088 -- Alerting Levels are defined in GSM 02.07 +6089 +6090 alertingCategory-1 AlertingPattern ::= '00000100'B +6091 alertingCategory-2 AlertingPattern ::= '00000101'B +6092 alertingCategory-3 AlertingPattern ::= '00000110'B +6093 alertingCategory-4 AlertingPattern ::= '00000111'B +6094 alertingCategory-5 AlertingPattern ::= '00001000'B +6095 -- all other values of Alerting Category are reserved +6096 -- Alerting categories are defined in GSM 02.07 +6097 +6098 GSN-Address ::= OCTET STRING (SIZE (5..17)) +6099 -- Octets are coded according to TS 3GPP TS 23.003 [17] +6100 +6101 Time ::= OCTET STRING (SIZE (4)) +6102 -- Octets are coded according to IETF RFC 3588 [139] +6103 +6104 +6105 -- data types for numbering and identification +6106 +6107 IMSI ::= TBCD-STRING (SIZE (3..8)) +6108 -- digits of MCC, MNC, MSIN are concatenated in this order. +6109 + +``` + +``` + +6110 Identity ::= CHOICE { +6111 imsi IMSI, +6112 imsi-WithLMSI IMSI-WithLMSI} +6113 +6114 IMSI-WithLMSI ::= SEQUENCE { +6115 imsi IMSI, +6116 lmsi LMSI, +6117 -- a special value 00000000 indicates that the LMSI is not in use +6118 ...} +6119 +6120 ASCI-CallReference ::= TBCD-STRING (SIZE (1..8)) +6121 -- digits of VGCS/VBS-area,Group-ID are concatenated in this order if there is a +6122 -- VGCS/VBS-area. +6123 +6124 TMSI ::= OCTET STRING (SIZE (1..4)) +6125 +6126 SubscriberId ::= CHOICE { +6127 imsi [0] IMSI, +6128 tmsi [1] TMSI} +6129 +6130 IMEI ::= TBCD-STRING (SIZE (8)) +6131 -- Refers to International Mobile Station Equipment Identity +6132 -- and Software Version Number (SVN) defined in TS 3GPP TS 23.003 [17]. +6133 -- If the SVN is not present the last octet shall contain the +6134 -- digit 0 and a filler. +6135 -- If present the SVN shall be included in the last octet. +6136 +6137 HLR-Id ::= IMSI +6138 -- leading digits of IMSI, i.e. (MCC, MNC, leading digits of +6139 -- MSIN) forming HLR Id defined in TS 3GPP TS 23.003 [17]. +6140 +6141 HLR-List ::= SEQUENCE SIZE (1..maxNumOfHLR-Id) OF +6142 HLR-Id +6143 +6144 maxNumOfHLR-Id INTEGER ::= 50 +6145 +6146 LMSI ::= OCTET STRING (SIZE (4)) +6147 +6148 GlobalCellId ::= OCTET STRING (SIZE (5..7)) +6149 -- Refers to Cell Global Identification defined in TS 3GPP TS 23.003 [17]. +6150 -- The internal structure is defined as follows: +6151 -- octet 1 bits 4321 Mobile Country Code 1st digit +6152 -- bits 8765 Mobile Country Code 2nd digit +6153 -- octet 2 bits 4321 Mobile Country Code 3rd digit +6154 -- bits 8765 Mobile Network Code 3rd digit +6155 -- or filler (1111) for 2 digit MNCs +6156 -- octet 3 bits 4321 Mobile Network Code 1st digit +6157 -- bits 8765 Mobile Network Code 2nd digit +6158 -- octets 4 and 5 Location Area Code according to TS 3GPP TS 24.008 +6159 [35] +6160 -- octets 6 and 7 Cell Identity (CI) according to TS 3GPP TS 24.008 +6161 [35] +6162 +6163 NetworkResource ::= ENUMERATED { +6164 plmn (0), +6165 hlr (1), +6166 vlr (2), +6167 pvlr (3), +6168 controllingMSC (4), +6169 vmsc (5), +6170 eir (6), +6171 rss (7)} +6172 +6173 AdditionalNetworkResource ::= ENUMERATED { +6174 sgsn (0), +6175 ggsn (1), +6176 gmlc (2), +6177 gsmSCF (3), +6178 nplr (4), +6179 auc (5), +6180 ... , +6181 ue (6), +6182 mme (7)} +6183 -- if unknown value is received in AdditionalNetworkResource +6184 -- it shall be ignored. +6185 +6186 + +``` + +``` + +6187 NAEA-PreferredCI := SEQUENCE { +6188 naea-PreferredCIC [0] NAEA-CIC, +6189 extensionContainer [1] ExtensionContainer OPTIONAL, +6190 ... } +6191 +6192 NAEA-CIC := OCTET STRING (SIZE (3)) +6193 -- The internal structure is defined by the Carrier Identification +6194 -- parameter in ANSI T1.113.3. Carrier codes between "000" and "999" may +6195 -- be encoded as 3 digits using "000" to "999" or as 4 digits using +6196 -- "0000" to "0999". Carrier codes between "1000" and "9999" are encoded +6197 -- using 4 digits. +6198 +6199 SubscriberIdentity := CHOICE { +6200 imsi [0] IMSI, +6201 msisdN [1] ISDN-AddressString +6202 } +6203 +6204 LCSCClientExternalID := SEQUENCE { +6205 externalAddress [0] ISDN-AddressString OPTIONAL, +6206 extensionContainer [1] ExtensionContainer OPTIONAL, +6207 ... } +6208 +6209 LCSCClientInternalID := ENUMERATED { +6210 broadcastService (0), +6211 o-andM-HPLMN (1), +6212 o-andM-VPLMN (2), +6213 anonymousLocation (3), +6214 targetMSsubscribedService (4), +6215 ... } +6216 -- for a CAMEL phase 3 PLMN operator client, the value targetMSsubscribedService shall be used +6217 +6218 LCSServiceTypeID := INTEGER (0..127) +6219 -- the integer values 0-63 are reserved for Standard LCS service types +6220 -- the integer values 64-127 are reserved for Non Standard LCS service types +6221 +6222 -- Standard LCS Service Types +6223 emergencyServices LCSServiceTypeID := 0 +6224 emergencyAlertServices LCSServiceTypeID := 1 +6225 personTrackingLCSServiceTypeID := 2 +6226 fleetManagement LCSServiceTypeID := 3 +6227 assetManagement LCSServiceTypeID := 4 +6228 trafficCongestionReporting LCSServiceTypeID := 5 +6229 roadsideAssistance LCSServiceTypeID := 6 +6230 routingToNearestCommercialEnterprise LCSServiceTypeID := 7 +6231 navigation LCSServiceTypeID := 8 +6232 --this service type is reserved for use in previous releases +6233 citySightseeing LCSServiceTypeID := 9 +6234 localizedAdvertising LCSServiceTypeID := 10 +6235 mobileYellowPages LCSServiceTypeID := 11 +6236 trafficAndPublicTransportationInfo LCSServiceTypeID := 12 +6237 weather LCSServiceTypeID := 13 +6238 assetAndServiceFinding LCSServiceTypeID := 14 +6239 gaming LCSServiceTypeID := 15 +6240 findYourFriendLCSServiceTypeID := 16 +6241 dating LCSServiceTypeID := 17 +6242 chatting LCSServiceTypeID := 18 +6243 routeFinding LCSServiceTypeID := 19 +6244 whereAmI LCSServiceTypeID := 20 +6245 +6246 -- The values of LCSServiceTypeID are defined according to 3GPP TS 22.071. +6247 + +``` + +``` + +6248 -- Non Standard LCS Service Types +6249 serv64 LCSServiceTypeID := 64 +6250 serv65 LCSServiceTypeID := 65 +6251 serv66 LCSServiceTypeID := 66 +6252 serv67 LCSServiceTypeID := 67 +6253 serv68 LCSServiceTypeID := 68 +6254 serv69 LCSServiceTypeID := 69 +6255 serv70 LCSServiceTypeID := 70 +6256 serv71 LCSServiceTypeID := 71 +6257 serv72 LCSServiceTypeID := 72 +6258 serv73 LCSServiceTypeID := 73 +6259 serv74 LCSServiceTypeID := 74 +6260 serv75 LCSServiceTypeID := 75 +6261 serv76 LCSServiceTypeID := 76 +6262 serv77 LCSServiceTypeID := 77 +6263 serv78 LCSServiceTypeID := 78 +6264 serv79 LCSServiceTypeID := 79 +6265 serv80 LCSServiceTypeID := 80 +6266 serv81 LCSServiceTypeID := 81 +6267 serv82 LCSServiceTypeID := 82 +6268 serv83 LCSServiceTypeID := 83 +6269 serv84 LCSServiceTypeID := 84 +6270 serv85 LCSServiceTypeID := 85 +6271 serv86 LCSServiceTypeID := 86 +6272 serv87 LCSServiceTypeID := 87 +6273 serv88 LCSServiceTypeID := 88 +6274 serv89 LCSServiceTypeID := 89 +6275 serv90 LCSServiceTypeID := 90 +6276 serv91 LCSServiceTypeID := 91 +6277 serv92 LCSServiceTypeID := 92 +6278 serv93 LCSServiceTypeID := 93 +6279 serv94 LCSServiceTypeID := 94 +6280 serv95 LCSServiceTypeID := 95 +6281 serv96 LCSServiceTypeID := 96 +6282 serv97 LCSServiceTypeID := 97 +6283 serv98 LCSServiceTypeID := 98 +6284 serv99 LCSServiceTypeID := 99 +6285 serv100 LCSServiceTypeID := 100 +6286 serv101 LCSServiceTypeID := 101 +6287 serv102 LCSServiceTypeID := 102 +6288 serv103 LCSServiceTypeID := 103 +6289 serv104 LCSServiceTypeID := 104 +6290 serv105 LCSServiceTypeID := 105 +6291 serv106 LCSServiceTypeID := 106 +6292 serv107 LCSServiceTypeID := 107 +6293 serv108 LCSServiceTypeID := 108 +6294 serv109 LCSServiceTypeID := 109 +6295 serv110 LCSServiceTypeID := 110 +6296 serv111 LCSServiceTypeID := 111 +6297 serv112 LCSServiceTypeID := 112 +6298 serv113 LCSServiceTypeID := 113 +6299 serv114 LCSServiceTypeID := 114 +6300 serv115 LCSServiceTypeID := 115 +6301 serv116 LCSServiceTypeID := 116 +6302 serv117 LCSServiceTypeID := 117 +6303 serv118 LCSServiceTypeID := 118 +6304 serv119 LCSServiceTypeID := 119 +6305 serv120 LCSServiceTypeID := 120 +6306 serv121 LCSServiceTypeID := 121 +6307 serv122 LCSServiceTypeID := 122 +6308 serv123 LCSServiceTypeID := 123 +6309 serv124 LCSServiceTypeID := 124 +6310 serv125 LCSServiceTypeID := 125 +6311 serv126 LCSServiceTypeID := 126 +6312 serv127 LCSServiceTypeID := 127 + +``` + +6313 + +``` + +6314 PLMN-Id := OCTET STRING (SIZE (3)) +6315 -- The internal structure is defined as follows: +6316 -- octet 1 bits 4321 Mobile Country Code 1st digit +6317 -- bits 8765 Mobile Country Code 2nd digit +6318 -- octet 2 bits 4321 Mobile Country Code 3rd digit +6319 -- bits 8765 Mobile Network Code 3rd digit +6320 -- or filler (1111) for 2 digit MNCs +6321 -- octet 3 bits 4321 Mobile Network Code 1st digit +6322 -- bits 8765 Mobile Network Code 2nd digit + +``` + +6323 + +``` + +6324 E-UTRAN-CGI := OCTET STRING (SIZE (7)) +6325 -- Octets are coded as described in 3GPP TS 29.118 [152]. +6326 +6327 NR-CGI := OCTET STRING (SIZE (8)) +6328 -- Octets are coded as described in 3GPP TS 38.413 [153]. +6329 +6330 TA-Id := OCTET STRING (SIZE (5)) +6331 -- Octets are coded as described in 3GPP TS 29.118 [152]. +6332 +6333 NR-TA-Id := OCTET STRING (SIZE (6)) +6334 -- Octets are coded as described in 3GPP TS 38.413 [153]. +6335 +6336 RAIdentity := OCTET STRING (SIZE (6)) +6337 -- Routing Area Identity is coded in accordance with 3GPP TS 29.060 [105]. +6338 -- It shall contain the value part defined in 3GPP TS 29.060 only. I.e. the 3GPP TS 29.060 +6339 -- type identifier octet shall not be included. +6340 +6341 NetworkNodeDiameterAddress := SEQUENCE { +6342 diameter-Name [0] DiameterIdentity, +6343 diameter-Realm [1] DiameterIdentity } +6344 +6345 -- data types for CAMEL +6346 +6347 CellGlobalIdOrServiceAreaIdOrLAI := CHOICE { +6348 cellGlobalIdOrServiceAreaIdFixedLength [0] CellGlobalIdOrServiceAreaIdFixedLength, +6349 laiFixedLength [1] LAIFixedLength} +6350 +6351 CellGlobalIdOrServiceAreaIdFixedLength := OCTET STRING (SIZE (7)) +6352 -- Refers to Cell Global Identification or Service Area Identification +6353 -- defined in 3GPP TS 23.003. +6354 -- The internal structure is defined as follows: +6355 -- octet 1 bits 4321 Mobile Country Code 1st digit +6356 -- bits 8765 Mobile Country Code 2nd digit +6357 -- octet 2 bits 4321 Mobile Country Code 3rd digit +6358 -- bits 8765 Mobile Network Code 3rd digit +6359 -- or filler (1111) for 2 digit MNCs +6360 -- octet 3 bits 4321 Mobile Network Code 1st digit +6361 -- bits 8765 Mobile Network Code 2nd digit +6362 -- octets 4 and 5 Location Area Code according to 3GPP TS 24.008 +6363 -- octets 6 and 7 Cell Identity (CI) value or +6364 -- Service Area Code (SAC) value +6365 -- according to 3GPP TS 23.003 +6366 +6367 LAIFixedLength := OCTET STRING (SIZE (5)) +6368 -- Refers to Location Area Identification defined in 3GPP TS 23.003 [17]. +6369 -- The internal structure is defined as follows: +6370 -- octet 1 bits 4321 Mobile Country Code 1st digit +6371 -- bits 8765 Mobile Country Code 2nd digit +6372 -- octet 2 bits 4321 Mobile Country Code 3rd digit +6373 -- bits 8765 Mobile Network Code 3rd digit +6374 -- or filler (1111) for 2 digit MNCs +6375 -- octet 3 bits 4321 Mobile Network Code 1st digit +6376 -- bits 8765 Mobile Network Code 2nd digit +6377 -- octets 4 and 5 Location Area Code according to 3GPP TS 24.008 [35] +6378 +6379 -- data types for subscriber management +6380 +6381 BasicServiceCode := CHOICE { +6382 bearerService [2] BearerServiceCode, +6383 teleservice [3] TeleserviceCode} +6384 +6385 Ext-BasicServiceCode := CHOICE { +6386 ext-BearerService [2] Ext-BearerServiceCode, +6387 ext-Teleservice [3] Ext-TeleserviceCode} +6388 +6389 EMLPP-Info := SEQUENCE { +6390 maximumUntitledPriority EMLPP-Priority, +6391 defaultPriority EMLPP-Priority, +6392 extensionContainer ExtensionContainer OPTIONAL, +6393 ...} +6394 +6395 EMLPP-Priority := INTEGER (0..15) +6396 -- The mapping from the values A,B,0,1,2,3,4 to the integer-value is +6397 -- specified as follows where A is the highest and 4 is the lowest +6398 -- priority level +6399 -- the integer values 7-15 are spare and shall be mapped to value 4 +6400 + +``` + +``` + +6401 priorityLevelA EMLPP-Priority := 6 +6402 priorityLevelB EMLPP-Priority := 5 +6403 priorityLevel0 EMLPP-Priority := 0 +6404 priorityLevel1 EMLPP-Priority := 1 +6405 priorityLevel2 EMLPP-Priority := 2 +6406 priorityLevel3 EMLPP-Priority := 3 +6407 priorityLevel4 EMLPP-Priority := 4 +6408 +6409 MC-SS-Info := SEQUENCE { +6410 ss-Code [0] SS-Code, +6411 ss-Status [1] Ext-SS-Status, +6412 nbrSB [2] MaxMC-Bearers, +6413 nbrUser [3] MC-Bearers, +6414 extensionContainer [4] ExtensionContainer OPTIONAL, +6415 } +6416 +6417 MaxMC-Bearers := INTEGER (2..maxNumOfMC-Bearers) +6418 +6419 MC-Bearers := INTEGER (1..maxNumOfMC-Bearers) +6420 +6421 maxNumOfMC-Bearers INTEGER := 7 +6422 +6423 Ext-SS-Status := OCTET STRING (SIZE (1..5)) +6424 +6425 -- OCTET 1: +6426 -- +6427 -- bits 8765: 0000 (unused) +6428 -- bits 4321: Used to convey the "P bit", "R bit", "A bit" and "Q bit", +6429 -- representing supplementary service state information +6430 -- as defined in TS 3GPP TS 23.011 [22] +6431 +6432 -- bit 4: "Q bit" +6433 +6434 -- bit 3: "P bit" +6435 +6436 -- bit 2: "R bit" +6437 +6438 -- bit 1: "A bit" +6439 +6440 -- OCTETS 2-5: reserved for future use. They shall be discarded if +6441 -- received and not understood. +6442 +6443 +6444 -- data types for geographic location +6445 +6446 AgeOfLocationInformation := INTEGER (0..32767) +6447 -- the value represents the elapsed time in minutes since the last +6448 -- network contact of the mobile station (i.e. the actuality of the +6449 -- location information). +6450 -- value "0" indicates that the MS is currently in contact with the +6451 -- network +6452 -- value "32767" indicates that the location information is at least +6453 -- 32767 minutes old +6454 +6455 END + +``` + +## 6456 17.7.9 Teleservice Codes + +``` + +6457 MAP-TS-Code { +6458 itu-t identified-organization (4) etsi (0) mobileDomain (0) +6459 gsm-Network (1) modules (3) map-TS-Code (19) version21 (21)} +6460 +6461 DEFINITIONS +6462 +6463 ::= +6464 +6465 BEGIN +6466 +6467 TeleserviceCode := OCTET STRING (SIZE (1)) +6468 -- This type is used to represent the code identifying a single +6469 -- teleservice, a group of teleservices, or all teleservices. The +6470 -- services are defined in TS GSM 22.003 [4]. +6471 -- The internal structure is defined as follows: +6472 +6473 -- bits 87654321: group (bits 8765) and specific service +6474 -- (bits 4321) +6475 + +``` + +``` + +6476 Ext-TeleserviceCode ::= OCTET STRING (SIZE (1..5)) +6477 -- This type is used to represent the code identifying a single +6478 -- teleservice, a group of teleservices, or all teleservices. The +6479 -- services are defined in TS GSM 22.003 [4]. +6480 -- The internal structure is defined as follows: +6481 +6482 -- OCTET 1: +6483 -- bits 87654321: group (bits 8765) and specific service +6484 -- (bits 4321) +6485 +6486 -- OCTETS 2-5: reserved for future use. If received the +6487 -- Ext-TeleserviceCode shall be +6488 -- treated according to the exception handling defined for the +6489 -- operation that uses this type. +6490 +6491 -- Ext-TeleserviceCode includes all values defined for TeleserviceCode. +6492 +6493 allTeleservices TeleserviceCode ::= '00000000'B +6494 +6495 allSpeechTransmissionServices TeleserviceCode ::= '00010000'B +6496 telephony TeleserviceCode ::= '00010001'B +6497 emergencyCalls TeleserviceCode ::= '00010010'B +6498 +6499 allShortMessageServices TeleserviceCode ::= '00100000'B +6500 shortMessageMT-PP TeleserviceCode ::= '00100001'B +6501 shortMessageMO-PP TeleserviceCode ::= '00100010'B +6502 +6503 allFacsimileTransmissionServices TeleserviceCode ::= '01100000'B +6504 facsimileGroup3AndAlterSpeech TeleserviceCode ::= '01100001'B +6505 automaticFacsimileGroup3 TeleserviceCode ::= '01100010'B +6506 facsimileGroup4 TeleserviceCode ::= '01100011'B +6507 +6508 -- The following non-hierarchical Compound Teleservice Groups +6509 -- are defined in TS 3GPP TS 22.030: +6510 allDataTeleservices TeleserviceCode ::= '01110000'B +6511 -- covers Teleservice Groups 'allFacsimileTransmissionServices' +6512 -- and 'allShortMessageServices' +6513 allTeleservices-ExceptSMS TeleserviceCode ::= '10000000'B +6514 -- covers Teleservice Groups 'allSpeechTransmissionServices' and +6515 -- 'allFacsimileTransmissionServices' +6516 -- +6517 -- Compound Teleservice Group Codes are only used in call +6518 -- independent supplementary service operations, i.e. they +6519 -- are not used in InsertSubscriberData or in +6520 -- DeleteSubscriberData messages. +6521 +6522 allVoiceGroupCallServices TeleserviceCode ::= '10010000'B +6523 voiceGroupCall TeleserviceCode ::= '10010001'B +6524 voiceBroadcastCall TeleserviceCode ::= '10010010'B +6525 +6526 allPLMN-specificTS TeleserviceCode ::= '11010000'B +6527 plmn-specificTS-1 TeleserviceCode ::= '11010001'B +6528 plmn-specificTS-2 TeleserviceCode ::= '11010010'B +6529 plmn-specificTS-3 TeleserviceCode ::= '11010011'B +6530 plmn-specificTS-4 TeleserviceCode ::= '11010100'B +6531 plmn-specificTS-5 TeleserviceCode ::= '11010101'B +6532 plmn-specificTS-6 TeleserviceCode ::= '11010110'B +6533 plmn-specificTS-7 TeleserviceCode ::= '11010111'B +6534 plmn-specificTS-8 TeleserviceCode ::= '11011000'B +6535 plmn-specificTS-9 TeleserviceCode ::= '11011001'B +6536 plmn-specificTS-A TeleserviceCode ::= '11011010'B +6537 plmn-specificTS-B TeleserviceCode ::= '11011011'B +6538 plmn-specificTS-C TeleserviceCode ::= '11011100'B +6539 plmn-specificTS-D TeleserviceCode ::= '11011101'B +6540 plmn-specificTS-E TeleserviceCode ::= '11011110'B +6541 plmn-specificTS-F TeleserviceCode ::= '11011111'B +6542 +6543 END + +``` + +## 6544 17.7.10 Bearer Service Codes + +``` + +6545 MAP-BS-Code { +6546 itu-t identified-organization (4) etsi (0) mobileDomain (0) +6547 gsm-Network (1) modules (3) map-BS-Code (20) version21 (21)} +6548 +6549 DEFINITIONS +6550 + +``` + +``` + +6551 ::= +6552 +6553 BEGIN +6554 +6555 BearerServiceCode ::= OCTET STRING (SIZE (1)) +6556 -- This type is used to represent the code identifying a single +6557 -- bearer service, a group of bearer services, or all bearer +6558 -- services. The services are defined in TS 3GPP TS 22.002 [3]. +6559 -- The internal structure is defined as follows: +6560 -- +6561 -- plmn-specific bearer services: +6562 -- bits 87654321: defined by the HPLMN operator +6563 +6564 -- rest of bearer services: +6565 -- bit 8: 0 (unused) +6566 -- bits 7654321: group (bits 7654), and rate, if applicable +6567 -- (bits 321) +6568 +6569 Ext-BearerServiceCode ::= OCTET STRING (SIZE (1..5)) +6570 -- This type is used to represent the code identifying a single +6571 -- bearer service, a group of bearer services, or all bearer +6572 -- services. The services are defined in TS 3GPP TS 22.002 [3]. +6573 -- The internal structure is defined as follows: +6574 -- +6575 -- OCTET 1: +6576 -- plmn-specific bearer services: +6577 -- bits 87654321: defined by the HPLMN operator +6578 -- +6579 -- rest of bearer services: +6580 -- bit 8: 0 (unused) +6581 -- bits 7654321: group (bits 7654), and rate, if applicable +6582 -- (bits 321) +6583 +6584 -- OCTETS 2-5: reserved for future use. If received the +6585 -- Ext-TeleserviceCode shall be +6586 -- treated according to the exception handling defined for the +6587 -- operation that uses this type. +6588 +6589 +6590 -- Ext-BearerServiceCode includes all values defined for BearerServiceCode. +6591 +6592 allBearerServices BearerServiceCode ::= '00000000'B +6593 +6594 allDataCDA-Services BearerServiceCode ::= '00010000'B +6595 dataCDA-300bps BearerServiceCode ::= '00010001'B +6596 dataCDA-1200bps BearerServiceCode ::= '00010010'B +6597 dataCDA-1200-75bps BearerServiceCode ::= '00010011'B +6598 dataCDA-2400bps BearerServiceCode ::= '00010100'B +6599 dataCDA-4800bps BearerServiceCode ::= '00010101'B +6600 dataCDA-9600bps BearerServiceCode ::= '00010110'B +6601 general-dataCDA BearerServiceCode ::= '00010111'B +6602 +6603 allDataCDS-Services BearerServiceCode ::= '00011000'B +6604 dataCDS-1200bps BearerServiceCode ::= '00011010'B +6605 dataCDS-2400bps BearerServiceCode ::= '00011100'B +6606 dataCDS-4800bps BearerServiceCode ::= '00011101'B +6607 dataCDS-9600bps BearerServiceCode ::= '00011110'B +6608 general-dataCDS BearerServiceCode ::= '00011111'B +6609 +6610 allPadAccessCA-Services BearerServiceCode ::= '00100000'B +6611 padAccessCA-300bps BearerServiceCode ::= '00100001'B +6612 padAccessCA-1200bps BearerServiceCode ::= '00100010'B +6613 padAccessCA-1200-75bps BearerServiceCode ::= '00100011'B +6614 padAccessCA-2400bps BearerServiceCode ::= '00100100'B +6615 padAccessCA-4800bps BearerServiceCode ::= '00100101'B +6616 padAccessCA-9600bps BearerServiceCode ::= '00100110'B +6617 general-padAccessCA BearerServiceCode ::= '00100111'B +6618 +6619 allDataPDS-Services BearerServiceCode ::= '00101000'B +6620 dataPDS-2400bps BearerServiceCode ::= '00101100'B +6621 dataPDS-4800bps BearerServiceCode ::= '00101101'B +6622 dataPDS-9600bps BearerServiceCode ::= '00101110'B +6623 general-dataPDS BearerServiceCode ::= '00101111'B +6624 +6625 allAlternateSpeech-DataCDA BearerServiceCode ::= '00110000'B +6626 +6627 allAlternateSpeech-DataCDS BearerServiceCode ::= '00111000'B + +``` + +``` + +6628 +6629 allSpeechFollowedByDataCDA BearerServiceCode ::= '01000000'B +6630 +6631 allSpeechFollowedByDataCDS BearerServiceCode ::= '01001000'B +6632 +6633 -- The following non-hierarchical Compound Bearer Service +6634 -- Groups are defined in TS 3GPP TS 22.030: +6635 allDataCircuitAsynchronous BearerServiceCode ::= '01010000'B +6636 -- covers "allDataCDA-Services", "allAlternateSpeech-DataCDA" and +6637 -- "allSpeechFollowedByDataCDA" +6638 allAsynchronousServices BearerServiceCode ::= '01100000'B +6639 -- covers "allDataCDA-Services", "allAlternateSpeech-DataCDA", +6640 -- "allSpeechFollowedByDataCDA" and "allPadAccessCDA-Services" +6641 allDataCircuitSynchronous BearerServiceCode ::= '01011000'B +6642 -- covers "allDataCDS-Services", "allAlternateSpeech-DataCDS" and +6643 -- "allSpeechFollowedByDataCDS" +6644 allSynchronousServices BearerServiceCode ::= '01101000'B +6645 -- covers "allDataCDS-Services", "allAlternateSpeech-DataCDS", +6646 -- "allSpeechFollowedByDataCDS" and "allDataPDS-Services" +6647 -- +6648 -- Compound Bearer Service Group Codes are only used in call +6649 -- independent supplementary service operations, i.e. they +6650 -- are not used in InsertSubscriberData or in +6651 -- DeleteSubscriberData messages. +6652 +6653 allPLMN-specificBS BearerServiceCode ::= '11010000'B +6654 plmn-specificBS-1 BearerServiceCode ::= '11010001'B +6655 plmn-specificBS-2 BearerServiceCode ::= '11010010'B +6656 plmn-specificBS-3 BearerServiceCode ::= '11010011'B +6657 plmn-specificBS-4 BearerServiceCode ::= '11010100'B +6658 plmn-specificBS-5 BearerServiceCode ::= '11010101'B +6659 plmn-specificBS-6 BearerServiceCode ::= '11010110'B +6660 plmn-specificBS-7 BearerServiceCode ::= '11010111'B +6661 plmn-specificBS-8 BearerServiceCode ::= '11011000'B +6662 plmn-specificBS-9 BearerServiceCode ::= '11011001'B +6663 plmn-specificBS-A BearerServiceCode ::= '11011010'B +6664 plmn-specificBS-B BearerServiceCode ::= '11011011'B +6665 plmn-specificBS-C BearerServiceCode ::= '11011100'B +6666 plmn-specificBS-D BearerServiceCode ::= '11011101'B +6667 plmn-specificBS-E BearerServiceCode ::= '11011110'B +6668 plmn-specificBS-F BearerServiceCode ::= '11011111'B +6669 +6670 END + +``` + +## 6671 17.7.11 Extension data types + +``` + +6672 MAP-ExtensionDataTypes { +6673 itu-t identified-organization (4) etsi (0) mobileDomain (0) +6674 gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version21 (21)} +6675 +6676 DEFINITIONS +6677 +6678 IMPLICIT TAGS +6679 +6680 ::= +6681 +6682 BEGIN +6683 +6684 EXPORTS +6685 +6686 PrivateExtension, +6687 ExtensionContainer, +6688 SLR-ArgExtensionContainer; +6689 +6690 +6691 -- IOC for private MAP extensions +6692 +6693 +6694 MAP-EXTENSION ::= CLASS { +6695 &ExtensionType OPTIONAL, +6696 &extensionId OBJECT IDENTIFIER } +6697 -- The length of the Object Identifier shall not exceed 16 octets and the +6698 -- number of components of the Object Identifier shall not exceed 16 +6699 +6700 -- data types +6701 + +``` + +``` + +6702 ExtensionContainer ::= SEQUENCE { +6703 privateExtensionList [0] PrivateExtensionList OPTIONAL, +6704 pcs-Extensions [1] PCS-Extensions OPTIONAL, +6705 ... } +6706 +6707 SLR-ArgExtensionContainer ::= SEQUENCE { +6708 privateExtensionList [0] PrivateExtensionList OPTIONAL, +6709 slr-Arg-PCS-Extensions [1] SLR-Arg-PCS-Extensions OPTIONAL, +6710 ... } +6711 +6712 PrivateExtensionList ::= SEQUENCE SIZE (1..maxNumOfPrivateExtensions) OF +6713 PrivateExtension +6714 +6715 PrivateExtension ::= SEQUENCE { +6716 extId MAP-EXTENSION.&extensionId +6717 ({ExtensionSet}), +6718 extType MAP-EXTENSION.&ExtensionType +6719 ({ExtensionSet}{@extId}) OPTIONAL} +6720 +6721 maxNumOfPrivateExtensions INTEGER ::= 10 +6722 +6723 ExtensionSet MAP-EXTENSION ::= +6724 { ... +6725 -- ExtensionSet is the set of all defined private extensions +6726 } +6727 -- Unsupported private extensions shall be discarded if received. +6728 +6729 PCS-Extensions ::= SEQUENCE { +6730 ... } +6731 +6732 SLR-Arg-PCS-Extensions ::= SEQUENCE { +6733 ..., +6734 na-ESRK-Request [0] NULL OPTIONAL } +6735 +6736 END +6737 + +``` + +## 6738 17.7.12 Group Call data types + +``` + +6739 MAP-GR-DataTypes { +6740 itu-t identified-organization (4) etsi (0) mobileDomain (0) +6741 gsm-Network (1) modules (3) map-GR-DataTypes (23) version21 (21)} +6742 +6743 DEFINITIONS +6744 +6745 IMPLICIT TAGS +6746 +6747 ::= +6748 +6749 BEGIN +6750 +6751 EXPORTS +6752 PrepareGroupCallArg, +6753 PrepareGroupCallRes, +6754 SendGroupCallEndSignalArg, +6755 SendGroupCallEndSignalRes, +6756 ForwardGroupCallSignallingArg, +6757 ProcessGroupCallSignallingArg, +6758 SendGroupCallInfoArg, +6759 SendGroupCallInfoRes +6760 ; +6761 +6762 IMPORTS +6763 ISDN-AddressString, +6764 IMSI, +6765 TMSI, +6766 EMLPP-Priority, +6767 ASCI-CallReference, +6768 SignalInfo, +6769 GlobalCellId, +6770 AccessNetworkSignalInfo +6771 FROM MAP-CommonDataTypes { +6772 itu-t identified-organization (4) etsi (0) mobileDomain (0) +6773 gsm-Network (1) modules (3) map-CommonDataTypes (18) version21 (21)} +6774 +6775 Ext-TeleserviceCode +6776 FROM MAP-TS-Code { + +``` + +``` + +6777 itu-t identified-organization (4) etsi (0) mobileDomain (0) +6778 gsm-Network (1) modules (3) map-TS-Code (19) version21 (21)} +6779 +6780 Kc, +6781 AdditionalInfo, +6782 GroupId, +6783 Long-GroupId, +6784 AdditionalSubscriptions, +6785 Cksn +6786 FROM MAP-MS-DataTypes { +6787 itu-t identified-organization (4) etsi (0) mobileDomain (0) +6788 gsm-Network (1) modules (3) map-MS-DataTypes (11) version21 (21)} +6789 +6790 ExtensionContainer +6791 FROM MAP-ExtensionDataTypes { +6792 itu-t identified-organization (4) etsi (0) mobileDomain (0) +6793 gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version21 (21)} +6794 ; +6795 +6796 + +``` + +``` + +6797 PrepareGroupCallArg ::= SEQUENCE { +6798 teleservice Ext-TeleserviceCode, +6799 asciCallReference ASCI-CallReference, +6800 codec-Info CODEC-Info, +6801 cipheringAlgorithm CipheringAlgorithm, +6802 groupKeyNumber-Vk-Id [0] GroupKeyNumber OPTIONAL, +6803 groupKey [1] Kc OPTIONAL, +6804 -- this parameter shall not be sent and shall be discarded if received +6805 priority [2] EMLPP-Priority OPTIONAL, +6806 uplinkFree [3] NULL OPTIONAL, +6807 extensionContainer [4] ExtensionContainer OPTIONAL, +6808 ..., +6809 vstk [5] VSTK OPTIONAL, +6810 vstk-rand [6] VSTK-RAND OPTIONAL, +6811 talkerChannelParameter [7] NULL OPTIONAL, +6812 uplinkReplyIndicator [8] NULL OPTIONAL} + +``` + +``` + +6813 +6814 VSTK ::= OCTET STRING (SIZE (16)) + +``` + +``` + +6815 +6816 VSTK-RAND ::= OCTET STRING (SIZE (5)) +6817 -- The 36 bit value is carried in bit 7 of octet 1 to bit 4 of octet 5 +6818 -- bits 3, 2, 1, and 0 of octet 5 are padded with zeros. + +``` + +``` + +6819 +6820 PrepareGroupCallRes ::= SEQUENCE { +6821 groupCallNumber ISDN-AddressString, +6822 extensionContainer ExtensionContainer OPTIONAL, +6823 ...} + +``` + +``` + +6824 +6825 SendGroupCallEndSignalArg ::= SEQUENCE { +6826 imsi IMSI OPTIONAL, +6827 extensionContainer ExtensionContainer OPTIONAL, +6828 ..., +6829 talkerPriority [0] TalkerPriority OPTIONAL, +6830 additionalInfo [1] AdditionalInfo OPTIONAL } + +``` + +``` + +6831 +6832 TalkerPriority ::= ENUMERATED { +6833 normal (0), +6834 privileged (1), +6835 emergency (2)} + +``` + +``` + +6836 +6837 SendGroupCallEndSignalRes ::= SEQUENCE { +6838 extensionContainer ExtensionContainer OPTIONAL, +6839 ...} + +``` + +``` + +6840 + +``` + +``` + +6841 ForwardGroupCallSignallingArg ::= SEQUENCE { +6842 imsi IMSI OPTIONAL, +6843 uplinkRequestAck [0] NULL OPTIONAL, +6844 uplinkReleaseIndication [1] NULL OPTIONAL, +6845 uplinkRejectCommand [2] NULL OPTIONAL, +6846 uplinkSeizedCommand [3] NULL OPTIONAL, +6847 uplinkReleaseCommand [4] NULL OPTIONAL, +6848 extensionContainer ExtensionContainer OPTIONAL, +6849 ..., +6850 stateAttributes [5] StateAttributes OPTIONAL, +6851 talkerPriority [6] TalkerPriority OPTIONAL, +6852 additionalInfo [7] AdditionalInfo OPTIONAL, +6853 emergencyModeResetCommandFlag [8] NULL OPTIONAL, +6854 sm-RP-UI [9] SignalInfo OPTIONAL, +6855 an-APDU [10] AccessNetworkSignalInfo OPTIONAL +6856 } +6857 +6858 ProcessGroupCallSignallingArg ::= SEQUENCE { +6859 uplinkRequest [0] NULL OPTIONAL, +6860 uplinkReleaseIndication [1] NULL OPTIONAL, +6861 releaseGroupCall [2] NULL OPTIONAL, +6862 extensionContainer ExtensionContainer OPTIONAL, +6863 ..., +6864 talkerPriority [3] TalkerPriority OPTIONAL, +6865 additionalInfo [4] AdditionalInfo OPTIONAL, +6866 emergencyModeResetCommandFlag [5] NULL OPTIONAL, +6867 an-APDU [6] AccessNetworkSignalInfo OPTIONAL } +6868 +6869 GroupKeyNumber ::= INTEGER (0..15) +6870 +6871 CODEC-Info ::= OCTET STRING (SIZE (5..10)) +6872 -- Refers to channel type +6873 -- coded according to 3GPP TS 48.008 [49] and including Element identifier and Length +6874 +6875 CipheringAlgorithm ::= OCTET STRING (SIZE (1)) +6876 -- Refers to 'permitted algorithms' in 'encryption information' +6877 -- coded according to 3GPP TS 48.008 [49]: +6878 +6879 -- Bits 8-1 +6880 -- 8765 4321 +6881 -- 0000 0001 No encryption +6882 -- 0000 0010 GSM A5/1 +6883 -- 0000 0100 GSM A5/2 +6884 -- 0000 1000 GSM A5/3 +6885 -- 0001 0000 GSM A5/4 +6886 -- 0010 0000 GSM A5/5 +6887 -- 0100 0000 GSM A5/6 +6888 -- 1000 0000 GSM A5/7 +6889 +6890 StateAttributes ::= SEQUENCE { +6891 downlinkAttached [5] NULL OPTIONAL, +6892 uplinkAttached [6] NULL OPTIONAL, +6893 dualCommunication [7] NULL OPTIONAL, +6894 callOriginator [8] NULL OPTIONAL } +6895 +6896 -- Refers to 3GPP TS 44.068 for definitions of StateAttributes fields. +6897 +6898 +6899 SendGroupCallInfoArg ::= SEQUENCE { +6900 requestedInfo RequestedInfo, +6901 groupId Long-GroupId, +6902 teleservice Ext-TeleserviceCode, +6903 cellId [0] GlobalCellId OPTIONAL, +6904 imsi [1] IMSI OPTIONAL, +6905 tmsi [2] TMSI OPTIONAL, +6906 additionalInfo [3] AdditionalInfo OPTIONAL, +6907 talkerPriority [4] TalkerPriority OPTIONAL, +6908 cksn [5] Cksn OPTIONAL, +6909 extensionContainer [6] ExtensionContainer OPTIONAL, +6910 ... } +6911 + +``` + +``` + +6912 RequestedInfo ::= ENUMERATED { +6913 anchorMSC-AddressAndASCI-CallReference (0), +6914 imsiAndAdditionalInfoAndAdditionalSubscription(1), +6915 ... } +6916 -- exception handling: +6917 -- an unrecognized value shall be rejected by the receiver with a return error cause of +6918 -- unexpected data value +6919 +6920 SendGroupCallInfoRes ::= SEQUENCE { +6921 anchorMSC-Address [0] ISDN-AddressString OPTIONAL, +6922 asciCallReference [1] ASCI-CallReference OPTIONAL, +6923 imsi [2] IMSI OPTIONAL, +6924 additionalInfo [3] AdditionalInfo OPTIONAL, +6925 additionalSubscriptions [4] AdditionalSubscriptions OPTIONAL, +6926 kc [5] Kc OPTIONAL, +6927 extensionContainer [6] ExtensionContainer OPTIONAL, +6928 ... } +6929 +6930 +6931 END + +``` + +## 6932 17.7.13 Location service data types + +``` + +1 MAP-LCS-DataTypes { +2 itu-t identified-organization (4) etsi (0) mobileDomain (0) +3 gsm-Network (1) modules (3) map-LCS-DataTypes (25) version21 (21)} +4 +5 DEFINITIONS +6 IMPLICIT TAGS +7 ::= +8 BEGIN +9 +10 EXPORTS +11 RoutingInfoForLCS-Arg, +12 RoutingInfoForLCS-Res, +13 ProvideSubscriberLocation-Arg, +14 ProvideSubscriberLocation-Res, +15 SubscriberLocationReport-Arg, +16 SubscriberLocationReport-Res, +17 LocationType, +18 DeferredLocationEventType, +19 LCSClientName, +20 LCS-QoS, +21 Horizontal-Accuracy, +22 ResponseTime, +23 Ext-GeographicalInformation, +24 VelocityEstimate, +25 SupportedGADShapes, +26 Add-GeographicalInformation, +27 LCSRequestorID, +28 LCS-ReferenceNumber, +29 LCSCodeword, +30 AreaEventInfo, +31 ReportingPLMNList, +32 PeriodicLDRInfo, +33 SequenceNumber, +34 LCSClientType, +35 LCS-Priority, +36 OccurrenceInfo, +37 IntervalTime +38 ; +39 +40 IMPORTS +41 AddressString, +42 ISDN-AddressString, +43 IMEI, +44 IMSI, +45 LMSI, +46 SubscriberIdentity, +47 AgeOfLocationInformation, +48 LCSClientExternalID, +49 LCSClientInternalID, +50 LCSServiceTypeID, +51 CellGlobalIdOrServiceAreaIdOrLAI, +52 PLMN-Id, +53 GSN-Address, +54 DiameterIdentity + +``` + +``` + +55 FROM MAP-CommonDataTypes { +56 itu-t identified-organization (4) etsi (0) mobileDomain (0) +57 gsm-Network (1) modules (3) map-CommonDataTypes (18) version21 (21)} +58 +59 ExtensionContainer, +60 SLR-ArgExtensionContainer +61 FROM MAP-ExtensionDataTypes { +62 itu-t identified-organization (4) etsi (0) mobileDomain (0) +63 gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version21 (21)} +64 +65 USSD-DataCodingScheme, +66 USSD-String +67 FROM MAP-SS-DataTypes { +68 itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) +69 map-SS-DataTypes (14) version21 (21)} +70 +71 APN, +72 SupportedLCS-CapabilitySets +73 FROM MAP-MS-DataTypes { +74 itu-t identified-organization (4) etsi (0) mobileDomain (0) +75 gsm-Network (1) modules (3) map-MS-DataTypes (11) version21 (21)} +76 +77 Additional-Number +78 FROM MAP-SM-DataTypes { +79 itu-t identified-organization (4) etsi (0) mobileDomain (0) +80 gsm-Network (1) modules (3) map-SM-DataTypes (16) version21 (21)} +81 ; +82 +83 + +``` + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 84 RoutingInfoForLCS-Arg := SEQUENCE { 85     mlcNumber [0] ISDN-AddressString, 86     targetMS [1] SubscriberIdentity, 87     extensionContainer [2] ExtensionContainer OPTIONAL, 88     ...}
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 90 RoutingInfoForLCS-Res := SEQUENCE { 91     targetMS [0] SubscriberIdentity, 92     lcsLocationInfo [1] LCSLocationInfo, 93     extensionContainer [2] ExtensionContainer OPTIONAL, 94     ..., 95     v-gmlc-Address [3] GSN-Address OPTIONAL, 96     h-gmlc-Address [4] GSN-Address OPTIONAL, 97     ppr-Address [5] GSN-Address OPTIONAL, 98     additional-v-gmlc-Address [6] GSN-Address OPTIONAL }
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 100 LCSLocationInfo := SEQUENCE { 101     networkNode-Number ISDN-AddressString, 102     -- NetworkNode-number can be msc-number, sgsn-number or a dummy value of "0" 103     lmsi [0] LMSI OPTIONAL, 104     extensionContainer [1] ExtensionContainer OPTIONAL, 105     ... , 106     gprsNodeIndicator [2] NULL OPTIONAL, 107     -- gprsNodeIndicator is set only if the SGSN number is sent as the Network Node Number 108     additional-Number [3] Additional-Number OPTIONAL, 109     supportedLCS-CapabilitySets [4] SupportedLCS-CapabilitySets OPTIONAL, 110     additional-LCS-CapabilitySets [5] SupportedLCS-CapabilitySets OPTIONAL, 111     mme-Name [6] DiameterIdentity OPTIONAL, 112     aaa-Server-Name [8] DiameterIdentity OPTIONAL, 113     sgsn-Name [9] DiameterIdentity OPTIONAL, 114     sgsn-Realm [10] DiameterIdentity OPTIONAL 115 }
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +116 + +``` + +117 ProvideSubscriberLocation-Arg ::= SEQUENCE { +118 locationType LocationType, +119 mlc-Number ISDN-AddressString, +120 lcs-ClientID [0] LCS-ClientID OPTIONAL, +121 privacyOverride [1] NULL OPTIONAL, +122 imsi [2] IMSI OPTIONAL, +123 msisdn [3] ISDN-AddressString OPTIONAL, +124 lmsi [4] LMSI OPTIONAL, +125 imei [5] IMEI OPTIONAL, +126 lcs-Priority [6] LCS-Priority OPTIONAL, +127 lcs-QoS [7] LCS-QoS OPTIONAL, +128 extensionContainer [8] ExtensionContainer OPTIONAL, +129 ... , +130 supportedGADShapes [9] SupportedGADShapes OPTIONAL, +131 lcs-ReferenceNumber [10] LCS-ReferenceNumber OPTIONAL, +132 lcsServiceTypeID [11] LCSServiceTypeID OPTIONAL, +133 lcsCodeword [12] LCSCodeword OPTIONAL, +134 lcs-PrivacyCheck [13] LCS-PrivacyCheck OPTIONAL, +135 areaEventInfo [14] AreaEventInfo OPTIONAL, +136 h-gmlc-Address [15] GSN-Address OPTIONAL, +137 mo-lrShortCircuitIndicator [16] NULL OPTIONAL, +138 periodicLDRInfo [17] PeriodicLDRInfo OPTIONAL, +139 reportingPLMNList [18] ReportingPLMNList OPTIONAL } +140 +141 -- one of imsi or msisdn is mandatory +142 -- If a location estimate type indicates activate deferred location or cancel deferred +143 -- location, a lcs-Reference number shall be included. +144 +145 LocationType ::= SEQUENCE { +146 locationEstimateType [0] LocationEstimateType, +147 ... , +148 deferredLocationEventType [1] DeferredLocationEventType OPTIONAL } +149 +150 LocationEstimateType ::= ENUMERATED { +151 currentLocation (0), +152 currentOrLastKnownLocation (1), +153 initialLocation (2), +154 ... , +155 activateDeferredLocation (3), +156 cancelDeferredLocation (4) , +157 notificationVerificationOnly (5) } +158 -- exception handling: +159 -- a ProvideSubscriberLocation-Arg containing an unrecognized LocationEstimateType +160 -- shall be rejected by the receiver with a return error cause of unexpected data value +161 +162 DeferredLocationEventType ::= BIT STRING { +163 msAvailable (0) , +164 enteringIntoArea (1) , +165 leavingFromArea (2) , +166 beingInsideArea (3) , +167 periodicLDR (4) } (SIZE (1..16)) +168 -- beingInsideArea is always treated as oneTimeEvent regardless of the possible value +169 -- of occurrenceInfo inside areaEventInfo. +170 -- exception handling: +171 -- a ProvideSubscriberLocation-Arg containing other values than listed above in +172 -- DeferredLocationEventType shall be rejected by the receiver with a return error cause of +173 -- unexpected data value. +174 +175 LCS-ClientID ::= SEQUENCE { +176 lcsClientType [0] LCSClientType, +177 lcsClientExternalID [1] LCSClientExternalID OPTIONAL, +178 lcsClientDialedByMS [2] AddressString OPTIONAL, +179 lcsClientInternalID [3] LCSClientInternalID OPTIONAL, +180 lcsClientName [4] LCSClientName OPTIONAL, +181 ... , +182 lcsAPN [5] APN OPTIONAL, +183 lcsRequestorID [6] LCSRequestorID OPTIONAL } +184 + +``` + +``` + +185 LCSClientType ::= ENUMERATED { +186 emergencyServices (0), +187 valueAddedServices (1), +188 plmnOperatorServices (2), +189 lawfulInterceptServices (3), +190 ... } +191 -- exception handling: +192 -- unrecognized values may be ignored if the LCS client uses the privacy override +193 -- otherwise, an unrecognized value shall be treated as unexpected data by a receiver +194 -- a return error shall then be returned if received in a MAP invoke +195 +196 LCSClientName ::= SEQUENCE { +197 dataCodingScheme [0] USSD-DataCodingScheme, +198 nameString [2] NameString, +199 ..., +200 lcs-FormatIndicator [3] LCS-FormatIndicator OPTIONAL } +201 +202 -- The USSD-DataCodingScheme shall indicate use of the default alphabet through the +203 -- following encoding +204 -- bit 7 6 5 4 3 2 1 0 +205 -- 0 0 0 0 1 1 1 1 +206 +207 NameString ::= USSD-String (SIZE (1..maxNameStringLength)) +208 +209 maxNameStringLength INTEGER ::= 63 +210 +211 LCSRequestorID ::= SEQUENCE { +212 dataCodingScheme [0] USSD-DataCodingScheme, +213 requestorIDString [1] RequestorIDString, +214 ..., +215 lcs-FormatIndicator [2] LCS-FormatIndicator OPTIONAL } +216 +217 RequestorIDString ::= USSD-String (SIZE (1..maxRequestorIDStringLength)) +218 +219 maxRequestorIDStringLength INTEGER ::= 63 +220 +221 LCS-FormatIndicator ::= ENUMERATED { +222 logicalName (0), +223 e-mailAddress (1), +224 msisdn (2), +225 url (3), +226 sipUrl (4), +227 ... } +228 +229 LCS-Priority ::= OCTET STRING (SIZE (1)) +230 -- 0 = highest priority +231 -- 1 = normal priority +232 -- all other values treated as 1 +233 +234 LCS-QoS ::= SEQUENCE { +235 horizontal-accuracy [0] Horizontal-Accuracy OPTIONAL, +236 verticalCoordinateRequest [1] NULL OPTIONAL, +237 vertical-accuracy [2] Vertical-Accuracy OPTIONAL, +238 responseTime [3] ResponseTime OPTIONAL, +239 extensionContainer [4] ExtensionContainer OPTIONAL, +240 ..., +241 velocityRequest [5] NULL OPTIONAL, +242 lcs-qos-class [6] LCS-QoS-Class OPTIONAL +243 } +244 -- lcs-qos-class may only be included in MO-LR request sent by the UE to the network. +245 +246 +247 Horizontal-Accuracy ::= OCTET STRING (SIZE (1)) +248 -- bit 8 = 0 +249 -- bits 7-1 = 7 bit Uncertainty Code defined in 3GPP TS 23.032. The horizontal location +250 -- error should be less than the error indicated by the uncertainty code with 67% +251 -- confidence. +252 +253 Vertical-Accuracy ::= OCTET STRING (SIZE (1)) +254 -- bit 8 = 0 +255 -- bits 7-1 = 7 bit Vertical Uncertainty Code defined in 3GPP TS 23.032. +256 -- The vertical location error should be less than the error indicated +257 -- by the uncertainty code with 67% confidence. +258 + +``` + +``` + +259 ResponseTime ::= SEQUENCE { +260 responseTimeCategory ResponseTimeCategory, +261 ...} +262 -- note: an expandable SEQUENCE simplifies later addition of a numeric response time. +263 +264 ResponseTimeCategory ::= ENUMERATED { +265 lowdelay (0), +266 delaytolerant (1), +267 ... } +268 -- exception handling: +269 -- an unrecognized value shall be treated the same as value 1 (delaytolerant) +270 +271 LCS-QoS-Class ::= ENUMERATED { +272 bestEffort (0), +273 assured (1), +274 ... } +275 -- exception handling: +276 -- an unrecognized value shall be treated the same as value 0 (bestEffort) +277 +278 SupportedGADShapes ::= BIT STRING { +279 ellipsoidPoint (0), +280 ellipsoidPointWithUncertaintyCircle (1), +281 ellipsoidPointWithUncertaintyEllipse (2), +282 polygon (3), +283 ellipsoidPointWithAltitude (4), +284 ellipsoidPointWithAltitudeAndUncertaintyEllipsoid (5), +285 ellipsoidArc (6) } (SIZE (7..16)) +286 -- A node shall mark in the BIT STRING all Shapes defined in 3GPP TS 23.032 it supports. +287 -- exception handling: bits 7 to 15 shall be ignored if received. +288 +289 LCS-ReferenceNumber ::= OCTET STRING (SIZE(1)) +290 +291 LCSCodeword ::= SEQUENCE { +292 dataCodingScheme [0] USSD-DataCodingScheme, +293 lcsCodewordString [1] LCSCodewordString, +294 ...} +295 +296 LCSCodewordString ::= USSD-String (SIZE (1..maxLCSCodewordStringLength)) +297 +298 maxLCSCodewordStringLength INTEGER ::= 20 +299 +300 LCS-PrivacyCheck ::= SEQUENCE { +301 callSessionUnrelated [0] PrivacyCheckRelatedAction, +302 callSessionRelated [1] PrivacyCheckRelatedAction OPTIONAL, +303 ...} +304 +305 PrivacyCheckRelatedAction ::= ENUMERATED { +306 allowedWithoutNotification (0), +307 allowedWithNotification (1), +308 allowedIfNoResponse (2), +309 restrictedIfNoResponse (3), +310 notAllowed (4), +311 ...} +312 -- exception handling: +313 -- a ProvideSubscriberLocation-Arg containing an unrecognized PrivacyCheckRelatedAction +314 -- shall be rejected by the receiver with a return error cause of unexpected data value +315 +316 AreaEventInfo ::= SEQUENCE { +317 areaDefinition [0] AreaDefinition, +318 occurrenceInfo [1] OccurrenceInfo OPTIONAL, +319 intervalTime [2] IntervalTime OPTIONAL, +320 ...} +321 +322 AreaDefinition ::= SEQUENCE { +323 areaList [0] AreaList, +324 ...} +325 +326 AreaList ::= SEQUENCE SIZE (1..maxNumOfAreas) OF Area +327 +328 maxNumOfAreas INTEGER ::= 10 +329 +330 Area ::= SEQUENCE { +331 areaType [0] AreaType, +332 areaIdentification [1] AreaIdentification, +333 ...} +334 + +``` + +``` + +335 AreaType ::= ENUMERATED { +336 countryCode (0), +337 plmnId (1), +338 locationAreaId (2), +339 routingAreaId (3), +340 cellGlobalId (4), +341 ..., +342 utranCellId (5) } +343 +344 AreaIdentification ::= OCTET STRING (SIZE (2..7)) +345 -- The internal structure is defined as follows: +346 -- octet 1 bits 4321 Mobile Country Code 1st digit +347 -- bits 8765 Mobile Country Code 2nd digit +348 -- octet 2 bits 4321 Mobile Country Code 3rd digit +349 -- bits 8765 Mobile Network Code 3rd digit if 3 digit MNC included +350 -- or filler (1111) +351 -- octet 3 bits 4321 Mobile Network Code 1st digit +352 -- bits 8765 Mobile Network Code 2nd digit +353 -- octets 4 and 5 Location Area Code (LAC) for Local Area Id, +354 -- Routing Area Id and Cell Global Id +355 -- octet 6 Routing Area Code (RAC) for Routing Area Id +356 -- octets 6 and 7 Cell Identity (CI) for Cell Global Id +357 -- octets 4 until 7 Utran Cell Identity (UC-Id) for Utran Cell Id +358 +359 OccurrenceInfo ::= ENUMERATED { +360 oneTimeEvent (0), +361 multipleTimeEvent (1), +362 ...} +363 +364 IntervalTime ::= INTEGER (1..32767) +365 -- minimum interval time between area reports in seconds +366 +367 PeriodicLDRInfo ::= SEQUENCE { +368 reportingAmount ReportingAmount, +369 reportingInterval ReportingInterval, +370 ..., +371 reportingOptionMilliseconds [0] ReportingOptionMilliseconds OPTIONAL +372 } +373 -- reportingInterval x reportingAmount shall not exceed 8639999 (99 days, 23 hours, +374 -- 59 minutes and 59 seconds) for compatibility with OMA MLP and RLP +375 -- When reportingOptionMilliseconds is provided and supported, reportingInterval & +376 -- reportingAmount shall be ignored. +377 +378 ReportingAmount ::= INTEGER (1..maxReportingAmount) +379 +380 maxReportingAmount INTEGER ::= 8639999 +381 +382 ReportingInterval ::= INTEGER (1..maxReportingInterval) +383 -- ReportingInterval is in seconds +384 +385 maxReportingInterval INTEGER ::= 8639999 +386 +387 ReportingOptionMilliseconds ::= SEQUENCE { +388 reportingAmountMilliseconds ReportingAmountMilliseconds, +389 reportingIntervalMilliseconds ReportingIntervalMilliseconds, +390 ...} +391 -- reportingAmountMilliseconds x reportingIntervalMilliseconds shall not exceed 8639999000 +392 -- (99 days, 23 hours, 59 minutes and 59 seconds) for compatibility with OMA MLP and RLP +393 +394 ReportingAmountMilliseconds ::= INTEGER (1..maxReportingAmountMilliseconds) +395 +396 maxReportingAmountMilliseconds INTEGER ::= 8639999000 +397 +398 ReportingIntervalMilliseconds ::= INTEGER (1..maxReportingIntervalMilliseconds) +399 +400 maxReportingIntervalMilliseconds INTEGER ::= 999 +401 +402 ReportingPLMNList ::= SEQUENCE { +403 plmn-ListPrioritized [0] NULL OPTIONAL, +404 plmn-List [1] PLMNList, +405 ...} +406 + +``` + +``` + +407 PLMNList ::= SEQUENCE SIZE (1..maxNumOfReportingPLMN) OF +408 ReportingPLMN +409 +410 maxNumOfReportingPLMN INTEGER ::= 20 +411 +412 ReportingPLMN ::= SEQUENCE { +413 plmn-Id [0] PLMN-Id, +414 ran-Technology [1] RAN-Technology OPTIONAL, +415 ran-PeriodicLocationSupport [2] NULL OPTIONAL, +416 ... } +417 +418 RAN-Technology ::= ENUMERATED { +419 gsm (0), +420 umts (1), +421 ... } +422 +423 ProvideSubscriberLocation-Res ::= SEQUENCE { +424 locationEstimate Ext-GeographicalInformation, +425 ageOfLocationEstimate [0] AgeOfLocationInformation OPTIONAL, +426 extensionContainer [1] ExtensionContainer OPTIONAL, +427 ... , +428 add-LocationEstimate [2] Add-GeographicalInformation OPTIONAL, +429 deferredmt-lrResponseIndicator [3] NULL OPTIONAL, +430 geranPositioningData [4] PositioningDataInformation OPTIONAL, +431 utranPositioningData [5] UtranPositioningDataInfo OPTIONAL, +432 cellIdOrSai [6] CellGlobalIdOrServiceAreaIdOrLAI OPTIONAL, +433 sai-Present [7] NULL OPTIONAL, +434 accuracyFulfilmentIndicator [8] AccuracyFulfilmentIndicator OPTIONAL, +435 velocityEstimate [9] VelocityEstimate OPTIONAL, +436 mo-lrShortCircuitIndicator [10] NULL OPTIONAL, +437 geranGANSPositioningData [11] GeranGANSPositioningData OPTIONAL, +438 utranGANSPositioningData [12] UtranGANSPositioningData OPTIONAL, +439 targetServingNodeForHandover [13] ServingNodeAddress OPTIONAL, +440 utranAdditionalPositioningData [14] UtranAdditionalPositioningData OPTIONAL, +441 utranBaroPressureMeas [15] UtranBaroPressureMeas OPTIONAL, +442 utranCivicAddress [16] UtranCivicAddress OPTIONAL } +443 +444 -- if deferredmt-lrResponseIndicator is set, locationEstimate is ignored. +445 +446 -- the add-LocationEstimate parameter shall not be sent to a node that did not indicate the +447 -- geographic shapes supported in the ProvideSubscriberLocation-Arg +448 -- The locationEstimate and the add-locationEstimate parameters shall not be sent if +449 -- the supportedGADShapes parameter has been received in ProvideSubscriberLocation-Arg +450 -- and the shape encoded in locationEstimate or add-LocationEstimate is not marked +451 -- as supported in supportedGADShapes. In such a case ProvideSubscriberLocation +452 -- shall be rejected with error FacilityNotSupported with additional indication +453 -- shapeOfLocationEstimateNotSupported. +454 -- sai-Present indicates that the cellIdOrSai parameter contains a Service Area Identity. +455 +456 AccuracyFulfilmentIndicator ::= ENUMERATED { +457 requestedAccuracyFulfilled (0), +458 requestedAccuracyNotFulfilled (1), +459 ... } +460 + +``` + +``` + +461 Ext-GeographicalInformation ::= OCTET STRING (SIZE (1..maxExt-GeographicalInformation)) +462 -- Refers to geographical Information defined in 3GPP TS 23.032. +463 -- This is composed of 1 or more octets with an internal structure according to +464 -- 3GPP TS 23.032 +465 -- Octet 1: Type of shape, only the following shapes in 3GPP TS 23.032 are allowed: +466 -- (a) Ellipsoid point with uncertainty circle +467 -- (b) Ellipsoid point with uncertainty ellipse +468 -- (c) Ellipsoid point with altitude and uncertainty ellipsoid +469 -- (d) Ellipsoid Arc +470 -- (e) Ellipsoid Point +471 -- Any other value in octet 1 shall be treated as invalid +472 -- Octets 2 to 8 for case (a) - Ellipsoid point with uncertainty circle +473 -- Degrees of Latitude 3 octets +474 -- Degrees of Longitude 3 octets +475 -- Uncertainty code 1 octet +476 -- Octets 2 to 11 for case (b) - Ellipsoid point with uncertainty ellipse: +477 -- Degrees of Latitude 3 octets +478 -- Degrees of Longitude 3 octets +479 -- Uncertainty semi-major axis 1 octet +480 -- Uncertainty semi-minor axis 1 octet +481 -- Angle of major axis 1 octet +482 -- Confidence 1 octet +483 -- Octets 2 to 14 for case (c) - Ellipsoid point with altitude and uncertainty ellipsoid +484 -- Degrees of Latitude 3 octets +485 -- Degrees of Longitude 3 octets +486 -- Altitude 2 octets +487 -- Uncertainty semi-major axis 1 octet +488 -- Uncertainty semi-minor axis 1 octet +489 -- Angle of major axis 1 octet +490 -- Uncertainty altitude 1 octet +491 -- Confidence 1 octet +492 -- Octets 2 to 13 for case (d) - Ellipsoid Arc +493 -- Degrees of Latitude 3 octets +494 -- Degrees of Longitude 3 octets +495 -- Inner radius 2 octets +496 -- Uncertainty radius 1 octet +497 -- Offset angle 1 octet +498 -- Included angle 1 octet +499 -- Confidence 1 octet +500 -- Octets 2 to 7 for case (e) - Ellipsoid Point +501 -- Degrees of Latitude 3 octets +502 -- Degrees of Longitude 3 octets +503 +504 -- +505 -- An Ext-GeographicalInformation parameter comprising more than one octet and +506 -- containing any other shape or an incorrect number of octets or coding according +507 -- to 3GPP TS 23.032 shall be treated as invalid data by a receiver. +508 -- +509 -- An Ext-GeographicalInformation parameter comprising one octet shall be discarded +510 -- by the receiver if an Add-GeographicalInformation parameter is received +511 -- in the same message. +512 -- +513 -- An Ext-GeographicalInformation parameter comprising one octet shall be treated as +514 -- invalid data by the receiver if an Add-GeographicalInformation parameter is not +515 -- received in the same message. + +``` + +``` + +516 +517 maxExt-GeographicalInformation INTEGER ::= 20 +518 -- the maximum length allows for further shapes in 3GPP TS 23.032 to be included in later +519 -- versions of 3GPP TS 29.002 +520 + +``` + +``` +521 VelocityEstimate ::= OCTET STRING (SIZE (4..7)) +522 -- Refers to Velocity description defined in 3GPP TS 23.032. +523 -- This is composed of 4 or more octets with an internal structure according to +524 -- 3GPP TS 23.032 +525 -- Octet 1: Type of velocity, only the following types in 3GPP TS 23.032 are allowed: +526 -- (a) Horizontal Velocity +527 -- (b) Horizontal with Vertical Velocity +528 -- (c) Horizontal Velocity with Uncertainty +529 -- (d) Horizontal with Vertical Velocity and Uncertainty +530 -- For types Horizontal with Vertical Velocity and Horizontal with Vertical Velocity +531 -- and Uncertainty, the direction of the Vertical Speed is also included in Octet 1 +532 -- Any other value in octet 1 shall be treated as invalid +533 -- Octets 2 to 4 for case (a) Horizontal velocity: +534 -- Bearing 1 octet +535 -- Horizontal Speed 2 octets +536 -- Octets 2 to 5 for case (b) - Horizontal with Vertical Velocity: +537 -- Bearing 1 octet +538 -- Horizontal Speed 2 octets +539 -- Vertical Speed 1 octet +540 -- Octets 2 to 5 for case (c) - Horizontal velocity with Uncertainty: +541 -- Bearing 1 octet +542 -- Horizontal Speed 2 octets +543 -- Uncertainty Speed 1 octet +544 -- Octets 2 to 7 for case (d) - Horizontal with Vertical Velocity and Uncertainty: +545 -- Bearing 1 octet +546 -- Horizontal Speed 2 octets +547 -- Vertical Speed 1 octet +548 -- Horizontal Uncertainty Speed 1 octet +549 -- Vertical Uncertainty Speed 1 octet +``` + +``` +551 PositioningDataInformation ::= OCTET STRING (SIZE (2..maxPositioningDataInformation)) +552 -- Refers to the Positioning Data defined in 3GPP TS 49.031. +553 -- This is composed of 2 or more octets with an internal structure according to +554 -- 3GPP TS 49.031. +``` + +``` +556 maxPositioningDataInformation INTEGER ::= 10 +557 -- +``` + +``` +559 UtranPositioningDataInfo ::= OCTET STRING (SIZE (3..maxUtranPositioningDataInfo)) +560 -- Refers to the Position Data defined in 3GPP TS 25.413. +561 -- This is composed of the positioningDataDiscriminator and the positioningDataSet +562 -- included in positionData as defined in 3GPP TS 25.413. +``` + +``` +564 maxUtranPositioningDataInfo INTEGER ::= 11 +565 -- +``` + +``` +567 GeranGANSSEpositioningData ::= OCTET STRING (SIZE (2..maxGeranGANSSEpositioningData)) +568 -- Refers to the GANSSE Positioning Data defined in 3GPP TS 49.031. +569 -- This is composed of 2 or more octets with an internal structure according to +570 -- 3GPP TS 49.031. +``` + +``` +572 maxGeranGANSSEpositioningData INTEGER ::= 10 +573 -- +``` + +``` +575 UtranGANSSEpositioningData ::= OCTET STRING (SIZE (1..maxUtranGANSSEpositioningData)) +576 -- Refers to the Position Data defined in 3GPP TS 25.413. +577 -- This is composed of the GANSSE-PositioningDataSet only, included in PositionData +578 -- as defined in 3GPP TS 25.413. +``` + +``` +580 maxUtranGANSSEpositioningData INTEGER ::= 9 +581 -- +``` + +``` +583 UtranAdditionalPositioningData ::= OCTET STRING (SIZE (1..maxUtranAdditionalPositioningData)) +584 -- Refers to the Position Data defined in 3GPP TS 25.413. +585 -- This is composed of the Additional-PositioningDataSet only, included in PositionData +586 -- as defined in 3GPP TS 25.413. +``` + +``` +588 maxUtranAdditionalPositioningData INTEGER ::= 8 +589 -- +``` + +``` +591 UtranBaroPressureMeas ::= INTEGER (30000..115000) +592 -- Refers to the barometric pressure measurement defined in 3GPP TS 25.413. +593 -- This is composed of the BarometricPressureMeasurement only as defined in 3GPP TS +594 -- 25.413. +``` + +``` +595 +``` + +``` + +596 UtranCivicAddress ::= OCTET STRING +597 -- Refers to the civic address defined in 3GPP TS 25.413. +598 -- This is composed of the CivicAddress only as defined in 3GPP TS 25.413. +599 +600 Add-GeographicalInformation ::= OCTET STRING (SIZE (1..maxAdd-GeographicalInformation)) +601 -- Refers to geographical Information defined in 3GPP TS 23.032. +602 -- This is composed of 1 or more octets with an internal structure according to +603 -- 3GPP TS 23.032 +604 -- Octet 1: Type of shape, all the shapes defined in 3GPP TS 23.032 are allowed: +605 -- Octets 2 to n (where n is the total number of octets necessary to encode the shape +606 -- according to 3GPP TS 23.032) are used to encode the shape itself in accordance with +607 the +608 -- encoding defined in 3GPP TS 23.032 +609 -- +610 -- An Add-GeographicalInformation parameter, whether valid or invalid, received +611 -- together with a valid Ext-GeographicalInformation parameter in the same message +612 -- shall be discarded. +613 -- +614 -- An Add-GeographicalInformation parameter containing any shape not defined in +615 -- 3GPP TS 23.032 or an incorrect number of octets or coding according to +616 -- 3GPP TS 23.032 shall be treated as invalid data by a receiver if not received +617 -- together with a valid Ext-GeographicalInformation parameter in the same message. +618 +619 maxAdd-GeographicalInformation INTEGER ::= 91 +620 -- the maximum length allows support for all the shapes currently defined in 3GPP TS +621 23.032 +622 +623 SubscriberLocationReport-Arg ::= SEQUENCE { +624 lcs-Event LCS-Event, +625 lcs-ClientID LCS-ClientID, +626 lcsLocationInfo LCSLocationInfo, +627 msisdn [0] ISDN-AddressString OPTIONAL, +628 imsi [1] IMSI OPTIONAL, +629 imei [2] IMEI OPTIONAL, +630 na-ESRD [3] ISDN-AddressString OPTIONAL, +631 na-ESRK [4] ISDN-AddressString OPTIONAL, +632 locationEstimate [5] Ext-GeographicalInformation OPTIONAL, +633 ageOfLocationEstimate [6] AgeOfLocationInformation OPTIONAL, +634 slr-ArgExtensionContainer [7] SLR-ArgExtensionContainer OPTIONAL, +635 ... , +636 add-LocationEstimate [8] Add-GeographicalInformation OPTIONAL, +637 deferredmt-lrData [9] Deferredmt-lrData OPTIONAL, +638 lcs-ReferenceNumber [10] LCS-ReferenceNumber OPTIONAL, +639 geranPositioningData [11] PositioningDataInformation OPTIONAL, +640 utranPositioningData [12] UtranPositioningDataInfo OPTIONAL, +641 cellIdOrSai [13] CellGlobalIdOrServiceAreaIdOrLAI OPTIONAL, +642 h-gmlc-Address [14] GSN-Address OPTIONAL, +643 lcssServiceTypeID [15] LCSServiceTypeID OPTIONAL, +644 sai-Present [17] NULL OPTIONAL, +645 pseudonymIndicator [18] NULL OPTIONAL, +646 accuracyFulfilmentIndicator [19] AccuracyFulfilmentIndicator OPTIONAL, +647 velocityEstimate [20] VelocityEstimate OPTIONAL, +648 sequenceNumber [21] SequenceNumber OPTIONAL, +649 periodicLDRInfo [22] PeriodicLDRInfo OPTIONAL, +650 mo-lrShortCircuitIndicator [23] NULL OPTIONAL, +651 geranGANSPositioningData [24] GeranGANSPositioningData OPTIONAL, +652 utranGANSPositioningData [25] UtranGANSPositioningData OPTIONAL, +653 targetServingNodeForHandover [26] ServingNodeAddress OPTIONAL, +654 utranAdditionalPositioningData [27] UtranAdditionalPositioningData OPTIONAL, +655 utranBaroPressureMeas [28] UtranBaroPressureMeas OPTIONAL, +656 utranCivicAddress [29] UtranCivicAddress OPTIONAL } +657 +658 -- one of msisdn or imsi is mandatory +659 -- a location estimate that is valid for the locationEstimate parameter should +660 -- be transferred in this parameter in preference to the add-LocationEstimate. +661 -- the deferredmt-lrData parameter shall be included if and only if the lcs-Event +662 -- indicates a deferredmt-lrResponse. +663 -- if the lcs-Event indicates a deferredmt-lrResponse then the locationEstimate +664 -- and the add-LocationEstimate parameters shall not be sent if the +665 -- supportedGADShapes parameter had been received in ProvideSubscriberLocation-Arg +666 -- and the shape encoded in locationEstimate or add-LocationEstimate was not marked +667 -- as supported in supportedGADShapes. In such a case terminationCause +668 -- in deferredmt-lrData shall be present with value +669 -- shapeOfLocationEstimateNotSupported. +670 -- If a lcs event indicates deferred mt-lr response, the lcs-Reference number shall be +671 -- included. +672 -- sai-Present indicates that the cellIdOrSai parameter contains a Service Area Identity. +673 + +``` + +``` + +674 Deferredmt-lrData ::= SEQUENCE { +675 deferredLocationEventType DeferredLocationEventType, +676 terminationCause [0] TerminationCause OPTIONAL, +677 lcsLocationInfo [1] LCSLocationInfo OPTIONAL, +678 ...} +679 -- lcsLocationInfo may be included only if a terminationCause is present +680 -- indicating mt-lrRestart. +681 +682 LCS-Event ::= ENUMERATED { +683 emergencyCallOrigination (0), +684 emergencyCallRelease (1), +685 mo-lr (2), +686 ..., +687 deferredmt-lrResponse (3) , +688 deferredmo-lrTTTPInitiation (4), +689 emergencyCallHandover (5) } +690 -- deferredmt-lrResponse is applicable to the delivery of a location estimate +691 -- for an LDR initiated earlier by either the network (via an MT-LR activate deferred +692 -- location) or the UE (via a deferred MO-LR TTTP initiation) +693 -- exception handling: +694 -- a SubscriberLocationReport-Arg containing an unrecognized LCS-Event +695 -- shall be rejected by a receiver with a return error cause of unexpected data value +696 +697 TerminationCause ::= ENUMERATED { +698 normal (0), +699 errorundefined (1), +700 internalTimeout (2), +701 congestion (3), +702 mt-lrRestart (4), +703 privacyViolation (5), +704 ..., +705 shapeOfLocationEstimateNotSupported (6) , +706 subscriberTermination (7), +707 uETermination (8), +708 networkTermination (9) } +709 -- mt-lrRestart shall be used to trigger the GMLC to restart the location procedure, +710 -- either because the sending node knows that the terminal has moved under coverage +711 -- of another MSC or SGSN (e.g. Send Identification received), or because the subscriber +712 -- has been deregistered due to a Cancel Location received from HLR. +713 -- +714 -- exception handling +715 -- an unrecognized value shall be treated the same as value 1 (errorundefined) +716 +717 SequenceNumber ::= INTEGER (1..maxReportingAmount) +718 +719 ServingNodeAddress ::= CHOICE { +720 msc-Number [0] ISDN-AddressString, +721 sgsn-Number [1] ISDN-AddressString, +722 mme-Number [2] DiameterIdentity } +723 +724 SubscriberLocationReport-Res ::= SEQUENCE { +725 extensionContainer ExtensionContainer OPTIONAL, +726 ..., +727 na-ESRK [0] ISDN-AddressString OPTIONAL, +728 na-ESRD [1] ISDN-AddressString OPTIONAL, +729 h-gmlc-Address [2] GSN-Address OPTIONAL, +730 mo-lrShortCircuitIndicator [3] NULL OPTIONAL, +731 reportingPLMNList [4] ReportingPLMNList OPTIONAL, +732 lcs-ReferenceNumber [5] LCS-ReferenceNumber OPTIONAL } +733 +734 -- na-ESRK and na-ESRD are mutually exclusive +735 -- +736 -- exception handling +737 -- receipt of both na-ESRK and na-ESRD shall be treated the same as a return error +738 +739 +740 END + +``` + +## 17.7.14 Void + +--- + +## 742 18 General on MAP user procedures + +### 743 18.1 Introduction + +744 Clauses 18 to 25 describe the use of MAP services for GSM signalling procedures. GSM signalling procedures may +745 involve one or several interfaces running one or several application protocols. The present document addresses only the +746 signalling procedures which require at least the use of one MAP service. + +747 When a signalling procedure takes place in the network, an application process invocation is created in each system +748 component involved. Part of the application process invocation acts as a MAP user and handles one or several MAP +749 dialogues. For each dialogue it employs an instance of the MAP service provider. It may also use other communication +750 services to exchange information on other interfaces, but detailed description of these aspects is outside the scope of the +751 present document. + +### 752 18.2 Common aspects of user procedure descriptions + +#### 753 18.2.1 General conventions + +754 For each signalling procedure the present document provides a brief textual overview accompanied by a flow diagram +755 which represent the functional interactions between system components. Functional interactions are labelled using the +756 MAP service name when the interaction results from a service request or by this service name followed by the symbol +757 "ack" when this interaction results from a service response. + +758 For each of the system components involved, the present document also provides a detailed textual description of the +759 application process behaviour as well as an SDL diagram. SDL diagrams describe the sequence of events, as seen by the +760 MAP-User, which occurs at MAP service provider boundaries as well as external events which occur at other interfaces +761 and which impact on the previous sequence. + +762 External events do not necessarily correspond to the messages of other protocols used in the system component. The +763 MAP-user procedures are described as if a set of interworking functions (IWF) between the MAP-user and the other +764 protocol entities was implemented (see figure 18.2/1). Such interworking functions are assumed to perform either an +765 identity mapping or some processing or translation as required to eliminate information irrelevant to the MAP-user. + +766 The mapping of service primitives on to protocol elements is described in clauses 14 to 17. + +767 GSM signalling procedures are built from one or more sub-procedures (e.g. authentication, ciphering, ...). + +768 Sub-procedures from which signalling procedures are built are represented using SDL MACRO descriptions. + +769 In case of any discrepancy between the textual descriptions and the SDL descriptions, the latter take precedence. + +#### 770 18.2.2 Naming conventions + +771 Events related to MAP are represented by MAP service primitives. The signal names used in the SDL diagrams are +772 derived from the service primitive names defined in clauses 7 to 12, with some lexical transformations for readability +773 and parsability purposes (blanks between words are replaced by underscores, the first letter of each word is capitalised). + +774 Events received and sent on other interfaces are named by appending the message or signal name to a symbol +775 representing the interface type, with some lexical transformations for readability and parsability purposes (blanks +776 between words are replaced by underscores, the first letter of each word is capitalised). + +777 The following symbols are used to represent the interface types: + +778 "I": For interfaces to the fixed network. "I" stands for ISUP interface. + +779 "A": For interfaces between the MSC and the BSS (i.e. A-interfaces); + +780 "Gb": For interfaces between the SGSN and the BSS (i.e. Gb-interfaces); + +781 "OM": For network management interfaces (communication with OMC, MML interface, ...); +782 "SC": For interfaces to a Service Centre; +783 "HO\_CA": For internal interfaces to the Handover Control Application. +784 "US": For a local USSD application. + +785 These naming conventions can be summarised by the following BNF description: + +``` + +786 ::= | +787 ::= | | | | +788 | +789 ::= MAP_Open_Req | MAP_Open_Ind | MAP_Open_Rsp | MAP_Open_Cnf +790 ::= MAP_Close_Req | MAP_Close_Ind +791 ::= MAP_U_Abort_Req | MAP_U_Abort_Ind +792 ::= MAP_P_Abort_Ind +793 ::= MAP_Notice_Ind +794 ::= | | | +795 ::= MAP__Req +796 ::= MAP__Ind +797 ::= MAP__Rsp +798 ::= MAP__Cnf +799 ::= _ +800 ::= I | A | Gb | OM | SC | HO AC | US +801 ::= +802 ::= +803 ::= | _ +804 ::= +805 ::= | +806 ::= | +807 ::= | +808 ::= 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 +809 ::= 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 +810 ::= 1|2|3|4|5|6|7|8|9|0 + +``` + +811 **Figure 18.2/1: Interfaces applicable to the MAP-User** + +## 812 18.2.3 Convention on primitives parameters + +### 813 18.2.3.1 Open service + +814 When the originating and destination reference parameters shall be included in the MAP-OPEN request primitive, their +815 value are indicated as a comment to the signal which represents this primitive. + +### 816 18.2.3.2 Close service + +817 When a pre-arranged release is requested, a comment is attached to the signal which represents the MAP-CLOSE +818 request primitive. In the absence of comment, a normal release is assumed. + +## 819 18.2.4 Version handling at dialogue establishment + +820 Unless explicitly indicated in subsequent clauses, the following principles regarding version handling procedures at +821 dialogue establishment are applied by the MAP-user. + +### 822 18.2.4.1 Behaviour at the initiating side + +823 When a MAP user signalling procedure has to be executed, the MAP-user issues a MAP-OPEN request primitive with +824 an appropriate application-context-name. If several names are supported (i.e. several versions) a suitable one is selected +825 using the procedures described in clause 5. + +826 + +827 If version n is selected (where $1 < n \leq$ highest existing version) and a MAP-OPEN Confirm primitive is received in +828 response to the MAP-OPEN request with a result parameter set to "refused" and a diagnostic parameter indicating +829 "application context not supported" or "potential version incompatibility problem", the MAP-User issues a new MAP- +830 OPEN request primitive with the equivalent version y context (where $1 \leq y < n$ ). This is informally represented in the +831 SDL diagrams by task symbols indicating 'Perform Vr procedure'. + +### 832 18.2.4.2 Behaviour at the responding side + +833 On receipt of a MAP-OPEN indication primitive, the MAP-User analyses the application-context-name and executes +834 the procedure associated with the requested version context. For example, if it refers to a version one context, the +835 associated V1 procedure is executed; if it refers to a version two context, the associated V2 procedure is executed; etc. + +## 836 18.2.5 Abort Handling + +837 Unless explicitly indicated in subsequent clauses, the following principles are applied by the MAP-user regarding abort +838 handling procedures: + +839 On receipt of a MAP-P-ABORT indication or MAP-U-ABORT Indication primitive from any MAP-provider +840 invocation, the MAP-User issues a MAP-U-ABORT Request primitive to each MAP-provider invocation associated +841 with the same user procedure. + +842 If applicable a decision is made to decide if the affected user procedure has to be retried or not. + +## 843 18.2.6 SDL conventions + +844 The MAP SDLs make use of a number of SDL concepts and conventions, where not all of them may be widely known. +845 Therefore, this clause outlines the use of a few concepts and conventions to improve understanding of the MAP SDLs. + +846 The MAP User SDLs make use of SDL Processes, Procedures and Macros. Processes are independent from each other +847 even if one process starts another one: The actions of both of them have no ordering in time. SDL Procedures and +848 Macros are just used to ease writing of the specification: They contain parts of a behaviour used in several places, and +849 the corresponding Procedure/Macro definition has to be expanded at the position of the Procedure/Macro call. + +850 All Processes are started at system initialisation and live forever, unless process creation/termination is indicated +851 explicitly (i.e. a process is created by some other process). + +852 The direction of Input/Output Signals in the SDL graphs is used to indicate the entity to which/from which +853 communication is directed. If a process A communicates in parallel with processes B and C, all Inputs/Outputs to/from +854 B are directed to one side, whereas communication with C is directed to the other side. However, there has been no + +855 formal convention used that communication to a certain entity (e.g. a HLR) will always be directed to a certain side +856 (e.g. right). + +857 In each state all those Input Signals are listed, which result in an action and/or state change. If an Input Signal is not +858 listed in a state, receipt of this input should lead to an implicit consumption without any action or state change +859 (according to the SDL rules). This implicit consumption is mainly used for receipt of the MAP DELIMITER indication +860 and for receipt of a MAP CLOSE indication, except for a premature MAP CLOSE. + +## 861 18.3 Interaction between MAP Provider and MAP Users + +862 Each MAP User is defined by at least one SDL process. On the dialogue initiating side, the MAP User will create a new +863 instance of a MAP Provider implicit by issuing a MAP-OPEN request. This instance corresponds to a TC Dialogue and +864 lives as long as the dialogue exists (see also clause 14.3). There is a fixed relation between MAP User and this Provider +865 instance, i.e. all MAP service primitives from the MAP User for this dialogue are sent to this instance and all TC +866 components received by this MAP Provider are mapped onto service primitives sent to this MAP User. + +867 On the receiving side a MAP Provider instance is created implicit by receipt of a TC BEGIN indication. The +868 corresponding MAP User is determined by the Application Context name included in this primitive, i.e. each +869 Application Context is associated with one and only one MAP User. An instance of this User will be created implicitly +870 by receiving a MAP-OPEN indication. Note that in some cases there exist several SDL Processes for one MAP User +871 (Application Context), e.g. the processes Register\_SS\_HLR, Erase\_SS\_HLR, Activate\_SS\_HLR, Deactivate\_SS\_HLR, +872 Interrogate\_SS\_HLR, and Register\_Password for the AC Network\_Functional\_SS\_Handling. In these cases, a +873 coordinator process is introduced acting as a MAP User, which in turn starts a sub-process depending on the first MAP +874 service primitive received. + +--- + +## 875 19 Mobility procedures + +### 876 19.1 Location management Procedures + +877 The signalling procedures in this clause support: + +- 878 - Interworking between the VLR and the HLR and between the VLR and the previous VLR (PVLR) when a non- +879 GPRS subscriber performs a location update to a new VLR service area; +- 880 - Interworking between the SGSN, the HLR and the VLR when a subscriber with both GPRS and non-GPRS +881 subscriptions performs a routeing area update in an SGSN and the Gs interface is implemented; +- 882 - Interworking between the SGSN and the VLR when a GPRS subscriber performs a routeing area update to a new +883 SGSN service area; +- 884 - Interworking between the HLR and the VLR and between the HLR and the SGSN to delete a subscriber record +885 from the VLR or the SGSN; +- 886 - Interworking between the VLR and the HLR and between the SGSN and the HLR to report to the HLR that a +887 subscriber record has been purged from the VLR or the SGSN. + +888 The MAP co-ordinating process in the HLR to handle a dialogue opened with the network location updating context is +889 shown in figure 19.1/1. The MAP process invokes a macro not defined in this clause; the definition of this macro can be +890 found as follows: + +891     Receive\_Open\_Ind see clause 25.1.1. + +![State transition diagram for process Location_Management_Coordinator_HLR. The diagram shows transitions between states (Null, Wait_For_Service_Primitive, Update_Location_HLR, Restore_Data_HLR, MAP_CLOSE_req) and actions (Receive_Open_ind, Perform_MAP_Vr_dialogue, MAP_UPDATE_LOCATION_ind, MAP_RESTORE_DATA_ind, MAP_NOTICE_ind, MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind). It includes callouts to figures 19.1.1/13 and 19.3.1/2. The diagram is divided into three horizontal sections by lines, with the bottom section containing four parallel paths.](0e9742f79dd41bef90d8187d1716879b_img.jpg) + +**process Location\_Management\_Coordinator\_HLR** LMC\_HLR1(1) + +Process in the HLR to handle a dialogue opening request using the application context neiLocUpContext. + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the child process + +``` + +stateDiagram-v2 + [*] --> Null + Null --> Receive_Open_ind + Receive_Open_ind --> Perform_MAP_Vr_dialogue : Vr + Perform_MAP_Vr_dialogue --> Null + Receive_Open_ind --> Wait_For_Service_Primitive : OK + Receive_Open_ind --> Null : Error + Wait_For_Service_Primitive --> MAP_UPDATE_LOCATION_ind + Wait_For_Service_Primitive --> MAP_RESTORE_DATA_ind + Wait_For_Service_Primitive --> MAP_NOTICE_ind + Wait_For_Service_Primitive --> MAP_U_ABORT_ind + MAP_UPDATE_LOCATION_ind --> Update_Location_HLR : Figure 19.1.1/13 + Update_Location_HLR --> MAP_UPDATE_LOCATION_ind + MAP_UPDATE_LOCATION_ind --> Relay_Info + MAP_RESTORE_DATA_ind --> Restore_Data_HLR : Figure 19.3.1/2 + Restore_Data_HLR --> MAP_RESTORE_DATA_ind + MAP_RESTORE_DATA_ind --> Relay_Info + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Null + MAP_U_ABORT_ind --> MAP_U_ABORT_req + MAP_U_ABORT_req --> Null + MAP_U_ABORT_req --> Relay_Info + MAP_P_ABORT_req --> Null + MAP_P_ABORT_req --> Relay_Info + MAP_CLOSE_req --> Null + MAP_CLOSE_req --> Relay_Info + +``` + +State transition diagram for process Location\_Management\_Coordinator\_HLR. The diagram shows transitions between states (Null, Wait\_For\_Service\_Primitive, Update\_Location\_HLR, Restore\_Data\_HLR, MAP\_CLOSE\_req) and actions (Receive\_Open\_ind, Perform\_MAP\_Vr\_dialogue, MAP\_UPDATE\_LOCATION\_ind, MAP\_RESTORE\_DATA\_ind, MAP\_NOTICE\_ind, MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind). It includes callouts to figures 19.1.1/13 and 19.3.1/2. The diagram is divided into three horizontal sections by lines, with the bottom section containing four parallel paths. + +892 + +893 + +**Figure 19.1/1: Process Location\_Management\_Coordinator\_HLR** + +## 894 19.1.1 Location updating + +### 895 19.1.1.1 General + +896 The stage 2 specification for GPRS is in 3GPP TS 23.060 [104]. The interworking between the MAP signalling + 897 procedures and the GPRS procedures in the SGSN and the HLR is shown by the transfer of signals between these + 898 procedures. + +899 The message flow for successful inter-VLR location updating when the IMSI can be retrieved from the PVLR is shown +900 in figure 19.1.1/2. + +901 The message flow for successful inter-VLR location updating when the IMSI cannot be retrieved from the PVLR is +902 shown in figure 19.1.1/3. + +903 The message flow for successful GPRS Attach/RA update procedure (Gs interface not installed) is shown in figure +904 19.1.1/4. + +905 The message flow for successful GPRS Attach/RA update procedure combined with a successful VLR location +906 updating (Gs interface installed) is shown in figure 19.1.1/5. + +![Sequence diagram showing message flow for location updating to a new VLR area. Lifelines: MS, MSC/VLR, PVLR, HLR. The diagram shows 12 numbered messages. 1: MS to MSC/VLR (dotted line); 2: MSC/VLR to PVLR; 3: PVLR to MSC/VLR; 4: MSC/VLR to HLR; 5: HLR to PVLR; 6: PVLR to HLR; 7: HLR to MSC/VLR; 8: MSC/VLR to HLR; 9: MSC/VLR to HLR; 10: HLR to MSC/VLR; 11: MSC/VLR to HLR; 12: MSC/VLR to MS (dotted line).](da535696dd83f3ef649c81510656b0d0_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC/VLR + participant PVLR + participant HLR + Note left of MS: 1) A_LU_REQUEST (Note 1) + MS-->>MSC/VLR: + Note right of MSC/VLR: 2) MAP_SEND_IDENTIFICATION_req/ind + MSC/VLR->>PVLR: + Note right of PVLR: 3) MAP_SEND_IDENTIFICATION_rsp/cnf + PVLR-->>MSC/VLR: + Note right of MSC/VLR: 4) MAP_UPDATE_LOCATION_req/ind + MSC/VLR->>HLR: + Note right of HLR: 5) MAP_CANCEL_LOCATION_req/ind + HLR-->>PVLR: + Note right of PVLR: 6) MAP_CANCEL_LOCATION_rsp/cnf + PVLR-->>HLR: + Note right of HLR: 7) MAP_ACTIVATE_TRACE_MODE_req/ind (Note 2) + HLR-->>MSC/VLR: + Note right of MSC/VLR: 8) MAP_ACTIVATE_TRACE_MODE_rsp/cnf (Note 2) + MSC/VLR->>HLR: + Note right of HLR: 9) MAP_INSERT_SUBSCRIBER_DATA_req/ind + HLR-->>MSC/VLR: + Note right of MSC/VLR: 10) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf + MSC/VLR->>HLR: + Note right of HLR: 11) MAP_UPDATE_LOCATION_rsp/cnf + HLR-->>MSC/VLR: + Note right of MSC/VLR: 12) A_LU_CONFIRM (Note 1) + MSC/VLR-->>MS: +``` + +Sequence diagram showing message flow for location updating to a new VLR area. Lifelines: MS, MSC/VLR, PVLR, HLR. The diagram shows 12 numbered messages. 1: MS to MSC/VLR (dotted line); 2: MSC/VLR to PVLR; 3: PVLR to MSC/VLR; 4: MSC/VLR to HLR; 5: HLR to PVLR; 6: PVLR to HLR; 7: HLR to MSC/VLR; 8: MSC/VLR to HLR; 9: MSC/VLR to HLR; 10: HLR to MSC/VLR; 11: MSC/VLR to HLR; 12: MSC/VLR to MS (dotted line). + +907 + +908 PVLR = Previous VLR + +909 + +- 910 1) A\_LU\_REQUEST (Note 1) +- 911 2) MAP\_SEND\_IDENTIFICATION\_req/ind +- 912 3) MAP\_SEND\_IDENTIFICATION\_rsp/cnf +- 913 4) MAP\_UPDATE\_LOCATION\_req/ind +- 914 5) MAP\_CANCEL\_LOCATION\_req/ind +- 915 6) MAP\_CANCEL\_LOCATION\_rsp/cnf +- 916 7) *MAP\_ACTIVATE\_TRACE\_MODE\_req/ind* (Note 2) +- 917 8) *MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf* (Note 2) +- 918 9) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind +- 919 10) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf +- 920 11) MAP\_UPDATE\_LOCATION\_rsp/cnf +- 921 12) A\_LU\_CONFIRM (Note 1) + +922 + +923 NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35]. Services shown in dotted lines +924 indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio +925 path. + +926 NOTE 2: Services printed in *italics* are optional. + +927 + +928 **Figure 19.1.1/2: Message flow for location updating to a new VLR area,** +929 **when the IMSI can be retrieved from the previous VLR** + +![Sequence diagram showing message flow for location updating to a new VLR area. Lifelines: MS, MSC/VLR, PVLR, HLR. The diagram shows 12 numbered messages. Messages 2, 3, and 12 are shown with dashed lines, indicating they are triggered by radio path signalling. Messages 7, 8, and 9 are shown in italics, indicating they are optional. The sequence is: 1) MS to MSC/VLR (A_LU_REQUEST); 2) MSC/VLR to MS (A_IDENTITY_REQUEST); 3) MS to MSC/VLR (A_IDENTITY_RESPONSE); 4) MSC/VLR to HLR (MAP_UPDATE_LOCATION_req/ind); 5) HLR to PVLR (MAP_CANCEL_LOCATION_req/ind); 6) PVLR to HLR (MAP_CANCEL_LOCATION_rsp/cnf); 7) HLR to MSC/VLR (MAP_ACTIVATE_TRACE_MODE_req/ind); 8) MSC/VLR to HLR (MAP_ACTIVATE_TRACE_MODE_rsp/cnf); 9) HLR to MSC/VLR (MAP_INSERT_SUBSCRIBER_DATA_req/ind); 10) MSC/VLR to HLR (MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf); 11) HLR to MSC/VLR (MAP_UPDATE_LOCATION_rsp/cnf); 12) MSC/VLR to MS (A_LU_CONFIRM).](0282ba2f6b0525117a4f18ceeadbb2bb_img.jpg) + +Sequence diagram showing message flow for location updating to a new VLR area. Lifelines: MS, MSC/VLR, PVLR, HLR. The diagram shows 12 numbered messages. Messages 2, 3, and 12 are shown with dashed lines, indicating they are triggered by radio path signalling. Messages 7, 8, and 9 are shown in italics, indicating they are optional. The sequence is: 1) MS to MSC/VLR (A\_LU\_REQUEST); 2) MSC/VLR to MS (A\_IDENTITY\_REQUEST); 3) MS to MSC/VLR (A\_IDENTITY\_RESPONSE); 4) MSC/VLR to HLR (MAP\_UPDATE\_LOCATION\_req/ind); 5) HLR to PVLR (MAP\_CANCEL\_LOCATION\_req/ind); 6) PVLR to HLR (MAP\_CANCEL\_LOCATION\_rsp/cnf); 7) HLR to MSC/VLR (MAP\_ACTIVATE\_TRACE\_MODE\_req/ind); 8) MSC/VLR to HLR (MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf); 9) HLR to MSC/VLR (MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind); 10) MSC/VLR to HLR (MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf); 11) HLR to MSC/VLR (MAP\_UPDATE\_LOCATION\_rsp/cnf); 12) MSC/VLR to MS (A\_LU\_CONFIRM). + +931 + +932 PVLR = Previous VLR + +933 + +- 934 1) A\_LU\_REQUEST (Note 1) + 935 2) A\_IDENTITY\_REQUEST (Note 1) + 936 3) A\_IDENTITY\_RESPONSE (Note 1) + 937 4) MAP\_UPDATE\_LOCATION\_req/ind + 938 5) MAP\_CANCEL\_LOCATION\_req/ind + 939 6) MAP\_CANCEL\_LOCATION\_rsp/cnf + 940 7) *MAP\_ACTIVATE\_TRACE\_MODE\_req/ind* (Note 2) + 941 8) *MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf* (Note 2) + 942 9) *MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind* + 943 10) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf + 944 11) MAP\_UPDATE\_LOCATION\_rsp/cnf + 945 12) A\_LU\_CONFIRM (Note 1) + +946 + +947 NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35]. Services shown in dotted lines + 948 indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio + 949 path. + +950 NOTE 2: Services printed in *italics* are optional. + +951 + +952 + +953 + +**Figure 19.1.1/3: Message flow for location updating to a new VLR area, + when the IMSI cannot be retrieved from the previous VLR** + +![Sequence diagram showing message flow for GPRS location updating between MS, SGSN, PSGSN, and HLR. The diagram shows 10 numbered messages: 1) MS to SGSN (dotted), 2) SGSN to HLR, 3) HLR to PSGSN, 4) PSGSN to HLR, 5) HLR to SGSN, 6) SGSN to HLR, 7) HLR to SGSN, 8) SGSN to HLR, 9) HLR to SGSN, 10) SGSN to MS (dotted).](cf6b2e5b134aeadae43f0ba8d04dea2f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant SGSN + participant PSGSN + participant HLR + Note left of MS: 1) + MS-->>SGSN: + Note right of SGSN: 2) + SGSN->>HLR: + Note right of HLR: 3) + HLR->>PSGSN: + Note right of PSGSN: 4) + PSGSN->>HLR: + Note right of HLR: 5) + HLR->>SGSN: + Note right of SGSN: 6) + SGSN->>HLR: + Note right of HLR: 7) + HLR->>SGSN: + Note right of SGSN: 8) + SGSN->>HLR: + Note right of HLR: 9) + HLR->>SGSN: + Note left of MS: 10) + SGSN-->>MS: + +``` + +Sequence diagram showing message flow for GPRS location updating between MS, SGSN, PSGSN, and HLR. The diagram shows 10 numbered messages: 1) MS to SGSN (dotted), 2) SGSN to HLR, 3) HLR to PSGSN, 4) PSGSN to HLR, 5) HLR to SGSN, 6) SGSN to HLR, 7) HLR to SGSN, 8) SGSN to HLR, 9) HLR to SGSN, 10) SGSN to MS (dotted). + +954 + +955 PSGSN = Previous SGSN + +956 + +957 1) Gb\_ATTACH\_REQUEST or RA\_UPDATE\_REQUEST (Note 1, note 2) + +958 2) MAP\_UPDATE\_GPRS\_LOCATION\_req/ind + +959 3) MAP\_CANCEL\_LOCATION\_req/ind + +960 4) MAP\_CANCEL\_LOCATION\_rsp/cnf + +961 5) *MAP\_ACTIVATE\_TRACE\_MODE\_req/ind* (Note 3) + +962 6) *MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf* (Note 3) + +963 7) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind + +964 8) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf + +965 9) MAP\_UPDATE\_GPRS\_LOCATION\_rsp/cnf + +966 10) Gb\_ATTACH\_ACCEPT or RA\_UPDATE\_ACCEPT (Note 1) + +967 + +968 NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35]. The services shown in dotted lines indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio path. + +969 NOTE 2: For security functions (authentication, ciphering, IMEI check) triggering refer to 3GPP TS 23.060 [104]. The MAP signalling invoked for these functions is described in clause 25 of the present document. + +970 NOTE 3: Services printed in *italics* are optional. + +971 NOTE 4: Refer to 3GPP TS 23.060 [104] for termination of the procedure and triggering of the signalling on the interface between the BSS and the SGSN. + +972 + +973 **Figure 19.1.1/4: Message flow for GPRS location updating (Gs interface not installed)** + +974 + +![Sequence diagram showing signaling between MS, SGSN, VLR, PSGSN, and HLR. The diagram includes 18 numbered messages, some solid and some dotted, representing various GPRS and MAP signaling procedures.](00965742b9d7c465ff2058c927ff2e6c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant SGSN + participant VLR + participant PSGSN + participant HLR + + Note left of MS: 1) Gb_ATTACH_REQUEST or RA_UPDATE_REQUEST + MS-->>SGSN: 1) Gb_ATTACH_REQUEST or RA_UPDATE_REQUEST + Note right of HLR: 2) MAP_UPDATE_GPRS_LOCATION_req/ind + HLR-->>PSGSN: 2) MAP_UPDATE_GPRS_LOCATION_req/ind + Note left of PSGSN: 3) MAP_CANCEL_LOCATION_req/ind + PSGSN-->>HLR: 3) MAP_CANCEL_LOCATION_req/ind + Note right of HLR: 4) MAP_CANCEL_LOCATION_rsp/cnf + HLR-->>PSGSN: 4) MAP_CANCEL_LOCATION_rsp/cnf + Note left of PSGSN: 5) MAP_ACTIVATE_TRACE_MODE_req/ind + PSGSN-->>SGSN: 5) MAP_ACTIVATE_TRACE_MODE_req/ind + Note right of HLR: 6) MAP_ACTIVATE_TRACE_MODE_rsp/cnf + HLR-->>PSGSN: 6) MAP_ACTIVATE_TRACE_MODE_rsp/cnf + Note left of PSGSN: 7) MAP_INSERT_SUBSCRIBER_DATA_req/ind + PSGSN-->>SGSN: 7) MAP_INSERT_SUBSCRIBER_DATA_req/ind + Note right of HLR: 8) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf + HLR-->>PSGSN: 8) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf + Note left of PSGSN: 9) MAP_UPDATE_GPRS_LOCATION_rsp/cnf + PSGSN-->>SGSN: 9) MAP_UPDATE_GPRS_LOCATION_rsp/cnf + Note left of SGSN: 10) Gs_LOCATION_UPDATE_REQUEST + SGSN-->>VLR: 10) Gs_LOCATION_UPDATE_REQUEST + Note right of HLR: 11) MAP_UPDATE_LOCATION_req/ind + HLR-->>VLR: 11) MAP_UPDATE_LOCATION_req/ind + Note left of VLR: 12) MAP_INSERT_SUBSCRIBER_DATA_req/ind + VLR-->>HLR: 12) MAP_INSERT_SUBSCRIBER_DATA_req/ind + Note right of HLR: 13) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf + HLR-->>VLR: 13) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf + Note left of VLR: 14) MAP_UPDATE_LOCATION_rsp/cnf + VLR-->>HLR: 14) MAP_UPDATE_LOCATION_rsp/cnf + Note left of VLR: 15) Gs_LOCATION_UPDATE_ACCEPT + VLR-->>SGSN: 15) Gs_LOCATION_UPDATE_ACCEPT + Note left of MS: 16) Gb_ATTACH_ACCEPT or RA_UPDATE_ACCEPT + MS-->>SGSN: 16) Gb_ATTACH_ACCEPT or RA_UPDATE_ACCEPT + Note left of SGSN: 17) Gb_TMSI_REALLOCATION_COMPLETE + SGSN-->>MS: 17) Gb_TMSI_REALLOCATION_COMPLETE + Note left of VLR: 18) Gs_TMSI_REALLOCATION_COMPLETE + VLR-->>SGSN: 18) Gs_TMSI_REALLOCATION_COMPLETE + +``` + +Sequence diagram showing signaling between MS, SGSN, VLR, PSGSN, and HLR. The diagram includes 18 numbered messages, some solid and some dotted, representing various GPRS and MAP signaling procedures. + +978 + +979 + +980 1) Gb\_ATTACH\_REQUEST or RA\_UPDATE\_REQUEST (Note 1, note 2) + +981 2) MAP\_UPDATE\_GPRS\_LOCATION\_req/ind + +982 3) MAP\_CANCEL\_LOCATION\_req/ind + +983 4) MAP\_CANCEL\_LOCATION\_rsp/cnf + +984 5) *MAP\_ACTIVATE\_TRACE\_MODE\_req/ind* (Note 3) + +985 6) *MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf* (Note 3) + +986 7) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind + +987 8) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf + +988 9) MAP\_UPDATE\_GPRS\_LOCATION\_rsp/cnf + +989 10) Gs\_LOCATION\_UPDATE\_REQUEST (Note 4) + +990 11) MAP\_UPDATE\_LOCATION\_req/ind (Note 5) + +991 12) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind + +992 13) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf + +993 14) MAP\_UPDATE\_LOCATION\_rsp/cnf + +994 15) Gs\_LOCATION\_UPDATE\_ACCEPT (Note 4) + +995 16) Gb\_ATTACH\_ACCEPT or RA\_UPDATE\_ACCEPT (Note 1) + +996 17) Gb\_TMSI\_REALLOCATION\_COMPLETE (Note 1) + +997 18) Gs\_TMSI\_REALLOCATION\_COMPLETE (Note 4) + +998 + +999 NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35]. The services shown in dotted lines indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio path. + +1000 NOTE 2: For security functions (authentication, ciphering, IMEI check) triggering refer to 3GPP TS 23.060 [104]. + +1001 MAP processes invoked for those procedures are described in clause 25.5. + +1002 NOTE 3: Services printed in *italics* are optional. + +1005 NOTE 5: For details of the procedure on the path between the SGSN and the VLR, see 3GPP TS 29.018 [106]. The +1006 services shown in chain lines indicate the trigger provided by the signalling on the path between the SGSN +1007 and the VLR, and the signalling triggered on the path between the SGSN and the VLR. +1008 NOTE 4: Refer to 3GPP TS 23.060 [104] for termination of the procedure and triggering of the signalling on the +1009 interface between the BSS and the SGSN. +1010 NOTE 5: For simplicity, the Location Cancellation procedure towards the previous VLR and optional tracing +1011 activation towards the new VLR are not shown in this figure. +1012 +1013 + +**Figure 19.1.1/5: Message flow for GPRS location updating (Gs interface installed)** + +#### 1014 19.1.1.2 Procedures in the VLR + +1015 The MAP process in the VLR for location updating for a non-GPRS subscriber is shown in figure 19.1.1/6. The MAP +1016 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +1017 Receive\_Open\_Cnf see clause 25.1.2; + +1018 Check\_Confirmation see clause 25.2.2. + +1019 The MAP process in the VLR to retrieve the IMSI of a subscriber from the previous VLR (PVLRR) is shown in figure +1020 19.1.1/7. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as +1021 follows: + +1022 Receive\_Open\_Cnf see clause 25.1.2; + +1023 Check\_Confirmation see clause 25.2.2. + +1024 The process in the VLR for location updating for a GPRS subscriber when the Gs interface is installed is shown in +1025 figure 19.1.1/8. + +1026 The macro GPRS\_Location\_Update\_Completion\_VLR is shown in figure 19.1.1/9. The macro invokes a process not +1027 defined in this clause; the definition of this process can be found as follows: + +1028 Subscriber\_Present\_VLR see clause 25.10.1. + +1029 The macro GPRS\_Update\_HLR\_VLR is shown in figure 19.1.1/10. The macro invokes macros not defined in this +1030 clause; the definitions of these macros can be found as follows: + +1031 Receive\_Open\_Cnf see clause 25.1.2; + +1032 Check\_Confirmation see clause 25.2.2; + +1033 Insert\_Subs\_Data\_VLR see clause 25.7.1; + +1034 Activate\_Tracing\_VLR see clause 25.9.4. + +#### 1035 19.1.1.3 Procedure in the PVLRR + +1036 The MAP process in the PVLRR to handle a request for the IMSI of a subscriber from the new VLR is shown in figure +1037 19.1.1/11. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as +1038 follows: + +1039 Receive\_Open\_Ind see clause 25.1.1. + +#### 1040 19.1.1.4 Procedure in the SGSN + +1041 The MAP process in the SGSN for location updating for a GPRS subscriber is shown in figure 19.1.1/12. The MAP +1042 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +1043 Receive\_Open\_Cnf see clause 25.1.2; + +1044 Check\_Confirmation see clause 25.2.2; + +1045 Insert\_Subs\_Data\_SGSN see clause 25.7.2; + +1046     Activate\_Tracing\_SGSN   see clause 25.9.5. + +1047 Sheet 2: The procedure Check\_User\_Error\_In\_Serving\_Network\_Entity is specific to Super-Charger; it is specified in +1048 3GPP TS 23.116 [110]. + +#### 1049 19.1.1.5     Procedures in the HLR + +1050 The MAP process in the HLR to handle a location updating request from a VLR is shown in figure 19.1.1/13. The MAP +1051 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1052     Check\_Confirmation   see clause 25.2.2. + +1053 The MAP process in the HLR to handle a location updating request from an SGSN is shown in figure 19.1.1/14. The +1054 MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +1055     Receive\_Open\_Ind     see clause 25.1.1; + +1056     Check\_Indication     see clause 25.2.1; + +1057     Check\_Confirmation   see clause 25.2.2; + +1058     Control\_Tracing\_With\_SGSN\_HLR see clause 25.9.7. + +1059 Sheet 2: The procedure Super\_Charged\_Cancel\_Location\_HLR is specific to Super-Charger; it is specified in +1060 3GPP TS 23.116 [110]. If the HLR does not support the Super-Charger functionality, processing continues from the +1061 "No" exit of the test "Result=Pass?". + +1062 Sheet 2: The procedure Super\_Charged\_Location\_Updating\_HLR is specific to Super-Charger; it is specified in +1063 3GPP TS 23.116 [110]. If the HLR does not support the Super-Charger functionality, processing continues from the +1064 "No" exit of the test "Result=Pass?". + +1065 Sheet 2: If the HLR supports the Administrative Restriction of Subscribers' Access feature and roaming is allowed in +1066 the VPLMN then the HLR may check the "Supported RAT Types" received from the VLR against the access restriction +1067 parameters. If this check fails then the decision box "Roaming allowed in this PLMN" shall take the exit "No". + +1068 The MAP process in the HLR to notify Short Message Service Centres that a subscriber is now reachable is shown in +1069 figure 19.1.1/15. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found +1070 as follows: + +1071     Alert\_Service\_Centre\_HLR see clause 25.10.3. + +![Flowchart for process Update_Location_VLR. It starts with 'Null', followed by 'Update Location', then a merge point with messages MAP_OPEN_req, MAP_UPDATE_LOCATION_req, and MAP_DELIMITER_req. It then goes to 'Receive_Open_Cnf'. From there, three paths emerge: 'Error' leads to 'Set negative response: System failure' -> 'Update Location negative response' -> 'Null'; 'Vr' leads to 'Perform MAP Vr dialogue' -> 'Result'; 'OK' leads to 'Wait_For_HLR_Response'. 'Result' has four outcomes: 'Unknown Subscriber', 'Roaming not allowed', 'Procedure error', and 'Aborted', all leading to 'Set negative response' boxes which then lead to 'Update Location negative response' -> 'Null'. 'Procedure error' also leads to 'Update Location ack' -> 'Null'. 'Wait_For_HLR_Response' branches into 'MAP_ACTIVATE_TRACE_MODE_ind' -> 'Activate Trace Mode' and 'MAP_INSERT_SUBSCRIBER_DATA_ind' -> 'Insert Subscriber Data', both leading to 'Wait_For_HLR_Or_Application_Response' -> 'Null'. A label 'HLR number' is near the 'Update Location ack' path.](99eaf23e3d47f7e6cd7837e5587b6aee_img.jpg) + +**process Update\_Location\_VLR** **UL\_VLR1(2)** + +Process in the VLR to handle a location updating dialogue with the HLR when the Gs interface is not used + +Signals to/from the left are to/from the location management application process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/from the HLR + +``` + + graph TD + Start([Null]) --> UpdateLoc{Update Location} + UpdateLoc --> Merge(( )) + Merge --> Messages["MAP_OPEN_req +MAP_UPDATE_LOCATION_req +MAP_DELIMITER_req"] + Messages --> ReceiveCnf[Receive_Open_Cnf] + + ReceiveCnf -- Error --> ErrResp["Set negative response: +System failure"] + ErrResp --> ErrLoc{Update Location negative response} + ErrLoc --> Null1([Null]) + + ReceiveCnf -- Vr --> PerformVr[Perform MAP Vr dialogue] + + PerformVr --> Result{Result} + + Result -- "Unknown Subscriber" --> Res1["Set negative response: +Unknown subscriber"] + Result -- "Roaming not allowed" --> Res2["Set negative response: +Roaming not allowed"] + Result -- "Procedure error" --> Res3["Set negative response: +Procedure error"] + Result -- "Aborted" --> Res4["Set negative response: +Aborted"] + + Res1 --> NegLoc{Update Location negative response} + Res2 --> NegLoc + Res3 --> NegLoc + Res3 --> PosLoc{Update Location ack} + Res4 --> NegLoc + + NegLoc --> Null2([Null]) + + PosLoc --> Null3([Null]) + + ReceiveCnf -- OK --> WaitHLR[Wait_For_HLR_Response] + + WaitHLR -- "MAP_ACTIVATE_TRACE_MODE_ind" --> ActTrace{Activate Trace Mode} + WaitHLR -- "MAP_INSERT_SUBSCRIBER_DATA_ind" --> InsertData{Insert Subscriber Data} + + ActTrace --> WaitApp[Wait_For_HLR_Or_Application_Response] + InsertData --> WaitApp + + WaitApp --> Null4([Null]) + + Note["HLR number"] -.-> PosLoc + +``` + +Flowchart for process Update\_Location\_VLR. It starts with 'Null', followed by 'Update Location', then a merge point with messages MAP\_OPEN\_req, MAP\_UPDATE\_LOCATION\_req, and MAP\_DELIMITER\_req. It then goes to 'Receive\_Open\_Cnf'. From there, three paths emerge: 'Error' leads to 'Set negative response: System failure' -> 'Update Location negative response' -> 'Null'; 'Vr' leads to 'Perform MAP Vr dialogue' -> 'Result'; 'OK' leads to 'Wait\_For\_HLR\_Response'. 'Result' has four outcomes: 'Unknown Subscriber', 'Roaming not allowed', 'Procedure error', and 'Aborted', all leading to 'Set negative response' boxes which then lead to 'Update Location negative response' -> 'Null'. 'Procedure error' also leads to 'Update Location ack' -> 'Null'. 'Wait\_For\_HLR\_Response' branches into 'MAP\_ACTIVATE\_TRACE\_MODE\_ind' -> 'Activate Trace Mode' and 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind' -> 'Insert Subscriber Data', both leading to 'Wait\_For\_HLR\_Or\_Application\_Response' -> 'Null'. A label 'HLR number' is near the 'Update Location ack' path. + +1072 + +1073 + +**Figure 19.1.1/6 (sheet 1 of 2): Process Update\_Location\_VLR** + +![State transition diagram for Update_Location_VLR process. It starts with Wait_For_HLR_Or_Application_Response, branches into various MAP operations (Activate Trace Mode, Insert Subscriber Data, MAP_INSERT_SUBSCRIBER_DATA_ind, MAP_FORWARD_CHECK_SS_ind), and ends with Null states after processing responses like Update Location ack or negative response.](14512fe72d075c1f96895f3037f52aad_img.jpg) + +**process Update\_Location\_VLR** UL\_VLR2(2) + +Process in the VLR to handle a location updating dialogue with the HLR when the Gs interface is not used + +``` + +stateDiagram-v2 + [*] --> Wait_For_HLR_Or_Application_Response + state "Wait_For_HLR_Or_Application_Response" as Wait_For_HLR_Or_Application_Response + state "Activate Trace Mode ack" as Activate_Trace_Mode_ack + state "Activate Trace Mode negative response" as Activate_Trace_Mode_neg_resp + state "Insert Subscriber Data ack" as Insert_Subscriber_Data_ack + state "Insert Subscriber Data negative response" as Insert_Subscriber_Data_neg_resp + state "MAP_INSERT_SUBSCRIBER_DATA_ind" as MAP_INSERT_SUBSCRIBER_DATA_ind + state "MAP_FORWARD_CHECK_SS_ind" as MAP_FORWARD_CHECK_SS_ind + state "Set User Error" as Set_User_Error + state "MAP_ACTIVATE_TRACE_MODE_rsp" as MAP_ACTIVATE_TRACE_MODE_rsp + state "MAP_INSERT_SUBSCRIBER_DATA_rsp" as MAP_INSERT_SUBSCRIBER_DATA_rsp + state "Insert Subscriber Data" as Insert_Subscriber_Data + state "Forward Check SS" as Forward_Check_SS + state "Wait_For_HLR_Or_Application_Response" as Wait_For_HLR_Or_Application_Response + state "MAP_UPDATE_LOCATION_cnf" as MAP_UPDATE_LOCATION_cnf + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" as MAP_U_ABORT_ind + state "Check Confirmation" as Check_Confirmation + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "Set negative response" as Set_Neg_Resp + state "Set negative response: System failure" as Set_Neg_Resp_Sys_Fail + state "Update Location negative response" as Update_Location_Neg_Resp + state "Update Location ack" as Update_Location_Ack + state "Null" as Null + + Wait_For_HLR_Or_Application_Response --> Activate_Trace_Mode_ack + Wait_For_HLR_Or_Application_Response --> Activate_Trace_Mode_neg_resp + Wait_For_HLR_Or_Application_Response --> Insert_Subscriber_Data_ack + Wait_For_HLR_Or_Application_Response --> Insert_Subscriber_Data_neg_resp + Wait_For_HLR_Or_Application_Response --> MAP_INSERT_SUBSCRIBER_DATA_ind + Wait_For_HLR_Or_Application_Response --> MAP_FORWARD_CHECK_SS_ind + + Activate_Trace_Mode_ack --> MAP_ACTIVATE_TRACE_MODE_rsp + Activate_Trace_Mode_neg_resp --> Set_User_Error + Set_User_Error --> MAP_ACTIVATE_TRACE_MODE_rsp + Insert_Subscriber_Data_ack --> MAP_INSERT_SUBSCRIBER_DATA_rsp + Insert_Subscriber_Data_neg_resp --> Set_User_Error + Set_User_Error --> MAP_INSERT_SUBSCRIBER_DATA_rsp + MAP_INSERT_SUBSCRIBER_DATA_ind --> Insert_Subscriber_Data + MAP_FORWARD_CHECK_SS_ind --> Forward_Check_SS + + MAP_ACTIVATE_TRACE_MODE_rsp --> Wait_For_HLR_Or_Application_Response + MAP_INSERT_SUBSCRIBER_DATA_rsp --> Wait_For_HLR_Or_Application_Response + Insert_Subscriber_Data --> Wait_For_HLR_Or_Application_Response + Forward_Check_SS --> Wait_For_HLR_Or_Application_Response + + Wait_For_HLR_Or_Application_Response --> MAP_UPDATE_LOCATION_cnf + Wait_For_HLR_Or_Application_Response --> MAP_NOTICE_ind + Wait_For_HLR_Or_Application_Response --> MAP_U_ABORT_ind + + MAP_UPDATE_LOCATION_cnf --> Check_Confirmation + Check_Confirmation --> Set_Neg_Resp : User Error, Provider Error, Data Error + Check_Confirmation --> Update_Location_Ack : OK + Update_Location_Ack --> Null + Set_Neg_Resp --> Update_Location_Neg_Resp + Update_Location_Neg_Resp --> Null + + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Set_Neg_Resp_Sys_Fail + Set_Neg_Resp_Sys_Fail --> Update_Location_Neg_Resp + Update_Location_Neg_Resp --> Null + +``` + +Signals to/from the left are to/from the location management application process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/from the HLR + +State transition diagram for Update\_Location\_VLR process. It starts with Wait\_For\_HLR\_Or\_Application\_Response, branches into various MAP operations (Activate Trace Mode, Insert Subscriber Data, MAP\_INSERT\_SUBSCRIBER\_DATA\_ind, MAP\_FORWARD\_CHECK\_SS\_ind), and ends with Null states after processing responses like Update Location ack or negative response. + +1074 + +1075 + +Figure 19.1.1/6 (sheet 2 of 2): Process Update\_Location\_VLR + +![Flowchart for process Send_Identification_VLR. The process starts with 'Null', followed by 'Send Identification', then a message box with MAP_OPEN_req, MAP_SEND_IDENTIFICATION_req, and MAP_DELIMITER_req. It then enters 'Receive_Open_Cnf' with three branches: Error (leading to 'Set negative response: System failure'), Vr (leading to 'Perform MAP Vr dialogue'), and OK (leading to 'Wait_For_PVLR_Response'). The 'Perform MAP Vr dialogue' branch leads to a decision 'IMSI received?'. If 'No', it goes to 'Send Identification negative response' and then 'Null'. If 'Yes', it goes to 'Send Identification ack' and then 'Null'. The 'Wait_For_PVLR_Response' branch leads to a message box with MAP_SEND_IDENTIFICATION_cnf, then 'Check Confirmation'. 'Check Confirmation' has an 'OK' branch leading to 'Wait_For_Dialogue_End' and a 'User Error, Provider Error, Data Error' branch leading to a decision 'IMSI received?'. If 'No', it goes to 'Send Identification negative response' and then 'Null'. If 'Yes', it goes to 'Send Identification ack' and then 'Null'. 'Wait_For_Dialogue_End' leads to 'MAP_CLOSE_ind', which leads to 'Send Identification ack' and then 'Null'. 'Wait_For_Dialogue_End' also leads to 'MAP_DELIMITER_ind', which leads to a message box with MAP_SEND_IDENTIFICATION_req and MAP_DELIMITER_req, which then leads to 'Wait_For_PVLR_Response'.](38ce7d231f30a146f0db151df41f9091_img.jpg) + +**process Send\_Identification\_VLR** **SI\_VLR1(2)** + +Process in the VLR to request IMSI and authentication information from the previous VLR + +Signals to/from the left are to/from the location management application process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/from the PVLR + +``` + + graph TD + Start([Null]) --> SendID[Send Identification] + SendID --> Msg1[MAP_OPEN_req +MAP_SEND_IDENTIFICATION_req +MAP_DELIMITER_req] + Msg1 --> RecvOpenCnf[Receive_Open_Cnf] + RecvOpenCnf -- Error --> NegResp[Set negative response: +System failure] + RecvOpenCnf -- Vr --> PerformVr[Perform MAP Vr dialogue] + RecvOpenCnf -- OK --> WaitPVLR[Wait_For_PVLR_Response] + + PerformVr --> IMSIRecVr{IMSI received?} + IMSIRecVr -- No --> NegRespVr[Send Identification negative response] + NegRespVr --> NullVr([Null]) + + IMSIRecVr -- Yes --> AckVr[Send Identification ack] + AckVr --> NullVr + + WaitPVLR --> Msg2[MAP_SEND_IDENTIFICATION_cnf] + Msg2 --> CheckConf[Check Confirmation] + + CheckConf -- OK --> WaitDialogEnd[Wait_For_Dialogue_End] + + CheckConf -- "User Error, Provider Error, Data Error" --> IMSIRec{IMSI received?} + + IMSIRec -- No --> NegRespMain[Send Identification negative response] + NegRespMain --> NullMain([Null]) + + IMSIRec -- Yes --> AckMain[Send Identification ack] + AckMain --> NullMain + + WaitDialogEnd --> MAPCloseInd[MAP_CLOSE_ind] + + MAPCloseInd --> AckMain + AckMain --> NullMain + + WaitDialogEnd --> MAPDelimInd[MAP_DELIMITER_ind] + + MAPDelimInd --> Msg3[MAP_SEND_IDENTIFICATION_req +MAP_DELIMITER_req] + + Msg3 --> WaitPVLR + +``` + +Flowchart for process Send\_Identification\_VLR. The process starts with 'Null', followed by 'Send Identification', then a message box with MAP\_OPEN\_req, MAP\_SEND\_IDENTIFICATION\_req, and MAP\_DELIMITER\_req. It then enters 'Receive\_Open\_Cnf' with three branches: Error (leading to 'Set negative response: System failure'), Vr (leading to 'Perform MAP Vr dialogue'), and OK (leading to 'Wait\_For\_PVLR\_Response'). The 'Perform MAP Vr dialogue' branch leads to a decision 'IMSI received?'. If 'No', it goes to 'Send Identification negative response' and then 'Null'. If 'Yes', it goes to 'Send Identification ack' and then 'Null'. The 'Wait\_For\_PVLR\_Response' branch leads to a message box with MAP\_SEND\_IDENTIFICATION\_cnf, then 'Check Confirmation'. 'Check Confirmation' has an 'OK' branch leading to 'Wait\_For\_Dialogue\_End' and a 'User Error, Provider Error, Data Error' branch leading to a decision 'IMSI received?'. If 'No', it goes to 'Send Identification negative response' and then 'Null'. If 'Yes', it goes to 'Send Identification ack' and then 'Null'. 'Wait\_For\_Dialogue\_End' leads to 'MAP\_CLOSE\_ind', which leads to 'Send Identification ack' and then 'Null'. 'Wait\_For\_Dialogue\_End' also leads to 'MAP\_DELIMITER\_ind', which leads to a message box with MAP\_SEND\_IDENTIFICATION\_req and MAP\_DELIMITER\_req, which then leads to 'Wait\_For\_PVLR\_Response'. + +1076 + +1077 + +Figure 19.1.1/7 (sheet 1 of 2): Process Send\_Identification\_VLR + +![Flowchart for process Send_Identification_VLR. It starts with 'Wait_For_PVLR_Response', leading to a split. One path goes left to 'Abort' then 'Null'. Another path goes right through 'MAP_NOTICE_ind' and 'MAP_CLOSE_req' to a decision 'IMSI received?'. If 'No', it goes left to 'Send Identification negative response' then 'Null'. If 'Yes', it goes right to 'Send Identification ack' then 'Null'. A third path from the initial split goes right to an unlabeled box, which then connects to a box containing 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind'.](67f1290c75b9e4a4a36af1afacbb7932_img.jpg) + +**process Send\_Identification\_VLR** **SI\_VLR2(2)** + +Process in the VLR to request IMSI and authentication information from the previous VLR + +Signals to/from the left are to/from the location management application process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/from the PVLR + +``` + + graph TD + Start([Wait_For_PVLR_Response]) --> Split1(( )) + Split1 --> Abort[/Abort/] + Abort --> Null1([Null]) + Split1 --> Notice[/MAP_NOTICE_ind/] + Notice --> Close[/MAP_CLOSE_req/] + Close --> IMSI{IMSI received?} + IMSI -- No --> NegResponse[/Send Identification negative response/] + NegResponse --> Null2([Null]) + IMSI -- Yes --> Ack[/Send Identification ack/] + Ack --> Null3([Null]) + Split1 --> Unlabeled[/ /] + Unlabeled --> Signals[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + +``` + +Flowchart for process Send\_Identification\_VLR. It starts with 'Wait\_For\_PVLR\_Response', leading to a split. One path goes left to 'Abort' then 'Null'. Another path goes right through 'MAP\_NOTICE\_ind' and 'MAP\_CLOSE\_req' to a decision 'IMSI received?'. If 'No', it goes left to 'Send Identification negative response' then 'Null'. If 'Yes', it goes right to 'Send Identification ack' then 'Null'. A third path from the initial split goes right to an unlabeled box, which then connects to a box containing 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind'. + +1078 + +1079 + +**Figure 19.1.1/7 (sheet 2 of 2): Process Send\_Identification\_VLR** + +![Flowchart for process GPRS_Update_Location_Area_VLR. It starts with Null, receives Gs_GPRS_LOCATION_UPDATING_ind, checks if subscriber is known. If no, it confirms location info in HLR (False), then checks if radio contact is confirmed (True), updates LAI, and checks if VLR-SGSN association exists. If no, it creates association; if yes, it updates association. Then it checks if HLR update is required. If yes, it goes to connector 1. If no, it checks if PgA is supported. If no, it sets GPRS_Location_Update_Completion_VLR, updates register, and ends at Null. If yes, it checks if PgA changed. If no, it goes to connector 1. If yes, it checks if HLR supports PgA. If no, it goes to connector 1. If yes, it sets skip subscriber data update and goes to connector 1.](0da7dffc768694ed2710d63f80ca7c19_img.jpg) + +process GPRS\_Update\_Location\_Area\_VLR + +GULA\_VLR1(2) + +Process in the VLR to handle an Update Location Area request received over the Gs interface + +Signals to/from the left are to/from the SGSN + +``` + +graph TD + Start([Null]) --> Input{{Gs_GPRS_LOCATION_UPDATING_ind}} + Input --> SubKnown{Subscriber known?} + SubKnown -- No --> LocInfo[Location Information Confirmed in HLR:=False] + LocInfo --> RadioContact[Confirmed by Radio Contact:=True] + RadioContact --> UpdateLAI[Update LAI] + UpdateLAI --> AssocExists{VLR-SGSN association exists?} + AssocExists -- No --> CreateAssoc[Create association] + AssocExists -- Yes --> UpdateAssoc[Update association] + CreateAssoc --> HLRUpdate{HLR update required?} + UpdateAssoc --> HLRUpdate + HLRUpdate -- Yes --> C1((1)) + HLRUpdate -- No --> PgASupported{PgA supported?} + PgASupported -- No --> GPRSUpdate[GPRS_Location_Update_Completion_VLR] + PgASupported -- Yes --> PgAChanged{PgA changed?} + PgAChanged -- No --> C1 + PgAChanged -- Yes --> HLRSupportPgA{HLR support PgA?} + HLRSupportPgA -- No --> C1 + HLRSupportPgA -- Yes --> SkipData[Set skip Subscriber Data Update] + SkipData --> C2((1)) + GPRSUpdate --> UpdateReg[Update register] + UpdateReg --> End([Null]) + +``` + +Flowchart for process GPRS\_Update\_Location\_Area\_VLR. It starts with Null, receives Gs\_GPRS\_LOCATION\_UPDATING\_ind, checks if subscriber is known. If no, it confirms location info in HLR (False), then checks if radio contact is confirmed (True), updates LAI, and checks if VLR-SGSN association exists. If no, it creates association; if yes, it updates association. Then it checks if HLR update is required. If yes, it goes to connector 1. If no, it checks if PgA is supported. If no, it sets GPRS\_Location\_Update\_Completion\_VLR, updates register, and ends at Null. If yes, it checks if PgA changed. If no, it goes to connector 1. If yes, it checks if HLR supports PgA. If no, it goes to connector 1. If yes, it sets skip subscriber data update and goes to connector 1. + +1080 + +1081 + +Figure 19.1.1/8 (sheet 1 of 2): Process GPRS\_Update\_Location\_Area\_VLR + +![Flowchart for GPRS_Update_Location_Area_VLR process. It starts at connector '1', goes to 'GPRS_Update_HLR_VLR'. From there, 'OK' leads to 'GPRS_Location_Update_Completion_VLR' -> 'Update register' -> 'Null'. 'Procedure_Error' leads to 'Set User Error' -> 'Gs_GPRS_LOCATION_UPDATING_rsp' -> 'Null'. 'Unknown_Subscriber, Roaming_Not_Allowed' leads to 'Delete subscriber record' -> 'Set User Error'.](a9cffaea1e423f35f76268ce60023115_img.jpg) + +**process GPRS\_Update\_Location\_Area\_VLR** **GULA\_VLR2(2)** + +Process in the VLR to handle an Update Location Area request received over the Gs interface + +Signals to/from the left are to/from the SGSN + +``` + + graph TD + 1((1)) --> GPRS_Update_HLR_VLR[GPRS_Update_HLR_VLR] + GPRS_Update_HLR_VLR -- OK --> GPRS_Location_Update_Completion_VLR[GPRS_Location_Update_VLR] + GPRS_Location_Update_Completion_VLR --> Update_register[Update register] + Update_register --> Null1([Null]) + + GPRS_Update_HLR_VLR -- Procedure_Error --> Set_User_Error[Set User Error] + Set_User_Error --> Gs_GPRS_LOCATION_UPDATING_rsp[Gs_GPRS_LOCATION_UPDATING_rsp] + Gs_GPRS_LOCATION_UPDATING_rsp --> Null2([Null]) + + GPRS_Update_HLR_VLR -- "Unknown_Subscriber, Roaming_Not_Allowed" --> Delete_subscriber_record[Delete subscriber record] + Delete_subscriber_record --> Set_User_Error + +``` + +Flowchart for GPRS\_Update\_Location\_Area\_VLR process. It starts at connector '1', goes to 'GPRS\_Update\_HLR\_VLR'. From there, 'OK' leads to 'GPRS\_Location\_Update\_Completion\_VLR' -> 'Update register' -> 'Null'. 'Procedure\_Error' leads to 'Set User Error' -> 'Gs\_GPRS\_LOCATION\_UPDATING\_rsp' -> 'Null'. 'Unknown\_Subscriber, Roaming\_Not\_Allowed' leads to 'Delete subscriber record' -> 'Set User Error'. + +1082 + +1083 + +**Figure 19.1.1/8 (sheet 2 of 2): Process GPRS\_Update\_Location\_Area\_VLR** + +![Flowchart for GPRS_Location_Update_Completion_VLR macro. It starts with a decision 'Roaming allowed in target LA?'. If 'No', it sets 'LA not allowed:= True', 'Set User Error' (See 3GPP TS 29.018), and sends 'Gs_GPRS_LOCATION_UPDATING_rsp'. If 'Yes', it sets 'LA not allowed:= False' and 'IMSI detached:= False', then checks 'Subscriber Present_VLR'. If 'No', it sends 'Set result' and 'Gs_GPRS_LOCATION_UPDATING_rsp'. If 'Yes', it allocates a new TMSI, sets the TMSI parameter, starts a TMSI reallocation timer, sends 'Gs_GPRS_LOCATION_UPDATING_rsp', and waits for 'TMSI_Allocation_Confirm'. Upon confirmation, it sends 'GS_GPRS_TMSI_REALLOCATION_COMPLETE_ind'. If the 'TMSI reallocation timer expired' (Internal), it freezes the old TMSI.](9d79dd380d110194f9f53b210c40a1ec_img.jpg) + +**macrodefinition GPRS\_Location\_Update\_Completion\_VLR** **GLUC\_VLR1(1)** + +Macro in the VLR to complete the local handling of an Update Location Area request received over the Gs interface + +Signals to/from the left are to/from the SGSN + +``` + +graph TD + Start([Start]) --> Roaming{Roaming allowed in target LA?} + Roaming -- No --> LA_Not_Allowed[LA not allowed:= True] + LA_Not_Allowed --> Set_User_Error[Set User Error +See 3GPP TS 29.018] + Set_User_Error --> Gs_Rsp_1{Gs_GPRS_LOCATION_UPDATING_rsp} + Gs_Rsp_1 --> End_1([End]) + Roaming -- Yes --> LA_Not_Allowed_Yes[LA not allowed:= False +IMSI detached:= False] + LA_Not_Allowed_Yes --> Sub_Present{Subscriber Present_VLR} + Sub_Present -- No --> Set_Result[Set result] + Set_Result --> Gs_Rsp_2{Gs_GPRS_LOCATION_UPDATING_rsp} + Gs_Rsp_2 --> End_2([End]) + Sub_Present -- Yes --> Allocate_TMSI[Allocate TMSI] + Allocate_TMSI --> Set_TMSI_Param[Set TMSI parameter] + Set_TMSI_Param --> Start_Timer[Start TMSI reallocation timer] + Start_Timer --> Gs_Rsp_3{Gs_GPRS_LOCATION_UPDATING_rsp} + Gs_Rsp_3 --> Wait_Confirm([Wait_For_TMSI_Allocation_Confirm]) + Wait_Confirm --> Complete_Ind{GS_GPRS_TMSI_REALLOCATION_COMPLETE_ind} + Complete_Ind --> End_3([End]) + Wait_Confirm --> Timer_Expired{TMSI reallocation timer expired} + Timer_Expired -.-> Internal[Internal] + Timer_Expired --> Freeze_Old_TMSI[Freeze old TMSI] + Freeze_Old_TMSI --> End_4([End]) + +``` + +Flowchart for GPRS\_Location\_Update\_Completion\_VLR macro. It starts with a decision 'Roaming allowed in target LA?'. If 'No', it sets 'LA not allowed:= True', 'Set User Error' (See 3GPP TS 29.018), and sends 'Gs\_GPRS\_LOCATION\_UPDATING\_rsp'. If 'Yes', it sets 'LA not allowed:= False' and 'IMSI detached:= False', then checks 'Subscriber Present\_VLR'. If 'No', it sends 'Set result' and 'Gs\_GPRS\_LOCATION\_UPDATING\_rsp'. If 'Yes', it allocates a new TMSI, sets the TMSI parameter, starts a TMSI reallocation timer, sends 'Gs\_GPRS\_LOCATION\_UPDATING\_rsp', and waits for 'TMSI\_Allocation\_Confirm'. Upon confirmation, it sends 'GS\_GPRS\_TMSI\_REALLOCATION\_COMPLETE\_ind'. If the 'TMSI reallocation timer expired' (Internal), it freezes the old TMSI. + +1084 + +1085 + +**Figure 19.1.1/9: Macro GPRS\_Location\_Update\_Completion\_VLR** + +macrodefinition GPRS\_Update\_HLR\_VLR + +GUHLR\_VLR1(2) + +Macro in the VLR to handle a location updating dialogue with the HLR when the Gs interface is used + +Signals to/from the right are to/from the HLR + +![Flowchart for GPRS_Update_HLR_VLR macro. It starts with a decision 'HLR address known?'. If 'No', it goes to 'Roaming_Not_Allowed'. If 'Yes', it sends 'MAP_OPEN_req', 'MAP_UPDATE_LOCATION_req', and 'MAP_DELIMITER_req', then receives 'Open_Cnf'. From 'Open_Cnf', it branches based on 'Error', 'Vr', and 'OK'. 'Error' leads to 'Procedure_Error'. 'Vr' leads to 'Perform MAP_Vr dialogue', which then leads to 'Result?'. 'Result?' branches into 'Procedure error, Aborted' (leading to 'Procedure_Error'), 'Unknown subscriber' (leading to 'Unknown_Subscriber'), 'Roaming not allowed' (leading to 'Roaming_Not_Allowed'), and 'HLR number' (leading to 'OK'). 'OK' from 'Open_Cnf' leads to 'Wait_For_HLR_Response'. Both 'Unknown_Subscriber' and 'HLR number' lead to 'Wait_For_HLR_Response'. From 'Wait_For_HLR_Response', it branches into 'Insert Subs Data_VLR', 'Activate Tracing_VLR', 'MAP_FORWARD_CHECK_SS_INDICATION_ind', 'MAP_NOTICE_ind', and 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind'. 'Insert Subs Data_VLR', 'Activate Tracing_VLR', and 'MAP_FORWARD_CHECK_SS_INDICATION_ind' all lead to 'Wait_For_HLR_Response'. 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req', which leads to a block 'Subscriber data confirmed by HLR=False; Location information confirmed in HLR=False', which then leads to 'Procedure_Error'. 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' also leads to 'Procedure_Error'.](78b2f2e47d941e9f565e3691a1947d50_img.jpg) + +``` + +graph TD + Start([ ]) --> HLR_Known{HLR address known?} + HLR_Known -- No --> Roaming_Not_Allowed1(( )) + Roaming_Not_Allowed1 --> Roaming_Not_Allowed1_out[Roaming_Not_Allowed] + HLR_Known -- Yes --> MAP_Open_Req["MAP_OPEN_req +MAP_UPDATE_LOCATION_req +MAP_DELIMITER_req"] + MAP_Open_Req --> Receive_Open_Cnf[Receive_Open_Cnf] + Receive_Open_Cnf -- Error --> Procedure_Error1(( )) + Procedure_Error1 --> Procedure_Error1_out[Procedure_Error] + Receive_Open_Cnf -- Vr --> Perform_MAP_Vr[Perform MAP_Vr dialogue] + Perform_MAP_Vr --> Result{Result?} + Result -- "Procedure error, Aborted" --> Procedure_Error2(( )) + Procedure_Error2 --> Procedure_Error2_out[Procedure_Error] + Result -- "Unknown subscriber" --> Unknown_Subscriber(( )) + Unknown_Subscriber --> Unknown_Subscriber_out[Unknown_Subscriber] + Result -- "Roaming not allowed" --> Roaming_Not_Allowed2(( )) + Roaming_Not_Allowed2 --> Roaming_Not_Allowed2_out[Roaming_Not_Allowed] + Result -- "HLR number" --> OK1(( )) + OK1 --> OK1_out[OK] + Receive_Open_Cnf -- OK --> Wait_For_HLR_Response1[Wait_For_HLR_Response] + Unknown_Subscriber --> Wait_For_HLR_Response2[Wait_For_HLR_Response] + HLR_number --> Wait_For_HLR_Response2 + Wait_For_HLR_Response1 --> Insert Subs Data_VLR[Insert Subs Data_VLR] + Insert Subs Data_VLR --> Wait_For_HLR_Response3[Wait_For_HLR_Response] + Wait_For_HLR_Response1 --> Activate Tracing_VLR[Activate Tracing_VLR] + Activate Tracing_VLR --> Wait_For_HLR_Response4[Wait_For_HLR_Response] + Wait_For_HLR_Response1 --> MAP_FORWARD_CHECK_SS_INDICATION_ind[MAP_FORWARD_CHECK_SS_INDICATION_ind] + MAP_FORWARD_CHECK_SS_INDICATION_ind --> Wait_For_HLR_Response5[Wait_For_HLR_Response] + Wait_For_HLR_Response1 --> MAP_NOTICE_ind[MAP_NOTICE_ind] + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> Subscriber_Data_Confirmed["Subscriber data confirmed by HLR=False; +Location information confirmed in HLR=False"] + Subscriber_Data_Confirmed --> Procedure_Error3(( )) + Procedure_Error3 --> Procedure_Error3_out[Procedure_Error] + Wait_For_HLR_Response1 --> MAP_U_ABORT_ind["MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind"] + MAP_U_ABORT_ind --> Procedure_Error3 + +``` + +Flowchart for GPRS\_Update\_HLR\_VLR macro. It starts with a decision 'HLR address known?'. If 'No', it goes to 'Roaming\_Not\_Allowed'. If 'Yes', it sends 'MAP\_OPEN\_req', 'MAP\_UPDATE\_LOCATION\_req', and 'MAP\_DELIMITER\_req', then receives 'Open\_Cnf'. From 'Open\_Cnf', it branches based on 'Error', 'Vr', and 'OK'. 'Error' leads to 'Procedure\_Error'. 'Vr' leads to 'Perform MAP\_Vr dialogue', which then leads to 'Result?'. 'Result?' branches into 'Procedure error, Aborted' (leading to 'Procedure\_Error'), 'Unknown subscriber' (leading to 'Unknown\_Subscriber'), 'Roaming not allowed' (leading to 'Roaming\_Not\_Allowed'), and 'HLR number' (leading to 'OK'). 'OK' from 'Open\_Cnf' leads to 'Wait\_For\_HLR\_Response'. Both 'Unknown\_Subscriber' and 'HLR number' lead to 'Wait\_For\_HLR\_Response'. From 'Wait\_For\_HLR\_Response', it branches into 'Insert Subs Data\_VLR', 'Activate Tracing\_VLR', 'MAP\_FORWARD\_CHECK\_SS\_INDICATION\_ind', 'MAP\_NOTICE\_ind', and 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind'. 'Insert Subs Data\_VLR', 'Activate Tracing\_VLR', and 'MAP\_FORWARD\_CHECK\_SS\_INDICATION\_ind' all lead to 'Wait\_For\_HLR\_Response'. 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req', which leads to a block 'Subscriber data confirmed by HLR=False; Location information confirmed in HLR=False', which then leads to 'Procedure\_Error'. 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' also leads to 'Procedure\_Error'. + +1086 + +1087 + +Figure 19.1.1/10 (sheet 1 of 2): Macro GPRS\_Update\_HLR\_VLR + +macrodefinition GPRS\_Update\_HLR\_VLR + +GUHLR\_VLR2(2) + +Macro in the VLR to handle a location updating dialogue with the HLR when the Gs interface is used + +Signals to/from the right are to/from the HLR + +![Flowchart for GPRS_Update_HLR_VLR macro. It starts with 'Wait_For_HLR_Response', followed by a merge point for 'MAP_UPDATE_LOCATION_cnf'. Then 'Check_Confirmation' leads to 'OK' (success) or 'User Error'. 'User Error' branches into 'Unknown subscriber', 'Roaming not allowed', and 'Else' (which leads to 'Provider Error, Data Error' and 'Procedure_Error').](86f84829fd1c592351b2c1724f03ebbf_img.jpg) + +``` + +graph TD + Start([Wait_For_HLR_Response]) --> Merge(( )) + Merge --> MAP_UPDATE_LOCATION_cnf[MAP_UPDATE_LOCATION_cnf] + MAP_UPDATE_LOCATION_cnf --> Check_Confirmation[Check_Confirmation] + Check_Confirmation --> OK[OK] + Check_Confirmation --> User_Error[User Error] + OK --> OK_Success[Subscriber data confirmed by HLR:=True; Location information confirmed in HLR:=True] + OK_Success --> OK_End((OK)) + User_Error --> Unknown_Subscriber[Unknown subscriber] + User_Error --> Roaming_Not_Allowed[Roaming not allowed] + User_Error --> Else[Else] + Unknown_Subscriber --> Unknown_Subs[Unknown_Subscriber] + Unknown_Subs --> Unknown_End(( )) + Roaming_Not_Allowed --> Roaming_Not_Allowed_Subs[Roaming_Not_Allowed] + Roaming_Not_Allowed_Subs --> Roaming_End(( )) + Else --> Else_Subs[Subscriber data confirmed by HLR:=False; Location information confirmed in HLR:=False] + Else_Subs --> Else_End(( )) + Else_Subs --> Procedure_Error[Procedure_Error] + Else_Subs --> Provider_Error[Provider Error, Data Error] + +``` + +Flowchart for GPRS\_Update\_HLR\_VLR macro. It starts with 'Wait\_For\_HLR\_Response', followed by a merge point for 'MAP\_UPDATE\_LOCATION\_cnf'. Then 'Check\_Confirmation' leads to 'OK' (success) or 'User Error'. 'User Error' branches into 'Unknown subscriber', 'Roaming not allowed', and 'Else' (which leads to 'Provider Error, Data Error' and 'Procedure\_Error'). + +1088 + +1089 + +Figure 19.1.1/10 (sheet 2 of 2): Macro GPRS\_Update\_HLR\_VLR + +![Flowchart for process Send_Identification_PVLR. It starts with an initial state leading to 'Null', then 'Receive_Open_Ind'. From 'Receive_Open_Ind', three paths emerge: 'Vr' leading to 'Perform MAP Vr dialogue' then 'Null'; 'OK' leading to 'Wait_For_Service_Primitive'; and 'Error' leading to 'Null'. 'Wait_For_Service_Primitive' leads to a merge point. From this merge point, four paths emerge: 'MAP_NOTICE_ind' leading to 'Null'; 'MAP_P_ABORT_ind' leading to a merge point; a rightward arrow leading to 'MAP_SEND_IDENTIFICATION_ind'; and 'Send Identification' leading to 'Wait_For_Application_Response'. 'MAP_NOTICE_ind' and 'MAP_P_ABORT_ind' both lead to 'MAP_CLOSE_req', which then leads to 'Null'. 'MAP_SEND_IDENTIFICATION_ind' leads to 'Send Identification'. 'Wait_For_Application_Response' leads to another merge point. From this merge point, four paths emerge: 'MAP_NOTICE_ind' leading to 'Null'; a rightward arrow leading to 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind'; 'Send Identification negative response' leading to 'Set User Error'; and 'Set User Error' leading to a merge point. 'MAP_NOTICE_ind' and the rightward arrow both lead to 'MAP_CLOSE_req', which then leads to 'Abort' and finally 'Null'. The merge point from 'Set User Error' leads to 'MAP_SEND_IDENTIFICATION_rsp, MAP_CLOSE_req', which then leads to 'Null'.](5547a75375f032b096428428783e9718_img.jpg) + +**process Send\_Identification\_PVLR** **SI\_PVLR1(2)** + +Process in the PVLR to handle a request for IMSI and authentication information from the new VLR + +Signals to/from the left are to/from the new VLR, signals to/from the right are to/from the location management application process in the PVLR (see 3GPP TS 23.012) + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive[Receive_Open_Ind] + Receive -- Vr --> Perform[Perform MAP Vr dialogue] + Perform --> Null2([Null]) + Receive -- OK --> Wait1[Wait_For_Service_Primitive] + Receive -- Error --> Null3([Null]) + Wait1 --> Merge1(( )) + Merge1 -- "MAP_NOTICE_ind" --> Null4([Null]) + Merge1 -- "MAP_P_ABORT_ind" --> Merge2(( )) + Merge1 --> Right1[ ] + Right1 -- "MAP_SEND_IDENTIFICATION_ind" --> Right1 + Merge1 -- "Send Identification" --> Wait2[Wait_For_Application_Response] + Merge2 -- "MAP_CLOSE_req" --> Null5([Null]) + Wait2 --> Merge3(( )) + Merge3 -- "MAP_NOTICE_ind" --> Null6([Null]) + Merge3 --> Right2[ ] + Merge3 -- "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" --> Right2 + Merge3 -- "Send Identification negative response" --> SetError[Set User Error] + SetError --> Merge4(( )) + Merge4 -- "MAP_SEND_IDENTIFICATION_rsp, MAP_CLOSE_req" --> Merge4 + Merge4 --> Null7([Null]) + Right2 --> Merge5(( )) + Merge5 -- "MAP_CLOSE_req" --> Abort[Abort] + Abort --> Null8([Null]) + +``` + +Flowchart for process Send\_Identification\_PVLR. It starts with an initial state leading to 'Null', then 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', three paths emerge: 'Vr' leading to 'Perform MAP Vr dialogue' then 'Null'; 'OK' leading to 'Wait\_For\_Service\_Primitive'; and 'Error' leading to 'Null'. 'Wait\_For\_Service\_Primitive' leads to a merge point. From this merge point, four paths emerge: 'MAP\_NOTICE\_ind' leading to 'Null'; 'MAP\_P\_ABORT\_ind' leading to a merge point; a rightward arrow leading to 'MAP\_SEND\_IDENTIFICATION\_ind'; and 'Send Identification' leading to 'Wait\_For\_Application\_Response'. 'MAP\_NOTICE\_ind' and 'MAP\_P\_ABORT\_ind' both lead to 'MAP\_CLOSE\_req', which then leads to 'Null'. 'MAP\_SEND\_IDENTIFICATION\_ind' leads to 'Send Identification'. 'Wait\_For\_Application\_Response' leads to another merge point. From this merge point, four paths emerge: 'MAP\_NOTICE\_ind' leading to 'Null'; a rightward arrow leading to 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind'; 'Send Identification negative response' leading to 'Set User Error'; and 'Set User Error' leading to a merge point. 'MAP\_NOTICE\_ind' and the rightward arrow both lead to 'MAP\_CLOSE\_req', which then leads to 'Abort' and finally 'Null'. The merge point from 'Set User Error' leads to 'MAP\_SEND\_IDENTIFICATION\_rsp, MAP\_CLOSE\_req', which then leads to 'Null'. + +1090 + +1091 + +**Figure 19.1.1/11 (sheet 1 of 2): Process Send\_Identification\_PVLR** + +![Flowchart for process Send_Identification_PVLR. It starts with 'Wait_For_Application_Response', followed by 'Send Identification ack' leading to connector '1'. Then 'MAP_SEND_IDENTIFICATION_rsp' is received. A decision 'More authentication sets to send?' follows. If 'No', it goes to 'MAP_CLOSE_req' then 'Null'. If 'Yes', it goes to another decision 'Segmentation allowed?'. If 'No', it goes to 'MAP_CLOSE_req'. If 'Yes', it goes to 'MAP_DELIMITER_req' then 'Wait_For_Next_Request'. From 'Wait_For_Next_Request', three paths emerge: 'MAP_SEND_IDENTIFICATION_ind' leading to connector '1', 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req', and a group of 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind' leading to 'Abort'. Both 'MAP_CLOSE_req' and 'Abort' lead to 'Null'.](707ce14d1a5d5c7d61bf59aa85401fa9_img.jpg) + +**process Send\_Identification\_PVLR** **SI\_PVLR2(2)** + +Process in the PVLR to handle a request for IMSI and authentication information from the new VLR + +Signals to/from the left are to/from the new VLR, signals to/from the right are to/from the location management application process in the PVLR (see 3GPP TS 23.012) + +``` + + graph TD + Start([Wait_For_Application_Response]) --> SendAck{{Send Identification ack}} + SendAck --> C1((1)) + C1 --> Rsp{{MAP_SEND_IDENTIFICATION_rsp}} + Rsp --> D1{More authentication sets to send?} + D1 -- No --> CloseReq1{{MAP_CLOSE_req}} + D1 -- Yes --> D2{Segmentation allowed?} + D2 -- No --> CloseReq1 + D2 -- Yes --> DelimiterReq{{MAP_DELIMITER_req}} + DelimiterReq --> WaitNext([Wait_For_Next_Request]) + WaitNext --> Ind1{{MAP_SEND_IDENTIFICATION_ind}} + Ind1 --> C2((1)) + WaitNext --> Ind2{{MAP_NOTICE_ind}} + Ind2 --> CloseReq2{{MAP_CLOSE_req}} + WaitNext --> Ind3{{MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind}} + CloseReq1 --> Null1([Null]) + CloseReq2 --> Abort{{Abort}} + Ind3 --> Abort + Abort --> Null2([Null]) + +``` + +Flowchart for process Send\_Identification\_PVLR. It starts with 'Wait\_For\_Application\_Response', followed by 'Send Identification ack' leading to connector '1'. Then 'MAP\_SEND\_IDENTIFICATION\_rsp' is received. A decision 'More authentication sets to send?' follows. If 'No', it goes to 'MAP\_CLOSE\_req' then 'Null'. If 'Yes', it goes to another decision 'Segmentation allowed?'. If 'No', it goes to 'MAP\_CLOSE\_req'. If 'Yes', it goes to 'MAP\_DELIMITER\_req' then 'Wait\_For\_Next\_Request'. From 'Wait\_For\_Next\_Request', three paths emerge: 'MAP\_SEND\_IDENTIFICATION\_ind' leading to connector '1', 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req', and a group of 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind' leading to 'Abort'. Both 'MAP\_CLOSE\_req' and 'Abort' lead to 'Null'. + +1092 + +1093 + +**Figure 19.1.1/11 (sheet 2 of 2): Process Send\_Identification\_PVLR** + +![Flowchart for process Update_GPRS_Location_SGSN. It starts with 'Null', followed by 'Update Location'. A decision 'HLR address known?' follows. If 'No', it goes to 'Set negative response: Unknown HLR' and then 'Null'. If 'Yes', it sends 'MAP_OPEN_req', 'MAP_UPDATE_GPRS_LOCATION_req', and 'MAP_DELIMITER_req'. Then it receives 'Open_Cnf'. If 'OK', it goes to 'Wait_For_HLR_Response'. If 'Vr, Error', it goes to 'Set negative response: Procedure error'. From 'Wait_For_HLR_Response', it branches into 'Update Location negative response', 'Abort', 'Insert Subs_Data_SGSN', 'Activate Tracing_SGSN', 'MAP_NOTICE_ind', and a block with 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind'. 'Update Location negative response' leads to 'Null'. 'Abort' leads to 'MAP_U_ABORT_req' and then 'Null'. 'Insert Subs_Data_SGSN' and 'Activate Tracing_SGSN' both lead to 'Wait_For_HLR_Response'. 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req'. The block with 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind' also leads to 'MAP_CLOSE_req'. 'MAP_CLOSE_req' leads to 'Set negative response: Procedure error', which leads to 'Update Location negative response' and then 'Null'.](96b47d5db5f5f313cc8c40db35ebcdf3_img.jpg) + +**process Update\_GPRS\_Location\_SGSN** **UGL\_SGSN1(2)** + +Process in the SGSN to handle a location updating dialogue with the HLR + +Signals to/from the left are to/from the GPRS mobility management application process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/from the HLR + +``` + + graph TD + Start([Null]) --> UpdateLoc{Update Location} + UpdateLoc --> HLRKnown{HLR address known?} + HLRKnown -- No --> NegResp1[Set negative response: Unknown HLR] + NegResp1 --> UpdateLocNeg[Update Location negative response] + UpdateLocNeg --> Null1([Null]) + + HLRKnown -- Yes --> MAPReq["MAP_OPEN_req +MAP_UPDATE_GPRS_LOCATION_req +MAP_DELIMITER_req"] + MAPReq --> OpenCnf[Receive Open_Cnf] + + OpenCnf -- "Vr, Error" --> NegResp2[Set negative response: Procedure error] + + OpenCnf -- OK --> WaitHLR[Wait_For_HLR_Response] + + WaitHLR --> UpdateLocNeg2[Update Location negative response] + UpdateLocNeg2 --> Null2([Null]) + + WaitHLR --> Abort[Abort] + Abort --> MAPUAbort[MAP_U_ABORT_req] + MAPUAbort --> Null3([Null]) + + WaitHLR --> InsertSubs[Insert Subs_Data_SGSN] + InsertSubs --> WaitHLR2[Wait_For_HLR_Response] + + WaitHLR --> ActivateTracing[Activate Tracing_SGSN] + ActivateTracing --> WaitHLR3[Wait_For_HLR_Response] + + WaitHLR --> MAPNotice[MAP_NOTICE_ind] + + WaitHLR --> MAPCloseReq[MAP_CLOSE_req] + + MAPNotice --> MAPCloseReq + + MAPCloseReq --> NegResp3[Set negative response: Procedure error] + + MAPCloseReq --> MAPUAbortInd["MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind"] + + MAPUAbortInd --> MAPCloseReq + + NegResp3 --> UpdateLocNeg3[Update Location negative response] + UpdateLocNeg3 --> Null4([Null]) + +``` + +Flowchart for process Update\_GPRS\_Location\_SGSN. It starts with 'Null', followed by 'Update Location'. A decision 'HLR address known?' follows. If 'No', it goes to 'Set negative response: Unknown HLR' and then 'Null'. If 'Yes', it sends 'MAP\_OPEN\_req', 'MAP\_UPDATE\_GPRS\_LOCATION\_req', and 'MAP\_DELIMITER\_req'. Then it receives 'Open\_Cnf'. If 'OK', it goes to 'Wait\_For\_HLR\_Response'. If 'Vr, Error', it goes to 'Set negative response: Procedure error'. From 'Wait\_For\_HLR\_Response', it branches into 'Update Location negative response', 'Abort', 'Insert Subs\_Data\_SGSN', 'Activate Tracing\_SGSN', 'MAP\_NOTICE\_ind', and a block with 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind'. 'Update Location negative response' leads to 'Null'. 'Abort' leads to 'MAP\_U\_ABORT\_req' and then 'Null'. 'Insert Subs\_Data\_SGSN' and 'Activate Tracing\_SGSN' both lead to 'Wait\_For\_HLR\_Response'. 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req'. The block with 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind' also leads to 'MAP\_CLOSE\_req'. 'MAP\_CLOSE\_req' leads to 'Set negative response: Procedure error', which leads to 'Update Location negative response' and then 'Null'. + +1094 + +1095 + +**Figure 19.1.1/12 (sheet 1 of 2): Process Update\_GPRS\_Location\_SGSN** + +![UML Sequence diagram for Update_GPRS_Location_SGSN process. The process starts with 'Wait_For_HLR_Response', followed by a merge symbol receiving 'MAP_UPDATE_GPRS_LOCATION_cnf'. It then enters 'Check_Confirmation', which branches into three paths: 'User Error' (leading to 'Check_User_Error_In_Serving_Network_Entity', 'Set negative response', 'Update Location negative response', and 'Null'), 'OK' (leading to 'Set result', 'Update Location ack', and 'Null'), and 'Provider Error, Data Error' (leading to 'Set negative response: Procedure error', 'Update Location negative response', and 'Null'). A note 'See 3GPP TS 23.116' is associated with the User Error path.](2b10056b07ec6fecdc2d1b4c2000a2f6_img.jpg) + +**process Update\_GPRS\_Location\_SGSN** **UGL\_SGSN2(2)** + +Process in the SGSN to handle a location updating dialogue with the HLR + +Signals to/from the left are to/from the GPRS mobility management application process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/from the HLR + +``` + +sequenceDiagram + participant HLR + participant SGSN + Note left of SGSN: Process in the SGSN to handle a location updating dialogue with the HLR + Note right of SGSN: Signals to/from the left are to/from the GPRS mobility management application process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/from the HLR + + SGSN->>HLR: Wait_For_HLR_Response + Note right of SGSN: See 3GPP TS 23.116 + HLR-->>SGSN: MAP_UPDATE_GPRS_LOCATION_cnf + Note right of SGSN: Check_Confirmation + Note right of SGSN: User Error + Note right of SGSN: OK + Note right of SGSN: Provider Error, Data Error + + Note right of SGSN: Check_User_Error_In_Serving_Network_Entity + Note right of SGSN: Set negative response + Note right of SGSN: Update Location negative response + Note right of SGSN: Null + + Note right of SGSN: Set result + Note right of SGSN: Update Location ack + Note right of SGSN: Null + + Note right of SGSN: Set negative response: Procedure error + Note right of SGSN: Update Location negative response + Note right of SGSN: Null + +``` + +UML Sequence diagram for Update\_GPRS\_Location\_SGSN process. The process starts with 'Wait\_For\_HLR\_Response', followed by a merge symbol receiving 'MAP\_UPDATE\_GPRS\_LOCATION\_cnf'. It then enters 'Check\_Confirmation', which branches into three paths: 'User Error' (leading to 'Check\_User\_Error\_In\_Serving\_Network\_Entity', 'Set negative response', 'Update Location negative response', and 'Null'), 'OK' (leading to 'Set result', 'Update Location ack', and 'Null'), and 'Provider Error, Data Error' (leading to 'Set negative response: Procedure error', 'Update Location negative response', and 'Null'). A note 'See 3GPP TS 23.116' is associated with the User Error path. + +1096 + +1097 + +**Figure 19.1.1/12 (sheet 2 of 2): Process Update\_GPRS\_Location\_SGSN** + +![Flowchart for process Update_Location_HLR. It starts with an oval, followed by 'Null', then a merge symbol with 'MAP_UPDATE_LOCATION_ind' input. Then 'Update Location', 'Wait_For_Application_Response'. A split leads to four paths: 1) 'Update Location ack' -> 'Set Result' -> merge symbol with 'MAP_UPDATE_LOCATION_rsp' and 'MAP_CLOSE_req' output. 2) 'Update Location negative response' -> 'Set User Error' -> merge symbol. 3) 'Activate Trace Mode' -> merge symbol with 'MAP_ACTIVATE_TRACE_MODE_req' and 'MAP_DELIMITER_req' input -> 'Wait_For_ATM_Cnf'. 4) 'Insert Subscriber Data' -> merge symbol with 'MAP_INSERT_SUBSCRIBER_DATA_req' and 'MAP_DELIMITER_req' input -> 'Wait_For_ISD_Cnf_Or_Application_Response'. All four paths converge to a final merge symbol with an 'X' below it.](2dd0ba902cf30ea954edf716f87194da_img.jpg) + +**process Update\_Location\_HLR** **UL\_HLR1(3)** + +Process in the HLR to handle an Update Location request from a VLR + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the location management application process in the HLR (see 3GPP TS 23.012) + +``` + + graph TD + Start([ ]) --> Null([Null]) + Null --> Merge1{ } + MAP_UPDATE_LOCATION_ind[MAP_UPDATE_LOCATION_ind] --> Merge1 + Merge1 --> UpdateLocation[Update Location] + UpdateLocation --> WaitApp[Wait_For_Application_Response] + WaitApp --> Split1[ ] + + Split1 --> UpdateAck[Update Location ack] + UpdateAck --> SetResult[Set Result] + + Split1 --> UpdateNeg[Update Location negative response] + UpdateNeg --> SetUserError[Set User Error] + + Split1 --> ActivateTrace[Activate Trace Mode] + ActivateTrace --> Merge2{ } + MAP_ACTIVATE_TRACE_MODE_req[MAP_ACTIVATE_TRACE_MODE_req] --> Merge2 + MAP_DELIMITER_req1[MAP_DELIMITER_req] --> Merge2 + Merge2 --> WaitATM[Wait_For_ATM_Cnf] + + Split1 --> InsertData[Insert Subscriber Data] + InsertData --> Merge3{ } + MAP_INSERT_SUBSCRIBER_DATA_req[MAP_INSERT_SUBSCRIBER_DATA_req] --> Merge3 + MAP_DELIMITER_req2[MAP_DELIMITER_req] --> Merge3 + Merge3 --> WaitISD[Wait_For_ISD_Cnf_Or_Application_Response] + + SetResult --> Merge4{ } + SetUserError --> Merge4 + WaitATM --> Merge4 + WaitISD --> Merge4 + + Merge4 --> Merge5{ } + MAP_UPDATE_LOCATION_rsp[MAP_UPDATE_LOCATION_rsp] --> Merge5 + MAP_CLOSE_req[MAP_CLOSE_req] --> Merge5 + + Merge5 --> End((X)) + +``` + +Flowchart for process Update\_Location\_HLR. It starts with an oval, followed by 'Null', then a merge symbol with 'MAP\_UPDATE\_LOCATION\_ind' input. Then 'Update Location', 'Wait\_For\_Application\_Response'. A split leads to four paths: 1) 'Update Location ack' -> 'Set Result' -> merge symbol with 'MAP\_UPDATE\_LOCATION\_rsp' and 'MAP\_CLOSE\_req' output. 2) 'Update Location negative response' -> 'Set User Error' -> merge symbol. 3) 'Activate Trace Mode' -> merge symbol with 'MAP\_ACTIVATE\_TRACE\_MODE\_req' and 'MAP\_DELIMITER\_req' input -> 'Wait\_For\_ATM\_Cnf'. 4) 'Insert Subscriber Data' -> merge symbol with 'MAP\_INSERT\_SUBSCRIBER\_DATA\_req' and 'MAP\_DELIMITER\_req' input -> 'Wait\_For\_ISD\_Cnf\_Or\_Application\_Response'. All four paths converge to a final merge symbol with an 'X' below it. + +1098 + +1099 + +**Figure 19.1.1/13 (sheet 1 of 3): Process Update\_Location\_HLR** + +![State transition diagram for Update_Location_HLR process. It shows two main state machines. The top one starts in 'Wait_For_ATM_Cnf' and handles MAP_CLOSE_req, leading to Check_Confirmation and various responses (Set negative response: System failure, Activate Trace Mode negative response, Activate Trace Mode ack). The bottom one starts in 'Wait_For_ISD_Cnf_Or_Application_Response' and handles MAP_NOTICE_ind, leading to Set negative response: System failure, Insert Subscriber Data negative response, and MAP_INSERT_SUBSCRIBER_DATA_req. Both include Abort and error handling paths.](86fa12b2972ca1c2a9695ec59ca4226c_img.jpg) + +**process Update\_Location\_HLR** **UL\_HLR2(3)** + +Process in the HLR to handle an Update Location request from a VLR + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the location management application process in the HLR (see 3GPP TS 23.012) + +``` + +stateDiagram-v2 + [*] --> Wait_For_ATM_Cnf + state "Wait_For_ATM_Cnf" as Wait_For_ATM_Cnf + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" as MAP_U_ABORT_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_ACTIVATE_TRACE_MODE_cnf" as MAP_ACTIVATE_TRACE_MODE_cnf + state "Abort" as Abort + state "X" as X + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "Check_Confirmation" as Check_Confirmation + state "Set negative response: System failure" as Set_Neg_Resp_Sys_Fail_1 + state "Set negative response: System failure" as Set_Neg_Resp_Sys_Fail_2 + state "Set negative response" as Set_Neg_Resp + state "Activate Trace Mode negative response" as Act_Trace_Neg_Resp_1 + state "Activate Trace Mode negative response" as Act_Trace_Neg_Resp_2 + state "Activate Trace Mode ack" as Act_Trace_Ack + state "X" as X + state "Wait_For_Application_Response" as Wait_For_App_Resp + + Wait_For_ATM_Cnf --> MAP_U_ABORT_ind + Wait_For_ATM_Cnf --> MAP_NOTICE_ind + Wait_For_ATM_Cnf --> MAP_ACTIVATE_TRACE_MODE_cnf + MAP_U_ABORT_ind --> Abort + Abort --> X + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Check_Confirmation + Check_Confirmation --> Set_Neg_Resp_Sys_Fail_1 : Provider Error + Check_Confirmation --> Set_Neg_Resp_Sys_Fail_2 : Data Error + Check_Confirmation --> Set_Neg_Resp : User Error + Check_Confirmation --> Act_Trace_Ack : OK + Set_Neg_Resp_Sys_Fail_1 --> Act_Trace_Neg_Resp_1 + Act_Trace_Neg_Resp_1 --> X + Set_Neg_Resp_Sys_Fail_2 --> Act_Trace_Neg_Resp_2 + Set_Neg_Resp --> Act_Trace_Neg_Resp_2 + Act_Trace_Neg_Resp_2 --> Wait_For_Application_Response + Wait_For_Application_Response --> Act_Trace_Ack + + [*] --> Wait_For_ISD_Cnf_Or_Application_Response + state "Wait_For_ISD_Cnf_Or_Application_Response" as Wait_For_ISD_Cnf_Or_Application_Response + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" as MAP_U_ABORT_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "Insert Subscriber Data" as Insert_Subscriber_Data + state "Abort" as Abort + state "X" as X + state "Set negative response: System failure" as Set_Neg_Resp_Sys_Fail_3 + state "Insert Subscriber Data negative response" as Insert_Sub_Dat_Neg_Resp + state "MAP_INSERT_SUBSCRIBER_DATA_req, MAP_DELIMITER_req" as MAP_INSERT_SUBSCRIBER_DATA_req + state "Wait_For_ISD_Cnf_Or_Application_Response" as Wait_For_ISD_Cnf_Or_Application_Response + + Wait_For_ISD_Cnf_Or_Application_Response --> MAP_U_ABORT_ind + Wait_For_ISD_Cnf_Or_Application_Response --> MAP_NOTICE_ind + Wait_For_ISD_Cnf_Or_Application_Response --> Insert_Subscriber_Data + MAP_U_ABORT_ind --> Abort + Abort --> X + MAP_NOTICE_ind --> Set_Neg_Resp_Sys_Fail_3 + Set_Neg_Resp_Sys_Fail_3 --> Insert_Sub_Dat_Neg_Resp + Insert_Sub_Dat_Neg_Resp --> MAP_INSERT_SUBSCRIBER_DATA_req + MAP_INSERT_SUBSCRIBER_DATA_req --> Insert_Subscriber_Data + Insert_Subscriber_Data --> Wait_For_ISD_Cnf_Or_Application_Response + +``` + +State transition diagram for Update\_Location\_HLR process. It shows two main state machines. The top one starts in 'Wait\_For\_ATM\_Cnf' and handles MAP\_CLOSE\_req, leading to Check\_Confirmation and various responses (Set negative response: System failure, Activate Trace Mode negative response, Activate Trace Mode ack). The bottom one starts in 'Wait\_For\_ISD\_Cnf\_Or\_Application\_Response' and handles MAP\_NOTICE\_ind, leading to Set negative response: System failure, Insert Subscriber Data negative response, and MAP\_INSERT\_SUBSCRIBER\_DATA\_req. Both include Abort and error handling paths. + +1100 + +1101 + +**Figure 19.1.1/13 (sheet 2 of 3): Process Update\_Location\_HLR** + +![Sequence diagram for process Update_Location_HLR. The diagram shows the interaction between an external entity (left) and internal HLR processes (right). It starts with a 'Wait_For_ISD_Cnf_Or_Application_Response' state. The left side includes 'Update Location ack', 'Update Location negative response', 'Set Result', 'Set User Error', and 'MAP_UPDATE_LOCATION_rsp MAP_CLOSE_req'. The right side includes 'MAP_INSERT_SUBSCRIBER_DATA_cnf', 'Check_Confirmation', and four error paths: 'OK', 'User Error', 'Data Error', and 'Provider Error', each leading to specific response actions and a return to the initial wait state.](3206908d095735fe036950cff84908e8_img.jpg) + +**process Update\_Location\_HLR** **UL\_HLR3(3)** + +Process in the HLR to handle an Update Location request from a VLR + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the location management application process in the HLR (see 3GPP TS 23.012) + +``` + +sequenceDiagram + participant External + participant HLR_Internal + Note right of HLR_Internal: Wait_For_ISD_Cnf_Or_Application_Response + Note left of External: Update Location ack + Note left of External: Update Location negative response + Note left of External: Set Result + Note left of External: Set User Error + Note left of External: MAP_UPDATE_LOCATION_rsp +MAP_CLOSE_req + Note right of HLR_Internal: MAP_INSERT_SUBSCRIBER_DATA_cnf + Note right of HLR_Internal: Check_Confirmation + Note right of HLR_Internal: OK + Note right of HLR_Internal: User Error + Note right of HLR_Internal: Data Error + Note right of HLR_Internal: Provider Error + Note right of HLR_Internal: Insert Subscriber Data ack + Note right of HLR_Internal: Insert Subscriber Data negative response + Note right of HLR_Internal: Wait_For_ISD_Cnf_Or_Application_Response + +``` + +Sequence diagram for process Update\_Location\_HLR. The diagram shows the interaction between an external entity (left) and internal HLR processes (right). It starts with a 'Wait\_For\_ISD\_Cnf\_Or\_Application\_Response' state. The left side includes 'Update Location ack', 'Update Location negative response', 'Set Result', 'Set User Error', and 'MAP\_UPDATE\_LOCATION\_rsp MAP\_CLOSE\_req'. The right side includes 'MAP\_INSERT\_SUBSCRIBER\_DATA\_cnf', 'Check\_Confirmation', and four error paths: 'OK', 'User Error', 'Data Error', and 'Provider Error', each leading to specific response actions and a return to the initial wait state. + +1102 + +1103 + +**Figure 19.1.1/13 (sheet 3 of 3): Process Update\_Location\_HLR** + +![Flowchart for process Update_GPRS_Location_HLR. It starts with an initial state, followed by 'Null', 'Receive_Open_ind', and 'Wait_For_Service_Primitive'. From 'Wait_For_Service_Primitive', an 'OK' path leads to 'MAP_UPDATE_GPRS_LOCATION_ind' and 'Check_Indication', while a 'Vr, Error' path leads to 'Null'. 'Check_Indication' leads to 'Subscriber known?'. If 'No', it goes to 'Set diagnostic: IMSI unknown' and then 'Set User Error: Unknown subscriber'. If 'Yes', it goes to 'Network Access Mode?'. If 'Non-GPRS only', it goes to 'Set diagnostic: GPRS subscription unknown'. Both diagnostic paths lead to 'Set User Error: Unknown subscriber'. From 'Set User Error: Unknown subscriber', it goes to a response block 'MAP_UPDATE_GPRS_LOCATION_rsp' and 'MAP_CLOSE_req', then to 'Null'. If 'Subscriber known?' is 'Yes' and 'Network Access Mode?' is 'Else', it goes to 'Subscriber tracing active in SGSN:= False' and then to connector '1'. If 'Subscriber known?' is 'Yes' and 'Network Access Mode?' is 'Error', it goes to a response block 'MAP_UPDATE_GPRS_LOCATION_rsp' and 'MAP_CLOSE_req', then to 'Null'. There are also 'MAP_P_ABORT_ind' and 'MAP_NOTICE_ind' paths from 'Wait_For_Service_Primitive' leading to 'Null' and 'MAP_CLOSE_req' respectively.](cdf6308d33c8eb877deede2d942cc349_img.jpg) + +**process Update\_GPRS\_Location\_HLR** **UGL\_HLR1(2)** + +Process in the HLR to handle an Update GPRS Location request from an SGSN + +Signals to/from the left are to/from the SGSN; signals to/from the right are to/from the GPRS mobility management application process in the HLR (see 3GPP TS 23.060) + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive[Receive_Open_ind] + Receive --> Wait[Wait_For_Service_Primitive] + Wait -- OK --> Ind1[MAP_UPDATE_GPRS_LOCATION_ind] + Ind1 --> Check[Check_Indication] + Check --> SubKnown{Subscriber known?} + SubKnown -- No --> Diag1[Set diagnostic: IMSI unknown] + SubKnown -- Yes --> NetMode{Network Access Mode?} + NetMode -- Non-GPRS only --> Diag2[Set diagnostic: GPRS subscription unknown] + NetMode -- Else --> Trace[Subscriber tracing active in SGSN:= False] + Trace --> Connector1((1)) + Diag1 --> UserError[Set User Error: Unknown subscriber] + Diag2 --> UserError + UserError --> Rsp1[MAP_UPDATE_GPRS_LOCATION_rsp +MAP_CLOSE_req] + Rsp1 --> Null2([Null]) + SubKnown -- Yes --> Error[Error] + Error --> Rsp2[MAP_UPDATE_GPRS_LOCATION_rsp +MAP_CLOSE_req] + Rsp2 --> Null3([Null]) + Wait -- Vr, Error --> Null4([Null]) + Wait --> Abort[MAP_P_ABORT_ind] + Abort --> Null5([Null]) + Wait --> Notice[MAP_NOTICE_ind] + Notice --> Close[MAP_CLOSE_req] + Close --> Null6([Null]) + +``` + +Flowchart for process Update\_GPRS\_Location\_HLR. It starts with an initial state, followed by 'Null', 'Receive\_Open\_ind', and 'Wait\_For\_Service\_Primitive'. From 'Wait\_For\_Service\_Primitive', an 'OK' path leads to 'MAP\_UPDATE\_GPRS\_LOCATION\_ind' and 'Check\_Indication', while a 'Vr, Error' path leads to 'Null'. 'Check\_Indication' leads to 'Subscriber known?'. If 'No', it goes to 'Set diagnostic: IMSI unknown' and then 'Set User Error: Unknown subscriber'. If 'Yes', it goes to 'Network Access Mode?'. If 'Non-GPRS only', it goes to 'Set diagnostic: GPRS subscription unknown'. Both diagnostic paths lead to 'Set User Error: Unknown subscriber'. From 'Set User Error: Unknown subscriber', it goes to a response block 'MAP\_UPDATE\_GPRS\_LOCATION\_rsp' and 'MAP\_CLOSE\_req', then to 'Null'. If 'Subscriber known?' is 'Yes' and 'Network Access Mode?' is 'Else', it goes to 'Subscriber tracing active in SGSN:= False' and then to connector '1'. If 'Subscriber known?' is 'Yes' and 'Network Access Mode?' is 'Error', it goes to a response block 'MAP\_UPDATE\_GPRS\_LOCATION\_rsp' and 'MAP\_CLOSE\_req', then to 'Null'. There are also 'MAP\_P\_ABORT\_ind' and 'MAP\_NOTICE\_ind' paths from 'Wait\_For\_Service\_Primitive' leading to 'Null' and 'MAP\_CLOSE\_req' respectively. + +1104 + +1105 + +**Figure 19.1.1/14 (sheet 1 of 2): Process Update\_GPRS\_Location\_HLR** + +process Update\_GPRS\_Location\_HLR + +UGL\_HLR2(2) + +Process in the HLR to handle an Update GPRS Location request from an SGSN + +![Flowchart for process Update_GPRS_Location_HLR. It starts at node 1 and branches based on 'New SGSN?' and 'Roaming allowed in this PLMN?' decisions. It includes steps for charging, routing info updates, and subscriber data insertion, leading to a response message or null/error states.](6027f9f24ff9e9ac90508994e1f84733_img.jpg) + +``` + +graph TD + Start((1)) --> NewSGSN{New SGSN?} + NewSGSN -- No --> Merge1(( )) + NewSGSN -- Yes --> SuperCharged[Super_Charged_Cancel_Location_HLR] + SuperCharged -.-> Note1[See 3GPP TS 23.116] + SuperCharged --> ResultPass1{Result=Pass?} + ResultPass1 -- Yes --> Merge1 + ResultPass1 -- No --> CancelGPRS[Cancel_GPRS_Location_Child_HLR] + CancelGPRS --> Merge1 + Merge1 --> RoamingAllowed{Roaming allowed in this PLMN?} + RoamingAllowed -- No --> DeleteRouting[Delete Routeing Info] + DeleteRouting --> SetUserError1[Set User Error: Roaming not allowed] + SetUserError1 --> Null1([Null]) + SetUserError1 --> MAP_UPDATE[MAP_UPDATE_GPRS_LOCATION_rsp +MAP_CLOSE_req] + RoamingAllowed -- Yes --> UpdateRouting[Update Routeing Info; +MS Purged for GPRS:=False] + UpdateRouting --> ControlTracing[Control_Tracing_With_SGSN_HLR] + ControlTracing -- OK --> SuperCharged2[Super_Charged_Location_Updating_HLR] + SuperCharged2 -.-> Note2[See 3GPP TS 23.116] + ControlTracing -- Error --> Null2([Null]) + SuperCharged2 --> ResultPass2{Result=Pass?} + ResultPass2 -- Yes --> Merge2(( )) + ResultPass2 -- No --> InsertGPRS[Insert_GPRS_Subs_Data_Framed_HLR] + InsertGPRS -- OK --> SubscriberPresent[Subscriber_Present_HLR] + InsertGPRS -- Error --> SetUserError2[Set User Error: System failure] + InsertGPRS -- Aborted --> Null3([Null]) + SubscriberPresent --> Merge2 + Merge2 --> MAP_UPDATE2[MAP_UPDATE_GPRS_LOCATION_rsp +MAP_CLOSE_req] + MAP_UPDATE2 --> Null4([Null]) + +``` + +Flowchart for process Update\_GPRS\_Location\_HLR. It starts at node 1 and branches based on 'New SGSN?' and 'Roaming allowed in this PLMN?' decisions. It includes steps for charging, routing info updates, and subscriber data insertion, leading to a response message or null/error states. + +1106 + +1107 + +Figure 19.1.1/14 (sheet 2 of 2): Process Update\_GPRS\_Location\_HLR + +process Subscriber\_Present\_HLR + +SP\_HLR1(1) + +Process in the HLR to alert SMS service centres if required as part of the location updating process for a GPRS or non-GPRS subscriber + +![Flowchart for process Subscriber_Present_HLR. It starts with an oval, followed by a decision diamond 'Message waiting data set?'. The 'No' path bypasses the 'Alert_Service_Centre_HLR' process block. The 'Yes' path goes through the process block. Both paths lead to a merge point marked with an 'X'.](2e7ad223353e4888238650784ee941ef_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{Message waiting data set?}; Decision -- No --> Merge((X)); Decision -- Yes --> Process[Alert_Service_Centre_HLR]; Process --> Merge; +``` + +Flowchart for process Subscriber\_Present\_HLR. It starts with an oval, followed by a decision diamond 'Message waiting data set?'. The 'No' path bypasses the 'Alert\_Service\_Centre\_HLR' process block. The 'Yes' path goes through the process block. Both paths lead to a merge point marked with an 'X'. + +1108 + +1109 + +Figure 19.1.1/15: Process Subscriber\_Present\_HLR + +1110 **19.1.1A Location updating for VCSG** + +1111 **19.1.1A.1 General** + +1112 The message flow for successful VCSG location updating between VLR and CSS or between SGSN and CSS is shown +1113 in figure 19.1.1A/1. + +![Sequence diagram showing message flow between VLR/SGSN and CSS. The diagram consists of two vertical lifelines: VLR/SGSN on the left and CSS on the right. Four numbered messages are shown: 1) A message from CSS to VLR/SGSN; 2) A message from VLR/SGSN to CSS; 3) A message from CSS to VLR/SGSN; 4) A message from VLR/SGSN to CSS.](961f2a48693ab0934b554468ea75aa60_img.jpg) + +``` + +sequenceDiagram + participant CSS + participant VLR_SGSN as VLR/SGSN + Note right of CSS: 1 + CSS->>VLR_SGSN: + Note left of VLR_SGSN: 2 + VLR_SGSN->>CSS: + Note right of CSS: 3 + CSS->>VLR_SGSN: + Note left of VLR_SGSN: 4 + VLR_SGSN->>CSS: + +``` + +Sequence diagram showing message flow between VLR/SGSN and CSS. The diagram consists of two vertical lifelines: VLR/SGSN on the left and CSS on the right. Four numbered messages are shown: 1) A message from CSS to VLR/SGSN; 2) A message from VLR/SGSN to CSS; 3) A message from CSS to VLR/SGSN; 4) A message from VLR/SGSN to CSS. + +1114 + +- 1115 1) MAP\_UPDATE\_VCSG\_LOCATION\_req/ind +- 1116 2) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind +- 1117 3) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf +- 1118 4) MAP\_UPDATE\_VCSG\_LOCATION\_rsp/cnf + +1119 + +1120 + +**Figure 19.1.1A/1: Message flow for VCSG location updating** + +1121 **19.1.1A.2 Procedures in the VLR** + +1122 The MAP process in the VLR for VCSG location updating for a roaming subscriber is shown in figure 19.1.1A/2. + +1123 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +- 1124 Receive\_Open\_Cnf see clause 25.1.2; +- 1125 Check\_Confirmation see clause 25.2.2; +- 1126 Insert\_Subs\_Data\_VLR see clause 25.7.2. + +1127 **19.1.1A.3 Procedures in the SGSN** + +1128 The MAP process in the SGSN for VCSG location updating for a roaming subscriber is shown in figure 19.1.1A/3. + +1129 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +- 1130 Receive\_Open\_Cnf see clause 25.1.2; +- 1131 Check\_Confirmation see clause 25.2.2; +- 1132 Insert\_Subs\_Data\_SGSN see clause 25.7.2. + +1133 **19.1.1A.4 Procedures in the CSS** + +1134 The MAP process in the CSS to handle a VCSG location updating request from a VLR or SGSN is shown in figure +1135 19.1.1A/4. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as +1136 follows: + +- 1137 Receive\_Open\_Ind see clause 25.1.1; + +1138 Check\_Indication see clause 25.2.1; +1139 Check\_Confirmation see clause 25.2.2; +1140 Insert\_VCSG\_Subs\_Data\_Framed\_CSS see clause 19.5A.1. +1141 + +process Update\_VCSG\_Location\_VLR + +Process in the VLR to open a dialogue for VCSG location updating with the CSS + +Signals to/from the left are to/from the VCSG mobility management application process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/from the CSS + +![Flowchart for process Update_VCSG_Location_VLR. It starts with an entry point leading to 'Null', then 'Update VCSG Location'. A decision 'CSS address known?' follows. If 'No', it goes to 'Set negative result: Unknown CSS' and then 'Update VCSG Location negative response' to 'Null'. If 'Yes', it sends 'MAP_OPEN_req', 'MAP_UPDATE_VCSG_LOCATION_req', and 'MAP_DELIMITER_req', then receives 'Open_Cnf'. If 'OK', it goes to 'Wait_For_CSS_Response'. If 'Vr, Error', it goes to 'Set negative result: Procedure error' and then 'Update VCSG Location negative response' to 'Null'. From 'Wait_For_CSS_Response', it branches into five paths: 1) 'MAP_INSERT_SUBSCRIBER_DATA_ind' leads to 'insert subscriber data ack', which leads to 'MAP_INSERT_SUBSCRIBER_DATA_rsp', which leads to 'Wait_For_CSS_Response'. 2) 'insert subscriber data neg ack' leads to 'Set user error'. 3) 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req'. 4) 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' leads to 'Set negative result: System failure' and then 'Update VCSG Location negative response' to 'Null'. 5) A note 'Subscriber data confirmed by CSS: False; Location Information confirmed by CSS: False.' leads to 'Update VCSG Location negative response' to 'Null'.](065202f6f7813acf6a58126294abec05_img.jpg) + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> UpdateLoc[Update VCSG Location] + UpdateLoc --> CSSKnown{CSS address known?} + CSSKnown -- No --> SetNeg1[Set negative result: Unknown CSS] + SetNeg1 --> NegResp1[Update VCSG Location negative response] + NegResp1 --> Null2([Null]) + CSSKnown -- Yes --> SendReq[MAP_OPEN_req +MAP_UPDATE_VCSG_LOCATION_req +MAP_DELIMITER_req] + SendReq --> RecvCnf[Receive Open_Cnf] + RecvCnf -- OK --> WaitCSS[Wait_For_CSS_Response] + RecvCnf -- "Vr, Error" --> SetNeg2[Set negative result: Procedure error] + SetNeg2 --> NegResp2[Update VCSG Location negative response] + NegResp2 --> Null3([Null]) + WaitCSS --> Ind1[MAP_INSERT_SUBSCRIBER_DATA_ind] + Ind1 --> Ack1[insert subscriber data ack] + Ack1 --> Rsp1[MAP_INSERT_SUBSCRIBER_DATA_rsp] + Rsp1 --> WaitCSS + Ack1 --> Ack2[insert subscriber data neg ack] + Ack2 --> UserErr[Set user error] + Ack1 --> Ind2[MAP_NOTICE_ind] + Ind2 --> CloseReq[MAP_CLOSE_req] + Ack1 --> Ind3["MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind"] + Ind3 --> SetNeg3[Set negative result: System failure] + SetNeg3 --> NegResp3[Update VCSG Location negative response] + NegResp3 --> Null4([Null]) + Ack1 --> Note["Subscriber data confirmed by CSS: False; +Location Information confirmed by CSS: False."] + Note --> NegResp4[Update VCSG Location negative response] + NegResp4 --> Null5([Null]) + +``` + +Flowchart for process Update\_VCSG\_Location\_VLR. It starts with an entry point leading to 'Null', then 'Update VCSG Location'. A decision 'CSS address known?' follows. If 'No', it goes to 'Set negative result: Unknown CSS' and then 'Update VCSG Location negative response' to 'Null'. If 'Yes', it sends 'MAP\_OPEN\_req', 'MAP\_UPDATE\_VCSG\_LOCATION\_req', and 'MAP\_DELIMITER\_req', then receives 'Open\_Cnf'. If 'OK', it goes to 'Wait\_For\_CSS\_Response'. If 'Vr, Error', it goes to 'Set negative result: Procedure error' and then 'Update VCSG Location negative response' to 'Null'. From 'Wait\_For\_CSS\_Response', it branches into five paths: 1) 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind' leads to 'insert subscriber data ack', which leads to 'MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp', which leads to 'Wait\_For\_CSS\_Response'. 2) 'insert subscriber data neg ack' leads to 'Set user error'. 3) 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req'. 4) 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' leads to 'Set negative result: System failure' and then 'Update VCSG Location negative response' to 'Null'. 5) A note 'Subscriber data confirmed by CSS: False; Location Information confirmed by CSS: False.' leads to 'Update VCSG Location negative response' to 'Null'. + +1142 + +1143 + +Figure 19.1.1A/2 (sheet 1 of 2): Process Update\_VCSG\_Location\_VLR + +process Update\_VCSG\_Location\_VLR + +Process in the VLR to open a dialogue for VCSG location updating with the CSS + +Signals to/from the left are to/from the VCSG mobility management application process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/from the CSS + +![Flowchart for process Update_VCSG_Location_VLR. It starts with 'Wait_For_CSS_Response', followed by 'MAP_UPDATE_VCSG_LOCATION_cnf', and 'Check_Confirmation'. From 'Check_Confirmation', an 'OK' path leads to 'Set result' (with 'Subscriber data confirmed by CSS: True; Location Information confirmed by CSS: True.') and then to 'Update VCSG Location response' and 'Null'. A 'Provider Error, Data Error' path leads to 'Set negative result' and then to 'Update VCSG Location negative response' (with 'Subscriber data confirmed by CSS: False; Location Information confirmed by CSS: False.') and 'Null'. A 'User error' decision point leads to 'Unknown Subscriber' (Set negative result: Unknown subscriber) or 'else' (Set negative result), both leading to 'Update VCSG Location negative response' and 'Null'.](23f1a7e498776906be1c80ef1e61686b_img.jpg) + +``` + +graph TD + Start([Wait_For_CSS_Response]) --> cnf[MAP_UPDATE_VCSG_LOCATION_cnf] + cnf --> Check[Check_Confirmation] + Check -- OK --> SetResult[Set result] + SetResult --> ResultInfo[Subscriber data confirmed by CSS: True; Location Information confirmed by CSS: True.] + ResultInfo --> UpdateResponse{Update VCSG Location response} + UpdateResponse --> Null1([Null]) + Check -- "Provider Error, Data Error" --> SetNegResult1[Set negative result] + SetNegResult1 --> UpdateNegResponse{Update VCSG Location negative response} + UpdateNegResponse --> NegResultInfo[Subscriber data confirmed by CSS: False; Location Information confirmed by CSS: False.] + NegResultInfo --> Null2([Null]) + Check -- User error --> UserError{User error} + UserError -- Unknown Subscriber --> SetNegResult2[Set negative result: Unknown subscriber] + UserError -- else --> SetNegResult3[Set negative result] + SetNegResult2 --> UpdateNegResponse + SetNegResult3 --> UpdateNegResponse + +``` + +Flowchart for process Update\_VCSG\_Location\_VLR. It starts with 'Wait\_For\_CSS\_Response', followed by 'MAP\_UPDATE\_VCSG\_LOCATION\_cnf', and 'Check\_Confirmation'. From 'Check\_Confirmation', an 'OK' path leads to 'Set result' (with 'Subscriber data confirmed by CSS: True; Location Information confirmed by CSS: True.') and then to 'Update VCSG Location response' and 'Null'. A 'Provider Error, Data Error' path leads to 'Set negative result' and then to 'Update VCSG Location negative response' (with 'Subscriber data confirmed by CSS: False; Location Information confirmed by CSS: False.') and 'Null'. A 'User error' decision point leads to 'Unknown Subscriber' (Set negative result: Unknown subscriber) or 'else' (Set negative result), both leading to 'Update VCSG Location negative response' and 'Null'. + +1144 + +1145 + +Figure 19.1.1A/2 (sheet 2 of 2): Process Update\_VCSG\_Location\_VLR + +process Update\_VCSG\_Location\_SGSN + +Process in the SGSN to open a dialogue for a VCSG location updating with the CSS + +Signals to/from the left are to/from the VCSG mobility management application process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/from the CSS + +![Flowchart for process Update_VCSG_Location_SGSN. It starts with NULL, followed by Update VCSG Location. A decision 'CSS address known?' leads to 'Yes' (sending MAP_OPEN_req, MAP_UPDATE_VCSG_LOCATION_req, MAP_DELIMITER_req) or 'No' (Set negative result: Unknown CSS). The 'Yes' path leads to Receive_Open_Cnf, then Wait_For_CSS_Response. From Wait_For_CSS_Response, multiple paths emerge: 'Vr, Error' leads to Set negative result: Procedure error; 'MAP_INSERT_SUBSCRIBER_DATA ind' leads to Insert subscriber data; 'insert subscriber data ack' leads to MAP_INSERT_SUBSCRIBER_DATA_rsp; 'insert subscriber data neg ack' leads to Set user error; 'MAP_NOTICE_ind' leads to MAP_CLOSE_req; 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' leads to Set negative result: System failure. All these paths eventually lead to Update VCSG Location negative response and then Null. A note indicates 'Subscriber data confirmed by CSS: False; Location Information confirmed by CSS: False.'](df8aa6d2b7df5f22fedb0cbcc364972d_img.jpg) + +``` + +graph TD + Start([NULL]) --> Init[Update VCSG Location] + Init --> Decision{CSS address known?} + Decision -- No --> Neg1[Set negative result: Unknown CSS] + Neg1 --> Neg1Resp[Update VCSG Location negative response] + Neg1Resp --> Null1([Null]) + Decision -- Yes --> Req[MAP_OPEN_req +MAP_UPDATE_VCSG_LOCATION_req +MAP_DELIMITER_req] + Req --> OpenCnf[Receive_Open_Cnf] + OpenCnf -- OK --> Wait[Wait_For_CSS_Response] + OpenCnf -- Vr, Error --> Neg2[Set negative result: Procedure error] + Wait --> Ind1[MAP_INSERT_SUBSCRIBER_DATA ind] + Wait --> Ack1[insert subscriber data ack] + Wait --> NegAck1[insert subscriber data neg ack] + Wait --> Ind2[MAP_NOTICE_ind] + Wait --> Ind3[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Ind1 --> InsertData[Insert subscriber data] + InsertData --> Wait2[Wait_For_CSS_Response] + Ack1 --> Rsp1[MAP_INSERT_SUBSCRIBER_DATA_rsp] + NegAck1 --> UserError[Set user error] + Ind2 --> CloseReq[MAP_CLOSE_req] + Ind3 --> Neg3[Set negative result: System failure] + UserError --> Neg2Resp[Update VCSG Location negative response] + CloseReq --> Neg2Resp + Neg3 --> Neg3Resp[Update VCSG Location negative response] + Neg2Resp --> Null2([Null]) + Neg3Resp --> Null3([Null]) + Note[Subscriber data confirmed by CSS: False; +Location Information confirmed by CSS: False.] + +``` + +Flowchart for process Update\_VCSG\_Location\_SGSN. It starts with NULL, followed by Update VCSG Location. A decision 'CSS address known?' leads to 'Yes' (sending MAP\_OPEN\_req, MAP\_UPDATE\_VCSG\_LOCATION\_req, MAP\_DELIMITER\_req) or 'No' (Set negative result: Unknown CSS). The 'Yes' path leads to Receive\_Open\_Cnf, then Wait\_For\_CSS\_Response. From Wait\_For\_CSS\_Response, multiple paths emerge: 'Vr, Error' leads to Set negative result: Procedure error; 'MAP\_INSERT\_SUBSCRIBER\_DATA ind' leads to Insert subscriber data; 'insert subscriber data ack' leads to MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp; 'insert subscriber data neg ack' leads to Set user error; 'MAP\_NOTICE\_ind' leads to MAP\_CLOSE\_req; 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' leads to Set negative result: System failure. All these paths eventually lead to Update VCSG Location negative response and then Null. A note indicates 'Subscriber data confirmed by CSS: False; Location Information confirmed by CSS: False.' + +1146 + +1147 + +Figure 19.1.1A/3 (sheet 1 of 2): Process Update\_VCSG\_Location\_SGSN + +process Update\_VCSG\_Location\_SGSN + +Process in the SGSN to open a dialogue for a VCSG location updating with the CSS + +Signals to/from the left are to/from the VCSG mobility management application process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/from the CSS + +![Flowchart for process Update_VCSG_Location_SGSN. It starts with 'Wait_For_CSS_Response', followed by 'MAP_UPDATE_VCSG_LOCATION.cnf', and 'Check_Confirmation'. From 'Check_Confirmation', there are three paths: 'OK' leading to 'Set result' (with a note 'Subscriber data confirmed by CSS: True; Location Information confirmed by CSS: True.') and then 'Update VCSG Location response' to 'Null'; 'User error' leading to 'Set negative result: Unknown subscriber' and then 'Update VCSG Location negative response' (with a note 'Subscriber data confirmed by CSS: False; Location Information confirmed by CSS: False.') to 'Null'; and 'Provider Error, Data Error' leading to 'Set negative result' to 'Null'.](bbefe499225465a871d9b936d8a84e39_img.jpg) + +``` + +graph TD + Start([Wait_For_CSS_Response]) --> cnf[MAP_UPDATE_VCSG_LOCATION.cnf] + cnf --> Check[Check_Confirmation] + Check -- OK --> SetResult[Set result] + SetResult --> NoteTrue[Subscriber data confirmed by CSS: True; Location Information confirmed by CSS: True.] + NoteTrue --> UpdateResponse{Update VCSG Location response} + UpdateResponse --> Null1([Null]) + Check -- User error --> Unknown[Set negative result: Unknown subscriber] + Unknown --> NegativeResponse{Update VCSG Location negative response} + NegativeResponse --> NoteFalse[Subscriber data confirmed by CSS: False; Location Information confirmed by CSS: False.] + NoteFalse --> Null2([Null]) + Check -- "else (Provider Error, Data Error)" --> NegResult1[Set negative result] + NegResult1 --> Null3([Null]) + +``` + +Flowchart for process Update\_VCSG\_Location\_SGSN. It starts with 'Wait\_For\_CSS\_Response', followed by 'MAP\_UPDATE\_VCSG\_LOCATION.cnf', and 'Check\_Confirmation'. From 'Check\_Confirmation', there are three paths: 'OK' leading to 'Set result' (with a note 'Subscriber data confirmed by CSS: True; Location Information confirmed by CSS: True.') and then 'Update VCSG Location response' to 'Null'; 'User error' leading to 'Set negative result: Unknown subscriber' and then 'Update VCSG Location negative response' (with a note 'Subscriber data confirmed by CSS: False; Location Information confirmed by CSS: False.') to 'Null'; and 'Provider Error, Data Error' leading to 'Set negative result' to 'Null'. + +1148 + +1149 + +Figure 19.1.1A/3 (sheet 2 of 2): Process Update\_VCSG\_Location\_SGSN + +![Flowchart for process Update_VCSG_Location_CSS. It starts with an initial node, followed by 'Null', then 'Receive Open_Ind'. From 'Receive Open_Ind', an 'OK' path leads to 'Wait_For_Service_Primitive' and a 'Vr, Error' path leads to 'Null'. 'Wait_For_Service_Primitive' branches into three paths: 'MAP_P_ABORT_ind' leading to 'Null', 'MAP_UPDATE_VCSG_LOCATION_ind' leading to 'Check_Indication', and 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req' and then 'Null'. 'Check_Indication' has an 'OK' path leading to 'Subscriber known?' and an 'Error' path leading to a response block ('MAP_UPDATE_VCSG_LOCATION_rsp', 'MAP_CLOSE_req') and then 'Null'. 'Subscriber known?' has a 'Yes' path leading to connector '1' and a 'No' path leading to 'Set diagnostic: IMSI unknown', 'Set User Error: Unknown subscriber', a response block ('MAP_UPDATE_VCSG_LOCATION_rsp', 'MAP_CLOSE_req'), and finally 'Null'.](69907ac8150588f702fb1fbb9748e7e3_img.jpg) + +process Update\_VCSG\_Location\_CSS UVL\_CSS1(2) + +Process in the CSS to handle an Update VCSG Location request from a VLR or SGSN + +Signals to/from the left are to/from the VLR or the SGSN; signals to/from the right are to/from the VCSG mobility management application process in the CSS + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> RecOpen[Receive Open_Ind] + RecOpen -- OK --> Wait[Wait_For_Service_Primitive] + RecOpen -- "Vr, Error" --> Null2([Null]) + Wait --> MAP_P_ABORT{MAP_P_ABORT_ind} + Wait --> MAP_UPDATE{MAP_UPDATE_VCSG_LOCATION_ind} + Wait --> MAP_NOTICE{MAP_NOTICE_ind} + MAP_P_ABORT --> Null3([Null]) + MAP_UPDATE --> Check[Check_Indication] + MAP_NOTICE --> MAP_CLOSE_req{MAP_CLOSE_req} + MAP_CLOSE_req --> Null4([Null]) + Check -- OK --> SubKnown{Subscriber known?} + Check -- Error --> Res1[MAP_UPDATE_VCSG_LOCATION_rsp +MAP_CLOSE_req] + Res1 --> Null5([Null]) + SubKnown -- Yes --> Connector1((1)) + SubKnown -- No --> SetDiag[Set diagnostic: +IMSI unknown] + SetDiag --> SetErr[Set User Error: +Unknown subscriber] + SetErr --> Res2[MAP_UPDATE_VCSG_LOCATION_rsp +MAP_CLOSE_req] + Res2 --> Null6([Null]) + +``` + +Flowchart for process Update\_VCSG\_Location\_CSS. It starts with an initial node, followed by 'Null', then 'Receive Open\_Ind'. From 'Receive Open\_Ind', an 'OK' path leads to 'Wait\_For\_Service\_Primitive' and a 'Vr, Error' path leads to 'Null'. 'Wait\_For\_Service\_Primitive' branches into three paths: 'MAP\_P\_ABORT\_ind' leading to 'Null', 'MAP\_UPDATE\_VCSG\_LOCATION\_ind' leading to 'Check\_Indication', and 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req' and then 'Null'. 'Check\_Indication' has an 'OK' path leading to 'Subscriber known?' and an 'Error' path leading to a response block ('MAP\_UPDATE\_VCSG\_LOCATION\_rsp', 'MAP\_CLOSE\_req') and then 'Null'. 'Subscriber known?' has a 'Yes' path leading to connector '1' and a 'No' path leading to 'Set diagnostic: IMSI unknown', 'Set User Error: Unknown subscriber', a response block ('MAP\_UPDATE\_VCSG\_LOCATION\_rsp', 'MAP\_CLOSE\_req'), and finally 'Null'. + +1150 + +1151 + +Figure 19.1.1A/4 (sheet 1 of 2): Process Update\_VCSG\_Location\_CSS + +![Flowchart for process Update_VCSG_Location_CSS. It starts at connector 1, proceeds to Insert_VCSG_Subs_Data_Framed_CSS, then to a Result? decision. If OK, it goes to Update_Routeing_Info, then to a merge point for MAP_UPDATE_VCSG_LOCATION_rsp and MAP_CLOSE_req, and finally to Null. If Error, it goes to Set User Error: System failure, then to the same merge point. If Aborted, it goes directly to Null.](e3adfe9588ba47502c2c933a6e025ca4_img.jpg) + +process Update\_VCSG\_Location\_CSS UVL\_CSS2(2) + +Process in the CSS to handle an Update VCSG Location request from a VLR or SGSN + +Signals to/from the left are to/from the VLR or the SGSN; signals to/from the right are to/from the VCSG mobility management application process in the CSS + +``` + +graph TD + 1((1)) --> Insert[Insert_VCSG_Subs_Data_Framed_CSS] + Insert --> Result{Result?} + Result -- OK --> Update[Update_Routeing_Info] + Update --> Merge{ } + Merge --> Null1([Null]) + Result -- Error --> Error[Set User Error: System failure] + Error --> Merge + Merge -- "MAP_UPDATE_VCSG_LOCATION_rsp +MAP_CLOSE_req" --> Null2([Null]) + Result -- Aborted --> Null3([Null]) + +``` + +Flowchart for process Update\_VCSG\_Location\_CSS. It starts at connector 1, proceeds to Insert\_VCSG\_Subs\_Data\_Framed\_CSS, then to a Result? decision. If OK, it goes to Update\_Routeing\_Info, then to a merge point for MAP\_UPDATE\_VCSG\_LOCATION\_rsp and MAP\_CLOSE\_req, and finally to Null. If Error, it goes to Set User Error: System failure, then to the same merge point. If Aborted, it goes directly to Null. + +1152 + +1153 + +Figure 19.1.1A/4 (sheet 2 of 2): Process Update\_VCSG\_Location\_CSS + +1154 **19.1.2 Location Cancellation** + +1155 **19.1.2.1 General** + +1156 Location cancellation is used to delete a subscriber record from the serving node (VLR or SGSN). The procedure is +1157 invoked: + +- 1158 - because the subscriber has registered with a new serving node, or +- 1159 - because the HPLMN operator has decided to delete the subscriber record from the serving node, e.g. because the +1160 subscription has been withdrawn, or because roaming restrictions have been imposed. Location cancellation can +1161 be used to force location updating including updating of subscriber data in the serving node at the next +1162 subscriber access. + +1163 The message flow for location cancellation for a non-GPRS subscriber is shown in figure 19.1.2/1. + +1164 The message flow for location cancellation for a GPRS subscriber is shown in figure 19.1.2/2. + +![Sequence diagram for non-GPRS location cancellation showing interactions between VLR, HLR, and PVLR.](436937dfff8d225780cc49207a18e87f_img.jpg) + +The diagram shows three lifelines: VLR, HLR, and PVLR. + 1. A dotted arrow points from the VLR lifeline to the HLR lifeline, labeled with a box containing '1'. + 2. A solid arrow points from the HLR lifeline to the PVLR lifeline, labeled with a box containing '2'. + 3. A solid arrow points from the PVLR lifeline back to the HLR lifeline, labeled with a box containing '3'. + +Sequence diagram for non-GPRS location cancellation showing interactions between VLR, HLR, and PVLR. + +1165 + +- 1166 1) MAP\_UPDATE\_LOCATION\_req/ind +- 1167 2) MAP\_CANCEL\_LOCATION\_req/ind +- 1168 3) MAP\_CANCEL\_LOCATION\_rsp/cnf +- 1169 + +1170 NOTE: The service shown in dotted lines indicates the trigger provided by other MAP signalling. +1171 + +1172 **Figure 19.1.2/1: Message flow for Location Cancellation (non-GPRS)** +1173 + +![Sequence diagram for GPRS location cancellation showing interactions between SGSN, HLR, and PSGSN.](5bb65c8534cf12a55e688b511347512f_img.jpg) + +The diagram shows three lifelines: SGSN, HLR, and PSGSN. + 1. A dotted arrow points from the SGSN lifeline to the HLR lifeline, labeled with a box containing '1'. + 2. A solid arrow points from the HLR lifeline to the PSGSN lifeline, labeled with a box containing '2'. + 3. A solid arrow points from the PSGSN lifeline back to the HLR lifeline, labeled with a box containing '3'. + +Sequence diagram for GPRS location cancellation showing interactions between SGSN, HLR, and PSGSN. + +1174 + +- 1175 1) MAP\_UPDATE\_GPRS\_LOCATION\_req/ind +- 1176 2) MAP\_CANCEL\_LOCATION\_req/ind +- 1177 3) MAP\_CANCEL\_LOCATION\_rsp/cnf +- 1178 + +1179 NOTE: The service shown in dotted lines indicates the trigger provided by other MAP signalling. +1180 + +1181 **Figure 19.1.2/2: Message flow for Location Cancellation (GPRS)** +1182 + +1183 **19.1.2.2 Procedure in the HLR** + +1184 The MAP process in the HLR to cancel the location information in a VLR is shown in figure 19.1.2/3. The MAP +1185 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +1186     Receive\_Open\_Cnf     see clause 25.1.2; + +1187     Check\_Confirmation     see clause 25.2.2. + +1188 The MAP process in the HLR to cancel the location information in a VLR as an independent process invoked from +1189 another process is shown in figure 19.1.2/4. + +1190 The MAP process in the HLR to cancel the location information in an SGSN is shown in figure 19.1.2/5. The MAP +1191 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +1192     Receive\_Open\_Cnf     see clause 25.1.2; + +1193     Check\_Confirmation     see clause 25.2.2. + +1194 The MAP process in the HLR to cancel the location information in an SGSN as an independent process invoked from +1195 another process is shown in figure 19.1.2/6. + +### 1196 19.1.2.3     Procedure in the VLR + +1197 The MAP process in the VLR to handle a location cancellation request is shown in figure 19.1.2/7. The MAP process +1198 invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1199     Receive\_Open\_Ind     see clause 25.1.1. + +### 1200 19.1.2.4     Procedure in the SGSN + +1201 The MAP process in the SGSN to handle a location cancellation request is shown in figure 19.1.2/8. The MAP process +1202 invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1203     Receive\_Open\_Ind     see clause 25.1.1. + +1204 + +![Flowchart for process Cancel_Location_HLR. The process starts with an initial state, followed by 'Null', 'Cancel Location', and a merge point for MAP requests (OPEN, CANCEL_LOCATION, DELIMITER). It then enters 'Receive_Open_Cnf'. From here, a 'Vr' path leads to 'Perform MAP Vr dialogue' and 'Null'. An 'OK' path leads to 'Wait_For_VLR_Response', which then branches into three indicators: 'MAP_P_ABORT_ind' (leading to 'Abort' and 'Null'), 'MAP_CANCEL_LOCATION_cnf' (leading to 'Check Confirmation'), and 'MAP_NOTICE_ind' (leading to 'MAP_CLOSE_req'). 'Check Confirmation' has three outcomes: 'Provider Error, Data Error' (leading to 'Set negative response: System failure', 'Cancel Location negative response', and 'Null'), 'OK' (leading to 'Cancel Location ack' and 'Null'), and 'User Error' (leading to 'Set negative response', 'Cancel Location negative response', and 'Null'). An 'Error' path from 'Wait_For_VLR_Response' leads to 'Set negative response: System failure', 'Cancel Location negative response', and 'Null'.](ad73d5ca7408dae269a6a821e33b1869_img.jpg) + +process Cancel\_Location\_HLR CL\_HLR1(1) + +Process in the HLR to cancel the information stored in a VLR + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the location management application process in the HLR (see 3GPP TS 23.012) or the process Cancel\_Location\_Child\_HLR + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> CancelLocation[Cancel Location] + CancelLocation --> Merge{ } + Merge --- MAP_Req["MAP_OPEN_req +MAP_CANCEL_LOCATION_req +MAP_DELIMITER_req"] + Merge --> ReceiveOpenCnf[Receive_Open_Cnf] + + ReceiveOpenCnf -- Vr --> PerformVr[Perform MAP Vr dialogue] + PerformVr --> Null2([Null]) + + ReceiveOpenCnf -- OK --> WaitForVLR[Wait_For_VLR_Response] + + WaitForVLR -- Error --> SetNegSys[Set negative response: System failure] + SetNegSys --> CancelNeg[Cancel Location negative response] + CancelNeg --> Null3([Null]) + + WaitForVLR --> MAP_P_ABORT_ind{MAP_P_ABORT_ind} + MAP_P_ABORT_ind --> Abort[Abort] + Abort --> Null4([Null]) + + WaitForVLR --> MAP_CANCEL_LOCATION_cnf{MAP_CANCEL_LOCATION_cnf} + MAP_CANCEL_LOCATION_cnf --> CheckConfirmation[Check Confirmation] + + CheckConfirmation -- "Provider Error, Data Error" --> SetNegSys2[Set negative response: System failure] + SetNegSys2 --> CancelNeg2[Cancel Location negative response] + CancelNeg2 --> Null5([Null]) + + CheckConfirmation -- OK --> CancelLocAck[Cancel Location ack] + CancelLocAck --> Null6([Null]) + + CheckConfirmation -- User Error --> SetNegUser[Set negative response] + SetNegUser --> CancelNeg3[Cancel Location negative response] + CancelNeg3 --> Null7([Null]) + + WaitForVLR --> MAP_NOTICE_ind{MAP_NOTICE_ind} + MAP_NOTICE_ind --> MAP_CLOSE_req{MAP_CLOSE_req} + MAP_CLOSE_req --> SetNegSys3[Set negative response: System failure] + SetNegSys3 --> CancelNeg4[Cancel Location negative response] + CancelNeg4 --> Null8([Null]) + +``` + +Flowchart for process Cancel\_Location\_HLR. The process starts with an initial state, followed by 'Null', 'Cancel Location', and a merge point for MAP requests (OPEN, CANCEL\_LOCATION, DELIMITER). It then enters 'Receive\_Open\_Cnf'. From here, a 'Vr' path leads to 'Perform MAP Vr dialogue' and 'Null'. An 'OK' path leads to 'Wait\_For\_VLR\_Response', which then branches into three indicators: 'MAP\_P\_ABORT\_ind' (leading to 'Abort' and 'Null'), 'MAP\_CANCEL\_LOCATION\_cnf' (leading to 'Check Confirmation'), and 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req'). 'Check Confirmation' has three outcomes: 'Provider Error, Data Error' (leading to 'Set negative response: System failure', 'Cancel Location negative response', and 'Null'), 'OK' (leading to 'Cancel Location ack' and 'Null'), and 'User Error' (leading to 'Set negative response', 'Cancel Location negative response', and 'Null'). An 'Error' path from 'Wait\_For\_VLR\_Response' leads to 'Set negative response: System failure', 'Cancel Location negative response', and 'Null'. + +1205 + +1206 + +Figure 19.1.2/3: Process Cancel\_Location\_HLR + +![State transition diagram for process Cancel_Location_Child_HLR. The process starts at an initial state (oval), transitions to a 'Cancel Location' state (diamond), then to a 'Wait_For_VLR_Response' state (oval). From there, it branches into two possible states: 'Cancel Location negative response' (diamond) and 'Cancel Location ack' (diamond). Both of these states lead to terminal states (crosses). A note on the top left indicates this is a child process in the HLR to cancel information in a VLR. A note on the top right indicates signals to/from the left are to/from the process Cancel_Location_HLR.](dc16cec51c6540030d965176f36e4810_img.jpg) + +process **Cancel\_Location\_Child\_HLR** CLC\_HLR1(1) + +``` +stateDiagram-v2 + [*] --> Cancel_Location + Cancel_Location --> Wait_For_VLR_Response + state "Cancel Location negative response" as Cancel_Location_negative_response + state "Cancel Location ack" as Cancel_Location_ack + Wait_For_VLR_Response --> Cancel_Location_negative_response + Wait_For_VLR_Response --> Cancel_Location_ack + Cancel_Location_negative_response --> [*] + Cancel_Location_ack --> [*] +``` + +Child process in the HLR to cancel the information stored in a VLR + +Signals to/from the left are to/from the process **Cancel\_Location\_HLR** + +State transition diagram for process Cancel\_Location\_Child\_HLR. The process starts at an initial state (oval), transitions to a 'Cancel Location' state (diamond), then to a 'Wait\_For\_VLR\_Response' state (oval). From there, it branches into two possible states: 'Cancel Location negative response' (diamond) and 'Cancel Location ack' (diamond). Both of these states lead to terminal states (crosses). A note on the top left indicates this is a child process in the HLR to cancel information in a VLR. A note on the top right indicates signals to/from the left are to/from the process Cancel\_Location\_HLR. + +1207 + +1208 + +**Figure 19.1.2/4: Process Cancel\_Location\_Child\_HLR** + +![Flowchart for process Cancel_GPRS_Location_HLR. It starts with an internal timer expiry leading to 'Repeat attempt timer expired', which then leads to 'Cancel GPRS Location'. From 'Cancel GPRS Location', it sends MAP requests (OPEN, CANCEL_GPRS_LOCATION, DELIMITER) and waits for a response. If 'OK', it checks the confirmation. If 'User Error' or 'Provider Error/Data Error', it checks if a repeat attempt is allowed. If 'Yes', it restarts the timer and loops back. If 'No', it sets a negative response and ends. If 'Vr, Error', it sets a system failure response and ends.](3ba7b01a4ad082fa3e585e0945b135d2_img.jpg) + +**process Cancel\_GPRS\_Location\_HLR** **CGL\_HLR1(1)** + +Process in the HLR to cancel the information stored in an SGSN + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the GPRS mobility management application process in the HLR (see 3GPP TS 23.060) or the process Cancel\_GPRS\_Location\_Child\_HLR unless marked otherwise + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> CancelGPRS[Cancel GPRS Location] + + Internal[Internal] --> TimerExpired{Repeat attempt timer expired} + + CancelGPRS --> MAPReq["MAP_OPEN_req +MAP_CANCEL_GPRS_LOCATION_req +MAP_DELIMITER_req"] + + MAPReq --> ReceiveOpenCnf[Receive_Open_Cnf] + + ReceiveOpenCnf --> WaitForVLR[Wait_For_VLR_Response] + + WaitForVLR --> DecisionOK{OK} + + DecisionOK -- Vr, Error --> SystemFailure[Set negative response: System failure] + + SystemFailure --> CancelNeg[Cancel GPRS Location negative response] + + CancelNeg --> Null2([Null]) + + DecisionOK -- OK --> CheckConfirmation[Check Confirmation] + + CheckConfirmation --> DecisionProviderError{Provider Error, Data Error} + + DecisionProviderError -- Yes --> RepeatAttempt{Repeat attempt?} + + RepeatAttempt -- No --> SystemFailure2[Set negative response: System failure] + + SystemFailure2 --> CancelNeg2[Cancel GPRS Location negative response] + + CancelNeg2 --> Null3([Null]) + + RepeatAttempt -- Yes --> StartRepeat[Start Repeat attempt timer] + + StartRepeat --> WaitForRepeat[Wait_For_Repeat_Attempt_Timer_Expiry] + + WaitForRepeat --> TimerExpired + + DecisionProviderError -- OK --> CancelAck[Cancel GPRS Location ack] + + CancelAck --> Null4([Null]) + + DecisionProviderError -- User Error --> DecisionUserError{Repeat attempt?} + + DecisionUserError -- No --> SetNeg[Set negative response] + + SetNeg --> CancelNeg3[Cancel GPRS Location negative response] + + CancelNeg3 --> Null5([Null]) + + DecisionUserError -- Yes --> StartRepeat2[Start Repeat attempt timer] + + StartRepeat2 --> WaitForRepeat2[Wait_For_Repeat_Attempt_Timer_Expiry] + + WaitForRepeat2 --> TimerExpired + + DecisionOK --> MAP_P_ABORT[MAP_P_ABORT_ind] + + DecisionOK --> MAP_NOTICE[MAP_NOTICE_ind] + + DecisionOK --> MAP_CANCEL_CNF[MAP_CANCEL_LOCATION_cnf] + + MAP_CANCEL_CNF --> CheckConfirmation + + MAP_NOTICE --> MAP_CLOSE_REQ{MAP_CLOSE_req} + + MAP_CLOSE_REQ --> DecisionProviderError + + MAP_P_ABORT --> DecisionProviderError + +``` + +Flowchart for process Cancel\_GPRS\_Location\_HLR. It starts with an internal timer expiry leading to 'Repeat attempt timer expired', which then leads to 'Cancel GPRS Location'. From 'Cancel GPRS Location', it sends MAP requests (OPEN, CANCEL\_GPRS\_LOCATION, DELIMITER) and waits for a response. If 'OK', it checks the confirmation. If 'User Error' or 'Provider Error/Data Error', it checks if a repeat attempt is allowed. If 'Yes', it restarts the timer and loops back. If 'No', it sets a negative response and ends. If 'Vr, Error', it sets a system failure response and ends. + +1209 + +1210 + +**Figure 19.1.2/5: Process Cancel\_GPRS\_Location\_HLR** + +![Flowchart for process Cancel_GPRS_Location_Child_HLR. It starts with an oval, followed by a 'Cancel GPRS Location' message box. Then a 'Wait_For_SGSN_Response' box. A decision line splits into two message boxes: 'Cancel GPRS Location negative response' and 'Cancel GPRS Location ack'. Both lead to an 'X' symbol representing an exit or error state.](96bcdda8c2915356b4fa959ef3c4ee2f_img.jpg) + +process Cancel\_GPRS\_Location\_Child\_HLR CGLC\_HLR1(1) + +Child process in the HLR to cancel the information stored in an SGSN + +Signals to/from the left are to/from the process Cancel\_GPRS\_Location\_HLR + +``` + +graph TD + Start([ ]) --> Msg1[Cancel GPRS Location] + Msg1 --> Wait[Wait_For_SGSN_Response] + Wait --> Decision(( )) + Decision --> Msg2[Cancel GPRS Location negative response] + Decision --> Msg3[Cancel GPRS Location ack] + Msg2 --> Exit1[X] + Msg3 --> Exit2[X] + +``` + +Flowchart for process Cancel\_GPRS\_Location\_Child\_HLR. It starts with an oval, followed by a 'Cancel GPRS Location' message box. Then a 'Wait\_For\_SGSN\_Response' box. A decision line splits into two message boxes: 'Cancel GPRS Location negative response' and 'Cancel GPRS Location ack'. Both lead to an 'X' symbol representing an exit or error state. + +1211 + +1212 + +**Figure 19.1.2/6: Process Cancel\_GPRS\_Location\_Child\_HLR** + +![Flowchart for process Cancel_Location_VLR. It starts with an initial node, followed by 'Null', then 'Receive Open_Ind'. From 'Receive Open_Ind', three paths emerge: 'Vr' leading to 'Perform MAP Vr dialogue' then 'Null'; 'OK' leading to 'Wait_For_Service_Primitive'; and 'Error' leading to 'Null'. From 'Wait_For_Service_Primitive', a 'MAP_CANCEL_LOCATION_ind' signal is received, leading to 'Cancel Location', then 'Wait_For_Application_Response'. From 'Wait_For_Application_Response', two paths emerge: 'Cancel Location ack' leading to 'Set Result', and 'Cancel Location negative response' leading to 'Set User Error'. Both 'Set Result' and 'Set User Error' lead to a merge point, which then leads to a 'MAP_CANCEL_LOCATION_rsp' / 'MAP_CLOSE_req' signal, and finally to 'Null'.](135596da3b529757391156b44220a6c7_img.jpg) + +**process Cancel\_Location\_VLR** **CL\_VLR1(1)** + +Process in the VLR to handle a Cancel Location request + +Signals to/from the left are to/from the location management application process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/from the HLR + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> RecOpen[Receive Open_Ind] + RecOpen -- Vr --> PerformVr[Perform MAP Vr dialogue] + PerformVr --> Null2([Null]) + RecOpen -- OK --> WaitService[Wait_For_Service_Primitive] + RecOpen -- Error --> Null3([Null]) + WaitService -- "MAP_CANCEL_LOCATION_ind" --> CancelLoc{Cancel Location} + CancelLoc --> WaitApp[Wait_For_Application_Response] + WaitApp -- "Cancel Location ack" --> SetResult[Set Result] + WaitApp -- "Cancel Location negative response" --> SetUserError[Set User Error] + SetResult --> Merge(( )) + SetUserError --> Merge + Merge -- "MAP_CANCEL_LOCATION_rsp +MAP_CLOSE_req" --> Null4([Null]) + +``` + +Flowchart for process Cancel\_Location\_VLR. It starts with an initial node, followed by 'Null', then 'Receive Open\_Ind'. From 'Receive Open\_Ind', three paths emerge: 'Vr' leading to 'Perform MAP Vr dialogue' then 'Null'; 'OK' leading to 'Wait\_For\_Service\_Primitive'; and 'Error' leading to 'Null'. From 'Wait\_For\_Service\_Primitive', a 'MAP\_CANCEL\_LOCATION\_ind' signal is received, leading to 'Cancel Location', then 'Wait\_For\_Application\_Response'. From 'Wait\_For\_Application\_Response', two paths emerge: 'Cancel Location ack' leading to 'Set Result', and 'Cancel Location negative response' leading to 'Set User Error'. Both 'Set Result' and 'Set User Error' lead to a merge point, which then leads to a 'MAP\_CANCEL\_LOCATION\_rsp' / 'MAP\_CLOSE\_req' signal, and finally to 'Null'. + +1213 + +1214 + +**Figure 19.1.2/7: Process Cancel\_Location\_VLR** + +![Flowchart for process Cancel_Location_SGSN. It starts with an initial node, followed by 'Null', 'Receive Open_Ind', 'Wait_For_Service_Primitive', a decision point for 'MAP_CANCEL_LOCATION_ind', 'Check_Indication', 'Subscriber registered?' decision, 'Delete subscriber record', 'Release P-TMSI', a merge point for 'MAP_CANCEL_LOCATION_rsp' and 'MAP_CLOSE_req', and finally 'Null'.](4e3b813e7d14508be44d187387c824d5_img.jpg) + +**process Cancel\_Location\_SGSN** **CGL\_SGSN1(1)** + +Process in the SGSN to handle a Cancel Location request + +Signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> RecOpen[Receive Open_Ind] + RecOpen -- OK --> WaitFor[Wait_For_Service_Primitive] + RecOpen -- "Vr, Error" --> Null2([Null]) + WaitFor --> Merge1(( )) + Merge1 --> MAP_CANCEL_LOCATION_ind{MAP_CANCEL_LOCATION_ind} + MAP_CANCEL_LOCATION_ind --> CheckInd[Check_Indication] + CheckInd -- OK --> SubReg{Subscriber registered?} + CheckInd -- Error --> ReleaseP[Release P-TMSI] + SubReg -- No --> ReleaseP + SubReg -- Yes --> DeleteSub[Delete subscriber record] + DeleteSub --> ReleaseP + ReleaseP --> Merge2(( )) + Merge2 -- "MAP_CANCEL_LOCATION_rsp +MAP_CLOSE_req" --> Null3([Null]) + MAP_CANCEL_LOCATION_ind --> MAP_NOTICE_ind[/MAP NOTICE_ind/] + MAP_NOTICE_ind --> MAP_CLOSE_req[/MAP CLOSE_req/] + MAP_CLOSE_req --> Null4([Null]) + Merge1 --> MAP_P_ABORT_ind[/MAP_P_ABORT_ind/] + MAP_P_ABORT_ind --> Null5([Null]) + +``` + +Flowchart for process Cancel\_Location\_SGSN. It starts with an initial node, followed by 'Null', 'Receive Open\_Ind', 'Wait\_For\_Service\_Primitive', a decision point for 'MAP\_CANCEL\_LOCATION\_ind', 'Check\_Indication', 'Subscriber registered?' decision, 'Delete subscriber record', 'Release P-TMSI', a merge point for 'MAP\_CANCEL\_LOCATION\_rsp' and 'MAP\_CLOSE\_req', and finally 'Null'. + +1215 + +1216 + +**Figure 19.1.2/8: Process Cancel\_Location\_SGSN** + +1217 **19.1.2A Location Cancellation for VCSG** + +1218 **19.1.2A.1 General** + +1219 Location cancellation for VCSG is used to delete a subscriber record from the serving node (VLR or SGSN). The +1220 procedure is invoked: + +- 1221 - because there is a removal of the CSG subscription data in the CSS and of the MS registration +- 1222 - because the CSS has decided to cancel the registration of the MS which does not have CSG subscription data in +- 1223 the CSS. + +1224 NOTE: How the CSS determines when to cancel the registration of the MS is implementation dependent. + +1225 The message flow for VCSG location cancellation for a subscriber is shown in figure 19.1.2A/1. + +![Sequence diagram showing message flow between CSS and VLR/SGSN. Step 1: CSS sends a request to VLR/SGSN. Step 2: VLR/SGSN sends a response back to CSS.](cc3a36cfa986a92dcc94840351e1c36c_img.jpg) + +``` + +sequenceDiagram + participant CSS + participant VLR_SGSN as VLR/SGSN + Note right of VLR_SGSN: 1 + CSS->>VLR_SGSN: Request + Note left of CSS: 2 + VLR_SGSN-->>CSS: Response + +``` + +Sequence diagram showing message flow between CSS and VLR/SGSN. Step 1: CSS sends a request to VLR/SGSN. Step 2: VLR/SGSN sends a response back to CSS. + +1226 + +1227 + +1228 1) MAP\_CANCEL\_VCSG\_LOCATION\_req/ind + +1229 2) MAP\_CANCEL\_VCSG\_LOCATION\_rsp/cnf + +1230 + +1231 + +1232 + +**Figure 19.1.2A/1: Message flow for VCSG Location Cancellation** + +1233 **19.1.2A.2 Procedure in the CSS** + +1234 The MAP process in the CSS to cancel the VCSG location information in a VLR is shown in figure 19.1.2A/2. The +1235 MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +1236 Receive\_Open\_Cnf see clause 25.1.2; + +1237 Check\_Confirmation see clause 25.2.2. + +1238 The MAP process in the CSS to cancel the VCSG location information in a SGSN is shown in figure 19.1.2A/3. The +1239 MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +1240 Receive\_Open\_Cnf see clause 25.1.2; + +1241 Check\_Confirmation see clause 25.2.2. + +1242 + +1243 **19.1.2A.3 Procedure in the VLR** + +1244 The MAP process in the VLR to handle a VCSG location cancellation request is shown in figure 19.1.2A/4. The MAP +1245 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1246 Receive\_Open\_Ind see clause 25.1.1. + +1247 **19.1.2A.4 Procedure in the SGSN** + +1248 The MAP process in the SGSN to handle a VCSG location cancellation request is shown in figure 19.1.2A/5. The MAP +1249 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1250    Receive\_Open\_Ind    see clause 25.1.1. + +1251 + +# process Cancel\_VCSG\_Location\_CSS + +Process in the CSS to cancel the information stored in a VLR or SGSN + +Signals to are to/from signals to are to/from management process in 3GPP TS TS 23.060 + +![Flowchart for process Cancel_VCSG_Location_CSS. It starts with an initial state leading to 'Null', then 'Cancel VCSG Location'. A decision diamond shows incoming signals: MAP_OPEN_req, MAP_CANCEL_VCSG_LOCATION_req, and MAP_DELIMITER_req. It then goes to 'Receive_Open_Cnf'. From there, a 'Vr' path leads to 'Perform MAP Vr dialogue' and then 'Null'. An 'OK' path leads to 'Wait_For_VLR_Response'. From this wait state, three options are available: 'MAP_P_ABORT_ind' leading to 'Abort' and then 'Null'; 'MAP_CANCEL_VCSG_LOCATION_cnf' leading to 'Check Confirmation'; and 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req'. The 'Check Confirmation' state has three outcomes: 'Provider Error, Data Error' leading to 'Set negative response: System failure' and then 'Cancel VCSG Location negative response'; 'OK' leading to 'Cancel VCSG Location ack'; and 'User Error' leading to 'Set negative response' and then 'Cancel VCSG Location negative response'.](e43b059d4c242c9ff54eb0d7faf4eca5_img.jpg) + +``` + +graph TD + Start(( )) --> Null1[Null] + Null1 --> CancelLoc[Cancel VCSG Location] + CancelLoc --> InMsg{ } + InMsg --- InMsgText["MAP_OPEN_req +MAP_CANCEL_VCSG_LOCATION_req +MAP_DELIMITER_req"] + InMsg --> RecOpenCnf[Receive_Open_Cnf] + RecOpenCnf -- Vr --> PerformVr[Perform MAP Vr dialogue] + PerformVr --> Null2[Null] + RecOpenCnf -- OK --> WaitVLR[Wait_For_VLR_Response] + WaitVLR --> MAP_P_ABORT_ind{MAP_P_ABORT_ind} + WaitVLR --> MAP_CANCEL_VCSG_cnf{MAP_CANCEL_VCSG_LOCATION_cnf} + WaitVLR --> MAP_NOTICE_ind{MAP_NOTICE_ind} + MAP_P_ABORT_ind --> Abort[Abort] + Abort --> Null3[Null] + MAP_CANCEL_VCSG_cnf --> CheckConf[Check Confirmation] + CheckConf -- "Provider Error, Data Error" --> SetNegSys[Set negative response: System failure] + SetNegSys --> NegResp1[Cancel VCSG Location negative response] + CheckConf -- OK --> Ack[Cancel VCSG Location ack] + CheckConf -- User Error --> SetNegUser[Set negative response] + SetNegUser --> NegResp2[Cancel VCSG Location negative response] + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + +``` + +Flowchart for process Cancel\_VCSG\_Location\_CSS. It starts with an initial state leading to 'Null', then 'Cancel VCSG Location'. A decision diamond shows incoming signals: MAP\_OPEN\_req, MAP\_CANCEL\_VCSG\_LOCATION\_req, and MAP\_DELIMITER\_req. It then goes to 'Receive\_Open\_Cnf'. From there, a 'Vr' path leads to 'Perform MAP Vr dialogue' and then 'Null'. An 'OK' path leads to 'Wait\_For\_VLR\_Response'. From this wait state, three options are available: 'MAP\_P\_ABORT\_ind' leading to 'Abort' and then 'Null'; 'MAP\_CANCEL\_VCSG\_LOCATION\_cnf' leading to 'Check Confirmation'; and 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req'. The 'Check Confirmation' state has three outcomes: 'Provider Error, Data Error' leading to 'Set negative response: System failure' and then 'Cancel VCSG Location negative response'; 'OK' leading to 'Cancel VCSG Location ack'; and 'User Error' leading to 'Set negative response' and then 'Cancel VCSG Location negative response'. + +1252 +1253 + +**Figure 19.1.2A/2: Process Cancel\_VCSG\_Location\_CSS** + +![Flowchart for process Cancel_VCSG_Location_VLR. It starts with an initial node, followed by 'Null', then 'Receive_Open_Ind'. From 'Receive_Open_Ind', three paths emerge: 'Vr' leading to 'Perfor MAP Vr dialogue' -> 'Null'; 'OK' leading to 'Wait_For_Service_Primitive' -> 'Cancel VCSG Location' -> 'Wait_For_Application_Response'; and 'Error' leading to 'Null'. 'Wait_For_Application_Response' branches into 'Cancel VCSG Location ack' -> 'Set Result' and 'Cancel VCSG Location negative response' -> 'Set User Error'. Both 'Set Result' and 'Set User Error' lead to a merge point, which then leads to 'MAP_CANCEL_LOCATION_rsp MAP_CLOSE_req' -> 'Null'. There are also intermediate signals: 'MAP NOTICE_in' -> 'MAP CLOSE_req' -> 'Null' from the 'Vr' path; 'MAP_CANCEL_VCSG_LOCATION_ind' from the 'OK' path; and 'MAP_P_ABORT_in' -> 'Null' from the 'Error' path.](e114d1c9df1ab13459f56ec96de1c1b4_img.jpg) + +**process Cancel\_VCSG\_Location\_VLR** **CVL\_VLR1(1)** + +Process in the VLR to handle a Cancel VCSG Location request + +Signals to/from the left are to/from the location management application process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/from the CSS + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind -- Vr --> Perfor[Perfor MAP Vr dialogue] + Perfor --> Null2([Null]) + Receive_Open_Ind -- OK --> Wait_Service[Wait_For_Service_Primitive] + Wait_Service --> Cancel_VCSG[Cancel VCSG Location] + Cancel_VCSG --> Wait_App[Wait_For_Application_Response] + Wait_App --> Ack[Cancel VCSG Location ack] + Wait_App --> Neg[Cancel VCSG Location negative response] + Ack --> Set_Result[Set Result] + Neg --> Set_User_Error[Set User Error] + Set_Result --> Merge(( )) + Set_User_Error --> Merge + Merge --> MAP_Rsp[MAP_CANCEL_LOCATION_rsp +MAP_CLOSE_req] + MAP_Rsp --> Null3([Null]) + Receive_Open_Ind -- Error --> Null4([Null]) + Null4 --> MAP_P_ABORT[MAP_P_ABORT_in] + MAP_P_ABORT --> Null5([Null]) + Perfor --> MAP_NOTICE[MAP NOTICE_in] + MAP_NOTICE --> MAP_CLOSE[MAP CLOSE_req] + MAP_CLOSE --> Null6([Null]) + Wait_Service --> MAP_CANCEL_IND[MAP_CANCEL_VCSG_LOCATION_ind] + +``` + +Flowchart for process Cancel\_VCSG\_Location\_VLR. It starts with an initial node, followed by 'Null', then 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', three paths emerge: 'Vr' leading to 'Perfor MAP Vr dialogue' -> 'Null'; 'OK' leading to 'Wait\_For\_Service\_Primitive' -> 'Cancel VCSG Location' -> 'Wait\_For\_Application\_Response'; and 'Error' leading to 'Null'. 'Wait\_For\_Application\_Response' branches into 'Cancel VCSG Location ack' -> 'Set Result' and 'Cancel VCSG Location negative response' -> 'Set User Error'. Both 'Set Result' and 'Set User Error' lead to a merge point, which then leads to 'MAP\_CANCEL\_LOCATION\_rsp MAP\_CLOSE\_req' -> 'Null'. There are also intermediate signals: 'MAP NOTICE\_in' -> 'MAP CLOSE\_req' -> 'Null' from the 'Vr' path; 'MAP\_CANCEL\_VCSG\_LOCATION\_ind' from the 'OK' path; and 'MAP\_P\_ABORT\_in' -> 'Null' from the 'Error' path. + +1254 + +1255 + +**Figure 19.1.2A/3: Process Cancel\_VCSG\_Location\_VLR** + +![Flowchart for process Cancel_VCSG_Location_SGSN. It starts with an initial node leading to 'Null', then 'Receive_Open_Ind'. From 'Receive_Open_Ind', an 'OK' path leads to 'Wait_For_Service_Primitive' and a 'Vr, Error' path leads to 'Null'. 'Wait_For_Service_Primitive' leads to a junction. From the junction, three paths emerge: 'MAP_NOTICE_in' leading to 'MAP_CLOSE_req' then 'Null'; 'MAP_CANCEL_VCSG_LOCATION_ind' leading to 'Check_Indication'; and 'MAP_P_ABORT_in' leading to 'Null'. 'Check_Indication' leads to a decision 'Subscriber registered?'. If 'Yes', it leads to 'Delete the CSS Record and CSG Subscription data', which then leads to a junction. If 'No', it also leads to this junction. From this junction, an 'Error' path leads to another junction, and an 'OK' path leads to a junction with 'MAP_CANCEL_VCSG_LOCATION_rsp' and 'MAP_CLOSE_req'. All three junctions lead to the final 'Null' node.](ca9c21b01f6bef8651e2f6d0c4d2e882_img.jpg) + +**process Cancel\_VCSG\_Location\_SGSN** **CVL\_SGSN1(1)** + +Process in the SGSN to handle a Cancel VCSG Location request + +Signals to/from the right are to/from the CSS + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind -- OK --> Wait_For_Service_Primitive([Wait_For_Service_Primitive]) + Receive_Open_Ind -- "Vr, Error" --> Null2([Null]) + Wait_For_Service_Primitive --> Junction1(( )) + Junction1 -- "MAP_NOTICE_in" --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> Null3([Null]) + Junction1 -- "MAP_CANCEL_VCSG_LOCATION_ind" --> Check_Indication[Check_Indication] + Junction1 -- "MAP_P_ABORT_in" --> Null4([Null]) + Check_Indication --> Subscriber_registered{Subscriber registered?} + Subscriber_registered -- Yes --> Delete_CSS[Delete the CSS Record and CSG Subscription data] + Subscriber_registered -- No --> Junction2(( )) + Delete_CSS --> Junction2 + Junction2 -- Error --> Junction3(( )) + Junction2 -- OK --> Junction4(( )) + Junction4 -- "MAP_CANCEL_VCSG_LOCATION_rsp" --> MAP_CANCEL_VCSG_LOCATION_rsp[MAP_CANCEL_VCSG_LOCATION_rsp] + Junction4 -- "MAP_CLOSE_req" --> MAP_CLOSE_req2[MAP_CLOSE_req] + Junction3 --> Null5([Null]) + Junction4 --> Null5 + +``` + +Flowchart for process Cancel\_VCSG\_Location\_SGSN. It starts with an initial node leading to 'Null', then 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', an 'OK' path leads to 'Wait\_For\_Service\_Primitive' and a 'Vr, Error' path leads to 'Null'. 'Wait\_For\_Service\_Primitive' leads to a junction. From the junction, three paths emerge: 'MAP\_NOTICE\_in' leading to 'MAP\_CLOSE\_req' then 'Null'; 'MAP\_CANCEL\_VCSG\_LOCATION\_ind' leading to 'Check\_Indication'; and 'MAP\_P\_ABORT\_in' leading to 'Null'. 'Check\_Indication' leads to a decision 'Subscriber registered?'. If 'Yes', it leads to 'Delete the CSS Record and CSG Subscription data', which then leads to a junction. If 'No', it also leads to this junction. From this junction, an 'Error' path leads to another junction, and an 'OK' path leads to a junction with 'MAP\_CANCEL\_VCSG\_LOCATION\_rsp' and 'MAP\_CLOSE\_req'. All three junctions lead to the final 'Null' node. + +1256 + +1257 + +**Figure 19.1.2A/4: Process Cancel\_VCSG\_Location\_SGSN** + +1258 + +1259 **19.1.3 Void** + +1260 **19.1.4 MS Purging** + +1261 **19.1.4.1 General** + +1262 O&M procedures in the VLR or SGSN can trigger MS purging either because of administrative action or because the +1263 MS has been inactive for an extended period. The O&M process in the VLR or in the SGSN should ensure that during +1264 the MS purging procedure any other attempt to access the MS record is blocked, to maintain consistency of data. + +1265 The message flow for a VLR to report MS purging to the HLR is shown in figure 19.1.4/1. + +1266 The message flow for an SGSN to report MS purging to the HLR is shown in figure 19.1.4/2. + +![Sequence diagram for VLR to HLR MS purging. The VLR sends a message (1) to the HLR, and the HLR responds with a message (2) back to the VLR.](22f129958642affe06cd9285c2a16dde_img.jpg) + +``` +sequenceDiagram + participant VLR + participant HLR + Note right of HLR: 1 + VLR->>HLR: + Note left of VLR: 2 + HLR->>VLR: +``` + +Sequence diagram for VLR to HLR MS purging. The VLR sends a message (1) to the HLR, and the HLR responds with a message (2) back to the VLR. + +1267 + +1268 + +- 1269 1) MAP\_PURGE\_MS\_req/ind +- 1270 2) MAP\_PURGE\_MS\_rsp/cnf + +1271 + +1272 + +**Figure 19.1.4/1: Message flow for MS purging (non-GPRS)** + +1273 + +![Sequence diagram for SGSN to HLR MS purging. The SGSN sends a message (1) to the HLR, and the HLR responds with a message (2) back to the SGSN.](118206423180cf0f363dbd0ddbdd569e_img.jpg) + +``` +sequenceDiagram + participant SGSN + participant HLR + Note right of HLR: 1 + SGSN->>HLR: + Note left of SGSN: 2 + HLR->>SGSN: +``` + +Sequence diagram for SGSN to HLR MS purging. The SGSN sends a message (1) to the HLR, and the HLR responds with a message (2) back to the SGSN. + +1274 + +1275 + +- 1276 1) MAP\_PURGE\_MS\_req/ind +- 1277 2) MAP\_PURGE\_MS\_rsp/cnf + +1278 + +1279 + +**Figure 19.1.4/2: Message flow for MS purging (GPRS)** + +1280 **19.1.4.2 Procedure in the VLR** + +1281 The MAP process in the VLR to report MS purging to the HLR is shown in figure 19.1.4/3. The MAP process invokes +1282 macros not defined in this clause; the definitions of these macros can be found as follows: + +- 1283 Receive\_Open\_Cnf see clause 25.1.2; +- 1284 Check\_Confirmation see clause 25.2.2. + +1285 **19.1.4.3 Procedure in the SGSN** + +1286 The MAP process in the SGSN to report MS purging to the HLR is shown in figure 19.1.4/4. The MAP process invokes +1287 macros not defined in this clause; the definitions of these macros can be found as follows: + +- 1288 Receive\_Open\_Cnf see clause 25.1.2; +- 1289 Check\_Confirmation see clause 25.2.2. + +1290 Sheet 1: The procedure Purge\_MS\_In\_Serving\_Network\_Entity is specific to Super-Charger; it is specified in 3GPP +1291 TS 23.116 [110]. If the HLR does not support the Super-Charger functionality, processing continues from the "No" exit +1292 of the test "Result=Pass?". + +#### 1293 19.1.4.4 Procedure in the HLR + +1294 The MAP process in the HLR to handle a notification from a VLR or an SGSN that an MS record has been purged is +1295 shown in figure 19.1.4/5. The MAP process invokes macros not defined in this clause; the definitions of these macros +1296 can be found as follows: + +1297     Receive\_Open\_Ind     see clause 25.1.1; + +1298     Check\_Indication     see clause 25.2.1. + +1299 If the notification was received from a VLR, the MAP process communicates with the location management application +1300 process specified in 3GPP TS 23.012 [23]; if the notification was received from an SGSN, the MAP process +1301 communicates with the GPRS mobility management application process specified in 3GPP TS 23.060 [104]. + +1302 + +![Flowchart for process Purge_MS_VLR. The process starts with an oval, followed by a 'Null' oval, then a 'Purge MS' process block. It then enters a loop: a merge node receives 'MAP_OPEN_req', 'MAP_PURGE_MS_req', and 'MAP_DELIMITER_req'; followed by 'Receive_Open_Cnf'. A decision node branches on 'Vr' (left) to 'Perform MAP Vr dialogue' and 'Null', and on 'OK' (right) to 'Wait_For_HLR_Response'. From 'Wait_For_HLR_Response', three paths emerge: 'MAP_PURGE_MS_cnf' leads to 'Check_Confirmation', which branches on 'OK' (left) to 'Purge MS ack' and 'Null', 'User Error' (middle) to 'Set negative response' and then 'Purge MS negative response' and 'Null', and 'Provider Error, Data Error' (right) to 'Set negative response: System failure' and then 'Purge MS negative response' and 'Null'; 'MAP_P_ABORT_ind' and 'MAP_NOTICE_ind' both lead to 'MAP_CLOSE_req', which then leads to a 'Set negative response: System failure' block and 'Purge MS negative response' and 'Null'; an 'Error' path from the decision node also leads to 'Set negative response: System failure' and 'Purge MS negative response' and 'Null'.](a168167bf5e95524ddc74df99b4a977f_img.jpg) + +**process Purge\_MS\_VLR** **PMS\_VLR1(1)** + +Process in the VLR to report purging to the HLR + +Signals to/from the left are to/from the location management application process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/from the HLR + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> PurgeMS[Purge MS] + PurgeMS --> Merge{ } + Merge -- "MAP_OPEN_req +MAP_PURGE_MS_req +MAP_DELIMITER_req" --> RecvCnf[Receive_Open_Cnf] + RecvCnf --> Decision{ } + Decision -- Vr --> PerformVr[Perform MAP Vr dialogue] + PerformVr --> Null2([Null]) + Decision -- OK --> WaitForHLR[Wait_For_HLR_Response] + WaitForHLR --> MapPurgeCnf[MAP_PURGE_MS_cnf] + MapPurgeCnf --> CheckConfirm[Check_Confirmation] + CheckConfirm -- OK --> PurgeMSAck{Purge MS ack} + PurgeMSAck --> Null3([Null]) + CheckConfirm -- User Error --> SetNegResp[Set negative response] + SetNegResp --> PurgeMSNegResp1{Purge MS negative response} + PurgeMSNegResp1 --> Null4([Null]) + CheckConfirm -- "Provider Error, +Data Error" --> SetNegRespSysFail1[Set negative response: System failure] + SetNegRespSysFail1 --> PurgeMSNegResp2{Purge MS negative response} + PurgeMSNegResp2 --> Null5([Null]) + WaitForHLR --> MapPAbortInd[MAP_P_ABORT_ind] + MapPAbortInd --> MapCloseReq[MAP_CLOSE_req] + MapCloseReq --> SetNegRespSysFail2[Set negative response: System failure] + SetNegRespSysFail2 --> PurgeMSNegResp3{Purge MS negative response} + PurgeMSNegResp3 --> Null6([Null]) + WaitForHLR --> MapNoticeInd[MAP_NOTICE_ind] + MapNoticeInd --> MapCloseReq + Decision -- Error --> SetNegRespSysFail3[Set negative response: System failure] + SetNegRespSysFail3 --> PurgeMSNegResp4{Purge MS negative response} + PurgeMSNegResp4 --> Null7([Null]) + +``` + +Flowchart for process Purge\_MS\_VLR. The process starts with an oval, followed by a 'Null' oval, then a 'Purge MS' process block. It then enters a loop: a merge node receives 'MAP\_OPEN\_req', 'MAP\_PURGE\_MS\_req', and 'MAP\_DELIMITER\_req'; followed by 'Receive\_Open\_Cnf'. A decision node branches on 'Vr' (left) to 'Perform MAP Vr dialogue' and 'Null', and on 'OK' (right) to 'Wait\_For\_HLR\_Response'. From 'Wait\_For\_HLR\_Response', three paths emerge: 'MAP\_PURGE\_MS\_cnf' leads to 'Check\_Confirmation', which branches on 'OK' (left) to 'Purge MS ack' and 'Null', 'User Error' (middle) to 'Set negative response' and then 'Purge MS negative response' and 'Null', and 'Provider Error, Data Error' (right) to 'Set negative response: System failure' and then 'Purge MS negative response' and 'Null'; 'MAP\_P\_ABORT\_ind' and 'MAP\_NOTICE\_ind' both lead to 'MAP\_CLOSE\_req', which then leads to a 'Set negative response: System failure' block and 'Purge MS negative response' and 'Null'; an 'Error' path from the decision node also leads to 'Set negative response: System failure' and 'Purge MS negative response' and 'Null'. + +1303 + +1304 + +Figure 19.1.4/3: Process Purge\_MS\_VLR + +![Flowchart for process Purge_MS_SGSN. The process starts with 'Null', followed by 'OM_PURGE_MS_ind'. It then calls 'Purge_MS_In_Serving_Network_Entity' (referencing 3GPP TS 23.116). A decision 'Result=Pass?' follows. If 'Yes', it goes to connector '1'. If 'No', it sends 'MAP_OPEN_req', 'MAP_PURGE_MS_req', and 'MAP_DELIMITER_req', then 'Receive_Open_Cnf'. From 'Receive_Open_Cnf', an 'OK' path leads to 'Wait_For_HLR_Response', while a 'Vr. Error' path leads to 'Set User Error: System failure'. From 'Wait_For_HLR_Response', 'MAP_NOTICE_ind' and 'MAP_P_ABORT_ind' are received. Both lead to 'MAP_CLOSE_req', which then leads to 'Set User Error: System failure'. Finally, 'OM_PURGE_MS_rsp' is sent, and the process ends at 'Null'.](7ad4b768587dcc590d8228b2ee3c8e64_img.jpg) + +process Purge\_MS\_SGSN PMS\_SGSN1(2) + +Process in the SGSN to report purging to the HLR + +Signals to/from the left are to/from the O&M application in the SGSN; signals to/from the right are to/from the HLR + +``` + +graph TD + Start([Null]) --> OM_PURGE_MS_ind{OM_PURGE_MS_ind} + OM_PURGE_MS_ind --> Purge_MS_In_Serving_Network_Entity[Purge_MS_In_Serving_Network_Entity] + Purge_MS_In_Serving_Network_Entity -.-> Note1[See3GPP TS 23.116] + Purge_MS_In_Serving_Network_Entity --> Result_Pass{Result=Pass?} + Result_Pass -- Yes --> Connector1((1)) + Result_Pass -- No --> MAP_OPEN_req[MAP_OPEN_req +MAP_PURGE_MS_req +MAP_DELIMITER_req] + MAP_OPEN_req --> Receive_Open_Cnf[Receive_Open_Cnf] + Receive_Open_Cnf -- OK --> Wait_For_HLR_Response[Wait_For_HLR_Response] + Receive_Open_Cnf -- Vr. Error --> Set_User_Error[Set User Error: +System failure] + Wait_For_HLR_Response --> MAP_NOTICE_ind{MAP_NOTICE_ind} + Wait_For_HLR_Response --> MAP_P_ABORT_ind{MAP_P_ABORT_ind} + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_P_ABORT_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Set_User_Error + Set_User_Error --> OM_PURGE_MS_rsp{OM_PURGE_MS_rsp} + OM_PURGE_MS_rsp --> End([Null]) + +``` + +Flowchart for process Purge\_MS\_SGSN. The process starts with 'Null', followed by 'OM\_PURGE\_MS\_ind'. It then calls 'Purge\_MS\_In\_Serving\_Network\_Entity' (referencing 3GPP TS 23.116). A decision 'Result=Pass?' follows. If 'Yes', it goes to connector '1'. If 'No', it sends 'MAP\_OPEN\_req', 'MAP\_PURGE\_MS\_req', and 'MAP\_DELIMITER\_req', then 'Receive\_Open\_Cnf'. From 'Receive\_Open\_Cnf', an 'OK' path leads to 'Wait\_For\_HLR\_Response', while a 'Vr. Error' path leads to 'Set User Error: System failure'. From 'Wait\_For\_HLR\_Response', 'MAP\_NOTICE\_ind' and 'MAP\_P\_ABORT\_ind' are received. Both lead to 'MAP\_CLOSE\_req', which then leads to 'Set User Error: System failure'. Finally, 'OM\_PURGE\_MS\_rsp' is sent, and the process ends at 'Null'. + +1305 + +1306 + +Figure 19.1.4/4 (sheet 1 of 2): Process Purge\_MS\_SGSN + +![Flowchart for process Purge_MS_SGSN. It starts with 'Wait_For_HLR_Response', followed by 'MAP_PURGE_MS_cnf', 'Check_Confirmation', 'Delete subscriber data', 'Freeze P-TMSI?', 'Set Result', 'OM_PURGE_MS_rsp', and 'Null'. Error paths lead to 'Set User Error' or 'Set User Error: System failure'.](f134541214bf186a785a96cfd8b7325b_img.jpg) + +process Purge\_MS\_SGSN PMS\_SGSN2(2) + +Process in the SGSN to report purging to the HLR + +Signals to/from the left are to/from the O&M application in the SGSN; signals to/from the right are to/from the HLR + +``` + + graph TD + Start([Wait_For_HLR_Response]) --> MAP{MAP_PURGE_MS_cnf} + MAP --> Check[Check_Confirmation] + Check --> OK((1)) + OK --> Delete[Delete subscriber data] + Check --> UserError[Set User Error] + Check --> SystemFailure[Set User Error: System failure] + Delete --> Freeze{Freeze P-TMSI?} + Freeze -- No --> SetResult[Set Result] + Freeze -- Yes --> FreezeP[Freeze P-TMSI] + FreezeP --> SetResult + SetResult --> OM{OM_PURGE_MS_rsp} + OM --> Null([Null]) + +``` + +Flowchart for process Purge\_MS\_SGSN. It starts with 'Wait\_For\_HLR\_Response', followed by 'MAP\_PURGE\_MS\_cnf', 'Check\_Confirmation', 'Delete subscriber data', 'Freeze P-TMSI?', 'Set Result', 'OM\_PURGE\_MS\_rsp', and 'Null'. Error paths lead to 'Set User Error' or 'Set User Error: System failure'. + +1307 + +1308 + +Figure 19.1.4/4 (sheet 2 of 2): Process Purge\_MS\_SGSN + +![Flowchart for process Purge_MS_HLR. It starts with an initial state leading to 'Null', then 'Receive Open_Ind'. From 'Receive Open_Ind', three paths emerge: 'Vr' leading to 'Perform MAP Vr dialogue' then 'Null'; 'OK' leading to 'Wait_For_Service_Primitive'; and 'V1, Error' leading to 'Null'. From 'Wait_For_Service_Primitive', three paths emerge: 'MAP_P_ABORT_ind' leading to 'Null'; 'MAP_PURGE_MS_ind' leading to 'Purge MS' then 'Wait_For_Application_Response'; and 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req' then 'Null'. From 'Wait_For_Application_Response', two paths emerge: 'Purge MS ack' leading to 'Set Result'; and 'Purge MS negative response' leading to 'Set User Error'. Both 'Set Result' and 'Set User Error' lead to a merge point, which then leads to 'MAP_PURGE_MS_rsp / MAP_CLOSE_req' and finally 'Null'.](75f5e8a70ce294160298220122ac295b_img.jpg) + +**process Purge\_MS\_HLR** **PMS\_HLR1(1)** + +Process in the HLR to handle a notification from the VLR or the SGSN that an MS has been purged + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the location management application process in the HLR (see 3GPP TS 23.012) or the GPRS location management application process in the HLR (see 3GPP TS 23.060) + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> RecOpen[Receive Open_Ind] + RecOpen -- Vr --> PerformVr[Perform MAP Vr dialogue] + PerformVr --> Null2([Null]) + RecOpen -- OK --> WaitService[Wait_For_Service_Primitive] + RecOpen -- "V1, Error" --> Null3([Null]) + WaitService -- "MAP_P_ABORT_ind" --> Null4([Null]) + WaitService -- "MAP_PURGE_MS_ind" --> PurgeMS[Purge MS] + PurgeMS --> WaitApp[Wait_For_Application_Response] + WaitService -- "MAP_NOTICE_ind" --> MAPCloseReq{MAP_CLOSE_req} + MAPCloseReq --> Null5([Null]) + WaitApp -- "Purge MS ack" --> SetResult[Set Result] + WaitApp -- "Purge MS negative response" --> SetUserError[Set User Error] + SetResult --> Merge(( )) + SetUserError --> Merge + Merge -- "MAP_PURGE_MS_rsp / MAP_CLOSE_req" --> Null6([Null]) + +``` + +Flowchart for process Purge\_MS\_HLR. It starts with an initial state leading to 'Null', then 'Receive Open\_Ind'. From 'Receive Open\_Ind', three paths emerge: 'Vr' leading to 'Perform MAP Vr dialogue' then 'Null'; 'OK' leading to 'Wait\_For\_Service\_Primitive'; and 'V1, Error' leading to 'Null'. From 'Wait\_For\_Service\_Primitive', three paths emerge: 'MAP\_P\_ABORT\_ind' leading to 'Null'; 'MAP\_PURGE\_MS\_ind' leading to 'Purge MS' then 'Wait\_For\_Application\_Response'; and 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req' then 'Null'. From 'Wait\_For\_Application\_Response', two paths emerge: 'Purge MS ack' leading to 'Set Result'; and 'Purge MS negative response' leading to 'Set User Error'. Both 'Set Result' and 'Set User Error' lead to a merge point, which then leads to 'MAP\_PURGE\_MS\_rsp / MAP\_CLOSE\_req' and finally 'Null'. + +1309 + +1310 + +Figure 19.1.4/5: Process Purge\_MS\_HLR + +1311 **19.2 Handover procedures** + +1312 **19.2.1 General** + +1313 In this clause, the term "Inter- MSC handover" is used to denote handover or relocation between different MSCs. + +1314 The interfaces involved for Inter- MSC handover are shown in figure 19.2/1. There are two Inter- MSC handover +1315 procedures: + +1316 1) Basic Inter- MSC handover: + +1317 The call is handed over from the controlling MSC(MSC—A) to another MSC(MSC—B) (figure 19.2/1a). + +1318 Figure 19.2/2 shows the message flow for a successful handover from MSC-A to MSC—B, including a +1319 request for handover number allocation from MSC-B to VLR-B. + +1320 2) Subsequent Inter- MSC handover: + +1321 After the call has been handed over from MSC-A to MSC-B, a further handover either to MSC-A +1322 (figure 19.2/1a) or to a third MSC (MSC-B') (figure 19.2/1b) may be necessary in order to continue the call. + +1323 Figure 19.2/3 shows the message flow for a successful subsequent handover to MSC-B'. For a successful +1324 subsequent handover to MSC-A, the messages to and from MSC-B' and VLR-B' are omitted.. + +![Diagram showing the interface structure for basic handover procedure MSC-A to MSC-B. It consists of three boxes: MSC-A, MSC-B, and VLR-B. MSC-A is connected to MSC-B via an interface labeled 'E'. MSC-B is connected to VLR-B via an interface labeled 'B'.](9cf7132bdaf0943fa5595c89731c8ac0_img.jpg) + +1325 + +Diagram showing the interface structure for basic handover procedure MSC-A to MSC-B. It consists of three boxes: MSC-A, MSC-B, and VLR-B. MSC-A is connected to MSC-B via an interface labeled 'E'. MSC-B is connected to VLR-B via an interface labeled 'B'. + +1326 **a) Basic handover procedure MSC-A to MSC-B** +1327 **and subsequent handover procedure MSC-B to MSC-A.** + +![Diagram showing the interface structure for subsequent handover procedure MSC-B to MSC-B'. It consists of three boxes: MSC-A, MSC-B, and VLR-B in the top row, and MSC-B', VLR-B' in the bottom row. MSC-A is connected to MSC-B via interface 'E'. MSC-B is connected to VLR-B via interface 'B'. MSC-A is also connected to MSC-B' via interface 'E'. MSC-B' is connected to VLR-B' via interface 'B'.](44c56e7532e80e9f28c541da8e075d0e_img.jpg) + +1328 + +Diagram showing the interface structure for subsequent handover procedure MSC-B to MSC-B'. It consists of three boxes: MSC-A, MSC-B, and VLR-B in the top row, and MSC-B', VLR-B' in the bottom row. MSC-A is connected to MSC-B via interface 'E'. MSC-B is connected to VLR-B via interface 'B'. MSC-A is also connected to MSC-B' via interface 'E'. MSC-B' is connected to VLR-B' via interface 'B'. + +1329 **b) Subsequent handover procedure MSC-B to MSC-B'.** + +1330 **Figure 19.2/1: Interface structure for handover** + +![Sequence diagram showing a successful basic handover procedure to MSC-B. The diagram involves three lifelines: MSC-A, MSC-B, and VLR-B. The sequence of messages is: 1) MSC-A to MSC-B, 2) MSC-B to VLR-B, 3) VLR-B to MSC-B, 4) MSC-B to MSC-A, 5) MSC-B to VLR-B, 6) VLR-B to MSC-A, 7) MSC-A to MSC-B, 8) MSC-B to MSC-A, 9) MSC-A to MSC-B, 10) MSC-B to MSC-A.](29ec21437e0dff9d3f11718bca722b88_img.jpg) + +``` + +sequenceDiagram + participant MSC-A + participant MSC-B + participant VLR-B + Note left of MSC-A: + MSC-A->>MSC-B: 1) + MSC-B->>VLR-B: 2) + VLR-B->>MSC-B: 3) + MSC-B->>MSC-A: 4) + MSC-B->>VLR-B: 5) + VLR-B->>MSC-A: 6) + MSC-A->>MSC-B: 7) + MSC-B->>MSC-A: 8) + MSC-A->>MSC-B: 9) + MSC-B->>MSC-A: 10) + +``` + +Sequence diagram showing a successful basic handover procedure to MSC-B. The diagram involves three lifelines: MSC-A, MSC-B, and VLR-B. The sequence of messages is: 1) MSC-A to MSC-B, 2) MSC-B to VLR-B, 3) VLR-B to MSC-B, 4) MSC-B to MSC-A, 5) MSC-B to VLR-B, 6) VLR-B to MSC-A, 7) MSC-A to MSC-B, 8) MSC-B to MSC-A, 9) MSC-A to MSC-B, 10) MSC-B to MSC-A. + +1331 + 1332 + 1333 + 1334 + 1335 + 1336 + 1337 + 1338 + 1339 + 1340 + 1341 + 1342 + 1343 + 1344 + 1345 + 1346 + +- 1) MAP\_PREPARE\_HANDOVER\_req/ind +- 2) MAP\_ALLOCATE\_HANDOVER\_NUMBER\_req/ind +- 3) MAP\_SEND\_HANDOVER\_REPORT\_req/ind +- 4) MAP\_PREPARE\_HANDOVER\_rsp/cnf +- 5) MAP\_SEND\_HANDOVER\_REPORT\_rsp/cnf (Note) +- 6) MAP\_PROCESS\_ACCESS\_SIGNALLING\_req/ind +- 7) MAP\_SEND\_END\_SIGNAL\_req/ind +- 8) MAP\_FORWARD\_ACCESS\_SIGNALLING\_req/ind +- 9) MAP\_PROCESS\_ACCESS\_SIGNALLING\_req/ind +- 10) MAP\_SEND\_END\_SIGNAL\_rsp/cnf + +NOTE: This can be sent at any time after the connection between MSC-A and MSC-B is established. + +**Figure 19.2/2: Example of a successful basic handover procedure to MSC-B** + +![Sequence diagram showing a successful subsequent handover to a third MSC. Lifelines: MSC-A, MSC-B, VLR-B, MSC-B', VLR-B'. The sequence of messages is numbered 1 through 17. The process involves preparation, allocation, reporting, and processing of access signalling between the involved entities.](8ff35d11a04be22995ad783fca5d8dbe_img.jpg) + +``` + +sequenceDiagram + participant MSC-A + participant MSC-B + participant VLR-B + participant MSC-B' + participant VLR-B' + + Note left of MSC-A: 1) MAP_PREPARE_HANDOVER_req/ind + MSC-A->>MSC-B: 1) + Note right of MSC-B: 2) MAP_ALLOCATE_HANDOVER_NUMBER_req/ind + MSC-B->>VLR-B: 2) + Note right of VLR-B: 3) MAP_SEND_HANDOVER_REPORT_req/ind + VLR-B->>MSC-B: 3) + Note left of MSC-A: 4) MAP_PREPARE_HANDOVER_rsp/cnf + MSC-B->>MSC-A: 4) + Note right of VLR-B: 5) MAP_SEND_HANDOVER_REPORT_rsp/cnf (Note 1) + VLR-B->>MSC-B: 5) + Note left of MSC-A: 6) MAP_PROCESS_ACCESS_SIGNALLING_req/ind + MSC-A->>MSC-B: 6) + Note left of MSC-A: 7) MAP_SEND_END_SIGNAL_req/ind + MSC-A->>MSC-B: 7) + Note left of MSC-A: 8) MAP_PREPARE_SUBSEQUENT_HANDOVER_req/ind + MSC-A->>MSC-B: 8) + Note right of MSC-B: 9) MAP_PREPARE_HANDOVER_req/ind + MSC-B->>MSC-B': 9) + Note right of MSC-B': 10) MAP_ALLOCATE_HANDOVER_NUMBER_req/ind + MSC-B'->>VLR-B': 10) + Note right of VLR-B': 11) MAP_SEND_HANDOVER_REPORT_req/ind + VLR-B'->>MSC-B': 11) + Note left of MSC-A: 12) MAP_PREPARE_HANDOVER_rsp/cnf + MSC-B'->>MSC-A: 12) + Note right of VLR-B': 13) MAP_SEND_HANDOVER_REPORT_rsp/cnf (Note 2) + VLR-B'->>MSC-B': 13) + Note right of MSC-B': 14) MAP_PREPARE_SUBSEQUENT_HANDOVER_rsp/cnf + MSC-B'->>MSC-B: 14) + Note left of MSC-A: 15) MAP_PROCESS_ACCESS_SIGNALLING_req/ind + MSC-A->>MSC-B: 15) + Note left of MSC-A: 16) MAP_SEND_END_SIGNAL_req/ind + MSC-A->>MSC-B: 16) + Note left of MSC-A: 17) MAP_SEND_END_SIGNAL_rsp/cnf (Note 3) + MSC-B->>MSC-A: 17) + +``` + +Sequence diagram showing a successful subsequent handover to a third MSC. Lifelines: MSC-A, MSC-B, VLR-B, MSC-B', VLR-B'. The sequence of messages is numbered 1 through 17. The process involves preparation, allocation, reporting, and processing of access signalling between the involved entities. + +1347 + +1348 + +- 1349 1) MAP\_PREPARE\_HANDOVER\_req/ind +- 1350 2) MAP\_ALLOCATE\_HANDOVER\_NUMBER\_req/ind +- 1351 3) MAP\_SEND\_HANDOVER\_REPORT\_req/ind +- 1352 4) MAP\_PREPARE\_HANDOVER\_rsp/cnf +- 1353 5) MAP\_SEND\_HANDOVER\_REPORT\_rsp/cnf (Note 1) +- 1354 6) MAP\_PROCESS\_ACCESS\_SIGNALLING\_req/ind +- 1355 7) MAP\_SEND\_END\_SIGNAL\_req/ind +- 1356 8) MAP\_PREPARE\_SUBSEQUENT\_HANDOVER\_req/ind +- 1357 9) MAP\_PREPARE\_HANDOVER\_req/ind +- 1358 10) MAP\_ALLOCATE\_HANDOVER\_NUMBER\_req/ind +- 1359 11) MAP\_SEND\_HANDOVER\_REPORT\_req/ind +- 1360 12) MAP\_PREPARE\_HANDOVER\_rsp/cnf +- 1361 13) MAP\_SEND\_HANDOVER\_REPORT\_rsp/cnf (Note 2) +- 1362 14) MAP\_PREPARE\_SUBSEQUENT\_HANDOVER\_rsp/cnf +- 1363 15) MAP\_PROCESS\_ACCESS\_SIGNALLING\_req/ind +- 1364 16) MAP\_SEND\_END\_SIGNAL\_req/ind +- 1365 17) MAP\_SEND\_END\_SIGNAL\_rsp/cnf (Note 3) + +1366 + +NOTE 1: This can be sent at any time after the connection between MSC-A and MSC-B is established. + +1367 + +NOTE 2: This can be sent at any time after the connection between MSC-A and MSC-B' is established. + +1368 + +NOTE 3: At this stage, the subsequent handover is complete. Any further interworking between MSC-A and MSC-B' is the same as the interworking between MSC-A and MSC-B after basic handover + +1369 + +1370 + +1371 + +**Figure 19.2/3: Example of a successful subsequent handover to a third MSC** + +1373 The MAP signalling procedures for inter-MSC handover support the allocation of a handover number or one or more +1374 relocation numbers and the transfer of encapsulated BSSAP or RANAP messages. + +1375 The minimum application context version for the MAP handover application context shall be: + +- 1376 - version 3 for inter-MSC UTRAN to UTRAN handover; +- 1377 - version 3 for inter-MSC intersystem handover from GSM BSS to UTRAN; +- 1378 - version 2 for inter-MSC intersystem handover from UTRAN to GSM BSS. + +1379 NOTE: If the MAP handover application context version 2 is used, subsequent handover to UTRAN is not +1380 possible. + +1381 The minimum application context version for the MAP handover application context should be version 2 for inter-MSC +1382 handover from GSM BSS to GSM BSS. + +1383 NOTE: If the MAP handover application context version 2 or lower is used, subsequent handover to UTRAN is +1384 not possible. + +1385 The BSSAP or RANAP messages encapsulated in MAP messages are processed by the Handover Control Application +1386 in each MSC. The information in the encapsulated BSSAP or RANAP messages is passed from the Handover Control +1387 Application to the MAP process at the sending end; the notation used in the SDL diagrams for the MAP processes is +1388 "HO\_CA\_MESSAGE\_ind(Message transfer)". The information in the encapsulated BSSAP or RANAP messages is +1389 passed from the MAP process to the Handover Control Application at the sending end; the notation used in the SDL +1390 diagrams for the MAP processes is "HO\_CA\_MESSAGE\_req(Message transfer)". + +1391 For details of the interworking between the A-interface and MAP procedures or the Iu-interface and MAP procedures, +1392 see 3GPP TS 23.009 [21] and 3GPP TS 29.010 [58]. + +## 1393 19.2.2 Procedure in MSC-A + +1394 This clause describes the inter-MSC handover procedure in MSC-A; it covers basic inter-MSC handover to another +1395 MSC (MSC-B) and subsequent inter-MSC handover to a third MSC (MSC-B') or back to the controlling MSC +1396 (MSC-A). + +1397 The MAP process in MSC-A to handle inter-MSC handover is shown in figure 19.2/4. The MAP process invokes +1398 macros not defined in this clause; the definitions of these macros can be found as follows: + +- 1399 Receive\_Open\_Cnf see clause 25.1.2; +- 1400 Check\_Indication see clause 25.2.1. +- 1401 Check\_Confirmation see clause 25.2.2. + +1402 Communication between the MAP handover process and the Handover Control application is represented by the +1403 HO\_CA\_MESSAGE service. For a detailed description of the interworking between the Handover Control applications +1404 in different MSCs for the inter-MSC handover procedure, see 3GPP TS 23.009 [21]. + +### 1405 19.2.2.1 Basic handover + +1406 The handling in MSC-A for basic inter-MSC handover is shown in sheets 1 to 6 of figure 19.2/4. + +1407 Sheet 1: The MAP\_PREPARE\_HANDOVER request may contain: + +- 1408 - an indication that handover number allocation is not required; +- 1409 - the target Cell ID, for compatibility for handover to GSM; +- 1410 - the target RNC ID, for SRNS relocation or inter-system handover from GSM to UMTS; +- 1411 - the IMSI; +- 1412 - UMTS encryption information and UMTS integrity protection information, which are necessary for inter-system +1413 handover from GSM to UMTS; + +1414 - GSM radio resource information (channel type); + +1415 - the LCLS Global Call Reference; + +1416 - the LCLS-Negotiation; + +1417 - the LCLS-Configuration-Preference. + +1418 The conditions for the presence of these parameters and the processing in MSC-B (3G\_MSC-B) are described in detail +1419 in 3GPP TS 29.010 [58], 3GPP TS 23.009 [21] and 3GPP TS 29.205 [146]. + +1420 Sheet 2: The MAP\_PREPARE\_HANDOVER confirmation contains one of: + +1421 - no handover number, if the MAP\_PREPARE\_HANDOVER request included an indication that handover +1422 number allocation is not required; + +1423 - a handover number; + +1424 - one or more relocation numbers. + +1425 Sheet 2: The MAP\_PREPARE\_HANDOVER confirmation contains BSSAP or RANAP signalling information, which +1426 is passed to the Handover Control application in MSC-A. + +1427 Sheet 2: If the MAP\_PREPARE\_HANDOVER confirmation contains an indication that MSC-B does not support +1428 multiple bearers, the Handover Control application in MSC-A may request handover of one bearer to the same cell in +1429 MSC-B. + +1430 Sheet 5: If the original MAP\_PREPARE\_HANDOVER request included a parameter indicating that handover number +1431 allocation is not required, the Handover Control application in MSC-A may request a handover number (or one or more +1432 relocation numbers); this triggers a further MAP\_PREPARE\_HANDOVER request towards MSC-B. + +### 1433 19.2.2.2 Handling of access signalling + +1434 The Handover Control application in MSC-A may forward access signalling to any of the MS, RNS-B or BSS-B using +1435 the MAP\_FORWARD\_ACCESS\_SIGNALLING service; any of the MS, RNS-B or BSS-B may forward access +1436 signalling to the Handover Control application in MSC-A using the MAP\_PROCESS\_ACCESS\_SIGNALLING +1437 service. These are non-confirmed services. + +### 1438 19.2.2.3 Subsequent handover + +1439 The handling in MSC-A for subsequent inter-MSC handover is shown in sheets 7 & 8 of figure 19.2/4. If the Handover +1440 Control Application determines that the call is to be handed over to a third MSC (MSC-B') it triggers another instance +1441 of the MAP process to handle the basic handover to MSC-B', and reports the result of the subsequent handover to the +1442 instance of the MAP process which handles the dialogue with MSC-B. + +1443 Sheet 8: While the MAP process in MSC-A is waiting for the completion of subsequent handover, it relays access +1444 signalling between the Handover Control application and the MS, RNS-B or BSS-B as described in clause 19.2.2.2. + +## 1445 19.2.3 Procedure in MSC-B + +1446 This clause describes the handover or relocation procedure in MSC-B; it covers basic handover or relocation from the +1447 controlling MSC (MSC-A) and subsequent handover or relocation. + +1448 The MAP process in MSC-B to handle handover or relocation is shown in figure 19.2/5. The MAP process invokes +1449 macros not defined in this clause; the definitions of these macros can be found as follows: + +1450 Receive\_Open\_Ind see clause 25.1.1; + +1451 Receive\_Open\_Cnf see clause 25.1.2; + +1452 Check\_Indication see clause 25.2.1. + +1453 Check\_Confirmation see clause 25.2.2. + +1454 Communication between the MAP handover process and the Handover Control application is represented by the +1455 HO\_CA\_MESSAGE service. For a detailed description of the interworking between the Handover Control applications +1456 in different MSCs for the inter-MSC handover procedure, see 3GPP TS 23.009 [21]. + +1457 The ordering of allocation of handover number and radio resources shown in the SDL diagrams is not mandatory. + +### 1458 19.2.3.1 Basic handover + +1459 The handling in MSC-B for basic inter-MSC handover is shown in sheets 1 to 7 of figure 19.2/5. + +1460 Sheet 2: If the MAP\_PREPARE\_HANDOVER indication included a parameter requesting multiple bearers but MSC-B +1461 does not support multiple bearers, MSC-B sends a MAP\_PREPARE\_HANDOVER response indicating that multiple +1462 bearers are not supported, and waits for a possible MAP\_PREPARE\_HANDOVER indication requesting handover of a +1463 single bearer. + +1464 Sheet 6: If the original MAP\_PREPARE\_HANDOVER indication included a parameter indicating that handover +1465 number allocation is not required, MSC-A may send a further MAP\_PREPARE\_HANDOVER request to request the +1466 allocation of a handover number (or one or more relocation numbers). + +### 1467 19.2.3.2 Handling of access signalling + +1468 The Handover Control application in MSC-A may forward access signalling to any of the MS, RNS-B or BSS-B using +1469 the MAP\_FORWARD\_ACCESS\_SIGNALLING service; any of the MS, RNS-B or BSS-B may forward access +1470 signalling to the Handover Control application in MSC-A using the MAP\_PROCESS\_ACCESS\_SIGNALLING +1471 service. These are non-confirmed services. Signals to or from any of the MS, RNS-B or BSS-B are routed through the +1472 Handover Control application in MSC-B. + +### 1473 19.2.3.3 Subsequent handover + +1474 The handling in MSC-B for subsequent inter-MSC handover is shown in sheet 8 of figure 19.2/5. + +1475 While the MAP process in MSC-B is waiting for the completion of subsequent handover, it relays access signalling +1476 between MSC-A and the MS, RNS-B or BSS-B through the Handover Control application as described in clause +1477 19.2.3.2. + +## 1478 19.2.4 Macro Receive\_Error\_From\_HO\_CA + +1479 This macro is used by the handover processes in MSC-A and MSC-B to receive errors from the Handover Control +1480 Application at any state of a handover process. + +## 1481 19.2.5 Procedure in VLR-B + +1482 The process in VLR-B to handle a request for a handover number is shown in figure 19.2/7. The process invokes +1483 macros not defined in this clause; the definitions of these macros can be found as follows: + +1484     Receive\_Open\_Ind       see clause 25.1.1; + +1485     Check\_Indication       see clause 25.2.1. + +![State transition diagram for process HO_MSC_A. The process starts at an initial state, goes to 'Null', then receives an 'HO_CA_MESSAGE_ind (Handover Request)'. It then sends 'MAP_OPEN_req', 'MAP_PREPARE_HANDOVER_req', and 'MAP_DELIMITER_req', followed by 'Receive_Open_Cnf'. From 'Receive_Open_Cnf', three paths emerge: 'Error' leads to 'HO_CA_MESSAGE_req (MAP Error)' then 'Null'; 'OK' leads to 'Wait_For_Prepare_Handover_Result'; 'Vr' leads to 'Perform MAP Vr dialogue' then 'Null'. From 'Wait_For_Prepare_Handover_Result', four paths emerge: 1) 'HO_CA_MESSAGE_ind (Call Release)' then 'MAP_U_ABORT_req' then 'Null'; 2) 'MAP_CLOSE_ind' then 'HO_CA_MESSAGE_req (Connection Closed)' then 'Null'; 3) 'MAP_U_ABORT_ind, MAP_P_ABORT_ind' and 'MAP_NOTICE_ind' both lead to a common 'HO_CA_MESSAGE_req (MAP Error)' then 'Null'; 4) 'MAP_CLOSE_req' leads to a common 'HO_CA_MESSAGE_req (MAP Error)' then 'Null'.](49130613602e28504e722d05013e2040_img.jpg) + +**process Handover\_MSC\_A** **HO\_MSCA1(8)** + +Process in MSC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to MSC-A or to MSC-B' (the new Relay MSC) + +Signals to/from the left are to/from the Handover Control Application in MSC-A; signals to/from the right are to/from MSC-B + +``` + +stateDiagram-v2 + [*] --> Null1[Null] + Null1 --> HO_CA_MESSAGE_ind1[HO_CA_MESSAGE_ind (Handover Request)] + HO_CA_MESSAGE_ind1 --> MAP_OPEN_req[MAP_OPEN_req +MAP_PREPARE_HANDOVER_req +MAP_DELIMITER_req] + MAP_OPEN_req --> Receive_Open_Cnf[Receive_Open_Cnf] + Receive_Open_Cnf --> Error[Error] + Receive_Open_Cnf --> OK[OK] + Receive_Open_Cnf --> Vr[Vr] + Error --> HO_CA_MESSAGE_req1[HO_CA_MESSAGE_req (MAP Error)] + HO_CA_MESSAGE_req1 --> Null2[Null] + OK --> Wait_For_Prepare_Handover_Result[Wait_For_Prepare_Handover_Result] + Vr --> Perform_MAP_Vr_dialogue[Perform MAP Vr dialogue] + Perform_MAP_Vr_dialogue --> Null3[Null] + Wait_For_Prepare_Handover_Result --> HO_CA_MESSAGE_ind2[HO_CA_MESSAGE_ind (Call Release)] + Wait_For_Prepare_Handover_Result --> MAP_CLOSE_ind[MAP_CLOSE_ind] + Wait_For_Prepare_Handover_Result --> MAP_U_ABORT_ind[MAP_U_ABORT_ind, MAP_P_ABORT_ind] + Wait_For_Prepare_Handover_Result --> MAP_NOTICE_ind[MAP_NOTICE_ind] + HO_CA_MESSAGE_ind2 --> MAP_U_ABORT_req[MAP_U_ABORT_req] + MAP_U_ABORT_req --> Null4[Null] + MAP_CLOSE_ind --> HO_CA_MESSAGE_req2[HO_CA_MESSAGE_req (Connection Closed)] + HO_CA_MESSAGE_req2 --> Null5[Null] + MAP_U_ABORT_ind --> HO_CA_MESSAGE_req3[HO_CA_MESSAGE_req (MAP Error)] + MAP_NOTICE_ind --> HO_CA_MESSAGE_req3 + HO_CA_MESSAGE_req3 --> Null6[Null] + MAP_CLOSE_req[MAP_CLOSE_req] --> HO_CA_MESSAGE_req3 + HO_CA_MESSAGE_req3 --> Null6 + +``` + +State transition diagram for process HO\_MSC\_A. The process starts at an initial state, goes to 'Null', then receives an 'HO\_CA\_MESSAGE\_ind (Handover Request)'. It then sends 'MAP\_OPEN\_req', 'MAP\_PREPARE\_HANDOVER\_req', and 'MAP\_DELIMITER\_req', followed by 'Receive\_Open\_Cnf'. From 'Receive\_Open\_Cnf', three paths emerge: 'Error' leads to 'HO\_CA\_MESSAGE\_req (MAP Error)' then 'Null'; 'OK' leads to 'Wait\_For\_Prepare\_Handover\_Result'; 'Vr' leads to 'Perform MAP Vr dialogue' then 'Null'. From 'Wait\_For\_Prepare\_Handover\_Result', four paths emerge: 1) 'HO\_CA\_MESSAGE\_ind (Call Release)' then 'MAP\_U\_ABORT\_req' then 'Null'; 2) 'MAP\_CLOSE\_ind' then 'HO\_CA\_MESSAGE\_req (Connection Closed)' then 'Null'; 3) 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind' and 'MAP\_NOTICE\_ind' both lead to a common 'HO\_CA\_MESSAGE\_req (MAP Error)' then 'Null'; 4) 'MAP\_CLOSE\_req' leads to a common 'HO\_CA\_MESSAGE\_req (MAP Error)' then 'Null'. + +1486 + +1487 + +Figure 19.2/4 (sheet 1 of 8): Process HO\_MSC\_A + +![State transition diagram for process Handover_MSC_A. The process starts in 'Wait_For_Prepare_Handover_Result' state, transitions to 'MAP_PREPARE_HANDOVER_cnf' message, then to 'Check_Confirmation' state. From 'Check_Confirmation', three paths emerge: 'OK' leads to an unlabeled state then to 'HO_CA_MESSAGE_req (Prepare Handover Result)' message; 'Provider Error' leads directly to another unlabeled state then to 'HO_CA_MESSAGE_req (MAP Error)' message; 'User Error, Data Error' leads to 'MAP_U_ABORT_req' message. Both 'HO_CA_MESSAGE_req' messages lead to a decision diamond 'Multiple bearer not supported indication received?'. If 'No', it leads to 'Wait_For_HO_Completion_On_MSC_B' state, then to 'Receive_Error_From_HO_CA' state, which then leads to either 'Wait_For_HO_Completion_On_MSC_B' state (Error) or 'Null' state. If 'Yes', it leads to 'Wait_For_Resend' state, which then leads to an unlabeled state. From this state, two paths emerge: one to 'HO_CA_MESSAGE_ind (Handover Request)' message, then to another unlabeled state, then to 'MAP_PREPARE_HANDOVER_req MAP_DELIMITER_req' message, then to 'Wait_For_Prepare_Handover_Result' state; the other to 'HO_CA_MESSAGE_ind (Error)' message, then to 'MAP_U_ABORT_req' message, then to 'Null' state.](3d3c6241ebe0653d7cf2f2e4524e5f84_img.jpg) + +**process Handover\_MSC\_A** **HO\_MSCA2(8)** + +Process in MSC-A (the Anchor MSC) to handle inter- MSC handover to MSC-B (the Relay MSC) and subsequent handover back to MSC-A or to MSC-B' (the new Relay MSC) + +Signals to/from the left are to/from the Handover Control Application in MSC-A; signals to/from the right are to/from MSC-B + +``` + +stateDiagram-v2 + [*] --> Wait_For_Prepare_Handover_Result + Wait_For_Prepare_Handover_Result --> MAP_PREPARE_HANDOVER_cnf + MAP_PREPARE_HANDOVER_cnf --> Check_Confirmation + Check_Confirmation --> OK + Check_Confirmation --> Provider_Error: Provider Error + Check_Confirmation --> User_Error_Data_Error: User Error, Data Error + OK --> State_1 + State_1 --> HO_CA_MESSAGE_req_1: HO_CA_MESSAGE_req (Prepare Handover Result) + Provider_Error --> State_2 + State_2 --> HO_CA_MESSAGE_req_2: HO_CA_MESSAGE_req (MAP Error) + User_Error_Data_Error --> MAP_U_ABORT_req_1: MAP_U_ABORT_req + HO_CA_MESSAGE_req_1 --> Decision + HO_CA_MESSAGE_req_2 --> Null_1: Null + MAP_U_ABORT_req_1 --> Null_1 + Decision --> No + Decision --> Yes: Multiple bearer not supported indication received? + No --> Wait_For_HO_Completion_On_MSC_B_1: Wait_For_HO_Completion_On_MSC_B + Yes --> Wait_For_Resend + Wait_For_HO_Completion_On_MSC_B_1 --> Receive_Error_From_HO_CA + Receive_Error_From_HO_CA --> Wait_For_HO_Completion_On_MSC_B_2: Wait_For_HO_Completion_On_MSC_B (Error) + Receive_Error_From_HO_CA --> Null_2: Null + Wait_For_Resend --> State_3 + State_3 --> HO_CA_MESSAGE_ind_1: HO_CA_MESSAGE_ind (Handover Request) + State_3 --> HO_CA_MESSAGE_ind_2: HO_CA_MESSAGE_ind (Error) + HO_CA_MESSAGE_ind_1 --> State_4 + State_4 --> MAP_PREPARE_HANDOVER_req_MAP_DELIMITER_req: MAP_PREPARE_HANDOVER_req MAP_DELIMITER_req + MAP_PREPARE_HANDOVER_req_MAP_DELIMITER_req --> Wait_For_Prepare_Handover_Result + HO_CA_MESSAGE_ind_2 --> MAP_U_ABORT_req_2: MAP_U_ABORT_req + MAP_U_ABORT_req_2 --> Null_3: Null + +``` + +State transition diagram for process Handover\_MSC\_A. The process starts in 'Wait\_For\_Prepare\_Handover\_Result' state, transitions to 'MAP\_PREPARE\_HANDOVER\_cnf' message, then to 'Check\_Confirmation' state. From 'Check\_Confirmation', three paths emerge: 'OK' leads to an unlabeled state then to 'HO\_CA\_MESSAGE\_req (Prepare Handover Result)' message; 'Provider Error' leads directly to another unlabeled state then to 'HO\_CA\_MESSAGE\_req (MAP Error)' message; 'User Error, Data Error' leads to 'MAP\_U\_ABORT\_req' message. Both 'HO\_CA\_MESSAGE\_req' messages lead to a decision diamond 'Multiple bearer not supported indication received?'. If 'No', it leads to 'Wait\_For\_HO\_Completion\_On\_MSC\_B' state, then to 'Receive\_Error\_From\_HO\_CA' state, which then leads to either 'Wait\_For\_HO\_Completion\_On\_MSC\_B' state (Error) or 'Null' state. If 'Yes', it leads to 'Wait\_For\_Resend' state, which then leads to an unlabeled state. From this state, two paths emerge: one to 'HO\_CA\_MESSAGE\_ind (Handover Request)' message, then to another unlabeled state, then to 'MAP\_PREPARE\_HANDOVER\_req MAP\_DELIMITER\_req' message, then to 'Wait\_For\_Prepare\_Handover\_Result' state; the other to 'HO\_CA\_MESSAGE\_ind (Error)' message, then to 'MAP\_U\_ABORT\_req' message, then to 'Null' state. + +1488 + +1489 + +Figure 19.2/4 (sheet 2 of 8): Process HO\_MSC\_A + +![SDL state diagram for process HO_MSC_A showing transitions from Wait_For_HO_Completion_On_MSCB and Wait_For_HO_Completion_On_MSC_B states based on various MAP and HO_CA signals.](c13433e749e902dc29bddea7aedd49c7_img.jpg) + +process Handover\_MSC\_A +HO\_MSCA3(8) + +Process in MSC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to MSC-A or to MSC-B' (the new Relay MSC) + +Signals to/from the left are to/from the Handover Control Application in MSC-A; signals to/from the right are to/from MSC-B + +``` + + graph TD + %% Top Section + S1([Wait_For_HO_Completion_On_MSCB]) + + S1 --> I1[/HO_CA_MESSAGE_ind +(Message Transfer)/] + I1 --> O1[MAP_FORWARD_ACCESS_SIGNALLING_req +MAP_DELIMITER_req] + O1 --> S2([Wait_For_HO_Completion_On_MSC_B]) + + S1 --> I2[/MAP_SEND_END_SIGNAL_ind/] + I2 --> D1{Check_Indication} + D1 -- OK --> O2[HO_CA_MESSAGE_req +(Handover Complete)] + O2 --> O3[MS_On_MSCB] + O3 --> N1([Null]) + D1 -- Error --> O4[HO_CA_MESSAGE_req +(MAP Error)] + O4 --> O5[MAP_U_ABORT_req] + O5 --> N2([Null]) + + S1 --> I3[/MAP_PROCESS_ACCESS_SIGNALLING_ind/] + I3 --> D2{Check_Indication} + D2 -- Error --> S3([Wait_For_HO_Completion_On_MSC_B]) + D2 -- OK --> O6[HO_CA_MESSAGE_req +(Message Transfer)] + O6 --> S4([Wait_For_HO_Completion_On_MSC_B]) + + %% Bottom Section + S5([Wait_For_HO_Completion_On_MSC_B]) + + S5 --> I4[/MAP_CLOSE_req/] + I4 --> O7[HO_CA_MESSAGE_req +(Connection Closed)] + O7 --> N3([Null]) + + S5 --> I5[/MAP_U_ABORT_ind, +MAP_P_ABORT_ind/] + I5 --> O8[HO_CA_MESSAGE_req +(MAP Error)] + O8 --> N4([Null]) + + S5 --> I6[/MAP_NOTICE_ind/] + I6 --> O9[HO_CA_MESSAGE_req +(MAP Error)] + O9 --> S6([Wait_For_HO_Completion_On_MSC_B]) + +``` + +SDL state diagram for process HO\_MSC\_A showing transitions from Wait\_For\_HO\_Completion\_On\_MSCB and Wait\_For\_HO\_Completion\_On\_MSC\_B states based on various MAP and HO\_CA signals. + +1490 + +1491 + +**Figure 19.2/4 (sheet 3 of 8): Process HO\_MSC\_A** + +![State transition diagram for process HO_MSC_A. The diagram shows two main state transition paths starting from MS_On_MSC_B. The top path handles incoming HO_CA_MESSAGE_ind, MAP_FORWARD_ACCESS_SIGNALLING_req, and MAP_PROCESS_ACCESS_SIGNALLING_ind. The bottom path handles incoming MAP_CLOSE_req, MAP_U_ABORT_ind/MAP_P_ABORT_ind, and MAP_NOTICE_ind. Most transitions lead to Null or back to MS_On_MSC_B.](f6dc7fdc0c74e067766ad27976d76403_img.jpg) + +**process Handover\_MSC\_A** **HO\_MSCA4(8)** + +Process in MSC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to MSC-A or to MSC-B' (the new Relay MSC) + +Signals to/from the left are to/from the Handover Control Application in MSC-A; signals to/from the right are to/from MSC-B + +``` + +stateDiagram-v2 + [*] --> MS_On_MSC_B + state "MS_On_MSC_B" as MS_On_MSC_B + state "Null" as Null + + MS_On_MSC_B --> HO_CA_MESSAGE_ind (Message Transfer) + HO_CA_MESSAGE_ind --> MAP_FORWARD_ACCESS_SIGNALLING_req + MAP_FORWARD_ACCESS_SIGNALLING_req --> MS_On_MSC_B + + MS_On_MSC_B --> Receive_Error_From_HO_CA + Receive_Error_From_HO_CA --> MS_On_MSC_B : Error + Receive_Error_From_HO_CA --> Null : Null + Null --> MS_On_MSC_B : Error + Null --> MS_On_MSC_B : OK + + MS_On_MSC_B --> MAP_PROCESS_ACCESS_SIGNALLING_ind + MAP_PROCESS_ACCESS_SIGNALLING_ind --> Check_Indication + Check_Indication --> HO_CA_MESSAGE_req (Message Transfer) + HO_CA_MESSAGE_req --> MS_On_MSC_B + + MS_On_MSC_B --> MAP_CLOSE_req + MAP_CLOSE_req --> HO_CA_MESSAGE_req (Connection Closed) + HO_CA_MESSAGE_req --> Null + + MS_On_MSC_B --> MAP_U_ABORT_ind_MAP_P_ABORT_ind + MAP_U_ABORT_ind_MAP_P_ABORT_ind --> HO_CA_MESSAGE_req (MAP Error) + HO_CA_MESSAGE_req --> Null + + MS_On_MSC_B --> MAP_NOTICE_ind + MAP_NOTICE_ind --> HO_CA_MESSAGE_req (MAP Error) + HO_CA_MESSAGE_req --> MS_On_MSC_B + +``` + +State transition diagram for process HO\_MSC\_A. The diagram shows two main state transition paths starting from MS\_On\_MSC\_B. The top path handles incoming HO\_CA\_MESSAGE\_ind, MAP\_FORWARD\_ACCESS\_SIGNALLING\_req, and MAP\_PROCESS\_ACCESS\_SIGNALLING\_ind. The bottom path handles incoming MAP\_CLOSE\_req, MAP\_U\_ABORT\_ind/MAP\_P\_ABORT\_ind, and MAP\_NOTICE\_ind. Most transitions lead to Null or back to MS\_On\_MSC\_B. + +1492 + +1493 + +Figure 19.2/4 (sheet 4 of 8): Process HO\_MSC\_A + +![Flowchart for process Handover_MSC_A. It starts with MS_On_MSC_B. Two main paths emerge: one for HO_CA_MESSAGE_ind (Call Release) leading to MAP_SEND_END_SIGNAL_rsp and Null; the other for HO_CA_MESSAGE_ind (HO Number Required) leading to MAP_PREPARE_HANDOVER_req, Wait_For_HO_Number_From_MSC_B, MAP_PREPARE_HANDOVER_cnt, and Check_Confirmation. Check_Confirmation leads to OK, User Error/Data Error, or Provider Error. OK leads to a decision 'Handover number received?'. Yes leads to 'Set HO-number: present', No leads to 'Set HO-number: not present'. Both lead to HO_CA_MESSAGE_req (Routing information) and MS_On_MSC_B. User Error/Data Error leads to HO_CA_MESSAGE_req (MAP Error) and MS_On_MSC_B. Provider Error leads to HO_CA_MESSAGE_req (MAP Error) and Null.](2d1c5bc46086b7f59c21275beea4e683_img.jpg) + +**process Handover\_MSC\_A** **HO\_MSCA5(8)** + +Process in MSC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to MSC-A or to MSC-B' (the new Relay MSC) + +Signals to/from the left are to/from the Handover Control Application in MSC-A; signals to/from the right are to/from MSC-B + +``` + +graph TD + Start([MS_On_MSC_B]) --> In1{{ }} + In1 --> HO_CA_MESSAGE_ind1[HO_CA_MESSAGE_ind +(Call Release)] + In1 --> In2{{ }} + In2 --> HO_CA_MESSAGE_ind2[HO_CA_MESSAGE_ind +(HO Number Required)] + In2 --> MAP_PREPARE_HANDOVER_req[MAP_PREPARE_HANDOVER_req +MAP_DELIMITER_req] + MAP_PREPARE_HANDOVER_req --> Wait_For_HO_Number_From_MSC_B([Wait_For_HO_Number_From_MSC_B]) + Wait_For_HO_Number_From_MSC_B --> MAP_PREPARE_HANDOVER_cnt{{ }} + MAP_PREPARE_HANDOVER_cnt --> Check_Confirmation[Check_Confirmation] + Check_Confirmation --> OK{OK} + OK -- Yes --> Handover_number_received{Handover number received?} + OK -- No --> Set_HO_number_not_present[Set HO-number: +not present] + Handover_number_received -- Yes --> Set_HO_number_present[Set HO-number: +present] + Set_HO_number_present --> HO_CA_MESSAGE_req_routing[HO_CA_MESSAGE_req +(Routing information)] + Set_HO_number_not_present --> HO_CA_MESSAGE_req_routing + HO_CA_MESSAGE_req_routing --> MS_On_MSC_B2([MS_On_MSC_B]) + Check_Confirmation -- "User Error, Data Error" --> HO_CA_MESSAGE_req_error1[HO_CA_MESSAGE_req +(MAP Error)] + HO_CA_MESSAGE_req_error1 --> MS_On_MSC_B3([MS_On_MSC_B]) + Check_Confirmation -- "Provider Error" --> HO_CA_MESSAGE_req_error2[HO_CA_MESSAGE_req +(MAP Error)] + HO_CA_MESSAGE_req_error2 --> Null2([Null]) + In1 --> MAP_SEND_END_SIGNAL_rsp[MAP_SEND_END_SIGNAL_rsp +MAP_CLOSE_req] + MAP_SEND_END_SIGNAL_rsp --> Null1([Null]) + +``` + +Flowchart for process Handover\_MSC\_A. It starts with MS\_On\_MSC\_B. Two main paths emerge: one for HO\_CA\_MESSAGE\_ind (Call Release) leading to MAP\_SEND\_END\_SIGNAL\_rsp and Null; the other for HO\_CA\_MESSAGE\_ind (HO Number Required) leading to MAP\_PREPARE\_HANDOVER\_req, Wait\_For\_HO\_Number\_From\_MSC\_B, MAP\_PREPARE\_HANDOVER\_cnt, and Check\_Confirmation. Check\_Confirmation leads to OK, User Error/Data Error, or Provider Error. OK leads to a decision 'Handover number received?'. Yes leads to 'Set HO-number: present', No leads to 'Set HO-number: not present'. Both lead to HO\_CA\_MESSAGE\_req (Routing information) and MS\_On\_MSC\_B. User Error/Data Error leads to HO\_CA\_MESSAGE\_req (MAP Error) and MS\_On\_MSC\_B. Provider Error leads to HO\_CA\_MESSAGE\_req (MAP Error) and Null. + +1494 + +1495 + +Figure 19.2/4 (sheet 5 of 8): Process HO\_MSC\_A + +![State transition diagram for process Handover_MSC_A. The diagram shows three main paths from an initial 'Wait_For_HO_Number_From_MSC_B' state. Path 1: MAP_CLOSE_req leads to HO_CA_MESSAGE_req (Connection Closed) and then to a Null state. Path 2: MAP_U_ABORT_ind, MAP_P_ABORT_ind leads to HO_CA_MESSAGE_req (MAP Error) and then to a Null state. Path 3: MAP_NOTICE_ind leads to HO_CA_MESSAGE_req (MAP Error) and then to another Wait_For_HO_Number_From_MSC_B state. From this second wait state, a 'Receive_Error_From_HO_CA' event leads to either a Null state (if Null) or back to the initial Wait_For_HO_Number_From_MSC_B state (if Error).](18b107026de7da3bcd10d73dfa8cd527_img.jpg) + +**process Handover\_MSC\_A** **HO\_MSCA6(8)** + +Process in MSC-A (the Anchor MSC) to handle inter- MSC handover to MSC-B (the Relay MSC) and subsequent handover back to MSC-A or to MSC-B' (the new Relay MSC) + +Signals to/from the left are to/from the Handover Control Application in MSC-A; signals to/from the right are to/from MSC-B + +``` + +stateDiagram-v2 + [*] --> Wait_For_HO_Number_From_MSC_B + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind" as MAP_U_ABORT_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "HO_CA_MESSAGE_req (Connection Closed)" as HO_CA_MESSAGE_req_1 + state "HO_CA_MESSAGE_req (MAP Error)" as HO_CA_MESSAGE_req_2 + state "Null" as Null_1 + state "Null" as Null_2 + state "Wait_For_HO_Number_From_MSC_B" as Wait_For_HO_Number_From_MSC_B_2 + state "Receive_Error_From_HO_CA" as Receive_Error_From_HO_CA + state "Null" as Null_3 + state "Wait_For_HO_Number_From_MSC_B" as Wait_For_HO_Number_From_MSC_B_3 + + Wait_For_HO_Number_From_MSC_B --> MAP_CLOSE_req + Wait_For_HO_Number_From_MSC_B --> MAP_U_ABORT_ind + Wait_For_HO_Number_From_MSC_B --> MAP_NOTICE_ind + + MAP_CLOSE_req --> HO_CA_MESSAGE_req_1 + HO_CA_MESSAGE_req_1 --> Null_1 + + MAP_U_ABORT_ind --> HO_CA_MESSAGE_req_2 + HO_CA_MESSAGE_req_2 --> Null_2 + + MAP_NOTICE_ind --> HO_CA_MESSAGE_req_2 + HO_CA_MESSAGE_req_2 --> Wait_For_HO_Number_From_MSC_B_2 + + Wait_For_HO_Number_From_MSC_B_2 --> Receive_Error_From_HO_CA + + Receive_Error_From_HO_CA --> Null_3 : Null + Receive_Error_From_HO_CA --> Wait_For_HO_Number_From_MSC_B_3 : Error + +``` + +State transition diagram for process Handover\_MSC\_A. The diagram shows three main paths from an initial 'Wait\_For\_HO\_Number\_From\_MSC\_B' state. Path 1: MAP\_CLOSE\_req leads to HO\_CA\_MESSAGE\_req (Connection Closed) and then to a Null state. Path 2: MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind leads to HO\_CA\_MESSAGE\_req (MAP Error) and then to a Null state. Path 3: MAP\_NOTICE\_ind leads to HO\_CA\_MESSAGE\_req (MAP Error) and then to another Wait\_For\_HO\_Number\_From\_MSC\_B state. From this second wait state, a 'Receive\_Error\_From\_HO\_CA' event leads to either a Null state (if Null) or back to the initial Wait\_For\_HO\_Number\_From\_MSC\_B state (if Error). + +1496 + +1497 + +Figure 19.2/4 (sheet 6 of 8): Process HO\_MSC\_A + +![Flowchart for process Handover_MSC_A. It starts with MS_On_MSC_B, followed by MAP_PREPARE_SUBSEQUENT_HANDOVER_ind. A decision 'MSC known?' leads to 'Set User Error: Unknown MSC' if No, or 'HO_CA_MESSAGE_req (Handover Request)' if Yes. The 'Yes' path leads to 'Wait_For_Subsequent_Handover', which then splits into 'HO_CA_MESSAGE_ind (Subsequent Handover Accepted)' or 'HO_CA_MESSAGE_ind (Subsequent Handover Failure)'. The 'Accepted' path leads to 'MAP_PREPARE_SUBSEQUENT_HANDOVER_rsp' and 'MAP_DELIMITER_req', then 'Wait_For_Subsequent_Handover_Completion', 'HO_CA_MESSAGE_ind (Subsequent Handover Complete)', 'MAP_SEND_END_SIGNAL_rsp' and 'MAP_CLOSE_req', and finally 'Null'. The 'Failure' path leads to 'Set User Error: Subsequent Handover Failure', 'MAP_PREPARE_SUBSEQUENT_HANDOVER_rsp' and 'MAP_DELIMITER_req', and then 'MS_On_MSC_B'. The 'Error' path from 'Check_Indication' leads to 'MAP_PREPARE_SUBSEQUENT_HANDOVER_rsp' and 'MAP_DELIMITER_req', and then 'MS_On_MSC_B'.](b9f1899edf1da4ab3f1d88710590a72d_img.jpg) + +**process Handover\_MSC\_A** **HO\_MSCA7(8)** + +Process in MSC-A (the Anchor MSC) to handle inter- MSC handover to MSC-B (the Relay MSC) and subsequent handover back to MSC-A or to MSC-B' (the new Relay MSC) + +Signals to/from the left are to/from the Handover Control Application in MSC-A; signals to/from the right are to/from MSC-B + +``` + + graph TD + Start([MS_On_MSC_B]) --> Ind1[MAP_PREPARE_SUBSEQUENT_HANDOVER_ind] + Ind1 --> Check[Check_Indication] + Check -- OK --> Decision{MSC known?} + Check -- Error --> Merge1(( )) + Decision -- No --> Error1[Set User Error: Unknown MSC] + Error1 --> Merge1 + Decision -- Yes --> Req1[HO_CA_MESSAGE_req +(Handover Request)] + Req1 --> Wait1[Wait_For_Subsequent_Handover] + Wait1 --> Merge2(( )) + Merge2 --> Ind2[HO_CA_MESSAGE_ind +(Subsequent Handover Accepted)] + Merge2 --> Ind3[HO_CA_MESSAGE_ind +(Subsequent Handover Failure)] + Ind2 --> Merge3(( )) + Merge3 --> Rsp1[MAP_PREPARE_SUBSEQUENT_HANDOVER_rsp +MAP_DELIMITER_req] + Rsp1 --> Wait2[Wait_For_Subsequent_Handover_Completion] + Wait2 --> Merge4(( )) + Merge4 --> Ind4[HO_CA_MESSAGE_ind +(Subsequent Handover Complete)] + Ind4 --> Merge5(( )) + Merge5 --> Rsp2[MAP_SEND_END_SIGNAL_rsp +MAP_CLOSE_req] + Rsp2 --> Null([Null]) + Ind3 --> Error2[Set User Error: Subsequent Handover Failure] + Error2 --> Merge6(( )) + Merge6 --> Rsp3[MAP_PREPARE_SUBSEQUENT_HANDOVER_rsp +MAP_DELIMITER_req] + Rsp3 --> MSOnB2([MS_On_MSC_B]) + +``` + +Flowchart for process Handover\_MSC\_A. It starts with MS\_On\_MSC\_B, followed by MAP\_PREPARE\_SUBSEQUENT\_HANDOVER\_ind. A decision 'MSC known?' leads to 'Set User Error: Unknown MSC' if No, or 'HO\_CA\_MESSAGE\_req (Handover Request)' if Yes. The 'Yes' path leads to 'Wait\_For\_Subsequent\_Handover', which then splits into 'HO\_CA\_MESSAGE\_ind (Subsequent Handover Accepted)' or 'HO\_CA\_MESSAGE\_ind (Subsequent Handover Failure)'. The 'Accepted' path leads to 'MAP\_PREPARE\_SUBSEQUENT\_HANDOVER\_rsp' and 'MAP\_DELIMITER\_req', then 'Wait\_For\_Subsequent\_Handover\_Completion', 'HO\_CA\_MESSAGE\_ind (Subsequent Handover Complete)', 'MAP\_SEND\_END\_SIGNAL\_rsp' and 'MAP\_CLOSE\_req', and finally 'Null'. The 'Failure' path leads to 'Set User Error: Subsequent Handover Failure', 'MAP\_PREPARE\_SUBSEQUENT\_HANDOVER\_rsp' and 'MAP\_DELIMITER\_req', and then 'MS\_On\_MSC\_B'. The 'Error' path from 'Check\_Indication' leads to 'MAP\_PREPARE\_SUBSEQUENT\_HANDOVER\_rsp' and 'MAP\_DELIMITER\_req', and then 'MS\_On\_MSC\_B'. + +1498 + +1499 + +Figure 19.2/4 (sheet 7 of 8): Process HO\_MSC\_A + +![State transition diagram for process HO_MSC_A. The diagram shows two main state machines. The top state machine starts in a state with transitions 'Wait_For_Subsequent_Handover' and 'Wait_For_Subsequent_Handover_Completion'. It has three outgoing transitions: 'HO_CA_MESSAGE_ind (Message Transfer)' leading to a state with 'MAP_FORWARD_ACCESS_SIGNALLING_req' and 'MAP_DELIMITER_req'; 'MAP_PROCESS_ACCESS_SIGNALLING_ind' leading to a 'Check_Indication' state; and 'Receive_Error_From_HO_CA' leading to 'Null' or 'MS_On_MSC_B' states. The 'Check_Indication' state has 'OK' and 'Error' transitions leading to 'HO_CA_MESSAGE_req (Message Transfer)' and terminal states. The 'HO_CA_MESSAGE_req' state leads to 'Wait_For_Handover_Indication'. The bottom state machine starts in a state with transitions 'Wait_For_Subsequent_Handover' and 'Wait_For_Subsequent_Handover_Completion'. It has three outgoing transitions: 'MAP_CLOSE_req' leading to 'HO_CA_MESSAGE_req (Connection Closed)' and 'Null'; 'MAP_U_ABORT_ind, MAP_P_ABORT_ind' leading to 'HO_CA_MESSAGE_req (MAP Error)' and 'Null'; and 'MAP_NOTICE_ind' leading to 'HO_CA_MESSAGE_req (MAP Error)' and a terminal state.](1902200b1ad3f4c86ba69bae8fe13737_img.jpg) + +**process Handover\_MSC\_A** **HO\_MSCA8(8)** + +Process in MSC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to MSC-A or to MSC-B' (the new Relay MSC) + +Signals to/from the left are to/from the Handover Control Application in MSC-A; signals to/from the right are to/from MSC-B + +``` + + graph TD + subgraph TopState [ ] + T1(( )) --> T1_W[Wait_For_Subsequent_Handover, Wait_For_Subsequent_Handover_Completion] + T1 --> HO_CA_MESSAGE_ind[HO_CA_MESSAGE_ind Message Transfer] + T1 --> MAP_PROCESS_ACCESS_SIGNALLING_ind[MAP_PROCESS_ACCESS_SIGNALLING_ind] + T1 --> Receive_Error_From_HO_CA[Receive_Error_From_HO_CA] + HO_CA_MESSAGE_ind --> MAP_FORWARD_ACCESS_SIGNALLING_req[MAP_FORWARD_ACCESS_SIGNALLING_req MAP_DELIMITER_req] + MAP_FORWARD_ACCESS_SIGNALLING_req --> T1_E1(( )) + MAP_PROCESS_ACCESS_SIGNALLING_ind --> Check_Indication[Check_Indication] + Check_Indication -- OK --> HO_CA_MESSAGE_req_1[HO_CA_MESSAGE_req Message Transfer] + HO_CA_MESSAGE_req_1 --> Wait_For_Handover_Indication[Wait_For_Handover_Indication] + Check_Indication -- Error --> T1_E2(( )) + Receive_Error_From_HO_CA -- Null --> Null_1[Null] + Receive_Error_From_HO_CA -- Error --> MS_On_MSC_B[MS_On_MSC_B] + end + + subgraph BottomState [ ] + B1(( )) --> B1_W[Wait_For_Subsequent_Handover, Wait_For_Subsequent_Handover_Completion] + B1 --> MAP_CLOSE_req[MAP_CLOSE_req] + B1 --> MAP_U_ABORT_ind_MAP_P_ABORT_ind[MAP_U_ABORT_ind, MAP_P_ABORT_ind] + B1 --> MAP_NOTICE_ind[MAP_NOTICE_ind] + MAP_CLOSE_req --> HO_CA_MESSAGE_req_2[HO_CA_MESSAGE_req Connection Closed] + HO_CA_MESSAGE_req_2 --> Null_2[Null] + MAP_U_ABORT_ind_MAP_P_ABORT_ind --> HO_CA_MESSAGE_req_3[HO_CA_MESSAGE_req MAP Error] + HO_CA_MESSAGE_req_3 --> Null_3[Null] + MAP_NOTICE_ind --> HO_CA_MESSAGE_req_4[HO_CA_MESSAGE_req MAP Error] + HO_CA_MESSAGE_req_4 --> B1_E3(( )) + end + +``` + +State transition diagram for process HO\_MSC\_A. The diagram shows two main state machines. The top state machine starts in a state with transitions 'Wait\_For\_Subsequent\_Handover' and 'Wait\_For\_Subsequent\_Handover\_Completion'. It has three outgoing transitions: 'HO\_CA\_MESSAGE\_ind (Message Transfer)' leading to a state with 'MAP\_FORWARD\_ACCESS\_SIGNALLING\_req' and 'MAP\_DELIMITER\_req'; 'MAP\_PROCESS\_ACCESS\_SIGNALLING\_ind' leading to a 'Check\_Indication' state; and 'Receive\_Error\_From\_HO\_CA' leading to 'Null' or 'MS\_On\_MSC\_B' states. The 'Check\_Indication' state has 'OK' and 'Error' transitions leading to 'HO\_CA\_MESSAGE\_req (Message Transfer)' and terminal states. The 'HO\_CA\_MESSAGE\_req' state leads to 'Wait\_For\_Handover\_Indication'. The bottom state machine starts in a state with transitions 'Wait\_For\_Subsequent\_Handover' and 'Wait\_For\_Subsequent\_Handover\_Completion'. It has three outgoing transitions: 'MAP\_CLOSE\_req' leading to 'HO\_CA\_MESSAGE\_req (Connection Closed)' and 'Null'; 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind' leading to 'HO\_CA\_MESSAGE\_req (MAP Error)' and 'Null'; and 'MAP\_NOTICE\_ind' leading to 'HO\_CA\_MESSAGE\_req (MAP Error)' and a terminal state. + +1500 + +1501 + +**Figure 19.2/4 (sheet 8 of 8): Process HO\_MSC\_A** + +![Flowchart for process Handover_MSC_B. It starts with an initial state leading to 'Null', then 'Receive_Open_ind'. From 'Receive_Open_ind', an 'Error' leads to 'Null', 'OK' leads to 'Wait_For_Service_Indication', and 'Vr' leads to 'Perform MAP Vr dialogue'. 'Wait_For_Service_Indication' branches into three paths: 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req' and 'Null'; 'MAP_PREPARE_HANDOVER_ind' leading to 'Check_Indication'; and 'MAP_U_ABORT_ind, MAP_P_ABORT_ind' leading to 'Perform MAP Vr dialogue'. 'Check_Indication' has an 'Error' path to 'MAP_PREPARE_HANDOVER_rsp, MAP_CLOSE_req' and 'OK' path to 'VBS or VGCS?'. 'VBS or VGCS?' has a 'No' path to 'Perform MAP Vr dialogue' and a 'Yes' path to 'New cell in Group Call area?'. 'New cell in Group Call area?' has a 'Yes' path to 'Perform MAP Vr dialogue' and a 'No' path to 'Set User Error: Target cell outside Group Call area'. 'Set User Error: Target cell outside Group Call area' leads to 'MAP_PREPARE_HANDOVER_rsp, MAP_CLOSE_req' and 'Null'. 'MAP_PREPARE_HANDOVER_rsp, MAP_CLOSE_req' from 'Set User Error' leads to a merge point. 'MAP_PREPARE_HANDOVER_rsp, MAP_CLOSE_req' from 'Error' in 'Check_Indication' also leads to this merge point. From this merge point, a 'Yes' path from 'Handover number allocation required?' leads to connector '1', and a 'No' path leads to 'HO_CA_MESSAGE_req (Handover Request)' and 'Wait_For_Channel'. 'Perform MAP Vr dialogue' from 'Vr' in 'Receive_Open_ind' leads to 'Null'. 'Perform MAP Vr dialogue' from 'MAP_U_ABORT_ind, MAP_P_ABORT_ind' leads to the same 'Null' state.](4f53860bfd35d33fcb6f7365143da345_img.jpg) + +**process Handover\_MSC\_B** **HO\_MSCB1(8)** + +Process in MSC-B (the Relay MSC) to handle inter- MSC handover from MSC-A (the Anchor MSC) + +Signals to/from the left are to/from MSC-A; signals to/from the right are to/from the Handover Control Application in MSC-B + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_ind[Receive_Open_ind] + Receive_Open_ind -- Error --> Null2([Null]) + Receive_Open_ind -- OK --> Wait_For_Service_Indication([Wait_For_Service_Indication]) + Receive_Open_ind -- Vr --> Perform_MAP_Vr_dialogue1[Perform MAP Vr dialogue] + + Wait_For_Service_Indication --> MAP_NOTICE_ind[/MAP_NOTICE_ind/] + Wait_For_Service_Indication --> MAP_PREPARE_HANDOVER_ind[/MAP_PREPARE_HANDOVER_ind/] + Wait_For_Service_Indication --> MAP_U_ABORT_ind[/MAP_U_ABORT_ind, MAP_P_ABORT_ind/] + + MAP_NOTICE_ind --> MAP_CLOSE_req1[/MAP_CLOSE_req/] + MAP_CLOSE_req1 --> Null3([Null]) + + MAP_PREPARE_HANDOVER_ind --> Check_Indication[Check_Indication] + + Check_Indication -- Error --> MAP_PREPARE_HANDOVER_rsp1[MAP_PREPARE_HANDOVER_rsp +MAP_CLOSE_req] + + Check_Indication -- OK --> VBS_or_VGCS{VBS or VGCS?} + + VBS_or_VGCS -- No --> Perform_MAP_Vr_dialogue2[Perform MAP Vr dialogue] + + VBS_or_VGCS -- Yes --> New_cell_in_Group_Call_area{New cell in Group Call area?} + + New_cell_in_Group_Call_area -- Yes --> Perform_MAP_Vr_dialogue2 + + New_cell_in_Group_Call_area -- No --> Set_User_Error[Set User Error: +Target cell outside Group Call area] + + Set_User_Error --> MAP_PREPARE_HANDOVER_rsp2[MAP_PREPARE_HANDOVER_rsp +MAP_CLOSE_req] + + MAP_PREPARE_HANDOVER_rsp2 --> Merge1[/ /] + + Merge1 --> Handover_number_allocation_required{Handover number allocation required?} + + Handover_number_allocation_required -- Yes --> Connector1((1)) + + Handover_number_allocation_required -- No --> HO_CA_MESSAGE_req[HO_CA_MESSAGE_req +(Handover Request)] + + HO_CA_MESSAGE_req --> Wait_For_Channel([Wait_For_Channel]) + + MAP_U_ABORT_ind --> Perform_MAP_Vr_dialogue2 + + Perform_MAP_Vr_dialogue2 --> Null4([Null]) + +``` + +Flowchart for process Handover\_MSC\_B. It starts with an initial state leading to 'Null', then 'Receive\_Open\_ind'. From 'Receive\_Open\_ind', an 'Error' leads to 'Null', 'OK' leads to 'Wait\_For\_Service\_Indication', and 'Vr' leads to 'Perform MAP Vr dialogue'. 'Wait\_For\_Service\_Indication' branches into three paths: 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req' and 'Null'; 'MAP\_PREPARE\_HANDOVER\_ind' leading to 'Check\_Indication'; and 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind' leading to 'Perform MAP Vr dialogue'. 'Check\_Indication' has an 'Error' path to 'MAP\_PREPARE\_HANDOVER\_rsp, MAP\_CLOSE\_req' and 'OK' path to 'VBS or VGCS?'. 'VBS or VGCS?' has a 'No' path to 'Perform MAP Vr dialogue' and a 'Yes' path to 'New cell in Group Call area?'. 'New cell in Group Call area?' has a 'Yes' path to 'Perform MAP Vr dialogue' and a 'No' path to 'Set User Error: Target cell outside Group Call area'. 'Set User Error: Target cell outside Group Call area' leads to 'MAP\_PREPARE\_HANDOVER\_rsp, MAP\_CLOSE\_req' and 'Null'. 'MAP\_PREPARE\_HANDOVER\_rsp, MAP\_CLOSE\_req' from 'Set User Error' leads to a merge point. 'MAP\_PREPARE\_HANDOVER\_rsp, MAP\_CLOSE\_req' from 'Error' in 'Check\_Indication' also leads to this merge point. From this merge point, a 'Yes' path from 'Handover number allocation required?' leads to connector '1', and a 'No' path leads to 'HO\_CA\_MESSAGE\_req (Handover Request)' and 'Wait\_For\_Channel'. 'Perform MAP Vr dialogue' from 'Vr' in 'Receive\_Open\_ind' leads to 'Null'. 'Perform MAP Vr dialogue' from 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind' leads to the same 'Null' state. + +1502 + +1503 + +Figure 19.2/5 (sheet 1 of 8): Process HO\_MSC\_B + +![](16c2a5cb6db777cd9386004ea5cdbfd5_img.jpg) + +**process Handover\_MSC\_B** + +**HO\_MSCB2(8)** + +Process in MSC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC) + +Signals to/from the left are to/from MSC-A; signals to/from the right are to/from the Handover Control Application in MSC-B unless marked otherwise + +``` + + graph TD + Start((1)) --> Q1{Multiple +bearer +requested?} + Q1 -- No --> Q2{Multiple +bearer +supported?} + Q1 -- Yes --> Q2 + + Q2 -- No --> Out1[/MAP_PREPARE_HANDOVER_rsp +MAP_DELIMITER_req/] + Q2 -- Yes --> Out2[/MAP_OPEN_req +MAP_ALLOCATE_HANDOVER_NUMBER_req +MAP_DELIMITER_req/] + + Out1 --> State1([Wait_For_ +Service_ +Indication]) + Out2 --> ToVLRB1[[To VLR-B]] + ToVLRB1 --> In1[\Receive_ +Open_Cnf\] + In1 -- OK --> State2([Wait_For_ +Handover_ +Number]) + + State2 --> In2[\MAP_SEND_HANDOVER_REPORT_ind\] + In2 --> FromVLRB1[[From VLR-B]] + FromVLRB1 --> CheckInd{Check_ +Indication} + + CheckInd -- OK --> Out3[/HO_CA_MESSAGE_req +(Handover Number +allocated)/] + Out3 --> State3([Wait_For_ +Channel]) + + CheckInd -- Error --> Task1[Set User Error: +System failure] + + State2 --> In3[\MAP_ALLOCATE_HANDOVER_NUMBER_cnf\] + In3 --> FromVLRB2[[From VLR-B]] + In3 -- Vr, Error --> Task2[Set User Error: +No Handover +Number available] + + Task1 --> Out4[/MAP_PREPARE_HANDOVER_rsp +MAP_CLOSE_req/] + Task2 --> Out4 + Out4 --> Null([Null]) + +``` + +1504 + +1505 + +**Figure 19.2/5 (sheet 2 of 8): Process HO\_MSC\_B** + +![State transition diagram for process HO_MSC_B. The diagram shows two main state machines. The top state machine starts at 'Wait_For_Channel' and branches into three paths: 1) MAP NOTICE_ind leads to MAP_CLOSE_req, then HO_CA_MESSAGE_ind (MAP Error), ending at Null. 2) A merge point receives HO_CA_MESSAGE_ind (Handover Request ack) and leads to a decision 'SCCP segmentation required?'. If 'No', it goes to MAP_DELIMITER_req. If 'Yes', it goes to MAP_DELIMITER_req. Both lead to a merge point receiving MAP_PREPARE_HANDOVER_rsp and MAP_DELIMITER_req, then to 'Wait_For_Connection'. 3) Receive_Error_From_HO_CA leads to MAP_U_ABORT_req, which then leads to Null (Error) or Null (Null). The bottom state machine starts at a merge point with a list of states: Wait_For_Assignment, Wait_For_Channel, Wait_For_Connection, MS_On_MSC_B. It branches into two paths: 1) MAP_U_ABORT_ind and MAP_P_ABORT_ind lead to HO_CA_MESSAGE_ind (MAP Error), ending at Null. 2) MAP_CLOSE_ind leads to HO_CA_MESSAGE_ind (Connection Closed), ending at Null.](825f1c23f73e29f6da4dd471d7d80cca_img.jpg) + +**process Handover\_MSC\_B** **HO\_MSCB3(8)** + +Process in MSC-B (the Relay MSC) to handle inter- MSC handover from MSC-A (the Anchor MSC) + +Signals to/from the left are to/from MSC-A; signals to/from the right are to/from the Handover Control Application in MSC-B + +``` + +stateDiagram-v2 + [*] --> Wait_For_Channel + state "Wait_For_Channel" as Wait_For_Channel + state "SCCP segmentation required?" as SCCP_segmentation_required + state "MAP_DELIMITER_req" as MAP_DELIMITER_req + state "MAP_PREPARE_HANDOVER_rsp / MAP_DELIMITER_req" as MAP_PREPARE_HANDOVER_rsp_MAP_DELIMITER_req + state "Wait_For_Connection" as Wait_For_Connection + state "Null" as Null1[Null] + state "Null" as Null2[Null] + state "Null" as Null3[Null] + state "Null" as Null4[Null] + + Wait_For_Channel --> MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> HO_CA_MESSAGE_ind_MAP_Error1[HO_CA_MESSAGE_ind (MAP Error)] + HO_CA_MESSAGE_ind_MAP_Error1 --> Null1 + + Wait_For_Channel --> Merge1(( )) + Merge1 --> HO_CA_MESSAGE_ind_Handover_Request_ack[HO_CA_MESSAGE_ind (Handover Request ack)] + HO_CA_MESSAGE_ind_Handover_Request_ack --> SCCP_segmentation_required + SCCP_segmentation_required --> MAP_DELIMITER_req + SCCP_segmentation_required --> Merge2(( )) + Merge2 --> MAP_PREPARE_HANDOVER_rsp_MAP_DELIMITER_req + MAP_PREPARE_HANDOVER_rsp_MAP_DELIMITER_req --> Wait_For_Connection + + Wait_For_Channel --> Receive_Error_From_HO_CA + Receive_Error_From_HO_CA --> MAP_U_ABORT_req + MAP_U_ABORT_req --> Null2 + MAP_U_ABORT_req --> Null3 + + [*] --> Merge3(( )) + Merge3 --> Wait_For_Assignment_Wait_For_Channel_Wait_For_Connection_MS_On_MSC_B[Wait_For_Assignment, Wait_For_Channel, Wait_For_Connection, MS_On_MSC_B] + Wait_For_Assignment_Wait_For_Channel_Wait_For_Connection_MS_On_MSC_B --> Merge4(( )) + Merge4 --> MAP_U_ABORT_ind_MAP_P_ABORT_ind[MAP_U_ABORT_ind / MAP_P_ABORT_ind] + MAP_U_ABORT_ind_MAP_P_ABORT_ind --> HO_CA_MESSAGE_ind_MAP_Error2[HO_CA_MESSAGE_ind (MAP Error)] + HO_CA_MESSAGE_ind_MAP_Error2 --> Null4 + + Merge4 --> MAP_CLOSE_ind + MAP_CLOSE_ind --> HO_CA_MESSAGE_ind_Connection_Closed[HO_CA_MESSAGE_ind (Connection Closed)] + HO_CA_MESSAGE_ind_Connection_Closed --> Null4 + +``` + +State transition diagram for process HO\_MSC\_B. The diagram shows two main state machines. The top state machine starts at 'Wait\_For\_Channel' and branches into three paths: 1) MAP NOTICE\_ind leads to MAP\_CLOSE\_req, then HO\_CA\_MESSAGE\_ind (MAP Error), ending at Null. 2) A merge point receives HO\_CA\_MESSAGE\_ind (Handover Request ack) and leads to a decision 'SCCP segmentation required?'. If 'No', it goes to MAP\_DELIMITER\_req. If 'Yes', it goes to MAP\_DELIMITER\_req. Both lead to a merge point receiving MAP\_PREPARE\_HANDOVER\_rsp and MAP\_DELIMITER\_req, then to 'Wait\_For\_Connection'. 3) Receive\_Error\_From\_HO\_CA leads to MAP\_U\_ABORT\_req, which then leads to Null (Error) or Null (Null). The bottom state machine starts at a merge point with a list of states: Wait\_For\_Assignment, Wait\_For\_Channel, Wait\_For\_Connection, MS\_On\_MSC\_B. It branches into two paths: 1) MAP\_U\_ABORT\_ind and MAP\_P\_ABORT\_ind lead to HO\_CA\_MESSAGE\_ind (MAP Error), ending at Null. 2) MAP\_CLOSE\_ind leads to HO\_CA\_MESSAGE\_ind (Connection Closed), ending at Null. + +1506 + +1507 + +Figure 19.2/5 (sheet 3 of 8): Process HO\_MSC\_B + +![State transition diagram for process HO_MSC_B. The diagram shows two main state machines. The top one starts at 'Wait_For_Connection' and branches into three paths based on HO_CA_MESSAGE_ind signals: 'Message Transfer' (leading to MAP_PROCESS_ACCESS_SIGNALLING_req and back to Wait_For_Connection), 'Release Handover Number' (leading to 'Set result', then MAP_SEND_HANDOVER_REPORT_rsp/MAP_CLOSE_req to VLR-B, and back to Wait_For_Connection), and 'Handover Complete' (leading to MAP_SEND_END_SIGNAL_req and then MS_On_MSC_B). The bottom state machine starts at 'Wait_For_Connection' and branches into 'MAP_NOTICE_ind' (leading to MAP_CLOSE_req, HO_CA_MESSAGE_ind (MAP Error), and Null) and 'Receive_Error_From_HO_CA' (leading to a decision: 'Error' leads to MAP_U_ABORT_req and Null, 'Null' leads directly to Null).](9f8684f45b509e2771465930b4d3bc3b_img.jpg) + +**process Handover\_MSC\_B** **HO\_MSCB4(8)** + +Process in MSC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC) + +Signals to/from the left are to/from MSC-A; signals to/from the right are to/from the Handover Control Application in MSC-B unless marked otherwise + +``` + + graph TD + subgraph Top_State_Machine + WFC1([Wait_For_Connection]) --> HO1[HO_CA_MESSAGE_ind +Message Transfer] + WFC1 --> HO2[HO_CA_MESSAGE_ind +Release Handover Number] + WFC1 --> HO3[HO_CA_MESSAGE_ind +Handover Complete] + HO1 --> MP[MAP_PROCESS_ACCESS_SIGNALLING_req +MAP_DELIMITER_req] + MP --> WFC1 + HO2 --> SR[Set result] + SR --> MSR[MAP_SEND_HANDOVER_REPORT_rsp +MAP_CLOSE_req] + MSR -.-> VLRB[To VLR-B] + MSR --> WFC1 + HO3 --> MES[MAP_SEND_END_SIGNAL_req +MAP_DELIMITER_req] + MES --> MOB([MS_On_MSC_B]) + end + + subgraph Bottom_State_Machine + WFC2([Wait_For_Connection]) --> MN[MAP_NOTICE_ind] + WFC2 --> REF[Receive_Error_From_HO_CA] + MN --> MC[MAP_CLOSE_req] + MC --> HO4[HO_CA_MESSAGE_ind +MAP Error] + HO4 --> N1([Null]) + REF --> Error[Error] + REF --> Null1[Null] + Error --> MU[MAP_U_ABORT_req] + MU --> N2([Null]) + Null1 --> N3([Null]) + end + +``` + +State transition diagram for process HO\_MSC\_B. The diagram shows two main state machines. The top one starts at 'Wait\_For\_Connection' and branches into three paths based on HO\_CA\_MESSAGE\_ind signals: 'Message Transfer' (leading to MAP\_PROCESS\_ACCESS\_SIGNALLING\_req and back to Wait\_For\_Connection), 'Release Handover Number' (leading to 'Set result', then MAP\_SEND\_HANDOVER\_REPORT\_rsp/MAP\_CLOSE\_req to VLR-B, and back to Wait\_For\_Connection), and 'Handover Complete' (leading to MAP\_SEND\_END\_SIGNAL\_req and then MS\_On\_MSC\_B). The bottom state machine starts at 'Wait\_For\_Connection' and branches into 'MAP\_NOTICE\_ind' (leading to MAP\_CLOSE\_req, HO\_CA\_MESSAGE\_ind (MAP Error), and Null) and 'Receive\_Error\_From\_HO\_CA' (leading to a decision: 'Error' leads to MAP\_U\_ABORT\_req and Null, 'Null' leads directly to Null). + +1508 + +1509 + +**Figure 19.2/5 (sheet 4 of 8): Process HO\_MSC\_B** + +![State transition diagram for process HO_MSCB5(8) in MSC-B. The diagram shows two main state transition paths starting from 'MS_On_MSC_B'. The top path handles 'MAP_SEND_END_SIGNAL_cnf', 'MAP_FORWARD_ACCESS_SIGNALLING_ind', and 'HO_CA_MESSAGE_ind (Message Transfer)'. The bottom path handles 'MAP_NOTICE_ind' and 'Receive_Error_From_HO_CA'. Transitions lead to 'Null' or back to 'MS_On_MSC_B'.](a2bbf801d7d0f95626d38da25e972941_img.jpg) + +**process Handover\_MSC\_B** **HO\_MSCB5(8)** + +Process in MSC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC) + +Signals to/from the left are to/from MSC-A; signals to/from the right are to/from the Handover Control Application in MSC-B + +``` + +stateDiagram-v2 + [*] --> MS_On_MSC_B + state "MS_On_MSC_B" as MS_On_MSC_B + + MS_On_MSC_B --> MAP_SEND_END_SIGNAL_cnf + MS_On_MSC_B --> MAP_FORWARD_ACCESS_SIGNALLING_ind + MS_On_MSC_B --> HO_CA_MESSAGE_ind_MT[HO_CA_MESSAGE_ind (Message Transfer)] + + MAP_SEND_END_SIGNAL_cnf --> HO_CA_MESSAGE_ind_CC[HO_CA_MESSAGE_ind (Connection Closed)] + HO_CA_MESSAGE_ind_CC --> Null + + MAP_FORWARD_ACCESS_SIGNALLING_ind --> Check_Indication + Check_Indication --> HO_CA_MESSAGE_req_MT[HO_CA_MESSAGE_req (Message Transfer)] + Check_Indication --> Error + Check_Indication --> OK + HO_CA_MESSAGE_req_MT --> MS_On_MSC_B + Error --> MS_On_MSC_B + OK --> MS_On_MSC_B + + HO_CA_MESSAGE_ind_MT --> MAP_PROCESS_ACCESS_SIGNALLING_req[MAP_PROCESS_ACCESS_SIGNALLING_req +MAP_DELIMITER_req] + MAP_PROCESS_ACCESS_SIGNALLING_req --> MS_On_MSC_B + + MS_On_MSC_B --> MAP_NOTICE_ind + MS_On_MSC_B --> Receive_Error_From_HO_CA + + MAP_NOTICE_ind --> HO_CA_MESSAGE_ind_ME[HO_CA_MESSAGE_ind (MAP Error)] + HO_CA_MESSAGE_ind_ME --> MS_On_MSC_B + + Receive_Error_From_HO_CA --> Error + Receive_Error_From_HO_CA --> Null + +``` + +State transition diagram for process HO\_MSCB5(8) in MSC-B. The diagram shows two main state transition paths starting from 'MS\_On\_MSC\_B'. The top path handles 'MAP\_SEND\_END\_SIGNAL\_cnf', 'MAP\_FORWARD\_ACCESS\_SIGNALLING\_ind', and 'HO\_CA\_MESSAGE\_ind (Message Transfer)'. The bottom path handles 'MAP\_NOTICE\_ind' and 'Receive\_Error\_From\_HO\_CA'. Transitions lead to 'Null' or back to 'MS\_On\_MSC\_B'. + +1510 + +1511 + +**Figure 19.2/5 (sheet 5 of 8): Process HO\_MSC\_B** + +process Handover\_MSC\_B + +HO\_MSCB6(8) + +Process in MSC-B (the Relay MSC) to handle inter- MSC handover from MSC-A (the Anchor MSC) + +Signals to/from the left are to/from MSC-A; signals to/from the right are to/from the Handover Control Application in MSC-B unless marked otherwise + +![Flowchart for process Handover_MSC_B. It starts with MS_On_MSC_B, followed by a merge symbol leading to MAP_PREPARE_HANDOVER_ind. Then Check_Indication, followed by a decision diamond 'HO Number Not Required parameter present?'. If Yes, it goes to 'HO Number Not Required parameter present?'. If No, it goes to another decision diamond 'Handover number already used?'. If Yes, it goes to 'Set User Error: Unexpected data value'. If No, it goes to a merge symbol leading to a list of messages: MAP_OPEN_req, MAP_ALLOCATE_HANDOVER_NUMBER_req, MAP_DELIMITER_req, and 'To VLR-B'. Then Receive_Open_Cnf, followed by a decision diamond 'OK'. If OK, it goes to 'Wait_For_Handover_Number_Allocation'. If Vr, Error, it goes to 'Set User Error: No Handover Number available'. Both error paths lead to a merge symbol leading to a list of messages: MAP_PREPARE_HANDOVER_rsp, MAP_DELIMITER_req. Finally, it ends with MS_On_MSC_B.](a4a814d3fa0262489da4fe8224205075_img.jpg) + +``` + +graph TD + Start([MS_On_MSC_B]) --> Merge1{ } + Merge1 --> MAP_PREPARE_HANDOVER_ind[MAP_PREPARE_HANDOVER_ind] + MAP_PREPARE_HANDOVER_ind --> Check_Indication[Check_Indication] + Check_Indication --> Decision1{HO Number Not Required parameter present?} + Decision1 -- Yes --> HO_Number_Not_Required[HO Number Not Required parameter present?] + Decision1 -- No --> Decision2{Handover number already used?} + Decision2 -- Yes --> Set_User_Error_Unexpected[Set User Error: Unexpected data value] + Decision2 -- No --> Merge2{ } + Merge2 --> MAP_OPEN_req[MAP_OPEN_req] + Merge2 --> MAP_ALLOCATE_HANDOVER_NUMBER_req[MAP_ALLOCATE_HANDOVER_NUMBER_req] + Merge2 --> MAP_DELIMITER_req1[MAP_DELIMITER_req] + Merge2 -.-> To_VLR_B[To VLR-B] + MAP_OPEN_req --> Receive_Open_Cnf[Receive_Open_Cnf] + MAP_ALLOCATE_HANDOVER_NUMBER_req --> Receive_Open_Cnf + MAP_DELIMITER_req1 --> Receive_Open_Cnf + To_VLR_B -.-> Receive_Open_Cnf + Receive_Open_Cnf --> Decision3{OK} + Decision3 -- OK --> Wait_For_Handover_Number_Allocation[Wait_For_Handover_Number_Allocation] + Decision3 -- Vr, Error --> Set_User_Error_No_Handover[Set User Error: No Handover Number available] + Set_User_Error_Unexpected --> Merge3{ } + Set_User_Error_No_Handover --> Merge3 + Merge3 --> MAP_PREPARE_HANDOVER_rsp[MAP_PREPARE_HANDOVER_rsp] + Merge3 --> MAP_DELIMITER_req2[MAP_DELIMITER_req] + MAP_PREPARE_HANDOVER_rsp --> End([MS_On_MSC_B]) + MAP_DELIMITER_req2 --> End + +``` + +Flowchart for process Handover\_MSC\_B. It starts with MS\_On\_MSC\_B, followed by a merge symbol leading to MAP\_PREPARE\_HANDOVER\_ind. Then Check\_Indication, followed by a decision diamond 'HO Number Not Required parameter present?'. If Yes, it goes to 'HO Number Not Required parameter present?'. If No, it goes to another decision diamond 'Handover number already used?'. If Yes, it goes to 'Set User Error: Unexpected data value'. If No, it goes to a merge symbol leading to a list of messages: MAP\_OPEN\_req, MAP\_ALLOCATE\_HANDOVER\_NUMBER\_req, MAP\_DELIMITER\_req, and 'To VLR-B'. Then Receive\_Open\_Cnf, followed by a decision diamond 'OK'. If OK, it goes to 'Wait\_For\_Handover\_Number\_Allocation'. If Vr, Error, it goes to 'Set User Error: No Handover Number available'. Both error paths lead to a merge symbol leading to a list of messages: MAP\_PREPARE\_HANDOVER\_rsp, MAP\_DELIMITER\_req. Finally, it ends with MS\_On\_MSC\_B. + +1512 + +1513 + +Figure 19.2/5 (sheet 6 of 8): Process HO\_MSC\_B + +![State transition diagram for process HO_MSC_B. The process starts in 'Wait_For_Handover_Number_Allocation'. It receives 'MAP_ALLOCATE_HANDOVER_NUMBER_cnf' from VLR-B. If 'Error' (No Handover Number available or System failure), it goes to 'Set User Error' states. If 'OK', it receives 'MAP_SEND_HANDOVER_REPORT_ind' from VLR-B, checks the indication, and sends 'HO_CA_MESSAGE_req' to the Handover Control Application. It then enters 'Wait_For_Assignment'. From there, it can receive 'MAP_PREPARE_HANDOVER_rsp' and 'MAP_DELIMITER_req' from VLR-B, leading to 'MS_On_MSC_B'. It can also send 'MAP_NOTICE_ind' to the Handover Control Application, which may return 'HO_CA_MESSAGE_ind (MAP Error)', leading to 'Wait_For_Assignment'. It can receive 'HO_CA_MESSAGE_ind (Handover Request ack)' from the Handover Control Application. If 'SCCP segmentation required?' is 'No', it sends 'MAP_DELIMITER_req' to VLR-B, then 'MAP_PREPARE_HANDOVER_rsp' and 'MAP_DELIMITER_req' to VLR-B, leading to 'MS_On_MSC_B'. If 'Yes', it goes to 'SCCP segmentation required?'. It can also receive 'Error' or 'Null' from 'Receive_Error_From_HO_CA', leading to 'Wait_For_Assignment' or 'Null' respectively.](97390572a8ffb768231d191922d28d74_img.jpg) + +**process Handover\_MSC\_B** **HO\_MSCB7(8)** + +Process in MSC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC) + +Signals to/from the left are to/from MSC-A; signals to/from the right are to/from the Handover Control Application in MSC-B unless marked otherwise + +``` + +stateDiagram-v2 + [*] --> Wait_For_Handover_Number_Allocation + state "MAP_ALLOCATE_HANDOVER_NUMBER_cnf" as MAP_ALLOCATE_HANDOVER_NUMBER_cnf + state "MAP_SEND_HANDOVER_REPORT_ind" as MAP_SEND_HANDOVER_REPORT_ind + state "Check_Indication" as Check_Indication + state "HO_CA_MESSAGE_req (Handover Number allocated)" as HO_CA_MESSAGE_req + state "Set User Error: No Handover Number available" as Set_User_Error_No_Handover_Number_available + state "Set User Error: System failure" as Set_User_Error_System_failure + state "MAP_PREPARE_HANDOVER_rsp MAP_DELIMITER_req" as MAP_PREPARE_HANDOVER_rsp_MAP_DELIMITER_req + state "MS_On_MSC_B" as MS_On_MSC_B + state "Wait_For_Assignment" as Wait_For_Assignment + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "HO_CA_MESSAGE_ind (Handover Request ack)" as HO_CA_MESSAGE_ind_Handover_Request_ack + state "Receive_Error_From_HO_CA" as Receive_Error_From_HO_CA + state "Null" as Null + state "SCCP segmentation required?" as SCCP_segmentation_required + state "MAP_DELIMITER_req" as MAP_DELIMITER_req + state "HO_CA_MESSAGE_ind (MAP Error)" as HO_CA_MESSAGE_ind_MAP_Error + + Note right of MAP_ALLOCATE_HANDOVER_NUMBER_cnf: From VLR-B + Note right of MAP_SEND_HANDOVER_REPORT_ind: From VLR-B + + Wait_For_Handover_Number_Allocation --> MAP_ALLOCATE_HANDOVER_NUMBER_cnf + MAP_ALLOCATE_HANDOVER_NUMBER_cnf --> Check_Indication + Check_Indication --> HO_CA_MESSAGE_req + HO_CA_MESSAGE_req --> Wait_For_Assignment + Wait_For_Assignment --> MAP_PREPARE_HANDOVER_rsp_MAP_DELIMITER_req + MAP_PREPARE_HANDOVER_rsp_MAP_DELIMITER_req --> MS_On_MSC_B + + Check_Indication --> Set_User_Error_No_Handover_Number_available + Check_Indication --> Set_User_Error_System_failure + + Wait_For_Assignment --> MAP_NOTICE_ind + MAP_NOTICE_ind --> HO_CA_MESSAGE_ind_MAP_Error + HO_CA_MESSAGE_ind_MAP_Error --> Wait_For_Assignment + + Wait_For_Assignment --> HO_CA_MESSAGE_ind_Handover_Request_ack + HO_CA_MESSAGE_ind_Handover_Request_ack --> SCCP_segmentation_required + SCCP_segmentation_required --> MAP_DELIMITER_req + MAP_DELIMITER_req --> MAP_PREPARE_HANDOVER_rsp_MAP_DELIMITER_req + MAP_PREPARE_HANDOVER_rsp_MAP_DELIMITER_req --> MS_On_MSC_B + + Wait_For_Assignment --> Receive_Error_From_HO_CA + Receive_Error_From_HO_CA --> Wait_For_Assignment + Receive_Error_From_HO_CA --> Null + +``` + +State transition diagram for process HO\_MSC\_B. The process starts in 'Wait\_For\_Handover\_Number\_Allocation'. It receives 'MAP\_ALLOCATE\_HANDOVER\_NUMBER\_cnf' from VLR-B. If 'Error' (No Handover Number available or System failure), it goes to 'Set User Error' states. If 'OK', it receives 'MAP\_SEND\_HANDOVER\_REPORT\_ind' from VLR-B, checks the indication, and sends 'HO\_CA\_MESSAGE\_req' to the Handover Control Application. It then enters 'Wait\_For\_Assignment'. From there, it can receive 'MAP\_PREPARE\_HANDOVER\_rsp' and 'MAP\_DELIMITER\_req' from VLR-B, leading to 'MS\_On\_MSC\_B'. It can also send 'MAP\_NOTICE\_ind' to the Handover Control Application, which may return 'HO\_CA\_MESSAGE\_ind (MAP Error)', leading to 'Wait\_For\_Assignment'. It can receive 'HO\_CA\_MESSAGE\_ind (Handover Request ack)' from the Handover Control Application. If 'SCCP segmentation required?' is 'No', it sends 'MAP\_DELIMITER\_req' to VLR-B, then 'MAP\_PREPARE\_HANDOVER\_rsp' and 'MAP\_DELIMITER\_req' to VLR-B, leading to 'MS\_On\_MSC\_B'. If 'Yes', it goes to 'SCCP segmentation required?'. It can also receive 'Error' or 'Null' from 'Receive\_Error\_From\_HO\_CA', leading to 'Wait\_For\_Assignment' or 'Null' respectively. + +1514 + +1515 + +Figure 19.2/5 (sheet 7 of 8): Process HO\_MSC\_B + +![State transition diagram for process HO_MSCB8(8). The process starts at MS_On_MSC_B, receives HO_CA_MESSAGE_ind (Handover Required), then MAP_PREPARE_SUBSEQUENT_HANDOVER_req and MAP_DELIMITER_req. It enters Wait_For_Perform_Subsequent_Handover_Result state. From there, it branches based on MAP_FORWARD_ACCESS_SIGNALLING_ind, MAP_PREPARE_SUBSEQUENT_HANDOVER_cnf, and HO_CA_MESSAGE_req (Message Transfer). The diagram shows various transitions to states like Check_Indication, Check_Confirmation, and final states like MS_On_MSC_B, Null, and Wait_For_Perform_Subsequent_Handover_Result, with associated message transfers and error handling.](8b7c6cbcb1fb65cd6c4cdd48a79c3ac4_img.jpg) + +**process Handover\_MSC\_B** **HO\_MSCB8(8)** + +Process in MSC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC) + +Signals to/from the left are to/from MSC-A; signals to/from the right are to/from the Handover Control Application in MSC-B + +``` + +stateDiagram-v2 + [*] --> MS_On_MSC_B + MS_On_MSC_B --> HO_CA_MESSAGE_ind + HO_CA_MESSAGE_ind --> MAP_PREPARE_SUBSEQUENT_HANDOVER_req + MAP_PREPARE_SUBSEQUENT_HANDOVER_req --> Wait_For_Perform_Subsequent_Handover_Result + state "Wait_For_Perform_Subsequent_Handover_Result" as Wait_For_Perform_Subsequent_Handover_Result + state "Check_Indication" as Check_Indication + state "Check_Confirmation" as Check_Confirmation + state "MS_On_MSC_B" as MS_On_MSC_B + state "Null" as Null + + Wait_For_Perform_Subsequent_Handover_Result --> MAP_FORWARD_ACCESS_SIGNALLING_ind + Wait_For_Perform_Subsequent_Handover_Result --> MAP_PREPARE_SUBSEQUENT_HANDOVER_cnf + Wait_For_Perform_Subsequent_Handover_Result --> HO_CA_MESSAGE_req_MT[HO_CA_MESSAGE_req (Message Transfer)] + + MAP_FORWARD_ACCESS_SIGNALLING_ind --> Check_Indication + Check_Indication --> OK_1[OK] + Check_Indication --> Error_1[Error] + OK_1 --> HO_CA_MESSAGE_req_MT_1[HO_CA_MESSAGE_req (Message Transfer)] + HO_CA_MESSAGE_req_MT_1 --> Wait_For_Perform_Subsequent_Handover_Result_1[Wait_For_Perform_Subsequent_Handover_Result] + Error_1 --> Wait_For_Perform_Subsequent_Handover_Result_2[Wait_For_Perform_Subsequent_Handover_Result] + + MAP_PREPARE_SUBSEQUENT_HANDOVER_cnf --> Check_Confirmation + Check_Confirmation --> OK_2[OK] + Check_Confirmation --> User_Error[User Error, Data Error] + Check_Confirmation --> Provider_Error[Provider Error] + OK_2 --> HO_CA_MESSAGE_req_HP[HO_CA_MESSAGE_req (HO-Prepared)] + HO_CA_MESSAGE_req_HP --> MS_On_MSC_B_1[MS_On_MSC_B] + User_Error --> HO_CA_MESSAGE_req_SHF[HO_CA_MESSAGE_req (Subsequent Handover Failure)] + HO_CA_MESSAGE_req_SHF --> MS_On_MSC_B_2[MS_On_MSC_B] + Provider_Error --> HO_CA_MESSAGE_req_CC[HO_CA_MESSAGE_req (Connection closed)] + HO_CA_MESSAGE_req_CC --> Null + + HO_CA_MESSAGE_req_MT --> HO_CA_MESSAGE_req_PT[HO_CA_MESSAGE_req (Message Transfer)] + HO_CA_MESSAGE_req_PT --> MAP_PROCESS_ACCESS_SIGNALLING_req + MAP_PROCESS_ACCESS_SIGNALLING_req --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_Perform_Subsequent_Handover_Result_3[Wait_For_Perform_Subsequent_Handover_Result] + +``` + +State transition diagram for process HO\_MSCB8(8). The process starts at MS\_On\_MSC\_B, receives HO\_CA\_MESSAGE\_ind (Handover Required), then MAP\_PREPARE\_SUBSEQUENT\_HANDOVER\_req and MAP\_DELIMITER\_req. It enters Wait\_For\_Perform\_Subsequent\_Handover\_Result state. From there, it branches based on MAP\_FORWARD\_ACCESS\_SIGNALLING\_ind, MAP\_PREPARE\_SUBSEQUENT\_HANDOVER\_cnf, and HO\_CA\_MESSAGE\_req (Message Transfer). The diagram shows various transitions to states like Check\_Indication, Check\_Confirmation, and final states like MS\_On\_MSC\_B, Null, and Wait\_For\_Perform\_Subsequent\_Handover\_Result, with associated message transfers and error handling. + +1516 + +1517 + +Figure 19.2/5 (sheet 8 of 8): Process HO\_MSC\_B + +![Flowchart for macro Receive_Error_From_HO_CA. It starts with a merge node, followed by an input message HO_CA_MESSAGE_ind (Error Indication). A decision diamond 'Error indication?' follows. If 'Keep dialogue', it sends a MAP_DELIMITER_req and ends at an 'Error' node. If 'Close dialogue', it goes to another decision diamond 'MAP_NOTICE previously received?'. If 'No', it sends a MAP_U_ABORT_req and ends at a 'Null' node. If 'Yes', it sends a MAP_CLOSE_req and ends at a 'Null' node.](3d02994616bea5c657c0f138adc25aad_img.jpg) + +macrodefinition **Receive\_Error\_From\_HO\_CA** REF\_HOCA1(1) + +Macro in the MSC to handle an error indication from the Handover Control Application + +Signals to/from the left are to/from the local Handover Control Application; signals to/from the right are to/from the distant MSC + +``` + + graph TD + Start([ ]) --> Input{{HO_CA_MESSAGE_ind +(Error Indication)}} + Input --> Decision1{Error indication?} + Decision1 -- Keep dialogue --> Output1{{MAP_DELIMITER_req}} + Output1 --> End1((Error)) + Decision1 -- Close dialogue --> Decision2{MAP_NOTICE previously received?} + Decision2 -- No --> Output2{{MAP_U_ABORT_req}} + Output2 --> End2((Null)) + Decision2 -- Yes --> Output3{{MAP_CLOSE_req}} + Output3 --> End3((Null)) + +``` + +Flowchart for macro Receive\_Error\_From\_HO\_CA. It starts with a merge node, followed by an input message HO\_CA\_MESSAGE\_ind (Error Indication). A decision diamond 'Error indication?' follows. If 'Keep dialogue', it sends a MAP\_DELIMITER\_req and ends at an 'Error' node. If 'Close dialogue', it goes to another decision diamond 'MAP\_NOTICE previously received?'. If 'No', it sends a MAP\_U\_ABORT\_req and ends at a 'Null' node. If 'Yes', it sends a MAP\_CLOSE\_req and ends at a 'Null' node. + +1518 + +1519 + +**Figure 19.2/6: Macro Receive\_error\_from\_HO\_CA** + +![Flowchart for process Handover_VLR_B. It starts with an initial state, followed by 'Null', 'Receive_Open_ind'. A decision point follows: if 'OK', it sends 'MAP_ALLOCATE_HANDOVER_NUMBER_ind' and goes to 'Check_Indication'; if 'Vr, Error', it goes to 'Null'. From 'Check_Indication', if 'OK', it checks if a handover number is available. If 'No', it sets a user error and sends 'MAP_ALLOCATE_HANDOVER_NUMBER_rsp' and 'MAP_CLOSE_req' before reaching 'Null'. If 'Yes', it allocates the handover number, sends 'MAP_SEND_HANDOVER_REPORT_req' and 'MAP_DELIMITER_req', and enters 'Wait_For_Handover_Report'. From there, it can send 'MAP_SEND_HANDOVER_REPORT_cnf', receive 'MAP_U_ABORT_ind', or perform a 'Local Abort' (sending 'MAP_U_ABORT_req'). All three paths lead to a final 'Null' state after releasing the handover number.](010423317d39b0a59b0a3438b3d33a5a_img.jpg) + +**process Handover\_VLR\_B** **HO\_VLRB1(1)** + +Process in VLR-B (the VLR of the Relay MSC) to handle inter-MSB handover from MSC-A to MSC-B + +Signals to/from the left are to/from MSC-B; signals from the right are from the handover control application in VLR-B + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> RecOpen[Receive_Open_ind] + RecOpen --> Decision1{ } + Decision1 -- OK --> SendAlloc[MAP_ALLOCATE_HANDOVER_NUMBER_ind] + SendAlloc --> CheckInd[Check_Indication] + Decision1 -- Vr, Error --> Null2([Null]) + CheckInd --> Decision2{ } + Decision2 -- OK --> Decision3{Handover number available?} + Decision3 -- No --> SetError[Set User Error: No Handover number available] + SetError --> SendRsp[MAP_ALLOCATE_HANDOVER_NUMBER_rsp +MAP_CLOSE_req] + SendRsp --> Null3([Null]) + Decision3 -- Yes --> Alloc[Allocate Handover number] + Alloc --> SendReq[MAP_SEND_HANDOVER_REPORT_req +MAP_DELIMITER_req] + SendReq --> WaitReport[Wait_For_Handover_Report] + WaitReport --> Decision4{ } + Decision4 --> SendCnf[MAP_SEND_HANDOVER_REPORT_cnf] + SendCnf --> Release[Release Handover number] + Decision4 --> AbortInd[MAP_U_ABORT_ind] + AbortInd --> Release + Decision4 --> LocalAbort[Local Abort] + LocalAbort --> AbortReq[MAP_U_ABORT_req] + AbortReq --> Release + Release --> Null4([Null]) + +``` + +Flowchart for process Handover\_VLR\_B. It starts with an initial state, followed by 'Null', 'Receive\_Open\_ind'. A decision point follows: if 'OK', it sends 'MAP\_ALLOCATE\_HANDOVER\_NUMBER\_ind' and goes to 'Check\_Indication'; if 'Vr, Error', it goes to 'Null'. From 'Check\_Indication', if 'OK', it checks if a handover number is available. If 'No', it sets a user error and sends 'MAP\_ALLOCATE\_HANDOVER\_NUMBER\_rsp' and 'MAP\_CLOSE\_req' before reaching 'Null'. If 'Yes', it allocates the handover number, sends 'MAP\_SEND\_HANDOVER\_REPORT\_req' and 'MAP\_DELIMITER\_req', and enters 'Wait\_For\_Handover\_Report'. From there, it can send 'MAP\_SEND\_HANDOVER\_REPORT\_cnf', receive 'MAP\_U\_ABORT\_ind', or perform a 'Local Abort' (sending 'MAP\_U\_ABORT\_req'). All three paths lead to a final 'Null' state after releasing the handover number. + +1520 + +1521 + +Figure 19.2/7: Process HO\_VLR\_B + +## 19.3 Fault recovery procedures + +1523 When a location register has restarted after a fault, the fault recovery procedures ensure that the subscriber data in the + 1524 VLR or in the SGSN become consistent with the subscriber data that are stored in the HLR for the MS concerned and + 1525 that the location information in the HLR , the VLR and the SGSN reflect accurately the current location of the MS. + +1526 The stage 2 specification of fault recovery procedures in location registers is 3GPP TS 23.007 [19]. + +### 19.3.1 VLR fault recovery procedures + +#### 19.3.1.1 General + +1529 Restoration of an IMSI record in a VLR can be triggered by a location registration request from the MS or by a request + 1530 from the HLR for a roaming number to route a mobile terminated call to the MS. If the restoration is triggered by a + 1531 location registration request from the MS, the VLR performs the location updating procedure described in + 1532 3GPP TS 23.012 [23] and clause 19.1.1 of the present document. If the restoration is triggered by a request for a + 1533 roaming number, the VLR provides the roaming number and triggers an independent dialogue to restore the subscriber + 1534 data as described in 3GPP TS 23.018 [97]. The message flow for data restoration triggered by a request for a roaming + 1535 number is shown in figure 19.3.1/1. + +![Sequence diagram showing the message flow for data restoration between a VLR and an HLR. The diagram consists of two vertical lifelines labeled 'VLR' and 'HLR'. The sequence of messages is as follows: 1) A message from HLR to VLR; 2) A message from VLR to HLR; 3) A message from HLR to VLR; 4) A message from VLR to HLR; 5) A message from HLR to VLR; 6) A message from VLR to HLR; 7) A message from HLR to VLR; 8) A message from VLR to HLR; 9) A message from HLR to VLR; 10) A message from VLR to HLR.](3602573ad341ace82ec8fb6c8cc5cf42_img.jpg) + +Sequence diagram showing the message flow for data restoration between a VLR and an HLR. The diagram consists of two vertical lifelines labeled 'VLR' and 'HLR'. The sequence of messages is as follows: 1) A message from HLR to VLR; 2) A message from VLR to HLR; 3) A message from HLR to VLR; 4) A message from VLR to HLR; 5) A message from HLR to VLR; 6) A message from VLR to HLR; 7) A message from HLR to VLR; 8) A message from VLR to HLR; 9) A message from HLR to VLR; 10) A message from VLR to HLR. + +1536 + +- 1537 +- 1538 1) MAP\_PROVIDE\_ROAMING\_NUMBER\_req/ind +- 1539 2) MAP\_PROVIDE\_ROAMING\_NUMBER\_rsp/cnf +- 1540 3) *MAP\_SEND\_AUTHENTICATION\_INFO\_req/ind* (Note 1, note 2) +- 1541 4) *MAP\_SEND\_AUTHENTICATION\_INFO\_rsp/cnf* (Note 1, note 2) +- 1542 5) MAP\_RESTORE\_DATA\_req/ind +- 1543 6) *MAP\_ACTIVATE\_TRACE\_MODE\_req/ind* (Note 1, note 3) +- 1544 7) *MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf* (Note 1, note 3) +- 1545 8) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind +- 1546 9) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf +- 1547 10) MAP\_RESTORE\_DATA\_rsp/cnf + +1548 + +1549 NOTE 1: Services printed in *italics* are optional. + +1550 NOTE 2: If authentication is required. + +1551 NOTE 3: If subscriber tracing is active in the HLR. + +1552 + +1553 + +**Figure 19.3/1: Message flow for VLR restoration at mobile terminated call set-up** + +1554 **19.3.1.2 Procedure in the VLR** + +1555 The procedure in the VLR to handle a dialogue for subscriber data restoration is defined in clause 21.2.6 of the present + +1556 document. + +1557 **19.3.1.3 Procedure in the HLR** + +1558 The MAP process in the HLR to handle a request for data restoration in the VLR is shown in figure 19.3.1/2. The MAP + +1559 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +1560 Check\_Indication see clause 25.2.1; + +1561 Control\_Tracing\_With\_VLR\_HLR see clause 25.9.6. + +1562 + +![Flowchart for process Restore_Data_HLR. It starts with an entry point, followed by 'Null', 'MAP RESTORE DATA_ind', and 'Check_Indication'. From 'Check_Indication', an 'OK' path leads to 'IMSIs known?'. If 'No', it goes to 'Set User Error: Unknown subscriber' and then to an 'Error' exit. If 'Yes', it goes to 'LMSI received?'. If 'No', it goes to 'Set User Error: System failure' and then to an 'Error' exit. If 'Yes', it goes to 'Update LMSI', then 'Subscriber tracing active in VLR:=False', then 'Control_Tracing_With_VLR_HLR'. From 'Control_Tracing_With_VLR_HLR', an 'OK' path leads to 'Insert Subs_Data Framed_HLR', which then leads to a connector '1'. An 'Error' path from 'Control_Tracing_With_VLR_HLR' leads to 'Set User Error: System failure' and then to an 'Error' exit. An 'Aborted' path from 'Control_Tracing_With_VLR_HLR' leads to an 'X' symbol. From connector '1', the flow goes to 'MNRF set?'. If 'No', it goes to an 'Error' exit. If 'Yes', it goes to 'Set: MNRF', then 'Set: HLR number', then to an exit block containing 'MAP RESTORE DATA_rsp' and 'MAP_CLOSE_req'.](3fe4863bfa4bc82904128d9adde9a00b_img.jpg) + +**process Restore\_Data\_HLR** **RD\_HLR1(1)** + +Process in the HLR to handle a request from the VLR to restore subscriber data + +Signals to/from the left are to/from the VLR + +``` + +graph TD + Start([ ]) --> Null[Null] + Null --> MAP_IND{MAP RESTORE DATA_ind} + MAP_IND --> Check[Check_Indication] + Check -- OK --> IMSI{IMSIs known?} + IMSI -- No --> Error1[Set User Error: Unknown subscriber] + Error1 --> ErrorExit1(( )) + IMSI -- Yes --> LMSI{LMSI received?} + LMSI -- No --> Error2[Set User Error: System failure] + Error2 --> ErrorExit2(( )) + LMSI -- Yes --> Update[Update LMSI] + Update --> Tracing[Subscriber tracing active in VLR:=False] + Tracing --> Control[Control_Tracing_With_VLR_HLR] + Control -- OK --> Insert[Insert Subs_Data Framed_HLR] + Insert -- OK --> Connector1((1)) + Control -- Error --> Error3[Set User Error: System failure] + Error3 --> ErrorExit3(( )) + Control -- Aborted --> X1((X)) + Connector1 --> MNRF{MNRF set?} + MNRF -- No --> ErrorExit4(( )) + MNRF -- Yes --> SetMNRF[Set: MNRF] + SetMNRF --> SetHLR[Set: HLR number] + SetHLR --> ExitBlock[MAP RESTORE DATA_rsp +MAP_CLOSE_req] + ExitBlock --> X2((X)) + +``` + +Flowchart for process Restore\_Data\_HLR. It starts with an entry point, followed by 'Null', 'MAP RESTORE DATA\_ind', and 'Check\_Indication'. From 'Check\_Indication', an 'OK' path leads to 'IMSIs known?'. If 'No', it goes to 'Set User Error: Unknown subscriber' and then to an 'Error' exit. If 'Yes', it goes to 'LMSI received?'. If 'No', it goes to 'Set User Error: System failure' and then to an 'Error' exit. If 'Yes', it goes to 'Update LMSI', then 'Subscriber tracing active in VLR:=False', then 'Control\_Tracing\_With\_VLR\_HLR'. From 'Control\_Tracing\_With\_VLR\_HLR', an 'OK' path leads to 'Insert Subs\_Data Framed\_HLR', which then leads to a connector '1'. An 'Error' path from 'Control\_Tracing\_With\_VLR\_HLR' leads to 'Set User Error: System failure' and then to an 'Error' exit. An 'Aborted' path from 'Control\_Tracing\_With\_VLR\_HLR' leads to an 'X' symbol. From connector '1', the flow goes to 'MNRF set?'. If 'No', it goes to an 'Error' exit. If 'Yes', it goes to 'Set: MNRF', then 'Set: HLR number', then to an exit block containing 'MAP RESTORE DATA\_rsp' and 'MAP\_CLOSE\_req'. + +1563 + +1564 + +Figure 19.3.1/2: Process Restore\_Data\_HLR + +1565 **19.3.2 HLR fault recovery procedures** + +1566 **19.3.2.1 General** + +1567 For the HLR, periodic back-up of data to non-volatile memory is mandatory. + +1568 Data that have been changed after the last back-up and before the restart of the HLR cannot be recovered by reload from + 1569 the non-volatile memory. Therefore, a restoration procedure is triggered for each IMSI record that has been affected by + 1570 the HLR fault at the first authenticated radio contact with the MS concerned. + +1571 As an implementation option, a notification can be forwarded to the MS to alert the subscriber to check the parameters + 1572 for supplementary services that allow subscriber controlled input (MAP\_FORWARD\_CHECK\_SS\_INDICATION + 1573 service). If the VLR receives this notification from the HLR it shall forward the notification to the MS. If the Gs- + 1574 interface is implemented the VLR shall not forward this notification. + +1575 A restoration procedure may also be triggered for IMSI records that shares subscription data with other IMSI records + 1576 when the shared subscription data is modified, added or deleted. This option presumes the support of Reset-IDs. + +1577 The message flow for HLR restoration for a non-GPRS subscriber is shown in figure 19.3.2/1. + +1578 The message flow for HLR restoration for a GPRS subscriber is shown in figure 19.3.2/2. + +![Sequence diagram showing message flow between MSC, VLR, and HLR for HLR restoration. The diagram consists of three vertical lifelines: MSC, VLR, and HLR. The sequence of messages is: 1. HLR to VLR (MAP_RESET_req/ind); 2. MSC to VLR (MAP_PROCESS_ACCESS_REQUEST_req/ind); 3. VLR to HLR (MAP_UPDATE_LOCATION_req/ind); 4. HLR to VLR (MAP_ACTIVATE_TRACE_MODE_req/ind); 5. VLR to HLR (MAP_ACTIVATE_TRACE_MODE_rsp/cnf); 6. HLR to VLR (MAP_INSERT_SUBSCRIBER_DATA_req/ind); 7. VLR to HLR (MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf); 8. HLR to VLR (MAP_UPDATE_LOCATION_rsp/cnf); 9. VLR to HLR (MAP_FORWARD_CHECK_SS_INDICATION_req/ind); 10. HLR to MSC (MAP_FORWARD_CHECK_SS_INDICATION_req/ind).](0a2fb1366851831edc7041ad2e47bdc4_img.jpg) + +Sequence diagram showing message flow between MSC, VLR, and HLR for HLR restoration. The diagram consists of three vertical lifelines: MSC, VLR, and HLR. The sequence of messages is: 1. HLR to VLR (MAP\_RESET\_req/ind); 2. MSC to VLR (MAP\_PROCESS\_ACCESS\_REQUEST\_req/ind); 3. VLR to HLR (MAP\_UPDATE\_LOCATION\_req/ind); 4. HLR to VLR (MAP\_ACTIVATE\_TRACE\_MODE\_req/ind); 5. VLR to HLR (MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf); 6. HLR to VLR (MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind); 7. VLR to HLR (MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf); 8. HLR to VLR (MAP\_UPDATE\_LOCATION\_rsp/cnf); 9. VLR to HLR (MAP\_FORWARD\_CHECK\_SS\_INDICATION\_req/ind); 10. HLR to MSC (MAP\_FORWARD\_CHECK\_SS\_INDICATION\_req/ind). + +1579 + +- 1580 +- 1581 1) MAP\_RESET\_req/ind +- 1582 2) MAP\_PROCESS\_ACCESS\_REQUEST\_req/ind +- 1583 3) MAP\_UPDATE\_LOCATION\_req/ind +- 1584 4) *MAP\_ACTIVATE\_TRACE\_MODE\_req/ind* (Note 1, Note 2) +- 1585 5) *MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf* (Note 1, Note 2) +- 1586 6) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind +- 1587 7) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf +- 1588 8) MAP\_UPDATE\_LOCATION\_rsp/cnf +- 1589 9) *MAP\_FORWARD\_CHECK\_SS\_INDICATION\_req/ind* (Note 1) +- 1590 10) *MAP\_FORWARD\_CHECK\_SS\_INDICATION\_req/ind* (Note 1) + +1591 + +1592 NOTE 1: Services printed in *italics* are optional. + +1593 NOTE 2: If subscriber tracing is active in the HLR. + +1594 +1595 +1596 +1597 + +Steps 2 to 10 may be skipped if the procedure is used to update shared subscription data. + +**Figure 19.3.2/1: Message flow for HLR restoration (non-GPRS)** + +1598 + +![Sequence diagram for HLR restoration (non-GPRS) showing message flow between SGSN and HLR. The diagram consists of two vertical lifelines: SGSN on the left and HLR on the right. Seven numbered messages are shown: 1) SGSN to HLR, 2) HLR to SGSN (with a break in the line), 3) SGSN to HLR, 4) HLR to SGSN, 5) SGSN to HLR, 6) HLR to SGSN, 7) SGSN to HLR.](8cebaca6b0616289d83a5dd723276e65_img.jpg) + +Sequence diagram for HLR restoration (non-GPRS) showing message flow between SGSN and HLR. The diagram consists of two vertical lifelines: SGSN on the left and HLR on the right. Seven numbered messages are shown: 1) SGSN to HLR, 2) HLR to SGSN (with a break in the line), 3) SGSN to HLR, 4) HLR to SGSN, 5) SGSN to HLR, 6) HLR to SGSN, 7) SGSN to HLR. + +1599 + +1600 +1601 +1602 +1603 +1604 +1605 +1606 +1607 + +- 1) MAP\_RESET\_req/ind +- 2) MAP\_UPDATE\_GPRS\_LOCATION\_req/ind +- 3) *MAP\_ACTIVATE\_TRACE\_MODE\_req/ind* (Note 1, Note 2) +- 4) *MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf* (Note 1, Note 2) +- 5) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind +- 6) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf +- 7) MAP\_UPDATE\_GPRS\_LOCATION\_rsp/cnf + +NOTE 1: Services printed in *italics* are optional. +NOTE 2: If subscriber tracing is active in the HLR. + +1608 +1609 +1610 +1611 +1612 +1613 +1614 +1615 + +Steps 2 to 7 may be skipped if the procedure is used to update shared subscription data. + +**Figure 19.3.2/2: Message flow for HLR restoration (GPRS)** + +1616 **19.3.2.2 Procedure in the HLR** + +1617 The MAP process in the HLR to notify the relevant serving nodes that the HLR has restarted is shown in figure 19.3.2/3. + +1619 The SGSN address list includes one instance of the address of each SGSN in which (according to the HLR data retrieved from the non-volatile memory) there is at least one subscriber registered who is affected by the HLR restart. + +1621 The VLR address list includes one instance of the address of each VLR in which (according to the HLR data retrieved from the non-volatile memory) there is at least one subscriber registered who is affected by the HLR restart. + +1623 The MAP process in the HLR to notify a VLR that the HLR has restarted is shown in figure 19.3.2/4. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1625     Receive\_Open\_Cnf     see clause 25.1.2. + +1626 The MAP process in the HLR to notify an SGSN that the HLR has restarted is shown in figure 19.3.2/5. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1628     Receive\_Open\_Cnf     see clause 25.1.2. + +### 1629 19.3.2.3 Procedure in the VLR + +1630 The MAP process in the VLR to handle a notification that an HLR has restarted is shown in figure 19.3.2/6. The MAP +1631 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1632     Receive\_Open\_Ind     see clause 25.1.1. + +1633 When Reset-IDs are not supported or not present in the MAP\_RESET indication, the VLR uses the HLR number or the +1634 HLR identity list included in the MAP\_RESET indication to identify the IMSI records which are affected by the HLR +1635 restart. + +1636 When Reset-IDs are supported and present in the MAP\_RESET indication, the VLR uses the Reset-IDs included in the +1637 MAP\_RESET indication to identify the affected IMSI records. + +1638 The task "Update Data" includes any required action to let the update come into effect. + +1639 If the update of shared subscription data requires only local updates in the VLR (i.e., the update of the profile does not +1640 imply to initiate any signalling interaction towards other network nodes), the updates should be performed immediately +1641 (e.g. deleting an Operator Determined Barring). + +1642 If the update of shared subscription data implies initiating a signalling interaction towards other nodes, the signalling +1643 towards other nodes should be deferred to the next authenticated radio contact with that UE. + +1644     NOTE:     The rational for the recommendation to defer signalling towards other nodes until the next authenticated +1645                 radio contact is to consider impacts to the network only when the updates are required, and to spread the +1646                 signalling towards other nodes over some time, based on user's activity. + +1647 To avoid high processing/signalling load resulting from shared subscription data update, processing/signalling actions +1648 resulting from data updates in the VLR may take a maximum operator configuration-depending time. + +1649 + +### 1650 19.3.2.4 Procedure in the SGSN + +1651 The MAP process in the SGSN to handle a notification that an HLR has restarted is shown in figure 19.3.2/7. The MAP +1652 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1653     Receive\_Open\_Ind     see clause 25.1.1. + +1654 When Reset-IDs are not supported or not present in the MAP\_RESET indication, the SGSN uses the HLR number or +1655 the HLR identity list included in the MAP\_RESET indication to identify the IMSI records which are affected by the +1656 HLR restart. + +1657 When Reset-IDs are supported and present in the MAP\_RESET indication, the SGSN uses the Reset-IDs included in +1658 the MAP\_RESET indication to identify the affected IMSI records. + +1659 The task "Update Data" includes any required action to let the update come into effect. + +1660 If the update of shared subscription data requires only local updates in the SGSN (i.e., the update of the profile does not +1661 imply to initiate any signalling interaction towards other network nodes), the updates should be performed immediately +1662 (e.g. deleting an Operator Determined Barring). + +1663 If the update of shared subscription data implies initiating a signalling interaction towards other nodes, the signalling +1664 towards other nodes should be deferred to the next authenticated radio contact with that UE. + +1665     NOTE:     The rational for the recommendation to defer signalling towards other nodes until the next authenticated +1666                 radio contact is to consider impacts to the network only when the updates are required, and to spread the +1667                 signalling towards other nodes over some time, based on user's activity. + +1668 To avoid high processing/signalling load resulting from shared subscription data update, processing/signalling actions +1669 resulting from data updates in the SGSN may take a maximum operator configuration-depending time. + +![Flowchart for process Restart_HLR. It starts with an oval, followed by 'Null', 'OM_RESTART_ind', 'Reload data from backup', and then splits into two parallel paths for GPRS and non-GPRS subscribers. The GPRS path involves checking tracing, purging MS, reading SGSN address list, and sending reset messages. The non-GPRS path is similar but uses VLR instead of SGSN. Both paths converge at a connector '1'.](2617157e11d8900104fc3f290e412821_img.jpg) + +**process Restart\_HLR** **R\_HLR1(1)** + +Process in the HLR to notify the relevant serving nodes after an HLR restart + +Signals from the right are from the O&M application in the HLR + +``` + + graph TD + Start([ ]) --> Null1[Null] + Null1 --> OM[OM_RESTART_ind] + OM --> Reload[Reload data from backup] + + Reload --> GPRS_Trace[Subscriber tracing active in SGSN:=False] + GPRS_Trace -.-> GPRS_Trace_Note[For each GPRS subscriber affected by the HLR restart] + + GPRS_Trace --> GPRS_Purge[MS purged for GPRS:=False] + GPRS_Purge -.-> GPRS_Purge_Note[For each GPRS subscriber affected by the HLR restart] + + GPRS_Purge --> GPRS_Read[Read SGSN address list] + + GPRS_Read --> GPRS_Reset[Send_Reset_To_SGSN_HLR] + + GPRS_Reset --> GPRS_All_Notified{All SGSNs notified?} + + GPRS_All_Notified -- No --> GPRS_Reset + GPRS_All_Notified -- Yes --> GPRS_Forward[Forward Check SS indication supported?] + + GPRS_Forward --> GPRS_Required{Check SS required:=True} + + GPRS_Required -.-> GPRS_Required_Note[For each non-GPRS subscriber affected by the HLR restart] + + GPRS_Required --> GPRS_Connector((1)) + + GPRS_Connector --> NonGPRS_Trace[Subscriber tracing active in VLR:=False] + + NonGPRS_Trace -.-> NonGPRS_Trace_Note[For each non-GPRS subscriber affected by the HLR restart] + + NonGPRS_Trace --> NonGPRS_Purge[MS purged:=False] + + NonGPRS_Purge -.-> NonGPRS_Purge_Note[For each non-GPRS subscriber affected by the HLR restart] + + NonGPRS_Purge --> NonGPRS_Read[Read VLR address list] + + NonGPRS_Read --> NonGPRS_Reset[Send_Reset_To_VLR_HLR] + + NonGPRS_Reset --> NonGPRS_All_Notified{All VLRs notified?} + + NonGPRS_All_Notified -- No --> NonGPRS_Reset + NonGPRS_All_Notified -- Yes --> NonGPRS_Null[Null] + +``` + +Flowchart for process Restart\_HLR. It starts with an oval, followed by 'Null', 'OM\_RESTART\_ind', 'Reload data from backup', and then splits into two parallel paths for GPRS and non-GPRS subscribers. The GPRS path involves checking tracing, purging MS, reading SGSN address list, and sending reset messages. The non-GPRS path is similar but uses VLR instead of SGSN. Both paths converge at a connector '1'. + +1670 + +1671 + +**Figure 19.3.2/3: Process Restart\_HLR** + +![A state transition diagram for the process Send_Reset_To_VLR_HLR. It starts at an initial state, transitions to a state with outgoing MAP_OPEN_req, MAP_RESET_req, and MAP_DELIMITER_req messages, then to a 'Receive_Open_Cnf' state. From there, it branches into three paths: 'Vr' leading to 'Perform MAP Vr dialogue', 'OK' leading to a 'MAP_CLOSE_req' state with 'Release method= Prearranged End', and 'Error' leading to a terminal state. Both 'Perform MAP Vr dialogue' and 'MAP_CLOSE_req' lead to terminal states.](81eebff59300420692082c50d4f0d1fc_img.jpg) + +process Send\_Reset\_To\_VLR\_HLR SR\_VLR\_HLR1(1) + +``` + +stateDiagram-v2 + [*] --> S1 + S1 --> S2 : MAP_OPEN_req, MAP_RESET_req, MAP_DELIMITER_req + S2 --> S3 : Receive_Open_Cnf + S3 --> S4 : Vr + S3 --> S5 : OK + S3 --> [*] : Error + S4 --> [*] + S5 --> S6 : Release method= Prearranged End + S5 --> [*] + +``` + +Process in the HLR to send a Reset message to a VLR + +Signals to the left are to the VLR + +MAP\_OPEN\_req +MAP\_RESET\_req +MAP\_DELIMITER\_req + +Receive\_Open\_Cnf + +Vr + +OK + +Error + +Perform MAP Vr dialogue + +MAP\_CLOSE\_req + +Release method= Prearranged End + +A state transition diagram for the process Send\_Reset\_To\_VLR\_HLR. It starts at an initial state, transitions to a state with outgoing MAP\_OPEN\_req, MAP\_RESET\_req, and MAP\_DELIMITER\_req messages, then to a 'Receive\_Open\_Cnf' state. From there, it branches into three paths: 'Vr' leading to 'Perform MAP Vr dialogue', 'OK' leading to a 'MAP\_CLOSE\_req' state with 'Release method= Prearranged End', and 'Error' leading to a terminal state. Both 'Perform MAP Vr dialogue' and 'MAP\_CLOSE\_req' lead to terminal states. + +1672 + +1673 + +Figure 19.3.2/4: Process Send\_Reset\_To\_VLR\_HLR + +![State transition diagram for process Send_Reset_To_VLR_HLR. It starts at an initial state, transitions to a state with MAP_OPEN_req, MAP_RESET_req, and MAP_DELIMITER_req. From there, it goes to a 'Receive_Open_Cnf' state. A transition labeled 'OK' leads to a 'MAP_CLOSE_req' state, which is associated with 'Release method = Prearranged End'. A transition labeled 'Vr' leads to a 'Perform MAP Vr dialogue' state. Both 'Perform MAP Vr dialogue' and 'MAP_CLOSE_req' lead to terminal states (X). A transition labeled 'Error' from 'Receive_Open_Cnf' also leads to a terminal state (X). Notes indicate the process is in the HLR sending a Reset message to a VLR, and signals to the left are to the VLR.](4f33a6e9083ffb400e3c2e074c21434e_img.jpg) + +process Send\_Reset\_To\_VLR\_HLR SR\_VLR\_HLR1(1) + +``` + +stateDiagram-v2 + [*] --> State1 + State1 --> State2 : MAP_OPEN_req, MAP_RESET_req, MAP_DELIMITER_req + State2 --> State3 : Receive_Open_Cnf + State3 --> State4 : OK + State3 --> State5 : Vr + State3 --> [*] : Error + State4 --> [*] + State5 --> [*] + note right of State1 : Process in the HLR to send a Reset message to a VLR + note right of State2 : Signals to the left are to the VLR + note right of State4 : Release method = Prearranged End + +``` + +State transition diagram for process Send\_Reset\_To\_VLR\_HLR. It starts at an initial state, transitions to a state with MAP\_OPEN\_req, MAP\_RESET\_req, and MAP\_DELIMITER\_req. From there, it goes to a 'Receive\_Open\_Cnf' state. A transition labeled 'OK' leads to a 'MAP\_CLOSE\_req' state, which is associated with 'Release method = Prearranged End'. A transition labeled 'Vr' leads to a 'Perform MAP Vr dialogue' state. Both 'Perform MAP Vr dialogue' and 'MAP\_CLOSE\_req' lead to terminal states (X). A transition labeled 'Error' from 'Receive\_Open\_Cnf' also leads to a terminal state (X). Notes indicate the process is in the HLR sending a Reset message to a VLR, and signals to the left are to the VLR. + +1674 + +1675 + +Figure 19.3.2/5: Process Send\_Reset\_To\_SGSN\_HLR + +![Flowchart for Process Receive_Reset_VLR](64ae0196fdf7931139d52ac102898ef9_img.jpg) + +The diagram is a flowchart titled 'Process Receive\_Reset\_VLR'. It begins at the top with a rectangular process block, which points down to a decision diamond. From this diamond, one path leads to a cylinder-shaped data store on the left, and the other leads to a rectangular process block on the right. The right path continues through a series of rectangular process blocks and a decision diamond. From this second decision diamond, one path leads to a cylinder-shaped data store on the right, and the other leads to a rectangular process block on the left. This left path then passes through another decision diamond and ends at a third cylinder-shaped data store at the bottom. The right path from the second decision diamond also passes through a rectangular process block and ends at a third cylinder-shaped data store on the right. The entire flowchart is enclosed in a large rectangular frame. Above the frame, there are two large black rectangular redaction blocks. The top redaction block covers the upper portion of the page, and the bottom redaction block covers a horizontal strip just above the flowchart's top border. To the right of the bottom redaction block, a small cylinder-shaped data store is partially visible. + +Flowchart for Process Receive\_Reset\_VLR + +1676 +1677 + +**Figure 19.3.2/6: Process Receive\_Reset\_VLR** + +![A flowchart diagram titled 'Process Receive_Reset_SGSN'. The diagram is partially obscured by two large black rectangular redaction boxes at the top. The visible portion shows a sequence of steps: a rectangular process block, a decision diamond, and a loop. The loop contains a rectangular process block, a decision diamond, and a connector oval. The main path continues from the first decision diamond to another rectangular process block, which then leads to a second decision diamond. This second decision diamond has two branches, each consisting of a rectangular process block followed by a connector oval. A dashed box is also visible next to the second rectangular process block.](4bad0d660ca8b0915540efeb317f3ae6_img.jpg) + +``` +graph TD; A[ ] --> B{ }; B --> C[ ]; C --> D{ }; D --> E[ ]; E --> F{ }; F --> G[ ]; G --> H[ ]; H --> I([ ]); F --> J[ ]; J --> K[ ]; K --> L([ ]); +``` + +A flowchart diagram titled 'Process Receive\_Reset\_SGSN'. The diagram is partially obscured by two large black rectangular redaction boxes at the top. The visible portion shows a sequence of steps: a rectangular process block, a decision diamond, and a loop. The loop contains a rectangular process block, a decision diamond, and a connector oval. The main path continues from the first decision diamond to another rectangular process block, which then leads to a second decision diamond. This second decision diamond has two branches, each consisting of a rectangular process block followed by a connector oval. A dashed box is also visible next to the second rectangular process block. + +1678 + +1679 + +**Figure 19.3.2/7: Process Receive\_Reset\_SGSN** + +1680 **19.3.3 CSS fault recovery procedures** + +1681 **19.3.3.1 General** + +1682 For the CSS, periodic back-up of data to non-volatile memory is mandatory. + +1683 Serving node numbers that have been changed after the last back-up and before the restart of the CSS cannot be +1684 recovered by reload from the non-volatile memory. Therefore, a restoration procedure is triggered for each IMSI record +1685 that has been affected by the CSS fault at the first authenticated radio contact with the MS concerned. + +1686 The message flow for CSS restoration for a non-GPRS subscriber is shown in figure 19.3.3/1. + +1687 The message flow for CSS restoration for a GPRS subscriber is shown in figure 19.3.3/2. + +![Sequence diagram for non-GPRS CSS restoration between VLR and CSS.](5e6399e6cc782a35c8e0c1aaceaadcb2_img.jpg) + +A sequence diagram showing the message flow for CSS restoration for a non-GPRS subscriber. The diagram consists of two vertical lifelines: VLR on the left and CSS on the right. The interaction is as follows: 1) A message labeled '1' is sent from the VLR lifeline to the CSS lifeline. 2) A message labeled '2' is sent from the CSS lifeline to the VLR lifeline. 3) A message labeled '3' is sent from the VLR lifeline to the CSS lifeline. 4) A message labeled '4' is sent from the CSS lifeline to the VLR lifeline. 5) A message labeled '5' is sent from the VLR lifeline to the CSS lifeline. The messages are represented by horizontal arrows with small numbered boxes next to them. + +Sequence diagram for non-GPRS CSS restoration between VLR and CSS. + +1688 + +1689 + +1690 + +1691 + +1692 + +1693 + +1694 + +1695 + +1696 + +1697 + +- 1) MAP\_RESET\_req/ind +- 2) MAP\_UPDATE\_VCSG\_LOCATION\_req/ind +- 3) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind +- 4) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf +- 5) MAP\_UPDATE\_VCSG\_LOCATION\_rsp/cnf + +**Figure 19.3.3/1: Message flow for CSS restoration (non-GPRS)** + +1698 + +![Sequence diagram for GPRS CSS restoration between SGSN and CSS.](76c03f7b5abcc83130e66d006621a2cf_img.jpg) + +A sequence diagram showing the message flow for CSS restoration for a GPRS subscriber. The diagram consists of two vertical lifelines: SGSN on the left and CSS on the right. The interaction is as follows: 1) A message labeled '1' is sent from the SGSN lifeline to the CSS lifeline. 2) A message labeled '2' is sent from the CSS lifeline to the SGSN lifeline. 3) A message labeled '3' is sent from the SGSN lifeline to the CSS lifeline. 4) A message labeled '4' is sent from the CSS lifeline to the SGSN lifeline. 5) A message labeled '5' is sent from the SGSN lifeline to the CSS lifeline. The messages are represented by horizontal arrows with small numbered boxes next to them. + +Sequence diagram for GPRS CSS restoration between SGSN and CSS. + +1699 + +1700 + +1701 + +1702 + +- 1) MAP\_RESET\_req/ind +- 2) MAP\_UPDATE\_VCSG\_LOCATION\_req/ind + +1703 3) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind +1704 4) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf +1705 5) MAP\_UPDATE\_VCSG\_LOCATION\_rsp/cnf +1706 +1707 +1708 + +**Figure 19.3.3/2: Message flow for CSS restoration (GPRS)** + +### 1709 19.3.3.2 Procedure in the CSS + +1710 The MAP process in the CSS to notify the relevant serving nodes that the CSS has restarted is shown in figure 19.3.3/3. + +1711 The SGSN address list includes one instance of the address of each SGSN in which (according to the CSS data retrieved +1712 from the non-volatile memory) there is at least one subscriber registered who is affected by the CSS restart. + +1713 The VLR address list includes one instance of the address of each VLR in which (according to the CSS data retrieved +1714 from the non-volatile memory) there is at least one subscriber registered who is affected by the CSS restart. + +1715 The MAP process in the CSS to notify a VLR that the CSS has restarted is shown in figure 19.3.3/4. The MAP process +1716 invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1717 Receive\_Open\_Cnf see clause 25.1.2. + +1718 The MAP process in the CSS to notify an SGSN that the CSS has restarted is shown in figure 19.3.3/5. The MAP +1719 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1720 Receive\_Open\_Cnf see clause 25.1.2. + +### 1721 19.3.3.3 Procedure in the VLR + +1722 The MAP process in the VLR to handle a notification that a CSS has restarted is shown in figure 19.3.3/6. The MAP +1723 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1724 Receive\_Open\_Ind see clause 25.1.1. + +1725 The VLR uses the CSS number (filled in Sending Node number parameter) included in the MAP\_RESET indication to +1726 identify the user's IMSI records which are affected by the CSS restart. + +### 1727 19.3.3.4 Procedure in the SGSN + +1728 The MAP process in the SGSN to handle a notification that a CSS has restarted is shown in figure 19.3.3/6. The MAP +1729 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1730 Receive\_Open\_Ind see clause 25.1.1. + +1731 The SGSN uses the CSS number (filled in Sending Node number parameter) included in the MAP\_RESET indication to +1732 identify the user's IMSI records which are affected by the CSS restart. + +![Flowchart for process Restart_CSS. It starts with an oval, followed by 'Null', 'OM_RESTART_ind', 'Reload data from backup', and 'Read SGSN address list'. A loop exists for 'Send_Reset_To_SGSN_CSS' and 'All SGSNs notified?'. A connector '1' leads to the second part: 'Read VLR address list', 'Send_Reset_To_VLR_CSS', 'All VLRs notified?', and finally 'Null'.](4ecc29a3c000f2a2409ade321df55f28_img.jpg) + +**process Restart\_CSS** **R\_CSS1(1)** + +Process in the CSS to notify the relevant serving nodes after a CSS restart + +Signals from the right are from the O&M application in the CSS + +``` + +graph TD + Start([ ]) --> Null1[Null] + Null1 --> OM[OM_RESTART_ind] + OM --> Reload[Reload data from backup] + Reload --> ReadSGSN[Read SGSN address list] + ReadSGSN --> SendSGSN[Send_Reset_To_SGSN_CSS] + SendSGSN --> AllSGSNs{All SGSNs notified?} + AllSGSNs -- No --> SendSGSN + AllSGSNs -- Yes --> 1((1)) + 1 --> ReadVLR[Read VLR address list] + ReadVLR --> SendVLR[Send_Reset_To_VLR_CSS] + SendVLR --> AllVLRs{All VLRs notified?} + AllVLRs -- No --> SendVLR + AllVLRs -- Yes --> Null2[Null] + +``` + +Flowchart for process Restart\_CSS. It starts with an oval, followed by 'Null', 'OM\_RESTART\_ind', 'Reload data from backup', and 'Read SGSN address list'. A loop exists for 'Send\_Reset\_To\_SGSN\_CSS' and 'All SGSNs notified?'. A connector '1' leads to the second part: 'Read VLR address list', 'Send\_Reset\_To\_VLR\_CSS', 'All VLRs notified?', and finally 'Null'. + +1733 + +1734 + +Figure 19.3.3/3: Process Restart\_CSS + +![Sequence diagram for process Send_Reset_To_VLR_CSS. The diagram shows a vertical timeline starting with an initial node, followed by a left-pointing arrow representing a request. A box next to the arrow lists 'MAP_OPEN_req', 'MAP_RESET_req', and 'MAP_DELIMITER_req'. Below the arrow is a 'Receive_Open_Cnf' box. From this box, two paths emerge: one labeled 'OK' leading to a right-pointing arrow representing a response, and another labeled 'Vr, Error' leading to an 'X' (error). The right-pointing arrow is next to a box containing 'Release method:= Prearranged End'. The sequence ends with an 'X' at the bottom of the timeline.](5ae965392e3ed6f9493eff40d2f1cc3e_img.jpg) + +process Send\_Reset\_To\_VLR\_CSS SR\_VLR\_CSS1(1) + +Process in the CSS to send a Reset message to a VLR + +Signals to the left are to the VLR + +MAP\_OPEN\_req +MAP\_RESET\_req +MAP\_DELIMITER\_req + +Receive\_Open\_Cnf + +OK + +Vr, Error + +MAP\_CLOSE\_req + +Release method:= +Prearranged End + +Sequence diagram for process Send\_Reset\_To\_VLR\_CSS. The diagram shows a vertical timeline starting with an initial node, followed by a left-pointing arrow representing a request. A box next to the arrow lists 'MAP\_OPEN\_req', 'MAP\_RESET\_req', and 'MAP\_DELIMITER\_req'. Below the arrow is a 'Receive\_Open\_Cnf' box. From this box, two paths emerge: one labeled 'OK' leading to a right-pointing arrow representing a response, and another labeled 'Vr, Error' leading to an 'X' (error). The right-pointing arrow is next to a box containing 'Release method:= Prearranged End'. The sequence ends with an 'X' at the bottom of the timeline. + +1735 + +1736 + +Figure 19.3.3/4: Process Send\_Reset\_To\_VLR\_CSS + +![SDL diagram for process Send_Reset_To_SGSN_CSS showing the sequence of sending MAP_OPEN_req, MAP_RESET_req, and MAP_DELIMITER_req, receiving an Open_Cnf, and then either closing the connection if OK or terminating if an error occurs.](53668fc0567b0e9fce35a73e32dcee59_img.jpg) + +process Send\_Reset\_To\_SGSN\_CSS +SR\_SGSN\_CSS1(1) + + + +``` + + graph TD + Start([ ]) --> Output1[MAP_OPEN_req +MAP_RESET_req +MAP_DELIMITER_req] + Output1 --> Input1[Receive_Open_Cnf] + Input1 --> Decision{ } + Decision -- OK --> Output2[MAP_CLOSE_req] + Output2 --- Comment[Release method= +Prearranged End] + Output2 --> End1((X)) + Decision -- "Vr, Error" --> End2((X)) + + subgraph Callouts + direction LR + C1[Process in the CSS to +send a Reset message to +an SGSN] + C2[Signals to the left +are to the SGSN] + end + +``` + +SDL diagram for process Send\_Reset\_To\_SGSN\_CSS showing the sequence of sending MAP\_OPEN\_req, MAP\_RESET\_req, and MAP\_DELIMITER\_req, receiving an Open\_Cnf, and then either closing the connection if OK or terminating if an error occurs. + +1737 + +1738 + +**Figure 19.3.3/5: Process Send\_Reset\_To\_SGSN\_CSS** + +![Flowchart for process Receive_Reset_From_CSS_VLR. It starts with an initial node, followed by 'Null', then 'Receive_Open_Ind'. From 'Receive_Open_Ind', an 'OK' path leads to 'Wait_For_Service_Primitive' and an error path labeled 'Vr, Error' leads to 'Null'. From 'Wait_For_Service_Primitive', two parallel paths emerge: 'MAP_P_ABORT_ind' leading to 'Null', and 'MAP_RESET_ind' leading to 'MAP_CLOSE_req'. 'MAP_CLOSE_req' has a note 'Release method:= Prearranged End' and leads to 'Identify IMSI records'. 'Identify IMSI records' leads to 'Location information confirmed by CSS:=False', which has a note 'For each identified IMSI record'. Finally, it leads to 'Null'.](fad4b22bbd4eb39d94bd3c80cea4cc13_img.jpg) + +process **Receive\_Reset\_From\_CSS\_VLR** RR\_CSS\_VLR1(1) + +Process in the VLR to handle a Reset message from the CSS + +Signals to/from the right are to/from the CSS + +``` + +graph TD + Start([ ]) --> Null1[Null] + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind -- OK --> Wait_For_Service_Primitive[Wait_For_Service_Primitive] + Receive_Open_Ind -- "Vr, Error" --> Null2[Null] + Wait_For_Service_Primitive --> MAP_P_ABORT_ind[/MAP_P_ABORT_ind/] + Wait_For_Service_Primitive --> MAP_RESET_ind[/MAP_RESET_ind/] + MAP_P_ABORT_ind --> Null3[Null] + MAP_RESET_ind --> MAP_CLOSE_req[/MAP_CLOSE_req/] + MAP_CLOSE_req -- "Release method:= Prearranged End" --> Identify_IMSI_records[Identify IMSI records] + Identify_IMSI_records --> Location_Information_Confirmed[Location information confirmed by CSS:=False] + Location_Information_Confirmed -- "For each identified IMSI record" --> Null4[Null] + +``` + +Flowchart for process Receive\_Reset\_From\_CSS\_VLR. It starts with an initial node, followed by 'Null', then 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', an 'OK' path leads to 'Wait\_For\_Service\_Primitive' and an error path labeled 'Vr, Error' leads to 'Null'. From 'Wait\_For\_Service\_Primitive', two parallel paths emerge: 'MAP\_P\_ABORT\_ind' leading to 'Null', and 'MAP\_RESET\_ind' leading to 'MAP\_CLOSE\_req'. 'MAP\_CLOSE\_req' has a note 'Release method:= Prearranged End' and leads to 'Identify IMSI records'. 'Identify IMSI records' leads to 'Location information confirmed by CSS:=False', which has a note 'For each identified IMSI record'. Finally, it leads to 'Null'. + +1739 + +1740 + +**Figure 19.3.3/6: Process Receive\_Reset\_From\_CSS\_VLR** + +![Flowchart for process Receive_Reset_From_CSS_SGSN. The process starts at an entry point, goes to 'Null', then 'Receive_Open_Ind'. From 'Receive_Open_Ind', an 'OK' path leads to 'Wait_For_Service_Primitive' and a 'Vr, Error' path leads to 'Null'. From 'Wait_For_Service_Primitive', two paths emerge: 'MAP_P_ABORT_ind' leading to 'Null' and 'MAP_RESET_ind' leading to 'MAP_CLOSE_req'. 'MAP_CLOSE_req' has an associated note 'Release method:= Prearranged End' and leads to 'Identify IMSI records'. 'Identify IMSI records' leads to 'Location information confirmed by CSS:=False', which has an associated note 'For each identified IMSI record'. Finally, it leads to 'Null'.](ac991aadd44a0ddcae4451e75069dbdc_img.jpg) + +process Receive\_Reset\_From\_CSS\_SGSN RR\_CSS\_SGSN1(1) + +Process in the SGSN to handle a Reset message from the CSS + +Signals to/from the right are to/from the CSS + +``` + +graph TD + Entry([ ]) --> Null1[Null] + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind -- OK --> Wait_For_Service_Primitive[Wait_For_Service_Primitive] + Receive_Open_Ind -- Vr, Error --> Null2[Null] + Wait_For_Service_Primitive --> MAP_P_ABORT_ind{MAP_P_ABORT_ind} + Wait_For_Service_Primitive --> MAP_RESET_ind{MAP_RESET_ind} + MAP_P_ABORT_ind --> Null3[Null] + MAP_RESET_ind --> MAP_CLOSE_req{MAP_CLOSE_req} + MAP_CLOSE_req -.-> Note1[Release method:= Prearranged End] + MAP_CLOSE_req --> Identify_IMSI_records[Identify IMSI records] + Identify_IMSI_records --> Location_Information_Confirmed[Location information confirmed by CSS:=False] + Location_Information_Confirmed -.-> Note2[For each identified IMSI record] + Location_Information_Confirmed --> Null4[Null] + +``` + +Flowchart for process Receive\_Reset\_From\_CSS\_SGSN. The process starts at an entry point, goes to 'Null', then 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', an 'OK' path leads to 'Wait\_For\_Service\_Primitive' and a 'Vr, Error' path leads to 'Null'. From 'Wait\_For\_Service\_Primitive', two paths emerge: 'MAP\_P\_ABORT\_ind' leading to 'Null' and 'MAP\_RESET\_ind' leading to 'MAP\_CLOSE\_req'. 'MAP\_CLOSE\_req' has an associated note 'Release method:= Prearranged End' and leads to 'Identify IMSI records'. 'Identify IMSI records' leads to 'Location information confirmed by CSS:=False', which has an associated note 'For each identified IMSI record'. Finally, it leads to 'Null'. + +1741 + +1742 + +Figure 19.3.3/7: Process Receive\_Reset\_From\_CSS\_SGSN + +## 1743 19.4 Mobility Management event notification procedure + +### 1744 19.4.1 General + +1745 The Mobility Management event notification procedure is used to notify a gsmSCF about the successful completion of a + 1746 Mobility Management event. + +1747 The message flow for Mobility Management event notification is shown in figure 19.4/1. + +![Sequence diagram showing message flow between VLR or SGSN and gsmSCF. Step 1: VLR or SGSN sends a message to gsmSCF. Step 2: gsmSCF sends a response back to VLR or SGSN.](07c40b9688931ac29fe8f71c02a2edcc_img.jpg) + +``` +sequenceDiagram + participant VLR or SGSN + participant gsmSCF + Note right of gsmSCF: 1 + VLR or SGSN->>gsmSCF: + Note left of VLR or SGSN: 2 + gsmSCF-->>VLR or SGSN: +``` + +Sequence diagram showing message flow between VLR or SGSN and gsmSCF. Step 1: VLR or SGSN sends a message to gsmSCF. Step 2: gsmSCF sends a response back to VLR or SGSN. + +1748 + +1749 + +1750 1) MAP\_REPORT\_MM\_EVENT\_req/ind + +1751 2) MAP\_REPORT\_MM\_EVENT\_rsp/cnf + +1752 + +1753 + +**Figure 19.5/1: Message flow for Mobility Management event notification** + +## 1754 19.4.2 Procedure in the VLR or SGSN + +1755 The MAP process in the VLR or the SGSN to report a Mobility Management event to the gsmSCF is shown in figure + +1756 19.4/2. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as + +1757 follows: + +1758    Receive\_Open\_Cnf       see clause 25.1.2; + +1759    Check\_Confirmation:     see clause 25.2.2. + +## 1760 19.4.3 Procedure in the gsmSCF + +1761 The MAP process in the gsmSCF to handle the report of a Mobility Management event is shown in figure 19.4/3. The + +1762 MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1763    Receive\_Open\_Ind       see clause 25.1.1; + +![Flowchart for process Notify_MM_Event_VLR_Or_SGSN. The process starts with an initial state, followed by a 'Null' state. It then sends an MM event notification. A decision block on the right lists MAP_OPEN_req, MAP_REPORT_MM_EVENT_req, and MAP_DELIMITER_req. The flow proceeds to 'Receive_Open_Cnf'. From there, an 'OK' path leads to 'Wait_For_gsmSCF_Response', while a 'Vr, Error' path leads to an 'Abort' state and then 'Null'. From 'Wait_For_gsmSCF_Response', three paths emerge: 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req', a middle path leading to a block with 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind', and 'MAP_REPORT_MM_EVENT_cnf' leading to 'Check_Confirmation'. 'MAP_CLOSE_req' leads to 'Set negative response: System failure'. The middle block leads to 'Set negative response: System failure'. 'Check_Confirmation' has three outcomes: 'Provider Error, Data Error' leading to 'Set negative response: System failure', 'User Error' leading to 'Set negative response', and 'OK' leading to a decision block. All three 'Set negative response' blocks lead to a merge point. From this merge point, one path leads to a decision block for 'Send MM event notification negative response' and then to 'Null'. The 'OK' path from 'Check_Confirmation' leads to a decision block for 'Send MM event notification ack' and then to 'Null'.](a125eb91cd79c79645898152eb2a9c94_img.jpg) + +process Notify\_MM\_Event\_VLR\_Or\_SGSN + +NMME\_VLR\_SGSN1(1) + +Process in the VLR or SGSN to notify the gsmSCF of a mobility management event + +Signals to/from the left are to/from the location management application process in the VLR (see 3GPP TS 23.012) or the GPRS mobility management application process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/from the gsmSCF + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> SendMM[Send MM event notification] + SendMM --> Decision1{ } + Decision1 -.->|MAP_OPEN_req +MAP_REPORT_MM_EVENT_req +MAP_DELIMITER_req| Right1[ ] + Decision1 --> RecvOpen[Receive_Open_Cnf] + RecvOpen -- OK --> WaitGsmSCF([Wait_For_gsmSCF_Response]) + RecvOpen -- Vr, Error --> Abort{Abort} + Abort --> Null2([Null]) + WaitGsmSCF --> Decision2{ } + Decision2 -- MAP_NOTICE_ind --> MAPCloseReq[MAP_CLOSE_req] + MAPCloseReq --> NegSysFail1[Set negative response: System failure] + Decision2 --> MiddleBlock[ ] + MiddleBlock -.->|MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind| MiddleBlock + MiddleBlock --> NegSysFail2[Set negative response: System failure] + Decision2 -- MAP_REPORT_MM_EVENT_cnf --> CheckConf[Check_Confirmation] + CheckConf -- "Provider Error, Data Error" --> NegSysFail3[Set negative response: System failure] + CheckConf -- User Error --> NegResp[Set negative response] + CheckConf -- OK --> Decision3{ } + NegSysFail1 --> Merge1(( )) + NegSysFail2 --> Merge1 + NegResp --> Merge1 + Merge1 --> Decision4{ } + Decision4 -.->|Send MM event notification negative response| Decision4 + Decision4 --> Null3([Null]) + Decision3 --> Decision5{ } + Decision5 -.->|Send MM event notification ack| Decision5 + Decision5 --> Null4([Null]) + +``` + +Flowchart for process Notify\_MM\_Event\_VLR\_Or\_SGSN. The process starts with an initial state, followed by a 'Null' state. It then sends an MM event notification. A decision block on the right lists MAP\_OPEN\_req, MAP\_REPORT\_MM\_EVENT\_req, and MAP\_DELIMITER\_req. The flow proceeds to 'Receive\_Open\_Cnf'. From there, an 'OK' path leads to 'Wait\_For\_gsmSCF\_Response', while a 'Vr, Error' path leads to an 'Abort' state and then 'Null'. From 'Wait\_For\_gsmSCF\_Response', three paths emerge: 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req', a middle path leading to a block with 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind', and 'MAP\_REPORT\_MM\_EVENT\_cnf' leading to 'Check\_Confirmation'. 'MAP\_CLOSE\_req' leads to 'Set negative response: System failure'. The middle block leads to 'Set negative response: System failure'. 'Check\_Confirmation' has three outcomes: 'Provider Error, Data Error' leading to 'Set negative response: System failure', 'User Error' leading to 'Set negative response', and 'OK' leading to a decision block. All three 'Set negative response' blocks lead to a merge point. From this merge point, one path leads to a decision block for 'Send MM event notification negative response' and then to 'Null'. The 'OK' path from 'Check\_Confirmation' leads to a decision block for 'Send MM event notification ack' and then to 'Null'. + +1764 + +1765 + +Figure 19.4/2: Process Notify\_MM\_Event\_VLR\_Or\_SGSN + +![Flowchart for process Notify_MM_Event_gsmSCF. It starts with an initial state, followed by 'Null', 'Receive_Open_Ind', and a decision 'OK' vs 'Vr, Error'. The 'OK' path leads to 'Wait_For_Service_Primitive', which then branches into three paths: 'MAP_P_ABORT_ind' (leading to 'Null'), 'MAP_REPORT_MM_EVENT_ind' (leading to 'Report MM Event' and then 'Wait_For_Application_Response'), and 'MAP_NOTICE_ind' (leading to 'MAP_CLOSE_req' and then 'Null'). From 'Wait_For_Application_Response', it branches into 'Report MM Event ack' (leading to 'Set Result') and 'Report MM Event negative response' (leading to 'Set User Error'). Both 'Set Result' and 'Set User Error' lead to a merge point, which then leads to 'MAP_REPORT_MM_EVENT_rsp' / 'MAP_CLOSE_req' and finally 'Null'.](fadcd3e9a0aec99f497cb697846fbf7f_img.jpg) + +process Notify\_MM\_Event\_gsmSCF + +NMME\_SCF1(1) + +Process in the gsmSCF to handle the notification of a mobility management event + +Signals to/from the left are to/from the VLR or SGSN; signals to/from the right are to/from the service logic application process in the gsmSCF + +``` + +graph TD + Start([ ]) --> Null1[Null] + Null1 --> Receive[Receive_Open_Ind] + Receive --> OK{OK} + OK -- Vr, Error --> Null2[Null] + OK --> WaitService[Wait_For_Service_Primitive] + WaitService --> MAP_ABORT{MAP_P_ABORT_ind} + WaitService --> MAP_REPORT{MAP_REPORT_MM_EVENT_ind} + WaitService --> MAP_NOTICE{MAP_NOTICE_ind} + MAP_ABORT --> Null3[Null] + MAP_REPORT --> ReportMM[Report MM Event] + ReportMM --> WaitApp[Wait_For_Application_Response] + MAP_NOTICE --> MAP_CLOSE_req{MAP_CLOSE_req} + MAP_CLOSE_req --> Null4[Null] + WaitApp --> ReportAck{Report MM Event ack} + WaitApp --> ReportNeg{Report MM Event negative response} + ReportAck --> SetResult[Set Result] + ReportNeg --> SetUserError[Set User Error] + SetResult --> Merge{ } + SetUserError --> Merge + Merge --> RspClose{MAP_REPORT_MM_EVENT_rsp +MAP_CLOSE_req} + RspClose --> Null5[Null] + +``` + +Flowchart for process Notify\_MM\_Event\_gsmSCF. It starts with an initial state, followed by 'Null', 'Receive\_Open\_Ind', and a decision 'OK' vs 'Vr, Error'. The 'OK' path leads to 'Wait\_For\_Service\_Primitive', which then branches into three paths: 'MAP\_P\_ABORT\_ind' (leading to 'Null'), 'MAP\_REPORT\_MM\_EVENT\_ind' (leading to 'Report MM Event' and then 'Wait\_For\_Application\_Response'), and 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req' and then 'Null'). From 'Wait\_For\_Application\_Response', it branches into 'Report MM Event ack' (leading to 'Set Result') and 'Report MM Event negative response' (leading to 'Set User Error'). Both 'Set Result' and 'Set User Error' lead to a merge point, which then leads to 'MAP\_REPORT\_MM\_EVENT\_rsp' / 'MAP\_CLOSE\_req' and finally 'Null'. + +1766 + +1767 + +Figure 19.4/3: Process Notify\_MM\_Event\_gsmSCF + +## 1768 19.5 HLR Insert Subscriber Data macros + +### 1769 19.5.1 Macro Insert\_Subs\_Data\_Framed\_HLR + +1770 This macro is used to transfer subscriber data to the VLR as part of an existing dialogue for location updating or data +1771 restoration. The macro invokes a macro and a process not defined in this clause; the definitions of the macro and the +1772 process can be found as follows: + +1773     Wait\_For\_Insert\_Subs\_Data\_Cnf see clause 25.7.5; + +1774     Send\_Insert\_Subs\_Data\_HLR: see clause 25.7.7. + +1775 The HLR may wait for each MAP\_INSERT\_SUBSCRIBER\_DATA request to be acknowledged before it sends the +1776 next request, or it may handle the requests and the confirmations in parallel. + +1777 If the VLR has indicated that it does not support a service or feature (e.g. Closed User Group or Advice Of Charge +1778 Charging Level) which the HLR operator regards as essential for the subscriber, the macro + +1779 Wait\_for\_Insert\_Subs\_Data\_Cnf takes the Replace\_Service exit; the HLR sets the Roaming Restriction Due To +1780 Unsupported Feature flag to roaming restricted and sends Roaming Restriction Due To Unsupported Feature in a +1781 subsequent MAP\_INSERT\_SUBSCRIBER\_DATA request. + +1782 If the HLR operator does not regard the unsupported service or feature as essential for the subscriber but the macro +1783 Wait\_for\_Insert\_Subs\_Data\_Cnf takes the Replace\_Service exit, the HLR sends the data for a replacement service in a +1784 subsequent MAP\_INSERT\_SUBSCRIBER\_DATA request. + +1785 If subscriber data for CAMEL Phase 2 or later services are sent to a VLR which does not support the appropriate phase +1786 of CAMEL, the service behaviour may be unpredictable or incorrect. The HLR should therefore ensure that at the +1787 conclusion of a stand alone Insert Subscriber data procedure the data in the VLR do not require a capability that the +1788 VLR does not have. Possible mechanisms to ensure this are described in 3GPP TS 23.078 [98]. + +1789 The HLR should send a Forwarded-to number which is not in E.164 international format to the VLR only when the +1790 HLR has ascertained that the VLR supports CAMEL Phase 2 or later. Thus, the ISD message containing the +1791 Forwarded-to number which is not in E.164 international format shall be sent to the VLR only if the HLR previously +1792 received confirmation from the VLR at Location Update that CAMEL Phase 2 or later is supported. + +### 1793 19.5.2 Macro Insert\_GPRS\_Subs\_Data\_Framed\_HLR + +1794 This macro is used to transfer subscriber data to the SGSN as part of an existing dialogue for location updating. The +1795 macro invokes a macro and a process not defined in this clause; the definitions of the macro and the process can be +1796 found as follows: + +1797     Wait\_For\_Insert\_GPRS\_Subs\_Data\_Cnf see clause 25.7.5; + +1798     Send\_Insert\_Subs\_Data\_HLR: see clause 25.7.7. + +1799 The HLR may wait for each MAP\_INSERT\_SUBSCRIBER\_DATA request to be acknowledged before it sends the +1800 next request, or it may handle the requests and the confirmations in parallel. + +1801 If the SGSN has indicated that it does not support a service or feature which the HLR operator regards as essential for +1802 the subscriber, the macro Wait\_for\_Insert\_GPRS\_Subs\_Data\_Cnf takes the Replace\_Service exit; the HLR sets the +1803 Roaming Restricted In SGSN Due To Unsupported Feature flag to roaming restricted and sends Roaming Restricted In +1804 SGSN Due To Unsupported Feature in a subsequent MAP\_INSERT\_SUBSCRIBER\_DATA request. + +1805 If the HLR operator does not regard the unsupported service or feature as essential for the subscriber but the macro +1806 Wait\_for\_Insert\_GPRS\_Subs\_Data\_Cnf takes the Replace\_Service exit, the HLR sends the data for a replacement +1807 service in a subsequent MAP\_INSERT\_SUBSCRIBER\_DATA request. + +![Flowchart for macrodefinition Insert_Subs_Data_Framed_HLR. The process starts with an entry point, followed by sending MAP_INSERT_SUBSCRIBER_DATA_req and MAP_DELIMITER_req. It then initializes Count:=1 and checks if all data is inserted. If not, it sends Insert_Subs_Data_HLR, increments Count, and loops back. If all data is inserted, it waits for a confirmation. The confirmation can be OK, Replace_Service, Error, or Abort. OK leads to Count:=Count-1 and a loop back if Count>0. Replace_Service leads to setting replacement services, Count:=Count-1, and an exit point. Error leads to an Error exit point. Abort leads to an Aborted state. If Count>0 is false, it checks for network node area restrictions. If none, it sets MSC Area restricted to Not restricted. If restricted, it sets MSC Area restricted to Restricted. Both lead to an OK exit point.](e8820d8ca264fb5f85d8cd4e4a9c4c2a_img.jpg) + +macrodefinition Insert\_Subs\_Data\_Framed\_HLR + +ISDF\_HLR1(1) + +Macro in the HLR to transfer subscriber data to the VLR in an existing dialogue + +Signals to the left are to the VLR + +``` + +graph TD + Entry([ ]) --> Out1{{ )) + Out1 -- "MAP_INSERT_SUBSCRIBER_DATA_req +MAP_DELIMITER_req" --> Count1[Count:=1] + Count1 --> AllData{All data inserted?} + AllData -- No --> Send[Send Insert_Subs_Data_HLR] + Send --> CountInc[Count:=Count+1] + CountInc --> AllData + AllData -- Yes --> Wait[Wait For Insert_Subs_Data_Cnf] + Wait -- OK --> CountDec1[Count:=Count-1] + CountDec1 --> CountGT0{Count>0?} + CountGT0 -- Yes --> Wait + CountGT0 -- No --> Restricted{Network node area restricted received OR Roaming Restriction due to Unsupported Feature?} + Wait -- Replace_Service --> Set[Set replacement service(s)] + Set --> CountDec2[Count:=Count-1] + CountDec2 --> Exit1((1)) + Wait -- Error --> Error((Error)) + Wait -- Abort --> Aborted[Aborted] + Restricted -- Yes --> MSCRestricted[MSC Area restricted:= Restricted] + Restricted -- No --> MSCNotRestricted[MSC Area restricted:= Not restricted] + MSCRestricted --> ExitOK((OK)) + MSCNotRestricted --> ExitOK + +``` + +Flowchart for macrodefinition Insert\_Subs\_Data\_Framed\_HLR. The process starts with an entry point, followed by sending MAP\_INSERT\_SUBSCRIBER\_DATA\_req and MAP\_DELIMITER\_req. It then initializes Count:=1 and checks if all data is inserted. If not, it sends Insert\_Subs\_Data\_HLR, increments Count, and loops back. If all data is inserted, it waits for a confirmation. The confirmation can be OK, Replace\_Service, Error, or Abort. OK leads to Count:=Count-1 and a loop back if Count>0. Replace\_Service leads to setting replacement services, Count:=Count-1, and an exit point. Error leads to an Error exit point. Abort leads to an Aborted state. If Count>0 is false, it checks for network node area restrictions. If none, it sets MSC Area restricted to Not restricted. If restricted, it sets MSC Area restricted to Restricted. Both lead to an OK exit point. + +1808 + +1809 + +Figure 19.5/1: Macro Insert\_Subs\_Data\_Framed\_HLR + +macrodefinition Insert\_GPRS\_Subs\_Data\_Framed\_HLR + +IGSDF\_HLR1(1) + +Macro in the HLR to transfer subscriber data to the SGSN in an existing dialogue + +Signals to the left are to the VLR + +![Flowchart for Insert_GPRS_Subs_Data_Framed_HLR macro. It starts with an entry point, followed by MAP_INSERT_SUBSCRIBER_DATA_req and MAP_DELIMITER_req messages. A loop begins with Count:=1 and a decision 'All data inserted?'. If 'No', it goes to 'Send Insert_Subs_Data_HLR', increments Count, and loops back. If 'Yes', it goes to 'Wait_For_Insert_GPRS_Subs_Data_Cnf'. From there, four outcomes are possible: 'OK' leads to Count:=Count-1 and a 'Count>0?' decision; 'Replace_Service' leads to 'Set replacement service(s)', then Count:=Count-1, and then to connector '1'; 'Error' leads to an 'Error' connector; 'Abort' leads to an 'Abort' connector. If 'Count>0?' is 'Yes', it loops back to the 'All data inserted?' decision. If 'No', it goes to a decision 'Network node area restricted received OR Roaming Restricted in SGSN due to Unsupported Feature?'. If 'Yes', it sets 'SGSN Area restricted:= Restricted'; if 'No', it sets 'SGSN Area restricted:= Not restricted'. Both lead to an 'OK' connector.](fdcb84b9824ff628439843df1ab772d7_img.jpg) + +``` + +graph TD + Entry([ ]) --> In(( )) + In --> Msg["MAP_INSERT_SUBSCRIBER_DATA_req +MAP_DELIMITER_req"] + Msg --> Count1["Count:=1"] + Count1 --> AllData{All data inserted?} + AllData -- No --> Send["Send Insert_Subs_Data_HLR"] + Send --> CountInc["Count:=Count+1"] + CountInc --> AllData + AllData -- Yes --> Wait["Wait_For_Insert_GPRS_Subs_Data_Cnf"] + Wait -- OK --> CountDec1["Count:=Count-1"] + CountDec1 --> CountGT0{Count>0?} + CountGT0 -- Yes --> AllData + CountGT0 -- No --> NetRestrict{Network node area restricted received OR +Roaming Restricted in SGSN due to Unsupported Feature?} + Wait -- Replace_Service --> SetService["Set replacement service(s)"] + SetService --> CountDec2["Count:=Count-1"] + CountDec2 --> Conn1((1)) + Wait -- Error --> ErrorConn((Error)) + Wait -- Abort --> AbortConn(( )) + AbortConn --> Aborted[Aborted] + NetRestrict -- Yes --> RestrictYes["SGSN Area restricted:= Restricted"] + NetRestrict -- No --> RestrictNo["SGSN Area restricted:= Not restricted"] + RestrictYes --> OKConn((OK)) + RestrictNo --> OKConn + +``` + +Flowchart for Insert\_GPRS\_Subs\_Data\_Framed\_HLR macro. It starts with an entry point, followed by MAP\_INSERT\_SUBSCRIBER\_DATA\_req and MAP\_DELIMITER\_req messages. A loop begins with Count:=1 and a decision 'All data inserted?'. If 'No', it goes to 'Send Insert\_Subs\_Data\_HLR', increments Count, and loops back. If 'Yes', it goes to 'Wait\_For\_Insert\_GPRS\_Subs\_Data\_Cnf'. From there, four outcomes are possible: 'OK' leads to Count:=Count-1 and a 'Count>0?' decision; 'Replace\_Service' leads to 'Set replacement service(s)', then Count:=Count-1, and then to connector '1'; 'Error' leads to an 'Error' connector; 'Abort' leads to an 'Abort' connector. If 'Count>0?' is 'Yes', it loops back to the 'All data inserted?' decision. If 'No', it goes to a decision 'Network node area restricted received OR Roaming Restricted in SGSN due to Unsupported Feature?'. If 'Yes', it sets 'SGSN Area restricted:= Restricted'; if 'No', it sets 'SGSN Area restricted:= Not restricted'. Both lead to an 'OK' connector. + +1810 + +1811 + +Figure 19.5/2: Macro Insert\_GPRS\_Subs\_Data\_Framed\_HLR + +## 1812 19.5A CSS Insert Subscriber Data macros + +### 1813 19.5A.1 Macro Insert\_VCSG\_Subs\_Data\_Framed\_CSS + +1814 This macro is used to transfer CSG subscriber data from the CSS to the VLR or the SGSN as part of an existing +1815 dialogue for VCSG location updating. The macro invokes a macro and a process not defined in this clause; the +1816 definitions of the macro and the process can be found as follows: + +1817     Wait\_For\_Insert\_VCSG\_Subs\_Data\_Cnf see clause 25.7.9; + +1818     Send\_Insert\_VCSG\_Subs\_Data\_CSS: see clause 25.7.10. + +1819 The CSS may wait for each MAP\_INSERT\_SUBSCRIBER\_DATA request to be acknowledged before it sends the +1820 next request, or it may handle the requests and the confirmations in parallel. + +1821 If the VLR or the SGSN has indicated that it does not support a service or feature which the CSS operator regards as +1822 essential for the subscriber, the macro Wait\_for\_Insert\_VCSG\_Subs\_Data\_Cnf takes the Replace\_Service exit. + +1823 If the CSS operator does not regard the unsupported service or feature as essential for the subscriber but the macro +1824 Wait\_for\_Insert\_VCSG\_Subs\_Data\_Cnf takes the Replace\_Service exit, the CSS sends the data for a replacement +1825 service in a subsequent MAP\_INSERT\_SUBSCRIBER\_DATA request. + +1826 + +![Flowchart for Insert_VCSG_Subs_Data_Framed_CSS macro. It starts with an entry point, followed by MAP_INSERT_SUBSCRIBER_DATA_req and MAP_DELIMITER_req signals. Count is initialized to 1. A loop begins with 'All data inserted?' decision. If No, it goes to 'Send_Insert_VCSG_Subs_Data_CSS', increments Count, and loops back. If Yes, it goes to 'Wait_For_Insert_VCSG_Subs_Data_Cnf'. From there, four paths exist: OK (decrements Count, checks if Count > 0), Replace_Service (sets replacement services, decrements Count), Error (ends in Error state), and Abort (ends in Aborted state). If Count > 0 after OK or Replace_Service, it loops back to 'All data inserted?'. If Count = 0, it ends in OK state.](341c5e236a73f03a1cc436237fe64d8e_img.jpg) + +**macrodefinition Insert\_VCSG\_Subs\_Data\_Framed\_CSS** IVSDF\_CSS1(1) + +Macro in the CSS to transfer CSG subscriber data to the VLR or the SGSN in an existing dialogue + +Signals to the left are to the VLR or the SGSN + +``` +graph TD; Entry([ ]) --> Signals["MAP_INSERT_SUBSCRIBER_DATA_req +MAP_DELIMITER_req"]; Signals --> Count1["Count:=1"]; Count1 --> AllDataInserted{All data inserted?}; AllDataInserted -- No --> SendInsert["Send_Insert_VCSG_Subs_Data_CSS"]; SendInsert --> CountInc["Count:=Count+1"]; CountInc --> AllDataInserted; AllDataInserted -- Yes --> WaitForCnf["Wait_For_Insert_VCSG_Subs_Data_Cnf"]; WaitForCnf -- OK --> CountDec1["Count:=Count-1"]; WaitForCnf -- Replace_Service --> SetReplacement["Set replacement services(s)"]; SetReplacement --> CountDec2["Count:=Count-1"]; WaitForCnf -- Error --> ErrorState((Error)); WaitForCnf -- Abort --> AbortedState((Aborted)); AbortedState --> Aborted["Aborted"]; CountDec1 --> CountGT0{Count>0?}; CountDec2 --> One1((1)); CountGT0 -- Yes --> AllDataInserted; CountGT0 -- No --> OKState((OK)); +``` + +Flowchart for Insert\_VCSG\_Subs\_Data\_Framed\_CSS macro. It starts with an entry point, followed by MAP\_INSERT\_SUBSCRIBER\_DATA\_req and MAP\_DELIMITER\_req signals. Count is initialized to 1. A loop begins with 'All data inserted?' decision. If No, it goes to 'Send\_Insert\_VCSG\_Subs\_Data\_CSS', increments Count, and loops back. If Yes, it goes to 'Wait\_For\_Insert\_VCSG\_Subs\_Data\_Cnf'. From there, four paths exist: OK (decrements Count, checks if Count > 0), Replace\_Service (sets replacement services, decrements Count), Error (ends in Error state), and Abort (ends in Aborted state). If Count > 0 after OK or Replace\_Service, it loops back to 'All data inserted?'. If Count = 0, it ends in OK state. + +1827 + +1828 + +**Figure 19.5A/1: Macro Insert\_VCSG\_Subs\_Data\_Framed\_CSS** + +--- + +## 1829 20 Operation and maintenance procedures + +### 1830 20.1 General + +1831 The Operation and Maintenance procedures are used to support operation and maintenance of the network. + +1832 The following procedures exist for operation and maintenance purposes: + +- 1833 i) Tracing procedures; +- 1834 ii) Subscriber Data Management procedures; +- 1835 iii) Subscriber Identity procedure. + +1836 The following application contexts refer to complex MAP Users consisting of several processes: + +- 1837 - subscriberDataManagementContext; +- 1838 - tracingContext. + +1839 Each of these two application contexts needs a co-ordinating process in the VLR or in the SGSN as described in the +1840 following clauses. + +#### 1841 20.1.1 Tracing Co-ordinator for the VLR + +1842 The Tracing Co-ordinator process in the VLR is shown in figure 20.1/1. The MAP process invokes a macro not +1843 defined in this clause; the definition of this macro can be found as follows: + +1844     Receive\_Open\_Ind     see clause 25.1.1. + +#### 1845 20.1.2 Tracing Co-ordinator for the SGSN + +1846 The Tracing Co-ordinator process in the SGSN is shown in figure 20.1/2. The MAP process invokes a macro not +1847 defined in this clause; the definition of this macro can be found as follows: + +1848     Receive\_Open\_Ind     see clause 25.1.1. + +#### 1849 20.1.3 Subscriber Data Management Co-ordinator for the VLR + +1850 The Subscriber Data Management Co-ordinator process in the VLR is shown in figure 20.1/3 and figure 20.1/5. The +1851 MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1852     Receive\_Open\_Ind     see clause 25.1.1. + +#### 1853 20.1.4 Subscriber Data Management Co-ordinator for the SGSN + +1854 The Subscriber Data Management Co-ordinator process in the SGSN is shown in figure 20.1/4 and figure 20.1/6. The +1855 MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1856     Receive\_Open\_Ind     see clause 25.1.1. + +![Flowchart for process Co_Tracing_VLR. It starts with an entry point leading to 'Null', then 'Receive_Open_ind' (referencing Figure 25.1/1). From 'Receive_Open_ind', three paths emerge: 'Vr' leading to 'Perform MAP Vr dialogue' then 'Null'; 'OK' leading to 'Wait_For_Service_Primitive'; and 'Error' leading to 'Null'. 'Wait_For_Service_Primitive' branches into four parallel paths: 1) 'MAP_ACTIVATE_TRACE_MODE_ind' leading to 'ATM_Stand_Alone_VLR' (referencing Figure 20.2/10) then 'MAP_ACTIVATE_TRACE_MODE_ind' (outward) then 'Relay_Info'; 2) 'MAP_DEACTIVATE_TRACE_MODE_ind' leading to 'DTM_Stand_Alone_VLR' (referencing Figure 20.2/14) then 'MAP_DEACTIVATE_TRACE_MODE_ind' (outward) then 'Relay_Info'; 3) 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req' then 'Null'; 4) 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' (outward) then 'Null'. All four 'Relay_Info' blocks from the first two paths lead to a common 'Relay_Info' block. This 'Relay_Info' block branches into four parallel paths: 1) 'MAP_U_ABORT_req, MAP_CLOSE_req' (outward) then '-' (outward) then 'Null'; 2) '*' (outward) then '-' (outward) then 'Relay_Info'; 3) 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' (outward) then '-' (outward) then 'Null'; 4) '*' (outward) then '-' (outward) then 'Relay_Info'.](a72557efa52586542f028f0a62ff9cf5_img.jpg) + +**process Co\_Tracing\_VLR** **Co\_Tr\_VLR1(1)** + +Co-ordinating process in the VLR to handle a dialogue opening request using the application context tracingContext + +Signals to/from the left are to/from the child process; signals to/from the right are to/from the HLR + +``` + +graph TD + Entry([ ]) --> Null1([Null]) + Null1 --> Receive_Open_ind[Receive_Open_ind] + Receive_Open_ind -.-> F25_1_1[Figure 25.1/1] + Receive_Open_ind -- Vr --> Perform_Vr[Perform MAP Vr dialogue] + Perform_Vr --> Null2([Null]) + Receive_Open_ind -- OK --> Wait_For_Primitive[Wait_For_Service_Primitive] + Receive_Open_ind -- Error --> Null3([Null]) + Wait_For_Primitive --> MAP_ACTIVATE_ind[MAP_ACTIVATE_TRACE_MODE_ind] + Wait_For_Primitive --> MAP_DEACTIVATE_ind[MAP_DEACTIVATE_TRACE_MODE_ind] + Wait_For_Primitive --> MAP_NOTICE_ind[MAP_NOTICE_ind] + Wait_For_Primitive --> MAP_U_ABORT_ind[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + MAP_ACTIVATE_ind --> ATM_Stand_Alone_VLR[ATM_Stand_Alone_VLR] + ATM_Stand_Alone_VLR -.-> F20_2_10[Figure 20.2/10] + ATM_Stand_Alone_VLR --> MAP_ACTIVATE_out[MAP_ACTIVATE_TRACE_MODE_ind] + MAP_DEACTIVATE_ind --> DTM_Stand_Alone_VLR[DTM_Stand_Alone_VLR] + DTM_Stand_Alone_VLR -.-> F20_2_14[Figure 20.2/14] + DTM_Stand_Alone_VLR --> MAP_DEACTIVATE_out[MAP_DEACTIVATE_TRACE_MODE_ind] + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> Null4([Null]) + MAP_U_ABORT_ind --> Null5([Null]) + MAP_ACTIVATE_out --> Relay_Info1[Relay_Info] + MAP_DEACTIVATE_out --> Relay_Info2[Relay_Info] + Relay_Info1 --> Relay_Info3[Relay_Info] + Relay_Info2 --> Relay_Info3 + Relay_Info3 --> MAP_U_ABORT_req[MAP_U_ABORT_req, MAP_CLOSE_req] + Relay_Info3 --> Star1[*] + Relay_Info3 --> MAP_U_ABORT_ind2[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Relay_Info3 --> Star2[*] + MAP_U_ABORT_req --> Dash1[-] + Dash1 --> Null6([Null]) + Star1 --> Dash2[-] + Dash2 --> Relay_Info4[Relay_Info] + MAP_U_ABORT_ind2 --> Dash3[-] + Dash3 --> Null7([Null]) + Star2 --> Dash4[-] + Dash4 --> Relay_Info5[Relay_Info] + +``` + +Flowchart for process Co\_Tracing\_VLR. It starts with an entry point leading to 'Null', then 'Receive\_Open\_ind' (referencing Figure 25.1/1). From 'Receive\_Open\_ind', three paths emerge: 'Vr' leading to 'Perform MAP Vr dialogue' then 'Null'; 'OK' leading to 'Wait\_For\_Service\_Primitive'; and 'Error' leading to 'Null'. 'Wait\_For\_Service\_Primitive' branches into four parallel paths: 1) 'MAP\_ACTIVATE\_TRACE\_MODE\_ind' leading to 'ATM\_Stand\_Alone\_VLR' (referencing Figure 20.2/10) then 'MAP\_ACTIVATE\_TRACE\_MODE\_ind' (outward) then 'Relay\_Info'; 2) 'MAP\_DEACTIVATE\_TRACE\_MODE\_ind' leading to 'DTM\_Stand\_Alone\_VLR' (referencing Figure 20.2/14) then 'MAP\_DEACTIVATE\_TRACE\_MODE\_ind' (outward) then 'Relay\_Info'; 3) 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req' then 'Null'; 4) 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' (outward) then 'Null'. All four 'Relay\_Info' blocks from the first two paths lead to a common 'Relay\_Info' block. This 'Relay\_Info' block branches into four parallel paths: 1) 'MAP\_U\_ABORT\_req, MAP\_CLOSE\_req' (outward) then '-' (outward) then 'Null'; 2) '\*' (outward) then '-' (outward) then 'Relay\_Info'; 3) 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' (outward) then '-' (outward) then 'Null'; 4) '\*' (outward) then '-' (outward) then 'Relay\_Info'. + +1857 + +1858 + +**Figure 20.1/1: Process Co\_Tracing\_VLR** + +![Flowchart for process Co_Tracing_SGSN. It starts with an entry point leading to 'Null', then 'Receive_Open_ind' (linked to Figure 25.1/1). From 'Receive_Open_ind', three paths emerge: 'Vr' leads to 'Perform MAP Vr dialogue' then 'Null'; 'OK' leads to 'Wait_For_Service_Primitive'; 'Error' leads to 'Null'. 'Wait_For_Service_Primitive' branches into four paths: 1) 'MAP_ACTIVATE_TRACE_MODE_ind' leads to 'ATM_Stand_Alone_SGSN' (linked to Figure 20.2/11) then 'MAP_ACTIVATE_TRACE_MODE_ind' (outward) then 'Relay_Info'; 2) 'MAP_DEACTIVATE_TRACE_MODE_ind' leads to 'DTM_Stand_Alone_SGSN' (linked to Figure 20.2/15) then 'MAP_DEACTIVATE_TRACE_MODE_ind' (outward) then 'Relay_Info'; 3) 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req' then 'Null'; 4) 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' (outward) then 'Relay_Info'. All four 'Relay_Info' blocks lead to a final section with four parallel paths: 1) 'MAP_U_ABORT_req, MAP_CLOSE_req' (outward) then 'Null'; 2) '*' (outward) then 'Relay_Info'; 3) 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' (outward) then 'Null'; 4) '*' (outward) then 'Relay_Info'.](cbf400f805c12c870d53a2cce2a45ae4_img.jpg) + +**process Co\_Tracing\_SGSN** **Co\_Tr\_SGSN1(1)** + +Co-ordinating process in the SGSN to handle a dialogue opening request using the application context tracingContext + +Signals to/from the left are to/from the child process; signals to/from the right are to/from the HLR + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_ind[Receive_Open_ind] + Receive_Open_ind -.-> F25_1_1[Figure 25.1/1] + + Receive_Open_ind -- Vr --> Perform_Vr[Perform MAP Vr dialogue] + Perform_Vr --> Null2([Null]) + + Receive_Open_ind -- OK --> Wait_For_Service_Primitive[Wait_For_Service_Primitive] + + Receive_Open_ind -- Error --> Null3([Null]) + + Wait_For_Service_Primitive --> MAP_ACTIVATE_TRACE_MODE_ind_in1[MAP_ACTIVATE_TRACE_MODE_ind] + MAP_ACTIVATE_TRACE_MODE_ind_in1 --> ATM_Stand_Alone_SGSN[ATM_Stand_Alone_SGSN] + ATM_Stand_Alone_SGSN -.-> F20_2_11[Figure 20.2/11] + + Wait_For_Service_Primitive --> MAP_DEACTIVATE_TRACE_MODE_ind_in1[MAP_DEACTIVATE_TRACE_MODE_ind] + MAP_DEACTIVATE_TRACE_MODE_ind_in1 --> DTM_Stand_Alone_SGSN[DTM_Stand_Alone_SGSN] + DTM_Stand_Alone_SGSN -.-> F20_2_15[Figure 20.2/15] + + Wait_For_Service_Primitive --> MAP_NOTICE_ind_in[MAP_NOTICE_ind] + + Wait_For_Service_Primitive --> MAP_U_ABORT_ind_in[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + + ATM_Stand_Alone_SGSN --> MAP_ACTIVATE_TRACE_MODE_ind_out1[MAP_ACTIVATE_TRACE_MODE_ind] + + DTM_Stand_Alone_SGSN --> MAP_DEACTIVATE_TRACE_MODE_ind_out1[MAP_DEACTIVATE_TRACE_MODE_ind] + + MAP_NOTICE_ind_in --> MAP_CLOSE_req[MAP_CLOSE_req] + + MAP_U_ABORT_ind_in --> MAP_U_ABORT_ind_out1[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + + MAP_ACTIVATE_TRACE_MODE_ind_out1 --> Relay_Info1[Relay_Info] + MAP_DEACTIVATE_TRACE_MODE_ind_out1 --> Relay_Info2[Relay_Info] + MAP_CLOSE_req --> Null4([Null]) + MAP_U_ABORT_ind_out1 --> Relay_Info3[Relay_Info] + + Relay_Info1 --> MAP_U_ABORT_req[MAP_U_ABORT_req, MAP_CLOSE_req] + MAP_U_ABORT_req --> Null5([Null]) + + Relay_Info2 --> Star1[*] + Star1 --> Relay_Info4[Relay_Info] + + Relay_Info3 --> MAP_U_ABORT_ind_out2[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + MAP_U_ABORT_ind_out2 --> Null6([Null]) + + Relay_Info4 --> Star2[*] + Star2 --> Relay_Info5[Relay_Info] + +``` + +Flowchart for process Co\_Tracing\_SGSN. It starts with an entry point leading to 'Null', then 'Receive\_Open\_ind' (linked to Figure 25.1/1). From 'Receive\_Open\_ind', three paths emerge: 'Vr' leads to 'Perform MAP Vr dialogue' then 'Null'; 'OK' leads to 'Wait\_For\_Service\_Primitive'; 'Error' leads to 'Null'. 'Wait\_For\_Service\_Primitive' branches into four paths: 1) 'MAP\_ACTIVATE\_TRACE\_MODE\_ind' leads to 'ATM\_Stand\_Alone\_SGSN' (linked to Figure 20.2/11) then 'MAP\_ACTIVATE\_TRACE\_MODE\_ind' (outward) then 'Relay\_Info'; 2) 'MAP\_DEACTIVATE\_TRACE\_MODE\_ind' leads to 'DTM\_Stand\_Alone\_SGSN' (linked to Figure 20.2/15) then 'MAP\_DEACTIVATE\_TRACE\_MODE\_ind' (outward) then 'Relay\_Info'; 3) 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req' then 'Null'; 4) 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' (outward) then 'Relay\_Info'. All four 'Relay\_Info' blocks lead to a final section with four parallel paths: 1) 'MAP\_U\_ABORT\_req, MAP\_CLOSE\_req' (outward) then 'Null'; 2) '\*' (outward) then 'Relay\_Info'; 3) 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' (outward) then 'Null'; 4) '\*' (outward) then 'Relay\_Info'. + +1859 + +1860 + +Figure 20.1/2: Process Co\_Tracing\_SGSN + +![State transition diagram for process Co_SDM_VLR. The process starts at an initial state, goes to 'Null', then 'Receive_Open_ind' (linked to Figure 25.1/1). From 'Receive_Open_ind', three paths emerge: 'Vr' leads to 'Perform MAP Vr dialogue' then 'Null'; 'OK' leads to 'Wait_For_Service_Primitive'; 'Error' leads to 'Null'. 'Wait_For_Service_Primitive' branches into four paths: 1) 'MAP_INSERT_SUBSCRIBER_DATA_ind' leads to 'Ins Subs Data Stand Alone_VLR' (linked to Figure 20.3/9), then 'MAP_INSERT_SUBSCRIBER_DATA_ind', then 'Relay_Info'. 2) 'MAP_DELETE_SUBSCRIBER_DATA_ind' leads to 'Delete Subs Data_VLR' (linked to Figure 20.3/10), then 'MAP_DELETE_SUBSCRIBER_DATA_ind', then 'Relay_Info'. 3) 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req', then 'Null'. 4) 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' leads to 'Null'. All four 'Relay_Info' blocks lead to a final state. The first 'Relay_Info' leads to 'MAP_U_ABORT_req, MAP_CLOSE_req' then 'Null'. The second 'Relay_Info' leads to 'Null'. The third 'Relay_Info' leads to 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' then 'Null'. The fourth 'Relay_Info' leads to 'Null'.](2f3f2aa440b5f97bb36333c1617d1ab3_img.jpg) + +**process Co\_SDM\_VLR** **Co\_SDM\_VLR1(1)** + +Co-ordinating process in the VLR to handle a dialogue opening request using the application context subscriberDataMngtContext + +Signals to/from the left are to/from the child process; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Null1[Null] + Null1 --> Receive_Open_ind[Receive_Open_ind] + Receive_Open_ind --> Vr[Perform MAP Vr dialogue] + Receive_Open_ind --> OK[Wait_For_Service_Primitive] + Receive_Open_ind --> Error[Null] + Vr --> Null2[Null] + OK --> Insert[MAP_INSERT_SUBSCRIBER_DATA_ind] + OK --> Delete[MAP_DELETE_SUBSCRIBER_DATA_ind] + OK --> Notice[MAP_NOTICE_ind] + OK --> Abort[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Insert --> InsSubs[Ins Subs Data Stand Alone_VLR] + InsSubs --> InsertOut[MAP_INSERT_SUBSCRIBER_DATA_ind] + Delete --> DeleteSubs[Delete Subs Data_VLR] + DeleteSubs --> DeleteOut[MAP_DELETE_SUBSCRIBER_DATA_ind] + Notice --> CloseReq[MAP_CLOSE_req] + CloseReq --> Null3[Null] + Abort --> Null4[Null] + InsertOut --> RelayInfo1[Relay_Info] + DeleteOut --> RelayInfo2[Relay_Info] + CloseReq --> Null3 + Abort --> Null4 + RelayInfo1 --> RelayInfo1_1[MAP_U_ABORT_req, MAP_CLOSE_req] + RelayInfo1 --> Null5[Null] + RelayInfo1 --> RelayInfo1_3[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + RelayInfo1 --> Null6[Null] + RelayInfo2 --> Null5 + RelayInfo2 --> Null7[Null] + RelayInfo2 --> Null8[Null] + RelayInfo2 --> Null9[Null] + +``` + +State transition diagram for process Co\_SDM\_VLR. The process starts at an initial state, goes to 'Null', then 'Receive\_Open\_ind' (linked to Figure 25.1/1). From 'Receive\_Open\_ind', three paths emerge: 'Vr' leads to 'Perform MAP Vr dialogue' then 'Null'; 'OK' leads to 'Wait\_For\_Service\_Primitive'; 'Error' leads to 'Null'. 'Wait\_For\_Service\_Primitive' branches into four paths: 1) 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind' leads to 'Ins Subs Data Stand Alone\_VLR' (linked to Figure 20.3/9), then 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind', then 'Relay\_Info'. 2) 'MAP\_DELETE\_SUBSCRIBER\_DATA\_ind' leads to 'Delete Subs Data\_VLR' (linked to Figure 20.3/10), then 'MAP\_DELETE\_SUBSCRIBER\_DATA\_ind', then 'Relay\_Info'. 3) 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req', then 'Null'. 4) 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' leads to 'Null'. All four 'Relay\_Info' blocks lead to a final state. The first 'Relay\_Info' leads to 'MAP\_U\_ABORT\_req, MAP\_CLOSE\_req' then 'Null'. The second 'Relay\_Info' leads to 'Null'. The third 'Relay\_Info' leads to 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' then 'Null'. The fourth 'Relay\_Info' leads to 'Null'. + +1861 + +1862 + +**Figure 20.1/3: Process Co\_SDM\_VLR** + +![Flowchart for process Co_SDM_SGSN. It starts with an initial node leading to 'Null', then 'Receive_Open_ind' (linked to Figure 25.1/1). From 'Receive_Open_ind', an 'OK' path leads to 'Wait_For_Service_Primitive' and a 'Vr, Error' path leads to another 'Null' node. 'Wait_For_Service_Primitive' branches into four parallel paths: 1) MAP_INSERT_SUBSCRIBER_DATA_ind -> Ins_Subs_Data_Stand_Alone_SGSN (linked to Figure 20.3/11) -> MAP_INSERT_SUBSCRIBER_DATA_ind -> Relay_Info. 2) MAP_DELETE_SUBSCRIBER_DATA_ind -> Delete_Subs_Data_SGSN (linked to Figure 20.3/12) -> MAP_DELETE_SUBSCRIBER_DATA_ind -> Relay_Info. 3) MAP_NOTICE_ind -> MAP_CLOSE_req -> Null. 4) MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind -> Null. The 'Relay_Info' from the first two paths branches into four more parallel paths: 1) MAP_U_ABORT_req, MAP_CLOSE_req -> - -> Null. 2) * -> - -> Relay_Info. 3) MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind -> - -> Null. 4) * -> - -> Relay_Info.](b33531f195991b13ef7056eb27220f98_img.jpg) + +**process Co\_SDM\_SGSN** **Co\_SDM\_SGSN1(1)** + +Co-ordinating process in the SGSN to handle a dialogue opening request using the application context subscriberDataMngtContext + +Signals to/from the left are to/from the child process, signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_ind[Receive_Open_ind] + Receive_Open_ind -.-> F25_1_1[Figure 25.1/1] + Receive_Open_ind -- OK --> Wait_For_Service_Primitive[Wait_For_Service_Primitive] + Receive_Open_ind -- "Vr, Error" --> Null2([Null]) + Wait_For_Service_Primitive --> MAP_INSERT_SUBSCRIBER_DATA_ind1[MAP_INSERT_SUBSCRIBER_DATA_ind] + Wait_For_Service_Primitive --> MAP_DELETE_SUBSCRIBER_DATA_ind1[MAP_DELETE_SUBSCRIBER_DATA_ind] + Wait_For_Service_Primitive --> MAP_NOTICE_ind[MAP_NOTICE_ind] + Wait_For_Service_Primitive --> MAP_U_ABORT_ind_etc[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + MAP_INSERT_SUBSCRIBER_DATA_ind1 --> Ins_Subs_Data_Stand_Alone_SGSN[Ins_Subs_Data_Stand_Alone_SGSN] + Ins_Subs_Data_Stand_Alone_SGSN -.-> F20_3_11[Figure 20.3/11] + Ins_Subs_Data_Stand_Alone_SGSN --> MAP_INSERT_SUBSCRIBER_DATA_ind2[MAP_INSERT_SUBSCRIBER_DATA_ind] + MAP_DELETE_SUBSCRIBER_DATA_ind1 --> Delete_Subs_Data_SGSN[Delete_Subs_Data_SGSN] + Delete_Subs_Data_SGSN -.-> F20_3_12[Figure 20.3/12] + Delete_Subs_Data_SGSN --> MAP_DELETE_SUBSCRIBER_DATA_ind2[MAP_DELETE_SUBSCRIBER_DATA_ind] + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> Null3([Null]) + MAP_U_ABORT_ind_etc --> Null4([Null]) + MAP_INSERT_SUBSCRIBER_DATA_ind2 --> Relay_Info1[Relay_Info] + MAP_DELETE_SUBSCRIBER_DATA_ind2 --> Relay_Info1 + Relay_Info1 --> MAP_U_ABORT_req_etc[MAP_U_ABORT_req, MAP_CLOSE_req] + Relay_Info1 --> Star1[*] + Relay_Info1 --> MAP_U_ABORT_ind_etc2[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Relay_Info1 --> Star2[*] + MAP_U_ABORT_req_etc --> Dash1[-] + Dash1 --> Null5([Null]) + Star1 --> Dash2[-] + Dash2 --> Relay_Info2[Relay_Info] + MAP_U_ABORT_ind_etc2 --> Dash3[-] + Dash3 --> Null6([Null]) + Star2 --> Dash4[-] + Dash4 --> Relay_Info3[Relay_Info] + +``` + +Flowchart for process Co\_SDM\_SGSN. It starts with an initial node leading to 'Null', then 'Receive\_Open\_ind' (linked to Figure 25.1/1). From 'Receive\_Open\_ind', an 'OK' path leads to 'Wait\_For\_Service\_Primitive' and a 'Vr, Error' path leads to another 'Null' node. 'Wait\_For\_Service\_Primitive' branches into four parallel paths: 1) MAP\_INSERT\_SUBSCRIBER\_DATA\_ind -> Ins\_Subs\_Data\_Stand\_Alone\_SGSN (linked to Figure 20.3/11) -> MAP\_INSERT\_SUBSCRIBER\_DATA\_ind -> Relay\_Info. 2) MAP\_DELETE\_SUBSCRIBER\_DATA\_ind -> Delete\_Subs\_Data\_SGSN (linked to Figure 20.3/12) -> MAP\_DELETE\_SUBSCRIBER\_DATA\_ind -> Relay\_Info. 3) MAP\_NOTICE\_ind -> MAP\_CLOSE\_req -> Null. 4) MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind -> Null. The 'Relay\_Info' from the first two paths branches into four more parallel paths: 1) MAP\_U\_ABORT\_req, MAP\_CLOSE\_req -> - -> Null. 2) \* -> - -> Relay\_Info. 3) MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind -> - -> Null. 4) \* -> - -> Relay\_Info. + +1863 + +1864 + +**Figure 20.1/4: Process Co\_SDM\_SGSN** + +![State transition diagram for process Co_CSG_SDM_VLR. The diagram shows a sequence of states and transitions. It starts with an initial state leading to 'Null', then 'Receive_Open_Ind' (referencing Figure 25.1/1). From 'Receive_Open_Ind', an 'OK' transition leads to 'Wait_For_Service_Primitive', while a 'Vr, Error' transition leads to another 'Null' state. 'Wait_For_Service_Primitive' leads to a parallel state machine with four branches. The first branch involves 'MAP_INSERT_SUBSCRIBER_DATA_ind', 'Ins_VCSG_Subs_Data_Stand_Alone_VLR' (referencing Figure 20.3A/8), and another 'MAP_INSERT_SUBSCRIBER_DATA_ind' leading to 'Relay_Info'. The second branch involves 'MAP_DELETE_SUBSCRIBER_DATA_ind', 'Delete_VCSG_Subs_Data_VLR' (referencing Figure 20.3A/9), and another 'MAP_DELETE_SUBSCRIBER_DATA_ind' leading to 'Relay_Info'. The third branch involves 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req' and then to 'Null'. The fourth branch involves a transition to a state with 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' leading to 'Relay_Info'. From the first 'Relay_Info' state, four sub-branches lead to final states: 'Null', 'Relay_Info', 'Null', and 'Relay_Info'. These sub-branches involve 'MAP_U_ABORT_req, MAP_CLOSE_req', '*', 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind', and '*'.](68ba0c51631dd29d48b79431e37dbb16_img.jpg) + +**process Co\_CSG\_SDM\_VLR** **Co\_CSG\_SDM\_VLR1(1)** + +Co-ordinating process in the VLR to handle a dialogue opening request using the application context subscriberDataMngtContext + +Signals to/from the left are to/from the child process; signals to/from the right are to/from the CSS + +``` + +stateDiagram-v2 + [*] --> Null1[Null] + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind --> Null2[Null] : Vr, Error + Receive_Open_Ind --> Wait_For_Service_Primitive[Wait_For_Service_Primitive] : OK + Wait_For_Service_Primitive --> Parallel_States + state "Parallel_States" as Parallel_States + state "Branch 1" as Branch1 + state "Branch 2" as Branch2 + state "Branch 3" as Branch3 + state "Branch 4" as Branch4 + Parallel_States --> Branch1 + Parallel_States --> Branch2 + Parallel_States --> Branch3 + Parallel_States --> Branch4 + state "Branch 1" as Branch1 + Branch1 --> B1_S1[MAP_INSERT_SUBSCRIBER_DATA_ind] + B1_S1 --> B1_S2[Ins_VCSG_Subs_Data_Stand_Alone_VLR] + B1_S2 --> B1_S3[MAP_INSERT_SUBSCRIBER_DATA_ind] + B1_S3 --> B1_S4[Relay_Info] + state "Branch 2" as Branch2 + Branch2 --> B2_S1[MAP_DELETE_SUBSCRIBER_DATA_ind] + B2_S1 --> B2_S2[Delete_VCSG_Subs_Data_VLR] + B2_S2 --> B2_S3[MAP_DELETE_SUBSCRIBER_DATA_ind] + B2_S3 --> B2_S4[Relay_Info] + state "Branch 3" as Branch3 + Branch3 --> B3_S1[MAP_NOTICE_ind] + B3_S1 --> B3_S2[MAP_CLOSE_req] + B3_S2 --> B3_S3[Null] + state "Branch 4" as Branch4 + Branch4 --> B4_S1[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + B4_S1 --> B4_S2[Relay_Info] + state "B1_S4" as B1_S4 + B1_S4 --> B1_S4_S1[MAP_U_ABORT_req, MAP_CLOSE_req] + B1_S4_S1 --> B1_S4_S2[-] + B1_S4_S2 --> B1_S4_S3[Null] + B1_S4 --> B1_S4_S4[*] + B1_S4_S4 --> B1_S4_S5[-] + B1_S4_S5 --> B1_S4_S6[Relay_Info] + B1_S4 --> B1_S4_S7[-] + B1_S4_S7 --> B1_S4_S8[Null] + B1_S4 --> B1_S4_S9[*] + B1_S4_S9 --> B1_S4_S10[-] + B1_S4_S10 --> B1_S4_S11[Relay_Info] + +``` + +State transition diagram for process Co\_CSG\_SDM\_VLR. The diagram shows a sequence of states and transitions. It starts with an initial state leading to 'Null', then 'Receive\_Open\_Ind' (referencing Figure 25.1/1). From 'Receive\_Open\_Ind', an 'OK' transition leads to 'Wait\_For\_Service\_Primitive', while a 'Vr, Error' transition leads to another 'Null' state. 'Wait\_For\_Service\_Primitive' leads to a parallel state machine with four branches. The first branch involves 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind', 'Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_VLR' (referencing Figure 20.3A/8), and another 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind' leading to 'Relay\_Info'. The second branch involves 'MAP\_DELETE\_SUBSCRIBER\_DATA\_ind', 'Delete\_VCSG\_Subs\_Data\_VLR' (referencing Figure 20.3A/9), and another 'MAP\_DELETE\_SUBSCRIBER\_DATA\_ind' leading to 'Relay\_Info'. The third branch involves 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req' and then to 'Null'. The fourth branch involves a transition to a state with 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' leading to 'Relay\_Info'. From the first 'Relay\_Info' state, four sub-branches lead to final states: 'Null', 'Relay\_Info', 'Null', and 'Relay\_Info'. These sub-branches involve 'MAP\_U\_ABORT\_req, MAP\_CLOSE\_req', '\*', 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind', and '\*'. + +1865 + +1866 + +Figure 20.1/5: Process Co\_CSG\_SDM\_VLR + +![Flowchart for process Co_CSG_SDM_SGSN. It starts with an initial node leading to 'Null', then 'Receive_Open_Ind' (linked to Figure 25.1/1). From 'Receive_Open_Ind', an 'OK' path leads to 'Wait_For_Service_Primitive' and a 'Vr, Error' path leads to 'Null'. 'Wait_For_Service_Primitive' leads to a horizontal split. The left branch goes through 'MAP_INSERT_SUBSCRIBER_DATA_ind' to 'Ins_VCSG_Subs_Data_SGSN' (linked to Figure 20.3A/10, labeled 'Stand_Alone_SGSN'), then to 'MAP_INSERT_SUBSCRIBER_DATA_ind' again, and finally to 'Relay_Info'. The middle branch goes through 'MAP_DELETE_SUBSCRIBER_DATA_ind' to 'Delete_VCSG_Subs_Data_SGSN' (linked to Figure 20.3A/11), then to 'MAP_DELETE_SUBSCRIBER_DATA_ind', and finally to 'Relay_Info'. The right branch goes through 'MAP_NOTICE_ind' to 'MAP_CLOSE_req', which leads to 'Null'. A fourth branch from the split leads to a box containing 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind', which then leads to 'Relay_Info'. Below the first 'Relay_Info' node, there is another horizontal split. The first path goes through 'MAP_U_ABORT_req, MAP_CLOSE_req' to a '-' node and then to 'Null'. The second path goes through a '*' node, a '-' node, and then to 'Relay_Info'. The third path goes through a '-' node and then to 'Null'. The fourth path goes through 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind', a '*' node, a '-' node, and then to 'Relay_Info'.](be5db98077bb821cfe2d717c02215f0b_img.jpg) + +**process Co\_CSG\_SDM\_SGSN** **Co\_CSG\_SDM\_SGSN1(1)** + +Co-ordinating process in the SGSN to handle a dialogue opening request using the application context subscriberDataMngtContext + +Signals to/from the left are to/from the child process; signals to/from the right are to/from the CSS + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> RecOpen[Receive_Open_Ind] + RecOpen -.-> Fig25_1_1[Figure 25.1/1] + RecOpen -- OK --> WaitFor[Wait_For_Service_Primitive] + RecOpen -- Vr, Error --> Null2([Null]) + WaitFor --> Split1(( )) + Split1 --> InsertInd1[MAP_INSERT_SUBSCRIBER_DATA_ind] + Split1 --> DeleteInd1[MAP_DELETE_SUBSCRIBER_DATA_ind] + Split1 --> NoticeInd[MAP_NOTICE_ind] + Split1 --> OtherInds["MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind"] + InsertInd1 --> InsVCSG[Ins_VCSG_Subs_Data_SGSN] + InsVCSG -.-> Fig20_3A_10[Figure 20.3A/10] + InsVCSG -- Stand_Alone_SGSN --> InsertInd2[MAP_INSERT_SUBSCRIBER_DATA_ind] + DeleteInd1 --> DeleteVCSG[Delete_VCSG_Subs_Data_SGSN] + DeleteVCSG -.-> Fig20_3A_11[Figure 20.3A/11] + DeleteVCSG --> DeleteInd2[MAP_DELETE_SUBSCRIBER_DATA_ind] + NoticeInd --> CloseReq[MAP_CLOSE_req] + CloseReq --> Null3([Null]) + OtherInds --> RelayInfo1[Relay_Info] + InsertInd2 --> RelayInfo1 + DeleteInd2 --> RelayInfo1 + RelayInfo1 --> Split2(( )) + Split2 --> UAbortReq["MAP_U_ABORT_req, MAP_CLOSE_req"] + Split2 --> Star1[*] + Split2 --> Dash1[-] + Split2 --> UAbortInds["MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind"] + Split2 --> Star2[*] + UAbortReq --> Dash2[-] + Dash2 --> Null4([Null]) + Star1 --> Dash3[-] + Dash3 --> RelayInfo2[Relay_Info] + Dash1 --> Null5([Null]) + UAbortInds --> Dash4[-] + Dash4 --> RelayInfo3[Relay_Info] + +``` + +Flowchart for process Co\_CSG\_SDM\_SGSN. It starts with an initial node leading to 'Null', then 'Receive\_Open\_Ind' (linked to Figure 25.1/1). From 'Receive\_Open\_Ind', an 'OK' path leads to 'Wait\_For\_Service\_Primitive' and a 'Vr, Error' path leads to 'Null'. 'Wait\_For\_Service\_Primitive' leads to a horizontal split. The left branch goes through 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind' to 'Ins\_VCSG\_Subs\_Data\_SGSN' (linked to Figure 20.3A/10, labeled 'Stand\_Alone\_SGSN'), then to 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind' again, and finally to 'Relay\_Info'. The middle branch goes through 'MAP\_DELETE\_SUBSCRIBER\_DATA\_ind' to 'Delete\_VCSG\_Subs\_Data\_SGSN' (linked to Figure 20.3A/11), then to 'MAP\_DELETE\_SUBSCRIBER\_DATA\_ind', and finally to 'Relay\_Info'. The right branch goes through 'MAP\_NOTICE\_ind' to 'MAP\_CLOSE\_req', which leads to 'Null'. A fourth branch from the split leads to a box containing 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind', which then leads to 'Relay\_Info'. Below the first 'Relay\_Info' node, there is another horizontal split. The first path goes through 'MAP\_U\_ABORT\_req, MAP\_CLOSE\_req' to a '-' node and then to 'Null'. The second path goes through a '\*' node, a '-' node, and then to 'Relay\_Info'. The third path goes through a '-' node and then to 'Null'. The fourth path goes through 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind', a '\*' node, a '-' node, and then to 'Relay\_Info'. + +1867 + +1868 + +Figure 20.1/6: Process Co\_CSG\_SDM\_SGSN + +1869 **20.2 Tracing procedures** + +1870 Three types of tracing procedures exist: + +- 1871 i) Subscriber tracing management procedures; +- 1872 ii) Subscriber tracing procedures; +- 1873 iii) Event tracing procedures. + +1874 The subscriber tracing management procedures are used to manage the status and the type of the tracing. The subscriber +1875 tracing activation procedure is used at location updating or data restoration when the trace mode of a subscriber is set +1876 active in the HLR or, as a stand alone procedure, when the subscriber is already registered and the trace mode becomes +1877 active in the HLR. The procedures to activate tracing in the VLR are shown in figures 20.2/1 and 20.2/3. The +1878 procedures to activate tracing in the SGSN are shown in figures 20.2/2 and 20.2/4. + +![Sequence diagram for non-GPRS tracing activation involving VLR, HLR, and OMC.](0eb9f817692d7c6ea4ff57e4e31b492c_img.jpg) + +``` + +sequenceDiagram + participant OMC + participant HLR + participant VLR + Note right of OMC: 1) Subscriber Tracing Activation + OMC->>HLR: 2) MAP_ACTIVATE_TRACE_MODE_req/ind + HLR->>VLR: 3) MAP_ACTIVATE_TRACE_MODE_rsp/cnf + HLR->>OMC: 4) Subscriber Tracing Activation Accepted + +``` + +Sequence diagram for non-GPRS tracing activation involving VLR, HLR, and OMC. + +1879 +1880 +1881 +1882 +1883 +1884 +1885 +1886 + +- 1) Subscriber Tracing Activation +- 2) MAP\_ACTIVATE\_TRACE\_MODE\_req/ind +- 3) MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf +- 4) Subscriber Tracing Activation Accepted + +**Figure 20.2/1: Stand-alone subscriber tracing activation procedure for non-GPRS** + +1887 + +![Sequence diagram for GPRS tracing activation involving SGSN, HLR, and OMC.](493232c165f622d2ab5b27b05787e85b_img.jpg) + +``` + +sequenceDiagram + participant OMC + participant HLR + participant SGSN + Note right of OMC: 1) Subscriber Tracing Activation + OMC->>HLR: 2) MAP_ACTIVATE_TRACE_MODE_req/ind + HLR->>SGSN: 3) MAP_ACTIVATE_TRACE_MODE_rsp/cnf + HLR->>OMC: 4) Subscriber Tracing Activation Accepted + +``` + +Sequence diagram for GPRS tracing activation involving SGSN, HLR, and OMC. + +1888 +1889 +1890 +1891 +1892 +1893 +1894 +1895 + +- 1) Subscriber Tracing Activation +- 2) MAP\_ACTIVATE\_TRACE\_MODE\_req/ind +- 3) MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf +- 4) Subscriber Tracing Activation Accepted + +**Figure 20.2/2: Stand-alone subscriber tracing activation procedure for GPRS** + +1896 + +![Sequence diagram for Figure 20.2/3 showing the interaction between VLR and HLR. The sequence consists of four steps: 1) VLR to HLR (MAP_UPDATE_LOCATION or MAP_RESTORE_DATA_req/ind), 2) HLR to VLR (MAP_ACTIVATE_TRACE_MODE_req/ind), 3) VLR to HLR (MAP_ACTIVATE_TRACE_MODE_rsp/cnf), and 4) HLR to VLR (MAP_UPDATE_LOCATION_rsp/cnf or MAP_RESTORE_DATA_rsp/cnf).](0ab41cb59d8d1227f6df86aaa7e9b093_img.jpg) + +``` + +sequenceDiagram + participant VLR + participant HLR + Note right of HLR: 1) + VLR->>HLR: + Note left of VLR: 2) + HLR->>VLR: + Note right of HLR: 3) + VLR->>HLR: + Note left of VLR: 4) + HLR->>VLR: + +``` + +Sequence diagram for Figure 20.2/3 showing the interaction between VLR and HLR. The sequence consists of four steps: 1) VLR to HLR (MAP\_UPDATE\_LOCATION or MAP\_RESTORE\_DATA\_req/ind), 2) HLR to VLR (MAP\_ACTIVATE\_TRACE\_MODE\_req/ind), 3) VLR to HLR (MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf), and 4) HLR to VLR (MAP\_UPDATE\_LOCATION\_rsp/cnf or MAP\_RESTORE\_DATA\_rsp/cnf). + +1897 + +1898 + +1899 1) MAP\_UPDATE\_LOCATION or MAP\_RESTORE\_DATA\_req/ind + +1900 + +2) MAP\_ACTIVATE\_TRACE\_MODE\_req/ind + +1901 + +3) MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf + +1902 + +4) MAP\_UPDATE\_LOCATION\_rsp/cnf or MAP\_RESTORE\_DATA\_rsp/cnf + +1903 + +1904 + +**Figure 20.2/3: Subscriber tracing activation procedure at location updating or data restoration** + +1905 + +![Sequence diagram for Figure 20.2/4 showing the interaction between SGSN and HLR. The sequence consists of four steps: 1) SGSN to HLR (MAP_UPDATE_GPRS_LOCATION_req/ind), 2) HLR to SGSN (MAP_ACTIVATE_TRACE_MODE_req/ind), 3) SGSN to HLR (MAP_ACTIVATE_TRACE_MODE_rsp/cnf), and 4) HLR to SGSN (MAP_UPDATE_GPRS_LOCATION_rsp/cnf).](5c7d818d8c0e801f5226c9ab6445df08_img.jpg) + +``` + +sequenceDiagram + participant SGSN + participant HLR + Note right of HLR: 1) + SGSN->>HLR: + Note left of SGSN: 2) + HLR->>SGSN: + Note right of HLR: 3) + SGSN->>HLR: + Note left of SGSN: 4) + HLR->>SGSN: + +``` + +Sequence diagram for Figure 20.2/4 showing the interaction between SGSN and HLR. The sequence consists of four steps: 1) SGSN to HLR (MAP\_UPDATE\_GPRS\_LOCATION\_req/ind), 2) HLR to SGSN (MAP\_ACTIVATE\_TRACE\_MODE\_req/ind), 3) SGSN to HLR (MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf), and 4) HLR to SGSN (MAP\_UPDATE\_GPRS\_LOCATION\_rsp/cnf). + +1906 + +1907 + +1908 + +1) MAP\_UPDATE\_GPRS\_LOCATION\_req/ind + +1909 + +2) MAP\_ACTIVATE\_TRACE\_MODE\_req/ind + +1910 + +3) MAP\_ACTIVATE\_TRACE\_MODE\_rsp/cnf + +1911 + +4) MAP\_UPDATE\_GPRS\_LOCATION\_rsp/cnf + +1912 + +1913 + +**Figure 20.2/4: Subscriber tracing activation procedure at GPRS location updating** + +1914 The MAP\_ACTIVATE\_TRACE\_MODE request includes the IMSI, trace reference, trace type and identity of the + +1915 OMC. + +1916 The subscriber tracing deactivation procedure is used when tracing of a subscriber in the VLR or in the SGSN is no + +1917 longer required. The procedures are shown in figures 20.2/5 and 20.2/6. + +1918 +1919 +1920 +1921 +1922 +1923 +1924 +1925 + +![Sequence diagram for Figure 20.2/5: Subscriber tracing deactivation procedure for non-GPRS. Lifelines: VLR, HLR, OMC. Step 1: OMC to HLR. Step 2: HLR to VLR. Step 3: VLR to HLR. Step 4: HLR to OMC.](d6d9874e255955cbc5b5e94235d3e0b1_img.jpg) + +``` + +sequenceDiagram + participant VLR + participant HLR + participant OMC + OMC->>HLR: 1 + HLR->>VLR: 2 + VLR->>HLR: 3 + HLR->>OMC: 4 + +``` + +Sequence diagram for Figure 20.2/5: Subscriber tracing deactivation procedure for non-GPRS. Lifelines: VLR, HLR, OMC. Step 1: OMC to HLR. Step 2: HLR to VLR. Step 3: VLR to HLR. Step 4: HLR to OMC. + +- 1) Subscriber Tracing Deactivation +- 2) MAP\_DEACTIVATE\_TRACE\_MODE\_req/ind +- 3) MAP\_DEACTIVATE\_TRACE\_MODE\_rsp/cnf +- 4) Subscriber Tracing Deactivation Accepted + +**Figure 20.2/5: Subscriber tracing deactivation procedure for non-GPRS** + +![Sequence diagram for Figure 20.2/6: Subscriber tracing deactivation procedure for GPRS. Lifelines: SGSN, HLR, OMC. Step 1: OMC to HLR. Step 2: HLR to SGSN. Step 3: SGSN to HLR. Step 4: HLR to OMC.](a693ed717fe54e3c7f29cfddc82542b7_img.jpg) + +``` + +sequenceDiagram + participant SGSN + participant HLR + participant OMC + OMC->>HLR: 1 + HLR->>SGSN: 2 + SGSN->>HLR: 3 + HLR->>OMC: 4 + +``` + +Sequence diagram for Figure 20.2/6: Subscriber tracing deactivation procedure for GPRS. Lifelines: SGSN, HLR, OMC. Step 1: OMC to HLR. Step 2: HLR to SGSN. Step 3: SGSN to HLR. Step 4: HLR to OMC. + +1926 +1927 +1928 +1929 +1930 +1931 +1932 +1933 + +- 1) Subscriber Tracing Deactivation +- 2) MAP\_DEACTIVATE\_TRACE\_MODE\_req/ind +- 3) MAP\_DEACTIVATE\_TRACE\_MODE\_rsp/cnf +- 4) Subscriber Tracing Deactivation Accepted + +**Figure 20.2/6: Subscriber tracing deactivation procedure for GPRS** + +1934 The subscriber tracing procedures are used when the VLR detects any subscriber related activity for which the trace +1935 mode is activated, e.g. the VLR receives a MAP\_PROCESS\_ACCESS\_REQUEST indication. The procedure is shown +1936 in figure 20.2/7. + +![Sequence diagram for Figure 20.2/7: Subscriber tracing procedure in the serving MSC. Lifelines: MSC, VLR, OMC. Step 1: MSC to VLR. Step 2: VLR to MSC. Step 3: VLR to OMC.](d49c368a5d9f037f252cadd6e1f6ea07_img.jpg) + +``` + +sequenceDiagram + participant MSC + participant VLR + participant OMC + MSC->>VLR: 1 + VLR->>MSC: 2 + VLR->>OMC: 3 + +``` + +Sequence diagram for Figure 20.2/7: Subscriber tracing procedure in the serving MSC. Lifelines: MSC, VLR, OMC. Step 1: MSC to VLR. Step 2: VLR to MSC. Step 3: VLR to OMC. + +1937 +1938 +1939 +1940 +1941 +1942 +1943 + +- 1) MAP\_PROCESS\_ACCESS\_REQUEST\_req/ind +- 2) MAP\_TRACE\_SUBSCRIBER\_ACTIVITY\_req/ind +- 3) Subscriber tracing information + +**Figure 20.2/7: Subscriber tracing procedure in the serving MSC** + +## 1944 20.2.1 Subscriber tracing activation procedure + +### 1945 20.2.1.1 Procedures in the HLR + +1946 A subscriber tracing activation request from the OMC starts the appropriate process in the HLR: + +1947 ATM\_With\_VLR\_HLR if tracing is required in the MSC/VLR, ATM\_With\_SGSN\_HLR if tracing is required in the +1948 SGSN. + +1949 The process in the HLR to activate tracing in the VLR is shown in figure 20.2/8. The MAP process invokes macros not +1950 defined in this clause; the definitions of these macros can be found as follows: + +1951     Receive\_Open\_Cnf     see clause 25.1.2; + +1952     Check\_Confirmation    see clause 25.2.2. + +1953 Sheet 1: If the Repeat attempt counter has reached its limit, the test "Repeat Attempt" takes the "No" exit; otherwise the +1954 test takes the "Yes" exit. The number of repeat attempts and the interval between successive repeat attempts are +1955 operator options. + +1956 The process in the HLR to activate tracing in the SGSN is shown in figure 20.2/9. The MAP process invokes macros +1957 not defined in this clause; the definitions of these macros can be found as follows: + +1958     Receive\_Open\_Cnf     see clause 25.1.2; + +1959     Check\_Confirmation    see clause 25.2.2. + +1960 Sheet 1: If the Repeat attempt counter has reached its limit, the test "Repeat Attempt" takes the "No" exit; otherwise the +1961 test takes the "Yes" exit. The number of repeat attempts and the interval between successive repeat attempts are +1962 operator options. + +### 1963 20.2.1.2 Procedure in the VLR + +1964 The process in the VLR to activate tracing in a stand-alone dialogue is shown in figure 20.2/10. The MAP process +1965 invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1966     Check\_Indication      see clause 25.2.1. + +### 1967 20.2.1.3 Procedure in the SGSN + +1968 The process in the SGSN to activate tracing in a stand-alone dialogue is shown in figure 20.2/11. The MAP process +1969 invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +1970     Check\_Indication      see clause 25.2.1. + +## 1971 20.2.2 Subscriber tracing deactivation procedure + +### 1972 20.2.2.1 Procedures in the HLR + +1973 A subscriber tracing deactivation request from the OMC starts the appropriate process in the HLR: + +1974 DTM\_HLR\_With\_VLR if tracing is no longer required in the MSC/VLR, DTM\_HLR\_With\_SGSN if tracing is no +1975 longer required in the SGSN. + +1976 The process in the HLR to deactivate tracing in the VLR is shown in figure 20.2/12. The MAP process invokes macros +1977 not defined in this clause; the definitions of these macros can be found as follows: + +1978     Receive\_Open\_Cnf     see clause 25.1.2; + +1979     Check\_Confirmation    see clause 25.2.2. + +1980 Sheet 1: If the Repeat attempt counter has reached its limit, the test "Repeat Attempt" takes the "No" exit; otherwise the +1981 test takes the "Yes" exit. The number of repeat attempts and the interval between successive repeat attempts are +1982 operator options. + +1983 The process in the HLR to deactivate tracing in the SGSN is shown in figure 20.2/13. The MAP process invokes macros +1984 not defined in this clause; the definitions of these macros can be found as follows: + +1985     Receive\_Open\_Cnf     see clause 25.1.2; + +1986     Check\_Confirmation     see clause 25.2.2. + +1987 Sheet 1: If the Repeat attempt counter has reached its limit, the test "Repeat Attempt" takes the "No" exit; otherwise the +1988 test takes the "Yes" exit. The number of repeat attempts and the interval between successive repeat attempts are +1989 operator options. + +#### 1990 20.2.2.2     Procedure in the VLR + +1991 The process in the VLR to deactivate tracing is shown in figure 20.2/14. The MAP process invokes a macro not defined +1992 in this clause; the definition of this macro can be found as follows: + +1993     Check\_Indication     see clause 25.2.1. + +#### 1994 20.2.2.3     Procedure in the SGSN + +1995 The process in the SGSN to deactivate tracing is shown in figure 20.2/15. The MAP process invokes a macro not +1996 defined in this clause; the definition of this macro can be found as follows: + +1997     Check\_Indication     see clause 25.2.1. + +![Flowchart for process ATM_With_VLR_HLR. It starts with a Null state, followed by an OM_Subscriber_Tracing_Activation_ind. A decision 'Subscriber known?' leads to 'Set User Error: Unknown Subscriber' if No, or 'Subscriber tracing active in HLR?' if Yes. The 'Yes' path leads to 'Subscriber tracing active in HLR:=True' and then 'Subscriber deregistered?'. If 'Yes' to deregistered, it leads to 'Set User Error: Tracing already active'. If 'No', it leads to 'Subscriber in home PLMN area?'. If 'Yes', it leads to 'Repeat attempt counter:=0' and then a MAP request block. If 'No', it leads to 'Subscriber tracing active in VLR:=False'. The 'Subscriber known?' No path also leads to 'Subscriber tracing active in VLR:=False'. Both 'Subscriber tracing active in VLR:=False' states lead to 'OM_Subscriber_Tracing_Activation_rsp' and then Null. The MAP request block includes MAP_OPEN_req, MAP_ACTIVATE_TRACE_MODE_req, and MAP_DELIMITER_req, followed by 'Receive_Open_Cnf'. This leads to 'Error' (to connector 1), 'OK' (to 'Wait_For_ATM_Result'), or 'Vr' (to 'Perform MAP Vr dialogue' and then Null). A 'Repeat attempt?' decision at the top left leads to 'Subscriber tracing active in VLR:=False' if No, or 'Repeat attempt counter:= Repeat attempt counter+1' if Yes. The Yes path leads to 'Start repeat attempt timer', 'Wait_For_Timer_Expiry', and 'Repeat attempt timer expired' (triggered by an Internal event), which then leads to the MAP request block.](240935a46874e902465be02ff045e6ef_img.jpg) + +**process ATM\_With\_VLR\_HLR** **ATM\_VLR\_HLR1(2)** + +Process in the HLR to activate trace mode in the VLR using a stand-alone dialogue + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the OMC + +``` + + graph TD + Start([Null]) --> Ind{{OM_Subscriber_Tracing_Activation_ind}} + Ind --> Known{Subscriber known?} + Known -- No --> ErrorUnknown[Set User Error: Unknown Subscriber] + Known -- Yes --> TracingActiveHLR{Subscriber tracing active in HLR?} + TracingActiveHLR -- True --> ErrorActive[Set User Error: Tracing already active] + TracingActiveHLR -- False --> TracingActiveHLRTrue[Subscriber tracing active in HLR:=True] + TracingActiveHLRTrue --> Deregistered{Subscriber deregistered?} + Deregistered -- Yes --> ErrorActive + Deregistered -- No --> HomePLMN{Subscriber in home PLMN area?} + HomePLMN -- No --> TracingActiveVLRFalse1[Subscriber tracing active in VLR:=False] + HomePLMN -- Yes --> CounterZero[Repeat attempt counter:=0] + CounterZero --> MAP_Req[MAP_OPEN_req +MAP_ACTIVATE_TRACE_MODE_req +MAP_DELIMITER_req] + MAP_Req --> OpenCnf[Receive_Open_Cnf] + OpenCnf -- Error --> Connector1((1)) + OpenCnf -- OK --> WaitResult[Wait_For_ATM_Result] + OpenCnf -- Vr --> MAPVr[Perform MAP Vr dialogue] + MAPVr --> Null1([Null]) + ErrorUnknown --> OM_Rsp1{{OM_Subscriber_Tracing_Activation_rsp}} + OM_Rsp1 --> Null2([Null]) + ErrorActive --> OM_Rsp2{{OM_Subscriber_Tracing_Activation_rsp}} + OM_Rsp2 --> Null3([Null]) + TracingActiveVLRFalse1 --> OM_Rsp3{{OM_Subscriber_Tracing_Activation_rsp}} + OM_Rsp3 --> Null4([Null]) + + Connector2((1)) --> RepeatAttempt{Repeat attempt?} + RepeatAttempt -- No --> TracingActiveVLRFalse2[Subscriber tracing active in VLR:=False] + RepeatAttempt -- Yes --> CounterInc[Repeat attempt counter:= Repeat attempt counter+1] + CounterInc --> StartTimer[Start repeat attempt timer] + StartTimer --> WaitTimer[Wait_For_Timer_Expiry] + WaitTimer -- Internal --> TimerExpired[Repeat attempt timer expired] + TimerExpired --> CounterZero + +``` + +Flowchart for process ATM\_With\_VLR\_HLR. It starts with a Null state, followed by an OM\_Subscriber\_Tracing\_Activation\_ind. A decision 'Subscriber known?' leads to 'Set User Error: Unknown Subscriber' if No, or 'Subscriber tracing active in HLR?' if Yes. The 'Yes' path leads to 'Subscriber tracing active in HLR:=True' and then 'Subscriber deregistered?'. If 'Yes' to deregistered, it leads to 'Set User Error: Tracing already active'. If 'No', it leads to 'Subscriber in home PLMN area?'. If 'Yes', it leads to 'Repeat attempt counter:=0' and then a MAP request block. If 'No', it leads to 'Subscriber tracing active in VLR:=False'. The 'Subscriber known?' No path also leads to 'Subscriber tracing active in VLR:=False'. Both 'Subscriber tracing active in VLR:=False' states lead to 'OM\_Subscriber\_Tracing\_Activation\_rsp' and then Null. The MAP request block includes MAP\_OPEN\_req, MAP\_ACTIVATE\_TRACE\_MODE\_req, and MAP\_DELIMITER\_req, followed by 'Receive\_Open\_Cnf'. This leads to 'Error' (to connector 1), 'OK' (to 'Wait\_For\_ATM\_Result'), or 'Vr' (to 'Perform MAP Vr dialogue' and then Null). A 'Repeat attempt?' decision at the top left leads to 'Subscriber tracing active in VLR:=False' if No, or 'Repeat attempt counter:= Repeat attempt counter+1' if Yes. The Yes path leads to 'Start repeat attempt timer', 'Wait\_For\_Timer\_Expiry', and 'Repeat attempt timer expired' (triggered by an Internal event), which then leads to the MAP request block. + +1998 + +1999 + +Figure 20.2/8 (sheet 1 of 2): Process ATM\_With\_VLR\_HLR + +![State transition diagram for process ATM_With_VLR_HLR. The diagram shows a state machine with states represented by rounded rectangles and transitions represented by arrows. The initial state is 'Wait_For_ATM_Result'. Transitions include 'MAP_ACTIVATE_TRACE_MODE_cnf', 'MAP_NOTICE_ind', and 'MAP_CLOSE_req'. A 'Check_Confirmation' state leads to 'Subscriber tracing active in VLR:=True' and then to 'OM_Subscriber Tracing_Activation_rsp', which leads to the 'Null' state. Error transitions lead to a circle labeled '1'.](8141e6759be9baa334fc7833145d81ab_img.jpg) + +**process ATM\_With\_VLR\_HLR** **ATM\_VLR\_HLR2(2)** + +Process in the HLR to activate trace mode in the VLR using a stand-alone dialogue + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the OMC + +``` + +stateDiagram-v2 + [*] --> Wait_For_ATM_Result + state "Wait_For_ATM_Result" as Wait_For_ATM_Result + state "MAP_ACTIVATE_TRACE_MODE_cnf" as MAP_ACTIVATE_TRACE_MODE_cnf + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "Check_Confirmation" as Check_Confirmation + state "Subscriber tracing active in VLR:=True" as Subscriber_tracing_active_in_VLR_True + state "OM_Subscriber Tracing_Activation_rsp" as OM_Subscriber_Tracing_Activation_rsp + state "Null" as Null + state "1" as 1 + + Wait_For_ATM_Result --> MAP_ACTIVATE_TRACE_MODE_cnf + Wait_For_ATM_Result --> MAP_NOTICE_ind + Wait_For_ATM_Result --> MAP_CLOSE_req + + MAP_ACTIVATE_TRACE_MODE_cnf --> Check_Confirmation + Check_Confirmation --> Subscriber_tracing_active_in_VLR_True : OK + Check_Confirmation --> 1 : User Error, Provider Error, Data Error + + Subscriber_tracing_active_in_VLR_True --> OM_Subscriber_Tracing_Activation_rsp + OM_Subscriber_Tracing_Activation_rsp --> Null + +``` + +State transition diagram for process ATM\_With\_VLR\_HLR. The diagram shows a state machine with states represented by rounded rectangles and transitions represented by arrows. The initial state is 'Wait\_For\_ATM\_Result'. Transitions include 'MAP\_ACTIVATE\_TRACE\_MODE\_cnf', 'MAP\_NOTICE\_ind', and 'MAP\_CLOSE\_req'. A 'Check\_Confirmation' state leads to 'Subscriber tracing active in VLR:=True' and then to 'OM\_Subscriber Tracing\_Activation\_rsp', which leads to the 'Null' state. Error transitions lead to a circle labeled '1'. + +2000 + +2001 + +**Figure 20.2/8 (sheet 2 of 2): Process ATM\_With\_VLR\_HLR** + +![Flowchart for process ATM_With_SGSN_HLR. It starts with a 'Null' entry point, followed by an 'OM_GPRS_Subscriber_Activation_ind' input. A decision 'GPRS subscriber known?' leads to either 'Set User Error: Unknown Subscriber' (No) or 'Subscriber tracing active in HLR?' (Yes). The 'Yes' path leads to 'Subscriber tracing active in HLR=True', which then checks 'Subscriber deregistered?'. If 'Yes', it leads to 'Set User Error: Tracing already active'. If 'No', it checks 'Subscriber in home PLMN area?'. If 'Yes', it leads to 'Repeat attempt counter:=0'. If 'No', it leads to 'Subscriber tracing active in SGSN:=False'. Both 'Repeat attempt counter:=0' and 'Subscriber tracing active in SGSN:=False' lead to a MAP request block. The 'Repeat attempt counter:=0' path also includes 'Repeat attempt?' (Yes/No), 'Subscriber tracing active in SGSN:=False', 'Set: Subscriber Tracing Activation Failure', 'OM_GPRS_Subscriber_Activation_rsp', and 'Null'. The 'Yes' path of 'Repeat attempt?' leads to 'Repeat attempt counter:= Repeat attempt counter+1', 'Start repeat attempt timer', 'Wait_For_Timer_Expiry', and 'Repeat attempt timer expired'. An 'Internal' signal also leads to 'Repeat attempt timer expired'. All paths converge to a MAP request block containing 'MAP_OPEN_req', 'MAP_ACTIVATE_TRACE_MODE_req', and 'MAP_DELIMITER_req'. This is followed by 'Receive_Open_Cnf' with 'Error', 'OK', and 'Vr' outcomes. 'Error' leads to connector '1'. 'OK' leads to 'Wait_For_ATM_Result'. 'Vr' leads to 'Perform MAP Vr dialogue' and then 'Null'. A final 'OM_GPRS_Subscriber_Activation_rsp' leads to 'Null'.](aa07c1556282a134134e8e1f5902d8f6_img.jpg) + +**process ATM\_With\_SGSN\_HLR** **ATM\_SGSN\_HLR1(2)** + +Process in the HLR to activate trace mode in the SGSN using a stand-alone dialogue + +Signals to/from the left are to/from the SGSN; signals to/from the right are to/from the OMC + +``` + + graph TD + Start([Null]) --> Input{OM_GPRS_Subscriber_Activation_ind} + Input --> Decision1{GPRS subscriber known?} + Decision1 -- No --> Error1[Set User Error: Unknown Subscriber] + Decision1 -- Yes --> Decision2{Subscriber tracing active in HLR?} + Decision2 -- True --> Error2[Set User Error: Tracing already active] + Decision2 -- False --> State1[Subscriber tracing active in HLR=True] + State1 --> Decision3{Subscriber deregistered?} + Decision3 -- Yes --> Error2 + Decision3 -- No --> Decision4{Subscriber in home PLMN area?} + Decision4 -- No --> State2[Subscriber tracing active in SGSN:=False] + Decision4 -- Yes --> Counter0[Repeat attempt counter:=0] + Counter0 --> MAP_Req[MAP_OPEN_req +MAP_ACTIVATE_TRACE_MODE_req +MAP_DELIMITER_req] + State2 --> MAP_Req + Error1 --> MAP_Req + Error2 --> MAP_Req + MAP_Req --> Receive[Receive_Open_Cnf] + Receive -- Error --> End1((1)) + Receive -- OK --> End2([Wait_For_ATM_Result]) + Receive -- Vr --> Dialogue[Perform MAP Vr dialogue] + Dialogue --> End3([Null]) + State2 --> Rsp{OM_GPRS_Subscriber_Activation_rsp} + Rsp --> End4([Null]) + + Counter0 --> Decision5{Repeat attempt?} + Decision5 -- No --> State2 + Decision5 -- Yes --> CounterInc[Repeat attempt counter:= Repeat attempt counter+1] + CounterInc --> StartTimer[Start repeat attempt timer] + StartTimer --> WaitTimer[Wait_For_Timer_Expiry] + WaitTimer --> TimerExpired[Repeat attempt timer expired] + Internal[Internal] --> TimerExpired + TimerExpired --> MAP_Req + +``` + +Flowchart for process ATM\_With\_SGSN\_HLR. It starts with a 'Null' entry point, followed by an 'OM\_GPRS\_Subscriber\_Activation\_ind' input. A decision 'GPRS subscriber known?' leads to either 'Set User Error: Unknown Subscriber' (No) or 'Subscriber tracing active in HLR?' (Yes). The 'Yes' path leads to 'Subscriber tracing active in HLR=True', which then checks 'Subscriber deregistered?'. If 'Yes', it leads to 'Set User Error: Tracing already active'. If 'No', it checks 'Subscriber in home PLMN area?'. If 'Yes', it leads to 'Repeat attempt counter:=0'. If 'No', it leads to 'Subscriber tracing active in SGSN:=False'. Both 'Repeat attempt counter:=0' and 'Subscriber tracing active in SGSN:=False' lead to a MAP request block. The 'Repeat attempt counter:=0' path also includes 'Repeat attempt?' (Yes/No), 'Subscriber tracing active in SGSN:=False', 'Set: Subscriber Tracing Activation Failure', 'OM\_GPRS\_Subscriber\_Activation\_rsp', and 'Null'. The 'Yes' path of 'Repeat attempt?' leads to 'Repeat attempt counter:= Repeat attempt counter+1', 'Start repeat attempt timer', 'Wait\_For\_Timer\_Expiry', and 'Repeat attempt timer expired'. An 'Internal' signal also leads to 'Repeat attempt timer expired'. All paths converge to a MAP request block containing 'MAP\_OPEN\_req', 'MAP\_ACTIVATE\_TRACE\_MODE\_req', and 'MAP\_DELIMITER\_req'. This is followed by 'Receive\_Open\_Cnf' with 'Error', 'OK', and 'Vr' outcomes. 'Error' leads to connector '1'. 'OK' leads to 'Wait\_For\_ATM\_Result'. 'Vr' leads to 'Perform MAP Vr dialogue' and then 'Null'. A final 'OM\_GPRS\_Subscriber\_Activation\_rsp' leads to 'Null'. + +2002 + +2003 + +Figure 20.2/9 (sheet 1 of 2): Process ATM\_with\_SGSN\_HLR + +![State transition diagram for process ATM_With_SGSN_HLR. It starts with a 'Wait_For_ATM_Result' state. Transitions include 'MAP_ACTIVATE_TRACE_MODE_cnf' leading to 'Check_Confirmation', 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req', and a self-loop on 'Wait_For_ATM_Result' labeled with 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind'. 'Check_Confirmation' has an 'OK' transition to 'Subscriber tracing active in SGSN=True', which leads to 'OM_GPRS_Subscriber_Tracing_Activation_rsp' and then to a 'Null' state. 'MAP_CLOSE_req' has a transition to a circle labeled '1' with labels 'User Error, Provider Error, Data Error'.](df079c3046a59bebedea2cc7a9ce5f98_img.jpg) + +**process ATM\_With\_SGSN\_HLR** **ATM\_SGSN\_HLR2(2)** + +Process in the HLR to activate trace mode in the SGSN using a stand-alone dialogue + +Wait\_For\_ATM\_Result + +Signals to/from the left are to/from the SGSN; signals to/from the right are to/from the OMC + +``` + +stateDiagram-v2 + [*] --> Wait_For_ATM_Result + state "Wait_For_ATM_Result" as Wait_For_ATM_Result + state "Check_Confirmation" as Check_Confirmation + state "Subscriber tracing active in SGSN=True" as Subscriber_tracing_active_in_SGSN_True + state "OM_GPRS_Subscriber_Tracing_Activation_rsp" as OM_GPRS_Subscriber_Tracing_Activation_rsp + state "Null" as Null + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "1" as 1 + + Wait_For_ATM_Result --> Check_Confirmation : MAP_ACTIVATE_TRACE_MODE_cnf + Check_Confirmation --> Subscriber_tracing_active_in_SGSN_True : OK + Subscriber_tracing_active_in_SGSN_True --> OM_GPRS_Subscriber_Tracing_Activation_rsp + OM_GPRS_Subscriber_Tracing_Activation_rsp --> Null + + Wait_For_ATM_Result --> MAP_CLOSE_req : MAP_NOTICE_ind + MAP_CLOSE_req --> 1 : User Error, Provider Error, Data Error + + Wait_For_ATM_Result --> Wait_For_ATM_Result : MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + +``` + +State transition diagram for process ATM\_With\_SGSN\_HLR. It starts with a 'Wait\_For\_ATM\_Result' state. Transitions include 'MAP\_ACTIVATE\_TRACE\_MODE\_cnf' leading to 'Check\_Confirmation', 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req', and a self-loop on 'Wait\_For\_ATM\_Result' labeled with 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind'. 'Check\_Confirmation' has an 'OK' transition to 'Subscriber tracing active in SGSN=True', which leads to 'OM\_GPRS\_Subscriber\_Tracing\_Activation\_rsp' and then to a 'Null' state. 'MAP\_CLOSE\_req' has a transition to a circle labeled '1' with labels 'User Error, Provider Error, Data Error'. + +2004 + +2005 + +**Figure 20.2/9 (sheet 2 of 2): Process ATM\_with\_SGSN\_HLR** + +![Flowchart for process ATM_Stand_Alone_VLR. It starts with an initial node, followed by a 'Null' node. An input signal 'MAP_ACTIVATE_TRACE_MODE_ind' enters at a merge node. The flow then goes to 'Check_Indication'. From there, an 'OK' path leads to a decision 'Subscriber known?'. If 'No', it goes to 'Set User Error: Unidentified subscriber'. If 'Yes', it goes to 'Tracing supported?'. If 'No', it goes to 'Set User Error: Facility not supported'. If 'Yes', it goes to 'Tracing buffer full?'. If 'No', it goes to 'Subscriber tracing active:= True'. If 'Yes', it goes to 'Set User Error: Tracing buffer full'. All four error/active nodes lead to a merge node. From this merge node, an 'Error' path leads out to the left, and a response path leads to a split node with output signals 'MAP_ACTIVATE_TRACE_MODE_rsp' and 'MAP_CLOSE_req'. The process ends at a final node marked with an 'X'.](195bfcf817b1bea7a7c4ad3ba8c02ccc_img.jpg) + +process ATM\_Stand\_Alone\_VLR + +ATM\_SA\_VLR1(1) + +Process in the VLR to activate trace mode in a stand-alone-dialogue + +Signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> Null[Null] + Null --> Merge{ } + MAP_ACTIVATE_TRACE_MODE_ind[MAP_ACTIVATE_TRACE_MODE_ind] --> Merge + Merge --> Check[Check_Indication] + Check -- OK --> SubKnown{Subscriber known?} + SubKnown -- No --> ErrUnid[Set User Error: Unidentified subscriber] + SubKnown -- Yes --> TracingSupp{Tracing supported?} + TracingSupp -- No --> ErrFac[Set User Error: Facility not supported] + TracingSupp -- Yes --> BufferFull{Tracing buffer full?} + BufferFull -- No --> SubActive[Subscriber tracing active:= True] + BufferFull -- Yes --> ErrFull[Set User Error: Tracing buffer full] + ErrUnid --> Merge2{ } + ErrFac --> Merge2 + SubActive --> Merge2 + ErrFull --> Merge2 + Merge2 -- Error --> OutLeft[ ] + Merge2 --> Split{ } + Split --> MAP_ACTIVATE_TRACE_MODE_rsp[MAP_ACTIVATE_TRACE_MODE_rsp] + Split --> MAP_CLOSE_req[MAP_CLOSE_req] + Split --> End([X]) + +``` + +Flowchart for process ATM\_Stand\_Alone\_VLR. It starts with an initial node, followed by a 'Null' node. An input signal 'MAP\_ACTIVATE\_TRACE\_MODE\_ind' enters at a merge node. The flow then goes to 'Check\_Indication'. From there, an 'OK' path leads to a decision 'Subscriber known?'. If 'No', it goes to 'Set User Error: Unidentified subscriber'. If 'Yes', it goes to 'Tracing supported?'. If 'No', it goes to 'Set User Error: Facility not supported'. If 'Yes', it goes to 'Tracing buffer full?'. If 'No', it goes to 'Subscriber tracing active:= True'. If 'Yes', it goes to 'Set User Error: Tracing buffer full'. All four error/active nodes lead to a merge node. From this merge node, an 'Error' path leads out to the left, and a response path leads to a split node with output signals 'MAP\_ACTIVATE\_TRACE\_MODE\_rsp' and 'MAP\_CLOSE\_req'. The process ends at a final node marked with an 'X'. + +2006 + +2007 + +Figure 20.2/10: Process ATM\_Standalone\_VLR + +![Flowchart for process ATM_Stand_Alone_SGSN. It starts with 'Null', then receives 'MAP_ACTIVATE_TRACE_MODE_ind'. It checks the indication, then if the subscriber is known and tracing is supported, it checks if the tracing buffer is full. Depending on these checks, it either sets tracing active, sets an error (facility not supported, buffer full, or unidentified subscriber), or returns a response with 'MAP_ACTIVATE_TRACE_MODE_rsp' and 'MAP_CLOSE_req'.](6c2f572f3cbbbae048521f83d7add4da_img.jpg) + +process ATM\_Stand\_Alone\_SGSN ATM\_SA\_SGSN1(1) + +Process in the SGSN to activate trace mode in a stand-alone-dialogue + +Signals to/from the right are to/from the HLR + +``` + + graph TD + Start([Null]) --> In{ } + In -- "MAP_ACTIVATE_TRACE_MODE_ind" --> In + In --> Check[Check Indication] + Check --> OK{OK} + OK -- No --> Unknown[Set User Error: Unidentified subscriber] + OK -- Yes --> Supported{Tracing supported?} + Supported -- No --> NotSupported[Set User Error: Facility not supported] + Supported -- Yes --> Full{Tracing buffer full?} + Full -- Yes --> BufferFull[Set User Error: Tracing buffer full] + Full -- No --> Active[Subscriber tracing active:= True] + Unknown --> Out{ } + NotSupported --> Out + BufferFull --> Out + Active --> Out + Out -- "MAP_ACTIVATE_TRACE_MODE_rsp +MAP_CLOSE_req" --> End(( )) + +``` + +Flowchart for process ATM\_Stand\_Alone\_SGSN. It starts with 'Null', then receives 'MAP\_ACTIVATE\_TRACE\_MODE\_ind'. It checks the indication, then if the subscriber is known and tracing is supported, it checks if the tracing buffer is full. Depending on these checks, it either sets tracing active, sets an error (facility not supported, buffer full, or unidentified subscriber), or returns a response with 'MAP\_ACTIVATE\_TRACE\_MODE\_rsp' and 'MAP\_CLOSE\_req'. + +2008 + +2009 + +Figure 20.2/11: Process ATM\_Standalone\_SGSN + +![Flowchart for process DTM_With_VLR_HLR. It starts with an entry point leading to a 'Null' state. From 'Null', it goes to 'OM_Subscriber_Tracing_Deactivation_ind'. A decision 'Subscriber known?' follows. If 'No', it goes to 'Set User Error: Unknown Subscriber' and then to 'Null'. If 'Yes', it checks 'Subscriber tracing active in HLR'. If 'False', it goes to 'Set User Error: Unknown Subscriber'. If 'True', it checks 'Subscriber tracing active in VLR'. If 'False', it goes to 'Set User Error: Unknown Subscriber'. If 'True', it sets 'Repeat attempt counter:=0' and then sends MAP messages (MAP_OPEN_req, MAP_DEACTIVATE_TRACE_MODE_req, MAP_DELIMITER_req) via an internal process to 'Receive_Open_Cnf'. From 'Receive_Open_Cnf', three outcomes are possible: 'Error' leads to exit point '1'; 'OK' leads to 'Wait_For_DTM_Result'; 'Vr' leads to 'Perform MAP Vr dialogue' and then to 'Null'. Another path from 'OM_Subscriber_Tracing_Deactivation_ind' leads to a decision 'Repeat attempt?'. If 'Yes', it increments 'Repeat attempt counter:= Repeat attempt counter+1', starts a timer, and waits for 'Timer_Expired'. If 'Internal' signal occurs, it loops back to 'Repeat attempt?'. If 'No', it checks 'Subscriber tracing active in VLR:=True', sets 'Subscriber Tracing Deactivation Failure', sends 'OM_Subscriber_Tracing_Deactivation_rsp', and ends at 'Null'.](5f46be30e6ab02f9ce75b6ed98bb0d50_img.jpg) + +**process DTM\_With\_VLR\_HLR** **DTM\_VLR\_HLR1(2)** + +Process in the HLR to deactivate trace mode in the VLR using a stand-alone dialogue + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the OMC + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> OM1{{OM_Subscriber_Tracing_Deactivation_ind}} + + OM1 --> SubKnown{Subscriber known?} + SubKnown -- No --> UserError1[Set User Error: Unknown Subscriber] + UserError1 --> Null2([Null]) + + SubKnown -- Yes --> SubActiveHLR{Subscriber tracing active in HLR} + SubActiveHLR -- False --> UserError1 + SubActiveHLR -- True --> SubActiveVLR{Subscriber tracing active in VLR} + + SubActiveVLR -- False --> UserError1 + SubActiveVLR -- True --> Counter0[Repeat attempt counter:=0] + + Counter0 --> Internal1[Internal] + Internal1 --> MAPReq["MAP_OPEN_req +MAP_DEACTIVATE_TRACE_MODE_req +MAP_DELIMITER_req"] + + MAPReq --> RecvCnf[Receive_Open_Cnf] + + RecvCnf -- Error --> Exit1((1)) + RecvCnf -- OK --> WaitResult[Wait_For_DTM_Result] + RecvCnf -- Vr --> MAPVr[Perform MAP Vr dialogue] + + MAPVr --> Null3([Null]) + + OM1 --> RepeatAttempt{Repeat attempt?} + + RepeatAttempt -- Yes --> CounterInc[Repeat attempt counter:= +Repeat attempt counter+1] + + CounterInc --> StartTimer[Start repeat attempt timer] + + StartTimer --> WaitTimer[Wait_For_Timer_Expired] + + WaitTimer --> TimerExpired[Repeat attempt timer expired] + + TimerExpired --> RepeatAttempt + + RepeatAttempt -- No --> SubActiveVLR2[Subscriber tracing active in VLR:=True] + + SubActiveVLR2 --> SetFailure[Set: Subscriber Tracing Deactivation Failure] + + SetFailure --> OM2{{OM_Subscriber_Tracing_Deactivation_rsp}} + + OM2 --> Null4([Null]) + +``` + +Flowchart for process DTM\_With\_VLR\_HLR. It starts with an entry point leading to a 'Null' state. From 'Null', it goes to 'OM\_Subscriber\_Tracing\_Deactivation\_ind'. A decision 'Subscriber known?' follows. If 'No', it goes to 'Set User Error: Unknown Subscriber' and then to 'Null'. If 'Yes', it checks 'Subscriber tracing active in HLR'. If 'False', it goes to 'Set User Error: Unknown Subscriber'. If 'True', it checks 'Subscriber tracing active in VLR'. If 'False', it goes to 'Set User Error: Unknown Subscriber'. If 'True', it sets 'Repeat attempt counter:=0' and then sends MAP messages (MAP\_OPEN\_req, MAP\_DEACTIVATE\_TRACE\_MODE\_req, MAP\_DELIMITER\_req) via an internal process to 'Receive\_Open\_Cnf'. From 'Receive\_Open\_Cnf', three outcomes are possible: 'Error' leads to exit point '1'; 'OK' leads to 'Wait\_For\_DTM\_Result'; 'Vr' leads to 'Perform MAP Vr dialogue' and then to 'Null'. Another path from 'OM\_Subscriber\_Tracing\_Deactivation\_ind' leads to a decision 'Repeat attempt?'. If 'Yes', it increments 'Repeat attempt counter:= Repeat attempt counter+1', starts a timer, and waits for 'Timer\_Expired'. If 'Internal' signal occurs, it loops back to 'Repeat attempt?'. If 'No', it checks 'Subscriber tracing active in VLR:=True', sets 'Subscriber Tracing Deactivation Failure', sends 'OM\_Subscriber\_Tracing\_Deactivation\_rsp', and ends at 'Null'. + +2010 + +2011 + +Figure 20.2/12 (sheet 1 of 2): Process DTM\_with\_VLR\_HLR + +![State transition diagram for process DTM_With_VLR_HLR. It starts at 'Wait_For_DTM_Result' and branches into three paths: 1) MAP_DEACTIVATE_TRACE_MODE_cnf leads to 'Check_Confirmation' (OK path leads to 'Subscriber tracing active in VLR:=False' -> 'OM_Subscriber Tracing_Deactivation_rsp' -> 'Null'); 2) MAP_NOTICE_ind leads to 'MAP_CLOSE_req' which has an error path ('User Error, Provider Error, Data Error') and a transition to state '1'; 3) An unlabeled path leads to a state with MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind.](c2cc2ebb8004b97b8922758a0ae0a1ed_img.jpg) + +**process DTM\_With\_VLR\_HLR** **DTM\_VLR\_HLR2(2)** + +Process in the HLR to deactivate trace mode in the VLR using a stand-alone dialogue + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the OMC + +``` + +stateDiagram-v2 + [*] --> Wait_For_DTM_Result + state "MAP_DEACTIVATE_TRACE_MODE_cnf" as MAP_DEACTIVATE_TRACE_MODE_cnf + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "Subscriber tracing active in VLR:=False" as Subscriber_tracing_active_in_VLR_False + state "OM_Subscriber Tracing_Deactivation_rsp" as OM_Subscriber_Tracing_Deactivation_rsp + state "Null" as Null + state "1" as 1 + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" as MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind + + Wait_For_DTM_Result --> MAP_DEACTIVATE_TRACE_MODE_cnf + Wait_For_DTM_Result --> MAP_NOTICE_ind + Wait_For_DTM_Result --> MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind + + MAP_DEACTIVATE_TRACE_MODE_cnf --> Check_Confirmation + state "Check_Confirmation" as Check_Confirmation + Check_Confirmation --> Subscriber_tracing_active_in_VLR_False : OK + Check_Confirmation --> MAP_CLOSE_req : User Error, Provider Error, Data Error + + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> 1 : User Error, Provider Error, Data Error + +``` + +State transition diagram for process DTM\_With\_VLR\_HLR. It starts at 'Wait\_For\_DTM\_Result' and branches into three paths: 1) MAP\_DEACTIVATE\_TRACE\_MODE\_cnf leads to 'Check\_Confirmation' (OK path leads to 'Subscriber tracing active in VLR:=False' -> 'OM\_Subscriber Tracing\_Deactivation\_rsp' -> 'Null'); 2) MAP\_NOTICE\_ind leads to 'MAP\_CLOSE\_req' which has an error path ('User Error, Provider Error, Data Error') and a transition to state '1'; 3) An unlabeled path leads to a state with MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind. + +2012 + +2013 + +**Figure 20.2/12 (sheet 2 of 2): Process DTM\_with\_VLR\_HLR** + +![Flowchart for process DTM_With_SGSN_HLR. It starts with a connector '1' leading to a decision 'Repeat attempt?'. If 'No', it checks if tracing is active in SGSN, sets a failure, and sends a response. If 'Yes', it increments a counter and starts a timer. After the timer expires, it checks if tracing is active in HLR. If 'False', it sends a response. If 'True', it resets the counter and sends MAP requests. The MAP requests result in 'Error', 'OK', or 'Vr' responses, leading to connectors '1', 'Wait_For_DTM_Result', or 'Null' respectively. A 'Null' entry point also leads to a 'Subscriber known?' check. If 'No', it sets an unknown subscriber error. If 'Yes', it checks if tracing is active in HLR. If 'False', it sends a response. If 'True', it checks if tracing is active in SGSN. If 'False', it sends a response. If 'True', it resets the counter and sends MAP requests.](50c70e799740b36cdcc2da0c90d0c12a_img.jpg) + +**process DTM\_With\_SGSN\_HLR** **DTM\_SGSN\_HLR1(2)** + +Process in the HLR to deactivate trace mode in the VLR using a stand-alone dialogue + +Signals to/from the left are to/from the OMC; signals to/from the right are to/from the SGSN + +``` + + graph TD + subgraph Left [ ] + direction TB + L1((1)) --> L2{Repeat attempt?} + L2 -- No --> L3[Subscriber tracing active in SGSN:=True] + L3 --> L4[Set: Subscriber Tracing Deactivation Failure] + L4 --> L5[OM_GPRS_Subscriber_Tracing_Deactivation_rsp] + L5 --> L6[Null] + L2 -- Yes --> L7[Repeat attempt counter:= Repeat attempt counter+1] + L7 --> L8[Start repeat attempt timer] + L8 --> L9[Wait_For_Timer_Expiry] + L9 --> L10[Repeat attempt timer expired] + L10 --> L11[ ] + L11 -.-> Internal[Internal] + end + + subgraph Right [ ] + direction TB + R1[Null] --> R2[OM_GPRS_Subscriber_Tracing_Deactivation_ind] + R2 --> R3{Subscriber known?} + R3 -- No --> R4[Set User Error: Unknown Subscriber] + R3 -- Yes --> R5{Subscriber tracing active in HLR} + R5 -- False --> R6[ ] + R5 -- True --> R7[Subscriber tracing active in HLR:=False] + R7 --> R8{Subscriber tracing active in SGSN} + R8 -- False --> R9[ ] + R8 -- True --> R10[Repeat attempt counter:=0] + R10 --> R11[ ] + R11 --> R12[MAP_OPEN_req +MAP_DEACTIVATE_TRACE_MODE_req +MAP_DELIMITER_req] + R12 --> R13[Receive_Open_Cnf] + R13 -- Error --> R14((1)) + R13 -- OK --> R15[Wait_For_DTM_Result] + R13 -- Vr --> R16[Perform MAP Vr dialogue] + R16 --> R17[Null] + R17 --> R18[ ] + R18 --> R19[OM_GPRS_Subscriber_Tracing_Deactivation_rsp] + R19 --> R20[Null] + end + + L11 --> R11 + R4 --> R20 + +``` + +Flowchart for process DTM\_With\_SGSN\_HLR. It starts with a connector '1' leading to a decision 'Repeat attempt?'. If 'No', it checks if tracing is active in SGSN, sets a failure, and sends a response. If 'Yes', it increments a counter and starts a timer. After the timer expires, it checks if tracing is active in HLR. If 'False', it sends a response. If 'True', it resets the counter and sends MAP requests. The MAP requests result in 'Error', 'OK', or 'Vr' responses, leading to connectors '1', 'Wait\_For\_DTM\_Result', or 'Null' respectively. A 'Null' entry point also leads to a 'Subscriber known?' check. If 'No', it sets an unknown subscriber error. If 'Yes', it checks if tracing is active in HLR. If 'False', it sends a response. If 'True', it checks if tracing is active in SGSN. If 'False', it sends a response. If 'True', it resets the counter and sends MAP requests. + +2014 + +2015 + +Figure 20.2/13 (sheet 1 of 2): Process DTM\_with\_SGSN\_HLR + +![Flowchart for process DTM_With_SGSN_HLR. It starts with 'Wait_For_DTM_Result' leading to a split. The left path sends 'MAP_DEACTIVATE_TRACE_MODE_cnf', checks confirmation, and if 'OK', sets 'Subscriber tracing active in SGSN:=False' and sends 'OM_GPRS_Subscriber_Tracing_Deactivation_rsp' to 'Null'. The right path receives 'MAP_NOTICE_ind', sends 'MAP_CLOSE_req', and then joins a common path leading to connector '1'. A 'User Error, Provider Error, Data Error' is also shown on the right path. A third split on the right leads to a box with 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind'.](240d035b4af1a1143c0a31b95362f077_img.jpg) + +**process DTM\_With\_SGSN\_HLR** **DTM\_SGSN\_HLR2(2)** + +Process in the HLR to deactivate trace mode in the VLR using a stand-alone dialogue + +Signals to/from the left are to/from the SGSN; signals to/from the right are to/from the OMC + +``` + +graph TD + Start([Wait_For_DTM_Result]) --> Split1(( )) + Split1 --> LeftPath[MAP_DEACTIVATE_TRACE_MODE_cnf] + Split1 --> RightPath1[MAP_NOTICE_ind] + Split1 --> RightPath2[ ] + LeftPath --> Check[Check Confirmation] + Check -- OK --> Active[Subscriber tracing active in SGSN:=False] + Active --> Rsp[OM_GPRS_Subscriber_Tracing_Deactivation_rsp] + Rsp --> Null([Null]) + RightPath1 --> CloseReq{MAP_CLOSE_req} + CloseReq --> Join1(( )) + RightPath2 --> Error[User Error, Provider Error, Data Error] + Error --> Join1 + RightPath2 --> RightPath3[ ] + RightPath3 --> Indications[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Indications --> Join1 + Join1 --> Connector1((1)) + +``` + +Flowchart for process DTM\_With\_SGSN\_HLR. It starts with 'Wait\_For\_DTM\_Result' leading to a split. The left path sends 'MAP\_DEACTIVATE\_TRACE\_MODE\_cnf', checks confirmation, and if 'OK', sets 'Subscriber tracing active in SGSN:=False' and sends 'OM\_GPRS\_Subscriber\_Tracing\_Deactivation\_rsp' to 'Null'. The right path receives 'MAP\_NOTICE\_ind', sends 'MAP\_CLOSE\_req', and then joins a common path leading to connector '1'. A 'User Error, Provider Error, Data Error' is also shown on the right path. A third split on the right leads to a box with 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind'. + +2016 + +2017 + +**Figure 20.2/13 (sheet 2 of 2): Process DTM\_with\_SGSN\_HLR** + +![Flowchart for process DTM_Stand_Alone_VLR. The process starts with an oval, followed by a 'Null' block. It then enters a loop via a merge symbol (chevron) receiving 'MAP_DEACTIVATE_TRACE_MODE_ind'. A 'Check_Indication' block follows. An 'OK' path leads to a 'Subscriber known?' decision. If 'No', it goes to 'Set User Error: Unidentified subscriber'. If 'Yes', it goes to a 'Tracing supported?' decision. If 'No', it goes to 'Set User Error: Facility not supported'. If 'Yes', it goes to 'Subscriber tracing active:= False'. All three error/processing blocks lead to a merge symbol (cross) before sending 'MAP_DEACTIVATE_TRACE_MODE_rsp' and 'MAP_CLOSE_req' via another merge symbol (chevron), ending at an exit symbol (cross). An 'Error' path from the 'Check_Indication' block also leads to the first merge symbol (cross).](7294734c2ddd2be18cc08977e6ea7d2f_img.jpg) + +process DTM\_Stand\_Alone\_VLR + +DTM\_SA\_VLR1(1) + +Process in the VLR to deactivate trace mode in a stand-alone-dialogue + +Signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> Null[Null] + Null --> Merge1{ } + Merge1 --> Check[Check_Indication] + Check -- OK --> SubKnown{Subscriber known?} + Check -- Error --> Merge2{ } + SubKnown -- No --> Err1[Set User Error: +Unidentified +subscriber] + SubKnown -- Yes --> TracingSupp{Tracing supported?} + TracingSupp -- No --> Err2[Set User Error: +Facility not +supported] + TracingSupp -- Yes --> ActFalse[Subscriber +tracing active:= +False] + Err1 --> Merge2 + Err2 --> Merge2 + ActFalse --> Merge2 + Merge2 --> Merge3{ } + Merge3 --> Send[MAP_DEACTIVATE_TRACE_MODE_rsp +MAP_CLOSE_req] + Send --> Exit[ ] + +``` + +Flowchart for process DTM\_Stand\_Alone\_VLR. The process starts with an oval, followed by a 'Null' block. It then enters a loop via a merge symbol (chevron) receiving 'MAP\_DEACTIVATE\_TRACE\_MODE\_ind'. A 'Check\_Indication' block follows. An 'OK' path leads to a 'Subscriber known?' decision. If 'No', it goes to 'Set User Error: Unidentified subscriber'. If 'Yes', it goes to a 'Tracing supported?' decision. If 'No', it goes to 'Set User Error: Facility not supported'. If 'Yes', it goes to 'Subscriber tracing active:= False'. All three error/processing blocks lead to a merge symbol (cross) before sending 'MAP\_DEACTIVATE\_TRACE\_MODE\_rsp' and 'MAP\_CLOSE\_req' via another merge symbol (chevron), ending at an exit symbol (cross). An 'Error' path from the 'Check\_Indication' block also leads to the first merge symbol (cross). + +2018 + +2019 + +Figure 20.2/14: Process DTM\_Standalone\_VLR + +![Flowchart for process DTM_Stand_Alone_SGSN. The process starts with an oval, followed by a 'Null' block. It then enters a loop via a merge symbol (circle with a line) associated with 'MAP_DEACTIVATE_TRACE_MODE_ind'. A 'Check Indication' block follows. An 'OK' path leads to a 'Subscriber known?' decision. If 'No', it goes to 'Set User Error: Unidentified subscriber'. If 'Yes', it goes to a 'Tracing supported?' decision. If 'No', it goes to 'Set User Error: Facility not supported'. If 'Yes', it goes to 'Subscriber tracing active:= False'. All three error/processing blocks lead to a merge symbol (circle with a line) associated with 'MAP_DEACTIVATE_TRACE_MODE_rsp' and 'MAP_CLOSE_req'. An 'Error' path from the 'Check Indication' block also leads to this merge symbol. The process ends with an exit symbol (crossed lines).](7d4ca396ee7dcc1f8da61ad2ed9c6c07_img.jpg) + +process DTM\_Stand\_Alone\_SGSN + +DTM\_SA\_SGSN1(1) + +Process in the SGSN to deactivate trace mode in a stand-alone-dialogue + +Signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> Null[Null] + Null --> Merge1(( )) + Merge1 --- MAP_DEACTIVATE_TRACE_MODE_ind[MAP_DEACTIVATE_TRACE_MODE_ind] + Merge1 --> CheckInd[Check Indication] + CheckInd -- OK --> SubKnown{Subscriber known?} + CheckInd -- Error --> Merge2(( )) + SubKnown -- No --> Err1[Set User Error: Unidentified subscriber] + SubKnown -- Yes --> TracingSup{Tracing supported?} + TracingSup -- No --> Err2[Set User Error: Facility not supported] + TracingSup -- Yes --> ActFalse[Subscriber tracing active:= False] + Err1 --> Merge2 + Err2 --> Merge2 + ActFalse --> Merge2 + Merge2 --- MAP_DEACTIVATE_TRACE_MODE_rsp[MAP_DEACTIVATE_TRACE_MODE_rsp] + Merge2 --- MAP_CLOSE_req[MAP_CLOSE_req] + Merge2 --> Exit(( )) + +``` + +Flowchart for process DTM\_Stand\_Alone\_SGSN. The process starts with an oval, followed by a 'Null' block. It then enters a loop via a merge symbol (circle with a line) associated with 'MAP\_DEACTIVATE\_TRACE\_MODE\_ind'. A 'Check Indication' block follows. An 'OK' path leads to a 'Subscriber known?' decision. If 'No', it goes to 'Set User Error: Unidentified subscriber'. If 'Yes', it goes to a 'Tracing supported?' decision. If 'No', it goes to 'Set User Error: Facility not supported'. If 'Yes', it goes to 'Subscriber tracing active:= False'. All three error/processing blocks lead to a merge symbol (circle with a line) associated with 'MAP\_DEACTIVATE\_TRACE\_MODE\_rsp' and 'MAP\_CLOSE\_req'. An 'Error' path from the 'Check Indication' block also leads to this merge symbol. The process ends with an exit symbol (crossed lines). + +2020 + +2021 + +Figure 20.2/15: Process DTM\_Standalone\_SGSN + +2022 **20.3 Subscriber data management procedures for HLR** + +2023 Two types of subscriber data management procedures exist: + +- 2024 1) Subscriber Deletion; +- 2025 2) Subscriber Data Modification. + +2026 The subscriber deletion and subscriber data modification procedures are initiated by the OMC (see figures 20.3/1 , +2027 20.3/2, 20.3/3 and 20.3/4). + +![Sequence diagram for non-GPRS subscriber deletion. Lifelines: VLR, HLR, OMC. Step 1: OMC to HLR. Step 2: HLR to VLR. Step 3: VLR to HLR. Step 4: HLR to OMC.](9e31c4113f34a97fa2ff01325f5c88bc_img.jpg) + +``` +sequenceDiagram + participant OMC + participant HLR + participant VLR + Note right of OMC: 1 + OMC->>HLR: + Note right of HLR: 2 + HLR->>VLR: + Note right of VLR: 3 + VLR->>HLR: + Note right of HLR: 4 + HLR->>OMC: +``` + +Sequence diagram for non-GPRS subscriber deletion. Lifelines: VLR, HLR, OMC. Step 1: OMC to HLR. Step 2: HLR to VLR. Step 3: VLR to HLR. Step 4: HLR to OMC. + +2028 + +- 2029 +- 2030 1) Delete Subscriber +- 2031 2) MAP\_CANCEL\_LOCATION\_req/ind +- 2032 3) MAP\_CANCEL\_LOCATION\_rsp/cnf +- 2033 4) Subscriber Deleted +- 2034 +- 2035 + +**Figure 20.3/1: Subscriber deletion procedure for non-GPRS** + +2036 In the subscriber deletion procedure for a non-GPRS subscriber the subscriber data are removed from the VLR and the +2037 HLR. The HLR uses the MAP\_CANCEL\_LOCATION service. + +![Sequence diagram for GPRS subscriber deletion. Lifelines: SGSN, HLR, OMC. Step 1: OMC to HLR. Step 2: HLR to SGSN. Step 3: SGSN to HLR. Step 4: HLR to OMC.](d0671ff4e6ea09355aabd187a2d3ff7b_img.jpg) + +``` +sequenceDiagram + participant OMC + participant HLR + participant SGSN + Note right of OMC: 1 + OMC->>HLR: + Note right of HLR: 2 + HLR->>SGSN: + Note right of SGSN: 3 + SGSN->>HLR: + Note right of HLR: 4 + HLR->>OMC: +``` + +Sequence diagram for GPRS subscriber deletion. Lifelines: SGSN, HLR, OMC. Step 1: OMC to HLR. Step 2: HLR to SGSN. Step 3: SGSN to HLR. Step 4: HLR to OMC. + +2038 + +- 2039 +- 2040 1) Delete GPRS Subscriber +- 2041 2) MAP\_CANCEL\_LOCATION\_req/ind +- 2042 3) MAP\_CANCEL\_LOCATION\_rsp/cnf +- 2043 4) GPRS Subscriber Deleted +- 2044 +- 2045 + +**Figure 20.3/2: Subscriber deletion procedure for GPRS** + +2046 In the subscriber deletion procedure for a GPRS subscriber the subscriber data are removed from the SGSN and the +2047 HLR. The HLR uses the MAP\_CANCEL\_LOCATION service. + +![Sequence diagram for Figure 20.3/3: Subscriber data modification procedure for non-GPRS. Lifelines: VLR, HLR, OMC. 1) OMC to HLR (1), 2) HLR to VLR (2), 3) VLR to HLR (3), 4) HLR to OMC (4).](10b5f8259a1411e6de336da5a0e96bd7_img.jpg) + +``` + +sequenceDiagram + participant OMC + participant HLR + participant VLR + Note right of OMC: 1 + OMC->>HLR: + Note right of HLR: 2 + HLR->>VLR: + Note right of VLR: 3 + VLR->>HLR: + Note right of HLR: 4 + HLR->>OMC: + +``` + +Sequence diagram for Figure 20.3/3: Subscriber data modification procedure for non-GPRS. Lifelines: VLR, HLR, OMC. 1) OMC to HLR (1), 2) HLR to VLR (2), 3) VLR to HLR (3), 4) HLR to OMC (4). + +2048 +2049 +2050 +2051 +2052 +2053 +2054 +2055 +2056 +2057 + +- 1) Modify Subscriber Data +- 2) MAP\_CANCEL\_LOCATION\_req/ind, MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind or +MAP\_DELETE\_SUBSCRIBER\_DATA\_req/ind +- 3) MAP\_CANCEL\_LOCATION\_rsp/cnf, MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf or +MAP\_DELETE\_SUBSCRIBER\_DATA\_rsp/cnf +- 4) Subscriber Data Modified + +**Figure 20.3/3: Subscriber data modification procedure for non-GPRS** + +![Sequence diagram for Figure 20.3/4: Subscriber data modification procedure for GPRS. Lifelines: SGSN, HLR, OMC. 1) OMC to HLR (1), 2) HLR to SGSN (2), 3) SGSN to HLR (3), 4) HLR to OMC (4).](7ed01b362db267d4426e1b664fb44143_img.jpg) + +``` + +sequenceDiagram + participant OMC + participant HLR + participant SGSN + Note right of OMC: 1 + OMC->>HLR: + Note right of HLR: 2 + HLR->>SGSN: + Note right of SGSN: 3 + SGSN->>HLR: + Note right of HLR: 4 + HLR->>OMC: + +``` + +Sequence diagram for Figure 20.3/4: Subscriber data modification procedure for GPRS. Lifelines: SGSN, HLR, OMC. 1) OMC to HLR (1), 2) HLR to SGSN (2), 3) SGSN to HLR (3), 4) HLR to OMC (4). + +2058 +2059 +2060 +2061 +2062 +2063 +2064 +2065 +2066 + +- 1) Modify GPRS Subscriber Data +- 2) MAP\_CANCEL\_LOCATION\_req/ind, MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind or +MAP\_DELETE\_SUBSCRIBER\_DATA\_req/ind +- 3) MAP\_CANCEL\_LOCATION\_rsp/cnf, MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf or +MAP\_DELETE\_SUBSCRIBER\_DATA\_rsp/cnf +- 4) GPRS Subscriber Data Modified + +**Figure 20.3/4: Subscriber data modification procedure for GPRS** + +2067 In the subscriber data modification procedure the subscriber data are modified in the HLR and when necessary also in +2068 the VLR or in the SGSN. The HLR initiates one of the MAP\_INSERT\_SUBSCRIBER\_DATA, +2069 MAP\_DELETE\_SUBSCRIBER\_DATA or MAP\_CANCEL\_LOCATION services depending on the modified data. + +2070 **20.3.1 Subscriber deletion procedure** + +2071 **20.3.1.1 Procedure in the HLR** + +2072 The subscriber deletion process in the HLR is shown in figure 20.3/5. The MAP process invokes processes not defined +2073 in this clause; the definitions of these processes can be found as follows: + +- 2074 Cancel\_GPRS\_Location\_Child\_HLR see clause 19.1.2.2; +- 2075 Cancel\_Location\_Child\_HLR see clause 19.1.2.2. + +2076 **20.3.1.2 Procedure in the VLR** + +2077 The subscriber deletion procedure in the VLR is described in clause 19.1.2.3 of the present document. + +### 2078 20.3.1.3 Procedure in the SGSN + +2079 The subscriber deletion procedure in the SGSN is described in clause 19.1. 2.4 of the present document. + +## 2080 20.3.2 Subscriber data modification procedure + +### 2081 20.3.2.1 Procedure in the HLR + +2082 The OMC can modify the subscriber data in several different ways. The modifications can be categorised in the +2083 following groups: + +- 2084 1) data shall be modified in the HLR; no effect in the VLR; +- 2085 2) data shall be modified in both the HLR and the VLR; +- 2086 3) withdrawal of a basic service or a supplementary service requiring change to VLR data; +- 2087 4) modification affects the roaming permission for the subscriber and the subscriber record shall be removed from +2088 the VLR data base; +- 2089 5) withdrawal of non-GPRS Subscription caused by a change of Network Access Mode; +- 2090 6) data shall be modified in the HLR; no effect in the SGSN; +- 2091 7) data shall be modified in both the HLR and the SGSN; +- 2092 8) withdrawal of GPRS subscription data or a basic service or a supplementary service requiring change to SGSN +2093 data; +- 2094 9) modification affects the roaming permission for the subscriber and the subscriber record shall be removed from +2095 the SGSN data base; +- 2096 10) withdrawal of GPRS Subscription caused by a change of Network Access Mode; +- 2097 11) authentication algorithm or authentication key of the subscriber is modified. + +2098 In cases 2 and 7 the HLR uses the MAP\_INSERT\_SUBSCRIBER\_DATA service. + +2099 In cases 3 and 8 the HLR uses the MAP\_DELETE\_SUBSCRIBER\_DATA service. + +2100 In cases 4, 5, 9, 10 and 11 the HLR uses the MAP\_CANCEL\_LOCATION service. + +2101 If the deletion of subscriber data fails, the HLR may repeat the request; the number of repeat attempts and the time in +2102 between are HLR operator options, depending on the error returned by the VLR or the SGSN. + +2103 The subscriber data modification process in the HLR is shown in figure 20.3/6. The MAP process invokes processes not +2104 defined in this clause; the definitions of these processes can be found as follows: + +2105 Insert\_Subs\_Data\_Stand\_Alone\_HLR see clause 25.7.3; + +2106 Cancel\_Location\_Child\_HLR see clause 19.1.2.2; + +2107 Insert\_GPRS\_Subs\_Data\_Stand\_Alone\_HLR see clause 25.7.4; + +2108 Cancel\_GPRS\_Location\_Child\_HLR see clause 19.1.2.2. + +2109 The macro Delete\_Subscriber\_Data\_HLR is shown in figure 20.3/7. The macro invokes macros not defined in this +2110 clause; the definitions of these macros can be found as follows: + +2111 Receive\_Open\_Cnf see clause 25.1.2; + +2112 Check\_Confirmation see clause 25.2.2. + +2113 The macro Delete\_GPRS\_Subscriber\_Data\_HLR is shown in figure 20.3/8. The macro invokes macros not defined in +2114 this clause; the definitions of these macros can be found as follows: + +2115    Receive\_Open\_Cnf           see clause 25.1.2; +2116    Check\_Confirmation       see clause 25.2.2. + +### 2117 20.3.2.2       Procedures in the VLR + +2118 The process in the VLR to update subscriber data in a stand-alone dialogue is shown in figure 20.3/9. The MAP process +2119 invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +2120    Check\_Indication           see clause 25.2.1; +2121    Insert\_Subs\_Data\_VLR   see clause 25.7.1. + +2122 The process in the VLR to delete subscriber data is shown in figure 20.3/10. The MAP process invokes a macro not +2123 defined in this clause; the definition of this macro can be found as follows: + +2124    Check\_Indication           see clause 25.2.1. + +### 2125 20.3.2.3       Procedures in the SGSN + +2126 The process in the SGSN to update subscriber data in a stand-alone dialogue is shown in figure 20.3/11. The MAP +2127 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +2128    Check\_Indication           see clause 25.2.1; +2129    Insert\_Subs\_Data\_SGSN   see clause 25.7.2. + +2130 The process in the SGSN to delete subscriber data is shown in figure 20.3/12. The MAP process invokes a macro not +2131 defined in this clause; the definition of this macro can be found as follows: + +2132    Check\_Indication           see clause 25.2.1. + +![Flowchart for process Delete_Subscriber_HLR. The process starts with 'Null', followed by 'OM_Delete_Subscriber_ind'. A decision 'Subscriber known?' follows. If 'No', it goes to 'Set User Error: Unknown subscriber'. If 'Yes', it checks 'Subscriber registered in an SGSN?'. If 'No', it goes to 'Cancel_GPRS_Location_Child_HLR'. If 'Yes', it goes to 'Subscriber registered in a VLR?'. If 'No', it goes to 'Cancel_Location_Child_HLR'. If 'Yes', it goes to 'Delete subscriber data from HLR'. Both 'Cancel' steps lead to 'Delete subscriber data from HLR'. From 'Delete subscriber data from HLR', it goes to 'OM_Delete_Subscriber_rsp' and finally 'Null'.](b6a1b0707decc2aedee3b44d70a2c5ae_img.jpg) + +process Delete\_Subscriber\_HLR + +Del\_Sub\_HLR1(1) + +Process in the HLR to delete a subscriber record from the SGSN and the VLR + +Signals to/from the right are to/from the OMC + +``` + +graph TD + Start([Null]) --> OM_Delete_Subscriber_ind{{OM_Delete_Subscriber_ind}} + OM_Delete_Subscriber_ind --> Subscriber_known{Subscriber known?} + Subscriber_known -- No --> Set_User_Error[Set User Error: Unknown subscriber] + Subscriber_known -- Yes --> Subscriber_registered_SGSN{Subscriber registered in an SGSN?} + Subscriber_registered_SGSN -- No --> Cancel_GPRS[Cancel_GPRS_Location_Child_HLR] + Subscriber_registered_SGSN -- Yes --> Subscriber_registered_VLR{Subscriber registered in a VLR?} + Cancel_GPRS --> Delete_data[Delete subscriber data from HLR] + Subscriber_registered_VLR -- No --> Cancel_Location[Cancel_Location_Child_HLR] + Subscriber_registered_VLR -- Yes --> Delete_data + Cancel_Location --> Delete_data + Delete_data --> OM_Delete_Subscriber_rsp{{OM_Delete_Subscriber_rsp}} + OM_Delete_Subscriber_rsp --> End([Null]) + Set_User_Error --> End + +``` + +Flowchart for process Delete\_Subscriber\_HLR. The process starts with 'Null', followed by 'OM\_Delete\_Subscriber\_ind'. A decision 'Subscriber known?' follows. If 'No', it goes to 'Set User Error: Unknown subscriber'. If 'Yes', it checks 'Subscriber registered in an SGSN?'. If 'No', it goes to 'Cancel\_GPRS\_Location\_Child\_HLR'. If 'Yes', it goes to 'Subscriber registered in a VLR?'. If 'No', it goes to 'Cancel\_Location\_Child\_HLR'. If 'Yes', it goes to 'Delete subscriber data from HLR'. Both 'Cancel' steps lead to 'Delete subscriber data from HLR'. From 'Delete subscriber data from HLR', it goes to 'OM\_Delete\_Subscriber\_rsp' and finally 'Null'. + +2133 + +2134 + +Figure 20.3/5: Process Delete\_Subscriber\_HLR + +![Flowchart for process Modify_Data_HLR. It starts with an entry point leading to 'Null', then 'OM_Modify_Subscriber_Data_ind'. A decision 'Subscriber known?' follows. If 'No', it goes to 'Set User Error: Unknown subscriber' then 'OM_Modify_Subscriber_Data_rsp' to 'Null'. If 'Yes', it goes to 'OM_Modify_Subscriber_Data_rsp', then 'Modify subscriber data in HLR database'. A decision 'Subscriber registered in a VLR?' follows. If 'No', it goes to connector '2'. If 'Yes', it goes to a 'Type of modification' decision. The 'Type of modification' has four branches: 'No effect in VLR' (to connector 2), 'Data to be modified in VLR' (to 'Insert_Subs_Data_Stand_Alone_HLR' then connector 2), 'Data to be deleted from VLR' (to 'Delete_Subscriber_Data_HLR' which has 'OK' to connector 2 and 'Error' to connector 1), and 'Subscriber record to be deleted from VLR' (to 'Cancel_Location_Child_HLR' then connector 2). A separate flow starts with connector '1', decision 'Repeat operation?'. If 'No', it goes to connector '2'. If 'Yes', it goes to 'Start repeat timer', 'Wait_For_Timer_Expiry', 'Repeat timer expired' (with an 'Internal' note), and then to the 'Type of modification' decision.](649db563f545d0dccc6d518baf536453_img.jpg) + +**process Modify\_Data\_HLR** **Mod\_Dat\_HLR1(2)** + +Process in the HLR to modify subscriber data in the SGSN and/or VLR + +Signals to/from the right are to/from the OMC + +``` + + graph TD + Entry([ ]) --> Null1([Null]) + Null1 --> OM_Modify_Subscriber_Data_ind{{OM_Modify_Subscriber_Data_ind}} + + OM_Modify_Subscriber_Data_ind --> Subscriber_known{Subscriber known?} + + Subscriber_known -- No --> Set_User_Error[Set User Error: Unknown subscriber] + Set_User_Error --> OM_Modify_Subscriber_Data_rsp1{{OM_Modify_Subscriber_Data_rsp}} + OM_Modify_Subscriber_Data_rsp1 --> Null2([Null]) + + Subscriber_known -- Yes --> OM_Modify_Subscriber_Data_rsp2{{OM_Modify_Subscriber_Data_rsp}} + OM_Modify_Subscriber_Data_rsp2 --> Modify_Subs_Data[Modify subscriber data in HLR database] + + Modify_Subs_Data --> Subscriber_registered{Subscriber registered in a VLR?} + + Subscriber_registered -- No --> Connector2_1((2)) + + Subscriber_registered -- Yes --> Type_of_Modification{Type of modification} + + Type_of_Modification -- "No effect in VLR" --> Connector2_2((2)) + + Type_of_Modification -- "Data to be modified in VLR" --> Insert_Subs_Data[Insert_Subs_Data_Stand_Alone_HLR] + Insert_Subs_Data --> Connector2_3((2)) + + Type_of_Modification -- "Data to be deleted from VLR" --> Delete_Subs_Data[Delete_Subscriber_Data_HLR] + + Delete_Subs_Data -- OK --> Connector2_4((2)) + + Delete_Subs_Data -- Error --> Connector1_1((1)) + + Type_of_Modification -- "Subscriber record to be deleted from VLR" --> Cancel_Location[Cancel_Location_Child_HLR] + Cancel_Location --> Connector2_5((2)) + + Connector1_2((1)) --> Repeat_Operation{Repeat operation?} + + Repeat_Operation -- No --> Connector2_6((2)) + + Repeat_Operation -- Yes --> Start_Repeat_Timer[Start repeat timer] + + Start_Repeat_Timer --> Wait_For_Timer_Expiry[Wait_For_Timer_Expiry] + + Wait_For_Timer_Expiry --> Repeat_Timer_Expired[Repeat timer expired] + + Note1[Internal] -.-> Repeat_Timer_Expired + + Repeat_Timer_Expired --> Type_of_Modification + +``` + +Flowchart for process Modify\_Data\_HLR. It starts with an entry point leading to 'Null', then 'OM\_Modify\_Subscriber\_Data\_ind'. A decision 'Subscriber known?' follows. If 'No', it goes to 'Set User Error: Unknown subscriber' then 'OM\_Modify\_Subscriber\_Data\_rsp' to 'Null'. If 'Yes', it goes to 'OM\_Modify\_Subscriber\_Data\_rsp', then 'Modify subscriber data in HLR database'. A decision 'Subscriber registered in a VLR?' follows. If 'No', it goes to connector '2'. If 'Yes', it goes to a 'Type of modification' decision. The 'Type of modification' has four branches: 'No effect in VLR' (to connector 2), 'Data to be modified in VLR' (to 'Insert\_Subs\_Data\_Stand\_Alone\_HLR' then connector 2), 'Data to be deleted from VLR' (to 'Delete\_Subscriber\_Data\_HLR' which has 'OK' to connector 2 and 'Error' to connector 1), and 'Subscriber record to be deleted from VLR' (to 'Cancel\_Location\_Child\_HLR' then connector 2). A separate flow starts with connector '1', decision 'Repeat operation?'. If 'No', it goes to connector '2'. If 'Yes', it goes to 'Start repeat timer', 'Wait\_For\_Timer\_Expiry', 'Repeat timer expired' (with an 'Internal' note), and then to the 'Type of modification' decision. + +2135 + +2136 + +**Figure 20.3/6 (sheet 1 of 2): Process Modify\_Data\_HLR** + +![Flowchart for process Modify_Data_HLR. It starts at connector 3, checks if an operation should be repeated. If yes, it starts a timer and waits for expiry. If no, it goes to Null. After timer expiry, it checks if the subscriber is registered in an SGSN. If no, it goes to Null. If yes, it checks the type of modification: no effect, modify, delete, or cancel. Modify, delete, and cancel lead to specific HLR actions followed by Null, OK/Error, and Null respectively. All paths eventually lead back to connector 3.](1300bcbec98350ff4935821e311faad8_img.jpg) + +process Modify\_Data\_HLR Mod\_Dat\_HLR2(2) + +Process in the HLR to modify subscriber data in the SGSN and/or VLR + +``` + + graph TD + 3((3)) --> Repeat{Repeat operation?} + Repeat -- No --> Null1([Null]) + Repeat -- Yes --> StartTimer[Start repeat timer] + StartTimer --> WaitTimer([Wait For Timer Expiry]) + WaitTimer --> TimerExpired{Repeat timer expired} + TimerExpired --> RegInSGSN{Subscriber registered in an SGSN?} + RegInSGSN -- No --> Null2([Null]) + RegInSGSN -- Yes --> TypeMod{Type of modification} + TypeMod -- "No effect in SGSN" --> Null3([Null]) + TypeMod -- "Data to be modified in SGSN" --> Insert[Insert_GPRS_Subs_Data_Stand_Alone_HLR] + Insert --> Null4([Null]) + TypeMod -- "Data to be deleted from SGSN" --> Delete[Delete_Subscriber_Data_HLR] + Delete -- OK --> Null5([Null]) + Delete -- Error --> 3 + TypeMod -- "Subscriber record to be deleted from SGSN" --> Cancel[Cancel_GPRS_Location_Child_HLR] + Cancel --> Null6([Null]) + +``` + +Flowchart for process Modify\_Data\_HLR. It starts at connector 3, checks if an operation should be repeated. If yes, it starts a timer and waits for expiry. If no, it goes to Null. After timer expiry, it checks if the subscriber is registered in an SGSN. If no, it goes to Null. If yes, it checks the type of modification: no effect, modify, delete, or cancel. Modify, delete, and cancel lead to specific HLR actions followed by Null, OK/Error, and Null respectively. All paths eventually lead back to connector 3. + +2137 + +2138 + +**Figure 20.3/6 (sheet 2 of 2): Process Modify\_Data\_HLR** + +![Flowchart for Delete_Subscriber_Data_HLR macro. The process starts with an entry point, followed by a selection of signals (MAP_OPEN_req, MAP_DELETE_SUBSCRIBER_DATA_req, MAP_DELIMITER_req). It then receives an Open_Cnf response. From there, it branches based on 'Vr', 'OK', and 'Error' paths. The 'Vr' path leads to 'Perform MAP Vr dialogue', which then checks for a 'Successful result?'. The 'OK' path leads to 'Wait_For_VLR_Response', which then branches into 'MAP_DELETE_SUBSCRIBER_DATA_cnf', 'MAP_NOTICE_ind', and an unnamed signal. The 'MAP_DELETE_SUBSCRIBER_DATA_cnf' path leads to 'Check_Confirmation', which then checks for 'Network Node Area Restricted received OR Roaming Restriction Due To Unsupported Feature'. The 'MAP_NOTICE_ind' path leads to 'MAP_CLOSE_req', which then leads to an 'Error' state. The unnamed signal path leads to a signal block containing 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind', which then leads to an 'Error' state.](bb6596f55ac1aa20c63d2a0c8fe00d27_img.jpg) + +macrodefinition Delete\_Subscriber\_Data\_HLR + +DSD\_HLR1(1) + +Macro in the HLR to delete specific subscriber data from a VLR + +Signals to/from the left are to/from the VLR + +``` + + graph TD + Start([ ]) --> Signals["MAP_OPEN_req +MAP_DELETE_SUBSCRIBER_DATA_req +MAP_DELIMITER_req"] + Signals --> OpenCnf[Receive_Open_Cnf] + OpenCnf -- Vr --> PerformVr[Perform MAP Vr dialogue] + OpenCnf -- OK --> WaitForVLR[Wait_For_VLR_Response] + OpenCnf -- Error --> Error1((Error)) + + PerformVr --> SuccessfulResult{Successful result?} + SuccessfulResult -- No --> Error2((Error)) + SuccessfulResult -- Yes --> OK1((OK)) + + WaitForVLR --> DeleteCnf{MAP_DELETE_SUBSCRIBER_DATA_cnf} + WaitForVLR --> NoticeInd{MAP_NOTICE_ind} + WaitForVLR --> UnnamedSignal{ } + + DeleteCnf --> CheckConfirmation[Check_Confirmation] + CheckConfirmation -- "User Error, Provider Error, Data Error" --> Error3((Error)) + CheckConfirmation -- OK --> Restricted{Network Node Area Restricted received OR Roaming Restriction Due To Unsupported Feature} + + Restricted -- No --> MSCFalse[MSC Area Restricted:= False] + Restricted -- Yes --> MSCTrue[MSC Area Restricted:= True] + + MSCFalse --> OK2((OK)) + MSCTrue --> OK2 + + NoticeInd --> CloseReq{MAP_CLOSE_req} + + UnnamedSignal --> AbortInd["MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind"] + + CloseReq --> Error4((Error)) + +``` + +Flowchart for Delete\_Subscriber\_Data\_HLR macro. The process starts with an entry point, followed by a selection of signals (MAP\_OPEN\_req, MAP\_DELETE\_SUBSCRIBER\_DATA\_req, MAP\_DELIMITER\_req). It then receives an Open\_Cnf response. From there, it branches based on 'Vr', 'OK', and 'Error' paths. The 'Vr' path leads to 'Perform MAP Vr dialogue', which then checks for a 'Successful result?'. The 'OK' path leads to 'Wait\_For\_VLR\_Response', which then branches into 'MAP\_DELETE\_SUBSCRIBER\_DATA\_cnf', 'MAP\_NOTICE\_ind', and an unnamed signal. The 'MAP\_DELETE\_SUBSCRIBER\_DATA\_cnf' path leads to 'Check\_Confirmation', which then checks for 'Network Node Area Restricted received OR Roaming Restriction Due To Unsupported Feature'. The 'MAP\_NOTICE\_ind' path leads to 'MAP\_CLOSE\_req', which then leads to an 'Error' state. The unnamed signal path leads to a signal block containing 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind', which then leads to an 'Error' state. + +2139 + +2140 + +Figure 20.3/7: Macro Delete\_Subscriber\_Data\_HLR + +![Flowchart for Delete_GPRS_Subscriber_Data_HLR macro. The process starts with an entry point, followed by a block of outgoing signals (MAP_OPEN_req, MAP_DELETE_SUBSCRIBER_DATA_req, MAP_DELIMITER_req). It then receives an Open_Cnf response. If OK, it enters a 'Wait_For_SGSN_Response' state. If Vr, Error, it goes to an Error state. From the wait state, three paths emerge: 1) MAP_DELETE_SUBSCRIBER_DATA_cnf leads to Check_Confirmation. If OK, it reaches a decision diamond. If User Error, Provider Error, or Data Error, it goes to an Error state. 2) MAP_NOTICE_ind leads to MAP_CLOSE_req, which then leads to an Error state. 3) An unlabeled path leads to a block of outgoing signals (MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind), which then leads to an Error state. The decision diamond checks for 'Network Node Area Restricted received OR Roaming Restricted in SGSN Due To Unsupported Feature'. If No, it checks 'SGSN Area Restricted:= False'. If Yes, it checks 'SGSN Area Restricted:= True'. Both lead to an OK state.](997b07a913097ec381a81470ca4ab97e_img.jpg) + +macrodefinition Delete\_GPRS\_Subscriber\_Data\_HLR + +DGCSD\_HLR(1) + +Macro in the HLR to delete specific subscriber data from an SGSN + +Signals to/from the left are to/from the SGSN + +``` + +graph TD + Start([ ]) --> Out1[MAP_OPEN_req +MAP_DELETE_SUBSCRIBER_DATA_req +MAP_DELIMITER_req] + Out1 --> Rec1[Receive Open_Cnf] + Rec1 -- OK --> Wait[Wait_For_SGSN_Response] + Rec1 -- "Vr, Error" --> Error1((Error)) + Wait --> Out2[MAP_DELETE_SUBSCRIBER_DATA_cnf] + Wait --> Out3[MAP_NOTICE_ind] + Wait --> Out4[ ] + Out2 --> Check[Check_Confirmation] + Check -- "User Error, Provider Error, Data Error" --> Error2((Error)) + Check -- OK --> Decision{ } + Out3 --> Rec2[MAP_CLOSE_req] + Rec2 --> Error3((Error)) + Out4 --> Out5[MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind] + Out5 --> Error4((Error)) + Decision -- "Network Node Area Restricted received OR +Roaming Restricted in SGSN Due To Unsupported Feature" --> Yes[Yes] + Decision -- No --> No1[SGSN Area Restricted:= False] + Yes --> Yes1[SGSN Area Restricted:= True] + No1 --> OK1((OK)) + Yes1 --> OK1 + +``` + +Flowchart for Delete\_GPRS\_Subscriber\_Data\_HLR macro. The process starts with an entry point, followed by a block of outgoing signals (MAP\_OPEN\_req, MAP\_DELETE\_SUBSCRIBER\_DATA\_req, MAP\_DELIMITER\_req). It then receives an Open\_Cnf response. If OK, it enters a 'Wait\_For\_SGSN\_Response' state. If Vr, Error, it goes to an Error state. From the wait state, three paths emerge: 1) MAP\_DELETE\_SUBSCRIBER\_DATA\_cnf leads to Check\_Confirmation. If OK, it reaches a decision diamond. If User Error, Provider Error, or Data Error, it goes to an Error state. 2) MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req, which then leads to an Error state. 3) An unlabeled path leads to a block of outgoing signals (MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind), which then leads to an Error state. The decision diamond checks for 'Network Node Area Restricted received OR Roaming Restricted in SGSN Due To Unsupported Feature'. If No, it checks 'SGSN Area Restricted:= False'. If Yes, it checks 'SGSN Area Restricted:= True'. Both lead to an OK state. + +2141 + +2142 + +Figure 20.3/8: Macro Delete\_GPRS\_Subscriber\_Data\_HLR + +![Flowchart for process Ins_Subs_Data_Stand_Alone_VLR. The process starts with an oval, followed by a 'Null' block. It then enters a loop: MAP_INSERT_SUBSCRIBER_DATA_ind -> Check_Indication. From Check_Indication, an 'OK' path leads to a decision 'IMSI known?'. If 'No', it goes to 'Set User Error: Unidentified Subscriber'. If 'Yes', it goes to another decision 'All received services & features supported?'. If 'No', it goes to 'Update subscriber data for supported services & features' then 'Set parameters for unsupported services & features'. If 'Yes', it goes to 'Update subscriber data'. Both 'Update subscriber data' and 'Set parameters for unsupported services & features' lead to a decision 'MSC area restricted due to regional subscription?'. If 'Yes', it goes to 'Set network node area restricted'. If 'No', it proceeds. All three paths ('Set User Error...', 'Set network node...', and the 'No' path) converge at a junction. From the junction, the flow goes to a block labeled 'MAP_INSERT_SUBSCRIBER_DATA_rsp' and 'MAP_DELIMITER_req', which then leads to 'Wait_For_Service_Indication'. An 'Error' path from 'Check_Indication' leads to 'Subscriber data confirmed by HLR:=False', which also converges at the junction.](89b65fcd380f864418aabeaa26627411_img.jpg) + +process Ins\_Subs\_Data\_Stand\_Alone\_VLR + +ISD\_SA\_VLR1(2) + +Process in the VLR to handle Insert Subscriber Data requests in a stand-alone dialogue + +Signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> Null[Null] + Null --> MAP_ind{MAP_INSERT_SUBSCRIBER_DATA_ind} + MAP_ind --> Check[Check_Indication] + Check -- OK --> IMSI{IMSI known?} + Check -- Error --> Confirmed[Subscriber data confirmed by HLR:=False] + IMSI -- No --> UserError[Set User Error: Unidentified Subscriber] + IMSI -- Yes --> Supported{All received services & features supported?} + Supported -- No --> UpdateSupported[Update subscriber data for supported services & features] + UpdateSupported --> SetParams[Set parameters for unsupported services & features] + Supported -- Yes --> UpdateData[Update subscriber data] + UpdateData --> Restricted{MSC area restricted due to regional subscription?} + SetParams --> Restricted + Restricted -- Yes --> NetworkNode[Set network node area restricted] + Restricted -- No --> Junction(( )) + UserError --> Junction + NetworkNode --> Junction + Confirmed --> Junction + Junction --> MAP_rsp{MAP_INSERT_SUBSCRIBER_DATA_rsp +MAP_DELIMITER_req} + MAP_rsp --> Wait[Wait_For_Service_Indication] + +``` + +Flowchart for process Ins\_Subs\_Data\_Stand\_Alone\_VLR. The process starts with an oval, followed by a 'Null' block. It then enters a loop: MAP\_INSERT\_SUBSCRIBER\_DATA\_ind -> Check\_Indication. From Check\_Indication, an 'OK' path leads to a decision 'IMSI known?'. If 'No', it goes to 'Set User Error: Unidentified Subscriber'. If 'Yes', it goes to another decision 'All received services & features supported?'. If 'No', it goes to 'Update subscriber data for supported services & features' then 'Set parameters for unsupported services & features'. If 'Yes', it goes to 'Update subscriber data'. Both 'Update subscriber data' and 'Set parameters for unsupported services & features' lead to a decision 'MSC area restricted due to regional subscription?'. If 'Yes', it goes to 'Set network node area restricted'. If 'No', it proceeds. All three paths ('Set User Error...', 'Set network node...', and the 'No' path) converge at a junction. From the junction, the flow goes to a block labeled 'MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp' and 'MAP\_DELIMITER\_req', which then leads to 'Wait\_For\_Service\_Indication'. An 'Error' path from 'Check\_Indication' leads to 'Subscriber data confirmed by HLR:=False', which also converges at the junction. + +2143 + +2144 + +Figure 20.3/9 (sheet 1 of 2): Process Ins\_Subs\_Data\_Stand\_Alone\_VLR + +![State transition diagram for process Ins_Subs_Data_Stand_Alone_VLR. The diagram shows a state machine with four main states: Wait_For_Service_Indication, Insert_Subs_Data_VLR, MAP_CLOSE_ind, and MAP_NOTICE_ind. Transitions are triggered by signals from the HLR (MAP_CLOSE_ind, MAP_NOTICE_ind, MAP_U_ABORT_ind, MAP_P_ABORT_ind) or result in signals to the HLR (Insert_Subs_Data_VLR, MAP_CLOSE_req). The process ends in two terminal states: Subscriber data confirmed by HLR:=True and Subscriber data confirmed by HLR:=False.](a4de814f6aad47c148e3f0e6edb48c55_img.jpg) + +process Ins\_Subs\_Data\_Stand\_Alone\_VLR + +ISD\_SA\_VLR2(2) + +Process in the VLR to handle Insert Subscriber Data requests in a stand-alone dialogue + +Signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Wait_For_Service_Indication + state "Insert Subscriber Data requests" as Insert_Subs_Data_VLR + state "MAP_CLOSE_ind" as MAP_CLOSE_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "Subscriber data confirmed by HLR:=True" as True + state "Subscriber data confirmed by HLR:=False" as False + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind" as Abort + + Wait_For_Service_Indication --> Insert_Subs_Data_VLR + Insert_Subs_Data_VLR --> Wait_For_Service_Indication + Wait_For_Service_Indication --> MAP_CLOSE_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + Wait_For_Service_Indication --> Abort + MAP_CLOSE_ind --> Store_data[Store subscriber data in VLR] + Store_data --> True + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> False + MAP_NOTICE_ind --> Abort + MAP_NOTICE_ind --> MAP_CLOSE_ind + Abort --> MAP_NOTICE_ind + +``` + +State transition diagram for process Ins\_Subs\_Data\_Stand\_Alone\_VLR. The diagram shows a state machine with four main states: Wait\_For\_Service\_Indication, Insert\_Subs\_Data\_VLR, MAP\_CLOSE\_ind, and MAP\_NOTICE\_ind. Transitions are triggered by signals from the HLR (MAP\_CLOSE\_ind, MAP\_NOTICE\_ind, MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind) or result in signals to the HLR (Insert\_Subs\_Data\_VLR, MAP\_CLOSE\_req). The process ends in two terminal states: Subscriber data confirmed by HLR:=True and Subscriber data confirmed by HLR:=False. + +2145 + +2146 + +Figure 20.3/9 (sheet 2 of 2): Process Ins\_Subs\_Data\_Stand\_Alone\_VLR + +![Flowchart for process Delete_Subs_Data_VLR. It starts with an oval, followed by a 'Null' block, then a 'MAP_DELETE_SUBSCRIBER_DATA_ind' message. A 'Check_Indication' block follows, leading to an 'IMSI known?' decision. If 'No', it goes to 'Set User Error: Unknown subscriber'. If 'Yes', it goes to 'Delete subscriber data from VLR', then 'Deletion successful?'. If 'No', it goes to 'Subscriber data confirmed by HLR:=False' then 'MAP_U_ABORT_req'. If 'Yes', it goes to a decision 'MSC area restricted due to regional subscription?'. If 'Yes', it goes to 'Set network node area restricted' then to a merge point. If 'No', it goes directly to the merge point. From the merge point, it goes to 'Subscriber data confirmed by HLR:=True', then a 'MAP_DELETE_SUBSCRIBER_DATA_rsp / MAP_CLOSE_req' message block, ending with an 'X' symbol. The 'Error' path from 'Check_Indication' leads to 'Subscriber data confirmed by HLR:=False' then to the same merge point.](157b9aaba9418b037266b482404acae7_img.jpg) + +**process Delete\_Subs\_Data\_VLR** **DSD\_VLR1(1)** + +Process in the VLR to handle Delete Subscriber Data requests + +Signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> Null[Null] + Null --> MAP_DELETE_SUBSCRIBER_DATA_ind[/MAP_DELETE_SUBSCRIBER_DATA_ind/] + MAP_DELETE_SUBSCRIBER_DATA_ind --> Check_Indication[Check_Indication] + Check_Indication -- OK --> IMSI_known{IMSI known?} + Check_Indication -- Error --> SubDataConfirmedFalse1[Subscriber data confirmed by HLR:=False] + IMSI_known -- No --> SetUserError[Set User Error: Unknown subscriber] + IMSI_known -- Yes --> DeleteSubData[Delete subscriber data from VLR] + DeleteSubData --> DeletionSuccessful{Deletion successful?} + DeletionSuccessful -- No --> SubDataConfirmedFalse2[Subscriber data confirmed by HLR:=False] + DeletionSuccessful -- Yes --> MSCAreaRestricted{MSC area restricted due to regional subscription?} + MSCAreaRestricted -- Yes --> SetNetworkNodeRestricted[Set network node area restricted] + SetNetworkNodeRestricted --> Merge1(( )) + MSCAreaRestricted -- No --> Merge1 + SubDataConfirmedFalse1 --> Merge2(( )) + SubDataConfirmedFalse2 --> Merge2 + SetUserError --> Merge2 + Merge1 --> SubDataConfirmedTrue[Subscriber data confirmed by HLR:=True] + SubDataConfirmedTrue --> MAP_DELETE_SUBSCRIBER_DATA_rsp[MAP_DELETE_SUBSCRIBER_DATA_rsp / MAP_CLOSE_req] + MAP_DELETE_SUBSCRIBER_DATA_rsp --> End1((X)) + Merge2 --> SubDataConfirmedFalse3[Subscriber data confirmed by HLR:=False] + SubDataConfirmedFalse3 --> MAP_U_ABORT_req[/MAP_U_ABORT_req/] + MAP_U_ABORT_req --> End2((X)) + +``` + +Flowchart for process Delete\_Subs\_Data\_VLR. It starts with an oval, followed by a 'Null' block, then a 'MAP\_DELETE\_SUBSCRIBER\_DATA\_ind' message. A 'Check\_Indication' block follows, leading to an 'IMSI known?' decision. If 'No', it goes to 'Set User Error: Unknown subscriber'. If 'Yes', it goes to 'Delete subscriber data from VLR', then 'Deletion successful?'. If 'No', it goes to 'Subscriber data confirmed by HLR:=False' then 'MAP\_U\_ABORT\_req'. If 'Yes', it goes to a decision 'MSC area restricted due to regional subscription?'. If 'Yes', it goes to 'Set network node area restricted' then to a merge point. If 'No', it goes directly to the merge point. From the merge point, it goes to 'Subscriber data confirmed by HLR:=True', then a 'MAP\_DELETE\_SUBSCRIBER\_DATA\_rsp / MAP\_CLOSE\_req' message block, ending with an 'X' symbol. The 'Error' path from 'Check\_Indication' leads to 'Subscriber data confirmed by HLR:=False' then to the same merge point. + +2147 + +2148 + +**Figure 20.3/10: Process Delete\_Subs\_Data\_VLR** + +![Flowchart for process Ins_Subs_Data_Stand_Alone_SGSN. The process starts with an oval, followed by a 'Null' block. It then enters a loop: MAP_INSERT_SUBSCRIBER_DATA_ind -> Check_Indication. From Check_Indication, an 'OK' path leads to a decision 'IMSI known?'. If 'No', it goes to 'Set User Error: Unidentified Subscriber'. If 'Yes', it goes to another decision 'All received services & features supported?'. If 'No', it goes to 'Update subscriber data for supported services & features' -> 'Set parameters for unsupported services & features'. If 'Yes', it goes to 'Update subscriber data'. Both 'Update subscriber data' and 'Set parameters for unsupported services & features' lead to a decision 'SGSN area restricted due to regional subscription?'. If 'Yes', it goes to 'Set network node area restricted'. If 'No', it proceeds. All three paths ('Set User Error...', 'Set network node...', and 'No' from the second decision) converge at a junction. From this junction, an 'Error' path leads to 'Subscriber data confirmed by HLR:=False', which loops back to the 'Check_Indication' block. The main path continues to a block with 'MAP_INSERT_SUBSCRIBER_DATA_rsp' and 'MAP_DELIMITER_req', which then leads to 'Wait_For_Service_Indication'.](6994939b855d6bde94efb2f31dee555e_img.jpg) + +process Ins\_Subs\_Data\_Stand\_Alone\_SGSN + +ISD\_SA\_SGSN1(2) + +Process in the SGSN to handle Insert Subscriber Data requests in a stand-alone dialogue + +Signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> Null[Null] + Null --> MAP_ind[/MAP_INSERT_SUBSCRIBER_DATA_ind/] + MAP_ind --> Check[Check_Indication] + Check -- OK --> IMSI{IMSI known?} + IMSI -- No --> ErrorSub[Set User Error: Unidentified Subscriber] + IMSI -- Yes --> AllSupp{All received services & features supported?} + AllSupp -- No --> UpdateSupp[Update subscriber data for supported services & features] + AllSupp -- Yes --> UpdateData[Update subscriber data] + UpdateSupp --> AreaRestricted{SGSN area restricted due to regional subscription?} + UpdateData --> AreaRestricted + AreaRestricted -- Yes --> NetworkRestricted[Set network node area restricted] + AreaRestricted -- No --> Junction(( )) + ErrorSub --> Junction + NetworkRestricted --> Junction + Junction -- Error --> Confirmed[Subscriber data confirmed by HLR:=False] + Confirmed --> Check + Junction --> MAP_rsp[/MAP_INSERT_SUBSCRIBER_DATA_rsp
MAP_DELIMITER_req/] + MAP_rsp --> Wait[Wait_For_Service_Indication] + +``` + +Flowchart for process Ins\_Subs\_Data\_Stand\_Alone\_SGSN. The process starts with an oval, followed by a 'Null' block. It then enters a loop: MAP\_INSERT\_SUBSCRIBER\_DATA\_ind -> Check\_Indication. From Check\_Indication, an 'OK' path leads to a decision 'IMSI known?'. If 'No', it goes to 'Set User Error: Unidentified Subscriber'. If 'Yes', it goes to another decision 'All received services & features supported?'. If 'No', it goes to 'Update subscriber data for supported services & features' -> 'Set parameters for unsupported services & features'. If 'Yes', it goes to 'Update subscriber data'. Both 'Update subscriber data' and 'Set parameters for unsupported services & features' lead to a decision 'SGSN area restricted due to regional subscription?'. If 'Yes', it goes to 'Set network node area restricted'. If 'No', it proceeds. All three paths ('Set User Error...', 'Set network node...', and 'No' from the second decision) converge at a junction. From this junction, an 'Error' path leads to 'Subscriber data confirmed by HLR:=False', which loops back to the 'Check\_Indication' block. The main path continues to a block with 'MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp' and 'MAP\_DELIMITER\_req', which then leads to 'Wait\_For\_Service\_Indication'. + +2149 + +2150 + +Figure 20.3/11 (sheet 1 of 2): Process Ins\_Subs\_Data\_Stand\_Alone\_SGSN + +![State transition diagram for process Ins_Subs_Data_Stand_Alone_SGSN. The diagram shows a state machine with four main states: Wait_For_Service_Indication, Insert_Subs_Data_SGSN, MAP_CLOSE_ind, and MAP_NOTICE_ind. Transitions are triggered by various MAP messages and result in actions like storing subscriber data or sending responses. The diagram includes callouts explaining the process and the direction of signals.](483699c07b228d3166457b63f36922df_img.jpg) + +process Ins\_Subs\_Data\_Stand\_Alone\_SGSN ISD\_SA\_SGSN2(2) + +*Process in the SGSN to handle Insert Subscriber Data requests in a stand-alone dialogue* + +*Signals to/from the right are to/from the HLR* + +``` + +stateDiagram-v2 + [*] --> Wait_For_Service_Indication + state "Insert_Subs_Data_SGSN" as Insert_Subs_Data_SGSN + state "MAP_CLOSE_ind" as MAP_CLOSE_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state " " as UnlabeledState + + Wait_For_Service_Indication --> Insert_Subs_Data_SGSN + Wait_For_Service_Indication --> MAP_CLOSE_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + Wait_For_Service_Indication --> UnlabeledState + + Insert_Subs_Data_SGSN --> Wait_For_Service_Indication + + MAP_CLOSE_ind --> Store_subscriber_data_in_SGSN + Store_subscriber_data_in_SGSN --> Subscriber_data_confirmed_by_HLR_True + Subscriber_data_confirmed_by_HLR_True --> [*] + + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Subscriber_data_confirmed_by_HLR_False + Subscriber_data_confirmed_by_HLR_False --> [*] + + UnlabeledState --> MAP_U_ABORT_ind_MAP_P_ABORT_ind + MAP_U_ABORT_ind_MAP_P_ABORT_ind --> UnlabeledState + +``` + +States and Transitions: + +- Initial State:** Wait\_For\_Service\_Indication +- State: Insert\_Subs\_Data\_SGSN** + - Transition to: Wait\_For\_Service\_Indication +- State: MAP\_CLOSE\_ind** + - Transition to: Store subscriber data in SGSN + - From: Store subscriber data in SGSN + - From: Subscriber data confirmed by HLR:=True + - End: [\*] +- State: MAP\_NOTICE\_ind** + - Transition to: MAP\_CLOSE\_req + - From: MAP\_CLOSE\_req + - From: Subscriber data confirmed by HLR:=False + - End: [\*] +- Unlabeled State (Orange)** + - Transition to: MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind + - From: MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind + +Callouts: + +- Process in the SGSN to handle Insert Subscriber Data requests in a stand-alone dialogue +- Signals to/from the right are to/from the HLR + +State transition diagram for process Ins\_Subs\_Data\_Stand\_Alone\_SGSN. The diagram shows a state machine with four main states: Wait\_For\_Service\_Indication, Insert\_Subs\_Data\_SGSN, MAP\_CLOSE\_ind, and MAP\_NOTICE\_ind. Transitions are triggered by various MAP messages and result in actions like storing subscriber data or sending responses. The diagram includes callouts explaining the process and the direction of signals. + +2151 + +2152 + +Figure 20.3/11 (sheet 2 of 2): Process Ins\_Subs\_Data\_Stand\_Alone\_SGSN + +![Flowchart for process Delete_Subs_Data_SGSN. The process starts with an oval, followed by a 'Null' block. It then receives a 'MAP_DELETE_SUBSCRIBER_DATA_ind' signal. A 'Check_Indication' block follows. From there, an 'OK' path leads to a decision 'IMSI known?'. If 'No', it goes to 'Set User Error: Unknown subscriber'. If 'Yes', it goes to 'Delete subscriber data from SGSN'. From there, a decision 'Deletion successful?' follows. If 'No', it goes to 'Subscriber data confirmed by HLR:=False' and then 'MAP_U_ABORT_req'. If 'Yes', it goes to another decision 'SGSN area restricted due to regional subscription?'. If 'Yes', it goes to 'Set network node area restricted'. If 'No', it goes to 'Subscriber data confirmed by HLR:=True'. Both 'Set network node area restricted' and 'Subscriber data confirmed by HLR:=True' lead to a common block. From this block, it goes to 'Subscriber data confirmed by HLR:=True' and then to a block with 'MAP_DELETE_SUBSCRIBER_DATA_rsp' and 'MAP_CLOSE_req'. An 'Error' path from 'Check_Indication' leads to 'Subscriber data confirmed by HLR:=False'.](e46f2cda7483721fe450058613289df5_img.jpg) + +process Delete\_Subs\_Data\_SGSN + +DSD\_SGSN1(1) + +Process in the SGSN to handle Delete Subscriber Data requests + +Signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> Null[Null] + Null --> MAP_DELETE_SUBSCRIBER_DATA_ind[/MAP_DELETE_SUBSCRIBER_DATA_ind/] + MAP_DELETE_SUBSCRIBER_DATA_ind --> Check_Indication[Check_Indication] + Check_Indication -- OK --> IMSI_known{IMSI known?} + Check_Indication -- Error --> HLR_False1[Subscriber data confirmed by HLR:=False] + IMSI_known -- No --> Unknown[Set User Error: Unknown subscriber] + IMSI_known -- Yes --> Delete_SGSN[Delete subscriber data from SGSN] + Delete_SGSN --> Deletion_successful{Deletion successful?} + Deletion_successful -- No --> HLR_False2[Subscriber data confirmed by HLR:=False] + Deletion_successful -- Yes --> Area_Restricted{SGSN area restricted due to regional subscription?} + Area_Restricted -- Yes --> Set_Restricted[Set network node area restricted] + Area_Restricted -- No --> HLR_True1[Subscriber data confirmed by HLR:=True] + Set_Restricted --> HLR_True1 + HLR_False1 --> MAP_U_ABORT_req[/MAP_U_ABORT_req/] + HLR_False2 --> MAP_U_ABORT_req + Unknown --> Common(( )) + HLR_True1 --> Common + Common --> MAP_DELETE_SUBSCRIBER_DATA_rsp[MAP_DELETE_SUBSCRIBER_DATA_rsp] + Common --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_DELETE_SUBSCRIBER_DATA_rsp --> End1([X]) + MAP_CLOSE_req --> End2([X]) + +``` + +Flowchart for process Delete\_Subs\_Data\_SGSN. The process starts with an oval, followed by a 'Null' block. It then receives a 'MAP\_DELETE\_SUBSCRIBER\_DATA\_ind' signal. A 'Check\_Indication' block follows. From there, an 'OK' path leads to a decision 'IMSI known?'. If 'No', it goes to 'Set User Error: Unknown subscriber'. If 'Yes', it goes to 'Delete subscriber data from SGSN'. From there, a decision 'Deletion successful?' follows. If 'No', it goes to 'Subscriber data confirmed by HLR:=False' and then 'MAP\_U\_ABORT\_req'. If 'Yes', it goes to another decision 'SGSN area restricted due to regional subscription?'. If 'Yes', it goes to 'Set network node area restricted'. If 'No', it goes to 'Subscriber data confirmed by HLR:=True'. Both 'Set network node area restricted' and 'Subscriber data confirmed by HLR:=True' lead to a common block. From this block, it goes to 'Subscriber data confirmed by HLR:=True' and then to a block with 'MAP\_DELETE\_SUBSCRIBER\_DATA\_rsp' and 'MAP\_CLOSE\_req'. An 'Error' path from 'Check\_Indication' leads to 'Subscriber data confirmed by HLR:=False'. + +2153 + +2154 + +Figure 20.3/12: Process Delete\_Subs\_Data\_SGSN + +2155 **20.3A Subscriber Data Management procedures for CSS** + +2156 Two types of subscriber data management procedures exist: + +- 2157 1) Subscriber Deletion; +- 2158 2) Subscriber Data Modification. + +2159 The subscriber deletion and subscriber data modification procedures are initiated by the OMC (see figures 20.3A/1, +2160 20.3A/2, 20.3A/3 and 20.3A/4). + +![Sequence diagram for non-GPRS subscriber deletion. Lifelines: VLR, CSS, OMC. Step 1: OMC to CSS. Step 2: CSS to VLR. Step 3: VLR to CSS. Step 4: CSS to OMC.](478a57893fbff452d4943a78b725a07e_img.jpg) + +``` +sequenceDiagram + participant OMC + participant CSS + participant VLR + Note right of OMC: 1 + OMC->>CSS: + Note right of CSS: 2 + CSS->>VLR: + Note right of VLR: 3 + VLR->>CSS: + Note right of CSS: 4 + CSS->>OMC: +``` + +Sequence diagram for non-GPRS subscriber deletion. Lifelines: VLR, CSS, OMC. Step 1: OMC to CSS. Step 2: CSS to VLR. Step 3: VLR to CSS. Step 4: CSS to OMC. + +2161 +2162 +2163 +2164 +2165 +2166 +2167 +2168 + +- 1) Delete Subscriber +- 2) MAP\_DELETE\_SUBSCRIBER\_DATA\_req/ind +- 3) MAP\_DELETE\_SUBSCRIBER\_DATA\_rsp/cnf +- 4) Subscriber Deleted + +**Figure 20.3A/1: Subscriber deletion procedure for non-GPRS** + +2169 In the subscriber deletion procedure for a non-GPRS subscriber the CSG subscription data for the subscriber in the +2170 VPLMN are removed from the VLR and the CSS. The CSS uses the MAP\_DELETE\_SUBSCRIBER\_DATA service. + +![Sequence diagram for GPRS subscriber deletion. Lifelines: SGSN, CSS, OMC. Step 1: OMC to CSS. Step 2: CSS to SGSN. Step 3: SGSN to CSS. Step 4: CSS to OMC.](6ead1e4ea94e914050b62a8502ec2e3d_img.jpg) + +``` +sequenceDiagram + participant OMC + participant CSS + participant SGSN + Note right of OMC: 1 + OMC->>CSS: + Note right of CSS: 2 + CSS->>SGSN: + Note right of SGSN: 3 + SGSN->>CSS: + Note right of CSS: 4 + CSS->>OMC: +``` + +Sequence diagram for GPRS subscriber deletion. Lifelines: SGSN, CSS, OMC. Step 1: OMC to CSS. Step 2: CSS to SGSN. Step 3: SGSN to CSS. Step 4: CSS to OMC. + +2171 +2172 +2173 +2174 +2175 +2176 +2177 +2178 + +- 1) Delete GPRS Subscriber +- 2) MAP\_DELETE\_SUBSCRIBER\_DATA\_req/ind +- 3) MAP\_DELETE\_SUBSCRIBER\_DATA\_rsp/cnf +- 4) GPRS Subscriber Deleted + +**Figure 20.3A/2: Subscriber deletion procedure for GPRS** + +2179 In the subscriber deletion procedure for a GPRS subscriber the CSG subscription data for the GPRS subscriber in the +2180 VPLMN are removed from the SGSN and the CSS. The CSS uses the MAP\_DELETE\_SUBSCRIBER\_DATA service. + +![Sequence diagram for Figure 20.3A/3: Subscriber data modification procedure for non-GPRS. The diagram shows three entities: VLR, CSS, and OMC. The sequence of messages is: 1) OMC sends a request to CSS; 2) CSS sends a request to VLR; 3) VLR sends a response to CSS; 4) CSS sends a response to OMC.](672a318767e4141941272424110be3b2_img.jpg) + +``` + +sequenceDiagram + participant OMC + participant CSS + participant VLR + Note right of OMC: 1) + OMC->>CSS: Request + Note right of CSS: 2) + CSS->>VLR: Request + Note right of VLR: 3) + VLR->>CSS: Response + Note right of CSS: 4) + CSS->>OMC: Response + +``` + +Sequence diagram for Figure 20.3A/3: Subscriber data modification procedure for non-GPRS. The diagram shows three entities: VLR, CSS, and OMC. The sequence of messages is: 1) OMC sends a request to CSS; 2) CSS sends a request to VLR; 3) VLR sends a response to CSS; 4) CSS sends a response to OMC. + +- 2181 +- 2182 +- 2183 1) Modify Subscriber Data +- 2184 2) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind or MAP\_DELETE\_SUBSCRIBER\_DATA\_req/ind +- 2185 3) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf or MAP\_DELETE\_SUBSCRIBER\_DATA\_rsp/cnf +- 2186 4) Subscriber Data Modified +- 2187 +- 2188 **Figure 20.3A/3: Subscriber data modification procedure for non-GPRS** + +![Sequence diagram for Figure 20.3A/4: Subscriber data modification procedure for GPRS. The diagram shows three entities: SGSN, CSS, and OMC. The sequence of messages is: 1) OMC sends a request to CSS; 2) CSS sends a request to SGSN; 3) SGSN sends a response to CSS; 4) CSS sends a response to OMC.](d17f5c469a96ddc06765b0c99361e999_img.jpg) + +``` + +sequenceDiagram + participant OMC + participant CSS + participant SGSN + Note right of OMC: 1) + OMC->>CSS: Request + Note right of CSS: 2) + CSS->>SGSN: Request + Note right of SGSN: 3) + SGSN->>CSS: Response + Note right of CSS: 4) + CSS->>OMC: Response + +``` + +Sequence diagram for Figure 20.3A/4: Subscriber data modification procedure for GPRS. The diagram shows three entities: SGSN, CSS, and OMC. The sequence of messages is: 1) OMC sends a request to CSS; 2) CSS sends a request to SGSN; 3) SGSN sends a response to CSS; 4) CSS sends a response to OMC. + +- 2189 +- 2190 +- 2191 1) Modify GPRS Subscriber Data +- 2192 2) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind or MAP\_DELETE\_SUBSCRIBER\_DATA\_req/ind +- 2193 3) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf or MAP\_DELETE\_SUBSCRIBER\_DATA\_rsp/cnf +- 2194 4) GPRS Subscriber Data Modified +- 2195 +- 2196 **Figure 20.3A/4: Subscriber data modification procedure for GPRS** + +2197 In the subscriber data modification procedure the CSG subscription data in the VPLMN for the subscriber data are + +2198 modified in the CSS and when necessary also in the VLR or in the SGSN. The CSS initiates one of the + +2199 MAP\_INSERT\_SUBSCRIBER\_DATA or MAP\_DELETE\_SUBSCRIBER\_DATA services depending on the modified + +2200 data. + +2201 **20.3A.1 Subscriber deletion procedure** + +2202 **20.3A.1.1 Procedure in the CSS** + +2203 The process in the CSS to delete subscriber is shown in figure 20.3A/5. In this case the CSS uses the + +2204 MAP\_DELETE\_SUBSCRIBER\_DATA service. + +2205 **20.3A.1.2 Procedure in the VLR** + +2206 The process in the VLR for the CSG subscriber deletion procedure is shown in figure 20.3A/9. + +2207 **20.3A.1.3 Procedure in the SGSN** + +2208 The process in the SGSN for the CSG subscriber deletion procedure is shown in figure 20.3A/11. + +## 2209 20.3A.2 Subscriber data modification procedure + +### 2210 20.3A.2.1 Procedure in the CSS + +2211 The OMC can modify the CSG subscriber data in several different ways. The modifications can be categorised in the +2212 following groups: + +- 2213 1) CSG subscription data shall be modified in the CSS; no effect in the VLR; +- 2214 2) CSG subscription data shall be modified in both the CSS and the VLR; +- 2215 3) withdrawal of CSG subscription data requiring change to VLR data. +- 2216 4) CSG subscription data shall be modified in the CSS; no effect in the SGSN; +- 2217 5) CSG subscription data shall be modified in both the CSS and the SGSN; +- 2218 6) withdrawal of CSG subscription data requiring change to SGSN data. + +2219 In cases 2 and 5 the CSS uses the MAP\_INSERT\_SUBSCRIBER\_DATA service. + +2220 In cases 3 and 6 the CSS uses the MAP\_DELETE\_SUBSCRIBER\_DATA service. + +2221 If the deletion of CSG subscriber data fails, the CSS may repeat the request; the number of repeat attempts and the time +2222 in between are CSS operator options, depending on the error returned by the VLR or the SGSN. The CSS removes the +2223 routing information after the completion of CSG subscriber data deletion procedure. + +2224 The CSG subscriber data modification process in the CSS is shown in figure 20.3A/6. The MAP process invokes +2225 processes not defined in this clause; the definitions of these processes can be found as follows: + +2226 Insert\_VCSG\_Subs\_Data\_Stand\_Alone\_CSS see clause 25.7.8; + +2227 The macro Delete\_VCSG\_Subs\_Data\_CSS is shown in figure 20.3A/7. The macro invokes macros not defined in this +2228 clause; the definitions of these macros can be found as follows: + +2229 Receive\_Open\_Cnf see clause 25.1.2; + +2230 Check\_Confirmation see clause 25.2.2. + +### 2231 20.3A.2.2 Procedures in the VLR + +2232 The process in the VLR to update CSG subscription data in the VPLMN for the subscriber in a stand-alone dialogue is +2233 shown in figure 20.3A/8. The MAP process invokes macros not defined in this clause; the definitions of these macros +2234 can be found as follows: + +2235 Check\_Indication see clause 25.2.1; + +2236 Insert\_Subs\_Data\_VLR see clause 25.7.1. + +2237 The process in the VLR to delete CSG subscriber data is shown in figure 20.3A/9. The MAP process invokes a macro +2238 not defined in this clause; the definition of this macro can be found as follows: + +2239 Check\_Indication see clause 25.2.1. + +### 2240 20.3A.2.3 Procedures in the SGSN + +2241 The process in the SGSN to update CSG subscription data in the VPLMN for the GPRS subscriber in a stand-alone +2242 dialogue is shown in figure 20.3A/10. The MAP process invokes macros not defined in this clause; the definitions of +2243 these macros can be found as follows: + +2244 Check\_Indication see clause 25.2.1; + +2245 Insert\_Subs\_Data\_SGSN see clause 25.7.2. + +2246 The process in the SGSN to delete subscriber data is shown in figure 20.3A/11. The MAP process invokes a macro not +2247 defined in this clause; the definition of this macro can be found as follows: + +2248     Check\_Indication               see clause 25.2.1. + +![Flowchart for process Delete_Subscriber_CSS. It starts with an oval 'Null', followed by a 'Null' rectangle. Then a parallelogram 'OM_Delete_Subscriber_ind'. A decision diamond 'Subscriber known?' has a 'No' path to 'Set User Error: Unknown subscriber' and a 'Yes' path to another decision diamond 'Subscriber registered in an SGSN?'. The 'Yes' path from the first diamond leads to 'Subscriber registered in an SGSN?'. From 'Subscriber registered in an SGSN?', a 'No' path leads to 'Delete_VCSG Subs_Data_CSS' and a 'Yes' path leads to 'Remove routing info from SGSN'. Both lead to a third decision diamond 'Subscriber registered in a VLR?'. From 'Subscriber registered in a VLR?', a 'No' path leads to 'Delete_VCSG Subs_Data_CSS' and a 'Yes' path leads to 'Remove routing info from VLR'. Both lead to 'Delete CSG subscriber data from CSS'. From 'Delete CSG subscriber data from CSS', the path leads to a parallelogram 'OM_Delete_Subscriber_rsp', which finally leads to an oval 'Null'.](5030a7405308d6b508b5a4e169901081_img.jpg) + +process Delete\_Subscriber\_CSS Del\_Sub\_CSS1(1) + +Process in the CSS to delete a subscriber record from the SGSN and/or the VLR + +Signals to/from the right are to/from the OMC + +``` + +graph TD + Start([Null]) --> Null1[Null] + Null1 --> OM_Delete_Subscriber_ind[/OM_Delete_Subscriber_ind/] + OM_Delete_Subscriber_ind --> Subscriber_known{Subscriber known?} + Subscriber_known -- No --> Set_User_Error[Set User Error: Unknown subscriber] + Subscriber_known -- Yes --> Subscriber_registered_SGSN{Subscriber registered in an SGSN?} + Subscriber_registered_SGSN -- No --> Delete_VCSG_Subs_Data_CSS1[Delete_VCSG Subs_Data_CSS] + Subscriber_registered_SGSN -- Yes --> Remove_routing_info_SGSN[Remove routing info from SGSN] + Delete_VCSG_Subs_Data_CSS1 --> Subscriber_registered_VLR{Subscriber registered in a VLR?} + Remove_routing_info_SGSN --> Subscriber_registered_VLR + Subscriber_registered_VLR -- No --> Delete_VCSG_Subs_Data_CSS2[Delete_VCSG Subs_Data_CSS] + Subscriber_registered_VLR -- Yes --> Remove_routing_info_VLR[Remove routing info from VLR] + Delete_VCSG_Subs_Data_CSS2 --> Delete_CSG_subscriber_data[Delete CSG subscriber data from CSS] + Remove_routing_info_VLR --> Delete_CSG_subscriber_data + Delete_CSG_subscriber_data --> OM_Delete_Subscriber_rsp[/OM_Delete_Subscriber_rsp/] + Set_User_Error --> OM_Delete_Subscriber_rsp + OM_Delete_Subscriber_rsp --> Null2([Null]) + +``` + +Flowchart for process Delete\_Subscriber\_CSS. It starts with an oval 'Null', followed by a 'Null' rectangle. Then a parallelogram 'OM\_Delete\_Subscriber\_ind'. A decision diamond 'Subscriber known?' has a 'No' path to 'Set User Error: Unknown subscriber' and a 'Yes' path to another decision diamond 'Subscriber registered in an SGSN?'. The 'Yes' path from the first diamond leads to 'Subscriber registered in an SGSN?'. From 'Subscriber registered in an SGSN?', a 'No' path leads to 'Delete\_VCSG Subs\_Data\_CSS' and a 'Yes' path leads to 'Remove routing info from SGSN'. Both lead to a third decision diamond 'Subscriber registered in a VLR?'. From 'Subscriber registered in a VLR?', a 'No' path leads to 'Delete\_VCSG Subs\_Data\_CSS' and a 'Yes' path leads to 'Remove routing info from VLR'. Both lead to 'Delete CSG subscriber data from CSS'. From 'Delete CSG subscriber data from CSS', the path leads to a parallelogram 'OM\_Delete\_Subscriber\_rsp', which finally leads to an oval 'Null'. + +2249 + +2250 + +Figure 20.3A/5: Process Delete\_Subscriber\_CSS + +![Flowchart for process Modify_Data_CSS. It starts with an entry point leading to 'Null', then 'OM_Modify_Subscriber_Data_ind'. A decision 'Subscriber known?' follows. If 'No', it goes to 'Set User Error: Unknown subscriber' and then 'Null'. If 'Yes', it goes to 'OM_Modify_Subscriber_Data_rsp', then 'Modify subscriber data in CSS database'. A decision 'Subscriber registered in a VLR?' follows. If 'No', it goes to connector '2'. If 'Yes', it goes to a 'Type of modification' decision. From 'Type of modification', three paths exist: 'No effect in VLR' (to connector '2'), 'Data to be modified in VLR' (to 'Insert_VCSG_Subs_Data_Stand_Alone_CSS' then to connector '2'), and 'Data to be deleted from VLR' (to 'Delete_VCSG_Subs_Data_CSS', then 'OK' leads to 'Remove VLR Routeing Info in CSS database' then to connector '2', while 'Error' leads to connector '1'). A separate path starts with connector '1', leading to 'Repeat operation?'. If 'No', it goes to 'Remove VLR Routeing Info in CSS database' then to connector '2'. If 'Yes', it goes to 'Start repeat timer', then 'Wait_For_Timer_Expiry', then 'Repeat timer expired' (reached via 'Internal' signal). From 'Repeat timer expired', it goes to the 'Type of modification' decision.](9d6590334113ac3b64d7959d0ad63ac2_img.jpg) + +**process Modify\_Data\_CSS** **Mod\_Dat\_CSS1(2)** + +Process in the CSS to modify VPLMN CSG subscriber data in the SGSN and/or VLR + +Signals to/from the right are to/from the OMC + +``` + +graph TD + Entry([ ]) --> Null1([Null]) + Null1 --> OM_Modify_Subscriber_Data_ind[/OM_Modify_Subscriber_Data_ind/] + OM_Modify_Subscriber_Data_ind --> Subscriber_known{Subscriber known?} + Subscriber_known -- No --> Set_User_Error[Set User Error: Unknown subscriber] + Set_User_Error --> Null2([Null]) + Subscriber_known -- Yes --> OM_Modify_Subscriber_Data_rsp1[/OM_Modify_Subscriber_Data_rsp/] + OM_Modify_Subscriber_Data_rsp1 --> Modify_CSS[Modify subscriber data in CSS database] + Modify_CSS --> Subscriber_registered{Subscriber registered in a VLR?} + Subscriber_registered -- No --> Connector_2_1((2)) + Subscriber_registered -- Yes --> Type_of_modification{Type of modification} + Type_of_modification -- "No effect in VLR" --> Connector_2_2((2)) + Type_of_modification -- "Data to be modified in VLR" --> Insert_VCSG[Insert_VCSG_Subs_Data_Stand_Alone_CSS] + Insert_VCSG --> Connector_2_3((2)) + Type_of_modification -- "Data to be deleted from VLR" --> Delete_VCSG[Delete_VCSG_Subs_Data_CSS] + Delete_VCSG -- OK --> Remove_VLR_Info[Remove VLR Routeing Info in CSS database] + Remove_VLR_Info --> Connector_2_4((2)) + Delete_VCSG -- Error --> Connector_1_1((1)) + Connector_1_2((1)) --> Repeat_operation{Repeat operation?} + Repeat_operation -- No --> Remove_VLR_Info_2[Remove VLR Routeing Info in CSS database] + Remove_VLR_Info_2 --> Connector_2_5((2)) + Repeat_operation -- Yes --> Start_Timer[Start repeat timer] + Start_Timer --> Wait_Timer[Wait_For_Timer_Expiry] + Wait_Timer --> Repeat_Timer_Expired[Repeat timer expired] + Internal[Internal] --> Repeat_Timer_Expired + Repeat_Timer_Expired --> Type_of_modification + +``` + +Flowchart for process Modify\_Data\_CSS. It starts with an entry point leading to 'Null', then 'OM\_Modify\_Subscriber\_Data\_ind'. A decision 'Subscriber known?' follows. If 'No', it goes to 'Set User Error: Unknown subscriber' and then 'Null'. If 'Yes', it goes to 'OM\_Modify\_Subscriber\_Data\_rsp', then 'Modify subscriber data in CSS database'. A decision 'Subscriber registered in a VLR?' follows. If 'No', it goes to connector '2'. If 'Yes', it goes to a 'Type of modification' decision. From 'Type of modification', three paths exist: 'No effect in VLR' (to connector '2'), 'Data to be modified in VLR' (to 'Insert\_VCSG\_Subs\_Data\_Stand\_Alone\_CSS' then to connector '2'), and 'Data to be deleted from VLR' (to 'Delete\_VCSG\_Subs\_Data\_CSS', then 'OK' leads to 'Remove VLR Routeing Info in CSS database' then to connector '2', while 'Error' leads to connector '1'). A separate path starts with connector '1', leading to 'Repeat operation?'. If 'No', it goes to 'Remove VLR Routeing Info in CSS database' then to connector '2'. If 'Yes', it goes to 'Start repeat timer', then 'Wait\_For\_Timer\_Expiry', then 'Repeat timer expired' (reached via 'Internal' signal). From 'Repeat timer expired', it goes to the 'Type of modification' decision. + +2251 + +2252 + +**Figure 20.3A/6 (sheet 1 of 2): Process Modify\_Data\_CSS** + +![Flowchart for process Modify_Data_CSS. It starts at connector 3, checks if a repeat operation is needed. If no, it removes SGSN routing info and ends. If yes, it starts a timer and waits for expiry. Once expired, it checks if the subscriber is registered in an SGSN. If not, it ends. If yes, it checks the type of modification: no effect, modify, or delete. Modify and delete both lead to database updates and then to connector 3. Delete also has an error path.](7c4fdc38f4200c353bcd874b5ff3d57a_img.jpg) + +process Modify\_Data\_CSS Mod\_Dat\_CSS2(2) + +Process in the CSS to modify VPLMN CSG subscriber data in the SGSN and/or VLR + +``` + + graph TD + 3((3)) --> Repeat{Repeat operation?} + Repeat -- No --> Remove1[Remove SGSN Routeing Info in CSS database] + Remove1 --> Null1([Null]) + Repeat -- Yes --> StartTimer[Start repeat timer] + StartTimer --> WaitTimer[Wait_For_Timer_Expiry] + WaitTimer --> TimerExpired{Repeat timer expired} + TimerExpired --> Registered{Subscriber registered in an SGSN?} + Registered -- No --> Null2([Null]) + Registered -- Yes --> TypeMod{Type of modification} + TypeMod -- "No effect in SGSN" --> Null3([Null]) + TypeMod -- "Data to be modified in SGSN" --> Insert[Insert_VCSG_Subs_Data_Stand_Alone_CSS] + Insert --> Null4([Null]) + TypeMod -- "Data to be deleted from SGSN" --> Delete[Delete_VCSG_Subs_Data_CSS] + Delete -- OK --> Remove2[Remove SGSN Routeing Info in CSS database] + Remove2 --> Null5([Null]) + Delete -- Error --> 3 + +``` + +Flowchart for process Modify\_Data\_CSS. It starts at connector 3, checks if a repeat operation is needed. If no, it removes SGSN routing info and ends. If yes, it starts a timer and waits for expiry. Once expired, it checks if the subscriber is registered in an SGSN. If not, it ends. If yes, it checks the type of modification: no effect, modify, or delete. Modify and delete both lead to database updates and then to connector 3. Delete also has an error path. + +2253 + +2254 + +Figure 20.3A/6 (sheet 2 of 2): Process Modify\_Data\_CSS + +![Flowchart for macro Delete_VCSG_Subs_Data_CSS. It starts with an entry point leading to a merge point for MAP_OPEN_req, MAP_DELETE_SUBSCRIBER_DATA_req, and MAP_DELIMITER_req. This is followed by a 'Receive_Open_Cnf' block. An 'OK' path leads to 'Wait_For_VLR_Or_SGSN_Response', while a 'Vr, Error' path leads to an 'Error' circle. From the wait block, three paths emerge: 1) 'MAP_DELETE_SUBSCRIBER_DATA_cnf' leads to 'Check_Confirmation', which has an 'OK' path to an 'OK' circle and an error path to an 'Error' circle. 2) 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req', which then leads to an 'Error' circle. 3) A third path leads to a merge point for 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind', which then leads to an 'Error' circle.](d11c6cc5ae4b83017d57a7fed1f5607a_img.jpg) + +**macrodefinition Delete\_VCSG\_Subs\_Data\_CSS** **DVSD\_CSS(1)** + +Macro in the CSS to delete CSG subscriber data in VPLMN from a VLR or SGSN + +Signals to/from the left are to/from the VLR or the SGSN + +``` +graph TD; Entry([ ]) --> Merge1{{ }}; Merge1 -- "MAP_OPEN_req +MAP_DELETE_SUBSCRIBER_DATA_req +MAP_DELIMITER_req" --> ReceiveCnf[Receive_Open_Cnf]; ReceiveCnf -- OK --> WaitForResponse([Wait_For_VLR_Or_SGSN_Response]); ReceiveCnf -- "Vr, Error" --> Error1((Error)); WaitForResponse --> DeleteCnf{MAP_DELETE_SUBSCRIBER_DATA_cnf}; WaitForResponse --> NoticeInd{MAP_NOTICE_ind}; WaitForResponse --> Merge2{{ }}; DeleteCnf --> CheckConfirmation[Check_Confirmation]; CheckConfirmation -- OK --> OK((OK)); CheckConfirmation -- "User Error, Provider Error, Data Error" --> Error2((Error)); NoticeInd --> CloseReq{MAP_CLOSE_req}; CloseReq --> Error3((Error)); Merge2 -- "MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind" --> Error3 +``` + +Flowchart for macro Delete\_VCSG\_Subs\_Data\_CSS. It starts with an entry point leading to a merge point for MAP\_OPEN\_req, MAP\_DELETE\_SUBSCRIBER\_DATA\_req, and MAP\_DELIMITER\_req. This is followed by a 'Receive\_Open\_Cnf' block. An 'OK' path leads to 'Wait\_For\_VLR\_Or\_SGSN\_Response', while a 'Vr, Error' path leads to an 'Error' circle. From the wait block, three paths emerge: 1) 'MAP\_DELETE\_SUBSCRIBER\_DATA\_cnf' leads to 'Check\_Confirmation', which has an 'OK' path to an 'OK' circle and an error path to an 'Error' circle. 2) 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req', which then leads to an 'Error' circle. 3) A third path leads to a merge point for 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind', which then leads to an 'Error' circle. + +**Figure 20.3A/7: Macro Delete\_VCSG\_Subs\_Data\_CSS** + +![Flowchart for process Ins_VCSG_Subs_Data_Stand_Alone_VLR. The process starts with an entry point, followed by a 'Null' state. It then receives a 'MAP_INSERT_SUBSCRIBER_DATA_ind' and enters a 'Check_Indication' state. From there, it checks if the IMSI is known. If not, it sets a user error for an unidentified subscriber. If known, it checks if all received services and features are supported. If not, it updates subscriber data for supported services and features and sets parameters for unsupported ones. If supported, it updates subscriber data. Next, it checks if the MSC area is restricted due to regional subscription. If yes, it sets the network node area restricted. Finally, it sends a 'MAP_INSERT_SUBSCRIBER_DATA_rsp' and 'MAP_DELIMITER_req' and enters a 'Wait_For_Service_Indication' state. An 'Error' path from 'Check_Indication' leads to 'Subscriber data confirmed by CSS:=False'.](4067b0820e16788e1e01899473b3a1e2_img.jpg) + +process Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_VLR + +IVSD\_SA\_VLR1(2) + +Process in the VLR to handle Insert Subscriber Data requests in a stand-alone dialogue + +Signals to/from the right are to/from the CSS + +``` + +graph TD + Entry([ ]) --> Null[Null] + Null --> Ind[MAP_INSERT_SUBSCRIBER_DATA_ind] + Ind --> Check[Check_Indication] + Check -- OK --> IMSI{IMSI known?} + Check -- Error --> CSS[Subscriber data confirmed by CSS:=False] + IMSI -- No --> ErrorSub[Set User Error Unidentified Subscriber] + IMSI -- Yes --> AllSupp{All received services & features supported?} + AllSupp -- No --> UpdateSupp[Update subscriber data for supported services & features] + UpdateSupp --> SetParams[Set parameters for unsupported services & features] + AllSupp -- Yes --> UpdateData[Update subscriber data] + UpdateData --> MSCRestricted{MSC area restricted due to regional subscription?} + MSCRestricted -- Yes --> NetworkRestricted[Set network node area restricted] + MSCRestricted -- No --> Join(( )) + ErrorSub --> Join + NetworkRestricted --> Join + CSS --> Join + Join --> Rsp[MAP_INSERT_SUBSCRIBER_DATA_rsp +MAP_DELIMITER_req] + Rsp --> Wait[Wait_For_Service_Indication] + +``` + +Flowchart for process Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_VLR. The process starts with an entry point, followed by a 'Null' state. It then receives a 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind' and enters a 'Check\_Indication' state. From there, it checks if the IMSI is known. If not, it sets a user error for an unidentified subscriber. If known, it checks if all received services and features are supported. If not, it updates subscriber data for supported services and features and sets parameters for unsupported ones. If supported, it updates subscriber data. Next, it checks if the MSC area is restricted due to regional subscription. If yes, it sets the network node area restricted. Finally, it sends a 'MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp' and 'MAP\_DELIMITER\_req' and enters a 'Wait\_For\_Service\_Indication' state. An 'Error' path from 'Check\_Indication' leads to 'Subscriber data confirmed by CSS:=False'. + +2258 + +2259 + +Figure 20.3A/8 (sheet 1 of 2): Process Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_VLR + +![State transition diagram for process Ins_VCSG_Subs_Data_Stand_Alone_VLR. The diagram shows transitions between states based on MAP messages. Initial state: Wait_For_Service_Indication. Transitions: Insert_Subs_Data_VLR leads to Wait_For_Service_Indication; MAP_CLOSE_ind leads to Store CSG subscriber data in VLR; MAP_NOTICE_ind leads to MAP_CLOSE_req. From MAP_CLOSE_req, a transition leads to an unlabeled state (receiving MAP_U_ABORT_ind, MAP_P_ABORT_ind) and another to 'Subscriber data confirmed by CSS:=False'. From Store CSG subscriber data in VLR, a transition leads to 'Subscriber data confirmed by CSS:=True'. Both final states lead to a dead state (marked with X).](3d9f6a7ee390e08ac762a77fe7472b9f_img.jpg) + +process Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_VLR + +IVSD\_SA\_VLR2(2) + +Process in the VLR to handle Insert Subscriber Data requests in a stand-alone dialogue + +Signals to/from the right are to/from the CSS + +``` + +stateDiagram-v2 + [*] --> Wait_For_Service_Indication + state "Wait_For_Service_Indication" as Wait_For_Service_Indication + state "Store CSG subscriber data in VLR" as Store CSG subscriber data in VLR + state "Subscriber data confirmed by CSS:=True" as Subscriber data confirmed by CSS:=True + state "Subscriber data confirmed by CSS:=False" as Subscriber data confirmed by CSS:=False + state "Unlabeled State" as Unlabeled State + state [*] as [*] + + Wait_For_Service_Indication --> Insert_Subs_Data_VLR : Insert_Subs_Data_VLR + Insert_Subs_Data_VLR --> Wait_For_Service_Indication : Wait_For_Service_Indication + Wait_For_Service_Indication --> MAP_CLOSE_ind : MAP_CLOSE_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind : MAP_NOTICE_ind + MAP_CLOSE_ind --> Store CSG subscriber data in VLR : Store CSG subscriber data in VLR + Store CSG subscriber data in VLR --> Subscriber data confirmed by CSS:=True : Subscriber data confirmed by CSS:=True + MAP_NOTICE_ind --> MAP_CLOSE_req : MAP_CLOSE_req + MAP_CLOSE_req --> Unlabeled State : MAP_U_ABORT_ind, MAP_P_ABORT_ind + MAP_CLOSE_req --> Subscriber data confirmed by CSS:=False : Subscriber data confirmed by CSS:=False + Subscriber data confirmed by CSS:=True --> [*] : X + Subscriber data confirmed by CSS:=False --> [*] : X + +``` + +State transition diagram for process Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_VLR. The diagram shows transitions between states based on MAP messages. Initial state: Wait\_For\_Service\_Indication. Transitions: Insert\_Subs\_Data\_VLR leads to Wait\_For\_Service\_Indication; MAP\_CLOSE\_ind leads to Store CSG subscriber data in VLR; MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req. From MAP\_CLOSE\_req, a transition leads to an unlabeled state (receiving MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind) and another to 'Subscriber data confirmed by CSS:=False'. From Store CSG subscriber data in VLR, a transition leads to 'Subscriber data confirmed by CSS:=True'. Both final states lead to a dead state (marked with X). + +2260 + +2261 + +Figure 20.3A/8 (sheet 2 of 2): Process Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_VLR + +![Flowchart for process Delete_VCSG_Subs_Data_VLR. The process starts with an initial node, followed by a 'Null' node. It then receives a 'MAP_DELETE_SUBSCRIBER_DATA_ind' signal. A 'Check_Indication' block follows. If 'OK', it checks if 'IMSI known?'. If 'No', it goes to 'Set User Error: Unknown subscriber'. If 'Yes', it proceeds to 'Delete CSG subscriber data received from CSS stored in the VLR'. From there, if 'Deletion successful?' is 'No', it goes to 'Subscriber data confirmed by CSS:=False'. If 'Yes', it checks if 'MSC area restricted due to regional subscription?'. If 'Yes', it goes to 'Set network node area restricted'. Both 'Set network node area restricted' and 'Subscriber data confirmed by CSS:=False' lead to 'Location Information confirmed by CSS:=False'. If 'MSC area restricted due to regional subscription?' is 'No', it goes to 'Subscriber data confirmed by CSS:=True', then 'Location Information confirmed by CSS:=False'. All three 'Location Information confirmed by CSS:=False' blocks lead to a merge node, which then leads to 'MAP_DELETE_SUBSCRIBER_DATA_rsp' and 'MAP_CLOSE_req'. An 'Error' path from 'Check_Indication' leads to 'Subscriber data confirmed by CSS:=False', then 'Location Information confirmed by CSS:=False'. The process ends with an exit node.](6a2cf14cfb5a58fc668f27ae692095c7_img.jpg) + +process Delete\_VCSG\_Subs\_Data\_VLR + +DVSD\_VLR1(1) + +Process in the VLR to handle Delete Subscriber Data requests + +Signals to/from the right are to/from the CSS + +``` + +graph TD + Start([ ]) --> Null[Null] + Null --> Ind[MAP_DELETE_SUBSCRIBER_DATA_ind] + Ind --> Check[Check_Indication] + Check -- OK --> IMSI{IMSI known?} + Check -- Error --> SubFalse1[Subscriber data confirmed by CSS:=False] + IMSI -- No --> UserError[Set User Error: Unknown subscriber] + IMSI -- Yes --> Delete[Delete CSG subscriber data received from CSS stored in the VLR] + Delete -- No --> SubFalse2[Subscriber data confirmed by CSS:=False] + Delete -- Yes --> Restricted{MSC area restricted due to regional subscription?} + Restricted -- Yes --> SetRestricted[Set network node area restricted] + Restricted -- No --> SubTrue[Subscriber data confirmed by CSS:=True] + SetRestricted --> LocFalse1[Location Information confirmed by CSS:=False] + SubFalse2 --> LocFalse2[Location Information confirmed by CSS:=False] + SubTrue --> LocFalse3[Location Information confirmed by CSS:=False] + SubFalse1 --> LocFalse4[Location Information confirmed by CSS:=False] + LocFalse1 --> Merge{ } + LocFalse2 --> Merge + LocFalse3 --> Merge + LocFalse4 --> Merge + Merge --> Rsp[MAP_DELETE_SUBSCRIBER_DATA_rsp +MAP_CLOSE_req] + Rsp --> End([X]) + UserError --> Merge + SubFalse1 --> LocFalse4 + LocFalse4 --> Abort[MAP_U_ABORT_req] + Abort --> End + +``` + +Flowchart for process Delete\_VCSG\_Subs\_Data\_VLR. The process starts with an initial node, followed by a 'Null' node. It then receives a 'MAP\_DELETE\_SUBSCRIBER\_DATA\_ind' signal. A 'Check\_Indication' block follows. If 'OK', it checks if 'IMSI known?'. If 'No', it goes to 'Set User Error: Unknown subscriber'. If 'Yes', it proceeds to 'Delete CSG subscriber data received from CSS stored in the VLR'. From there, if 'Deletion successful?' is 'No', it goes to 'Subscriber data confirmed by CSS:=False'. If 'Yes', it checks if 'MSC area restricted due to regional subscription?'. If 'Yes', it goes to 'Set network node area restricted'. Both 'Set network node area restricted' and 'Subscriber data confirmed by CSS:=False' lead to 'Location Information confirmed by CSS:=False'. If 'MSC area restricted due to regional subscription?' is 'No', it goes to 'Subscriber data confirmed by CSS:=True', then 'Location Information confirmed by CSS:=False'. All three 'Location Information confirmed by CSS:=False' blocks lead to a merge node, which then leads to 'MAP\_DELETE\_SUBSCRIBER\_DATA\_rsp' and 'MAP\_CLOSE\_req'. An 'Error' path from 'Check\_Indication' leads to 'Subscriber data confirmed by CSS:=False', then 'Location Information confirmed by CSS:=False'. The process ends with an exit node. + +2262 + +2263 + +Figure 20.3A/9: Process Delete\_VCSG\_Subs\_Data\_VLR + +![Flowchart for process Ins_VCSG_Subs_Data_Stand_Alone_SGSN. The process starts with an oval, followed by a 'Null' block. It then enters a loop with 'MAP_INSERT_SUBSCRIBER_DATA_ind', 'Check_Indication', and a decision 'IMSI known?'. If 'No', it goes to 'Set User Error: Unidentified Subscriber'. If 'Yes', it checks if all services and features are supported. If 'No', it updates data for supported services and sets parameters for unsupported ones. If 'Yes', it updates subscriber data. Both paths lead to a decision 'SGSN area restricted due to regional subscription?'. If 'Yes', it sets network node area restricted. If 'No', it proceeds. All paths converge to a block with 'MAP_INSERT_SUBSCRIBER_DATA_rsp' and 'MAP_DELIMITER_req', ending with 'Wait_For_Service_Indication'. An 'Error' path from 'Check_Indication' leads to 'Subscriber data confirmed by CSS:=False'.](78de160f13972924f5ca78417879b13b_img.jpg) + +process Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_SGSN + +IVSD\_SA\_SGSN1(2) + +Process in the SGSN to handle Insert Subscriber Data requests in a stand-alone dialogue + +Signals to/from the right are to/from the CSS + +``` + +graph TD + Start([ ]) --> Null[Null] + Null --> Ind[MAP_INSERT_SUBSCRIBER_DATA_ind] + Ind --> Check[Check_Indication] + Check -- OK --> IMSI{IMSI known?} + Check -- Error --> CSS[Subscriber data confirmed by CSS:=False] + IMSI -- No --> ErrorSub[Set User Error: Unidentified Subscriber] + IMSI -- Yes --> AllSupp{All received services & features supported?} + AllSupp -- No --> UpdateSupp[Update subscriber data for supported services & features] + UpdateSupp --> SetParams[Set parameters for unsupported services & features] + AllSupp -- Yes --> UpdateData[Update subscriber data] + UpdateSupp --> Restricted{SGSN area restricted due to regional subscription?} + SetParams --> Restricted + UpdateData --> Restricted + Restricted -- Yes --> SetRestricted[Set network node area restricted] + SetRestricted --> Join(( )) + CSS --> Join + ErrorSub --> Join + Join --> Rsp[MAP_INSERT_SUBSCRIBER_DATA_rsp +MAP_DELIMITER_req] + Rsp --> Wait[Wait_For_Service_Indication] + +``` + +Flowchart for process Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_SGSN. The process starts with an oval, followed by a 'Null' block. It then enters a loop with 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind', 'Check\_Indication', and a decision 'IMSI known?'. If 'No', it goes to 'Set User Error: Unidentified Subscriber'. If 'Yes', it checks if all services and features are supported. If 'No', it updates data for supported services and sets parameters for unsupported ones. If 'Yes', it updates subscriber data. Both paths lead to a decision 'SGSN area restricted due to regional subscription?'. If 'Yes', it sets network node area restricted. If 'No', it proceeds. All paths converge to a block with 'MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp' and 'MAP\_DELIMITER\_req', ending with 'Wait\_For\_Service\_Indication'. An 'Error' path from 'Check\_Indication' leads to 'Subscriber data confirmed by CSS:=False'. + +2264 + +2265 + +Figure 20.3A/10 (sheet 1 of 2): Process Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_SGSN + +![State transition diagram for process Ins_VCSG_Subs_Data_Stand_Alone_SGSN. It shows transitions between states like 'Wait_For_Service_Indication', 'Insert_Subs_Data_SGSN', 'Store CSG subscriber data in SGSN', and 'Subscriber data confirmed by CSS:=True/False'. Transitions are labeled with MAP messages like CLOSE_ind, NOTICE_ind, CLOSE_req, and ABORT_ind.](ac74e08980f38375bdb77b8e8d14bd0f_img.jpg) + +process Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_SGSN IVSD\_SA\_SGSN2(2) + +Process in the SGSN to handle Insert Subscriber Data requests in a stand-alone dialogue + +Signals to/from the right are to/from the CSS + +``` + +stateDiagram-v2 + [*] --> Wait_For_Service_Indication + state "Wait_For_Service_Indication" as Wait_For_Service_Indication + state "Insert_Subs_Data_SGSN" as Insert_Subs_Data_SGSN + state "Store CSG subscriber data in SGSN" as Store_CSG_subscriber_data_in_SGSN + state "Subscriber data confirmed by CSS:=True" as Subscriber_data_confirmed_by_CSS_True + state "Subscriber data confirmed by CSS:=False" as Subscriber_data_confirmed_by_CSS_False + + Wait_For_Service_Indication --> Insert_Subs_Data_SGSN : Insert_Subs_Data_SGSN + Insert_Subs_Data_SGSN --> Wait_For_Service_Indication : Wait_For_Service_Indication + Insert_Subs_Data_SGSN --> Store_CSG_subscriber_data_in_SGSN : MAP_CLOSE_ind + Store_CSG_subscriber_data_in_SGSN --> Subscriber_data_confirmed_by_CSS_True : Store CSG subscriber data in SGSN + Store_CSG_subscriber_data_in_SGSN --> Subscriber_data_confirmed_by_CSS_False : MAP_NOTICE_ind + Subscriber_data_confirmed_by_CSS_False --> Insert_Subs_Data_SGSN : MAP_CLOSE_req + Subscriber_data_confirmed_by_CSS_False --> [*] : + Subscriber_data_confirmed_by_CSS_False --> Insert_Subs_Data_SGSN : MAP_U_ABORT_ind, MAP_P_ABORT_ind + +``` + +State transition diagram for process Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_SGSN. It shows transitions between states like 'Wait\_For\_Service\_Indication', 'Insert\_Subs\_Data\_SGSN', 'Store CSG subscriber data in SGSN', and 'Subscriber data confirmed by CSS:=True/False'. Transitions are labeled with MAP messages like CLOSE\_ind, NOTICE\_ind, CLOSE\_req, and ABORT\_ind. + +2266 + +2267 + +Figure 20.3A/10 (sheet 2 of 2): Process Ins\_VCSG\_Subs\_Data\_Stand\_Alone\_SGSN + +![Flowchart for process Delete_VCSG_Subs_Data_SGSN. The process starts with an initial node, followed by a 'Null' node. It then receives a 'MAP_DELETE_SUBSCRIBER_DATA_ind' message. A 'Check_Indication' block is followed by a decision 'IMSI known?'. If 'No', it goes to 'Set User Error: Unknown subscriber'. If 'Yes', it proceeds to 'Delete CSG subscriber data received from CSS stored in the SGSN'. From there, a decision 'Deletion successful?' follows. If 'No', it goes to 'Subscriber data confirmed by CSS:=False' and then 'Location Information confirmed by CSS:=False', leading to 'MAP_U_ABORT_req'. If 'Yes', it checks 'SGSN area restricted due to regional subscription?'. If 'Yes', it goes to 'Set network node area restricted'. If 'No', it goes to 'Subscriber data confirmed by CSS:=True' and then 'Location Information confirmed by CSS:=False'. Both 'Set network node area restricted' and 'Location Information confirmed by CSS:=False' lead to a merge point before the final response 'MAP_DELETE_SUBSCRIBER_DATA_rsp' and 'MAP_CLOSE_req'. An 'Error' path from 'Check_Indication' leads to 'Subscriber data confirmed by CSS:=False' and 'Location Information confirmed by CSS:=False'.](351fc45d07147498cc7990485c230a41_img.jpg) + +process Delete\_VCSG\_Subs\_Data\_SGSN + +DVSD\_SGSN1(1) + +Process in the SGSN to handle Delete Subscriber Data requests + +Signals to/from the right are to/from the CSS + +``` + +graph TD + Start([ ]) --> Null[Null] + Null --> Ind[MAP_DELETE_SUBSCRIBER_DATA_ind] + Ind --> Check[Check_Indication] + Check -- OK --> IMSI{IMSI known?} + Check -- Error --> SubDataFalse1[Subscriber data confirmed by CSS:=False] + SubDataFalse1 --> LocInfoFalse1[Location Information confirmed by CSS:=False] + IMSI -- No --> UserError[Set User Error: Unknown subscriber] + IMSI -- Yes --> DeleteCSG[Delete CSG subscriber data received from CSS stored in the SGSN] + DeleteCSG --> Deletion{Deletion successful?} + Deletion -- No --> SubDataFalse2[Subscriber data confirmed by CSS:=False] + SubDataFalse2 --> LocInfoFalse2[Location Information confirmed by CSS:=False] + Deletion -- Yes --> Restricted{SGSN area restricted due to regional subscription?} + Restricted -- Yes --> SetRestricted[Set network node area restricted] + Restricted -- No --> SubDataTrue[Subscriber data confirmed by CSS:=True] + SubDataTrue --> LocInfoFalse3[Location Information confirmed by CSS:=False] + SetRestricted --> LocInfoFalse3 + SubDataFalse2 --> Merge(( )) + LocInfoFalse1 --> Merge + LocInfoFalse2 --> Merge + LocInfoFalse3 --> Merge + UserError --> Merge + Merge --> Res[MAP_DELETE_SUBSCRIBER_DATA_rsp +MAP_CLOSE_req] + Res --> End([ ]) + LocInfoFalse2 --> Abort[MAP_U_ABORT_req] + Abort --> End2([ ]) + +``` + +Flowchart for process Delete\_VCSG\_Subs\_Data\_SGSN. The process starts with an initial node, followed by a 'Null' node. It then receives a 'MAP\_DELETE\_SUBSCRIBER\_DATA\_ind' message. A 'Check\_Indication' block is followed by a decision 'IMSI known?'. If 'No', it goes to 'Set User Error: Unknown subscriber'. If 'Yes', it proceeds to 'Delete CSG subscriber data received from CSS stored in the SGSN'. From there, a decision 'Deletion successful?' follows. If 'No', it goes to 'Subscriber data confirmed by CSS:=False' and then 'Location Information confirmed by CSS:=False', leading to 'MAP\_U\_ABORT\_req'. If 'Yes', it checks 'SGSN area restricted due to regional subscription?'. If 'Yes', it goes to 'Set network node area restricted'. If 'No', it goes to 'Subscriber data confirmed by CSS:=True' and then 'Location Information confirmed by CSS:=False'. Both 'Set network node area restricted' and 'Location Information confirmed by CSS:=False' lead to a merge point before the final response 'MAP\_DELETE\_SUBSCRIBER\_DATA\_rsp' and 'MAP\_CLOSE\_req'. An 'Error' path from 'Check\_Indication' leads to 'Subscriber data confirmed by CSS:=False' and 'Location Information confirmed by CSS:=False'. + +2268 + +2269 + +Figure 20.3A/11: Process Delete\_VCSG\_Subs\_Data\_SGSN + +## 20.4 Subscriber Identity procedure + +In the subscriber identity procedure the IMSI of the subscriber is retrieved from the HLR. The procedure is shown in figure 20.4/1. + +![Sequence diagram of the subscriber identity procedure showing interactions between OMC, VLR, and HLR.](4965ba9124b08743865ab2ca64355ac0_img.jpg) + +``` +sequenceDiagram + participant OMC + participant VLR + participant HLR + Note left of OMC: 1) Identity request + OMC->>VLR: + Note right of VLR: 2) MAP_SEND_IMSI_req/ind + VLR->>HLR: + Note right of HLR: 3) MAP_SEND_IMSI_rsp/cnf + HLR->>VLR: + Note left of VLR: 4) Identity confirm + VLR->>OMC: +``` + +Sequence diagram of the subscriber identity procedure showing interactions between OMC, VLR, and HLR. + +2273 + +- 2274 +- 2275 1) Identity request +- 2276 2) MAP\_SEND\_IMSI\_req/ind +- 2277 3) MAP\_SEND\_IMSI\_rsp/cnf +- 2278 4) Identity confirm + +Figure 20.4/1: The subscriber identity procedure + +### 20.4.1 Procedure in the VLR + +The subscriber identity process in the VLR is shown in figure 20.4/2. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +- 2283 Receive\_Open\_Cnf see clause 25.1.2; +- 2284 Check\_Confirmation see clause 25.2.2. + +### 20.4.2 Procedure in the HLR + +The subscriber identity process in the HLR is shown in figure 20.4/3. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +- 2288 Receive\_Open\_Ind see clause 25.1.1; +- 2289 Check\_Indication see clause 25.2.1. + +2290 + +![Flowchart for process Send_IMSI_VLR. The process starts with an initial node, followed by a 'Null' node. It then receives an 'OM_Subscriber_Identity_ind' signal. Next, it sends 'MAP_OPEN_req', 'MAP_SEND_IMSI_req', and 'MAP_DELIMITER_req' signals. It then enters a 'Receive_Open_Cnf' state. A decision diamond 'Vr=V1?' follows. If 'Yes', it goes to 'Set User Error'. If 'No', it goes to 'Perform MAP Vr dialogue' and then to a 'Null' node. If 'OK', it goes to 'Wait_For_HLR_Response'. From there, it sends 'MAP_SEND_IMSI_cnf', 'MAP_NOTICE_ind', and another signal (MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind). It then enters a 'Check_Confirmation' state. From 'Check_Confirmation', an 'OK' response leads to 'OM_Subscriber_Identity_rsp' and then to a 'Null' node. A 'User Error, Provider Error, Data Error' response leads to 'Set User Error', which then leads to 'OM_Subscriber_Identity_rsp' and finally to a 'Null' node.](8ecf4fcb6fbc87c458f23d5fe82014b6_img.jpg) + +**process Send\_IMSI\_VLR** **SI\_VLR1(1)** + +Process in the VLR to request the IMSI of a subscriber from the HLR + +Signals to/from the left are to/from the OMC; signals to/from the right are to/from the HLR + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> In1{{ }} + In1 --> OM_Sig1[OM_Subscriber_Identity_ind] + OM_Sig1 --> Out1{{ }} + Out1 --> MAP_Sigs1["MAP_OPEN_req +MAP_SEND_IMSI_req +MAP_DELIMITER_req"] + MAP_Sigs1 --> RecOpenCnf[Receive_Open_Cnf] + RecOpenCnf --> VrV1{Vr=V1?} + VrV1 -- Yes --> SetUserErr1[Set User Error] + VrV1 -- No --> PerformMAP[Perform MAP Vr dialogue] + PerformMAP --> Null2([Null]) + VrV1 -- OK --> WaitForHLR[Wait_For_HLR_Response] + WaitForHLR --> Out2{{ }} + Out2 --> MAP_Sig2[MAP_SEND_IMSI_cnf] + WaitForHLR --> Out3{{ }} + Out3 --> MAP_Sig3[MAP_NOTICE_ind] + WaitForHLR --> Out4{{ }} + Out4 --> MAP_Sig4["MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind"] + MAP_Sig2 --> CheckConf[Check_Confirmation] + MAP_Sig3 --> Out5{{ }} + Out5 --> MAP_Sig5[MAP_CLOSE_req] + CheckConf -- OK --> In2{{ }} + In2 --> OM_Sig2[OM_Subscriber_Identity_rsp] + OM_Sig2 --> Null3([Null]) + CheckConf -- "User Error, +Provider Error, +Data Error" --> SetUserErr2[Set User Error] + SetUserErr2 --> In3{{ }} + In3 --> OM_Sig2 + +``` + +Flowchart for process Send\_IMSI\_VLR. The process starts with an initial node, followed by a 'Null' node. It then receives an 'OM\_Subscriber\_Identity\_ind' signal. Next, it sends 'MAP\_OPEN\_req', 'MAP\_SEND\_IMSI\_req', and 'MAP\_DELIMITER\_req' signals. It then enters a 'Receive\_Open\_Cnf' state. A decision diamond 'Vr=V1?' follows. If 'Yes', it goes to 'Set User Error'. If 'No', it goes to 'Perform MAP Vr dialogue' and then to a 'Null' node. If 'OK', it goes to 'Wait\_For\_HLR\_Response'. From there, it sends 'MAP\_SEND\_IMSI\_cnf', 'MAP\_NOTICE\_ind', and another signal (MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind). It then enters a 'Check\_Confirmation' state. From 'Check\_Confirmation', an 'OK' response leads to 'OM\_Subscriber\_Identity\_rsp' and then to a 'Null' node. A 'User Error, Provider Error, Data Error' response leads to 'Set User Error', which then leads to 'OM\_Subscriber\_Identity\_rsp' and finally to a 'Null' node. + +2291 + +2292 + +Figure 20.4/2: Process Send\_IMSI\_VLR + +![Flowchart for process Send_IMSI_HLR. It starts with an initial node, followed by 'Null', then 'Receive_Open_Ind'. From 'Receive_Open_Ind', three paths emerge: 'OK' leads to 'Wait_For_Service_Indication', 'Vr' leads to 'Perform MAP Vr dialogue', and 'Error' leads to 'Null'. 'Wait_For_Service_Indication' leads to a horizontal line with three branches: 'MAP_P_ABORT_ind' (leading to 'Null'), 'MAP_NOTICE_ind' (leading to 'MAP_CLOSE_req' then 'Null'), and 'MAP_SEND_IMSI_ind' (leading to 'Check_Indication'). 'Perform MAP Vr dialogue' leads to 'Null'. 'Check_Indication' leads to a decision 'Subscriber known?'. If 'Yes', it goes to 'Fetch IMSI'. If 'No', it goes to 'Set User Error: Unknown subscriber'. Both 'Fetch IMSI' and 'Set User Error' lead to a merge point. From this merge point, a box contains 'MAP_SEND_IMSI_rsp' and 'MAP_CLOSE_req', which then leads to a pentagonal node and finally 'Null'. An 'Error' path also leads from the 'Subscriber known?' decision to the merge point.](fdbf814083ff2d7d499496be85b828a1_img.jpg) + +**process Send\_IMSI\_HLR** **SI\_HLR1(1)** + +Process in the HLR to handle a request from the VLR for the IMSI of a subscriber + +Signals to/from the left are to/from the VLR + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind -- OK --> Wait_For_Service_Indication([Wait_For_Service_Indication]) + Receive_Open_Ind -- Vr --> Perform_MAP_Vr_dialogue[Perform MAP Vr dialogue] + Receive_Open_Ind -- Error --> Null2([Null]) + Wait_For_Service_Indication --> MAP_P_ABORT_ind[/MAP_P_ABORT_ind/] + Wait_For_Service_Indication --> MAP_NOTICE_ind[/MAP_NOTICE_ind/] + Wait_For_Service_Indication --> MAP_SEND_IMSI_ind[/MAP_SEND_IMSI_ind/] + Perform_MAP_Vr_dialogue --> Null3([Null]) + MAP_P_ABORT_ind --> Null4([Null]) + MAP_NOTICE_ind --> MAP_CLOSE_req[/MAP_CLOSE_req/] + MAP_CLOSE_req --> Null5([Null]) + MAP_SEND_IMSI_ind --> Check_Indication[Check_Indication] + Check_Indication -- OK --> Subscriber_known{Subscriber known?} + Subscriber_known -- No --> Set_User_Error[Set User Error: Unknown subscriber] + Subscriber_known -- Yes --> Fetch_IMSI[Fetch IMSI] + Set_User_Error --> Merge(( )) + Fetch_IMSI --> Merge + Merge --> MAP_SEND_IMSI_rsp[MAP_SEND_IMSI_rsp] + Merge --> MAP_CLOSE_req2[MAP_CLOSE_req] + MAP_SEND_IMSI_rsp --> Pentagonal{ } + MAP_CLOSE_req2 --> Pentagonal + Pentagonal --> Null6([Null]) + Subscriber_known -- Error --> Merge + +``` + +Flowchart for process Send\_IMSI\_HLR. It starts with an initial node, followed by 'Null', then 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', three paths emerge: 'OK' leads to 'Wait\_For\_Service\_Indication', 'Vr' leads to 'Perform MAP Vr dialogue', and 'Error' leads to 'Null'. 'Wait\_For\_Service\_Indication' leads to a horizontal line with three branches: 'MAP\_P\_ABORT\_ind' (leading to 'Null'), 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req' then 'Null'), and 'MAP\_SEND\_IMSI\_ind' (leading to 'Check\_Indication'). 'Perform MAP Vr dialogue' leads to 'Null'. 'Check\_Indication' leads to a decision 'Subscriber known?'. If 'Yes', it goes to 'Fetch IMSI'. If 'No', it goes to 'Set User Error: Unknown subscriber'. Both 'Fetch IMSI' and 'Set User Error' lead to a merge point. From this merge point, a box contains 'MAP\_SEND\_IMSI\_rsp' and 'MAP\_CLOSE\_req', which then leads to a pentagonal node and finally 'Null'. An 'Error' path also leads from the 'Subscriber known?' decision to the merge point. + +2293 + +2294 + +Figure 20.4/3: Process Send\_IMSI\_HLR + +--- + +## 2295 21 Call handling procedures + +### 2296 21.1 General + +2297 The MAP call handling procedures are used: + +- 2298 - to retrieve routeing information to handle a mobile terminating call; +- 2299 - to transfer control of a call back to the GMSC if the call is to be forwarded; +- 2300 - to retrieve and transfer information between anchor MSC and relay MSC for inter MSC group calls / broadcast +- 2301 calls; +- 2302 - to handle the reporting of MS status for call completion services; +- 2303 - to handle the notification of remote user free for CCBS; +- 2304 - to handle the alerting and termination of ongoing call activities for a specific subscriber; +- 2305 - to handle early release of no longer needed resources; +- 2306 - to relay a mobile terminating call from the old to the new MSC during the Mobile Terminating Roaming +- 2307 Forwarding procedure. + +2308 The procedures to handle a mobile originating call and a mobile terminating call after the call has arrived at the +2309 destination MSC do not require any signalling over a MAP interface. These procedures are specified in 3GPP TS +2310 23.018 [97]. + +2311 The stage 2 specification for the retrieval of routeing information to handle a mobile terminating call is in 3GPP TS +2312 23.018 [97]; modifications to this procedure for CAMEL are specified in 3GPP TS 23.078 [98], for optimal routeing of +2313 a basic mobile-to-mobile call in 3GPP TS 23.079 [99] and for CCBS in 3GPP TS 23.093 [107]. The interworking +2314 between the MAP signalling procedures and the call handling procedures for each entity (GMSC, HLR and VLR) is +2315 shown by the transfer of signals between these procedures. + +2316 The stage 2 specification for the transfer of control of a call back to the GMSC if the call is to be forwarded is in 3GPP +2317 TS 23.079 [99]. The interworking between the MAP signalling procedures and the call handling procedures for each +2318 entity (VMSC and GMSC) is shown by the transfer of signals between these procedures. + +2319 The stage 2 specifications for inter MSC group calls / broadcast calls are in 3GPP TS 43.068 [100] and 3GPP TS 43.069 +2320 [101]. The interworking between the MAP signalling procedures and the group call /broadcast call procedures for each +2321 entity (Anchor MSC and Relay MSC) is shown by the transfer of signals between these procedures. + +2322 The interworking between the call handling procedures and signalling protocols other than MAP are shown in 3GPP TS +2323 23.018, 3GPP TS 23.078 and 3GPP TS 23.079 [99]. + +2324 The stage 2 specification for the handling of reporting of MS status for call completion services and notification of +2325 remote user free for CCBS is in 3GPP TS 23.093 [107]. + +2326 The stage 2 specification for the Mobile Terminating Roaming Forwarding procedure is in 3GPP TS 23.018 [97] and +2327 3GPP TS 23.012 [23]. + +### 2328 21.2 Retrieval of routing information + +#### 2329 21.2.1 General + +2330 The message flows for successful retrieval of routeing information for a mobile terminating call are shown in +2331 figure 21.2/1 (mobile terminating call which has not been optimally routed) and 21.2/2 (mobile-to-mobile call which +2332 has been optimally routed). The message flow for successful retrieval of routeing information for a gsmSCF initiated +2333 call is shown in figure 21.2/3. The message flow for a successful Mobile Terminating Roaming Forwarding procedure +2334 is shown in figure 21.2/4. + +![Sequence diagram showing message flow for retrieval of routing information between PSTN/ISDN, GMSC, HLR, VLR, and MSC. The diagram shows 14 numbered message exchanges between these entities.](16fcd4fa5a01a7016b528f4dfad779cb_img.jpg) + +``` + +sequenceDiagram + participant PSTN_ISDN as PSTN/ISDN + participant GMSC + participant HLR + participant VLR + participant MSC + + Note right of PSTN_ISDN: 1) I_IAM (Note 1) + PSTN_ISDN->>GMSC: + Note right of GMSC: 2) MAP_SEND_ROUTING_INFORMATION_req/ind (Note 2) + GMSC->>HLR: + Note right of HLR: 3) MAP_PROVIDE_SUBSCRIBER_INFO_req/ind (Note 3, Note 4) + HLR->>VLR: + Note right of VLR: 4) MAP_PROVIDE_SUBSCRIBER_INFO_rsp/cnf (Note 4) + VLR->>HLR: + Note right of HLR: 5) MAP_SEND_ROUTING_INFORMATION_rsp/cnf (Note 4) + HLR->>GMSC: + Note right of GMSC: 6) MAP_SEND_ROUTING_INFORMATION_req/ind (Note 4) + GMSC->>HLR: + Note right of HLR: 7) MAP_PROVIDE_ROAMING_NUMBER_req/ind + HLR->>VLR: + Note right of VLR: 8) MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf + VLR->>HLR: + Note right of HLR: 9) MAP_SEND_ROUTING_INFORMATION_rsp/cnf + HLR->>GMSC: + Note right of GMSC: 10) I_IAM (Note 1) + GMSC->>MSC: + Note right of MSC: 11) MAP_RESTORE_DATA_req/ind (Note 4) + MSC->>HLR: + Note right of HLR: 12) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 4) + HLR->>VLR: + Note right of VLR: 13) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 4) + VLR->>HLR: + Note right of HLR: 14) MAP_RESTORE_DATA_rsp/cnf (Note 4) + HLR->>GMSC: + +``` + +Sequence diagram showing message flow for retrieval of routing information between PSTN/ISDN, GMSC, HLR, VLR, and MSC. The diagram shows 14 numbered message exchanges between these entities. + +2335 + +2336 + +- 2337 1) I\_IAM (Note 1) +- 2338 2) MAP\_SEND\_ROUTING\_INFORMATION\_req/ind (Note 2) +- 2339 3) *MAP\_PROVIDE\_SUBSCRIBER\_INFO\_req/ind* (Note 3, Note 4) +- 2340 4) *MAP\_PROVIDE\_SUBSCRIBER\_INFO\_rsp/cnf* (Note 4) +- 2341 5) *MAP\_SEND\_ROUTING\_INFORMATION\_rsp/cnf* (Note 4) +- 2342 6) *MAP\_SEND\_ROUTING\_INFORMATION\_req/ind* (Note 4) +- 2343 7) *MAP\_PROVIDE\_ROAMING\_NUMBER\_req/ind* +- 2344 8) *MAP\_PROVIDE\_ROAMING\_NUMBER\_rsp/cnf* +- 2345 9) *MAP\_SEND\_ROUTING\_INFORMATION\_rsp/cnf* +- 2346 10) I\_IAM (Note 1) +- 2347 11) *MAP\_RESTORE\_DATA\_req/ind* (Note 4) +- 2348 12) *MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind* (Note 4) +- 2349 13) *MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf* (Note 4) +- 2350 14) *MAP\_RESTORE\_DATA\_rsp/cnf* (Note 4) + +2351 + +2352 NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the +2353 MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations +2354 and ETSI specification: + +- 2355 - Q.721-725 - Telephone User Part (TUP); +- 2356 - ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part +2357 (ISUP) version 2 for the international interface; Part 1: Basic services. + +2358 NOTE 2: This service may also be used by an ISDN exchange for obtaining routing information from the HLR. + +2359 NOTE 3: As a network operator option, the HLR sends *MAP\_PROVIDE\_SUBSCRIBER\_INFORMATION* to the +2360 VLR. For further details on the CAMEL procedures refer to 3GPP TS 23.078 [98]. + +2361 NOTE 4: Services printed in *italics* are optional. + +2362 + +2363 + +**Figure 21.2/1: Message flow for retrieval of routing information (non-optimally routed call)** + +![Sequence diagram showing message flow for retrieval of routing information (optimally routed call) between VMSC, GMSC, HLR, and VLR. The diagram includes 12 numbered messages: 1) I_IAM from VMSC to GMSC; 2) MAP_SEND_ROUTING_INFORMATION_req/ind from GMSC to HLR; 3) MAP_PROVIDE_SUBSCRIBER_INFO_req/ind from HLR to VLR; 4) MAP_PROVIDE_SUBSCRIBER_INFO_rsp/cnf from VLR to HLR; 5) MAP_PROVIDE_ROAMING_NUMBER_req/ind from HLR to VLR; 6) MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf from VLR to HLR; 7) MAP_SEND_ROUTING_INFORMATION_rsp/cnf from HLR to GMSC; 8) I_IAM from GMSC to MSC; 9) MAP_RESTORE_DATA_req/ind from GMSC to HLR; 10) MAP_INSERT_SUBSCRIBER_DATA_req/ind from HLR to VLR; 11) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf from VLR to HLR; 12) MAP_RESTORE_DATA_rsp/cnf from HLR to GMSC.](601fa245dc7f9388c1cc2d2c4ddb4a14_img.jpg) + +``` + +sequenceDiagram + participant VMSC + participant GMSC + participant HLR + participant VLR + participant MSC + + Note left of VMSC: + VMSC->>GMSC: 1) I_IAM (Note 1) + GMSC->>HLR: 2) MAP_SEND_ROUTING_INFORMATION_req/ind + HLR->>VLR: 3) MAP_PROVIDE_SUBSCRIBER_INFO_req/ind (Note 2) + VLR->>HLR: 4) MAP_PROVIDE_SUBSCRIBER_INFO_rsp/cnf (Note 2) + HLR->>VLR: 5) MAP_PROVIDE_ROAMING_NUMBER_req/ind (Note 2) + VLR->>HLR: 6) MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf (Note 2) + HLR->>GMSC: 7) MAP_SEND_ROUTING_INFORMATION_rsp/cnf + GMSC->>MSC: 8) I_IAM (Note 1) + GMSC->>HLR: 9) MAP_RESTORE_DATA_req/ind (Note 3) + HLR->>VLR: 10) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3) + VLR->>HLR: 11) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3) + HLR->>GMSC: 12) MAP_RESTORE_DATA_rsp/cnf (Note 3) + +``` + +Sequence diagram showing message flow for retrieval of routing information (optimally routed call) between VMSC, GMSC, HLR, and VLR. The diagram includes 12 numbered messages: 1) I\_IAM from VMSC to GMSC; 2) MAP\_SEND\_ROUTING\_INFORMATION\_req/ind from GMSC to HLR; 3) MAP\_PROVIDE\_SUBSCRIBER\_INFO\_req/ind from HLR to VLR; 4) MAP\_PROVIDE\_SUBSCRIBER\_INFO\_rsp/cnf from VLR to HLR; 5) MAP\_PROVIDE\_ROAMING\_NUMBER\_req/ind from HLR to VLR; 6) MAP\_PROVIDE\_ROAMING\_NUMBER\_rsp/cnf from VLR to HLR; 7) MAP\_SEND\_ROUTING\_INFORMATION\_rsp/cnf from HLR to GMSC; 8) I\_IAM from GMSC to MSC; 9) MAP\_RESTORE\_DATA\_req/ind from GMSC to HLR; 10) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind from HLR to VLR; 11) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf from VLR to HLR; 12) MAP\_RESTORE\_DATA\_rsp/cnf from HLR to GMSC. + +2364 + +2365 + +- 2366 1) I\_IAM (Note 1) +- 2367 2) MAP\_SEND\_ROUTING\_INFORMATION\_req/ind +- 2368 3) MAP\_PROVIDE\_SUBSCRIBER\_INFO\_req/ind (Note 2) +- 2369 4) MAP\_PROVIDE\_SUBSCRIBER\_INFO\_rsp/cnf (Note 2) +- 2370 5) MAP\_PROVIDE\_ROAMING\_NUMBER\_req/ind (Note 2) +- 2371 6) MAP\_PROVIDE\_ROAMING\_NUMBER\_rsp/cnf (Note 2) +- 2372 7) MAP\_SEND\_ROUTING\_INFORMATION\_rsp/cnf +- 2373 8) I\_IAM (Note 1) +- 2374 9) *MAP\_RESTORE\_DATA\_req/ind (Note 3)* +- 2375 10) *MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind (Note 3)* +- 2376 11) *MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf (Note 3)* +- 2377 12) *MAP\_RESTORE\_DATA\_rsp/cnf (Note 3)* + +2378 + +2379 NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the + 2380 MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations + 2381 & ETSI specification: + 2382 - Q.721-725 - Telephone User Part (TUP); + 2383 - ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part + 2384 (ISUP) version 2 for the international interface; Part 1: Basic services. + +2385 NOTE 2: For Optimal Routeing phase 1, only one of the information flows for Provide Subscriber Info and Provide + 2386 Roaming Number is used. + +2387 NOTE 3: Services printed in *italics* are optional. + +2388 + +2389 + +**Figure 21.2/2: Message flow for retrieval of routing information (optimally routed call)** + +2390 + +![Sequence diagram showing message flow between gsmSCF, HLR, and VLR. The sequence starts with gsmSCF sending a request to HLR (1). HLR responds (2). gsmSCF sends another request (3). HLR sends a request to VLR (4). VLR responds (5). HLR responds to gsmSCF (6). HLR sends a request to VLR (7). VLR responds (8). HLR sends a request to VLR (9). VLR responds (10).](70711ca94e7e6d64dd173b9bf46f602a_img.jpg) + +``` + +sequenceDiagram + participant gsmSCF + participant HLR + participant VLR + Note right of HLR: 1 + gsmSCF->>HLR: + Note left of gsmSCF: 2 + HLR-->>gsmSCF: + Note right of HLR: 3 + gsmSCF->>HLR: + Note right of HLR: 4 + HLR->>VLR: + Note left of HLR: 5 + VLR-->>HLR: + Note left of gsmSCF: 6 + HLR-->>gsmSCF: + Note left of HLR: 7 + HLR->>VLR: + Note right of HLR: 8 + VLR-->>HLR: + Note left of HLR: 9 + HLR->>VLR: + Note right of HLR: 10 + VLR-->>HLR: + +``` + +Sequence diagram showing message flow between gsmSCF, HLR, and VLR. The sequence starts with gsmSCF sending a request to HLR (1). HLR responds (2). gsmSCF sends another request (3). HLR sends a request to VLR (4). VLR responds (5). HLR responds to gsmSCF (6). HLR sends a request to VLR (7). VLR responds (8). HLR sends a request to VLR (9). VLR responds (10). + +2391 + +- 2392 1) MAP\_SEND\_ROUTING\_INFORMATION\_req/ind +- 2393 2) *MAP\_SEND\_ROUTING\_INFORMATION\_rsp/cnf* (Note 1) +- 2394 3) *MAP\_SEND\_ROUTING\_INFORMATION\_req/ind* (Note 1) +- 2395 4) MAP\_PROVIDE\_ROAMING\_NUMBER\_req/ind +- 2396 5) MAP\_PROVIDE\_ROAMING\_NUMBER\_rsp/cnf +- 2397 6) MAP\_SEND\_ROUTING\_INFORMATION\_rsp/cnf +- 2398 7) *MAP\_RESTORE\_DATA\_req/ind* (Note 1) +- 2399 8) *MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind* (Note 1) +- 2400 9) *MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf* (Note 1) +- 2401 10) *MAP\_RESTORE\_DATA\_rsp/cnf* (Note 1) + +2402 + +2403 NOTE 1: Services printed in *italics* are optional. + +2404 + +2405 **Figure 21.2/3: Message flow for retrieval of routing information for a gsmSCF initiated call** + +2406 The following MAP services are used to retrieve routing information: + +- 2407 MAP\_SEND\_ROUTING\_INFORMATION see clause 10.1; +- 2408 MAP\_PROVIDE\_ROAMING\_NUMBER see clause 10.2; +- 2409 MAP\_PROVIDE\_SUBSCRIBER\_INFO see clause 8.11.2; +- 2410 MAP\_RESTORE\_DATA see clause 8.10.3. + +![Sequence diagram for Mobile Terminating Roaming Forwarding. Lifelines: GMSC, old MSC/VLR, new MSC/VLR, HLR. The sequence of messages is: 1) I_IAM from GMSC to old MSC/VLR; 2) MAP_CANCEL_LOCATION_req/ind from old MSC/VLR to HLR; 3) MAP_PROVIDE_ROAMING_NUMBER_req/ind from HLR to new MSC/VLR; 4) MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf from new MSC/VLR to old MSC/VLR; 5) I_IAM from old MSC/VLR to new MSC/VLR.](c51726be9e547fe7702158a6a10a88a8_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant oldMSC as old MSC/VLR + participant HLR + participant newMSC as new MSC/VLR + Note right of oldMSC: 1 + GMSC->>oldMSC: I_IAM + Note right of oldMSC: 2 + oldMSC->>HLR: MAP_CANCEL_LOCATION_req/ind + Note right of newMSC: 3 + HLR->>newMSC: MAP_PROVIDE_ROAMING_NUMBER_req/ind + Note right of oldMSC: 4 + newMSC->>oldMSC: MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf + Note right of newMSC: 5 + oldMSC->>newMSC: I_IAM + +``` + +Sequence diagram for Mobile Terminating Roaming Forwarding. Lifelines: GMSC, old MSC/VLR, new MSC/VLR, HLR. The sequence of messages is: 1) I\_IAM from GMSC to old MSC/VLR; 2) MAP\_CANCEL\_LOCATION\_req/ind from old MSC/VLR to HLR; 3) MAP\_PROVIDE\_ROAMING\_NUMBER\_req/ind from HLR to new MSC/VLR; 4) MAP\_PROVIDE\_ROAMING\_NUMBER\_rsp/cnf from new MSC/VLR to old MSC/VLR; 5) I\_IAM from old MSC/VLR to new MSC/VLR. + +2411 + +2412 + +- 2413 1) I\_IAM +- 2414 2) MAP\_CANCEL\_LOCATION\_req/ind +- 2415 3) MAP\_PROVIDE\_ROAMING\_NUMBER\_req/ind +- 2416 4) MAP\_PROVIDE\_ROAMING\_NUMBER\_rsp/cnf +- 2417 5) I\_IAM + +2418 + +2419 + +**Figure 21.2/4: Message flow for Mobile Terminating Roaming Forwarding** + +2420 The following MAP services are used for the Mobile Terminating Roaming Forwarding procedure: + +2421 MAP\_PROVIDE\_ROAMING\_NUMBER see clause 10.2; + +2422 + +## 2423 21.2.2 Procedure in the GMSC + +2424 The MAP process in the GMSC to retrieve routeing information for a mobile terminating call is shown in figure 21.2/6. + +2425 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +2426 Receive\_Open\_Cnf see clause 25.1.2; + +2427 Check\_Confirmation see clause 25.2.2. + +2428 Sheet 1: if the MAP\_SEND\_ROUTING\_INFORMATION request included the OR Interrogation parameter, the test + +2429 "OR interrogation?" takes the "Yes" exit; otherwise the test takes the "No" exit. + +## 2430 21.2.9 Process in the gsmSCF + +2431 For the purposes of retrieving routeing information from the HLR, the gsmSCF takes the role of the GMSC and follows + +2432 the process specified in clause 21.2.2. + +## 2433 21.2.4 Procedure in the HLR + +2434 The MAP process in the HLR to retrieve routeing information for a mobile terminating call is shown in figure 21.2/7. + +2435 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +2436 Receive\_Open\_Ind see clause 25.1.1; + +2437 Receive\_Open\_Cnf see clause 25.1.2; + +2438     Check\_Confirmation               see clause 25.2.2. + +2439 Sheet 3: if the MAP\_PROVIDE\_ROAMING\_NUMBER request included the OR Interrogation parameter, the test "OR +2440 interrogation?" takes the "Yes" exit; otherwise the test takes the "No" exit. + +## 2441 **21.2.5   Procedure in the VLR to provide a roaming number** + +2442 The MAP process in the VLR to provide a roaming number for a mobile terminating call is shown in figure 21.2/8. The +2443 MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +2444     Receive\_Open\_Ind   see clause 25.1.1; + +## 2445 **21.2.6   Procedure in the VLR to restore subscriber data** + +2446 The MAP process in the HLR to restore subscriber data is shown in figure 21.2/9. The MAP process invokes macros +2447 not defined in this clause; the definitions of these macros can be found as follows: + +2448     Receive\_Open\_Cnf see clause 25.1.2; + +2449     Check\_Confirmationsee clause 25.2.2; + +2450     Insert\_Subs\_Data\_VLR see clause 25.7.1; + +2451     Activate\_Tracing\_VLR see clause 25.9.4. + +## 2452 **21.2.7   Procedure in the VLR to provide subscriber information** + +2453 The MAP process in the VLR to provide subscriber information for a mobile terminating call subject to CAMEL +2454 invocation is shown in figure 21.2/9. The MAP process invokes a macro not defined in this clause; the definition of this +2455 macro can be found as follows: + +2456     Receive\_Open\_Ind   see clause 25.1.1; + +## 2457 **21.2.8   Procedure in the old VLR to request a Roaming Number (MTRF)** + +2458 The MAP process in the old VLR for Mobile Terminating Roaming Forwarding is shown in figure 21.2/11. The MAP +2459 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +2460     Receive\_Open\_Cnf see clause 25.1.2 + +2461     Check\_Confirmationsee clause 25.2.2 + +![Flowchart for process SRI_GMSC. It starts at an initial state, goes to Idle, then Send Routeing Info. A message box lists MAP_OPEN_req, MAP_SEND_ROUTING_INFORMATION_req, and MAP_DELIMITER_req. It then goes to Receive_Open_Cnf. From there, three paths emerge: OK leads to Wait_For_HLR_Response; Vr leads to a decision 'OR interrogation?'; Error leads to Abort. The 'OR interrogation?' decision has Yes and No branches. Yes leads to Set negative response: OR not allowed, then Send Routeing Info negative response, then Idle. No leads to Perform MAP Vr dialogue, then Idle. Wait_For_HLR_Response leads to a message box with MAP_SEND_ROUTING_INFORMATION_cnf, then Check Confirmation. Check Confirmation has OK and error (Provider Error, User Error, Data Error) branches. OK leads to Send Routeing Info ack, then Idle. Error leads to Send Routeing Info negative response, then Idle.](bc70af19359c8df5ba8a1d98926b9477_img.jpg) + +**process SRI\_GMSC** **SRI\_GMSC1(2)** + +Process in the GMSC to retrieve routing information for an MT call + +Signals to/from the left are to/from the application process in the GMSC (see 3GPP TS 23.018); signals to/from the right are to/from the HLR + +``` + + graph TD + Start([ ]) --> Idle1([Idle]) + Idle1 --> SendRouteingInfo1[Send Routeing Info] + SendRouteingInfo1 --> Messages1["MAP_OPEN_req +MAP_SEND_ROUTING_INFORMATION_req +MAP_DELIMITER_req"] + Messages1 --> ReceiveOpenCnf[Receive_Open_Cnf] + ReceiveOpenCnf -- OK --> WaitForHLRResponse[Wait_For_HLR_Response] + ReceiveOpenCnf -- Vr --> ORInterrogation{OR interrogation?} + ReceiveOpenCnf -- Error --> Abort{Abort} + Abort --> Idle2([Idle]) + + ORInterrogation -- Yes --> SetNegativeResponse[Set negative response: +OR not allowed] + SetNegativeResponse --> SendRouteingInfoNeg[Send Routeing Info negative response] + SendRouteingInfoNeg --> Idle3([Idle]) + + ORInterrogation -- No --> PerformMAPVr[Perform MAP Vr dialogue] + PerformMAPVr --> Idle4([Idle]) + + WaitForHLRResponse --> Messages2["MAP_SEND_ROUTING_INFORMATION_cnf"] + Messages2 --> CheckConfirmation[Check Confirmation] + + CheckConfirmation -- OK --> SendRouteingInfoAck[Send Routeing Info ack] + SendRouteingInfoAck --> Idle5([Idle]) + + CheckConfirmation -- "Provider Error, +User Error, +Data Error" --> SendRouteingInfoNeg2[Send Routeing Info negative response] + SendRouteingInfoNeg2 --> Idle6([Idle]) + +``` + +Flowchart for process SRI\_GMSC. It starts at an initial state, goes to Idle, then Send Routeing Info. A message box lists MAP\_OPEN\_req, MAP\_SEND\_ROUTING\_INFORMATION\_req, and MAP\_DELIMITER\_req. It then goes to Receive\_Open\_Cnf. From there, three paths emerge: OK leads to Wait\_For\_HLR\_Response; Vr leads to a decision 'OR interrogation?'; Error leads to Abort. The 'OR interrogation?' decision has Yes and No branches. Yes leads to Set negative response: OR not allowed, then Send Routeing Info negative response, then Idle. No leads to Perform MAP Vr dialogue, then Idle. Wait\_For\_HLR\_Response leads to a message box with MAP\_SEND\_ROUTING\_INFORMATION\_cnf, then Check Confirmation. Check Confirmation has OK and error (Provider Error, User Error, Data Error) branches. OK leads to Send Routeing Info ack, then Idle. Error leads to Send Routeing Info negative response, then Idle. + +2462 + +2463 + +Figure 21.2/6 (sheet 1 of 2): Process SRI\_GMSC + +![State transition diagram for process SRI_GMSC. It starts at 'Wait_For_HLR_Response'. Transitions include: 1) 'Abort' to 'Idle' (left side); 2) internal transitions for 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind'; 3) 'MAP_NOTICE_ind' to 'MAP_CLOSE_req' (right side); 4) 'Set negative response: System Failure' to 'Send Routeing Info negative response' to 'Idle' (bottom).](0eae447995c0dcb49ce6b55795609787_img.jpg) + +**process SRI\_GMSC** **SRI\_GMSC2(2)** + +Process in the GMSC to retrieve routeing information for an MT call + +Signals to/from the left are to/from the application process in the GMSC (see 3GPP TS 23.018); signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Wait_For_HLR_Response + state "Abort" as Abort + state "Idle" as Idle + state "Set negative response: System Failure" as Set_Negative_Response + state "Send Routeing Info negative response" as Send_Negative_Response + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + + Abort --> Idle + Wait_For_HLR_Response --> Abort + Wait_For_HLR_Response --> Set_Negative_Response + Wait_For_HLR_Response --> MAP_NOTICE_ind + Set_Negative_Response --> Send_Negative_Response + Send_Negative_Response --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Set_Negative_Response + +``` + +MAP\_U\_ABORT\_ind, + MAP\_P\_ABORT\_ind, + MAP\_CLOSE\_ind + +State transition diagram for process SRI\_GMSC. It starts at 'Wait\_For\_HLR\_Response'. Transitions include: 1) 'Abort' to 'Idle' (left side); 2) internal transitions for 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind'; 3) 'MAP\_NOTICE\_ind' to 'MAP\_CLOSE\_req' (right side); 4) 'Set negative response: System Failure' to 'Send Routeing Info negative response' to 'Idle' (bottom). + +2464 + +2465 + +**Figure 21.2/6 (sheet 2 of 2): Process SRI\_GMSC** + +![State transition diagram for process SRI_HLR. It starts at Idle, receives an Open_Ind, and branches based on OK, Error, or Vr signals. The main path involves waiting for service indication, sending routing information, and handling responses from the call handling application process.](6a6350d02cfabf076cabe037aba19f9a_img.jpg) + +**process SRI\_HLR** **SRI\_HLR1(3)** + +Process in the HLR to handle a request for routing information for an MT call + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR unless marked otherwise + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_Ind + Receive_Open_Ind --> Idle : Error + Receive_Open_Ind --> Perform_MAP_Vr_dialogue : Vr + Perform_MAP_Vr_dialogue --> Idle + Receive_Open_Ind --> Wait_For_Service_Indication : OK + Wait_For_Service_Indication --> MAP_P_ABORT_ind + Wait_For_Service_Indication --> MAP_SEND_ROUTING_INFORMATION_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + MAP_P_ABORT_ind --> Idle + MAP_SEND_ROUTING_INFORMATION_ind --> Send_Routing_Info + Send_Routing_Info --> To_HLR_call_handling_application_process + Send_Routing_Info --> Wait_For_Call_Handling_Response + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + Wait_For_Call_Handling_Response --> Send_Routing_Info_ack + Wait_For_Call_Handling_Response --> Send_Routing_Info_negative_response + Send_Routing_Info_ack --> From_HLR_call_handling_application_process + Send_Routing_Info_ack --> Set_result + Send_Routing_Info_negative_response --> From_HLR_call_handling_application_process + Send_Routing_Info_negative_response --> Set_error + Set_result --> MAP_SEND_ROUTING_INFORMATION_rsp + Set_error --> MAP_SEND_ROUTING_INFORMATION_rsp + MAP_SEND_ROUTING_INFORMATION_rsp --> MAP_CLOSE_req + MAP_SEND_ROUTING_INFORMATION_rsp --> Idle + +``` + +State transition diagram for process SRI\_HLR. It starts at Idle, receives an Open\_Ind, and branches based on OK, Error, or Vr signals. The main path involves waiting for service indication, sending routing information, and handling responses from the call handling application process. + +2466 + +2467 + +Figure 21.2/7 (sheet 1 of 3): Process SRI\_HLR + +![State transition diagram for process SRI_HLR. The diagram shows various states (Wait_For_Call_Handling_Response, Receive_Open_Cnf, Wait_For_PSI_Response, Check_Confirmation) and transitions (Provide Subscriber Info, MAP_PROVIDE_SUBSCRIBER_INFO_req, MAP_U_ABORT_ind, etc.) with associated logic and external process interactions.](6ffd01f84f590b96da66e2713c6df286_img.jpg) + +**process SRI\_HLR** **SRI\_HLR2(3)** + +Process in the HLR to handle a request for routing information for an MT call + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR unless marked otherwise + +``` + +stateDiagram-v2 + [*] --> Wait_For_Call_Handling_Response + state "Wait_For_Call_Handling_Response" as Wait_For_Call_Handling_Response + state "Receive_Open_Cnf" as Receive_Open_Cnf + state "Wait_For_PSI_Response" as Wait_For_PSI_Response + state "Check_Confirmation" as Check_Confirmation + state "Set negative response: System failure" as Set_negative_response_System_failure + state "Set negative response: System Failure" as Set_negative_response_System_Failure + + Wait_For_Call_Handling_Response --> Provide_Subscriber_Info + Provide_Subscriber_Info --> Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_PSI_Response : OK + Receive_Open_Cnf --> Set_negative_response_System_failure : Vr, Error + Set_negative_response_System_failure --> Provide_Subscriber_Info_negative_response + Provide_Subscriber_Info_negative_response --> To_HLR_call_handling_application_process + Provide_Subscriber_Info_negative_response --> Wait_For_Call_Handling_Response + + Wait_For_PSI_Response --> MAP_PROVIDE_SUBSCRIBER_INFO_cnf + Wait_For_PSI_Response --> MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind + Wait_For_PSI_Response --> MAP_NOTICE_ind + Wait_For_PSI_Response --> MAP_CLOSE_req + + MAP_PROVIDE_SUBSCRIBER_INFO_cnf --> Check_Confirmation + Check_Confirmation --> Provide_Subscriber_Info_ack : OK + Check_Confirmation --> Provide_Subscriber_Info_negative_response : Provider Error, User Error, Data Error + Provide_Subscriber_Info_ack --> To_HLR_call_handling_application_process + Provide_Subscriber_Info_ack --> Wait_For_Call_Handling_Response + Provide_Subscriber_Info_negative_response --> To_HLR_call_handling_application_process + Provide_Subscriber_Info_negative_response --> Wait_For_Call_Handling_Response + + MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind --> Set_negative_response_System_Failure + Set_negative_response_System_Failure --> Provide_Subscriber_Info_negative_response + Provide_Subscriber_Info_negative_response --> To_HLR_call_handling_application_process + Provide_Subscriber_Info_negative_response --> Wait_For_Call_Handling_Response + + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Set_negative_response_System_Failure + Set_negative_response_System_Failure --> Provide_Subscriber_Info_negative_response + Provide_Subscriber_Info_negative_response --> To_HLR_call_handling_application_process + Provide_Subscriber_Info_negative_response --> Wait_For_Call_Handling_Response + +``` + +State transition diagram for process SRI\_HLR. The diagram shows various states (Wait\_For\_Call\_Handling\_Response, Receive\_Open\_Cnf, Wait\_For\_PSI\_Response, Check\_Confirmation) and transitions (Provide Subscriber Info, MAP\_PROVIDE\_SUBSCRIBER\_INFO\_req, MAP\_U\_ABORT\_ind, etc.) with associated logic and external process interactions. + +2468 + +2469 + +Figure 21.2/7 (sheet 2 of 3): Process SRI\_HLR + +![Flowchart for process SRI_HLR. The process starts with 'Wait_For_Call_Handling_Response', followed by 'Provide Roaming Number' (to HLR call handling application process). It then enters a loop: 'MAP_OPEN_req / MAP_PROVIDE_ROAMING_NUMBER_req / MAP_DELIMITER_req' -> 'Receive_Open_Cnf'. From 'Receive_Open_Cnf', three paths emerge: 'Error' -> 'Set negative response: System failure' -> 'Provide Roaming Number negative response' (to HLR call handling application process) -> 'Wait_For_Call_Handling_Response'; 'OK' -> 'Wait_For_PRN_Response'; 'Vr' -> 'OR interrogation?'. If 'Yes', it goes to 'Set negative response: OR not allowed' -> 'Provide Roaming Number negative response' (to HLR call handling application process) -> 'Wait_For_Call_Handling_Response'. If 'No', it goes to 'Perform MAP Vr dialogue' -> 'MAP Vr dialogue result' (to HLR call handling application process) -> 'Wait_For_Call_Handling_Response'. Below 'Wait_For_PRN_Response', there are three parallel inputs: 'MAP_PROVIDE_ROAMING_NUMBER_cnf' -> 'Check_Confirmation' -> 'OK' (to 'Provide Roaming Number ack' -> to HLR call handling application process) or 'Provider Error, User Error, Data Error' (to 'Provide Roaming Number negative response' -> to HLR call handling application process); a group of 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' -> 'Set negative response: System Failure' -> 'Provide Roaming Number negative response' (to HLR call handling application process); and 'MAP_NOTICE_ind' -> 'MAP_CLOSE_req'. All three paths lead to 'Wait_For_Call_Handling_Response'.](b926b978b58fbca2dc80f670f4b52736_img.jpg) + +**process SRI\_HLR** **SRI\_HLR3(3)** + +Process in the HLR to handle a request for routing information for an MT call + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR unless marked otherwise + +``` + +graph TD + Start([Wait_For_Call_Handling_Response]) --> ProvideRN[Provide Roaming Number] + ProvideRN -.-> ToHLR1[To HLR call handling application process] + ProvideRN --> MAP_OPEN{MAP_OPEN_req +MAP_PROVIDE_ROAMING_NUMBER_req +MAP_DELIMITER_req} + MAP_OPEN --> ReceiveOCnf[Receive_Open_Cnf] + ReceiveOCnf -- Error --> SetNegSys[Set negative response: +System failure] + SetNegSys --> ProvideRNNeg[Provide Roaming Number negative response] + ProvideRNNeg -.-> ToHLR2[To HLR call handling application process] + ProvideRNNeg --> WaitFCH2([Wait_For_Call_Handling_Response]) + ReceiveOCnf -- OK --> WaitFPRN[Wait_For_PRN_Response] + ReceiveOCnf -- Vr --> ORInt{OR interrogation?} + ORInt -- Yes --> SetNegOR[Set negative response: +OR not allowed] + SetNegOR --> ProvideRNNeg2[Provide Roaming Number negative response] + ProvideRNNeg2 -.-> ToHLR3[To HLR call handling application process] + ProvideRNNeg2 --> WaitFCH3([Wait_For_Call_Handling_Response]) + ORInt -- No --> PerformVr[Perform MAP Vr dialogue] + PerformVr --> MAPVrResult{MAP Vr dialogue result} + MAPVrResult -.-> ToHLR4[To HLR call handling application process] + MAPVrResult --> WaitFCH4([Wait_For_Call_Handling_Response]) + WaitFPRN --> MAP_PROVIDE_ROAMING_NUMBER_cnf{MAP_PROVIDE_ROAMING_NUMBER_cnf} + MAP_PROVIDE_ROAMING_NUMBER_cnf --> CheckConf[Check_Confirmation] + CheckConf -- OK --> ProvideRNack[Provide Roaming Number ack] + ProvideRNack -.-> ToHLR5[To HLR call handling application process] + CheckConf -- "Provider Error, +User Error, +Data Error" --> ProvideRNNeg3[Provide Roaming Number negative response] + ProvideRNNeg3 -.-> ToHLR6[To HLR call handling application process] + ProvideRNNeg3 --> WaitFCH5([Wait_For_Call_Handling_Response]) + MAP_U_ABORT_ind[MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind] --> SetNegSysFail[Set negative response: +System Failure] + SetNegSysFail --> ProvideRNNeg4[Provide Roaming Number negative response] + ProvideRNNeg4 -.-> ToHLR7[To HLR call handling application process] + ProvideRNNeg4 --> WaitFCH5 + MAP_NOTICE_ind[MAP_NOTICE_ind] --> MAP_CLOSE_req{MAP_CLOSE_req} + MAP_CLOSE_req --> WaitFCH5 + +``` + +Flowchart for process SRI\_HLR. The process starts with 'Wait\_For\_Call\_Handling\_Response', followed by 'Provide Roaming Number' (to HLR call handling application process). It then enters a loop: 'MAP\_OPEN\_req / MAP\_PROVIDE\_ROAMING\_NUMBER\_req / MAP\_DELIMITER\_req' -> 'Receive\_Open\_Cnf'. From 'Receive\_Open\_Cnf', three paths emerge: 'Error' -> 'Set negative response: System failure' -> 'Provide Roaming Number negative response' (to HLR call handling application process) -> 'Wait\_For\_Call\_Handling\_Response'; 'OK' -> 'Wait\_For\_PRN\_Response'; 'Vr' -> 'OR interrogation?'. If 'Yes', it goes to 'Set negative response: OR not allowed' -> 'Provide Roaming Number negative response' (to HLR call handling application process) -> 'Wait\_For\_Call\_Handling\_Response'. If 'No', it goes to 'Perform MAP Vr dialogue' -> 'MAP Vr dialogue result' (to HLR call handling application process) -> 'Wait\_For\_Call\_Handling\_Response'. Below 'Wait\_For\_PRN\_Response', there are three parallel inputs: 'MAP\_PROVIDE\_ROAMING\_NUMBER\_cnf' -> 'Check\_Confirmation' -> 'OK' (to 'Provide Roaming Number ack' -> to HLR call handling application process) or 'Provider Error, User Error, Data Error' (to 'Provide Roaming Number negative response' -> to HLR call handling application process); a group of 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' -> 'Set negative response: System Failure' -> 'Provide Roaming Number negative response' (to HLR call handling application process); and 'MAP\_NOTICE\_ind' -> 'MAP\_CLOSE\_req'. All three paths lead to 'Wait\_For\_Call\_Handling\_Response'. + +2470 + +2471 + +Figure 21.2/7 (sheet 3 of 3): Process SRI\_HLR + +![State transition diagram for process PRN_VLR. It starts at an initial state, goes to Idle, then receives an Open_Ind. From there, it branches based on the response: OK leads to Wait_For_Service_Indication, which then leads to a decision point for MAP_P_ABORT_ind, MAP_PROVIDE_ROAMING_NUMBER_ind, or MAP_NOTICE_ind. MAP_P_ABORT_ind leads to Idle. MAP_PROVIDE_ROAMING_NUMBER_ind leads to Provide Roaming Number, then Wait_For_Roaming_Number, then a decision point for Provide Roaming Number ack or negative response, leading to Set result or Set error, then a response state, and finally Idle. MAP_NOTICE_ind leads to MAP_CLOSE_req, then Idle. A 'Vr' signal from the left leads to Perform MAP Vr dialogue, then Idle. An 'Error' signal from the right leads to Idle.](5663991a761141b2ebb40327ca5231de_img.jpg) + +**process PRN\_VLR** **PRN\_VLR1(1)** + +Process in the VLR to handle a request for a roaming number + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the application process in the VLR (see 3GPP TS 23.018) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_Ind + Receive_Open_Ind --> Idle : Error + Receive_Open_Ind --> Wait_For_Service_Indication : OK + Receive_Open_Ind --> Perform_MAP_Vr_dialogue : Vr + Perform_MAP_Vr_dialogue --> Idle + Wait_For_Service_Indication --> MAP_P_ABORT_ind + Wait_For_Service_Indication --> MAP_PROVIDE_ROAMING_NUMBER_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + MAP_P_ABORT_ind --> Idle + MAP_PROVIDE_ROAMING_NUMBER_ind --> Provide_Roaming_Number[Provide Roaming Number] + Provide_Roaming_Number --> Wait_For_Roaming_Number + Wait_For_Roaming_Number --> Provide_Roaming_Number_ack[Provide Roaming Number ack] + Wait_For_Roaming_Number --> Provide_Roaming_Number_neg_response[Provide Roaming Number negative response] + Provide_Roaming_Number_ack --> Set_result[Set result] + Provide_Roaming_Number_neg_response --> Set_error[Set error] + Set_result --> MAP_PROVIDE_ROAMING_NUMBER_rsp[MAP_PROVIDE_ROAMING_NUMBER_rsp / MAP_CLOSE_req] + Set_error --> MAP_PROVIDE_ROAMING_NUMBER_rsp + MAP_PROVIDE_ROAMING_NUMBER_rsp --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + +``` + +State transition diagram for process PRN\_VLR. It starts at an initial state, goes to Idle, then receives an Open\_Ind. From there, it branches based on the response: OK leads to Wait\_For\_Service\_Indication, which then leads to a decision point for MAP\_P\_ABORT\_ind, MAP\_PROVIDE\_ROAMING\_NUMBER\_ind, or MAP\_NOTICE\_ind. MAP\_P\_ABORT\_ind leads to Idle. MAP\_PROVIDE\_ROAMING\_NUMBER\_ind leads to Provide Roaming Number, then Wait\_For\_Roaming\_Number, then a decision point for Provide Roaming Number ack or negative response, leading to Set result or Set error, then a response state, and finally Idle. MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req, then Idle. A 'Vr' signal from the left leads to Perform MAP Vr dialogue, then Idle. An 'Error' signal from the right leads to Idle. + +2472 + +2473 + +Figure 21.2/8: Process PRN\_VLR + +![State transition diagram for process Restore_Data_VLR. The process starts at Idle, receives a Restore Data request, sends MAP_OPEN_req, MAP_RESTORE_DATA_req, and MAP_DELIMITER_req, then receives an Open_Cnf. If OK, it waits for an HLR Response. If Vr, it performs a MAP Vr dialogue and returns to Idle. If Error, it sends a Restore Data negative response and returns to Idle. Upon receiving an HLR Response, it inserts subscriber data, activates tracing, and sends a MAP_RESTORE_DATA_cnf. It then checks the confirmation. If OK, it sends a Restore Data ack and returns to Idle. If User Error, Provider Error, or Data Error, it sends a Restore Data negative response and returns to Idle. If the HLR Response contains MAP_U_ABORT_ind, MAP_P_ABORT_ind, or MAP_CLOSE_ind, it sends a MAP_NOTICE_ind and a MAP_CLOSE_req, then sends a Restore Data negative response and returns to Idle.](5f07e508bcb460244d3958773a51de14_img.jpg) + +**process Restore\_Data\_VLR** **RD\_VLR1(1)** + +Process in the VLR to request restoration of subscriber data + +Signals to/from the left are to/from the HLR; + signals to/from the right are to/from the application process in the VLR + (see 3GPP TS 23.018) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Restore_Data + Restore_Data --> Open_Req + Open_Req --> Receive_Open_Cnf + Receive_Open_Cnf --> Vr + Receive_Open_Cnf --> OK + Receive_Open_Cnf --> Error + Vr --> Perform_MAP_Vr_dialogue + Perform_MAP_Vr_dialogue --> Idle + OK --> Wait_For_HLR_Response + Error --> Restore_Data_negative_response + Restore_Data_negative_response --> Idle + Wait_For_HLR_Response --> Insert_Subsc_Data_VLR + Wait_For_HLR_Response --> Activate_Tracing_VLR + Wait_For_HLR_Response --> MAP_RESTORE_DATA_cnf + Insert_Subsc_Data_VLR --> Wait_For_HLR_Response + Activate_Tracing_VLR --> Wait_For_HLR_Response + MAP_RESTORE_DATA_cnf --> Check_Confirmation + Check_Confirmation --> OK + Check_Confirmation --> User_Error_Provider_Error_Data_Error + OK --> Restore_Data_ack + Restore_Data_ack --> Idle + User_Error_Provider_Error_Data_Error --> Restore_Data_negative_response + Restore_Data_negative_response --> Idle + Wait_For_HLR_Response --> MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind + MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind --> MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Restore_Data_negative_response + Restore_Data_negative_response --> Idle + +``` + +State transition diagram for process Restore\_Data\_VLR. The process starts at Idle, receives a Restore Data request, sends MAP\_OPEN\_req, MAP\_RESTORE\_DATA\_req, and MAP\_DELIMITER\_req, then receives an Open\_Cnf. If OK, it waits for an HLR Response. If Vr, it performs a MAP Vr dialogue and returns to Idle. If Error, it sends a Restore Data negative response and returns to Idle. Upon receiving an HLR Response, it inserts subscriber data, activates tracing, and sends a MAP\_RESTORE\_DATA\_cnf. It then checks the confirmation. If OK, it sends a Restore Data ack and returns to Idle. If User Error, Provider Error, or Data Error, it sends a Restore Data negative response and returns to Idle. If the HLR Response contains MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, or MAP\_CLOSE\_ind, it sends a MAP\_NOTICE\_ind and a MAP\_CLOSE\_req, then sends a Restore Data negative response and returns to Idle. + +2474 + +2475 + +Figure 21.2/9: Process Restore\_Data\_VLR + +![State transition diagram for process PSI_VLR. The diagram shows states (Idle, Wait_For_Service_Indication, Wait_For_Subscriber_Info) and transitions (Receive_Open_Ind, MAP_P_ABORT_ind, MAP_PROVIDE_SUBSCRIBER_INFO_ind, MAP_NOTICE_ind, MAP_CLOSE_req, Provide Subscriber Info, Provide Subscriber Info ack, Provide Subscriber Info negative response, Set result, Set error, MAP_PROVIDE_SUBSCRIBER_INFO_rsp, MAP_CLOSE_req). Transitions are labeled with 'OK' or 'Vr, Error'.](778677a2608531f07304d9a602c42c20_img.jpg) + +**process PSI\_VLR** **PSI\_VLR1(1)** + +Process in the VLR to handle a request for subscriber information + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the application process in the VLR (see 3GPP TS 23.018) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_Ind + Receive_Open_Ind --> Idle : Vr, Error + Receive_Open_Ind --> Wait_For_Service_Indication : OK + Wait_For_Service_Indication --> MAP_P_ABORT_ind + Wait_For_Service_Indication --> MAP_PROVIDE_SUBSCRIBER_INFO_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + MAP_P_ABORT_ind --> Idle + MAP_PROVIDE_SUBSCRIBER_INFO_ind --> Provide Subscriber Info + Provide Subscriber Info --> Wait_For_Subscriber_Info + Wait_For_Subscriber_Info --> Provide Subscriber Info ack + Wait_For_Subscriber_Info --> Provide Subscriber Info negative response + Provide Subscriber Info ack --> Set result + Provide Subscriber Info negative response --> Set error + Set result --> MAP_PROVIDE_SUBSCRIBER_INFO_rsp + Set error --> MAP_PROVIDE_SUBSCRIBER_INFO_rsp + MAP_PROVIDE_SUBSCRIBER_INFO_rsp --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + +``` + +State transition diagram for process PSI\_VLR. The diagram shows states (Idle, Wait\_For\_Service\_Indication, Wait\_For\_Subscriber\_Info) and transitions (Receive\_Open\_Ind, MAP\_P\_ABORT\_ind, MAP\_PROVIDE\_SUBSCRIBER\_INFO\_ind, MAP\_NOTICE\_ind, MAP\_CLOSE\_req, Provide Subscriber Info, Provide Subscriber Info ack, Provide Subscriber Info negative response, Set result, Set error, MAP\_PROVIDE\_SUBSCRIBER\_INFO\_rsp, MAP\_CLOSE\_req). Transitions are labeled with 'OK' or 'Vr, Error'. + +2476 + +2477 + +Figure 21.2/10: Process PSI\_VLR + +![A flowchart diagram titled 'Process PRN_Old_VLR' with a large black redaction box in the center. The visible parts show various process steps represented by rectangles, ovals, and arrows, connected by lines. The top part shows a sequence of three shapes (oval, chevron, rectangle) with a document icon to the left. The bottom part shows a more complex flow with multiple arrows and shapes, including a central oval at the bottom.](eb8b7df8a0c294b217f369f3ab60d0b5_img.jpg) + +A flowchart diagram titled 'Process PRN\_Old\_VLR' with a large black redaction box in the center. The visible parts show various process steps represented by rectangles, ovals, and arrows, connected by lines. The top part shows a sequence of three shapes (oval, chevron, rectangle) with a document icon to the left. The bottom part shows a more complex flow with multiple arrows and shapes, including a central oval at the bottom. + +2478 + +2479 + +**Figure 21.2/11: Process PRN\_Old\_VLR** + +## 2480 21.3 Transfer of call handling + +### 2481 21.3.1 General + +2482 The message flow for successful transfer of call handling to forward a call is shown in figure 21.3/1. + +![Sequence diagram showing the message flow for transfer of call handling between GMSC, HLR, VMSC, and Forwarded-To Local Exchange.](2aff3776e7865ab7d7e769d44ba12442_img.jpg) + +``` +sequenceDiagram + participant GMSC + participant HLR + participant VMSC + participant FLE as Forwarded-To Local Exchange + + Note left of GMSC: 1 + GMSC->>HLR: 2 + Note right of HLR: 3 + HLR->>GMSC: + Note right of VMSC: 4 + VMSC->>HLR: + Note right of VMSC: 5 + VMSC->>FLE: + Note right of FLE: 6 +``` + +The diagram is a sequence diagram with four lifelines: GMSC, HLR, VMSC, and Forwarded-To Local Exchange. The sequence of messages is as follows: 1. A message is sent from the GMSC to the HLR. 2. The HLR sends a response to the GMSC. 3. The GMSC then sends a message to the VMSC. 4. The VMSC sends a response to the HLR. 5. The HLR sends another response to the VMSC. 6. Finally, the VMSC sends a message to the Forwarded-To Local Exchange. + +Sequence diagram showing the message flow for transfer of call handling between GMSC, HLR, VMSC, and Forwarded-To Local Exchange. + +2483 + +2484 + +- 2485 1) *MAP\_RESUME\_CALL\_HANDLING\_req/ind* +- 2486 2) *MAP\_SEND\_ROUTING\_INFORMATION\_req/ind* (Note 2) +- 2487 3) *MAP\_SEND\_ROUTING\_INFORMATION\_rsp/cnf* (Note 2) +- 2488 4) *MAP\_RESUME\_CALL\_HANDLING\_rsp/cnf* +- 2489 5) I\_REL (Note 1) +- 2490 6) I\_IAM (Note 1) + +2491 + +2492 NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the +2493 MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations +2494 & ETSI specification: +2495 - Q.721-725 - Telephone User Part (TUP); +2496 - ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part +2497 (ISUP) version 2 for the international interface; Part 1: Basic services. + +2498 + +NOTE 2: Services printed in *italics* are optional. + +2499 + +2500 + +**Figure 21.3/1: Message flow for transfer of call handling** + +2501 If the HLR indicated in the response to the original request for routeing information that forwarding interrogation is +2502 required, the GMSC executes the Send Routeing Information procedure with the HLR to obtain forwarding +2503 information; otherwise the GMSC uses the forwarding data which were sent in the +2504 *MAP\_RESUME\_CALL\_HANDLING\_req/ind*. + +### 2505 21.3.2 Process in the VMSC + +2506 The MAP process in the VMSC to retrieve routeing information for a mobile terminating call is shown in figure 21.3/2. +2507 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +2508 *Receive\_Open\_Cnf* see clause 25.1.2; + +2509 *Check\_Confirmation* see clause 25.2.2. + +2510 If the capacity of a message signal unit in the lower layers of the protocol is enough to carry all the information which +2511 has to be sent to the GMSC, the test "Segmentation needed?" takes the "No" exit; otherwise the test takes the "Yes" exit. + +### 2512 21.3.3 Process in the GMSC + +2513 The MAP process in the GMSC to handle a request for the GMSC to resume call handling is shown in figure 21.3/3. + +2514 The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +2515       Receive\_Open\_Ind see clause 25.1.1; + +2516 If the parameter All Information Sent was present in the MAP\_RESUME\_CALL\_HANDLING indication, the test "All + +2517 Information Sent" takes the "Yes" exit; otherwise the test takes the "No" exit. + +![State transition diagram for process RCH_VMSC. It starts at 'Idle', goes to 'Resume Call Handling', then checks 'Segmentation needed?'. If 'Yes', it goes to connector '1'. If 'No', it sets 'All Information Sent' and sends 'MAP_RESUME_CALL_HANDLING_req' and 'MAP_DELIMITER_req' to the left. It then enters 'Wait_For_GMSC_Response'. From there, it can receive 'MAP_RESUME_CALL_HANDLING_cnf' (leading to 'Check_Confirmation'), 'MAP_NOTICE_ind', or 'MAP_P_ABORT_ind'/'MAP_CLOSE_ind'. 'Check_Confirmation' leads to 'All information sent?' decision. If 'Yes', it goes to connector '1'. If 'No', it sends 'Resume Call Handling ack' to the right and returns to 'Idle'. 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req'. 'MAP_P_ABORT_ind'/'MAP_CLOSE_ind' leads to 'Idle'. 'MAP_CLOSE_req' leads to 'Set negative response: System failure', which sends 'Resume Call Handling negative response' to the right and returns to 'Idle'. 'Set negative response: System failure' also handles 'Provider Error, User Error, Data Error' by sending 'Resume Call Handling negative response' to the right and returning to 'Idle'. A 'Vr, Error' from 'Wait_For_GMSC_Response' leads to 'Resume Call Handling negative response' and then to 'Idle'.](570f62943c32a8ad78a7898137afd9ac_img.jpg) + +**process RCH\_VMSC** **RCH\_VMSC1(1)** + +Process in the VMSC to request the GMSC to resume call handling + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the application process in the VMSC (see 3GPP TS 23.079) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> ResumeCallHandling: Resume Call Handling + ResumeCallHandling --> SegmentationNeeded1{Segmentation needed?} + SegmentationNeeded1 --> 1: Yes + SegmentationNeeded1 --> AllInformationSent1[Set: All Information Sent] + AllInformationSent1 --> MAP_RESUME_CALL_HANDLING_req[MAP_RESUME_CALL_HANDLING_req +MAP_DELIMITER_req] + MAP_RESUME_CALL_HANDLING_req --> Wait_For_GMSC_Response1[Wait_For_GMSC_Response] + Wait_For_GMSC_Response1 --> MAP_RESUME_CALL_HANDLING_cnf[MAP_RESUME_CALL_HANDLING_cnf] + Wait_For_GMSC_Response1 --> MAP_NOTICE_ind[MAP_NOTICE_ind] + Wait_For_GMSC_Response1 --> MAP_P_ABORT_ind[MAP_P_ABORT_ind, MAP_CLOSE_ind] + Wait_For_GMSC_Response1 --> Vr_Error[Resume Call Handling negative response]: Vr, Error + MAP_P_ABORT_ind --> Idle + MAP_RESUME_CALL_HANDLING_cnf --> Check_Confirmation[Check_Confirmation] + Check_Confirmation --> AllInformationSent2{All information sent?} + AllInformationSent2 --> 1: Yes + AllInformationSent2 --> No1: No + No1 --> ResumeCallHandling_ack[Resume Call Handling ack] + ResumeCallHandling_ack --> Idle + No1 --> ResumeCallHandling_neg_resp1[Resume Call Handling negative response] + ResumeCallHandling_neg_resp1 --> Idle + No1 --> SetNegResponse[System failure] + SetNegResponse --> ResumeCallHandling_neg_resp2[Resume Call Handling negative response] + ResumeCallHandling_neg_resp2 --> Idle + SetNegResponse --> ProviderError[Provider Error, User Error, Data Error] + ProviderError --> ResumeCallHandling_neg_resp3[Resume Call Handling negative response] + ResumeCallHandling_neg_resp3 --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> SetNegResponse + +``` + +State transition diagram for process RCH\_VMSC. It starts at 'Idle', goes to 'Resume Call Handling', then checks 'Segmentation needed?'. If 'Yes', it goes to connector '1'. If 'No', it sets 'All Information Sent' and sends 'MAP\_RESUME\_CALL\_HANDLING\_req' and 'MAP\_DELIMITER\_req' to the left. It then enters 'Wait\_For\_GMSC\_Response'. From there, it can receive 'MAP\_RESUME\_CALL\_HANDLING\_cnf' (leading to 'Check\_Confirmation'), 'MAP\_NOTICE\_ind', or 'MAP\_P\_ABORT\_ind'/'MAP\_CLOSE\_ind'. 'Check\_Confirmation' leads to 'All information sent?' decision. If 'Yes', it goes to connector '1'. If 'No', it sends 'Resume Call Handling ack' to the right and returns to 'Idle'. 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req'. 'MAP\_P\_ABORT\_ind'/'MAP\_CLOSE\_ind' leads to 'Idle'. 'MAP\_CLOSE\_req' leads to 'Set negative response: System failure', which sends 'Resume Call Handling negative response' to the right and returns to 'Idle'. 'Set negative response: System failure' also handles 'Provider Error, User Error, Data Error' by sending 'Resume Call Handling negative response' to the right and returning to 'Idle'. A 'Vr, Error' from 'Wait\_For\_GMSC\_Response' leads to 'Resume Call Handling negative response' and then to 'Idle'. + +2518 + +2519 + +Figure 21.3/2: Process RCH\_VMSC + +![State transition diagram for process RCH_GMSC. The process starts at an initial state, goes to Idle, then receives an Open_ind. From Open_ind, an OK response leads to Wait_For_Service_Indication, while a Vr, Error response leads to Idle. From Wait_For_Service_Indication, three paths are possible: MAP_P_ABORT_ind leads to Idle; MAP_RESUME_CALL_HANDLING_ind leads to a decision 'All Information Sent?'; MAP_NOTICE_ind leads to MAP_CLOSE_req and then Idle. If 'All Information Sent?' is No, it goes to Store received data, then to a state that sends MAP_RESUME_CALL_HANDLING_rsp and MAP_DELIMITER_req, then to Wait_For_Service_Indication. If 'All Information Sent?' is Yes, it goes to Assemble received data, then to Resume Call Handling, then to Wait_For_Call_Handling_Response. From Wait_For_Call_Handling_Response, two paths are possible: Resume Call Handling ack leads to Set Result; Resume Call Handling negative response leads to Set Error. Both Set Result and Set Error lead to a state that sends MAP_RESUME_CALL_HANDLING_rsp and MAP_CLOSE_req, then to Idle.](d0b7cc026701eaf4a8334cdaebd0bd6f_img.jpg) + +**process RCH\_GMSC** **RCH\_GMSC1(1)** + +Process in the GMSC to handle a request to resume call handling + +Signals to/from the left are to/from the application process in the GMSC (see 3GPP TS 23.079); signals to/from the right are to/from the VMSC; + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_ind + Receive_Open_ind --> Wait_For_Service_Indication: OK + Receive_Open_ind --> Idle: Vr, Error + Wait_For_Service_Indication --> Idle: MAP_P_ABORT_ind + Wait_For_Service_Indication --> All_Information_Sent: MAP_RESUME_CALL_HANDLING_ind + Wait_For_Service_Indication --> Idle: MAP_NOTICE_ind + All_Information_Sent --> Idle: MAP_CLOSE_req + All_Information_Sent --> Assemble_received_data: Yes + All_Information_Sent --> Store_received_data: No + Assemble_received_data --> Resume_Call_Handling + Store_received_data --> MAP_DELIMITER_req_state: MAP_RESUME_CALL_HANDLING_rsp + MAP_DELIMITER_req_state --> Wait_For_Service_Indication + Resume_Call_Handling --> Wait_For_Call_Handling_Response + Wait_For_Call_Handling_Response --> Set_Result: Resume Call Handling ack + Wait_For_Call_Handling_Response --> Set_Error: Resume Call Handling negative response + Set_Result --> MAP_CLOSE_req_state: MAP_RESUME_CALL_HANDLING_rsp + Set_Error --> MAP_CLOSE_req_state: MAP_CLOSE_req + MAP_CLOSE_req_state --> Idle + +``` + +State transition diagram for process RCH\_GMSC. The process starts at an initial state, goes to Idle, then receives an Open\_ind. From Open\_ind, an OK response leads to Wait\_For\_Service\_Indication, while a Vr, Error response leads to Idle. From Wait\_For\_Service\_Indication, three paths are possible: MAP\_P\_ABORT\_ind leads to Idle; MAP\_RESUME\_CALL\_HANDLING\_ind leads to a decision 'All Information Sent?'; MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req and then Idle. If 'All Information Sent?' is No, it goes to Store received data, then to a state that sends MAP\_RESUME\_CALL\_HANDLING\_rsp and MAP\_DELIMITER\_req, then to Wait\_For\_Service\_Indication. If 'All Information Sent?' is Yes, it goes to Assemble received data, then to Resume Call Handling, then to Wait\_For\_Call\_Handling\_Response. From Wait\_For\_Call\_Handling\_Response, two paths are possible: Resume Call Handling ack leads to Set Result; Resume Call Handling negative response leads to Set Error. Both Set Result and Set Error lead to a state that sends MAP\_RESUME\_CALL\_HANDLING\_rsp and MAP\_CLOSE\_req, then to Idle. + +2520 + +2521 + +Figure 21.3/3: Process RCH\_GMSC + +2522 **21.4 Inter MSC Group Call Procedures** + +2523 **21.4.1 General** + +2524 The message flow for successful inter MSC group call / broadcast call set-up is shown in figure 21.4/1. + +![Sequence diagram showing message flow between PSTN/ISDN, Anchor MSC, and Relay MSC. The diagram consists of three vertical lifelines. 1) PSTN/ISDN sends message 1 to Anchor MSC. 2) Anchor MSC sends message 2 to Relay MSC. 3) Relay MSC sends message 3 back to Anchor MSC. 4) Anchor MSC sends message 4 to Relay MSC. 5) Relay MSC sends message 5 back to Anchor MSC. 6) Anchor MSC sends message 6 to Relay MSC. 7) Anchor MSC sends message 7 to PSTN/ISDN. 8) Anchor MSC sends message 8 to Relay MSC. 9) Relay MSC sends message 9 back to Anchor MSC. 10) Anchor MSC sends message 10 to Relay MSC. 11) PSTN/ISDN sends message 11 to Anchor MSC. 12) Anchor MSC sends message 12 to Relay MSC.](7b54229ed3e78df624c177e8e582701c_img.jpg) + +Sequence diagram showing message flow between PSTN/ISDN, Anchor MSC, and Relay MSC. The diagram consists of three vertical lifelines. 1) PSTN/ISDN sends message 1 to Anchor MSC. 2) Anchor MSC sends message 2 to Relay MSC. 3) Relay MSC sends message 3 back to Anchor MSC. 4) Anchor MSC sends message 4 to Relay MSC. 5) Relay MSC sends message 5 back to Anchor MSC. 6) Anchor MSC sends message 6 to Relay MSC. 7) Anchor MSC sends message 7 to PSTN/ISDN. 8) Anchor MSC sends message 8 to Relay MSC. 9) Relay MSC sends message 9 back to Anchor MSC. 10) Anchor MSC sends message 10 to Relay MSC. 11) PSTN/ISDN sends message 11 to Anchor MSC. 12) Anchor MSC sends message 12 to Relay MSC. + +2525 + +2526 + +- 2527 1) I\_IAM (Note 1) +- 2528 2) MAP\_PREPARE\_GROUP\_CALL\_req/ind +- 2529 3) MAP\_PREPARE\_GROUP\_CALL\_rsp/cnf +- 2530 4) I\_IAM (Note 1) +- 2531 5) MAP\_SEND\_GROUP\_CALL\_END\_SIGNAL\_req/ind +- 2532 6) I\_ACM (Note 1) +- 2533 7) I\_ACM (Note 1) +- 2534 8) MAP\_FORWARD\_GROUP\_CALL\_SIGNALLING\_req/ind (Note 2) +- 2535 9) MAP\_PROCESS\_GROUP\_CALL\_SIGNALLING\_req/ind (Note 2) +- 2536 10) MAP\_SEND\_GROUP\_CALL\_END\_SIGNAL\_rsp/cnf +- 2537 11) I\_REL (Note 3) +- 2538 12) I\_REL (Note 3) + +2539 + +2540 NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the + 2541 MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations + 2542 and ETSI specification: + +- 2543 - Q.721-725 - Telephone User Part (TUP); +- 2544 - ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part + 2545 (ISUP) version 2 for the international interface; Part 1: Basic services. + +2546 NOTE 2: The MAP\_FORWARD\_GROUP\_CALL\_SIGNALLING and + 2547 MAP\_PROCESS\_GROUP\_CALL\_SIGNALLING services are not applicable for voice broadcast calls. + +2548 NOTE 3: The call can be released from the PSTN/ISDN or the Relay MSC + +2549 + +2550 + +**Figure 21.4/1: Message flow for inter MSC group call / broadcast call** + +2551 **21.4.2 Process in the Anchor MSC** + +2552 The MAP process in the Anchor MSC to retrieve and transfer information from / to the Relay MSC for VBS and VGCS +2553 calls is shown in figure 21.4/2. The MAP process invokes macros not defined in this clause; the definitions of these +2554 macros can be found as follows: + +2555       Receive\_Open\_Cnf see clause 25.1.2; + +2556       Check\_Indication see clause 25.2.1; + +2557       Check\_Confirmation see clause 25.2.2. + +### 2558 21.4.3 Process in the Relay MSC + +2559 The MAP process in the Relay MSC to receive and transfer information from / to the Anchor MSC for VBS and VGCS +2560 calls is shown in figure 21.4/3. The MAP process invokes macros not defined in this clause; the definitions of these +2561 macros can be found as follows: + +2562       Receive\_Open\_Ind see clause 25.1.2; + +2563       Check\_Indication see clause 25.2.1. + +![Sequence diagram for process ASCI_Ancestor_MSC. The diagram shows the internal state transitions and message exchanges within the Anchor MSC. It starts at an initial state, goes to Idle, then Prepare Group Call. From there, it sends MAP_OPEN_req, MAP_PREPARE_GROUP_CALL_req, and MAP_DELIMITER_req. It then enters a Receive_Open_Cnf state. If OK, it goes to Wait_For_Group_Call_Number, receives MAP_PREPARE_GROUP_CALL_cnf, and enters a Check_Confirmation state. From Check_Confirmation, if OK, it goes to Prepare Group Call ack, then Wait_For_Call_Completion, and finally Idle. If Provider Error or User Error/Data Error, it goes to Prepare Group Call negative response, then sends MAP_U_ABORT_req and returns to Idle. If Vr, Error occurs in Receive_Open_Cnf, it goes to Abort and returns to Idle. A second path starts from an initial state (*), goes to MAP_NOTICE_ind, then MAP_CLOSE_req, then Abort, and finally Idle. A message box on the right indicates that MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind are received from the Relay MSC.](7be65c99e859604f653de03aa0c095e9_img.jpg) + +**process ASCI\_Ancestor\_MSC** **AA\_MSC1(2)** + +Process in the Anchor MSC for ASCI call handling + +Signals to/from the left are to/from the ASCI call handling process in the anchor MSC; signals to/from the right are to/from the Relay MSC + +``` + +sequenceDiagram + participant Start1 as + participant Idle1 as Idle + participant PrepareGroupCall1 as Prepare Group Call + participant OpenReq["MAP_OPEN_req +MAP_PREPARE_GROUP_CALL_req +MAP_DELIMITER_req"] + participant ReceiveOpenCnf as Receive_Open_Cnf + participant Abort1 as Abort + participant Idle2 as Idle + participant WaitForGroupCallNumber as Wait_For_Group_Call_Number + participant PrepareGroupCallCnf["MAP_PREPARE_GROUP_CALL_cnf"] + participant CheckConfirmation as Check_Confirmation + participant PrepareGroupCallAck as Prepare Group Call ack + participant WaitForCallCompletion as Wait_For_Call_Completion + participant PrepareGroupCallNegResponse1 as Prepare Group Call negative response + participant MAPUAbortReq["MAP_U_ABORT_req"] + participant Idle3 as Idle + participant Start2 as * + participant MAPNoticeInd as MAP_NOTICE_ind + participant MAPCloseReq as MAP_CLOSE_req + participant Abort2 as Abort + participant Idle4 as Idle + participant MAPUAbortInd["MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind"] + + Note left of Start1: Process in the Anchor MSC for ASCI call handling + Note right of Start2: Signals to/from the left are to/from the ASCI call handling process in the anchor MSC; signals to/from the right are to/from the Relay MSC + + Start1 --> Idle1 + Idle1 --> PrepareGroupCall1 + PrepareGroupCall1 --> OpenReq + OpenReq --> ReceiveOpenCnf + ReceiveOpenCnf --> Abort1: Vr, Error + ReceiveOpenCnf --> WaitForGroupCallNumber: OK + Abort1 --> Idle2 + WaitForGroupCallNumber --> PrepareGroupCallCnf + PrepareGroupCallCnf --> CheckConfirmation + CheckConfirmation --> PrepareGroupCallAck: OK + CheckConfirmation --> PrepareGroupCallNegResponse1: Provider Error + CheckConfirmation --> PrepareGroupCallNegResponse1: User Error, Data Error + PrepareGroupCallAck --> WaitForCallCompletion + WaitForCallCompletion --> Idle3 + PrepareGroupCallNegResponse1 --> MAPUAbortReq + MAPUAbortReq --> Idle3 + + Start2 --> MAPNoticeInd + MAPNoticeInd --> MAPCloseReq + MAPCloseReq --> Abort2 + Abort2 --> Idle4 + MAPNoticeInd --> MAPUAbortInd + +``` + +Sequence diagram for process ASCI\_Ancestor\_MSC. The diagram shows the internal state transitions and message exchanges within the Anchor MSC. It starts at an initial state, goes to Idle, then Prepare Group Call. From there, it sends MAP\_OPEN\_req, MAP\_PREPARE\_GROUP\_CALL\_req, and MAP\_DELIMITER\_req. It then enters a Receive\_Open\_Cnf state. If OK, it goes to Wait\_For\_Group\_Call\_Number, receives MAP\_PREPARE\_GROUP\_CALL\_cnf, and enters a Check\_Confirmation state. From Check\_Confirmation, if OK, it goes to Prepare Group Call ack, then Wait\_For\_Call\_Completion, and finally Idle. If Provider Error or User Error/Data Error, it goes to Prepare Group Call negative response, then sends MAP\_U\_ABORT\_req and returns to Idle. If Vr, Error occurs in Receive\_Open\_Cnf, it goes to Abort and returns to Idle. A second path starts from an initial state (\*), goes to MAP\_NOTICE\_ind, then MAP\_CLOSE\_req, then Abort, and finally Idle. A message box on the right indicates that MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind are received from the Relay MSC. + +2564 + +2565 + +**Figure 21.4/2 (sheet 1 of 2): Process ASCI\_Ancestor\_MSC** + +![Sequence diagram for process ASCI_Anschor_MSC. The diagram shows the internal logic of the Anchor MSC for ASCI call handling. It starts with 'Wait_For_Call_Completion', followed by an output signal 'MAP_SEND_GROUP_CALL_END_SIGNAL_ind'. A 'Check_Indication' block follows, leading to either an 'Abort' (Error) or 'Send_Group_Call_End_Signal' (OK). The 'Send_Group_Call_End_Signal' path leads to 'Uplink_Management', which then branches into three paths: 1) 'Idle', 2) 'Forward_Group_Call_Signalling' leading to 'MAP_FORWARD_GROUP_CALL_SIGNALLING_req' and 'MAP_DELIMITER_req', then 'Uplink_Management', then 'Send_Group_Call_End_Signal_ack', then 'MAP_SEND_GROUP_CALL_END_SIGNAL_rsp' and 'MAP_CLOSE_req', ending at 'Idle'; 3) an input signal 'MAP_PROCESS_GROUP_CALL_SIGNALLING_ind' leading to 'Check_Indication', which then branches into 'Abort' (Error) leading to 'MAP_U_ABORT_req' and 'Idle', or 'Process_Group_Call_Signalling' (OK) leading to 'Uplink_Management'.](5a43b8ef2db63ac99a6fb75aa61ebeab_img.jpg) + +**process ASCI\_Anschor\_MSC** **AA\_MSC2(2)** + +Process in the Anchor MSC for ASCI call handling + +Signals to/from the left are to/from the ASCI call handling process in the anchor MSC; signals to/from the right are to/from the Relay MSC + +``` + +sequenceDiagram + participant Internal + Note left of Internal: Process in the Anchor MSC for ASCI call handling + Note right of Internal: Signals to/from the left are to/from the ASCI call handling process in the anchor MSC; signals to/from the right are to/from the Relay MSC + + Internal->>Internal: Wait_For_Call_Completion + Internal->>Relay: MAP_SEND_GROUP_CALL_END_SIGNAL_ind + Internal->>Internal: Check_Indication + alt Error: Abort + Internal->>Internal: Abort + Internal->>Relay: MAP_U_ABORT_req + Internal->>Internal: Idle + else OK: Send_Group_Call_End_Signal + Internal->>Internal: Send_Group_Call_End_Signal + Internal->>Internal: Uplink_Management + alt Idle + Internal->>Internal: Idle + else Forward_Group_Call_Signalling + Internal->>Internal: Forward_Group_Call_Signalling + Internal->>Relay: MAP_FORWARD_GROUP_CALL_SIGNALLING_req + Internal->>Relay: MAP_DELIMITER_req + Internal->>Internal: Uplink_Management + Internal->>Internal: Send_Group_Call_End_Signal_ack + Internal->>Relay: MAP_SEND_GROUP_CALL_END_SIGNAL_rsp + Internal->>Relay: MAP_CLOSE_req + Internal->>Internal: Idle + else MAP_PROCESS_GROUP_CALL_SIGNALLING_ind + Internal->>Relay: MAP_PROCESS_GROUP_CALL_SIGNALLING_ind + Internal->>Internal: Check_Indication + alt Error: Abort + Internal->>Internal: Abort + Internal->>Relay: MAP_U_ABORT_req + Internal->>Internal: Idle + else OK: Process_Group_Call_Signalling + Internal->>Internal: Process_Group_Call_Signalling + Internal->>Internal: Uplink_Management + end + end + end + +``` + +Sequence diagram for process ASCI\_Anschor\_MSC. The diagram shows the internal logic of the Anchor MSC for ASCI call handling. It starts with 'Wait\_For\_Call\_Completion', followed by an output signal 'MAP\_SEND\_GROUP\_CALL\_END\_SIGNAL\_ind'. A 'Check\_Indication' block follows, leading to either an 'Abort' (Error) or 'Send\_Group\_Call\_End\_Signal' (OK). The 'Send\_Group\_Call\_End\_Signal' path leads to 'Uplink\_Management', which then branches into three paths: 1) 'Idle', 2) 'Forward\_Group\_Call\_Signalling' leading to 'MAP\_FORWARD\_GROUP\_CALL\_SIGNALLING\_req' and 'MAP\_DELIMITER\_req', then 'Uplink\_Management', then 'Send\_Group\_Call\_End\_Signal\_ack', then 'MAP\_SEND\_GROUP\_CALL\_END\_SIGNAL\_rsp' and 'MAP\_CLOSE\_req', ending at 'Idle'; 3) an input signal 'MAP\_PROCESS\_GROUP\_CALL\_SIGNALLING\_ind' leading to 'Check\_Indication', which then branches into 'Abort' (Error) leading to 'MAP\_U\_ABORT\_req' and 'Idle', or 'Process\_Group\_Call\_Signalling' (OK) leading to 'Uplink\_Management'. + +2566 + +2567 + +**Figure 21.4/2 (sheet 2 of 2): Process ASCI\_Anschor\_MSC** + +![Sequence diagram for process ASCI_Relay_MSC. The process starts at an 'Idle' state, receives an 'Open_Ind' signal, and then branches based on the response: 'Vr, Error' leads back to 'Idle'; 'OK' leads to 'Wait_For_Service_Indication'. From there, three paths emerge: 1) 'MAP_P_ABORT_ind' leads to 'Idle'; 2) 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req' which leads to 'Idle'; 3) 'MAP_PREPARE_GROUP_CALL_ind' leads to 'Check_Indication'. 'Check_Indication' has an 'Error' path to 'MAP_U_ABORT_req' leading to 'Idle', and an 'OK' path to 'Prepare Group Call' leading to 'Wait_For_Group_Call_Number'. From 'Wait_For_Group_Call_Number', two paths emerge: 1) 'Prepare Group Call ack' leads to 'Set result' leading to a merge point for 'MAP_PREPARE_GROUP_CALL_rsp' and 'MAP_DELIMITER_req', ending at 'Wait_For_End_Signal'; 2) 'Prepare Group Call negative response' leads to 'Set error' leading to a merge point for 'MAP_PREPARE_GROUP_CALL_rsp' and 'MAP_CLOSE_req', ending at 'Idle'.](ae94cc8a2e767eb4f87c9d7cb812d6da_img.jpg) + +process ASCI\_Relay\_MSC + +AR\_MSC1(2) + +Process in the Relay MSC for ASCI call handling + +Signals to/from the left are to/from the Relay MSC; signals to/from the right are to/from the ASCI call handling process in the relay MSC + +``` + +sequenceDiagram + participant Start + participant Idle1[Idle] + participant Open_Ind[Receive Open_Ind] + participant Wait_For_Service_Indication[Wait_For_Service_Indication] + participant Vr_Error[Idle] + participant MAP_P_ABORT_ind{MAP_P_ABORT_ind} + participant MAP_NOTICE_ind{MAP_NOTICE_ind} + participant MAP_PREPARE_GROUP_CALL_ind{MAP_PREPARE_GROUP_CALL_ind} + participant MAP_CLOSE_req{MAP_CLOSE_req} + participant Check_Indication[Check_Indication] + participant MAP_U_ABORT_req{MAP_U_ABORT_req} + participant Prepare_Group_Call{Prepare Group Call} + participant Wait_For_Group_Call_Number[Wait_For_Group_Call_Number] + participant Prepare_Group_Call_ack{Prepare Group Call ack} + participant Set_result[Set result] + participant Prepare_Group_Call_negative_response{Prepare Group Call negative response} + participant Set_error[Set error] + participant Merge1{ } + participant Merge2{ } + participant MAP_DELIMITER_req[MAP_DELIMITER_req] + participant MAP_CLOSE_req2[MAP_CLOSE_req] + participant Wait_For_End_Signal[Wait_For_End_Signal] + + Start --> Idle1 + Idle1 --> Open_Ind + Open_Ind --> Vr_Error: Vr, Error + Open_Ind --> Wait_For_Service_Indication: OK + Wait_For_Service_Indication --> MAP_P_ABORT_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + Wait_For_Service_Indication --> MAP_PREPARE_GROUP_CALL_ind + MAP_P_ABORT_ind --> Idle1 + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle1 + MAP_PREPARE_GROUP_CALL_ind --> Check_Indication + Check_Indication --> MAP_U_ABORT_req: Error + MAP_U_ABORT_req --> Idle1 + Check_Indication --> Prepare_Group_Call: OK + Prepare_Group_Call --> Wait_For_Group_Call_Number + Wait_For_Group_Call_Number --> Prepare_Group_Call_ack + Wait_For_Group_Call_Number --> Prepare_Group_Call_negative_response + Prepare_Group_Call_ack --> Set_result + Set_result --> Merge1 + Merge1 --> MAP_DELIMITER_req + Merge1 --> Wait_For_End_Signal + Prepare_Group_Call_negative_response --> Set_error + Set_error --> Merge2 + Merge2 --> MAP_CLOSE_req2 + Merge2 --> MAP_PREPARE_GROUP_CALL_rsp + Merge2 --> Idle1 + +``` + +Sequence diagram for process ASCI\_Relay\_MSC. The process starts at an 'Idle' state, receives an 'Open\_Ind' signal, and then branches based on the response: 'Vr, Error' leads back to 'Idle'; 'OK' leads to 'Wait\_For\_Service\_Indication'. From there, three paths emerge: 1) 'MAP\_P\_ABORT\_ind' leads to 'Idle'; 2) 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req' which leads to 'Idle'; 3) 'MAP\_PREPARE\_GROUP\_CALL\_ind' leads to 'Check\_Indication'. 'Check\_Indication' has an 'Error' path to 'MAP\_U\_ABORT\_req' leading to 'Idle', and an 'OK' path to 'Prepare Group Call' leading to 'Wait\_For\_Group\_Call\_Number'. From 'Wait\_For\_Group\_Call\_Number', two paths emerge: 1) 'Prepare Group Call ack' leads to 'Set result' leading to a merge point for 'MAP\_PREPARE\_GROUP\_CALL\_rsp' and 'MAP\_DELIMITER\_req', ending at 'Wait\_For\_End\_Signal'; 2) 'Prepare Group Call negative response' leads to 'Set error' leading to a merge point for 'MAP\_PREPARE\_GROUP\_CALL\_rsp' and 'MAP\_CLOSE\_req', ending at 'Idle'. + +2568 + +2569 + +Figure 21.4/3 (sheet 1 of 2): Process ASCI\_Relay\_MSC + +![Sequence diagram for process ASCI_Relay_MSC. The diagram shows the interaction between the Relay MSC and the ASCI call handling process. It starts with 'Wait_For_End_Signal' and 'Send Group Call End Signal'. The main loop involves 'Uplink_Management', 'MAP_FORWARD_GROUP_CALL_SIGNALLING_ind', 'Check_Indication' (Error/OK), 'Abort' or 'Forward Group Call Signalling', 'MAP_U_ABORT_req', 'Idle', 'Wait_For_Group_Call_Number', 'MAP_NOTICE_ind', 'MAP_CLOSE_req', 'MAP_P_ABORT_ind', 'MAP_CLOSE_ind', 'MAP_SEND_GROUP_CALL_END_SIGNAL_req', 'MAP_SEND_GROUP_CALL_END_SIGNAL_cnf', 'VGCS?' decision, 'Send Group Call End Signal ack', and final 'Idle' states.](3600801fb4c34c9aa22b834d51213c2e_img.jpg) + +**process ASCI\_Relay\_MSC** **AR\_MSC2(2)** + +Process in the Relay MSC for ASCI call handling + +Signals to/from the left are to/from the Relay MSC; signals to/from the right are to/from the ASCI call handling process in the relay MSC + +``` + +sequenceDiagram + participant RelayMSC as Relay MSC + participant ASCI_Process as ASCI call handling process + Note left of RelayMSC: Process in the Relay MSC for ASCI call handling + Note right of RelayMSC: Signals to/from the left are to/from the Relay MSC; signals to/from the right are to/from the ASCI call handling process in the relay MSC + + RelayMSC->>ASCI_Process: Wait_For_End_Signal + RelayMSC->>ASCI_Process: Send Group Call End Signal + RelayMSC->>ASCI_Process: MAP_SEND_GROUP_CALL_END_SIGNAL_req + RelayMSC->>ASCI_Process: Uplink_Management + RelayMSC->>ASCI_Process: MAP_FORWARD_GROUP_CALL_SIGNALLING_ind + RelayMSC->>ASCI_Process: Check_Indication + alt Error + RelayMSC->>ASCI_Process: Abort + RelayMSC->>ASCI_Process: MAP_U_ABORT_req + RelayMSC->>ASCI_Process: Idle + else OK + RelayMSC->>ASCI_Process: Forward Group Call Signalling + RelayMSC->>ASCI_Process: Uplink_Management + RelayMSC->>ASCI_Process: Wait_For_Group_Call_Number + RelayMSC->>ASCI_Process: MAP_NOTICE_ind + RelayMSC->>ASCI_Process: MAP_CLOSE_req + RelayMSC->>ASCI_Process: MAP_P_ABORT_ind + RelayMSC->>ASCI_Process: MAP_CLOSE_ind + RelayMSC->>ASCI_Process: Abort + RelayMSC->>ASCI_Process: Idle + end + + ASCI_Process->>RelayMSC: Process Group Call Signalling + ASCI_Process->>RelayMSC: MAP_PROCESS_GROUP_CALL_SIGNALLING_req + ASCI_Process->>RelayMSC: Uplink_Management + ASCI_Process->>RelayMSC: MAP_SEND_GROUP_CALL_END_SIGNAL_cnf + Note right of ASCI_Process: VGCS? + alt Yes + ASCI_Process->>RelayMSC: Send Group Call End Signal ack + ASCI_Process->>RelayMSC: Idle + else No + ASCI_Process->>RelayMSC: Idle + end + +``` + +Sequence diagram for process ASCI\_Relay\_MSC. The diagram shows the interaction between the Relay MSC and the ASCI call handling process. It starts with 'Wait\_For\_End\_Signal' and 'Send Group Call End Signal'. The main loop involves 'Uplink\_Management', 'MAP\_FORWARD\_GROUP\_CALL\_SIGNALLING\_ind', 'Check\_Indication' (Error/OK), 'Abort' or 'Forward Group Call Signalling', 'MAP\_U\_ABORT\_req', 'Idle', 'Wait\_For\_Group\_Call\_Number', 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', 'MAP\_P\_ABORT\_ind', 'MAP\_CLOSE\_ind', 'MAP\_SEND\_GROUP\_CALL\_END\_SIGNAL\_req', 'MAP\_SEND\_GROUP\_CALL\_END\_SIGNAL\_cnf', 'VGCS?' decision, 'Send Group Call End Signal ack', and final 'Idle' states. + +2570 + +2571 + +Figure 21.4/3 (sheet 2 of 2): Process ASCI\_Relay\_MSC + +2572 **21.4A Inter MSC Group Call Info Retrieval** + +2573 **21.4A.1 General** + +2574 The message flow for successful inter MSC group call info retrieval is shown in figure 21.4A/1. + +![Sequence diagram showing message flow between two MSCs. The first MSC sends a 'MAP Send Group Call Info req/ind' message to the second MSC, and the second MSC responds with a 'MAP Send Group Call Info rsp/cnf' message.](f61004df7ea0150efe6eacf1295ac41b_img.jpg) + +``` +sequenceDiagram + participant MSC1 as MSC + participant MSC2 as MSC + Note right of MSC1: MAP Send Group Call Info req/ind + MSC1->>MSC2: + Note right of MSC2: MAP Send Group Call Info rsp/cnf + MSC2->>MSC1: +``` + +Sequence diagram showing message flow between two MSCs. The first MSC sends a 'MAP Send Group Call Info req/ind' message to the second MSC, and the second MSC responds with a 'MAP Send Group Call Info rsp/cnf' message. + +2575 + +2576 **Figure 21.4A/1: Message flow for inter MSC group call info retrieval** + +2577 **21.4A.2 Process in the MSC** + +2578 The MAP process in the MSC to retrieve and group call information is shown in figure 21.4A/2. The MAP process +2579 invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +2580     Receive\_Open\_Cnf see clause 25.1.2; + +2581     Check\_Confirmation see clause 25.2.2. + +2582     Receive\_Open\_Ind see clause 25.1.2; + +![State transition diagram for process Group_Call_Info_Retrieval_MSC. The diagram shows states (Idle, Wait_For_Distant_MSC_Response) and transitions (Send Group_Call_Info, Receive_Open_Cnf, MAP_SEND_GROUP_CALL_INFO_cnf, MAP_NOTICE_ind, MAP_CLOSE_req, Check_Confirmation, Send_Group_Call_Info_ack, Send_Group_Call_Info_negative_response). Transitions are labeled with MAP messages like MAP_OPEN_req, MAP_SEND_GROUP_CALL_INFO_req, MAP_DELIMITER_req, MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind, and error conditions like User Error, Provider Error, Data Error, Vr, Error.](3ffe1dfb268095f8b2ebcc4d58568a5a_img.jpg) + +**process Group\_Call\_Info\_Retrieval\_MSC** **GCIR\_MSC(2)** + +process in the MSC to send and receive Group Call Info Retrieval messages + +Signals to/from the left are to/from the application process in the MSC; + signals to/from the right are to/from the distant MSC + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Send_Group_Call_Info + Send_Group_Call_Info --> Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_Distant_MSC_Response + Wait_For_Distant_MSC_Response --> Idle : Vr, Error + Wait_For_Distant_MSC_Response --> MAP_SEND_GROUP_CALL_INFO_cnf : OK + Wait_For_Distant_MSC_Response --> MAP_NOTICE_ind + Wait_For_Distant_MSC_Response --> MAP_CLOSE_req + MAP_SEND_GROUP_CALL_INFO_cnf --> Check_Confirmation + Check_Confirmation --> Send_Group_Call_Info_ack : OK + Check_Confirmation --> Send_Group_Call_Info_negative_response : User Error, Provider Error, Data Error + Send_Group_Call_Info_ack --> Idle + Send_Group_Call_Info_negative_response --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Send_Group_Call_Info_negative_response + MAP_CLOSE_req --> MAP_U_ABORT_ind + MAP_CLOSE_req --> MAP_P_ABORT_ind + MAP_CLOSE_req --> MAP_CLOSE_ind + +``` + +State transition diagram for process Group\_Call\_Info\_Retrieval\_MSC. The diagram shows states (Idle, Wait\_For\_Distant\_MSC\_Response) and transitions (Send Group\_Call\_Info, Receive\_Open\_Cnf, MAP\_SEND\_GROUP\_CALL\_INFO\_cnf, MAP\_NOTICE\_ind, MAP\_CLOSE\_req, Check\_Confirmation, Send\_Group\_Call\_Info\_ack, Send\_Group\_Call\_Info\_negative\_response). Transitions are labeled with MAP messages like MAP\_OPEN\_req, MAP\_SEND\_GROUP\_CALL\_INFO\_req, MAP\_DELIMITER\_req, MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind, and error conditions like User Error, Provider Error, Data Error, Vr, Error. + +2583 + +2584 + +**Figure 21.4A/2 (sheet 1 of 2): Process Group\_Call\_Info\_Retrieval\_MSC** + +![State transition diagram for process Group_Call_Info_Retrieval_MSC. The diagram shows states (Idle, Wait_For_Service_Indication, Wait_For_Application_Response) and transitions (Receive_Open_ind, MAP_P_ABORT_ind, MAP_SEND_GROUP_CALL_INFO_ind, MAP_NOTICE_ind, MAP_CLOSE_req, MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind, Send_Group_Call_info, Send_Group_Call_info_ack, Send_Group_Call_info_negative_response, Set User Error, MAP_SEND_GROUP_CALL_INFO_rsp). Transitions are labeled with OK, Vr, Error, and MAP_CLOSE_req.](3f5a5593228cdb8d717ce04dc85d73a8_img.jpg) + +process Group\_Call\_Info\_Retrieval\_MSC GCRI\_MSC(2) + +process in the MSC to send and receive Group Call Info Retrieval messages + +Signals to/from the left are to/from the application process in the MSC; signals to/from the right are to/from the distant MSC + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_ind + Receive_Open_ind --> Wait_For_Service_Indication : OK + Receive_Open_ind --> Idle : Vr, Error + Wait_For_Service_Indication --> MAP_P_ABORT_ind + Wait_For_Service_Indication --> MAP_SEND_GROUP_CALL_INFO_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + MAP_P_ABORT_ind --> Idle + MAP_SEND_GROUP_CALL_INFO_ind --> Send_Group_Call_info + Send_Group_Call_info --> Wait_For_Application_Response + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + Wait_For_Application_Response --> MAP_U_ABORT_ind + Wait_For_Application_Response --> Send_Group_Call_info_ack + Wait_For_Application_Response --> Send_Group_Call_info_negative_response + MAP_U_ABORT_ind --> Idle + Send_Group_Call_info_ack --> MAP_SEND_GROUP_CALL_INFO_rsp + Send_Group_Call_info_ack --> Idle + Send_Group_Call_info_negative_response --> Set User Error + Set User Error --> MAP_SEND_GROUP_CALL_INFO_rsp + Set User Error --> Idle + MAP_SEND_GROUP_CALL_INFO_rsp --> Idle + +``` + +State transition diagram for process Group\_Call\_Info\_Retrieval\_MSC. The diagram shows states (Idle, Wait\_For\_Service\_Indication, Wait\_For\_Application\_Response) and transitions (Receive\_Open\_ind, MAP\_P\_ABORT\_ind, MAP\_SEND\_GROUP\_CALL\_INFO\_ind, MAP\_NOTICE\_ind, MAP\_CLOSE\_req, MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind, Send\_Group\_Call\_info, Send\_Group\_Call\_info\_ack, Send\_Group\_Call\_info\_negative\_response, Set User Error, MAP\_SEND\_GROUP\_CALL\_INFO\_rsp). Transitions are labeled with OK, Vr, Error, and MAP\_CLOSE\_req. + +2585 + +2586 + +Figure 21.4A/2 (sheet 2 of 2): Process Group\_Call\_Info\_Retrieval\_MSC + +## 2587 21.5 Void + +## 2588 21.6 CCBS: monitoring and reporting the status of the subscriber + +### 2589 21.6.1 Reporting co-ordinator process in the VLR + +2590 The MAP co-ordinating process in the VLR to handle a dialogue opened with the reporting application context is shown +2591 in figure 21.6/6. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found +2592 as follows: + +2593       Receive\_Open\_Ind see clause 25.1.1. + +2594 + +### 2595 21.6.2 Setting the reporting state – stand-alone + +2596 The message flow for setting the reporting state in a stand-alone dialogue is shown in figure 21.6/1. + +![Sequence diagram showing message flow between VLR and HLR for setting the reporting state. The HLR sends a request (1) to the VLR, and the VLR sends a response (2) back to the HLR.](fbcb102c13c3286cfefff5bad73d8c6f_img.jpg) + +``` +sequenceDiagram + participant HLR + participant VLR + Note right of HLR: 1 + HLR->>VLR: MAP_SET_REPORTING_STATE_req/ind + Note left of VLR: 2 + VLR-->>HLR: MAP_SET_REPORTING_STATE_rsp/cnf +``` + +Sequence diagram showing message flow between VLR and HLR for setting the reporting state. The HLR sends a request (1) to the VLR, and the VLR sends a response (2) back to the HLR. + +- 2597 +- 2598 +2599 1)       MAP\_SET\_REPORTING\_STATE\_req/ind +2600 2)       MAP\_SET\_REPORTING\_STATE\_rsp/cnf +2601 +2602 +- Figure 21.6/1: Message flow for setting the reporting state – stand-alone dialogue** + +#### 2603 21.6.2.1 Process in the HLR + +2604 The MAP process in the HLR to set the reporting state in the VLR in a stand-alone dialogue is shown in figure 21.6/7. +2605 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +2606       Receive\_Open\_Cnf see clause 25.1.2; + +2607       Check\_Confirmation see clause 25.2.2. + +2608 The result of a request to stop reporting is not reported to the CCBS application in the HLR. + +#### 2609 21.6.2.2 Process in the VLR + +2610 The MAP process in the VLR to set the reporting state is shown in figure 21.6/8. + +2611 The macro Set\_Reporting\_State\_VLR is shown in figure 21.6/9. + +## 2612 21.6.3 Status Reporting + +2613 The message flows for reporting the status of a subscriber are shown in figures 21.6/2 and 21.6/3. + +![Sequence diagram for Figure 21.6/2 showing message flow between VLR and HLR. The HLR sends a request (1) to the VLR, and the VLR responds (2).](12957cc44ed694f84719f5792dc73ed3_img.jpg) + +``` + +sequenceDiagram + participant HLR + participant VLR + Note right of HLR: 1 + HLR->>VLR: + Note left of VLR: 2 + VLR-->>HLR: + +``` + +Sequence diagram for Figure 21.6/2 showing message flow between VLR and HLR. The HLR sends a request (1) to the VLR, and the VLR responds (2). + +2614 + 2615 + 2616 + 2617 + 2618 + 2619 + +- 1) MAP\_STATUS\_REPORT\_req/ind +- 2) MAP\_STATUS\_REPORT\_rsp/cnf + +**Figure 21.6/2: Message flow for status reporting, when monitoring continues in the VLR** + +![Sequence diagram for Figure 21.6/3 showing message flow between VLR and HLR. The HLR sends a request (1) to the VLR. The VLR responds (2) and then sends a request (3) to the HLR. The HLR responds (4).](7c3939cca352ff2db6b1b0e7eef75df1_img.jpg) + +``` + +sequenceDiagram + participant HLR + participant VLR + Note right of HLR: 1 + HLR->>VLR: + Note left of VLR: 2 + VLR-->>HLR: + Note left of VLR: 3 + VLR->>HLR: + Note right of HLR: 4 + HLR-->>VLR: + +``` + +Sequence diagram for Figure 21.6/3 showing message flow between VLR and HLR. The HLR sends a request (1) to the VLR. The VLR responds (2) and then sends a request (3) to the HLR. The HLR responds (4). + +2620 + 2621 + 2622 + 2623 + 2624 + 2625 + 2626 + 2627 + +- 1) MAP\_STATUS\_REPORT\_req/ind +- 2) MAP\_STATUS\_REPORT\_rsp/cnf +- 3) MAP\_SET\_REPORTING\_STATE\_req/ind +- 4) MAP\_SET\_REPORTING\_STATE\_rsp/cnf + +**Figure 21.6/3: Message flow for status reporting, when monitoring stops** + +2628 The MAP\_SET\_REPORTING\_STATE request is used to stop monitoring in the VLR. If the HLR requires the VLR to + 2629 continue monitoring, it closes the dialogue without sending a MAP\_SET\_REPORTING\_STATE request. + +### 2630 21.6.3.1 Process in the VLR + +2631 The MAP process in the VLR to send a status report to the HLR is shown in figure 21.6/10. The MAP process invokes + 2632 macros not defined in this clause; the definitions of these macros can be found as follows: + +- 2633       Receive\_Open\_Cnf see clause 25.1.2; +- 2634       Check\_Confirmation see clause 25.2.2. + +2635 This process can be used to report: + +- 2636       - an event, such as the user becoming free, or +- 2637       - the result of a CCBS call attempt +- 2638 to the HLR + +2639 21.6.3.2 Process in the HLR + +2640 The MAP process in the HLR to handle a status report is shown in figure 21.6/11. The MAP process invokes a macro +2641 not defined in this clause; the definition of this macro can be found as follows: + +2642       Receive\_Open\_Ind see clause 25.1.1; + +2643 It is an implementation option whether to send the MAP\_DELIMITER request before invoking the macro + +2644       Set\_Reporting\_State\_HLR. + +2645 The macro Receive\_Status\_Report\_HLR is shown in figure 21.6/12. + +2646 The macro Set\_Reporting\_State\_HLR is shown in figure 21.6/13. The macro invokes a macro not defined in this clause; +2647 the definition of this macro can be found as follows: + +2648       Check\_Confirmation see clause 25.2.2. + +2649 21.6.4 CCBS: Remote User Free + +2650 The message flows for handling remote user free are shown in figures 21.6/4 and 21.6/5. + +![Sequence diagram for Remote User Free: recall not accepted. It shows two lifelines, VLR and HLR. Step 1 is a message from HLR to VLR. Step 2 is a message from VLR to HLR.](751e1cf53975481ed9d0a1a34089acc4_img.jpg) + +``` + +sequenceDiagram + participant VLR + participant HLR + Note left of VLR: 1 + HLR->>VLR: + Note right of HLR: 2 + VLR->>HLR: + +``` + +Sequence diagram for Remote User Free: recall not accepted. It shows two lifelines, VLR and HLR. Step 1 is a message from HLR to VLR. Step 2 is a message from VLR to HLR. + +2651 + +- 2652 +- 2653 1)       MAP\_REMOTE\_USER\_FREE\_req/ind +- 2654 2)       MAP\_REMOTE\_USER\_FREE\_rsp/cnf +- 2655 +- 2656 + +**Figure 21.6/4: Remote User Free: recall not accepted** + +![Sequence diagram for Remote User Free: recall not accepted. It shows two lifelines, VLR and HLR. Step 1 is a message from HLR to VLR. Step 2 is a message from VLR to HLR. Step 3 is a message from HLR to VLR. Step 4 is a message from VLR to HLR.](12f813f41fdd775110aa16e22731173f_img.jpg) + +``` + +sequenceDiagram + participant VLR + participant HLR + Note left of VLR: 1 + HLR->>VLR: + Note right of HLR: 2 + VLR->>HLR: + Note right of HLR: 3 + HLR->>VLR: + Note left of VLR: 4 + VLR->>HLR: + +``` + +Sequence diagram for Remote User Free: recall not accepted. It shows two lifelines, VLR and HLR. Step 1 is a message from HLR to VLR. Step 2 is a message from VLR to HLR. Step 3 is a message from HLR to VLR. Step 4 is a message from VLR to HLR. + +2657 + +- 2658 +- 2659 1)       MAP\_REMOTE\_USER\_FREE\_req/ind +- 2660 2)       MAP\_REMOTE\_USER\_FREE\_rsp/cnf +- 2661 3)       MAP\_STATUS\_REPORT\_req/ind +- 2662 4)       MAP\_STATUS\_REPORT\_rsp/cnf +- 2663 + +2664 + +**Figure 21.6/5: Remote User Free: recall accepted** + +2665 **21.6.4.1 Process in the HLR** + +2666 The MAP process in the HLR to handle Remote User Free is shown in figure 21.6/14. The MAP process invokes +2667 macros not defined in this clause; the definitions of these macros can be found as follows: + +2668       Receive\_Open\_Cnf see clause 25.1.2; + +2669       Check\_Confirmation see clause 25.2.2. + +2670 **21.6.3.2 Process in the VLR** + +2671 The MAP process in the VLR to handle Remote User Free is shown in figure 21.6/15. The MAP process invokes a +2672 macro not defined in this clause; the definition of this macro can be found as follows: + +2673       Check\_Confirmation see clause 25.2.2. + +![State transition diagram for process Reporting_Coord_VLR. The diagram shows states (Idle, Wait_For_Service_Indication, Relay_Information) and transitions (Receive_Open_Ind, MAP_REMOTE_USER_FREE_ind, MAP_SET_REPORTING_STATE_ind, MAP_NOTICE_ind, MAP_CLOSE_req). It includes callouts for signal directions and process context.](f514006eae532ed76cc7446a17595018_img.jpg) + +**process Reporting\_Coord\_VLR** **Rep\_Co\_VLR1(1)** + +Co-ordinating process in the VLR to handle a dialogue opened with the AC ReportingContext + +Signals to/from the left are to/from the HLR; +signals to/from the right are to/from the child process + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_Ind + Receive_Open_Ind --> Wait_For_Service_Indication : OK + Receive_Open_Ind --> Idle : Vr, Error + Wait_For_Service_Indication --> MAP_REMOTE_USER_FREE_ind + Wait_For_Service_Indication --> MAP_SET_REPORTING_STATE_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + Wait_For_Service_Indication --> MAP_CLOSE_req + MAP_REMOTE_USER_FREE_ind --> Remote_User_Free_VLR + Remote_User_Free_VLR --> MAP_REMOTE_USER_FREE_ind + MAP_REMOTE_USER_FREE_ind --> Relay_Information + MAP_SET_REPORTING_STATE_ind --> Set_Reporting_State_VLR + Set_Reporting_State_VLR --> MAP_SET_REPORTING_STATE_ind + MAP_SET_REPORTING_STATE_ind --> Relay_Information + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + MAP_CLOSE_req --> MAP_U_ABORT_ind + MAP_U_ABORT_ind --> MAP_P_ABORT_ind + MAP_P_ABORT_ind --> MAP_CLOSE_ind + MAP_CLOSE_ind --> Idle + +``` + +State transition diagram for process Reporting\_Coord\_VLR. The diagram shows states (Idle, Wait\_For\_Service\_Indication, Relay\_Information) and transitions (Receive\_Open\_Ind, MAP\_REMOTE\_USER\_FREE\_ind, MAP\_SET\_REPORTING\_STATE\_ind, MAP\_NOTICE\_ind, MAP\_CLOSE\_req). It includes callouts for signal directions and process context. + +2674 + +2675 + +**Figure 21.6/6: Process Reporting\_Coord\_VLR** + +process Set\_Reporting\_State\_Stand\_Alone\_HLR + +SRS\_SA\_HLR1(1) + +Process in the HLR to set the reporting state in the VLR using a separate dialogue + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the CCBS application process in the HLR (see 3GPP TS 23.093) + +![Flowchart for process Set_Reporting_State_Stand_Alone_HLR. It starts at 'Idle', branches into 'Start reporting' and 'Stop reporting', both leading to 'Set required reporting state: Start/Stop'. These lead to a message block with MAP_OPEN_req, MAP_SET_REPORTING_STATE_req, and MAP_DELIMITER_req. This is followed by 'Receive_Open_Cnf'. From 'Receive_Open_Cnf', an 'OK' path leads to 'Wait_For_VLR_Response', which then branches into 'MAP_NOTICE_ind', 'MAP_CLOSE_req', and 'MAP_SET_REPORTING_STATE_cnf'. The 'MAP_SET_REPORTING_STATE_cnf' path leads to 'Check Confirmation', which has an 'OK' path leading to a decision 'Required reporting state=Start?'. If 'Yes', it leads to 'Start reporting ack' and then 'Idle'. If 'No', it leads to 'User Error, Provider Error, Data Error'. The 'MAP_NOTICE_ind' path leads to 'MAP_CLOSE_req', which leads to a decision 'Required reporting state=Start?'. If 'Yes', it leads to 'Start reporting negative response' and then 'Idle'. If 'No', it leads to 'User Error, Provider Error, Data Error'. The 'Receive_Open_Cnf' also has a 'Vr, Error' path leading to a decision 'Required reporting state=Start?'. If 'Yes', it leads to 'Start reporting negative response' and then 'Idle'. If 'No', it leads to 'User Error, Provider Error, Data Error'.](683fef8013ee552e09df0f171a40cf4c_img.jpg) + +``` + +graph TD + Start([ ]) --> Idle1([Idle]) + Idle1 --> StartReporting[Start reporting] + Idle1 --> StopReporting[Stop reporting] + StartReporting --> SetStart[Set required reporting state: Start] + StopReporting --> SetStop[Set required reporting state: Stop] + SetStart --> MapReq[MAP_OPEN_req +MAP_SET_REPORTING_STATE_req +MAP_DELIMITER_req] + SetStop --> MapReq + MapReq --> ReceiveCnf[Receive_Open_Cnf] + ReceiveCnf -- OK --> WaitForResponse[Wait_For_VLR_Response] + ReceiveCnf -- "Vr, Error" --> Decision1{Required reporting state=Start?} + WaitForResponse --> NoticeInd[MAP_NOTICE_ind] + WaitForResponse --> CloseReq[MAP_CLOSE_req] + WaitForResponse --> SetStateCnf[MAP_SET_REPORTING_STATE_cnf] + SetStateCnf --> CheckConfirmation[Check Confirmation] + CheckConfirmation -- OK --> Decision2{Required reporting state=Start?} + CheckConfirmation -- "User Error, Provider Error, Data Error" --> Error1[ ] + Decision2 -- Yes --> StartAck[Start reporting ack] + StartAck --> Idle2([Idle]) + Decision2 -- No --> Decision3{Required reporting state=Start?} + Decision3 -- Yes --> StartAck + StartAck --> Idle2 + Decision3 -- No --> Error1 + NoticeInd --> CloseReq + CloseReq --> Decision4{Required reporting state=Start?} + Decision4 -- Yes --> StartNegResponse[Start reporting negative response] + StartNegResponse --> Idle3([Idle]) + Decision4 -- No --> Error1 + Decision1 -- Yes --> StartNegResponse + StartNegResponse --> Idle3 + Decision1 -- No --> Error1 + +``` + +Flowchart for process Set\_Reporting\_State\_Stand\_Alone\_HLR. It starts at 'Idle', branches into 'Start reporting' and 'Stop reporting', both leading to 'Set required reporting state: Start/Stop'. These lead to a message block with MAP\_OPEN\_req, MAP\_SET\_REPORTING\_STATE\_req, and MAP\_DELIMITER\_req. This is followed by 'Receive\_Open\_Cnf'. From 'Receive\_Open\_Cnf', an 'OK' path leads to 'Wait\_For\_VLR\_Response', which then branches into 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', and 'MAP\_SET\_REPORTING\_STATE\_cnf'. The 'MAP\_SET\_REPORTING\_STATE\_cnf' path leads to 'Check Confirmation', which has an 'OK' path leading to a decision 'Required reporting state=Start?'. If 'Yes', it leads to 'Start reporting ack' and then 'Idle'. If 'No', it leads to 'User Error, Provider Error, Data Error'. The 'MAP\_NOTICE\_ind' path leads to 'MAP\_CLOSE\_req', which leads to a decision 'Required reporting state=Start?'. If 'Yes', it leads to 'Start reporting negative response' and then 'Idle'. If 'No', it leads to 'User Error, Provider Error, Data Error'. The 'Receive\_Open\_Cnf' also has a 'Vr, Error' path leading to a decision 'Required reporting state=Start?'. If 'Yes', it leads to 'Start reporting negative response' and then 'Idle'. If 'No', it leads to 'User Error, Provider Error, Data Error'. + +2676 + +2677 + +Figure 21.6/7: Process Set\_Reporting\_State\_Stand\_Alone\_HLR + +![State transition diagram for process Set_Reporting_State_VLR. The diagram shows a vertical flow: an initial state (oval) leading to an Idle state (rounded rectangle), which leads to a Receive_Set_Reporting_State_VLR state (double-bordered rectangle), which leads to a MAP CLOSE_req state (pentagon). The flow ends at a crossed-out line. Two callout boxes provide additional information: one on the left describes the process as handling an HLR request to set reporting state, and one on the right notes that signals to/from the right are to/from the HLR.](240d7169714fb062f650cf571f5888ea_img.jpg) + +process Set\_Reporting\_State\_VLR + +SRS\_VLR1(1) + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Set_Reporting_State_VLR + Receive_Set_Reporting_State_VLR --> MAP_CLOSE_req + MAP_CLOSE_req --> [*] +``` + +Process in the VLR to handle a request from the HLR to set the reporting state for a subscriber + +Signals to/from the right are to/from the HLR + +State transition diagram for process Set\_Reporting\_State\_VLR. The diagram shows a vertical flow: an initial state (oval) leading to an Idle state (rounded rectangle), which leads to a Receive\_Set\_Reporting\_State\_VLR state (double-bordered rectangle), which leads to a MAP CLOSE\_req state (pentagon). The flow ends at a crossed-out line. Two callout boxes provide additional information: one on the left describes the process as handling an HLR request to set reporting state, and one on the right notes that signals to/from the right are to/from the HLR. + +2678 + +2679 + +Figure 21.6/8: Process Set\_Reporting\_State\_VLR + +macrodefinition Receive\_Set\_Reporting\_State\_VLR + +RSRS\_VLR1(1) + +Macro in the VLR to handle a request from the HLR to set the reporting state for a subscriber + +Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR + +![Flowchart for macrodefinition Receive_Set_Reporting_State_VLR. It starts with an entry point, followed by MAP_SET_REPORTING_STATE_ind. A decision diamond asks 'Required reporting state=Start?'. If 'No', it goes to 'Stop Reporting'. If 'Yes', it goes to 'Start Reporting', then 'Wait_For_Application_Response'. From there, it branches to 'Start Reporting ack' or 'Start Reporting negative response'. The latter leads to 'Set User Error'. Both 'Stop Reporting', 'Start Reporting ack', and 'Set User Error' lead to a common merge point, which then leads to 'MAP_SET_REPORTING_STATE_rsp' and finally an exit point.](00d5ae6b4f3a95e996e39ddb32e522a4_img.jpg) + +``` + +graph TD + Entry(( )) --> Input[/MAP_SET_REPORTING_STATE_ind/] + Input --> Decision{Required reporting state=Start?} + Decision -- No --> StopReporting{{Stop Reporting}} + Decision -- Yes --> StartReporting{{Start Reporting}} + StartReporting --> WaitForResponse([Wait_For_Application_Response]) + WaitForResponse --> StartReportingAck[/Start Reporting ack/] + WaitForResponse --> StartReportingNeg[/Start Reporting negative response/] + StartReportingNeg --> SetUserError[Set User Error] + StopReporting --> Merge(( )) + StartReportingAck --> Merge + SetUserError --> Merge + Merge --> Output[/MAP_SET_REPORTING_STATE_rsp/] + Output --> Exit(( )) + +``` + +Flowchart for macrodefinition Receive\_Set\_Reporting\_State\_VLR. It starts with an entry point, followed by MAP\_SET\_REPORTING\_STATE\_ind. A decision diamond asks 'Required reporting state=Start?'. If 'No', it goes to 'Stop Reporting'. If 'Yes', it goes to 'Start Reporting', then 'Wait\_For\_Application\_Response'. From there, it branches to 'Start Reporting ack' or 'Start Reporting negative response'. The latter leads to 'Set User Error'. Both 'Stop Reporting', 'Start Reporting ack', and 'Set User Error' lead to a common merge point, which then leads to 'MAP\_SET\_REPORTING\_STATE\_rsp' and finally an exit point. + +2680 + +2681 + +Figure 21.6/9: Macro Receive\_Set\_Reporting\_State\_VLR + +![State transition diagram for process Send_Status_Report_VLR. It starts at Idle, branches into Event Report and CCBS Call Report paths, both leading to MAP message building. It then uses a MAP_OPEN_req, MAP_STATUS_REPORT_req, or MAP_DELIMITER_req. After receiving Open_Cnf, it enters Wait_For_HLR_Response. From there, it handles MAP_STATUS_REPORT_cnf, MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind, or MAP_NOTICE_ind. MAP_CLOSE_ind leads to MAP_CLOSE_req. A decision diamond checks if CCBS call report data is present. If No, it goes to Event Report negative response. If Yes, it goes to CCBS Call Report negative response. Both negative responses lead to Wait_For_Set_Reporting_State, which then returns to Idle. Error states (User Error, Provider Error, Data Error, Vr, Error) also lead to Idle.](3de4054a64d656760b2bfd54ed67fb83_img.jpg) + +process Send\_Status\_Report\_VLR SSR\_VLR1(2) + +Process in the VLR to send a status report to the HLR + +Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Event_Report + Idle --> CCBS_Call_Report + Event_Report --> Build_MAP_message_1[Build MAP message] + CCBS_Call_Report --> Build_MAP_message_2[Build MAP message] + Build_MAP_message_2 --> Include_call_report_data[Include call report data] + Build_MAP_message_1 --> MAP_Open_req + Build_MAP_message_2 --> MAP_Open_req + MAP_Open_req --> Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_HLR_Response + Wait_For_HLR_Response --> MAP_STATUS_REPORT_cnf + Wait_For_HLR_Response --> MAP_U_ABORT_ind + Wait_For_HLR_Response --> MAP_P_ABORT_ind + Wait_For_HLR_Response --> MAP_CLOSE_ind + Wait_For_HLR_Response --> MAP_NOTICE_ind + MAP_STATUS_REPORT_cnf --> Check_Confirmation + Check_Confirmation --> User_Error[User Error, Provider Error, Data Error] + User_Error --> Idle + MAP_U_ABORT_ind --> Idle + MAP_P_ABORT_ind --> Idle + MAP_CLOSE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Decision[CCBS call report data present?] + MAP_NOTICE_ind --> Idle + Decision -- No --> Event_Report_negative_response[Event Report negative response] + Decision -- Yes --> CCBS_Call_Report_negative_response[CCBS Call Report negative response] + Event_Report_negative_response --> Wait_For_Set_Reporting_State + CCBS_Call_Report_negative_response --> Idle + Wait_For_Set_Reporting_State --> Idle + Vr_Error[Vr, Error] --> Idle + +``` + +State transition diagram for process Send\_Status\_Report\_VLR. It starts at Idle, branches into Event Report and CCBS Call Report paths, both leading to MAP message building. It then uses a MAP\_OPEN\_req, MAP\_STATUS\_REPORT\_req, or MAP\_DELIMITER\_req. After receiving Open\_Cnf, it enters Wait\_For\_HLR\_Response. From there, it handles MAP\_STATUS\_REPORT\_cnf, MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind, or MAP\_NOTICE\_ind. MAP\_CLOSE\_ind leads to MAP\_CLOSE\_req. A decision diamond checks if CCBS call report data is present. If No, it goes to Event Report negative response. If Yes, it goes to CCBS Call Report negative response. Both negative responses lead to Wait\_For\_Set\_Reporting\_State, which then returns to Idle. Error states (User Error, Provider Error, Data Error, Vr, Error) also lead to Idle. + +2682 + +2683 + +Figure 21.6/10 (sheet 1 of 2): Process Send\_Status\_Report\_VLR + +![State transition diagram for process Send_Status_Report_VLR. It starts in 'Wait_For_Set_Reporting_State' and branches into four paths based on incoming signals: 'Receive_Set_Reporting_State_VLR', 'MAP_CLOSE_ind', 'MAP_NOTICE_ind', and an unlabeled path for 'MAP_U_ABORT_ind' and 'MAP_P_ABORT_ind'. The first three paths lead to 'MAP_CLOSE_req' and then 'Idle'. The unlabeled path leads directly to 'Idle'. 'MAP_CLOSE_ind' also leads to 'Continue Monitoring' before reaching 'Idle'.](27437c680df436ac580ac2cbbe0738f2_img.jpg) + +process Send\_Status\_Report\_VLR SSR\_VLR2(2) + +Process in the VLR to send a status report to the HLR + +Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Wait_For_Set_Reporting_State + state "Wait_For_Set_Reporting_State" as Wait_For_Set_Reporting_State + state "Receive_Set_Reporting_State_VLR" as Receive_Set_Reporting_State_VLR + state "MAP_CLOSE_ind" as MAP_CLOSE_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind" as MAP_U_ABORT_ind_MAP_P_ABORT_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "Continue Monitoring" as Continue_Monitoring + state "Idle" as Idle + + Wait_For_Set_Reporting_State --> Receive_Set_Reporting_State_VLR + Wait_For_Set_Reporting_State --> MAP_CLOSE_ind + Wait_For_Set_Reporting_State --> MAP_NOTICE_ind + Wait_For_Set_Reporting_State --> MAP_U_ABORT_ind_MAP_P_ABORT_ind + + Receive_Set_Reporting_State_VLR --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + + MAP_CLOSE_ind --> Continue_Monitoring + Continue_Monitoring --> Idle + + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + + MAP_U_ABORT_ind_MAP_P_ABORT_ind --> Idle + +``` + +State transition diagram for process Send\_Status\_Report\_VLR. It starts in 'Wait\_For\_Set\_Reporting\_State' and branches into four paths based on incoming signals: 'Receive\_Set\_Reporting\_State\_VLR', 'MAP\_CLOSE\_ind', 'MAP\_NOTICE\_ind', and an unlabeled path for 'MAP\_U\_ABORT\_ind' and 'MAP\_P\_ABORT\_ind'. The first three paths lead to 'MAP\_CLOSE\_req' and then 'Idle'. The unlabeled path leads directly to 'Idle'. 'MAP\_CLOSE\_ind' also leads to 'Continue Monitoring' before reaching 'Idle'. + +2684 + +2685 + +Figure 21.6/10 (sheet 2 of 2): Process Send\_Status\_Report\_VLR + +![State transition diagram for process Status_Report_HLR. The process starts at an initial state, goes to Idle, then receives an Open_Ind. From there, it can go to Wait_For_Service_Indication (OK path) or Idle (Vr, Error path). Wait_For_Service_Indication leads to a decision point for MAP_P_ABORT_ind, Receive_Status_Report_HLR, or MAP_NOTICE_ind. The Receive_Status_Report_HLR path continues through Wait_For_Application_Response, Stop Reporting, Set required reporting state: Stop, MAP_DELIMITER_req, and Set_Reporting_State_HLR to a final Idle state. The MAP_P_ABORT_ind path leads to Idle, then Continue Monitoring, MAP_CLOSE_req, and Idle. The MAP_NOTICE_ind path leads to MAP_CLOSE_req and Idle.](6cba75c8486e1053fc1859aa66af45c6_img.jpg) + +**process Status\_Report\_HLR** **SR\_HLR1(1)** + +Process in the HLR to handle a status report from the VLR + +Signals to/from the left are to/from the VLR; + signals to/from the right are to/from the CCBS application process in the HLR (see 3GPP TS 23.093) + +``` + +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind --> Wait_For_Service_Indication[Wait_For_Service_Indication] : OK + Receive_Open_Ind --> Idle2[Idle] : Vr, Error + Wait_For_Service_Indication --> Decision1{ } + Decision1 --> MAP_P_ABORT_ind[MAP_P_ABORT_ind] + Decision1 --> Receive_Status_Report_HLR[Receive_Status_Report_HLR] + Decision1 --> MAP_NOTICE_ind[MAP_NOTICE_ind] + MAP_P_ABORT_ind --> Idle3[Idle] + Idle3 --> Continue_Monitoring[Continue Monitoring] + Continue_Monitoring --> MAP_CLOSE_req1[MAP_CLOSE_req] + MAP_CLOSE_req1 --> Idle4[Idle] + Receive_Status_Report_HLR --> Wait_For_Application_Response[Wait_For_Application_Response] + Wait_For_Application_Response --> Stop_Reporting[Stop Reporting] + Stop_Reporting --> Set_required_reporting_state[Set required reporting state: Stop] + Set_required_reporting_state --> MAP_DELIMITER_req[MAP_DELIMITER_req] + MAP_DELIMITER_req --> Set_Reporting_State_HLR[Set_Reporting_State_HLR] + Set_Reporting_State_HLR --> Idle5[Idle] : OK, Error, Aborted + MAP_NOTICE_ind --> MAP_CLOSE_req2[MAP_CLOSE_req] + MAP_CLOSE_req2 --> Idle6[Idle] + +``` + +State transition diagram for process Status\_Report\_HLR. The process starts at an initial state, goes to Idle, then receives an Open\_Ind. From there, it can go to Wait\_For\_Service\_Indication (OK path) or Idle (Vr, Error path). Wait\_For\_Service\_Indication leads to a decision point for MAP\_P\_ABORT\_ind, Receive\_Status\_Report\_HLR, or MAP\_NOTICE\_ind. The Receive\_Status\_Report\_HLR path continues through Wait\_For\_Application\_Response, Stop Reporting, Set required reporting state: Stop, MAP\_DELIMITER\_req, and Set\_Reporting\_State\_HLR to a final Idle state. The MAP\_P\_ABORT\_ind path leads to Idle, then Continue Monitoring, MAP\_CLOSE\_req, and Idle. The MAP\_NOTICE\_ind path leads to MAP\_CLOSE\_req and Idle. + +2686 + +2687 + +Figure 21.6/11: Process Status Report\_HLR + +macrodefinition Receive\_Status\_Report\_HLR + +RSR\_HLR1(1) + +Macro in the HLR to receive a status report from the VLR + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the CCBS application process in the HLR (see 3GPP TS 23.093) + +![Flowchart for macrodefinition Receive_Status_Report_HLR. It starts with a connector, followed by MAP_STATUS_REPORT_ind. A decision diamond asks 'CCBS call report data present?'. If 'Yes', it goes to 'CCBS Call Report'. If 'No', it goes to 'Event Report'. Both lead to 'Wait For Application_Response'. From there, four paths emerge: 'CCBS Call Report ack', 'CCBS Call Report negative response' (leading to 'Set User Error'), 'Event Report ack', and 'Event Report negative response' (leading to 'Set User Error'). All four paths converge to 'MAP_STATUS_REPORT_rsp', which ends at a connector.](50b0a679fb121fc66ab60c8a8a5b4ae3_img.jpg) + +``` + +graph TD + Start([ ]) --> Ind{MAP_STATUS_REPORT_ind} + Ind --> Decision{CCBS call report data present?} + Decision -- Yes --> CCBS_Report[CCBS Call Report] + Decision -- No --> Event_Report[Event Report] + CCBS_Report --> Wait[Wait For Application_Response] + Event_Report --> Wait + Wait --> Ack1[CCBS Call Report ack] + Wait --> Neg1[CCBS Call Report negative response] + Wait --> Ack2[Event Report ack] + Wait --> Neg2[Event Report negative response] + Neg1 --> Error1[Set User Error] + Neg2 --> Error2[Set User Error] + Ack1 --> Rsp{MAP_STATUS_REPORT_rsp} + Error1 --> Rsp + Ack2 --> Rsp + Error2 --> Rsp + Rsp --> End([ ]) + +``` + +Flowchart for macrodefinition Receive\_Status\_Report\_HLR. It starts with a connector, followed by MAP\_STATUS\_REPORT\_ind. A decision diamond asks 'CCBS call report data present?'. If 'Yes', it goes to 'CCBS Call Report'. If 'No', it goes to 'Event Report'. Both lead to 'Wait For Application\_Response'. From there, four paths emerge: 'CCBS Call Report ack', 'CCBS Call Report negative response' (leading to 'Set User Error'), 'Event Report ack', and 'Event Report negative response' (leading to 'Set User Error'). All four paths converge to 'MAP\_STATUS\_REPORT\_rsp', which ends at a connector. + +2688 + +2689 + +Figure 21.6/12: Macro Receive\_Status\_Report\_HLR + +# macrodefinition Set\_Reporting\_State\_HLR + +SRS\_HLR1(1) + +Macro in the HLR to instruct the VLR to set the reporting state for a subscriber + +Signals to/from the left are to/from the VLR + +![State transition diagram for Set_Reporting_State_HLR macro. It starts with an initial state leading to a request (MAP_SET_REPORTING_STATE_req, MAP_DELIMITER_req), followed by a wait state (Wait_For_VLR_Response). From there, it branches into three paths: a successful confirmation (MAP_SET_REPORTING_STATE_cnf) leading to a check and then OK or Error states; a notice indication (MAP_NOTICE_ind) leading to a close request (MAP_CLOSE_req) and then an Aborted state; and an abort/close indication (MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind) leading directly to the Aborted state.](86de25c748dbfa7189a602dbda537b3b_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Request + state "MAP_SET_REPORTING_STATE_req
MAP_DELIMITER_req" as Request + Request --> Wait + state "Wait_For_VLR_Response" as Wait + Wait --> Success + state "MAP_SET_REPORTING_STATE_cnf" as Success + Success --> Check + state "Check_Confirmation" as Check + Check --> OK + state "OK" as OK + Check --> Error + state "Error" as Error + Note right of Error: User Error, Provider Error, Data Error + Wait --> Notice + state "MAP_NOTICE_ind" as Notice + Notice --> CloseReq + state "MAP_CLOSE_req" as CloseReq + CloseReq --> Aborted + state "Aborted" as Aborted + Wait --> AbortClose + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" as AbortClose + AbortClose --> Aborted + +``` + +State transition diagram for Set\_Reporting\_State\_HLR macro. It starts with an initial state leading to a request (MAP\_SET\_REPORTING\_STATE\_req, MAP\_DELIMITER\_req), followed by a wait state (Wait\_For\_VLR\_Response). From there, it branches into three paths: a successful confirmation (MAP\_SET\_REPORTING\_STATE\_cnf) leading to a check and then OK or Error states; a notice indication (MAP\_NOTICE\_ind) leading to a close request (MAP\_CLOSE\_req) and then an Aborted state; and an abort/close indication (MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind) leading directly to the Aborted state. + +2690 + +2691 + +Figure 21.6/13: Macro Set\_Reporting\_State\_HLR + +process Remote\_User\_Free\_HLR + +RUF\_HLR1(1) + +Process in the HLR to send a Remote User Free notification to the VLR + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the CCBS application process in the HLR (see 3GPP TS 23.093) + +![State transition diagram for process Remote_User_Free_HLR. The process starts at an 'Idle' state, receives a 'CCBS RUF' signal, sends 'MAP_OPEN_req', 'MAP_REMOTE_USER_FREE_req', and 'MAP_DELIMITER_req' to the VLR, receives 'Receive_Open_Cnf', and then enters a 'Wait_For_VLR_Response' state. From there, it branches based on the response: 'OK' leads to 'MAP_REMOTE_USER_FREE_cnf' and 'Check_Confirmation'; 'User Error, Provider Error, Data Error' leads to 'MAP_CLOSE_req'; 'Vr, Error' leads to 'Set negative response: System failure'. 'Check_Confirmation' leads to 'CCBS RUF ack' and 'Wait_For_Status_Report'. 'Wait_For_Status_Report' branches to 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' (leading to 'Idle'), 'MAP_NOTICE_ind' (leading to 'MAP_CLOSE_req' and then 'Idle'), 'Receive_Status_Report_HLR' (leading to 'Abort' and then 'MAP_CLOSE_req' and 'Idle'), or 'Set negative response: System failure' (leading to 'CCBS RUF negative response' and then 'Idle').](4300fa385c800064ed8ea51254c7aaaa_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> CCBS_RUF_in {CCBS RUF} + CCBS_RUF_in --> Send_Requests + state "Send Requests" as Send_Requests + Send_Requests : MAP_OPEN_req, MAP_REMOTE_USER_FREE_req, MAP_DELIMITER_req + Send_Requests --> Receive_Open_Cnf + state "Receive_Open_Cnf" as Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_VLR_Response + state "Wait_For_VLR_Response" as Wait_For_VLR_Response + Wait_For_VLR_Response --> OK + Wait_For_VLR_Response --> Error + OK --> MAP_REMOTE_USER_FREE_cnf + state "MAP_REMOTE_USER_FREE_cnf" as MAP_REMOTE_USER_FREE_cnf + MAP_REMOTE_USER_FREE_cnf --> Check_Confirmation + state "Check_Confirmation" as Check_Confirmation + Check_Confirmation --> CCBS_RUF_ack + state "CCBS RUF ack" as CCBS_RUF_ack + CCBS_RUF_ack --> Wait_For_Status_Report + state "Wait_For_Status_Report" as Wait_For_Status_Report + Wait_For_Status_Report --> Abort_Ind + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" as Abort_Ind + Abort_Ind --> Idle + Wait_For_Status_Report --> Notice_Ind + state "MAP_NOTICE_ind" as Notice_Ind + Notice_Ind --> MAP_CLOSE_req + state "MAP_CLOSE_req" as MAP_CLOSE_req + MAP_CLOSE_req --> Idle + Wait_For_Status_Report --> Status_Report + state "Receive_Status_Report_HLR" as Status_Report + Status_Report --> Abort + state "Abort" as Abort + Abort --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + Wait_For_Status_Report --> System_Failure + state "Set negative response: System failure" as System_Failure + System_Failure --> CCBS_RUF_negative_response + state "CCBS RUF negative response" as CCBS_RUF_negative_response + CCBS_RUF_negative_response --> Idle + Error --> Vr_Error + state "Vr, Error" as Vr_Error + Vr_Error --> System_Failure + User_Error --> MAP_CLOSE_req + state "User Error, Provider Error, Data Error" as User_Error + User_Error --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + +``` + +State transition diagram for process Remote\_User\_Free\_HLR. The process starts at an 'Idle' state, receives a 'CCBS RUF' signal, sends 'MAP\_OPEN\_req', 'MAP\_REMOTE\_USER\_FREE\_req', and 'MAP\_DELIMITER\_req' to the VLR, receives 'Receive\_Open\_Cnf', and then enters a 'Wait\_For\_VLR\_Response' state. From there, it branches based on the response: 'OK' leads to 'MAP\_REMOTE\_USER\_FREE\_cnf' and 'Check\_Confirmation'; 'User Error, Provider Error, Data Error' leads to 'MAP\_CLOSE\_req'; 'Vr, Error' leads to 'Set negative response: System failure'. 'Check\_Confirmation' leads to 'CCBS RUF ack' and 'Wait\_For\_Status\_Report'. 'Wait\_For\_Status\_Report' branches to 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' (leading to 'Idle'), 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req' and then 'Idle'), 'Receive\_Status\_Report\_HLR' (leading to 'Abort' and then 'MAP\_CLOSE\_req' and 'Idle'), or 'Set negative response: System failure' (leading to 'CCBS RUF negative response' and then 'Idle'). + +2692 + +2693 + +Figure 21.6/14: Process Remote\_User\_Free\_HLR + +![State transition diagram for process Remote_User_Free_VLR. It starts at Idle, receives MAP_REMOTE_USER_FREE_ind, enters CCBS RUF state, and waits for a response. Responses include ack (accepted), ack (unsuccessful), negative response, or an abort/close indication. Successful ack leads to sending responses and waiting for a call report. Unsuccessful ack and negative response lead to setting an error and sending responses. The abort/close path ends in a terminal state.](e343a5925678a3d9126523971922bd1c_img.jpg) + +**process Remote\_User\_Free\_VLR** **RUF\_VLR1(2)** + +Process in the VLR to handle a Remote User Free notification from the HLR + +Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> MAP_REMOTE_USER_FREE_ind + MAP_REMOTE_USER_FREE_ind --> CCBS_RUF : CCBS RUF + CCBS_RUF --> Wait_For_Application_Response + state "Wait_For_Application_Response" as Wait_For_Application_Response + state "CCBS RUF ack (Recall accepted)" as CCBS_RUF_ack_accepted + state "CCBS RUF ack (Recall unsuccessful)" as CCBS_RUF_ack_unsuccessful + state "CCBS RUF negative response" as CCBS_RUF_negative_response + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" as Abort_Close_Ind + state "Set User Error" as Set_User_Error + state "MAP_REMOTE_USER_FREE_rsp, MAP_DELIMITER_req" as Rsp_Delimiter_Req + state "MAP_REMOTE_USER_FREE_rsp, MAP_CLOSE_req" as Rsp_Close_Req + state "Wait_For_Call_Report" as Wait_For_Call_Report + state "X" as Terminal + + Wait_For_Application_Response --> CCBS_RUF_ack_accepted + Wait_For_Application_Response --> CCBS_RUF_ack_unsuccessful + Wait_For_Application_Response --> CCBS_RUF_negative_response + Wait_For_Application_Response --> Abort_Close_Ind + + CCBS_RUF_ack_accepted --> Rsp_Delimiter_Req + Rsp_Delimiter_Req --> Wait_For_Call_Report + + CCBS_RUF_ack_unsuccessful --> Set_User_Error + Set_User_Error --> Rsp_Close_Req + Rsp_Close_Req --> Terminal + + CCBS_RUF_negative_response --> Set_User_Error + Set_User_Error --> Rsp_Close_Req + Rsp_Close_Req --> Terminal + + Abort_Close_Ind --> Terminal + +``` + +State transition diagram for process Remote\_User\_Free\_VLR. It starts at Idle, receives MAP\_REMOTE\_USER\_FREE\_ind, enters CCBS RUF state, and waits for a response. Responses include ack (accepted), ack (unsuccessful), negative response, or an abort/close indication. Successful ack leads to sending responses and waiting for a call report. Unsuccessful ack and negative response lead to setting an error and sending responses. The abort/close path ends in a terminal state. + +2694 + +2695 + +**Figure 21.6/15 (sheet 1 of 2): Process Remote\_User\_Free\_VLR** + +![Sequence diagram for process Remote_User_Free_VLR. The process starts in a 'Wait_For_Call_Report' state. It receives a 'CCBS Call Report' from the left, which triggers a 'MAP_STATUS_REPORT_req' and 'MAP_DELIMITER_req' to the right. It then enters a 'Wait_For_HLR_Response' state. From there, it can receive a 'MAP_STATUS_REPORT_cnf' from the right, leading to a 'Check_Confirmation' block. If 'OK', the process ends. If 'User Error, Provider Error, Data Error', it sends a 'MAP_CLOSE_req' to the right. Alternatively, it can receive a 'MAP_NOTICE_ind' from the right, which triggers a 'MAP_CLOSE_req' to the right. It also receives various indication signals (ABORT, CLOSE) from the right. The process ends in a negative response state.](bf4cb26ecd7a615a6de16a510d0d06e5_img.jpg) + +**process Remote\_User\_Free\_VLR** **RUF\_VLR2(2)** + +Process in the VLR to handle a Remote User Free notification from the HLR + +Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR + +``` + +sequenceDiagram + participant VLR as Remote_User_Free_VLR + Note right of VLR: Wait_For_Call_Report + Note left of VLR: CCBS Call Report + Note right of VLR: MAP_STATUS_REPORT_req, MAP_DELIMITER_req + Note left of VLR: Wait_For_HLR_Response + Note right of VLR: MAP_STATUS_REPORT_cnf + Note left of VLR: Check_Confirmation + Note right of VLR: OK + Note right of VLR: User Error, Provider Error, Data Error + Note right of VLR: MAP_CLOSE_req + Note right of VLR: MAP_NOTICE_ind + Note right of VLR: MAP_CLOSE_req + Note right of VLR: CCBS Call Report negative response + +``` + +Sequence diagram for process Remote\_User\_Free\_VLR. The process starts in a 'Wait\_For\_Call\_Report' state. It receives a 'CCBS Call Report' from the left, which triggers a 'MAP\_STATUS\_REPORT\_req' and 'MAP\_DELIMITER\_req' to the right. It then enters a 'Wait\_For\_HLR\_Response' state. From there, it can receive a 'MAP\_STATUS\_REPORT\_cnf' from the right, leading to a 'Check\_Confirmation' block. If 'OK', the process ends. If 'User Error, Provider Error, Data Error', it sends a 'MAP\_CLOSE\_req' to the right. Alternatively, it can receive a 'MAP\_NOTICE\_ind' from the right, which triggers a 'MAP\_CLOSE\_req' to the right. It also receives various indication signals (ABORT, CLOSE) from the right. The process ends in a negative response state. + +2696 + +2697 + +**Figure 21.6/15 (sheet 2 of 2): Process Remote\_User\_Free\_VLR** + +2698 21.7 Void + +2699 21.8 Void + +## 2700 21.9 Immediate Service Termination (IST) + +### 2701 21.9.1 IST Alert + +2702 The Immediate Service Termination Alert procedure is used to keep track of the call activities performed by subscribers +2703 who are marked as being subject to IST monitoring and, possibly, to terminate the call activities for which the alert was +2704 sent, or all the call activities related to the subscriber for whom the alert was sent. + +2705 The message flow for alerting is shown in figure 21.9/1; the MSC may be a Visited MSC or a Gateway MSC. + +![Sequence diagram showing the message flow for IST Alert between an MSC and an HLR. The MSC sends a message to the HLR (labeled 1), and the HLR responds (labeled 2).](f252804b6058cc43c4ee3a3251702abe_img.jpg) + +``` +sequenceDiagram + participant MSC + participant HLR + Note right of HLR: 1 + MSC->>HLR: + Note left of MSC: 2 + HLR-->>MSC: +``` + +Sequence diagram showing the message flow for IST Alert between an MSC and an HLR. The MSC sends a message to the HLR (labeled 1), and the HLR responds (labeled 2). + +2706 + +2707 +2708 1) MAP\_IST\_ALERT\_req/ind +2709 2) MAP\_IST\_ALERT\_rsp/cnf +2710 +2711 + +Figure 21.9/1: Message flow for IST Alert + +### 2712 21.9.1.1 Procedure in the MSC + +2713 The MAP process in the MSC (Visited MSC or Gateway MSC) is shown in figure 21.9/3. The MAP process invokes +2714 macros not defined in this clause; the definitions of these macros can be found as follows: + +2715       Receive\_Open\_Cnf           see clause 25.1.2; + +2716       Check\_Confirmation         see clause 25.2.2. + +### 2717 21.9.1.2 Procedure in the HLR + +2718 The MAP process in the HLR is shown in figure 21.9/4. The MAP process invokes a macro not defined in this clause; +2719 the definition of this macro can be found as follows: + +2720       Receive\_Open\_Ind           see clause 25.1.1; + +## 2721 21.9.2 IST Command + +2722 The Immediate Service Termination Command procedure is used to terminate the call activities related to a subscriber. + +2723 The message flow for the IST Command procedure is shown in figure 21.9/2; the MSC may be a Visited MSC or a +2724 Gateway MSC. + +![Sequence diagram showing message flow between MSC and HLR. The MSC sends a message (1) to the HLR, and the HLR responds (2).](527a7b5533d626c7395e2606b08fc220_img.jpg) + +``` + +sequenceDiagram + participant MSC + participant HLR + Note left of MSC: 1 + MSC->>HLR: + Note right of HLR: 2 + HLR->>MSC: + +``` + +Sequence diagram showing message flow between MSC and HLR. The MSC sends a message (1) to the HLR, and the HLR responds (2). + +2725 + +2726 + +2727 1) MAP\_IST\_COMMAND\_req/ind + +2728 2) MAP\_IST\_COMMAND\_rsp/cnf + +2729 + +2730 + +**Figure 21.9/2: Message flow for IST Command** + +### 2731 21.9.2.1 Procedure in the HLR + +2732 The MAP process in the HLR is shown in figure 21.9/5. The MAP process invokes macros not defined in this clause; +2733 the definitions of these macros can be found as follows: + +2734 Receive\_Open\_Cnf see clause 25.1.2; + +2735 Check\_Confirmation see clause 25.2.2. + +### 2736 21.9.2.2 Procedure in the MSC + +2737 The MAP process in the MSC is shown in figure 21.9/6. The MAP process invokes a macro not defined in this clause; +2738 the definition of this macro can be found as follows: + +2739 Receive\_Open\_Ind see clause 25.1.1. + +![State transition diagram for process IST_Alert_MSC. The process starts at an initial state, goes to Idle, then IST Alert. It sends MAP_OPEN_req, MAP_IST_ALERT_req, and MAP_DELIMITER_req to the HLR. It receives Open_Cnf. If OK, it goes to Wait_For_HLR_Response. If Vr, Error, it goes to IST Alert negative response and then Idle. From Wait_For_HLR_Response, it receives MAP_IST_ALERT_cnf, MAP_NOTICE_ind, and MAP_CLOSE_req. If MAP_IST_ALERT_cnf is OK, it goes to Check Confirmation. If MAP_NOTICE_ind is User Error, Provider Error, or Data Error, it goes to IST Alert negative response. If MAP_CLOSE_req is OK, it goes to IST Alert ack. If MAP_CLOSE_req is not OK, it goes to IST Alert negative response. Both IST Alert ack and IST Alert negative response lead to Idle. There is also a transition from the third state to MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind.](e41e58044b89601b2e949f518af843eb_img.jpg) + +process IST\_Alert\_MSC + +ISTA\_MSC1(1) + +Process in the MSC to send an IST alert to the HLR + +Signals to/from the left are to/from the call handling application process in the MSC; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> IST_Alert + IST_Alert --> State1 + State1 --> Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_HLR_Response: OK + Receive_Open_Cnf --> IST_Alert_negative_response: Vr, Error + IST_Alert_negative_response --> Idle + Wait_For_HLR_Response --> MAP_IST_ALERT_cnf + Wait_For_HLR_Response --> MAP_NOTICE_ind + Wait_For_HLR_Response --> State3 + State3 --> MAP_U_ABORT_ind + MAP_IST_ALERT_cnf --> Check_Confirmation + Check_Confirmation --> IST_Alert_ack: OK + Check_Confirmation --> MAP_CLOSE_req: User Error, Provider Error, Data Error + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> IST_Alert_ack: OK + MAP_CLOSE_req --> IST_Alert_negative_response: User Error, Provider Error, Data Error + IST_Alert_ack --> Idle + IST_Alert_negative_response --> Idle + +``` + +2740 + +2741 + +State transition diagram for process IST\_Alert\_MSC. The process starts at an initial state, goes to Idle, then IST Alert. It sends MAP\_OPEN\_req, MAP\_IST\_ALERT\_req, and MAP\_DELIMITER\_req to the HLR. It receives Open\_Cnf. If OK, it goes to Wait\_For\_HLR\_Response. If Vr, Error, it goes to IST Alert negative response and then Idle. From Wait\_For\_HLR\_Response, it receives MAP\_IST\_ALERT\_cnf, MAP\_NOTICE\_ind, and MAP\_CLOSE\_req. If MAP\_IST\_ALERT\_cnf is OK, it goes to Check Confirmation. If MAP\_NOTICE\_ind is User Error, Provider Error, or Data Error, it goes to IST Alert negative response. If MAP\_CLOSE\_req is OK, it goes to IST Alert ack. If MAP\_CLOSE\_req is not OK, it goes to IST Alert negative response. Both IST Alert ack and IST Alert negative response lead to Idle. There is also a transition from the third state to MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind. + +Figure 21.9/3: Process IST\_Alert\_MSC + +![State transition diagram for process IST_Alert_HLR. The process starts at an initial state, goes to Idle, then receives an Open_Ind. If OK, it waits for a service indication. From there, it can handle MAP_P_ABORT_ind, MAP_IST_ALERT_ind, or MAP_NOTICE_ind. MAP_IST_ALERT_ind leads to an IST Alert state and then waiting for an application response. Responses include IST Alert ack, IST Alert negative response, or a combined response. MAP_NOTICE_ind leads to a MAP_CLOSE_req and then Idle. MAP_P_ABORT_ind also leads to Idle. The combined response includes MAP_IST_ALERT_rsp and MAP_CLOSE_req.](1962ee7e9a747e60da0f0a30a9509763_img.jpg) + +**process IST\_Alert\_HLR** **ISTA\_HLR(1)** + +Process in the HLR to handle an IST Alert from the MSC + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the IST application process in the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_Ind + Receive_Open_Ind --> Wait_For_Service_Indication: OK + Receive_Open_Ind --> Idle: Vr, Error + Wait_For_Service_Indication --> MAP_P_ABORT_ind + Wait_For_Service_Indication --> MAP_IST_ALERT_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + MAP_P_ABORT_ind --> Idle + MAP_IST_ALERT_ind --> IST_Alert + IST_Alert --> Wait_For_Application_Response + Wait_For_Application_Response --> IST_Alert_ack + Wait_For_Application_Response --> IST_Alert_negative_response + Wait_For_Application_Response --> Combined_Response + IST_Alert_ack --> Idle + IST_Alert_negative_response --> Set_User_Error + Set_User_Error --> Combined_Response + Combined_Response --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + +``` + +MAP\_P\_ABORT\_ind + MAP\_IST\_ALERT\_ind + MAP\_NOTICE\_ind + IST Alert + Wait\_For\_Application\_Response + IST Alert ack + IST Alert negative response + Set User Error + MAP\_IST\_ALERT\_rsp + MAP\_CLOSE\_req + +State transition diagram for process IST\_Alert\_HLR. The process starts at an initial state, goes to Idle, then receives an Open\_Ind. If OK, it waits for a service indication. From there, it can handle MAP\_P\_ABORT\_ind, MAP\_IST\_ALERT\_ind, or MAP\_NOTICE\_ind. MAP\_IST\_ALERT\_ind leads to an IST Alert state and then waiting for an application response. Responses include IST Alert ack, IST Alert negative response, or a combined response. MAP\_NOTICE\_ind leads to a MAP\_CLOSE\_req and then Idle. MAP\_P\_ABORT\_ind also leads to Idle. The combined response includes MAP\_IST\_ALERT\_rsp and MAP\_CLOSE\_req. + +2742 + +2743 + +Figure 21.9/4: Process IST\_Alert\_HLR + +![State transition diagram for process IST_Command_HLR. The process starts at an initial state, goes to Idle, then receives an IST Command. It sends MAP_OPEN_req, MAP_IST_COMMAND_req, and MAP_DELIMITER_req, then receives Open_Cnf. If OK, it goes to Wait_For_MSC_Response. If Vr, Error, it sends an IST Command negative response and returns to Idle. From Wait_For_MSC_Response, it can receive MAP_IST_COMMAND_cnf, MAP_NOTICE_ind, or an empty box. MAP_IST_COMMAND_cnf leads to Check_Confirmation. If OK, it sends an IST Command ack and returns to Idle. If User Error, Provider Error, or Data Error, it sends an IST Command negative response and returns to Idle. MAP_NOTICE_ind leads to MAP_CLOSE_req. An empty box leads to a box with MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind. Both lead to IST Command negative response and return to Idle.](009a676afba09ee7f6a02dbf84a75fb8_img.jpg) + +process IST\_Command\_HLR ISTC\_HLR1(1) + +Process in the HLR to send an IST command to the MSC + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the IST application process in the HLR + +``` + +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> IST_Command[IST Command] + IST_Command --> MAP_Requests[MAP_OPEN_req, MAP_IST_COMMAND_req, MAP_DELIMITER_req] + MAP_Requests --> Receive_Open_Cnf[Receive_Open_Cnf] + Receive_Open_Cnf --> Wait_For_MSC_Response[Wait_For_MSC_Response] + Wait_For_MSC_Response --> OK1[OK] + Wait_For_MSC_Response --> Vr_Error[Vr, Error] + Vr_Error --> IST_Neg_Response1[IST Command negative response] + IST_Neg_Response1 --> Idle2[Idle] + OK1 --> MAP_IST_COMMAND_cnf[MAP_IST_COMMAND_cnf] + OK1 --> MAP_NOTICE_ind[MAP_NOTICE_ind] + OK1 --> EmptyBox[ ] + EmptyBox --> MAP_U_ABORT_ind[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + MAP_IST_COMMAND_cnf --> Check_Confirmation[Check_Confirmation] + Check_Confirmation --> OK2[OK] + Check_Confirmation --> User_Error[User Error, Provider Error, Data Error] + User_Error --> IST_Neg_Response2[IST Command negative response] + IST_Neg_Response2 --> Idle3[Idle] + OK2 --> IST_Ack[IST Command ack] + IST_Ack --> Idle4[Idle] + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> IST_Neg_Response3[IST Command negative response] + IST_Neg_Response3 --> Idle5[Idle] + MAP_U_ABORT_ind --> IST_Neg_Response4[IST Command negative response] + IST_Neg_Response4 --> Idle6[Idle] + +``` + +State transition diagram for process IST\_Command\_HLR. The process starts at an initial state, goes to Idle, then receives an IST Command. It sends MAP\_OPEN\_req, MAP\_IST\_COMMAND\_req, and MAP\_DELIMITER\_req, then receives Open\_Cnf. If OK, it goes to Wait\_For\_MSC\_Response. If Vr, Error, it sends an IST Command negative response and returns to Idle. From Wait\_For\_MSC\_Response, it can receive MAP\_IST\_COMMAND\_cnf, MAP\_NOTICE\_ind, or an empty box. MAP\_IST\_COMMAND\_cnf leads to Check\_Confirmation. If OK, it sends an IST Command ack and returns to Idle. If User Error, Provider Error, or Data Error, it sends an IST Command negative response and returns to Idle. MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req. An empty box leads to a box with MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind. Both lead to IST Command negative response and return to Idle. + +2744 + +2745 + +Figure 21.9/5: Process IST\_Command\_HLR + +![Sequence diagram for process IST_Command_MSC. The diagram shows the state transitions and message exchanges for handling an IST Command. It starts at an initial state, goes to Idle, receives an Open_Ind, and then branches based on the response (OK or Vr, Error). The OK path leads to Wait_For_Service_Indication, which then branches into three possible indications: MAP_P_ABORT_ind, MAP_IST_COMMAND_ind, and MAP_NOTICE_ind. The MAP_IST_COMMAND_ind path leads to an IST Command state, then Wait_For_Application_Response, which branches into IST Command ack, IST Command negative response, or a combined state with MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind. The IST Command ack path leads to a state with MAP_IST_COMMAND_rsp and MAP_CLOSE_req, which then leads to Idle. The IST Command negative response path leads to Set User Error, which then leads to the combined state. The combined state leads to Idle. The MAP_P_ABORT_ind and MAP_NOTICE_ind paths both lead to Idle states. The Vr, Error path from the initial Open_Ind also leads to Idle.](e791584696ddaa89eecf172a72ae05e9_img.jpg) + +process IST\_Command\_MSC ISTC\_MSC1(1) + +Process in the MSC to handle an IST Command from the HLR + +Signals to/from the left are to/from the call handling application process in the MSC; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Open_Ind : Receive_Open_Ind + Open_Ind --> Wait_For_Service_Indication : OK + Open_Ind --> Idle : Vr, Error + Wait_For_Service_Indication --> MAP_P_ABORT_ind : MAP_P_ABORT_ind + Wait_For_Service_Indication --> MAP_IST_COMMAND_ind : MAP_IST_COMMAND_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind : MAP_NOTICE_ind + MAP_P_ABORT_ind --> Idle + MAP_IST_COMMAND_ind --> IST_Command : IST Command + IST_Command --> Wait_For_Application_Response : Wait_For_Application_Response + Wait_For_Application_Response --> Ack : IST Command ack + Wait_For_Application_Response --> Negative : IST Command negative response + Wait_For_Application_Response --> Combined : MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + Ack --> Rsp : MAP_IST_COMMAND_rsp, MAP_CLOSE_req + Rsp --> Idle + Negative --> Set_User_Error : Set User Error + Set_User_Error --> Combined + Combined --> Idle + MAP_NOTICE_ind --> Close_Req : MAP_CLOSE_req + Close_Req --> Idle + +``` + +Sequence diagram for process IST\_Command\_MSC. The diagram shows the state transitions and message exchanges for handling an IST Command. It starts at an initial state, goes to Idle, receives an Open\_Ind, and then branches based on the response (OK or Vr, Error). The OK path leads to Wait\_For\_Service\_Indication, which then branches into three possible indications: MAP\_P\_ABORT\_ind, MAP\_IST\_COMMAND\_ind, and MAP\_NOTICE\_ind. The MAP\_IST\_COMMAND\_ind path leads to an IST Command state, then Wait\_For\_Application\_Response, which branches into IST Command ack, IST Command negative response, or a combined state with MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind. The IST Command ack path leads to a state with MAP\_IST\_COMMAND\_rsp and MAP\_CLOSE\_req, which then leads to Idle. The IST Command negative response path leads to Set User Error, which then leads to the combined state. The combined state leads to Idle. The MAP\_P\_ABORT\_ind and MAP\_NOTICE\_ind paths both lead to Idle states. The Vr, Error path from the initial Open\_Ind also leads to Idle. + +2746 + +2747 + +Figure 21.9/6: Process IST\_Command\_MSC + +## 21.10 Resource Management + +### 21.10.1 General + +The message flow for successful release of resources is shown in figure 21.10/1. + +![Sequence diagram showing message flow for early release of resources between GMSC, HLR, and VMSC/VLR.](4286d6102bce8b0903b7ad79cd772959_img.jpg) + +The diagram is a sequence diagram with three lifelines: GMSC, HLR, and VMSC/VLR. The message flow is as follows: + +- An external message (1) is received by the GMSC. +- The GMSC sends a message (2) to the HLR. +- The HLR sends a message (3) to the VMSC/VLR. +- An external message (4) is received by the GMSC. +- The VMSC/VLR sends a message (5) to the HLR. +- The HLR sends a message (6) to the GMSC. +- The GMSC sends a message (7) to the VMSC/VLR. + +Sequence diagram showing message flow for early release of resources between GMSC, HLR, and VMSC/VLR. + +2751 + +2752 + +- 2753 1) I\_IAM (Note 1) +- 2754 2) MAP\_SEND\_ROUTING\_INFORMATION\_req/ind +- 2755 3) MAP\_PROVIDE\_ROAMING\_NUMBER\_req/ind +- 2756 4) I\_REL (Note 1) +- 2757 5) MAP\_PROVIDE\_ROAMING\_NUMBER\_rsp/cnf +- 2758 6) MAP\_SEND\_ROUTING\_INFORMATION\_rsp/cnf +- 2759 7) *MAP\_RELEASE\_RESOURCES* (Note 2) + +2760 + +2761 NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the +2762 MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations +2763 & ETSI specification: +2764 - Q.721-725 - Telephone User Part (TUP); +2765 - ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part +2766 (ISUP) version 2 for the international interface; Part 1: Basic services. + +2767 + +NOTE 2: Services printed in *italics* are optional. + +2768 + +2769 + +**Figure 21.10/1: Message flow for early release of resources** + +### 21.3.2 Process in the GMSC + +2771 The MAP process in the GMSC to release resources is shown in figure 21.10/2. The MAP process invokes macros not +2772 defined in this clause; the definitions of these macros can be found as follows: + +2773 Receive\_Open\_Cnf see clause 25.1.2; + +2774 Check\_Confirmation see clause 25.2.2. + +### 21.3.3 Process in the VMSC + +2776 The MAP process in the VMSC to handle a request for the GMSC to release resources is shown in figure 21.10/3. The +2777 MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +2778 Receive\_Open\_Ind see clause 25.1.1; + +process Release\_Resources\_GMSC + +1(1) + +Process in the GMSC to request the VMSC to release resources + +Signals to/from the left are to/from the application process in the GMSC (see 3GPP TS 23.018); signals to/from the right are to/from the VMSC; + +![State transition diagram for process Release_Resources_GMSC. It starts at an initial state, goes to Idle, then Release Resources. A transition leads to a state where MAP_OPEN_req, MAPRELEASE_RESOURCES_req, and MAP_DELIMITER_req are sent. Then, Receive_Open_cnf is received. If OK, it goes to Wait_For_VMSC_Response. If Vr, Error, it goes to Idle. From Wait_For_VMSC_Response, three transitions are possible: MAP_NOTICE_ind (leading to MAP_CLOSE_req), MAP_RELEASE_RESOURCES_cnf (leading to Idle), and a transition leading to a state where MAP_P_ABORT_ind and MAP_CLOSE_req are sent. All three paths eventually lead to the Idle state.](1fc4ebd7c0ce26ca009bfb082bbe39d1_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> ReleaseResources[Release Resources] + ReleaseResources --> Out1[ ] + state " " as Out1 + Out1 --> In1[ ] + state " " as In1 + In1 --> ReceiveOpenCnf[Receive_Open_cnf] + ReceiveOpenCnf --> WaitForVMSCResponse[Wait_For_VMSC_Response] + ReceiveOpenCnf --> Idle2[Idle] + Note right of In1: MAP_OPEN_req +MAPRELEASE_RESOURCES_req +MAP_DELIMITER_req + Note right of WaitForVMSCResponse: OK + Note right of Idle2: Vr, Error + WaitForVMSCResponse --> Out2[ ] + state " " as Out2 + Out2 --> In2[ ] + state " " as In2 + In2 --> MAPNoticeInd[MAP_NOTICE_ind] + In2 --> MAPReleaseResourcesCnf[MAP_RELEASE_RESOURCES_cnf] + In2 --> Out3[ ] + state " " as Out3 + Out3 --> In3[ ] + state " " as In3 + In3 --> MAPCloseReq1[MAP_CLOSE_req] + In3 --> Idle3[Idle] + Note right of Out3: MAP_P_ABORT_ind, +MAP_CLOSE_req + MAPNoticeInd --> MAPCloseReq2[MAP_CLOSE_req] + MAPCloseReq2 --> Idle3 + MAPReleaseResourcesCnf --> Idle3 + +``` + +State transition diagram for process Release\_Resources\_GMSC. It starts at an initial state, goes to Idle, then Release Resources. A transition leads to a state where MAP\_OPEN\_req, MAPRELEASE\_RESOURCES\_req, and MAP\_DELIMITER\_req are sent. Then, Receive\_Open\_cnf is received. If OK, it goes to Wait\_For\_VMSC\_Response. If Vr, Error, it goes to Idle. From Wait\_For\_VMSC\_Response, three transitions are possible: MAP\_NOTICE\_ind (leading to MAP\_CLOSE\_req), MAP\_RELEASE\_RESOURCES\_cnf (leading to Idle), and a transition leading to a state where MAP\_P\_ABORT\_ind and MAP\_CLOSE\_req are sent. All three paths eventually lead to the Idle state. + +2779 +2780 + +Figure 21.10/2: Process Release Resources\_GMSC + +process Release\_Resources\_VMSC + +1(1) + +Process in the VMSC to handle a request to release resources + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the application process in the VMSC (see 3GPP TS 23.018) + +![State transition diagram for process Release_Resources_VMSC. It starts at an initial state, goes to Idle, then receives an Open_ind. From there, it branches based on OK or Vr, Error. The OK path leads to Wait_For_Service_Indication, which then branches into three paths: MAP_P_ABORT_ind (leading to Idle), a central path with MAP_RELEASE_RESOURCES_ind, Release Resources, Wait-For_Call_Handling_Response, Release Resources Ack, and finally Idle; and a right path with MAP_NOTICE_ind, MAP_CLOSE_req, and Idle. The Vr, Error path from the initial branch leads to Idle. The central path also includes a 'Set Error' block and a response message block (MAP_RELEASE_RESOURCES_rsp, MAP_CLOSE_req) before reaching the final Idle state.](16e669d3add13913a04db9fd11cb1834_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> Receive_Open_ind[Receive_Open_ind] + Receive_Open_ind --> Wait_For_Service_Indication[Wait_For_Service_Indication] + Receive_Open_ind --> Idle2[Idle] : Vr, Error + Wait_For_Service_Indication --> MAP_P_ABORT_ind[/MAP_P_ABORT_ind/] + Wait_For_Service_Indication --> MAP_RELEASE_RESOURCES_ind[MAP_RELEASE_RESOURCES_ind] + Wait_For_Service_Indication --> MAP_NOTICE_ind[/MAP_NOTICE_ind/] + MAP_P_ABORT_ind --> Idle3[Idle] + MAP_RELEASE_RESOURCES_ind --> Release_Resources[/Release Resources/] + Release_Resources --> Wait-For_Call_Handling_Response[Wait-For_Call_Handling_Response] + Wait-For_Call_Handling_Response --> Release_Resources_Ack[/Release Resources Ack/] + Wait-For_Call_Handling_Response --> Release_Resources_Negative_Response[/Release Resources negative response/] + Release_Resources_Negative_Response --> Set_Error[Set Error] + Set_Error --> MAP_RELEASE_RESOURCES_rsp[MAP_RELEASE_RESOURCES_rsp] + Set_Error --> MAP_CLOSE_req[MAP_CLOSE_req] + Release_Resources_Ack --> Idle4[Idle] + MAP_RELEASE_RESOURCES_rsp --> Idle4 + MAP_CLOSE_req --> Idle4 + MAP_NOTICE_ind --> MAP_CLOSE_req2[/MAP_CLOSE_req/] + MAP_CLOSE_req2 --> Idle5[Idle] + +``` + +State transition diagram for process Release\_Resources\_VMSC. It starts at an initial state, goes to Idle, then receives an Open\_ind. From there, it branches based on OK or Vr, Error. The OK path leads to Wait\_For\_Service\_Indication, which then branches into three paths: MAP\_P\_ABORT\_ind (leading to Idle), a central path with MAP\_RELEASE\_RESOURCES\_ind, Release Resources, Wait-For\_Call\_Handling\_Response, Release Resources Ack, and finally Idle; and a right path with MAP\_NOTICE\_ind, MAP\_CLOSE\_req, and Idle. The Vr, Error path from the initial branch leads to Idle. The central path also includes a 'Set Error' block and a response message block (MAP\_RELEASE\_RESOURCES\_rsp, MAP\_CLOSE\_req) before reaching the final Idle state. + +2781 + +2782 + +Figure 21.10/3: Process Release Resources\_VMSC + +--- + +## 22 Supplementary services procedures + +### 22.1 Supplementary service co-ordinator processes + +#### 22.1.1 Supplementary service co-ordinator process for the MSC + +The co-ordinator process in the MSC to handle a CM connection request with CM service type Supplementary service activation is shown in figure 22.1/1. The process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +Process\_Access\_Request\_MSC see clause 25.4.1. + +#### 22.1.2 Void + +#### 22.1.3 Functional supplementary service co-ordinator process for the HLR + +The MAP co-ordinator process in the HLR to handle a dialogue opened with the networkFunctionalSS application context is shown in figure 22.1/3. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +Receive\_Open\_Ind see clause 25.1.1. + +#### 22.1.4 Call completion supplementary service co-ordinator process for the HLR + +The MAP co-ordinator process in the HLR to handle a dialogue opened with the callCompletion application context is shown in figure 22.1/4. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +Receive\_Open\_Ind see clause 25.1.1. + +![Flowchart of process SS_Coordinator_MSC. It starts with an initial node, followed by 'Null', then 'A_CM_SERV_REQ' (CM Service type = Supplementary service activation), then 'Process_Access_Request_MSC'. From there, an 'OK' path leads to 'Wait_For_Service_Indication' and an 'Error' path leads to 'Null'. 'Wait_For_Service_Indication' branches into six parallel paths: 1. A_REGISTER_SS_ind -> Register_SS_MSC -> A_REGISTER_SS_ind; 2. A_ERASE_SS_ind -> Erase_SS_MSC -> A_ERASE_SS_ind; 3. A_ACTIVATE_SS_ind -> Activate_SS_MSC -> A_ACTIVATE_SS_ind; 4. A_DEACTIVATE_SS_ind -> Deactivate_SS_MSC -> A_DEACTIVATE_SS_ind; 5. A_INTERROGATE_SS_ind -> Interrogate_SS_MSC -> A_INTERROGATE_SS_ind; 6. A_REGISTER_PASSWORD_ind (From interworking function; see 3GPP TS 29.011) -> Register_Password_MSC -> A_REGISTER_PASSWORD_ind. All six paths converge to a final 'Relay_Info' node.](bdedf1de83edcaaff55b513dc0e077c5_img.jpg) + +process SS\_Coordinator\_MSC SSC\_MSC1(2) + +Supplementary service co-ordinating process in the MSC + +Signals to/from the left are to/from the MS; + signals to/from the right are to/from the child process unless shown otherwise + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> CM_REQ{A_CM_SERV_REQ} + CM_REQ --- CM_Type[CM Service type= Supplementary service activation] + CM_REQ --> ProcessAccess[Process_Access_Request_MSC] + ProcessAccess -- OK --> WaitForInd[Wait_For_Service_Indication] + ProcessAccess -- Error --> Null2([Null]) + WaitForInd --> RegisterInd{A_REGISTER_SS_ind} + WaitForInd --> EraseInd{A_ERASE_SS_ind} + WaitForInd --> ActivateInd{A_ACTIVATE_SS_ind} + WaitForInd --> DeactivateInd{A_DEACTIVATE_SS_ind} + WaitForInd --> InterrogateInd{A_INTERROGATE_SS_ind} + WaitForInd --> RegisterPasswordInd{A_REGISTER_PASSWORD_ind} + RegisterInd --> RegisterMSC[Register_SS_MSC] + RegisterMSC --> RegisterOut{A_REGISTER_SS_ind} + EraseInd --> EraseMSC[Erase_SS_MSC] + EraseMSC --> EraseOut{A_ERASE_SS_ind} + ActivateInd --> ActivateMSC[Activate_SS_MSC] + ActivateMSC --> ActivateOut{A_ACTIVATE_SS_ind} + DeactivateInd --> DeactivateMSC[Deactivate_SS_MSC] + DeactivateMSC --> DeactivateOut{A_DEACTIVATE_SS_ind} + InterrogateInd --> InterrogateMSC[Interrogate_SS_MSC] + InterrogateMSC --> InterrogateOut{A_INTERROGATE_SS_ind} + RegisterPasswordInd --- PasswordNote[From interworking function; see 3GPP TS 29.011] + RegisterPasswordInd --> RegisterPasswordMSC[Register_Password_MSC] + RegisterPasswordMSC --> RegisterPasswordOut{A_REGISTER_PASSWORD_ind} + RegisterOut --> RelayInfo([Relay_Info]) + EraseOut --> RelayInfo + ActivateOut --> RelayInfo + DeactivateOut --> RelayInfo + InterrogateOut --> RelayInfo + RegisterPasswordOut --> RelayInfo + +``` + +Flowchart of process SS\_Coordinator\_MSC. It starts with an initial node, followed by 'Null', then 'A\_CM\_SERV\_REQ' (CM Service type = Supplementary service activation), then 'Process\_Access\_Request\_MSC'. From there, an 'OK' path leads to 'Wait\_For\_Service\_Indication' and an 'Error' path leads to 'Null'. 'Wait\_For\_Service\_Indication' branches into six parallel paths: 1. A\_REGISTER\_SS\_ind -> Register\_SS\_MSC -> A\_REGISTER\_SS\_ind; 2. A\_ERASE\_SS\_ind -> Erase\_SS\_MSC -> A\_ERASE\_SS\_ind; 3. A\_ACTIVATE\_SS\_ind -> Activate\_SS\_MSC -> A\_ACTIVATE\_SS\_ind; 4. A\_DEACTIVATE\_SS\_ind -> Deactivate\_SS\_MSC -> A\_DEACTIVATE\_SS\_ind; 5. A\_INTERROGATE\_SS\_ind -> Interrogate\_SS\_MSC -> A\_INTERROGATE\_SS\_ind; 6. A\_REGISTER\_PASSWORD\_ind (From interworking function; see 3GPP TS 29.011) -> Register\_Password\_MSC -> A\_REGISTER\_PASSWORD\_ind. All six paths converge to a final 'Relay\_Info' node. + +2802 + +2803 + +Figure 22.1/1 (sheet 1 of 2): Process SS\_Coordinator\_MSC + +![Sequence diagram for process SS_Coordinator_MSC. The diagram shows the flow of signals and messages within the process. It starts with 'Wait_For_Service_Indication' leading to three parallel branches. The first branch involves 'A_CM_SERV_RELEASE_ind', 'MAP_U_ABORT_req' (leading to 'Application procedure cancellation'), 'A_CM_RELEASE_COMPLETE_req', and 'Null'. The second branch involves 'A_PROCESS_UNSTRUCTURED_SS_REQUEST_ind', 'MS_Init_USSD_MSC', 'A_PROCESS_UNSTRUCTURED_SS_REQUEST_ind', and 'Relay_Info'. The third branch involves an unlabeled merge node, 'A_CM_RELEASE_req', and 'Null'. All three branches converge to a second set of parallel branches. The first sub-branch has 'A_REL', 'A_REL', and 'Null'. The second sub-branch has an unlabeled merge node, an unlabeled message, and 'Relay_Info'. The third sub-branch has 'A_REL', 'A_REL', and 'Null'. The fourth sub-branch has an unlabeled merge node, an unlabeled message, and 'Relay_Info'.](4239623dc3aa0e3e90a1a7574869c9c6_img.jpg) + +process SS\_Coordinator\_MSC SSC\_MSC2(2) + +Supplementary service co-ordinating process in the MSC + +Signals to/from the left are to/from the MS; signals to/from the right are to/from the child process + +MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind + +``` + +sequenceDiagram + participant Wait_For_Service_Indication + Note left of Wait_For_Service_Indication: Supplementary service co-ordinating process in the MSC + Note right of Wait_For_Service_Indication: Signals to/from the left are to/from the MS; signals to/from the right are to/from the child process + Note right of Wait_For_Service_Indication: MAP_U_ABORT_ind, MAP_CLOSE_ind + + Wait_For_Service_Indication --> A_CM_SERV_RELEASE_ind + Wait_For_Service_Indication --> A_PROCESS_UNSTRUCTURED_SS_REQUEST_ind + Wait_For_Service_Indication --> Merge1(( )) + + A_CM_SERV_RELEASE_ind --> MAP_U_ABORT_req + MAP_U_ABORT_req --> Application_procedure_cancellation[Application procedure cancellation] + Application_procedure_cancellation --> A_CM_RELEASE_COMPLETE_req + A_CM_RELEASE_COMPLETE_req --> Null1(Null) + + A_PROCESS_UNSTRUCTURED_SS_REQUEST_ind --> MS_Init_USSD_MSC + MS_Init_USSD_MSC --> A_PROCESS_UNSTRUCTURED_SS_REQUEST_ind2[A_PROCESS_UNSTRUCTURED_SS_REQUEST_ind] + A_PROCESS_UNSTRUCTURED_SS_REQUEST_ind2 --> Relay_Info1(Relay_Info) + + Merge1 --> A_CM_RELEASE_req1[A_CM_RELEASE_req] + A_CM_RELEASE_req1 --> Null2(Null) + + Null1 --> Merge2(( )) + Relay_Info1 --> Merge2 + Null2 --> Merge2 + + Merge2 --> A_REL1[A_REL] + Merge2 --> Merge3(( )) + Merge2 --> A_REL2[A_REL] + Merge2 --> Merge4(( )) + + A_REL1 --> A_REL1_msg[A_REL] + A_REL1_msg --> Null3(Null) + + Merge3 --> Merge3_msg[-] + Merge3_msg --> Relay_Info2(Relay_Info) + + A_REL2 --> A_REL2_msg[A_REL] + A_REL2_msg --> Null4(Null) + + Merge4 --> Merge4_msg[-] + Merge4_msg --> Relay_Info3(Relay_Info) + +``` + +Sequence diagram for process SS\_Coordinator\_MSC. The diagram shows the flow of signals and messages within the process. It starts with 'Wait\_For\_Service\_Indication' leading to three parallel branches. The first branch involves 'A\_CM\_SERV\_RELEASE\_ind', 'MAP\_U\_ABORT\_req' (leading to 'Application procedure cancellation'), 'A\_CM\_RELEASE\_COMPLETE\_req', and 'Null'. The second branch involves 'A\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_ind', 'MS\_Init\_USSD\_MSC', 'A\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_ind', and 'Relay\_Info'. The third branch involves an unlabeled merge node, 'A\_CM\_RELEASE\_req', and 'Null'. All three branches converge to a second set of parallel branches. The first sub-branch has 'A\_REL', 'A\_REL', and 'Null'. The second sub-branch has an unlabeled merge node, an unlabeled message, and 'Relay\_Info'. The third sub-branch has 'A\_REL', 'A\_REL', and 'Null'. The fourth sub-branch has an unlabeled merge node, an unlabeled message, and 'Relay\_Info'. + +2804 + +2805 + +Figure 22.1/1 (sheet 2 of 2): Process SS\_Coordinator\_MSC + +2806 + +Figure 22.1/2 void + +![Flowchart for process SS_Coordinator_HLR. It starts with a Null state, followed by Receive_Open_Ind. A decision point 'OK' leads to Wait_For_Service_Indication, which then branches into six parallel MAP operations: REGISTER, ERASE, ACTIVATE, DEACTIVATE, INTERROGATE, and REGISTER PASSWORD. These lead to a Relay_Info state. From Relay_Info, it branches into four paths: one with MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind leading to Null; one with a '*' symbol leading to Relay_Info; one with MAP_U_ABORT_req, MAP_CLOSE_req leading to Null; and one with a '-' symbol leading to Relay_Info. All four paths converge to a Wait_For_Service_Indication state, which then branches into MAP_NOTICE_ind and MAP_CLOSE_req leading to Null, and another path with MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind leading to Null.](26f743627a63ee4e129d3afd6ba69c6c_img.jpg) + +**process SS\_Coordinator\_HLR** **SSC\_HLR1(1)** + +Supplementary service co-ordinating process in the HLR + +Signals to/from the left are to/from the VLR; +signals to/from the right are to/from the child process + +``` + + graph TD + Start([Null]) --> RecOpen[Receive_Open_Ind] + RecOpen --> Decision1{ } + Decision1 -- Error --> Null1([Null]) + Decision1 -- OK --> WaitF1[Wait_For_Service_Indication] + Decision1 -- Vr --> PerformMAP[Perform MAP Vr dialogue] + PerformMAP --> Null2([Null]) + + WaitF1 --> MAP_REG[MAP_REGISTER_SS_ind] + WaitF1 --> MAP_ERASE[MAP_ERASE_SS_ind] + WaitF1 --> MAP_ACTIVATE[MAP_ACTIVATE_SS_ind] + WaitF1 --> MAP_DEACTIVATE[MAP_DEACTIVATE_SS_ind] + WaitF1 --> MAP_INTERROGATE[MAP_INTERROGATE_SS_ind] + WaitF1 --> MAP_REG_PWD[MAP_REGISTER_PASSWORD_ind] + + MAP_REG --> RegHLR[Register_SS_HLR] + MAP_ERASE --> EraseHLR[Erase_SS_HLR] + MAP_ACTIVATE --> ActivateHLR[Activate_SS_HLR] + MAP_DEACTIVATE --> DeactivateHLR[Deactivate_SS_HLR] + MAP_INTERROGATE --> InterrogateHLR[Interrogate_SS_HLR] + MAP_REG_PWD --> RegPwdHLR[Register_Password_HLR] + + RegHLR --> MAP_REG_OUT[MAP_REGISTER_SS_ind] + EraseHLR --> MAP_ERASE_OUT[MAP_ERASE_SS_ind] + ActivateHLR --> MAP_ACTIVATE_OUT[MAP_ACTIVATE_SS_ind] + DeactivateHLR --> MAP_DEACTIVATE_OUT[MAP_DEACTIVATE_SS_ind] + InterrogateHLR --> MAP_INTERROGATE_OUT[MAP_INTERROGATE_SS_ind] + RegPwdHLR --> MAP_REG_PWD_OUT[MAP_REGISTER_PASSWORD_ind] + + MAP_REG_OUT --> RelayInfo1[Relay_Info] + MAP_ERASE_OUT --> RelayInfo1 + MAP_ACTIVATE_OUT --> RelayInfo1 + MAP_DEACTIVATE_OUT --> RelayInfo1 + MAP_INTERROGATE_OUT --> RelayInfo1 + MAP_REG_PWD_OUT --> RelayInfo1 + + RelayInfo1 --> MAP_P_ABORT[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] + MAP_P_ABORT --> Null3([Null]) + + RelayInfo1 --> Star[*] + Star --> Null4([Null]) + + RelayInfo1 --> MAP_U_ABORT[MAP_U_ABORT_req, MAP_CLOSE_req] + MAP_U_ABORT --> Null5([Null]) + + RelayInfo1 --> Dash[-] + Dash --> Null6([Null]) + + Null3 --> WaitF2[Wait_For_Service_Indication] + Null4 --> WaitF2 + Null5 --> WaitF2 + Null6 --> WaitF2 + + WaitF2 --> MAP_NOTICE[MAP_NOTICE_ind] + MAP_NOTICE --> MAP_CLOSE[MAP_CLOSE_req] + MAP_CLOSE --> Null7([Null]) + + WaitF2 --> MAP_P_ABORT2[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] + MAP_P_ABORT2 --> Null8([Null]) + +``` + +Flowchart for process SS\_Coordinator\_HLR. It starts with a Null state, followed by Receive\_Open\_Ind. A decision point 'OK' leads to Wait\_For\_Service\_Indication, which then branches into six parallel MAP operations: REGISTER, ERASE, ACTIVATE, DEACTIVATE, INTERROGATE, and REGISTER PASSWORD. These lead to a Relay\_Info state. From Relay\_Info, it branches into four paths: one with MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind leading to Null; one with a '\*' symbol leading to Relay\_Info; one with MAP\_U\_ABORT\_req, MAP\_CLOSE\_req leading to Null; and one with a '-' symbol leading to Relay\_Info. All four paths converge to a Wait\_For\_Service\_Indication state, which then branches into MAP\_NOTICE\_ind and MAP\_CLOSE\_req leading to Null, and another path with MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind leading to Null. + +2807 + +2808 + +Figure 22.1/3: Process SS\_Coordinator\_HLR + +![Flowchart for process CC_Coordinator_HLR. It starts with an initial state leading to 'Null', then 'Receive_Open_Ind'. From 'Receive_Open_Ind', an 'OK' path leads to 'Wait_For_Service_Indication' and a 'Vr, Error' path leads to 'Null'. 'Wait_For_Service_Indication' branches into four paths: 1) 'MAP_REGISTER_CC_ENTRY_ind' -> 'Register_CC_Entry_HLR' -> 'MAP_REGISTER_CC_ENTRY_ind' -> 'Relay_Info'; 2) 'MAP_ERASE_CC_ENTRY_ind' -> 'Erase_CC_Entry_HLR' -> 'MAP_ERASE_CC_ENTRY_ind' -> 'Relay_Info'; 3) 'MAP_NOTICE_ind' -> 'MAP_CLOSE_req' -> 'Null'; 4) an unlabeled path leading to a box with 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' -> 'Null'. All four paths converge to a 'Relay_Info' state. From 'Relay_Info', four paths emerge: 1) an unlabeled path -> a box with 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' -> a box with '-' -> 'Null'; 2) a path with '*' -> a box with '-' -> 'Relay_Info'; 3) a path with '-' -> a box with '-' -> 'Null'; 4) a path with '*' -> a box with 'MAP_U_ABORT_req, MAP_CLOSE_req' -> a box with '-' -> 'Relay_Info'.](c70920fb7053af492e6b0a7f14ce0ccd_img.jpg) + +**process CC\_Coordinator\_HLR** **CCC\_HLR1(1)** + +Call Completion co-ordinating process in the HLR + +Signals to/from the left are to/from the VLR; + signals to/from the right are to/from the child process + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind -- OK --> Wait_For_Service_Indication([Wait_For_Service_Indication]) + Receive_Open_Ind -- "Vr, Error" --> Null2([Null]) + + Wait_For_Service_Indication --> MAP_REGISTER_CC_ENTRY_ind[/MAP_REGISTER_CC_ENTRY_ind/] + Wait_For_Service_Indication --> MAP_ERASE_CC_ENTRY_ind[/MAP_ERASE_CC_ENTRY_ind/] + Wait_For_Service_Indication --> MAP_NOTICE_ind[/MAP_NOTICE_ind/] + + MAP_REGISTER_CC_ENTRY_ind --> Register_CC_Entry_HLR[Register_CC_Entry_HLR] + Register_CC_Entry_HLR --> MAP_REGISTER_CC_ENTRY_ind2[/MAP_REGISTER_CC_ENTRY_ind/] + + MAP_ERASE_CC_ENTRY_ind --> Erase_CC_Entry_HLR[Erase_CC_Entry_HLR] + Erase_CC_Entry_HLR --> MAP_ERASE_CC_ENTRY_ind2[/MAP_ERASE_CC_ENTRY_ind/] + + MAP_NOTICE_ind --> MAP_CLOSE_req{MAP_CLOSE_req} + + MAP_CLOSE_req --> Null3([Null]) + + MAP_CLOSE_req --> Unlabeled1[ ] + Unlabeled1 --> MAP_P_ABORT_ind[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] + + MAP_REGISTER_CC_ENTRY_ind2 --> Relay_Info1([Relay_Info]) + MAP_ERASE_CC_ENTRY_ind2 --> Relay_Info1 + + Relay_Info1 --> Unlabeled2[ ] + Unlabeled2 --> MAP_P_ABORT_ind2[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] + + Relay_Info1 --> Star1[*] + Star1 --> Dash1[ ] + + Relay_Info1 --> Dash2[ ] + + Relay_Info1 --> Star2[*] + Star2 --> MAP_U_ABORT_req[MAP_U_ABORT_req, MAP_CLOSE_req] + + MAP_P_ABORT_ind2 --> Dash3[ ] + Dash3 --> Null4([Null]) + + Dash1 --> Dash4[ ] + Dash4 --> Relay_Info2([Relay_Info]) + + Dash2 --> Dash5[ ] + Dash5 --> Null5([Null]) + + MAP_U_ABORT_req --> Dash6[ ] + Dash6 --> Relay_Info3([Relay_Info]) + +``` + +Flowchart for process CC\_Coordinator\_HLR. It starts with an initial state leading to 'Null', then 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', an 'OK' path leads to 'Wait\_For\_Service\_Indication' and a 'Vr, Error' path leads to 'Null'. 'Wait\_For\_Service\_Indication' branches into four paths: 1) 'MAP\_REGISTER\_CC\_ENTRY\_ind' -> 'Register\_CC\_Entry\_HLR' -> 'MAP\_REGISTER\_CC\_ENTRY\_ind' -> 'Relay\_Info'; 2) 'MAP\_ERASE\_CC\_ENTRY\_ind' -> 'Erase\_CC\_Entry\_HLR' -> 'MAP\_ERASE\_CC\_ENTRY\_ind' -> 'Relay\_Info'; 3) 'MAP\_NOTICE\_ind' -> 'MAP\_CLOSE\_req' -> 'Null'; 4) an unlabeled path leading to a box with 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' -> 'Null'. All four paths converge to a 'Relay\_Info' state. From 'Relay\_Info', four paths emerge: 1) an unlabeled path -> a box with 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' -> a box with '-' -> 'Null'; 2) a path with '\*' -> a box with '-' -> 'Relay\_Info'; 3) a path with '-' -> a box with '-' -> 'Null'; 4) a path with '\*' -> a box with 'MAP\_U\_ABORT\_req, MAP\_CLOSE\_req' -> a box with '-' -> 'Relay\_Info'. + +2809 + +2810 + +**Figure 22.1/4: Process CC\_Coordinator\_HLR** + +## 22.2 Registration procedure + +### 22.2.1 General + +The registration procedure is used to register data related to a supplementary service in the HLR. The registration procedure is a fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of the procedure, as described in the clauses below. + +The registration procedure is shown in figure 22.2.1/1. + +The following services may be used: + +- MAP\_PROCESS\_ACCESS\_REQUEST (see clauses 8 and 25); +- MAP\_TRACE\_SUBSCRIBER\_ACTIVITY (see clauses 9 and 25); +- MAP\_PROVIDE\_IMSI (see clauses 8 and 25); +- MAP\_FORWARD\_NEW\_TMSI (see clauses 8 and 25); +- MAP\_AUTHENTICATE (see clauses 8 and 25); +- MAP\_SET\_CIPHERING\_MODE (see clauses 8 and 25); +- MAP\_CHECK\_IMEI (see clauses 8 and 25); +- MAP\_READY\_FOR\_SM (see clauses 12 and 25); +- MAP\_INSERT\_SUBSCRIBER\_DATA (see clauses 8 and 25); + +The following service is certainly used: + +- MAP\_REGISTER\_SS (defined in clause 11). + +![Sequence diagram showing the registration procedure between MS, MSC, VLR, and HLR. The diagram consists of four lifelines: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends A_CM_SERV_REQ to MSC; 2. MSC sends MAP_PROCESS_ACCESS_REQUEST to VLR; 3. MS sends A_REGISTER_SS to MSC; 4. MSC sends MAP_REGISTER_SS_req/ind to VLR; 5. VLR sends MAP_REGISTER_SS_req/ind to HLR; 6. HLR sends MAP_REGISTER_SS_rsp/cnf to VLR; 7. VLR sends MAP_REGISTER_SS_rsp/cnf to MSC; 8. MSC sends A_REGISTER_SS ack to MS; 9. VLR sends MAP_INSERT_SUBSCRIBER_DATA_req/ind to HLR; 10. HLR sends MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf to VLR.](020a8313c255e32fd3c32d21526de441_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note left of MS: 1) A_CM_SERV_REQ (Note 1) + MS->>MSC: 1) A_CM_SERV_REQ (Note 1) + Note right of MSC: 2) MAP_PROCESS_ACCESS_REQUEST (Note 2) + MSC->>VLR: 2) MAP_PROCESS_ACCESS_REQUEST (Note 2) + Note left of MS: 3) A_REGISTER_SS (Note 1) + MS->>MSC: 3) A_REGISTER_SS (Note 1) + Note right of MSC: 4) MAP_REGISTER_SS_req/ind + MSC->>VLR: 4) MAP_REGISTER_SS_req/ind + Note right of VLR: 5) MAP_REGISTER_SS_req/ind + VLR->>HLR: 5) MAP_REGISTER_SS_req/ind + Note right of HLR: 6) MAP_REGISTER_SS_rsp/cnf + HLR->>VLR: 6) MAP_REGISTER_SS_rsp/cnf + Note right of VLR: 7) MAP_REGISTER_SS_rsp/cnf + VLR->>MSC: 7) MAP_REGISTER_SS_rsp/cnf + Note left of MSC: 8) A_REGISTER_SS ack (Note 1) + MSC->>MS: 8) A_REGISTER_SS ack (Note 1) + Note right of VLR: 9) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3) + VLR->>HLR: 9) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3) + Note right of HLR: 10) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3) + HLR->>VLR: 10) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3) + +``` + +Sequence diagram showing the registration procedure between MS, MSC, VLR, and HLR. The diagram consists of four lifelines: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends A\_CM\_SERV\_REQ to MSC; 2. MSC sends MAP\_PROCESS\_ACCESS\_REQUEST to VLR; 3. MS sends A\_REGISTER\_SS to MSC; 4. MSC sends MAP\_REGISTER\_SS\_req/ind to VLR; 5. VLR sends MAP\_REGISTER\_SS\_req/ind to HLR; 6. HLR sends MAP\_REGISTER\_SS\_rsp/cnf to VLR; 7. VLR sends MAP\_REGISTER\_SS\_rsp/cnf to MSC; 8. MSC sends A\_REGISTER\_SS ack to MS; 9. VLR sends MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind to HLR; 10. HLR sends MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf to VLR. + +- 1) A\_CM\_SERV\_REQ (Note 1) +- 2) MAP\_PROCESS\_ACCESS\_REQUEST (Note 2) +- 3) A\_REGISTER\_SS (Note 1) +- 4) MAP\_REGISTER\_SS\_req/ind +- 5) MAP\_REGISTER\_SS\_req/ind +- 6) MAP\_REGISTER\_SS\_rsp/cnf +- 7) MAP\_REGISTER\_SS\_rsp/cnf +- 8) A\_REGISTER\_SS ack (Note 1) +- 9) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind (Note 3) +- 10) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf (Note 3) + +2842 NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS +2843 24.08x and 3GPP TS 24.09x. Services shown in dotted lines indicate the trigger provided by the signalling +2844 on the radio path, and the signalling triggered on the radio path. +2845 NOTE 2: For details of the Process Access Request procedure, refer to clause 25.4 in the present document. +2846 NOTE 3: Services printed in *italics* are optional. +2847 +2848 **Figure 22.2.1/1: Message flow for supplementary service registration** + +## 2849 22.2.2 Procedure in the MSC + +2850 The A\_REGISTER\_SS service indication received by the MAP process in the MSC contains the SS-Code and any +2851 parameters that are related to the supplementary service. + +2852 The MAP user transfers the received information to the VLR in the MAP\_REGISTER\_SS request without checking the +2853 contents of the service indication. Rules for the mapping are described in 3GPP TS 29.011 [59]. + +2854 The information in the MAP\_REGISTER\_SS confirm from the VLR is relayed to the MS in the A\_REGISTER\_SS +2855 response message as described in 3GPP TS 24.08x, 3GPP TS 24.08x and 3GPP TS 29.011. + +2856 For call independent SS operations, each message shall contain only a single component. Messages which contain more +2857 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). + +2858 The registration process in the MSC is shown in figure 22.2.2/1. + +## 2859 22.2.3 Procedure in the VLR + +2860 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +2861 *Receive\_Open\_Ind* see clause 25.1.1; + +2862 *Receive\_Open\_Cnf* see clause 25.1.2; + +2863 *Check Confirmation* see clause 25.2.2; + +2864 *Process\_Access\_Request\_VLR* see clause 25.4.2. + +2865 The MAP process in the VLR transfers the information received in the MAP\_REGISTER\_SS indication to the HLR in +2866 the MAP\_REGISTER\_SS request without checking the contents. The MAP\_OPEN request includes the IMSI of the +2867 subscriber as the destination reference and the VLR number as the originating reference. + +2868 If the MAP\_REGISTER\_SS confirm is properly formed and contains a result or a user error, the MAP process in the +2869 VLR shall transfer the information contained in this primitive to the MSC in the MAP\_REGISTER\_SS response. + +2870 For call independent SS operations, each message shall contain only a single component. Messages which contain more +2871 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). + +2872 The registration process in the VLR is shown in figure 22.2.3/1. + +## 2873 22.2.4 Procedure in the HLR + +2874 The MAP process invokes a macro and a process not defined in this clause; the definitions of the macro and process can +2875 be found as follows: + +2876 *Check\_Indication* see clause 25.2.1; + +2877 *Insert\_Subs\_Data\_Stand\_Alone\_HLR* see clause 25.7.3. + +2878 The supplementary service request shall be processed according to 3GPP TS 23.011 [22] and the 23.08x and 23.09x- +2879 series of technical specifications. This handling may lead to a successful result, a partially successful result or an error +2880 being returned. + +2881 For call independent SS operations, each message shall contain only a single component. Messages which contain more +2882 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). + +2883 The registration process in the HLR is shown in figure 22.2.4/1. + +![SDL diagram for process Register_SS_MSC. It shows state transitions and signal exchanges between the MSC and VLR for supplementary service registration. Key states include 'Null' and 'Wait_For_Register_SS_Confirm'. Signals include A_REGISTER_SS_ind, MAP_REGISTER_SS_req, MAP_REGISTER_SS_cnf, and various abort/release signals.](570c644e6b2f2bdf49ec9e1b4eb4b626_img.jpg) + +**process Register\_SS\_MSC** **RSS\_MSC1(1)** + +Process in the MSC to handle a request to register data for a supplementary service + +Signals to/from the left are to/from the SS co-ordinating process in the MSC; signals to/from the right are to/from the VLR + + + +``` + + graph TD + Start([ ]) --> Null[Null] + Null --> A_CM_SERV_RELEASE_ind_1{A_CM_SERV_RELEASE_ind} + Null --> A_REGISTER_SS_ind_1{A_REGISTER_SS_ind} + Null --> MAP_ABORT_CLOSE_ind_1{MAP_U_ABORT_ind, +MAP_CLOSE_ind} + + A_CM_SERV_RELEASE_ind_1 --> MAP_U_ABORT_req_1[/MAP_U_ABORT_req/] + MAP_U_ABORT_req_1 -- Application procedure cancellation --> A_CM_RELEASE_COMPLETE_req_1[/A_CM_RELEASE_COMPLETE_req/] + A_CM_RELEASE_COMPLETE_req_1 --> Term1((X)) + + A_REGISTER_SS_ind_1 --> MAP_REG_DELIM_req[/MAP_REGISTER_SS_req, +MAP_DELIMITER_req/] + MAP_REG_DELIM_req --> Wait_For_SS_Confirm[Wait_For_Register_SS_Confirm] + + MAP_ABORT_CLOSE_ind_1 --> A_CM_RELEASE_req_1[/A_CM_RELEASE_req/] + A_CM_RELEASE_req_1 --> Term2((X)) + + Wait_For_SS_Confirm --> A_CM_SERV_RELEASE_ind_2{A_CM_SERV_RELEASE_ind} + Wait_For_SS_Confirm --> MAP_REGISTER_SS_cnf_1{MAP_REGISTER_SS_cnf} + Wait_For_SS_Confirm --> MAP_ABORT_CLOSE_ind_2{MAP_U_ABORT_ind, +MAP_CLOSE_ind} + + A_CM_SERV_RELEASE_ind_2 --> MAP_U_ABORT_req_2[/MAP_U_ABORT_req/] + MAP_U_ABORT_req_2 -- Application procedure cancellation --> A_CM_RELEASE_COMPLETE_req_2[/A_CM_RELEASE_COMPLETE_req/] + A_CM_RELEASE_COMPLETE_req_2 --> Term3((X)) + + MAP_REGISTER_SS_cnf_1 --> A_REG_SS_rsp_RELEASE_req[/A_REGISTER_SS_rsp, +A_CM_RELEASE_req/] + A_REG_SS_rsp_RELEASE_req --> Term4((X)) + + MAP_ABORT_CLOSE_ind_2 --> A_CM_RELEASE_req_2[/A_CM_RELEASE_req/] + A_CM_RELEASE_req_2 --> Term5((X)) + +``` + +SDL diagram for process Register\_SS\_MSC. It shows state transitions and signal exchanges between the MSC and VLR for supplementary service registration. Key states include 'Null' and 'Wait\_For\_Register\_SS\_Confirm'. Signals include A\_REGISTER\_SS\_ind, MAP\_REGISTER\_SS\_req, MAP\_REGISTER\_SS\_cnf, and various abort/release signals. + +2884 + +2885 + +Figure 22.2.2/1: Process Register\_SS\_MSC + +![Flowchart for process Register_SS_VLR. The process starts at an oval, goes to 'Null', then 'Receive_Open_Ind'. From 'Receive_Open_Ind', 'OK' leads to 'Wait_For_PAR' and 'Vr, Error' leads to 'Null'. 'Wait_For_PAR' leads to a junction. One path goes left to a chevron, then 'MAP_U_ABORT_ind, MAP_CLOSE_ind', then 'Null'. The other path goes right to 'Process_Access_Request_VLR'. From 'Process_Access_Request_VLR', 'OK' leads to 'Wait_For_Register_SS_Request' and 'Error' leads to 'Null'. 'Wait_For_Register_SS_Request' leads to 'MAP_REGISTER_SS_ind'. 'MAP_REGISTER_SS_ind' leads to a junction. One path goes right to 'MAP_OPEN_req, MAP_REGISTER_SS_req, MAP_DELIMITER_req', then to 'Receive_Open_Cnf'. 'Receive_Open_Cnf' has three outputs: 'Error' leads to 'MAP_U_ABORT_req' then 'Null'; 'OK' leads to 'Wait_For_Register_SS_Confirm'; 'Vr' leads to 'Perform MAP Vr dialogue' then 'Null'.](ad98c332aee74f5ad3f274a2b22dfee5_img.jpg) + +**process Register\_SS\_VLR** **RSS\_VLR1(2)** + +Process in the VLR to handle a request to register data for a supplementary service + +Signals to/from the left are to/from the MSC; +signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind -- "OK" --> Wait_For_PAR([Wait_For_PAR]) + Receive_Open_Ind -- "Vr, Error" --> Null2([Null]) + Wait_For_PAR --> Junction1(( )) + Junction1 --> Chevron1{ } + Chevron1 --> MAP_U_ABORT_ind[MAP_U_ABORT_ind, MAP_CLOSE_ind] + MAP_U_ABORT_ind --> Null3([Null]) + Junction1 --> Process_Access_Request_VLR[Process_Access_Request_VLR] + Process_Access_Request_VLR -- "OK" --> Wait_For_Register_SS_Request([Wait_For_Register_SS_Request]) + Process_Access_Request_VLR -- "Error" --> Null4([Null]) + Wait_For_Register_SS_Request --> MAP_REGISTER_SS_ind[MAP_REGISTER_SS_ind] + MAP_REGISTER_SS_ind --> Junction2(( )) + Junction2 --> MAP_OPEN_req[MAP_OPEN_req, MAP_REGISTER_SS_req, MAP_DELIMITER_req] + MAP_OPEN_req --> Receive_Open_Cnf[Receive_Open_Cnf] + Receive_Open_Cnf -- "Error" --> MAP_U_ABORT_req{MAP_U_ABORT_req} + MAP_U_ABORT_req --> Null5([Null]) + Receive_Open_Cnf -- "OK" --> Wait_For_Register_SS_Confirm([Wait_For_Register_SS_Confirm]) + Receive_Open_Cnf -- "Vr" --> Perform_MAP_Vr_dialogue[Perform MAP Vr dialogue] + Perform_MAP_Vr_dialogue --> Null6([Null]) + +``` + +Flowchart for process Register\_SS\_VLR. The process starts at an oval, goes to 'Null', then 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', 'OK' leads to 'Wait\_For\_PAR' and 'Vr, Error' leads to 'Null'. 'Wait\_For\_PAR' leads to a junction. One path goes left to a chevron, then 'MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind', then 'Null'. The other path goes right to 'Process\_Access\_Request\_VLR'. From 'Process\_Access\_Request\_VLR', 'OK' leads to 'Wait\_For\_Register\_SS\_Request' and 'Error' leads to 'Null'. 'Wait\_For\_Register\_SS\_Request' leads to 'MAP\_REGISTER\_SS\_ind'. 'MAP\_REGISTER\_SS\_ind' leads to a junction. One path goes right to 'MAP\_OPEN\_req, MAP\_REGISTER\_SS\_req, MAP\_DELIMITER\_req', then to 'Receive\_Open\_Cnf'. 'Receive\_Open\_Cnf' has three outputs: 'Error' leads to 'MAP\_U\_ABORT\_req' then 'Null'; 'OK' leads to 'Wait\_For\_Register\_SS\_Confirm'; 'Vr' leads to 'Perform MAP Vr dialogue' then 'Null'. + +2886 + +2887 + +**Figure 22.2.3/1 (sheet 1 of 2): Process Register\_SS\_VLR** + +![State transition diagram for process Register_SS_VLR. It starts at 'Wait_For_Register_SS_Confirm' and branches into four main paths based on incoming indications: MAP_U_ABORT_ind/MAP_CLOSE_ind, MAP_REGISTER_SS_cnf, MAP_NOTICE_ind, and MAP_P_ABORT_ind/MAP_U_ABORT_ind/MAP_CLOSE_ind. Each path leads to specific requests and eventually to a 'Null' state.](c620ea4d9898d79f8c56cbe446f91bd4_img.jpg) + +**process Register\_SS\_VLR** **RSS\_VLR2(2)** + +Process in the VLR to handle a request to register data for a supplementary service + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Wait_For_Register_SS_Confirm + state "Wait_For_Register_SS_Confirm" as Wait_For_Register_SS_Confirm + state "Null" as Null + state "Check_Confirmation" as Check_Confirmation + state "MAP_REGISTER_SS_rsp / MAP_CLOSE_req" as MAP_REGISTER_SS_rsp_MAP_CLOSE_req + + Wait_For_Register_SS_Confirm --> MAP_U_ABORT_ind_in + Wait_For_Register_SS_Confirm --> MAP_REGISTER_SS_cnf_in + Wait_For_Register_SS_Confirm --> MAP_NOTICE_ind_in + Wait_For_Register_SS_Confirm --> MAP_P_ABORT_ind_in + + state "MAP_U_ABORT_ind, MAP_CLOSE_ind" as MAP_U_ABORT_ind_in + state "MAP_REGISTER_SS_cnf" as MAP_REGISTER_SS_cnf_in + state "MAP_NOTICE_ind" as MAP_NOTICE_ind_in + state "MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind" as MAP_P_ABORT_ind_in + + MAP_U_ABORT_ind_in --> MAP_U_ABORT_req + MAP_REGISTER_SS_cnf_in --> Check_Confirmation + MAP_NOTICE_ind_in --> MAP_CLOSE_req + MAP_P_ABORT_ind_in --> MAP_U_ABORT_req + + state "MAP_U_ABORT_req" as MAP_U_ABORT_req + state "MAP_CLOSE_req" as MAP_CLOSE_req + + Check_Confirmation --> OK_User_Error_Data_Error + Check_Confirmation --> Provider_Error + + state "OK, User Error, Data Error" as OK_User_Error_Data_Error + state "Provider Error" as Provider_Error + + OK_User_Error_Data_Error --> MAP_REGISTER_SS_rsp_MAP_CLOSE_req + Provider_Error --> MAP_U_ABORT_req + + MAP_U_ABORT_req --> Null + MAP_REGISTER_SS_rsp_MAP_CLOSE_req --> Null + MAP_CLOSE_req --> Null + +``` + +State transition diagram for process Register\_SS\_VLR. It starts at 'Wait\_For\_Register\_SS\_Confirm' and branches into four main paths based on incoming indications: MAP\_U\_ABORT\_ind/MAP\_CLOSE\_ind, MAP\_REGISTER\_SS\_cnf, MAP\_NOTICE\_ind, and MAP\_P\_ABORT\_ind/MAP\_U\_ABORT\_ind/MAP\_CLOSE\_ind. Each path leads to specific requests and eventually to a 'Null' state. + +2888 + +2889 + +Figure 22.2.3/1 (sheet 2 of 2): Process Register\_SS\_VLR + +![Flowchart for process Register_SS_HLR. It starts with an oval, followed by a 'Null' block, then 'MAP_REGISTER_SS_ind'. A decision 'OK' leads to 'Check_Indication'. From 'Check_Indication', 'Yes' leads to 'Operator Determined Barring of SS management?' and 'No' leads to 'SS request'. 'Operator Determined Barring of SS management?' leads to 'Set User Error: Call barred' and 'Call barring cause= Operator barring', which then lead to 'MAP_REGISTER_SS_rsp' and 'MAP_CLOSE_req'. 'SS request' leads to 'Wait_For_Application_Response'. From 'Wait_For_Application_Response', five paths emerge: 'acknowledge', 'partial acceptance', 'error', 'MAP_NOTICE_ind', and an unlabeled path leading to 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind'. 'acknowledge', 'partial acceptance', and 'error' lead to 'Set Result', 'Set User Error', and 'MAP_U_ABORT_req' respectively. 'MAP_NOTICE_ind' leads to 'MAP_U_ABORT_req'. All three lead to a merge point. From the merge point, 'MAP_REGISTER_SS_rsp' and 'MAP_CLOSE_req' are sent. A decision 'Update of subs data required in VLR?' follows. 'Yes' leads to 'Insert Subs_Data Stand_Alone_HLR'. Both 'No' and 'Insert Subs_Data Stand_Alone_HLR' lead to an exit point marked with an 'X'. There are also exit points marked with 'X' on the left and right sides of the diagram.](15907527acdc7018da2e4a290405cb8a_img.jpg) + +**process Register\_SS\_HLR** **RSS\_HLR1(1)** + +Process in the HLR to handle a request to register data for a supplementary service + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the process SS\_REQUEST\_WITH\_BS\_GROUP (see 3GPP TS 23.011) + +``` + + graph TD + Start([ ]) --> Null[Null] + Null --> MAP_REGISTER_SS_ind[/MAP_REGISTER_SS_ind/] + MAP_REGISTER_SS_ind --> Check_Indication[Check_Indication] + Check_Indication -- Yes --> Operator_Determined[Operator Determined Barring of SS management?] + Check_Indication -- No --> SS_request[/SS request/] + + Operator_Determined --> Set_User_Error[Set User Error: Call barred] + Set_User_Error --> Call_barring_cause[Call barring cause= Operator barring] + + SS_request --> Wait_For_Application_Response[Wait_For_Application_Response] + + Wait_For_Application_Response -- acknowledge --> Set_Result[Set Result] + Wait_For_Application_Response -- partial acceptance --> Set_Result + Wait_For_Application_Response -- error --> Set_User_Error_2[Set User Error] + Wait_For_Application_Response -- MAP_NOTICE_ind[/MAP_NOTICE_ind/] --> MAP_U_ABORT_req[/MAP_U_ABORT_req/] + + Set_Result --> Merge1(( )) + Set_User_Error_2 --> Merge1 + MAP_U_ABORT_req --> Merge1 + + Merge1 --> MAP_REGISTER_SS_rsp[MAP_REGISTER_SS_rsp] + Merge1 --> MAP_CLOSE_req[MAP_CLOSE_req] + + MAP_REGISTER_SS_rsp --> Update_of_subs_data{Update of subs data required in VLR?} + MAP_CLOSE_req --> Update_of_subs_data + + Update_of_subs_data -- Yes --> Insert_Subs_Data[Insert Subs_Data Stand_Alone_HLR] + + Insert_Subs_Data --> Exit1((X)) + Update_of_subs_data -- No --> Exit1 + + Exit2((X)) --> MAP_REGISTER_SS_rsp + MAP_REGISTER_SS_rsp --> Exit2 + + MAP_P_ABORT_ind[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] --> Exit3((X)) + +``` + +Flowchart for process Register\_SS\_HLR. It starts with an oval, followed by a 'Null' block, then 'MAP\_REGISTER\_SS\_ind'. A decision 'OK' leads to 'Check\_Indication'. From 'Check\_Indication', 'Yes' leads to 'Operator Determined Barring of SS management?' and 'No' leads to 'SS request'. 'Operator Determined Barring of SS management?' leads to 'Set User Error: Call barred' and 'Call barring cause= Operator barring', which then lead to 'MAP\_REGISTER\_SS\_rsp' and 'MAP\_CLOSE\_req'. 'SS request' leads to 'Wait\_For\_Application\_Response'. From 'Wait\_For\_Application\_Response', five paths emerge: 'acknowledge', 'partial acceptance', 'error', 'MAP\_NOTICE\_ind', and an unlabeled path leading to 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind'. 'acknowledge', 'partial acceptance', and 'error' lead to 'Set Result', 'Set User Error', and 'MAP\_U\_ABORT\_req' respectively. 'MAP\_NOTICE\_ind' leads to 'MAP\_U\_ABORT\_req'. All three lead to a merge point. From the merge point, 'MAP\_REGISTER\_SS\_rsp' and 'MAP\_CLOSE\_req' are sent. A decision 'Update of subs data required in VLR?' follows. 'Yes' leads to 'Insert Subs\_Data Stand\_Alone\_HLR'. Both 'No' and 'Insert Subs\_Data Stand\_Alone\_HLR' lead to an exit point marked with an 'X'. There are also exit points marked with 'X' on the left and right sides of the diagram. + +2890 + +2891 + +Figure 22.2.4/1: Process Register\_SS\_HLR + +## 22.3 Erasure procedure + +### 22.3.1 General + +The erasure procedure is used to erase data related to a supplementary service in the HLR. The erasure procedure is a fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of the procedure, as described in the clauses below. + +The erasure procedure is shown in figure 22.3.1/1. + +The following services may be used: + +- MAP\_PROCESS\_ACCESS\_REQUEST (see clauses 8 and 25); +- MAP\_TRACE\_SUBSCRIBER\_ACTIVITY (see clauses 9 and 25); +- MAP\_PROVIDE\_IMSI (see clauses 8 and 25); +- MAP\_FORWARD\_NEW\_TMSI (see clauses 8 and 25); +- MAP\_AUTHENTICATE (see clauses 8 and 25); +- MAP\_SET\_CIPHERING\_MODE (see clauses 8 and 25); +- MAP\_CHECK\_IMEI (see clauses 8 and 25); +- MAP\_READY\_FOR\_SM (see clauses 12 and 25); +- MAP\_INSERT\_SUBSCRIBER\_DATA (see clauses 8 and 25); + +The following service is certainly used: + +- MAP\_ERASE\_SS (defined in clause 11). + +![Sequence diagram showing the erasure procedure between MS, MSC, VLR, and HLR. The diagram consists of four vertical lifelines: MS, MSC, VLR, and HLR. The sequence of messages is as follows: 1) MS sends A_CM_SERV_REQ to MSC; 2) MSC sends MAP_PROCESS_ACCESS_REQUEST to VLR; 3) MS sends A_ERASE_SS to MSC; 4) MSC sends MAP_ERASE_SS_req/ind to VLR; 5) VLR sends MAP_ERASE_SS_req/ind to HLR; 6) HLR sends MAP_ERASE_SS_rsp/cnf to VLR; 7) VLR sends MAP_ERASE_SS_rsp/cnf to MSC; 8) MSC sends A_ERASE_SS ack to MS; 9) VLR sends MAP_INSERT_SUBSCRIBER_DATA_req/ind to HLR; 10) HLR sends MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf to VLR.](009bd9eab25edaa72970a496fba6c755_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note left of MS: 1) A_CM_SERV_REQ (Note 1) + MS->>MSC: 1) A_CM_SERV_REQ (Note 1) + Note right of MSC: 2) MAP_PROCESS_ACCESS_REQUEST (Note 2) + MSC->>VLR: 2) MAP_PROCESS_ACCESS_REQUEST (Note 2) + Note left of MS: 3) A_ERASE_SS (Note 1) + MS->>MSC: 3) A_ERASE_SS (Note 1) + Note right of MSC: 4) MAP_ERASE_SS_req/ind + MSC->>VLR: 4) MAP_ERASE_SS_req/ind + Note right of VLR: 5) MAP_ERASE_SS_req/ind + VLR->>HLR: 5) MAP_ERASE_SS_req/ind + Note right of HLR: 6) MAP_ERASE_SS_rsp/cnf + HLR->>VLR: 6) MAP_ERASE_SS_rsp/cnf + Note right of VLR: 7) MAP_ERASE_SS_rsp/cnf + VLR->>MSC: 7) MAP_ERASE_SS_rsp/cnf + Note left of MSC: 8) A_ERASE_SS ack (Note 1) + MSC->>MS: 8) A_ERASE_SS ack (Note 1) + Note right of VLR: 9) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3) + VLR->>HLR: 9) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3) + Note right of HLR: 10) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3) + HLR->>VLR: 10) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3) + +``` + +Sequence diagram showing the erasure procedure between MS, MSC, VLR, and HLR. The diagram consists of four vertical lifelines: MS, MSC, VLR, and HLR. The sequence of messages is as follows: 1) MS sends A\_CM\_SERV\_REQ to MSC; 2) MSC sends MAP\_PROCESS\_ACCESS\_REQUEST to VLR; 3) MS sends A\_ERASE\_SS to MSC; 4) MSC sends MAP\_ERASE\_SS\_req/ind to VLR; 5) VLR sends MAP\_ERASE\_SS\_req/ind to HLR; 6) HLR sends MAP\_ERASE\_SS\_rsp/cnf to VLR; 7) VLR sends MAP\_ERASE\_SS\_rsp/cnf to MSC; 8) MSC sends A\_ERASE\_SS ack to MS; 9) VLR sends MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind to HLR; 10) HLR sends MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf to VLR. + +- 1) A\_CM\_SERV\_REQ (Note 1) +- 2) MAP\_PROCESS\_ACCESS\_REQUEST (Note 2) +- 3) A\_ERASE\_SS (Note 1) +- 4) MAP\_ERASE\_SS\_req/ind +- 5) MAP\_ERASE\_SS\_req/ind +- 6) MAP\_ERASE\_SS\_rsp/cnf +- 7) MAP\_ERASE\_SS\_rsp/cnf +- 8) A\_ERASE\_SS ack (Note 1) +- 9) MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind (Note 3) +- 10) MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf (Note 3) + +2923 NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS +2924 24.08x and 3GPP TS 24.09x. Services shown in dotted lines indicate the trigger provided by the signalling +2925 on the radio path, and the signalling triggered on the radio path. +2926 NOTE 2: For details of the Process Access Request procedure, refer to clause 25.4 in the present document. +2927 NOTE 3: Services printed in *italics* are optional. +2928 +2929 **Figure 22.3.1/1: Message flow for supplementary service erasure** + +## 2930 22.3.2 Procedure in the MSC + +2931 The MSC procedure for erasure is identical to that specified for registration in clause 22.2.2. The text and diagrams in +2932 clause 22.2.2 apply with all references to registration changed to erasure. + +## 2933 22.3.3 Procedure in the VLR + +2934 The VLR procedure for erasure is identical to that specified for registration in clause 22.2.3. The text and diagrams in +2935 clause 22.2.3 apply with all references to registration changed to erasure. + +## 2936 22.3.4 Procedure in the HLR + +2937 The HLR procedure for erasure is identical to that specified for registration in clause 22.2.4. The text and diagrams in +2938 clause 22.2.4 apply with all references to registration changed to erasure. + +# 2939 22.4 Activation procedure + +## 2940 22.4.1 General + +2941 The activation procedure is used to activate a supplementary service in the HLR. The activation procedure is a fully +2942 transparent communication between the MS and the HLR, except that some services may be invoked as a result of the +2943 procedure, as described in the clauses below. + +2944 The activation procedure is shown in figure 22.4.1/1. + +2945 The following services may be used: + +2946 MAP\_PROCESS\_ACCESS\_REQUEST (see clauses 8 and 25); +2947 MAP\_TRACE\_SUBSCRIBER\_ACTIVITY (see clauses 9 and 25); +2948 MAP\_PROVIDE\_IMSI (see clauses 8 and 25); +2949 MAP\_FORWARD\_NEW\_TMSI (see clauses 8 and 25); +2950 MAP\_AUTHENTICATE (see clauses 8 and 25); +2951 MAP\_SET\_CIPHERING\_MODE (see clauses 8 and 25); +2952 MAP\_CHECK\_IMEI (see clauses 8 and 25); +2953 MAP\_READY\_FOR\_SM (see clauses 12 and 25); +2954 MAP\_GET\_PASSWORD (defined in clause 11); +2955 MAP\_INSERT\_SUBSCRIBER\_DATA (see clauses 8 and 25); + +2956 The following service is certainly used: + +2957 MAP\_ACTIVATE\_SS (defined in clause 11). + +![Sequence diagram showing message flow for supplementary service activation between MS, MSC, VLR, and HLR. The diagram includes 16 numbered messages. Solid lines represent optional MAP messages, while dashed lines represent mandatory A messages. The sequence starts with MS sending A_CM_SERV_REQ to MSC, followed by MSC sending MAP_PROCESS_ACCESS_REQUEST to VLR. The process continues with various activation and password-related messages between the entities.](e3514230081b133d75e94b4fb40b04e0_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + Note left of MS: 1) A_CM_SERV_REQ (Note 1) + MS-->>MSC: 1) A_CM_SERV_REQ (Note 1) + Note right of MSC: 2) MAP_PROCESS_ACCESS_REQUEST (Note 2) + MSC->>VLR: 2) MAP_PROCESS_ACCESS_REQUEST (Note 2) + Note left of MSC: 3) A_ACTIVATE_SS (Note 1) + MSC-->>MS: 3) A_ACTIVATE_SS (Note 1) + Note right of VLR: 4) MAP_ACTIVATE_SS_req/ind + VLR->>MSC: 4) MAP_ACTIVATE_SS_req/ind + Note right of MSC: 5) MAP_ACTIVATE_SS_req/ind + MSC->>HLR: 5) MAP_ACTIVATE_SS_req/ind + Note right of HLR: 6) MAP_GET_PASSWORD_req/ind (Note 3) + HLR->>VLR: 6) MAP_GET_PASSWORD_req/ind (Note 3) + Note right of VLR: 7) MAP_GET_PASSWORD_req/ind (Note 3) + VLR->>MSC: 7) MAP_GET_PASSWORD_req/ind (Note 3) + Note left of MSC: 8) A_GET_PASSWORD (Note 1, Note 3) + MSC-->>MS: 8) A_GET_PASSWORD (Note 1, Note 3) + Note left of MS: 9) A_GET_PASSWORD ack (Note 1, Note 3) + MS-->>MSC: 9) A_GET_PASSWORD ack (Note 1, Note 3) + Note right of MSC: 10) MAP_GET_PASSWORD_rsp/cnf (Note 3) + MSC->>VLR: 10) MAP_GET_PASSWORD_rsp/cnf (Note 3) + Note right of VLR: 11) MAP_GET_PASSWORD_rsp/cnf (Note 3) + VLR->>HLR: 11) MAP_GET_PASSWORD_rsp/cnf (Note 3) + Note right of HLR: 12) MAP_ACTIVATE_SS_rsp/cnf + HLR->>VLR: 12) MAP_ACTIVATE_SS_rsp/cnf + Note right of VLR: 13) MAP_ACTIVATE_SS_rsp/cnf + VLR->>MSC: 13) MAP_ACTIVATE_SS_rsp/cnf + Note left of MSC: 14) A_ACTIVATE_SS ack (Note 1) + MSC-->>MS: 14) A_ACTIVATE_SS ack (Note 1) + Note right of MSC: 15) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3) + MSC->>VLR: 15) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3) + Note right of VLR: 16) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3) + VLR->>HLR: 16) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3) + +``` + +Sequence diagram showing message flow for supplementary service activation between MS, MSC, VLR, and HLR. The diagram includes 16 numbered messages. Solid lines represent optional MAP messages, while dashed lines represent mandatory A messages. The sequence starts with MS sending A\_CM\_SERV\_REQ to MSC, followed by MSC sending MAP\_PROCESS\_ACCESS\_REQUEST to VLR. The process continues with various activation and password-related messages between the entities. + +2958 + +2959 + +- 2960 1) A\_CM\_SERV\_REQ (Note 1) +- 2961 2) MAP\_PROCESS\_ACCESS\_REQUEST (Note 2) +- 2962 3) A\_ACTIVATE\_SS (Note 1) +- 2963 4) MAP\_ACTIVATE\_SS\_req/ind +- 2964 5) MAP\_ACTIVATE\_SS\_req/ind +- 2965 6) *MAP\_GET\_PASSWORD\_req/ind* (Note 3) +- 2966 7) *MAP\_GET\_PASSWORD\_req/ind* (Note 3) +- 2967 8) A\_GET\_PASSWORD (Note 1, Note 3) +- 2968 9) *A\_GET\_PASSWORD ack* (Note 1, Note 3) +- 2969 10) *MAP\_GET\_PASSWORD\_rsp/cnf* (Note 3) +- 2970 11) *MAP\_GET\_PASSWORD\_rsp/cnf* (Note 3) +- 2971 12) MAP\_ACTIVATE\_SS\_rsp/cnf +- 2972 13) MAP\_ACTIVATE\_SS\_rsp/cnf +- 2973 14) A\_ACTIVATE\_SS ack (Note 1) +- 2974 15) *MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind* (Note 3) +- 2975 16) *MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf* (Note 3) + +2976 + +2977 NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS + 2978 24.08x and 3GPP TS 24.09x. Services shown in dotted lines indicate the trigger provided by the signalling + 2979 on the radio path, and the signalling triggered on the radio path. + +2980 NOTE 2: For details of the Process Access Request procedure, refer to clause 25.4 of this document. + +2981 NOTE 3: Services printed in *italics* are optional. + +2982 + +2983 + +**Figure 22.4.1/1: Message flow for supplementary service activation** + +## 2984 22.4.2 Procedure in the MSC + +2985 The A\_ACTIVATE\_SS service indication received by the MAP user in the MSC contains the SS-Code and any + 2986 parameters related to the supplementary service. + +2987 The MSC transfers the received information to the VLR in the MAP\_ACTIVATE\_SS request without checking the + 2988 contents of the service indication. Rules for the mapping are described in 3GPP TS 29.011 [59]. + +2989 The information in the MAP\_ACTIVATE\_SS confirm from the VLR is relayed to the MS in the A\_ACTIVATE\_SS + 2990 response message, as described in TS 24.08x, 3GPP TS 24.08x and 3GPP TS 29.011. + +2991 For call independent SS operations, each message shall contain only a single component. Messages which contain more + 2992 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). + +2993 The activation process in the MSC is shown in figure 22.4.2/1. + +### 2994 22.4.3 Procedure in the VLR + +2995 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +2996     Receive\_Open\_Ind       see clause 25.1.1; + +2997     Receive\_Open\_Cnf       see clause 25.1.2; + +2998     Check\_Confirmation      see clause 25.2.2; + +2999     Process\_Access\_Request\_VLR see clause 25.4.2. + +3000 The MAP process in the VLR transfers the information received in the MAP\_ACTIVATE\_SS indication to the HLR in +3001 the MAP\_ACTIVATE\_SS request without checking the contents. The MAP\_OPEN request includes the IMSI of the +3002 subscriber as the destination reference and the VLR number as the originating reference. + +3003 If the MAP\_REGISTER\_SS confirm is properly formed and contains a result or a user error, the MAP process in the +3004 VLR shall transfer the information contained in this primitive to the MSC in the MAP\_ACTIVATE\_SS response. + +3005 For call independent SS operations, each message shall contain only a single component. Messages which contain more +3006 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). + +3007 The activation process in the VLR is shown in figure 22.4.3/1. + +### 3008 22.4.4 Procedure in the HLR + +3009 The MAP process invokes a macro and a process not defined in this clause; the definitions of the macro and process can +3010 be found as follows: + +3011     Check\_Indication           see clause 25.2.1; + +3012     Insert\_Subs\_Data\_Stand\_Alone\_HLR see clause 25.7.3. + +3013 The supplementary service request shall be processed according to 3GPP TS 23.011 [22] and the 23.08x and 23.09x- +3014 series of technical specifications. This handling may lead to a successful result, a partially successful result or an error +3015 being returned. + +3016 For call independent SS operations, each message shall contain only a single component. Messages which contain more +3017 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). + +3018 The activation process in the HLR is shown in figure 22.4.4/1. + +![State transition diagram for process Activate_SS_MSC. It starts at a 'Null' state and branches into three main paths. The left path handles release/abort signals. The middle path handles activation signals, leading to a 'Wait_For_Activate_SS_Confirm' state. The right path handles close/abort signals. From the activation wait state, it branches into three sub-paths: release/abort, activation response, and password handling. The password path leads to a 'Get_Password_MSC' block with 'Null' and 'OK' outcomes.](3dbe2da229eb652369eb63de9975139e_img.jpg) + +**process Activate\_SS\_MSC** **ASS\_MSC1(1)** + +Process in the MSC to handle a request to activate a supplementary service + +Signals to/from the left are to/from the SS co-ordinating process in the MSC; signals to/from the right are to/from the VLR + +``` + +stateDiagram-v2 + [*] --> Null + Null --> A_CM_SERV_RELEASE_ind + Null --> A_ACTIVATE_SS_ind + Null --> MAP_U_ABORT_ind_MAP_CLOSE_ind + + state "A_CM_SERV_RELEASE_ind" as A_CM_SERV_RELEASE_ind + A_CM_SERV_RELEASE_ind --> MAP_U_ABORT_req + MAP_U_ABORT_req --> Application_procedure_cancellation + Application_procedure_cancellation --> A_CM_RELEASE_COMPLETE_req + A_CM_RELEASE_COMPLETE_req --> [*] + + state "A_ACTIVATE_SS_ind" as A_ACTIVATE_SS_ind + A_ACTIVATE_SS_ind --> MAP_ACTIVATE_SS_req_MAP_DELIMITER_req + MAP_ACTIVATE_SS_req_MAP_DELIMITER_req --> Wait_For_Activate_SS_Confirm + Wait_For_Activate_SS_Confirm --> A_CM_SERV_RELEASE_ind + Wait_For_Activate_SS_Confirm --> MAP_ACTIVATE_SS_cnf + Wait_For_Activate_SS_Confirm --> Get_Password_MSC + Wait_For_Activate_SS_Confirm --> MAP_U_ABORT_ind_MAP_CLOSE_ind + + state "MAP_ACTIVATE_SS_cnf" as MAP_ACTIVATE_SS_cnf + MAP_ACTIVATE_SS_cnf --> A_ACTIVATE_SS_rsp_A_CM_RELEASE_req + A_ACTIVATE_SS_rsp_A_CM_RELEASE_req --> [*] + + state "Get_Password_MSC" as Get_Password_MSC + Get_Password_MSC --> Null + Get_Password_MSC --> OK + OK --> Wait_For_SS_Confirm + Wait_For_SS_Confirm --> [*] + + state "MAP_U_ABORT_ind_MAP_CLOSE_ind" as MAP_U_ABORT_ind_MAP_CLOSE_ind + MAP_U_ABORT_ind_MAP_CLOSE_ind --> A_CM_RELEASE_req + A_CM_RELEASE_req --> [*] + +``` + +State transition diagram for process Activate\_SS\_MSC. It starts at a 'Null' state and branches into three main paths. The left path handles release/abort signals. The middle path handles activation signals, leading to a 'Wait\_For\_Activate\_SS\_Confirm' state. The right path handles close/abort signals. From the activation wait state, it branches into three sub-paths: release/abort, activation response, and password handling. The password path leads to a 'Get\_Password\_MSC' block with 'Null' and 'OK' outcomes. + +3019 + +3020 + +Figure 22.4.2/1: Process Activate\_SS\_MSC + +![Flowchart for process Activate_SS_VLR. The process starts at an oval, goes to 'Null', then 'Receive_Open_Ind'. From 'Receive_Open_Ind', 'OK' leads to 'Wait_For_PAR' and 'Vr, Error' leads to 'Null'. 'Wait_For_PAR' leads to a junction. One path from the junction goes left through a chevron to 'Null', with a box 'MAP_U_ABORT_ind, MAP_CLOSE_ind' above it. The other path goes right to 'Process_Access_Request_VLR'. From 'Process_Access_Request_VLR', 'OK' leads to 'Wait_For_Activate_SS_Request' and 'Error' leads to 'Null'. 'Wait_For_Activate_SS_Request' leads to a chevron 'MAP_ACTIVATE_SS_ind'. This leads to another junction. A box to the right of this junction contains 'MAP_OPEN_req', 'MAP_ACTIVATE_SS_req', and 'MAP_DELIMITER_req'. The main path continues down to 'Receive_Open_Cnf'. From 'Receive_Open_Cnf', 'Error' leads to a decision 'MAP_U_ABORT_req' which leads to 'Null'. 'OK' leads to 'Wait_For_Activate_SS_Confirm'. 'Vr' leads to 'Perform MAP Vr dialogue' which leads to 'Null'.](a014601c1ffe7fbee64d9b81187c4d86_img.jpg) + +**process Activate\_SS\_VLR** **ASS\_VLR1(2)** + +Process in the VLR to handle a request to activate a supplementary service + +Signals to/from the left are to/from the MSC; +signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind -- "OK" --> Wait_For_PAR([Wait_For_PAR]) + Receive_Open_Ind -- "Vr, Error" --> Null2([Null]) + Wait_For_PAR --> Junction1(( )) + Junction1 -- "MAP_U_ABORT_ind, MAP_CLOSE_ind" --> Null3([Null]) + Junction1 --> Process_Access_Request_VLR[Process_Access_Request_VLR] + Process_Access_Request_VLR -- "OK" --> Wait_For_Activate_SS_Request([Wait_For_Activate_SS_Request]) + Process_Access_Request_VLR -- "Error" --> Null4([Null]) + Wait_For_Activate_SS_Request --> MAP_ACTIVATE_SS_ind[/MAP_ACTIVATE_SS_ind/] + MAP_ACTIVATE_SS_ind --> Junction2(( )) + Junction2 -- "MAP_OPEN_req +MAP_ACTIVATE_SS_req +MAP_DELIMITER_req" --> Null5([Null]) + Junction2 --> Receive_Open_Cnf[Receive_Open_Cnf] + Receive_Open_Cnf -- "Error" --> MAP_U_ABORT_req{MAP_U_ABORT_req} + MAP_U_ABORT_req --> Null6([Null]) + Receive_Open_Cnf -- "OK" --> Wait_For_Activate_SS_Confirm([Wait_For_Activate_SS_Confirm]) + Receive_Open_Cnf -- "Vr" --> Perform_MAP_Vr_dialogue[Perform MAP Vr dialogue] + Perform_MAP_Vr_dialogue --> Null7([Null]) + +``` + +Flowchart for process Activate\_SS\_VLR. The process starts at an oval, goes to 'Null', then 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', 'OK' leads to 'Wait\_For\_PAR' and 'Vr, Error' leads to 'Null'. 'Wait\_For\_PAR' leads to a junction. One path from the junction goes left through a chevron to 'Null', with a box 'MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' above it. The other path goes right to 'Process\_Access\_Request\_VLR'. From 'Process\_Access\_Request\_VLR', 'OK' leads to 'Wait\_For\_Activate\_SS\_Request' and 'Error' leads to 'Null'. 'Wait\_For\_Activate\_SS\_Request' leads to a chevron 'MAP\_ACTIVATE\_SS\_ind'. This leads to another junction. A box to the right of this junction contains 'MAP\_OPEN\_req', 'MAP\_ACTIVATE\_SS\_req', and 'MAP\_DELIMITER\_req'. The main path continues down to 'Receive\_Open\_Cnf'. From 'Receive\_Open\_Cnf', 'Error' leads to a decision 'MAP\_U\_ABORT\_req' which leads to 'Null'. 'OK' leads to 'Wait\_For\_Activate\_SS\_Confirm'. 'Vr' leads to 'Perform MAP Vr dialogue' which leads to 'Null'. + +3021 + +3022 + +Figure 22.4.3/1 (sheet 1 of 2): Process Activate\_SS\_VLR + +![State transition diagram for process Activate_SS_VLR. It shows two main state machines. The top one starts in 'Wait_For_Activate_SS_Confirm' and handles 'MAP_U_ABORT_ind, MAP_CLOSE_ind', 'MAP_ACTIVATE_SS_cnf', 'MAP_NOTICE_ind', and 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind'. The bottom one starts in 'Wait_For_Activate_SS_Confirm', calls 'Get_Password_VLR', and then either returns to 'Wait_For_Activate_SS_Confirm' on 'OK' or goes to 'Null' on 'Null'.](6818896c78f403ee74f560a89f9e4e69_img.jpg) + +**process Activate\_SS\_VLR** **ASS\_VLR2(2)** + +Process in the VLR to handle a request to activate a supplementary service + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> W1: Wait_For_Activate_SS_Confirm + W1 --> S1: MAP_U_ABORT_ind, MAP_CLOSE_ind + W1 --> S2: MAP_ACTIVATE_SS_cnf + W1 --> S3: MAP_NOTICE_ind + W1 --> S4: MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind + + S1 --> R1: MAP_U_ABORT_req + R1 --> Null1: Null + + S2 --> C1: Check Confirmation + C1 --> S5: OK, User Error, Data Error + C1 --> S6: Provider Error + S5 --> R2: MAP_ACTIVATE_SS_rsp, MAP_CLOSE_req + R2 --> Null2: Null + S6 --> R3: MAP_U_ABORT_req + R3 --> Null3: Null + + S3 --> R4: MAP_CLOSE_req + R4 --> R5: MAP_U_ABORT_req + R5 --> Null4: Null + + S4 --> R5 + R5 --> Null4 + + [*] --> W2: Wait_For_Activate_SS_Confirm + W2 --> G1: Get_Password_VLR + G1 --> W2: OK + G1 --> Null5: Null + +``` + +State transition diagram for process Activate\_SS\_VLR. It shows two main state machines. The top one starts in 'Wait\_For\_Activate\_SS\_Confirm' and handles 'MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind', 'MAP\_ACTIVATE\_SS\_cnf', 'MAP\_NOTICE\_ind', and 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind'. The bottom one starts in 'Wait\_For\_Activate\_SS\_Confirm', calls 'Get\_Password\_VLR', and then either returns to 'Wait\_For\_Activate\_SS\_Confirm' on 'OK' or goes to 'Null' on 'Null'. + +3023 + +3024 + +Figure 22.4.3/1 (sheet 2 of 2): Process Activate\_SS\_VLR + +![Flowchart for process Activate_SS_HLR. The process starts with an oval, followed by a 'Null' block. It then receives a 'MAP_ACTIVATE_SS_ind' signal. A 'Check Indication' block follows. If 'OK', it checks 'Operator Determined Barring of SS management?'. If 'Yes', it sets a user error 'Call barred' with cause 'Operator barring' and sends 'MAP_ACTIVATE_SS_rsp' and 'MAP_CLOSE_req' signals. If 'No', it sends an 'SS request' and waits for an application response. The response can be 'acknowledge', 'partial acceptance', 'error', or 'MAP_NOTICE_ind'. 'acknowledge' and 'partial acceptance' lead to 'Set Result'. 'error' leads to 'Set User Error'. 'MAP_NOTICE_ind' leads to 'MAP_U_ABORT_req'. All three paths lead to a common merge point. From there, it sends 'MAP_ACTIVATE_SS_rsp' and 'MAP_CLOSE_req' signals. A decision 'Update of subs data required in VLR?' follows. If 'Yes', it performs 'Insert Subs Data Stand Alone_HLR'. Finally, it reaches connector '1'.](76e7ce06af53fb17b6207582a43218d0_img.jpg) + +**process Activate\_SS\_HLR** **ASS\_HLR1(2)** + +Process in the HLR to handle a request to activate a supplementary service + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the process SS\_REQUEST\_WITH\_BS\_GROUP (see 3GPP TS 23.011) + +``` + + graph TD + Start([ ]) --> Null[Null] + Null --> In1{{MAP_ACTIVATE_SS_ind}} + In1 --> Check[Check Indication] + Check -- OK --> Decision1{Operator Determined Barring of SS management?} + Decision1 -- Yes --> SetError1[Set User Error: Call barred] + SetError1 --> Cause[Call barring cause=Operator barring] + Cause --> Out1{{MAP_ACTIVATE_SS_rsp +MAP_CLOSE_req}} + Out1 -- Error --> End1((X)) + Decision1 -- No --> In2{{SS request}} + In2 --> Wait[Wait_For_Application_Response] + Wait --> Acknowledge{{acknowledge}} + Wait --> PartialAcceptance{{partial acceptance}} + Wait --> Error2{{error}} + Wait --> NoticeInd{{MAP_NOTICE_ind}} + Acknowledge --> SetResult[Set Result] + Error2 --> SetError2[Set User Error] + NoticeInd --> AbortReq{{MAP_U_ABORT_req}} + SetResult --> Merge1(( )) + SetError2 --> Merge1 + AbortReq --> Merge1 + Merge1 --> Out2{{MAP_ACTIVATE_SS_rsp +MAP_CLOSE_req}} + Out2 --> Decision2{Update of subs data required in VLR?} + Decision2 -- Yes --> InsertData[Insert Subs Data Stand Alone_HLR] + InsertData --> Merge2(( )) + Decision2 -- No --> Merge2 + Merge2 --> End2((1)) + +``` + +Flowchart for process Activate\_SS\_HLR. The process starts with an oval, followed by a 'Null' block. It then receives a 'MAP\_ACTIVATE\_SS\_ind' signal. A 'Check Indication' block follows. If 'OK', it checks 'Operator Determined Barring of SS management?'. If 'Yes', it sets a user error 'Call barred' with cause 'Operator barring' and sends 'MAP\_ACTIVATE\_SS\_rsp' and 'MAP\_CLOSE\_req' signals. If 'No', it sends an 'SS request' and waits for an application response. The response can be 'acknowledge', 'partial acceptance', 'error', or 'MAP\_NOTICE\_ind'. 'acknowledge' and 'partial acceptance' lead to 'Set Result'. 'error' leads to 'Set User Error'. 'MAP\_NOTICE\_ind' leads to 'MAP\_U\_ABORT\_req'. All three paths lead to a common merge point. From there, it sends 'MAP\_ACTIVATE\_SS\_rsp' and 'MAP\_CLOSE\_req' signals. A decision 'Update of subs data required in VLR?' follows. If 'Yes', it performs 'Insert Subs Data Stand Alone\_HLR'. Finally, it reaches connector '1'. + +3025 + +3026 + +Figure 22.4.4/1 (sheet 1 of 2): Process Activate\_SS\_HLR + +![State transition diagram for process Activate_SS_HLR. The process starts in 'Wait_For_Application_Response', transitions to 'SS Get Password', then to a state with 'MAP_GET_PASSWORD_req' and 'MAP_DELIMITER_req'. It then enters 'Wait_For_Password'. From there, it can transition to 'MAP_NOTICE_ind' (leading to 'MAP_CLOSE_req' and then an error state), 'MAP_GET_PASSWORD_cnf' (leading to 'Check Confirmation'), or an unlabeled state (leading to error signals and an error state). From 'Check Confirmation', 'OK, User Error' leads to 'SS Get Password_Ack' and back to 'Wait_For_Application_Response', while 'Provider Error, Data Error' leads to an error state.](bca588deb64f5309a2502fe06555eec4_img.jpg) + +**process Activate\_SS\_HLR** **ASS\_HLR2(2)** + +Process in the HLR to handle a request to activate a supplementary service + +``` + +stateDiagram-v2 + [*] --> Wait_For_Application_Response + state "Wait_For_Application_Response" as Wait_For_Application_Response + state "SS Get Password" as SS_Get_Password + state "MAP_GET_PASSWORD_req, MAP_DELIMITER_req" as MAP_GET_PASSWORD_req_MAP_DELIMITER_req + state "Wait_For_Password" as Wait_For_Password + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_GET_PASSWORD_cnf" as MAP_GET_PASSWORD_cnf + state "Check Confirmation" as Check_Confirmation + state "SS Get Password_Ack" as SS_Get_Password_Ack + state "MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind" as Error_Signals + state "Error State" as [*] + + Wait_For_Application_Response --> SS_Get_Password + SS_Get_Password --> MAP_GET_PASSWORD_req_MAP_DELIMITER_req + MAP_GET_PASSWORD_req_MAP_DELIMITER_req --> Wait_For_Password + Wait_For_Password --> MAP_NOTICE_ind + Wait_For_Password --> MAP_GET_PASSWORD_cnf + Wait_For_Password --> Error_Signals + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> [*] + MAP_GET_PASSWORD_cnf --> Check_Confirmation + Check_Confirmation --> SS_Get_Password_Ack : OK, User Error + Check_Confirmation --> [*] : Provider Error, Data Error + SS_Get_Password_Ack --> Wait_For_Application_Response + +``` + +State transition diagram for process Activate\_SS\_HLR. The process starts in 'Wait\_For\_Application\_Response', transitions to 'SS Get Password', then to a state with 'MAP\_GET\_PASSWORD\_req' and 'MAP\_DELIMITER\_req'. It then enters 'Wait\_For\_Password'. From there, it can transition to 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req' and then an error state), 'MAP\_GET\_PASSWORD\_cnf' (leading to 'Check Confirmation'), or an unlabeled state (leading to error signals and an error state). From 'Check Confirmation', 'OK, User Error' leads to 'SS Get Password\_Ack' and back to 'Wait\_For\_Application\_Response', while 'Provider Error, Data Error' leads to an error state. + +3027 + +3028 + +**Figure 22.4.4/1 (sheet 2 of 2): Process Activate\_SS\_HLR** + +## 3029 22.5 Deactivation procedure + +### 3030 22.5.1 General + +3031 The deactivation procedure is used to deactivate a supplementary service in the HLR. The deactivation procedure is a +3032 fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of +3033 the procedure, as described in the clauses below. + +3034 The deactivation procedure is shown in figure 22.5.1/1. + +3035 The following services may be used: + +- 3036 MAP\_PROCESS\_ACCESS\_REQUEST (see clauses 8 and 25); +- 3037 MAP\_TRACE\_SUBSCRIBER\_ACTIVITY (see clauses 9 and 25); +- 3038 MAP\_PROVIDE\_IMSI (see clauses 8 and 25); +- 3039 MAP\_FORWARD\_NEW\_TMSI (see clauses 8 and 25); +- 3040 MAP\_AUTHENTICATE (see clauses 8 and 25); +- 3041 MAP\_SET\_CIPHERING\_MODE (see clauses 8 and 25); +- 3042 MAP\_CHECK\_IMEI (see clauses 8 and 25); +- 3043 MAP\_READY\_FOR\_SM (see clauses 12 and 25); +- 3044 MAP\_GET\_PASSWORD (defined in clause 11); +- 3045 MAP\_INSERT\_SUBSCRIBER\_DATA (see clauses 8 and 25); + +3046 The following service is certainly used: + +- 3047 MAP\_DEACTIVATE\_SS (defined in clause 11). + +![Sequence diagram for the deactivation procedure. Lifelines: MS, MSC, VLR, HLR. The sequence starts with the MS sending a request (1) to the MSC. The MSC then sends a request (2) to the VLR. The VLR sends a request (3) to the HLR. The HLR responds (4) to the VLR. The VLR responds (5) to the MSC. The MSC responds (6) to the MS. The MS sends a response (7) to the MSC. The MSC sends a response (8) to the VLR. The VLR sends a response (9) to the HLR. The HLR responds (10) to the VLR. The VLR responds (11) to the MSC. The MSC responds (12) to the MS. The MS sends a response (13) to the MSC. The MSC sends a response (14) to the VLR. The VLR sends a response (15) to the HLR. The HLR responds (16) to the VLR.](5a572c77a281fc60efe055dcd75215a2_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note left of MS: 1) A_CM_SERV_REQ (Note 1) + MS->>MSC: 1 + MSC->>VLR: 2 + VLR->>HLR: 3 + HLR-->>VLR: 4 + VLR-->>MSC: 5 + MSC-->>MS: 6 + MS->>MSC: 7 + MSC-->>VLR: 8 + VLR-->>HLR: 9 + HLR-->>VLR: 10 + VLR-->>MSC: 11 + MSC-->>MS: 12 + MS->>MSC: 13 + MSC-->>VLR: 14 + VLR-->>HLR: 15 + HLR-->>VLR: 16 +``` + +Sequence diagram for the deactivation procedure. Lifelines: MS, MSC, VLR, HLR. The sequence starts with the MS sending a request (1) to the MSC. The MSC then sends a request (2) to the VLR. The VLR sends a request (3) to the HLR. The HLR responds (4) to the VLR. The VLR responds (5) to the MSC. The MSC responds (6) to the MS. The MS sends a response (7) to the MSC. The MSC sends a response (8) to the VLR. The VLR sends a response (9) to the HLR. The HLR responds (10) to the VLR. The VLR responds (11) to the MSC. The MSC responds (12) to the MS. The MS sends a response (13) to the MSC. The MSC sends a response (14) to the VLR. The VLR sends a response (15) to the HLR. The HLR responds (16) to the VLR. + +3048 + +- 3049 +- 3050 1) A\_CM\_SERV\_REQ (Note 1) +- 3051 2) MAP\_PROCESS\_ACCESS\_REQUEST (Note 2) + +3052 3) *A\_DEACTIVATE\_SS* (Note 1) +3053 4) *MAP\_DEACTIVATE\_SS\_req/ind* +3054 5) *MAP\_DEACTIVATE\_SS\_req/ind* +3055 6) *MAP\_GET\_PASSWORD\_req/ind* (Note 3) +3056 7) *MAP\_GET\_PASSWORD\_req/ind* (Note 3) +3057 8) *A\_GET\_PASSWORD* (Note 1, Note 3) +3058 9) *A\_GET\_PASSWORD\_ack* (Note 1, Note 3) +3059 10) *MAP\_GET\_PASSWORD\_rsp/cnf* (Note 3) +3060 11) *MAP\_GET\_PASSWORD\_rsp/cnf* (Note 3) +3061 12) *MAP\_DEACTIVATE\_SS\_rsp/cnf* +3062 13) *MAP\_DEACTIVATE\_SS\_rsp/cnf* +3063 14) *A\_DEACTIVATE\_SS\_ack* (Note 1) +3064 15) *MAP\_INSERT\_SUBSCRIBER\_DATA\_req/ind* (Note 3) +3065 16) *MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp/cnf* (Note 3) +3066 +3067 NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS +3068 24.08x and 3GPP TS 24.09x. Services shown in dotted lines indicate the trigger provided by the signalling +3069 on the radio path, and the signalling triggered on the radio path. +3070 NOTE 2: For details of the Process Access Request procedure, refer to clause 25.4 in the present document. +3071 NOTE 3: Services printed in *italics* are optional. +3072 +3073 **Figure 22.5.1/1: Message flow for supplementary service deactivation** + +## 3074 22.5.2 Procedure in the MSC + +3075 The MSC procedure for deactivation is identical to that specified for activation in clause 22.4.2. The text and diagrams +3076 in clause 22.4.2 apply with all references to activation changed to deactivation. + +## 3077 22.5.3 Procedures in the VLR + +3078 The VLR procedure for deactivation is identical to that specified for activation in clause 22.4.3. The text and diagrams +3079 in clause 22.4.3 apply with all references to activation changed to deactivation. + +## 3080 22.5.4 Procedures in the HLR + +3081 The HLR procedure for deactivation is identical to that specified for activation in clause 22.4.4. The text and diagrams +3082 in clause 22.4.4 apply with all references to activation changed to deactivation. + +# 3083 22.6 Interrogation procedure + +## 3084 22.6.1 General + +3085 The interrogation procedure is used to retrieve information related to a supplementary service from the VLR or the +3086 HLR. It is the VLR which decides whether an interrogation request should be forwarded to the HLR or not. Some non- +3087 supplementary service related services may be invoked as a result of the procedure, as described in the clauses below. + +3088 The interrogation procedure is shown in figure 22.6.1/1. + +3089 The following services may be used: + +3090 *MAP\_PROCESS\_ACCESS\_REQUEST* (see clauses 8 and 25); +3091 *MAP\_TRACE\_SUBSCRIBER\_ACTIVITY* (see clauses 9 and 25); +3092 *MAP\_PROVIDE\_IMSI* (see clauses 8 and 25); +3093 *MAP\_FORWARD\_NEW\_TMSI* (see clauses 8 and 25); +3094 *MAP\_AUTHENTICATE* (see clauses 8 and 25); +3095 *MAP\_SET\_CIPHERING\_MODE* (see clauses 8 and 25); + +3096 MAP\_CHECK\_IMEI (see clauses 8 and 25); + 3097 MAP\_READY\_FOR\_SM (see clauses 12 and 25); + 3098 The following service is certainly used: + 3099 MAP\_INTERROGATE\_SS (defined in clause 11). + +![Sequence diagram showing message flow for supplementary service interrogation between MS, MSC, VLR, and HLR. The diagram shows 8 numbered messages: 1) A_CM_SERV_REQ (dotted line MS to MSC), 2) MAP_PROCESS_ACCESS_REQUEST (solid line MSC to VLR), 3) A_INTERROGATE_SS (dotted line MS to MSC), 4) MAP_INTERROGATE_SS_req/ind (solid line MSC to VLR), 5) MAP_INTERROGATE_SS_req/ind (solid line VLR to HLR), 6) MAP_INTERROGATE_SS_rsp/cnf (solid line HLR to VLR), 7) MAP_INTERROGATE_SS_rsp/cnf (solid line VLR to MSC), 8) A_INTERROGATE_SS ack (dotted line MSC to MS).](fa2660fd2f78ad77de9acb043a931d97_img.jpg) + +Sequence diagram showing message flow for supplementary service interrogation between MS, MSC, VLR, and HLR. The diagram shows 8 numbered messages: 1) A\_CM\_SERV\_REQ (dotted line MS to MSC), 2) MAP\_PROCESS\_ACCESS\_REQUEST (solid line MSC to VLR), 3) A\_INTERROGATE\_SS (dotted line MS to MSC), 4) MAP\_INTERROGATE\_SS\_req/ind (solid line MSC to VLR), 5) MAP\_INTERROGATE\_SS\_req/ind (solid line VLR to HLR), 6) MAP\_INTERROGATE\_SS\_rsp/cnf (solid line HLR to VLR), 7) MAP\_INTERROGATE\_SS\_rsp/cnf (solid line VLR to MSC), 8) A\_INTERROGATE\_SS ack (dotted line MSC to MS). + +3100 + +3101 + 3102 1) A\_CM\_SERV\_REQ (Note 1) + 3103 2) MAP\_PROCESS\_ACCESS\_REQUEST (Note 2) + 3104 3) A\_INTERROGATE\_SS (Note 1) + 3105 4) MAP\_INTERROGATE\_SS\_req/ind + 3106 5) *MAP\_INTERROGATE\_SS\_req/ind* + 3107 6) *MAP\_INTERROGATE\_SS\_rsp/cnf* + 3108 7) MAP\_INTERROGATE\_SS\_rsp/cnf + 3109 8) A\_INTERROGATE\_SS ack (Note 1) + +3110 + +3111 NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS + 3112 24.08x and 3GPP TS 24.09x. Services shown in dotted lines indicate the trigger provided by the signalling + 3113 on the radio path, and the signalling triggered on the radio path. + +3114 NOTE 2: For details of the Process Access Request procedure, refer to clause 25.4 in the present document. + +3115 NOTE 3: Services printed in *italics* are optional. + +3116 + +3117 + +**Figure 22.6.1/1: Message flow for supplementary service interrogation** + +## 3118 22.6.2 Procedure in the MSC + +3119 The MSC procedures for interrogation are identical to those specified for registration in clause 22.2.2. The text and + 3120 diagrams in clause 22.2.2 apply with all references to registration changed to interrogation. + +## 3121 22.6.3 Procedures in the VLR + +3122 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +3123 Receive\_Open\_Ind see clause 25.1.1; + 3124 Receive\_Open\_Cnf see clause 25.1.2; + 3125 Check\_Confirmation see clause 25.2.2; + 3126 Process\_Access\_Request\_VLR see clause 25.4.2. + +3127 The interrogation is answered either by the VLR or by the HLR, depending on the service interrogated. + +3128 1) **Interrogation to be handled by the VLR** + +3129 The supplementary service request shall be processed according to 3GPP TS 23.011 [22] and the 23.08x and 23.09x- +3130 series of technical specifications. This handling may lead to a successful result, a partially successful result or an error +3131 being returned. + +3132 For call independent SS operations, each message shall contain only a single component. Messages which contain more +3133 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). + +#### 3134 **2) Interrogation to be handled by the HLR** + +3135 If the interrogation is to be handled by the HLR, the MAP process in the VLR transfers the information received in the +3136 MAP\_INTERROGATE\_SS indication to the HLR in the MAP\_INTERROGATE\_SS request without checking the +3137 contents of the service indication. The MAP\_OPEN request includes the IMSI of the subscriber as the destination +3138 reference and the VLR number as the originating reference. + +3139 If the MAP\_INTERROGATE\_SS confirm is properly formed and contains a result or a user error, the MAP process in +3140 the VLR shall transfer the information contained in this primitive to the MSC in the MAP\_INTERROGATE\_SS +3141 response. + +3142 For call independent SS operations, each message shall contain only a single component. Messages which contain more +3143 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). + +3144 The Interrogation process in the VLR is shown in figure 22.6.3/1. + +### 3145 **22.6.4 Procedure in the HLR** + +3146 The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +3147 Check\_Indication see clause 25.2.1. + +3148 The HLR acts as follows: + +3149 The interrogation is answered either by the VLR or by the HLR, depending on the service interrogated. + +#### 3150 **1) Interrogation to be handled by the VLR** + +3151 If the interrogation procedure should have been answered by the VLR, then the HLR assumes that the VLR does +3152 not support the interrogated supplementary service, and returns the SS Not Available error to the VLR. + +#### 3153 **2) Interrogation to be handled by HLR** + +3154 The supplementary service request shall be processed according to 3GPP TS 23.011 [22] and the 23.08x and +3155 23.09x-series of technical specifications. This handling may lead to either a successful result or an error being +3156 returned. + +3157 For call independent SS operations, each message shall contain only a single component. Messages which contain more +3158 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). + +3159 The Interrogation process in the HLR is shown in figure 22.6.4/1. + +![Flowchart for process Interrogate_SS_VLR. It details the logic for handling supplementary service interrogation requests in the VLR, including access requests, barring checks, and determining if interrogation is handled locally or forwarded.](b58be03dfedfc48f5e785b7d59a28b53_img.jpg) + +**process Interrogate\_SS\_VLR** **ISS\_VLR1(2)** + +Processs in the VLR to handle a request to interrogate data for a supplementary service + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the process SS\_REQUEST\_WITH\_BS\_GROUP (see 3GPP TS 23.011) + +``` + + graph TD + Start([ ]) --> Null1(Null) + Null1 --> RecOpen[/Receive_Open_Ind/] + RecOpen -- OK --> WaitPAR(Wait_For_PAR) + RecOpen -- "Vr, Error" --> NullErr(Null) + + WaitPAR --> ProcAcc[Process_Access_Request_VLR] + ProcAcc -- OK --> WaitInterrog(Wait_For_Interrogate_SS_Request) + ProcAcc -- Error --> NullErr2(Null) + + %% Left side branch + WaitPAR -- "MAP_U_ABORT_ind, +MAP_CLOSE_ind" --> NullAbort(Null) + + WaitInterrog --> MAPInd[/MAP_INTERROGATE_SS_ind/] + MAPInd --> Barring{Operator Determined Barring +of SS management?} + + Barring -- Yes --> SetError[Set User Error: +Call barred] + SetError --> Cause[Call barring cause= +Operator barring] + Cause --> MAPRsp[/MAP_INTERROGATE_SS_rsp +MAP_CLOSE_req/] + MAPRsp --> NullEnd(Null) + + Barring -- No --> SSKnown{SS known?} + SSKnown -- No --> Conn1((1)) + SSKnown -- Yes --> HandleVLR{Handle interrogation +in VLR?} + + HandleVLR -- No --> Conn1 + HandleVLR -- Yes --> SSReq[/SS request/] + SSReq --> WaitApp(Wait_For_Application_Response) + +``` + +Flowchart for process Interrogate\_SS\_VLR. It details the logic for handling supplementary service interrogation requests in the VLR, including access requests, barring checks, and determining if interrogation is handled locally or forwarded. + +3160 + +3161 + +**Figure 22.6.3/1 (sheet 1 of 2): Process Interrogate\_SS\_VLR** + +![Flowchart for process Interrogate_SS_VLR. The process starts at a circle labeled '1', leading to a decision diamond. The left branch handles Error and Vr cases, leading to MAP_U_ABORT_req and Null. The right branch (OK) leads to Wait_For_Interrogate_SS_Confirm, then a decision diamond. The left sub-branch handles MAP_U_ABORT_ind and MAP_CLOSE_ind, leading to MAP_U_ABORT_req and Null. The middle sub-branch handles MAP_INTERROGATE_SS_cnf, leading to Check_Confirmation. The right sub-branch handles MAP_P_ABORT_ind, MAP_U_ABORT_ind, and MAP_CLOSE_ind, leading to MAP_NOTICE_ind and MAP_CLOSE_req. Check_Confirmation leads to a decision diamond for OK, User Error, Data Error, and Provider Error. The OK branch leads to MAP_INTERROGATE_SS_rsp and MAP_CLOSE_req, then Null. The User Error and Data Error branches lead to MAP_U_ABORT_req and Null. The Provider Error branch leads to MAP_U_ABORT_req and Null. Below this, the process continues to Wait_For_Application_Response, then a decision diamond for acknowledge, partial acceptance, and error. The acknowledge and partial acceptance branches lead to Set Result. The error branch leads to Set User Error. Both Set Result and Set User Error lead to a decision diamond for MAP_INTERROGATE_SS_rsp and MAP_CLOSE_req, which then leads to Null.](3112451876ed341b259b5f389b56723f_img.jpg) + +**process Interrogate\_SS\_VLR** **ISS\_VLR2(2)** + +Process in the VLR to handle a request to interrogate data for a supplementary service + +In the upper subtree, signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR + +``` + + graph TD + Start((1)) --> Decision1{ } + Decision1 --> OpenCnf[Receive Open_Cnf] + OpenCnf --> Decision2{ } + Decision2 -- Error --> UAbortReq1[MAP_U_ABORT_req] + UAbortReq1 --> Null1([Null]) + Decision2 -- Vr --> PerformVr[Perform MAP Vr dialogue] + PerformVr --> Null1 + Decision2 -- OK --> WaitConfirm[Wait_For_Interrogate_SS_Confirm] + WaitConfirm --> Decision3{ } + Decision3 --> UAbortInd1[MAP_U_ABORT_ind, MAP_CLOSE_ind] + UAbortInd1 --> UAbortReq2[MAP_U_ABORT_req] + UAbortReq2 --> Null2([Null]) + Decision3 --> InterrogateCnf[MAP_INTERROGATE_SS_cnf] + InterrogateCnf --> CheckConfirm[Check_Confirmation] + CheckConfirm --> Decision4{ } + Decision4 -- "OK, User Error, Data Error" --> InterrogateRsp1[MAP_INTERROGATE_SS_rsp, MAP_CLOSE_req] + InterrogateRsp1 --> Null3([Null]) + Decision4 -- Provider Error --> UAbortReq3[MAP_U_ABORT_req] + UAbortReq3 --> Null4([Null]) + Decision3 --> PAbortInd[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] + PAbortInd --> NoticeInd[MAP_NOTICE_ind] + NoticeInd --> CloseReq1[MAP_CLOSE_req] + CloseReq1 --> UAbortReq4[MAP_U_ABORT_req] + UAbortReq4 --> Null5([Null]) + Null2 --> WaitAppResp[Wait_For_Application_Response] + Null3 --> WaitAppResp + Null4 --> WaitAppResp + Null5 --> WaitAppResp + WaitAppResp --> Decision5{ } + Decision5 -- acknowledge --> SetResult[Set Result] + Decision5 -- partial acceptance --> SetResult + Decision5 -- error --> SetUserError[Set User Error] + SetResult --> Decision6{ } + SetUserError --> Decision6 + Decision6 --> InterrogateRsp2[MAP_INTERROGATE_SS_rsp, MAP_CLOSE_req] + InterrogateRsp2 --> Null6([Null]) + +``` + +In the lower subtree, signals to/from the left are to/from the MSC; signals to/from the right are to/from the process SS\_REQUEST\_WITH\_BS\_GROUP (see 3GPP TS 23.011) + +Flowchart for process Interrogate\_SS\_VLR. The process starts at a circle labeled '1', leading to a decision diamond. The left branch handles Error and Vr cases, leading to MAP\_U\_ABORT\_req and Null. The right branch (OK) leads to Wait\_For\_Interrogate\_SS\_Confirm, then a decision diamond. The left sub-branch handles MAP\_U\_ABORT\_ind and MAP\_CLOSE\_ind, leading to MAP\_U\_ABORT\_req and Null. The middle sub-branch handles MAP\_INTERROGATE\_SS\_cnf, leading to Check\_Confirmation. The right sub-branch handles MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, and MAP\_CLOSE\_ind, leading to MAP\_NOTICE\_ind and MAP\_CLOSE\_req. Check\_Confirmation leads to a decision diamond for OK, User Error, Data Error, and Provider Error. The OK branch leads to MAP\_INTERROGATE\_SS\_rsp and MAP\_CLOSE\_req, then Null. The User Error and Data Error branches lead to MAP\_U\_ABORT\_req and Null. The Provider Error branch leads to MAP\_U\_ABORT\_req and Null. Below this, the process continues to Wait\_For\_Application\_Response, then a decision diamond for acknowledge, partial acceptance, and error. The acknowledge and partial acceptance branches lead to Set Result. The error branch leads to Set User Error. Both Set Result and Set User Error lead to a decision diamond for MAP\_INTERROGATE\_SS\_rsp and MAP\_CLOSE\_req, which then leads to Null. + +3162 + +3163 + +Figure 22.6.3/1 (sheet 2 of 2): Process Interrogate\_SS\_VLR + +![Flowchart for process Interrogate_SS_HLR. It starts with 'Null', followed by 'MAP_INTERROGATE_SS_ind'. A decision diamond 'Check_Indication' leads to 'OK' or 'Error'. 'OK' leads to a decision 'Operator Determined Barring of SS management?'. If 'Yes', it goes to 'Set User Error: Call barred' (with 'Call barring cause= Operator barring') and then to an error exit. If 'No', it goes to 'SS supported in HLR?'. If 'Yes', it goes to 'Set User Error: Unexpected data value' and then to an error exit. If 'No', it goes to 'Interrogation should be handled in VLR?'. If 'Yes', it goes to 'Set User Error: SS not available' and then to an error exit. If 'No', it goes to 'SS request' -> 'Wait_For_Application_Response'. From there, it branches into 'acknowledge' -> 'Set Result' -> 'MAP_INTERROGATE_SS_rsp' / 'MAP_CLOSE_req' -> exit; 'error' -> 'Set User Error' -> 'MAP_INTERROGATE_SS_rsp' / 'MAP_CLOSE_req' -> exit; 'MAP_NOTICE_ind' -> 'MAP_U_ABORT_req' -> exit; and an unlabeled path leading to 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' -> exit.](a40aa98acf7618b7940b8f222255c8cb_img.jpg) + +**process Interrogate\_SS\_HLR** **ISS\_HLR1(1)** + +Process in the HLR to handle a request to interrogate data for a supplementary service + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the process SS\_REQUEST\_WITH\_BS\_GROUP (see 3GPP TS 23.011) + +``` + + graph TD + Start([Null]) --> MAP_IND{MAP_INTERROGATE_SS_ind} + MAP_IND --> CHECK[Check_Indication] + CHECK -- OK --> DEC1{Operator Determined Barring of SS management?} + CHECK -- Error --> EXIT1((X)) + DEC1 -- Yes --> SET_ERR1[Set User Error: Call barred] + SET_ERR1 --> SET_ERR1_CAUSE[Call barring cause= Operator barring] + SET_ERR1_CAUSE --> EXIT1 + DEC1 -- No --> DEC2{SS supported in HLR?} + DEC2 -- Yes --> SET_ERR2[Set User Error: Unexpected data value] + SET_ERR2 --> EXIT1 + DEC2 -- No --> DEC3{Interrogation should be handled in VLR?} + DEC3 -- Yes --> SET_ERR3[Set User Error: SS not available] + SET_ERR3 --> EXIT1 + DEC3 -- No --> SS_REQ[/SS request/] + SS_REQ --> WAIT[Wait_For_Application_Response] + WAIT --> ACK[/acknowledge/] + WAIT --> ERR[/error/] + WAIT --> NOTICE[MAP_NOTICE_ind] + WAIT --> UNL[ ] + style UNL fill:none,stroke:none + ACK --> SET_RES[Set Result] + SET_RES --> RSP1[/MAP_INTERROGATE_SS_rsp / MAP_CLOSE_req/] + RSP1 --> EXIT2((X)) + ERR --> SET_ERR4[Set User Error] + SET_ERR4 --> RSP2[/MAP_INTERROGATE_SS_rsp / MAP_CLOSE_req/] + RSP2 --> EXIT3((X)) + NOTICE --> ABORT[MAP_U_ABORT_req] + ABORT --> EXIT4((X)) + UNL --> ABORT_IND[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] + ABORT_IND --> EXIT5((X)) + +``` + +Flowchart for process Interrogate\_SS\_HLR. It starts with 'Null', followed by 'MAP\_INTERROGATE\_SS\_ind'. A decision diamond 'Check\_Indication' leads to 'OK' or 'Error'. 'OK' leads to a decision 'Operator Determined Barring of SS management?'. If 'Yes', it goes to 'Set User Error: Call barred' (with 'Call barring cause= Operator barring') and then to an error exit. If 'No', it goes to 'SS supported in HLR?'. If 'Yes', it goes to 'Set User Error: Unexpected data value' and then to an error exit. If 'No', it goes to 'Interrogation should be handled in VLR?'. If 'Yes', it goes to 'Set User Error: SS not available' and then to an error exit. If 'No', it goes to 'SS request' -> 'Wait\_For\_Application\_Response'. From there, it branches into 'acknowledge' -> 'Set Result' -> 'MAP\_INTERROGATE\_SS\_rsp' / 'MAP\_CLOSE\_req' -> exit; 'error' -> 'Set User Error' -> 'MAP\_INTERROGATE\_SS\_rsp' / 'MAP\_CLOSE\_req' -> exit; 'MAP\_NOTICE\_ind' -> 'MAP\_U\_ABORT\_req' -> exit; and an unlabeled path leading to 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' -> exit. + +3164 + +3165 + +Figure 22.6.4/1: Process Interrogate\_SS\_HLR + +3166 **22.7 Void** + +3167 + +**Figure 22.7.2/1 void** + +3168 + +**Figure 22.7.3/1 void** + +## 3169 22.8 Password registration procedure + +### 3170 22.8.1 General + +3171 The password registration procedure is used to register a password in the HLR. The password registration procedure is a +3172 fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of +3173 the procedure, as described below. + +3174 The password registration procedure is shown in figure 22.8.1/1. + +3175 The following services may be used: + +3176 MAP\_PROCESS\_ACCESS\_REQUEST (see clauses 8 and 25); + +3177 MAP\_TRACE\_SUBSCRIBER\_ACTIVITY (see clauses 9 and 25); + +3178 MAP\_PROVIDE\_IMSI (see clauses 8 and 25); + +3179 MAP\_FORWARD\_NEW\_TMSI (see clauses 8 and 25); + +3180 MAP\_AUTHENTICATE (see clauses 8 and 25); + +3181 MAP\_SET\_CIPHERING\_MODE (see clauses 8 and 25); + +3182 MAP\_CHECK\_IMEI (see clauses 8 and 25); + +3183 MAP\_READY\_FOR\_SM (see clauses 12 and 25); + +3184 The following services are certainly used: + +3185 MAP\_REGISTER\_PASSWORD (defined in clause 11); + +3186 MAP\_GET\_PASSWORD (defined in clause 11). + +![Sequence diagram showing interactions between MS, MSC, VLR, and HLR. The diagram consists of four vertical lifelines: MS, MSC, VLR, and HLR. Messages are numbered 1 through 26. Solid arrows represent MAP and A messages, while dashed arrows represent A messages. The sequence starts with MS sending A_CM_SERV_REQ (1) to MSC. MSC then sends MAP_PROCESS_ACCESS_REQUEST (2) to VLR. VLR sends MAP_REGISTER_PASSWORD_req/ind (3) to MSC. MSC sends A_REGISTER_PASSWORD (4) to MS. MSC also sends MAP_REGISTER_PASSWORD_req/ind (5) to HLR. HLR sends MAP_GET_PASSWORD_req/ind (6) to VLR. VLR sends MAP_GET_PASSWORD_req/ind (7) to MSC. MSC sends A_GET_PASSWORD (8) to MS. MS sends A_GET_PASSWORD ack (9) to MSC. MSC sends MAP_GET_PASSWORD_rsp/cnf (10) to VLR. VLR sends MAP_GET_PASSWORD_rsp/cnf (11) to HLR. HLR sends MAP_GET_PASSWORD_req/ind (12) to VLR. VLR sends MAP_GET_PASSWORD_req/ind (13) to MSC. MSC sends A_GET_PASSWORD (14) to MS. MS sends A_GET_PASSWORD ack (15) to MSC. MSC sends MAP_GET_PASSWORD_rsp/cnf (16) to VLR. VLR sends MAP_GET_PASSWORD_rsp/cnf (17) to HLR. HLR sends MAP_GET_PASSWORD_req/ind (18) to VLR. VLR sends MAP_GET_PASSWORD_req/ind (19) to MSC. MSC sends A_GET_PASSWORD (20) to MS. MS sends A_GET_PASSWORD ack (21) to MSC. MSC sends MAP_GET_PASSWORD_rsp/cnf (22) to VLR. VLR sends MAP_GET_PASSWORD_rsp/cnf (23) to HLR. HLR sends MAP_REGISTER_PASSWORD_rsp/cnf (24) to VLR. VLR sends MAP_REGISTER_PASSWORD_rsp/cnf (25) to MSC. MSC sends A_REGISTER_PASSWORD (26) to MS.](5097b7cfd8f956654072fd7cf0fccbb3_img.jpg) + +Sequence diagram showing interactions between MS, MSC, VLR, and HLR. The diagram consists of four vertical lifelines: MS, MSC, VLR, and HLR. Messages are numbered 1 through 26. Solid arrows represent MAP and A messages, while dashed arrows represent A messages. The sequence starts with MS sending A\_CM\_SERV\_REQ (1) to MSC. MSC then sends MAP\_PROCESS\_ACCESS\_REQUEST (2) to VLR. VLR sends MAP\_REGISTER\_PASSWORD\_req/ind (3) to MSC. MSC sends A\_REGISTER\_PASSWORD (4) to MS. MSC also sends MAP\_REGISTER\_PASSWORD\_req/ind (5) to HLR. HLR sends MAP\_GET\_PASSWORD\_req/ind (6) to VLR. VLR sends MAP\_GET\_PASSWORD\_req/ind (7) to MSC. MSC sends A\_GET\_PASSWORD (8) to MS. MS sends A\_GET\_PASSWORD ack (9) to MSC. MSC sends MAP\_GET\_PASSWORD\_rsp/cnf (10) to VLR. VLR sends MAP\_GET\_PASSWORD\_rsp/cnf (11) to HLR. HLR sends MAP\_GET\_PASSWORD\_req/ind (12) to VLR. VLR sends MAP\_GET\_PASSWORD\_req/ind (13) to MSC. MSC sends A\_GET\_PASSWORD (14) to MS. MS sends A\_GET\_PASSWORD ack (15) to MSC. MSC sends MAP\_GET\_PASSWORD\_rsp/cnf (16) to VLR. VLR sends MAP\_GET\_PASSWORD\_rsp/cnf (17) to HLR. HLR sends MAP\_GET\_PASSWORD\_req/ind (18) to VLR. VLR sends MAP\_GET\_PASSWORD\_req/ind (19) to MSC. MSC sends A\_GET\_PASSWORD (20) to MS. MS sends A\_GET\_PASSWORD ack (21) to MSC. MSC sends MAP\_GET\_PASSWORD\_rsp/cnf (22) to VLR. VLR sends MAP\_GET\_PASSWORD\_rsp/cnf (23) to HLR. HLR sends MAP\_REGISTER\_PASSWORD\_rsp/cnf (24) to VLR. VLR sends MAP\_REGISTER\_PASSWORD\_rsp/cnf (25) to MSC. MSC sends A\_REGISTER\_PASSWORD (26) to MS. + +3187 + +3188 + 3189 1) A\_CM\_SERV\_REQ (Note 1) + 3190 2) MAP\_PROCESS\_ACCESS\_REQUEST (Note 2) + 3191 3) A\_REGISTER\_PASSWORD (Note 1) + 3192 4) MAP\_REGISTER\_PASSWORD\_req/ind + 3193 5) MAP\_REGISTER\_PASSWORD\_req/ind + 3194 6) MAP\_GET\_PASSWORD\_req/ind (Note 3) + 3195 7) MAP\_GET\_PASSWORD\_req/ind (Note 3) + 3196 8) A\_GET\_PASSWORD (Note 1, Note 3) + 3197 9) A\_GET\_PASSWORD ack (Note 1, Note 3) + 3198 10) MAP\_GET\_PASSWORD\_rsp/cnf (Note 3) + 3199 11) MAP\_GET\_PASSWORD\_rsp/cnf (Note 3) + 3200 12) MAP\_GET\_PASSWORD\_req/ind (Note 3) + 3201 13) MAP\_GET\_PASSWORD\_req/ind (Note 3) + 3202 14) A\_GET\_PASSWORD (Note 1, Note 3) + 3203 15) A\_GET\_PASSWORD ack (Note 1, Note 3) + 3204 16) MAP\_GET\_PASSWORD\_rsp/cnf (Note 3) + 3205 17) MAP\_GET\_PASSWORD\_rsp/cnf (Note 3) + 3206 18) MAP\_GET\_PASSWORD\_req/ind (Note 3) + 3207 19) MAP\_GET\_PASSWORD\_req/ind (Note 3) + 3208 20) A\_GET\_PASSWORD (Note 1, Note 3) + 3209 21) A\_GET\_PASSWORD ack (Note 1, Note 3) + 3210 22) MAP\_GET\_PASSWORD\_rsp/cnf (Note 3) + 3211 23) MAP\_GET\_PASSWORD\_rsp/cnf (Note 3) + 3212 24) MAP\_REGISTER\_PASSWORD\_rsp/cnf + 3213 25) MAP\_REGISTER\_PASSWORD\_rsp/cnf + 3214 26) A\_REGISTER\_PASSWORD (Note 1) + 3215 + +3216 NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS +3217 24.08x and 3GPP TS 24.09x. Services shown in dotted lines are triggers/ triggered signalling on the radio +3218 path. +3219 NOTE 2: For details of the Process Access Request procedure, refer to clause 25.4 in the present document. +3220 NOTE 3: The use of each of the three MAP\_GET\_PASSWORD operations is described in clause 22.8.4. +3221 +3222 **Figure 22.8.1/1: Message flow for supplementary service password registration** + +## 3223 22.8.2 Procedure in the MSC + +3224 The password registration procedure in the MSC is identical to that for activation specified in clause 22.4.2. All the text +3225 and diagrams in clause 22.4.2 apply with all references to activation changed to password registration. + +## 3226 22.8.3 Procedure in the VLR + +3227 The password registration procedure in the VLR is identical to that for activation specified in clause 22.4.3. All the text +3228 and diagrams in clause 22.4.3 apply with all references to activation changed to password registration. + +## 3229 22.8.4 Procedure in the HLR + +3230 The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +3231 Check\_Indication see clause 25.2.1. + +3232 The HLR shall process the MAP\_REGISTER\_PASSWORD indication as specified in 3GPP TS 23.011 [22]. During +3233 the handling of password registration, the password procedure is initiated (as specified in 3GPP TS 23.011 [22]) This +3234 involves the sending of MAP\_GET\_PASSWORD requests to the VLR. + +3235 The password registration process in the HLR is shown in figure 22.8.4/1. + +![Flowchart for process Register_Password_HLR. It starts with an oval, followed by a 'Null' oval, then a 'MAP_REGISTER_PASSWORD_ind' signal block. A 'Check_Indication' block follows. A decision diamond 'Operator Determined Barring of SS management?' has 'Yes' and 'No' paths. The 'Yes' path leads to 'Set User Error: Call barred' and 'Call barring cause= Operator barring', which then lead to a 'MAP_REGISTER_SS_rsp' and 'MAP_CLOSE_req' block, ending at a crossed-out line. The 'No' path leads to a 'register password' block, then a 'Wait_For_Application_Response' oval. From there, it splits into two parallel paths: one with 'MAP_NOTICE_ind' and 'MAP_U_ABORT_req' blocks, and another with a signal block containing 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind'. Both paths end at a crossed-out line.](1820e5591678c51a3797ca92464a6080_img.jpg) + +**process Register\_Password\_HLR** **RP\_HLR1(2)** + +Process in the HLR to handle a request to register a password for a supplementary service + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the application process PW1/PW2/PW3/PW4 (see 3GPP TS 23.011) + +``` + + graph TD + Start([ ]) --> Null([Null]) + Null --> MAP_REG[MAP_REGISTER_PASSWORD_ind] + MAP_REG --> Check[Check_Indication] + Check --> Decision{Operator Determined Barring of SS management?} + Decision -- Yes --> SetError[Set User Error: Call barred] + SetError --> CallBarring[Call barring cause= Operator barring] + CallBarring --> MAP_RSP[MAP_REGISTER_SS_rsp +MAP_CLOSE_req] + MAP_RSP --> End1((X)) + + Decision -- No --> Register[register password] + Register --> Wait[Wait_For_Application_Response] + + Wait --> MAP_NOTICE[MAP_NOTICE_ind] + Wait --> MAP_ABORT[MAP_P_ABORT_ind, +MAP_U_ABORT_ind, +MAP_CLOSE_ind] + + MAP_NOTICE --> MAP_U_ABORT[MAP_U_ABORT_req] + + MAP_U_ABORT --> End2((X)) + MAP_ABORT --> End2 + +``` + +Flowchart for process Register\_Password\_HLR. It starts with an oval, followed by a 'Null' oval, then a 'MAP\_REGISTER\_PASSWORD\_ind' signal block. A 'Check\_Indication' block follows. A decision diamond 'Operator Determined Barring of SS management?' has 'Yes' and 'No' paths. The 'Yes' path leads to 'Set User Error: Call barred' and 'Call barring cause= Operator barring', which then lead to a 'MAP\_REGISTER\_SS\_rsp' and 'MAP\_CLOSE\_req' block, ending at a crossed-out line. The 'No' path leads to a 'register password' block, then a 'Wait\_For\_Application\_Response' oval. From there, it splits into two parallel paths: one with 'MAP\_NOTICE\_ind' and 'MAP\_U\_ABORT\_req' blocks, and another with a signal block containing 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind'. Both paths end at a crossed-out line. + +3236 + +3237 + +**Figure 22.8.4/1 (sheet 1 of 2): Process Register\_PW\_HLR** + +![State transition diagram for process Register_Password_HLR. It shows states like 'Wait_For_Application_Response', 'Wait_For_Password', and 'Check_Confirmation', and transitions for messages like 'password changed', 'error', 'get password', 'get new password', 'get new password again', 'MAP_REGISTER_PASSWORD_rsp', 'MAP_GET_PASSWORD_req', 'MAP_NOTICE_ind', 'MAP_P_ABORT_ind', 'MAP_U_ABORT_ind', 'MAP_CLOSE_ind', 'SS_Get_Password_Ack', and 'MAP_REGISTER_PASSWORD_rsp'. It also includes error handling for 'Data Error' and 'Provider Error'.](f0c43de2e9993b7f72f164a820ff22f5_img.jpg) + +**process Register\_Password\_HLR** RP\_HLR2(2) + +Process in the HLR to handle a request to register a password for a supplementary service + +``` + +stateDiagram-v2 + [*] --> Wait_For_Application_Response + state "Wait_For_Application_Response" as Wait_For_Application_Response + state "Wait_For_Password" as Wait_For_Password + state "Check_Confirmation" as Check_Confirmation + state "SS_Get_Password_Ack" as SS_Get_Password_Ack + + Wait_For_Application_Response --> password_changed + Wait_For_Application_Response --> error + Wait_For_Application_Response --> get_password + Wait_For_Application_Response --> get_new_password + Wait_For_Application_Response --> get_new_password_again + + get_password --> [*] + get_new_password --> [*] + get_new_password_again --> [*] + + error --> Set_User_Error + Set_User_Error --> password_changed + + password_changed --> MAP_REGISTER_PASSWORD_rsp + MAP_REGISTER_PASSWORD_rsp --> [*] + + get_new_password --> MAP_GET_PASSWORD_req + MAP_GET_PASSWORD_req --> Wait_For_Password + + Wait_For_Password --> MAP_GET_PASSWORD_cnf + Wait_For_Password --> MAP_NOTICE_ind + Wait_For_Password --> MAP_P_ABORT_ind + Wait_For_Password --> MAP_U_ABORT_ind + Wait_For_Password --> MAP_CLOSE_ind + + MAP_GET_PASSWORD_cnf --> Check_Confirmation + Check_Confirmation --> SS_Get_Password_Ack + SS_Get_Password_Ack --> Wait_For_Application_Response + + Check_Confirmation --> Data_Error : Data Error + Check_Confirmation --> Provider_Error : Provider Error + Check_Confirmation --> OK_User_Error : OK, User Error + + Data_Error --> Set_User_Error_System_failure + Set_User_Error_System_failure --> MAP_REGISTER_PASSWORD_rsp + MAP_REGISTER_PASSWORD_rsp --> [*] + + Provider_Error --> [*] + + OK_User_Error --> [*] + + MAP_NOTICE_ind --> MAP_U_ABORT_req + MAP_U_ABORT_req --> [*] + + MAP_P_ABORT_ind --> [*] + MAP_U_ABORT_ind --> [*] + MAP_CLOSE_ind --> [*] + +``` + +State transition diagram for process Register\_Password\_HLR. It shows states like 'Wait\_For\_Application\_Response', 'Wait\_For\_Password', and 'Check\_Confirmation', and transitions for messages like 'password changed', 'error', 'get password', 'get new password', 'get new password again', 'MAP\_REGISTER\_PASSWORD\_rsp', 'MAP\_GET\_PASSWORD\_req', 'MAP\_NOTICE\_ind', 'MAP\_P\_ABORT\_ind', 'MAP\_U\_ABORT\_ind', 'MAP\_CLOSE\_ind', 'SS\_Get\_Password\_Ack', and 'MAP\_REGISTER\_PASSWORD\_rsp'. It also includes error handling for 'Data Error' and 'Provider Error'. + +3238 + +3239 + +**Figure 22.8.4/1 (sheet 2 of 2): Process Register\_PW\_HLR** + +## 3240 22.9 Mobile Initiated USSD procedure + +### 3241 22.9.1 General + +3242 The procedure supports supplementary service signalling procedures which allow PLMN specific services to be +3243 introduced. + +3244 The message flow for the procedure can be found in 3GPP TS 23.090 [34]. + +3245 The following services may be used: + +3246 MAP\_PROCESS\_ACCESS\_REQUEST (see clauses 8 and 25); + +3247 MAP\_TRACE\_SUBSCRIBER\_ACTIVITY (see clauses 9 and 25); + +3248 MAP\_PROVIDE\_IMSI (see clauses 8 and 25); + +3249 MAP\_FORWARD\_NEW\_TMSI (see clauses 8 and 25); + +3250 MAP\_AUTHENTICATE (see clauses 8 and 25); + +3251 MAP\_SET\_CIPHERING\_MODE (see clauses 8 and 25); + +3252 MAP\_CHECK\_IMEI (see clauses 8 and 25); + +3253 MAP\_READY\_FOR\_SM (see clauses 12 and 25); + +3254 MAP\_UNSTRUCTURED\_SS\_REQUEST (defined in clause 11); + +3255 MAP\_UNSTRUCTURED\_SS\_NOTIFY (defined in clause 11). + +3256 The following service is certainly used: + +3257 MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST (defined in clause 11). + +### 3258 22.9.2 Procedure in the MSC + +3259 The process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +3260 Check\_Confirmation see clause 25.2.2. + +3261 The A\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST from the MS contains information input by the user; the +3262 message may be fed to an application contained locally in the MSC or to the VLR. The rules for determining this are +3263 specified in 3GPP TS 23.090 [34]. + +#### 3264 1) Message Destined for the VLR + +3265 If the message is destined for the VLR then the MSC shall transfer the message to the VLR using the mapping specified +3266 in detail in 3GPP TS 29.011 [59]. + +#### 3267 2) Message Destined for the Local Application + +3268 If the message is destined for the local USSD application then the MSC shall transfer the information contained in the +3269 message to the application. + +3270 The process in the MSC is shown in figure 22.9.2/1. + +### 3271 22.9.3 Procedure in the VLR + +3272 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +3273 Receive\_Open\_Cnf see clause 25.1.2; + +3274 Check\_Confirmation see clause 25.2.2; + +3275 Process\_Access\_Request\_VLR see clause 25.4.2. + +3276 The MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST from the MSC contains information input by the user; the +3277 message may be fed to an application contained locally in the VLR or to the HLR. The rules for determining this are +3278 specified in 3GPP TS 23.090 [34]. + +3279 **1) Message Destined for the HLR** + +3280 If the message is destined for the HLR then the VLR shall transfer the message transparently to the HLR. + +3281 **2) Message Destined for the Local Application** + +3282 If the message is destined for the local USSD application then the VLR shall transfer the information contained in the +3283 message to the application. + +3284 The process in the VLR is shown in figure 22.9.3/1. + +## 3285 22.9.4 Procedure in the HLR + +3286 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +3287     Receive\_Open\_Ind       see clause 25.1.1; + +3288     Receive\_Open\_Cnf      see clause 25.1.2; + +3289     Check\_Confirmation    see clause 25.2.2. + +3290 The MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST from the VLR contains information input by the user. If the +3291 alphabet used for the message is understood then the message shall be fed to an application contained locally in the +3292 HLR or to the gsmSCF or to a secondary HLR where the USSD application is located. + +3293 **1) Message Destined for the Local Application** + +3294 If the message is destined for the local USSD application then the HLR shall transfer the information contained in the +3295 message to the local application. + +3296 **2) Message Destined for the gsmSCF or the secondary HLR** + +3297 If the message is destined for the gsmSCF or the secondary HLR then the primary HLR shall transfer the message +3298 transparently to the next node. + +3299 The process in the primary HLR is shown in figure 22.9.4/1. + +## 3300 22.9.5 Procedures in the gsmSCF/secondary HLR + +3301 The MAP process invokes a macro not defined in this clause; the definition of this macros can be found as follows: + +3302     Receive\_Open\_Ind       see clause 25.1.1. + +3303 The process in the gsmSCF or secondary HLR is shown in figure 22.9.5/1. + +![Flowchart for process MS_Init_USSD_MSC. It starts with an oval, followed by 'Wait_For_Service_Indication'. A decision diamond 'Handle in MSC?' (See 3GPP TS 23.090) follows. If 'Yes', it goes to connector '1'. If 'No', it sends 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_req' and 'MAP_DELIMITER_req', then waits for 'PUSSR_Confirm'. From there, it branches into two paths: one for notification (sending 'MAP_UNSTRUCTURED_SS_NOTIFY_ind', receiving 'A_UNSTRUCTURED_SS_NOTIFY_req', waiting for 'USSLN_Confirm', receiving 'A_UNSTRUCTURED_SS_NOTIFY_cnf', sending 'MAP_UNSTRUCTURED_SS_NOTIFY_rsp' and 'MAP_DELIMITER_req', then waiting for 'PUSSR_Confirm'); the other for request (sending 'MAP_UNSTRUCTURED_SS_REQUEST_ind', receiving 'A_UNSTRUCTURED_SS_REQUEST_req', waiting for 'USSLR_Confirm', receiving 'A_UNSTRUCTURED_SS_REQUEST_cnf', sending 'MAP_UNSTRUCTURED_SS_REQUEST_rsp' and 'MAP_DELIMITER_req', then waiting for 'PUSSR_Confirm').](76041f86868a4730a97b21b203d610c7_img.jpg) + +**process MS\_Init\_USSD\_MSC** **MI\_USSD\_MSC1(3)** + +Process in the MSC to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the SS co-ordinating process in the MSC; signals to/from the right are to/from the VLR + +``` + + graph TD + Start([ ]) --> WFS[Wait_For_Service_Indication] + WFS --> A_PU[A_PROCESS_UNSTRUCTURED_SS_REQUEST_ind] + A_PU --> Decision{Handle in MSC? +(See 3GPP TS 23.090)} + Decision -- Yes --> Connector1((1)) + Decision -- No --> MAP_PU_REQ[MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_req +MAP_DELIMITER_req] + MAP_PU_REQ --> WPC[Wait_For_PUSSR_Confirm] + WPC --> Split(( )) + Split --> MAP_UNI_IND[MAP_UNSTRUCTURED_SS_NOTIFY_ind] + Split --> MAP_USR_IND[MAP_UNSTRUCTURED_SS_REQUEST_ind] + MAP_UNI_IND --> AUSN_REQ[A_UNSTRUCTURED_SS_NOTIFY_req] + AUSN_REQ --> WUC[Wait_For_USSLN_Confirm] + WUC --> AUSN_CNF[A_UNSTRUCTURED_SS_NOTIFY_cnf] + AUSN_CNF --> MAP_UNI_RSP[MAP_UNSTRUCTURED_SS_NOTIFY_rsp +MAP_DELIMITER_req] + MAP_UNI_RSP --> WPC2[Wait_For_PUSSR_Confirm] + MAP_USR_IND --> AUSR_REQ[A_UNSTRUCTURED_SS_REQUEST_req] + AUSR_REQ --> WURC[Wait_For_USSLR_Confirm] + WURC --> AUSR_CNF[A_UNSTRUCTURED_SS_REQUEST_cnf] + AUSR_CNF --> MAP_USR_RSP[MAP_UNSTRUCTURED_SS_REQUEST_rsp +MAP_DELIMITER_req] + MAP_USR_RSP --> WPC3[Wait_For_PUSSR_Confirm] + +``` + +Flowchart for process MS\_Init\_USSD\_MSC. It starts with an oval, followed by 'Wait\_For\_Service\_Indication'. A decision diamond 'Handle in MSC?' (See 3GPP TS 23.090) follows. If 'Yes', it goes to connector '1'. If 'No', it sends 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_req' and 'MAP\_DELIMITER\_req', then waits for 'PUSSR\_Confirm'. From there, it branches into two paths: one for notification (sending 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_ind', receiving 'A\_UNSTRUCTURED\_SS\_NOTIFY\_req', waiting for 'USSLN\_Confirm', receiving 'A\_UNSTRUCTURED\_SS\_NOTIFY\_cnf', sending 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_rsp' and 'MAP\_DELIMITER\_req', then waiting for 'PUSSR\_Confirm'); the other for request (sending 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_ind', receiving 'A\_UNSTRUCTURED\_SS\_REQUEST\_req', waiting for 'USSLR\_Confirm', receiving 'A\_UNSTRUCTURED\_SS\_REQUEST\_cnf', sending 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_rsp' and 'MAP\_DELIMITER\_req', then waiting for 'PUSSR\_Confirm'). + +3304 + +3305 + +Figure 22.9.2/1 (sheet 1 of 3): Process MS\_Init\_USSD\_MSC + +![State transition diagram for process MS_Init_USSD_MSC. The diagram shows two main vertical paths. The top path starts with 'Wait_For_PUSSR_Confirm', followed by an input 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_cnf', then 'Check_Confirmation'. From 'Check_Confirmation', an 'OK, User Error, Data Error' output leads to a state with 'A_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp' and 'A_CM_RELEASE_req', which ends with a cross. A 'Provider Error' output from 'Check_Confirmation' leads to a state with 'A_CM_RELEASE_req', which also ends with a cross. The bottom path starts with a state containing 'Wait_For_PUSSR_Confirm, Wait_For_USSN_Confirm, Wait_For_USSR_Confirm'. This state branches into two paths. The left path has an output 'A_CM_SERV_RELEASE_ind', followed by an input 'MAP_U_ABORT_req' leading to 'Application procedure cancellation', then an output 'A_CM_RELEASE_COMPLETE_req', ending with a cross. The right path has an input 'MAP_U_ABORT_ind, MAP_CLOSE_ind', followed by an output 'A_CM_RELEASE_req', ending with a cross.](4ca9477ab422c43c6f5ac022fa8b7baa_img.jpg) + +**process MS\_Init\_USSD\_MSC** **MI\_USSD\_MSC2(3)** + +Process in the MSC to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the SS co-ordinating process in the MSC; signals to/from the right are to/from the VLR + +``` + +stateDiagram-v2 + [*] --> Wait_For_PUSSR_Confirm + state "Wait_For_PUSSR_Confirm" as Wait_For_PUSSR_Confirm + state "Check_Confirmation" as Check_Confirmation + state "A_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp, A_CM_RELEASE_req" as State1 + state "A_CM_RELEASE_req" as State2 + [*] --> Wait_For_PUSSR_Confirm + state "Wait_For_PUSSR_Confirm, Wait_For_USSN_Confirm, Wait_For_USSR_Confirm" as State3 + state "A_CM_SERV_RELEASE_ind" as State4 + state "MAP_U_ABORT_req" as State5 + state "Application procedure cancellation" as State6 + state "A_CM_RELEASE_COMPLETE_req" as State7 + state "MAP_U_ABORT_ind, MAP_CLOSE_ind" as State8 + state "A_CM_RELEASE_req" as State9 + + Wait_For_PUSSR_Confirm --> State1 + State1 --> [*] + Check_Confirmation --> State1 + Check_Confirmation --> State2 + State2 --> [*] + State3 --> State4 + State3 --> State8 + State4 --> State5 + State5 --> State6 + State6 --> State7 + State7 --> [*] + State8 --> State9 + State9 --> [*] + +``` + +State transition diagram for process MS\_Init\_USSD\_MSC. The diagram shows two main vertical paths. The top path starts with 'Wait\_For\_PUSSR\_Confirm', followed by an input 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_cnf', then 'Check\_Confirmation'. From 'Check\_Confirmation', an 'OK, User Error, Data Error' output leads to a state with 'A\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_rsp' and 'A\_CM\_RELEASE\_req', which ends with a cross. A 'Provider Error' output from 'Check\_Confirmation' leads to a state with 'A\_CM\_RELEASE\_req', which also ends with a cross. The bottom path starts with a state containing 'Wait\_For\_PUSSR\_Confirm, Wait\_For\_USSN\_Confirm, Wait\_For\_USSR\_Confirm'. This state branches into two paths. The left path has an output 'A\_CM\_SERV\_RELEASE\_ind', followed by an input 'MAP\_U\_ABORT\_req' leading to 'Application procedure cancellation', then an output 'A\_CM\_RELEASE\_COMPLETE\_req', ending with a cross. The right path has an input 'MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind', followed by an output 'A\_CM\_RELEASE\_req', ending with a cross. + +3306 + +3307 + +**Figure 22.9.2/1 (sheet 2 of 3): Process MS\_Init\_USSD\_MSC** + +process MS\_Init\_USSD\_MSC + +MI\_USSD\_MSC3(3) + +Process in the MSC to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the SS co-ordinating process in the MSC; signals to/from the right are to/from the USSD application process in the MSC unless shown otherwise + +![Sequence diagram for process MS_Init_USSD_MSC. It starts with a connector '1', followed by 'Process Unstructured SS Request', 'MAP CLOSE_req' (to VLR), and 'Wait_For_Application_Response'. It then branches into three paths: 1) 'Unstructured SS Notify' -> 'A_UNSTRUCTURED_SS_NOTIFY_req' -> 'Wait_For_USSN_Confirm_Local' -> 'A_UNSTRUCTURED_SS_NOTIFY_cnf' -> 'Unstructured SS Notify ack' -> 'Wait_For_PUSSR_Confirm'. 2) 'Unstructured SS Request' -> 'A_UNSTRUCTURED_SS_REQUEST_req' -> 'Wait_For_USSR_Confirm_Local' -> 'A_UNSTRUCTURED_SS_REQUEST_cnf' -> 'Unstructured SS Request ack' -> 'Wait_For_PUSSR_Confirm'. 3) A path leading to 'Process Unstructured SS Request ack, Process Unstructured SS Request negative response' -> 'A_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp' / 'A_CM_RELEASE_req'. This path then leads to a state 'Wait_For_Application_Response, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local', which branches to 'A_CM_SERV_RELEASE_ind' (leading to 'Abort' and 'A_CM_RELEASE_COMPLETE_req') and 'Abort' (leading to 'A_CM_SERV_RELEASE_req').](9343540fbb568aaaa5bdd259337839d2_img.jpg) + +``` + +sequenceDiagram + participant 1 as 1 + participant P as Process Unstructured SS Request + participant M as MAP CLOSE_req + participant W as Wait_For_Application_Response + participant U1 as Unstructured SS Notify + participant U2 as Unstructured SS Request + participant P1 as Process Unstructured SS Request ack, Process Unstructured SS Request negative response + participant A1 as A_UNSTRUCTURED_SS_NOTIFY_req + participant A2 as A_UNSTRUCTURED_SS_REQUEST_req + participant A3 as A_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp / A_CM_RELEASE_req + participant W1 as Wait_For_USSN_Confirm_Local + participant W2 as Wait_For_USSR_Confirm_Local + participant W3 as Wait_For_Application_Response, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local + participant A4 as A_UNSTRUCTURED_SS_NOTIFY_cnf + participant A5 as A_UNSTRUCTURED_SS_REQUEST_cnf + participant U3 as Unstructured SS Notify ack + participant U4 as Unstructured SS Request ack + participant W4 as Wait_For_PUSSR_Confirm + participant A6 as A_CM_SERV_RELEASE_ind + participant A7 as A_CM_RELEASE_COMPLETE_req + participant A8 as A_CM_SERV_RELEASE_req + + Note right of P: To VLR + + 1->>P: + P->>M: + M-->>W: + W-->>U1: + W-->>U2: + W-->>P1: + U1->>A1: + A1->>W1: + W1->>A4: + A4->>U3: + U3->>W4: + U2->>A2: + A2->>W2: + W2->>A5: + A5->>U4: + U4->>W4: + P1->>A3: + A3->>W3: + W3->>A6: + A6->>Abort1: + Abort1->>A7: + W3->>Abort2: + Abort2->>A8: + +``` + +Sequence diagram for process MS\_Init\_USSD\_MSC. It starts with a connector '1', followed by 'Process Unstructured SS Request', 'MAP CLOSE\_req' (to VLR), and 'Wait\_For\_Application\_Response'. It then branches into three paths: 1) 'Unstructured SS Notify' -> 'A\_UNSTRUCTURED\_SS\_NOTIFY\_req' -> 'Wait\_For\_USSN\_Confirm\_Local' -> 'A\_UNSTRUCTURED\_SS\_NOTIFY\_cnf' -> 'Unstructured SS Notify ack' -> 'Wait\_For\_PUSSR\_Confirm'. 2) 'Unstructured SS Request' -> 'A\_UNSTRUCTURED\_SS\_REQUEST\_req' -> 'Wait\_For\_USSR\_Confirm\_Local' -> 'A\_UNSTRUCTURED\_SS\_REQUEST\_cnf' -> 'Unstructured SS Request ack' -> 'Wait\_For\_PUSSR\_Confirm'. 3) A path leading to 'Process Unstructured SS Request ack, Process Unstructured SS Request negative response' -> 'A\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_rsp' / 'A\_CM\_RELEASE\_req'. This path then leads to a state 'Wait\_For\_Application\_Response, Wait\_For\_USSN\_Confirm\_Local, Wait\_For\_USSR\_Confirm\_Local', which branches to 'A\_CM\_SERV\_RELEASE\_ind' (leading to 'Abort' and 'A\_CM\_RELEASE\_COMPLETE\_req') and 'Abort' (leading to 'A\_CM\_SERV\_RELEASE\_req'). + +3308 + +3309 + +Figure 22.9.2/1 (sheet 3 of 3): Process MS\_Init\_USSD\_MSC + +![Flowchart for process MS_Init_USSD_VLR. It starts with an oval, followed by 'Null', 'Receive_Open_Ind'. From 'Receive_Open_Ind', 'OK' leads to 'Wait_For_PAR' and 'Vr, Error' leads to 'Null'. From 'Wait_For_PAR', an arrow points to a merge point. From this merge point, one path goes left through a chevron to 'Null' with message 'MAP_U_ABORT_ind, MAP_CLOSE_ind'. The main path goes right to 'Process_Access_Request_VLR'. From 'Process_Access_Request_VLR', 'OK' leads to 'Wait_For_PUSSR_Request' and 'Error' leads to 'Null'. From 'Wait_For_PUSSR_Request', an arrow points to another merge point. From this merge point, one path goes left through a chevron to 'Null' with message 'MAP_CLOSE_ind'. The main path goes right through a chevron to a decision diamond 'Operator Determined Barring of SS management?'. If 'Yes', it goes to 'Set User Error: Call barred' with message 'Call barring cause= Operator barring', then to a chevron with message 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp, MAP_CLOSE_req', and finally to 'Null'. If 'No', it goes to another decision diamond 'Handle in VLR? (See 3GPP TS 23.090)'. If 'Yes', it goes to a circle with number '1'. If 'No', it goes to a chevron with messages 'MAP_OPEN_req, MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_req, MAP_DELIMITER_req', then to 'Receive_Open_Cnf'. From 'Receive_Open_Cnf', 'Vr' leads to a chevron with message 'MAP_U_ABORT_req' and 'Null'. 'Error' leads to 'Set User Error: System failure', then to a chevron with message 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp, MAP_CLOSE_req', and finally to 'Null'. 'OK' leads to 'Wait_For_PUSSR_Confirm'.](fc5d9ea5b3acb1856df98efc488f7c3d_img.jpg) + +**process MS\_Init\_USSD\_VLR** **MI\_USSD\_VLR1(4)** + +Process in the VLR to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the MSC; +signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> Null1[Null] + Null1 --> RecOpenInd[Receive_Open_Ind] + RecOpenInd -- OK --> WaitForPAR[Wait_For_PAR] + RecOpenInd -- Vr, Error --> Null2[Null] + WaitForPAR --> Merge1(( )) + Merge1 --> Chevron1[/ /] + Chevron1 -- "MAP_U_ABORT_ind, MAP_CLOSE_ind" --> Null3[Null] + Merge1 --> ProcessAccessReq[Process_Access_Request_VLR] + ProcessAccessReq -- OK --> WaitForPUSSRReq[Wait_For_PUSSR_Request] + ProcessAccessReq -- Error --> Null4[Null] + WaitForPUSSRReq --> Merge2(( )) + Merge2 --> Chevron2[/ /] + Chevron2 -- "MAP_CLOSE_ind" --> Null5[Null] + Merge2 --> Decision1{Operator Determined Barring of SS management?} + Decision1 -- Yes --> SetUserError1[Set User Error: Call barred] + SetUserError1 -- "Call barring cause= Operator barring" --> Chevron3[/ /] + Chevron3 -- "MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp, MAP_CLOSE_req" --> Null6[Null] + Decision1 -- No --> Decision2{Handle in VLR? (See 3GPP TS 23.090)} + Decision2 -- Yes --> Circle1((1)) + Decision2 -- No --> Chevron4[/ /] + Chevron4 -- "MAP_OPEN_req, MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_req, MAP_DELIMITER_req" --> RecOpenCnf[Receive_Open_Cnf] + RecOpenCnf -- Vr --> Chevron5[/ /] + Chevron5 -- "MAP_U_ABORT_req" --> Null7[Null] + RecOpenCnf -- Error --> SetUserError2[Set User Error: System failure] + SetUserError2 --> Chevron6[/ /] + Chevron6 -- "MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp, MAP_CLOSE_req" --> Null8[Null] + RecOpenCnf -- OK --> WaitForPUSSRCnf[Wait_For_PUSSR_Confirm] + +``` + +Flowchart for process MS\_Init\_USSD\_VLR. It starts with an oval, followed by 'Null', 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', 'OK' leads to 'Wait\_For\_PAR' and 'Vr, Error' leads to 'Null'. From 'Wait\_For\_PAR', an arrow points to a merge point. From this merge point, one path goes left through a chevron to 'Null' with message 'MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind'. The main path goes right to 'Process\_Access\_Request\_VLR'. From 'Process\_Access\_Request\_VLR', 'OK' leads to 'Wait\_For\_PUSSR\_Request' and 'Error' leads to 'Null'. From 'Wait\_For\_PUSSR\_Request', an arrow points to another merge point. From this merge point, one path goes left through a chevron to 'Null' with message 'MAP\_CLOSE\_ind'. The main path goes right through a chevron to a decision diamond 'Operator Determined Barring of SS management?'. If 'Yes', it goes to 'Set User Error: Call barred' with message 'Call barring cause= Operator barring', then to a chevron with message 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_rsp, MAP\_CLOSE\_req', and finally to 'Null'. If 'No', it goes to another decision diamond 'Handle in VLR? (See 3GPP TS 23.090)'. If 'Yes', it goes to a circle with number '1'. If 'No', it goes to a chevron with messages 'MAP\_OPEN\_req, MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_req, MAP\_DELIMITER\_req', then to 'Receive\_Open\_Cnf'. From 'Receive\_Open\_Cnf', 'Vr' leads to a chevron with message 'MAP\_U\_ABORT\_req' and 'Null'. 'Error' leads to 'Set User Error: System failure', then to a chevron with message 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_rsp, MAP\_CLOSE\_req', and finally to 'Null'. 'OK' leads to 'Wait\_For\_PUSSR\_Confirm'. + +3310 + +3311 + +Figure 22.9.3/1 (sheet 1 of 4): Process MS\_Init\_USSD\_VLR + +process MS\_Init\_USSD\_VLR + +MI\_USSD\_VLR2(4) + +Process in the VLR to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR + +![State transition diagram for process MS_Init_USSD_VLR. It shows two main paths starting from 'Wait_For_PUSSR_Confirm'. The left path handles 'Provider Error' via 'MAP_U_ABORT_req' to 'Null'. The right path handles 'OK, User Error, Data Error' via 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp' and 'MAP_CLOSE_req' to 'Null'. A second 'Wait_For_PUSSR_Confirm' state leads to two parallel paths: one for 'MAP_UNSTRUCTURED_SS_NOTIFY_ind' and another for 'MAP_UNSTRUCTURED_SS_REQUEST_ind'. Both paths involve intermediate state transitions and messages like 'MAP_UNSTRUCTURED_SS_NOTIFY_req', 'MAP_DELIMITER_req', 'MAP_UNSTRUCTURED_SS_NOTIFY_rsp', and 'MAP_UNSTRUCTURED_SS_REQUEST_rsp' before returning to 'Wait_For_PUSSR_Confirm'.](93065516414db5e661217149adc134d6_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Wait_For_PUSSR_Confirm + state "Wait_For_PUSSR_Confirm" as Wait_For_PUSSR_Confirm + state "Check_Confirmation" as Check_Confirmation + state "Null" as Null + state "MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp" as MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_U_ABORT_req" as MAP_U_ABORT_req + state "MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_cnf" as MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_cnf + state "MAP_UNSTRUCTURED_SS_NOTIFY_ind" as MAP_UNSTRUCTURED_SS_NOTIFY_ind + state "MAP_UNSTRUCTURED_SS_REQUEST_ind" as MAP_UNSTRUCTURED_SS_REQUEST_ind + state "MAP_UNSTRUCTURED_SS_NOTIFY_req" as MAP_UNSTRUCTURED_SS_NOTIFY_req + state "MAP_DELIMITER_req" as MAP_DELIMITER_req + state "Wait_For_USSN_Confirm" as Wait_For_USSN_Confirm + state "MAP_UNSTRUCTURED_SS_NOTIFY_cnf" as MAP_UNSTRUCTURED_SS_NOTIFY_cnf + state "MAP_UNSTRUCTURED_SS_NOTIFY_rsp" as MAP_UNSTRUCTURED_SS_NOTIFY_rsp + state "MAP_UNSTRUCTURED_SS_REQUEST_cnf" as MAP_UNSTRUCTURED_SS_REQUEST_cnf + state "MAP_UNSTRUCTURED_SS_REQUEST_rsp" as MAP_UNSTRUCTURED_SS_REQUEST_rsp + state "MAP_DELIMITER_req" as MAP_DELIMITER_req + + Wait_For_PUSSR_Confirm --> Check_Confirmation + Check_Confirmation --> Null : Provider Error + Check_Confirmation --> MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp : OK, User Error, Data Error + MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp --> MAP_CLOSE_req + MAP_CLOSE_req --> Null + + Wait_For_PUSSR_Confirm --> MAP_UNSTRUCTURED_SS_NOTIFY_ind + Wait_For_PUSSR_Confirm --> MAP_UNSTRUCTURED_SS_REQUEST_ind + + MAP_UNSTRUCTURED_SS_NOTIFY_ind --> MAP_UNSTRUCTURED_SS_NOTIFY_req + MAP_UNSTRUCTURED_SS_NOTIFY_req --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_USSN_Confirm + Wait_For_USSN_Confirm --> MAP_UNSTRUCTURED_SS_NOTIFY_cnf + MAP_UNSTRUCTURED_SS_NOTIFY_cnf --> MAP_UNSTRUCTURED_SS_NOTIFY_rsp + MAP_UNSTRUCTURED_SS_NOTIFY_rsp --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_PUSSR_Confirm + + MAP_UNSTRUCTURED_SS_REQUEST_ind --> MAP_UNSTRUCTURED_SS_REQUEST_req + MAP_UNSTRUCTURED_SS_REQUEST_req --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_USSR_Confirm + Wait_For_USSR_Confirm --> MAP_UNSTRUCTURED_SS_REQUEST_cnf + MAP_UNSTRUCTURED_SS_REQUEST_cnf --> MAP_UNSTRUCTURED_SS_REQUEST_rsp + MAP_UNSTRUCTURED_SS_REQUEST_rsp --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_PUSSR_Confirm + +``` + +State transition diagram for process MS\_Init\_USSD\_VLR. It shows two main paths starting from 'Wait\_For\_PUSSR\_Confirm'. The left path handles 'Provider Error' via 'MAP\_U\_ABORT\_req' to 'Null'. The right path handles 'OK, User Error, Data Error' via 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_rsp' and 'MAP\_CLOSE\_req' to 'Null'. A second 'Wait\_For\_PUSSR\_Confirm' state leads to two parallel paths: one for 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_ind' and another for 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_ind'. Both paths involve intermediate state transitions and messages like 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_req', 'MAP\_DELIMITER\_req', 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_rsp', and 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_rsp' before returning to 'Wait\_For\_PUSSR\_Confirm'. + +3312 + +3313 + +Figure 22.9.3/1 (sheet 2 of 4): Process MS\_Init\_USSD\_VLR + +![State transition diagram for process MS_Init_USSD_VLR. It starts with an initial state leading to a 'Wait' state. From 'Wait', three transitions are possible: 1) Left to an unlabeled state, then down to 'MAP_U_ABORT_req' and 'Null'. 2) Right to an unlabeled state, then down to 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind'. 3) Right to 'MAP_NOTICE_ind', then down to 'MAP_CLOSE_req', then right to 'MAP_U_ABORT_req' and 'Null'.](bb90121f4f3d2a58df74e15f7918c754_img.jpg) + +**process MS\_Init\_USSD\_VLR** **MI\_USSD\_VLR3(4)** + +Process in the VLR to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Wait + state "Wait_For_PUSSR_Confirm, Wait_For_USSN_Confirm, Wait_For_USSR_Confirm" as Wait + Wait --> S1 + state " " as S1 + S1 --> S2 + state " " as S2 + S1 --> S3 + state "MAP_NOTICE_ind" as S3 + S3 --> S4 + state "MAP_CLOSE_req" as S4 + S4 --> S5 + state "MAP_U_ABORT_req" as S5 + S5 --> Null1 + state "Null" as Null1 + S2 --> S6 + state "MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind" as S6 + S6 --> S5 + S1 --> S7 + state "MAP_U_ABORT_ind, MAP_CLOSE_ind" as S7 + S7 --> S8 + state "MAP_U_ABORT_req" as S8 + S8 --> Null2 + state "Null" as Null2 + +``` + +State transition diagram for process MS\_Init\_USSD\_VLR. It starts with an initial state leading to a 'Wait' state. From 'Wait', three transitions are possible: 1) Left to an unlabeled state, then down to 'MAP\_U\_ABORT\_req' and 'Null'. 2) Right to an unlabeled state, then down to 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind'. 3) Right to 'MAP\_NOTICE\_ind', then down to 'MAP\_CLOSE\_req', then right to 'MAP\_U\_ABORT\_req' and 'Null'. + +3314 + +3315 + +**Figure 22.9.3/1 (sheet 3 of 4): Process\_MS\_Init\_USSD\_VLR** + +![State transition diagram for process MS_Init_USSD_VLR. It starts at state 1, proceeds to 'Process Unstructured SS Request', then 'Wait_For_Application_Response'. From there, it branches into three paths: 1) 'Unstructured SS Notify' -> 'MAP_UNSTRUCTURED_SS_NOTIFY_req' -> 'Wait_For_USSN_Confirm_Local' -> 'MAP_UNSTRUCTURED_SS_NOTIFY_cnf' -> 'Unstructured SS Notify ack' -> 'Wait_For_PUSSR_Confirm'. 2) 'Unstructured SS Request' -> 'MAP_UNSTRUCTURED_SS_REQUEST_req' -> 'Wait_For_USSR_Confirm_Local' -> 'MAP_UNSTRUCTURED_SS_REQUEST_cnf' -> 'Unstructured SS Request ack' -> 'Wait_For_PUSSR_Confirm'. 3) A path leading to 'Process Unstructured SS Request ack, Process Unstructured SS Request negative response' -> 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp' -> 'MAP_CLOSE_req' -> 'Null'. From 'Wait_For_PUSSR_Confirm', it goes to a state with 'Wait_For_Application_Response, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local', which then branches to 'MAP_U_ABORT_ind, MAP_CLOSE_ind' -> 'Abort' -> 'Null' or 'MAP_U_ABORT_req' -> 'Abort' -> 'Null'.](8c9b13e5dffc82125436bced758cb953_img.jpg) + +**process MS\_Init\_USSD\_VLR** **MIUSSD\_VLR4(4)** + +Process in the VLR to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the USSD application process in the VLR + +``` + +stateDiagram-v2 + [*] --> 1 + 1 --> Process_Unstructured_SS_Request : Process Unstructured SS Request + Process_Unstructured_SS_Request --> Wait_For_Application_Response : Wait_For_Application_Response + state "Unstructured SS Notify" as Unstructured_SS_Notify + state "Unstructured SS Request" as Unstructured_SS_Request + state "Process Unstructured SS Request ack, Process Unstructured SS Request negative response" as Process_Ack_Neg + Wait_For_Application_Response --> Unstructured_SS_Notify + Wait_For_Application_Response --> Unstructured_SS_Request + Wait_For_Application_Response --> Process_Ack_Neg + Unstructured_SS_Notify --> MAP_UNSTRUCTURED_SS_NOTIFY_req : MAP_UNSTRUCTURED_SS_NOTIFY_req, MAP_DELIMITER_req + Unstructured_SS_Request --> MAP_UNSTRUCTURED_SS_REQUEST_req : MAP_UNSTRUCTURED_SS_REQUEST_req, MAP_DELIMITER_req + Process_Ack_Neg --> MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp : MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp, MAP_CLOSE_req + MAP_UNSTRUCTURED_SS_NOTIFY_req --> Wait_For_USSN_Confirm_Local : Wait_For_USSN_Confirm_Local + MAP_UNSTRUCTURED_SS_REQUEST_req --> Wait_For_USSR_Confirm_Local : Wait_For_USSR_Confirm_Local + MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp --> Null : Null + Wait_For_USSN_Confirm_Local --> MAP_UNSTRUCTURED_SS_NOTIFY_cnf : MAP_UNSTRUCTURED_SS_NOTIFY_cnf + Wait_For_USSR_Confirm_Local --> MAP_UNSTRUCTURED_SS_REQUEST_cnf : MAP_UNSTRUCTURED_SS_REQUEST_cnf + MAP_UNSTRUCTURED_SS_NOTIFY_cnf --> Unstructured_SS_Notify_ack : Unstructured SS Notify ack + MAP_UNSTRUCTURED_SS_REQUEST_cnf --> Unstructured_SS_Request_ack : Unstructured SS Request ack + Unstructured_SS_Notify_ack --> Wait_For_PUSSR_Confirm : Wait_For_PUSSR_Confirm + Unstructured_SS_Request_ack --> Wait_For_PUSSR_Confirm : Wait_For_PUSSR_Confirm + Wait_For_PUSSR_Confirm --> Wait_For_Application_Response_etc : Wait_For_Application_Response, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local + state "Wait_For_Application_Response, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local" as Wait_For_Application_Response_etc + Wait_For_Application_Response_etc --> MAP_U_ABORT_ind : MAP_U_ABORT_ind, MAP_CLOSE_ind + Wait_For_Application_Response_etc --> MAP_U_ABORT_req : MAP_U_ABORT_req + MAP_U_ABORT_ind --> Abort : Abort + MAP_U_ABORT_req --> Abort : Abort + Abort --> Null : Null + +``` + +State transition diagram for process MS\_Init\_USSD\_VLR. It starts at state 1, proceeds to 'Process Unstructured SS Request', then 'Wait\_For\_Application\_Response'. From there, it branches into three paths: 1) 'Unstructured SS Notify' -> 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_req' -> 'Wait\_For\_USSN\_Confirm\_Local' -> 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_cnf' -> 'Unstructured SS Notify ack' -> 'Wait\_For\_PUSSR\_Confirm'. 2) 'Unstructured SS Request' -> 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_req' -> 'Wait\_For\_USSR\_Confirm\_Local' -> 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_cnf' -> 'Unstructured SS Request ack' -> 'Wait\_For\_PUSSR\_Confirm'. 3) A path leading to 'Process Unstructured SS Request ack, Process Unstructured SS Request negative response' -> 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_rsp' -> 'MAP\_CLOSE\_req' -> 'Null'. From 'Wait\_For\_PUSSR\_Confirm', it goes to a state with 'Wait\_For\_Application\_Response, Wait\_For\_USSN\_Confirm\_Local, Wait\_For\_USSR\_Confirm\_Local', which then branches to 'MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' -> 'Abort' -> 'Null' or 'MAP\_U\_ABORT\_req' -> 'Abort' -> 'Null'. + +3316 + +3317 + +**Figure 22.9.3/1 (sheet 4 of 4): Process\_MS\_Init\_USSD\_VLR** + +3318 + +**Figure 22.9.3/2 void** + +![Flowchart for process MS_Init_USSD_HLR. The process starts with an entry point, followed by 'Null', 'Receive_Open_Ind'. From 'Receive_Open_Ind', an 'Error' path leads to 'Perform MAP Vr dialogue' and then 'Null'. An 'OK' path leads to 'Wait_For_Service_Indication'. From 'Wait_For_Service_Indication', the flow goes to a decision diamond 'Operator Determined Barring of SS management?'. If 'Yes', it goes to 'Set User Error: Call barred' -> 'Call barring cause= Operator barring' -> 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp' -> 'MAP_CLOSE_req' -> 'Null'. If 'No', it goes to 'Alphabet supported?'. If 'Yes', it goes to 'Handle in HLR? (See 3GPP TS 23.090)' -> '1'. If 'No', it goes to 'Set User Error: Unknown alphabet' -> 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp' -> 'MAP_CLOSE_req' -> 'Null'. From 'Handle in HLR? (See 3GPP TS 23.090)' if 'Yes', it goes to 'MAP_OPEN_req' -> 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_req' -> 'MAP_DELIMITER_req' -> 'Receive_Open_Cnf'. From 'Receive_Open_Cnf', an 'Error' path leads to 'Set User Error: System failure' -> 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp' -> 'MAP_CLOSE_req' -> 'Null'. An 'OK' path leads to 'Wait_For_PUSSR_Confirm' -> 'Null'. A 'Vr' path leads to 'MAP_U_ABORT_req' -> 'Null'.](bbb098bf9218bf7be1e8e037ed2327f0_img.jpg) + +**process MS\_Init\_USSD\_HLR** **MI\_USSD\_HLR1(4)** + +Process in the HLR to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the VLR; + signals to/from the right are to/from the next node (gsmSCF or secondary HLR) + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind -- Error --> Perform_MAP_Vr_dialogue[Perform MAP Vr dialogue] + Perform_MAP_Vr_dialogue --> Null2([Null]) + Receive_Open_Ind -- OK --> Wait_For_Service_Indication[Wait_For_Service_Indication] + Wait_For_Service_Indication --> Operator_Determined_Barring{Operator Determined Barring of SS management?} + Operator_Determined_Barring -- Yes --> Set_User_Error_Call_barred[Set User Error: Call barred] + Set_User_Error_Call_barred --> Call_barring_cause[Call barring cause= Operator barring] + Call_barring_cause --> MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp1[MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp] + MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp1 --> MAP_CLOSE_req1[MAP_CLOSE_req] + MAP_CLOSE_req1 --> Null3([Null]) + Operator_Determined_Barring -- No --> Alphabet_supported{Alphabet supported?} + Alphabet_supported -- Yes --> Handle_in_HLR{Handle in HLR? (See 3GPP TS 23.090)} + Handle_in_HLR -- Yes --> Connector1((1)) + Handle_in_HLR -- No --> MAP_OPEN_req[MAP_OPEN_req] + MAP_OPEN_req --> MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_req[MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_req] + MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_req --> MAP_DELIMITER_req[MAP_DELIMITER_req] + MAP_DELIMITER_req --> Receive_Open_Cnf[Receive_Open_Cnf] + Receive_Open_Cnf -- Error --> Set_User_Error_System_failure[Set User Error: System failure] + Set_User_Error_System_failure --> MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp2[MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp] + MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp2 --> MAP_CLOSE_req2[MAP_CLOSE_req] + MAP_CLOSE_req2 --> Null4([Null]) + Receive_Open_Cnf -- OK --> Wait_For_PUSSR_Confirm[Wait_For_PUSSR_Confirm] + Wait_For_PUSSR_Confirm --> Null5([Null]) + Receive_Open_Cnf -- Vr --> MAP_U_ABORT_req[MAP_U_ABORT_req] + MAP_U_ABORT_req --> Null6([Null]) + Alphabet_supported -- No --> Set_User_Error_Unknown_alphabet[Set User Error: Unknown alphabet] + Set_User_Error_Unknown_alphabet --> MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp3[MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp] + MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp3 --> MAP_CLOSE_req3[MAP_CLOSE_req] + MAP_CLOSE_req3 --> Null7([Null]) + +``` + +Flowchart for process MS\_Init\_USSD\_HLR. The process starts with an entry point, followed by 'Null', 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', an 'Error' path leads to 'Perform MAP Vr dialogue' and then 'Null'. An 'OK' path leads to 'Wait\_For\_Service\_Indication'. From 'Wait\_For\_Service\_Indication', the flow goes to a decision diamond 'Operator Determined Barring of SS management?'. If 'Yes', it goes to 'Set User Error: Call barred' -> 'Call barring cause= Operator barring' -> 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_rsp' -> 'MAP\_CLOSE\_req' -> 'Null'. If 'No', it goes to 'Alphabet supported?'. If 'Yes', it goes to 'Handle in HLR? (See 3GPP TS 23.090)' -> '1'. If 'No', it goes to 'Set User Error: Unknown alphabet' -> 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_rsp' -> 'MAP\_CLOSE\_req' -> 'Null'. From 'Handle in HLR? (See 3GPP TS 23.090)' if 'Yes', it goes to 'MAP\_OPEN\_req' -> 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_req' -> 'MAP\_DELIMITER\_req' -> 'Receive\_Open\_Cnf'. From 'Receive\_Open\_Cnf', an 'Error' path leads to 'Set User Error: System failure' -> 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_rsp' -> 'MAP\_CLOSE\_req' -> 'Null'. An 'OK' path leads to 'Wait\_For\_PUSSR\_Confirm' -> 'Null'. A 'Vr' path leads to 'MAP\_U\_ABORT\_req' -> 'Null'. + +3319 + +3320 + +Figure 22.9.4/1 (sheet 1 of 4): Process MS\_Init\_USSD\_HLR + +process MS\_Init\_USSD\_HLR + +MI\_USSD\_HLR2(4) + +Process in the HLR to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the next node (gsmSCF or secondary HLR) + +![State transition diagram for process MS_Init_USSD_HLR. It shows two main paths starting from 'Wait_For_PUSSR_Confirm'. The first path handles a 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_cnf' and then checks for a confirmation, leading to either an abort or a response. The second path handles 'MAP_UNSTRUCTURED_SS_NOTIFY_ind' and 'MAP_UNSTRUCTURED_SS_REQUEST_ind' signals, followed by a series of request/response exchanges and delimiter handling, ending in another 'Wait_For_PUSSR_Confirm' state.](ae10a7e5d67793deb1d25f3bb963e76e_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Wait_For_PUSSR_Confirm + state "Wait_For_PUSSR_Confirm" as Wait_For_PUSSR_Confirm + state "Check_Confirmation" as Check_Confirmation + state "MAP_U_ABORT_req" as MAP_U_ABORT_req + state "Null" as Null + state "MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_cnf" as MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_cnf + state "MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp" as MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_UNSTRUCTURED_SS_NOTIFY_ind" as MAP_UNSTRUCTURED_SS_NOTIFY_ind + state "MAP_UNSTRUCTURED_SS_REQUEST_ind" as MAP_UNSTRUCTURED_SS_REQUEST_ind + state "MAP_UNSTRUCTURED_SS_NOTIFY_req" as MAP_UNSTRUCTURED_SS_NOTIFY_req + state "MAP_DELIMITER_req" as MAP_DELIMITER_req + state "Wait_For_USSN_Confirm" as Wait_For_USSN_Confirm + state "MAP_UNSTRUCTURED_SS_NOTIFY_cnf" as MAP_UNSTRUCTURED_SS_NOTIFY_cnf + state "MAP_UNSTRUCTURED_SS_NOTIFY_rsp" as MAP_UNSTRUCTURED_SS_NOTIFY_rsp + state "MAP_UNSTRUCTURED_SS_REQUEST_cnf" as MAP_UNSTRUCTURED_SS_REQUEST_cnf + state "MAP_UNSTRUCTURED_SS_REQUEST_rsp" as MAP_UNSTRUCTURED_SS_REQUEST_rsp + state "Wait_For_PUSSR_Confirm_2" as Wait_For_PUSSR_Confirm + + Wait_For_PUSSR_Confirm --> MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_cnf + MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_cnf --> Check_Confirmation + Check_Confirmation --> MAP_U_ABORT_req : Provider Error + Check_Confirmation --> MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp : OK, User Error, Data Error + Check_Confirmation --> MAP_CLOSE_req : OK, User Error, Data Error + MAP_U_ABORT_req --> Null + MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp --> Null + MAP_CLOSE_req --> Null + + Wait_For_PUSSR_Confirm --> MAP_UNSTRUCTURED_SS_NOTIFY_ind + Wait_For_PUSSR_Confirm --> MAP_UNSTRUCTURED_SS_REQUEST_ind + MAP_UNSTRUCTURED_SS_NOTIFY_ind --> MAP_UNSTRUCTURED_SS_NOTIFY_req + MAP_UNSTRUCTURED_SS_NOTIFY_ind --> MAP_DELIMITER_req + MAP_UNSTRUCTURED_SS_NOTIFY_req --> Wait_For_USSN_Confirm + MAP_DELIMITER_req --> Wait_For_USSN_Confirm + Wait_For_USSN_Confirm --> MAP_UNSTRUCTURED_SS_NOTIFY_cnf + MAP_UNSTRUCTURED_SS_NOTIFY_cnf --> MAP_UNSTRUCTURED_SS_NOTIFY_rsp + MAP_UNSTRUCTURED_SS_NOTIFY_cnf --> MAP_DELIMITER_req + MAP_UNSTRUCTURED_SS_NOTIFY_rsp --> Wait_For_PUSSR_Confirm_2 + MAP_DELIMITER_req --> Wait_For_PUSSR_Confirm_2 + + MAP_UNSTRUCTURED_SS_REQUEST_ind --> MAP_UNSTRUCTURED_SS_REQUEST_req + MAP_UNSTRUCTURED_SS_REQUEST_ind --> MAP_DELIMITER_req + MAP_UNSTRUCTURED_SS_REQUEST_req --> Wait_For_USSN_Confirm + MAP_DELIMITER_req --> Wait_For_USSN_Confirm + Wait_For_USSN_Confirm --> MAP_UNSTRUCTURED_SS_REQUEST_cnf + MAP_UNSTRUCTURED_SS_REQUEST_cnf --> MAP_UNSTRUCTURED_SS_REQUEST_rsp + MAP_UNSTRUCTURED_SS_REQUEST_cnf --> MAP_DELIMITER_req + MAP_UNSTRUCTURED_SS_REQUEST_rsp --> Wait_For_PUSSR_Confirm_2 + MAP_DELIMITER_req --> Wait_For_PUSSR_Confirm_2 + +``` + +State transition diagram for process MS\_Init\_USSD\_HLR. It shows two main paths starting from 'Wait\_For\_PUSSR\_Confirm'. The first path handles a 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_cnf' and then checks for a confirmation, leading to either an abort or a response. The second path handles 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_ind' and 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_ind' signals, followed by a series of request/response exchanges and delimiter handling, ending in another 'Wait\_For\_PUSSR\_Confirm' state. + +3321 + +3322 + +Figure 22.9.4/1 (sheet 2 of 4): Process MS\_Init\_USSD\_HLR + +![State transition diagram for process MS_Init_USSD_HLR. It starts with an initial state leading to a 'Wait' state. From 'Wait', it branches into two parallel paths. The left path goes through 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' to a merge point, then 'MAP_NOTICE_ind' to 'MAP_CLOSE_req', then 'MAP_U_ABORT_req' to 'Null'. The right path goes through 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' to another merge point, then 'MAP_NOTICE_ind' to 'MAP_CLOSE_req', then 'MAP_U_ABORT_req' to 'Null'. Both merge points lead to the 'MAP_U_ABORT_req' state.](9c366736af445890a3e1dd2b9c1651a5_img.jpg) + +**process MS\_Init\_USSD\_HLR** **MI\_USSD\_HLR3(4)** + +Process in the HLR to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the next node (gsmSCF or secondary HLR) + +Wait\_For\_PUSSR\_Confirm, +Wait\_For\_USSN\_Confirm, +Wait\_For\_USSR\_Confirm, + +``` + +stateDiagram-v2 + [*] --> Wait + state "Wait_For_PUSSR_Confirm, Wait_For_USSN_Confirm, Wait_For_USSR_Confirm," as Wait + Wait --> LeftMerge + Wait --> RightMerge + state "MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind" as LeftMerge + state "MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind" as RightMerge + LeftMerge --> LeftNotice + RightMerge --> RightNotice + state "MAP_NOTICE_ind" as LeftNotice + state "MAP_NOTICE_ind" as RightNotice + LeftNotice --> LeftCloseReq + RightNotice --> RightCloseReq + state "MAP_CLOSE_req" as LeftCloseReq + state "MAP_CLOSE_req" as RightCloseReq + LeftCloseReq --> LeftAbortReq + RightCloseReq --> RightAbortReq + state "MAP_U_ABORT_req" as LeftAbortReq + state "MAP_U_ABORT_req" as RightAbortReq + LeftAbortReq --> Null1 + RightAbortReq --> Null2 + state "Null" as Null1 + state "Null" as Null2 + +``` + +State transition diagram for process MS\_Init\_USSD\_HLR. It starts with an initial state leading to a 'Wait' state. From 'Wait', it branches into two parallel paths. The left path goes through 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' to a merge point, then 'MAP\_NOTICE\_ind' to 'MAP\_CLOSE\_req', then 'MAP\_U\_ABORT\_req' to 'Null'. The right path goes through 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' to another merge point, then 'MAP\_NOTICE\_ind' to 'MAP\_CLOSE\_req', then 'MAP\_U\_ABORT\_req' to 'Null'. Both merge points lead to the 'MAP\_U\_ABORT\_req' state. + +3323 + +3324 + +Figure 22.9.4/1 (sheet 3 of 4): Process MS\_Init\_USSD\_HLR + +![State transition diagram for process MS_Init_USSD_HLR. The process starts at state 1, proceeds to 'Process Unstructured SS Request', then 'Wait_For_Application_Response'. It then branches into three paths: 1) 'Unstructured SS Notify' leading to 'MAP_UNSTRUCTURED_SS_NOTIFY_req', 'Wait_For_USSN_Confirm_Local', 'MAP_UNSTRUCTURED_SS_NOTIFY_cnf', 'Unstructured SS Notify ack', and 'Wait_For_PUSSR_Confirm'. 2) 'Unstructured SS Request' leading to 'MAP_UNSTRUCTURED_SS_REQUEST_req', 'Wait_For_USSR_Confirm_Local', 'MAP_UNSTRUCTURED_SS_REQUEST_cnf', 'Unstructured SS Request ack', and 'Wait_For_PUSSR_Confirm'. 3) A negative response path leading to 'Process Unstructured SS Request ack, Process Unstructured SS Request negative response', 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp', 'MAP_CLOSE_req', and 'Null'. Both 'Wait_For_PUSSR_Confirm' states lead to a common state with a note: 'Wait_For_PUSSR_Confirm, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local'. From this state, it branches into: 1) 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' leading to 'Abort' and 'Null'. 2) 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req' and then 'Abort' and 'Null'. 3) 'Abort' leading to 'MAP_U_ABORT_req' and 'Null'.](6c759550c6d07880e10c4374ad85c181_img.jpg) + +**process MS\_Init\_USSD\_HLR** **MI\_USSD\_HLR4(4)** + +Process in the HLR to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the USSD application process in the HLR + +``` + +stateDiagram-v2 + [*] --> 1 + 1 --> Process_Unstructured_SS_Request: Process Unstructured SS Request + Process_Unstructured_SS_Request --> Wait_For_Application_Response: Wait_For_Application_Response + state "Unstructured SS Notify" as Unstructured_SS_Notify + state "Unstructured SS Request" as Unstructured_SS_Request + state "Process Unstructured SS Request ack, Process Unstructured SS Request negative response" as Negative_Response + Unstructured_SS_Notify --> MAP_UNSTRUCTURED_SS_NOTIFY_req: MAP_UNSTRUCTURED_SS_NOTIFY_req, MAP_DELIMITER_req + MAP_UNSTRUCTURED_SS_NOTIFY_req --> Wait_For_USSN_Confirm_Local: Wait_For_USSN_Confirm_Local + Wait_For_USSN_Confirm_Local --> MAP_UNSTRUCTURED_SS_NOTIFY_cnf: MAP_UNSTRUCTURED_SS_NOTIFY_cnf + MAP_UNSTRUCTURED_SS_NOTIFY_cnf --> Unstructured_SS_Notify_ack: Unstructured SS Notify ack + Unstructured_SS_Notify_ack --> Wait_For_PUSSR_Confirm_1: Wait_For_PUSSR_Confirm + Unstructured_SS_Request --> MAP_UNSTRUCTURED_SS_REQUEST_req: MAP_UNSTRUCTURED_SS_REQUEST_req, MAP_DELIMITER_req + MAP_UNSTRUCTURED_SS_REQUEST_req --> Wait_For_USSR_Confirm_Local: Wait_For_USSR_Confirm_Local + Wait_For_USSR_Confirm_Local --> MAP_UNSTRUCTURED_SS_REQUEST_cnf: MAP_UNSTRUCTURED_SS_REQUEST_cnf + MAP_UNSTRUCTURED_SS_REQUEST_cnf --> Unstructured_SS_Request_ack: Unstructured SS Request ack + Unstructured_SS_Request_ack --> Wait_For_PUSSR_Confirm_2: Wait_For_PUSSR_Confirm + Negative_Response --> MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp: MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp, MAP_CLOSE_req + MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp --> Null_1: Null + Wait_For_PUSSR_Confirm_1 --> Common_Wait: Wait_For_PUSSR_Confirm, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local + Wait_For_PUSSR_Confirm_2 --> Common_Wait + Common_Wait --> MAP_P_ABORT_ind: MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind + MAP_P_ABORT_ind --> Abort_1: Abort + Abort_1 --> Null_2: Null + Common_Wait --> MAP_NOTICE_ind: MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req_2: MAP_CLOSE_req + MAP_CLOSE_req_2 --> Abort_2: Abort + Abort_2 --> Null_3: Null + Common_Wait --> Abort_3: Abort + Abort_3 --> MAP_U_ABORT_req: MAP_U_ABORT_req + MAP_U_ABORT_req --> Null_4: Null + +``` + +State transition diagram for process MS\_Init\_USSD\_HLR. The process starts at state 1, proceeds to 'Process Unstructured SS Request', then 'Wait\_For\_Application\_Response'. It then branches into three paths: 1) 'Unstructured SS Notify' leading to 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_req', 'Wait\_For\_USSN\_Confirm\_Local', 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_cnf', 'Unstructured SS Notify ack', and 'Wait\_For\_PUSSR\_Confirm'. 2) 'Unstructured SS Request' leading to 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_req', 'Wait\_For\_USSR\_Confirm\_Local', 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_cnf', 'Unstructured SS Request ack', and 'Wait\_For\_PUSSR\_Confirm'. 3) A negative response path leading to 'Process Unstructured SS Request ack, Process Unstructured SS Request negative response', 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_rsp', 'MAP\_CLOSE\_req', and 'Null'. Both 'Wait\_For\_PUSSR\_Confirm' states lead to a common state with a note: 'Wait\_For\_PUSSR\_Confirm, Wait\_For\_USSN\_Confirm\_Local, Wait\_For\_USSR\_Confirm\_Local'. From this state, it branches into: 1) 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' leading to 'Abort' and 'Null'. 2) 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req' and then 'Abort' and 'Null'. 3) 'Abort' leading to 'MAP\_U\_ABORT\_req' and 'Null'. + +3325 + +3326 + +Figure 22.9.4/1 (sheet 4 of 4): Process MS\_Init\_USSD\_HLR + +process MS\_INIT\_USSD\_gsmSCF\_Secondary\_HLR + +MI\_USSD\_SCF1(2) + +Process in the gsmSCF or secondary HLR to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the USSD application process + +![Flowchart for process MS_INIT_USSD_gsmSCF_Secondary_HLR. The process starts with an entry point leading to 'Null', then 'Receive_Open_ind'. From 'Receive_Open_ind', an 'Error' path leads to 'Perform MAP Vr dialogue' and then 'Null'. An 'OK' path leads to 'Wait_For_Service_Indication', which then leads to a merge point for 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_ind'. This is followed by 'Process Unstructured SS Request' and 'Wait_For_Application_Response'. From 'Wait_For_Application_Response', three paths emerge: 1) 'Unstructured SS Notify' leading to a merge point for 'MAP_UNSTRUCTURED_SS_NOTIFY_req' and 'MAP_DELIMITER_req', then 'Wait_For_USSN_Confirm_Local', then a merge point for 'MAP_UNSTRUCTURED_SS_NOTIFY_cnf', then 'Unstructured SS Notify ack', and finally 'Wait_For_PUSSR_Confirm'. 2) 'Unstructured SS Request' leading to a merge point for 'MAP_UNSTRUCTURED_SS_REQUEST_req' and 'MAP_DELIMITER_req', then 'Wait_For_USSR_Confirm_Local', then a merge point for 'MAP_UNSTRUCTURED_SS_REQUEST_cnf', then 'Unstructured SS Request ack', and finally 'Wait_For_PUSSR_Confirm'. 3) A path leading to a merge point for 'Process Unstructured SS Request ack, Process Unstructured SS Request negative response', then a merge point for 'MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp' and 'MAP_CLOSE_req', and finally 'Null'.](66478ca94b9cd879c8980a6a91490faf_img.jpg) + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_ind[Receive_Open_ind] + Receive_Open_ind -- Error --> Perform_MAP_Vr_dialogue[Perform MAP Vr dialogue] + Perform_MAP_Vr_dialogue --> Null2([Null]) + Receive_Open_ind -- OK --> Wait_For_Service_Indication[Wait_For_Service_Indication] + Wait_For_Service_Indication --> Merge1{ } + Merge1 --> MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_ind[MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_ind] + MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_ind --> Process_Unstructured_SS_Request[/Process Unstructured SS Request/] + Process_Unstructured_SS_Request --> Wait_For_Application_Response[Wait_For_Application_Response] + Wait_For_Application_Response --> Merge2{ } + Merge2 --> Unstructured_SS_Notify[/Unstructured SS Notify/] + Merge2 --> Unstructured_SS_Request[/Unstructured SS Request/] + Merge2 --> Merge3{ } + Unstructured_SS_Notify --> Merge4{ } + Merge4 --> MAP_UNSTRUCTURED_SS_NOTIFY_req[MAP_UNSTRUCTURED_SS_NOTIFY_req +MAP_DELIMITER_req] + MAP_UNSTRUCTURED_SS_NOTIFY_req --> Wait_For_USSN_Confirm_Local[Wait_For_USSN_Confirm_Local] + Wait_For_USSN_Confirm_Local --> Merge5{ } + Merge5 --> MAP_UNSTRUCTURED_SS_NOTIFY_cnf[MAP_UNSTRUCTURED_SS_NOTIFY_cnf] + MAP_UNSTRUCTURED_SS_NOTIFY_cnf --> Unstructured_SS_Notify_ack[/Unstructured SS Notify ack/] + Unstructured_SS_Notify_ack --> Wait_For_PUSSR_Confirm1[Wait_For_PUSSR_Confirm] + Unstructured_SS_Request --> Merge6{ } + Merge6 --> MAP_UNSTRUCTURED_SS_REQUEST_req[MAP_UNSTRUCTURED_SS_REQUEST_req +MAP_DELIMITER_req] + MAP_UNSTRUCTURED_SS_REQUEST_req --> Wait_For_USSR_Confirm_Local[Wait_For_USSR_Confirm_Local] + Wait_For_USSR_Confirm_Local --> Merge7{ } + Merge7 --> MAP_UNSTRUCTURED_SS_REQUEST_cnf[MAP_UNSTRUCTURED_SS_REQUEST_cnf] + MAP_UNSTRUCTURED_SS_REQUEST_cnf --> Unstructured_SS_Request_ack[/Unstructured SS Request ack/] + Unstructured_SS_Request_ack --> Wait_For_PUSSR_Confirm2[Wait_For_PUSSR_Confirm] + Merge3 --> Merge8{ } + Merge8 --> Process_Unstructured_SS_Request_ack[Process Unstructured SS Request ack, +Process Unstructured SS Request negative response] + Process_Unstructured_SS_Request_ack --> Merge9{ } + Merge9 --> MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp[MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp +MAP_CLOSE_req] + MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp --> Null3([Null]) + +``` + +Flowchart for process MS\_INIT\_USSD\_gsmSCF\_Secondary\_HLR. The process starts with an entry point leading to 'Null', then 'Receive\_Open\_ind'. From 'Receive\_Open\_ind', an 'Error' path leads to 'Perform MAP Vr dialogue' and then 'Null'. An 'OK' path leads to 'Wait\_For\_Service\_Indication', which then leads to a merge point for 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_ind'. This is followed by 'Process Unstructured SS Request' and 'Wait\_For\_Application\_Response'. From 'Wait\_For\_Application\_Response', three paths emerge: 1) 'Unstructured SS Notify' leading to a merge point for 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_req' and 'MAP\_DELIMITER\_req', then 'Wait\_For\_USSN\_Confirm\_Local', then a merge point for 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_cnf', then 'Unstructured SS Notify ack', and finally 'Wait\_For\_PUSSR\_Confirm'. 2) 'Unstructured SS Request' leading to a merge point for 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_req' and 'MAP\_DELIMITER\_req', then 'Wait\_For\_USSR\_Confirm\_Local', then a merge point for 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_cnf', then 'Unstructured SS Request ack', and finally 'Wait\_For\_PUSSR\_Confirm'. 3) A path leading to a merge point for 'Process Unstructured SS Request ack, Process Unstructured SS Request negative response', then a merge point for 'MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST\_rsp' and 'MAP\_CLOSE\_req', and finally 'Null'. + +3327 + +3328 + +Figure 22.9.5/1 (sheet 1 of 2): Process MS\_Init\_USSD\_gsmSCF\_Secondary\_HLR + +process MS\_INIT\_USSD\_gsmSCF\_Secondary\_HLR + +MI\_USSD\_SCF2(2) + +Process in the gsmSCF or secondary HLR to handle an MS initiated USSD transaction + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the USSD application process + +![State transition diagram for process MS_INIT_USSD_gsmSCF_Secondary_HLR. It shows transitions between states based on MAP messages like P_ABORT, U_ABORT, CLOSE, NOTICE, and U_ABORT requests, leading to Null states or Abort states.](97d40ecf574c206406b1674e364a0484_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Wait_For_PUSSR_Confirm + state "Wait_For_PUSSR_Confirm, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local" as Wait_For_PUSSR_Confirm + state "MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind" as Left_External + state "MAP_NOTICE_ind" as Right_External + state "MAP_CLOSE_req" as Right_External + state "Abort" as Left_External + state "MAP_U_ABORT_req" as Right_External + state "Null" as Left_End + state "Null" as Right_End + + Wait_For_PUSSR_Confirm --> Left_External + Wait_For_PUSSR_Confirm --> Right_External + Wait_For_PUSSR_Confirm --> Right_External + Left_External --> Right_External + Right_External --> Right_External + Right_External --> Left_External + Right_External --> Left_End + Right_External --> Right_End + +``` + +State transition diagram for process MS\_INIT\_USSD\_gsmSCF\_Secondary\_HLR. It shows transitions between states based on MAP messages like P\_ABORT, U\_ABORT, CLOSE, NOTICE, and U\_ABORT requests, leading to Null states or Abort states. + +3329 + +3330 + +Figure 22.9.5/1 (sheet 2 of 2): Process MS\_Init\_USSD\_gsmSCF\_Secondary\_HLR + +## 3331 22.10 Network initiated USSD procedure + +### 3332 22.10.1 General + +3333 The procedure supports supplementary service signalling procedures which allow PLMN specific services to be +3334 introduced. + +3335 The message flow for the procedure can be found in 3GPP TS 23.090 [34]. + +3336 The following services may be used: + +- 3337 MAP\_PAGE (see clauses 8 and 25); +- 3338 MAP\_SEARCH\_FOR\_MOBILE\_SUBSCRIBER (see clauses 8 and 25); +- 3339 MAP\_PROCESS\_ACCESS\_REQUEST (see clauses 8 and 25); +- 3340 MAP\_AUTHENTICATE (see clauses 8 and 25); +- 3341 MAP\_SET\_CIPHERING\_MODE (see clauses 8 and 25); +- 3342 MAP\_FORWARD\_NEW\_TMSI (see clauses 8 and 25); +- 3343 MAP\_READY\_FOR\_SM (see clauses 12 and 25). + +3344 At least one of the following services will certainly be used, and both may be used: + +- 3345 MAP\_UNSTRUCTURED\_SS\_REQUEST (defined in clause 11); +- 3346 MAP\_UNSTRUCTURED\_SS\_NOTIFY (defined in clause 11). + +### 3347 22.10.2 Procedure in the MSC + +3348 The process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +- 3349 Receive\_Open\_Ind see clause 25.1.1; +- 3350 Receive\_Open\_Cnf see clause 25.1.2; +- 3351 Page\_MSC see clause 25.3.1; +- 3352 Search\_For\_MS\_MSC see clause 25.3.2; +- 3353 Process\_Access\_Request\_MSC see clause 25.4.1. + +3354 The process in the MSC is shown in figure 22.10.2/1. + +### 3355 22.10.3 Procedure in the VLR + +3356 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +- 3357 Receive\_Open\_Ind see clause 25.1.1; +- 3358 Receive\_Open\_Cnf see clause 25.1.2; +- 3359 Check\_Indication see clause 25.2.1; +- 3360 Check\_Confirmation see clause 25.2.2. + +3361 The process in the VLR is shown in figure 22.10.3/1. + +### 3362 MSC Initiated USSD + +3363 If a USSD application in the MSC wishes to use the network initiated USSD procedure, and a connection to the MS +3364 does not exist then the MSC opens a dialogue with the VLR. This dialogue leads to the VLR performing page or search +3365 using the macro Start\_USSD\_VLR. + +3366 **Macro Start\_USSD\_VLR** + +3367 The macro invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +3368     Check\_Confirmation     see clause 25.2.1; + +3369     Process\_Access\_Request\_VLR see clause 25.4.2. + +3370 The macro is shown in figure 22.10.3/2. + +## 3371 22.10.4 Procedure in the HLR + +3372 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +3373     Receive\_Open\_Ind     see clause 25.1.1; + +3374     Receive\_Open\_Cnf     see clause 25.1.2; + +3375     Check\_Indication     see clause 25.2.1; + +3376     Check\_Confirmation     see clause 25.2.2. + +3377 The process in the primary HLR is shown in figures 22.10.4/1 and 22.10.4/2. + +## 3378 22.10.5 Procedure in the gsmSCF or secondary HLR + +3379 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +3380     Receive\_Open\_Cnf     see clause 25.1.2; + +3381     Check\_Confirmation     see clause 25.2.2. + +3382 The procedure in the gsmSCF or secondary HLR is shown in figure 22.10.5/1. + +![State transition diagram for process NW_Init_USSD_MSC. The process starts at 'Null', receives 'Start USSD' from the application, sends 'MAP_OPEN_req' and 'MAP_DELIMITER_req', receives 'Receive_Open_Cnf', and then branches based on 'Wait_For_Paging_Command_Local' (OK or Vr, Error).](6432fc33a8cf0dface0a39ba95522a9a_img.jpg) + +**process NW\_Init\_USSD\_MSC** **NI\_USSD\_MSC3(4)** + +Process in the MSC to handle a network initiated USSD transaction + +Signals to/from the left are to/from the MS; + signals to/from the right are to/from the VLR + unless marked otherwise + +``` + +stateDiagram-v2 + [*] --> Null + Null --> Start_USSD + Start_USSD --> Open_Req + Open_Req --> Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_Paging_Command_Local + Wait_For_Paging_Command_Local --> Page_MSC + Wait_For_Paging_Command_Local --> Search_For_MS_MSC + Wait_For_Paging_Command_Local --> Abort + Wait_For_Paging_Command_Local --> Vr_Error + Page_MSC --> Null + Page_MSC --> Error + Page_MSC --> OK + Search_For_MS_MSC --> Error + Search_For_MS_MSC --> OK + Search_For_MS_MSC --> Null + Error --> MAP_CLOSE_req + MAP_CLOSE_req --> Null + OK --> Process_Access_Request_MSC + Process_Access_Request_MSC --> MAP_CLOSE_req + Process_Access_Request_MSC --> Error + MAP_CLOSE_req --> Wait_For_USSD_Instruction + Wait_For_USSD_Instruction --> Null + Abort --> Null + +``` + +**State Transitions:** + +- Null** → **Start USSD** (From the USSD application in the MSC) +- Start USSD** → **MAP\_OPEN\_req / MAP\_DELIMITER\_req** +- MAP\_OPEN\_req / MAP\_DELIMITER\_req** → **Receive\_Open\_Cnf** +- Receive\_Open\_Cnf** → **Wait\_For\_Paging\_Command\_Local** (OK) or **1** (Vr, Error) +- Wait\_For\_Paging\_Command\_Local** → **Page\_MSC**, **Search\_For\_MS\_MSC**, **Abort** (To the USSD application in the MSC), or **1** +- Page\_MSC** → **Null** (Null), **MAP\_CLOSE\_req** (Error), or **Process\_Access\_Request\_MSC** (OK) +- Search\_For\_MS\_MSC** → **MAP\_CLOSE\_req** (Error), **Process\_Access\_Request\_MSC** (OK), or **1** (Null) +- Process\_Access\_Request\_MSC** → **MAP\_CLOSE\_req** (OK) or **1** (Error) +- MAP\_CLOSE\_req** → **Null** +- MAP\_CLOSE\_req** → **Wait\_For\_USSD\_Instruction** +- Wait\_For\_USSD\_Instruction** → **Null** + +State transition diagram for process NW\_Init\_USSD\_MSC. The process starts at 'Null', receives 'Start USSD' from the application, sends 'MAP\_OPEN\_req' and 'MAP\_DELIMITER\_req', receives 'Receive\_Open\_Cnf', and then branches based on 'Wait\_For\_Paging\_Command\_Local' (OK or Vr, Error). + +3383 + +3384 + +Figure 22.10.2/1 (sheet 1 of 4): Process NW\_Init\_USSD\_MSC + +process NW\_Init\_USSD\_MSC + +NI\_USSD\_MSC2(4) + +Process in the MSC to handle a network initiated USSD transaction + +Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR + +![State transition diagram for process NW_Init_USSD_MSC. The diagram shows two main vertical paths starting from a 'Wait_For_USSD_Indication' state. The left path handles NOTIFY messages, and the right path handles REQUEST messages. Both paths lead to a common 'Wait_For_USSN_Confirm, Wait_For_USSR_Confirm' state, which then branches into either a successful release sequence or an abort sequence.](dae0b516657a8fa6cf81e92cf48e6033_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Wait_For_USSD_Indication + state "Wait_For_USSD_Indication" as Wait_For_USSD_Indication + state "Wait_For_USSN_Confirm" as Wait_For_USSN_Confirm + state "Wait_For_USSR_Confirm" as Wait_For_USSR_Confirm + state "Wait_For_USSN_Confirm, Wait_For_USSR_Confirm" as Wait_For_USSN_Confirm_Wait_For_USSR_Confirm + state "A_CM_RELEASE_COMPLETE_req" as A_CM_RELEASE_COMPLETE_req + state "A_CM_RELEASE_req" as A_CM_RELEASE_req + state "Null" as Null + state "Application procedure cancellation" as Application_procedure_cancellation + + Wait_For_USSD_Indication --> Wait_For_USSN_Confirm : MAP_UNSTRUCTURED_SS_NOTIFY_ind + Wait_For_USSN_Confirm --> Wait_For_USSD_Indication : A_UNSTRUCTURED_SS_NOTIFY_req + Wait_For_USSN_Confirm --> Wait_For_USSR_Confirm : A_UNSTRUCTURED_SS_NOTIFY_cnf + Wait_For_USSR_Confirm --> Wait_For_USSD_Indication : MAP_UNSTRUCTURED_SS_REQUEST_ind + Wait_For_USSR_Confirm --> Wait_For_USSN_Confirm : A_UNSTRUCTURED_SS_REQUEST_req + Wait_For_USSR_Confirm --> Wait_For_USSN_Confirm_Wait_For_USSR_Confirm : A_UNSTRUCTURED_SS_REQUEST_cnf + Wait_For_USSN_Confirm_Wait_For_USSR_Confirm --> A_CM_RELEASE_COMPLETE_req : MAP_UNSTRUCTURED_SS_NOTIFY_rsp, MAP_DELIMITER_req + Wait_For_USSN_Confirm_Wait_For_USSR_Confirm --> MAP_U_ABORT_ind : MAP_U_ABORT_ind, MAP_CLOSE_ind + A_CM_RELEASE_COMPLETE_req --> Null + MAP_U_ABORT_req --> Application_procedure_cancellation + Application_procedure_cancellation --> A_CM_RELEASE_COMPLETE_req + A_CM_RELEASE_req --> Null + +``` + +State transition diagram for process NW\_Init\_USSD\_MSC. The diagram shows two main vertical paths starting from a 'Wait\_For\_USSD\_Indication' state. The left path handles NOTIFY messages, and the right path handles REQUEST messages. Both paths lead to a common 'Wait\_For\_USSN\_Confirm, Wait\_For\_USSR\_Confirm' state, which then branches into either a successful release sequence or an abort sequence. + +3385 + +3386 + +Figure 22.10.2/1 (sheet 2 of 4): Process NW\_Init\_USSD\_MSC + +![State transition diagram for process NW_Init_USSD_MSC. The process starts at 'Null', receives 'Start USSD' from the application, sends 'MAP_OPEN_req' and 'MAP_DELIMITER_req', receives 'Receive_Open_Cnf', and then branches based on 'OK' or 'Vr, Error'. The 'OK' path leads to 'Wait_For_Paging_Command_Local', which then branches into 'Page_MSC', 'Search_For_MS_MSC', and an 'Abort' path. 'Page_MSC' and 'Search_For_MS_MSC' lead to 'MAP_CLOSE_req' and then to state '1'. 'Search_For_MS_MSC' also leads to 'Process_Access_Request_MSC', which leads to 'MAP_CLOSE_req' and then to 'Wait_For_USSD_Instruction'. The 'Abort' path leads to 'To the USSD application in the MSC' and then to 'Null'.](93719af32eaa0771c630c27247cc89b6_img.jpg) + +**process NW\_Init\_USSD\_MSC** **NI\_USSD\_MSC3(4)** + +Process in the MSC to handle a network initiated USSD transaction + +Signals to/from the left are to/from the MS; + signals to/from the right are to/from the VLR + unless marked otherwise + +``` + +stateDiagram-v2 + [*] --> Null + Null --> Start_USSD : From the USSD application in the MSC + Start_USSD --> MAP_OPEN_req : MAP_OPEN_req, MAP_DELIMITER_req + MAP_OPEN_req --> Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_Paging_Command_Local : OK + Receive_Open_Cnf --> 1 : Vr, Error + Wait_For_Paging_Command_Local --> Page_MSC + Wait_For_Paging_Command_Local --> Search_For_MS_MSC + Wait_For_Paging_Command_Local --> Abort : MAP_U_ABORT_ind, MAP_CLOSE_ind + Page_MSC --> 1 : Null + Page_MSC --> MAP_CLOSE_req : Error + Page_MSC --> 1 : OK + Search_For_MS_MSC --> 1 : Null + Search_For_MS_MSC --> MAP_CLOSE_req : Error + Search_For_MS_MSC --> Process_Access_Request_MSC : OK + Process_Access_Request_MSC --> 1 : Error + Process_Access_Request_MSC --> MAP_CLOSE_req : OK + MAP_CLOSE_req --> 1 + MAP_CLOSE_req --> Wait_For_USSD_Instruction + Abort --> To_USSD_application : To the USSD application in the MSC + To_USSD_application --> Null + +``` + +State transition diagram for process NW\_Init\_USSD\_MSC. The process starts at 'Null', receives 'Start USSD' from the application, sends 'MAP\_OPEN\_req' and 'MAP\_DELIMITER\_req', receives 'Receive\_Open\_Cnf', and then branches based on 'OK' or 'Vr, Error'. The 'OK' path leads to 'Wait\_For\_Paging\_Command\_Local', which then branches into 'Page\_MSC', 'Search\_For\_MS\_MSC', and an 'Abort' path. 'Page\_MSC' and 'Search\_For\_MS\_MSC' lead to 'MAP\_CLOSE\_req' and then to state '1'. 'Search\_For\_MS\_MSC' also leads to 'Process\_Access\_Request\_MSC', which leads to 'MAP\_CLOSE\_req' and then to 'Wait\_For\_USSD\_Instruction'. The 'Abort' path leads to 'To the USSD application in the MSC' and then to 'Null'. + +3387 + +3388 + +**Figure 22.10.2/1 (sheet 3 of 4): Process NW\_Init\_USSD\_MSC** + +![State transition diagram for process NW_Init_USSD_MSC. The process starts in 'Wait_For_USSD_Instruction' and branches into two parallel paths: 'Unstructured SS Notify' and 'Unstructured SS Request'. Both paths involve local confirmations and subsequent instructions. A central state contains three wait conditions. From this state, the process can either release the service (leading to 'Abort' and 'Null') or continue with 'USSD release' (leading to 'Null').](56649cc9e7ebcf10ce69f4c018e67419_img.jpg) + +**process NW\_Init\_USSD\_MSC** **NI\_USSD\_MSC4(4)** + +Process in the MSC to handle a network initiated USSD transaction + +Signals to/from the left are to/from the MS; + signals to/from the right are to/from the USSD application in the MSC + +``` + +stateDiagram-v2 + [*] --> Wait_For_USSD_Instruction + state "Wait_For_USSD_Instruction" as Wait_For_USSD_Instruction + state "Unstructured SS Notify" as Unstructured_SS_Notify + state "Unstructured SS Request" as Unstructured_SS_Request + state "A_UNSTRUCTURED_SS_NOTIFY_req" as A_UNSTRUCTURED_SS_NOTIFY_req + state "A_UNSTRUCTURED_SS_REQUEST_req" as A_UNSTRUCTURED_SS_REQUEST_req + state "Wait_For_USSN_Confirm_Local" as Wait_For_USSN_Confirm_Local + state "Wait_For_USSR_Confirm_Local" as Wait_For_USSR_Confirm_Local + state "A_UNSTRUCTURED_SS_NOTIFY_cnf" as A_UNSTRUCTURED_SS_NOTIFY_cnf + state "A_UNSTRUCTURED_SS_REQUEST_cnf" as A_UNSTRUCTURED_SS_REQUEST_cnf + state "Unstructured SS Notify ack" as Unstructured_SS_Notify_ack + state "Unstructured SS Request ack" as Unstructured_SS_Request_ack + state "Wait_For_USSD_Instruction_2" as Wait_For_USSD_Instruction + state "Wait_For_USSD_Instruction, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local" as Wait_Conditions + state "A_CM_SERV_RELEASE_ind" as A_CM_SERV_RELEASE_ind + state "USSD release" as USSD_release + state "Abort" as Abort + state "A_CM_RELEASE_COMPLETE_req" as A_CM_RELEASE_COMPLETE_req + state "A_CM_SERV_RELEASE_req" as A_CM_SERV_RELEASE_req + state "Null" as Null + + Wait_For_USSD_Instruction --> Unstructured_SS_Notify + Wait_For_USSD_Instruction --> Unstructured_SS_Request + Unstructured_SS_Notify --> A_UNSTRUCTURED_SS_NOTIFY_req + A_UNSTRUCTURED_SS_NOTIFY_req --> Wait_For_USSN_Confirm_Local + Wait_For_USSN_Confirm_Local --> A_UNSTRUCTURED_SS_NOTIFY_cnf + A_UNSTRUCTURED_SS_NOTIFY_cnf --> Unstructured_SS_Notify_ack + Unstructured_SS_Notify_ack --> Wait_For_USSD_Instruction + Unstructured_SS_Request --> A_UNSTRUCTURED_SS_REQUEST_req + A_UNSTRUCTURED_SS_REQUEST_req --> Wait_For_USSR_Confirm_Local + Wait_For_USSR_Confirm_Local --> A_UNSTRUCTURED_SS_REQUEST_cnf + A_UNSTRUCTURED_SS_REQUEST_cnf --> Unstructured_SS_Request_ack + Unstructured_SS_Request_ack --> Wait_For_USSD_Instruction + Wait_For_USSD_Instruction --> Wait_Conditions + Wait_Conditions --> A_CM_SERV_RELEASE_ind + Wait_Conditions --> USSD_release + A_CM_SERV_RELEASE_ind --> Abort + Abort --> A_CM_RELEASE_COMPLETE_req + A_CM_RELEASE_COMPLETE_req --> Null + USSD_release --> A_CM_SERV_RELEASE_req + A_CM_SERV_RELEASE_req --> Null + +``` + +State transition diagram for process NW\_Init\_USSD\_MSC. The process starts in 'Wait\_For\_USSD\_Instruction' and branches into two parallel paths: 'Unstructured SS Notify' and 'Unstructured SS Request'. Both paths involve local confirmations and subsequent instructions. A central state contains three wait conditions. From this state, the process can either release the service (leading to 'Abort' and 'Null') or continue with 'USSD release' (leading to 'Null'). + +3389 + +3390 + +Figure 22.10.2/1 (sheet 4 of 4): Process NW\_Init\_USSD\_MSC + +![State transition diagram for process NW_Init_USSD_VLR. The process starts at a Null state, receives an Open_Ind from the HLR, and then branches based on the type of indication (SS_NOTIFY, SS_REQUEST, or P_ABORT/U_ABORT/CLOSE). It then checks the indication, sends responses, and either starts the USSD_VLR process or sets a user error.](61d27a7d74168c5c2f5cd8b0de0a9098_img.jpg) + +**process NW\_Init\_USSD\_VLR** **NI\_USSD\_VLR1(5)** + +Process in the VLR to handle a network initiated USSD transaction + +Signals to/from the left are to/from the MSC; + signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Null1[Null] + Null1 --> Receive_Open_Ind + Receive_Open_Ind --> Wait_For_USSD_Indication + Wait_For_USSD_Indication --> Check_Indication1[Check_Indication] + Wait_For_USSD_Indication --> Check_Indication2[Check_Indication] + Wait_For_USSD_Indication --> MAP_CLOSE_req + Check_Indication1 --> MAP_UNSTRUCTURED_SS_NOTIFY_rsp + Check_Indication1 --> Null2[Null] + Check_Indication2 --> MAP_UNSTRUCTURED_SS_REQUEST_rsp + Check_Indication2 --> Null3[Null] + MAP_CLOSE_req --> Null4[Null] + MAP_UNSTRUCTURED_SS_NOTIFY_rsp --> MAP_OPEN_req + MAP_UNSTRUCTURED_SS_REQUEST_rsp --> MAP_OPEN_req + MAP_OPEN_req --> Receive_Open_Cnf + Receive_Open_Cnf --> Start_USSD_VLR1[Start_USSD_VLR] + Receive_Open_Cnf --> Null5[Null] + Start_USSD_VLR1 --> Wait_For_USSN_Confirm + Start_USSD_VLR1 --> Set_User_Error1[Set User Error] + Start_USSD_VLR1 --> MAP_UNSTRUCTURED_SS_NOTIFY_rsp2 + Start_USSD_VLR1 --> Null6[Null] + Set_User_Error1 --> Null7[Null] + MAP_UNSTRUCTURED_SS_NOTIFY_rsp2 --> Null8[Null] + MAP_UNSTRUCTURED_SS_REQUEST_rsp --> MAP_OPEN_req2 + MAP_OPEN_req2 --> Receive_Open_Cnf2 + Receive_Open_Cnf2 --> Start_USSD_VLR2[Start_USSD_VLR] + Receive_Open_Cnf2 --> Null9[Null] + Start_USSD_VLR2 --> Wait_For_USSR_Confirm + Start_USSD_VLR2 --> Set_User_Error2[Set User Error] + Start_USSD_VLR2 --> MAP_UNSTRUCTURED_SS_REQUEST_rsp2 + Start_USSD_VLR2 --> Null10[Null] + Set_User_Error2 --> Null11[Null] + MAP_UNSTRUCTURED_SS_REQUEST_rsp2 --> Null12[Null] + +``` + +State transition diagram for process NW\_Init\_USSD\_VLR. The process starts at a Null state, receives an Open\_Ind from the HLR, and then branches based on the type of indication (SS\_NOTIFY, SS\_REQUEST, or P\_ABORT/U\_ABORT/CLOSE). It then checks the indication, sends responses, and either starts the USSD\_VLR process or sets a user error. + +3391 + +3392 + +**Figure 22.10.3/1 (sheet 1 of 5): Process NW\_Init\_USSD\_VLR** + +![State transition diagram for process NW_Init_USSD_VLR. It starts at 'Wait_For_Next_USSD_Indication' and branches based on incoming indications: MAP_CLOSE_ind, MAP_UNSTRUCTURED_SS_NOTIFY_ind, and MAP_UNSTRUCTURED_SS_REQUEST_ind. Each branch handles the respective indication, sends responses, and returns to the initial wait state or ends in a Null state.](4d1315a63029d027c93c29f2dce12b83_img.jpg) + +**process NW\_Init\_USSD\_VLR** **NI\_USSD\_VLR2(5)** + +Process in the VLR to handle a network initiated USSD transaction + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Wait_For_Next_USSD_Indication + state "MAP_CLOSE_ind" as MAP_CLOSE_ind + state "MAP_UNSTRUCTURED_SS_NOTIFY_ind" as MAP_UNSTRUCTURED_SS_NOTIFY_ind + state "MAP_UNSTRUCTURED_SS_REQUEST_ind" as MAP_UNSTRUCTURED_SS_REQUEST_ind + state "Null" as Null + state "Check_Indication" as Check_Indication + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_UNSTRUCTURED_SS_NOTIFY_rsp" as MAP_UNSTRUCTURED_SS_NOTIFY_rsp + state "MAP_UNSTRUCTURED_SS_REQUEST_rsp" as MAP_UNSTRUCTURED_SS_REQUEST_rsp + state "MAP_UNSTRUCTURED_SS_NOTIFY_req" as MAP_UNSTRUCTURED_SS_NOTIFY_req + state "MAP_DELIMITER_req" as MAP_DELIMITER_req + state "Wait_For_USSN_Confirm" as Wait_For_USSN_Confirm + state "MAP_UNSTRUCTURED_SS_NOTIFY_cnf" as MAP_UNSTRUCTURED_SS_NOTIFY_cnf + state "MAP_UNSTRUCTURED_SS_REQUEST_cnf" as MAP_UNSTRUCTURED_SS_REQUEST_cnf + state "Wait_For_USSR_Confirm" as Wait_For_USSR_Confirm + state "MAP_UNSTRUCTURED_SS_NOTIFY_rsp" as MAP_UNSTRUCTURED_SS_NOTIFY_rsp + state "MAP_DELIMITER_req" as MAP_DELIMITER_req + state "Wait_For_Next_USSD_Indication" as Wait_For_Next_USSD_Indication + + Wait_For_Next_USSD_Indication --> MAP_CLOSE_ind + Wait_For_Next_USSD_Indication --> MAP_UNSTRUCTURED_SS_NOTIFY_ind + Wait_For_Next_USSD_Indication --> MAP_UNSTRUCTURED_SS_REQUEST_ind + + MAP_CLOSE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Null + + MAP_UNSTRUCTURED_SS_NOTIFY_ind --> Check_Indication + Check_Indication --> Null : Error + Check_Indication --> MAP_UNSTRUCTURED_SS_NOTIFY_rsp : OK + MAP_UNSTRUCTURED_SS_NOTIFY_rsp --> MAP_CLOSE_req + MAP_CLOSE_req --> Null + + MAP_UNSTRUCTURED_SS_REQUEST_ind --> Check_Indication + Check_Indication --> Null : Error + Check_Indication --> MAP_UNSTRUCTURED_SS_REQUEST_rsp : OK + MAP_UNSTRUCTURED_SS_REQUEST_rsp --> MAP_CLOSE_req + MAP_CLOSE_req --> Null + + MAP_UNSTRUCTURED_SS_NOTIFY_rsp --> MAP_UNSTRUCTURED_SS_NOTIFY_req + MAP_UNSTRUCTURED_SS_NOTIFY_req --> Wait_For_USSN_Confirm + Wait_For_USSN_Confirm --> MAP_UNSTRUCTURED_SS_NOTIFY_cnf + MAP_UNSTRUCTURED_SS_NOTIFY_cnf --> MAP_UNSTRUCTURED_SS_NOTIFY_rsp + MAP_UNSTRUCTURED_SS_NOTIFY_rsp --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_Next_USSD_Indication + + MAP_UNSTRUCTURED_SS_REQUEST_rsp --> MAP_UNSTRUCTURED_SS_REQUEST_req + MAP_UNSTRUCTURED_SS_REQUEST_req --> Wait_For_USSR_Confirm + Wait_For_USSR_Confirm --> MAP_UNSTRUCTURED_SS_REQUEST_cnf + MAP_UNSTRUCTURED_SS_REQUEST_cnf --> MAP_UNSTRUCTURED_SS_REQUEST_rsp + MAP_UNSTRUCTURED_SS_REQUEST_rsp --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_Next_USSD_Indication + +``` + +State transition diagram for process NW\_Init\_USSD\_VLR. It starts at 'Wait\_For\_Next\_USSD\_Indication' and branches based on incoming indications: MAP\_CLOSE\_ind, MAP\_UNSTRUCTURED\_SS\_NOTIFY\_ind, and MAP\_UNSTRUCTURED\_SS\_REQUEST\_ind. Each branch handles the respective indication, sends responses, and returns to the initial wait state or ends in a Null state. + +3393 + +3394 + +**Figure 22.10.3/1 (sheet 2 of 5): Process NW\_Init\_USSD\_VLR** + +![State transition diagram for process NW_Init_USSD_VLR. The diagram is divided into two main sections: upper subtrees (signals to/from VLR) and lower subtrees (signals to/from USSD application). States are represented by rounded rectangles, transitions by arrows, and decision points by diamonds. Labels include MAP_CLOSE_ind, MAP_U_ABORT_req, Null, Wait_For_USSN_Confirm, Wait_For_USSR_Confirm, MAP_U_ABORT_ind, MAP_CLOSE_ind, MAP_NOTICE_ind, MAP_P_ABORT_ind, Receive_Open_ind, From MSC, OK, Vr, Error, Start_USSD_VLR, Abort, Wait_For_USSD_Instruction, Wait_For_USSN_Confirm, Wait_For_USSR_Confirm, Wait_For_Next_USSD_Instruction, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local.](8b41806930c4899e083c07f69462b876_img.jpg) + +**process NW\_Init\_USSD\_VLR** **NI\_USSD\_VLR3(5)** + +Process in the VLR to handle a network initiated USSD transaction + +In the upper subtrees, signals to/from the left are to/from the VLR; signals to/from the right are to/from the HLR + +In the lower subtrees, signals to/from the left are to/from the VLR; signals to/from the right are to/from the USSD application in the VLR + +``` + +stateDiagram-v2 + [*] --> S1 : Wait_For_Next_USSD_Indication, Wait_For_USSN_Confirm, Wait_For_USSR_Confirm + S1 --> S2 : MAP_CLOSE_ind + S2 --> S3 : MAP_U_ABORT_req + S3 --> [*] : Null + S1 --> S4 : MAP_U_ABORT_ind, MAP_CLOSE_ind + S4 --> S5 : MAP_U_ABORT_req + S5 --> [*] : Null + S1 --> S6 : MAP_NOTICE_ind + S6 --> S7 : MAP_CLOSE_req + S7 --> S8 : MAP_U_ABORT_req + S8 --> [*] : Null + S1 --> S9 : MAP_P_ABORT_ind, MAP_U_ABORT_ind + S9 --> S7 + S9 --> S8 + S9 --> [*] : Null + + [*] --> S10 : Null + S10 --> S11 : Receive_Open_ind + S11 --> S12 : OK + S11 --> S13 : Vr, Error + S12 --> S14 : Start_USSD_VLR + S14 --> S10 : OK, Error + S14 --> S13 : OK, Error + S10 --> S15 : Abort + S15 --> S16 : MAP_U_ABORT_req + S16 --> [*] : Null + S10 --> S17 : Wait_For_USSD_Instruction, Wait_For_USSN_Confirm, Wait_For_USSR_Confirm + S17 --> S18 : MAP_U_ABORT_ind, MAP_CLOSE_ind + S18 --> S19 : Abort + S19 --> [*] : Null + S10 --> S20 : Wait_For_Next_USSD_Instruction, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local + S20 --> S18 + +``` + +State transition diagram for process NW\_Init\_USSD\_VLR. The diagram is divided into two main sections: upper subtrees (signals to/from VLR) and lower subtrees (signals to/from USSD application). States are represented by rounded rectangles, transitions by arrows, and decision points by diamonds. Labels include MAP\_CLOSE\_ind, MAP\_U\_ABORT\_req, Null, Wait\_For\_USSN\_Confirm, Wait\_For\_USSR\_Confirm, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind, MAP\_NOTICE\_ind, MAP\_P\_ABORT\_ind, Receive\_Open\_ind, From MSC, OK, Vr, Error, Start\_USSD\_VLR, Abort, Wait\_For\_USSD\_Instruction, Wait\_For\_USSN\_Confirm, Wait\_For\_USSR\_Confirm, Wait\_For\_Next\_USSD\_Instruction, Wait\_For\_USSN\_Confirm\_Local, Wait\_For\_USSR\_Confirm\_Local. + +3395 + +3396 + +Figure 22.10.3/1 (sheet 3 of 5): Process NW\_Init\_USSD\_VLR + +process NW\_Init\_USSD\_VLR + +NI\_USSD\_VLR4(5) + +Process in the VLR to handle a network initiated USSD transaction + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the USSD application in the VLR + +![Flowchart for process NW_Init_USSD_VLR. It starts with 'Null' leading to 'Start USSD', which leads to a decision diamond. The right path from the diamond is labeled 'MAP_OPEN_req' and 'MAP_DELIMITER_req', leading to 'Receive_Open_Cnf'. From 'Receive_Open_Cnf', an 'OK' path leads to 'Wait_For_USSD_Instruction' and a 'Vr, Error' path leads to 'Abort' (which ends at 'Null'). From 'Wait_For_USSD_Instruction', the flow splits into two parallel paths. The left path goes through 'Unstructured SS Notify' to 'Start_USSD_VLR', which then splits into 'OK' (leading to a decision diamond, then 'MAP_UNSTRUCTURED_SS_NOTIFY_req'/'MAP_DELIMITER_req', then 'Wait_For_USSN_Confirm_Local') and 'Error' (leading to 'Set negative response', then 'Unstructured SS Notify negative response', then 'Null'). The right path goes through 'Unstructured SS Request' to 'Start_USSD_VLR', which similarly splits into 'OK' (leading to a decision diamond, then 'MAP_UNSTRUCTURED_SS_REQUEST_req'/'MAP_DELIMITER_req', then 'Wait_For_USSR_Confirm_Local') and 'Error' (leading to 'Set negative response', then 'Unstructured SS Request negative response', then 'Null').](6147b14ea158d1697f84344113b5b027_img.jpg) + +``` + +graph TD + Null1([Null]) --> StartUSSD{{Start USSD}} + StartUSSD --> Decision1{ } + Decision1 -- "MAP_OPEN_req +MAP_DELIMITER_req" --> ReceiveOpenCnf[Receive_Open_Cnf] + ReceiveOpenCnf -- OK --> WaitForUSSDInstruction([Wait_For_USSD_Instruction]) + ReceiveOpenCnf -- "Vr, Error" --> Abort{{Abort}} + Abort --> Null2([Null]) + WaitForUSSDInstruction --> UnstructuredSSNotify{{Unstructured SS Notify}} + WaitForUSSDInstruction --> UnstructuredSSRequest{{Unstructured SS Request}} + UnstructuredSSNotify --> StartUSSDVLR1[Start_USSD_VLR] + StartUSSDVLR1 -- OK --> Decision2{ } + Decision2 -- "MAP_UNSTRUCTURED_SS_NOTIFY_req +MAP_DELIMITER_req" --> WaitForUSSNConfirmLocal([Wait_For_USSN_Confirm_Local]) + StartUSSDVLR1 -- Error --> SetNegativeResponse1[Set negative response] + SetNegativeResponse1 --> UnstructuredSSNotifyNegativeResponse{{Unstructured SS Notify negative response}} + UnstructuredSSNotifyNegativeResponse --> Null3([Null]) + UnstructuredSSRequest --> StartUSSDVLR2[Start_USSD_VLR] + StartUSSDVLR2 -- OK --> Decision3{ } + Decision3 -- "MAP_UNSTRUCTURED_SS_REQUEST_req +MAP_DELIMITER_req" --> WaitForUSSRConfirmLocal([Wait_For_USSR_Confirm_Local]) + StartUSSDVLR2 -- Error --> SetNegativeResponse2[Set negative response] + SetNegativeResponse2 --> UnstructuredSSRequestNegativeResponse{{Unstructured SS Request negative response}} + UnstructuredSSRequestNegativeResponse --> Null4([Null]) + +``` + +Flowchart for process NW\_Init\_USSD\_VLR. It starts with 'Null' leading to 'Start USSD', which leads to a decision diamond. The right path from the diamond is labeled 'MAP\_OPEN\_req' and 'MAP\_DELIMITER\_req', leading to 'Receive\_Open\_Cnf'. From 'Receive\_Open\_Cnf', an 'OK' path leads to 'Wait\_For\_USSD\_Instruction' and a 'Vr, Error' path leads to 'Abort' (which ends at 'Null'). From 'Wait\_For\_USSD\_Instruction', the flow splits into two parallel paths. The left path goes through 'Unstructured SS Notify' to 'Start\_USSD\_VLR', which then splits into 'OK' (leading to a decision diamond, then 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_req'/'MAP\_DELIMITER\_req', then 'Wait\_For\_USSN\_Confirm\_Local') and 'Error' (leading to 'Set negative response', then 'Unstructured SS Notify negative response', then 'Null'). The right path goes through 'Unstructured SS Request' to 'Start\_USSD\_VLR', which similarly splits into 'OK' (leading to a decision diamond, then 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_req'/'MAP\_DELIMITER\_req', then 'Wait\_For\_USSR\_Confirm\_Local') and 'Error' (leading to 'Set negative response', then 'Unstructured SS Request negative response', then 'Null'). + +3397 + +3398 + +Figure 22.10.3/1 (sheet 4 of 5): Process NW\_Init\_USSD\_VLR + +![State transition diagram for process NW_Init_USSD_VLR. It starts with 'Wait_For_Next_USSD_Instruction' and branches into three paths: USSD release, Unstructured SS Notify, and Unstructured SS Request. Each path involves MAP requests, local confirmation checks, and subsequent responses or acknowledgments before returning to the initial wait state.](8d5aefe6fd62d986007fc4724ad48628_img.jpg) + +**process NW\_Init\_USSD\_VLR** **NI\_USSD\_VLR5(5)** + +Process in the VLR to handle a network initiated USSD transaction + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the USSD application in the VLR + +``` + +stateDiagram-v2 + [*] --> Wait_For_Next_USSD_Instruction + state "Wait_For_Next_USSD_Instruction" as Wait_For_Next_USSD_Instruction + state "USSD release" as USSD_release + state "Unstructured SS Notify" as Unstructured_SS_Notify + state "Unstructured SS Request" as Unstructured_SS_Request + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "Null" as Null + state "MAP_UNSTRUCTURED_SS_NOTIFY_req" as MAP_UNSTRUCTURED_SS_NOTIFY_req + state "Wait_For_USSN_Confirm_Local" as Wait_For_USSN_Confirm_Local + state "MAP_UNSTRUCTURED_SS_NOTIFY_cnf" as MAP_UNSTRUCTURED_SS_NOTIFY_cnf + state "Check_Confirmation" as Check_Confirmation + state "Set negative response" as Set_negative_response + state "Set ack" as Set_ack + state "Unstructured SS Notify negative response" as Unstructured_SS_Notify_negative_response + state "Unstructured SS Notify ack" as Unstructured_SS_Notify_ack + state "MAP_UNSTRUCTURED_SS_REQUEST_req" as MAP_UNSTRUCTURED_SS_REQUEST_req + state "Wait_For_USSR_Confirm_Local" as Wait_For_USSR_Confirm_Local + state "MAP_UNSTRUCTURED_SS_REQUEST_cnf" as MAP_UNSTRUCTURED_SS_REQUEST_cnf + state "Unstructured SS Request negative response" as Unstructured_SS_Request_negative_response + state "Unstructured SS Request ack" as Unstructured_SS_Request_ack + + Wait_For_Next_USSD_Instruction --> USSD_release + Wait_For_Next_USSD_Instruction --> Unstructured_SS_Notify + Wait_For_Next_USSD_Instruction --> Unstructured_SS_Request + + USSD_release --> MAP_CLOSE_req + MAP_CLOSE_req --> Null + Null --> Wait_For_Next_USSD_Instruction + + Unstructured_SS_Notify --> MAP_UNSTRUCTURED_SS_NOTIFY_req + MAP_UNSTRUCTURED_SS_NOTIFY_req --> Wait_For_USSN_Confirm_Local + Wait_For_USSN_Confirm_Local --> MAP_UNSTRUCTURED_SS_NOTIFY_cnf + MAP_UNSTRUCTURED_SS_NOTIFY_cnf --> Check_Confirmation + Check_Confirmation --> Set_negative_response : User Error, Data Error, Provider Error + Check_Confirmation --> Set_ack : OK + Set_negative_response --> Unstructured_SS_Notify_negative_response + Set_ack --> Unstructured_SS_Notify_ack + Unstructured_SS_Notify_negative_response --> Wait_For_Next_USSD_Instruction + Unstructured_SS_Notify_ack --> Wait_For_Next_USSD_Instruction + + Unstructured_SS_Request --> MAP_UNSTRUCTURED_SS_REQUEST_req + MAP_UNSTRUCTURED_SS_REQUEST_req --> Wait_For_USSR_Confirm_Local + Wait_For_USSR_Confirm_Local --> MAP_UNSTRUCTURED_SS_REQUEST_cnf + MAP_UNSTRUCTURED_SS_REQUEST_cnf --> Check_Confirmation + Check_Confirmation --> Set_negative_response : User Error, Data Error, Provider Error + Check_Confirmation --> Set_ack : OK + Set_negative_response --> Unstructured_SS_Request_negative_response + Set_ack --> Unstructured_SS_Request_ack + Unstructured_SS_Request_negative_response --> Wait_For_Next_USSD_Instruction + Unstructured_SS_Request_ack --> Wait_For_Next_USSD_Instruction + +``` + +State transition diagram for process NW\_Init\_USSD\_VLR. It starts with 'Wait\_For\_Next\_USSD\_Instruction' and branches into three paths: USSD release, Unstructured SS Notify, and Unstructured SS Request. Each path involves MAP requests, local confirmation checks, and subsequent responses or acknowledgments before returning to the initial wait state. + +3399 + +3400 + +**Figure 22.10.3/1 (sheet 5 of 5): Process NW\_Init\_USSD\_VLR** + +macrodefinition Start\_USSD\_VLR + +S\_USSD\_VLR1(2) + +Macro in the VLR to page the MS to start a network initiated USSD transaction + +Signals to/from the left are to/from the MSC + +![Flowchart for macrodefinition Start_USSD_VLR. It starts with an entry point, followed by a decision 'Subscriber data confirmed by HLR?'. If 'No', it goes to 'Set User Error: System Failure' then 'Error'. If 'Yes', it goes to 'IMSI detached?'. If 'Yes', it goes to 'Set User Error: Absent Subscriber' then 'Error'. If 'No', it goes to 'Roaming allowed in current location area?'. If 'No', it goes to 'Error'. If 'Yes', it goes to 'LAI known?'. If 'No', it goes to 'Confirmed by Radio Contact?'. If 'Yes', it goes to 'MAP_PAGE_req' and 'MAP_DELIMITER_req', then 'Wait_For_Access_Request'. If 'No', it goes to 'MAP_SEARCH_FOR_MS_req' and 'MAP_DELIMITER_req', then 'Wait_For_Access_Request'.](5175a695be4c949bfb94d01307f8e0fa_img.jpg) + +``` + +graph TD + Entry([ ]) --> D1{Subscriber data confirmed by HLR?} + D1 -- No --> E1[Set User Error: System Failure] + E1 --> Error((Error)) + D1 -- Yes --> D2{IMSI detached?} + D2 -- Yes --> E2[Set User Error: Absent Subscriber] + E2 --> Error + D2 -- No --> D3{Roaming allowed in current location area?} + D3 -- No --> Error + D3 -- Yes --> D4{LAI known?} + D4 -- No --> D5{Confirmed by Radio Contact?} + D5 -- Yes --> P1[MAP_PAGE_req +MAP_DELIMITER_req] + D5 -- No --> S1[MAP_SEARCH_FOR_MS_req +MAP_DELIMITER_req] + P1 --> W[Wait_For_Access_Request] + S1 --> W + +``` + +Flowchart for macrodefinition Start\_USSD\_VLR. It starts with an entry point, followed by a decision 'Subscriber data confirmed by HLR?'. If 'No', it goes to 'Set User Error: System Failure' then 'Error'. If 'Yes', it goes to 'IMSI detached?'. If 'Yes', it goes to 'Set User Error: Absent Subscriber' then 'Error'. If 'No', it goes to 'Roaming allowed in current location area?'. If 'No', it goes to 'Error'. If 'Yes', it goes to 'LAI known?'. If 'No', it goes to 'Confirmed by Radio Contact?'. If 'Yes', it goes to 'MAP\_PAGE\_req' and 'MAP\_DELIMITER\_req', then 'Wait\_For\_Access\_Request'. If 'No', it goes to 'MAP\_SEARCH\_FOR\_MS\_req' and 'MAP\_DELIMITER\_req', then 'Wait\_For\_Access\_Request'. + +3401 + +3402 + +Figure 22.10.3/2 (sheet 1 of 2): Macro Start\_USSD\_VLR + +![Flowchart for macro definition Start_USSD_VLR. It starts with 'Wait_For_Access_Request' and branches into four paths: 'MAP_U_ABORT_ind' (Error), 'Process_Access_Request_VLR' (OK/Error), 'MAP_PAGE_cnf' (User Error/Absent subscriber/System failure), and 'MAP_SEARCH_FOR_MS_cnf' (OK/Update LAI/Confirmed/Wait_For_Access_Request or Provider Error/Data Error).](86ab158965bc6f92917abcc615d51e57_img.jpg) + +macrodefinition Start\_USSD\_VLR + +S\_USSD\_VLR2(2) + +Macro in the VLR to page the MS to start a network initiated USSD transaction + +Signals to/from the left are to/from the MSC + +``` + +graph TD + Start([Wait_For_Access_Request]) --> MAP_U_ABORT_ind[/MAP_U_ABORT_ind/] + Start --> Process_Access_Request_VLR[Process_Access_Request_VLR] + Start --> MAP_PAGE_cnf[/MAP_PAGE_cnf/] + Start --> MAP_SEARCH_FOR_MS_cnf[/MAP_SEARCH_FOR_MS_cnf/] + + MAP_U_ABORT_ind --> Error1((Error)) + + Process_Access_Request_VLR -- OK --> OK1((OK)) + Process_Access_Request_VLR -- Error --> Error2((Error)) + + MAP_PAGE_cnf -- User Error --> Error3((Error)) + MAP_PAGE_cnf -- Yes --> Set_User_Error_Absent[Set User Error: Absent subscriber] + MAP_PAGE_cnf -- No --> Set_User_Error_System[Set User Error: System failure] + Set_User_Error_Absent --> MAP_CLOSE_req[/MAP_CLOSE_req/] + Set_User_Error_System --> MAP_CLOSE_req + MAP_CLOSE_req --> Error4((Error)) + + MAP_SEARCH_FOR_MS_cnf -- OK --> Update_LAI[Update LAI] + Update_LAI --> Confirmed[Confirmed by Radio Contact= Confirmed] + Confirmed --> Wait_For_Access_Request2([Wait_For_Access_Request]) + + MAP_SEARCH_FOR_MS_cnf -- "Provider Error, Data Error" --> Error5((Error)) + +``` + +Flowchart for macro definition Start\_USSD\_VLR. It starts with 'Wait\_For\_Access\_Request' and branches into four paths: 'MAP\_U\_ABORT\_ind' (Error), 'Process\_Access\_Request\_VLR' (OK/Error), 'MAP\_PAGE\_cnf' (User Error/Absent subscriber/System failure), and 'MAP\_SEARCH\_FOR\_MS\_cnf' (OK/Update LAI/Confirmed/Wait\_For\_Access\_Request or Provider Error/Data Error). + +3403 + +3404 + +Figure 22.10.3/2 (sheet 2 of 2): Macro Start\_USSD\_VLR + +![State transition diagram for process NW_Init_USSD_HLR. The process starts at an initial state, goes to 'Null', then receives an 'Open_ind' from gsmSCF or secondary HLR. It then enters 'Wait_For_USSD_Indication'. From there, it branches based on indications: 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req' then 'Null'; 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' leads to 'Null'; 'MAP_UNSTRUCTURED_SS_REQUEST_ind' leads to 'Check_Indication'. 'Check_Indication' has 'OK' (to 'Start_USSD_HLR') and 'Error' (to 'Null') paths. 'Start_USSD_HLR' has 'OK' (to connector 1), 'Abort' (to 'MAP_U_ABORT_req' then 'Null'), and 'Error' (to 'Null') paths. Another 'Check_Indication' block on the right has 'OK' (to 'Start_USSD_HLR'), 'Error' (to 'Null'), and 'Abort' (to 'MAP_U_ABORT_req' then 'Null') paths. 'Start_USSD_HLR' also has an 'OK' path to connector 2. A third 'Check_Indication' block in the middle leads to 'Null'.](1f3d7b206a7e807b225da932f6e47236_img.jpg) + +**process NW\_Init\_USSD\_HLR** **NI\_USSD\_HLR1(5)** + +Process in the HLR to handle a network initiated USSD transaction + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the next node (gsmSCF or secondary HLR) + +``` + +stateDiagram-v2 + [*] --> Null + Null --> Receive_Open_ind + Receive_Open_ind --> Wait_For_USSD_Indication + Wait_For_USSD_Indication --> MAP_NOTICE_ind + Wait_For_USSD_Indication --> MAP_P_ABORT_ind + Wait_For_USSD_Indication --> MAP_UNSTRUCTURED_SS_REQUEST_ind + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Null + MAP_P_ABORT_ind --> Null + MAP_UNSTRUCTURED_SS_REQUEST_ind --> Check_Indication_R + Check_Indication_R --> Start_USSD_HLR_R + Start_USSD_HLR_R --> Null + Start_USSD_HLR_R --> MAP_U_ABORT_req_R + Start_USSD_HLR_R --> MAP_UNSTRUCTURED_SS_REQUEST_rsp + Start_USSD_HLR_R --> Null + Start_USSD_HLR_R --> 2 + Check_Indication_M --> Null + Check_Indication --> Start_USSD_HLR + Start_USSD_HLR --> Null + Start_USSD_HLR --> MAP_U_ABORT_req + Start_USSD_HLR --> MAP_UNSTRUCTURED_SS_NOTIFY_rsp + Start_USSD_HLR --> Null + Start_USSD_HLR --> 1 + +``` + +State transition diagram for process NW\_Init\_USSD\_HLR. The process starts at an initial state, goes to 'Null', then receives an 'Open\_ind' from gsmSCF or secondary HLR. It then enters 'Wait\_For\_USSD\_Indication'. From there, it branches based on indications: 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req' then 'Null'; 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' leads to 'Null'; 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_ind' leads to 'Check\_Indication'. 'Check\_Indication' has 'OK' (to 'Start\_USSD\_HLR') and 'Error' (to 'Null') paths. 'Start\_USSD\_HLR' has 'OK' (to connector 1), 'Abort' (to 'MAP\_U\_ABORT\_req' then 'Null'), and 'Error' (to 'Null') paths. Another 'Check\_Indication' block on the right has 'OK' (to 'Start\_USSD\_HLR'), 'Error' (to 'Null'), and 'Abort' (to 'MAP\_U\_ABORT\_req' then 'Null') paths. 'Start\_USSD\_HLR' also has an 'OK' path to connector 2. A third 'Check\_Indication' block in the middle leads to 'Null'. + +3405 + +3406 + +Figure 22.10.4/1 (sheet 1 of 5): Process NW\_Init\_USSD\_HLR + +![State transition diagram for process NW_Init_USSD_HLR. The diagram is divided into two main vertical paths, 1 and 2, which merge into a common horizontal state. Path 1 and 2 start with an initial state (circle with number), leading to a decision diamond. From the diamond, a message block (MAP_OPEN_req, MAP_UNSTRUCTURED_SS_NOTIFY_req, MAP_DELIMITER_req) is sent. This leads to a 'Receive_Open_Cnf' state. From 'Receive_Open_Cnf', an 'OK' transition leads to 'Wait_For_USSN_Confirm' and a 'Vr, Error' transition leads to a 'MAP_U_ABORT_req' state, which then leads to 'Null'. Paths 1 and 2 merge into a common state 'Wait_For_USSN_Confirm, Wait_For_USSR_Confirm'. From this state, four transitions are possible: 1) 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' to the left, 2) 'MAP_NOTICE_ind' to the right, 3) 'MAP_CLOSE_req' to the right, and 4) 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' to the right. The 'MAP_NOTICE_ind' and 'MAP_CLOSE_req' paths both lead to a 'Set User Error: System failure' state. From 'Set User Error: System failure', a 'MAP_UNSTRUCTURED_SS_REQUEST_rsp, MAP_CLOSE_req' message is sent to the left, leading to 'Null'. The 'MAP_CLOSE_req' path also leads to a 'MAP_U_ABORT_req' state, which leads to 'Null'.](524a1954e3bc2e0a657892149a5aab0a_img.jpg) + +**process NW\_Init\_USSD\_HLR** **NI\_USSD\_HLR2(5)** + +Process in the HLR to handle a network initiated USSD transaction + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the next node (gsmSCF or secondary HLR) + +``` + +stateDiagram-v2 + [*] --> 1 + [*] --> 2 + 1 --> D1{ } + D1 --> M1[MAP_OPEN_req +MAP_UNSTRUCTURED_SS_NOTIFY_req +MAP_DELIMITER_req] + M1 --> S1[Receive_Open_Cnf] + S1 --> W1[Wait_For_USSN_Confirm] : OK + S1 --> A1[MAP_U_ABORT_req] : Vr, Error + A1 --> N1[Null] + 2 --> D2{ } + D2 --> M2[MAP_OPEN_req +MAP_UNSTRUCTURED_SS_REQUEST_req +MAP_DELIMITER_req] + M2 --> S2[Receive_Open_Cnf] + S2 --> W2[Wait_For_USSR_Confirm] : OK + S2 --> A2[MAP_U_ABORT_req] : Vr, Error + A2 --> N2[Null] + W1 --> W[Wait_For_USSN_Confirm, Wait_For_USSR_Confirm] + W2 --> W + W --> M3[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] : left + W --> M4[MAP_NOTICE_ind] : right + W --> M5[MAP_CLOSE_req] : right + W --> M6[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] : right + M4 --> S3[Set User Error: System failure] + M5 --> S3 + S3 --> M7[MAP_UNSTRUCTURED_SS_REQUEST_rsp +MAP_CLOSE_req] : left + M7 --> N3[Null] + M5 --> A3[MAP_U_ABORT_req] + A3 --> N4[Null] + +``` + +State transition diagram for process NW\_Init\_USSD\_HLR. The diagram is divided into two main vertical paths, 1 and 2, which merge into a common horizontal state. Path 1 and 2 start with an initial state (circle with number), leading to a decision diamond. From the diamond, a message block (MAP\_OPEN\_req, MAP\_UNSTRUCTURED\_SS\_NOTIFY\_req, MAP\_DELIMITER\_req) is sent. This leads to a 'Receive\_Open\_Cnf' state. From 'Receive\_Open\_Cnf', an 'OK' transition leads to 'Wait\_For\_USSN\_Confirm' and a 'Vr, Error' transition leads to a 'MAP\_U\_ABORT\_req' state, which then leads to 'Null'. Paths 1 and 2 merge into a common state 'Wait\_For\_USSN\_Confirm, Wait\_For\_USSR\_Confirm'. From this state, four transitions are possible: 1) 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' to the left, 2) 'MAP\_NOTICE\_ind' to the right, 3) 'MAP\_CLOSE\_req' to the right, and 4) 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' to the right. The 'MAP\_NOTICE\_ind' and 'MAP\_CLOSE\_req' paths both lead to a 'Set User Error: System failure' state. From 'Set User Error: System failure', a 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_rsp, MAP\_CLOSE\_req' message is sent to the left, leading to 'Null'. The 'MAP\_CLOSE\_req' path also leads to a 'MAP\_U\_ABORT\_req' state, which leads to 'Null'. + +3407 + +3408 + +**Figure 22.10.4/1 (sheet 2 of 5): Process NW\_Init\_USSD\_HLR** + +![State transition diagram for process NW_Init_USSD_HLR. It starts with Wait_For_Next_USSD_Indication and branches based on incoming indications: MAP_CLOSE_ind, MAP_UNSTRUCTURED_SS_NOTIFY_ind, and MAP_UNSTRUCTURED_SS_REQUEST_ind. Each branch leads to a check, then either a response, a null state, or further signaling.](63db7f66a26834861edbcf76049f647c_img.jpg) + +**process NW\_Init\_USSD\_HLR** **NI\_USSD\_HLR3(5)** + +Process in the HLR to handle a network initiated USSD transaction + +Wait\_For\_Next\_USSD\_Indication + +Signals to/from the left are to/from the VLR; +signals to/from the right are to/from the next node (gsmSCF or secondary HLR) + +``` + +stateDiagram-v2 + [*] --> Wait_For_Next_USSD_Indication + state "MAP_CLOSE_ind" as MAP_CLOSE_ind + state "MAP_UNSTRUCTURED_SS_NOTIFY_ind" as MAP_UNSTRUCTURED_SS_NOTIFY_ind + state "MAP_UNSTRUCTURED_SS_REQUEST_ind" as MAP_UNSTRUCTURED_SS_REQUEST_ind + state "Check_Indication" as Check_Indication + state "Error" as Error + state "OK" as OK + state "Null" as Null + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_UNSTRUCTURED_SS_NOTIFY_rsp" as MAP_UNSTRUCTURED_SS_NOTIFY_rsp + state "MAP_UNSTRUCTURED_SS_REQUEST_rsp" as MAP_UNSTRUCTURED_SS_REQUEST_rsp + state "MAP_UNSTRUCTURED_SS_NOTIFY_req" as MAP_UNSTRUCTURED_SS_NOTIFY_req + state "MAP_DELIMITER_req" as MAP_DELIMITER_req + state "Wait_For_USSN_Confirm" as Wait_For_USSN_Confirm + state "MAP_UNSTRUCTURED_SS_NOTIFY_cnf" as MAP_UNSTRUCTURED_SS_NOTIFY_cnf + state "MAP_UNSTRUCTURED_SS_REQUEST_cnf" as MAP_UNSTRUCTURED_SS_REQUEST_cnf + state "Wait_For_Next_USSD_Indication" as Wait_For_Next_USSD_Indication + + Wait_For_Next_USSD_Indication --> MAP_CLOSE_ind + Wait_For_Next_USSD_Indication --> MAP_UNSTRUCTURED_SS_NOTIFY_ind + Wait_For_Next_USSD_Indication --> MAP_UNSTRUCTURED_SS_REQUEST_ind + + MAP_CLOSE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Null + + MAP_UNSTRUCTURED_SS_NOTIFY_ind --> Check_Indication + Check_Indication --> Error + Check_Indication --> OK + Error --> Null + OK --> MAP_UNSTRUCTURED_SS_NOTIFY_rsp + MAP_UNSTRUCTURED_SS_NOTIFY_rsp --> MAP_CLOSE_req + MAP_CLOSE_req --> Null + + MAP_UNSTRUCTURED_SS_REQUEST_ind --> Check_Indication + Check_Indication --> Error + Check_Indication --> OK + Error --> Null + OK --> MAP_UNSTRUCTURED_SS_REQUEST_rsp + MAP_UNSTRUCTURED_SS_REQUEST_rsp --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_USSN_Confirm + Wait_For_USSN_Confirm --> MAP_UNSTRUCTURED_SS_REQUEST_cnf + MAP_UNSTRUCTURED_SS_REQUEST_cnf --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_Next_USSD_Indication + + MAP_UNSTRUCTURED_SS_NOTIFY_rsp --> MAP_UNSTRUCTURED_SS_NOTIFY_req + MAP_UNSTRUCTURED_SS_NOTIFY_req --> Wait_For_USSN_Confirm + Wait_For_USSN_Confirm --> MAP_UNSTRUCTURED_SS_NOTIFY_cnf + MAP_UNSTRUCTURED_SS_NOTIFY_cnf --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_Next_USSD_Indication + +``` + +State transition diagram for process NW\_Init\_USSD\_HLR. It starts with Wait\_For\_Next\_USSD\_Indication and branches based on incoming indications: MAP\_CLOSE\_ind, MAP\_UNSTRUCTURED\_SS\_NOTIFY\_ind, and MAP\_UNSTRUCTURED\_SS\_REQUEST\_ind. Each branch leads to a check, then either a response, a null state, or further signaling. + +3409 + +3410 + +Figure 22.10.4/1 (sheet 3 of 5): Process NW\_Init\_USSD\_HLR + +![State transition diagram for process NW_Init_USSD_HLR. The diagram shows two main entry points from 'Null' states: 'Unstructured SS Notify' and 'Unstructured SS Request'. Both lead to 'MS reachable?' decision diamonds. If 'No', they lead to 'Set Negative response: MS not reachable' and then to 'Null'. If 'Yes', they lead to 'Receive_Open_Cnf' blocks. From 'Receive_Open_Cnf', 'OK' leads to 'Wait_For_USSN_Confirm_Local' and 'Vr, Error' leads to 'Abort' and then 'Null'. 'Wait_For_USSN_Confirm_Local' leads to a 'MAP_NOTICE_ind' block, which then leads to 'MAP_CLOSE_req' and 'Abort' to 'Null'. 'Wait_For_USSN_Confirm_Local' also leads to a 'Wait_For_Next_USSD_Instruction, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local' block, which leads to 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' and then to 'Abort' to 'Null'. 'Unstructured SS Request' path is similar but leads to 'Wait_For_USSR_Confirm_Local' and 'MAP_U_ABORT_req' to 'Null'.](b4c2c3df00aa13813eab98fa243a456f_img.jpg) + +**process NW\_Init\_USSD\_HLR** **NI\_USSD\_HLR4(5)** + +Process in the HLR to handle a network initiated USSD transaction + +Signals to/from the left are to/from the VLR; +signals to/from the right are to/from the USSD application in the HLR + +``` + +stateDiagram-v2 + [*] --> Null1[Null] + Null1 --> Unstructured_SS_Notify[Unstructured SS Notify] + Null1 --> Unstructured_SS_Request[Unstructured SS Request] + + Unstructured_SS_Notify --> MS_Reachable_Notify{MS reachable?} + MS_Reachable_Notify -- No --> Set_Neg_Response_Notify[Set Negative response: MS not reachable] + Set_Neg_Response_Notify --> Null2[Null] + + MS_Reachable_Notify -- Yes --> Receive_Open_Cnf_Notify[Receive_Open_Cnf] + Receive_Open_Cnf_Notify -- OK --> Wait_For_USSN_Confirm_Local_Notify[Wait_For_USSN_Confirm_Local] + Receive_Open_Cnf_Notify -- Vr, Error --> Abort_Notify[Abort] + Abort_Notify --> Null3[Null] + + Unstructured_SS_Request --> MS_Reachable_Request{MS reachable?} + MS_Reachable_Request -- No --> Set_Neg_Response_Request[Set Negative response: MS not reachable] + Set_Neg_Response_Request --> Null4[Null] + + MS_Reachable_Request -- Yes --> Receive_Open_Cnf_Request[Receive_Open_Cnf] + Receive_Open_Cnf_Request -- OK --> Wait_For_USSR_Confirm_Local_Request[Wait_For_USSR_Confirm_Local] + Receive_Open_Cnf_Request -- Vr, Error --> Abort_Request[Abort] + Abort_Request --> Null5[Null] + + Wait_For_USSN_Confirm_Local_Notify --> MAP_NOTICE_ind[MAP_NOTICE_ind] + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> Abort_Notify + Abort_Notify --> Null3 + + Wait_For_USSN_Confirm_Local_Notify --> Wait_For_Next_USSD_Instruction[Wait_For_Next_USSD_Instruction, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local] + Wait_For_Next_USSD_Instruction --> MAP_P_ABORT_ind[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] + MAP_P_ABORT_ind --> Abort_Notify + Abort_Notify --> Null3 + + Wait_For_USSR_Confirm_Local_Request --> Wait_For_USSN_Confirm_Local_Request[Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local] + Wait_For_USSN_Confirm_Local_Request --> MAP_U_ABORT_req[MAP_U_ABORT_req] + MAP_U_ABORT_req --> Null5 + +``` + +State transition diagram for process NW\_Init\_USSD\_HLR. The diagram shows two main entry points from 'Null' states: 'Unstructured SS Notify' and 'Unstructured SS Request'. Both lead to 'MS reachable?' decision diamonds. If 'No', they lead to 'Set Negative response: MS not reachable' and then to 'Null'. If 'Yes', they lead to 'Receive\_Open\_Cnf' blocks. From 'Receive\_Open\_Cnf', 'OK' leads to 'Wait\_For\_USSN\_Confirm\_Local' and 'Vr, Error' leads to 'Abort' and then 'Null'. 'Wait\_For\_USSN\_Confirm\_Local' leads to a 'MAP\_NOTICE\_ind' block, which then leads to 'MAP\_CLOSE\_req' and 'Abort' to 'Null'. 'Wait\_For\_USSN\_Confirm\_Local' also leads to a 'Wait\_For\_Next\_USSD\_Instruction, Wait\_For\_USSN\_Confirm\_Local, Wait\_For\_USSR\_Confirm\_Local' block, which leads to 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' and then to 'Abort' to 'Null'. 'Unstructured SS Request' path is similar but leads to 'Wait\_For\_USSR\_Confirm\_Local' and 'MAP\_U\_ABORT\_req' to 'Null'. + +3411 + +3412 + +Figure 22.10.4/1 (sheet 4 of 5): Process NW\_Init\_USSD\_HLR + +![State transition diagram for process NW_Init_USSD_HLR. The process starts in 'Wait_For_Next_USSD_Instruction' and branches into three paths: 'USSD release' leading to 'Null', 'Unstructured SS Notify' leading to 'MAP_UNSTRUCTURED_SS_NOTIFY_req' and then 'Wait_For_USSN_Confirm_Local', and 'Unstructured SS Request' leading to 'MAP_UNSTRUCTURED_SS_REQUEST_req' and then 'Wait_For_USSR_Confirm_Local'. Both wait states lead to 'Check_Confirmation' which branches into 'Set negative response' or 'Set ack' based on 'User Error, Data Error, Provider Error' or 'OK'. All paths eventually lead back to 'Wait_For_Next_USSD_Instruction'.](7dd9a58aeb9a178544e2002f8b43f0d7_img.jpg) + +**process NW\_Init\_USSD\_HLR** **NI\_USSD\_HLR5(5)** + +Process in the HLR to handle a network initiated USSD transaction + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the USSD application in the HLR + +``` + +stateDiagram-v2 + [*] --> Wait_For_Next_USSD_Instruction + state "Wait_For_Next_USSD_Instruction" as Wait_For_Next_USSD_Instruction + state "USSD release" as USSD_release + state "Unstructured SS Notify" as Unstructured_SS_Notify + state "Unstructured SS Request" as Unstructured_SS_Request + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "Null" as Null + state "MAP_UNSTRUCTURED_SS_NOTIFY_req" as MAP_UNSTRUCTURED_SS_NOTIFY_req + state "MAP_DELIMITER_req" as MAP_DELIMITER_req + state "Wait_For_USSN_Confirm_Local" as Wait_For_USSN_Confirm_Local + state "MAP_UNSTRUCTURED_SS_NOTIFY_cnf" as MAP_UNSTRUCTURED_SS_NOTIFY_cnf + state "Check_Confirmation" as Check_Confirmation + state "Set negative response" as Set_negative_response + state "Set ack" as Set_ack + state "Unstructured SS Notify negative response" as Unstructured_SS_Notify_negative_response + state "Unstructured SS Notify ack" as Unstructured_SS_Notify_ack + state "MAP_UNSTRUCTURED_SS_REQUEST_req" as MAP_UNSTRUCTURED_SS_REQUEST_req + state "MAP_DELIMITER_req" as MAP_DELIMITER_req + state "Wait_For_USSR_Confirm_Local" as Wait_For_USSR_Confirm_Local + state "MAP_UNSTRUCTURED_SS_REQUEST_cnf" as MAP_UNSTRUCTURED_SS_REQUEST_cnf + state "Check_Confirmation" as Check_Confirmation + state "Set negative response" as Set_negative_response + state "Set ack" as Set_ack + state "Unstructured SS Request negative response" as Unstructured_SS_Request_negative_response + state "Unstructured SS Request ack" as Unstructured_SS_Request_ack + + Wait_For_Next_USSD_Instruction --> USSD_release + Wait_For_Next_USSD_Instruction --> Unstructured_SS_Notify + Wait_For_Next_USSD_Instruction --> Unstructured_SS_Request + + USSD_release --> MAP_CLOSE_req + MAP_CLOSE_req --> Null + + Unstructured_SS_Notify --> MAP_UNSTRUCTURED_SS_NOTIFY_req + MAP_UNSTRUCTURED_SS_NOTIFY_req --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_USSN_Confirm_Local + Wait_For_USSN_Confirm_Local --> MAP_UNSTRUCTURED_SS_NOTIFY_cnf + MAP_UNSTRUCTURED_SS_NOTIFY_cnf --> Check_Confirmation + Check_Confirmation --> Set_negative_response : User Error, Data Error, Provider Error + Check_Confirmation --> Set_ack : OK + Set_negative_response --> Unstructured_SS_Notify_negative_response + Set_ack --> Unstructured_SS_Notify_ack + Unstructured_SS_Notify_negative_response --> Wait_For_Next_USSD_Instruction + Unstructured_SS_Notify_ack --> Wait_For_Next_USSD_Instruction + + Unstructured_SS_Request --> MAP_UNSTRUCTURED_SS_REQUEST_req + MAP_UNSTRUCTURED_SS_REQUEST_req --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_USSR_Confirm_Local + Wait_For_USSR_Confirm_Local --> MAP_UNSTRUCTURED_SS_REQUEST_cnf + MAP_UNSTRUCTURED_SS_REQUEST_cnf --> Check_Confirmation + Check_Confirmation --> Set_negative_response : User Error, Data Error, Provider Error + Check_Confirmation --> Set_ack : OK + Set_negative_response --> Unstructured_SS_Request_negative_response + Set_ack --> Unstructured_SS_Request_ack + Unstructured_SS_Request_negative_response --> Wait_For_Next_USSD_Instruction + Unstructured_SS_Request_ack --> Wait_For_Next_USSD_Instruction + +``` + +State transition diagram for process NW\_Init\_USSD\_HLR. The process starts in 'Wait\_For\_Next\_USSD\_Instruction' and branches into three paths: 'USSD release' leading to 'Null', 'Unstructured SS Notify' leading to 'MAP\_UNSTRUCTURED\_SS\_NOTIFY\_req' and then 'Wait\_For\_USSN\_Confirm\_Local', and 'Unstructured SS Request' leading to 'MAP\_UNSTRUCTURED\_SS\_REQUEST\_req' and then 'Wait\_For\_USSR\_Confirm\_Local'. Both wait states lead to 'Check\_Confirmation' which branches into 'Set negative response' or 'Set ack' based on 'User Error, Data Error, Provider Error' or 'OK'. All paths eventually lead back to 'Wait\_For\_Next\_USSD\_Instruction'. + +3413 + +3414 + +Figure 22.10.4/1 (sheet 5 of 5): Process NW\_Init\_USSD\_HLR + +macrodefinition Start\_USSD\_HLR + +S\_USSD\_HLR1(1) + +Macro in the HLR to check the reachability of the subscriber for a network initiated USSD transaction + +![Flowchart for macrodefinition Start_USSD_HLR. It starts with an oval connector, followed by a decision 'Subscriber known?'. If 'No', it goes to an 'Abort' circle. If 'Yes', it goes to 'Location known?'. If 'No', it goes to 'Set User Error: Absent subscriber' box. If 'Yes', it goes to 'MS purged?'. If 'Yes', it goes to 'Set User Error: Absent subscriber' box. If 'No', it goes to a decision diamond (MSC area restricted?). If 'Yes', it goes to 'MSC area restricted?' box. If 'No', it goes to another decision diamond (Roaming restriction due to unsupported feature?). If 'Yes', it goes to 'Roaming restriction due to unsupported feature?' box. Both 'Yes' paths lead to 'Set User Error: Absent subscriber' box. Finally, it leads to either an 'Error' circle or an 'OK' circle.](4fc51a9baa4c09a1aa997449702dcb05_img.jpg) + +``` + +graph TD + Start([ ]) --> D1{Subscriber known?} + D1 -- No --> Abort((Abort)) + D1 -- Yes --> D2{Location known?} + D2 -- No --> SetError[Set User Error: Absent subscriber] + D2 -- Yes --> D3{MS purged?} + D3 -- Yes --> SetError + D3 -- No --> D4{ } + D4 -- Yes --> MSCRestricted[MSC area restricted?] + D4 -- No --> D5{ } + D5 -- Yes --> RoamingRestriction[Roaming restriction due to unsupported feature?] + D5 -- No --> SetError + SetError --> Error((Error)) + D5 -- No --> OK((OK)) + +``` + +Flowchart for macrodefinition Start\_USSD\_HLR. It starts with an oval connector, followed by a decision 'Subscriber known?'. If 'No', it goes to an 'Abort' circle. If 'Yes', it goes to 'Location known?'. If 'No', it goes to 'Set User Error: Absent subscriber' box. If 'Yes', it goes to 'MS purged?'. If 'Yes', it goes to 'Set User Error: Absent subscriber' box. If 'No', it goes to a decision diamond (MSC area restricted?). If 'Yes', it goes to 'MSC area restricted?' box. If 'No', it goes to another decision diamond (Roaming restriction due to unsupported feature?). If 'Yes', it goes to 'Roaming restriction due to unsupported feature?' box. Both 'Yes' paths lead to 'Set User Error: Absent subscriber' box. Finally, it leads to either an 'Error' circle or an 'OK' circle. + +3415 + +3416 + +Figure 22.10.4/2: Macro Start\_USSD\_HLR + +![State transition diagram for process NI_USSD_gsmSCF_Secondary_HLR. The diagram shows two main entry points from 'Null' states. The left path is for 'Unstructured SS Notify' and the right path is for 'Unstructured SS Request'. Both paths lead to 'Receive_Open_Cnf' states with associated MAP messages. From 'Receive_Open_Cnf', 'OK' leads to 'Wait_For_USSN_Confirm_Local' or 'Wait_For_USSR_Confirm_Local' states, while 'Vr, Error' leads to 'Abort' and then 'Null'. The 'Wait' states lead to a central loop involving 'MAP_NOTICE_ind', 'MAP_CLOSE_req', and 'Abort' transitions, eventually returning to 'Null'.](e3ed7cd4fa87f55c884d0d7548b8ae7d_img.jpg) + +**process NI\_USSD\_gsmSCF\_Secondary\_HLR** **NI\_USSD\_SCF1(2)** + +Process in the gsmSCF or secondary HLR to handle a network initiated USSD transaction + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the USSD application process + +``` + +stateDiagram-v2 + [*] --> Null1[Null] + Null1 --> Unstructured_SS_Notify[Unstructured SS Notify] + Null1 --> Unstructured_SS_Request[Unstructured SS Request] + + Unstructured_SS_Notify --> Receive_Open_Cnf_Notify[Receive_Open_Cnf] + Unstructured_SS_Notify --> MAP_Open_Notify[MAP_OPEN_req, MAP_UNSTRUCTURED_SS_NOTIFY_req, MAP_DELIMITER_req] + + Unstructured_SS_Request --> Receive_Open_Cnf_Request[Receive_Open_Cnf] + Unstructured_SS_Request --> MAP_Open_Request[MAP_OPEN_req, MAP_UNSTRUCTURED_SS_REQUEST_req, MAP_DELIMITER_req] + + Receive_Open_Cnf_Notify --> Wait_For_USSN_Confirm_Local_Notify[Wait_For_USSN_Confirm_Local] + Receive_Open_Cnf_Notify --> Abort_Notify[Abort] + Wait_For_USSN_Confirm_Local_Notify --> Null2[Null] + Abort_Notify --> Null2 + + Receive_Open_Cnf_Request --> Wait_For_USSR_Confirm_Local_Request[Wait_For_USSR_Confirm_Local] + Receive_Open_Cnf_Request --> Abort_Request[Abort] + Wait_For_USSR_Confirm_Local_Request --> Null3[Null] + Abort_Request --> Null3 + + Wait_For_USSN_Confirm_Local_Notify --> Wait_For_Next_USSD_Instruction[Wait_For_Next_USSD_Instruction, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local] + Wait_For_USSR_Confirm_Local_Request --> Wait_For_USSN_Confirm_Local_Wait[Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local] + + Wait_For_Next_USSD_Instruction --> MAP_NOTICE_ind[MAP_NOTICE_ind] + Wait_For_USSN_Confirm_Local_Wait --> Abort_Wait[Abort] + + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> MAP_P_abort_ind[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] + MAP_CLOSE_req --> MAP_U_abort_req[MAP_U_ABORT_req] + + MAP_P_abort_ind --> Abort_Wait + MAP_U_abort_req --> Null4[Null] + +``` + +State transition diagram for process NI\_USSD\_gsmSCF\_Secondary\_HLR. The diagram shows two main entry points from 'Null' states. The left path is for 'Unstructured SS Notify' and the right path is for 'Unstructured SS Request'. Both paths lead to 'Receive\_Open\_Cnf' states with associated MAP messages. From 'Receive\_Open\_Cnf', 'OK' leads to 'Wait\_For\_USSN\_Confirm\_Local' or 'Wait\_For\_USSR\_Confirm\_Local' states, while 'Vr, Error' leads to 'Abort' and then 'Null'. The 'Wait' states lead to a central loop involving 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', and 'Abort' transitions, eventually returning to 'Null'. + +3417 + +3418 + +**Figure 22.10.5/1 (sheet 1 of 2): Process NW\_Init\_USSD\_gsmSCF\_secondary\_HLR** + +![State transition diagram for process NI_USSD_gsmSCF_Secondary_HLR. The diagram shows three main paths starting from 'Wait_For_Next_USSD_Instruction': 1) USSD release leads to MAP_CLOSE_req and Null. 2) Unstructured SS Notify leads to MAP_UNSTRUCTURED_SS_NOTIFY_req, Wait_For_USSN_Confirm_Local, MAP_UNSTRUCTURED_SS_NOTIFY_cnf, Check_Confirm, and then either Set negative response or Set ack, leading to Unstructured SS Notify negative response or Unstructured SS Notify ack, and finally back to Wait_For_Next_USSD_Instruction. 3) Unstructured SS Request leads to MAP_UNSTRUCTURED_SS_REQUEST_req, Wait_For_USSR_Confirm_Local, MAP_UNSTRUCTURED_SS_REQUEST_cnf, Check_Confirm, and then either Set negative response or Set ack, leading to Unstructured SS Request negative response or Unstructured SS Request ack, and finally back to Wait_For_Next_USSD_Instruction.](8f58a770e664298894e5d40a9261aafa_img.jpg) + +**process NI\_USSD\_gsmSCF\_Secondary\_HLR** **NI\_USSD\_SCF2(2)** + +Process in the gsmSCF or secondary HLR to handle a network initiated USSD transaction + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the USSD application process + +``` + +stateDiagram-v2 + [*] --> Wait_For_Next_USSD_Instruction + state "Wait_For_Next_USSD_Instruction" as Wait_For_Next_USSD_Instruction + state "USSD release" as USSD_release + state "Unstructured SS Notify" as Unstructured_SS_Notify + state "Unstructured SS Request" as Unstructured_SS_Request + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "Null" as Null + state "MAP_UNSTRUCTURED_SS_NOTIFY_req" as MAP_UNSTRUCTURED_SS_NOTIFY_req + state "Wait_For_USSN_Confirm_Local" as Wait_For_USSN_Confirm_Local + state "MAP_UNSTRUCTURED_SS_NOTIFY_cnf" as MAP_UNSTRUCTURED_SS_NOTIFY_cnf + state "Check_Confirm" as Check_Confirm + state "Set negative response" as Set_negative_response + state "Set ack" as Set_ack + state "Unstructured SS Notify negative response" as Unstructured_SS_Notify_negative_response + state "Unstructured SS Notify ack" as Unstructured_SS_Notify_ack + state "MAP_UNSTRUCTURED_SS_REQUEST_req" as MAP_UNSTRUCTURED_SS_REQUEST_req + state "Wait_For_USSR_Confirm_Local" as Wait_For_USSR_Confirm_Local + state "MAP_UNSTRUCTURED_SS_REQUEST_cnf" as MAP_UNSTRUCTURED_SS_REQUEST_cnf + state "Unstructured SS Request negative response" as Unstructured_SS_Request_negative_response + state "Unstructured SS Request ack" as Unstructured_SS_Request_ack + + Wait_For_Next_USSD_Instruction --> USSD_release + Wait_For_Next_USSD_Instruction --> Unstructured_SS_Notify + Wait_For_Next_USSD_Instruction --> Unstructured_SS_Request + + USSD_release --> MAP_CLOSE_req + MAP_CLOSE_req --> Null + + Unstructured_SS_Notify --> MAP_UNSTRUCTURED_SS_NOTIFY_req + MAP_UNSTRUCTURED_SS_NOTIFY_req --> Wait_For_USSN_Confirm_Local + Wait_For_USSN_Confirm_Local --> MAP_UNSTRUCTURED_SS_NOTIFY_cnf + MAP_UNSTRUCTURED_SS_NOTIFY_cnf --> Check_Confirm + Check_Confirm --> Set_negative_response : User Error, Data Error, Provider Error + Check_Confirm --> Set_ack : OK + Set_negative_response --> Unstructured_SS_Notify_negative_response + Set_ack --> Unstructured_SS_Notify_ack + Unstructured_SS_Notify_negative_response --> Wait_For_Next_USSD_Instruction + Unstructured_SS_Notify_ack --> Wait_For_Next_USSD_Instruction + + Unstructured_SS_Request --> MAP_UNSTRUCTURED_SS_REQUEST_req + MAP_UNSTRUCTURED_SS_REQUEST_req --> Wait_For_USSR_Confirm_Local + Wait_For_USSR_Confirm_Local --> MAP_UNSTRUCTURED_SS_REQUEST_cnf + MAP_UNSTRUCTURED_SS_REQUEST_cnf --> Check_Confirm + Check_Confirm --> Set_negative_response : User Error, Data Error, Provider Error + Check_Confirm --> Set_ack : OK + Set_negative_response --> Unstructured_SS_Request_negative_response + Set_ack --> Unstructured_SS_Request_ack + Unstructured_SS_Request_negative_response --> Wait_For_Next_USSD_Instruction + Unstructured_SS_Request_ack --> Wait_For_Next_USSD_Instruction + +``` + +State transition diagram for process NI\_USSD\_gsmSCF\_Secondary\_HLR. The diagram shows three main paths starting from 'Wait\_For\_Next\_USSD\_Instruction': 1) USSD release leads to MAP\_CLOSE\_req and Null. 2) Unstructured SS Notify leads to MAP\_UNSTRUCTURED\_SS\_NOTIFY\_req, Wait\_For\_USSN\_Confirm\_Local, MAP\_UNSTRUCTURED\_SS\_NOTIFY\_cnf, Check\_Confirm, and then either Set negative response or Set ack, leading to Unstructured SS Notify negative response or Unstructured SS Notify ack, and finally back to Wait\_For\_Next\_USSD\_Instruction. 3) Unstructured SS Request leads to MAP\_UNSTRUCTURED\_SS\_REQUEST\_req, Wait\_For\_USSR\_Confirm\_Local, MAP\_UNSTRUCTURED\_SS\_REQUEST\_cnf, Check\_Confirm, and then either Set negative response or Set ack, leading to Unstructured SS Request negative response or Unstructured SS Request ack, and finally back to Wait\_For\_Next\_USSD\_Instruction. + +3419 + +3420 + +**Figure 22.10.5/1 (sheet 2 of 2): Process NW\_Init\_USSD\_gsmSCF\_Secondary\_HLR** + +## 3421 22.11 Common macros for clause 22 + +3422 The following macros are used for the description of more than one of the supplementary service processes described in +3423 clause 22. + +### 3424 22.11.1 SS Password handling macros + +#### 3425 **Macro Get\_Password\_MSC** + +3426 This macro is used by the MSC to relay a request for password from the VLR to the MS, and to relay a response from +3427 the MS back to the VLR. The macro is shown in figure 22.11.1/1. + +#### 3428 **Macro Get\_Password\_VLR** + +3429 This macro is used by the VLR to relay a request for password from the HLR to the MSC, and to relay a response from +3430 the MSC back to the HLR. The macro invokes a macro not defined in this clause; the definition of this macro can be +3431 found as follows: + +3432     Check\_Indication               see clause 25.2.1. + +3433 The macro is shown in figure 22.11.1/2. + +### 3434 22.11.2 Void + +![Sequence diagram for Get_Password_MSC macro. The process starts with a MAP_GET_PASSWORD_ind, followed by an A_GET_PASSWORD_req. It then enters a 'Wait_For_Password' state. From there, three possible outcomes are shown: 1) A CM SERV_RELEASE_ind leads to a MAP_U_ABORT_req and an A_CM_RELEASE_COMPLETE_req, ending in a Null state. 2) An A_GET_PASSWORD_cnf leads to a MAP_GET_PASSWORD_rsp and a MAP_DELIMITER_req, ending in an OK state. 3) An unlabeled signal leads to a MAP_U_ABORT_ind and a MAP_CLOSE_ind, followed by an A_CM_RELEASE_req and ending in a Null state. A note indicates that signals to/from the left are to/from the MS, and signals to/from the right are to/from the VLR. Another note indicates this macro relays a password request and response.](a50ae81de6cad563aeaa11bc7d744359_img.jpg) + +macrodefinition Get\_Password\_MSC Get\_Pwd\_MSC1(1) + +Macro in the MSC to relay a password request and response + +Signals to/from the left are to/from the MS; +signals to/from the right are to/from the VLR + +``` + +sequenceDiagram + participant MS + participant VLR + Note left of MS: Macro in the MSC to relay a password request and response + Note right of VLR: Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR + + MS->>VLR: MAP_GET_PASSWORD_ind + VLR->>MS: A_GET_PASSWORD_req + Note right of VLR: Wait_For_Password + alt Path 1: CM Release + VLR->>MS: A_CM_SERV_RELEASE_ind + MS->>VLR: MAP_U_ABORT_req + Note right of VLR: Application procedure cancellation + VLR->>MS: A_CM_RELEASE_COMPLETE_req + Note right of MS: Null + alt Path 2: Password Confirm + VLR->>MS: A_GET_PASSWORD_cnf + MS->>VLR: MAP_GET_PASSWORD_rsp + Note right of VLR: MAP_DELIMITER_req + Note right of MS: OK + alt Path 3: Abort/Close + VLR->>MS: + MS->>VLR: MAP_U_ABORT_ind + Note right of VLR: MAP_CLOSE_ind + VLR->>MS: A_CM_RELEASE_req + Note right of MS: Null + +``` + +Sequence diagram for Get\_Password\_MSC macro. The process starts with a MAP\_GET\_PASSWORD\_ind, followed by an A\_GET\_PASSWORD\_req. It then enters a 'Wait\_For\_Password' state. From there, three possible outcomes are shown: 1) A CM SERV\_RELEASE\_ind leads to a MAP\_U\_ABORT\_req and an A\_CM\_RELEASE\_COMPLETE\_req, ending in a Null state. 2) An A\_GET\_PASSWORD\_cnf leads to a MAP\_GET\_PASSWORD\_rsp and a MAP\_DELIMITER\_req, ending in an OK state. 3) An unlabeled signal leads to a MAP\_U\_ABORT\_ind and a MAP\_CLOSE\_ind, followed by an A\_CM\_RELEASE\_req and ending in a Null state. A note indicates that signals to/from the left are to/from the MS, and signals to/from the right are to/from the VLR. Another note indicates this macro relays a password request and response. + +3435 + +3436 + +Figure 22.11.1/1: Macro Get\_Password\_MSC + +![Sequence diagram for macro Get_Password_VLR. The process starts with an indication MAP_GET_PASSWORD_ind, followed by a 'Check_Indication' block. If 'Error', it sends MAP_U_ABORT_req to the left and ends at a 'Null' state. If 'OK', it sends MAP_GET_PASSWORD_req and MAP_DELIMITER_req to the right, enters 'Wait_For_Password' state, and then branches based on incoming signals (MAP_U_ABORT_ind, MAP_GET_PASSWORD_cnf, MAP_NOTICE_ind, MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind). The 'MAP_GET_PASSWORD_cnf' path leads to a response MAP_GET_PASSWORD_rsp and MAP_DELIMITER_req to the right, ending at an 'OK' state. Other paths lead to 'Null' states via MAP_U_ABORT_req or MAP_CLOSE_req.](a7de6044abdc076b478fd75ba2473648_img.jpg) + +macrodefinition Get\_Password\_VLR Get\_Pwd\_VLR1(1) + +Macro in the VLR to relay a password request and response + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR + +``` + +sequenceDiagram + participant VLR + Note left of VLR: Macro in the VLR to relay a password request and response + Note right of VLR: Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR + + VLR->>VLR: MAP_GET_PASSWORD_ind + VLR->>VLR: Check_Indication + alt Error + VLR->>Left: MAP_U_ABORT_req + VLR-->>Null1((Null)) + else OK + VLR->>Right: MAP_GET_PASSWORD_req + VLR->>Right: MAP_DELIMITER_req + VLR->>VLR: Wait_For_Password + alt MAP_U_ABORT_ind, MAP_CLOSE_ind + VLR->>Left: MAP_U_ABORT_req + VLR-->>Null2((Null)) + else MAP_GET_PASSWORD_cnf + VLR->>Right: MAP_GET_PASSWORD_rsp + VLR->>Right: MAP_DELIMITER_req + VLR-->>OK((OK)) + else MAP_NOTICE_ind + VLR->>Right: MAP_CLOSE_req + VLR-->>Null3((Null)) + else MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind + VLR->>Right: MAP_CLOSE_req + VLR-->>Null4((Null)) + end + end + +``` + +Sequence diagram for macro Get\_Password\_VLR. The process starts with an indication MAP\_GET\_PASSWORD\_ind, followed by a 'Check\_Indication' block. If 'Error', it sends MAP\_U\_ABORT\_req to the left and ends at a 'Null' state. If 'OK', it sends MAP\_GET\_PASSWORD\_req and MAP\_DELIMITER\_req to the right, enters 'Wait\_For\_Password' state, and then branches based on incoming signals (MAP\_U\_ABORT\_ind, MAP\_GET\_PASSWORD\_cnf, MAP\_NOTICE\_ind, MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind). The 'MAP\_GET\_PASSWORD\_cnf' path leads to a response MAP\_GET\_PASSWORD\_rsp and MAP\_DELIMITER\_req to the right, ending at an 'OK' state. Other paths lead to 'Null' states via MAP\_U\_ABORT\_req or MAP\_CLOSE\_req. + +3437 + +3438 + +Figure 22.11.1/2: Macro Get\_Password\_VLR + +3439 + +Figure 22.11.2/1 void + +3440 + +Figure 22.11.2/2 void + +3441 + +Figure 22.11.2/3 void + +3442 + +Figure 22.11.2/4 void + + + +## 22.12 Supplementary Service Invocation Notification procedure + +### 22.12.1 General + +The Supplementary Service Invocation Notification procedure is used to notify a gsmSCF about the invocation of a GSM Supplementary Service. + +The supplementary service invocation notification procedure is shown in figure 22.12.1/1. + +The following service is certainly used: + +MAP\_SS\_INVOCATION\_NOTIFY (defined in clause 11). + +![Sequence diagram showing the message flow for supplementary service invocation notification between an MSC and a gsmSCF. The MSC sends a message to the gsmSCF (labeled 1), and the gsmSCF sends a response back to the MSC (labeled 2).](cf347939c11f91fbebf49d96e8713d63_img.jpg) + +``` +sequenceDiagram + participant MSC + participant gsmSCF + Note right of gsmSCF: 1 + MSC->>gsmSCF: MAP_SS_INVOCATION_NOTIFY_req/ind + Note left of MSC: 2 + gsmSCF-->>MSC: MAP_SS_INVOCATION_NOTIFY_rsp/cnf +``` + +Sequence diagram showing the message flow for supplementary service invocation notification between an MSC and a gsmSCF. The MSC sends a message to the gsmSCF (labeled 1), and the gsmSCF sends a response back to the MSC (labeled 2). + +- 1) MAP\_SS\_INVOCATION\_NOTIFY\_req/ind +2) MAP\_SS\_INVOCATION\_NOTIFY\_rsp/cnf +- Figure 22.12.1/1: Message flow for supplementary service invocation notification** + +### 22.12.2 Procedure in the MSC + +The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +Receive\_Open\_Cnf see clause 25.1.2; + +Check\_Confirmation see clause 25.2.2. + +The supplementary service invocation notification process in the MSC is shown in figure 22.12.2/1. + +### 22.12.3 Procedure in the gsmSCF + +The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +Receive\_Open\_Ind see clause 25.1.1. + +The supplementary service invocation notification process in the gsmSCF is shown in figure 22.12.3/1. + +![Sequence diagram for process Notify_SS_Invocation_MSC. The process starts with an initial node, followed by 'Null', 'Note SS invocation', and a request block containing MAP_OPEN_req, MAP_SS_INVOCATION_NOTIFY_req, and MAP_DELIMITER_req. It then enters 'Receive_Open_Cnf', which leads to 'Abort' on error or 'Wait_For_gsmSCF_Response' on OK. The wait state leads to three parallel paths: one for MAP_P_ABORT_ind, MAP_U_ABORT_ind, and MAP_CLOSE_ind; one for MAP_NOTICE_ind leading to MAP_CLOSE_req; and one for MAP_SS_INVOCATION_NOTIFY_cnf leading to 'Check_Confirmation'. 'Check_Confirmation' leads to 'Note SS invocation ack' on OK, or 'Set Negative response: System failure' on User Error or Provider/Data Error, which then leads to 'Note SS invocation negative response'. All three parallel paths eventually lead to a 'Null' terminal node.](222390abf7ceb44aaaf7f6e994ec33ff_img.jpg) + +**process Notify\_SS\_Invocation\_MSC** **NSSI\_MSC1(1)** + +Process in the MSC to notify the gsmSCF that a supplementary service has been invoked + +Signals to/from the left are to/from the SS handling application process in the MSC; signals to/from the right are to/from the gsmSCF + +``` + +sequenceDiagram + participant Start as + participant Null1[Null] + participant NoteSS[Note SS invocation] + participant Req["MAP_OPEN_req +MAP_SS_INVOCATION_NOTIFY_req +MAP_DELIMITER_req"] + participant RecOpenCnf[Receive_Open_Cnf] + participant Abort{Abort} + participant WaitForResponse[Wait_For_gsmSCF_Response] + participant PAbortInd["MAP_P_ABORT_ind, +MAP_U_ABORT_ind, +MAP_CLOSE_ind"] + participant NoticeInd[MAP_NOTICE_ind] + participant CloseReq[MAP_CLOSE_req] + participant ConfirmCnf[MAP_SS_INVOCATION_NOTIFY_cnf] + participant CheckConfirmation[Check_Confirmation] + participant NegResponse1[Set Negative response: +System failure] + participant NegResponse2[Set Negative response: +System failure] + participant NegResponse3[Set Negative response: +System failure] + participant NoteSSNeg[Note SS invocation negative response] + participant NoteSSAck[Note SS invocation ack] + participant Null2[Null] + participant Null3[Null] + participant Null4[Null] + + Note left of Start: Process in the MSC to notify the gsmSCF that a supplementary service has been invoked + Start --> Null1 + Null1 --> NoteSS + NoteSS --> Req + Req --> RecOpenCnf + RecOpenCnf --> Abort: Vr, Error + RecOpenCnf --> WaitForResponse: OK + Abort --> Null2 + WaitForResponse --> PAbortInd + WaitForResponse --> NoticeInd + WaitForResponse --> ConfirmCnf + PAbortInd --> NegResponse1 + NoticeInd --> CloseReq + CloseReq --> NegResponse1 + ConfirmCnf --> CheckConfirmation + CheckConfirmation --> NoteSSAck: OK + CheckConfirmation --> NegResponse2: User Error + CheckConfirmation --> NegResponse3: Provider Error, Data Error + NegResponse1 --> NoteSSNeg + NoteSSNeg --> Null2 + NoteSSAck --> Null3 + NegResponse2 --> NoteSSNeg + NoteSSNeg --> Null4 + NegResponse3 --> NoteSSNeg + NoteSSNeg --> Null4 + +``` + +Sequence diagram for process Notify\_SS\_Invocation\_MSC. The process starts with an initial node, followed by 'Null', 'Note SS invocation', and a request block containing MAP\_OPEN\_req, MAP\_SS\_INVOCATION\_NOTIFY\_req, and MAP\_DELIMITER\_req. It then enters 'Receive\_Open\_Cnf', which leads to 'Abort' on error or 'Wait\_For\_gsmSCF\_Response' on OK. The wait state leads to three parallel paths: one for MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, and MAP\_CLOSE\_ind; one for MAP\_NOTICE\_ind leading to MAP\_CLOSE\_req; and one for MAP\_SS\_INVOCATION\_NOTIFY\_cnf leading to 'Check\_Confirmation'. 'Check\_Confirmation' leads to 'Note SS invocation ack' on OK, or 'Set Negative response: System failure' on User Error or Provider/Data Error, which then leads to 'Note SS invocation negative response'. All three parallel paths eventually lead to a 'Null' terminal node. + +3465 + +3466 + +**Figure 22.12.2/1: Process Notify\_SS\_Invocation\_MSC** + +![Flowchart for process Note_SS_Invocation_gsmSCF. It starts with an initial state leading to 'Null', then 'Receive Open_Ind'. From 'Receive Open_Ind', an 'OK' path leads to 'Wait_For_Service_Indication' and a 'Vr, Error' path leads to 'Null'. 'Wait_For_Service_Indication' leads to a junction. One path from the junction goes left through 'MAP_P_ABORT_ind' and 'MAP_NOTICE_ind' to 'MAP_CLOSE_req' and then to 'Null'. The other path goes right through a junction to 'MAP_SS_INVOCATION_NOTIFY_ind', then 'Note SS invocation', then 'Wait_For_Application_Response'. 'Wait_For_Application_Response' leads to another junction. One path from this junction goes left through 'Note SS invocation ack' to 'Set Result'. The other path goes right through 'Note SS invocation negative response' to 'Set User Error'. Both 'Set Result' and 'Set User Error' lead to a third junction. From this junction, a path goes right to 'MAP_SS_INVOCATION_NOTIFY_rsp' and 'MAP_CLOSE_req', and then down to the final 'Null' state.](56c813b6db0a87376846e0f6dde99095_img.jpg) + +**process Note\_SS\_Invocation\_gsmSCF** **NSSI\_SCF1(1)** + +Process in the gsmSCF to handle a notification of supplementary service invocation + +Signals to/from the left are to/from the MSC; +signals to/from the right are to/from the application process in the gsmSCF + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> RecOpen[Receive Open_Ind] + RecOpen -- OK --> WaitService[Wait_For_Service_Indication] + RecOpen -- "Vr, Error" --> Null2([Null]) + WaitService --> Junction1(( )) + Junction1 --> MAP_P_ABORT[MAP_P_ABORT_ind] + Junction1 --> MAP_NOTICE[MAP_NOTICE_ind] + Junction1 --> Junction2(( )) + MAP_P_ABORT --> MAP_CLOSE_req{MAP_CLOSE_req} + MAP_NOTICE --> MAP_CLOSE_req + MAP_CLOSE_req --> Null3([Null]) + Junction2 --> MAP_SS_NOTIFY_ind[MAP_SS_INVOCATION_NOTIFY_ind] + MAP_SS_NOTIFY_ind --> NoteSS[Note SS invocation] + NoteSS --> WaitApp[Wait_For_Application_Response] + WaitApp --> Junction3(( )) + Junction3 --> NoteSS_ack[Note SS invocation ack] + Junction3 --> NoteSS_neg[Note SS invocation negative response] + NoteSS_ack --> SetResult[Set Result] + NoteSS_neg --> SetUserError[Set User Error] + SetResult --> Junction4(( )) + SetUserError --> Junction4 + Junction4 --> MAP_SS_NOTIFY_rsp[MAP_SS_INVOCATION_NOTIFY_rsp] + Junction4 --> MAP_CLOSE_req2[MAP_CLOSE_req] + MAP_SS_NOTIFY_rsp --> Null4([Null]) + MAP_CLOSE_req2 --> Null4 + +``` + +Flowchart for process Note\_SS\_Invocation\_gsmSCF. It starts with an initial state leading to 'Null', then 'Receive Open\_Ind'. From 'Receive Open\_Ind', an 'OK' path leads to 'Wait\_For\_Service\_Indication' and a 'Vr, Error' path leads to 'Null'. 'Wait\_For\_Service\_Indication' leads to a junction. One path from the junction goes left through 'MAP\_P\_ABORT\_ind' and 'MAP\_NOTICE\_ind' to 'MAP\_CLOSE\_req' and then to 'Null'. The other path goes right through a junction to 'MAP\_SS\_INVOCATION\_NOTIFY\_ind', then 'Note SS invocation', then 'Wait\_For\_Application\_Response'. 'Wait\_For\_Application\_Response' leads to another junction. One path from this junction goes left through 'Note SS invocation ack' to 'Set Result'. The other path goes right through 'Note SS invocation negative response' to 'Set User Error'. Both 'Set Result' and 'Set User Error' lead to a third junction. From this junction, a path goes right to 'MAP\_SS\_INVOCATION\_NOTIFY\_rsp' and 'MAP\_CLOSE\_req', and then down to the final 'Null' state. + +3467 + +3468 + +**Figure 22.12.3/1: Process Note\_SS\_Invocation\_gsmSCF** + +3469 **22.13 Activation of a CCBS request** + +3470 **22.13.1 General** + +3471 The message flow to activate a CCBS request is shown in figure 22.13.1/1. + +3472 The following service is certainly used: + +3473        MAP\_REGISTER\_CC\_ENTRY        (defined in clause 11). + +![Sequence diagram showing message flow between VLR and HLR. Step 1: VLR to HLR. Step 2: HLR to VLR.](a8a60ff34b2c12d3b5ae528c9843d3fd_img.jpg) + +``` +sequenceDiagram + participant VLR + participant HLR + Note right of HLR: 1 + VLR->>HLR: + Note left of VLR: 2 + HLR->>VLR: +``` + +Sequence diagram showing message flow between VLR and HLR. Step 1: VLR to HLR. Step 2: HLR to VLR. + +3474 + +3475 + +3476    1)        MAP\_REGISTER\_CC\_ENTRY\_req/ind + +3477    2)        MAP\_REGISTER\_CC\_ENTRY\_rsp/cnf + +3478 + +3479 + +**Figure 22.13.1/1: Message flow to activate a CCBS request** + +3480 **22.13.2 Procedure in the VLR** + +3481 The MAP process in the VLR to activate a CCBS request is shown in figure 22.13.2/1. The MAP process invokes + +3482 macros not defined in this clause; the definitions of these macros can be found as follows: + +3483    Receive\_Open\_Cnf see clause 25.1.2; + +3484    Check\_Confirmation see clause 25.2.2. + +3485 **22.13.3 Procedure in the HLR** + +3486 The MAP process in the HLR to activate a CCBS request is shown in figure 22.13.2/1. + +![Flowchart for process Register_CC_Entry_VLR. It starts with an initial state, followed by a 'Null' state, then a 'CCBS request' input. It then sends MAP messages (MAP_OPEN_req, MAP_REGISTER_CC_ENTRY_req, MAP_DELIMITER_req) and receives 'Open_Cnf'. A 'Wait_For_Response_From_HLR' state follows. From there, it branches based on MAP messages: 'MAP_P_ABORT_ind' leads to 'Vr, Error'; 'MAP_NOTICE_ind' leads to 'MAP CLOSE_req'; 'MAP_REGISTER_CC_ENTRY_cnf' leads to 'Check_Confirmation'. 'Check_Confirmation' branches into 'Provider Error, Data Error', 'User Error', and 'OK'. 'Provider Error, Data Error' and 'User Error' both lead to 'Set Negative response: System failure' and 'CCBS request negative response', ending in 'Null'. 'OK' leads to 'CCBS request ack' and 'Null'. A 'Vr, Error' line also connects to 'Set Negative response: System failure' and 'CCBS request negative response'.](51feb1c455e865f743be045d0b423bb7_img.jpg) + +**process Register\_CC\_Entry\_VLR** **RCCE\_VLR1(1)** + +Process in the VLR to request registration of a Call Completion entry in the HLR + +Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> CCBS_req{CCBS request} + CCBS_req --> MAP_send[ ] + MAP_send --> MAP_req["MAP_OPEN_req +MAP_REGISTER_CC_ENTRY_req +MAP_DELIMITER_req"] + MAP_req --> Open_Cnf[Receive_Open_Cnf] + Open_Cnf --> Wait[Wait_For_Response_From_HLR] + Wait --> MAP_abort{MAP_P_ABORT_ind} + Wait --> MAP_notice{MAP_NOTICE_ind} + Wait --> MAP_cnf{MAP_REGISTER_CC_ENTRY_cnf} + MAP_abort --> Vr_Error[Vr, Error] + MAP_notice --> MAP_close[MAP CLOSE_req] + MAP_cnf --> Check[Check_Confirmation] + Check --> Provider_Error[Provider Error, Data Error] + Check --> User_Error[User Error] + Check --> OK[OK] + Provider_Error --> Neg_Sys[Set Negative response: +System failure] + User_Error --> Neg_User[Set Negative response] + Neg_Sys --> Neg_Req1{CCBS request negative response} + Neg_User --> Neg_Req2{CCBS request negative response} + OK --> Ack{CCBS request ack} + Neg_Req1 --> Null2([Null]) + Neg_Req2 --> Null3([Null]) + Ack --> Null4([Null]) + Vr_Error --> Neg_Sys + Vr_Error --> Neg_Req1 + +``` + +Flowchart for process Register\_CC\_Entry\_VLR. It starts with an initial state, followed by a 'Null' state, then a 'CCBS request' input. It then sends MAP messages (MAP\_OPEN\_req, MAP\_REGISTER\_CC\_ENTRY\_req, MAP\_DELIMITER\_req) and receives 'Open\_Cnf'. A 'Wait\_For\_Response\_From\_HLR' state follows. From there, it branches based on MAP messages: 'MAP\_P\_ABORT\_ind' leads to 'Vr, Error'; 'MAP\_NOTICE\_ind' leads to 'MAP CLOSE\_req'; 'MAP\_REGISTER\_CC\_ENTRY\_cnf' leads to 'Check\_Confirmation'. 'Check\_Confirmation' branches into 'Provider Error, Data Error', 'User Error', and 'OK'. 'Provider Error, Data Error' and 'User Error' both lead to 'Set Negative response: System failure' and 'CCBS request negative response', ending in 'Null'. 'OK' leads to 'CCBS request ack' and 'Null'. A 'Vr, Error' line also connects to 'Set Negative response: System failure' and 'CCBS request negative response'. + +3487 + +3488 + +Figure 22.13.2/1: Process Register\_CC\_Entry\_VLR + +![Flowchart for process Register_CC_Entry_HLR. The process starts with an oval, followed by a 'Null' block. It then enters a loop: a chevron (left) receives 'MAP_REGISTER_CC_ENTRY_ind' from the right, followed by a 'CCBS request' block, and a 'Wait For Application_Response' block. A decision point follows, leading to four paths: 1) 'MAP_NOTICE_ind' (left) leads to 'MAP_CLOSE_req' (left) which then leads to an 'Abort' block (left) and an end symbol. 2) A chevron (left) leads to a block with 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' (right) which then leads to the 'Abort' block. 3) 'CCBS request negative response' (right) leads to 'Ser User Error' (right) which then leads to a chevron (left) receiving 'MAP_REGISTER_CC_ENTRY_rsp' and 'MAP_CLOSE_req' (right) before ending. 4) 'CCBS request ack' (right) leads to 'Set Result' (right) which then leads to the same chevron and response block before ending.](2844c942c7f3a3a71d1ad69519978c0a_img.jpg) + +**process Register\_CC\_Entry\_HLR** **RCCE\_HLR1(1)** + +Process in the HLR to handle a request to register a Call Completion entry + +Signals to/from the left are to/from the VLR; signals to/from the right are to/from the CCBS application process in the HLR (see 3GPP TS 23.093) + +``` + + graph TD + Start([ ]) --> Null[Null] + Null --> In1{ } + In1 --> In1_Ext[MAP_REGISTER_CC_ENTRY_ind] + In1 --> CCBS[CCBS request] + CCBS --> Wait[Wait For Application_Response] + Wait --> Decision(( )) + + Decision --> Out1{ } + Out1 --> Out1_Ext[MAP_NOTICE_ind] + + Decision --> Out2{ } + + Decision --> Out3{ } + Out3 --> Out3_Ext[CCBS request negative response] + + Decision --> Out4{ } + Out4 --> Out4_Ext[CCBS request ack] + + Out1_Ext --> CloseReq1[MAP_CLOSE_req] + + Out3_Ext --> UserError[Ser User Error] + + Out4_Ext --> SetResult[Set Result] + + CloseReq1 --> Abort[Abort] + + UserError --> In2{ } + + SetResult --> In2 + + In2 --> In2_Ext[MAP_REGISTER_CC_ENTRY_rsp +MAP_CLOSE_req] + + Abort --> End1((X)) + + In2_Ext --> End2((X)) + +``` + +Flowchart for process Register\_CC\_Entry\_HLR. The process starts with an oval, followed by a 'Null' block. It then enters a loop: a chevron (left) receives 'MAP\_REGISTER\_CC\_ENTRY\_ind' from the right, followed by a 'CCBS request' block, and a 'Wait For Application\_Response' block. A decision point follows, leading to four paths: 1) 'MAP\_NOTICE\_ind' (left) leads to 'MAP\_CLOSE\_req' (left) which then leads to an 'Abort' block (left) and an end symbol. 2) A chevron (left) leads to a block with 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' (right) which then leads to the 'Abort' block. 3) 'CCBS request negative response' (right) leads to 'Ser User Error' (right) which then leads to a chevron (left) receiving 'MAP\_REGISTER\_CC\_ENTRY\_rsp' and 'MAP\_CLOSE\_req' (right) before ending. 4) 'CCBS request ack' (right) leads to 'Set Result' (right) which then leads to the same chevron and response block before ending. + +3489 + +3490 + +Figure 22.13.3/1: Process Register\_CC\_Entry\_HLR + +3491 **22.14 Deactivation of a CCBS request** + +3492 **22.14.1 General** + +3493 The message flow to deactivate a CCBS request is shown in figure 22.14.1/1. + +3494 The following service is certainly used: + +3495        MAP\_ERASE\_CC\_ENTRY        (defined in clause 11). + +![Sequence diagram showing message flow between VLR and HLR. Step 1: VLR to HLR. Step 2: HLR to VLR.](41995432d27e3667e838217005d3db93_img.jpg) + +``` +sequenceDiagram + participant VLR + participant HLR + Note right of HLR: 1 + VLR->>HLR: + Note left of VLR: 2 + HLR->>VLR: +``` + +Sequence diagram showing message flow between VLR and HLR. Step 1: VLR to HLR. Step 2: HLR to VLR. + +3496 + +3497 + +3498    1)        MAP\_ERASE\_CC\_ENTRY\_req/ind + +3499    2)        MAP\_ERASE\_CC\_ENTRY\_rsp/cnf + +3500 + +3501 + +**Figure 22.14.1/1: Message flow to deactivate a CCBS request** + +3502 **22.14.2 Procedure in the VLR** + +3503 The MAP process in the VLR to deactivate a CCBS request is shown in figure 22.14.2/1. The MAP process invokes + +3504 macros not defined in this clause; the definitions of these macros can be found as follows: + +3505        Receive\_Open\_Cnf see clause 25.1.2; + +3506        Check\_Confirmation see clause 25.2.2. + +3507 **22.14.3 Procedure in the HLR** + +3508 The MAP process in the HLR to deactivate a CCBS request is shown in figure 22.14.2/1. + +![Flowchart for process Erase_CC_Entry_VLR. The process starts with an initial node, followed by 'Null', 'Deactivate CCBS', and a block with MAP_OPEN_req, MAP_ERASE_CC_ENTRY_req, and MAP_DELIMITER_req. It then enters 'Receive_Open_Cnf'. From 'Receive_Open_Cnf', an 'OK' path leads to 'Wait_For_Response_From_HLR', while a 'Vr, Error' path leads to 'Set Negative response: System failure'. From 'Wait_For_Response_From_HLR', three paths emerge: 'MAP_P_ABORT_ind' leading to 'MAP CLOSE_req', 'MAP NOTICE_ind' leading to 'MAP CLOSE_req', and 'MAP_ERASE_CC_ENTRY_cnf' leading to 'Check Confirmation'. From 'Check Confirmation', three paths emerge: 'Provider Error, Data Error' leading to 'Set Negative response: System failure', 'User Error' leading to 'Set Negative response', and 'OK' leading to 'Deactivate CCBS ack'. All three paths from 'Check Confirmation' lead to 'Null' nodes. Both 'MAP CLOSE_req' and 'Set Negative response: System failure' lead to 'Deactivate CCBS negative response', which then leads to 'Null'.](54d5b7faa03d245014a06e342884c642_img.jpg) + +**process Erase\_CC\_Entry\_VLR** **ECCE\_VLR1(1)** + +Process in the VLR to request erasure of a Call Completion entry in the HLR + +Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> DeactivateCCBS1{Deactivate CCBS} + DeactivateCCBS1 --> MAP_Req["MAP_OPEN_req +MAP_ERASE_CC_ENTRY_req +MAP_DELIMITER_req"] + MAP_Req --> ReceiveOpenCnf[Receive_Open_Cnf] + ReceiveOpenCnf -- OK --> WaitForResponse[Wait_For_Response_From_HLR] + ReceiveOpenCnf -- "Vr, Error" --> SetNegSysFailure1[Set Negative response: +System failure] + WaitForResponse -- "MAP_P_ABORT_ind" --> MAPCloseReq1[MAP CLOSE_req] + WaitForResponse -- "MAP NOTICE_ind" --> MAPCloseReq2[MAP CLOSE_req] + WaitForResponse -- "MAP_ERASE_CC_ENTRY_cnf" --> CheckConfirmation[Check Confirmation] + CheckConfirmation -- "Provider Error, Data Error" --> SetNegSysFailure2[Set Negative response: +System failure] + CheckConfirmation -- "User Error" --> SetNegResponse[Set Negative response] + CheckConfirmation -- OK --> DeactivateCCBSAck{Deactivate CCBS ack} + SetNegSysFailure1 --> DeactivateCCBSNeg1{Deactivate CCBS negative response} + SetNegSysFailure2 --> DeactivateCCBSNeg2{Deactivate CCBS negative response} + SetNegResponse --> DeactivateCCBSNeg3{Deactivate CCBS negative response} + DeactivateCCBSAck --> Null2([Null]) + DeactivateCCBSNeg1 --> Null3([Null]) + DeactivateCCBSNeg2 --> Null4([Null]) + DeactivateCCBSNeg3 --> Null5([Null]) + +``` + +Flowchart for process Erase\_CC\_Entry\_VLR. The process starts with an initial node, followed by 'Null', 'Deactivate CCBS', and a block with MAP\_OPEN\_req, MAP\_ERASE\_CC\_ENTRY\_req, and MAP\_DELIMITER\_req. It then enters 'Receive\_Open\_Cnf'. From 'Receive\_Open\_Cnf', an 'OK' path leads to 'Wait\_For\_Response\_From\_HLR', while a 'Vr, Error' path leads to 'Set Negative response: System failure'. From 'Wait\_For\_Response\_From\_HLR', three paths emerge: 'MAP\_P\_ABORT\_ind' leading to 'MAP CLOSE\_req', 'MAP NOTICE\_ind' leading to 'MAP CLOSE\_req', and 'MAP\_ERASE\_CC\_ENTRY\_cnf' leading to 'Check Confirmation'. From 'Check Confirmation', three paths emerge: 'Provider Error, Data Error' leading to 'Set Negative response: System failure', 'User Error' leading to 'Set Negative response', and 'OK' leading to 'Deactivate CCBS ack'. All three paths from 'Check Confirmation' lead to 'Null' nodes. Both 'MAP CLOSE\_req' and 'Set Negative response: System failure' lead to 'Deactivate CCBS negative response', which then leads to 'Null'. + +3509 + +3510 + +**Figure 22.14.2/1: Process Erase\_CC\_Entry\_VLR** + +![Flowchart for process Erase_CC_Entry_HLR. It starts with an oval, followed by a 'Null' block, then an input block for 'MAP_ERASE_CC_ENTRY_ind'. This is followed by a 'Deactivate CCBS' block and a 'Wait For Application_Response' block. A decision point follows, leading to four paths: 1) 'MAP_NOTICE_ind' -> 'MAP_CLOSE_req' -> 'Abort' -> end; 2) an unlabeled input block -> a block with 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' -> 'Abort' -> end; 3) 'Deactivate CCBS negative response' -> 'Ser User Error' -> an unlabeled output block -> a block with 'MAP_ERASE_CC_ENTRY_rsp, MAP_CLOSE_req' -> end; 4) 'Deactivate CCBS ack' -> 'Set Result' -> the same unlabeled output block -> end.](4b29d7112312e8a8a704a0f9a9db35b2_img.jpg) + +**process Erase\_CC\_Entry\_HLR** **ECCE\_HLR1(1)** + +Process in the HLR to handle a request to erase a Call Completion entry + +Signals to/from the left are to/from the VLR; + signals to/from the right are to/from the CCBS application process in the HLR (see 3GPP TS 23.093) + +``` + + graph TD + Start([ ]) --> Null[Null] + Null --> Input1{{ }} + Input1 --- MAP_ERASE_CC_ENTRY_ind[MAP_ERASE_CC_ENTRY_ind] + Input1 --> DeactivateCCBS[Deactivate CCBS] + DeactivateCCBS --> WaitForResponse[Wait For Application_Response] + WaitForResponse --> Decision(( )) + + Decision --> Input2{{ }} + Input2 --- MAP_NOTICE_ind[MAP_NOTICE_ind] + Input2 --> MAP_CLOSE_req[MAP_CLOSE_req] + + Decision --> Input3{{ }} + Input3 --- MAP_P_ABORT_ind[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] + + Decision --> Input4{{ }} + Input4 --- DeactivateCCBS_neg[Deactivate CCBS negative response] + + Decision --> Input5{{ }} + Input5 --- DeactivateCCBS_ack[Deactivate CCBS ack] + + MAP_CLOSE_req --> Abort[Abort] + MAP_P_ABORT_ind --> Abort + Abort --> End1((X)) + + DeactivateCCBS_neg --> SerUserError[Ser User Error] + DeactivateCCBS_ack --> SetResult[Set Result] + + SerUserError --> Output1{{ }} + SetResult --> Output1 + + Output1 --- MAP_ERASE_CC_ENTRY_rsp[MAP_ERASE_CC_ENTRY_rsp, MAP_CLOSE_req] + Output1 --> End2((X)) + +``` + +Flowchart for process Erase\_CC\_Entry\_HLR. It starts with an oval, followed by a 'Null' block, then an input block for 'MAP\_ERASE\_CC\_ENTRY\_ind'. This is followed by a 'Deactivate CCBS' block and a 'Wait For Application\_Response' block. A decision point follows, leading to four paths: 1) 'MAP\_NOTICE\_ind' -> 'MAP\_CLOSE\_req' -> 'Abort' -> end; 2) an unlabeled input block -> a block with 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' -> 'Abort' -> end; 3) 'Deactivate CCBS negative response' -> 'Ser User Error' -> an unlabeled output block -> a block with 'MAP\_ERASE\_CC\_ENTRY\_rsp, MAP\_CLOSE\_req' -> end; 4) 'Deactivate CCBS ack' -> 'Set Result' -> the same unlabeled output block -> end. + +3511 + +3512 + +Figure 22.14.3/1: Process Erase\_CC\_Entry\_HLR + +--- + +## 3513 23 Short message service procedures + +### 3514 23.1 General + +3515 The short message service procedures are used to control both mobile originated and mobile terminated short message +3516 transfer. + +3517 Four procedures exist for short message services: + +- 3518 - mobile originated short message service transfer; +- 3519 - mobile terminated short message service transfer; +- 3520 - short message alert procedure; +- 3521 - short message delivery status report procedure. + +3522 The following application context refers to a complex MAP user consisting of several processes: + +- 3523 - shortMessageGatewayContext. + +3524 This application context needs a co-ordinating process in the HLR. Additionally a co-ordinating process needed for the +3525 mobile originated situation in the MSC, because the A\_CM\_SERV\_REQ message does not distinguish between mobile +3526 originated short message transfer and the short message alert procedures. + +3527 NOTE: the A\_CM\_SERV\_REQ message is not used for SMS over GPRS. The modelling is based on the +3528 assumption that the SGSN will trigger the appropriate process, according to whether an RP\_MO\_DATA +3529 or an RP\_SM\_MEMORY\_AVAILABLE is received over the LLC layer. + +3530 When the "SMS in MME" architecture option is supported, the clause 23 and its associated figures applies where HSS +3531 replaces HLR and where MME is handled as a MSC, except the procedures between the serving MSC and the VLR +3532 which, here, are not applicable to the MME. + +3533 NOTE: MSC and MME cannot be both registered as serving nodes for MT SMS at a given time (cf 3GPP TS +3534 23.272 [2]) + +### 3535 23.1.1 Mobile originated short message service Co-ordinator for the MSC + +3536 The process starts when the MSC receives an A\_CM\_SERV\_REQ message (see 3GPP TS 24.008 [35]), with a CM +3537 service type indicating short message service, from the A-interface. The process invokes a macro not defined in this +3538 clause; the definition of this macro can be found as follows: + +3539 Process\_Access\_Request\_MSC see clause 25.4.1. + +3540 If the macro Process\_Access\_Request\_MSC takes the "OK" exit (which means that the MSC has sent an +3541 A\_CM\_SERVICE\_ACCEPT to the MS), , the MS initiates mobile originated short message transfer or sends an +3542 indication that it has memory available for more short messages. + +3543 The SMS Co-ordinator process in the MSC is shown in figure 23.1/1. + +### 3544 23.1.2 Short message Gateway Co-ordinator for the HLR + +3545 The process starts when the HLR receives a MAP\_OPEN indication using when the application context +3546 shortMessageGatewayContext. The MAP process invokes a macro not defined in this clause; the definition of this +3547 macro can be found as follows: + +3548 Receive\_Open\_Ind see clause 25.1.1. + +3549 The SM Gateway Co-ordinator process in the HLR is shown in figure 23.1/2. + +3550 If the Receive\_Open\_Ind macro takes the Vr exit then HLR shall perform the MAP dialogue as specified for the +3551 appropriate application context version. Depending on the subscriber data, handling at the MAP user application level +3552 may be performed as specified in clauses 23.3.2 and 23.5.2 of the present document: + +![State transition diagram for process Co_SMS_MSC. The diagram starts with an initial state leading to 'Null', then 'A CM_SERVICE_REQUEST', then 'Process_Access_Request_MSC'. From there, an 'Error' leads to 'Null' and an 'OK' leads to 'Wait_For_Service_Primitive'. A horizontal line connects 'Wait_For_Service_Primitive' to four parallel paths. Path 1: 'A_MM_RELEASE_ind' -> 'MAP_U_ABORT_req' -> 'Null'. Path 2: 'A_RP_MO_DATA' -> 'MO_SM_MSC' -> 'A_RP_MO_DATA' (To offspring) -> 'Relay_Info'. Path 3: 'A_RP_SM_MEMORY_AVAILABLE' -> 'SM_Alert_MSC' -> 'A_RP_SM_MEMORY_AVAILABLE' (To offspring) -> 'Relay_Info'. Path 4: an unlabeled state -> 'MAP_U_ABORT_ind, MAP_CLOSE_ind' -> 'Null'.](cc3fc3e0d3d8b84502df9fb9c840d365_img.jpg) + +process Co\_SMS\_MSC Co\_SMS\_MSC1(2) + +Co-ordinating process in the MSC for mobile originated SMS activity + +Signals to/from the left are to/from the MS; + signals to/from the right are to/from the VLR unless marked otherwise + +``` + +stateDiagram-v2 + [*] --> Null1[Null] + Null1 --> A_CM_SERVICE_REQUEST{A CM_SERVICE_REQUEST} + A_CM_SERVICE_REQUEST --> Process_Access_Request_MSC[Process_Access_Request_MSC] + Process_Access_Request_MSC --> Null2[Null] : Error + Process_Access_Request_MSC --> Wait_For_Service_Primitive{Wait_For_Service_Primitive} : OK + state " " as UnlabeledState + Wait_For_Service_Primitive --> A_MM_RELEASE_ind{A_MM_RELEASE_ind} + Wait_For_Service_Primitive --> A_RP_MO_DATA1{A_RP_MO_DATA} + Wait_For_Service_Primitive --> A_RP_SM_MEMORY_AVAILABLE1{A_RP_SM_MEMORY_AVAILABLE} + Wait_For_Service_Primitive --> UnlabeledState + A_MM_RELEASE_ind --> MAP_U_ABORT_req{{MAP_U_ABORT_req}} + MAP_U_ABORT_req --> Null3[Null] + A_RP_MO_DATA1 --> MO_SM_MSC[MO_SM_MSC] + MO_SM_MSC --> A_RP_MO_DATA2{A_RP_MO_DATA} + A_RP_MO_DATA2 --> To_offspring1[To offspring] + To_offspring1 --> Relay_Info[Relay_Info] + A_RP_SM_MEMORY_AVAILABLE1 --> SM_Alert_MSC[SM_Alert_MSC] + SM_Alert_MSC --> A_RP_SM_MEMORY_AVAILABLE2{A_RP_SM_MEMORY_AVAILABLE} + A_RP_SM_MEMORY_AVAILABLE2 --> To_offspring2[To offspring] + To_offspring2 --> Relay_Info + UnlabeledState --> MAP_U_ABORT_ind_MAP_CLOSE_ind{{MAP_U_ABORT_ind, MAP_CLOSE_ind}} + MAP_U_ABORT_ind_MAP_CLOSE_ind --> Null4[Null] + +``` + +State transition diagram for process Co\_SMS\_MSC. The diagram starts with an initial state leading to 'Null', then 'A CM\_SERVICE\_REQUEST', then 'Process\_Access\_Request\_MSC'. From there, an 'Error' leads to 'Null' and an 'OK' leads to 'Wait\_For\_Service\_Primitive'. A horizontal line connects 'Wait\_For\_Service\_Primitive' to four parallel paths. Path 1: 'A\_MM\_RELEASE\_ind' -> 'MAP\_U\_ABORT\_req' -> 'Null'. Path 2: 'A\_RP\_MO\_DATA' -> 'MO\_SM\_MSC' -> 'A\_RP\_MO\_DATA' (To offspring) -> 'Relay\_Info'. Path 3: 'A\_RP\_SM\_MEMORY\_AVAILABLE' -> 'SM\_Alert\_MSC' -> 'A\_RP\_SM\_MEMORY\_AVAILABLE' (To offspring) -> 'Relay\_Info'. Path 4: an unlabeled state -> 'MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' -> 'Null'. + +3553 + +3554 + +Figure 23.1/1 (sheet 1 of 2): Process Co\_SMS\_MSC + +![Sequence diagram for process Co_SMS_MSC. The diagram is split into two subtrees. The upper subtree shows three signal paths starting from a Relay_Info lifeline: 1) A_MM_RELEASE_ind leads to a Null state; 2) A_DISC_ind leads to a Null state; 3) A_* leads to another Relay_Info lifeline. The lower subtree shows four signal paths starting from a Relay_Info lifeline: 1) A signal with MAP_U_ABORT_ind, MAP_CLOSE_ind leads to a Null state; 2) A_* signal leads to a Relay_Info lifeline; 3) A signal with MAP_U_ABORT_ind, MAP_CLOSE_ind leads to a Null state; 4) A '-' signal leads to a Relay_Info lifeline.](c2d91061c4a09b286eb6aaf27bd84a5f_img.jpg) + +**process Co\_SMS\_MSC** **Co\_SMS\_MSC2(2)** + +Co-ordinating process in the MSC for mobile originated SMS activity + +In the upper subtree, signals to/from the left are to/from the MS; signals to/from the right are to/from the child process + +In the lower subtree, signals to/from the left are to/from the VLR; signals to/from the right are to/from the child process + +Sequence diagram for process Co\_SMS\_MSC. The diagram is split into two subtrees. The upper subtree shows three signal paths starting from a Relay\_Info lifeline: 1) A\_MM\_RELEASE\_ind leads to a Null state; 2) A\_DISC\_ind leads to a Null state; 3) A\_\* leads to another Relay\_Info lifeline. The lower subtree shows four signal paths starting from a Relay\_Info lifeline: 1) A signal with MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind leads to a Null state; 2) A\_\* signal leads to a Relay\_Info lifeline; 3) A signal with MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind leads to a Null state; 4) A '-' signal leads to a Relay\_Info lifeline. + +3555 + +3556 + +**Figure 23.1/1 (sheet 2 of 2): Process Co\_SMS\_MSC** + +![Flowchart for process Co_SM_GW_HLR. It starts with an initial node leading to 'Null', then 'Receive_Open_ind' (linked to Figure 25.1/1). From 'Receive_Open_ind', three paths emerge: 'Error' leading to 'Null', 'OK' leading to 'Wait_For_Service_Primitive', and 'Vr' leading to 'Perform Vr dialogue' then 'Null'. 'Wait_For_Service_Primitive' branches into five parallel paths: 1) 'MAP_SEND_ROUTING_INFO_FOR_SM_ind' -> 'MTSM_HLR' -> 'MAP_SEND_ROUTING_INFO_FOR_SM_ind' -> 'Relay_Info'; 2) 'Report_SM_Delivery_Status_HLR' -> 'MAP_REPORT_SM_DELIVERY_STATUS_ind' -> 'Relay_Info'; 3) 'MAP_REPORT_SM_DELIVERY_STATUS_ind' -> 'Relay_Info'; 4) 'MAP_NOTICE_ind' -> 'MAP_CLOSE_req' -> 'Null'; 5) 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' -> 'Relay_Info'. All five 'Relay_Info' nodes converge to a final horizontal bus. From this bus, four paths emerge: 1) 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' -> 'Null'; 2) '*' -> 'Relay_Info'; 3) 'MAP_U_ABORT_ind, MAP_CLOSE_ind' -> 'Null'; 4) '*' -> 'Relay_Info'.](f6d30d19c55b4183969d1e72c52578f3_img.jpg) + +**process Co\_SM\_GW\_HLR** **Co\_SM\_GW\_HLR1(1)** + +Co-ordinating process in the HLR for SMS activity using the shortMsgGatewayContext + +Signals to/from the left are to/from the SMS-GMSC, signals to/from the right are to/from the child process + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive[Receive_Open_ind] + Receive -.-> Fig25_1_1[Figure 25.1/1] + Receive -- Error --> Null2([Null]) + Receive -- OK --> Wait[Wait_For_Service_Primitive] + Receive -- Vr --> VrDialog[Perform Vr dialogue] + VrDialog --> Null3([Null]) + Wait --> Split1(( )) + Split1 --> Path1_1[MAP_SEND_ROUTING_INFO_FOR_SM_ind] + Path1_1 --> Path1_2[MTSM_HLR] + Path1_2 --> Path1_3[MAP_SEND_ROUTING_INFO_FOR_SM_ind] + Path1_3 --> Path1_4[Relay_Info] + Split1 --> Path2_1[Report_SM_Delivery_Status_HLR] + Path2_1 --> Path2_2[MAP_REPORT_SM_DELIVERY_STATUS_ind] + Path2_2 --> Path2_3[Relay_Info] + Split1 --> Path3_1[MAP_REPORT_SM_DELIVERY_STATUS_ind] + Path3_1 --> Path3_2[Relay_Info] + Split1 --> Path4_1[MAP_NOTICE_ind] + Path4_1 --> Path4_2[MAP_CLOSE_req] + Path4_2 --> Path4_3[Null] + Split1 --> Path5_1[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Path5_1 --> Path5_2[Relay_Info] + Path1_4 --> Split2(( )) + Path2_3 --> Split2 + Path3_2 --> Split2 + Path4_3 --> Split2 + Path5_2 --> Split2 + Split2 --> Path6_1[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Path6_1 --> Path6_2[Null] + Split2 --> Path7_1[*] + Path7_1 --> Path7_2[Relay_Info] + Split2 --> Path8_1[MAP_U_ABORT_ind, MAP_CLOSE_ind] + Path8_1 --> Path8_2[Null] + Split2 --> Path9_1[*] + Path9_1 --> Path9_2[Relay_Info] + +``` + +Flowchart for process Co\_SM\_GW\_HLR. It starts with an initial node leading to 'Null', then 'Receive\_Open\_ind' (linked to Figure 25.1/1). From 'Receive\_Open\_ind', three paths emerge: 'Error' leading to 'Null', 'OK' leading to 'Wait\_For\_Service\_Primitive', and 'Vr' leading to 'Perform Vr dialogue' then 'Null'. 'Wait\_For\_Service\_Primitive' branches into five parallel paths: 1) 'MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_ind' -> 'MTSM\_HLR' -> 'MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_ind' -> 'Relay\_Info'; 2) 'Report\_SM\_Delivery\_Status\_HLR' -> 'MAP\_REPORT\_SM\_DELIVERY\_STATUS\_ind' -> 'Relay\_Info'; 3) 'MAP\_REPORT\_SM\_DELIVERY\_STATUS\_ind' -> 'Relay\_Info'; 4) 'MAP\_NOTICE\_ind' -> 'MAP\_CLOSE\_req' -> 'Null'; 5) 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' -> 'Relay\_Info'. All five 'Relay\_Info' nodes converge to a final horizontal bus. From this bus, four paths emerge: 1) 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' -> 'Null'; 2) '\*' -> 'Relay\_Info'; 3) 'MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' -> 'Null'; 4) '\*' -> 'Relay\_Info'. + +3557 + +3558 + +**Figure 23.1/2: Process Co\_SM\_Gateway\_HLR** + +3559 **23.2 The mobile originated short message transfer procedure** + +3560 The mobile originated short message service procedure is used to forward a short message from a mobile subscriber to a + 3561 Service Centre. The message flow for the mobile originated short message service procedure is shown in figure 23.2/1. + +![Sequence diagram showing the mobile originated short message transfer procedure between MS, Serving MSC or SGSN, VLR, Interworking MSC, and SC. The sequence of messages is: 1) Short Message from MS to Serving MSC or SGSN; 2) MAP_SEND_INFO_FOR_MO_SMS from Serving MSC or SGSN to VLR; 3) MAP_SEND_INFO_FOR_MO_SMS_ACK from VLR to Serving MSC or SGSN; 4) TCAP BEGIN from Serving MSC or SGSN to Interworking MSC; 4a) TCAP CONTINUE from Interworking MSC to Serving MSC or SGSN; 4b) MAP_MO_FORWARD_SHORT_MESSAGE from Interworking MSC to Serving MSC or SGSN; 5) Short message from Interworking MSC to SC; 6) Short message Acknowledgement from SC to Interworking MSC; 7) MAP_MO_FORWARD_SHORT_MESSAGE_ACK from Interworking MSC to Serving MSC or SGSN; 8) Short Message Acknowledgement from Serving MSC or SGSN to MS.](2579889c2739c3e124f5ff8f1053054d_img.jpg) + +Sequence diagram showing the mobile originated short message transfer procedure between MS, Serving MSC or SGSN, VLR, Interworking MSC, and SC. The sequence of messages is: 1) Short Message from MS to Serving MSC or SGSN; 2) MAP\_SEND\_INFO\_FOR\_MO\_SMS from Serving MSC or SGSN to VLR; 3) MAP\_SEND\_INFO\_FOR\_MO\_SMS\_ACK from VLR to Serving MSC or SGSN; 4) TCAP BEGIN from Serving MSC or SGSN to Interworking MSC; 4a) TCAP CONTINUE from Interworking MSC to Serving MSC or SGSN; 4b) MAP\_MO\_FORWARD\_SHORT\_MESSAGE from Interworking MSC to Serving MSC or SGSN; 5) Short message from Interworking MSC to SC; 6) Short message Acknowledgement from SC to Interworking MSC; 7) MAP\_MO\_FORWARD\_SHORT\_MESSAGE\_ACK from Interworking MSC to Serving MSC or SGSN; 8) Short Message Acknowledgement from Serving MSC or SGSN to MS. + +3562 + +- 3563 +- 3564 1) Short Message (3GPP TS 24.011 [37]). +- 3565 2) MAP\_SEND\_INFO\_FOR\_MO\_SMS (\*). +- 3566 3) MAP\_SEND\_INFO\_FOR\_MO\_SMS\_ACK (\*). +- 3567 4) TCAP BEGIN (\*\*) +- 3568 4a) TCAP CONTINUE (\*\*) +- 3569 4b) MAP\_MO\_FORWARD\_SHORT\_MESSAGE. +- 3570 5) Short message (3GPP TS 23.040). +- 3571 6) Short message Acknowledgement (3GPP TS 23.040). +- 3572 7) MAP\_MO\_FORWARD\_SHORT\_MESSAGE\_ACK. +- 3573 8) Short Message Acknowledgement (3GPP TS 24.011 [37]). +- 3574 (\*) Messages 2) and 3) are not used by the SGSN. +- 3575 (\*\*) If +- 3576 a) +- 3577 the capacity of a message signal unit in the lower layers of the protocol is enough to carry the content of +- 3578 the MAP\_OPEN request and the content of the MAP\_MO\_FORWARD\_SHORT\_MESSAGE request in a +- 3579 single TC message +- 3580 +- 3581 and +- 3582 b) the Interworking MSC operator and the serving node (MSC or SGSN) operator agreed not to use the +- 3583 TCAP handshake countermeasure against SMS fraud for messages exchanged between their networks +- 3584 (see 3GPP TS 33.204 [34a]) +- 3585 +- 3586 then +- 3587 the TCAP handshake may be omitted. + +3588 **Figure 23.2/1: Mobile originated short message transfer** + +3590 In addition the following MAP services are used: + +- 3591 MAP\_PROCESS\_ACCESS\_REQUEST (see clause 8.3); (\*) +- 3592 MAP\_AUTHENTICATE (see clause 8.5); (\*) +- 3593 MAP\_SET\_CIPHERING\_MODE (see clause 8.6); (\*) +- 3594 MAP\_PROVIDE\_IMSI (see clause 8.9); (\*) + +3595 MAP\_CHECK\_IMEI (see clause 8.7); + 3596 MAP\_FORWARD\_NEW\_TMSI (see clause 8.9); (\*) + 3597 MAP\_TRACE\_SUBSCRIBER\_ACTIVITY (see clause 9.1); (\*) + 3598 MAP\_READY\_FOR\_SM (see clause 12.4). + 3599 (\*) These services are not used by the SGSN. + +## 3600 23.2.1 Procedure in the serving MSC + +3601 Any CAMEL-specific handling defined in this clause is omitted if the MSC does not support CAMEL control of MO + 3602 SMS, or if the subscriber does not have a subscription for CAMEL control of MO SMS. + +3603 The process starts when the MSC receives a short message from the MS. The process invokes macros not defined in this + 3604 clause; the definitions of these macros can be found as follows: + +3605 Receive\_Open\_Cnf see clause 25.1.2; + +3606 Check\_Indication see clause 25.2.1; + +3607 Check\_Confirmation see clause 25.2.2. + +3608 Sheet 1: If the MSC is integrated with the SMS-IWMSC, it communicates directly with the Short Message Service + 3609 Centre (SMSC) using one of the protocols described in 3GPP TS 23.039 [25a]; otherwise it communicates with the + 3610 SMS-IWMSC using MAP. + +3611 Sheet 3: If the capacity of a message signal unit in the lower layers of the protocol is enough to carry the content of the + 3612 MAP\_OPEN request and the content of the MAP\_MO\_FORWARD\_SHORT\_MESSAGE request in a single TC + 3613 message, the test "Message segmentation needed" takes the "No" exit; otherwise the test takes the "Yes" exit. + +3614 Sheet 3: The decision box "TCAP Handshake required" takes the "yes" or "no" exit depending on agreements between + 3615 the serving MSC's operator and the SMS-IWMSC's operator (see 3GPP TS 33.204 [34a]). + +3616 The mobile originated short message service process in the MSC is shown in figure 23.2/2. + +## 3617 23.2.2 Procedure in the VLR + +3618 Any CAMEL-specific handling defined in this clause is omitted if the VLR does not support CAMEL control of MO + 3619 SMS. + +3620 The process starts when the VLR receives a dialogue opening request followed by a + 3621 MAP\_PROCESS\_ACCESS\_REQUEST including a CM service type Short Message Service. The process invokes + 3622 macros not defined in this clause; the definitions of these macros can be found as follows: + +3623 Receive\_Open\_Ind see clause 25.1.1; + +3624 Check\_Indication see clause 25.2.1; + +3625 Process\_Access\_Request\_VLR see clause 25.4.2. + +3626 The mobile originated short message transfer process in the VLR is shown in figure 23.2/3. + +## 3627 23.2.3 Procedure in the SGSN + +3628 Any CAMEL-specific handling defined in this clause is omitted if the SGSN does not support CAMEL control of MO + 3629 SMS, or if the subscriber does not have a subscription for CAMEL control of MO SMS. + +3630 The process starts when the SGSN receives a short message received from the MS over the Gb interface. The MAP + 3631 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +3632 Receive\_Open\_Cnf see clause 25.1.2; + +3633 Check\_Confirmation see clause 25.2.2. + +3634 Sheet 2: If the capacity of a message signal unit in the lower layers of the protocol is enough to carry the content of the +3635 MAP\_OPEN request and the content of the MAP\_MO\_FORWARD\_SHORT\_MESSAGE request in a single TC +3636 message, the test "Message segmentation needed" takes the "No" exit; otherwise the test takes the "Yes" exit. + +3637 Sheet 2: The decision box "TCAP Handshake required" takes the "yes" or "no" exit depending on agreements between +3638 the serving SGSN's operator and the SMS-IWMSC's operator (see 3GPP TS 33.204 [34a]). + +3639 The mobile originated short message service process in the SGSN is shown in figure 23.2/4. + +## 3640 23.2.4 Procedure in the SMS Interworking MSC (SMS-IWMSC) + +3641 This procedure applies only when the SMS-IWMSC is not integrated with the serving MSC or SGSN. + +3642 The process starts when the SMS-IWMSC receives a dialogue opening request with the application context +3643 shortMsgMO-RelayContext. The MAP process invokes macros not defined in this clause; the definitions of these +3644 macros can be found as follows: + +3645 Receive\_Open\_Ind see clause 25.1.1; + +3646 Check\_Indication see clause 25.2.1. + +3647 Sheet 1: The decision box "TCAP Handshake required" takes the "yes" or "no" exit depending on agreements between +3648 the SMS-IWMSC's operator and the serving node's operator (see 3GPP TS 33.204 [34a]). + +3649 The mobile originated short message service transfer process in the SMS-IWMSC is shown in figure 23.2/5. + +![Flowchart for process MO_SM_MSC. The process starts with an initial state, followed by 'Null', then 'A_RP_MO_DATA_ind'. It then sends 'MAP_SEND_INFO_FOR_MO_SMS_req' and 'MAP_DELIMITER_req', and waits for a 'VLR_Response'. A decision point follows: if 'MAP_U_ABORT_ind' or 'MAP_CLOSE_ind' is received, it sends 'CAMEL_O_SMS_FAILURE' (referencing 3GPP TS 23.078), sets 'RP_ERROR: Network out of order', and sends 'A_RP_ERROR_req' (terminated). If 'MAP_SEND_INFO_FOR_MO_SMS_cnf' is received, it checks the confirmation. If 'OK', it checks if 'MSC=IWMSC?'. If 'Yes', it sends 'SC_RP_MO_DATA_req' to the SMSC and waits for confirmation. If 'No', it goes to connector '1'. If 'User Error' or 'Data Error', it sends 'CAMEL_O_SMS_FAILURE' (referencing 3GPP TS 23.078), sets 'RP_ERROR' or 'Network out of order', sends 'A_RP_ERROR_req' (terminated), or goes to connector '1'.](a3a4a1bab05ca97f74c3e8462ac962be_img.jpg) + +**process MO\_SM\_MSC** **MO\_SM\_MSC1(4)** + +Process in the MSC to handle MO short message submission + +Signals to/from the left are to/from the MS; + signals to/from the right are to/from the VLR + unless marked otherwise + +``` + + graph TD + Start([ ]) --> Null[Null] + Null --> In1{{ }} + In1 --> A_RP_MO_DATA_ind[A_RP_MO_DATA_ind] + A_RP_MO_DATA_ind --> In2{{ }} + In2 --> Out1[MAP_SEND_INFO_FOR_MO_SMS_req +MAP_DELIMITER_req] + Out1 --> Wait_VLR[Wait_For_VLR_Response] + Wait_VLR --> Decision1{{ }} + Decision1 --> In3{{ }} + In3 --> Out2[MAP_U_ABORT_ind, +MAP_CLOSE_ind] + In3 --> In4{{ }} + In4 --> Out3[MAP_SEND_INFO_FOR_MO_SMS_cnf] + Out3 --> Check[Check_Confirmation] + Check --> Decision2{MSC=IWMSC?} + Decision2 -- Yes --> Out4[SC_RP_MO_DATA_req] + Out4 --> To_SMSC[To SMSC] + To_SMSC --> Wait_Confirm[Wait_For_Confirm_From_SC] + Decision2 -- No --> Connector1((1)) + Check -- User Error --> Failure1[CAMEL_O_SMS_FAILURE] + Failure1 --> Ref1[See 3GPP TS 23.078] + Failure1 --> Set_Error1[Set RP_ERROR] + Set_Error1 --> Connector1 + Check -- Data Error --> Failure2[CAMEL_O_SMS_FAILURE] + Failure2 --> Ref2[See 3GPP TS 23.078] + Failure2 --> Set_Error2[Set RP_ERROR: +Network out of order] + Set_Error2 --> A_RP_ERROR_req2[A_RP_ERROR_req] + A_RP_ERROR_req2 --> End2[ ] + Decision2 -- OK --> Failure3[CAMEL_O_SMS_FAILURE] + Failure3 --> Ref3[See 3GPP TS 23.078] + Failure3 --> Set_Error3[Set RP_ERROR: +Network out of order] + Set_Error3 --> A_RP_ERROR_req3[A_RP_ERROR_req] + A_RP_ERROR_req3 --> End3[ ] + +``` + +Flowchart for process MO\_SM\_MSC. The process starts with an initial state, followed by 'Null', then 'A\_RP\_MO\_DATA\_ind'. It then sends 'MAP\_SEND\_INFO\_FOR\_MO\_SMS\_req' and 'MAP\_DELIMITER\_req', and waits for a 'VLR\_Response'. A decision point follows: if 'MAP\_U\_ABORT\_ind' or 'MAP\_CLOSE\_ind' is received, it sends 'CAMEL\_O\_SMS\_FAILURE' (referencing 3GPP TS 23.078), sets 'RP\_ERROR: Network out of order', and sends 'A\_RP\_ERROR\_req' (terminated). If 'MAP\_SEND\_INFO\_FOR\_MO\_SMS\_cnf' is received, it checks the confirmation. If 'OK', it checks if 'MSC=IWMSC?'. If 'Yes', it sends 'SC\_RP\_MO\_DATA\_req' to the SMSC and waits for confirmation. If 'No', it goes to connector '1'. If 'User Error' or 'Data Error', it sends 'CAMEL\_O\_SMS\_FAILURE' (referencing 3GPP TS 23.078), sets 'RP\_ERROR' or 'Network out of order', sends 'A\_RP\_ERROR\_req' (terminated), or goes to connector '1'. + +3650 + +3651 + +Figure 23.2/2 (sheet 1 of 4): Process MO\_SM\_MSC + +![Sequence diagram for process MO_SM_MSC. It starts with Wait_For_VLR_Response, followed by a merge point for MAP_CONTINUE_CAMEL_SMS_HANDLING_ind. Then Check_Indication, CAMEL_O_SMS_INIT (referencing 3GPP TS 23.078), and a Result? decision. The Continue path leads to MAP_SEND_INFO_FOR_MO_SMS_req and back to Wait_For_VLR_Response. The Release_SMS path leads to Set RP_ERROR, A_RP_ERROR_req, and MAP_U_ABORT_req. The Redirect_SMS path leads to Modify data and then to the merge point before MAP_SEND_INFO_FOR_MO_SMS_req. The Error path leads to Set RP_ERROR: Network out of order, A_RP_ERROR_req, and MAP_U_ABORT_req. The SMS_Aborted path leads directly to MAP_U_ABORT_req.](90163785f797d2f1152f74c311e6cae9_img.jpg) + +**process MO\_SM\_MSC** **MO\_SM\_MSC2(4)** + +Process in the MSC to handle MO short message submission + +Signals to/from the left are to/from the MS; + Signals to/from the right are to/from the VLR + +``` + +sequenceDiagram + participant MS + participant VLR + participant MSC + Note left of MSC: Process in the MSC to handle MO short message submission + Note right of MSC: Signals to/from the left are to/from the MS; Signals to/from the right are to/from the VLR + + MSC->>MSC: Wait_For_VLR_Response + Note right of MSC: MAP_CONTINUE_CAMEL_SMS_HANDLING_ind + MSC->>MSC: Check_Indication + Note right of MSC: OK + Note right of MSC: Error + MSC->>MSC: CAMEL_O_SMS_INIT + Note right of MSC: See 3GPP TS 23.078 + MSC->>MSC: Result? + Note right of MSC: Continue + Note right of MSC: Release_SMS + Note right of MSC: Redirect_SMS + Note right of MSC: SMS_Aborted + + alt Continue + MSC->>MSC: MAP_SEND_INFO_FOR_MO_SMS_req + Note right of MSC: MAP_DELIMITER_req + MSC->>MSC: Wait_For_VLR_Response + else Release_SMS + MSC->>MSC: Set RP_ERROR according to gsmSCF instructions + MSC->>MSC: A_RP_ERROR_req + MSC->>MSC: MAP_U_ABORT_req + Note right of MSC: X + else Redirect_SMS + MSC->>MSC: Modify data according to gsmSCF instructions + Note right of MSC: Merge point before MAP_SEND_INFO_FOR_MO_SMS_req + else Error + MSC->>MSC: Set RP_ERROR: Network out of order + MSC->>MSC: A_RP_ERROR_req + MSC->>MSC: MAP_U_ABORT_req + Note right of MSC: X + else SMS_Aborted + MSC->>MSC: MAP_U_ABORT_req + Note right of MSC: X + end + +``` + +Sequence diagram for process MO\_SM\_MSC. It starts with Wait\_For\_VLR\_Response, followed by a merge point for MAP\_CONTINUE\_CAMEL\_SMS\_HANDLING\_ind. Then Check\_Indication, CAMEL\_O\_SMS\_INIT (referencing 3GPP TS 23.078), and a Result? decision. The Continue path leads to MAP\_SEND\_INFO\_FOR\_MO\_SMS\_req and back to Wait\_For\_VLR\_Response. The Release\_SMS path leads to Set RP\_ERROR, A\_RP\_ERROR\_req, and MAP\_U\_ABORT\_req. The Redirect\_SMS path leads to Modify data and then to the merge point before MAP\_SEND\_INFO\_FOR\_MO\_SMS\_req. The Error path leads to Set RP\_ERROR: Network out of order, A\_RP\_ERROR\_req, and MAP\_U\_ABORT\_req. The SMS\_Aborted path leads directly to MAP\_U\_ABORT\_req. + +3652 + +3653 + +Figure 23.2/2 (sheet 2 of 4): Process MO\_SM\_MSC + +![SDL Flowchart for MO_SM_MSC process showing message segmentation logic, TCAP handshake requirements, and CAMEL interaction for short message submission.](c321eed701b327255a025f66b51b8535_img.jpg) + +process MO\_SM\_MSC +MO\_SM\_MSC3(4) + +Process in the MSC to handle MO short message submission + +Signals to/from the left are to/from the MS; + Signals to/from the right are to/from the IWMSC + +``` + + graph TD + Start((1)) --> SegNeeded{Message +segmentation +needed?} + + SegNeeded -- No --> TCAPReq{TCAP +Handshake +required} + SegNeeded -- Yes --> MAPOpenReqR[MAP_OPEN_req +MAP_DELIMITER_req] + + TCAPReq -- no --> RecOpenCnfL[Receive_ +Open_Cnf] + TCAPReq -- yes --> MAPOpenReqL[MAP_OPEN_req +MAP_MO_FORWARD_SHORT_MESSAGE_req +MAP_DELIMITER_req] + + MAPOpenReqR --> RecOpenCnfR[Receive_ +Open_Cnf] + + RecOpenCnfL -- OK --> WaitResultL(Wait_For_ +MO_SMS_ +Result) + RecOpenCnfL -- Vr --> PerformVrL[Perform +MAP Vr +dialogue] + RecOpenCnfL -- Error --> CamelFailL[CAMEL_O_ +SMS_ +FAILURE] + + RecOpenCnfR -- OK --> WaitResultR(Wait_For_ +MO_SMS_ +Result) + RecOpenCnfR -- Vr --> PerformVrR[Perform +MAP Vr +dialogue] + + PerformVrL --> State2((2)) + + CamelFailL --> Note1[See 3GPP +TS 23.078] + CamelFailL --> SetErrorNet[Set RP_ERROR: +Network +out of order] + SetErrorNet --> ARPErrorReqL[A_RP_ +ERROR_req] + ARPErrorReqL --> End1((X)) + + PerformVrR --> SubSuccess{Submission +successful?} + + WaitResultL --> MAPMOFwdCnf[MAP_MO_FORWARD_SHORT_MESSAGE_cnf] + MAPMOFwdCnf --> CheckConf{Check_ +Confirmation} + + CheckConf -- OK --> CamelSubL[CAMEL_O_ +SMS_ +SUBMITTED] + CamelSubL --> Note2[See 3GPP +TS 23.078] + CamelSubL --> ARPACKReqL[A_RP_ +ACK_req] + ARPACKReqL --> End2((X)) + + CheckConf -- "Provider Error, +User Error, +Data Error" --> CamelFailMid[CAMEL_O_ +SMS_ +FAILURE] + CamelFailMid --> Note3[See 3GPP +TS 23.078] + CamelFailMid --> SetRPError[Set +RP_ERROR] + SetRPError --> ARPErrorReqMid[A_RP_ +ERROR_req] + ARPErrorReqMid --> End3((X)) + + SubSuccess -- No --> CamelFailMid + SubSuccess -- Yes --> CamelSubR[CAMEL_O_ +SMS_ +SUBMITTED] + CamelSubR --> Note4[See 3GPP +TS 23.078] + CamelSubR --> ARPACKReqR[A_RP_ +ACK_req] + ARPACKReqR --> End4((X)) + +``` + +SDL Flowchart for MO\_SM\_MSC process showing message segmentation logic, TCAP handshake requirements, and CAMEL interaction for short message submission. + +3654 + +3655 + +**Figure 23.2/2 (sheet 3 of 4): Process MO\_SM\_MSC** + +![State transition diagram for process MO_SM_MSC. The diagram shows two main vertical paths. The left path starts with SC_RP_ERROR_ind leading to CAMEL_O_SMS_FAILURE (referencing 3GPP TS 23.078), then Set RP_ERROR, and finally A_RP_ERROR_req. The middle path starts with Wait_For_Confirm_From_SC leading to SC_ABORT_ind, then CAMEL_O_SMS_FAILURE (referencing 3GPP TS 23.078), then Set RP_ERROR: Network out of order, then A_RP_ERROR_req. The right path starts with SC_RP_ACK_ind leading to CAMEL_O_SMS_SUBMITTED (referencing 3GPP TS 23.078), then A_RP_ACK_ind. Both A_RP_ERROR_req and A_RP_ACK_ind lead to a merge point. Below the merge point is Wait_For_MO_SMS_RESULT. From there, the left path leads to MAP_NOTICE_ind, then MAP_CLOSE_req, then CAMEL_O_SMS_FAILURE (referencing 3GPP TS 23.078), then Set RP_ERROR: Network out of order, then A_RP_ERROR_req. The right path from Wait_For_MO_SMS_RESULT leads to an unlabeled box, which then leads to MAP_U_ABORT_ind and MAP_P_ABORT_ind. Both A_RP_ERROR_req and the path from the unlabeled box lead to a final merge point.](a97065d6f7f90c18eb5af01c0afaec5b_img.jpg) + +**process MO\_SM\_MSC** **MO\_SM\_MSC4(4)** + +*Process in the MSC to handle MO short message submission* + +*In the upper subtree, signals to/from the left are to/from the MS; Signals to/from the right are to/from the SMSC* + +*In the lower subtree, signals to/from the left are to/from the MS; Signals to/from the right are to/from the IWMSC* + +``` + +stateDiagram-v2 + [*] --> Wait_For_Confirm_From_SC + state "SC_RP_ERROR_ind" as SC_RP_ERROR_ind + state "SC_ABORT_ind" as SC_ABORT_ind + state "SC_RP_ACK_ind" as SC_RP_ACK_ind + state "CAMEL_O_SMS_FAILURE" as CAMEL_O_SMS_FAILURE + state "CAMEL_O_SMS_SUBMITTED" as CAMEL_O_SMS_SUBMITTED + state "Set RP_ERROR" as Set RP_ERROR + state "Set RP_ERROR: Network out of order" as Set RP_ERROR: Network out of order + state "A_RP_ERROR_req" as A_RP_ERROR_req + state "A_RP_ACK_ind" as A_RP_ACK_ind + state "Wait_For_MO_SMS_RESULT" as Wait_For_MO_SMS_RESULT + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind" as MAP_U_ABORT_ind, MAP_P_ABORT_ind + state "Unlabeled Box" as + state [*] as [*] + + Wait_For_Confirm_From_SC --> SC_RP_ERROR_ind + Wait_For_Confirm_From_SC --> SC_ABORT_ind + Wait_For_Confirm_From_SC --> SC_RP_ACK_ind + + SC_RP_ERROR_ind --> CAMEL_O_SMS_FAILURE + CAMEL_O_SMS_FAILURE --> Set RP_ERROR + Set RP_ERROR --> A_RP_ERROR_req + + SC_ABORT_ind --> CAMEL_O_SMS_FAILURE + CAMEL_O_SMS_FAILURE --> Set RP_ERROR: Network out of order + Set RP_ERROR: Network out of order --> A_RP_ERROR_req + + SC_RP_ACK_ind --> CAMEL_O_SMS_SUBMITTED + CAMEL_O_SMS_SUBMITTED --> A_RP_ACK_ind + + A_RP_ERROR_req --> Merge1 + A_RP_ACK_ind --> Merge1 + Merge1 --> Wait_For_MO_SMS_RESULT + + Wait_For_MO_SMS_RESULT --> MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> CAMEL_O_SMS_FAILURE + CAMEL_O_SMS_FAILURE --> Set RP_ERROR: Network out of order + Set RP_ERROR: Network out of order --> A_RP_ERROR_req + + Wait_For_MO_SMS_RESULT --> Unlabeled Box + Unlabeled Box --> MAP_U_ABORT_ind, MAP_P_ABORT_ind + + A_RP_ERROR_req --> Merge2 + MAP_U_ABORT_ind, MAP_P_ABORT_ind --> Merge2 + Merge2 --> [*] + +``` + +State transition diagram for process MO\_SM\_MSC. The diagram shows two main vertical paths. The left path starts with SC\_RP\_ERROR\_ind leading to CAMEL\_O\_SMS\_FAILURE (referencing 3GPP TS 23.078), then Set RP\_ERROR, and finally A\_RP\_ERROR\_req. The middle path starts with Wait\_For\_Confirm\_From\_SC leading to SC\_ABORT\_ind, then CAMEL\_O\_SMS\_FAILURE (referencing 3GPP TS 23.078), then Set RP\_ERROR: Network out of order, then A\_RP\_ERROR\_req. The right path starts with SC\_RP\_ACK\_ind leading to CAMEL\_O\_SMS\_SUBMITTED (referencing 3GPP TS 23.078), then A\_RP\_ACK\_ind. Both A\_RP\_ERROR\_req and A\_RP\_ACK\_ind lead to a merge point. Below the merge point is Wait\_For\_MO\_SMS\_RESULT. From there, the left path leads to MAP\_NOTICE\_ind, then MAP\_CLOSE\_req, then CAMEL\_O\_SMS\_FAILURE (referencing 3GPP TS 23.078), then Set RP\_ERROR: Network out of order, then A\_RP\_ERROR\_req. The right path from Wait\_For\_MO\_SMS\_RESULT leads to an unlabeled box, which then leads to MAP\_U\_ABORT\_ind and MAP\_P\_ABORT\_ind. Both A\_RP\_ERROR\_req and the path from the unlabeled box lead to a final merge point. + +3656 + +3657 + +**Figure 23.2/2 (sheet 4 of 4): Process MO\_SM\_MSC** + +![State transition diagram for process MO_SM_VLR. The diagram shows a sequence of states and transitions. It starts with an initial state (oval), leading to a 'Null' state (oval). From 'Null', a transition 'Receive_Open_Ind' (rectangle) leads to 'Wait_For_Service_Primitive' (oval). From 'Wait_For_Service_Primitive', a transition 'Process_Access_Request_VLR' (rectangle) leads to another decision point. From this point, an 'OK' transition leads to 'Wait_For_Info_Request' (oval), and a 'Vr, Error' transition leads to another 'Null' state (oval).](d27fb5fe0f1e92b128d45dfbc529d9c7_img.jpg) + +process MO\_SM\_VLR + +MO\_SM\_VLR1(2) + +Process in the VLR to handle a request for information to handle MO short message submission + +Signals to/from the left are to/from the MSC + +``` + +stateDiagram-v2 + [*] --> Null1[Null] + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind --> Wait_For_Service_Primitive[Wait_For_Service_Primitive] + Wait_For_Service_Primitive --> Process_Access_Request_VLR[Process_Access_Request_VLR] + Process_Access_Request_VLR --> Wait_For_Info_Request[Wait_For_Info_Request] : OK + Process_Access_Request_VLR --> Null2[Null] : Vr, Error + +``` + +State transition diagram for process MO\_SM\_VLR. The diagram shows a sequence of states and transitions. It starts with an initial state (oval), leading to a 'Null' state (oval). From 'Null', a transition 'Receive\_Open\_Ind' (rectangle) leads to 'Wait\_For\_Service\_Primitive' (oval). From 'Wait\_For\_Service\_Primitive', a transition 'Process\_Access\_Request\_VLR' (rectangle) leads to another decision point. From this point, an 'OK' transition leads to 'Wait\_For\_Info\_Request' (oval), and a 'Vr, Error' transition leads to another 'Null' state (oval). + +3658 + +3659 + +Figure 23.2/3 (sheet 1 of 2): Process MOSM\_VLR + +![Flowchart for process MO_SM_VLR. It starts with 'Wait_For_Info_Request', leading to a merge point. From the merge point, one path goes to 'MAP_U_ABORT_req' -> 'Null'. The other path goes to 'MAP_SEND_INFO_FOR_MO_SMS_ind' -> 'Check_Indication'. 'Check_Indication' leads to 'MO_SMS_provisioned?' decision. If 'No', it goes to 'Set User Error: Teleservice not provisioned' -> merge point. If 'OK', it goes to 'Operator barring?' decision. If 'Yes', it goes to 'BAOC'. If 'No', it goes to 'SS barring?' decision. If 'Yes', it goes to 'BAOC'. If 'No', it goes to 'CAMEL_MO_SMS_VLR' -> 'See 3GPP TS 23.078' -> 'Result?' decision. 'Result?' 'Fail' goes to 'Null'. 'Result?' 'Pass' goes to 'Operator barring?' decision. If 'Yes', it goes to 'BOIC or BOIC-exHC etc'. If 'No', it goes to 'SS barring?' decision. If 'Yes', it goes to 'BOIC or BOIC-exHC'. If 'No', it goes to 'Set User Error: Call barred (Operator barring)' or 'Set User Error: Call barred (barring service active)' -> merge point. All paths eventually lead to a merge point before 'MAP_SEND_INFO_FOR_MO_SMS_rsp' -> 'MAP_CLOSE_req' -> 'Null'.](82d715590769d59b129a92b92d02bbc2_img.jpg) + +**process MO\_SM\_VLR** **MO\_SM\_VLR2(2)** + +Process in the VLR to handle a request for information to handle MO short message submission + +Signals to/from the left are to/from the MSC + +``` + + graph TD + WFI[Wait_For_Info_Request] --> Merge1(( )) + Merge1 --> MUI[MAP_U_ABORT_req] + MUI --> Null1([Null]) + Merge1 --> MSIM[MAP_SEND_INFO_FOR_MO_SMS_ind] + MSIM --> CI[Check_Indication] + CI --> MSP{MO_SMS_provisioned?} + MSP -- No --> SUE1[Set User Error: Teleservice not provisioned] + SUE1 --> Merge1 + CI -- OK --> OB1{Operator barring?} + OB1 -- Yes --> BAOC1[BAOC] + OB1 -- No --> SS1{SS barring?} + SS1 -- Yes --> BAOC2[BAOC] + SS1 -- No --> CMV[CAMEL_MO_SMS_VLR] + CMV --> S3GPP[See 3GPP TS 23.078] + CMV --> Res{Result?} + Res -- Fail --> Null2([Null]) + Res -- Pass --> OB2{Operator barring?} + OB2 -- Yes --> BOIC1[BOIC or BOIC-exHC etc] + OB2 -- No --> SS2{SS barring?} + SS2 -- Yes --> BOIC2[BOIC or BOIC-exHC] + SS2 -- No --> SUE2[Set User Error: Call barred (Operator barring)] + SS2 -- No --> SUE3[Set User Error: Call barred (barring service active)] + SUE2 --> Merge2(( )) + SUE3 --> Merge2 + BOIC1 --> Merge2 + BOIC2 --> Merge2 + Merge2 --> MSIR[MAP_SEND_INFO_FOR_MO_SMS_rsp] + MSIR --> MCR[MAP_CLOSE_req] + MCR --> Null3([Null]) + +``` + +Flowchart for process MO\_SM\_VLR. It starts with 'Wait\_For\_Info\_Request', leading to a merge point. From the merge point, one path goes to 'MAP\_U\_ABORT\_req' -> 'Null'. The other path goes to 'MAP\_SEND\_INFO\_FOR\_MO\_SMS\_ind' -> 'Check\_Indication'. 'Check\_Indication' leads to 'MO\_SMS\_provisioned?' decision. If 'No', it goes to 'Set User Error: Teleservice not provisioned' -> merge point. If 'OK', it goes to 'Operator barring?' decision. If 'Yes', it goes to 'BAOC'. If 'No', it goes to 'SS barring?' decision. If 'Yes', it goes to 'BAOC'. If 'No', it goes to 'CAMEL\_MO\_SMS\_VLR' -> 'See 3GPP TS 23.078' -> 'Result?' decision. 'Result?' 'Fail' goes to 'Null'. 'Result?' 'Pass' goes to 'Operator barring?' decision. If 'Yes', it goes to 'BOIC or BOIC-exHC etc'. If 'No', it goes to 'SS barring?' decision. If 'Yes', it goes to 'BOIC or BOIC-exHC'. If 'No', it goes to 'Set User Error: Call barred (Operator barring)' or 'Set User Error: Call barred (barring service active)' -> merge point. All paths eventually lead to a merge point before 'MAP\_SEND\_INFO\_FOR\_MO\_SMS\_rsp' -> 'MAP\_CLOSE\_req' -> 'Null'. + +3660 + +3661 + +**Figure 23.2/3 (sheet 2 of 2): Process MO\_SM\_VLR** + +![Flowchart for process MO_SM_SGSN. It starts with 'Null', then 'Gb_RP_MO_DATA_ind'. Decision: 'MO SMS provisioned?'. If No, goes to 'Set RP_ERROR: Requested facility not subscribed' -> 'Gb_RP_ERROR_req' -> 'Null'. If Yes, decision: 'Operator barring?'. If Yes, goes to 'BAOC'. If No, decision: 'SS barring?'. If Yes, goes to 'BAOC'. If No, goes to 'CAMEL_O_SMS_INIT' -> 'See 3GPP TS 23.078' -> 'Result?'. From 'Result?', options: 'SMS_Aborted' -> 'Null', 'Release_SMS' -> 'Set RP_ERROR according to gsmSCF instructions' -> 'Gb_RP_ERROR_req' -> 'Null', 'Redirect_SMS' -> 'Modify data according to gsmSCF instructions' -> 'Operator barring?'. If Yes, goes to 'BOIC or BOIC-exHC etc'. If No, decision: 'SS barring?'. If Yes, goes to 'CAMEL_O_SMS_FAILURE' -> 'See 3GPP TS 23.078' -> '2'. If No, goes to '3'. There are also connector points '1' and '2' leading to 'CAMEL_O_SMS_FAILURE' -> 'See 3GPP TS 23.078' -> 'Set RP_ERROR: Operator determined barring' -> 'Gb_RP_ERROR_req' -> 'Null'.](25f7c3066ddba1641935c3ba3cbcde1b_img.jpg) + +**process MO\_SM\_SGSN** **MO\_SM\_SGSN1(3)** + +Process in the SGSN to handle submission of a short message + +Signals to/from the left are to/from the UE; +signals to/from the right are to/from the HLR + +``` + +graph TD + Start([Null]) --> GbRP[Gb_RP_MO_DATA_ind] + GbRP --> MO_SMS_Prov{MO SMS provisioned?} + MO_SMS_Prov -- No --> RP_Err_Req1[Gb_RP_ERROR_req] + RP_Err_Req1 --> Null1([Null]) + MO_SMS_Prov -- Yes --> Op_Barr1{Operator barring?} + Op_Barr1 -- Yes --> BAOC1[BAOC] + Op_Barr1 -- No --> SS_Barr1{SS barring?} + SS_Barr1 -- Yes --> BAOC2[BAOC] + SS_Barr1 -- No --> CAMEL_Init[CAMEL_O_SMS_INIT] + CAMEL_Init --> TS_23_078_1[See 3GPP TS 23.078] + CAMEL_Init --> Result{Result?} + Result -- SMS_Aborted --> Null2([Null]) + Result -- Release_SMS --> RP_Err_Req2[Gb_RP_ERROR_req] + RP_Err_Req2 --> Null3([Null]) + Result -- Redirect_SMS --> ModData[Modify data according to gsmSCF instructions] + ModData --> Op_Barr2{Operator barring?} + Op_Barr2 -- Yes --> BOIC[BOIC or BOIC-exHC etc] + Op_Barr2 -- No --> SS_Barr2{SS barring?} + SS_Barr2 -- Yes --> CAMEL_Fail[CAMEL_O_SMS_FAILURE] + CAMEL_Fail --> TS_23_078_2[See 3GPP TS 23.078] + CAMEL_Fail --> Connector2((2)) + SS_Barr2 -- No --> Connector3((3)) + Connector1((1)) --> CAMEL_Fail2[CAMEL_O_SMS_FAILURE] + CAMEL_Fail2 --> TS_23_078_3[See 3GPP TS 23.078] + CAMEL_Fail2 --> RP_Err_Req3[Gb_RP_ERROR_req] + RP_Err_Req3 --> Null4([Null]) + Connector2 --> RP_Err_Req4[Gb_RP_ERROR_req] + RP_Err_Req4 --> Null5([Null]) + +``` + +Flowchart for process MO\_SM\_SGSN. It starts with 'Null', then 'Gb\_RP\_MO\_DATA\_ind'. Decision: 'MO SMS provisioned?'. If No, goes to 'Set RP\_ERROR: Requested facility not subscribed' -> 'Gb\_RP\_ERROR\_req' -> 'Null'. If Yes, decision: 'Operator barring?'. If Yes, goes to 'BAOC'. If No, decision: 'SS barring?'. If Yes, goes to 'BAOC'. If No, goes to 'CAMEL\_O\_SMS\_INIT' -> 'See 3GPP TS 23.078' -> 'Result?'. From 'Result?', options: 'SMS\_Aborted' -> 'Null', 'Release\_SMS' -> 'Set RP\_ERROR according to gsmSCF instructions' -> 'Gb\_RP\_ERROR\_req' -> 'Null', 'Redirect\_SMS' -> 'Modify data according to gsmSCF instructions' -> 'Operator barring?'. If Yes, goes to 'BOIC or BOIC-exHC etc'. If No, decision: 'SS barring?'. If Yes, goes to 'CAMEL\_O\_SMS\_FAILURE' -> 'See 3GPP TS 23.078' -> '2'. If No, goes to '3'. There are also connector points '1' and '2' leading to 'CAMEL\_O\_SMS\_FAILURE' -> 'See 3GPP TS 23.078' -> 'Set RP\_ERROR: Operator determined barring' -> 'Gb\_RP\_ERROR\_req' -> 'Null'. + +3662 + +3663 + +Figure 23.2/4 (sheet 1 of 3): Process MO\_SM\_SGSN + +![Flowchart for process MO_SM_SGSN. It starts at connector 3, checks for message segmentation. If 'Yes', it sends MAP_OPEN_req and MAP_DELIMITER_req to the HLR, receives confirmation, performs a MAP_Vr dialogue, and then checks submission success. If 'No', it checks if a TCAP handshake is required. If 'yes', it sends MAP_OPEN_req, MAP_MO_FORWARD_SHORT_MESSAGE_req, and MAP_DELIMITER_req to the HLR, receives confirmation, performs a MAP_Vr dialogue, and checks submission success. If 'no', it sends MAP_MO_FORWARD_SHORT_MESSAGE_req to the HLR, receives confirmation, checks submission success, and then handles the result (CAMEL_O_SMS_SUBMITTED, FAILURE, or error handling).](52b571c5f533172048bd268c4eff2da0_img.jpg) + +**process MO\_SM\_SGSN** **MO\_SM\_SGSN2(3)** + +*Process in the SGSN to handle submission of a short message* + +*Signals to/from the left are to/from the UE; signals to/from the right are to/from the HLR* + +``` + +graph TD + Start((3)) --> Segmentation{Message segmentation needed?} + Segmentation -- Yes --> OpenReq1[MAP_OPEN_req +MAP_DELIMITER_req] + OpenReq1 --> OpenCnf1[Receive_Open_Cnf] + OpenCnf1 -- OK --> ForwardReq1[MAP_MO_FORWARD_SHORT_MESSAGE_req +MAP_DELIMITER_req] + ForwardReq1 --> WaitResult1[Wait_For_MO_SMS_Result] + OpenCnf1 -- Vr --> PerformVr1[Perform MAP_Vr dialogue] + PerformVr1 --> Success{Submission successful?} + Success -- Yes --> Submitted1[CAMEL_O_SMS_SUBMITTED] + Submitted1 --> AckReq1{Gb_RP_ACK_req} + AckReq1 --> Null1[Null] + Success -- No --> Failure1[CAMEL_O_SMS_FAILURE] + Failure1 --> SetError1[Set RP_ERROR] + SetError1 --> ErrorReq1{Gb_RP_ERROR_req} + ErrorReq1 --> Null2[Null] + Segmentation -- No --> Handshake{TCAP Handshake required} + Handshake -- yes --> OpenReq2[MAP_OPEN_req +MAP_MO_FORWARD_SHORT_MESSAGE_req +MAP_DELIMITER_req] + OpenReq2 --> OpenCnf2[Receive_Open_Cnf] + OpenCnf2 -- OK --> ForwardReq2[MAP_MO_FORWARD_SHORT_MESSAGE_req] + ForwardReq2 --> WaitResult2[Wait_For_MO_SMS_Result] + OpenCnf2 -- Vr --> PerformVr2[Perform MAP_Vr dialogue] + PerformVr2 --> Success2{Submission successful?} + Success2 -- Yes --> Submitted2[CAMEL_O_SMS_SUBMITTED] + Submitted2 --> AckReq2{Gb_RP_ACK_req} + AckReq2 --> Null3[Null] + Success2 -- No --> Failure2[CAMEL_O_SMS_FAILURE] + Failure2 --> SetError2[Set RP_ERROR] + SetError2 --> ErrorReq2{Gb_RP_ERROR_req} + ErrorReq2 --> Null4[Null] + Handshake -- no --> ForwardReq3[MAP_MO_FORWARD_SHORT_MESSAGE_req] + ForwardReq3 --> CheckConfirm[Check Confirmation] + CheckConfirm -- OK --> Submitted3[CAMEL_O_SMS_SUBMITTED] + Submitted3 --> AckReq3{Gb_RP_ACK_req} + AckReq3 --> Null5[Null] + CheckConfirm -- "Provider Error, User Error, Data Error" --> Failure3[CAMEL_O_SMS_FAILURE] + Failure3 --> SetError3[Set RP_ERROR] + SetError3 --> ErrorReq3{Gb_RP_ERROR_req} + ErrorReq3 --> Null6[Null] + PerformVr1 -.-> See3GPP1[See 3GPP TS 23.078] + PerformVr2 -.-> See3GPP2[See 3GPP TS 23.078] + Submitted1 -.-> See3GPP3[See 3GPP TS 23.078] + Failure1 -.-> See3GPP4[See 3GPP TS 23.078] + Submitted2 -.-> See3GPP5[See 3GPP TS 23.078] + Failure2 -.-> See3GPP6[See 3GPP TS 23.078] + Submitted3 -.-> See3GPP7[See 3GPP TS 23.078] + Failure3 -.-> See3GPP8[See 3GPP TS 23.078] + CAMEL_O_SMS_FAILURE1[CAMEL_O_SMS_FAILURE] -.-> See3GPP9[See 3GPP TS 23.078] + CAMEL_O_SMS_FAILURE2[CAMEL_O_SMS_FAILURE] -.-> See3GPP10[See 3GPP TS 23.078] + CAMEL_O_SMS_FAILURE3[CAMEL_O_SMS_FAILURE] -.-> See3GPP11[See 3GPP TS 23.078] + +``` + +Flowchart for process MO\_SM\_SGSN. It starts at connector 3, checks for message segmentation. If 'Yes', it sends MAP\_OPEN\_req and MAP\_DELIMITER\_req to the HLR, receives confirmation, performs a MAP\_Vr dialogue, and then checks submission success. If 'No', it checks if a TCAP handshake is required. If 'yes', it sends MAP\_OPEN\_req, MAP\_MO\_FORWARD\_SHORT\_MESSAGE\_req, and MAP\_DELIMITER\_req to the HLR, receives confirmation, performs a MAP\_Vr dialogue, and checks submission success. If 'no', it sends MAP\_MO\_FORWARD\_SHORT\_MESSAGE\_req to the HLR, receives confirmation, checks submission success, and then handles the result (CAMEL\_O\_SMS\_SUBMITTED, FAILURE, or error handling). + +3664 + +3665 + +Figure 23.2/4 (sheet 2 of 3): Process MO\_SM\_SGSN + +![Flowchart for process MO_SM_SGSN. The flow starts with 'Wait_For_MO_SMS_Result', followed by 'MAP_NOTICE_ind' (left) and an unlabeled box (right) leading to 'MAP_U_ABORT_ind, MAP_P_ABORT_ind'. Then 'MAP_CLOSE_req' (left) and a merge point. Next is 'CAMEL_O_SMS_FAILURE' (left) with a note 'See 3GPP TS 23.078'. Then 'Set RP_ERROR: Network out of order' (left), 'Gb_RP_ERROR_req' (left), and finally 'Null'.](e4734458e8913c13c84699d9d3f66ec8_img.jpg) + +process MO\_SM\_SGSN + +MO\_SM\_SGSN3(3) + +Process in the SGSN to handle submission of a short message + +Signals to/from the left are to/from the UE; signals to/from the right are to/from the HLR + +``` + +graph TD + Start([Wait_For_MO_SMS_Result]) --> MAP_NOTICE_ind[/MAP_NOTICE_ind/] + Start --> Unlabeled[ ] + Unlabeled --> MAP_U_ABORT_ind[MAP_U_ABORT_ind, MAP_P_ABORT_ind] + MAP_NOTICE_ind --> MAP_CLOSE_req[/MAP_CLOSE_req/] + MAP_CLOSE_req --> Merge(( )) + MAP_U_ABORT_ind --> Merge + Merge --> CAMEL_O_SMS_FAILURE[CAMEL_O_SMS_FAILURE] + CAMEL_O_SMS_FAILURE -.-> Note[See 3GPP TS 23.078] + CAMEL_O_SMS_FAILURE --> SetRP[Set RP_ERROR: Network out of order] + SetRP --> GbRP[Gb_RP_ERROR_req] + GbRP --> Null([Null]) + +``` + +Flowchart for process MO\_SM\_SGSN. The flow starts with 'Wait\_For\_MO\_SMS\_Result', followed by 'MAP\_NOTICE\_ind' (left) and an unlabeled box (right) leading to 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind'. Then 'MAP\_CLOSE\_req' (left) and a merge point. Next is 'CAMEL\_O\_SMS\_FAILURE' (left) with a note 'See 3GPP TS 23.078'. Then 'Set RP\_ERROR: Network out of order' (left), 'Gb\_RP\_ERROR\_req' (left), and finally 'Null'. + +3666 + +3667 + +Figure 23.2/4 (sheet 3 of 3): Process MO\_SM\_SGSN + +![Flowchart for process MO_SM_IWMSC. It starts with an initial node leading to 'Null', then 'Receive_Open_Ind'. From 'Receive_Open_Ind', three paths emerge: 'Vr' leading to 'Perform MAP Vr dialogue' -> 'Null'; 'OK' leading to a decision 'TCAP Handshake required'; and 'Error' leading to 'Null'. From 'TCAP Handshake required', 'no' leads to 'Wait_For_Service_Primitive' -> 'MAP_DELIMITER_ind' -> 'MAP_DELIMITER_req' -> 'Wait_For_Service_Primitive'; 'yes' leads to 'Wait_For_DELIMITER'. From 'Wait_For_DELIMITER', multiple paths emerge: 1) 'MAP_DELIMITER_ind' -> 'MAP_DELIMITER_req' -> 'Wait_For_Service_Primitive'; 2) an unlabeled path leading to 'Set Error System Failure' -> 'MAP_MO_FORWARD_SM_rsp' -> 'MAP_CLOSE_req' -> 'Null'; 3) 'MAP_MO_FORWARD_SHORT_MESSAGE_ind'; 4) 'MAP_NOTICE_ind' -> 'MAP_CLOSE_req' -> 'Null'; 5) an unlabeled path leading to a box with 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' -> 'Null'.](46e1d5619acee885091b5677076bba4b_img.jpg) + +**process MO\_SM\_IWMSC** **MO\_SM\_IWMSC1(2)** + +Process in the MSC to handle MO short message submission + +Signals to/from the left are to/from the MSC; +signals to/from the right are to/from the SMSC + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind -- Vr --> Perform_MAP_Vr_dialogue[Perform MAP Vr dialogue] + Perform_MAP_Vr_dialogue --> Null2([Null]) + Receive_Open_Ind -- OK --> TCAP_Handshake_required{TCAP Handshake required} + Receive_Open_Ind -- Error --> Null3([Null]) + TCAP_Handshake_required -- no --> Wait_For_Service_Primitive1[Wait_For_Service_Primitive] + Wait_For_Service_Primitive1 --> MAP_DELIMITER_ind1[MAP_DELIMITER_ind] + MAP_DELIMITER_ind1 --> MAP_DELIMITER_req1[MAP_DELIMITER_req] + MAP_DELIMITER_req1 --> Wait_For_Service_Primitive2[Wait_For_Service_Primitive] + TCAP_Handshake_required -- yes --> Wait_For_DELIMITER[Wait_For_DELIMITER] + Wait_For_DELIMITER --> MAP_DELIMITER_ind2[MAP_DELIMITER_ind] + MAP_DELIMITER_ind2 --> MAP_DELIMITER_req2[MAP_DELIMITER_req] + MAP_DELIMITER_req2 --> Wait_For_Service_Primitive3[Wait_For_Service_Primitive] + Wait_For_DELIMITER --> Set_Error_System_Failure[Set Error System Failure] + Set_Error_System_Failure --> MAP_MO_FORWARD_SM_rsp[MAP_MO_FORWARD_SM_rsp] + MAP_MO_FORWARD_SM_rsp --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> Null4([Null]) + Wait_For_DELIMITER --> MAP_MO_FORWARD_SHORT_MESSAGE_ind[MAP_MO_FORWARD_SHORT_MESSAGE_ind] + Wait_For_DELIMITER --> MAP_NOTICE_ind[MAP_NOTICE_ind] + MAP_NOTICE_ind --> MAP_CLOSE_req2[MAP_CLOSE_req] + MAP_CLOSE_req2 --> Null5([Null]) + Wait_For_DELIMITER --> Unlabeled1[ ] + Unlabeled1 --> MAP_U_ABORT_ind[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + MAP_U_ABORT_ind --> Null6([Null]) + +``` + +Flowchart for process MO\_SM\_IWMSC. It starts with an initial node leading to 'Null', then 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', three paths emerge: 'Vr' leading to 'Perform MAP Vr dialogue' -> 'Null'; 'OK' leading to a decision 'TCAP Handshake required'; and 'Error' leading to 'Null'. From 'TCAP Handshake required', 'no' leads to 'Wait\_For\_Service\_Primitive' -> 'MAP\_DELIMITER\_ind' -> 'MAP\_DELIMITER\_req' -> 'Wait\_For\_Service\_Primitive'; 'yes' leads to 'Wait\_For\_DELIMITER'. From 'Wait\_For\_DELIMITER', multiple paths emerge: 1) 'MAP\_DELIMITER\_ind' -> 'MAP\_DELIMITER\_req' -> 'Wait\_For\_Service\_Primitive'; 2) an unlabeled path leading to 'Set Error System Failure' -> 'MAP\_MO\_FORWARD\_SM\_rsp' -> 'MAP\_CLOSE\_req' -> 'Null'; 3) 'MAP\_MO\_FORWARD\_SHORT\_MESSAGE\_ind'; 4) 'MAP\_NOTICE\_ind' -> 'MAP\_CLOSE\_req' -> 'Null'; 5) an unlabeled path leading to a box with 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' -> 'Null'. + +3668 + +3669 + +3670 + +**Figure 23.2/5 (sheet 1 of 2): Process MO\_SM\_IWMSC** + +process MO\_SM\_IWMSC + +MO\_SM\_IWMSC2(2) + +Process in the MSC to handle MO short message submission + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the SMSC + +![Flowchart for process MO_SM_IWMSC showing message handling logic between MSC and SMSC.](1fc0375eeb03547ee607c15fef041f56_img.jpg) + +``` + + graph TD + Start([Wait_For_Service_Primitive]) --> Branch1(( )) + Branch1 --> In1{{ }} + In1 --> Out1[MAP_MO_FORWARD_SHORT_MESSAGE_ind] + Out1 --> Check[Check_Indication] + Check --> Decision{SC known?} + Decision -- OK --> Yes[Yes] + Decision -- No --> Error1((Error 1)) + Yes --> Req1{SC_RP_MO_DATA_req} + Req1 --> Wait1([Wait_For_Confirm_From_SC]) + Wait1 --> Branch2(( )) + Branch2 --> In2{{ }} + In2 --> Out2[MAP_NOTICE_ind] + Out2 --> Req2{MAP_CLOSE_req} + Req2 --> Out3[SC_ABORT_req] + Out3 --> Null1([Null]) + Branch2 --> In3{{ }} + In3 --> Out4[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Branch2 --> In4{{ }} + In4 --> Out5[SC_RP_ACK_ind] + Out5 --> Null2([Null]) + Branch2 --> In5{{ }} + In5 --> Out6[SC_RP_ERROR_ind] + Out6 --> Error2[Set User Error: SM delivery failure] + Error2 --> Param2[Set error parameter: according to service centre error value] + Param2 --> End2((1)) + Branch2 --> In6{{ }} + In6 --> Out7[MAP_MO_FORWARD_SHORT_MESSAGE_rsp] + Out7 --> Null3([Null]) + Branch1 --> In7{{ }} + In7 --> Out8[MAP_NOTICE_ind] + Out8 --> Req3{MAP_CLOSE_req} + Req3 --> Null4([Null]) + Branch1 --> In8{{ }} + In8 --> Out9[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Branch1 --> In9{{ }} + In9 --> Out10[MAP_MO_FORWARD_SHORT_MESSAGE_ind] + Out10 --> Null5([Null]) + +``` + +Flowchart for process MO\_SM\_IWMSC showing message handling logic between MSC and SMSC. + +3671 + +3672 + +Figure 23.2/5 (sheet 2 of 2): Process MO\_SM\_IWMSC + +3673 **23.3 The mobile terminated short message transfer procedure** + +3674 The mobile terminated short message transfer procedure is used for forwarding a short message or several short + 3675 messages from a Service Centre to a mobile subscriber. The message flow for the mobile terminated short message + 3676 procedure for a single short message transfer is shown in figure 23.3/1. + +![Sequence diagram showing the mobile terminated short message transfer procedure between MS, Serving MSC or SGSN, VLR, HLR, Gateway MSC, and SC.](514150054ea2e72f86da03de4e230d7d_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Serving MSC or SGSN + participant VLR + participant HLR + participant Gateway MSC + participant SC + + Note right of SC: 1 + SC->>Gateway MSC: + Note right of Gateway MSC: 2 + Gateway MSC->>HLR: + Note right of HLR: 3 + HLR->>Gateway MSC: + Note right of Gateway MSC: 4a + Gateway MSC->>Serving MSC or SGSN: + Note right of Serving MSC or SGSN: 4b + Serving MSC or SGSN->>VLR: + Note right of VLR: 5 + VLR->>Serving MSC or SGSN: + Note right of Serving MSC or SGSN: 5a + Serving MSC or SGSN->>VLR: + Note right of VLR: 5b + VLR->>MS: + Note right of MS: 7 + MS->>Serving MSC or SGSN: + Note right of Serving MSC or SGSN: 8 + Serving MSC or SGSN->>VLR: + Note right of VLR: 9 + VLR->>MS: + Note right of MS: 11 + MS->>Serving MSC or SGSN: + Note right of Serving MSC or SGSN: 12 + Serving MSC or SGSN->>Gateway MSC: + Note right of Gateway MSC: 13 + Gateway MSC->>SC: + Note right of SC: 14 + +``` + +Sequence diagram showing the mobile terminated short message transfer procedure between MS, Serving MSC or SGSN, VLR, HLR, Gateway MSC, and SC. + +3677 + +3678 + +**Figure 23.3/1: Mobile terminated short message service procedures** + +3679 1) Short Message (3GPP TS 23.040). + 3680 2) MAP\_SEND\_ROUTING\_INFO\_FOR\_SM. + 3681 3) MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_ACK. + 3682 4) TCAP BEGIN (\*\*\*) + 3683 4a) TCAP CONTINUE (\*\*\*) + 3684 4b) MAP\_MT\_FORWARD\_SHORT\_MESSAGE. + 3685 The message should include the timer value used at the SMS-GMSC for the supervision of the + 3686 MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK. + 3687 5) MAP\_SEND\_INFO\_FOR\_MT\_SMS (\*). + 3688 5a) MAP\_CONTINUE\_CAMEL\_SMS\_HANDLING (\*) (\*\*\*) + 3689 5b) MAP\_SEND\_INFO\_FOR\_MT\_SMS (\*) (\*\*\*) + 3690 6) MAP\_PAGE/MAP\_SEARCH\_FOR\_MOBILE\_SUBSCRIBER (\*). + 3691 7) Page (3GPP TS 24.008 [35]). + 3692 8) Page response (3GPP TS 24.008 [35]). + 3693 9) MAP\_PROCESS\_ACCESS\_REQUEST\_ACK and + 3694 MAP\_SEARCH\_FOR\_MOBILE\_SUBSCRIBER\_ACK (\*). + 3695 10) MAP\_SEND\_INFO\_FOR\_MT\_SMS\_ACK (\*). + 3696 11) Short Message (3GPP TS 24.011 [37]). + 3697 12) Short Message Acknowledgement (3GPP TS 24.011 [37]). + 3698 13) MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK. + 3699 14) Short Message Acknowledgement (3GPP TS 23.040). + 3700 + 3701 (\*) Messages 5), 5a), 5b), 6), 9), and 10) are not used by the SGSN. + 3702 (\*\*) These messages are used only for a subscriber provisioned with MT-SMS-CSI in the VLR. + 3703 (\*\*\*) If + 3704 a) + 3705 - the capacity of a message signal unit in the lower layers of the protocol is enough to carry the + 3706 content of the MAP\_OPEN request and the content of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE + 3707 request in a single TC message, + 3708 + 3709 and + 3710 b) the SMS Gateway MSC operator and the serving node (MSC or SGSN) operator + 3711 agreed not to use the TCAP handshake countermeasure against SMS fraud for + 3712 messages exchanged between their networks (see 3GPP TS 33.204 [34a]) + 3713 then + 3714 the TCAP handshake may be omitted. + 3715 + +3716 The message flow for the mobile terminated short message procedure for multiple short message transfer is shown in + 3717 figure 23.3/2. + +![Sequence diagram showing the mobile terminated short message procedure for multiple short message transfer. Lifelines: MS, Serving MSC or SGSN, VLR, HLR, Gateway MSC, SC. The sequence starts with the SC sending a Short Message (1) to the Gateway MSC, which then sends a MAP_SEND_ROUTING_INFO_FOR_SM (2) to the HLR. The HLR responds with a MAP_SEND_ROUTING_INFO_FOR_SM_ACK (3). The Gateway MSC then sends a TCAP BEGIN (4) to the Serving MSC or SGSN. The Serving MSC or SGSN sends a TCAP CONTINUE (4a) to the Gateway MSC, which responds with a MAP_MT_FORWARD_SHORT_MESSAGE (4b). The Serving MSC or SGSN then sends a MAP_SEND_INFO_FOR_MT_SMS (5) to the VLR, which responds with a MAP_CONTINUE_CAMEL_SMS_HANDLING (5a). The Serving MSC or SGSN then sends a MAP_SEND_INFO_FOR_MT_SMS (5b) to the VLR, which responds with a MAP_PAGE/MAP_SEARCH_FOR_MOBILE_SUBSCRIBER (6). The VLR then sends a Page (7) to the MS, which responds with a Page response (8). The VLR then sends a MAP_PROCESS_ACCESS_REQUEST_ACK and a MAP_SEARCH_FOR_MOBILE_SUBSCRIBER_ACK (9) to the Serving MSC or SGSN. The Serving MSC or SGSN then sends a MAP_SEND_INFO_FOR_MT_SMS_ACK (10) to the VLR, which responds with a Short Message (11). The VLR then sends a Short Message Acknowledgement (12) to the MS. Finally, the Serving MSC or SGSN sends a MAP_MT_FORWARD_SHORT_MESSAGE_ACK (13) to the Gateway MSC, which then sends a Short Message (14) to the SC. The SC responds with a Short Message Acknowledgement (15). The Gateway MSC then sends a Short Message (16) to the MS, which responds with a Short Message Acknowledgement (17). The Gateway MSC then sends a Short Message (18) to the Serving MSC or SGSN, which responds with a Short Message Acknowledgement (19). The Serving MSC or SGSN then sends a Short Message (20) to the VLR.](8d47784a87ca9afcc7731bbe41341031_img.jpg) + +Sequence diagram showing the mobile terminated short message procedure for multiple short message transfer. Lifelines: MS, Serving MSC or SGSN, VLR, HLR, Gateway MSC, SC. The sequence starts with the SC sending a Short Message (1) to the Gateway MSC, which then sends a MAP\_SEND\_ROUTING\_INFO\_FOR\_SM (2) to the HLR. The HLR responds with a MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_ACK (3). The Gateway MSC then sends a TCAP BEGIN (4) to the Serving MSC or SGSN. The Serving MSC or SGSN sends a TCAP CONTINUE (4a) to the Gateway MSC, which responds with a MAP\_MT\_FORWARD\_SHORT\_MESSAGE (4b). The Serving MSC or SGSN then sends a MAP\_SEND\_INFO\_FOR\_MT\_SMS (5) to the VLR, which responds with a MAP\_CONTINUE\_CAMEL\_SMS\_HANDLING (5a). The Serving MSC or SGSN then sends a MAP\_SEND\_INFO\_FOR\_MT\_SMS (5b) to the VLR, which responds with a MAP\_PAGE/MAP\_SEARCH\_FOR\_MOBILE\_SUBSCRIBER (6). The VLR then sends a Page (7) to the MS, which responds with a Page response (8). The VLR then sends a MAP\_PROCESS\_ACCESS\_REQUEST\_ACK and a MAP\_SEARCH\_FOR\_MOBILE\_SUBSCRIBER\_ACK (9) to the Serving MSC or SGSN. The Serving MSC or SGSN then sends a MAP\_SEND\_INFO\_FOR\_MT\_SMS\_ACK (10) to the VLR, which responds with a Short Message (11). The VLR then sends a Short Message Acknowledgement (12) to the MS. Finally, the Serving MSC or SGSN sends a MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK (13) to the Gateway MSC, which then sends a Short Message (14) to the SC. The SC responds with a Short Message Acknowledgement (15). The Gateway MSC then sends a Short Message (16) to the MS, which responds with a Short Message Acknowledgement (17). The Gateway MSC then sends a Short Message (18) to the Serving MSC or SGSN, which responds with a Short Message Acknowledgement (19). The Serving MSC or SGSN then sends a Short Message (20) to the VLR. + +3718 + 3719 **Figure 23.3/2: Mobile terminated short message procedure for multiple short message transfer** + +- 3720 1) Short Message (3GPP TS 23.040 [26]). +- 3721 2) MAP\_SEND\_ROUTING\_INFO\_FOR\_SM. +- 3722 3) MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_ACK. +- 3723 4) TCAP BEGIN (\*\*\*) +- 3724 4a) TCAP CONTINUE (\*\*\*) +- 3725 4b) MAP\_MT\_FORWARD\_SHORT\_MESSAGE (note 1). +- 3726 The message should include the timer value used at the SMS-GMSC for the supervision of the +- 3727 MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK. +- 3728 5) MAP\_SEND\_INFO\_FOR\_MT\_SMS (\*). +- 3729 5a) MAP\_CONTINUE\_CAMEL\_SMS\_HANDLING (\*) (\*\*) +- 3730 5b) MAP\_SEND\_INFO\_FOR\_MT\_SMS (\*) (\*\*) +- 3731 6) MAP\_PAGE/MAP\_SEARCH\_FOR\_MOBILE\_SUBSCRIBER (\*). +- 3732 7) Page (3GPP TS 48.008 [49]). +- 3733 8) Page response (3GPP TS 24.008 [35]). +- 3734 9) MAP\_PROCESS\_ACCESS\_REQUEST\_ACK and +- 3735 MAP\_SEARCH\_FOR\_MOBILE\_SUBSCRIBER\_ACK (\*). +- 3736 10) MAP\_SEND\_INFO\_FOR\_MT\_SMS\_ACK (\*). +- 3737 11) Short Message (3GPP TS 24.011 [37]). +- 3738 12) Short Message Acknowledgement (3GPP TS 24.011 [37]). +- 3739 13) MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK. + +3740 14) Short Message Acknowledgement (3GPP TS 23.040 [26]). + +3741 15) Short Message (3GPP TS 23.040 [26]). + +3742 16) MAP\_MT\_FORWARD\_SHORT\_MESSAGE (note 2). + +3743 The message should include the timer value used at the SMS-GMSC for the supervision of the + +3744 MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK. + +3745 17) Short Message (3GPP TS 24.011 [37]). + +3746 18) Short Message Acknowledgement (3GPP TS 24.011 [37]). + +3747 19) MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK. + +3748 20) Short Message Acknowledgement (3GPP TS 23.040 [26]). + +3749 + +3750 (\*) Messages 5), 5a), 5b) 6), 9), and 10) are not used by the SGSN. + +3751 (\*\*) These messages are used only for a subscriber provisioned with MT-SMS-CSI in the VLR. + +3752 (\*\*\*) If + +3753 a) the capacity of a message signal unit in the lower layers of the protocol is enough to carry the + +3754 content of the MAP\_OPEN request and the content of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE + +3755 request in a single TC message, + +3756 and + +3757 b) the SMS Gateway MSC operator and the serving node (MSC or SGSN) operator + +3758 agreed not to use the TCAP handshake countermeasure against SMS fraud for + +3759 messages exchanged between their networks (see 3GPP TS 33.204 [34a]) + +3760 then the TCAP handshake may be omitted. + +3761 + +3762 NOTE 1: The "More Messages To Send" flag is TRUE. + +3763 NOTE 2: The "More Messages To Send" flag is FALSE. + +3764 + +3765 In the multiple short message transfer the service MAP\_MT\_FORWARD\_SHORT\_MESSAGE can be used several + +3766 times. However, the short message transfer is always acknowledged to the Service Centre before the next short message + +3767 is sent. + +3768 In addition the following MAP services are used: + +3769 MAP\_PROCESS\_ACCESS\_REQUEST (see clause 8.3); (\*) + +3770 MAP\_PAGE (see clause 8.2); (\*) + +3771 MAP\_SEARCH\_FOR\_MS (see clause 8.2); (\*) + +3772 MAP\_AUTHENTICATE (see clause 8.5); (\*) + +3773 MAP\_SET\_CIPHERING\_MODE (see clause 8.6); (\*) + +3774 MAP\_CHECK\_IMEI (see clause 8.7); + +3775 MAP\_FORWARD\_NEW\_TMSI (see clause 8.9); (\*) + +3776 MAP\_REPORT\_SM\_DELIVERY\_STATUS (see clause 12.3); + +3777 MAP\_INFORM\_SERVICE\_CENTRE (see clause 12.6); + +3778 MAP\_TRACE\_SUBSCRIBER\_ACTIVITY (see clause 9.1); (\*) + +3779 MAP\_READY\_FOR\_SM (see clause 12.4). + +3780 (\*) These services are not used by the SGSN. + +3781 A message flow example for the mobile terminated short message procedure for a single short message transfer in an + +3782 environment that makes use of an SMS Router for MT-short-message-transfer is shown in figure 23.3/2a. + +3783 NOTE: This message flow can be applied only if no IP-SM-GW deployed in the same network. + +![Sequence diagram for Mobile terminated short message procedure with SMS Router. Six vertical lifelines are shown. Arrows indicate message flow: from the 6th lifeline to the 5th, then to the 4th, then to the 3rd, and finally from the 3rd to the 5th.](17acb575c195ee674cfb0d30fc8a33e0_img.jpg) + +Sequence diagram for Mobile terminated short message procedure with SMS Router. Six vertical lifelines are shown. Arrows indicate message flow: from the 6th lifeline to the 5th, then to the 4th, then to the 3rd, and finally from the 3rd to the 5th. + +3784 + +3785 + +**Figure 23.3/2a Mobile terminated short message procedure with SMS Router** + +- 3786 1) Short Message (3GPP TS 23.040 [26]) +- 3787 2) & 3) MAP\_SEND\_ROUTING\_INFO\_FOR\_SM +- 3788 NOTE: The HLR relays the message MAP\_SEND\_ROUTING\_INFO\_FOR\_SM received from the SMS-GMSC +- 3789 to the SMS Router on SCCP level. How this is done is implementation specific. +- 3790 4) MAP\_SEND\_ROUTING\_INFO\_FOR\_SM +- 3791 5) MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_ACK and conditionally MAP\_INFORM\_SERVICE\_CENTRE +- 3792 6) MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_ACK and conditionally MAP\_INFORM\_SERVICE\_CENTRE +- 3793 7) Conditionally: Inform Service Centre (3GPP TS 23.040 [26]) +- 3794 8) MAP\_MT\_FORWARD\_SHORT\_MESSAGE +- 3795 The message should include the timer value used at the SMS-GMSC for the supervision of the +- 3796 MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK. +- 3797 NOTE: In this example the SMS-GMSC decides to attempt delivery via MSC. Therefore the SCCP called party +- 3798 SSN shall be set to SSN for MSC. +- 3799 9) MAP\_MT\_FORWARD\_SHORT\_MESSAGE +- 3800 The message should include the timer value used at the SMS-GMSC for the supervision of the +- 3801 MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK. +- 3802 10) MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ERROR +- 3803 NOTE: In this example delivery via the MSC is unsuccessful e.g. due to IMSI detached +- 3804 11) MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ERROR +- 3805 12) MAP\_MT\_FORWARD\_SHORT\_MESSAGE +- 3806 NOTE: In this example the SMS-GMSC decides to retry delivery via the SGSN. Therefore the SCCP called party +- 3807 SSN shall be set to the SSN for SGSN. + +3808 13) MAP\_MT\_FORWARD\_SHORT\_MESSAGE +3809 The message should include the timer value used at the SMS-GMSC for the supervision of the +3810 MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK. +3811 14) MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK +3812 NOTE: In this example delivery via SGSN is successful +3813 15) MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK +3814 16) Conditionally: MAP\_REPORT\_SM\_DELIVERY\_STATUS +3815 NOTE: In this example unsuccessful delivery via MSC and successful delivery via SGSN is reported +3816 17) MAP\_REPORT\_SM\_DELIVERY\_STATUS\_Ack +3817 18) Short Message Acknowledgement (3GPP TS 23.040 [26]). +3818 +3819 A message flow example for the mobile terminated short message procedure for a single short message transfer in an +3820 environment that makes use of an IP-SM-GW (see 3GPP TS 23.204 [134]) for MT-short-message-transfer is shown in +3821 figure 23.3/2b. +3822 NOTE: SMS Routers can apply this message flow as well. + +![Sequence diagram showing three messages between four lifelines. The messages are: 1) from the 4th lifeline to the 3rd, 2) from the 3rd lifeline to the 2nd, and 3) from the 2nd lifeline to the 1st.](54327e3de1d855ebc746b9fc1d29eca4_img.jpg) + +``` +sequenceDiagram + participant 4 + participant 3 + participant 2 + participant 1 + Note right of 4: 1) Short Message (3GPP TS 23.040 [26]) + 4->>3: + Note right of 3: 2) MAP_SEND_ROUTING_INFO_FOR_SM + 3->>2: + Note right of 2: 3) MAP_SEND_ROUTING_INFO_FOR_SM + 2->>1: +``` + +Sequence diagram showing three messages between four lifelines. The messages are: 1) from the 4th lifeline to the 3rd, 2) from the 3rd lifeline to the 2nd, and 3) from the 2nd lifeline to the 1st. + +3824 + +3825 + +**Figure 23.3/2b Mobile terminated short message procedure with IP-SM-GW** + +3826 + +1) + +Short Message (3GPP TS 23.040 [26]) + +3827 + +2) + +MAP\_SEND\_ROUTING\_INFO\_FOR\_SM + +3828 + +the message is forwarded to the IP-SM-GW assigned to the recipient of the SM + +3829 + +the message may contain IP-SM-GW Guidance support indication + +3830 + +3) + +MAP\_SEND\_ROUTING\_INFO\_FOR\_SM + +3831 4) MAP\_SEND\_ROUTING\_INFO\_FOR\_SM +3832 since the message is received from an IP-SM-GW, it is not forwarded to an IP-SM-GW +3833 5) MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_ACK and conditionally MAP\_INFORM\_SERVICE\_CENTRE +3834 6) MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_ACK and conditionally MAP\_INFORM\_SERVICE\_CENTRE +3835 The IP-SM-GW returns its own address within the network node number parameter +3836 The message may include IP-SM-GW Guidance +3837 7) Conditionally: Inform Service Centre (3GPP TS 23.040 [26]) +3838 8) MAP\_MT\_FORWARD\_SHORT\_MESSAGE +3839 If the IP-SM-GW-Guidance support indicator was present in message 2 and IP-SM-GW-Guidance was +3840 present in message 6, message 8 shall contain the used timer value for supervision of +3841 MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK; the used timer should be identical to the recommended +3842 value received in message 6 to ensure that the IP-SM-GW can attempt delivery to multiple domains if +3843 necessary and shall not be lower than the minimum value received in message 6 to ensure that an IP-SM- +3844 GW can attempt delivery to at least one domain. +3845 Otherwise, The message should include the timer value used at the SMS-GMSC for the supervision of the +3846 MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK. +3847 9) MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK +3848 10) Conditionally: MAP\_REPORT\_SM\_DELIVERY\_STATUS +3849 NOTE: As an IP-SM-GW is deployed the message is acknowledged ignoring its content + +3850 11) MAP\_REPORT\_SM\_DELIVERY\_STATUS\_Ack +3851 12) Conditionally: MAP\_REPORT\_SM\_DELIVERY\_STATUS +3852 since the message is received from an IP-SM-GW, it is processed +3853 13) MAP\_REPORT\_SM\_DELIVERY\_STATUS\_Ack +3854 NOTE: Step 12 and 13 is independent of steps 10, 11, and 14. They can run in parallel. + +3855 14) Short Message Acknowledgement (3GPP TS 23.040 [26]). +3856 + +### 3857 23.3.1 Procedure in the SMS-GMSC + +3858 Any CAMEL-specific handling described in this clause is omitted if the SMS-GMSC does not support CAMEL. +3859 CAMEL-specific handling is invoked only if the SMS-GMSC is integrated with the VMSC. + +3860 The process starts when the SMS-GMSC receives an SC\_RP\_MT\_DATA indication from a Service Centre. The MAP +3861 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +3862 Receive\_Open\_Cnf see clause 25.1.2; + +3863 Check\_Confirmation see clause 25.2.2. + +3864 Process MT\_SM\_GMSC sheet 1: If the MAP\_SEND\_ROUTING\_INFO\_FOR\_SM confirmation included an LMSI, it +3865 shall be included in the sm-RP-DA information field of the first MAP\_MT\_FORWARD\_SHORT\_MESSAGE request +3866 sent to the serving MSC. In this case, the IMSI shall be included in the Destination Reference of the MAP\_OPEN +3867 request. The SMS-GMSC shall not send an LMSI to an SGSN. If the SMS-GMSC does not send an LMSI to the +3868 serving node, the sm-RP-DA information field in the first MAP\_MT\_FORWARD\_SHORT\_MESSAGE request sent to +3869 the serving MSC or SGSN shall contain the IMSI, and the Destination Reference in the MAP\_OPEN request shall not +3870 be present. The parameter SM\_RP\_OA shall contain the Service Centre address. + +3871 Process MT\_SM\_GMSC sheet 1: The indication of which number belongs to the SGSN and which to the MSC, +3872 received from the HLR in the MAP\_SEND\_ROUTING\_INFO\_FOR\_SM confirm (see clause 23.3.2) will enable the +3873 SMS-GMSC to map the causes received from one or both serving nodes into the appropriate causes for non GPRS, +3874 GPRS or both, and send them to the SC and the HLR. + +3875 Process MT\_SM\_GMSC sheet 2: The SMS-GMSC maps "Unexpected data value" and "System failure" MAP errors +3876 from the serving node to a "System failure" RP\_ERROR error cause. The mapping between other MAP error causes +3877 and the RP\_ERROR error cause is given in 3GPP TS 23.040 [26] and 3GPP TS 24.011 [37]. + +3878 Process MT\_SM\_GMSC sheet 2: If the SMS-GMSC receives both MSC and SGSN numbers from the HLR as routeing +3879 information, it may choose which serving node to use for the first delivery attempt. + +3880 Process MT\_SM\_GMSC sheet 2: If the SMS-GMSC makes two delivery attempts, it may report the result of each +3881 delivery attempt to the HLR according to the conditions described below. + +3882 Procedure MT\_SM\_Delivery\_Attempt\_GMSC sheet 1: if the macro MT\_SM\_Transfer\_MSC takes the Error exit, the +3883 SMS-GMSC maps the MAP User Error to the corresponding SC\_RP error, as defined in 3GPP TS 23.040 [26]. + +3884 Procedure MT\_SM\_Delivery\_Attempt\_GMSC sheet 3: The decision box "TCAP Handshake required" takes the "yes" +3885 or "no" exit depending on agreements between the GMSC's operator and the serving node's operator (see 3GPP TS +3886 33.204 [34a]). + +Procedure MT\_SM\_Delivery\_Attempt\_GMSC sheet 1, sheet 2, sheet 4, sheet 5: The SMS-GMSC invokes the macro +Report\_SM\_Delivery\_Stat\_GMSC if: + +- 3887 - the reason received from the serving node for failure to deliver the message is absent subscriber\_SM, +3888 unidentified subscriber or SM delivery failure with error cause "MS memory capacity exceeded", and the SC +3889 address is not yet included in the MWD set, or +- 3890 - the reason received from the serving node for failure to deliver the message is absent subscriber\_SM, +3891 unidentified subscriber or SM delivery failure with error cause MS memory capacity exceeded, and the +3892 corresponding flag in the HLR (as indicated in the information received in the MAP\_INFORM\_ +3893 SERVICE\_CENTRE) is not set, or +- 3894 - the reason received from the serving node (MSC or SGSN) for failure to deliver the message is absent +3895 subscriber\_SM and the absent subscriber diagnostic is different from the absent subscriber diagnostic received in +3896 the MAP\_INFORM\_SERVICE\_CENTRE. + +Procedure MT\_SM\_Delivery\_Attempt\_GMSC sheet 1, sheet 2, sheet 4, sheet 5: If absent subscriber diagnostic +information (see 3GPP TS 23.040 [26]) is included with the absent subscriber\_SM error indication then the SMS- +GMSC relays this information to the HLR using the MAP\_REPORT\_SM\_DELIVERY\_STATUS service. + +3897 Procedure MT\_SM\_Delivery\_Attempt\_GMSC sheet 1, sheet 4: The More Messages To Send flag is set to TRUE or +3898 FALSE according to the information received from the Service Centre. + +3899 Procedure MT\_SM\_Delivery\_Attempt\_GMSC sheet 3: If the capacity of a message signal unit in the lower layers of +3900 the protocol is enough to carry the content of the MAP\_OPEN request and the content of the +3901 MAP\_MT\_FORWARD\_SHORT\_MESSAGE request in a single TC message, the test "Message segmentation needed" +3902 takes the "No" exit; otherwise the test takes the "Yes" exit. + +3903 The mobile terminated short message transfer process in the SMS-GMSC is shown in figure 23.3/3. The procedure +3904 MT\_SM\_Delivery\_Attempt\_GMSC is shown in figure 23.3/4. The macro MT\_SM\_Transfer\_MSC is shown in +3905 figure 23.3/7. + +3906 The SMS-GMSC may include the Maximum Retransmission Time IE in the MT Forward Short Message Request to +3907 indicate that it is capable to retransmit the Short Message until the indicated maximum retransmission time, if the +3908 following conditions are fulfilled: + +- 3909 - the destination user pertains to the PLMN of the SMS-GMSC; and +- 3910 - if an SMS Router is used for MT SMS sent to destination users pertaining to the PLMN of the SMS-GMSC, the +3911 SMS Router is known to support the Alert Service Centre procedure specified in clause 12.5. + +3912 The SMS-GMSC shall include its E.164 number in the SMS-GMSC address and, if available its Diameter Identity in +3913 the SMS-GMSC Diameter Address in the request if it also includes the Maximum-Retransmission-Time IE. + +3914 If subsequently, the SMS-GMSC receives an Alert Service Centre request from an MME (via an IWF), SGSN or MSC, +3915 the SMS-GMSC shall retransmit pending MT SMS(s) for the destination user identified by the User Identifier Alert, to +3916 the same serving node if the SMS-GMSC Alert Event indicates that the MS is available for MT SMS, or to the new +3917 serving node if the SMS-GMSC Alert Event indicates that the MS has moved under the coverage of another MME, +3918 SGSN or MSC. In the latter case, if neither New MSC Number, nor New SGSN Number, nor New SGSN Diameter +3919 Address, nor New MME Number, nor New MME Diameter Address are received in the Alert Service Centre request, +3920 the SMS-GMSC shall initiate a Send Routing Info for SM procedure to retrieve the new serving node's address from +3921 the HLR. + +## 3922 23.3.2 Procedure in the HLR + +3923 The process starts when the HLR receives a MAP\_SEND\_ROUTING\_INFO\_FOR\_SM indication from the SMS- +3924 GMSC. If an SMS Router is deployed, the HLR receives MAP\_SEND\_ROUTING\_INFO\_FOR\_SM from the +3925 SMS Router (step 4 in figure 23.3/2a); relaying a message received from the SMS-GMSC to the SMS Router on SCCP +3926 level (steps 2 and 3 in figure 23.3/2a) is done by implementation specific means and is not shown in figure 23.3/5. + +3927 The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +3928     Check\_Indication       see clause 25.2.1. + +3929 Sheet 1: The decision box "Relay to IP-SM-GW" takes the "yes" exit if an IP-SM-GW is deployed and the message was +3930 not received from an IP-SM-GW. + +3931 Sheet 3: If the SMS-GMSC does not support GPRS functionality, it uses the protocol defined in the Release 96 version +3932 of this specification. The parameter "msc-Number" in "RoutingInfoForSM-Res" in the Release 96 version of the +3933 protocol definition corresponds to the parameter "networkNode-Number" in "RoutingInfoForSM-Res" in the Release 97 +3934 (and later) version of the protocol definition; therefore if the HLR populates the parameter "networkNode-Number" +3935 with the SGSN number, the Release 96 SMS-GMSC will interpret the SGSN number as an MSC number. If the HLR +3936 populates the "gprsNodeIndicator" parameter in the MAP\_SEND\_ROUTING\_INFO\_FOR\_SM response, a Release 96 +3937 SMS-GMSC will silently discard the parameter. + +3938 Sheet 5: If the HLR received a LMSI from the VLR at location updating, it shall include the LMSI in the +3939 MAP\_SEND\_ROUTING\_INFO\_FOR\_SM response only if the MAP\_SEND\_ROUTING\_INFO\_FOR\_SM response +3940 also includes the MSC number. + +3941 The mobile terminated short message transfer process in the HLR is shown in figure 23.3/5. + +## 3942 23.3.3 Procedure in the Serving MSC + +3943 Any CAMEL-specific handling defined in this clause is omitted if the MSC does not support CAMEL control of MT +3944 SMS, or if the subscriber does not have a subscription for CAMEL control of MT SMS. + +3945 The process starts when the MSC receives a dialogue opening request with the application context shortMsgMT- +3946 RelayContext. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found +3947 as follows: + +3948     Receive\_Open\_Ind       see clause 25.1.1; + +3949     Check\_Indication       see clause 25.2.1. + +3950 The mobile terminated short message transfer process in the serving MSC is shown in figure 23.3/6 + +3951 Procedure MT\_SM\_VMSC sheet 1: The decision box "TCAP Handshake required" takes the "yes" or "no" exit +3952 depending on agreements between the Serving MSC's operator and the SMS Gateway MSC's operator (see 3GPP TS +3953 33.204 [34a]). + +3954 The macro MT\_SM\_Transfer\_MSC may be invoked either in a stand-alone serving MSC or in a serving MSC which is +3955 integrated with the SMS-GMSC. It is used to transfer the first MT short message of a possible sequence of messages. +3956 The macro invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +3957     Check\_Confirmation     see clause 25.2.2. + +3958     Page\_MSC             see clause 25.3.1; + +3959     Search\_for\_MS\_MSC    see clause 25.3.2; + +3960     Process\_Access\_Request\_MSC see clause 25.4.1; + +3961     Trace\_Subscriber\_Activity\_MSC see clause 25.9.1. + +3962 The macro MT\_SM\_Transfer\_MSC is shown in figure 23.3/7. The macro Check\_Subscr\_Identity\_For\_MT\_SMS is +3963 shown in figure 23.3/8. + +3964 3GPP TS 29.118 [152] specifies the extensions applicable to the MT SMS procedure over SGs for a UE using extended +3965 idle mode DRX (as defined in 3GPP TS 23.682 [148]). + +3966 If the MS is using a power saving mechanism such as extended idle mode DRX (see 3GPP TS 23.682 [148]), and if the +3967 MT Forward Short Message Request includes the Maximum Retransmission Time IE, an MSC using Deployment +3968 Option 2 (see clause 8.2.4a.1 of 3GPP TS 23.272 [143] and 3GPP TS 23.040 [6]) may return an MT Forward Short +3969 Message Response with the User Error set to Absent Subscriber\_SM and with the Requested-Retransmission-Time IE +3970 requesting the SMS-GMSC to retransmit the Short Message at a later time prior to the Maximum Retransmission Time. +3971 In that case, the MSC shall store (if not already done) the SMS-GMSC address and, if available, the SMS-GMSC +3972 Diameter Identity received in the request and shall not set the MNRF flag. + +3973 NOTE: This mechanism does not cause additional signalling at the HSS to retransmit the Short Message. + +3974 An MSC using Deployment Option 2 (see clause 8.2.4a.1 of 3GPP TS 23.272 [143] and 3GPP TS 23.040 [6]) shall +3975 initiate the MAP Service Center Alert procedure to alert the SMS-GMSC when the UE, for which one or more MT +3976 SMS have been requested to be retransmitted at a later time, becomes available for MT SMS delivery or moves under +3977 the coverage of another MSC prior to the requested SM retransmission time. The MSC shall then delete the stored +3978 SMS-GMSC address after the Alert Service Centre procedure is completed. + +3979 + +### 3980 23.3.4 Procedure in the VLR + +3981 Any CAMEL-specific handling defined in this clause is omitted if the VLR does not support CAMEL control of MT +3982 SMS. + +3983 The process starts when the VLR receives a dialogue opening request from the MSC. The process invokes macros not +3984 defined in this clause; the definitions of these macros can be found as follows: + +3985     Receive\_Open\_Ind       see clause 25.1.1; + +3986     Check\_Indication       see clause 25.2.1; + +3987     Check\_Confirmation    see clause 25.2.2; + +3988     Process\_Access\_Request\_VLR see clause 25.4.2. + +3989 The mobile terminated short message transfer process in the VLR is shown in figure 23.3/9. + +3990 If the VLR has no IMSI record, or if the record is marked "Subscriber Data Not Confirmed by HLR", the VLR may +3991 perform the data restoration procedure as specified in clause 4.2.2 in 3GPP TS 23.007 [19]. + +### 3992 23.3.5 Procedure in the SGSN + +3993 Any CAMEL-specific handling defined in this clause is omitted if the SGSN does not support CAMEL control of MT +3994 SMS, or if the subscriber does not have a subscription for CAMEL control of MT SMS. + +3995 The process starts when the SGSN receives a dialogue opening request with the application context shortMsgMT- +3996 RelayContext. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found +3997 as follows: + +3998     Receive\_Open\_Ind       see clause 25.1.1; + +3999     Check\_Indication       see clause 25.2.1. + +4000 The mobile terminated short message transfer process in the SGSN is shown in figure 23.3/10. + +4001 Procedure MT\_SM\_SGSN sheet 1: The decision box "TCAP Handshake required" takes the "yes" or "no" exit +4002 depending on agreements between the Serving SGSN's operator and the SMS Gateway MSC's operator (see 3GPP TS +4003 33.204 [34a]). + +4004 The macro MT\_SM\_Transfer\_SGSN is used to transfer the first MT short message of a possible sequence of messages. +4005 It is shown in figure 23.3/11. + +4006 If the MS is using extended idle mode DRX (as defined in 3GPP TS 23.682 [148]) and the MS is expected to respond to +4007 paging shortly or within the time frame indicated by the SM-Delivery-Timer and SM-Delivery-Start-Time IEs, the +4008 SGSN should page the MS and attempt to deliver the short message to the MS. + +4009 If the MS is using extended idle mode DRX (as defined in 3GPP TS 23.682 [148]) and the MS is expected to not +4010 respond to paging shortly or within the time frame indicated by the SM-Delivery-Timer and SM-Delivery-Start-Time +4011 IEs, the SGSN may behave as specified in figure 23.3/11 for an MS that is not reachable, i.e. set the MNRG flag and +4012 return an Absent Subscriber Error to the SMS-GMSC, while still paging the MS. + +4013 NOTE 1: This mechanism is not intended for MSs which are known to wake up shortly (e.g. within the next 10 +4014 seconds) as enough time needs to elapse, between the sending of the MT Forward Short Message +4015 Response and the subsequent Ready For SM procedure towards the HLR when the MS becomes +4016 reachable, for the Report SM Delivery Status procedure to take place beforehand from the SMS-GMSC to +4017 the HLR. + +4018 If the MS is using a power saving mechanism such as extended idle mode DRX (see 3GPP TS 23.682 [148]), and if the +4019 MT Forward Short Message Request includes the Maximum Retransmission Time IE, the SGSN may return an MT +4020 Forward Short Message Response with the User Error set to Absent Subscriber\_SM and with the Requested- +4021 Retransmission-Time IE requesting the SMS-GMSC to retransmit the Short Message at a later time prior to the +4022 Maximum Retransmission Time. In that case, the SGSN shall store (if not already done) the SMS-GMSC address and, +4023 if available, the SMS-GMSC Diameter Identity received in the request and shall not set the MNRG flag. + +4024 NOTE 2: This mechanism does not cause additional signalling at the HSS to retransmit the Short Message. + +4025 The SGSN shall initiate the MAP Service Center Alert procedure to alert the SMS-GMSC when the UE, for which one +4026 or more MT SMS have been requested to be retransmitted at a later time, becomes available for MT SMS delivery or +4027 moves under the coverage of another MME or SGSN prior to the requested SM retransmission time. The SGSN shall +4028 then delete the stored SMS-GMSC address after the Alert Service Centre procedure is completed. + +4029 The macro Check\_Subscr\_Identity\_For\_MT\_SMS is shown in figure 23.3/8. The page and search procedures are +4030 shown in figures 23.3/12 and 23.3/13. + +### 4031 23.3.6 Procedure in the SMS Router + +4032 If SMS Router is deployed together with IP-SM-GW, then mobile terminated short message transfer process for IP-SM- +4033 GW applies as described in clause 23.3.7. + +4034 The mobile terminated short message transfer process in the SMS Router is shown in figure 23.3/14. + +4035 Procedure MT\_SM\_SMS\_ROUTER sheet 2: Allocated MT Correlation IDs have a limited lifetime, managed by Timer +4036 T1. The value of Timer T1 shall be operator configurable (its value being dependant on such factors as subscriber base, +4037 network size, number of roaming/SMS-interworking partners, average and peak SMS traffic load, etc.). + +4038 The value of the timer T1 shall cover at least the time indicated by the SM Delivery Start Time and SM Delivery Timer +4039 and, if the SMS Router support the Alert Service Centre procedure specified in clause 12.5, the Maximum +4040 Retransmission Time signalled in the MAP-MT-FORWARD-SHORT-MESSAGE. + +4041 Procedure MT\_SM\_SMS\_ROUTER sheet 2: MAP parameters to be stored against the MT Correlation ID are IMSI, +4042 networkNode-Number, gprsNodeIndicator, and additional-Number (if and as received within +4043 MAP\_SEND\_ROUTING\_INFO\_FOR\_SHORT\_MESSAGE\_cnf), and optionally MSISDN as received within +4044 MAP\_SEND\_ROUTING\_INFO\_FOR\_SHORT\_MESSAGE\_ind from the SMS-GMSC (and relayed by the HLR). +4045 The SMS Router may also store the GT, or just the CC and NDC parts of the GT, of the SMS-GMSC from which the +4046 MAP\_SEND\_ROUTING\_INFO\_FOR\_SHORT\_MESSAGE\_ind was received. + +4047 Procedure MT\_SM\_SMS\_ROUTER sheet 3: The SCCP called party SSN received with Open\_ind is used to decide +4048 whether the new dialogue is opened with the MSC or with the SGSN. + +4049 The detail of replacing RP-OA is described in TS23.040 [26]. + +4050 Procedure MT\_SM\_SMS\_ROUTER sheet 4: The decision box "Retry expected" takes the "Yes" exit if two addresses +4051 were received from the HLR, the first delivery attempt was unsuccessful, and the second attempt has not yet been made. + +4052 Procedure MT\_SM\_SMS\_ROUTER sheet 4: The task "Release MT Correlation ID" includes deleting of data stored +4053 against the MT Correlation ID. + +4054 If the MT Forward Short Message Request includes the Maximum-Retransmission-Time IE, the SMS Router shall store +4055 the SMS-GMSC address and, if available, the SMS-GMSC Diameter Identity received in the request and replace it by +4056 its SMS Router address (E.164 number) and, if available, its SMS Router Diameter Identity when forwarding the +4057 request to the MME (via an IFW), SGSN or MSC. + +4058 If the MT Forward Short Message Response includes the Requested-Retransmission-Time IE, the SMS Router shall +4059 include the User Identifier Alert IE when forwarding the response to the SMS-GMSC. + +4060 NOTE: The User Identifier Alert is further used in the Alert Service Centre procedure specified in clause 12.5 to +4061 enable the SMS-GMSC to identify and retransmit all pending MT SMS messages towards the destination +4062 user. + +4063 When receiving an Alert Service Centre request from an MME (via an IWF), SGSN or MSC, the SMS-Router shall +4064 replace the IMSI received in the IMSI IE by the User Identifier Alert previously sent in the MT Forward Short Message +4065 Response, and forward that request to the SMS-GMSC. + +### 4066 23.3.7 Procedure in the IP-SM-GW + +4067 Process MT\_SM\_IPSMGW sheet 3: After unsuccessful delivery via the S-CSCF the IP-SM-GW may retry delivery via +4068 MSC and/or SGSN if MSC address and/or SGSN address are available (unless the reported error was "memory capacity +4069 exceeded" in which case a retry shall not be done). If the retry is successful, a positive response is returned to the SMS- +4070 GMSC. If the retry is unsuccessful, an error indication is returned to the SMS-GMSC as follows: +4071 If one of the error indications received from S-CSCF, MSC, or SGSN is AbsentSubscriberSM or +4072 UnidentifiedSubscriber, this error shall be returned to the SMS-GMSC. + +Process MT\_SM\_IPSMGW sheet 3: The IP-SM-GW invokes the macro Report\_SM\_Delivery\_Stat\_IPSMGW if: + +- 4073 - the reason for failure to deliver the message is absent subscriber\_SM, unidentified subscriber or SM delivery +4074 failure with error cause "MS memory capacity exceeded", and the SC address is not yet included in the MWD +4075 set, or +- 4076 - the reason for failure to deliver the message is absent subscriber\_SM, unidentified subscriber or SM delivery +4077 failure with error cause MS memory capacity exceeded, and the corresponding flag in the HLR (as indicated in +4078 the information received in the MAP\_INFORM\_SERVICE\_CENTRE) is not set, or +- 4079 - the reason for failure to deliver the message is absent subscriber\_SM and the absent subscriber diagnostic is +4080 different from the absent subscriber diagnostic received in the MAP\_INFORM\_SERVICE\_CENTRE. + +4081 + +4082 The mobile terminated short message transfer process in the IP-SM-GW is shown in figure 23.3/15. + +4083 + +![Flowchart for Process MT_SM_GMSC. It starts with a Null terminal, followed by an SC_RP_MT_DATA_ind signal. Then, MAP_OPEN_req, MAP_SEND_ROUTING_INFO_FOR_SM_req, and MAP_DELIMITER_req are sent. The process waits for a Receive_Open_Cnf. If OK, it goes to Wait_For_Routing_Info. If V1, it performs a MAP_V1 Dialogue and reaches connector 1. If Error, it goes to Set RP_CAUSE: System Failure. From Wait_For_Routing_Info, it handles SC_ABORT_ind, MAP_SEND_ROUTING_INFO_FOR_SM_cnf, MAP_NOTICE_ind, or MAP_U_ABORT_ind/MAP_P_ABORT_ind/MAP_CLOSE_ind. After Check Confirmation, if OK, it checks if LMSI is included in routing info. If Yes, it sets destination reference: IMSI and SM_RP_DA: LMSI. If No, it sets destination reference: not included and SM_RP_DA: IMSI. Both lead to Wait_For_INFORM_SC. If User Error, it sets RP_CAUSE. If Provider Error, Data Error, it goes to Set RP_CAUSE: System Failure, then SC_RP_ERROR_req, and finally Null.](6867d3c00b89576b972010f96477d70c_img.jpg) + +### Process MT\_SM\_GMSC + +MT\_SM\_GMSC1(2) + +Process in the SMS-GMSC to handle delivery of an MT short message + +Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the HLR + +``` + + graph TD + Start([Null]) --> SC_RP_MT_DATA_ind{SC_RP_MT_DATA_ind} + SC_RP_MT_DATA_ind --> MAP_Requests[MAP_OPEN_req +MAP_SEND_ROUTING_INFO_FOR_SM_req +MAP_DELIMITER_req] + MAP_Requests --> Receive_Open_Cnf[Receive_Open_Cnf] + Receive_Open_Cnf -- V1 --> Perform_MAP_V1[Perform_MAP_V1 Dialogue] + Perform_MAP_V1 --> 1((1)) + Receive_Open_Cnf -- OK --> Wait_For_Routing_Info[Wait_For_Routing_Info] + Receive_Open_Cnf -- Error --> Set_RP_CAUSE_System_Failure[Set RP_CAUSE: System Failure] + Wait_For_Routing_Info --> SC_ABORT_ind{SC_ABORT_ind} + Wait_For_Routing_Info --> MAP_SEND_ROUTING_INFO_FOR_SM_cnf{MAP_SEND_ROUTING_INFO_FOR_SM_cnf} + Wait_For_Routing_Info --> MAP_NOTICE_ind{MAP_NOTICE_ind} + Wait_For_Routing_Info --> MAP_U_ABORT_ind[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + SC_ABORT_ind --> MAP_U_ABORT_req[MAP_U_ABORT_req] + MAP_U_ABORT_req --> Null1([Null]) + MAP_SEND_ROUTING_INFO_FOR_SM_cnf --> Check_Confirmation[Check Confirmation] + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> Check_Confirmation + MAP_U_ABORT_ind --> Check_Confirmation + Check_Confirmation -- OK --> LMSI_included{LMSI included in routing info?} + Check_Confirmation -- User Error --> Set_RP_CAUSE[Set RP_CAUSE] + Check_Confirmation -- "Provider Error, Data Error" --> Set_RP_CAUSE_System_Failure + LMSI_included -- Yes --> Set_dest_ref_IMSI[Set destination reference: IMSI] + Set_dest_ref_IMSI --> Set_SM_RP_DA_LMSI[Set SM_RP_DA: LMSI] + LMSI_included -- No --> Set_dest_ref_not_included[Set destination reference: not included] + Set_dest_ref_not_included --> Set_SM_RP_DA_IMSI[Set SM_RP_DA: IMSI] + Set_SM_RP_DA_LMSI --> Wait_For_INFORM_SC[Wait_For_INFORM_SC] + Set_SM_RP_DA_IMSI --> Wait_For_INFORM_SC + Set_RP_CAUSE --> Wait_For_INFORM_SC + Set_RP_CAUSE_System_Failure --> SC_RP_ERROR_req[SC_RP_ERROR_req] + SC_RP_ERROR_req --> Null2([Null]) + +``` + +Flowchart for Process MT\_SM\_GMSC. It starts with a Null terminal, followed by an SC\_RP\_MT\_DATA\_ind signal. Then, MAP\_OPEN\_req, MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_req, and MAP\_DELIMITER\_req are sent. The process waits for a Receive\_Open\_Cnf. If OK, it goes to Wait\_For\_Routing\_Info. If V1, it performs a MAP\_V1 Dialogue and reaches connector 1. If Error, it goes to Set RP\_CAUSE: System Failure. From Wait\_For\_Routing\_Info, it handles SC\_ABORT\_ind, MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_cnf, MAP\_NOTICE\_ind, or MAP\_U\_ABORT\_ind/MAP\_P\_ABORT\_ind/MAP\_CLOSE\_ind. After Check Confirmation, if OK, it checks if LMSI is included in routing info. If Yes, it sets destination reference: IMSI and SM\_RP\_DA: LMSI. If No, it sets destination reference: not included and SM\_RP\_DA: IMSI. Both lead to Wait\_For\_INFORM\_SC. If User Error, it sets RP\_CAUSE. If Provider Error, Data Error, it goes to Set RP\_CAUSE: System Failure, then SC\_RP\_ERROR\_req, and finally Null. + +4084 + +4085 + +Figure 23.3/3 (sheet 1 of 2): Process MT\_SM\_GMSC + +![Flowchart for Process MT_SM_GMSC. It starts with a connector '1' leading to 'MAP_CLOSE_ind'. From there, it branches into 'MAP_INFORM_SERVICE_Centre_ind' (leading to 'Check_Indication'), 'MAP_NOTICE_ind' (leading to 'MAP_CLOSE_req'), and 'SC_ABORT_ind' (leading to 'MAP_U_ABORT_req' and then 'Null'). 'Check_Indication' leads to 'Error from HLR?' (OK/Error paths). 'Error from HLR?' (Yes) leads to 'Set RP_IMSI; Set RP_MSISDN' and then 'SC_RP_ERROR_req' (leading to 'Null'). 'Error from HLR?' (No) leads to 'Routing info received?'. 'Routing info received?' (Yes) leads to 'MT_SM_Delivery_Attempt_GMSC' and then 'Result?'. 'Result?' (Fail) leads to 'Null'. 'Result?' (Pass, Abort) leads to 'Second routing address provided?'. 'Second routing address provided?' (Yes) leads to another 'MT_SM_Delivery_Attempt_GMSC' block, which then leads to 'Null'. 'Second routing address provided?' (No) leads to 'Null'. 'Routing info received?' (No) leads to 'Null'.](058e1c4e97c83889f2e61dcdd201982f_img.jpg) + +### Process MT\_SM\_GMSC + +### MT\_SM\_GMSC2(2) + +Process in the SMS-GMSC to handle delivery of an MT short message + +Signals to/from the left are to/from the short message service centre; +signals to/from the right are to/from the HLR + +``` + +graph TD + 1((1)) --> MAP_CLOSE_ind[/MAP_CLOSE_ind/] + MAP_CLOSE_ind --> MAP_INFORM_SERVICE_Centre_ind[/MAP_INFORM_SERVICE_Centre_ind/] + MAP_INFORM_SERVICE_Centre_ind --> Check_Indication[Check_Indication] + Check_Indication -- OK --> MAP_NOTICE_ind[/MAP_NOTICE_ind/] + Check_Indication -- Error --> MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req[/MAP_CLOSE_req/] + MAP_CLOSE_req --> Error_from_HLR{Error from HLR?} + Error_from_HLR -- Yes --> Set_RP[Set RP_IMSI; Set RP_MSISDN] + Set_RP --> SC_RP_ERROR_req[/SC_RP_ERROR_req/] + SC_RP_ERROR_req --> Null1([Null]) + Error_from_HLR -- No --> Routing_info{Routing info received?} + Routing_info -- Yes --> MT_SM_Delivery_Attempt_GMSC1[MT_SM_Delivery_Attempt_GMSC] + MT_SM_Delivery_Attempt_GMSC1 --> Result{Result?} + Result -- Fail --> Null2([Null]) + Result -- "Pass, Abort" --> Second_routing{Second routing address provided?} + Second_routing -- Yes --> MT_SM_Delivery_Attempt_GMSC2[MT_SM_Delivery_Attempt_GMSC] + MT_SM_Delivery_Attempt_GMSC2 --> Null3([Null]) + Second_routing -- No --> Null4([Null]) + Routing_info -- No --> Null5([Null]) + MAP_NOTICE_ind --> SC_ABORT_ind[/SC_ABORT_ind/] + SC_ABORT_ind --> MAP_U_ABORT_req[/MAP_U_ABORT_req/] + MAP_U_ABORT_req --> Null6([Null]) + +``` + +Flowchart for Process MT\_SM\_GMSC. It starts with a connector '1' leading to 'MAP\_CLOSE\_ind'. From there, it branches into 'MAP\_INFORM\_SERVICE\_Centre\_ind' (leading to 'Check\_Indication'), 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req'), and 'SC\_ABORT\_ind' (leading to 'MAP\_U\_ABORT\_req' and then 'Null'). 'Check\_Indication' leads to 'Error from HLR?' (OK/Error paths). 'Error from HLR?' (Yes) leads to 'Set RP\_IMSI; Set RP\_MSISDN' and then 'SC\_RP\_ERROR\_req' (leading to 'Null'). 'Error from HLR?' (No) leads to 'Routing info received?'. 'Routing info received?' (Yes) leads to 'MT\_SM\_Delivery\_Attempt\_GMSC' and then 'Result?'. 'Result?' (Fail) leads to 'Null'. 'Result?' (Pass, Abort) leads to 'Second routing address provided?'. 'Second routing address provided?' (Yes) leads to another 'MT\_SM\_Delivery\_Attempt\_GMSC' block, which then leads to 'Null'. 'Second routing address provided?' (No) leads to 'Null'. 'Routing info received?' (No) leads to 'Null'. + +4086 + +4087 + +Figure 23.3/3 (sheet 2 of 2): Process MT\_SM\_GMSC + +Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +MTSMDA1(8) + +Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcome + +Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the BSS + +![Flowchart for Procedure MT_SM_Delivery_Attempt_GMSC. It starts with a decision 'Serving node = GMSC?'. If 'No', it goes to connector '1'. If 'Yes', it calls 'MT_SM_Transfer_MSC'. From there, it branches into 'Abort', 'OK', and 'Release SMS' paths. The 'OK' path leads to connector '2' and then to a 'Camel Handling' decision. Both 'Camel Handling' decisions lead to either 'CAMEL_T_SMS_FAILURE' (referencing TS 23.078) or 'CAMEL_T_SMS_DELIVERED' (referencing TS 23.078). The 'CAMEL_T_SMS_DELIVERED' path leads to a 'More messages to send?' decision. If 'Yes', it loops back to connector '2'. If 'No', it checks if 'MCEF or MNRF set in HLR?'. If 'Yes', it calls 'Report_SM_Delivery_Stat_GMSC' and then sends 'SC_RP_ACK_req' resulting in 'Result= Pass'. If 'No', it sends 'SC_RP_MT_DATA_ind'. From there, a 'Camel Handling' decision leads to 'CAMEL_T_SMS_INIT' (referencing TS 23.078), which then leads to a 'Result?' decision. If 'Release_SMS', it sends 'SC_ABORT_req' resulting in 'Result= Abort'. If 'Continue', it sends 'A_RP_MT_DATA_req' and then 'Wait_For_Subsequent_A_SM_CONFIRM'. The 'CAMEL_T_SMS_FAILURE' path from the first 'Camel Handling' leads to 'Result= Fail'. The 'CAMEL_T_SMS_FAILURE' path from the second 'Camel Handling' leads to an 'Error?' decision. If 'Else', it loops back to connector '2'. If 'Unidentified Subscriber', it sends 'Set UE: Absent Subscriber'. If 'MWD already set?' is 'Yes', it checks 'Failure cause= indication from HLR?'. If 'No', it sends 'Report_SM_Delivery_Stat_GMSC'. If 'Yes', it sends 'Set RP_ERROR'. Both lead to 'SC_RP_ERROR_req' resulting in 'Result= Fail'. If 'MWD already set?' is 'No', it loops back to connector '2'. Other notes include 'Absent Subscriber, MS Memory Capacity Exceeded' and 'See TS 23.078'.](169399d9ec7701f9c5583c95442c2ef5_img.jpg) + +Flowchart for Procedure MT\_SM\_Delivery\_Attempt\_GMSC. It starts with a decision 'Serving node = GMSC?'. If 'No', it goes to connector '1'. If 'Yes', it calls 'MT\_SM\_Transfer\_MSC'. From there, it branches into 'Abort', 'OK', and 'Release SMS' paths. The 'OK' path leads to connector '2' and then to a 'Camel Handling' decision. Both 'Camel Handling' decisions lead to either 'CAMEL\_T\_SMS\_FAILURE' (referencing TS 23.078) or 'CAMEL\_T\_SMS\_DELIVERED' (referencing TS 23.078). The 'CAMEL\_T\_SMS\_DELIVERED' path leads to a 'More messages to send?' decision. If 'Yes', it loops back to connector '2'. If 'No', it checks if 'MCEF or MNRF set in HLR?'. If 'Yes', it calls 'Report\_SM\_Delivery\_Stat\_GMSC' and then sends 'SC\_RP\_ACK\_req' resulting in 'Result= Pass'. If 'No', it sends 'SC\_RP\_MT\_DATA\_ind'. From there, a 'Camel Handling' decision leads to 'CAMEL\_T\_SMS\_INIT' (referencing TS 23.078), which then leads to a 'Result?' decision. If 'Release\_SMS', it sends 'SC\_ABORT\_req' resulting in 'Result= Abort'. If 'Continue', it sends 'A\_RP\_MT\_DATA\_req' and then 'Wait\_For\_Subsequent\_A\_SM\_CONFIRM'. The 'CAMEL\_T\_SMS\_FAILURE' path from the first 'Camel Handling' leads to 'Result= Fail'. The 'CAMEL\_T\_SMS\_FAILURE' path from the second 'Camel Handling' leads to an 'Error?' decision. If 'Else', it loops back to connector '2'. If 'Unidentified Subscriber', it sends 'Set UE: Absent Subscriber'. If 'MWD already set?' is 'Yes', it checks 'Failure cause= indication from HLR?'. If 'No', it sends 'Report\_SM\_Delivery\_Stat\_GMSC'. If 'Yes', it sends 'Set RP\_ERROR'. Both lead to 'SC\_RP\_ERROR\_req' resulting in 'Result= Fail'. If 'MWD already set?' is 'No', it loops back to connector '2'. Other notes include 'Absent Subscriber, MS Memory Capacity Exceeded' and 'See TS 23.078'. + +4088 + +4089 + +Figure 23.3/4 (sheet 1 of 8): Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +# Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +MTSMDA2(8) + +Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcome + +Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the BSS + +![Flowchart for Procedure MT_SM_Delivery_Attempt_GMSC. It starts with 'Wait For Subsequent A_SM_CONFIRM', then branches into 'A_RP_ERROR_ind' and 'A_RP_ACK_ind'. The 'A_RP_ERROR_ind' path leads to 'Camel Handling' (False/True), 'CAMEL_T_SMS_FAILURE' (See TS 23.078), 'Error?' (Else/MS Memory Capacity Exceeded), 'MWD already set?' (Yes/No), a decision diamond for 'Failure cause= indication from HLR?', 'Report_SM_Delivery_Stat_GMSC' (OK, Error), 'SC_ABORT_req', 'Result= Abort', and an end symbol. The 'A_RP_ACK_ind' path leads to 'Camel Handling' (False/True), 'CAMEL_T_SMS_DELIVERED' (See TS 23.078), and an end symbol labeled '2'.](cfea3ca54d33b18d2069ba64e3cedaa4_img.jpg) + +``` +graph TD; Start([Wait For Subsequent A_SM_CONFIRM]) --> A_RP_ERROR_ind{{A_RP_ERROR_ind}}; Start --> A_RP_ACK_ind{{A_RP_ACK_ind}}; A_RP_ERROR_ind -- False --> Camel_Handling_E{Camel Handling}; A_RP_ERROR_ind -- True --> CAMEL_T_SMS_FAILURE[["CAMEL_T_SMS_FAILURE"]]; CAMEL_T_SMS_FAILURE -.-> Note_E[See TS 23.078]; Camel_Handling_E -- True --> CAMEL_T_SMS_FAILURE; Camel_Handling_E -- False --> Error{Error?}; Error -- Else --> Report_SM_Delivery_Stat_GMSC[["Report_SM_Delivery_Stat_GMSC"]]; Error -- "MS Memory Capacity Exceeded" --> MWD_already_set{MWD already set?}; MWD_already_set -- No --> Decision{ }; MWD_already_set -- Yes --> Decision; Decision -- Yes --> Failure_cause[Failure cause= indication from HLR?]; Failure_cause --> Decision; Decision -- No --> Report_SM_Delivery_Stat_GMSC; Report_SM_Delivery_Stat_GMSC -- "OK, Error" --> SC_ABORT_req{{SC_ABORT_req}}; SC_ABORT_req --> Result_Abort[Result= Abort]; Result_Abort --> End_E((X)); A_RP_ACK_ind -- False --> Camel_Handling_A{Camel Handling}; A_RP_ACK_ind -- True --> CAMEL_T_SMS_DELIVERED[["CAMEL_T_SMS_DELIVERED"]]; CAMEL_T_SMS_DELIVERED -.-> Note_A[See TS 23.078]; Camel_Handling_A -- True --> CAMEL_T_SMS_DELIVERED; Camel_Handling_A -- False --> End_A((2)); +``` + +Flowchart for Procedure MT\_SM\_Delivery\_Attempt\_GMSC. It starts with 'Wait For Subsequent A\_SM\_CONFIRM', then branches into 'A\_RP\_ERROR\_ind' and 'A\_RP\_ACK\_ind'. The 'A\_RP\_ERROR\_ind' path leads to 'Camel Handling' (False/True), 'CAMEL\_T\_SMS\_FAILURE' (See TS 23.078), 'Error?' (Else/MS Memory Capacity Exceeded), 'MWD already set?' (Yes/No), a decision diamond for 'Failure cause= indication from HLR?', 'Report\_SM\_Delivery\_Stat\_GMSC' (OK, Error), 'SC\_ABORT\_req', 'Result= Abort', and an end symbol. The 'A\_RP\_ACK\_ind' path leads to 'Camel Handling' (False/True), 'CAMEL\_T\_SMS\_DELIVERED' (See TS 23.078), and an end symbol labeled '2'. + +Figure 23.3/4 (sheet 2 of 8): Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +MTSMDA3(8) + +Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcome + +Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the serving node (VMSC or SGSN) + +![Flowchart for Procedure MT_SM_Delivery_Attempt_GMSC. It starts with a connector '1', followed by a decision 'Message segmenting needed?'. If 'Yes', it goes to a process block with 'MAP_OPEN_req' and 'MAP_DELIMITER_req'. If 'No', it goes to a decision 'TCAP Handshake required?'. If 'Yes', it goes to a process block with 'MAP_OPEN_req', 'MAP_MT_FORWARD_SHORT_MESSAGE_req', and 'MAP_DELIMITER_req'. If 'No', it goes directly to 'Receive_Open_Cnf'. Both 'Receive_Open_Cnf' blocks lead to a decision 'Successful delivery?'. If 'Yes', 'Result:= Pass' and an end connector. If 'No', 'SC_RP_ERROR_req' leads to 'Set RP_ERROR: System Failure' and an end connector. If 'OK' from 'Receive_Open_Cnf', it goes to a process block with 'MAP_MT_FORWARD_SHORT_MESSAGE_req' and 'MAP_DELIMITER_req', then to 'Wait_For_First_MT_SMS_Confirm'.](97a02a1421ed287213fa80182159166b_img.jpg) + +``` + +graph TD + 1((1)) --> D1{Message segmenting needed?} + D1 -- Yes --> P1[MAP_OPEN_req +MAP_DELIMITER_req] + D1 -- No --> D2{TCAP Handshake required?} + D2 -- Yes --> P2[MAP_OPEN_req +MAP_MT_FORWARD_SHORT_MESSAGE_req +MAP_DELIMITER_req] + D2 -- No --> R1[Receive_Open_Cnf] + P1 --> R2[Receive_Open_Cnf] + R1 --> D3{Successful delivery?} + R2 --> D4{Successful delivery?} + D3 -- Yes --> RP1[Result:= Pass] + D3 -- No --> SC1[SC_RP_ERROR_req] + SC1 --> SF1[Set RP_ERROR: System Failure] + RP1 --> E1(( )) + SF1 --> E2(( )) + D4 -- Yes --> RP2[Result:= Pass] + D4 -- No --> SC2[SC_RP_ERROR_req] + SC2 --> SF2[Set RP_ERROR: System Failure] + RP2 --> E3(( )) + SF2 --> E4(( )) + R1 -- OK --> P3[MAP_MT_FORWARD_SHORT_MESSAGE_req +MAP_DELIMITER_req] + R2 -- OK --> P3 + P3 --> W1[Wait_For_First_MT_SMS_Confirm] + W1 --> E5(( )) + +``` + +Flowchart for Procedure MT\_SM\_Delivery\_Attempt\_GMSC. It starts with a connector '1', followed by a decision 'Message segmenting needed?'. If 'Yes', it goes to a process block with 'MAP\_OPEN\_req' and 'MAP\_DELIMITER\_req'. If 'No', it goes to a decision 'TCAP Handshake required?'. If 'Yes', it goes to a process block with 'MAP\_OPEN\_req', 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req', and 'MAP\_DELIMITER\_req'. If 'No', it goes directly to 'Receive\_Open\_Cnf'. Both 'Receive\_Open\_Cnf' blocks lead to a decision 'Successful delivery?'. If 'Yes', 'Result:= Pass' and an end connector. If 'No', 'SC\_RP\_ERROR\_req' leads to 'Set RP\_ERROR: System Failure' and an end connector. If 'OK' from 'Receive\_Open\_Cnf', it goes to a process block with 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req' and 'MAP\_DELIMITER\_req', then to 'Wait\_For\_First\_MT\_SMS\_Confirm'. + +4093 + +4094 + +Figure 23.3/4 (sheet 3 of 8): Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +![Flowchart for Procedure MT_SM_Delivery_Attempt_GMSC. It starts with 'Wait_For_First_MT_SMS_Confirm', followed by 'MAP_MT_FORWARD_SHORT_MESSAGE_cnf', 'Check_Confirmation', and then branches based on 'OK', 'User Error', or 'Provider Error/Data Error' outcomes.](11a7d67a5e1bb4b322c906c038b8482a_img.jpg) + +### Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +MTSMDA4(8) + +Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcome + +Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the serving node (VMSC or SGSN) unless shown otherwise + +``` + + graph TD + Start([Wait_For_First_MT_SMS_Confirm]) --> CNF[MAP_MT_FORWARD_SHORT_MESSAGE_cnf] + CNF --> CHECK[Check_Confirmation] + CHECK --> OK{OK} + OK -- Yes --> MORE[More messages to send?] + MORE -- No --> HLR{MCEF or MNRF set in HLR?} + HLR -- Yes --> STAT1[Report_SM_Delivery_Stat_GMSC] + STAT1 --> ACK1[SC_RP_ACK_req] + ACK1 --> WAIT1[Wait_For_More_Messages_Remote_Delivery] + WAIT1 --> IND[SC_RP_MT_DATA_ind] + IND --> REQ[MAP_MT_FORWARD_SHORT_MESSAGE_req MAP_DELIMITER_req] + REQ --> WAIT2[Wait_For_Subsequent_MT_SMS_Confirm] + MORE -- No --> HLR + HLR -- No --> STAT1 + OK -- User Error --> ERROR{Error?} + ERROR -- Unidentified Subscriber --> SET1[Set UE: Absent Subscriber] + SET1 --> MWD{MWD already set?} + MWD -- Yes --> VMSC{Failure cause from VMSC=indication from HLR?} + VMSC -- Yes --> STAT2[Report_SM_Delivery_Stat_GMSC] + VMSC -- No --> STAT2 + MWD -- No --> STAT2 + STAT2 --> OK2[OK, Error] + OK2 --> SET2[Set RP_ERROR] + SET2 --> REQ2[SC_RP_ERROR_req] + REQ2 --> FAIL1[Result= Fail] + FAIL1 --> END1(( )) + ERROR -- Else --> SET1 + OK -- Provider Error, Data Error --> SET3[Set RP_ERROR] + SET3 --> REQ3[SC_RP_ERROR_req] + REQ3 --> FAIL2[Result= Fail] + FAIL2 --> END2(( )) + SET1 -.-> NOTES[Absent Subscriber, MS Memory Capacity Exceeded] + +``` + +Flowchart for Procedure MT\_SM\_Delivery\_Attempt\_GMSC. It starts with 'Wait\_For\_First\_MT\_SMS\_Confirm', followed by 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_cnf', 'Check\_Confirmation', and then branches based on 'OK', 'User Error', or 'Provider Error/Data Error' outcomes. + +**Figure 23.3/4 (sheet 4 of 8): Procedure MT\_SM\_Delivery\_Attempt\_GMSC** + +Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +MTSMDA5(8) + +Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcome + +Signals to/from the left are to/from the short message service centre, signals to/from the right are to/from the serving node (VMSC or SGSN) + +![Flowchart for Procedure MT_SM_Delivery_Attempt_GMSC. The process starts with 'Wait_For_Subsequent_MT_SMS_Confirm', followed by 'MAP_MT_FORWARD_SHORT_MESSAGE_cnf', and 'Check_Confirmation'. It then branches based on 'Error?' (OK, User Error, Provider Error, Data Error). The 'Error?' decision leads to 'MS Memory Capacity Exceeded' if 'User Error'. From 'MS Memory Capacity Exceeded', it goes to 'MWD already set?'. If 'Yes', it goes to a decision diamond (Failure cause from VMSC=indication from HLR?). If 'No', it goes to 'Report_SM_Delivery_Stat_GMSC'. Both paths lead to 'SC_ABORT_req'. From the decision diamond, 'Yes' leads to 'Report_SM_Delivery_Stat_GMSC' and 'No' leads to 'SC_ABORT_req'. 'Report_SM_Delivery_Stat_GMSC' leads to 'SC_ABORT_req' (OK, Error). All 'SC_ABORT_req' paths lead to 'Result= Abort' and then to an exit symbol. The 'OK' path from 'Check_Confirmation' leads to connector '3'.](0d333f1ed20780e733957984b3ee1a76_img.jpg) + +``` + +graph TD + Start([Wait_For_Subsequent_MT_SMS_Confirm]) --> MAP[MAP_MT_FORWARD_SHORT_MESSAGE_cnf] + MAP --> Check[Check_Confirmation] + Check --> Error{Error?} + Error -- OK --> 3((3)) + Error -- User Error --> Memory{MS Memory Capacity Exceeded} + Memory --> MWD{MWD already set?} + MWD -- No --> Report[Report_SM_Delivery_Stat_GMSC] + MWD -- Yes --> Decision{Failure cause from VMSC=indication from HLR?} + Decision -- Yes --> Report + Decision -- No --> AbortReq1{SC_ABORT_req} + Report -- "OK, Error" --> AbortReq2{SC_ABORT_req} + AbortReq1 --> Result1[Result= Abort] + Result1 --> Exit1((X)) + AbortReq2 --> Result2[Result= Abort] + Result2 --> Exit2((X)) + Error -- "Provider Error, Data Error" --> AbortReq3{SC_ABORT_req} + AbortReq3 --> Result3[Result= Abort] + Result3 --> Exit3((X)) + +``` + +Flowchart for Procedure MT\_SM\_Delivery\_Attempt\_GMSC. The process starts with 'Wait\_For\_Subsequent\_MT\_SMS\_Confirm', followed by 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_cnf', and 'Check\_Confirmation'. It then branches based on 'Error?' (OK, User Error, Provider Error, Data Error). The 'Error?' decision leads to 'MS Memory Capacity Exceeded' if 'User Error'. From 'MS Memory Capacity Exceeded', it goes to 'MWD already set?'. If 'Yes', it goes to a decision diamond (Failure cause from VMSC=indication from HLR?). If 'No', it goes to 'Report\_SM\_Delivery\_Stat\_GMSC'. Both paths lead to 'SC\_ABORT\_req'. From the decision diamond, 'Yes' leads to 'Report\_SM\_Delivery\_Stat\_GMSC' and 'No' leads to 'SC\_ABORT\_req'. 'Report\_SM\_Delivery\_Stat\_GMSC' leads to 'SC\_ABORT\_req' (OK, Error). All 'SC\_ABORT\_req' paths lead to 'Result= Abort' and then to an exit symbol. The 'OK' path from 'Check\_Confirmation' leads to connector '3'. + +4098 + +4099 + +Figure 23.3/4 (sheet 5 of 8): Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +# Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +MTSMDA6(8) + +Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcome + +Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the serving node (VMSC or SGSN) unless shown otherwise + +![Flowchart for Procedure MT_SM_Delivery_Attempt_GMSC. The process starts with a 'Wait' state, followed by an 'SC_ABORT_ind' signal. A 'Camel Handling' decision follows. If 'True', it triggers 'CAMEL_T_SMS_FAILURE' (referencing TS 23.078), then 'A_ABORT_req' to the BSS, and ends with 'Result= Abort'. If 'False', it proceeds to 'A_ABORT_req' to the BSS and ends with 'Result= Abort'. There are two parallel sub-processes starting from connectors. The left sub-process starts with 'Wait_For_First_A_SM_CONFIRM', followed by 'A_ABORT_ind' from the BSS. A 'Camel Handling' decision follows. If 'True', it triggers 'CAMEL_T_SMS_FAILURE' (referencing TS 23.078), then 'Set RP_ERROR: System Failure', 'SC_RP_ERROR_req', and ends with 'Result= Fail'. If 'False', it bypasses these steps and ends with 'Result= Fail'. The right sub-process starts with 'Wait_For_Subsequent_A_SM_CONFIRM', followed by 'A_ABORT_ind' from the BSS. A 'Camel Handling' decision follows. If 'True', it triggers 'CAMEL_T_SMS_FAILURE' (referencing TS 23.078), then 'SC_ABORT_req', and ends with 'Result= Abort'. If 'False', it bypasses these steps and ends with 'Result= Abort'.](f603beac63483f85d6922a3288fd781b_img.jpg) + +``` + +graph TD + Start([ ]) --> Wait1[Wait_For_First_A_SM_CONFIRM, Wait_For_Subsequent_A_SM_CONFIRM] + Wait1 --> SC_ABORT_ind1{SC_ABORT_ind} + SC_ABORT_ind1 -- False --> CamelHandling1{Camel Handling} + CamelHandling1 -- True --> CAMEL_T_SMS_FAILURE1[CAMEL_T_SMS_FAILURE] + CAMEL_T_SMS_FAILURE1 -.-> TS23078_1[See TS 23.078] + CamelHandling1 -- False --> A_ABORT_req1[A_ABORT_req] + A_ABORT_req1 -.-> ToBSS1[To BSS] + A_ABORT_req1 --> ResultAbort1[Result= Abort] + ResultAbort1 --> End1(( )) + + Start --> Wait2[Wait_For_First_A_SM_CONFIRM] + Wait2 --> A_ABORT_ind2{A_ABORT_ind} + A_ABORT_ind2 -.-> FromBSS2[From BSS] + A_ABORT_ind2 -- False --> CamelHandling2{Camel Handling} + CamelHandling2 -- True --> CAMEL_T_SMS_FAILURE2[CAMEL_T_SMS_FAILURE] + CAMEL_T_SMS_FAILURE2 -.-> TS23078_2[See TS 23.078] + CamelHandling2 -- False --> SetRPError[Set RP_ERROR: System Failure] + SetRPError --> SC_RP_ERROR_req[SC_RP_ERROR_req] + SC_RP_ERROR_req --> ResultFail[Result= Fail] + ResultFail --> End2(( )) + + Start --> Wait3[Wait_For_Subsequent_A_SM_CONFIRM] + Wait3 --> A_ABORT_ind3{A_ABORT_ind} + A_ABORT_ind3 -.-> FromBSS3[From BSS] + A_ABORT_ind3 -- False --> CamelHandling3{Camel Handling} + CamelHandling3 -- True --> CAMEL_T_SMS_FAILURE3[CAMEL_T_SMS_FAILURE] + CAMEL_T_SMS_FAILURE3 -.-> TS23078_3[See TS 23.078] + CamelHandling3 -- False --> SC_ABORT_req[SC_ABORT_req] + SC_ABORT_req --> ResultAbort3[Result= Abort] + ResultAbort3 --> End3(( )) + +``` + +Flowchart for Procedure MT\_SM\_Delivery\_Attempt\_GMSC. The process starts with a 'Wait' state, followed by an 'SC\_ABORT\_ind' signal. A 'Camel Handling' decision follows. If 'True', it triggers 'CAMEL\_T\_SMS\_FAILURE' (referencing TS 23.078), then 'A\_ABORT\_req' to the BSS, and ends with 'Result= Abort'. If 'False', it proceeds to 'A\_ABORT\_req' to the BSS and ends with 'Result= Abort'. There are two parallel sub-processes starting from connectors. The left sub-process starts with 'Wait\_For\_First\_A\_SM\_CONFIRM', followed by 'A\_ABORT\_ind' from the BSS. A 'Camel Handling' decision follows. If 'True', it triggers 'CAMEL\_T\_SMS\_FAILURE' (referencing TS 23.078), then 'Set RP\_ERROR: System Failure', 'SC\_RP\_ERROR\_req', and ends with 'Result= Fail'. If 'False', it bypasses these steps and ends with 'Result= Fail'. The right sub-process starts with 'Wait\_For\_Subsequent\_A\_SM\_CONFIRM', followed by 'A\_ABORT\_ind' from the BSS. A 'Camel Handling' decision follows. If 'True', it triggers 'CAMEL\_T\_SMS\_FAILURE' (referencing TS 23.078), then 'SC\_ABORT\_req', and ends with 'Result= Abort'. If 'False', it bypasses these steps and ends with 'Result= Abort'. + +4100 + +4101 + +Figure 23.3/4 (sheet 6 of 8): Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +# Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +MTSMDA7(8) + +Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcome + +Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the serving node (VMSC or SGSN) unless shown otherwise + +![Sequence diagram for Procedure MT_SM_Delivery_Attempt_GMSC. The diagram shows two main paths starting from a common entry point. The first path leads to an 'Abort' result via SC_ABORT_ind and MAP_U_ABORT_ind. The second path branches into two parallel sequences: 'Wait_For_First_MT_SMS_Confirm' and 'Wait_For_Subsequent_MT_SMS_Confirm'. Both parallel sequences involve MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_NOTICE_ind, and MAP_CLOSE_req signals. The 'Wait_For_First_MT_SMS_Confirm' path leads to 'Set RP_ERROR: System Failure', then SC_RP_ERROR_req, and finally a 'Fail' result. The 'Wait_For_Subsequent_MT_SMS_Confirm' path leads to SC_ABORT_req and finally an 'Abort' result. All paths end at a circular connector symbol.](53489512b29fbe1eecb47a56bb155fda_img.jpg) + +``` + +sequenceDiagram + participant SMSC as Short Message Service Centre + participant GMSC as SMS-GMSC + participant VMSC_SGSN as VMSC or SGSN + + Note right of SMSC: Wait_For_First_MT_SMS_Confirm, Wait_For_Subsequent_MT_SMS_Confirm + + SMSC->>GMSC: SC_ABORT_ind + GMSC->>SMSC: MAP_U_ABORT_ind + GMSC->>GMSC: Result= Abort + Note right of SMSC: Wait_For_Subsequent_MT_SMS_Confirm + + Note left of SMSC: Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the serving node (VMSC or SGSN) unless shown otherwise + + Note left of GMSC: Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcome + + GMSC->>SMSC: MAP_U_ABORT_ind, MAP_P_ABORT_ind + SMSC->>GMSC: MAP_NOTICE_ind + GMSC->>SMSC: MAP_CLOSE_req + + Note left of SMSC: Wait_For_First_MT_SMS_Confirm + Note right of SMSC: Wait_For_Subsequent_MT_SMS_Confirm + + Note left of GMSC: Set RP_ERROR: System Failure + GMSC->>SMSC: SC_RP_ERROR_req + GMSC->>GMSC: Result= Fail + + Note right of SMSC: Wait_For_Subsequent_MT_SMS_Confirm + GMSC->>SMSC: SC_ABORT_req + GMSC->>GMSC: Result= Abort + +``` + +Sequence diagram for Procedure MT\_SM\_Delivery\_Attempt\_GMSC. The diagram shows two main paths starting from a common entry point. The first path leads to an 'Abort' result via SC\_ABORT\_ind and MAP\_U\_ABORT\_ind. The second path branches into two parallel sequences: 'Wait\_For\_First\_MT\_SMS\_Confirm' and 'Wait\_For\_Subsequent\_MT\_SMS\_Confirm'. Both parallel sequences involve MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_NOTICE\_ind, and MAP\_CLOSE\_req signals. The 'Wait\_For\_First\_MT\_SMS\_Confirm' path leads to 'Set RP\_ERROR: System Failure', then SC\_RP\_ERROR\_req, and finally a 'Fail' result. The 'Wait\_For\_Subsequent\_MT\_SMS\_Confirm' path leads to SC\_ABORT\_req and finally an 'Abort' result. All paths end at a circular connector symbol. + +4102 + +4103 + +Figure 23.3/4 (sheet 7 of 8): Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +MTSMDA8(8) + +Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcome + +Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the serving node (VMSC or SGSN) unless shown otherwise + +![Flowchart for Procedure MT_SM_Delivery_Attempt_GMSC. The diagram is split into two main vertical paths. The top path starts with 'Wait_For_More_Messages_Local_Delivery' and branches into two abort scenarios: one triggered by 'SC_ABORT_ind' and another by 'A_ABORT_ind' (labeled 'From BSS'). Both lead through 'Camel Handling' (referencing TS 23.078) to 'Result= Abort'. The bottom path starts with 'Wait_For_More_Messages_Remote_Delivery' and branches into three scenarios: 'SC_ABORT_ind' leading to 'Result= Abort', a central path receiving 'MAP_U_ABORT_ind' and 'MAP_P_ABORT_ind' via 'SC_ABORT_req' leading to 'Result= Abort', and a right path receiving 'MAP_NOTICE_ind' and 'MAP_CLOSE_req' via 'SC_ABORT_req' leading to 'Result= Abort'.](362f3486dadd99f17896333a8d291ef6_img.jpg) + +``` + +graph TD + subgraph Local_Delivery + W1[Wait_For_More_Messages_Local_Delivery] --> SC1{SC_ABORT_ind} + W1 --> A1{A_ABORT_ind} + A1 -.-> FromBSS[From BSS] + SC1 -- False --> CH1{Camel Handling} + CH1 -- True --> C1[CAMEL_T_SMS_FAILURE] + C1 -.-> TS1[See TS 23.078] + CH1 -- False --> A1R[A_ABORT_req] + A1R -.-> ToBSS[To BSS] + A1R --> R1[Result= Abort] + R1 --> E1((X)) + A1 -- False --> CH2{Camel Handling} + CH2 -- True --> C2[CAMEL_T_SMS_FAILURE] + C2 -.-> TS2[See TS 23.078] + CH2 -- False --> SC1R[SC_ABORT_req] + SC1R --> R2[Result= Abort] + R2 --> E2((X)) + end + subgraph Remote_Delivery + W2[Wait_For_More_Messages_Remote_Delivery] --> SC2{SC_ABORT_ind} + W2 --> M[ ] + W2 --> MN[MAP_NOTICE_ind] + M --> MU[MAP_U_ABORT_ind, MAP_P_ABORT_ind] + MU --> SC3R[SC_ABORT_req] + SC3R --> R3[Result= Abort] + R3 --> E3((X)) + MN --> MC[MAP_CLOSE_req] + MC --> SC4R[SC_ABORT_req] + SC4R --> R4[Result= Abort] + R4 --> E4((X)) + SC2 --> MU2[MAP_U_ABORT_ind] + MU2 --> R5[Result= Abort] + R5 --> E5((X)) + end + style M fill:none,stroke:none + style MU fill:none,stroke:none + style MC fill:none,stroke:none + style MU2 fill:none,stroke:none + style SC1R fill:none,stroke:none + style SC3R fill:none,stroke:none + style SC4R fill:none,stroke:none + style R4 fill:none,stroke:none + style R5 fill:none,stroke:none + style E4 fill:none,stroke:none + style E5 fill:none,stroke:none + +``` + +Flowchart for Procedure MT\_SM\_Delivery\_Attempt\_GMSC. The diagram is split into two main vertical paths. The top path starts with 'Wait\_For\_More\_Messages\_Local\_Delivery' and branches into two abort scenarios: one triggered by 'SC\_ABORT\_ind' and another by 'A\_ABORT\_ind' (labeled 'From BSS'). Both lead through 'Camel Handling' (referencing TS 23.078) to 'Result= Abort'. The bottom path starts with 'Wait\_For\_More\_Messages\_Remote\_Delivery' and branches into three scenarios: 'SC\_ABORT\_ind' leading to 'Result= Abort', a central path receiving 'MAP\_U\_ABORT\_ind' and 'MAP\_P\_ABORT\_ind' via 'SC\_ABORT\_req' leading to 'Result= Abort', and a right path receiving 'MAP\_NOTICE\_ind' and 'MAP\_CLOSE\_req' via 'SC\_ABORT\_req' leading to 'Result= Abort'. + +4104 + +4105 + +Figure 23.3/4 (sheet 8 of 8): Procedure MT\_SM\_Delivery\_Attempt\_GMSC + +![A flowchart diagram representing the process MT_SM_HLR. The flow starts with an oval connector, followed by a rounded rectangle, a chevron shape, and a double-bordered rectangle. It then enters a loop of four diamond-shaped decision nodes. The first diamond has a self-loop and an exit path to the left. The second diamond has a self-loop and an exit path to the right. The third diamond has an exit path to the right. The fourth diamond has three exit paths to the bottom. The diagram includes various rectangular process blocks and ends with an 'X' symbol at the bottom left.](0a45b25b2693d2f26fbe2f70eb3fc705_img.jpg) + +A flowchart diagram representing the process MT\_SM\_HLR. The flow starts with an oval connector, followed by a rounded rectangle, a chevron shape, and a double-bordered rectangle. It then enters a loop of four diamond-shaped decision nodes. The first diamond has a self-loop and an exit path to the left. The second diamond has a self-loop and an exit path to the right. The third diamond has an exit path to the right. The fourth diamond has three exit paths to the bottom. The diagram includes various rectangular process blocks and ends with an 'X' symbol at the bottom left. + +4106 + +4107 + +**Figure 23.3/5 (sheet 1 of 6): Process MT\_SM\_HLR** + +![Flowchart for process MT_SM_HLR. It starts at node 2, checks if the MS is reachable in the MSC. If no, it goes to node 5. If yes, it checks if the MSC supports MT SMS. If no, it sets a user error 'Facility not supported' and goes to node 1. If yes, it checks if there is operator barring. If yes, it sets a user error 'Call barred' with cause 'Operator barring' and goes to node 1. If no, it checks if there is SS barring. If yes, it sets a user error 'Call barred' with cause 'Barring service active' and goes to node 1. If no, it checks if MNRF is set. If yes, it checks SM-RP priority. If SM-RP priority is true, it retrieves routing information, sets MW status, and goes to node 10. If SM-RP priority is false, it sets MNRF and goes to node 6. If MNRF is not set, it retrieves routing information and goes to node 11.](33449456be26bf6ac2d988e9db39ba2f_img.jpg) + +process MT\_SM\_HLR + +MT\_SM\_HLR2(6) + +Process in the HLR to provide routing information for MT SMS + +NAM=Non-GPRS + +``` + +graph TD + 2((2)) --> D1{MS reachable in MSC?} + D1 -- No --> 5((5)) + D1 -- Yes --> D2{MSC supports MT SMS?} + D2 -- No --> E1[Set User Error: Facility not supported] + E1 --> 1((1)) + D2 -- Yes --> D3{Operator barring?} + D3 -- Yes --> E2[Set User Error: Call barred] + E2 --> C1[Set Barring cause: Operator barring] + C1 --> 1 + D3 -- No --> D4{SS barring?} + D4 -- Yes --> E3[Set User Error: Call barred] + E3 --> C2[Set Barring cause: Barring service active] + C2 --> 1 + D4 -- No --> D5{MNRF set?} + D5 -- Yes --> D6{SM-RP priority?} + D6 -- True --> R1[Retrieve routing information] + R1 --> S1[Set MW status] + S1 --> 10((10)) + D6 -- False --> S2[Set MNRF] + S2 --> 6((6)) + D5 -- No --> R2[Retrieve routing information] + R2 --> 11((11)) + +``` + +Flowchart for process MT\_SM\_HLR. It starts at node 2, checks if the MS is reachable in the MSC. If no, it goes to node 5. If yes, it checks if the MSC supports MT SMS. If no, it sets a user error 'Facility not supported' and goes to node 1. If yes, it checks if there is operator barring. If yes, it sets a user error 'Call barred' with cause 'Operator barring' and goes to node 1. If no, it checks if there is SS barring. If yes, it sets a user error 'Call barred' with cause 'Barring service active' and goes to node 1. If no, it checks if MNRF is set. If yes, it checks SM-RP priority. If SM-RP priority is true, it retrieves routing information, sets MW status, and goes to node 10. If SM-RP priority is false, it sets MNRF and goes to node 6. If MNRF is not set, it retrieves routing information and goes to node 11. + +4108 + +4109 + +Figure 23.3/5 (sheet 2 of 6): Process MT\_SM\_HLR + +![Flowchart for process MT_SM_HLR. It starts at node 3, checks if MS is reachable in SGSN. If No, it goes to Set MNRG and then to node 9. If Yes, it checks if SGSN supports MT SMS. If No, it goes to node 7. If Yes, it checks if Operator barring. If Yes, it sets User Error: Call barred and Barring cause: Operator barring, then goes to node 1. If No, it checks if SS barring. If Yes, it sets User Error: Call barred and Barring cause: Barring service active, then goes to node 1. If No, it checks if MNRG set. If Yes, it checks SM-RP priority. If True, it retrieves routing information, sets MW status, and goes to node 10. If False, it goes to Set MNRG and then to node 9. If No, it retrieves routing information and goes to node 11.](2ce6b75ca6bbddbcc328c143363111aa_img.jpg) + +process MT\_SM\_HLR + +MT\_SM\_HLR3(6) + +Process in the HLR to provide routing information for MT SMS + +NAM=GPRS + +``` + +graph TD + 3((3)) --> D1{MS reachable in SGSN?} + D1 -- No --> SetMNRG[Set MNRG] + SetMNRG --> 9((9)) + D1 -- Yes --> D2{SGSN supports MT SMS?} + D2 -- No --> 7((7)) + D2 -- Yes --> D3{Operator barring?} + D3 -- Yes --> SetUE1[Set User Error: Call barred] + SetUE1 --> SetBC1[Set Barring cause: Operator barring] + SetBC1 --> 1((1)) + D3 -- No --> D4{SS barring?} + D4 -- Yes --> SetUE2[Set User Error: Call barred] + SetUE2 --> SetBC2[Set Barring cause: Barring service active] + SetBC2 --> 1 + D4 -- No --> D5{MNRG set?} + D5 -- Yes --> D6{SM-RP priority?} + D6 -- True --> RI1[Retrieve routing information] + RI1 --> SetMW[Set MW status] + SetMW --> 10((10)) + D6 -- False --> SetMNRG + D5 -- No --> RI2[Retrieve routing information] + RI2 --> 11((11)) + 8((8)) --> D3 + NAM[GPRS] -.-> 3 + Note[Process in the HLR to provide routing information for MT SMS] -.-> 3 + +``` + +Flowchart for process MT\_SM\_HLR. It starts at node 3, checks if MS is reachable in SGSN. If No, it goes to Set MNRG and then to node 9. If Yes, it checks if SGSN supports MT SMS. If No, it goes to node 7. If Yes, it checks if Operator barring. If Yes, it sets User Error: Call barred and Barring cause: Operator barring, then goes to node 1. If No, it checks if SS barring. If Yes, it sets User Error: Call barred and Barring cause: Barring service active, then goes to node 1. If No, it checks if MNRG set. If Yes, it checks SM-RP priority. If True, it retrieves routing information, sets MW status, and goes to node 10. If False, it goes to Set MNRG and then to node 9. If No, it retrieves routing information and goes to node 11. + +4110 + +4111 + +Figure 23.3/5 (sheet 3 of 6): Process MT\_SM\_HLR + +![Flowchart for process MT_SM_HLR. It starts at node 4 and checks if SMS-GMSC supports GPRS. If No, it goes to a 'Preferred delivery node' decision between MSC (node 2) and SGSN (node 3). If Yes, it checks if MS is reachable in MSC. If No, it checks if MS is reachable in SGSN. If No, node 7 leads to 'Set MNRF; Set MNRG' then node 9. If Yes, it checks if MSC supports MT SMS. If No, it checks if SGSN supports MT SMS. If No, 'Set User Error: Facility not supported' leads to node 1. If Yes, it checks if Operator barring? If Yes, 'Set User Error: Call barred' and 'Set Barring cause: Operator barring' lead to node 6. If No, it checks if SS barring? If Yes, 'Set User Error: Call barred' and 'Set Barring cause: Barring service active' lead to node 1. If No, it checks if MNRF set? If Yes, it checks if MNRG set? If Yes, it checks if SM-RP priority? If True, 'Set MSC address; Set SGSN address' leads to 'Retrieve routing information'. If False, 'Set SGSN address' leads to 'Retrieve routing information'. If No, it checks if SM-RP priority? If True, 'Set MSC address; Set SGSN address' leads to 'Retrieve routing information'. If False, 'Set MSC address' leads to 'Retrieve routing information'. If No, it checks if MNRG set? If Yes, 'Set MSC address; Set SGSN address' leads to node 11. If No, 'Set MSC address; Set SGSN address' leads to 'Retrieve routing information'. 'Retrieve routing information' leads to 'Set MW status' then node 10.](8717425dd6fafc72a992383b93f6118d_img.jpg) + +**process MT\_SM\_HLR** **MT\_SM\_HLR4(6)** + +Process in the HLR to provide routing information for MT SMS + +NAM=Non-GPRS & GPRS + +``` + +graph TD + 4((4)) --> D1{SMS-GMSC supports GPRS?} + D1 -- No --> PDN{Preferred delivery node} + PDN -- MSC --> 2((2)) + PDN -- SGSN --> 3((3)) + D1 -- Yes --> D2{MS reachable in MSC?} + D2 -- No --> D3{MS reachable in SGSN?} + D3 -- No --> 7((7)) + 7 --> S1[Set MNRF; Set MNRG] + S1 --> 9((9)) + D2 -- Yes --> D4{MS reachable in SGSN?} + D4 -- No --> 5((5)) + D4 -- Yes --> D5{MSC supports MT SMS?} + D5 -- No --> D6{SGSN supports MT SMS?} + D6 -- No --> S2[Set User Error: Facility not supported] + S2 --> 1((1)) + D6 -- Yes --> D7{Operator barring?} + D7 -- Yes --> S3[Set User Error: Call barred] + S3 --> S4[Set Barring cause: Operator barring] + S4 --> 6((6)) + D7 -- No --> D8{SS barring?} + D8 -- Yes --> S5[Set User Error: Call barred] + S5 --> S6[Set Barring cause: Barring service active] + S6 --> 1((1)) + D8 -- No --> D9{MNRF set?} + D9 -- Yes --> D10{MNRG set?} + D10 -- Yes --> D11{SM-RP priority?} + D11 -- True --> S7[Set MSC address; Set SGSN address] + D10 -- No --> D12{SM-RP priority?} + D12 -- False --> S8[Set SGSN address] + S7 --> RI[Retrieve routing information] + S8 --> RI + D9 -- No --> D13{MNRG set?} + D13 -- Yes --> D14{SM-RP priority?} + D14 -- True --> S9[Set MSC address; Set SGSN address] + D14 -- False --> S10[Set MSC address] + S9 --> RI + S10 --> RI + D13 -- No --> S11[Set MSC address; Set SGSN address] + S11 --> 11((11)) + RI --> S12[Set MW status] + S12 --> 10((10)) + +``` + +Flowchart for process MT\_SM\_HLR. It starts at node 4 and checks if SMS-GMSC supports GPRS. If No, it goes to a 'Preferred delivery node' decision between MSC (node 2) and SGSN (node 3). If Yes, it checks if MS is reachable in MSC. If No, it checks if MS is reachable in SGSN. If No, node 7 leads to 'Set MNRF; Set MNRG' then node 9. If Yes, it checks if MSC supports MT SMS. If No, it checks if SGSN supports MT SMS. If No, 'Set User Error: Facility not supported' leads to node 1. If Yes, it checks if Operator barring? If Yes, 'Set User Error: Call barred' and 'Set Barring cause: Operator barring' lead to node 6. If No, it checks if SS barring? If Yes, 'Set User Error: Call barred' and 'Set Barring cause: Barring service active' lead to node 1. If No, it checks if MNRF set? If Yes, it checks if MNRG set? If Yes, it checks if SM-RP priority? If True, 'Set MSC address; Set SGSN address' leads to 'Retrieve routing information'. If False, 'Set SGSN address' leads to 'Retrieve routing information'. If No, it checks if SM-RP priority? If True, 'Set MSC address; Set SGSN address' leads to 'Retrieve routing information'. If False, 'Set MSC address' leads to 'Retrieve routing information'. If No, it checks if MNRG set? If Yes, 'Set MSC address; Set SGSN address' leads to node 11. If No, 'Set MSC address; Set SGSN address' leads to 'Retrieve routing information'. 'Retrieve routing information' leads to 'Set MW status' then node 10. + +4112 + +4113 + +Figure 23.3/5 (sheet 4 of 6): Process MT\_SM\_HLR + +![Flowchart for process MT_SM_HLR. It starts with three entry points (9, 10, 11) leading to MAP_SEND_ROUTING_INFO_FOR_SM_rsp. Point 9 leads to a decision 'SC address in MWD list?'. If No, it goes to 'Update MWD list' then 'MWD update failed?'. If Yes, it goes to 'MWD status:= SC address included'. Point 10 leads to 'SC address in MWD list?'. If No, it goes to 'MWD status:= SC address not included'. If Yes, it goes to 'MWD status:= SC address included'. Point 11 leads to 'MCEF set?'. If No, it goes to 'MSISDN= MSISDN Alert?'. If Yes, it goes to 'Set MW status'. All status updates lead to 'MSISDN= MSISDN Alert?'. If No, it goes to 'Set MSISDN Alert' then 'MAP_INFORM_SERVICE_CENTRE_req MAP_CLOSE_req'. If Yes, it goes directly to 'MAP_INFORM_SERVICE_CENTRE_req MAP_CLOSE_req'. The 'MSISDN= MSISDN Alert?' decision from point 11 leads to 'Set MSISDN Alert' then 'MAP_INFORM_SERVICE_CENTRE_req' then 'MAP_CLOSE_req'. All final paths end with an 'X' mark.](f753096fee70af0f41b82a35ee0f13e1_img.jpg) + +**process MT\_SM\_HLR** **MT\_SM\_HLR5(6)** + +Process in the HLR to provide routing information for MT SMS + +Signals to the left are to the SMS-GMSC + +``` + +graph TD + 9((9)) --> R9[MAP_SEND_ROUTING_INFO_FOR_SM_rsp] + 10((10)) --> R10[MAP_SEND_ROUTING_INFO_FOR_SM_rsp] + 11((11)) --> R11[MAP_SEND_ROUTING_INFO_FOR_SM_rsp] + + R9 --> D9{SC address in MWD list?} + D9 -- Yes --> S9[MWD status:= SC address included] + D9 -- No --> U[Update MWD list] + U --> F{MWD update failed?} + F -- Yes --> N9[MWD status:= SC address not included] + F -- No --> S9 + + R10 --> D10{SC address in MWD list?} + D10 -- Yes --> S10[MWD status:= SC address included] + D10 -- No --> N10[MWD status:= SC address not included] + + R11 --> D11{MCEF set?} + D11 -- Yes --> S11[Set MW status] + D11 -- No --> A11{MSISDN= MSISDN Alert?} + + S9 --> A{MSISDN= MSISDN Alert?} + N9 --> A + S10 --> A + N10 --> A + S11 --> A + + A -- Yes --> I[MAP_INFORM_SERVICE_CENTRE_req +MAP_CLOSE_req] + A -- No --> AL[Set MSISDN Alert] + AL --> I + + A11 -- Yes --> C[MAP_CLOSE_req] + A11 -- No --> AL11[Set MSISDN Alert] + AL11 --> I11[MAP_INFORM_SERVICE_CENTRE_req] + I11 --> C + + I --> X1((X)) + C --> X2((X)) + +``` + +Flowchart for process MT\_SM\_HLR. It starts with three entry points (9, 10, 11) leading to MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_rsp. Point 9 leads to a decision 'SC address in MWD list?'. If No, it goes to 'Update MWD list' then 'MWD update failed?'. If Yes, it goes to 'MWD status:= SC address included'. Point 10 leads to 'SC address in MWD list?'. If No, it goes to 'MWD status:= SC address not included'. If Yes, it goes to 'MWD status:= SC address included'. Point 11 leads to 'MCEF set?'. If No, it goes to 'MSISDN= MSISDN Alert?'. If Yes, it goes to 'Set MW status'. All status updates lead to 'MSISDN= MSISDN Alert?'. If No, it goes to 'Set MSISDN Alert' then 'MAP\_INFORM\_SERVICE\_CENTRE\_req MAP\_CLOSE\_req'. If Yes, it goes directly to 'MAP\_INFORM\_SERVICE\_CENTRE\_req MAP\_CLOSE\_req'. The 'MSISDN= MSISDN Alert?' decision from point 11 leads to 'Set MSISDN Alert' then 'MAP\_INFORM\_SERVICE\_CENTRE\_req' then 'MAP\_CLOSE\_req'. All final paths end with an 'X' mark. + +4114 + +4115 + +Figure 23.3/5 (sheet 5 of 6): Process MT\_SM\_HLR + +![A process flow diagram for MT_SM_HLR. It starts with an entry point leading to a decision diamond. The first path from the diamond leads to a process block (two rectangles), which then loops back to the entry point. The second path from the diamond leads to another decision diamond. The first path from this second diamond leads to another process block (two rectangles), which loops back to the entry point. The second path from the second diamond leads to a data store (double rectangle), which then leads to an exit point marked with an 'X'. A small note box is in the top left corner.](e5a887b3a099d85d9b170d574b0604e3_img.jpg) + +``` +graph TD; Entry(( )) --> D1{ }; D1 -- Loop1 --> P1[ ][ ]; P1 --> Entry; D1 -- Loop2 --> D2{ }; D2 -- Loop3 --> P2[ ][ ]; P2 --> Entry; D2 -- DataStore --> DS[= =]; DS --> Exit[X]; +``` + +A process flow diagram for MT\_SM\_HLR. It starts with an entry point leading to a decision diamond. The first path from the diamond leads to a process block (two rectangles), which then loops back to the entry point. The second path from the diamond leads to another decision diamond. The first path from this second diamond leads to another process block (two rectangles), which loops back to the entry point. The second path from the second diamond leads to a data store (double rectangle), which then leads to an exit point marked with an 'X'. A small note box is in the top left corner. + +4116 + +4117 + +**Figure 23.3/5 (sheet 6 of 6): Process MT\_SM\_HLR** + +procedure Perform\_Relaying + +1(1) + +Procedure in the HLR to perform the relaying of the Send Routing Info For SM message to the IP-SM-GW + +Signals to/from the left are to/from the SMS-GMSC; +Signals to/from the right are to/from the IP-SM-GW + +![Flowchart for procedure Perform_Relaying. It starts with a connector, followed by a process block with MAP_OPEN_req, MAP_SEND_ROUTING_INFO_FOR_SM_req, and MAP_DELIMITER_req. Then 'Transparent Relaying' is performed. A loop follows with two parallel paths: one with a '*' symbol and a '-' symbol, and another with a '-' symbol. A decision diamond 'Dialogue closed' follows. If 'Yes', it ends at a connector. If 'No', it goes to another 'Transparent Relaying' block.](2a8b6914e187cb2ba5e51a4d51d32a4c_img.jpg) + +``` + +graph TD + Start([ ]) --> Process["MAP_OPEN_req +MAP_SEND_ROUTING_INFO_FOR_SM_req +MAP_DELIMITER_req"] + Process --> TR1([Transparent Relaying]) + TR1 --> LoopStart(( )) + LoopStart --> LeftPath["* +-"] + LoopStart --> RightPath["-"] + LeftPath --> LoopEnd(( )) + RightPath --> LoopEnd + LoopEnd --> Decision{Dialogue closed} + Decision -- Yes --> End([X]) + Decision -- No --> TR2([Transparent Relaying]) + +``` + +Flowchart for procedure Perform\_Relaying. It starts with a connector, followed by a process block with MAP\_OPEN\_req, MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_req, and MAP\_DELIMITER\_req. Then 'Transparent Relaying' is performed. A loop follows with two parallel paths: one with a '\*' symbol and a '-' symbol, and another with a '-' symbol. A decision diamond 'Dialogue closed' follows. If 'Yes', it ends at a connector. If 'No', it goes to another 'Transparent Relaying' block. + +4118 + +4119 + +Figure 23.3/5a (sheet 1 of 1): Procedure Perform\_Relaying + +# Process MT\_SM\_VMSC + +MT\_SM\_VMSC1(4) + +The mobile terminated short message service process in the VMSC + +Signals to/from the left are to/from the SMS-GMSC + +![Flowchart for Process MT_SM_VMSC. It starts with an entry point leading to a 'Null' state, then 'Receive_Open_Ind'. From there, it branches based on 'Vr', 'OK', and 'Error' signals. The 'OK' path leads to 'Destination Reference received' decision. If 'No', it goes to 'Null'. If 'Yes', it goes to 'Store Destination Reference'. Both paths lead to 'TCAP Handshake required' decision. If 'No', it goes to 'Wait_For_Service_Primitive' and then 'MAP_DELIMITER_ind'. If 'Yes', it goes to 'Wait_For_DELIMITER'. From 'Wait_For_DELIMITER', it branches into multiple paths: 'MAP_DELIMITER_ind' (leading to 'MAP_DELIMITER_req' and 'Wait_For_Service_Primitive'), 'MAP_MT_FORW_SM_ind' (leading to 'Set Error System Failure' and 'MAP_MT_FORW_SM_rsp'), 'MAP_DELIMITER_ind' (leading to 'MAP_DELIMITER_req' and 'Wait_For_Service_Primitive'), a path leading to 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind', and 'MAP_NOTICE_ind' (leading to 'MAP_CLOSE_req' and 'Null'). From the 'Wait_For_Service_Primitive' state in the middle path, it branches into 'MAP_DELIMITER_ind' (leading to 'MAP_DELIMITER_req' and 'Null'), a path leading to 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind', and 'MAP_NOTICE_ind' (leading to 'MAP_CLOSE_req' and 'Null').](5ee8f90537f5f1092504f72bfc7c29f3_img.jpg) + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind -- Vr --> Perform_MAP_Vr_Dialogue[Perform MAP Vr Dialogue] + Perform_MAP_Vr_Dialogue --> Null2([Null]) + Receive_Open_Ind -- OK --> Destination_Reference_received{Destination Reference received} + Destination_Reference_received -- No --> Null3([Null]) + Destination_Reference_received -- Yes --> Store_Destination_Reference[Store Destination Reference] + Store_Destination_Reference --> TCAP_Handshake_required{TCAP Handshake required} + TCAP_Handshake_required -- No --> Wait_For_Service_Primitive1[Wait_For_Service_Primitive] + Wait_For_Service_Primitive1 --> MAP_DELIMITER_ind1[MAP_DELIMITER_ind] + MAP_DELIMITER_ind1 --> MAP_DELIMITER_req1[MAP_DELIMITER_req] + MAP_DELIMITER_req1 --> Wait_For_Service_Primitive2[Wait_For_Service_Primitive] + TCAP_Handshake_required -- Yes --> Wait_For_DELIMITER[Wait_For_DELIMITER] + Wait_For_DELIMITER --> MAP_DELIMITER_ind2[MAP_DELIMITER_ind] + MAP_DELIMITER_ind2 --> MAP_DELIMITER_req2[MAP_DELIMITER_req] + MAP_DELIMITER_req2 --> Wait_For_Service_Primitive3[Wait_For_Service_Primitive] + Wait_For_DELIMITER --> MAP_MT_FORW_SM_ind[MAP_MT_FORW_SM_ind] + MAP_MT_FORW_SM_ind --> Set_Error_System_Failure[Set Error System Failure] + Set_Error_System_Failure --> MAP_MT_FORW_SM_rsp[MAP_MT_FORW_SM_rsp] + MAP_MT_FORW_SM_rsp --> MAP_CLOSE_req2[MAP_CLOSE_req] + MAP_CLOSE_req2 --> Null4([Null]) + Wait_For_DELIMITER --> MAP_DELIMITER_ind3[MAP_DELIMITER_ind] + MAP_DELIMITER_ind3 --> MAP_DELIMITER_req3[MAP_DELIMITER_req] + MAP_DELIMITER_req3 --> Wait_For_Service_Primitive4[Wait_For_Service_Primitive] + Wait_For_DELIMITER --> MAP_NOTICE_ind1[MAP_NOTICE_ind] + MAP_NOTICE_ind1 --> MAP_CLOSE_req3[MAP_CLOSE_req] + MAP_CLOSE_req3 --> Null5([Null]) + Wait_For_DELIMITER --> MAP_U_ABORT_ind[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Wait_For_DELIMITER --> MAP_NOTICE_ind2[MAP_NOTICE_ind] + MAP_NOTICE_ind2 --> MAP_CLOSE_req4[MAP_CLOSE_req] + MAP_CLOSE_req4 --> Null6([Null]) + Wait_For_Service_Primitive4 --> MAP_DELIMITER_ind4[MAP_DELIMITER_ind] + MAP_DELIMITER_ind4 --> MAP_DELIMITER_req4[MAP_DELIMITER_req] + MAP_DELIMITER_req4 --> Null7([Null]) + Wait_For_Service_Primitive4 --> MAP_U_ABORT_ind2[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Wait_For_Service_Primitive4 --> MAP_NOTICE_ind3[MAP_NOTICE_ind] + MAP_NOTICE_ind3 --> MAP_CLOSE_req5[MAP_CLOSE_req] + MAP_CLOSE_req5 --> Null8([Null]) + +``` + +Flowchart for Process MT\_SM\_VMSC. It starts with an entry point leading to a 'Null' state, then 'Receive\_Open\_Ind'. From there, it branches based on 'Vr', 'OK', and 'Error' signals. The 'OK' path leads to 'Destination Reference received' decision. If 'No', it goes to 'Null'. If 'Yes', it goes to 'Store Destination Reference'. Both paths lead to 'TCAP Handshake required' decision. If 'No', it goes to 'Wait\_For\_Service\_Primitive' and then 'MAP\_DELIMITER\_ind'. If 'Yes', it goes to 'Wait\_For\_DELIMITER'. From 'Wait\_For\_DELIMITER', it branches into multiple paths: 'MAP\_DELIMITER\_ind' (leading to 'MAP\_DELIMITER\_req' and 'Wait\_For\_Service\_Primitive'), 'MAP\_MT\_FORW\_SM\_ind' (leading to 'Set Error System Failure' and 'MAP\_MT\_FORW\_SM\_rsp'), 'MAP\_DELIMITER\_ind' (leading to 'MAP\_DELIMITER\_req' and 'Wait\_For\_Service\_Primitive'), a path leading to 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind', and 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req' and 'Null'). From the 'Wait\_For\_Service\_Primitive' state in the middle path, it branches into 'MAP\_DELIMITER\_ind' (leading to 'MAP\_DELIMITER\_req' and 'Null'), a path leading to 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind', and 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req' and 'Null'). + +4120 + +4121 + +Figure 23.3/6 (sheet 1 of 4): Procedure MT\_SM\_VMSC + +![Flowchart for Process MT_SM_VMSC. It starts with 'Wait_For_Service_Primitive', followed by 'MAP_MT_FORWARD_SHORT_MESSAGE_ind', 'Check_Indication' (referencing Figure 25.2/1), and 'MT_SM_Transfer_MSC' (referencing Figure 23.3/4). From there, it branches based on 'CAMEL Handling' (True/False) and 'More messages to send?' (Yes/No).](0d0294701ebee83eb3e046fc9a4dc18e_img.jpg) + +### Process MT\_SM\_VMSC MT\_SM\_VMSC2(4) + +The mobile terminated short message service process in the VMSC + +Signals to/from the left are to/from the SMS-GMSC + +``` + +graph TD + Start([Wait_For_Service_Primitive]) --> In1{{ }} + In1 -- "MAP_MT_FORWARD_SHORT_MESSAGE_ind" --> Check[Check_Indication] + Check -.-> F2521[Figure 25.2/1] + Check -- OK --> MTSM[MT_SM_Transfer_MSC] + MTSM -.-> F2334[Figure 23.3/4] + MTSM -- Error --> Release[Release SMS] + MTSM -- OK --> CH1{CAMEL Handling} + CH1 -- True --> Delivered[CAMEL_T_SMS_DELIVERED] + Delivered -.-> TS23078_1[See TS 23.078] + CH1 -- False --> MoreMsg{More messages to send?} + CH1 -- Abort --> CH2{CAMEL Handling} + CH2 -- True --> Failure1[CAMEL_T_SMS_FAILURE] + Failure1 -.-> TS23078_2[See TS 23.078] + CH2 -- False --> MoreMsg + CH2 -- Error --> Release + Failure1 --> Null1([Null]) + MoreMsg -- Yes --> Out1{{ }} + Out1 -- "MAP_MT_FORWARD_SHORT_MESSAGE_rsp +MAP_DELIMITER_req" --> WaitMore[Wait_For_More_Messages] + MoreMsg -- No --> Join(( )) + CH3{CAMEL Handling} -- True --> Failure2[CAMEL_T_SMS_FAILURE] + Failure2 -.-> TS23078_3[See TS 23.078] + CH3 -- False --> Release + Failure2 --> Null2([Null]) + Join --> Out2{{ }} + Out2 -- "MAP_MT_FORWARD_SHORT_MESSAGE_rsp +MAP_CLOSE_req" --> Null2 + +``` + +Flowchart for Process MT\_SM\_VMSC. It starts with 'Wait\_For\_Service\_Primitive', followed by 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ind', 'Check\_Indication' (referencing Figure 25.2/1), and 'MT\_SM\_Transfer\_MSC' (referencing Figure 23.3/4). From there, it branches based on 'CAMEL Handling' (True/False) and 'More messages to send?' (Yes/No). + +4122 + +4123 + +Figure 23.3/6 (sheet 2 of 4): Procedure MT\_SM\_VMSC + +Process MT\_SM\_VMSC + +MT\_SM\_VMSC3(4) + +The mobile terminated short message service process in the VMSC + +Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MS + +![Flowchart for Process MT_SM_VMSC showing the logic for mobile terminated short message service in the VMSC. It starts with 'Wait_For_More_Messages', followed by 'MAP_MT_FORWARD_SHORT_MESSAGE_ind', 'Check_Indication', and various decision points for CAMEL handling and message delivery status.](2541521b5520088e72e6e6252691cd13_img.jpg) + +``` + +graph TD + Start([Wait_For_More_Messages]) --> In1{{ }} + In1 --> In1 + In1 --> MAP_ind[MAP_MT_FORWARD_SHORT_MESSAGE_ind] + MAP_ind --> Check[Check_Indication] + Check --> OK{OK} + OK -- True --> CAMEL_Handling_1{CAMEL Handling} + OK -- False --> CAMEL_Handling_1 + CAMEL_Handling_1 -- True --> CAMEL_T_SMS_INIT[CAMEL_T_SMS_INIT] + CAMEL_T_SMS_INIT -.-> TS_23_078_1[See TS 23.078] + CAMEL_T_SMS_INIT --> Result{Result?} + Result -- Release_SMS --> Set_Error[Set Error according to gsmSCF instructions] + Set_Error --> Error[Error] + Result -- Continue --> A_RP_MT_DATA_req[A_RP_MT_DATA_req] + A_RP_MT_DATA_req --> Wait_Subsequent[Wait_For_Subsequent_A_SM_CONFIRM] + Wait_Subsequent --> A_RP_ERROR_ind{{A_RP_ERROR_ind}} + Wait_Subsequent --> A_RP_ACK_ind{{A_RP_ACK_ind}} + A_RP_ERROR_ind --> Set_User_Error[Set User Error] + Set_User_Error --> CAMEL_Handling_2{CAMEL Handling} + CAMEL_Handling_2 -- True --> CAMEL_T_SMS_FAILURE[CAMEL_T_SMS_FAILURE] + CAMEL_T_SMS_FAILURE -.-> TS_23_078_2[See TS 23.078] + CAMEL_Handling_2 -- False --> Error + A_RP_ACK_ind --> CAMEL_Handling_3{CAMEL Handling} + CAMEL_Handling_3 -- True --> CAMEL_T_SMS_DELIVERED[CAMEL_T_SMS_DELIVERED] + CAMEL_T_SMS_DELIVERED -.-> TS_23_078_3[See TS 23.078] + CAMEL_Handling_3 -- False --> More_Messages{More messages to send?} + More_Messages -- No --> Error + More_Messages -- Yes --> Out1{{ }} + Out1 --> Out1 + Out1 --> MAP_rsp[MAP_MT_FORWARD_SHORT_MESSAGE_rsp] + MAP_rsp --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> Null([Null]) + Out1 --> MAP_DELIMITER_req[MAP_DELIMITER_req] + MAP_DELIMITER_req --> Wait_For_More_Messages_2([Wait_For_More_Messages]) + +``` + +Flowchart for Process MT\_SM\_VMSC showing the logic for mobile terminated short message service in the VMSC. It starts with 'Wait\_For\_More\_Messages', followed by 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ind', 'Check\_Indication', and various decision points for CAMEL handling and message delivery status. + +4124 + +4125 + +Figure 23.3/6 (sheet 3 of 4): Procedure MT\_SM\_VMSC + +![Sequence diagram for Process MT_SM_VMSC. The diagram is split into two main sections. The top section starts with 'Wait_For_More_Messages' and shows a loop for handling multiple messages, ending at 'Null'. The bottom section starts with 'Wait_For_Subsequent_A_SM_CONFIRM' and shows a loop for subsequent confirmations, which can lead to 'CAMEL_T_SMS_FAILURE' (referencing TS 23.078) or 'Null'. Various MAP and A messages are exchanged between the VMSC and the SMS-GMSC (left) and the MS (right).](ec3bfe8b7736481dc1218d736a699e89_img.jpg) + +### Process MT\_SM\_VMSC + +### MT\_SM\_VMSC4(4) + +The mobile terminated short message service process in the VMSC + +Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MS + +``` + +sequenceDiagram + participant VMSC + participant SMS-GMSC as SMS-GMSC + participant MS as MS + + Note left of VMSC: The mobile terminated short message service process in the VMSC + Note right of VMSC: Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MS + + Note over VMSC: Wait_For_More_Messages + VMSC->>SMS-GMSC: MAP_U_ABORT_ind / MAP_P_ABORT_ind + VMSC->>MS: MAP_NOTICE_ind + VMSC->>MS: MAP_CLOSE_req + VMSC->>MS: A_ABORT_req + VMSC->>SMS-GMSC: A_ABORT_req + VMSC->>MS: A_MM_RELEASE + VMSC->>MS: MAP_U_ABORT_req + Note over VMSC: Null + + Note over VMSC: Wait_For_Subsequent_A_SM_CONFIRM + VMSC->>SMS-GMSC: MAP_U_ABORT_ind / MAP_P_ABORT_ind + VMSC->>MS: MAP_NOTICE_ind + VMSC->>MS: MAP_CLOSE_req + VMSC->>MS: A_ABORT_req + VMSC->>SMS-GMSC: A_ABORT_req + VMSC->>MS: A_MM_RELEASE + VMSC->>MS: MAP_U_ABORT_req + Note over VMSC: CAMEL-Handling + Note right of VMSC: See TS 23.078 + Note over VMSC: CAMEL_T_SMS_FAILURE + Note over VMSC: Null + +``` + +Sequence diagram for Process MT\_SM\_VMSC. The diagram is split into two main sections. The top section starts with 'Wait\_For\_More\_Messages' and shows a loop for handling multiple messages, ending at 'Null'. The bottom section starts with 'Wait\_For\_Subsequent\_A\_SM\_CONFIRM' and shows a loop for subsequent confirmations, which can lead to 'CAMEL\_T\_SMS\_FAILURE' (referencing TS 23.078) or 'Null'. Various MAP and A messages are exchanged between the VMSC and the SMS-GMSC (left) and the MS (right). + +4126 + +4127 + +Figure 23.3/6 (sheet 4 of 4): Procedure MT\_SM\_VMSC + +Macrodefinition MT\_SM\_Transfer\_MSC + +MT\_SM\_Xfer\_MSC1(4) + +The mobile terminated short message transfer macro in the MSC + +Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR + +![State transition diagram for MT_SM_Transfer_MSC macro. The process starts with a check if the MSC supports MT SMS. If 'No', it sets a user error 'Facility Not Supported' and ends in an 'Error' state. If 'Yes', it checks subscriber identity for MT SMS. If 'OK', it sends MAP requests (OPEN_req, SEND_INFO_FOR_MT_SMS_req, DELIMITER_req) and receives a confirmation. If 'Vr, Error', it sets a user error 'System Failure' and ends in an 'Error' state. It then checks if CAMEL handling is false. If so, it waits for a page. The diagram then branches into three parallel paths: 'Page_MSC' (leading to Figure 25.3/1), 'Search_for_MS_MSC' (leading to Figure 25.3/2), and 'MAP_SEND_INFO_FOR_MT_SMS_cnf'. All three paths lead to a decision 'MS supports SMS?'. If 'No', it sets a user error 'SM Delivery Failure' with cause 'Equipment not SM equipped', sends MAP_U_ABORT_req and A_ABORT_req, and ends in an 'Error' state. If 'Yes', it proceeds to 'Process_Access_Request_MSC' (leading to Figure 25.4/1). From there, if 'Error', it sets a user error 'System Failure' and ends in an 'Error' state. If 'OK', it waits for a VLR response.](6678caa2abcfcdb18b5a35654250f4c4_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Start + Start --> MSC_Supports_MT_SMS{MSC supports MT SMS?} + MSC_Supports_MT_SMS -- No --> Set_User_Error_1[Set User Error: Facility Not Supported] + Set_User_Error_1 --> Error_1((Error)) + MSC_Supports_MT_SMS -- Yes --> Check_Subscr[Check_Subscr_Identity_for_MT_SMS] + Check_Subscr -- OK --> MAP_Requests[MAP_OPEN_req, MAP_SEND_INFO_FOR_MT_SMS_req, MAP_DELIMITER_req] + MAP_Requests --> Receive_Open_Cnf[Receive_Open_Cnf] + Receive_Open_Cnf -- OK --> CAMEL_Handling[CAMEL Handling:= False] + Receive_Open_Cnf -- Vr, Error --> Set_User_Error_2[Set User Error: System Failure] + Set_User_Error_2 --> Error_2((Error)) + CAMEL_Handling --> Wait_For_Page[Wait_For_Page] + Wait_For_Page --> Page_MSC[Page_MSC] + Wait_For_Page --> Search_for_MS_MSC[Search_for_MS_MSC] + Wait_For_Page --> MAP_SEND_INFO_FOR_MT_SMS_cnf[MAP_SEND_INFO_FOR_MT_SMS_cnf] + Page_MSC -- Null --> Set_User_Error_3[Set User Error: System Failure] + Set_User_Error_3 --> Error_3((Error)) + Page_MSC -- Error --> Wait_For_VLR_Response_1[Wait_For_VLR_Response] + Page_MSC -- OK --> MS_Supports_SMS{MS supports SMS?} + Search_for_MS_MSC -- Null --> Set_User_Error_4[Set User Error: System Failure] + Set_User_Error_4 --> Error_4((Error)) + Search_for_MS_MSC -- Error --> Wait_For_VLR_Response_2[Wait_For_VLR_Response] + Search_for_MS_MSC -- OK --> MS_Supports_SMS + MAP_SEND_INFO_FOR_MT_SMS_cnf --> Set_User_Error_5[Set User Error] + Set_User_Error_5 --> Error_5((Error)) + MS_Supports_SMS -- No --> Set_User_Error_6[Set User Error: SM Delivery Failure] + Set_User_Error_6 --> Delivery_Failure_Cause[Delivery failure cause:= Equipment not SM equipped] + Delivery_Failure_Cause --> MAP_U_ABORT_req[MAP_U_ABORT_req] + MAP_U_ABORT_req --> A_ABORT_req[A_ABORT_req] + A_ABORT_req --> Error_6((Error)) + MS_Supports_SMS -- Yes --> Process_Access_Request_MSC[Process_Access_Request_MSC] + Process_Access_Request_MSC -- Error --> Set_User_Error_7[Set User Error: System Failure] + Set_User_Error_7 --> Error_7((Error)) + Process_Access_Request_MSC -- OK --> Wait_For_VLR_Response_3[Wait_For_VLR_Response] + +``` + +State transition diagram for MT\_SM\_Transfer\_MSC macro. The process starts with a check if the MSC supports MT SMS. If 'No', it sets a user error 'Facility Not Supported' and ends in an 'Error' state. If 'Yes', it checks subscriber identity for MT SMS. If 'OK', it sends MAP requests (OPEN\_req, SEND\_INFO\_FOR\_MT\_SMS\_req, DELIMITER\_req) and receives a confirmation. If 'Vr, Error', it sets a user error 'System Failure' and ends in an 'Error' state. It then checks if CAMEL handling is false. If so, it waits for a page. The diagram then branches into three parallel paths: 'Page\_MSC' (leading to Figure 25.3/1), 'Search\_for\_MS\_MSC' (leading to Figure 25.3/2), and 'MAP\_SEND\_INFO\_FOR\_MT\_SMS\_cnf'. All three paths lead to a decision 'MS supports SMS?'. If 'No', it sets a user error 'SM Delivery Failure' with cause 'Equipment not SM equipped', sends MAP\_U\_ABORT\_req and A\_ABORT\_req, and ends in an 'Error' state. If 'Yes', it proceeds to 'Process\_Access\_Request\_MSC' (leading to Figure 25.4/1). From there, if 'Error', it sets a user error 'System Failure' and ends in an 'Error' state. If 'OK', it waits for a VLR response. + +4128 + +4129 + +Figure 23.3/7 (sheet 1 of 4): Macro MT\_SM\_Transfer\_MSC + +![SDL Macro diagram for MT_SM_Transfer_MSC. It shows the logic flow from Wait_For_Page, handling CAMEL initialization, and branching based on the result to either abort or request info for MT SMS.](44f36a2e7dd76edc5279dfac49e85199_img.jpg) + +## Macrodefinition MT\_SM\_Transfer\_MSC MT\_SM\_Xfer\_MSC2(4) + +The mobile terminated short message transfer macro in the MSC + +Signals to/from the right are to/from the VLR + +``` + + graph TD + Start([Wait_For_Page]) --> Input[/MAP_CONTINUE_CAMEL_SMS_HANDLING_ind/] + Input --> Task1[CAMEL Handling:= True] + Task1 --> Proc1[[CAMEL_T_SMS_INIT]] + Proc1 --- Note1[See TS 23.078] + Proc1 --> Dec1{Result?} + + Dec1 -- Release_SMS --> Out1[/MAP_U_ABORT_req/] + Out1 --> End1([Release SMS]) + + Dec1 -- Continue --> Task2[Set Suppress MT-SMS-CSI] + Task2 --> Out2[/MAP_SEND_INFO_FOR_MT_SMS_req/] + Out2 --> End2([Wait_For_Page]) + +``` + +SDL Macro diagram for MT\_SM\_Transfer\_MSC. It shows the logic flow from Wait\_For\_Page, handling CAMEL initialization, and branching based on the result to either abort or request info for MT SMS. + +4130 + +4131 + +**Figure 23.3/7 (sheet 2 of 4): Macro MT\_SM\_Transfer\_MSC** + +# Macrodefinition MT\_SM\_Transfer\_MSC + +MT\_SM\_Xfer\_MSC3(4) + +The mobile terminated short message transfer macro in the MSC + +Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR + +Figure 25.9/1 + +![Flowchart for Macro MT_SM_Transfer_MSC. The process starts with 'Wait_For_VLR_Response', followed by 'Trace_Subscriber_Activity_MSC' and 'MAP_SEND_INFO_FOR_MT_SMS_cnf'. It then enters another 'Wait_For_VLR_Response' loop. A decision 'A_RP_MT_DATA_req' follows, with 'OK' leading to 'Wait_For_First_A_SM_CONFIRM' and then 'A_RP_ACK_ind' (OK), and 'Provider Error, Data Error' or 'User Error' leading to 'Set User Error' (Error). A 'Check_Confirmation' block also leads to 'Set User Error' (Error) for 'User Error' cases, with a note that for absent subscribers, the error includes a diagnostic indication.](8e2e5961af70ba6bc28c2e895f3f98ca_img.jpg) + +``` + +graph TD + Start([Wait_For_VLR_Response]) --> Trace[Trace_Subscriber_Activity_MSC] + Trace --> MAP[MAP_SEND_INFO_FOR_MT_SMS_cnf] + Trace --> Wait2([Wait_For_VLR_Response]) + Wait2 --> Decision{A_RP_MT_DATA_req} + Decision -- OK --> Wait3([Wait_For_First_A_SM_CONFIRM]) + Decision -- "Provider Error, Data Error" --> SetError1[Set User Error: System Failure] + SetError1 --> Error1((Error)) + Decision -- User Error --> SetError2[Set User Error] + SetError2 --> Error2((Error)) + Check[Check_Confirmation] -- User Error --> SetError3[Set User Error] + SetError3 --> Error3((Error)) + Note1[For Absent Subscriber, User Error includes diagnostic indication] -.-> SetError3 + Wait3 --> ACK{A_RP_ACK_ind} + ACK --> OK1((OK)) + Wait3 --> ERROR{A_RP_ERROR_ind} + ERROR --> SetError4[Set User Error] + SetError4 --> Error4((Error)) + +``` + +Flowchart for Macro MT\_SM\_Transfer\_MSC. The process starts with 'Wait\_For\_VLR\_Response', followed by 'Trace\_Subscriber\_Activity\_MSC' and 'MAP\_SEND\_INFO\_FOR\_MT\_SMS\_cnf'. It then enters another 'Wait\_For\_VLR\_Response' loop. A decision 'A\_RP\_MT\_DATA\_req' follows, with 'OK' leading to 'Wait\_For\_First\_A\_SM\_CONFIRM' and then 'A\_RP\_ACK\_ind' (OK), and 'Provider Error, Data Error' or 'User Error' leading to 'Set User Error' (Error). A 'Check\_Confirmation' block also leads to 'Set User Error' (Error) for 'User Error' cases, with a note that for absent subscribers, the error includes a diagnostic indication. + +4132 + +4133 + +Figure 23.3/7 (sheet 3 of 4): Macro MT\_SM\_Transfer\_MSC + +Macrodefinition MT\_SM\_Transfer\_MSC + +MT\_SM\_Xfer\_MSC4(4) + +The mobile terminated short message transfer macro in the MSC + +In the upper subtree: +Signals to/from the left are to/from the MS; +signals to/from the right are to/from the VLR + +![Sequence diagram for the upper subtree of MT_SM_Transfer_MSC. It starts with a state box containing 'Wait_For_Page, Wait_For_VLR_Response, Wait_For_First_A_SM_CONFIRM'. A horizontal line leads to a decision point. The left path consists of 'A_MM_RELEASE_ind' (diamond), 'MAP_U_ABORT_req' (arrow), and 'Set User Error: System Failure' (rectangle), ending at an 'Error' circle. The right path consists of a diamond leading to 'MAP_U_ABORT_ind, MAP_CLOSE_ind' (rectangle), then 'A_ABORT_Req' (diamond), and finally merging into the 'Set User Error' path.](e822e328d38fd41da4a4aa84c6d60725_img.jpg) + +Sequence diagram for the upper subtree of MT\_SM\_Transfer\_MSC. It starts with a state box containing 'Wait\_For\_Page, Wait\_For\_VLR\_Response, Wait\_For\_First\_A\_SM\_CONFIRM'. A horizontal line leads to a decision point. The left path consists of 'A\_MM\_RELEASE\_ind' (diamond), 'MAP\_U\_ABORT\_req' (arrow), and 'Set User Error: System Failure' (rectangle), ending at an 'Error' circle. The right path consists of a diamond leading to 'MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' (rectangle), then 'A\_ABORT\_Req' (diamond), and finally merging into the 'Set User Error' path. + +In the lower subtree: +Signals to/from the left are to/from the MS; +signals to/from the right are to/from the SMS-GMSC unless marked otherwise + +![Sequence diagram for the lower subtree of MT_SM_Transfer_MSC. It starts with a state box containing 'Wait_For_Page, Wait_For_VLR_Response, Wait_For_First_A_SM_CONFIRM'. A horizontal line leads to a decision point. The left path consists of 'MAP_NOTICE_ind' (diamond), 'MAP_CLOSE_req' (arrow), and 'MAP_U_ABORT_Req' (arrow) which points to a 'To VLR' box. The right path consists of a diamond leading to 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' (rectangle), then 'A_ABORT_Req' (diamond), and finally merging into the 'MAP_U_ABORT_Req' path. Both paths end at an 'Abort' circle.](1aa4931f90dcf4d8d632d1ac4533bf16_img.jpg) + +Sequence diagram for the lower subtree of MT\_SM\_Transfer\_MSC. It starts with a state box containing 'Wait\_For\_Page, Wait\_For\_VLR\_Response, Wait\_For\_First\_A\_SM\_CONFIRM'. A horizontal line leads to a decision point. The left path consists of 'MAP\_NOTICE\_ind' (diamond), 'MAP\_CLOSE\_req' (arrow), and 'MAP\_U\_ABORT\_Req' (arrow) which points to a 'To VLR' box. The right path consists of a diamond leading to 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' (rectangle), then 'A\_ABORT\_Req' (diamond), and finally merging into the 'MAP\_U\_ABORT\_Req' path. Both paths end at an 'Abort' circle. + +4134 + +4135 + +Figure 23.3/7 (sheet 4 of 4): Macro MT\_SM\_Transfer\_MSC + +macrodefinition Check\_Subscr\_Identity\_for\_MT\_SMS + +CSIFMTSMS1(1) + +Macro to check the identity of a subscriber for MT SMS; invoked in the VMSC and the SGSN + +![Flowchart for macrodefinition Check_Subscr_Identity_for_MT_SMS. It starts with an oval connector, leading to a decision diamond 'Destination reference present?'. If 'No', it goes to another decision diamond 'SM_RP_DA= IMSI?'. If 'Yes', it sets 'Destination reference:= Not included' and then 'SM_RP_DA:= IMSI' to reach an 'OK' terminal. If 'No', it goes to a 'Set User Error: Unexpected data value' block to reach an 'Error' terminal. If 'Yes' from the first diamond, it goes to a decision diamond 'SM_RP_DA= LMSI?'. If 'Yes', it sets 'Destination reference:= IMSI' and then 'SM_RP_DA:= LMSI' to reach an 'OK' terminal. If 'No', it joins the path before the 'Set User Error' block.](f6c91eee4c272a5313689832a5622706_img.jpg) + +``` + +graph TD + Start([ ]) --> D1{Destination reference present?} + D1 -- No --> D2{SM_RP_DA= IMSI?} + D1 -- Yes --> D3{SM_RP_DA= LMSI?} + D2 -- Yes --> P1[Destination reference:= Not included] + P1 --> P2[SM_RP_DA:= IMSI] + P2 --> OK1([OK]) + D2 -- No --> J(( )) + D3 -- Yes --> P3[Destination reference:= IMSI] + P3 --> P4[SM_RP_DA:= LMSI] + P4 --> OK2([OK]) + D3 -- No --> J + J --> E[Set User Error: Unexpected data value] + E --> Error([Error]) + +``` + +Flowchart for macrodefinition Check\_Subscr\_Identity\_for\_MT\_SMS. It starts with an oval connector, leading to a decision diamond 'Destination reference present?'. If 'No', it goes to another decision diamond 'SM\_RP\_DA= IMSI?'. If 'Yes', it sets 'Destination reference:= Not included' and then 'SM\_RP\_DA:= IMSI' to reach an 'OK' terminal. If 'No', it goes to a 'Set User Error: Unexpected data value' block to reach an 'Error' terminal. If 'Yes' from the first diamond, it goes to a decision diamond 'SM\_RP\_DA= LMSI?'. If 'Yes', it sets 'Destination reference:= IMSI' and then 'SM\_RP\_DA:= LMSI' to reach an 'OK' terminal. If 'No', it joins the path before the 'Set User Error' block. + +4136 + +4137 + +Figure 23.3/8: Macro Check\_Subscr\_Identity\_For\_MT\_SMS + +![Flowchart for process MT_SM_VLR. It starts with an initial state, followed by a 'Null' state, then 'Receive Open_Ind'. From 'Receive Open_Ind', an 'OK' path leads to 'Wait_For_Service_Primitive' and a 'Vr, Error' path leads to 'Null'. From 'Wait_For_Service_Primitive', the flow goes to a merge point for 'MAP_SEND_INFO_FOR_MT_SMS_ind'. From this merge point, it goes to 'Check_Indication'. From 'Check_Indication', an 'OK' path leads to a decision 'Subscriber known?'. If 'No', it goes to 'Set User Error: Unidentified subscriber'. If 'Yes', it goes to another decision 'Confirmed by HLR?'. If 'No', it goes to the same 'Set User Error' block. If 'Yes', it leads to connector '1'. Both 'Set User Error' and an 'Error' path from 'Check_Indication' lead to a merge point for 'MAP_SEND_INFO_FOR_MT_SMS_rsp' and 'MAP_CLOSE_req', which then leads to a 'Null' state.](f5657d08a46856dfb878f4ed80220a7f_img.jpg) + +**process MT\_SM\_VLR** **MT\_SM\_VLR1(3)** + +Process in the VLR to handle a request for information to handle MT short message delivery + +Signals to/from the left are to/from the MSC + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> RecOpen[Receive Open_Ind] + RecOpen -- OK --> WaitFor[Wait_For_Service_Primitive] + RecOpen -- "Vr, Error" --> Null2([Null]) + WaitFor --> Merge1{ } + Merge1 -- "MAP_SEND_INFO_FOR_MT_SMS_ind" --> CheckInd[Check_Indication] + CheckInd -- OK --> SubKnown{Subscriber known?} + CheckInd -- Error --> Merge2{ } + SubKnown -- No --> SetError[Set User Error: Unidentified subscriber] + SubKnown -- Yes --> Confirmed{Confirmed by HLR?} + Confirmed -- No --> SetError + Confirmed -- Yes --> Connector1((1)) + SetError --> Merge2 + Merge2 -- "MAP_SEND_INFO_FOR_MT_SMS_rsp +MAP_CLOSE_req" --> Null3([Null]) + +``` + +Flowchart for process MT\_SM\_VLR. It starts with an initial state, followed by a 'Null' state, then 'Receive Open\_Ind'. From 'Receive Open\_Ind', an 'OK' path leads to 'Wait\_For\_Service\_Primitive' and a 'Vr, Error' path leads to 'Null'. From 'Wait\_For\_Service\_Primitive', the flow goes to a merge point for 'MAP\_SEND\_INFO\_FOR\_MT\_SMS\_ind'. From this merge point, it goes to 'Check\_Indication'. From 'Check\_Indication', an 'OK' path leads to a decision 'Subscriber known?'. If 'No', it goes to 'Set User Error: Unidentified subscriber'. If 'Yes', it goes to another decision 'Confirmed by HLR?'. If 'No', it goes to the same 'Set User Error' block. If 'Yes', it leads to connector '1'. Both 'Set User Error' and an 'Error' path from 'Check\_Indication' lead to a merge point for 'MAP\_SEND\_INFO\_FOR\_MT\_SMS\_rsp' and 'MAP\_CLOSE\_req', which then leads to a 'Null' state. + +4138 + +4139 + +**Figure 23.3/9 (sheet 1 of 3): Process MT\_SM\_VLR** + +![Flowchart for process MT_SM_VLR. It starts at connector '1', checks if IMSI is detached or if roaming is allowed. If either is 'Yes', it sets a user error, sets an MNRF, sends MAP signals, and ends at 'Null'. If both are 'No', it calls CAMEL_MT_SMS_VLR. If that fails, it ends at 'Null'. If it passes, it checks if LAI is known. If 'No', it sends MAP_SEARCH_FOR_MS_req and MAP_DELIMITER_req, then waits for an access request. If 'Yes', it checks if confirmed by radio contact. If 'No', it sends MAP_SEARCH_FOR_MS_req and MAP_DELIMITER_req, then waits. If 'Yes', it sends MAP_PAGE_req and MAP_DELIMITER_req, then waits.](4e78e866a4fb9c5b16c9c479230964f5_img.jpg) + +**process MT\_SM\_VLR** **MT\_SM\_VLR2(3)** + +Process in the VLR to handle a request for information to handle MT short message delivery + +Signals to/from the left are to/from the MSC + +``` + + graph TD + 1((1)) --> IMSI{IMSI detached?} + IMSI -- Yes --> Error[Set User Error: Absent subscriber] + IMSI -- No --> Roam{Roaming in LA allowed?} + Roam -- No --> Error + Roam -- Yes --> CAMEL[|| CAMEL_MT_SMS_VLR ||] + CAMEL -.-> See3GPP[See 3GPP TS 23.078] + CAMEL --> Result{Result?} + Result -- Fail --> Null1([Null]) + Result -- Pass --> LAI{LAI known?} + LAI -- No --> SearchReq[MAP_SEARCH_FOR_MS_req +MAP_DELIMITER_req] + SearchReq --> Wait[Wait_For_Access_Request] + LAI -- Yes --> Radio{Confirmed by radio contact?} + Radio -- No --> SearchReq + Radio -- Yes --> PageReq[MAP_PAGE_req +MAP_DELIMITER_req] + PageReq --> Wait + Error --> Diag[Set diagnostic: IMSI detached] + Diag --> MNRF[Set MNRF] + MNRF --> SendInfo[MAP_SEND_INFO_FOR_MT_SMS_rsp +MAP_CLOSE_req] + SendInfo --> Null2([Null]) + +``` + +Flowchart for process MT\_SM\_VLR. It starts at connector '1', checks if IMSI is detached or if roaming is allowed. If either is 'Yes', it sets a user error, sets an MNRF, sends MAP signals, and ends at 'Null'. If both are 'No', it calls CAMEL\_MT\_SMS\_VLR. If that fails, it ends at 'Null'. If it passes, it checks if LAI is known. If 'No', it sends MAP\_SEARCH\_FOR\_MS\_req and MAP\_DELIMITER\_req, then waits for an access request. If 'Yes', it checks if confirmed by radio contact. If 'No', it sends MAP\_SEARCH\_FOR\_MS\_req and MAP\_DELIMITER\_req, then waits. If 'Yes', it sends MAP\_PAGE\_req and MAP\_DELIMITER\_req, then waits. + +4140 + +4141 + +**Figure 23.3/9 (sheet 2 of 3): Process MT\_SM\_VLR** + +![Flowchart for process MT_SM_VLR. It starts with 'Wait_For_Access_Request' and branches into four parallel paths: 1) 'Process_Access_Request_VLR' leading to 'Set subscriber data' (OK) or 'Null' (Error). 2) 'MAP_U_ABORT_ind' leading to 'Null'. 3) 'MAP_PAGE_cnf' leading to a decision 'User error= absent subscriber?'. If 'Yes', it goes to 'Ser User Error: Absent subscriber' or 'Set User Error', then 'Set MNRF'. If 'No', it goes to 'Null'. 4) 'MAP_SEARCH_FOR_MS_cnf' leading to 'Check Confirmation'. If 'OK', it goes to 'Update LAI' then 'Confirmed by Radio Contact:= Confirmed' then 'Wait_For_Access_Request'. If 'User Error', it goes to 'Set User Error' then 'Set MNRF'. If 'Provider Error, Data Error', it goes to 'Null'. All paths converge to a merge point, followed by 'MAP_SEND_INFO_FOR_MT_SMS_rsp' and 'MAP_CLOSE_req', ending at 'Null'.](a7939a752385c56d07193179102acbcb_img.jpg) + +**process MT\_SM\_VLR** **MT\_SM\_VLR3(3)** + +Process in the VLR to handle a request for information to handle MT short message delivery + +Signals to/from the left are to/from the MSC + +``` + +graph TD + Start([Wait_For_Access_Request]) --> P1[Process_Access_Request_VLR] + Start --> P2[MAP_U_ABORT_ind] + Start --> P3[MAP_PAGE_cnf] + Start --> P4[MAP_SEARCH_FOR_MS_cnf] + + P1 --> P1_Exit{ } + P1_Exit -- Error --> Null1([Null]) + P1_Exit -- OK --> SetSub[Set subscriber data] + + P2 --> Null2([Null]) + + P3 --> Decision1{User error= absent subscriber?} + Decision1 -- Yes --> SerUserErr1[Ser User Error: Absent subscriber] + Decision1 -- Yes --> SetUserErr1[Set User Error] + SerUserErr1 --> SetMNRF[Set MNRF] + SetUserErr1 --> SetMNRF + Decision1 -- No --> Null3([Null]) + + P4 --> CheckConf[Check Confirmation] + CheckConf -- OK --> UpdateLAI[Update LAI] + UpdateLAI --> Confirmed[Confirmed by Radio Contact:= Confirmed] + Confirmed --> WaitForReq2([Wait_For_Access_Request]) + + CheckConf -- User Error --> SetUserErr2[Set User Error] + SetUserErr2 --> SetMNRF + + CheckConf -- "Provider Error, Data Error" --> Null4([Null]) + + SetSub --> Merge(( )) + SetMNRF --> Merge + Null3 --> Merge + + Merge --> MAP_SEND[MAP_SEND_INFO_FOR_MT_SMS_rsp] + Merge --> MAP_CLOSE[MAP_CLOSE_req] + + MAP_SEND --> Null5([Null]) + MAP_CLOSE --> Null5 + +``` + +Flowchart for process MT\_SM\_VLR. It starts with 'Wait\_For\_Access\_Request' and branches into four parallel paths: 1) 'Process\_Access\_Request\_VLR' leading to 'Set subscriber data' (OK) or 'Null' (Error). 2) 'MAP\_U\_ABORT\_ind' leading to 'Null'. 3) 'MAP\_PAGE\_cnf' leading to a decision 'User error= absent subscriber?'. If 'Yes', it goes to 'Ser User Error: Absent subscriber' or 'Set User Error', then 'Set MNRF'. If 'No', it goes to 'Null'. 4) 'MAP\_SEARCH\_FOR\_MS\_cnf' leading to 'Check Confirmation'. If 'OK', it goes to 'Update LAI' then 'Confirmed by Radio Contact:= Confirmed' then 'Wait\_For\_Access\_Request'. If 'User Error', it goes to 'Set User Error' then 'Set MNRF'. If 'Provider Error, Data Error', it goes to 'Null'. All paths converge to a merge point, followed by 'MAP\_SEND\_INFO\_FOR\_MT\_SMS\_rsp' and 'MAP\_CLOSE\_req', ending at 'Null'. + +4142 + +4143 + +**Figure 23.3/9 (sheet 3 of 3): Process MT\_SM\_VLR** + +![Flowchart for Process MT_SM_SGSN. It starts with an entry point leading to a 'Null' state, then 'Receive_Open_Ind'. A decision 'Destination Reference received' follows. If 'OK', it goes to 'Store Destination Reference'. If 'Error', it goes to 'Null'. If 'Vr', it goes to 'Perform MAP Vr Dialogue' (with a note about GSM 09.02 or TS 29.002) then to 'Null'. From 'Store Destination Reference', a decision 'TCAP Handshake required' follows. If 'No', it goes to 'Wait_For_Service_Primitive' then to 'MAP_DELIMITER_ind' then to 'MAP_DELIMITER_req' then to 'Wait_For_Service_Primitive' then to 'Null'. If 'Yes', it goes to 'Wait_For_DELIMITER'. From 'Wait_For_DELIMITER', there are four paths: 1) 'MAP_DELIMITER_ind' -> 'MAP_DELIMITER_req' -> 'Wait_For_Service_Primitive' -> 'Null'; 2) 'MAP_MT_FORW_SW_ind' -> 'Set Error System Failure' -> 'MAP_MT_FORW_SM_rsp' -> 'MAP_CLOSE_req' -> 'Null'; 3) 'MAP_DELIMITER_ind' -> 'MAP_DELIMITER_req' -> 'Wait_For_Service_Primitive' -> (join point) -> 'Null'; 4) 'MAP_NOTICE_ind' -> 'MAP_CLOSE_req' -> 'Null'. A callout 'Figure 25.1/1' is near 'Receive_Open_Ind'.](3a3bf4ad529fa99ba16ada1dfc922882_img.jpg) + +### Process MT\_SM\_SGSN + +### MT\_SM\_SGSN1(4) + +The mobile terminated short message service process in the SGSN + +Signals to/from the left are to/from the SMS-GMSC + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind --> DestRef{Destination Reference received} + DestRef -- OK --> StoreRef[Store Destination Reference] + DestRef -- Error --> Null2([Null]) + DestRef -- Vr --> PerformVr[Perform MAP Vr Dialogue] + PerformVr --> Null3([Null]) + StoreRef --> TCAP{TCAP Handshake required} + TCAP -- No --> WaitFSP1[Wait_For_Service_Primitive] + WaitFSP1 --> MDI1[MAP_DELIMITER_ind] + MDI1 --> MDReq1[MAP_DELIMITER_req] + MDReq1 --> WaitFSP2[Wait_For_Service_Primitive] + WaitFSP2 --> Null4([Null]) + TCAP -- Yes --> WaitFD[Wait_For_DELIMITER] + WaitFD --> MDI2[MAP_DELIMITER_ind] + MDI2 --> MDReq2[MAP_DELIMITER_req] + MDReq2 --> WaitFSP3[Wait_For_Service_Primitive] + WaitFSP3 --> Join1(( )) + Join1 --> Null5([Null]) + WaitFD --> MTFSW[MAP_MT_FORW_SW_ind] + MTFSW --> SetError[Set Error System Failure] + SetError --> MTFSMR[MAP_MT_FORW_SM_rsp] + MTFSMR --> MCReq[MAP_CLOSE_req] + MCReq --> Null6([Null]) + WaitFD --> MDI3[MAP_DELIMITER_ind] + MDI3 --> MDReq3[MAP_DELIMITER_req] + MDReq3 --> WaitFSP4[Wait_For_Service_Primitive] + WaitFSP4 --> Join2(( )) + Join2 --> Null7([Null]) + WaitFD --> MDI4[MAP_NOTICE_ind] + MDI4 --> MCReq2[MAP_CLOSE_req] + MCReq2 --> Null8([Null]) + +``` + +Flowchart for Process MT\_SM\_SGSN. It starts with an entry point leading to a 'Null' state, then 'Receive\_Open\_Ind'. A decision 'Destination Reference received' follows. If 'OK', it goes to 'Store Destination Reference'. If 'Error', it goes to 'Null'. If 'Vr', it goes to 'Perform MAP Vr Dialogue' (with a note about GSM 09.02 or TS 29.002) then to 'Null'. From 'Store Destination Reference', a decision 'TCAP Handshake required' follows. If 'No', it goes to 'Wait\_For\_Service\_Primitive' then to 'MAP\_DELIMITER\_ind' then to 'MAP\_DELIMITER\_req' then to 'Wait\_For\_Service\_Primitive' then to 'Null'. If 'Yes', it goes to 'Wait\_For\_DELIMITER'. From 'Wait\_For\_DELIMITER', there are four paths: 1) 'MAP\_DELIMITER\_ind' -> 'MAP\_DELIMITER\_req' -> 'Wait\_For\_Service\_Primitive' -> 'Null'; 2) 'MAP\_MT\_FORW\_SW\_ind' -> 'Set Error System Failure' -> 'MAP\_MT\_FORW\_SM\_rsp' -> 'MAP\_CLOSE\_req' -> 'Null'; 3) 'MAP\_DELIMITER\_ind' -> 'MAP\_DELIMITER\_req' -> 'Wait\_For\_Service\_Primitive' -> (join point) -> 'Null'; 4) 'MAP\_NOTICE\_ind' -> 'MAP\_CLOSE\_req' -> 'Null'. A callout 'Figure 25.1/1' is near 'Receive\_Open\_Ind'. + +4144 + +4145 + +**Figure 23.3/10 (sheet 1 of 4): Process MT\_SM\_SGSN** + +![Flowchart for Process MT_SM_SGSN. It starts with 'Wait_For_Service_Primitive', followed by 'MAP_MT_FORWARD_SHORT_MESSAGE_ind'. Then 'Check_Indication' (refer to Figure 25.2/1). An 'OK' path leads to 'MT_SM_Transfer_SGSN' (refer to Figure 23.3/4). From there, three 'CAMEL Handling' decision diamonds are shown. The first 'OK' path leads to 'CAMEL_T_SMS_DELIVERED' (refer to TS 23.078). The second 'Abort' path leads to 'CAMEL_T_SMS_FAILURE' (refer to TS 23.078) and then 'Null'. The third 'Error' path leads to 'CAMEL_T_SMS_FAILURE' (refer to TS 23.078) and then 'Null'. A 'Release SMS' signal is sent from the 'Error' path. After the first 'CAMEL Handling' decision, a 'More messages to send?' decision is made. If 'Yes', it goes to 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_DELIMITER_req', then 'Wait_For_More_Messages'. If 'No', it goes to 'Null'. After the second and third 'CAMEL Handling' decisions, it goes to 'Null'. A 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_CLOSE_req' message is sent before the final 'Null' state.](bf8329bbe3bb1ecee069cfdc92e5b386_img.jpg) + +# Process MT\_SM\_SGSN MT\_SM\_SGSN2(4) + +The mobile terminated short message service process in the SGSN + +Signals to/from the left are to/from the SMS-GMSC + +``` + +graph TD + Start([Wait_For_Service_Primitive]) --> Ind[MAP_MT_FORWARD_SHORT_MESSAGE_ind] + Ind --> Check[Check_Indication] + Check -- OK --> Transfer[MT_SM_Transfer_SGSN] + Transfer --> CH1{CAMEL Handling} + Transfer -- Error --> Release[Release SMS] + CH1 -- OK --> Delivered[CAMEL_T_SMS_DELIVERED] + CH1 -- False --> More{More messages to send?} + Delivered -- True --> TS1[See TS 23.078] + TS1 --> More + More -- Yes --> Rsp1[MAP_MT_FORWARD_SHORT_MESSAGE_rsp +MAP_DELIMITER_req] + Rsp1 --> WaitMore([Wait_For_More_Messages]) + More -- No --> Null1([Null]) + CH1 -- Abort --> CH2{CAMEL Handling} + CH2 -- True --> Failure1[CAMEL_T_SMS_FAILURE] + Failure1 -- True --> TS2[See TS 23.078] + TS2 --> Null2([Null]) + CH2 -- False --> Null1 + CH1 -- Error --> CH3{CAMEL Handling} + CH3 -- True --> Failure2[CAMEL_T_SMS_FAILURE] + Failure2 -- True --> TS3[See TS 23.078] + TS3 --> Null3([Null]) + CH3 -- False --> Null1 + Null1 --> Rsp2[MAP_MT_FORWARD_SHORT_MESSAGE_rsp +MAP_CLOSE_req] + Rsp2 --> Null4([Null]) + +``` + +Flowchart for Process MT\_SM\_SGSN. It starts with 'Wait\_For\_Service\_Primitive', followed by 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ind'. Then 'Check\_Indication' (refer to Figure 25.2/1). An 'OK' path leads to 'MT\_SM\_Transfer\_SGSN' (refer to Figure 23.3/4). From there, three 'CAMEL Handling' decision diamonds are shown. The first 'OK' path leads to 'CAMEL\_T\_SMS\_DELIVERED' (refer to TS 23.078). The second 'Abort' path leads to 'CAMEL\_T\_SMS\_FAILURE' (refer to TS 23.078) and then 'Null'. The third 'Error' path leads to 'CAMEL\_T\_SMS\_FAILURE' (refer to TS 23.078) and then 'Null'. A 'Release SMS' signal is sent from the 'Error' path. After the first 'CAMEL Handling' decision, a 'More messages to send?' decision is made. If 'Yes', it goes to 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_DELIMITER\_req', then 'Wait\_For\_More\_Messages'. If 'No', it goes to 'Null'. After the second and third 'CAMEL Handling' decisions, it goes to 'Null'. A 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_CLOSE\_req' message is sent before the final 'Null' state. + +4146 + +4147 + +Figure 23.3/10 (sheet 2 of 4): Process MT\_SM\_SGSN + +![Flowchart for Process MT_SM_SGSN. It starts with 'Wait_For_More_Messages', followed by 'MAP_MT_FORWARD_SHORT_MESSAGE_ind'. Then 'Check_Indication' (refer to Figure 25.2/1). A decision 'CAMEL Handling' follows. If 'True', 'CAMEL_T_SMS_INIT' (refer to TS 23.078) is called, then 'Result?' is checked. If 'Release_SMS', 'Set Error according to gsmSCF instructions' is done. If 'Continue', 'Gb_RP_MT_DATA_req' is sent. If 'CAMEL Handling' is 'False', it goes to 'Gb_RP_MT_DATA_req'. From 'Gb_RP_MT_DATA_req', it goes to 'Wait_For_Subsequent_Gb_SM_CONFIRM'. Then 'Gb_RP_ERROR_ind' or 'Gb_RP_ACK_ind' is received. If 'Gb_RP_ERROR_ind', 'Set User Error' is done, then 'CAMEL Handling' is checked. If 'True', 'CAMEL_T_SMS_FAILURE' (refer to TS 23.078) is called. If 'False', it goes to 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_CLOSE_req'. If 'Gb_RP_ACK_ind', 'CAMEL Handling' is checked. If 'True', 'CAMEL_T_SMS_DELIVERED' (refer to TS 23.078) is called. Then 'More messages to send?' is checked. If 'Yes', 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_DELIMITER_req' are sent, then back to 'Wait_For_More_Messages'. If 'No', it goes to 'MAP_MT_FORWARD_SHORT_MESSAGE_rsp' and 'MAP_CLOSE_req'. All paths lead to 'Null' at the bottom left.](c83534e2fbfa7d2e2ab5d5e5cc76b6aa_img.jpg) + +### Process MT\_SM\_SGSN + +### MT\_SM\_SGSN3(4) + +The mobile terminated short message service process in the SGSN + +Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MS + +``` + +graph TD + Start([Wait_For_More_Messages]) --> In1{{ }} + In1 --> In1_msg[MAP_MT_FORWARD_SHORT_MESSAGE_ind] + In1 --> Check[Check_Indication] + Check --> Check_note[Figure 25.2/1] + Check --> CH1{CAMEL Handling} + CH1 -- True --> Init[CAMEL_T_SMS_INIT] + Init --> Init_note[See TS 23.078] + Init --> Result{Result?} + Result -- Release_SMS --> SetError[Set Error according to gsmSCF instructions] + Result -- Continue --> GbReq[Gb_RP_MT_DATA_req] + CH1 -- False --> GbReq + GbReq --> WaitSub[Wait_For_Subsequent_Gb_SM_CONFIRM] + WaitSub --> In2{{ }} + In2 --> In2_msg[ ] + In2 --> GbError[Gb_RP_ERROR_ind] + In2 --> GbAck[Gb_RP_ACK_ind] + GbError --> SetUserError[Set User Error] + SetUserError --> CH2{CAMEL Handling} + CH2 -- True --> Failure[CAMEL_T_SMS_FAILURE] + Failure --> Failure_note[See TS 23.078] + CH2 -- False --> Rsp1[MAP_MT_FORWARD_SHORT_MESSAGE_rsp] + Rsp1 --> Close1[MAP_CLOSE_req] + GbAck --> CH3{CAMEL Handling} + CH3 -- True --> Delivered[CAMEL_T_SMS_DELIVERED] + Delivered --> Delivered_note[See TS 23.078] + Delivered --> MoreMsg{More messages to send?} + MoreMsg -- Yes --> Rsp2[MAP_MT_FORWARD_SHORT_MESSAGE_rsp] + Rsp2 --> Delimiter[MAP_DELIMITER_req] + Delimiter --> WaitMore([Wait_For_More_Messages]) + MoreMsg -- No --> Rsp3[MAP_MT_FORWARD_SHORT_MESSAGE_rsp] + Rsp3 --> Close2[MAP_CLOSE_req] + SetError --> Null([Null]) + Close1 --> Null + Close2 --> Null + +``` + +Flowchart for Process MT\_SM\_SGSN. It starts with 'Wait\_For\_More\_Messages', followed by 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ind'. Then 'Check\_Indication' (refer to Figure 25.2/1). A decision 'CAMEL Handling' follows. If 'True', 'CAMEL\_T\_SMS\_INIT' (refer to TS 23.078) is called, then 'Result?' is checked. If 'Release\_SMS', 'Set Error according to gsmSCF instructions' is done. If 'Continue', 'Gb\_RP\_MT\_DATA\_req' is sent. If 'CAMEL Handling' is 'False', it goes to 'Gb\_RP\_MT\_DATA\_req'. From 'Gb\_RP\_MT\_DATA\_req', it goes to 'Wait\_For\_Subsequent\_Gb\_SM\_CONFIRM'. Then 'Gb\_RP\_ERROR\_ind' or 'Gb\_RP\_ACK\_ind' is received. If 'Gb\_RP\_ERROR\_ind', 'Set User Error' is done, then 'CAMEL Handling' is checked. If 'True', 'CAMEL\_T\_SMS\_FAILURE' (refer to TS 23.078) is called. If 'False', it goes to 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_CLOSE\_req'. If 'Gb\_RP\_ACK\_ind', 'CAMEL Handling' is checked. If 'True', 'CAMEL\_T\_SMS\_DELIVERED' (refer to TS 23.078) is called. Then 'More messages to send?' is checked. If 'Yes', 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_DELIMITER\_req' are sent, then back to 'Wait\_For\_More\_Messages'. If 'No', it goes to 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_CLOSE\_req'. All paths lead to 'Null' at the bottom left. + +4148 + +4149 + +Figure 23.3/10 (sheet 3 of 4): Process MT\_SM\_SGSN + +Process MT\_SM\_SGSN + +MT\_SM\_SGSN4(4) + +![SDL diagram for Process MT_SM_SGSN showing state transitions from 'Wait_For_More_Messages' and 'Wait_For_Subsequent_Gb_SM_CONFIRM' to 'NULL'.](30c613511d0b3ee7d8d2f5afb4680c9e_img.jpg) + +The mobile terminated short message service process in the SGSN + +Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MS + +``` + + graph TD + %% Top Section + S1([Wait_For_More_Messages]) + S1 --> In1{ } + In1 -- MAP_U_ABORT_ind +MAP_P_ABORT_ind --> Out1[Gb_LLC_RELEASE_req] + In1 -- MAP_NOTICE_ind --> Out2[MAP_CLOSE_req] + Out2 --> Out3[Gb_LLC_RELEASE_req] + In1 -- Gb_LLC_RELEASE_ind --> Out4[MAP_U_ABORT_req] + Out1 --> N1([NULL]) + Out3 --> N1 + Out4 --> N1 + + %% Bottom Section + S2([Wait_For_Subsequent_Gb_SM_CONFIRM]) + S2 --> In2{ } + In2 -- MAP_U_ABORT_ind +MAP_P_ABORT_ind --> Out5[Gb_LLC_RELEASE_req] + In2 -- MAP_NOTICE_ind --> Out6[MAP_CLOSE_req] + Out6 --> Out7[Gb_LLC_RELEASE_req] + In2 -- Gb_LLC_RELEASE_ind --> Out8[MAP_U_ABORT_req] + + Out5 --> D1{CAMEL Handling} + Out7 --> D1 + Out8 --> D1 + + D1 -- False --> N2([NULL]) + D1 -- True --> C1[CAMEL_T_SMS_FAILURE] + C1 --> N2 + + subgraph Note + C1 -.-> T1[See TS 23.078] + end + +``` + +**Diagram Description:** + +The diagram illustrates two parallel logic flows for the SGSN process: + +- Flow 1:** Starts at state **Wait\_For\_More\_Messages**. + - Receiving **MAP\_U\_ABORT\_ind** or **MAP\_P\_ABORT\_ind** (from left) leads to sending **Gb\_LLC\_RELEASE\_req** (to right) and entering state **NULL**. + - Receiving **MAP\_NOTICE\_ind** (from left) leads to sending **MAP\_CLOSE\_req** (to left) then **Gb\_LLC\_RELEASE\_req** (to right) and entering state **NULL**. + - Receiving **Gb\_LLC\_RELEASE\_ind** (from right) leads to sending **MAP\_U\_ABORT\_req** (to left) and entering state **NULL**. +- Flow 2:** Starts at state **Wait\_For\_Subsequent\_Gb\_SM\_CONFIRM**. It follows the same signal logic as Flow 1 but passes through a **CAMEL Handling** decision point before reaching the **NULL** state. + - If **CAMEL Handling** is *False*, it transitions directly to **NULL**. + - If **CAMEL Handling** is *True*, it executes **CAMEL\_T\_SMS\_FAILURE** (referencing TS 23.078) before transitioning to **NULL**. + +SDL diagram for Process MT\_SM\_SGSN showing state transitions from 'Wait\_For\_More\_Messages' and 'Wait\_For\_Subsequent\_Gb\_SM\_CONFIRM' to 'NULL'. + +4150 + +4151 + +**Figure 23.3/10 (sheet 4 of 4): Process MT\_SM\_SGSN** + +Macrodefinition MT\_SM\_Transfer\_SGSN + +MT\_SM\_Xfer\_SGSN1(3) + +The mobile terminated short message transfer macro in the SGSN + +![Flowchart for MT_SM_Transfer_SGSN macro. It starts with a decision 'SGSN supports MT SMS?'. If 'No', it goes to 'Set User Error: Facility Not Supported'. If 'Yes', it goes to 'Check_Subscriber_Identity_for_MT_SMS'. From there, if 'OK', it checks 'Subscriber known?'. If 'No', it goes to 'Set User Error: Unidentified Subscriber'. If 'Yes', it checks 'Confirmed by HLR?'. If 'No', it goes to 'Set User Error: Unidentified Subscriber'. If 'Yes', it checks 'GPRS detached flag=Detached?'. If 'Yes', it goes to 'Set User Error: Absent subscriber' -> 'Set MNRG' -> 'Release SMS'. If 'No', it checks 'RA Not Allowed flag=Not allowed?'. If 'Yes', it goes to 'Set User Error: Absent subscriber' -> 'Set MNRG' -> 'Release SMS'. If 'No', it goes to 'CAMEL_MT_SMS_SGSN' (with a note 'See TS 23.078'). From 'CAMEL_MT_SMS_SGSN', it goes to 'Result?'. If 'Continue', it goes to 'CAMEL Handling'. If 'CAMEL Handling:= False', it goes to 'Release SMS'. If 'CAMEL Handling:= True', it goes to 'CAMEL_T_SMS_INIT' (with a note 'See TS 23.078'). From 'CAMEL_T_SMS_INIT', it goes to 'Result?'. If 'Release_SMS', it goes to 'Set User Error according to gsmSCF instructions' -> 'Release SMS'. If 'Continue', it goes to 'Release SMS'.](4b7adfd81f4c5c15da852897406fee15_img.jpg) + +``` + +graph TD + Start([Start]) --> Decision1{SGSN supports MT SMS?} + Decision1 -- No --> Error1[Set User Error: Facility Not Supported] + Decision1 -- Yes --> Process1[Check_Subscriber_Identity_for_MT_SMS] + Process1 -- OK --> Decision2{Subscriber known?} + Process1 -- Error --> Error1 + Decision2 -- No --> Error2[Set User Error: Unidentified Subscriber] + Decision2 -- Yes --> Decision3{Confirmed by HLR?} + Decision3 -- No --> Error2 + Decision3 -- Yes --> Decision4{GPRS detached flag=Detached?} + Decision4 -- Yes --> Error3[Set User Error: Absent subscriber] + Decision4 -- No --> Decision5{RA Not Allowed flag=Not allowed?} + Decision5 -- Yes --> Error3 + Decision5 -- No --> Process2[CAMEL_MT_SMS_SGSN] + Note1[See TS 23.078] -.-> Process2 + Process2 -- Continue --> Decision6{Result?} + Decision6 -- Continue --> Decision7{CAMEL Handling} + Decision7 -- "CAMEL Handling:= False" --> ReleaseSMS([Release SMS]) + Decision7 -- "CAMEL Handling:= True" --> Process3[CAMEL_T_SMS_INIT] + Note2[See TS 23.078] -.-> Process3 + Process3 -- Continue --> Decision8{Result?} + Decision8 -- Release_SMS --> Error4[Set User Error according to gsmSCF instructions] + Error4 --> ReleaseSMS + Decision8 -- Continue --> ReleaseSMS + Error3 --> SetMNRG[Set MNRG] + SetMNRG --> ReleaseSMS + Error3 --> Diagnostic[Diagnostic= GPRS detached] + Diagnostic --> ReleaseSMS + +``` + +Flowchart for MT\_SM\_Transfer\_SGSN macro. It starts with a decision 'SGSN supports MT SMS?'. If 'No', it goes to 'Set User Error: Facility Not Supported'. If 'Yes', it goes to 'Check\_Subscriber\_Identity\_for\_MT\_SMS'. From there, if 'OK', it checks 'Subscriber known?'. If 'No', it goes to 'Set User Error: Unidentified Subscriber'. If 'Yes', it checks 'Confirmed by HLR?'. If 'No', it goes to 'Set User Error: Unidentified Subscriber'. If 'Yes', it checks 'GPRS detached flag=Detached?'. If 'Yes', it goes to 'Set User Error: Absent subscriber' -> 'Set MNRG' -> 'Release SMS'. If 'No', it checks 'RA Not Allowed flag=Not allowed?'. If 'Yes', it goes to 'Set User Error: Absent subscriber' -> 'Set MNRG' -> 'Release SMS'. If 'No', it goes to 'CAMEL\_MT\_SMS\_SGSN' (with a note 'See TS 23.078'). From 'CAMEL\_MT\_SMS\_SGSN', it goes to 'Result?'. If 'Continue', it goes to 'CAMEL Handling'. If 'CAMEL Handling:= False', it goes to 'Release SMS'. If 'CAMEL Handling:= True', it goes to 'CAMEL\_T\_SMS\_INIT' (with a note 'See TS 23.078'). From 'CAMEL\_T\_SMS\_INIT', it goes to 'Result?'. If 'Release\_SMS', it goes to 'Set User Error according to gsmSCF instructions' -> 'Release SMS'. If 'Continue', it goes to 'Release SMS'. + +4152 + +4153 + +Figure 23.3/11 (sheet 1 of 3): Macro MT\_SM\_TRANSFER\_SGSN + +Macrodefinition MT\_SM\_Transfer\_SGSN + +MT\_SM\_Xfer\_SGSN2(3) + +The mobile terminated short message transfer macro in the SGSN + +Signals to/from the right are to/from the MS + +![Flowchart for Macro MT_SM_Transfer_SGSN. It starts at connector 1, checks if confirmed by radio contact. If not confirmed, it goes to Search_SMS_SGSN. If confirmed, it checks if RAI is known. If No, it goes to Search_SMS_SGSN. If Yes, it goes to Page_SMS_SGSN. Both lead to a Result decision. If Pass, it checks if MS supports SMS. If No, it sends Gb_LLC_RELEASE_req and ends at Error. If Yes, it sends Gb_RP_MT_DATA_req, waits for confirmation, receives Gb_RP_ACK_ind, and ends at OK. If Result is Fail, it checks for Error. If Absent Subscriber, it sets User Error: Absent Subscriber, sets MNRG, and ends at Error. Else, it sets User Error and ends at Error. A note indicates signals to/from the right are to/from the MS.](1f3c29c51892700d40eaee37ed6b870c_img.jpg) + +``` + +graph TD + 1((1)) --> C1{Confirmed by radio contact} + C1 -- Not confirmed --> S[Search_SMS_SGSN] + C1 -- Confirmed --> R1{RAI known?} + R1 -- No --> S + R1 -- Yes --> P[Page_SMS_SGSN] + P --> Res1{Result} + S --> Res2{Result} + Res1 -- Fail --> 2((2)) + Res1 -- Pass --> MS{MS supports SMS?} + Res2 -- Pass --> MS + Res2 -- Fail --> Err{Error} + Err -- Else --> SetErr[Set User Error] + Err -- Absent Subscriber --> SetErrSub[Set User Error: Absent Subscriber] + SetErrSub --> SetMNRG[Set MNRG] + SetMNRG --> Error((Error)) + SetErr --> Error + MS -- No --> GbLLC[Gb_LLC_RELEASE_req] + GbLLC --> SetErrFail[Set User Error: SM delivery failure] + SetErrFail --> FailCause[Delivery failure cause:= Equipment not SM equipped] + SetErrFail --> Error + MS -- Yes --> GbRPMT[Gb_RP_MT_DATA_req] + GbRPMT --> Wait[Wait_For_First_Gb_SM_Confirm] + Wait --> GbRPACK{Gb_RP_ACK_ind} + Wait --> GbRPERROR{Gb_RP_ERROR_ind} + GbRPACK --> OK((OK)) + GbRPERROR --> SetErr2[Set User Error] + SetErr2 --> Error + +``` + +Flowchart for Macro MT\_SM\_Transfer\_SGSN. It starts at connector 1, checks if confirmed by radio contact. If not confirmed, it goes to Search\_SMS\_SGSN. If confirmed, it checks if RAI is known. If No, it goes to Search\_SMS\_SGSN. If Yes, it goes to Page\_SMS\_SGSN. Both lead to a Result decision. If Pass, it checks if MS supports SMS. If No, it sends Gb\_LLC\_RELEASE\_req and ends at Error. If Yes, it sends Gb\_RP\_MT\_DATA\_req, waits for confirmation, receives Gb\_RP\_ACK\_ind, and ends at OK. If Result is Fail, it checks for Error. If Absent Subscriber, it sets User Error: Absent Subscriber, sets MNRG, and ends at Error. Else, it sets User Error and ends at Error. A note indicates signals to/from the right are to/from the MS. + +4154 + +4155 + +Figure 23.3/11 (sheet 2 of 3): Macro MT\_SM\_TRANSFER\_SGSN + +Macrodefinition MT\_SM\_Transfer\_SGSN + +MT\_SM\_Xfer\_SGSN3(3) + +The mobile terminated short message transfer macro in the SGSN + +Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MS + +![State transition diagram for MT_SM_Transfer_SGSN macro. It starts with a 'Wait_For_First_Gb_SM_Confirm' state. Transitions include 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req' and then to 'Gb_LLC_RELEASE_req' (which leads to 'Abort'); 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' leading to 'Gb_LLC_RELEASE_req'; and 'Gb_LLC_RELEASE_ind' leading to 'Set User Error: System failure' (which leads to 'Error').](00f437f8c15ec7fd05fc003781d92db0_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Wait_For_First_Gb_SM_Confirm + state "Wait_For_First_Gb_SM_Confirm" as Wait_For_First_Gb_SM_Confirm + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" as MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind + state "Gb_LLC_RELEASE_ind" as Gb_LLC_RELEASE_ind + state "Gb_LLC_RELEASE_req" as Gb_LLC_RELEASE_req + state "Set User Error: System failure" as Set_User_Error_System_failure + state "Abort" as Abort + state "Error" as Error + + Wait_For_First_Gb_SM_Confirm --> MAP_NOTICE_ind + Wait_For_First_Gb_SM_Confirm --> MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind + Wait_For_First_Gb_SM_Confirm --> Gb_LLC_RELEASE_ind + + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Gb_LLC_RELEASE_req + Gb_LLC_RELEASE_req --> Abort + + MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind --> Gb_LLC_RELEASE_req + + Gb_LLC_RELEASE_ind --> Set_User_Error_System_failure + Set_User_Error_System_failure --> Error + +``` + +State transition diagram for MT\_SM\_Transfer\_SGSN macro. It starts with a 'Wait\_For\_First\_Gb\_SM\_Confirm' state. Transitions include 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req' and then to 'Gb\_LLC\_RELEASE\_req' (which leads to 'Abort'); 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' leading to 'Gb\_LLC\_RELEASE\_req'; and 'Gb\_LLC\_RELEASE\_ind' leading to 'Set User Error: System failure' (which leads to 'Error'). + +4156 + +4157 + +Figure 23.3/11 (sheet 3 of 3): Macro MT\_SM\_TRANSFER\_SGSN + +Procedure Page\_SMS\_SGSN + +Page\_SMS\_SGSN1(1) + +Procedure in the SGSN to page an MS for MT SMS delivery + +Signals to/from the right are to/from the MS + +![Flowchart for Procedure Page_SMS_SGSN. It starts with a decision 'MS connection exists?'. If 'Yes', it goes to 'Result= Pass' and ends. If 'No', it sends 'Gb_PAGE_REQUEST' (noted as being in the specified routing area), then 'Wait_For_Page_Response'. From there, it branches into 'Gb_PAGE_RESPONSE' (leading to 'Result= Pass'), 'Gb_NO_PAGE_RESPONSE' (leading to 'Error:= Absent subscriber' then 'Result= Fail'), or a default path (marked with '*'). All three paths end with connector symbols.](9c9b18de18babe304d651d5648864315_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{MS connection exists?}; Decision -- Yes --> ResultPass1[Result= Pass]; ResultPass1 --> End1(( )); Decision -- No --> Request[Gb_PAGE_REQUEST]; Note1[In specified routing area] -.-> Request; Request --> Wait[Wait_For_Page_Response]; Wait --> ResponseGb[Gb_PAGE_RESPONSE]; Wait --> NoResponseGb[Gb_NO_PAGE_RESPONSE]; Wait --> Default[*]; ResponseGb --> ResultPass2[Result= Pass]; ResultPass2 --> End2(( )); NoResponseGb --> Error[Error:= Absent subscriber]; Error --> ResultFail[Result= Fail]; ResultFail --> End3(( )); Default --> End4(( )); +``` + +Flowchart for Procedure Page\_SMS\_SGSN. It starts with a decision 'MS connection exists?'. If 'Yes', it goes to 'Result= Pass' and ends. If 'No', it sends 'Gb\_PAGE\_REQUEST' (noted as being in the specified routing area), then 'Wait\_For\_Page\_Response'. From there, it branches into 'Gb\_PAGE\_RESPONSE' (leading to 'Result= Pass'), 'Gb\_NO\_PAGE\_RESPONSE' (leading to 'Error:= Absent subscriber' then 'Result= Fail'), or a default path (marked with '\*'). All three paths end with connector symbols. + +4158 + +4159 + +Figure 23.3/12 (sheet 1 of 1): Procedure Page\_SMS\_SGSN + +Procedure Search\_SMS\_SGSN + +Search\_SMS\_SGSN1(1) + +Procedure in the SGSN to search for an MS for MT SMS delivery + +Signals to/from the right are to/from the MS + +![Flowchart for Search_SMS_SGSN procedure. It starts with a connector, followed by a decision 'MS connection exists?'. If 'Yes', it goes to 'Result= Pass' and then a connector. If 'No', it goes to 'Gb_PAGE_REQUEST' (with a note 'In all routing areas'), then 'Wait_For_Search_Response'. From there, it branches into 'Gb_PAGE_RESPONSE' (leading to 'Update LAI' and 'Result= Pass'), 'Gb_NO_PAGE_RESPONSE' (leading to 'Error:= Absent subscriber' and 'Result= Fail'), or a general connector.](56e90393ca2226804734e447812d148b_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{MS connection exists?}; Decision -- Yes --> ResultPass1[Result= Pass]; ResultPass1 --> Connector1(( )); Decision -- No --> GbPAGE[Gb_PAGE_REQUEST]; Note1[In all routing areas] -.-> GbPAGE; GbPAGE --> Wait[Wait_For_Search_Response]; Wait --> GbPAGE_RESP[Gb_PAGE_RESPONSE]; Wait --> GbNOPAGE_RESP[Gb_NO_PAGE_RESPONSE]; Wait --> Asterisk[/ * /]; GbPAGE_RESP --> UpdateLAI[Update LAI]; UpdateLAI --> ResultPass2[Result= Pass]; ResultPass2 --> Connector2(( )); GbNOPAGE_RESP --> Error[Error:= Absent subscriber]; Error --> ResultFail[Result= Fail]; ResultFail --> Connector3(( )); +``` + +Flowchart for Search\_SMS\_SGSN procedure. It starts with a connector, followed by a decision 'MS connection exists?'. If 'Yes', it goes to 'Result= Pass' and then a connector. If 'No', it goes to 'Gb\_PAGE\_REQUEST' (with a note 'In all routing areas'), then 'Wait\_For\_Search\_Response'. From there, it branches into 'Gb\_PAGE\_RESPONSE' (leading to 'Update LAI' and 'Result= Pass'), 'Gb\_NO\_PAGE\_RESPONSE' (leading to 'Error:= Absent subscriber' and 'Result= Fail'), or a general connector. + +4160 + +4161 + +Figure 23.3/13 (sheet 1 of 1): Procedure Search\_SMS\_SGSN + +process MT\_SM\_SMS\_ROUTER + +1(4) + +Process in the SMS Router to handle delivery of an MT short message + +Signals to/from the left are to/from the HLR +Signals to/from the right are to/from the SMS-GMSC + +![Flowchart for process MT_SM_SMS_ROUTER. The process starts with a 'Null' terminal, followed by a 'MAP_SEND_ROUTING_INFO_FOR_SM_ind' input. It then enters a 'Check_Indication' block. If 'Error', it goes to an 'Error' terminal. If 'OK', it reaches connector 'A'. From connector 'A', it goes to a decision 'SM-Delivery Not Intended'. If 'yes', it checks if 'more than one MCC/MNC allocated for this PLMN'. If 'yes', it goes to connector 'B'. If 'no', it checks if 'only MCC-MNC requested'. If 'yes', it goes to connector 'B'. If 'no', it goes to connector 'A'. If 'no' from the first decision, it goes to 'Set all MAP parameters as received', then sends 'MAP_OPEN_req', 'MAP_SEND_ROUTING_INFO_FOR_SM_req', and 'MAP_DELIMITER_req'. It then 'Receive_Open_Cnf'. If 'Error', it goes to an 'Error' terminal. If 'OK', it goes to 'Wait_For_Routing_Info'. From there, it branches into three paths: 'MAP_NOTICE_ind' -> 'MAP_CLOSE_req'; 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind'; and 'MAP_SEND_ROUTING_INFO_FOR_SM_cnf' -> 'Check_Confirmation'. All three paths lead to a second 'SM-Delivery Not Intended' decision. If 'yes', it goes to connector 'B'. If 'no', it checks if 'only MCC-MNC requested'. If 'yes', it goes to connector 'B'. If 'no', it goes to connector 'C'. The 'MAP_CLOSE_req' path also leads to 'MAP_SEND_ROUTING_INFO_FOR_SM_rsp' and 'MAP_CLOSE_req' output, which then leads to a 'Null' terminal. An 'Error' terminal is also shown on the left side.](6cb9708fe557402511bdf7de0dccf3e5_img.jpg) + +``` + +graph TD + Start([Null]) --> Input1{{MAP_SEND_ROUTING_INFO_FOR_SM_ind}} + Input1 --> CheckInd[Check_Indication] + CheckInd -- Error --> Error1((Error)) + CheckInd -- OK --> A1((A)) + A1 --> Dec1{SM-Delivery Not Intended} + Dec1 -- yes --> MoreMCC{more than one MCC/MNC allocated for this PLMN} + MoreMCC -- yes --> B1((B)) + MoreMCC -- no --> OnlyMCC{only MCC-MNC requested} + OnlyMCC -- yes --> B1 + OnlyMCC -- no --> A1 + Dec1 -- no --> SetParams[Set all MAP parameters as received] + SetParams --> Output1{{MAP_OPEN_req +MAP_SEND_ROUTING_INFO_FOR_SM_req +MAP_DELIMITER_req}} + Output1 --> RecvCnf[Receive_Open_Cnf] + RecvCnf -- Error --> Error2((Error)) + RecvCnf -- OK --> WaitInfo[Wait_For_Routing_Info] + WaitInfo --> NoticeInd{{MAP_NOTICE_ind}} + WaitInfo --> AbortInd{{MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind}} + WaitInfo --> SendCnf{{MAP_SEND_ROUTING_INFO_FOR_SM_cnf}} + NoticeInd --> CloseReq1{{MAP_CLOSE_req}} + SendCnf --> CheckConf[Check_Confirmation] + CloseReq1 --> Dec2{SM-Delivery Not Intended} + AbortInd --> Dec2 + CheckConf --> Dec2 + Dec2 -- yes --> B2((B)) + Dec2 -- no --> OnlyMCC2{only MCC-MNC requested} + OnlyMCC2 -- yes --> B2 + OnlyMCC2 -- no --> C((C)) + CloseReq1 --> Output2{{MAP_SEND_ROUTING_INFO_FOR_SM_rsp +MAP_CLOSE_req}} + Output2 --> Null2([Null]) + SendCnf -- no --> AllocateID[Allocate MT Correlation ID] + AllocateID --> 1((1)) + +``` + +Flowchart for process MT\_SM\_SMS\_ROUTER. The process starts with a 'Null' terminal, followed by a 'MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_ind' input. It then enters a 'Check\_Indication' block. If 'Error', it goes to an 'Error' terminal. If 'OK', it reaches connector 'A'. From connector 'A', it goes to a decision 'SM-Delivery Not Intended'. If 'yes', it checks if 'more than one MCC/MNC allocated for this PLMN'. If 'yes', it goes to connector 'B'. If 'no', it checks if 'only MCC-MNC requested'. If 'yes', it goes to connector 'B'. If 'no', it goes to connector 'A'. If 'no' from the first decision, it goes to 'Set all MAP parameters as received', then sends 'MAP\_OPEN\_req', 'MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_req', and 'MAP\_DELIMITER\_req'. It then 'Receive\_Open\_Cnf'. If 'Error', it goes to an 'Error' terminal. If 'OK', it goes to 'Wait\_For\_Routing\_Info'. From there, it branches into three paths: 'MAP\_NOTICE\_ind' -> 'MAP\_CLOSE\_req'; 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind'; and 'MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_cnf' -> 'Check\_Confirmation'. All three paths lead to a second 'SM-Delivery Not Intended' decision. If 'yes', it goes to connector 'B'. If 'no', it checks if 'only MCC-MNC requested'. If 'yes', it goes to connector 'B'. If 'no', it goes to connector 'C'. The 'MAP\_CLOSE\_req' path also leads to 'MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_rsp' and 'MAP\_CLOSE\_req' output, which then leads to a 'Null' terminal. An 'Error' terminal is also shown on the left side. + +4162 + +4163 + +Figure 23.3/14 (sheet 1 of 4): Process MT\_SM\_SMS\_ROUTER + +process MT\_SM\_SMS\_ROUTER + +2(4) + +Process in the SMS Router to handle delivery of an MT short message + +Signals to/from the left are to/from the HLR +Signals to/from the right are to/from the SMS-GMSC + +![Flowchart for process MT_SM_SMS_ROUTER. It starts with 'Start Timer T1', followed by 'Store required MAP parameters against MT Correlation ID'. Then it branches into three 'Set parameters' blocks (B, C, and a central one) with specific parameter details. These merge into 'MAP_SEND_ROUTING_INFO_FOR_SM_rsp', which leads to 'Wait_For_INFORM_SC'. From there, it branches into four paths: 'MAP_CLOSE_ind' leading to 'MAP_INFORM_SERVICE_CENTRE_req' then 'MAP_CLOSE_req' then a decision 'SM-Delivery Not Intended' (yes leads to 'Null', no leads to 'Wait_For_Short_Message'); 'MAP_INFORM_SERVICE_CENTRE_ind' leading to 'MAP_INFORM_SERVICE_CENTRE_req'; 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req' then 'Stop Timer T1' then 'Release MT Correlation ID' then 'Error'; and 'Timer Expiry T1' leading to 'Internal'.](7885090ca50e88f1ee27fa0f1211b0be_img.jpg) + +``` + +graph TD + Start((1)) --> StartTimer[Start Timer T1] + StartTimer --> StoreParams[Store required MAP parameters against MT Correlation ID] + StoreParams --> Merge1(( )) + Merge1 --> B[Set parameters] + Merge1 --> C[Set parameters] + Merge1 --> Central[Set parameters] + B --> BParam[parameter IMSI is populated with MCC+MNC+ dummy MSIN] + C --> CParam[parameter networkNodeNumber is populated with a dummy value] + Central --> CentralParam[parameter IMSI is populated with MT Correlation ID] + BParam --> Merge2(( )) + CParam --> Merge2 + CentralParam --> Merge2 + Merge2 --> MAPSend[MAP_SEND_ROUTING_INFO_FOR_SM_rsp] + MAPSend --> WaitInform[Wait_For_INFORM_SC] + WaitInform --> Merge3(( )) + Merge3 --> MAPCloseInd[MAP_CLOSE_ind] + Merge3 --> MAPInformCentreInd[MAP_INFORM_SERVICE_CENTRE_ind] + Merge3 --> MAPNoticeInd[MAP_NOTICE_ind] + Merge3 --> TimerExpiry[Timer Expiry T1] + MAPCloseInd --> MAPInformCentreReq[MAP_INFORM_SERVICE_CENTRE_req] + MAPInformCentreReq --> MAPCloseReq1[MAP_CLOSE_req] + MAPCloseReq1 --> SMDeliveryNotIntended{SM-Delivery Not Intended} + SMDeliveryNotIntended -- yes --> Null[Null] + SMDeliveryNotIntended -- no --> WaitForShortMessage[Wait_For_Short_Message] + MAPInformCentreInd --> MAPInformCentreReq2[MAP_INFORM_SERVICE_CENTRE_req] + MAPNoticeInd --> MAPCloseReq2[MAP_CLOSE_req] + MAPCloseReq2 --> StopTimer[Stop Timer T1] + StopTimer --> ReleaseMT[Release MT Correlation ID] + ReleaseMT --> Error((Error)) + TimerExpiry --> Internal[Internal] + +``` + +Flowchart for process MT\_SM\_SMS\_ROUTER. It starts with 'Start Timer T1', followed by 'Store required MAP parameters against MT Correlation ID'. Then it branches into three 'Set parameters' blocks (B, C, and a central one) with specific parameter details. These merge into 'MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_rsp', which leads to 'Wait\_For\_INFORM\_SC'. From there, it branches into four paths: 'MAP\_CLOSE\_ind' leading to 'MAP\_INFORM\_SERVICE\_CENTRE\_req' then 'MAP\_CLOSE\_req' then a decision 'SM-Delivery Not Intended' (yes leads to 'Null', no leads to 'Wait\_For\_Short\_Message'); 'MAP\_INFORM\_SERVICE\_CENTRE\_ind' leading to 'MAP\_INFORM\_SERVICE\_CENTRE\_req'; 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req' then 'Stop Timer T1' then 'Release MT Correlation ID' then 'Error'; and 'Timer Expiry T1' leading to 'Internal'. + +4164 + +4165 + +Figure 23.3/14 (sheet 2 of 4): Process MT\_SM\_SMS\_ROUTER + +![Large black redacted area covering the main diagram content.](c36484ee30def42acfc0ed11c6a03ced_img.jpg) + +A large rectangular black box covers the majority of the page, redacting the content of the diagram. Only the title and footer information remain visible. + +Large black redacted area covering the main diagram content. + +![Partial diagram elements visible at the bottom of the redacted area, including a downward arrow.](57ccddd121f0e37792e0ef451fc683de_img.jpg) + +At the bottom of the redacted area, there are several small, partially visible elements. On the left, a small orange rectangle has a downward-pointing arrow below it. In the center, there is a horizontal line. On the right, there is a small, light-colored rounded shape. + +Partial diagram elements visible at the bottom of the redacted area, including a downward arrow. + +4166 + +4167 + +**Figure 23.3/14 (sheet 3 of 4): Process MT\_SM\_ SMS\_ROUTER** + +![State transition diagram for process MT_SM_SMS_ROUTER. It shows various states (Transparent, Set IMSI, Start Timer T1, Wait for Short_Message, Null, Exit) and transitions between them based on MAP messages like MAP_MT_FORWARD_SHORT_MESSAGE_cnf, MAP_DELIMITER_ind, and MAP_CLOSE_ind. The diagram includes decision points for 'Success?' and 'Retry expected'.](18884d42b9bf346a68c7f1b9a02a5a4c_img.jpg) + +**process MT\_SM\_SMS\_ROUTER** 4(4) + +Process in the SMS Router to handle delivery of an MT short message + +Signals to/from the left are to/from the SMS-GMSC +Signals to/from the right are to/from the MSC/SGSN + +``` + +stateDiagram-v2 + [*] --> Transparent1: Transparent + Transparent1 --> MAP_MT_FORWARD_SHORT_MESSAGE_cnf + MAP_MT_FORWARD_SHORT_MESSAGE_cnf --> MAP_DELIMITER_ind + MAP_DELIMITER_ind --> MAP_CLOSE_ind + MAP_CLOSE_ind --> Success{Success?} + Success -- No --> RetryExpected{Retry expected} + Success -- Yes --> Exit((Exit)) + RetryExpected -- No --> Exit + RetryExpected -- Yes --> StartTimerT1: Start Timer T1 + StartTimerT1 --> WaitForShortMessage: Wait for Short_Message + WaitForShortMessage --> [*] + MAP_DELIMITER_ind --> MAP_DELIMITER_req + MAP_DELIMITER_req --> MAP_MT_FORWARD_SHORT_MESSAGE_rsp + MAP_MT_FORWARD_SHORT_MESSAGE_rsp --> Transparent2: Transparent + Transparent2 --> MAP_MT_FORWARD_SHORT_MESSAGE_ind + MAP_MT_FORWARD_SHORT_MESSAGE_ind --> SetIMSI: Set IMSI + SetIMSI --> MAP_MT_FORWARD_SHORT_MESSAGE_req_MAP_DELIMITER_req: MAP_MT_FORWARD_SHORT_MESSAGE_req, MAP_DELIMITER_req + MAP_MT_FORWARD_SHORT_MESSAGE_req_MAP_DELIMITER_req --> Transparent3: Transparent + Exit --> ReleaseMTCorrelationID: Release MT Correlation ID + ReleaseMTCorrelationID --> Null: Null + +``` + +State transition diagram for process MT\_SM\_SMS\_ROUTER. It shows various states (Transparent, Set IMSI, Start Timer T1, Wait for Short\_Message, Null, Exit) and transitions between them based on MAP messages like MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_cnf, MAP\_DELIMITER\_ind, and MAP\_CLOSE\_ind. The diagram includes decision points for 'Success?' and 'Retry expected'. + +4168 + +4169 + +Figure 23.3/14 (sheet 4 of 4): Process MT\_SM\_ SMS\_ROUTER + +process MT\_SM\_IPSMGW + +1(3) + +Process in the IP-SM-GW to handle delivery of an MT short message + +Signals to/from the left are to/from the HLR +Signals to/from the right are to/from the S-CSCF + +![Flowchart for process MT_SM_IPSMGW showing the logic for handling MT short messages, including routing checks, MAP signaling, and error handling.](86da052b1b6a67f928c0c66c0e083aba_img.jpg) + +``` + +graph TD + Start([Null]) --> Null1([Null]) + Null1 --> MAP_SEND_ROUTING_INFO_FOR_SM_ind[MAP_SEND_ROUTING_INFO_FOR_SM_ind] + MAP_SEND_ROUTING_INFO_FOR_SM_ind --> SM_Delivery_Not_Intended{SM-Delivery Not Intended} + SM_Delivery_Not_Intended -- no --> Null1 + SM_Delivery_Not_Intended -- yes --> MoreThanOneMCCMNC{more than one MCC/MNC pair allocated for this PLMN} + MoreThanOneMCCMNC -- yes --> OnlyMCCMNC{only MCC-MNC requested} + MoreThanOneMCCMNC -- no --> SetAllMAP[set all MAP parameter as received] + OnlyMCCMNC -- yes --> B((B)) + OnlyMCCMNC -- no --> SetAllMAP + SetAllMAP --> MAP_OPEN_req[MAP_OPEN_req +MAP_SEND_ROUTING_INFO_FOR_SM_req +MAP_DELIMITER_req] + MAP_OPEN_req --> Receive_Open_Cnf[Receive_Open_Cnf] + Receive_Open_Cnf -- OK --> Wait_For_Routing_Info[Wait_For_Routing_Info] + Receive_Open_Cnf -- Error --> Error((Error)) + Wait_For_Routing_Info --> MAP_NOTICE_ind[MAP_NOTICE_ind] + Wait_For_Routing_Info --> MAP_U_ABORT_ind[MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind] + Wait_For_Routing_Info --> MAP_SEND_ROUTING_INFO_FOR_SM_cnf[MAP_SEND_ROUTING_INFO_FOR_SM_cnf] + MAP_NOTICE_ind --> MAP_SEND_ROUTING_INFO_FOR_SM_rsp[MAP_SEND_ROUTING_INFO_FOR_SM_rsp +MAP_CLOSE_req] + MAP_SEND_ROUTING_INFO_FOR_SM_rsp --> Null2([Null]) + MAP_U_ABORT_ind --> Error + MAP_CLOSE_ind --> Error + MAP_SEND_ROUTING_INFO_FOR_SM_cnf --> Check_Confirmation[Check_Confirmation] + Check_Confirmation -- OK --> 1((1)) + Check_Indication[Check_Indication] -- OK --> A((A)) + Check_Indication -- Error --> Error + A --> SM_Delivery_Not_Intended + B --> SetAllMAP + +``` + +Flowchart for process MT\_SM\_IPSMGW showing the logic for handling MT short messages, including routing checks, MAP signaling, and error handling. + +4170 + +4171 + +Figure 23.3/15 (sheet 1 of 3): Process MT\_SM\_IPSMGW + +process MT\_SM\_IPSMGW + +2(3) + +Process in the IP-SM-GW to handle delivery of an MT short message + +Signals to/from the left are to/from the HLR +Signals to/from the right are to/from the S-CSCF + +![Flowchart for process MT_SM_IPSMGW. It starts with a circle '1' leading to 'Set parameter' (parameter network node number is populated with the IP-SM-GW address). A circle 'B' leads to 'Set parameter' (parameter IMSI is populated with MCC+MNC+ dummy MSIN). Both lead to 'MAP_SEND_ROUTING_INFO_FOR_SM_rsp', which leads to 'Wait For INFORM_SC'. From there, it branches into three paths: 'MAP_CLOSE_ind' leading to 'MAP_INFORM_SERVICE_CENTRE_req' leading to 'MAP_CLOSE_req'; 'MAP_INFORM_SERVICE_CENTRE_ind' leading to 'MAP_INFORM_SERVICE_CENTRE_req' leading to 'MAP_CLOSE_req'; and 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req'. All three 'MAP_CLOSE_req' paths lead to a decision 'SM-Delivery Not Intended'. If 'yes', it goes to 'NULL'. If 'no', it goes to 'Wait_For_Short_Message'. An 'Error' circle is also shown as a terminal state.](5082fe2ab14161df495765246fdacfcf_img.jpg) + +``` + +graph TD + 1((1)) --> SP1[Set parameter] + SP1 --> SP1_desc[parameter network node number is populated with the IP-SM-GW address] + B((B)) --> SP2[Set parameter] + SP2 --> SP2_desc[parameter IMSI is populated with MCC+MNC+ dummy MSIN] + SP1_desc --> MR[MAP_SEND_ROUTING_INFO_FOR_SM_rsp] + SP2_desc --> MR + MR --> WFIS[Wait For INFORM_SC] + WFIS --> MC_ind[MAP_CLOSE_ind] + WFIS --> ISC_ind[MAP_INFORM_SERVICE_CENTRE_ind] + WFIS --> MN_ind[MAP_NOTICE_ind] + MC_ind --> ISC_req[MAP_INFORM_SERVICE_CENTRE_req] + ISC_ind --> ISC_req + MN_ind --> MC_req[MAP_CLOSE_req] + ISC_req --> MC_req + MC_req --> SNI{SM-Delivery Not Intended} + SNI -- yes --> NULL[NULL] + SNI -- no --> WFM[Wait_For_Short_Message] + MN_ind --> Error((Error)) + +``` + +Flowchart for process MT\_SM\_IPSMGW. It starts with a circle '1' leading to 'Set parameter' (parameter network node number is populated with the IP-SM-GW address). A circle 'B' leads to 'Set parameter' (parameter IMSI is populated with MCC+MNC+ dummy MSIN). Both lead to 'MAP\_SEND\_ROUTING\_INFO\_FOR\_SM\_rsp', which leads to 'Wait For INFORM\_SC'. From there, it branches into three paths: 'MAP\_CLOSE\_ind' leading to 'MAP\_INFORM\_SERVICE\_CENTRE\_req' leading to 'MAP\_CLOSE\_req'; 'MAP\_INFORM\_SERVICE\_CENTRE\_ind' leading to 'MAP\_INFORM\_SERVICE\_CENTRE\_req' leading to 'MAP\_CLOSE\_req'; and 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req'. All three 'MAP\_CLOSE\_req' paths lead to a decision 'SM-Delivery Not Intended'. If 'yes', it goes to 'NULL'. If 'no', it goes to 'Wait\_For\_Short\_Message'. An 'Error' circle is also shown as a terminal state. + +4172 + +4173 + +Figure 23.3/15 (sheet 2 of 3): Process MT\_SM\_IPSMGW + +process MT\_SM\_IPSMGW + +3(3) + +Process in the IP-SM-GW to handle delivery of an MT short message + +Signals to/from the left are to/from the SMS-GMSC +Signals to/from the right are to/from the S-CSCF + +![Flowchart for process MT_SM_IPSMGW showing the sequence of operations for delivering an MT short message, including waiting for a message, receiving an indication, checking indications, delivering the SM, and handling responses.](12c19535683984538a011e6fd053c7cd_img.jpg) + +``` + +graph TD + Start([Wait_For_Short_Message]) --> Recv[Receive_Open_ind] + Recv -- OK --> WaitSvc[Wait_For_Service_Primitive] + Recv -- Error --> MAPClose[MAP-CLOSE_req] + MAPClose --> Null1([Null]) + WaitSvc --> MAPForward[MAP_MT_FORWARD_SM_ind] + MAPForward --> Check[Check_Indication] + Check -- OK --> Deliver[Deliver SM] + Check -- Error --> MAPRsp[MAP_MT_FORWARD_SM_rsp] + Deliver --> WaitResp[Wait For Response] + WaitResp -- positive response --> MAPRsp + WaitResp -- negative response --> Decision{delivery via alternative domain successful?} + Decision -- yes --> MAPRsp + Decision -- no --> SetUNR1[set UNR1] + SetUNR1 --> SetError[set error Absent Subscriber SM] + SetError --> MAPRsp + MAPRsp --> Report[Report_SM_Delivery_Stat_IPSMGW] + Report --> Null2([Null]) + +``` + +Flowchart for process MT\_SM\_IPSMGW showing the sequence of operations for delivering an MT short message, including waiting for a message, receiving an indication, checking indications, delivering the SM, and handling responses. + +4174 + +4175 + +Figure 23.3/15 (sheet 3 of 3): Process MT\_SM\_IPSMGW + +4176 **23.4 The Short Message Alert procedure** + +4177 The Short Message Alert procedure is used to alert the Service Centre when the mobile subscriber is active after a short + 4178 message transfer has failed because the mobile subscriber is not reachable, or when the MS has indicated that it has + 4179 memory capacity to accept a short message. + +4180 The message flow for the Short Message Alert procedure for the case when the mobile subscriber was not reachable is + 4181 shown in figure 23.4/1. + +![Sequence diagram for Short Message Alert procedure (Mobile is present). Lifelines: MS, Serving MSC or SGSN, VLR, HLR, Interworking MSC, SC. The sequence shows messages 1 through 7 being exchanged between these entities to alert the Service Centre.](40eb71118a3bf2b8136e6fec828d0a9c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Serving MSC or SGSN + participant VLR + participant HLR + participant Interworking MSC + participant SC + + Note left of MS: 1) CM Service Request (**), Page response or Location Updating (3GPP TS 24.008 [35]). + MS->>Serving MSC or SGSN: 1) + Note left of Serving MSC or SGSN: 2) MAP_PROCESS_ACCESS_REQUEST / MAP_UPDATE_LOCATION_AREA (**). + Serving MSC or SGSN->>VLR: 2) + Note left of VLR: 3) MAP_READY_FOR_SM (Mobile Present) / MAP_UPDATE_LOCATION / Supplementary Service Control Request (*). + VLR->>HLR: 3) + Note left of HLR: 4) MAP_READY_FOR_SM_ACK (*). + HLR->>VLR: 4) + Note left of HLR: 5) MAP_ALERT_SERVICE_CENTRE (notes 1 and 2). + HLR->>Interworking MSC: 5) + Note left of Interworking MSC: 6) Alert Service Centre (3GPP TS 23.040). + Interworking MSC->>SC: 6) + Note left of Interworking MSC: 5) + Interworking MSC->>Interworking MSC: 5) + Note left of Interworking MSC: 6) + Interworking MSC->>SC: 6) + Note left of Interworking MSC: 5) + Interworking MSC->>Interworking MSC: 5) + Note left of Interworking MSC: 6) + Interworking MSC->>SC: 6) + Note left of Interworking MSC: 7) MAP_ALERT_SERVICE_CENTRE_ACK. + Interworking MSC->>HLR: 7) + Note left of HLR: 7) + HLR->>HLR: 7) + Note left of HLR: 7) + HLR->>HLR: 7) + +``` + +Sequence diagram for Short Message Alert procedure (Mobile is present). Lifelines: MS, Serving MSC or SGSN, VLR, HLR, Interworking MSC, SC. The sequence shows messages 1 through 7 being exchanged between these entities to alert the Service Centre. + +- 4182 +- 4183 + - 4184 1) CM Service Request (\*\*), Page response or Location Updating (3GPP TS 24.008 [35]). + - 4185 2) MAP\_PROCESS\_ACCESS\_REQUEST / MAP\_UPDATE\_LOCATION\_AREA (\*\*). + - 4186 3) MAP\_READY\_FOR\_SM (Mobile Present) / MAP\_UPDATE\_LOCATION / + - 4187 Supplementary Service Control Request (\*). + - 4188 4) MAP\_READY\_FOR\_SM\_ACK (\*). + - 4189 5) MAP\_ALERT\_SERVICE\_CENTRE (notes 1 and 2). + - 4190 6) Alert Service Centre (3GPP TS 23.040). + - 4191 7) MAP\_ALERT\_SERVICE\_CENTRE\_ACK. + - 4192 NOTE 1: To all Service Centres in the Message Waiting List. + - 4193 NOTE 2: The HLR initiates the MAP\_ALERT\_SERVICE\_CENTRE service only if the MS Memory Capacity + - 4194 Exceeded flag is clear. + - 4195 (\*) For GPRS, messages 3) and 4) are sent/received by the SGSN. + - 4196 (\*\*) These messages are not used by the SGSN. + +4197 + 4198 **Figure 23.4/1: Short message alert procedure (Mobile is present)** + +4199 The message flow for the Short Message Alert procedure for the case where the MS indicates that it has memory + 4200 capacity to accept one or more short messages is shown in figure 23.4/2. + +![Sequence diagram for Short message alert procedure (MS memory capacity available). The diagram shows interactions between MS, Serving MSC or SGSN, VLR, HLR, Interworking MSC, and SC. The sequence of messages is: 1) MS to Serving MSC or SGSN; 2) Serving MSC or SGSN to VLR; 3) VLR to HLR; 4) HLR to VLR; 5) VLR to Serving MSC or SGSN; 6) Serving MSC or SGSN to MS; 7) HLR to Interworking MSC (three times); 8) Interworking MSC to SC (three times); 9) Interworking MSC to HLR (three times).](4a7971babb6c8726633005c19e30bf05_img.jpg) + +Sequence diagram for Short message alert procedure (MS memory capacity available). The diagram shows interactions between MS, Serving MSC or SGSN, VLR, HLR, Interworking MSC, and SC. The sequence of messages is: 1) MS to Serving MSC or SGSN; 2) Serving MSC or SGSN to VLR; 3) VLR to HLR; 4) HLR to VLR; 5) VLR to Serving MSC or SGSN; 6) Serving MSC or SGSN to MS; 7) HLR to Interworking MSC (three times); 8) Interworking MSC to SC (three times); 9) Interworking MSC to HLR (three times). + +4201 + +4202 + +4203 1) SM memory capacity available ( 3GPP TS 24.011 [37]). + +4204 2) MAP\_READY\_FOR\_SM (Memory Available) (\*). + +4205 3) MAP\_READY\_FOR\_SM (Memory Available) (\*\*). + +4206 4) MAP\_READY\_FOR\_SM\_ACK (\*\*). + +4207 5) MAP\_READY\_FOR\_SM\_ACK (\*). + +4208 6) SM memory capacity available (Acknowledge) (3GPP TS 24.011 [37]). + +4209 7) MAP\_ALERT\_SERVICE\_CENTRE (note). + +4210 8) Alert Service Centre (3GPP TS 23.040). + +4211 9) MAP\_ALERT\_SERVICE\_CENTRE\_ACK. + +4212 NOTE: To all Service Centres in the Message Waiting List. + +4213 (\*) Messages 2) and 5) are not used by the SGSN. + +4214 (\*\*) For GPRS, messages 3) and 4) are sent/received by the SGSN. + +4215 + +4216 + +**Figure 23.4/2: Short message alert procedure (MS memory capacity available)** + +4217 In addition the following MAP services are used in the MS memory available case: + +4218 MAP\_PROCESS\_ACCESS\_REQUEST (see clause 8.3); (\*) + +4219 MAP\_AUTHENTICATE (see clause 8.5); (\*) + +4220 MAP\_SET\_CIPHERING\_MODE (see clause 8.6); (\*) + +4221 MAP\_PROVIDE\_IMSI (see clause 8.9); (\*) + +4222 MAP\_CHECK\_IMEI (see clause 8.7); + +4223 MAP\_FORWARD\_NEW\_TMSI (see clause 8.9); (\*) + +4224 MAP\_TRACE\_SUBSCRIBER\_ACTIVITY (see clause 9.1). (\*) + +4225 (\*) These services are not used by the SGSN. + +4226 The Short Message Alert procedure when the MS indicates successful transfer after polling is shown in figure 23.4/3. + +![Sequence diagram for Short message alert procedure (Successful transfer after polling). The diagram shows four lifelines: Gateway MSC, HLR, Interworking MSC, and SC. The sequence of messages is: 1) Gateway MSC to HLR (MAP_REPORT_SM_DELIVERY_STATUS); 2) HLR to Gateway MSC (MAP_REPORT_SM_DELIVERY_STATUS_ACK); 3) HLR to Interworking MSC (MAP_ALERT_SERVICE_CENTRE); 4) Interworking MSC to SC (Alert Service Centre); 5) Interworking MSC to HLR (MAP_ALERT_SERVICE_CENTRE_ACK).](6febe06e14962a80f5a508b46c1ae93f_img.jpg) + +``` + +sequenceDiagram + participant Gateway MSC + participant HLR + participant Interworking MSC + participant SC + Note right of HLR: 1 + Gateway MSC->>HLR: + Note right of HLR: 2 + HLR->>Gateway MSC: + Note right of HLR: 3 + HLR->>Interworking MSC: + Note right of Interworking MSC: 3 + Interworking MSC->>HLR: + Note right of Interworking MSC: 4 + Interworking MSC->>SC: + Note right of Interworking MSC: 4 + Interworking MSC->>HLR: + Note right of Interworking MSC: 4 + Interworking MSC->>SC: + Note right of Interworking MSC: 5 + Interworking MSC->>HLR: + Note right of HLR: 5 + HLR->>Interworking MSC: + Note right of HLR: 5 + HLR->>Interworking MSC: + Note right of HLR: 5 + HLR->>Interworking MSC: + +``` + +Sequence diagram for Short message alert procedure (Successful transfer after polling). The diagram shows four lifelines: Gateway MSC, HLR, Interworking MSC, and SC. The sequence of messages is: 1) Gateway MSC to HLR (MAP\_REPORT\_SM\_DELIVERY\_STATUS); 2) HLR to Gateway MSC (MAP\_REPORT\_SM\_DELIVERY\_STATUS\_ACK); 3) HLR to Interworking MSC (MAP\_ALERT\_SERVICE\_CENTRE); 4) Interworking MSC to SC (Alert Service Centre); 5) Interworking MSC to HLR (MAP\_ALERT\_SERVICE\_CENTRE\_ACK). + +4227 + +4228 + +4229 1) MAP\_REPORT\_SM\_DELIVERY\_STATUS (Successful Transfer). + +4230 2) MAP\_REPORT\_SM\_DELIVERY\_STATUS\_ACK. + +4231 3) MAP\_ALERT\_SERVICE\_CENTRE (note). + +4232 4) Alert Service Centre (3GPP TS 23.040). + +4233 5) MAP\_ALERT\_SERVICE\_CENTRE\_ACK. + +4234 NOTE: To all Service Centres in the Message Waiting List. + +4235 + +4236 + +**Figure 23.4/3: Short message alert procedure (Successful transfer after polling)** + +## 4237 23.4.1 Procedure in the Serving MSC – the MS has memory available + +4238 The process starts when the MSC receives a notification from the MS that it has memory available. The process invokes +4239 a macro not defined in this clause; the definition of this macro can be found as follows: + +4240 Check\_Confirmation see clause 25.2.2. + +4241 The short message alert process in the MSC for the MS memory capacity available case is shown in figure 23.4/4. + +## 4242 23.4.2 Procedures in the VLR + +### 4243 23.4.2.1 The Mobile Subscriber is present + +4244 If the VLR successfully handles a MAP\_PROCESS\_ACCESS\_REQUEST indication or a +4245 MAP\_UPDATE\_LOCATION\_AREA indication while the MS Not Reachable Flag (MNRF) is set, the VLR sends a +4246 MAP\_READY\_FOR\_SM request to the HLR. The Alert Reason is set to indicate that the mobile subscriber is present +4247 for non GPRS. If authentication fails during the handling of a MAP\_PROCESS\_ACCESS\_REQUEST indication or a +4248 MAP\_UPDATE\_LOCATION\_AREA indication, the VLR shall not send a MAP\_READY\_FOR\_SM request to the +4249 HLR. The process in the VLR is described in detail in clause 25.10.1. + +### 4250 23.4.2.2 The MS has memory available + +4251 The process starts when the VLR receives dialogue opening request followed by a +4252 MAP\_PROCESS\_ACCESS\_REQUEST indication including a CM service type Short Message Service. The MAP +4253 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +4254 Receive\_Open\_Ind see clause 25.1.1; + +4255 Receive\_Open\_Cnf see clause 25.1.2; + +4256 Check\_Indication see clause 25.2.1; + +4257 Check\_Confirmation see clause 25.2.2. + +4258 The short message alert process in the VLR for the MS memory capacity available case is shown in figure 23.4/5. + +### 4259 23.4.3 Procedures in the SGSN + +#### 4260 23.4.3.1 The Mobile Subscriber is present + +4261 If the SGSN successfully handles a Page response, Attach request or Routing Area Update request message (3GPP TS +4262 24.008 [35]), while the MS Not Reachable for GPRS (MNRG) flag is set, the SGSN sends a MAP\_READY\_FOR\_SM +4263 request to the HLR. The Alert Reason is set to indicate that the mobile subscriber is present for GPRS. If authentication +4264 fails during the handling of a Page response, Attach request or Routing Area Update request, the SGSN shall not send a +4265 MAP\_READY\_FOR\_SM request to the HLR + +4266 The process in the SGSN is described in detail in clause 25.10.23. + +#### 4267 23.4.3.2 The Mobile Equipment has memory available + +4268 The process starts when the SGSN receives an RP\_SM\_MEMORY\_AVAILABLE indication from the MS. The MAP +4269 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +4270 Receive\_Open\_Cnf see clause 25.1.2; + +4271 Check\_Confirmation see clause 25.2.2. + +4272 The short message alert procedure in the SGSN for the MS memory capacity available case is shown in figure 23.4/6. + +### 4273 23.4.4 Procedure in the HLR + +4274 The process starts when the HLR receives a dialogue opening request using the application context mwdMngtContext. +4275 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +4276 Receive\_Open\_Ind see clause 25.1.1; + +4277 Check\_Indication see clause 25.2.1; + +4278 Alert\_Service\_Centre\_HLR see clause 25.10.3. + +4279 Sheet 1: If the dialogue opening request is from an SGSN, version 2 and version 1 of the application context are not +4280 applicable. + +4281 The short message alert process in the HLR is shown in figure 23.4/7. + +### 4282 23.4.5 Procedure in the SMS Interworking MSC + +4283 The process starts when the SMS-IWMSC receives a dialogue opening request using the application context +4284 shortMsgAlertContext. The MAP process invokes macros not defined in this clause; the definitions of these macros can +4285 be found as follows: + +4286 Receive\_Open\_Ind see clause 25.1.1; + +4287 Check\_Indication see clause 25.2.1. + +4288 The short message alert process in the SMS-IWMSC is shown in figure 23.4/8. + +![Sequence diagram for process SM_Alert_MSC. The flow starts with an initial node, followed by a 'Null' node. It then enters a loop: an output node sends 'A_RP_SM_MEMORY_AVAILABLE_ind' to the right; an input node receives 'MAP_READY_FOR_SM_req' and 'MAP_DELIMITER_req' from the right; a 'Wait_For_VLR_Response' node follows. A decision node then branches into three paths: 1) Output node sends 'A_MM_Release_ind' to the left, followed by an input node receiving 'MAP_U_ABORT_req' from the left, ending with an 'X'. 2) Input node receives 'MAP_READY_FOR_SM_cnf' from the right, followed by a 'Check_Confirmation' node. From 'Check_Confirmation', an 'OK' path leads to an input node receiving 'A_RP_ACK_req' from the left, ending with an 'X'. A non-OK path (User Error, Provider Error, Data Error) leads to a 'Set RP_ERROR' node, then an input node receiving 'A_RP_ERROR_req' from the left, ending with an 'X'. 3) Input node receives 'MAP_U_ABORT_ind' and 'MAP_CLOSE_ind' from the right, followed by a 'Set RP_ERROR: Network out of order' node, then an input node receiving 'A_RP_ERROR_req' from the left, ending with an 'X'.](434430603574c3a3b337b264c6f76438_img.jpg) + +**process SM\_Alert\_MSC** **SMA\_MSC1(1)** + +Process in the MSC to forward a notification that the MS has memory available to store short messages + +Signals to/from the left are to/from the MS; +signals to/from the right are to/from the VLR + +``` + +sequenceDiagram + participant Start + participant Null + participant Out1 + participant In1 + participant Wait + participant Decision + participant Out2 + participant In2 + participant Check + participant SetRE1 + participant In3 + participant SetRE2 + participant In4 + + Start --> Null + Null --> Out1 + Out1 --> In1 + In1 --> Wait + Wait --> Decision + Decision --> Out2 + Out2 --> In2 + In2 --> Check + Check --> SetRE1 + SetRE1 --> In3 + Check --> SetRE2 + SetRE2 --> In4 + +``` + +Sequence diagram for process SM\_Alert\_MSC. The flow starts with an initial node, followed by a 'Null' node. It then enters a loop: an output node sends 'A\_RP\_SM\_MEMORY\_AVAILABLE\_ind' to the right; an input node receives 'MAP\_READY\_FOR\_SM\_req' and 'MAP\_DELIMITER\_req' from the right; a 'Wait\_For\_VLR\_Response' node follows. A decision node then branches into three paths: 1) Output node sends 'A\_MM\_Release\_ind' to the left, followed by an input node receiving 'MAP\_U\_ABORT\_req' from the left, ending with an 'X'. 2) Input node receives 'MAP\_READY\_FOR\_SM\_cnf' from the right, followed by a 'Check\_Confirmation' node. From 'Check\_Confirmation', an 'OK' path leads to an input node receiving 'A\_RP\_ACK\_req' from the left, ending with an 'X'. A non-OK path (User Error, Provider Error, Data Error) leads to a 'Set RP\_ERROR' node, then an input node receiving 'A\_RP\_ERROR\_req' from the left, ending with an 'X'. 3) Input node receives 'MAP\_U\_ABORT\_ind' and 'MAP\_CLOSE\_ind' from the right, followed by a 'Set RP\_ERROR: Network out of order' node, then an input node receiving 'A\_RP\_ERROR\_req' from the left, ending with an 'X'. + +4289 + +4290 + +Figure 23.4/4: Procedure SM\_Alert\_MSC + +![Flowchart for process SM_Alert_VLR. The process starts with an initial state, followed by 'Null', 'Receive_Open_Ind', 'Wait_For_Service_Primitive', 'Process_Access_Request_VLR', 'Wait_For_Ready_For_SM', a decision point for 'MAP_READY_FOR_SM_ind', 'Check_Indication', another decision point for 'Set Ready for SM Reason', a list of MAP requests, 'Receive_Open_Cnf', and finally a decision based on response (Error, V1, Vr, OK) leading to error handling, HLR dialogue, or waiting for response.](870240d0d80351b5b3969050f46660ae_img.jpg) + +**process SM\_Alert\_VLR** **SMA\_VLR1(2)** + +Process in the VLR to forward a notification that the MS has memory available to store short messages + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR; + +``` + + graph TD + Start([ ]) --> Null1([Null]) + Null1 --> RecOpenInd[Receive_Open_Ind] + RecOpenInd -- OK --> WaitService[Wait_For_Service_Primitive] + RecOpenInd -- "Error, Vr" --> Null2([Null]) + WaitService --> ProcessAccess[Process_Access_Request_VLR] + ProcessAccess -- OK --> WaitReady[Wait_For_Ready_For_SM] + ProcessAccess -- Error --> Null2 + WaitReady --> Decision1{ } + Decision1 -- "MAP_READY_FOR_SM_ind" --> CheckInd[Check_Indication] + CheckInd -- OK --> Decision2{ } + Decision2 -- "Set Ready for SM Reason: Memory available for non-GPRS" --> Decision3{ } + Decision3 -- "MAP_OPEN_req +MAP_READY_FOR_SM_req +MAP_DELIMITER_req" --> RecOpenCnf[Receive_Open_Cnf] + RecOpenCnf -- Error --> Decision4{ } + RecOpenCnf -- V1 --> SetErrorV1[Set User Error: Facility not supported] + RecOpenCnf -- Vr --> PerformMAP[Perform MAP Vr dialogue] + RecOpenCnf -- OK --> WaitHLR[Wait_For_HLR_Response] + SetErrorV1 --> Decision4 + PerformMAP --> Null3([Null]) + WaitHLR --> Decision4 + Decision4 -- "MAP_READY_FOR_SM_rsp +MAP_CLOSE_req" --> Null4([Null]) + +``` + +Flowchart for process SM\_Alert\_VLR. The process starts with an initial state, followed by 'Null', 'Receive\_Open\_Ind', 'Wait\_For\_Service\_Primitive', 'Process\_Access\_Request\_VLR', 'Wait\_For\_Ready\_For\_SM', a decision point for 'MAP\_READY\_FOR\_SM\_ind', 'Check\_Indication', another decision point for 'Set Ready for SM Reason', a list of MAP requests, 'Receive\_Open\_Cnf', and finally a decision based on response (Error, V1, Vr, OK) leading to error handling, HLR dialogue, or waiting for response. + +4291 + +4292 + +**Figure 23.4/5 (sheet 1 of 2): Procedure SM\_Alert\_VLR** + +![Flowchart for process SM_Alert_VLR. It starts with 'Wait_For_HLR_Response' leading to a horizontal line. From this line, three paths emerge: 1) Left: 'MAP_READY_FOR_SM_cnf' leads to a left-pointing arrow, then 'Check_Confirmation'. 'Check_Confirmation' has an 'OK' path leading down to a bottom-pointing arrow, and an error path ('User Error, Provider Error, Data Error') leading to 'Set User Error'. 2) Middle: 'MAP_NOTICE_ind' leads down to 'MAP_CLOSE_req', which leads down to 'Set User Error: System failure'. 3) Right: A right-pointing arrow leads to a box with 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind', which then leads down to the bottom-pointing arrow. Both 'Set User Error' and 'Set User Error: System failure' lead to the bottom-pointing arrow. The bottom-pointing arrow leads to a box with 'MAP_READY_FOR_SM_rsp' and 'MAP_CLOSE_req', which finally leads down to 'Null'.](1c4c92c2c4c668fd3164a94e2d7a3921_img.jpg) + +**process SM\_Alert\_VLR** **SMA\_VLR2(2)** + +Process in the VLR to forward a notification that the MS has memory available to store short messages + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR; + +``` + +graph TD + Start([Wait_For_HLR_Response]) --> Junction(( )) + Junction --> LeftArrow{ } + Junction --> MiddleLine[ ] + Junction --> RightArrow{ } + LeftArrow --> MAP_READY_FOR_SM_cnf[MAP_READY_FOR_SM_cnf] + MAP_READY_FOR_SM_cnf --> Check_Confirmation[Check_Confirmation] + Check_Confirmation -- OK --> BottomArrow{ } + Check_Confirmation -- "User Error, Provider Error, Data Error" --> Set_User_Error[Set User Error] + MiddleLine --> MAP_NOTICE_ind[MAP_NOTICE_ind] + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> Set_User_Error_System_Failure[Set User Error: System failure] + RightArrow --> Error_Indications["MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind"] + Error_Indications --> BottomArrow + Set_User_Error --> BottomArrow + Set_User_Error_System_Failure --> BottomArrow + BottomArrow --> Responses["MAP_READY_FOR_SM_rsp, MAP_CLOSE_req"] + Responses --> Null([Null]) + +``` + +Flowchart for process SM\_Alert\_VLR. It starts with 'Wait\_For\_HLR\_Response' leading to a horizontal line. From this line, three paths emerge: 1) Left: 'MAP\_READY\_FOR\_SM\_cnf' leads to a left-pointing arrow, then 'Check\_Confirmation'. 'Check\_Confirmation' has an 'OK' path leading down to a bottom-pointing arrow, and an error path ('User Error, Provider Error, Data Error') leading to 'Set User Error'. 2) Middle: 'MAP\_NOTICE\_ind' leads down to 'MAP\_CLOSE\_req', which leads down to 'Set User Error: System failure'. 3) Right: A right-pointing arrow leads to a box with 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind', which then leads down to the bottom-pointing arrow. Both 'Set User Error' and 'Set User Error: System failure' lead to the bottom-pointing arrow. The bottom-pointing arrow leads to a box with 'MAP\_READY\_FOR\_SM\_rsp' and 'MAP\_CLOSE\_req', which finally leads down to 'Null'. + +4293 + +4294 + +**Figure 23.4/5 (sheet 2 of 2): Procedure SM\_Alert\_VLR** + +![Flowchart for process SM_Alert_SGSN. The flow starts at a Null terminal, followed by a merge symbol receiving Gb_RP_SM_MEMORY_AVAILABLE_ind. It then passes through a process block 'Set Ready for SM Reason: Memory available for GPRS', then a decision symbol with inputs MAP_OPEN_req, MAP_READY_FOR_SM_req, and MAP_DELIMITER_req. The next block is 'Receive_Open_Cnf'. From there, three paths emerge: 'Error' leads to 'Set RP_ERROR: Network out of order'; 'Vr' leads to 'Set RP_ERROR: Facility not supported'; 'OK' leads to 'Wait_For_HLR_Response'. All three paths converge to a decision symbol 'Gb_RP_ERROR_req', which finally leads to a Null terminal.](9e291c566dabfe04833c505f14d02db0_img.jpg) + +**process SM\_Alert\_SGSN** **SMA\_SGSN1(2)** + +Process in the SGSN to forward a notification that the MS has memory available to store short messages + +Signals to/from the left are to/from the MS; signals to/from the right are to/from the HLR + +``` + +graph TD + Start([Null]) --> Merge{ } + Merge -- "Gb_RP_SM_MEMORY_AVAILABLE_ind" --> Process1[Set Ready for SM Reason: +Memory available for GPRS] + Process1 --> Decision1{ } + Decision1 -- "MAP_OPEN_req +MAP_READY_FOR_SM_req +MAP_DELIMITER_req" --> Process2[Receive_Open_Cnf] + Process2 -- Error --> ErrorPath[Set RP_ERROR: +Network out of order] + Process2 -- Vr --> VrPath[Set RP_ERROR: +Facility not supported] + Process2 -- OK --> OKPath([Wait_For_HLR_Response]) + ErrorPath --> Decision2{Gb_RP_ERROR_req} + VrPath --> Decision2 + OKPath --> Decision2 + Decision2 --> End([Null]) + +``` + +Flowchart for process SM\_Alert\_SGSN. The flow starts at a Null terminal, followed by a merge symbol receiving Gb\_RP\_SM\_MEMORY\_AVAILABLE\_ind. It then passes through a process block 'Set Ready for SM Reason: Memory available for GPRS', then a decision symbol with inputs MAP\_OPEN\_req, MAP\_READY\_FOR\_SM\_req, and MAP\_DELIMITER\_req. The next block is 'Receive\_Open\_Cnf'. From there, three paths emerge: 'Error' leads to 'Set RP\_ERROR: Network out of order'; 'Vr' leads to 'Set RP\_ERROR: Facility not supported'; 'OK' leads to 'Wait\_For\_HLR\_Response'. All three paths converge to a decision symbol 'Gb\_RP\_ERROR\_req', which finally leads to a Null terminal. + +4295 + +4296 + +**Figure 23.4/6 (sheet 1 of 2): Process SM\_Alert\_SGSN** + +![State transition diagram for process SM_Alert_SGSN. The diagram starts with a 'Wait_For_HLR_Response' state. It branches into four main paths: 1) Gb_LLC_RELEASE_ind leads to MAP_U_ABORT_req and then Null. 2) MAP_READY_FOR_SM_cnf leads to Check_Confirmation, which on 'OK' leads to Gb_RP_ACK_req and then Null, and on 'User Error, Provider Error, Data Error' leads to Set_RP_ERROR, Gb_RP_ERROR_req, and then Null. 3) MAP_NOTICE_ind leads to MAP_CLOSE_req, Set_RP_ERROR: Network out of order, Gb_RP_ERROR_req, and then Null. 4) A group of signals (MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind) leads to a merge point before Set_RP_ERROR: Network out of order.](be33878621994047f90b955f7cb9ed86_img.jpg) + +**process SM\_Alert\_SGSN** **SMA\_SGSN2(2)** + +Process in the SGSN to forward a notification that the MS has memory available to store short messages + +Signals to/from the left are to/from the MS; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Wait_For_HLR_Response + state "Wait_For_HLR_Response" as Wait_For_HLR_Response + state "Gb_LLC_RELEASE_ind" as Gb_LLC_RELEASE_ind + state "MAP_READY_FOR_SM_cnf" as MAP_READY_FOR_SM_cnf + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" as MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + state "MAP_U_ABORT_req" as MAP_U_ABORT_req + state "Check_Confirmation" as Check_Confirmation + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "Set_RP_ERROR" as Set_RP_ERROR + state "Set_RP_ERROR: Network out of order" as Set_RP_ERROR_Network_out_of_order + state "Gb_RP_ACK_req" as Gb_RP_ACK_req + state "Gb_RP_ERROR_req" as Gb_RP_ERROR_req + state "Null" as Null + + Wait_For_HLR_Response --> Gb_LLC_RELEASE_ind + Wait_For_HLR_Response --> MAP_READY_FOR_SM_cnf + Wait_For_HLR_Response --> MAP_NOTICE_ind + Wait_For_HLR_Response --> MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + + Gb_LLC_RELEASE_ind --> MAP_U_ABORT_req + MAP_U_ABORT_req --> Null + + MAP_READY_FOR_SM_cnf --> Check_Confirmation + Check_Confirmation --> Gb_RP_ACK_req : OK + Check_Confirmation --> Set_RP_ERROR : User Error, Provider Error, Data Error + Set_RP_ERROR --> Gb_RP_ERROR_req + Gb_RP_ACK_req --> Null + Gb_RP_ERROR_req --> Null + + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Set_RP_ERROR_Network_out_of_order + Set_RP_ERROR_Network_out_of_order --> Gb_RP_ERROR_req + Gb_RP_ERROR_req --> Null + + MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind --> Set_RP_ERROR_Network_out_of_order + +``` + +State transition diagram for process SM\_Alert\_SGSN. The diagram starts with a 'Wait\_For\_HLR\_Response' state. It branches into four main paths: 1) Gb\_LLC\_RELEASE\_ind leads to MAP\_U\_ABORT\_req and then Null. 2) MAP\_READY\_FOR\_SM\_cnf leads to Check\_Confirmation, which on 'OK' leads to Gb\_RP\_ACK\_req and then Null, and on 'User Error, Provider Error, Data Error' leads to Set\_RP\_ERROR, Gb\_RP\_ERROR\_req, and then Null. 3) MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req, Set\_RP\_ERROR: Network out of order, Gb\_RP\_ERROR\_req, and then Null. 4) A group of signals (MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind) leads to a merge point before Set\_RP\_ERROR: Network out of order. + +4297 + +4298 + +Figure 23.4/6 (sheet 2 of 2): Process SM\_Alert\_SGSN + +![Flowchart for process SM_Alert_HLR. It starts with 'Null' -> 'Receive_Open_ind'. From 'Receive_Open_ind', three paths emerge: 'Vr' (left) leads to 'Perform MAP Vr dialogue' -> 'Null'; 'OK' (center) leads to 'Wait_For_Service_Primitive'; 'Error' (right) leads to 'Null'. 'Wait_For_Service_Primitive' branches into four paths: 1) 'MAP_READY_FOR_SM_ind' -> 'Check_Indication' -> Decision 'MNRF or MNRG supported AND MCEF supported AND MWD supported?'. If 'No', 'Set User Error: Facility not supported' -> 'Error' (left). If 'Yes', Decision 'Subscriber known?'. If 'No', 'Set User Error: Unknown subscriber' -> 'Error' (left). If 'Yes', Decision 'MCEF set OR MNRG set OR UNRI set'. If 'No', 'Start Race timer' -> 'Alert_Pending'. If 'Yes', connector '1'. 2) 'MAP_P_ABORT_ind' -> 'Null'. 3) 'MAP_NOTICE_ind' -> 'MAP_CLOSE_req' -> 'Null'. 4) 'MAP_REPORT_SM_DELIVERY_STATUS_ind' -> 'Report_SM_Delivery_Stat_HLR' -> Decision 'Delivery Result=Success?'. If 'No', 'Alert_Pending'. If 'Yes', 'Stop Race timer' -> 'Null'. At the bottom left, a merge point leads to 'MAP_READY_FOR_SM_rsp MAP_CLOSE_req' -> 'Null'.](7607b9e1dc17f539f850ff99f8cac783_img.jpg) + +**process SM\_Alert\_HLR** **SMA\_HLR1(2)** + +Process in the HLR to handle a notification that the MS is ready to receive short messages + +Signals to/from the left are to/from the VLR or the SGSN; signals to/from the right are from the SMS-GMSC + +``` + + graph TD + Start([Null]) --> RecOpen[Receive_Open_ind] + RecOpen -- Vr --> PerformVr[Perform MAP Vr dialogue] + PerformVr --> Null1([Null]) + RecOpen -- OK --> WaitService[Wait_For_Service_Primitive] + RecOpen -- Error --> Null2([Null]) + + WaitService --> MapReadyInd{MAP_READY_FOR_SM_ind} + MapReadyInd --> CheckInd[Check_Indication] + + CheckInd --> DecisionMNRF{MNRF or MNRG supported AND MCEF supported AND MWD supported?} + + DecisionMNRF -- No --> SetErrorFacility[Set User Error: Facility not supported] + SetErrorFacility --> ErrorLeft[Error] + + DecisionMNRF -- Yes --> SubKnown{Subscriber known?} + + SubKnown -- No --> SetErrorUnknown[Set User Error: Unknown subscriber] + SetErrorUnknown --> ErrorLeft + + SubKnown -- Yes --> DecisionMCEF{MCEF set OR MNRG set OR UNRI set} + + DecisionMCEF -- No --> StartRace[Start Race timer] + StartRace --> AlertPending1[Alert_Pending] + + DecisionMCEF -- Yes --> Connector1((1)) + + MapReadyInd --> MapPAbortInd{MAP_P_ABORT_ind} + MapPAbortInd --> Null3([Null]) + + MapReadyInd --> MapNoticeInd{MAP_NOTICE_ind} + MapNoticeInd --> MapCloseReq[MAP_CLOSE_req] + MapCloseReq --> Null4([Null]) + + MapReadyInd --> MapReportSMInd{MAP_REPORT_SM_DELIVERY_STATUS_ind} + MapReportSMInd --> ReportSM[Report_SM_Delivery_Stat_HLR] + + ReportSM --> DecisionDelResult{Delivery Result=Success?} + + DecisionDelResult -- No --> AlertPending2[Alert_Pending] + + DecisionDelResult -- Yes --> StopRace[Stop Race timer] + StopRace --> Null5([Null]) + + ErrorLeft --> MergePoint{{}} + + MergePoint --> MapReadyRsp[MAP_READY_FOR_SM_rsp MAP_CLOSE_req] + + MapReadyRsp --> Null6([Null]) + +``` + +Flowchart for process SM\_Alert\_HLR. It starts with 'Null' -> 'Receive\_Open\_ind'. From 'Receive\_Open\_ind', three paths emerge: 'Vr' (left) leads to 'Perform MAP Vr dialogue' -> 'Null'; 'OK' (center) leads to 'Wait\_For\_Service\_Primitive'; 'Error' (right) leads to 'Null'. 'Wait\_For\_Service\_Primitive' branches into four paths: 1) 'MAP\_READY\_FOR\_SM\_ind' -> 'Check\_Indication' -> Decision 'MNRF or MNRG supported AND MCEF supported AND MWD supported?'. If 'No', 'Set User Error: Facility not supported' -> 'Error' (left). If 'Yes', Decision 'Subscriber known?'. If 'No', 'Set User Error: Unknown subscriber' -> 'Error' (left). If 'Yes', Decision 'MCEF set OR MNRG set OR UNRI set'. If 'No', 'Start Race timer' -> 'Alert\_Pending'. If 'Yes', connector '1'. 2) 'MAP\_P\_ABORT\_ind' -> 'Null'. 3) 'MAP\_NOTICE\_ind' -> 'MAP\_CLOSE\_req' -> 'Null'. 4) 'MAP\_REPORT\_SM\_DELIVERY\_STATUS\_ind' -> 'Report\_SM\_Delivery\_Stat\_HLR' -> Decision 'Delivery Result=Success?'. If 'No', 'Alert\_Pending'. If 'Yes', 'Stop Race timer' -> 'Null'. At the bottom left, a merge point leads to 'MAP\_READY\_FOR\_SM\_rsp MAP\_CLOSE\_req' -> 'Null'. + +4299 + +4300 + +Figure 23.4/7 (sheet 1 of 2): Process SM\_Alert\_HLR + +![Flowchart for process SM_Alert_HLR. It starts with a connector '1' leading to a decision 'Ready for SM Reason'. From this decision, three main paths emerge based on memory and subscriber status. The first path (Memory available for GPRS, non-GPRS, or IP-SM-GW) leads to clearing flags (MNRG, MNRF, UNRI, MCEF) and then to an 'Alert_Service_Centre_HLR' message. The second path (Subscriber present for IP-SM-GW) leads to clearing UNRI. The third path (Subscriber present for GPRS or non-GPRS) leads to clearing MNRG or MNRF. All three paths converge to a decision 'MCEF set?'. If 'No', it goes to 'Alert_Service_Centre_HLR'. If 'Yes', it goes to 'Null'. Both 'Alert_Service_Centre_HLR' and 'Null' lead to 'Alert_Pending'. From 'Alert_Pending', the flow goes to a 'Race timer expired' decision. If 'Internal' (Error), it goes to 'Null'. If 'OK', it goes to 'Wait_For_Service_Primitive'. If 'Vr', it goes to 'Perform MAP Vr dialogue' and then to 'Null'.](e0615287488ece40d876c62e5bc1ff69_img.jpg) + +process SM\_Alert\_HLR + +SMA\_HLR2(2) + +Process in the HLR to handle a notification that the MS is ready to receive short messages + +``` + +graph TD + 1((1)) --> Ready{Ready for SM Reason} + Ready --> M1[Memory available for GPRS] + Ready --> M2[Memory available for non-GPRS] + Ready --> M3[Memory available for IP-SM-GW] + Ready --> S1[Subscriber present for IP-SM-GW] + Ready --> S2[Subscriber present for GPRS] + Ready --> S3[Subscriber present for non-GPRS] + M1 --> C1[Clear MNRG; Clear MCEF] + M2 --> C2[Clear MNRF; Clear MCEF] + M3 --> C3[Clear UNRI; Clear MCEF] + S1 --> C4[Clear UNRI] + S2 --> C5[Clear MNRG] + S3 --> C6[Clear MNRF] + C1 --> MCEF{MCEF set?} + C2 --> MCEF + C3 --> MCEF + C4 --> MCEF + C5 --> MCEF + C6 --> MCEF + MCEF -- No --> ASC[Alert_Service_Centre_HLR] + MCEF -- Yes --> Null1[Null] + ASC --> Null1 + Null1 --> AP[Alert_Pending] + AP --> Race{Race timer expired} + Race -- Internal --> Null2[Null] + Race -- OK --> WFP[Wait_For_Service_Primitive] + Race -- Vr --> PMVD[Perform MAP Vr dialogue] + PMVD --> Null3[Null] + +``` + +Flowchart for process SM\_Alert\_HLR. It starts with a connector '1' leading to a decision 'Ready for SM Reason'. From this decision, three main paths emerge based on memory and subscriber status. The first path (Memory available for GPRS, non-GPRS, or IP-SM-GW) leads to clearing flags (MNRG, MNRF, UNRI, MCEF) and then to an 'Alert\_Service\_Centre\_HLR' message. The second path (Subscriber present for IP-SM-GW) leads to clearing UNRI. The third path (Subscriber present for GPRS or non-GPRS) leads to clearing MNRG or MNRF. All three paths converge to a decision 'MCEF set?'. If 'No', it goes to 'Alert\_Service\_Centre\_HLR'. If 'Yes', it goes to 'Null'. Both 'Alert\_Service\_Centre\_HLR' and 'Null' lead to 'Alert\_Pending'. From 'Alert\_Pending', the flow goes to a 'Race timer expired' decision. If 'Internal' (Error), it goes to 'Null'. If 'OK', it goes to 'Wait\_For\_Service\_Primitive'. If 'Vr', it goes to 'Perform MAP Vr dialogue' and then to 'Null'. + +4301 + +4302 + +4303 + +Figure 23.4/7 (sheet 2 of 2): Process SM\_Alert\_HLR + +![State transition diagram for process Alert_SC_IWMSC. It starts with an initial state leading to 'Null', then 'Receive_Open_Ind'. From 'Receive_Open_Ind', three paths emerge: 'Error' to 'Null', 'OK' to 'Wait_For_Service_Primitive', and 'Vr' to 'Perform MAP Vr dialogue' (which leads to 'Null'). From 'Wait_For_Service_Primitive', an arrow points to a merge state (chevron). From this merge state, an arrow points to 'Check_Indication', and a signal 'MAP_ALERT_SERVICE_CENTRE_ind' is sent to the right. From 'Check_Indication', two paths emerge: 'Error' leading to a merge state for 'MAP_NOTICE_ind' and 'MAP_CLOSE_ind' (both leading to 'Null'), and 'OK' leading to a decision state (diamond). From the decision state, an arrow points to a merge state (chevron), and signals 'SC_RP_ALERT_SC_req' and 'MAP_ALERT_SERVICE_CENTRE_rsp / MAP_CLOSE_req' are sent to the right. Finally, an arrow from the merge state leads to the 'Null' state.](419bff93f5e948c1d9c64c3582832f7b_img.jpg) + +**process Alert\_SC\_IWMSC** **ASC\_IWMSC1(1)** + +Process in the SMS Interworking MSC to relay an alert to the SMSC + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the SMSC + +``` + +stateDiagram-v2 + [*] --> Null1[Null] + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind --> Null2[Null] : Error + Receive_Open_Ind --> Wait_For_Service_Primitive[Wait_For_Service_Primitive] : OK + Receive_Open_Ind --> Perform_MAP_Vr_dialogue[Perform MAP Vr dialogue] : Vr + Perform_MAP_Vr_dialogue --> Null3[Null] + Wait_For_Service_Primitive --> Merge1{ } + Merge1 --> Check_Indication[Check_Indication] + Merge1 --> MAP_ALERT_SERVICE_CENTRE_ind[MAP_ALERT_SERVICE_CENTRE_ind] + Check_Indication --> Null4[Null] : Error + Check_Indication --> Decision{ } : OK + Decision --> Merge2{ } + Decision --> SC_RP_ALERT_SC_req[SC_RP_ALERT_SC_req] + Decision --> MAP_ALERT_SERVICE_CENTRE_rsp[MAP_ALERT_SERVICE_CENTRE_rsp / MAP_CLOSE_req] + Merge2 --> Null5[Null] + Merge2 --> MAP_NOTICE_ind[MAP_NOTICE_ind] + Merge2 --> MAP_CLOSE_ind[MAP_CLOSE_ind] + MAP_NOTICE_ind --> Null6[Null] + MAP_CLOSE_ind --> Null7[Null] + +``` + +State transition diagram for process Alert\_SC\_IWMSC. It starts with an initial state leading to 'Null', then 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', three paths emerge: 'Error' to 'Null', 'OK' to 'Wait\_For\_Service\_Primitive', and 'Vr' to 'Perform MAP Vr dialogue' (which leads to 'Null'). From 'Wait\_For\_Service\_Primitive', an arrow points to a merge state (chevron). From this merge state, an arrow points to 'Check\_Indication', and a signal 'MAP\_ALERT\_SERVICE\_CENTRE\_ind' is sent to the right. From 'Check\_Indication', two paths emerge: 'Error' leading to a merge state for 'MAP\_NOTICE\_ind' and 'MAP\_CLOSE\_ind' (both leading to 'Null'), and 'OK' leading to a decision state (diamond). From the decision state, an arrow points to a merge state (chevron), and signals 'SC\_RP\_ALERT\_SC\_req' and 'MAP\_ALERT\_SERVICE\_CENTRE\_rsp / MAP\_CLOSE\_req' are sent to the right. Finally, an arrow from the merge state leads to the 'Null' state. + +4304 + +4305 + +Figure 23.4/8: Process Alert\_SC\_IWMSC + +## 23.5 The SM delivery status report procedure + +The SM delivery status report procedure is used: + +- to set the Service Centre address into the message waiting list in the HLR after short message delivery has failed because the subscriber is absent or unidentified or the memory capacity is exceeded. The procedure sets: +- the Memory Capacity Exceeded Flag (MCEF) in the HLR if the MS memory does not have room for more messages; +- and/or the MS Not Reachable Flag for non-GPRS if there is no record for the subscriber in the VLR or the subscriber does not respond to paging for delivery via the MSC; +- and/or the MS Not Reachable for GPRS (MNRG) flag if there is no record for the subscriber in the SGSN or the subscriber does not respond to paging for delivery via the SGSN; +- and/or the UE Not Reachable for IP (UNRI) flag if delivery via the IMS was not successful. +- to report to the HLR that delivery has succeeded. The conditions for report of a successful delivery are described in clause 23.3.1. + +The message flow for the SM delivery status report procedure is shown in figure 23.5/1. + +![Sequence diagram of the SM delivery status report procedure. Lifelines: V-MSC or SGSN or IP-SM-GW, HLR, Gateway MSC, SC. The sequence starts with the Gateway MSC sending a message (1) to the V-MSC/SGSN/IP-SM-GW. The V-MSC/SGSN/IP-SM-GW then sends a message (2) to the HLR. The HLR responds with a message (2a) to the V-MSC/SGSN/IP-SM-GW. The V-MSC/SGSN/IP-SM-GW then sends a message (2b) to the Gateway MSC. The Gateway MSC sends a message (3) to the HLR. Finally, the Gateway MSC sends a message (4) to the SC.](fd15797a5f766057f869e827657b63b1_img.jpg) + +``` + +sequenceDiagram + participant V as V-MSC or SGSN or IP-SM-GW + participant H as HLR + participant G as Gateway MSC + participant S as SC + Note right of G: 1 + G->>V: + Note left of V: 2a + V->>H: 2 + Note left of G: 2b + H->>G: + Note right of G: 3 + G->>S: 4 + +``` + +Sequence diagram of the SM delivery status report procedure. Lifelines: V-MSC or SGSN or IP-SM-GW, HLR, Gateway MSC, SC. The sequence starts with the Gateway MSC sending a message (1) to the V-MSC/SGSN/IP-SM-GW. The V-MSC/SGSN/IP-SM-GW then sends a message (2) to the HLR. The HLR responds with a message (2a) to the V-MSC/SGSN/IP-SM-GW. The V-MSC/SGSN/IP-SM-GW then sends a message (2b) to the Gateway MSC. The Gateway MSC sends a message (3) to the HLR. Finally, the Gateway MSC sends a message (4) to the SC. + +- 1) MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ACK/\_NACK (Absent subscriber\_SM, unidentified subscriber or memory capacity exceeded). +- 2) MAP\_REPORT\_SM\_DELIVERY\_STATUS. (The HLR ignores the content of this message when an IP-SM-GW is deployed) +- 2a) MAP\_REPORT\_SM\_DELIVERY\_STATUS (sent only by IP-SM-GW) +- 2b) MAP-REPORT\_SM\_DELIVERY\_STATUS\_ACK. +- 3) MAP\_REPORT\_SM\_DELIVERY\_STATUS\_ACK. +- 4) Short Message Negative Acknowledgement (3GPP TS 23.040). + +**Figure 23.5/1: Short message delivery status report procedure** + +### 23.5.1 Procedure in the SMS-GMSC + +The conditions for the GMSC to invoke the short message delivery status report procedure are specified in clause 23.3.1. + +The short message delivery status report macro in the SMS-GMSC is shown in figure 23.5/2. + +### 23.5.2 Procedure in the HLR + +4335 When the HLR receives a MAP\_REPORT\_SM\_DELIVERY\_STATUS indication while an IP-SM-GW is deployed in +4336 the network and the message is not received from an IP-SM-GW, it ignores the information received in the message; +4337 otherwise it acts as described in clause 23.6, macro Report\_SM\_Delivery\_Stat\_HLR. + +4338 The short message delivery status report process in the HLR is shown in figure 23.5/3. + +### 4339 23.5.3 Procedure in the IP-SM-GW + +The conditions for the IP-SM-GW and for SMS Router, if deployed with IP-SM-GW, to invoke the short message delivery status report procedure are specified in clause 23.3.7. + +4340 The short message delivery status report macro in the IP-SM-GW is shown in figure 23.5/4. + +4341 + +macrodefinition Report\_SM\_Delivery\_Stat\_GMSC + +RSMDS\_GMSC1(1) + +Macro to report the result of an MT short message delivery attempt + +Signals to/from the right are to/from the HLR + +![SDL diagram for Macro Report_SM_Delivery_Stat_GMSC showing the logic for reporting MT short message delivery status to the HLR, including handling of different MAP versions, success/failure results, and error conditions.](16a841958dd6c4294286b1caa9c87103_img.jpg) + +``` + +graph TD + Start([Start]) --> SendReqs[MAP_OPEN_req +MAP_REPORT_SM_DELIVERY_STATUS_req +MAP_DELIMITER_req] + SendReqs --> ReceiveOpenCnf{{Receive_ +Open_Cnf}} + + ReceiveOpenCnf -- V1 --> DelivResult{Delivery +result?} + DelivResult -- Success --> ErrorTerm1((Error)) + DelivResult -- Failure --> FailReason{Other +Delivery +failure +reason?} + FailReason -- "Absent +Subscriber" --> VrBranch + FailReason -- Other --> ErrorTerm1 + + ReceiveOpenCnf -- Vr --> VrBranch[Perform +MAP Vr +dialogue] + VrBranch -- OK --> OKTerm1((OK)) + + ReceiveOpenCnf -- OK --> WaitHLR{{Wait_For_ +HLR_Response}} + WaitHLR -- "MAP_REPORT_SM_DELIVERY_STATUS_cnf" --> CheckCnf[Check_ +Confirmation] + CheckCnf -- OK --> OKTerm2((OK)) + CheckCnf -- "Provider Error, +User Error, +Data Error" --> ErrorTerm2((Error)) + + ReceiveOpenCnf -- Error --> ErrorTerm3((Error)) + + WaitHLR -- "MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind" --> AbortHandler[ ] + AbortHandler --> MapNotice[/MAP_ +NOTICE_ +ind/] + MapNotice --> MapClose[MAP_ +CLOSE_ +req] + MapClose --> ErrorTerm4((Error)) + +``` + +SDL diagram for Macro Report\_SM\_Delivery\_Stat\_GMSC showing the logic for reporting MT short message delivery status to the HLR, including handling of different MAP versions, success/failure results, and error conditions. + +4342 + +4343 + +Figure 23.5/2: Macro Report\_SM\_Delivery\_Stat\_GMSC + +![A flowchart diagram representing the process SM_Delivery_Status_Report_HLR. The flow starts with an oval, followed by a cylinder, then a chevron pointing right to a rectangle. Below the chevron is a diamond, which connects to another diamond. From the second diamond, one path leads left to a chevron pointing left followed by a rectangle, and the other path leads down to a rectangle. Both final rectangles lead to an 'X' symbol. There are two empty note boxes at the top corners of the diagram area.](2943235f20a8f0c41127fb6a8284d272_img.jpg) + +A flowchart diagram representing the process SM\_Delivery\_Status\_Report\_HLR. The flow starts with an oval, followed by a cylinder, then a chevron pointing right to a rectangle. Below the chevron is a diamond, which connects to another diamond. From the second diamond, one path leads left to a chevron pointing left followed by a rectangle, and the other path leads down to a rectangle. Both final rectangles lead to an 'X' symbol. There are two empty note boxes at the top corners of the diagram area. + +4344 + +4345 + +**Figure 23.5/3: Process SM\_Delivery\_Status\_Report\_HLR** + +macrodefinition Report\_SM\_Delivery\_Stat\_IPSMGW + +1(1) + +Macro to report result of an MT short message delivery attempt + +Signals to/from the right are to/from the HLR + +![Flowchart for macrodefinition Report_SM_Delivery_Stat_IPSMGW showing the process of reporting MT short message delivery results.](5a2d577ae08bb387232b2f0f166feb2a_img.jpg) + +``` + +graph TD + Start([Start]) --> Req["MAP_OPEN_req +MAP_REPORT_SM_DELIVERY_STATUS_req +MAP_DELIMITER_req"] + Req --> Recv["Receive_Open_Cnf"] + Recv --> Decision1{Delivery result?} + Decision1 -- V1 --> Decision2{Other Delivery failure reason?} + Decision1 -- Vr --> Perform["Perform MAP Vr dialogue"] + Perform --> OK1((OK)) + Decision1 -- Failure --> Decision2 + Decision2 -- Absent Subscriber --> Perform + Decision2 -- Success --> Error1((Error)) + Decision1 -- OK --> Wait1[Wait_For_HLR_Response] + Wait1 --> Recv2[MAP_REPORT_SM_DELIVERY_STATUS_cnf] + Recv2 --> Check["Check Confirmation"] + Check -- OK --> OK2((OK)) + Check -- "Provider Error, User Error, Data Error" --> Error2((Error)) + Wait1 --> Wait2[Wait_For_HLR_Response] + Wait2 --> Ind1[MAP_NOTICE_ind] + Ind1 --> Req2[MAP_CLOSE_req] + Req2 --> Error3((Error)) + Wait2 --> Ind2[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Ind2 --> Error3 + +``` + +The flowchart illustrates the macrodefinition Report\_SM\_Delivery\_Stat\_IPSMGW. It begins with a start node leading to a block of outgoing signals: MAP\_OPEN\_req, MAP\_REPORT\_SM\_DELIVERY\_STATUS\_req, and MAP\_DELIMITER\_req. This is followed by a 'Receive\_Open\_Cnf' block. A decision diamond 'Delivery result?' follows, with three main paths: V1 (Success), Vr (Failure), and OK. The V1 path leads to another decision diamond 'Other Delivery failure reason?'. From this second decision, 'Success' leads to an 'Error' terminal, 'Failure' leads to 'Absent Subscriber' which then leads to 'Perform MAP Vr dialogue', and 'Other' leads to 'Perform MAP Vr dialogue'. The 'Perform MAP Vr dialogue' block leads to an 'OK' terminal. The OK path from the first decision leads to 'Wait\_For\_HLR\_Response', which then leads to a 'MAP\_REPORT\_SM\_DELIVERY\_STATUS\_cnf' block, followed by 'Check Confirmation'. 'Check Confirmation' leads to an 'OK' terminal or an 'Error' terminal labeled 'Provider Error, User Error, Data Error'. Both 'Wait\_For\_HLR\_Response' blocks lead to a 'MAP\_NOTICE\_ind' block, which leads to a 'MAP\_CLOSE\_req' block, which leads to an 'Error' terminal. Both 'Wait\_For\_HLR\_Response' blocks also lead to a block containing 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind', which leads to an 'Error' terminal. + +Flowchart for macrodefinition Report\_SM\_Delivery\_Stat\_IPSMGW showing the process of reporting MT short message delivery results. + +4346 + +4347 + +Figure 23.5/4: Macro Report\_SM\_Delivery\_Stat\_IPSMGW + +## 4348 23.6 The macro Report\_SM\_Delivery\_Stat\_HLR + +4349 This macro is invoked when the HLR receives a MAP\_REPORT\_SM\_DELIVERY\_STATUS indication from the +4350 SMS-GMSC. The macro invokes macros not defined in this clause; the definitions of these macros can be found as +4351 follows: + +4352 Check\_Indication see clause 25.2.1; + +4353 Alert\_Service\_Centre\_HLR see clause 25.10.3. + +4354 Sheet 1: If the MAP\_REPORT\_SM\_DELIVERY\_STATUS indication did not include the GPRS support indicator, the +4355 HLR deduces the domain for which the delivery report applies as follows: + +4356 - if the subscriber is a GPRS-only subscriber, the report applies for GPRS; + +4357 - if the subscriber is a non-GPRS-only subscriber, the report applies for non-GPRS; + +4358 - if the subscriber is a GPRS and non-GPRS subscriber and the subscription option for MT SMS delivery when +4359 the SMS-GMSC does not support GPRS is set to "Delivery via the SGSN", the report applies for GPRS; + +4360 - if the subscriber is a GPRS and non-GPRS subscriber and the subscription option for MT SMS delivery when +4361 the SMS-GMSC does not support GPRS is set to "Delivery via the MSC", the report applies for non-GPRS; + +4362 The short message delivery status report macro in the HLR is shown in figure 23.6/1. + +![Flowchart for macrodefinition Report_SM_Delivery_Stat_HLR. The process starts with 'Check_Indication', followed by 'Subscriber known?'. If 'No', it goes to 'Set User Error: Unknown Subscriber' and then to an 'Error' terminal. If 'Yes', it goes to 'Delivery result?'. From 'Delivery result?', 'Delivery failure' leads to 'Update MWD list', which then leads to 'MWD update failed?'. If 'Yes', it goes to 'Set User Error: MWD list full' and then to an 'Error' terminal. If 'No', it goes to 'Delivery Result:= Failure' and then to terminal '1'. 'Successful transfer for non-GPRS' leads to 'Clear MNRF: Clear MCEF', which leads to a merge point. 'Successful transfer for GPRS' leads to 'Clear MNRG: Clear MCEF', and 'Successful transfer via IP-SM-GW' leads to 'Clear UNRI Clear MCEF', both leading to the same merge point. From the merge point, it goes to 'MAP_REPORT_SM_DELIVERY_STATUS_rsp MAP_CLOSE_req', then to 'Alert_Service_Centre_HLR', then to 'Delivery Result:= Success', and finally to terminal 'OK'.](4323fed99d217013d0d8926487ee55e9_img.jpg) + +**macrodefinition Report\_SM\_Delivery\_Stat\_HLR** **RSMDS\_HLR1(2)** + +Macro in the HLR to handle an SM delivery status report from the SMS-GMSC + +Signals to/from the left are to/from the SMS-GMSC + +``` + +graph TD + Start([Start]) --> Check[Check_Indication] + Check --> OK[OK] + OK --> Sub{Subscriber known?} + Sub -- No --> Err1[Set User Error: Unknown Subscriber] + Err1 --> Error1((Error)) + Sub -- Yes --> Res{Delivery result?} + Res -- "Delivery failure" --> Update[Update MWD list] + Update --> Failed{MWD update failed?} + Failed -- Yes --> Err2[Set User Error: MWD list full] + Err2 --> Error2((Error)) + Failed -- No --> ResFail[Delivery Result:= Failure] + ResFail --> 1((1)) + Res -- "Successful transfer for non-GPRS" --> Clear1[Clear MNRF: Clear MCEF] + Res -- "Successful transfer for GPRS" --> Clear2[Clear MNRG: Clear MCEF] + Res -- "Successful transfer via IP-SM-GW" --> Clear3[Clear UNRI Clear MCEF] + Clear1 --> Merge{Merge} + Clear2 --> Merge + Clear3 --> Merge + Merge --> MapRsp[MAP_REPORT_SM_DELIVERY_STATUS_rsp +MAP_CLOSE_req] + MapRsp --> Alert[Alert_Service_Centre_HLR] + Alert --> ResSuccess[Delivery Result:= Success] + ResSuccess --> OK2((OK)) + +``` + +Flowchart for macrodefinition Report\_SM\_Delivery\_Stat\_HLR. The process starts with 'Check\_Indication', followed by 'Subscriber known?'. If 'No', it goes to 'Set User Error: Unknown Subscriber' and then to an 'Error' terminal. If 'Yes', it goes to 'Delivery result?'. From 'Delivery result?', 'Delivery failure' leads to 'Update MWD list', which then leads to 'MWD update failed?'. If 'Yes', it goes to 'Set User Error: MWD list full' and then to an 'Error' terminal. If 'No', it goes to 'Delivery Result:= Failure' and then to terminal '1'. 'Successful transfer for non-GPRS' leads to 'Clear MNRF: Clear MCEF', which leads to a merge point. 'Successful transfer for GPRS' leads to 'Clear MNRG: Clear MCEF', and 'Successful transfer via IP-SM-GW' leads to 'Clear UNRI Clear MCEF', both leading to the same merge point. From the merge point, it goes to 'MAP\_REPORT\_SM\_DELIVERY\_STATUS\_rsp MAP\_CLOSE\_req', then to 'Alert\_Service\_Centre\_HLR', then to 'Delivery Result:= Success', and finally to terminal 'OK'. + +4363 + +4364 + +Figure 23.6/1 (sheet 1 of 2): Macro Report\_SM\_Delivery\_Stat\_HLR + +macrodefinition Report\_SM\_Delivery\_Stat\_HLR + +RSMDS\_HLR2(2) + +![Flowchart for SM delivery status report handling in the HLR. The process starts with a macro entry point '1'. It checks if MSISDN=MSISDN-Alert. If 'Yes', it proceeds to 'Delivery failure cause?'. If 'No', it sets MSISDN-Alert and then proceeds to 'Delivery failure cause?'. From 'Delivery failure cause?', multiple paths emerge based on memory capacity or subscriber absence across different network types (non-GPRS, GPRS, IP-SM-GW). These paths lead to setting flags like MCEF, MNRF, MNRG, or UNRI. All paths converge to a decision 'Reason for absence available?'. If 'Yes', it stores the reason, checks absent subscriber status (referencing 3GPP TS 23.116), sends a MAP response, and exits at point '2'. If 'No', it proceeds to another entry point '2' which checks if MCEF is set, then checks if other flags (MNRF, MNRG, UNRI) are set, potentially triggering an 'Alert_Service_Centre_HLR' before reaching 'OK'.](7463e5fb239caa7f0913af358e12e97f_img.jpg) + +Macro in the HLR to handle +an SM delivery status report +from the SMS-GMSC + +Signals to/from the left +are to/from the SMS-GMSC + +``` + + graph TD + Start((1)) --> D1{MSISDN= +MSISDN- +Alert} + D1 -- Yes --> D2{Delivery +failure +cause?} + D1 -- No --> S1[Set MSISDN- +Alert] + S1 --> D2 + + D2 -- "MS memory +capacity +exceeded +for non-GPRS" --> S2[Set MCEF; +Clear MNRF] + D2 -- "MS memory +capacity +exceeded +for GPRS" --> S3[Set MCEF; +Clear MNRG] + D2 -- "MS memory +capability +exceeded +for +IP-SM-GW" --> S4[Set MCEF; +Clear UNRI] + D2 -- "Absent +Subscriber +for +IP-SM-GW" --> S5[Set UNRI] + D2 -- "Absent +Subscriber +for +non-GPRS" --> S6[Set MNRF] + D2 -- "Absent +Subscriber +for GPRS" --> S7[Set MNRG] + D2 -- "Absent +Subscriber +for +non-GPRS +& GPRS" --> S8[Set MNRF; +Set MNRG] + + S2 & S3 & S4 & S5 & S6 & S7 & S8 --> D3{Reason for +absence +available?} + + D3 -- Yes --> S9[Store +Reason for +absence] + S9 --> S10[Check_Absent_ +SubscriberSM_ +In_HLR] + S10 -.-> Note1[See 3GPP TS 23.116] + S10 --> S11[MAP_REPORT_SM_DELIVERY_ +STATUS_rsp +MAP_Close_req] + S11 --> Exit1((2)) + + S9 -.-> Note2[to +MNRR (MSC) +MNRR (SGSN) or +UNRR +depending on the node type of the node +where delivery failed] + + D3 -- No --> J1((2)) + J1 --> D4{MCEF set} + D4 -- yes --> J2(( )) + D4 -- no --> D5{MNRF set & +MNRG set & +UNRI set ?} + D5 -- yes --> J2 + D5 -- no --> S12[Alert_Service_ +Centre_HLR] + S12 --> OK((OK)) + +``` + +Flowchart for SM delivery status report handling in the HLR. The process starts with a macro entry point '1'. It checks if MSISDN=MSISDN-Alert. If 'Yes', it proceeds to 'Delivery failure cause?'. If 'No', it sets MSISDN-Alert and then proceeds to 'Delivery failure cause?'. From 'Delivery failure cause?', multiple paths emerge based on memory capacity or subscriber absence across different network types (non-GPRS, GPRS, IP-SM-GW). These paths lead to setting flags like MCEF, MNRF, MNRG, or UNRI. All paths converge to a decision 'Reason for absence available?'. If 'Yes', it stores the reason, checks absent subscriber status (referencing 3GPP TS 23.116), sends a MAP response, and exits at point '2'. If 'No', it proceeds to another entry point '2' which checks if MCEF is set, then checks if other flags (MNRF, MNRG, UNRI) are set, potentially triggering an 'Alert\_Service\_Centre\_HLR' before reaching 'OK'. + +4365 + +4366 + +**Figure 23.6/1 (sheet 2 of 2): Macro Report\_SM\_Delivery\_Stat\_HLR** + +4367 **23.7 The mobile terminated short message transfer procedure** +4368 **for VGCS** + +4369 The mobile terminated short message transfer for VGCS procedure is used for forwarding a short message from a +4370 Service Centre to the group call anchor MSC. The message flow for the mobile terminated short message transfer +4371 procedure for VGCS is shown in figure 23.7/1. + +![Sequence diagram showing the mobile terminated short message transfer procedure for VGCS. Lifelines: Anchor MSC, GCR, Gateway MSC, SC. Steps: 1. SC to Gateway MSC; 2. Gateway MSC to Anchor MSC; 3. Anchor MSC to Gateway MSC; 4. Gateway MSC to Anchor MSC; 5. Anchor MSC to GCR; 6. GCR to Anchor MSC; 7. Anchor MSC to Gateway MSC; 8. Gateway MSC to SC.](6481339ecf03de9d3565629c3d7b31fc_img.jpg) + +``` +sequenceDiagram + participant SC + participant Gateway MSC + participant Anchor MSC + participant GCR + Note right of SC: 1 + SC->>Gateway MSC: + Note right of Gateway MSC: 2 + Gateway MSC->>Anchor MSC: + Note right of Anchor MSC: 3 + Anchor MSC->>Gateway MSC: + Note right of Gateway MSC: 4 + Gateway MSC->>Anchor MSC: + Note right of Anchor MSC: 5 + Anchor MSC->>GCR: + Note right of GCR: 6 + GCR->>Anchor MSC: + Note right of Anchor MSC: 7 + Anchor MSC->>Gateway MSC: + Note right of Gateway MSC: 8 + Gateway MSC->>SC: +``` + +Sequence diagram showing the mobile terminated short message transfer procedure for VGCS. Lifelines: Anchor MSC, GCR, Gateway MSC, SC. Steps: 1. SC to Gateway MSC; 2. Gateway MSC to Anchor MSC; 3. Anchor MSC to Gateway MSC; 4. Gateway MSC to Anchor MSC; 5. Anchor MSC to GCR; 6. GCR to Anchor MSC; 7. Anchor MSC to Gateway MSC; 8. Gateway MSC to SC. + +4372 +4373 **Figure 23.7/1: Mobile terminated short message for VGCS service procedures** + +``` + +4374 1) Short Message (3GPP TS 23.040). +4375 2) TCAP BEGIN (*) +4376 3) TCAP CONTINUE (*) +4377 4) MAP_MT_FORWARD_SM_FOR_VGCS. +4378 5) GCR_SMS_INTERROGATION (3GPP TS 43.068). +4379 6) GCR_SMS_INTERROGATION_ACK (3GPP TS 43.068). +4380 7) MAP_MT_FORWARD_SM_FOR_VGCS_ACK. +4381 8) Short Message Acknowledgement (3GPP TS 23.040). +4382 +4383 (*) If +4384 a) +4385 - the capacity of a message signal unit in the lower layers of the protocol is enough to carry the +4386 content of the MAP_OPEN request and the content of the MAP_MT_FORWARD_SM_FOR_VGCS +4387 request in a single TC message, +4388 +4389 and +4390 b) the SMS Gateway MSC operator and the serving node (Anchor-MSC) operator +4391 agreed not to use the TCAP handshake countermeasure against SMS fraud for +4392 messages exchanged between their networks (see 3GPP TS 33.204 [34a]) +4393 then +4394 the TCAP handshake may be omitted. +4395 + +``` + +## 4396 23.7.1 Procedure in the SMS-GMSC + +4397 The process starts when the SMS-GMSC receives an SC\_RP\_MT\_DATA indication from a Service Centre. The MAP +4398 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +4399     Receive\_Open\_Cnf     see clause 25.1.2; + +4400     Check\_Confirmation    see clause 25.2.2. + +4401 The mobile terminated short message transfer for VGCS process in the SMS-GMSC is shown in figure 23.7/2. + +## 4402 23.7.2 Procedure in the Anchor MSC + +4403 The process starts when the MSC receives a dialogue opening request with the application context shortMsgMT-Relay- +4404 VGCS-Context. The MAP process invokes macros not defined in this clause; the definitions of these macros can be +4405 found as follows: + +4406     Receive\_Open\_Ind     see clause 25.1.1; + +4407 The mobile terminated short message transfer for VGCS process in the Anchor MSC is shown in figure 23.7/3 + +4408 Procedure MT\_SM\_VGCS\_GMSC sheet 1: The decision box "TCAP Handshake required" takes the "yes" or "no" exit +4409 depending on agreements between the Serving MSC's operator and the SMS Gateway MSC's operator (see 3GPP TS +4410 33.204 [34a]). + +process MT\_SM\_VGCS\_GMSC + +1(2) + +Process in the SMS-GMSC to handle delivery of an MT short message to a VGCS call + +Signals to/from the left are to/from the short message service centre, signals to/from the right are to/from the Group Call Anchor MSC + +![Flowchart for process MT_SM_VGCS_GMSC. It starts with an entry point leading to a 'Null' state, then an 'SC_RP_MT_DATA_ind' message (including a Group Call Reference Number). A decision 'Message segmenting needed?' follows. If 'yes', it goes to 'MAP_OPEN_req' and 'MAP_DELIMITER_req'. If 'no', it checks 'TCAP Handshake required?'. If 'yes', it goes to 'MAP_OPEN_req' and 'MAP_DELIMITER_req'. If 'no', it goes to 'MAP_OPEN_req', 'MAP_MT_FORWARD_SM_VGCS_req', and 'MAP_DELIMITER_req'. Both 'MAP_OPEN_req' paths lead to 'Receive_Open_Cnf'. From 'Receive_Open_Cnf', 'Error, Vr' leads to 'Set RP_ERROR: System Failure' -> 'SC_RP_ERROR_req' -> 'NULL'. 'OK' leads to 'Wait_For_Confirm'.](14aaccd030ccca62597f3c5034f49061_img.jpg) + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> SC_RP_MT_DATA_ind{{SC_RP_MT_DATA_ind}} + Note1[including a Group Call Reference Number] -.-> SC_RP_MT_DATA_ind + SC_RP_MT_DATA_ind --> Segmenting{Message segmenting needed?} + Segmenting -- yes --> MAP_OPEN_req1{{MAP_OPEN_req +MAP_DELIMITER_req}} + Segmenting -- no --> TCAP{TCAP Handshake required?} + TCAP -- yes --> MAP_OPEN_req1 + TCAP -- no --> MAP_OPEN_req2{{MAP_OPEN_req +MAP_MT_FORWARD_SM_VGCS_req +MAP_DELIMITER_req}} + MAP_OPEN_req1 --> Receive_Open_Cnf1[Receive_Open_Cnf] + MAP_OPEN_req2 --> Receive_Open_Cnf2[Receive_Open_Cnf] + Receive_Open_Cnf1 -- "Error, Vr" --> Set_RP_Error1[Set RP_ERROR: +System Failure] + Set_RP_Error1 --> SC_RP_ERROR_req1{{SC_RP_ERROR_req}} + SC_RP_ERROR_req1 --> NULL1_end([NULL]) + Receive_Open_Cnf1 -- OK --> Wait_For_Confirm1[Wait_For_Confirm] + Receive_Open_Cnf2 -- "Error, Vr" --> Set_RP_Error2[Set RP_ERROR: +System Failure] + Set_RP_Error2 --> SC_RP_ERROR_req2{{SC_RP_ERROR_req}} + SC_RP_ERROR_req2 --> NULL2_end([NULL]) + Receive_Open_Cnf2 -- OK --> MAP_MT_FORWARD_SM_VGCS_req{{MAP_MT_FORWARD_SM_VGCS_req +MAP_DELIMITER_req}} + MAP_MT_FORWARD_SM_VGCS_req --> Wait_For_Confirm2[Wait_For_Confirm] + +``` + +Flowchart for process MT\_SM\_VGCS\_GMSC. It starts with an entry point leading to a 'Null' state, then an 'SC\_RP\_MT\_DATA\_ind' message (including a Group Call Reference Number). A decision 'Message segmenting needed?' follows. If 'yes', it goes to 'MAP\_OPEN\_req' and 'MAP\_DELIMITER\_req'. If 'no', it checks 'TCAP Handshake required?'. If 'yes', it goes to 'MAP\_OPEN\_req' and 'MAP\_DELIMITER\_req'. If 'no', it goes to 'MAP\_OPEN\_req', 'MAP\_MT\_FORWARD\_SM\_VGCS\_req', and 'MAP\_DELIMITER\_req'. Both 'MAP\_OPEN\_req' paths lead to 'Receive\_Open\_Cnf'. From 'Receive\_Open\_Cnf', 'Error, Vr' leads to 'Set RP\_ERROR: System Failure' -> 'SC\_RP\_ERROR\_req' -> 'NULL'. 'OK' leads to 'Wait\_For\_Confirm'. + +4411 + +4412 + +Figure 23.7/2 (sheet 1 of 2): Process MT\_SM\_VGCS\_GMSC + +process MT\_SM\_VGCS\_GMSC + +2(2) + +Process in the SMS-GMSC to handle delivery of an MT short message to a VGCS call + +Signals to/from the left are to/from the short message service centre, signals to/from the right are to/from the Group Call Anchor MSC + +![State transition diagram for process MT_SM_VGCS_GMSC. It starts with 'Wait_For_Confirm' leading to three parallel paths: 1) MAP_FORWARD_SM_VGCS_cnf -> Check_Confirmation -> OK leads to SC_RP_ACK_req -> NULL; 2) MAP_NOTICE_ind -> MAP_CLOSE_req -> SET_RP_ERROR -> SC_RP_ERROR_req -> NULL; 3) MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind -> SET_RP_ERROR -> SC_RP_ERROR_req -> NULL. A 'User Error, Provider Error, Data Error' label is present between Check_Confirmation and SET_RP_ERROR.](b58b410e1be789df60ddeae5e55f94fb_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Wait_For_Confirm + state "MAP_FORWARD_SM_VGCS_cnf" as MAP_FORWARD_SM_VGCS_cnf + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" as MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + state "Check_Confirmation" as Check_Confirmation + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "SET_RP_ERROR" as SET_RP_ERROR + state "SC_RP_ACK_req" as SC_RP_ACK_req + state "SC_RP_ERROR_req" as SC_RP_ERROR_req + state NULL + + Wait_For_Confirm --> MAP_FORWARD_SM_VGCS_cnf + Wait_For_Confirm --> MAP_NOTICE_ind + Wait_For_Confirm --> MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + + MAP_FORWARD_SM_VGCS_cnf --> Check_Confirmation + Check_Confirmation --> OK + Check_Confirmation --> User_Error, Provider_Error, Data_Error + OK --> SC_RP_ACK_req + User_Error, Provider_Error, Data_Error --> SET_RP_ERROR + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind --> SET_RP_ERROR + SET_RP_ERROR --> SC_RP_ERROR_req + SC_RP_ACK_req --> NULL + SC_RP_ERROR_req --> NULL + +``` + +State transition diagram for process MT\_SM\_VGCS\_GMSC. It starts with 'Wait\_For\_Confirm' leading to three parallel paths: 1) MAP\_FORWARD\_SM\_VGCS\_cnf -> Check\_Confirmation -> OK leads to SC\_RP\_ACK\_req -> NULL; 2) MAP\_NOTICE\_ind -> MAP\_CLOSE\_req -> SET\_RP\_ERROR -> SC\_RP\_ERROR\_req -> NULL; 3) MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind -> SET\_RP\_ERROR -> SC\_RP\_ERROR\_req -> NULL. A 'User Error, Provider Error, Data Error' label is present between Check\_Confirmation and SET\_RP\_ERROR. + +4413 + +4414 + +Figure 23.7/2 (sheet 2 of 2): Process MT\_SM\_VGCS\_GMSC + +process MT\_SM\_VGCS\_Anchor\_MSC + +1(2) + +Process in the Group Call Anchor MSC to handle delivery of an MT short message to a VGCS call + +Signals to/from the left are to/from the SMS GMSC; signals to/from the right are to/from the the application process in the Anchor MSC + +![State transition diagram for process MT_SM_VGCS_Anchor_MSC. It starts at an initial state, goes to IDLE, then receives an Open_indication. From there, it branches based on 'Error, Vr' (back to IDLE), 'OK' (to a decision 'Message protected by MAPsec'), 'yes' (to 'Wait_For_Service_Primitive'), or 'no' (to 'TCAP Handshake required'). From 'TCAP Handshake required', 'no' leads to 'Wait_For_Service_Primitive' and 'yes' leads to 'Wait_For_DELIMITER'. Both wait states lead to a horizontal line with four options: 'MAP_MT_FORWARD_SM_VGCS_ind' (leading to 'Set Error System Failure' then 'MAP_MT_FORWARD_SM_VGCS_rsp' then 'MAP_CLOSE_req' then IDLE), 'MAP_DELIMITER_ind' (leading to 'MAP_DELIMITER_req' then 'Wait_For_Service_Primitive'), 'MAP_U_ABORT_ind / MAP_P_ABORT_ind / MAP_CLOSE_ind' (leading directly to IDLE), and 'MAP_NOTICE_ind' (leading to 'MAP_CLOSE_req' then IDLE).](8fc68c981924a8acc53f3b4bb79bf158_img.jpg) + +``` + +stateDiagram-v2 + [*] --> IDLE + IDLE --> Receive_Open_ind + state "Receive_Open_ind" as Receive_Open_ind + Receive_Open_ind --> IDLE : Error, Vr + Receive_Open_ind --> Message_protected_by_MAPsec : OK + state "Message protected by MAPsec" as Message_protected_by_MAPsec + Message_protected_by_MAPsec --> Wait_For_Service_Primitive : yes + Message_protected_by_MAPsec --> TCAP_Handshake_required : no + state "TCAP Handshake required" as TCAP_Handshake_required + TCAP_Handshake_required --> Wait_For_Service_Primitive : no + TCAP_Handshake_required --> Wait_For_DELIMITER : yes + state "Wait_For_Service_Primitive" as Wait_For_Service_Primitive + state "Wait_For_DELIMITER" as Wait_For_DELIMITER + Wait_For_Service_Primitive --> MAP_MT_FORWARD_SM_VGCS_ind + Wait_For_DELIMITER --> MAP_MT_FORWARD_SM_VGCS_ind + state "MAP_MT_FORWARD_SM_VGCS_ind" as MAP_MT_FORWARD_SM_VGCS_ind + state "MAP_DELIMITER_ind" as MAP_DELIMITER_ind + state "MAP_U_ABORT_ind / MAP_P_ABORT_ind / MAP_CLOSE_ind" as MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + MAP_MT_FORWARD_SM_VGCS_ind --> Set_Error_System_Failure + state "Set Error System Failure" as Set_Error_System_Failure + Set_Error_System_Failure --> MAP_MT_FORWARD_SM_VGCS_rsp + state "MAP_MT_FORWARD_SM_VGCS_rsp" as MAP_MT_FORWARD_SM_VGCS_rsp + MAP_MT_FORWARD_SM_VGCS_rsp --> MAP_CLOSE_req + state "MAP_CLOSE_req" as MAP_CLOSE_req + MAP_CLOSE_req --> IDLE + MAP_DELIMITER_ind --> MAP_DELIMITER_req + state "MAP_DELIMITER_req" as MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_Service_Primitive + MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind --> IDLE + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> IDLE + +``` + +State transition diagram for process MT\_SM\_VGCS\_Anchor\_MSC. It starts at an initial state, goes to IDLE, then receives an Open\_indication. From there, it branches based on 'Error, Vr' (back to IDLE), 'OK' (to a decision 'Message protected by MAPsec'), 'yes' (to 'Wait\_For\_Service\_Primitive'), or 'no' (to 'TCAP Handshake required'). From 'TCAP Handshake required', 'no' leads to 'Wait\_For\_Service\_Primitive' and 'yes' leads to 'Wait\_For\_DELIMITER'. Both wait states lead to a horizontal line with four options: 'MAP\_MT\_FORWARD\_SM\_VGCS\_ind' (leading to 'Set Error System Failure' then 'MAP\_MT\_FORWARD\_SM\_VGCS\_rsp' then 'MAP\_CLOSE\_req' then IDLE), 'MAP\_DELIMITER\_ind' (leading to 'MAP\_DELIMITER\_req' then 'Wait\_For\_Service\_Primitive'), 'MAP\_U\_ABORT\_ind / MAP\_P\_ABORT\_ind / MAP\_CLOSE\_ind' (leading directly to IDLE), and 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req' then IDLE). + +4415 + +4416 + +Figure 23.7/3 (sheet 1 of 2): Process MT\_SM\_VGCS\_Anchor MSC + +process MT\_SM\_VGCS\_Anchor\_MSC + +2(2) + +Process in the Group Call Anchor MSC to handle delivery of an MT short message to a VGCS call + +Signals to/from the left are to/from the SMS GMSC; signals to/from the right are to/from the the application process in the Anchor MSC + +![State transition diagram for process MT_SM_VGCS_Anchor_MSC. It starts with Wait_For_Service_Primitive, leading to four possible indications: MAP_DELIMITER_ind, MAP_MT_FORWARD_SM_VGCS_ind, MAP_U_ABORT_ind/MAP_P_ABORT_ind/MAP_CLOSE_ind, and MAP_NOTICE_ind. The first leads to MAP_DELIMITER_req and back to Wait_For_Service_Primitive. The second leads to MT_Forward_SM_VGCS (referencing 3GPP TS 43.068) and then to Wait_For_Response. The third and fourth lead to MAP_CLOSE_req and then to IDLE. From Wait_For_Response, a positive response leads to set result and a negative response leads to set error, both then leading to MAP_MT_FORWARD_SM_VGCS_rsp/MAP_CLOSE_req and finally to IDLE.](6bf6442555ad45b5b3ec1f6e174c08ce_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Wait_For_Service_Primitive + state "Wait_For_Service_Primitive" as Wait_For_Service_Primitive + state "IDLE" as IDLE + state "MT_Forward_SM_VGCS" as MT_Forward_SM_VGCS + state "Wait_For_Response" as Wait_For_Response + state "set result" as set result + state "set error" as set error + state "MAP_MT_FORWARD_SM_VGCS_rsp / MAP_CLOSE_req" as MAP_MT_FORWARD_SM_VGCS_rsp / MAP_CLOSE_req + + Wait_For_Service_Primitive --> MAP_DELIMITER_ind + Wait_For_Service_Primitive --> MAP_MT_FORWARD_SM_VGCS_ind + Wait_For_Service_Primitive --> MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind + Wait_For_Service_Primitive --> MAP_NOTICE_ind + + MAP_DELIMITER_ind --> MAP_DELIMITER_req + MAP_DELIMITER_req --> Wait_For_Service_Primitive + + MAP_MT_FORWARD_SM_VGCS_ind --> MT_Forward_SM_VGCS + MT_Forward_SM_VGCS --> Wait_For_Response + + MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> IDLE + + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> IDLE + + Wait_For_Response --> positive_response + Wait_For_Response --> negative_response + + positive_response --> set result + negative_response --> set error + + set result --> MAP_MT_FORWARD_SM_VGCS_rsp / MAP_CLOSE_req + set error --> MAP_MT_FORWARD_SM_VGCS_rsp / MAP_CLOSE_req + + MAP_MT_FORWARD_SM_VGCS_rsp / MAP_CLOSE_req --> IDLE + +``` + +State transition diagram for process MT\_SM\_VGCS\_Anchor\_MSC. It starts with Wait\_For\_Service\_Primitive, leading to four possible indications: MAP\_DELIMITER\_ind, MAP\_MT\_FORWARD\_SM\_VGCS\_ind, MAP\_U\_ABORT\_ind/MAP\_P\_ABORT\_ind/MAP\_CLOSE\_ind, and MAP\_NOTICE\_ind. The first leads to MAP\_DELIMITER\_req and back to Wait\_For\_Service\_Primitive. The second leads to MT\_Forward\_SM\_VGCS (referencing 3GPP TS 43.068) and then to Wait\_For\_Response. The third and fourth lead to MAP\_CLOSE\_req and then to IDLE. From Wait\_For\_Response, a positive response leads to set result and a negative response leads to set error, both then leading to MAP\_MT\_FORWARD\_SM\_VGCS\_rsp/MAP\_CLOSE\_req and finally to IDLE. + +4417 + +4418 + +Figure 23.7/3 (sheet 2 of 2): Process MT\_SM\_VGCS\_Anchor MSC + +4419 + +## 24 GPRS process description + +4420 The MAP GPRS procedures are used for the Network Requested PDP-Context Activation procedures. + +4421 The stage 2 specification for General Packet Radio Service (GPRS) is in 3GPP TS 23.060 [104]. + +## 4422 24.1 Procedure for retrieval of routing information for GPRS + +### 4423 24.1.1 Process in the GGSN + +4424 The MAP process in the GGSN to request routing information for a network requested PDP context activation is +4425 shown in figure 24.1/2. The MAP process invokes macros not defined in this clause; the definition of these macros can +4426 be found as follows: + +4427     Receive\_Open\_Cnf see clause 25.1.2; + +4428     Check\_Confirmation see clause 25.2.2. + +### 4429 24.1.2 Process in the HLR + +4430 The MAP process in the HLR to provide routing information for a network-requested PDP context activation is shown +4431 in figure 24.1/1. The MAP process invokes macros not defined in this clause; the definitions of these macros can be +4432 found as follows: + +4433     Receive\_Open\_Ind see clause 25.1.1; + +4434     Check\_Indication see clause 25.2.1. + +![State transition diagram for SRI_GPRS_GGSN process. It starts at an initial state, goes to Idle, then Send Routing Info for GPRS. It then branches based on MAP messages (OPEN_req, SEND_ROUTING_INFO_FOR_GPRS_req, DELIMITER_req). From Receive_Open_Cnf, it branches to Wait_For_Routeing_Info (OK) or Perform MAP Vr dialogue (Error). Wait_For_Routeing_Info leads to a decision point for MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind, MAP_NOTICE_ind, and MAP_SEND_ROUTING_INFO_FOR_GPRS_cnf. MAP_NOTICE_ind leads to MAP_CLOSE_req, which then leads to a decision point for Provider Error, Data Error, User Error, and OK. Provider Error, Data Error, and User Error lead to Set negative response: System failure, which then leads to Send Routing Info for GPRS negative response and back to Idle. OK leads to Send Routing Info for GPRS ack and back to Idle.](4ba8a90dcc7c49bb9b60c5326193057d_img.jpg) + +**process SRI\_GPRS\_GGSN** **SRI\_GPRS\_GGSN1(1)** + +Process in the GGSN to retrieve routing information to establish a network-requested PDP context + +Signals to/from the left are to/from the application process in the GGSN; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> SendRoutingInfo[Send Routing Info for GPRS] + SendRoutingInfo --> OpenCnf[Receive_Open_Cnf] + OpenCnf --> WaitForRouteingInfo[Wait_For_Routeing_Info] : OK + OpenCnf --> PerformMAPVr[Perform MAP Vr dialogue] : Error + PerformMAPVr --> Idle2[Idle] + WaitForRouteingInfo --> Decision1{ } + Decision1 --> MAPUAbort[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Decision1 --> MAPNotice[MAP_NOTICE_ind] + Decision1 --> MAPSendRoutingInfoCnf[MAP_SEND_ROUTING_INFO_FOR_GPRS_cnf] + MAPNotice --> MAPCloseReq[MAP_CLOSE_req] + MAPCloseReq --> Decision2{ } + Decision2 --> SetNegativeResponse[Set negative response: System failure] : Provider Error, Data Error + Decision2 --> SendRoutingInfoNeg[Send Routing Info for GPRS negative response] : User Error + Decision2 --> SendRoutingInfoAck[Send Routing Info for GPRS ack] : OK + SetNegativeResponse --> SendRoutingInfoNeg + SendRoutingInfoNeg --> Idle3[Idle] + SendRoutingInfoAck --> Idle4[Idle] + +``` + +State transition diagram for SRI\_GPRS\_GGSN process. It starts at an initial state, goes to Idle, then Send Routing Info for GPRS. It then branches based on MAP messages (OPEN\_req, SEND\_ROUTING\_INFO\_FOR\_GPRS\_req, DELIMITER\_req). From Receive\_Open\_Cnf, it branches to Wait\_For\_Routeing\_Info (OK) or Perform MAP Vr dialogue (Error). Wait\_For\_Routeing\_Info leads to a decision point for MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind, MAP\_NOTICE\_ind, and MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS\_cnf. MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req, which then leads to a decision point for Provider Error, Data Error, User Error, and OK. Provider Error, Data Error, and User Error lead to Set negative response: System failure, which then leads to Send Routing Info for GPRS negative response and back to Idle. OK leads to Send Routing Info for GPRS ack and back to Idle. + +4435 + +4436 + +Figure 24.1/1: Process SRI\_GPRS\_GGSN + +process SRI\_GPRS\_HLR + +SRI\_GPRS\_HLR1(1) + +Process in the HLR to provide routing information to establish a network-requested PDP context + +Signals to/from the left are to/from the GGSN; signals to/from the right are to/from the GPRS application process in the HLR + +![State transition diagram for process SRI_GPRS_HLR. The process starts at an initial state leading to 'Idle'. From 'Idle', it receives an 'Open_Ind' signal. The 'Receive_Open_Ind' block has three outputs: 'OK' leading to 'Wait_For_Service_Indication', 'Error' leading back to 'Idle', and 'Vr' leading to 'Perform MAP Vr dialogue' which then returns to 'Idle'. From 'Wait_For_Service_Indication', there are three internal transitions: 'MAP_SEND_ROUTING_INFO_FOR_GPRS_ind' (left), 'MAP_P_ABORT_ind' (right), and 'MAP_NOTICE_ind' (right). 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req' (right) which returns to 'Idle'. 'MAP_P_ABORT_ind' also leads to 'MAP_CLOSE_req' (right) which returns to 'Idle'. 'MAP_SEND_ROUTING_INFO_FOR_GPRS_ind' leads to 'Check_Indication'. 'Check_Indication' has 'OK' leading to 'Send Routing Info for GPRS' (left) and 'Error' leading to the bottom 'Idle' state. 'Send Routing Info for GPRS' (left) leads to 'Wait_For_Routing_Info'. From 'Wait_For_Routing_Info', there are three internal transitions: 'Send Routing Info for GPRS ack' (left), 'Send Routing Info for GPRS negative response' (right), and 'MAP_NOTICE_ind' (right). 'Send Routing Info for GPRS ack' (left) leads to 'Set Routing info' (left) which returns to the bottom 'Idle' state. 'Send Routing Info for GPRS negative response' (right) leads to 'Set User Error' (right) which returns to the bottom 'Idle' state. 'MAP_NOTICE_ind' (right) leads to 'MAP_CLOSE_req' (right) which returns to the bottom 'Idle' state. Additionally, 'MAP_P_ABORT_ind' (right) from 'Wait_For_Routing_Info' leads to a block with 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind' (right) which returns to the bottom 'Idle' state. Finally, 'MAP_SEND_ROUTING_INFO_FOR_GPRS_rsp' and 'MAP_CLOSE_req' (left) lead to the bottom 'Idle' state.](b2108e34a59251458599a28c389bbcc4_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_Ind + state "Receive_Open_Ind" as Receive_Open_Ind + Receive_Open_Ind --> Wait_For_Service_Indication : OK + Receive_Open_Ind --> Idle : Error + Receive_Open_Ind --> Perform_MAP_Vr_dialogue : Vr + state "Perform MAP Vr dialogue" as Perform_MAP_Vr_dialogue + Perform_MAP_Vr_dialogue --> Idle + state "Wait_For_Service_Indication" as Wait_For_Service_Indication + Wait_For_Service_Indication --> MAP_SEND_ROUTING_INFO_FOR_GPRS_ind : MAP_SEND_ROUTING_INFO_FOR_GPRS_ind + Wait_For_Service_Indication --> MAP_P_ABORT_ind : MAP_P_ABORT_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind : MAP_NOTICE_ind + state "MAP_SEND_ROUTING_INFO_FOR_GPRS_ind" as MAP_SEND_ROUTING_INFO_FOR_GPRS_ind + state "MAP_P_ABORT_ind" as MAP_P_ABORT_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req : MAP_CLOSE_req + MAP_CLOSE_req --> Idle + MAP_P_ABORT_ind --> MAP_CLOSE_req : MAP_CLOSE_req + MAP_CLOSE_req --> Idle + MAP_SEND_ROUTING_INFO_FOR_GPRS_ind --> Check_Indication + state "Check_Indication" as Check_Indication + Check_Indication --> Send_Routing_Info_for_GPRS : OK + Check_Indication --> Idle : Error + state "Send Routing Info for GPRS" as Send_Routing_Info_for_GPRS + Send_Routing_Info_for_GPRS --> Wait_For_Routing_Info + state "Wait_For_Routing_Info" as Wait_For_Routing_Info + Wait_For_Routing_Info --> Send_Routing_Info_for_GPRS_ack : Send Routing Info for GPRS ack + Wait_For_Routing_Info --> Send_Routing_Info_for_GPRS_neg_resp : Send Routing Info for GPRS negative response + Wait_For_Routing_Info --> MAP_NOTICE_ind : MAP_NOTICE_ind + state "Send Routing Info for GPRS ack" as Send_Routing_Info_for_GPRS_ack + state "Send Routing Info for GPRS negative response" as Send_Routing_Info_for_GPRS_neg_resp + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + Send_Routing_Info_for_GPRS_ack --> Set_Routing_info : Set Routing info + Set_Routing_info --> Idle + Send_Routing_Info_for_GPRS_neg_resp --> Set_User_Error : Set User Error + Set_User_Error --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req : MAP_CLOSE_req + MAP_CLOSE_req --> Idle + Wait_For_Routing_Info --> MAP_P_ABORT_ind : MAP_P_ABORT_ind + state "MAP_P_ABORT_ind" as MAP_P_ABORT_ind + MAP_P_ABORT_ind --> MAP_U_ABORT_ind_block : MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" as MAP_U_ABORT_ind_block + MAP_U_ABORT_ind_block --> Idle + MAP_SEND_ROUTING_INFO_FOR_GPRS_rsp : MAP_SEND_ROUTING_INFO_FOR_GPRS_rsp + MAP_CLOSE_req : MAP_CLOSE_req + MAP_SEND_ROUTING_INFO_FOR_GPRS_rsp --> Idle + MAP_CLOSE_req --> Idle + +``` + +State transition diagram for process SRI\_GPRS\_HLR. The process starts at an initial state leading to 'Idle'. From 'Idle', it receives an 'Open\_Ind' signal. The 'Receive\_Open\_Ind' block has three outputs: 'OK' leading to 'Wait\_For\_Service\_Indication', 'Error' leading back to 'Idle', and 'Vr' leading to 'Perform MAP Vr dialogue' which then returns to 'Idle'. From 'Wait\_For\_Service\_Indication', there are three internal transitions: 'MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS\_ind' (left), 'MAP\_P\_ABORT\_ind' (right), and 'MAP\_NOTICE\_ind' (right). 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req' (right) which returns to 'Idle'. 'MAP\_P\_ABORT\_ind' also leads to 'MAP\_CLOSE\_req' (right) which returns to 'Idle'. 'MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS\_ind' leads to 'Check\_Indication'. 'Check\_Indication' has 'OK' leading to 'Send Routing Info for GPRS' (left) and 'Error' leading to the bottom 'Idle' state. 'Send Routing Info for GPRS' (left) leads to 'Wait\_For\_Routing\_Info'. From 'Wait\_For\_Routing\_Info', there are three internal transitions: 'Send Routing Info for GPRS ack' (left), 'Send Routing Info for GPRS negative response' (right), and 'MAP\_NOTICE\_ind' (right). 'Send Routing Info for GPRS ack' (left) leads to 'Set Routing info' (left) which returns to the bottom 'Idle' state. 'Send Routing Info for GPRS negative response' (right) leads to 'Set User Error' (right) which returns to the bottom 'Idle' state. 'MAP\_NOTICE\_ind' (right) leads to 'MAP\_CLOSE\_req' (right) which returns to the bottom 'Idle' state. Additionally, 'MAP\_P\_ABORT\_ind' (right) from 'Wait\_For\_Routing\_Info' leads to a block with 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind' (right) which returns to the bottom 'Idle' state. Finally, 'MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS\_rsp' and 'MAP\_CLOSE\_req' (left) lead to the bottom 'Idle' state. + +4437 + +4438 + +Figure 24.1/2: Process SRI\_GPRS\_HLR + +## 4439 24.2 Procedure for reporting failure to establish a network 4440 requested PDP context + +### 4441 24.2.1 Process in the GGSN + +4442 The MAP process in the GGSN to report the failure to establish a network requested PDP context is shown in figure +4443 24.2/2. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as +4444 follows: + +4445     Receive\_Open\_Cnf see clause 25.1.2; + +4446     Check\_Confirmation see clause 25.2.2. + +### 4447 24.2.2 Process in the HLR + +4448 The MAP process in the HLR to handle a notification from the GGSN that a network requested PDP context could not +4449 be established is shown in figure 24.2/2. The MAP process invokes macros not defined in this clause; the definitions of +4450 these macros can be found as follows: + +4451     Receive\_Open\_Ind see clause 25.1.1; + +4452     Check Indication see clause 25.2.1. + +![State transition diagram for process Failure_Report_GGSN. It starts at Idle, goes to Failure report, then to a state with MAP_OPEN_req, MAP_FAILURE_REPORT_req, and MAP_DELIMITER_req. It then receives an Open_Cnf and enters Wait_For_HLR_Response. From there, it can receive MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind (leading to Vr, Error), MAP_NOTICE_ind (leading to MAP_CLOSE_req), or MAP_FAILURE_REPORT_cnf (leading to Check Confirmation). Check Confirmation leads to either Set negative response: System failure (leading to Failure report negative response and Idle), or Failure report ack (leading to Idle). MAP_CLOSE_req also leads to either Set negative response: System failure or Idle based on Provider Error, Data Error or User Error.](0435bdd4c5e220acd2db04fce162b313_img.jpg) + +**process Failure\_Report\_GGSN** **FR\_GGSN1(1)** + +Process in the GGSN to report a failure to establish a network-requested PDP context + +Signals to/from the left are to/from the application process in the GGSN; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Failure_report: Failure report + Failure_report --> State1: MAP_OPEN_req, MAP_FAILURE_REPORT_req, MAP_DELIMITER_req + State1 --> Receive_Open_Cnf: Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_HLR_Response: OK + Wait_For_HLR_Response --> State2: MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + Wait_For_HLR_Response --> State3: MAP_NOTICE_ind + Wait_For_HLR_Response --> State4: MAP_FAILURE_REPORT_cnf + State2 --> Vr_Error: Vr, Error + State3 --> MAP_CLOSE_req: MAP_CLOSE_req + State4 --> Check_Confirmation: Check Confirmation + Check_Confirmation --> Set_Negative_Response: Set negative response: System failure + Check_Confirmation --> Failure_report_ack: Failure report ack + MAP_CLOSE_req --> Set_Negative_Response: Provider Error, Data Error + MAP_CLOSE_req --> Idle: User Error + Set_Negative_Response --> Failure_report_negative_response: Failure report negative response + Failure_report_negative_response --> Idle + Failure_report_ack --> Idle + +``` + +State transition diagram for process Failure\_Report\_GGSN. It starts at Idle, goes to Failure report, then to a state with MAP\_OPEN\_req, MAP\_FAILURE\_REPORT\_req, and MAP\_DELIMITER\_req. It then receives an Open\_Cnf and enters Wait\_For\_HLR\_Response. From there, it can receive MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind (leading to Vr, Error), MAP\_NOTICE\_ind (leading to MAP\_CLOSE\_req), or MAP\_FAILURE\_REPORT\_cnf (leading to Check Confirmation). Check Confirmation leads to either Set negative response: System failure (leading to Failure report negative response and Idle), or Failure report ack (leading to Idle). MAP\_CLOSE\_req also leads to either Set negative response: System failure or Idle based on Provider Error, Data Error or User Error. + +4453 + +4454 + +Figure 24.2/1: Process Failure\_Report\_GGSN + +![State transition diagram for process Failure_Report_HLR. The process starts at an initial state, goes to Idle, then receives an Open_Indication. From there, it can go to Wait_For_Service_Indication (OK path) or back to Idle (Vr, Error path). From Wait_For_Service_Indication, it branches into three paths: 1) MAP_FAILURE_REPORT_ind leads to Check_Indication, then either Failure report (OK) or Error. Failure report leads to Wait_For_Application_Response, which then branches into Failure report ack (leading to Idle), Failure report negative response (leading to Set User Error), or a response message (MAP_FAILURE_REPORT_rsp, MAP_CLOSE_req) leading to Idle. 2) MAP_P_ABORT_ind leads directly to Idle. 3) MAP_NOTICE_ind leads to MAP_CLOSE_req, which leads to Idle.](3b645d2a2a405391a3c5592e50cdb4ba_img.jpg) + +**process Failure\_Report\_HLR** **FR\_HLR1(1)** + +Process in the HLR to handle a failure report from the GGSN + +Signals to/from the left are to/from the GGSN; + signals to/from the right are to/from the GPRS application process in the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_Ind + Receive_Open_Ind --> Wait_For_Service_Indication: OK + Receive_Open_Ind --> Idle: Vr, Error + Wait_For_Service_Indication --> MAP_FAILURE_REPORT_ind + Wait_For_Service_Indication --> MAP_P_ABORT_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + MAP_FAILURE_REPORT_ind --> Check_Indication + Check_Indication --> Failure_report: OK + Check_Indication --> Error + Failure_report --> Wait_For_Application_Response + Wait_For_Application_Response --> Failure_report_ack + Wait_For_Application_Response --> Failure_report_negative_response + Wait_For_Application_Response --> MAP_FAILURE_REPORT_rsp + Failure_report_ack --> Idle + Failure_report_negative_response --> Set_User_Error + Set_User_Error --> Failure_report_ack + MAP_FAILURE_REPORT_rsp --> Idle + MAP_P_ABORT_ind --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + +``` + +State transition diagram for process Failure\_Report\_HLR. The process starts at an initial state, goes to Idle, then receives an Open\_Indication. From there, it can go to Wait\_For\_Service\_Indication (OK path) or back to Idle (Vr, Error path). From Wait\_For\_Service\_Indication, it branches into three paths: 1) MAP\_FAILURE\_REPORT\_ind leads to Check\_Indication, then either Failure report (OK) or Error. Failure report leads to Wait\_For\_Application\_Response, which then branches into Failure report ack (leading to Idle), Failure report negative response (leading to Set User Error), or a response message (MAP\_FAILURE\_REPORT\_rsp, MAP\_CLOSE\_req) leading to Idle. 2) MAP\_P\_ABORT\_ind leads directly to Idle. 3) MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req, which leads to Idle. + +4455 + +4456 + +**Figure 24.2/2: Process Failure\_Report\_HLR** + +4457 **24.3** Procedure for reporting that an MS has become reachable +4458 for GPRS + +4459 **24.3.1** Process in the HLR + +4460 The MAP process in the HLR to report that an MS is reachable for GPRS is shown in figure 24.3/1. The MAP process +4461 invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +4462     Receive\_Open\_Cnf see clause 25.1.2; + +4463     Check\_Confirmation see clause 25.2.2. + +4464 **24.3.2** Process in the GGSN for Note Ms Present For Gprs + +4465 The MAP process in the GGSN to handle a notification that the subscriber is present for GPRS again is shown in figure +4466 24.3/2. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as +4467 follows: + +4468     Receive\_Open\_Ind see clause 25.1.1; + +4469     Check\_Indication see clause 25.2.1. + +![State transition diagram for process Note_MS_Present_for_GPRS_HLR. The process starts at an Idle state, transitions to 'Note MS present for GPRS', then to a state where it sends MAP_OPEN_req, MAP_NOTE_MS_PRESENT_FOR_GPRS_req, and MAP_DELIMITER_req. It then receives an Open_Cnf. If OK, it goes to 'Wait_For_GGSN_Response'. From there, it can receive MAP_U_ABORT_ind, MAP_P_ABORT_ind, or MAP_CLOSE_ind (leading to a negative response), MAP_NOTICE_ind (leading to a close request), or MAP_NOTE_MS_PRESENT_FOR_GPRS_cnf (leading to a confirmation check). A confirmation check can result in a negative response, a provider/data error, a user error, or an OK (leading to an ack and back to Idle).](672e2bbc82c7be834d21e0dd0f839194_img.jpg) + +**process Note\_MS\_Present\_for\_GPRS\_HLR** **NMP\_GPRS\_HLR1(1)** + +Process in the HLR to report to the GGSN that an MS is reachable for GPRS + +Signals to/from the left are to/from the GGSN; signals to/from the right are to/from the GPRS application process in the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Note_MS_present_for_GPRS : Note MS present for GPRS + Note_MS_present_for_GPRS --> Send_Requests : MAP_OPEN_req, MAP_NOTE_MS_PRESENT_FOR_GPRS_req, MAP_DELIMITER_req + Send_Requests --> Receive_Open_Cnf : Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_GGSN_Response : OK + Receive_Open_Cnf --> Vr_Error : Vr, Error + Wait_For_GGSN_Response --> MAP_U_ABORT_ind : MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + Wait_For_GGSN_Response --> MAP_NOTICE_ind : MAP_NOTICE_ind + Wait_For_GGSN_Response --> MAP_NOTE_MS_PRESENT_FOR_GPRS_cnf : MAP_NOTE_MS_PRESENT_FOR_GPRS_cnf + MAP_U_ABORT_ind --> Set_Negative_Response : Set negative response: System failure + MAP_NOTICE_ind --> MAP_CLOSE_req : MAP_CLOSE_req + MAP_CLOSE_req --> Set_Negative_Response : Provider Error, Data Error + MAP_CLOSE_req --> Note_MS_present_for_GPRS_ack : OK + MAP_NOTE_MS_PRESENT_FOR_GPRS_cnf --> Check_Confirmation : Check Confirmation + Check_Confirmation --> Set_Negative_Response : User Error + Check_Confirmation --> Note_MS_present_for_GPRS_ack : OK + Set_Negative_Response --> Note_MS_present_for_GPRS_neg : Note MS present for GPRS negative response + Note_MS_present_for_GPRS_neg --> Idle + Note_MS_present_for_GPRS_ack --> Idle + +``` + +State transition diagram for process Note\_MS\_Present\_for\_GPRS\_HLR. The process starts at an Idle state, transitions to 'Note MS present for GPRS', then to a state where it sends MAP\_OPEN\_req, MAP\_NOTE\_MS\_PRESENT\_FOR\_GPRS\_req, and MAP\_DELIMITER\_req. It then receives an Open\_Cnf. If OK, it goes to 'Wait\_For\_GGSN\_Response'. From there, it can receive MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, or MAP\_CLOSE\_ind (leading to a negative response), MAP\_NOTICE\_ind (leading to a close request), or MAP\_NOTE\_MS\_PRESENT\_FOR\_GPRS\_cnf (leading to a confirmation check). A confirmation check can result in a negative response, a provider/data error, a user error, or an OK (leading to an ack and back to Idle). + +4470 + +4471 + +**Figure 24.3/1: Process Note\_MS\_Present\_For\_GPRS\_HLR** + +![State transition diagram for process Note_MS_Present_For_GPRS_GGSN. It starts at Idle, receives an Open indication, and then branches based on OK or Vr, Error. The OK path leads to Wait_For_Service_Indication, which then branches into three paths: MAP_NOTE_MS_PRESENT_FOR_GPRS_ind (leading to Check_Indication and then Note MS present for GPRS), MAP_P_ABORT_ind (leading to Idle), and MAP_NOTICE_ind (leading to MAP_CLOSE_req and then Idle). The Note MS present for GPRS path leads to Wait_For_Application_Response, which branches into Note MS present for GPRS ack (leading to Set Routing info), Note MS present for GPRS negative response (leading to Set User Error), and a combined path for MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind (leading to MAP_CLOSE_req and then Idle). Both Set Routing info and Set User Error lead to a merge point before sending a response. The response is MAP_NOTE_MS_PRESENT_FOR_GPRS_rsp and MAP_CLOSE_req, leading back to Idle. The initial Idle state also has a transition to Idle on Vr, Error.](aa35a318211516e2ee82c0634445520d_img.jpg) + +**process Note\_MS\_Present\_For\_GPRS\_GGSN** **NMP\_GPRS\_GGSN1(1)** + +Process in the GGSN to handle a notification that the MS is reachable for GPRS + +Signals to/from the left are to/from the application process in the GGSN; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_ind + Receive_Open_ind --> Wait_For_Service_Indication: OK + Receive_Open_ind --> Idle: Vr, Error + Wait_For_Service_Indication --> MAP_NOTE_MS_PRESENT_FOR_GPRS_ind + Wait_For_Service_Indication --> MAP_P_ABORT_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + MAP_NOTE_MS_PRESENT_FOR_GPRS_ind --> Check_Indication + Check_Indication --> Note_MS_present_for_GPRS: OK + Check_Indication --> [*]: Error + Note_MS_present_for_GPRS --> Wait_For_Application_Response + Wait_For_Application_Response --> Note_MS_present_for_GPRS_ack + Wait_For_Application_Response --> Note_MS_present_for_GPRS_negative_response + Wait_For_Application_Response --> MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind + Note_MS_present_for_GPRS_ack --> Set_Routing_info + Note_MS_present_for_GPRS_negative_response --> Set_User_Error + Set_Routing_info --> Merge + Set_User_Error --> Merge + Merge --> MAP_NOTE_MS_PRESENT_FOR_GPRS_rsp_MAP_CLOSE_req + MAP_NOTE_MS_PRESENT_FOR_GPRS_rsp_MAP_CLOSE_req --> Idle + MAP_P_ABORT_ind --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + +``` + +State transition diagram for process Note\_MS\_Present\_For\_GPRS\_GGSN. It starts at Idle, receives an Open indication, and then branches based on OK or Vr, Error. The OK path leads to Wait\_For\_Service\_Indication, which then branches into three paths: MAP\_NOTE\_MS\_PRESENT\_FOR\_GPRS\_ind (leading to Check\_Indication and then Note MS present for GPRS), MAP\_P\_ABORT\_ind (leading to Idle), and MAP\_NOTICE\_ind (leading to MAP\_CLOSE\_req and then Idle). The Note MS present for GPRS path leads to Wait\_For\_Application\_Response, which branches into Note MS present for GPRS ack (leading to Set Routing info), Note MS present for GPRS negative response (leading to Set User Error), and a combined path for MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind (leading to MAP\_CLOSE\_req and then Idle). Both Set Routing info and Set User Error lead to a merge point before sending a response. The response is MAP\_NOTE\_MS\_PRESENT\_FOR\_GPRS\_rsp and MAP\_CLOSE\_req, leading back to Idle. The initial Idle state also has a transition to Idle on Vr, Error. + +4472 + +4473 + +Figure 24.3/2: Process Note\_MS\_Present\_For\_GPRS\_GGSN + +--- + +## 4474 24A CSE interrogation and control of subscriber data + +### 4475 24A.1 General + +4476 The MAP procedures for interrogation and control of subscriber data are used to allow the CSE: + +- 4477 - to retrieve subscriber data from the HLR; +- 4478 - to modify subscriber data in the HLR; +- 4479 - to receive notification from the HLR when there is a change in subscriber data; +- 4480 - to request information about the location of a subscriber from the HLR or the GMLC; +- 4481 - to request information about the state of a subscriber from the HLR. + +4482 The following application context refers to a complex MAP user consisting of several processes: + +- 4483 - **anyTimeInfoHandlingContext** + +4484 This application context needs a co-ordinating process in the HLR. + +4485 The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +4486     Receive\_Open\_Ind see clause 25.1.1; + +4487 The Any Time Info Handling Co-ordinator process in the HLR is shown in figure 24A.1/1. + +![State transition diagram for process Co_ATIH_HLR. The process starts at an initial state, goes to 'Null', then receives an 'Open_ind' (referencing Figure 25.1/1). From 'Receive_Open_ind', an 'OK' response leads to 'Wait_For_Service_Primitive', while a 'Vr, Error' leads to another 'Null' state. 'Wait_For_Service_Primitive' branches into four parallel paths: 1) 'MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION_ind' leads to 'ATSI_HLR' and then to another 'MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION_ind' state, which ends at 'Null'. 2) 'MAP_ANY_TIME_MODIFICATION_ind' leads to 'ATM_HLR' and then to another 'MAP_ANY_TIME_MODIFICATION_ind' state, which leads to 'Relay_Info'. 3) 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req', which then leads to 'Null'. 4) 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' leads to a state that also leads to 'Null'. All four paths converge to a 'Relay_Info' state. From 'Relay_Info', the process branches into four more parallel paths: 1) 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' leads to a state that ends at 'Null'. 2) A state with '*' leads to another state with '-' which ends at 'Relay_Info'. 3) A state with 'MAP_U_ABORT_req, MAP_CLOSE_req' leads to a state with '-' which ends at 'Null'. 4) A state with '*' leads to another state with '-' which ends at 'Relay_Info'.](1796f4a3ab45e16480c90d3cfb0d35b2_img.jpg) + +**process Co\_ATIH\_HLR** **Co\_ATIH\_HLR1(1)** + +Co-ordinating process in the HLR + to handle a dialogue opening request + using the application context + anyTimeInfoHandlingContext + +Signals to/from the left + are to/from the gsmSCF; + signals to/from the right + are to/from the child process + +``` + +stateDiagram-v2 + [*] --> Null1[Null] + Null1 --> Receive_Open_ind + Receive_Open_ind --> Null2[Null] : Vr, Error + Receive_Open_ind --> Wait_For_Service_Primitive : OK + Wait_For_Service_Primitive --> MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION_ind1[MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION_ind] + Wait_For_Service_Primitive --> MAP_ANY_TIME_MODIFICATION_ind1[MAP_ANY_TIME_MODIFICATION_ind] + Wait_For_Service_Primitive --> MAP_NOTICE_ind + Wait_For_Service_Primitive --> MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION_ind1 --> ATSI_HLR + ATSI_HLR --> MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION_ind2[MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION_ind] + MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION_ind2 --> Null3[Null] + MAP_ANY_TIME_MODIFICATION_ind1 --> ATM_HLR + ATM_HLR --> MAP_ANY_TIME_MODIFICATION_ind2[MAP_ANY_TIME_MODIFICATION_ind] + MAP_ANY_TIME_MODIFICATION_ind2 --> Relay_Info1[Relay_Info] + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Null4[Null] + MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind --> Null5[Null] + Null3 --> Relay_Info1 + Null4 --> Relay_Info1 + Null5 --> Relay_Info1 + Relay_Info1 --> MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind3[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Relay_Info1 --> Star1[*] + Relay_Info1 --> MAP_U_ABORT_req_MAP_CLOSE_req[MAP_U_ABORT_req, MAP_CLOSE_req] + Relay_Info1 --> Star2[*] + MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind3 --> Dash1[-] + Dash1 --> Null6[Null] + Star1 --> Dash2[-] + Dash2 --> Relay_Info2[Relay_Info] + MAP_U_ABORT_req_MAP_CLOSE_req --> Dash3[-] + Dash3 --> Null7[Null] + Star2 --> Dash4[-] + Dash4 --> Relay_Info3[Relay_Info] + +``` + +State transition diagram for process Co\_ATIH\_HLR. The process starts at an initial state, goes to 'Null', then receives an 'Open\_ind' (referencing Figure 25.1/1). From 'Receive\_Open\_ind', an 'OK' response leads to 'Wait\_For\_Service\_Primitive', while a 'Vr, Error' leads to another 'Null' state. 'Wait\_For\_Service\_Primitive' branches into four parallel paths: 1) 'MAP\_ANY\_TIME\_SUBSCRIPTION\_INTERROGATION\_ind' leads to 'ATSI\_HLR' and then to another 'MAP\_ANY\_TIME\_SUBSCRIPTION\_INTERROGATION\_ind' state, which ends at 'Null'. 2) 'MAP\_ANY\_TIME\_MODIFICATION\_ind' leads to 'ATM\_HLR' and then to another 'MAP\_ANY\_TIME\_MODIFICATION\_ind' state, which leads to 'Relay\_Info'. 3) 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req', which then leads to 'Null'. 4) 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' leads to a state that also leads to 'Null'. All four paths converge to a 'Relay\_Info' state. From 'Relay\_Info', the process branches into four more parallel paths: 1) 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' leads to a state that ends at 'Null'. 2) A state with '\*' leads to another state with '-' which ends at 'Relay\_Info'. 3) A state with 'MAP\_U\_ABORT\_req, MAP\_CLOSE\_req' leads to a state with '-' which ends at 'Null'. 4) A state with '\*' leads to another state with '-' which ends at 'Relay\_Info'. + +4488 + +4489 + +Figure 24A.1/1: Process Co\_ATIH\_HLR + +## 24A.2 Any Time Subscription Interrogation procedure + +### 24A.2.1 General + +The message flow for successful retrieval of subscription information related to an any time subscription interrogation from the CAMEL server are shown in figure 24A.1/1. In an IP Multimedia Core Network, an IM-SSF can take on the role of a gsmSCF for this procedure (see 3GPP TS 23.278 [125]). + +![Sequence diagram showing the message flow for any time subscription interrogation between gsmSCF and HLR.](43cfb9718d89aae4f22d31e2cdc704f1_img.jpg) + +``` +sequenceDiagram + participant gsmSCF + participant HLR + Note right of gsmSCF: MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION + gsmSCF->>HLR: MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION + Note left of HLR: MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION ack + HLR-->>gsmSCF: MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION ack +``` + +The diagram illustrates a sequence of messages between a gsmSCF and an HLR. The gsmSCF sends a 'MAP\_ANY\_TIME\_SUBSCRIPTION\_INTERROGATION' message to the HLR, and the HLR responds with a 'MAP\_ANY\_TIME\_SUBSCRIPTION\_INTERROGATION ack' message. The messages are shown in rectangular boxes with arrows indicating the direction of the flow. + +Sequence diagram showing the message flow for any time subscription interrogation between gsmSCF and HLR. + +4495 + +4496 **Figure 24A.2/1: Message flow for any time subscription interrogation** + +4497 The following MAP service is used to retrieve requested information: + +4498 `MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION` see clause 8.11.3. + +### 24A.2.2 Process in the gsmSCF + +The MAP process in the gsmSCF to obtain subscription information in response to a request from the application process in the gsmSCF is shown in figure 24A.2/2. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +4503 `Receive_Open_Cnf` see clause 25.1.2; + +4504 `Check_Confirmation` see clause 25.2.2 + +### 24A.2.3 Process in the HLR + +The MAP process in the HLR to provide subscription information in response to an interrogation from the CAMEL server is shown in figure 24A.2/3. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: + +4509 `Check_Indication` see clause 25.2.2 + +If the `MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION` service response cannot be carried in a single TC-Result component, it is carried in one or more TC-Result-NL components (each sent in a TC-CONTINUE), followed by a TC-Result-L component in a TC-END message. + +![State transition diagram for process ATSI_gsmSCF. It starts at an initial state, goes to Idle, then handles a subscription request by sending MAP_OPEN_req and waiting for a response. From the response, it branches based on OK, Vr, Error, MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION_cnf, MAP_NOTICE_ind, or MAP_P_ABORT_ind/MAP_U_ABORT_ind/MAP_CLOSE_ind. Each branch leads to either a final Idle state, a negative response, or a system failure state.](69a9920131a220478b8197986108a334_img.jpg) + +**process ATSI\_gsmSCF** **ATSI\_SCF1(1)** + +Process in the gsmSCF to retrieve subscription information from the HLR + +Signals to/from the left are to/from the application process in the gsmSCF; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> Request{Any time subscription interrogation request} + Request --> SendReq[MAP_OPEN_req, MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION_req, MAP_DELIMITER_req] + SendReq --> ReceiveCnf[Receive_Open_Cnf] + ReceiveCnf --> WaitForResponse[Wait_For_HLR_Response] + WaitForResponse --> OK + WaitForResponse --> VrError((1)) + WaitForResponse --> Cnf{MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION_cnf} + WaitForResponse --> Notice{MAP_NOTICE_ind} + WaitForResponse --> AbortClose{MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind} + Cnf --> CheckConfirmation[Check Confirmation] + CheckConfirmation --> OK2[OK] + CheckConfirmation --> UserError[User Error] + CheckConfirmation --> ProviderError[Provider Error, Data Error] + OK2 --> Ack{Any time subscription interrogation ack} + Ack --> Idle2[Idle] + UserError --> NegativeResponse1{Any time subscription interrogation negative response} + NegativeResponse1 --> Idle3[Idle] + ProviderError --> VrError2((1)) + Notice --> CloseReq[MAP_CLOSE_req] + CloseReq --> AbortClose + AbortClose --> SetNegativeResponse[Set negative response: System failure] + SetNegativeResponse --> NegativeResponse2{Any time subscription interrogation negative response} + NegativeResponse2 --> Idle4[Idle] + +``` + +State transition diagram for process ATSI\_gsmSCF. It starts at an initial state, goes to Idle, then handles a subscription request by sending MAP\_OPEN\_req and waiting for a response. From the response, it branches based on OK, Vr, Error, MAP\_ANY\_TIME\_SUBSCRIPTION\_INTERROGATION\_cnf, MAP\_NOTICE\_ind, or MAP\_P\_ABORT\_ind/MAP\_U\_ABORT\_ind/MAP\_CLOSE\_ind. Each branch leads to either a final Idle state, a negative response, or a system failure state. + +4513 + +4514 + +Figure 24A.2/2: Process ATSI\_gsmSCF + +![State transition diagram for process ATSI_HLR. The process starts at an initial state, waits for a service indication, receives a MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION_ind, checks the indication, and then either sends a request or an error. It then waits for an application response and handles it based on whether it's an ack, error, or other indication.](3375413f96777e748d6bb7381255b459_img.jpg) + +**process ATSI\_HLR** **ATSI\_HLR1(1)** + +Process in the HLR to handle a request from the gsmSCF for subscription information + +Signals to/from the left are to/from the gsmSCF; signals to/from the right are to/from the subscriber data management application in the HLR + +``` + +stateDiagram-v2 + [*] --> Wait_For_Service_Indication + state "Wait_For_Service_Indication" as Wait_For_Service_Indication + state "Check_Indication" as Check_Indication + state "Any Time Subscription Interrogation request" as Any_Time_Subscription_Interrogation_request + state "Error" as Error + state "Wait_For_Application_Response" as Wait_For_Application_Response + state "Set result" as Set_result + state "Set User Error" as Set_User_Error + state "MAP_CLOSE_req" as MAP_CLOSE_req + + Wait_For_Service_Indication --> Check_Indication + Check_Indication --> Any_Time_Subscription_Interrogation_request : OK + Check_Indication --> Error : Error + Error --> [*] + Any_Time_Subscription_Interrogation_request --> Wait_For_Application_Response + Wait_For_Application_Response --> Set_result + Wait_For_Application_Response --> Set_User_Error + Wait_For_Application_Response --> MAP_CLOSE_req + Set_result --> [*] + Set_User_Error --> [*] + MAP_CLOSE_req --> [*] + +``` + +The diagram illustrates the state transitions for the **ATSI\_HLR** process. It begins at an initial state, transitioning to **Wait\_For\_Service\_Indication**. From there, it moves to **Check\_Indication**. A transition labeled **OK** leads to **Any Time Subscription Interrogation request**, while an **Error** transition leads to an error state marked with a circle containing '1'. The process then enters **Wait\_For\_Application\_Response**. From this state, three transitions are possible: **Set result**, **Set User Error**, and **MAP\_CLOSE\_req**. Both **Set result** and **Set User Error** lead to the final state (marked with an 'X'), while **MAP\_CLOSE\_req** also leads to the final state. A note indicates that signals to/from the left are to/from the gsmSCF, and signals to/from the right are to/from the subscriber data management application in the HLR. + +State transition diagram for process ATSI\_HLR. The process starts at an initial state, waits for a service indication, receives a MAP\_ANY\_TIME\_SUBSCRIPTION\_INTERROGATION\_ind, checks the indication, and then either sends a request or an error. It then waits for an application response and handles it based on whether it's an ack, error, or other indication. + +4515 + +4516 + +Figure 24A.2/3: Process ATSI\_HLR + +## 24A.3 Any Time Modification procedure + +### 24A.3.1 General + +The message flow for successful modification of subscription information related to an any time modification request from the CAMEL server is shown in figure 24A.3/1 + +![Sequence diagram showing the message flow for any time modification between gsmSCF and HLR. The gsmSCF sends a MAP_ANY_TIME_MODIFICATION message to the HLR, and the HLR responds with a MAP_ANY_TIME_MODIFICATION ack.](141512f04b9aa27a5291824b4ae7c2d8_img.jpg) + +``` +sequenceDiagram + participant gsmSCF + participant HLR + Note right of gsmSCF: MAP_ANY_TIME_MODIFICATION + gsmSCF->>HLR: MAP_ANY_TIME_MODIFICATION + Note left of HLR: MAP_ANY_TIME_MODIFICATION ack + HLR-->>gsmSCF: MAP_ANY_TIME_MODIFICATION ack +``` + +Sequence diagram showing the message flow for any time modification between gsmSCF and HLR. The gsmSCF sends a MAP\_ANY\_TIME\_MODIFICATION message to the HLR, and the HLR responds with a MAP\_ANY\_TIME\_MODIFICATION ack. + +4521 + +4522 + +**Figure 24A.3/1: Message flow for any time modification** + +The following MAP service is used to modify subscription information: + +MAP\_ANY\_TIME\_MODIFICATION see clause 8.11.4. + +### 24A.3.2 Process in the gsmSCF + +The MAP process in the gsmSCF to modify subscription information in response to a request from the application process in the gsmSCF is shown in figure 24A.3/2. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +Receive\_Open\_Cnf see clause 25.1.2; + +Check\_Confirmation see clause 25.2.2 + +### 24A.3.3 Process in the HLR + +The MAP process in the HLR to modify subscriber information in response to a modification request from the CAMEL server is shown in figure 24A.3/3. The MAP process invokes a macro and a process not defined in this clause; the definitions of these can be found as follows: + +Check\_Indication see clause 25.2.2; + +Insert\_Subs\_Data\_Stand\_Alone\_HLR see clause 25.7.3; + +If the macro takes the OK exit, the MAP process waits for a service indication. + +If the MAP\_ANY\_TIME\_MODIFICATION service response cannot be carried in a single TC-Result component, it is carried in one or more TC-Result-NL components (each sent in a TC-CONTINUE), followed by a TC-Result-L component in a TC-END message. + +If the serving node (VLR or SGSN) is to be updated after the modification, the MAP process creates an instance of the appropriate process (Insert\_Subs\_Data\_Stand\_Alone\_HLR for VLR update, Insert\_GPRS\_Subs\_Data\_Stand\_Alone\_HLR for SGSN update). + +![State transition diagram for process ATM_gsmSCF. The process starts at an initial state, goes to Idle, then receives an 'Any time modification request'. It sends MAP_OPEN_req, MAP_ANY_TIME_MODIFICATION_req, and MAP_DELIMITER_req to the HLR. It receives an Open_Cnf. If OK, it waits for an HLR response. If Vr, Error, it goes to connector 1. From 'Wait For_HLR_Response', it branches: 1) MAP_ANY_TIME_MODIFICATION_cnf to application, then Check Confirmation. If OK, it sends 'Any time modification ack' to application and returns to Idle. If User Error, it sends 'Any time modification negative response' to application and returns to Idle. If Provider Error, Data Error, it goes to connector 1. 2) MAP_NOTICE_ind to HLR, then MAP_CLOSE_req to HLR. 3) MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind to application. A merge point for connectors 1 and MAP_CLOSE_req leads to 'Set negative response: System failure', which then sends 'Any time modification negative response' to application and returns to Idle.](ac78f53876459c8656e94fd118f9603a_img.jpg) + +**process ATM\_gsmSCF** **ATM\_SCF1(1)** + +Process in the gsmSCF to modify subscription information in the HLR + +Signals to/from the left are to/from the application process in the gsmSCF; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Any_time_modification_request {Any time modification request} + Any_time_modification_request --> Outgoing {MAP_OPEN_req, MAP_ANY_TIME_MODIFICATION_req, MAP_DELIMITER_req} + Outgoing --> Receive_Open_Cnf {Receive_Open_Cnf} + Receive_Open_Cnf --> Wait_For_HLR_Response {Wait For_HLR_Response} + Wait_For_HLR_Response --> MAP_ANY_TIME_MODIFICATION_cnf {MAP_ANY_TIME_MODIFICATION_cnf} + Wait_For_HLR_Response --> MAP_NOTICE_ind {MAP_NOTICE_ind} + Wait_For_HLR_Response --> MAP_P_ABORT_ind {MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind} + Wait_For_HLR_Response --> Vr_Error {Vr, Error} --> 1 + MAP_ANY_TIME_MODIFICATION_cnf --> Check Confirmation {Check Confirmation} + Check Confirmation --> OK_1 {OK} + Check Confirmation --> User_Error {User Error} + Check Confirmation --> Provider_Error {Provider Error, Data Error} --> 1 + OK_1 --> Any_time_modification_ack {Any time modification ack} + Any_time_modification_ack --> Idle_1 {Idle} + User_Error --> Any_time_modification_negative_response_1 {Any time modification negative response} + Any_time_modification_negative_response_1 --> Idle_2 {Idle} + MAP_NOTICE_ind --> MAP_CLOSE_req {MAP_CLOSE_req} + MAP_P_ABORT_ind --> Merge {Merge} + MAP_CLOSE_req --> Merge + Merge --> Set_negative_response {Set negative response: System failure} + Set_negative_response --> Any_time_modification_negative_response_2 {Any time modification negative response} + Any_time_modification_negative_response_2 --> Idle_3 {Idle} + +``` + +State transition diagram for process ATM\_gsmSCF. The process starts at an initial state, goes to Idle, then receives an 'Any time modification request'. It sends MAP\_OPEN\_req, MAP\_ANY\_TIME\_MODIFICATION\_req, and MAP\_DELIMITER\_req to the HLR. It receives an Open\_Cnf. If OK, it waits for an HLR response. If Vr, Error, it goes to connector 1. From 'Wait For\_HLR\_Response', it branches: 1) MAP\_ANY\_TIME\_MODIFICATION\_cnf to application, then Check Confirmation. If OK, it sends 'Any time modification ack' to application and returns to Idle. If User Error, it sends 'Any time modification negative response' to application and returns to Idle. If Provider Error, Data Error, it goes to connector 1. 2) MAP\_NOTICE\_ind to HLR, then MAP\_CLOSE\_req to HLR. 3) MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind to application. A merge point for connectors 1 and MAP\_CLOSE\_req leads to 'Set negative response: System failure', which then sends 'Any time modification negative response' to application and returns to Idle. + +4544 + +4545 + +Figure 24A.3/2: Process ATM\_gsmSCF + +![Flowchart for process ATM_HLR. The process starts with an initial node, followed by 'Wait_For_Service_Indication'. It then receives 'MAP_ANY_TIME_MODIFICATION_ind' from the right. A 'Check_Indication' block follows, with 'OK' leading to 'Any Time Modification request' and 'Error' leading to connector '1'. The request leads to 'Wait_For_Application_Response'. From there, four paths emerge: 1) 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' leading to an exit; 2) 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req' and then an exit; 3) 'Any Time Modification ack' leading to 'Set result'; 4) 'Any Time Modification error' leading to 'Set User Error'. Both 'Set result' and 'Set User Error' lead to a merge point. From the merge point, 'MAP_ANY_TIME_MODIFICATION_rsp' and 'MAP_CLOSE_req' are sent to the right. A decision 'VLR/SGSN update required?' follows. If 'No', it leads to an exit. If 'Yes', it leads to 'Insert Subs_Data Stand_Alone_HLR', which is associated with a note 'Insert_GPRS_Subs_Data_Stand_Alone_HLR for SGSN update'. This path then leads to an exit.](ec494612ff3d129d88e4e3acb82e1d1e_img.jpg) + +**process ATM\_HLR** **ATM\_HLR1(1)** + +Process in the HLR to handle a request from the gsmSCF to modify subscription information + +Signals to/from the left are to/from the gsmSCF; signals to/from the right are to/from the subscriber data management application in the HLR + +``` + +graph TD + Start([ ]) --> WaitService[Wait_For_Service_Indication] + WaitService --> In1{{ }} + In1 -- "MAP_ANY_TIME_MODIFICATION_ind" --> Check[Check_Indication] + Check -- OK --> Request{Any Time Modification request} + Check -- Error --> C1((1)) + Request --> WaitApp[Wait_For_Application_Response] + WaitApp --> In2{{ }} + In2 -- "MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind" --> Exit1[ ] + In2 -- "MAP_NOTICE_ind" --> CloseReq1{MAP_CLOSE_req} --> Exit2[ ] + In2 -- "Any Time Modification ack" --> SetResult[Set result] + In2 -- "Any Time Modification error" --> SetUserError[Set User Error] + SetResult --> Merge{{ }} + SetUserError --> Merge + Merge -- "MAP_ANY_TIME_MODIFICATION_rsp +MAP_CLOSE_req" --> In3{{ }} + In3 --> Decision{VLR/SGSN update required?} + Decision -- No --> Exit3[ ] + Decision -- Yes --> Insert[Insert Subs_Data Stand_Alone_HLR] + Insert -.-> Note["Insert_GPRS_Subs_Data_Stand_Alone_HLR for SGSN update"] + Insert --> Exit4[ ] + +``` + +Flowchart for process ATM\_HLR. The process starts with an initial node, followed by 'Wait\_For\_Service\_Indication'. It then receives 'MAP\_ANY\_TIME\_MODIFICATION\_ind' from the right. A 'Check\_Indication' block follows, with 'OK' leading to 'Any Time Modification request' and 'Error' leading to connector '1'. The request leads to 'Wait\_For\_Application\_Response'. From there, four paths emerge: 1) 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' leading to an exit; 2) 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req' and then an exit; 3) 'Any Time Modification ack' leading to 'Set result'; 4) 'Any Time Modification error' leading to 'Set User Error'. Both 'Set result' and 'Set User Error' lead to a merge point. From the merge point, 'MAP\_ANY\_TIME\_MODIFICATION\_rsp' and 'MAP\_CLOSE\_req' are sent to the right. A decision 'VLR/SGSN update required?' follows. If 'No', it leads to an exit. If 'Yes', it leads to 'Insert Subs\_Data Stand\_Alone\_HLR', which is associated with a note 'Insert\_GPRS\_Subs\_Data\_Stand\_Alone\_HLR for SGSN update'. This path then leads to an exit. + +4546 + +4547 + +Figure 24A.3/3: Process ATM\_HLR + +## 24A.4 Subscriber Data Modification Notification procedure + +### 24A.4.1 General + +The Subscriber Data Modification Notification procedure is used to notify a gsmSCF about the modification of subscriber data. In an IP Multimedia Core Network, an IM-SSF can take on the role of a gsmSCF for this procedure. + +The stage 2 specification for Subscriber Data Modification Notification is in 3GPP TS 23.078 [98] and 3GPP TS 23.278 [125]. The interworking between the MAP signalling procedures and the Subscriber Data Modification Notification procedures for each entity (HLR, gsmSCF) is shown by the transfer of signals between these processes. + +The following services are used: + +![Sequence diagram showing message flow between HLR and gsmSCF for subscriber data modification notification.](5446756274ab50ff60d829395bd1136e_img.jpg) + +``` +sequenceDiagram + participant HLR + participant gsmSCF + Note right of HLR: MAP_NOTE_SUBSCRIBER_DATA_MODIFIED + HLR->>gsmSCF: MAP_NOTE_SUBSCRIBER_DATA_MODIFIED + Note left of gsmSCF: MAP_NOTE_SUBSCRIBER_DATA_MODIFIED ack + gsmSCF->>HLR: MAP_NOTE_SUBSCRIBER_DATA_MODIFIED ack +``` + +Sequence diagram showing message flow between HLR and gsmSCF for subscriber data modification notification. + +4556 + +4557 + +**Figure 24A.4/1: Message flow for subscriber data modification notification** + +The following MAP service is used to send the notification to the gsmSCF: + +MAP\_NOTE\_SUBSCRIBER\_DATA\_MODIFIED see clause 8.11.5. + +### 24A.4.2 Process in the HLR + +The MAP process in the HLR to send modified data to the gsmSCF is shown in figure 24A.4/2. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +Receive\_Open\_Cnf see clause 25.1.2; + +Check\_Confirmation see clause 25.2.2. + +If the required information cannot be carried in a single MAP\_NOTE\_SUBSCRIBER\_DATA\_MODIFIED service request, the HLR segments the information into two or more requests. The "All Information Sent" parameter is omitted from each request except the last. + +Sheet 2: If the MAP\_NOTE\_SUBSCRIBER\_DATA\_MODIFIED service request contained the "All Information Sent" parameter, the test "All information sent" takes the "Yes" exit. + +### 24A.4.3 Process in the gsmSCF + +The MAP process in the gsmSCF to handle a notification to the gsmSCF of change of subscriber data is shown in figure 24A.4/3. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +Receive\_Open\_Ind see clause 25.1.1; + +Check\_Indication see clause 25.2.1 + +4576 If the MAP\_NOTE\_SUBSCRIBER\_DATA\_MODIFIED service indication contained the "All Information Sent" +4577 parameter, the test "All information sent" takes the "Yes" exit. + +4578 If the test "All information sent" takes the "No" exit, the MAP process stores the data received in the +4579 MAP\_NOTE\_SUBSCRIBER\_DATA\_MODIFIED service indication. If the test "All information sent" takes the "Yes" +4580 exit, the MAP process assembles the data received in all the MAP\_NOTE\_SUBSCRIBER\_DATA\_MODIFIED service +4581 indications received in the dialogue and sends the assembled data to the application process in the gsmSCF. + +![Flowchart for process NSDC_HLR. It starts at an initial state, goes to Idle, then Notify Subscriber Data change. A decision diamond asks 'Segmentation required?'. If Yes, it goes to 'Set: All Information Sent'. If No, it goes to a merge point. Both paths lead to a process block with MAP_OPEN_req, MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_req, and MAP_DELIMITER_req. This is followed by 'Receive_Open_Cnf'. From there, an 'OK' path leads to 'Wait_For_gsmSCF_Response' and a 'Vr, Error' path leads to 'Set negative response: System failure', which then leads to 'Notify Subscriber Data Change negative response' and finally 'Idle'.](0a2bc9e00f84ccec4da49716d4a590ee_img.jpg) + +process NSDC\_HLR + +NSDC\_HLR1(2) + +Process in the HLR to notify the gsmSCF that subscriber data have changed + +Signals to/from the left are to/from the application process in the HLR (see 3GPP TS 23.078 or 3GPP TS 23.278); + Signals to/from the right are to/from the gsmSCF + +``` + +graph TD + Start([ ]) --> Idle1([Idle]) + Idle1 --> Notify[Notify Subscriber Data change] + Notify --> Decision{Segmentation required?} + Decision -- Yes --> Set[Set: All Information Sent] + Decision -- No --> Merge(( )) + Set --> Merge + Merge --> MAP[MAP_OPEN_req +MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_req +MAP_DELIMITER_req] + MAP --> Receive[Receive_Open_Cnf] + Receive -- OK --> Wait[Wait_For_gsmSCF_Response] + Receive -- Vr, Error --> SetNeg[Set negative response: System failure] + SetNeg --> Merge2(( )) + Merge2 --> NotifyNeg[Notify Subscriber Data Change negative response] + NotifyNeg --> Idle2([Idle]) + +``` + +Flowchart for process NSDC\_HLR. It starts at an initial state, goes to Idle, then Notify Subscriber Data change. A decision diamond asks 'Segmentation required?'. If Yes, it goes to 'Set: All Information Sent'. If No, it goes to a merge point. Both paths lead to a process block with MAP\_OPEN\_req, MAP\_NOTE\_SUBSCRIBER\_DATA\_MODIFIED\_req, and MAP\_DELIMITER\_req. This is followed by 'Receive\_Open\_Cnf'. From there, an 'OK' path leads to 'Wait\_For\_gsmSCF\_Response' and a 'Vr, Error' path leads to 'Set negative response: System failure', which then leads to 'Notify Subscriber Data Change negative response' and finally 'Idle'. + +4582 + +4583 + +Figure 24A.4/2 (sheet 1 of 2): Process NSDC\_HLR + +![Flowchart for process NSDC_HLR. It starts with 'Wait_For_gsmSCF_Response' leading to a merge point. From the merge point, one path goes left through 'MAP_NOTICE_ind' to 'MAP_CLOSE_req' to a merge point, then to 'Notify Subscriber Data Change negative response' and finally 'Idle'. The other path from the merge point goes right through 'MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_cnf' to 'Check_Confirmation'. 'Check_Confirmation' has an 'OK' path leading to a decision 'All information sent?'. If 'Yes', it goes to a merge point, then to 'Notify Subscriber Data Change response' and finally 'Idle'. If 'No', it goes to another decision 'Segmentation required?'. If 'Yes', it goes to a merge point. If 'No', it goes to 'Set: All Information Sent', then to a merge point. From this merge point, it goes right through 'MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_req' and 'MAP_DELIMITER_req' to 'Wait_For_gsmSCF_Response'. A 'User Error, Provider Error, Data Error' path from the first merge point leads to the second merge point. A box with 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind' is also connected to the first merge point.](091179da3e4866bfb1d00c8f9e1963f4_img.jpg) + +**process NSDC\_HLR** **NSDC\_HLR2(2)** + +Process in the HLR to notify the gsmSCF that subscriber data have changed + +Signals to/from the left are to/from the application process in the HLR (see 3GPP TS 23.078 or 3GPP TS 23.278); + Signals to/from the right are to/from the gsmSCF + +``` + + graph TD + W1([Wait_For_gsmSCF_Response]) --> M1(( )) + M1 --> N1[MAP_NOTICE_ind] + N1 --> C1[MAP_CLOSE_req] + C1 --> M2(( )) + M2 --> N2[Notify Subscriber Data Change negative response] + N2 --> I1([Idle]) + + M1 --> E[User Error, Provider Error, Data Error] + + M1 --> N3[MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_cnf] + N3 --> C2[Check_Confirmation] + + C2 -- OK --> D1{All information sent?} + + D1 -- Yes --> M3(( )) + M3 --> N4[Notify Subscriber Data Change response] + N4 --> I2([Idle]) + + D1 -- No --> D2{Segmentation required?} + + D2 -- Yes --> M3 + + D2 -- No --> S[Set: All Information Sent] + + S --> M3 + + M3 --> N5[MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_req +MAP_DELIMITER_req] + + N5 --> W2([Wait_For_gsmSCF_Response]) + + M1 --> A[MAP_P_ABORT_ind, +MAP_U_ABORT_ind, +MAP_CLOSE_ind] + +``` + +Flowchart for process NSDC\_HLR. It starts with 'Wait\_For\_gsmSCF\_Response' leading to a merge point. From the merge point, one path goes left through 'MAP\_NOTICE\_ind' to 'MAP\_CLOSE\_req' to a merge point, then to 'Notify Subscriber Data Change negative response' and finally 'Idle'. The other path from the merge point goes right through 'MAP\_NOTE\_SUBSCRIBER\_DATA\_MODIFIED\_cnf' to 'Check\_Confirmation'. 'Check\_Confirmation' has an 'OK' path leading to a decision 'All information sent?'. If 'Yes', it goes to a merge point, then to 'Notify Subscriber Data Change response' and finally 'Idle'. If 'No', it goes to another decision 'Segmentation required?'. If 'Yes', it goes to a merge point. If 'No', it goes to 'Set: All Information Sent', then to a merge point. From this merge point, it goes right through 'MAP\_NOTE\_SUBSCRIBER\_DATA\_MODIFIED\_req' and 'MAP\_DELIMITER\_req' to 'Wait\_For\_gsmSCF\_Response'. A 'User Error, Provider Error, Data Error' path from the first merge point leads to the second merge point. A box with 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind' is also connected to the first merge point. + +4584 + +4585 + +Figure 24A.4/2 (sheet 2 of 2): Process NSDC\_HLR + +![State transition diagram for process NSDC_gsmSCF. The process starts at an initial state, goes to Idle, then receives an Open indication. If OK, it waits for a service indication. From there, it can send MAP_NOTICE_ind, MAP_P_ABORT_ind, or MAP_CLOSE_req to the HLR (left), or receive a MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_ind from the HLR (right). It then checks the indication. If OK, it checks if all information is sent. If No, it stores received data and sends a response to the application (right) and waits for another service indication. If Yes, it assembles received data, notifies the subscriber data change to the application (right), and waits for an application response. Upon receiving a response, it sends a notification to the HLR (left) and returns to Idle. If an error occurs at any point, it returns to Idle.](665e93f3a2eb6c3ccbbb391fc666a77d_img.jpg) + +**process NSDC\_gsmSCF** **NSDC\_SCF1(1)** + +Process in the gsmSCF to handle a notification of change of subscriber data + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the application process in the gsmSCF + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_ind + Receive_Open_ind --> Wait_For_Service_Indication: OK + Receive_Open_ind --> Idle: Vr, Error + Wait_For_Service_Indication --> MAP_NOTICE_ind + Wait_For_Service_Indication --> MAP_P_ABORT_ind + Wait_For_Service_Indication --> MAP_CLOSE_req + Wait_For_Service_Indication --> MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_ind + MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_ind --> Check_Indication + Check_Indication --> Decision1{All information sent?} + Decision1 --> Store_received_data: No + Decision1 --> Assemble_received_data: Yes + Store_received_data --> MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_rsp + MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_rsp --> Wait_For_Service_Indication + Assemble_received_data --> Notify_Subscriber_Data_Change + Notify_Subscriber_Data_Change --> Wait_For_Application_Response + Wait_For_Application_Response --> Notify_Subscriber_Data_Change_neg_response + Notify_Subscriber_Data_Change_neg_response --> Set_User_Error + Set_User_Error --> MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_rsp + MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_rsp --> Idle + MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_rsp --> MAP_P_ABORT_ind + MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_rsp --> MAP_U_ABORT_ind + MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_rsp --> MAP_CLOSE_ind + MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_rsp --> MAP_CLOSE_req + MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_rsp --> Idle + Check_Indication --> Error + Error --> Idle + MAP_CLOSE_req --> Idle + MAP_P_ABORT_ind --> Idle + MAP_NOTICE_ind --> Idle + +``` + +State transition diagram for process NSDC\_gsmSCF. The process starts at an initial state, goes to Idle, then receives an Open indication. If OK, it waits for a service indication. From there, it can send MAP\_NOTICE\_ind, MAP\_P\_ABORT\_ind, or MAP\_CLOSE\_req to the HLR (left), or receive a MAP\_NOTE\_SUBSCRIBER\_DATA\_MODIFIED\_ind from the HLR (right). It then checks the indication. If OK, it checks if all information is sent. If No, it stores received data and sends a response to the application (right) and waits for another service indication. If Yes, it assembles received data, notifies the subscriber data change to the application (right), and waits for an application response. Upon receiving a response, it sends a notification to the HLR (left) and returns to Idle. If an error occurs at any point, it returns to Idle. + +4586 + +4587 + +Figure 24A.4/3: Process NSDC\_gsmSCF + +4588 **24A.5 Any Time Interrogation procedure** + +4589 **24A.5.1 General** + +4590 The message flows for successful retrieval of subscriber information related to an any time interrogation from the +4591 CAMEL server are shown in figure 24A.5/1 for interrogation directed to an HLR and figure 24A.5/2 for interrogation +4592 directed to a GMLC. + +![Sequence diagram for Figure 24A.5/1: Message flow for any time interrogation (gsmSCF to HLR). The diagram shows four numbered message exchanges between gsmSCF, HLR, and SGSN or VLR. 1) gsmSCF to HLR, 2) HLR to SGSN or VLR, 3) SGSN or VLR to HLR, 4) HLR to gsmSCF.](6ccb75cb5c1d05ca2da85a5d10dfbd0c_img.jpg) + +``` +sequenceDiagram + participant gsmSCF + participant HLR + participant SGSN or VLR + Note right of gsmSCF: 1 + gsmSCF->>HLR: + Note right of HLR: 2 + HLR->>SGSN or VLR: + Note right of SGSN or VLR: 3 + SGSN or VLR->>HLR: + Note right of HLR: 4 + HLR->>gsmSCF: +``` + +Sequence diagram for Figure 24A.5/1: Message flow for any time interrogation (gsmSCF to HLR). The diagram shows four numbered message exchanges between gsmSCF, HLR, and SGSN or VLR. 1) gsmSCF to HLR, 2) HLR to SGSN or VLR, 3) SGSN or VLR to HLR, 4) HLR to gsmSCF. + +4593 + +4594 + +- 4595 1) MAP\_ANY\_TIME\_INTERROGATION\_req/ind +- 4596 2) MAP\_PROVIDE\_SUBSCRIBER\_INFO\_req/ind +- 4597 3) MAP\_PROVIDE\_SUBSCRIBER\_INFO\_rsp/cnf +- 4598 4) MAP\_ANY\_TIME\_INTERROGATION\_rsp/cnf + +4599 + +4600 + +**Figure 24A.5/1: Message flow for any time interrogation (gsmSCF to HLR)** + +4601 The following MAP services are used to retrieve information about the status and/or location of a subscriber: + +4602 MAP\_ANY\_TIME\_INTERROGATION see clause 8.11.1; + +4603 MAP\_PROVIDE\_SUBSCRIBER\_INFO see clause 8.11.2. + +4604 The HLR sends the MAP\_PROVIDE\_SUBSCRIBER\_INFO request to the SGSN or the VLR, according to the domain +4605 for which the gsmSCF requested the information. + +![Sequence diagram for Figure 24A.5/2: Message flow for any time interrogation (gsmSCF to GMLC). The diagram shows two numbered message exchanges between gsmSCF and GMLC. 1) gsmSCF to GMLC, 2) GMLC to gsmSCF.](98eb542ec579cfbf15c8cf7659ae79d0_img.jpg) + +``` +sequenceDiagram + participant gsmSCF + participant GMLC + Note right of GMLC: 1 + gsmSCF->>GMLC: + Note right of gsmSCF: 2 + GMLC->>gsmSCF: +``` + +Sequence diagram for Figure 24A.5/2: Message flow for any time interrogation (gsmSCF to GMLC). The diagram shows two numbered message exchanges between gsmSCF and GMLC. 1) gsmSCF to GMLC, 2) GMLC to gsmSCF. + +4606 + +4607 + +- 4608 1) MAP\_ANY\_TIME\_INTERROGATION\_req/ind +- 4609 2) MAP\_ANY\_TIME\_INTERROGATION\_rsp/cnf + +4610 + +4611 + +**Figure 24A.5/2: Message flow for any time interrogation (gsmSCF to GMLC)** + +4612 The following MAP service is used to retrieve location information from a GMLC: + +4613 MAP\_ANY\_TIME\_INTERROGATION see clause 8.11.1; + +4614 In addition, the GMLC may use MAP Services specific to Location Services. + +## 4615 24A.5.2 Procedures in the gsmSCF + +4616 The process in the gsmSCF to request information about the location and/or state of a subscriber from the HLR is +4617 shown in figure 24A.5/3. The MAP process invokes macros not defined in this clause; the definitions of these macros +4618 can be found as follows: + +4619     Receive\_Open\_Cnf see clause 25.1.2; + +4620     Check\_Confirmation see clause 25.2.2. + +4621 The process in the gsmSCF to request location information from the GMLC is shown in figure 24A.5/4. The MAP +4622 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +4623     Receive\_Open\_Cnf see clause 25.1.2; + +4624     Check\_Confirmation see clause 25.2.2. + +## 4625 24A.5.3 Procedure in the HLR + +4626 The MAP process in the HLR to provide subscriber information in response to an interrogation from the CAMEL server +4627 is shown in figure 24A.5/5. The MAP process invokes macros not defined in this clause; the definitions of these macros +4628 can be found as follows: + +4629     Receive\_Open\_Ind see clause 25.1.1; + +4630     Receive\_Open\_Cnf see clause 25.1.2; + +4631     Check\_Confirmation see clause 25.2.2. + +## 4632 24A.5.4 Procedure in the GMLC + +4633 The MAP process in the GMLC to provide location information in response to a request from the gsmSCF is shown in +4634 figure 24A.5/6. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found +4635 as follows: + +4636     Receive\_Open\_Ind see clause 25.1.1. + +![State transition diagram for process ATI_To_HLR_gsmSCF. The process starts at an initial state, goes to Idle, then Any Time Interrogation. It sends MAP_OPEN_req, MAP_ANY_TIME_INTERROGATION_req, and MAP_DELIMITER_req to the HLR. It receives Open_Cnf from the HLR. If OK, it goes to Wait_For_HLR_Response. If Vr, Error, it goes to Abort. From Wait_For_HLR_Response, it can receive MAP_ANY_TIME_INTERROGATION_cnf, MAP_NOTICE_ind, or MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind from the HLR. If MAP_ANY_TIME_INTERROGATION_cnf is received, it goes to Check_Confirmation. If OK, it goes to Any Time Interrogation ack, then Idle. If User Error, Provider Error, or Data Error is received, it goes to MAP_CLOSE_req. If MAP_NOTICE_ind is received, it goes to MAP_CLOSE_req. If MAP_P_ABORT_ind, MAP_U_ABORT_ind, or MAP_CLOSE_ind is received, it goes to Set negative response: system failure, then Any Time Interrogation negative response, then Idle.](7cbe81e808d4abb374cc659ddcd3fa53_img.jpg) + +process ATI\_To\_HLR\_gsmSCF + +ATI2HLR\_SCF1(1) + +Process in the gsmSCF to request subscriber location and/or state from the HLR + +Signals to/from the left are to/from the application process in the gsmSCF; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> ATI: Any Time Interrogation + ATI --> OutReq: MAP_OPEN_req, MAP_ANY_TIME_INTERROGATION_req, MAP_DELIMITER_req + OutReq --> RecOpenCnf: Receive_Open_Cnf + RecOpenCnf --> Wait_For_HLR_Response: OK + RecOpenCnf --> Abort: Vr, Error + Abort --> Idle + Wait_For_HLR_Response --> RecCnf: MAP_ANY_TIME_INTERROGATION_cnf + Wait_For_HLR_Response --> RecNotice: MAP_NOTICE_ind + Wait_For_HLR_Response --> RecAbortClose: MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind + RecCnf --> Check_Confirmation + Check_Confirmation --> ATI_Ack: Any Time Interrogation ack + Check_Confirmation --> Error: User Error, Provider Error, Data Error + ATI_Ack --> Idle + Error --> RecCloseReq: MAP_CLOSE_req + RecCloseReq --> Set_Neg_Response: Set negative response: system failure + Set_Neg_Response --> ATI_Neg_Response: Any Time Interrogation negative response + ATI_Neg_Response --> Idle + RecNotice --> RecCloseReq + RecAbortClose --> Set_Neg_Response + +``` + +State transition diagram for process ATI\_To\_HLR\_gsmSCF. The process starts at an initial state, goes to Idle, then Any Time Interrogation. It sends MAP\_OPEN\_req, MAP\_ANY\_TIME\_INTERROGATION\_req, and MAP\_DELIMITER\_req to the HLR. It receives Open\_Cnf from the HLR. If OK, it goes to Wait\_For\_HLR\_Response. If Vr, Error, it goes to Abort. From Wait\_For\_HLR\_Response, it can receive MAP\_ANY\_TIME\_INTERROGATION\_cnf, MAP\_NOTICE\_ind, or MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind from the HLR. If MAP\_ANY\_TIME\_INTERROGATION\_cnf is received, it goes to Check\_Confirmation. If OK, it goes to Any Time Interrogation ack, then Idle. If User Error, Provider Error, or Data Error is received, it goes to MAP\_CLOSE\_req. If MAP\_NOTICE\_ind is received, it goes to MAP\_CLOSE\_req. If MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, or MAP\_CLOSE\_ind is received, it goes to Set negative response: system failure, then Any Time Interrogation negative response, then Idle. + +4637 + +4638 + +Figure 24A.5/3: Process ATI\_To\_HLR\_gsmSCF + +![State transition diagram for process ATI_To_GMLC_gsmSCF. The process starts at an initial state, goes to Idle, then Obtain Subscriber Location. It then sends MAP requests (OPEN, ANY_TIME_INTERROGATION, DELIMITER) to the GMLC. It receives an Open_Cnf and checks it. If OK, it goes to Wait_For_GMLC_Response. If Vr, Error, it goes to Abort and then Idle. From Wait_For_GMLC_Response, it can receive MAP_ANY_TIME_INTERROGATION_cnf (leading to Check Confirmation), MAP_NOTICE_ind (leading to MAP_CLOSE_req), or MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind. Check Confirmation leads to Obtain Subscriber Location ack and then Idle. MAP_CLOSE_req leads to Set negative response: system failure, which leads to Obtain Subscriber Location negative response and then Idle.](1fafab41a297e962a03d24cacd32f479_img.jpg) + +**process ATI\_To\_GMLC\_gsmSCF** **ATI2GMLC\_SCF1(1)** + +Process in the gsmSCF to request subscriber location from the GMLC + +Signals to/from the left are to/from the application process in the gsmSCF; signals to/from the right are to/from the GMLC + +``` + +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> Obtain[Obtain Subscriber Location] + Obtain --> SendReq{ } + SendReq --> SendReq : MAP_OPEN_req, MAP_ANY_TIME_INTERROGATION_req, MAP_DELIMITER_req + SendReq --> ReceiveCnf[Receive Open_Cnf] + ReceiveCnf --> Decision1{ } + Decision1 --> Abort : Vr, Error + Decision1 --> WaitForResponse[Wait_For_GMLC_Response] : OK + Abort --> Idle2[Idle] + WaitForResponse --> Decision2{ } + Decision2 --> ReceiveCnf2[MAP_ANY_TIME_INTERROGATION_cnf] + Decision2 --> NoticeInd[MAP_NOTICE_ind] + Decision2 --> AbortInd[MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind] + ReceiveCnf2 --> CheckConfirmation[Check Confirmation] + CheckConfirmation --> ObtainAck[Obtain Subscriber Location ack] : OK + CheckConfirmation --> SetNegative[Set negative response: system failure] : User Error, Provider Error, Data Error + ObtainAck --> Idle3[Idle] + NoticeInd --> CloseReq[MAP_CLOSE_req] + CloseReq --> SetNegative + AbortInd --> SetNegative + SetNegative --> ObtainNeg[Obtain Subscriber Location negative response] + ObtainNeg --> Idle4[Idle] + +``` + +State transition diagram for process ATI\_To\_GMLC\_gsmSCF. The process starts at an initial state, goes to Idle, then Obtain Subscriber Location. It then sends MAP requests (OPEN, ANY\_TIME\_INTERROGATION, DELIMITER) to the GMLC. It receives an Open\_Cnf and checks it. If OK, it goes to Wait\_For\_GMLC\_Response. If Vr, Error, it goes to Abort and then Idle. From Wait\_For\_GMLC\_Response, it can receive MAP\_ANY\_TIME\_INTERROGATION\_cnf (leading to Check Confirmation), MAP\_NOTICE\_ind (leading to MAP\_CLOSE\_req), or MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind. Check Confirmation leads to Obtain Subscriber Location ack and then Idle. MAP\_CLOSE\_req leads to Set negative response: system failure, which leads to Obtain Subscriber Location negative response and then Idle. + +4639 + +4640 + +Figure 24A.5/4: Process ATI\_To\_GMLC\_gsmSCF + +![Flowchart for process ATI_HLR. It starts with an initial state leading to 'Idle'. From 'Idle', it receives an 'Open_ind' signal. If 'OK', it goes to 'Wait_For_Service_Indication'. If 'Vr, Error', it returns to 'Idle'. From 'Wait_For_Service_Indication', it branches into three paths: 'MAP_P_ABORT_ind' (leading to 'Idle'), 'MAP_ANY_TIME_INTERROGATION_ind' (leading to 'Any Time Interrogation request'), and 'MAP_NOTICE_ind' (leading to 'MAP_CLOSE_req' and then 'Idle'). From 'Any Time Interrogation request', it goes to 'Wait_For_Application_Response'. From there, it branches into 'Any Time Interrogation ack' (leading to 'Set result') and 'Any Time Interrogation negative response' (leading to 'Set error'). Both 'Set result' and 'Set error' lead to a merge point. From the merge point, it sends 'MAP_ANY_TIME_INTERROGATION_rsp' and 'MAP_CLOSE_req' signals, and then returns to 'Idle'.](0ce1118265c8d34891db8c8066c14971_img.jpg) + +**process ATI\_HLR** **ATI\_HLR1(2)** + +Process in the HLR to handle an Any Time Interrogation request + +Signals to/from the left are to/from the gsmSCF; signals to/from the right are to/from the application process in the HLR (see 3GPP TS 23.078) + +``` + + graph TD + Start([ ]) --> Idle1([Idle]) + Idle1 -- "Receive_Open_ind" --> WaitForService[Wait_For_Service_Indication] + WaitForService -- "OK" --> WaitForService + WaitForService -- "Vr, Error" --> Idle2([Idle]) + WaitForService --> MAP_P_ABORT{MAP_P_ABORT_ind} + WaitForService --> MAP_ANY_TIME_INTERROGATION{MAP_ANY_TIME_INTERROGATION_ind} + WaitForService --> MAP_NOTICE{MAP_NOTICE_ind} + MAP_P_ABORT --> Idle3([Idle]) + MAP_ANY_TIME_INTERROGATION --> ATI_Request{{Any Time Interrogation request}} + ATI_Request --> WaitForApp[Wait_For_Application_Response] + MAP_NOTICE --> MAP_CLOSE_req{{MAP_CLOSE_req}} + MAP_CLOSE_req --> Idle4([Idle]) + WaitForApp --> ATI_Ack{{Any Time Interrogation ack}} + WaitForApp --> ATI_NegResp{{Any Time Interrogation negative response}} + ATI_Ack --> SetResult[Set result] + ATI_NegResp --> SetError[Set error] + SetResult --> Merge(( )) + SetError --> Merge + Merge --> MAP_ANY_TIME_INTERROGATION_rsp[MAP_ANY_TIME_INTERROGATION_rsp] + Merge --> MAP_CLOSE_req2[MAP_CLOSE_req] + Merge --> Idle5([Idle]) + +``` + +Flowchart for process ATI\_HLR. It starts with an initial state leading to 'Idle'. From 'Idle', it receives an 'Open\_ind' signal. If 'OK', it goes to 'Wait\_For\_Service\_Indication'. If 'Vr, Error', it returns to 'Idle'. From 'Wait\_For\_Service\_Indication', it branches into three paths: 'MAP\_P\_ABORT\_ind' (leading to 'Idle'), 'MAP\_ANY\_TIME\_INTERROGATION\_ind' (leading to 'Any Time Interrogation request'), and 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req' and then 'Idle'). From 'Any Time Interrogation request', it goes to 'Wait\_For\_Application\_Response'. From there, it branches into 'Any Time Interrogation ack' (leading to 'Set result') and 'Any Time Interrogation negative response' (leading to 'Set error'). Both 'Set result' and 'Set error' lead to a merge point. From the merge point, it sends 'MAP\_ANY\_TIME\_INTERROGATION\_rsp' and 'MAP\_CLOSE\_req' signals, and then returns to 'Idle'. + +4641 + +4642 + +**Figure 24A.5/5 (sheet 1 of 2): Process ATI\_HLR** + +![State transition diagram for process ATI_HLR. The process starts in 'Wait_For_Application_Response', moves to 'Provide Subscriber Info', then to an interface with 'To VLR or SGSN' where it sends 'MAP_OPEN_req', 'MAP_PROVIDE_SUBSCRIBER_INFO_req', and 'MAP_DELIMITER_req'. It receives 'Receive_Open_Cnf' with 'OK' or 'Vr, Error' outcomes. 'OK' leads to 'Wait_For_PSI_Response', which then leads to a state with three outgoing transitions: 'MAP_PROVIDE_SUBSCRIBER_INFO_cnf' to 'Check Confirmation' (OK leads to 'Provide Subscriber Info ack' then 'Wait_For_Application_Response'), 'MAP_NOTICE_ind' to 'MAP_CLOSE_req' (leading to 'Provide Subscriber Info negative response' then 'Wait_For_Application_Response'), and an unlabeled transition to 'MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind'. 'Vr, Error' from 'Receive_Open_Cnf' leads to 'Provide Subscriber Info negative response' then 'Wait_For_Application_Response'. 'Check Confirmation' also leads to 'MAP_CLOSE_req' on 'User Error, Provider Error, Data Error'.](ef965323bcabea8dc2e3f8be98b8f7dd_img.jpg) + +**process ATI\_HLR** + +Process in the HLR to handle an Any Time Interrogation request + +**ATI\_HLR2(2)** + +Signals to/from the left are to/from the gsmSCF; signals to/from the right are to/from the application process in the HLR (see 3GPP TS 23.078) unless marked otherwise + +``` + +stateDiagram-v2 + [*] --> Wait_For_Application_Response + Wait_For_Application_Response --> Provide_Subscriber_Info : Provide Subscriber Info + Provide_Subscriber_Info --> Interface : To VLR or SGSN + state "Interface" as Interface + Interface --> Send_Requests : MAP_OPEN_req, MAP_PROVIDE_SUBSCRIBER_INFO_req, MAP_DELIMITER_req + Send_Requests --> Receive_Open_Cnf : Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_PSI_Response : OK + Receive_Open_Cnf --> Provide_Subscriber_Info_Neg : Vr, Error + Wait_For_PSI_Response --> State_With_Three_Out + state "State With Three Out" as State_With_Three_Out + State_With_Three_Out --> Check_Confirmation : MAP_PROVIDE_SUBSCRIBER_INFO_cnf + State_With_Three_Out --> MAP_CLOSE_req : MAP_NOTICE_ind + State_With_Three_Out --> MAP_P_ABORT_ind : + Check_Confirmation --> Provide_Subscriber_Info_Ack : OK + Check_Confirmation --> MAP_CLOSE_req : User Error, Provider Error, Data Error + Provide_Subscriber_Info_Ack --> Wait_For_Application_Response + MAP_CLOSE_req --> Provide_Subscriber_Info_Neg + Provide_Subscriber_Info_Neg --> Wait_For_Application_Response + MAP_P_ABORT_ind --> Wait_For_Application_Response + +``` + +State transition diagram for process ATI\_HLR. The process starts in 'Wait\_For\_Application\_Response', moves to 'Provide Subscriber Info', then to an interface with 'To VLR or SGSN' where it sends 'MAP\_OPEN\_req', 'MAP\_PROVIDE\_SUBSCRIBER\_INFO\_req', and 'MAP\_DELIMITER\_req'. It receives 'Receive\_Open\_Cnf' with 'OK' or 'Vr, Error' outcomes. 'OK' leads to 'Wait\_For\_PSI\_Response', which then leads to a state with three outgoing transitions: 'MAP\_PROVIDE\_SUBSCRIBER\_INFO\_cnf' to 'Check Confirmation' (OK leads to 'Provide Subscriber Info ack' then 'Wait\_For\_Application\_Response'), 'MAP\_NOTICE\_ind' to 'MAP\_CLOSE\_req' (leading to 'Provide Subscriber Info negative response' then 'Wait\_For\_Application\_Response'), and an unlabeled transition to 'MAP\_P\_ABORT\_ind, MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind'. 'Vr, Error' from 'Receive\_Open\_Cnf' leads to 'Provide Subscriber Info negative response' then 'Wait\_For\_Application\_Response'. 'Check Confirmation' also leads to 'MAP\_CLOSE\_req' on 'User Error, Provider Error, Data Error'. + +4643 + +4644 + +**Figure 24A.5/5 (sheet 2 of 2): Process ATI\_HLR** + +![State transition diagram for process ATI_GMLC. It starts at an initial state, goes to Idle, then receives an Open indication. From there, it can go to Wait_For_Service_Indication (OK path) or Idle (Vr, Error path). Wait_For_Service_Indication leads to a decision point for MAP_P_ABORT_ind, MAP_ANY_TIME_INTERROGATION_ind, and MAP_NOTICE_ind. The central path leads to Any Time Interrogation request, then Wait_For_Application_Response, which then branches to Any Time Interrogation ack or negative response, leading to Set result or Set error. Both lead to a response state with MAP_ANY_TIME_INTERROGATION_rsp and MAP_CLOSE_req, returning to Idle. The MAP_P_ABORT_ind and MAP_NOTICE_ind paths also lead to Idle states via MAP_CLOSE_req.](252e7ba24faaa002513a8f0399938188_img.jpg) + +**process ATI\_GMLC** + +**ATI\_GMLC1(1)** + +Process in the HLR to handle an Any Time Interrogation request + +Signals to/from the left are to/from the gsmSCF; signals to/from the right are to/from the application process in the GMLC (see 3GPP TS 23.078) + +``` + +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> Receive_Open_ind[Receive_Open_ind] + Receive_Open_ind --> Wait_For_Service_Indication[Wait_For_Service_Indication] : OK + Receive_Open_ind --> Idle2[Idle] : Vr, Error + Wait_For_Service_Indication --> Decision1{ } + Decision1 --> MAP_P_ABORT_ind[MAP_P_ABORT_ind] + Decision1 --> MAP_ANY_TIME_INTERROGATION_ind[MAP_ANY_TIME_INTERROGATION_ind] + Decision1 --> MAP_NOTICE_ind[MAP_NOTICE_ind] + MAP_P_ABORT_ind --> Idle3[Idle] + MAP_ANY_TIME_INTERROGATION_ind --> Any_Time_Interrogation_request[Any Time Interrogation request] + Any_Time_Interrogation_request --> Wait_For_Application_Response[Wait_For_Application_Response] + Wait_For_Application_Response --> Decision2{ } + Decision2 --> Any_Time_Interrogation_ack[Any Time Interrogation ack] + Decision2 --> Any_Time_Interrogation_negative_response[Any Time Interrogation negative response] + Any_Time_Interrogation_ack --> Set_result[Set result] + Any_Time_Interrogation_negative_response --> Set_error[Set error] + Set_result --> Decision3{ } + Set_error --> Decision3 + Decision3 --> MAP_ANY_TIME_INTERROGATION_rsp[MAP_ANY_TIME_INTERROGATION_rsp] + Decision3 --> MAP_CLOSE_req1[MAP_CLOSE_req] + MAP_ANY_TIME_INTERROGATION_rsp --> Idle4[Idle] + MAP_CLOSE_req1 --> Idle4 + MAP_NOTICE_ind --> MAP_CLOSE_req2[MAP_CLOSE_req] + MAP_CLOSE_req2 --> Idle5[Idle] + +``` + +State transition diagram for process ATI\_GMLC. It starts at an initial state, goes to Idle, then receives an Open indication. From there, it can go to Wait\_For\_Service\_Indication (OK path) or Idle (Vr, Error path). Wait\_For\_Service\_Indication leads to a decision point for MAP\_P\_ABORT\_ind, MAP\_ANY\_TIME\_INTERROGATION\_ind, and MAP\_NOTICE\_ind. The central path leads to Any Time Interrogation request, then Wait\_For\_Application\_Response, which then branches to Any Time Interrogation ack or negative response, leading to Set result or Set error. Both lead to a response state with MAP\_ANY\_TIME\_INTERROGATION\_rsp and MAP\_CLOSE\_req, returning to Idle. The MAP\_P\_ABORT\_ind and MAP\_NOTICE\_ind paths also lead to Idle states via MAP\_CLOSE\_req. + +4645 + +4646 + +Figure 24A.5/6: Process ATI\_GMLC + +--- + +## 4647 24B Location Services process description + +### 4648 24B.1 Routeing information retrieval procedure for LCS + +#### 4649 24B.1.1 General + +4650 The message flow for successful retrieval of routeing information related to location services is shown in figure +4651 24B.1/1. + +![Sequence diagram showing message flow between GMLC and HLR for routeing information retrieval.](89fc4d82cf10d623e9edc219240205d8_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant HLR + Note right of GMLC: MAP_SEND_ROUTING_INFO_FOR_LCS + GMLC->>HLR: MAP_SEND_ROUTING_INFO_FOR_LCS + Note left of HLR: MAP_SEND_ROUTING_INFO_FOR_LCS_ACK + HLR->>GMLC: MAP_SEND_ROUTING_INFO_FOR_LCS_ACK +``` + +The diagram illustrates a sequence of messages between two entities, GMLC and HLR. The GMLC sends a message labeled 'MAP\_SEND\_ROUTING\_INFO\_FOR\_LCS' to the HLR. The HLR responds with a message labeled 'MAP\_SEND\_ROUTING\_INFO\_FOR\_LCS\_ACK' back to the GMLC. + +Sequence diagram showing message flow between GMLC and HLR for routeing information retrieval. + +4652 + +4653 **Figure 24B.1/1: Message flow for retrieval of routeing information for LCS** + +4654 The following MAP service is used to retrieve routeing information: + +4655 `MAP_SEND_ROUTING_INFO_FOR_LCS` see clause 13A.1. + +#### 4656 24B.1.2 Process in the GMLC + +4657 The MAP process in the GMLC to request routeing information for LCS is shown in figure 24B.1/2. The MAP process +4658 invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +4659 `Receive_Open_Cnf` see clause 25.1.2; + +4660 `Check_Confirmation` see clause 25.2.2. + +#### 4661 24B.1.3 Process in the HLR + +4662 The MAP process in the HLR to handle a request for routeing information for LCS is shown in figure 24B.1/3. The +4663 MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +4664 `Receive_Open_Ind` see clause 25.1.1; + +4665 `Check_Indication` see clause 25.2.1. + +4666 + +![State transition diagram for process SRI_LCS_GMLC. The process starts at an initial state, goes to Idle, then sends routing info for LCS. It then sends MAP_OPEN_req, MAP_SEND_ROUTING_INFO_FOR_LCS_req, and MAP_DELIMITER_req to the HLR. It receives an Open_Cnf. If OK, it waits for an HLR response. If Vr, Error, it goes to a negative response. The HLR response can be MAP_SEND_ROUTING_INFO_FOR_LCS_cnf (leading to Check Confirmation), MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind, or MAP_NOTICE_ind (leading to MAP_CLOSE_req). Check Confirmation leads to OK (send ack), User Error (send negative response), or Provider Error, Data Error (set negative response: System failure). All paths lead to Idle.](24508c55181829a29c6681322035ca67_img.jpg) + +**process SRI\_LCS\_GMLC** **SRI\_LCS\_GMLC1(1)** + +Process in the GMLC to retrieve routing information for a location services enquiry + +Signals to/from the left are to/from the application process in the GMLC; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Send_routing_info_for_LCS + Send_routing_info_for_LCS --> Send_MAP_requests + Send_MAP_requests --> Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_HLR_Response: OK + Receive_Open_Cnf --> Set_negative_response_System_failure: Vr, Error + Wait_For_HLR_Response --> MAP_SEND_ROUTING_INFO_FOR_LCS_cnf + Wait_For_HLR_Response --> MAP_U_ABORT_ind + Wait_For_HLR_Response --> MAP_P_ABORT_ind + Wait_For_HLR_Response --> MAP_CLOSE_ind + Wait_For_HLR_Response --> MAP_NOTICE_ind + MAP_SEND_ROUTING_INFO_FOR_LCS_cnf --> Check_Confirmation + MAP_U_ABORT_ind --> Set_negative_response_System_failure + MAP_P_ABORT_ind --> Set_negative_response_System_failure + MAP_CLOSE_ind --> Set_negative_response_System_failure + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Set_negative_response_System_failure + Check_Confirmation --> OK + Check_Confirmation --> User_Error + Check_Confirmation --> Provider_Error_Data_Error + OK --> Send_routing_info_for_LCS_ack + User_Error --> Send_routing_info_for_LCS_negative_response + Provider_Error_Data_Error --> Set_negative_response_System_failure + Send_routing_info_for_LCS_ack --> Idle + Send_routing_info_for_LCS_negative_response --> Idle + Set_negative_response_System_failure --> Send_routing_info_for_LCS_negative_response + Send_routing_info_for_LCS_negative_response --> Idle + +``` + +**States:** Idle (Initial, Idle, Idle, Idle, Idle) +**Transitions:** + - Send routing info for LCS + - Send routing info for LCS ack + - Send routing info for LCS negative response +**Internal Messages:** + - MAP\_OPEN\_req, MAP\_SEND\_ROUTING\_INFO\_FOR\_LCS\_req, MAP\_DELIMITER\_req + - Receive\_Open\_Cnf + - MAP\_SEND\_ROUTING\_INFO\_FOR\_LCS\_cnf + - MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind + - MAP\_NOTICE\_ind + - MAP\_CLOSE\_req +**External Conditions/Responses:** + - OK + - User Error + - Provider Error, Data Error + - Vr, Error + +State transition diagram for process SRI\_LCS\_GMLC. The process starts at an initial state, goes to Idle, then sends routing info for LCS. It then sends MAP\_OPEN\_req, MAP\_SEND\_ROUTING\_INFO\_FOR\_LCS\_req, and MAP\_DELIMITER\_req to the HLR. It receives an Open\_Cnf. If OK, it waits for an HLR response. If Vr, Error, it goes to a negative response. The HLR response can be MAP\_SEND\_ROUTING\_INFO\_FOR\_LCS\_cnf (leading to Check Confirmation), MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind, or MAP\_NOTICE\_ind (leading to MAP\_CLOSE\_req). Check Confirmation leads to OK (send ack), User Error (send negative response), or Provider Error, Data Error (set negative response: System failure). All paths lead to Idle. + +4667 + +4668 + +Figure 24B.1/2: Process SRI\_LCS\_GMLC + +![State transition diagram for process SRI_LCS_HLR. It starts at Idle, receives an Open indication, and then branches based on the response. One path sends routing info and returns to Idle. Another path handles notices or aborts and returns to Idle. A third path handles errors and returns to Idle.](1665ab0c7278ae76e38c3328113f09e5_img.jpg) + +**process SRI\_LCS\_HLR** **SRI\_LCS\_HLR1(1)** + +Process in the HLR to provide routing information for a location services enquiry + +Signals to/from the left are to/from the GMLC; signals to/from the right are to/from the application process in the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_Ind + Receive_Open_Ind --> Wait_For_Service_Indication: OK + Receive_Open_Ind --> Idle: Vr, Error + Wait_For_Service_Indication --> MAP_SEND_ROUTING_INFO_FOR_LCS_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + Wait_For_Service_Indication --> MAP_P_ABORT_ind + MAP_SEND_ROUTING_INFO_FOR_LCS_ind --> Check_Indication + Check_Indication --> Send_routing_info_for_LCS: OK + Check_Indication --> [*]: Error + Send_routing_info_for_LCS --> Wait_For_Routing_Info + Wait_For_Routing_Info --> Send_routing_info_for_LCS_ack + Wait_For_Routing_Info --> Send_routing_info_for_LCS_negative_response + Send_routing_info_for_LCS_ack --> Set_Result + Send_routing_info_for_LCS_negative_response --> Set_User_Error + Set_Result --> [*] + Set_User_Error --> [*] + [*] --> MAP_SEND_ROUTING_INFO_FOR_LCS_rsp + [*] --> MAP_CLOSE_req + MAP_SEND_ROUTING_INFO_FOR_LCS_rsp --> Idle + MAP_CLOSE_req --> Idle + +``` + +State transition diagram for process SRI\_LCS\_HLR. It starts at Idle, receives an Open indication, and then branches based on the response. One path sends routing info and returns to Idle. Another path handles notices or aborts and returns to Idle. A third path handles errors and returns to Idle. + +4669 + +4670 + +Figure 24B.1/3: Process SRI\_LCS\_HLR + +## 24B.2 Provide Subscriber Location procedure + +### 24B.2.1 General + +The message flow for successful retrieval of the location information of a target MS related to location services is shown in figure 24B.1/1. + +![Sequence diagram showing the message flow for retrieval of location information between GMLC and MSC/SGSN.](3db9a2e103b487562fa906a9df1e500a_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant MSC_SGSN as MSC/SGSN + Note right of GMLC: MAP_PROVIDE_SUBSCRIBER_LOCATION + GMLC->>MSC_SGSN: MAP_PROVIDE_SUBSCRIBER_LOCATION + Note left of MSC_SGSN: MAP_PROVIDE_SUBSCRIBER_LOCATION_ACK + MSC_SGSN-->>GMLC: MAP_PROVIDE_SUBSCRIBER_LOCATION_ACK +``` + +Sequence diagram showing the message flow for retrieval of location information between GMLC and MSC/SGSN. + +4675 + +4676 + +**Figure 24B.2/1: Message flow for retrieval of location information** + +The following MAP service is used to retrieve location information: + +MAP\_PROVIDE\_SUBSCRIBER\_LOCATION see clause 13A.2. + +### 24B.2.2 Process in the GMLC + +The MAP process in the GMLC to request location information from an MSC or an SGSN is shown in figure 24B.2/2. + +The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +Receive\_Open\_Cnf see clause 25.1.2; + +Check\_Confirmation see clause 25.2.2. + +### 24B.2.3 Process in the MSC + +The MAP process in the MSC to handle a request for location information from a GMLC is shown in figure 24B.2/3. + +The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +Receive\_Open\_Ind see clause 25.1.1; + +Check\_Indication see clause 25.2.1. + +### 24B.2.4 Process in the SGSN + +The MAP process in the SGSN to handle a request for location information from a GMLC is shown in figure 24B.2/4. + +The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +Receive\_Open\_Ind see clause 25.1.1; + +Check\_Indication see clause 25.2.1. + +![State transition diagram for process PSL_GMLC. The process starts at an initial state, goes to Idle, then Provide subscriber location. It then sends MAP_OPEN_req, MAP_PROVIDE_SUBSCRIBER_LOCATION_req, and MAP_DELIMITER_req. It receives Open_Cnf and enters Wait_For_Serving_Node_Response. From there, it can receive MAP_PROVIDE_SUBSCRIBER_LOCATION_cnf (leading to Check Confirmation), MAP_U_ABORT_ind, MAP_P_ABORT_ind, or MAP_CLOSE_ind (leading to Set negative response: System failure). Check Confirmation leads to Provide subscriber location ack or Set negative response: System failure. MAP_CLOSE_req leads to Set negative response: System failure. All negative responses lead to Provide subscriber location negative response. All final states lead back to Idle.](5ca1f26bc949fa36dc4ce38993cdfb20_img.jpg) + +**process PSL\_GMLC** **PSL\_GMLC1(1)** + +Process in the GMLC to retrieve the location of a target MS from the MSC or the SGSN + +Signals to/from the left are to/from the application process in the GMLC; signals to/from the right are to/from the MSC or the SGSN + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Provide_subscriber_location: Provide subscriber location + Provide_subscriber_location --> Outgoing: MAP_OPEN_req, MAP_PROVIDE_SUBSCRIBER_LOCATION_req, MAP_DELIMITER_req + Outgoing --> Receive_Open_Cnf: Receive Open_Cnf + Receive_Open_Cnf --> Wait_For_Serving_Node_Response: OK + Wait_For_Serving_Node_Response --> Incoming1: MAP_PROVIDE_SUBSCRIBER_LOCATION_cnf + Wait_For_Serving_Node_Response --> Incoming2: MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + Wait_For_Serving_Node_Response --> Incoming3: MAP_NOTICE_ind + Incoming1 --> Check_Confirmation: Check Confirmation + Check_Confirmation --> Provide_subscriber_location_ack: OK + Check_Confirmation --> Set_negative_response_1: User Error, Provider Error, Data Error + Set_negative_response_1 --> Provide_subscriber_location_negative_response_1: Provide subscriber location negative response + Incoming2 --> Set_negative_response_2: Set negative response: System failure + Incoming3 --> MAP_CLOSE_req: MAP_CLOSE_req + MAP_CLOSE_req --> Set_negative_response_3: Set negative response: System failure + Set_negative_response_2 --> Provide_subscriber_location_negative_response_2: Provide subscriber location negative response + Set_negative_response_3 --> Provide_subscriber_location_negative_response_3: Provide subscriber location negative response + Provide_subscriber_location_ack --> Idle + Provide_subscriber_location_negative_response_1 --> Idle + Provide_subscriber_location_negative_response_2 --> Idle + Provide_subscriber_location_negative_response_3 --> Idle + +``` + +State transition diagram for process PSL\_GMLC. The process starts at an initial state, goes to Idle, then Provide subscriber location. It then sends MAP\_OPEN\_req, MAP\_PROVIDE\_SUBSCRIBER\_LOCATION\_req, and MAP\_DELIMITER\_req. It receives Open\_Cnf and enters Wait\_For\_Serving\_Node\_Response. From there, it can receive MAP\_PROVIDE\_SUBSCRIBER\_LOCATION\_cnf (leading to Check Confirmation), MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, or MAP\_CLOSE\_ind (leading to Set negative response: System failure). Check Confirmation leads to Provide subscriber location ack or Set negative response: System failure. MAP\_CLOSE\_req leads to Set negative response: System failure. All negative responses lead to Provide subscriber location negative response. All final states lead back to Idle. + +4694 + +4695 + +Figure 24B.2/2: Process PSL\_GMLC + +![State transition diagram for process PSL_MSC. It starts at an initial state, goes to Idle, then Receive_Open_ind. From there, an OK path leads to Wait_For_Service_Indication, which then branches into three paths: MAP_PROVIDE_SUBSCRIBER_LOCATION_ind (leading to Check_Indication, then Provide subscriber location, then Wait_For_Location_Info, then either Provide subscriber location ack or Provide subscriber location negative response, then Set Result or Set User Error), MAP_NOTICE_ind (leading to MAP_CLOSE_req), and MAP_P_ABORT_ind (leading to Idle). Both Set Result and MAP_CLOSE_req lead to a merge point, which then leads to a response state (MAP_PROVIDE_SUBSCRIBER_LOCATION_rsp / MAP_CLOSE_req) and finally back to Idle. An Error path from Check_Indication also leads to Idle.](323b3cf879e2d4b1684f987244766b53_img.jpg) + +**process PSL\_MSC** **PSL\_MSC1(1)** + +Process in the MSC to retrieve the location of a target MS + +Signals to/from the left are to/from the GMLC; +signals to/from the right are to/from the application process in the MSC + +``` + +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> Receive_Open_ind[Receive_Open_ind] + Receive_Open_ind --> Wait_For_Service_Indication[Wait_For_Service_Indication] + Wait_For_Service_Indication --> MAP_PROVIDE_SUBSCRIBER_LOCATION_ind[MAP_PROVIDE_SUBSCRIBER_LOCATION_ind] + Wait_For_Service_Indication --> MAP_NOTICE_ind[MAP_NOTICE_ind] + Wait_For_Service_Indication --> MAP_P_ABORT_ind[MAP_P_ABORT_ind] + MAP_P_ABORT_ind --> Idle2[Idle] + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> MergePoint(( )) + MAP_PROVIDE_SUBSCRIBER_LOCATION_ind --> Check_Indication[Check_Indication] + Check_Indication --> Error[Error] + Check_Indication --> OK1[OK] + OK1 --> Provide_subscriber_location[Provide subscriber location] + Provide_subscriber_location --> Wait_For_Location_Info[Wait_For_Location_Info] + Wait_For_Location_Info --> Provide_subscriber_location_ack[Provide subscriber location ack] + Wait_For_Location_Info --> Provide_subscriber_location_negative_response[Provide subscriber location negative response] + Provide_subscriber_location_ack --> Set_Result[Set Result] + Provide_subscriber_location_negative_response --> Set_User_Error[Set User Error] + Set_Result --> MergePoint + Set_User_Error --> MergePoint + MergePoint --> MAP_PROVIDE_SUBSCRIBER_LOCATION_rsp[MAP_PROVIDE_SUBSCRIBER_LOCATION_rsp / MAP_CLOSE_req] + MAP_PROVIDE_SUBSCRIBER_LOCATION_rsp --> Idle3[Idle] + +``` + +State transition diagram for process PSL\_MSC. It starts at an initial state, goes to Idle, then Receive\_Open\_ind. From there, an OK path leads to Wait\_For\_Service\_Indication, which then branches into three paths: MAP\_PROVIDE\_SUBSCRIBER\_LOCATION\_ind (leading to Check\_Indication, then Provide subscriber location, then Wait\_For\_Location\_Info, then either Provide subscriber location ack or Provide subscriber location negative response, then Set Result or Set User Error), MAP\_NOTICE\_ind (leading to MAP\_CLOSE\_req), and MAP\_P\_ABORT\_ind (leading to Idle). Both Set Result and MAP\_CLOSE\_req lead to a merge point, which then leads to a response state (MAP\_PROVIDE\_SUBSCRIBER\_LOCATION\_rsp / MAP\_CLOSE\_req) and finally back to Idle. An Error path from Check\_Indication also leads to Idle. + +4696 + +4697 + +**Figure 24B.2/3: Process PSL\_MSC** + +![State transition diagram for process PSL_SGSN. The process starts at an initial state, goes to Idle, then receives an Open indication. From there, it can go to Wait_For_Service_Indication, then either back to Idle (on error), or branch into three parallel paths: MAP_PROVIDE_SUBSCRIBER_LOCATION_ind, MAP_NOTICE_ind, and MAP_P_ABORT_ind. The first path leads to Check_Indication, then either to Provide subscriber location (on OK) or back to Idle (on Error). The second path leads to MAP_CLOSE_req. The third path leads directly to Idle. Both Provide subscriber location and MAP_CLOSE_req lead to Wait_For_Location_Info. From there, it can lead to Provide subscriber location ack, Set Result, or Set User Error. All three lead to a merge point, which then leads to a response state (MAP_PROVIDE_SUBSCRIBER_LOCATION_rsp, MAP_CLOSE_req) and finally back to Idle.](2938130791afc86f7e37f5cd529eb667_img.jpg) + +**process PSL\_SGSN** **PSL\_SGSN1(1)** + +Process in the SGSN to retrieve the location of a target MS + +Signals to/from the left are to/from the GMLC; +signals to/from the right are to/from the application process in the SGSN + +``` + +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> Receive_Open_ind[Receive_Open_ind] + Receive_Open_ind --> Wait_For_Service_Indication[Wait_For_Service_Indication] + Wait_For_Service_Indication --> Idle2[Idle] : Vr, Error + Wait_For_Service_Indication --> MAP_PROVIDE_SUBSCRIBER_LOCATION_ind[MAP_PROVIDE_SUBSCRIBER_LOCATION_ind] + Wait_For_Service_Indication --> MAP_NOTICE_ind[MAP_NOTICE_ind] + Wait_For_Service_Indication --> MAP_P_ABORT_ind[MAP_P_ABORT_ind] + MAP_P_ABORT_ind --> Idle3[Idle] + MAP_NOTICE_ind --> MAP_CLOSE_req1[MAP_CLOSE_req] + MAP_CLOSE_req1 --> MAP_P_ABORT_ind + MAP_PROVIDE_SUBSCRIBER_LOCATION_ind --> Check_Indication[Check_Indication] + Check_Indication --> Idle2 : Error + Check_Indication --> Provide_subscriber_location[Provide subscriber location] : OK + Provide_subscriber_location --> Wait_For_Location_Info[Wait_For_Location_Info] + Wait_For_Location_Info --> Provide_subscriber_location_ack[Provide subscriber location ack] + Wait_For_Location_Info --> Set_Result[Set Result] + Wait_For_Location_Info --> Set_User_Error[Set User Error] + Set_User_Error --> MergePoint(( )) + Set_Result --> MergePoint + Provide_subscriber_location_ack --> MergePoint + MergePoint --> MAP_PROVIDE_SUBSCRIBER_LOCATION_rsp[MAP_PROVIDE_SUBSCRIBER_LOCATION_rsp +MAP_CLOSE_req] + MAP_PROVIDE_SUBSCRIBER_LOCATION_rsp --> Idle4[Idle] + +``` + +State transition diagram for process PSL\_SGSN. The process starts at an initial state, goes to Idle, then receives an Open indication. From there, it can go to Wait\_For\_Service\_Indication, then either back to Idle (on error), or branch into three parallel paths: MAP\_PROVIDE\_SUBSCRIBER\_LOCATION\_ind, MAP\_NOTICE\_ind, and MAP\_P\_ABORT\_ind. The first path leads to Check\_Indication, then either to Provide subscriber location (on OK) or back to Idle (on Error). The second path leads to MAP\_CLOSE\_req. The third path leads directly to Idle. Both Provide subscriber location and MAP\_CLOSE\_req lead to Wait\_For\_Location\_Info. From there, it can lead to Provide subscriber location ack, Set Result, or Set User Error. All three lead to a merge point, which then leads to a response state (MAP\_PROVIDE\_SUBSCRIBER\_LOCATION\_rsp, MAP\_CLOSE\_req) and finally back to Idle. + +4698 + +4699 + +Figure 24B.2/4: Process PSL\_SGSN + +## 24B.3 Subscriber Location Report procedure + +### 24B.3.1 General + +The message flow for successful report of the location information of a target MS related to location services is shown in figure 24B.3/1. + +![Sequence diagram showing the message flow for report of the location information between GMLC and MSC/SGSN.](6f3fc13f5890b406edd19c32ca20a482_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant MSC_SGSN as MSC/SGSN + Note right of MSC_SGSN: MAP_SUBSCRIBER_LOCATION_REPORT + MSC_SGSN->>GMLC: MAP_SUBSCRIBER_LOCATION_REPORT + Note left of GMLC: MAP_SUBSCRIBER_LOCATION_REPORT_ACK + GMLC->>MSC_SGSN: MAP_SUBSCRIBER_LOCATION_REPORT_ACK +``` + +Sequence diagram showing the message flow for report of the location information between GMLC and MSC/SGSN. + +4704 + +4705 + +**Figure 24B.3/1: Message flow for report of the location information** + +The following MAP services are used to report location information: + +MAP\_SUBSCRIBER\_LOCATION\_REPORT see clause 13A.3. + +### 24B.3.2 Process in the MSC + +The MAP process in the MSC to send a subscriber location report to the GMLC is shown in figure 24B.3/2. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +Receive\_Open\_Cnf see clause 25.1.2; + +Check\_Confirmation see clause 25.2.2. + +### 24B.3.3 Process in the SGSN + +The MAP process in the SGSN to send a subscriber location report to the GMLC is shown in figure 24B.3/3. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +Receive\_Open\_Cnf see clause 25.1.2; + +Check\_Confirmation see clause 25.2.2. + +### 24B.3.4 Process in the GMLC + +The MAP process in the GMLC to handle a subscriber location report is shown in figure 24B.3/4. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: + +Receive\_Open\_Ind see clause 25.1.1; + +Check\_Indication see clause 25.2.1. + +![Sequence diagram for process SLR_MSC showing the interaction between an application process and a GMLC for subscriber location reporting. The process starts at an Idle state, receives a location report, sends MAP requests, receives an Open confirmation, waits for a response, and then handles either a confirmation, an abort/notice, or a close request, leading to either an acknowledgment, a negative response, or returning to Idle.](428a14cda2c27da82e83d1024d9f717e_img.jpg) + +**process SLR\_MSC** **SLR\_MSC1(1)** + +Process in the MSC to report the location of an MS to the GMLC + +Signals to/from the left are to/from the GMLC; signals to/from the right are to/from the application process in the MSC + +``` + +sequenceDiagram + participant Application + participant SLR_MSC + Note left of Application: Process in the MSC to report the location of an MS to the GMLC + Note right of Application: Signals to/from the left are to/from the GMLC; signals to/from the right are to/from the application process in the MSC + + Application->>SLR_MSC: Subscriber location report + SLR_MSC->>Application: MAP_OPEN_req, MAP_SUBSCRIBER_LOCATION_REPORT_req, MAP_DELIMITER_req + Application-->>SLR_MSC: Receive_Open_Cnf + SLR_MSC->>Application: Wait_For_GMLC_Response + Note right of Application: OK + Note right of Application: Vr, Error + + alt Confirmation Path + SLR_MSC->>Application: MAP_SUBSCRIBER_LOCATION_REPORT_cnf + Application->>SLR_MSC: Check_Confirmation + Note right of Application: OK + SLR_MSC->>Application: Subscriber location report ack + Application-->>SLR_MSC: Idle + else User Error / Provider Error, Data Error + Application->>SLR_MSC: Set negative response: System failure + SLR_MSC->>Application: Subscriber location report negative response + Application-->>SLR_MSC: Idle + else Notice/Abort/Close Path + SLR_MSC->>Application: MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + SLR_MSC->>Application: MAP_NOTICE_ind + Application->>SLR_MSC: MAP_CLOSE_req + Note right of Application: System failure + SLR_MSC->>Application: Subscriber location report negative response + Application-->>SLR_MSC: Idle + end + +``` + +Sequence diagram for process SLR\_MSC showing the interaction between an application process and a GMLC for subscriber location reporting. The process starts at an Idle state, receives a location report, sends MAP requests, receives an Open confirmation, waits for a response, and then handles either a confirmation, an abort/notice, or a close request, leading to either an acknowledgment, a negative response, or returning to Idle. + +4723 + +4724 + +**Figure 24B.3/2: Process SLR\_MSC** + +![State transition diagram for process SLR_SGSN. The process starts at an initial state, goes to Idle, then receives a subscriber location report. It sends MAP_OPEN_req, MAP_SUBSCRIBER_LOCATION_REPORT_req, and MAP_DELIMITER_req. It then receives an Open_Cnf. If OK, it waits for a GMLC response. If Vr, Error, it goes to a negative response state. The GMLC response can be a confirmation (leading to Check Confirmation), an indication of abort/close (leading to a negative response state), or a notice (leading to a MAP CLOSE_req). Check Confirmation leads to a report ack and Idle state if OK, or a negative response state if User Error or Provider Error/Data Error. MAP CLOSE_req leads to a negative response state. All negative response states lead to an Idle state.](4e3fafcdb2449d818d4b424f3ef1e958_img.jpg) + +**process SLR\_SGSN** **SLR\_SGSN1(1)** + +Process in the SGSN to report the location of an MS to the GMLC + +Signals to/from the left are to/from the GMLC; signals to/from the right are to/from the application process in the MSC + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> SLR_Req: Subscriber location report + SLR_Req --> OutReq: MAP_OPEN_req, MAP_SUBSCRIBER_LOCATION_REPORT_req, MAP_DELIMITER_req + OutReq --> Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_GMLC_Response: OK + Receive_Open_Cnf --> Negative_Response: Vr, Error + Wait_For_GMLC_Response --> Confirmation: MAP_SUBSCRIBER_LOCATION_REPORT_cnf + Wait_For_GMLC_Response --> Indication: MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + Wait_For_GMLC_Response --> Notice: MAP_NOTICE_ind + Confirmation --> Check_Confirmation + Check_Confirmation --> Ack: OK + Check_Confirmation --> Negative_Response: User Error, Provider Error, Data Error + Ack --> Idle + Negative_Response --> Idle + Notice --> Close_Req: MAP_CLOSE_req + Close_Req --> Negative_Response + Negative_Response --> Idle + +``` + +State transition diagram for process SLR\_SGSN. The process starts at an initial state, goes to Idle, then receives a subscriber location report. It sends MAP\_OPEN\_req, MAP\_SUBSCRIBER\_LOCATION\_REPORT\_req, and MAP\_DELIMITER\_req. It then receives an Open\_Cnf. If OK, it waits for a GMLC response. If Vr, Error, it goes to a negative response state. The GMLC response can be a confirmation (leading to Check Confirmation), an indication of abort/close (leading to a negative response state), or a notice (leading to a MAP CLOSE\_req). Check Confirmation leads to a report ack and Idle state if OK, or a negative response state if User Error or Provider Error/Data Error. MAP CLOSE\_req leads to a negative response state. All negative response states lead to an Idle state. + +4725 + +4726 + +Figure 24B.3/3: Process SLR\_SGSN + +![State transition diagram for process SLR_GMLC. It starts at Idle, receives an Open indication, and then branches based on the response: OK leads to Wait_For_Service_Indication, while Vr, Error leads back to Idle. From Wait_For_Service_Indication, three signals are possible: MAP_SUBSCRIBER_LOCATION_REPORT_ind, MAP_NOTICE_ind, and MAP_P_ABORT_ind. The first leads to Check_Indication, which then leads to a decision point for Subscriber location report. If OK, it goes to Wait_For_Location_Info, then either Subscriber location report ack or Subscriber location report negative response, then Set Result or Set User Error, and finally to a merge point. If Error, it goes directly to the merge point. The second signal, MAP_NOTICE_ind, leads to MAP_CLOSE_req, which then leads to Idle. The third signal, MAP_P_ABORT_ind, also leads to Idle. From the merge point, the process sends a response (MAP_SUBSCRIBER_LOCATION_REPORT_rsp or MAP_CLOSE_req) and returns to Idle.](f22332641b460a9ad3c181dddf857ac7_img.jpg) + +**process SLR\_GMLC** **SLR\_GMLC1(1)** + +Process in the GMLC to receive a subscriber location report from the MSC or the SGSN + +Signals to/from the left are to/from the application process in the GMLC; signals to/from the right are to/from the MSC or the SGSN + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_ind + Receive_Open_ind --> Wait_For_Service_Indication : OK + Receive_Open_ind --> Idle : Vr, Error + Wait_For_Service_Indication --> MAP_SUBSCRIBER_LOCATION_REPORT_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + Wait_For_Service_Indication --> MAP_P_ABORT_ind + MAP_P_ABORT_ind --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + MAP_SUBSCRIBER_LOCATION_REPORT_ind --> Check_Indication + Check_Indication --> Subscriber_location_report : OK + Check_Indication --> Merge : Error + Subscriber_location_report --> Wait_For_Location_Info + Wait_For_Location_Info --> Subscriber_location_report_ack + Wait_For_Location_Info --> Subscriber_location_report_negative_response + Subscriber_location_report_ack --> Set Result + Subscriber_location_report_negative_response --> Set User Error + Set Result --> Merge + Set User Error --> Merge + Merge --> Response + Response --> Idle + +``` + +State transition diagram for process SLR\_GMLC. It starts at Idle, receives an Open indication, and then branches based on the response: OK leads to Wait\_For\_Service\_Indication, while Vr, Error leads back to Idle. From Wait\_For\_Service\_Indication, three signals are possible: MAP\_SUBSCRIBER\_LOCATION\_REPORT\_ind, MAP\_NOTICE\_ind, and MAP\_P\_ABORT\_ind. The first leads to Check\_Indication, which then leads to a decision point for Subscriber location report. If OK, it goes to Wait\_For\_Location\_Info, then either Subscriber location report ack or Subscriber location report negative response, then Set Result or Set User Error, and finally to a merge point. If Error, it goes directly to the merge point. The second signal, MAP\_NOTICE\_ind, leads to MAP\_CLOSE\_req, which then leads to Idle. The third signal, MAP\_P\_ABORT\_ind, also leads to Idle. From the merge point, the process sends a response (MAP\_SUBSCRIBER\_LOCATION\_REPORT\_rsp or MAP\_CLOSE\_req) and returns to Idle. + +4727 + +4728 + +Figure 24B.3/4: Process SLR\_GMLC + +--- + +## 4729 25 General macro description + +### 4730 25.1 MAP\_OPEN handling macros + +#### 4731 25.1.1 Macro Receive\_Open\_Ind + +4732 This macro is used by a MAP service-user procedure when a peer entity requests opening of a dialogue. + +#### 4733 25.1.2 Macro Receive\_Open\_Cnf + +4734 This macro is used by a user procedure after it has requested opening of a dialogue towards a peer entity. + +macrodefinition Receive\_Open\_Ind + +Rec\_Open\_Ind1(2) + +Macro to handle a +MAP\_OPEN indication + +Signals to/from the left +are to/from the remote +peer entity + +![Flowchart for macrodefinition Receive_Open_Ind. It starts with an oval connector, followed by a process block 'MAP_OPEN_ind'. A decision diamond 'Version 1 AC?' has a 'Yes' path to connector 'Vr' and a 'No' path to decision 'MAP_OPEN info present?'. The 'No' path from 'MAP_OPEN info present?' leads to connector '2'. The 'Yes' path leads to 'Reference := Destination reference', then 'Check_Reference' (linked to Figure 25.1/3). From 'Check_Reference', 'OK' leads to 'Reference := Originating reference' and 'Error' leads to 'Refuse-reason := Invalid destination reference' (connector '1'). From 'Reference := Originating reference', it goes to another 'Check_Reference' (linked to Figure 25.1/3). From this 'Check_Reference', 'OK' leads to decision 'Destination reference check required?'. The 'No' path from this decision leads to connector '2', and the 'Yes' path leads to decision 'Destination reference known?'. The 'No' path from 'Destination reference known?' leads to 'Refuse-reason := Invalid destination reference' (connector '1'). The 'Yes' path from 'Destination reference known?' leads to connector '2'. All connectors (Vr, 1, 2) are circles with numbers or letters inside.](0d5b9c8b2002af22ccfc93c405fbea92_img.jpg) + +``` + +graph TD + Start([ ]) --> MAP_OPEN_ind[MAP_OPEN_ind] + MAP_OPEN_ind --> Version1AC{Version 1 AC?} + Version1AC -- Yes --> Vr((Vr)) + Version1AC -- No --> MAP_OPEN_info{MAP_OPEN info present?} + MAP_OPEN_info -- No --> Connector2_1((2)) + MAP_OPEN_info -- Yes --> RefDest[Reference := Destination reference] + RefDest --> CheckRef1[Check_Reference] + CheckRef1 -.-> Figure25_1_3_1[Figure 25.1/3] + CheckRef1 -- OK --> RefOrig[Reference := Originating reference] + CheckRef1 -- Error --> RefuseReason1[Refuse-reason := Invalid destination reference] + RefuseReason1 --> Connector1_1((1)) + RefOrig --> CheckRef2[Check_Reference] + CheckRef2 -.-> Figure25_1_3_2[Figure 25.1/3] + CheckRef2 -- OK --> DestCheckReq{Destination reference check required?} + DestCheckReq -- No --> Connector2_2((2)) + DestCheckReq -- Yes --> DestKnown{Destination reference known?} + DestKnown -- No --> RefuseReason2[Refuse-reason := Invalid destination reference] + RefuseReason2 --> Connector1_2((1)) + DestKnown -- Yes --> Connector2_3((2)) + +``` + +Flowchart for macrodefinition Receive\_Open\_Ind. It starts with an oval connector, followed by a process block 'MAP\_OPEN\_ind'. A decision diamond 'Version 1 AC?' has a 'Yes' path to connector 'Vr' and a 'No' path to decision 'MAP\_OPEN info present?'. The 'No' path from 'MAP\_OPEN info present?' leads to connector '2'. The 'Yes' path leads to 'Reference := Destination reference', then 'Check\_Reference' (linked to Figure 25.1/3). From 'Check\_Reference', 'OK' leads to 'Reference := Originating reference' and 'Error' leads to 'Refuse-reason := Invalid destination reference' (connector '1'). From 'Reference := Originating reference', it goes to another 'Check\_Reference' (linked to Figure 25.1/3). From this 'Check\_Reference', 'OK' leads to decision 'Destination reference check required?'. The 'No' path from this decision leads to connector '2', and the 'Yes' path leads to decision 'Destination reference known?'. The 'No' path from 'Destination reference known?' leads to 'Refuse-reason := Invalid destination reference' (connector '1'). The 'Yes' path from 'Destination reference known?' leads to connector '2'. All connectors (Vr, 1, 2) are circles with numbers or letters inside. + +4735 + +4736 + +Figure 25.1/1 (sheet 1 of 2): Macro Receive\_Open\_Ind + +macrodefinition Receive\_Open\_Ind + +Rec\_Open\_Ind2(2) + +Macro to handle a +MAP\_OPEN indication + +Signals to/from the left +are to/from the remote +peer entity + +![Flowchart for macrodefinition Receive_Open_Ind. It consists of two vertical paths. Path 1 (left) starts at circle '1', goes to 'Result:= Dialogue refused', then 'AC name:= Highest version supported', then a pentagon 'MAP_OPEN_rsp', and ends at circle 'Error'. Path 2 (right) starts at circle '2', goes to 'Result:= Dialogue accepted', then 'AC name:= Received AC name', then a pentagon 'MAP_OPEN_rsp', then a decision diamond. The diamond has a 'Yes' path to circle 'OK' and a 'No' path to circle 'Vr'. A note next to the diamond asks: 'Received AC version (Vr)= the one defined in this version of 3GPP TS 29.002?'.](28950712913dcf8428ff4b863e5fa780_img.jpg) + +``` + +graph TD + subgraph Path1 + 1((1)) --> R1[Result:= Dialogue refused] + R1 --> AC1[AC name:= Highest version supported] + AC1 --> M1{MAP_OPEN_rsp} + M1 --> E((Error)) + end + subgraph Path2 + 2((2)) --> R2[Result:= Dialogue accepted] + R2 --> AC2[AC name:= Received AC name] + AC2 --> M2{MAP_OPEN_rsp} + M2 --> D{Received AC version (Vr)= the one defined in this version of 3GPP TS 29.002?} + D -- Yes --> OK((OK)) + D -- No --> Vr((Vr)) + end + +``` + +Flowchart for macrodefinition Receive\_Open\_Ind. It consists of two vertical paths. Path 1 (left) starts at circle '1', goes to 'Result:= Dialogue refused', then 'AC name:= Highest version supported', then a pentagon 'MAP\_OPEN\_rsp', and ends at circle 'Error'. Path 2 (right) starts at circle '2', goes to 'Result:= Dialogue accepted', then 'AC name:= Received AC name', then a pentagon 'MAP\_OPEN\_rsp', then a decision diamond. The diamond has a 'Yes' path to circle 'OK' and a 'No' path to circle 'Vr'. A note next to the diamond asks: 'Received AC version (Vr)= the one defined in this version of 3GPP TS 29.002?'. + +4737 + +4738 + +Figure 25.1/1 (sheet 2 of 2): Macro Receive\_Open\_Ind + +![Flowchart for macrodefinition Receive_Open_Cnf. It starts with a connector, followed by 'Wait_For_Open_Cnf'. A horizontal line branches into three paths: 1) MAP_NOTICE_ind leads to MAP_CLOSE_req and then an Error state. 2) An unlabeled path leads to a box with MAP_U_ABORT_ind and MAP_P_ABORT_ind, then to an Error state. 3) MAP_OPEN_cnf leads to a 'Result?' decision diamond. From 'Result?', 'Dialogue accepted' leads to an OK state, and 'Dialogue refused' leads to a 'Refuse reason?' decision diamond. From 'Refuse reason?', 'AC not supported' leads to a 'Yes/No' decision diamond (Yes leads to Vr, No leads to Error), 'Potential version incompatibility' leads to a 'Vr:=V1' box and then to a Vr state, and 'Else' leads to an Error state.](f72079d5107eb4d888c7d6c24dfed66e_img.jpg) + +macrodefinition **Receive\_Open\_Cnf** **Rec\_Open\_Cnf1(1)** + +Macro to handle a MAP\_OPEN confirm + +Signals to/from the right are to/from the remote peer entity + +``` + +graph TD + Start([ ]) --> Wait[Wait_For_Open_Cnf] + Wait --> Branch1(( )) + Branch1 --> Notice[MAP_NOTICE_ind] + Branch1 --> Unlabeled[ ] + Branch1 --> OpenCnf[MAP_OPEN_cnf] + Notice --> CloseReq[MAP_CLOSE_req] + CloseReq --> Error1((Error)) + Unlabeled --> AbortInd[MAP_U_ABORT_ind, MAP_P_ABORT_ind] + AbortInd --> Error2((Error)) + OpenCnf --> Result{Result?} + Result -- Dialogue accepted --> OK((OK)) + Result -- Dialogue refused --> RefuseReason{Refuse reason?} + RefuseReason -- AC not supported --> YesNo{Yes/No} + YesNo -- Yes --> Vr1((Vr)) + YesNo -- No --> Error3((Error)) + RefuseReason -- Potential version incompatibility --> VrAssign[Vr:=V1] + VrAssign --> Vr2((Vr)) + RefuseReason -- Else --> Error4((Error)) + +``` + +Flowchart for macrodefinition Receive\_Open\_Cnf. It starts with a connector, followed by 'Wait\_For\_Open\_Cnf'. A horizontal line branches into three paths: 1) MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req and then an Error state. 2) An unlabeled path leads to a box with MAP\_U\_ABORT\_ind and MAP\_P\_ABORT\_ind, then to an Error state. 3) MAP\_OPEN\_cnf leads to a 'Result?' decision diamond. From 'Result?', 'Dialogue accepted' leads to an OK state, and 'Dialogue refused' leads to a 'Refuse reason?' decision diamond. From 'Refuse reason?', 'AC not supported' leads to a 'Yes/No' decision diamond (Yes leads to Vr, No leads to Error), 'Potential version incompatibility' leads to a 'Vr:=V1' box and then to a Vr state, and 'Else' leads to an Error state. + +4739 + +4740 + +**Figure 25.1/2: Macro Receive\_Open\_Cnf** + +macrodefinition Check\_Reference + +Check\_Ref1(1) + +Macro to check a received destination reference or originating reference + +![Flowchart for macro Check_Reference. It starts with a connector, then a decision 'Reference present?'. If 'No', it goes to a second decision 'Reference required for this AC?'. If 'Yes' to the second decision, it ends in 'Error'; if 'No', it ends in 'OK'. If 'Yes' to the first decision, it goes to a third decision 'Reference allowed for this AC?'. If 'Yes' to the third decision, it goes to a fourth decision 'Data type correct?'. If 'Yes' to the fourth decision, it ends in 'OK'; if 'No', it ends in 'Error'. If 'No' to the third decision, it ends in 'Error'.](8e7bb810b1f26df58adcdb261f87a400_img.jpg) + +``` +graph TD; Start([ ]) --> Q1{Reference present?}; Q1 -- No --> Q2{Reference required for this AC?}; Q1 -- Yes --> Q3{Reference allowed for this AC?}; Q2 -- Yes --> Error1([Error]); Q2 -- No --> OK1([OK]); Q3 -- Yes --> Q4{Data type correct?}; Q3 -- No --> Error2([Error]); Q4 -- Yes --> OK2([OK]); Q4 -- No --> Error3([Error]); +``` + +Flowchart for macro Check\_Reference. It starts with a connector, then a decision 'Reference present?'. If 'No', it goes to a second decision 'Reference required for this AC?'. If 'Yes' to the second decision, it ends in 'Error'; if 'No', it ends in 'OK'. If 'Yes' to the first decision, it goes to a third decision 'Reference allowed for this AC?'. If 'Yes' to the third decision, it goes to a fourth decision 'Data type correct?'. If 'Yes' to the fourth decision, it ends in 'OK'; if 'No', it ends in 'Error'. If 'No' to the third decision, it ends in 'Error'. + +4741 + +4742 + +Figure 25.1/3: Macro Check\_Reference + +4743 **25.2**    **Macros to check the content of indication and confirmation** +4744            **primitives** + +4745 **25.2.1**    **Macro Check\_Indication** + +4746 This macro checks that an indication includes all the parameters required by the application, no more and no less, and +4747 that the parameters are all within the correct range. It does not handle syntax checking; that is part of the function of the +4748 MAP protocol machine. + +4749 **25.2.2**    **Macro Check\_Confirmation** + +4750 This macro checks whether a confirmation contains an error or a result, and if it contains a result whether the result is +4751 correctly formed. + +macrodefinition Check\_Indication + +Check\_Ind1(1) + +Macro to check the content +of a MAP specific service indication + +![Flowchart for macro Check_Indication. It starts with a connector, followed by a decision 'Data missing?'. If 'Yes', it goes to 'Set User Error: Data missing' and then an 'Error' connector. If 'No', it goes to 'Unexpected data?'. If 'Yes', it goes to 'Set User Error: Unexpected data value' and then an 'Error' connector. If 'No', it goes to 'Unexpected value?'. If 'Yes', it goes to the same 'Set User Error: Unexpected data value' block. If 'No', it goes to an 'OK' connector.](6cbd3519014bac30018a1913c42f430b_img.jpg) + +``` +graph TD; Start([ ]) --> D1{Data missing?}; D1 -- Yes --> E1[Set User Error: Data missing]; E1 --> Error1((Error)); D1 -- No --> D2{Unexpected data?}; D2 -- Yes --> E2[Set User Error: Unexpected data value]; D2 -- No --> D3{Unexpected value?}; D3 -- Yes --> E2; D3 -- No --> OK((OK)); E2 --> Error2((Error)); +``` + +Flowchart for macro Check\_Indication. It starts with a connector, followed by a decision 'Data missing?'. If 'Yes', it goes to 'Set User Error: Data missing' and then an 'Error' connector. If 'No', it goes to 'Unexpected data?'. If 'Yes', it goes to 'Set User Error: Unexpected data value' and then an 'Error' connector. If 'No', it goes to 'Unexpected value?'. If 'Yes', it goes to the same 'Set User Error: Unexpected data value' block. If 'No', it goes to an 'OK' connector. + +4752 + +4753 + +Figure 25.2/1: Macro Check\_Indication + +![Flowchart for macrodefinition Check_Confirmation. It starts with an oval connector, followed by a series of decision diamonds: 'Provider error?', 'User error?', 'Data missing?', 'Unexpected data?', and 'Unexpected value?'. 'Yes' paths from 'Provider error?' and 'User error?' lead to a 'MAP_CLOSE_req' block and a 'Provider Error' block. 'Yes' paths from 'Data missing?', 'Unexpected data?', and 'Unexpected value?' lead to a 'Data Error' block. A 'No' path from 'Unexpected value?' leads to an 'OK' connector.](862ff33478042f58ccebd2dda6efa7e8_img.jpg) + +**macrodefinition Check\_Confirmation** **Check\_Cnf1(1)** + +Macro to check the content of a MAP specific service confirmation + +Signals to/from the right are to/from the remote peer entity + +``` + + graph TD + Start([ ]) --> D1{Provider error?} + D1 -- Yes --> MAP_CLOSE_req{{MAP_CLOSE_req}} + D1 -- No --> D2{User error?} + D2 -- Yes --> User_Error(( )) + D2 -- No --> D3{Data missing?} + D3 -- Yes --> Data_Error(( )) + D3 -- No --> D4{Unexpected data?} + D4 -- Yes --> Data_Error + D4 -- No --> D5{Unexpected value?} + D5 -- Yes --> Data_Error + D5 -- No --> OK([OK]) + MAP_CLOSE_req --> Provider_Error(( )) + +``` + +Flowchart for macrodefinition Check\_Confirmation. It starts with an oval connector, followed by a series of decision diamonds: 'Provider error?', 'User error?', 'Data missing?', 'Unexpected data?', and 'Unexpected value?'. 'Yes' paths from 'Provider error?' and 'User error?' lead to a 'MAP\_CLOSE\_req' block and a 'Provider Error' block. 'Yes' paths from 'Data missing?', 'Unexpected data?', and 'Unexpected value?' lead to a 'Data Error' block. A 'No' path from 'Unexpected value?' leads to an 'OK' connector. + +4754 + +4755 + +**Figure 25.2/2: Macro Check\_Confirmation** + +## 4756 25.3 The page and search macros + +### 4757 25.3.1 Macro PAGE\_MSC + +4758 This macro is called if an unstructured SS notification, a network-initiated unstructured SS request or a mobile +4759 terminating short message is to be delivered to the MS and the current location area identity of the MS is known in the +4760 VLR. + +4761 If an MM-connection over the radio link already exists for the given IMSI, the MSC sets the access connection status +4762 according to the characteristics of the existing connection (i.e. RR-connection established, ciphering mode on/off, MM- +4763 connection existing and authenticated or not). + +4764 If the MSC pages the MS and the VLR provided the TMSI, the MSC uses it to identify the MS at the radio interface; +4765 otherwise the MSC uses the IMSI. The MSC also uses the IMSI to determine the page group (see 3GPP TS 24.008 +4766 [35]). + +4767 If the MS responds with a channel request containing an establishment cause which is not "answer to paging" the MSC +4768 sends a MAP\_PAGE response primitive with user error Busy Subscriber. This gives priority to the mobile originating +4769 request. Alternatively, as an implementation option, the MSC may treat this as a response to paging, which gives +4770 priority to the mobile terminating request. + +4771 If the paging is for MT SMS delivery and the VLR aborts the transaction before the MSC receives a response from the +4772 MS, the MSC aborts the transaction with the SMS-GMSC. + +### 4773 25.3.2 Macro Search\_For\_MS\_MSC + +4774 This macro is called if an unstructured SS notification, a network-initiated unstructured SS request or a mobile +4775 terminating short message is to be delivered to the MS and the current location area identity of the MS is not known in +4776 VLR. + +4777 If an MM-connection over the radio link already exists for the given IMSI, the MSC returns a +4778 MAP\_SEARCH\_FOR\_MS response containing the IMSI and current location area identification of the called MS to the +4779 VLR and sets the access connection status according to the characteristics of the existing connection (i.e. RR- +4780 connection established, ciphering mode on/off, MM-connection existing and authenticated or not). + +4781 If the MSC pages the MS, the MSC uses the IMSI to identify the subscriber and the page group (see 3GPP TS 24.008 +4782 [35]). + +4783 If the MS responds with a channel request containing an establishment cause which is not "answer to paging" the MSC +4784 sends a MAP\_SEARCH\_FOR\_MS response with user error Busy Subscriber. This gives priority to the mobile +4785 originating request. Alternatively, as an implementation option, the MSC may treat this as a response to paging, which +4786 gives priority to the mobile terminating request. + +4787 If the paging is for MT SMS delivery and the VLR aborts the transaction before the MSC receives a response from the +4788 MS, the MSC aborts the transaction with the SMS-GMSC. + +![Flowchart for macrodefinition Page_MSC. It starts with MAP_PAGE_ind, checks LAI known, transaction still exists, and MS connection exists. If OK, it sends A_Page_Request and waits for response. If No to any check, it sets user errors (Unknown LAI or System failure) and returns MAP_PAGE_rsp. The Wait_For_Page_Response block leads to various responses: A_Page_Response (OK), A_No_Page_Response (1), A_CM_Service_Request (1), MAP_U_ABORT_ind (Null), and signals from SMS-GMSC (Null).](91243a030cf879636d9526d54e9675e1_img.jpg) + +**macrodefinition Page\_MSC** **Page\_MSC1(1)** + +Macro in the MSC to page an MS for network initiated SS activity or SMS delivery + +Signals to/from the left are to/from the BSS; + signals to/from the right are to/from the VLR + unless marked otherwise + +``` + + graph TD + Start([Start]) --> MAP_PAGE_ind[MAP_PAGE_ind] + MAP_PAGE_ind --> Check_Ind[Check_Indication] + Check_Ind -- OK --> LAI_Known{LAI known?} + Check_Ind -- Error --> Error_Sync(( )) + + LAI_Known -- No --> Set_Error_Unknown[Set User Error: Unknown LAI] + Set_Error_Unknown --> Error_Sync + + LAI_Known -- Yes --> Transaction_Exists{Transaction still exists?} + + Transaction_Exists -- No --> Set_Error_System[Set User Error: System failure] + Set_Error_System --> Error_Sync + + Transaction_Exists -- Yes --> MS_Connection{MS connection exists?} + + MS_Connection -- No --> A_Page_Req{A_Page_Request} + + MS_Connection -- Yes --> Set_Access_Status[Set access connection status] + + A_Page_Req --> Wait_For_Resp[Wait_For_Page_Response] + + Wait_For_Resp --> A_Page_Resp[A_Page_Response] + A_Page_Resp --> Set_Access_Status_1[Set access connection status] + Set_Access_Status_1 --> OK_1((OK)) + + Wait_For_Resp --> A_No_Page_Resp[A_No_Page_Response] + A_No_Page_Resp --> Set_Error_Absent[Set User Error: Absent Subscriber] + Set_Error_Absent --> 1_1((1)) + + Wait_For_Resp --> A_CM_Service_Req[A_CM_Service_Request] + A_CM_Service_Req --> Set_Error_Busy[Set User Error: Busy Subscriber] + Set_Error_Busy --> 1_2((1)) + + Wait_For_Resp --> MAP_U_ABORT_ind[MAP_U_ABORT_ind] + MAP_U_ABORT_ind --> MAP_U_ABORT_req[MAP_U_ABORT_req] + MAP_U_ABORT_req --> To_SMS_GMSC[To SMS-GMSC] + To_SMS_GMSC --> Null_1((Null)) + + Wait_For_Resp --> From_SMS_GMSC[From SMS-GMSC] + From_SMS_GMSC --> MAP_U_ABORT_req_2[MAP_U_ABORT_req] + MAP_U_ABORT_req_2 --> Null_2((Null)) + + Error_Sync --> MAP_PAGE_rsp[MAP_PAGE_rsp] + MAP_PAGE_rsp --> MAP_DELIMITER_req[MAP_DELIMITER_req] + +``` + +Flowchart for macrodefinition Page\_MSC. It starts with MAP\_PAGE\_ind, checks LAI known, transaction still exists, and MS connection exists. If OK, it sends A\_Page\_Request and waits for response. If No to any check, it sets user errors (Unknown LAI or System failure) and returns MAP\_PAGE\_rsp. The Wait\_For\_Page\_Response block leads to various responses: A\_Page\_Response (OK), A\_No\_Page\_Response (1), A\_CM\_Service\_Request (1), MAP\_U\_ABORT\_ind (Null), and signals from SMS-GMSC (Null). + +4789 + +4790 + +Figure 25.3/1: Macro Page\_MSC + +![Flowchart for Search_For_MS_MSC macro. It starts with an entry point, followed by MAP_SEARCH_FOR_MS_ind. A decision 'Check_Indication' leads to 'OK' or 'Error'. 'OK' leads to 'Transaction still exists?'. If 'Yes', it leads to 'MS connection exists?'. If 'Yes', it goes to connector 2. If 'No', it goes to 'A_Page_Request'. 'A_Page_Request' leads to 'Wait_For_Search_Response'. 'Error' from 'Check_Indication' leads to connector 1, then to a merge point. From the merge point, it goes to 'MAP_SEARCH_FOR_MS_rsp' and 'MAP_DELIMITER_req', then to an 'Error' connector. 'Wait_For_Search_Response' leads to a horizontal bus with five branches: 1. 'A_Page_Response' leads to connector 2, then to a merge point for 'MAP_SEARCH_FOR_MS_rsp' and 'MAP_DELIMITER_req', then to 'Set access connection status; Set LAI', ending at 'OK' connector. 2. 'A_No_Page_Response' leads to 'Set User Error: Absent Subscriber', ending at connector 1. 3. 'A_CM_Service_Request' leads to 'Set User Error: Busy Subscriber', ending at connector 1. 4. 'MAP_U_ABORT_ind' leads to 'MAP_U_ABORT_req', which goes 'To SMS-GMSC' (from a 'From SMS-GMSC' note), ending at 'Null' connector. 5. A branch with 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' leads to a merge point, then to 'MAP_U_ABORT_req', ending at 'Null' connector.](8aac418e4cec0201d026975ef91bf912_img.jpg) + +**macrodefinition Search\_For\_MS\_MSC** **Search\_MSC1(1)** + +Macro in the MSC to search for an MS (i.e. page in all location areas) for network initiated SS activity or SMS delivery + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` + + graph TD + Start([ ]) --> MAP_SEARCH_FOR_MS_ind[/MAP_SEARCH_FOR_MS_ind/] + MAP_SEARCH_FOR_MS_ind --> Check_Indication[Check_Indication] + Check_Indication -- OK --> Transaction_exists{Transaction still exists?} + Check_Indication -- Error --> C1((1)) + Transaction_exists -- Yes --> MS_connection{MS connection exists?} + Transaction_exists -- No --> A_Page_Request{A_Page_Request} + MS_connection -- Yes --> C2((2)) + MS_connection -- No --> A_Page_Request + A_Page_Request --> Wait_For_Search_Response([Wait_For_Search_Response]) + C1 --> Merge1(( )) + Merge1 --> MAP_SEARCH_FOR_MS_rsp[/MAP_SEARCH_FOR_MS_rsp/] + Merge1 --> MAP_DELIMITER_req[/MAP_DELIMITER_req/] + MAP_SEARCH_FOR_MS_rsp --> Error((Error)) + Wait_For_Search_Response --> Bus[ ] + Bus --> A_Page_Response[/A_Page_Response/] + Bus --> A_No_Page_Response[/A_No_Page_Response/] + Bus --> A_CM_Service_Request[/A_CM_Service_Request/] + Bus --> MAP_U_ABORT_ind[/MAP_U_ABORT_ind/] + Bus --> MAP_U_ABORT_ind_2[/MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind/] + A_Page_Response --> C2 + C2 --> Merge2(( )) + Merge2 --> MAP_SEARCH_FOR_MS_rsp_2[/MAP_SEARCH_FOR_MS_rsp/] + Merge2 --> MAP_DELIMITER_req_2[/MAP_DELIMITER_req/] + MAP_SEARCH_FOR_MS_rsp_2 --> Set_access[Set access connection status; Set LAI] + Set_access --> OK((OK)) + A_No_Page_Response --> Set_User_Error_Absent[Set User Error: Absent Subscriber] + Set_User_Error_Absent --> C1_1((1)) + A_CM_Service_Request --> Set_User_Error_Busy[Set User Error: Busy Subscriber] + Set_User_Error_Busy --> C1_2((1)) + MAP_U_ABORT_ind --> MAP_U_ABORT_req_1[/MAP_U_ABORT_req/] + MAP_U_ABORT_req_1 --> To_SMS_GMSC[To SMS-GMSC] + From_SMS_GMSC[From SMS-GMSC] -.-> To_SMS_GMSC + MAP_U_ABORT_req_1 --> Null_1((Null)) + MAP_U_ABORT_ind_2 --> Merge3(( )) + Merge3 --> MAP_U_ABORT_req_2[/MAP_U_ABORT_req/] + MAP_U_ABORT_req_2 --> Null_2((Null)) + +``` + +Flowchart for Search\_For\_MS\_MSC macro. It starts with an entry point, followed by MAP\_SEARCH\_FOR\_MS\_ind. A decision 'Check\_Indication' leads to 'OK' or 'Error'. 'OK' leads to 'Transaction still exists?'. If 'Yes', it leads to 'MS connection exists?'. If 'Yes', it goes to connector 2. If 'No', it goes to 'A\_Page\_Request'. 'A\_Page\_Request' leads to 'Wait\_For\_Search\_Response'. 'Error' from 'Check\_Indication' leads to connector 1, then to a merge point. From the merge point, it goes to 'MAP\_SEARCH\_FOR\_MS\_rsp' and 'MAP\_DELIMITER\_req', then to an 'Error' connector. 'Wait\_For\_Search\_Response' leads to a horizontal bus with five branches: 1. 'A\_Page\_Response' leads to connector 2, then to a merge point for 'MAP\_SEARCH\_FOR\_MS\_rsp' and 'MAP\_DELIMITER\_req', then to 'Set access connection status; Set LAI', ending at 'OK' connector. 2. 'A\_No\_Page\_Response' leads to 'Set User Error: Absent Subscriber', ending at connector 1. 3. 'A\_CM\_Service\_Request' leads to 'Set User Error: Busy Subscriber', ending at connector 1. 4. 'MAP\_U\_ABORT\_ind' leads to 'MAP\_U\_ABORT\_req', which goes 'To SMS-GMSC' (from a 'From SMS-GMSC' note), ending at 'Null' connector. 5. A branch with 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' leads to a merge point, then to 'MAP\_U\_ABORT\_req', ending at 'Null' connector. + +4791 + +4792 + +**Figure 25.3/2: Macro Search\_for\_MS\_MSC** + +## 4793 25.4 Macros for handling an Access Request + +4794 These macros are invoked when a MS accesses the network, e.g. to submit an MO short message or when responding to +4795 paging. The macros handle identification and authentication of the mobile subscriber as well as invocation of security +4796 related features (see 3GPP TS 42.009 [6]). + +### 4797 25.4.1 Macro Process\_Access\_Request\_MSC + +4798 Sheet 1: The MAP\_PROCESS\_ACCESS\_REQUEST request includes the following parameters: + +- 4799 - the received subscriber identification (IMSI, TMSI); +- 4800 - the CM service type, indicating the type of request; +- 4801 - the status of the access connection, i.e. whether a connection to this MS already exists and if so, whether it is +4802 already authenticated and ciphered; +- 4803 - the current location area id of the MS; and +- 4804 - the CKSN received from the MS. + +4805 Sheet 2, sheet 3: If the MSC receives an A\_SETUP indication while it is waiting for further instructions from the VLR +4806 or for the acknowledgment of TMSI reallocation from the MS, the MSC saves the setup request for processing after +4807 control has returned from the macro Process\_Access\_Request\_MSC to the calling process. + +4808 Sheet 3: When the MSC is waiting for a possible instruction to allocate a new TMSI, a MAP\_DELIMITER indication +4809 indicates that TMSI reallocation is not required. + +4810 Sheet 3: If the MS sends a TMSI reallocation failure in response to the TMSI reallocation command, the MSC takes the +4811 OK exit; the VLR treats the lack of response as a provider error (see macro Process\_Access\_Request\_VLR). + +### 4812 25.4.2 Macro Process\_Access\_Request\_VLR + +4813 Sheet 3: If the MSC does not send a positive response to the MAP\_FORWARD\_NEW\_TMSI request, this is treated as +4814 a MAP\_FORWARD\_NEW\_TMSI confirmation containing a provider error. The Macro takes the Error exit. If TMSI +4815 reallocation does not succeed, the old TMSI is frozen, to prevent it from being reallocated. In this case, both old and +4816 new TMSIs are regarded as valid. + +### 4817 25.4.3 Macro Obtain\_Identity\_VLR + +4818 This macro is invoked by the macro Process\_Access\_Request\_VLR if the subscriber's identity is not known in the +4819 VLR. + +4820 It is an operator option to allow or prevent retrieval of the IMSI without encryption. + +### 4821 25.4.4 Process Update\_Location\_Child\_VLR + +4822 This process is started when the subscriber successfully accesses the network, e.g. for mobile originated short message +4823 submission, response to paging or supplementary services handling. + +4824 The procedure Notify\_gsmSCF is specified in 3GPP TS 23.078. + +![Sequence diagram for Process_Access_Request_MSC macro. The process starts with a decision 'VLR dialogue exists?'. If 'Yes', it sends 'MAP_PROCESS_ACCESS_REQUEST_req' and 'MAP_DELIMITER_REQ' to the VLR. If 'No', it sends 'MAP_OPEN_REQ', 'MAP_PROCESS_ACCESS_REQUEST_req', and 'MAP_DELIMITER_REQ' to the VLR, then receives a confirmation. Both paths lead to 'Wait_For_PAR_Result'. From there, it branches into 'Trace_Subscriber_Activity_MSC', 'Obtain_IMSI_MSC', and 'Obtain_IMEI_MSC'. 'Obtain_IMSI_MSC' and 'Obtain_IMEI_MSC' lead to 'Wait_For_PAR_Result' on OK and 'Error' on failure. All three lead to a merge point before 'MAP_PROCESS_ACCESS_REQUEST_cnf'. This leads to 'Check Confirmation'. If 'OK', it checks 'Ciphering required'. If 'True', it sends 'A_CIPHER_MODE_COMMAND_req' to the MS. If 'False', it checks 'CM service type= Page response?'. If 'Yes', it sends 'A_CM_SERVICE_ACCEPT_req' to the MS. Both 'A_CIPHER_MODE_COMMAND_req' and 'A_CM_SERVICE_ACCEPT_req' lead to 'Wait_For_TMSI_Reallocation'. If 'Check Confirmation' is not 'OK', it maps the error to a reject cause and sends 'A_CM_SERVICE_REJECT_req' to the MS, leading to 'Error'.](4992b9ef8fd1b4f81f112d70312862fc_img.jpg) + +**macrodefinition Process\_Access\_Request\_MSC** **Proc\_Acc\_Req\_MSC1(3)** + +Macro in the MSC to handle a request from the MS for access for SMS transfer or SS activity + +Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR + +``` + +sequenceDiagram + participant MS + participant VLR + participant MSC + + Note left of MSC: Macro in the MSC to handle a request from the MS for access for SMS transfer or SS activity + Note right of MSC: Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR + + MSC->>VLR: MAP_PROCESS_ACCESS_REQUEST_req, MAP_DELIMITER_REQ + Note right of MSC: VLR dialogue exists? + alt Yes: Proceed to Wait_For_PAR_Result + alt No: Send MAP_OPEN_REQ, MAP_PROCESS_ACCESS_REQUEST_req, MAP_DELIMITER_REQ to VLR + VLR-->>MSC: Receive_Open_Cnf + Note right of MSC: OK + MSC->>VLR: Wait_For_PAR_Result + Note right of MSC: Vr, Error + MSC->>MSC: Trace_Subscriber_Activity_MSC + MSC->>MSC: Obtain_IMSI_MSC + MSC->>MSC: Obtain_IMEI_MSC + Note right of MSC: OK + Note right of MSC: Error + MSC->>MSC: Wait_For_PAR_Result + Note right of MSC: Error + MSC->>MSC: Wait_For_PAR_Result + Note right of MSC: MAP_PROCESS_ACCESS_REQUEST_cnf + MSC->>MSC: Check Confirmation + Note right of MSC: OK + Note right of MSC: User error, Data error + MSC->>MSC: Ciphering required + Note right of MSC: True + Note right of MSC: False + MSC->>MSC: CM service type= Page response? + Note right of MSC: Yes + Note right of MSC: No + MSC->>MS: A_CIPHER_MODE_COMMAND_req + MSC->>MS: A_CM_SERVICE_ACCEPT_req + Note right of MSC: A_CM_SERVICE_REJECT_req + MSC->>MS: Error + MSC->>MSC: Wait_For_TMSI_Reallocation + +``` + +Sequence diagram for Process\_Access\_Request\_MSC macro. The process starts with a decision 'VLR dialogue exists?'. If 'Yes', it sends 'MAP\_PROCESS\_ACCESS\_REQUEST\_req' and 'MAP\_DELIMITER\_REQ' to the VLR. If 'No', it sends 'MAP\_OPEN\_REQ', 'MAP\_PROCESS\_ACCESS\_REQUEST\_req', and 'MAP\_DELIMITER\_REQ' to the VLR, then receives a confirmation. Both paths lead to 'Wait\_For\_PAR\_Result'. From there, it branches into 'Trace\_Subscriber\_Activity\_MSC', 'Obtain\_IMSI\_MSC', and 'Obtain\_IMEI\_MSC'. 'Obtain\_IMSI\_MSC' and 'Obtain\_IMEI\_MSC' lead to 'Wait\_For\_PAR\_Result' on OK and 'Error' on failure. All three lead to a merge point before 'MAP\_PROCESS\_ACCESS\_REQUEST\_cnf'. This leads to 'Check Confirmation'. If 'OK', it checks 'Ciphering required'. If 'True', it sends 'A\_CIPHER\_MODE\_COMMAND\_req' to the MS. If 'False', it checks 'CM service type= Page response?'. If 'Yes', it sends 'A\_CM\_SERVICE\_ACCEPT\_req' to the MS. Both 'A\_CIPHER\_MODE\_COMMAND\_req' and 'A\_CM\_SERVICE\_ACCEPT\_req' lead to 'Wait\_For\_TMSI\_Reallocation'. If 'Check Confirmation' is not 'OK', it maps the error to a reject cause and sends 'A\_CM\_SERVICE\_REJECT\_req' to the MS, leading to 'Error'. + +4825 + +4826 + +Figure 25.4/1 (sheet 1 of 3): Macro Process\_Access\_Request\_MSC + +![State transition diagram for Process_Access_Request_MSC macro. It consists of two main vertical flows. The top flow starts with 'Wait_For_PAR_Result' and branches into 'A_CM_SERVICE_ABORT_ind', 'MAP_SET_CIPHERING_MODE_ind', 'Authenticate_MSC', 'Check_IMEI_MSC', and a merge point. The bottom flow starts with 'Wait_For_TMSI_Reallocation' and branches into 'A_CM_SERVICE_ABORT_ind', 'A_SETUP_ind', 'Authenticate_MSC', 'Check_IMEI_MSC', and a merge point. Both flows include 'Error' states and 'Wait_For_PAR_Result' loops.](9241ae748c6bc391a42f69c9337d18c0_img.jpg) + +**macrodefinition Process\_Access\_Request\_MSC** **Proc\_Acc\_Req\_MSC2(3)** + +Macro in the MSC to handle a request from the MS for access for SMS transfer or SS activity + +Signals to/from the left are to/from the MS; +signals to/from the right are to/from the VLR + +``` + + graph TD + subgraph TopFlow [Top Flow] + WPR1[Wait_For_PAR_Result] --> AC1{A_CM_SERVICE_ABORT_ind} + WPR1 --> M1[MAP_SET_CIPHERING_MODE_ind] + WPR1 --> AM1[Authenticate_MSC] + WPR1 --> CM1[Check_IMEI_MSC] + WPR1 --> Merge1(( )) + AC1 --> MU1[MAP_U_ABORT_req] + MU1 --> E1((Error)) + M1 --> CR1[Ciphering Required:= True] + CR1 --> WPR2[Wait_For_PAR_Result] + AM1 -- OK --> WPR3[Wait_For_PAR_Result] + AM1 -- Error --> E2((Error)) + CM1 -- OK --> WPR4[Wait_For_PAR_Result] + CM1 -- Error --> E2 + Merge1 --> MU2[MAP_U_ABORT_ind, MAP_CLOSE_ind] + MU2 --> AC2{A_CM_SERVICE_REJECT_req} + AC2 --> E3((Error)) + end + + subgraph BottomFlow [Bottom Flow] + WTR[Wait_For_TMSI_Reallocation] --> AC3{A_CM_SERVICE_ABORT_ind} + WTR --> AS[A_SETUP_ind] + WTR --> AM2[Authenticate_MSC] + WTR --> CM2[Check_IMEI_MSC] + WTR --> Merge2(( )) + AC3 --> MU3[MAP_U_ABORT_req] + MU3 --> E4((Error)) + AM2 -- OK --> WPR5[Wait_For_PAR_Result] + AM2 -- Error --> E5((Error)) + CM2 -- OK --> WPR6[Wait_For_PAR_Result] + CM2 -- Error --> E5 + Merge2 --> MU4[MAP_U_ABORT_ind, MAP_CLOSE_ind] + MU4 --> AC4{A_CM_SERVICE_REJECT_req} + AC4 --> E6((Error)) + end + +``` + +State transition diagram for Process\_Access\_Request\_MSC macro. It consists of two main vertical flows. The top flow starts with 'Wait\_For\_PAR\_Result' and branches into 'A\_CM\_SERVICE\_ABORT\_ind', 'MAP\_SET\_CIPHERING\_MODE\_ind', 'Authenticate\_MSC', 'Check\_IMEI\_MSC', and a merge point. The bottom flow starts with 'Wait\_For\_TMSI\_Reallocation' and branches into 'A\_CM\_SERVICE\_ABORT\_ind', 'A\_SETUP\_ind', 'Authenticate\_MSC', 'Check\_IMEI\_MSC', and a merge point. Both flows include 'Error' states and 'Wait\_For\_PAR\_Result' loops. + +4827 + +4828 + +**Figure 25.4/1 (sheet 2 of 3): Macro Process\_Access\_Request\_MSC** + +![Sequence diagram for Process_Access_Request_MSC. The process starts with 'Wait_For_TMSI_Reallocation', followed by a merge point. From the merge point, one path goes left through 'MAP_DELIMITER_ind' to an 'OK' terminal. The other path goes right through 'MAP_FORWARD_NEW_TMSI_ind' to 'A_TMSI_REALLOC_CMD_req', then 'Wait_For_TMSI_Ack'. From 'Wait_For_TMSI_Ack', the path splits into five branches: 1) 'A_CM_SERVICE_ABORT_ind' leads to 'MAP_U_ABORT_req' and an 'Error' terminal. 2) 'A_TMSI_REALLOC_COMPLETE_ind' leads to a merge point, then 'MAP_FORWARD_NEW_TMSI_rsp' and 'MAP_DELIMITER_req', ending at an 'OK' terminal. 3) 'A_TMSI_REALLOC_FAILURE_ind' leads to an 'OK' terminal. 4) 'A_SETUP_ind' is a standalone path. 5) A merge point leads to 'MAP_U_ABORT_ind, MAP_CLOSE_ind', then 'A_CM_SERVICE_REJECT_req', ending at an 'Error' terminal.](220a56aa2a8455e5a0dba15a4acd596d_img.jpg) + +**macrodefinition Process\_Access\_Request\_MSC** **Proc\_Acc\_Req\_MSC3(3)** + +Macro in the MSC to handle a request from the MS for access for SMS transfer or SS activity + +Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + + Note left of MSC: Macro in the MSC to handle a request from the MS for access for SMS transfer or SS activity + Note right of MSC: Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR + + MSC->>MS: Wait_For_TMSI_Reallocation + Note right of MSC: + MSC->>VLR: MAP_FORWARD_NEW_TMSI_ind + Note left of MSC: + MSC->>MS: MAP_DELIMITER_ind + Note left of MSC: OK + Note right of MSC: + MSC->>MS: A_TMSI_REALLOC_CMD_req + Note right of MSC: + MSC->>MS: Wait_For_TMSI_Ack + Note right of MSC: + MSC->>MS: A_CM_SERVICE_ABORT_ind + Note left of MSC: + MSC->>VLR: MAP_U_ABORT_req + Note left of MSC: Error + Note right of MSC: + MSC->>MS: A_TMSI_REALLOC_COMPLETE_ind + Note right of MSC: + Note right of MSC: + MSC->>VLR: MAP_FORWARD_NEW_TMSI_rsp + MSC->>VLR: MAP_DELIMITER_req + Note right of MSC: OK + Note right of MSC: + MSC->>MS: A_TMSI_REALLOC_FAILURE_ind + Note left of MSC: OK + Note right of MSC: + MSC->>MS: A_SETUP_ind + Note right of MSC: + Note right of MSC: + MSC->>VLR: MAP_U_ABORT_ind, MAP_CLOSE_ind + Note right of MSC: + MSC->>MS: A_CM_SERVICE_REJECT_req + Note left of MSC: Error + +``` + +Sequence diagram for Process\_Access\_Request\_MSC. The process starts with 'Wait\_For\_TMSI\_Reallocation', followed by a merge point. From the merge point, one path goes left through 'MAP\_DELIMITER\_ind' to an 'OK' terminal. The other path goes right through 'MAP\_FORWARD\_NEW\_TMSI\_ind' to 'A\_TMSI\_REALLOC\_CMD\_req', then 'Wait\_For\_TMSI\_Ack'. From 'Wait\_For\_TMSI\_Ack', the path splits into five branches: 1) 'A\_CM\_SERVICE\_ABORT\_ind' leads to 'MAP\_U\_ABORT\_req' and an 'Error' terminal. 2) 'A\_TMSI\_REALLOC\_COMPLETE\_ind' leads to a merge point, then 'MAP\_FORWARD\_NEW\_TMSI\_rsp' and 'MAP\_DELIMITER\_req', ending at an 'OK' terminal. 3) 'A\_TMSI\_REALLOC\_FAILURE\_ind' leads to an 'OK' terminal. 4) 'A\_SETUP\_ind' is a standalone path. 5) A merge point leads to 'MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind', then 'A\_CM\_SERVICE\_REJECT\_req', ending at an 'Error' terminal. + +4829 + +4830 + +**Figure 25.4/1 (sheet 3 of 3): Macro Process\_Access\_Request\_MSC** + +![Flowchart for Process_Access_Request_VLR macro. It starts with an entry point, receives a MAP_PROCESS_ACCESS_REQUEST_ind, checks the indication, and then branches based on whether the identity is known and if authentication is required. It handles various error cases like system failure, illegal subscriber, or unidentified subscriber, and finally sends a response.](d63ed85b030c766b96f0c01ec86f5868_img.jpg) + +**macrodefinition Process\_Access\_Request\_VLR** **Proc\_Acc\_Req\_VLR1(3)** + +Macro in the VLR to handle a request from the MS for access for SMS transfer or SS activity + +Signals to/from the left are to/from the MSC + +``` + + graph TD + Entry([ ]) --> Input{{ }} + Input -- "MAP_PROCESS_ACCESS_REQUEST_ind" --> Check[Check_Indication] + Check --> IdentityKnown{Identity known?} + IdentityKnown -- No --> Obtain[Obtain Identity_VLR] + Obtain --> Error1((Error)) + Obtain -- OK --> IdentityIMEI{Identity=IMEI?} + IdentityKnown -- Yes --> IdentityIMEI + IdentityIMEI -- No --> AuthRequired{Authentication required?} + IdentityIMEI -- Yes --> Exit2((2)) + AuthRequired -- No --> SystemFailure[Set User Error: System Failure] + SystemFailure --> Exit2 + AuthRequired -- Yes --> Authenticate[Authenticate_VLR] + Authenticate -- "OK" --> Exit2 + Authenticate -- "Procedure_Error" --> SystemFailure + SystemFailure --> Exit2 + Authenticate -- "Illegal_Subscriber" --> Illegal[Set User Error: Illegal subscriber] + Illegal --> Exit2 + Authenticate -- "Aborted" --> Error2((Error)) + Authenticate -- "Unknown_Subscriber, Unidentified_Subscriber" --> Unidentified[Set User Error: Unidentified subscriber] + Unidentified --> Exit2 + Exit2 --> Output{{ }} + Output -- "MAP_PROCESS_ACCESS_REQUEST_rsp +MAP_CLOSE_req" --> Error3((Error)) + +``` + +Flowchart for Process\_Access\_Request\_VLR macro. It starts with an entry point, receives a MAP\_PROCESS\_ACCESS\_REQUEST\_ind, checks the indication, and then branches based on whether the identity is known and if authentication is required. It handles various error cases like system failure, illegal subscriber, or unidentified subscriber, and finally sends a response. + +4831 + +4832 + +**Figure 25.4/2 (sheet 1 of 3): Macro Process\_Access\_Request\_VLR** + +# macrodefinition Process\_Access\_Request\_VLR + +Proc\_Acc\_Req\_VLR2(3) + +Macro in the VLR to handle a request from the MS for access for SMS transfer or SS activity + +Signals to/from the left are to/from the MSC + +![Flowchart for Process_Access_Request_VLR macro. It starts at connector 2, checks radio contact, location info, subscriber data, roaming status, IMSI status, mobile reachability, tracing, and ciphering requirements, leading to connectors 1, 3, and 4.](7017f0dbe12b3cef766e7453972aed37_img.jpg) + +``` + +graph TD + 2((2)) --> C1[Confirmed by radio contact:=True] + C1 --> D1{ } + D1 -- Yes --> D2{Location info confirmed in HLR?} + D1 -- No --> P1[Update_Location_Child_VLR] + P1 --> D3{Subscriber data confirmed by HLR?} + D3 -- Yes --> D4{Roaming allowed in current LA?} + D3 -- No --> E1[Set User Error: Unidentified subscriber] + D4 -- Yes --> P2[IMSI detached:=False] + D4 -- No --> E2[Set User Error: Roaming not allowed in this LA] + P2 --> D5{Mobile Not Reachable Flag set?} + D5 -- Yes --> P3[Subscriber_Present_VLR] + P3 --> D6{Tracing required?} + D6 -- Yes --> P4[Trace_Subscriber_Activity_VLR] + P4 --> D7{Ciphering required?} + D7 -- Yes --> O1{{MAP_SET_CIPHERING_MODE_req +MAP_DELIMITER_req}} + O1 --> 3((3)) + D7 -- No --> 4((4)) + E1 --> 1((1)) + E2 --> 1 + +``` + +Flowchart for Process\_Access\_Request\_VLR macro. It starts at connector 2, checks radio contact, location info, subscriber data, roaming status, IMSI status, mobile reachability, tracing, and ciphering requirements, leading to connectors 1, 3, and 4. + +4833 + +4834 + +Figure 25.4/2 (sheet 2 of 3): Macro Process\_Access\_Request\_VLR + +macrodefinition Process\_Access\_Request\_VLR + +Proc\_Acc\_Req\_VLR3(3) + +Macro in the VLR to handle a request from the MS for access for SMS transfer or SS activity + +Signals to/from the left are to/from the MSC + +![Flowchart for Process_Access_Request_VLR macro. It starts at connector 3, checks if IMEI check is required. If yes, it calls Check_IMEI_VLR. If no, it proceeds to Identity:= IMSI. Both paths lead to a decision diamond. If 'TMSI reallocation required?' is Yes, it calls MAP_FORWARD_NEW_TMSI_req, Freeze old TMSI, Wait_For_TMSI_Ack, and then Check_Confirmation. If No, it goes to OK connector. If 'IMEI check required?' is No (from connector 4), it also proceeds to Identity:= IMSI. If 'IMEI check required?' is Yes, it calls Check_IMEI_VLR. Both paths from connector 4 lead to a decision diamond. If 'Error' or 'Aborted' from Check_IMEI_VLR, it sets IMSI detached:= True and Set User Error: Illegal equipment, then goes to connector 1. If 'OK', it proceeds to Identity:= IMSI. From Identity:= IMSI, it calls MAP_PROCESS_ACCESS_REQUEST_rsp and MAP_DELIMITER_req, then goes to OK connector. From Check_Confirmation, if 'Provider Error', it goes to Error connector. If 'User Error, Data Error', it goes to OK connector. If 'OK', it calls Unfreeze old TMSI and goes to OK connector.](ec13be3d306e581971b0f30add6c4241_img.jpg) + +``` + +graph TD + 3((3)) --> D1{IMEI check required?} + D1 -- No --> I1[Identity:= IMSI] + D1 -- Yes --> C1[Check_IMEI_VLR] + C1 -- Error --> ID1[IMSI detached:= True] + ID1 --> UE1[Set User Error: Illegal equipment] + UE1 --> 1_1((1)) + C1 -- Aborted --> E1((Error)) + C1 -- OK --> I1 + I1 --> D2{TMSI reallocation required?} + D2 -- Yes --> M1[MAP_FORWARD_NEW_TMSI_req +MAP_DELIMITER_req] + M1 --> F[Freeze old TMSI] + F --> W[Wait_For_TMSI_Ack] + W --> C2[Check_Confirmation] + D2 -- No --> OK_1((OK)) + 4((4)) --> D3{IMEI check required?} + D3 -- No --> I2[Identity:= IMSI] + D3 -- Yes --> C3[Check_IMEI_VLR] + C3 -- Error --> ID2[IMSI detached:= True] + ID2 --> UE2[Set User Error: Illegal equipment] + UE2 --> 1_2((1)) + C3 -- Aborted --> E2((Error)) + C3 -- OK --> I2 + I2 --> D4{TMSI reallocation required?} + D4 -- Yes --> M2[MAP_FORWARD_NEW_TMSI_req +MAP_DELIMITER_req] + M2 --> F2[Freeze old TMSI] + F2 --> W2[Wait_For_TMSI_Ack] + W2 --> C3_2[Check_Confirmation] + D4 -- No --> OK_2((OK)) + I2 --> M3[MAP_PROCESS_ACCESS_REQUEST_rsp +MAP_DELIMITER_req] + M3 --> OK_3((OK)) + C2 -- "Provider Error" --> E3((Error)) + C2 -- "User Error, Data Error" --> OK_4((OK)) + C2 -- OK --> U[Unfreeze old TMSI] + U --> OK_5((OK)) + +``` + +Flowchart for Process\_Access\_Request\_VLR macro. It starts at connector 3, checks if IMEI check is required. If yes, it calls Check\_IMEI\_VLR. If no, it proceeds to Identity:= IMSI. Both paths lead to a decision diamond. If 'TMSI reallocation required?' is Yes, it calls MAP\_FORWARD\_NEW\_TMSI\_req, Freeze old TMSI, Wait\_For\_TMSI\_Ack, and then Check\_Confirmation. If No, it goes to OK connector. If 'IMEI check required?' is No (from connector 4), it also proceeds to Identity:= IMSI. If 'IMEI check required?' is Yes, it calls Check\_IMEI\_VLR. Both paths from connector 4 lead to a decision diamond. If 'Error' or 'Aborted' from Check\_IMEI\_VLR, it sets IMSI detached:= True and Set User Error: Illegal equipment, then goes to connector 1. If 'OK', it proceeds to Identity:= IMSI. From Identity:= IMSI, it calls MAP\_PROCESS\_ACCESS\_REQUEST\_rsp and MAP\_DELIMITER\_req, then goes to OK connector. From Check\_Confirmation, if 'Provider Error', it goes to Error connector. If 'User Error, Data Error', it goes to OK connector. If 'OK', it calls Unfreeze old TMSI and goes to OK connector. + +4835 + +4836 + +Figure 25.4/2 (sheet 3 of 3): Macro Process\_Access\_Request\_VLR + +macrodefinition Obtain\_Identity\_VLR + +Obt\_ID\_VLR1(1) + +Macro in the VLR to obtain a useable identity of the MS + +![Flowchart for Obtain_Identity_VLR macro. It starts with an oval connector, followed by a decision 'Identity= IMSI?'. If 'Yes', it goes to an 'Error' terminal. If 'No', it goes to another decision 'Retrieval of IMSI allowed?'. If 'No', it goes to an 'Error' terminal. If 'Yes', it goes to a process 'Obtain IMSI_VLR'. From there, it goes to a decision 'IMSI known?'. If 'No', it goes to an 'Error' terminal. If 'Yes', it goes to an 'OK' terminal. If 'Aborted', it goes to an 'Aborted' terminal.](cec3bc41df2df61b9f95d88c0bf7ad99_img.jpg) + +``` +graph TD; Start([ ]) --> D1{Identity= IMSI?}; D1 -- Yes --> Error1((Error)); D1 -- No --> D2{Retrieval of IMSI allowed?}; D2 -- No --> Error2((Error)); D2 -- Yes --> P1[Obtain IMSI_VLR]; P1 -- OK --> D3{IMSI known?}; P1 -- Error --> Error3((Error)); P1 -- Aborted --> Aborted((Aborted)); D3 -- No --> Error4((Error)); D3 -- Yes --> OK((OK)); +``` + +Flowchart for Obtain\_Identity\_VLR macro. It starts with an oval connector, followed by a decision 'Identity= IMSI?'. If 'Yes', it goes to an 'Error' terminal. If 'No', it goes to another decision 'Retrieval of IMSI allowed?'. If 'No', it goes to an 'Error' terminal. If 'Yes', it goes to a process 'Obtain IMSI\_VLR'. From there, it goes to a decision 'IMSI known?'. If 'No', it goes to an 'Error' terminal. If 'Yes', it goes to an 'OK' terminal. If 'Aborted', it goes to an 'Aborted' terminal. + +4837 + +4838 + +Figure 25.4/3: Macro Obtain\_Identity\_VLR + +![Flowchart for Update_Location_Child_VLR process. It starts with a decision 'HLR address known?'. If 'No', it goes to 'Delete subscriber record'. If 'Yes', it sends MAP requests (OPEN_req, UPDATE_LOCATION_req, DELIMITER_req), receives Open_Cnf, and performs a MAP_Vr dialogue. The Result can be OK, Procedure Error/Aborted, or Unknown Subscriber/ Roaming Not Allowed. OK leads to 'Set Event met: Location update to other VLR', 'Notify_gsmSCF' (referencing 3GPP TS 23.078), and then a 'Wait_For_HLR_Response'. Procedure Error/Aborted and Unknown Subscriber/ Roaming Not Allowed both lead to 'Delete subscriber record'. From the first 'Wait_For_HLR_Response', it branches to 'Activate_Tracing_VLR', 'Insert_Subs_Data_VLR', 'MAP_NOTICE_ind', and a merge point. 'Activate_Tracing_VLR' and 'Insert_Subs_Data_VLR' lead to their own 'Wait_For_HLR_Response' blocks. 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req', which leads to a merge point. The merge point leads to a block with 'Subscriber data confirmed by HLR:=False' and 'Location information confirmed in HLR:=False', which then leads to another 'Wait_For_HLR_Response' block.](9fb3b9417f90b681f29dba5f20344645_img.jpg) + +**process Update\_Location\_Child\_VLR** **ULC\_VLR1(2)** + +Child process in the VLR to update the location information in the HLR + +Signals to/from the right are to/from the HLR + +``` + +graph TD + Start([ ]) --> HLR_Known{HLR address known?} + HLR_Known -- No --> Delete_1[Delete subscriber record] + HLR_Known -- Yes --> MAP_Req[MAP_OPEN_req +MAP_UPDATE_LOCATION_req +MAP_DELIMITER_req] + MAP_Req --> Open_Cnf[Receive Open_Cnf] + Open_Cnf -- Vr --> MAP_Vr[Perform MAP_Vr dialogue] + Open_Cnf -- Error --> X1((X)) + Open_Cnf -- OK --> Wait_1[Wait_For_HLR_Response] + MAP_Vr --> Result{Result} + Result -- OK --> Set_Event[Set Event met: +Location update to other VLR] + Set_Event --> Notify[Notify_gsmSCF] + Notify -.-> Ref[See 3GPP TS 23.078] + Notify --> X2((X)) + Result -- "Procedure Error, Aborted" --> X3((X)) + Result -- "Unknown Subscriber, +Roaming Not Allowed" --> Delete_2[Delete subscriber record] + Delete_2 --> X4((X)) + X2 --> Wait_2[Wait_For_HLR_Response] + Wait_2 --> Activate[Activate_Tracing_VLR] + Wait_2 --> Insert[Insert_Subs_Data_VLR] + Wait_2 --> Notice[MAP_NOTICE_ind] + Wait_2 --> Merge(( )) + Activate --> Wait_3[Wait_For_HLR_Response] + Insert --> Wait_4[Wait_For_HLR_Response] + Notice --> Close[MAP_CLOSE_req] + Close --> Merge + Merge --> Confirmed[Subscriber data confirmed by HLR:=False +Location information confirmed in HLR:=False] + Confirmed --> Wait_5[Wait_For_HLR_Response] + +``` + +Flowchart for Update\_Location\_Child\_VLR process. It starts with a decision 'HLR address known?'. If 'No', it goes to 'Delete subscriber record'. If 'Yes', it sends MAP requests (OPEN\_req, UPDATE\_LOCATION\_req, DELIMITER\_req), receives Open\_Cnf, and performs a MAP\_Vr dialogue. The Result can be OK, Procedure Error/Aborted, or Unknown Subscriber/ Roaming Not Allowed. OK leads to 'Set Event met: Location update to other VLR', 'Notify\_gsmSCF' (referencing 3GPP TS 23.078), and then a 'Wait\_For\_HLR\_Response'. Procedure Error/Aborted and Unknown Subscriber/ Roaming Not Allowed both lead to 'Delete subscriber record'. From the first 'Wait\_For\_HLR\_Response', it branches to 'Activate\_Tracing\_VLR', 'Insert\_Subs\_Data\_VLR', 'MAP\_NOTICE\_ind', and a merge point. 'Activate\_Tracing\_VLR' and 'Insert\_Subs\_Data\_VLR' lead to their own 'Wait\_For\_HLR\_Response' blocks. 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req', which leads to a merge point. The merge point leads to a block with 'Subscriber data confirmed by HLR:=False' and 'Location information confirmed in HLR:=False', which then leads to another 'Wait\_For\_HLR\_Response' block. + +4839 + +4840 + +**Figure 25.4/4 (sheet 1 of 2): Process Update\_Location\_Child\_VLR** + +![Flowchart for Update_Location_Child_VLR process. It starts with 'Wait_For_HLR_Response', followed by 'MAP_UPDATE_LOCATION_cnf' input. Then 'Check_Confirmation' block. From there, three paths: 'OK' leads to 'Subscriber data confirmed by HLR:=True; Location information confirmed in HLR:=True' then 'Set Event met: Location update to other VLR' then 'Notify_gsmSCF' (see 3GPP TS 23.078); 'User Error' leads to a decision diamond; 'Provider Error, Data Error' leads to 'Subscriber data confirmed by HLR:=False; Location information confirmed in HLR:=False'. The 'User error' diamond has 'Else' (leads to 'Delete subscriber record') and 'Roaming Not Allowed, Unknown Subscriber' (leads to 'Subscriber data confirmed by HLR:=False; Location information confirmed in HLR:=False'). All terminal paths end with an 'X' symbol.](4f52ec26fe6cc02317dc1e3374476a1b_img.jpg) + +**process Update\_Location\_Child\_VLR** **ULC\_VLR2(2)** + +Child process in the VLR to update the location information in the HLR + +Signals from the right are from the HLR + +``` + +graph TD + Start([Wait_For_HLR_Response]) --> Input{ } + Input -- "MAP_UPDATE_LOCATION_cnf" --> Input + Input --> Check[Check_Confirmation] + Check -- "OK" --> OK[ ] + OK --> OK_Data["Subscriber data confirmed by HLR:=True; +Location information confirmed in HLR:=True"] + OK_Data --> SetEvent["Set Event met: +Location update to other VLR"] + SetEvent --> Notify["Notify_gsmSCF"] + Notify --> NotifyRef["See 3GPP TS 23.078"] + Notify --> EndX1[X] + Check -- "User Error" --> UserError{User error} + UserError -- "Else" --> Delete["Delete subscriber record"] + Delete --> EndX2[X] + UserError -- "Roaming Not Allowed, Unknown Subscriber" --> ErrorData["Subscriber data confirmed by HLR:=False; +Location information confirmed in HLR:=False"] + ErrorData --> EndX3[X] + Check -- "Provider Error, Data Error" --> ProviderError[ ] + ProviderError --> ProviderErrorData["Subscriber data confirmed by HLR:=False; +Location information confirmed in HLR:=False"] + ProviderErrorData --> EndX4[X] + +``` + +Flowchart for Update\_Location\_Child\_VLR process. It starts with 'Wait\_For\_HLR\_Response', followed by 'MAP\_UPDATE\_LOCATION\_cnf' input. Then 'Check\_Confirmation' block. From there, three paths: 'OK' leads to 'Subscriber data confirmed by HLR:=True; Location information confirmed in HLR:=True' then 'Set Event met: Location update to other VLR' then 'Notify\_gsmSCF' (see 3GPP TS 23.078); 'User Error' leads to a decision diamond; 'Provider Error, Data Error' leads to 'Subscriber data confirmed by HLR:=False; Location information confirmed in HLR:=False'. The 'User error' diamond has 'Else' (leads to 'Delete subscriber record') and 'Roaming Not Allowed, Unknown Subscriber' (leads to 'Subscriber data confirmed by HLR:=False; Location information confirmed in HLR:=False'). All terminal paths end with an 'X' symbol. + +4841 + +4842 + +**Figure 25.4/4 (sheet 2 of 2): Process Update\_Location\_Child\_VLR** + +## 4843 25.5 Authentication macros and processes + +4844 The following macros are used in the network in order to enable authentication of a mobile subscriber. + +### 4845 25.5.1 Macro Authenticate\_MSC + +4846 This macro is used by the MSC to relay a request for authentication transparently from the VLR to the MS, wait for a +4847 response from the MS and relay the response from the MS back to the VLR. + +### 4848 25.5.2 Macro Authenticate\_VLR + +4849 This macro is used by the VLR to control the authentication of a subscriber. + +4850 Sheet 1: The test "Received SRES=Expected SRES" indicates: + +4851 - a comparison of the Signed RESult received from the MS with the Signed RESult received from the HLR, if +4852 GSM authentication is used (see 3GPP TS 43.020 [24]), or + +4853 - a comparison of the RESult received from the MS with the expected RESult received from the HLR, if UMTS +4854 authentication is used (see 3GPP TS 33.102). + +### 4855 25.5.3 Macro Obtain\_Authent\_Params\_VLR + +4856 This macro is used by the VLR to request authentication vectors from the HLR. + +4857 Sheet 1, sheet 2, sheet 3: It is an operator option whether to allow the re-use of old authentication triplets. + +4858 Sheet 2, sheet 3: Old UMTS quintuplets shall not be re-used. + +4859 Sheet 2: if the VLR requests more authentication vectors in the same dialogue, the subsequent +4860 MAP\_SEND\_AUTHENTIFICATION\_INFO request has no parameters. + +### 4861 25.5.4 Process Obtain\_Authentication\_Sets\_VLR + +4862 This process is initiated by the VLR to fetch authentication vectors from a subscriber's HLR independently of any other +4863 processing. + +### 4864 25.5.5 Process Obtain\_Authent\_Sets\_SGSN + +4865 The procedure for authentication when the serving node is an SGSN is described in 3GPP TS 23.060 [104] and 3GPP +4866 TS 24.008 [35]. + +4867 This Process is used by the SGSN to request authentication vectors from the HLR. + +4868 Sheet 1, sheet 2: It is an operator option whether to allow the re-use of old authentication triplets. + +4869 Sheet 2: Old UMTS quintuplets shall not be re-used. + +### 4870 25.5.6 Process Obtain\_Authent\_Sets\_HLR + +4871 This process is used to provide authentication vectors (triplets or quintuplets) in response to a request from a VLR or an +4872 SGSN. + +4873 Upon receipt of an authentication information request for a UMTS subscriber, the HLR shall return authentication +4874 quintuplets. If the user is a GSM subscriber, the HLR shall return authentication triplets. + +4875 **25.5.7 Authentication Failure Reporting** + +4876 **25.5.7.1 General** + +4877 The Authentication Failure Report procedure is used to notify an HLR about the occurrence of an authentication failure +4878 in the SGSN or VLR. + +4879 The message flows for this procedure are shown in figures 25.5/7& 25.5/8. + +![Sequence diagram showing message flow between VLR and HLR. The VLR sends a MAP_AUTHENTICATION_FAILURE_REPORT to the HLR, and the HLR responds with a MAP_AUTHENTICATION_FAILURE_REPORT_ACK.](22200464a296d1f8d3937a49864455e0_img.jpg) + +``` +sequenceDiagram + participant VLR + participant HLR + Note right of VLR: MAP_AUTHENTICATION_FAILURE_REPORT + VLR->>HLR: MAP_AUTHENTICATION_FAILURE_REPORT + Note right of HLR: MAP_AUTHENTICATION_FAILURE_REPORT_ACK + HLR->>VLR: MAP_AUTHENTICATION_FAILURE_REPORT_ACK +``` + +Sequence diagram showing message flow between VLR and HLR. The VLR sends a MAP\_AUTHENTICATION\_FAILURE\_REPORT to the HLR, and the HLR responds with a MAP\_AUTHENTICATION\_FAILURE\_REPORT\_ACK. + +4880 + +4881 + +**Figure 25.5/7: Message Flow for Authentication Failure Report – VLR to HLR** + +![Sequence diagram showing message flow between SGSN and HLR. The SGSN sends a MAP_AUTHENTICATION_FAILURE_REPORT to the HLR, and the HLR responds with a MAP_AUTHENTICATION_FAILURE_REPORT_ACK.](1d272c631c1e0794a8ba1a9523049d28_img.jpg) + +``` +sequenceDiagram + participant SGSN + participant HLR + Note right of SGSN: MAP_AUTHENTICATION_FAILURE_REPORT + SGSN->>HLR: MAP_AUTHENTICATION_FAILURE_REPORT + Note right of HLR: MAP_AUTHENTICATION_FAILURE_REPORT_ACK + HLR->>SGSN: MAP_AUTHENTICATION_FAILURE_REPORT_ACK +``` + +Sequence diagram showing message flow between SGSN and HLR. The SGSN sends a MAP\_AUTHENTICATION\_FAILURE\_REPORT to the HLR, and the HLR responds with a MAP\_AUTHENTICATION\_FAILURE\_REPORT\_ACK. + +4882 + +4883 + +**Figure 25.5/8: Message Flow for Authentication Failure Report – SGSN to HLR** + +4884 **25.5.7.2 Process in the VLR** + +4885 **25.5.7.3 Process in the SGSN** + +4886 **25.5.7.4 Process in the HLR** + +![SDL diagram for Authenticate_MSC macro. It shows the logic flow for handling authentication between MS and VLR, including state transitions and signal exchanges.](6de86797fa3956088bc69c8c5ea7c4fb_img.jpg) + +macrodefinition Authenticate\_MSC + +Auth\_MSC1(1) + +Macro in the MSC to relay the signalling for authentication between the MS and the VLR + +Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR + +``` + + graph TD + Start([ ]) --> Input1[/MAP_AUTHENTICATE_ind/] + Input1 --> Task1[Check_Indication] + Task1 --> Decision1{ } + Decision1 -- OK --> Output1[A_AUTHENTICATE_req] + Decision1 -- Error --> Output2[MAP_AUTHENTICATE_rsp +MAP_DELIMITER_req] + Output2 --> OK_End1((OK)) + Output1 --> State1{{Wait_For_MS_Response}} + + State1 --> Input2[/A_AUTHENTICATE_cnf/] + Input2 --> Decision2{Error?} + Decision2 -- Yes --> Task2[Set User Error] + Decision2 -- No --> Join1 + Task2 --> Join1 + Join1 --> Output3[MAP_AUTHENTICATE_rsp +MAP_DELIMITER_req] + Output3 --> OK_End2((OK)) + + State1 --> Input3[/A_CM_SERVICE_ABORT_ind/] + Input3 --> Output4[MAP_U_ABORT_req] + Output4 --> Error_End1((Error)) + + State1 --> Input4[/MAP_U_ABORT_ind +MAP_CLOSE_ind/] + Input4 --> Error_End2((Error)) + +``` + +SDL diagram for Authenticate\_MSC macro. It shows the logic flow for handling authentication between MS and VLR, including state transitions and signal exchanges. + +4887 + +4888 + +**Figure 25.5/1: Macro Authenticate\_MSC** + +![Flowchart for macrodefinition Authenticate_VLR. It starts at connector '2', checks if authentication vectors are available. If no, it obtains parameters from VLR. Then it sends MAP_AUTHENTICATE_req and MAP_DELIMITER_req. It waits for a response from MSC. If the response is Null, OK, Unknown_Subscriber, or Procedure_Error, it handles each accordingly. For OK, it checks the confirmation. If OK, it checks if received SRES equals expected SRES. If yes, it checks if more authentication vectors are required. If no, it ends at connector '1'. If yes, it obtains authentication sets from VLR and loops back to connector '2'. If received SRES does not equal expected SRES, it ends at connector '1'. If confirmation is not OK, it sends MAP_U_ABORT_ind, MAP_CLOSE_ind, and ends at connector '1'. Other responses (Null, Unknown_Subscriber, Procedure_Error) lead to their respective end states.](091c1ab9163076c6e911f6fd33219793_img.jpg) + +**macrodefinition Authenticate\_VLR** **Auth\_VLR1(2)** + +Macro in the VLR to authenticate an MS + +Signals to/from the left are to/from the MSC + +``` + +graph TD + Start((2)) --> Decision1{Authentication vectors available?} + Decision1 -- No --> Process1[Obtain_Authent_Params_VLR] + Process1 --> Decision2{ } + Decision2 -- Null --> EndNull1((Null)) + Decision2 -- OK --> Process2[MAP_AUTHENTICATE_req +MAP_DELIMITER_req] + Decision2 -- Unknown_Subscriber --> EndUnknown((Unknown_Subscriber)) + Decision2 -- Procedure_Error --> EndProcedure((Procedure_Error)) + Process2 --> Process3[Wait_For_Response_From_MSC] + Process3 --> Decision3{ } + Decision3 -- User Error, Provider Error, Data Error --> End1((1)) + Decision3 -- MAP_U_ABORT_ind, MAP_CLOSE_ind --> EndNull2((Null)) + Decision3 -- MAP_AUTHENTICATE_cnf --> Process4[Check_Confirmation] + Process4 -- OK --> Decision4{Received SRES=Expected SRES?} + Decision4 -- No --> End1 + Decision4 -- Yes --> Decision5{More authentication vectors required?} + Decision5 -- No --> End1 + Decision5 -- Yes --> Process5[Obtain_Authent_Sets_VLR] + Process5 --> EndOK((OK)) + EndOK --> Start + +``` + +Flowchart for macrodefinition Authenticate\_VLR. It starts at connector '2', checks if authentication vectors are available. If no, it obtains parameters from VLR. Then it sends MAP\_AUTHENTICATE\_req and MAP\_DELIMITER\_req. It waits for a response from MSC. If the response is Null, OK, Unknown\_Subscriber, or Procedure\_Error, it handles each accordingly. For OK, it checks the confirmation. If OK, it checks if received SRES equals expected SRES. If yes, it checks if more authentication vectors are required. If no, it ends at connector '1'. If yes, it obtains authentication sets from VLR and loops back to connector '2'. If received SRES does not equal expected SRES, it ends at connector '1'. If confirmation is not OK, it sends MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind, and ends at connector '1'. Other responses (Null, Unknown\_Subscriber, Procedure\_Error) lead to their respective end states. + +4889 + +4890 + +**Figure 25.5/2 (sheet 1 of 2): Macro Authenticate\_VLR** + +![Flowchart for Authenticate_VLR macro. It starts at node 1, checks if Identity=IMSI. If No, it checks if Retry with IMSI? If Yes, it obtains IMSI_VLR. If No, it goes to a merge point. From Obtain IMSI_VLR, if OK, it checks if IMSI known? If No, it leads to Unidentified_subscriber. If Yes, it checks if IMSI matches TMSI? If Yes, it goes to a merge point. If No, it sets Identity=IMSI and goes to node 2. From Obtain IMSI_VLR, if Error, it leads to Procedure_Error. If Aborted, it leads to Null. Both merge points lead to a common exit node associated with Illegal_Subscriber.](f421b56e7f2a6a91f8056e79402e3e8b_img.jpg) + +macrodefinition Authenticate\_VLR + +Auth\_VLR2(2) + +Macro in the VLR to authenticate an MS + +``` + + graph TD + 1((1)) --> D1{Identity=IMSI?} + D1 -- Yes --> Merge1(( )) + D1 -- No --> D2{Retry with IMSI?} + D2 -- No --> Merge1 + D2 -- Yes --> P1[Obtain IMSI_VLR] + P1 -- OK --> D3{IMSI known?} + P1 -- Error --> P2[Procedure_Error] + P1 -- Aborted --> N1((Null)) + D3 -- No --> P3[Unidentified_subscriber] + D3 -- Yes --> D4{IMSI matches TMSI?} + D4 -- Yes --> Merge2(( )) + D4 -- No --> P4[Identity=IMSI] + P4 --> 2((2)) + Merge1 --> Merge2 + Merge2 --> P5[Illegal_Subscriber] + +``` + +Flowchart for Authenticate\_VLR macro. It starts at node 1, checks if Identity=IMSI. If No, it checks if Retry with IMSI? If Yes, it obtains IMSI\_VLR. If No, it goes to a merge point. From Obtain IMSI\_VLR, if OK, it checks if IMSI known? If No, it leads to Unidentified\_subscriber. If Yes, it checks if IMSI matches TMSI? If Yes, it goes to a merge point. If No, it sets Identity=IMSI and goes to node 2. From Obtain IMSI\_VLR, if Error, it leads to Procedure\_Error. If Aborted, it leads to Null. Both merge points lead to a common exit node associated with Illegal\_Subscriber. + +4891 + +4892 + +Figure 25.5/2 (sheet 2 of 2): Macro Authenticate\_VLR + +macrodefinition Obtain\_Authent\_Params\_VLR + +Obt\_Auth\_Par\_VLR1(3) + +Macro in the VLR to obtain authentication parameters from the HLR + +Signals to/from the right are to/from the HLR + +![Flowchart for Obtain_Authent_Params_VLR macro. It starts with a start node, followed by a process block with MAP_OPEN_req, MAP_SEND_AUTHENTICATION_INFO_req, and MAP_DELIMITER_req. Then a 'Receive_Open_Cnf' block. From there, three paths: 'OK' leads to 'Wait_For_Authentication_Info'; 'Vr' leads to 'Perform MAP Vr dialogue'; 'Error' leads to a connector and 'Procedure_Error'. The 'Perform' block leads to 'Successful result?'. 'Yes' leads to 'Empty result?'. 'No' leads to 'Error=Unknown subscriber?'. 'Error=Unknown subscriber?' 'Yes' leads to 'Unknown_Subscriber' connector; 'No' leads to 'Empty result?'. 'Empty result?' 'Yes' leads to 'Re-use old triplets?'; 'No' leads to 'OK' connector. 'Re-use old triplets?' 'Yes' leads to 'OK' connector; 'No' leads to a connector and 'Procedure_Error'.](903f003288ca0c29563d037be8c23c75_img.jpg) + +``` + +graph TD + Start([Start]) --> Process["MAP_OPEN_req +MAP_SEND_AUTHENTICATION_INFO_req +MAP_DELIMITER_req"] + Process --> Receive["Receive_Open_Cnf"] + Receive -- OK --> Wait["Wait_For_Authentication_Info"] + Receive -- Vr --> Perform["Perform MAP Vr dialogue"] + Receive -- Error --> ErrorConn(( )) + ErrorConn --> ProcedureError1["Procedure_Error"] + Perform --> SuccessfulResult{Successful result?} + SuccessfulResult -- Yes --> EmptyResult{Empty result?} + SuccessfulResult -- No --> UnknownSubscriber{Error=Unknown subscriber?} + UnknownSubscriber -- Yes --> UnknownSubscriberConn(( )) + UnknownSubscriberConn --> UnknownSubscriber["Unknown_Subscriber"] + UnknownSubscriber -- No --> EmptyResult + EmptyResult -- Yes --> ReUseOldTriplets{Re-use old triplets?} + EmptyResult -- No --> OKConn(( )) + ReUseOldTriplets -- Yes --> OKConn + ReUseOldTriplets -- No --> ProcedureError2(( )) + ProcedureError2 --> ProcedureError3["Procedure_Error"] + OKConn --> OK["OK"] + +``` + +Flowchart for Obtain\_Authent\_Params\_VLR macro. It starts with a start node, followed by a process block with MAP\_OPEN\_req, MAP\_SEND\_AUTHENTICATION\_INFO\_req, and MAP\_DELIMITER\_req. Then a 'Receive\_Open\_Cnf' block. From there, three paths: 'OK' leads to 'Wait\_For\_Authentication\_Info'; 'Vr' leads to 'Perform MAP Vr dialogue'; 'Error' leads to a connector and 'Procedure\_Error'. The 'Perform' block leads to 'Successful result?'. 'Yes' leads to 'Empty result?'. 'No' leads to 'Error=Unknown subscriber?'. 'Error=Unknown subscriber?' 'Yes' leads to 'Unknown\_Subscriber' connector; 'No' leads to 'Empty result?'. 'Empty result?' 'Yes' leads to 'Re-use old triplets?'; 'No' leads to 'OK' connector. 'Re-use old triplets?' 'Yes' leads to 'OK' connector; 'No' leads to a connector and 'Procedure\_Error'. + +4893 + +4894 + +Figure 25.5/3 (sheet 1 of 3): Macro Obtain\_Authent\_Params\_VLR + +macrodefinition Obtain\_Authent\_Params\_VLR + +Obt\_Auth\_Par\_VLR2(3) + +Macro in the VLR to obtain authentication parameters from the HLR + +Signals to/from the right are to/from the HLR + +![Flowchart for Obtain_Authent_Params_VLR macro. It starts with 'Wait_For_Authentication_Info', followed by 'MAP_SEND_AUTHENTICATION_INFO_cnf', and 'Check_Confirmation'. From 'Check_Confirmation', four paths emerge: OK (leading to 'Wait_For_Close_Or_Delimiter'), User Error (leading to 'Unknown_subscriber?' - if Yes, 'Unknown_Subscriber'; if No, 'Re-use_old_vectors?' - if Yes, 'OK'; if No, 'Procedure_Error'), Provider Error (leading to 'Re-use_old_vectors?' - if Yes, 'OK'; if No, 'Procedure_Error'), and Data Error (leading to 'MAP_CLOSE_req' and then '1'). 'Wait_For_Close_Or_Delimiter' leads to 'MAP_CLOSE_ind' and 'MAP_DELIMITER_ind'. 'MAP_CLOSE_ind' leads to a decision 'Authentication_vectors_received?' - if No, '1'; if Yes, 'OK'. 'MAP_DELIMITER_ind' leads to 'More_vectors_required?' - if Yes, 'MAP_SEND_AUTHENTICATION_INFO_req' and 'MAP_DELIMITER_req' (looping back to start); if No, 'MAP_CLOSE_req' and 'OK'.](e20e1d3fe823fee992d85fb88c7ff990_img.jpg) + +``` + +graph TD + Start([Wait_For_Authentication_Info]) --> CNF[MAP_SEND_AUTHENTICATION_INFO_cnf] + CNF --> Confirm[Check_Confirmation] + Confirm --> OK1[OK] + Confirm --> UserError[User Error] + Confirm --> ProviderError[Provider Error] + Confirm --> DataError[Data Error] + OK1 --> WaitClose[Wait_For_Close_Or_Delimiter] + UserError --> UnknownSub[Unknown_subscriber?] + UnknownSub -- Yes --> UnknownSubOut(( )) + UnknownSubOut --> UnknownSubText[Unknown_Subscriber] + UnknownSub -- No --> ReuseOld[Re-use_old_vectors?] + ProviderError --> ReuseOld + ReuseOld -- Yes --> OK2((OK)) + ReuseOld -- No --> ProcedureError(( )) + ProcedureError --> ProcedureErrorText[Procedure_Error] + DataError --> MAPCloseReq[MAP_CLOSE_req] + MAPCloseReq --> One1((1)) + WaitClose --> MAPCloseInd[MAP_CLOSE_ind] + WaitClose --> MAPDelimiterInd[MAP_DELIMITER_ind] + MAPCloseInd --> AuthVecRec[Authentication_vectors_received?] + AuthVecRec -- No --> One2((1)) + AuthVecRec -- Yes --> OK3((OK)) + MAPDelimiterInd --> MoreVecsReq[More_vectors_required?] + MoreVecsReq -- Yes --> MAPSendAuthReq[MAP_SEND_AUTHENTICATION_INFO_req] + MoreVecsReq -- Yes --> MAPDelimiterReq[MAP_DELIMITER_req] + MAPSendAuthReq --> Start + MoreVecsReq -- No --> MAPCloseReq2[MAP_CLOSE_req] + MAPCloseReq2 --> OK4((OK)) + +``` + +Flowchart for Obtain\_Authent\_Params\_VLR macro. It starts with 'Wait\_For\_Authentication\_Info', followed by 'MAP\_SEND\_AUTHENTICATION\_INFO\_cnf', and 'Check\_Confirmation'. From 'Check\_Confirmation', four paths emerge: OK (leading to 'Wait\_For\_Close\_Or\_Delimiter'), User Error (leading to 'Unknown\_subscriber?' - if Yes, 'Unknown\_Subscriber'; if No, 'Re-use\_old\_vectors?' - if Yes, 'OK'; if No, 'Procedure\_Error'), Provider Error (leading to 'Re-use\_old\_vectors?' - if Yes, 'OK'; if No, 'Procedure\_Error'), and Data Error (leading to 'MAP\_CLOSE\_req' and then '1'). 'Wait\_For\_Close\_Or\_Delimiter' leads to 'MAP\_CLOSE\_ind' and 'MAP\_DELIMITER\_ind'. 'MAP\_CLOSE\_ind' leads to a decision 'Authentication\_vectors\_received?' - if No, '1'; if Yes, 'OK'. 'MAP\_DELIMITER\_ind' leads to 'More\_vectors\_required?' - if Yes, 'MAP\_SEND\_AUTHENTICATION\_INFO\_req' and 'MAP\_DELIMITER\_req' (looping back to start); if No, 'MAP\_CLOSE\_req' and 'OK'. + +4895 + +4896 + +Figure 25.5/3 (sheet 2 of 3): Macro Obtain\_Authent\_Params\_VLR + +macrodefinition Obtain\_Authent\_Params\_VLR + +Obt\_Auth\_Par\_VLR3(3) + +Macro in the VLR to obtain authentication parameters from the HLR + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR + +![State transition diagram for Obtain_Authent_Params_VLR macro. It starts with 'Wait_For_Authentication_Info' and branches into three paths: one leading to 'Null' via 'MAP_U_ABORT_req', one leading to 'OK' via 'Re-use old vectors?' (Yes), and one leading to 'Procedure_Error' via 'Re-use old vectors?' (No).](816198e6a82098ac1c2af8551d3a6e16_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Wait_For_Authentication_Info + state "MAP_U_ABORT_ind, MAP_CLOSE_ind" as Left + state "MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind" as Center + state "MAP_NOTICE_ind" as Right + state "MAP_U_ABORT_req" as LeftReq + state "MAP_CLOSE_req" as RightReq + state "Re-use old vectors?" as Decision + state Null as [*] + state OK as [*] + state Procedure_Error as [*] + + Wait_For_Authentication_Info --> Left + Wait_For_Authentication_Info --> Center + Wait_For_Authentication_Info --> Right + Left --> LeftReq + LeftReq --> Null + Center --> Decision + Right --> RightReq + RightReq --> Decision + Decision -- Yes --> OK + Decision -- No --> Procedure_Error + +``` + +State transition diagram for Obtain\_Authent\_Params\_VLR macro. It starts with 'Wait\_For\_Authentication\_Info' and branches into three paths: one leading to 'Null' via 'MAP\_U\_ABORT\_req', one leading to 'OK' via 'Re-use old vectors?' (Yes), and one leading to 'Procedure\_Error' via 'Re-use old vectors?' (No). + +4897 + +4898 + +Figure 25.5/3 (sheet 3 of 3): Macro Obtain\_Authent\_Params\_VLR + +![A state transition diagram for the process Obtain_Authent_Sets_VLR. It starts with an initial state (orange oval) leading to a state box labeled 'Obtain_Authent_Params_VLR'. A note box on the left contains the text 'Process in the VLR to obtain authentication sets from the HLR'. From the 'Obtain_Authent_Params_VLR' state, a transition arrow points down to an exit state (crossed circle). The transition is labeled with 'OK, Null, Unknown_Subscriber, Procedure_Error'.](b6b45350db23a8328edfa2e4ed42440b_img.jpg) + +process Obtain\_Authent\_Sets\_VLR + +Obt\_Auth\_Sets\_VLR1(1) + +``` +stateDiagram-v2 + [*] --> Obtain_Authent_Params_VLR + Obtain_Authent_Params_VLR --> [*] : OK, Null, Unknown_Subscriber, Procedure_Error +``` + +A state transition diagram for the process Obtain\_Authent\_Sets\_VLR. It starts with an initial state (orange oval) leading to a state box labeled 'Obtain\_Authent\_Params\_VLR'. A note box on the left contains the text 'Process in the VLR to obtain authentication sets from the HLR'. From the 'Obtain\_Authent\_Params\_VLR' state, a transition arrow points down to an exit state (crossed circle). The transition is labeled with 'OK, Null, Unknown\_Subscriber, Procedure\_Error'. + +4899 + +4900 + +Figure 25.5/4: Process Obtain\_Authent\_Sets\_VLR + +![Flowchart for process Obtain_Authent_Sets_SGSN. It starts at 'Idle', receives an 'Authentication parameter request', checks if the HLR is unknown. If yes, it sets a negative response and returns to 'Idle'. If no, it sends MAP requests and receives an 'Open_Cnf'. From there, it branches based on 'OK', 'Vr', or 'Error'. The 'Vr' path leads to 'Perform MAP Vr dialogue', which then checks for a successful result. If successful, it checks if the result is empty. If empty, it checks if old triplets can be reused. If not, it sends a negative response and returns to 'Idle'. If old triplets can be reused or the result is not empty, it sends an 'Authentication parameter ack' and returns to 'Idle'. If the result is not successful, it checks if it's an unknown subscriber error. If yes, it sends a negative response and returns to 'Idle'. If no, it checks if old triplets can be reused. If yes, it sends an 'Authentication parameter ack' and returns to 'Idle'. If no, it sends a negative response and returns to 'Idle'. The 'OK' path leads to 'Wait_For_Authentication_Info' and returns to 'Idle'. The 'Error' path leads to a connector '1'.](dfb22056a59b72fa70702df3cb815f8c_img.jpg) + +**process Obtain\_Authent\_Sets\_SGSN** **Obt\_Auth\_Sets\_SGSN1(2)** + +Process in the SGSN to obtain authentication sets from the HLR + +Signals to/from the left are to/from the application process in the SGSN; signals to/from the right are to/from the HLR + +``` + + graph TD + Start([Idle]) --> Request{Authentication parameter request} + Request --> UnknownHLR{Unknown HLR?} + UnknownHLR -- Yes --> NegativeResponse1[Set negative response: Unknown HLR] + NegativeResponse1 --> NegativeResponse1_out{Authentication parameter negative response} + NegativeResponse1_out --> Idle1([Idle]) + + UnknownHLR -- No --> MAPRequests[MAP_OPEN_req +MAP_SEND_AUTHENTICATION_INFO_req +MAP_DELIMITER_req] + MAPRequests --> OpenCnf[Receive_Open_Cnf] + + OpenCnf -- OK --> WaitInfo[Wait_For_Authentication_Info] + WaitInfo --> Idle2([Idle]) + + OpenCnf -- Vr --> MAPVr[Perform MAP Vr dialogue] + + MAPVr --> Successful{Successful result?} + + Successful -- Yes --> Empty{Empty result?} + + Empty -- No --> Ack[Authentication parameter ack] + + Empty -- Yes --> Reuse{Re-use old triplets?} + + Reuse -- Yes --> Ack + + Reuse -- No --> NegativeResponse2{Authentication parameter negative response} + + NegativeResponse2 --> Idle3([Idle]) + + Successful -- No --> UnknownSub{Error=Unknown subscriber?} + + UnknownSub -- Yes --> NegativeResponse3{Authentication parameter negative response} + + NegativeResponse3 --> Idle4([Idle]) + + UnknownSub -- No --> Reuse + + Ack --> Idle5([Idle]) + + OpenCnf -- Error --> Connector1((1)) + + Empty -- Yes --> Connector2((1)) + +``` + +Flowchart for process Obtain\_Authent\_Sets\_SGSN. It starts at 'Idle', receives an 'Authentication parameter request', checks if the HLR is unknown. If yes, it sets a negative response and returns to 'Idle'. If no, it sends MAP requests and receives an 'Open\_Cnf'. From there, it branches based on 'OK', 'Vr', or 'Error'. The 'Vr' path leads to 'Perform MAP Vr dialogue', which then checks for a successful result. If successful, it checks if the result is empty. If empty, it checks if old triplets can be reused. If not, it sends a negative response and returns to 'Idle'. If old triplets can be reused or the result is not empty, it sends an 'Authentication parameter ack' and returns to 'Idle'. If the result is not successful, it checks if it's an unknown subscriber error. If yes, it sends a negative response and returns to 'Idle'. If no, it checks if old triplets can be reused. If yes, it sends an 'Authentication parameter ack' and returns to 'Idle'. If no, it sends a negative response and returns to 'Idle'. The 'OK' path leads to 'Wait\_For\_Authentication\_Info' and returns to 'Idle'. The 'Error' path leads to a connector '1'. + +4901 + +4902 + +**Figure 25.5/5 (sheet 1 of 2): Process Obtain\_Authent\_Sets\_SGSN** + +process Obtain\_Authent\_Sets\_SGSN + +Obt\_Auth\_Sets\_SGSN2(2) + +Process in the SGSN to obtain authentication sets from the HLR + +Signals to/from the left are to/from the application process in the SGSN; signals to/from the right are to/from the HLR + +![Flowchart for process Obtain_Authent_Sets_SGSN. It starts with 'Wait_For_Authentication_Info', followed by 'MAP_SEND_AUTHENTICATION_INFO_cnf', and 'Check_Confirmation'. From 'Check_Confirmation', it branches into 'OK', 'User Error' (Unknown subscriber? No), and 'Provider Error, Data Error'. 'OK' leads to 'Wait_For_Close_Or_Delimiter'. 'User Error' (Unknown subscriber? No) leads to 'Re-use old vectors?'. 'Provider Error, Data Error' leads to 'Re-use old vectors?'. 'Re-use old vectors? Yes' leads to 'Authentication parameter ack' and 'Idle'. 'Re-use old vectors? No' leads to 'Unknown subscriber? Yes', which leads to 'Authentication parameter negative response' and 'Idle'. 'Wait_For_Close_Or_Delimiter' leads to 'MAP_CLOSE_ind' and 'MAP_DELIMITER_ind'. 'MAP_CLOSE_ind' leads to a decision diamond. 'No' leads to connector '1'. 'Yes' leads to 'Authentication vectors received?'. 'MAP_DELIMITER_ind' leads to 'More vectors required?'. 'Yes' leads to 'MAP_SEND_AUTHENTICATION_INFO_req' and 'MAP_DELIMITER_req', which leads to 'Wait_For_Authentication_Info'. 'No' leads to 'MAP_CLOSE_req', which leads to 'Authentication parameter ack' and 'Idle'.](4e6012e3ba9ac443fd007e2f4adda702_img.jpg) + +``` + +graph TD + Start([Wait_For_Authentication_Info]) --> MAP_SEND_AUTHENTICATION_INFO_cnf[MAP_SEND_AUTHENTICATION_INFO_cnf] + MAP_SEND_AUTHENTICATION_INFO_cnf --> Check_Confirmation[Check_Confirmation] + Check_Confirmation --> OK[OK] + Check_Confirmation --> User_Error[User Error] + Check_Confirmation --> Provider_Error[Provider Error, Data Error] + User_Error --> Unknown_subscriber{Unknown subscriber?} + Unknown_subscriber -- No --> Re_use_old_vectors{Re-use old vectors?} + Unknown_subscriber -- Yes --> Auth_param_neg_resp{Authentication parameter negative response} + Auth_param_neg_resp --> Idle1([Idle]) + Provider_Error --> Re_use_old_vectors + Re_use_old_vectors -- Yes --> Auth_param_ack1{Authentication parameter ack} + Auth_param_ack1 --> Idle2([Idle]) + Re_use_old_vectors -- No --> Unknown_subscriber + OK --> Wait_For_Close_Or_Delimiter[Wait_For_Close_Or_Delimiter] + Wait_For_Close_Or_Delimiter --> MAP_CLOSE_ind[MAP_CLOSE_ind] + Wait_For_Close_Or_Delimiter --> MAP_DELIMITER_ind[MAP_DELIMITER_ind] + MAP_CLOSE_ind --> Decision1{ } + Decision1 -- No --> Connector1((1)) + Decision1 -- Yes --> Auth_vectors_received{Authentication vectors received?} + MAP_DELIMITER_ind --> More_vectors_required{More vectors required?} + More_vectors_required -- Yes --> MAP_SEND_AUTHENTICATION_INFO_req[MAP_SEND_AUTHENTICATION_INFO_req] + More_vectors_required -- Yes --> MAP_DELIMITER_req[MAP_DELIMITER_req] + MAP_SEND_AUTHENTICATION_INFO_req --> Wait_For_Authentication_Info + More_vectors_required -- No --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> Auth_param_ack2{Authentication parameter ack} + Auth_param_ack2 --> Idle3([Idle]) + Auth_vectors_received --> Auth_param_ack2 + +``` + +Flowchart for process Obtain\_Authent\_Sets\_SGSN. It starts with 'Wait\_For\_Authentication\_Info', followed by 'MAP\_SEND\_AUTHENTICATION\_INFO\_cnf', and 'Check\_Confirmation'. From 'Check\_Confirmation', it branches into 'OK', 'User Error' (Unknown subscriber? No), and 'Provider Error, Data Error'. 'OK' leads to 'Wait\_For\_Close\_Or\_Delimiter'. 'User Error' (Unknown subscriber? No) leads to 'Re-use old vectors?'. 'Provider Error, Data Error' leads to 'Re-use old vectors?'. 'Re-use old vectors? Yes' leads to 'Authentication parameter ack' and 'Idle'. 'Re-use old vectors? No' leads to 'Unknown subscriber? Yes', which leads to 'Authentication parameter negative response' and 'Idle'. 'Wait\_For\_Close\_Or\_Delimiter' leads to 'MAP\_CLOSE\_ind' and 'MAP\_DELIMITER\_ind'. 'MAP\_CLOSE\_ind' leads to a decision diamond. 'No' leads to connector '1'. 'Yes' leads to 'Authentication vectors received?'. 'MAP\_DELIMITER\_ind' leads to 'More vectors required?'. 'Yes' leads to 'MAP\_SEND\_AUTHENTICATION\_INFO\_req' and 'MAP\_DELIMITER\_req', which leads to 'Wait\_For\_Authentication\_Info'. 'No' leads to 'MAP\_CLOSE\_req', which leads to 'Authentication parameter ack' and 'Idle'. + +4903 + +4904 + +Figure 25.5/5 (sheet 2 of 2): Process Obtain\_Authent\_Sets\_SGSN + +![Flowchart for process Obtain_Authent_Sets_HLR. It starts with an initial node, followed by a 'Null' node, then 'Receive_Open_Ind'. From 'Receive_Open_Ind', three paths emerge: 'Error' (leading to 'Null'), 'Vr' (leading to 'Perform MAP Vr dialogue' then 'Null'), and 'OK' (leading to 'Wait_For_Service_Primitive'). 'Wait_For_Service_Primitive' leads to 'MAP_NOTICE_ind'. 'MAP_NOTICE_ind' leads to a merge node, which then leads to 'MAP_SEND_AUTHENTICATION_INFO_ind'. 'MAP_SEND_AUTHENTICATION_INFO_ind' leads to 'Check_Indication'. From 'Check_Indication', 'OK' leads to a connector node '1', and 'Error' leads to a merge node for 'MAP_SEND_AUTHENTICATION_INFO_rsp' and 'MAP_CLOSE_req', which then leads to 'Null'. 'MAP_NOTICE_ind' also leads directly to 'MAP_CLOSE_req', which leads to 'Null'.](477a5b2a3b9218257a4cb98508246975_img.jpg) + +**process Obtain\_Authent\_Sets\_HLR** **Obt\_Auth\_Sets\_HLR1(2)** + +Process in the HLR to handle a request from the VLR for authentication sets + +Signals to/from the left are to/from the VLR or the SGSN + +``` + +graph TD + Start([ ]) --> Null1([Null]) + Null1 --> Receive_Open_Ind[Receive_Open_Ind] + Receive_Open_Ind -- Error --> Null2([Null]) + Receive_Open_Ind -- Vr --> Perform_MAP_Vr[Perform MAP Vr dialogue] + Perform_MAP_Vr --> Null3([Null]) + Receive_Open_Ind -- OK --> Wait_For_Service_Primitive[Wait_For_Service_Primitive] + Wait_For_Service_Primitive --> MAP_NOTICE_ind{MAP_NOTICE_ind} + MAP_NOTICE_ind --> Merge1{ } + Merge1 --> MAP_SEND_AUTHENTICATION_INFO_ind[MAP_SEND_AUTHENTICATION_INFO_ind] + MAP_SEND_AUTHENTICATION_INFO_ind --> Check_Indication[Check_Indication] + Check_Indication -- OK --> Connector1((1)) + Check_Indication -- Error --> Merge2{ } + Merge2 --> MAP_SEND_AUTHENTICATION_INFO_rsp[MAP_SEND_AUTHENTICATION_INFO_rsp] + Merge2 --> MAP_CLOSE_req1[MAP_CLOSE_req] + MAP_SEND_AUTHENTICATION_INFO_rsp --> Null4([Null]) + MAP_CLOSE_req1 --> Null5([Null]) + MAP_NOTICE_ind --> MAP_CLOSE_req2[MAP_CLOSE_req] + MAP_CLOSE_req2 --> Null6([Null]) + +``` + +Flowchart for process Obtain\_Authent\_Sets\_HLR. It starts with an initial node, followed by a 'Null' node, then 'Receive\_Open\_Ind'. From 'Receive\_Open\_Ind', three paths emerge: 'Error' (leading to 'Null'), 'Vr' (leading to 'Perform MAP Vr dialogue' then 'Null'), and 'OK' (leading to 'Wait\_For\_Service\_Primitive'). 'Wait\_For\_Service\_Primitive' leads to 'MAP\_NOTICE\_ind'. 'MAP\_NOTICE\_ind' leads to a merge node, which then leads to 'MAP\_SEND\_AUTHENTICATION\_INFO\_ind'. 'MAP\_SEND\_AUTHENTICATION\_INFO\_ind' leads to 'Check\_Indication'. From 'Check\_Indication', 'OK' leads to a connector node '1', and 'Error' leads to a merge node for 'MAP\_SEND\_AUTHENTICATION\_INFO\_rsp' and 'MAP\_CLOSE\_req', which then leads to 'Null'. 'MAP\_NOTICE\_ind' also leads directly to 'MAP\_CLOSE\_req', which leads to 'Null'. + +4905 + +4906 + +**Figure 25.5/6 (sheet 1 of 2): Process Obtain\_Authent\_Sets\_HLR** + +![Flowchart for process Obtain_Authent_Sets_HLR. It starts at connector '1', checks if a requesting node type is present. If no, it checks if it's an SGSN with non-GPRS access or a VLR with GPRS access. If neither, it sets a diagnostic or user error and returns a response. If yes, it checks available vectors, then if segmentation is needed, it obtains vectors from AuC and returns a response. Finally, it sends a delimiter request and waits for a service primitive.](3c76eca7bc00e29848744fae0d9d017e_img.jpg) + +**process Obtain\_Authent\_Sets\_HLR** **Obt\_Auth\_Sets\_HLR2(2)** + +Process in the HLR to handle a request from the VLR for authentication sets + +Signals to/from the left are to/from the VLR or the SGSN + +``` + +graph TD + Start((1)) --> Q1{Requesting node type present?} + Q1 -- No --> Q2{Requesting node type=SGSN AND Network access mode=Non-GPRS only} + Q2 -- Yes --> D1[Set Diagnostic: GPRS subscription unknown] + Q2 -- No --> Q3{Requesting node type=VLR AND Network access mode=GPRS only} + Q3 -- Yes --> D2[Set User Error: Unknown subscriber] + D1 --> R1[MAP_SEND_AUTHENTICATION_INFO_rsp +MAP_CLOSE_req] + D2 --> R1 + R1 --> Null1([Null]) + Q1 -- Yes --> P1[Check Available Vectors] + P1 --> Q4{Segmentation allowed and supported and needed?} + Q4 -- No --> R2[MAP_SEND_AUTHENTICATION_INFO_rsp +MAP_CLOSE_req] + Q4 -- Yes --> P2[Obtain Vectors From_AuC] + P2 --> Note[To be stored for later use; see 3GPP TS 33.102 (UMTS) or 3GPP TS 43.020 (GSM)] + P2 --> Null2([Null]) + Note --> R2 + R2 --> P3[MAP_SEND_AUTHENTICATION_INFO_rsp +MAP_DELIMITER_req] + P3 --> End[Wait_For_Service_Primitive] + +``` + +Flowchart for process Obtain\_Authent\_Sets\_HLR. It starts at connector '1', checks if a requesting node type is present. If no, it checks if it's an SGSN with non-GPRS access or a VLR with GPRS access. If neither, it sets a diagnostic or user error and returns a response. If yes, it checks available vectors, then if segmentation is needed, it obtains vectors from AuC and returns a response. Finally, it sends a delimiter request and waits for a service primitive. + +4907 + +4908 + +**Figure 25.5/6 (sheet 2 of 2): Process Obtain\_Authent\_Sets\_HLR** + +procedure Check\_Available\_Vectors + +Chk\_Avl\_Vec1(1) + +Procedure in the HLR to check the number of authentication vectors requested against the number of available vectors + +![Flowchart for Check_Available_Vectors procedure](59bcca262fbcdfd92ec4b9202aa586a1_img.jpg) + +``` +graph TD; Start([Start]) --> D1{More vectors requested than stored?}; D1 -- No --> Exit1(( )); D1 -- Yes --> D2{Number of vectors stored=0?}; D2 -- Yes --> Exit2(( )); D2 -- No --> D3{Immediate Response Preferred indicator supported?}; D3 -- Yes --> D4{Immediate response preferred?}; D3 -- No --> Exit3(( )); D4 -- Yes --> Exit4(( )); D4 -- No --> Process1[Obtain vectors from AuC]; Process1 --> Exit5(( )); D3 -- Yes --> Process2[Obtain vectors from AuC]; Process2 --> Exit6(( )); Note1[HLR operator option] -.-> Process2; +``` + +The flowchart illustrates the 'Check\_Available\_Vectors' procedure. It begins with a start symbol leading to a decision diamond: 'More vectors requested than stored?'. If 'No', it ends at an exit symbol. If 'Yes', it proceeds to another decision diamond: 'Number of vectors stored=0?'. If 'Yes', it ends at an exit symbol. If 'No', it proceeds to a decision diamond: 'Immediate Response Preferred indicator supported?'. If 'No', it ends at an exit symbol. If 'Yes', it proceeds to a decision diamond: 'Immediate response preferred?'. If 'Yes', it ends at an exit symbol. If 'No', it proceeds to a process block: 'Obtain vectors from AuC', which then ends at an exit symbol. If 'Yes' from the 'Immediate Response Preferred indicator supported?' diamond, it proceeds to another process block: 'Obtain vectors from AuC', which is also associated with an 'HLR operator option' note and ends at an exit symbol. + +Flowchart for Check\_Available\_Vectors procedure + +4909 + +4910 + +Figure 25.5/7: Procedure Check\_Available\_Vectors + +![State transition diagram for process Report_Authentication_Failure_VLR. The process starts at an initial state, goes to Idle, then to an Authentication failure report state. From there, it sends MAP_OPEN_req, MAP_AUTHENTICATION_FAILURE_REPORT_req, and MAP_DELIMITER_req to enter a Receive_Open_Cnf state. From Receive_Open_Cnf, an OK response leads to Wait_For_HLR_Response, while a Vr, Error response leads back to Idle. From Wait_For_HLR_Response, a MAP_NOTICE_ind leads to a MAP_CLOSE_req state which returns to Idle. A successful completion (MAP_AUTHENTICATION_FAILURE_REPORT_cnf, MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind) also returns the process to Idle.](b605973eb46aa44282266453180c5d23_img.jpg) + +**process Report\_Authentication\_Failure\_VLR** **Rep\_Auth\_Fail\_VLR1(1)** + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Auth_Fail_Report: Authentication failure report + Auth_Fail_Report --> Send_Req: MAP_OPEN_req, MAP_AUTHENTICATION_FAILURE_REPORT_req, MAP_DELIMITER_req + Send_Req --> Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_HLR_Response: OK + Receive_Open_Cnf --> Idle: Vr, Error + Wait_For_HLR_Response --> Notice_Ind: MAP_NOTICE_ind + Notice_Ind --> Close_Req: MAP_CLOSE_req + Close_Req --> Idle + Wait_For_HLR_Response --> Done: MAP_AUTHENTICATION_FAILURE_REPORT_cnf, MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + Done --> Idle + +``` + +Process in the VLR to send an authentication failure report to the HLR + +Signals to/from the left are to/from the application process in the VLR; signals to/from the right are to/from the HLR + +State transition diagram for process Report\_Authentication\_Failure\_VLR. The process starts at an initial state, goes to Idle, then to an Authentication failure report state. From there, it sends MAP\_OPEN\_req, MAP\_AUTHENTICATION\_FAILURE\_REPORT\_req, and MAP\_DELIMITER\_req to enter a Receive\_Open\_Cnf state. From Receive\_Open\_Cnf, an OK response leads to Wait\_For\_HLR\_Response, while a Vr, Error response leads back to Idle. From Wait\_For\_HLR\_Response, a MAP\_NOTICE\_ind leads to a MAP\_CLOSE\_req state which returns to Idle. A successful completion (MAP\_AUTHENTICATION\_FAILURE\_REPORT\_cnf, MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind) also returns the process to Idle. + +4911 + +4912 + +**Figure 25.5/9: Process Report\_Authentication\_Failure\_VLR** + +![State transition diagram for process Report_Authentication_Failure_SGSN. It starts at Idle, receives an authentication failure report, sends MAP requests, receives a confirmation, and then either waits for an HLR response or returns to Idle. Upon receiving an HLR response, it sends a notice and close request, returning to Idle, or handles an authentication failure report confirmation.](26cf894361680874f5c51acffdd85eaf_img.jpg) + +**process Report\_Authentication\_Failure\_SGSN** **Rep\_Auth\_Fail\_SGSN1(1)** + +Process in the SGSN to send an authentication failure report to the HLR + +Signals to/from the left are to/from the application process in the SGSN; signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Auth_Fail_Report: Authentication failure report + Auth_Fail_Report --> Send_Req: MAP_OPEN_req, MAP_AUTHENTICATION_FAILURE_REPORT_req, MAP_DELIMITER_req + Send_Req --> Receive_Open_Cnf: Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_HLR_Response: OK + Receive_Open_Cnf --> Idle: Vr, Error + Wait_For_HLR_Response --> Send_Notice: MAP_NOTICE_ind + Wait_For_HLR_Response --> Handle_Cnf: MAP_AUTHENTICATION_FAILURE_REPORT_cnf, MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + Send_Notice --> Send_Close: MAP_CLOSE_req + Send_Close --> Idle + Handle_Cnf --> Idle + +``` + +State transition diagram for process Report\_Authentication\_Failure\_SGSN. It starts at Idle, receives an authentication failure report, sends MAP requests, receives a confirmation, and then either waits for an HLR response or returns to Idle. Upon receiving an HLR response, it sends a notice and close request, returning to Idle, or handles an authentication failure report confirmation. + +4913 + +4914 + +**Figure 25.5/10: Process Report\_Authentication\_Failure\_SGSN** + +![State transition diagram for Note_Authentication_Failure_HLR process. It starts at Idle, receives an Open_Ind, waits for a report, then branches based on MAP_AUTHENTICATION_FAILURE_REPORT_ind, MAP_NOTICE_ind, and MAP_P_ABORT_ind. It includes decision points for subscriber status and error handling, returning to Idle.](b76d25ab65e4f05f195c2d46acbdbd72_img.jpg) + +**process Note\_Authentication\_Failure\_HLR** **Note\_Auth\_Fail\_HLR1(1)** + +Process in the HLR to handle an authentication failure report from the VLR or SGSN + +Signals to/from the left are to/from the VLR or SGSN; +signals to/from the right are to/from the application process in the HLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_Ind + Receive_Open_Ind --> Wait_For_Report : OK + Receive_Open_Ind --> Idle : Vr, Error + state "MAP_AUTHENTICATION_FAILURE_REPORT_ind" as MAP_AUTHENTICATION_FAILURE_REPORT_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_P_ABORT_ind" as MAP_P_ABORT_ind + Wait_For_Report --> MAP_AUTHENTICATION_FAILURE_REPORT_ind + Wait_For_Report --> MAP_NOTICE_ind + Wait_For_Report --> MAP_P_ABORT_ind + MAP_AUTHENTICATION_FAILURE_REPORT_ind --> Check_Indication + Check_Indication --> Subscriber_known? : OK + Check_Indication --> Error + Subscriber_known? --> Authentication_failure_report : Yes + Subscriber_known? --> Set_User_Error : No + Set_User_Error --> Set_User_Error : Unknown Subscriber + Authentication_failure_report --> MAP_AUTHENTICATION_FAILURE_REPORT_rsp + Set_User_Error --> MAP_AUTHENTICATION_FAILURE_REPORT_rsp + Error --> MAP_AUTHENTICATION_FAILURE_REPORT_rsp + MAP_AUTHENTICATION_FAILURE_REPORT_rsp --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_P_ABORT_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle + state "MAP_AUTHENTICATION_FAILURE_REPORT_rsp" as MAP_AUTHENTICATION_FAILURE_REPORT_rsp + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "Set User Error: Unknown Subscriber" as Set_User_Error + state "Authentication failure report" as Authentication_failure_report + state "Subscriber known?" as Subscriber_known? + state "Check_Indication" as Check_Indication + state "Receive_Open_Ind" as Receive_Open_Ind + state "Wait_For_Report" as Wait_For_Report + +``` + +State transition diagram for Note\_Authentication\_Failure\_HLR process. It starts at Idle, receives an Open\_Ind, waits for a report, then branches based on MAP\_AUTHENTICATION\_FAILURE\_REPORT\_ind, MAP\_NOTICE\_ind, and MAP\_P\_ABORT\_ind. It includes decision points for subscriber status and error handling, returning to Idle. + +4915 + +4916 + +**Figure 25.5/11: Process Note\_Authentication\_Failure\_HLR** + +## 4917 25.6 IMEI Handling Macros + +4918 The following macros are used in the network in order to enable handling and checking of the mobile equipment +4919 identity. + +### 4920 25.6.1 Macro Check\_IMEI\_MSC + +4921 This macro is used by the MSC to receive a request from the VLR, relay it to the EIR, and pass the result from the EIR +4922 back to the VLR. + +4923 Sheet 1: If the dialogue with the EIR drops back to a previous protocol version and the EIR returned an error, the MSC +4924 relays the error to the VLR in the MAP\_CHECK\_IMEI response. If the dialogue with the EIR failed, or the EIR +4925 returned a badly formed result, the MSC sends a System Failure error to the VLR in the MAP\_CHECK\_IMEI response. + +### 4926 25.6.2 Macro Check\_IMEI\_VLR + +4927 This macro is used by the VLR to control the check of a mobile equipment's IMEI. It may also be used to request the +4928 BMUEF from the EIR. + +### 4929 25.6.3 Process Check\_IMEI\_SGSN + +4930 This process is used by the SGSN to control the check of a mobile equipment's IMEI. It may also be used to request the +4931 BMUEF from the EIR. + +### 4932 25.6.4 Process Check\_IMEI\_EIR + +4933 This process is used by the EIR to obtain the status of a mobile equipment, upon request from the MSC or from the +4934 SGSN. It may also be used to obtain the BMUEF. + +### 4935 25.6.5 Macro Obtain\_IMEI\_MSC + +4936 This macro is used by the MSC to respond to a request from the VLR to provide the IMEI. + +### 4937 25.6.6 Macro Obtain\_IMEI\_VLR + +4938 This macro is used by the VLR to obtain the IMEI from the MSC. + +macrodefinition Check\_IMEI\_MSC + +Chk\_IMEI\_MSC1(2) + +Macro in the MSC to check the IMEI of the MS, and report the result to the VLR + +Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR unless marked otherwise + +![Flowchart for macrodefinition Check_IMEI_MSC. The process starts with a MAP_CHECK_IMEI_ind signal. It checks if BMUEF is requested. If no, it checks if IMEI is available. If yes, it sends an A_IDENTITY_REQUEST_req with Requested identity=IMEI and waits for IMEI. If no, it goes to connector 1. If BMUEF is requested, it checks if IMEISV is available. If yes, it sends an A_IDENTITY_REQUEST_req with Requested identity=IMEISV and waits for IMEI. If no, it goes to connector 1. Both wait states lead to a merge point. From the merge point, it sends MAP_OPEN_req, MAP_CHECK_IMEI_req, and MAP_DELIMITER_req to the EIR. It receives an Open_Cnf and checks if the response is OK, Vr, or Error. If OK, it waits for an EIR_Response. If Vr, it performs a MAP Vr dialogue and checks for a successful result. If successful, it adds IMEI to the service response to VLR. If not, it sets a user error. If Error, it sets a user error for system failure. All three paths (OK, Vr, Error) lead to a merge point that sends a MAP_CHECK_IMEI_rsp and MAP_DELIMITER_req to the VLR and ends at an OK connector. The EIR_Response path leads to a MAP_CHECK_IMEI_cnf signal, a Check_Confirmation process, and then checks for OK, User Error, or Provider Error/Data Error. OK leads to adding IMEI to the service response to VLR. User Error and Provider Error/Data Error lead to setting a user error for system failure. Both lead to a merge point that sends a MAP_CHECK_IMEI_rsp and MAP_DELIMITER_req to the VLR and ends at an OK connector.](87c2452c5d2acd3ac68f64b22b4a473f_img.jpg) + +``` + +graph TD + Start([Start]) --> MAP_CHECK_IMEI_ind{MAP_CHECK_IMEI_ind} + MAP_CHECK_IMEI_ind --> BMUEF_requested{BMUEF requested?} + BMUEF_requested -- No --> IMEI_available{IMEI available?} + BMUEF_requested -- Yes --> IMEISV_available{IMEISV available?} + IMEI_available -- No --> A_IDENTITY_REQUEST_req_IMEI{A_IDENTITY_REQUEST_req} + IMEI_available -- Yes --> 1((1)) + A_IDENTITY_REQUEST_req_IMEI --> Requested_identity_IMEI[Requested identity=IMEI] + Requested_identity_IMEI --> Wait_For_IMEI_1[Wait_For_IMEI] + IMEISV_available -- No --> A_IDENTITY_REQUEST_req_IMEISV{A_IDENTITY_REQUEST_req} + IMEISV_available -- Yes --> Requested_identity_IMEISV[Requested identity=IMEISV] + Requested_identity_IMEISV --> Wait_For_IMEI_2[Wait_For_IMEI] + Wait_For_IMEI_1 --> Merge1(( )) + Wait_For_IMEI_2 --> Merge1 + Merge1 --> To_EIR[To EIR] + To_EIR --> MAP_OPEN_req[MAP_OPEN_req +MAP_CHECK_IMEI_req +MAP_DELIMITER_req] + MAP_OPEN_req --> Receive_Open_Cnf[Receive_Open_Cnf] + Receive_Open_Cnf --> Response_Decision{Response Decision} + Response_Decision -- OK --> Wait_For_EIR_Response[Wait_For_EIR_Response] + Response_Decision -- Vr --> Perform_MAP_Vr_dialogue[Perform MAP Vr dialogue] + Response_Decision -- Error --> Set_User_Error_System_Failure_1[Set User Error: System failure] + Perform_MAP_Vr_dialogue --> Successful_result{Successful result?} + Successful_result -- Yes --> Add_IMEI_to_service_response_1[Add IMEI to service response to VLR] + Successful_result -- No --> Set_User_Error_1[Set User Error] + Add_IMEI_to_service_response_1 --> Merge2(( )) + Set_User_Error_1 --> Merge2 + Set_User_Error_System_Failure_1 --> Merge2 + Merge2 --> MAP_CHECK_IMEI_rsp_1[MAP_CHECK_IMEI_rsp +MAP_DELIMITER_req] + MAP_CHECK_IMEI_rsp_1 --> OK_1((OK)) + Wait_For_EIR_Response --> MAP_CHECK_IMEI_cnf{MAP_CHECK_IMEI_cnf} + MAP_CHECK_IMEI_cnf --> From_EIR[From EIR] + From_EIR --> Check_Confirmation[Check_Confirmation] + Check_Confirmation --> Confirmation_Decision{Confirmation Decision} + Confirmation_Decision -- OK --> Add_IMEI_to_service_response_2[Add IMEI to service response to VLR] + Confirmation_Decision -- User Error --> Set_User_Error_System_Failure_2[Set User Error: System failure] + Confirmation_Decision -- Provider Error, Data Error --> Set_User_Error_System_Failure_2 + Add_IMEI_to_service_response_2 --> Merge3(( )) + Set_User_Error_System_Failure_2 --> Merge3 + Merge3 --> MAP_CHECK_IMEI_rsp_2[MAP_CHECK_IMEI_rsp +MAP_DELIMITER_req] + MAP_CHECK_IMEI_rsp_2 --> OK_2((OK)) + +``` + +Flowchart for macrodefinition Check\_IMEI\_MSC. The process starts with a MAP\_CHECK\_IMEI\_ind signal. It checks if BMUEF is requested. If no, it checks if IMEI is available. If yes, it sends an A\_IDENTITY\_REQUEST\_req with Requested identity=IMEI and waits for IMEI. If no, it goes to connector 1. If BMUEF is requested, it checks if IMEISV is available. If yes, it sends an A\_IDENTITY\_REQUEST\_req with Requested identity=IMEISV and waits for IMEI. If no, it goes to connector 1. Both wait states lead to a merge point. From the merge point, it sends MAP\_OPEN\_req, MAP\_CHECK\_IMEI\_req, and MAP\_DELIMITER\_req to the EIR. It receives an Open\_Cnf and checks if the response is OK, Vr, or Error. If OK, it waits for an EIR\_Response. If Vr, it performs a MAP Vr dialogue and checks for a successful result. If successful, it adds IMEI to the service response to VLR. If not, it sets a user error. If Error, it sets a user error for system failure. All three paths (OK, Vr, Error) lead to a merge point that sends a MAP\_CHECK\_IMEI\_rsp and MAP\_DELIMITER\_req to the VLR and ends at an OK connector. The EIR\_Response path leads to a MAP\_CHECK\_IMEI\_cnf signal, a Check\_Confirmation process, and then checks for OK, User Error, or Provider Error/Data Error. OK leads to adding IMEI to the service response to VLR. User Error and Provider Error/Data Error lead to setting a user error for system failure. Both lead to a merge point that sends a MAP\_CHECK\_IMEI\_rsp and MAP\_DELIMITER\_req to the VLR and ends at an OK connector. + +4939 + +4940 + +Figure 25.6/1 (sheet 1 of 2): Macro Check\_IMEI\_MSC + +![State transition diagram for macro Check_IMEI_MSC. The diagram shows various states and transitions between them, including inputs like A_CM_RELEASE_ind, MAP_U_ABORT_req, A_DISC_req, and A_CLEAR_CMD_req, and outputs like To EIR, From EIR, and internal actions like Set User Error: System failure. It ends in OK and Error states.](6b1e14f97d1425d42564ddd890cf73b4_img.jpg) + +macrodefinition Check\_IMEI\_MSC + +Chk\_IMEI\_MSC2(2) + +Macro in the MSC to check the IMEI of the MS; and report the result to the VLR + +Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR unless marked otherwise + +``` + +stateDiagram-v2 + [*] --> Wait_For_EIR_Response + state "Wait_For_EIR_Response" as Wait_For_EIR_Response + + Wait_For_EIR_Response --> A_CM_RELEASE_ind + Wait_For_EIR_Response --> MAP_U_ABORT_ind_MAP_CLOSE_ind + Wait_For_EIR_Response --> MAP_NOTICE_ind + Wait_For_EIR_Response --> MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind_from_EIR + + A_CM_RELEASE_ind --> MAP_U_ABORT_req_1[MAP_U_ABORT_req] + MAP_U_ABORT_req_1 --> To_EIR_1[To EIR] + MAP_U_ABORT_req_1 --> MAP_U_ABORT_req_2[MAP_U_ABORT_req] + MAP_U_ABORT_req_2 --> Error_1((Error)) + + MAP_U_ABORT_ind_MAP_CLOSE_ind --> MAP_U_ABORT_req_3[MAP_U_ABORT_req] + MAP_U_ABORT_req_3 --> To_EIR_2[To EIR] + MAP_U_ABORT_req_3 --> A_DISC_req + A_DISC_req --> A_CLEAR_CMD_req + A_CLEAR_CMD_req --> Error_2((Error)) + + MAP_NOTICE_ind --> From_EIR[From EIR] + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> To_EIR_3[To EIR] + + MAP_U_ABORT_ind_MAP_P_ABORT_ind_MAP_CLOSE_ind_from_EIR --> Set_User_Error[Set User Error: System failure] + Set_User_Error --> MAP_CHECK_IMEI_rsp_MAP_DELIMITER_req + MAP_CHECK_IMEI_rsp_MAP_DELIMITER_req --> OK((OK)) + +``` + +State transition diagram for macro Check\_IMEI\_MSC. The diagram shows various states and transitions between them, including inputs like A\_CM\_RELEASE\_ind, MAP\_U\_ABORT\_req, A\_DISC\_req, and A\_CLEAR\_CMD\_req, and outputs like To EIR, From EIR, and internal actions like Set User Error: System failure. It ends in OK and Error states. + +4941 + +4942 + +Figure 25.6/1 (sheet 2 of 2): Macro Check\_IMEI\_MSC + +macrodefinition Check\_IMEI\_VLR + +Chk\_IMEI\_VLR1(1) + +Macro in the VLR to instruct the MSC to check the IMEI of the MS and handle the report of the result + +Signals to/from the left are to/from the MSC; signals to/from the right are to/from the OMC + +![Flowchart for macro Check_IMEI_VLR. It starts with an entry point, followed by a signal request (MAP_CHECK_IMEI_req, MAP_DELIMITER_req) to the left. Then a 'Wait_For_Check_IMEI_REesult' state. A decision point follows: if 'MAP_CHECK_IMEI_cnf' is received from the left, it checks if 'O&M notification required?'. If 'Yes', it sends 'OM_ALARM_req' to the left and then checks if 'Service granted?'. If 'Yes', it ends at 'OK'; if 'No', it ends at 'Error'. If 'No' to the first decision, it ends at 'OK'. If the second signal (MAP_U_ABORT_rind, MAP_CLOSE_ind) is received from the right, it ends at 'Aborted'.](a91e602653dae90e99b0810577600005_img.jpg) + +``` + +graph TD + Start([ ]) --> Request[MAP_CHECK_IMEI_req +MAP_DELIMITER_req] + Request --> Wait[Wait_For +Check_IMEI_ +REesult] + Wait --> Decision1{ } + Decision1 --> CNF[MAP +CHECK_ +IMEI_cnf] + Decision1 --> ABORT[MAP_U_ABORT_rind, +MAP_CLOSE_ind] + CNF --> OandM{O&M +notification +required?} + OandM -- No --> OK1([OK]) + OandM -- Yes --> Alarm[OM_ALARM_ +req] + Alarm --> Service{Service +granted?} + Service -- No --> Error([Error]) + Service -- Yes --> OK2([OK]) + ABORT --> Aborted([Aborted]) + +``` + +Flowchart for macro Check\_IMEI\_VLR. It starts with an entry point, followed by a signal request (MAP\_CHECK\_IMEI\_req, MAP\_DELIMITER\_req) to the left. Then a 'Wait\_For\_Check\_IMEI\_REesult' state. A decision point follows: if 'MAP\_CHECK\_IMEI\_cnf' is received from the left, it checks if 'O&M notification required?'. If 'Yes', it sends 'OM\_ALARM\_req' to the left and then checks if 'Service granted?'. If 'Yes', it ends at 'OK'; if 'No', it ends at 'Error'. If 'No' to the first decision, it ends at 'OK'. If the second signal (MAP\_U\_ABORT\_rind, MAP\_CLOSE\_ind) is received from the right, it ends at 'Aborted'. + +4943 + +4944 + +Figure 25.6/2: Macro Check\_IMEI\_VLR + +process Check\_IMEI\_SGSN + +Chk\_IMEI\_SGSN1(2) + +Process in the SGSN to check the IMEI of an MS + +Signals to/from the left are to/from the application process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/from the EIR + +![Flowchart for process Check_IMEI_SGSN. It starts with 'Idle', followed by 'Check IMEI'. A decision 'BMUEF requested?' leads to two parallel checks: 'IMEI available?' and 'IMEISV available?'. If both are 'Yes', it sends 'MAP_OPEN_req', 'MAP_CHECK_IMEI_req', and 'MAP_DELIMITER_req' to the EIR, then receives 'Open_Cnf'. A decision 'Requested Info includes Equipment status?' follows. If 'Yes', it performs a 'MAP Vr dialogue' with the EIR. The 'Result?' from the dialogue can be 'Success' (leading to 'Check IMEI ack' and back to 'Idle'), 'User Error' (leading to 'Set negative response: System failure' and then to connector '1'), or 'Provider Error, Data Error' (also leading to 'Set negative response: System failure' and connector '1'). If 'No' to the equipment status question, it goes to 'Wait_For_EIR_Response' and then to connector '1'. If 'Error' to the equipment status question, it goes directly to connector '1'. If either 'IMEI available?' or 'IMEISV available?' is 'No', it goes directly to connector '1'.](2fdcbae1c7a6dc2ee6e97c1b5df177b4_img.jpg) + +``` + +graph TD + Start([Idle]) --> CheckIMEI{Check IMEI} + CheckIMEI --> BMUEF{BMUEF requested?} + BMUEF -- No --> IMEIAvailable{IMEI available?} + BMUEF -- Yes --> IMEISVAvailable{IMEISV available?} + IMEIAvailable -- No --> 1((1)) + IMEIAvailable -- Yes --> MAP_Req[MAP_OPEN_req +MAP_CHECK_IMEI_req +MAP_DELIMITER_req] + IMEISVAvailable -- No --> 1 + IMEISVAvailable -- Yes --> MAP_Req + MAP_Req --> OpenCnf[Receive Open_Cnf] + OpenCnf --> RequestedInfo{Requested Info includes Equipment status?} + RequestedInfo -- No --> WaitForResponse([Wait_For_EIR_Response]) + RequestedInfo -- Yes --> MAPVr[Perform MAP Vr dialogue] + RequestedInfo -- Error --> 1 + MAPVr --> Result{Result?} + Result -- Success --> IMEIAck{Check IMEI ack} + IMEIAck --> Idle([Idle]) + Result -- User Error --> NegativeResponse[Set negative response: System failure] + NegativeResponse --> 1 + Result -- "Provider Error, Data Error" --> NegativeResponse + WaitForResponse --> 1 + +``` + +Flowchart for process Check\_IMEI\_SGSN. It starts with 'Idle', followed by 'Check IMEI'. A decision 'BMUEF requested?' leads to two parallel checks: 'IMEI available?' and 'IMEISV available?'. If both are 'Yes', it sends 'MAP\_OPEN\_req', 'MAP\_CHECK\_IMEI\_req', and 'MAP\_DELIMITER\_req' to the EIR, then receives 'Open\_Cnf'. A decision 'Requested Info includes Equipment status?' follows. If 'Yes', it performs a 'MAP Vr dialogue' with the EIR. The 'Result?' from the dialogue can be 'Success' (leading to 'Check IMEI ack' and back to 'Idle'), 'User Error' (leading to 'Set negative response: System failure' and then to connector '1'), or 'Provider Error, Data Error' (also leading to 'Set negative response: System failure' and connector '1'). If 'No' to the equipment status question, it goes to 'Wait\_For\_EIR\_Response' and then to connector '1'. If 'Error' to the equipment status question, it goes directly to connector '1'. If either 'IMEI available?' or 'IMEISV available?' is 'No', it goes directly to connector '1'. + +4945 + +4946 + +Figure 25.6/3 (sheet 1 of 2): Process Check\_IMEI\_SGSN + +![Flowchart for process Check_IMEI_SGSN. It starts with 'Wait_For_EIR_Response'. From here, three paths emerge: 1) Left path: 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' leads to 'Set negative response: System failure' and connector '1'. 2) Middle path: 'MAP_CHECK_IMEI_cnf' leads to 'Check_Confirmation'. From 'Check_Confirmation', 'User Error' leads to connector '1', 'OK' leads to decision 'O&M notification required?'. If 'Yes', 'OM_ALARM_req' leads to 'To OMC' and then to decision 'Service granted?'. If 'No', it leads directly to 'Service granted?'. From 'Service granted?', 'Yes' leads to 'Check IMEI ack' and 'Idle', while 'No' leads to 'Set negative response: System failure' and connector '1'. 3) Right path: 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req', which leads to 'Set negative response: System failure' and connector '1'. All 'Set negative response: System failure' blocks lead to connector '1'. All 'Idle' blocks lead to connector '1'. A 'Provider Error, Data Error' signal is shown between the middle and right paths.](21a0b5ff618c57628a62641fb899dd66_img.jpg) + +process Check\_IMEI\_SGSN + +Chk\_IMEI\_SGSN2(2) + +Process in the SGSN to check the IMEI of an MS + +Signals to/from the left are to/from the application process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/from the EIR + +``` + +graph TD + Start([Wait_For_EIR_Response]) --> MAP_U_ABORT[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + Start --> MAP_CHECK_IMEI_cnf[MAP_CHECK_IMEI_cnf] + Start --> MAP_NOTICE_ind[MAP_NOTICE_ind] + MAP_U_ABORT --> SetNeg1[Set negative response: System failure] + SetNeg1 --> C1((1)) + MAP_CHECK_IMEI_cnf --> CheckConf[Check_Confirmation] + CheckConf -- User Error --> C2((1)) + CheckConf -- OK --> OandMReq{O&M notification required?} + OandMReq -- Yes --> OMAlarm[OM_ALARM_req] + OMAlarm --> ToOMC[To OMC] + ToOMC --> ServiceGranted{Service granted?} + OandMReq -- No --> ServiceGranted + ServiceGranted -- Yes --> CheckIMEIAck[Check IMEI ack] + CheckIMEIAck --> Idle1([Idle]) + ServiceGranted -- No --> SetNeg2[Set negative response: System failure] + SetNeg2 --> C3((1)) + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> SetNeg3[Set negative response: System failure] + SetNeg3 --> C4((1)) + CheckConf -- "Provider Error, Data Error" --> MAP_NOTICE_ind + +``` + +Flowchart for process Check\_IMEI\_SGSN. It starts with 'Wait\_For\_EIR\_Response'. From here, three paths emerge: 1) Left path: 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' leads to 'Set negative response: System failure' and connector '1'. 2) Middle path: 'MAP\_CHECK\_IMEI\_cnf' leads to 'Check\_Confirmation'. From 'Check\_Confirmation', 'User Error' leads to connector '1', 'OK' leads to decision 'O&M notification required?'. If 'Yes', 'OM\_ALARM\_req' leads to 'To OMC' and then to decision 'Service granted?'. If 'No', it leads directly to 'Service granted?'. From 'Service granted?', 'Yes' leads to 'Check IMEI ack' and 'Idle', while 'No' leads to 'Set negative response: System failure' and connector '1'. 3) Right path: 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req', which leads to 'Set negative response: System failure' and connector '1'. All 'Set negative response: System failure' blocks lead to connector '1'. All 'Idle' blocks lead to connector '1'. A 'Provider Error, Data Error' signal is shown between the middle and right paths. + +4947 + +4948 + +Figure 25.6/3 (sheet 2 of 2): Process Check\_IMEI\_SGSN + +![Flowchart for process Check_IMEI_EIR. It starts at 'Idle', receives an 'Open_Ind' primitive, and then branches based on 'OK', 'Error', or 'Vr' outcomes. The 'OK' path leads to 'Wait_For_Service_Primitive', which then branches into 'MAP_NOTICE_ind', 'MAP_CLOSE_req', and 'MAP_CHECK_IMEI_ind'. The 'MAP_CHECK_IMEI_ind' path leads to 'Check_Indication', which then branches based on 'OK' or 'Error'. The 'OK' path leads to 'IMEI known?' decision. If 'Yes', it goes to connector '1'. If 'No', it leads to 'Set User Error: Unknown Equipment', which then leads to 'MAP_CHECK_IMEI_rsp' and 'MAP_CLOSE_req', and finally 'Idle'. The 'Error' path from 'Check_Indication' leads to 'Idle'. The 'Error' path from 'Wait_For_Service_Primitive' leads to 'Perform MAP Vr dialogue', which then leads to connector '1'. The 'Vr' path from 'Wait_For_Service_Primitive' leads to 'Idle'. Connector '1' leads to 'Equipment status requested?' decision. If 'No', it goes to 'Idle'. If 'Yes', it leads to 'Equipment status supported?' decision. If 'No', it goes to 'Idle'. If 'Yes', it leads to 'Set equipment status', which then leads to 'BMUEF requested?' decision. If 'No', it goes to 'Idle'. If 'Yes', it leads to 'BMUEF supported?' decision. If 'No', it goes to 'Idle'. If 'Yes', it leads to 'Set BMUEF', which then leads to 'MAP_CHECK_IMEI_rsp' and 'MAP_CLOSE_req', and finally 'Idle'.](0a75caa32bf3096417c03cfc94efb1f5_img.jpg) + +**process Check\_IMEI\_EIR** **Chk\_IMEI\_EIR1(1)** + +Process in the EIR to check the IMEI of an MS + +Signals to/from the left are to/from the MSC or the SGSN + +``` + +graph TD + Start([Idle]) --> Receive_Ind[Receive_Open_Ind] + Receive_Ind -- OK --> Wait_For_Service_Primitive([Wait_For_Service_Primitive]) + Receive_Ind -- Error --> Perform_MAP_Vr_dialogue[Perform MAP Vr dialogue] + Receive_Ind -- Vr --> Idle1([Idle]) + Wait_For_Service_Primitive --> MAP_NOTICE_ind[/MAP_NOTICE_ind/] + Wait_For_Service_Primitive --> MAP_CLOSE_req[/MAP_CLOSE_req/] + Wait_For_Service_Primitive --> MAP_CHECK_IMEI_ind[/MAP_CHECK_IMEI_ind/] + MAP_NOTICE_ind --> Idle2([Idle]) + MAP_CLOSE_req --> Idle2 + MAP_CHECK_IMEI_ind --> Check_Indication[Check_Indication] + Check_Indication -- OK --> IMEI_known{IMEI known?} + Check_Indication -- Error --> Idle3([Idle]) + IMEI_known -- Yes --> Connector_1((1)) + IMEI_known -- No --> Set_User_Error[Set User Error: Unknown Equipment] + Set_User_Error --> MAP_CHECK_IMEI_rsp[MAP_CHECK_IMEI_rsp] + Set_User_Error --> MAP_CLOSE_req2[/MAP_CLOSE_req/] + MAP_CHECK_IMEI_rsp --> Idle4([Idle]) + MAP_CLOSE_req2 --> Idle4 + Connector_1 --> Equipment_status_requested{Equipment status requested?} + Equipment_status_requested -- No --> Idle5([Idle]) + Equipment_status_requested -- Yes --> Equipment_status_supported{Equipment status supported?} + Equipment_status_supported -- No --> Idle5 + Equipment_status_supported -- Yes --> Set_equipment_status[Set equipment status] + Set_equipment_status --> BMUEF_requested{BMUEF requested?} + BMUEF_requested -- No --> Idle5 + BMUEF_requested -- Yes --> BMUEF_supported{BMUEF supported?} + BMUEF_supported -- No --> Idle5 + BMUEF_supported -- Yes --> Set_BMUEF[Set BMUEF] + Set_BMUEF --> MAP_CHECK_IMEI_rsp2[MAP_CHECK_IMEI_rsp] + Set_BMUEF --> MAP_CLOSE_req3[/MAP_CLOSE_req/] + MAP_CHECK_IMEI_rsp2 --> Idle6([Idle]) + MAP_CLOSE_req3 --> Idle6 + +``` + +Flowchart for process Check\_IMEI\_EIR. It starts at 'Idle', receives an 'Open\_Ind' primitive, and then branches based on 'OK', 'Error', or 'Vr' outcomes. The 'OK' path leads to 'Wait\_For\_Service\_Primitive', which then branches into 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', and 'MAP\_CHECK\_IMEI\_ind'. The 'MAP\_CHECK\_IMEI\_ind' path leads to 'Check\_Indication', which then branches based on 'OK' or 'Error'. The 'OK' path leads to 'IMEI known?' decision. If 'Yes', it goes to connector '1'. If 'No', it leads to 'Set User Error: Unknown Equipment', which then leads to 'MAP\_CHECK\_IMEI\_rsp' and 'MAP\_CLOSE\_req', and finally 'Idle'. The 'Error' path from 'Check\_Indication' leads to 'Idle'. The 'Error' path from 'Wait\_For\_Service\_Primitive' leads to 'Perform MAP Vr dialogue', which then leads to connector '1'. The 'Vr' path from 'Wait\_For\_Service\_Primitive' leads to 'Idle'. Connector '1' leads to 'Equipment status requested?' decision. If 'No', it goes to 'Idle'. If 'Yes', it leads to 'Equipment status supported?' decision. If 'No', it goes to 'Idle'. If 'Yes', it leads to 'Set equipment status', which then leads to 'BMUEF requested?' decision. If 'No', it goes to 'Idle'. If 'Yes', it leads to 'BMUEF supported?' decision. If 'No', it goes to 'Idle'. If 'Yes', it leads to 'Set BMUEF', which then leads to 'MAP\_CHECK\_IMEI\_rsp' and 'MAP\_CLOSE\_req', and finally 'Idle'. + +4949 + +4950 + +Figure 25.6/4: Process Check\_IMEI\_EIR + +![Flowchart for macro Obtain_IMEI_MSC. The process starts with a connector, followed by a signal MAP_OBTAIN_IMEI_ind. A decision 'IMEI available?' follows. If 'Yes', it goes to 'Set IMEI'. If 'No', it goes to 'A_IDENTITY_REQUEST_req' (with 'Requested identity=IMEI'), then 'Wait_For_IMEI'. From 'Wait_For_IMEI', it branches to 'A_IDENTITY_RESPONSE_ind', 'A_CM_RELEASE_ind' (leading to 'Set User Error: System failure'), and an unlabeled signal block (leading to 'Error' and signals MAP_U_ABORT_ind, MAP_CLOSE_ind). All three branches converge to 'Set IMEI', which then leads to another unlabeled signal block (with signals MAP_OBTAIN_IMEI_rsp, MAP_DELIMITER_req) and finally 'OK'.](dc9c6705b711ba1323550e2a75df8454_img.jpg) + +macrodefinition Obtain\_IMEI\_MSC + +Obt\_IMEI\_MSC1(1) + +Macro in the MSC to obtain the IMEI from the MS + +Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR + +``` + +graph TD + Start([ ]) --> S1[MAP_OBTAIN_IMEI_ind] + S1 --> D{IMEI available?} + D -- Yes --> S2[Set IMEI] + D -- No --> S3{A_IDENTITY_REQUEST_req} + S3 --> T1[Requested identity=IMEI] + S3 --> S4([Wait_For_IMEI]) + S4 --> S5{A_IDENTITY_RESPONSE_ind} + S4 --> S6{A_CM_RELEASE_ind} + S4 --> S7[ ] + S6 --> T2[Set User Error: System failure] + S7 --> T3[MAP_U_ABORT_ind, MAP_CLOSE_ind] + S7 --> S8((Error)) + S5 --> S2 + T2 --> S2 + S2 --> S9[ ] + S9 --> T4[MAP_OBTAIN_IMEI_rsp, MAP_DELIMITER_req] + S9 --> S10((OK)) + +``` + +Flowchart for macro Obtain\_IMEI\_MSC. The process starts with a connector, followed by a signal MAP\_OBTAIN\_IMEI\_ind. A decision 'IMEI available?' follows. If 'Yes', it goes to 'Set IMEI'. If 'No', it goes to 'A\_IDENTITY\_REQUEST\_req' (with 'Requested identity=IMEI'), then 'Wait\_For\_IMEI'. From 'Wait\_For\_IMEI', it branches to 'A\_IDENTITY\_RESPONSE\_ind', 'A\_CM\_RELEASE\_ind' (leading to 'Set User Error: System failure'), and an unlabeled signal block (leading to 'Error' and signals MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind). All three branches converge to 'Set IMEI', which then leads to another unlabeled signal block (with signals MAP\_OBTAIN\_IMEI\_rsp, MAP\_DELIMITER\_req) and finally 'OK'. + +4951 + +4952 + +Figure 25.6/5: Macro Obtain\_IMEI\_MSC + +![State transition diagram for macro Obtain_IMEI_VLR. The diagram shows a sequence of states and transitions. It starts with an initial state leading to a transition labeled 'MAP_OBTAIN_IMEI_req' and 'MAP_DELIMITER_req'. This leads to a 'Wait_For_IMEI' state. From this state, a transition labeled 'MAP_OBTAIN_IMEI_cnf' leads to a 'Check Confirmation' state. From 'Check Confirmation', an 'OK' transition leads to an 'OK' state, and a 'User Error, Provider Error, Data Error' transition leads to an 'Error' state. There is also a transition from 'Wait_For_IMEI' to an 'Aborted' state, labeled with 'MAP_U_ABORT_ind' and 'MAP_CLOSE_ind'.](c401b995325dba88808f67e3758152ff_img.jpg) + +macrodefinition Obtain\_IMEI\_VLR + +Obt\_IMEI\_VLR1(1) + +Macro in the VLR to instruct the MSC to obtain the IMEI of the MS and handle the report of the result + +Signals to/from the left are to/from the MSC + +``` + +stateDiagram-v2 + [*] --> Transition1 + state " " as Transition1 + Transition1 --> Wait_For_IMEI + state "Wait_For_IMEI" as Wait_For_IMEI + Wait_For_IMEI --> CheckConfirmation + state "Check Confirmation" as CheckConfirmation + CheckConfirmation --> OK + state "OK" as OK + CheckConfirmation --> Error + state "Error" as Error + Wait_For_IMEI --> Aborted + state "Aborted" as Aborted + Transition1 --> MAP_OBTAIN_IMEI_req + note right of MAP_OBTAIN_IMEI_req: MAP_OBTAIN_IMEI_req +MAP_DELIMITER_req + CheckConfirmation --> MAP_U_ABORT_ind + note right of MAP_U_ABORT_ind: MAP_U_ABORT_ind, +MAP_CLOSE_ind + CheckConfirmation --> UserError + note right of UserError: User Error, +Provider Error, +Data Error + +``` + +State transition diagram for macro Obtain\_IMEI\_VLR. The diagram shows a sequence of states and transitions. It starts with an initial state leading to a transition labeled 'MAP\_OBTAIN\_IMEI\_req' and 'MAP\_DELIMITER\_req'. This leads to a 'Wait\_For\_IMEI' state. From this state, a transition labeled 'MAP\_OBTAIN\_IMEI\_cnf' leads to a 'Check Confirmation' state. From 'Check Confirmation', an 'OK' transition leads to an 'OK' state, and a 'User Error, Provider Error, Data Error' transition leads to an 'Error' state. There is also a transition from 'Wait\_For\_IMEI' to an 'Aborted' state, labeled with 'MAP\_U\_ABORT\_ind' and 'MAP\_CLOSE\_ind'. + +4953 + +4954 + +Figure 25.6/6: Macro Obtain\_IMEI\_VLR + +## 4955 25.7 Insert Subscriber Data macros and processes + +### 4956 25.7.1 Macro Insert\_Subs\_Data\_VLR + +4957 This macro is used by any procedure in the VLR that triggers the reception of subscriber data (e.g. Update Location, +4958 Update VCSG Location or Restore Data). + +### 4959 25.7.2 Macro Insert\_Subs\_Data\_SGSN + +4960 This macro is used by any procedure that triggers the reception of subscriber data (e.g. Update GPRS Location or +4961 Update VCSG Location ). + +### 4962 25.7.3 Process Insert\_Subs\_Data\_Stand\_Alone\_HLR + +4963 This process is used by HLR to transfer subscriber data to the VLR in a stand alone mode, i.e. in a separate dialogue. +4964 This is done whenever a change of subscriber data is performed either by the operator or by the subscriber and this +4965 change has to be reported to the VLR. + +4966 Sheet 1: The HLR may wait for each MAP\_INSERT\_SUBSCRIBER\_DATA request to be acknowledged before it +4967 sends the next request, or it may handle the requests and the confirmations in parallel. + +4968 Sheet 1, sheet 2: If the VLR has indicated that it does not support a service or feature (e.g. Closed User Group or +4969 Advice Of Charge Charging Level) which the HLR operator regards as essential for the subscriber, the macro +4970 Wait\_for\_Insert\_Subs\_Data\_Cnf takes the Replace\_Service exit; the HLR sets the Roaming Restriction Due To +4971 Unsupported Feature flag to roaming restricted and sends Roaming Restriction Due To Unsupported Feature in a +4972 subsequent MAP\_INSERT\_SUBSCRIBER\_DATA request. + +4973 Sheet 1, sheet 2: If the HLR operator does not regard the unsupported service or feature as essential for the subscriber +4974 but the macro Wait\_for\_Insert\_Subs\_Data\_Cnf takes the Replace\_Service exit, the HLR sends the data for a +4975 replacement service in a subsequent MAP\_INSERT\_SUBSCRIBER\_DATA request. + +4976 Sheet 2: It is an operator option whether to repeat the download of subscriber data if the VLR returns an error response. +4977 The number of repeat attempts and the interval between them is also an operator option, depending on the error +4978 response from the VLR. + +4979 If subscriber data for CAMEL Phase 2 or later services are sent to a VLR which does not support the appropriate phase +4980 of CAMEL, the service behaviour may be unpredictable or incorrect. The HLR should therefore ensure that at the +4981 conclusion of a stand alone Insert Subscriber data procedure the data in the VLR do not require a capability that the +4982 VLR does not have. Possible mechanisms to ensure this are described in 3GPP TS 23.078 [98]. + +4983 The HLR should send a Forwarded-to number which is not in E.164 international format to the VLR only when the +4984 HLR has ascertained that the VLR supports CAMEL Phase 2 or later. Thus, the ISD message containing the +4985 Forwarded-to number which is not in E.164 international format shall be sent to the VLR only if the HLR previously +4986 received confirmation from the VLR at Location Update that CAMEL Phase 2 or later is supported. + +### 4987 25.7.4 Process Insert\_GPRS\_Subs\_Data\_Stand\_Alone\_HLR + +4988 This process is used by the HLR to transfer subscriber data from the HLR to the SGSN in a stand alone mode, i.e. in a +4989 separate dialogue. This is done whenever a change of subscriber data is performed either by the operator or by the +4990 subscriber and this change has to be reported to the SGSN. + +4991 Sheet 1: The HLR may wait for each MAP\_INSERT\_SUBSCRIBER\_DATA request to be acknowledged before it +4992 sends the next request, or it may handle the requests and the confirmations in parallel. + +4993 Sheet 1, sheet 2: If the SGSN has indicated that it does not support a service or feature which the HLR operator regards +4994 as essential for the subscriber, the macro Wait\_for\_Insert\_GPRS\_Subs\_Data\_Cnf takes the Replace\_Service exit; the +4995 HLR sets the Roaming Restricted In SGSN Due To Unsupported Feature flag to roaming restricted and sends Roaming +4996 Restricted In SGSN Due To Unsupported Feature in a subsequent MAP\_INSERT\_SUBSCRIBER\_DATA request. + +4997 Sheet 1, sheet 2: If the HLR operator does not regard the unsupported service or feature as essential for the subscriber +4998 but the macro Wait\_for\_Insert\_GPRS\_Subs\_Data\_Cnf takes the Replace\_Service exit, the HLR sends the data for a +4999 replacement service in a subsequent MAP\_INSERT\_SUBSCRIBER\_DATA request. + +5000 Sheet 2: It is an operator option whether to repeat the download of subscriber data if the SGSN returns an error +5001 response. The number of repeat attempts and the interval between them is also an operator option, depending on the +5002 error response from the SGSN. + +### 5003 25.7.5 Macro Wait\_for\_Insert\_Subs\_Data\_Cnf + +5004 This macro is used by any process or macro that describes the handling in the HLR of the transfer of subscriber data to +5005 the VLR (e.g. Update Location or Restore Data). + +### 5006 25.7.6 Macro Wait\_for\_Insert\_GPRS\_Subs\_Data\_Cnf + +5007 This macro is used by any process or macro that describes the handling in the HLR of the transfer of subscriber data to +5008 the SGSN (e.g. Update GPRS Location). + +### 5009 25.7.7 Process Send\_Insert\_Subs\_Data\_HLR + +5010 This process is used by any process or macro in the HLR where a MAP\_INSERT\_SUBSCRIBER\_DATA request is +5011 sent to the VLR or to the SGSN. + +### 5012 25.7.8 Process Insert\_VCSG\_Subs\_Data\_Stand\_Alone\_CSS + +5013 This process is used by the CSS to transfer CSG subscriber data from the CSS to the VLR or the SGSN in a stand alone +5014 mode, i.e. in a separate dialogue. This is done whenever a change of CSG subscriber data in the CSS is performed either +5015 by the operator or by the subscriber and this change has to be reported to the VLR or the SGSN. + +5016 Sheet 1: The CSS may wait for each MAP\_INSERT\_SUBSCRIBER\_DATA request to be acknowledged before it +5017 sends the next request, or it may handle the requests and the confirmations in parallel. + +5018 Sheet 1, sheet 2: If the VLR or the SGSN has indicated that it does not support a service or feature which the CSS +5019 operator regards as essential for the subscriber, the macro Wait\_for\_Insert\_VCSG\_Subs\_Data\_Cnf takes the +5020 Replace\_Service exit. + +5021 Sheet 1, sheet 2: If the CSS operator does not regard the unsupported service or feature as essential for the subscriber +5022 but the macro Wait\_for\_Insert\_VCSG\_Subs\_Data\_Cnf takes the Replace\_Service exit, the CSS sends the data for a +5023 replacement service in a subsequent MAP\_INSERT\_SUBSCRIBER\_DATA request. + +5024 Sheet 2: It is an operator option whether to repeat the download of CSG subscriber data if the VLR or the SGSN returns +5025 an error response. The number of repeat attempts and the interval between them is also an operator option, depending +5026 on the error response from the VLR or the SGSN. + +### 5027 25.7.9 Macro Wait\_for\_Insert\_VCSG\_Subs\_Data\_Cnf + +5028 This macro is used by any process or macro that describes the handling in the CSS of the transfer of CSG subscriber +5029 data to the VLR or to the SGSN (e.g. Update VCSG Location). + +### 5030 25.7.10 Process Send\_Insert\_VCSG\_Subs\_Data\_CSS + +5031 This process is used by any process or macro in the CSS where a MAP\_INSERT\_SUBSCRIBER\_DATA request is sent +5032 to the VLR or to the SGSN. + +5033 + +![Flowchart for Insert_Subs_Data_VLR macro. It starts with an incoming MAP_INSERT_SUBSCRIBER_DATA_ind signal, followed by a 'Check_Indication' block. An 'OK' path leads to a decision 'All received services & features supported?'. If 'Yes', it proceeds to 'Update subscriber data'. If 'No', it proceeds to 'Update subscriber data for supported services & features' and then 'Set parameters for unsupported services & features'. Both paths lead to a decision 'MSC area restricted due to regional subscription?'. If 'Yes', it proceeds to 'Set network node area restricted'. If 'No', it bypasses this block. All paths converge to an output block containing 'MAP_INSERT_SUBSCRIBER_DATA_rsp' and 'MAP_DELIMITER_req', ending at a connector symbol. An 'Error' path from 'Check_Indication' also leads to the output block.](60c66cf2790b64e5d2f34597d8d59fa1_img.jpg) + +macrodefinition Insert\_Subs\_Data\_VLR + +Ins\_Sub\_Dat\_VLR1(1) + +Macro in the VLR to handle an Insert Subscriber Data request from the HLR or the CSS + +Signals to/from the right are to/from the HLR or the CSS + +``` + +graph TD + Start([ ]) --> In{ } + In --> MAP_IN[MAP_INSERT_SUBSCRIBER_DATA_ind] + MAP_IN --> Check[Check_Indication] + Check -- OK --> Decision1{All received services & features supported?} + Check -- Error --> Output + Decision1 -- Yes --> Update1[Update subscriber data] + Decision1 -- No --> Update2[Update subscriber data for supported services & features] + Update2 --> SetParams[Set parameters for unsupported services & features] + Update1 --> Decision2{MSC area restricted due to regional subscription?} + SetParams --> Decision2 + Decision2 -- Yes --> SetRestricted[Set network node area restricted] + SetRestricted --> Output + Decision2 -- No --> Output + Output --> End([ ]) + subgraph Output + direction TB + O1[MAP_INSERT_SUBSCRIBER_DATA_rsp] + O2[MAP_DELIMITER_req] + end + +``` + +Flowchart for Insert\_Subs\_Data\_VLR macro. It starts with an incoming MAP\_INSERT\_SUBSCRIBER\_DATA\_ind signal, followed by a 'Check\_Indication' block. An 'OK' path leads to a decision 'All received services & features supported?'. If 'Yes', it proceeds to 'Update subscriber data'. If 'No', it proceeds to 'Update subscriber data for supported services & features' and then 'Set parameters for unsupported services & features'. Both paths lead to a decision 'MSC area restricted due to regional subscription?'. If 'Yes', it proceeds to 'Set network node area restricted'. If 'No', it bypasses this block. All paths converge to an output block containing 'MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp' and 'MAP\_DELIMITER\_req', ending at a connector symbol. An 'Error' path from 'Check\_Indication' also leads to the output block. + +5034 + +5035 + +Figure 25.7/1: Macro Insert\_Subs\_Data\_VLR + +![Flowchart for Insert_Subs_Data_SGSN macro. It starts with an incoming MAP_INSERT_SUBSCRIBER_DATA_ind signal, followed by a 'Check_Indication' step. If 'OK', it checks if all services and features are supported. If 'Yes', it updates subscriber data. If 'No', it updates data for supported services and sets parameters for unsupported ones. Both paths lead to a decision on whether the SGSN area is restricted. If 'Yes', it sets the network node area as restricted. Finally, it sends a response with MAP_INSERT_SUBSCRIBER_DATA_rsp and MAP_DELIMITER_req. An 'Error' path from 'Check_Indication' leads directly to the response stage.](11fcb90588a977a8dc718244fd07f5eb_img.jpg) + +macrodefinition Insert\_Subs\_Data\_SGSN + +Ins\_Sub\_Dat\_SGSN1(1) + +Macro in the VLR to handle an Insert Subscriber Data request from the HLR or the CSS + +Signals to/from the right are to/from the HLR or the CSS + +``` + +graph TD + Start([ ]) --> In{ } + In --> MAP_ind[MAP_INSERT_SUBSCRIBER_DATA_ind] + MAP_ind --> Check[Check_Indication] + Check -- OK --> AllSupp{All received services & features supported?} + Check -- Error --> Out{ } + AllSupp -- Yes --> UpdateData[Update subscriber data] + AllSupp -- No --> UpdateSupp[Update subscriber data for supported services & features] + UpdateSupp --> SetParams[Set parameters for unsupported services & features] + UpdateData --> Restricted{SGSN area restricted due to regional subscription?} + SetParams --> Restricted + Restricted -- Yes --> SetRestricted[Set network node area restricted] + SetRestricted --> Out + Restricted -- No --> Out + Out --> MAP_rsp[MAP_INSERT_SUBSCRIBER_DATA_rsp +MAP_DELIMITER_req] + MAP_rsp --> End([ ]) + +``` + +Flowchart for Insert\_Subs\_Data\_SGSN macro. It starts with an incoming MAP\_INSERT\_SUBSCRIBER\_DATA\_ind signal, followed by a 'Check\_Indication' step. If 'OK', it checks if all services and features are supported. If 'Yes', it updates subscriber data. If 'No', it updates data for supported services and sets parameters for unsupported ones. Both paths lead to a decision on whether the SGSN area is restricted. If 'Yes', it sets the network node area as restricted. Finally, it sends a response with MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp and MAP\_DELIMITER\_req. An 'Error' path from 'Check\_Indication' leads directly to the response stage. + +5036 + +5037 + +Figure 25.7/2: Macro Insert\_Subs\_Data\_SGSN + +![Flowchart for process Insert_Subs_Data_Stand_Alone_HLR. The process starts at node 5, opens a dialogue, receives confirmation, and then attempts to insert subscriber data. It includes loops for retries and handles various outcomes like OK, Error, and Abort.](bf7348d754a32240520fb34fcd03c5dd_img.jpg) + +**process Insert\_Subs\_Data\_Stand\_Alone\_HLR** **ISD\_SA\_HLR1(2)** + +Process in the HLR to open a dialogue and transfer subscriber data to the VLR + +Signals to/from the left are to/from the VLR + +``` + +graph TD + Start((5)) --> OpenReq{MAP_OPEN_req +MAP_INSERT_SUBSCRIBER_DATA_req +MAP_DELIMITER_req} + OpenReq --> ReceiveOpenCnf[Receive Open_Cnf] + ReceiveOpenCnf --> Decision1{OK / Error / Abort} + Decision1 -- OK --> WaitForInsertCnf[Wait_For_Insert_Subs_Data_Cnf] + Decision1 -- Error --> End1((1)) + Decision1 -- Abort --> End1 + WaitForInsertCnf --> Decision2{OK / Replace_Service / Error} + Decision2 -- OK --> AllDataInserted1{All data inserted?} + Decision2 -- Replace_Service --> SetReplacement[Set replacement service(s)] + SetReplacement --> AllDataInserted1 + Decision2 -- Error --> MAPUAbortReq{MAP_U_ABORT_req} + MAPUAbortReq --> End1 + AllDataInserted1 -- Yes --> End3((3)) + AllDataInserted1 -- No --> Count0[Count:=0] + Count0 --> SendInsertSubsDataHLR[Send_Insert_Subs_Data_HLR] + SendInsertSubsDataHLR --> CountInc[Count:= Count+1] + CountInc --> AllDataInserted2{All data inserted?} + AllDataInserted2 -- Yes --> End2((2)) + AllDataInserted2 -- No --> End4((4)) + PerformMAPVr[Perform MAP Vr dialogue] --> EndX[ ] + style EndX fill:none,stroke:none + +``` + +Flowchart for process Insert\_Subs\_Data\_Stand\_Alone\_HLR. The process starts at node 5, opens a dialogue, receives confirmation, and then attempts to insert subscriber data. It includes loops for retries and handles various outcomes like OK, Error, and Abort. + +5038 + +5039 + +**Figure 25.7/3 (sheet 1 of 2): Process Insert\_Subs\_Data\_Stand\_Alone\_HLR** + +![Flowchart for process Insert_Subs_Data_Stand_Alone_HLR. It starts at connector 2, goes to 'Wait_For_Insert_Subs_Data_Cnf'. From there, four paths emerge: 'Replace_Service' (Count:= Count-1, Set replacement service(s), connector 4), 'OK' (Count:= Count-1, Count>0? decision), 'Error' (MAP_U_ABORT_req, connector 1), and a path to connector 3. From connector 3, it goes to a decision 'Network node area restricted received OR Roaming Restriction due to Unsupported Feature?'. 'No' leads to connector 1. 'Yes' leads to 'MSC Area restricted:= Not restricted' or 'MSC Area restricted:= Restricted', both leading to 'MAP_CLOSE_req'. From 'MAP_CLOSE_req', it goes to 'Repeat update of VLR?'. 'No' leads to a crossed-out path. 'Yes' leads to 'Start repetition timer', 'Wait_For_Repetition_Timer_Expire', 'Repetition timer expired' (Internal), and connector 5.](578d951f22826d7b6df90f5769e1873a_img.jpg) + +**process Insert\_Subs\_Data\_Stand\_Alone\_HLR** **ISD\_SA\_HLR2(2)** + +Process in the HLR to open a dialogue and transfer subscriber data to the VLR + +Signals to/from the left are to/from the VLR + +``` + +graph TD + Start((2)) --> Wait[Wait_For_Insert_Subs_Data_Cnf] + Wait -- Replace_Service --> Count1[Count:= Count-1] + Count1 --> Set[Set replacement service(s)] + Set --> End4((4)) + Wait -- OK --> Count2[Count:= Count-1] + Count2 --> CountGT0{Count>0?} + CountGT0 -- No --> End2((2)) + CountGT0 -- Yes --> End3((3)) + Wait -- Error --> MAPU[MAP_U_ABORT_req] + MAPU --> End1((1)) + Wait --> End3 + End3 --> Restricted{Network node area restricted received OR Roaming Restriction due to Unsupported Feature?} + Restricted -- No --> End1 + Restricted -- Yes --> NotRestricted[MSC Area restricted:= Not restricted] + Restricted -- Yes --> RestrictedYes[MSC Area restricted:= Restricted] + NotRestricted --> MAPClose[MAP_CLOSE_req] + RestrictedYes --> MAPClose + MAPClose --> Repeat{Repeat update of VLR?} + Repeat -- No --> CrossedOut[✗] + Repeat -- Yes --> StartTimer[Start repetition timer] + StartTimer --> WaitTimer[Wait_For_Repetition_Timer_Expire] + WaitTimer --> TimerExpired[Repetition timer expired] + TimerExpired -- Internal --> End5((5)) + +``` + +Flowchart for process Insert\_Subs\_Data\_Stand\_Alone\_HLR. It starts at connector 2, goes to 'Wait\_For\_Insert\_Subs\_Data\_Cnf'. From there, four paths emerge: 'Replace\_Service' (Count:= Count-1, Set replacement service(s), connector 4), 'OK' (Count:= Count-1, Count>0? decision), 'Error' (MAP\_U\_ABORT\_req, connector 1), and a path to connector 3. From connector 3, it goes to a decision 'Network node area restricted received OR Roaming Restriction due to Unsupported Feature?'. 'No' leads to connector 1. 'Yes' leads to 'MSC Area restricted:= Not restricted' or 'MSC Area restricted:= Restricted', both leading to 'MAP\_CLOSE\_req'. From 'MAP\_CLOSE\_req', it goes to 'Repeat update of VLR?'. 'No' leads to a crossed-out path. 'Yes' leads to 'Start repetition timer', 'Wait\_For\_Repetition\_Timer\_Expire', 'Repetition timer expired' (Internal), and connector 5. + +5040 + +5041 + +**Figure 25.7/3 (sheet 2 of 2): Process Insert\_Subs\_Data\_Stand\_Alone\_HLR** + +![Flowchart for process Insert_GPRS_Subs_Data_Stand_Alone_HLR. The process starts at connector 5, opens a dialogue (MAP_OPEN_req, MAP_INSERT_SUBSCRIBER_DATA_req, MAP_DELIMITER_req), receives Open_Cnf, waits for Insert_GPRS_Subs_Data_Cnf, handles replacement services, checks if all data is inserted, sends Insert_Subs_Data_HLR, increments a counter, and checks if all data is inserted again. It ends at connectors 1, 2, 3, or 4 based on the outcome.](5250dd5a75788abbf98d300933b056ae_img.jpg) + +**process Insert\_GPRS\_Subs\_Data\_Stand\_Alone\_HLR** **IGSD\_SA\_HLR1(2)** + +Process in the HLR to open a dialogue and transfer subscriber data to the SGSN + +Signals to/from the left are to/from the SGSN + +``` + +graph TD + 5((5)) --> OpenReq{MAP_OPEN_req +MAP_INSERT_SUBSCRIBER_DATA_req +MAP_DELIMITER_req} + OpenReq --> ReceiveOpenCnf[Receive Open_Cnf] + ReceiveOpenCnf -- OK --> WaitForInsertGPRSSubsDataCnf[Wait_For Insert_GPRS_Subs_Data_Cnf] + WaitForInsertGPRSSubsDataCnf -- "Vr, Error" --> 1((1)) + WaitForInsertGPRSSubsDataCnf -- Abort --> 1 + WaitForInsertGPRSSubsDataCnf -- "Replace_Service" --> SetReplacement[Set replacement service(s)] + SetReplacement --> AllDataInserted1{All data inserted?} + AllDataInserted1 -- No --> Count0[Count:=0] + Count0 --> SendInsertSubsDataHLR[Send Insert_Subs_Data_HLR] + SendInsertSubsDataHLR --> CountPlus1[Count:= Count+1] + CountPlus1 --> AllDataInserted2{All data inserted?} + AllDataInserted2 -- No --> 4((4)) + AllDataInserted2 -- Yes --> 2((2)) + AllDataInserted1 -- Yes --> 3((3)) + SetReplacement -- "Error" --> MAPUAbortReq{MAP_U_ABORT_req} + MAPUAbortReq --> 1 + +``` + +Flowchart for process Insert\_GPRS\_Subs\_Data\_Stand\_Alone\_HLR. The process starts at connector 5, opens a dialogue (MAP\_OPEN\_req, MAP\_INSERT\_SUBSCRIBER\_DATA\_req, MAP\_DELIMITER\_req), receives Open\_Cnf, waits for Insert\_GPRS\_Subs\_Data\_Cnf, handles replacement services, checks if all data is inserted, sends Insert\_Subs\_Data\_HLR, increments a counter, and checks if all data is inserted again. It ends at connectors 1, 2, 3, or 4 based on the outcome. + +5042 + +5043 + +**Figure 25.7/4 (sheet 1 of 2): Process Insert\_GPRS\_Subs\_Data\_Stand\_Alone\_HLR** + +![Flowchart for process Insert_GPRS_Subs_Data_Stand_Alone_HLR. It starts at connector 2, goes to 'Wait_For_Insert_GPRS_Subs_Data_Cnf'. From there, four paths emerge: 'Replace_Service' leads to 'Count:= Count-1' then 'Set replacement service(s)' to connector 4; 'OK' leads to 'Count:= Count-1' then a decision 'Count>0?'. If 'Yes', it goes to connector 2; if 'No', it goes to connector 3. 'Error' leads to 'MAP_U_ABORT_req' then to connector 1. 'Abort' also leads to connector 1. From connector 3, it goes to a decision 'Network node area restricted received OR Roaming Restricted in SGSN due to Unsupported Feature?'. If 'Yes', it goes to 'SGSN Area restricted:= Restricted' then to 'MAP_CLOSE_req'. If 'No', it goes to 'SGSN Area restricted:= Not restricted' then to 'MAP_CLOSE_req'. From 'MAP_CLOSE_req', it goes to connector 1 and then to a decision 'Repeat update of SGSN?'. If 'Yes', it goes to 'Start repetition timer' then 'Wait_For_Repetition_Timer_Expire' (internal signal) then to connector 5. If 'No', the path ends with a cross symbol.](87a2e35a8ce420838d250c7a1ecef202_img.jpg) + +**process Insert\_GPRS\_Subs\_Data\_Stand\_Alone\_HLR** **IGSD\_SA\_HLR2(2)** + +Process in the HLR to open a dialogue and transfer subscriber data to the SGSN + +Signals to/from the left are to/from the SGSN + +``` + +graph TD + 2((2)) --> W[Wait_For_Insert_GPRS_Subs_Data_Cnf] + W -- Replace_Service --> C1[Count:= Count-1] + C1 --> S[Set replacement service(s)] + S --> 4((4)) + W -- OK --> C2[Count:= Count-1] + C2 --> D1{Count>0?} + D1 -- Yes --> 2 + D1 -- No --> 3((3)) + W -- Error --> MA[MAP_U_ABORT_req] + MA --> 1a((1)) + W -- Abort --> 1b((1)) + 3 --> D2{Network node area restricted received OR Roaming Restricted in SGSN due to Unsupported Feature?} + D2 -- Yes --> R[SGSN Area restricted:= Restricted] + D2 -- No --> NR[SGSN Area restricted:= Not restricted] + R --> MC[MAP_CLOSE_req] + NR --> MC + MC --> 1c((1)) + MC --> D3{Repeat update of SGSN?} + D3 -- Yes --> ST[Start repetition timer] + ST --> WRE[Wait_For_Repetition_Timer_Expire] + WRE -- Internal --> 5((5)) + D3 -- No --> X[ ] + style X fill:none,stroke:none + +``` + +Flowchart for process Insert\_GPRS\_Subs\_Data\_Stand\_Alone\_HLR. It starts at connector 2, goes to 'Wait\_For\_Insert\_GPRS\_Subs\_Data\_Cnf'. From there, four paths emerge: 'Replace\_Service' leads to 'Count:= Count-1' then 'Set replacement service(s)' to connector 4; 'OK' leads to 'Count:= Count-1' then a decision 'Count>0?'. If 'Yes', it goes to connector 2; if 'No', it goes to connector 3. 'Error' leads to 'MAP\_U\_ABORT\_req' then to connector 1. 'Abort' also leads to connector 1. From connector 3, it goes to a decision 'Network node area restricted received OR Roaming Restricted in SGSN due to Unsupported Feature?'. If 'Yes', it goes to 'SGSN Area restricted:= Restricted' then to 'MAP\_CLOSE\_req'. If 'No', it goes to 'SGSN Area restricted:= Not restricted' then to 'MAP\_CLOSE\_req'. From 'MAP\_CLOSE\_req', it goes to connector 1 and then to a decision 'Repeat update of SGSN?'. If 'Yes', it goes to 'Start repetition timer' then 'Wait\_For\_Repetition\_Timer\_Expire' (internal signal) then to connector 5. If 'No', the path ends with a cross symbol. + +5044 + +5045 + +Figure 25.7/4 (sheet 2 of 2): Process Insert\_GPRS\_Subs\_Data\_Stand\_Alone\_HLR + +![State transition diagram for macro Wait_For_Insert_Subs_Data_Cnf. It starts with an initial state leading to 'Wait_For_ISD_Cnf'. From there, it branches into three main paths based on incoming signals: MAP_INSERT_SUBSCRIBER_DATA_cnf, a group of MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind, and MAP_NOTICE_ind. The first path leads to 'Check_Confirmation' and then to a decision diamond 'Service unsupported in VLR?'. The second path leads to an 'Abort' state. The third path leads to 'MAP_CLOSE_req' and then to a decision diamond 'Provider Error'. Both 'Service unsupported in VLR?' and 'Provider Error' lead to 'Ignore?' decision diamonds. If 'Yes' to 'Ignore?', it goes to 'OK'. If 'No', it goes to 'Replace service in VLR?' decision diamond. If 'Yes' to that, it goes to 'HLR internal action' and then to 'OK'. If 'No', it goes to 'Replace_Service' and then to an end state.](5041c81f4f739c03bbcdbdef8490c0aa_img.jpg) + +**macrodefinition Wait\_For\_Insert\_Subs\_Data\_Cnf** **WF\_ISD\_Cnf1(1)** + +Macro in the HLR to receive and process the MAP\_INSERT\_SUBSCRIBER\_DATA confirmation + +Signals to/from the left are to/from the VLR + +``` + +stateDiagram-v2 + [*] --> Wait_For_ISD_Cnf + state "MAP_INSERT_SUBSCRIBER_DATA_cnf" as M1 + state "MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind" as M2 + state "MAP_NOTICE_ind" as M3 + Wait_For_ISD_Cnf --> M1 + Wait_For_ISD_Cnf --> M2 + Wait_For_ISD_Cnf --> M3 + M1 --> Check_Confirmation + Check_Confirmation --> Error + Check_Confirmation --> PE{Provider Error} + PE --> Abort + PE --> SE{Service unsupported in VLR?} + SE --> Yes1{Yes} + SE --> No1{No} + Yes1 --> Abort + No1 --> Ignore{Ignore?} + Ignore --> Yes2{Yes} + Ignore --> No2{No} + Yes2 --> OK + No2 --> RS{Replace service in VLR?} + RS --> Yes3{Yes} + RS --> No3{No} + Yes3 --> HLR_action[HLR internal action] + HLR_action --> OK + No3 --> Replace_Service + Replace_Service --> [*] + +``` + +State transition diagram for macro Wait\_For\_Insert\_Subs\_Data\_Cnf. It starts with an initial state leading to 'Wait\_For\_ISD\_Cnf'. From there, it branches into three main paths based on incoming signals: MAP\_INSERT\_SUBSCRIBER\_DATA\_cnf, a group of MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind, and MAP\_NOTICE\_ind. The first path leads to 'Check\_Confirmation' and then to a decision diamond 'Service unsupported in VLR?'. The second path leads to an 'Abort' state. The third path leads to 'MAP\_CLOSE\_req' and then to a decision diamond 'Provider Error'. Both 'Service unsupported in VLR?' and 'Provider Error' lead to 'Ignore?' decision diamonds. If 'Yes' to 'Ignore?', it goes to 'OK'. If 'No', it goes to 'Replace service in VLR?' decision diamond. If 'Yes' to that, it goes to 'HLR internal action' and then to 'OK'. If 'No', it goes to 'Replace\_Service' and then to an end state. + +5046 + +5047 + +**Figure 25.7/5: Macro Wait\_for\_Insert\_Subs\_Data\_Cnf** + +![Flowchart for macrodefinition Wait_For_Insert_GPRS_Subs_Data_Cnf. It starts with an entry point leading to 'Wait_For_IGSD_Cnf'. From there, it branches into three main paths: 1) MAP_INSERT_SUBSCRIBER_DATA_cnf leads to 'Check_Confirmation', which then leads to a decision diamond. 2) A middle path with MAP_U_ABORT_ind, MAP_P_ABORT_ind, and MAP_CLOSE_ind leads to an 'Abort' terminal. 3) MAP_NOTICE_ind leads to MAP_CLOSE_req, which also leads to the decision diamond. The decision diamond has three outcomes: 'User Error, Data Error' leading to 'Error'; 'OK' leading to 'Service unsupported in SGSN?'; and 'Provider Error' leading to 'Abort'. 'Service unsupported in SGSN?' has 'Yes' leading to 'Abort' and 'No' leading to 'Ignore?'. 'Ignore?' has 'Yes' leading to 'OK' and 'No' leading to 'Replace service in SGSN?'. 'Replace service in SGSN?' has 'Yes' leading to 'Replace_Service' and 'No' leading to 'HLR internal action', which then leads to 'OK'.](b8e2571e058a2b0768d3d365d7061b67_img.jpg) + +macrodefinition **Wait\_For\_Insert\_GPRS\_Subs\_Data\_Cnf** WF\_IGSD\_Cnf1(1) + +Macro in the HLR to receive and process the MAP\_INSERT\_SUBSCRIBER\_DATA confirmation + +Signals to/from the left are to/from the SGSN + +``` + + graph TD + Entry([ ]) --> Wait_For_IGSD_Cnf[Wait_For_IGSD_Cnf] + Wait_For_IGSD_Cnf --> Branch(( )) + + Branch --> MAP_INSERT_SUBSCRIBER_DATA_cnf[MAP_INSERT_SUBSCRIBER_DATA_cnf] + MAP_INSERT_SUBSCRIBER_DATA_cnf --> Check_Confirmation[Check_Confirmation] + + Branch --> MiddlePath[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + + Branch --> MAP_NOTICE_ind[MAP_NOTICE_ind] + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + + Check_Confirmation --> Decision{ } + + MiddlePath --> Abort([Abort]) + + MAP_CLOSE_req --> Decision + + Decision -- "User Error, Data Error" --> Error([Error]) + + Decision -- "OK" --> ServiceUnsupported{Service unsupported in SGSN?} + + Decision -- "Provider Error" --> Abort + + ServiceUnsupported -- Yes --> Abort + ServiceUnsupported -- No --> Ignore{Ignore?} + + Ignore -- Yes --> OK([OK]) + Ignore -- No --> ReplaceService{Replace service in SGSN?} + + ReplaceService -- Yes --> Replace_Service[Replace_Service] + + ReplaceService -- No --> HLRInternalAction[HLR internal action] + + HLRInternalAction --> OK + +``` + +Flowchart for macrodefinition Wait\_For\_Insert\_GPRS\_Subs\_Data\_Cnf. It starts with an entry point leading to 'Wait\_For\_IGSD\_Cnf'. From there, it branches into three main paths: 1) MAP\_INSERT\_SUBSCRIBER\_DATA\_cnf leads to 'Check\_Confirmation', which then leads to a decision diamond. 2) A middle path with MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind leads to an 'Abort' terminal. 3) MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req, which also leads to the decision diamond. The decision diamond has three outcomes: 'User Error, Data Error' leading to 'Error'; 'OK' leading to 'Service unsupported in SGSN?'; and 'Provider Error' leading to 'Abort'. 'Service unsupported in SGSN?' has 'Yes' leading to 'Abort' and 'No' leading to 'Ignore?'. 'Ignore?' has 'Yes' leading to 'OK' and 'No' leading to 'Replace service in SGSN?'. 'Replace service in SGSN?' has 'Yes' leading to 'Replace\_Service' and 'No' leading to 'HLR internal action', which then leads to 'OK'. + +5048 + +5049 + +**Figure 25.7/6: Macro Wait\_for\_Insert\_GPRS\_Subs\_Data\_Cnf** + +![UML process diagram for Send_Insert_Subs_Data_HLR. The diagram shows a process box with a title 'Send_Insert_Subs_Data_HLR' and a sub-label 'Send_ISD_HLR1(1)'. Inside the box, there are three callouts: a top-left note stating 'Process in the HLR to send a MAP_INSERT_SUBSCRIBER_DATA request, independently of the invoking process'; a top-right note stating 'Signals to/from the left are to/from the VLR or SGSN'; and a central message box containing 'MAP_INSERT_SUBSCRIBER_DATA_req' and 'MAP_DELIMITER_req'. A vertical lifeline passes through the center, starting with an oval at the top, followed by a left-pointing arrowhead, and ending with an 'X' at the bottom.](48d327b5c662916972f82213c8f25a4a_img.jpg) + +process Send\_Insert\_Subs\_Data\_HLR + +Send\_ISD\_HLR1(1) + +Process in the HLR to send a MAP\_INSERT\_SUBSCRIBER\_DATA request, independently of the invoking process + +Signals to/from the left are to/from the VLR or SGSN + +MAP\_INSERT\_SUBSCRIBER\_DATA\_req +MAP\_DELIMITER\_req + +UML process diagram for Send\_Insert\_Subs\_Data\_HLR. The diagram shows a process box with a title 'Send\_Insert\_Subs\_Data\_HLR' and a sub-label 'Send\_ISD\_HLR1(1)'. Inside the box, there are three callouts: a top-left note stating 'Process in the HLR to send a MAP\_INSERT\_SUBSCRIBER\_DATA request, independently of the invoking process'; a top-right note stating 'Signals to/from the left are to/from the VLR or SGSN'; and a central message box containing 'MAP\_INSERT\_SUBSCRIBER\_DATA\_req' and 'MAP\_DELIMITER\_req'. A vertical lifeline passes through the center, starting with an oval at the top, followed by a left-pointing arrowhead, and ending with an 'X' at the bottom. + +5050 + +5051 + +**Figure 25.7/7: Process Send\_Insert\_Subs\_Data\_HLR** + +![Flowchart for process Insert_VCSG_Subs_Data_Stand_Alone_CSS. It starts at connector 5, sends MAP requests, receives a confirmation, waits, and then attempts to insert subscriber data. It includes decision points for 'All data inserted?' and handles errors and service replacements.](468660ac6a78a5225a9ed117dea1185b_img.jpg) + +process Insert\_VCSG\_Subs\_Data\_Stand\_Alone\_CSS + +IVSD\_SA\_CSS1(2) + +Process in the CSS to open a dialogue and transfer CSG subscriber data to the VLR or the SGSN + +Signals to/from the left are to/from the VLR or the SGSN + +``` + +graph TD + 5((5)) --> Start([Start]) + Start --> SendReq[MAP_OPEN_req +MAP_INSERT_SUBSCRIBER_DATA_req +MAP_DELIMITER_req] + SendReq --> RecvCnf[Receive_Open_Cnf] + RecvCnf -- OK --> Wait[Wait_For_Insert_VCSG_Subs_Data_Cnf] + RecvCnf -- Vr, Error --> Abort[Abort] + Wait --> Decision1{All data inserted?} + Decision1 -- OK --> SetService[Set replacement service(s)] + SetService --> SendInsert[Send_Insert_VCSG_Subs_Data_CSS] + Decision1 -- Error --> MAPUAbort[MAP_U_ABORT_req] + MAPUAbort --> 1((1)) + SendInsert --> Count0[Count:=0] + Count0 --> Decision2{All data inserted?} + Decision2 -- No --> CountInc[Count:=Count+1] + CountInc --> Decision2 + Decision2 -- Yes --> 2((2)) + Decision2 -- No --> 4((4)) + Decision1 -- Yes --> 3((3)) + +``` + +Flowchart for process Insert\_VCSG\_Subs\_Data\_Stand\_Alone\_CSS. It starts at connector 5, sends MAP requests, receives a confirmation, waits, and then attempts to insert subscriber data. It includes decision points for 'All data inserted?' and handles errors and service replacements. + +5052 + +5053 + +Figure 25.7/8 (sheet 1 of 2): Process Insert\_VCSG\_Subs\_Data\_Stand\_Alone\_CSS + +5054 + +![Flowchart for process Insert_VCSG_Subs_Data_Stand_Alone_CSS. It starts at connector 2, goes to Wait_For_Insert_VCSG_Subs_Data_Cnf. From there, four paths emerge: Replace_Service (Count:=Count-1, Set replacement service(s), connector 4), OK (Count:=Count-1, Count>0? Yes to connector 2, No to connector 3), Error (MAP_U_ABORT_req, connector 1), and Abort (connector 1). From connector 3, it goes to MAP_CLOSE_req (connector 1), then Repeat update of VLR or SGSN? Yes/No. Yes leads to Start repetition timer, Wait_For_Repetition_Timer_Expiry, Repetition timer expired (Internal), connector 5. No leads to a crossed-out path.](b1d18f77df1ab590375a74069612121a_img.jpg) + +**process Insert\_VCSG\_Subs\_Data\_Stand\_Alone\_CSS** IVSD\_SA\_CSS2(2) + +Process in the CSS to open a dialogue and transfer CSG subscriber data to the VLR or the SGSN + +Signals to/from the left are to/from the VLR or the SGSN + +``` +graph TD + C2((2)) --> W[Wait_For_Insert_VCSG_Subs_Data_Cnf] + W -- Replace_Service --> C1[Count:=Count-1] + C1 --> S[Set replacement service(s)] + S --> C4((4)) + W -- OK --> C2_2[Count:=Count-1] + C2_2 --> D{Count>0?} + D -- Yes --> C2_3((2)) + D -- No --> C3((3)) + W -- Error --> E{MAP_U_ABORT_req} + E --> C1_1((1)) + W -- Abort --> C1_2((1)) + C3 --> M{MAP_CLOSE_req} + M --> C1_3((1)) + M --> R{Repeat update of VLR or SGSN?} + R -- Yes --> SRT[Start repetition timer] + SRT --> WRT[Wait_For_Repetition_Timer_Expiry] + WRT --> RTE{Repetition timer expired} + RTE -.-> I[Internal] + RTE --> C5((5)) + R -- No --> X[ ] + style X fill:none,stroke:none +``` + +Flowchart for process Insert\_VCSG\_Subs\_Data\_Stand\_Alone\_CSS. It starts at connector 2, goes to Wait\_For\_Insert\_VCSG\_Subs\_Data\_Cnf. From there, four paths emerge: Replace\_Service (Count:=Count-1, Set replacement service(s), connector 4), OK (Count:=Count-1, Count>0? Yes to connector 2, No to connector 3), Error (MAP\_U\_ABORT\_req, connector 1), and Abort (connector 1). From connector 3, it goes to MAP\_CLOSE\_req (connector 1), then Repeat update of VLR or SGSN? Yes/No. Yes leads to Start repetition timer, Wait\_For\_Repetition\_Timer\_Expiry, Repetition timer expired (Internal), connector 5. No leads to a crossed-out path. + +5055 + +5056 + +**Figure 25.7/8 (sheet 2 of 2): Process Insert\_VCSG\_Subs\_Data\_Stand\_Alone\_CSS** + +![Flowchart for macro Wait_For_Insert_VCSG_Subs_Data_Cnf. It starts with an entry point leading to 'Wait_For_IVSD_Cnf'. From there, it branches into 'MAP_INSERT_SUBSCRIBER_DATA_cnf' (which leads to 'Check_Confirmation'), 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind', and 'MAP_NOTICE_ind' (which leads to 'MAP_CLOSE_req'). 'Check_Confirmation' leads to a decision diamond 'Service unsupported in VLR or SGSN?'. If 'User Error, Data Error', it goes to 'Error'. If 'OK', it goes to 'OK'. If 'Yes', it goes to 'Ignore?'. If 'No', it goes to 'Replace service in VLR or SGSN?'. If 'Yes', it goes to 'Replace_Service'. If 'No', it goes to 'CSS internal action'. 'Abort' is also shown as a possible outcome.](21bbf996a829bb6fae2b51ba92676ce3_img.jpg) + +macrodefinition Wait\_For\_Insert\_VCSG\_Subs\_Data\_Cnf + +WF\_IVSD\_Cnf1(1) + +Macro in the CSS to receive and process the MAP\_INSERT\_SUBSCRIBER\_DATA confirmation + +Signals to/from the left are to/from the VLR or the SGSN + +``` + +graph TD + Entry(( )) --> WF_IVSD_Cnf[Wait_For_IVSD_Cnf] + WF_IVSD_Cnf --> MAP_INSERT_SUBSCRIBER_DATA_cnf[MAP_INSERT_SUBSCRIBER_DATA_cnf] + WF_IVSD_Cnf --> MAP_U_ABORT_ind[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind] + WF_IVSD_Cnf --> MAP_NOTICE_ind[MAP_NOTICE_ind] + MAP_INSERT_SUBSCRIBER_DATA_cnf --> Check_Confirmation[Check_Confirmation] + MAP_NOTICE_ind --> MAP_CLOSE_req{MAP_CLOSE_req} + Check_Confirmation --> ServiceUnsupported{Service unsupported in VLR or SGSN?} + ServiceUnsupported -- User Error, Data Error --> Error((Error)) + ServiceUnsupported -- OK --> OK((OK)) + ServiceUnsupported -- Yes --> Ignore{Ignore?} + ServiceUnsupported -- No --> ReplaceService{Replace service in VLR or SGSN?} + Ignore -- Yes --> OK + Ignore -- No --> ReplaceService + ReplaceService -- Yes --> Replace_Service[Replace_Service] + ReplaceService -- No --> CSSInternalAction[CSS internal action] + CSSInternalAction --> OK + MAP_CLOSE_req -- Provider Error --> Abort((Abort)) + +``` + +Flowchart for macro Wait\_For\_Insert\_VCSG\_Subs\_Data\_Cnf. It starts with an entry point leading to 'Wait\_For\_IVSD\_Cnf'. From there, it branches into 'MAP\_INSERT\_SUBSCRIBER\_DATA\_cnf' (which leads to 'Check\_Confirmation'), 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind', and 'MAP\_NOTICE\_ind' (which leads to 'MAP\_CLOSE\_req'). 'Check\_Confirmation' leads to a decision diamond 'Service unsupported in VLR or SGSN?'. If 'User Error, Data Error', it goes to 'Error'. If 'OK', it goes to 'OK'. If 'Yes', it goes to 'Ignore?'. If 'No', it goes to 'Replace service in VLR or SGSN?'. If 'Yes', it goes to 'Replace\_Service'. If 'No', it goes to 'CSS internal action'. 'Abort' is also shown as a possible outcome. + +5057 + +5058 + +Figure 25.7/9: Macro Wait\_for\_Insert\_VCSG\_Subs\_Data\_Cnf + +![UML sequence diagram for process Send_Insert_VCSG_Subs_Data_CSS. The diagram shows a self-call on a lifeline. A note on the left indicates this is a process in the CSS to send a MAP_INSERT_SUBSCRIBER_DATA request. A note on the right indicates signals to/from the left are to/from the VLR or SGSN. The message box contains MAP_INSERT_SUBSCRIBER_DATA_req and MAP_DELIMITER_req. The sequence ends with a destroy marker (X).](ffa32b60aa9e81d116b1baf01de955c0_img.jpg) + +process Send\_Insert\_VCSG\_Subs\_Data\_CSS + +Send\_IVSD\_CSS1(1) + +Process in the CSS to send a +MAP\_INSERT\_SUBSCRIBER\_DATA +request, independently of the +invoking process + +Signals to/from the left +are to/from the VLR or SGSN + +MAP\_INSERT\_SUBSCRIBER\_DATA\_req +MAP\_DELIMITER\_req + +UML sequence diagram for process Send\_Insert\_VCSG\_Subs\_Data\_CSS. The diagram shows a self-call on a lifeline. A note on the left indicates this is a process in the CSS to send a MAP\_INSERT\_SUBSCRIBER\_DATA request. A note on the right indicates signals to/from the left are to/from the VLR or SGSN. The message box contains MAP\_INSERT\_SUBSCRIBER\_DATA\_req and MAP\_DELIMITER\_req. The sequence ends with a destroy marker (X). + +5059 + +5060 + +**Figure 25.7/10: Process Send\_Insert\_VCSG\_Subs\_Data\_CSS** + +## 5061 25.8 Request IMSI Macros + +### 5062 25.8.1 Macro Obtain\_IMSI\_MSC + +5063 This macro describes the handling of the request received from the VLR to provide the IMSI of a subscriber (e.g. at +5064 Location Updating). + +### 5065 25.8.2 Macro Obtain\_IMSI\_VLR + +5066 This macro describes the way VLR requests the MSC the IMSI of a subscriber (e.g. at Location Updating). + +![State transition diagram for Obtain_IMSI_MSC macro. It starts with an initial state, followed by a MAP_PROVIDE_IMSI_ind signal. Then an A_IDENTITY_REQUEST_req is sent to the MS (Requested identity=IMSI). The system then enters a Wait_For_IMSI state. From there, three paths are possible: 1) A_IDENTITY_RESPONSE_ind received, leading to Set IMSI and then a MAP_PROVIDE_IMSI_rsp / MAP_DELIMITER_req signal to the VLR, ending in an OK state. 2) A_CM_RELEASE_ind received, leading to Set User Error: Absent Subscriber and then to the final signal. 3) An error condition (MAP_U_ABORT_ind, MAP_CLOSE_ind) leading to an Error state.](4f1c88f2ca77ac1678f0321255d8e016_img.jpg) + +**macrodefinition Obtain\_IMSI\_MSC** **Obt\_IMSI\_MSC1(1)** + +Macro in the MSC to retrieve the IMSI from the MS and return it to the VLR + +Signals to/from the left are to/from the MS; + signals to/from the right are to/from the VLR + +``` + +stateDiagram-v2 + [*] --> State1 + State1 --> State2: MAP_PROVIDE_IMSI_ind + State2 --> State3: A_IDENTITY_REQUEST_req (Requested identity=IMSI) + State3 --> State4: Wait_For_IMSI + State4 --> State5: A_IDENTITY_RESPONSE_ind + State4 --> State6: A_CM_RELEASE_ind + State4 --> State7: MAP_U_ABORT_ind, MAP_CLOSE_ind + State5 --> State8: Set IMSI + State6 --> State9: Set User Error: Absent Subscriber + State8 --> State10: MAP_PROVIDE_IMSI_rsp, MAP_DELIMITER_req + State9 --> State10 + State10 --> [*]: OK + State7 --> [*]: Error + +``` + +State transition diagram for Obtain\_IMSI\_MSC macro. It starts with an initial state, followed by a MAP\_PROVIDE\_IMSI\_ind signal. Then an A\_IDENTITY\_REQUEST\_req is sent to the MS (Requested identity=IMSI). The system then enters a Wait\_For\_IMSI state. From there, three paths are possible: 1) A\_IDENTITY\_RESPONSE\_ind received, leading to Set IMSI and then a MAP\_PROVIDE\_IMSI\_rsp / MAP\_DELIMITER\_req signal to the VLR, ending in an OK state. 2) A\_CM\_RELEASE\_ind received, leading to Set User Error: Absent Subscriber and then to the final signal. 3) An error condition (MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind) leading to an Error state. + +5067 + +5068 + +Figure 25.8/1: Macro Obtain\_IMSI\_MSC + +![State transition diagram for macro Obtain_IMSI_VLR. The process starts at an initial state, moves to a state where MAP_PROVIDE_IMSI_req and MAP_DELIMITER_req are sent. It then enters a Wait_For_IMSI state. From there, it can receive a MAP_PROVIDE_IMSI_cnf (leading to Check_Confirmation) or a MAP_U_ABORT_ind/MAP_CLOSE_ind (leading to an Aborted state). Check_Confirmation leads to either an OK state, an Error state (due to Provider Error), or an Aborted state (due to User Error or Data Error).](52ef9b2a0200e552b01e12640fe77c22_img.jpg) + +macrodefinition Obtain\_IMSI\_VLR + +Obt\_IMSI\_VLR1(1) + +Macro in the VLR to instruct the MSC to obtain the IMSI of the MS and handle the report of the result + +Signals to/from the left are to/from the MSC + +``` + +stateDiagram-v2 + [*] --> State1 + State1 --> State2 : MAP_PROVIDE_IMSI_req, MAP_DELIMITER_req + State2 --> State3 : Wait_For_IMSI + State3 --> State4 : MAP_PROVIDE_IMSI_cnf + State3 --> State5 : MAP_U_ABORT_ind, MAP_CLOSE_ind + State4 --> State6 : OK + State4 --> State7 : Provider Error + State4 --> State8 : User Error, Data Error + State5 --> State9 : Aborted + State6 --> [*] : OK + State7 --> [*] : Error + State8 --> [*] : Aborted + +``` + +State transition diagram for macro Obtain\_IMSI\_VLR. The process starts at an initial state, moves to a state where MAP\_PROVIDE\_IMSI\_req and MAP\_DELIMITER\_req are sent. It then enters a Wait\_For\_IMSI state. From there, it can receive a MAP\_PROVIDE\_IMSI\_cnf (leading to Check\_Confirmation) or a MAP\_U\_ABORT\_ind/MAP\_CLOSE\_ind (leading to an Aborted state). Check\_Confirmation leads to either an OK state, an Error state (due to Provider Error), or an Aborted state (due to User Error or Data Error). + +5069 + +5070 + +Figure 25.8/2: Macro Obtain\_IMSI\_VLR + +## 5071 25.9 Tracing macros + +### 5072 25.9.1 Macro Trace\_Subscriber\_Activity\_MSC + +5073 This macro shows the handling in the MSC for a request from the VLR to trace the activity of a subscriber. + +### 5074 25.9.2 Macro Trace\_Subscriber\_Activity\_VLR + +5075 This macro is called during the handling of subscriber activity in the VLR to activate tracing if necessary. + +### 5076 25.9.3 Macro Trace\_Subscriber\_Activity\_SGSN + +5077 This macro is called during the handling of subscriber activity in the SGSN to activate tracing if necessary. + +### 5078 25.9.4 Macro Activate\_Tracing\_VLR + +5079 This macro shows the handling in the VLR for a request from the HLR to activate tracing for a subscriber. + +### 5080 25.9.5 Macro Activate\_Tracing\_SGSN + +5081 This macro shows the handling in the SGSN for a request from the HLR to activate tracing for a subscriber. + +### 5082 25.9.6 Macro Control\_Tracing\_With\_VLR\_HLR + +5083 This macro shows the handling in the HLR to activate tracing in the VLR if it is required during a dialogue between the +5084 VLR and the HLR + +### 5085 25.9.7 Macro Control\_Tracing\_With\_SGSN\_HLR + +5086 This macro shows the handling in the HLR to activate tracing in the SGSN if it is required during a dialogue between +5087 the SGSN and the HLR + +![Sequence diagram for Trace_Subscriber_Activity_MSC macro. The diagram shows a vertical flow: a start node (oval), a merge node (chevron), a message box 'MAP_TRACE_SUBSCRIBER_ACTIVITY_ind', a 'Check_Indication' box, a 'Start Activity Tracing' box, and an end node (oval). There are 'OK' and 'Error' labels near the 'Start Activity Tracing' box. Callouts explain the symbols: 'Macro in the MSC to mark the subscriber for tracing' for the start node and 'Signals to/from the right are to/from the VLR' for the message box.](52340e7ce9cd96eda56e52e3f4b52960_img.jpg) + +macrodefinition Trace\_Subscriber\_Activity\_MSC + +Tr\_Sub\_Act\_MSC1(1) + +``` + +sequenceDiagram + participant VLR + Note left of VLR: Macro in the MSC to mark the subscriber for tracing + Note right of VLR: Signals to/from the right are to/from the VLR + VLR->>VLR: MAP_TRACE_SUBSCRIBER_ACTIVITY_ind + Note right of VLR: Check_Indication + Note right of VLR: Start Activity Tracing + Note right of VLR: OK + Note right of VLR: Error + +``` + +Sequence diagram for Trace\_Subscriber\_Activity\_MSC macro. The diagram shows a vertical flow: a start node (oval), a merge node (chevron), a message box 'MAP\_TRACE\_SUBSCRIBER\_ACTIVITY\_ind', a 'Check\_Indication' box, a 'Start Activity Tracing' box, and an end node (oval). There are 'OK' and 'Error' labels near the 'Start Activity Tracing' box. Callouts explain the symbols: 'Macro in the MSC to mark the subscriber for tracing' for the start node and 'Signals to/from the right are to/from the VLR' for the message box. + +5088 + +5089 + +Figure 25.9/1: Macro Trace\_Subscriber\_Activity\_MSC + +![Flowchart for Trace_Subscriber_Activity_VLR macro. It starts with a connector, goes to a decision diamond. If 'False', it ends at another connector. If 'True', it goes to a process box 'Subscriber tracing active', then to a merge connector, then to a process box 'MAP_TRACE_SUBSCRIBER_ACTIVITY_req', and finally to an end connector.](d21c4750abaf6590d9c5b77c6c1ca5af_img.jpg) + +macrodefinition Trace\_Subscriber\_Activity\_VLR + +Tr\_Sub\_Act\_VLR1(1) + +Macro in the VLR to start tracing in the MSC if required + +Signals to/from the left are to/from the MSC + +``` + +graph TD + Start([ ]) --> Decision{ } + Decision -- False --> End([ ]) + Decision -- True --> Process1[Subscriber tracing active] + Process1 --> Merge{ } + Merge --> Process2[MAP_TRACE_SUBSCRIBER_ACTIVITY_req] + Process2 --> End2([ ]) + +``` + +Flowchart for Trace\_Subscriber\_Activity\_VLR macro. It starts with a connector, goes to a decision diamond. If 'False', it ends at another connector. If 'True', it goes to a process box 'Subscriber tracing active', then to a merge connector, then to a process box 'MAP\_TRACE\_SUBSCRIBER\_ACTIVITY\_req', and finally to an end connector. + +5090 + +5091 + +Figure 25.9/2: Macro Trace\_Subscriber\_Activity\_VLR + +macrodefinition Trace\_Subscriber\_Activity\_SGSN + +Tr\_Sub\_Act\_SGSN1(1) + +Macro in the SGSN to start tracing if required + +![Flowchart for Trace_Subscriber_Activity_SGSN macro. It starts with an oval connector, leading to a decision diamond. The 'False' path bypasses a 'Start activity tracing' rectangle. The 'True' path goes through the rectangle and then to a final oval connector. A note 'Subscriber tracing active' is next to the 'True' path.](cd9412899b63b30e0c547d79f35a48c1_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{ }; Decision -- False --> End([ ]); Decision -- True --> Note[Subscriber tracing active]; Decision -- True --> Activity[Start activity tracing]; Activity --> End; +``` + +Flowchart for Trace\_Subscriber\_Activity\_SGSN macro. It starts with an oval connector, leading to a decision diamond. The 'False' path bypasses a 'Start activity tracing' rectangle. The 'True' path goes through the rectangle and then to a final oval connector. A note 'Subscriber tracing active' is next to the 'True' path. + +5092 + +5093 + +Figure 25.9/3: Macro Trace\_Subscriber\_Activity\_SGSN + +macrodefinition Activate\_Tracing\_VLR + +Act\_Tr\_VLR1(1) + +Macro in the VLR to handle a request from the HLR to activate tracing + +Signals to/from the right are to/from the HLR + +![Flowchart for Activate_Tracing_VLR macro. It starts with an entry point, receives MAP_ACTIVATE_TRACE_MODE_ind, checks indication, then checks if subscriber is known. If not known, it sets an error for unidentified subscriber. If known, it checks if tracing is supported. If not supported, it sets an error for facility not supported. If supported, it checks if tracing buffer is full. If full, it sets an error for buffer full. If not full, it sets subscriber tracing active to true. All error paths and the success path lead to a common exit point where MAP_ACTIVATE_TRACE_MODE_rsp and MAP_DELIMITER_req are sent.](25bc80f6f672ad2534ff1e7eae570971_img.jpg) + +``` + +graph TD + Entry([ ]) --> In{ } + In -- "MAP_ACTIVATE_TRACE_MODE_ind" --> In + In --> Check[Check_Indication] + Check --> OK[OK] + OK --> Sub{Subscriber known?} + Sub -- No --> Err1[Set User Error: Unidentified subscriber] + Sub -- Yes --> TracSup{Tracing supported?} + TracSup -- No --> Err2[Set User Error: Facility not supported] + TracSup -- Yes --> TracBuf{Tracing buffer full?} + TracBuf -- Yes --> Err3[Set User Error: Tracing buffer full] + TracBuf -- No --> Success[Subscriber tracing active:= True] + Err1 --> ErrorLine(( )) + Err2 --> ErrorLine + Err3 --> ErrorLine + Success --> ErrorLine + ErrorLine --> Out{ } + Out -- "MAP_ACTIVATE_TRACE_MODE_rsp +MAP_DELIMITER_req" --> Out + Out --> Exit([ ]) + +``` + +Flowchart for Activate\_Tracing\_VLR macro. It starts with an entry point, receives MAP\_ACTIVATE\_TRACE\_MODE\_ind, checks indication, then checks if subscriber is known. If not known, it sets an error for unidentified subscriber. If known, it checks if tracing is supported. If not supported, it sets an error for facility not supported. If supported, it checks if tracing buffer is full. If full, it sets an error for buffer full. If not full, it sets subscriber tracing active to true. All error paths and the success path lead to a common exit point where MAP\_ACTIVATE\_TRACE\_MODE\_rsp and MAP\_DELIMITER\_req are sent. + +5094 + +5095 + +Figure 25.9/4: Macro Activate\_Tracing\_VLR + +![Flowchart for Activate_Tracing_SGSN macro. It starts with an entry point, receives a MAP_ACTIVATE_TRACE_MODE_ind signal, checks an indication, then checks if the subscriber is known. If not known, it sets an 'Unidentified subscriber' error. If known, it checks if tracing is supported. If not supported, it sets a 'Facility not supported' error. If supported, it checks if the tracing buffer is full. If full, it sets a 'Tracing buffer full' error. If not full, it sets 'Subscriber tracing active := True'. All error paths lead to a common exit point. The successful path leads to a merge point where MAP_ACTIVATE_TRACE_MODE_rsp and MAP_DELIMITER_req signals are sent, followed by an exit point.](2fdab9416c9f7b5b14ff97505c4b32c0_img.jpg) + +macrodefinition **Activate\_Tracing\_SGSN** + +**Act\_Tr\_SGSN1(1)** + +Macro in the SGSN to handle a request from the HLR to activate tracing + +Signals to/from the right are to/from the HLR + +``` + + graph TD + Entry([ ]) --> In{ } + In -- "MAP_ACTIVATE_TRACE_MODE_ind" --> In + In --> Check[Check_Indication] + Check -- OK --> Sub{Subscriber known?} + Sub -- No --> Err1[Set User Error: Unidentified subscriber] + Sub -- Yes --> Trac{Tracing supported?} + Trac -- No --> Err4[Set User Error: Facility not supported] + Trac -- Yes --> Buf{Tracing buffer full?} + Buf -- Yes --> Err3[Set User Error: Tracing buffer full] + Buf -- No --> Succ[Subscriber tracing active := True] + Err1 --> Merge(( )) + Succ --> Merge + Err3 --> Merge + Err4 --> Merge + Merge --> Out{ } + Out -- "MAP_ACTIVATE_TRACE_MODE_rsp +MAP_DELIMITER_req" --> Out + Out --> Exit([ ]) + +``` + +Flowchart for Activate\_Tracing\_SGSN macro. It starts with an entry point, receives a MAP\_ACTIVATE\_TRACE\_MODE\_ind signal, checks an indication, then checks if the subscriber is known. If not known, it sets an 'Unidentified subscriber' error. If known, it checks if tracing is supported. If not supported, it sets a 'Facility not supported' error. If supported, it checks if the tracing buffer is full. If full, it sets a 'Tracing buffer full' error. If not full, it sets 'Subscriber tracing active := True'. All error paths lead to a common exit point. The successful path leads to a merge point where MAP\_ACTIVATE\_TRACE\_MODE\_rsp and MAP\_DELIMITER\_req signals are sent, followed by an exit point. + +5096 + +5097 + +**Figure 25.9/5: Macro Activate\_Tracing\_SGSN** + +![Flowchart for macrodefinition Control_Tracing_With_VLR_HLR. The process starts with a decision 'Subscriber tracing active in HLR'. If False, it proceeds to an 'OK' connector. If True, it proceeds to a decision 'Subscriber tracing active in VLR'. If False, it proceeds to a decision 'Subscriber in HPLMN area?'. If No, it proceeds to an 'OK' connector. If Yes, it sends 'MAP_ACTIVATE_TRACE_MODE_req' and 'MAP_DELIMITER_req' to the VLR, then enters 'Wait_For_ATM_Result'. From 'Wait_For_ATM_Result', it branches into three paths: 1) 'MAP_ACTIVATE_TRACE_MODE_cnf' leads to 'Check Confirmation', which then branches into 'OK' (Subscriber tracing active in VLR:= True), 'User Error, Data Error' (Subscriber tracing active in VLR:= False), and 'Provider Error' (Subscriber tracing active in VLR:= False). 2) 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req', which then leads to an 'Error' connector. 3) 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' leads to an 'Error' connector.](cc82244f939e49d9220051a01bbdfa4a_img.jpg) + +macrodefinition Control\_Tracing\_With\_VLR\_HLR + +Ctrl\_Tr\_VLR\_HLR1(1) + +Macro in the HLR to activate tracing in the VLR + +Signals to/from the left are to/from the VLR + +``` + +graph TD + Start([Start]) --> D1{Subscriber tracing active in HLR} + D1 -- False --> OK1((OK)) + D1 -- True --> D2{Subscriber tracing active in VLR} + D2 -- True --> D3{Subscriber in HPLMN area?} + D2 -- False --> D3 + D3 -- No --> OK1 + D3 -- Yes --> Req1[MAP_ACTIVATE_TRACE_MODE_req +MAP_DELIMITER_req] + Req1 --> Wait[Wait_For_ATM_Result] + Wait --> Cnf1[MAP_ACTIVATE_TRACE_MODE_cnf] + Wait --> Ind1[MAP_NOTICE_ind] + Wait --> Ind2[MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind] + Cnf1 --> Check[Check Confirmation] + Check -- OK --> True1[Subscriber tracing active in VLR:= True] + Check -- "User Error, Data Error" --> False1[Subscriber tracing active in VLR:= False] + Check -- "Provider Error" --> False2[Subscriber tracing active in VLR:= False] + True1 --> OK2((OK)) + False1 --> OK2 + False2 --> Error1((Error)) + Ind1 --> Req2[MAP_CLOSE_req] + Req2 --> Error2((Error)) + Ind2 --> Error3((Error)) + +``` + +Flowchart for macrodefinition Control\_Tracing\_With\_VLR\_HLR. The process starts with a decision 'Subscriber tracing active in HLR'. If False, it proceeds to an 'OK' connector. If True, it proceeds to a decision 'Subscriber tracing active in VLR'. If False, it proceeds to a decision 'Subscriber in HPLMN area?'. If No, it proceeds to an 'OK' connector. If Yes, it sends 'MAP\_ACTIVATE\_TRACE\_MODE\_req' and 'MAP\_DELIMITER\_req' to the VLR, then enters 'Wait\_For\_ATM\_Result'. From 'Wait\_For\_ATM\_Result', it branches into three paths: 1) 'MAP\_ACTIVATE\_TRACE\_MODE\_cnf' leads to 'Check Confirmation', which then branches into 'OK' (Subscriber tracing active in VLR:= True), 'User Error, Data Error' (Subscriber tracing active in VLR:= False), and 'Provider Error' (Subscriber tracing active in VLR:= False). 2) 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req', which then leads to an 'Error' connector. 3) 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' leads to an 'Error' connector. + +5098 + +5099 + +Figure 25.9/6: Macro Control\_Tracing\_With\_VLR\_HLR + +![Flowchart for macrodefinition Control_Tracing_With_SGSN_HLR. The process starts with a decision 'Subscriber tracing active in HLR'. If False, it goes to an OK connector. If True, it checks 'Subscriber tracing active in SGSN'. If True, it goes to an OK connector. If False, it checks 'Subscriber in HPLMN area?'. If No, it goes to an OK connector. If Yes, it sends 'MAP_ACTIVATE_TRACE_MODE_req' and 'MAP_DELIMITER_req' to the SGSN, then enters 'Wait_For_ATM_Result'. From there, it handles three cases: 'MAP_ACTIVATE_TRACE_MODE_cnf' leads to 'Check Confirmation' which results in 'Subscriber tracing active in SGSN:= True' (OK) or 'Subscriber tracing active in SGSN:= False' (Error); 'MAP_NOTICE_ind' leads to 'MAP_CLOSE_req' which goes to an Error connector; and a third case with 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' also goes to an Error connector. There are also 'User Error, Data Error' and 'Provider Error' paths from 'Check Confirmation' leading to 'Subscriber tracing active in SGSN:= False' (Error).](7ef58acaae097f1a37dac2a742e93445_img.jpg) + +macrodefinition Control\_Tracing\_With\_SGSN\_HLR + +Ctrl\_Tr\_SGSN\_HLR1(1) + +Macro in the HLR to activate tracing in the SGSN + +Signals to/from the left are to/from the SGSN + +``` + +graph TD + Start([Start]) --> D1{Subscriber tracing active in HLR} + D1 -- False --> OK1((OK)) + D1 -- True --> D2{Subscriber tracing active in SGSN} + D2 -- True --> OK2((OK)) + D2 -- False --> D3{Subscriber in HPLMN area?} + D3 -- No --> OK3((OK)) + D3 -- Yes --> Req1[MAP_ACTIVATE_TRACE_MODE_req +MAP_DELIMITER_req] + Req1 --> Wait[Wait_For_ATM_Result] + Wait --> Cnf1[MAP_ACTIVATE_TRACE_MODE_cnf] + Wait --> Ind1[MAP_NOTICE_ind] + Wait --> Ind2[MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind] + Cnf1 --> Check[Check Confirmation] + Check -- OK --> SubTrue1[Subscriber tracing active in SGSN:= True] + Check -- "User Error, Data Error" --> SubFalse1[Subscriber tracing active in SGSN:= False] + Check -- "Provider Error" --> SubFalse2[Subscriber tracing active in SGSN:= False] + SubTrue1 --> OK4((OK)) + SubFalse1 --> Error1((Error)) + SubFalse2 --> Error2((Error)) + Ind1 --> Req2[MAP_CLOSE_req] + Req2 --> Error3((Error)) + Ind2 --> Error4((Error)) + +``` + +Flowchart for macrodefinition Control\_Tracing\_With\_SGSN\_HLR. The process starts with a decision 'Subscriber tracing active in HLR'. If False, it goes to an OK connector. If True, it checks 'Subscriber tracing active in SGSN'. If True, it goes to an OK connector. If False, it checks 'Subscriber in HPLMN area?'. If No, it goes to an OK connector. If Yes, it sends 'MAP\_ACTIVATE\_TRACE\_MODE\_req' and 'MAP\_DELIMITER\_req' to the SGSN, then enters 'Wait\_For\_ATM\_Result'. From there, it handles three cases: 'MAP\_ACTIVATE\_TRACE\_MODE\_cnf' leads to 'Check Confirmation' which results in 'Subscriber tracing active in SGSN:= True' (OK) or 'Subscriber tracing active in SGSN:= False' (Error); 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req' which goes to an Error connector; and a third case with 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' also goes to an Error connector. There are also 'User Error, Data Error' and 'Provider Error' paths from 'Check Confirmation' leading to 'Subscriber tracing active in SGSN:= False' (Error). + +5100 + +5101 + +Figure 25.9/7: Macro Control\_Tracing\_With\_SGSN\_HLR + +## 5102 25.10 Short Message Alert procedures + +### 5103 25.10.1 Process Subscriber\_Present\_VLR + +5104 The VLR invokes the process Subscriber\_Present\_VLR when the mobile subscriber becomes active. The general +5105 description of the short message alert procedures is in clause 23.4 of the present document. + +### 5106 25.10.2 Process SubscriberPresent\_SGSN + +5107 The SGSN invokes the process Subscriber\_Present\_SGSN when it receives a Page response, a GPRS Attach request or +5108 a Routing area update request message (3GPP TS 24.008 [35]). The general description of the short message alert +5109 procedures is in clause 23.4 of the present document. + +### 5110 25.10.3 Macro Alert\_Service\_Centre\_HLR + +5111 The HLR invokes the macro Alert\_Service\_Centre\_HLR when Service Centre(s) are to be alerted. + +### 5112 25.10.4 Process Alert\_SC\_HLR + +5113 It is an operator option to resend the MAP\_ALERT\_SERVICE\_CENTRE request to the SMS-IWMSC if the alert is +5114 unsuccessful. The number of repeat attempts and the interval between them is also an operator option. The service +5115 centre address should be purged from the MWD list if the alert is consistently unsuccessful. + +![Flowchart for process Subscriber_Present_VLR. It starts with a decision 'MNRF set?'. If 'No', it ends. If 'Yes', it sends MAP_OPEN_req, MAP_READY_FOR_SM_req, and MAP_DELIMITER_req. Then it receives Open_Cnf. From Open_Cnf, it branches: 'Vr' leads to 'Perform MAP Vr dialogue' (ends), 'OK' leads to 'Wait_For_HLR_Response', and 'Error' ends. From 'Wait_For_HLR_Response', it branches: one path leads to a merge point with 'MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind' (ends), and another path leads to a merge point with 'MAP_READY_FOR_SM_cnf' which then leads to 'Check_Confirmation'. From 'Check_Confirmation', 'User Error, Data Error, Provider Error' ends the process, and 'OK' leads to 'Clear MNRF' which ends the process.](9c2c96a367ceb612a79b361b14406173_img.jpg) + +**process Subscriber\_Present\_VLR** **Sub\_Pres\_VLR1(1)** + +Process in the VLR to report to the HLR that the subscriber has become reachable + +Signals to/from the right are to/from the HLR + +``` + + graph TD + Start([ ]) --> MNRF{MNRF set?} + MNRF -- No --> End1((X)) + MNRF -- Yes --> Send[ ] + Send --> SendMsg["MAP_OPEN_req +MAP_READY_FOR_SM_req +MAP_DELIMITER_req"] + SendMsg --> Recv[Receive Open_Cnf] + Recv -- Vr --> Perform[Perform MAP Vr dialogue] + Perform --> End2((X)) + Recv -- OK --> Wait[Wait_For_HLR_Response] + Recv -- Error --> End3((X)) + Wait --> Merge1[ ] + Merge1 --> Merge1Msg["MAP_U_ABORT_ind, +MAP_P_ABORT_ind, +MAP_CLOSE_ind"] + Merge1Msg --> End4((X)) + Wait --> Merge2[ ] + Merge2 --> Merge2Msg["MAP_READY_FOR_SM_cnf"] + Merge2Msg --> Check[Check_Confirmation] + Check -- "User Error, +Data Error, +Provider Error" --> End5((X)) + Check -- OK --> Clear[Clear MNRF] + Clear --> End6((X)) + +``` + +Flowchart for process Subscriber\_Present\_VLR. It starts with a decision 'MNRF set?'. If 'No', it ends. If 'Yes', it sends MAP\_OPEN\_req, MAP\_READY\_FOR\_SM\_req, and MAP\_DELIMITER\_req. Then it receives Open\_Cnf. From Open\_Cnf, it branches: 'Vr' leads to 'Perform MAP Vr dialogue' (ends), 'OK' leads to 'Wait\_For\_HLR\_Response', and 'Error' ends. From 'Wait\_For\_HLR\_Response', it branches: one path leads to a merge point with 'MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind' (ends), and another path leads to a merge point with 'MAP\_READY\_FOR\_SM\_cnf' which then leads to 'Check\_Confirmation'. From 'Check\_Confirmation', 'User Error, Data Error, Provider Error' ends the process, and 'OK' leads to 'Clear MNRF' which ends the process. + +5116 + +5117 + +**Figure 25.10/1: Process Subscriber\_Present\_VLR** + +![State transition diagram for process Subscriber_Present_SGSN. It starts at an initial state, checks if MNRG is set. If 'No', it ends. If 'Yes', it sends MAP requests (OPEN, READY_FOR_SM, DELIMITER) and waits for a response. Upon receiving 'Open_Cnf' with 'OK', it enters a wait state. From 'Wait_For_HLR_Response', it can receive 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', or 'MAP_CLOSE_ind' (leading to an error state), or 'MAP_READY_FOR_SM_cnf'. Upon receiving 'MAP_READY_FOR_SM_cnf', it checks the confirmation. If 'OK', it clears MNRG and ends. If an error ('User Error', 'Data Error', 'Provider Error') occurs, it ends. A 'Vr, Error' from the wait state also leads to an error state.](d9be851f95e31e733ac1f2e8aff74b81_img.jpg) + +**process Subscriber\_Present\_SGSN** **Sub\_Pres\_SGSN1(1)** + +Process in the SGSN to report to the HLR that the subscriber has become reachable + +Signals to/from the right are to/from the HLR + +``` + +stateDiagram-v2 + [*] --> Decision{MNRG set?} + Decision --> [*] : No + Decision --> Send_Requests : Yes + Send_Requests --> Wait_For_HLR_Response + Send_Requests : MAP_OPEN_req, MAP_READY_FOR_SM_req, MAP_DELIMITER_req + Wait_For_HLR_Response --> [*] : OK + Wait_For_HLR_Response --> [*] : Vr, Error + Wait_For_HLR_Response --> Receive_Indications : MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + Wait_For_HLR_Response --> Check_Confirmation : MAP_READY_FOR_SM_cnf + Check_Confirmation --> [*] : OK + Check_Confirmation --> [*] : User Error, Data Error, Provider Error + Check_Confirmation : Clear MNRG + +``` + +State transition diagram for process Subscriber\_Present\_SGSN. It starts at an initial state, checks if MNRG is set. If 'No', it ends. If 'Yes', it sends MAP requests (OPEN, READY\_FOR\_SM, DELIMITER) and waits for a response. Upon receiving 'Open\_Cnf' with 'OK', it enters a wait state. From 'Wait\_For\_HLR\_Response', it can receive 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', or 'MAP\_CLOSE\_ind' (leading to an error state), or 'MAP\_READY\_FOR\_SM\_cnf'. Upon receiving 'MAP\_READY\_FOR\_SM\_cnf', it checks the confirmation. If 'OK', it clears MNRG and ends. If an error ('User Error', 'Data Error', 'Provider Error') occurs, it ends. A 'Vr, Error' from the wait state also leads to an error state. + +5118 + +5119 + +Figure 25.10/2: Process Subscriber\_Present\_SGSN + +![Flowchart for macrodefinition Alert_Service_Centre_HLR. It starts with a connector, followed by a decision 'All MWD list entries processed?'. If 'Yes', it ends at an exit connector. If 'No', it goes to a process 'Alert_SC_HLR' and loops back to the start.](729c3e337f4826f94d4d07841eb88323_img.jpg) + +macrodefinition Alert\_Service\_Centre\_HLR + +AI\_Serv\_Ctr\_HLR1(1) + +``` +graph TD; Start([ ]) --> Decision{All MWD list entries processed?}; Decision -- Yes --> End([ ]); Decision -- No --> Process[Alert_SC_HLR]; Process --> Start; +``` + +Macro in the HLR to alert all Short Message Service centres with entries in the MWD list + +Flowchart for macrodefinition Alert\_Service\_Centre\_HLR. It starts with a connector, followed by a decision 'All MWD list entries processed?'. If 'Yes', it ends at an exit connector. If 'No', it goes to a process 'Alert\_SC\_HLR' and loops back to the start. + +5120 + +5121 + +Figure 25.10/3: Macro Alert\_Service\_Centre\_HLR + +![State transition diagram for process Alert_SC_HLR. The process starts in an initial state, transitions to 'Wait_For_Repeat_Timer_Expiry', then to 'Repeat timer expired' (triggered by 'Internal'). From there, it sends 'MAP_OPEN_req', 'MAP_ALERT_SERVICE_CENTRE_req', and 'MAP_DELIMITER_req' via a merge node. It then receives 'Open_Cnf' via a receive node. From 'Open_Cnf', an 'Error' leads to a dead state, 'OK' leads to 'Wait_For_Alert_SC_Response', and 'Vr' leads to 'Perform MAP Vr dialogue' (which also leads to a dead state). From 'Wait_For_Alert_SC_Response', a merge node leads to three paths: one with 'MAP_U_ABORT_ind', 'MAP_P_ABORT_ind', and 'MAP_CLOSE_ind'; another with 'MAP_NOTICE_ind' leading to 'MAP_CLOSE_req'; and a third with 'MAP_ALERT_SERVICE_CENTRE_cnf' leading to 'Check_Confirmation'. 'Check_Confirmation' leads to a decision diamond: 'User Error, Data Error, Provider Error' (No) leads to 'Remove SC address from MWD list?' which leads to 'Remove SC address from MWD list' and then to a dead state; 'OK' (Yes) leads to 'Repeat attempt?'. 'Repeat attempt?' (Yes) leads to 'Start repeat timer' and then back to 'Wait_For_Repeat_Timer_Expiry'; (No) leads to a dead state. The 'MAP_CLOSE_req' path also leads to a dead state.](8e14633000b27e10f59cd10539d49a6e_img.jpg) + +**process Alert\_SC\_HLR** **ASC\_HLR1(1)** + +``` + +stateDiagram-v2 + [*] --> Wait_For_Repeat_Timer_Expiry + state "Internal" as Internal + Internal --> Repeat_timer_expired : Repeat timer expired + Wait_For_Repeat_Timer_Expiry --> Repeat_timer_expired + Repeat_timer_expired --> Merge1{ } + Merge1 --> MAP_OPEN_req : MAP_OPEN_req, MAP_ALERT_SERVICE_CENTRE_req, MAP_DELIMITER_req + MAP_OPEN_req --> Receive_Open_Cnf : Receive_Open_Cnf + Receive_Open_Cnf --> Error : Error + Receive_Open_Cnf --> Wait_For_Alert_SC_Response : OK + Receive_Open_Cnf --> Perform_MAP_Vr_dialogue : Vr + Perform_MAP_Vr_dialogue --> [*] : + Wait_For_Alert_SC_Response --> Merge2{ } + Merge2 --> MAP_U_ABORT_ind : MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind + Merge2 --> MAP_NOTICE_ind : MAP_NOTICE_ind + Merge2 --> MAP_ALERT_SERVICE_CENTRE_cnf : MAP_ALERT_SERVICE_CENTRE_cnf + MAP_NOTICE_ind --> MAP_CLOSE_req : MAP_CLOSE_req + MAP_ALERT_SERVICE_CENTRE_cnf --> Check_Confirmation : Check_Confirmation + Check_Confirmation --> Decision1{ } + Decision1 --> Remove_SC_address_from_MWD_list : User Error, Data Error, Provider Error (No) + Decision1 --> Repeat_attempt : OK (Yes) + Remove_SC_address_from_MWD_list --> [*] : + Repeat_attempt --> Start_repeat_timer : Yes + Repeat_attempt --> [*] : No + Start_repeat_timer --> Wait_For_Repeat_Timer_Expiry + MAP_CLOSE_req --> [*] : + +``` + +Process in the HLR to alert a Short Message Service centre + +Signals to/from the right are to/from the SMS-IWMSC + +State transition diagram for process Alert\_SC\_HLR. The process starts in an initial state, transitions to 'Wait\_For\_Repeat\_Timer\_Expiry', then to 'Repeat timer expired' (triggered by 'Internal'). From there, it sends 'MAP\_OPEN\_req', 'MAP\_ALERT\_SERVICE\_CENTRE\_req', and 'MAP\_DELIMITER\_req' via a merge node. It then receives 'Open\_Cnf' via a receive node. From 'Open\_Cnf', an 'Error' leads to a dead state, 'OK' leads to 'Wait\_For\_Alert\_SC\_Response', and 'Vr' leads to 'Perform MAP Vr dialogue' (which also leads to a dead state). From 'Wait\_For\_Alert\_SC\_Response', a merge node leads to three paths: one with 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind'; another with 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req'; and a third with 'MAP\_ALERT\_SERVICE\_CENTRE\_cnf' leading to 'Check\_Confirmation'. 'Check\_Confirmation' leads to a decision diamond: 'User Error, Data Error, Provider Error' (No) leads to 'Remove SC address from MWD list?' which leads to 'Remove SC address from MWD list' and then to a dead state; 'OK' (Yes) leads to 'Repeat attempt?'. 'Repeat attempt?' (Yes) leads to 'Start repeat timer' and then back to 'Wait\_For\_Repeat\_Timer\_Expiry'; (No) leads to a dead state. The 'MAP\_CLOSE\_req' path also leads to a dead state. + +5122 + +5123 + +**Figure 25.10/4: Process Alert\_SC\_HLR** + +5124 **Annex A (informative):** + +5125 **ASN.1 Cross-reference listing and fully expanded sources** + +5126 The ASN.1 Cross-reference listing and the fully expanded ASN.1 sources of the MAP protocol are provided for + +5127 information at [http://www.3gpp.org/ftp/Specs/archive/29\\_series/29.002/ASN.1/](http://www.3gpp.org/ftp/Specs/archive/29_series/29.002/ASN.1/) + +--- + +5128 Annex B (informative): +5129 Void + +--- + +## 5130 Annex C (informative): 5131 Message Segmentation Mechanisms + +5132 Various segmentation mechanisms are in use to overcome the problem where a MAP parameter carried in an Invoke, +5133 Result (or Error) component is too long to fit into a single SCCP UDT message. These mechanisms are: + +### 5134 C.1 SCCP segmentation + +5135 Instead of one UDT message several XUDT messages are used according to + +5136 Signalling Connection Control Part, Signalling System no. 7 ITU-T recommendation (07/96) Q.711 to Q.716 +5137 ('White Book SCCP'). + +5138 This mechanism may be used for all MAP messages. If no segmentation mechanism at the TCAP or MAP level is +5139 available, this is the only remaining possibility. + +5140 This mechanism has no impact on the MAP provider level and above; the MAP provider sees the parameter as being +5141 sent in a single segment. + +5142 It should be noted that not all SCCP transit nodes (world wide) currently support the transfer of XUDT messages. +5143 Therefore XUDT messages may be lost without notice, depending on the route the message takes. The routes which +5144 successive messages take between two end points can differ because of load balancing. It is therefore recommended that +5145 this mechanism is used only for: + +5146 a) messages which do not cross PLMN boundaries (when the PLMN operator ensures that all SCCP transit nodes +5147 within his PLMN support White Book SCCP) + +5148 b) messages with low priority i.e. loss of the message does not result in serious misoperation. + +5149 It should be noted that the decision whether or not a message crosses PLMN boundaries needs to be taken at the MAP +5150 application level; it is therefore based on the message's operation code rather than on the SCCP called party address, i.e. +5151 only messages which never cross PLMN boundaries due to the type of message (SendIdentification, SendRoutingInfo +5152 without OR, AnyTimeInterrogation, ...) can be regarded as not crossing PLMN boundaries. + +### 5153 C.2 TCAP segmentation + +5154 At the TCAP level the following segmentation mechanisms are available: + +#### 5155 C.2.1 Empty Begin + +5156 In a dialogue with AC version >1 the first forward message (Begin) must contain a Dialogue Portion. Instead of sending +5157 the Dialogue Portion and the Component Portion in the first forward message, an empty Begin (i.e. without a +5158 Component Portion) is sent, followed (after successful dialogue establishment) by a Continue message which can carry +5159 a longer Component Portion since no Dialogue Portion is present in the second forward message. + +#### 5160 C.2.2 Empty Continue + +5161 In a dialogue with AC version >1 the first backward message (Continue / End) must contain a Dialogue Portion. Instead +5162 of sending the Dialogue Portion and the Component Portion in the first backward message, an empty Continue (i.e. +5163 without a Component Portion) is sent, followed by a Continue/End message which can carry a longer Component +5164 Portion since no Dialogue Portion is present in the second backward message. + +#### 5165 C.2.3 TC-Result-NL + +5166 A Result component may be segmented into one or several Result-Not-Last components followed by a Result-Last +5167 component. As specified in clause 15.6.3, the MAP user parameter shall be split so that each segment is compatible +5168 with the type defined for the parameter of the result of the associated operation. + +5169 Note that this segmentation mechanism runs the risk that the message carrying the Result-Last component arrives +5170 before the message carrying a Result-Not-Last component which results in failure. The use of SCCP class 1 "Sequence +5171 guaranteed", which raises the chance of in sequence delivery, is recommended. + +## 5172 C.3 MAP Segmentation + +5173 At the MAP level the following segmentation mechanisms are available: + +### 5174 C.3.1 Invoke without explicit indication + +5175 An Invoke component may be segmented into several Invoke components. These may be sent in burst mode (in which +5176 case SCCP class 1 is recommended) or in acknowledged mode. The receiving node does not get an indication of +5177 whether or not more segments will be received, so it must not close the dialogue. The MAP user parameter shall be split +5178 so that each segment is compatible with the type defined for the parameter of the invoke of the associated operation. + +### 5179 C.3.2 Invoke with explicit indication + +5180 An Invoke component may be segmented into several Invoke components sent in acknowledged mode. Each +5181 component contains at the MAP level an indication of whether or not subsequent components will follow. The receiving +5182 node terminates the dialogue when the last component is received. The MAP user parameter shall be split so that each +5183 segment is compatible with the type defined for the parameter of the invoke of the associated operation. + +### 5184 C.3.3 Result + +5185 A Result (last) component may be segmented into several Result (last) components sent in acknowledged mode where a +5186 new (empty) Invoke component serves as an acknowledgment. The last segment is not acknowledged. The MAP user +5187 parameter shall be split so that each segment is compatible with the type defined for the parameter of the result of the +5188 associated operation. + +5189 The following tables show the applicability of the mechanisms described above: + +5190 + +**AC Version 4:** + +| Parameter | SCCP-segmentation | Empty Begin | Empty Continue | TC-Result-NL | Invoke without indication | Invoke with indication | Result | +|-----------------------|--------------------------|--------------------|-----------------------|---------------------|----------------------------------|-------------------------------|---------------| +| ResumeCallHandlingArg | allowed | not allowed | n.a. | n.a. | not allowed | recommended | n.a. | + +5191 + +5192 + +**AC Version 3:** + +| Parameter | SCCP-segmentation | Empty Begin | Empty Continue | TC-Result-NL | Invoke without indication | Invoke with indication | Result | +|-------------------------------------|--------------------------|--------------------|-----------------------|---------------------|----------------------------------|-------------------------------|---------------| +| InsertSubscriberDataArg | risky | not allowed | n.a. | n.a. | recommended | n.a. | n.a. | +| SendIdentificationRes | allowed | n.a. | not allowed | not allowed | n.a. | n.a. | recommended | +| PrepareHO-Arg | allowed | not allowed | n.a. | n.a. | not allowed | n.a. | n.a. | +| PrepareHO-Res | allowed | n.a. | recommended | not recommended | n.a. | n.a. | not allowed | +| ProcessAccessSignalling-Arg | allowed | n.a. | n.a. | n.a. | not allowed | n.a. | n.a. | +| ForwardAccessSignalling-Arg | allowed | n.a. | n.a. | n.a. | not allowed | n.a. | n.a. | +| PrepareSubsequentHO-Arg | allowed | n.a. | n.a. | n.a. | not allowed | n.a. | n.a. | +| PrepareSubsequentHO-Res | allowed | n.a. | n.a. | not recommended | n.a. | n.a. | not allowed | +| SendAuthenticationInfoRes | risky | n.a. | not allowed | not allowed | n.a. | n.a. | recommended | +| ProvideSubscriberInfoRes | allowed | n.a. | not allowed | not recommended | n.a. | n.a. | not allowed | +| AnyTimeInterrogationRes | allowed | n.a. | not allowed | not recommended | n.a. | n.a. | not allowed | +| AnyTimeModificationRes | allowed | n.a. | not allowed | recommended | n.a. | n.a. | not allowed | +| AnyTimeSubscriptionInterrogationRes | allowed | n.a. | not allowed | recommended | n.a. | n.a. | not allowed | +| noteSubscriberDataModifiedArg | allowed | not allowed | n.a. | n.a. | not allowed | recommended | n.a. | +| SendRoutingInfoRes | allowed | n.a. | not allowed | recommended | n.a. | n.a. | not allowed | +| MO-ForwardSM-Arg | risky | recommended | n.a. | n.a. | not allowed | n.a. | n.a. | +| MT-ForwardSM-Arg | risky | recommended | n.a. | n.a. | not allowed | n.a. | n.a. | + +5193 + +5194 + +**AC Version 2:** + +| Parameter | SCCP-segmentation | Empty Begin | Empty Continue | TC-Result-NL | Invoke without indication | Invoke with indication | Result | +|---------------------------|--------------------------|--------------------|-----------------------|---------------------|----------------------------------|-------------------------------|---------------| +| InsertSubscriberDataArg | risky | not allowed | not allowed | n.a. | recommended | n.a. | n.a. | +| SendIdentificationRes | allowed | n.a. | not allowed | not recommended | n.a. | n.a. | not allowed | +| SendAuthenticationInfoRes | risky | n.a. | not allowed | not recommended | n.a. | n.a. | not allowed | +| ForwardSM-Arg | risky | recommended | n.a. | n.a. | not allowed | n.a. | n.a. | +| PrepareHO-Res | allowed | n.a. | recommended | not recommended | n.a. | n.a. | not allowed | + +5195 + +5196 + +### AC Version 1: + +| Parameter | SCCP-segmentation | Empty Begin | Empty Continue | TC-Result-NL | Invoke without indication | Invoke with indication | Result | +|-------------------------|-------------------|-------------|----------------|--------------|---------------------------|------------------------|-------------| +| InsertSubscriberDataArg | risky | n.a. | n.a. | n.a. | recommended | n.a. | n.a. | +| SentParameterList | risky | n.a. | n.a. | recommended | n.a. | n.a. | not allowed | + +5197 + +5198 In the tables above the keywords "recommended", "allowed", "risky", "not recommended", "not allowed" and "n.a." are used as follows: + +5199 **"recommended"** + +5200 indicates that the normative part of this specification explicitly specifies the use of this mechanism for the parameter in question; + +5201 **"allowed"** + +5202 indicates that the normative part of this specification allows the use of this mechanism for the sending node and mandates support of this mechanism for the receiving node; + +5203 **"risky"** + +5204 indicates that the mechanism is "allowed". However, the use of this mechanism for the parameter in question may result in serious misoperation because SCCP transit nodes are +5205 not guaranteed to support XUDT messages. + +5206 **"not recommended"** + +5207 indicates that the normative part of this specification does not explicitly specify the use of this mechanism for the parameter in question. + +5208 **"not allowed"** + +5209 indicates that the normative part of this specification implicitly prohibits the use of this mechanism for the parameter in question. + +5210 **"n.a."** + +5211 indicates that the mechanism is not applicable for the parameter in question. + +5212 + +--- + +5213 Annex D (informative): Void + +5214 **Annex E (informative):** + 5215 **Change History** + +5216 + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|------|-------|-----------|------|-----|----------------------------------------------------------------------------------------------------|-------| +| | 04 | N2-99227 | A002 | 3 | Use of E interface | 3.1.0 | +| | 04 | N2-99578 | A003 | | Introduction of TIF-CSI for Call Deflection | 3.1.0 | +| | 04 | N2-99233 | A004 | | Clarification in ASN.1 encoding of O-CSI and T-CSI | 3.1.0 | +| | 04 | N2-99269 | A005 | | Introduction of MSISDN in USSD operation | 3.1.0 | +| | 04 | N2-99650 | A006 | | Modification of the O-CSI ASN.1 structure | 3.1.0 | +| | 04 | N2-99250 | A007 | | Adding of MAP_DELIMITER_req to the Status report operation | 3.1.0 | +| | 04 | N2-99628 | A008 | | Correction to the Purge MS "Detailed procedure in the HLR" | 3.1.0 | +| | 04 | N2-99677 | A009 | | Adding of MNP-indicator to the SRI ack | 3.1.0 | +| | 04 | N2-99228 | A010 | | New subscription options for call forwarding | 3.1.0 | +| | 04 | N2-99585 | A011 | | Adding the support of ANSI SCCP which is required in North America (World Zone 1) | 3.1.0 | +| | 04 | N2-99515 | A012 | | Introduction of 3-digit MNCs correction | 3.1.0 | +| | 04 | N2-99520 | A013 | | Export of NAEA-CIC | 3.1.0 | +| | 04 | N2-99548 | A014 | | Clarification to text to identify how the LSA data relevant in the current VPLMN can be determined | 3.1.0 | +| | 04 | 3C99-468 | A015 | | Alignment with 04.80 | 3.1.0 | +| | 04 | N2-99519 | A016 | | VBS data | 3.1.0 | +| | 04 | N2-99461 | A017 | | Introduction of Data Missing error to the Resume Call Handling | 3.1.0 | +| | 04 | N2-99583 | A018 | | Removal of 3-digit MNCs | 3.1.0 | +| | 04 | N2-99676 | A019 | | Corrections of mapping from MAP service to TC service | 3.1.0 | +| | 04 | 3C99-206 | A020 | | Introduction of UUS service to Resume Call Handling | 3.1.0 | +| | 05 | N2-99906 | 021 | | Clarification on VLR CAMEL Subscription Info | 3.2.0 | +| | 05 | N2-99908 | 022 | | Clarification on DestinationNumberCriteria | 3.2.0 | +| | 05 | N2-99910 | 023 | | Removal of TDP-Criteria from RCH | 3.2.0 | +| | 05 | N2-99934 | 025 | | Various corrections related to GGSN-HLR Interface. | 3.2.0 | +| | 05 | N2-99936 | 034 | | Update Location handling for GPRS-only subscription | 3.2.0 | +| | 05 | N2-99938 | 035 | | Correction of OP & AC definitions for NoteMS-PresentForGPRS | 3.2.0 | +| | 05 | N2-99952 | 036 | | Removal of redundant information from RCH | 3.2.0 | +| | 05 | N2-99956 | 026 | | OR capability IE in PRN | 3.2.0 | +| | 05 | N2-99964 | 024 | 1 | GSMSC-CAMEL phase 2 support IE in PRN | 3.2.0 | +| | 05 | N2-99A19 | 028 | | Alignment of 29.002 with 02.67 | 3.2.0 | +| | 05 | N2-99A45 | 029 | 1 | Non-CAMEL IST implementation | 3.2.0 | +| | 05 | N2-99B57 | 027 | 2 | Addition of the information elements and the ASN.1 definitions for Pre-paging | 3.2.0 | +| | 05 | N2-99C27 | 042 | | Clarification on 'Supported CAMEL Phases' in ISD ack | 3.2.0 | +| | 05 | N2-99C78 | 044 | | Editing error correction on VLR capabilities | 3.2.0 | +| | 05 | N2-99D06 | 043 | 1 | Addition of exception handling to the CancellationType | 3.2.0 | +| | 05 | N2-99D33 | 046 | | Clarification of LR-REJECT cause corresponding to RoamingRestrictionDueToUnsupportedFeature | 3.2.0 | +| | 05 | N2-99D35 | 047 | | Clarification of returning the MSISDN in SRIack | 3.2.0 | +| | 06 | N2-99G06 | 033 | 3 | Introduction of the Super-Charger Concept in TS 29.002 | 3.3.0 | +| | 06 | N2-99G18 | 032 | 2 | Introduction of White Book SCCP in MAP | 3.3.0 | +| | 06 | N2-99G50 | 070 | | Addition of GGSN number for the SRIforGPRS | 3.3.0 | +| | 06 | N2-99J88 | 075 | 1 | Introduction of Follow Me | 3.3.0 | +| | 06 | N2-99K12 | 077 | | Use of SSN for GPRS | 3.3.0 | +| | 06 | N2-99K24 | 069 | | Correction of the USSD procedure in the HLR. | 3.3.0 | +| | 06 | N2-99K52 | 060 | 1 | MAP Impacts for Location Services (LCS) | 3.3.0 | +| | 06 | N2-99K58 | 045 | 4 | Authentication Enhancements | 3.3.0 | +| | 06 | N2-99K60 | 050 | 5 | QoS-Subscribed field modification | 3.3.0 | +| | 06 | N2-99L20 | 073 | 1 | Introduction of CAMEL Phase 3 in 3GPP TS 29.002 | 3.3.0 | +| | 06 | N2-99J52 | 074 | | Restructuring of MAP Location Management Procedures for the Circuit Switched Domain | 3.3.0 | +| | 06 | N2-99J92 | 068 | | Update of SDIs to support Super-Charger | 3.3.0 | +| | | | | | New version created to fix a CR implementation error | 3.3.1 | +| | 07 | N2B000436 | 048 | 5 | Introduction of Multicall | 3.4.0 | +| | 07 | N2B000319 | 059 | 1 | Alternative solution for ALR | 3.4.0 | +| | 07 | N2B000461 | 063 | 4 | MNP Database Mismatch | 3.4.0 | +| | 07 | N2B000375 | 066 | 5 | Addition of the FTN-AddressString | 3.4.0 | +| | 07 | N2B000456 | 079 | 4 | Correction of SS Invocation Notification for CCBS | 3.4.0 | +| | 07 | N2A000023 | 080 | | Corrections to ATSI, ATM, NCSD | 3.4.0 | +| | 07 | N2B000046 | 083 | | Privacy notification/verification for call related privacy class | 3.4.0 | + +| | | | | | | | +|--|----|-----------|-----|---|--------------------------------------------------------------------------------------------------|-------| +| | 07 | N2B000142 | 084 | 2 | Addition of CS Allocation/retention priority | 3.4.0 | +| | 07 | N2B000144 | 086 | 1 | Editorial cleanup of 29.002 | 3.4.0 | +| | 07 | N2B000100 | 087 | | Correction of LSA information | 3.4.0 | +| | 07 | N2B000067 | 089 | | Security interworking between release 99 and pre-99 MSC/VLRs | 3.4.0 | +| | 07 | N2B000113 | 090 | 1 | Improving GPRS charging efficiency | 3.4.0 | +| | 07 | N2B000120 | 094 | 2 | QoS-Subscribed field enhancements | 3.4.0 | +| | 07 | N2B000322 | 095 | 1 | RANAP support on the E-interface | 3.4.0 | +| | 07 | N2B000191 | 099 | | UMTS Authentication | 3.4.0 | +| | 07 | N2B000466 | 100 | 5 | Support of 3G Handover, including Multicall | 3.4.0 | +| | 07 | N2B000372 | 101 | 1 | Introduction of Service Area Identification | 3.4.0 | +| | 07 | N2B000380 | 102 | 2 | Clarification on Authentication Info Retrieval | 3.4.0 | +| | 07 | N2B000330 | 103 | 1 | Addition of UMTS security to MAP B interface | 3.4.0 | +| | 07 | N2B000244 | 104 | | Re-Synchronisation Info | 3.4.0 | +| | 07 | N2B000324 | 105 | 1 | Introduction of additional service parameters for inter-system handover | 3.4.0 | +| | 07 | N2B000281 | 107 | | Removal of architectural information from clause 4 | 3.4.0 | +| | 07 | N2-000454 | 110 | 1 | Introduction of Authentication Failure Report | 3.4.0 | +| | 07 | N2B000357 | 111 | | Use of MAP private extensions to implement region-specific requirements | 3.4.0 | +| | 07 | N2B000470 | 112 | | Prioritisation of MAP application context related to VGCS/VBS | 3.4.0 | +| | 07 | N2B000472 | 113 | | Correction of SS-Codes for LCS | 3.4.0 | +| | 08 | N4-000098 | 115 | 1 | Minor corrections to CAMEL3 NSDC/ATM/ATSI information flows | 3.5.0 | +| | 08 | N4-000094 | 117 | 1 | Using DSD to delete CCBS-B from the subscriber | 3.5.0 | +| | 08 | N4-000089 | 118 | 1 | Indication in PRN of support of Long FTNs | 3.5.0 | +| | 08 | N4-000073 | 120 | 1 | QoS-Subscribed field enhancements | 3.5.0 | +| | 08 | N4-000050 | 121 | | Correction of introduction of additional service parameters for inter-system handover | 3.5.0 | +| | 08 | N4-000100 | 122 | 2 | Proposed information flow on NSDC | 3.5.0 | +| | 08 | N4-000321 | 124 | 3 | CAMEL Subscription Info | 3.5.0 | +| | 08 | N4-000068 | 125 | | Clarification to GMLC List definition | 3.5.0 | +| | 08 | N4-000320 | 127 | 1 | Optionality of parameters in d-csi and in sms-csi | 3.5.0 | +| | 08 | N4-000209 | 130 | | Version 3 tags for handover messages | 3.5.0 | +| | 08 | N4-000211 | 132 | | Correction of version handling at dialogue establishment | 3.5.0 | +| | 08 | N4-000357 | 133 | 1 | Various corrections and/or cleanup to 29.002 | 3.5.0 | +| | 08 | N4-000217 | 134 | | Correction of errors in Figure 25.1/1: Macro Receive_Open_Ind | 3.5.0 | +| | 08 | N4-000326 | 135 | 1 | Addition of charging characteristics per PDP context | 3.5.0 | +| | 08 | N4-000264 | 138 | | Clarification of SAI-ack segmentation procedure | 3.5.0 | +| | 08 | N4-000392 | 139 | 1 | Indication of unsupported position method | 3.5.0 | +| | 08 | N4-000276 | 141 | | Clarification for ReportSM-DeliveryStatus operation | 3.5.0 | +| | 08 | N4-000349 | 142 | 1 | Addition of a parameter in the subsequent Handover from UMTS to GSM with Multicall | 3.5.0 | +| | 08 | N4-000278 | 143 | | Editorial correction to MSC-A handover SDLs | 3.5.0 | +| | 08 | N4-000378 | 144 | 1 | Use of NAM parameter with MAP-INSERT-SUBSCRIBER-DATA service between HLR and SGSN | 3.5.0 | +| | 08 | N4-000293 | 145 | | Addition of state attributes in Forward group call signalling | 3.5.0 | +| | 08 | N4-000294 | 146 | | New user error 'target cell outside group call area' in MAP Prepare Handover message | 3.5.0 | +| | 08 | N4-000374 | 149 | | Correction to the description of MAP-MO-Forward-Short-Message service | 3.5.0 | +| | 08 | N4-000407 | 148 | 4 | Changes to MAP for secure transport of MAP messages | 4.0.0 | +| | 08 | | | | Version 4.0.1 created to allow inclusion of automatic update of Annexes A and B and of clause 17 | 4.0.1 | +| | 09 | N4-000543 | 152 | 1 | Clarifications for secure MAP transport | 4.1.0 | +| | 09 | N4-000539 | 153 | 1 | Generalization of version handling text in clause 18.2.4 | 4.1.0 | +| | 09 | N4-000491 | 158 | | Deletion of informative Annexe C | 4.1.0 | +| | 09 | N4-000540 | 159 | | Aligning 29.002 with 25.413 (UTRAN Iu Interface RANAP Signalling) | 4.1.0 | +| | 09 | N4-000541 | 160 | | AUTS and AUTN parameter length | 4.1.0 | +| | 09 | N4-000744 | 161 | 2 | Clarification on Authentication Failure Report ack | 4.1.0 | +| | 09 | N4-000666 | 163 | 1 | Correction on Location Information | 4.1.0 | +| | 09 | N4-000777 | 174 | 2 | Optionality of parameters in GPRS-CSI | 4.1.0 | +| | 09 | N4-000788 | 176 | 1 | Correction to QoS indication | 4.1.0 | +| | 09 | N4-000747 | 178 | 1 | Clarification of use of Radio Resource Information | 4.1.0 | +| | 09 | N4-000750 | 180 | 2 | Correction to MSC-A handover SDLs | 4.1.0 | +| | 09 | N4-000736 | 182 | | Removal of LSAIdentity from NoteMM-EventArgs | 4.1.0 | +| | 09 | N4-000772 | 184 | | LCS Support for CAMEL Phase 3 | 4.1.0 | +| | 09 | N4-000751 | 186 | 1 | Correction to MSC-A handover SDLs | 4.1.0 | +| | 09 | N4-000779 | 188 | | Clarification for segmentation of D-CSI and SMS-CSI | 4.1.0 | +| | 10 | N4-000912 | 166 | 3 | Corrections and clarifications for USSD procedures on the HLR - gsmSCF interface | 4.2.0 | +| | 10 | N4-000908 | 191 | 1 | Corrections of ISD data structure for CAMEL phase 3 | 4.2.0 | +| | 10 | N4-001069 | 193 | 2 | USSD Corrections for Follow Me | 4.2.0 | +| | 10 | N4-001071 | 196 | 1 | GSM to 3G Handover: MAP parameter Target Cell ID | 4.2.0 | +| | 10 | N4-000921 | 198 | | ASN.1 description of targetCellId | 4.2.0 | +| | 10 | N4-001073 | 200 | 1 | IMSI in MAP_PREPARE_HANDOVER | 4.2.0 | +| | 10 | N4-001076 | 208 | 1 | Alignment of the Target RNC-ID | 4.2.0 | +| | 10 | N4-001089 | 211 | 1 | Export of GSN-Address data type | 4.2.0 | + +| | | | | | | | +|--|----|-----------|-----|---|----------------------------------------------------------------------------------------|-------| +| | 10 | N4-001095 | 212 | | Transport of long RANAP messages on MAP-E interface | 4.2.0 | +| | - | - | - | - | Automatic update of annexes A and B | 4.2.1 | +| | 11 | N4-010036 | 206 | 1 | Correction to LCS application context | 4.3.0 | +| | 11 | N4-010276 | 215 | 2 | Add parameters to ISD and SRI for GPRS to handle ODB for PS | 4.3.0 | +| | 11 | N4-010033 | 217 | | Correction to maximum number of RAB's | 4.3.0 | +| | 11 | N4-010198 | 222 | 2 | PS domain support for LCS Release 4 | 4.3.0 | +| | 11 | N4-010058 | 224 | | Failure of Update GPRS Location when HLR is not reachable | 4.3.0 | +| | 11 | N4-010287 | 231 | 1 | Extension of call related privacy class for LCS Release 4 | 4.3.0 | +| | 11 | N4-010375 | 232 | 2 | Maximum number of LCS Clients | 4.3.0 | +| | 11 | N4-010261 | 234 | | MAP over IP according to SIGTRAN | 4.3.0 | +| | 11 | N4-010465 | 236 | 1 | Requesting node type in authentication set request | 4.3.0 | +| | 11 | N4-010360 | 246 | | Adding EXPORT definition for LSIdentity | 4.3.0 | +| | 11 | N4-010361 | 247 | | Removing duplicate parameters from ss-CSI | 4.3.0 | +| | 11 | N4-010362 | 248 | | Correction to description of SS-CSI in HLR to VLR information flow | 4.3.0 | +| | 11 | N4-010365 | 250 | | GSM to UMTS handover: addition of MAP parameter RNC ID | 4.3.0 | +| | 11 | N4-010393 | 252 | | Clarification of the use of multicall bearer information | 4.3.0 | +| | 11 | N4-010428 | 258 | | Adding EXPORT definition for GeographicalInformation | 4.3.0 | +| | 11 | N4-010446 | 260 | | Failure of Authentication Parameter GPRS when HLR is not reachable | 4.3.0 | +| | 11 | N4-010484 | 262 | 1 | Correction to D-CSI | 4.3.0 | +| | 12 | N4-010728 | 239 | 4 | Addition of selected UMTS algorithm indication to the handover procedures | 4.4.0 | +| | 12 | N4-010730 | 241 | 4 | Addition of allowed GSM algorithms indication to the handover procedures | 4.4.0 | +| | 12 | N4-010733 | 244 | 4 | Addition of allowed UMTS algorithm indication to the handover procedures | 4.4.0 | +| | 12 | N4-010735 | 245 | 4 | Addition of selected GSM algorithm indication to the handover procedures | 4.4.0 | +| | 12 | N4-010739 | 254 | 2 | Addition of radio resource list to the handover procedures | 4.4.0 | +| | 12 | NP-010247 | 256 | 3 | Addition of GSM channel type and GSM chosen channel indications to handover procedures | 4.4.0 | +| | 12 | N4-010787 | 264 | 3 | Add support in MAP for all shapes defined in 23.032 | 4.4.0 | +| | 12 | N4-010633 | 270 | 1 | Correction to description of RNCId parameter | 4.4.0 | +| | 12 | N4-010635 | 272 | 1 | Correction to Encryption Information and Integrity Protection parameters | 4.4.0 | +| | 12 | N4-010767 | 279 | 3 | Essential drawbacks on services due to introduction of Super-Charger function | 4.4.0 | +| | 12 | N4-010741 | 283 | 1 | Introduction of selected Rab-id to the Process Access Signalling operation | 4.4.0 | +| | 12 | N4-010673 | 285 | | Mistake in the definition of Authentication Failure Report Application Context | 4.4.0 | +| | 12 | N4-010551 | 266 | | Add support in MAP for Ellipsoid Point | 4.4.0 | +| | 12 | N4-010778 | 168 | 5 | Security Header modification | 4.4.0 | +| | 12 | N4-010785 | 267 | 3 | Additional Parameters in Authentication Failure Report | 4.4.0 | +| | 12 | N4-010783 | 268 | 3 | MS presence notification procedure for LCS | 4.4.0 | +| | 12 | N4-010790 | 289 | 2 | Component level granularity of protection | 4.4.0 | +| | | | | | Corrupted headers fixed | 4.4.1 | +| | 13 | N4-010840 | 290 | | Clarifications on long forwarded-to numbers | 4.5.0 | +| | 13 | N4-010929 | 291 | 1 | Corrections for Deferred MT-LR | 4.5.0 | +| | 13 | N4-010930 | 292 | 2 | Clarifications on SupportedLCS-CapabilitySets | 4.5.0 | +| | 13 | N4-010958 | 295 | 2 | Corrections on the introduction of LCS for PS domain | 4.5.0 | +| | 13 | N4-010970 | 302 | 2 | Additional SGSN related values to Access Type | 4.5.0 | +| | 13 | N4-010976 | 306 | | Addition of data type definitions to EXPORT statements for the usage in CAP | 4.5.0 | +| | 13 | N4-011017 | 307 | 2 | Minimum MAP application context for intersystem MSC handover from GSM to UMTS | 4.5.0 | +| | 13 | N4-011019 | 309 | 2 | Minimum MAP application context for intersystem MSC handover from UMTS to GSM | 4.5.0 | +| | 13 | N4-010845 | 277 | 1 | Correction on the SDL of NW initiated USSD operations | 4.5.0 | +| | 13 | | | | Editorial Clean up | 4.5.0 | +| | 14 | N4-011031 | 313 | | Clarification on LCS parameters in MAP | 4.6.0 | +| | 14 | N4-011043 | 314 | | Handling of linked operations in the MAP protocol machine | 4.6.0 | +| | 14 | N4-011285 | 316 | | Corrections on the SDL diagrams for LCS | 4.6.0 | +| | 14 | N4-011198 | 318 | 1 | Indication of deletion of CSI in Notify Subscriber Data Change | 4.6.0 | +| | 14 | N4-011074 | 320 | | Correct length of Add-GeographicalInformation | 4.6.0 | +| | 14 | N4-011091 | 322 | | Clarify encoding of RNC Id | 4.6.0 | +| | 14 | N4-011094 | 324 | | Clarify encoding of RANAP parameters in MAP | 4.6.0 | +| | 14 | N4-011097 | 325 | | Clarifications on long forwarded-to numbers | 4.6.0 | +| | 14 | N4-011227 | 331 | 1 | Clarification of methodology for maintaining data consistency in Supercharger | 4.6.0 | +| | 14 | N4-011173 | 334 | | Addition of RAB ID to Prepare Handover procedure | 4.6.0 | +| | 14 | N4-011175 | 336 | | Correction to the Allowed GSM Algorithms parameter | 4.6.0 | +| | 14 | N4-011177 | 337 | 1 | Correction of references | 4.6.0 | +| | 14 | N4-011190 | 339 | | CUG-Info is not exported from 29.002 | 4.6.0 | +| | 14 | N4-011209 | 341 | | Clarification on NSCD when data is withdrawn | 4.6.0 | +| | 14 | N4-011211 | 343 | | Clarification of sending CAMEL information in stand alone ISD case | 4.6.0 | +| | 14 | N4-011262 | 344 | | Correction of the priority for "SRI for LCS" | 4.6.0 | +| | 14 | N4-011273 | 347 | | ASN.1 correction | 4.6.0 | +| | 14 | N4-011437 | 349 | 2 | Handling of MNRR in the HLR & SMS-GMSC | 4.6.0 | +| | 14 | N4-011433 | 354 | 1 | Minimum MAP application context for G2G inter-MSC handover | 4.6.0 | + +| | | | | | | | +|--|-----|-----------|-----|---|-------------------------------------------------------------------------------------|-------| +| | 14 | N4-011439 | 359 | 2 | Alignment of parameter lengths with those prescribed in 08.08 | 4.6.0 | +| | 14 | N4-011423 | 360 | 1 | Aligning the security header elements with TS33.200 | 4.6.0 | +| | 14 | N4-011394 | 364 | | Syntax error in the ATM result and ATSI result | 4.6.0 | +| | 14 | N4-011381 | 355 | 1 | LCS Capability Handling for UE's | 5.0.0 | +| | 15 | N4-020300 | 368 | 4 | Collective CAMEL Phase 4 CR | 5.1.0 | +| | 15 | N4-020013 | 373 | | Inclusion of complete ODB data in ATSI and NSDC | 5.1.0 | +| | 15 | N4-020266 | 381 | 2 | Introduction of the "Requestor ID" | 5.1.0 | +| | 15 | N4-020068 | 386 | | Correction to AC version of gprsLocationInfoRetrievalContext | 5.1.0 | +| | 15 | N4-020248 | 390 | 1 | Incomplete description of Restore Data parameters | 5.1.0 | +| | 15 | N4-020183 | 403 | | Clarification on CODEC-Info | 5.1.0 | +| | 15 | N4-020250 | 407 | 1 | ODB alignment | 5.1.0 | +| | 16 | N4-020530 | 428 | 2 | LCS: error handling if shape not supported by GMLC | 5.2.0 | +| | 16 | N4-020622 | 453 | | Addition of Radio Resource List to the Forward Access Signalling operation | 5.2.0 | +| | 16 | N4-020641 | 460 | | Clarification on Resume Call Handling | 5.2.0 | +| | 16 | N4-020746 | 440 | 2 | Clarification on SendAuthenticationInfo | 5.2.0 | +| | 16 | N4-020750 | 446 | 1 | Addition of Service Handover parameters to MAP Handover messages | 5.2.0 | +| | 16 | N4-020318 | 398 | | Check of NAM and Requesting Node Type on receipt of SendAuthenticationInfo | 5.2.0 | +| | 16 | N4-020333 | 410 | | Handling the MNRR flag in the HLR & SMS-GMSC | 5.2.0 | +| | 16 | N4-020499 | 420 | 1 | Clarification of introducing Session related and unrelated class | 5.2.0 | +| | 16 | N4-020511 | 430 | 1 | Corrections on the introduction of LCS for PS domain | 5.2.0 | +| | 16 | N4-020743 | 448 | 1 | Corrections in SS-code chapter | 5.2.0 | +| | 16 | N4-020408 | 423 | | Clarification of handling of MT-SMS-TPDU-Type and SMS-TDP | 5.2.0 | +| | 16 | N4-020410 | 425 | | Clarify conditions to trigger restart of MTLR-Deferred procedure | 5.2.0 | +| | 16 | N4-020468 | 414 | 1 | Corrections to the handling of Any Time Interrogation and Provide Subscriber Info | 5.2.0 | +| | 16 | N4-020476 | 435 | 1 | Change PS-connected in PS-PDPactive | 5.2.0 | +| | 16 | N4-020483 | 422 | 1 | Triggering of gsmSCF for MT-SMS-CSI | 5.2.0 | +| | 16 | N4-020485 | 408 | 2 | Transferring the MS classmark & IMEI to the gsmSCF | 5.2.0 | +| | 16 | N4-020543 | 441 | | Correction of Object Identifiers for ASN.1 modules | 5.2.0 | +| | 16 | N4-020608 | 450 | | Enhancement to LCS in the PS domain | 5.2.0 | +| | 16 | N4-020623 | 454 | | Addition of Location Information GPRS to Note MM Event operation | 5.2.0 | +| | 16 | N4-020703 | 421 | 4 | LCS: Codeword and Service Type | 5.2.0 | +| | 16 | N4-020756 | 436 | 2 | Splitting of CAMEL phase 4 | 5.2.0 | +| | 17 | N4-021001 | 437 | 3 | Compatible upgrade to ASN.1:1997 of 29.002 | 5.3.0 | +| | 17 | NP-020399 | 462 | 2 | Introduction of GERAN classmark | 5.3.0 | +| | 17 | N4-020841 | 465 | | Clarification on Call Deflection | 5.3.0 | +| | 17 | N4-021040 | 470 | 1 | Correction to the usage of "Roaming not allowed" error | 5.3.0 | +| | 17 | N4-021041 | 471 | 1 | Clarifications on Send Identification | 5.3.0 | +| | 17 | N4-021094 | 479 | 2 | Handling of partial implementations of CAMEL phase 4 | 5.3.0 | +| | 17 | N4-021047 | 480 | | Removal of ChargingNotification feature | 5.3.0 | +| | 17 | N4-020810 | 481 | | CR29.002-443 (rel5) on extensions to ATM for CAMEL control of IMS | 5.3.0 | +| | 17 | N4-020809 | 482 | | CR to 29.002 for the support of the MAP Si interface | 5.3.0 | +| | 18 | N4-021290 | 499 | | Correction to segmentation of O-CSI and T-CSI | 5.4.0 | +| | 18 | N4-021418 | 508 | | ODB correction | 5.4.0 | +| | 18 | N4-021563 | 511 | 1 | Addition of reference number to deferred location request procedure | 5.4.0 | +| | 18 | N4-021573 | 516 | 2 | Correction to the Service Handover parameters | 5.4.0 | +| | 18 | N4-021299 | 442 | 3 | Description of MT SM delivery via two serving nodes | 5.4.0 | +| | 18 | N4-021294 | 474 | 2 | Correction of handling of MT-SMS in the SGSN | 5.4.0 | +| | 18 | N4-021124 | 475 | | ODB and CB for SMS | 5.4.0 | +| | 18 | N4-021153 | 486 | | Correction of IMEI check for SGSN | 5.4.0 | +| | 18 | N4-021467 | 489 | 5 | Available codecs list and selected codec indication | 5.4.0 | +| | 18 | N4-021194 | 490 | | Clarification of the use of Requested CAMEL Subscription Info parameters | 5.4.0 | +| | 18 | N4-021252 | 495 | | Correction to RCH – adding O-CSI trigger criteria | 5.4.0 | +| | 18 | N4-021264 | 496 | | Additional MM-Code for MG-CSI | 5.4.0 | +| | 18 | N4-021296 | 497 | 1 | Additional handling of partial implementations of CAMEL phase 4 | 5.4.0 | +| | 18 | N4-021383 | 512 | | Correction of Codeword Handling | 5.4.0 | +| | 18 | N4-021443 | 513 | | Reference to TS 23.078 in TS 29.002 regarding handling of VMSC address is missing | 5.4.0 | +| | 18 | N4-021524 | 521 | 1 | Editorial clean-up | 5.4.0 | +| | 18 | N4-021531 | 522 | | Introduction of the CHOICE element "netDetNotReachable" for PS-SubscriberState | 5.4.0 | +| | 18 | N4-021260 | 491 | 1 | Addition of LCS Format Indicator to LCS Client ID | 6.0.0 | +| | 18 | N4-021504 | 517 | 2 | Addition of V-GMLC Address to the Update Location and Update GPRS Location requests | 6.0.0 | +| | 18 | N4-021567 | 518 | 3 | Addition of V-GMLC and H-GMLC Addresses to the Send Routing Info for LCS response | 6.0.0 | +| | 18- | N4-021506 | 519 | 2 | Addition of PPR Address to the Send Routing Info for LCS response | 6.0.0 | +| | 19 | N4-030234 | 509 | 3 | Introduction of Call Barring for SMS in PS domain | 6.1.0 | +| | 19 | N4-030325 | 524 | 3 | Clean-up of SMS procedures chapter | 6.1.0 | +| | 19 | NP-030068 | 545 | 2 | Correction to interactions between CAMEL control of MO SMS and barring | 6.1.0 | +| | 19 | N4-030061 | 526 | | Incrementing ASN.1 module versions | 6.1.0 | +| | 19 | N4-030063 | 528 | | LCS diagnostic alignment | 6.1.0 | + +| | | | | | | | +|--|----|------------|-----|---|----------------------------------------------------------------------------------------------------|-------| +| | 19 | N4-030054 | 529 | | Addition of LCS Capability Set 4 | 6.1.0 | +| | 19 | N4-030301 | 533 | 1 | Correction to the definitions of Radio Resource List and BSSMAP Service Handover List | 6.1.0 | +| | 19 | N4-030305 | 541 | 2 | Handover of Group Calls where MSC-B has bearer established | 6.1.0 | +| | 19 | N4-030287 | 551 | 1 | Change of SS-Code List description for Insert Subscriber Data | 6.1.0 | +| | 19 | N4-030289 | 559 | 1 | Missing of "Continue Monitoring message" in SDL 21.7_3.2 | 6.1.0 | +| | 19 | N4-030297 | 563 | 1 | Alignment of TS 29.002 with TS 23.107 regarding QoS subscribed data | 6.1.0 | +| | 19 | N4-030222 | 566 | 1 | Introduction of MSC Number as a new parameter in MAP-SEND-IDENTIFICATION operation | 6.1.0 | +| | 20 | N4-030692 | 536 | 2 | Additional SGSN Related Access Type – Detach | 6.2.0 | +| | 20 | N4-030658 | 568 | 4 | Addition of Positioning Data IE to Provide Subscriber Location and Send Location Report | 6.2.0 | +| | 20 | N4-030638 | 574 | 1 | Provision of SDL diagrams and removal of redundant text in chapter 25 | 6.2.0 | +| | 20 | N4-030713 | 595 | 2 | Removal of redundant text from 29.002 Chapter 23 | 6.2.0 | +| | 20 | N4-030439 | 599 | | LCS Client external ID | 6.2.0 | +| | 20 | N4-030682 | 607 | 1 | Provision of SDL diagrams and removal of redundant text in chapter 22 | 6.2.0 | +| | 20 | N4-030608 | 608 | 1 | Addition of LCS capability sets to MAP_SRI for LCS response | 6.2.0 | +| | 20 | N4-030647 | 612 | 1 | Enhancement of the CheckIMEI operation to retrieve the BMUEF | 6.2.0 | +| | 20 | N4-030678 | 619 | 1 | Correction to naming of PRN parameter | 6.2.0 | +| | 20 | N4-030609 | 624 | 1 | Addition of Privacy Check Related Action to Provide Subscriber Location request | 6.2.0 | +| | 20 | N4-030642 | 610 | 1 | Transfer of UE-specific behaviour bitmap at handover | 6.2.0 | +| | 20 | N4-030601 | 633 | | Missing SMSs over MSC even if the MS is capable of such sending | 6.2.0 | +| | 21 | N4-031043 | 584 | 2 | Correction to MAP Process Secure_MAP_DSM SDLs | 6.3.0 | +| | 21 | N4-031053 | 664 | 1 | Correction of encoding description of Group-Id | 6.3.0 | +| | 21 | N4-030828 | 657 | | Reduce maximum length of "LCS Requestor ID" and "LCS Codeword". | 6.3.0 | +| | 21 | N4-030922 | 647 | 1 | UESBI -IU format | 6.3.0 | +| | 21 | N4-031069 | 616 | 3 | Incorrect Charging with MNP | 6.3.0 | +| | 21 | N4-031057 | 660 | 2 | Notification of the 2nd BSG in case of Late CF with OR | 6.3.0 | +| | 21 | N4-031059 | 614 | 3 | HLR Interrogation for SCUDIF calls | 6.3.0 | +| | 21 | N4-030785 | 644 | | Removal of tables in clause 7.6 | 6.3.0 | +| | 21 | N4-030806 | 649 | | Correction of References | 6.3.0 | +| | 21 | N4-030815 | 648 | | Correction of wrong AC name in the table in 17.1.6 | 6.3.0 | +| | 21 | N4-030824 | 654 | | New LCS Service Types | 6.3.0 | +| | 21 | N4-030951 | 671 | | SS-Barring Category | 6.3.0 | +| | 21 | N4-031006 | 650 | 1 | Add SGSN, GGSN, GMLC, gsmSCF, NPLR and AuC to network resource parameter | 6.3.0 | +| | 21 | N4-0301038 | 645 | 1 | Introduction of North American Interim Location Based Routing of Emergency Call | 6.3.0 | +| | 21 | N4-031065 | 674 | | Positioning Data for UTRAN LCS | 6.3.0 | +| | 21 | N4-030953 | 637 | 1 | Provision of SDL diagrams and removal of redundant text in chapter 19 | 6.3.0 | +| | 21 | N4-030745 | 639 | | Provision of SDL diagrams and removal of redundant text in chapter 20 | 6.3.0 | +| | 21 | N4-030747 | 641 | | Provision of SDL diagrams and removal of redundant text in chapter 21 | 6.3.0 | +| | 21 | N4-030748 | 642 | | Removal of SIWF description | 6.3.0 | +| | 21 | N4-030749 | 643 | | Deletion of redundant Annex D | 6.3.0 | +| | 22 | N4-031098 | 677 | | Enhancements for the Partial Implementation for "Change of position procedure armed with criteria" | 6.4.0 | +| | 22 | N4-031135 | 687 | | Collective CR for Rel-6 Enhanced Dialled Services | 6.4.0 | +| | 22 | N4-031274 | 648 | 2 | Message Segmentation Mechanisms | 6.4.0 | +| | 22 | N4-031315 | 703 | | Addition of requestingPLMN-ID to Send Authentication Info Request | 6.4.0 | +| | 22 | N4-031372 | 680 | 2 | Addition of CGI to LCS procedures | 6.4.0 | +| | 22 | N4-031373 | 696 | 2 | Include v-gmlc parameter in RESTORE DATA MAP message | 6.4.0 | +| | 22 | N4-031365 | 702 | 2 | Deferred MT-LR Area Event | 6.4.0 | +| | 22 | N4-031132 | 686 | | More spare bits for CAMEL4 enhancements | 6.4.0 | +| | 22 | N4-031163 | 692 | | Clarification on D-CSI segmentation | 6.4.0 | +| | 22 | N4-031342 | 676 | 2 | MNP correction for prepaid charging | 6.4.0 | +| | 22 | N4-031338 | 695 | 1 | Remove redundant option for retrieval of routeing information in figure 21.2.3 | 6.4.0 | +| | 22 | N4-031108 | 679 | | Modification of description for conditions on inclusion of Positioning Data | 6.4.0 | +| | 22 | N4-031317 | 689 | 2 | HSDPA impacts to MAP | 6.4.0 | +| | 22 | NP-030533 | 704 | | EXPORT data types to CAP (Change of position armed with criteria) | 6.4.0 | +| | 23 | N4-040310 | 668 | 3 | Codec Modification/ Mid-Call Codec Negotiation after Inter-MSC Relocation | 6.5.0 | +| | 23 | N4-040193 | 670 | 2 | Correction of Inter-MSC SRSN Relocation procedure | 6.5.0 | +| | 23 | N4-040249 | 701 | 3 | Introduction of Presence Stage 3 (Ph, Pc and Pg) to the MAP interface | 6.5.0 | +| | 23 | N4-040333 | 708 | 2 | Correction to Insert Subscriber Data message for LCS SS | 6.5.0 | +| | 23 | N4-040328 | 709 | 1 | SCCP segmentation for Inter PLMN MAP message | 6.5.0 | +| | 23 | N4-040327 | 711 | 2 | Inclusion of UTRAN Positioning Data parameter | 6.5.0 | +| | 23 | N4-040284 | 717 | 1 | Include administrative restriction subscription parameter | 6.5.0 | +| | 23 | N4-040340 | 720 | 2 | Add new Unavailability cause for SCUDIF | 6.5.0 | +| | 23 | N4-040171 | 721 | | CR implemented by fault | 6.5.0 | +| | 23 | N4-040182 | 724 | | Removal of R-GMLC Address | 6.5.0 | +| | 23 | N4-040322 | 725 | 1 | MO-LR Service Identity support | 6.5.0 | +| | 23 | N4-040267 | 726 | 1 | CAMEL4 SCUDIF notification during active call for prepay | 6.5.0 | +| | 24 | N4-040520 | 731 | | Introduction of North American Interim Location Based Routing of | 6.6.0 | + +| | | | | | | +|--|----|-----------|------|---------------------------------------------------------------------------------------|--------| +| | | | | Emergency Call | | +| | 24 | N4-040585 | 735 | Modify IMEI parameter usage definition in MAP-PSL and MAP-SLR | 6.6.0 | +| | 24 | N4-040600 | 736 | Addition of SAI-Present indication to the LCS procedures | 6.6.0 | +| | 24 | N4-040601 | 737 | Clarification on the use of MSISDN parameter for Follow Me functionality | 6.6.0 | +| | 24 | N4-04732 | 734 | 1 Add Additional V-GMLC parameter in MAP-SRI-INFO-FOR-LCS | 6.6.0 | +| | 24 | N4-040736 | 718 | 6 Addition of IMEISV to Update Location Procedure for ADD function | 6.6.0 | +| | 25 | N4-040929 | 739 | Export of UU-Data data type | 6.7.0 | +| | 25 | N4-041021 | 743 | Wrong SDL flow page implemented | 6.7.0 | +| | 25 | N4-041128 | 732 | 2 Pre-Paging Resource Optimization | 6.7.0 | +| | 26 | N4-041272 | 747 | Incorrect Implementation of CR 731 | 6.8.0 | +| | 26 | N4-041477 | 752 | Correction to the service response parameters of ATI | 6.8.0 | +| | 26 | N4-041662 | 746 | 1 Introducing VGCS/VBS ciphering | 6.8.0 | +| | 26 | N4-041683 | 757 | 2 Clarification about returning authentication data for a subscriber (GSM or UMTS) | 6.8.0 | +| | 26 | N4-041684 | 748 | 1 LCS Capability Handling for UE's | 6.8.0 | +| | 26 | N4-041685 | 753 | 1 Enable NA-ESRD Provision from a GMLC for E911 Location in North America | 6.8.0 | +| | 26 | N4-041641 | 740 | 2 SMS Fraud countermeasures | 6.8.0 | +| | 27 | N4-050212 | 749 | 1 Management Based Activation Impacts | 6.9.0 | +| | 27 | N4-050369 | 761 | 1 Addition of LAI to SendIdentification Request | 6.9.0 | +| | 27 | N4-050430 | 760 | 1 Subscribed Charging Characteristics | 6.9.0 | +| | 27 | N4-050444 | 759 | 1 Addition of TCAP-Handshake for MO-ForwardSM | 6.9.0 | +| | 27 | N4-050446 | 745 | 2 Introduction of Hop Counter for Send Identification | 6.9.0 | +| | 27 | N4-050463 | 738 | 8 Rel-6 trace management additions to trace activation and deactivation procedures | 6.9.0 | +| | 27 | N4-050467 | 763 | 2 Pseudonym indicator support in MO-LR | 6.9.0 | +| | 28 | C4-050737 | 769 | 1 Correction to Trace parameters to allow trace at the BM-SC | 6.10.0 | +| | 28 | C4-050832 | 770 | 6 Full RANAP support of network initiated SCUDIF | 6.10.0 | +| | 28 | C4-050895 | 766 | 2 Clarification on the use of Access Restriction Data parameter | 6.10.0 | +| | 28 | C4-050784 | 765 | 1 Addition of CollectInformation procedure to OfferedCAMEL4Functionalities | 7.0.0 | +| | 29 | C4-051013 | 771 | ASN.1 module version update | 7.1.0 | +| | 29 | C4-051295 | 776 | 2 Enabling the Providing of Velocity | 7.1.0 | +| | 29 | C4-051333 | 772 | 1 Support of talker priorities and talker identity presentation | 7.1.0 | +| | 29 | C4-051334 | 773 | 1 Delivery of SMS to voice group call | 7.1.0 | +| | 29 | C4-051368 | 777 | 2 CS data Mobile Terminating calls from PSTN | 7.1.0 | +| | 29 | C4-051336 | 780 | 2 Correction on misalignment with stage 2 for Location Services | 7.1.0 | +| | 30 | C4-051775 | 783 | 2 Addition of UMTS Trace parameters to handover procedure | 7.2.0 | +| | 31 | C4-060320 | 794 | 1 Addition of UMTS Trace parameters to handover procedure | 7.3.0 | +| | 31 | C4-060295 | 790 | 1 Removal of MAPsec material | 7.3.0 | +| | 31 | C4-060315 | 787 | 1 addition of "supported RAT types indicator" during location/routing area update | 7.3.0 | +| | 31 | C4-060378 | 792 | 1 Addition of Periodic Location Feature Support | 7.3.0 | +| | 31 | C4-060434 | 781 | 3 New LocationType for the notification based on current location of target UE | 7.3.0 | +| | 31 | C4-060318 | 788 | 1 SMS Relay Application Context Names for Version 1 | 7.3.0 | +| | 31 | C4-060041 | 789 | Precision on segmentation of MAP GPRSSubscriptionData parameter | 7.3.0 | +| | 31 | C4-060250 | 801 | Improvements to VGCS Call Establishment | 7.3.0 | +| | 31 | C4-060011 | 786 | Addition of Authentication Domains in MAP Send Authentication Info | 7.3.0 | +| | 32 | C4-060813 | 0808 | 2 List of MSISDNs and Basic Service Code for MAP Any Time Subscription Interrogation. | 7.4.0 | +| | 32 | C4-060499 | 0803 | Correction of LCS parameter for emergency call usage | 7.4.0 | +| | 32 | C4-060680 | 0814 | SSN for FFN | 7.4.0 | +| | 32 | C4-060706 | 0817 | Removal of MAPsec material | 7.4.0 | +| | 33 | CP-060522 | 0818 | 1 Removal of ASN.1 Expanded Source | 7.5.0 | +| | 33 | C4-061047 | 0805 | 1 Interoperability between VBS/VGCS and RANflex | 7.5.0 | +| | 34 | CP-060741 | 0795 | 1 Support of SMS over IP networks | 7.6.0 | +| | 34 | C4-061800 | 0828 | 1 Extension of Group ID | 7.6.0 | +| | 34 | C4-061633 | 0829 | Addition of Teleservice Code to SendGroupCallInfo | 7.6.0 | +| | 34 | C4-061775 | 0834 | Accuracy Fulfillment Indicator parameter to MAP SLR for deferred MT-LR | 7.6.0 | +| | 34 | C4-060693 | 0832 | 2 Optional Suppress Terminating Services Bit String in SRI | 7.6.0 | +| | 34 | C4-061632 | 0807 | 2 Introduction of sending application-specific data to group call members | 8.0.0 | +| | 35 | C4-070140 | 0843 | ASN.1 module version update | 8.1.0 | +| | 35 | C4-070097 | 0837 | Corrections to RAB Configuration Indicator and lu-Selected codec | 8.1.0 | +| | 35 | C4-070229 | 0840 | Addition of capability to route MT-SMs via the HPLMN of the receiving MS | 8.1.0 | +| | 36 | C4-070388 | 0849 | Mobile Termination whilst the MS is moving to another MSC | 8.2.0 | +| | 36 | C4-070394 | 0842 | 2 Addition of SMS over IP functionality | 8.2.0 | +| | 36 | CP-070476 | 0859 | Detailed procedure in the IP-SM-GW | 8.2.0 | +| | 37 | C4-071055 | 0862 | QoS Extension | 8.3.0 | +| | 37 | C4-071072 | 0863 | Talker Channel Parameter | 8.3.0 | +| | 37 | C4-071266 | 0869 | LMSI For MT-SMS | 8.3.0 | +| | 37 | C4-071281 | 0873 | 1 NPI for the call forwarding to number | 8.3.0 | +| | 37 | C4-071285 | 0864 | 1 Limit on number of concurrent MT-LR location requests | 8.3.0 | +| | 37 | C4-071383 | 0868 | 2 Corrections to SMS over IP handling | 8.3.0 | + +| | | | | | | | +|--|----|-----------|------|---|--------------------------------------------------------------------------------------------------------------------------|--------| +| | 38 | C4-071724 | 0876 | | TCRT: Clarification on coding of Notification Data | 8.4.0 | +| | 38 | C4-071815 | 0879 | | Removal of CCBS_Call_Report_Ack and Event_Report_Ack | 8.4.0 | +| | 38 | C4-071855 | 0881 | | Restriction on the use of ccbs-A SS indication | 8.4.0 | +| | 38 | C4-071891 | 0877 | 3 | SMS Router Optimization | 8.4.0 | +| | 38 | C4-071997 | 0875 | 1 | Behaviour of the IP-SM-GW for SM Delivery Status Report | 8.4.0 | +| | 39 | C4-080267 | 0885 | | Updating of RAT Types | 8.5.0 | +| | 39 | C4-080148 | 0883 | | SDL correction for procedure Check_Available_Vectors | 8.5.0 | +| | 39 | C4-080532 | 0886 | 2 | HLR involvement in SMS Router Optimization | 8.5.0 | +| | 40 | C4-081277 | 0888 | 1 | Extension of Group ID | 8.6.0 | +| | 40 | C4-080647 | 0882 | 1 | Paging optimization with A/lu flex | 8.6.0 | +| | 41 | C4-081730 | 0890 | | Addition of IMS Centralized Service subscription information | 8.7.0 | +| | 41 | C4-082447 | 0891 | 1 | eMLPP Priority in MAP SRI, PRN and PSI request | 8.7.0 | +| | 41 | C4-082335 | 0892 | 1 | Gr+ enhancements for EPS | 8.7.0 | +| | 42 | C4-082721 | 0894 | | Gr alignment | 8.8.0 | +| | 42 | C4-082758 | 0896 | | RAT Frequency Selection Priority | 8.8.0 | +| | 42 | C4-083029 | 0899 | | Change in AMBR placement | 8.8.0 | +| | 42 | C4-083221 | 0901 | | PDN-GW-Identity | 8.8.0 | +| | 42 | C4-083223 | 0902 | | APN-OIReplacement | 8.8.0 | +| | 42 | C4-083247 | 0903 | | Access Restriction | 8.8.0 | +| | 42 | CP-080706 | 0906 | 1 | Access Restriction Data Handling | 8.8.0 | +| | 42 | Cp-080771 | 0895 | 4 | Closed Subscriber Group | 8.8.0 | +| | 42 | | | | SDL files added in Zip-file | 8.8.1 | +| | 43 | C4-090140 | 0908 | | Context Identifier for Update or Removal of PDN GW | 8.9.0 | +| | 43 | C4-090269 | 0911 | | Handling LCS Subscription Data | 8.9.0 | +| | 43 | C4-090507 | 0914 | | PDN GW Update for Wildcard APN | 8.9.0 | +| | 43 | C4-090701 | 0909 | 1 | Ready for SM | 8.9.0 | +| | 43 | C4-090855 | 0915 | | Handling SMS Subscription Data | 8.9.0 | +| | 43 | C4-090889 | 0916 | | Allocation Retention Priority Definition | 8.9.0 | +| | 44 | C4-091071 | 0919 | | SMS over IP | 8.10.0 | +| | 44 | C4-091028 | 0917 | | MAP RESTORE DATA service | 8.10.0 | +| | 44 | C4-091377 | 0921 | 1 | Subscription Data Clarification for MAP Interface | 8.10.0 | +| | 44 | C4-091429 | 0920 | 1 | Trace | 8.10.0 | +| | 44 | C4-091435 | 0922 | 1 | Supported Features | 8.10.0 | +| | 44 | CP-090379 | 0923 | 1 | User Data Download | 8.10.0 | +| | 45 | C4-091713 | 0924 | | Notification of SMS over IP Non-Delivery for E-UTRAN and UE Reachability | 8.11.0 | +| | 45 | C4-092244 | 0927 | | SGSN interface list for trace | 8.11.0 | +| | 45 | C4-092254 | 0925 | 2 | Cancel Location for Initial Attach | 8.11.0 | +| | 45 | C4-092291 | 0929 | | Fix APN-Configuration to support dual IP addresses | 8.11.0 | +| | 46 | C4-094140 | 0941 | 1 | Alignment of specifications on Usage of MAP_SEND_AUTHENTICATION_INFO | 8.12.0 | +| | 46 | C4-093972 | 0942 | 1 | SMS over SGs charging | 8.12.0 | +| | 46 | C4-094136 | 0936 | 1 | Subscription to Notification of UE Reachability | 8.12.0 | +| | 46 | C4-093588 | 0935 | 1 | Evolved ARP | 9.0.0 | +| | 46 | C4-093294 | 0932 | 2 | APN level APN-OI-Replacement | 9.0.0 | +| | 46 | C4-093221 | 0933 | 1 | ICS-Flag | 9.0.0 | +| | 47 | C4-100386 | 0949 | | Correction to the location information EPS IE | 9.1.0 | +| | 47 | C4-101003 | 0951 | 1 | User CSG Information for CAMEL | 9.1.0 | +| | 47 | C4-100946 | 0945 | 2 | Support of Location Continuity on the Lg Interface | 9.1.0 | +| | 47 | C4-100947 | 0958 | 2 | Enhancement of MAP-SEND-ROUTING-INFO-FOR-LCS Service for EPS | 9.1.0 | +| | 47 | C4-100264 | 0943 | | Evolved ARP Corrections | 9.1.0 | +| | 47 | C4-100920 | 0928 | 4 | AoIP – MAP level codec negotiation for GSM codecs | 9.1.0 | +| | 47 | C4-100265 | 0944 | | Dual Stack support in GPRS | 9.1.0 | +| | 47 | C4-100353 | 0939 | 2 | Support MT Roaming Retry on Pre-paging | 9.1.0 | +| | 47 | C4-100892 | 0954 | 1 | TCRT: Uplink reply procedure | 9.1.0 | +| | 47 | C4-100881 | 0956 | 1 | TADS support in MAP | 9.1.0 | +| | 47 | C4-101010 | 0950 | 1 | UE-AMBR in GPRS Subscription | 9.1.0 | +| | 47 | CP-100234 | 0960 | | Incorrect KASME length | 9.1.0 | +| | 47 | CP-100203 | 0952 | 5 | EPS Subscriber State and Location Information Request | 9.1.0 | +| | 48 | C4-101236 | 0971 | | CR implementation CR 642 | 9.2.0 | +| | 48 | C4-101403 | 0963 | 1 | Correction to missing GANSS position data in Provide Subscriber Location and Provide Subscriber Location Report services | 9.2.0 | +| | 48 | C4-101400 | 0967 | 1 | Tracking Area Identity Length | 9.2.0 | +| | 48 | C4-101131 | 0961 | | ASN.1 Module Version Update | 9.2.0 | +| | 48 | C4-101135 | 0962 | | EPS state and location retrieval | 9.2.0 | +| | 49 | C4-101802 | 0975 | 1 | Sending of MME name or SGSN Number to the VLR during the data restoration procedure | 9.3.0 | +| | 49 | C4-101805 | 0977 | 1 | Data Restoration for SMS | 9.3.0 | +| | 49 | C4-102251 | 0966 | 3 | MAP SRI Return Error message | 9.3.0 | +| | 49 | C4-102269 | 0985 | 1 | EPS Subscription Data over Gr | 9.3.0 | +| | 49 | C4-102376 | 0980 | 3 | RP-OA modification in SMS Router | 9.3.0 | +| | 49 | C4-101809 | 0976 | 1 | Addition of SIPTO permissions in PS subscription data | 10.0.0 | +| | 49 | C4-102250 | 0957 | 4 | Prevention of Timeout in IP-SM-GW | 10.0.0 | + +| | | | | | | | +|--|----|-----------|------|---|---------------------------------------------------------------------------------------------------------------|--------| +| | 49 | CP-100608 | 0979 | 2 | Addition of SS codes to the ATSI and ATM procedures | 10.0.0 | +| | 50 | C4-103099 | 0990 | 2 | locationInformationEPS in Subscriber Info response | 10.1.0 | +| | 50 | C4-102699 | 0988 | 1 | Removal of MAP Update GPRS Location message during detach or last PDN connection deactivation via 3GPP access | 10.1.0 | +| | 50 | C4-102737 | 0993 | 1 | URRP for SGSN | 10.1.0 | +| | 50 | C4-103156 | 1005 | | Location data including only serving node address | 10.1.0 | +| | 50 | C4-103157 | 0997 | 2 | Correction to ATM for call waiting | 10.1.0 | +| | 50 | C4-103314 | 1002 | 2 | Periodic TAU/RAU timer in HSS subscription | 10.1.0 | +| | 50 | C4-102614 | 0991 | | ASN.1 module version upgrade | 10.1.0 | +| | 50 | C4-102687 | 0987 | 1 | Addition of MPS Priority in Subscription Data | 10.1.0 | +| | 50 | C4-102809 | 0986 | 1 | Addition of LIPA permission in Subscription Data | 10.1.0 | +| | 51 | C4-110389 | 1006 | 2 | UE SRVCC Capability Support in MAP Message | 10.2.0 | +| | 51 | C4-110292 | 1008 | 1 | Use of recovered MME Name / SGSN Name in MSC/VLR | 10.2.0 | +| | 51 | C4-110133 | 1009 | | Zone Code Propagation at Handover | 10.2.0 | +| | 51 | C4-110665 | 1016 | | Retrieval of T-ADS data via MAP ATI | 10.2.0 | +| | 51 | C4-110759 | 1018 | 1 | Mobile Terminating Roaming Forwarding | 10.2.0 | +| | 51 | C4-110778 | 1007 | 2 | Minimization of Drive Tests (MDT) | 10.2.0 | +| | 51 | C4-110793 | 1015 | 1 | Introduction of LCLS functionality in TS 29.002 | 10.2.0 | +| | 51 | C4-110958 | 1017 | 2 | Enhancements of T-ADS data retrieval via MAP ATI | 10.2.0 | +| | 52 | C4-111112 | 1024 | | Correction on Subscriber Data Withdrawal | 10.3.0 | +| | 52 | C4-111611 | 1030 | 2 | Missing MME Name in EPS Location Information | 10.3.0 | +| | 52 | C4-111534 | 1020 | 1 | MDT user consent | 10.3.0 | +| | 52 | C4-111567 | 1021 | 1 | SC Address in IP-SM-GW Register Response | 10.3.0 | +| | 52 | C4-111402 | 1025 | 1 | Periodic LAU timer in HSS subscription | 10.3.0 | +| | 52 | C4-111414 | 1026 | 1 | New LMSI handling for MTRF | 10.3.0 | +| | 52 | C4-111416 | 1029 | 1 | Addition of VMSC Address in PRN Ack | 10.3.0 | +| | 53 | C4-112067 | 1047 | | Use of UE-Reachability by SGSN | 10.4.0 | +| | 53 | C4-112081 | 1042 | 1 | APN-AMBR for GPRS | 10.4.0 | +| | 53 | C4-112096 | 1033 | 1 | MTRF and Super Charger interactions | 10.4.0 | +| | 53 | C4-111986 | 1043 | | ASN.1 exports for 32.298 | 11.0.0 | +| | 53 | C4-112033 | 1032 | 1 | Addition of Anonymous Call Rejection in the CS domain | 11.0.0 | +| | 53 | C4-112209 | 1037 | 2 | Add vSRVCC updates to the Gr interface | 11.0.0 | +| | 53 | C4-112222 | 1040 | 2 | MAP-READY-FOR-SM for IP-SM-GW | 11.0.0 | +| | 54 | C4-112930 | 1053 | 1 | Provide Subscriber Information handling for UE under LTE | 11.1.0 | +| | 54 | C4-112988 | 1063 | | PDN-Type | 11.1.0 | +| | 54 | C4-112990 | 1056 | 1 | Equivalent PLMN CSG Subscription Request | 11.1.0 | +| | 54 | C4-113037 | 1055 | 2 | LCLS negotiation MAP update | 11.1.0 | +| | 54 | C4-112464 | 1039 | 4 | Cancellation type initial attach | 11.1.0 | +| | 55 | C4-120406 | 1064 | 1 | Initial Attach Indication in MAP_CANCEL_LOCATION | 11.2.0 | +| | 55 | C4-120420 | 1073 | 1 | Removal of Subscribed Periodic TAU/RAU timer in HSS subscription | 11.2.0 | +| | 55 | C4-120528 | 1072 | 2 | User Unknown Error in Provide Subscriber Info MAP operation | 11.2.0 | +| | 55 | C4-120224 | 1066 | | UE reachability | 11.2.0 | +| | 55 | C4-120322 | 1070 | | TC-RT: Introduction of group IDs with prefix | 11.2.0 | +| | 55 | C4-120416 | 1067 | 1 | CSG subscription data propagation | 11.2.0 | +| | 55 | C4-120423 | 1069 | 1 | Trace Depth | 11.2.0 | +| | 56 | C4-120707 | 1078 | | Editorial corrections to TS 29.002 | 11.3.0 | +| | 56 | C4-120713 | 1079 | | Equivalent PLMN CSG Subscription Request for CS | 11.3.0 | +| | 56 | C4-120732 | 1080 | | EPS location in MAP Note MM Event | 11.3.0 | +| | 56 | C4-120959 | 1065 | 3 | CSG ID and Local Time for NPLI | 11.3.0 | +| | 56 | C4-121086 | 1082 | | Clarification on HLR procedure for SMS delivery via IP-SM-GW | 11.3.0 | +| | 56 | C4-121222 | 1059 | 4 | Procedures for Update VCSG Location service | 11.3.0 | +| | 56 | C4-121223 | 1049 | 9 | Retrieving CSG subscription data from the CSS to the VLR/SGSN | 11.3.0 | +| | 56 | C4-121227 | 1060 | 5 | CSG Data Management in the VPLMN | 11.3.0 | +| | 57 | C4-121465 | 1089 | - | TC RT: Number of Dispatcher extension | 11.4.0 | +| | 57 | C4-121635 | 1088 | 1 | Check IMEI Error | 11.4.0 | +| | 57 | C4-121805 | 1092 | 2 | Local Time Zone | 11.4.0 | +| | 57 | C4-121534 | 1084 | 1 | IMSI in MAP-MO-FORWARD-SHORT-MESSAGE | 11.4.0 | +| | 57 | C4-121817 | 1068 | 5 | PS additional number | 11.4.0 | +| | 57 | C4-121813 | 1090 | 2 | SRI for SM and MME Diameter address | 11.4.0 | +| | 57 | C4-121802 | 1091 | 2 | MSISDN-less MT-SMS | 11.4.0 | +| | 57 | C4-121625 | 1083 | 1 | PS only subscription w/o MSISDN | 11.4.0 | +| | 57 | C4-121809 | 1077 | 4 | SMS in MME/SGSN | 11.4.0 | +| | 57 | C4-121648 | 1085 | 1 | CSS Reset Procedures | 11.4.0 | +| | 57 | C4-121650 | 1086 | 2 | Temporary empty CSG subscription data | 11.4.0 | +| | 58 | C4-122660 | 1106 | 4 | Clarification on EPS Info | 11.5.0 | +| | 58 | C4-122497 | 1108 | 1 | Pdp Type | 11.5.0 | +| | 58 | C4-122164 | 1093 | 1 | Trace Depth extension | 11.5.0 | +| | 58 | C4-121847 | 1094 | | AC version for Reset | 11.5.0 | +| | 58 | C4-122469 | 1095 | 4 | MSISDN-less UEs | 11.5.0 | +| | 58 | C4-122476 | 1096 | 3 | T4 Device Trigger via IMS | 11.5.0 | +| | 58 | C4-122187 | 1097 | 2 | T4 Trigger indication to IP-SM-GW | 11.5.0 | +| | 58 | C4-122190 | 1098 | 2 | Add Diameter Addresses to MT-SMS target node registrations | 11.5.0 | +| | 58 | C4-121870 | 1099 | | IMSI in AbsentSubscriberSM-param | 11.5.0 | + +| | | | | | | | +|---------|-------|-----------|------|---|-------------------------------------------------------------------------------------------------------|--------| +| | 58 | C4-122165 | 1101 | 1 | Handling of current security context during inter-VLR location update | 11.5.0 | +| | 59 | C4-130330 | 1118 | 1 | SGSN acting on access restriction e-utranNotAllowed | 11.6.0 | +| | 59 | C4-130293 | 1119 | 1 | Registration for SMS Request for SMS in SGSN | 11.6.0 | +| | 59 | C4-130305 | 1120 | 1 | MDT parameters | 11.6.0 | +| | 59 | C4-130335 | 1121 | 1 | Providing Diameter identity of the SGSN to the GMLC over Lh interface | 12.0.0 | +| | 59 | C4-130340 | 1122 | 1 | SGSN indicating support of Lgd interface and providing its Diameter identity to HLR over Gr interface | 12.0.0 | +| | 59 | C4-130423 | 1123 | 2 | Validity Time of Short Message | 12.0.0 | +| | 59 | C4-130256 | 1114 | | Mobile Terminating call pending flag in MAP Send Identification response | 12.0.0 | +| | 60 | C4-131046 | 1147 | 2 | Subscribed RFSP index for Gn SGSNs | 12.1.0 | +| | 60 | C4-131061 | 1142 | 3 | MME identity for restoration procedures | 12.1.0 | +| | 60 | C4-130603 | 1128 | | Explicit T4-Trigger Indicator in SRI-SM | 12.1.0 | +| | 60 | C4-130929 | 1126 | 1 | Restoration Priority during SGW and PGW restoration procedures | 12.1.0 | +| | 60 | CP-130379 | 1132 | 3 | SIPTO permission for Local Network enhancements | 12.1.0 | +| | 60 | C4-130859 | 1131 | 1 | Clarification on RNC ID value | 12.1.0 | +| | 60 | C4-130979 | 1129 | 1 | Storing Last known Location Information of purged UE in HSS | 12.1.0 | +| | 60 | C4-131040 | 1135 | 2 | Maximum value for subscribed periodic timers | 12.1.0 | +| | 61 | C4-131488 | 1158 | 2 | Addition of Missing Supported Features | 12.2.0 | +| | 61 | C4-131261 | 1160 | | ASN.1 module version update | 12.2.0 | +| | 61 | C4-131540 | 1149 | 1 | Returning to former LTE PLMN after CSFB | 12.2.0 | +| | 61 | C4-131398 | 1152 | 2 | Complements for Gdd support | 12.2.0 | +| | 61 | C4-131445 | 1153 | 1 | GERAN Iu Mode | 12.2.0 | +| | 61 | C4-131478 | 1150 | 2 | CancelLocation requesting reattach | 12.2.0 | +| | 61 | C4-131529 | 1161 | | Enforcing access restriction during I-RAT RAU/TAU procedures | 12.2.0 | +| | 61 | C4-131370 | 1130 | 2 | SMS for IMS UE to IMS UE without MSISDN | 12.2.0 | +| | 62 | C4-131758 | 1162 | 1 | Addition of a reference to TS 23.018 for MTRF optimal routing | 12.3.0 | +| | 62 | C4-131759 | 1163 | 1 | Removal of Editor's Notes for Single-shot SM | 12.3.0 | +| | 62 | C4-131764 | 1165 | 1 | Clarification on Serving Node for SMS | 12.3.0 | +| | 62 | C4-132011 | 1167 | | MME Initiated Removal of MME Registration for SMS | 12.3.0 | +| | 62 | C4-132125 | 1169 | 1 | Update of Homogeneous Support of IMS Voice Over PS Sessions | 12.3.0 | +| | 62 | C4-132202 | 1171 | 1 | Time Zone retrieval from a Gn/Gp-SGSN | 12.3.0 | +| | 63 | C4-140243 | 1174 | 1 | Addition of SGSN CAMEL Capability to SupportedFeatures | 12.4.0 | +| | 64 | C4-140515 | 1177 | | CS to PS SRVCC | 12.5.0 | +| | 64 | C4-140897 | 1179 | | Indication of IMEISV during Inter- MSC Handover | 12.5.0 | +| | 65 | C4-141526 | 1181 | 1 | P-CSCF Restoration Indication | 12.6.0 | +| | 65 | C4-141653 | 1182 | 1 | Closing TS 29.234 and reused AVP in TS 29.273 | 12.6.0 | +| | 66 | C4-141778 | 1183 | 1 | MDT PLMN List | 12.7.0 | +| | 66 | C4-142039 | 1187 | 1 | WLAN offloadability for MAP | 12.7.0 | +| | 68 | C4-150647 | 1188 | 1 | Access restriction per VPLMN | 13.0.0 | +| | 68 | C4-150880 | 1190 | | Access Restriction Data per PLMN | 13.0.0 | +| | 69 | C4-151177 | 1191 | | ASN.1 module version update | 13.1.0 | +| | 70 | C4-151631 | 1194 | | Reference Correction | 13.2.0 | +| | 70 | C4-151813 | 1192 | 1 | Introducing IMSI-Group ID Lists to the insert subscriber data | 13.2.0 | +| | 70 | C4-151801 | 1195 | 1 | Retrieval of "UE Usage Type" over MAP-Gr | 13.2.0 | +| | 70 | C4-152198 | 1196 | 1 | Positioning enhancement impacts on MAP protocol | 13.2.0 | +| | 70 | CP-150868 | 1198 | 2 | Mobile Terminating SMS handling for extended Idle mode DRX – Additional Option | 13.2.0 | +| | 70 | CP-150869 | 1197 | 2 | Mobile Terminating SMS handling for extended Idle mode DRX | 13.2.0 | +| | 71 | C4-161271 | 1202 | 1 | Alert procedure from MME/SGSN to SMS-GMSC for MT SMS to UE using eDRX | 13.3.0 | +| | 71 | C4-161062 | 1200 | | Requested Retransmission Time in MT-Forward-SM response | 13.3.0 | +| | 71 | C4-161527 | 1205 | 2 | New PDN-Type for Cellular IoT | 13.3.0 | +| | 71 | C4-161492 | 1204 | 2 | Addition of NB-IoT radio access type to the Access-Restriction-Data feature | 13.3.0 | +| | 71 | C4-161161 | 1203 | | Time Zone in MAP-Any-Time-Interrogation | 13.3.0 | +| | 71 | C4-161317 | 1201 | 1 | User Plane Integrity Protection Indicator | 13.3.0 | +| | 72 | C4-162090 | 1213 | | Clause Numbering | 13.4.0 | +| | 72 | C4-163271 | 1215 | 3 | Group-Service-Id | 13.4.0 | +| 2016-06 | CT#72 | CP-160217 | 1216 | 1 | Use of recovered MME Name / SGSN Name in MSC/VLR | 14.0.0 | +| 2016-06 | CT#72 | CP-160217 | 1214 | 1 | Zone Code Propagation at Handover | 14.0.0 | +| 2016-09 | CT#73 | CP-160430 | 1219 | | Retrieval of T-ADS data via MAP ATI | 14.1.0 | +| 2016-09 | CT#73 | CP-160583 | 1218 | 2 | Mobile Terminating Roaming Forwarding | 14.1.0 | +| 2016-09 | CT#73 | CP-160423 | 1221 | 1 | Minimization of Drive Tests (MDT) | 14.1.0 | +| 2016-12 | CT#74 | CP-160667 | 1225 | 1 | Introduction of LCLS functionality in TS 29.002 | 14.2.0 | +| 2016-12 | CT#74 | CP-160665 | 1229 | 1 | Enhancements of T-ADS data retrieval via MAP ATI | 14.2.0 | +| 2016-12 | CT#74 | CP-160659 | 1227 | | Correction on Subscriber Data Withdrawal | 14.2.0 | +| 2016-12 | CT#74 | CP-160683 | 1230 | 3 | Missing MME Name in EPS Location Information | 14.2.0 | +| 2016-12 | CT#74 | CP-160657 | 1233 | | MDT user consent | 14.2.0 | +| 2016-12 | CT#74 | CP-160683 | 1231 | 1 | SC Address in IP-SM-GW Register Response | 14.2.0 | +| 2017-03 | CT#75 | CP-170034 | 1236 | | T4 Triggering | 14.3.0 | +| 2017-03 | CT#75 | CP-170039 | 1234 | 1 | Enhanced Coverage | 14.3.0 | +| 2017-03 | CT#75 | CP-170039 | 1235 | 1 | Inter-RAT PDN-Continuity | 14.3.0 | +| 2017-03 | CT#76 | CP-171039 | 1237 | - | T-ADS info retrieval | 15.0.0 | +| 2017-09 | CT#77 | CP-172021 | 1239 | - | ASN.1 module version update | 15.1.0 | + +| | | | | | | | +|---------|--------|-----------|------|---|----------------------------------------------------------------------|--------| +| 2017-12 | CT#78 | CP-173016 | 1243 | 2 | Correction on subscribed eDRX parameter value | 15.2.0 | +| 2017-12 | CT#78 | CP-173036 | 1240 | - | Access Restrictions to NR as Secondary RAT | 15.2.0 | +| 2017-12 | CT#78 | CP-173036 | 1241 | - | Extended Qos | 15.2.0 | +| 2018-03 | CT#79 | CP-180027 | 1244 | 2 | Access restriction to unlicensed spectrum as secondary RAT | 15.3.0 | +| 2018-10 | | | | | Cover page version number was corrected | 15.3.1 | +| 2018-12 | CT#82 | C4-187638 | 1245 | 2 | Location Information used by IM-SSF in 5G | 15.4.0 | +| 2019-06 | CT#84 | CP-191020 | 1249 | | ASN.1 corrections | 15.5.0 | +| 2019-06 | CT#84 | CP-191058 | 1250 | 1 | SMSF Address | 15.5.0 | +| 2020-03 | CT#87 | CP-200049 | 1253 | | Correction on Location Information used by IM-SSF in 5G | 15.6.0 | +| 2020-03 | CT#87 | CP-200027 | 1251 | 3 | Addition of IAB operation permission to subscriber data | 16.0.0 | +| 2020-12 | CT#90e | CP-203027 | 1255 | | Inform SC | 16.1.0 | +| 2020-12 | CT#90e | CP-203027 | 1257 | | SMSF parameter description | 16.1.0 | +| 2021-03 | CT#91e | CP-210053 | 1260 | | Correction on length of 5GS TAI | 16.2.0 | +| 2021-03 | CT#91e | CP-210036 | 1261 | | Clarification for dummy Network Node Number | 17.0.0 | +| 2021-03 | CT#91e | CP-210036 | 1259 | 1 | Support of MAP messages at the UDM for SMS in 5GS | 17.0.0 | +| 2021-06 | CT#92e | CP-211075 | 1263 | | ASN.1 module version update | 17.1.0 | +| 2021-06 | CT#92e | CP-211319 | 1265 | | Misimplemented CR on Inclusive language review: EIR lists | 17.1.0 | +| 2022-06 | CT#96 | CP-221045 | 1266 | - | 3GPP TS 23.107 missing in clause 2 | 17.2.0 | +| 2023-06 | CT#100 | CP-231075 | 1267 | 1 | Missing finer periodicities than 1s and an infinite reporting amount | 17.3.0 | +| 2023-09 | CT#101 | CP-232075 | 1270 | 1 | Missed LCS QoS Class | 17.4.0 | +| 2023-09 | CT#101 | CP-232058 | 1268 | - | ASN.1 module version update | 18.0.0 | + +5217 \ No newline at end of file diff --git a/marked/Rel-18/29_series/29010/raw.md b/marked/Rel-18/29_series/29010/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6849b37bd9d6ad067fdf33a48ea137fb5a40d464 --- /dev/null +++ b/marked/Rel-18/29_series/29010/raw.md @@ -0,0 +1,6387 @@ + + +# 3GPP TS 29.010 V18.0.0 (2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling procedures and the Mobile Application Part (MAP) (Release 18)** + +![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for LTE Advanced Pro, featuring the word "lte" in black lowercase letters with a green signal icon above the "t", and the words "Advanced Pro" in red and green text to the right. + +LTE Advanced Pro logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters "3GPP" in a stylized black font with a red signal icon below the "G", and the text "A GLOBAL INITIATIVE" in black capital letters below it. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 1.1 References ..... | 7 | +| 1.2 Abbreviations ..... | 8 | +| 1.3 Definitions..... | 8 | +| 2 Classification of interworking cases ..... | 9 | +| 2.1 Transparent procedures ..... | 9 | +| 2.2 Non-transparent procedures ..... | 9 | +| 3 Interworking in the MSC, Transparent case ..... | 9 | +| 3.1 General ..... | 9 | +| 3.2 Routeing area updating..... | 12 | +| 3.3 Authentication ..... | 13 | +| 3.4 Retrieval of the IMSI from the MS ..... | 14 | +| 3.5 Reallocation of TMSI..... | 15 | +| 3.6 Retrieval of the IMEI from the MS ..... | 15 | +| 3.7 Tracing subscriber activity ..... | 16 | +| 3.8 Location update ..... | 17 | +| 4 Interworking in the MSC, Non-transparent cases..... | 18 | +| 4.1 General ..... | 18 | +| 4.2 Outgoing call set-up (MS originating call) ..... | 18 | +| 4.3 Incoming call set-up (MS terminating call) ..... | 22 | +| 4.4 Cipher mode setting ..... | 24 | +| 4.5 Inter-MSC Handover..... | 24 | +| 4.5.1 Basic Inter-MSC Handover ..... | 25 | +| 4.5.2 Subsequent Inter-MSC Handover back to MSC-A ..... | 30 | +| 4.5.3 Subsequent Inter-MSC Handover to third MSC ..... | 34 | +| 4.5.4 BSSAP Messages transfer on E-Interface ..... | 37 | +| 4.5.5 Processing in MSC-B, and information transfer on E-interface..... | 38 | +| 4.5.5.1 Encryption Information..... | 39 | +| 4.5.5.2 Channel Type..... | 39 | +| 4.5.5.3 Classmark..... | 40 | +| 4.5.5.4 Downlink DTX-Flag..... | 40 | +| 4.5.5.5 Priority ..... | 41 | +| 4.5.5.6 MSC/BSC-Invoke Trace Information Elements..... | 41 | +| 4.5.5.7 LSA Identifier List..... | 41 | +| 4.5.5.8 Selected UMTS Algorithm ..... | 41 | +| 4.5.5.9 Allowed UMTS Algorithms ..... | 41 | +| 4.5.5.10 BSSMAP Service Handover..... | 42 | +| 4.5.5.11 RANAP Service Handover ..... | 42 | +| 4.5.5.12 SNA Access Information ..... | 42 | +| 4.5.5.13 UESBI..... | 43 | +| 4.5.5.14 Alternative Channel Type..... | 43 | +| 4.5.5.15 Trace parameters..... | 43 | +| 4.5.6 Overview of the Technical Specifications GSM interworking for the Inter-MSC Handover..... | 43 | +| 4.6 Inter-MSC Handover (UMTS to GSM) ..... | 45 | +| 4.6.1 Basic Inter-MSC Handover ..... | 45 | +| 4.6.2 Subsequent Inter-MSC Handover from 3G-MSC-B back to MSC-A..... | 50 | +| 4.6.3 Subsequent Inter-MSC Handover to third MSC ..... | 54 | +| 4.6.4 BSSAP Messages transfer on E-Interface ..... | 58 | +| 4.6.5 Processing in MSC-B, and information transfer on E-interface..... | 58 | +| 4.6.6 Cause Code Mapping ..... | 58 | +| 4.7 Inter-MSC Handover (GSM to UMTS) ..... | 60 | +| 4.7.1 Basic Inter-MSC Handover ..... | 60 | +| 4.7.2 Subsequent Inter-MSC Handover from MSC-B back to 3G_MSC-A ..... | 66 | +| 4.7.3 Subsequent Inter-MSC Handover to third MSC ..... | 71 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------|-----| +| 4.7.4 | BSSAP Messages transfer on E-Interface ..... | 73 | +| 4.7.4.1 | Assignment ..... | 73 | +| 4.7.4.2 | Cipher Mode Control ..... | 74 | +| 4.7.4.3 | Location Reporting Control ..... | 75 | +| 4.7.5 | Processing in 3G_MSC-B, and information transfer on E-interface..... | 75 | +| 4.7.5.1 | Encryption Information..... | 76 | +| 4.7.5.2 | Channel Type..... | 76 | +| 4.7.5.3 | Classmark..... | 76 | +| 4.7.5.4 | Priority ..... | 76 | +| 4.7.5.5 | MSC-Invoke Trace Information Elements ..... | 77 | +| 4.7.5.6 | Selected UMTS Algorithm ..... | 77 | +| 4.7.5.7 | Allowed UMTS Algorithms ..... | 77 | +| 4.7.5.8 | BSSMAP Service Handover..... | 78 | +| 4.7.5.9 | RANAP Service Handover ..... | 78 | +| 4.7.5.10 | GERAN Classmark..... | 78 | +| 4.7.5.11 | SNA Access Information ..... | 79 | +| 4.7.5.12 | UESBI..... | 79 | +| 4.7.5.13 | Alternative Channel Type..... | 79 | +| 4.7.5.14 | Trace parameters ..... | 79 | +| 4.7.6 | Cause Code Mapping ..... | 79 | +| 4.8 | Inter-MSC Relocation ..... | 83 | +| 4.8.1 | Basic Inter-MSC Relocation..... | 83 | +| 4.8.2 | Subsequent Inter-MSC Relocation back to 3G_MSC-A..... | 88 | +| 4.8.3 | Subsequent Inter-MSC Relocation to third MSC..... | 92 | +| 4.8.4 | RANAP Messages transfer on E-Interface..... | 95 | +| 4.8.5 | Processing in 3G_MSC-B, and information transfer on E-interface..... | 96 | +| 4.8.5.1 | Integrity Protection Information ..... | 96 | +| 4.8.5.2 | Encryption Information..... | 97 | +| 4.8.5.3 | RAB Parameters ..... | 97 | +| 4.8.5.4 | Channel Type..... | 97 | +| 4.8.5.5 | Selected GSM Algorithm..... | 98 | +| 4.8.5.6 | Allowed GSM Algorithms..... | 98 | +| 4.8.5.7 | Chosen Channel..... | 99 | +| 4.8.5.8 | BSSMAP Service Handover..... | 99 | +| 4.8.5.9 | RANAP Service Handover ..... | 99 | +| 4.8.5.10 | GERAN Classmark..... | 99 | +| 4.8.5.11 | SNA Access Information ..... | 100 | +| 4.8.5.12 | UESBI..... | 100 | +| 4.8.5.13 | Alternative RAB Parameters Value..... | 100 | +| 4.8.5.14 | Trace parameters ..... | 100 | +| 4.8.6 | Overview of the Technical Specifications 3GPP interworking for the Inter-MSC Relocation ..... | 101 | +| 4.9 | Location Services ..... | 103 | +| 4.9.1 | Completed Location Acquisition..... | 103 | +| 4.9.1.1 | Inter-MSC Handover (GSM to GSM)..... | 103 | +| 4.9.1.2 | Inter-MSC Handover (GSM to UMTS) ..... | 104 | +| 4.9.1.3 | Inter-MSC Handover (UMTS to GSM) ..... | 106 | +| 4.9.1.4 | Inter-MSC SRNS Relocation ..... | 107 | +| 4.9.2 | Cause Code Mapping ..... | 110 | +| 4.9.2.1 | Inter-MSC Handover (GSM to GSM)..... | 110 | +| 4.9.2.2 | Inter-MSC Handover (GSM to UMTS) ..... | 110 | +| 4.9.2.3 | Inter-MSC Handover (UMTS to GSM) ..... | 111 | +| 4.9.2.4 | Inter-MSC SRNS Relocation ..... | 111 | +| 4.9.3 | Aborted Location Acquisition ..... | 111 | +| 4.9.3.1 | Inter-MSC Handover (GSM to GSM)..... | 111 | +| 4.9.3.2 | Inter-MSC Handover (GSM to UMTS) ..... | 112 | +| 4.9.3.3 | Inter-MSC Handover (UMTS to GSM) ..... | 114 | +| 4.9.3.4 | Inter-MSC SRNS Relocation ..... | 115 | +| 4.9.4 | Request of Assistance Data or De-ciphering Keys: Successful Case..... | 118 | +| 4.9.4.1 | Inter-MSC Handover (GSM to GSM)..... | 118 | +| 4.9.4.2 | Inter-MSC Handover (GSM to UMTS) ..... | 119 | +| 4.9.4.3 | Inter-MSC Handover (UMTS to GSM) ..... | 122 | +| 4.9.4.4 | Inter-MSC SRNS Relocation ..... | 123 | + +| | | | +|----------------------------------------------------|--------------------------------------------------------------------------------|------------| +| 4.9.5 | Request of Assistance Data or De-ciphering Keys: Failure Case ..... | 127 | +| 4.9.5.1 | Inter-MSC Handover (GSM to GSM)..... | 127 | +| 4.9.5.2 | Inter-MSC Handover (GSM to UMTS) ..... | 128 | +| 4.9.5.3 | Inter-MSC Handover (UMTS to GSM) ..... | 129 | +| 4.9.5.4 | Inter-MSC SRNS Relocation ..... | 130 | +| 4.9.6 | Abort of Request of Assistance Data or De-ciphering Keys:..... | 132 | +| 4.9.6.1 | Inter-MSC Handover (GSM to GSM)..... | 132 | +| 4.9.6.2 | Inter-MSC Handover (GSM to UMTS) ..... | 134 | +| 4.9.6.3 | Inter-MSC Handover (UMTS to GSM) ..... | 135 | +| 4.9.6.4 | Inter-MSC SRNS Relocation ..... | 135 | +| 4.10 | Single Radio Voice Call Continuity (SRVCC)..... | 135 | +| 4.10.1 | General ..... | 135 | +| 4.10.2 | SRVCC Handover from UTRAN (HSPA) to GERAN ..... | 135 | +| 4.10.3 | SRVCC Handover from UTRAN (HSPA) to UTRAN ..... | 135 | +| 4.10.4 | SRVCC Handover from E-UTRAN to GERAN ..... | 135 | +| 4.10.5 | SRVCC Handover from E-UTRAN to UTRAN ..... | 135 | +| 5 | Interworking in the MME ..... | 136 | +| 5.1 | General ..... | 136 | +| 5.2 | Void..... | 136 | +| 5.3 | Interworking between RANAP protocol messages and SIAP protocol messages ..... | 136 | +| 5.4 | Interworking between BSSGP protocol messages and SIAP protocol messages ..... | 137 | +| 6 | Interworking in the S4-SGSN..... | 139 | +| 6.1 | General ..... | 139 | +| 6.2 | Interworking between RANAP protocol messages and SIAP protocol messages ..... | 139 | +| 6.3 | Interworking between BSSGP protocol messages and SIAP protocol messages ..... | 140 | +| 6.4 | Interworking between BSSGP protocol messages and RANAP protocol messages ..... | 140 | +| 7 | Interworking in the AMF ..... | 141 | +| 7.1 | General ..... | 141 | +| 7.2 | Interworking between SIAP protocol messages and NGAP protocol messages..... | 141 | +| Annex A (informative): Change history ..... | | 143 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC) Signalling procedures and the Mobile Application Part (MAP) within the digital cellular telecommunications system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The scope of the present document is: + +- i) to provide a detailed specification for the interworking between information elements contained in layer 3 messages sent on the MS-MSC interface (Call Control and Mobility Management parts of 3GPP TS 24.008 [4]) and parameters contained in MAP services sent over the MSC-VLR interface (3GPP TS 29.002 [9]) where the MSC acts as a transparent relay of information; +- ii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages sent on the BSC-MSC interface (3GPP TS 48.008 [12]) and parameters contained in MAP services sent over the MSC-VLR interface (3GPP TS 29.002 [9]) where the MSC acts as a transparent relay of information; +- iii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages (3GPP TS 48.008 [12]) and RANAP ((3GPP TS 25.413 [7])); +- iv) to provide a detailed specification for the interworking as in i) and ii) above when the MSC also processes the information; +- v) to provide a detailed specification for the interworking between information elements contained in layer 3 messages sent on the MS-SGSN interface (GPRS mobility part of 3GPP TS 24.008 [4]) and parameters contained in MAP services sent over the SGSN-HLR interface (3GPP TS 29.002 [9]); +- vi) to provide a detailed specification for the interworking between information elements contained in RANAP messages sent on the SGSN-RNC interface (3GPP TS 25.413 [7]) and parameters contained in SIAP messages sent on the MME-eNodeB interface (3GPP TS 36.413 [21]); +- vii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages (3GPP TS 48.008 [12]) or RANAP messages (3GPP TS 25.413 [7]) during SRVCC handovers. + +Interworking for supplementary services is given in 3GPP TS 29.011 [11]. Interworking for the short message service is given in 3GPP TS 23.040 [3] and 3GPP TS 24.011. Interworking between the call control signalling of 3GPP TS 24.008 [4] and the PSTN/ISDN is given in GSM 09.03 [13], 3GPP TS 29.007 [10] and 3GPP TS 49.008 [14] [14]. Interworking between the 'A' and 'E' interfaces for inter-MSC handover signalling is given in 3GPP TS 29.007 [10] and 3GPP TS 49.008 [14] [14]. + +## 1.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 21.905: "3G Vocabulary". +- [2] 3GPP TS 23.009: "Handover procedures". +- [3] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)". +- [4] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols-Stage 3". +- [5] 3GPP TS 24.010: "Mobile radio interface layer 3 Supplementary services specification - General aspects". + +- [6] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". +- [7] 3GPP TS 25.413: "Iu interface RANAP signalling". +- [8] 3GPP TS 27.001: " General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [9] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [10] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [11] 3GPP TS 29.011: "Digital cellular telecommunications system (Phase 2+); Signalling interworking for supplementary services". +- [12] 3GPP TS 48.008: " Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification". +- [13] GSM 09.03: "Digital cellular telecommunications system (Phase 2+); Signalling requirements on interworking between the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) and the Public Land Mobile Network (PLMN)". +- [14] 3GPP TS 49.008 [14]: "Digital cellular telecommunications system (Phase 2+); Application of the Base Station System Application Part (BSSAP) on the E-interface". +- [15] 3GPP TS 29.108: "Application of the Radio Access Network Application Part (RANAP) on the E-interface" +- [16] 3GPP TS 23.271: "Functional stage 2 description of LCS" +- [17] 3GPP TS 43.051: "Technical Specification Group GSM/EDGE; Radio Access Network; Overall description - Stage 2". +- [18] 3GPP TS 23.012: "Location management procedures". +- [19] Void. +- [20] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)". +- [21] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network E-UTRAN; S1 Application Protocol (S1AP)". +- [22] 3GPP TS 23.401: " General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ". +- [23] 3GPP TS 29.060: "GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface". +- [24] 3GPP TS 48.018: " Base Station System (BSS) -Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [25] 3GPP TS 29.280: "3GPP EPS Sv interface (MME to MSC) for SRVCC". +- [26] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". + +## 1.2 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TS 21.905 [1]. + +## 1.3 Definitions + +The following terms are used in this Technical Specification: + +**A/Gb mode:** mode of operation of the MS when connected to the Core Network via GERAN and the A and/or Gb interfaces. Throughout this specification the term GSM refers to GERAN A/Gb mode. + +**Iu mode:** mode of operation of the MS when connected to the Core Network via GERAN or UTRAN and the Iu interface. Throughout this specification the term UMTS refers to UTRAN or GERAN Iu mode. + +# --- 2 Classification of interworking cases + +## 2.1 Transparent procedures + +The following MSC procedures require transparent mapping of access protocol information elements into MAP parameters and vice versa (see 3GPP TS 29.002 [9] for definitions and the use of the procedures): + +- location update; +- forward new TMSI; +- provide IMSI; +- obtain IMEI; +- check IMEI; +- authenticate; +- trace subscriber activity. + +## 2.2 Non-transparent procedures + +Procedures in this class require processing in the MSC and information element mapping. These procedures include those related to: + +- outgoing call set-up; +- incoming call set-up; +- handover; +- cipher mode setting; +- location services. + +# --- 3 Interworking in the MSC, Transparent case + +## 3.1 General + +When the MSC receives a forward message from the BSS (possibly forwarded transparently from the MS), it will invoke the desired MAP service and establish a cross reference between the BSSAP procedure and the MAP procedure in order to return the result of the operation to the BSS (which may forward it transparently to the MS. The cross reference is deleted when the MSC terminates the MAP procedure. + +Positive or negative results of the MAP procedure are returned in the appropriate BSSAP message. + +The parameters of the forward BSSAP message are mapped by a one-to-one mapping into the parameters of the MAP service. However, in some cases parameters received on the radio path may be suppressed at the MSC because they are related to another protocol entity, e.g. information related to RR-management may be included in MM-management messages. Similarly, parameters received in the (positive) MAP service response are mapped one-to-one into parameters of the corresponding backward BSSAP message. + +A negative outcome, as carried in various MAP services (MAP specific service response, MAP\_U\_ABORT, MAP\_P\_ABORT, MAP\_NOTICE and premature MAP\_CLOSE, see 3GPP TS 29.002 [9] for definitions) is mapped into a cause value in the required backward BSSAP message. In this case several negative results of MAP may be mapped into the same BSSAP cause value, i.e. without discrimination between these negative results. + +NOTE: For O & M purposes, the MAP procedure entity in the MSC may require a more detailed overview of negative results than the MS. + +These principles are illustrated in figure 1. + +![Figure 1: Illustration of mapping principles in the MSC. The diagram shows three examples of message mapping between 24.008 (48.008) forward messages and MAP service requests, positive acks and responses, and negative causes and responses. The first example shows a one-to-one mapping for a forward message to a MAP service request. The second example shows a one-to-one mapping for a positive ack to a MAP service response. The third example shows a one-to-one or many-to-one mapping for negative causes to a negative response.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +24.008 (48.008) forward message + +MAP service request + +information element + +parameter + +one-to-one mapping + +positive ack + +MAP service response + +information element + +parameter + +one-to-one mapping + +negative cause + +negative response + +cause + +cause + +one-to-one or many-to-one mapping + +Figure 1: Illustration of mapping principles in the MSC. The diagram shows three examples of message mapping between 24.008 (48.008) forward messages and MAP service requests, positive acks and responses, and negative causes and responses. The first example shows a one-to-one mapping for a forward message to a MAP service request. The second example shows a one-to-one mapping for a positive ack to a MAP service response. The third example shows a one-to-one or many-to-one mapping for negative causes to a negative response. + +**Figure 1: Illustration of mapping principles in the MSC** + +For each of the transparent operations listed in clause 2.1, the following format is used to show the mapping. + +| | 24.008 or 48.008 | 29.002 | Notes | +|-----------------|--------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|-------| +| Forward message | MS/BSS to MSC
message name
information element 1
information element 2 | MSC to VLR
MAP service request
parameter 1
parameter 2 | | +| Positive result | MSC to MS/BSS
message name
information element 1
information element 2 | VLR to MSC
positive response
parameter 1
parameter 2 | | +| Negative result | MSC to MS/BSS
message name
cause 1
cause 2
cause 3
cause 3
cause 3 | VLR to MSC
negative response
cause 1
cause 2
MAP U/P ABORT
MAP NOTICE
MAP CLOSE | | + +Equivalent mapping principles apply for operations invoked by the VLR towards the BSS/MS. However, negative results are generally not received from the BSS/MS but are generated in the MSC. Therefore, for such operations the interworking for negative results is not normally shown. + +## 3.2 Routeing area updating + +| | 24.008 | 29.002 | Notes | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------| +| Forward message | GMM (ROUTEING AREA UPDATE REQUEST)
MS classmark 1
MS classmark 4
GPRS Ciphering key seq number
Mobile station identity
Old routeing area identification | MAP UPDATE GPRS LOCATION-request -
-
-
-
IMSI
- | | +| Positive results | GMM (ROUTEING AREA UPDATE ACCEPT)
Routeing area identification
Mobile station identity
C Mobile station
C Reject: IMSI unknown in HLR
C Reject: MSC temporarily not reachable | MAP UPDATE GPRS LOCATION-response
-
-
-
-
- | 1
2
3
4 | +| Negative results | GMM (ROUTEING AREA UPDATE REJECT)
Network failure
GPRS services not allowed in this PLMN
GPRS services not allowed
GPRS services and non GPRS services not allowed
C GPRS services not allowed
C GPRS services and non-GPRS services not allowed
MS identity cannot be derived by the network
GPRS services not allowed in this PLMN
LA not allowed
Roaming not allowed in this LA
No Suitable cells in location area
GPRS services not allowed in this PLMN
GPRS services not allowed in this PLMN
C GPRS services not allowed in this PLMN
No Suitable cells in location area
Illegal MS
Illegal ME
Network failure
Network failure
Network failure
Network failure | MAP UPDATE GPRS LOCATION-response
-
Unknown HLR
Unknown subscriber (no GPRS subscription)
Unknown subscriber (IMSI unknown)
Unknown subscriber (no GPRS subscription)
Unknown subscriber (IMSI unknown)
-
Roaming not allowed: PLMN not allowed
-
-
-
Operator determined barring
-
-
Additional roaming not allowed: Supported RAT Types not allowed
-
-
System Failure
Unexpected data value
MAP U/P ABORT
MAP_NOTICE | 5
6
7
8
9
10
11
12
12
12
13 | + +![Sequence diagram fragment showing Network failure and MAP_CLOSE messages.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +A sequence diagram fragment showing two vertical lifelines. The left lifeline is labeled "Network failure" and the right lifeline is labeled "MAP\_CLOSE". A dashed horizontal line connects the two lifelines, representing a message exchange. The diagram is partially cut off by the left and right edges of the page. + +Sequence diagram fragment showing Network failure and MAP\_CLOSE messages. + +- NOTE 1: The mobile station identity is inserted by the SGSN if the SGSN wants to deallocate or re-allocate a P-TMSI. If the SGSN wants to deallocate the P-TMSI it shall include the IMSI. If the SGSN wants to re-allocate the P-TMSI it shall include the new P-TMSI. If a P-TMSI is included, the MS shall respond with a ROUTING AREA UPDATE COMPLETE message. +- NOTE 2: The mobile station identity is inserted by the SGSN if it is received in a BSSAP+ LOCATION UPDATE ACCEPT message from the VLR. If a TMSI is included, the MS shall respond with a ROUTING AREA UPDATE COMPLETE message. Only used in the Combined Routing and Location Area procedure. +- NOTE 3: This reject cause is inserted on the positive response by the SGSN if the SGSN receives a BSSAP+ LOCATION UPDATE REJECT message from the VLR indicating in the reject cause IMSI unknown in HLR. Only used in the Combined Routing and Location Area procedure. +- NOTE 4: This reject cause is inserted on the positive response by the SGSN if the SGSN does not receive any response from the VLR to a previous BSSAP+ LOCATION UPDATE REQUEST message. Only used in the Combined Routing and Location Area procedure. +- NOTE 5: The Unknown RA error is only generated as a result of incorrect information being inserted by the BSS. +- NOTE 6: The HLR shall send Unknown subscriber with diagnostic value No GPRS subscription if the HLR indicates that there is an error in the type of subscription (i.e. SGSN requests service for a non-GPRS only subscriber). The HLR may also send this error in the MAP SEND AUTHENTICATION INFO RESPONSE message. +- NOTE 7: The HLR shall send Unknown subscriber with diagnostic value IMSI unknown if the HLR indicates that the IMSI provided by the SGSN is unknown. +- NOTE 8: The HLR shall send Unknown subscriber with diagnostic value No GPRS subscription if the HLR indicates that there is an error in the type of subscription (i.e. SGSN requests service for a non-GPRS only subscriber). Used in the Combined Routing and Location Area procedure. The HLR may also send this error in the MAP SEND AUTHENTICATION INFO RESPONSE message. +- NOTE 9: This reject cause is inserted if the SGSN receives a MAP GPRS UPDATE LOCATION negative response message indicating IMSI unknown. Used in the Combined Routing and Location Area procedure. +- NOTE 10: This reject cause is inserted if the SGSN does not receive any response from the old SGSN to a previous SGSN CONTEXT REQUEST message. +- NOTE 11: The "No Suitable cells in location area" error is generated when the MS has access to only part of the PLMN e.g. due to Administrative Restriction of Subscribers' Access, but where there may also be suitable location areas available. The MS retries on another location area. The recommended cause due to Administrative Restriction of Subscriber's Access is "No Suitable Cells in Location Area", but cause "Roaming Not Allowed in this LA" may also be used, based on operator configuration. +- NOTE 12: This reject cause is inserted if the SGSN receives in MAP INSERT SUBSCRIBER DATA message an indication of Roaming restricted in SGSN due to unsupported feature. +- NOTE 13: Other reject causes than "no Suitable cells in location area" can be used (e.g. "Roaming not allowed in this location area"). +- NOTE 14: The cause "LA not allowed" shall be sent only if the HLR indicates that due to subscription to a "regionally restricted service" the MS is not allowed to operate in the location area. + +## 3.3 Authentication + +The message flow for the authentication procedure is shown in figure 2. + +![Sequence diagram of the authentication operation between MS, MSC, and VLR. The MSC sends a MAP_AUTHENTICATE request to the VLR. The VLR sends a MAP_AUTHENTICATE response or a MAP_U/P_ABORT to the MSC. The MSC sends an AUTHENTICATION REQUEST to the MS. The MS sends an AUTHENTICATION RESPONSE to the MSC.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note right of MSC: MAP_AUTHENTICATE request + MSC->>VLR: MAP_AUTHENTICATE request + Note right of VLR: MAP_AUTHENTICATE response or MAP_U/P_ABORT + VLR-->>MSC: MAP_AUTHENTICATE response or MAP_U/P_ABORT + Note left of MSC: AUTHENTICATION REQUEST + MSC->>MS: AUTHENTICATION REQUEST + Note left of MS: AUTHENTICATION RESPONSE + MS-->>MSC: AUTHENTICATION RESPONSE + +``` + +Sequence diagram of the authentication operation between MS, MSC, and VLR. The MSC sends a MAP\_AUTHENTICATE request to the VLR. The VLR sends a MAP\_AUTHENTICATE response or a MAP\_U/P\_ABORT to the MSC. The MSC sends an AUTHENTICATION REQUEST to the MS. The MS sends an AUTHENTICATION RESPONSE to the MSC. + +Figure 2: Authentication operation + +The MSC can only act on a MAP\_AUTHENTICATE request if an RR connection exists with the MS. If such a connection does not exist, the MSC shall terminate the MAP procedure with a MAP\_U\_ABORT. The same applies if the MS does not respond to an AUTHENTICATION REQUEST message. + +| | 24.008 | 29.002 | Notes | +|-----------------|--------------------------------------------------------------------|--------------------------------------------------|-------| +| Forward message | AUTHENTICATION REQUEST

RAND

Ciphering key seq number | MAP_AUTHENTICATE request

RAND

CKSN | | +| Backward result | AUTHENTICATION RESPONSE

SRES | MAP_AUTHENTICATE response

SRES | | + +If the SRES parameter does not match the value stored in the VLR, then the ongoing MAP procedure shall be terminated with a cause 'illegal subscriber'. This shall cause the MSC to send an AUTHENTICATION REJECT message. + +## 3.4 Retrieval of the IMSI from the MS + +The VLR may request open identification of an MS with a MAP\_PROVIDE\_IMSI request. + +The mapping of information elements is as follows: + +| | 24.008 | 29.002 | Notes | +|-----------------|----------------------------------------------------|---------------------------|-------| +| Forward message | IDENTITY REQUEST

Identity type set to: IMSI | MAP_PROVIDE_IMSI request | 1 | +| Backward result | IDENTITY RESPONSE
Mobile Identity (IMSI) | MAP_PROVIDE_IMSI response | | + +NOTE 1: The INVOKE does not carry any parameters. The identity type is inferred from the invoke name. + +The MSC shall return a MAP\_PROVIDE\_IMSI response with user error "absent subscriber" if: + +- there is no RR connection with the MS when the MAP service request is received; +- there is no response from the MS. + +## 3.5 Reallocation of TMSI + +This operation is invoked by the VLR. The MAP\_FORWARD\_NEW\_TMSI request contains the new TMSI which is forwarded to the MS in the TMSI REALLOCATION COMMAND. When the MS acknowledges the receipt of the new TMSI, the MSC will return a MAP\_FORWARD\_NEW\_TMSI response to the VLR. + +If there is no radio connection to the MS when the MSC receives the MAP service request, the MSC shall ignore the message. + +| | 24.008 | 29.002 | Notes | +|-----------------|------------------------------------------------------------------------------|-------------------------------------------|-------| +| Forward message | TMSI REALLOCATION COMMAND
Mobile identity
Location area identification | MAP_FORWARD_NEW_TMSI request
TMSI
- | | +| Backward result | TMSI REALLOCATION COMPLETE | MAP_FORWARD_NEW_TMSI response | | + +## 3.6 Retrieval of the IMEI from the MS + +The VLR may use the MAP\_OBTAIN\_IMEI service to request the MS to supply its IMEI, or may use the MAP\_CHECK\_IMEI service to request the MSC to check the MS's IMEI. For either MAP service the BSSAP signalling is the same. + +The mapping of information elements is as follows: + +| | 24.008 | 29.002 | Notes | +|-----------------|------------------------------------------------|---------------------------------------------------------------------|-------| +| Forward message | IDENTITY REQUEST
Identity type set to: IMEI | {(MAP_CHECK_IMEI request
or
MAP_OBTAIN_IMEI request | 1 | +| Backward result | IDENTITY RESPONSE
Mobile Identity (IMEI) | {(MAP_CHECK_IMEI response
or
MAP_OBTAIN_IMEI response
IMEI | 2 | + +NOTE 1: The MAP service request does not carry any parameters. The identity type is inferred from the service name. + +NOTE 2: If the MAP\_CHECK\_IMEI service was used, the MSC also returns the equipment status to the VLR in the MAP\_CHECK\_IMEI response, after a successful dialogue with the EIR using the IMEI received from the MS. + +The MSC shall terminate the MAP dialogue with the VLR using a MAP\_U\_ABORT if: + +- there is no RR connection with the MS when the MAP service request is received; +- there is no response from the MS. + +NOTE: The MSC can also obtain the IMEI from a phase 2 MS by including appropriate information in the BSSMAP Cipher Mode Command. + +## 3.7 Tracing subscriber activity + +The VLR may request the MSC and/or BSS to record data about the current transaction with an MS. + +| | 48.008 | 29.002 | Notes | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------| +| Forward message | MSC INVOKE TRACE
Trace type
TriggerId
Trace reference
TransactionId
Mobile identity (IMSI)
Mobile identity (IMEI)
OMCId | MAP TRACE SUBSCRIBER
ACTIVITY request
Trace type
Trace reference
IMSI
IMEI
OMCId | 1
1 | +| Backward result | none | none | | + +NOTE 1: The VLR may provide either an IMSI or IMEI, but not both. + +## 3.8 Location update + +| | 24.008 | 29.002 | Notes | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Forward message | MM (LOCATION UPDATING REQUEST)
Location area id
Mobile identity
Mobile station classmark 1
Mobile station classmark 2
Ciphering key seq number
Location update type | MAP_UPDATE LOCATION_request
-
IMSI
-
-
-
- | | +| Positive results | MM (LOCATION UPDATING ACCEPT)
Location area identity
Mobile identity
Follow on proceed | MAP_UPDATE LOCATION_response
-
-
- | | +| Negative results | MM (LOCATION UPDATING REJECT)
IMSI unknown in HLR
PLMN not allowed
LA not allowed
Roaming not allowed in this LA
No Suitable cells in location area
PLMN not allowed
No Suitable cells in location area
Illegal MS
Illegal ME
Network failure
Network failure
Network failure
Network failure
Network failure
Network failure | Unknown subscriber
Roaming not allowed:
PLMN not allowed
-
-
-
Operator determined barring
Additional roaming not allowed:
Supported RAT Types not allowed
-
-
System Failure
Unexpected data value
Data Missing
MAP U/P ABORT
MAP NOTICE
MAP_CLOSE | 1
3
2 | + +NOTE 1 The HLR shall also send this error if there is an error in the type of subscription (i.e. VLR requests service for a GPRS only subscriber). + +NOTE 2: Other reject causes than "no Suitable cells in location area" can be used (e.g. "Roaming not allowed in this location area"). + +NOTE 3 The VLR shall return the cause "LA not allowed" only if the HLR indicates that due to subscription to a "regionally restricted service" the MS is not allowed to operate in the location area. + +If the VLR finds out that the access is denied due to Administrative Restriction of Subscribers" Access based on subscription info received from HLR, VLR will send negative response to the MSC. The MSC will map the received cause using following mapping table: + +| 24.008 | | | Notes | +|------------------|------------------------------------|-------------------------------|-------| +| Negative results | MM (LOCATION UPDATING REJECT) | UPDATE LOCATION AREA Response | 1 | +| | PLMN not allowed | PLMN not allowed | | +| | Roaming not allowed in this LA | National Roaming not allowed | | +| | No Suitable cells in location area | RAT not allowed | | + +NOTE 1 The UPDATE LOCATION AREA response refers to the internal interface used between VLR and MSC (see 3GPP TS 23.012 [18]). + +# 4 Interworking in the MSC, Non-transparent cases + +## 4.1 General + +For interworking other than the mapping of information fields, see 3GPP TS 49.008 [14] [14]. + +## 4.2 Outgoing call set-up (MS originating call) + +Figure 3 shows those elements of a call set-up sequence which require interworking between BSSAP and MAP. BSSAP messages which do not require interworking with MAP are not shown. + +![Sequence diagram showing the part of outgoing call set-up sequence between MS, MSC, and VLR. The sequence starts with CM SERVICE REQUEST from MS to MSC, followed by MAP_PROCESS_ACCESS_REQUEST from MSC to VLR. The VLR may perform identification/authentication and then send MAP_SET_CIPHERING_MODE request to MSC. MSC responds with CM SERVICE ACCEPT, CIPHER MODE COMMAND, and CIPHER MODE COMPLETE. MSC then sends TMSI REALLOCATION COMMAND to MS. VLR sends MAP_FORWARD_NEW_TMSI request to MSC, which MSC forwards to MS as TMSI REALLOCATION COMPLETE. VLR also sends MAP_PROCESS_ACCESS_REQUEST response to MSC. If negative, MSC sends CM SERVICE REJECT to MS. If positive, MSC sends MAP_FORWARD_NEW_TMSI response to VLR. MSC then sends SETUP to MS. VLR sends MAP_SEND_INFO_FOR_OUTGOING_CALL request to MSC, which MSC forwards to MS as CALL PROCEEDING. Finally, VLR sends MAP_SEND_INFO_FOR_OUTGOING_CALL response to MSC, which MSC forwards to MS as RELEASE COMPLETE.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note right of MSC: Possibly identification procedure/ +authentication procedure + MS->>MSC: CM SERVICE REQUEST + MSC->>VLR: MAP_PROCESS_ACCESS_REQUEST request + Note right of VLR: Possibly identification procedure/ +authentication procedure + VLR->>MSC: MAP_SET_CIPHERING_MODE request + Note right of MSC: (Note 1) + MSC->>VLR: MAP_PROCESS_ACCESS_REQUEST response + Note right of VLR: positive result (Note 1) + MSC->>MS: CM SERVICE ACCEPT + Note right of MS: (Note 2) + MSC->>MS: CIPHER MODE COMMAND + Note right of MS: (Note 2) + MSC->>MS: CIPHER MODE COMPLETE + MSC->>MS: TMSI REALLOCATION COMMAND + VLR->>MSC: MAP_FORWARD_NEW_TMSI request + Note right of MSC: (Note 3) + MSC->>MS: TMSI REALLOCATION COMPLETE + VLR->>MSC: MAP_PROCESS_ACCESS_REQUEST response + Note right of MSC: negative result, MAP U/P ABORT, +MAP_NOTICE, MAP_CLOSE + MSC->>MS: CM SERVICE REJECT + Note right of MS: (Note 4) + MSC->>MS: SETUP (Note 5) + VLR->>MSC: MAP_SEND_INFO_FOR_OUTGOING_CALL request + MSC->>MS: CALL PROCEEDING + VLR->>MSC: MAP_SEND_INFO_FOR_OUTGOING_CALL response + Note right of MSC: response, MAP U/P ABORT, +MAP_NOTICE, MAP_CLOSE + MSC->>MS: RELEASE COMPLETE + Note right of MS: (Note 6) + +``` + +Sequence diagram showing the part of outgoing call set-up sequence between MS, MSC, and VLR. The sequence starts with CM SERVICE REQUEST from MS to MSC, followed by MAP\_PROCESS\_ACCESS\_REQUEST from MSC to VLR. The VLR may perform identification/authentication and then send MAP\_SET\_CIPHERING\_MODE request to MSC. MSC responds with CM SERVICE ACCEPT, CIPHER MODE COMMAND, and CIPHER MODE COMPLETE. MSC then sends TMSI REALLOCATION COMMAND to MS. VLR sends MAP\_FORWARD\_NEW\_TMSI request to MSC, which MSC forwards to MS as TMSI REALLOCATION COMPLETE. VLR also sends MAP\_PROCESS\_ACCESS\_REQUEST response to MSC. If negative, MSC sends CM SERVICE REJECT to MS. If positive, MSC sends MAP\_FORWARD\_NEW\_TMSI response to VLR. MSC then sends SETUP to MS. VLR sends MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL request to MSC, which MSC forwards to MS as CALL PROCEEDING. Finally, VLR sends MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL response to MSC, which MSC forwards to MS as RELEASE COMPLETE. + +**Figure 3: Part of outgoing call set-up sequence** + +NOTE 1: If the MSC received a MAP\_SET\_CIPHERING\_MODE request, it stores it until it receives the MAP\_PROCESS\_ACCESS\_REQUEST response. + +NOTE 2: CM SERVICE ACCEPT is sent only if the ciphering procedure is not invoked. + +NOTE 3: TMSI reallocation need not be sequenced with other messages, but should be sent after ciphering. + +NOTE 4: CM SERVICE REJECT is sent as a result of a user error parameter in the MAP\_PROCESS\_ACCESS\_REQUEST response, or termination of the MAP dialogue. + +NOTE 5: The SETUP message is sent after the MS has either received a CM SERVICE ACCEPT or sent a CIPHER MODE COMPLETE. + +NOTE 6: RELEASE COMPLETE is sent as a result of a user error parameter in the MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL response, or termination of the MAP dialogue. + +The procedure can be considered in two parts: the handling of the CM SERVICE REQUEST and the handling of the SETUP request. + +The procedure is initiated by the MS sending a CM SERVICE REQUEST message. The MSC will forward the service request to the VLR in the MAP\_PROCESS\_ACCESS\_REQUEST request. The VLR may then invoke other operations, e.g. authentication and identification. These operations are defined in clauses 3.4 and 3.5. + +If there is a positive outcome for the CM SERVICE REQUEST procedure, the VLR always sends a MAP\_PROCESS\_ACCESS\_REQUEST response. If the request is for a first MM-connection and ciphering is required, the MAP\_PROCESS\_ACCESS\_REQUEST response is preceded by a MAP\_SET\_CIPHERING\_MODE request. In this case the MSC sends a CIPHER MODE COMMAND towards the MS. The interworking for cipher mode setting is described in clause 4.4. If the request is for an additional MM-connection or for a first MM-connection where ciphering is not required, then the positive MAP\_PROCESS\_ACCESS\_REQUEST response causes the MSC to send a CM SERVICE ACCEPT message to the MS. After cipher mode setting has been completed or the CM SERVICE ACCEPT message has been returned, the MS will send the SETUP (or EMERGENCY SETUP) message and information retrieval takes place as shown. + +A negative outcome for the MAP\_PROCESS\_ACCESS\_REQUEST procedure can be signalled by a MAP\_PROCESS\_ACCESS\_REQUEST response containing a user error parameter, or by terminating the MAP dialogue between the MSC and the VLR. + +A positive outcome for the call setup procedure is indicated by a MAP\_COMPLETE\_CALL request from the VLR to the MSC, which causes the MSC to send a CALL PROCEEDING message towards the MS. + +A negative outcome for the call setup procedure can be signalled by a MAP\_SEND\_INFO\_FOR\_INCOMING\_CALL response or by terminating the dialogue between the MSC and the VLR. + +Information element mapping is required between the messages: + +- CM SERVICE REQUEST to MAP\_PROCESS\_ACCESS\_REQUEST request; +- SETUP to MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL request; +- MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL response, MAP\_U/P\_ABORT, MAP\_NOTICE or premature MAP\_CLOSE to RELEASE COMPLETE or CM SERVICE REJECT. + +The information contained in the MAP\_COMPLETE\_CALL request is not transmitted on the radio interface but is used in the MSC for connecting the call. + +The conversion of information elements is as follows: + +| | 48.008/24.008 | 29.002 | Notes | +|--------------------|-----------------------------------------------|----------------------------------------|-------| +| Forward | COMPLETE LAYER 3 INFO
(CM SERVICE REQUEST) | MAP PROCESS ACCESS
REQUEST request | | +| | CM Service type | CM Service type | 1 | +| | Ciphering key
sequence number | CKSN | | +| | Mobile identity | TMSI or IMSI or IMEI | | +| | Mobile station
Classmark 2 | - | | +| | Cell identifier | Current LA Id | 4 | +| | Chosen channel | - | | +| | - | Access Connection
Status | 3 | +| Positive
result | DTAP(CM SERVICE ACCEPT) | MAP PROCESS ACCESS
REQUEST response | 2 | +| Negative
result | DTAP(CM SERVICE REJECT) | MAP PROCESS ACCESS
REQUEST response | | +| | IMSI unknown in VLR | Unidentified
Subscriber | | +| [ | Requested service
option not
subscribed | ??????? | | +| | Illegal ME | Illegal equipment | ] | +| | Network failure | System failure | | +| | Network failure | MAP U/P ABORT | | +| | Network failure | MAP-NOTICE | | +| | Network failure | MAP-CLOSE | | +| | DTAP(AUTHENTICATION
REJECT) | MAP PROCESS ACCESS
REQUEST response | | +| | | Illegal subscriber | | + +NOTE 1: Indicates, in this case, a mobile originating call establishment or an emergency call establishment. + +NOTE 2: The CM SERVICE ACCEPT is sent when the ciphering procedure is not invoked. + +NOTE 3: Indicates whether or not an RR-connection exists and whether or not ciphering has been started. + +NOTE 4: The Current LA Id parameter is derived by the MSC from the Cell identifier information element. + +| | 24.008 | 29.002 | Notes | +|-----------------|----------------------------------|------------------------------------------|-------| +| Forward message | SETUP | MAP SEND INFO FOR OUTGOING_CALL_request | | +| | BC repeat indicator | - | | +| | Bearer capability 1 | - | 3 | +| | Bearer capability 2 | - | 3 | +| | Calling party subaddress | - | | +| | Called party BCD number | Called Number | | +| | Called party subaddress | - | | +| | LLC repeat indicator | - | | +| | Low layer compatibility I | - | | +| | Low layer compatibility II | - | | +| | HLC repeat indicator | - | | +| | High layer compatibility i | - | | +| | High layer compatibility ii | - | | +| | - | Bearer service | 3 | +| | - | Teleservice | 3 | +| | Facility | - | 1 | +| | - | CUG index | 4 | +| | - | Suppress pref CUG | 4 | +| | - | Suppress CUG OA | 4 | +| | User-user | - | | +| | SS version | - | | +| | CLIRO flag | - | | +| Positive result | | | 2 | +| Negative result | RELEASE COMPLETE | MAP SEND INFO FOR OUTGOING_CALL_response | | +| | 3GPP TS 24.010 | Call Barred | | +| | | Barring Service | | +| | | Active | | +| | Operator determined barring | Call Barred | | +| | | Operator Determined | | +| | | Barring | | +| | Network out of order | Data Missing | | +| | Network out of order | Unexpected Data Value | | +| | Network out of order | System Failure | | +| | Bearer capability not authorized | Bearer service not provisioned | | +| | Bearer capability not authorized | Teleservice not provisioned | | +| | [User not member of CUG] | CUG reject | | +| | Network out of order | MAP U/P ABORT | | +| | Network out of order | MAP NOTICE | | +| | Network out of order | MAP CLOSE | | + +NOTE 1: If the Facility IE contains CUG information, the CUG information is transferred to the VLR in the MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL service; any other information contained in a Facility IE is transferred to the VLR in a MAP Supplementary Services related service. + +NOTE 2: The call setup parameters retrieved from the VLR are not sent to the MS. The parameters are carried in the MAP\_COMPLETE\_CALL service. + +NOTE 3: The bearer capabilities can be used to derive the bearer/tele service. + +NOTE 4: CUG information is derived from the contents of the Facility IE. + +## 4.3 Incoming call set-up (MS terminating call) + +Figure 4 shows those elements of the procedure which require interworking between MAP and 3GPP TS 24.008 [4] procedures. + +![](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Sequence diagram illustrating the Incoming call set-up process between MS, MSC, and VLR. + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + + Note right of VLR: Info retrieval + VLR->>MSC: MAP_PAGE request or MAP_SEARCH_FOR_MS request + Note left of MSC: PAGE REQUEST (Note 1) + MSC->>MS: PAGE REQUEST + MS-->>MSC: PAGING RESPONSE + Note right of MSC: MAP_SEARCH_FOR_MS response (Note 2) + MSC->>VLR: MAP_PROCESS_ACCESS_REQUEST request + Note right of VLR: Possibly authentication procedure + VLR->>MSC: MAP_SET_CIPHERING_MODE request (Note 3) + Note left of MSC: CIPHER MODE COMMAND (Note 3) + MSC->>MS: CIPHER MODE COMPLETE + Note right of MSC: MAP_PROCESS_ACCESS_REQUEST response positive result (Note 4) + MSC->>VLR: MAP_FORWARD_NEW_TMSI request (Note 5) + Note left of MSC: TMSI REALLOCATION COMMAND + MSC->>MS: TMSI REALLOCATION COMPLETE + Note right of VLR: MAP_FORWARD_NEW_TMSI response + VLR->>MSC: MAP_COMPLETE_CALL request + Note left of MSC: SETUP + MSC->>MS: RELEASE COMPLETE (Note 6) + +``` + +**Figure 4: Incoming call set-up** + +NOTE 1: If an MM connection already exists, the PAGE REQUEST is not sent. If the call can be accepted, the MSC sends a MAP\_PROCESS\_ACCESS\_REQUEST request in response to the MAP\_PAGE request. If the call cannot be accepted the MSC sends a MAP\_PAGE response containing the error 'busy subscriber'. + +NOTE 2: Sent only if MAP\_SEARCH\_FOR\_MS was used. + +NOTE 3: Needed only if a ciphered MM-connection does not exist already. + +NOTE 4: If the MSC received a MAP\_SET\_CIPHERING\_MODE request, it stores it until it receives the MAP\_PROCESS\_ACCESS\_REQUEST response. + +NOTE 5: TMSI reallocation need not be sequenced with other messages, but should be sent after ciphering. + +NOTE 6: RELEASE COMPLETE is sent as a result of a user error parameter in the MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL response, or termination of the MAP dialogue. + +The paging procedure is controlled by the VLR. It may be followed by authentication (clause 3.4), ciphering (clause 4.4) and reallocation of TMSI (clause 3.6). The SETUP message is sent when the MAP\_COMPLETE\_CALL request is received. + +Normally there is no interworking between the MAP\_COMPLETE\_CALL request and the SETUP message. However, the MAP\_COMPLETE\_CALL request may contain a bearer service indication which will be used to establish the bearer capabilities at the MSC. The interworking between the MAP\_PAGE request or MAP\_SEARCH\_FOR\_MS request and the BSSMAP PAGING REQUEST message is as follows: + +| | 48.008/24.008 | 29.002 | Notes | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|--------| +| Forward message | PAGING REQUEST
IMSI
TMSI
Cell identifier
list | MAP_PAGE request or
MAP_SEARCH_FOR_MS request
IMSI
TMSI
Stored LA Id | 1 | +| Backward message | COMPLETE LAYER 3 INFO
(PAGING RESPONSE)
-
Ciphering key
sequence number
Mobile identity
Mobile station
classmark 2
Cell Identifier
-
Chosen channel | MAP_PROCESS_ACCESS
REQUEST request
CM service type
CKSN
TMSI or IMSI
-
Current LA Id
Access connection
status
- | 2
3 | + +NOTE 1: If TMSI is included, the TMSI is used as the mobile identity in the 3GPP TS 24.008 [4] PAGE REQUEST message, otherwise the IMSI is used as the mobile identity. + +NOTE 2: In this case the MAP CM service type is set to 'mobile terminating call'. + +NOTE 3: The Target LA Id parameter is derived by the MSC from the Cell identifier information element. + +## 4.4 Cipher mode setting + +The interworking is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|----------------------------------------------------------------------|-----------------------------------------------------------|-------| +| Forward | CIPHER MODE COMMAND
Cipher mode setting
Encryption information | MAP_SET_CIPHERING_MODE
request
Ciphering mode
Kc | 1 | +| Positive result | CIPHER MODE COMPLETE | None | | +| Negative result | CIPHER MODE REJECT | None | | + +NOTE 1: The key Kc is passed through the BSS to the BTS, but is not passed to the MS. + +## 4.5 Inter-MSC Handover + +The general principles of the handover procedures are given in 3GPP TS 23.009 [2]. 3GPP TS 29.010 gives the necessary information for interworking between the 3GPP TS 48.008 [12] handover protocol and the 3GPP TS 29.002 [9] MAP protocol. + +The following principle shall apply when new parameters need to be added for transfer on the E-interface: + +- 1- The parameters shall be added to be carried in the AN-APDU when they need to be forwarded to the target radio access network and the encapsulated protocol is the same as the protocol used at the interface between the target MSC and the target radio access network. +2. The parameters shall be added to be carried in a MAP message + - when they need to be forwarded to the target radio access network and the encapsulated protocol is different from the protocol used at the interface between the target MSC and the target radio access network; + - when they are required by the target MSC, but not to be forwarded to the target radio access network; or + - when they are required by the target MSC for subsequent procedures + +and they cannot be derived from the message encapsulated in the AN-APDU. + +### 4.5.1 Basic Inter-MSC Handover + +When a Mobile Station is handed over between two MSCs, the establishment of a connection between them (described in 3GPP TS 23.009 [2]) requires interworking between A-Interface and E-Interface. + +The signalling at initiation, execution, completion of the Basic Inter-MSC handover procedure is shown in figures 5 to 10 with both possible positive or negative outcomes. + +Additionally figures 5b and 5c show the possible interworking when trace related messages are transparently transferred on the E-Interface at Basic Inter-MSC Handover initiation. + +![Figure 5a: Signalling for Basic Inter-MSC Handover initiation (no trace related messages transferred). The diagram shows three entities: BSS-A, MSC-A, and MSC-B. BSS-A sends a HANDOVER REQUIRED message to MSC-A. MSC-A sends a MAP PREPARE HANDOVER request to MSC-B. MSC-B sends a HANDOVER REQUEST message to BSS-B. A box labeled 'Possible Alloc. of a handover no. in the VLR-B' is shown within MSC-B's processing.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant MSC-B + participant BSS-B + Note right of MSC-B: Possible Alloc. of a handover no. in the VLR-B + BSS-A-->>MSC-A: HANDOVER REQUIRED + MSC-A-->>MSC-B: MAP PREPARE HANDOVER request + MSC-B-->>BSS-B: HANDOVER REQUEST + +``` + +Figure 5a: Signalling for Basic Inter-MSC Handover initiation (no trace related messages transferred). The diagram shows three entities: BSS-A, MSC-A, and MSC-B. BSS-A sends a HANDOVER REQUIRED message to MSC-A. MSC-A sends a MAP PREPARE HANDOVER request to MSC-B. MSC-B sends a HANDOVER REQUEST message to BSS-B. A box labeled 'Possible Alloc. of a handover no. in the VLR-B' is shown within MSC-B's processing. + +**Figure 5a: Signalling for Basic Inter-MSC Handover initiation (no trace related messages transferred)** + +![Figure 5b: Signalling for Basic Inter-MSC Handover initiation (BSC invoke trace message transferred). The diagram shows three entities: BSS-A, MSC-A, and MSC-B. BSS-A sends a BSC INVOKE TRACE message to MSC-A, followed by a HANDOVER REQUIRED message. MSC-A sends a MAP PREPARE HANDOVER request (*) to MSC-B. MSC-B sends a HANDOVER REQUEST message to BSS-B, followed by a BSC INVOKE TRACE message (**). A box labeled 'Possible Alloc. of a handover no. in the VLR-B' is shown within MSC-B's processing.](303fadfb9def251d1575d6221199b158_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant MSC-B + participant BSS-B + Note right of MSC-B: Possible Alloc. of a handover no. in the VLR-B + BSS-A-->>MSC-A: BSC INVOKE TRACE + BSS-A-->>MSC-A: HANDOVER REQUIRED + MSC-A-->>MSC-B: MAP PREPARE HANDOVER request (*) + MSC-B-->>BSS-B: HANDOVER REQUEST + MSC-B-->>BSS-B: BSC INVOKE TRACE (**) + +``` + +Figure 5b: Signalling for Basic Inter-MSC Handover initiation (BSC invoke trace message transferred). The diagram shows three entities: BSS-A, MSC-A, and MSC-B. BSS-A sends a BSC INVOKE TRACE message to MSC-A, followed by a HANDOVER REQUIRED message. MSC-A sends a MAP PREPARE HANDOVER request (\*) to MSC-B. MSC-B sends a HANDOVER REQUEST message to BSS-B, followed by a BSC INVOKE TRACE message (\*\*). A box labeled 'Possible Alloc. of a handover no. in the VLR-B' is shown within MSC-B's processing. + +**Figure 5b: Signalling for Basic Inter-MSC Handover initiation (BSC invoke trace message transferred)** + +(\*): In that case, HANDOVER REQUEST and BSC INVOKE TRACE messages are included within the AN-APDU parameter. + +(\*\*): BSC INVOKE TRACE is forwarded to BSS-B if supported by MSC-B. + +![Sequence diagram for Basic Inter-MSC Handover initiation. Lifelines: BSS-A, MSC-A, MSC-B, BSS-B. BSS-A sends HANDOVER REQUIRED to MSC-A. MSC-A sends MAP PREPARE HANDOVER request (**) to MSC-B. MSC-B performs possible allocation of a handover number. MSC-B sends HANDOVER REQUEST and MSC INVOKE TRACE (***) to BSS-B.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant MSC-B + participant BSS-B + Note over MSC-A: (*) + BSS-A->>MSC-A: HANDOVER REQUIRED + MSC-A->>MSC-B: MAP PREPARE HANDOVER request (**) + Note over MSC-B: Possible Alloc. +of a handover +no. in the VLR-B + MSC-B->>BSS-B: HANDOVER REQUEST + MSC-B->>BSS-B: MSC INVOKE TRACE (***) + +``` + +Sequence diagram for Basic Inter-MSC Handover initiation. Lifelines: BSS-A, MSC-A, MSC-B, BSS-B. BSS-A sends HANDOVER REQUIRED to MSC-A. MSC-A sends MAP PREPARE HANDOVER request (\*\*) to MSC-B. MSC-B performs possible allocation of a handover number. MSC-B sends HANDOVER REQUEST and MSC INVOKE TRACE (\*\*\*) to BSS-B. + +**Figure 5c: Signalling for Basic Inter-MSC Handover initiation (MSC invoke trace message transferred)** + +(\*): Tracing invocation has been received from VLR. + +(\*\*): In that case, HANDOVER REQUEST and MSC INVOKE TRACE messages are included within the AN-APDU parameter. + +(\*\*\*): MSC INVOKE TRACE is forwarded to BSS-B if supported by MSC-B. + +Possible Positive outcomes: + +a) successful radio resources allocation and handover number allocation (if performed): + +![Sequence diagram for Positive outcome (a). Lifelines: BSS-A, MSC-A, MSC-B, BSS-B. MSC-B sends HANDOVER REQUEST to BSS-B. BSS-B sends HANDOVER REQUEST ACKNOWLEDGE to MSC-B. MSC-B sends MAP PREPARE HANDOVER response to MSC-A. MSC-A sends HANDOVER COMMAND to BSS-A.](ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant MSC-B + participant BSS-B + MSC-B->>BSS-B: HANDOVER REQUEST + BSS-B-->>MSC-B: HANDOVER REQUEST ACKNOWLEDGE + MSC-B-->>MSC-A: MAP PREPARE HANDOVER response + MSC-A->>BSS-A: HANDOVER COMMAND + +``` + +Sequence diagram for Positive outcome (a). Lifelines: BSS-A, MSC-A, MSC-B, BSS-B. MSC-B sends HANDOVER REQUEST to BSS-B. BSS-B sends HANDOVER REQUEST ACKNOWLEDGE to MSC-B. MSC-B sends MAP PREPARE HANDOVER response to MSC-A. MSC-A sends HANDOVER COMMAND to BSS-A. + +b) radio resources allocation queued and successful handover number allocation (if performed). Later successful radio resources allocation indication: + +![Sequence diagram for Positive outcome (b). Lifelines: BSS-A, MSC-A, MSC-B, BSS-B. MSC-B sends QUEUING INDICATION to MSC-A. MSC-A sends MAP PREPARE HANDOVER response to MSC-B. MSC-B sends HANDOVER REQUEST to BSS-B. BSS-B sends HANDOVER REQUEST ACKNOWLEDGE to MSC-B. MSC-B sends MAP PROCESS ACCESS SIGNALLING request to MSC-A. MSC-A sends HANDOVER COMMAND to BSS-A.](1c140ee5d1a87186977da94a96bfa700_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant MSC-B + participant BSS-B + MSC-B-->>MSC-A: QUEUING INDICATION + MSC-A->>MSC-B: MAP PREPARE HANDOVER + MSC-B-->>MSC-A: response + MSC-B->>BSS-B: HANDOVER REQUEST + BSS-B-->>MSC-B: ACKNOWLEDGE + MSC-B-->>MSC-A: MAP PROCESS ACCESS SIGNALLING request + MSC-A->>BSS-A: HANDOVER COMMAND + +``` + +Sequence diagram for Positive outcome (b). Lifelines: BSS-A, MSC-A, MSC-B, BSS-B. MSC-B sends QUEUING INDICATION to MSC-A. MSC-A sends MAP PREPARE HANDOVER response to MSC-B. MSC-B sends HANDOVER REQUEST to BSS-B. BSS-B sends HANDOVER REQUEST ACKNOWLEDGE to MSC-B. MSC-B sends MAP PROCESS ACCESS SIGNALLING request to MSC-A. MSC-A sends HANDOVER COMMAND to BSS-A. + +**Figure 6: Signalling for Basic Inter-MSC Handover execution (Positive outcomes)** + +Possible Negative outcomes: + +- c) user error detected, or handover number allocation unsuccessful (if performed), or component rejection or dialogue abortion performed by MSC-B: + +![Sequence diagram for scenario c: user error detected, or handover number allocation unsuccessful (if performed), or component rejection or dialogue abortion performed by MSC-B.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant MSC-B + participant BSS-B + Note right of MSC-A: MAP PREPARE HANDOVER response +negative result, MAP CLOSE + MSC-A->>MSC-B: MAP U/P-ABORT + Note left of MSC-A: HANDOVER REQUIRED + Note left of MSC-A: REJECT (Note 1) + +``` + +Sequence diagram for scenario c: user error detected, or handover number allocation unsuccessful (if performed), or component rejection or dialogue abortion performed by MSC-B. + +- d) radio resources allocation failure: + +![Sequence diagram for scenario d: radio resources allocation failure.](088921fa3f5a44c8551815122517eefd_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant MSC-B + participant BSS-B + Note right of MSC-A: MAP PREPARE HANDOVER + Note right of MSC-A: response + Note left of MSC-A: HANDOVER REQUIRED + Note left of MSC-A: REJECT (Note 1) + MSC-B->>BSS-B: HANDOVER FAILURE + +``` + +Sequence diagram for scenario d: radio resources allocation failure. + +- e) radio resources allocation queued and successful handover number allocation (if performed). Later unsuccessful radio resources allocation: + +![Sequence diagram for scenario e: radio resources allocation queued and successful handover number allocation (if performed). Later unsuccessful radio resources allocation.](356eb99ab9489bbd647223390a913903_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant MSC-B + participant BSS-B + Note right of MSC-A: MAP PREPARE HANDOVER + Note right of MSC-A: response + Note right of MSC-A: MAP PROCESS ACCESS + Note right of MSC-A: SIGNALLING request + Note left of MSC-A: HANDOVER REQUIRED + Note left of MSC-A: REJECT (Note 1) + MSC-B->>BSS-B: QUEUING INDICATION + MSC-B->>BSS-B: HANDOVER FAILURE + +``` + +Sequence diagram for scenario e: radio resources allocation queued and successful handover number allocation (if performed). Later unsuccessful radio resources allocation. + +- f) unsuccessful handover execution (Reversion to the old channel): + +![Sequence diagram for scenario f: unsuccessful handover execution (Reversion to the old channel).](db5ab5d386827a5d5f5fad0f45612b90_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant MSC-B + participant BSS-B + Note left of MSC-A: HANDOVER FAILURE + Note right of MSC-A: MAP U -ABORT + MSC-A->>MSC-B: CLEAR COMMAND + +``` + +Sequence diagram for scenario f: unsuccessful handover execution (Reversion to the old channel). + +**Figure 7: Signalling for Basic Inter-MSC Handover execution (Negative outcomes)** + +NOTE: Possible rejection of the handover because of the negative outcome of MAP or BSSMAP procedure. + +![Figure 8: Signalling for Basic Inter-MSC Handover completion. This sequence diagram shows four lifelines: BSS-A, MSC-A, MSC-B, and BSS-B. The sequence of messages is: 1. BSS-A sends a CLEAR sCOMMAND to MSC-A. 2. MSC-A sends a MAP SEND END SIGNAL request to MSC-B. 3. MSC-B sends a HANDOVER COMPLETE message to BSS-B.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant MSC-B + participant BSS-B + BSS-A->>MSC-A: CLEAR sCOMMAND + MSC-A->>MSC-B: MAP SEND END SIGNAL request + MSC-B->>BSS-B: HANDOVER COMPLETE + +``` + +Figure 8: Signalling for Basic Inter-MSC Handover completion. This sequence diagram shows four lifelines: BSS-A, MSC-A, MSC-B, and BSS-B. The sequence of messages is: 1. BSS-A sends a CLEAR sCOMMAND to MSC-A. 2. MSC-A sends a MAP SEND END SIGNAL request to MSC-B. 3. MSC-B sends a HANDOVER COMPLETE message to BSS-B. + +**Figure 8: Signalling for Basic Inter-MSC Handover completion** + +Positive outcome + +![Figure 9: Signalling for Basic Inter-MSC Handover completion (Positive outcome). This sequence diagram shows four lifelines: BSS-A, MSC-A, MSC-B, and BSS-B. The sequence of messages is: 1. MSC-A sends a MAP SEND END SIGNAL to MSC-B. 2. MSC-B sends a response to MSC-A. 3. MSC-B sends a CLEAR COMMAND (Note 1) to BSS-B.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant MSC-B + participant BSS-B + MSC-A->>MSC-B: MAP SEND END SIGNAL + MSC-B-->>MSC-A: response + MSC-B->>BSS-B: CLEAR COMMAND (Note 1) + +``` + +Figure 9: Signalling for Basic Inter-MSC Handover completion (Positive outcome). This sequence diagram shows four lifelines: BSS-A, MSC-A, MSC-B, and BSS-B. The sequence of messages is: 1. MSC-A sends a MAP SEND END SIGNAL to MSC-B. 2. MSC-B sends a response to MSC-A. 3. MSC-B sends a CLEAR COMMAND (Note 1) to BSS-B. + +**Figure 9: Signalling for Basic Inter-MSC Handover completion (Positive outcome)** + +Negative outcome + +![Figure 10: Signalling for Basic Inter-MSC Handover completion (Negative outcome). This sequence diagram shows four lifelines: BSS-A, MSC-A, MSC-B, and BSS-B. The sequence of messages is: 1. MSC-A sends a MAP U/P -ABORT to MSC-B. 2. MSC-B sends a CLEAR COMMAND to BSS-B.](9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant MSC-B + participant BSS-B + MSC-A->>MSC-B: MAP U/P -ABORT + MSC-B->>BSS-B: CLEAR COMMAND + +``` + +Figure 10: Signalling for Basic Inter-MSC Handover completion (Negative outcome). This sequence diagram shows four lifelines: BSS-A, MSC-A, MSC-B, and BSS-B. The sequence of messages is: 1. MSC-A sends a MAP U/P -ABORT to MSC-B. 2. MSC-B sends a CLEAR COMMAND to BSS-B. + +**Figure 10: Signalling for Basic Inter-MSC Handover completion (Negative outcome)** + +NOTE: From interworking between MAP and BSSMAP point of view. + +The handover procedure is normally triggered by BSS-A by sending a HANDOVER REQUIRED message on A-Interface to MSC-A. The invocation of the Basic Inter-MSC handover procedure is performed and controlled by MSC-A. The sending of the MAP Prepare-Handover request to MSC-B is triggered in MSC-A upon receipt of the HANDOVER REQUIRED message. For compatibility reason, the cell identity of the cell where the call is to be handed over in MSC-B area, provided in the HANDOVER REQUIRED message, is mapped into targetCellId MAP parameter and the HANDOVER REQUEST message is encapsulated in the AN-APDU MAP parameter of the Prepare-Handover MAP request. MSC-B can invoke another operation towards the VLR-B (allocation of the handover number described in 3GPP TS 29.002 [9]). + +Additionally, if tracing activity has been invoked, the trace related messages can be transferred on the E-Interface encapsulated in the AN-APDU MAP parameter of the Prepare-Handover Request. If transferred, one complete trace related message at a time shall be included in the AN-APDU MAP parameter after the HANDOVER REQUEST message. + +The interworking between Prepare Handover and HANDOVER REQUIRED is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Forward message | HANDOVER REQUIRED
BSSMAP information elements | MAP PREPARE HANDOVER request
-ho-NumberNotRequired
-targetCellId
-AN-APDU(
HANDOVER REQUEST,
BSC INVOKE TRACE
or MSC INVOKE TRACE) | 1
2
3 | +| Positive result | | MAP PREPARE HANDOVER response
-handover number
-AN-APDU(
QUEUING INDICATION
or HANDOVER REQUEST
ACKNOWLEDGE or
HANDOVER FAILURE) | 4 | +| Negative result | HANDOVER REQUIRED REJECT
equipment failure
equipment failure
equipment failure
equipment failure
equipment failure | MAP PREPARE HANDOVER
System Failure
No Handover Number
available
UnexpectedDataValue
Data Missing
MAP CLOSE
MAP U/P -ABORT | 5 | + +NOTE 1: The ho-NumberNotRequired parameter is included by MSC-A, when MSC-A decides not to use any circuit connection with MSC-B. No handover number shall be present in the positive result. Any negative response from MSC-B shall not be due to handover number allocation problem. + +NOTE 2: The process performed on the BSSMAP information elements received in the HANDOVER REQUIRED message is described in the GSM Recommendation 48.008. + +NOTE 3: The process performed on the BSSMAP information elements received in the MSC or BSC INVOKE TRACE message is described in clause 4.5.6.6. + +NOTE 4: The response to the Prepare-Handover request can include in its AN-APDU parameter, identifying the GSM-08.06 protocol, either a BSSMAP QUEUING INDICATION, or a BSSMAP HANDOVER REQUEST ACKNOWLEDGE or a BSSMAP HANDOVER FAILURE. + +In the first case, MSC-A shall wait for the radio resources allocation response from MSC-B, transmitted to MSC-A as described in clause 4.5.4. + +In the second case, the positive result triggers in MSC-A the sending on A-Interface of the HANDOVER COMMAND. + +In the third case, the positive result triggers in MSC-A one of the following: + +- another handover attempt is initiated by MSC-A; +- optionally the sending of the HANDOVER REQUIRED REJECT. + +(The possible sending of the HANDOVER REQUIRED REJECT message upon receipt of the HANDOVER FAILURE is out of the scope of 3GPP TS 29.010 and lies in 3GPP TS 48.008 [12]). + +NOTE 5: The possible sending of the HANDOVER REQUIRED REJECT message is described in 3GPP TS 48.008 [12]. + +The interworking between Send End Signal and HANDOVER COMPLETE in MSC-B is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|-----------------------------------------------------------------|----------------------------------------------------------------|-------| +| Forward message | HANDOVER COMPLETE | MAP SEND END SIGNAL request
-AN-APDU(
HANDOVER COMPLETE) | | +| Positive result | CLEAR COMMAND
-Call Control release | MAP SEND END SIGNAL response | 1 | +| Negative result | CLEAR COMMAND
-Call Control release
-Call Control release | MAP CLOSE
MAP U/P -ABORT | 2 | + +NOTE 1: The positive empty result triggers the clearing of the Radio Resources on the A-Interface and the release of the SCCP connection between MSC-B and BSS-B. If a circuit connection is used between MSC-A and MSC-B, the 'Call Control release' clearing cause shall only be given to BSS-B when MSC-B has received a clearing indication on its circuit connection with MSC-A. + +NOTE 2: The abortion of the dialogue or the rejection of the component triggers in MSC-B the clearing of its circuit connection with MSC-A, if any, of the Radio Resources on the A-Interface and the release of the SCCP connection between MSC-B and BSS-B. + +The interworking between Send End Signal and CLEAR COMMAND in MSC-A is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|-----------------------------------------------------------------|-------------------------------------------|-------| +| Forward message | MAP SEND END SIGNAL response
-AN-APDU(
HANDOVER COMPLETE) | CLEAR COMMAND
- Handover
Successful | | +| Positive result | | | | +| Negative result | | | | + +The interworking between HANDOVER FAILURE in case of reversion to old channel of the MS and User Abort in MSC-A is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|---------------------------------------------------|--------------|-------| +| Forward message | HANDOVER FAILURE
- Reversion to old
channel | MAP U -ABORT | | +| Positive result | | | | +| Negative result | | | | + +### 4.5.2 Subsequent Inter-MSC Handover back to MSC-A + +When a Mobile Station is being handed over back to MSC-A, the procedure (described in 3GPP TS 23.009 [2]) requires interworking between A-Interface and E-Interface. + +The signalling at initiation, execution and completion of the Subsequent Inter-MSC handover procedure is shown in figures 11 to 15. + +![Sequence diagram for Figure 11: Signalling for Subsequent Inter-MSC Handover back to MSC-A initiation. The diagram shows three entities: BSS-A, MSC-B, and MSC-A. BSS-A sends a 'HANDOVER REQUIRED' message to MSC-B. MSC-B sends a 'MAP PREPARE SUBSEQUENT' message to MSC-A, which is labeled as 'HANDOVER request'. MSC-A then sends a 'HANDOVER REQUEST' message to BSS-B.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant BSS-B + Note left of BSS-A: HANDOVER REQUIRED + BSS-A-->>MSC-B: HANDOVER REQUIRED + MSC-B-->>MSC-A: MAP PREPARE SUBSEQUENT + Note right of MSC-A: HANDOVER request + MSC-A-->>BSS-B: HANDOVER REQUEST + +``` + +Sequence diagram for Figure 11: Signalling for Subsequent Inter-MSC Handover back to MSC-A initiation. The diagram shows three entities: BSS-A, MSC-B, and MSC-A. BSS-A sends a 'HANDOVER REQUIRED' message to MSC-B. MSC-B sends a 'MAP PREPARE SUBSEQUENT' message to MSC-A, which is labeled as 'HANDOVER request'. MSC-A then sends a 'HANDOVER REQUEST' message to BSS-B. + +**Figure 11: Signalling for Subsequent Inter-MSC Handover back to MSC-A initiation** + +Possible Positive outcomes: + +a) successful radio resources allocation: + +![Sequence diagram for Figure 12, outcome a) successful radio resources allocation. The diagram shows four entities: BSS-A, MSC-B, MSC-A, and BSS-B. MSC-A sends a 'HANDOVER REQUEST' to BSS-B, which responds with 'ACKNOWLEDGE'. MSC-A then sends a 'MAP PREPARE SUBSEQUENT' message to MSC-B, which responds with 'HANDOVER response'. MSC-B sends a 'HANDOVER COMMAND' message to BSS-A.](fc0735d325f0ebd9214171975c68a888_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant BSS-B + MSC-A-->>BSS-B: HANDOVER REQUEST + BSS-B-->>MSC-A: ACKNOWLEDGE + MSC-A-->>MSC-B: MAP PREPARE SUBSEQUENT + MSC-B-->>MSC-A: HANDOVER response + MSC-B-->>BSS-A: HANDOVER COMMAND + +``` + +Sequence diagram for Figure 12, outcome a) successful radio resources allocation. The diagram shows four entities: BSS-A, MSC-B, MSC-A, and BSS-B. MSC-A sends a 'HANDOVER REQUEST' to BSS-B, which responds with 'ACKNOWLEDGE'. MSC-A then sends a 'MAP PREPARE SUBSEQUENT' message to MSC-B, which responds with 'HANDOVER response'. MSC-B sends a 'HANDOVER COMMAND' message to BSS-A. + +b) radio resources allocation queued. Later successful radio resources allocation indication: + +![Sequence diagram for Figure 12, outcome b) radio resources allocation queued. The diagram shows four entities: BSS-A, MSC-B, MSC-A, and BSS-B. MSC-A sends a 'QUEUING INDICATION' to BSS-B. MSC-A then sends a 'HANDOVER REQUEST' to BSS-B, which responds with 'ACKNOWLEDGE'. MSC-A sends a 'MAP FORWARD ACCESS' message to MSC-B, which responds with 'SIGNALLING request'. MSC-B sends a 'HANDOVER COMMAND' message to BSS-A.](5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant BSS-B + MSC-A-->>BSS-B: QUEUING INDICATION + MSC-A-->>BSS-B: HANDOVER REQUEST + BSS-B-->>MSC-A: ACKNOWLEDGE + MSC-A-->>MSC-B: MAP FORWARD ACCESS + MSC-B-->>MSC-A: SIGNALLING request + MSC-B-->>BSS-A: HANDOVER COMMAND + +``` + +Sequence diagram for Figure 12, outcome b) radio resources allocation queued. The diagram shows four entities: BSS-A, MSC-B, MSC-A, and BSS-B. MSC-A sends a 'QUEUING INDICATION' to BSS-B. MSC-A then sends a 'HANDOVER REQUEST' to BSS-B, which responds with 'ACKNOWLEDGE'. MSC-A sends a 'MAP FORWARD ACCESS' message to MSC-B, which responds with 'SIGNALLING request'. MSC-B sends a 'HANDOVER COMMAND' message to BSS-A. + +**Figure 12: Signalling for Subsequent Inter-MSC Handover back to MSC-A execution (Positive outcome)** + +Possible Negative outcomes: + +c) user error detected, or component rejection or dialogue abortion performed by MSC-A: + +![Sequence diagram for Figure 12, outcome c) user error detected, or component rejection or dialogue abortion performed by MSC-A. The diagram shows four entities: BSS-A, MSC-B, MSC-A, and BSS-B. MSC-A sends a 'MAP PREPARE SUBSEQUENT HANDOVER' message to MSC-B, which responds with 'response negative result'. MSC-A then sends a 'HANDOVER REQUIRED' message to BSS-A, which responds with 'REJECT (Note 1)'.](da6000b1371b5528262d4f9cb2f2707c_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant BSS-B + MSC-A-->>MSC-B: MAP PREPARE SUBSEQUENT HANDOVER + MSC-B-->>MSC-A: response negative result + MSC-A-->>BSS-A: HANDOVER REQUIRED + BSS-A-->>MSC-A: REJECT (Note 1) + +``` + +Sequence diagram for Figure 12, outcome c) user error detected, or component rejection or dialogue abortion performed by MSC-A. The diagram shows four entities: BSS-A, MSC-B, MSC-A, and BSS-B. MSC-A sends a 'MAP PREPARE SUBSEQUENT HANDOVER' message to MSC-B, which responds with 'response negative result'. MSC-A then sends a 'HANDOVER REQUIRED' message to BSS-A, which responds with 'REJECT (Note 1)'. + +d) component rejection or dialogue abortion performed by MSC-A: + +![Sequence diagram showing initial signaling for inter-MSC handover. Lifelines: BSS-A, MSC-B, MSC-A, BSS-B. MSC-A sends 'MAP CLOSE, MAP U/P ABORT' to MSC-B. MSC-B sends 'CLEAR COMMAND' to BSS-A.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant BSS-B + Note right of MSC-A: MAP CLOSE, MAP U/P ABORT + MSC-A-->MSC-B: MAP CLOSE, MAP U/P ABORT + Note left of MSC-B: CLEAR COMMAND + MSC-B-->BSS-A: CLEAR COMMAND + +``` + +Sequence diagram showing initial signaling for inter-MSC handover. Lifelines: BSS-A, MSC-B, MSC-A, BSS-B. MSC-A sends 'MAP CLOSE, MAP U/P ABORT' to MSC-B. MSC-B sends 'CLEAR COMMAND' to BSS-A. + +e) radio resources allocation failure: + +![Sequence diagram for radio resources allocation failure. Lifelines: BSS-A, MSC-B, MSC-A, BSS-B. BSS-A sends 'HANDOVER REQUIRED' to MSC-B. MSC-B sends 'MAP PREPARE SUBSEQUENT' to MSC-A. MSC-A returns 'HANDOVER response' to MSC-B. MSC-B sends 'REJECT (Note 1)' to BSS-A. MSC-A sends 'HANDOVER FAILURE' to BSS-B.](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant BSS-B + Note left of MSC-B: HANDOVER REQUIRED + BSS-A-->MSC-B: HANDOVER REQUIRED + Note right of MSC-B: MAP PREPARE SUBSEQUENT + MSC-B-->MSC-A: MAP PREPARE SUBSEQUENT + Note right of MSC-A: HANDOVER response + MSC-A-->MSC-B: HANDOVER response + Note left of MSC-B: REJECT (Note 1) + MSC-B-->BSS-A: REJECT (Note 1) + Note right of MSC-A: HANDOVER FAILURE + MSC-A-->BSS-B: HANDOVER FAILURE + +``` + +Sequence diagram for radio resources allocation failure. Lifelines: BSS-A, MSC-B, MSC-A, BSS-B. BSS-A sends 'HANDOVER REQUIRED' to MSC-B. MSC-B sends 'MAP PREPARE SUBSEQUENT' to MSC-A. MSC-A returns 'HANDOVER response' to MSC-B. MSC-B sends 'REJECT (Note 1)' to BSS-A. MSC-A sends 'HANDOVER FAILURE' to BSS-B. + +f) radio resources allocation queued. Later unsuccessful radio resources allocation: + +![Sequence diagram for radio resources allocation queued. Lifelines: BSS-A, MSC-B, MSC-A, BSS-B. BSS-A sends 'HANDOVER REQUIRED' to MSC-B. MSC-B sends 'MAP PREPARE SUBSEQUENT' to MSC-A. MSC-A returns 'HANDOVER response' to MSC-B. MSC-B sends 'MAP FORWARD ACCESS' to MSC-A. MSC-A returns 'SIGNALLING request' to MSC-B. MSC-B sends 'REJECT (Note 1)' to BSS-A. MSC-A sends 'QUEUING INDICATION' to BSS-B. Later, MSC-A sends 'HANDOVER FAILURE' to BSS-B.](94fd137860c16c8dfd75512f10161fe8_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant BSS-B + Note left of MSC-B: HANDOVER REQUIRED + BSS-A-->MSC-B: HANDOVER REQUIRED + Note right of MSC-B: MAP PREPARE SUBSEQUENT + MSC-B-->MSC-A: MAP PREPARE SUBSEQUENT + Note right of MSC-A: HANDOVER response + MSC-A-->MSC-B: HANDOVER response + Note right of MSC-B: MAP FORWARD ACCESS + MSC-B-->MSC-A: MAP FORWARD ACCESS + Note right of MSC-A: SIGNALLING request + MSC-A-->MSC-B: SIGNALLING request + Note left of MSC-B: REJECT (Note 1) + MSC-B-->BSS-A: REJECT (Note 1) + Note right of MSC-A: QUEUING INDICATION + MSC-A-->BSS-B: QUEUING INDICATION + Note right of MSC-A: HANDOVER FAILURE + MSC-A-->BSS-B: HANDOVER FAILURE + +``` + +Sequence diagram for radio resources allocation queued. Lifelines: BSS-A, MSC-B, MSC-A, BSS-B. BSS-A sends 'HANDOVER REQUIRED' to MSC-B. MSC-B sends 'MAP PREPARE SUBSEQUENT' to MSC-A. MSC-A returns 'HANDOVER response' to MSC-B. MSC-B sends 'MAP FORWARD ACCESS' to MSC-A. MSC-A returns 'SIGNALLING request' to MSC-B. MSC-B sends 'REJECT (Note 1)' to BSS-A. MSC-A sends 'QUEUING INDICATION' to BSS-B. Later, MSC-A sends 'HANDOVER FAILURE' to BSS-B. + +**Figure 13: Signalling for Subsequent Inter-MSC Handover back to MSC-A execution (Negative outcome)** + +NOTE 1: Possible rejection of the handover because of the negative outcome of MAP or BSSMAP procedure. + +![Sequence diagram for successful completion of subsequent inter-MSC handover back to MSC-A. Lifelines: BSS-B, MSC-A, MSC-B, BSS-A. BSS-B sends 'HANDOVER COMPLETE' to MSC-A. MSC-A sends 'MAP SEND END SIGNAL' to MSC-B. MSC-B returns 'response' to MSC-A. MSC-B sends 'CLEAR COMMAND' to BSS-A.](80ec3bf791fd8eb41f73a420c2122529_img.jpg) + +``` + +sequenceDiagram + participant BSS-B + participant MSC-A + participant MSC-B + participant BSS-A + Note left of MSC-A: HANDOVER COMPLETE + BSS-B-->MSC-A: HANDOVER COMPLETE + Note right of MSC-A: MAP SEND END SIGNAL + MSC-A-->MSC-B: MAP SEND END SIGNAL + Note right of MSC-B: response + MSC-B-->MSC-A: response + Note right of MSC-B: CLEAR COMMAND + MSC-B-->BSS-A: CLEAR COMMAND + +``` + +Sequence diagram for successful completion of subsequent inter-MSC handover back to MSC-A. Lifelines: BSS-B, MSC-A, MSC-B, BSS-A. BSS-B sends 'HANDOVER COMPLETE' to MSC-A. MSC-A sends 'MAP SEND END SIGNAL' to MSC-B. MSC-B returns 'response' to MSC-A. MSC-B sends 'CLEAR COMMAND' to BSS-A. + +**Figure 14: Signalling for Subsequent Inter-MSC Handover back to MSC-A completion (Successful completion of the procedure)** + +NOTE: Positive outcome case shown in figure 9. + +![Sequence diagram for unsuccessful completion of subsequent inter-MSC handover back to MSC-A. Lifelines: BSS-B, MSC-A, MSC-B, BSS-A. BSS-B sends 'HANDOVER COMPLETE' to MSC-A. MSC-A sends 'MAP SEND END SIGNAL' to MSC-B. MSC-B returns 'response' to MSC-A. MSC-A sends 'MAP U/P -ABORT' to MSC-B. MSC-B sends 'CLEAR COMMAND (Note 1)' to BSS-A.](0977b81510f7649846289ee785d20e74_img.jpg) + +``` + +sequenceDiagram + participant BSS-B + participant MSC-A + participant MSC-B + participant BSS-A + Note left of MSC-A: HANDOVER COMPLETE + BSS-B-->MSC-A: HANDOVER COMPLETE + Note right of MSC-A: MAP SEND END SIGNAL + MSC-A-->MSC-B: MAP SEND END SIGNAL + Note right of MSC-B: response + MSC-B-->MSC-A: response + Note right of MSC-A: MAP U/P -ABORT + MSC-A-->MSC-B: MAP U/P -ABORT + Note right of MSC-B: CLEAR COMMAND (Note 1) + MSC-B-->BSS-A: CLEAR COMMAND (Note 1) + +``` + +Sequence diagram for unsuccessful completion of subsequent inter-MSC handover back to MSC-A. Lifelines: BSS-B, MSC-A, MSC-B, BSS-A. BSS-B sends 'HANDOVER COMPLETE' to MSC-A. MSC-A sends 'MAP SEND END SIGNAL' to MSC-B. MSC-B returns 'response' to MSC-A. MSC-A sends 'MAP U/P -ABORT' to MSC-B. MSC-B sends 'CLEAR COMMAND (Note 1)' to BSS-A. + +**Figure 15: Signalling for Subsequent Inter-MSC Handover back to MSC-A completion (Unsuccessful completion of the procedure)** + +NOTE 1: Abnormal end of the procedure which triggers the clearing of all resources in MSC-B. + +The interworking between Prepare Subsequent Handover and HANDOVER REQUIRED is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | HANDOVER REQUIRED MAP PREPARE

BSSMAP information elements | SUBSEQUENT HANDOVER request

-target MSC number
-targetCellId
-AN-APDU(
HANDOVER REQUEST) | 1 | +| Positive result | HANDOVER REQUIRED MAP PREPARE | SUBSEQUENT HANDOVER response
-AN-APDU(
QUEUING INDICATION
or HANDOVER REQUEST
ACKNOWLEDGE or
HANDOVER FAILURE) | 2 | +| Negative result | HANDOVER REQUIRED REJECT

equipment failure
equipment failure

equipment failure
equipment failure

CLEAR COMMAND

equipment failure
equipment failure | MAP PREPARE SUBSEQUENT HANDOVER response

Unknown MSC
Subsequent Handover Failure
UnexpectedDataValue
Data Missing





MAP CLOSE
MAP U/P -ABORT | 3 | + +NOTE 1: The processing performed on the BSSMAP information elements received in the HANDOVER REQUIRED message is out of the scope of the present document. The target MSC number is provided to MSC-A by MSC-B based on the information received from BSS-B. + +NOTE 2: The response to the Prepare-Subsequent-Handover request can include in its AN-APDU parameter, identifying the GSM-0806 protocol, either a BSSMAP QUEUING INDICATION, or a BSSMAP HANDOVER REQUEST ACKNOWLEDGE or a BSSMAP HANDOVER FAILURE. + +In the first case, MSC-B shall wait for the radio resources allocation response from MSC-A, transmitted to MSC-B as described in clause 4.5.4. + +In the second case, the positive result triggers in MSC-B the sending on A-Interface of the HANDOVER COMMAND. + +In the third case, the positive result triggers in MSC-B one of the following: + +- another handover attempt is initiated by MSC-B; +- optionally the sending of the HANDOVER REQUIRED REJECT. + +(The possible sending of the HANDOVER REQUIRED REJECT message upon receipt of the HANDOVER FAILURE is out of the scope of 3GPP TS 29.010 and lies in 3GPP TS 48.008 [12]). + +NOTE 3: The possible sending of the HANDOVER REQUIRED REJECT message is described in 3GPP TS 48.008 [12]. + +The interworking between Send End Signal Result and HANDOVER COMPLETE in MSC-A is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|-------------------|------------------------------|-------| +| Forward message | HANDOVER COMPLETE | MAP SEND END SIGNAL response | | +| Positive result | | | | +| Negative result | | MAP U/P -ABORT | 1 | + +NOTE 1: The abortion of the dialogue ends the handover procedure with MSC-B. + +### 4.5.3 Subsequent Inter-MSC Handover to third MSC + +When a Mobile Station is being handed over to a third MSC, the procedure (described in 3GPP TS 23.009 [2]) does require one specific interworking case in MSC-A (figure 20) between E-Interface from MSC-B and E-Interface from MSC-B' other than the combination of the ones described in the clause 4.5.1 and 4.5.2. + +![Figure 16: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') initiation. The diagram shows a sequence of messages between BSS-A, MSC-B, MSC-A, and MSC-B'. BSS-A sends a HANDOVER REQUIRED to MSC-B. MSC-B sends a MAP PREPARE SUSEQUENT HANDOVER request to MSC-A. MSC-A sends a MAP PREPARE HANDOVER request to MSC-B'. MSC-B' contains a box for 'Possib. Alloc. of ho. number VLR-B' and 'BSS-B'' and sends a HANDOVER REQUEST to BSS-B'.](8658cfab6a458b4a80ab2e384c61ff89_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant MSC-B' + Note right of MSC-B': Possib. Alloc. of ho. number VLR-B + Note right of MSC-B': BSS-B' + BSS-A->>MSC-B: HANDOVER REQUIRED + MSC-B->>MSC-A: MAP PREPARE SUSEQUENT HANDOVER request + MSC-A->>MSC-B': MAP PREPARE HANDOVER request + MSC-B'-->>BSS-B': HANDOVER REQUEST + +``` + +Figure 16: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') initiation. The diagram shows a sequence of messages between BSS-A, MSC-B, MSC-A, and MSC-B'. BSS-A sends a HANDOVER REQUIRED to MSC-B. MSC-B sends a MAP PREPARE SUSEQUENT HANDOVER request to MSC-A. MSC-A sends a MAP PREPARE HANDOVER request to MSC-B'. MSC-B' contains a box for 'Possib. Alloc. of ho. number VLR-B' and 'BSS-B'' and sends a HANDOVER REQUEST to BSS-B'. + +Figure 16: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') initiation + +Possible Positive outcomes: + +a) successful radio resources allocation: + +![Figure 17: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') successful radio resources allocation. The diagram shows a sequence of messages between BSS-A, MSC-B, MSC-A, and MSC-B'. MSC-A sends a MAP PREPARE HANDOVER response to MSC-B. MSC-B sends a MAP PREPARE SUSEQUENT HANDOVER response to BSS-A. BSS-A sends a HANDOVER COMMAND to the mobile station. MSC-B' sends a HANDOVER REQUEST ACKNOWLEDGE to MSC-A.](b54ce9bffd341cd643e196d5f4538829_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant MSC-B' + Note right of MSC-B': BSS-B' + MSC-A->>MSC-B: MAP PREPARE HANDOVER response + MSC-B->>BSS-A: MAP PREPARE SUSEQUENT HANDOVER response + BSS-A->>MS: HANDOVER COMMAND + MSC-B'->>MSC-A: HANDOVER REQUEST ACKNOWLEDGE + +``` + +Figure 17: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') successful radio resources allocation. The diagram shows a sequence of messages between BSS-A, MSC-B, MSC-A, and MSC-B'. MSC-A sends a MAP PREPARE HANDOVER response to MSC-B. MSC-B sends a MAP PREPARE SUSEQUENT HANDOVER response to BSS-A. BSS-A sends a HANDOVER COMMAND to the mobile station. MSC-B' sends a HANDOVER REQUEST ACKNOWLEDGE to MSC-A. + +b) radio resources allocation queued and successful handover number allocation, if performed. Later successful radio resources allocation indication: + +![Sequence diagram for Figure 17: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution (Positive outcome).](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + + Note right of MSC-B': QUEUING INDICAT. + MSC-A->>MSC-B': MAP PREPARE HANDOVER + MSC-B'-->>MSC-A: response + MSC-B'->>BSS-B': HANDOVER REQUEST + BSS-B'-->>MSC-B': ACKNOWLEDGE + MSC-A->>MSC-B: MAP PROCESS ACCESS + MSC-B-->>MSC-A: SIGNALLING request + MSC-B->>BSS-A: MAP FORWARD ACCESS + BSS-A-->>MSC-B: SIGNALLING request + MSC-B->>BSS-A: HANDOVER COMMAND + +``` + +Sequence diagram for Figure 17: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution (Positive outcome). + +**Figure 17: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution (Positive outcome)** + +Possible Negative outcomes: + +c) user error detected, or component rejection or dialogue abortion performed by MSC-B': + +![Sequence diagram for Possible Negative outcome c): user error detected, or component rejection or dialogue abortion performed by MSC-B'.](875c6f4f441fdd3ca7e1908fd1582983_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + + MSC-A->>MSC-B': MAP PREPARE HANDOVER + MSC-B'-->>MSC-A: response negative result + MSC-A->>MSC-B: MAP CLOSE + MSC-B'-->>MSC-A: MAP U/P -ABORT + MSC-A->>MSC-B: MAP PREPARE SUBSEQUENT + MSC-B-->>MSC-A: HANDOVER response negative result + MSC-B->>BSS-A: HANDOVER REQUIRED REJECT (Note 1) + +``` + +Sequence diagram for Possible Negative outcome c): user error detected, or component rejection or dialogue abortion performed by MSC-B'. + +d) radio resources allocation failure: + +![Sequence diagram showing a negative outcome for subsequent inter-MSC handover.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + + MSC-B'-->>BSS-B': HANDOVER + BSS-B'-->>MSC-B': FAILURE + MSC-A->>MSC-B': MAP PREPARE HANDOVER + MSC-B'-->>MSC-A: response + MSC-B->>MSC-A: MAP PREPARE SUBSEQUENT + MSC-A-->>MSC-B: HANDOVER response + MSC-B-->>BSS-A: HANDOVER + Note over BSS-A: REQUIRED +REJECT +(Note 1) + +``` + +Sequence diagram showing a negative outcome for subsequent inter-MSC handover. + +e) radio resources allocation queued and successful handover number allocation (if performed). Later unsuccessful radio resources allocation: + +![Sequence diagram for Figure 18: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution (Negative outcome).](fcbc3c31776721edc98ceb1944ec438f_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + + MSC-B'-->>BSS-B': QUEUING + BSS-B'-->>MSC-B': INDICAT. + MSC-A->>MSC-B': MAP PREPARE HANDOVER + MSC-B'-->>MSC-A: response + MSC-B->>MSC-A: MAP PREPARE SUBSEQUENT + MSC-A-->>MSC-B: HANDOVER response + BSS-B'-->>MSC-B': HANDOVER + MSC-B'-->>BSS-B': FAILURE + MSC-A->>MSC-B': MAP PROCESS ACCESS + MSC-B'-->>MSC-A: SIGNALLING request + MSC-B->>MSC-A: MAP FORWARD ACCESS + MSC-A-->>MSC-B: SIGNALLING request + MSC-B-->>BSS-A: HANDOVER + Note over BSS-A: REQUIRED +REJECT +(Note 1) + +``` + +Sequence diagram for Figure 18: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution (Negative outcome). + +**Figure 18: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution (Negative outcome)** + +NOTE 1: Possible rejection of the handover because of the negative outcome of MAP or BSSMAP procedure. + +Positive outcome: + +![Sequence diagram for successful inter- MSC handover completion. Lifelines: BSS-A, MSC-B, MSC-A, MSC-B', BSS-B'. The sequence starts with BSS-A sending a CLEAR COMMAND to MSC-B. MSC-B sends a MAP SEND END SIGNAL response to MSC-A. MSC-A sends a MAP SEND END SIGNAL to MSC-B'. MSC-B' sends a HANDOVER COMPLETE message to BSS-B'.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + Note left of BSS-A: CLEAR COMMAND + BSS-A->>MSC-B: CLEAR COMMAND + MSC-B-->>MSC-A: MAP SEND END SIGNAL response + MSC-A-->>MSC-B': MAP SEND END SIGNAL + MSC-B'-->>BSS-B': HANDOVER COMPLETE + +``` + +Sequence diagram for successful inter- MSC handover completion. Lifelines: BSS-A, MSC-B, MSC-A, MSC-B', BSS-B'. The sequence starts with BSS-A sending a CLEAR COMMAND to MSC-B. MSC-B sends a MAP SEND END SIGNAL response to MSC-A. MSC-A sends a MAP SEND END SIGNAL to MSC-B'. MSC-B' sends a HANDOVER COMPLETE message to BSS-B'. + +**Figure 19: Signalling for Subsequent Inter- MSC Handover to third MSC (MSC-B') completion (Successful completion of the procedure)** + +Negative outcome: + +![Sequence diagram for unsuccessful inter- MSC handover completion. Lifelines: BSS-A, MSC-B, MSC-A, MSC-B', BSS-B'. The sequence starts with BSS-A sending a HANDOVER FAILURE message to MSC-B. MSC-B sends a MAP PROCESS ACCESS SIGNALLING request (Note 1) to MSC-A. MSC-A sends a MAP U -ABORT message to MSC-B'. MSC-B' sends a CLEAR COMMAND message to BSS-B'.](fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + Note left of BSS-A: HANDOVER FAILURE + BSS-A-->>MSC-B: HANDOVER FAILURE + MSC-B-->>MSC-A: MAP PROCESS ACCESS SIGNALLING request (Note 1) + MSC-A-->>MSC-B': MAP U -ABORT + MSC-B'-->>BSS-B': CLEAR COMMAND + +``` + +Sequence diagram for unsuccessful inter- MSC handover completion. Lifelines: BSS-A, MSC-B, MSC-A, MSC-B', BSS-B'. The sequence starts with BSS-A sending a HANDOVER FAILURE message to MSC-B. MSC-B sends a MAP PROCESS ACCESS SIGNALLING request (Note 1) to MSC-A. MSC-A sends a MAP U -ABORT message to MSC-B'. MSC-B' sends a CLEAR COMMAND message to BSS-B'. + +**Figure 20: Signalling for Subsequent Inter- MSC Handover to third MSC (MSC-B') completion (Unsuccessful completion of the procedure)** + +NOTE 1: Specific interworking case detailed below. + +The specific interworking case in MSC-A compared to the clauses 4.5.1 and 4.5.2 occurs between HANDOVER FAILURE encapsulated in a Process Access Signalling from MSC-B and the abortion of the dialogue with MSC-B' in the case of a reversion to old channel of the MS: + +| | 29.002 | 29.002 | Notes | +|-----------------|----------------------------------------------------------------|----------------|-------| +| Forward message | MAP PROCESS-SIGNALLING request
-AN-APDU ( HANDOVER FAILURE) | MAP U -ABORT | 1 | +| Positive result | | | | +| Negative result | | MAP U/P -ABORT | 2 | + +NOTE 1: The abortion of the dialogue triggers in MSC-B' the clearing of the circuit connection with MSC-A, if any, and of the Resources between MSC-B' and BSS-B'. The abortion of the dialogue ends the handover procedure with MSC-B'. + +NOTE 2: The abortion of the dialogue ends the handover procedure with MSC-B. + +### 4.5.4 BSSAP Messages transfer on E-Interface + +The following mapping applies to the encapsulation performed in MSC-A. + +| | 24.008/48.008 | 29.002 | Notes | +|-----------------|----------------|--------------------------------------------------------------------|-------| +| Forward message | BSSAP messages | MAP FORWARD ACCESS SIGNALLING request
-AN-APDU (BSSAP messages) | 1 | +| Positive result | | | 2 | +| Negative result | | MAP CLOSE
MAP U/P -ABORT | | + +NOTE 1: Complete BSSAP messages to be sent on MSC-B - BSS-B interface (BSSMAP or DTAP messages) are embedded into the AN-APDU parameter (see clause 6 of 3GPP TS 49.008 [14] [14] for the description of the set of BSSMAP messages). + +NOTE 2: The Return Result does not apply. If MSC-B returns a message, this message will arrive in an Invoke: Process Access Signalling. + +The following mapping applies to the encapsulation performed in MSC-B. + +| | 24.008/48.008 | 29.002 | Notes | +|-----------------|------------------------------------|--------------------------------------------------------------------|-------| +| Forward message | BSSAP messages | MAP PROCESS ACCESS SIGNALLING request
-AN-APDU (BSSAP messages) | 1 | +| Positive result | | | 2 | +| Negative result | CLEAR COMMAND
equipment failure | MAP CLOSE
MAP U/P -ABORT | 3 | + +NOTE 1: Complete BSSAP messages to be sent to MSC-A (BSSMAP or DTAP messages) are embedded into the AN-APDU parameter (see 3GPP TS 49.008 [14] for the description of the set of BSSMAP messages). + +NOTE 2: The Return Result does not apply. If MSC-A returns a message, this message will arrive in an Invoke: Forward Access Signalling. + +NOTE 3: The abortion of the dialogue triggers the clearing of the circuit connection with MSC-A, if any, of the Radio Resources on the A-Interface and the release of the SCCP connection between MSC-B and BSS-B. The clearing of the Radio Resources (the clearing indication received from BSS-B is transmitted to MSC-A) or the loss of the SCCP connection between MSC-B and BSS-B, triggers in MSC-B the abortion of the dialogue on the E-Interface and the clearing of the circuit connection with MSC-A, if any. + +### 4.5.5 Processing in MSC-B, and information transfer on E-interface + +The following parameters require processing (e.g. to store the parameter, to internally generate the parameter) in MSC-B. The relevant BSSMAP procedures are mentioned to ease the comprehension, their detailed description is the scope of 3GPP TS 48.008 [12]. Each BSSMAP message listed in 3GPP TS 49.008 [14] being transferred on E-interface shall use the mechanisms given in clause 4.5.4 and is described in 3GPP TS 48.008 [12]. + +For intra-MSC-B handover/relocation and security interworking, after inter-MSC handover from GSM to GSM, the 3G\_MSC-B needs additional information to be able to perform security mode and integrity protection procedures. These RANAP informations are transferred between MSC-A and 3G-MSC-B in MAP messages, defined in 3GPP TS 29.002 [9]. + +For subsequent handover/relocation, after inter-MSC handover from GSM to GSM, the 3G\_MSC-B needs additional information to be able to perform service handover procedures. The relevant information is transferred between MSC-A and 3G-MSC-B in MAP messages, defined in 3GPP TS 29.002 [9]. + +For subsequent handover/relocation, after inter-MSC handover from GSM to GSM, the 3G\_MSC-B needs additional information to be able to forward access rights information in the context of Shared Network to the RAN. The relevant information is transferred between MSC-A and 3G-MSC-B in MAP messages, defined in 3GPP TS 29.002 [9]. + +For intra-MSC-B handover after inter MSC handover, MSC-B needs additional information to be able to perform regional subscription checks and CSG subscription checks. The relevant information is transferred between MSC-A and MSC-B in MAP messages, defined in 3GPP TS 29.002 [9]. + +#### 4.5.5.1 Encryption Information + +A sequence of possible encryption algorithms can be sent to a BSS in Cipher Mode Command or Handover Request. The BSS chooses one of the listed algorithms and reports this back to the MSC in Cipher Mode Complete or Handover Request Acknowledge respectively. + +MSC-B shall remove algorithms not allowed by MSC-B from the list of algorithms received from MSC-A before forwarding it to the BSS. The modified list of algorithms, the ciphering key and the chosen algorithm shall be stored by MSC-B, and the chosen value sent to MSC-A. + +Transfer of Information: + +If ciphering has not been performed before Inter-MSC Handover, this will be controlled by MSC-A after the completion of Inter-MSC Handover. + +Ciphering control towards MSC-B: + +If Ciphering has been performed before Inter-MSC Handover: + +- in the Handover Request BSSMAP message (information included). + +The Handover Request Acknowledge should in this case contain the indication of the chosen algorithm. + +If Ciphering has NOT been performed before Inter-MSC Handover: + +- in the Cipher Mode Command procedure between MSC-A and MSC-B. + +If the encryption algorithm is changed at an intra-BSS handover in BSS-B this must be reported to MSC-A in: + +- the BSSMAP Handover Performed procedure. + +If the encryption algorithm is changed at an intra-MSC handover in MSC-B this must be reported to MSC-A in: + +- the BSSMAP Handover Performed procedure which shall be initiated by MSC-B on reception from BSS-B of the Handover Complete message (the information being previously received in the Handover Request Acknowledge message). + +Note also that the chosen encryption value may be contained in the BSSMAP Assignment Complete message. This may happen if the encryption value changes e.g. at a second assignment during a call (e.g. from TCH to SDCCH). + +#### 4.5.5.2 Channel Type + +Assignment Request and Handover Request (BSSMAP) may give the BSS a choice, in the same way as the Encryption Algorithm above. Depending on the Channel Type Info, the chosen channel may have impact on subsequent handovers, internal in MSC-B and inter-MSC controlled by MSC-A. Some values in channel Type Info indicate that if a particular channel once has been chosen, the same type must be used for the rest of the call. + +The Channel Type, and the characteristics of the chosen channel shall be stored by MSC-B, and the Chosen Channel and/or Speech Version information elements transferred to MSC-A. + +Transfer of Information: + +Independently of the type of resource (Signalling only (e.g. SDCCH) or TCH) assigned to the MS, the Channel Type Information is transferred to MSC-B in: + +- the Handover Request BSSMAP message, and the Chosen Channel and/or Speech Version should be reported back to MSC-A in the Handover Request Acknowledge. + +If a new type of resource is to be assigned after Inter-MSC Handover, this can be made with: + +- the BSSMAP Assignment procedure between MSC-A and MSC-B (Chosen Channel and/or Speech Version in Assignment Complete). + +If the Channel Type (the chosen channel and/or chosen speech version) is changed at an intra-BSS handover in BSS-B this must be reported to MSC-A in: + +- the BSSMAP Handover Performed procedure. + +If the Channel Type (the chosen channel or chosen speech version) is changed at an intra-MSC handover in MSC-B this must be reported to MSC-A in: + +- the BSSMAP Handover Performed procedure which shall be initiated by MSC-B on reception from BSS-B of the Handover Complete message (the information being previously received in the Handover Request Acknowledge message). + +#### 4.5.5.3 Classmark + +This information shall be stored by MSC-B and might be received either from MSC-A, or from the MS when the MS initiates a Classmark Update. + +Transfer of Information due to Classmark received from MSC-A: + +This information shall be stored by MSC-B and is received: + +- in the Handover Request BSSMAP message. + +If a new type of resource is to be assigned after Inter-MSC Handover, Classmark Information MAY be included: + +- in the BSSMAP Assignment procedure. + +Transfer of Information, due to "Classmark Signalling Procedures". + +This information shall be stored by MSC-B and can be received: + +- Due to a classmark update, either requested from MSC-A (Classmark Request, Classmark Update), or an MS-Initiated Classmark Update. + +This can be carried out either with: + +- the BSSMAP Classmark procedure(s). + +Apart from these cases there is the "odd" case where a Classmark Update can be received during an Inter-MSC Handover by MSC-B, i.e. before the MS has moved to the new channel controlled by MSC-B. This can be made with transparent transfer of BSSMAP Classmark Update. + +#### 4.5.5.4 Downlink DTX-Flag + +The parameter shall be stored by MSC-B to be used at internal Handover in MSC-B. + +Transfer of Information: + +Received by MSC-B from MSC-A in either: + +If the MS has already been assigned to a TCH for speech before the Inter-MSC Handover, the DTX-flag should be sent in: + +- the Handover Request BSSMAP message; + +(if the type of resource is not TCH for speech, the DTX-flag shall not be included). + +If a new assignment to a TCH for speech after an Inter-MSC Handover is to be performed, this can be made with: + +- the BSSMAP Assignment procedure. + +#### 4.5.5.5 Priority + +The parameter shall be stored by MSC-B and is received according to below: + +Transfer of Information: + +Received by MSC-B from MSC-A in: + +- the Handover Request BSSMAP message. + +If a change is needed after an Inter-MSC Handover with: + +- the BSSMAP Assignment procedure. + +#### 4.5.5.6 MSC/BSC-Invoke Trace Information Elements + +The process to be performed by MSC-B on the information elements of the MSC or BSC Invoke Trace BSSMAP messages is left for further study. + +#### 4.5.5.7 LSA Identifier List + +The parameter shall be stored by MSC-B and is received according to below: + +Transfer of Information: + +Received by MSC-B from MSC-A in: + +- the Handover Request BSSMAP message. + +If a change is needed after an Inter-MSC Handover with: + +- the LSA Information BSSMAP message. + +#### 4.5.5.8 Selected UMTS Algorithm + +After inter-MSC handover, the 3G\_MSC-B can perform intra-MSC GSM to UMTS handover. A sequence of possible encryption and integrity protection algorithms, received from the 3G\_MSC-A, can be sent to an RNS in Relocation Request or in Security Mode Command in case of cipher mode setting after intra-MSC-B handover from GSM to UMTS. The RNS chooses one of the listed algorithms and reports this back to the 3G\_MSC in Relocation Request Acknowledge or Security Mode Complete respectively. The MSC-B provides the Selected UMTS algorithm information to the MSC-A. The Selected UMTS algorithms IE in the MAP Process Access Signalling Request message refers to the Chosen Integrity Protection Algorithm and Chosen Encryption Algorithm, defined in RANAP specification 3GPP TS 25.413 [7] + +The selected algorithm shall be stored by 3G\_MSC-B, and sent to 3G\_MSC-A. + +Transfer of Information: + +- If ciphering has not been performed before Inter-MSC Handover, this will be controlled by 3G\_MSC-A after the completion of Inter-MSC Handover and possibly after intra-MSC-B handover from GSM to UMTS. In both cases Selected UMTS algorithm information is received by 3G\_MSC-A from 3G\_MSC-B in: +- The Process Access Signalling Request MAP message. + +#### 4.5.5.9 Allowed UMTS Algorithms + +In case of GSM-subscriber, the Integrity Protection Information and UMTS Encryption Information are not transferred to the MSC-B during inter-MSC handover. Allowed UMTS algorithms is UMTS information that is required in + +RANAP Relocation Request and RANAP Security Mode Command, and shall be provided by 3G\_MSC-A. 3G\_MSC-B needs this information in case of an intra-MSC GSM to UMTS handover and in subsequent security mode setting, after an inter-MSC handover. Therefore 3G\_MSC-A must provide this information in case of an inter-MSC GSM to GSM handover. The Allowed UMTS algorithms IE in the MAP Prepare Handover and in the MAP Forward Access Signalling Request messages refers to the Permitted Integrity Protection Algorithms in Integrity Protection Information and Permitted Encryption Algorithms in Encryption Information, defined in RANAP specification 3GPP TS 25.413 [7]. + +Allowed UMTS algorithms shall be stored by 3G\_MSC-B. + +Transfer of information: + +If ciphering has not been performed before Inter-MSC Handover, this will be controlled by 3G\_MSC-A after the completion of Inter-MSC Handover. + +Ciphering control towards 3G\_MSC-B: + +If Ciphering has been performed before Inter-MSC Handover: + +- The Prepare Handover Request MAP message. + +If Ciphering has NOT been performed before Inter-MSC Handover: + +- The Forward Access Signalling Request MAP message. + +#### 4.5.5.10 BSSMAP Service Handover + +This information shall be stored by 3G\_MSC-B and sent to a BSS in Handover Request, when 3G\_MSC-B performs handover to GSM. + +Transfer of information: + +- The BSSMAP Service Handover information is transferred to 3G\_MSC-B in: + - the Handover Request BSSMAP message. + +If a new assignment of a TCH after an inter-MSC handover is to be performed, the BSSMAP Service Handover information is transferred to 3G\_MSC-B in: + +- the BSSMAP Assignment procedure. + +#### 4.5.5.11 RANAP Service Handover + +This information shall be stored by 3G\_MSC-B and sent to an RNS in Relocation Request, when 3G\_MSC-B performs relocation or handover to UMTS. + +Transfer of information: + +- The RANAP Service Handover information is transferred to 3G\_MSC-B in: + - the Prepare Handover Request MAP message. + +If a new assignment of a Radio Access Bearer after an inter-MSC handover is to be performed, the information is transferred to 3G\_MSC-B in: + +- the Forward Access Signalling Request MAP message + +and sent by 3G\_MSC-B to the RNS in RAB Assignment Request. + +#### 4.5.5.12 SNA Access Information + +This information shall be stored by 3G\_MSC-B and sent to an RNS in the Relocation Request message when 3G\_MSC-B performs handover to UMTS. + +Transfer of information: + +- The SNA Access Information is transferred to 3G\_MSC-B in: + - the Handover Request BSSMAP message. + +#### 4.5.5.13 UESBI + +This information shall be stored by 3G\_MSC-B and sent to an RNS in Relocation Request, when 3G\_MSC-B performs relocation or handover to UMTS. + +Transfer of information: + +The UESBI information is transferred to 3G\_MSC-B in: + +- the Prepare Handover Request MAP message. + +#### 4.5.5.14 Alternative Channel Type + +This information shall be stored by 3G\_MSC-B and from this information 3G\_MSC-B shall generate Alternative RAB Parameters Value IE sent to an RNS in Relocation Request, when 3G\_MSC-B performs relocation or handover to UMTS. + +Transfer of information: + +- The Alternative Channel Type information is transferred to 3G\_MSC-B in: + - the Prepare Handover Request MAP message. + +If a new assignment of a Radio Access Bearer after an inter-MSC handover is to be performed, the information is transferred to 3G\_MSC-B in: + +- the Forward Access Signalling Request MAP message. + +#### 4.5.5.15 Trace parameters + +This information shall be stored by 3G\_MSC-B and 3G\_MSC-B shall use this information for trace activation for MSC-S, MGW, RNC or BSC. + +Transfer of information: + +- The Trace Parameter List information for MSC-S, MGW and RNC tracing is transferred to 3G\_MSC-B in: + - the Prepare Handover Request MAP message. +- The Trace Reference and Trace Type information for BSC tracing is transferred to 3G\_MSC-B in: + - the MSC Invoke Trace BSSMAP message. + +### 4.5.6 Overview of the Technical Specifications GSM interworking for the Inter-MSC Handover + +![Protocol stack diagram for PSTN/ISDN, PLMN, BSS-A, MSC-A, MSC-B, BSS-B, and MS. It shows layers like RR, CM, MM, MAP/E, TCAP, SCCP, and MTP with various interfaces labeled 48.008, 29.010, 29.002, 23.009, and 24.008 (Note).](32ff77da4286b58c4778033acaa10836_img.jpg) + +The diagram illustrates the protocol stack for a mobile network architecture involving PSTN/ISDN, PLMN, BSS-A, MSC-A, MSC-B, BSS-B, and MS. The stack is organized into several layers: + +- RR (Radio Resource) Layer:** Present in BSS-A, MSC-A, MSC-B, BSS-B, and MS. It is the lowest layer in the BSS and MS, and sits above MAP/E in the MSCs. +- CM (Connection Management) Layer:** Present in MSC-A, MSC-B, and MS. It sits above the RR layer. +- MM (Mobility Management) Layer:** Present in MSC-A, MSC-B, and MS. It sits above the CM layer. +- MAP/E (Mobile Application Part/Exchange) Layer:** Present in MSC-A and MSC-B. It sits below the RR layer. +- TCAP (Transaction Capabilities Application Part) Layer:** Present in MSC-A and MSC-B. It sits below the MAP/E layer. +- SCCP (Signaling Connection Control Part) Layer:** Present in MSC-A and MSC-B. It sits above the TCAP layer. +- MTP (Message Transfer Part) Layer:** Present in MSC-A and MSC-B. It is the highest layer shown, sitting above the SCCP layer. + +Interfaces and references are indicated by labels and arrows: + +- 48.008:** Interface between BSS-A and MSC-A, and between BSS-B and MSC-B. +- 29.010:** Interface between MSC-A and MSC-B. +- 29.002:** Interface between MAP/E layers in MSC-A and MSC-B. +- 23.009:** Interface between BSS-B and MS. +- 24.008 (Note):** Interface between MSC-A and MS. + +**Note:** Subset of 48.008 procedures as described in the TS 3GPP TS 48.008. + +**Remark:** The A-bis interface and the link layer protocols being out of the scope of this Specification are not shown here. + +Protocol stack diagram for PSTN/ISDN, PLMN, BSS-A, MSC-A, MSC-B, BSS-B, and MS. It shows layers like RR, CM, MM, MAP/E, TCAP, SCCP, and MTP with various interfaces labeled 48.008, 29.010, 29.002, 23.009, and 24.008 (Note). + +## 4.6 Inter-MSC Handover (UMTS to GSM) + +The general principles of the handover procedures are given in 3GPP TS 23.009 [2]. 3GPP TS 29.010 gives the necessary information for interworking between the 3GPP TS 25.413 [7] RANAP protocol, GSM handover procedures and the 3GPP TS 29.002 [9] MAP protocol. The RANAP protocol is used between the RNS and the 3G-MSC. + +The following three principles apply for the Inter-MSC handover UMTS to GSM: + +- The BSSMAP parameters required for Inter-MSC handover UMTS to GSM are generated as in GSM. + +- Received BSSMAP parameters, e.g. cause code or Handover command, are mapped to the appropriate RANAP parameters, e.g. cause code transparent container to source RNS. + +- When new parameters need to be added for transfer on the E-interface, the principles stated in the beginning of clause 4.5 shall be followed. + +### 4.6.1 Basic Inter-MSC Handover + +When a Mobile Station is handed over between two MSCs, the establishment of a connection between them (described in 3GPP TS 23.009 [2]) requires interworking between A-Interface and E-Interface. + +The signalling at initiation, execution, completion of the Basic Inter-MSC handover procedure is shown in figures 21 to 26 with both possible positive or negative outcomes. + +Additionally figure 21b shows the possible interworking when the trace related message is transparently transferred on the E-Interface at Basic Inter-MSC Handover initiation. + +![Sequence diagram for Basic Inter-MSC Handover initiation (no trace related messages transferred).](d6015fcef74bce83d04acd2e17b4fc15_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant MSC-B + participant BSS-B + + RNS-A->>3G-MSC-A: RELOCATION REQUIRED + 3G-MSC-A->>MSC-B: MAP PREPARE HANDOVER request + Note over MSC-B: Possible Alloc. +of a handover +no. in the VLR-B + MSC-B->>BSS-B: HANDOVER REQUEST + +``` + +The diagram shows the signalling flow for Basic Inter-MSC Handover initiation without trace related messages. It involves four entities: RNS-A, 3G-MSC-A, MSC-B, and BSS-B. The sequence starts with RNS-A sending a RELOCATION REQUIRED message to 3G-MSC-A. 3G-MSC-A then sends a MAP PREPARE HANDOVER request to MSC-B. MSC-B performs an internal allocation (Possible Alloc. of a handover no. in the VLR-B) and then sends a HANDOVER REQUEST message to BSS-B. + +Sequence diagram for Basic Inter-MSC Handover initiation (no trace related messages transferred). + +**Figure 21a: Signalling for Basic Inter-MSC Handover initiation (no trace related messages transferred)** + +![Sequence diagram for Basic Inter-MSC Handover initiation (MSC invoke trace message transferred).](252210dd01a9d2f476bfb1c284c59ccf_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A (*) + participant MSC-B + participant BSS-B + + RNS-A->>3G-MSC-A (*): RELOCATION REQUIRED + 3G-MSC-A (*)->>MSC-B: MAP PREPARE HANDOVER request (**) + Note over MSC-B: Possible Alloc. +of a handover +no. in the VLR-B + MSC-B->>BSS-B: HANDOVER REQUEST + MSC-B->>3G-MSC-A (*): MSC INVOKE TRACE (***) + +``` + +The diagram shows the signalling flow for Basic Inter-MSC Handover initiation with trace related messages transferred. It involves four entities: RNS-A, 3G-MSC-A (marked with \*), MSC-B, and BSS-B. The sequence starts with RNS-A sending a RELOCATION REQUIRED message to 3G-MSC-A. 3G-MSC-A then sends a MAP PREPARE HANDOVER request (marked with \*\*) to MSC-B. MSC-B performs an internal allocation (Possible Alloc. of a handover no. in the VLR-B) and then sends a HANDOVER REQUEST message to BSS-B. Finally, MSC-B sends an MSC INVOKE TRACE (marked with \*\*\*) message back to 3G-MSC-A. + +Sequence diagram for Basic Inter-MSC Handover initiation (MSC invoke trace message transferred). + +**Figure 21b: Signalling for Basic Inter-MSC Handover initiation (MSC invoke trace message transferred)** + +- (\*): Tracing invocation has been received from VLR. +- (\*\*): In that case, HANDOVER REQUEST and MSC INVOKE TRACE messages are included within the AN-APDU parameter. +- (\*\*\*): MSC INVOKE TRACE is forwarded to BSS-B if supported by MSC-B. + +Possible Positive outcomes: + +- a) successful radio resources allocation and handover number allocation (if performed): + +![Sequence diagram for outcome (a): successful radio resources allocation and handover number allocation.](c1278da91cbcabe32628e589ebc47418_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant MSC-B + participant BSS-B + Note right of MSC-B: HANDOVER REQUEST + MSC-B->>BSS-B: HANDOVER REQUEST + BSS-B-->>MSC-B: ACKNOWLEDGE + Note left of MSC-B: MAP PREPARE HANDOVER + 3G-MSC-A->>MSC-B: MAP PREPARE HANDOVER + MSC-B-->>3G-MSC-A: response + Note left of RNS-A: RELOCATION COMMAND + 3G-MSC-A->>RNS-A: RELOCATION COMMAND + +``` + +Sequence diagram for outcome (a): successful radio resources allocation and handover number allocation. + +- b) radio resources allocation queued and successful handover number allocation (if performed). Later successful radio resources allocation indication: + +![Sequence diagram for outcome (b): radio resources allocation queued and successful handover number allocation.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant MSC-B + participant BSS-B + Note right of MSC-B: QUEUING INDICATION + MSC-B->>BSS-B: QUEUING INDICATION + Note left of MSC-B: MAP PREPARE HANDOVER + 3G-MSC-A->>MSC-B: MAP PREPARE HANDOVER + MSC-B-->>3G-MSC-A: response + Note right of MSC-B: HANDOVER REQUEST + MSC-B->>BSS-B: HANDOVER REQUEST + BSS-B-->>MSC-B: ACKNOWLEDGE + Note left of MSC-B: MAP PROCESS ACCESS + 3G-MSC-A->>MSC-B: MAP PROCESS ACCESS + MSC-B-->>3G-MSC-A: response + Note left of RNS-A: RELOCATION COMMAND + 3G-MSC-A->>RNS-A: RELOCATION COMMAND + Note right of MSC-B: SIGNALLING request + MSC-B->>3G-MSC-A: SIGNALLING request + +``` + +Sequence diagram for outcome (b): radio resources allocation queued and successful handover number allocation. + +**Figure 22: Signalling for Basic Inter-MSC Handover execution (Positive outcomes)** + +Possible Negative outcomes: + +- c) user error detected, or handover number allocation unsuccessful (if performed), or component rejection or dialogue abortion performed by MSC-B: + +![Sequence diagram for outcome (c): user error detected, or handover number allocation unsuccessful.](4767b6e106f34fe8b63a6838810bf913_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant MSC-B + participant BSS-B + Note left of RNS-A: RELOCATION PREPARATION + RNS-A->>3G-MSC-A: RELOCATION PREPARATION + Note right of MSC-B: MAP PREPARE HANDOVER response + MSC-B->>3G-MSC-A: MAP PREPARE HANDOVER response + Note right of MSC-B: negative result, MAP CLOSE + MSC-B->>3G-MSC-A: negative result, MAP CLOSE + Note right of MSC-B: MAP U/P-ABORT + MSC-B->>3G-MSC-A: MAP U/P-ABORT + Note left of RNS-A: FAILURE (Note 1) + 3G-MSC-A->>RNS-A: FAILURE (Note 1) + +``` + +Sequence diagram for outcome (c): user error detected, or handover number allocation unsuccessful. + +- d) radio resources allocation failure: + +![Sequence diagram for Figure 23 (part e) showing a successful handover preparation followed by a failure in relocation preparation.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant MSC-B + participant BSS-B + 3G-MSC-A->>MSC-B: MAP PREPARE HANDOVER + MSC-B-->>3G-MSC-A: response + BSS-B-->>MSC-B: HANDOVER FAILURE + 3G-MSC-A-->>RNS-A: RELOCATION PREPARATION FAILURE (Note 1) + +``` + +Sequence diagram for Figure 23 (part e) showing a successful handover preparation followed by a failure in relocation preparation. + +e) radio resources allocation queued and successful handover number allocation (if performed). Later unsuccessful radio resources allocation: + +![Sequence diagram for Figure 23 (part f) showing a successful handover preparation, followed by queuing and then a failure in relocation preparation.](69e5f1993021af230d08c08aac97d9df_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant MSC-B + participant BSS-B + 3G-MSC-A->>MSC-B: MAP PREPARE HANDOVER + MSC-B-->>3G-MSC-A: response + BSS-B-->>MSC-B: QUEUING INDICATION + 3G-MSC-A->>MSC-B: MAP PROCESS ACCESS + MSC-B-->>3G-MSC-A: SIGNALLING request + BSS-B-->>MSC-B: HANDOVER FAILURE + 3G-MSC-A-->>RNS-A: RELOCATION PREPARATION FAILURE (Note 1) + +``` + +Sequence diagram for Figure 23 (part f) showing a successful handover preparation, followed by queuing and then a failure in relocation preparation. + +f) unsuccessful handover execution (Reversion to the old radio resources): + +![Sequence diagram for Figure 23 (part f) showing the reversion to old radio resources after a failure.](052543d8c9c0643b05b3ce45c6decca1_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant MSC-B + participant BSS-B + RNS-A->>3G-MSC-A: RELOCATION CANCEL + 3G-MSC-A->>MSC-B: MAP U -ABORT + MSC-B->>BSS-B: CLEAR COMMAND + 3G-MSC-A-->>RNS-A: RELOCATION CANCEL ACK + +``` + +Sequence diagram for Figure 23 (part f) showing the reversion to old radio resources after a failure. + +**Figure 23: Signalling for Basic Inter-MSC Handover execution (Negative outcomes)** + +NOTE 1: Possible rejection of the handover because of the negative outcome of MAP or RANAP procedure. + +![Sequence diagram for Figure 24 showing the completion of a successful handover.](d116934392360da963e91d840d1e45a8_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant MSC-B + participant BSS-B + BSS-B->>MSC-B: HANDOVER COMPLETE + MSC-B->>3G-MSC-A: MAP SEND END SIGNAL request + 3G-MSC-A->>RNS-A: IU RELEASE COMMAND + +``` + +Sequence diagram for Figure 24 showing the completion of a successful handover. + +**Figure 24: Signalling for Basic Inter-MSC Handover completion** + +Positive outcome: + +![Sequence diagram for Basic Inter-MSC Handover completion (Positive outcome)](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant MSC-B + participant BSS-B + Note left of 3G-MSC-A: + 3G-MSC-A->>MSC-B: MAP SEND END SIGNAL + Note right of MSC-B: + MSC-B-->>3G-MSC-A: response + Note right of MSC-B: + MSC-B->>BSS-B: CLEAR COMMAND + Note right of BSS-B: (Note 2) + +``` + +The diagram shows a sequence of messages for a positive handover completion. It starts with 3G-MSC-A sending a 'MAP SEND END SIGNAL' to MSC-B. MSC-B responds with a 'response' message. Finally, MSC-B sends a 'CLEAR COMMAND' to BSS-B, which is noted as being relevant from an interworking perspective between MAP and BSSMAP when the call is released. + +Sequence diagram for Basic Inter-MSC Handover completion (Positive outcome) + +**Figure 25: Signalling for Basic Inter-MSC Handover completion (Positive outcome)** + +Negative outcome: + +![Sequence diagram for Basic Inter-MSC Handover completion (Negative outcome)](0f26e70157bd4c45f825795cdcd20fbd_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant MSC-B + participant BSS-B + Note left of 3G-MSC-A: + 3G-MSC-A->>MSC-B: MAP U/P -ABORT + Note right of MSC-B: + MSC-B->>BSS-B: CLEAR COMMAND + +``` + +The diagram shows a sequence of messages for a negative handover completion. It starts with 3G-MSC-A sending a 'MAP U/P -ABORT' message to MSC-B. In response, MSC-B sends a 'CLEAR COMMAND' message to BSS-B. + +Sequence diagram for Basic Inter-MSC Handover completion (Negative outcome) + +**Figure 26: Signalling for Basic Inter-MSC Handover completion (Negative outcome)** + +NOTE 2: From interworking between MAP and BSSMAP point of view, when the call is released. + +The handover procedure is normally triggered by RNS-A by sending a RELOCATION REQUIRED message on Iu-Interface to 3G-MSC-A. The invocation of the Basic Inter-MSC handover procedure is performed and controlled by 3G-MSC-A. The sending of the MAP Prepare-Handover request to MSC-B is triggered in 3G-MSC-A upon receipt of the RELOCATION REQUIRED message. For compatibility reason, the cell identity of the cell where the call is to be handed over in MSC-B area, provided in the RELOCATION REQUIRED message, is mapped into targetCellId MAP parameter and the HANDOVER REQUEST message is encapsulated in the AN-APDU MAP parameter of the Prepare-Handover MAP request. MSC-B can invoke another operation towards the VLR-B (allocation of the handover number described in 3GPP TS 29.002 [9]). + +Additionally, if tracing activity has been invoked, the trace related message can be transferred on the E-Interface encapsulated in the AN-APDU MAP parameter of the Prepare-Handover Request. If transferred, one complete trace related message at a time shall be included in the AN-APDU MAP parameter after the HANDOVER REQUEST message. + +The interworking between Prepare Handover and RELOCATION REQUIRED is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|---------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| Forward message | RELOCATION REQUIRED MAP PREPARE HANDOVER request
RANAP information elements
MSC INVOKE TRACE) | -ho-NumberNotRequired
-targetCellId
-AN-APDU(
HANDOVER REQUEST, | 1
2 | +| Positive result | RELOCATION CMD | MAP PREPARE HANDOVER response
-handover number
-AN-APDU(
QUEUING INDICATION
or HANDOVER REQUEST
ACKNOWLEDGE) | 3 | +| Negative result | RELOCATION PREP FAILURE
Relocation failure in
" target RNC/CN or target system
"
"
"
"
" | MAP PREPARE HANDOVER
System Failure
No Handover Number
available
UnexpectedDataValue
Data Missing
MAP CLOSE
MAP U/P -ABORT | 4 | + +NOTE 1: The BSSMAP information elements are already stored in 3G-MSC. + +The ho-NumberNotRequired parameter is included by 3G-MSC-A, when 3G-MSC-A decides not to use any circuit connection with MSC-B. No handover number shall be present in the positive result. Any negative response from MSC-B shall not be due to handover number allocation problem. + +NOTE 2: The process performed on the RANAP information elements received in the RELOCATION REQUIRED message is described in the 3GPP TS 25.413 [7]. + +NOTE 3: The response to the Prepare-Handover request can include in its AN-APDU parameter, identifying the 3GPP TS 48.006 protocol, either a BSSMAP QUEUING INDICATION, or a BSSMAP HANDOVER REQUEST ACKNOWLEDGE. + +In the first case, 3G-MSC-A shall wait for the radio resources allocation response from MSC-B, transmitted to 3G-MSC-A as described in clause 4.5.4. + +In the second case, the positive result triggers in 3G-MSC-A the sending on Iu-Interface of the RELOCATION CMD. + +In the third case, the positive result triggers in 3G-MSC-A. + +NOTE 4: The possible sending of the RELOCATION PREP FAILURE message is described in the 3G 25.413. + +(The possible sending of the RELOCATION PREP FAILURE message upon receipt of the HANDOVER FAILURE is out of the scope of the 3GPP TS 29.010 and lies in the 3GPP TS 25.413 [7]). + +The interworking between Send End Signal and HANDOVER COMPLETE in MSC-B is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|-----------------------------------------------------------------|-------------------------------------------------------------|-------| +| Forward message | HANDOVER COMPLETE | MAP SEND END SIGNAL request
-AN-APDU (HANDOVER COMPLETE) | | +| Positive result | CLEAR COMMAND
-Call Control release | MAP SEND END SIGNAL response | 1 | +| Negative result | CLEAR COMMAND
-Call Control release
-Call Control release | MAP CLOSE
MAP U/P -ABORT | 2 | + +NOTE 1: The positive empty result triggers the clearing of the Radio Resources on the A-Interface and the release of the SCCP connection between MSC-B and BSS-B. If a circuit connection is used between 3G\_MSC-A and MSC-B, the 'Call Control release' clearing cause shall only be given to BSS-B when MSC-B has received a clearing indication on its circuit connection with 3G\_MSC-A. + +NOTE 2: The abortion of the dialogue or the rejection of the component triggers in MSC-B the clearing of its circuit connection with 3G\_MSC-A, if any, of the Radio Resources on the A-Interface and the release of the SCCP connection between MSC-B and BSS-B. + +The interworking between Send End Signal and IU RELEASE COMMAND in 3G\_MSC-A is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|---------------------------------------------------------------------------------------|--------------------|-------| +| Forward message | MAP SEND END SIGNAL response
-AN-APDU (HANDOVER COMPLETE)
Successful Relocation | IU RELEASE COMMAND | | +| Positive result | | | | +| Negative result | | | | + +The interworking between RELOCATION CANCEL in case of reversion to old channel of the UE and User Abort in 3G-MSC-A is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|--------------------------------------------|--------------|-------| +| Forward message | RELOCATION CANCEL
-Relocation cancelled | MAP U -ABORT | | +| Positive result | RELOCATION CANCEL ACKNOWLEDGEMENT | | | +| Negative result | | | | + +### 4.6.2 Subsequent Inter-MSC Handover from 3G-MSC-B back to MSC-A + +When a Mobile Station is being handed over back to MSC-A, the procedure (described in TS 23.009) requires interworking between A-Interface, Iu-interface and E-Interface. + +The signalling at initiation, execution and completion of the Subsequent Inter-MSC handover procedure is shown in figures 27 to 31. + +![Sequence diagram for Figure 27: Signalling for Subsequent Inter-MSC Handover back to MSC-A initiation. Lifelines: RNS-A, 3G-MSC-B, MSC-A, BSS-B. RNS-A sends RELOCATION REQUIRED to 3G-MSC-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER request to MSC-A. MSC-A sends HANDOVER REQUEST to BSS-B.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant BSS-B + Note left of RNS-A: RELOCATION REQUIRED + RNS-A-->>3G-MSC-B: RELOCATION REQUIRED + 3G-MSC-B-->>MSC-A: MAP PREPARE SUBSEQUENT HANDOVER request + MSC-A-->>BSS-B: HANDOVER REQUEST + +``` + +Sequence diagram for Figure 27: Signalling for Subsequent Inter-MSC Handover back to MSC-A initiation. Lifelines: RNS-A, 3G-MSC-B, MSC-A, BSS-B. RNS-A sends RELOCATION REQUIRED to 3G-MSC-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER request to MSC-A. MSC-A sends HANDOVER REQUEST to BSS-B. + +Figure 27: Signalling for Subsequent Inter-MSC Handover back to MSC-A initiation + +Possible Positive outcomes: + +a) successful radio resources allocation: + +![Sequence diagram for outcome a: successful radio resources allocation. Lifelines: RNS-A, 3G-MSC-B, MSC-A, BSS-B. MSC-A sends HANDOVER REQUEST to BSS-B. BSS-B responds with ACKNOWLEDGE. MSC-A sends MAP PREPARE SUBSEQUENT HANDOVER response to 3G-MSC-B. 3G-MSC-B sends RELOCATION CMD to RNS-A.](396197257cf9437b526bb6585b6a9c8a_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant BSS-B + MSC-A-->>BSS-B: HANDOVER REQUEST + BSS-B-->>MSC-A: ACKNOWLEDGE + MSC-A-->>3G-MSC-B: MAP PREPARE SUBSEQUENT HANDOVER response + 3G-MSC-B-->>RNS-A: RELOCATION CMD + +``` + +Sequence diagram for outcome a: successful radio resources allocation. Lifelines: RNS-A, 3G-MSC-B, MSC-A, BSS-B. MSC-A sends HANDOVER REQUEST to BSS-B. BSS-B responds with ACKNOWLEDGE. MSC-A sends MAP PREPARE SUBSEQUENT HANDOVER response to 3G-MSC-B. 3G-MSC-B sends RELOCATION CMD to RNS-A. + +b) radio resources allocation queued. Later successful radio resources allocation indication: + +![Sequence diagram for outcome b: radio resources allocation queued. Lifelines: RNS-A, 3G-MSC-B, MSC-A, BSS-B. MSC-A sends QUEUING INDICATION to BSS-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER response to MSC-A. MSC-A sends HANDOVER REQUEST to BSS-B. BSS-B responds with ACKNOWLEDGE. MSC-A sends MAP FORWARD ACCESS SIGNALLING request to 3G-MSC-B. 3G-MSC-B sends RELOCATION CMD to RNS-A.](2aa94b70ba3fadcba8420d9e3128253a_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant BSS-B + MSC-A-->>BSS-B: QUEUING INDICATION + 3G-MSC-B-->>MSC-A: MAP PREPARE SUBSEQUENT HANDOVER response + MSC-A-->>BSS-B: HANDOVER REQUEST + BSS-B-->>MSC-A: ACKNOWLEDGE + MSC-A-->>3G-MSC-B: MAP FORWARD ACCESS SIGNALLING request + 3G-MSC-B-->>RNS-A: RELOCATION CMD + +``` + +Sequence diagram for outcome b: radio resources allocation queued. Lifelines: RNS-A, 3G-MSC-B, MSC-A, BSS-B. MSC-A sends QUEUING INDICATION to BSS-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER response to MSC-A. MSC-A sends HANDOVER REQUEST to BSS-B. BSS-B responds with ACKNOWLEDGE. MSC-A sends MAP FORWARD ACCESS SIGNALLING request to 3G-MSC-B. 3G-MSC-B sends RELOCATION CMD to RNS-A. + +Figure 28: Signalling for Subsequent Inter-MSC Handover back to MSC-A execution (Positive outcome) + +Possible Negative outcomes: + +c) user error detected, or component rejection or dialogue abortion performed by MSC-A: + +![Sequence diagram for outcome c: user error detected, or component rejection or dialogue abortion performed by MSC-A. Lifelines: RNS-A, 3G-MSC-B, MSC-A, BSS-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER to MSC-A. MSC-A responds with response negative result. RNS-A sends RELOCATION PREP FAILURE (Note 1) to 3G-MSC-B.](fdc47b9a20953c3611add6122f6831bf_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant BSS-B + 3G-MSC-B-->>MSC-A: MAP PREPARE SUBSEQUENT HANDOVER + MSC-A-->>3G-MSC-B: response negative result + RNS-A-->>3G-MSC-B: RELOCATION PREP FAILURE (Note 1) + +``` + +Sequence diagram for outcome c: user error detected, or component rejection or dialogue abortion performed by MSC-A. Lifelines: RNS-A, 3G-MSC-B, MSC-A, BSS-B. 3G-MSC-B sends MAP PREPARE SUBSEQUENT HANDOVER to MSC-A. MSC-A responds with response negative result. RNS-A sends RELOCATION PREP FAILURE (Note 1) to 3G-MSC-B. + +d) component rejection or dialogue abortion performed by MSC-A: + +![Sequence diagram for outcome d: component rejection or dialogue abortion performed by MSC-A. Lifelines: RNS-A, 3G-MSC-B, MSC-A, BSS-B. MSC-A sends MAP CLOSE, MAP U/P ABORT to 3G-MSC-B. RNS-A sends IU RELEASE COMMAND to 3G-MSC-B.](85c4282df510941b5d97b3cf36b11e2a_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant BSS-B + MSC-A-->>3G-MSC-B: MAP CLOSE, MAP U/P ABORT + RNS-A-->>3G-MSC-B: IU RELEASE COMMAND + +``` + +Sequence diagram for outcome d: component rejection or dialogue abortion performed by MSC-A. Lifelines: RNS-A, 3G-MSC-B, MSC-A, BSS-B. MSC-A sends MAP CLOSE, MAP U/P ABORT to 3G-MSC-B. RNS-A sends IU RELEASE COMMAND to 3G-MSC-B. + +e) radio resources allocation failure: + +![Sequence diagram for Figure 29: Signalling for Subsequent Inter-MSC Handover back to MSC-A execution (Negative outcome).](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant BSS-B + RNS-A->>3G-MSC-B: RELOCATION PREP + 3G-MSC-B->>MSC-A: MAP PREPARE SUBSEQUENT + MSC-A-->>BSS-B: HANDOVER FAILURE + MSC-A-->>3G-MSC-B: HANDOVER response + 3G-MSC-B-->>RNS-A: FAILURE (Note 1) + +``` + +Sequence diagram for Figure 29: Signalling for Subsequent Inter-MSC Handover back to MSC-A execution (Negative outcome). + +f) radio resources allocation queued. Later unsuccessful radio resources allocation: + +![Sequence diagram for Figure 29 continuation: radio resources allocation queued.](aeb2a26a07219661191294dba528067a_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant BSS-B + RNS-A->>3G-MSC-B: RELOCATION PREP + 3G-MSC-B->>MSC-A: MAP PREPARE SUBSEQUENT + MSC-A-->>BSS-B: QUEUING INDICATION + MSC-A-->>3G-MSC-B: HANDOVER response + 3G-MSC-B->>MSC-A: MAP FORWARD ACCESS + MSC-A-->>BSS-B: HANDOVER FAILURE + 3G-MSC-B-->>RNS-A: FAILURE (Note 1) + +``` + +Sequence diagram for Figure 29 continuation: radio resources allocation queued. + +**Figure 29: Signalling for Subsequent Inter-MSC Handover back to MSC-A execution +(Negative outcome)** + +NOTE 1: Possible rejection of the handover because of the negative outcome of MAP or BSSMAP procedure. + +![Sequence diagram for Figure 30: Signalling for Subsequent Inter-MSC Handover back to MSC-A completion (Successful completion of the procedure).](58bbc570572758132ea39938e4f03b5b_img.jpg) + +``` + +sequenceDiagram + participant BSS-B + participant MSC-A + participant 3G-MSC-B + participant RNS-A + BSS-B->>MSC-A: HANDOVER COMPLETE + MSC-A->>3G-MSC-B: MAP SEND END SIGNAL + 3G-MSC-B-->>MSC-A: response + 3G-MSC-B->>RNS-A: Iu RELEASE COMMAND + +``` + +Sequence diagram for Figure 30: Signalling for Subsequent Inter-MSC Handover back to MSC-A completion (Successful completion of the procedure). + +**Figure 30: Signalling for Subsequent Inter-MSC Handover back to MSC-A completion +(Successful completion of the procedure)** + +NOTE: Positive outcome case shown in figure 9. + +![Sequence diagram for Figure 31: Signalling for Subsequent Inter-MSC Handover back to MSC-A completion (Unsuccessful completion of the procedure).](a548c5381cebd2650c5edb725b19f795_img.jpg) + +``` + +sequenceDiagram + participant BSS-B + participant MSC-A + participant 3G-MSC-B + participant RNS-A + BSS-B->>MSC-A: HANDOVER COMPLETE + MSC-A->>3G-MSC-B: MAP SEND END SIGNAL + 3G-MSC-B-->>MSC-A: response + MSC-A-->>3G-MSC-B: MAP U/P -ABORT + 3G-MSC-B->>RNS-A: Iu RELEASE COMMAND (Note 1) + +``` + +Sequence diagram for Figure 31: Signalling for Subsequent Inter-MSC Handover back to MSC-A completion (Unsuccessful completion of the procedure). + +**Figure 31: Signalling for Subsequent Inter-MSC Handover back to MSC-A completion (Unsuccessful +completion of the procedure)** + +NOTE 1: Abnormal end of the procedure which triggers the clearing of all resources in 3G-MSC-B. + +The interworking between Prepare Subsequent Handover and RELOCATION REQUIRED is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | REL. REQUIRED

RANAP information elements:

MS Classmark 2
Source Id
Target Id
Cause
MS Classmark 3 | MAP PREPARE SUBSEQUENT HANDOVER request

-target MSC number
-targetCellId
-AN-APDU(
HANDOVER REQUEST)

BSSMAP information elements:

CM2
Cell Id (serving)
Cell Id (target)
Cause
CM3

info stored/generated in/by 3G-MSC-B:
Message Type
Channel Type
Speech version
Priority
Interference Band to be used | 1 | +| Positive result | RELOCATION CMD.

RANAP information elements:
L3 information | MAP PREPARE SUBSEQUENT HANDOVER response
-AN-APDU(
QUEUING INDICATION or HANDOVER REQUEST
ACKNOWLEDGE or HANDOVER FAILURE)

BSSMAP information elements:
L3 information | 2 | +| Negative result | REL. PREP. FAILURE

Relocation Failure in Target CN/RNC or Target System
Unknown MSC
Relocation Failure in Target CN/RNC or Target System
Subsequent Handover

Relocation Failure in Target CN/RNC or Target System
UnexpectedDataValue
Relocation Failure in Target CN/RNC or Target System
Data Missing

Iu RELEASE COMMAND

Relocation Cancelled MAP CLOSE
Relocation Cancelled MAP U/P -ABORT | MAP PREPARE SUBSEQUENT HANDOVER response | 3 | + +NOTE 1: The mapping of cause code values between BSSMAP and RANAP is FFS. + +NOTE 2: The response to the Prepare-Subsequent-Handover request can include in its AN-APDU parameter, identifying the 3GPP TS 48.006 protocol, a BSSMAP QUEUING INDICATION, or a BSSMAP HANDOVER REQUEST ACKNOWLEDGE or a BSSMAP HANDOVER FAILURE. + +In the first case, 3G-MSC-B shall wait for the radio resources allocation response from MSC-A, transmitted to 3G-MSC-B as described in clause 4.5.4. + +In the second case, the positive result triggers in 3G-MSC-B the sending on Iu-Interface of the RELOCATION COMMAND. + +In the third case, the positive result triggers in 3G-MSC-B the sending of the RELOCATION PREPARATION FAILURE. + +NOTE 3: The possible sending of the RELOCATION PREPARATION FAILURE message is described in 3GPP TS 25.413 [7]. + +The interworking between Send End Signal Result and HANDOVER COMPLETE in MSC-A is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|-------------------|------------------------------|-------| +| Forward message | HANDOVER COMPLETE | MAP SEND END SIGNAL response | | +| Positive result | | | | +| Negative result | | MAP U/P -ABORT | 1 | + +NOTE: The abortion of the dialogue ends the handover procedure with 3G-MSC-B. + +### 4.6.3 Subsequent Inter-MSC Handover to third MSC + +When a Mobile Station is being handed over to a third MSC, the procedure (described in 3GPP TS 23.009 [2]) does require one specific interworking case in MSC-A between E-Interface from 3G-MSC-B and E-Interface from MSC-B' other than the combination of the ones described in clauses 4.6.1 and 4.6.2. + +![Sequence diagram showing signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') initiation. The diagram shows four entities: RNS-A, 3G-MSC-B, MSC-A, and MSC-B'. The sequence starts with RNS-A sending a RELOCATION REQUIRED message to 3G-MSC-B. 3G-MSC-B sends a MAP PREPARE SUBSEQUENT HANDOVER request to MSC-A. MSC-A sends a MAP PREPARE HANDOVER request to MSC-B'. MSC-B' contains a nested box for 'Possib. Alloc. of ho. number VLR-B' and 'BSS-B'' and sends a HANDOVER REQUEST message back to MSC-A.](62ee64afa2d368d732de66628cf2c841_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + Note right of MSC-B': Possib. Alloc. of ho. number VLR-B + Note right of MSC-B': BSS-B' + RNS-A->>3G-MSC-B: RELOCATION REQUIRED + 3G-MSC-B->>MSC-A: MAP PREPARE SUBSEQUENT HANDOVER request + MSC-A->>MSC-B': MAP PREPARE HANDOVER request + MSC-B'-->>MSC-A: HANDOVER REQUEST + +``` + +Sequence diagram showing signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') initiation. The diagram shows four entities: RNS-A, 3G-MSC-B, MSC-A, and MSC-B'. The sequence starts with RNS-A sending a RELOCATION REQUIRED message to 3G-MSC-B. 3G-MSC-B sends a MAP PREPARE SUBSEQUENT HANDOVER request to MSC-A. MSC-A sends a MAP PREPARE HANDOVER request to MSC-B'. MSC-B' contains a nested box for 'Possib. Alloc. of ho. number VLR-B' and 'BSS-B'' and sends a HANDOVER REQUEST message back to MSC-A. + +Figure 32: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') initiation + +Possible Positive outcomes: + +- successful radio resources allocation: + +![Sequence diagram for Figure 33 (Positive outcome) showing signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution. Lifelines: RNS-A, 3G-MSC-B, MSC-A, MSC-B', BSS-B'. The sequence starts with RNS-A sending a RELOCATION COMMAND to 3G-MSC-B. 3G-MSC-B sends a MAP PREPARE SUBSEQUENT HANDOVER response to MSC-A. MSC-A sends a MAP PREPARE HANDOVER response to MSC-B'. MSC-B' sends a HANDOVER REQUEST to BSS-B'. BSS-B' sends a HANDOVER ACKNOWLEDGE to MSC-B'.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + Note right of RNS-A: RELOCATION COMMAND + RNS-A->>3G-MSC-B: RELOCATION COMMAND + 3G-MSC-B-->>MSC-A: MAP PREPARE SUBSEQUENT HANDOVER response + MSC-A-->>MSC-B': MAP PREPARE HANDOVER response + MSC-B'-->>BSS-B': HANDOVER REQUEST + BSS-B'-->>MSC-B': HANDOVER ACKNOWLEDGE + +``` + +Sequence diagram for Figure 33 (Positive outcome) showing signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution. Lifelines: RNS-A, 3G-MSC-B, MSC-A, MSC-B', BSS-B'. The sequence starts with RNS-A sending a RELOCATION COMMAND to 3G-MSC-B. 3G-MSC-B sends a MAP PREPARE SUBSEQUENT HANDOVER response to MSC-A. MSC-A sends a MAP PREPARE HANDOVER response to MSC-B'. MSC-B' sends a HANDOVER REQUEST to BSS-B'. BSS-B' sends a HANDOVER ACKNOWLEDGE to MSC-B'. + +b) radio resources allocation queued and successful handover number allocation, if performed. Later successful radio resources allocation indication: + +![Sequence diagram for Figure 33 (Positive outcome) showing signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution. Lifelines: RNS-A, 3G-MSC-B, MSC-A, MSC-B', BSS-B'. The sequence starts with RNS-A sending a RELOCATION COMMAND to 3G-MSC-B. 3G-MSC-B sends a MAP PREPARE SUBSEQUENT HANDOVER response to MSC-A. MSC-A sends a MAP PREPARE HANDOVER response to MSC-B'. MSC-B' sends a QUEUING INDICAT. to BSS-B'. BSS-B' sends a HANDOVER REQUEST to MSC-B'. MSC-B' sends a MAP PROCESS ACCESS SIGNALLING request to MSC-A. MSC-A sends a MAP FORWARD ACCESS SIGNALLING request to 3G-MSC-B. 3G-MSC-B sends a RELOCATION COMMAND to RNS-A.](18e519d1f91133e080347562f681dfb5_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + Note right of RNS-A: RELOCATION COMMAND + RNS-A->>3G-MSC-B: RELOCATION COMMAND + 3G-MSC-B-->>MSC-A: MAP PREPARE SUBSEQUENT HANDOVER response + MSC-A-->>MSC-B': MAP PREPARE HANDOVER response + MSC-B'-->>BSS-B': QUEUING INDICAT. + BSS-B'-->>MSC-B': HANDOVER REQUEST + MSC-B'-->>MSC-A: MAP PROCESS ACCESS SIGNALLING request + MSC-A-->>3G-MSC-B: MAP FORWARD ACCESS SIGNALLING request + 3G-MSC-B-->>RNS-A: RELOCATION COMMAND + +``` + +Sequence diagram for Figure 33 (Positive outcome) showing signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution. Lifelines: RNS-A, 3G-MSC-B, MSC-A, MSC-B', BSS-B'. The sequence starts with RNS-A sending a RELOCATION COMMAND to 3G-MSC-B. 3G-MSC-B sends a MAP PREPARE SUBSEQUENT HANDOVER response to MSC-A. MSC-A sends a MAP PREPARE HANDOVER response to MSC-B'. MSC-B' sends a QUEUING INDICAT. to BSS-B'. BSS-B' sends a HANDOVER REQUEST to MSC-B'. MSC-B' sends a MAP PROCESS ACCESS SIGNALLING request to MSC-A. MSC-A sends a MAP FORWARD ACCESS SIGNALLING request to 3G-MSC-B. 3G-MSC-B sends a RELOCATION COMMAND to RNS-A. + +**Figure 33: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution (Positive outcome)** + +Possible Negative outcomes: + +c) user error detected, or component rejection or dialogue abortion performed by MSC-B': + +![Sequence diagram for scenario d) radio resources allocation failure. Lifelines: RNS-A, 3G-MSC-B, MSC-A, MSC-B', BSS-B'. The sequence shows a handover preparation from MSC-A to MSC-B' via BSS-B', which fails. MSC-A then sends a MAP PREPARE SUBSEQUENT to 3G-MSC-B, which also fails, resulting in a RELOCATION PREPARATION FAILURE at RNS-A.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + Note right of MSC-A: MAP PREPARE HANDOVER + MSC-A->>BSS-B': response negative result + Note right of MSC-A: MAP CLOSE + Note right of MSC-A: <----- + Note right of MSC-A: MAP U/P -ABORT + Note right of 3G-MSC-B: MAP PREPARE SUBSEQUENT + Note right of 3G-MSC-B: <----- + Note right of 3G-MSC-B: HANDOVER response negative + Note right of 3G-MSC-B: result + Note right of RNS-A: RELOCATION + Note right of RNS-A: <----- + Note right of RNS-A: PREPARATION + Note right of RNS-A: FAILURE + Note right of RNS-A: (Note 1) + +``` + +Sequence diagram for scenario d) radio resources allocation failure. Lifelines: RNS-A, 3G-MSC-B, MSC-A, MSC-B', BSS-B'. The sequence shows a handover preparation from MSC-A to MSC-B' via BSS-B', which fails. MSC-A then sends a MAP PREPARE SUBSEQUENT to 3G-MSC-B, which also fails, resulting in a RELOCATION PREPARATION FAILURE at RNS-A. + +d) radio resources allocation failure: + +![Sequence diagram for scenario e) radio resources allocation queued and successful handover number allocation. Lifelines: RNS-A, 3G-MSC-B, MSC-A, MSC-B', BSS-B'. The sequence shows a handover preparation from MSC-A to MSC-B' via BSS-B', which fails. MSC-A then sends a MAP PREPARE SUBSEQUENT to 3G-MSC-B, which succeeds with a HANDOVER response. This results in a RELOCATION PREPARATION FAILURE at RNS-A.](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + Note right of BSS-B': HANDOVER + Note right of BSS-B': <----- + Note right of BSS-B': FAILURE + Note right of MSC-A: MAP PREPARE HANDOVER + Note right of MSC-A: <----- + Note right of MSC-A: response + Note right of 3G-MSC-B: MAP PREPARE SUBSEQUENT + Note right of 3G-MSC-B: <----- + Note right of 3G-MSC-B: HANDOVER response + Note right of RNS-A: RELOCATION + Note right of RNS-A: <----- + Note right of RNS-A: PREPARATION + Note right of RNS-A: FAILURE + Note right of RNS-A: (Note 1) + +``` + +Sequence diagram for scenario e) radio resources allocation queued and successful handover number allocation. Lifelines: RNS-A, 3G-MSC-B, MSC-A, MSC-B', BSS-B'. The sequence shows a handover preparation from MSC-A to MSC-B' via BSS-B', which fails. MSC-A then sends a MAP PREPARE SUBSEQUENT to 3G-MSC-B, which succeeds with a HANDOVER response. This results in a RELOCATION PREPARATION FAILURE at RNS-A. + +e) radio resources allocation queued and successful handover number allocation (if performed). Later unsuccessful radio resources allocation: + +![Sequence diagram for Figure 34: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution (Negative outcome).](7ed5d5770331f31ade15439a21c31425_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + + Note right of BSS-B': QUEUING +INDICAT. + MSC-A->>MSC-B': MAP PREPARE HANDOVER + MSC-B'-->>MSC-A: response + MSC-A->>3G-MSC-B: MAP PREPARE SUBSEQUENT + 3G-MSC-B-->>MSC-A: HANDOVER response + BSS-B'-->>MSC-B': HANDOVER +FAILURE + MSC-B'-->>MSC-A: MAP PROCESS ACCESS +SIGNALLING request + MSC-A->>3G-MSC-B: MAP FORWARD ACCESS +SIGNALLING request + 3G-MSC-B-->>RNS-A: RELOCATION +PREPARATION +FAILURE +(Note 1) + +``` + +Sequence diagram for Figure 34: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution (Negative outcome). + +**Figure 34: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') execution (Negative outcome)** + +NOTE 1: Possible rejection of the handover because of the negative outcome of MAP or BSSMAP procedure. + +Positive outcome: + +![Sequence diagram for Figure 35: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') completion (Successful completion of the procedure).](d7948c38a18636aefecdd95388196460_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + + BSS-B'-->>MSC-B': HANDOVER +COMPLETE + MSC-B'-->>MSC-A: MAP SEND END SIGNAL + MSC-A->>3G-MSC-B: MAP SEND END SIGNAL + 3G-MSC-B-->>MSC-A: response + 3G-MSC-B-->>RNS-A: IU-RELEASE +COMMAND + +``` + +Sequence diagram for Figure 35: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') completion (Successful completion of the procedure). + +**Figure 35: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') completion (Successful completion of the procedure)** + +Negative outcome: + +![Sequence diagram showing signalling for subsequent inter-MSC handover to third MSC (MSC-B') completion (Unsuccessful completion of the procedure).](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant MSC-A + participant MSC-B' + participant BSS-B' + + Note left of RNS-A: RELOCATION +-----> +CANCEL + RNS-A->>3G-MSC-B: + 3G-MSC-B->>MSC-A: MAP PROCESS ACCESS +-----> +SIGNALLING request (Note 1) + Note right of MSC-A: MAP U -ABORT +-----> +MSC-A->>MSC-B': + MSC-B'->>BSS-B': CLEAR +-----> +COMMAND + Note left of RNS-A: RELOCATION +<----- +CANCEL ACK + +``` + +Sequence diagram showing signalling for subsequent inter-MSC handover to third MSC (MSC-B') completion (Unsuccessful completion of the procedure). + +**Figure 36: Signalling for Subsequent Inter-MSC Handover to third MSC (MSC-B') completion (Unsuccessful completion of the procedure)** + +NOTE 1: Specific interworking case detailed below. + +The specific interworking case in MSC-A compared to the clauses 4.5.1 and 4.5.2 occurs between HANDOVER FAILURE encapsulated in a Process Access Signalling from 3G-MSC-B and the abortion of the dialogue with MSC-B' in the case of a reversion to old channel of the MS: + +| | 29.002 | 29.002 | Notes | +|-----------------|-----------------------------------------------------------------------|----------------|-------| +| Forward message | MAP PROCESS-SIGNALLING request

-AN-APDU (
HANDOVER FAILURE) | MAP U -ABORT | 1 | +| Positive result | | | | +| Negative result | | MAP U/P -ABORT | 2 | + +NOTE 1: The abortion of the dialogue triggers in MSC-B' the clearing of the circuit connection with MSC-A, if any, and of the Resources between MSC-B' and BSS-B'. The abortion of the dialogue ends the handover procedure with MSC-B'. + +NOTE 2: The abortion of the dialogue ends the handover procedure with 3G-MSC-B. + +### 4.6.4 BSSAP Messages transfer on E-Interface + +The handling is described in clause 4.5.4. + +### 4.6.5 Processing in MSC-B, and information transfer on E-interface + +The handling is described in clause 4.5.5. + +### 4.6.6 Cause Code Mapping + +When a Mobile Station is handed over between UMTS and GSM, a mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed. The mapping described here is applicable to the BSSMAP protocol even when used inside MAP in the E-interface. + +The mapping between the cause codes received in RANAP Relocation Required and the cause codes sent in BSSMAP Handover Request is as follows: + +| 25.413 | 48.008 | Notes | +|-----------------------------------------|------------------------------|-------| +| RELOCATION REQUIRED | HANDOVER REQUEST | | +| -Time critical relocation | -'uplink quality' | | +| -Resource optimisation relocation | -Traffic | | +| -Relocation desirable for radio reasons | -Better cell | | +| -Directed retry | -Directed retry | | +| -Reduce Load in serving cell | -Reduce Load in serving cell | | +| -Any other value | -Better cell | | + +The mapping between the cause codes received in RANAP Relocation Cancel and the cause codes sent in BSSMAP Clear Command is as follows: + +| 25.413 | 48.008 | Notes | +|-----------------------------------|----------------------------------------------------|-------| +| RELOCATION CANCEL | CLEAR COMMAND | | +| -Trelocprepexpiry | -Radio interface failure, reversion to old channel | | +| -Interaction with other procedure | -Radio interface failure, reversion to old channel | | +| -Any other value | -Radio interface failure, reversion to old channel | | + +The mapping between the cause codes received in BSSMAP Handover Failure and the cause codes sent in RANAP Relocation Preparation Failure is as follows: + +| 48.008 | 25.413 | Notes | +|-----------------------------------------------------------------|-------------------------------------------------------------------|-------| +| HANDOVER FAILURE | RELOCATION PREP. FAILURE | | +| -Ciphering algorithm not supported | -Requested ciphering and/or integrity protection is not supported | | +| -Circuit pool mismatch | | 1 | +| -Equipment failure | -Relocation failure in Target CN/RNC or target system | | +| -Invalid message contents | -Abstract Syntax Error | | +| -No radio resource available | -No Radio Resources Available in Target Cell | | +| -O and M intervention | -O and M intervention | 2 | +| -Radio interface failure, reversion to old channel | | | +| -Radio interface message failure | -Relocation failure in Target CN/RNC or target system | | +| -Requested speech version unavailable | -Relocation failure in Target CN/RNC or target system | | +| -Requested terrestrial resource unavailable | -Relocation failure in Target CN/RNC or target system | | +| -Requested transcoding/rate adaption unavailable | -Relocation failure in Target CN/RNC or target system | | +| -Switch circuit pool | | 1 | +| -Terrestrial circuit already allocated | -Relocation failure in Target CN/RNC or target system | | +| -Traffic load in the target cell higher than in the source cell | -Traffic load in the target cell higher than in the source cell | | +| -Any other value | -Relocation failure in Target CN/RNC or target system | | + +NOTE 1: Cause code not used at inter-system handover. + +NOTE 2: Cause code not applicable to this traffic case. + +The mapping between the cause codes received in BSSMAP Clear Request and the cause codes sent in RANAP Iu Release Request is as follows: + +| 48.008 | 25.413 | Notes | +|-------------------------------------------|-------------------------------------------------------|-------| +| CLEAR REQUEST | IU RELEASE REQUEST | | +| -Radio interface message failure | -Relocation failure in Target CN/RNC or target system | | +| -O and M intervention | -O and M intervention | | +| -Equipment failure | -Relocation failure in Target CN/RNC or target system | | +| -Joined group call channel | -Unspecified failure | | +| -Protocol failure between BSS and MSC | -Message not compatible with receiver state | | +| -Preemption | -RAB pre-empted | | +| -Access restricted due to shared networks | -Access restricted due to shared networks | | +| -Any other value | -Relocation failure in Target CN/RNC or target system | | + +## 4.7 Inter-MSC Handover (GSM to UMTS) + +The general principles of the handover procedures are given in 3GPP TS 23.009 [2]. 3GPP TS 29.010 gives the necessary information for interworking between the 3GPP TS 25.413 [7] RANAP protocol, GSM handover procedures and the 3GPP TS 29.002 [9] MAP protocol. The RANAP protocol is used between the RNS and the 3G\_MSC. + +The following four principles apply for the Inter-MSC handover GSM to UMTS: + +The BSSMAP parameters required for Inter-MSC handover GSM to UMTS are generated as in GSM. + +Received RANAP parameters, e.g. cause code or transparent container, are mapped to the appropriate BSSMAP parameters, e.g. cause code or Handover command. + +The RANAP parameters required for Inter-MSC handover GSM to UMTS are generated from received or stored GSM parameters. + +When new parameters need to be added for transfer on the E-interface, the principles stated in the beginning of clause 4.5 shall be followed. + +### 4.7.1 Basic Inter-MSC Handover + +When a Mobile Station is handed over between two MSCs, the establishment of a connection between them (described in 3GPP TS 23.009 [2]) requires interworking between A-Interface, Iu-Interface and E-Interface. + +The signalling at initiation, execution and completion of the Basic Inter-MSC handover procedure is shown in figures 37 to 42 with both possible positive or negative outcomes. + +Additionally figure 37b shows the possible interworking when the trace related message is transparently transferred on the E-Interface at Basic Inter-MSC Handover initiation. + +![Sequence diagram for Basic Inter-MSC Handover initiation (no trace related messages transferred).](a9fa8656fd01e4e407bc91dba6ac0ad5_img.jpg) + +``` + +BSS-A MSC-A 3G-MSC-B + | | | + | HANDOVER | | + | REQUIRED | | + |----------------->| MAP PREPARE HANDOVER | + | |---------------------------->| +-----------------+ + | | request | | Possible Alloc. | + | | | | of a handover | + | | | | no. in the VLR-B| + | | | +-----------------+ + | | | | + | | | RNS-B + | | | | + | | | RELOCATION REQUEST + | | |---------------->| + +``` + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + + BSS-A->>MSC-A: HANDOVER REQUIRED + MSC-A->>3G-MSC-B: MAP PREPARE HANDOVER request + Note over 3G-MSC-B: Possible Alloc. of a handover no. in the VLR-B + 3G-MSC-B->>RNS-B: RELOCATION REQUEST + +``` + +Sequence diagram for Basic Inter-MSC Handover initiation (no trace related messages transferred). + +**Figure 37a: Signalling for Basic Inter-MSC Handover initiation (no trace related messages transferred)** + +![Sequence diagram for Basic Inter-MSC Handover initiation (CN invoke trace message transferred).](a837cac1f7bd531da90c4dfb9474ccb3_img.jpg) + +``` + +BSS-A MSC-A 3G-MSC-B + | (*) | + | HANDOVER | | + | REQUIRED | | + |----------------->| MAP PREPARE HANDOVER | + | |---------------------------->| +-----------------+ + | | request (**) | | Possible Alloc. | + | | | | of a handover | + | | | | no. in the VLR-B| + | | | +-----------------+ + | | | | + | | | RNS-B + | | | | + | | | RELOCATION REQUEST + | | |---------------->| + | | | | + | | | CN INVOKE TRACE | + | | |----------------> (***) + +``` + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + + BSS-A->>MSC-A: HANDOVER REQUIRED + Note over MSC-A: (*) + MSC-A->>3G-MSC-B: MAP PREPARE HANDOVER request (**) + Note over 3G-MSC-B: Possible Alloc. of a handover no. in the VLR-B + 3G-MSC-B->>RNS-B: RELOCATION REQUEST + 3G-MSC-B->>RNS-B: CN INVOKE TRACE (***) + +``` + +Sequence diagram for Basic Inter-MSC Handover initiation (CN invoke trace message transferred). + +**Figure 37b: Signalling for Basic Inter-MSC Handover initiation (CN invoke trace message transferred)** + +- (\*): Tracing invocation has been received from VLR. +- (\*\*): In that case, HANDOVER REQUEST and MSC INVOKE TRACE messages are included within the AN-apdu parameter. +- (\*\*\*): CN INVOKE TRACE is forwarded to RNS-B if supported by 3G\_MSC-B. + +Possible Positive outcomes: successful radio resources allocation and handover number allocation (if performed): + +![Sequence diagram for Figure 38: Signalling for Basic Inter-MSC Handover execution (Positive outcome).](3c04b14104f95eb8f7100f6d497d956e_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + 3G-MSC-B->>RNS-B: RELOCATION REQUEST + RNS-B-->>3G-MSC-B: ACKNOWLEDGE LOCATION REPORTING CONTROL + 3G-MSC-B-->>MSC-A: MAP PREPARE HANDOVER response + MSC-A-->>BSS-A: HANDOVER COMMAND + +``` + +Sequence diagram for Figure 38: Signalling for Basic Inter-MSC Handover execution (Positive outcome). + +**Figure 38: Signalling for Basic Inter-MSC Handover execution (Positive outcome)** + +Possible Negative outcomes: + +- a) user error detected, or handover number allocation unsuccessful (if performed), or component rejection or dialogue abortion performed by 3G\_MSC-B: + +![Sequence diagram for Negative outcome a: user error detected, or handover number allocation unsuccessful (if performed), or component rejection or dialogue abortion performed by 3G_MSC-B.](4d8ec886ccb5f4f6d90fe2c8d0c118bd_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + 3G-MSC-B-->>MSC-A: MAP PREPARE HANDOVER response negative result, MAP CLOSE + 3G-MSC-B-->>MSC-A: MAP U/P-ABORT + MSC-A-->>BSS-A: HANDOVER REQUIRED REJECT (Note 1) + +``` + +Sequence diagram for Negative outcome a: user error detected, or handover number allocation unsuccessful (if performed), or component rejection or dialogue abortion performed by 3G\_MSC-B. + +- b) radio resources allocation failure: + +![Sequence diagram for Negative outcome b: radio resources allocation failure.](7913c315e0db8233cb1ac2455e4a0a81_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + RNS-B-->>3G-MSC-B: RELOCATION FAILURE + 3G-MSC-B-->>MSC-A: MAP PREPARE HANDOVER response + MSC-A-->>BSS-A: HANDOVER REQUIRED REJECT (Note 1) + +``` + +Sequence diagram for Negative outcome b: radio resources allocation failure. + +- c) unsuccessful handover execution (Reversion to the old radio resources): + +![Sequence diagram for Figure 39: Signalling for Basic Inter-MSC Handover execution (Negative outcomes).](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + BSS-A->>MSC-A: HANDOVER FAILURE + MSC-A->>3G-MSC-B: MAP U -ABORT + 3G-MSC-B->>RNS-B: IU RELEASE COMMAND + +``` + +Sequence diagram for Figure 39: Signalling for Basic Inter-MSC Handover execution (Negative outcomes). + +**Figure 39: Signalling for Basic Inter-MSC Handover execution (Negative outcomes)** + +NOTE 1: Possible rejection of the handover because of the negative outcome of MAP or RANAP procedure. + +![Sequence diagram for Figure 40: Signalling for Basic Inter-MSC Handover completion.](a4bfa2343d75076b79f7e33d93915e00_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + RNS-B->>3G-MSC-B: RELOCATION COMPLETE + 3G-MSC-B->>MSC-A: MAP SEND END SIGNAL request + MSC-A->>BSS-A: CLEAR COMMAND + +``` + +Sequence diagram for Figure 40: Signalling for Basic Inter-MSC Handover completion. + +**Figure 40: Signalling for Basic Inter-MSC Handover completion** + +Positive outcome: + +![Sequence diagram for Figure 41: Signalling for Basic Inter-MSC Handover completion (Positive outcome).](ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + MSC-A->>3G-MSC-B: MAP SEND END SIGNAL response + 3G-MSC-B->>RNS-B: IU RELEASE COMMAND (Note 2) + +``` + +Sequence diagram for Figure 41: Signalling for Basic Inter-MSC Handover completion (Positive outcome). + +**Figure 41: Signalling for Basic Inter-MSC Handover completion (Positive outcome)** + +Negative outcome: + +![Sequence diagram for Figure 42: Signalling for Basic Inter-MSC Handover completion (Negative outcome).](a1dc2b799cd6ca93414adab971763c3e_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + MSC-A->>3G-MSC-B: MAP U/P -ABORT + 3G-MSC-B->>RNS-B: IU RELEASE COMMAND + +``` + +Sequence diagram for Figure 42: Signalling for Basic Inter-MSC Handover completion (Negative outcome). + +**Figure 42: Signalling for Basic Inter-MSC Handover completion (Negative outcome)** + +NOTE 2: From interworking between MAP and RANAP point of view, when the call is released. + +![Sequence diagram for Figure 42a: Signalling for updating of anchor MSC after change of location in RNS.](695068a37ee8ec4b395658c3ff2209f2_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B + participant RNS-B + RNS-B->>3G-MSC-B: LOCATION REPORT + 3G-MSC-B->>MSC-A: MAP PROCESS ACCESS SIGNALLING + +``` + +Sequence diagram for Figure 42a: Signalling for updating of anchor MSC after change of location in RNS. + +**Figure 42a: Signalling for updating of anchor MSC after change of location in RNS** + +The handover procedure is normally triggered by BSS-A by sending a HANDOVER REQUIRED message on A-Interface to MSC-A. The invocation of the Basic Inter-MSC handover procedure is performed and controlled by MSC-A. The sending of the MAP Prepare-Handover request to 3G\_MSC-B is triggered in MSC-A upon receipt of the HANDOVER REQUIRED message. The identity of the target RNC where the call is to be handed over in 3G\_MSC-B area, provided in the HANDOVER REQUIRED message in the information element Cell Identifier List (Preferred), is + +mapped to the target RNC Id MAP parameter and the HANDOVER REQUEST message is encapsulated in the an-APDU MAP parameter of the Prepare-Handover MAP request. 3G\_MSC-B can invoke another operation towards the VLR-B (allocation of the handover number described in 3GPP TS 29.002 [9]). + +Additionally, if tracing activity has been invoked, the trace related message can be transferred on the E-Interface encapsulated in the an-APDU MAP parameter of the Prepare-Handover Request. If transferred, one complete trace related message at a time shall be included in the an-APDU MAP parameter after the HANDOVER REQUEST message. Note: UMTS supports only CN initiated tracing. + +The interworking between Prepare Handover and HANDOVER REQUIRED is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Forward message | HANDOVER REQUIRED
BSSMAP information elements
GERAN classmark | MAP PREPARE HANDOVER request
-ho-NumberNotRequired
-target RNC Id
-IMSI
-Integrity protection info
-Encryption info
-an-APDU(
HANDOVER REQUEST,
MSC INVOKE TRACE)
-GERAN classmark | 1
2
3
4
7 | +| Positive result | | MAP PREPARE HANDOVER response
-handover number
-an-APDU(
HANDOVER REQUEST
ACKNOWLEDGE or
HANDOVER FAILURE) | 5 | +| Negative result | HANDOVER REQUIRED REJECT
equipment failure
equipment failure
equipment failure
equipment failure
equipment failure
equipment failure | MAP PREPARE HANDOVER
System Failure
NO Handover Number
available
UnexpectedDataValue
Data Missing
MAP CLOSE
MAP U/P -ABORT | 6 | + +NOTE 1: The ho-NumberNotRequired parameter is included by MSC-A, when MSC-A decides not to use any circuit connection with 3G\_MSC-B. No handover number shall be present in the positive result. Any negative response from 3G\_MSC-B shall not be due to handover number allocation problem. + +NOTE 2: Integrity protection information, encryption information and IMSI parameters are included by MSC-A, only when the MSC-A uses 29.002 as per release 99. These IEs are not included if the MSC-A is R98 or earlier. + +NOTE 3: The process performed on the BSSMAP information elements received in the HANDOVER REQUIRED message is described in the 3GPP TS 48.008 [12]. + +NOTE 4: The process performed on the BSSMAP information elements received in the MSC INVOKE TRACE message is described in clause 4.5.5.6. + +NOTE 5: The response to the Prepare-Handover request can include in its an-APDU parameter, identifying the 3GPP TS 48.006 protocol, either a BSSMAP HANDOVER REQUEST ACKNOWLEDGE or a BSSMAP HANDOVER FAILURE. + +In the first case, the positive result triggers in MSC-A the sending on A-Interface of the HANDOVER COMMAND. + +In the second case, the positive result triggers in MSC-A optionally the sending of the HANDOVER REQUIRED REJECT. + +(The possible sending of the HANDOVER REQUIRED REJECT message upon receipt of the HANDOVER FAILURE is out of the scope of 3GPP TS 29.010 and lies in 3GPP TS 48.008 [12]). + +NOTE 6: The possible sending of the HANDOVER REQUIRED REJECT message is described in 3GPP TS 48.008 [12]. + +NOTE 7: If the GERAN Classmark was not received with the HANDOVER REQUIRED message initiating the handover, MSC-A shall include any previously received GERAN Classmark. See 3GPP TS 43.051 [17]. + +The interworking between Prepare Handover and RELOCATION REQUEST in 3G\_MSC-B is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| Forward message | MAP PREPARE HANDOVER request
- ho-NumberNotRequired
- target RNC Id
- IMSI
- Integrity protection info
- Encryption info
- RANAP service handover
- UESBI
- an-APDU(
HANDOVER REQUEST,
MSC INVOKE TRACE)

BSSMAP information elements:

Channel Type
Cause
sRNC to tRNC container
SNA Access Information | RELOCATION REQUEST

RANAP information elements:

RAB parameters
Cause
sRNC to tRNC container
SNA Access Information

info stored/generated
in/by 3G MSC-B:
CN domain indicator | 1












3 | +| Positive result | MAP PREPARE HANDOVER response
- an-APDU(
HANDOVER REQUEST ACK)

BSSMAP information elements:

Layer 3 info | RELOCATION REQUEST ACK

RANAP information elements:

tRNC to sRNC container | | +| Negative result | MAP PREPARE HANDOVER response
- an-APDU(
HANDOVER FAILURE)
BSSMAP information elements:

GERAN classmark | RELOCATION FAILURE

RANAP information elements:

GERAN classmark |












2 | + +NOTE 1: Integrity protection information, encryption information, IMSI and RANAP service handover parameters are included by MSC-A only when the MSC-A uses 29.002 as per release 99. These IEs are not included if the MSC-A is R98 or earlier. + +NOTE 2: If a handover to GERAN Iu-mode failed, the target RNS may include a GERAN classmark in the RELOCATION FAILURE message. See 3GPP TS 43.051 [17]. + +NOTE 3: SNA Access Information parameter is included by MSC-A only when the MSC-A uses 29.002 as per release 5. This IE is not included if the MSC-A is release 4 or earlier. + +The interworking between Send End Signal and RELOCATION COMPLETE in 3G\_MSC-B is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|--------------------------------------------------------------------|---------------------------------|-------| +| Forward message | RELOCATION COMPLETE MAP SEND END SIGNAL request | -an-APDU(
HANDOVER COMPLETE) | | +| Positive result | IU RELEASE COMMAND MAP SEND END SIGNAL response
-Normal release | | 1 | +| Negative result | IU RELEASE COMMAND
-Normal release | MAP CLOSE
MAP U/P -ABORT | 2 | + +NOTE 1: The positive empty result triggers the clearing of the Radio Resources on the Iu-Interface and the release of the SCCP connection between 3G\_MSC-B and RNS-B. If a circuit connection is used between MSC-A and 3G\_MSC-B, the 'Normal release' clearing cause shall only be given to RNS-B when 3G\_MSC-B has received a clearing indication on its circuit connection with MSC-A. + +NOTE 2: The abortion of the dialogue or the rejection of the component triggers in 3G\_MSC-B the clearing of its circuit connection with MSC-A, if any, of the Radio Resources on the Iu-Interface and the release of the SCCP connection between 3G\_MSC-B and RNS-B. + +The interworking between Send End Signal and CLEAR COMMAND in MSC-A is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|----------------------------------------------------------------|-------------------------------------------|-------| +| Forward message | MAP SEND END SIGNAL request
-an-APDU(
HANDOVER COMPLETE) | CLEAR COMMAND
- Handover
Successful | | +| Positive result | | | | +| Negative result | | | | + +The interworking between HANDOVER FAILURE in case of reversion to old channel of the MS and User Abort in MSC-A is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|---------------------------------------------------|--------------|-------| +| Forward message | HANDOVER FAILURE
- Reversion to old
channel | MAP U -ABORT | | +| Positive result | | | | +| Negative result | | | | + +### 4.7.2 Subsequent Inter-MSC Handover from MSC-B back to 3G\_MSC-A + +When a Mobile Station is being handed over back to 3G\_MSC-A, the procedure (described in 3GPP TS 23.009 [2]) requires interworking between A-Interface, Iu-Interface and E-Interface. + +The signalling at initiation, execution and completion of the Subsequent Inter-MSC handover procedure is shown in figures 43 to 47. + +![Figure 43: Signalling for Subsequent Inter-MSC Handover back to 3G_MSC-A initiation](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant 3G-MSC-A + participant RNS-B + Note over BSS-A, MSC-B: HANDOVER REQUIRED + BSS-A->>MSC-B: + Note over MSC-B, 3G-MSC-A: MAP PREPARE SUBSEQUENT + Note over MSC-B, 3G-MSC-A: HANDOVER request + MSC-B->>3G-MSC-A: + Note over 3G-MSC-A, RNS-B: RELOCATION REQUEST + 3G-MSC-A->>RNS-B: + +``` + +Figure 43: Signalling for Subsequent Inter-MSC Handover back to 3G\_MSC-A initiation + +**Figure 43: Signalling for Subsequent Inter-MSC Handover back to 3G\_MSC-A initiation** + +Possible Positive outcomes: successful radio resources allocation: + +![Figure 44: Signalling for Subsequent Inter-MSC Handover back to 3G_MSC-A execution (Positive outcome)](9e26cd5584f423e1b2155fb341db579f_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant 3G-MSC-A + participant RNS-B + Note over 3G-MSC-A, RNS-B: RELOCATION REQUEST + Note over 3G-MSC-A, RNS-B: ACKNOWLEDGE + RNS-B-->>3G-MSC-A: + Note over MSC-B, 3G-MSC-A: MAP PREPARE SUBSEQUENT + Note over MSC-B, 3G-MSC-A: HANDOVER response + 3G-MSC-A-->>MSC-B: + Note over BSS-A, MSC-B: HANDOVER COMMAND + MSC-B-->>BSS-A: + +``` + +Figure 44: Signalling for Subsequent Inter-MSC Handover back to 3G\_MSC-A execution (Positive outcome) + +**Figure 44: Signalling for Subsequent Inter-MSC Handover back to 3G\_MSC-A execution (Positive outcome)** + +Possible Negative outcomes: + +a) user error detected, or component rejection or dialogue abortion performed by 3G\_MSC-A: + +![Sequence diagram for negative outcome (a)](a04291a026e9ac4a7b644e556a0672b4_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant 3G-MSC-A + participant RNS-B + Note over MSC-B, 3G-MSC-A: MAP PREPARE SUBSEQUENT HANDOVER + MSC-B->>3G-MSC-A: + Note over MSC-B, 3G-MSC-A: response negative result + 3G-MSC-A-->>MSC-B: + Note over BSS-A, MSC-B: HANDOVER REQUIRED + Note over BSS-A, MSC-B: REJECT (Note 1) + MSC-B-->>BSS-A: + +``` + +Sequence diagram for negative outcome (a) + +b) component rejection or dialogue abortion performed by 3G\_MSC-A: + +![Sequence diagram for negative outcome (b)](a02b188a5fd52c99f84255322873bf29_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant 3G-MSC-A + participant RNS-B + Note over MSC-B, 3G-MSC-A: MAP CLOSE, MAP U/P ABORT + 3G-MSC-A-->>MSC-B: + Note over BSS-A, MSC-B: CLEAR COMMAND + MSC-B-->>BSS-A: + +``` + +Sequence diagram for negative outcome (b) + +c) radio resources allocation failure: + +![Sequence diagram for negative outcome (c)](a3c1310e720178d2450a3748c7c75422_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant 3G-MSC-A + participant RNS-B + Note over MSC-B, 3G-MSC-A: MAP PREPARE SUBSEQUENT + MSC-B->>3G-MSC-A: + Note over 3G-MSC-A, RNS-B: RELOCATION FAILURE + RNS-B-->>3G-MSC-A: + Note over MSC-B, 3G-MSC-A: HANDOVER response + 3G-MSC-A-->>MSC-B: + Note over BSS-A, MSC-B: HANDOVER REQUIRED + Note over BSS-A, MSC-B: REJECT (Note 1) + MSC-B-->>BSS-A: + +``` + +Sequence diagram for negative outcome (c) + +d) unsuccessful relocation execution (reversion to the old radio resources): + +![Sequence diagram for Figure 45: Signalling for Subsequent Inter-MSC Handover back to 3G_MSC-A execution (Negative outcome).](343e05a9fd8a8c8743428fa4ae6e2736_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant 3G-MSC-A + participant RNS-B + Note over BSS-A: HANDOVER +FAILURE + BSS-A->>MSC-B: + MSC-B->>3G-MSC-A: MAP PROCESS ACCESS + Note over MSC-B,3G-MSC-A: SIGNALLING request + 3G-MSC-A->>RNS-B: IU RELEASE COMMAND + +``` + +Sequence diagram for Figure 45: Signalling for Subsequent Inter-MSC Handover back to 3G\_MSC-A execution (Negative outcome). + +**Figure 45: Signalling for Subsequent Inter-MSC Handover back to 3G\_MSC-A execution (Negative outcome)** + +NOTE 1: Possible rejection of the handover because of the negative outcome of MAP or BSSMAP procedure. + +![Sequence diagram for Figure 46: Signalling for Subsequent Inter-MSC Handover back to 3G_MSC-A completion (Successful completion of the procedure).](ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg) + +``` + +sequenceDiagram + participant RNS-B + participant 3G-MSC-A + participant MSC-B + participant BSS-A + Note over RNS-B: RELOCATION +COMPLETE + RNS-B->>3G-MSC-A: + 3G-MSC-A->>MSC-B: MAP SEND END SIGNAL + Note over 3G-MSC-A,MSC-B: response + MSC-B->>BSS-A: CLEAR COMMAND + +``` + +Sequence diagram for Figure 46: Signalling for Subsequent Inter-MSC Handover back to 3G\_MSC-A completion (Successful completion of the procedure). + +**Figure 46: Signalling for Subsequent Inter-MSC Handover back to 3G\_MSC-A completion (Successful completion of the procedure)** + +NOTE: Positive outcome case shown in figure 41. + +![Sequence diagram for Figure 47: Signalling for Subsequent Inter-MSC Handover back to 3G_MSC-A completion (Unsuccessful completion of the procedure).](01465752f3ac36c403672804f406a676_img.jpg) + +``` + +sequenceDiagram + participant RNS-B + participant 3G-MSC-A + participant MSC-B + participant BSS-A + Note over 3G-MSC-A: MAP U/P -ABORT + 3G-MSC-A->>MSC-B: + MSC-B->>BSS-A: CLEAR COMMAND + Note over MSC-B,BSS-A: (Note 1) + +``` + +Sequence diagram for Figure 47: Signalling for Subsequent Inter-MSC Handover back to 3G\_MSC-A completion (Unsuccessful completion of the procedure). + +**Figure 47: Signalling for Subsequent Inter-MSC Handover back to 3G\_MSC-A completion (Unsuccessful completion of the procedure)** + +NOTE 1: Abnormal end of the procedure that triggers the clearing of all resources in MSC-B. + +The interworking between Prepare Subsequent Handover and HANDOVER REQUIRED is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| Forward message | HANDOVER REQUIRED MAP PREPARE

BSSMAP information elements

GERAN classmark | SUBSEQUENT HANDOVER request

-target MSC number
-target RNC Id
-an-APDU(
HANDOVER REQUEST)
-GERAN classmark | 1



4 | +| Positive result | HANDOVER REQUIRED MAP PREPARE | SUBSEQUENT HANDOVER response
-an-APDU(
HANDOVER REQUEST
ACKNOWLEDGE or
HANDOVER FAILURE) | 2 | +| Negative result | HANDOVER REQUIRED REJECT

equipment failure
equipment failure

equipment failure
equipment failure

CLEAR COMMAND

equipment failure
equipment failure | MAP PREPARE SUBSEQUENT HANDOVER response
Unknown MSC
Subsequent Handover Failure
UnexpectedDataValue
Data Missing



MAP CLOSE
MAP U/P -ABORT | 3 | + +NOTE 1: The processing performed on the BSSMAP information elements received in the HANDOVER REQUIRED message is out of the scope of the present document. The target MSC number is provided to 3G\_MSC-A by MSC-B based on the information received from RNS-B. + +NOTE 2: The response to the Prepare-Subsequent-Handover request can include in its an-APDU parameter, identifying the 3GPP TS 48.006 protocol, either a BSSMAP HANDOVER REQUEST ACKNOWLEDGE or a BSSMAP HANDOVER FAILURE. + +In the first case, the positive result triggers in MSC-B the sending on A-Interface of the HANDOVER COMMAND. + +In the second case, the positive result triggers in MSC-B optionally the sending of the HANDOVER REQUIRED REJECT. + +(The possible sending of the HANDOVER REQUIRED REJECT message upon receipt of the HANDOVER FAILURE is out of the scope of 3GPP TS 29.010 and lies in 3GPP TS 48.008 [12]). + +NOTE 3: The possible sending of the HANDOVER REQUIRED REJECT message is described in 3GPP TS 48.008 [12]. + +NOTE 4: If the GERAN Classmark was not received with the HANDOVER REQUIRED message initiating the handover, MSC-B shall include any previously received GERAN Classmark. See 3GPP TS 43.051 [17]. + +The interworking between Prepare Subsequent Handover and RELOCATION REQUEST in 3G\_MSC-A is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP PREPARE SUB HANDOVER request
- ho-NumberNotRequired
- target RNC ID
- an-APDU(
HANDOVER REQUEST,
MSC INVOKE TRACE)

BSSMAP information elements:
Cause
sRNC to tRNC container | RELOCATION REQUEST

RANAP information elements:
Cause
sRNC to tRNC container

info stored/generated
in/by 3G MSC-A:
CN domain indicator
RAB parameters
Permanent NAS UE id
Encryption info
Integrity protection
info | | +| Positive result | MAP PREPARE SUB HANDOVER response
- an-APDU(
HANDOVER REQUEST ACK)

BSSMAP information elements:
Layer 3 info | RELOCATION REQUEST ACK

RANAP information elements:
tRNC to sRNC container | | +| Negative result | MAP SUB PREPARE HANDOVER response
- an-APDU(
HANDOVER FAILURE)

BSSMAP information elements:
GERAN classmark | RELOCATION FAILURE

RANAP information elements:
GERAN classmark | 1 | + +NOTE 1: If a handover to GERAN lu-mode failed, the target RNS may include a GERAN classmark in the RELOCATION FAILURE message. See 3GPP TS 43.051 [17]. + +The interworking between HANDOVER FAILURE and MAP Process Signalling Request in 3G\_MSC-B is as follows: + +| | 48.008 | 29.002 | Notes | +|-----------------|------------------|-------------------------------------------------------------------|-------| +| Forward message | HANDOVER FAILURE | MAP PROCESS-SIGNALLING request
- an-APDU(
HANDOVER FAILURE) | | +| Positive result | | | | +| Negative result | | | | + +The interworking between Send End Signal Response and RELOCATION COMPLETE in 3G\_MSC-A is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|---------------------|------------------------------|-------| +| Forward message | RELOCATION COMPLETE | MAP SEND END SIGNAL response | | +| Positive result | | | | +| Negative result | | MAP U/P -ABORT | 1 | + +NOTE 1: The abortion of the dialogue ends the handover procedure with MSC-B. + +### 4.7.3 Subsequent Inter-MSC Handover to third MSC + +When a Mobile Station is being handed over to a third MSC, the procedure (described in 3GPP TS 23.009 [2]) does require one specific interworking case in MSC-A (figure 49) between E-Interface from MSC-B and E-Interface from 3G\_MSC-B' other than the combination of the ones described in the clause 4.5.1 and 4.7.2. + +![Sequence diagram for Subsequent Inter-MSC Handover to third MSC (3G_MSC-B') initiation. The diagram shows four lifelines: BSS-A, MSC-B, MSC-A, and 3G-MSC-B'. The sequence starts with BSS-A sending a HANDOVER REQUIRED message to MSC-B. MSC-B then sends a MAP PREPARE SUBSEQUENT message to MSC-A, which is also labeled as a HANDOVER request. MSC-A then sends a MAP PREPARE message to 3G-MSC-B', which is also labeled as a HANDOVER request. 3G-MSC-B' contains a nested box with 'Possib. Alloc. of ho. number VLR-B' and 'RNS-B'' inside. Finally, 3G-MSC-B' sends a RELOCATION REQUEST message back to MSC-A.](b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant 3G-MSC-B' + + Note right of 3G-MSC-B': Possib. +Alloc. +of ho. +number +VLR-B + Note right of 3G-MSC-B': RNS-B' + + BSS-A->>MSC-B: HANDOVER REQUIRED + MSC-B->>MSC-A: MAP PREPARE SUBSEQUENT +HANDOVER request + MSC-A->>3G-MSC-B': MAP PREPARE +HANDOVER request + 3G-MSC-B'->>MSC-A: RELOCATION REQUEST + +``` + +Sequence diagram for Subsequent Inter-MSC Handover to third MSC (3G\_MSC-B') initiation. The diagram shows four lifelines: BSS-A, MSC-B, MSC-A, and 3G-MSC-B'. The sequence starts with BSS-A sending a HANDOVER REQUIRED message to MSC-B. MSC-B then sends a MAP PREPARE SUBSEQUENT message to MSC-A, which is also labeled as a HANDOVER request. MSC-A then sends a MAP PREPARE message to 3G-MSC-B', which is also labeled as a HANDOVER request. 3G-MSC-B' contains a nested box with 'Possib. Alloc. of ho. number VLR-B' and 'RNS-B'' inside. Finally, 3G-MSC-B' sends a RELOCATION REQUEST message back to MSC-A. + +**Figure 45: Signalling for Subsequent Inter-MSC Handover to third MSC (3G\_MSC-B') initiation** + +Possible Positive outcomes: successful radio resources allocation: + +![Sequence diagram for Figure 46: Signalling for Subsequent Inter-MSC Handover to third MSC (3G_MSC-B') execution (Positive outcome).](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant 3G-MSC-B' + participant RNS-B' + + RNS-B'-->>3G-MSC-B': RELOCATION REQUEST ACKNOWLEDGE + 3G-MSC-B'-->>RNS-B': LOCATION REPORTING CONTROL + MSC-A->>3G-MSC-B': MAP PREPARE HANDOVER + 3G-MSC-B'-->>MSC-A: response + MSC-A->>MSC-B: MAP PREPARE SUBSEQUENT + MSC-B-->>MSC-A: HANDOVER response + MSC-B->>BSS-A: HANDOVER COMMAND + +``` + +Sequence diagram for Figure 46: Signalling for Subsequent Inter-MSC Handover to third MSC (3G\_MSC-B') execution (Positive outcome). + +**Figure 46: Signalling for Subsequent Inter-MSC Handover to third MSC (3G\_MSC-B') execution (Positive outcome)** + +Possible Negative outcomes: + +a) user error detected, or component rejection or dialogue abortion performed by MSC-B': + +![Sequence diagram for Figure 47 (Negative outcome a): Signalling for Subsequent Inter-MSC Handover to third MSC (3G_MSC-B') execution (Negative outcome).](f06d7a2fad72d80fe12fca1b65fc805b_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant 3G-MSC-B' + participant RNS-B' + + MSC-A->>3G-MSC-B': MAP PREPARE HANDOVER + 3G-MSC-B'-->>MSC-A: response negative result + MSC-A->>3G-MSC-B': MAP CLOSE + 3G-MSC-B'-->>MSC-A: MAP U/P -ABORT + MSC-A->>MSC-B: MAP PREPARE SUBSEQUENT + MSC-B-->>MSC-A: HANDOVER response negative result + MSC-B->>BSS-A: HANDOVER REQUIRED REJECT (Note 1) + +``` + +Sequence diagram for Figure 47 (Negative outcome a): Signalling for Subsequent Inter-MSC Handover to third MSC (3G\_MSC-B') execution (Negative outcome). + +b) radio resources allocation failure: + +![Sequence diagram for Figure 47 (Negative outcome b): Signalling for Subsequent Inter-MSC Handover to third MSC (3G_MSC-B') execution (Negative outcome).](854cb86f664ff62fd23e7607cfeb5727_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant 3G-MSC-B' + participant RNS-B' + + RNS-B'-->>3G-MSC-B': RELOCATION FAILURE + MSC-A->>3G-MSC-B': MAP PREPARE HANDOVER + 3G-MSC-B'-->>MSC-A: response + MSC-A->>MSC-B: MAP PREPARE SUBSEQUENT + MSC-B-->>MSC-A: HANDOVER response + MSC-B->>BSS-A: HANDOVER REQUIRED REJECT (Note 1) + +``` + +Sequence diagram for Figure 47 (Negative outcome b): Signalling for Subsequent Inter-MSC Handover to third MSC (3G\_MSC-B') execution (Negative outcome). + +**Figure 47: Signalling for Subsequent Inter-MSC Handover to third MSC (3G\_MSC-B') execution (Negative outcome)** + +NOTE 1: Possible rejection of the handover because of the negative outcome of MAP or BSSMAP procedure. + +Positive outcome: + +![Sequence diagram for Figure 48: Signalling for Subsequent Inter-MSC Handover to third MSC (3G_MSC-B') completion (Successful completion of the procedure).](aa6e28822419dba9f22129fee66c9c4c_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant 3G-MSC-B' + participant RNS-B' + + Note right of RNS-B': RELOCATION COMPLETE + RNS-B'->>3G-MSC-B': RELOCATION COMPLETE + 3G-MSC-B'-->>MSC-A: MAP SEND END SIGNAL request + MSC-A-->>MSC-B: MAP SEND END SIGNAL response + MSC-B-->>BSS-A: CLEAR COMMAND + +``` + +Sequence diagram for Figure 48: Signalling for Subsequent Inter-MSC Handover to third MSC (3G\_MSC-B') completion (Successful completion of the procedure). + +**Figure 48: Signalling for Subsequent Inter-MSC Handover to third MSC (3G\_MSC-B') completion (Successful completion of the procedure)** + +Negative outcome: + +![Sequence diagram for Figure 49: Signalling for Subsequent Inter-MSC Handover to third MSC (3G_MSC-B') completion (Unsuccessful completion of the procedure).](007fefafb4fcbdb7d388209f63a0ba5d_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-B + participant MSC-A + participant 3G-MSC-B' + participant RNS-B' + + BSS-A-->>MSC-B: HANDOVER FAILURE + MSC-B-->>MSC-A: MAP PROCESS ACCESS SIGNALLING request (Note 1) + MSC-A-->>3G-MSC-B': MAP U -ABORT + 3G-MSC-B'-->>RNS-B': IU RELEASE COMMAND + +``` + +Sequence diagram for Figure 49: Signalling for Subsequent Inter-MSC Handover to third MSC (3G\_MSC-B') completion (Unsuccessful completion of the procedure). + +**Figure 49: Signalling for Subsequent Inter-MSC Handover to third MSC (3G\_MSC-B') completion (Unsuccessful completion of the procedure)** + +NOTE: Specific interworking case detailed below. + +![Sequence diagram for Figure 49a: Signalling for updating of anchor MSC after change of location in RNS.](1ae16a393229b439c7b3f8b2e63d8d6c_img.jpg) + +``` + +sequenceDiagram + participant BSS-A + participant MSC-A + participant 3G-MSC-B' + participant RNS-B' + + MSC-A-->>3G-MSC-B': MAP PROCESS ACCESS SIGNALLING + 3G-MSC-B'-->>RNS-B': LOCATION REPORT + +``` + +Sequence diagram for Figure 49a: Signalling for updating of anchor MSC after change of location in RNS. + +**Figure 49a: Signalling for updating of anchor MSC after change of location in RNS** + +The specific interworking case in MSC-A compared to the clauses 4.5.1 and 4.7.2 occurs between HANDOVER FAILURE encapsulated in a Process Access Signalling from MSC-B and the abortion of the dialogue with 3G\_MSC-B' in the case of a reversion to old channel of the MS: + +| | 29.002 | 29.002 | Notes | +|-----------------|----------------------------------------------------------------|----------------|-------| +| Forward message | MAP PROCESS-SIGNALLING request
-an-APDU ( HANDOVER FAILURE) | MAP U -ABORT | 1 | +| Positive result | | | | +| Negative result | | MAP U/P -ABORT | 2 | + +NOTE 1: The abortion of the dialogue triggers in 3G\_MSC-B' the clearing of the circuit connection with MSC-A, if any, and of the Resources between 3G\_MSC-B' and RNS-B'. The abortion of the dialogue ends the handover procedure with 3G\_MSC-B'. + +NOTE 2: The abortion of the dialogue ends the handover procedure with MSC-B. + +### 4.7.4 BSSAP Messages transfer on E-Interface + +The handling is described in clause 4.5.4, additional cases are described in this clause. + +#### 4.7.4.1 Assignment + +The interworking between the BSSMAP assignment messages in MAP and the RANAP RAB assignment messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP PREPARE HANDOVER request
-RANAP service handover
-an-APDU ( ASSIGNMENT REQUEST)

BSSMAP information elements:
Channel Type | RAB ASSIGNMENT REQ
Service handover

RANAP information elements:
RAB parameters | | +| Positive result | MAP PREPARE HANDOVER request
-an-APDU ( ASSIGNMENT COMPLETE
or
ASSIGNMENT FAILURE)

BSSMAP information elements:
Cause | RAB ASSIGNMENT RESPONSE
(positive result)
RAB ASSIGNMENT RESPONSE
(negative result)

RANAP information elements:
Cause | 1 | +| Negative result | | MAP U/P -ABORT | | + +NOTE 1: For the mapping between the cause codes see clause 4.7.6. + +#### 4.7.4.2 Cipher Mode Control + +The interworking between the BSSMAP cipher mode messages in MAP and the RANAP security mode messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIGN.
request
-an-APDU(
CIPHER MODE CMD)

BSSMAP information
elements:

Encryption information | SECURITY MODE CMD

RANAP information
elements:

Integrity
protection info
Encryption info | | +| Positive result | MAP PROCESS ACCESS SIGN.
request
-an-APDU(
CIPHER MODE COMPLETE
or
CIPHER MODE REJECT)

BSSMAP information
elements:

Encryption information

Cause | SECURITY MODE
COMPLETE
SECURITY MODE
REJECT

RANAP information
elements:

Integrity
protection info
Encryption info
Cause | 1 | +| Negative result | | MAP U/P -ABORT | | + +NOTE 1: For the mapping between the cause codes see clause 4.7.6. + +#### 4.7.4.3 Location Reporting Control + +The interworking between the RANAP location report message and the BSSMAP handover performed message in MAP is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|-------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | LOCATION REPORT

RANAP information
elements:

Area identity (SAI)
Cause | MAP PROC. ACC. SIGNALLING

-an-APDU(
HANDOVER PERFORMED)

BSSMAP information
elements:

Cell identifier
Cause | | +| Positive result | | | | +| Negative result | | | | + +### 4.7.5 Processing in 3G\_MSC-B, and information transfer on E-interface + +The following parameters require processing (e.g. to store the parameter, to internally generate the parameter) in MSC-B. The relevant BSSMAP procedures are mentioned to ease the comprehension, their detailed description is the scope of 3GPP TS 48.008 [12]. Each BSSMAP message listed in 3GPP TS 49.008 [14] being transferred on E-interface shall use the mechanisms given in clause 4.5.4 and is described in 3GPP TS 48.008 [12]. + +#### 4.7.5.1 Encryption Information + +3G\_MSC-B shall remove algorithms not allowed by 3G\_MSC-B from the list of GSM algorithms received from MSC-A. The modified list of algorithms, the ciphering key and the chosen algorithm shall be stored by 3G\_MSC-B and used for generating the UMTS parameters Encryption Information and Integrity Protection Information if they are not received in MAP Prepare Handover Request (the generation of the UMTS parameters from the GSM parameters is described in TS 33.102). + +Transfer of Information: + +If ciphering has not been performed before Inter-MSC Handover, this will be controlled by MSC-A after the completion of Inter-MSC Handover. + +Ciphering control towards 3G\_MSC-B: + +If Ciphering has been performed before Inter-MSC Handover: + +- in the Handover Request BSSMAP message (information included). + +The Handover Request Acknowledge should in this case NOT contain the indication of the chosen algorithm. + +If Ciphering has NOT been performed before Inter-MSC Handover: + +- in the Cipher Mode Command procedure between MSC-A and 3G\_MSC-B. + +#### 4.7.5.2 Channel Type + +The Channel Type shall be stored by 3G\_MSC-B and used for generating RAB parameters. + +Transfer of Information: + +Independently of the type of resource (Signalling only or traffic channel) assigned to the MS, the Channel Type Information is transferred to 3G\_MSC-B in: + +- the Handover Request BSSMAP message. + +Chosen Channel and/or Speech Version shall NOT be reported back to MSC-A in the Handover Request Acknowledge + +If a new type of resource is to be assigned after Inter-MSC Handover, this can be made with: + +- the BSSMAP Assignment procedure between MSC-A and 3G\_MSC-B. + +#### 4.7.5.3 Classmark + +This information shall be stored by 3G\_MSC-B and might be received from MSC-A. + +Transfer of Information due to Classmark received from MSC-A: + +This information shall be stored by 3G\_MSC-B and is received: + +- in the Handover Request BSSMAP message. + +If a new type of resource is to be assigned after Inter-MSC Handover, Classmark Information MAY be included: + +- in the BSSMAP Assignment procedure. + +#### 4.7.5.4 Priority + +The parameter shall be stored by 3G\_MSC-B and used for generating RAB parameters. It is received as detailed below: + +Transfer of Information: + +Received by 3G\_MSC-B from MSC-A in: + +- the Handover Request BSSMAP message. + +If a change is needed after an Inter-MSC Handover with: + +- the BSSMAP Assignment procedure. + +#### 4.7.5.5 MSC-Invoke Trace Information Elements + +The process to be performed by 3G\_MSC-B on the information elements of the MSC Invoke Trace BSSMAP messages is left for further study. + +Note that MSC-A does not forward BSC Invoke Trace in case of GSM to UMTS handover. + +#### 4.7.5.6 Selected UMTS Algorithm + +A sequence of possible encryption and integrity protection algorithms, received from the 3G\_MSC-A, can be sent to an RNS in Relocation Request or in Security Mode Command in case of cipher mode setting after inter- MSC handover from GSM to UMTS. The RNS chooses one of the listed algorithms and reports this back to the 3G\_MSC in Relocation Request Acknowledge or Security Mode Complete respectively. The MSC-B provides the Selected UMTS algorithm information to the MSC-A. The Selected UMTS algorithms IE in the MAP Process Access Signalling Request and MAP Prepare Handover Response messages refers to the Chosen Integrity Protection Algorithm and Chosen Encryption Algorithm, defined in RANAP specification 3GPP TS 25.413 [7] + +The selected algorithm shall be stored by 3G\_MSC-B, and sent to 3G\_MSC-A. + +Transfer of Information: + +If ciphering has not been performed before Inter- MSC Handover, this will be controlled by 3G\_MSC-A after the completion of Inter- MSC Handover. + +If Ciphering has been performed before Inter- MSC Handover, Selected UMTS algorithm information is received by 3G\_MSC-A from 3G\_MSC-B in: + +- The Prepare Handover Response MAP message. + +If Ciphering has NOT been performed before Inter- MSC Handover, Selected UMTS algorithm information is received by 3G\_MSC-A from 3G\_MSC-B in: + +- The Process Access Signalling Request MAP message. + +#### 4.7.5.7 Allowed UMTS Algorithms + +In case of GSM-subscriber, the Integrity Protection Information and UMTS Encryption Information are not transferred to the MSC-B during inter- MSC handover from GSM to UMTS. Allowed UMTS algorithms is UMTS information that is required in RANAP Relocation Request and RANAP Security Mode Command, and shall be provided by 3G\_MSC-A. 3G\_MSC-B needs this information in case of an inter- MSC GSM to UMTS handover and in subsequent security mode setting, after an inter- MSC GSM to UMTS handover. Therefore 3G\_MSC-A must provide this information in case of an inter- MSC GSM to UMTS handover. The Allowed UMTS algorithms IE in the MAP Prepare Handover and in the MAP Forward Access Signalling Request messages refers to the Permitted Integrity Protection Algorithms in Integrity Protection Information and Permitted Encryption Algorithms in Encryption Information, defined in RANAP specification 3GPP TS 25.413 [7]. + +Allowed UMTS algorithms shall be stored by 3G\_MSC-B. + +Transfer of information: + +If ciphering has not been performed before Inter-MSC Handover, this will be controlled by 3G\_MSC-A after the completion of Inter-MSC Handover. + +Ciphering control towards 3G\_MSC-B: + +If Ciphering has been performed before Inter-MSC Handover: + +- The Prepare Handover Request MAP message. + +If Ciphering has NOT been performed before Inter-MSC Handover: + +- The Forward Access Signalling Request MAP message. + +#### 4.7.5.8 BSSMAP Service Handover + +This information shall be stored by 3G\_MSC-B and sent to a BSS in Handover Request, when 3G\_MSC-B performs handover to GSM. + +Transfer of information: + +The BSSMAP Service Handover information is transferred to 3G\_MSC-B in: + +- the Handover Request BSSMAP message. + +If a new assignment of a TCH after an inter-MSC handover is to be performed, the BSSMAP Service Handover information is transferred to 3G\_MSC-B in: + +- the BSSMAP Assignment procedure. + +#### 4.7.5.9 RANAP Service Handover + +This information shall be stored by 3G\_MSC-B and sent to an RNS in Relocation Request during the basic inter-MSC handover or when 3G\_MSC-B performs a subsequent relocation or handover to UMTS. + +Transfer of information: + +The RANAP Service Handover information is transferred to 3G\_MSC-B in: + +- the Prepare Handover Request MAP message. + +If a new assignment of a Radio Access Bearer after an inter-MSC handover is to be performed, the information is transferred to 3G\_MSC-B in: + +- the Forward Access Signalling Request MAP message + +and sent by 3G\_MSC-B to the RNS in RAB Assignment Request. + +#### 4.7.5.10 GERAN Classmark + +The GERAN Classmark shall be stored by 3G\_MSC-B and can be received from MSC-A, from the serving BSS or serving RNS, or from the target RNS. The GERAN Classmark shall be used together with other parameters, e.g. the Channel Type, for selecting a service and for generating RAB parameters for handover to GERAN Iu-mode, subsequent relocation or handover to GERAN Iu-mode, and RAB (re-)assignment when the MS is in GERAN Iu-mode. + +Transfer of Information due to GERAN Classmark received from MSC-A: + +Received by 3G\_MSC-B in: + +- the Prepare Handover Request MAP message. + +Transfer of Information due to GERAN Classmark received from the serving BSS or serving RNS: + +Received by 3G\_MSC-B in: + +- the Handover Required BSSMAP message; +- the Initial UE RANAP message; or +- the RAB Assignment Response RANAP message. + +Transfer of Information due to GERAN Classmark received from the target RNS: + +Received by 3G\_MSC-B in: + +- the Relocation Failure RANAP message. + +#### 4.7.5.11 SNA Access Information + +This information shall be stored by 3G\_MSC-B and sent to an RNS in the Relocation Request message when 3G\_MSC-B performs handover to UMTS. + +Transfer of information: + +The SNA Access Information is transferred to 3G\_MSC-B in: + +- the Handover Request BSSMAP message. + +#### 4.7.5.12 UESBI + +This information shall be stored by 3G\_MSC-B and sent to an RNS in Relocation Request during the basic inter-MSC handover or when 3G\_MSC-B performs a subsequent relocation or handover to UMTS. + +Transfer of information: + +The UESBI information is transferred to 3G\_MSC-B in: + +- the Prepare Handover Request MAP message. + +#### 4.7.5.13 Alternative Channel Type + +This information shall be stored by 3G\_MSC-B and from this information 3G\_MSC-B shall generate Alternative RAB Parameters Value IE sent to an RNS in Relocation Request, when 3G\_MSC-B performs relocation or handover to UMTS. + +Transfer of information: + +The Alternative Channel Type information is transferred to 3G\_MSC-B in: + +- the Prepare Handover Request MAP message. + +If a new assignment of a Radio Access Bearer after an inter-MSC handover is to be performed, the information is transferred to 3G\_MSC-B in: + +- the Forward Access Signalling Request MAP message. + +#### 4.7.5.14 Trace parameters + +This information shall be stored by 3G\_MSC-B and 3G\_MSC-B shall use this information for trace activation for MSC-S, MGW, RNC or BSC. + +Transfer of information: + +The Trace Parameter List information for MSC-S, MGW and RNC tracing is transferred to 3G\_MSC-B in: + +- the Prepare Handover Request MAP message. + +The Trace Reference and Trace Type information for BSC tracing is transferred to 3G\_MSC-B in: + +- the MSC Invoke Trace BSSMAP message. + +### 4.7.6 Cause Code Mapping + +When a Mobile Station is handed over between GSM and UMTS, a mapping of the cause codes used in the BSSMAP and the RANAP protocols is needed. The mapping described here is applicable to the BSSMAP protocol even when used inside MAP in the E-interface. + +The mapping between the cause codes received in BSSMAP Handover Required and the cause codes sent in RANAP Relocation Request is as follows: + +| 48.008 | 25.413 | Notes | +|---------------------------------|--------------------------------------------|-------| +| HANDOVER REQUIRED | RELOCATION REQUEST | | +| -Better Cell | -Relocation Desirable
for Radio Reasons | | +| -Directed retry | -Directed retry | | +| -Distance | -Time critical reloc. | | +| -Downlink quality | -Time critical reloc. | | +| -Downlink strength | -Time critical reloc. | | +| -O and M intervention | -O and M intervention | | +| -Preemption | -RAB pre-empted | | +| -Response to MSC invocation | -Network Optimisation | | +| -Switch circuit pool | | 1 | +| -Traffic | -Resource Optimisation
Relocation | | +| -Uplink quality | -Time critical reloc. | | +| -Uplink strength | -Time critical reloc. | | +| -Reduce Load in
serving cell | -Reduce Load in
serving cell | | +| -Any other value | -Relocation Desirable
For Radio Reasons | | + +NOTE 1: Cause code not used at inter-system handover. + +The mapping between the cause codes received in BSSMAP Handover Request and the cause codes sent in RANAP Relocation Request is as follows (the mapping is only used for the MAP-E interface): + +| 48.008 | 25.413 | Notes | +|---------------------------------|--------------------------------------------|-------| +| HANDOVER REQUEST | RELOCATION REQUEST | | +| -Better Cell | -Relocation Desirable
for Radio Reasons | | +| -Directed retry | - Directed retry | | +| -Distance | -Time critical reloc. | | +| -Downlink quality | -Time critical reloc. | | +| -Downlink strength | -Time critical reloc. | | +| -O and M intervention | -O and M intervention | | +| -Preemption | -RAB pre-empted | | +| -Response to MSC invocation | -Network Optimisation | | +| -Switch circuit pool | | 1 | +| -Traffic | -Resource Optimisation
Relocation | | +| -Uplink quality | -Time critical reloc. | | +| -Uplink strength | -Time critical reloc. | | +| -Reduce Load in
serving cell | -Reduce Load in
serving cell | | +| -Any other value | -Relocation Desirable
For Radio Reasons | | + +NOTE 1: Cause code not used at inter-system handover. + +The mapping between the cause codes received in BSSMAP Handover Failure and the cause codes sent in RANAP Iu Release Command is as follows: + +| 48.008 | 25.413 | Notes | +|----------------------------------------------------|------------------------|-------| +| HANDOVER FAILURE | IU RELEASE COMMAND | | +| -Ciphering algorithm not supported | | 2 | +| -Circuit pool mismatch | | 1 | +| -Equipment failure | -Relocation cancelled | | +| -Invalid message contents | -Abstract Syntax Error | 2 | +| -No radio resource available | | | +| -O and M intervention | -O and M intervention | | +| -Radio interface failure, reversion to old channel | -Relocation cancelled | | +| -Radio interface message failure | -Relocation cancelled | | +| -Requested speech version unavailable | | 2 | +| -Requested terrestrial resource unavailable | | 2 | +| -Requested transcoding/rate adaption unavailable | | 2 | +| -Switch circuit pool | | 1 | +| -Terrestrial circuit already allocated | -Relocation cancelled | | +| -Any other value | -Relocation cancelled | | + +NOTE 1: Cause code not used at inter-system handover. + +NOTE 2: Cause code not applicable to this traffic case. + +The mapping between the cause codes received in RANAP Relocation Failure and the cause codes sent in BSSMAP Handover Failure is as follows (this mapping is only used for the MAP-E interface): + +| 25.413 | 48.008 | Notes | +|-----------------------------------------------------------------|-----------------------------------------------------------------|-------| +| RELOCATION FAILURE | HANDOVER FAILURE | | +| -GERAN Iu-mode failure | -GERAN Iu-mode failure | | +| -Traffic load in the target cell higher than in the source cell | -Traffic load in the target cell higher than in the source cell | | +| -Any other value | -No radio resource available | | + +The mapping between the cause codes received in RANAP Relocation Failure and the cause codes sent in BSSMAP Handover Required Reject is as follows: + +| 25.413 | 48.008 | Notes | +|-----------------------------------------------------------------|-----------------------------------------------------------------|-------| +| RELOCATION FAILURE | HANDOVER REQUIRED REJECT | | +| -GERAN Iu-mode failure | -GERAN Iu-mode failure | | +| -Incoming Relocation Not Supported Due To PUESBINE Feature | -Incoming Relocation Not Supported Due To PUESBINE Feature | | +| -Traffic load in the target cell higher than in the source cell | -Traffic load in the target cell higher than in the source cell | | +| -Any other value | -No radio resource available | | + +The mapping between the RANAP and the BSSMAP assignment messages is used in the MAP-E interface. RANAP RAB Assignment Response with successful result is mapped to BSSMAP Assignment Complete; RANAP RAB Assignment Response with unsuccessful result is mapped to BSSMAP Assignment Failure. The mapping between the + +cause codes received in RANAP RAB Assignment Response and the cause codes sent in BSSMAP Assignment Failure is as follows (this mapping is only used for the MAP-E interface): + +| 25.413 | 48.008 | Notes | +|-----------------------------------------------------|----------------------------------|-------| +| RAB ASSIGNMENT RESPONSE | ASSIGNMENT FAILURE | | +| -Requested traffic class not available | -No radio resource available | | +| -Invalid RAB parameters value | -Invalid msg. contents | | +| -Requested max bit rate not available | -No radio resource available | | +| -Requested max bit rate for DL not available | -No radio resource available | | +| -Requested max bit rate for UL not available | -No radio resource available | | +| -Requested guaranteed bit rate not available | -No radio resource available | | +| -Requested guaranteed bit rate for DL not available | -No radio resource available | | +| -Requested guaranteed bit rate for UL not available | -No radio resource available | | +| -Requested transfer delay not achievable | -No radio resource available | | +| -Invalid RAB param. combination | -Invalid msg. contents | | +| -Condition violation for SDU parameters | -Invalid msg. contents | | +| -Condition violation for traffic handling priority | -Invalid msg. contents | | +| -Condition violation for guaranteed bit rate | -Invalid msg. contents | | +| -User plane not supported | -No radio resource available | | +| -Iu UP failure | -Equipment failure | | +| -Tqueueing expiry | -Radio interface message failure | | +| -Invalid RAB id | -Invalid msg. contents | | +| -Request superseded | -No radio resource available | | +| -Relocation triggered | -Relocation triggered | | +| -GERAN Iu-mode failure | -GERAN Iu-mode failure | | +| -Any other value | -Radio interface message failure | | + +The mapping between the cause codes received in RANAP Security Mode Reject and the cause codes sent in BSSMAP Cipher Mode Reject is as follows (this mapping is only used for the MAP-E interface): + +| 25.413 | 48.008 | Notes | +|---------------------------------------------------------------------------|------------------------------------|-------| +| SECURITY MODE REJECT | CIPHER MODE REJECT | | +| -Requested ciphering and/or integrity protection algorithms not supported | -Ciphering algorithm not supported | | +| -Failure in the radio interface procedure | -Radio interface message failure | | +| -Change of ciphering and/or integrity protection is not supported | -Invalid msg. contents | | +| -Relocation triggered | -Relocation triggered | | +| -Any other value | -Radio interface message failure | | + +The mapping between the cause codes received in RANAP Location Report and the cause codes sent in BSSMAP Handover Performed is as follows (this mapping is only used for the MAP-E interface): + +| 25.413 | 48.008 | Notes | +|--------------------------------------|--------------------|-------| +| LOCATION REPORT | HANDOVER PERFORMED | | +| -User restriction start ind. | -O&M intervention | | +| -User restriction start ind. | -O&M intervention | | +| -Requested report type not supported | | 1 | +| -Any other value | -Better cell | | + +NOTE 1: In this case, no Handover Performed is sent. + +The mapping between the cause codes received in RANAP Iu Release Request and the cause codes sent in BSSMAP Clear Request is as follows: + +| 25.413 | 48.008 | Notes | +|------------------------------------------------------------|-------------------------------------------|-------| +| IU RELEASE REQUEST | CLEAR REQUEST | | +| -O and M intervention | -O and M intervention | | +| -Unspecified failure | -Equipment failure | | +| -Repeated integrity checking failure | -Invalid message contents | | +| -Release due to UE generated signalling connection release | -Call control | | +| -Radio connection with UE lost | -Radio interface failure | | +| -Access restricted due to shared networks | -Access restricted due to shared networks | | +| -Any other value | -No radio resource available | | + +## 4.8 Inter-MSC Relocation + +The general principles of the relocation procedures are given in Technical Specification TS 23.009. TS 29.010 gives the necessary information for interworking between the TS 25.413 relocation protocol and the TS 29.002 MAP protocol. + +For intra UMTS handovers, RANAP is carried over the MAP-E interface instead of BSSAP. Please refer to 3GPP TS 29.108 [15]. + +When new parameters need to be added for transfer on the E-interface, the principles stated in the beginning of clause 4.5 shall be followed. + +### 4.8.1 Basic Inter-MSC Relocation + +When a Mobile Station is relocated between two MSCs, the establishment of a connection between them (described in TS 23.009) requires interworking between Iu-Interface and E-Interface. + +The signalling at initiation, execution and completion of the Basic Inter-MSC relocation procedure is shown in figures 50 to 54 with both possible positive or negative outcomes. + +Additionally figure 50b shows the possible interworking when trace related messages are transparently transferred on the E-Interface at Basic Inter-MSC Relocation initiation. + +![Sequence diagram for Figure 50a: Signalling for Basic Inter-MSC Relocation initiation (no trace related messages transferred).](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + RNS-A->>3G-MSC-A: RELOCATION REQUIRED + 3G-MSC-A->>3G-MSC-B: MAP PREPARE HANDOVER request + Note over 3G-MSC-B: +--------------------+ + Note over 3G-MSC-B: | Possible Alloc. | + Note over 3G-MSC-B: | of a relocation | + Note over 3G-MSC-B: | no. in the VLR-B | + Note over 3G-MSC-B: +--------------------+ + 3G-MSC-B->>RNS-B: RELOCATION REQUEST + +``` + +Sequence diagram for Figure 50a: Signalling for Basic Inter-MSC Relocation initiation (no trace related messages transferred). + +**Figure 50a: Signalling for Basic Inter-MSC Relocation initiation (no trace related messages transferred)** + +![Sequence diagram for Figure 50b: Signalling for Basic Inter-MSC Relocation initiation (CN invoke trace message transferred).](4a390493f601ce1ac6b9201db4e28b5a_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + Note over 3G-MSC-A: (*) + RNS-A->>3G-MSC-A: RELOCATION REQUIRED + 3G-MSC-A->>3G-MSC-B: MAP PREPARE HANDOVER request (**) + Note over 3G-MSC-B: +--------------------+ + Note over 3G-MSC-B: | Possible Alloc. | + Note over 3G-MSC-B: | of a relocation | + Note over 3G-MSC-B: | no. in the VLR-B | + Note over 3G-MSC-B: +--------------------+ + 3G-MSC-B->>RNS-B: RELOCATION REQUEST + 3G-MSC-B->>RNS-B: CN INVOKE TRACE (***) + +``` + +Sequence diagram for Figure 50b: Signalling for Basic Inter-MSC Relocation initiation (CN invoke trace message transferred). + +**Figure 50b: Signalling for Basic Inter-MSC Relocation initiation (CN invoke trace message transferred)** + +(\*): Tracing invocation has been received from VLR. + +(\*\*): In that case, RELOCATION REQUEST and CN INVOKE TRACE messages are included within the AN-apdu parameter. + +(\*\*\*): CN INVOKE TRACE is forwarded to RNS-B if supported by 3G\_MSC-B. + +Possible Positive outcomes: successful radio resources allocation and relocation numbers allocation (if performed): + +![Sequence diagram for possible positive outcomes of Basic Inter-MSC Relocation initiation.](0adcd19063a66145a465add40bf956e6_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + Note over 3G-MSC-B, RNS-B: RELOCATION REQUEST + Note over 3G-MSC-B, RNS-B: ACKNOWLEDGE + 3G-MSC-B-->>3G-MSC-A: MAP PREPARE HANDOVER response + 3G-MSC-A-->>RNS-A: RELOCATION COMMAND + +``` + +Sequence diagram for possible positive outcomes of Basic Inter-MSC Relocation initiation. + +Possible Negative outcomes: + +- a) user error detected, or relocation numbers allocation unsuccessful (if performed), or component rejection or dialogue abortion performed by 3G\_MSC-B: + +![Sequence diagram showing a negative result for MAP PREPARE HANDOVER leading to relocation failure.](c07e21a8d65991db04263322f859c94f_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + 3G-MSC-B->>3G-MSC-A: MAP PREPARE HANDOVER response negative result, MAP CLOSE + 3G-MSC-A->>3G-MSC-B: MAP U/P-ABORT + 3G-MSC-A->>RNS-A: RELOCATION PREPARATION FAILURE + 3G-MSC-A->>3G-MSC-B: MAP CLOSE + +``` + +Sequence diagram showing a negative result for MAP PREPARE HANDOVER leading to relocation failure. + +b) radio resources allocation failure: + +![Sequence diagram for radio resources allocation failure where RNS-B returns a RELOCATION FAILURE.](9f51a76cae7309a296cbc6997941eb3f_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + 3G-MSC-A->>3G-MSC-B: MAP PREPARE HANDOVER + RNS-B-->>3G-MSC-B: RELOCATION FAILURE + 3G-MSC-B-->>3G-MSC-A: response + 3G-MSC-A-->>RNS-A: RELOCATION PREPARATION FAILURE + +``` + +Sequence diagram for radio resources allocation failure where RNS-B returns a RELOCATION FAILURE. + +c) radio resources allocation partial failure (3G\_MSC-A decides to reject the relocation): + +![Sequence diagram for partial failure where 3G-MSC-A rejects the relocation after an ACK from RNS-B.](b71ad9fc874230de9ba4480e12a216f7_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + 3G-MSC-A->>3G-MSC-B: MAP PREPARE HANDOVER + 3G-MSC-B->>RNS-B: RELOCATION REQUEST + RNS-B-->>3G-MSC-B: ACK + 3G-MSC-B-->>3G-MSC-A: response + 3G-MSC-A-->>RNS-A: RELOCATION PREPARATION FAILURE + +``` + +Sequence diagram for partial failure where 3G-MSC-A rejects the relocation after an ACK from RNS-B. + +d) unsuccessful relocation execution (relocation cancelled): + +![Sequence diagram for cancelled relocation execution involving MAP U-ABORT and IU RELEASE COMMAND.](99e9a4791d2e5bb5afa1bb884652d4db_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + RNS-A->>3G-MSC-A: RELOCATION CANCEL + 3G-MSC-A->>3G-MSC-B: MAP U -ABORT + 3G-MSC-A-->>RNS-A: RELOCATION CANCEL ACK + 3G-MSC-B->>RNS-B: IU RELEASE COMMAND + +``` + +Sequence diagram for cancelled relocation execution involving MAP U-ABORT and IU RELEASE COMMAND. + +**Figure 51: Signalling for Basic Inter-MSC Relocation execution (Negative outcomes)** + +![Sequence diagram for Basic Inter-MSC Relocation completion (General)](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + RNS-B->>3G-MSC-B: RELOCATION COMPLETE + 3G-MSC-B->>3G-MSC-A: MAP SEND END SIGNAL request + 3G-MSC-A->>RNS-A: IU RELEASE COMMAND + +``` + +Sequence diagram for Basic Inter-MSC Relocation completion (General) + +**Figure 52: Signalling for Basic Inter-MSC Relocation completion** + +Positive outcome + +![Sequence diagram for Basic Inter-MSC Relocation completion (Positive outcome)](1314748d1fff41b2d57a8ba9e9687c6a_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + 3G-MSC-A->>3G-MSC-B: MAP SEND END SIGNAL response + 3G-MSC-B->>RNS-B: IU RELEASE COMMAND (Note 1) + +``` + +Sequence diagram for Basic Inter-MSC Relocation completion (Positive outcome) + +**Figure 53: Signalling for Basic Inter-MSC Relocation completion (Positive outcome)** + +NOTE: From interworking between MAP and RANAP point of view. + +Negative outcome: + +![Sequence diagram for Basic Inter-MSC Relocation completion (Negative outcome)](7b18671bc31881a5c474883bf6a300fd_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + 3G-MSC-A->>3G-MSC-B: MAP U/P -ABORT + 3G-MSC-B->>RNS-B: IU RELEASE COMMAND + +``` + +Sequence diagram for Basic Inter-MSC Relocation completion (Negative outcome) + +**Figure 54: Signalling for Basic Inter-MSC Relocation completion (Negative outcome)** + +The relocation procedure is normally triggered by RNS-A by sending a RELOCATION REQUIRED message on Iu-Interface to 3G\_MSC-A. The invocation of the Basic Inter-MSC relocation procedure is performed and controlled by 3G\_MSC-A. The sending of the MAP Prepare-Handover request to 3G\_MSC-B is triggered in 3G\_MSC-A upon receipt of the RELOCATION REQUIRED message. The identity of the target RNC where the call is to be handed over in 3G\_MSC-B area, provided in the RELOCATION REQUIRED message, is mapped to the target RNC Id MAP parameter and the RELOCATION REQUEST message is encapsulated in the an-APDU MAP parameter of the Prepare-Handover MAP request. 3G\_MSC-B can invoke another operation towards the VLR-B (allocation of the relocation numbers described in 3GPP TS 29.002 [9]). + +Additionally, if tracing activity has been invoked, the trace related messages can be transferred on the E-Interface encapsulated in the an-APDU MAP parameter of the Prepare-Handover Request. If transferred, one complete trace related message at a time shall be included in the an-APDU MAP parameter after the RELOCATION REQUEST message. + +The interworking between Prepare Handover and RELOCATION REQUIRED is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| Forward message | RELOCATION REQUIRED MAP PREPARE HANDOVER request

RANAP information elements

GERAN classmark | -ho-NumberNotRequired
-target RNC Id
-Radio Resource Info
-an-APDU(
RELOCATION REQUEST,
CN INVOKE TRACE)
-GERAN classmark | 1

2

4 | +| Positive result | MAP PREPARE HANDOVER response

RELOCATION COMMAND

RELOCATION PREP FAILURE | -relocation numbers
-an-APDU(
RELOCATION REQUEST
ACKNOWLEDGE
or
RELOCATION FAILURE) | 3 | +| Negative result | RELOCATION PREP FAILURE

Unspecified failure
Unspecified failure

Unspecified failure
Unspecified failure

Unspecified failure
Unspecified failure | MAP PREPARE HANDOVER

System Failure
No Handover Number
available
UnexpectedDataValue
Data Missing

MAP CLOSE
MAP U/P -ABORT | | + +NOTE 1: The RANAP information elements are already stored in 3G\_MSC. + +The ho-NumberNotRequired parameter is included by 3G\_MSC-A, when 3G\_MSC-A decides not to use any circuit connection with 3G\_MSC-B. No relocation numbers shall be present in the positive result. Any negative response from 3G\_MSC-B shall not be due to relocation number allocation problem. + +NOTE 2: The process performed on the RANAP information elements received in the RELOCATION REQUIRED message is described in the 3GPP TS 25.413 [7]. + +NOTE 3: The response to the Prepare-Handover request can include in its an-APDU parameter, identifying the 3GPP TS 25.413 [7] protocol, either a RANAP RELOCATION REQUEST ACKNOWLEDGE or a RANAP RELOCATION FAILURE. + +In the first case, the positive result triggers in 3G\_MSC-A the sending on Iu-Interface of the RELOCATION CMD. + +In the second case, the positive result triggers in 3G\_MSC-A the sending of the RELOCATION PREP FAILURE. + +NOTE 4: If the GERAN Classmark was not received with the RELOCATION REQUIRED message initiating the relocation, 3G\_MSC-A shall include any previously received GERAN Classmark. See 3GPP TS 43.051 [17]. + +The interworking between Send End Signal and RELOCATION COMPLETE in 3G\_MSC-B is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|--------------------------------------------------------------------|--------------------------------|-------| +| Forward message | RELOCATION COMPLETE MAP SEND END SIGNAL request | -an-APDU(
RELOCATION COMPL) | | +| Positive result | IU RELEASE COMMAND MAP SEND END SIGNAL response
-Normal release | | 1 | +| Negative result | IU RELEASE COMMAND
-Normal release
-Normal release | MAP CLOSE
MAP U/P -ABORT | 2 | + +NOTE 1: The positive empty result triggers the clearing of the Radio Resources on the Iu-Interface and the release of the SCCP connection between 3G\_MSC-B and RNS-B. If a circuit connection is used between 3G\_MSC-A and 3G\_MSC-B, the 'Normal release' clearing cause shall only be given to RNS-B when 3G\_MSC-B has received a clearing indication on its circuit connection with 3G\_MSC-A. + +NOTE 2: The abortion of the dialogue or the rejection of the component triggers in 3G\_MSC-B the clearing of its circuit connection with 3G\_MSC-A, if any, of the Radio Resources on the Iu-Interface and the release of the SCCP connection between 3G\_MSC-B and RNS-B. + +The interworking between Send End Signal and IU RELEASE COMMAND in 3G\_MSC-A is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-----------------------------------|--------------------------------------------------|-------| +| Forward message | MAP SEND END SIGNAL request | IU RELEASE COMMAND
- Successful
Relocation | | +| Positive result | -an-APDU(
RELOCATION COMPLETE) | | | +| Negative result | | | | + +The interworking between RELOCATION CANCEL in case of relocation cancelled and User Abort in 3G\_MSC-A is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|------------------------------------------------|--------------|-------| +| Forward message | RELOCATION CANCEL
- Relocation
cancelled | MAP U -ABORT | | +| Positive result | RELOCATION CANCEL ACKNOWLEDGEMENT | | | +| Negative result | | | | + +### 4.8.2 Subsequent Inter-MSC Relocation back to 3G\_MSC-A + +When a Mobile Station is being relocated back to 3G\_MSC-A, the procedure (described in TS 23.009) requires interworking between Iu-Interface and E-Interface. + +The signalling at initiation, execution and completion of the Subsequent Inter-MSC relocation procedure is shown in figures 55 to 59. + +![Figure 55: Signalling for Subsequent Inter-MSC Relocation back to 3G_MSC-A initiation](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + RNS-A->>3G-MSC-B: RELOCATION REQUIRED + 3G-MSC-B->>3G-MSC-A: MAP PREPARE SUBSEQUENT HANDOVER request + 3G-MSC-A->>RNS-B: RELOCATION REQUEST + +``` + +Figure 55: Signalling for Subsequent Inter-MSC Relocation back to 3G\_MSC-A initiation + +**Figure 55: Signalling for Subsequent Inter-MSC Relocation back to 3G\_MSC-A initiation** + +Possible Positive outcomes: successful radio resources allocation: + +![Figure 56: Signalling for Subsequent Inter-MSC Relocation back to 3G_MSC-A execution (Positive outcome)](384ca4ed072674dbb16642cd334b1c15_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + RNS-B->>3G-MSC-A: RELOCATION REQUEST ACKNOWLEDGE + 3G-MSC-A->>3G-MSC-B: MAP PREPARE SUBSEQUENT HANDOVER response + 3G-MSC-B->>RNS-A: RELOCATION COMMAND + +``` + +Figure 56: Signalling for Subsequent Inter-MSC Relocation back to 3G\_MSC-A execution (Positive outcome) + +**Figure 56: Signalling for Subsequent Inter-MSC Relocation back to 3G\_MSC-A execution (Positive outcome)** + +Possible Negative outcomes: + +- a) user error detected, or component rejection or dialogue abortion performed by 3G\_MSC-A: + +![Negative outcome (a): user error or rejection by 3G_MSC-A](fbdd4682fb49c08ff8415c854336a6ab_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + 3G-MSC-A-->>3G-MSC-B: MAP PREPARE SUBSEQUENT HANDOVER response negative result + 3G-MSC-B->>RNS-A: RELOCATION PREP FAILURE (Note 1) + +``` + +Negative outcome (a): user error or rejection by 3G\_MSC-A + +- b) component rejection or dialogue abortion performed by 3G\_MSC-A: + +![Negative outcome (b): dialogue abortion by 3G_MSC-A](4caed5b90277a5c5ee07547bfc8ff884_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + 3G-MSC-A-->>3G-MSC-B: MAP CLOSE, MAP U/P ABORT + 3G-MSC-B->>RNS-A: IU RELEASE COMMAND + +``` + +Negative outcome (b): dialogue abortion by 3G\_MSC-A + +- c) radio resources allocation failure: + +![Negative outcome (c): radio resources allocation failure](5bafbca630e8c8a3f0d7e1854bd23aa2_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + RNS-B-->>3G-MSC-A: RELOCATION FAILURE + 3G-MSC-A->>3G-MSC-B: MAP PREPARE SUBSEQUENT HANDOVER response + 3G-MSC-B->>RNS-A: RELOCATION PREP FAILURE + +``` + +Negative outcome (c): radio resources allocation failure + +d) radio resources allocation partial failure (3G\_MSC-A decides to reject the relocation): + +![Sequence diagram for radio resources allocation partial failure](145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + 3G-MSC-B->>3G-MSC-A: MAP PREPARE SUBSEQUENT + 3G-MSC-A->>RNS-B: RELOCATION REQUEST + RNS-B-->>3G-MSC-A: ACK + 3G-MSC-A-->>3G-MSC-B: HANDOVER response + 3G-MSC-B-->>RNS-A: RELOCATION PREP FAILURE + +``` + +Sequence diagram for radio resources allocation partial failure + +e) unsuccessful relocation execution (relocation cancelled): + +![Sequence diagram for unsuccessful relocation execution](e38f0349f1b6094626cbfeab7105f029_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + RNS-A->>3G-MSC-B: RELOCATION CANCEL + 3G-MSC-B->>3G-MSC-A: MAP PROCESS ACCESS + Note over 3G-MSC-B,3G-MSC-A: SIGNALLING request + 3G-MSC-A->>RNS-B: IU RELEASE COMMAND + RNS-B-->>3G-MSC-A: IU RELEASE COMPLETE + 3G-MSC-A->>3G-MSC-B: MAP FORWARD ACCESS + Note over 3G-MSC-A,3G-MSC-B: SIGNALLING request + 3G-MSC-B-->>RNS-A: RELOCATION CANCEL ACK + +``` + +Sequence diagram for unsuccessful relocation execution + +**Figure 57: Signalling for Subsequent Inter-MSC Relocation back to 3G\_MSC-A execution (Negative outcome)** + +![Sequence diagram for Figure 58: Successful completion](223c6f5bda05ffdd254a828a148b53f1_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + RNS-B->>3G-MSC-A: RELOCATION COMPLETE + 3G-MSC-A->>3G-MSC-B: MAP SEND END SIGNAL + 3G-MSC-B-->>3G-MSC-A: response + 3G-MSC-B-->>RNS-A: IU RELEASE CMD + +``` + +Sequence diagram for Figure 58: Successful completion + +**Figure 58: Signalling for Subsequent Inter-MSC Relocation back to 3G\_MSC-A completion (Successful completion of the procedure)** + +NOTE: Positive outcome case shown in figure 53. + +![Sequence diagram for Figure 59: Unsuccessful completion](061a752e081b43db4964482b0349f751_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant RNS-B + 3G-MSC-B->>3G-MSC-A: MAP U/P -ABORT + 3G-MSC-A->>RNS-B: IU RELEASE COMMAND (Note 1) + +``` + +Sequence diagram for Figure 59: Unsuccessful completion + +**Figure 59: Signalling for Subsequent Inter-MSC Relocation back to 3G\_MSC-A completion (Unsuccessful completion of the procedure)** + +NOTE: Abnormal end of the procedure that triggers the clearing of all resources in 3G\_MSC-B. + +The interworking between Prepare Subsequent Handover and RELOCATION REQUIRED is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| Forward message | REL. REQUIRED

RANAP information elements

GERAN classmark | MAP PREPARE SUBSEQUENT HANDOVER request

-target MSC number
-target RNC Id
-an-APDU(
RELOCATION REQ)

-GERAN classmark |

1

3 | +| Positive result | MAP PREPARE

RELOCATION CMD.

RELOCATION PREP FAILURE | SUBSEQUENT HANDOVER response
-an-APDU(
RELOCATION REQUEST
ACKNOWLEDGE
or
RELOCATION FAILURE) |

2 | +| Negative result | REL. PREP. FAILURE

Unspecified failure
Unspecified failure

Unspecified failure
Unspecified failure

Iu RELEASE COMMAND

Unspecified failure
Unspecified failure | MAP PREPARE SUBSEQUENT HANDOVER response
Unknown MSC
Subsequent Handover Failure

UnexpectedDataValue
Data Missing

MAP CLOSE
MAP U/P -ABORT | | + +NOTE 1: The processing performed on the RANAP information elements received in the RELOCATION REQUIRED message is out of the scope of the present document. The target MSC number is provided to 3G\_MSC-A by 3G\_MSC-B based on the information received from RNS-B. + +NOTE 2: The response to the Prepare-Subsequent-Handover request can include in its an-APDU parameter, identifying the 3GPP TS 25.413 [7] protocol, a RANAP RELOCATION REQUEST ACKNOWLEDGE or a RANAP RELOCATION FAILURE. + +NOTE 3: If the GERAN Classmark was not received with the RELOCATION REQUIRED message initiating the relocation, MSC-B shall include any previously received GERAN Classmark. See 3GPP TS 43.051 [17]. + +In the first case, the positive result triggers in 3G\_MSC-B the sending on Iu-Interface of the RELOCATION COMMAND. + +In the second case, the positive result triggers in 3G\_MSC-B the sending of the RELOCATION PREPARATION FAILURE. + +The interworking between RELOCATION CANCEL and MAP Process Signalling Request in 3G\_MSC-A is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-----------------------------------------------------------------------|---------------------|-------| +| Forward message | MAP PROCESS-SIGNALLING request
-an-APDU(
RELOCATION CANCEL) | IU RELEASE COMMAND | | +| Positive result | MAP FORWARD-SIGNALLING request
-an-APDU(
RELOCATION CANCEL ACK) | IU RELEASE COMPLETE | | +| Negative result | | | | + +The interworking between RELOCATION CANCEL and MAP Process Signalling Request in 3G\_MSC-B is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|-----------------------|-----------------------------------------------------------------------|-------| +| Forward message | RELOCATION CANCEL | MAP PROCESS-SIGNALLING request
-an-APDU(
RELOCATION CANCEL) | | +| Positive result | RELOCATION CANCEL ACK | MAP FORWARD-SIGNALLING request
-an-APDU(
RELOCATION CANCEL ACK) | | +| Negative result | | | | + +The interworking between Send End Signal Result and RELOCATION COMPLETE in 3G\_MSC-A is as follows: + +| | 25.413 | 29.002 | Notes | +|-----------------|---------------------|------------------------------|-------| +| Forward message | RELOCATION COMPLETE | MAP SEND END SIGNAL response | | +| Positive result | | | | +| Negative result | | MAP U/P -ABORT | 1 | + +NOTE: The abortion of the dialogue ends the relocation procedure with 3G\_MSC-B. + +### 4.8.3 Subsequent Inter-MSC Relocation to third MSC + +When a Mobile Station is being relocated to a third MSC, the procedure (described in 3GPP TS 23.009 [2]) does require one specific interworking case in 3G\_MSC-A (figure 64) between E-Interface from 3G\_MSC-B and E-Interface from 3G\_MSC-B' other than the combination of the ones described in the clause 4.8.1 and 4.8.2. + +![](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` + +RNS-A 3G-MSC-B 3G-MSC-A 3G-MSC-B' + | | | | + | RELOCATION | | | + | REQUIRED | | | + |-------------->| MAP PREPARE SUBSEQUENT| | + | |---------------------->| | + | | HANDOVER request | MAP PREPARE | + | | |------------------->| + | | | HANDOVER request | +---------+ + | | | | | Possib. | + | | | | | Alloc. | + | | | | | of relo | + | | | | | number | + | | | | | VLR-B | + | | | | +---------+ + | | | | RNS-B' + | | | | RELOCATION + | | | |-----------> + | | | | REQUEST + +``` + +**Figure 60: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G\_MSC-B') initiation** + +Possible Positive outcomes: successful radio resources allocation: + +![](f2486d5031b55e42b300903a716b0a00_img.jpg) + +``` + +RNS-A 3G-MSC-B 3G-MSC-A 3G-MSC-B' + | | | | RNS-B' + | | | | RELOCATION + | | | |<----------- + | | | | REQUEST + | | | | ACKNOWLEDGE + | | | MAP PREPARE HANDOVER + | | |<------------------- + | | MAP PREPARE SUBSEQUENT| response + | |<----------------------| + | | HANDOVER response | + | RELOCATION | + |<--------------| + | COMMAND | + +``` + +**Figure 61: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G\_MSC-B') execution (Positive outcome)** + +Possible Negative outcomes: + +a) user error detected, or component rejection or dialogue abortion performed by 3G\_MSC-B': + +![](665db9e4c084c517dc46f23397c8533a_img.jpg) + +``` + +RNS-A 3G-MSC-B 3G-MSC-A 3G-MSC-B' + | | | | RNS-B' + | | | MAP PREPARE HANDOVER + | | | response negative result + | | | MAP CLOSE + | | |<------------------- + | | | MAP U/P -ABORT + | | MAP PREPARE SUBSEQUENT| + | |<----------------------| + | | HANDOVER response negative + | RELOCATION | result + |<--------------| + | PREPARATION | + | FAILURE | + +``` + +b) radio resources allocation failure: + +![Sequence diagram for Figure 62 (Negative outcome) showing a radio resource allocation failure during inter-MSC relocation.](c7e27041e661260fd0c8e89c763bb32e_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant 3G-MSC-B_prime as 3G-MSC-B' + participant RNS-B_prime as RNS-B' + + Note right of RNS-A: RELOCATION PREPARATION FAILURE + RNS-A-->3G-MSC-B: + 3G-MSC-B->>3G-MSC-A: MAP PREPARE SUBSEQUENT HANDOVER response + 3G-MSC-A-->>3G-MSC-B_prime: MAP PREPARE HANDOVER response + Note right of RNS-B_prime: RELOCATION FAILURE + +``` + +Sequence diagram for Figure 62 (Negative outcome) showing a radio resource allocation failure during inter-MSC relocation. + +c) radio resources allocation partial failure (3G\_MSC-A decides to reject the relocation): + +![Sequence diagram for Figure 62 (Partial failure) showing a partial radio resource allocation failure where 3G_MSC-A rejects the relocation.](079326de347e985e278d2674647d17dc_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant 3G-MSC-B_prime as 3G-MSC-B' + participant RNS-B_prime as RNS-B' + + Note right of RNS-A: RELOCATION PREPARATION FAILURE + RNS-A-->3G-MSC-B: + 3G-MSC-B->>3G-MSC-A: MAP PREPARE SUBSEQUENT HANDOVER response + 3G-MSC-A-->>3G-MSC-B_prime: MAP PREPARE HANDOVER response + Note right of RNS-B_prime: RELOCATION REQ ACK + +``` + +Sequence diagram for Figure 62 (Partial failure) showing a partial radio resource allocation failure where 3G\_MSC-A rejects the relocation. + +**Figure 62: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G\_MSC-B') execution (Negative outcome)** + +Positive outcome: + +![Sequence diagram for Figure 63 (Successful completion) showing the successful completion of the inter-MSC relocation procedure.](88066268366ca160709e20f13ed8f356_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant 3G-MSC-B_prime as 3G-MSC-B' + participant RNS-B_prime as RNS-B' + + Note right of RNS-A: IU RELEASE COMMAND + RNS-A-->3G-MSC-B: + 3G-MSC-B->>3G-MSC-A: MAP SEND END SIGNAL response + 3G-MSC-A-->>3G-MSC-B_prime: MAP SEND END SIGNAL request + Note right of RNS-B_prime: RELOCATION COMPLETE + +``` + +Sequence diagram for Figure 63 (Successful completion) showing the successful completion of the inter-MSC relocation procedure. + +**Figure 63: Signalling for Subsequent Inter-MSC Relocation to third MSC (3G\_MSC-B') completion (Successful completion of the procedure)** + +Negative outcome: + +![Sequence diagram showing signalling for Subsequent Inter- MSC Relocation to third MSC (3G_MSC-B') completion (Unsuccessful completion of the procedure).](886963464425186f4a465fa8155d2a3c_img.jpg) + +``` + +sequenceDiagram + participant RNS-A + participant 3G-MSC-B + participant 3G-MSC-A + participant 3G-MSC-B_prime as 3G-MSC-B' + participant RNS-B_prime as RNS-B' + + Note left of RNS-A: Negative outcome: + RNS-A->>3G-MSC-B: RELOCATION CANCEL + 3G-MSC-B->>3G-MSC-A: MAP PROCESS ACCESS SIGNALLING request (Note 1) + 3G-MSC-A->>3G-MSC-B_prime: MAP U -ABORT + 3G-MSC-B_prime->>RNS-B_prime: IU RELEASE COMMAND + 3G-MSC-B->>RNS-A: RELOCATION CANCEL ACK + +``` + +Sequence diagram showing signalling for Subsequent Inter- MSC Relocation to third MSC (3G\_MSC-B') completion (Unsuccessful completion of the procedure). + +**Figure 64: Signalling for Subsequent Inter- MSC Relocation to third MSC (3G\_MSC-B') completion (Unsuccessful completion of the procedure)** + +NOTE: Specific interworking case detailed below. + +The specific interworking case in 3G\_MSC-A compared to the clauses 4.8.1 and 4.8.2 occurs between RELOCATION FAILURE encapsulated in a Process Access Signalling from 3G\_MSC-B and the abortion of the dialogue with 3G\_MSC-B' in the case of relocation cancelled: + +| | 29.002 | 29.002 | Notes | +|-----------------|-----------------------------------------------------------------------|----------------|-------| +| Forward message | MAP PROCESS-SIGNALLING request
-an-APDU(
RELOCATION CANCEL) | MAP U -ABORT | 1 | +| Positive result | MAP FORWARD-SIGNALLING request
-an-APDU(
RELOCATION CANCEL ACK) | | | +| Negative result | | MAP U/P -ABORT | 2 | + +NOTE 1: The abortion of the dialogue triggers in 3G\_MSC-B' the clearing of the circuit connection with 3G\_MSC-A, if any, and of the Resources between 3G\_MSC-B' and RNS-B'. The abortion of the dialogue ends the relocation procedure with 3G\_MSC-B'. + +NOTE 2: The abortion of the dialogue ends the relocation procedure with 3G\_MSC-B. + +### 4.8.4 RANAP Messages transfer on E-Interface + +The following mapping applies to the encapsulation performed in 3G\_MSC-A. + +| | 25.413 | 29.002 | Notes | +|-----------------|----------------|--------------------------------------------------------------------|-------| +| Forward message | RANAP messages | MAP FORWARD ACCESS SIGNALLING request
-an-APDU (RANAP messages) | 1 | +| Positive result | | | 2 | +| Negative result | | MAP CLOSE
MAP U/P -ABORT | | + +NOTE 1: Complete RANAP messages to be sent on 3G\_MSC-B - RNS-B interface are embedded into the an-APDU parameter. + +NOTE 2: The Return Result does not apply. If 3G\_MSC-B returns a message, this message will arrive in an Invoke: Process Access Signalling. + +The following mapping applies to the encapsulation performed in 3G\_MSC-B. + +| | 25.413 | 29.002 | Notes | +|-----------------|-------------------------------------------|--------------------------------------------------------------------|-------| +| Forward message | RANAP messages | MAP PROCESS ACCESS SIGNALLING request
-an-APDU (RANAP messages) | 1 | +| Positive result | | | 2 | +| Negative result | IU RELEASE COMMAND
Unspecified failure | MAP CLOSE
MAP U/P -ABORT | 3 | + +NOTE 1: Complete RANAP messages to be sent to 3G\_MSC-A are embedded into the an-APDU parameter. + +NOTE 2: The Return Result does not apply. If 3G\_MSC-A returns a message, this message will arrive in an Invoke: Forward Access Signalling. + +NOTE 3: The abortion of the dialogue triggers the clearing of the circuit connection with 3G\_MSC-A, if any, of the Radio Resources on the Iu-Interface and the release of the SCCP connection between 3G\_MSC-B and RNS-B. The clearing of the Radio Resources (the clearing indication received from RNS-B is transmitted to 3G\_MSC-A) or the loss of the SCCP connection between 3G\_MSC-B and RNS-B, triggers in 3G\_MSC-B the abortion of the dialogue on the E-Interface and the clearing of the circuit connection with 3G\_MSC-A, if any. + +### 4.8.5 Processing in 3G\_MSC-B, and information transfer on E-interface + +The following parameters require processing (e.g. to store the parameter, to internally generate the parameter) in 3G\_MSC-B. The relevant RANAP procedures are mentioned to ease the comprehension, their detailed description is the scope of the TS 25.413. Each RANAP message being transferred on E-interface shall use the mechanisms given in clause 4.8.4 and is described in TS 25.413. + +#### 4.8.5.1 Integrity Protection Information + +A sequence of possible integrity protection algorithms can be sent to an RNS in Security Mode Command or Relocation Request. The RNS chooses one of the listed algorithms and reports this back to the 3G\_MSC in Security Mode Complete or Relocation Request Acknowledge respectively. + +3G\_MSC-B shall remove algorithms not allowed by 3G\_MSC-B from the list of algorithms received from 3G\_MSC-A before forwarding it to the RNS. The modified list of algorithms, the integrity protection key and the chosen algorithm shall be stored by 3G\_MSC-B. + +Transfer of Information: + +If integrity protection has not been performed before Inter- MSC Relocation, this will be controlled by 3G\_MSC-A after the completion of Inter- MSC Relocation. + +Integrity protection control towards 3G\_MSC-B: + +If Integrity protection has been performed before Inter- MSC Relocation: + +- in the Relocation Request RANAP message (information included). + +The Relocation Request Acknowledge should in this case contain the indication of the chosen algorithm. + +If Integrity protection has NOT been performed before Inter- MSC Relocation: + +- in the Security Mode Command procedure between 3G\_MSC-A and 3G\_MSC-B. + +#### 4.8.5.2 Encryption Information + +A sequence of possible encryption algorithms can be sent to an RNS in Security Mode Command or Relocation Request. The RNS chooses one of the listed algorithms and reports this back to the 3G\_MSC in Security Mode Complete or Relocation Request Acknowledge respectively. + +3G\_MSC-B shall remove algorithms not allowed by MSC-B from the list of algorithms received from 3G\_MSC-A before forwarding it to the RNS. The modified list of algorithms, the ciphering key and the chosen algorithm shall be stored by 3G\_MSC-B, and the chosen value sent to 3G\_MSC-A. + +Transfer of Information: + +If ciphering has not been performed before Inter- MSC Relocation, this will be controlled by 3G\_MSC-A after the completion of Inter- MSC Relocation. + +Ciphering control towards 3G\_MSC-B: + +If Ciphering has been performed before Inter- MSC Relocation: + +- in the Relocation Request RANAP message (information included). + +The Relocation Request Acknowledge should in this case contain the indication of the chosen algorithm. + +If Ciphering has NOT been performed before Inter- MSC Relocation: + +- in the Security Mode Command procedure between 3G\_MSC-A and 3G\_MSC-B. + +#### 4.8.5.3 RAB Parameters + +The parameters shall be stored by 3G\_MSC-B to be used at internal Relocation in 3G\_MSC-B. + +Transfer of information: + +Received by 3G\_MSC-B from 3G\_MSC-A in: + +- The Relocation Request RANAP message. + +If a new type of resource is to be assigned after Inter- MSC Relocation, this can be made with: + +- The RAB Assignment Request RANAP message. + +#### 4.8.5.4 Channel Type + +Channel Type is GSM information that is required in BSSMAP Handover Request and BSSMAP Assignment Request, and it shall be provided by 3G\_MSC-A. 3G\_MSC-B needs this information in case of an intra-MSC UMTS to GSM handover after an inter-MSC relocation and subsequent assignment procedures. The Channel Type derived from the Bearer Capability that is available in 3G\_MSC-A. This mapping is described in 3GPP TS 27.001 [8]. Therefore 3G\_MSC-A must provide this information in case of an inter-MSC relocation. The Radio Resource Information IE in the MAP Prepare Handover message refers to the Channel Type GSM information. + +Channel Type shall be stored by 3G\_MSC-B. + +Transfer of information: + +Received by 3G\_MSC-B from 3G\_MSC-A in: + +- The Prepare Handover Request MAP message. +- The Forward Access Signalling Request message. + +#### 4.8.5.5 Selected GSM Algorithm + +After inter-MSC relocation, the 3G\_MSC-B can perform intra-MSC UMTS to GSM handover. A sequence of possible encryption algorithms, received from the 3G\_MSC-A, can be sent to an BSS in Handover Request or in Cipher Mode Command in case of cipher mode setting after intra-MSC-B handover from UMTS to GSM. The BSS chooses one of the listed algorithms and reports this back to the 3G\_MSC in Handover Request Acknowledge or Cipher Mode Complete respectively. The MSC-B provides the Selected GSM algorithm information to the MSC-A. The Selected GSM algorithms IE in the MAP Process Access Signalling Request message refers to the Algorithm identifier octet in the Chosen Encryption Algorithm GSM information. + +The chosen algorithm shall be stored by 3G\_MSC-B, and sent to 3G\_MSC-A. + +Transfer of Information: + +If ciphering has not been performed before Inter-MSC Relocation, this will be controlled by 3G\_MSC-A after the completion of Inter-MSC Relocation. + +If Ciphering has been performed before Inter-MSC Relocation, Selected GSM algorithm information is received by 3G\_MSC-A from 3G\_MSC-B in: + +- The Handover Performed BSSMAP message. + +If Ciphering has NOT been performed before Intra-MSC-B handover from UMTS to GSM after Inter-MSC Relocation, Selected GSM algorithm information is received by 3G\_MSC-A from 3G\_MSC-B in: + +- The Process Access Signalling Request MAP message. + +#### 4.8.5.6 Allowed GSM Algorithms + +Allowed GSM algorithms is GSM information that is required in BSSMAP Handover Request and BSSMAP Cipher Mode Command, and shall be provided by 3G\_MSC-A. 3G\_MSC-B needs this information in case of an intra-MSC UMTS to GSM handover and in subsequent ciphering mode setting, after an inter-MSC relocation. Therefore 3G\_MSC-A must provide this information in case of an inter-MSC relocation. The Allowed GSM algorithms IE in the MAP Prepare Handover and in the MAP Forward Access Signalling Request messages refers to the Algorithm identifier octet in the Permitted Algorithms GSM information. + +Allowed GSM algorithms shall be stored by 3G\_MSC-B. + +Transfer of information: + +If ciphering has not been performed before Inter-MSC Relocation, this will be controlled by 3G\_MSC-A after the completion of Inter-MSC Relocation. + +Ciphering control towards 3G\_MSC-B: + +If Ciphering has been performed before Inter-MSC Relocation: + +- The Prepare Handover Request MAP message. + +If Ciphering has NOT been performed before Inter-MSC Relocation: + +- The Forward Access Signalling Request MAP message. + +#### 4.8.5.7 Chosen Channel + +BSSMAP Assignment Request may give the BSS some freedom in the selection of radio resource (for instance channel rate selection, speech version selection etc.). Chosen Channel and/or Speech Version is reported back to 3G\_MSC-B in BSSMAP Assignment Complete. The Chosen Radio Resource Information IE in the MAP Prepare Handover Response and Process Access Signalling Request messages refers to the Chosen Channel and/or Speech Version GSM information. + +The Channel Type and the characteristics of the chosen channel shall be stored by 3G\_MSC-B, and the Chosen Channel and/or Speech Version information elements shall be transferred to MSC-A or 3G\_MSC-A. + +Transfer of information: + +Received by MSC-A or 3G\_MSC-A from 3G\_MSC-B in: + +- The Prepare Handover Response MAP message +- The Process Access Signalling request MAP message + +#### 4.8.5.8 BSSMAP Service Handover + +This information shall be stored by 3G\_MSC-B and sent to a BSS in Handover Request, when 3G\_MSC-B performs handover to GSM. + +Transfer of information: + +The BSSMAP Service Handover information is transferred to 3G\_MSC-B in: + +- the Prepare Handover Request MAP message. + +If a new assignment of a TCH after an inter-MSC relocation is to be performed, the BSSMAP Service Handover information is transferred to 3G\_MSC-B in: + +- the Forward Access Signalling Request MAP message + +and sent by 3G\_MSC-B to the BSS in the Assignment Request BSSMAP message. + +#### 4.8.5.9 RANAP Service Handover + +This information shall be stored by 3G\_MSC-B and sent to an RNS in Relocation Request during the basic inter-MSC relocation or when 3G\_MSC-B performs a subsequent intra-MSC relocation or handover to UMTS. + +Transfer of information: + +The RANAP Service Handover information is transferred to 3G\_MSC-B in: + +- the Relocation Request RANAP message. + +If a new assignment of a Radio Access Bearer after an inter-MSC relocation is to be performed, the information is transferred to 3G\_MSC-B in: + +- the RANAP RAB Assignment procedure. + +#### 4.8.5.10 GERAN Classmark + +The GERAN Classmark shall be stored by 3G\_MSC-B and can be received from MSC-A, from the serving BSS or serving RNS, or from the target RNS. The GERAN Classmark shall be used together with other parameters, e.g. the Channel Type, for selecting a service and for generating RAB parameters for relocation to GERAN Iu-mode, subsequent relocation or handover to GERAN Iu-mode, and RAB (re-)assignment when the MS is in GERAN Iu-mode. + +Transfer of Information due to GERAN Classmark received from MSC-A: + +Received by 3G\_MSC-B in: + +- the Prepare Handover Request MAP message. + +Transfer of Information due to GERAN Classmark received from the serving RNS: + +Received by 3G\_MSC-B in: + +- the Handover Required BSSMAP message; +- the Relocation Required RANAP message; +- the Initial UE RANAP message; or +- the RAB Assignment Response RANAP message. + +Transfer of Information due to GERAN Classmark received from the target RNS: + +Received by 3G\_MSC-B in: + +- the Relocation Failure RANAP message. + +#### 4.8.5.11 SNA Access Information + +This information shall be stored by 3G\_MSC-B and sent to an RNS in the Relocation Request message when 3G\_MSC-B performs handover to UMTS. + +Transfer of information: + +The SNA Access Information is transferred to 3G\_MSC-B in: + +- the Relocation Request RANAP message encapsulated in the Prepare Handover request MAP message. + +#### 4.8.5.12 UESBI + +This information shall be stored by 3G\_MSC-B and sent to an RNS in Relocation Request during the basic inter-MSC relocation or when 3G\_MSC-B performs a subsequent intra-MSC relocation or handover to UMTS. + +Transfer of information: + +The UESBI information is transferred to 3G\_MSC-B in: + +- the Relocation Request RANAP message. + +#### 4.8.5.13 Alternative RAB Parameters Value + +This information shall be stored by 3G\_MSC-B and sent to an RNS in Relocation Request during the basic inter-MSC relocation or when 3G\_MSC-B performs a subsequent intra-MSC relocation or handover to UMTS. + +Transfer of information: + +The Alternative RAB Parameters Value information is transferred to 3G\_MSC-B in: + +- the Relocation Request RANAP message. + +If an assignment of a Radio Access Bearer after an inter-MSC relocation is to be performed, the information is transferred to 3G\_MSC-B in: + +- the RAB Assignment Request RANAP message. + +#### 4.8.5.14 Trace parameters + +This information shall be stored by 3G\_MSC-B and 3G\_MSC-B shall use this information for trace activation for MSC-S, MGW, RNC or BSC. + +Transfer of information: + +The Trace Parameter List information for MSC-S, MGW and BSC tracing is transferred to 3G\_MSC-B in: + +- the Prepare Handover Request MAP message. + +The Trace Propagation Parameter information for RNC tracing is transferred to 3G\_MSC-B in: + +- the CN Invoke Trace RANAP message. + +### 4.8.6 Overview of the Technical Specifications 3GPP interworking for the Inter-MSC Relocation + +![Protocol stack diagram for UMTS showing layers for RNS-A, 3G-MSC-A, 3G-MSC-B, RNS-B, and MS. It includes interfaces like 25.413, 24.008, 29.010, 29.002, and 23.009, and protocols like CM, MM, RR, MAP/E, TCAP, SCCP, and MTP.](c0ca823603794512478906b302176bca_img.jpg) + +The diagram illustrates the protocol stack for a UMTS system, showing the interaction between a PSTN/ISDN, RNS-A, 3G-MSC-A, 3G-MSC-B, RNS-B, and MS. The stack is organized into layers, with specific protocols and interfaces labeled. + +- PSTN/ISDN:** The top layer, connected to the UMTS network. +- UMTS:** The main network area, containing the following components: + - RNS-A:** Radio Network Subsystem A, containing layers RR (Radio Resource). + - 3G-MSC-A:** Serving MSC A, containing layers CM (Connection Management), MM (Mobility Management), RR (Radio Resource), MAP/E (Mobile Application Part/Exchange), TCAP (Transaction Capabilities Application Part), SCCP (Signaling Connection Control Part), and MTP (Message Transfer Part). + - 3G-MSC-B:** Serving MSC B, containing layers CM, MM, RR, MAP/E, TCAP, SCCP, and MTP. + - RNS-B:** Radio Network Subsystem B, containing layers RR. + - MS:** Mobile Station, containing layers CM, MM, and RR. + +**Interfaces and Protocols:** + +- 25.413:** Interface between RNS-A and 3G-MSC-A, and between 3G-MSC-B and RNS-B. +- 24.008:** Interface between 3G-MSC-A and 3G-MSC-B. +- 29.010:** Interface between 3G-MSC-A and 3G-MSC-B. +- 29.002:** Interface between 3G-MSC-A and 3G-MSC-B. +- 23.009:** Interface between 3G-MSC-A and 3G-MSC-B. + +**Remark:** The RRC interface and the link layer protocols being out of the scope of this Specification are not shown here. + +Protocol stack diagram for UMTS showing layers for RNS-A, 3G-MSC-A, 3G-MSC-B, RNS-B, and MS. It includes interfaces like 25.413, 24.008, 29.010, 29.002, and 23.009, and protocols like CM, MM, RR, MAP/E, TCAP, SCCP, and MTP. + +## 4.9 Location Services + +The general principles of the location services procedures are given in Technical Specification 3GPP TS 23.271 [16]. + +3GPP TS 29.010 gives the necessary information for interworking between the 3GPP TS 25.413 [7] RANAP protocol and the 3GPP TS 48.008 [12] BSSMAP protocol. The interworking is necessary for positioning requests issued after a completed GSM to UMTS inter system handover. BSSMAP messages carried by MAP over the E-interface must be mapped by the non-anchor 3G-MSC into the corresponding RANAP messages to be sent over the Iu-interface and vice versa. For Inter-MSC GSM to GSM Handover and Inter-MSC UMTS to UMTS SRNS Relocation no mapping between the 3GPP TS 25.413 [7] RANAP protocol and the 3GPP TS 48.008 [12] BSSMAP protocol is necessary, but only the interworking with the MAP protocol over the E-interface needs to be described. + +### 4.9.1 Completed Location Acquisition + +#### 4.9.1.1 Inter-MSC Handover (GSM to GSM) + +After a successful Inter-MSC handover, any positioning request received by the anchor MSC via the MAP message Provide Subscriber Location triggers the BSSMAP procedure Location Acquisition described in 3GPP TS 48.008 [12]. For handover this procedure is executed according to GSM 3GPP TS 49.008 [14] with the anchor MSC playing the role of the MSC and the non anchor MSC playing the role of the BSS. + +The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non anchor MSC the BSSMAP messages received from the anchor MSC are forwarded to the BSS, and the BSSMAP messages received from the BSS are sent over the E-interface to the anchor MSC. + +The signalling for a completed Location Acquisition procedure is shown in figures 65a. + +![Sequence diagram for Figure 65a: Signalling for a completed Location Acquisition procedure. The diagram shows interactions between GMLC, MSC-A, MSC-B, and BSS-B. GMLC sends a MAP PROVIDE SUBSCRIBER LOCATION to MSC-A. MSC-A sends a MAP FORWARD ACCESS SIGNALLING to MSC-B, containing an -an-APDU (PERFORM LOCATION REQUEST). MSC-B sends a PERFORM LOCATION REQUEST to BSS-B. BSS-B performs positioning and returns a PERFORM LOCATION RESPONSE to MSC-B. MSC-B sends a MAP PROCESS ACCESS SIGNALLING to MSC-A, containing an -an-APDU (PERFORM LOCATION RESPONSE). Finally, MSC-A sends a MAP PROVIDE SUBSCRIBER LOCATION res to GMLC.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +``` + +sequenceDiagram + participant GMLC + participant MSC-A + participant MSC-B + participant BSS-B + + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION + GMLC-->>MSC-A: MAP PROVIDE SUBSCRIBER LOCATION + Note right of MSC-A: MAP FORWARD ACCESS SIGNALLING + MSC-A-->>MSC-B: MAP FORWARD ACCESS SIGNALLING + Note right of MSC-B: -an-APDU (PERFORM LOCATION REQUEST) + MSC-B-->>BSS-B: PERFORM LOCATION REQUEST + Note right of BSS-B: Positioning is performed + BSS-B-->>MSC-B: PERFORM LOCATION RESPONSE + Note right of MSC-B: MAP PROCESS ACCESS SIGNALLING + MSC-B-->>MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of MSC-A: -an-APDU (PERFORM LOCATION RESPONSE) + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION res + MSC-A-->>GMLC: MAP PROVIDE SUBSCRIBER LOCATION res + +``` + +Sequence diagram for Figure 65a: Signalling for a completed Location Acquisition procedure. The diagram shows interactions between GMLC, MSC-A, MSC-B, and BSS-B. GMLC sends a MAP PROVIDE SUBSCRIBER LOCATION to MSC-A. MSC-A sends a MAP FORWARD ACCESS SIGNALLING to MSC-B, containing an -an-APDU (PERFORM LOCATION REQUEST). MSC-B sends a PERFORM LOCATION REQUEST to BSS-B. BSS-B performs positioning and returns a PERFORM LOCATION RESPONSE to MSC-B. MSC-B sends a MAP PROCESS ACCESS SIGNALLING to MSC-A, containing an -an-APDU (PERFORM LOCATION RESPONSE). Finally, MSC-A sends a MAP PROVIDE SUBSCRIBER LOCATION res to GMLC. + +**Figure 65a: Signalling for a completed Location Acquisition procedure** + +After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. Any positioning request received by the anchor MSC after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.1.2). + +#### 4.9.1.2 Inter-MSC Handover (GSM to UMTS) + +After a successful Inter-MSC GSM to UMTS inter system handover, any positioning request received by the anchor MSC via the MAP message Provide Subscriber Location triggers the BSSMAP procedure Location Acquisition described in 3GPP TS 48.008 [12]. For handover this procedure is executed according to 3GPP TS 49.008 [14] with the anchor MSC playing the role of the MSC and the non anchor 3G MSC playing the role of the BSS. + +The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non anchor 3G MSC the BSSMAP messages received from the anchor MSC are mapped into the corresponding RANAP messages to be sent to the RNS, and the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent over the E-interface to the anchor MSC. + +The signalling for a completed Location Acquisition procedure is shown in figures 65b. + +![Sequence diagram showing signalling for a completed Location Acquisition procedure between GMLC, MSC-A, 3G-MSC-B, and RNS-B.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant MSC-A + participant 3G-MSC-B + participant RNS-B + + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION + GMLC-->>MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of MSC-A: -an-APDU( PERFORM LOCATION REQUEST) + MSC-A-->>3G-MSC-B: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-B: LOCATION REPORTING CONTROL + 3G-MSC-B-->>RNS-B: LOCATION REPORTING CONTROL + Note right of RNS-B: Positioning is performed + RNS-B-->>3G-MSC-B: LOCATION REPORT + 3G-MSC-B-->>MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of MSC-A: -an-APDU( PERFORM LOCATION RESPONSE) + MSC-A-->>GMLC: MAP PROVIDE SUBSCRIBER LOCATION res +``` + +The diagram illustrates the signalling flow for a completed location acquisition procedure. It involves four main entities: GMLC, MSC-A, 3G-MSC-B, and RNS-B. The sequence starts with GMLC sending a 'MAP PROVIDE SUBSCRIBER LOCATION' message to MSC-A. MSC-A then sends a 'MAP FORWARD ACCESS SIGNALLING' message to 3G-MSC-B, which contains an '-an-APDU( PERFORM LOCATION REQUEST)'. 3G-MSC-B sends a 'LOCATION REPORTING CONTROL' message to RNS-B. RNS-B performs the positioning and sends a 'LOCATION REPORT' back to 3G-MSC-B. 3G-MSC-B then sends a 'MAP PROCESS ACCESS SIGNALLING' message to MSC-A, which contains an '-an-APDU( PERFORM LOCATION RESPONSE)'. Finally, MSC-A sends a 'MAP PROVIDE SUBSCRIBER LOCATION res' message back to GMLC. A dashed box labeled 'Positioning is performed' is shown between the 'LOCATION REPORTING CONTROL' and 'LOCATION REPORT' messages. + +Sequence diagram showing signalling for a completed Location Acquisition procedure between GMLC, MSC-A, 3G-MSC-B, and RNS-B. + +**Figure 65b: Signalling for a completed Location Acquisition procedure** + +The interworking between the BSSMAP location acquisition messages in MAP and the RANAP location reporting messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG. request
-an-APDU(
PERFORM LOCATION REQUEST)
BSSMAP information elements:
Location Type
>Current Geographic Location
Cell Identifier
Classmark Inf. Type3
LCS Client Type
Chosen Channel
LCS Priority
LCS QoS
>Horizontal Accuracy
GPS Assistance Data APDU | LOCATION REPORTING CONTROL
RANAP information elements:
Request Type
>Event = Direct
>Report Area = Geo. Coord.
-----
-----
-----
-----
-----
Request Type
>Accuracy Code
-----
----- | 1 | +| Result | MAP PROCESS ACCESS SIG. request
-an-APDU(
PERFORM LOCATION RESPONSE)
BSSMAP information elements:
Location Estimate
Positioning Data
Deciphering Keys
LCS Cause
----- | LOCATION REPORT
RANAP information elements:
Area Identity
>Geographical Area
-----
-----
Cause
Request Type | | + +NOTE 1: All other Location Type possibilities are not supported by UMTS positioning + +After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any positioning request received by the anchor MSC after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see clause 4.9.1.1). + +#### 4.9.1.3 Inter-MSC Handover (UMTS to GSM) + +After a successful Inter-MSC UMTS to GSM inter system handover, any positioning request received by the anchor 3G-MSC via the MAP message Provide Subscriber Location triggers the BSSMAP procedure Location Acquisition described in 3GPP TS 48.008 [12]. For handover this procedure is executed according to 3GPP TS 49.008 [14] with the anchor 3G-MSC playing the role of the 3G-MSC and the non anchor MSC playing the role of the BSS. + +The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non anchor MSC the BSSMAP messages received from the anchor 3G-MSC are forwarded to the BSS, and the BSSMAP messages received from the BSS are sent over the E-interface to the anchor 3G-MSC. + +The signalling for a completed Location Acquisition procedure is shown in figures 65c. + +![Sequence diagram for Figure 65c: Signalling for a completed Location Acquisition procedure. Lifelines: GMLC, 3G- MSC-A, MSC-B, BSS-B. The sequence shows the GMLC sending a MAP PROVIDE SUBSCRIBER LOCATION to 3G- MSC-A, which then sends a MAP FORWARD ACCESS SIGNALLING to MSC-B. MSC-B sends a PERFORM LOCATION REQUEST to BSS-B. BSS-B performs positioning and returns a PERFORM LOCATION RESPONSE to MSC-B. MSC-B then sends a MAP PROCESS ACCESS SIGNALLING back to 3G- MSC-A, which finally sends a MAP PROVIDE SUBSCRIBER LOCATION res back to the GMLC. The MAP messages contain an-an-APDU with PERFORM LOCATION REQUEST or RESPONSE.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +``` + +sequenceDiagram + participant GMLC + participant 3G- MSC-A + participant MSC-B + participant BSS-B + + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION + GMLC-->>3G- MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of 3G- MSC-A: -an-APDU( PERFORM LOCATION REQUEST) + 3G- MSC-A-->>MSC-B: MAP FORWARD ACCESS SIGNALLING + Note right of MSC-B: PERFORM LOCATION REQUEST + Note right of BSS-B: Positioning is performed + BSS-B-->>MSC-B: PERFORM LOCATION RESPONSE + MSC-B-->>3G- MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of 3G- MSC-A: -an-APDU( PERFORM LOCATION RESPONSE) + 3G- MSC-A-->>GMLC: MAP PROVIDE SUBSCRIBER LOCATION res + +``` + +Sequence diagram for Figure 65c: Signalling for a completed Location Acquisition procedure. Lifelines: GMLC, 3G- MSC-A, MSC-B, BSS-B. The sequence shows the GMLC sending a MAP PROVIDE SUBSCRIBER LOCATION to 3G- MSC-A, which then sends a MAP FORWARD ACCESS SIGNALLING to MSC-B. MSC-B sends a PERFORM LOCATION REQUEST to BSS-B. BSS-B performs positioning and returns a PERFORM LOCATION RESPONSE to MSC-B. MSC-B then sends a MAP PROCESS ACCESS SIGNALLING back to 3G- MSC-A, which finally sends a MAP PROVIDE SUBSCRIBER LOCATION res back to the GMLC. The MAP messages contain an-an-APDU with PERFORM LOCATION REQUEST or RESPONSE. + +**Figure 65c: Signalling for a completed Location Acquisition procedure** + +After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. Any positioning request received by the anchor 3G MSC after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.1.2). + +#### 4.9.1.4 Inter-MSC SRNS Relocation + +After a successful Inter-MSC SRNS Relocation, any positioning request received by the anchor 3G-MSC via the MAP message Provide Subscriber Location triggers the RANAP procedure Location Reporting Control described in TS 25.413. For handover this procedure is executed according to 23.009 with the anchor 3G-MSC playing the role of the 3G-MSC and the non anchor 3G-MSC playing the role of the RNS. + +The needed RANAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non anchor 3G-MSC the RANAP messages received from the anchor 3G-MSC are forwarded to the RNS, and the RANAP messages received from the RNS are sent over the E-interface to the anchor 3G-MSC. + +The signalling for a completed Location Acquisition procedure is shown in figures 65d. + +![Sequence diagram showing signalling for a completed Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and RNS-B.](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION + GMLC-->>3G-MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU ( LOCATION REPORTING CONTROL) + 3G-MSC-A-->>3G-MSC-B: + Note right of 3G-MSC-B: LOCATION REPORTING CONTROL + Note right of RNS-B: Positioning is performed + RNS-B-->>3G-MSC-B: LOCATION REPORT + 3G-MSC-B-->>3G-MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU ( LOCATION REPORT) + 3G-MSC-A-->>GMLC: MAP PROVIDE SUBSCRIBER LOCATION res +``` + +The sequence diagram illustrates the signalling for a completed Location Acquisition procedure. It involves four main entities: GMLC, 3G-MSC-A, 3G-MSC-B, and RNS-B. The process begins with GMLC sending a 'MAP PROVIDE SUBSCRIBER LOCATION' message to 3G-MSC-A. 3G-MSC-A responds with 'MAP FORWARD ACCESS SIGNALLING', which contains an '-an-APDU ( LOCATION REPORTING CONTROL)'. This message is forwarded to 3G-MSC-B. 3G-MSC-B then sends a 'LOCATION REPORTING CONTROL' message to RNS-B. RNS-B performs the positioning and sends a 'LOCATION REPORT' back to 3G-MSC-B. 3G-MSC-B processes this with 'MAP PROCESS ACCESS SIGNALLING', containing an '-an-APDU ( LOCATION REPORT)', and forwards it to 3G-MSC-A. Finally, 3G-MSC-A sends a 'MAP PROVIDE SUBSCRIBER LOCATION res' message back to GMLC. + +Sequence diagram showing signalling for a completed Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and RNS-B. + +**Figure 65d: Signalling for a completed Location Acquisition procedure** + +After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any positioning request received by the anchor 3G MSC after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC. + +The signalling for a completed Location Acquisition procedure is shown in figures 65e. + +![Sequence diagram showing signalling for a completed Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and BSS-B.](737abf1e655afd3324b6b3987945d913_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant 3G-MSC-A + participant 3G-MSC-B + participant BSS-B + + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION + GMLC-->>3G-MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU( LOCATION REPORTING CONTROL) + 3G-MSC-A-->>3G-MSC-B: + Note right of 3G-MSC-B: PERFORM LOCATION REQUEST + 3G-MSC-B-->>BSS-B: + Note right of BSS-B: Positioning is performed + BSS-B-->>3G-MSC-B: + Note right of 3G-MSC-B: PERFORM LOCATION RESPONSE + 3G-MSC-B-->>3G-MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU( LOCATION REPORT) + 3G-MSC-A-->>GMLC: + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION res +``` + +Sequence diagram showing signalling for a completed Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and BSS-B. + +Figure 65e: Signalling for a completed Location Acquisition procedure + +the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG. request

-an-APDU(
LOCATION REPORTING CONTROL)

RANAP information elements:

Request Type
>Event = Direct
>Report Area =
Geo. Coord.

Request Type
>Accuracy Code | PERFORM LOCATION REQUEST


BSSMAP information elements:

Location Type
>Current Geographic Location

LCS QoS
>Horizontal Accuracy | | +| Result | MAP PROCESS ACCESS SIG. request

-an-APDU(
LOCATION REPORT)

RANAP information elements:

Area Identity
>Geographical Area

Cause
Request Type | PERFORM LOCATION RESPONSE


BSSMAP information elements:

Location Estimate

LCS Cause
---- | | + +### 4.9.2 Cause Code Mapping + +#### 4.9.2.1 Inter-MSC Handover (GSM to GSM) + +When a mobile station is handed over from GSM to GSM, no mapping of cause codes is required. The MSC shall use the cause codes specified in 3GPP TS 48.008 [12]. + +After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. A mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed after completion of the intra-MSC GSM to UMTS handover and is the same as for Inter-MSC Handover GSM to UMTS (see clause 4.9.2.2).. + +#### 4.9.2.2 Inter-MSC Handover (GSM to UMTS) + +When a Mobile Station is handed over between GSM and UMTS, a mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed. The mapping described here is applicable to the BSSMAP protocol even when used inside MAP in the E-interface. + +The mapping between the cause codes received in RANAP Location Report and the LCS cause codes sent in BSSMAP Perform Location Response is as follows: + +| 25.413 | 48.008 | Notes | +|---------------------------------------|---------------------------|-------| +| LOCATION REPORT | PERFORM LOCATION RESPONSE | | +| - Requested Report Type not Supported | - Position method failure | | +| - Requested Information not Available | - Position method failure | | +| - all other cause codes | - System Failure | | + +After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. No mapping of cause codes is required after completion of the intra-MSC UMTS to GSM handover as for Inter-MSC Handover GSM to GSM (see clause 4.9.2.1). + +#### 4.9.2.3 Inter-MSC Handover (UMTS to GSM) + +When a mobile station is handed over from UMTS to GSM, no mapping of cause codes is required. The 3G-MSC shall use the cause codes specified in 3GPP TS 48.008 [12]. + +After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. A mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed after completion of the intra-MSC GSM to UMTS handover and is the same as for Inter-MSC Handover GSM to UMTS (see clause 4.9.2.2)... + +#### 4.9.2.4 Inter-MSC SRNS Relocation + +When a mobile station is handed over from UMTS to UMTS, no mapping of cause codes is required. Both 3G-MSCs shall use the cause codes specified in TS 25.413. + +After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. A mapping of the cause codes used in the RANAP and the BSSMAP protocols is needed after completion of the intra-MSC UMTS to GSM handover. + +The mapping between the cause codes received in BSSMAP Perform Location Response and the LCS cause codes sent in RANAP Location Report is as follows: + +| 48.008 | 25.413 | Notes | +|---------------------------------------------|---------------------------------------|-------| +| PERFORM LOCATION RESPONSE | LOCATION REPORT | | +| - Position method failure | - Requested Report Type not Supported | | +| - System Failure | - Unspecified Failure | | +| - Protocol Error | - Unspecified Failure | | +| - Data missing in position request | - Unspecified Failure | | +| - Unexpected data value in position request | - Unspecified Failure | | +| - Target MS Unreachable | - Unspecified Failure | | +| - Location request aborted | - Unspecified Failure | | +| - Facility not supported | - Requested Report Type not Supported | | +| - Inter-BSC Handover Ongoing | - Unspecified Failure | | +| - Intra-BSC Handover Complete | - Unspecified Failure | | +| - Congestion | - Unspecified Failure | | +| - Unspecified | - Unspecified Failure | | + +### 4.9.3 Aborted Location Acquisition + +#### 4.9.3.1 Inter-MSC Handover (GSM to GSM) + +When for any reason the on going location acquisition procedure needs to be aborted, the anchor MSC sends the BSSMAP message Perform Location Abort over the E-interface. + +Figure 66a shows the signalling for an aborted Location Acquisition procedure. + +![Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, MSC-A, MSC-B, and BSS-B.](521e2e9d53a2d9c4b3e22d151d46ee23_img.jpg) + +The diagram illustrates the following sequence of messages: + +- GMLC** sends a **MAP PROVIDE SUBSCRIBER LOCATION** message to **MSC-A**. +- MSC-A** sends a **MAP FORWARD ACCESS SIGNALLING** message to **MSC-B**, containing an **-an-APDU (PERFORM LOCATION REQUEST)**. +- MSC-B** sends a **PERFORM LOCATION REQUEST** message to **BSS-B**. +- MSC-A** sends another **MAP FORWARD ACCESS SIGNALLING** message to **MSC-B**, containing an **-an-APDU (PERFORM LOCATION ABORT)**. +- MSC-B** sends a **PERFORM LOCATION ABORT** message to **BSS-B**. +- BSS-B** sends a **PERFORM LOCATION RESPONSE** message back to **MSC-B**. +- MSC-B** sends a **MAP PROCESS ACCESS SIGNALLING** message back to **MSC-A**, containing an **-an-APDU (PERFORM LOCATION RESPONSE)**. + +Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, MSC-A, MSC-B, and BSS-B. + +Figure 66a: Signalling for an aborted Location Acquisition procedure + +After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. A positioning request that needs to be aborted by the anchor MSC after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.3.2). + +#### 4.9.3.2 Inter-MSC Handover (GSM to UMTS) + +When for any reason the on going location acquisition procedure needs to be aborted, the anchor MSC sends the BSSMAP message Perform Location Abort over the E-interface. + +Figure 66b shows the signalling for an aborted Location Acquisition procedure. + +![Figure 66b: Signalling for an aborted Location Acquisition procedure](17431d8b59408f09df7552d8bdbaa015_img.jpg) + +``` + +sequenceDiagram + participant GMLC + participant MSC-A + participant 3G-MSC-B + participant RNS-B + + Note left of GMLC: MAP PROVIDE +SUBSCRIBER +LOCATION + GMLC->>MSC-A: + Note right of MSC-A: MAP FORWARD ACCESS +SIGNALLING + MSC-A->>3G-MSC-B: + Note right of MSC-A: -an-APDU( +PERFORM LOCATION +REQUEST) + Note right of 3G-MSC-B: LOCATION REPORTING +CONTROL + 3G-MSC-B->>RNS-B: + Note right of MSC-A: MAP FORWARD ACCESS +SIGNALLING + MSC-A->>3G-MSC-B: + Note right of MSC-A: -an-APDU( +PERFORM LOCATION ABORT) + Note right of 3G-MSC-B: LOCATION REPORTING +CONTROL + 3G-MSC-B->>RNS-B: + Note right of 3G-MSC-B: LOCATION REPORT + RNS-B->>3G-MSC-B: + Note right of MSC-A: MAP PROCESS ACCESS +SIGNALLING + 3G-MSC-B->>MSC-A: + Note right of MSC-A: -an-APDU( +PERFORM LOCATION +RESPONSE) + +``` + +Detailed description of Figure 66b signaling flow: +1. The procedure starts with a **MAP PROVIDE SUBSCRIBER LOCATION** request from GMLC to MSC-A. +2. MSC-A sends a **MAP FORWARD ACCESS SIGNALLING** message to 3G-MSC-B. This message contains an **-an-APDU(PERFORM LOCATION REQUEST)**. +3. 3G-MSC-B then sends a **LOCATION REPORTING CONTROL** message to RNS-B. +4. Subsequently, MSC-A sends another **MAP FORWARD ACCESS SIGNALLING** message to 3G-MSC-B, this time containing an **-an-APDU(PERFORM LOCATION ABORT)**. +5. 3G-MSC-B sends a **LOCATION REPORTING CONTROL** message to RNS-B. +6. RNS-B responds to 3G-MSC-B with a **LOCATION REPORT**. +7. Finally, 3G-MSC-B sends a **MAP PROCESS ACCESS SIGNALLING** message back to MSC-A, containing an **-an-APDU(PERFORM LOCATION RESPONSE)**. + +Figure 66b: Signalling for an aborted Location Acquisition procedure + +**Figure 66b: Signalling for an aborted Location Acquisition procedure** + +The interworking between the BSSMAP location acquisition messages in MAP and the RANAP location reporting messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG. request
-an-APDU(
PERFORM LOCATION ABORT)
BSSMAP information elements:
LCS Cause | LOCATION REPORTING CONTROL
RANAP information elements:
Request Type
>Event = Stop
>Report Area = Geo. Coord. | | +| Result | MAP PROCESS ACCESS SIG. request
-an-APDU(
PERFORM LOCATION RESPONSE)
BSSMAP information elements:
LCS Cause | LOCATION REPORT
RANAP information elements:
Cause | 1 | + +NOTE 1: PERFORM LOCATION RESPONSE with LCS cause shall be generated by 3G-MSC-B. + +After the inter- MSC GSM to UMTS handover, the 3G MSC-B can perform intra- MSC UMTS to GSM handover. A positioning request that needs to be aborted by the anchor MSC after completion of the intra- MSC UMTS to GSM handover is handled as for Inter- MSC Handover GSM to GSM (see clause 4.9.3.1). + +#### 4.9.3.3 Inter- MSC Handover (UMTS to GSM) + +When for any reason the on going location acquisition procedure needs to be aborted, the anchor 3G- MSC sends the BSSMAP message Perform Location Abort over the E-interface. + +Figure 66c shows the signalling for an aborted Location Acquisition procedure. + +![Sequence diagram for an aborted Location Acquisition procedure. The diagram shows four vertical lifelines: GMLC, 3G-MSC-A, MSC-B, and BSS-B. 1. A dashed arrow labeled 'MAP PROVIDE SUBSCRIBER LOCATION' goes from GMLC to 3G-MSC-A. 2. A dashed arrow labeled 'MAP FORWARD ACCESS SIGNALLING' and '-an-APDU( PERFORM LOCATION REQUEST)' goes from 3G-MSC-A to MSC-B. 3. A dashed arrow labeled 'PERFORM LOCATION REQUEST' goes from MSC-B to BSS-B. 4. A second dashed arrow labeled 'MAP FORWARD ACCESS SIGNALLING' and '-an-APDU( PERFORM LOCATION ABORT)' goes from 3G-MSC-A to MSC-B. 5. A dashed arrow labeled 'PERFORM LOCATION ABORT' goes from MSC-B to BSS-B. 6. A dashed arrow labeled 'PERFORM LOCATION RESPONSE' returns from BSS-B to MSC-B. 7. A final dashed arrow labeled 'MAP PROCESS ACCESS SIGNALLING' and '-an-APDU( PERFORM LOCATION RESPONSE)' returns from MSC-B to 3G-MSC-A.](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +``` + +sequenceDiagram + participant GMLC + participant 3G-MSC-A + participant MSC-B + participant BSS-B + + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION + GMLC-->>3G-MSC-A: + Note right of 3G-MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU( PERFORM LOCATION REQUEST) + 3G-MSC-A-->>MSC-B: + MSC-B-->>BSS-B: PERFORM LOCATION REQUEST + Note right of 3G-MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU( PERFORM LOCATION ABORT) + 3G-MSC-A-->>MSC-B: + MSC-B-->>BSS-B: PERFORM LOCATION ABORT + BSS-B-->>MSC-B: PERFORM LOCATION RESPONSE + Note right of 3G-MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU( PERFORM LOCATION RESPONSE) + MSC-B-->>3G-MSC-A: + +``` + +Sequence diagram for an aborted Location Acquisition procedure. The diagram shows four vertical lifelines: GMLC, 3G-MSC-A, MSC-B, and BSS-B. 1. A dashed arrow labeled 'MAP PROVIDE SUBSCRIBER LOCATION' goes from GMLC to 3G-MSC-A. 2. A dashed arrow labeled 'MAP FORWARD ACCESS SIGNALLING' and '-an-APDU( PERFORM LOCATION REQUEST)' goes from 3G-MSC-A to MSC-B. 3. A dashed arrow labeled 'PERFORM LOCATION REQUEST' goes from MSC-B to BSS-B. 4. A second dashed arrow labeled 'MAP FORWARD ACCESS SIGNALLING' and '-an-APDU( PERFORM LOCATION ABORT)' goes from 3G-MSC-A to MSC-B. 5. A dashed arrow labeled 'PERFORM LOCATION ABORT' goes from MSC-B to BSS-B. 6. A dashed arrow labeled 'PERFORM LOCATION RESPONSE' returns from BSS-B to MSC-B. 7. A final dashed arrow labeled 'MAP PROCESS ACCESS SIGNALLING' and '-an-APDU( PERFORM LOCATION RESPONSE)' returns from MSC-B to 3G-MSC-A. + +**Figure 66c: Signalling for an aborted Location Acquisition procedure** + +After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. A positioning request that needs to be aborted by the anchor 3G MSC after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.3.2).. + +#### 4.9.3.4 Inter-MSC SRNS Relocation + +When for any reason the on going location acquisition procedure needs to be aborted, the anchor 3G-MSC sends the RANAP message Location Reporting Control over the E-interface. + +Figure 66d shows the signalling for an aborted Location Acquisition procedure. + +![Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and RNS-B.](40b80ef077f6151a9fbb593b8ad4864d_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant 3G-MSC-A + participant 3G-MSC-B + participant RNS-B + + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION + GMLC-->>3G-MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU ( LOCATION REPORTING CONTROL) + 3G-MSC-A-->>3G-MSC-B: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-B: LOCATION REPORTING CONTROL + 3G-MSC-B-->>RNS-B: LOCATION REPORTING CONTROL + Note right of 3G-MSC-A: -an-APDU ( LOCATION REPORTING CONTROL = STOP) + 3G-MSC-A-->>3G-MSC-B: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-B: LOCATION REPORTING CONTROL = STOP DIRECT + 3G-MSC-B-->>RNS-B: LOCATION REPORTING CONTROL + Note right of 3G-MSC-B: LOCATION REPORT + 3G-MSC-B-->>3G-MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU ( LOCATION REPORT) +``` + +Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and RNS-B. + +Figure 66d: Signalling for an aborted Location Acquisition procedure + +After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. A positioning request that needs to be aborted by the anchor 3G MSC after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC. + +The signalling for a completed Location Acquisition procedure is shown in figures 65e. + +![Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and BSS-B.](6348f4fc8b3848158fcfbe85e26a731d_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant 3G-MSC-A + participant 3G-MSC-B + participant BSS-B + + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION + GMLC-->>3G-MSC-A: MAP FORWARD ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU ( LOCATION REPORTING CONTROL) + 3G-MSC-A-->>3G-MSC-B: + Note right of 3G-MSC-B: + 3G-MSC-B-->>BSS-B: + Note right of BSS-B: + BSS-B-->>3G-MSC-B: PERFORM LOCATION ABORT + Note right of 3G-MSC-B: + 3G-MSC-B-->>BSS-B: PERFORM LOCATION RESPONSE + Note right of BSS-B: + 3G-MSC-B-->>3G-MSC-A: MAP PROCESS ACCESS SIGNALLING + Note right of 3G-MSC-A: -an-APDU ( LOCATION REPORT) + 3G-MSC-A-->>GMLC: + Note left of GMLC: MAP PROVIDE SUBSCRIBER LOCATION res +``` + +The sequence diagram illustrates the signalling for an aborted Location Acquisition procedure. It involves four entities: GMLC, 3G-MSC-A, 3G-MSC-B, and BSS-B. The process begins with GMLC sending a MAP PROVIDE SUBSCRIBER LOCATION message to 3G-MSC-A. 3G-MSC-A responds with a MAP FORWARD ACCESS SIGNALLING message, which contains an -an-APDU ( LOCATION REPORTING CONTROL). This message is forwarded to 3G-MSC-B. 3G-MSC-B then sends a message to BSS-B. BSS-B responds with a PERFORM LOCATION ABORT message to 3G-MSC-B. 3G-MSC-B then sends a PERFORM LOCATION RESPONSE message to BSS-B. Finally, 3G-MSC-B sends a MAP PROCESS ACCESS SIGNALLING message to 3G-MSC-A, which contains an -an-APDU ( LOCATION REPORT). 3G-MSC-A then sends a MAP PROVIDE SUBSCRIBER LOCATION res message back to GMLC. + +Sequence diagram showing signalling for an aborted Location Acquisition procedure between GMLC, 3G-MSC-A, 3G-MSC-B, and BSS-B. + +Figure 65e: Signalling for an aborted Location Acquisition procedure + +the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG.
request

-an-APDU(
LOCATION REPORTING CONTROL)

RANAP information elements:

Request Type
>Event = Stop Direct
>Report Area =
Geo. Coord. | PERFORM LOCATION
ABORT


BSSMAP information elements:

LCS Cause
> Location request
aborted | | +| Result | MAP PROCESS ACCESS SIG.
request

-an-APDU(
LOCATION REPORT)

RANAP information elements:

Cause
>Unspecified
Failure | PERFORM LOCATION
RESPONSE


BSSMAP information elements:

LCS Cause
> Location request
aborted | | + +### 4.9.4 Request of Assistance Data or De-ciphering Keys: Successful Case + +#### 4.9.4.1 Inter-MSC Handover (GSM to GSM) + +After a successful Inter-MSC handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is forwarded to the anchor MSC by encapsulating the DTAP message into the MAP messages Process Access Signalling. The anchor MSC triggers the BSSMAP procedure Location Acquisition described in 3G TS 48.008. For handover this procedure is executed according to 3G TS 49.008 with the anchor MSC playing the role of the MSC and the non anchor MSC playing the role of the BSS. + +The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non anchor MSC the BSSMAP messages received from the anchor MSC are forwarded to the BSS, and the BSSMAP messages received from the BSS are sent over the E-interface to the anchor MSC. + +Once the BSSMAP procedure has been completed, the anchor MSC sends the DTAP message LCS-MOLR Response encapsulated in the MAP message Forward Access Signalling to the non anchor MSC, which relays it to the MS. + +The signalling for a completed request of Assistance Data or De-ciphering Keys is shown in figures 67a. + +![Sequence diagram for Figure 67a: Signalling for the request of Assistance Data or De-ciphering Keys. The diagram shows interactions between MSC-A, MSC-B, BSS-B, and MS. MSC-B receives an LCS-MOLR from the MS and forwards it to MSC-A via MAP PROCESS ACCESS SIGNALLING. MSC-A then sends a MAP FORWARD ACCESS SIGNALLING message to MSC-B containing a perform location request. MSC-B forwards this to BSS-B. A conditional block indicates that if assistance data was requested, it is delivered to the MS. Finally, a response is returned from BSS-B through MSC-B to the MS via an LCS-MOLR Response message.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC-B + participant MSC-A + participant BSS-B + + Note right of MS: LCS-MOLR + MS-->>MSC-B: LCS-MOLR + Note left of MSC-B: MAP PROCESS ACCESS SIGNALLING + MSC-B-->>MSC-A: -an-APDU(LCS-MOLR) + Note left of MSC-A: MAP FORWARD ACCESS SIGNALLING + MSC-A-->>MSC-B: -an-APDU( PERFORM LOCATION REQUEST) + Note left of MSC-B: + MSC-B-->>BSS-B: + Note left of BSS-B: PERFORM LOCATION REQUEST + alt If Assistance Data were requested then Delivery of Assistance Data to MS + Note right of BSS-B: + BSS-B-->>MSC-B: PERFORM LOCATION RESPONSE + Note left of MSC-B: MAP PROCESS ACCESS SIGNALLING + MSC-B-->>MSC-A: -an-APDU( PERFORM LOCATION RESPONSE) + Note left of MSC-A: MAP FORWARD ACCESS SIGNALLING + MSC-A-->>MSC-B: -an-APDU( LCS-MOLR Response) + Note left of MSC-B: + MSC-B-->>MS: LCS-MOLR Response + +``` + +Sequence diagram for Figure 67a: Signalling for the request of Assistance Data or De-ciphering Keys. The diagram shows interactions between MSC-A, MSC-B, BSS-B, and MS. MSC-B receives an LCS-MOLR from the MS and forwards it to MSC-A via MAP PROCESS ACCESS SIGNALLING. MSC-A then sends a MAP FORWARD ACCESS SIGNALLING message to MSC-B containing a perform location request. MSC-B forwards this to BSS-B. A conditional block indicates that if assistance data was requested, it is delivered to the MS. Finally, a response is returned from BSS-B through MSC-B to the MS via an LCS-MOLR Response message. + +**Figure 67a: Signalling for the request of Assistance Data or De-ciphering Keys** + +After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.4.2). + +#### 4.9.4.2 Inter-MSC Handover (GSM to UMTS) + +After a successful Inter-MSC GSM to UMTS inter system handover, any request of Assistance Data or De-ciphering keys received by the non-anchor 3G MSC via the DTAP message LCS-MOLR is forwarded to the anchor MSC by encapsulating the DTAP message into the MAP messages Process Access Signalling. The anchor MSC triggers the BSSMAP procedure Location Acquisition described in 3G TS 48.008. For handover this procedure is executed according to 3G TS 49.008 with the anchor MSC playing the role of the MSC and the non anchor 3G MSC playing the role of the BSS. + +The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non-anchor 3G MSC the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent to the RNS, and the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent over the E-interface to the anchor MSC. + +Once the BSSMAP procedure has been completed, the anchor MSC sends the DTAP message LCS-MOLR Response encapsulated in the MAP message Forward Access Signalling to the non anchor 3G MSC, which relays it to the UE. + +The signalling for a completed request of Assistance Data or De-ciphering Keys is shown in figures 67b. + +![Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between MSC-A, 3G MSC-B, RNS-B, and UE.](8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg) + +The sequence diagram illustrates the following interactions: + +- UE to 3G MSC-B:** LCS-MOLR (dashed line) +- 3G MSC-B to MSC-A:** MAP PROCESS ACCESS SIGNALLING with -an-APDU (LCS-MOLR) (dashed line) +- MSC-A to 3G MSC-B:** MAP FORWARD ACCESS SIGNALLING with -an-APDU (PERFORM LOCATION REQUEST) (dashed line) +- 3G MSC-B to RNS-B:** LOCATION RELATED DATA REQUEST (dashed line) +- Inside a box labeled 'If Assistance Data were requested then Delivery of Assistance Data to UE':** + - RNS-B to 3G MSC-B:** LOCATION RELATED DATA RESPONSE (dashed line) +- 3G MSC-B to MSC-A:** MAP PROCESS ACCESS SIGNALLING with -an-APDU (PERFORM LOCATION RESPONSE) (dashed line) +- MSC-A to 3G MSC-B:** MAP FORWARD ACCESS SIGNALLING with -an-APDU (LCS-MOLR Response) (dashed line) +- 3G MSC-B to UE:** LCS-MOLR Response (dashed line) + +Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between MSC-A, 3G MSC-B, RNS-B, and UE. + +Figure 67b: Signalling for the request of Assistance Data or De-ciphering Keys + +When the UE requires the delivery of Assistance Data for the GPS Assisted positioning method, the interworking between the BSSMAP messages encapsulated in MAP and the RANAP messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG. request
-an-APDU(
PERFORM LOCATION REQUEST)
BSSMAP information elements:
Location Type.
Location Information
> location assistance info for target MS
Location Type.
Positioning Method
> Assisted GPS
GPS Assistance Data | LOCATION RELATED DATA REQUEST
RANAP information elements:
Requested Location Related Data Type
>Dedicated Assistance Data for Assisted GPS
Requested GPS Assistance Data | 1 | +| Result | MAP PROCESS ACCESS SIG. request
-an-APDU(
PERFORM LOCATION RESPONSE)
BSSMAP information elements: | LOCATION RELATED DATA RESPONSE
RANAP information elements: | 2 | + +NOTE 1: All other Positioning Method possibilities are not supported by UMTS when Location Information is "location assistance information for the target MS". + +NOTE 2: The absence of the Cause IE in the RANAP message Location Related Data Response is an indication that the requested assistance data has been successfully delivered to the UE.. + +If the UE requires the delivery of Assistance Data for an UMTS specific method, then the anchor MSC cannot forward the request to the non anchor 3G MSC, and replies with the error "System"to the LCS-MOLR message. + +If the anchor MSC sends a request for assistance data for a GSM specific method in BSSMAP Perform Location Request encapsulated in MAP Forward Access Signalling, then the non anchor 3G MSC replies immediately by generating and encapsulating BSSMAP Perform Location Response with Cause "System Failure" in MAP Process Access Signalling. This traffic case can happen if an LCS-MOLR had been received in the anchor MSC before the initiation of the handover procedure. + +When the UE requires the delivery of De-ciphering Keys for the GPS Assisted positioning method, the interworking between the BSSMAP messages encapsulated in MAP and the RANAP messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG. request
-an-APDU(
PERFORM LOCATION REQUEST)
BSSMAP information elements:
Location Type.
Location.Information
> deciphering keys
for broadcast
assistance data
for the target MS
Location Type.
Positioning Method
> Assisted GPS | LOCATION RELATED DATA REQUEST
RANAP information elements:
Requested Location
Related Data Type
> Deciphering Keys
for Assisted GPS | 1 | +| Result | MAP PROCESS ACCESS SIG. request
-an-APDU(
PERFORM LOCATION RESPONSE)
BSSMAP information elements:
Deciphering Keys | LOCATION RELATED DATA RESPONSE
RANAP information elements:
Broadcast Assistance
Data Deciphering Keys | | + +NOTE 1: All other Positioning Method possibilities are not supported by UMTS when Location Information is "deciphering keys for broadcast assistance data for the target MS". + +If the UE requires the delivery of De-ciphering Keys for an UMTS specific method, then the anchor MSC cannot forward the request to the non anchor 3G MSC, and replies with the error "System" to the LCS-MOLR message. + +If the anchor MSC sends a request for De-ciphering Keys for a GSM specific method in BSSMAP Perform Location Request encapsulated in MAP Forward Access Signalling, then the non anchor 3G MSC replies immediately by generating and encapsulating BSSMAP Perform Location Response with Cause "System Failure" in MAP Process Access Signalling. This traffic case can happen if an LCS-MOLR had been received in the anchor MSC before the initiation of the handover procedure. + +After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see clause 4.9.4.1). + +#### 4.9.4.3 Inter-MSC Handover (UMTS to GSM) + +After a successful Inter-MSC UMTS to GSM inter system handover, any request of Assistance Data or De-ciphering keys received by the non-anchor MSC via the DTAP message LCS-MOLR is forwarded to the anchor 3G MSC by encapsulating the DTAP message into the MAP messages Process Access Signalling. The anchor 3G MSC triggers the BSSMAP procedure Location Acquisition described in 3G TS 48.008. For handover this procedure is executed according to 3G TS 49.008 with the anchor 3G MSC playing the role of the MSC and the non-anchor MSC playing the role of the BSS. + +The needed BSSMAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non-anchor MSC the BSSMAP messages received from the anchor 3G MSC are forwarded to the BSS, and the BSSMAP messages received from the BSS are sent over the E-interface to the anchor 3G MSC. + +Once the BSSMAP procedure has been completed, the anchor 3G MSC sends the DTAP message LCS-MOLR Response encapsulated in the MAP message Forward Access Signalling to the non-anchor MSC, which relays it to the UE. + +The signalling for a completed request of Assistance Data or De-ciphering Keys is shown in figures 67c. + +![Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, MSC-B, BSS-B, and MS.](f1ba1e68228ebd4c3109371574a723e6_img.jpg) + +``` + +sequenceDiagram + participant 3G MSC-A + participant MSC-B + participant BSS-B + participant MS + + Note left of MSC-B: LCS-MOLR + MSC-B-->MS: LCS-MOLR + Note left of 3G MSC-A: MAP PROCESS ACCESS SIGNALLING + 3G MSC-A-->MSC-B: -an-APDU(LCS-MOLR) + Note left of 3G MSC-A: MAP FORWARD ACCESS SIGNALLING + 3G MSC-A-->MSC-B: -an-APDU(PERFORM LOCATION REQUEST) + MSC-B-->BSS-B: PERFORM LOCATION REQUEST + Note right of BSS-B: If Assistance Data were requested then Delivery of Assistance Data to MS + BSS-B-->MSC-B: PERFORM LOCATION RESPONSE + Note left of 3G MSC-A: MAP PROCESS ACCESS SIGNALLING + 3G MSC-A-->MSC-B: -an-APDU(PERFORM LOCATION RESPONSE) + Note left of 3G MSC-A: MAP FORWARD ACCESS SIGNALLING + 3G MSC-A-->MSC-B: -an-APDU(LCS-MOLR Response) + MSC-B-->MS: LCS-MOLR Response + +``` + +The sequence diagram illustrates the signalling flow for a completed request of Assistance Data or De-ciphering Keys. It involves four main entities: 3G MSC-A, MSC-B, BSS-B, and MS. The process begins with MSC-B sending an LCS-MOLR message to the MS. Simultaneously, 3G MSC-A sends a MAP PROCESS ACCESS SIGNALLING message to MSC-B containing an -an-APDU(LCS-MOLR). Next, 3G MSC-A sends a MAP FORWARD ACCESS SIGNALLING message to MSC-B containing an -an-APDU(PERFORM LOCATION REQUEST). MSC-B then sends a PERFORM LOCATION REQUEST to BSS-B. A conditional block indicates that if Assistance Data were requested, the delivery of Assistance Data to the MS occurs. BSS-B sends a PERFORM LOCATION RESPONSE back to MSC-B. 3G MSC-A then sends another MAP PROCESS ACCESS SIGNALLING message to MSC-B containing an -an-APDU(PERFORM LOCATION RESPONSE). Finally, 3G MSC-A sends a MAP FORWARD ACCESS SIGNALLING message to MSC-B containing an -an-APDU(LCS-MOLR Response), and MSC-B sends the LCS-MOLR Response to the MS. + +Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, MSC-B, BSS-B, and MS. + +**Figure 67c: Signalling for the request of Assistance Data or De-ciphering Keys** + +After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.4.2).. + +#### 4.9.4.4 Inter-MSC SRNS Relocation + +After a successful Inter-MSC SRNS Relocation , any request of Assistance Data or De-ciphering keys received by the non anchor 3G MSC via the DTAP message LCS-MOLR is forwarded to the anchor 3G MSC by encapsulating the DTAP message into the MAP messages Process Access Signalling. The anchor 3G MSC triggers the RANAP procedure Location + +Related Data described in TS 25.413. For handover this procedure is executed according to 23.009 with the anchor 3G-MSC playing the role of the 3G-MSC and the non anchor 3G-MSC playing the role of the RNS. + +The needed RANAP signalling is sent over the E-interface encapsulated in the MAP messages Process Access Signalling and Forward Access Signalling. + +At the non anchor 3G MSC the RANAP messages received from the anchor 3G MSC are forwarded to the RNS, and the RANAP messages received from the RNS are sent over the E-interface to the anchor 3G MSC. + +Once the RANAP procedure has been completed, the anchor 3G MSC sends the DTAP message LCS-MOLR Response encapsulated in the MAP message Forward Access Signalling to the non anchor 3G MSC, which relays it to the UE. + +The signalling for a completed request of Assistance Data or De-ciphering Keys is shown in figures 67d. + +![Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, 3G MSC-B, RNS-B, and UE.](3ec35c497a0765a1a885c85f214b1bef_img.jpg) + +``` + +sequenceDiagram + participant A as 3G MSC-A + participant B as 3G MSC-B + participant R as RNS-B + participant U as UE + + U-->>B: LCS-MOLR + Note over A: MAP PROCESS ACCESS +SIGNALLING + B-->>A: -an-APDU (LCS-MOLR) + Note over A: MAP FORWARD ACCESS +SIGNALLING + A->>B: -an-APDU ( +LOCATION RELATED +DATA REQUEST) + B->>R: LOCATION RELATED +DATA REQUEST + Note over R, U: If Assistance Data were requested then +Delivery of Assistance Data to UE + R-->>B: LOCATION RELATED +DATA RESPONSE + Note over A: MAP PROCESS ACCESS +SIGNALLING + B-->>A: -an-APDU ( +LOCATION RELATED +DATA RESPONSE) + Note over A: MAP FORWARD ACCESS +SIGNALLING + A->>B: -an-APDU ( +LCS-MOLR Response) + B->>U: LCS-MOLR Response + +``` + +The sequence diagram illustrates the signalling flow for requesting Assistance Data or De-ciphering Keys. The entities involved are 3G MSC-A (anchor), 3G MSC-B (serving), RNS-B, and the UE. The flow starts with an LCS-MOLR from the UE to 3G MSC-B, which is then forwarded to 3G MSC-A via a MAP PROCESS ACCESS SIGNALLING message containing an -an-APDU(LCS-MOLR). 3G MSC-A then sends a MAP FORWARD ACCESS SIGNALLING message with a LOCATION RELATED DATA REQUEST to 3G MSC-B, which forwards it to RNS-B. A conditional step shows that if assistance data was requested, it is delivered from RNS-B to the UE. RNS-B then sends a LOCATION RELATED DATA RESPONSE to 3G MSC-B, which is forwarded to 3G MSC-A via MAP PROCESS ACCESS SIGNALLING. Finally, 3G MSC-A sends a MAP FORWARD ACCESS SIGNALLING message with an LCS-MOLR Response to 3G MSC-B, which delivers the final LCS-MOLR Response to the UE. + +Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, 3G MSC-B, RNS-B, and UE. + +**Figure 67d: Signalling for the request of Assistance Data or De-ciphering Keys** + +After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC. The signalling for a completed request of Assistance Data or De-ciphering Keys in this traffic case is shown in figures 67e. + +![Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, 3G MSC-B, BSS-B, and UE.](24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg) + +The sequence diagram illustrates the following interaction: + +- UE** sends an **LCS-MOLR** message to **3G MSC-B**. +- 3G MSC-B** sends a **MAP PROCESS ACCESS SIGNALLING** message to **3G MSC-A**, containing an **-an-APDU (LCS-MOLR)**. +- 3G MSC-A** sends a **MAP FORWARD ACCESS SIGNALLING** message to **3G MSC-B**, containing an **-an-APDU (LOCATION RELATED DATA REQUEST)**. +- 3G MSC-B** sends a **PERFORM LOCATION REQUEST** message to **BSS-B**. +- Inside a conditional block labeled "If Assistance Data were requested then Delivery of Assistance Data to MS", **BSS-B** sends a **PERFORM LOCATION RESPONSE** message back to **3G MSC-B**. +- 3G MSC-B** sends a **MAP PROCESS ACCESS SIGNALLING** message to **3G MSC-A**, containing an **-an-APDU (LOCATION RELATED DATA RESPONSE)**. +- 3G MSC-A** sends a **MAP FORWARD ACCESS SIGNALLING** message to **3G MSC-B**, containing an **-an-APDU (LCS-MOLR Response)**. +- 3G MSC-B** sends an **LCS-MOLR Response** message to the **UE**. + +Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, 3G MSC-B, BSS-B, and UE. + +**Figure 67e: Signalling for the request of Assistance Data or De-ciphering Keys** + +When the UE requires the delivery of Assistance Data for the GPS Assisted positioning method, the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG. request
-an-APDU(
LOCATION RELATED
DATA REQUEST)
RANAP information elements:
Requested Location
Related Data Type
> Dedicated Assistance
Data for Assisted GPS
Requested GPS Assistance Data | PERFORM LOCATION REQUEST
BSSMAP information elements:
Location Type.
Location Information
> location assistance info for target MS
Location Type.
Positioning Method
> Assisted GPS
GPS Assistance Data | 1 | +| Result | MAP PROCESS ACCESS SIG. request
-an-APDU(
LOCATION RELATED
DATA RESPONSE)
RANAP information elements: | PERFORM LOCATION RESPONSE
BSSMAP information elements: | 2 | + +NOTE 1: All other Positioning Method possibilities are not supported by GSM when Location Information is "deciphering keys for broadcast assistance data for the target MS". + +NOTE 2: The absence of the Cause IE in the BSSMAP message Perform Location Response is an indication that the requested assistance data has been successfully delivered to the UE.. + +If the UE requires the delivery of Assistance Data for a GSM specific method, then the anchor 3G-MSC cannot forward the request to the non anchor 3G MSC, and replies with the error "System" to the LCS-MOLR message. + +If the anchor 3G MSC sends a request for Assistance Data for an UMTS specific method in RANAP Location Related Data Request encapsulated in MAP Forward Access Signalling, then the non anchor 3G MSC replies immediately by generating and encapsulating RANAP Location Related Data Failure with Cause "Unspecified Failure" in MAP Process Access Signalling. This traffic case can happen if an LCS-MOLR had been received in the anchor MSC before the initiation of the intra-MSC handover procedure. + +When the UE requires the delivery of De-ciphering Keys for the GPS Assisted positioning method, the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | MAP FORWARD ACCESS SIG. request

-an-APDU(
LOCATION RELATED
DATA REQUEST)

RANAP information elements:

Requested Location
Related Data Type
> Deciphering Keys
for Assisted GPS | PERFORM LOCATION REQUEST

BSSMAP information elements:

Location Type.
Location Information
> deciphering keys
for broadcast
assistance data
for the target MS
Location Type.
Positioning Method
> Assisted GPS | 1 | +| Result | MAP PROCESS ACCESS SIG. request

-an-APDU(
LOCATION RELATED
DATA RESPONSE)

RANAP information elements:

Broadcast Assistance
Data Deciphering Keys | PERFORM LOCATION RESPONSE

BSSMAP information elements:

Deciphering Keys | | + +NOTE 1: All other Positioning Method possibilities are not supported by GSM when Location Information is "deciphering keys for broadcast assistance data for the target MS". + +If the UE requires the delivery of De-ciphering Keys for a GSM specific method, then the anchor 3G-MSC cannot forward the request to the non anchor 3G MSC, and replies with the error "System" to the LCS-MOLR message. + +If the anchor 3G MSC sends a request for De-ciphering Keys for an UMTS specific method in RANAP Location Related Data Request encapsulated in MAP Forward Access Signalling, then the non anchor 3G MSC replies immediately by generating and encapsulating RANAP Location Related Data Failure with Cause "Unspecified Failure" in MAP Process Access Signalling. This traffic case can happen if an LCS-MOLR had been received in the anchor MSC before the initiation of the intra-MSC handover procedure. + +### 4.9.5 Request of Assistance Data or De-ciphering Keys: Failure Case + +#### 4.9.5.1 Inter-MSC Handover (GSM to GSM) + +After a successful Inter-MSC handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.1. + +If the request fails, either because the BSS-B cannot return the requested De-ciphering Keys to the anchor MSC or cannot deliver the required Assistance Data to the MS, the signalling is the same as for the successful case and is shown in figure 67a. + +After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.4.2). + +If the request fails the signalling is the same as for the failure case for Inter-MSC Handover GSM to UMTS (see clause 4.9.5.2) + +#### 4.9.5.2 Inter-MSC Handover (GSM to UMTS) + +After a successful Inter-MSC GSM to UMTS handover, any request of Assistance Data or De-ciphering keys received by the non anchor 3G MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.2. + +If the request fails, either because BSS-B cannot return the requested De-ciphering Keys to the anchor MSC or because BSS-B cannot deliver the required Assistance Data to the MS, the signalling is as shown in figure 68a. + +![Sequence diagram showing signalling for a failed request of Assistance Data or De-ciphering Keys between MSC-A, 3G MSC-B, RNS-B, and UE.](b11b654648249b38a82129a35555b481_img.jpg) + +``` + +sequenceDiagram + participant MSC-A + participant 3G MSC-B + participant RNS-B + participant UE + + UE-->>3G MSC-B: LCS-MOLR + 3G MSC-B-->>MSC-A: MAP PROCESS ACCESS SIGNALLING +-an-APDU (LCS-MOLR) + MSC-A-->>3G MSC-B: MAP FORWARD ACCESS SIGNALLING +-an-APDU (PERFORM LOCATION REQUEST) + 3G MSC-B-->>RNS-B: LOCATION RELATED DATA REQUEST + Note over RNS-B, UE: If Assistance Data were requested then +Delivery of Assistance Data to UE + RNS-B-->>3G MSC-B: LOCATION RELATED DATA FAILURE + 3G MSC-B-->>MSC-A: MAP PROCESS ACCESS SIGNALLING +-an-APDU (PERFORM LOCATION RESPONSE) + MSC-A-->>3G MSC-B: MAP FORWARD ACCESS SIGNALLING +-an-APDU (LCS-MOLR Response) + 3G MSC-B-->>UE: LCS-MOLR Response + +``` + +The sequence diagram illustrates the signalling flow for a failed request. It begins with the UE sending an LCS-MOLR message to 3G MSC-B. 3G MSC-B then sends a MAP PROCESS ACCESS SIGNALLING message containing an -an-APDU(LCS-MOLR) to MSC-A. MSC-A responds with a MAP FORWARD ACCESS SIGNALLING message containing an -an-APDU(PERFORM LOCATION REQUEST) to 3G MSC-B. 3G MSC-B then sends a LOCATION RELATED DATA REQUEST to RNS-B. A conditional block indicates that if assistance data were requested, it would be delivered to the UE. However, RNS-B returns a LOCATION RELATED DATA FAILURE to 3G MSC-B. 3G MSC-B then sends a MAP PROCESS ACCESS SIGNALLING message containing an -an-APDU(PERFORM LOCATION RESPONSE) to MSC-A. MSC-A then sends a MAP FORWARD ACCESS SIGNALLING message containing an -an-APDU(LCS-MOLR Response) to 3G MSC-B. Finally, 3G MSC-B sends an LCS-MOLR Response message to the UE. + +Sequence diagram showing signalling for a failed request of Assistance Data or De-ciphering Keys between MSC-A, 3G MSC-B, RNS-B, and UE. + +**Figure 68a: Signalling for a failed request of Assistance Data or De-ciphering Keys** + +When the delivery to the UE of Assistance Data for the GPS Assisted positioning method fails, the interworking between the BSSMAP messages encapsulated in MAP and the RANAP messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------| +| Forward message | "For the forward messages please refer to the corresponding table in clause 4.9.4.2" | | | +| Result | MAP PROCESS ACCESS SIG. request
-an-APDU(
PERFORM LOCATION RESPONSE)

BSSMAP information elements:
LCS Cause
> System Failure | LOCATION RELATED DATA FAILURE

RANAP information elements:
Cause
> Dedicated Assistance Data Not Available | | + +When the RNS-B cannot satisfy the request for De-ciphering Keys, the interworking between the BSSMAP messages encapsulated in MAP and the RANAP messages is as follows: + +| | 29.002 | 25.413 | Notes | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|-------| +| Forward message | "For the forward messages please refer to the corresponding table in clause 4.9.4.2" | | | +| Result | MAP PROCESS ACCESS SIG. request
-an-APDU(
PERFORM LOCATION RESPONSE)

BSSMAP information elements:
LCS Cause
> System Failure | LOCATION RELATED DATA FAILURE

RANAP information elements:
Cause
> Deciphering Keys Not Available | | + +After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see clause 4.9.4.1). + +If the request fails the signalling is the same as for the failure case for Inter-MSC Handover GSM to GSM (see clause 4.9.5.1) + +#### 4.9.5.3 Inter-MSC Handover (UMTS to GSM) + +After a successful Inter-MSC UMTS to GSM handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.3. + +If the request fails, either because the BSS-B cannot return the requested De-ciphering Keys to the anchor 3G MSC or BSS-B cannot deliver the required Assistance Data to the MS, the signalling is the same as for the successful case and is shown in figure 67c. + +After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.4.2).. + +If the request fails the signalling is the same as for the failure case for Inter-MSC Handover GSM to UMTS (see clause 4.9.5.2) + +#### 4.9.5.4 Inter-MSC SRNS Relocation + +After a successful Inter-MSC SRNS Relocation, any request of Assistance Data or De-ciphering keys received by the non anchor 3G MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.4. + +If the request fails, either because the RNS-B cannot return the requested De-ciphering Keys to the anchor 3G MSC or RNS-B cannot deliver the required Assistance Data to the MS, the signalling is shown in figure 68b. + +![Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, 3G MSC-B, RNS-B, and UE.](e699312f10b7831b388e6c6a5e7032ee_img.jpg) + +``` + +sequenceDiagram + participant 3G MSC-A + participant 3G MSC-B + participant RNS-B + participant UE + + UE-->>3G MSC-B: LCS-MOLR + Note over 3G MSC-A: MAP PROCESS ACCESS SIGNALLING + 3G MSC-B-->>3G MSC-A: -an-APDU (LCS-MOLR) + Note over 3G MSC-A: MAP FORWARD ACCESS SIGNALLING + 3G MSC-A->>3G MSC-B: -an-APDU (LOCATION RELATED DATA REQUEST) + 3G MSC-B->>RNS-B: LOCATION RELATED DATA REQUEST + Note over RNS-B, UE: If Assistance Data were requested then Delivery of Assistance Data to UE + RNS-B-->>3G MSC-B: LOCATION RELATED DATA FAILURE + Note over 3G MSC-A: MAP PROCESS ACCESS SIGNALLING + 3G MSC-B-->>3G MSC-A: -an-APDU (LOCATION RELATED DATA FAILURE) + Note over 3G MSC-A: MAP FORWARD ACCESS SIGNALLING + 3G MSC-A->>3G MSC-B: -an-APDU (LCS-MOLR Response) + 3G MSC-B-->>UE: LCS-MOLR Response + +``` + +Sequence diagram showing signalling for the request of Assistance Data or De-ciphering Keys between 3G MSC-A, 3G MSC-B, RNS-B, and UE. + +**Figure 68b: Signalling for the request of Assistance Data or De-ciphering Keys** + +After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC. + +If the request fails, either because the BSS-B cannot return the requested De-ciphering Keys to the anchor 3G MSC or BSS-B cannot deliver the required Assistance Data to the MS, the signalling is as shown in figure 68c. + +![Sequence diagram for Figure 68c: Signalling for the request of Assistance Data or De-ciphering Keys. The diagram shows interactions between 3G MSC-A, 3G MSC-B, BSS-B, and UE.](886af5e2ffd5d8f11079c547675cf882_img.jpg) + +``` + +sequenceDiagram + participant 3G MSC-A + participant 3G MSC-B + participant BSS-B + participant UE + + Note left of 3G MSC-A: MAP PROCESS ACCESS SIGNALLING + 3G MSC-A->>3G MSC-B: -an-APDU (LCS-MOLR) + Note left of 3G MSC-A: MAP FORWARD ACCESS SIGNALLING + 3G MSC-A->>3G MSC-B: -an-APDU (LOCATION RELATED DATA REQUEST) + 3G MSC-B->>BSS-B: PERFORM LOCATION REQUEST + Note right of BSS-B: If Assistance Data were requested then Delivery of Assistance Data to MS + BSS-B-->>3G MSC-B: PERFORM LOCATION RESPONSE + Note left of 3G MSC-A: MAP PROCESS ACCESS SIGNALLING + 3G MSC-B->>3G MSC-A: -an-APDU (LOCATION RELATED DATA FAILURE) + Note left of 3G MSC-A: MAP FORWARD ACCESS SIGNALLING + 3G MSC-B->>3G MSC-A: -an-APDU (LCS-MOLR Response) + 3G MSC-B-->>UE: LCS-MOLR Response + +``` + +The sequence diagram illustrates the signalling process for requesting assistance data or de-ciphering keys. It involves four main entities: 3G MSC-A (anchor), 3G MSC-B (non-anchor), BSS-B (base station), and UE (user equipment). The process begins with 3G MSC-A sending a MAP PROCESS ACCESS SIGNALLING message containing an -an-APDU (LCS-MOLR) to 3G MSC-B. 3G MSC-A then sends a MAP FORWARD ACCESS SIGNALLING message containing an -an-APDU (LOCATION RELATED DATA REQUEST) to 3G MSC-B. 3G MSC-B forwards this as a PERFORM LOCATION REQUEST to BSS-B. A conditional block indicates that if assistance data was requested, it would be delivered to the MS. BSS-B responds with a PERFORM LOCATION RESPONSE to 3G MSC-B. 3G MSC-B then sends a MAP PROCESS ACCESS SIGNALLING message containing an -an-APDU (LOCATION RELATED DATA FAILURE) back to 3G MSC-A. Finally, 3G MSC-A sends a MAP FORWARD ACCESS SIGNALLING message containing an -an-APDU (LCS-MOLR Response) to 3G MSC-B, which in turn sends an LCS-MOLR Response to the UE. + +Sequence diagram for Figure 68c: Signalling for the request of Assistance Data or De-ciphering Keys. The diagram shows interactions between 3G MSC-A, 3G MSC-B, BSS-B, and UE. + +**Figure 68c: Signalling for the request of Assistance Data or De-ciphering Keys** + +After the inter-MSC SRNS Relocation, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM requires that at the non anchor 3G MSC the received RANAP messages are mapped into the corresponding BSSMAP messages to be sent to the + +BSS, and the received BSSMAP messages are mapped into the corresponding RANAP messages to be sent over the E-interface to the anchor 3G-MSC. + +When the UE requires the delivery of Assistance Data for the GPS Assisted positioning method, the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------| +| Forward message | "For the forward messages please refer to the corresponding table in clause 4.9.4.4" | | | +| Result | MAP PROCESS ACCESS SIG. request
-an-APDU(
LOCATION RELATED
DATA FAILURE)

RANAP information elements:

Cause
> Dedicated Assistance
Data Not Available | PERFORM LOCATION RESPONSE

BSSMAP information elements:

LCS Cause
> | | + +When the UE requires the delivery of De-ciphering Keys for the GPS Assisted positioning method, the interworking between the RANAP messages encapsulated in MAP and the BSSMAP messages is as follows: + +| | 29.002 | 48.008 | Notes | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------| +| Forward message | "For the forward messages please refer to the corresponding table in clause 4.9.4.4" | | | +| Result | MAP PROCESS ACCESS SIG. request
-an-APDU(
LOCATION RELATED
DATA FAILURE)

RANAP information elements:

Cause
> Deciphering Keys
Not Available | PERFORM LOCATION RESPONSE

BSSMAP information elements:

LCS Cause
> | | + +### 4.9.6 Abort of Request of Assistance Data or De-ciphering Keys: + +#### 4.9.6.1 Inter-MSC Handover (GSM to GSM) + +After a successful Inter-MSC handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.1. + +If the request is aborted by the anchor MSC the signalling is as shown in figure 69a. + +![Sequence diagram showing signalling for the abortion of a request for Assistance Data or De-ciphering Keys. The diagram involves MSC-A, MSC-B, BSS-B, and MS. The sequence starts with MSC-B sending an LCS-MOLR request to the MS. MSC-A then sends a MAP PROCESS ACCESS SIGNALLING message to MSC-B with an -an-APDU(LCS-MOLR). MSC-B responds with a MAP FORWARD ACCESS SIGNALLING message containing an -an-APDU(PERFORM LOCATION REQUEST) to the BSS-B. The BSS-B sends a PERFORM LOCATION REQUEST to the MS. MSC-A then sends another MAP FORWARD ACCESS SIGNALLING message to MSC-B with an -an-APDU(PERFORM LOCATION ABORT). The BSS-B receives this and sends a PERFORM LOCATION ABORT to the MS. The MS responds with a PERFORM LOCATION RESPONSE to the BSS-B, which then forwards it to MSC-B via a MAP PROCESS ACCESS SIGNALLING message with an -an-APDU(PERFORM LOCATION RESPONSE). Finally, MSC-B sends a MAP FORWARD ACCESS SIGNALLING message to MSC-A with an -an-APDU(LCS-MOLR Response), and MSC-B sends an LCS-MOLR Response to the MS.](8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg) + +``` + +sequenceDiagram + participant MSC-A + participant MSC-B + participant BSS-B + participant MS + + Note left of MSC-B: LCS-MOLR + MSC-B-->>MS: LCS-MOLR + Note left of MSC-A: MAP PROCESS ACCESS SIGNALLING + MSC-A-->>MSC-B: -an-APDU(LCS-MOLR) + Note left of MSC-B: MAP FORWARD ACCESS SIGNALLING + MSC-B-->>BSS-B: -an-APDU(PERFORM LOCATION REQUEST) + Note right of BSS-B: PERFORM LOCATION REQUEST + BSS-B-->>MS: PERFORM LOCATION REQUEST + Note left of MSC-A: MAP FORWARD ACCESS SIGNALLING + MSC-A-->>MSC-B: -an-APDU(PERFORM LOCATION ABORT) + Note right of BSS-B: PERFORM LOCATION ABORT + BSS-B-->>MS: PERFORM LOCATION ABORT + Note right of BSS-B: PERFORM LOCATION RESPONSE + BSS-B-->>MSC-B: PERFORM LOCATION RESPONSE + Note left of MSC-A: MAP PROCESS ACCESS SIGNALLING + MSC-B-->>MSC-A: -an-APDU(PERFORM LOCATION RESPONSE) + Note left of MSC-B: MAP FORWARD ACCESS SIGNALLING + MSC-B-->>MSC-A: -an-APDU(LCS-MOLR Response) + Note left of MSC-B: LCS-MOLR Response + MSC-B-->>MS: LCS-MOLR Response + +``` + +Sequence diagram showing signalling for the abortion of a request for Assistance Data or De-ciphering Keys. The diagram involves MSC-A, MSC-B, BSS-B, and MS. The sequence starts with MSC-B sending an LCS-MOLR request to the MS. MSC-A then sends a MAP PROCESS ACCESS SIGNALLING message to MSC-B with an -an-APDU(LCS-MOLR). MSC-B responds with a MAP FORWARD ACCESS SIGNALLING message containing an -an-APDU(PERFORM LOCATION REQUEST) to the BSS-B. The BSS-B sends a PERFORM LOCATION REQUEST to the MS. MSC-A then sends another MAP FORWARD ACCESS SIGNALLING message to MSC-B with an -an-APDU(PERFORM LOCATION ABORT). The BSS-B receives this and sends a PERFORM LOCATION ABORT to the MS. The MS responds with a PERFORM LOCATION RESPONSE to the BSS-B, which then forwards it to MSC-B via a MAP PROCESS ACCESS SIGNALLING message with an -an-APDU(PERFORM LOCATION RESPONSE). Finally, MSC-B sends a MAP FORWARD ACCESS SIGNALLING message to MSC-A with an -an-APDU(LCS-MOLR Response), and MSC-B sends an LCS-MOLR Response to the MS. + +**Figure 69a: Signalling for the abortion of a request for Assistance Data or De-ciphering Keys** + +After the inter-MSC handover, the MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.4.2). + +If the request is aborted the signalling is the same as for the abortion case for Inter-MSC Handover GSM to UMTS (see clause 4.9.6.2) + +#### 4.9.6.2 Inter-MSC Handover (GSM to UMTS) + +After a successful Inter-MSC GSM to UMTS handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.1. + +If the request is aborted by the anchor MSC the signalling is as shown in figure 69b. + +![Sequence diagram showing signalling for the abortion of the request for Assistance Data or De-ciphering Keys between MSC-A, 3G MSC-B, RNS-B, and UE.](ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg) + +``` + +sequenceDiagram + participant MSC-A + participant 3G MSC-B + participant RNS-B + participant UE + + UE-->>3G MSC-B: LCS-MOLR + 3G MSC-B-->>MSC-A: MAP PROCESS ACCESS SIGNALLING +-an-APDU (LCS-MOLR) + MSC-A-->>3G MSC-B: MAP FORWARD ACCESS SIGNALLING +-an-APDU (PERFORM LOCATION REQUEST) + 3G MSC-B-->>RNS-B: LOCATION RELATED DATA REQUEST + MSC-A-->>3G MSC-B: MAP FORWARD ACCESS SIGNALLING +-an-APDU (PERFORM LOCATION ABORT) + 3G MSC-B-->>MSC-A: MAP PROCESS ACCESS SIGNALLING +-an-APDU (PERFORM LOCATION RESPONSE) + 3G MSC-B-->>MSC-A: MAP FORWARD ACCESS SIGNALLING +-an-APDU (LCS-MOLR Response) + 3G MSC-B-->>UE: LCS-MOLR Response + +``` + +Sequence diagram showing signalling for the abortion of the request for Assistance Data or De-ciphering Keys between MSC-A, 3G MSC-B, RNS-B, and UE. + +**Figure 69b: Signalling for the abortion of the request for Assistance Data or De-ciphering Keys** + +There's no interworking between the BSSMAP Perform Location Abort and any RANAP message since it is not possible to abort a request for Assistance Data or De-ciphering Keys with RANAP. The BSSMAP message Perform Location Response is generated by the non-anchor 3G MSC. + +After the inter-MSC GSM to UMTS handover, the 3G MSC-B can perform intra-MSC UMTS to GSM handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC UMTS to GSM handover is handled as for Inter-MSC Handover GSM to GSM (see clause 4.9.4.1). + +If the request is aborted the signalling is the same as for the abortion case for Inter-MSC Handover GSM to GSM (see clause 4.9.6.1) + +#### 4.9.6.3 Inter-MSC Handover (UMTS to GSM) + +After a successful Inter-MSC UMTS to GSM handover, any request of Assistance Data or De-ciphering keys received by the non anchor MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.3. + +If the request is aborted by the anchor 3G MSC the signalling is the same as for the abortion for Inter-MSC GSM to GSM handover and is shown in figure 69a. + +After the inter-MSC UMTS to GSM handover, the 3G MSC-B can perform intra-MSC GSM to UMTS handover. Any request for Assistance Data or De-ciphering keys received after completion of the intra-MSC GSM to UMTS handover is handled as for Inter-MSC Handover GSM to UMTS (see clause 4.9.4.2).. + +If the request is aborted the signalling is the same as for the abortion case for Inter-MSC Handover GSM to UMTS (see clause 4.9.6.2) + +#### 4.9.6.4 Inter-MSC SRNS Relocation + +After a successful Inter-MSC SRNS Relocation , any request of Assistance Data or De-ciphering keys received by the non anchor 3G MSC via the DTAP message LCS-MOLR is handled as described in clause 4.9.4.4. + +The request cannot be aborted by the 3G anchor MSC since RANAP does not support abortion of a request for Assistance Data or De-Ciphering Keys. + +## 4.10 Single Radio Voice Call Continuity (SRVCC) + +### 4.10.1 General + +The general principles of the SRVCC handover procedures are specified in 3GPP TS 23.009 [2]. This clause provides a detailed specification for the interworking performed by the MSC Server enhanced for SRVCC. It defines in particular the encoding of RANAP and BSSMAP cause values to avoid different encodings in different implementations. + +### 4.10.2 SRVCC Handover from UTRAN (HSPA) to GERAN + +#### **Encoding of the cause code sent in BSSMAP Handover Request:** + +When it receives the SRVCC PS to CS Request message from the SGSN (see 3GPP TS 29.280 [25]), the MSC Server enhanced for SRVCC shall set the BSSMAP Cause to the value 'Uplink quality' in the Handover Request message. + +### 4.10.3 SRVCC Handover from UTRAN (HSPA) to UTRAN + +#### **Encoding of the cause code sent in RANAP Relocation Request:** + +When it receives the SRVCC PS to CS Request message from the SGSN (see 3GPP TS 29.280 [25]), the MSC Server enhanced for SRVCC shall set the RANAP Cause to the value 'Time critical Relocation ' in the Relocation Request message. + +### 4.10.4 SRVCC Handover from E-UTRAN to GERAN + +#### **Encoding of the cause code sent in BSSMAP Handover Request:** + +When it receives the SRVCC PS to CS Request message from the MME (see 3GPP TS 29.280 [25]), the MSC Server enhanced for SRVCC shall set the BSSMAP Cause to the value 'Uplink quality' in the Handover Request message. + +### 4.10.5 SRVCC Handover from E-UTRAN to UTRAN + +#### Encoding of the cause code sent in RANAP Relocation Request: + +When it receives the SRVCC PS to CS Request message from the MME (see 3GPP TS 29.280 [25]), the MSC Server enhanced for SRVCC shall set the RANAP Cause to the value 'Time critical Relocation ' in the Relocation Request message. + +# 5 Interworking in the MME + +## 5.1 General + +This clause provides a detailed specification for the interworking performed by the MME. + +## 5.2 Void + +## 5.3 Interworking between RANAP protocol messages and S1AP protocol messages + +This clause defines a mapping of RANAP and S1AP cause values used in connection with inter RAT Handover to avoid different mappings in different implementations. + +### Inter RAT Handover from UTRAN to LTE: + +Table 5.3.1 defines a cause value mapping performed by the MME when the MME receives the Forward Relocation Request message from the S4-SGSN. + +**Table 5.3.1: Cause value mapping from RANAP Cause to S1AP Cause** + +| 25.413 [7] | | 36.413 [21] | | +|-----------------------------------|----------------------------------|-------------------------------|--------------------------------------| +| RELOCATION REQUIRED (RANAP Cause) | | HANDOVER REQUEST (S1AP Cause) | | +| Group | Value | Group | Value | +| Radio Network Layer Cause | Time critical Relocation | Radio Network Layer Cause | Time critical handover | +| Radio Network Layer Cause | Resource Optimisation Relocation | Radio Network Layer Cause | Resource optimisation handover | +| Radio Network Layer Cause | Reduce Load in Serving Cell | Radio Network Layer Cause | Reduce load in serving cell | +| Any other value | | Radio Network Layer Cause | Handover Desirable for Radio Reasons | + +For inter RAT handover from UTRAN served by Gn/Gp-SGSN to LTE, the MME maps the RANAP cause in the GTPv1 Forward Relocation Request message to an S1AP cause as per Table 5.3.1. The MME sends this S1AP cause in the S1AP Handover Request message to the eNodeB. + +For inter RAT handover from UTRAN served by Gn/Gp-SGSN to LTE, if the handover fails in the LTE access, the MME maps the S1AP cause in the S1AP Handover Failure message to a RANAP cause by using the mapping in Table 6.2.1. The MME uses the RANAP cause in the GTPv1 Forward Relocation Response message to the Gn/Gp-SGSN. + +### Inter RAT Handover from LTE to UTRAN: + +The table 5.3.2 defines a cause value mapping performed by the MME when the MME receives the Forward Relocation Response message from the S4-SGSN. This mapping is only needed if the inter RAT Handover failed in UTRAN. + +**Table 5.3.2: Cause value mapping from RANAP Cause to S1AP Cause for failure case** + +| 25.413 [7] | | 36.413 [21] | | +|----------------------------------|--------------------------------------------------------------------------|-------------------------------------------|-----------------------------------------------------------------| +| RELOCATION FAILURE (RANAP Cause) | | HANDOVER PREPARATION FAILURE (S1AP Cause) | | +| Group | Value | Group | Value | +| Radio Network Layer Cause | No Radio Resources Available in Target Cell | Radio Network Layer Cause | No Radio Resources Available in Target Cell | +| Radio Network Layer Cause | Requested Ciphering and/or Integrity Protection algorithms not supported | Radio Network Layer Cause | Encryption and/or integrity protection algorithms not supported | +| Radio Network Layer Cause | Traffic Load In The Target Cell Higher Than In The Source Cell | Radio Network Layer Cause | No Radio Resources Available in Target Cell | +| Miscellaneous Cause | O&M Intervention | Miscellaneous Cause | O&M Intervention | +| Any other value | | Radio Network Layer Cause | Handover Failure In Target EPC/eNB Or Target System | + +For inter RAT handover from LTE to UTRAN served by Gn/Gp-SGSN, the MME maps the S1AP cause in S1AP Handover Required message to a RANAP cause by using the mapping in Table 6.2.2. The MME uses this RANAP cause in the GTPv1 Forward Relocation Request message to the Gn/Gp-SGSN. + +For inter RAT handover from LTE to UTRAN served by Gn/Gp-SGSN, if the handover fails in the UTRAN access, the MME maps the RANAP cause received in the GTPv1 Forward Relocation Response message to an S1AP cause as per Table 5.3.2. The MME sends this S1AP cause in the S1AP Handover Preparation Failure message to the eNodeB. + +## 5.4 Interworking between BSSGP protocol messages and S1AP protocol messages + +This clause defines a mapping of BSSGP and S1AP cause values used in connection with inter RAT Handover to avoid different mappings in different implementations. + +### Inter RAT Handover from GERAN to LTE: + +Table 5.4.1 defines a cause value mapping performed by the MME when the MME receives the GTPv2 Forward Relocation Request message from the S4-SGSN or the GTPv1 Forward Relocation Request message from Gn/Gp-SGSN (as per Annex D of 3GPP TS 23.401[22]). + +NOTE1: The mapping in Table 5.4.1 has been derived based on Table 15.1 in 3GPP TS 29.060 [23] and Table 5.3.1 in this specification. + +**Table 5.4.1: Cause value mapping from BSSGP Cause to S1AP Cause** + +| 48.018 [24] | 36.413 [21] | | +|-------------------------------------------|--------------------------------------|--------------------------------------| +| PS HANDOVER REQUIRED (BSSGP Cause) | HANDOVER REQUEST (S1AP Cause) | | +| Value | Group | Value | +| Uplink quality | Radio Network Layer Cause | Time critical handover | +| Uplink strength | Radio Network Layer Cause | Time critical handover | +| Downlink quality | Radio Network Layer Cause | Time critical handover | +| Downlink strength | Radio Network Layer Cause | Time critical handover | +| Distance | Radio Network Layer Cause | Time critical handover | +| Traffic | Radio Network Layer Cause | Resource optimisation handover | +| Cell traffic congestion | Radio Network Layer Cause | Reduce load in serving cell | +| Any other value | Radio Network Layer Cause | Handover Desirable for Radio Reasons | + +For inter RAT handover from GERAN served by Gn/Gp-SGSN to LTE, if the handover fails in the LTE access, the MME maps the S1AP cause in S1AP Handover Failure message to a RANAP cause by using the mapping in Table 6.2.1. The MME uses the RANAP cause in the GTPv1 Forward Relocation Response message to the Gn/Gp-SGSN. The Gn-Gp/SGSN maps the RANAP cause to a BSSGP cause as per Table 15.2 in 3GPP TS 29.060 [23] and sends this BSSGP cause in the BSSGP PS Handover Required Nack message. + +### Inter RAT Handover from LTE to GERAN: + +Table 5.4.2 defines a cause value mapping performed by the MME when the MME receives the GTPv2 Forward Relocation Response message from the S4-SGSN or the GTPv1 Forward Relocation Response message from the Gn/Gp-SGSN (as per Annex D of 3GPP TS 23.401[22]). This mapping is only needed if the inter RAT Handover failed in GERAN. + +NOTE2: The mapping in Table 5.4.2 has been derived based on Table 15.4 in 3GPP TS 29.060 [23] and Table 5.3.2 in this specification. + +**Table 5.4.2: Cause value mapping from BSSGP Cause to S1AP Cause for failure case** + +| 48.018 [24] | 36.413 [21] | | +|-----------------------------------------------|--------------------------------------------------|-----------------------------------------------------| +| PS HANDOVER REQUEST NACK (BSSGP Cause) | HANDOVER PREPARATION FAILURE (S1AP Cause) | | +| Value | Group | Value | +| Cell traffic congestion | Radio Network Layer Cause | No Radio Resources Available in Target Cell | +| O&M intervention | Miscellaneous Cause | O&M Intervention | +| Any other value | Radio Network Layer Cause | Handover Failure In Target EPC/eNB Or Target System | + +For inter RAT handover from LTE to GERAN served by Gn/Gp-SGSN, the MME maps the S1AP cause in S1AP Handover Required message to a RANAP cause by using the mapping in Table 6.2.2. The MME uses the RANAP cause in the GTPv1 Forward Relocation Request message to the Gn/Gp-SGSN. The Gn-Gp/SGSN maps the RANAP cause to a BSSGP cause as per Table 15.3 in 3GPP TS 29.060 [23] and sends this BSSGP cause in the BSSGP PS Handover Request message. + +# 6 Interworking in the S4-SGSN + +## 6.1 General + +This clause provides a detailed specification for the interworking performed by the S4-SGSN. + +## 6.2 Interworking between RANAP protocol messages and S1AP protocol messages + +This clause defines a mapping of RANAP and SIAP cause values used in connection with inter RAT Handover to avoid different mappings in different implementations. + +### Inter RAT Handover from UTRAN to LTE: + +The table 6.2.1 defines a cause value mapping performed by the S4-SGSN when the S4-SGSN receives the Forward Relocation Response message from the MME. This mapping is only needed if the inter RAT Handover failed in LTE. + +**Table 6.2.1: Cause value mapping from S1AP Cause to RANAP Cause for failure case** + +| 36.413 [21] | | 25.413 [7] | | +|-------------------------------|-----------------------------------------------------------------|----------------------------------------------|--------------------------------------------------------------------------| +| HANDOVER FAILURE (S1AP Cause) | | RELOCATION PREPARATION FAILURE (RANAP Cause) | | +| Group | Value | Group | Value | +| Radio Network Layer Cause | No Radio Resources Available in Target Cell | Radio Network Layer Cause | No Radio Resources Available in Target Cell | +| Radio Network Layer Cause | Encryption and/or integrity protection algorithms not supported | Radio Network Layer Cause | Requested Ciphering and/or Integrity Protection algorithms not supported | +| Miscellaneous Cause | O&M Intervention | Miscellaneous Cause | O&M Intervention | +| Any other value | | Radio Network Layer Cause | Relocation Failure in Target CN/RNC or Target System | + +### Inter RAT Handover from LTE to UTRAN: + +Table 6.2.2 defines a cause value mapping performed by the S4-SGSN when the S4-SGSN receives the Forward Relocation Request message from the MME. + +**Table 6.2.2: Cause value mapping from S1AP Cause to RANAP Cause** + +| 36.413 [21] | | 25.413 [7] | | +|--------------------------------|--------------------------------------|----------------------------------|----------------------------------------| +| HANDOVER REQUIRED (S1AP Cause) | | RELOCATION REQUEST (RANAP Cause) | | +| Group | Value | Group | Value | +| Radio Network Layer Cause | Handover Desirable for Radio Reasons | Radio Network Layer Cause | Relocation Desirable for Radio Reasons | +| Radio Network Layer Cause | Time Critical Handover | Radio Network Layer Cause | Time critical Relocation | +| Radio Network Layer Cause | Reduce Load in Serving Cell | Radio Network Layer Cause | Reduce Load in Serving Cell | +| Radio Network Layer Cause | CS Fallback Triggered | Radio Network Layer Cause | CS Fallback triggered | +| Any other value | | Radio Network Layer Cause | Resource Optimized Relocation | + +## 6.3 Interworking between BSSGP protocol messages and S1AP protocol messages + +This clause defines a mapping of BSSGP and S1AP cause values used in connection with inter RAT Handover to avoid different mappings in different implementations. + +### Inter RAT Handover from GERAN to LTE: + +Table 6.3.1 defines a cause value mapping performed by the S4-SGSN when the S4-SGSN receives the GTPv2 Forward Relocation Response message from the MME. + +NOTE1: The mapping in Table 6.3.1 has been derived based on Table 6.2.1 in this specification and Table 15.2 in 3GPP TS 29.060 [23]. + +**Table 6.3.1: Cause value mapping from S1AP Cause to BSSGP Cause for failure case** + +| 36.413 [21] | | 48.018 [24] | +|-------------------------------|-----------------------------------------------------------------|--------------------------------------------------------------------------| +| HANDOVER FAILURE (S1AP Cause) | | PS HANDOVER REQUIRED NACK (BSSGP Cause) | +| Group | Value | Value | +| Radio Network Layer Cause | No Radio Resources Available in Target Cell | Cell traffic congestion | +| Radio Network Layer Cause | Encryption and/or integrity protection algorithms not supported | Requested ciphering and/or integrity protection algorithms not supported | +| Miscellaneous Cause | O&M Intervention | O&M Intervention | +| Any other value | | Relocation failure in target system | + +### Inter RAT Handover from LTE to GERAN: + +Table 6.3.2 defines a cause value mapping performed by the S4-SGSN when the S4-SGSN receives the GTPv2 Forward Relocation Request message from the MME. + +NOTE2: The mapping in Table 6.3.2 has been derived based on Table 6.2.2 in this specification and Table 15.3 in 3GPP TS 29.060 [23]. + +**Table 6.3.2: Cause value mapping from S1AP Cause to BSSGP Cause** + +| 36.413 [21] | | 48.018 [24] | +|--------------------------------|--------------------------------------|-----------------------------------| +| HANDOVER REQUIRED (S1AP Cause) | | PS HANDOVER REQUEST (BSSGP Cause) | +| Group | Value | Value | +| Radio Network Layer Cause | Handover Desirable for Radio Reasons | Better cell | +| Radio Network Layer Cause | Time Critical Handover | Time critical relocation | +| Radio Network Layer Cause | Reduce Load in Serving Cell | Cell traffic congestion | +| Any other value | | Traffic | + +## 6.4 Interworking between BSSGP protocol messages and RANAP protocol messages + +For the mapping of BSSGP and RANAP cause values used in connection with inter RAT Handover between GERAN and UTRAN, the mapping tables in clause 15 in 3GPP TS 29.060 [23] applies. The mapping is performed by the target S4-SGSN. + +# 7 Interworking in the AMF + +## 7.1 General + +This clause provides a detailed specification for the interworking performed by the AMF. + +## 7.2 Interworking between S1AP protocol messages and NGAP protocol messages + +This clause defines a mapping of S1AP and NGAP cause values used in connection with inter RAT Handover to avoid different mappings in different implementations. + +### Inter RAT Handover from LTE to NG-RAN: + +Table 7.2.1 defines a cause value mapping performed by the AMF when the AMF receives the Forward Relocation Request message from the MME. + +**Table 7.2.1: Cause value mapping from S1AP Cause to NGAP Cause** + +| 36.413 [21] | | 38.413 [26] | | +|--------------------------------|--------------------------------|-------------------------------|--------------------------------------| +| HANDOVER REQUIRED (S1AP Cause) | | HANDOVER REQUEST (NGAP Cause) | | +| Group | Value | Group | Value | +| Radio Network Layer Cause | Time critical Handover | Radio Network Layer Cause | Time critical handover | +| Radio Network Layer Cause | Resource Optimisation Handover | Radio Network Layer Cause | Resource optimisation handover | +| Radio Network Layer Cause | Reduce Load in Serving Cell | Radio Network Layer Cause | Reduce load in serving cell | +| Any other value | | Radio Network Layer Cause | Handover Desirable for Radio Reasons | + +For inter RAT handover from LTE served by MME to NG-RAN, the AMF maps the S1AP cause in the GTPv2 Forward Relocation Request message to an NGAP cause as per Table 7.2.1. The AMF sends this NGAP cause in the NGAP Handover Request message to the NG-RAN. + +The table 7.2.2 defines a cause value mapping performed by the AMF when the AMF receives the NGAP Handover Failure message from the NG-RAN. This mapping is only needed if the inter RAT Handover failed in NG-RAN. + +**Table 7.2.2: Cause value mapping from NGAP Cause to S1AP Cause for failure case** + +| 38.413 [26] | | 36.413 [21] | | +|--------------------------------------|-----------------------------------------------------------------|--------------------------------------------------|-----------------------------------------------------------------| +| HANDOVER FAILURE (NGAP Cause) | | HANDOVER PREPARATION FAILURE (S1AP Cause) | | +| Group | Value | Group | Value | +| Radio Network Layer Cause | No Radio Resources Available in Target Cell | Radio Network Layer Cause | No Radio Resources Available in Target Cell | +| Radio Network Layer Cause | Encryption and/or integrity protection algorithms not supported | Radio Network Layer Cause | Encryption and/or integrity protection algorithms not supported | +| Radio Network Layer Cause | Insufficient UE Capabilities | Radio Network Layer Cause | Insufficient UE Capabilities | +| Miscellaneous Cause | O&M Intervention | Miscellaneous Cause | O&M Intervention | +| Any other value | | Radio Network Layer Cause | Handover Failure In Target EPC/eNB Or Target System | + +For inter RAT handover from LTE served by MME to NG-RAN, if the handover fails in the NG-RAN access, the AMF maps the NGAP cause in the NGAP Handover Failure message to a S1AP cause by using the mapping in Table 7.2.2. The AMF uses the S1AP cause in the GTPv2 Forward Relocation Response message to the MME. + +### Inter RAT Handover from NG-RAN to LTE: + +The table 7.2.3 defines a cause value mapping performed by the AMF when the AMF receives the HANDOVER REQUIRED from the NG-RAN. + +**Table 7.2.3: Cause value mapping from NGAP Cause to S1AP Cause** + +| 38.413 [26] | | 36.413 [21] | | +|---------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------| +| HANDOVER REQUIRED (NGAP Cause) | | HANDOVER REQUEST (S1AP Cause) | | +| Group | Value | Group | Value | +| Radio Network Layer Cause | Handover Desirable for Radio Reasons | Radio Network Layer Cause | Handover Desirable for Radio Reasons | +| Radio Network Layer Cause | Time Critical Handover | Radio Network Layer Cause | Time critical Handover | +| Radio Network Layer Cause | Reduce Load in Serving Cell | Radio Network Layer Cause | Reduce Load in Serving Cell | +| Any other value | | Radio Network Layer Cause | Resource Optimized Relocation | + +For inter RAT handover from NG-RAN to LTE served by MME, the AMF maps the NGAP cause in NGAP Handover Required message to a S1AP cause by using the mapping in Table 7.2.3. The AMF uses this S1AP cause in the GTPv2 Forward Relocation Request message to the MME. + +Table 7.2.4 defines a cause value mapping performed by the AMF when the AMF receives the Forward Relocation Response message from the MME. This mapping is only needed if the inter RAT Handover failed in LTE. + +Table 7.2.4: Cause value mapping from S1AP Cause to NGAP Cause for failure case + +| 36.413 [21] | | 38.413 [26] | | +|-------------------------------|-----------------------------------------------------------------|-------------------------------------------|-----------------------------------------------------------------| +| HANDOVER FAILURE (S1AP Cause) | | HANDOVER PREPARATION FAILURE (NGAP Cause) | | +| Group | Value | Group | Value | +| Radio Network Layer Cause | No Radio Resources Available in Target Cell | Radio Network Layer Cause | No Radio Resources Available in Target Cell | +| Radio Network Layer Cause | Encryption and/or integrity protection algorithms not supported | Radio Network Layer Cause | Encryption and/or integrity protection algorithms not supported | +| Radio Network Layer Cause | No Radio Resources Available in Target Cell | Radio Network Layer Cause | No Radio Resources Available in Target Cell | +| Radio Network Layer Cause | Insufficient UE Capabilities | Radio Network Layer Cause | Insufficient UE Capabilities | +| Miscellaneous Cause | O&M Intervention | Miscellaneous Cause | O&M Intervention | +| Any other value | | Radio Network Layer Cause | Handover failure in target 5GC/ NG-RAN node or target system | + +For inter RAT handover from NG-RAN to LTE served by MME, if the handover fails in the LTE access, the AMF maps the S1AP cause received in the GTPv2 Forward Relocation Response message to an NGAP cause as per Table 7.2.4. The AMF sends this NGAP cause in the NGAP Handover Preparation Failure message to the NG-RAN. + diff --git a/marked/Rel-18/29_series/29011/raw.md b/marked/Rel-18/29_series/29011/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9d9ff817403a893ad657c890f09c354caf6c47d4 --- /dev/null +++ b/marked/Rel-18/29_series/29011/raw.md @@ -0,0 +1,1480 @@ + + +# 3GPP TS 29.011 V18.0.0 (2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Signalling interworking for supplementary services (Release 18)** + +![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for LTE Advanced Pro. It features the word "lte" in a bold, black, lowercase font. Above the "e" is the text "Advanced Pro" in a smaller, red font. To the right of the "e" is a green signal icon consisting of three curved lines. + +LTE Advanced Pro logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The logo for 3GPP. It features the letters "3GPP" in a stylized, bold, black font. Below the "P" is a red signal icon consisting of three curved lines. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, uppercase font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + + + +# --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 1.1 Normative references ..... | 6 | +| 1.2 Definitions and abbreviations..... | 7 | +| 2 Introduction..... | 7 | +| 2.1 MSC/VLR procedures for handling supplementary service signalling received over the A-interface..... | 8 | +| 2.2 MSC/VLR procedures for handling supplementary service signalling received over the D-interface..... | 8 | +| 3 SS version negotiation ..... | 8 | +| 3.1 Call related supplementary services interworking..... | 8 | +| 3.2 Call independent supplementary services interworking..... | 8 | +| 4 Mapping between TC transaction sublayer messages and layer 3 radio path messages..... | 9 | +| 4.1 D-interface to A-interface mapping ..... | 9 | +| 4.2 A-interface to D-interface mapping ..... | 9 | +| 4.3 Procedures ..... | 9 | +| 5 Call related supplementary services management ..... | 10 | +| 5.1 SS management in connection establishment phase ..... | 10 | +| 5.1.1 Line Identification services ..... | 10 | +| 5.1.1.1 Calling Line Identification Presentation (CLIP)..... | 10 | +| 5.1.1.2 Calling Line Identification Restriction (CLIR) ..... | 11 | +| 5.1.1.3 Connected Line Identification Presentation (COLP)..... | 11 | +| 5.1.1.4 Connected Line Identification Restriction (COLR)..... | 12 | +| 5.1.2 Call Forwarding services..... | 12 | +| 5.1.2.1 Notification to served mobile subscriber..... | 12 | +| 5.1.3 Call Waiting service (CW)..... | 12 | +| 5.1.3.1 Offering a waiting call ..... | 12 | +| 5.1.3.2 Notification of waiting call to calling subscriber..... | 13 | +| 5.1.4 Closed User Group service (CUG)..... | 13 | +| 5.1.4.1 Explicit invocation of a CUG call..... | 13 | +| 5.1.4.2 Notification of CUG invocation to served MS ..... | 14 | +| 5.1.4.3 Notification of rejection of CUG invocation to served MS..... | 14 | +| 5.1.4.4 Notification of CUG invocation to terminating MS ..... | 15 | +| 5.1.5 Advice of Charge services..... | 16 | +| 5.1.5.1 Notification of Charging information to served MS, mobile originated call..... | 16 | +| 5.1.5.2 Notification of Charging information to served MS, mobile terminated call..... | 16 | +| 5.1.6 Call Barring services ..... | 17 | +| 5.1.6.1 Barring of outgoing calls ..... | 17 | +| 5.1.6.2 Barring of incoming calls ..... | 17 | +| 5.1.7 CCBS call outcome ..... | 18 | +| 5.2 SS Management in stable connection state ..... | 18 | +| 5.2.1 Call Forwarding services..... | 18 | +| 5.2.1.1 Notification of invocation of CFB to served mobile subscriber..... | 18 | +| 5.2.2 Call Hold service (HOLD) ..... | 19 | +| 5.2.3 Multi Party service (MPTY)..... | 20 | +| 5.2.4 Advice of Charge services..... | 20 | +| 5.2.5 Explicit Call Transfer service (ECT)..... | 21 | +| 5.3 SS Management in disconnecting phase ..... | 21 | +| 5.3.1 Call Forwarding services..... | 22 | +| 5.3.2 CCBS Request Activation ..... | 22 | +| 5.3.3 Call Deflection service ..... | 23 | +| 5.3.3.1 Call Deflection Operation Request ..... | 23 | +| 5.3.3.2 Call Deflection Operation Response..... | 23 | +| 6 Call independent supplementary services management..... | 24 | +| 6.1 MS initiated SS Management..... | 24 | + +| | | | +|-------------------------------|--------------------------------------------------------------------------------------|-----------| +| 6.1.1 | Connection establishment phase..... | 24 | +| 6.1.2 | Connection established..... | 25 | +| 6.1.3 | Connection release..... | 26 | +| 6.2 | Network initiated SS Management ..... | 26 | +| 6.2.1 | Connection establishment phase..... | 26 | +| 6.2.2 | Connection established..... | 26 | +| 6.2.3 | Connection release..... | 27 | +| 6.2.4 | ForwardCheckSSIndication..... | 27 | +| 6.2.5 | CCBS Recall..... | 27 | +| 6.2.6 | CCBS Monitoring..... | 28 | +| 6.3 | Mapping of Operation Codes, Error Codes, Parameter Tags and Parameter Contents ..... | 29 | +| 6.3.1 | Operation codes ..... | 29 | +| 6.3.2 | Error codes..... | 29 | +| 6.3.3 | Parameter tags and parameter values..... | 29 | +| Annex A (informative): | Change history..... | 30 | + +# --- Foreword + +This Technical Specification has been produced by the 3GPP. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version 3.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 Indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the specification; + +# 1 Scope + +The scope of this Technical Specification is to provide a detailed specification for interworking between the A interface protocol and the Mobile Application Part for handling of supplementary services. The MAP interfaces of interest are the B-, C-, D- and E-interfaces. + +The A-, C-, D- and E-interfaces are physical interfaces while the B-interface is an internal interface defined for modelling purposes. Information relating to the modelling interface is not normative in this specification. + +Supplementary service signalling may be passed by the MSC/VLR between the A- and E-interfaces after inter-MSC handover. This procedure is transparent as far as supplementary services are concerned therefore interworking concerning this process is not described in this specification. + +Clause 2 describes general procedures for interworking between the A- and D- physical interfaces. + +Clause 3 describes the general procedures for the SS version negotiation. + +Clause 4 describes the mapping of layer 3 radio path messages with Transaction Capabilities (TC) transaction sublayer messages for interworking between the A- and D- physical interfaces. + +Clause 5 describes specific interworking procedures for all interfaces relating to call related SS activity. + +Clause 6 describes specific interworking procedures for all interfaces relating to call independent SS activity. Clause 6 also covers the interworking between the MAP User (see 3GPP TS 29.002) and the SS handling functions of the network entities (see 3GPP TS 24.010 and 3GPP TS 24.080). + +Reference is made to the following Technical Specifications: + +- 3GPP TS 22.004 and 3GPP TS 22.08x and 3GPP TS 22.09x-series, for definition of supplementary services; +- 3GPP TS 23.011, 3GPP TS 23.08x and 3GPP TS 23.09x-series, for technical realisation of supplementary services; +- 3GPP TS 24.010, 3GPP TS 24.080, 3GPP TS 24.08x and 3GPP TS 24.09x-series, for radio path signalling procedures for supplementary services; +- 3GPP TS 29.002 (MAP). + +## 1.1 Normative references + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.004: "General on supplementary services". +- [3] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)". +- [4] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1". +- [5] 3GPP TS 22.086: "Advice of Charge (AoC) supplementary services - Stage 1". +- [6] 3GPP TS 22.093: "Completion of Calls to Busy Subscriber - Stage 1". +- [7] 3GPP TS 23.011: "Technical realization of supplementary services". +- [8] 3GPP TS 23.086: "Advice of Charge (AoC) supplementary services - Stage 2". +- [9] 3GPP TS 23.093: "Completion of Calls to Busy Subscriber - Stage 2". +- [10] 3GPP TS 24.008: "Mobile radio interface layer 3 specification". +- [11] 3GPP TS 24.010: "Mobile radio interface layer 3 Supplementary services specification General aspects". +- [12] 3GPP TS 24.072: "Call Deflection supplementary service - Stage 3". +- [13] 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification Formats and coding". +- [14] 3GPP TS 24.081: "Line identification supplementary services - Stage 3". +- [15] 3GPP TS 24.082: "Call Forwarding (CF) supplementary services - Stage 3". +- [16] 3GPP TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". +- [17] 3GPP TS 24.084: "Multi Party (MPTY) supplementary services - Stage 3". +- [18] 3GPP TS 24.085: "Closed User Group (CUG) supplementary services - Stage 3". +- [19] 3GPP TS 24.086: "Advice of Charge (AoC) supplementary services - Stage 3". +- [20] 3GPP TS 24.088: "Call Barring (CB) supplementary services - Stage 3". +- [21] 3GPP TS 24.090: "Unstructured supplementary services operation - Stage 3". +- [22] 3GPP TS 24.091: "Explicit Call Transfer (ECT) supplementary services - Stage 3". +- [23] 3GPP TS 24.093: "Completion of Calls to Busy Subscriber - Stage 3". +- [24] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [25] 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station System and BSS - Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)". +- [26] 3GPP TS 23.088: "Call Barring (CB) Supplementary Service; Stage 2". + +## 1.2 Definitions and abbreviations + +Abbreviations used in this specification are listed in 3GPP TR 21.905. + +# --- 2 Introduction + +This clause describes general procedure at the MSC/VLR for SS interworking between the A- and D-interfaces. + +## 2.1 MSC/VLR procedures for handling supplementary service signalling received over the A-interface + +Upon receipt of supplementary service signalling on the A-interface, the MSC/VLR shall: + +- perform any internal SS checks or procedures appropriate to the signal (see clauses 4 and 5); +- if necessary request access to the HLR over the D-interface using the procedures defined in this specification and MAP, 3GPP TS 29.002; +- use the version indicator received from the MS to set up the right AC context name towards the HLR (see clause 3). The version indicator is described in 3GPP TS 24.010 and 3GPP TS 24.080. AC names are defined in 3GPP TS 29.002; +- perform mapping between layer 3 messages on the radio path and TC transaction sublayer messages as required (see clause 3). + +## 2.2 MSC/VLR procedures for handling supplementary service signalling received over the D-interface + +Upon receipt of supplementary service signalling on the D-interface, the MSC/VLR shall: + +- perform any internal SS checks or procedures appropriate to the signal (see clauses 4 and 5); +- handle any information elements according to the screening indicator procedure as described in 3GPP TS 24.010; +- perform mapping between TC transaction sublayer messages and layer 3 messages on the radio path as required (see clause 3). + +# --- 3 SS version negotiation + +This clause describes the general procedures for the call related and call independent supplementary services version negotiation. + +## 3.1 Call related supplementary services interworking + +No interworking identified. + +## 3.2 Call independent supplementary services interworking + +On receipt of the REGISTER message from the MS, the MSC/VLR will include the appropriate AC name in the dialogue control portion of the BEGIN message based on the following rules: + +- if no version indicator is present, no AC name is included in the BEGIN message towards the HLR (no AC name indicates "version1"); +- if the version indicator is less or equal to the highest AC name the MSC/VLR and HLR both support, the "dialogue" will be handled according to the AC name corresponding to the version indicator and to the SS operation received; +- if the version indicator is greater than the highest commonly supported AC name within the network (MSC/VLR, HLR), the "dialogue" will be handled according to this highest AC name if the request from the MS can also be fulfilled with this version of the "dialogue". + +The selection of the highest commonly supported AC name by the network is described in 3GPP TS 29.002. + +It should be noted that unknown parameters of the extension field within the Facility Information Element shall be forwarded to a phase 2 HLR according to the Extensibility rules as defined in 3GPP TS 29.002. They may be discarded when sent to a phase 1 HLR. + +According to this version of the standards, the highest AC name is "version3". + +The description method employed in the clauses 4 to 6 is tabled showing the mapping of parameter values. The exact values of the parameters and parameter tags can be found in the referenced specifications. + +# 4 Mapping between TC transaction sublayer messages and layer 3 radio path messages + +This clause describes the mapping of TC transaction sublayer messages to layer 3 radio path messages over the external interfaces. The precise coding of these messages is given in other technical specifications. + +## 4.1 D-interface to A-interface mapping + +Table 4.1 shows the mapping of TC transaction sublayer messages to layer 3 messages on the radio path. + +**Table 4.1: Mapping of TC transaction sublayer messages to layer 3 radio path messages** + +| TC transaction sublayer message | Layer 3 radio path message | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| BEGIN | REGISTER (note 1) | +| CONTINUE (note 2) | FACILITY/REGISTER (note 3) | +| END (note 2) | RELEASE COMPLETE/REGISTER (note 3) | +| ABORT (note 2) | RELEASE COMPLETE | +| NOTE 1: AC name is not mapped to a version indicator.
NOTE 2: The user information field if present is discarded.
NOTE 3: A CONTINUE or END is mapped to REGISTER if a new transaction has to be established. | | + +## 4.2 A-interface to D-interface mapping + +Table 4.2 shows the mapping of layer 3 radio path messages to TC transaction sublayer messages. + +**Table 4.2: Mapping of layer 3 radio path messages to TC transaction sublayer messages** + +| Layer 3 radio path message | TC transaction sublayer message | +|----------------------------------------------------------|---------------------------------| +| REGISTER | BEGIN (note) | +| FACILITY | CONTINUE | +| RELEASE COMPLETE | END | +| NOTE: The right AC name shall be included, see clause 3. | | + +## 4.3 Procedures + +The mapping from TC Transaction Sublayer messages to Layer 3 radio path messages must include a replacement of the tag and length of the Component Portion in the Transaction Sublayer message with the Information element identifier and length of the Facility Information Element for the Layer 3 message. Similarly for the reverse mapping. However, if a version indicator is received an AC name will be provided in the BEGIN message, see clause 3. + +All transaction sublayer messages, except the ABORT message, will normally contain one or more components. If components are included, the conversion algorithm described below applies. If a message does not contain a + +component, then the corresponding message is also sent without a component: messages shall not be withheld by the interworking function. + +For call independent SS operations each message shall only contain a single component. If a message contains more than one component then a RELEASE COMPLETE message with the cause "Facility rejected" (see 3GPP TS 24.008) and without any component shall be sent on the radio path (see 3GPP TS 24.010). + +TC Transaction sublayer messages can also contain a dialogue portion. If a user-information is received within this dialogue portion, it will not be conveyed in a Layer 3 radio path message. + +If an ABORT message is received in TC, a RELEASE COMPLETE message is to be sent on the radio path. The RELEASE COMPLETE message shall not contain any component. If a cause is to be provided to the MS, one of the cause codes of 3GPP TS 24.008 shall be used. + +If an ABORT message with a dialogue portion indicating "version fallback" (e.g. the cause "AC-not-supported") is received in TC then, if the MSC does not re-attempt the "dialogue" (e.g. by using a different AC name), it shall send a RELEASE COMPLETE to the MS with the cause "Facility rejected" (see 3GPP TS 24.008) and without any component. + +If an END message with a dialogue portion indicating "dialogue refused" is received in TC then the MSC shall send a RELEASE COMPLETE to the MS with the cause "Facility rejected" (see 3GPP TS 24.008) and without any component. + +If a layer 3 radio path message or a component in the layer 3 radio path message is rejected by the MSC, the MSC shall: + +- return a RELEASE COMPLETE message to the MS. If the reject condition is not associated with a component, one of the cause codes of 3GPP TS 24.008 shall be inserted, as described below. If it is a component (except a REJECT component), a REJECT component with the appropriate problem code shall be inserted in the RELEASE COMPLETE message, as described below. If the reject condition concerns a REJECT component the RELEASE COMPLETE message may be empty; +- terminate the transaction with the VLR by use of an ABORT message. + +If a dialogue cannot be established with the HLR because no common AC name is available then the MSC shall send a RELEASE COMPLETE to the MS with the cause "Facility rejected". + +# --- 5 Call related supplementary services management + +## 5.1 SS management in connection establishment phase + +When a CM connection is being set up between an MS and an MSC, setting up of a connection between the MSC and the VLR to request access proceeds as for normal call set-up (see 3GPP TS 29.002). Moreover, the MSC will also assess the capabilities of the MS according to the screening indicator (see 3GPP TS 24.010 and 3GPP TS 24.080). As the call set-up proceeds, the following supplementary services may apply: + +### 5.1.1 Line Identification services + +These supplementary services (described in 3GPP TS 24.081) require interworking in the MSC between both 3GPP TS 24.008, MAP (3GPP TS 29.002) and the fixed network protocol, see also 3GPP TS 29.010. + +#### 5.1.1.1 Calling Line Identification Presentation (CLIP) + +The signalling at invocation of the CLIP supplementary service is shown in figure 5.1. + +![Figure 5.1: Signalling for CLIP supplementary service. This sequence diagram shows three lifelines: MS (Mobile Station), MSC (Mobile Switching Center), and VLR (Visitor Location Register). The sequence of messages is: 1. MSC sends 'SEND INFORMATION FOR INCOMING CALL SETUP' to VLR. 2. VLR sends 'COMPLETE CALL' back to MSC. 3. MSC sends 'SETUP' to MS.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC-->>MS: SETUP + +``` + +Figure 5.1: Signalling for CLIP supplementary service. This sequence diagram shows three lifelines: MS (Mobile Station), MSC (Mobile Switching Center), and VLR (Visitor Location Register). The sequence of messages is: 1. MSC sends 'SEND INFORMATION FOR INCOMING CALL SETUP' to VLR. 2. VLR sends 'COMPLETE CALL' back to MSC. 3. MSC sends 'SETUP' to MS. + +**Figure 5.1: Signalling for CLIP supplementary service** + +When a call terminates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that the CLIP service is provided (and CLIR is not indicated in the incoming call set-up message from the PSTN), then the number of the calling subscriber (if received in the incoming call set-up) shall be mapped onto the Calling Party BCD number parameter in the SETUP message sent to the mobile. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.081. + +#### 5.1.1.2 Calling Line Identification Restriction (CLIR) + +The signalling at invocation of the CLIR supplementary service is shown in figure 5.2. + +![Figure 5.2: Signalling for CLIR supplementary service. This sequence diagram shows three lifelines: MS, MSC, and VLR. The sequence of messages is: 1. MS sends 'SETUP' to MSC. 2. MSC sends 'SEND INFORMATION FOR OUTGOING CALL SETUP' to VLR. 3. VLR sends 'COMPLETE CALL' back to MSC.](c78c2eefd86269d1740ab85a916f24f2_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MS->>MSC: SETUP + MSC->>VLR: SEND INFORMATION FOR OUTGOING CALL SETUP + VLR-->>MSC: COMPLETE CALL + +``` + +Figure 5.2: Signalling for CLIR supplementary service. This sequence diagram shows three lifelines: MS, MSC, and VLR. The sequence of messages is: 1. MS sends 'SETUP' to MSC. 2. MSC sends 'SEND INFORMATION FOR OUTGOING CALL SETUP' to VLR. 3. VLR sends 'COMPLETE CALL' back to MSC. + +**Figure 5.2: Signalling for CLIR supplementary service** + +When a call originates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that the CLIR service is provided and if the CLIR service shall be invoked (according to the presentation mode and possible subscriber request), then this information is indicated in the initial address message sent using the fixed network protocol (if possible). + +If this parameter indicates that the CLIR service is not provided and the calling subscriber has attempted to invoke CLIR, then the call set-up shall be rejected as defined in 3GPP TS 24.081. + +#### 5.1.1.3 Connected Line Identification Presentation (COLP) + +The signalling at invocation of the COLP supplementary service is shown in figure 5.3. + +![Figure 5.3: Signalling for COLP supplementary service. This sequence diagram shows three lifelines: MS, MSC, and VLR. The sequence of messages is: 1. MS sends 'SETUP' to MSC. 2. MSC sends 'SEND INFORMATION FOR OUTGOING CALL SETUP' to VLR. 3. VLR sends 'COMPLETE CALL' back to MSC. 4. MSC sends 'CONNECT' to MS.](536951b2bbd94325ae266d8d1363df8f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MS->>MSC: SETUP + MSC->>VLR: SEND INFORMATION FOR OUTGOING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC-->>MS: CONNECT + +``` + +Figure 5.3: Signalling for COLP supplementary service. This sequence diagram shows three lifelines: MS, MSC, and VLR. The sequence of messages is: 1. MS sends 'SETUP' to MSC. 2. MSC sends 'SEND INFORMATION FOR OUTGOING CALL SETUP' to VLR. 3. VLR sends 'COMPLETE CALL' back to MSC. 4. MSC sends 'CONNECT' to MS. + +**Figure 5.3: Signalling for COLP supplementary service** + +When a call originates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that the COLP service is provided, then if the connected line identity is made available by the terminating network (i.e. no interworking or presentation restrictions apply) then the connected number is passed to the calling mobile subscriber in the ConnectedNumber parameter in the CONNECT message. + +#### 5.1.1.4 Connected Line Identification Restriction (COLR) + +The signalling at invocation of the COLR supplementary service is shown in figure 5.4. + +![Figure 5.4: Signalling for COLR supplementary service. This sequence diagram shows three lifelines: MS, MSC, and VLR. The MSC sends a 'SEND INFORMATION FOR INCOMING CALL SETUP' message to the VLR. The VLR responds with a 'COMPLETE CALL' message back to the MSC. Finally, the MSC sends a 'SETUP' message to the MS.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC-->>MS: SETUP + +``` + +Figure 5.4: Signalling for COLR supplementary service. This sequence diagram shows three lifelines: MS, MSC, and VLR. The MSC sends a 'SEND INFORMATION FOR INCOMING CALL SETUP' message to the VLR. The VLR responds with a 'COMPLETE CALL' message back to the MSC. Finally, the MSC sends a 'SETUP' message to the MS. + +**Figure 5.4: Signalling for COLR supplementary service** + +When a call terminates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that the COLR service is provided, then this information is sent to the originating network using the fixed network protocol (if possible). + +### 5.1.2 Call Forwarding services + +#### 5.1.2.1 Notification to served mobile subscriber + +As described in 3GPP TS 22.082, when a subscriber has any (set of) Call Forwarding service(s) active, a notification of this fact is sent to the MS at mobile originated call set-up from the served mobile subscriber. The signalling for this notification is shown in figure 5.5. + +![Figure 5.5: Signalling for notification of invocation of Call Forwarding supplementary service. This sequence diagram shows three lifelines: MS, MSC, and VLR. The MS sends a 'SETUP' message to the MSC. The MSC sends a 'SEND INFORMATION FOR OUTGOING CALL SETUP' message to the VLR. The VLR responds with a 'COMPLETE CALL' message back to the MSC. The MSC then sends an 'ALERTING/CONNECT/FACILITY' message to the MS.](63e0c22852c26699d0bd095a2d796bab_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MS->>MSC: SETUP + MSC->>VLR: SEND INFORMATION FOR OUTGOING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC-->>MS: ALERTING/CONNECT/FACILITY + +``` + +Figure 5.5: Signalling for notification of invocation of Call Forwarding supplementary service. This sequence diagram shows three lifelines: MS, MSC, and VLR. The MS sends a 'SETUP' message to the MSC. The MSC sends a 'SEND INFORMATION FOR OUTGOING CALL SETUP' message to the VLR. The VLR responds with a 'COMPLETE CALL' message back to the MSC. The MSC then sends an 'ALERTING/CONNECT/FACILITY' message to the MS. + +**Figure 5.5: Signalling for notification of invocation of Call Forwarding supplementary service** + +The MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that a call forwarding service is active, then any of the ALERTING, CONNECT or FACILITY messages may be used to convey the required NotifySS operation in a Facility information element. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.082. + +### 5.1.3 Call Waiting service (CW) + +#### 5.1.3.1 Offering a waiting call + +The signalling for this situation is shown in figure 5.6. + +![Figure 5.6: Signalling for setting up a waiting call. This sequence diagram shows three lifelines: MS, MSC, and VLR. The MSC sends a 'SEND INFORMATION FOR INCOMING CALL SETUP' message to the VLR. The VLR responds with a 'PROCESS CW' message back to the MSC. Finally, the MSC sends a 'SETUP' message to the MS.](bdfe4e1058d1a0e14bb838771b57254c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: PROCESS CW + MSC-->>MS: SETUP + +``` + +Figure 5.6: Signalling for setting up a waiting call. This sequence diagram shows three lifelines: MS, MSC, and VLR. The MSC sends a 'SEND INFORMATION FOR INCOMING CALL SETUP' message to the VLR. The VLR responds with a 'PROCESS CW' message back to the MSC. Finally, the MSC sends a 'SETUP' message to the MS. + +**Figure 5.6: Signalling for setting up a waiting call** + +A waiting call is offered to a busy MS using a normal SETUP message including a "Signal" information element with value #7 (call waiting tone on), as described in 3GPP TS 24.083. This is the required MSC behaviour if it has received a MAP\_PROCESS\_CALL\_WAITING service primitive as a response to a MAP\_SEND\_INFO\_FOR\_INCOMING\_CALL service primitive on the B-interface. Exact values of the parameter and parameter tag are indicated in 3GPP TS 24.008. + +#### 5.1.3.2 Notification of waiting call to calling subscriber + +The signalling for this notification is shown in figure 5.7. + +![Figure 5.7: Signalling for notification of waiting call to calling subscriber. A sequence diagram showing a dashed line labeled 'ALERTING' pointing from an MSC lifeline to an MS lifeline. Both lifelines are represented by vertical dashed lines with a '+' at the top.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +Figure 5.7: Signalling for notification of waiting call to calling subscriber. A sequence diagram showing a dashed line labeled 'ALERTING' pointing from an MSC lifeline to an MS lifeline. Both lifelines are represented by vertical dashed lines with a '+' at the top. + +**Figure 5.7: Signalling for notification of waiting call to calling subscriber** + +If there are no network interworking limitations between the originating and destination MSCs, then the calling MS receives notification of his waiting call as follows: A Facility Information element in the ALERTING message includes a NotifySS operation with the following parameters: + +- SS-Code parameter indicates "callWaiting"; +- CallIsWaitingIndicator parameter indicates "callIsWaiting". + +Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.083. + +### 5.1.4 Closed User Group service (CUG) + +#### 5.1.4.1 Explicit invocation of a CUG call + +The signalling for this situation is shown in figure 5.8. + +![Figure 5.8: Signalling at explicit invocation of a CUG call. A sequence diagram showing three lifelines: MS, MSC, and VLR. A dashed arrow labeled 'SETUP' points from the MS to the MSC. A dashed arrow labeled 'SEND INFORMATION FOR OUTGOING CALL SETUP' points from the MSC to the VLR. All lifelines are represented by vertical dashed lines with a '+' at the top.](3376375fe7236a570fd0ee9448d9c4ee_img.jpg) + +Figure 5.8: Signalling at explicit invocation of a CUG call. A sequence diagram showing three lifelines: MS, MSC, and VLR. A dashed arrow labeled 'SETUP' points from the MS to the MSC. A dashed arrow labeled 'SEND INFORMATION FOR OUTGOING CALL SETUP' points from the MSC to the VLR. All lifelines are represented by vertical dashed lines with a '+' at the top. + +**Figure 5.8: Signalling at explicit invocation of a CUG call** + +When a subscriber to the CUG supplementary service sets up a call, an explicit invocation involves transport of a ForwardCUG-Info operation in a Facility information element in the SETUP message. Parameter mapping between the air-interface SETUP message and the B-interface MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL service primitive shall take place in the MSC. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.085. The parameter tags and values are mapped as follows: + +**Table 5.1: Mapping of parameter names and values for explicit invocation of a CUG call** + +| 3GPP TS 24.080 parameter name | 3GPP TS 29.002 parameter name | +|-------------------------------|-------------------------------| +| cug-Index | cug-Index | +| suppressPrefCUG | suppressPrefCUG | +| suppressOA | suppressOutgoingAccess | + +#### 5.1.4.2 Notification of CUG invocation to served MS + +The signalling for this situation is shown in figure 5.9. + +![Figure 5.9: Signalling flow for notification of CUG invocation to served MS. The diagram shows three entities: MS, MSC, and VLR. The MS sends a CALL PROCEEDING/FACILITY message to the MSC. The MSC sends a SEND INFORMATION FOR INCOMING CALL SETUP message to the VLR. The VLR sends a COMPLETE CALL message back to the MSC. The MSC then sends a CALL PROCEEDING/FACILITY message back to the MS.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: + MS->>MSC: CALL PROCEEDING/FACILITY + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC-->>MS: CALL PROCEEDING/FACILITY + +``` + +Figure 5.9: Signalling flow for notification of CUG invocation to served MS. The diagram shows three entities: MS, MSC, and VLR. The MS sends a CALL PROCEEDING/FACILITY message to the MSC. The MSC sends a SEND INFORMATION FOR INCOMING CALL SETUP message to the VLR. The VLR sends a COMPLETE CALL message back to the MSC. The MSC then sends a CALL PROCEEDING/FACILITY message back to the MS. + +**Figure 5.9: Signalling flow for notification of CUG invocation to served MS** + +The network may indicate to the MS that a CUG has been invoked for the outgoing call by sending a NotifySS operation in the Facility information element in the FACILITY or CALL PROCEEDING message towards MSa. The parameter to be included in this operation (cug-Index) is obtained from the MAP\_COMPLETE\_CALL service primitive. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.085. + +#### 5.1.4.3 Notification of rejection of CUG invocation to served MS + +The signalling for this situation is shown in figure 5.10. + +![Figure 5.10: Signalling flow for notification of rejection of CUG invocation to served MS. The diagram shows three entities: MS, MSC, and VLR. The MS sends a SETUP message to the MSC. The MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP message to the VLR. The VLR sends a SEND INFORMATION FOR OUTGOING CALL SETUP ERROR message back to the MSC. The MSC then sends a DISCONNECT/RELEASE/RELEASE COMPLETE message back to the MS.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: + MS->>MSC: SETUP + MSC->>VLR: SEND INFORMATION FOR OUTGOING CALL SETUP + VLR-->>MSC: SEND INFORMATION FOR OUTGOING CALL SETUP ERROR + MSC-->>MS: DISCONNECT/RELEASE/RELEASE COMPLETE + +``` + +Figure 5.10: Signalling flow for notification of rejection of CUG invocation to served MS. The diagram shows three entities: MS, MSC, and VLR. The MS sends a SETUP message to the MSC. The MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP message to the VLR. The VLR sends a SEND INFORMATION FOR OUTGOING CALL SETUP ERROR message back to the MSC. The MSC then sends a DISCONNECT/RELEASE/RELEASE COMPLETE message back to the MS. + +**Figure 5.10: Signalling flow for notification of rejection of CUG invocation to served MS** + +When an attempted CUG call is rejected for CUG related reasons, mapping of parameter values take places in order to inform the MSa of the failure in the DISCONNECT, RELEASE or RELEASE COMPLETE message. If the call is rejected by the serving VLR, a mapping of errors received on the B-interface (as response to MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL) to diagnostics (in the diagnostics field of the Facility Rejected cause value) must be performed. The mapping from error code to diagnostic is as follows (detailed values of tags, cause values and diagnostics are found in 3GPP TS 29.002, 3GPP TS 24.008, and 3GPP TS 24.080 respectively): + +**Table 5.2: Mapping of 3GPP TS 29.002 error causes to diagnostics at notification of rejection of CUG invocation to served MS** + +| 3GPP TS 29.002 error cause | Facility rejected #29 diagnostic field | +|---------------------------------------------|-------------------------------------------------| +| outgoingCallsBarredWithinCUG | Outgoing calls barred within the CUG | +| noCUG-Selected | No CUG selected | +| unknownCUG-Index | Unknown CUG index | +| indexIncompatibleWith RequestedBasicService | Index incompatible with requested basic service | + +If there are no network interworking restrictions (i.e. originating MSC = gateway MSC = terminating MSC), interworking between MAP and the air-interface takes place also for rejection of CUG calls by terminating end. The signalling for this situation is shown in figure 5.11. + +![Figure 5.11: Signalling flow for notification of rejection of CUG invocation from terminating end. The diagram shows three entities: MSa, MSC, and HLR. The MSC sends a 'SEND ROUTING INFO/ SEND ROUTING INFO_SMS (for MSb)' message to the HLR. The HLR responds with a 'SEND ROUTING INFO' message to the MSC. The MSC then sends a 'DISCONNECT/ RELEASE/ RELEASE COMPLETE' message to the MSa.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant MSC + participant HLR + MSC->>HLR: SEND ROUTING INFO/ +SEND ROUTING INFO_SMS +(for MSb) + HLR-->>MSC: SEND ROUTING INFO + MSC-->>MSa: DISCONNECT/ +RELEASE/ +RELEASE COMPLETE + +``` + +Figure 5.11: Signalling flow for notification of rejection of CUG invocation from terminating end. The diagram shows three entities: MSa, MSC, and HLR. The MSC sends a 'SEND ROUTING INFO/ SEND ROUTING INFO\_SMS (for MSb)' message to the HLR. The HLR responds with a 'SEND ROUTING INFO' message to the MSC. The MSC then sends a 'DISCONNECT/ RELEASE/ RELEASE COMPLETE' message to the MSa. + +**Figure 5.11: Signalling flow for notification of rejection of CUG invocation from terminating end** + +The mapping from error code to diagnostic is as follows (detailed values of tags, cause values and diagnostics are found in 3GPP TS 29.002, 3GPP TS 24.008, and 3GPP TS 24.080 respectively): + +**Table 5.3: Mapping of 3GPP TS 29.002 error causes to cause values at notification of rejection by terminating end** + +| 3GPP TS 29.002 error cause | Cause information element (cause value) | +|----------------------------------------------|-------------------------------------------------------------------------| +| calledPartySSInteractionViolation | Facility Rejected #29,
Diagnostic = CUG call failure,
unspecified | +| incomingCallsBarredWithinCUG | Incoming calls barred within the CUG #55 | +| subscriberNotMemberOfCUG | User not a member of CUG #87 | +| requestedBasicServiceViolatesCUG-Constraints | Facility Rejected #29 | + +#### 5.1.4.4 Notification of CUG invocation to terminating MS + +The signalling for this situation is shown in figure 5.12. + +![Figure 5.12: Signalling flow for notification of CUG invocation to terminating end. The diagram shows three entities: MS, MSC, and VLR. The MSC sends a 'SEND INFORMATION FOR INCOMING CALL SETUP' message to the VLR. The VLR responds with a 'COMPLETE CALL/ PROCESS CALL WAITING' message to the MSC. The MSC then sends a 'SETUP' message to the MS.](3f1987804d7d78bc3b3bc560e974280a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: COMPLETE CALL/ +PROCESS CALL WAITING + MSC-->>MS: SETUP + +``` + +Figure 5.12: Signalling flow for notification of CUG invocation to terminating end. The diagram shows three entities: MS, MSC, and VLR. The MSC sends a 'SEND INFORMATION FOR INCOMING CALL SETUP' message to the VLR. The VLR responds with a 'COMPLETE CALL/ PROCESS CALL WAITING' message to the MSC. The MSC then sends a 'SETUP' message to the MS. + +**Figure 5.12: Signalling flow for notification of CUG invocation to terminating end** + +When a CUG call arrives at the terminating end, the CUG index associated with the invoked CUG may be passed to the mobile station. The cug-Index parameter is obtained from the fixed network connection establishment request message, or if no fixed network protocol is involved (i.e. originating = terminating MSC), it is obtained from the MAP\_COMPLETE\_CALL or MAP\_PROCESS\_CALL\_WAITING service primitive. Its value is mapped onto the cug-Index parameter in the NotifySS operation in the Facility Information element of the SETUP message on the air-interface. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.085. + +### 5.1.5 Advice of Charge services + +#### 5.1.5.1 Notification of Charging information to served MS, mobile originated call + +The signalling for this situation is shown in figure 5.13. + +![Signalling flow for notification of Mobile originated Charging Information to served MS](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +A sequence diagram showing three entities: MSa, MSC, and VLR. The MSC sends a 'COMPLETE CALL' message to the VLR. The VLR responds with a 'CONNECT/FACILITY' message to the MSC, which in turn sends a 'FACILITY' message to the MSa. + +``` +sequenceDiagram + participant MSa + participant MSC + participant VLR + MSC->>VLR: COMPLETE CALL + VLR-->>MSC: CONNECT/FACILITY + MSC-->>MSa: FACILITY +``` + +Signalling flow for notification of Mobile originated Charging Information to served MS + +**Figure 5.13: Signalling flow for notification of Mobile originated Charging Information to served MS** + +The network may indicate charging information to the MS at mobile originated call set-up. The MSC knows charging information is applicable due to the inclusion of an SS-Code indicating Advice Of Charge Charging or Advice Of Charge Information in the MAP\_COMPLETE\_CALL service indication from the VLR. This parameter's value is mapped onto the SS-Code parameter in the ForwardChargeAdvice operation which is to be sent to the MS together with the relevant charging parameters. The ForwardChargeAdvice operation shall be sent in the facility information element of either the CONNECT or the FACILITY message. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.085. + +#### 5.1.5.2 Notification of Charging information to served MS, mobile terminated call + +The signalling for this situation is shown in figure 5.14. + +![Signalling flow for notification of Mobile terminated Charging Information to served MS](96b0240f56d14453b5da05ec30fd5c6e_img.jpg) + +A sequence diagram showing three entities: MSb, MSC, and VLR. The MSC sends a 'COMPLETE CALL' message to the VLR. The VLR responds with a 'FACILITY' message to the MSC, which in turn sends a 'FACILITY' message to the MSb. + +``` +sequenceDiagram + participant MSb + participant MSC + participant VLR + MSC->>VLR: COMPLETE CALL + VLR-->>MSC: FACILITY + MSC-->>MSb: FACILITY +``` + +Signalling flow for notification of Mobile terminated Charging Information to served MS + +**Figure 5.14: Signalling flow for notification of Mobile terminated Charging Information to served MS** + +The network may indicate charging information to the MS at mobile terminated call set-up. The MSC knows charging information is applicable due to the inclusion of an SS-Code indicating Advice Of Charge Charging or Advice of Charge Information in the SS-Data parameter included in the MAP\_COMPLETE\_CALL service indication from the VLR. This parameter's value is mapped onto the SS-Code parameter in the ForwardChargeAdvice operation which is to be sent to the MS together with the relevant charging parameters. The ForwardChargeAdvice operation shall be sent in the facility information element of the FACILITY message. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.085. + +### 5.1.6 Call Barring services + +These supplementary services (described in 3GPP TS 24.088) require the following interworking in the MSC: + +#### 5.1.6.1 Barring of outgoing calls + +The signalling for this situation is shown in figure 5.15. + +![Figure 5.15: Signalling flow for barring of an outgoing call. The diagram shows three entities: MS, MSC, and VLR. The MS sends a RELEASE COMPLETE message to the MSC. The MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP / SEND INFORMATION FOR MOBILE ORIGINATED SMS message to the VLR. The VLR responds with a SEND INFORMATION FOR OUTGOING CALL SETUP ERROR / SEND INFORMATION FOR MOBILE ORIGINATED SMS ERROR / ERROR message to the MSC. The MSC then sends a RELEASE COMPLETE message back to the MS.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: RELEASE COMPLETE + MSC->>VLR: SEND INFORMATION FOR OUTGOING CALL SETUP / +SEND INFORMATION FOR MOBILE ORIGINATED SMS + VLR-->>MSC: SEND INFORMATION FOR OUTGOING CALL SETUP ERROR / +SEND INFORMATION FOR MOBILE ORIGINATED SMS ERROR / +ERROR + MSC-->>MS: RELEASE COMPLETE + +``` + +Figure 5.15: Signalling flow for barring of an outgoing call. The diagram shows three entities: MS, MSC, and VLR. The MS sends a RELEASE COMPLETE message to the MSC. The MSC sends a SEND INFORMATION FOR OUTGOING CALL SETUP / SEND INFORMATION FOR MOBILE ORIGINATED SMS message to the VLR. The VLR responds with a SEND INFORMATION FOR OUTGOING CALL SETUP ERROR / SEND INFORMATION FOR MOBILE ORIGINATED SMS ERROR / ERROR message to the MSC. The MSC then sends a RELEASE COMPLETE message back to the MS. + +**Figure 5.15: Signalling flow for barring of an outgoing call** + +If the error code "CallBarred" is received as a response to the MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL or MAP\_SEND\_INFO\_FOR\_MO\_SMS service primitives on the B-interface, then a RELEASE COMPLETE message with a NotifySS operation shall be sent to the originating MS, as described in 3GPP TS 24.088. The mapping of 3GPP TS 29.002 callBarringCause to 3GPP TS 24.008 cause values is shown in table 5.4. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080, 3GPP TS 24.088 and 3GPP TS 24.008. + +**Table 5.4: Mapping of 3GPP TS 29.002 callBarringCause to 3GPP TS 24.008 cause values at barring of outgoing call** + +| 3GPP TS 29.002 callBarringCause | 3GPP TS 24.008 Cause value | +|---------------------------------|---------------------------------| +| barringServiceActive | #31: Normal Unspecified | +| operatorBarring | #8: Operator Determined Barring | +| (None) | #21: Call Rejected | + +#### 5.1.6.2 Barring of incoming calls + +The signalling for this situation is shown in figure 5.16. + +![Figure 5.16: Signalling flow for barring of an incoming call. The diagram shows three entities: MSa, GMSC, and HLRb. The GMSC sends a SEND ROUTING INFO / SEND ROUTING INFO_SMS (for MSb) message to the HLRb. The HLRb responds with a SEND ROUTING INFO / ERROR message to the GMSC. The GMSC then sends a DISCONNECT / RELEASE / RELEASE COMPLETE message to the MSa.](4aa740e8119817a3f9b9f72d06eaa53d_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant GMSC + participant HLRb + GMSC->>HLRb: SEND ROUTING INFO / +SEND ROUTING INFO_SMS +(for MSb) + HLRb-->>GMSC: SEND ROUTING INFO / +ERROR + GMSC-->>MSa: DISCONNECT / +RELEASE / +RELEASE COMPLETE + +``` + +Figure 5.16: Signalling flow for barring of an incoming call. The diagram shows three entities: MSa, GMSC, and HLRb. The GMSC sends a SEND ROUTING INFO / SEND ROUTING INFO\_SMS (for MSb) message to the HLRb. The HLRb responds with a SEND ROUTING INFO / ERROR message to the GMSC. The GMSC then sends a DISCONNECT / RELEASE / RELEASE COMPLETE message to the MSa. + +**Figure 5.16: Signalling flow for barring of an incoming call** + +If the error code "CallBarred" is received as a response to the MAP\_SEND\_ROUTING\_INFO or MAP\_SEND\_ROUTING\_INFO\_FOR\_SM service primitives on the D-interface, then if no network interworking limitations apply, a NotifySS operation shall be sent to the originating MS in the first clearing message, as described in 3GPP TS 24.088. The mapping of 3GPP TS 29.002 error causes to 3GPP TS 24.008 cause values is shown in table 5.5. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080, 3GPP TS 24.088 and 3GPP TS 24.008. + +**Table 5.5: Mapping of 3GPP TS 29.002 error causes to cause values at barring of incoming call** + +| 3GPP TS 29.002 error cause | Cause value | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| barringServiceActive | #21: Call Rejected | +| operatorBarring | #21: Call Rejected | +| anonymousCallRejection | #31: Normal, unspecified (NOTE) | +| (None) | #21: Call Rejected | +| NOTE: The GMSC will play an announcement towards the calling user to signal that the call is rejected due to anonymous call rejection. See 3GPP TS 23.088 [26]. | | + +### 5.1.7 CCBS call outcome + +For the purpose of monitoring the destination B (the target of a CCBS request activated by subscriber A), the HLR on the B-side needs to know the outcome of a CCBS call. A CCBS call is a call being set-up after acceptance of a recall (indication to subscriber A that B is idle). Thus, in case of a CCBS call, on receipt of call related messages from the MS, the MSC shall send (via the VLR) the MAP\_STATUS\_REPORT to the HLR. + +![Sequence diagram showing signalling for CCBS call outcome between MS, MSC, VLR, and HLR.](77464a47f104d0d647b2414591137b64_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note left of MS: MS + Note left of MSC: MSC + Note left of VLR: VLR + Note left of HLR: HLR + MS->>MSC: SETUP + Note right of MSC: CONNECT/ +ALERTING/ +DISCONNECT/ +RELEASE/ +RELEASE +COMPLETE + MSC->>MS: CONNECT/ +ALERTING/ +DISCONNECT/ +RELEASE/ +RELEASE +COMPLETE + MSC->>VLR: CCBS CALL DELIVERY + VLR->>HLR: STATUS_REPORT + +``` + +Sequence diagram showing signalling for CCBS call outcome between MS, MSC, VLR, and HLR. + +**Figure 5.16a: Signalling for CCBS call outcome** + +The CONNECT or ALERTING messages imply that the call establishment has been successful. Then the value of the Outcome information element in the MAP\_STATUS\_REPORT is set to success. + +The DISCONNECT and RELEASE are, in this case, error messages and can contain different causes (e.g. *Call Rejected* or *User Busy*). The MSC translates the message and/or the cause received into the proper value for the Outcome information element (*Failure* or *Busy*). + +Exact coding and values of the messages and parameter tags can be found in 3GPP TS 24.008 and 3GPP TS 29.002. + +## 5.2 SS Management in stable connection state + +When a stable CM connection is set up between a mobile station and the network, the following supplementary services may apply: + +### 5.2.1 Call Forwarding services + +#### 5.2.1.1 Notification of invocation of CFB to served mobile subscriber + +As described in 3GPP TS 22.082, when the Call Forwarding on MS Busy service is invoked by the network, a notification of this fact may be sent to the MS. The signalling for the situation when the user is NDUB is shown in figure 5.17. Note that if the subscriber is not NDUB, this notification does not apply. + +![Figure 5.17: Signalling for notification of invocation of CFB supplementary service. The diagram shows three lifelines: MS, MSC, and VLR. The MSC sends a 'SEND INFORMATION FOR INCOMING CALL SETUP' message to the VLR. The VLR responds with a 'COMPLETE CALL' message. The MSC then sends a 'FACILITY' message to the MS. A note 'NDUB established' is placed between the MSC and VLR lifelines.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note right of MSC: NDUB established + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC-->>MS: FACILITY + +``` + +Figure 5.17: Signalling for notification of invocation of CFB supplementary service. The diagram shows three lifelines: MS, MSC, and VLR. The MSC sends a 'SEND INFORMATION FOR INCOMING CALL SETUP' message to the VLR. The VLR responds with a 'COMPLETE CALL' message. The MSC then sends a 'FACILITY' message to the MS. A note 'NDUB established' is placed between the MSC and VLR lifelines. + +**Figure 5.17: Signalling for notification of invocation of CFB supplementary service** + +The MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that CFB is active, then the FACILITY message may be used to convey the required NotifySS operation in a Facility information element. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.082. + +### 5.2.2 Call Hold service (HOLD) + +As described in 3GPP TS 24.083, an MS can at any time during the active phase of a call signal invocation of the Call Hold supplementary service towards the network. This is done by use of the HOLD message (defined in 3GPP TS 24.080). When the MSC receives such a message, it requests access to the VLR and sends the MAP\_INVOKE\_SS service primitive to the VLR (as described in 3GPP TS 29.002). The interworking function triggers this behaviour by sending an internal MAP\_INVOKE\_SS signal to the MAP Service User of the MSC, indicating the following parameter values: + +- SS-Code = Call Hold; +- BS-Code = Basic service of the on-going call. + +The signalling for this situation is shown in figure 5.18. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080, 3GPP TS 24.083 and 3GPP TS 29.002. + +![Figure 5.18: Signalling flow at invocation of Call Hold supplementary service. The diagram shows three lifelines: MS, MSC, and VLR. The MS sends a 'HOLD' message to the MSC. The MSC sends an 'INVOKESS' message to the VLR. The VLR responds with an 'INVOKESS ACK' message. The MSC then sends a 'HOLD ACK/HOLD REJ' message to the MS.](327ba94498e3381cf08eb41e3fd3d77f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MS->>MSC: HOLD + MSC->>VLR: INVOKESS + VLR-->>MSC: INVOKESS ACK + MSC-->>MS: HOLD ACK/HOLD REJ + +``` + +Figure 5.18: Signalling flow at invocation of Call Hold supplementary service. The diagram shows three lifelines: MS, MSC, and VLR. The MS sends a 'HOLD' message to the MSC. The MSC sends an 'INVOKESS' message to the VLR. The VLR responds with an 'INVOKESS ACK' message. The MSC then sends a 'HOLD ACK/HOLD REJ' message to the MS. + +**Figure 5.18: Signalling flow at invocation of Call Hold supplementary service** + +If the A\_INVOKE\_SS signal from the MAP Service User in the MSC is empty, the HOLD ACKNOWLEDGE message is returned to the MS. If it refers to an error, the mapping of error causes takes place according to table 5.6. Exact values of the parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 29.002. + +**Table 5.6: Mapping of 3GPP TS 29.002 operation errors to 3GPP TS 24.080 HOLD REJECT causes** + +| 3GPP TS 29.002 operation error | 3GPP TS 24.080 HOLD REJECT cause | +|--------------------------------|--------------------------------------------| +| SystemFailure | #63: Service/Option not available | +| DataMissing | #100: Invalid Information Element contents | +| UnexpectedDataValue | #100: Invalid Info. element contents | +| CallBarred | #29: Facility Rejected | +| IllegalSS-Operation | #50: Requested Facility not subscribed | +| SS-ErrorStatus | #50: Requested facility not subscribed | +| SS-NotAvailable | #69: Requested facility not implemented | + +Note that Call Retrieval requires no communication on the B-interface, and thus no interworking requirements have been identified. + +### 5.2.3 Multi Party service (MPTY) + +As described in 3GPP TS 24.084, an MS can at any time during the active phase of a call signal invocation of the Multi Party supplementary service towards the network. This is done by including a BuildMPTY operation (defined in 3GPP TS 24.080) in a FACILITY message. When the MSC receives such a request, it requests access to the VLR and sends the MAP\_INVOKE\_SS service primitive to the VLR (as described in 3GPP TS 29.002). The interworking function triggers this behaviour by sending an internal MAP\_INVOKE\_SS signal to the MAP Service User of the MSC, indicating the following parameter values: + +- SS-Code = MPTY; +- BS-Code = Basic Service Code of the on-going calls. + +Note that the MSC does not allow the MPTY to be invoked if the two calls are not telephony calls. + +The signalling for this situation is shown in figure 5.19. + +![Figure 5.19: Signalling flow at invocation of Multi Party supplementary service. The diagram shows three entities: MS, MSC, and VLR. The MS sends a 'buildMPTY' message to the MSC. The MSC sends an 'INVOKESS' message to the VLR. The VLR sends an 'INVOKESS ACK' message back to the MSC. The MSC then sends a 'buildMPTY' message back to the MS.](a51105b2031bad93b818b82f071c6add_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: MS + Note left of MSC: MSC + Note left of VLR: VLR + MS->>MSC: buildMPTY + MSC->>VLR: INVOKESS + VLR-->>MSC: INVOKESS ACK + MSC-->>MS: buildMPTY + +``` + +Figure 5.19: Signalling flow at invocation of Multi Party supplementary service. The diagram shows three entities: MS, MSC, and VLR. The MS sends a 'buildMPTY' message to the MSC. The MSC sends an 'INVOKESS' message to the VLR. The VLR sends an 'INVOKESS ACK' message back to the MSC. The MSC then sends a 'buildMPTY' message back to the MS. + +Figure 5.19: Signalling flow at invocation of Multi Party supplementary service + +If the A\_INVOKE\_SS signal from the MAP Service User in the MSC is empty, the BuildMPTY return result is returned to the MS in a FACILITY message. If it refers to an error, the mapping of errors takes place according to table 5.7. + +Table 5.7: Mapping of 3GPP TS 29.002 operation errors to 3GPP TS 24.080 BuildMPTY errors + +| 3GPP TS 29.002 operation error | 3GPP TS 24.080 BuildMPTY error | +|--------------------------------|--------------------------------| +| SystemFailure | SystemFailure | +| DataMissing | SystemFailure | +| UnexpectedDataValue | SystemFailure | +| CallBarred | IllegalSS-Operation | +| IllegalSS-Operation | IllegalSS-Operation | +| SS-ErrorStatus | SS-ErrorStatus | +| SS-NotAvailable | SS-NotAvailable | + +Note that Holding, Retrieving and Splitting a multi party requires no communication on the B-interface, and thus no interworking requirements have been identified. + +### 5.2.4 Advice of Charge services + +#### Notification of Charging information to served MS during the call + +The network may indicate revised charging parameters (as required according to 3GPP TS 22.024, 3GPP TS 22.086, 3GPP TS 23.086 and 3GPP TS 24.086) to the MS during a call. The parameters are forwarded to MSs using the ForwardChargeAdvice operation in the facility information element of the FACILITY message. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.085. + +### 5.2.5 Explicit Call Transfer service (ECT) + +As described in 3GPP TS 24.091, an MS can at any time during the active phase of a call signal invocation of the Explicit Call Transfer supplementary service towards the network. This is done by including a ExplicitCT operation (defined in 3GPP TS 24.080) in a FACILITY message. When the MSC receives such a request, it requests access to the VLR and sends the MAP\_INVOKE\_SS service primitive to the VLR (as described in 3GPP TS 29.002). The interworking function triggers this behaviour by sending an internal MAP\_INVOKE\_SS signal to the MAP Service User of the MSC, indicating the following parameter values: + +- SS-Code = ect; +- BS-Code = Basic Service Code of the on-going calls. + +Note that the MSC does not allow the ECT to be invoked if the two calls are not telephony calls. + +The signalling for this situation is shown in the following figure 5.21. + +![Figure 5.21: Signalling flow at invocation of Explicit Call Transfer supplementary service. The diagram shows three vertical dashed lines representing the MS, MSC, and VLR. The MS sends an 'explicitCT' message to the MSC. The MSC sends an 'INVOKESS' message to the VLR. The VLR sends an 'INVOKESS ACK' message back to the MSC. The MSC sends an 'explicitCT' message back to the MS.](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: MS + Note left of MSC: MSC + Note left of VLR: VLR + MS->>MSC: explicitCT + MSC->>VLR: INVOKESS + VLR-->>MSC: INVOKESS ACK + MSC-->>MS: explicitCT + +``` + +Figure 5.21: Signalling flow at invocation of Explicit Call Transfer supplementary service. The diagram shows three vertical dashed lines representing the MS, MSC, and VLR. The MS sends an 'explicitCT' message to the MSC. The MSC sends an 'INVOKESS' message to the VLR. The VLR sends an 'INVOKESS ACK' message back to the MSC. The MSC sends an 'explicitCT' message back to the MS. + +**Figure 5.21: Signalling flow at invocation of Explicit Call Transfer supplementary service** + +If the A\_INVOKE\_SS signal from the MAP Service User in the MSC is empty, the ExplicitCT return result is returned to the MS in a DISCONNECT/RELEASE/RELEASE COMPLETE message. If it refers to an error, the mapping of errors takes place according to table 5.8. + +**Table 5.7: Mapping of 3GPP TS 29.002 operation errors to 3GPP TS 24.080 ExplicitCT errors** + +| 3GPP TS 29.002 operation error | 3GPP TS 24.080 ExplicitCT error | +|--------------------------------|---------------------------------| +| SystemFailure | SystemFailure | +| DataMissing | SystemFailure | +| UnexpectedDataValue | SystemFailure | +| CallBarred | CallBarred | +| IllegalSS-Operation | IllegalSS-Operation | +| SS-ErrorStatus | SS-ErrorStatus | +| SS-NotAvailable | SS-NotAvailable | + +## 5.3 SS Management in disconnecting phase + +When a CM connection is being released, the following supplementary services may apply: + +### 5.3.1 Call Forwarding services + +#### Notification of invocation of CFNRy to served mobile subscriber + +As described in 3GPP TS 22.082, when the Call Forwarding on No Reply service is invoked by the network, a notification of this fact may be sent to the MS as the call attempt is disconnected. The signalling for this situation is shown in figure 5.20. + +![Sequence diagram for Figure 5.20: Signalling for notification of invocation of CFNRy supplementary service. The diagram shows three lifelines: MS, MSC, and VLR. The MSC sends a 'SEND INFORMATION FOR INCOMING CALL SETUP' message to the VLR. The VLR responds with 'COMPLETE CALL'. The MSC then sends a 'SETUP' message to the MS. A vertical ellipsis indicates a timeout period. After the timeout, the MSC sends 'NRCT Timeout' to the MS. Finally, the MSC sends a series of messages to the MS: 'FACILITY/ DISCONNECT', 'RELEASE/ RELEASE COMPLETE'.](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL SETUP + VLR-->>MSC: COMPLETE CALL + MSC->>MS: SETUP + Note right of MSC: NRCT Timeout + MSC->>MS: FACILITY/ DISCONNECT + MSC->>MS: RELEASE/ RELEASE COMPLETE + +``` + +Sequence diagram for Figure 5.20: Signalling for notification of invocation of CFNRy supplementary service. The diagram shows three lifelines: MS, MSC, and VLR. The MSC sends a 'SEND INFORMATION FOR INCOMING CALL SETUP' message to the VLR. The VLR responds with 'COMPLETE CALL'. The MSC then sends a 'SETUP' message to the MS. A vertical ellipsis indicates a timeout period. After the timeout, the MSC sends 'NRCT Timeout' to the MS. Finally, the MSC sends a series of messages to the MS: 'FACILITY/ DISCONNECT', 'RELEASE/ RELEASE COMPLETE'. + +Figure 5.20: Signalling for notification of invocation of CFNRy supplementary service + +The MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP\_COMPLETE\_CALL service primitive on the B-interface. If this parameter indicates that CFNRy is active, then if required, either one of the DISCONNECT, RELEASE, RELEASE COMPLETE or FACILITY messages may be used to convey the required NotifySS operation in a Facility information element. Exact values of the parameter and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 24.082. + +### 5.3.2 CCBS Request Activation + +As described in 3GPP TS 22.093, when subscriber A encounters a busy destination B, subscriber A can request the CCBS supplementary service (i.e. activate a CCBS request against destination B). + +The signalling for this situation is shown in figure 5.21. + +![Sequence diagram for Figure 5.21: Signalling for CCBS Request Activation. The diagram shows four lifelines: MS, MSC, VLR, and HLR. The MS sends 'DISCONNECT' and 'RELEASE' messages to the MSC. The MSC sends a 'CCBS REQUEST' message to the VLR. The VLR sends a 'REGISTER_CC ENTRY' message to the HLR. The HLR responds with 'REGISTER_CC ENTRY ACK' or 'REGISTER_CC ENTRY ERROR'. The MSC receives 'CCBS REQUEST ERROR' or 'CCBS REQUEST ACK' from the VLR. Finally, the MSC sends a 'RELEASE COMPLETE' message to the MS.](421fc75480c21e7ebb25756826652367_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + MS->>MSC: DISCONNECT + MS->>MSC: RELEASE + MSC->>VLR: CCBS REQUEST + VLR->>HLR: REGISTER_CC ENTRY + HLR-->>VLR: REGISTER_CC ENTRY ACK + HLR-->>VLR: REGISTER_CC ENTRY ERROR + VLR->>MSC: CCBS REQUEST ERROR + VLR->>MSC: CCBS REQUEST ACK + MSC->>MS: RELEASE COMPLETE + +``` + +Sequence diagram for Figure 5.21: Signalling for CCBS Request Activation. The diagram shows four lifelines: MS, MSC, VLR, and HLR. The MS sends 'DISCONNECT' and 'RELEASE' messages to the MSC. The MSC sends a 'CCBS REQUEST' message to the VLR. The VLR sends a 'REGISTER\_CC ENTRY' message to the HLR. The HLR responds with 'REGISTER\_CC ENTRY ACK' or 'REGISTER\_CC ENTRY ERROR'. The MSC receives 'CCBS REQUEST ERROR' or 'CCBS REQUEST ACK' from the VLR. Finally, the MSC sends a 'RELEASE COMPLETE' message to the MS. + +Figure 5.21: Signalling for CCBS Request Activation + +The MS request the activation of CCBS in a Facility information element of a RELEASE message in response to a DISCONNECT message containing the diagnostic *CCBS is possible* and the Allowed Actions information element set to *Recall is possible*. Then, the MSC transmits the request in an Invoke component together with the call information towards the VLR in a CCBS\_REQUEST message on the B-interface. The VLR forwards it in a MAP\_REGISTER\_CC\_ENTRY on the D-interface. + +The outcome of the activation is sent back by the HLR in a MAP\_REGISTER\_CC\_ENTRY\_ACK or a MAP\_REGISTER\_CC\_ENTRY\_ERROR message. This outcome is subsequently mapped and inserted in the Facility information element of the RELEASE COMPLETE message from the MSC to the MS. + +Exact values of the parameters and parameter tags are indicated in 3GPP TS 24.008, 3GPP TS 24.080, 3GPP TS 24.093 and 3GPP TS 29.002. + +### 5.3.3 Call Deflection service + +#### 5.3.3.1 Call Deflection Operation Request + +As described in 3GPP TS 24.072, a MS may signal invocation of the Call Deflection supplementary service for a mobile terminated call at any time after call confirmation until the call is accepted. + +The signalling for this situation is shown in figure 5.22. + +![Sequence diagram showing a Call Deflection Request. The MS sends a DISCONNECT message to the MSC. The MSC then sends a COMPLETE CALL ERROR / PROCESS CALL WAITING ERROR message to the VLR.](f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MS->>MSC: DISCONNECT + MSC->>VLR: COMPLETE CALL ERROR / PROCESS CALL WAITING ERROR + +``` + +Sequence diagram showing a Call Deflection Request. The MS sends a DISCONNECT message to the MSC. The MSC then sends a COMPLETE CALL ERROR / PROCESS CALL WAITING ERROR message to the VLR. + +Figure 5.22: Signalling of a Call Deflection Request + +The MS requests Invocation of Call Deflection by including a CallDeflection operation (defined in 3GPP TS 24.080) in a DISCONNECT message. The parameters of the CallDeflection operation of the DISCONNECT message shall be transferred by the MSC to the VLR with the B-interface COMPLETE\_CALL\_ERROR or PROCESS\_CALL\_WAITING\_ERROR message. + +#### 5.3.3.2 Call Deflection Operation Response + +##### Optimal Routeing of late call forwarding is not invoked + +The signalling for this situation is shown in figure 5.23. + +![Sequence diagram showing Call Deflection Response without SOR. The MSC sends a COMPLETE CALL ERROR / PROCESS CALL WAITING ERROR to the VLR. The VLR responds with SEND INFORMATION FOR INCOMING CALL SETUP ACK / SEND INFORMATION FOR INCOMING CALL SETUP ERROR. Finally, the MSC sends a RELEASE message to the MS.](836008eb3303ade9e269f93c04dc0a2e_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + MSC->>VLR: COMPLETE CALL ERROR / PROCESS CALL WAITING ERROR + VLR->>MSC: SEND INFORMATION FOR INCOMING CALL SETUP ACK / +SEND INFORMATION FOR INCOMING CALL SETUP ERROR + MSC->>MS: RELEASE + +``` + +Sequence diagram showing Call Deflection Response without SOR. The MSC sends a COMPLETE CALL ERROR / PROCESS CALL WAITING ERROR to the VLR. The VLR responds with SEND INFORMATION FOR INCOMING CALL SETUP ACK / SEND INFORMATION FOR INCOMING CALL SETUP ERROR. Finally, the MSC sends a RELEASE message to the MS. + +Figure 5.23: Mapping of Call Deflection Response without SOR + +The MSC shall send a CallDeflection return result to the MS if the SEND\_INFO\_FOR\_INCOMING\_CALL\_ACK message is received from the VLR and the invocation of Optimal Routeing is not requested. The MSC shall send a CallDeflection return error to the MS if a SEND\_INFORMATION\_FOR\_INCOMING\_CALL\_SETUP ERROR message is received from the VLR. The MSC shall obtain the value of the CallDeflection error from the error received in the SEND\_INFORMATION\_FOR\_INCOMING\_CALL\_SETUP ERROR message. + +##### Optimal Routeing of late call forwarding is invoked: + +The signalling for this situation is shown in figure 5.24. + +![Sequence diagram for Figure 5.24: Mapping of Call Deflection Response in case of SOR. The diagram shows four lifelines: MS, MSC, VLR, and GMSC. The sequence of messages is: 1. MSC sends 'SEND INFORMATION FOR INCOMING CALL' to VLR. 2. VLR responds with 'SETUP ACK' to MSC. 3. MSC sends 'RESUME CALL HANDLING' to GMSC. 4. GMSC responds with 'RESUME CALL HANDLING ACK / RESUME CALL HANDLING ERROR' to MSC. 5. MSC sends 'RELEASE' to MS.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant GMSC + MSC->>VLR: SEND INFORMATION FOR INCOMING CALL + VLR-->>MSC: SETUP ACK + MSC->>GMSC: RESUME CALL HANDLING + GMSC-->>MSC: RESUME CALL HANDLING ACK / RESUME CALL HANDLING ERROR + MSC-->>MS: RELEASE + +``` + +Sequence diagram for Figure 5.24: Mapping of Call Deflection Response in case of SOR. The diagram shows four lifelines: MS, MSC, VLR, and GMSC. The sequence of messages is: 1. MSC sends 'SEND INFORMATION FOR INCOMING CALL' to VLR. 2. VLR responds with 'SETUP ACK' to MSC. 3. MSC sends 'RESUME CALL HANDLING' to GMSC. 4. GMSC responds with 'RESUME CALL HANDLING ACK / RESUME CALL HANDLING ERROR' to MSC. 5. MSC sends 'RELEASE' to MS. + +**Figure 5.24: Mapping of Call Deflection Response in case of SOR** + +If for a Call Deflection Request Optimal Routeing of late call forwarding is invoked the MSC shall send a CallDeflection return result to the MS if the MAP\_RESUME\_CALL\_HANDLING\_ACK is received from the GMSC. If a MAP\_RESUME\_CALL\_HANDLING\_ERROR message with error "ForwardingFailed" is received from the GMSC the MSC shall send a CallDeflection return error "ForwardingFailed" to the MS. Reception of other errors than "ForwardingFailed" in the MAP\_RESUME\_CALL\_HANDLING\_ERROR message shall lead to local processing in the MSC. + +Exact values of the parameters and parameter tags are indicated in 3GPP TS 24.080 and 3GPP TS 29.002. + +# 6 Call independent supplementary services management + +## 6.1 MS initiated SS Management + +### 6.1.1 Connection establishment phase + +Call independent supplementary service management takes place on a separate, dedicated CM connection between the mobile station and the MSC. When a request to open such a connection arrives at the MSC, the MSC will request access permission from the VLR, as described in 3GPP TS 29.002. It will also assess the capabilities of the MS according to the screening indicator, as described in 3GPP TS 24.010 and 3GPP TS 24.080. The signalling for this situation is shown in figure 6.1. + +![Sequence diagram for Figure 6.1: Signalling flow for SS connection establishment. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The sequence of messages is: 1. MS sends 'CM service request (CM service type = SS Activation)' to MSC. 2. MSC sends 'A CM_SERV_REQ (CM service type = SS Activation)' to MAP User in MSC.](6a555cff11e140861ce08db72b01a6a2_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + MS->>MSC: CM service request (CM service type = SS Activation) + MSC->>MAP User in MSC: A CM_SERV_REQ (CM service type = SS Activation) + +``` + +Sequence diagram for Figure 6.1: Signalling flow for SS connection establishment. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The sequence of messages is: 1. MS sends 'CM service request (CM service type = SS Activation)' to MSC. 2. MSC sends 'A CM\_SERV\_REQ (CM service type = SS Activation)' to MAP User in MSC. + +**Figure 6.1: Signalling flow for SS connection establishment** + +### 6.1.2 Connection established + +At this stage of the connection, the version negotiation mechanism will be invoked as described in clause 3. The abstract definition of the protocol used for call independent SS operations is imported directly from 3GPP TS 29.002 into 3GPP TS 24.080. + +The signalling for invocation of a supplementary service operation is shown in figure 6.2, while figure 6.3 shows the signalling for returning the result of the supplementary service operation. Tables 6.1 and 6.2 show the mapping of 3GPP TS 24.080 operation codes to MAP service primitives, and vice versa respectively. The detailed mapping of the contents of the facility information elements to the service primitives triggering the MAP user are described in subclause 6.3. + +![Figure 6.2: Signalling flow for SS operation invocation. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The MS sends a REGISTER/FACILITY (SS OPERATION) message to the MSC. The MSC then sends an SS_SERVICE PRIMITIVE REQ message to the MAP User in MSC.](e354b57563dae469c00b412b2abdf765_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + Note right of MS: REGISTER/FACILITY (SS OPERATION) + MS-->>MSC: REGISTER/FACILITY (SS OPERATION) + Note right of MSC: SS_SERVICE PRIMITIVE REQ + MSC-->>MAP User in MSC: SS_SERVICE PRIMITIVE REQ + +``` + +Figure 6.2: Signalling flow for SS operation invocation. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The MS sends a REGISTER/FACILITY (SS OPERATION) message to the MSC. The MSC then sends an SS\_SERVICE PRIMITIVE REQ message to the MAP User in MSC. + +Figure 6.2: Signalling flow for SS operation invocation + +Choice of service primitive on the basis of received facility information element is as follows: + +Table 6.1: Mapping of 3GPP TS 24.080 operations to 3GPP TS 29.002 service primitives + +| Facility information element operation | Service primitive for MAP Service user | +|----------------------------------------|----------------------------------------| +| RegisterSS | A REGISTER SS | +| EraseSS | A ERASE SS | +| ActivateSS | A ACTIVATE SS | +| DeactivateSS | A DEACTIVATE SS | +| InterrogateSS | A INTERROGATE SS | +| RegisterPassword | A REGISTER PASSWORD | +| ProcessUnstructuredSS-Request | A PROCESS UNSTRUCTURED SS REQUEST | +| EraseCC-Entry | A ERASE CC ENTRY | + +![Figure 6.3: Signalling flow for SS operation return result. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The MAP User in MSC sends an SS_SERVICE PRIMITIVE CNF message to the MSC. The MSC then sends a REGISTER/FACILITY (SS OPERATION) message back to the MS.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + Note right of MAP User in MSC: SS_SERVICE PRIMITIVE CNF + MAP User in MSC-->>MSC: SS_SERVICE PRIMITIVE CNF + Note right of MSC: REGISTER/FACILITY (SS OPERATION) + MSC-->>MS: REGISTER/FACILITY (SS OPERATION) + +``` + +Figure 6.3: Signalling flow for SS operation return result. The diagram shows three lifelines: MS, MSC, and MAP User in MSC. The MAP User in MSC sends an SS\_SERVICE PRIMITIVE CNF message to the MSC. The MSC then sends a REGISTER/FACILITY (SS OPERATION) message back to the MS. + +Figure 6.3: Signalling flow for SS operation return result + +Choice of facility information element on the basis of received service primitive is as follows: + +Table 6.2: Mapping of 3GPP TS 29.002 service primitives to 3GPP TS 24.080 operations + +| Service primitive for MAP Service user | Facility information element operation | +|----------------------------------------|----------------------------------------| +| A REGISTER SS | RegisterSS | +| A ERASE SS | EraseSS | +| A ACTIVATE SS | ActivateSS | +| A DEACTIVATE SS | DeactivateSS | +| A INTERROGATE SS | InterrogateSS | +| A REGISTER PASSWORD | RegisterPassword | +| A PROCESS UNSTRUCTURED SS REQUEST | ProcessUnstructuredSS-Request | +| A UNSTRUCTURED SS REQUEST | UnstructuredSS-Request | +| A UNSTRUCTURED SS NOTIFY | ProcessUnstructuredSS-Notify | +| A GET PASSWORD | GetPassword | +| A REGISTER CC ENTRY | AccessRegisterCCEntry | +| A ERASE CC ENTRY | EraseCCEntry | + +### 6.1.3 Connection release + +A supplementary service control connection is usually released by the network. The signalling for this situation is shown in figure 6.4. + +![Sequence diagram for Figure 6.4: Signalling flow for SS connection release by the network. Lifelines: MS, MSC, and MAP User in MSC. The flow starts with the MAP User in MSC sending an A_CM_REL_COMP message to the MSC. The MSC then sends a RELEASE COMPLETE message to the MS.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + Note right of MAP User in MSC: A_CM_REL_COMP + MAP User in MSC-->>MSC: A_CM_REL_COMP + Note right of MSC: RELEASE COMPLETE + MSC-->>MS: RELEASE COMPLETE + +``` + +Sequence diagram for Figure 6.4: Signalling flow for SS connection release by the network. Lifelines: MS, MSC, and MAP User in MSC. The flow starts with the MAP User in MSC sending an A\_CM\_REL\_COMP message to the MSC. The MSC then sends a RELEASE COMPLETE message to the MS. + +Figure 6.4: Signalling flow for SS connection release by the network + +However, in exceptional circumstances, the MS may request release of the connection. The signalling for this situation is shown in figure 6.5. + +![Sequence diagram for Figure 6.5: Signalling flow for SS connection release by the MS. Lifelines: MS, MSC, and MAP User in MSC. The flow starts with the MS sending a RELEASE COMPLETE message to the MSC. The MSC then sends an A_CM_SERV_REL message to the MAP User in MSC.](392a79ccd95e682ccd08f35ab2e64144_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + Note right of MS: RELEASE COMPLETE + MS-->>MSC: RELEASE COMPLETE + Note right of MSC: A_CM_SERV_REL + MSC-->>MAP User in MSC: A_CM_SERV_REL + +``` + +Sequence diagram for Figure 6.5: Signalling flow for SS connection release by the MS. Lifelines: MS, MSC, and MAP User in MSC. The flow starts with the MS sending a RELEASE COMPLETE message to the MSC. The MSC then sends an A\_CM\_SERV\_REL message to the MAP User in MSC. + +Figure 6.5: Signalling flow for SS connection release by the MS + +## 6.2 Network initiated SS Management + +### 6.2.1 Connection establishment phase + +Call independent supplementary service management takes place on a separate, dedicated CM connection between the mobile station and the MSC. The MSC may need to open a connection towards the MS (as described in 3GPP TS 24.008) to send the Network initiated SS operation to the MS. Detailed mapping rules are described in subclause 6.3. + +### 6.2.2 Connection established + +The abstract definition of the protocol used for call independent SS operations is imported directly from 3GPP TS 29.002 into 3GPP TS 24.080. + +The signalling for invocation of a Network initiated SS operation is shown in figure 6.6, while figure 6.7 shows the signalling for returning the result of supplementary service operation. + +Choice of facility information element on the basis of received service primitive is described in table 6.2. + +![Sequence diagram for Figure 6.6: Signalling flow for Network Initiated SS operation invocation. Lifelines: MS, MSC, and MAP User in MSC. The flow starts with the MAP User in MSC sending an SS_SERVICE_PRIMITIVE REQ message to the MSC. The MSC then sends a REGISTER/FACILITY (SS OPERATION) message to the MS.](62e0e858742d9a9ea4cfdc52e448e8bb_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + Note right of MAP User in MSC: SS_SERVICE_PRIMITIVE REQ + MAP User in MSC-->>MSC: SS_SERVICE_PRIMITIVE REQ + Note right of MSC: REGISTER/FACILITY (SS OPERATION) + MSC-->>MS: REGISTER/FACILITY (SS OPERATION) + +``` + +Sequence diagram for Figure 6.6: Signalling flow for Network Initiated SS operation invocation. Lifelines: MS, MSC, and MAP User in MSC. The flow starts with the MAP User in MSC sending an SS\_SERVICE\_PRIMITIVE REQ message to the MSC. The MSC then sends a REGISTER/FACILITY (SS OPERATION) message to the MS. + +Figure 6.6: Signalling flow for Network Initiated SS operation invocation + +Choice of service primitive on the basis of received facility information element is described in table 6.2. + +![Sequence diagram for Figure 6.7: Signalling flow for Network Initiated SS operation return result. Lifelines: MS, MSC, and MAP User in MSC. The flow starts with the MS sending a FACILITY (SS OPERATION) message to the MSC. The MSC then sends an SS_SERVICE_PRIMITIVE CNF message to the MAP User in MSC.](45a7858c05aeb0908776032aa9df574a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant MAP User in MSC + Note right of MS: FACILITY (SS OPERATION) + MS-->>MSC: FACILITY (SS OPERATION) + Note right of MSC: SS_SERVICE_PRIMITIVE CNF + MSC-->>MAP User in MSC: SS_SERVICE_PRIMITIVE CNF + +``` + +Sequence diagram for Figure 6.7: Signalling flow for Network Initiated SS operation return result. Lifelines: MS, MSC, and MAP User in MSC. The flow starts with the MS sending a FACILITY (SS OPERATION) message to the MSC. The MSC then sends an SS\_SERVICE\_PRIMITIVE CNF message to the MAP User in MSC. + +Figure 6.7: Signalling flow for Network Initiated SS operation return result + +### 6.2.3 Connection release + +A Network initiated SS connection is usually released by the network. The signalling for this situation is shown in figure 6.4. + +However, in exceptional circumstances, the MS may request release of the connection. The signalling for this situation is shown in figure 6.5. + +### 6.2.4 ForwardCheckSSIndication + +When a mobile station first makes contact with the network after there has been a HLR restart, an indication may be sent by the HLR to the MS to inform of possible unintended consequences with respect to supplementary services. This indication is a separate service in the MAP (MAP\_FORWARD\_CHECK\_SS\_INDICATION service), and the abstract definition of its operation (ForwardCheckSSIndication) is imported into the 3GPP TS 24.080 protocol. + +Upon receipt of ForwardCheckSSIndication from the VLR, the MSC shall create a new call independent SS transaction and then send ForwardCheckSSIndication (see 3GPP TS 24.010). + +The MSC is only required to deliver ForwardCheckSSIndication if there is an active RR connection to the MS. The network shall not page the MS in order to deliver ForwardCheckSSIndication. + +![Sequence diagram for ForwardCheckSSIndication showing message flow between MS, MSC, VLR, and HLR.](db5ab5d386827a5d5f5fad0f45612b90_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: ForwardCheckSSInd. + HLR-->>VLR: ForwardCheckSSInd. + Note right of VLR: ForwardCheckSSInd. + VLR-->>MSC: ForwardCheckSSInd. + Note right of MSC: ForwardCheckSSInd. + MSC-->>MS: ForwardCheckSSInd. + +``` + +Sequence diagram for ForwardCheckSSIndication showing message flow between MS, MSC, VLR, and HLR. + +Figure 6.8: ForwardCheckSSIndication + +### 6.2.5 CCBS Recall + +As described in 3GPP TS 22.093, when destination B, target of a CCBS request activated by subscriber A, becomes idle, the network shall automatically recall subscriber A. When subscriber A accepts the recall, the network will automatically generate a CCBS call to destination B. + +The signalling for this situation is shown in figure 6.9. + +![Sequence diagram for CCBS Recall showing message flow between MS, MSC, VLR, and HLR.](db7ae70402c81d140ae7df14b002e057_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: REMOTE_USER_FREE + HLR-->>VLR: REMOTE_USER_FREE + Note right of VLR: CCBS RUF + VLR-->>MSC: CCBS RUF + Note right of MSC: CM SERVICE PROMPT + MSC-->>MS: CM SERVICE PROMPT + Note right of MS: Procedure defined in 3GPP TS 24.093 + Note right of MS: SETUP + MS-->>MSC: SETUP + Note right of MSC: CCBS RUF ACK + MSC-->>VLR: CCBS RUF ACK + Note right of VLR: REMOTE_USER_FREE_ACK + VLR-->>HLR: REMOTE_USER_FREE_ACK + +``` + +Sequence diagram for CCBS Recall showing message flow between MS, MSC, VLR, and HLR. + +Figure 6.9: Signalling for CCBS Recall + +The indication of destination B idle is sent in the MAP\_REMOTE\_USER\_FREE service primitive. It is transmitted on the D-interface and relayed on the B-interface. Then, the recall procedure starts with the establishment of a CC connection initiated by the network with the CM SERVICE PROMPT message. The following exchange of message concerns only the A-interface and is not described here since it is already done in 3GPP TS 24.093. + +The acceptance of the recall by the user is implicit in the SETUP message sent by the MS to the MSC. This message contains the call information previously sent to the MS and the indication that the call in its establishment phase is a CCBS call. The MSC informs the HLR of this acceptance by sending a MAP\_REMOTE\_USER\_FREE\_ACK message on the B-interface and further on the D-interface. + +In case an error occurs (e.g. *MS not reachable* or *Incompatible terminal*), at any time of the recall procedure (i.e. just after the error has been received), the MSC shall send the MAP\_REMOTE\_USER\_FREE\_ERROR with the appropriate value for the Error information element. + +Exact values of the parameters and parameter tags are indicated in 3GPP TS 24.008, 3GPP TS 24.093 and 3GPP TS 29.002. + +### 6.2.6 CCBS Monitoring + +The monitoring process is initiated by the network. It is started on the B-side as soon as subscriber B becomes a target of a CCBS request. It is started on the A-side when subscriber A is found to be busy or suspends a request while being offered a recall. Since the status of a subscriber is linked to its activity, a message sent by the MS to the MSC may lead to the transmission of a message containing the new status on the D-interface (i.e. the MAP\_STATUS\_REPORT service primitive). This message contains a Status information element which can take the value *Idle*, *Not Reachable* or *Not Idle*. + +Several situations might occur, they are described in the figure 6.10. + +![Sequence diagram illustrating Signalling for CCBS Monitoring. The diagram shows four lifelines: MS, MSC, VLR, and HLR. The sequence of messages is as follows: (a) MS sends CM SERVICE REQUEST to MSC; MSC sends MS ACTIVITY to VLR; VLR sends STATUS REPORT to HLR. (b) MS sends IMSI DETACH to MSC; MSC sends DETACH IMSI to VLR; VLR sends STATUS REPORT to HLR. (c) MS sends RELEASE to MSC; MSC sends CALL END to VLR; VLR sends STATUS REPORT to HLR. (d) MS sends SETUP to MSC; MSC sends NOT IDLE to VLR; VLR sends STATUS REPORT to HLR.](9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + Note left of MS: a. + MS->>MSC: CM SERVICE REQUEST + MSC->>VLR: MS ACTIVITY + VLR->>HLR: STATUS REPORT + + Note left of MS: b. + MS->>MSC: IMSI DETACH + MSC->>VLR: DETACH IMSI + VLR->>HLR: STATUS REPORT + + Note left of MS: c. + MS->>MSC: RELEASE + MSC->>VLR: CALL END + VLR->>HLR: STATUS REPORT + + Note left of MS: d. + MS->>MSC: SETUP + MSC->>VLR: NOT IDLE + VLR->>HLR: STATUS REPORT + +``` + +Sequence diagram illustrating Signalling for CCBS Monitoring. The diagram shows four lifelines: MS, MSC, VLR, and HLR. The sequence of messages is as follows: (a) MS sends CM SERVICE REQUEST to MSC; MSC sends MS ACTIVITY to VLR; VLR sends STATUS REPORT to HLR. (b) MS sends IMSI DETACH to MSC; MSC sends DETACH IMSI to VLR; VLR sends STATUS REPORT to HLR. (c) MS sends RELEASE to MSC; MSC sends CALL END to VLR; VLR sends STATUS REPORT to HLR. (d) MS sends SETUP to MSC; MSC sends NOT IDLE to VLR; VLR sends STATUS REPORT to HLR. + +Figure 6.10: Signalling for CCBS Monitoring + +For all these situations (from a to d), the transmission of the MAP\_STATUS\_REPORT service primitive depends on the possible change of status of the MS. The detailed behaviour of this procedure is described in 3GPP TS 23.093. + +Exact coding and values of the messages are indicated in 3GPP TS 24.008 and 3GPP TS 29.002. + +## 6.3 Mapping of Operation Codes, Error Codes, Parameter Tags and Parameter Contents + +### 6.3.1 Operation codes + +The same operation codes are used for equivalent operations in 3GPP TS 24.080 and 3GPP TS 29.002 for call independent supplementary service management. + +### 6.3.2 Error codes + +For call independent supplementary service management, the same error codes are used for equivalent error types in 3GPP TS 24.080 and 3GPP TS 29.002. + +The RETURN ERROR components are also constructed in the same way on both sides of the interface. + +### 6.3.3 Parameter tags and parameter values + +The same parameter tags and parameter values are used for equivalent parameters in 3GPP TS 24.080 and 3GPP TS 29.002. \ No newline at end of file diff --git a/marked/Rel-18/29_series/29016/raw.md b/marked/Rel-18/29_series/29016/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..670a3eda7706d1c1e370da634c16bddc21ba0289 --- /dev/null +++ b/marked/Rel-18/29_series/29016/raw.md @@ -0,0 +1,670 @@ + + +# 3GPP TS 29.016 V18.0.0 (2024-04) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface network service specification (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the letters is a red signal wave icon, and below that, the text 'A GLOBAL INITIATIVE' in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 2.1 Normative references ..... | 5 | +| 2.2 Informative references..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 4 Configuration of the Gs interface..... | 7 | +| 4.1 Use of Protocol Stacks ..... | 7 | +| 5 Conformance to message transfer part (MTP) ..... | 7 | +| 5.1 General ..... | 7 | +| 5.2 MTP Level 1..... | 8 | +| 5.3 MTP Level 2..... | 8 | +| 5.3.1 MTP Level 2 for E1 Interface..... | 8 | +| 5.3.2 MTP Level 2 for T1 Interface..... | 8 | +| 5.4 MTP Level 3..... | 8 | +| 5.4.1 MTP Level 3 for E1 Interface..... | 8 | +| 5.4.1.1 General clauses ..... | 9 | +| 5.4.1.2 Configuration dependent clauses ..... | 9 | +| 5.4.1.3 Informative clauses ..... | 11 | +| 5.4.2 MTP Level 3 for T1 Interface..... | 12 | +| 5.4.2.1 General clauses ..... | 12 | +| 5.4.2.2 Configuration dependent clauses ..... | 13 | +| 5.4.2.3 Informative clauses ..... | 15 | +| 6 Conformance to SCCP ..... | 16 | +| 6.1 Overview ..... | 16 | +| 6.2 SCCP Primitives..... | 16 | +| 6.2.1 SCCP Primitives for E1 Interface (ITU Recommendation Q.711) ..... | 16 | +| 6.2.2 SCCP Primitives for T1 Interface (ANSI Standards T1.112.1) ..... | 16 | +| 6.3 SCCP messages..... | 17 | +| 6.3.1 SCCP messages for E1 Interface (ITU Recommendation Q.712)..... | 17 | +| 6.3.2 SCCP messages for T1 Interface (ANSI Standards T1.112.2)..... | 17 | +| 6.4 SCCP formats and codes..... | 18 | +| 6.4.1 SCCP format and codes for E1 Interface (ITU Recommendation Q.713) ..... | 18 | +| 6.4.2 SCCP format and codes for T1 Interface (ANSI Standards T1.112.3) ..... | 18 | +| 6.5 SCCP procedures..... | 19 | +| 6.5.1 SCCP procedures for E1 Interface (ITU Recommendation Q.714) ..... | 19 | +| 6.5.2 SCCP procedures for T1 Interface (ANSI Standards T1.112.4) ..... | 19 | +| 7 Use of the SCCP (E1/T1 Interface)..... | 20 | +| Annex A (informative): Change history..... | 21 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document provides a mechanism giving reliable transfer of signalling messages between the Serving GPRS Support Node (SGSN) and the data base of a Visitors Location Register (VLR) for co-ordination between GSM circuit switched services and GSM packet data services within the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 Indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the specification; + +# --- Introduction + +The present document specifies or references the necessary information to provide a reliable transfer of signalling messages between the Serving GPRS Support Node (SGSN) and the Visitors Location Register (VLR). This reliable transfer of messages is provided by the Network Service Part (NSP) of the Signalling System No 7 (SS7). This document specifies or references the subset of MTP and SCCP to be used in the Gs interface. + +# --- 1 Scope + +The present document specifies or references the subset of MTP and SCCP which is used for the reliable transport of BSSAP+ messages in the Gs interface. The present document references the 3GPP TS 29.202 which specifies alternative transport layers that can be applied instead of the MTP. The present document also specifies the SCCP addressing capabilities to be provided in the Gs interface. + +The present document is divided into two main parts, clause 5 dealing with the use of MTP and clauses 6 and 7 dealing with the use of SCCP. + +Clause 5 of the present document deals with the subset of the MTP that is required between an SGSN and a VLR. It is intended that this implementation of MTP is compatible with a full MTP implementation. Clause 4 references the 3GPP TS 29.202 which specifies alternatives to the MTP. + +The SCCP is used to provide message routing between the SGSN and the VLR. The SCCP routing principles specified in the present document allow to connect one SGSN to several VLR. No segmentation at SCCP level is needed on the Gs interface. Only SCCP class 0 is used on the Gs interface. Clauses 6 and 7 identify the SCCP subset that should be used between an SGSN and an VLR. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +## 2.1 Normative references + +- [1] Void. +- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service description; Stage 1". +- [3] 3GPP TS 23.003: "Numbering, addressing and identification". +- [4] 3GPP TS 43.022: "Functions related to Mobile Station (MS) in idle mode and group receive mode". +- [5] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [6] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [7] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". +- [8] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [9] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". + +- [10] 3GPP TS 49.008: "Application of the Base Station System Application Part (BSSAP) on the E-interface". +- [11] 3GPP TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface Layer 3 specification". +- [12] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [13] ITU-T Recommendation Q.711: "Functional description of the signalling connection control part". +- [14] ITU-T Recommendation Q.712: "Definition and function of signalling connection control part messages". +- [15] ITU-T Recommendation Q.713: "Signalling connection control part formats and codes". +- [16] ITU-T Recommendation Q.714: "Signalling connection control part procedures". +- [17] ITU-T Recommendation Q.702: "Signalling data link". +- [18] ITU-T Recommendation Q.703: "Signalling link". +- [19] ITU-T Recommendation Q.704: "Signalling network functions and messages". +- [20] ITU-T Recommendation Q.707: "Testing and maintenance". +- [21] ANSI T1.111 (1996):"Signalling System No. 7 (SS7); Message Transfer Part". +- [22] ANSI T1.112 (1996): "Signalling System No. 7 (SS7); Signalling Connection Control Part Functional Description". +- [41] 3GPP TS 29.202: "Signalling System No. 7 (SS7) signalling transport in core network; Stage 3". + +## 2.2 Informative references + +- [23] 3GPP TS 22.001: "Principles of telecommunication services supported by a GSM Public Land Mobile Network (PLMN)". +- [24] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)". +- [25] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)". +- [26] Void. +- [27] Void. +- [28] 3GPP TS 43.064: "Overall description of the GPRS Radio interface; Stage 2". +- [29] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference configuration". +- [30] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [31] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3". +- [32] 3GPP TS 44.065: "Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDPCP)". +- [33] 3GPP TS 48.060: "Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels." +- [34] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". +- [35] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based services and Packet Data Networks (PDN)". + +- [36] Void. +- [37] Void. +- [38] Void. +- [39] Void. +- [40] Void. + +# --- 3 Definitions, symbols and abbreviations + +Unless listed below, the definitions, symbols and abbreviations are listed in 3GPP TR 21.905 and 3GPP TS 23.060. + +# --- 4 Configuration of the Gs interface + +The Gs interface connects the Serving GPRS Support Node (SGSN) to the Visitors Location Register (VLR). This interface is defined in the 64 kbit/s for E1 interface and for 64 kbit/s or 56 kbit/s for T1 interface boundary of an SGSN to a VLR or of a VLR to an SGSN. The configuration of the Gs interface shall not impose any restriction on the number of VLRs or SGSNs to be connected by the Gs interface. The Gs interface definition shall support an early implementation of GPRS when one SGSN may be connected to several VLRs or a more mature implementation when several SGSNs may be connected to one VLR. Therefore the interface shall support the use of an STP. + +The level of resilience in the Gs interface is determined by the operator, however it is recommended that the operator considers the use of more than one multiplex system between the SGSN and the VLR. Each multiplex system should be used to carry one signalling link and routing diversity should be provided among the signalling links to increase the resilience of the system. + +## 4.1 Use of Protocol Stacks + +BSSAP+ shall be transported over SCCP and the transport layers specified in 3GPP TS 29.202. The protocol stack is shown in figure 4.1. + +When MTP is used to transport BSSAP+ then the conformance rules specified in clause 5 shall apply. + +![](78d5774278a3f4a614f8c0ae485ce8d9_img.jpg) + +| | +|----------------------------------------------------| +| BSSAP+ | +| SCCP | +| Transport layers as specified in
3GPP TS 29.202 | + +**Figure 4.1: Protocol stack for the transportation of BSSAP+** + +# --- 5 Conformance to message transfer part (MTP) + +## 5.1 General + +The MTP functions as specified in ITU-T Recommendations Q.702, Q.703, Q.704 and Q.707 for E1 interface and ANSI T1.111 Recommendations for the T1 interface are applicable. However, the following subclauses provide a minimum set of MTP requirements that shall be implemented at a SGSN or VLR to support the functionality required by the BSSAP+ protocol in the Gs interface. The set of exceptions and modifications to those recommendations maintain compatibility with the implementation of a full specification of the MTP. The ITU-T recommendations for E1 interface and ANSI recommendation for T1 interface concerning the MTP shall be taken as requirements unless covered by a statement in the present document. + +## 5.2 MTP Level 1 + +The MTP level 1 exceptions and modifications to ITU-T Recommendation Q.702 and ANSI T1.111 Recommendation can be found in 3GPP TS 48.006 subclause 3.2. + +## 5.3 MTP Level 2 + +### 5.3.1 MTP Level 2 for E1 Interface + +The MTP level 2 exceptions and modifications to ITU-T Recommendation Q.703 are listed below. + +- ITU-T Recommendation Q.703, subclause 1.4: + - Only the basic error correction protocol is required. +- ITU-T Recommendation Q.703, clause 6: + - Not applicable, only basic error correction is required. +- ITU-T Recommendation Q.703, clause 7: + - Both the SGSN and the VLR may apply the emergency proving period or the normal proving period in the initial alignment procedure. If all the signalling links between the two entities are unavailable then the SGSN or the VLR shall apply the emergency proving period until one signalling link becomes available. +- ITU-T Recommendation Q.703, clause 8: + - The processor outage status indicator shall be recognised at the SGSN and the VLR and the procedures defined in ITU-T Recommendation Q.703 clause 8 supported. The SGSN and the VLR should support the generation of the processor outage indication towards the peer entity if this is appropriate. + +### 5.3.2 MTP Level 2 for T1 Interface + +The MTP level 2 exceptions and modifications to ANSI T1.111.3 are listed below. + +- ANSI T1.111.3, subclause 1.4: + - Only the basic error correction protocol is required (subclause 1.4.3 is not required). +- ANSI T1.111.3, clause 6: + - Not applicable, only basic error correction is required. +- ANSI T1.111.3, clause 7: + - Both the SGSN and the VLR may apply the emergency proving period or the normal proving period in the initial alignment procedure. If all the signalling links between the two entities are unavailable the SGSN or the VLR shall apply the emergency proving period until one signalling link becomes available. +- ANSI T1.111.3, clause 8: + - The processor outage status indicator shall be recognised at the SGSN and the procedures defined in ANSI T1.111.3 clause 8 supported. The SGSN and the VLR shall support the generation of the processor outage indication towards the peer entity if this is appropriate. + +## 5.4 MTP Level 3 + +### 5.4.1 MTP Level 3 for E1 Interface + +The Gs interface may be configured as a point to point interface or may use an intermediate SS7 network. In this last case an SGSN or a VLR may act always as end points of the Gs interface (SP functionality) or may be configured to act + +as an transfer point between a VLR and an SGSN (SP and STP functionality). The MTP level 3 exceptions and modifications to ITU-T Recommendation Q.704 are listed regarding whether the SGSN and the VLR are connected by a point to point link or are configured to act as SPs in an SS7 network or if they support STP functionality. + +Subclause 5.4.1.1 applies to all configurations of the Gs interface. In subclause 5.4.1.2 the exceptions and modifications to ITU-T Recommendation Q.704 are listed depending upon the configuration of the Gs interface, whether it is a point to point interface or the SGSN and VLR act as an SP only or as SP and STP. Subclause 5.4.1.3 provides points of clarification about the ITU-T Recommendation Q.704. + +#### 5.4.1.1 General clauses + +The MTP level 3 exceptions and modifications to ITU-T Recommendation Q.704 regardless of whether the SGSN supports STP functionality are listed below. + +- ITU-T Recommendation Q.704, subclause 2.3.5: + - Either of the two methods of congestion control is acceptable. The most appropriate method is dependent on national ITU-T No. 7 implementations. +- ITU-T Recommendation Q.704, subclause 2.4: + - The signalling point code for an SGSN may be included in the national signalling point code scheme or in a separate signalling network. +- ITU-T Recommendation Q.704, subclause 3.8.2: + - There are two acceptable methods of congestion control defined in ITU-T Recommendation Q.704, in subclauses 3.8.2.1 a) and b). The most appropriate method is dependent on national ITU-T No. 7 implementations. Each administration should specify its congestion threshold setting algorithm and nodal congestion abatement procedures at system procurement. +- ITU-T Recommendation Q.704, clause 12: + - Only basic link management procedures are required. +- ITU-T Recommendation Q.704, subclause 14.2.1: + - Since all messages are passed using the SCCP, the service indicator for Gs interface operation will be: + + +| | | | | | +|------|---|---|---|---| +| bits | D | C | B | A | +| | 0 | 0 | 1 | 1 | +- ITU-T Recommendation Q.704, subclause 14.2.2: + - The sub service field for Gs interface operation will always be set to one of the following values: + + +| | | | | +|------|---|---|------------------| +| bits | D | C | | +| | 1 | 0 | national network | +| | 1 | 1 | local network | +- ITU-T Recommendation Q.704, clause 15: + - The formats and codes listed are only relevant to the messages that are required, i.e. those not excluded in the rest of this recommendation. + +#### 5.4.1.2 Configuration dependent clauses + +The MTP level 3 exceptions and modifications to ITU-T Recommendation Q.704 are permitted if the SGSN or the VLR does not support STP functionality are listed below. + +- ITU-T Recommendation Q.704, subclause 1.1.2: + +- If the Gs interface is configured as a point to point interface, then there will be no signalling network management features which need to be considered. + - ITU-T Recommendation Q.704, clause 2: + - If STP functionality is not required the discrimination function of the MTP used for GPRS application can be significantly simplified. +- NOTE: If the implementation of this interface is for point to point application the routing function within the MTP will be present to select the point code appropriate to the parent VLR. +- ITU-T Recommendation Q.704, subclause 2.3: + - If the implementation of the Gs interface is point to point, load sharing between linksets is not required since there will only be one linkset between SGSN and VLR. + - ITU-T Recommendation Q.704, subclause 2.4: + - At an SGSN or VLR that does not implement STP functionality, only messages with a correctly checking DPC will be accepted. Others will be discarded. It is recommended that discarding a message because of an incorrectly set point code causes an incident report to be generated. + - ITU-T Recommendation Q.704, subclause 3.1.3 c): + - In a point to point configuration there is no requirement for signalling route management. + - ITU-T Recommendation Q.704, subclause 3.3.2.3: + - In a point to point configuration there is no requirement for signalling route management. + - ITU-T Recommendation Q.704, subclause 3.3.3.3: + - In a point to point configuration there is no requirement for signalling route management. + - ITU-T Recommendation Q.704, subclause 3.3.4.3: + - In a point to point configuration there is no requirement for signalling route management. + - ITU-T Recommendation Q.704, subclause 3.4.3: + - Not applicable if no STP functionality is implemented by the SGSN or the VLR. + - ITU-T Recommendation Q.704, subclause 3.5.3: + - Not applicable if no STP functionality is implemented by the SGSN or the VLR. + - ITU-T Recommendation Q.704, subclause 3.8.5.2: + - The signalling-route-set-congestion-test procedure is not required. + - ITU-T Recommendation Q.704, subclause 4.1.2: + - In a point to point configuration signalling routes are not applicable. + - ITU-T Recommendation Q.704, subclause 4.2: + - The normal routing situation in a point to point configuration will be that there are 1 or more signalling links available between a SGSN and VLR, these will constitute a link set. They will be run in a load sharing mode and changeover, changeback procedures will be supported between these signalling links. + - The normal routing situation if more than one route is available between the SGSN and the VLR will be that the load sharing, changeover and changeback procedures would be provided between signalling links within the same signalling linkset and between signalling linksets. + - ITU-T Recommendation Q.704, subclause 4.3.3: + - There will be no alternative linkset in a point to point configuration of the Gs interface. + +- ITU-T Recommendation Q.704, subclause 4.4.3: + - Not applicable in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, subclause 4.5: + - Not applicable in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, subclause 4.6: + - Not applicable in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, subclause 4.7: + - Not applicable in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, clause 5: + - Changeover between link sets is not applicable in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, clause 6: + - Changeback between link sets is not applicable in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, clause 7: + - Forced re-routing is not applicable if there is only one signalling route existing between SGSN and VLR in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, clause 8: + - Not applicable if there is only one signalling route existing between SGSN and VLR in a point to point configuration of the Gs interface. +- ITU-T Recommendation Q.704, subclause 13.2: + - The transfer prohibited function is not applicable if the SGSN or the VLR does not support STP functionality. At the reception of a TFP message, the SGSN or VLR acting as SP shall process the message. +- ITU-T Recommendation Q.704, subclause 13.3: + - The transfer allowed function is not applicable if the SGSN or the VLR does not support STP functionality. At the reception of a TFA-message, the SGSN or VLR acting as SP shall process the message. +- ITU-T Recommendation Q.704, subclause 13.4: + - The transfer restricted function is not applicable if the SGSN or the VLR does not support STP functionality. At the reception of the TFR message, the SGSN or VLR acting as SP shall process the message. +- ITU-T Recommendation Q.704, subclause 13.5: + - The signalling-route-set-test procedure is not applicable. +- ITU-T Recommendation Q.704, subclauses 13.6, 13.7 and 13.8: + - The transfer controlled function is not applicable if the SGSN or the VLR does not support STP functionality. At the reception of TFC message, the SGSN or VLR acting as SP shall process the message. +- ITU-T Recommendation Q.704, subclause 13.9: + - The signalling route-set-congestion-test function is not required. + - At the reception of signalling-route-set-congestion-test message no action is required by the receiving entity. + +#### 5.4.1.3 Informative clauses + +A list of clarifications to ITU-T Recommendation Q.704 are listed below. + +- ITU-T Recommendation Q.704, subclause 2.3.4: + - The load sharing procedures shall allow any value of the SLC field in the MTP3 network management messages that are not related to a specific signalling link. This allows compatibility between blue book implementations where only the 0000 value is used and white book implementations where load sharing may be applicable to network management messages +- ITU-T Recommendation Q.704, subclause 3.4.1: + - It should be noted that for point to point working, the signalling route will become unavailable when the associated link set fails. +- ITU-T Recommendation Q.704, subclause 3.4.2: + - It should be noted that for point to point working, the signalling route will become available when the associated link set is restored. +- ITU-T Recommendation Q.704, subclause 3.5.1: + - It should be noted that for point to point working the procedures used in connection with signalling route unavailability will be those specified for signalling route set unavailability in ITU-T Recommendation Q.704 subclause 11.2.1. +- ITU-T Recommendation Q.704, subclause 3.5.2: + - It should be noted that for point to point interworking the procedures used in connection with signalling route availability will be those specified for signalling route set availability in ITU-T Recommendation Q.704 subclause 11.2.2. +- ITU-T Recommendation Q.704, clause 9: + - The SGSN and the MSC/VLR shall implement the restart procedures specified in ITU-T Recommendation Q.704 (03/1993) MTP3. The restart procedure specified in ITU-T Recommendation Q.704 (11/1988) MTP3 shall not be used. +- ITU-T Recommendation Q.704, clause 11: + - It should be noted that for point to point working the signalling route set will consist of one associated signalling route only. + +### 5.4.2 MTP Level 3 for T1 Interface + +The Gs interface may be configured as a point to point interface or may use an intermediate SS7 network. In this last case an SGSN or a VLR may act always as end points of the Gs interface (SP functionality) or may be configured to act as a transfer point between a VLR and an SGSN (SP and STP functionality). The MTP level 3 exceptions and modifications to ANSI T1.111.4 are listed regarding whether the SGSN and the VLR are connected by a point to point link or are configured to act as SPs in an SS7 network or if they support STP functionality. + +Subclause 5.4.2.1 applies to all configurations of the Gs interface. In subclause 5.4.2.2 the exceptions and modifications to ANSI T1.111.4 are listed depending upon the configuration of the Gs interface, whether it is a point to point interface or the SGSN and VLR act as an SP only or SP and STP. Subclause 5.4.2.3 provides points of clarification about the ANSI T1.111.4. + +#### 5.4.2.1 General clauses + +The MTP level 3 exceptions and modifications to ANSI T1.111.4 regardless of whether the SGSN supports STP functionality are listed below. + +- ANSI T1.111.4, subclause 2.3.5: + - Support of ANSI specific Signalling Link Congestion Control as specified in this subclause is required. +- ANSI T1.111.4, subclause 2.4: + +- The signalling point code for an SGSN may be included in the national signalling point code scheme or in a separate signalling network. +- ANSI T1.111.4, subclause 3.8.2: + - Support of ANSI specific Network Congestion as defined in this subclause is required. +- ANSI T1.111.4, clause 12: + - Only basic link management procedures are required. +- ANSI T1.111.4, subclause 14.2.1: + - Since all messages are passed using the SCCP, the service indicator for Gs interface operation will be: + + +| | | | | | +|------|---|---|---|---| +| bits | D | C | B | A | +| | 0 | 0 | 1 | 1 | +- ANSI T1.111.4, subclause 14.2.2: + - The sub service field for Gs interface operation will always be set to one of the following values: + + +| | | | +|------|------------------|---| +| bits | D | C | +| | 1 | 0 | +| | national network | | +- ANSI T1.111.4, clause 15: + - The formats and codes listed are only relevant to the messages that are required. + +#### 5.4.2.2 Configuration dependent clauses + +The MTP level 3 exceptions and modifications to ANSI T1.111.4 are permitted if the SGSN or the VLR does not support STP functionality are listed below. + +- ANSI T1.111.4, subclause 1.1.2: + - If the Gs interface is configured as point to point interface, i.e., it does not support STP function, then the signalling transfer point network management features are not required. +- ANSI T1.111.4, clause 2: + - If STP function is not required, then the discrimination functions of the MTP used for GPRS application can be significantly simplified. + +NOTE: If the implementation of this interface is for point to point application the routing function within the MTP will be present to select the point code appropriate to the parent VLR. + +- ANSI T1.111.4, subclause 2.3: + - If the implementation of the Gs interface is point to point, load sharing between linksets is not required since there will only be one linkset between SGSN and VLR. +- ANSI T1.111.4, subclause 2.4: + - At the SGSN or VLR that does not implement STP functionality, only messages with a correctly checking DPC will be accepted. Other messages will be discarded. It is recommended that when messages are discarded because of an incorrectly set point code, an incident report should be generated. +- ANSI T1.111.4, subclause 3.1.3 (3): + - In a point to point configuration, there is no requirement for signalling route management. +- ANSI T1.111.4, subclause 3.3.2.3: + - In a point to point configuration, there is no requirement for signalling route management. + +- ANSI T1.111.4, subclause 3.3.3.3: + - In a point to point configuration, there is no requirement for signalling route management. +- ANSI T1.111.4, subclause 3.3.4.3: + - In a point to point configuration, there is no requirement for signalling route management. +- ANSI T1.111.4, subclause 3.4.3: + - Not applicable if no STP functionality is implemented in SGSN or VLR. +- ANSI T1.111.4, subclause 3.5.3: + - Not applicable if no STP functionality is implemented in SGSN or VLR. +- ANSI T1.111.4, subclause 3.8.5.2: + - The signalling-route-set-congestion-test procedure is not required. +- ANSI T1.111.4, subclause 4.1.2: + - In a point to point configuration signalling routes are not applicable. +- ANSI T1.111.4, subclause 4.2: + - The normal routing situation in a point to point configuration will be that there are 1 or more signalling links available between a SGSN and VLR, these will constitute a link set. They will run in a load sharing mode and changeover, changeback procedures will be supported between these signalling links. + - The normal routing situation if more than one route is available between the SGSN and the VLR will be that the load sharing, changeover and changeback procedures would be provided between signalling links within the same signalling linkset and between signalling linksets. +- ANSI T1.111.4, subclause 4.3.3: + - There will be no alternative linkset in a point to point configuration of the Gs interface. +- ANSI T1.111.4, subclause 4.4.3: + - Not applicable in a point to point configuration of the Gs interface. +- ANSI T1.111.4, subclause 4.5: + - Not applicable in a point to point configuration of the Gs interface. +- ANSI T1.111.4, subclause 4.6: + - Not applicable in a point to point configuration of the Gs interface. +- ANSI T1.111.4, subclause 4.7: + - Not applicable in a point to point configuration of the Gs interface. +- ANSI T1.111.4, clause 5: + - Changeover between link sets is not applicable in a point to point configuration of the Gs interface. +- ANSI T1.111.4, clause 6: + - Changeback between link sets is not applicable in a point to point configuration of the Gs interface. +- ANSI T1.111.4, clause 7: + - Forced re-routing is not applicable since there is only one signalling route existing between SGSN and VLR in a point to point configuration of the Gs interface. +- ANSI T1.111.4, clause 8: + +- Not applicable since there is only one signalling route existing between SGSN and VLR in a point to point configuration of the Gs interface. +- ANSI T1.111.4, subclause 13.2: + - The transfer prohibited function is not applicable if the SGSN does not support STP functionality. At the reception of a TFP message, the SGSN or VLR acting as SP shall process the message. +- ANSI T1.111.4, subclause 13.3: + - The transfer allowed function is not applicable if the SGSN does not support STP functionality. At the reception of a TFA-message, the SGSN or VLR acting as SP shall process the message. +- ANSI T1.111.4, subclause 13.4: + - The transfer restricted function is not applicable if the SGSN does not support STP functionality. At the reception of the TFR message the SGSN or VLR acting as SP shall process the message. +- ANSI T1.111.4, subclause 13.5: + - The signalling-route-set-test procedure is not applicable. +- ANSI T1.111.4, subclauses 13.6, 13.7 and 13.8: + - The transfer controlled function is not applicable if the SGSN does not support STP functionality. At the reception of TFC message, the SGSN or VLR acting as SP shall process the message. +- ANSI T1.111.4, subclause 13.9: + - The signalling route-set-congestion-test function is not applicable. At the reception of signalling-route-set-congestion-test message no action is taken by the receiving entity. + +#### 5.4.2.3 Informative clauses + +A list of clarifications to ANSI Recommendation T1.111.4 are listed below. + +- ANSI T1.111.4, subclause 2.3.4: + - The load sharing procedures shall allow any value of the SLS field in the MTP3 network management messages that are not related to a specific signalling link or a default value of 00000000 should be used. +- ANSI T1.111.4, subclause 3.4.1: + - For point to point working, the signalling route will become unavailable when the associated link set fails. +- ANSI T1.111.4, subclause 3.4.2: + - For point to point working, the signalling route will become available when the associated link set is restored. +- ANSI T1.111.4, subclause 3.5.1: + - For point to point working, the procedures used in connection with signalling route unavailability will be those specified for signalling route set unavailability in ANSI Recommendation T1.111.4 subclause 11.2.1. +- ANSI T1.111.4, subclause 3.5.2: + - For point to point working, the procedures used in connection with signalling route availability will be those specified for signalling route set availability in ANSI Recommendation T1.111.4 subclause 11.2.2. +- ANSI T1.111.4, clause 9: + - The SGSN and the MSC/VLR shall implement the restart procedures specified in ANSI T1.111.4. +- ANSI T1.111.4, clause 11: + - For point to point working, the signalling route set will consist of one associated signalling route only. + +# 6 Conformance to SCCP + +## 6.1 Overview + +The purpose of this clause is to identify the subset of the SCCP functions which are necessary to provide addressing, error detection and segmentation facilities in the Gs interface. If this subset of SCCP functions is implemented, compatibility with a full ITU-T or ANSI SCCP shall be maintained. Only the needs of the user of SCCP (refer to 3GPP TS 29.018) are taken into account in this clause: the operations and maintenance requirements about SCCP functions are outside the scope of the present document. + +No SCCP translation function is required in the VLR or the SGSN between the national and the local MTP. The Destination Point Code and Subsystem Number would allow direct routing by the local SCCP and MTP. Global Title addressing is supported on the Gs interface to provide flexibility in the addressing scheme implementation (note that the SGSN is assigned a global title in order to communicate with an HLR across an inter PLMN boundary). + +Only connectionless class 0 SCCP services are used on the Gs interface. These simplifications are applicable to the signalling between an SGSN and a VLR in GSM PLMNs. + +The minimum set of SCCP functions which apply are specified in the ITU-T Recommendations Q.711, Q.712, Q.713 and Q.714, for E1 interface and ANSI T1.112 for T1 interface with the qualifications specified in this Recommendation. + +## 6.2 SCCP Primitives + +### 6.2.1 SCCP Primitives for E1 Interface (ITU Recommendation Q.711) + +- ITU-T Recommendation Q.711, clause 1: + - No SCCP connection-oriented services are used. +- ITU-T Recommendation Q.711, clause 2: + - No SCCP connection-oriented services are used. Only connectionless class 0 is used. +- ITU-T Recommendation Q.711, subclause 2.1: + - Not applicable. +- ITU-T Recommendation Q.711, subclause 4.1: + - Connection-oriented functions are not applicable + +### 6.2.2 SCCP Primitives for T1 Interface (ANSI Standards T1.112.1) + +- ANSI T1.112.1, clause 1: + - No SCCP connection-oriented services are used. +- ANSI T1.112.1, clause 2: + - No SCCP connection-oriented services are used. Only connectionless class 0. +- ANSI T1.112.1, subclause 2.1: + - Not applicable. +- ANSI T1.112.1, subclause 4.1: + - Connection-oriented functions are not applicable. + +## 6.3 SCCP messages + +### 6.3.1 SCCP messages for E1 Interface (ITU Recommendation Q.712) + +- ITU-T Recommendation Q.712, subclauses 1.1 to 1.14: + - Messages not used. +- ITU-T Recommendation Q.712, subclause 1.16: + - The Subsystem-Out-Of-Service-Grant (SOG) message is not used. +- ITU-T Recommendation Q.712, subclause 1.17: + - The Subsystem-Out-Of-Service-Request (SOR) message is not used. +- ITU-T Recommendation Q.712, subclauses 2.4, 2.6, 2.7, 2.9, 2.11, 2.12, 2.13, 2.14, 2.16 and 2.17: + - Parameters not used. + +### 6.3.2 SCCP messages for T1 Interface (ANSI Standards T1.112.2) + +- ANSI T1.112.2, subclauses 2.1 to 2.14: + - Messages not used. +- ANSI T1.112.2, subclause 3.4: + - The Subsystem-Out-Of-Service-Request (SOR) message is not used. +- ANSI T1.112.2, subclause 3.5: + - The Subsystem-Out-Of-Service-Grant (SOG) message is not used. +- ANSI T1.112.2, subclause 3.6: + - The Subsystem-Backup Routing (SBR) (Optional) message is not used. +- ANSI T1.112.2, subclause 3.7: + - The Subsystem-Normal Routing (SNR) (Optional) message is not used. +- ANSI T1.112.2, subclause 3.8: + - The Subsystem-Routing Status Test (SRT) (Optional) message is not used. +- ANSI T1.112.2, subclauses 4.2, 4.4, 4.6, 4.7, 4.10, 4.11, 4.12, 4.13, 4.15, 4.16, 4.17, 4.18 and 4.19: + - Parameters not used. + +## 6.4 SCCP formats and codes + +### 6.4.1 SCCP format and codes for E1 Interface (ITU Recommendation Q.713) + +- ITU-T Recommendation Q.713, subclause 3.4: + - The called party address shall include the appropriate sub system number. All other aspects of SCCP addressing are network specific. +- ITU-T Recommendation Q.713, subclause 3.4.2.2: + - SSN value: + - This is a national network concern. Different SSN values can be allocated for SGSN and VLR. +- ITU-T Recommendation Q.713, subclause 3.5: + - The calling party address shall include the appropriate sub system number. All other aspects of SCCP addressing are network specific. +- ITU-T Recommendation Q.713, subclause 3.6: + - Protocol class: the classes 1, 2 and 3 are not used. +- ITU-T Recommendation Q.713, subclauses 3.7 3.8, 3.9, 3.10, 3.11, 3.13, 3.14 and 3.15: + - Parameters not used. +- ITU-T Recommendation Q.713, subclauses 4.2 to 4.9 and 4.12 to 4.17: + - Messages not used. +- ITU-T Recommendation Q.713, subclause 5.1.1: + - SOR and SOG not needed. + +### 6.4.2 SCCP format and codes for T1 Interface (ANSI Standards T1.112.3) + +- ANSI T1.112.3, subclause 3.4: + - The called party address shall include the appropriate sub system number. All other aspects of SCCP addressing are network specific. +- ANSI T1.112.3, subclause 3.4.2.1: + - The SSN values are a national network concern. Different SSN values can be allocated for SGSN and VLR. +- ANSI T1.112.3, subclause 3.5: + - The calling party address shall include the appropriate sub-system number. All other aspects of SCCP addressing are network specific. +- ANSI T1.112.3, subclause 3.6: + - Protocol class: the classes 2 and 3 are not used. +- ANSI T1.112.3, subclauses 3.7, 3.8, 3.9, 3.10, 3.11, 3.13, 3.14 and 3.15: + - Parameters not used. +- ANSI T1.112.3, subclauses 4.2 to 4.9 and 4.12 to 4.17: + - Messages not used. + +- ANSI T1.112.3, subclause 5.1.1: + - SOR, SNR, SRT, SBR, and SOG not needed. + +## 6.5 SCCP procedures + +### 6.5.1 SCCP procedures for E1 Interface (ITU Recommendation Q.714) + +- ITU-T Recommendation Q.714, subclauses 1.1.2 and 1.1.3: + - Protocol classes 2 and 3 not used. + - Connection-oriented services are not used. +- ITU-T Recommendation Q.714, subclause 1.2: + - Connection-oriented services are not used. +- ITU-T Recommendation Q.714, subclause 1.3: + - Protocol class 1 not used. +- ITU-T Recommendation Q.714, subclause 2.1: + - The two basic categories of addresses for connectionless messages are used. +- ITU-T Recommendation Q.714, subclause 2.2 and 2.3: + - No connection-oriented message is used. +- ITU-T Recommendation Q.714, clause 3: + - Connection-oriented procedures are not used. +- ITU-T Recommendation Q.714, clause 5: + - Only those messages and procedures relating to non-replicated subsystems or nodes are required. + +### 6.5.2 SCCP procedures for T1 Interface (ANSI Standards T1.112.4) + +- ANSI T1.112.4, subclauses 1.1.2 and 1.1.3: + - Protocol classes 2 and 3 not used. + - Connection-oriented services are not used. +- ANSI T1.112.4, subclause 1.2: + - Connection-oriented services are not used. +- ANSI T1.112.4, subclause 1.3: + - Protocol class 1 is not used. +- ANSI T1.112.4, subclause 2.1: + - The two basic categories of addresses for connectionless messages are used. +- ANSI T1.112.4, subclause 2.2 and 2.3: + - No connection-oriented message is used. +- ANSI T1.112.4, clause 3: + - Connection-oriented procedures not used. + +- ANSI T1.112.4, clause 5: + - Only those messages and procedures relating to non-replicated subsystems or nodes are required. + +# --- 7 Use of the SCCP (E1/T1 Interface) + +The underlying transport stack and the SCCP are used to support signalling messages between the SGSN and the MSC. The BSSAP+ protocol specified in 3GPP TS 29.018 is the user of the SCCP. 3GPP TS 29.018 only uses the services of the class 0 of the SCCP. + +The Gs interface connects an SGSN to a VLR within the same PLMN. The use of point codes or global titles is allowed for routing of SCCP messages. + +The format and coding of address parameters carried by the SCCP for routing purpose shall comply with ITU-T Recommendation Q.713 for E1 interface and ANSI T1.112.3 T1 interface with the following restrictions: + +- The called party address shall include: + - an SSN (see subclause 6.4.1 E1 interface and subclause 6.4.2 for T1 interface); + - all other aspects of the SCCP signalling are specified in 3GPP TS 29.002. +- The calling party address shall include: + - an SSN (see subclause 6.4.1 E1 interface and subclause 6.4.2 for T1 interface); + - all other aspects of the SCCP signalling are specified in 3GPP TS 29.002. + +When an SCCP message is sent, the Called Party Address is derived from the Called Address of the N-UNITDATA-REQUEST primitive issued by the local SCCP user. + +When an SCCP message is received, the Calling Address within the N-UNITDATA-INDICATION primitive is derived from the Calling Party Address of the SCCP UNITDATA message received. + +Only address information belonging to the E.164 numbering plan is allowed to be included as Global Title in the Called and Calling Party Address. The SGSN and the VLR store the address of the other entity using the format received in the Calling Party Address field or the address information received in the application part of the message. \ No newline at end of file diff --git a/marked/Rel-18/29_series/29018/raw.md b/marked/Rel-18/29_series/29018/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2f023b7fc781a29b8c4702b83ca89c9c82fc5565 --- /dev/null +++ b/marked/Rel-18/29_series/29018/raw.md @@ -0,0 +1,2428 @@ + + +# 3GPP TS 29.018 V18.0.0 (2024-04) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the letters is a red signal wave icon, and below that, the text 'A GLOBAL INITIATIVE' in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| Introduction ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 2.1 Normative references ..... | 8 | +| 2.2 Informative references..... | 9 | +| 3 Definitions, symbols and abbreviations..... | 11 | +| 4 Description of the association between a VLR and an SGSN ..... | 11 | +| 4.1 Association at the VLR ..... | 11 | +| 4.1.1 States at the VLR..... | 11 | +| 4.2 Association at the SGSN..... | 12 | +| 4.2.1 MM context variables at the SGSN..... | 12 | +| 4.2.2 States at the SGSN..... | 13 | +| 4.2.3 State transitions in the SGSN without BSSAP+ signalling..... | 13 | +| 5 Paging for non-GPRS services procedure..... | 14 | +| 5.1 General description ..... | 14 | +| 5.2 Procedures in the VLR ..... | 14 | +| 5.2.1 Paging Initiation ..... | 14 | +| 5.2.2 Paging Response..... | 14 | +| 5.2.3 Paging Failure..... | 14 | +| 5.2.4 MS unreachable ..... | 15 | +| 5.3 Procedures in the SGSN..... | 15 | +| 6 Location Update for non-GPRS services procedure ..... | 16 | +| 6.1 General description ..... | 16 | +| 6.2 Procedures in the SGSN..... | 17 | +| 6.2.1 Location Update Initiation..... | 17 | +| 6.2.1.1 General..... | 17 | +| 6.2.1.2 VLR fails without restart ..... | 19 | +| 6.2.2 Location Update Response ..... | 19 | +| 6.2.3 Location Update Failure ..... | 20 | +| 6.2.4 Abnormal cases ..... | 20 | +| 6.3 Procedures in the VLR ..... | 20 | +| 6.3.1 Location Update Response ..... | 21 | +| 6.3.2 Location Update Failure ..... | 21 | +| 6.3.3 TMSI reallocation procedure..... | 21 | +| 6.3.4 Abnormal cases ..... | 21 | +| 7 Non-GPRS alert procedure ..... | 22 | +| 7.1 General description ..... | 22 | +| 7.2 Procedures in the VLR ..... | 22 | +| 7.2.1 Alert Initiation ..... | 22 | +| 7.2.2 Alert Response..... | 23 | +| 7.2.3 Alert failure ..... | 23 | +| 7.2.4 Alert Indication..... | 23 | +| 7.2.5 Abnormal cases ..... | 23 | +| 7.3 Procedures in the SGSN..... | 23 | +| 7.3.1 Alert response..... | 23 | +| 7.3.2 Alert failure ..... | 23 | +| 7.3.3 Alert indication..... | 23 | +| 8 Explicit IMSI detach from GPRS services procedure ..... | 23 | +| 8.1 General description ..... | 23 | +| 8.2 Procedures in the SGSN..... | 24 | +| 8.2.1 Explicit GPRS detach initiation..... | 24 | + +| | | | +|--------|-------------------------------------------------------------|----| +| 8.2.2 | Explicit GPRS detach Response..... | 24 | +| 8.2.3 | Abnormal cases ..... | 24 | +| 8.3 | Procedures in the VLR..... | 24 | +| 9 | Explicit IMSI detach from non-GPRS services procedure ..... | 25 | +| 9.1 | General description ..... | 25 | +| 9.2 | Procedures in the SGSN..... | 25 | +| 9.2.1 | Explicit IMSI detach initiation ..... | 25 | +| 9.2.2 | Explicit IMSI detach Response ..... | 25 | +| 9.2.3 | Abnormal cases ..... | 25 | +| 9.3 | Procedures in the VLR..... | 25 | +| 10 | Implicit IMSI detach from non-GPRS services procedure ..... | 26 | +| 10.1 | General description ..... | 26 | +| 10.2 | Procedures in the SGSN..... | 26 | +| 10.3 | Procedures in the VLR..... | 26 | +| 11 | VLR failure procedure ..... | 26 | +| 11.1 | General description ..... | 26 | +| 11.2 | Procedures in the VLR..... | 27 | +| 11.2.1 | VLR Reset Initiation..... | 27 | +| 11.2.2 | VLR Reset Response..... | 27 | +| 11.2.3 | Abnormal cases ..... | 27 | +| 11.3 | Procedures in the SGSN..... | 27 | +| 11.3.1 | VLR reset indication..... | 27 | +| 11.3.2 | Void..... | 27 | +| 12 | SGSN failure procedure ..... | 27 | +| 12.1 | General description ..... | 27 | +| 12.2 | Procedures in the SGSN..... | 28 | +| 12.2.1 | SGSN Reset Initiation ..... | 28 | +| 12.2.2 | SGSN Reset Response..... | 28 | +| 12.2.3 | Abnormal cases ..... | 28 | +| 12.3 | Procedures in the VLR..... | 28 | +| 13 | HLR failure ..... | 28 | +| 13.1 | General description ..... | 28 | +| 13.2 | Procedures in the SGSN..... | 29 | +| 14 | MS Information procedure..... | 29 | +| 14.1 | General description ..... | 29 | +| 14.2 | Procedures in the VLR..... | 29 | +| 14.3 | Procedures in the SGSN..... | 29 | +| 15 | MM information procedure..... | 30 | +| 15.1 | General description ..... | 30 | +| 15.2 | Procedures in the VLR..... | 30 | +| 15.3 | Procedures in the SGSN..... | 30 | +| 16 | Error Handling and Future Compatibility ..... | 30 | +| 16.1 | General ..... | 30 | +| 16.2 | Message too short..... | 31 | +| 16.3 | Unknown or unforeseen message type..... | 31 | +| 16.4 | Missing mandatory information element ..... | 31 | +| 16.5 | IEs unknown or unforeseen in the message ..... | 31 | +| 16.6 | Out of sequence IEs..... | 31 | +| 16.7 | Repeated IEs..... | 31 | +| 16.8 | Syntactically incorrect mandatory IE..... | 32 | +| 16.9 | Syntactically incorrect optional IEs ..... | 32 | +| 16.10 | Conditional IE errors ..... | 32 | +| 16.11 | IEs with semantically incorrect contents..... | 32 | +| 17 | Message functional definitions and contents ..... | 32 | +| 17.1 | Message Contents..... | 32 | +| 17.1.1 | BSSAP+-ALERT-ACK message ..... | 32 | + +| | | | +|-----------|--------------------------------------------------|----| +| 17.1.2 | BSSAP+-ALERT-REJECT message ..... | 32 | +| 17.1.2.1 | Gs Cause ..... | 33 | +| 17.1.3 | BSSAP+-ALERT-REQUEST message..... | 33 | +| 17.1.4 | BSSAP+-DOWNLINK-TUNNEL-REQUEST message ..... | 33 | +| 17.1.5 | BSSAP+-GPRS-DETACH-ACK message ..... | 33 | +| 17.1.6 | BSSAP+-GPRS-DETACH-INDICATION message ..... | 33 | +| 17.1.6.1 | Cell global identity (A/Gb mode only) ..... | 34 | +| 17.1.6.2 | Service area identification (Iu mode only) ..... | 34 | +| 17.1.7 | BSSAP+-IMSI-DETACH-ACK message ..... | 34 | +| 17.1.8 | BSSAP+-IMSI-DETACH-INDICATION message ..... | 34 | +| 17.1.8.1 | Cell global identity (A/Gb mode only) ..... | 35 | +| 17.1.8.2 | Location information age..... | 35 | +| 17.1.8.3 | Service area identification (Iu mode only) ..... | 35 | +| 17.1.9 | BSSAP+-LOCATION-UPDATE-ACCEPT message..... | 35 | +| 17.1.9.1 | New TMSI, or IMSI..... | 35 | +| 17.1.10 | BSSAP+-LOCATION-UPDATE-REJECT message..... | 35 | +| 17.1.10.1 | Message definition..... | 35 | +| 17.1.10.2 | Location area identifier..... | 35 | +| 17.1.11 | BSSAP+-LOCATION-UPDATE-REQUEST message..... | 36 | +| 17.1.11.1 | Old location area identifier ..... | 36 | +| 17.1.11.2 | New cell global identity ..... | 36 | +| 17.1.11.3 | TMSI status..... | 36 | +| 17.1.11.4 | Mobile station classmark ..... | 36 | +| 17.1.11.5 | New service area identification..... | 36 | +| 17.1.11.6 | IMEISV ..... | 37 | +| 17.1.11.7 | TMSI based NRI container ..... | 37 | +| 17.1.11.8 | Selected CN operator..... | 37 | +| 17.1.12 | BSSAP+-MM-INFORMATION-REQUEST..... | 37 | +| 17.1.12.1 | MM information ..... | 37 | +| 17.1.13 | BSSAP+-MOBILE-STATUS message ..... | 37 | +| 17.1.13.1 | IMSI ..... | 37 | +| 17.1.14 | BSSAP+-MS-ACTIVITY-INDICATION message..... | 37 | +| 17.1.14.1 | Cell global identity (A/Gb mode only) ..... | 38 | +| 17.1.14.2 | Service area identification (Iu mode only) ..... | 38 | +| 17.1.15 | BSSAP+-MS-INFORMATION-REQUEST message ..... | 38 | +| 17.1.16 | BSSAP+-MS-INFORMATION-RESPONSE message ..... | 38 | +| 17.1.16.1 | IMEI..... | 39 | +| 17.1.16.2 | IMIESV..... | 39 | +| 17.1.16.3 | Cell global identity (A/Gb mode only) ..... | 39 | +| 17.1.16.4 | Location information age..... | 39 | +| 17.1.16.5 | Mobile station state..... | 39 | +| 17.1.16.6 | TMSI..... | 39 | +| 17.1.16.7 | Service area identification (Iu mode only) ..... | 39 | +| 17.1.17 | BSSAP+-MS-UNREACHABLE message..... | 40 | +| 17.1.17.1 | Gs Cause ..... | 40 | +| 17.1.18 | BSSAP+-PAGING-REJECT message ..... | 40 | +| 17.1.19 | BSSAP+-PAGING-REQUEST message ..... | 40 | +| 17.1.19.1 | TMSI..... | 41 | +| 17.1.19.2 | Location area identifier ..... | 41 | +| 17.1.19.3 | Channel needed..... | 41 | +| 17.1.19.4 | eMLPP priority ..... | 41 | +| 17.1.19.5 | Global CN-Id ..... | 41 | +| 17.1.20 | BSSAP+-RESET-ACK message..... | 41 | +| 17.1.20.1 | SGSN number ..... | 41 | +| 17.1.20.2 | VLR number ..... | 41 | +| 17.1.21 | BSSAP+-RESET-INDICATION message..... | 41 | +| 17.1.21.1 | SGSN number ..... | 42 | +| 17.1.21.2 | VLR number ..... | 42 | +| 17.1.22 | BSSAP+-TMSI-REALLOCATION-COMPLETE message..... | 42 | +| 17.1.22.1 | Cell global identity (A/Gb mode only) ..... | 42 | +| 17.1.22.2 | Service area identification (Iu mode only) ..... | 42 | +| 17.1.23 | BSSAP+-UPLINK-TUNNEL-REQUEST message ..... | 42 | + +| | | | +|-------------------------------|----------------------------------------------------|-----------| +| 18 | Message format and information element coding..... | 43 | +| 18.1 | Overview ..... | 43 | +| 18.2 | Message type..... | 43 | +| 18.3 | Information Element Identifiers ..... | 44 | +| 18.3a | Length indicator ..... | 44 | +| 18.4 | Information elements..... | 44 | +| 18.4.1 | Cell global identity ..... | 44 | +| 18.4.2 | Channel needed ..... | 45 | +| 18.4.3 | Downlink Tunnel Payload Control and Info ..... | 45 | +| 18.4.4 | eMLPP Priority ..... | 45 | +| 18.4.5 | Erroneous message ..... | 46 | +| 18.4.6 | GPRS location update type..... | 46 | +| 18.4.7 | Gs cause..... | 46 | +| 18.4.8 | IMEI ..... | 47 | +| 18.4.9 | IMEISV ..... | 47 | +| 18.4.10 | IMSI..... | 48 | +| 18.4.11 | IMSI detach from GPRS service type ..... | 48 | +| 18.4.12 | IMSI detach from non-GPRS service type ..... | 49 | +| 18.4.13 | Information requested..... | 49 | +| 18.4.14 | Location area identifier..... | 50 | +| 18.4.15 | Location information age ..... | 50 | +| 18.4.16 | MM information ..... | 51 | +| 18.4.17 | Mobile identity ..... | 51 | +| 18.4.18 | Mobile station classmark 1 ..... | 51 | +| 18.4.19 | Mobile station state..... | 52 | +| 18.4.20 | PTMSI ..... | 52 | +| 18.4.21 | Reject cause..... | 53 | +| 18.4.21b | Service Area Identification..... | 53 | +| 18.4.22 | SGSN number..... | 53 | +| 18.4.23 | TMSI..... | 53 | +| 18.4.24 | TMSI status ..... | 54 | +| 18.4.25 | Uplink Tunnel Payload Control and Info ..... | 54 | +| 18.4.26 | VLR number..... | 54 | +| 18.4.27 | Global CN-Id ..... | 55 | +| 18.4.28 | TMSI based NRI container..... | 55 | +| 18.4.29 | Selected CN operator..... | 55 | +| 19 | List of system variables..... | 56 | +| 19.1 | Timers..... | 56 | +| 19.2 | Retry counters ..... | 57 | +| 20 | Procedures for Tunnelling Non-GSM Signalling ..... | 57 | +| 20.1 | Procedures in the non-GSM MSC/VLR..... | 57 | +| 20.2 | Procedures in the SGSN ..... | 57 | +| Annex A (informative): | Change history..... | 59 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies procedures used between the Serving GPRS Support Node (SGSN) and the Visitors Location Register (VLR) for co-ordination between GSM circuit switched services and GSM packet data services within the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +The present document specifies or references the procedures to provide co-ordination between the GSM circuit switched services controlled at the Visitors Location Register (VLR) and the GSM packet switched services controlled at the Serving GPRS Support Node (SGSN). The procedures specified in the present document are intended to optimise the use of the resources when an MS supports both GSM circuit switched services and GSM packet switched services. + +# 1 Scope + +The present document specifies or references procedures used on the Serving GPRS Support Node (SGSN) to Visitors Location Register (VLR) interface for interoperability between GSM circuit switched services and GSM packet data services. + +The present document specifies the layer 3 messages and procedures on the Gs interface to allow coordination between databases and to relay certain messages related to GSM circuit switched services over the GPRS subsystem. + +The functional split between VLR and SGSN is defined in 3GPP TS 23.060 [8]. The required procedures between VLR and SGSN are defined in detail in the present document. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +## 2.1 Normative references + +- [1] [Void] +- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] [Void] +- [3] [Void] +- [4] [Void] +- [5] 3GPP TS 23.003: "Numbering, addressing and identification". +- [6] 3GPP TS 23.007: "Restoration procedures". +- [6a] 3GPP TS 23.018: "Basic Call Handling; Technical realization". +- [7] [Void] +- [8] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [8a] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [9] [Void] +- [10] [Void] +- [11] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [11a] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [12] 3GPP TS 44.064: "Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) layer specification". +- [13] [Void] + +- [14] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC-BSS) interface; Layer 3 specification". +- [15] 3GPP TS 48.018: "Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [16] [Void] +- [17] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [18] [Void] +- [19] [Void] +- [20] [Void] +- [21] [Void] +- [22] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". +- [23] 3GPP TS 23.195: "Provision of UE Specific Behaviour Information to Network Entities". +- [23A] 3GPP TS 22.101: "Service Principles". +- [24] 3GPP TS 23.251: "Network sharing; Architecture and functional description". +- [25] 3GPP TS 32.422: "Subscriber and equipment trace; Trace control and Configuration Management (CM)". +- [26] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [26A] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface". +- [27] 3GPP TS 29.118: "Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification". +- [28] 3GPP TS 29.272: "MME and SGSN Related Interfaces Based on Diameter Protocol". +- [28A] 3GPP TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3". + +## 2.2 Informative references + +- [22A] [Void] +- [23B] [Void] +- [24] [Void] +- [25] [Void] +- [26] [Void] +- [27] [Void] +- [28] [Void] +- [29] [Void] +- [30] [Void] +- [31] [Void] +- [32] [Void] +- [33] [Void] + +| | | +|------|--------------------------------------------------------------------------------------| +| [34] | [Void] | +| [35] | [Void] | +| [36] | [Void] | +| [37] | [Void] | +| [38] | [Void] | +| [39] | [Void] | +| [40] | [Void] | +| [41] | [Void] | +| [42] | [Void] | +| [43] | [Void] | +| [44] | [Void] | +| [45] | [Void] | +| [46] | [Void] | +| [47] | [Void] | +| [48] | [Void] | +| [49] | [Void] | +| [50] | [Void] | +| [51] | [Void] | +| [52] | [Void] | +| [53] | [Void] | +| [54] | [Void] | +| [55] | [Void] | +| [56] | [Void] | +| [57] | [Void] | +| [58] | [Void] | +| [59] | [Void] | +| [60] | [Void] | +| [61] | [Void] | +| [62] | [Void] | +| [63] | [Void] | +| [64] | ITU-T Recommendation Q.714 (05/01): "Signalling connection control part procedures". | +| [65] | [Void] | +| [66] | [Void] | + +# 3 Definitions, symbols and abbreviations + +For the purposes of the present document the definitions, symbols and abbreviations given in 3GPP TR 21.905 [1a] and in 3GPP TS 23.060 [8] apply. Additionally the following terms and definitions of 3GPP TS 23.251 [24] apply: + +**Common PLMN** + +**Gateway core network (GWCN)** + +**Non-supporting UE** + +**Supporting UE** + +# 4 Description of the association between a VLR and an SGSN + +The Gs interface connects the databases in the MSC/VLR and the SGSN. The procedures described in the present document are used to co-ordinate the location information of MSs that are IMSI attached to both GPRS and non-GPRS services. The Gs interface is also used to convey some circuit switched related procedures via the SGSN. + +The basis for the interworking between a VLR and an SGSN is the existence of an association between those entities per MS. An association consists of the SGSN storing the number of the VLR serving the MS for circuit switched services and the VLR storing the number of the SGSN serving the MS for packet switched services. The association is only applicable to MSs in class-A mode of operation and MSs in class-B mode of operation. The Gs association is not applicable if the subscriber data indicates that the MS has subscription for packet only. The Gs association is also not applicable if the MS requests only for GPRS services and "SMS-only service" and SMS service is to be provided by the SGSN based on conditions specified in 3GPP TS 23.060 [8]. + +All the messages described in the present document use the SCCP class 0 connectionless service. + +When the return option in SCCP is used and the sender receives an N\_NOTICE indication from SCCP, the sending entity shall report to the Operation and Maintenance system (see ITU-T Recommendation Q.714 [64]). + +The behaviour of the VLR and the SGSN entities related to the Gs interface are defined by the state of the association for an MS. Individual states per association, i.e. per MS in class-A mode of operation and MS in class-B mode of operation, are held at both the VLR and the SGSN. + +## 4.1 Association at the VLR + +The states associated to the Gs interface in the VLR are specified in this clause. The state diagram at the VLR is shown in figure 4.1. The state diagram does not include the message error handling specified in clause 16. + +### 4.1.1 States at the VLR + +#### Gs-NULL + +There is no association with an SGSN for the MS and therefore the VLR considers that the MS is IMSI detached for GPRS services. In this state no BSSAP+-MS-INFORMATION-REQUEST or BSSAP+-MM-INFORMATION-REQUEST messages are sent to the SGSN. The VLR may initiate paging on the Gs interface if the 'Confirmed by Radio Contact' restoration indicator in the VLR is set to 'false' (see 3GPP TS 23.007 [6]). Any message from the SGSN is ignored apart from the BSSAP+-LOCATION-UPDATE-REQUEST message, the BSSAP+-GPRS-DETACH-INDICATION message and the BSSAP+-IMSI-DETACH-INDICATION message. + +#### LA-UPDATE PRESENT + +The VLR has received a BSSAP+-LOCATION-UPDATE-REQUEST message from the SGSN. In this state the VLR may be waiting for the outcome of the Update Location procedure from the HLR. The VLR shall send BSSAP+-PAGING-REQUEST messages to MSs in class-A and MSs in class-B mode of operation via only the Gs interface. + +#### Gs-ASSOCIATED + +The VLR considers that the MS is attached to both GPRS and non-GPRS services. In this state the VLR sends BSSAP+-PAGING-REQUEST messages to MSs in class-A mode of operation and and MSs in class-B mode of operation via only the Gs interface. The VLR can perform the MS Identification procedure and the MM information procedure. + +![State diagram at the VLR showing three states: From one of the three states (at the VLR), Gs-NULL, and Gs-ASSOCIATED. Transitions are triggered by various messages from the SGSN, MS, or MME, leading to actions like sending paging or location updates.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +``` + +stateDiagram-v2 + [*] --> FromOneOfThreeStates + FromOneOfThreeStates --> Gs_NULL: Reset received from the SGSN + FromOneOfThreeStates --> Gs_NULL: VLR failure + FromOneOfThreeStates --> Gs_NULL: Detach indication received from the SGSN or the MS + Gs_NULL --> Gs_NULL: Paging failure received + Gs_NULL --> Gs_NULL: Location Update Request received from the SGSN + Gs_NULL --> Gs_NULL: Send Paging + Gs_NULL --> LA_UPDATE_PRESENT: Send Location Update Reject + Gs_NULL --> Gs_NULL: Location Update Request received from the MS via the A interface or via the lu-CS interface, or from the MME via the SGs interface + Gs_NULL --> Gs_NULL: Paging Failure or Alert Failure received + LA_UPDATE_PRESENT --> Gs_NULL: Send Paging + LA_UPDATE_PRESENT --> Gs_NULL: Location Update Request received from the SGSN + LA_UPDATE_PRESENT --> Gs_NULL: Send Location Update Accept + Gs_NULL --> Gs_ASSOCIATED: BSSAP+-MS-UNREACHABLE message received + Gs_NULL --> Gs_ASSOCIATED: TMSI Reallocation received + Gs_NULL --> Gs_NULL: Send Paging + Gs_ASSOCIATED --> Gs_NULL: Send Paging + Gs_ASSOCIATED --> Gs_NULL: Location Update Request received from the SGSN + Gs_ASSOCIATED --> Gs_NULL: Send Location Update Accept + +``` + +State diagram at the VLR showing three states: From one of the three states (at the VLR), Gs-NULL, and Gs-ASSOCIATED. Transitions are triggered by various messages from the SGSN, MS, or MME, leading to actions like sending paging or location updates. + +NOTE: Receipt of a BSSAP+-RESET-INDICATION message from the SGSN may change or not the state of the Gs interface of all the associations associated to the restarted SGSN, see subclause 12.3. + +Figure 4.1/3GPP TS 29.018: State diagram at the VLR + +## 4.2 Association at the SGSN + +The states and MM context variables associated to the Gs interface in the SGSN are specified in this clause. The state diagram at the SGSN is shown in figure 4.2. The state diagram does not include the message error handling specified in clause 16. + +### 4.2.1 MM context variables at the SGSN + +VLRR-Reliable: Boolean + +Set to 'false' when the SGSN has received a reset indication from the VLR. The SGSN may: + +- upon reception of a combined routing and location area update request from an MS that is still attached for non-GPRS service, perform immediately the location update for non-GPRS services procedure; or +- upon reception of a periodic routing area update request from an MS that is still attached for non-GPRS services, dependent on network configuration and operator policy, + - perform a network initiated detach with detach type "IMSI detach" immediately after the completion of the periodic routing area update procedure; or + - perform immediately the location update for non-GPRS services procedure. + +EMM Combined UE Waiting Flag: Boolean + +Set to 'true' when ISR is activated and: + +- the SGSN receives a Detach Notification indicating "Local Detach" for an MS which supports EMM Combined procedures from the associated MME; or + +- the SGSN receives the request from the Serving GW for deactivating the last PDP context for an MS which supports EMM Combined procedures. + +On the fifth expiry of timer T3322 described as T3322 time-out in 3GPP TS 24.008 [11], the EMM Combined UE Waiting Flag shall be deactivated if it is activated. + +SGSN-Reset: Boolean + +Set to 'true' when the SGSN restarts after a failure. The 'SGSN-Reset' variable is unique within an SGSN and it applies to all the MM context stored in the SGSN. + +### 4.2.2 States at the SGSN + +Gs-NULL + +There is no association with a VLR for the MS and therefore the SGSN considers that the MS is IMSI detached of non-GPRS services. In this state the SGSN accepts BSSAP+-PAGING-REQUEST messages to MSs only if the 'SGSN-Reset' restoration indicator in the SGSN is set to 'true'. + +LA-UPDATE Requested + +The SGSN has sent a BSSAP+-LOCATION-UPDATE-REQUEST message to the VLR. In this state the SGSN waits for the outcome of the Location Update for non-GPRS procedure at the VLR before sending the response to the MS. In this state the SGSN accepts BSSAP+-PAGING-REQUEST messages. + +Gs-ASSOCIATED + +The SGSN stores an association for that MS. In this state the SGSN performs the Location Update for non-GPRS services procedure towards the VLR for MSs in class-A and MSs in class-B mode of operation, e.g. when the MS moves to a new LA. All conditions describing when to trigger the location update for non-GPRS services procedure are listed in subclause 6.2.1. + +![State diagram at the SGSN showing transitions between Gs-NULL, LA-UPDATE Requested, and Gs-ASSOCIATED states.](3376375fe7236a570fd0ee9448d9c4ee_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Gs-NULL : From one of the three States (at the SGSN) + Gs-NULL --> Gs-NULL : Send any detach indication (to the VLR) + Gs-NULL --> Gs-NULL : SGSN failure + Gs-NULL --> Gs-NULL : Paging received + Gs-NULL --> LA-UPDATE Requested : Send Location Area Update Request (to the VLR) + LA-UPDATE Requested --> Gs-NULL : Location Area Update Reject received + LA-UPDATE Requested --> Gs-ASSOCIATED : Location Area Update Accept received + LA-UPDATE Requested --> Gs-NULL : Paging received + Gs-ASSOCIATED --> Gs-NULL : Normal Routing Area Update Request Received from the MS + Gs-ASSOCIATED --> Gs-NULL : Combined routing area update request received from the MS with conditions listed in subclause 6.2.1. + Gs-ASSOCIATED --> Gs-NULL : Periodic routing area update request received from the MS with conditions listed in subclause 6.2.1. + Gs-ASSOCIATED --> Gs-NULL : (Any other cases) Combined routing area or periodic routing area update request received from the MS + Gs-ASSOCIATED --> Gs-NULL : Set VLR_reliable=true (whether SGSN_reset=true or not) + Gs-ASSOCIATED --> Gs-NULL : Send TMSI Reallocation + Gs-ASSOCIATED --> Gs-NULL : Send BSSAP+-MS-UNREACHABLE message + Gs-ASSOCIATED --> Gs-NULL : Paging received + +``` + +State diagram at the SGSN showing transitions between Gs-NULL, LA-UPDATE Requested, and Gs-ASSOCIATED states. + +Figure 4.2/3GPP TS 29.018: State diagram at the SGSN + +### 4.2.3 State transitions in the SGSN without BSSAP+ signalling + +During the routing area update procedure or tracking area update procedure (see 3GPP TS 23.060 [8] and 3GPP TS 23.401[8a]) and if the Gs association is not Gs-NULL, the SGSN may change the state of the Gs association to Gs-NULL upon receipt of a SGSN Context Acknowledge message (see 3GPP TS 29.060 [26A]) or Context Acknowledge message without ISR activation (see 3GPP TS 29.274 [28A]) from the target network. + +During the inter-system handover from A/Gb mode or Iu mode to S1 mode, or handover from A/Gb mode or Iu mode to A/Gb mode or Iu mode (see 3GPP TS 23.060 [8] and 3GPP TS 23.401[8a]) and if the Gs association is not Gs-NULL, the SGSN may change the state of the Gs association to Gs-NULL upon receipt of a Forward Relocation Complete (see 3GPP TS 29.060 [26A]) or Forward Relocation Complete Notification message without ISR activation (see 3GPP TS 29.274 [28A]) from the target network. + +If the SGSN receives a normal attach request or a normal routing area update request from the MS in state Gs-ASSOCIATED, the SGSN shall change the state of the Gs association to Gs-NULL without explicit signalling towards the VLR (see 3GPP TS 23.060 [8]). + +# --- 5 Paging for non-GPRS services procedure + +## 5.1 General description + +This procedure is used by the VLR to send a BSSAP+-PAGING-REQUEST message to an MS via the GPRS service. This procedure applies to MSs that are simultaneously IMSI attached for GPRS services and non-GPRS services. The procedure can be performed simultaneously with any other procedure at the Gs interface. + +## 5.2 Procedures in the VLR + +The VLR shall handle the timers, queuing and retransmission for sending the BSSAP+-PAGING-REQUEST message on the Gs interface in the same way that it handles the sending of a PAGING message on the A or Iu-CS interface. + +### 5.2.1 Paging Initiation + +When a VLR has to page a GPRS MS it shall check whether the MSC has an SCCP connection for that MS. If no SCCP connection exists the VLR checks the state of the association to an SGSN and the value of the restoration indicators for that MS. The VLR sends BSSAP+-PAGING-REQUEST messages to the SGSN if the state of the association for the MS is Gs-ASSOCIATED, LA-UPDATE-PRESENT or if the state of the association is Gs-NULL and the 'Confirmed by Radio Contact' restoration indicator is set to 'false'. The sending of the BSSAP+-PAGING-REQUEST message does not change the state of the association with the SGSN. + +If the 'Confirmed by Radio Contact' restoration indicator is set to 'true', the VLR shall include the Location area identifier IE into the BSSAP+-PAGING-REQUEST message, otherwise (i.e. after a VLR failure) the Location area identifier IE shall not be included. When sending the BSSAP+-PAGING-REQUEST message, the VLR shall start timer T5. + +If the state of the association is Gs-NULL and the restoration indicator 'Confirmed by Radio Contact' is set to 'false', the VLR shall also perform a search procedure as specified in 3GPP TS 23.018 [6a]. + +While domain specific access control of the PS domain is ongoing the VLR shall be configured to send paging messages on the Gs, A and Iu-CS interfaces. + +Dependent on network configuration or operator policy, if the GPRS MS did not respond to a first paging on Gs interface, and A/Iu-CS paging has not been initiated already, the VLR may page on the A/Iu-CS interface. + +### 5.2.2 Paging Response + +The VLR stops the paging procedure on expiry of timer T5 or on receipt of an SCCP connection establishment containing the Initial L3 message from the MS via the A or Iu-CS interface. + +If the paging response is received from a location area which differs from the one stored in the VLR, the VLR shall move the Gs association to the Gs-NULL state after the MS has been authenticated successfully. + +### 5.2.3 Paging Failure + +On receipt of a BSSAP+-PAGING-REJECT message before the timer T5 expires, the VLR stops timer T5, the association is moved to the Gs-NULL state and within this state the association is marked with the contents of the Gs Cause IE. + +### 5.2.4 MS unreachable + +On receipt of a BSSAP+-MS-UNREACHABLE message before the timer T5 expires, the VLR stops timer T5 and the paging procedure for that paging request towards the SGSN is stopped. The state of the association at the VLR is not changed. + +## 5.3 Procedures in the SGSN + +The SGSN accepts BSSAP+-PAGING-REQUEST messages in any state of the association apart from Gs-NULL. Nevertheless the SGSN also accepts BSSAP+-PAGING-REQUEST messages in the Gs-NULL state if the 'SGSN-Reset' restoration indicator at the SGSN is set to 'true'. When an SGSN receives a BSSAP+-PAGING-REQUEST message from a VLR, the SGSN shall first check if the MS is known by the SGSN. The handling of the paging request depends on the state of the association and the MM context variables at the SGSN: + +- a) The MS is known and the restoration indicator 'SGSN-Reset' at the SGSN is set to 'false': + - If the MS is considered to be IMSI attached for GPRS and non-GPRS services (i.e. the association is not in the state Gs-NULL), the SGSN shall page the MS based on the location information stored in the SGSN. If the location area stored in the SGSN differs from the one received in the BSSAP+-PAGING-REQUEST message, the SGSN shall use the IMSI to page the MS. If the BSSAP+-PAGING-REQUEST message does not include the Location area identifier information element, the SGSN may set the "VLR-Reliable" MM context variable to "false". + - If the MS is marked as IMSI detached for GPRS services or IMSI (implicitly or explicitly) detached for non-GPRS services (i.e. the state of the association is Gs-NULL), the SGSN shall return a BSSAP+-PAGING-REJECT message to that VLR indicating in the Gs Cause IE the detach circumstance ('IMSI detached for GPRS services', 'IMSI detached for non-GPRS services' or 'IMSI implicitly detached for non-GPRS services'). + - If the MS is marked as unreachable (i.e. the PPF flag is set to 'false') the SGSN shall return a BSSAP+-MS-UNREACHABLE message to that VLR indicating in the Gs Cause IE 'MS unreachable'. The state of the association does not change at the SGSN. + - b) The MS is known and the restoration indicator 'SGSN-Reset' at the SGSN is set to 'true': + - If the BSSAP+-PAGING-REQUEST message includes the Location area identifier IE, the SGSN shall page the MS in all the routeing areas served by the SGSN that are included in the location area indicated in the Location area identifier IE. + - If the BSSAP+-PAGING-REQUEST message does not include the Location area identifier IE, the SGSN may page in all the routeing areas served by the SGSN that are also served by the sending VLR. +- NOTE 1: The SGSN can handle the paging request as a) for the purpose of optimization if the MS is known. +- c) The MS is not known and the restoration indicator 'SGSN-Reset' at the SGSN is set to 'false': + - The SGSN shall return a BSSAP+-PAGING-REJECT message to that VLR indicating in the Gs Cause IE 'IMSI unknown'. + - d) The MS is not known and the restoration indicator 'SGSN-Reset' at the SGSN is set to 'true': + - If the VLR provides the Location area identifier IE, the SGSN shall page within the location area indicated by the VLR. Otherwise the SGSN may page in all the routeing areas served by the SGSN that are also served by the sending VLR. + +If the SGSN accepts the paging request, the SGSN shall process the BSSAP+-PAGING-REQUEST message before sending the message on the Gb/Iu-PS interface. The result of the processing on the BSSAP+-PAGING-REQUEST message is the PAGING CS message (see 3GPP TS 48.018 [15]) sent on the Gb interface or the PAGING message with CN Domain Indicator 'CS domain' (see 3GPP TS 25.413 [22]) sent on the Iu-PS interface. + +The SGSN shall not retransmit the PAGING CS message on the Gb interface or the PAGING message on the Iu-PS interface. + +If within a location area there are cells that do not support GPRS services, the SGSN shall group these cells under a 'null RA'. The SGSN will perform the paging procedure described above within both the RA(s) derived from the location information and the 'null RA(s)' of the corresponding location area(s) (see 3GPP TS 24.008 [11]). + +NOTE 2: The eMLPP priority information element relates to relative priorities within the paged MS and not to the priority in the sending of PAGING CS messages by the BSS. + +# --- 6 Location Update for non-GPRS services procedure + +## 6.1 General description + +The location update for non-GPRS services procedure is a general procedure used by MSs in class-A mode of operation and MSs in class-B mode of operation. This procedure is not performed if: + +- the subscriber data indicates that the MS has subscription for packet only; +- the MS indicates SMS only and the HLR indicates "SMS in SGSN Support" and the SGSN supports SMS services. + +NOTE: For the cases specified above, the registration with a VLR is not required and the SGSN does not initiate the location update for non-GPRS services procedure. + +This procedure allows MSs and network to perform: + +- Combined IMSI attach for GPRS and non-GPRS services; +- IMSI attach for non-GPRS services if the MS is already IMSI attached for GPRS services; +- IMSI attach for GPRS services indication to the VLR if the MS is already IMSI attached for non-GPRS services; +- Normal Location Update procedure to the VLR if the MS is IMSI attached for both GPRS and non-GPRS services; +- Reallocation of TMSI to an MS. + +The Location Update for non-GPRS services procedures in the Gs interface is always started as a consequence of a direct action by the MS. The combined routing area update procedure is further specified in 3GPP TS 23.060 [8] and 3GPP TS 24.008 [11]. + +The Location Update for non-GPRS services procedure is used by the SGSN to forward to the VLR those parts of the combined routing area update or IMSI attach procedure which belong to the non-GPRS services. This means that non-GPRS related requests which are included in the combined request, are sent from the SGSN to the VLR. The procedure is also used by the SGSN to indicate to the VLR when an IMSI attach to GPRS services has been performed by an MS that was already IMSI attached to non-GPRS services. The SGSN may also forward a BSSAP+-TMSI-REALLOCATION-COMPLETE message from the MS to the VLR. + +The VLR shall acknowledge the BSSAP+-LOCATION-UPDATE-REQUEST message. When the VLR processes the request it does not perform authentication because it relies on the SGSN's security functions. + +When an MS is IMSI attached for GPRS and non-GPRS services, any implicit detach timer in the VLR shall be stopped. Instead the Paging Proceed Flag in the SGSN is used to determine the likely availability of the MS to the network. Upon reception of the periodic Routing Area Update message the SGSN does not report to the VLR, and the state of the association at the SGSN is not changed. When the MS performs a detach only from the GPRS system, and the VLR's implicit detach timer is not already running, the GPRS detach indication to the VLR shall cause the VLR's implicit detach timer to be restarted from its initial value. + +If the SGSN performs an implicit detach for both GPRS and non-GPRS traffic, then the SGSN shall indicate to the VLR a BSSAP+-IMSI-DETACH-INDICATION message with cause 'Implicit SGSN initiated IMSI detach from GPRS and non-GPRS service', as further described in clause 'Implicit IMSI detach from non-GPRS service procedure' (the implicit IMSI detach message indicates that the MS is unavailable for both GPRS and non-GPRS services). + +The IMSI attach for GPRS services to the VLR, when the MS is already IMSI attached for non-GPRS services, is requested by the MS sending a combined IMSI attach for GPRS and non-GPRS services message to the SGSN, as further specified in 3GPP TS 23.060 [8] and 3GPP TS 24.008 [11]. + +## 6.2 Procedures in the SGSN + +The location update for non-GPRS services is initiated with a combined routing area update procedure or a IMSI/GPRS attach procedure. On receipt of an ATTACH REQUEST message or ROUTING AREA UPDATE REQUEST message from the MS, the SGSN shall handle the GPRS related request as specified in 3GPP TS 24.008 [11]. + +When the SGSN receives the MAP-INSERT-SUBSCRIBER-DATA message containing subscription data from the HLR, the SGSN determines whether it needs to perform location update for non-GPRS services procedure. For the cases identified below, the SGSN sends response message to the MS without starting the location update for non-GPRS services procedure: + +- if the Network Access Mode (NAM) subscription data indicates that the MS has subscription for packet only (see 3GPP TS 29.272 [28]); or +- if the combined attach or routing area update procedure indicates that the MS has requested for GPRS services and "SMS-only service" (see 3GPP TS 24.008 [11]) and the HLR indicates "SMS in SGSN Support" and the SGSN supports SMS services. + +Otherwise, the SGSN shall start the location update for non-GPRS services procedure and wait for the outcome of both location update procedures towards the VLR and the HLR before sending the response message to the MS (see 3GPP TS 24.008 [11]). + +Upon reception of the periodic Routeing Area Update message, if the EMM Combined UE Waiting Flag is 'true', the SGSN shall perform network-initiated GPRS detach procedure with the detach type IE indicating "IMSI detach" as specified in 3GPP TS 24.008 [11]. + +### 6.2.1 Location Update Initiation + +#### 6.2.1.1 General + +If timer T6-1 is not running, the SGSN shall start the location update for non-GPRS service procedure when it receives from the MS: + +- an attach request indicating combined IMSI and GPRS attach; +- an attach request indicating GPRS attach while IMSI attached; +- a combined routing area update request indicating IMSI attach; +- a combined routing area update request indicating that the Location Area has changed; +- a combined routing area update request if the MS Network Capability IE indicates that EMM combined procedures are supported by the MS; +- a combined routing area update request, if the state of the association is Gs-NULL; or +- a combined routing area update request when the SGSN serving the MS has changed. + +If timer T6-1 is not running, the SGSN may start the location update for non-GPRS service procedure when it receives from the MS: + +- a combined routing area update request or a periodic routeing area update, if the 'VLR-Reliable' MM context variable for the MS is set to 'false' (see section 11.3). + +For networks not supporting the feature "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" the number of the VLR is derived from the RAI where the MS is camping. For networks supporting the feature 'Intra Domain Connection of RAN Nodes to Multiple CN Nodes', the VLR number is derived as described in 3GPP TS 23.236 [26]. The SGSN starts Timer T6-1. The BSSAP+-LOCATION-UPDATE-REQUEST message includes the Old location area identifier. If the SGSN received the old location area identification from the MS and the network supports S1 mode, the SGSN includes the old location area identification received from the MS as the Old location area identifier. If the SGSN did not receive the old location area identification from the MS or if the network does not support S1 mode, the SGSN derives the Old location area identifier from the old routing area identification received in the ROUTING AREA UPDATING REQUEST message (see 3GPP TS 24.008 [11]). The SGSN shall also include the New location area identifier where the MS is currently camping. The new LAI is derived from the RAI. + +If the VLR is configured for gateway core network (GWCN), the SGSN shall select a core network operator as specified in 3GPP TS 23.251 [24] and proceed as follows: + +- For supporting UEs, the SGSN includes the PLMN identity of the selected core network operator in the New cell global identity information element. +- For non-supporting UEs, the SGSN includes the selected core network operator in the Selected CN operator information element in the BSSAP+-LOCATION-UPDATE-REQUEST message, and the common PLMN in the New cell global identity information element. + +In networks supporting the feature "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" (3GPP TS 23.236 [26]), if the TMSI based NRI container is not received from the MS, and the SGSN determines that the serving VLR of the MS is changed, the SGSN shall include in the Old location area identifier a specific LAI value which is not broadcasted in the network and not associated with any VLR. + +NOTE 1: The SGSN determines that the serving VLR of the MS is changed when the Gs association changes from one serving VLR to a different one, or based on implementation dependent criteria. + +NOTE 2: When the VLR receives the BSSAP+-LOCATION-UPDATE-REQUEST message with the specific LAI value, the VLR retrieves the MM context of the MS from the HLR. + +In networks supporting the feature "Intra Domain Connection of RAN Nodes to Multiple CN Nodes", the SGSN shall support load re-distribution of MSs to another VLR than the current one as follows: + +When the SGSN receives a periodic routing area update request or a combined routing area update request, the SGSN shall check whether for this MS there is an association to a VLR for which load re-distribution has been initiated in the SGSN by O&M. If yes and + +- if a combined routing area update request is received, the SGSN shall derive the new VLR number as described in 3GPP TS 23.236 [26] and then send the BSSAP+-LOCATION-UPDATE-REQUEST message to the new selected VLR; or +- if a periodic routing area update request is received, dependent on network configuration and operator policy, the SGSN shall take one of the following actions: + - perform a network initiated detach with detach type "IMSI detach" immediately after the completion of the periodic routing area updating procedure; or + - derive the new VLR number as described in 3GPP TS 23.236 [26] and then send the BSSAP+-LOCATION-UPDATE-REQUEST message to the new selected VLR. + +The BSSAP+-LOCATION-UPDATE-REQUEST message includes the type of location update performed by the MS in the GPRS location update type IE. If the MS has performed a combined attach request or a combined routing and location area update request with IMSI attach, the SGSN indicates 'IMSI attach', otherwise the SGSN indicates 'Normal location update'. + +The BSSAP+-LOCATION-UPDATE-REQUEST message shall include the TMSI status if received from the MS. + +The SGSN shall include the TMSI based NRI container in the BSSAP+-LOCATION-UPDATE-REQUEST message if received from the MS. + +If the SGSN supports the "Provision of UE Specific Behaviour Information to Network Entities" (see 3GPP TS 23.195 [23]), or the "Automatic Device Detection" (see 3GPP TS 22.101 [23A]) or the "Trace for Management Based Activation/Deactivation" (see 3GPP TS 32.422 [25]), the BSSAP+-LOCATION-UPDATE-REQUEST message shall include the IMEISV. + +If timer T6-1 is running: + +If the SGSN receives from the MS: + +- an attach request indicating combined IMSI and GPRS attach; +- an attach request indicating GPRS attach while IMSI attached; or +- a combined routing area update request with or without IMSI attach. + +Then: + +- if the new LAI is the same as in the outstanding request, the SGSN shall not process this new request and shall wait for the VLR's response to the ongoing procedure; or +- if the new LAI is different but is in the same VLR as the outstanding request: + - any response from the VLR to the outstanding request is ignored; + - Timer T6-1 shall be stopped and reset; and + - The SGSN shall start the location update for non-GPRS service procedure; or +- if the new LAI is different, and is in a different VLR to the outstanding request: + - any response from the previously addressed VLR to the outstanding request is ignored; + - Timer T6-1 shall be stopped and reset; and + - the SGSN shall start the location update for non-GPRS service procedure. + +When the SGSN receives from the MS a routing area update request and the SGSN serving the MS has changed, the SGSN shall stop and reset timer T6-1. + +#### 6.2.1.2 VLR fails without restart + +If the SGSN supports restoration for CS services via an alternative VLR as defined in 3GPP TS 23.007 [6] and, upon reception of a combined routing area update request or periodic routing area update request from the MS, the SGSN detects that the VLR serving the MS is no longer in service, the SGSN may: + +- if a combined routing area update request is received, select an alternative VLR that is in service for the MS and immediately perform the location update for non-GPRS services procedure towards the selected VLR as described in clause 6; or +- if a periodic routing area update request is received, dependent on network configuration and operator policy, + - perform a network initiated detach with detach type "IMSI detach" immediately after the completion of the periodic routing area update procedure and then select an alternative VLR that is in service for the MS during the subsequent combined routing area update procedure, before performing the location update for non-GPRS services procedure towards the selected VLR as described in clause 6; or + - select an alternative VLR that is in service for the MS and immediately perform the location update for non-GPRS services procedure towards the selected VLR as described in clause 6. + +NOTE: How an SGSN detects a VLR is no longer in service and triggers selection of alternative VLR is implementation dependent. + +### 6.2.2 Location Update Response + +If the SGSN receives a BSSAP+-LOCATION-UPDATE-ACCEPT message from the VLR, the SGSN shall: + +- stop timer T6-1; and +- move the state of the association to Gs-ASSOCIATED; +- set the the MM context variable 'VLR-Reliable' to 'true'; +- set the the MM context variable 'EMM Combined UE Waiting Flag' to 'false'; and +- indicate to the MS the acceptance of the VLR to the Location Update procedure. The message to the MS includes the Routing Area Identity, from which the MS is able to extract the location area identity for which the location update procedure succeeded (see 3GPP TS 24.008 [11]). + +The SGSN shall wait for the outcome of the Location Update for non-GPRS service procedure towards the VLR before sending a response to location update procedure to the MS. Any Reject cause that needs to be reported to the MS is specified in 3GPP TS 24.008 [11]. + +If the VLR included the Mobile Identity IE in the BSSAP+-LOCATION-UPDATE-ACCEPT message, the SGSN shall forward the information received to the MS. If the Mobile Identity IE contains a new TMSI it will cause the MS to perform a TMSI reallocation procedure, while an IMSI causes the MS to deallocate its TMSI. In case a new TMSI was allocated for the MS the SGSN shall send to the VLR the BSSAP+-TMSI-REALLOCATION-COMPLETE message when the SGSN receives Attach Complete or the the Routeing Area Complete message from the MS. + +### 6.2.3 Location Update Failure + +If the SGSN receives a BSSAP+-LOCATION-UPDATE-REJECT message from the VLR, the SGSN shall: + +- stop timer T6-1; +- move the state of the association to Gs-NULL; and +- indicate to the MS the rejection of the VLR of the Location Update procedure as specified in 3GPP TS 24.008 [11]. The Reject cause value sent by the VLR shall be forwarded to the MS. + +### 6.2.4 Abnormal cases + +If timer T6-1 expires, the SGSN shall abort the Location Update for non-GPRS service procedure and indicate this to the MS with the Reject cause value 'MSC temporarily not reachable'. The state of the association to the VLR shall be Gs-NULL. + +If the SGSN receives a BSSAP+-LOCATION-UPDATE-ACCEPT message and timer T6-1 is not running then: + +- if timer T8 is running (see clause 8), the message shall be ignored; +- if timer T9 is running (see clause 9), the message shall be ignored; or +- if timers T8 and T9 are not running: + - if the state of the association to the VLR is GS-ASSOCIATED, the message shall be ignored; or + - if the state of the association to the VLR is different than GS-ASSOCIATED, the message shall be treated as a message incompatible with the protocol state of the SGSN (see clause 16.3). + +## 6.3 Procedures in the VLR + +When a VLR receives a BSSAP+-LOCATION-UPDATE-REQUEST message it checks whether the IMSI is known. If the IMSI is not known the VLR retrieves the MM context of the MS from the HLR. + +In networks supporting the feature 'Intra Domain Connection of RAN Nodes to Multiple CN Nodes' (3GPP TS 23.236 [26]), if the TMSI based NRI container is received in the BSSAP+-LOCATION-UPDATE-REQUEST message, the VLR derives the NRI value. If the NRI value is not allocated by the VLR, the VLR retrieves the MM context of the UE from the HSS. + +When the VLR is configured for gateway core network (GWCN), the VLR shall select the serving core network operator as follows: + +- If the Selected CN operator information element is received in the BSSAP+-LOCATION-UPDATE-REQUEST message, the VLR shall select the serving core network operator as specified in the Selected CN operator information element; +- If the Selected CN operator information element is not received in the BSSAP+-LOCATION-UPDATE-REQUEST message and the PLMN identity included in the New cell global identity information element identifies a core network operator, the VLR shall select the serving core network operator as specified in the New cell global identity information element; +- Otherwise, the VLR selects the serving core network operator based on local policies. + +For a VLR supporting the "Provision of UE Specific Behaviour Information to Network Entities" (see 3GPP TS 23.195 [23]) the following applies: + +- The VLR shall store the IMEISV value received in the BSSAP+-LOCATION-UPDATE-REQUEST message in the MM context for that MS. + +- If the VLR receives a BSSAP+-LOCATION-UPDATE-REQUEST message without IMEISV information element, the MSC/VLR shall request the IMEISV from the MS at the next Iu-CS or A interface connection establishment. + +### 6.3.1 Location Update Response + +If the Location Update is accepted by the VLR and, if necessary by the HLR, the VLR shall: + +- move the association to the Gs-ASSOCIATED state; +- set the restoration indicator 'Confirmed by Radio Contact' to 'true'; +- update the association by storing the SGSN number included in the BSSAP+-LOCATION-UPDATE-REQUEST message; and +- send a BSSAP+-LOCATION-UPDATE-ACCEPT message to the sending SGSN. This message includes the Location Area Identification received in the new Cell Global Identity IE in the previous BSSAP+-LOCATION-UPDATE-REQUEST message. + +### 6.3.2 Location Update Failure + +If the Location Update is rejected by the VLR it shall: + +- Send a BSSAP+-LOCATION-UPDATE-REJECT message to the SGSN with the appropriate reject cause as indicated in 3GPP TS 24.008 [11] and indicate to the SGSN the Location area identifier received in the corresponding BSSAP+-LOCATION-UPDATE-REQUEST message; and +- Move the association from any state to Gs-NULL. + +### 6.3.3 TMSI reallocation procedure + +If the VLR decides to reallocate the TMSI to the MS it shall include the new TMSI in the BSSAP+-LOCATION-UPDATE-ACCEPT message. If the VLR decides to deallocate the TMSI of the MS it shall include the IMSI of the MS in the BSSAP+-LOCATION-UPDATE-ACCEPT message. After sending the BSSAP+-LOCATION-UPDATE-ACCEPT message with a new TMSI the VLR starts timer T6-2. + +NOTE: In the BSSAP+-LOCATION-UPDATE-REQUEST the SGSN may indicate, that there is no valid TMSI available in the MS. This information may be used by the VLR to decide whether to reallocate a new TMSI to the MS. + +Upon receipt of the BSSAP+-TMSI-REALLOCATION-COMPLETE message, the VLR stops the timer T6-2 and considers the new TMSI as valid. + +If an IMSI was sent to the MS, the VLR considers the old TMSI if available, as deleted. + +If no BSSAP+-TMSI-REALLOCATION-COMPLETE message is received by the VLR before the timer T6-2 expires, the VLR aborts the TMSI reallocation procedure. The VLR shall consider old TMSI if available, occupied until the new TMSI is used in a subsequent A/Iu message, or for an implementation dependent time. The VLR may still perform the TMSI reallocation procedure via the A or Iu-CS interface. The outcome of the TMSI reallocation procedure does not change the state of the association. The VLR uses the IMSI or the new TMSI or, if available, the old TMSI for paging. + +### 6.3.4 Abnormal cases + +The following abnormal cases can be identified: + +- i) MM signalling via the A or Iu-CS interface + +If the VLR receives a Location Update request or an IMSI detach indication from the MS by the A or Iu-CS interface when the state of the association in the VLR is not Gs-NULL, the VLR shall move the state of the association to Gs-NULL. + +- ii) Additional Location Update Request + +If the state of the association in the VLR is in the LA-UPDATE PRESENT state and a BSSAP+-LOCATION-UPDATE-REQUEST message is received, then: + +- If the message is from the same SGSN and indicates the same New Location Area as the outstanding location update request, then this additional BSSAP+-LOCATION-UPDATE-REQUEST message shall be ignored; +- If the message is from the same SGSN but indicates a different New Location Area to the outstanding location update request, then this additional BSSAP+-LOCATION-UPDATE-REQUEST message shall be treated and the VLR shall not send any response to the previous BSSAP+-LOCATION-UPDATE-REQUEST message; or +- If the message is from a different SGSN (indicating either the same or different New Location Area) to the outstanding location update request, then this additional BSSAP+-LOCATION-UPDATE-REQUEST message shall be treated and the VLR shall not send any response to the previous BSSAP+-LOCATION-UPDATE-REQUEST message. + +#### iii) Detach signalling from SGSN + +If the state of the association in the VLR is in the LA-UPDATE PRESENT state and either a BSSAP+-GPRS-DETACH-INDICATION or a BSSAP+-IMSI-DETACH-INDICATION message is received, then, the Location Update for non-GPRS services procedure shall be abandoned in the VLR (neither a BSSAP+LOCATION-UPDATE-ACCEPT nor a BSSAP+LOCATION-UPDATE-REJECT messages is sent) and the further actions described in clauses 8 or 9 or 10 are followed. + +#### iv) Signalling via SGs interface + +If the VLR receives for a UE a SGsAP-LOCATION-UPDATE-REQUEST message (as defined in 3GPP TS 29.118 [27]) from an MME when the state of the association for this UE in the VLR is not Gs-NULL, the VLR shall move the state of the association to Gs-NULL. + +#### v) New Location Update Request during TMSI reallocation procedure + +If the VLR receives a BSSAP+-LOCATION-UPDATE-REQUEST message while T6-2 is running, the VLR shall stop timer T6-2, abort the TMSI reallocation procedure and proceed with the new location update for non-GPRS services procedure. If the VLR needs to page the MS during the new location update for non-GPRS services procedure, the VLR uses the IMSI or the new TMSI from the aborted TMSI reallocation procedure or, if available, the old TMSI for paging. + +#### vi) Reset signalling from SGSN + +If the state of the association in the VLR is in the LA-UPDATE PRESENT state and a BSSAP+-RESET-INDICATION message is received from the SGSN, then, the Location Update for non-GPRS services procedure shall be abandoned in the VLR (neither a BSSAP+LOCATION-UPDATE-ACCEPT nor a BSSAP+LOCATION-UPDATE-REJECT messages is sent) and the further actions described in clause 12 are followed. + +# --- 7 Non-GPRS alert procedure + +## 7.1 General description + +This procedure is used by the VLR to request from an SGSN an indication when activity (either signalling or data transmission) from an MS is detected. This procedure can be invoked at any time by the VLR. The BSSAP+-ALERT-REQUEST message shall be acknowledged by the SGSN. + +## 7.2 Procedures in the VLR + +### 7.2.1 Alert Initiation + +The VLR may start the Non-GPRS alert procedure at any time. When the VLR wants to request to an SGSN that further activity from an MS shall be reported by the SGSN, the VLR shall send an BSSAP+-ALERT-REQUEST message to that SGSN. The VLR starts timer T7 when the BSSAP+-ALERT-REQUEST message is sent. + +### 7.2.2 Alert Response + +When a BSSAP+-ALERT-ACK message is received, the VLR shall stop the timer T7. The state of the association is not changed. + +### 7.2.3 Alert failure + +If a BSSAP+-ALERT-REJECT message is received, the VLR shall stop the timer T7, move the state of the association to Gs-NULL and within this state the association is marked with the contents of the Gs Cause IE. + +### 7.2.4 Alert Indication + +The VLR shall not change the state of the association upon reception of an BSSAP+-MS-ACTIVITY-INDICATION message. + +### 7.2.5 Abnormal cases + +If no BSSAP+-ALERT-ACK message is received before the timer T7 expires, the VLR shall retransmit the BSSAP+-ALERT-REQUEST message a maximum of N7 times. If no BSSAP+-ALERT-ACK message is received after that, a report shall be made to the O&M system. The state of the association is not changed. + +## 7.3 Procedures in the SGSN + +### 7.3.1 Alert response + +The SGSN may receive a BSSAP+-ALERT-REQUEST message at any state of the association. Upon receipt of an BSSAP+-ALERT-REQUEST message from the VLR and if the IMSI is known in the SGSN, the SGSN shall reply with a BSSAP+-ALERT-ACK message and set the NGAF. + +### 7.3.2 Alert failure + +If a BSSAP+-ALERT-REQUEST message is received for an IMSI that is unknown at the SGSN, the SGSN shall return a BSSAP+-ALERT-REJECT message to the VLR indicating the Gs Cause IE value 'IMSI unknown'. + +### 7.3.3 Alert indication + +The SGSN shall report to the VLR upon detection of any activity (either signalling or data) from the MS if the NGAF is set. If the SGSN detects GPRS signalling that leads to a procedure towards the VLR, the SGSN shall follow this procedure and reset the NGAF. If the SGSN detects activity that does not lead to any procedure towards the VLR, the SGSN shall send an BSSAP+-MS-ACTIVITY-INDICATION message towards the VLR and reset the NGAF. + +# --- 8 Explicit IMSI detach from GPRS services procedure + +## 8.1 General description + +This procedure is used by the SGSN to indicate to the VLR that the MS has been IMSI detached from GPRS service and therefore the association between the SGSN and the VLR has to be deactivated. This procedure only applies to MSs that are not in the Gs-NULL state at the SGSN. The procedures specified in this clause apply to GPRS detach indication initiated by the MS or by the network as specified in 3GPP TS 23.060 [8]. + +The procedure is also used by the SGSN to indicate to the VLR when a combined Routing and Location Area Update procedure has been rejected by the SGSN. + +The procedure is also used by the SGSN to indicate to the VLR when a periodic Routing Area Update procedure has been rejected by the SGSN for an MS for which a Gs association exists. + +The Explicit IMSI detach from GPRS services procedure aborts any other ongoing procedure related to this MS on the Gs interface in the SGSN and in the VLR. + +The VLR and the MS should be synchronised as to whether the PBCCH or the BCCH is used, for any of the subsequent paging. In order to achieve this, the SGSN shall attempt to inform the VLR about the detach event by using a retry scheme if the initial delivery of the BSSAP+-GPRS-DETACH-INDICATION message fails. + +## 8.2 Procedures in the SGSN + +### 8.2.1 Explicit GPRS detach initiation + +The SGSN shall send a BSSAP+-GPRS-DETACH-INDICATION message to a VLR if: + +- The SGSN receives a GPRS only detach from the MS; +- The SGSN performs network-initiated GPRS detach procedure; +- The combined Routing and Location Area Update procedure is rejected at the SGSN; or +- The periodic Routing Area Update procedure is rejected at the SGSN for an MS for which a Gs association exists. + +If the SGSN receives a Detach Request from an MS and the state of the association to a VLR for that MS is not Gs-NULL, the SGSN shall check the detach type indicated in the message. If the MS is indicating GPRS detach the SGSN shall send a BSSAP+-GPRS-DETACH-INDICATION message to the VLR indicating 'MS initiated IMSI detach from GPRS service'. + +If the SGSN decides to perform a network-initiated GPRS detach and the state of the association to a VLR for that MS is not Gs-NULL, the SGSN shall send a BSSAP+-GPRS-DETACH-INDICATION message to the VLR indicating 'Network initiated IMSI detach from GPRS service'. + +If the combined Routing and Location Area Update procedure or periodic Routing Area Update procedure is rejected at the SGSN for an MS with an association state different from Gs-NULL, the SGSN shall send a BSSAP+-GPRS-DETACH-INDICATION to the VLR indicating 'GPRS services not allowed'. The SGSN then sends, for example, a Routing Area Update Reject message as specified in 3GPP TS 24.008 [11]. + +After the sending of the BSSAP+-GPRS-DETACH-INDICATION message, the SGSN shall move the state of the association to Gs-NULL. The SGSN shall start timer T8 upon transmission of the BSSAP+-GPRS-DETACH-INDICATION message and if timer T6-1 is running, timer T6-1 shall be stopped and reset. + +### 8.2.2 Explicit GPRS detach Response + +If the SGSN receives a BSSAP+-GPRS-DETACH-ACK message from the VLR, the SGSN shall stop timer T8. The SGSN shall not wait for the reception of the BSSAP+-GPRS-DETACH-ACK message before sending (if needed) the confirmation of the detach to the MS. + +### 8.2.3 Abnormal cases + +If no BSSAP+-GPRS-DETACH-ACK message is received by the SGSN to a previous BSSAP+-GPRS-DETACH-INDICATION message before timer T8 expires, the SGSN shall repeat the BSSAP+-GPRS-DETACH-INDICATION message a maximum of N8 times. If no BSSAP+-GPRS-DETACH-ACK message is received after that, a report shall be made to the O&M system. The state of the association during the acknowledgement procedure remains Gs-NULL. + +## 8.3 Procedures in the VLR + +When a VLR receives a BSSAP+-GPRS-DETACH-INDICATION message, the VLR shall send a BSSAP+-GPRS-DETACH-ACK message to the sending SGSN. The state of the association for the MS shall be moved from any state to Gs-NULL. The VLR marks the association as 'IMSI detached for GPRS services' with the reason indicated in the IMSI detach from GPRS service type IE. + +If the VLR's implicit detach timer is not running then, the VLR shall set and restart the implicit detach timer upon reception of a BSSAP+-GPRS-DETACH-INDICATION message. If the VLR's implicit detach timer is running (ie the state of the association was already Gs-NULL) then, the reception of a BSSAP+-GPRS-DETACH-INDICATION message shall not affect the VLR's implicit detach timer. + +# 9 Explicit IMSI detach from non-GPRS services procedure + +## 9.1 General description + +This procedure is used by the SGSN to indicate to the VLR that the MS has performed IMSI detach from non-GPRS services and therefore the association between the SGSN and the VLR has to be deactivated. This procedure only applies to MSs that are not in the Gs-NULL state at the SGSN. The procedures specified in this clause only apply to IMSI detach or combined IMSI and GPRS detach requests. + +The explicit IMSI detach from non-GPRS services procedure aborts any other ongoing procedure related to this MS on the Gs interface in the SGSN and in the VLR. + +The VLR and the MS should be synchronised as to whether the PBCCH or the BCCH is used, for any of the subsequent paging. In order to achieve this, the SGSN shall attempt to inform the VLR about the detach event by using a retry scheme if the initial delivery of the BSSAP+-IMSI-DETACH-INDICATION message fails. + +## 9.2 Procedures in the SGSN + +### 9.2.1 Explicit IMSI detach initiation + +When an SGSN receives a Detach Request from an MS which is not in the Gs-NULL state, it shall check the detach type indicated. If the MS is indicating IMSI detach or combined IMSI and GPRS detach the SGSN shall send an BSSAP+-IMSI-DETACH-INDICATION message to the VLR indicating 'Explicit MS initiated IMSI detach from non-GPRS service' or 'Combined explicit MS initiated IMSI detach from GPRS and non-GPRS services'. + +After the sending of the BSSAP+-IMSI-DETACH-INDICATION message to the VLR, the SGSN shall move the state of the association to Gs-NULL. The SGSN shall start timer T9 upon transmission of the BSSAP+-IMSI-DETACH-INDICATION message and if timer T6-1 is running, timer T6-1 shall be stopped and reset.. + +### 9.2.2 Explicit IMSI detach Response + +If the SGSN receives a BSSAP+-IMSI-DETACH-ACK message from the VLR, the SGSN shall stop timer T9. If the detach type received from the MS indicated IMSI only detach or combined IMSI and GPRS detach not due to switch off, the SGSN shall wait for the reception of the BSSAP+-IMSI-DETACH-ACK message before sending the confirmation of the detach to the MS. + +### 9.2.3 Abnormal cases + +#### i) with switch off + +If the SGSN sent a BSSAP+-IMSI-DETACH-INDICATION message for a combined IMSI and GPRS detach due to switch off and timer T9 expires, the SGSN shall repeat the BSSAP+-IMSI-DETACH-INDICATION message a maximum of N9 times. + +#### ii) with no switch off + +If the SGSN sent a BSSAP+-IMSI-DETACH-INDICATION message for a IMSI only detach or a combined IMSI and GPRS detach not due to switch off and timer T9 expires, the SGSN shall repeat the BSSAP+-IMSI-DETACH-INDICATION message a maximum of N9 times. If no BSSAP+-IMSI-DETACH-ACK is received after that the SGSN shall send the confirmation of the detach to the MS. + +## 9.3 Procedures in the VLR + +When a VLR receives an BSSAP+-IMSI-DETACH-INDICATION message, the VLR shall send an BSSAP+-IMSI-DETACH-ACK message to the sending SGSN. The state of the association for the MS shall be moved from any state to Gs-NULL. If the BSSAP+-IMSI-DETACH-INDICATION message indicated 'Explicit MS initiated IMSI detach from non-GPRS service', the VLR marks the association as 'IMSI detached for non-GPRS services'. If the BSSAP+-IMSI-DETACH-INDICATION message indicated 'Combined explicit MS initiated IMSI detach from GPRS and non-GPRS + +services', the VLR marks the association as 'IMSI detached for GPRS and non-GPRS services'. The VLR shall mark the MS as detached. + +--- + +# 10 Implicit IMSI detach from non-GPRS services procedure + +## 10.1 General description + +This procedure is used by the SGSN to indicate when, based on the criteria for implicit detach as specified in 3GPP TS 23.060 [8], the SGSN has decided to delete the GMM context of an MS or mark its GMM context as detached. This procedure only applies to MSs that are not in the Gs-NULL state at the SGSN. + +The implicit IMSI detach from non-GPRS services procedure aborts any other ongoing procedure related to this MS on the Gs interface in the SGSN and in the VLR. + +The VLR and the MS should be synchronised as to whether the PBCCH or the BCCH is used, for any of the subsequent paging. In order to achieve this, the SGSN shall attempt to inform the VLR about the detach event by using a retry scheme if the initial delivery of the BSSAP+-IMSI-DETACH-INDICATION message fails. + +## 10.2 Procedures in the SGSN + +When the implicit IMSI detach from non-GPRS services procedure is started for an MS, the SGSN shall send a BSSAP+-IMSI-DETACH-INDICATION message to the VLR indicating 'Implicit SGSN initiated IMSI detach from GPRS and non-GPRS service'. + +After the sending of the BSSAP+-IMSI-DETACH-INDICATION message, the SGSN shall move the state of the association to Gs-NULL. The SGSN shall start timer T10 upon transmission of the BSSAP+-IMSI-DETACH-INDICATION message. + +If the SGSN receives a BSSAP+-IMSI-DETACH-ACK message from the VLR, the SGSN shall stop timer T10. + +If no BSSAP+-IMSI-DETACH-ACK message is received by the SGSN to a previous BSSAP+-IMSI-DETACH-INDICATION message before timer T10 expires, the SGSN shall repeat the BSSAP+-IMSI-DETACH-INDICATION message a maximum of N10 times. The state of the association during the acknowledgement procedure remains Gs-NULL. + +## 10.3 Procedures in the VLR + +When a VLR receives the BSSAP+-IMSI-DETACH-INDICATION message, the VLR shall send an BSSAP+-IMSI-DETACH-ACK message to the sending SGSN. In addition, if the state of the Gs association is not Gs-NULL, the VLR proceeds as follows: + +- The VLR shall move the state of the association for the MS to Gs-NULL. If the VLR does not have a signalling connection for the MS, the VLR shall mark the MS as detached. Additionally, the VLR marks the association as 'IMSI implicitly detached for GPRS and non-GPRS services'. + +# --- 11 VLR failure procedure + +## 11.1 General description + +This procedure is used by the VLR to inform the associated SGSNs about the recovery from an internal failure that has affected the association with the SGSNs when the VLR fails with restart. + +The VLR recovery procedure shall be handled in such a way that the signalling load on the VLR and SGSN does not create any overload problem. + +## 11.2 Procedures in the VLR + +### 11.2.1 VLR Reset Initiation + +In the event of a failure at the VLR which has resulted in the loss of SGSN association information on some MSs, the VLR shall move from any state to the Gs-NULL state for these MSs. The VLR shall also set the 'Confirmed by Radio Contact' restoration indicator to 'false' (see 3GPP TS 23.007 [6]) for affected MSs. The VLR shall not send any BSSAP+- MS-INFORMATION-REQUEST or BSSAP+-MM-INFORMATION-REQUEST messages to MSs with the SGSN association in the Gs-NULL state. + +When the VLR restarts a BSSAP+-RESET-INDICATION message shall be sent to all the SGSNs connected to the VLR by the Gs interface. This message indicates to the SGSN that for the MSs with an association to that VLR, the association is no longer reliable. The VLR shall also start timer T11. + +### 11.2.2 VLR Reset Response + +Upon receipt of a BSSAP+-RESET-ACK message, the VLR shall stop the timer T11. + +### 11.2.3 Abnormal cases + +If the VLR does not receive a BSSAP+-RESET-ACK message from that SGSN before the T11 timer expires, the VLR shall retransmit the BSSAP+-RESET-INDICATION message. The retransmission is repeated a maximum of N11 times. If no BSSAP+-RESET-ACK is received after that a report shall be made to the O&M system. + +## 11.3 Procedures in the SGSN + +### 11.3.1 VLR reset indication + +Upon receipt of a BSSAP+-RESET-INDICATION message from the VLR, the SGSN is informed that all the associations with that VLR for all the MSs registered in the SGSN are no longer reliable because the VLR may have lost information about the state of the MSs and during the failure the VLR may have missed signalling messages. The SGSN shall set the 'VLR-Reliable' MM context variable to 'false'. The detach procedures for deleting the association are still applicable (clauses 8, 9 and 10). + +The SGSN sends a BSSAP+-RESET-ACK message to the VLR. + +If the 'VLR-Reliable' MM context variable is set to 'false', upon reception of a combined routing area update request or a periodic routing area update request from the MS that is attached for non-GPRS service, the SGSN may: + +- if a combined routing area update request is received, immediately perform the location update for non-GPRS services procedure towards the VLR as described in clause 6; or +- if a periodic routing area update request is received, dependent on network configuration and operator policy, + - perform a network initiated detach with detach type "IMSI detach" immediately after the completion of the periodic routing area update procedure; or + - perform immediately the location update for non-GPRS services procedure towards the VLR as described in clause 6. + +### 11.3.2 Void + +# --- 12 SGSN failure procedure + +## 12.1 General description + +This procedure is used by the SGSN to inform the associated VLRs about the recovery from an internal failure that has affected the association with the VLRs. + +The SGSN recovery procedure shall be handled in such a way that the signalling load on the VLR and SGSN does not create any overload problem. + +## 12.2 Procedures in the SGSN + +### 12.2.1 SGSN Reset Initiation + +In the event of a failure at the SGSN which has resulted in the loss of VLR association information on some MSs, the SGSN shall move from any state to the Gs-NULL state for these affected MSs. The SGSN shall also set the 'SGSN-Reset' MM context variable to 'true' and start the timer T12-1. When the timer T12-1 expires the 'SGSN-Reset' MM context variable is set to 'false'. The value of the timer T12-1 shall be longer than the periodic routing area update timer at the SGSN. + +A BSSAP+-RESET-INDICATION message may be sent to all the VLRs connected to the SGSN by Gs interfaces. The BSSAP+-RESET-INDICATION message indicates to the VLR that all the associations with that particular SGSN for all the MSs registered in the VLR are no longer reliable. The normal procedures for updating the association are still applicable (clauses 6, 8, 9 and 10). The SGSN shall also start timer T12-2. + +If no BSSAP+-RESET-INDICATION is sent, the SGSN shall move from any state to the Gs-NULL state only the associations of the MSs affected by the loss of VLR association information. + +NOTE: The option to not send any BSSAP+-RESET-INDICATION message to all the VLRs connected to the SGSN by Gs interfaces reduces subsequent paging signalling initiated by VLRs by avoiding a complete search of the MS on the entire VLR area. + +### 12.2.2 SGSN Reset Response + +Upon receipt of a BSSAP+-RESET-ACK message, the SGSN shall stop the timer T12-2. + +### 12.2.3 Abnormal cases + +If the SGSN does not receive a BSSAP+-RESET-ACK message from that VLR before the T12-2 timer expires, the SGSN shall retransmit the BSSAP+-RESET-INDICATION message. The retransmission is repeated a maximum of N12 times. If no BSSAP+-RESET-ACK is received after a report shall be to made the O&M system. + +## 12.3 Procedures in the VLR + +Upon receipt of a BSSAP+-RESET-INDICATION message from the SGSN, the VLR is informed that all the associations with that SGSN for all the MSs registered in the SGSN are no longer reliable because the SGSN may have lost information about the state of the MSs for that VLR and during the failure the SGSN may have missed signalling messages. The VLR shall either: + +- set the 'Confirmed by Radio Contact' restoration indicator to 'false' in all the associations containing the restarted SGSN and set the state of all the Gs associations containing the restarted SGSN to the Gs-NULL state; or +- keep the 'Confirmed by Radio Contact' restoration indication and the state of all the Gs associations containing the restarted SGSN unchanged. + +NOTE: The option to not set the 'Confirmed by Radio Contact' restoration indicator to 'false' in all the associations containing the restarted SGSN reduces subsequent paging signalling the VLR can initiate by avoiding a complete search of the MS on the entire VLR area. + +The VLR shall then send a BSSAP+-RESET-ACK message to the SGSN. + +If the 'Confirmed by Radio Contact' restoration indicator is 'false' the VLR may send paging messages on the Gs, A and Iu-CS interfaces. + +# --- 13 HLR failure + +This clause describes the SGSN behaviour towards the VLR as a consequence of an HLR reset. + +## 13.1 General description + +In the case of an HLR failure, the HLR informs the associated SGSNs about the recovery from an internal failure that has affected the association with the SGSNs according to the HLR reset procedure specified in 3GPP TS 29.002 [17]. + +This information is used in the SGSN to trigger the VLR to perform a location update towards the HLR in order to restore the HLR subscriber data. + +## 13.2 Procedures in the SGSN + +Upon receipt of a HLR reset indication from the HLR, the SGSN shall set the NGAF for all registered MSs in the SGSN for which a valid MSC/VLR-association exists. + +Upon detection of any activity (either signalling or data) from the MS, the SGSN shall report to the VLR if the NGAF is set for this MS. If the SGSN detects GPRS signalling that leads to a procedure towards the VLR, the SGSN shall follow this procedure and reset the NGAF. If the SGSN detects activity that does not lead to any procedure towards the VLR, the SGSN shall send an BSSAP+-MS-ACTIVITY-INDICATION message towards the VLR and reset the NGAF. The activity indication may be delayed by the SGSN for a maximum operator-configuration depending time period to avoid high signalling load. + +# --- 14 MS Information procedure + +## 14.1 General description + +The MS Information procedure is used by the VLR to request specific parameters about the MS. If the target MS for an MS Information procedure or a Provide Subscriber Info procedure (see 3GPP TS 23.018 [6a] and 3GPP TS 29.002 [17]) is GPRS attached (i.e. the state of the association to Gs-ASSOCIATED) the VLR may decide to perform the procedure via GPRS. The outcome of the MS Information procedure does not change the state of the association at the VLR or SGSN. + +## 14.2 Procedures in the VLR + +If the target MS for the MS information procedure is GPRS attached and the state of the association for the MS Gs-ASSOCIATED, the VLR may initiate the MS information procedure by transferring a BSSAP+-MS-INFORMATION-REQUEST message to the SGSN. If the state of the association is LA-UPDATE PRESENT, the VLR shall wait until this state is exited. The VLR starts the timer T14. The BSSAP+-MS-INFORMATION-REQUEST message specifies the requested information parameters in the Information requested information element. + +Upon receipt of a BSSAP+-MS-INFORMATION-RESPONSE the VLR shall stop timer T14. If no BSSAP+-MS-INFORMATION-RESPONSE for that MS is received before the expiry of timer T14 the VLR shall stop the Gs interface MS information procedure. The VLR may perform other actions to obtain the information about the MS (e.g. retry, or send a DTAP IDENTITY REQUEST message on the A interface). + +## 14.3 Procedures in the SGSN + +The SGSN shall examine the type of information that is requested and if it is stored in its database shall use this information in its response to the VLR. The BSSAP+-MS-INFORMATION-RESPONSE message contains the information parameters as requested by the VLR. In A/Gb mode, the Mobile location information indicates a request for Cell Global Identity and Location information age. In Iu mode, the Mobile location information indicates a request for Service Area Identification and Location information age. In this case, the SGSN shall use the Location Report Control procedure (see 3GPP TS 25.413 [22]) in order to retrieve the SA. + +If the SGSN receives an Information requested information element containing a 'not supported' value, then the value part of the Mobile station state information element in the BSSAP+-MS-INFORMATION-RESPONSE message shall be set to 'Information requested not supported'. + +If the information is not locally available and it is a request for mobile identity information, the SGSN forwards the IDENTITY REQUEST message to the MS indicated in the message unless the GPRS activities of the MS are suspended. Upon receipt of the IDENTITY RESPONSE message from the MS, the SGSN shall send a BSSAP+-MS-INFORMATION-RESPONSE message. The BSSAP+-MS-INFORMATION-RESPONSE message contains the information parameters as requested by the VLR. If the GPRS activities of the MS are suspended the SGSN shall return a BSSAP+-MS-INFORMATION-RESPONSE message indicating in the Mobile station state IE 'SUSPENDED'. If the requested information is not available or obtainable at the SGSN, the SGSN shall return a BSSAP+-MS-INFORMATION-RESPONSE message to the VLR without the requested information. The SGSN should include the Mobile station state IE in all BSSAP+-MS-INFORMATION-RESPONSE messages. + +If the IMSI is not known at the SGSN, the SGSN shall return a BSSAP+-MS-INFORMATION-RESPONSE message indicating in the Mobile station state IE 'IMSI unknown'. + +# --- 15 MM information procedure + +## 15.1 General description + +The MM information procedure may be performed by the VLR via GPRS if the target MS for the MM information procedure is IMSI attached to both GPRS and non-GPRS services (i.e. the state of the association is Gs-ASSOCIATED). The outcome of the MM Information procedure does not change the state of the association at the VLR or SGSN. + +## 15.2 Procedures in the VLR + +If the target MS for the MM information procedure is GPRS attached class A or B MS, the state of the association is Gs-ASSOCIATED, the VLR may initiate the MM information procedure by transferring a BSSAP+-MM-INFORMATION-REQUEST message to the SGSN. + +## 15.3 Procedures in the SGSN + +If the state of the association at the SGSN is not Gs-NULL, and the network only spans one time zone, the SGSN shall keep the information elements in the MM information unchanged. + +NOTE: For the determination of the number of time zones, both CS and PS domain are taken into account. + +If the network spans more than one time zone, the SGSN shall check and update the contents of the MM information element as follows: + +- if Network Daylight Saving Time has been included in the MM information, then the SGSN shall discard the Network Daylight Saving Time; +- if Local Time Zone has been included in the MM information, then the SGSN shall replace the Local Time Zone with the Local Time Zone applicable for this MS. In addition, if the local time zone in the SGSN has been adjusted for daylight saving time, the SGSN shall indicate this by including the value used for adjustment in Network Daylight Saving Time IE in the MM information; +- if Universal time and local time zone has been included in the MM information, then the SGSN shall replace it with the Universal time and local time zone applicable for this MS. In addition, if the local time zone in the SGSN has been adjusted for daylight saving time, the SGSN shall indicate this by including the value used for adjustment in Network Daylight Saving Time IE in the MM information; and +- other information elements in the MM information are kept unchanged. + +The SGSN shall then send the resultant MM-INFORMATION message to the MS indicated. + +# --- 16 Error Handling and Future Compatibility + +## 16.1 General + +This clause specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocol. + +In this clause the following terminology is used: + +- an IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved", or if its value part violates coding rules. However, it is not a syntactical error that an IE specifies in its Length Indicator a greater length than defined in the relevant clause; and + +- a message is defined to have semantically incorrect contents if it contains information which, possibly dependant on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part of 3GPP TS 29.018. + +When a receiving entity detects the need to send a BSSAP+-MOBILE-STATUS message (see errors detailed below), the entity shall copy the IMSI IE value (if included) of the incorrect message to the IMSI IE on the BSSAP+-MOBILE-STATUS message. The message in error is also included in the BSSAP+-MOBILE-STATUS message. Both the receiving and the sending entity shall abandon the procedure related to the incorrect message and return to the state from where the procedure related to the incorrect message was started. + +A BSSAP+-MOBILE-STATUS message shall not be sent in response to a received BSSAP+-MOBILE-STATUS message. + +Both the receiving and the sending entity shall inform the O&M entity upon sending or receiving a BSSAP+-MOBILE-STATUS message. + +The next clauses in this clause shall be applied in order of precedence. + +## 16.2 Message too short + +When a message is received that is too short to contain a complete message type information element, that message shall be ignored. + +## 16.3 Unknown or unforeseen message type + +If a message is received with a message type not defined or not implemented by the receiver it shall ignore the message. A BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "message unknown" and the Erroneous message IE containing the received message shall be returned. + +If a message is received that is not compatible with the protocol state, a BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "message not compatible with the protocol state" and the erroneous message shall be returned. + +If a message is received that is not defined to be received by that entity (i.e. the message is sent in the wrong direction) it shall be treated as unknown message and the message shall be ignored. A BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "message unknown" and the Erroneous message IE containing the received message shall be returned. + +## 16.4 Missing mandatory information element + +When on receipt of a message, and a "missing mandatory IE" error is diagnosed, the receiver shall ignore the message and return a BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "missing mandatory information element" and shall return the Erroneous message information element containing the received message. + +## 16.5 IEs unknown or unforeseen in the message + +All IEs unknown or unforeseen in a message shall be ignored. + +## 16.6 Out of sequence IEs + +All IEs that are out of sequence shall be ignored. + +## 16.7 Repeated IEs + +If an information element with format T, TV, or TLV is repeated in a message in which repetition of the information element is not specified, only the contents of the information element appearing first shall be handled and all subsequent repetitions of the information element shall be ignored. When repetition of information elements is specified, only the contents of specified repeated information elements shall be handled. If the limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored. + +## 16.8 Syntactically incorrect mandatory IE. + +On receipt of a message which contains a syntactically incorrect mandatory IE, the receiver shall ignore the message and return a BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "invalid mandatory information" and shall return the Erroneous message information element containing the received message. + +## 16.9 Syntactically incorrect optional IEs + +All optional IEs that are syntactically incorrect in a message shall be treated as not present in the message. + +## 16.10 Conditional IE errors + +When a VLR or SGSN receives a message and diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives a message containing at least one syntactically incorrect conditional IE which is required to be present in the message, a VLR or SGSN shall ignore the message and return a BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "conditional IE error" and shall return the Erroneous message information element containing the received message. + +When a VLR or SGSN receives a message containing a syntactically incorrect conditional IE which is not required to be present in the message, nor required to be absent in the message, then a VLR or SGSN shall ignore that IE. + +## 16.11 IEs with semantically incorrect contents + +When an IE with semantically incorrect contents is received, the foreseen reactions of the procedural part of 3GPP TS 29.018 are performed. + +If however no such reactions are specified, the receiving entity shall ignore that IE and treat the rest of the message. If, because this IE was ignored, the rest of the message can no longer be handled then the receiving entity shall return a BSSAP+-MOBILE-STATUS message with the Gs Cause Value set to "semantically incorrect message" and shall return the Erroneous message information element containing the received message. + +# 17 Message functional definitions and contents + +This clause defines the structure of the messages that are sent between the SGSN and the VLR. + +## 17.1 Message Contents + +### 17.1.1 BSSAP+-ALERT-ACK message + +This message is sent by the SGSN to the VLR to acknowledge a previous BSSAP+-ALERT-REQUEST message. + +**Table 17.1.1/3GPP TS 29.018: BSSAP+-ALERT-ACK message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | + +### 17.1.2 BSSAP+-ALERT-REJECT message + +This message is sent from the SGSN to the VLR to indicate that the SGSN could not identify the IMSI indicated in the BSSAP+-ALERT-Request message. + +**Table 17.1.2/3GPP TS 29.018: BSSAP+-ALERT-REJECT message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Gs Cause | Gs Cause
18.4.7 | M | TLV | 3 | + +#### 17.1.2.1 Gs Cause + +The value part which is typically sent for this information element in this message is 'IMSI unknown'. + +### 17.1.3 BSSAP+-ALERT-REQUEST message + +This message is sent by the VLR to the SGSN to request an indication when next activity from the MS is detected. + +**Table 17.1.3/3GPP TS 29.018: BSSAP+-ALERT-REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | + +### 17.1.4 BSSAP+-DOWNLINK-TUNNEL-REQUEST message + +This message is sent from the non-GSM MSC/VLR to the SGSN to convey a tunneling payload to the MS identified by the specified IMSI. + +**Table 17.1.4/3GPP TS 29.018: BSSAP+-DOWNLINK-TUNNEL-REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|------------------------------------------|----------------------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| VLR number | VLR number
18.4.26 | M | TLV | 5-11 | +| Downlink Tunnel Payload Control and Info | Downlink Tunnel Payload Control and Info
18.4.3 | M | TLV | 3-223 | + +### 17.1.5 BSSAP+-GPRS-DETACH-ACK message + +This message is sent by the VLR to the SGSN to acknowledge a previous BSSAP+-GPRS-DETACH-Indication message. + +**Table 17.1.5/3GPP TS 29.018: BSSAP+-GPRS-DETACH-ACK message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | + +### 17.1.6 BSSAP+-GPRS-DETACH-INDICATION message + +This message is sent by the SGSN to the VLR to indicate a GPRS detach performed from the MS or the SGSN. The type of detach is indicated in the IMSI detach from GPRS service type IE. + +**Table 17.1.6/3GPP TS 29.018: BSSAP+-GPRS-DETACH-INDICATION message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|------------------------------------|-----------------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| SGSN number | SGSN number
18.4.22 | M | TLV | 5-11 | +| IMSI detach from GPRS service type | IMSI detach from GPRS service type
18.4.11 | M | TLV | 3 | +| Cell global identity | Cell global identity
18.4.1 | O | TLV | 10 | +| Service area identification | Service area identification
18.4.21b | O | TLV | 9 | + +#### 17.1.6.1 Cell global identity (A/Gb mode only) + +In A/Gb mode, the SGSN shall include the Cell global identity where the mobile was in the last radio contact. + +#### 17.1.6.2 Service area identification (Iu mode only) + +In Iu mode, the SGSN should include the Service area identification where the mobile was in the last radio contact. + +### 17.1.7 BSSAP+-IMSI-DETACH-ACK message + +This message is sent by the VLR to the SGSN to acknowledge a previous BSSAP+-IMSI-DETACH-Indication message. + +**Table 17.1.7/3GPP TS 29.018: BSSAP+-IMSI-DETACH-ACK message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | + +### 17.1.8 BSSAP+-IMSI-DETACH-INDICATION message + +This message is sent by the SGSN to the VLR to indicate an IMSI detach performed from the MS. The type of detach is indicated in the IMSI detach from non-GPRS service type IE. + +**Table 17.1.8/3GPP TS 29.018: BSSAP+-IMSI-DETACH-INDICATION message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|----------------------------------------|---------------------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| SGSN number | SGSN number
18.4.22 | M | TLV | 5-11 | +| IMSI detach from non-GPRS service type | IMSI detach from non-GPRS service type
18.4.12 | M | TLV | 3 | +| Cell global identity | Cell global identity
18.4.1 | O | TLV | 10 | +| Location information age | Location information age
18.4.15 | O | TLV | 4 | +| Service area identification | Service area identification
18.4.21b | O | TLV | 9 | + +#### 17.1.8.1 Cell global identity (A/Gb mode only) + +In A/Gb mode, the SGSN shall include the Cell global identity where the mobile was in the last radio contact. + +#### 17.1.8.2 Location information age + +If the detach is due to implicit detach and the Cell global identity is available, then the SGSN should include the Location information age. + +#### 17.1.8.3 Service area identification (Iu mode only) + +In Iu mode, the SGSN should include the Service area identification where the mobile was in the last radio contact. + +### 17.1.9 BSSAP+-LOCATION-UPDATE-ACCEPT message + +This message is sent by the VLR to the SGSN to indicate that update or IMSI attach in the VLR has been completed. + +**Table 17.1.9/3GPP TS 29.018: BSSAP+-LOCATION-UPDATE-ACCEPT message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|--------------------------|-------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Location area identifier | Location area identifier
18.4.14 | M | TLV | 7 | +| New TMSI, or IMSI | Mobile identity
18.4.17 | O | TLV | 6-10 | + +#### 17.1.9.1 New TMSI, or IMSI + +This information element represents the identity to be used for (and then by) the MS. + +If this information element is an IMSI, then the mobile station is not allocated any TMSI (and deletes any TMSI accordingly). If this information element is a TMSI, then the mobile station will use this TMSI as the new temporary identity (the MS deletes its old TMSI if available, and stores the new TMSI). If neither a TMSI nor an IMSI are included in this information element, the old TMSI, if any available, will be kept. + +### 17.1.10 BSSAP+-LOCATION-UPDATE-REJECT message + +#### 17.1.10.1 Message definition + +This message is sent by the VLR to the SGSN to indicate that location update or IMSI attach has failed. + +**Table 17.1.10/3GPP TS 29.018: BSSAP+-LOCATION-UPDATE-REJECT message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|--------------------------|-------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Reject cause | Reject cause
18.4.21 | M | TLV | 3 | +| Location area identifier | Location area identifier
18.4.14 | O | TLV | 7 | + +#### 17.1.10.2 Location area identifier + +The VLR shall include this information element. + +### 17.1.11 BSSAP+-LOCATION-UPDATE-REQUEST message + +This message is sent by the SGSN to the VLR either to request update of its location file (normal update) or to request IMSI attach. + +**Table 17.1.11/3GPP TS 29.018: BSSAP+-LOCATION-UPDATE-REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------------------|-----------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| SGSN number | SGSN number
18.4.22 | M | TLV | 5-11 | +| Update type | GPRS location update type
18.4.6 | M | TLV | 3 | +| New Cell global identity | Cell global identity
18.4.1 | M | TLV | 10 | +| Mobile station classmark | Mobile station classmark 1
18.4.18 | M | TLV | 3 | +| Old location area identifier | Location area identifier
18.4.14 | O | TLV | 7 | +| TMSI status | TMSI status
18.4.24 | O | TLV | 3 | +| New service area identification | Service area identification
18.4.21b | O | TLV | 9 | +| IMEISV | IMEISV
18.4.9 | O | TLV | 10 | +| TMSI based NRI container | TMSI based NRI container
18.4.28 | O | TLV | 4 | +| Selected CN operator | Selected CN operator
18.4.29 | O | TLV | 5 | + +#### 17.1.11.1 Old location area identifier + +This information element should be included. + +#### 17.1.11.2 New cell global identity + +In A/Gb mode, the cell global identity which shall be included is the one where the MS is in the current radio contact. + +In Iu mode, the cell global identity which shall be included indicates where the MS is in the current location area. The cell identity part of this information shall be ignored by the VLR. + +In a shared network, the PLMN identity contained in the cell global identity shall be the PLMN identity of the selected core network operator (see 3GPP TS 23.251 [24]). + +#### 17.1.11.3 TMSI status + +This information element shall be included if the TMSI status received in the ATTACH REQUEST or ROUTING AREA UPDATING REQUEST message from the MS indicates, that no valid TMSI is available in the MS. + +#### 17.1.11.4 Mobile station classmark + +This information element does not serve any useful purpose, but shall be included for reasons of compatibility with earlier versions of the protocol. To ease interworking with old VLR equipment, the SGSN shall encode the contents of this information element as: revision level 'GSM phase 2', 'early classmark sending supported', 'encryption algorithm A5/1 supported', and RF power capability 'class 1'. + +#### 17.1.11.5 New service area identification + +In Iu mode, the service area identification which should be included is the one where the MS is in the current radio contact. + +In a shared network, the PLMN identity contained in the service area identification shall be the PLMN identity of the selected core network operator (see 3GPP TS 23.251 [24]). + +#### 17.1.11.6 IMEISV + +This information element shall be included, if the SGSN supports the "Provision of UE Specific Behaviour Information to Network Entities" or the "Automatic Device Detection", or the "Trace for Management Based Activation/Deactivation". + +#### 17.1.11.7 TMSI based NRI container + +This information element shall be included if the TMSI based NRI container has been received in the ATTACH REQUEST or ROUTING AREA UPDATING REQUEST message from the MS. + +#### 17.1.11.8 Selected CN operator + +This information element shall be included for the non-supporting UE if the network is configured to support gateway core network (GWCN). + +### 17.1.12 BSSAP+-MM-INFORMATION-REQUEST + +This message is sent by the VLR to the SGSN to provide the MS with subscriber specific information. + +**Table 17.1.12/3GPP TS 29.018: BSSAP+-MM-INFORMATION-REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|---------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| MM information | MM information
18.4.16 | O | TLV | 3-n | + +#### 17.1.12.1 MM information + +This information element should be included in this message. + +### 17.1.13 BSSAP+-MOBILE-STATUS message + +This message is sent by both the SGSN or the VLR to indicate an error. + +**Table 17.1.13/3GPP TS 29.018: BSSAP+-MOBILE-STATUS message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|-----------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | O | TLV | 6-10 | +| Gs Cause | Gs Cause
18.4.7 | M | TLV | 3 | +| Erroneous message | Erroneous message
18.4.5 | M | TLV | 3-n | + +#### 17.1.13.1 IMSI + +If the MS is identified by the IMSI, then this information element shall be included. + +### 17.1.14 BSSAP+-MS-ACTIVITY-INDICATION message + +This message is sent by the SGSN to the VLR to indicate that activity from an MS has been detected. + +**Table 17.1.14/3GPP TS 29.018: BSSAP+-MS-ACTIVITY-INDICATION message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|-----------------------------|-----------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Cell global identity | Cell global identity
18.4.1 | O | TLV | 10 | +| Service area identification | Service area identification
18.4.21b | O | TLV | 9 | + +#### 17.1.14.1 Cell global identity (A/Gb mode only) + +In A/Gb mode, the SGSN shall include the cell global identity where the MS was in the last radio contact. + +#### 17.1.14.2 Service area identification (Iu mode only) + +In Iu mode, the SGSN should include the Service area identification where the mobile was in the last radio contact. + +### 17.1.15 BSSAP+-MS-INFORMATION-REQUEST message + +This message is sent from the VLR to the SGSN to request information associated with the indicated IMSI. The type of information requested is specified in the Information requested IE. + +**Table 17.1.15/3GPP TS 29.018: BSSAP+-MS-INFORMATION-REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|-----------------------|----------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Information requested | Information requested
18.4.13 | M | TLV | 3 | + +### 17.1.16 BSSAP+-MS-INFORMATION-RESPONSE message + +This message is sent from the SGSN to the VLR as a response to a previous BSSAP+-MS-INFORMATION-REQUEST message. (At least one of the requested identities shall be sent). + +Table 17.1.16/3GPP TS 29.018: BSSAP+-MS-INFORMATION-RESPONSE message content + +| Information Element | Type/Reference | Presence | Format | Length | +|-----------------------------|-----------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| TMSI | TMSI
18.4.23 | O | TLV | 6 | +| PTMSI | PTMSI
18.4.20 | O | TLV | 6 | +| IMEI | IMEI
18.4.8 | O | TLV | 10 | +| IMEISV | IMEISV
18.4.9 | O | TLV | 10 | +| Cell global identity | Cell global identity
18.4.1 | O | TLV | 10 | +| Location information age | Location information age
18.4.15 | O | TLV | 4 | +| Mobile station state | Mobile station state
18.4.19 | O | TLV | 3 | +| Service area identification | Service area identification
18.4.21b | O | TLV | 9 | + +#### 17.1.16.1 IMEI + +This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST message and if this information is obtainable. + +#### 17.1.16.2 IMIESV + +This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST message and if this information is obtainable. + +#### 17.1.16.3 Cell global identity (A/Gb mode only) + +In A/Gb mode, cell global identity where the MS was in the last radio contact. + +This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST message and if this information is obtainable. + +#### 17.1.16.4 Location information age + +Time in minutes since the MS last established a radio transaction. + +This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST message and if this information is obtainable. + +#### 17.1.16.5 Mobile station state + +This information element should be included in this message, irrespective of the information requested. + +#### 17.1.16.6 TMSI + +This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST message and if this information is obtainable. + +#### 17.1.16.7 Service area identification (Iu mode only) + +In Iu mode, service area identification where the MS was in the last radio contact. + +This information element should be included if it was requested in the BSSAP+-MS-INFORMATION-REQUEST message and if this information is obtainable. + +### 17.1.17 BSSAP+-MS-UNREACHABLE message + +This message is sent from the SGSN to the VLR to indicate that, for example, paging could not be performed because the MS is marked as unreachable at the SGSN. + +**Table 17.1.17/3GPP TS 29.018: BSSAP+-MS-UNREACHABLE message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Gs Cause | Gs Cause
18.4.7 | M | TLV | 3 | + +#### 17.1.17.1 Gs Cause + +The value part which is typically sent for this information element in this message is 'MS unreachable'. + +### 17.1.18 BSSAP+-PAGING-REJECT message + +This message is sent from the SGSN to the VLR to indicate that the delivery of a previous BSSAP+-PAGING-REQUEST message has failed. + +**Table 17.1.18/3GPP TS 29.018: BSSAP+-PAGING-REJECT message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Gs Cause | Gs Cause
18.4.7 | M | TLV | 3 | + +### 17.1.19 BSSAP+-PAGING-REQUEST message + +This message is sent from the VLR to the SGSN and contains sufficient information to allow the paging message to be transmitted by the correct cells at the correct time. + +**Table 17.1.19/3GPP TS 29.018: BSSAP+-PAGING\_REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|--------------------------|-------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| VLR number | VLR number
18.4.26 | M | TLV | 5-11 | +| TMSI | TMSI
18.4.23 | O | TLV | 6 | +| Location area identifier | Location area identifier
18.4.14 | O | TLV | 7 | +| Channel needed | Channel needed
18.4.2 | O | TLV | 3 | +| eMLPP Priority | eMLPP Priority
18.4.4 | O | TLV | 3 | +| Global CN-Id | Global CN-Id
18.4.27 | O | TLV | 7 | + +#### 17.1.19.1 TMSI + +This element is omitted in the exceptional case where the IMSI is used instead of the TMSI as a paging address at the radio interface. + +#### 17.1.19.2 Location area identifier + +If the location area identifier is not included, then the SGSN shall page the MS in all the cells served by the VLR and the SGSN, unless the SGSN has reliable information about the location of the MS. + +#### 17.1.19.3 Channel needed + +If the Channel needed Information Element is not present, then the default value is assumed to be "any channel". + +#### 17.1.19.4 eMLPP priority + +This information element may be included when the subscriber has a subscription for eMLPP. + +#### 17.1.19.5 Global CN-Id + +If the network supports the Intra Domain Connection of RAN Nodes to multiple CN Nodes functionality, this information element shall be included when MSC/VLR initiates paging by IMSI, via the Gs interface. + +### 17.1.20 BSSAP+-RESET-ACK message + +This message is sent from the SGSN or the VLR to acknowledge a previous BSSAP+-RESET-INDICATION message. This message indicates that all the associations to the VLR or the SGSN have been marked as invalid. + +The sending entity (either SGSN or VLR) includes its identity in the BSSAP+-RESET-ACK message. + +**Table 17.1.20/3GPP TS 29.018: BSSAP+-RESET-ACK message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| SGSN number | SGSN number
18.4.22 | C | TLV | 5-11 | +| VLR number | VLR number
18.4.26 | C | TLV | 5-11 | + +#### 17.1.20.1 SGSN number + +If the SGSN is the sending entity, then it shall indicate its address by including its SGSN number Information Element. Otherwise (i.e. if the VLR is the sending entity), then the SGSN number Information Element shall not be included. + +#### 17.1.20.2 VLR number + +If the VLR is the sending entity, then it shall indicate its address by including its VLR number Information Element. Otherwise (i.e. if the SGSN is the sending entity), then the VLR number Information Element shall not be included. + +### 17.1.21 BSSAP+-RESET-INDICATION message + +This message is sent from the VLR to the SGSN to indicate that a failure in the VLR has occurred and all the associations to the VLR shall be marked as invalid. + +This message is also sent from the SGSN to the VLR to indicate that a failure in the SGSN has occurred and all the associations to the SGSN shall be marked as invalid. + +The sending entity (either SGSN or VLR) includes its identity in the BSSAP+-RESET-INDICATION message. + +**Table 17.1.21/3GPP TS 29.018: BSSAP+-RESET-INDICATION message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|---------------------|------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| SGSN number | SGSN number
18.4.22 | C | TLV | 5-11 | +| VLR number | VLR number
18.4.26 | C | TLV | 5-11 | + +#### 17.1.21.1 SGSN number + +If the SGSN is the sending entity, then it shall indicate its address by including its SGSN number Information Element. Otherwise (i.e. if the VLR is the sending entity), then the SGSN number Information Element shall not be included. + +#### 17.1.21.2 VLR number + +If the VLR is the sending entity, then it shall indicate its address by including its VLR number Information Element. Otherwise (i.e. if the SGSN is the sending entity), then the VLR number Information Element shall not be included. + +### 17.1.22 BSSAP+-TMSI-REALLOCATION-COMPLETE message + +This message is sent by the SGSN to the VLR to indicate that TMSI reallocation on the MS has been successfully completed. + +**Table 17.1.22/3GPP TS 29.018: BSSAP+-TMSI-REALLOCATION-COMPLETE message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|-----------------------------|-----------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| Cell global identity | Cell global identity
18.4.1 | O | TLV | 10 | +| Service area identification | Service area identification
18.4.21b | O | TLV | 9 | + +#### 17.1.22.1 Cell global identity (A/Gb mode only) + +The SGSN shall include the cell global identity where the Mobile Station was in the last radio contact. + +#### 17.1.22.2 Service area identification (Iu mode only) + +In Iu mode, the SGSN should include the Service area identification where the mobile was in the last radio contact. + +### 17.1.23 BSSAP+-UPLINK-TUNNEL-REQUEST message + +This message is sent from the SGSN to the non-GSM MSC/VLR to convey the tunneling payload received from the MS identified by the specified IMSI. + +**Table 17.1.23/3GPP TS 29.018: BSSAP+-UPLINK-TUNNEL-REQUEST message content** + +| Information Element | Type/Reference | Presence | Format | Length | +|----------------------------------------|---------------------------------------------------|----------|--------|--------| +| Message type | Message type
18.2 | M | V | 1 | +| IMSI | IMSI
18.4.10 | M | TLV | 6-10 | +| SGSN number | SGSN number
18.4.22 | M | TLV | 5-11 | +| Uplink Tunnel Payload Control and Info | Uplink Tunnel Payload Control and Info
18.4.25 | M | TLV | 3-223 | + +# 18 Message format and information element coding + +This clause specifies the coding of the Information Elements used in by the BSSAP+ protocol. The spare bits in the coding of an IE shall be set to zero by the sender and shall be ignored by the receiver. + +All unassigned codes (whether omitted or explicitly *Unassigned* in the text) shall be treated as unknown (see clause 16). + +## 18.1 Overview + +## 18.2 Message type + +Message type uniquely identifies the message being sent. It is a single octet element, mandatory in all messages. + +**Table 18.2/3GPP TS 29.018: Message type information element** + +| 8 7 6 5 4 3 2 1 | Message type | Reference | +|------------------------------------------|---------------------------------------------------------|-----------| +| 0 0 0 0 0 0 0 0 | Unassigned : treated as an unknown Message type. | 18 and 16 | +| 0 0 0 0 0 0 0 1 | BSSAP+-PAGING-REQUEST | 17.1.19 | +| 0 0 0 0 0 0 1 0 | BSSAP+-PAGING-REJECT | 17.1.18 | +| 0 0 0 0 0 1 1 0
to
0 0 0 0 0 1 1 0 | Unassigned : treated as an unknown Message type. | 18 and 16 | +| 0 0 0 0 0 1 1 1 | BSSAP+-DOWNLINK-TUNNEL-REQUEST | 17.1.4 | +| 0 0 0 0 1 0 0 0 | BSSAP+-UPLINK-TUNNEL-REQUEST | 17.1.23 | +| 0 0 0 0 1 0 0 1 | BSSAP+-LOCATION-UPDATE-REQUEST | 17.1.11 | +| 0 0 0 0 1 0 1 0 | BSSAP+-LOCATION-UPDATE-ACCEPT | 17.1.9 | +| 0 0 0 0 1 0 1 1 | BSSAP+-LOCATION-UPDATE-REJECT | 17.1.10 | +| 0 0 0 0 1 1 0 0 | BSSAP+-TMSI-REALLOCATION-COMPLETE | 17.1.22 | +| 0 0 0 0 1 1 0 1 | BSSAP+-ALERT-REQUEST | 17.1.3 | +| 0 0 0 0 1 1 1 0 | BSSAP+-ALERT-ACK | 17.1.1 | +| 0 0 0 0 1 1 1 1 | BSSAP+-ALERT-REJECT | 17.1.2 | +| 0 0 0 1 0 0 0 0 | BSSAP+-MS-ACTIVITY-INDICATION | 17.1.14 | +| 0 0 0 1 0 0 0 1 | BSSAP+-GPRS-DETACH-INDICATION | 17.1.6 | +| 0 0 0 1 0 0 1 0 | BSSAP+-GPRS-DETACH-ACK | 17.1.5 | +| 0 0 0 1 0 0 1 1 | BSSAP+-IMSI-DETACH-INDICATION | 17.1.8 | +| 0 0 0 1 0 1 0 0 | BSSAP+-IMSI-DETACH-ACK | 17.1.7 | +| 0 0 0 1 0 1 0 1 | BSSAP+-RESET-INDICATION | 17.1.21 | +| 0 0 0 1 0 1 1 0 | BSSAP+-RESET-ACK | 17.1.20 | +| 0 0 0 1 0 1 1 1 | BSSAP+-MS-INFORMATION-REQUEST | 17.1.15 | +| 0 0 0 1 1 0 0 0 | BSSAP+-MS-INFORMATION-RESPONSE | 17.1.16 | +| 0 0 0 1 1 0 0 1 | Unassigned : treated as an unknown Message type. | 18 and 16 | +| 0 0 0 1 1 0 1 0 | BSSAP+-MM-INFORMATION-REQUEST | 17.1.12 | +| 0 0 0 1 1 1 0 1 | BSSAP+-MOBILE-STATUS | 17.1.13 | +| 0 0 0 1 1 1 1 0 | Unassigned : treated as an unknown Message type. | 18 and 16 | +| 0 0 0 1 1 1 1 1 | BSSAP+-MS-UNREACHABLE | 17.1.17 | + +## 18.3 Information Element Identifiers + +The next list shows the coding of the Information Element Identifiers used in the present document. + +**Table 18.3/3GPP TS 29.018: Information Element Identifier coding** + +| 8 7 6 5 4 3 2 1 | Information element | Reference | +|------------------------------------------|-----------------------------------------------|-----------| +| 0 0 0 0 0 0 0 1 | IMSI | 18.4.10 | +| 0 0 0 0 0 1 0 | VLR number | 18.4.26 | +| 0 0 0 0 0 1 1 | TMSI | 18.4.23 | +| 0 0 0 0 1 0 0 | Location area identifier | 18.4.14 | +| 0 0 0 0 1 0 1 | Channel Needed | 18.4.2 | +| 0 0 0 0 1 1 0 | eMLPP Priority | 18.4.4 | +| 0 0 0 0 1 1 1 | TMSI status | 18.4.24 | +| 0 0 0 1 0 0 0 | Gs cause | 18.4.7 | +| 0 0 0 1 0 0 1 | SGSN number | 18.4.22 | +| 0 0 0 1 0 1 0 | GPRS location update type | 18.4.6 | +| 0 0 0 1 0 1 1 | Global CN-Id | 18.4.27 | +| 0 0 0 1 1 0 0 | Unassigned: treated as an unknown IEI. | 18 and 16 | +| 0 0 0 1 1 0 1 | Mobile station classmark 1 | 18.4.18 | +| 0 0 0 1 1 1 0 | Mobile identity | 18.4.17 | +| 0 0 0 1 1 1 1 | Reject cause | 18.4.21 | +| 0 0 1 0 0 0 0 | IMSI detach from GPRS service type | 18.4.11 | +| 0 0 1 0 0 0 1 | IMSI detach from non-GPRS service type | 18.4.12 | +| 0 0 1 0 0 1 0 | Information requested | 18.4.13 | +| 0 0 1 0 0 1 1 | PTMSI | 18.4.20 | +| 0 0 1 0 1 0 0 | IMEI | 18.4.8 | +| 0 0 1 0 1 0 1 | IMEISV | 18.4.9 | +| 0 0 1 0 1 1 0 | Unassigned: treated as an unknown IEI. | 18 and 16 | +| 0 0 1 0 1 1 1 | MM information | 18.4.16 | +| 0 0 1 1 0 0 0 | Cell Global Identity | 18.4.1 | +| 0 0 1 1 0 0 1 | Location information age | 18.4.15 | +| 0 0 1 1 0 1 0 | Mobile station state | 18.4.19 | +| 0 0 1 1 0 1 1 | Erroneous message | 18.4.5 | +| 0 0 1 1 1 0 0 | Downlink Tunnel Payload Control and Info | 18.4.3 | +| 0 0 1 1 1 0 1 | Uplink Tunnel Payload Control and Info | 18.4.25 | +| 0 0 1 1 1 1 0 | Service Area Identification | 18.4.21b | +| 0 0 1 1 1 1 1 | TMSI based NRI container | 18.4.28 | +| 0 0 1 0 0 0 0 0
to
1 1 1 1 1 1 1 1 | Unassigned: treated as an unknown IEI. | 18 and 16 | + +### 18.3a Length indicator + +The length indicator of the information elements consists of one octet and contains the binary encoding of the number of octets of the value part in the information elements. + +## 18.4 Information elements + +### 18.4.1 Cell global identity + +This information element uniquely identifies one cell. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
to
Octet 10 | The rest of the information element is coded as the value part of the cell global id IE defined in 3GPP TS 48.018 [15] (not including 3GPP TS 48.018 IEI and 3GPP TS 48.018 length indicator). | | | | | | | | + +Figure 18.4.1/3GPP TS 29.018: Cell global identity IE + +### 18.4.2 Channel needed + +The purpose of the *Channel Needed* information element is to indicate which type of channel is needed for the transaction linked to the paging procedure. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | The rest of the information element is coded as the IEI part and the value part of the Channel Needed IE defined in 3GPP TS 44.018 [11a]. | | | | | | | | + +Figure 18.4.2/3GPP TS 29.018: Channel needed IE + +### 18.4.3 Downlink Tunnel Payload Control and Info + +This information element is used to convey the payload of octets to be delivered to the identified mobile. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------------|------------------|----------------------------|---|---|---|-----------------|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Spare | TOM Protocol Discriminator | | | E | Tunnel Priority | | | +| Octet 4
to
Octet n | Tunnel payload | | | | | | | | + +TOM Protocol Discriminator: Identifies the protocol using tunnelling of non-GSM signalling. For coding, see 3GPP TS 44.064 [12]. + +E: Cipher Request. When set to 1 indicates that the SGSN shall cipher the payload, when set to 0 indicates that the SGSN shall not cipher the payload. + +Tunnel Priority: Indicates the priority of the Tunnel Payload. For coding, see table 20.1: Association between Tunnel Priority and LLC SAPs. + +Figure 18.4.3/3GPP TS 29.018: Downlink Tunnel Payload Control and Info IE + +### 18.4.4 eMLPP Priority + +This element indicates the eMLPP-Priority. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | The rest of the information element is coded as the value part of the eMLPP-Priority IE defined in 3GPP TS 48.008 [14] (not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 length indicator). | | | | | | | | + +Figure 18.4.4/3GPP TS 29.018: eMLPP Priority IE + +### 18.4.5 Erroneous message + +The Erroneous message IE is a TLV IE that encapsulates the message in error. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
-
Octet n | Erroneous message including the message type. | | | | | | | | +| NOTE: | If the size of the erroneous message including the message type exceeded 255 octets, only the first 255 octets are included. | | | | | | | | + +Figure 18.4.5/3GPP TS 29.018: Erroneous message IE + +### 18.4.6 GPRS location update type + +The purpose of the GPRS location update type information element is to indicate to the VLR whether an IMSI attach or a normal location update has been performed by the MS. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|---------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | GPRS location update type value | | | | | | | | + +Figure 18.4.6/3GPP TS 29.018: GPRS location update type IE + +Table 18.4.6/3GPP TS 29.018: GPRS location update type IE value part + +| | +|-------------------------------------------------------------------------------------------------------------------| +| GPRS location update type value (octet 3) | +| Bits | +| 8 7 6 5 4 3 2 1 | +| 0 0 0 0 0 0 0 0 Shall not be sent in this version of the protocol. If received, shall be treated as '00000010'. | +| 0 0 0 0 0 0 0 1 IMSI attach | +| 0 0 0 0 0 0 1 0 Normal location update | +| 0 0 0 0 0 0 1 1 Shall not be sent in this version of the protocol. If received, to shall be treated as 00000010'. | +| To | +| 1 1 1 1 1 1 1 1 | + +### 18.4.7 Gs cause + +The purpose of the value part of the Gs Cause information element is to indicate an error to the receiving entity. This could be a protocol data error or to indicate to the VLR the reason why a paging procedure could not be performed. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Gs Cause value | | | | | | | | + +Figure 18.4.7/3GPP TS 29.018: Gs Cause IE + +Table 18.4.7/3GPP TS 29.018: Gs Cause IE value part + +| Gs Cause value (octet 3) | | +|--------------------------|---------------------------------------------------------------| +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Normal, unspecified in this version of the protocol. | +| 0 0 0 0 0 0 0 1 | IMSI detached for GPRS services | +| 0 0 0 0 0 0 1 0 | IMSI detached for GPRS and non-GPRS services | +| 0 0 0 0 0 0 1 1 | IMSI unknown | +| 0 0 0 0 0 1 0 0 | IMSI detached for non-GPRS services | +| 0 0 0 0 0 1 0 1 | IMSI implicitly detached for non-GPRS services | +| 0 0 0 0 0 1 1 0 | MS unreachable | +| 0 0 0 0 0 1 1 1 | Message not compatible with the protocol state | +| 0 0 0 0 1 0 0 0 | Missing mandatory information element | +| 0 0 0 0 1 0 0 1 | Invalid mandatory information | +| 0 0 0 0 1 0 1 0 | Conditional IE error | +| 0 0 0 0 1 0 1 1 | Semantically incorrect message | +| 0 0 0 0 1 1 0 0 | Message unknown | +| 0 0 0 0 1 1 0 1 | Address error | +| 0 0 0 0 1 1 1 0 | TOM functionality not supported | +| 0 0 0 0 1 1 1 1 | Ciphering request cannot be accommodated | +| 0 0 0 1 0 0 0 0 | to Normal, unspecified in this version of the protocol | +| 1 1 1 1 1 1 1 1 | | + +NOTE: '*Normal, unspecified*' has the same meaning than in 3GPP TS 24.008 [11], informative Annex H (UMTS specific cause values for call control). It is used to report a normal event, and should not be interpreted as syntactically incorrect nor unknown if received. + +### 18.4.8 IMEI + +The IMEI is coded as a sequence of BCD digits, compressed two into each octet. The IMEI consists of 15 digits (see 3GPP TS 23.003 [5]). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------------|------------------|---|---|---|----------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | length indicator | | | | | | | | +| octet 3 | digit 2 | | | | digit 1 | | | | +| octet 4 | digit 4 | | | | digit 3 | | | | +| octet 5 | digit 6 | | | | digit 5 | | | | +| octet 6 | digit 8 | | | | digit 7 | | | | +| octet 7 | digit 10 | | | | digit 9 | | | | +| octet 8 | digit 12 | | | | digit 11 | | | | +| octet 9 | digit 14 | | | | digit 13 | | | | +| octet 10 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | + +Figure 18.4.8/3GPP TS 29.018: IMEI IE + +### 18.4.9 IMEISV + +The IMEISV is coded as a sequence of BCD digits, compressed two into each octet. The IMEISV consists of 16 digits (see 3GPP TS 23.003 [5]). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------|------------------|---|---|---|----------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | length indicator | | | | | | | | +| octet 3 | digit 2 | | | | digit 1 | | | | +| octet 4 | digit 4 | | | | digit 3 | | | | +| octet 5 | digit 6 | | | | digit 5 | | | | +| octet 6 | digit 8 | | | | digit 7 | | | | +| octet 7 | digit 10 | | | | digit 9 | | | | +| octet 8 | digit 12 | | | | digit 11 | | | | +| octet 9 | digit 14 | | | | digit 13 | | | | +| octet 10 | digit 16 | | | | digit 15 | | | | + +Figure 18.4.9/3GPP TS 29.018: IMEISV IE + +### 18.4.10 IMSI + +The IMSI is coded as a sequence of BCD digits, compressed two into each octet. This is a variable length element, and includes a length indicator. The IMSI is defined in 3GPP TS 23.003 [5]. It shall not exceed 15 digits (see 3GPP TS 23.003 [5]). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------|------------------|---|---|---|--------------|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | IMSI digit 1 | | | | * parity | 0 | 0 | 1 | +| Octet 4 | IMSI digit 3 | | | | IMSI digit 2 | | | | +| Octet 4+x | IMSI digit i+1 | | | | IMSI digit i | | | | + +Figure 18.4.10/3GPP TS 29.018: IMSI IE + +Where $x = (i-2)/2$ and $i$ is always even + +\* The value of the parity bit (bit 4 in octet 3) indicates: + +0 Even number of IMSI digits; + +1 Odd number of IMSI digits; + +If the number of IMSI digits is even then bits 5 to 8 of the last octet shall be filled with an end mark coded as 1111. + +### 18.4.11 IMSI detach from GPRS service type + +The purpose of the IMSI detach from GPRS service type information element is to indicate to the VLR the type of IMSI detach from GPRS service performed by the MS or the SGSN. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | IMSI detach from GPRS service type value | | | | | | | | + +Figure 18.4.11/3GPP TS 29.018: IMSI detach from GPRS service type IE + +Table 18.4.11/3GPP TS 29.018: IMSI detach from GPRS service type IE value part + +| | | +|----------------------------------------------------|-------------------------------------------------------------------| +| IMSI detach from GPRS service type value (octet 3) | | +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Interpreted as reserved in this version of the protocol | +| 0 0 0 0 0 0 0 1 | Network initiated IMSI detach from GPRS service | +| 0 0 0 0 0 1 0 | MS initiated IMSI detach from GPRS service | +| 0 0 0 0 0 1 1 | GPRS services not allowed | +| 0 0 0 0 1 0 0 | to Interpreted as reserved in this version of the protocol | +| 1 1 1 1 1 1 1 | | + +### 18.4.12 IMSI detach from non-GPRS service type + +The purpose of the IMSI detach from non-GPRS service type information element is to indicate to the VLR if the type of IMSI detach from non-GPRS service was explicitly performed by the MS or implicitly performed by the SGSN. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|----------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | IMSI detach from non-GPRS service type value | | | | | | | | + +Figure 18.4.12/3GPP TS 29.018: IMSI detach from non-GPRS service type IE + +Table 18.4.12/3GPP TS 29.018: IMSI detach from non-GPRS service type IE value part + +| | | +|--------------------------------------------------------|----------------------------------------------------------------------------| +| IMSI detach from non-GPRS service type value (octet 3) | | +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Interpreted as reserved in this version of the protocol | +| 0 0 0 0 0 0 0 1 | Explicit MS initiated IMSI detach from non-GPRS service | +| 0 0 0 0 0 1 0 | Combined explicit MS initiated IMSI detach from GPRS and non-GPRS services | +| 0 0 0 0 0 1 1 | Implicit SGSN initiated IMSI detach from GPRS and non-GPRS services | +| 0 0 0 0 1 0 0 | to Interpreted as reserved in this version of the protocol | +| 1 1 1 1 1 1 1 | | + +### 18.4.13 Information requested + +The Information requested IE is a TLV IE that indicates to the SGSN the type of information requested by the VLR. The coding of the V field is as follows. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|-----------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Information requested value | | | | | | | | + +Figure 18.4.13/3GPP TS 29.018: Information requested IE + +Table 18.4.13/3GPP TS 29.018: Information requested IE value part + +| | | +|---------------------------------------|----------------------------------------------------------------------| +| Information requested value (octet 3) | | +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Interpreted as Not supported in this version of the protocol. | +| 0 0 0 0 0 0 0 1 | PTMSI | +| 0 0 0 0 0 0 1 0 | IMEI | +| 0 0 0 0 0 0 1 1 | IMEISV | +| 0 0 0 0 0 1 0 0 | PTMSI and IMEI | +| 0 0 0 0 0 1 0 1 | PTMSI and IMEISV | +| 0 0 0 0 0 1 1 0 | IMEI and IMEISV | +| 0 0 0 0 0 1 1 1 | PTMSI, IMEI, and IMEISV | +| 0 0 0 0 1 0 0 0 | Mobile location information | +| 0 0 0 0 1 0 0 1 | TMSI | +| 0 0 0 0 1 0 1 0 | Interpreted as Not supported in this version of the protocol. | +| to | | +| 1 1 1 1 1 1 1 1 | | + +NOTE: The behaviour of the receiver in the case of a *Not supported* value is described in clause 14.3, *Procedures in the SGSN*. + +### 18.4.14 Location area identifier + +This element uniquely identifies one Location Area. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3
-
Octet 7 | The rest of the information element is coded as the value part of the location area identifier IE defined in 3GPP TS 48.018 [15] (not including 3GPP TS 48.018 IEI and 3GPP TS 48.018 length indicator). | | | | | | | | + +Figure 18.4.14/3GPP TS 29.018: Location area identifier IE + +### 18.4.15 Location information age + +The Location information age IE is a TLV IE that indicates the elapsed time in minutes since the last network contact of the mobile station. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------------------------|--------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
Octet 4 | The rest of the IE is coded as the value part of the AgeOfLocationInformation as specified in 3GPP TS 29.002 [17]. | | | | | | | | + +Figure 18.4.15/3GPP TS 29.018: Location information age IE + +### 18.4.16 MM information + +The MM information IE is a TLV IE that encapsulates the user information that the SGSN forwards to the MS. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3
–
Octet n | User information: This field is composed of one or more of the information elements of the MM information message as defined in 3GPP TS 24.008 [11], excluding the Protocol discriminator, Skip indicator and Message type. This field includes the IEI and length indicator of the other information elements. | | | | | | | | + +Figure 18.4.16/3GPP TS 29.018: MM information IE + +### 18.4.17 Mobile identity + +The purpose of the *Mobile identity* information element is to provide either: + +- The International Mobile Subscriber Identity (IMSI); +- The Temporary Mobile Subscriber Identity (TMSI); +- The International Mobile Equipment Identity (IMEI); or +- The International Mobile Equipment Identity together with the Software Version number (IMEISV). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3
–
Octet n | The rest of the information element is coded as the value part of the mobile identity IE defined in 3GPP TS 24.008 [11] (not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 length indicator). | | | | | | | | + +Figure 18.4.17/3GPP TS 29.018: Mobile identity IE + +### 18.4.18 Mobile station classmark 1 + +The purpose of the *Mobile Station Classmark 1* information element is to provide the network with information concerning aspects of high priority of the mobile station equipment. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | The rest of the information element is coded as the value part of the mobile station classmark 1 IE defined in 3GPP TS 24.008 [11] (not including 3GPP TS 24.008 IEI) | | | | | | | | + +Figure 18.4.18/3GPP TS 29.018: Mobile station classmark 1 IE + +### 18.4.19 Mobile station state + +The Mobile station state IE is a TLV IE that indicates to the VLR the GMM and GSM states of the MS in the SGSN. The coding of the V field is as follows. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|----------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Mobile station state value | | | | | | | | + +Figure 18.4.19/3GPP TS 29.018: Mobile station state IE + +Table 18.4.19/3GPP TS 29.018: Mobile station state IE value part + +| Mobile station state value (octet 3) | | | +|--------------------------------------|---|---------------------------------------------------------------------------------------------------------------------| +| Bits | | | +| 8 | 7 | 6 5 4 3 2 1 | +| 0 | 0 | 0 0 0 0 0 0 IDLE or PMM-DETACHED | +| 0 | 0 | 0 0 0 0 0 1 STANDBY or PMM-IDLE, 0 PDP contexts active | +| 0 | 0 | 0 0 0 0 1 0 STANDBY or PMM-IDLE, 1 or more PDP contexts active | +| 0 | 0 | 0 0 0 0 1 1 SUSPENDED, 0 PDP contexts active | +| 0 | 0 | 0 0 0 0 1 0 SUSPENDED, 1 or more PDP contexts active | +| 0 | 0 | 0 0 0 0 1 0 1 READY or PMM-CONNECTED, 0 PDP contexts active | +| 0 | 0 | 0 0 0 0 1 1 0 READY or PMM-CONNECTED, 1 or more PDP contexts active | +| 0 | 0 | 0 0 0 0 1 1 1 IMSI unknown | +| 0 | 0 | 0 0 0 0 1 0 0 Information requested not supported | +| 0 | 0 | 0 0 0 0 1 0 1 Shall not be sent in this version of the protocol.
to If received, shall be treated as '00001000'. | +| 1 | 1 | 1 1 1 1 1 1 1 | + +### 18.4.20 PTMSI + +The PTMSI consists of 4 octets. It can be coded using a full hexadecimal representation (see 3GPP TS 23.003 [5]). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | length indicator | | | | | | | | +| octet 3 | PTMSI octet 1 | | | | | | | | +| octet 4 | PTMSI octet 2 | | | | | | | | +| octet 5 | PTMSI octet 3 | | | | | | | | +| octet 6 | PTMSI octet 4 | | | | | | | | + +Figure 18.4.20/3GPP TS 29.018: PTMSI IE + +### 18.4.21 Reject cause + +The purpose of the *Reject Cause* information element is to indicate the reason why a request from the mobile station is rejected by the network. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3 | The rest of the information element is coded as the value part of the reject cause IE defined in 3GPP TS 24.008 [11], not including 3GPP TS 24.008 IEI. | | | | | | | | + +Figure 18.4.21/3GPP TS 29.018: Reject cause IE + +#### 18.4.21b Service Area Identification + +This information element uniquely identifies one service area. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
to
Octet 9 | The rest of the information element is coded as the the value part of the SAI IE defined in 3GPP TS 25.413 [22] (not including 3GPP TS 25.413 IEI and 3GPP TS 25.413 length indicator). | | | | | | | | + +Figure 18.4.27/3GPP TS 29.018: Service Area Identification IE + +### 18.4.22 SGSN number + +The SGSN number is coded as a sequence of TBCD digits (as specified in 3GPP TS 29.002 [17]), compressed two into each octet. The Number is in international E.164 format as indicated by Octet 3 which coding is specified in 3GPP TS 29.002 [17]. This is a variable length information element, and includes a length indicator. The value part of the SGSN number information element (not including IEI, Length indicator and Octet 3) shall not exceed 15 digits. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---------|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | +| Octet 4 | digit 2 | | | | digit 1 | | | | +| Octet n | digit i+1 | | | | digit i | | | | + +Figure 18.4.22/3GPP TS 29.018: SGSN number IE + +### 18.4.23 TMSI + +The TMSI consists of 4 octets. It can be coded using a full hexadecimal representation (see 3GPP TS 23.003 [5]). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | length indicator | | | | | | | | +| octet 3 | TMSI octet 1 | | | | | | | | +| octet 4 | TMSI octet 2 | | | | | | | | +| octet 5 | TMSI octet 3 | | | | | | | | +| octet 6 | TMSI octet 4 | | | | | | | | + +Figure 18.4.23/3GPP TS 29.018: TMSI IE + +### 18.4.24 TMSI status + +The purpose of the TMSI status information element is to indicate to the VLR whether a valid TMSI is available in the MS. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---|---|---|-----------| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Spare | | | | | | | TMSI flag | + +Figure 18.4.24/3GPP TS 29.018: TMSI status IE + +Table 18.4.24/3GPP TS 29.018: TMSI status IE value part + +| | +|------------------------------------------------------------------| +| TMSI flag (octet 3) | +| Bit | +| 1 | +| 0 no valid TMSI available | +| 1 valid TMSI available | +| Bits 2-8 in octet 3 are spare and shall be coded all equal to 0. | + +### 18.4.25 Uplink Tunnel Payload Control and Info + +This information element is used to convey the payload of octets received from the mobile to the appropriate non-GSM MSC/VLR. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------------|------------------|----------------------------|---|---|---|-----------------|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Spare | TOM Protocol Discriminator | | | E | Tunnel Priority | | | +| Octet 4
to
Octet n | Tunnel payload | | | | | | | | + +TOM Protocol Discriminator: Identifies the protocol using tunnelling of non-GSM signalling. For coding, see 3GPP TS 44.064 [12]. + +E: Cipher Request. When set to 1 indicates that the SGSN received the payload in ciphered form, when set to 0 indicates that the SGSN did not receive the payload in ciphered form. + +Tunnel Priority: Indicates the priority of the Tunnel Payload. For coding, see Table 20.1: Association between Tunnel Priority and LLC SAPs. + +Figure 18.4.25/3GPP TS 29.018: Uplink Tunnel Payload Control and Info IE + +### 18.4.26 VLR number + +The VLR number is coded as a sequence of TBCD digits (as specified in 3GPP TS 29.002 [17]), compressed two into each octet. The Number is in international E.164 format as indicated by Octet 3 which coding is specified in 3GPP TS 29.002 [17]. This is a variable length information element, and includes a length indicator. The value part of the VLR number information element (not including IEI, length indicator and Octet 3), shall not exceed 15 digits. + +Table 18.4.26/3GPP TS 29.018: VLR number IE + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---------|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | +| Octet 4 | digit 2 | | | | digit 1 | | | | +| Octet n | digit i+1 | | | | digit i | | | | + +### 18.4.27 Global CN-Id + +The Global CN-Id consists of a PLMN-Id and a CN-Id, see 3GPP TS 23.003 [5]. The PLMN-Id consists of MCC and MNC coded according to Location Area Identification in 3GPP TS 24.008 [11]. The CN-Id is an integer defined by O&M. The least significant bit of the CN-Id field is bit 1 of octet 7 and the most significant bit is bit 8 of octet 6. If the CN-Id does not fill the field reserved for it, the rest of the bits are set to '0'. + +Table 18.4.27/3GPP TS 29.018: Global CN-Id IE + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | PLMN-Id
Coded as octets 2 to 4 of the Location Area Identification IE, defined in 3GPP TS 24.008 [11] (not including 3GPP TS 24.008 IEI and LAC). | | | | | | | | +| Octet 4 | | | | | | | | | +| Octet 5 | | | | | | | | | +| Octet 6 | CN-Id (INTEGER 0..4095) | | | | | | | | +| Octet 7 | | | | | | | | | + +### 18.4.28 TMSI based NRI container + +The purpose of the TMSI based NRI container information element is to allow the VLR to determine whether the MS has performed inter VLR mobility or intra VLR mobility when the VLR holds a current registration of the UE that could also exist at another VLR. + +The TMSI based NRI container value consists of 10 bits which correspond to bits 23 to 14 of the valid TMSI (3GPP TS 23.236 [26]). + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3 | The rest of the information element is coded as the value part of the Network resource identifier container IE defined in 3GPP TS 24.008. | | | | | | | | +| Octet 4 | | | | | | | | | + +Figure 18.4.28/3GPP TS 29.018: TMSI based NRI container IE + +### 18.4.29 Selected CN operator + +The selected CN operator information element indicates the selected core network operator by the SGSN for the non-supporting UE when CS domain is configured for gateway core network (GWCN). The selected CN operator information element is coded as shown in figure 18.4.29. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Coded as octets 2 to 4 of the Location Area Identification IE, defined in 3GPP TS 24.008 [11] (not including 3GPP TS 24.008 IEI and LAC). | | | | | | | | +| Octet 4 | | | | | | | | | +| Octet 5 | | | | | | | | | + +Figure 18.4.29/3GPP TS 29.018: Selected CN operator information element + +# 19 List of system variables + +## 19.1 Timers + +This clause lists the management timers specified for the operation of the BSSAP+ protocol. All the implementation shall support the range of values specified below. The specific value of the timers shall be under the control of the operator. + +**Table 19.1/3GPP TS 29.018: Management Timers** + +| Timer name | Default value | Timer range | Granularity | Notes | Relation to other timers | +|------------|---------------|----------------|-------------|-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| T5 | - | 2 s to 20 s | 100 ms | Guards the Paging procedure at the VLR. | Value is correlated to DRX parameter Split PG CYCLE (max possible = 16 s)
Default should be set acc. to max split cycle supported by the SGSN (operator choice) | +| T6-1 | - | 10 s to 90 s | 1 s | Guards the Location Update procedure. | It should be higher than 2 times the maximum transmission time in the Gs interface, plus the supervision timer of the Update Location procedure [3GPP TS 29.002 [17]] | +| T6-2 | 40 s | 5 s to 60 s | 1 s | Guards the TMSI reallocation procedure. | It should be higher than 2 times the maximum transmission time in the Gs interface, plus 4 times T3350 [3GPP TS 24.008 [11]] | +| T7 | 4 s | 1 s to 30 s | 1 s | Guards the Non-GPRS alert procedure. | None. | +| T8 | 4 s | 1s to 30 s | 1 s | Guards the Explicit IMSI detach from GPRS services procedure. | None. | +| T9 | 4 s | 1-30 s | 1 s | Guards the Explicit IMSI detach from non-GPRS services procedure. | None. | +| T10 | 4 s | 1-30 s | 1 s | Guards the Implicit IMSI detach from non-GPRS services procedure. | None. | +| T11 | 4 s | 1-120 s | 1 s | Guards the VLR reset procedure. | None. | +| T12-1 | - | 8 - 60x384+8 s | 1 min | Controls the resetting of the 'SGSN-Reset' variable. | It should be longer than the longest Periodic RAU timer running on the SGSN, plus the transmission delay on the radio interface. | +| T12-2 | 4 s | 1-120 s | 1 sec | Guards the SGSN reset procedure. | None. | +| T14 | - | 4-36 s | 1 s | Guards the MS Information procedure. | None | + +NOTE: The Default value is the recommended value. + +## 19.2 Retry counters + +This clause lists the management retry counters specified for the operation of the BSSAP+ protocol. The values indicated are recommended values. + +**Table 19.2/3GPP TS 29.018: Management Retry counters** + +| Retry mnemonic | Retry value | Notes | +|----------------|-------------|-------------------| +| N7 | 2 | Recommended value | +| N8 | 2 | Recommended value | +| N9 | 2 | Recommended value | +| N10 | 2 | Recommended value | +| N11 | 2 | Recommended value | +| N12 | 2 | Recommended value | + +# 20 Procedures for Tunnelling Non-GSM Signalling + +This procedure is used to tunnel non-GSM signalling messages between an MS and a non-GSM MSC/VLR. + +## 20.1 Procedures in the non-GSM MSC/VLR + +When the non-GSM MSC/VLR has a message to be tunnelled to an MS, whose Gs state is not Gs-NULL, it shall send a BSSAP+-DOWNLINK-TUNNEL-REQUEST message to the SGSN associated with the MS. If LLC ciphering is required, the cipher request field E shall be set to 1. The Tunnel Priority field for the payload shall be set as required. On receiving a BSSAP+-UPLINK-TUNNEL-REQUEST message from an SGSN, the action taken by the non-GSM MSC/VLR is technology dependent. + +## 20.2 Procedures in the SGSN + +A message received by the SGSN from an MS or sent by the SGSN to an MS on one of the Tunneling of Messages (TOM) LLC SAPs is called a *TOM Protocol Envelope* (see 3GPP TS 44.064 [12]). The *TOM Protocol Envelope* is composed of the *TOM Protocol Header* immediately followed by a *Message Capsule*. + +Upon receipt of a *TOM Protocol Envelope* with a *TOM Protocol Header* indicating the presence of one or more non-GSM signalling messages, the SGSN shall determine the non-GSM MSC/VLR to which the *Message Capsule* in the *TOM Protocol Envelope* shall be forwarded. The SGSN shall make this determination based upon the RAI of the MS, the *TOM Protocol Discriminator* field in the *TOM Protocol Header*, and *TOM Protocol Discriminator* specific information in the remaining octets (if any) in the *TOM Protocol Header*. The SGSN shall then forward a BSSAP+-UPLINK-TUNNEL-REQUEST message to the selected non-GSM MSC/VLR with the received *Message Capsule* in the *Tunnel Payload* field. The *Protocol Discriminator* field in the BSSAP+-UPLINK-TUNNEL-REQUEST message shall be set based on the *TOM Protocol Discriminator* in the *TOM Protocol Envelope*. *Tunnel Priority* field in the BSSAP+-UPLINK-TUNNEL-REQUEST message shall be set based on the LLC SAP on which the *TOM Protocol Envelope* was received. The E field shall be set to 1 if the *TOM Protocol Envelope* was received by the LLC in ciphered form, otherwise it shall be set to 0. + +Upon receipt of a BSSAP+-DOWNLINK-TUNNEL-REQUEST message from a non-GSM MSC/VLR, the SGSN shall construct a *TOM Protocol Envelope* by mapping the *Tunnel Payload* field to the *Message Capsule* portion of the *TOM Protocol Envelope*. The *TOM Protocol Header* shall be constructed based on the *Protocol Discriminator* in the BSSAP+-DOWNLINK-TUNNEL-REQUEST message. The SGSN shall then send the *TOM Protocol Envelope* to the MS on a specific LLC SAP. That LLC SAP shall be determined by the *Tunnel Priority* field in the BSSAP+-DOWNLINK-TUNNEL-REQUEST message. LLC ciphering shall be enabled or disabled based upon the value of the *E* field in this message. If the SGSN is unable to send the *TOM Protocol Envelope* to the indicated MS for any reason, including the inability to accommodate the ciphering request as indicated in the BSSAP+-DOWNLINK-TUNNEL-REQUEST message, then it shall send a BSSAP+-MOBILE-STATUS message to the non-GSM MSC/VLR with an appropriate *Gs Cause* code. + +The association between the LLC SAPs and the *Tunnel Priority* shall be as in the following table, where 00 is top-most priority and 11 is lowest priority. + +**Table 20.1: Association between Tunnel Priority and LLC SAPs** + +| Tunnel Priority | LLC SAP | +|-----------------|-------------| +| 00 | TOM2 | +| 01 | Not defined | +| 10 | TOM8 | +| 11 | Not defined | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29061/raw.md b/marked/Rel-18/29_series/29061/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6427a342243946ca8cfc12ad1e64d175209d3c41 --- /dev/null +++ b/marked/Rel-18/29_series/29061/raw.md @@ -0,0 +1,7134 @@ + + +# 3GPP TS 29.061 V18.1.0 (2023-06) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above it and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +## --- **Keywords** + +UMTS, GSM, LTE, packet mode, interworking, +PLMN, PDN + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles – Sophia Antipolis +Valbonne – France +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------------------------|----| +| Foreword ..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions and abbreviations ..... | 13 | +| 3.1 Definitions..... | 13 | +| 3.2 Abbreviations ..... | 14 | +| 3.3 Symbols..... | 15 | +| 4 Network characteristics..... | 16 | +| 4.1 Key characteristics of PLMN..... | 16 | +| 4.2 Key characteristics of PSDN..... | 16 | +| 4.3 Key characteristics of IP Networks..... | 16 | +| 5 Interworking Classifications ..... | 16 | +| 5.1 Service Interworking..... | 16 | +| 5.2 Network Interworking..... | 16 | +| 5.3 Numbering and Addressing..... | 16 | +| 6 Access reference configuration..... | 17 | +| 6.1 General ..... | 17 | +| 6.2 Access Interfaces and Reference Points for non-EPC based Packet Domain..... | 17 | +| 6.3 Access Interfaces and Reference Points for EPC based Packet Domain ..... | 17 | +| 7 Interface to Packet Domain Bearer Services..... | 18 | +| 7.1 A/Gb mode ..... | 18 | +| 7.2 Iu mode..... | 18 | +| 7.3 Interface to EPC-based Packet Domain Bearer Services ..... | 18 | +| 8 Subscription checking..... | 19 | +| 8A Prevention of IP spoofing ..... | 19 | +| 9 Message Screening..... | 19 | +| 10 Interworking with PSDN (X.75/X.25)..... | 19 | +| 11 Interworking with PDN (IP) ..... | 19 | +| 11.1 General ..... | 19 | +| 11.2 PDN Interworking Model..... | 19 | +| 11.2.1 Access to Internet, Intranet or ISP through Packet Domain..... | 21 | +| 11.2.1.1 Transparent access to the Internet..... | 21 | +| 11.2.1.2 IPv4 Non Transparent access to an Intranet or ISP ..... | 22 | +| 11.2.1.2.1 non-EPC based IPv4 Non Transparent access ..... | 22 | +| 11.2.1.2.2 EPC based IPv4 Non Transparent access..... | 25 | +| 11.2.1.3 IPv6 Non Transparent access to an Intranet or ISP ..... | 28 | +| 11.2.1.3.1 IPv6 PDP Context Activation ..... | 28 | +| 11.2.1.3.1a IPv6 EPC based Bearer Activation ..... | 31 | +| 11.2.1.3.2 IPv6 Stateless Address Autoconfiguration..... | 34 | +| 11.2.1.3.2a IPv6 Stateless Address Autoconfiguration for EPC ..... | 35 | +| 11.2.1.3.3 IPv6 Stateful Address Autoconfiguration ..... | 38 | +| 11.2.1.3.4 IPv6 Router Configuration Variables..... | 38 | +| 11.2.1.3.5 IPv6 Prefix Delegation via DHCPv6 ..... | 39 | +| 11.2.1.4 Access to Internet, Intranet or ISP with Mobile IPv4..... | 39 | +| 11.2.1.5 IP Fragmentation Across Gi/Sgi ..... | 42 | +| 11.2.1.6 Support for CUPS across SGi..... | 42 | +| 11.2.1.7 Support L2TP for CUPS across SGi..... | 43 | +| 11.2.2 Access to networks handling Non-IP data services through Packet Domain..... | 45 | +| 11.3 Numbering and Addressing..... | 46 | +| 11.4 Charging..... | 47 | + +| | | | +|------------|-------------------------------------------------------------------------------------|----| +| 11.5 | Domain Name System Server (DNS Server) ..... | 47 | +| 11.6 | Screening..... | 47 | +| 11.7 | IP Multicast access ..... | 47 | +| 11.8 | Non-IP data transfering over SGi..... | 48 | +| 11.8.1 | General ..... | 48 | +| 11.8.2 | Gi/SGi PtP tunnelling based on UDP/IP ..... | 48 | +| 11.8.3 | Other SGi PtP tunnelling mechanisms ..... | 50 | +| 11.9 | Transport Level Marking ..... | 50 | +| 12 | Interworking with PDN (PPP) ..... | 50 | +| 12.1 | General ..... | 50 | +| 12.2 | PDN Interworking Model..... | 50 | +| 12.2.1 | Virtual dial-up- and direct Access to PDNs, or ISPs through Packet Domain..... | 51 | +| 12.2.1.1 | Procedural description ..... | 52 | +| 13 | Interworking with PDN (DHCP) ..... | 53 | +| 13.1 | General ..... | 53 | +| 13.2 | PDN Interworking Model of GGSN for DHCP ..... | 54 | +| 13.2.1 | Address allocation by the Intranet or ISP..... | 55 | +| 13.2.1.1 | Address allocation using DHCPv4..... | 55 | +| 13.2.1.2 | Void. .... | 56 | +| 13.2.2 | Other configuration by the Intranet or ISP (IPv6 only)..... | 56 | +| 13.3 | PDN Interworking Model of P-GW..... | 57 | +| 13.3.1 | Address allocation by the Intranet or ISP..... | 58 | +| 13.3.1.1 | IPv4 Address allocation and IPv4 parameter configuration via DHCPv4..... | 58 | +| 13.3.1.2 | IPv6 Prefix allocation via IPv6 stateless address autoconfiguration via DHCPv6..... | 59 | +| 13.3.1.3 | IPv6 parameter configuration via stateless DHCPv6 ..... | 59 | +| 13a | Interworking with IMS..... | 60 | +| 13a.1 | General ..... | 60 | +| 13a.2 | IMS Interworking Model ..... | 60 | +| 13a.2.1 | IMS Specific Configuration in the GGSN/P-GW ..... | 61 | +| 13a.2.2 | IMS Specific Procedures in the GGSN/P-GW ..... | 61 | +| 13a.2.2.1 | Request for Signalling Server Address..... | 61 | +| 13a.2.2.1a | Failure of Signalling Server Address..... | 62 | +| 13a.2.2.2 | Establishment of a PDP Context/EPS Bearer for Signalling ..... | 62 | +| 13a.2.2.3 | Creation of a PDP Context/EPS Bearer for IMS Media Flows ..... | 63 | +| 13b | Interworking with BM-SC in EPS ..... | 63 | +| 13b.1 | General ..... | 63 | +| 13b.2 | BM-SC interworking model of MBMS GW..... | 63 | +| 13b.3 | Forwarding of user plane packets at the MBMS GW ..... | 65 | +| 14 | Internet Hosted Octet Stream Service (IHOSS)..... | 65 | +| 15 | Interworking between Packet Domains ..... | 65 | +| 15.1 | Security Agreements ..... | 66 | +| 15.2 | Routing protocol agreements ..... | 66 | +| 15.3 | Charging agreements..... | 66 | +| 16 | Usage of RADIUS on Gi/Sgi interface ..... | 66 | +| 16.1 | RADIUS Authentication and Authorization ..... | 66 | +| 16.2 | RADIUS Accounting ..... | 67 | +| 16.3 | Authentication and accounting message flows on Gi interface ..... | 68 | +| 16.3.1 | IP PDP type ..... | 68 | +| 16.3.2 | PPP PDP type ..... | 70 | +| 16.3.3 | Accounting Update..... | 71 | +| 16.3.4 | AAA-Initiated PDP context termination ..... | 72 | +| 16.3a | Authentication and accounting message flows on Sgi interface..... | 73 | +| 16.3a.1 | Authentication, Authorization and Accounting procedures ..... | 73 | +| 16.3a.2 | Accounting Update..... | 75 | +| 16.3a.3 | AAA-Initiated Bearer termination..... | 76 | +| 16.4 | List of RADIUS attributes..... | 77 | +| 16.4.1 | Access-Request message (sent from GGSN/P-GW to AAA server) ..... | 77 | + +| | | | +|----------|-----------------------------------------------------------------------------|-----| +| 16.4.2 | Access-Accept (sent from AAA server to GGSN/P-GW)..... | 79 | +| 16.4.3 | Accounting-Request START (sent from GGSN/P-GW to AAA server)..... | 81 | +| 16.4.4 | Accounting Request STOP (sent from GGSN/P-GW to AAA server) ..... | 82 | +| 16.4.5 | Accounting Request ON (optionally sent from GGSN/P-GW to AAA server)..... | 84 | +| 16.4.6 | Accounting Request OFF (optionally sent from GGSN/P-GW to AAA server) ..... | 84 | +| 16.4.7 | Sub-attributes of the 3GPP Vendor-Specific attribute ..... | 85 | +| 16.4.7.1 | Presence of the 3GPP Vendor-Specific attribute in RADIUS messages..... | 85 | +| 16.4.7.2 | Coding 3GPP Vendor-Specific RADIUS attributes ..... | 90 | +| 16.4.8 | Accounting Request Interim-Update (sent from GGSN/P-GW to AAA server) ..... | 108 | +| 16.4.9 | Disconnect Request (optionally sent from AAA server to GGSN/P-GW) ..... | 110 | +| 16a | Usage of Diameter on Gi/Sgi interface ..... | 111 | +| 16a.1 | Diameter Authentication and Authorization ..... | 111 | +| 16a.2 | Diameter Accounting ..... | 112 | +| 16a.3 | Authentication and accounting message flows on Gi interface ..... | 113 | +| 16a.3.1 | IP PDP type ..... | 113 | +| 16a.3.2 | PPP PDP type ..... | 114 | +| 16a.3.3 | Accounting Update..... | 117 | +| 16a.3.4 | Server-Initiated PDP context termination ..... | 117 | +| 16a.3a | Authentication and accounting message flows on Sgi interface..... | 118 | +| 16a.3a.1 | Authentication, Authorization and Accounting procedures ..... | 118 | +| 16a.3a.2 | Accounting Update..... | 120 | +| 16a.3a.3 | Server-Initiated Bearer termination ..... | 121 | +| 16a.4 | Gi/Sgi Diameter messages ..... | 122 | +| 16a.4.1 | AAR Command ..... | 122 | +| 16a.4.2 | AAA Command..... | 123 | +| 16a.4.3 | ACR Command ..... | 124 | +| 16a.4.4 | ACA Command ..... | 126 | +| 16a.4.5 | STR Command ..... | 126 | +| 16a.4.6 | STA Command..... | 126 | +| 16a.4.7 | ASR Command..... | 127 | +| 16a.4.8 | ASA Command ..... | 127 | +| 16a.5 | Gi/Sgi specific AVPs ..... | 128 | +| 16a.6 | Gi/Sgi specific Experimental-Result-Code AVP ..... | 131 | +| 16a.7 | Gi/Sgi re-used AVPs ..... | 131 | +| 17 | Usage of Diameter on Gmb interface ..... | 131 | +| 17.1 | MBMS user authorisation ..... | 132 | +| 17.2 | MBMS service registration / de-registration..... | 132 | +| 17.3 | MBMS session start / update/ stop..... | 132 | +| 17.4 | MBMS user deactivation..... | 132 | +| 17.5 | Message flows..... | 133 | +| 17.5.1 | Service activation ..... | 133 | +| 17.5.2 | Session start procedure ..... | 134 | +| 17.5.3 | Session stop procedure ..... | 135 | +| 17.5.4 | Registration procedure..... | 135 | +| 17.5.5 | De-registration procedure (GGSN initiated) ..... | 136 | +| 17.5.6 | De-registration procedure (BM-SC initiated)..... | 136 | +| 17.5.7 | Service deactivation..... | 137 | +| 17.5.7.1 | BM-SC Initiated Multicast Service Deactivation ..... | 138 | +| 17.5.8 | Trace Session Activation procedure ..... | 138 | +| 17.5.9 | Trace Session Deactivation procedure ..... | 139 | +| 17.5.10 | MBMS UE Context Modification Procedure ..... | 139 | +| 17.5.11 | Session Update Procedure ..... | 140 | +| 17.5.12 | MBMS broadcast session termination (GGSN initiated) ..... | 141 | +| 17.6 | Gmb Messages ..... | 141 | +| 17.6.1 | AAR Command ..... | 142 | +| 17.6.2 | AAA Command..... | 143 | +| 17.6.3 | STR Command ..... | 143 | +| 17.6.4 | STA Command..... | 144 | +| 17.6.5 | Re-Auth-Request Command ..... | 144 | +| 17.6.6 | RE-Auth-Answer Command ..... | 146 | + +| | | | +|----------|-----------------------------------------------------------------------|-----| +| 17.6.7 | Abort-Session-Request Command ..... | 146 | +| 17.6.8 | Abort-Session-Answer Command..... | 146 | +| 17.7 | Gmb specific AVPs..... | 147 | +| 17.7.0 | General ..... | 147 | +| 17.7.1 | 3GPP-Vendor-Specific AVP ..... | 149 | +| 17.7.2 | TMGI AVP ..... | 149 | +| 17.7.3 | Required-MBMS-Bearer-Capabilities AVP..... | 149 | +| 17.7.4 | Void ..... | 149 | +| 17.7.5 | MBMS-StartStop-Indication AVP ..... | 149 | +| 17.7.6 | MBMS-Service-Area AVP..... | 150 | +| 17.7.7 | MBMS-Session-Duration AVP ..... | 150 | +| 17.7.8 | Alternative-APN AVP..... | 150 | +| 17.7.9 | MBMS-Service-Type AVP ..... | 150 | +| 17.7.10 | MBMS-2G-3G-Indicator AVP..... | 151 | +| 17.7.11 | MBMS-Session-Identity AVP..... | 151 | +| 17.7.12 | RAI AVP ..... | 151 | +| 17.7.13 | Additional-MBMS-Trace-Info AVP ..... | 151 | +| 17.7.14 | MBMS-Time-To-Data-Transfer AVP..... | 151 | +| 17.7.15 | MBMS-Session-Repetition-Number AVP ..... | 152 | +| 17.7.16 | MBMS-Required-QoS AVP..... | 152 | +| 17.7.17 | MBMS-Counting-Information AVP ..... | 152 | +| 17.7.18 | MBMS-User-Data-Mode-Indication AVP ..... | 152 | +| 17.7.19 | MBMS-GGSN-Address AVP ..... | 153 | +| 17.7.20 | MBMS-GGSN-Ipv6-Address AVP..... | 153 | +| 17.7.21 | MBMS-BMSC-SSM-IP-Address AVP..... | 153 | +| 17.7.22 | MBMS-BMSC-SSM-IPv6-Address AVP..... | 153 | +| 17.7.23 | MBMS-Flow-Identifier AVP ..... | 153 | +| 17.7.24 | CN-IP-Multicast-Distribution AVP..... | 153 | +| 17.7.25 | MBMS-HC-Indicator AVP ..... | 153 | +| 17.7a | Gmb re-used AVPs..... | 153 | +| 17.8 | Gmb specific Experimental-Result-Code AVP values ..... | 154 | +| 17.8.0 | General ..... | 154 | +| 17.8.1 | Success ..... | 154 | +| 17.8.2 | Permanent Failures ..... | 154 | +| 17.8.3 | Transient Failures ..... | 155 | +| 18 | Usage of RADIUS at the Pk Reference Point..... | 155 | +| 18.1 | General ..... | 155 | +| 18.2 | Radius Profile for Pk Reference Point ..... | 155 | +| 18.3 | Interconnecting the Presence Network Agent and the GGSN ..... | 155 | +| 19 | Usage of Diameter on Mz interface ..... | 156 | +| 19.1 | Introduction ..... | 156 | +| 19.2 | Call flows in roaming scenarios..... | 156 | +| 19.2.1 | Service activation ..... | 156 | +| 19.2.1.1 | Service Provided by the BM-SC in Home PLMN..... | 156 | +| 19.2.1.2 | Service Provided by the BM-SC in visited PLMN..... | 158 | +| 19.2.2 | Service deactivation..... | 159 | +| 19.2.2.1 | Service Provided by the BM-SC in home PLMN..... | 159 | +| 19.2.2.2 | Service Provided by the BM-SC in visited PLMN..... | 160 | +| 19.2.2.3 | BM-SC in the home PLMN initiated multicast service deactivation ..... | 161 | +| 19.3 | Mz messages ..... | 161 | +| 19.4 | Mz specific AVPs..... | 161 | +| 19.5 | Mz specific Experimental-Result-Code AVP values..... | 162 | +| 19.5.1 | Success ..... | 162 | +| 19.5.2 | Permanent Failures ..... | 162 | +| 19.5.3 | Transient Failures ..... | 162 | +| 20 | Usage of Diameter on SGmb interface ..... | 162 | +| 20.1 | General ..... | 162 | +| 20.2 | MBMS session start / update/ stop..... | 163 | +| 20.2A | MBMS heartbeat ..... | 163 | +| 20.3 | Message flows ..... | 163 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------|------------| +| 20.3.1 | Session start procedure ..... | 163 | +| 20.3.2 | Session update procedure ..... | 164 | +| 20.3.3 | Session stop procedure ..... | 165 | +| 20.3.4 | MBMS session termination (MBMS GW initiated)..... | 165 | +| 20.3.5 | MBMS heartbeat procedure ..... | 166 | +| 20.4 | SGmb Messages ..... | 167 | +| 20.4.1 | Re-Auth-Request Command ..... | 167 | +| 20.4.2 | RE-Auth-Answer Command ..... | 169 | +| 20.4.3 | Session-Termination-Request Command..... | 170 | +| 20.4.4 | Session-Termination-Answer Command ..... | 170 | +| 20.4.5 | Abort-Session-Request Command ..... | 170 | +| 20.4.6 | Abort-Session-Answer Command..... | 171 | +| 20.5 | SGmb re-used AVPs ..... | 171 | +| 20.5a | SGmb specific AVPs..... | 174 | +| 20.5a.1 | MBMS-Access-Indicator AVP..... | 174 | +| 20.5a.2 | MBMS-GW-SSM-IP-Address AVP ..... | 175 | +| 20.5a.3 | MBMS-GW-SSM-IPv6-Address AVP ..... | 175 | +| 20.5a.4 | MBMS-BMSC-SSM-UDP-Port AVP ..... | 175 | +| 20.5a.5 | MBMS-GW-UDP-Port AVP..... | 175 | +| 20.5a.6 | MBMS-GW-UDP-Port-Indicator AVP ..... | 175 | +| 20.5a.7 | MBMS-Data-Transfer-Start AVP ..... | 175 | +| 20.5a.8 | MBMS-Data-Transfer-Stop AVP..... | 175 | +| 20.5a.9 | MBMS-Flags AVP ..... | 175 | +| 20.5a.10 | Restart-Counter AVP..... | 176 | +| 20.5a.11 | Diagnostic-Info AVP..... | 176 | +| 20.5a.12 | MBMS-Cell-List AVP..... | 176 | +| 20.6 | SGmb specific Experimental-Result-Code AVP values ..... | 177 | +| 20.7 | Use of the Supported-Features AVP on the SGmb reference point..... | 177 | +| Annex A (informative): | Interworking PCS1900 with PSDNs ..... | 179 | +| Annex B (normative): | Rate control related to Cellular Internet Of Things (CIoT) optimisations ..... | 180 | +| B.1 | General..... | 180 | +| B.2 | Support of rate control of user data..... | 180 | +| B.2.0 | General ..... | 180 | +| B.2.1 | APN Rate Control in the PGW ..... | 180 | +| B.2.2 | Serving PLMN Rate Control information handling in the PGW ..... | 181 | +| Annex C (informative): | Change history..... | 182 | + +--- + +## Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document describes the network interworking for the Packet Domain. Interworking to various external networks is defined together with the interworking for data forwarding while subscribers roam within the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +# 1 Scope + +The present document defines the requirements for Packet Domain interworking between a: + +- a) PLMN and PDN; +- b) PLMN and PLMN. + +The present document is valid for a PLMN in A/Gb mode as well as for a PLMN in Iu mode. If text applies only for one of these systems it is explicitly mentioned by using the terms "A/Gb mode" and "Iu mode". Please note, that the A interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. + +For inter-working between EPC PLMN and external networks, the present document is valid for both 3GPP accesses and non-3GPP accesses. + +The present document also defines, in clause 17, the protocol for the Gmb interface, in clause 20, the protocol for the SGmb interface, and in clause 19, the protocol for the Mz interface. + +The present document also defines, in clause 18, the usage of Radius at the Pk Reference Point between the GGSN and the Presence Network Agent. + +The term "Packet Domain" includes both EPC based and non-EPC based Packet Domains. + +The present document also defines the specific requirements for rate control related to CIoT optimisations. + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] Void. +- [2] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service Description; Stage 1". +- [3] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2". +- [4] Void. +- [5] Void. +- [6] Void. +- [7] Void. +- [8] Void. +- [9] Void. +- [10] 3GPP TS 27.060: "Packet Domain; Mobile Station (MS) supporting Packet Switched services". +- [11] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [12] Void. + +- [13] Void. +- [14] Void. +- [15] IETF RFC 768 (1980): "User Datagram Protocol" (STD 6). +- [16] IETF RFC 791 (1981): "Internet Protocol" (STD 5). +- [17] IETF RFC 792 (1981): "Internet Control Message Protocol" (STD 5). +- [18] IETF RFC 793 (1981): "Transmission Control Protocol" (STD 7). +- [19] IETF RFC 1034 (1987): "Domain names – concepts and facilities" (STD 7). +- [20] Void. +- [21a] IETF RFC 1661 (1994): "The Point-to-Point Protocol (PPP)" (STD 51). +- [21b] IETF RFC 1662 (1994): "PPP in HDLC-like Framing". +- [22] IETF RFC 1700 (1994): "Assigned Numbers" (STD 2). +- [23] 3GPP TS 44.008: "Mobile radio interface layer 3 specification; Core Network protocols; Stage 3". +- [24] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface". +- [25] IETF RFC 2794 (2000): "Mobile IP Network Address Identifier Extension for IPv4", P. Calhoun, C. Perkins. +- [26] IETF RFC 2131 (1997): "Dynamic Host Configuration Protocol". +- [27] IETF RFC 1542 (1993): "Clarification and Extensions for the Bootstrap Protocol". +- [28] Void. +- [29] Void. +- [30] IETF RFC 3344 (2002): "IP Mobility Support", C. Perkins. +- [31] IETF RFC 2486 (1999): "The Network Access Identifier", B. Aboba and M. Beadles. +- [32] Void. +- [33] Void. +- [34] Void. +- [35] Void. +- [36] Void. +- [37] IETF RFC 2290 (1998): "Mobile-IPv4 Configuration Option for PPP IPCP", J. Solomon, S. Glass. +- [38] IETF RFC 2865 (2000): "Remote Authentication Dial In User Service (RADIUS)", C. Rigney, S. Willens, A. Rubens, W. Simpson. +- [39] IETF RFC 2866 (2000): "RADIUS Accounting", C. Rigney, Livingston. +- [40] 3GPP TS 23.003: "Numbering, addressing and identification". +- [41] IETF RFC 3576 (2003): "Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)", M.Chiba, M.Eklund, D.Mitton, B.Aboba. +- [42] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [43] Void. +- [44] Void. + +- [45] IETF RFC 3118 (2001): "Authentication for DHCP Messages", R. Droms, W. Arbaugh. +- [46] IETF RFC 3315 (2003) "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", R. Droms, J. Bound, B. Volz, T. Lemon, C. Perkins, M. Carney. +- [47] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP". +- [48] IETF RFC 2710 (1999): "Multicast Listener Discovery (MLD) for IPv6", S. Deering, W. Fenner, B. Haberman. +- [49] IETF RFC 2460 (1998): "Internet Protocol, Version 6 (IPv6) Specification", S.Deering, R.Hinden. +- [50] IETF RFC 3162 (2001): "RADIUS and IPv6", B. Adoba, G. Zorn, D. Mitton. +- [51] IETF RFC 2548 (1999): "Microsoft Vendor-specific RADIUS Attributes", G.Zorn. +- [52] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [53] Void +- [54] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network protocols; Stage 3". +- [55] Void. +- [56] Void +- [57] Void. +- [58] IETF RFC 1035 (1987): "Domain names – implementation and specification" (STD 13). +- [59] Void. +- [60] IETF RFC 1771 (1995): "A Border Gateway Protocol 4 (BGP-4)". +- [61] IETF RFC 1825 (1995): "Security Architecture for the Internet Protocol". +- [62] IETF RFC 1826 (1995): "IP Authentication Header". +- [63] IETF RFC 1827 (1995): "IP Encapsulating Security Payload (ESP)". +- [64] Void. +- [65] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS) Architecture and Functional Description". +- [66] Void. +- [67] Void. +- [68] 3GPP TS 23.141: "Presence Service; Architecture and functional description". +- [69] 3GPP TS 32.422: "Subscriber and equipment trace: Trace Control and Configuration Management". +- [70] 3GPP TS 48.018: "Base Station System (BSS) – Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [71] 3GPP TS 23.107: "Quality of Service (QoS) Concept and Architecture". +- [72] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN)". +- [73] IETF RFC 4604 (2006): "Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific Multicast". +- [74] IETF RFC 4607 (2006): "Source-Specific Multicast for IP". +- [75] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". + +- [76] 3GPP TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping". +- [77] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [78] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses". +- [79] IETF RFC 4039 (2005): "Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)". +- [80] IETF RFC 3736 (2004): "Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6". +- [81] 3GPP TS 29.274: "Evolved GPRS Tunnelling Protocol for EPS (GTPv2)". +- [82] IETF RFC 4291 (2006): "IP Version 6 Addressing Architecture". +- [83] IETF RFC 4862 (2007): "IPv6 Stateless Address Autoconfiguration". +- [84] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)". +- [85] IETF RFC 2132 (1997): "DHCP Options and BOOTP Vendor Extensions". +- [86] IETF RFC 3361 (2002): "Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers". +- [87] IETF RFC 3646 (2003): "DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)". +- [88] IETF RFC 3319 (2003): "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers". +- [89] IETF RFC 4861 (2007): "Neighbor Discovery for IP Version 6 (IPv6)". +- [90] 3GPP TS 23.203: "Policy and charging control architecture". +- [91] IETF RFC 4739 (2006): "Multiple Authentication Exchanges in the Internet Key Exchange (IKEv2) Protocol". +- [92] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling". +- [93] IETF RFC 5176 (2008): "Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)". +- [94] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [95] 3GPP TS 23.380: "IMS Restoration Procedures". +- [96] 3GPP TS 29.303: "Domain Name System Procedures; Stage 3". +- [97] IETF RFC 4818 (2007): "RADIUS Delegated-IPv6-Prefix Attribute". +- [98] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description". +- [99] 3GPP TS 23.221: "Architectural requirements". +- [100] 3GPP TS 23.682: "Architecture Enhancements to facilitate communications with Packet Data Networks and Applications". +- [101] 3GPP TS 29.336: "Home Subscriber Server (HSS) Diameter interfaces for interworking with packet data networks and applications". +- [102] IETF RFC 4282 (2005): "The Network Access Identifier". + +- [103] 3GPP TS 29.275: "Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3". +- [104] 3GPP TS 23.007: "Restoration procedures". +- [105] 3GPP TS 29.229: "Cx and Dx interfaces based on Diameter protocol; Protocol details". +- [106] 3GPP TS 25.446: "MBMS synchronisation protocol (SYNC)". +- [107] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP) specification". +- [108] Void. +- [109] IETF RFC 4960 (2007): "Stream Control Transmission Protocol". +- [110] 3GPP TS 29.128: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications ". +- [111] IETF RFC 6733: "Diameter Base Protocol". +- [112] 3GPP TS 23.285: "Architecture Enhancements for V2X services". +- [113] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE); MB2 Reference point; Stage 3". +- [114] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane of EPC Nodes; Stage 3". +- [115] 3GPP TS 38.413: "NG Radio Access Network (NG-RAN); NG Application Protocol (NGAP)". +- [116] IETF RFC 2869: "RADIUS Extensions". +- [117] 3GPP TS 23.214: "Architecture enhancements for control and user plane separation of EPC nodes; Stage 2". +- [118] IETF RFC 2661: " Layer Two Tunneling Protocol "L2TP". +- [119] IETF RFC 2868: "RADIUS Attributes for Tunnel Protocol Support". +- [120] IETF RFC 7155: "Diameter Network Access Server Application". +- [121] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point". + +--- + +## 3 Definitions and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 22.060 [2], 3GPP TS 23.060 [3], 3GPP TS 23.401 [77], 3GPP TS 23.402 [78] and the following apply: + +**2G- / 3G-:** prefixes 2G- and 3G- refers to functionality that supports only A/Gb mode GPRS or Iu mode, respectively, e.g., 2G-SGSN refers only to the A/Gb mode GPRS functionality of an SGSN. When the prefix is omitted, reference is made independently from the A/Gb mode GPRS or Iu mode functionality. + +**A/Gb mode:** indicates that the text applies only to a system or sub-system which operate in A/Gb mode of operation, i.e. with a functional division that is in accordance with the use of an A or a Gb interface between the radio access network and the core network. + +**Iu mode:** indicates that the text applies only to a system or a sub-system which operates in Iu mode of operation, i.e. with a functional division that is in accordance with the use of an Iu-CS or Iu-PS interface between the radio access network and the core network. + +**IP-CAN session:** association between a UE and an IP network + +The association is identified by a UE represented by an IPv4 address and/or an IPv6 prefix together with a UE identity information, if available, and a PDN identity (e.g. APN). An IP-CAN session incorporates one or more IP-CAN bearers. Support for multiple IP-CAN bearers per IP-CAN session is IP-CAN specific. An IP-CAN session exists as long as the related UE IPv4 address and/or IPv6 prefix are established and announced to the IP network. + +**EPC based Packet Domain:** Packet domain which makes use of EPC nodes (e.g. P-GW, S-GW, etc.). + +**Packet Domain Bearer:** A transmission path between a UE and a GGSN/P-GW, terminating at the User Plane protocol stack under the IP layers. + +**NR RedCap:** a 3GPP RAT type Identifier used in the Core Network only, which is a sub-type of NR RAT type, and defined to identify in the Core Network the NR when used by a UE indicating NR Reduced Capability. + +## 3.2 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TR 21.905 [42]. For the purposes of the present document, the following additional abbreviations apply: + +| | | +|---------|-----------------------------------------------| +| 5QI | 5G QoS Identifier | +| AMBR | Aggregate Maximum Bit Rate | +| APN | Access Point Name | +| ARP | Allocation and Retention Priority | +| ATM | Asynchronous Transfer Mode | +| APCO | Additional Protocol Configuration Options | +| BG | Border Gateway | +| BM-SC | Broadcast/Multicast Service Centre | +| CHAP | Challenge Handshake Authentication Protocol | +| CIoT | Cellular Internet of Things | +| DHCP | Dynamic Host Configuration Protocol | +| DHCPv6 | Dynamic Host Configuration Protocol version 6 | +| DNS | Domain Name System | +| DSMIPv6 | Dual-Stack MIPv6 | +| DVMRP | Distance Vector Multicast Routing Protocol | +| EPC | Evolved Packet Core | +| ePDG | Evolved Packet Data Gateway | +| EPS | Evolved Packet System | +| FQDN | Fully Qualified Domain Name | +| GBR | Guaranteed Bit Rate | +| GFBR | Guaranteed Flow Bit Rate | +| GGSN | Gateway GPRS Support Node | +| GTP-U | GPRS Tunnelling Protocol for user plane | +| ICMP | Internet Control Message Protocol | +| IETF | Internet Engineering Task Force | +| IGMP | Internet Group Management Protocol | +| IMS | IP Multimedia Subsystem | +| IP | Internet Protocol | +| IPCP | IP Control Protocol (PPP NCP for IPv4) | +| IPv4 | Internet Protocol version 4 | +| IPv6 | Internet Protocol version 6 | +| IPv6CP | IPv6 Control Protocol (PPP NCP for IPv6) | +| ISDN | Integrated Services Digital Network | +| ISP | Internet Service Provider | +| L2TP | Layer Two Tunneling Protocol | +| LAC | L2TP Access Concentrator | +| LAN | Local Area Network | +| LNS | L2TP Network Server | +| MBMS | Multimedia Broadcast/Multicast Service | +| MBR | Maximum Bit Rate | +| MFBR | Maximum Flow Bit Rate | +| MIP | Mobile IP | +| MLD | Multicast Listener Discovery | + +| | | +|--------|----------------------------------------------| +| MME | Mobility Management Entity | +| MOSPF | Multicast Open Shortest Path First | +| MS | Mobile Station | +| MT | Mobile Terminal | +| MTC | Machine Type Communication | +| MTU | Maximum Transfer Unit | +| NAI | Network Access Identifier | +| NCGI | NR Cell Global Identity | +| PAP | Password Authentication Protocol | +| PCC | Policy and Charging Control | +| PCO | Protocol Configuration Options | +| PCRF | Policy and Charging Rules Function | +| P-CSCF | Proxy Call Session Control Function | +| PDCP | Packet Data Convergence Protocol | +| PDN | Packet Data Network | +| PDU | Protocol Data Unit | +| P-GW | PDN Gateway | +| PGW-C | PDN Gateway Control plane function | +| PGW-U | PDN Gateway User plane function | +| PIM-SM | Protocol Independent Multicast – Sparse Mode | +| PPP | Point-to-Point Protocol | +| PS | Packet Switched | +| QCI | QoS Class Identifier | +| RADIUS | Remote Authentication Dial In User Service | +| SCEF | Service Capability Exposure Function | +| SGSN | Serving GPRS Support Node | +| S-GW | Serving Gateway | +| SMDS | Switched Multimegabit Data Service | +| SMF | Session Management Function | +| TCP | Transmission Control Protocol | +| TE | Terminal Equipment | +| TEID | Tunnel End-point Identifier | +| TMGI | Temporary Mobile Group Identity | +| TWAN | Trusted WLAN Access Network | +| UDP | User Datagram Protocol | + +### 3.3 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Gb | Interface between an SGSN and a BSC. | +| Gi | Reference point between Packet Domain and an external packet data network. | +| Gmb | Reference point between GGSN and BM-SC. | +| Gn | Interface between two GSNs within the same PLMN. | +| Go | Interface between a GGSN and a PDF. | +| Gp | Interface between two GSNs in different PLMNs. The Gp interface allows support of Packet Domain network services across areas served by the co-operating PLMNs. | +| Gs | Interface between an SGSN and MSC. | +| Iu | Interface between the RNS and the core network. It is also considered as a reference point. | +| Pk | Reference Point between GGSN and Presence Network Agent. | +| R | The reference point between a non-ISDN compatible TE and MT. Typically this reference point supports a standard serial interface. | +| S2a | It provides the user plane with related control and mobility support between trusted non-3GPP IP access and P-GW. | +| S2b | It provides the user plane with related control and mobility support between ePDG and P-GW. | +| S2c | It provides the user plane with related control and mobility support between UE and P-GW. This reference point is implemented over trusted and/or untrusted non-3GPP Access and/or 3GPP access. | +| S5 | Interface between a S-GW and a P-GW within the same PLMN. | +| S8 | Interface between a S-GW and a P-GW in different PLMNs. | +| Sgi | The reference point between the EPC based PLMN and the packet data network. | +| Sgi-mb | The reference point between BM-SC and MBMS GW for MBMS data delivery. | + +| | | +|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SGmb | The reference point for the control plane between BM-SC and MBMS GW. | +| T6a | Reference point used between SCEF and serving MME. | +| T6b | Reference point used between SCEF and serving SGSN. | +| Um | The interface between the MS and the fixed network part in A/Gb mode. The Um interface is the A/Gb mode network interface for providing packet data services over the radio to the MS. The MT part of the MS is used to access the GSM services through this interface. | +| Uu | Interface between the mobile station (MS) and the fixed network part in Iu mode. The Uu interface is the Iu mode network interface for providing packet data services over the radio to the MS. The MT part of the MS is used to access the UMTS services through this interface. | + +--- + +## 4 Network characteristics + +### 4.1 Key characteristics of PLMN + +The PLMN is fully defined in the 3GPP technical specifications. The Packet Domain related key characteristics are found in 3GPP TS 23.060 [3] , 3GPP TS 23.401 [77] and 3GPP TS 23.402 [78]. + +### 4.2 Key characteristics of PSDN + +Void. + +### 4.3 Key characteristics of IP Networks + +The Internet is a conglomeration of networks utilising a common set of protocols. IP protocols are defined in the relevant IETF STD specifications and RFCs. The networks topologies may be based on LANs (e.g. Ethernet), Point to Point leased lines, PSTN, ISDN, X.25 or WANs using switched technology (e.g. SMDS, ATM). + +--- + +## 5 Interworking Classifications + +### 5.1 Service Interworking + +Service interworking is required when the Teleservice at the calling and called terminals are different. For Packet Domain, service interworking is not applicable at the Gi/Sgi reference point. + +### 5.2 Network Interworking + +Network interworking is required whenever a PLMN is involved in communications with another network to provide end-to-end communications. The PLMN shall interconnect in a manner consistent with that of a normal Packet Data Network (type defined by the requirements e.g. IP). Interworking appears exactly like that of Packet Data Networks. + +### 5.3 Numbering and Addressing + +See 3GPP TS 23.003 [40] and the relevant section for IP addressing below. + +## 6 Access reference configuration + +### 6.1 General + +The figures depicted in subclauses 6.2 and 6.3 below are the logical representation of the EPC and the non-EPC based Packet Domains. Physically, an operator's PLMN may consist of both EPC and non-EPC nodes. In other words, for example, an operator's PLMN may have both GGSNs and P-GWs; and a Rel-8 SGSN may initiate PDP context activation procedure via both Gn/Gp and S4/S5/S8 reference points. + +### 6.2 Access Interfaces and Reference Points for non-EPC based Packet Domain + +Figure 1a shows the relationship between the MS, its terminal equipment and the PLMN network in the non-EPC based overall Packet Domain environment. + +![Figure 1a: Non-EPC based Packet Domain Access Interfaces and Reference Points diagram](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +The diagram illustrates the network architecture for a non-EPC based packet domain. On the left, a 'TE' (Terminal Equipment) and an 'MT' (Mobile Terminal) are connected by a solid line. These two components are grouped by a bracket labeled 'MS' (Mobile Station). Above the 'TE' is the 'R reference point'. The 'MT' is connected to a 'Non-EPC Based Packet Domain' (represented by an oval) via the 'Um or Uu' interface. Above the 'Non-EPC Based Packet Domain' is the 'Gi reference point'. Below the 'Non-EPC Based Packet Domain' is 'Packet Domain network 2' (another oval), connected via the 'Gp' interface. To the right of the 'Non-EPC Based Packet Domain' is a stack of circles representing the 'PDN or other network', connected via the 'Gi reference point'. + +Figure 1a: Non-EPC based Packet Domain Access Interfaces and Reference Points diagram + +Figure 1a: Non-EPC based Packet Domain Access Interfaces and Reference Points + +### 6.3 Access Interfaces and Reference Points for EPC based Packet Domain + +Figure 1b shows the relationship between the UE and the EPS network for both the 3GPP access and the non-3GPP access in the EPC based Packet Domain environment. The S8/S2a/S2b interface includes GTP-based and PMIP-based. + +![Figure 1b: EPC based Packet Domain Access Interfaces and Reference Points diagram](9b62a616c7a1097c5da57f001ab6dd64_img.jpg) + +The diagram illustrates the network architecture for an EPC based packet domain. On the left, a 'UE' (User Equipment) is connected to 'EPC Based Packet Domain network 1' (represented by an oval). This network is connected to 'Packet Domain network 2' (another oval) via the 'S8/S2a/S2b/S2c' interface. To the right of 'EPC Based Packet Domain network 1' is a stack of circles representing the 'PDN or other network', connected via the 'SGi' interface. + +Figure 1b: EPC based Packet Domain Access Interfaces and Reference Points diagram + +Figure 1b: EPC based Packet Domain Access Interfaces and Reference Points + +## 7 Interface to Packet Domain Bearer Services + +### 7.1 A/Gb mode + +Figure 2a shows the relationship of the non-EPC based Packet Domain Bearer in A/Gb mode terminating at the SNDCP layer to the rest of the A/Gb mode Packet Domain environment. It is shown for reference purposes only and detailed information can be found in 3GPP TS 23.060 [3]. + +![Figure 2a: User Plane for Packet Domain services in A/Gb mode. This diagram illustrates the protocol stack for user plane data across four main entities: MS (Mobile Station), BSS (Base Station System), SGSN (Serving GPRS Support Node), and GGSN (PDG). The MS stack includes SNDCP, LLC, RLC, MAC, and GSM RF layers. The BSS stack includes RLC, MAC, Network Service, and L1bis layers, with a 'Relay' function between RLC and MAC. The SGSN stack includes SNDCP, LLC, BSSGP, Network Service, and L1bis layers, with a 'Relay' function between SNDCP and LLC. The GGSN stack includes GTP-U, UDP, IP, L2, and L1 layers. Interfaces are labeled: Um between MS and BSS, Gb between BSS and SGSN, Gn between SGSN and GGSN, and Gi at the GGSN output. Access points are shown at the top of the MS and GGSN stacks.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +Figure 2a: User Plane for Packet Domain services in A/Gb mode. This diagram illustrates the protocol stack for user plane data across four main entities: MS (Mobile Station), BSS (Base Station System), SGSN (Serving GPRS Support Node), and GGSN (PDG). The MS stack includes SNDCP, LLC, RLC, MAC, and GSM RF layers. The BSS stack includes RLC, MAC, Network Service, and L1bis layers, with a 'Relay' function between RLC and MAC. The SGSN stack includes SNDCP, LLC, BSSGP, Network Service, and L1bis layers, with a 'Relay' function between SNDCP and LLC. The GGSN stack includes GTP-U, UDP, IP, L2, and L1 layers. Interfaces are labeled: Um between MS and BSS, Gb between BSS and SGSN, Gn between SGSN and GGSN, and Gi at the GGSN output. Access points are shown at the top of the MS and GGSN stacks. + +Figure 2a: User Plane for Packet Domain services in A/Gb mode + +### 7.2 Iu mode + +Figure 2b shows the relationship of the non-EPC based Packet Domain Bearer in Iu mode, terminating at the PDCP layer, to the rest of the Iu mode Packet Domain environment. It is shown for reference purposes only and detailed information can be found in 3GPP TS 23.060 [3]. + +![Figure 2b: User Plane for Packet Domain services in Iu mode. This diagram illustrates the protocol stack for user plane data across four main entities: MS (Mobile Station), RNS (Radio Network System), 3G SGSN (Serving GPRS Support Node), and GGSN (PDG). The MS stack includes PDCP, RLC, MAC, and L1 layers. The RNS stack includes PDCP, RLC, MAC, L1, and ATM layers, with a 'Relay' function between PDCP and RLC. The 3G SGSN stack includes GTP-U, UDP/IP, AAL5, ATM, and L1 layers, with a 'Relay' function between GTP-U and UDP/IP. The GGSN stack includes GTP-U, UDP/IP, L2, and L1 layers. Interfaces are labeled: Uu between MS and RNS, Iu-PS between RNS and 3G SGSN, Gn between 3G SGSN and GGSN, and Gi at the GGSN output. Access points are shown at the top of the MS and GGSN stacks.](124c6108c63173818afb8ed49521e22d_img.jpg) + +Figure 2b: User Plane for Packet Domain services in Iu mode. This diagram illustrates the protocol stack for user plane data across four main entities: MS (Mobile Station), RNS (Radio Network System), 3G SGSN (Serving GPRS Support Node), and GGSN (PDG). The MS stack includes PDCP, RLC, MAC, and L1 layers. The RNS stack includes PDCP, RLC, MAC, L1, and ATM layers, with a 'Relay' function between PDCP and RLC. The 3G SGSN stack includes GTP-U, UDP/IP, AAL5, ATM, and L1 layers, with a 'Relay' function between GTP-U and UDP/IP. The GGSN stack includes GTP-U, UDP/IP, L2, and L1 layers. Interfaces are labeled: Uu between MS and RNS, Iu-PS between RNS and 3G SGSN, Gn between 3G SGSN and GGSN, and Gi at the GGSN output. Access points are shown at the top of the MS and GGSN stacks. + +Figure 2b: User Plane for Packet Domain services in Iu mode + +### 7.3 Interface to EPC-based Packet Domain Bearer Services + +The user plane for EPC based packet domain services can be found in 3GPP TS 23.401 [77], 3GPP TS 23.402 [78] and 3GPP TS 23.060 [3]. + +--- + +## 8 Subscription checking + +The subscription of an MS/UE is checked by the PLMN during IP-CAN session establishment procedure as described in 3GPP TS 23.060 [3], 3GPP TS 23.401 [77] and 3GPP TS 23.402 [78]. The GGSN/P-GW implicitly checks its internal context related to the destination address for each mobile terminated packet. For PDN types other than Non-IP, if there is a context IP-CAN session associated with the IP address the packet shall be forwarded towards the MS/UE; otherwise the packet shall be discarded or rejected depending on the implemented protocol. For PDN type "Non-IP", the packet shall be forwarded towards the MS/UE, discarded or rejected depending on the implemented protocol. + +--- + +## 8A Prevention of IP spoofing + +For PDN types other than "Non-IP", if IP spoofing has to be prevented, the GGSN/P-GW shall verify the source IP address of the IP packets issued by the UE and compare it against the address, IPv4 or IPv6, assigned for the IP-CAN session. If the verification fails for a packet, the GGSN/P-GW shall discard the packets and shall be capable to log the event in the security log against the subscriber information (IMSI/MSISDN). + +--- + +## 9 Message Screening + +Screening functions reside within the Packet Domain as described in 3GPP TS 22.060 [2], 3GPP TS 23.060 [3], 3GPP TS 23.401 [77] and 3GPP TS 23.402 [78]. Screening may be applicable for only certain protocols. Screening is outside the scope of the present document. + +--- + +## 10 Interworking with PSDN (X.75/X.25) + +**Figure 3: Void** + +**Figure 4: Void** + +**Figure 5: Void** + +**Figure 6: Void** + +--- + +## 11 Interworking with PDN (IP) + +### 11.1 General + +Packet Domain shall support interworking with networks based on the Internet Protocol (IP). These interworked networks may be either intranets or the Internet. Packet Domain may also support interworking with networks handling Non-IP data services. + +### 11.2 PDN Interworking Model + +The Packet Domain can interwork with IP networks and networks handling Non-IP data services. When interworking with the IP networks, the Packet Domain can operate IPv4 and/or IPv6. The interworking point with the IP networks or networks handling Non-IP data services is at the Gi and Sgi reference point. Additionally, the interworking point with network handling Non-IP data services may also be the T6a (T6) reference point for Control Plane CIoT EPS Optimizations (see 3GPP TS 29.128 [110]). These interworking points are shown in figure 7. + +![Figure 7: IP network interworking diagram showing a UE connected to a Packet Domain Network, which is connected to two External Network(s) via Gi/SGi and T6 interfaces.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +The diagram illustrates IP network interworking. On the left, a 'UE' (User Equipment) is connected to a 'Packet Domain Network'. The 'Packet Domain Network' is connected to two 'External Network(s)' on the right. The connection to the top 'External Network(s)' is labeled 'Gi/SGi' and the connection to the bottom 'External Network(s)' is labeled 'T6'. Both connections are shown with double-headed arrows. + +Figure 7: IP network interworking diagram showing a UE connected to a Packet Domain Network, which is connected to two External Network(s) via Gi/SGi and T6 interfaces. + +**Figure 7: IP network interworking** + +The GGSN/P-GW for interworking with the IP network is the access point of the Packet Domain (see figure 8). In this case the Packet Domain network will look like any other IP network or subnetwork. + +![Figure 8: The protocol stacks of GGSN and P-GW for the IP network interworking diagram showing layers IP, L2, and L1 within a Packet Domain Bearer, connected to the Gi/SGi interface.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +The diagram shows the protocol stacks for GGSN and P-GW. A 'Packet Domain Bearer' is shown as a large rectangle. Inside it, there are three stacked layers: 'IP' (top), 'L2' (middle), and 'L1' (bottom). The 'IP' layer is further divided into two sections, each labeled 'IP', with a funnel-like shape between them. The 'Packet Domain Bearer' is connected to the 'Gi/SGi' interface on the right. The 'GGSN/P-GW' label is positioned above the protocol stack. + +Figure 8: The protocol stacks of GGSN and P-GW for the IP network interworking diagram showing layers IP, L2, and L1 within a Packet Domain Bearer, connected to the Gi/SGi interface. + +**Figure 8: The protocol stacks of GGSN and P-GW for the IP network interworking** + +Typically in the IP networks, the interworking with subnetworks is done via IP routers. The Gi reference point is between the GGSN and the external IP network; and the Sgi reference point is between the P-GW and the external IP network. From the external IP network's point of view, the GGSN/P-GW is seen as a normal IP router. The L2 and L1 layers are operator specific. + +It is out of the scope of the present document to standardise the router functions and the used protocols in the Gi/Sgi reference point. + +Interworking with user defined ISPs and private/public IP networks is subject to interconnect agreements between the network operators. + +No user data or header compression is done in the GGSN/P-GW. + +Both the GGSN/P-GW (for both Control Plane and User Plane CIoT EPS Optimizations) and the SCEF (for Control Plane CIoT EPS Optimization) for interworking with the network handling Non-IP data services are the access points of the Packet Domain. See 3GPP TS 23.401 [77] and 3GPP TS 23.060 [3] for further details. + +## 11.2.1 Access to Internet, Intranet or ISP through Packet Domain + +The access to Internet, Intranet or ISP may involve specific functions such as user authentication, user's authorization, end to end encryption between MS and Intranet/ISP, allocation of a dynamic address belonging to the PLMN/Intranet/ISP addressing space, IPv6 address autoconfiguration, etc. + +For this purpose the Packet Domain may offer: + +- either direct transparent access to the Internet; or +- a non transparent access to the Intranet/ISP. In this case the Packet Domain, i.e. the GGSN/P-GW, takes part in the functions listed above. + +The mechanisms for host configuration and user authentication described in this subclause and its subclauses are applicable for the initial IP-CAN session establishment to allocate IP addresses (IPv4 and/or IPv6) to the MS. For GTP based access, the activation of any subsequent IP-CAN bearers for that IP-CAN session, (i.e. secondary PDP context activation Procedure', dedicated bearer activation), as well as the use of TFTs, is described in 3GPP TS 23.060 [3], 3GPP TS 23.401 [77]. + +### 11.2.1.1 Transparent access to the Internet + +![Diagram of the PDN Interworking Model for transparent access to the Internet. It shows a Packet Domain Network (oval) connected to a GGSN (rectangle). The GGSN is connected to an Operator specific IP Network (oval). The Operator specific IP Network is connected to a Firewall / Proxy (rectangle), which is connected to an External IP Network (oval). The GGSN is also connected to a DHCP (rectangle) and a DNS (rectangle). The DHCP and DNS are connected to the Operator specific IP Network. The Gi Reference Point is indicated by a dashed line between the GGSN and the Operator specific IP Network.](5fbb4f0de01736f1293333e599410c99_img.jpg) + +``` + +graph LR + subgraph Packet_Domain_Network [Packet Domain Network] + GGSN[GGSN] + DHCP[DHCP] + DNS[DNS] + end + GGSN --- Gi_Ref[Gi Reference Point] + Gi_Ref --- Operator_IP_Net([Operator specific IP Network]) + Operator_IP_Net --- Firewall_Proxy[Firewall / Proxy] + Firewall_Proxy --- External_IP_Net([External IP Network]) + DHCP --- Operator_IP_Net + DNS --- Operator_IP_Net + +``` + +Diagram of the PDN Interworking Model for transparent access to the Internet. It shows a Packet Domain Network (oval) connected to a GGSN (rectangle). The GGSN is connected to an Operator specific IP Network (oval). The Operator specific IP Network is connected to a Firewall / Proxy (rectangle), which is connected to an External IP Network (oval). The GGSN is also connected to a DHCP (rectangle) and a DNS (rectangle). The DHCP and DNS are connected to the Operator specific IP Network. The Gi Reference Point is indicated by a dashed line between the GGSN and the Operator specific IP Network. + +**Figure 9: Example of the PDN Interworking Model, transparent case** + +In figure 9, an example PDN interworking model for transparent access to the Internet is provided for a GGSN and its Gi reference point. + +In transparent access to the Internet case: + +- the MS is given an IPv4 address and/or an IPv6 prefix belonging to the operator addressing space. The IPv4 address and/or IPv6 prefix is assigned either at subscription in which case it is a static address or at IP-CAN session establishment in which case it is a dynamic address. This IPv4 address and/or IPv6 prefix if applicable is used for packet forwarding between the Internet and the GGSN/P-GW and within the packet domain. With IPv6, Stateless Address Autoconfiguration shall be used to assign an IPv6 address to the MS. These procedures are as described in the IPv6 non-transparent access case except that the addresses belong to the operator addressing space. +- the MS need not send any authentication request at IP-CAN session establishment procedure and the GGSN/P-GW need not take any part in the user authentication/authorization process. + +The transparent case provides at least a basic ISP service. As a consequence of this it may therefore provide a bearer service for a tunnel to a private Intranet. + +Note that the remainder of this subclause deals with this specific use-case as depicted in figure 10. + +- The user level configuration may be carried out between the TE and the intranet, the Packet Domain network is transparent to this procedure. + +The used protocol stack is depicted in figure 10. + +![Figure 10: Transparent access to an Intranet. The diagram shows the protocol stack for a TE (Terminal Equipment), MT (Mobile Terminal), GGSN (PDN Gateway), and Intranet. The TE stack consists of Intranet protocol, IP, and PPP or L2. The MT stack consists of PPP or L2, which connects to the Packet Domain bearer. The GGSN stack consists of IP and L2. The Intranet stack consists of Intranet protocol, IP, and L2. Arrows indicate the flow of data from the TE through the MT, Packet Domain bearer, and GGSN to the Intranet.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +Figure 10: Transparent access to an Intranet. The diagram shows the protocol stack for a TE (Terminal Equipment), MT (Mobile Terminal), GGSN (PDN Gateway), and Intranet. The TE stack consists of Intranet protocol, IP, and PPP or L2. The MT stack consists of PPP or L2, which connects to the Packet Domain bearer. The GGSN stack consists of IP and L2. The Intranet stack consists of Intranet protocol, IP, and L2. Arrows indicate the flow of data from the TE through the MT, Packet Domain bearer, and GGSN to the Intranet. + +**Figure 10: Transparent access to an Intranet** + +In figure 10, an example for transparent access to an Intranet is provided for a GGSN and its Gi reference point, but the same principle is applicable to EPC. + +The communication between the PLMN and the Intranet may be performed over any network, even an insecure network e.g. the Internet. There is no specific security protocol between the GGSN and the Intranet because security is ensured on an end to end basis between the MS and the intranet by the "Intranet Protocol". + +User authentication and encryption of user data are done within the "Intranet Protocol" if either of them is needed. This "Intranet Protocol" may also carry private (IP) addresses belonging to the address space of the Intranet. + +An example of an "Intranet Protocol" is Ipsec (see RFC 1825 [61]). If Ipsec is used for this purpose then Ipsec authentication header or security header may be used for user (data) authentication and for the confidentiality of user data (see RFC 1826 [62] and RFC 1827 [63]). In this case private IP tunnelling within public IP takes place. + +## 11.2.1.2 IPv4 Non Transparent access to an Intranet or ISP + +### 11.2.1.2.1 non-EPC based IPv4 Non Transparent access + +In this case: + +- the MS is given an address belonging to the Intranet/ISP addressing space. The address is given either at subscription in which case it is a static address or at PDP context activation in which case it is a dynamic address. This address is used for packet forwarding within the GGSN and for packet forwarding on the Intranet/ISP. This requires a link between the GGSN and an address allocation server, like AAA, DHCP, ..., belonging to the Intranet/ISP; +- the MS shall send an authentication request at PDP context activation and the GGSN requests user authentication from a server, like AAA, DHCP, ..., belonging to the Intranet/ISP; +- the protocol configuration options are retrieved (if requested by the MS at PDP context activation) from some server (AAA or DHCP, ...) belonging to the Intranet/ISP; +- the communication between the Packet Domain and the Intranet/ISP may be performed over any network, even an insecure e.g. the Internet. In case of an insecure connection between the GGSN and the Intranet/ISP there may be a specific security protocol in between. This security protocol is defined by mutual agreement between PLMN operator and Intranet/ISP administrator. + +![](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +| TE | MT | | SGSN | | GGSN | | ISP | +|------------|------------|--------------|--------------|--------------|--------------|---------------------------------|-------------------------------| +| PPP/L2 | PPP/L2 | SM | SM | GTP-C | GTP-C | DHCP/
RADIUS/
Diameter | DHCP/
RADIUS/
Diameter | +| | | | | | | Transport layer
( See NOTE ) | Transport layer
(See NOTE) | +| | | | | | | IP | IP | +| Phy. layer | Phy. layer | Lower layers | Lower layers | Lower layers | Lower layers | Lower layers | Lower layers | + +**Figure 11a: Signalling plane of non transparent case** + +NOTE: The transport protocol UDP is used for DHCP and RADIUS, and TCP or SCTP are used for Diameter. + +The following description bullet items describe the signal flow. + +- 1) The TE sends an AT-command to the MT to set up parameters and enter PPP mode. The MT responds with an AT-response. +- 2) LCP negotiates Maximum-Receive-Unit and authentication protocol. The negotiated authentication protocol is, either CHAP, PAP or 'none'. The MT shall try to negotiate for CHAP as first priority. +- 3) If the negotiated authentication protocol is either of CHAP or PAP, the TE authenticates itself towards the MT by means of that protocol. The MT stores the necessary authentication data and sends a forced positive acknowledgement of the authentication to the TE. +- 4) The TE requests IP configuration by sending the IPCP Configure-Request message to the MT indicating either the static IP address that shall be used or that an IP-address shall be dynamically allocated. +- 5) The MT sends the Activate PDP context request message to the SGSN, including the Protocol Configuration Options. The SGSN sends the Create PDP context req message to the chosen GGSN including the unmodified Protocol Configuration Options. +- 6) The GGSN deduces from the APN: + - the server(s) to be used for address allocation, authentication and protocol configuration options retrieval; + - the protocol like RADIUS, DHCP, ... to be used with this / those server(s); + - the communication and security feature needed to dialogue with this / those server(s) e.g. tunnel, IPSec security association, dial-up connection (using possibly PPP), ... + +As an example the GGSN may use one of the following options: + +- RADIUS for authentication and IP-address allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the GGSN; +- RADIUS for authentication and DHCP for host configuration and address allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the GGSN. After a successful authentication, the DHCP client discovers the DHCP server(s) in the ISP/Intranet and receives host configuration data. +- If the received Protocol Configurations Options IE contains a PPP IPCP Configure-Request packet, the GGSN shall analyse all the contained IPCP options and their requested values. In accordance with the relevant PPP RFC 1661 [21a] and RFC 1662 [21b] the GGSN shall respond with the following messages: + - zero or one PPP IPCP Configure-Reject packet containing options not supported and options which values cannot be returned; + - zero or one PPP IPCP Configure-Nak packet containing options that are supported but has requested values that are incorrect/unsupported; and + +- zero or one PPP IPCP Configure-Ack packet containing options that are supported and has requested values that are correct/supported. + +Any returned PPP IPCP packets shall be contained in the Protocol Configurations Options IE. + +- 7) The GGSN sends back to the SGSN a Create PDP Context Response message, containing the Protocol Configuration Options IE. The cause value shall be set according to the outcome of the host –authentication and –configuration. A PDP context activation shall not be rejected solely due to the presence of unsupported or incorrect PPP IPCP options or option values, received from the MS in the Protocol Configurations Options IE. The MS may however later decide to immediately deactivate the activated PDP context due to the information received in the Protocol Configurations Options IE received from the network. +- 8) Depending on the cause value received in the Create PDP Context Response the SGSN sends either an Activate PDP Context Accept or an Activate PDP Context Reject, to the MS. + +If Protocol Configuration Options are received from the GGSN, the SGSN shall relay those to the MS. The MT sends either the configuration-ack packet (e.g. IPCP Configure Ack in PPP case), the configure-nack packet in case of dynamic address allocation (e.g. IPCP Configure Nack in PPP case), or a link Terminate request (LCP Terminate-Request in PPP case) back to the TE. In the case where a configure-nack packet was sent by the MT, a local negotiation may take place at the R reference point (i.e. the TE proposes the new value to the MT), after which a configuration-ack packet is sent to the TE. + +- 9) In case a configuration-ack packet was sent to the TE, the link from the TE to the external ISP/Intranet is established and IP packets may be exchanged. + +In case a link terminate request packet was sent to the TE, the TE and MT negotiates for link termination. The MT may then send a final AT-response to inform the TE about the rejected PDP Context activation. + +A link terminate request packet (such as LCP Terminate-request in PPP case) causes a PDP context deactivation. + +EXAMPLE: In the following example PPP is used as layer 2 protocol over the R reference point. + +The MT acts as a PPP server and translates Protocol Configuration Options into SM message Ies. GTP-C carries this information unchanged to the GGSN which uses the information e.g. for DHCP or RADIUS authentication and host configuration. The result of the host authentication and configuration is carried via GTP-C to the SGSN which relays the information to the MT. The MT sends an IPCP Configure-Ack to the TE with the appropriate options included. + +![Sequence diagram for PDP Context Activation for the IPv4 Non-transparent case. Lifelines: TE, MT, SGSN, GGSN (RADIUS/DHCP client), ISP/intranet (RADIUS/DHCP server). The diagram shows two options for authentication and IP address allocation: Option 1 (RADIUS) and Option 2 (RADIUS+DHCP).](26d664119ad25250780f554633444e54_img.jpg) + +The sequence diagram illustrates the PDP Context Activation process for the IPv4 Non-transparent case. The participants are TE (Terminal Equipment), MT (Mobile Terminal), SGSN (Serving GPRS Support Node), GGSN (PDN Gateway, acting as a RADIUS/DHCP client), and ISP/intranet (acting as a RADIUS/DHCP server). + +**Initial Setup:** + +- TE sends **AT-Commands [APN]** to MT. +- TE sends **LCP negotiation [MRU, Auth. prot.]** to MT. +- TE sends **Authentication [CHAP/PAP/none]** to MT. The MT stores the authentication parameters. +- TE sends **IPCP Config-req [ IP-address, Header compression ]** to MT. + +**PDP Context Activation:** + +- MT sends **Activate PDP Context req.** to SGSN, containing **[ APN, QoS, PDP-type, NSAPI, Protocol Configuration Options ]**. +- SGSN sends **Create PDP ContextReq.** to GGSN, containing **[ APN, QoS, PDP-type, TID, Protocol Configuration Options ]**. + +**Option 1: RADIUS** + +- GGSN sends **RADIUS Access-Request** to ISP/intranet, containing **Authentication, Configuration**. +- ISP/intranet responds with **RADIUS Access-Accept**, containing **Authentication, Configuration**. + +**Option 2: RADIUS+ DHCP** + +- GGSN sends **RADIUS Access-Request** to ISP/intranet, containing **Authentication**. +- ISP/intranet responds with **RADIUS Access-Accept**, containing **Authentication**. +- GGSN sends **DHCP-DISCOVER** to ISP/intranet. +- ISP/intranet responds with **DHCP-OFFER**, containing **Configuration**. +- GGSN sends **DHCP-REQUEST** to ISP/intranet, containing **Configuration**. +- ISP/intranet responds with **DHCP-ACK**, containing **Configuration**. + +**GGSN Processing:** + +- GGSN performs: + - APN -> ISP address translation via DNS + - allocates 1) RADIUS client or 2) RADIUS client and DHCP client + - Translates the Protocol Configuration Options DHCP option and RADIUS attributes. +- GGSN stores IP-address and composes an NCP-IPCP Configure-Ack packet. + +**Finalization:** + +- SGSN sends **Create PDP Context Response** to MT, containing **[Protocol Configuration Options, Cause]**. +- MT sends **Activate PDP Context Acc** to TE, containing **[Protocol Configuration Options, Cause]**. +- TE sends **IPCP Configuration-Ack [IP-address, Header compression]** to MT. + +Sequence diagram for PDP Context Activation for the IPv4 Non-transparent case. Lifelines: TE, MT, SGSN, GGSN (RADIUS/DHCP client), ISP/intranet (RADIUS/DHCP server). The diagram shows two options for authentication and IP address allocation: Option 1 (RADIUS) and Option 2 (RADIUS+DHCP). + +Figure 11b: PDP Context Activation for the IPv4 Non-transparent case + +## 11.2.1.2.2 EPC based IPv4 Non Transparent access + +In this case: + +- a static or a dynamic IPv4 address belonging to the Intranet/ISP addressing space is allocated to a UE at IP-CAN session establishment. The methods of allocating IP address to the UE are specified in 3GPP TS 23.060 [3], + +3GPP TS 23.401 [77] and 3GPP TS 23.402 [78]. The allocated IPv4 address is used for packet forwarding within the P-GW and for packet forwarding on the Intranet/ISP; + +- as a part of the IP-CAN session establishment, the P-GW may request user authentication from an external AAA server (i.e. RADIUS, Diameter) belonging to the Intranet/ISP; +- the IPv4 address allocation to the UE may be performed based on the subscription or a local address pool, which belongs to the Intranet/ISP addressing space, provisioned in the P-GW. The IPv4 address allocation to the UE may also be done via the address allocation servers (i.e. DHCPv4, RADIUS AAA, Diameter AAA) belonging to the Intranet/ISP; +- if requested by the UE at IP-CAN session establishment, the P-GW may retrieve the Protocol Configuration Options or IPv4 configuration parameters from a locally provisioned database in P-GW and/or from some external server (i.e. DHCPv4, RADIUS AAA, Diameter AAA) belonging to the Intranet/ISP; +- the communication between the Packet Domain and the Intranet/ISP may be performed over any network, even an insecure network ,e.g. the Internet. In case of an insecure connection between the P-GW and the Intranet/ISP, there may be a specific security protocol in between. This security protocol is defined by mutual agreement between PLMN operator and Intranet/ISP administrator. + +Table 0 summarizes the IPv4 address allocation and parameter configuration use cases between the UE and the P-GW that may lead the P-GW to interwork with the external DHCPv4, RADIUS AAA and Diameter AAA servers over Sgi reference point. For detailed description of the signalling flows between the UE and the P-GW, see the references in the table. The detailed description of the signalling use cases that may be triggered between the P-GW and the external servers are specified in this document, as referenced in the table. + +**Table 0 : IPv4 address allocation and parameter configuration use cases** + +| Signalling use cases between UE and P-GW | Signalling use cases between P-GW and external servers | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| | Authentication via RADIUS or Diameter server (Clauses 16 or 16a)

(NOTE 1,2,5) | IPv4 Address allocation via DHCPv4 or RADIUS or Diameter server (Clauses 13.3, 16 or 16a)

(NOTE 1 and 2) | IPv4 parameter configuration via DHCPv4 or RADIUS or Diameter server (Clauses 13.3, 16 or 16a)

(NOTE 1 and 2) | +| (1) IPv4 address allocation and parameter configuration via default bearer activation
(2) IPv4 address allocation and parameter configuration via DHCPv4 signalling from UE towards P-GW (NOTE 3 and 4)

deployment options applicable to both use cases (1) and (2):
- GTP-based S5/S8 (Subclauses 5.3.1, 5.3.2, 5.10.2 in TS 23.401 [77])
- PMIP-based S5/S8 (Subclauses 4.7.1, 5.2, 5.6 in TS 23.402 [78]) | X | X | X | + +| Signalling use cases between UE and P-GW | Signalling use cases between P-GW and external servers | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| | Authentication via RADIUS or Diameter server (Clauses 16 or 16a)

(NOTE 1,2,5) | IPv4 Address allocation via DHCPv4 or RADIUS or Diameter server (Clauses 13.3, 16 or 16a)

(NOTE 1 and 2) | IPv4 parameter configuration via DHCPv4 or RADIUS or Diameter server (Clauses 13.3, 16 or 16a)

(NOTE 1 and 2) | +| (3) IPv4 address allocation and parameter configuration during primary PDP context activation using S4-based SGSN
(4) IPv4 address allocation and parameter configuration using DHCPv4 signalling from UE towards P-GW (NOTE 3 and 4)

and using
- GTP-based S5/S8 (Subclauses 9.2, 9.2.2.1A in TS 23.060 [3])
- PMIP-based S5/S8 (Subclauses 4.7.1, 5.2, 5.6, 5.10 in TS 23.402 [78]) | X | X | X | +| (5) IPv4 address allocation in trusted non-3GPP IP access using on S2a (NOTE 4)
- PMIPv6 (Subclauses 4.7.2, 6.2.1, and 6.2.4 in TS 23.402 [78])
- GTPv2 (Subclauses 16.1.5, and 16.2 in TS 23.402 [78])
and using
- anchoring in P-GW
- chained S2a and PMIP-based S8

(6) IPv4 address allocation in trusted non-3GPP IP access using MIPv4 FACoA on S2a and anchoring in P-GW (NOTE 4)
(Subclause 6.2.3 of TS 23.402 [78])

(7) IPv4 address allocation and parameter configuration via DHCPv4 signalling in non-3GPP IP access on S2a (NOTE 3 and 4)
(Subclauses 4.7.2 in TS 23.402 [78]) | X | X | X | +| (8) IPv4 address allocation and parameter configuration in untrusted non-3GPP IP access using on S2b (NOTE 4)
- PMIPv6 (Subclauses 4.7.3, 7.2.1, and 7.2.3 in TS 23.402 [78])
- GTPv2 (Subclauses 7.2.4 in TS 23.402 [78])
and using
- anchoring in P-GW
- chained S2b and PMIP-based S8 | X | X | X | +| (9) IPv4 parameter configuration via DHCPv4 with DSMIPv6 on S2c (Subclauses 4.7.4 in TS 23.402 [78])

(10) IPv4 address allocation with DSMIPv6 on S2c
- in trusted non-3GPP IP access
- in untrusted non-3GPP IP access
(Subclauses 4.7.4, 6.3 and 7.3 of TS 23.402 [78]) | X | X | X | + +| Signalling use cases between UE and P-GW | Signalling use cases between P-GW and external servers | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| | Authentication via RADIUS or Diameter server (Clauses 16 or 16a)

(NOTE 1,2,5) | IPv4 Address allocation via DHCPv4 or RADIUS or Diameter server (Clauses 13.3, 16 or 16a)

(NOTE 1 and 2) | IPv4 parameter configuration via DHCPv4 or RADIUS or Diameter server (Clauses 13.3, 16 or 16a)

(NOTE 1 and 2) | +|

NOTE 1: When the P-GW interworks with AAA servers, the APN may be configured to interwork with either Diameter AAA or RADIUS AAA server.

NOTE 2: If RADIUS AAA or Diameter AAA server is used, the authentication, IPv4 address allocation and parameter configuration signalling may be combined. Similarly, if DHCPv4 server is used for IPv4 address allocation and parameter configuration, the signalling towards the DHCPv4 server may be combined.

NOTE 3: If the authentication procedure towards RADIUS AAA or Diameter AAA is required, it is performed by the PGW before the DHCPv4 signalling when it receives the initial access request (e.g. Create Session Request, or Proxy Binding Update).

NOTE 4: For PMIP-based S5/S8, S2a and S2b, the P-GW shall obtain the IPv4 address from the external server after receiving Proxy Binding Update and before sending the Proxy Binding Ack. See 3GPP TS 23.402 [78] for details.

NOTE 5: The UEs may provide PAP/CHAP user credentials in the PCO IE when accessing to EPS on 3GPP and non-3GPP IP accesses. If such information is provided to the P-GW, the P-GW may perform user authentication based on these credentials. For S2c, the P-GW may receive such credentials from the UE based on IETF RFC 4739 [91] during the establishment of security association signalling via IKEv2. For S2b, the UEs may provide such credentials in the IKEv2 protocol as specified in IETF RFC 4739 [91], and if the ePDG supports multiple authentications, it shall include such credentials in the APCO IE (see 3GPP TS 29.275 [103] subclause 12.1.1.19) on the S2b interface.

| | | | + +### 11.2.1.3 IPv6 Non Transparent access to an Intranet or ISP + +When using IPv6 Address Autoconfiguration, the process of setting up the access to an Intranet or ISP involves two signalling phases. The first signalling phase is done in the control plane and consists of the PDP context activation or initial attach (e.g. create default bearer) for EPC based access, followed by a second signalling phase done in the user plane. + +The user plane signalling phase shall be stateless. The stateless procedure, which involves only the MS/UE and the GGSN/P-GW, is described in subclause "IPv6 Stateless Address Autoconfiguration". + +For APNs that are configured for IPv6 address allocation, the GGSN/P-GW shall only use the Prefix part of the IPv6 address for forwarding of mobile terminated IP packets. The size of the prefix shall be according to the maximum prefix length for a global IPv6 address as specified in the IPv6 Addressing Architecture, see RFC 4291 [82]. + +The GGSN/P-GW indicates to the MS/UE that Stateless Autoconfiguration shall be performed by sending Router Advertisements as described in the corresponding subclause below and according to the principles defined in RFC 4861 [89] and RFC 4862 [83]. + +For MS/UE having IPv6, IPv6 Stateless Address Autoconfiguration is mandatory. + +#### 11.2.1.3.1 IPv6 PDP Context Activation + +In this case: + +- The GGSN provides the MS with an IPv6 Prefix belonging to the Intranet/ISP addressing space. A dynamic IPv6 address shall be given using stateless address autoconfiguration. This IPv6 address is used for packet forwarding within the packet domain and for packet forwarding on the Intranet/ISP; +- the MS may send an authentication request at PDP context activation and the GGSN may request user authentication from a server, e.g. AAA, ..., belonging to the Intranet/ISP; +- the protocol configuration options are retrieved (if requested by the MS at PDP context activation) from some server, e.g. AAA, ..., belonging to the Intranet/ISP; + +- in order to avoid any conflict between the link-local address of the MS and that of the GGSN, the Interface-Identifier used by the MS to build its link-local address shall be assigned by the GGSN. The GGSN ensures the uniqueness of this interface-identifier. The MT shall then enforce the use of this Interface-Identifier by the TE. +- the communication between the Packet Domain and the Intranet/ISP may be performed over any network, even an insecure e.g. the Internet. In case of an insecure connection between the GGSN and the Intranet/ISP there may be a specific security protocol over the insecure connection. This security protocol is defined by mutual agreement between PLMN operator and Intranet/ISP administrator. +- the MS may request for DNS server IPv6 addresses using the PCO IE in e.g. the PDP Context Request message. In that case the GGSN may return the IP address of one or more DNS servers in the PCO in the PDP Context Response message. The DNS address(es) shall be coded in the PCO as specified in 3GPP TS 24.008 [54]. If a list of servers is received, the MS shall adhere to the explicit prioritisation order of the list. + +In the following signalling flow example, PPP is used as layer 2 protocol over the R reference point. The MT behaves as a PPP server and translates Protocol Configuration Options into SM message Ies. GTP-C carries this information unchanged to the GGSN which uses the information e.g. for RADIUS authentication. The result of the host authentication is carried via GTP-C back to the SGSN, which then relays the result to the MT. The MT finalises the IPV6CP negotiation by sending an IPV6CP Configure-Ack message to the TE with the appropriate options included, e.g. Interface-Identifier. The Interface-Identifier shall be used in the TE to create a link-local address to be able to perform the IPv6 address autoconfiguration (see subclauses 11.2.1.3.2 and 11.2.1.3.3). + +- 1) The TE sends an AT-command to the MT to set up parameters and enter PPP mode. The MT responds with an AT-response. +- 2) LCP negotiates Maximum-Receive-Unit and authentication protocol. The negotiated authentication protocol is either CHAP, PAP or 'none'. The MT shall try to negotiate for CHAP as first priority. +- 3) If the negotiated authentication protocol is either of CHAP or PAP, the TE authenticates itself towards the MT by means of that protocol. The MT stores the necessary authentication data and sends a forced positive acknowledgement of the authentication to the TE. +- 4) The TE requests IPv6 Interface-Identifier negotiation by sending the IPV6CP Configure-Request message to the MT. +- 5) The MT sends the Activate PDP Context Request message to the SGSN, including the Protocol Configuration Options. The Protocol Configuration Options IE may contain negotiated LCP options such as negotiated Authentication Protocol as well as any authentication data previously stored in the MT. It may also contain a request for dynamic configuration of DNS server IPv6 addresses. The MS shall for dynamic address allocation leave PDP Address empty and set PDP Type to IPv6 or IPv4v6. The SGSN sends the Create PDP context request message to the chosen GGSN including the unmodified Protocol Configuration Options. +- 6) The GGSN deduces from local configuration data associated with the APN: + - the source of IPv6 Prefixes (GGSN internal prefix pool, or external address allocation server); + - any server(s) to be used for address allocation, authentication and/or protocol configuration options retrieval (e.g. IMS related configuration, see 3GPP TS 24.229 [47]); + - the protocol e.g. RADIUS, to be used with the server(s); + - the communication and security feature needed to communicate with the server(s); + +As an example the GGSN may use one of the following options: + +- GGSN internal Prefix pool for IPv6 prefix allocation and no authentication; +- GGSN internal Prefix pool for IPv6 prefix allocation and RADIUS for authentication. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the GGSN; +- RADIUS for authentication and IPv6 prefix allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the GGSN; + +NOTE: DHCPv6 may be used for IPv6 prefix allocation. + +IPv6 Prefixes in a GGSN internal Prefix pool shall be configurable and structured per APN. + +The GGSN shall in the PDP Address IE in the Create PDP Context Response return an IPv6 address composed of a Prefix and an Interface-Identifier. The Interface-Identifier may have any value and it does not need to be unique within or across APNs. It shall however not conflict with the Interface-Identifier the GGSN has selected for its own side of the MS-GGSN link. The Prefix assigned by the GGSN or the external AAA server shall be globally or site-local unique. + +The GGSN shall analyse the requested values of all the protocol options contained in the received Protocol Configurations Options IE. The contents of the Protocol Configurations Options IE sent in the GGSN response shall be in accordance with the relevant standards e.g. the PPP standard RFC 1661 [21a] and RFC 1662 [21b]. + +- 7) The GGSN sends back to the SGSN a Create PDP Context Response message, containing the PDP Address IE and the Protocol Configuration Options IE. The Protocol Configuration Options IE may contain configuration data such as a list of DNS server IPv6 addresses. The cause value shall be set according to the outcome of the host authentication and configuration. +- 8) Depending on the cause value received in the Create PDP Context Response, the SGSN either stores the PDP Address and sends an Activate PDP Context Accept to the MS or, sends an Activate PDP Context Reject, to the MS. + +If Protocol Configuration Options are received from the GGSN, the SGSN shall relay those to the MS. + +- 9) The MT extracts the Interface-Identifier from the address received in the PDP Address IE and ignores the Prefix part. If this Interface-Identifier is identical to the tentative Interface-Identifier indicated in the IPV6CP Configure-Request message sent from the TE, the MT sends an IPV6CP Configure Ack packet, indicating this Interface-Identifier, to the TE. + +If the Interface-Identifier extracted from the address contained in the PDP Address IE is not identical to the tentative Interface-Identifier indicated in the IPV6CP Configure-Request message sent from the TE, the MT sends an IPV6CP Configure-Nak packet, indicating the Interface-Identifier extracted from the address contained in the PDP Address IE, to the TE. The TE then sends a new IPV6CP Configure-Request message to the MT, indicating the same Interface-Identifier as was indicated in the received IPV6CP Configure Nak (as indicated by the dotted IPV6CP Configure-Request and Configure-Ack in the figure below). Finally the MT responds with a IPV6CP Configure Ack packet. + +In case a PDP Context Reject was sent to the MS the MT sends an LCP Terminate-Request to the TE. + +- 10) When the TE has accepted the Interface-Identifier given by the MT, the user plane link from the TE to the GGSN and the external ISP/Intranet is established and the IPv6 address autoconfiguration may proceed. + +In case a link terminate request packet was sent to the TE, the TE and MT negotiates for link termination. The MT may then send a final AT-response to inform the TE about the rejected PDP Context activation. + +An LCP Terminate-request causes a PDP context deactivation. + +![Sequence diagram for PDP Context Activation for the IPv6 Non-transparent case. Lifelines: TE, MT, SGSN, GGSN (RADIUS/DHCP client), ISP/intranet (RADIUS/DHCP server). The diagram shows two options for authentication and IP address allocation. Option 1 uses RADIUS only, while Option 2 uses RADIUS+DHCP. The GGSN performs APN translation via DNS and translates Protocol Configuration Options. The MT stores authentication parameters. The TE sends IPv6CP Configure-request and receives Ack/Nak. The MT sends Activate PDP Context req. to the SGSN, which creates a PDP ContextReq. for the GGSN. The GGSN authenticates and allocates an IP address. The SGSN then sends Activate PDP Context Acc. to the MT, which in turn sends IPv6CP Configure-Ack to the TE.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Sequence diagram illustrating PDP Context Activation for the IPv6 Non-transparent case. + +**Participants:** TE, MT, SGSN, GGSN (RADIUS/DHCP client), ISP/intranet (RADIUS/DHCP server). + +**Sequence of Messages:** + +- TE sends **AT-Commands [APN]** to MT. +- TE sends **LCP negotiation [MRU, Auth. prot.]** to MT. +- TE sends **Authentication [CHAP/PAP/none]** to MT. The MT stores the authentication parameters. +- TE sends **IPV6CP Configure-request [Interface Identifier, Compression ]** to MT. +- MT sends **Activate PDP Context req. [ APN, QoS, PDP-type, NSAPI, Protocol Configuration Options]** to SGSN. +- SGSN sends **Create PDP ContextReq. [ APN, QoS, PDP-type, TID, Protocol Configuration Options]** to GGSN. +- GGSN performs: + - APN -> ISP address translation via DNS + - allocates 1) RADIUS client or 2) RADIUS client and DHCP client + - Translates the Protocol Configuration Options, DHCP Option and RADIUS attributes. +- Option 1: RADIUS** + - GGSN sends **RADIUS Access-Request** to ISP/intranet. + - ISP/intranet responds with **Authentication, Configuration**. + - GGSN sends **RADIUS Access-Accept** to ISP/intranet. + - ISP/intranet responds with **Authentication, Configuration**. +- Option 2: RADIUS+ DHCP** + - GGSN sends **RADIUS Access-Request** to ISP/intranet. + - ISP/intranet responds with **Authentication**. + - GGSN sends **RADIUS Access-Accept** to ISP/intranet. + - ISP/intranet responds with **Authentication**. + - GGSN sends **DHCPv6 (Note)** to ISP/intranet. + - ISP/intranet responds with **Configuration**. +- GGSN stores IP-address. +- SGSN sends **Create PDP Context Response [PDP Address, Protocol Configuration Options, Cause]** to MT. +- MT sends **Activate PDP Context Acc [PDP Address, Protocol Configuration Options, Cause]** to TE. +- TE sends **IPV6CP Configure-Ack/Nak [Interface Identifier, Compression]** to MT. +- TE sends **IPV6CP Configure-Request [Interface Identifier, Compression]** to MT. +- TE sends **IPV6CP Configure-Ack [Interface Identifier, Compression]** to MT. + +Sequence diagram for PDP Context Activation for the IPv6 Non-transparent case. Lifelines: TE, MT, SGSN, GGSN (RADIUS/DHCP client), ISP/intranet (RADIUS/DHCP server). The diagram shows two options for authentication and IP address allocation. Option 1 uses RADIUS only, while Option 2 uses RADIUS+DHCP. The GGSN performs APN translation via DNS and translates Protocol Configuration Options. The MT stores authentication parameters. The TE sends IPv6CP Configure-request and receives Ack/Nak. The MT sends Activate PDP Context req. to the SGSN, which creates a PDP ContextReq. for the GGSN. The GGSN authenticates and allocates an IP address. The SGSN then sends Activate PDP Context Acc. to the MT, which in turn sends IPv6CP Configure-Ack to the TE. + +NOTE: DHCPv6 may be used for IPv6 prefix allocation. + +**Figure 11ba: PDP Context Activation for the IPv6 Non-transparent case** + +#### 11.2.1.3.1a IPv6 EPC based Bearer Activation + +In this case, the P-GW provides the UE with an IPv6 Prefix belonging to the Intranet/ISP addressing space. A dynamic IPv6 address is given using stateless address autoconfiguration. This IPv6 address is used for packet forwarding within the packet domain and for packet forwarding on the Intranet/ISP. + +When a P-GW receives an initial access request (e.g. Create Session Request or Proxy Binding Update) message, the P-GW deduces from local configuration data associated with the APN: + +- The source of IPv6 Prefixes (P-GW internal prefix pool, or external address allocation server); +- Any server(s) to be used for address allocation, authentication and/or protocol configuration options retrieval (e.g. IMS related configuration, see 3GPP TS 24.229 [47]); +- The protocol, i.e. RADIUS, Diameter or DHCPv6, to be used with the server(s); +- The communication and security feature needed to communicate with the server(s); + +As an example the P-GW may use one of the following options: + +- P-GW internal Prefix pool for IPv6 prefixes allocation and no authentication; +- P-GW internal Prefix pool for IPv6 prefixes allocation and RADIUS for authentication. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the P-GW; +- RADIUS for authentication and IPv6 prefix allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the P-GW; + +The P-GW includes the PDP Address IE in the the initial access response (e.g. Create Session Response or Proxy Binding Acknowledgement) and return an IPv6 address composed of a Prefix and an Interface-Identifier. The Interface-Identifier may have any value and it does not need to be unique within or across APNs. It shall however not conflict with the Interface-Identifier that the P-GW has selected for its own side of the UE-P-GW link. The Prefix assigned by the P-GW or the external AAA server shall be globally or site-local unique (see the Note in subclause 11.3 of this document regarding the usage of site-local addresses). + +Table 0.a summarizes the IPv6 prefix allocation and parameter configuration use cases between the UE and the P-GW that may lead the P-GW to interwork with the external RADIUS AAA, Diameter AAA and DHCPv6 servers over Sgi reference point. For detailed description of the signalling flows between the UE and the P-GW, see the references in the table. The detailed description of the signalling use cases that may be triggered between the P-GW and the external servers are specified in this document, as referenced in the table. + +**Table 0.a : IPv6 prefix allocation and parameter configuration use cases** + +| Signalling use cases between UE and P-GW | Signalling use cases between P-GW and external servers | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| | Authentication via RADIUS or Diameter server (Clauses 16 or 16a)

(NOTE 1, and 2, 3) | IPv6 prefix allocation via DHCPv6 or RADIUS or Diameter server (Clauses 13.3, 16 or 16a)

(NOTE 1 and 2) | IPv6 parameter configuration via DHCPv6 or RADIUS or Diameter server (Clauses 13.3, 16 or 16a)

(NOTE 1 and 2) | +| (1) IPv6 address allocation and parameter configuration
(2) IPv6 parameter configuration via stateless DHCPv6

deployment options applicable to both use cases (1) and (2):
- GTP-based S5/S8 (Subclauses 5.3.1, 5.3.2, 5.10.2 in TS 23.401 [77])
- PMIP-based S5/S8 (Subclauses 4.7.1, 5.2, 5.6 in TS 23.402 [78]) | X | X | X | +| (3) IPv6 address allocation and parameter configuration via S4-based SGSN
(4) IPv6 parameter configuration via stateless DHCPv6

and using
- GTP-based S5/S8 (Subclauses 9.2, 9.2.2.1A in TS 23.060 [3])
- PMIP-based S5/S8 (Subclauses 4.7.1, 5.2, 5.6, 5.10 in TS 23.402 [78]) | X | X | X | +| (5) IPv6 address allocation and parameter configuration in trusted non-3GPP IP access using on S2a
- PMIPv6 (Subclauses 4.7.2, 6.2.1, and 6.2.4 in TS 23.402 [78])
- GTPv2 (Subclauses 16.1.5, and 16.2 in TS 23.402 [78])

(6) IPv6 parameter configuration via stateless DHCPv6

and using
- anchoring in P-GW
- chained S2a and PMIP-based S8 | X | X | X | +| (7) IPv6 address allocation and parameter configuration in untrusted non-3GPP IP access using on S2b
- PMIPv6 (Subclauses 4.7.3, 7.2.1, and 7.2.3 in TS 23.402 [78])
- GTPv2 (Subclauses 7.2.4 in TS 23.402 [78])
and using
- anchoring in P-GW
- chained S2b and PMIP-based S8 | X | X | X | +| (8) IPv6 address allocation and parameter configuration on S2c
- in trusted non-3GPP IP access
- in untrusted non-3GPP IP access
(Subclauses 4.7.4, 6.3 and 7.3 of TS 23.402 [78])

(9) IPv6 parameter configuration via stateless DHCPv6 on S2c
(Subclauses 4.7.4 in TS 23.402 [78]) | X | X | X | +| NOTE 1: When the P-GW interworks with AAA servers, the APN may be configured to interwork with either Diameter AAA or RADIUS AAA server. | | | | +| NOTE 2: If RADIUS AAA or Diameter AAA server is used, the authentication, IPv6 prefix allocation and parameter configuration signalling may be combined. Similarly, if DHCPv6 server is used for IPv6 prefix allocation and parameter configuration, the signalling towards the DHCPv6 server may be combined. | | | | +| NOTE 3: The UEs may provide PAP/CHAP user credentials in the PCO IE when accessing to EPS on 3GPP and non-3GPP IP accesses. If such information is provided to the P-GW, the P-GW may perform user authentication based on these credentials. For S2c, the P-GW may receive such credentials from the UE based on IETF RFC 4739 [91] during the establishment of security association signalling via IKEv2. For S2b, the UEs may provide such credentials in the IKEv2 protocol as specified in IETF RFC 4739 [91], and if the ePDG supports multiple authentications, it shall include such credentials in the APCO IE (see 3GPP TS 29.275 [103] subclause 12.1.1.19) on the S2b interface. | | | | + +### 11.2.1.3.2 IPv6 Stateless Address Autoconfiguration + +As described in 3GPP TS 23.060 [3], the IPv6 prefix of a PDP Context of PDP type IPv6 or IPv4v6 activated by means of the IPv6 Stateless Address Autoconfiguration Procedure is uniquely identified by the prefix part of the IPv6 address only. The MS may select any value for the Interface-Identifier part of the address. The only exception is the Interface-Identifier for the link-local address used by the MS (see RFC 4291 [82]). This Interface-Identifier shall be assigned by the GGSN to avoid any conflict between the link-local address of the MS and that of the GGSN itself. This is described in subclause "IPv6 PDP Context Activation" above. + +For IPv6 the PDP Context Activation phase is followed by an address autoconfiguration phase. The procedure describing APNs configured to use Stateless Address Autoconfiguration, may be as follows: + +- 1) After the first phase of setting up IPv6 access to an Intranet or ISP, the MS shall use the IPv6 Interface-Identifier, as provided by the GGSN, to create its IPv6 Link-Local Unicast Address according to RFC 4291 [82]. + +Before the MS can communicate with other hosts or Mses on the Intranet/ISP, the MS must obtain an IPv6 Global or Site-Local Unicast Address. The simplest way is the IPv6 Stateless Address Autoconfiguration procedure described below and in 3GPP TS 23.060 [3]. The procedure is consistent with RFC 4862 [83]. + +The procedure below takes place through signalling in the user plane. It is done on the link between the MS and the GGSN. From the MS perspective the GGSN is now the first router on the link. + +- 2) After the GGSN has sent a Create PDP Context Response message to the SGSN, it shall start sending Router Advertisements periodically on the new MS-GGSN link established by the PDP Context. The MS may issue a Router Solicitation directly after the user plane establishment. This shall trigger the GGSN to send a Router Advertisement immediately. + +To indicate to the MS that stateless address autoconfiguration shall be performed, the GGSN shall leave the M-flag cleared in the Router Advertisement messages. The GGSN may set the O-flag if there are additional configuration parameters that need to be fetched by the MS (see below). + +The Prefix sent in the Router Advertisements shall be identical to the Prefix returned in the Create PDP Context Response. The Prefix is contained in the Prefix Information Option of the Router Advertisements and shall have the A-flag set ("Autonomous address configuration flag") and the L-flag cleared (i.e. the prefix should not be used for on-link determination). The lifetime of the prefix shall be set to infinity. In practice, the lifetime of a Prefix will be the lifetime of its PDP Context. There shall be exactly one Prefix included in the Router Advertisements. + +The handling of Router Advertisements shall be consistent with what is specified in RFC 4861 [89]. For the MS-GGSN link however, some specific handling shall apply. The randomisation part to determine when Router Advertisements shall be sent may be omitted since the GGSN is the only router on the link. Furthermore, some 3GPP specific protocol constants and default values shall apply (see subclause "IPv6 Router Configuration Variables in the GGSN"). These relate to the periodicity of the Router Advertisements initially and during continued operation. The motivation for this is to have a faster user-plane set-up even in bad radio conditions and to minimize MS power consumption during long continued operation. + +- 3) When creating a Global or Site-Local Unicast Address, the MS may use the Interface-Identifier received during the PDP Context Activation phase or it may generate a new Interface-Identifier. There is no restriction on the value of the Interface-Identifier of the Global or Site-Local Unicast Address, since the Prefix is unique. Interface-Identifiers shall in any case be 64-bit long. + +Since the GGSN guarantees that the Prefix is unique, the MS does not need to perform any Duplicate Address Detection on addresses it creates. That is, the 'DupAddrDetectTransmits' variable in the MS should have a value of zero. If the MS finds more than one Prefix in the Router Advertisement message, it shall only consider the first one and silently discard the others. The GGSN shall not generate any globally unique IPv6 addresses for itself using the Prefix assigned to the MS in the Router Advertisement. + +If the O-flag ("Other configuration flag") was set in the Router Advertisement, the MS may start a DHCP session to retrieve additional configuration parameters. See subclause 13.2.2 "Other configuration by the Intranet or ISP". If the MS is not DHCP capable, the O-flag may be ignored. + +![Sequence diagram for IPv6 Stateless Address Autoconfiguration. The diagram shows four lifelines: MS, SGSN, GGSN, and ISP/intranet RADIUS/Diameter/DHCP server. The sequence of messages is: 1. MS sends 'Activate PDP Context' to SGSN. 2. SGSN sends 'Create PDP Context' to GGSN. 3. GGSN sends 'RADIUS / Diameter / DHCPv6' to the ISP/intranet server. 4. MS sends a 'Router Solicitation' (dashed line) to GGSN. 5. GGSN sends a 'Router Advertisement' to MS with parameters: [M-flag=0, O-flag, Prefix, Lifetime, A-flag=1, L-flag=0]. 6. GGSN sends another 'Router Advertisement' to MS with the same parameters.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` + +sequenceDiagram + participant MS + participant SGSN + participant GGSN + participant ISP as ISP/intranet RADIUS/Diameter/DHCP server + + MS->>SGSN: Activate PDP Context + SGSN->>GGSN: Create PDP Context + GGSN->>ISP: RADIUS / Diameter / DHCPv6 + Note right of MS: Router Solicitation + MS-->>GGSN: Router Advertisement + Note right of GGSN: [M-flag=0, O-flag, Prefix, Lifetime, A-flag=1, L-flag=0] + GGSN-->>MS: Router Advertisement + Note right of GGSN: [M-flag=0, O-flag, Prefix, Lifetime, A-flag=1, L-flag=0] + +``` + +Sequence diagram for IPv6 Stateless Address Autoconfiguration. The diagram shows four lifelines: MS, SGSN, GGSN, and ISP/intranet RADIUS/Diameter/DHCP server. The sequence of messages is: 1. MS sends 'Activate PDP Context' to SGSN. 2. SGSN sends 'Create PDP Context' to GGSN. 3. GGSN sends 'RADIUS / Diameter / DHCPv6' to the ISP/intranet server. 4. MS sends a 'Router Solicitation' (dashed line) to GGSN. 5. GGSN sends a 'Router Advertisement' to MS with parameters: [M-flag=0, O-flag, Prefix, Lifetime, A-flag=1, L-flag=0]. 6. GGSN sends another 'Router Advertisement' to MS with the same parameters. + +**Figure 11bb: IPv6 Stateless Address Autoconfiguration** + +#### 11.2.1.3.2a IPv6 Stateless Address Autoconfiguration for EPC + +This subclause describes the signalling flows for the IPv6 Stateless Address Autoconfiguration procedures for EPC, in the case of using GTP-based S5/S8/S2a, and PMIP-based S5/S8/S2a. The procedures are based on the descriptions in TS 23.401 [77] and TS 23.402 [78]. Subclause 11.2.3.1a lists the use cases between the UE to the P-GW that may trigger the P-GW to interwork with the external PDNs for IPv6 Prefix allocation. + +IPv6 prefix is delivered to UE in Router Advertisement message from the access router, in the process of IPv6 Stateless Address Autoconfiguration. + +In the procedure in the cases of using GTP-based S5/S8, P-GW acts as an access router, and allocates to a UE a globally unique /64 IPv6 prefix if the PLMN allocates the prefix, or P-GW retrieves IPv6 prefix from an external PDN if one is allocated by the external PDN and advertises it to the UE. In the latter procedure, P-GW uses RADIUS, Diameter or DHCPv6 protocol for the retrieval of an IPv6 prefix. + +Following is the flow for IPv6 Stateless Address Autoconfiguration for EPC using GTP-based S5/S8. + +1. UE initiates the Attach procedure, indicating 'IPv6' or 'IPv4v6' for PDN type in PDP type information element. +2. MME requests for Default Bearer creation by sending Create Session Request to the S-GW. +- 2x. The S-GW sends Create Session Request to the P-GW. +3. P-GW retrieves IPv6 prefix using RADIUS, Diameter, or DHCPv6 mechanism. This procedure is performed when an external PDN allocates an IPv6 prefix. +4. The P-GW sends Create Session Response. It includes the IPv6 interface identifier I IPv6 prefix. +5. S-GW sends Create Session Response message to the MME. It includes the IPv6 interface identifier I IPv6 prefix. +- 5x. The MME sends Attach Accept message to the UE without the IPv6 prefix. The UE shall ignore the IPv6 prefix if it receives one in the message. +6. After receiving the Attach Accept message, the UE may send a Router Solicitation to the P-GW to solicit a Router Advertisement message. +7. The P-GW sends a Router Advertisement message to the UE, solicited or unsolicited. It shall include an IPv6 prefix in Prefix Information option field of the message. The prefix is the same as the one in the Attach Accept message, if it is provided during the default bearer establishment. For the handling of M, O, L and A flags, and the lifetime of the prefix in the Router Advertisement message, follow the description in subclause 11.2.1.3.2. + +![Sequence diagram for IPv6 Stateless Address Autoconfiguration for GTP-based S5/S8. The diagram shows the interaction between UE, MME, S-GW, P-GW, and External PDN. The sequence of messages is: 1. Attach Request (UE to MME), 2. Create Session Request (MME to S-GW), 2x. Create Session Request (S-GW to P-GW), 3. RADIUS / Diameter / DHCPv6 (P-GW to External PDN), 4. Create Session Response (P-GW to S-GW), 5. Create Session Response (S-GW to MME), 5x. Attach Accept (MME to UE), 6. Router Solicitation (UE to P-GW), and 7. Router Advertisement (P-GW to UE).](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MME + participant S-GW + participant P-GW + participant External PDN + + Note left of UE: 1. Attach Request + UE->>MME: 1. Attach Request + Note right of MME: 2. Create Session Request + MME->>S-GW: 2. Create Session Request + Note right of S-GW: 2x. Create Session Request + S-GW->>P-GW: 2x. Create Session Request + Note right of P-GW: 3. RADIUS / Diameter / DHCPv6 + P-GW-->>External PDN: 3. RADIUS / Diameter / DHCPv6 + Note right of External PDN: 4. Create Session Response + External PDN-->>P-GW: 4. Create Session Response + Note right of P-GW: 5. Create Session Response + P-GW->>S-GW: 5. Create Session Response + Note right of S-GW: 5x. Attach Accept + S-GW->>MME: 5x. Attach Accept + Note left of MME: 5x. Attach Accept + MME->>UE: 5x. Attach Accept + Note left of UE: 6. Router Solicitation + UE-->>P-GW: 6. Router Solicitation + Note right of P-GW: 7. Router Advertisement + P-GW->>UE: 7. Router Advertisement + +``` + +Sequence diagram for IPv6 Stateless Address Autoconfiguration for GTP-based S5/S8. The diagram shows the interaction between UE, MME, S-GW, P-GW, and External PDN. The sequence of messages is: 1. Attach Request (UE to MME), 2. Create Session Request (MME to S-GW), 2x. Create Session Request (S-GW to P-GW), 3. RADIUS / Diameter / DHCPv6 (P-GW to External PDN), 4. Create Session Response (P-GW to S-GW), 5. Create Session Response (S-GW to MME), 5x. Attach Accept (MME to UE), 6. Router Solicitation (UE to P-GW), and 7. Router Advertisement (P-GW to UE). + +**Figure 11bc: IPv6 Stateless Address Autoconfiguration for GTP-based S5/S8** + +If PMIP-based S5/S8 is used, S-GW acts as an access router. Therefore, it is responsible for receiving Router Solicitation from and sending Router Advertisement message to the UE. Other than this, procedure is the same as the case of using GTP-based S5/S8; P-GW allocates, or retrieves an IPv6 prefix from the external PDN. The prefix is delivered from the P-GW to the S-GW in the IPv6 Home Network Prefix Option IE of a Proxy Binding Acknowledgement message. + +In addition, the S-GW shall initiate sending the IPv6 Router Advertisement message (either solicited or unsolicited) to the UE once the PDN connection with PDN type IPv4v6 or IPv6 is setup after the procedure of E-UTRAN initial Attach, UE requested PDN connectivity, intra-3GPP access handover with Serving GW relocation, or handover from non-3GPP IP Access with S2a/S2b to 3GPP Access. + +Following diagram shows the case where PMIP-based S5/S8 is used. + +![Sequence diagram for IPv6 Stateless Address Autoconfiguration for PMIP-based S5/S8. Lifelines: UE, MME, S-GW, P-GW, External PDN. The sequence starts with UE sending an Attach Request to MME. MME sends a Create Default Bearer Request to S-GW. S-GW sends a Proxy Binding Update to P-GW. P-GW sends a RADIUS/Diameter/DHCPv6 message to External PDN and receives a response. P-GW sends a Proxy Binding Acknowledgement to S-GW. S-GW sends a Create Default Bearer Response to MME. MME sends an Attach Accept to UE. UE sends a Router Solicitation to S-GW. S-GW sends a Router Advertisement to UE.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MME + participant S-GW + participant P-GW + participant External PDN + + UE->>MME: Attach Request + MME->>S-GW: Create Default Bearer Request + S-GW->>P-GW: Proxy Binding Update + P-GW->>External PDN: RADIUS / Diameter / DHCPv6 + External PDN-->>P-GW: + P-GW->>S-GW: Proxy Binding Acknowledgement + S-GW->>MME: Create Default Bearer Response + MME->>UE: Attach Accept + UE-->>S-GW: Router Solicitation + S-GW->>UE: Router Advertisement + +``` + +Sequence diagram for IPv6 Stateless Address Autoconfiguration for PMIP-based S5/S8. Lifelines: UE, MME, S-GW, P-GW, External PDN. The sequence starts with UE sending an Attach Request to MME. MME sends a Create Default Bearer Request to S-GW. S-GW sends a Proxy Binding Update to P-GW. P-GW sends a RADIUS/Diameter/DHCPv6 message to External PDN and receives a response. P-GW sends a Proxy Binding Acknowledgement to S-GW. S-GW sends a Create Default Bearer Response to MME. MME sends an Attach Accept to UE. UE sends a Router Solicitation to S-GW. S-GW sends a Router Advertisement to UE. + +**Figure 11bd: IPv6 Stateless Address Autoconfiguration for PMIP-based S5/S8** + +For trusted non-3GPP accesses, the non-3GPP network supports prefix advertisement for IPv6 prefix received from the P-GW in PMIPv6 Proxy Binding Acknowledgement. If the trusted non-3GPP access network is a WLAN network, for GTP/PMIP-based S2a, TWAN acts as an access router. Therefore, TWAN is responsible for receiving Router Solicitation from and sending Router Advertisement message to the UE. Other than this, procedure is the same as the case of using GTP/PMIP-based S5/S8; P-GW allocates, or retrieves an IPv6 prefix from the external PDN. The prefix is delivered from the P-GW to the TWAN in the IPv6 Home Network Prefix Option IE of a Proxy Binding Acknowledgement message or in the PDN Address Allocation IE of Create Session Response message. + +Following diagram shows the case for trusted non-3GPP access network for WLAN access where GTP/PMIP-based S2a is used. + +![Sequence diagram for IPv6 Stateless Address Autoconfiguration for trusted WLAN access for GTP/PMIP-based S2a. Lifelines: UE, TWAN, P-GW, External PDN. The sequence starts with UE sending an EAP Authentication message to TWAN. TWAN sends a Create Session Request / Proxy Binding Update to P-GW. P-GW sends a RADIUS/Diameter/DHCPv6 message to External PDN and receives a response. P-GW sends a Create Session Response / Proxy Binding Acknowledgement to TWAN. UE sends a Router Solicitation to TWAN. TWAN sends a Router Advertisement to UE.](6be06b7dc72bb42afcb3465394667c3b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TWAN + participant P-GW + participant External PDN + + UE->>TWAN: EAP Authentication + TWAN->>P-GW: Create Session Request / Proxy Binding Update + P-GW->>External PDN: RADIUS / Diameter / DHCPv6 + External PDN-->>P-GW: + P-GW->>TWAN: Create Session Response / Proxy Binding Acknowledgement + UE-->>TWAN: Router Solicitation + TWAN->>UE: Router Advertisement + +``` + +Sequence diagram for IPv6 Stateless Address Autoconfiguration for trusted WLAN access for GTP/PMIP-based S2a. Lifelines: UE, TWAN, P-GW, External PDN. The sequence starts with UE sending an EAP Authentication message to TWAN. TWAN sends a Create Session Request / Proxy Binding Update to P-GW. P-GW sends a RADIUS/Diameter/DHCPv6 message to External PDN and receives a response. P-GW sends a Create Session Response / Proxy Binding Acknowledgement to TWAN. UE sends a Router Solicitation to TWAN. TWAN sends a Router Advertisement to UE. + +**Figure 11be: IPv6 Stateless Address Autoconfiguration for trusted WLAN access for GTP/PMIP-based S2a** + +The P-GW ensures that the advertised IPv6 prefix is globally unique. Regarding the handling of Duplicate Address Detection, follow subclause 11.2.1.3.2. + +The UE constructs its full IPv6 address in accordance with RFC 4862[83]. For the handling of IPv6 interface identifier, refer to subclause 11.2.1.3.2. + +If the P-GW, S-GW and TWAN receive Neighbor Solicitation message from the UE, it shall answer with Neighbor Advertisement message. + +To renew the allocated IPv6 prefix, the P-GW (GTP based S5/S8), S-GW (PMIPv6 based S5/S8) or TWAN (GTP/PMIP based S2a) shall send an IPv6 Router Advertisement (solicited or unsolicited) to the UE with the same assigned IPv6 prefix and and new non-zero values in preferred and valid lifetime fields for the PDN connection (PDN type IPv4v6 or IPv6), before the Router Advertisement lifetime and prefix lifetime expiry, as specified in IETF RFC 4861 [89]. When sending the IPv6 Router Advertisement message, the S-GW may trigger the paging (e.g. by sending a Downlink Data Notification message to the MME) if the UE is in idle state. In order to reduce paging an idle UE to deliver RA, the Router Advertisement lifetime and IPv6 prefix lifetime shall be configured accordingly. + +If a UE supports multiple PDN connections functionality, it can connect to multiple P-GWs simultaneously, or it can access multiple PDNs through a single P-GW. In the former case, the IPv6 prefix allocated for its default bearer is used for the UE's dedicated bearers toward the same PDN. In the latter case, IPv6 Stateless Address Autoconfiguration procedure is applied for each PDN connection. + +#### 11.2.1.3.3 IPv6 Stateful Address Autoconfiguration + +**Void.** + +**Figure 11bc : Void** + +#### 11.2.1.3.4 IPv6 Router Configuration Variables + +For IPv6 Address Autoconfiguration to work properly , network entities which act as an access router towards the MS/UE, i.e. PDN GW, Serving GW, ePDG and TWAN, shall be consistent with the RFCs specifying this process (for example RFC 4862 [83] and RFC 4861 [89]), unless stated otherwise in this or other 3GPP specifications. + +RFC 4861 [89] specifies a set of conceptual router configuration variables. Some of these variables require particular attention in GPRS and EPC in order to preserve radio resources and MS/UE power consumption while still allowing for appropriate robustness and fast user-plane set-up time even in bad radio conditions, or simply because they have a particular meaning in GPRS and EPC. These particular variables are listed below with appropriate (default) values and shall be configurable per APN. The values specified hereafter are specific to GPRS and EPC, and supersede those specified in RFC 4861 [89]. + +##### MaxRtrAdvInterval + +Shall have a default value of 21 600 s (6 h). + +##### MinRtrAdvInterval + +Shall have a default value of $0,75 \times \text{MaxRtrAdvInterval}$ i.e. 16 200 s (4,5 h). + +##### AdvValidLifetime + +Shall have a value giving Prefixes infinite lifetime, i.e. 0xFFFFFFFF. The assigned prefix remains Preferred until PDP Context/Bearer Deactivation. + +##### AdvPreferredLifetime + +Shall have a value giving Prefixes infinite lifetime, i.e. 0xFFFFFFFF. The assigned prefix remains Preferred until PDP Context/Bearer Deactivation. + +RFC 4861 [89] also specifies a number of protocol constants. The following shall have specific values for GPRS and EPC: + +MAX\_INITIAL\_RTR\_ADVERT\_INTERVAL + +This constant may be a variable within GPRS and EPC. It may have a value that gradually increases (exponentially or by some other means) with the number of initial Router Advertisements sent. This will enable a fast set-up of the MS-GGSN or MS/UE-PDN GW/Serving GW/ePDG/TWAN links in most cases, while still allowing the MS/UE to receive a Router Advertisement within the initial phase, even in case of bad radio conditions or slow response time, without having to send a large number of initial Router Advertisements. + +#### MAX\_INITIAL\_RTR\_ADVERTISEMENTS + +This is the number of Router Advertisements sent during the initial phase after the MS-GGSN or MS/UE-PDN GW/Serving GW/ePDG/TWAN links have been established. The value of this constant shall be chosen carefully, and in conjunction with MAX\_INITIAL\_RTR\_ADVERT\_INTERVAL, so as to not overload the radio interface while still allowing the MS/UE to complete its configuration in a reasonable delay. For instance, the default value could be chosen so that initial Router Advertisements are sent for at least 30 s. + +After the initial phase, the periodicity is controlled by the MaxRtrAdvInterval and the MinRtrAdvInterval constants. + +#### 11.2.1.3.5 IPv6 Prefix Delegation via DHCPv6 + +Optionally, a single network prefix shorter than the default /64 prefix may be assigned to a PDN connection. In this case, the /64 default prefix used for IPv6 stateless autoconfiguration will be allocated from this network prefix; the remaining address space from the network prefix can be delegated to the PDN connection using prefix delegation after the PDP context activation/default bearer establishment and IPv6 prefix allocation via IPv6 stateless address autoconfiguration as defined in clause 11.2.1.3.2/11.2.1.3.2a. When PLMN based parameter configuration is used, the GGSN / PDN GW provides the requested IPv6 prefix from a locally provisioned pool. When external PDN based IPv6 prefix allocation is used, the GGSN / PDN GW may obtain the prefix from the external PDN as per subclauses 16.4 and 16a.4. + +For the detailed description of the UE uses DHCPv6 to request additional IPv6 prefixes refer to 3GPP TS 23.060 [3] and 3GPP TS 23.401 [77]. + +#### 11.2.1.4 Access to Internet, Intranet or ISP with Mobile IPv4 + +##### General + +A way to allow users to roam from one environment to another, between fixed and mobile, between public and private as well as between different public systems is to use Mobile IP RFC 3344 [30]. Mobile IP (MIP) is a mobility management protocol developed by IETF. The Mobile IP Foreign Agent (FA) RFC 3344 [30] is located in the Core Network in the GGSN. MIP also uses a Home Agent (HA) RFC 3344 [30] which may or may not be located in a PLMN network. + +##### Interworking model for MIP + +A FA is located in the GGSN. The interface between the GGSN and the FA will probably not be standardised as the GGSN/FA is considered being one integrated node. The mapping between these two is a matter of implementation. Each FA must be configured with at least one care-of address. In addition a FA must maintain a list that combines IP addresses with TEIDs of all the visiting MSs that have registered with the FA. IP packets destined for the MS are intercepted by the HA and tunneled to the MS's care-of address, i.e. the FA. The FA de-tunnels the packets and forwards the packets to the MS. Mobile IP related signalling between the MS and the FA is done in the user plane. MIP registration messages RFC 3344 [30] are sent with UDP. + +![Figure 11c: Protocol stacks for the Gi IP reference point in the MIP signalling plane. The diagram shows a GGSN box containing a Foreign Agent, two JDP blocks, and two IP blocks. Below the GGSN is a Packet Domain Bearer box. To the right of the Packet Domain Bearer are L2 and L1 layers. A vertical dashed line labeled 'Gi' is on the far right.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Figure 11c: Protocol stacks for the Gi IP reference point in the MIP signalling plane. The diagram shows a GGSN box containing a Foreign Agent, two JDP blocks, and two IP blocks. Below the GGSN is a Packet Domain Bearer box. To the right of the Packet Domain Bearer are L2 and L1 layers. A vertical dashed line labeled 'Gi' is on the far right. + +Figure 11c: The protocol stacks for the Gi IP reference point in the MIP signalling plane + +![Figure 11d: Protocol stacks for user access with MIP. The diagram shows five entities: TE, MT, SGSN, GGSN, and Intranet/ISP. The TE has MIP Client, IP, and Phys. layers. The MT has a Packet Domain bearer. The GGSN has IP with FA Functionality, (Tunneling), and Lower layers. The Intranet/ISP has Home Agent, IP, (Tunneling), and Lower layers. The Packet Domain bearer connects the MT to the GGSN.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +Figure 11d: Protocol stacks for user access with MIP. The diagram shows five entities: TE, MT, SGSN, GGSN, and Intranet/ISP. The TE has MIP Client, IP, and Phys. layers. The MT has a Packet Domain bearer. The GGSN has IP with FA Functionality, (Tunneling), and Lower layers. The Intranet/ISP has Home Agent, IP, (Tunneling), and Lower layers. The Packet Domain bearer connects the MT to the GGSN. + +Figure 11d: Protocol stacks for user access with MIP + +In figure 11d: "(Tunneling)" is intended to show asymmetric traffic flow. Tunneling (IP-in-IP) is only used in the direction from the ISP towards the MT. + +Authentication of the user is supported in Mobile IPv4. This authentication mechanism may involve communication with an authentication server (e.g. RADIUS), although this is not shown in figure 11d. + +Address allocation – at PDP context activation no IP address is allocated to the MS indicated by 0.0.0.0. in the "Requested PDP Address" field. If the MS does not have a static IP address which it could register with the HA, it will acquire a dynamic IP address from the HA RFC 2794 [25]. After completion of the PDP activation the SGSN is informed of the assigned IP address by means of the GGSN initiated PDP Context Modification Procedure. + +An example of a signalling scheme, shown in figure 11e, is described below. In this example the MS is separated into a TE and MT, with AT commands and PPP used in-between (see 3GPP TS 27.060 [10]). The PS attach procedures have been omitted for clarity. + +## IPv4 - Registration UMTS/GPRS + MIP , FA care-of address + +![Sequence diagram illustrating IPv4 Registration UMTS/GPRS + MIP, FA care-of address. The diagram shows the interaction between TE, MT, SGSN, GGSN/FA, and Home Network. The MS (Mobile Station) contains the TE (Terminal Equipment) and MT (Mobile Terminal). The sequence starts with the TE sending an AT Command (APN) to the MT, followed by LCP Negotiation (MRU) and IPCP Conf. Req (MIPv4). The MT then sends an Activate PDP Context Request (APN=MIPv4FA) to the SGSN. The SGSN selects a suitable GGSN and sends a Create PDP Context Request (APN=MIPv4FA) to the GGSN/FA. The GGSN/FA sends a Create PDP Context Response (no PDP address) to the SGSN. The SGSN then sends an Activate PDP Context Accept (no PDP address) to the MT. The MT sends an IPCP Conf. Ack (MIPv4) to the TE. The MT also sends an Agent Advertisement to the TE. The MT sends a MIP Registration Request to the GGSN/FA. The GGSN/FA sends a MIP Registration Request to the Home Network. The Home Network sends a MIP Registration Reply to the GGSN/FA. The GGSN/FA sends a MIP Registration Reply to the MT. The GGSN/FA also sends an Update PDP Context to the SGSN, with a note 'B. Insert home address in PDP Context'. The SGSN sends an Update PDP Context to the MT.](13fde41de77bf026013a0b81684d1fc9_img.jpg) + +``` + +sequenceDiagram + participant TE + participant MT + participant SGSN + participant GGSN/FA + participant Home Network + Note right of MT: MS + + TE->>MT: 1. AT Command (APN) + MT-->>TE: 2. LCP Negotiation (MRU) + TE->>MT: 3. IPCP Conf. Req (MIPv4) + MT->>SGSN: 4. Activate PDP Context Request (APN=MIPv4FA) + Note right of SGSN: A. Select suitable GGSN + SGSN->>GGSN/FA: 5. Create PDP Context Request (APN=MIPv4FA) + GGSN/FA-->>SGSN: 6. Create PDP Context Response (no PDP address) + SGSN->>MT: 7. Activate PDP Context Accept (no PDP address) + MT->>TE: 8. IPCP Conf. Ack (MIPv4) + MT->>TE: 9. Agent Advertisement + MT->>GGSN/FA: 10. MIP Registration Request + GGSN/FA->>Home Network: 11. MIP Registration Request + Home Network-->>GGSN/FA: 12. MIP Registration Reply + GGSN/FA->>MT: 12. MIP Registration Reply + GGSN/FA->>SGSN: 13. Update PDP Context + Note right of GGSN/FA: B. Insert home address in PDP Context + SGSN->>MT: 13. Update PDP Context + +``` + +Sequence diagram illustrating IPv4 Registration UMTS/GPRS + MIP, FA care-of address. The diagram shows the interaction between TE, MT, SGSN, GGSN/FA, and Home Network. The MS (Mobile Station) contains the TE (Terminal Equipment) and MT (Mobile Terminal). The sequence starts with the TE sending an AT Command (APN) to the MT, followed by LCP Negotiation (MRU) and IPCP Conf. Req (MIPv4). The MT then sends an Activate PDP Context Request (APN=MIPv4FA) to the SGSN. The SGSN selects a suitable GGSN and sends a Create PDP Context Request (APN=MIPv4FA) to the GGSN/FA. The GGSN/FA sends a Create PDP Context Response (no PDP address) to the SGSN. The SGSN then sends an Activate PDP Context Accept (no PDP address) to the MT. The MT sends an IPCP Conf. Ack (MIPv4) to the TE. The MT also sends an Agent Advertisement to the TE. The MT sends a MIP Registration Request to the GGSN/FA. The GGSN/FA sends a MIP Registration Request to the Home Network. The Home Network sends a MIP Registration Reply to the GGSN/FA. The GGSN/FA sends a MIP Registration Reply to the MT. The GGSN/FA also sends an Update PDP Context to the SGSN, with a note 'B. Insert home address in PDP Context'. The SGSN sends an Update PDP Context to the MT. + +**Figure 11e: Example of PDP Context activation with Mobile IP registration +(the PS attach procedure not included)** + +1. The AT command carries parameters that the MT needs to request the PDP Context Activation. The important parameter here, is the APN (Access Point Name), see clause A below. The AT command is followed by a setup of the PPP connection between the MT and the TE. + 2. As part of the PPP connection, LCP negotiates Maximum-Receive-Unit between the TE and the MT. No PPP authentication is required when using MIPv4. + 3. As part of the PPP connection, the TE sends an IPCP Configure Request using the MIPv4 configuration option (see RFC 2290 [37]). The TE sends either its Home Address or a null address (i.e. 0.0.0.0) if the Network Address identifier is used (see RFC 2794 [25]). + 4. The MT sends the "Activate PDP Context Request" to the SGSN. The message includes various parameters of which the "APN" (Access Point Name) and the "Requested PDP Address" are of interest here. The TE/MT may use APN to select a reference point to a certain external network or to select a service. APN is a logical name referring to the external packet data network or to a service that the subscriber wishes to connect to. The "Requested PDP Address" should be omitted for all MSs using Mobile IP. This is done irrespective of if the TE has a permanently assigned Mobile IP address from its Mobile IP home network, a previously assigned dynamic home address from its Mobile IP home network or if it wishes the Mobile IP home network to allocate a "new" dynamic home address. +- A. The SGSN will base the choice of GGSN based on the APN that is given by the MS. +5. The SGSN requests the selected GGSN to set up a PDP Context for the MS. The PDP address and APN fields are the same as in the "Activate PDP Context Request" message. + 6. A Create PDP Context Response is sent from the GGSN/FA to the SGSN. If the creation of PDP Context was successful, some parameters will be returned to the SGSN, if not, an error code will be returned. If the GGSN has been configured, by the operator, to use a Foreign Agent for the requested APN, the PDP address returned by the GGSN shall be set to 0.0.0.0. indicating that the PDP address shall be reset by the MS with a Home Agent after the PDP context activation procedure. + +7. The Activate PDP Context Accept message is sent by the SGSN to the MT and contains similar information as the Create PDP Context Response message. +8. The MT sends an IPCP Configure Ack to the TE in order to terminate the PPP connection phase. +9. The Agent Advertisement RFC 3344 [30] is an ICMP (Internet Control Message Protocol) Router Advertisement message with a mobility agent advertisement extension. The latter part contains parameters of the FA that the mobile node needs, among those are one or more care-of addresses that the FA offers. This message should be sent, in the Packet Domain user plane, as an IP limited broadcast message, i.e. destination address 255.255.255.255, however only on the TEID for the requesting MS to avoid broadcast over the radio interface. +10. The Mobile IP Registration Request is sent from the mobile node to the GGSN/FA across the Packet Domain backbone as user traffic. The mobile node includes its (permanent) home address as a parameter RFC 3344 [30]. Alternatively, it can request a temporary address assigned by the home network by sending 0.0.0.0 as its home address, and include the Network Access Identifier (NAI) in a Mobile-Node-NAI Extension RFC 2794 [25] and RFC 2486 [31]. +11. The FA forwards the Mobile IP Registration Request to the home network of the mobile node, where a home agent (HA) processes it. Meanwhile, the GGSN/FA needs to store the home address of the mobile node or the NAI and the local link address of the MS, i.e. the TEID (Tunnel Endpoint ID). +12. The Registration Reply is sent from the home network to the FA, which extracts the information it needs and forwards the message to the mobile node in the Packet Domain user plane. As the FA/GGSN knows the TEID and the NAI or home address, it can pass it on to the correct MS. + - B. The GGSN/FA extracts the home address from the Mobile IP Registration Reply message and updates its GGSN PDP Context. +13. The GGSN triggers a "GGSN initiated PDP Context modification procedure" in order to update the PDP address in the SGSN and in the MT. + +### 11.2.1.5 IP Fragmentation Across Gi/Sgi + +3GPP and non-3GPP accesses provide IP services for a MS/UE. The GGSN/P-GW endpoint is a GTPv1-U tunnel (controlled by GTP Gn/Gp or S5/S8/S2a/S2b) or IP tunnel (controlled by S5/S8/S2a/S2b PMIPv6 or employed by a UE with MIPv4 or DSMIPv6). + +The MTU of the IP tunnel on the MS/UE side of the IP link may be different than the MTU of the IP link connecting the GGSN/P-GW to the PDN. As a result IP packets crossing the Gi/Sgi interface may need to be fragmented. Unnecessary fragmentation should be avoided when possible due to the following; + +- Fragmentation is bandwidth inefficient, since the complete IP header is duplicated in each fragment. +- Fragmentation is CPU intensive since more fragments require more processing at IP endpoints and IP routers. It also requires additional memory at the receiver. +- If one fragment is lost, the complete IP packet has to be discarded. The reason is there is no selective retransmission of IP fragments provided in IPv4 or IPv6. + +To avoid unnecessary fragmenting of IP packets the MS/UE, or a server in an external IP network, may find out the end-to-end MTU by path MTU discovery and hence fragment correctly at the source. IP Fragmentation on Gi/Sgi shall be handled according to IETF RFC 791 [16] and IETF RFC 2460 [49]. The GGSN/P-GW shall enforce the MTU of IP packets to/from the MS/UE based on IETF RFC 791 [16] and IETF RFC 2460 [49]. + +### 11.2.1.6 Support for CUPS across SGi + +Control plane and user plane separation of PGW as PGW-C and PGW-U, has been introduced as described in 3GPP TS 23.214 [117]. + +For UE IP address from the DN AAA server in the external PDN: If the AAA server in the external PDN is reachable only via the PGW-U, the PGW-U forward all the Diameter or RADIUS messages between the DN AAA server in the external PDN and the PGW-C, according to 3GPP TS 29.244 [114]. + +For UE IP address from DHCPv4/v6 server in the external PDN: If the DHCPv4/v6 server in the external PDN is reachable only via the PGW-U, the PGW-U forward all the DHCPv4/v6 messages between the DHCPv4/v6 server in the external PDN and the PGW-C. according to 3GPP TS 29.244 [114]. + +NOTE: If the DN AAA server or the DHCPv4/v6 server in the external PDN is reachable directly, then the PGW-C communicates with it directly, without involving the PGW-U. + +### 11.2.1.7 Support L2TP for CUPS across SGi + +L2TP (described in IETF RFC 2661 [118]) is a standard method for tunneling encapsulated Point-to-Point Protocol (PPP) frames over an IP network. L2TP operates between two L2TP endpoints (LAC and LNS), and tunnels PPP-encapsulated IP traffic between these endpoints. L2TP runs over UDP/IP and was originally defined for systems where PPP is used by an end-device to connect to a network (e.g. via DSL connections, or 2G/3G PPP PDP context). In these cases, a LAC could be deployed in the network (e.g. in a BNG or GGSN/PGW) to tunnel the PPP traffic to a server (LNS) over an IP network. + +For CUPS with the UE using IP PDN connection, the PPP functionality that is required to use L2TP is instead supported by the PGW-U, as illustrated in below figure. Upon receiving a PDN connection session establishment request from the UE via MME and SGW-C, PGW-C may depend on local L2TP configuration per APN or the received L2TP information from a DN AAA server in Access-Accept message, request the PGW-U to setup L2TP tunnel towards an L2TP network server (LNS) in the external DN and tunnel the PDN Connection user plane traffic in this L2TP tunnel. In this case the PGW-U acts as a L2TP access concentrator (LAC). + +To enable this, the PGW-C may provide L2TP tunnel information to the PGW-U as LAC, such as LNS IP address as described in 3GPP TS 29.244 [114]. This L2TP tunnel information may be configured on the PGW-C as part of the APN configuration or received from the DN-AAA server. Alternatively, the L2TP tunnel parameters may be configured in the PGW-U. The L2TP tunnel parameters include necessary parameters for setting up L2TP tunnel towards the LNS (e.g. LNS address, tunnel password). + +In addition, the PGW-C may provide PAP/CHAP authentication information to the PGW-U, for use in L2TP session establishment, in case it was received from the UE in the PCO or ePCO IE of the PDN Connection establishment request message. + +When L2TP is to be used for a PDN Connection, the PGW-C may select a PGW-U and requests the UE IP address to be allocated by LNS according to 3GPP TS 29.244 [114], the PGW-U (LAC) may retrieve this IP address from the LNS. + +![Diagram illustrating the L2TP Tunnel between CUPS and external DN. The diagram shows the flow of traffic from the UE through the RAN, MME, SGW-C, PGW-C, and PGW-U/LAC to the external DN, where it connects to the LNS. The L2TP tunnel is established between the PGW-U/LAC and the LNS. The EPC (Evolved Packet Core) is shown as a dashed box containing the MME, SGW-C, PGW-C, SGW-U, and PGW-U/LAC. The external DN is shown as a dashed circle containing the AAA server and LNS. The SGi interface is shown between the PGW-C and the external DN. The S1 interface is shown between the RAN and the MME. The S11 interface is shown between the MME and the SGW-C. The S5 interface is shown between the SGW-C and the PGW-C. The Sxa interface is shown between the SGW-C and the SGW-U. The Sxb interface is shown between the PGW-C and the PGW-U/LAC. The L2TP Tunnel is shown as a double-headed arrow between the PGW-U/LAC and the LNS.](ccdeaf31dbe65613f2f87a7b2b06e391_img.jpg) + +Diagram illustrating the L2TP Tunnel between CUPS and external DN. The diagram shows the flow of traffic from the UE through the RAN, MME, SGW-C, PGW-C, and PGW-U/LAC to the external DN, where it connects to the LNS. The L2TP tunnel is established between the PGW-U/LAC and the LNS. The EPC (Evolved Packet Core) is shown as a dashed box containing the MME, SGW-C, PGW-C, SGW-U, and PGW-U/LAC. The external DN is shown as a dashed circle containing the AAA server and LNS. The SGi interface is shown between the PGW-C and the external DN. The S1 interface is shown between the RAN and the MME. The S11 interface is shown between the MME and the SGW-C. The S5 interface is shown between the SGW-C and the PGW-C. The Sxa interface is shown between the SGW-C and the SGW-U. The Sxb interface is shown between the PGW-C and the PGW-U/LAC. The L2TP Tunnel is shown as a double-headed arrow between the PGW-U/LAC and the LNS. + +Figure 11f: L2TP Tunnel between CUPS and external DN + +Below figure describes the L2TP connection procedures between CUPS and external DN, upon the UE is accessed in EPS and the PGW-C and PGW-U has been negotiated supporting L2TP feature. + +![Sequence diagram showing L2TP connection procedures between CUPS and external DN. Lifelines: UE, PGW-C, PGW-U/LAC, DN AAA server, LNS (in external DN).](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PGW-C + participant PGW-U/LAC + participant DN AAA server + participant LNS as LNS (in external DN) + + Note over PGW-C, PGW-U/LAC: 0. L2TP Support Negotiation between PGW-C and PGW-U + PGW-C->>PGW-U/LAC: + PGW-U/LAC->>PGW-C: + + Note left of PGW-C: 1. PDN Connection Session Establishment Request (PCO:username, password) + UE->>PGW-C: + + PGW-C-->>DN AAA server: Access-Request/AAR + Note right of DN AAA server: 2. + DN AAA server-->>PGW-C: Access-Accept/AAA (LNS address, etc.) + + Note over PGW-C, PGW-U/LAC: 3. PFCP Session Establishment Request (L2TP Connection Information) + PGW-C->>PGW-U/LAC: + + rect rgb(240, 240, 240) + Note over PGW-U/LAC, LNS: 4. L2TP Tunnel Setup (if required) + PGW-U/LAC->>LNS: SCCRQ: Start-Control-Connection-Request + LNS->>PGW-U/LAC: SCCRP: Start-Control-Connection-Reply + PGW-U/LAC->>LNS: SCCCN: Start-Control-Connection-Connected + LNS->>PGW-U/LAC: ZLB ACK: Zero-Length Body Acknowledge + end + + rect rgb(240, 240, 240) + Note over PGW-U/LAC, LNS: 5. L2TP Session Setup + PGW-U/LAC->>LNS: ICRQ: Incoming-Call-Request + LNS->>PGW-U/LAC: ICRP: Incoming-Call-Reply + PGW-U/LAC->>LNS: ICCN: Incoming-Call-Connected + LNS->>PGW-U/LAC: ZLB ACK: Zero-Length Body Acknowledge + end + + Note over PGW-C, PGW-U/LAC: 6. PFCP Session Establishment Response (Created L2TP Connection) + PGW-U/LAC->>PGW-C: + + Note left of PGW-C: 7. PDN Connection Session Establishment Response + PGW-C->>UE: + + Note over UE, LNS: User Data Session + UE<->LNS: + +``` + +Sequence diagram showing L2TP connection procedures between CUPS and external DN. Lifelines: UE, PGW-C, PGW-U/LAC, DN AAA server, LNS (in external DN). + +**Figure 11g: L2TP connection procedures between CUPS and external DN** + +0. The PGW-C and the PGW-U negotiated supporting L2TP feature as specified in 3GPP TS 29.244 [114]. +1. The PGW-C receives a PDN Connection session establishment request from the UE via MME and SGW-C. + +The UE may include the authentication information for PAP and/or CHAP in PCO or ePCO IE. The PGW-C may locally configure the UE authentication information for a given APN. + +The PGW-C may determine that an L2TP session is required for the PDN Connection session based on local configured L2TP parameters per APN. + +2. The PGW-C may receive the L2TP Tunnel parameters (e.g. LNS IP address or FQDN, tunnel password) from the DN-AAA server in Access-Accept message or Diameter AAA message, or local configured. +3. If L2TP protocol is determined to support the PDN connection, the PGW-C selects a PGW-U supporting L2TP and be configured with the LAC name/addresses and then requests the PGW-U to setup an L2TP tunnel if needed and/or L2TP session towards the L2TP network server (LNS). + +The PGW-C sends PFCP Session Establishment Request to the PGW-U, which may include L2TP Tunnel Information for setting up a L2TP tunnel and L2TP session information to setup a L2TP session, together with the information for authentication used during L2TP Tunnel setup, as well as for L2TP session. + +The L2TP Tunnel Information includes LNS IPv4 address or IPv6 address of LNS, Tunnel Password. + +The L2TP Session Information includes specific information related to the PDN Connection, e.g. a Calling Number which may be set to UE's MSISDN, an indication to instruct that the PGW-U shall request the LNS to allocate an IP address for the PDN session, indications to instruct that the PGW-U shall request the LNS to provide DNS server addresses or NBNS server addresses etc. as specified in 3GPP TS 29.244 [114]. + +4. The PGW-U checks if any existing L2TP tunnel can be used to serve the PDN Connection according to the information provided in the L2TP Tunnel Information. + +If the PGW-U decides to setup a new L2TP tunnel, it initiates L2TP Tunnel establishment by sending an SCCRQ (Start-Control-Connection-Request) message towards the LNS, the PGW-U will allocate a Tunnel ID, and it may include a CHAP Challenge to authenticate the LNS. The Challenge and Challenge Response (to be included in SCCCN) is produced by the PGW-U using the Tunnel Password received from the PGW-C. + +The LNS responds with an SCCRP (Start-Control-Connection-Reply) message, containing its allocated Tunnel ID and a CHAP Challenge Response to the Challenge in SCCRQ. + +The PGW-U then responds with a Challenge response for tunnel authentication in the SCCCN (Start-Control-Connection-Connected) message. An L2TP tunnel is established after the tunnel authentication is successful, with the reception of the SCCCN message sent by the PGW-U to the LNS. + +If the PGW-U decides to use an already existing L2TP tunnel for the requested PDN Connection from the PGW-C, it proceeds with step 5 below directly without current step. + +5. Once the L2TP Tunnel is established (or already present) between the PGW-U and the LNS for the PDN Connection requested by the UE, the PGW-U proceeds with L2TP session setup towards the LNS. + +The PGW-U sends an ICRQ (Incoming-Call-Request) message towards the LNS, which contains the Tunnel ID assigned by the LNS, its assigned Session ID, and optionally, the Calling Number and Called Number. The LNS responds with an ICRP (Incoming-Call-Reply) message and provides the Session ID assigned by it to the LAC. + +The PGW-U then sends an ICCN (Incoming-Call-Connected) message. If proxy LCP and authentication are employed, the ICCN message includes the link control parameters (e.g. MRU) and UE authentication information sent from the PGW-C which was received via PCO or ePCO IE in step 1. In addition, the PGW-U (LAC) will act as a PPP endpoint to use IPCP to request UE IP Address, DNS server address and/or NBNS server address(es). + +The LCP renegotiation may be triggered by the LNS after receiving the ICCN message. If so, the LAC and LNS will use PPP LCP to communicate link specific control parameter (e.g. MRU), and indicate authentication type, then either PPP PAP/CHAP takes place. The PPP IPCP transactions takes place to retrieve UE IP Address, DNS server address and/or NBNS server address. + +6. The status of the L2TP session setup is sent by the PGW-U to the PGW-C in a PFCP Session Establishment Response. +7. The PGW-C sends a PDU Session Establishment Response to the UE and the user data session is initiated, which may contain the DNS and NBNS Server information. + +## 11.2.2 Access to networks handling Non-IP data services through Packet Domain + +The support of Non-IP data is part of the CIoT EPS optimisations (see 3GPP TS 23.401 [77]) and 3GPP TS 23.060 [3]). A PDN/PDP Type "Non-IP" is used for Non-IP data. The Non-IP data delivery to the network handling Non-IP data services is accomplished by one of two mechanisms: + +- Delivery using SCEF +- Delivery using a Point-to-Point (PtP) SGi tunnel + +Data delivery using SCEF is further described in 3GPP TS 29.128 [110]. + +In order to allow Non-IP delivery data using SGi PtP tunnelling based on UDP/IP (see subclause 11.8), the Packet Domain may offer direct transparent access to the Non-IP Packet Data Network with the following characteristics: + +- The IPv4 address and/or IPv6 prefix is assigned as part of the PDN connection establishment and identifies the PDN connection of the UE within the PLMN domain. +- IP address allocation procedures for the UE (i.e. PDN connection) are performed by the GGSN/P-GW based on APN configuration. Only a single IP address is used (i.e. either IPv4 or IPv6 prefix+Interface Identifier is allocated/assigned). In case of IPv6 the GGSN/P-GW assigns an Interface Identifier for the PDN connection. The IP address or IP prefix is not provided to the UE (i.e. SLAAC / Router Advertisements are not performed. DHCP or DHCPv6 are not used). +- The assigned IPv4 address or IPv6 prefix is used for UDP/IP encapsulation for PtP tunneling between the Non-IP network and the GGSN/P-GW (see subclause 11.8). +- Stateless Address Autoconfiguration does not apply for IPv6. Both IPv4 and IPv6 addresses belong to the operator addressing space. + +User authentication and encryption of user data when accessing networks handling Non-IP data services is outside 3GPP specification. + +## 11.3 Numbering and Addressing + +In the case of interworking with public IP networks (such as the Internet), the PLMN operator shall use public network addresses. These public addresses can be reserved from the responsible IP numbering body, or from an ISP with which the PLMN operator has an agreement. In case of IPv6, a global IPv6 prefix can be obtained from the same sources. + +In the case of interworking with private IP networks, two scenarios can be identified: + +1. the PLMN operator manages internally the subnetwork IPv4 addresses and/ or IPv6 prefixes as applicable. Each private network is assigned a unique subnetwork IPv4 addresses and/ or IPv6 prefixes. Normal routing functions are used to route packets to the appropriate private network; +2. each private network manages its own addressing. In general this will result in different private networks having overlapping address ranges. A logically separate connection (e.g. an IP in IP tunnel or layer 2 virtual circuit) is used between the GGSN/P-GW and each private network. In this case the IP address alone is not necessarily unique. The pair of values, Access Point Name (APN) and IPv4 address and/or IPv6 prefixes, is unique. + +NOTE 1: In IPv6, "site-local addresses" were originally designed to be used for addressing inside of a site that is similar to the usage of "private addresses" in IPv4. The usage of "site-local-addresses" is deprecated as specified in RFC 4291 [82]. Existing implementations and deployments may continue using site-local addresses. However, in new implementations the prefix that was allocated for "site local addresses" shall be treated as for "global unicast addresses", see RFC 4291 [82]. + +The PLMN operator allocates the IP addresses for the subscribers in either of the following ways. + +- The PLMN operator allocates a static IPv4 address and/or a static IPv6 prefix when the subscription record is built. The IPv4 address and/or IPv6 prefix are respectively reserved from a pool of free IPv4 addresses and/or IPv6 prefixes. Each external network has its own pool of IPv4 addresses and/or IPv6 prefixes. +- The PLMN operator allocates (either on its own or in conjunction with the external network) a dynamic IPv4 address and/or a dynamic IPv6 prefix as described in 3GPP TS 23.060 [3], 3GPP TS 23.401 [77] and 3GPP TS 23.402 [78]. + +For UEs used for Machine-Type Communications (MTC) as described in 3GPP TS 23.401 [77] and 3GPP TS 23.060 [3] and Cellular Internet of Things (CIoT) as described in 3GPP TS 23.401 [77] and 3GPP TS 23.060 [3], IPv6 address allocation should be the primary mechanism for IP address allocation. IPv4 based address allocation is considered a transition solution and is deprecated for MTC used over 3GPP accesses. + +NOTE 2: For implementation guidelines related to transition and other aspects of IPv4 address usage see 3GPP TS 23.221 [99] Annex B. + +In case of transferring Non-IP data over SGi PtP tunnelling based on UDP/IP (see subclause 11.8) the PLMN operator uses private network addresses for the establishment of the tunnel. + +## 11.4 Charging + +The PLMN operator may define the accuracy of the charging mechanism using one of the following categories: + +- every source/destination pair is logged separately; +- source/destination pairs are logged to an accuracy of subnetworks; +- source/destination pairs are logged to an accuracy of connection types (e.g., external data network, corporate network, another mobile). + +## 11.5 Domain Name System Server (DNS Server) + +Provision of Domain Name services shall be provided by the PLMN operators in the transparent case and the ISP in the non transparent case. For non-EPS networks see 3GPP TS 23.060 [3] (DNS documentation is provided in RFC 1034 [19] and RFC 1035 [58]) and for EPS networks see 3GPP TS 29.303 [96]. + +## 11.6 Screening + +The way the PLMN is performing the operator controlled screening and the subscription controlled screening is out of the scope of the present document. These functions may be done, for example, in a firewall. + +## 11.7 IP Multicast access + +NOTE: This section is applicable only to GERAN and UTRAN. + +The Packet Domain could allow access to IP Multicast traffic coming from an external network. The support of IP-Multicast in the Packet Domain is optional. + +In order for the Packet Core Network to support Multicast traffic that will allow the MS/UE to subscribe to multicast groups from outside the PLMN, the GGSN/P-GW shall support IGMP (IPv4) and/or MLD (IPv6) and one or more Inter-Router Multicast protocols, such as DVMRP, MOSPF, or PIM-SM. + +IGMP/MLD is an integral part of IP. All hosts wishing to receive IP multicasts are required to implement IGMP (or equivalent) and class-D IPv4 addresses or MLD and IPv6 multicast according to RFC 2710 [48]. IGMP/MLD messages are encapsulated in IP datagrams. + +To be able to deliver IP-Multicast packets to the appropriate Tes, the GGSN/P-GW may have an IP-Multicast proxy functionality. + +The IP-Multicast proxy will perform the following tasks: + +NOTE: In this example it is assumed that IGMP/MLD is used as a Host-Router Multicast protocol. + +- maintain a list of mobiles that joined one or more Multicast groups. This list is built/updated each time the GGSN/P-GW receives an IGMP Join or MLD Report message from the mobile; +- send, based on this maintained list of mobiles, multicast routing information to the routers attached to the Packet Domain, allowing them to route multicast packets; +- upon reception by the GGSN/P-GW of multicast packets, make and send a copy as Point-to-Point packets, to each mobile of the group. + +IP-Multicast traffic can only be handled after an MS/UE has attached to the Packet Domain, and a bearer (e.g. Activated PDP context(s)) (including possibly authentication) pointing to the preferred ISP/external network for this purpose. The Multicast traffic is handled at the application level from a Packet Domain perspective and is sent over UDP/IP. + +Figure 12 depicts the protocol configuration for handling Multicast traffic (control plane) for the non-EPC based domain case. The Multicast traffic handling affects the GGSN by the introduction of the IP-Multicast proxy and the support for an Inter-Router Multicast protocol and a host-router multicast protocol. If the protocol configuration for + +handling Multicast traffic (control plane) is applied for Sgi (i.e EPC based packet domain), the P-GW has the functionality of GGSN and Sgi corresponds to the Gi in Figure 12. + +![Figure 12: Protocol configuration for IP-Multicast handling (control plane). The diagram shows four main entities: TE+MT, SGSN, GGSN, and Intranet/ISP. TE+MT contains IP-M Application, IGMP, and IP layers. SGSN contains IP-M Proxy, IGMP, and IP layers. GGSN contains IP-M Proxy, PIM (or equiv), IP, and Lower layers. Intranet/ISP contains PIM (or equiv), IP, and Lower layers. A dashed line connects the IP-M Application in TE+MT to an IP-M application server in Intranet/ISP, passing through the IP-M Proxy in GGSN. A vertical dashed line labeled 'Gi' separates the GGSN and Intranet/ISP. A 'Packet Domain bearer' is shown between TE+MT and GGSN.](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg) + +Figure 12: Protocol configuration for IP-Multicast handling (control plane). The diagram shows four main entities: TE+MT, SGSN, GGSN, and Intranet/ISP. TE+MT contains IP-M Application, IGMP, and IP layers. SGSN contains IP-M Proxy, IGMP, and IP layers. GGSN contains IP-M Proxy, PIM (or equiv), IP, and Lower layers. Intranet/ISP contains PIM (or equiv), IP, and Lower layers. A dashed line connects the IP-M Application in TE+MT to an IP-M application server in Intranet/ISP, passing through the IP-M Proxy in GGSN. A vertical dashed line labeled 'Gi' separates the GGSN and Intranet/ISP. A 'Packet Domain bearer' is shown between TE+MT and GGSN. + +Figure 12: Protocol configuration for IP-Multicast handling (control plane) + +## 11.8 Non-IP data transferring over SGi + +### 11.8.1 General + +When support of Non-IP data is provided at the Gi/SGi interface, different Point-to-Point (PtP) tunneling techniques may be used. When using PtP tunneling by UDP/IP encapsulation subclause 11.8.2 below shall be followed. Other techniques as described in clause 11.8.3 below may be used. + +The Gi/SGi based Non-IP data delivery is applicable to the User Plane C IoT EPS Optimization and the Control Plane C IoT EPS Optimization (see 3GPP TS 23.401 [77] and 3GPP TS 23.060 [3]). + +### 11.8.2 Gi/SGi PtP tunnelling based on UDP/IP + +Gi/SGi PtP tunnelling based on UDP/IP may be used to deliver Non-IP data to an AS via Gi/SGi. + +The PtP tunnel is set up by configuration of tunnel parameters in both end of the tunnel. + +The following parameters are pre-configured in the GGSN/P-GW per APN; + +- the UDP destination port number to use when sending Non-IP data; +- the UDP port number it wants to receive Non-IP data; +- the destination IP address to be used for sending Non-IP data. + +NOTE 1: Many APNs can resolve to the same P-GW, but each APN can be unique to a particular AS. + +The following is pre-configured in the AS; + +- the UDP destination port number to use when sending Non-IP data; +- the UDP port number it wants to receive Non-IP data. + +NOTE 2: The GGSN/P-GW as well as the AS can use any UDP port numbers not assigned by IANA. The port numbers used need to be aligned between peers. + +IP address allocation procedures for the UE (i.e. PDN connection) are performed by the GGSN/P-GW as described in subclause 11.2.2. + +The UE IP address for the PDN connection or IPv6 prefix allocated for the PDN connection+suffix assigned for the PtP tunnel end point in the GGSN/P-GW is used as source address in the GGSN/P-GW and as destination address in the AS for the PtP tunnel. + +During the PDP context/PDN connection establishment, the GGSN/P-GW associates the GTP-U tunnel for the PDP context/PDN connection with the Gi/SGi PtP tunnel. The GTP-U tunnel with PDP/PDN type “Non-IP” is used. + +The GGSN/P-GW acts as a transparent forwarding node between the UE used for CIoT and the AS. + +NOTE 3: The UE can include application level identity to AS, what kind of identity is out of scope of this specification. + +For uplink delivery, if the uplink data is received from the GTP-U tunnel the GGSN/P-GW shall forward the received data to the AS over the Gi/SGi PtP tunnel associated with the GTP-U tunnel using UDP/IP encapsulation with the destination address of the AS and the configured UDP destination port number for “Non-IP” data as described above. + +For downlink delivery, the AS shall send the data using UDP/IP encapsulation with the IP address or IPv6 prefix+suffix of the UE as destination address and the configured UDP destination port number for “Non-IP” data as described above. + +NOTE 3: The UDP source port number to use for both uplink and downlink Non-IP data transfer can be a pre-configured or a locally allocated port number in the GGSN/P-GW and AS respectively. + +NOTE 4: For downlink delivery, the GGSN/P-GW decapsulates the received data (i.e. removes the UDP/IP headers) and forwards the data to SGSN/S-GW on the GTP-U tunnel identified by the IP address or the IPv6 prefix of the UE (i.e. PDN connection) for delivery to the UE. + +![Figure 11.8: Protocol configuration for Non-IP data (user plane) using SGiPtP tunneling. The diagram shows three main entities: S-GW, P-GW, and AS. The S-GW and P-GW are connected via S5/S8 interfaces, and the P-GW is connected to the AS via an SGi interface. The protocol stack is shown in layers: Non-IP, UDP, IP, L2, and L1. The S-GW and P-GW have 'Relay' blocks at the top. The S-GW's relay block contains two GTP-U entries. The P-GW's relay block contains one GTP-U entry and one UDP entry. The AS has a single column for its protocol stack. Horizontal lines connect the layers between adjacent entities.](b4f6d3668f7e851eaff07ccf26001623_img.jpg) + +Figure 11.8: Protocol configuration for Non-IP data (user plane) using SGiPtP tunneling. The diagram shows three main entities: S-GW, P-GW, and AS. The S-GW and P-GW are connected via S5/S8 interfaces, and the P-GW is connected to the AS via an SGi interface. The protocol stack is shown in layers: Non-IP, UDP, IP, L2, and L1. The S-GW and P-GW have 'Relay' blocks at the top. The S-GW's relay block contains two GTP-U entries. The P-GW's relay block contains one GTP-U entry and one UDP entry. The AS has a single column for its protocol stack. Horizontal lines connect the layers between adjacent entities. + +**Figure 11.8: Protocol configuration for Non-IP data (user plane) using SGiPtP tunneling** + +![Figure 11.9: Protocol configuration for Non-IP data (user plane) using Gi PtP tunneling. The diagram shows three main entities: SGSN, GGSN, and AS. The SGSN and GGSN are connected via Gn/Gp interfaces, and the GGSN is connected to the AS via a Gi interface. The protocol stack is shown in layers: Non-IP, UDP, IP, L2, and L1. The SGSN and GGSN have 'Relay' blocks at the top. The SGSN's relay block contains two GTP-U entries. The GGSN's relay block contains one GTP-U entry and one UDP entry. The AS has a single column for its protocol stack. Horizontal lines connect the layers between adjacent entities.](0b452c5334567cbdc22ee9817e1246f5_img.jpg) + +Figure 11.9: Protocol configuration for Non-IP data (user plane) using Gi PtP tunneling. The diagram shows three main entities: SGSN, GGSN, and AS. The SGSN and GGSN are connected via Gn/Gp interfaces, and the GGSN is connected to the AS via a Gi interface. The protocol stack is shown in layers: Non-IP, UDP, IP, L2, and L1. The SGSN and GGSN have 'Relay' blocks at the top. The SGSN's relay block contains two GTP-U entries. The GGSN's relay block contains one GTP-U entry and one UDP entry. The AS has a single column for its protocol stack. Horizontal lines connect the layers between adjacent entities. + +**Figure 11.9: Protocol configuration for Non-IP data (user plane) using Gi PtP tunneling.** + +### 11.8.3 Other SGi PtP tunnelling mechanisms + +SGi PtP tunnelling mechanisms such as PMIPv6/GRE, L2TP, GTP-C/U, etc, may be used to deliver Non-IP data to AS via SGi. + +The PtP tunnel is established towards the AS by the P-GW. Depending on the type of protocol employed on the SGi PtP tunnel, the SGi PtP tunnel setup may be done at the time of attach or at the time of first MO datagram being sent by the CIoT UE. + +The P-GW selects the AS based on the P-GW configuration (eg. per APN, or per PtP tunnel type etc). + +NOTE: IP address allocation procedures for the UE are not performed by the P-GW. + +For uplink Non-IP data, the P-GW forwards the received data to the AS over the established SGi PtP tunnel. + +For downlink Non-IP data, the AS locates the right SGi PtP tunnel for the UE (using information such as UE identifiers in the Non-IP protocol itself, etc) to forward the data. The AS sends the data to P-GW over the established SGi PtP tunnel. The P-GW then sends the data to S-GW on the GTP-U tunnel identified by the associated SGi PtP tunnel for delivery to the UE. + +## 11.9 Transport Level Marking + +Based on operator policy, the transport level packet marking (e.g. setting the DiffServ Code Point) by the P-GW in the uplink may be based on the QCI, and optionally the ARP priority level, of the associated EPS bearer. + +--- + +## 12 Interworking with PDN (PPP) + +### 12.1 General + +By means of the PDP type 'PPP' Packet Domain may support interworking with networks based on the point-to-point protocol (PPP), as well as with networks based on any protocol supported by PPP through one of its Network Control Protocols (NCPs). All protocols currently supported by PPP NCPs are listed in RFC 1661 [21a] and RFC 1662 [21b]. It may also support interworking by means of tunnelled PPP, by e.g. the Layer Two Tunnelling Protocol (L2TP). + +### 12.2 PDN Interworking Model + +The interworking point is at the Gi reference point. The GGSN for interworking with the ISP/PDN is the access point of the Packet Domain (see figure 13). The GGSN will either terminate the PPP connection towards the MS or may further relay PPP frames to the PDN. The PPP frames may be tunnelled in e.g. L2TP. + +![Figure 13: The protocol stacks for the Gi PPP reference point. The diagram shows a GGSN (dashed box) and a Packet Domain Bearer. Inside the GGSN, the stack consists of PPP, PPP-NCP supported protocol or PPP, and a stack of e.g. L2TP, UDP, and IP. The Packet Domain Bearer is connected to the PPP layer. The Gi interface is shown on the right side of the GGSN.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +The diagram illustrates the protocol stack for the Gi PPP reference point. A dashed box labeled 'GGSN' contains a 'PPP' layer, a 'PPP-NCP supported protocol or PPP' layer, and a stack of 'e.g. L2TP', 'UDP', and 'IP'. Below the GGSN box is a 'Packet Domain Bearer' layer. To the right of the GGSN box is the 'Gi' interface. At the bottom of the GGSN box, there are 'L2' and 'L1' layers. + +Figure 13: The protocol stacks for the Gi PPP reference point. The diagram shows a GGSN (dashed box) and a Packet Domain Bearer. Inside the GGSN, the stack consists of PPP, PPP-NCP supported protocol or PPP, and a stack of e.g. L2TP, UDP, and IP. The Packet Domain Bearer is connected to the PPP layer. The Gi interface is shown on the right side of the GGSN. + +**Figure 13: The protocol stacks for the Gi PPP reference point** + +In case the external PDN is an IP based network and the GGSN terminates PPP the same description applies as specified in subclause 11.2. + +In case the GGSN tunnels PPP frames to the PDN, the GGSN may behave like a LAC towards the external network. + +### 12.2.1 Virtual dial-up- and direct Access to PDNs, or ISPs through Packet Domain + +The access to PDNs, or ISPs may involve specific functions such as: user authentication, user's authorization, end to end encryption between MS and PDN/ISP, allocation of a dynamic address belonging to the PLMN/PDN/ISP addressing space, etc. + +For this purpose the PLMN may offer, based on configuration data: + +- direct access to an IP based Intranet/ISP using a protocol configuration as depicted in figure 14. Here DHCP and/or RADIUS are used between the GGSN and Intranet/ISP for performing the specific functions mentioned above. The Packet Domain may also offer access to networks based on any protocol supported by PPP through one of its Network Control Protocols (NCPs); + +![Figure 14: Protocol stack for direct access to IP-based Intranets/ISPs. The diagram shows five entities: TE, MT, SGSN, GGSN, and Intranet/ISP. The TE has a PPP layer and a Phy. layer. The MT has a Packet Domain bearer layer. The SGSN has a Packet Domain bearer layer. The GGSN has a PPP layer, a DHCP/RADIUS layer, a UDP layer, an IP layer, and Lower layers. The Intranet/ISP has a DHCP/RADIUS layer, a UDP layer, an IP layer, and Lower layers. The Packet Domain bearer layer is shared between the MT and the SGSN.](5c65cabec7c5062117fb0d578916cf8b_img.jpg) + +The diagram illustrates the protocol stack for direct access to IP-based Intranets/ISPs. It shows five entities: TE, MT, SGSN, GGSN, and Intranet/ISP. The TE has a 'PPP' layer and a 'Phy. layer'. The MT has a 'Packet Domain bearer' layer. The SGSN has a 'Packet Domain bearer' layer. The GGSN has a 'PPP' layer, a 'DHCP/RADIUS' layer, a 'UDP' layer, an 'IP' layer, and 'Lower layers'. The Intranet/ISP has a 'DHCP/RADIUS' layer, a 'UDP' layer, an 'IP' layer, and 'Lower layers'. The 'Packet Domain bearer' layer is shared between the MT and the SGSN. + +Figure 14: Protocol stack for direct access to IP-based Intranets/ISPs. The diagram shows five entities: TE, MT, SGSN, GGSN, and Intranet/ISP. The TE has a PPP layer and a Phy. layer. The MT has a Packet Domain bearer layer. The SGSN has a Packet Domain bearer layer. The GGSN has a PPP layer, a DHCP/RADIUS layer, a UDP layer, an IP layer, and Lower layers. The Intranet/ISP has a DHCP/RADIUS layer, a UDP layer, an IP layer, and Lower layers. The Packet Domain bearer layer is shared between the MT and the SGSN. + +**Figure 14: Protocol stack for direct access to IP-based Intranets/ISPs** + +- virtual dial-up access to a PDN with PPP frame tunnelling as depicted in figure 15. + +![Figure 15: Protocol stack for virtual dial-up access with PPP frame tunnelling. The diagram shows five entities: TE, MT, SGSN, GGSN (LAC), and LNS. The TE has a stack of PPP and Phy. layer. The MT has a Packet Domain bearer. The GGSN (LAC) has a stack of PPP, e.g. L2TP, UDP, IP, and Lower layers. The LNS has a stack of e.g. L2TP, UDP, IP, and Lower layers. The MT and GGSN (LAC) are connected via the Packet Domain bearer.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +| TE | MT | SGSN | GGSN (LAC) | LNS | +|------------|----------------------|------|--------------|--------------| +| PPP | Packet Domain bearer | | PPP | e.g. L2TP | +| Phy. layer | | | Lower layers | Lower layers | + +Figure 15: Protocol stack for virtual dial-up access with PPP frame tunnelling. The diagram shows five entities: TE, MT, SGSN, GGSN (LAC), and LNS. The TE has a stack of PPP and Phy. layer. The MT has a Packet Domain bearer. The GGSN (LAC) has a stack of PPP, e.g. L2TP, UDP, IP, and Lower layers. The LNS has a stack of e.g. L2TP, UDP, IP, and Lower layers. The MT and GGSN (LAC) are connected via the Packet Domain bearer. + +**Figure 15: Protocol stack for virtual dial-up access with PPP frame tunnelling** + +### 12.2.1.1 Procedural description + +In this case: + +- the MS is given an address belonging to the Intranet/ISP addressing space. The address is given either at subscription in which case it is a static address or at PDP context activation in which case it is a dynamic address. This address is used for packet forwarding within the GGSN and for packet forwarding on the Intranet/ISP. This requires a link between the GGSN and an address allocation server, such as AAA, or DHCP, belonging to the Intranet/ISP; +- the communication between the Packet Domain and the Intranet/ISP may be performed over any network, even an insecure e.g. the Internet. In case of an insecure connection between the GGSN and the Intranet/ISP there may be a specific security protocol in between. This security protocol is defined by mutual agreement between PLMN operator and Intranet/ISP administrator. + +The following description bullet items describe the signal flow. + +- 1) The TE sends an AT-command to the MT to set up parameters. +- 2) The MT sends the Activate PDP context request message to the SGSN which sends the Create PDP context request message to the chosen GGSN. +- 3) The GGSN deduces from the APN: + - the server(s) to be used for address allocation and authentication; + - the protocol such as RADIUS, DHCP or L2TP to be used with this / those server(s); + - the communication and security feature needed to dialogue with this / those server(s) e.g. tunnel ,IPSec security association, dial-up connection (using possibly PPP). + +As an example the GGSN may use one of the following options: + +- RADIUS for authentication and IP-address allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the GGSN; + - RADIUS for authentication and DHCP for host configuration and address allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the GGSN. After a successful authentication, the DHCP client discovers the DHCP server(s) in the ISP/Intranet and receives host configuration data; + - L2TP for forwarding PPP frames to a L2TP Network Server. +- 4) The GGSN sends back to the SGSN a Create PDP Context Response message. + - 5) Depending on the cause value received in the Create PDP Context Response the SGSN may either send the Activate PDP Context Accept message or send the Activate PDP Context Reject message to the MS. + +- 6) The MT responds with an AT-response that may indicate whether the context activation was successful or not. In the case of a non-successful context activation the response may also indicate the cause. + +In case of a successful context activation, the TE will start its PPP protocol after the LLC link has been established. The LCP, Authentication and NCP negotiations are then carried out. During these negotiations the GGSN may acknowledge values, for any LCP options related to 'L2' framing (e.g. 'ACCM', 'ACFC' and 'FCS-Alternatives'), as proposed by the MT, which itself is forwarding these negotiations from the TE. + +NOTE: With the "PPP" the MT may provide a PPP relay (or proxy) function between the TE and GGSN. This gives the opportunity for the MT to intercept the 'L2' framing end to end negotiations. + +EXAMPLE: In the following example the successful PDP context activation is shown. + +![Sequence diagram of PDP context activation showing interactions between TE, MT, SGSN, GGSN, and Intranet/ISP.](458fdbcb4015a4ee90bd84809afc4aac_img.jpg) + +``` + +sequenceDiagram + participant TE + participant MT + participant SGSN + participant GGSN + participant Intranet/ISP + + Note left of TE: AT-Commands + TE->>MT: AT-Commands + MT->>SGSN: Activate PDP Context Req. + SGSN->>GGSN: Create PDP Context req. + GGSN->>SGSN: Create PDP Context Resp. + SGSN->>MT: Activate PDP Context Acc. + MT->>TE: AT-Response + Note left of TE: LCP, Authentication and IPCP negotiation + TE->>GGSN: LCP, Authentication and IPCP negotiation + GGSN->>Intranet/ISP: RADIUS/DHCP or L2TP negotiation + Intranet/ISP->>GGSN: RADIUS/DHCP or L2TP negotiation + +``` + +The diagram illustrates the sequence of messages for a successful PDP context activation. It starts with the TE sending 'AT-Commands' to the MT. The MT then sends an 'Activate PDP Context Req.' to the SGSN. The SGSN forwards this as a 'Create PDP Context req.' to the GGSN. The GGSN responds with a 'Create PDP Context Resp.' to the SGSN, which in turn sends an 'Activate PDP Context Acc.' back to the MT. The MT then sends an 'AT-Response' back to the TE. Following this, the TE initiates 'LCP, Authentication and IPCP negotiation' directly with the GGSN. The GGSN then performs 'RADIUS/DHCP or L2TP negotiation' with the Intranet/ISP. + +Sequence diagram of PDP context activation showing interactions between TE, MT, SGSN, GGSN, and Intranet/ISP. + +Figure 16a + +## 13 Interworking with PDN (DHCP) + +### 13.1 General + +In current LAN environments the most commonly used configuration protocol is DHCP (Dynamic Host Configuration Protocol, RFC 2131 [26]) and DHCPv6 (Dynamic Host Configuration Protocol for IPv6, IETF RFC 3315 [46]). It provides a mechanism for passing a large set of configuration parameters to hosts connected to a TCP/IP network (IP address, sub-net mask, domain name, MTU, etc.) in an automatic manner. Moreover DHCP may assign IP addresses to clients for a finite lease time, allowing for sequential reassignment of addresses to different users. + +The lease time is chosen by the administrator of the DHCP server (in the external network), and is therefore out of the scope of the present document. + +The Packet Domain may obtain IP address via external DHCP server during the packet bearer establishment procedures (e.g. PDP Context activation, default bearer establishment). The GGSN/P-GW acts as a DHCP client towards the external DHCP server. + +The Packet Domain offers the end user the possibility to run DHCP end-to-end the same way as he does when connected directly to a LAN (e.g. an enterprise Intranet). No modifications should be required in common implementations of DHCP clients and servers. However in non-EPC based Packet Domain, a DHCP relay agent function is needed in the GGSN so as to allow correct routing of DHCP requests and replies between the TE and the DHCP servers. In EPC based Packet Domain for 3GPP access networks, the P-GW acts a DHCP server towards the UE and it acts as a DHCP client towards the external DHCP server. For trusted non-3GPP access networks, the non-3GPP access network may act as a DHCP relay or DHCP server. In the trusted WLAN access network, the TWAN acts a DHCP server towards the UE and PGW acts as a DHCP client towards the external DHCP server for the GTP/PMIP-based S2a. + +In non-EPC based Packet Domain, at PDP context activation no IP address is allocated, this is done afterwards through DHCP. After the TE's configuration has been completed by DHCP, the PDP context is updated by means of the GGSN-initiated PDP Context Modification Procedure in order to reflect the newly assigned IP address. + +In the following cases the bearer associated with the allocated IP address (i.e. IPv4 address or IPv6 prefix) shall be released: + +- if the DHCP lease expires; +- if the DHCP renewal is rejected by the DHCP server; +- if the IP address is changed during the renewal process. Usually when the lease is renewed, the IP address remains unchanged. However, if for any reason (e.g. poor configuration of the DHCP server), a different IP address is allocated during the lease renewal process the associated bearer shall be released. + +## 13.2 PDN Interworking Model of GGSN for DHCP + +A DHCP relay agent shall be located in the GGSN used for interworking with the IP network as illustrated in the following figure 16b. + +![Diagram of the protocol stack for the Gi IP reference point for DHCP. The diagram shows a GGSN box containing a DHCP Relay Agent, UDP, IP, L2, and L1 layers. To the left is the Packet Domain Bearer, and to the right is the Gi interface.](9e4f582a5d5f6742d1372956db0f8f0b_img.jpg) + +The diagram illustrates the protocol stack for the Gi IP reference point for DHCP. A dashed box labeled "GGSN" contains the following components from top to bottom: + + +- A **DHCP Relay Agent** (represented by a box with a downward-pointing triangle at the top). +- Two **UDP** protocol blocks. +- Two **IP** protocol blocks. +- An **L2** (Link Layer) block. +- An **L1** (Physical Layer) block. + + To the left of the GGSN box is a large box labeled **Packet Domain Bearer**. To the right of the GGSN box is a vertical dashed line labeled **Gi**, representing the interface to the external IP network. The L1 block in the GGSN stack is connected to the Gi interface. + +Diagram of the protocol stack for the Gi IP reference point for DHCP. The diagram shows a GGSN box containing a DHCP Relay Agent, UDP, IP, L2, and L1 layers. To the left is the Packet Domain Bearer, and to the right is the Gi interface. + +**Figure 16b: The protocol stacks for the Gi IP reference point for DHCP** + +The DHCP relay agent relays the requests received from the DHCP client to the DHCP server(s), and the replies received from the server(s) to the corresponding client. The DHCP relay agent allows for the replies from DHCP servers to be delivered to the correct terminal, as the logical connection from the MT terminates in the GGSN, and consequently only the GGSN holds enough information to locate the DHCP client. How the DHCP relay agent identifies the MT based on the DHCP messages is out of the scope of 3GPP standardisation. + +DHCP provides mechanisms for user authentication and integrity protection, but does not offer any message confidentiality, therefore additional mechanisms (e.g. Ipsec tunnel) may be provided if the link towards the external network is not secure. However this is out of the scope of the present document. + +Apart from the particulars mentioned above, this model is basically the same as the one for interworking with IP networks described elsewhere in the present document. Using DHCP corresponds to the transparent access case as the GGSN does not take part in the functions of authentication, authorisation, address allocation, etc. + +### 13.2.1 Address allocation by the Intranet or ISP + +The MS is given an address belonging to the Intranet/ISP addressing space. The address is given dynamically immediately after the PDP context activation. This address is used for packet forwarding between the Intranet/ISP and the GGSN and within the GGSN. + +The MS may authenticate itself to the Intranet/ISP by means of the relevant DHCP procedures (see RFC 3118 [45]). + +The protocol configuration options are retrieved from the DHCP server belonging to the Intranet/ISP. + +![Figure 16c: Protocol stack for access with DHCP end-to-end. The diagram shows the protocol stacks for TE, MT, SGSN, GGSN, and Intranet/ISP. The TE and MT stacks are identical, consisting of DHCP Client, UDP, IP, and Phy. layers. The GGSN stack consists of a DHCP Relay Agent, UDP, IP, and Lower layers. The Intranet/ISP stack consists of a DHCP Server, UDP, IP, and Lower layers. The MT, SGSN, and GGSN are connected via a Packet Domain bearer, which is supported by Lower layers in the GGSN.](71b0a68b4dd64961465d2b0e790538de_img.jpg) + +| TE | MT | SGSN | GGSN | Intranet/ISP | +|-------------|----------------------|------|------------------|--------------| +| DHCP Client | | | DHCP Relay Agent | DHCP Server | +| UDP | | | UDP | UDP | +| IP | | | IP | IP | +| Phy. layers | Packet Domain bearer | | Lower layers | Lower layers | + +Figure 16c: Protocol stack for access with DHCP end-to-end. The diagram shows the protocol stacks for TE, MT, SGSN, GGSN, and Intranet/ISP. The TE and MT stacks are identical, consisting of DHCP Client, UDP, IP, and Phy. layers. The GGSN stack consists of a DHCP Relay Agent, UDP, IP, and Lower layers. The Intranet/ISP stack consists of a DHCP Server, UDP, IP, and Lower layers. The MT, SGSN, and GGSN are connected via a Packet Domain bearer, which is supported by Lower layers in the GGSN. + +**Figure 16c: Protocol stack for access with DHCP end-to-end** + +#### 13.2.1.1 Address allocation using DHCPv4 + +The following description bullet items describe the DHCPv4 signal flow. For a detailed description of the DHCP messages refer to RFC 2131 [26] and RFC 1542 [27]. The end-to-end protocol configuration is depicted in figure 16c. + +- 1) The TE and MT exchange several AT commands carrying the QoS and other parameters requested by the TE, and requesting the activation of a PDP context of PDP type IP. The TE selects the APN of the configured Intranet/ISP offering a DHCP service, or the APN consisting of the Reserved Service Label for DHCP that the user has subscribed to. In the latter case the TE will be connected to a PLMN operator-configured service provider offering a DHCP service (according to the APN selection rules). +- 2) The MT sends the Activate PDP Context Request message to the SGSN with an empty PDP address field. +- 3) The SGSN selects a GGSN based on the APN requested by the MS and sends a Create PDP Context Request message to that GGSN. The GGSN replies with a Create PDP Context Response message. If the GGSN has not been configured by the operator to use external PDN address allocation with DHCP for the requested APN, the cause shall be set to 'Service not supported'. No IP address is assigned at this point; the PDP address returned by the GGSN is set to 0.0.0.0, indicating that the IP address is not yet assigned and shall be negotiated by the TE with the Intranet/ISP after the PDP context activation procedure. +- 4) Depending on the cause value received in the Create PDP Context Response the SGSN sends either an Activate PDP Context Accept or an Activate PDP Context Reject back to the MT. In case of a successful activation the PDP context is established with the PDP address set to 0.0.0.0. +- 5) Upon reception of the Activate PDP Context Accept, the MT sends an AT response to the TE that acknowledges the completion of the PDP context activation procedure. +- 6) The TE sends a DHCPDISCOVER message with the IP destination address set to the limited broadcast address (all 1s). The GGSN will pass the DHCPDISCOVER to the DHCP relay agent which will relay the request to the DHCP server configured for the APN of the PDP context. If more than one DHCP server is configured for a given APN, the request will be sent to all of them. The DHCP relay agent will add enough information to the DHCPDISCOVER message to be able to relay the replies back to the MS. How this is done is out of the scope of 3GPP standardisation. + +- 7) DHCP servers receiving the DHCPDISCOVER request reply by sending a DHCPOFFER message including an offered IP address. The DHCP relay agent forwards the replies to the proper MS. +- 8) The TE chooses one of the possibly several DHCPOFFERs and sends a DHCPREQUEST confirming its choice and requesting additional configuration information. The relay agent relays the DHCPREQUEST as explained in step 6. +- 9) The selected DHCP server receives the DHCPREQUEST and replies with a DHCPACK containing the configuration information requested by the TE. The DHCP relay agent relays the DHCPACK to the TE. +- 10) The DHCP relay agent passes the allocated IP address to the GGSN which stores it in the corresponding PDP context. The GGSN then initiates a PDP context modification procedure by sending an Update PDP Context Request to the appropriate SGSN with the End User Address information element set to the allocated IP address. +- 11) The SGSN sends a Modify PDP Context Request to the MT with the allocated IP address in the PDP Address information element. The MT acknowledges by sending a Modify PDP Context Accept to the SGSN. +- 12) The SGSN sends an Update PDP Context Response to the GGSN. The PDP context has been successfully updated with the allocated IP address. + +EXAMPLE: In the following example a successful PDP context activation with use of DHCP from end to end is shown. + +![Sequence diagram showing DHCPv4 signal flow between TE, MT, SGSN, GGSN (DHCP Relay Agent), and Intranet or ISP.](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) + +``` + +sequenceDiagram + participant TE + participant MT + participant SGSN + participant GGSN as GGSN +DHCP Relay Agent + participant Intranet or ISP + + Note left of TE: 1. AT commands + MT->>SGSN: 2. Activate PDP Context req. + SGSN->>GGSN: 3. Create PDP Context req. + GGSN->>SGSN: 3. Create PDP Context resp. + SGSN->>MT: 4. Activate PDP Context acc. + Note left of TE: 5. AT command + Note left of TE: 6. DHCPDISCOVER + TE->>Intranet or ISP: 6. DHCPDISCOVER + Intranet or ISP-->>GGSN: 7. DHCPOFFER (maybe several) + GGSN-->>TE: 7. DHCPOFFER (maybe several) + Note left of TE: 8. DHCPREQUEST + TE->>Intranet or ISP: 8. DHCPREQUEST + Intranet or ISP-->>GGSN: 9. DHCPACK + GGSN-->>TE: 9. DHCPACK + Note left of GGSN: 10. Update PDP Context req. + GGSN->>SGSN: 10. Update PDP Context req. + SGSN->>MT: 11. Modify PDP Context req. + MT-->>SGSN: 11. Modify PDP Context acc. + SGSN->>GGSN: 12. Update PDP Context resp. + +``` + +Sequence diagram showing DHCPv4 signal flow between TE, MT, SGSN, GGSN (DHCP Relay Agent), and Intranet or ISP. + +Figure 16d: DHCPv4 signal flow + +13.2.1.2 Void. + +## 13.2.2 Other configuration by the Intranet or ISP (IPv6 only) + +When using IPv6, in some situations the MS may need additional configuration information from the Intranet or ISP besides the IP address. It may for example be IMS related configuration options (see 3GPP TS 24.229 [47]). If the MS is DHCP capable and the IPv6 address has been allocated using Stateless Address Autoconfiguration, the MS may use a procedure as in the example below to configure additional external network protocol parameters, or other parameters + +that apply to the Intranet or ISP. The GGSN shall in this case indicate to the MS that there is additional configuration information to retrieve by setting the O-flag in the Router Advertisements. This shall be configured per APN in the GGSN. + +The following description bullet items describe an example of a signal flow, where the MS directs an Information-Request to the All\_DHCP\_Relay\_Agents\_and\_Servers multicast address. The MS may also direct the message to a specific server instead of all servers. For a detailed description of the DHCPv6 messages refer to the DHCPv6 IETF RFC 3315 [46]. The sequence is depicted in figure 16f. + +- 1) A Router Advertisement with the O-flag set, is sent from GGSN to TE to indicate to it to retrieve other configuration information. +- 2) The TE sends an INFORMATION-REQUEST message with the IP destination address set to the All\_DHCP\_Relay\_Agents\_and\_Servers multicast address defined in the DHCPv6 IETF RFC 3315 [46]. The source address shall be the link-local address of the MS. The DHCP relay agent in the GGSN shall forward the message. +- 3) DHCP servers receiving the forwarded INFORMATION-REQUEST message, reply by sending a RELAY-REPLY message, with the "Relay Message" option including a REPLY message with the requested configuration parameters. + +The TE chooses one of the possibly several REPLY messages and extracts the configuration information. + +EXAMPLE: In the following example a request for information with use of DHCPv6 from end to end is shown. + +![Sequence diagram illustrating DHCPv6 Other configuration signal flow between TE, MT, SGSN, GGSN (DHCP Relay Agent), and Intranet or ISP DHCP Server(s).](367378559e35017a5e1a6f5c30798c5a_img.jpg) + +``` + +sequenceDiagram + participant TE + participant MT + participant SGSN + participant GGSN as GGSN +DHCP Relay Agent + participant ISP as Intranet or ISP +DHCP Server(s) + + Note left of TE: 1. Router Advertisement ( O-flag=1 ) + GGSN->>TE: 1. Router Advertisement ( O-flag=1 ) + Note left of TE: 2. INFORMATION-REQUEST + TE->>GGSN: 2. INFORMATION-REQUEST + GGSN->>ISP: RELAY-FORWARD( INFORMATION-REQUEST ) + Note left of TE: 3. REPLY (maybe several) + ISP->>GGSN: RELAY-REPLY( REPLY ) + GGSN->>TE: 3. REPLY (maybe several) + +``` + +Sequence diagram illustrating DHCPv6 Other configuration signal flow between TE, MT, SGSN, GGSN (DHCP Relay Agent), and Intranet or ISP DHCP Server(s). + +Figure 16f: DHCPv6 Other configuration signal flow + +### 13.3 PDN Interworking Model of P-GW for DHCP + +A DHCP Client shall be located in the P-GW used for interworking with the IP network as illustrated in Figure 16g. + +![Diagram of the protocol stack for the Sgi IP reference point for DHCP. The stack is shown within a P-GW box, with layers from top to bottom: DHCP Client, UDP, IP, L2, and L1. The L1 layer connects to the SGi interface.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +The diagram illustrates the protocol stack for the Sgi IP reference point for DHCP. It shows a vertical stack of five protocol layers inside a box labeled 'P-GW'. From top to bottom, the layers are: 'DHCP Client', 'UDP', 'IP', 'L2', and 'L1'. A horizontal line extends from the 'L1' layer to the right, representing the 'SGi' interface. + +Diagram of the protocol stack for the Sgi IP reference point for DHCP. The stack is shown within a P-GW box, with layers from top to bottom: DHCP Client, UDP, IP, L2, and L1. The L1 layer connects to the SGi interface. + +**Figure 16g: The protocol stacks for the Sgi IP reference point for DHCP** + +The DHCP client function in P-GW shall be used to allocate IP address(es) to the UE and/or to configure associated parameters via external DHCP servers in PDN(s). As both IPv4 and IPv6 address allocation are supported in EPS, the P-GW shall have both DHCPv4 and DHCPv6 client functions. + +The procedures where the DHCP client function in the P-GW is used are further described in TS 23.060 [3], TS 23.401 [77] and TS 23.402 [78]. The procedures are IPv4 address allocation and IPv4 parameter configuration via an external DHCPv4 server in a PDN; IPv6 Prefix allocation via stateless address autoconfiguration; and IPv6 parameter configuration via stateless DHCPv6. These procedures are detailed in the subclauses below. + +### 13.3.1 Address allocation by the Intranet or ISP + +The subclauses below provide the signalling flows when the IP address allocation and/or the IP parameter configuration to a UE is performed via an external DHCP server in the PDN. + +#### 13.3.1.1 IPv4 Address allocation and IPv4 parameter configuration via DHCPv4 + +The UE may obtain the IPv4 address and/or its configuration parameters at or after the initial access signalling (e.g. default bearer establishment) to the packet domain. The request for IPv4 address and/or configuration parameters from the UE may trigger the P-GW acting as DHCPv4 client to request the IPv4 address and/or configuration parameters from an external DHCPv4 server and deliver them to the UE. See subclause 11.2.1.2.2 for details. The DHCPv4 functions in the P-GW, the UE and the external DHCPv4 server shall be compliant to RFC 2131 [26], RFC 1542 [27] and RFC 4039 [79]. + +The following bullet items describe the successful IPv4 address allocation and parameter configuration signalling flow between the P-GW and the external DHCPv4 server as depicted Figure 16h. For a detailed description of the DHCPv4 messages, refer to RFC 2131 [26], RFC 1542 [27] and RFC 4039 [79]. + +Figure 16h is an example signalling flow for IPv4 address allocation and parameter configuration at the default bearer setup using DHCPv4 as specified in RFC 2131 [26]. If the optimized signalling (Rapid Commit Option) is used as per RFC 4039 [79], the messages 2-3 can be eliminated. + +- 1) The DHCPv4 client function in the P-GW sends a DHCPDISCOVER as an IP limited broadcast message, i.e. the destination address 255.255.255.255, towards the external PDN. If the P-GW has the DHCPv4 server IP addresses configured for the APN, the DHCPDISCOVER shall be send as unicast (or even multicast) to the external DHCPv4 servers. +- 2) Upon receiving the DHCPDISCOVER request message, the external DHCPv4 servers reply by sending a DHCPOFFER message including an offered IP address. Several DHCPOFFER messages may be received by the P-GW if multiple DHCPv4 servers respond to the DHCPDISCOVER. + +- 3) The DHCPv4 client function in the P-GW processes the messages and sends a DHCPREQUEST towards the selected external DHCPv4 server. +- 4) Upon receiving the DHCPREQUEST message, the selected external DHCPv4 server acknowledges the address allocation by sending a DHCPACK containing the lease period (T1), the time-out time (T2) and the configuration information requested in DHCPREQUEST. The P-GW stores the allocated IPv4 address, the lease timers and the configuration parameters. The IPv4 address and the configuration parameters shall be delivered to the UE through P-GW to UE messages. + +![Sequence diagram showing the signalling flow for IPv4 address allocation and parameter configuration using DHCPv4. The diagram shows four messages between the P-GW (DHCPv4 Client) and the DHCPv4 Server: 1. DHCPDISCOVER (Client to Server), 2. DHCP OFFER (Server to Client), 3. DHCPREQUEST (Client to Server), and 4. DHCP ACK (Server to Client).](03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg) + +``` + +sequenceDiagram + participant P-GW as P-GW (DHCPv4 Client) + participant DHCPv4 Server as DHCPv4 Server + Note right of P-GW: 1. DHCPDISCOVER + P-GW->>DHCPv4 Server: 1. DHCPDISCOVER + Note left of DHCPv4 Server: 2. DHCP OFFER + DHCPv4 Server-->>P-GW: 2. DHCP OFFER + Note right of P-GW: 3. DHCPREQUEST + P-GW->>DHCPv4 Server: 3. DHCPREQUEST + Note left of DHCPv4 Server: 4. DHCP ACK + DHCPv4 Server-->>P-GW: 4. DHCP ACK + +``` + +Sequence diagram showing the signalling flow for IPv4 address allocation and parameter configuration using DHCPv4. The diagram shows four messages between the P-GW (DHCPv4 Client) and the DHCPv4 Server: 1. DHCPDISCOVER (Client to Server), 2. DHCP OFFER (Server to Client), 3. DHCPREQUEST (Client to Server), and 4. DHCP ACK (Server to Client). + +**Figure 16h: The signalling flow for IPv4 address allocation and parameter configuration using DHCPv4** + +Figure 16i is an example signalling flow for IPv4 address lease renew by using DHCPv4 protocol as specified in RFC 2131 [26]. + +- 1) The DHCPv4 client function in the P-GW sends a unicast DHCPREQUEST towards the external DHCPv4 server to extend the lease period of the allocated IPv4 address. +- 2) The external DHCPv4 server replies with a DHCPACK message confirming the renewed lease and the T1 and T2 timers are restarted. + +![Sequence diagram showing the signalling flow for IPv4 address lease renew using DHCPv4. The diagram shows two messages between the P-GW (DHCPv4 Client) and the DHCPv4 Server: 1. DHCPREQUEST (Client to Server) and 2. DHCPACK (Server to Client).](91b12db3c85bbf466ad27eb3665a1b06_img.jpg) + +``` + +sequenceDiagram + participant P-GW as P-GW (DHCPv4 Client) + participant DHCPv4 Server as DHCPv4 Server + Note right of P-GW: 1. DHCPREQUEST + P-GW->>DHCPv4 Server: 1. DHCPREQUEST + Note left of DHCPv4 Server: 2. DHCPACK + DHCPv4 Server-->>P-GW: 2. DHCPACK + +``` + +Sequence diagram showing the signalling flow for IPv4 address lease renew using DHCPv4. The diagram shows two messages between the P-GW (DHCPv4 Client) and the DHCPv4 Server: 1. DHCPREQUEST (Client to Server) and 2. DHCPACK (Server to Client). + +**Figure 16i: The signalling flow for IPv4 address lease renew using DHCPv4** + +### 13.3.1.2 IPv6 Prefix allocation via IPv6 stateless address autoconfiguration via DHCPv6 + +When the IPv6 prefix is allocated from the external PDN, it is the P-GW's responsibility to obtain the IPv6 prefix for external PDN, allocate and release the IPv6 prefix. The P-GW may use DHCPv6 to obtain the IPv6 prefix from the external PDN. In this context, the P-GW shall act as a DHCP client as per IETF RFC 3315 [46] towards the external DHCPv6 server. The use cases between the UE and the P-GW that may lead the P-GW to interwork with the external DHCPv6 servers are described in subclause 11.2.1.3.1a. + +### 13.3.1.3 IPv6 parameter configuration via stateless DHCPv6 + +A UE that has obtained an IPv6 address can use stateless DHCP to request other configuration information such as a list of DNS recursive name servers or SIP servers. + +For 3GPP networks if such IPv6 configuration parameters are locally provisioned in the P-GW, the P-GW returns the requested parameters to the UE via its DHCPv6 server function. For trusted non-3gpp access networks, if such IPv6 + +configuration parameters are locally provisioned in the P-GW, the P-GW may return the requested parameters to the UE via its DHCPv6 server function or the P-GW may return the IPv6 configuration parameters to the non-3gpp access network and then the non-3GPP access network may send the parameters to the UE via its DHCPv6 server function. When the non-3GPP access network is a trusted WLAN network, the PGW always returns the IPv6 configuration parameters to the TWAN via GTP/PMIP message, and then the TWAN sends the parameters to the UE via its DHCPv6 server function. When an external DHCPv6 server in a PDN is used to obtain the requested parameters, which is the use case covered in this subclause, the P-GW acts as a DHCPv6 client towards the external DHCPv6 server while acting a DHCPv6 server towards the UE. + +The IPv6 parameter configuration via stateless DHCPv6 function in the UE, the P-GW and the external DHCPv6 Server shall be compliant to RFC 3736 [80]. An example signalling flow for the GGSN is described in Subclause 13.2.2. For the P-GW, the signalling flow is same with the following modifications: + +- For 3GPP access networks, the P-GW sends Router Advertisement for GTP-based S5/S8. In the case of PMIP-based S5/S8, the S-GW sends the Router Advertisement. For trusted non-3GPP access networks, the trusted non-3GPP access network sends the Router Advertisement for PMIP S2a. When the non-3GPP access network is a trusted WLAN network, the TWAN sends the Router Advertisement + +As stated above, the P-GW acts as a DHCPv6 server towards the UE, while acting as a DHCPv6 client towards the external DHCPv6 server. + +--- + +## 13a Interworking with IMS + +### 13a.1 General + +Interworking with the IP Multimedia Core Network Subsystem (IMS) puts additional requirements on the GGSN/P-GW. When the MS/UE connects to the IP Multimedia Core Network Subsystem (IMS), specific parameters in Session Management messages may be handled. The IMS specific parameters are: IMS signalling flag, P-CSCF address request, P-CSCF restoration support, returned P-CSCF address(es) and flow identifier(s). + +For interworking with the IMS, the Gx interface (see 3GPP TS 29.212 [75]) is used to correlate the session (SIP/SDP) and the bearer (PDP Contexts). + +The mechanisms in GGSN/P-GW to support IMS shall be: + +- P-CSCF discovery. +- Dedicated signalling bearer (e.g. PDP contexts) (with or without enhanced QoS) for IMS signalling; with associated packet filters to permit signalling to/from designated servers. +- Gx interface for policy and charging control of bearer (e.g. PDP contexts) for IMS media flows. +- P-CSCF restoration. + +These mechanisms are however not restricted to the IMS and could be used for other services that could benefit from these mechanisms. + +The P-GW shall not modify the fields Type of Service (IPv4) and Traffic Class (IPv6) of the received downlink packets. + +NOTE: The P-CSCF can support paging policy differentiation for different traffic or service types over LTE by marking the fields Type of Service (IPv4) and Traffic Class (IPv6) (see clause L.3.2.4 of 3GPP TS 24.229 [47]). + +### 13a.2 IMS Interworking Model + +The signalling interface between MS/UE and P-CSCF is a logical interface, i.e. it is using GPRS or EPC as a bearer. The Gx interface is used for network communication between the GGSN/P-GW and the PCRF. For a description of the IMS architecture, refer to 3GPP TS 23.228 [52]. For a more detailed view of GGSN/P-GW IMS interworking, see 3GPP TS 29.213 [76]. + +### 13a.2.1 IMS Specific Configuration in the GGSN/P-GW + +The GGSN/P-GW shall have a list of preconfigured addresses of signalling servers (P-CSCF servers). This list shall be provided to MSs/UEs on request. The list shall be possible to preconfigure per APN. + +The GGSN/P-GW shall have locally preconfigured packet filters, and/or applicable PCC rules, as specified in 3GPP TS 29.212 [75] to be applied on the dedicated signalling bearer (e.g. PDP context). The packet filters shall filter up-link and down-link packets and only allow traffic to/from the signalling servers and to DNS and DHCP servers. The locally preconfigured packet filters shall be possible to pre-configure per APN. + +It shall be possible to enable/disable the use of the Gx interface per APN. When Gx is enabled the GGSN/P-GW shall handle IP-CAN Bearer Establishment (e.g. Create PDP Context Requests) as specified in 3GPP TS 29.212 [75]. + +The GGSN/P-GW shall support IPv4 and/or IPv6 addresses and protocol for IMS signalling and IMS bearers. + +The methods for an MS/UE to discover P-CSCF address(es) may vary depending on the access technology that the MS/UE is on. The details of the P-CSCF discovery mechanisms for various accesses are specified in 3GPP TS 23.228 [52] and 3GPP TS 24.229 [47]. For example, for an MS/UE accessing to IMS via GPRS in GERAN and UTRAN, the GGSN shall provide support for P-CSCF discovery in three different ways (see 3GPP TS 23.228 [52] and 3GPP TS 24.229 [47]): + +- GPRS procedure for P-CSCF discovery, i.e. request and provision of P-CSCF address(es) within the PCO IE in GPRS Session Management procedures (see 3GPP TS 24.008 [54]). +- Via DHCP servers i.e. the GGSN shall provide the functionality of a DHCP relay agent +- If the MS/UE has a P-CSCF FQDN locally configured and request the DNS IP address(es) from the GGSN (via PCO or DHCP procedures), the GGSN shall be able to provide DNS IP address(es) to the MS/UE. + +Similarly, the PGW shall have similar functional support depending on the P-CSCF discovery methods supported by the UE on the access technology. For example, for a UE in 3GPP access network (i.e. GERAN, UTRAN, EUTRAN), the P-GW shall support same functions as the GGSN that are specified above except that the P-GW does not act as a DHCP relay agent between the MS/UE and the external DHCP server. In other words, as specified in clause 13 of this document, the P-GW shall have DHCP server function towards the MS/UE while acting as a DHCP client towards external DHCP server, if the P-GW is configured to request DNS and/or P-CSCF IP addresses from external DHCP servers. + +The GGSN/P-GW shall be able to deliver DNS and/or P-CSCF addresses to the MS/UE if requested by the MS/UE via PCO (see 3GPP TS 24.008 [54] and 3GPP TS 24.301 [84]) or via DHCP procedures using the relevant DHCP options for IPv4/IPv6 DNS and SIP servers (see RFC 2132 [85], RFC 3361 [86], RFC 3646 [87] and RFC 3319 [88]). + +On APNs providing IMS services, the information advertised in Router Advertisements from GGSN/P-GW to MSs/UEs shall be configured in the same manner as for other APNs providing IPv6 services (see subclause 11.2.1.3.4), except that the "O-flag" shall be set. + +NOTE: The "O- flag" shall be set in IPv6 Router Advertisement messages sent by the GGSN/P-GW for APNs used for IMS services. This will trigger a DHCP capable MS/UE to start a DHCPv6 session to retrieve server addresses and other configuration parameters. An MS/UE which doesn't support DHCP will simply ignore the "O-flag". An MS/UE, which doesn't support DHCP, shall request IMS specific configuration (e.g. P-CSCF address) via the other discovery methods supported in the MS/UE (i.e. via locally configured P-CSCF address/FQDN in the MS/UE or via PCO procedure, if applicable). + +The GGSN/P-GW shall have configurable policy rules for controlling bearers (e.g. PDP contexts) used for signalling as specified in section 13a.2.2.2. + +### 13a.2.2 IMS Specific Procedures in the GGSN/P-GW + +#### 13a.2.2.1 Request for Signalling Server Address + +When an MS/UE indicates a request for a P-CSCF address in the PCO IE in a Create PDP Context Request message on GERAN/UTRAN or for E-UTRAN in initial access request (e.g. Attach Request, PDN Connectivity Request), the GGSN/P-GW shall respond with one or more P-CSCF server addresses if preconfigured for this APN. If the GGSN/P-GW has no P-CSCF address available, the GGSN/P-GW shall ignore the request. If the GGSN/P-GW provides more + +than one P-CSCF IPv4/IPv6 address in the response, the GGSN/P-GW shall sort the addresses with the highest priority P-CSCF server first in the PCO IE. The GGSN/P-GW may use different prioritisations for different Mses/UEs, e.g. for load sharing between the P-CSCF servers. + +The GGSN/P-GW may use a keep alive mechanism and/or other type based on local policy (e.g. statistical monitoring) to be able to detect a failure of P-CSCF address(es) preconfigured in the APN. The keep alive mechanism should make use of STUN or CRLF as specified for the UE in 3GPP TS 24.229 [47], clause K.2.1.5. As an alternative, ICMP echo request/response may be used. The GGSN/P-GW shall then provide only those P-CSCF address(es) that are available in a Create PDP Context Response/Create Session Response. + +The coding of the PCO IE is described in the 3GPP TS 24.008 [54]. This procedure shall be followed regardless of whether or not the MS/UE uses a dedicated PDP context/EPS bearer for IMS signalling, and irrespective of the Gx status for the APN. + +### 13a.2.2.1a Failure of Signalling Server Address + +If the GGSN/P-GW detects a failure: + +- in P-CSCF address(es) being used by the MS/UEs, if received via Gx (as specified in 3GPP TS 23.380 [95], clause 5); or +- upon receiving a P-CSCF restoration indication from the MME/SGSN or the PCRF, + +then the GGSN/P-GW shall act as specified in 3GPP TS 23.380 [95], clause 5. + +### 13a.2.2.2 Establishment of a PDP Context/EPS Bearer for Signalling + +The following applies for establishing a PDP context/EPS bearer for IMS signalling in the GGSN/P-GW as per 3GPP TS 23.228 [52]: + +- I. The GGSN/P-GW shall allow IMS signalling on a "general-purpose PDP context"/default EPS bearer, in which case the IMS signalling shall be provided like any other transparent services provided by the packet domain. +- II. The GGSN/P-GW may (dependent on operator policy) also support PDP Contexts/EPS Bearers dedicated for IMS services. If the the bearer establishment selected for the APN is controlled by the MS/UE, the MS/UE may request a dedicated PDP context/EPS Bearer for IMS signalling (see 3GPP TS 24.229 [47]) by setting the IM CN Subsystem signalling flag in the PCO IE. Specifically, the GGSN/P-GW may receive the IM CN Subsystem signalling flag in the PCO IE in the PDP context activation or Secondary PDP context activation for GERAN and UTRAN accesses; in the Attach, UE-requested PDN connectivity request or UE-requested bearer resource modification procedures for E-UTRAN access. If the bearer establishment selected for the APN is controlled by the network, depending on the operator policy, the GGSN or P-GW may also activate a PDP context or dedicated EPS bearer for IMS signalling via network-initiated Secondary PDP context activation or network-initiated Dedicated Bearer activation procedures, respectively. If dedicated PDP contexts/EPS Bearers for IMS signalling are not supported, the GGSN/P-GW will reset the signalling flag in the response to the MS/UE. For P-GW, if the APN offers non-IMS services, the default bearer shall not be allowed to be set up as a dedicated IM CN signalling bearer. If the PDP context/EPS bearer can be established as a dedicated bearer for IMS signalling, the GGSN/P-GW can provide a set of UL filters for the PDP context/EPS bearer used for IMS. The UL filters provide the MS/UE with the rules and restrictions applied by the GGSN/P-GW for the dedicated PDP context/EPS bearer for IMS signalling. The GGSN/P-GW can in addition provide the IMS signalling flag to explicitly indicate to the MS/UE the intention of using the PDP context/EPS bearer for IMS related signalling. + +In both cases, I and II, + +- The GGSN may receive the Signalling Indication parameter in the QoS IE. This indicates a request for prioritised handling over the radio interface. The GGSN shall be able to downgrade the QoS (dependent on operator policy) by resetting the Signalling Indication according to the normal procedures for QoS negotiation, see 3GPP TS 23.060 [3]. +- During the (default or dedicated) EPS bearer activation procedure, the P-GW may receive the request for appropriate QCI for IMS signalling traffic as specified in 3GPP TS 23.203 [90] in EPS bearer QoS IE that indicates the prioritised handling of the EPS bearer over the radio interface. The P-GW may either accept or reject the request based on the operator policy configured at the P-GW. + +IM CN subsystem signalling flag and Signalling Indication or appropriate QCI for IMS signalling in the QoS IE may be used independently of each other. However, based on the operator policy, the network may honor the Signalling Indication or appropriate QCI for IMS signalling if the IM CN Subsystem signalling flag is present in PCO IE. + +The operator may provide other properties to the PDP contexts/EPS bearers dedicated for IMS signalling, e.g. special charging. It is out of the current scope of this TS to further specify these properties. + +For a PDP Context/EPS bearer marked as a dedicated for IMS signalling, the GGSN/P-GW shall apply the applicable PCC rules, as specified in 3GPP TS 29.212 [75], and/or locally preconfigured packet filters, which shall only allow packets to be sent to and from a set of signalling servers, such as P-CSCF(s), DHCP server(s) and DNS server(s). The TFT filters on the dedicated signalling bearer shall have a precedence value so that they precede any other TFT filters. This will secure the use of the correct PDP context/EPS bearer for the signalling traffic, and that only authorized traffic uses the signalling PDP context. The locally preconfigured packet filters shall be defined in the GGSN/P-GW by the operator. + +### 13a.2.2.3 Creation of a PDP Context/EPS Bearer for IMS Media Flows + +For PDP Contexts/EPS bearers used to carry IMS media flows, specific policies may be applied. The policy includes packet filtering, which enables a specific charging for these PDP Contexts/EPS bearers, see 3GPP TS 29.212 [75]. + +The creation of a PDP Context/EPS bearer to be used to carry media flows involves interaction between the MS/UE and the GGSN/P-GW and between the GGSN/P-GW and the PCRF. The interaction between the GGSN/P-GW and the PCRF, i.e. the Gx interface, is described in detail in 3GPP TS 29.212 [75]. The interaction between the MS/UE and GGSN/P-GW is described in 3GPP TS 29.213 [76]. + +If Gx is enabled for the APN, the GGSN/P-GW contacts the PCRF selected during the establishment of the APN. + +--- + +## 13b Interworking with BM-SC in EPS + +### 13b.1 General + +MBMS GW is used for interworking with the BM-SC in EPS. One or more MBMS GWs may be used in a PLMN. The specific message, i.e. session start/session update/session stop, and specific parameters, e.g. TMGI, MBMS service area, list of MBMS control plane nodes, are handled. + +MBMS GW provides the Sgi-mb (user plane) reference point and the SGmb (control plane) reference point for interworking with the BM-SC. + +### 13b.2 BM-SC interworking model of MBMS GW + +The control plane and user plane protocol stacks of the MBMS GW for interworking with BM-SC are illustrated in Figure 16j, Figure 16k and Figure 16l. The figures include the following protocols: + +- The "Diameter" SGmb application, as specified in clause 20. +- The Control part of the Evolved GPRS Tunnelling Protocol for EPS, GTPv2-C, as specified in 3GPP TS 29.274 [81]. +- The User Datagram Protocol, UDP, as specified in IETF RFC 768 [15]. +- The Transmission Control Protocol, TCP, as specified in IETF RFC 793 [18] +- The Stream Control Transmission Protocol, SCTP, as specified in IETF RFC 4960 [109]. +- The Packet Data Convergence Protocol, PDCP, as specified in 3GPP TS 25.323 [107]. +- The MBMS synchronisation protocol, SYNC, as specified in 3GPP TS 25.446 [106]. +- The Internet Protocol, IP. + +- L1 and L2 transport protocols for IP (various options exist). + +![Figure 16j: Control plane protocol stacks of MBMS GW and BM-SC for interworking with SGmb.](1f1614411edea7edfc86c839a608e1fc_img.jpg) + +This diagram illustrates the control plane protocol stacks for the MBMS GW and the BM-SC, connected via the SGmb interface. Both entities share a common stack of protocols: Diameter, TCP/SCTP, IP, and L1/L2. The MBMS GW also includes GTPv2-C. + +| MBMS GW | | SGmb | BM-SC | | +|---------|----------|------|----------|--| +| GTPv2-C | Diameter | | Diameter | | +| UDP | TCP/SCTP | | TCP/SCTP | | +| IP | IP | | IP | | +| L1/L2 | L1/L2 | | L1/L2 | | + +Figure 16j: Control plane protocol stacks of MBMS GW and BM-SC for interworking with SGmb. + +Figure 16j: The control plane protocol stacks of MBMS GW for interworking with BM-SC + +![Figure 16k: User plane protocol stacks of MBMS GW and BM-SC for multicast over SGmb.](cc542843836eecb036b99cb270b54a1e_img.jpg) + +This diagram shows the user plane protocol stacks for the MBMS GW and the BM-SC for multicast traffic over the SGmb interface. The stacks are identical, starting with User plane data, followed by PDCP, SYNC, UDP, IP, and L1/L2. + +| MBMS GW | | SGmb | BM-SC | | +|-----------------|--|------|-----------------|--| +| User plane data | | | User plane data | | +| PDCP | | | PDCP | | +| SYNC | | | SYNC | | +| UDP | | | UDP | | +| IP | | | IP | | +| L1/L2 | | | L1/L2 | | + +Figure 16k: User plane protocol stacks of MBMS GW and BM-SC for multicast over SGmb. + +Figure 16k: The user plane protocol stacks of MBMS GW for interworking with BM-SC for multicast + +![Figure 16l: User plane protocol stacks of MBMS GW and BM-SC for broadcast over SGmb.](a057800564be3506d2d87b6a4daee25b_img.jpg) + +This diagram shows the user plane protocol stacks for the MBMS GW and the BM-SC for broadcast traffic over the SGmb interface. The stacks are identical, starting with User plane data, followed by SYNC, UDP, IP, and L1/L2. PDCP is not used in this mode. + +| MBMS GW | | SGmb | BM-SC | | +|-----------------|--|------|-----------------|--| +| User plane data | | | User plane data | | +| SYNC | | | SYNC | | +| UDP | | | UDP | | +| IP | | | IP | | +| L1/L2 | | | L1/L2 | | + +Figure 16l: User plane protocol stacks of MBMS GW and BM-SC for broadcast over SGmb. + +Figure 16l: The user plane protocol stacks of MBMS GW for interworking with BM-SC for broadcast + +A BM-SC sends user plane data to an MBMS GW either by IP unicast (default), or by IP multicasting. Through the control plane communication a BM-SC provides an MBMS GW with necessary data, so that MBMS GW could forward the user plane data downlink either by multicast (default) or by unicast. + +PDCP is not used when the MBMS service is broadcasted in the E-UTRAN, refer to 3GPP TS 36.331 [94]. + +### 13b.3 Forwarding of user plane packets at the MBMS GW + +If user plane data are to be sent to the MBMS Gateway using IP unicast, the MBMS Gateway allocates an IP transport address and a separate UDP port for each MBMS bearer ( i.e the service uniquely identified by its TMGI and Flow ID and provided by the EPS to deliver the same IP datagrams to multiple receivers in a designated location). The MBMS Gateway uses that destination unicast IP address and destination UDP port of user plane packets received over the SGi-mb interface to determine on which MBMS bearer to forward the received user plane packet. + +If user plane data are to be sent to the MBMS Gateway using IP multicast encapsulation, the MBMS Gateway uses, the SGi-mb (transport) plane destination multicast address used and the SGi-mb (transport) plane source UDP port number provided by the BM-SC of user plane packets received over the SGi-mb interface to determine on which MBMS bearer to forward the received user plane packet. + +## 14 Internet Hosted Octet Stream Service (IHOSS) + +Figure 17: Void + +Figure 18: Void + +Figure 19: Void + +Figure 20: Void + +## 15 Interworking between Packet Domains + +The primary reason for the interworking between Packet Domains is to support roaming subscribers as described in 3GPP TS 23.060 [3]. The general model for both GPRS and EPS Packet Domain interworking is shown in figure 21. + +![Figure 21: General interworking model for GPRS Packet Domains and EPS Packet Domains to support roaming subscribers. The diagram shows two packet domains, GPRS and EPS PLMN, connected via an Inter-PLMN Backbone. The GPRS domain includes GGS, BG, SGS, and SGSN. The EPS PLMN domain includes BG, PDN GW, SGS, and S-. Both domains are connected to a Packet Data Network via Gi and SGi interfaces respectively.](0db3cccd1279034258e5ad5b6fdcff01_img.jpg) + +The diagram illustrates the general interworking model for GPRS and EPS Packet Domains. At the top, a 'Packet Data Network' (represented by an oval) is connected to both domains. The GPRS domain (left) consists of a 'GGS' and 'BG' connected to an 'Intra-PLMN Backbone' (oval), which is further connected to 'SGS' and 'SGSN'. This domain connects to the 'Packet Data Network' via a 'Gi' interface and to the 'Inter-PLMN Backbone' (oval) via a 'Gp' interface. The EPS PLMN domain (right) consists of a 'BG' and 'PDN GW' connected to an 'Intra-PLMN Backbone' (oval), which is further connected to 'SGS' and 'S-'. This domain connects to the 'Packet Data Network' via an 'SGi' interface and to the 'Inter-PLMN Backbone' via an 'S8' interface. Both domains are shown as stacked green rectangles, indicating multiple instances. + +Figure 21: General interworking model for GPRS Packet Domains and EPS Packet Domains to support roaming subscribers. The diagram shows two packet domains, GPRS and EPS PLMN, connected via an Inter-PLMN Backbone. The GPRS domain includes GGS, BG, SGS, and SGSN. The EPS PLMN domain includes BG, PDN GW, SGS, and S-. Both domains are connected to a Packet Data Network via Gi and SGi interfaces respectively. + +Figure 21: General interworking model for GPRS Packet Domains and EPS Packet Domains to support roaming subscribers. + +NOTE: There may be multiple Packet Domains of the same type which interwork each other, such as the case of interwork between two GPRS Packet Domains. + +For roaming subscribers that have a PDP address allocated from the HPLMN a forwarding route between the HPLMN and the VPLMN is created. This route is used for both mobile terminated and mobile originated data traffic. The communication is done via the BGs (Border Gateways) as described in 3GPP TS 23.060 [3]. + +The procedures to set the link between the SGSN in the VPLMN and the GGSN in the HPLMN are described in 3GPP TS 23.060 [3]. + +The inter-PLMN link may be any packet data network or dedicated link as described in 3GPP TS 23.060 [3]. The PLMN operators may have a dedicated inter-PLMN link to fulfil the QoS requirements of a certain protocol. + +In the case of interworking between EPS Packet Domains, S8 reference point is the inter-PLMN interface, linking PDN GW of HPLMN and Serving GW of VPLMN. The procedure for setting the link is described in 3GPP TS 23.401 [77] and TS 23.402 [78]. + +## 15.1 Security Agreements + +Each PLMN operator may support Ipsec (RFC 1825 [61]) and accompanying specifications for authentication (RFC 1826 [62]) and encryption (RFC 1827 [63]) as a basic set of security functionality in its border gateways. The PLMN operators may decide to use other security protocols based on bilateral agreements. + +## 15.2 Routing protocol agreements + +Each PLMN operator may support BGP (RFC 1771 [60]) as a basic set of routing functionality in its border gateways. The PLMN operators may decide to use other routing protocols based on bilateral agreements. + +## 15.3 Charging agreements + +Sharing the cost of the inter-PLMN link is subject to the agreement between the PLMN operators. + +There may be a requirement to collect charging information in the Border Gateway (see figure 21) and this is down to the normal interconnect agreement between PLMN and PDN operators. + +--- + +## 16 Usage of RADIUS on Gi/Sgi interface + +A GGSN may, on a per APN basis, use RADIUS authentication to authenticate a user and RADIUS accounting to provide information to an AAA (Authentication, Authorization and Accounting) server. + +### 16.1 RADIUS Authentication and Authorization + +RADIUS Authentication and Authorization shall be used according to RFC 2865 [38], RFC 3162 [50] and RFC 4818 [97]. + +The RADIUS client function may reside in a GGSN/P-GW. When the GGSN receives a Create PDP Context request message or the P-GW receives an initial access request (e.g. Create Session Request) the RADIUS client function may send the authentication information to an authentication server, which is identified during the APN provisioning. + +The authentication server checks that the user can be accepted. The response (when positive) may contain network information, such as an IPv4 address and/or IPv6 prefix for the user when the GGSN or P-GW is interworking with the AAA server. + +The information delivered during the RADIUS authentication can be used to automatically correlate the users identity (the MSISDN or IMSI) to the IPv4 address and/or IPv6 prefix, if applicable, assigned/confirmed by the GGSN/P-GW or the authentication server respectively. The same procedure applies, in case of sending the authentication to a 'proxy' authentication server. + +RADIUS Authentication is only applicable to the primary PDP context. When the GGSN receives an Access-Accept message from the authentication server it shall complete the PDP context activation procedure. If Access-Reject or no response is received, the GGSN shall reject the PDP Context Activation attempt with a suitable cause code, e.g. User Authentication failed. The GGSN may also use the RADIUS re-authorization procedure for the purpose of IPv4 address allocation to the MS for PDP type of IPv4v6 after establishment of a PDN connection. + +For EPS, RADIUS Authentication is applicable to the initial access request. When the P-GW receives an Access-Accept message from the authentication server it shall complete the initial access procedure. If Access-Reject or no response is received, the P-GW shall reject the initial access procedure with a suitable cause code. The P-GW may also use the RADIUS re-authorization procedure for the purpose of IPv4 address allocation to the UE for PDN type of IPv4v6 after establishment of a PDN connection. The use cases that may lead this procedure are: + +- Deferred IPv4 address allocation via DHCPv4 procedure after successful attach on 3GPP accesses. +- Deferred IPv4 address allocation after successful attach in trusted non-3GPP IP access on S2a. +- Deferred IPv4 home address allocation via DSMIPv6 Re-Registration procedure via S2c. + +## 16.2 RADIUS Accounting + +RADIUS Accounting shall be used according to IETF RFC 2866 [39], IETF RFC 2869 [116], IETF RFC 3162 [50] and IETF RFC 4818 [97]. + +The RADIUS accounting client function may reside in a GGSN/P-GW. The RADIUS accounting client may send information to an accounting server, which is identified during the APN provisioning. The accounting server may store this information and use it to automatically identify the user. This information can be trusted because the Packet Domain network has authenticated the subscriber (i.e. SIM card and possibly other authentication methods). + +The GGSN/P-GW may use the RADIUS Accounting-Request Start and Stop messages during IP-CAN bearer (e.g. primary and secondary PDP context, default and dedicated bearer) activations and deactivations procedures, respectively. For EPC based Packet domain, if the P-GW is not aware of the IP-CAN bearers, e.g. in case of PMIP-based S5/S8, the P-GW may use the RADIUS Accounting-Request Start and Stop messages per IP-CAN session as it would be one IP-CAN bearer. + +The use of Accounting-Request STOP and in addition the Accounting ON and Accounting OFF messages may be used to ensure that information stored in the accounting server is synchronised with the GGSN/P-GW information. + +If the AAA server is used for IPv4 address and/or IPv6 prefix assignment, then, upon reception of a RADIUS Accounting-Request STOP message for all IP-CAN bearers associated to an IP-CAN session defined by APN and IMSI or MSISDN, the AAA server may make the associated IPv4 address and/or IPv6 prefix available for assignment. + +For PDN/PDP type IPv4v6 and deferred IPv4 address allocation, when the IPv4 address is allocated or re-allocated, the accounting session that was established for the IPv6 prefix allocation shall be used to inform the accounting server about the allocated IPv4 address by sending RADIUS Accounting-Request Interim-Update with Framed-IP-Address attribute and its value field containing the allocated IPv4 address. Similarly, the release of IPv4 address shall be indicated to the accounting server by sending RADIUS Accounting-Request Interim-Update without the Framed-IP-Address attribute. + +In order to avoid race conditions, the GGSN/P-GW shall include a 3GPP Vendor-Specific sub-attribute "Session Stop indicator" when it sends the Accounting-Request STOP for the last IP-CAN bearer of an IP-CAN session and the IP-CAN session is terminated (i.e. the IPv4 address and/or IPv6 prefix and any associated GTP tunnels or PMIP tunnel can be released). The AAA server shall not assume the IP-CAN session terminated until an Accounting-Request STOP with the Session Stop indicator is received. + +## 16.3 Authentication and accounting message flows on Gi interface + +### 16.3.1 IP PDP type + +Figure 22 represents the RADIUS message flows between a GGSN and an Authentication, Authorization and Accounting (AAA) server. + +![Sequence diagram showing RADIUS message flows for IP PDP type between MT, SGSN, GGSN, AAA Server, and PDN.](6031b46d356ee24f96bfe37ee2cb7616_img.jpg) + +``` + +sequenceDiagram + participant MT + participant SGSN + participant GGSN + participant AAA as AAA Server + participant PDN + + Note right of AAA: (Note 2) + + MT->>SGSN: PDP Context Activate Request + SGSN->>GGSN: Create PDP Context Request + GGSN-->>AAA: Access-Request + Note right of AAA: (Note 3) + AAA-->>GGSN: Access-Accept + GGSN->>AAA: Accounting-Request (start) + AAA-->>GGSN: Accounting-Response (start) + GGSN->>SGSN: Create PDP Context Response + Note right of SGSN: (Note 1) + SGSN->>MT: Activate PDP Context Accept + Note left of PDN: User Data + MT->>SGSN: Deactivate PDP Context Request + SGSN->>GGSN: Delete PDP Context Request + GGSN->>AAA: Accounting-Request (stop) + AAA-->>GGSN: Accounting-Response (stop) + GGSN->>SGSN: Delete PDP Context Response + SGSN->>MT: Deactivate PDP Context Accept + +``` + +The diagram illustrates the sequence of messages for activating and deactivating an IP PDP context. + **Activation:** The MT sends a 'PDP Context Activate Request' to the SGSN. The SGSN sends a 'Create PDP Context Request' to the GGSN. The GGSN sends an 'Access-Request' to the AAA Server. The AAA Server responds with 'Access-Accept' and an 'Accounting-Request (start)'. The GGSN sends a 'Create PDP Context Response' to the SGSN, which then sends an 'Activate PDP Context Accept' to the MT. + **Deactivation:** The MT sends a 'Deactivate PDP Context Request' to the SGSN. The SGSN sends a 'Delete PDP Context Request' to the GGSN. The GGSN sends an 'Accounting-Request (stop)' to the AAA Server. The AAA Server responds with an 'Accounting-Response (stop)'. The GGSN sends a 'Delete PDP Context Response' to the SGSN, which then sends a 'Deactivate PDP Context Accept' to the MT. + **Notes:** + +- Note 1: Located between GGSN and SGSN during activation. +- Note 2: Located next to the AAA Server label. +- Note 3: Located next to the 'Access-Request' message from GGSN to AAA. + + A horizontal line labeled 'User Data' indicates the data flow between the GGSN and the PDN. + +Sequence diagram showing RADIUS message flows for IP PDP type between MT, SGSN, GGSN, AAA Server, and PDN. + +NOTE 1: If some external applications require RADIUS Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Response (START) is received from the AAA server. The GGSN may wait for the Accounting Response (START) before sending the CreatePDPContextResponse. The GGSN may reject the PDP context if the Accounting Response (START) is not received. + +NOTE 2: Separate accounting and authentication servers may be used. + +NOTE 3: The Access-Request message shall be used for primary PDP context only. + +NOTE 4: The Accounting-Request (Start) message may be sent at a later stage, e.g. after IPv6 address has been assigned and PDP Context updated, in case of IP address allocation via DHCPv4 after successful PDP context activation signalling. + +**Figure 22: RADIUS message flow for PDP type IP (successful user authentication case)** + +When a GGSN receives a Create PDP Context Request message for a given APN, the GGSN may (depending on the configuration for this APN) send a RADIUS Access-Request to an AAA server. The AAA server authenticates and + +authorizes the user. If RADIUS is also responsible for IPv4 address and/or IPv6 prefix allocation the AAA server shall return the allocated IPv4 address and/or IPv6 prefix in the Access-Accept message. + +When PDP type is IPv4v6 and deferred IPv4 addressing via IPv4 address pool in the AAA server is used, the GGSN may initiate RADIUS re-authorization procedures after successful initial attach for the purpose of IPv4 address allocation or to renew the lease for a previously allocated IPv4 address. In this case, the GGSN shall set the Service-Type attribute to "Authorize Only" and the 3GPP-Allocate-IP-Type subattribute to the type of IP address to be allocated in the Access-Request message sent to the AAA server. See subclause 16.4.7.2 for the conditions to use 3GPP-Allocate-IP-Type sub-attribute in Access-Request messages. If the GGSN is using DHCPv4 signalling towards the MS and the RADIUS server includes the Session-Timeout attribute in the Access-Accept, the GGSN may use the Session-Timeout value as the DHCPv4 lease time. The GGSN shall not set the DHCPv4 lease time value higher than the Session-Timeout value. The GGSN may renew the DHCP lease to the MS without re-authorization towards the AAA server providing that the new lease expiry is no later than the Session-Timeout timer expiry. If the GGSN wishes to extend the lease time beyond the current Session-Timeout expiry, it shall initiate a new AAA re-authorization. + +Even if the GGSN was not involved in user authentication (e.g. transparent network access mode), it may send a RADIUS Accounting-Request START message to an AAA server. This message contains parameters, e.g. the tuple which includes the user-id and IPv4 address and/or IPv6 prefix, to be used by application servers (e.g. WAP gateway) in order to identify the user. This message also indicates to the AAA server that the user session has started. The session is uniquely identified by the Acct-Session-Id that is composed of the Charging-Id and the GGSN-Address. + +If some external applications require RADIUS Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Response (START) is received from the AAA server. The GGSN may wait for the Accounting Response (START) before sending the CreatePDPContextResponse. The GGSN may reject the PDP context if the Accounting Response (START) is not received. The authentication and accounting servers may be separately configured for each APN. + +For PDP type IPv4, at IPv4 address allocation via DHCPv4 signalling between the TE and the PDN, no IPv4 address is available at PDP context activation. In that case the GGSN may wait to send the Accounting-Request START message until the TE receives its IPv4 address in a DHCPACK. + +For PDP type IPv4v6 and deferred IPv4 addressing, when the IPv4 address is allocated or re-allocated, the accounting session that was established for the IPv6 prefix allocation shall be used to inform the accounting server about the allocated IPv4 address by sending RADIUS Accounting-Request Interim-Update with the Framed-IP-Address attribute and its value field containing the allocated IPv4 address. + +When the GGSN receives a Delete PDP Context Request message and providing a RADIUS Accounting-Request START message was sent previously, the GGSN shall send a RADIUS Accounting-Request STOP message to the AAA server, which indicates the termination of this particular user session. The GGSN shall immediately send a Delete PDP context response, without waiting for an Accounting-Response STOP message from the AAA server. + +The AAA server shall deallocate the IPv4 address and/or IPv6 prefix (if any) initially allocated to the subscriber, if there is no session for the subscriber. + +For PDP type IPv4v6 and deferred IPv4 addressing, when the GGSN receives a message from the MS or the network indicating the release of the IPv4 address (e.g. receiving DHCPRELEASE) or decides to release the IPv4 address on its own (e.g. due to DHCP lease timer expiry or GGSN assigned IPv4 address), the GGSN shall inform the accounting server about the deallocation of the IPv4 address by sending RADIUS Accounting-Request Interim-Update without the Framed-IP-Address attribute. + +Accounting-Request ON and Accounting-Request OFF messages may be sent from the GGSN to the AAA server to ensure the correct synchronization of the session information in the GGSN and the AAA server. + +The GGSN may send an Accounting-Request ON message to the AAA server to indicate that a restart has occurred. The AAA server may then release the associated resources. + +Prior to a scheduled restart, the GGSN may send Accounting-Request OFF message to the AAA server. The AAA server may then release the associated resources. + +If an Access-Challenge is sent to the GGSN when an Access-Request message is pending and when IP PDP type is used, the GGSN shall silently discard the Access-Challenge message and it shall treat an Access-Challenge as though it had received an Access-Reject instead RFC 2865 [38]. + +### 16.3.2 PPP PDP type + +Figure 23 describes the RADIUS message flows between a GGSN and an Authentication, Authorization and Accounting (AAA) server for the case where PPP is terminated at the GGSN. The case where PPP is relayed to an LNS is beyond the scope of the present document. + +![Sequence diagram showing RADIUS message flows for PPP PDP type between TE, MT, SGSN, GGSN, AAA Server, and PDN.](9b9262a549828579ab904148450734f6_img.jpg) + +``` + +sequenceDiagram + participant TE + participant MT + participant SGSN + participant GGSN + participant AAA as AAA Server + participant PDN + + Note right of AAA: (Note 1) + + MT->>SGSN: PDP Context Activate Request + SGSN->>GGSN: Create PDP Context Request + GGSN->>SGSN: Create PDP Context Response + SGSN->>MT: Activate PDP Context Accept + MT->>GGSN: LCP Negotiation + GGSN->>MT: Challenge + MT-->>GGSN: Authentication Request + GGSN->>AAA: Access-Request + Note left of GGSN: (Note 2) + AAA->>GGSN: Access-Accept + Note right of AAA: (Note 5) + GGSN-->>MT: Authentication Response + MT->>GGSN: NCP Negotiation + GGSN->>AAA: Accounting-Request (start) + AAA->>GGSN: Accounting-Response (start) + Note left of GGSN: (Note 3) + MT->>PDN: User Data + Note center: Session + MT-->>GGSN: LCP Termination + Note left of GGSN: (Note 4) + GGSN->>AAA: Accounting-Request (stop) + Note right of AAA: (Note 6) + AAA->>GGSN: Accounting-Response (stop) + GGSN-->>MT: Delete PDP Context Request + MT->>SGSN: Deactivate PDP Context Request + SGSN->>GGSN: Delete PDP Context Request + GGSN->>AAA: Accounting-Request (stop) + Note right of AAA: (Note 7) + AAA->>GGSN: Accounting-Response (stop) + GGSN-->>MT: Deactivate PDP Context Accept + +``` + +Sequence diagram showing RADIUS message flows for PPP PDP type between TE, MT, SGSN, GGSN, AAA Server, and PDN. + +NOTE 1: Separate accounting and Authentication servers may be used. + +NOTE 2: Actual messages depend on the used authentication protocol (e.g. PAP, CHAP). + +NOTE 3: If some external applications require RADIUS Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Response (START) is received from the AAA server. The GGSN may delete the PDP context if the Accounting Response (START) is not received. + +NOTE 4: An LCP termination procedure may be performed. Either the MS or the GGSN may initiate the context deactivation. + +NOTE 5: The Access-Request message shall be used for primary PDP context only. + +NOTE 6: Network Initiated deactivation. + +NOTE 7: User Initiated deactivation. + +Figure 23: RADIUS message flow for PDP type PPP (successful user authentication case) + +When a GGSN receives a Create PDP Context Request message for a given APN, the GGSN shall immediately send a Create PDP context response back to the SGSN. After PPP link setup, the authentication phase may take place. During Authentication phase, the GGSN sends a RADIUS Access-Request to an AAA server. The AAA server authenticates and authorizes the user. If RADIUS is also responsible for IP address allocation the AAA server shall return the allocated IP address or IPv6 prefix in the Access-Accept message (if the user was authenticated). + +If the user is not authenticated, the GGSN shall send a Delete PDP context request to the SGSN. + +Even if the GGSN was not involved in user authentication (e.g. for PPP no authentication may be selected), it may send a RADIUS Accounting-Request START message to an AAA server. This message contains parameters, e.g. a tuple which includes the user-id and IP address or IPv6 prefix, to be used by application servers (e.g. WAP gateway) in order to identify the user. This message also indicates to the AAA server that the user session has started, and the QoS parameters associated to the session. + +If some external applications require RADIUS Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Response (START) is received from the AAA server. The GGSN may delete the PDP context if the Accounting Response (START) is not received. The Authentication and Accounting servers may be separately configured for each APN. + +When the GGSN receives a Delete PDP Context Request message and providing a RADIUS Accounting-Request START message was sent previously, the GGSN shall send a RADIUS Accounting-Request STOP message to the AAA server, which indicates the termination of this particular user session. The GGSN shall immediately send a Delete PDP context response, without waiting for an Accounting-Response STOP message from the AAA server. + +The AAA server shall deallocate the IP address or IPv6 prefix (if any) initially allocated to the subscriber. + +Accounting-Request ON and Accounting-Request OFF messages may be sent from the GGSN to the AAA server to ensure the correct synchronization of the session information in the GGSN and the AAA server. + +The GGSN may send an Accounting-Request ON message to the AAA server to indicate that a restart has occurred. The AAA server may then release the associated resources. + +Prior to a scheduled restart, the GGSN may send Accounting-Request OFF message to the AAA server, the AAA server may then release the associated resources. + +If an Access-Challenge is sent to the GGSN when using PPP PDP type, the GGSN shall handle it by PPP CHAP providing PPP CHAP was the selected Authentication protocol. If CHAP authentication was not selected, authentication shall fail RFC 2865 [38]. + +### 16.3.3 Accounting Update + +During the life of a PDP context some information related to this PDP context may change (i.e. SGSN address if a Inter-SGSN RA update occurs). Upon reception of an UpdatePDPContextRequest from the SGSN, the GGSN may send an Accounting Request Interim-Update to the AAA server to update the necessary information related to this PDP context (see figure 24). Interim updates are also used when the IPv4 address is allocated/released/re-allocated for deferred IPv4 addressing for the PDP type IPv4v6. If the GGSN receives an UpdatePDPContextRequest from the SGSN that specifically indicates a direct tunnel establishment or a direct tunnel teardown (switching the user plane tunnel end back to the SGSN), and only the GTP user plane address and/or the GTP-U TEID have changed, then the GGSN should not send the Accounting Request Interim-Update to the AAA server. In such cases, the GGSN need not wait for the RADIUS AccountingResponse from the AAA server message before sending the UpdatePDPContextResponse to the SGSN. The GGSN may delete the PDP context if the AccountingResponse is not received from the AAA. + +![Sequence diagram showing RADIUS for PDP context Update between SGSN, GGSN, and AAA. The sequence is: 1. SGSN sends UpdatePDPContextReq to GGSN. 2. GGSN sends AccountingReq (Interim-Update) to AAA. 3. AAA sends AccountingRes to GGSN. 4. GGSN sends UpdatePDPContextRes to SGSN. A note indicates that the GGSN does not wait for the AccountingRes from the AAA before sending the UpdatePDPContextRes to the SGSN.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant SGSN + participant GGSN + participant AAA + Note right of GGSN: (Note) + SGSN->>GGSN: UpdatePDPContextReq + GGSN->>AAA: AccountingReq (Interim-Update) + AAA-->>GGSN: AccountingRes + GGSN-->>SGSN: UpdatePDPContextRes + +``` + +Sequence diagram showing RADIUS for PDP context Update between SGSN, GGSN, and AAA. The sequence is: 1. SGSN sends UpdatePDPContextReq to GGSN. 2. GGSN sends AccountingReq (Interim-Update) to AAA. 3. AAA sends AccountingRes to GGSN. 4. GGSN sends UpdatePDPContextRes to SGSN. A note indicates that the GGSN does not wait for the AccountingRes from the AAA before sending the UpdatePDPContextRes to the SGSN. + +NOTE: As shown the GGSN need not wait for the RADIUS AccountingResponse from the AAA server message to send the UpdatePDPContextResponse to the SGSN. The GGSN may delete the PDP context if the AccountingResponse is not received from the AAA. + +Figure 24: RADIUS for PDP context Update + +### 16.3.4 AAA-Initiated PDP context termination + +RADIUS is used as the protocol between the GGSN and an AAA server or proxy for applications (e.g. MMS) to deliver information related to GPRS user session. However some IP applications could need to interwork with the GGSN to terminate a particular PDP context. For this purpose, the AAA server or proxy may send a RADIUS Disconnect Request to the GGSN. As depicted in figure 25, the GGSN may react by deleting the corresponding PDP context or silently discard the Disconnect Request message. For more information on RADIUS Disconnect, see RFC 3576 [41]. If the GGSN deletes the corresponding PDP context, it need not wait for the DeletePDPContextResponse from the SGSN before sending the RADIUS DisconnectResponse to the AAA server. + +The Teardown-Indicator in the RADIUS Disconnect Request message indicates to the GGSN that all PDP contexts for this particular user and sharing the same user session shall be deleted. The PDP contexts belong to the same IP-CAN session are identified by the Acct-Session-Id. The Charging-Id contained in the Acct-Session-Id can be of any PDP context of the user. The GGSN is able to find out all the related PDP contexts sharing the same user session once it has found the exact PDP context from the Acct-Session-Id. If a user has the same user IP address for different sets of PDP contexts towards different networks, only the PDP contexts linked to the one identified by the Acct-Session-Id shall be deleted. + +Since the Charging-Id contained in the Acct-Session-Id is already sufficient to uniquely identify PDP context(s) for a user session on a GGSN, it has no impact if the user IP address is not known by the GGSN (e.g. in the case of transparent PPP IP-CAN sessions). In this case the user IP address in the Disconnect message should be set to zero (e.g. 0.0.0.0 for IPv4). + +![Sequence diagram showing PDP Context deletion with RADIUS. The diagram involves three entities: SGSN, GGSN, and AAA. The sequence of messages is: 1. AAA sends a DisconnectReq to GGSN. 2. GGSN sends a DeletePDPContextReq to SGSN. 3. SGSN sends a DeletePDPContextRes to GGSN. 4. GGSN sends a DisconnectRes to AAA. A note is present below the DisconnectRes message.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +``` + +sequenceDiagram + participant AAA + participant GGSN + participant SGSN + AAA->>GGSN: DisconnectReq + GGSN->>SGSN: DeletePDPContextReq + SGSN->>GGSN: DeletePDPContextRes + Note right of GGSN: (Note) + GGSN->>AAA: DisconnectRes + +``` + +Sequence diagram showing PDP Context deletion with RADIUS. The diagram involves three entities: SGSN, GGSN, and AAA. The sequence of messages is: 1. AAA sends a DisconnectReq to GGSN. 2. GGSN sends a DeletePDPContextReq to SGSN. 3. SGSN sends a DeletePDPContextRes to GGSN. 4. GGSN sends a DisconnectRes to AAA. A note is present below the DisconnectRes message. + +NOTE: As showed on figure 25, the GGSN need not wait for the DeletePDPContextResponse from the SGSN to send the RADIUS DisconnectResponse to the AAA server. + +Figure 25: PDP Context deletion with RADIUS + +## 16.3a Authentication and accounting message flows on Sgi interface + +### 16.3a.1 Authentication, Authorization and Accounting procedures + +When a P-GW receives an initial access request (e.g. Create Session Request or Proxy Binding Update) message for a given APN, the P-GW may (depending on the configuration for this APN) send a RADIUS Access-Request to an AAA server. The AAA server authenticates and authorizes the user. If the RADIUS server is also responsible for IPv4 address and/or IPv6 prefix allocation, the AAA server shall return the allocated IPv4 address and/or IPv6 prefix in the Access-Accept message. + +When PDN type is IPv4v6 and deferred IPv4 addressing via IPv4 address pool in the AAA server is used, the P-GW may initiate RADIUS re-authorization procedures after successful initial attach for the purpose of IPv4 address allocation or to renew the lease for a previously allocated IPv4 address. In this case, the P-GW shall set the Service-Type attribute to "Authorize Only" and the 3GPP-Allocate-IP-Type subattribute to the type of IP address to be allocated in the Access-Request message sent to the AAA server. See subclause 16.4.7.2 for the conditions to use 3GPP-Allocate-IP-Type sub-attribute in Access-Request messages. If the P-GW is using DHCPv4 signalling towards the UE and the RADIUS server includes the Session-Timeout attribute in the Access-Accept, the P-GW may use the Session-Timeout value as the DHCPv4 lease time. The P-GW shall not set the DHCPv4 lease time value higher than the Session-Timeout value. The P-GW may renew the DHCP lease to the UE without re-authorization towards the AAA server providing that the new lease expiry is no later than the Session-Timeout timer expiry. If the P-GW wishes to extend the lease time beyond the current Session-Timeout expiry, it shall initiate a new AAA re-authorization. + +Even if the P-GW was not involved in user authentication, it may send a RADIUS Accounting-Request (START) message to an AAA server. This message may contain parameters, e.g. the tuple which includes the user-id and IPv4 address and/or IPv6 prefix, to be used by application servers (e.g. WAP gateway) in order to identify the user. This message also indicates to the AAA server that the user session has started. The session is uniquely identified by the Acct-Session-Id that is composed of the Charging-Id and the PGW-Address. + +If some external applications require RADIUS Accounting-Request (START) information before they can process user packets, then the selected APN (P-GW) may be configured in such a way that the P-GW drops user data until the Accounting-Response (START) is received from the AAA server. The P-GW may wait for the Accounting-Response (START) before sending the initial access response (e.g. Create Session Response or Proxy Binding Acknowledgement). The P-GW may reject the initial access request if the Accounting-Response (START) is not received. The authentication and accounting servers may be separately configured for each APN. + +For PDN type IPv4, at IPv4 address allocation via DHCPv4 signalling between the UE and the PDN, no IPv4 address is available at initial access. In that case the P-GW may wait to send the Accounting-Request (START) message until the UE receives its IPv4 address in a DHCPACK. + +For PDN type IPv4v6 and deferred IPv4 addressing, when the IPv4 address is allocated or re-allocated, the accounting session that was established for the IPv6 prefix allocation shall be used to inform the accounting server about the allocated IPv4 address by sending RADIUS Accounting-Request Interim-Update with the Framed-IP-Address attribute and its value field containing the allocated IPv4 address. + +When the P-GW receives a message indicating a bearer deactivation request or PDN disconnection request or detach request (e.g. Delete Bearer Command or Proxy Binding Update with lifetime equal 0) and providing a RADIUS Accounting-Request (START) message was sent previously, the P-GW shall send a RADIUS Accounting-Request (STOP) message to the AAA server, which indicates the termination of this particular bearer or user session. The P-GW shall immediately send the corresponding response (e.g. Delete Bearer Request or Proxy Binding Ack with lifetime equal 0) to the peer node (e.g. S-GW) in the Packet Domain, without waiting for an Accounting-Response (STOP) message from the AAA server. + +The AAA server shall deallocate the IPv4 address and/or IPv6 prefix initially allocated to the subscriber, if there is no session for the subscriber. + +For PDN type IPv4v6 and deferred IPv4 addressing, when the P-GW receives a message from the UE or the network indicating the release of the IPv4 address (e.g. receiving DHCPRELEASE) or decides to release the IPv4 address on its own (e.g. due to DHCP lease timer expiry or P-GW assigned IPv4 address), the P-GW shall inform the accounting server about the deallocation of the IPv4 address by sending RADIUS Accounting-Request Interim-Update without the Framed-IP-Address attribute. + +Accounting-Request (ON) and Accounting-Request (OFF) messages may be sent from the P-GW to the AAA server to ensure the correct synchronization of the session information in the P-GW and the AAA server. + +The P-GW may send an Accounting-Request (ON) message to the AAA server to indicate that a restart has occurred. The AAA server may then release the associated resources. + +Prior to a scheduled restart, the P-GW may send Accounting-Request (OFF) message to the AAA server. The AAA server may then release the associated resources. + +If an Access-Challenge is sent to the P-GW when an Access-Request message is pending, the P-GW shall silently discard the Access-Challenge message and it shall treat an Access-Challenge as though it had received an Access-Reject instead RFC 2865 [38]. + +For example, figure 25a.1 represents the RADIUS message flows between a P-GW and an Authentication, Authorization and Accounting (AAA) server, which is applicable for GTP based S5/S8: + +![Sequence diagram showing RADIUS message flow on Sgi interface for GTP-based S5/S8. Lifelines: S-GW, P-GW, AAA server (note 2), and PDN. The diagram illustrates the interaction for session creation and deletion.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +``` + +sequenceDiagram + participant S-GW + participant P-GW + participant AAA_server as AAA server (note 2) + participant PDN + + Note left of S-GW: + S-GW->>P-GW: Create Session Request + P-GW->>AAA_server: Access-Request + AAA_server-->>P-GW: Access-Accept + P-GW->>AAA_server: Accounting-Request (start) + AAA_server-->>P-GW: Accounting-Response (start) + P-GW->>S-GW: Create Session Response (note 1) + Note left of S-GW: + S-GW->>P-GW: Delete Session Request + P-GW->>AAA_server: Accounting-Request (stop) + AAA_server-->>P-GW: Accounting-Response (stop) + P-GW->>S-GW: Delete Session Response + Note left of S-GW: + +``` + +Sequence diagram showing RADIUS message flow on Sgi interface for GTP-based S5/S8. Lifelines: S-GW, P-GW, AAA server (note 2), and PDN. The diagram illustrates the interaction for session creation and deletion. + +NOTE 1: If some external applications require RADIUS Accounting request (Start) information before they can process user packets, then the selected APN (P-GW) may be configured in such a way that the P-GW drops user data until the Accounting Response (START) is received from the AAA server. The P-GW may wait for the Accounting Response (START) before sending the Create Session Response. The P-GW may reject the bearer if the Accounting Response (START) is not received. + +NOTE 2: Separate accounting and authentication servers may be used. + +**Figure 25a.1: An example of RADIUS message flow on Sgi interface for GTP-based S5/S8 (successful user authentication case)** + +### 16.3a.2 Accounting Update + +During the life of an IP-CAN bearer some information related to this bearer may change. Upon occurrence of the following events, the P-GW may send RADIUS Accounting Request Interim-Update to the AAA server: RAT change, S-GW address change and QoS change. Interim updates are also used when the IPv4 address is allocated/released/re-allocated for deferred IPv4 addressing for the PDN type IPv4v6. + +When the P-GW receives a signalling request (e.g. Modify Bearer Request in case of GTP-based S5/S8) that indicates the occurrence of one of these chargeable events, the P-GW may send an Accounting Request Interim-Update to the AAA server to update the necessary information related to this bearer. The P-GW need not wait for the RADIUS AccountingResponse message from the AAA server before sending the response for the triggering signalling message (e.g. Modify Bearer Response). The P-GW may delete the bearer if the AccountingResponse is not received from the AAA. + +The P-GW may also send interim updates at the expiry of an operator configured time limit. + +The following Figure 25a.2 is an example message flow to show the procedure of RADIUS accounting update, which applicable for GTP based S5/S8: + +![Sequence diagram showing RADIUS accounting update for Modify Bearer Request. The diagram involves three entities: S-GW, P-GW, and AAA. The sequence is: 1. S-GW sends a 'Modify Bearer Request' to P-GW. 2. P-GW sends an 'AccountingReq (Interim-Update)' to AAA. 3. AAA sends an 'AccountingRes' back to P-GW. 4. P-GW sends a 'Modify Bearer Response' back to S-GW.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` +sequenceDiagram + participant S-GW + participant P-GW + participant AAA + S-GW->>P-GW: Modify Bearer Request + P-GW->>AAA: AccountingReq (Interim-Update) + AAA-->>P-GW: AccountingRes + P-GW-->>S-GW: Modify Bearer Response +``` + +Sequence diagram showing RADIUS accounting update for Modify Bearer Request. The diagram involves three entities: S-GW, P-GW, and AAA. The sequence is: 1. S-GW sends a 'Modify Bearer Request' to P-GW. 2. P-GW sends an 'AccountingReq (Interim-Update)' to AAA. 3. AAA sends an 'AccountingRes' back to P-GW. 4. P-GW sends a 'Modify Bearer Response' back to S-GW. + +Figure 25a.2: RADIUS accounting update for Modify Bearer Request + +### 16.3a.3 AAA-Initiated Bearer termination + +RADIUS is used as the protocol between the P-GW and the AAA server or proxy for applications (e.g. MMS) to deliver information related to EPS user session. However some IP applications could need to interwork with the P-GW to release the corresponding resource (e.g. terminate a particular bearer or Resource Allocation Deactivation procedures as defined in TS 23.402 [78]). For this purpose, the AAA server or proxy may send a RADIUS Disconnect Request to the P-GW. On receipt of the Disconnect-Request from the AAA server, the P-GW shall release the corresponding resources and reply with a Disconnect-ACK. If the P-GW is unable to release the corresponding resources, it shall reply to the AAA server with a Disconnect-NAK. For more information on RADIUS Disconnect, see IETF RFC 3576 [41]. If the P-GW deletes the corresponding bearer, it need not wait for the response from the S-GW or non-3GPP IP access or ePDG before sending the RADIUS DisconnectResponse to the AAA server. + +The Teardown-Indicator in the RADIUS Disconnect Request message indicates to the P-GW that all IP-CAN bearers for this particular user and sharing the same user session shall be deleted. The IP-CAN bearers that belong to the same IP-CAN session are identified by the Acct-Session-Id. The Charging-Id contained in the Acct-Session-Id can be of any IP-CAN bearer of the user. The P-GW is able to find out all the related IP-CAN bearers sharing the same user session once it has found the exact IP-CAN bearer from the Acct-Session-Id. If a user has the same user IP address for different sets of IP-CAN bearers towards different networks, only the IP-CAN bearers linked to the one identified by the Acct-Session-Id shall be deleted. If the value of Teardown-Indicator is set to "0" or if TI is missing, and if the Acct-Session-Id identifies the default bearer, the P-GW shall tear-down all the IP-CAN bearers that share the same user session identified by the Acct-Session-Id. + +The following Figure 25a.3 is an example message flow to show the procedure of RADIUS AAA-Initiated Bearer termination, which applicable for GTP based S5/S8: + +![Sequence diagram showing AAA-initiated bearer termination. The diagram involves three entities: S-GW, P-GW, and AAA. The sequence of messages is: 1. AAA sends a DisconnectReq to P-GW. 2. P-GW sends a Delete Bearer Request to S-GW. 3. S-GW sends a Delete Bearer Response to P-GW. 4. P-GW sends a DisconnectRes to AAA. A note is present below the DisconnectRes message.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +``` + +sequenceDiagram + participant AAA + participant P-GW + participant S-GW + Note right of P-GW: (Note) + AAA->>P-GW: DisconnectReq + P-GW->>S-GW: Delete Bearer Request + S-GW->>P-GW: Delete Bearer Response + P-GW->>AAA: DisconnectRes + +``` + +Sequence diagram showing AAA-initiated bearer termination. The diagram involves three entities: S-GW, P-GW, and AAA. The sequence of messages is: 1. AAA sends a DisconnectReq to P-GW. 2. P-GW sends a Delete Bearer Request to S-GW. 3. S-GW sends a Delete Bearer Response to P-GW. 4. P-GW sends a DisconnectRes to AAA. A note is present below the DisconnectRes message. + +NOTE: As shown on figure 25a.3, the P-GW need not wait for the Delete Bearer Response from the S-GW to send the RADIUS DisconnectResponse to the AAA server. + +Figure 25a.3: AAA-initiated bearer termination with RADIUS + +## 16.4 List of RADIUS attributes + +The following tables describe the actual content of the RADIUS messages exchanged between the GGSN/P-GW and the AAA server. Other RADIUS attributes may be used as defined in RADIUS RFC(s). Unless otherwise stated, when the encoding scheme of an attribute is specified as UTF-8 encoding, this shall be interpreted as UTF-8 hexadecimal encoding. + +NOTE: Any digit is converted into UTF-8 character. For example, digit 5 is converted to UTF-8 character '5', which in hexadecimal representation has a value 0x35. Similarly, a hexadecimal digit F is converted to either UTF-8 character 'F', which in hexadecimal representation has a value 0x46, or to UTF-8 character 'f', which in hexadecimal representation has a value 0x66. + +### 16.4.1 Access-Request message (sent from GGSN/P-GW to AAA server) + +Table 1 describes the attributes of the Access-Request message. + +Table 1: The attributes of the Access-Request message + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|--------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------------------| +| 1 | User-Name | Username is provided to the GGSN/P-GW by the user in Protocol Configuration Options (PCO) or for the case of the P-GW when multiple authentications are supported in the Additional Protocol Configuration Options (APCO) received during IP-CAN session establishment procedure. If PPP PDP type is used, it is provided to the GGSN by the user during PPP authentication phase. If no username is available, a generic username, configurable on a per APN basis, shall be present. | String | Mandatory | +| 2 | User-Password | User password is provided to the GGSN/P-GW by the user in the PCO or for the case of the P-GW when multiple authentications are supported in the APCO received during IP-CAN session establishment procedure if PAP is used. If PPP PDP type is used, it is provided to the GGSN by the user during PPP authentication phase. If no password is available a generic password, configurable on a per APN basis, shall be present. | String | Conditional
Note 1 | + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|----------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------| +| 3 | CHAP-Password | CHAP password is provided to the GGSN/P-GW by the user in the PCO or for the case of the P-GW when multiple authentications are supported in the APCO received during IP-CAN session establishment procedure. If PPP PDP type is used, it is provided to the GGSN by the user during PPP authentication phase. | String | Conditional Note 2 | +| 4 | NAS-IP-Address | IPv4 address of the GGSN/P-GW for communication with the AAA server. | IPv4 | Conditional Note 3 and 7 | +| 95 | NAS-IPv6-Address | IPv6 address of the GGSN/P-GW for communication with the AAA server. | IPv6 | Conditional Note 3 and 7 | +| 32 | NAS-Identifier | Hostname of the GGSN/P-GW for communication with the AAA server. | String | Conditional Note 3 | +| 6 | Service-Type | Indicates the type of service for this user | 2 (Framed)
or
17 (Authorize Only)
Note 9 | Optional | +| 7 | Framed-Protocol | Indicates the type of protocol for this user | 7 (GPRS PDP Context) | Optional Note 8 | +| 8 | Framed-IP-Address | IPv4 address allocated for this user | IPv4 | Conditional Note 4, Note 11 | +| 9 | Framed-IP-Netmask | Netmask for the user IPv4 address | IPv4 | Conditional Note 4, Note 11 | +| 97 | Framed-IPv6-Prefix | IPv6 prefix allocated for this user | IPv6 | Conditional Note 4, Note 11 | +| 123 | Delegated-IPv6-Prefix | IPv6 prefix delegated to the user. | IPv6 | Conditional Note 10 | +| 96 | Framed-Interface-Id | IPv6 Interface Identifier provided by the GGSN/P-GW to the UE at Initial Attach. | 64 bits as per IETF RFC 3162 [50] | Optional Note 5 | +| 30 | Called-Station-Id | Identifier for the target network | APN (UTF-8 encoded characters) | Mandatory | +| 31 | Calling-Station-Id | This attribute is the identifier for the MS, and it shall be configurable on a per APN basis. | MSISDN in international format according to 3GPP TS 23.003 [40], UTF-8 encoded decimal character. (Note 6) | Optional | +| 60 | CHAP-Challenge | CHAP Challenge is provided to the GGSN/P-GW by the user in the PCO or for the case of the P-GW when multiple authentications are supported in the APCO received during the IP-CAN session establishment procedure. If PPP PDP type is used, it is provided to the GGSN by the user during PPP authentication phase. | String | Conditional Note 2 | +| 61 | NAS-Port-Type | Port type for the GGSN/P-GW | As per RFC 2865 [38] | Optional | +| 26/10415 | 3GPP Vendor-Specific | Sub-attributes according subclause 16.4.7 | See subclause 16.4.7 | Optional except sub-attribute 3 and 27 which are conditional | + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------|----------------------| +| NOTE 1: | Shall be present if PAP is used. | | | | +| NOTE 2: | Shall be present if CHAP is used. | | | | +| NOTE 3: | If the 3GPP-PDP-Type is IPv4, IPv6, or IPv4v6, then the Either NAS-IP-Address or NAS-Identifier shall be present. | | | | +| NOTE 4: | IPv4 address and/or IPv6 prefix attributes shall be present. The IP protocol version for end-user and network may be different. | | | | +| NOTE 5: | As per subclause 9.2.1.1 of 3GPP TS 23.060 [3] and subclause 5.3.1.2.2 of 3GPP TS 23.401 [77] the UE shall use this interface identifier to configure its link-local address, however the UE can choose any interface identifier to generate its IPv6 address(es) other than link-local without involving the network . | | | | +| NOTE 6: | There are no leading characters in front of the country code. | | | | +| NOTE 7: | Either IPv4 or IPv6 address attribute shall be present. | | | | +| NOTE 8: | Framed-Protocol value of 7 is used by both GGSN and P-GW when interworking with RADIUS AAA servers. When used for P-GW, it represents the IP-CAN bearer. | | | | +| NOTE 9: | Service-Type attribute value of "Authorize Only" (RFC 5176 [93]) is only applicable for P-GW/GGSN when deferred IPv4 addressing for a UE needs to be performed for PDN/PDP type IPv4v6. In this use case, the Access Request at UE's initial access shall have Service-Type value "Framed", but the subsequent Access Request shall have Service-Type value of "Authorize Only". In both Access-Request messages, the 3GPP-Allocate-IP-Type sub-attribute shall be present. See subclause 16.4.7.2 for the typical uses cases how 3GPP-Allocate-IP-Type subattribute is utilised in Access-Request messages. | | | | +| NOTE 10: | Delegated IPv6 prefix shall be present if IPv6 prefix delegation is required from the external DN-AAA server. | | | | +| NOTE 11: | For an initial Access-Request message, the Ipv4 address and/or Ipv6 prefix attributes shall be present only if the 3GPP-Allocate-IP-Type sub-attribute is not present or is present with an IP Type value set to zero. | | | | + +## 16.4.2 Access-Accept (sent from AAA server to GGSN/P-GW) + +Table 2 describes the attributes of the Access-Accept message. See RFC 2548 [51] for definition of MS specific attributes. + +**Table 2: The attributes of the Access-Accept message** + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|--------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------------------| +| 1 | User-Name | Username received in the Access-Request message or a substitute username provided by the AAA server. If the User-Name has been received in the Access-Accept message, this user-name shall be used in preference to the above | String | Optional | +| 6 | Service-Type | Indicates the type of service for this user | Framed | Optional | +| 7 | Framed-Protocol | Indicates the type of protocol for this user | 7 (GPRS PDP Context) | Optional
Note 4 | +| 8 | Framed-IP-Address | IPv4 address allocated for this user, if the AAA server is used to allocate IP address. | IPv4 | Conditional
Note 2, Note 8 | +| 9 | Framed-IP-Netmask | Netmask for the user IPv4 address, if the AAA server is used to allocate IP netmask. | IPv4 | Conditional
Note 2, Note 8 | +| 97 | Framed-IPv6-Prefix | IPv6 address prefix allocated for this user, if the AAA server is used to allocate IPv6 address prefixes. | IPv6 | Conditional
Note 2, Note 8 | +| 123 | Delegated-IPv6-Prefix | IPv6 prefix delegated to the user. | IPv6 | Conditional
Note 6 | +| 96 | Framed-Interface-Id | IPv6 Interface Identifier provided by the GGSN/P-GW to the UE at Initial Attach. | 64 bits as per IETF RFC 3162 [50] | Optional
Note 7 | +| 100 | Framed-IPv6-Pool | Name of the IPv6 prefix pool for the specific APN | String | Optional
Note 2 | +| 12 | Framed-MTU | Maximum Transmission Unit of the PDP PDUs, between the MS and GGSN/P-GWs (Note 5) | String | Optional | +| 25 | Class | Identifier to be used in all subsequent accounting messages. | String | Optional
(Note 1) | + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|--------------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|----------------------| +| 27 | Session-Timeout | Indicates the timeout value (in seconds) for the user session | 32 bit unsigned Integer | Optional | +| 28 | Idle-Timeout | Indicates the timeout value (in seconds) for idle user session | 32 bit unsigned Integer | Optional | +| 26/311 | MS- Primary-DNS-Server | Contains the primary DNS server address for this APN | IPv4 | Optional
Note 3 | +| 26/311 | MS-Secondary-DNS-Server | Contains the secondary DNS server address for this APN | IPv4 | Optional
Note 3 | +| 26/311 | MS-Primary-NBNS-Server | Contains the primary NetBIOS name server address for this APN | IPv4 | Optional
Note 3 | +| 26/311 | MS-Secondary-NBNS-Server | Contains the secondary NetBIOS server address for this APN | IPv4 | Optional
Note 3 | +| 26/10415 /17 | 3GPP-IPv6-DNS-Servers | List of IPv6 addresses of DNS servers for this APN | IPv6 | Optional
Note 3 | +| 64 | Tunnel-Type | Indicates the tunneling protocol(s) to be used. Value 3 to be used for L2TP tunnel. | As per RFC 2868 [119] clause 3.1. | Optional
Note 9 | +| 65 | Tunnel-Medium-Type | Indicates which transport medium to use when creating a tunnel for those protocols (such as L2TP). Value 1 for IPv4 and/or value 2 for IPv6 to be used when the Tunnel-Type value 3 for L2TP tunnel is present. | As per RFC 2868 [119] clause 3.2. | Optional
Note 9 | +| 67 | Tunnel-Server-Endpoint | Indicates the address of the server end of the tunnel. | As per RFC 2868 [119] clause 3.4. | Optional
Note 9 | +| 69 | Tunnel-Password | Indicates the password to be used to authenticate to a remote server. | As per RFC 2868 [119] clause 3.5. | Optional | +| 83 | Tunnel-Preference | Indicates the relative preference assigned to each tunnel, If more than one set of tunneling attributes is included. | As per RFC 2868 [119] clause 3.8. | Optional
Note 9 | + +NOTE 1: The presence of this attribute is conditional upon this attribute being received in the Access-Accept message + +NOTE 2: If the 3GPP-PDP-Type is IPv4, IPv6, or IPv4v6, then the IPv4 address and/or IPv6 prefix attributes shall be present. The IP protocol version for the end-user and network may be different. + +NOTE 3: Depending on IP address(es) allocated to the user, either or both IPv4 and IPv6 address attributes shall be present. + +NOTE 4: Framed-Protocol value of 7 is used by both GGSN and P-GW when interworking with RADIUS AAA servers. When used for P-GW, it represents the IP-CAN bearer. + +NOTE 5: In network deployments that have MTU size of 1500 octets in the transport network, providing a link MTU value of 1358 octets to the MS as part of the IP configuration information from the network will prevent the IP layer fragmentation within the transport network between the MS and the GGSN/P-GW. Link MTU considerations are discussed further in Annex C of 3GPP TS 23.060 [3]. + +NOTE 6: Delegated IPv6 prefix shall be present if the user was delegated an IPv6 prefix. + +NOTE 7: As per subclause 9.2.1.1 of 3GPP TS 23.060 [3] and subclause 5.3.1.2.2 of 3GPP TS 23.401 [77] the UE shall use this interface identifier to configure its link-local address, however the UE can choose any interface identifier to generate its IPv6 address(es) other than link-local without involving the network. + +NOTE 8: For an initial Access-Accept message, the IPv4 address and/or IPv6 prefix attributes shall be present only if the 3GPP-Allocate-IP-Type sub-attribute is present with IP Type value 1, 2 or 3 in the initial Access-Request message. + +NOTE 9: If more than one set of "Tunneling" attributes are provided, the "Tunnel-Preference" attribute may be provided in each set to identify the relative preference. + +NOTE: The other optional attributes starting with "Tunnel-" not listed in the above table, can be referred to the IETF RFC 2868[119] with implementation specific. + +### 16.4.3 Accounting-Request START (sent from GGSN/P-GW to AAA server) + +Table 3 describes the attributes of the Accounting-Request START message. + +**Table 3: The attributes of the Accounting-Request START message** + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|--------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|---------------------------| +| 1 | User-Name | Username is provided to the GGSN/P-GW by the user in received during IP-CAN session establishment procedure. If PPP PDP type is used, it is provided to the GGSN by the user during PPP authentication phase. If no username is available a generic username, configurable on a per APN basis, shall be present. If the User-Name has been received in the Access-Accept message, this user-name shall be used in preference to the above | String | Optional | +| 4 | NAS-IP-Address | GGSN/P-GW IPv4 address for communication with the AAA server. | IPv4 | Conditional Notes 1 and 7 | +| 95 | NAS-IPv6-Address | GGSN/P-GW IPv6 address for communication with the AAA server. | IPv6 | Conditional Notes 1 and 7 | +| 32 | NAS-Identifier | Hostname of the GGSN/P-GW for communication with the AAA server. | String | Conditional Note 1 | +| 6 | Service-Type | Indicates the type of service for this user | Framed | Optional | +| 7 | Framed-Protocol | Indicates the type of protocol for this user | 7 (GPRS PDP Context) | Optional Note 8 | +| 8 | Framed-IP-Address | User IPv4 address | IPv4 | Conditional Note 3 | +| 97 | Framed-IPv6-Prefix | User IPv6 Prefix | IPv6 | Conditional Note 3 | +| 123 | Delegated-IPv6-Prefix | Delegates IPv6 Prefix to the user | IPv6 | Conditional Note 9 | +| 96 | Framed-Interface-Id | IPv6 Interface Identifier provided by the GGSN/P-GW to the UE at Initial Attach. | 64 bits as per IETF RFC 3162 [50] | Optional Note 4 | +| 25 | Class | Received in the Access-Accept | String | Conditional (Note 2) | +| 30 | Called-Station-Id | Identifier for the target network | APN (UTF-8 encoded) | Mandatory | +| 31 | Calling-Station-Id | This attribute is the identifier for the MS, and it shall be configurable on a per APN basis. | MSISDN in international format according to 3GPP TS 23.003 [40], UTF-8 encoded decimal character. (Note 6) | Optional | +| 40 | Acct-Status-Type | Type of accounting message | START | Mandatory | +| 41 | Acct-Delay-Time | Indicates how many seconds the GGSN/P-GW has been trying to send this record for, and can be subtracted from the time of arrival on the AAA server to find the approximate time (in seconds) of the event generating this Accounting-Request. | 32 unsigned integer | Optional | + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|----------|----------------------|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------| +| 44 | Acct-Session-Id | User session identifier. | GGSN/P-GW IP address (IPv4 or IPv6) and Charging-ID concatenated in a UTF-8 encoded hexadecimal character. (Note 5) | Mandatory | +| 45 | Acct-Authentic | Authentication method | RADIUS or LOCAL | Optional | +| 61 | NAS-Port-Type | Port type for the GGSN/P-GW | As per RFC 2865 [38] | Optional | +| 26/10415 | 3GPP Vendor-Specific | Sub-attributes according subclause 16.4.7. | See subclause 16.4.7 | Optional except sub-attribute 3 which is conditional | + +NOTE 1: Either NAS-IP-Address or NAS-Identifier shall be present. + +NOTE 2: The presence of this attribute is conditional upon this attribute being received in the Access-Accept message + +NOTE 3: If the 3GPP-PDP-Type is IPv4, IPv6, or IPv4v6, IPv4 address and/or IPv6 prefix attributes shall be present. The IP protocol version for end-user and network may be different. + +NOTE 4: As per subclause 9.2.1.1 of 3GPP TS 23.060 [3] and subclause 5.3.1.2.2 of 3GPP TS 23.401 [77] the UE shall use this interface identifier to configure its link-local address, however the UE can choose any interface identifier to generate its IPv6 address(es) other than link-local without involving the network . + +NOTE 5: The GGSN/P-GW IP address is the same one that is used in the CDRs generated by the GGSN/P-GW. + +NOTE 6: There are no leading characters in front of the country code. + +NOTE 7: Either IPv4 or IPv6 address attribute shall be present. + +NOTE 8: Framed-Protocol value of 7 is used by both GGSN and P-GW when interworking with RADIUS AAA servers. When used for P-GW, it represents the IP-CAN bearer. + +NOTE 9: Delegated IPv6 prefix shall be present if IPv6 prefix delegation is required from the external DN-AAA server. + +#### 16.4.4 Accounting Request STOP (sent from GGSN/P-GW to AAA server) + +Table 4 describes the attributes of the Accounting-Request STOP message. + +**Table 4: The attributes of the Accounting-Request STOP message** + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|--------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|---------------------------| +| 1 | User-Name | Username is provided to the GGSN/P-GW by the user in the PCO or for the case of the P-GW when multiple authentications are supported in the APCO received during IP-CAN session establishment procedure. If PPP PDP type is used, it is provided to the GGSN by the user during PPP authentication phase. If no username is available a generic username, configurable on a per APN basis, shall be present. If the User-Name has been received in the Access-Accept message, this username shall be used in preference to the above. | String | Optional | +| 4 | NAS-IP-Address | IPv4 address of the GGSN/P-GW for communication with the AAA server. | IPv4 | Conditional Notes 1 and 7 | +| 95 | NAS-IPv6-Address | IPv6 address of the GGSN/P-GW for communication with the AAA server. | IPv6 | Conditional Notes 1 and 7 | +| 32 | NAS-Identifier | Hostname of the GGSN/P-GW for communication with the AAA server. | String | Conditional Note 1 | +| 6 | Service-Type | Indicates the type of service for this user | Framed | Optional | +| 7 | Framed-Protocol | Indicates the type of protocol for this user | 7 (GPRS PDP Context) | Optional Note 8 | +| 8 | Framed-IP-Address | User IPv4 address | IPv4 | Conditional Note 3 | + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|--------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-----------------------| +| 97 | Framed-IPv6-Prefix | User IPv6 Prefix | IPv6 | Conditional
Note 3 | +| 123 | Delegated-IPv6-Prefix | Delegated IPv6 Prefix to the user | IPv6 | Conditional
Note 9 | +| 96 | Framed-Interface-Id | IPv6 Interface Identifier provided by the GGSN/P-GW to the UE at Initial Attach | 64 bits as per IETF RFC 3162 [50] | Optional
Note 4 | +| 25 | Class | Received in the Access-Accept | String | Optional
(Note 2) | +| 30 | Called-Station-Id | Identifier for the target network | APN (UTF-8 encoded characters) | Mandatory | +| 31 | Calling-Station-Id | This attribute is the identifier for the MS, and it shall be configurable on a per APN basis. | MSISDN in international format according to 3GPP TS 23.003 [40], UTF-8 encoded characters. (Note 6) | Optional | +| 40 | Acct-Status-Type | Indicates the type of accounting request | STOP | Mandatory | +| 41 | Acct-Delay-Time | Indicates how many seconds the GGSN/P-GW has been trying to send this record for, and can be subtracted from the time of arrival on the AAA server to find the approximate time of the event generating this Accounting-Request | Second | Optional | +| 42 | Acct-Input-Octets | GGSN/P-GW counted number of octets sent by the user for the IP-CAN bearer | 32 bit unsigned integer | Optional | +| 43 | Acct-Output-Octets | GGSN/P-GW counted number of octets received by the user for the IP-CAN bearer | 32 bit unsigned integer | Optional | +| 44 | Acct-Session-Id | User session identifier. | GGSN/P-GW IP address (IPv4 or IPv6) and Charging-ID concatenated in a UTF-8 encoded hexadecimal character. (Note 5) | Mandatory | +| 45 | Acct-Authentic | Authentication method | RADIUS or LOCAL | Optional | +| 46 | Acct-Session-Time | Duration of the session | Second | Optional | +| 47 | Acct-Input-Packets | GGSN/P-GW counted number of packets sent by the user | Packet | Optional
(Note 10) | +| 48 | Acct-Output-Packets | GGSN/P-GW counted number of packets received by the user | Packet | Optional
(Note 10) | +| 49 | Acct-Terminate-Cause | Indicate how the session was terminated | See IETF RFC 2866 [39] | Optional | +| 52 | Acct-Input-Gigawords | It indicates how many times the Acct-Input-Octets counter has wrapped around 2 32 and is present if the Acct-Input-Octets counter has wrapped around 2 32 . | 32 bit unsigned integer
See IETF RFC 2869 [116] | Conditional | +| 53 | Acct-Output-Gigawords | It indicates how many times the Acct-Output-Octets counter has wrapped around 2 32 and is present if the Acct-Output-Octets counter has wrapped around 2 32 . | 32 bit unsigned integer
See IETF RFC 2869 [116] | Conditional | +| 61 | NAS-Port-Type | Port type for the GGSN/P-GW | As per IETF RFC 2865 [38] | Optional | + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-----------------------------------------------|----------------------|------------------------------------------------------| +| 26/10415 | 3GPP Vendor-Specific | Sub-attributes according to subclause 16.4.7. | See subclause 16.4.7 | Optional except sub-attribute 3 which is conditional | +| NOTE 1: Either NAS-IP-Address or NAS-Identifier shall be present.
NOTE 2: The presence of this attribute is conditional upon this attribute being received in the Access-Accept message
NOTE 3: If the 3GPP-PDP-Type is IPv4, IPv6, or IPv4v6, IPv4 address and/or IPv6 prefix attributes shall be present. The IP protocol version for end-user and network may be different.
NOTE 4: As per subclause 9.2.1.1 of 3GPP TS 23.060 [3] and subclause 5.3.1.2.2 of 3GPP TS 23.401 [77] the UE shall use this interface identifier to configure its link-local address, however the UE can choose any interface identifier to generate its IPv6 address(es) other than link-local without involving the network .
NOTE 5: The GGSN/P-GW IP address is the same one that is used in the CDRs generated by the GGSN/P-GW.
NOTE 6: There are no leading characters in front of the country code.
NOTE 7: Either IPv4 or IPv6 address attribute shall be present.
NOTE 8: Framed-Protocol value of 7 is used by both GGSN and P-GW when interworking with RADIUS AAA servers. When used for P-GW, it represents the IP-CAN bearer.
NOTE 9: Delegated IPv6 prefix shall be present if IPv6 prefix delegation is required from the external DN-AAA server.
NOTE 10: If the P-GW is split into a user plane node and control plane node according to 3GPP TS 29.244 [114], the user plane function "MNOP" need to be supported. | | | | | + +### 16.4.5 Accounting Request ON (optionally sent from GGSN/P-GW to AAA server) + +Table 5 describes the attributes of the Accounting-Request ON message. + +**Table 5: The attributes of the Accounting-Request ON message** + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|--------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------|--------------------------------|------------------------------| +| 4 | NAS-IP-Address | IPv4 address of the GGSN/P-GW for communication with the AAA server. | IPv4 | Conditional
Notes 1 and 2 | +| 95 | NAS-IPv6-Address | IPv6 address of the GGSN/P-GW for communication with the AAA server. | IPv6 | Conditional
Notes 1 and 2 | +| 30 | Called-Station-ID | Identifier for the target network. | APN (UTF-8 encoded characters) | Optional | +| 32 | NAS-Identifier | Hostname of the GGSN/P-GW for communication with the AAA server. | String | Conditional
Note 1 | +| 40 | Acct-Status-Type | Type of accounting message | Accounting-On | Mandatory | +| NOTE 1: Either NAS-IP-Address or NAS-Identifier shall be present.
NOTE 2: Either IPv4 or IPv6 address attribute shall be present. | | | | | + +### 16.4.6 Accounting Request OFF (optionally sent from GGSN/P-GW to AAA server) + +Table 6 describes the attributes of the Accounting-Request OFF message. + +**Table 6: The attributes of the Accounting-Request OFF message** + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|--------|-------------------|--------------------------------------------------------------------|--------------------------------|------------------------------| +| 4 | NAS-IP-Address | IP address of the GGSN/P-GW for communication with the AAA server. | IPv4 | Conditional
Notes 1 and 2 | +| 95 | NAS-IPv6-Address | IP address of the GGSN/P-GW for communication with the AAA server. | IPv6 | Conditional
Notes 1 and 2 | +| 30 | Called-Station-ID | Identifier for the target network. | APN (UTF-8 encoded characters) | Optional | +| 32 | NAS-Identifier | Hostname of the GGSN/P-GW for communication with the AAA server. | String | Conditional
Note 1 | +| 40 | Acct-Status-Type | Type of accounting message | Accounting-Off | Mandatory | + +NOTE 1: Either NAS-IP-Address or NAS-Identifier shall be present. +NOTE 2: Either IPv4 or IPv6 address attribute shall be present. + +## 16.4.7 Sub-attributes of the 3GPP Vendor-Specific attribute + +Table 7 describes the sub-attributes of the 3GPP Vendor-Specific attribute of the Access-Request, Access-Accept, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update and Disconnect-Request messages. The applicability of each sub-attribute to Gi and Sgi reference points is also indicated in Table 7. + +### 16.4.7.1 Presence of the 3GPP Vendor-Specific attribute in RADIUS messages. + +**Table 7: List of the 3GPP Vendor-Specific sub-attributes** + +| Sub-attr # | Sub-attribute Name | Description | Presence Requirement | Associated attribute (Location of Sub-attr) | Applicable Reference Points | +|------------|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|------------------------------------------------------------------------------------------------------|-----------------------------| +| 1 | 3GPP-IMSI | IMSI for this user | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi, Sgi | +| 2 | 3GPP-Charging-Id | For GGSN, Charging ID for this PDP Context (this together with the GGSN IP Address constitutes a unique identifier for the PDP context).
For P-GW, Charging ID for this IP-CAN bearer (this together with the P-GW IP address constitutes a unique identifier for the IP-CAN bearer). | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi, Sgi | +| 3 | 3GPP-PDP-Type | For GGSN, it indicates the type of PDP context, e.g. IP or PPP. For P-GW, it indicates the PDN Type, e.g. IPv4, IPv6, IPv4v6. | Conditional (mandatory if attribute 7 is present) | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi, Sgi | +| 4 | 3GPP-CG-Address | Charging Gateway IP address | Optional | Access-Request, Accounting-Request START, Accounting- | Gi, Sgi | + +| Sub-attr # | Sub-attribute Name | Description | Presence Requirement | Associated attribute (Location of Sub-attr) | Applicable Reference Points | +|------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------------------------------------------------------------------------------------------------|-----------------------------| +| | | | | Request STOP, Accounting-Request Interim-Update | | +| 5 | 3GPP-GPRS-Negotiated-QoS-Profile | For GGSN, it represents the QoS profile for the PDP context.
For P-GW, it represents the QoS profile for the EPS bearer and the authorized APN-AMBR. | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi
Sgi | +| 6 | 3GPP-SGSN-Address | For GGSN, it represents the SGSN IPv4 address that is used by the GTP control plane for the handling of control messages.
For P-GW, it represents the IPv4 address of the S-GW, trusted non-3GPP IP access or ePDG that is used on S5/S8, S2a or S2b, or the SGSN IPv4 address for GnGp SGSN accesses to the PGW for the handling of control messages.
The address may be used to identify the PLMN to which the user is attached. | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi,
Sgi | +| 7 | 3GPP-GGSN-Address | For GGSN, it represents the GGSN IPv4 address that is used by the GTP control plane for the context establishment.
For P-GW, it represents the P-GW IPv4 address that is used on S5/S8, S2a, S2b or S2c control plane for the IP-CAN session establishment.
The address is the same as the GGSN/P-GW IPv4 address used in the CDRs generated by the GGSN/P-GW. | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi,
Sgi | +| 8 | 3GPP-IMSI-MCC-MNC | MCC and MNC extracted from the user's IMSI (first 5 or 6 digits, as applicable from the presented IMSI). | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi,
Sgi | +| 9 | 3GPP-GGSN- MCC-MNC | MCC-MNC of the network the GGSN or the P-GW belongs to. | Optional | Access-Request, Accounting-Request START, | Gi,
Sgi | + +| Sub-attr # | Sub-attribute Name | Description | Presence Requirement | Associated attribute (Location of Sub-attr) | Applicable Reference Points | +|------------|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------------------------------------------------------------------------------------------------|-----------------------------| +| | | | | Accounting-Request STOP, Accounting-Request Interim-Update | | +| 10 | 3GPP-NSAPI | For GGSN, it identifies a particular PDP context for the associated PDN and MSISDN/IMSI from creation to deletion. For P-GW, it identifies the EPS Bearer ID if it is known to the P-GW (i.e. GTP-based S5/S8 is in use). | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi, Sgi | +| 11 | 3GPP-Session-Stop-Indicator | Indicates to the AAA server that the last PDP context or EPS Bearer of a session is released and that the IP-CAN session has been terminated. | Optional | Accounting Request STOP | Gi, Sgi | +| 12 | 3GPP-Selection-Mode | For GGSN it contains the Selection mode for this PDP Context received in the Create PDP Context Request message. For P-GW it contains the Selection mode for this EPS Bearer received in the Create Session Request message. | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi, Sgi | +| 13 | 3GPP-Charging-Characteristics | For GGSN, it contains the charging characteristics for this PDP Context received in the Create PDP Context Request Message (only available in R99 and later releases). For P-GW, it contains the charging characteristics for the IP-CAN bearer. | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi, Sgi | +| 14 | 3GPP-CG-IPv6-Address | Charging Gateway IPv6 address | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi, Sgi | +| 15 | 3GPP-SGSN-IPv6-Address | For GGSN, it represents the SGSN IPv6 address that is used by the GTP control plane for the handling of control messages. | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi, Sgi | + +| Sub-attr # | Sub-attribute Name | Description | Presence Requirement | Associated attribute (Location of Sub-attr) | Applicable Reference Points | +|------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------------------------------------------------------------------------------------------------|-----------------------------| +| | | For P-GW, it represents the IPv6 address of the S-GW, trusted non-3GPP IP access or ePDG that is used on S5/S8, S2a or S2b, or the SGSN IPv6 address for GnGp SGSN accesses to the PGW for the handling of control messages. The address may be used to identify the PLMN to which the user is attached. | | | | +| 16 | 3GPP-GGSN-IPv6-Address | For GGSN, it represents the GGSN IPv6 address that is used by the GTP control plane for the context establishment. For P-GW, it represents the P-GW IPv6 address that is used on S5/S8, S2a, S2b or S2c control plane for the IP-CAN session establishment. | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi, Sgi | +| 17 | 3GPP-IPv6-DNS-Servers | List of IPv6 addresses of DNS servers for an APN | Optional | Access-Accept | Gi, Sgi | +| 18 | 3GPP-SGSN-MCC-MNC | For GGSN and PGW connected to a Gn/Gp SGSN, it represents the MCC and MNC extracted from the RAI within the Create PDP Context Request or Update PDP Context Request message. For P-GW in GTP/PMIP S5/S8 it represents the MCC and MNC extracted from the Serving Network. For PGW connected to S2a, it represents the MCC and MNC extracted from the Serving Network. For PGW connected to S2b, it represents the MCC and MNC extracted from the Serving Network. | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi, Sgi | + +| Sub-attr # | Sub-attribute Name | Description | Presence Requirement | Associated attribute (Location of Sub-attr) | Applicable Reference Points | +|------------|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|------------------------------------------------------------------------------------------------------|-----------------------------| +| 19 | 3GPP-Teardown-Indicator | Indicate to the GGSN/P-GW that all IP-CAN bearers for this particular user and sharing the same user session need to be deleted. | Optional | Disconnect Request | Gi
Sgi | +| 20 | 3GPP-IMEISV | International Mobile Equipment Id and its Software Version | Optional | Accounting-Request START, Accounting-Request STOP, Access-Request | Gi,
Sgi | +| 21 | 3GPP-RAT-Type | Indicate which Radio Access Technology is currently serving the UE | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi,
Sgi | +| 22 | 3GPP-User-Location-Info | Indicate details of where the UE is currently located (e.g. SAI or CGI). | Optional | Accounting-Request START, Access-Request, Accounting-Request STOP, Accounting-Request Interim-Update | Gi,
Sgi | +| 23 | 3GPP-MS-TimeZone | Indicate the offset between universal time and local time in steps of 15 minutes of where the MS/UE currently resides. | Optional | Accounting-Request START, Access-Request, Accounting-Request STOP, Accounting-Request Interim-Update | Gi,
Sgi | +| 24 | 3GPP-CAMEL-Charging-Info | Used to copy any CAMEL Information present in S-CDR(s). | Optional | Accounting-Request START, Access-Request | Gi | +| 25 | 3GPP-Packet-Filter | Packet Filter used for this PDP context or EPS bearer. | Optional | Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi,
Sgi | +| 26 | 3GPP-Negotiated-DSCP | DSCP used to mark the IP packets of this PDP context on the Gi interface or EPS Bearer context on the Sgi interface | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi,
Sgi | +| 27 | 3GPP-Allocate-IP-Type | Indicates whether the Access-Request is sent for user authentication only and/or for allocation of an IPv4 address and/or of an IPv6 prefix | Conditional (see subclause 16.4.7.2 for conditions) | Access-Request | Gi,
Sgi | + +| Sub-attr # | Sub-attribute Name | Description | Presence Requirement | Associated attribute (Location of Sub-attr) | Applicable Reference Points | +|------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|---------------------------------------------------------------------------------------------------------------------|-----------------------------| +| 28 | External-Identifier | A globally unique identifier of a UE used towards external servers instead of IMSI and MSISDN, refer to 3GPP TS 23.682 [100] and 3GPP TS 23.003 [40]. | Optional | Access-Request, Access-Accept, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Gi, Sgi | +| 29 | TWAN-Identifier | Indicates the UE location in a Trusted WLAN Access Network. | Optional | Accounting-Request START, Access-Request, Accounting-Request STOP, Accounting-Request Interim-Update | Sgi | +| 30 | 3GPP-User-Location-Info-Time | Indicate the time at which the UE was last known to be in the location which is reported during bearer deactivation or PDN disconnection procedure. | Optional | Accounting-Request STOP | Gi, Sgi | +| 31 | 3GPP-Secondary-RAT-Usage | Indicates the data usage in the secondary RAT. | Optional | Accounting-Request STOP, Accounting-Request Interim-Update | Sgi | +| 32 | 3GPP-UE-Local-IP-Address | Indicates the UE local IP address in an untrusted WLAN Access Network. | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Sgi | +| 33 | 3GPP-UE-Source-Port | Indicates the UE UDP or TCP source port number. | Optional | Access-Request, Accounting-Request START, Accounting-Request STOP, Accounting-Request Interim-Update | Sgi | + +The information represented by some of the Sgi sub-attributes may not be available to the P-GW depending on the UE's radio access and the S5/S8 protocol type (GTP or PMIP). For example, the P-GW will be aware of the User Location Info (e.g. TAI) if the user is in LTE access and GTP based S5/S8 is used. However, such information is not passed to the P-GW when PMIP based S5/S8 is utilised. In such scenarios, if a sub-attribute is configured in the P-GW to be transferred to the RADIUS AAA server, but the information in the P-GW is not up to date or not available; the P-GW shall not send the corresponding sub-attribute, unless otherwise stated in the following subclause where the encoding of each sub-attribute is specified. + +#### 16.4.7.2 Coding 3GPP Vendor-Specific RADIUS attributes + +In this subclause the provisions of IETF RFC 2865 [38] apply, which in particular specify the following: + +- the Length field of an attribute is one octet, and it indicates the length of this Attribute including the Type, Length and Value fields. + +- type String may be 1-253 octets long and it contains binary data (values 0 through 255 decimal, inclusive). Strings of length zero (0) shall not be sent, but the entire attribute shall be omitted. A NULL terminating character shall not be appended to an attribute of type String. +- type Text may be 1-253 octets long and it contains UTF-8 encoded characters. Text of length zero (0) shall not be sent, but the entire attribute shall be omitted. A NULL terminating character shall not be appended to an attribute of type Text. +- type Address is 32 bit value and most significant octet is the first one. +- type Integer is 32 bit unsigned value and most significant octet is the first one. + +The RADIUS vendor Attribute is encoded as follows (as per IETF RFC 2865 [38]) + +| Octets | Bits | | | | | | | | +|--------|-------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | Type = 26 | | | | | | | | +| 2 | Length = n | | | | | | | | +| 3 | Vendor id octet 1 | | | | | | | | +| 4 | Vendor id octet 2 | | | | | | | | +| 5 | Vendor id octet 3 | | | | | | | | +| 6 | Vendor id octet 4 | | | | | | | | +| 7-n | String | | | | | | | | + +$n \geq 7$ + +3GPP Vendor Id = 10415 + +The string part is encoded as follows: + +| Octets | Bits | | | | | | | | +|--------|-----------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = | | | | | | | | +| 2 | 3GPP Length = m | | | | | | | | +| 3-m | 3GPP value | | | | | | | | + +$m \geq 2$ and $m \leq 248$ + +The 3GPP specific attributes encoding is clarified below. + +NOTE 1: Unless otherwise stated, the encoding of the value field of a 3GPP vendor-specific attribute is identical for Gi and Sgi. + +## 1 – 3GPP-IMSI + +| Octets | Bits | | | | | | | | +|--------|--------------------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 1 | | | | | | | | +| 2 | 3GPP Length= m | | | | | | | | +| 3-m | IMSI digits 1-n (UTF-8 encoded characters) | | | | | | | | + +3GPP Type: 1 + +$n \leq 15$ + +Length: $m \leq 17$ + +IMSI value: Text type: + +A GGSN (or a P-GW) receives IMSI that is encoded according to 3GPP TS 29.060 [24] (or 3GPP TS 29.274 [81]) and converts IMSI into the UTF-8 characters, which are encoded as defined in 3GPP TS 23.003 [40]. There shall be no padding characters between the MCC and MNC, and between the MNC and MSIN. If the IMSI is less than 15 digits, the padding in the GTP information element shall be removed by the GGSN (or the P-GW) and not encoded in this sub-attribute. + +## 2 – 3GPP-Charging ID + +| Octets | Bits | | | | | | | | +|--------|---------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 2 | | | | | | | | +| 2 | 3GPP Length= 6 | | | | | | | | +| 3 | Charging ID value Octet 1 | | | | | | | | +| 4 | Charging ID value Octet 2 | | | | | | | | +| 5 | Charging ID value Octet 3 | | | | | | | | +| 6 | Charging ID value Octet 4 | | | | | | | | + +3GPP Type: 2 + +Length: 6 + +Charging ID value: 32 bits unsigned integer + +## 3 – 3GPP-PDP type + +| Octets | Bits | | | | | | | | +|--------|------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 3 | | | | | | | | +| 2 | 3GPP Length= 6 | | | | | | | | +| 3 | PDP type octet 1 | | | | | | | | +| 4 | PDP type octet 2 | | | | | | | | +| 5 | PDP type octet 3 | | | | | | | | +| 6 | PDP type octet 4 | | | | | | | | + +3GPP Type: 3 + +Length: 6 + +PDP type value: Unsigned 32 bits integer type + +PDP type may have the following values: + +- 0 = IPv4 +- 1 = PPP +- 2 = IPv6 +- 3 = IPv4v6 +- 4 = Non-IP +- 5 = Unstructured +- 6 = Ethernet + +For P-GW, this sub-attribute represents PDN Type and therefore only the values "0", "2", "3" and "4" are applicable. + +The value 5 Unstructured and 6 Ethernet of PDP type does not apply for the present specification. For specifications referencing the present RADIUS VSA, those values shall only apply if it is explicitly endorsed within the referencing specification. + +#### 4 – 3GPP-Charging Gateway address + +| Octets | Bits | | | | | | | | +|--------|--------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 4 | | | | | | | | +| 2 | 3GPP Length= 6 | | | | | | | | +| 3 | Charging GW addr Octet 1 | | | | | | | | +| 4 | Charging GW addr Octet 2 | | | | | | | | +| 5 | Charging GW addr Octet 3 | | | | | | | | +| 6 | Charging GW addr Octet 4 | | | | | | | | + +3GPP Type: 4 + +Length: 6 + +Charging GW address value: Address type. + +#### 5 – 3GPP-GPRS Negotiated QoS profile + +| Octets | Bits | | | | | | | | +|--------|---------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 5 | | | | | | | | +| 2 | 3GPP Length= L | | | | | | | | +| 3 – L | UTF-8 encoded QoS profile | | | | | | | | + +3GPP Type: 5 + +Length: For GGSN, $L \leq 37$ (release 7 or higher) or $L \leq 33$ (release 6 or release 5) or $L \leq 27$ (release 4 or release 99) or $L = 11$ (release 98). For P-GW, the length varies depending on the value of QCI. See below for details. + +QoS profile value: Text type + +UTF-8 encoded QoS profile syntax: + +" – " + + = UTF-8 encoded number (two characters) : + +For GGSN: + +"98" = Release 98 + +"99"= Release 99 or release 4 + +"05"= Release 5 or release 6 + +"07"= Release 7 or higher + +For P-GW: + +"08"= Release 8 or higher + +For SMF: + +"15"= Release 15 or higher + + = UTF-8 encoded QoS profile for the release indicated by the release indicator. + +The UTF-8 encoding of a QoS IE is defined as follows: each octet is described by 2 UTF-8 encoded characters, defining its hexadecimal representation. + +For GGSN: + +The QoS profile definition is in 3GPP TS 24.008 [54]. + +The release 98 QoS profile data is 3 octets long, which then results in a 6 octets UTF-8 encoded string. + +The release 99 and release 4 QoS profile data is 11 octets long, which results in a 22 octets UTF-8 encoded string. + +The release 5 and release 6 QoS profile data is 14 octets long, which results in a 28 octets UTF-8 encoded string. + +The release 7 (and higher) QoS profile data is 16 octets long, which results in a 32 octets UTF-8 encoded string. + +For P-GW: + +It contains the following QoS parameters associated with the EPS bearer: + +- QCI +- ARP +- GBR QoS information (UL/DL MBR, UL/DL GBR) or UL/DL APN-AMBR. In other words if the value of QCI indicates a GBR bearer, the GBR QoS information shall be present. If the value of QCI indicates a non-GBR bearer, the APN-AMBR information shall be present. + +The encoding of the EPS bearer QoS profile parameters is specified in 3GPP TS 29.274 [81]: ARP is specified in Bearer QoS IE; QCI, UL MBR, DL MBR, UL GBR and DL GBR are specified in Flow QoS IE; UL APN-AMBR and DL APN-AMBR are specified in AMBR IE. + +For GBR QCIs, the encoding of UTF-8 encoded QoS Profile field shall be as follows: + +| | | +|---------|---------------------------------------------| +| 1-2 | = " 08" (UTF-8 encoded) | +| 3 | "_" (UTF-8 encoded) | +| 4-5 | ARP (UTF-8 encoded) | +| 6-7 | QCI (UTF-8 encoded) | +| 8-m | UL MBR (UTF-8 encoded) | +| (m+1)-n | DL MBR (UTF-8 encoded) | +| (n+1)-o | UL GBR (UTF-8 encoded) | +| (o+1)-p | DL GBR (UTF-8 encoded) | + +For non-GBR QCIs, the UL/DL MBR and UL/DL GBR fields shall not be present; UL APN-AMBR and DL APN-AMBR fields shall be encoded (in UTF-8 encoded format) respectively after the QCI field. + +For SMF: + +It contains the following QoS parameters associated with the QoS flow: + +- 5QI +- ARP +- GBR QoS information (UL/DL MFBR, UL/DL GFBR) or UL/DL Session-AMBR. In other words if the value of 5QI indicates a GBR QoS flow, the GBR QoS information shall be present. If the value of 5QI indicates a non-GBR QoS flow, the Session-AMBR information shall be present. + +5QI value range is 0-255. ARP shall be encoded as Allocation/Retention Priority IE defined in 3GPP TS 29.274 [81]. The UTF-8 encoded UL/DL MFBR, UL/DL GFBR and UL/DL Session-AMBR has the following pattern: + +'^\d+(\.\d+)? (bps|Kbps|Mbps|Gbps|Tbps)\$' + +Examples: + +"125 Mbps", "0.125 Gbps", "125000 Kbps" + +For GBR 5QIs, the encoding of UTF-8 encoded QoS Profile field shall be as follows: + +| | | +|-------------|--------------------------------------------| +| 1-2 | = "15" (UTF-8 encoded) | +| 3 | "-" (UTF-8 encoded) | +| 4-5 | ARP (UTF-8 encoded) | +| 6-7 | 5QI (UTF-8 encoded) | +| 8-9 | UL MFBR length (UTF-8 encoded) | +| 10-m | UL MFBR (UTF-8 encoded) | +| (m+1)-(m+2) | DL MFBR length (UTF-8 encoded) | +| (m+3)-n | DL MFBR (UTF-8 encoded) | +| (n+1)-(n+2) | UL GFBR length (UTF-8 encoded) | +| (n+3)-o | UL GFBR (UTF-8 encoded) | +| (o+1)-(o+2) | UL GFBR length (UTF-8 encoded) | +| (o+3)-p | DL GFBR (UTF-8 encoded) | + +For non-GBR 5QIs, the encoding of UTF-8 encoded QoS Profile field shall be as follows: + +| | | +|-------------|---------------------------------------------| +| 1-2 | - = "15" (UTF-8 encoded) | +| 3 | "-" (UTF-8 encoded) | +| 4-5 | ARP (UTF-8 encoded) | +| 6-7 | 5QI (UTF-8 encoded) | +| 8-9 | UL Session-AMBR length (UTF-8 encoded) | +| 10-m | UL Session-AMBR (UTF-8 encoded) | +| (m+1)-(m+2) | DL Session-AMBR length (UTF-8 encoded) | +| (m+3)-n | DL Session-AMBR (UTF-8 encoded) | + +The above structures for encoding the QoS profile of Release indicator "15" do not apply for the present specification. For specifications referencing the present VSA, those formats shall only apply if it is explicitly endorsed within the referencing specification. + +## 6 – 3GPP-SGSN address + +| Octets | Bits | | | | | | | | +|--------|-------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 6 | | | | | | | | +| 2 | 3GPP Length= 6 | | | | | | | | +| 3 | SGSN addr Octet 1 | | | | | | | | +| 4 | SGSN addr Octet 2 | | | | | | | | +| 5 | SGSN addr Octet 3 | | | | | | | | +| 6 | SGSN addr Octet 4 | | | | | | | | + +3GPP Type: 6 + +Length: 6 + +SGSN address value: Address type. + +## 7 – 3GPP-GGSN address + +| Octets | Bits | | | | | | | | +|--------|-------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 7 | | | | | | | | +| 2 | 3GPP Length= 6 | | | | | | | | +| 3 | GGSN addr Octet 1 | | | | | | | | +| 4 | GGSN addr Octet 2 | | | | | | | | +| 5 | GGSN addr Octet 3 | | | | | | | | +| 6 | GGSN addr Octet 4 | | | | | | | | + +3GPP Type: 7 + +Length: 6 + +GGSN address value: Address type. + +## 8 – 3GPP-IMSI MCC-MNC + +| Octets | Bits | | | | | | | | +|--------|-------------------------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 8 | | | | | | | | +| 2 | 3GPP Length= n | | | | | | | | +| 3 | MCC digit1 (UTF-8 encoded character) | | | | | | | | +| 4 | MCC digit2 (UTF-8 encoded character) | | | | | | | | +| 5 | MCC digit3 (UTF-8 encoded character) | | | | | | | | +| 6 | MNC digit1 (UTF-8 encoded character) | | | | | | | | +| 7 | MNC digit2 (UTF-8 encoded character) | | | | | | | | +| 8 | MNC digit3 if present (UTF-8 encoded character) | | | | | | | | + +3GPP Type: 8 + +Length: n shall be 7 or 8 octets depending on the presence of MNC digit 3 + +IMSI MCC-MNC address value: Text type. + +This is the UTF-8 encoded characters representing the IMSI MCC-MNC numerical values. In accordance with 3GPP TS 29.060 [24] (for GGSN), 3GPP TS 29.274 [81] (for P-GW) and 3GPP TS 23.003 [40], the MCC shall be 3 digits and the MNC shall be either 2 or 3 digits. There shall be no padding characters between the MCC and MNC. + +## 9 – 3GPP-GGSN MCC-MNC + +| Octets | Bits | | | | | | | | +|--------|-------------------------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 9 | | | | | | | | +| 2 | 3GPP Length= n | | | | | | | | +| 3 | MCC digit1 (UTF-8 encoded character) | | | | | | | | +| 4 | MCC digit2 (UTF-8 encoded character) | | | | | | | | +| 5 | MCC digit3 (UTF-8 encoded character) | | | | | | | | +| 6 | MNC digit1 (UTF-8 encoded character) | | | | | | | | +| 7 | MNC digit2 (UTF-8 encoded character) | | | | | | | | +| 8 | MNC digit3 if present (UTF-8 encoded character) | | | | | | | | + +3GPP Type: 9 + +Length: n shall be 7 or 8 octets depending on the presence of MNC digit 3 + +GGSN address value: Text type. + +This is the UTF-8 encoding of the GGSN MCC-MNC values. In accordance with 3GPP TS 23.003 [40] and 3GPP TS 29.060 [24] the MCC shall be 3 digits and the MNC shall be either 2 or 3 digits. There shall be no padding characters between the MCC and MNC. + +### 10 – 3GPP-NSAPI + +| Octets | Bits | | | | | | | | +|--------|---------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 10 | | | | | | | | +| 2 | 3GPP Length= 3 | | | | | | | | +| 3 | NSAPI (UTF-8 encoded character) | | | | | | | | + +3GPP Type: 10 + +Length: 3 + +NSAPI value: Text Type. + +It is the value of the NSAPI of the PDP context the RADIUS message is related to. It is encoded as its hexadecimal representation, using one UTF-8 encoded character. The GGSN should receive NSAPI values in the following hexadecimal range 05 – 0F. The GGSN shall discard digit 0 and convert the remaining digit into one UTF-8 coded character. + +For P-GW, the value of this sub-attribute represents the EPS Bearer ID as specified in 3GPP TS 29.274 [81]. + +### 11 – 3GPP-Session Stop Indicator + +| Octets | Bits | | | | | | | | +|--------|------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 11 | | | | | | | | +| 2 | 3GPP Length= 3 | | | | | | | | +| 3 | 1 1 1 1 1 1 1 1 (bit string) | | | | | | | | + +3GPP Type: 11 + +Length: 3 + +Value is set to all 1. + +3GPP-Session Stop Indicator value: Bit String type. + +### 12 – 3GPP-Selection-Mode + +| Octets | Bits | | | | | | | | +|--------|----------------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 12 | | | | | | | | +| 2 | 3GPP Length= 3 | | | | | | | | +| 3 | UTF-8 encoded Selection mode character | | | | | | | | + +3GPP Type: 12 + +Length: 3 + +Selection mode value: Text type. + +The format of this sub-attribute shall be a character that represents a single digit, mapping from the binary value of the selection mode in the Create PDP Context message (3GPP TS 29.060 [24]) for the GGSN, and the Create Session Request message (3GPP TS 29.274 [81]) for the P-GW. Where 3GPP TS 29.060 [24] provides for interpretation of the value, e.g. map '3' to '2', this shall be done by the GGSN. + +### 13 – 3GPP-Charging-Characteristics + +| Octets | Bits | | | | | | | | +|--------|----------------------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 13 | | | | | | | | +| 2 | 3GPP Length= 6 | | | | | | | | +| 3-6 | UTF-8 encoded Charging Characteristics value | | | | | | | | + +3GPP Type: 13 + +Length: 6 + +Charging characteristics value: Text type. + +The charging characteristics is value of the 2 octets. The value field is taken from the GTP IE described in 3GPP TS 29.060 [24], subclause 7.7.23 for the GGSN and 3GPP TS 29.274 [81] for the P-GW. + +Each octet of this IE field value is represented via 2 UTF-8 encoded character, defining its hexadecimal representation. + +### 14 – 3GPP-Charging Gateway IPv6 address + +| Octets | Bits | | | | | | | | +|--------|----------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 14 | | | | | | | | +| 2 | 3GPP Length= 18 | | | | | | | | +| 3 | Charging GW IPv6 addr Octet 1 | | | | | | | | +| 4 | Charging GW IPv6 addr Octet 2 | | | | | | | | +| 5-18 | Charging GW IPv6 addr Octet 3-16 | | | | | | | | + +3GPP Type: 14 + +Length: 18 + +Charging GW IPv6 address value: IPv6 Address. + +Charging GW IPv6 address is Octet String type. + +### 15 – 3GPP-SGSN IPv6 address + +| Octets | Bits | | | | | | | | +|--------|---------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 15 | | | | | | | | +| 2 | 3GPP Length= 18 | | | | | | | | +| 3 | SGSN IPv6 addr Octet 1 | | | | | | | | +| 4 | SGSN IPv6 addr Octet 2 | | | | | | | | +| 5-18 | SGSN IPv6 addr Octet 3-16 | | | | | | | | + +3GPP Type: 15 + +Length: 18 + +SGSN IPv6 address value: IPv6 Address. + +SGSN IPv6 address is Octet String type. + +### 16 – 3GPP-GGSN IPv6 address + +| Octets | Bits | | | | | | | | +|--------|---------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 16 | | | | | | | | +| 2 | 3GPP Length= 18 | | | | | | | | +| 3 | GGSN IPv6 addr Octet 1 | | | | | | | | +| 4 | GGSN IPv6 addr Octet 2 | | | | | | | | +| 5-18 | GGSN IPv6 addr Octet 3-16 | | | | | | | | + +3GPP Type: 16 + +Length: 18 + +GGSN IPv6 address value: IPv6 Address. + +SGSN IPv6 address is Octet String type. + +### 17 – 3GPP-IPv6-DNS-Servers + +| Octets | Bits | | | | | | | | +|--------|---------------------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 17 | | | | | | | | +| 2 | 3GPP Length= m | | | | | | | | +| 3-18 | (1 st ) DNS IPv6 addr Octet 1-16 | | | | | | | | +| 19-34 | (2 nd ) DNS IPv6 addr Octet 1-16 | | | | | | | | +| k-m | (n-th) DNS IPv6 addr Octet 1-16 | | | | | | | | + +3GPP Type: 17 + +Length: $m = n \times 16 + 2$ ; $n \geq 1$ and $n \leq 15$ ; $k = m-15$ + +IPv6 DNS Server value: IPv6 Address. + +IPv6 DNS Server address is Octet String type. + +The 3GPP- IPv6-DNS-Servers sub-attribute provides a list of one or more ('n') IPv6 addresses of Domain Name Server (DNS) servers for an APN. The DNS servers are listed in the order of preference for use by a client resolver, i.e. the first is 'Primary DNS Server', the second is 'Secondary DNS Server' etc. The sub-attribute may be included in Access-Accept packets. + +### 18 – 3GPP-SGSN MCC-MNC + +| Octets | Bits | | | | | | | | +|--------|-------------------------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 18 | | | | | | | | +| 2 | 3GPP Length= n | | | | | | | | +| 3 | MCC digit1 (UTF-8 encoded character) | | | | | | | | +| 4 | MCC digit2 (UTF-8 encoded character) | | | | | | | | +| 5 | MCC digit3 (UTF-8 encoded character) | | | | | | | | +| 6 | MNC digit1 (UTF-8 encoded character) | | | | | | | | +| 7 | MNC digit2 (UTF-8 encoded character) | | | | | | | | +| 8 | MNC digit3 if present (UTF-8 encoded character) | | | | | | | | + +3GPP Type: 18 + +Length: n shall be 7 or 8 octets depending on the presence of MNC digit 3 + +SGSN MCC-MNC address value: Text type. + +This is the UTF-8 encoding of the MCC-MNC values extracted from the RAI or from the Serving Network. In accordance with 3GPP TS 23.003 [40] and 3GPP TS 29.060 [24] (for the GGSN and P-GW connected to a Gn/Gp SGSN) and 3GPP TS 29.274 [81] (for the P-GW in GTP/PMIP S5/S8, S2a, S2b), the MCC shall be 3 digits and the MNC shall be either 2 or 3 digits. There shall be no padding characters between the MCC and MNC. + +## 19 – 3GPP-Teardown Indicator + +| Octets | Bits | | | | | | | | +|--------|----------------|---|---|---|---|---|---|----| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 19 | | | | | | | | +| 2 | 3GPP Length= 3 | | | | | | | | +| 3 | spare | | | | | | | TI | + +3GPP Type: 19 + +Length: 3 + +Octet 3 is Octet String type. + +For GGSN, if the value of TI is set to "1", then all PDP contexts that share the same user session with the PDP context identified by the Acct-Session-Id shall be torn down. Only the PDP context identified by the Acct-Session-Id shall be torn down if the value of TI is "0" (see subclause 16.3.4 "AAA-Initiated PDP context termination"), or if TI is missing. + +For P-GW, the usage of Teardown-Indicator is as follows (see subclause 16.3a.3 for more details): + +- if the value of TI is set to "1", then all IP-CAN bearers that share the same user session with the IP-CAN bearer identified by the Acct-Session-Id shall be torn down. +- if the value of TI is "0", or if TI is missing, only the IP-CAN bearer identified by the Acct-Session-Id shall be torn down. If the Acct-Session-Id identifies the default bearer, the P-GW shall tear down all the IP-CAN bearers that share the same user session identified by the Acct-Session-Id. + +## 20 -3GGP- IMEISV + +| Bits | | | | | | | | | +|-----------|--------------------------------------------------|---|---|---|---|---|---|---| +| Octets | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP Type = 20 | | | | | | | | +| 2 | 3GPP Length = 2+n | | | | | | | | +| 3 – (2+n) | IMEI(SV) digits 1 – n (UTF-8 encoded characters) | | | | | | | | + +3GPP Type: 20 + +IMEISV value: Text type. + +A GGSN receives IMEI(SV) that is encoded according to 3GPP TS 29.060 [24]. A P-GW receives IMEI(SV) that is encoded in *ME Identity* IE specified in 3GPP TS 29.274 [81]. The GGSN or the P-GW converts IMEI(SV) into a sequence of UTF-8 characters. IMEI(SV) shall be encoded as defined in 3GPP TS 23.003 [40]. + +$14 \leq n \leq 16$ + +n = 16 for IMEISV, where TAC = 8 digits SNR = 6 digits & SVN = 2 digits; + +n = 15 for IMEI, where TAC = 8 digits SNR = 6 digits & Spare = 1 digit; + +n = 14 for IMEI, where TAC = 8 digits SNR = 6 digits (Spare digit is not sent) + +## 21 – 3GPP-RAT-Type + +| Octets | Bits | | | | | | | | +|--------|--------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 21 | | | | | | | | +| 2 | 3GPP Length= 3 | | | | | | | | +| 3 | RAT (octet string) | | | | | | | | + +3GPP Type: 21 + +The 3GPP-RAT-Type sub-attribute indicates which Radio Access Technology is currently serving the UE. + +RAT field: Radio Access Technology type values. RAT field is Octet String type. For GGSN, it shall be coded as specified in 3GPP TS 29.060 [24]. For P-GW, it shall be coded as follows: + +| | | +|---------|-------------------------------------| +| 0-9 | As specified in 3GPP TS 29.274 [81] | +| 10-50 | Spare for future use | +| 51 | NR | +| 52 | NR in unlicensed bands | +| 53 | Trusted WLAN | +| 54 | Trusted Non-3GPP access | +| 55 | Wireline access | +| 56 | Wireline Cable access | +| 57 | Wireline BBF access | +| 58 | NR RedCap | +| 59-100 | Spare for future use | +| 101 | IEEE 802.16e | +| 102 | 3GPP2 eHRPD | +| 103 | 3GPP2 HRPD | +| 104 | 3GPP2 1xRTT | +| 105 | 3GPP2 UMB | +| 106-255 | Spare for future use | + +The value 51-58 does not apply for the present specification. For specifications referencing the present RADIUS VSA, the value shall only apply if it is explicitly endorsed within the referencing specification. + +## 22 – 3GPP-User-Location-Info + +| Octets | Bits | | | | | | | | +|--------|------------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 22 | | | | | | | | +| 2 | 3GPP Length= m | | | | | | | | +| 3 | Geographic Location Type | | | | | | | | +| 4-m | Geographic Location (octet string) | | | | | | | | + +3GPP Type: 22 + +Length=m, where m depends on the Geographic Location Type + +For example, m= 10 in the CGI and SAI types. + +Geographic Location Type field is used to convey what type of location information is present in the ‘Geographic Location’ field. For GGSN, the Geographic Location Type values and coding are as defined in 3GPP TS 29.060 [24]. For P-GW, the Geographic Location Type values and coding are defined as follows: + +| | | +|-------|----------------------| +| 0 | CGI | +| 1 | SAI | +| 2 | RAI | +| 3-127 | Spare for future use | +| 128 | TAI | + +| | | +|---------|----------------------------| +| 129 | ECGI | +| 130 | TAI and ECGI | +| 131 | eNodeB ID | +| 132 | TAI and eNodeB ID | +| 133 | extended eNodeB ID | +| 134 | TAI and extended eNodeB ID | +| 135 | NCGI | +| 136 | 5GS TAI | +| 137 | 5GS TAI and NCGI | +| 138 | NG-RAN Node ID | +| 139 | 5GS TAI and NG-RAN Node ID | +| 140-255 | Spare for future use | + +Geographic Location field is used to convey the actual geographic information as indicated in the Geographic Location Type. For GGSN, the coding of this field is as specified in 3GPP TS 29.060 [24]. For P-GW, the coding of this field shall be as follows: + +- If the Geographic Location Type has a value indicating CGI, SAI, RAI, TAI or ECGI (i.e. the value field is equal to 0, 1, 2, 128, or 129), the coding of the Geographic Location field shall be as per clauses 8.21.1 to 8.21.5, respectively, in 3GPP TS 29.274 [81], +- If the Geographic Location Type has a value indicating TAI and ECGI (i.e. the value field is equal to 130), in Geographic Location field both TAI and ECGI shall be encoded one after another as per clauses 8.21.4 and 8.21.5 in 3GPP TS 29.274 [81]. TAI information shall be encoded first starting with Octet 4 of 3GPP-User-Location-Info. +- If the Geographic Location Type has a value indicating eNodeB ID (i.e. the value field is equal to 131), the coding of the Geographic Location field shall be as defined in subclause 8.21.7 in 3GPP TS 29.274 [81]. +- If the Geographic Location Type has a value indicating TAI and eNodeB ID (i.e. the value field is equal to 132), in Geographic Location field both TAI and eNodeB ID shall be encoded one after another as per subclauses 8.21.4 and 8.21.7 in 3GPP TS 29.274 [81]. +- If the Geographic Location Type has a value indicating extended eNodeB ID (i.e. the value field is equal to 133), the coding of the Geographic Location field shall be as defined in subclause 8.21.8 in 3GPP TS 29.274 [81]. +- If the Geographic Location Type has a value indicating TAI and extended eNodeB ID (i.e. the value field is equal to 134), in Geographic Location field both TAI and extended eNodeB ID shall be encoded one after another as per subclauses 8.21.4 and 8.21.8 in 3GPP TS 29.274 [81]. + +NOTE 1: The Geographic Location Type values "TAI and ECGI" is used only in 5GC-EPC interworking e.g in 3GPP TS 29.214 [121]. + +The Geographic Location Type values "NCGI", "5GS TAI", "5GS TAI and NCGI", "NG-RAN Node ID" and "5GS TAI and NG-RAN Node ID" are only introduced to extend the 3GPP-User-Location-Info AVP derived from the 3GPP Vendor-Specific RADIUS attributes and shall not apply for the present specification. For specifications referencing the present data type, those values shall only apply if they are explicitly endorsed within the referencing specification. For those values, the Geographic Location field shall be coded as follows: + +NOTE 2: The Geographic Location Type values "NCGI", "NG-RAN Node ID" and "5GS TAI and NG-RAN Node ID" are not used in 5G till current releases, while the value "5GS TAI and NCGI" is used only in 5GC e.g in 3GPP TS 29.214 [121]. + +- If the Geographic Location Type has a value indicating NCGI (i.e. the value field is equal to 135), the coding of the Geographic Location field shall be as per subclause 9.3.1.7 in 3GPP TS 38.413 [115]. Spare bits shall be placed just after the PLMN Identity and shall be set to zero. +- If the Geographic Location Type has a value indicating 5GS TAI (i.e. the value field is equal to 136), the coding of the Geographic Location field shall be as per subclause 9.3.3.11 in 3GPP TS 38.413 [115]. +- If the Geographic Location Type has a value indicating 5GS TAI and NCGI (i.e. the value field is equal to 137), in Geographic Location field both 5GS TAI and NCGI shall be encoded one after another as per subclause 9.3.3.11 in 3GPP TS 38.413 [115] and per subclause 9.3.1.7 in 3GPP TS 38.413 [115]. Spare bits for the NCGI shall be placed just after the PLMN Identity and shall be set to zero. + +- If the Geographic Location Type has a value indicating NG-RAN Node ID (i.e. the value field is equal to 138), the first octet of the Geographic Location field shall be length of the NG-RAN Node ID in unit of bit, and it also indicates the type of NG-RAN node as follows: + +1. length value = 18, short ng-eNodeB ID +2. length value = 20, ng-eNodeB ID +3. length value = 21, long ng-eNodeB ID +4. length value = 22-32, gNodeB ID + +Starting from the second octet of the Geographic Location field, the coding shall be as per subclause 9.3.1.5 in 3GPP TS 38.413 [115], i.e. first PLMN information then NG-RAN Node ID. Spare bits shall be set to zero. + +- If the Geographic Location Type has a value indicating 5GS TAI and NG-RAN Node ID (i.e. the value field is equal to 139), in Geographic Location field both 5GS TAI and NG-RAN Node ID shall be encoded one after another as per subclause 9.3.3.11 in 3GPP TS 38.413 [115] and as described for NG-RAN Node ID (i.e. the value field is equal to 138). Spare bits shall be set to zero. + +Geographic Location Type and Geographic Location fields are Octet String type. + +### 23 – 3GPP-MS-TimeZone + +| Octets | Bits | | | | | | | | +|--------|-------------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 23 | | | | | | | | +| 2 | 3GPP Length= 4 | | | | | | | | +| 3 | Time Zone | | | | | | | | +| 4 | Daylight Saving Time (octet string) | | | | | | | | + +3GPP Type: 23 + +Length=4 + +The Time Zone field and the Daylight Saving Time fields are used to indicate the offset between universal time and local time in steps of 15 minutes of where the MS/UE currently resides. + +For GGSN, both fields are coded as specified in 3GPP TS 29.060 [24] and represented as Octet String type. For, P-GW, both fields are coded as specified in 3GPP TS 29.274 [81] in UE-Time Zone IE and represented as Octet String type. + +### 24 – 3GPP-Camel-Charging-Info + +| Octets | Bits | | | | | | | | +|--------|-----------------------------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 24 | | | | | | | | +| 2 | 3GPP Length= m | | | | | | | | +| 3-m | CAMEL Charging Information Container (octet string) | | | | | | | | + +3GPP Type: 24 + +Length=m + +m depends on the size of the CAMELInformationPDP IE. + +The CAMEL Charging Information Container field is used to copy the CAMELInformationPDP IE including Tag and Length from the SGSN's CDR (S-CDR). + +The coding of this field is as specified in 3GPP TS 29.060 [24] and represented as Octet String type. + +## 25 – 3GPP-Packet-Filter + +| Octets | Bits | | | | | | | | +|--------|----------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 25 | | | | | | | | +| 2 | 3GPP Length= n | | | | | | | | +| 3-z | Packet Filter | | | | | | | | + +3GPP Type: 25 + +Length: n + +Each 3GPP-Packet-Filter sub-attribute contains only one packet filter. Multiple 3GPP-Packet-Filter sub-attributes can be sent in one RADIUS Accounting Request message. + +When the GGSN/P-GW sends the packet filter information, the RADIUS message shall carry ALL (or none) of the packet filters. + +Packet Filter Value: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------|---|---|---|---|---|---|---|---------| +| Packet filter identifier | | | | | | | | Octet 1 | +| Packet filter evaluation precedence | | | | | | | | Octet 2 | +| Length of Packet filter contents | | | | | | | | Octet 3 | +| Direction of Packet Filter | | | | | | | | Octet 4 | +| Packet filter contents | | | | | | | | Octet 5 | +| | | | | | | | | Octet m | + +Direction Value: + +00000000: Downlink + +00000001: Uplink + +00000010: Bidirectional + +The packet filter content is represented as Octet String type. The packet filter content is defined below: + +| Type | Value | +|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1: IPv4 address type |

Contains the source address if the direction value is set to Downlink, and the destination address if the direction value is set to Uplink.

Shall be encoded as a sequence of a four octet IPv4 address field and a four octet IPv4 address mask field. The IPv4 address field shall be transmitted first

| +| 2: IPv6 address type |

Contains the source address if the direction value is set to Downlink, and the destination address if the direction value is set to Uplink.

Shall be encoded as a sequence of a sixteen octet IPv6 address field and a sixteen octet IPv6 address mask field. The IPv6 address field shall be transmitted first

| +| 3: Protocol identifier/Next header type | shall be encoded as one octet which specifies the IPv4 protocol identifier or IPv6 next header | + +| | | +|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4 : Single destination port type | shall be encoded as two octet which specifies a port number | +| 5 : Destination port range type | shall be encoded as a sequence of a two octet port range low limit field and a two octet port range high limit field. The port range low limit field shall be transmitted first | +| 6 : Single source port type | shall be encoded as two octet which specifies a port number | +| 7 : Source port range type | shall be encoded as a sequence of a two octet port range low limit field and a two octet port range high limit field. The port range low limit field shall be transmitted first | +| 8: Security parameter index type (IPv6) | shall be encoded as four octet which specifies the IPSec security parameter index | +| 9: Type of service/Traffic class type | shall be encoded as a sequence of a one octet Type-of-Service/Traffic Class field and a one octet Type-of-Service/Traffic Class mask field. The Type-of-Service/Traffic Class field shall be transmitted first | +| 10: Flow label type (IPv6) | shall be encoded as three octets which specify the IPv6 flow label. The bits 8 through 5 of the first octet shall be spare whereas the remaining 20 bits shall contain the IPv6 flow label | + +NOTE 3: The sending of this sub-attribute is not recommended for an inter-operator interface for security reason. + +## 26 – 3GPP-Negotiated-DSCP + +| Octets | Bits | | | | | | | | +|--------|--------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 26 | | | | | | | | +| 2 | 3GPP Length= 3 | | | | | | | | +| 3 | Negotiated DSCP (octet string) | | | | | | | | + +3GPP Type: 26 + +Length: 3 + +Negotiated DSCP value: Octet String + +DSCP value: Octet String type. + +## 27 – 3GPP-Allocate-IP-Type + +| Octets | Bits | | | | | | | | +|--------|------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 27 | | | | | | | | +| 2 | 3GPP Length= 3 | | | | | | | | +| 3 | IP Type (octet string) | | | | | | | | + +3GPP Type: 27 + +If multiple Access-Request signalling towards a AAA server is needed during the lifetime of a PDN connection (e.g. for PDN/PDP type IPv4v6 and deferred IPv4 addressing), this sub-attribute shall be included in the Access-Request message to indicate how the AAA server needs to treat the request. The P-GW/GGSN may also use this sub-attribute if the AAA server is configured to allocate both IPv4 address and IPv6 prefix but the P-GW/GGSN requires assignment of only one IP type or both IP types (e.g. because the UE supports single IP stack and it has requested PDN/PDP type of IPv4 or IPv6). + +If this sub-attribute does not exist in Access-Request from P-GW/GGSN to the AAA server, the IP address allocation shall be based on the IP address allocation policy configured in the the AAA server. + +IP Type field: It is encoded in Octet String type and the following decimal equivalent values apply: + +- 0 Do not allocate IPv4 address or IPv6 prefix. +The typical use case is for PDN/PDP type IPv4v6 and deferred IPv4 addressing and only IPv4 address is allocated by the AAA server but IPv6 prefix is allocated by some other means, e.g. local pool in the P-GW/GGSN. The Access-Request from the P-GW/GGSN to the AAA server during the UE's initial access to the network shall set the value of this sub-attribute to 0. +- 1 Allocate IPv4 address +The typical use case is for PDN/PDP type IPv4v6 and deferred IPv4 addressing and the IPv4 address (and/or IPv6 prefix) is allocated by the AAA server. The Access-Request from the P-GW/GGSN to the AAA server when the P-GW/GGSN receives UE-initiated IPv4 address allocation signalling (e.g. DHCPv4) after UE's successful initial access to the PDN shall set the value of this attribute to 1. In this case, if the AAA server had allocated an IPv6 prefix earlier during UE's initial access to the network, same IPv6 prefix shall be kept allocated. +- 2 Allocate IPv6 prefix +The typical use case is for PDN/PDP type IPv4v6 and deferred IPv4 addressing and both IPv4 address and IPv6 prefix are allocated by the AAA server. The Access-Request from the P-GW/GGSN to the AAA server during the UE's initial access to the network shall set the value of this sub-attribute to 2. +- 3 Allocate IPv4 address and IPv6 prefix +Currently there is no use case identified to use this specific value for PDN/PDP type IPv4v6 and deferred IPv4 addressing. One potential use case is for PDN/PDP type IPv4v6 and non-deferred IPv4 addressing and both IPv4 address and IPv6 prefix are allocated by the AAA server. The Access-Request from the P-GW/GGSN to the AAA server may use this value to have both IPv4 address and IPv6 prefix assigned to the UE. + +4-255 Reserved for future use + +## 28 – External-Identifier + +| Octets | Bits | | | | | | | | +|--------|------------------------------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 28 | | | | | | | | +| 2 | 3GPP Length= m | | | | | | | | +| 3-m | Identifier characters 1-n (UTF-8 encoded characters) | | | | | | | | + +3GPP Type: 28 + +n ≤ 72 / 253 (n ≤ 72 octets shall be supported, n ≤ 253 octets recommended, refer to 3GPP TS 29.336 [101] and IETF RFC 4282 [102]) + +Length: m ≤ 74 / 255 (m ≤ 74 octets shall be supported, m ≤ 255 octets recommended, refer to 3GPP TS 29.336 [101] and IETF RFC 4282 [102]) + +External-Identifier value: Text type. + +A globally unique identifier of a UE used towards external server instead of IMSI and MSISDN, refer to 3GPP TS 23.682 [100] and 3GPP TS 23.003 [40]. + +## 29 – TWAN-Identifier + +| Octets | Bits | | | | | | | | +|--------|--------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 29 | | | | | | | | +| 2 | 3GPP Length= m | | | | | | | | +| 3-m | TWAN Identifier (octet string) | | | | | | | | + +3GPP Type: 29 + +Length=m, where m depends on the type of location that is present as described in 3GPP TS 29.274 [81]. + +TWAN Identifier field is used to convey the location information in a Trusted WLAN Access Network (TWAN). The coding of this field shall be the same as for the GTP TWAN Identifier starting with Octet 5, as per clause 8.100 in 3GPP TS 29.274 [81]. + +TWAN Identifier field is Octet String type. + +### 30 – 3GPP-User-Location-Info-Time + +| Octets | Bits | | | | | | | | +|--------|-------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 30 | | | | | | | | +| 2 | 3GPP Length= 6 | | | | | | | | +| 3-6 | User Location Info time | | | | | | | | + +3GPP Type: 30 + +Length=6 + +User Location Info time field is Unsigned32 type, it indicates the NTP time at which the UE was last known to be in the location which is reported during bearer deactivation or UE detach procedure. + +### 31 – 3GPP-Secondary-RAT-Usage + +| Octets | Bits | | | | | | | | | | | +|--------|---------------------|---|---|------|-----|---|---|---|--|--|--| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +| 1 | 3GPP type = 31 | | | | | | | | | | | +| 2 | 3GPP Length= 28 | | | | | | | | | | | +| 3 | spare | | | SESS | RAT | | | | | | | +| 4-7 | RAN Start timestamp | | | | | | | | | | | +| 8-11 | RAN End timestamp | | | | | | | | | | | +| 12-19 | Usage Data DL | | | | | | | | | | | +| 20-28 | Usage Data UL | | | | | | | | | | | + +3GPP Type: 31 + +Length=28 + +Multiple 3GPP-Secondary-RAT-Usage sub-attributes can be sent in one RADIUS Accounting Request Interim-Update/STOP message. + +Octet 3 is Octet String type. The encoding of RAT field (bit 1 to bit 4) is: + +- 0 – NR +- 1 – NR-U +- 2 – EUTRA +- 3 – EUTRA-U + +4 – Unlicensed Spectrum + +5-15 – spare, reserved for future use + +SESS (bit 5): If it is set to 1, it indicates the secondary RAT usage of the PDU session. + +The values 1, 2 and 3 of RAT field and SESS field do not apply for the present specification. For specifications referencing the present RADIUS VSA, they shall only apply if it is explicitly endorsed within the referencing specification. Bit 6 to bit 8 of octet 3 is spare and reserved for future use. + +The encoding of octets 4 to 28 is specified in Secondary RAT Usage Data Report IE of 3GPP TS 29.274 [81]. + +### 32 – 3GPP-UE-Local-IP-Address + +| Octets | Bits | | | | | | | | +|--------|------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 32 | | | | | | | | +| 2 | 3GPP Length= 7 or 19 | | | | | | | | +| 3 | IP Type (octet string) | | | | | | | | +| 4-m | UE local IP address | | | | | | | | + +3GPP Type: 32 + +Length=7 or 19 + +IP Type field: It is encoded in Octet String type and the following decimal equivalent values apply: + +| | | +|---|-----------------------| +| 1 | UE local IPv4 address | +| 2 | UE local IPv6 address | + +UE local IP address field: It is encoded in Octet String type, with 4 octets when the IP Type is UE local IPv4 address, or with 16 octets when the IP Type is UE local IPv6 address. + +### 33 – 3GPP-UE-Source-Port + +| Octets | Bits | | | | | | | | +|--------|---------------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | 3GPP type = 33 | | | | | | | | +| 2 | 3GPP Length= 5 | | | | | | | | +| 3 | Source Port Type (octet string) | | | | | | | | +| 4-5 | Port Number (octet string) | | | | | | | | + +3GPP Type: 33 + +Length=5 + +Source Port Type field: It is encoded in Octet String type and the following decimal equivalent values apply: + +| | | +|---|-----------------| +| 1 | UDP Source Port | +| 2 | TCP Source Port | + +Port Number field: It is encoded in Octet String type, with bit 8 of Octet 4 represents the most significant bit of the port number and bit 1 of Octet 5 represents the least significant bit. + +## 16.4.8 Accounting Request Interim-Update (sent from GGSN/P-GW to AAA server) + +Table 8 describes the attributes of the Accounting-Request Interim-Update message. + +**Table 8: The attributes of the Accounting-Request Interim-Update message** + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|--------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|---------------------------| +| 1 | User-Name | Username is provided to the GGSN/P-GW by the user in the PCO or for the case of the P-GW when multiple authentications are supported in the APCO received during IP-CAN session establishment procedure. If PPP PDN type is used, it is provided to the GGSN by the user during PPP authentication phase. If no username is available, a generic username, configurable on a per APN basis, shall be present. If the User-Name has been received in the Access-Accept message, this username shall be used in preference to the above. | String | Optional | +| 4 | NAS-IP-Address | IPv4 address of the GGSN/P-GW for communication with the AAA server. | IPv4 | Conditional Notes 1 and 7 | +| 95 | NAS-IPv6-Address | IPv6 address of the GGSN/P-GW for communication with the AAA server. | IPv6 | Conditional Notes 1 and 7 | +| 32 | NAS-Identifier | Hostname of the GGSN/P-GW for communication with the AAA server. | String | Conditional Note 1 | +| 6 | Service-Type | Indicates the type of service for this user | Framed | Optional | +| 7 | Framed Protocol | Indicates the type of protocol for this user | 7 (GPRS PDP Context) | Optional Note 8 | +| 8 | Framed-IP-Address | User IPv4 address | IPv4 | Conditional Note 3 | +| 97 | Framed-IPv6-Prefix | User IPv6 prefix | IPv6 | Conditional Note 3 | +| 123 | Delegated-IPv6-Prefix | Delegated IPv6 prefix to the user | IPv6 | Conditional Note 9 | +| 96 | Framed-Interface-Id | User IPv6 Interface Identifier | IPv6 | Conditional Notes 3 and 4 | +| 25 | Class | Received in the Access-Accept | String | Optional (Note 2) | +| 30 | Called-Station-Id | Identifier for the target network | APN (UTF-8 encoded) | Mandatory | +| 31 | Calling-Station-Id | This attribute is the identifier for the MS, and it shall be configurable on a per APN basis. | MSISDN in international format according to 3GPP TS 23.003 [40], UTF-8 encoded characters. (Note 6) | Optional | +| 40 | Acct-Status-Type | Indicates the type of accounting request | Interim-Update | Mandatory | +| 41 | Acct-Delay-Time | Indicates how many seconds the GGSN/P-GW has been trying to send this record for, and can be subtracted from the time of arrival on the AAA server to find the approximate time of the event generating this Accounting-Request | Second | Optional | +| 42 | Acct-Input-Octets | GGSN/P-GW counted number of octets sent by the user for the IP-CAN bearer | 32 bit unsigned integer | Optional | +| 43 | Acct-Output-Octets | GGSN/P-GW counted number of octets received by the user for the IP-CAN bearer | 32 bit unsigned integer | Optional | +| 44 | Acct-Session-Id | User session identifier. | GGSN/P-GW IP address (IPv4 or IPv6) and Charging-ID concatenated in a UTF-8 encoded hexadecimal characters. (Note 5) | Mandatory | + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|----------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|------------------------------------------------------| +| 45 | Acct-Authentic | Authentication method | RADIUS or LOCAL | Optional | +| 46 | Acct-Session-Time | Duration of the session | Second | Optional | +| 47 | Acct-Input-Packets | GGSN/P-GW counted number of packets sent by the user | Packet | Optional (Note 10) | +| 48 | Acct-Output-Packets | GGSN/P-GW counted number of packets received by the user | Packet | Optional (Note 10) | +| 52 | Acct-Input-Gigawords | It indicates how many times the Acct-Input-Octets counter has wrapped around $2^{32}$ and is present if the Acct-Input-Octets counter has wrapped around $2^{32}$ . | 32 bit unsigned integer
See IETF RFC 2869 [116] | Conditional | +| 53 | Acct-Output-Gigawords | It indicates how many times the Acct-Output-Octets counter has wrapped around $2^{32}$ and is present if the Acct-Output-Octets counter has wrapped around $2^{32}$ . | 32 bit unsigned integer
See IETF RFC 2869 [116] | Conditional | +| 61 | NAS-Port-Type | Port type for the GGSN/P-GW | As per RFC 2865 [38] | Optional | +| 26/10415 | 3GPP Vendor-Specific | Sub-attributes according to subclause 16.4.7. | See subclause 16.4.7 | Optional except sub-attribute 3 which is conditional | + +NOTE 1: Either NAS-IP-Address or NAS-Identifier shall be present. +NOTE 2: The presence of this attribute is conditional upon this attribute being received in the Access-Accept message +NOTE 3: If the 3GPP-PDP-Type is IPv4, IPv6, or IPv4v6, IPv4 and/or IPv6 address/prefix attributes shall be present. The IP protocol version for end-user and network may be different. +NOTE 4: Included if the prefix alone is not unique for the user. This may be the case, for example, if a static IPv6 address is assigned. +NOTE 5: The GGSN/P-GW IP address is the same one that is used in the CDRs generated by the GGSN/P-GW. +NOTE 6: There are no leading characters in front of the country code. +NOTE 7: Either IPv4 or IPv6 address attribute shall be present. +NOTE 8: Framed-Protocol value of 7 is used by both GGSN and P-GW when interworking with RADIUS AAA servers. When used for P-GW, it represents the IP-CAN bearer. +NOTE 9: Delegated IPv6 prefix shall be present if IPv6 prefix delegation is required from the external DN-AAA server. +NOTE 10: If the P-GW is split into a user plane node and control plane node according to 3GPP TS 29.244 [114], the user plane function "MNOP" need to be supported. + +### 16.4.9 Disconnect Request (optionally sent from AAA server to GGSN/P-GW) + +Table 9 describes the attributes of the Disconnect-Request message. + +**Table 9: The attributes of the Disconnect-Request message** + +| Attr # | Attribute Name | Description | Content | Presence Requirement | +|--------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------------------| +| 1 | User-Name | Username provided by the user (extracted from the PCO/APCO field received during PDN connection establishment) or PPP authentication phase (if PPP PDP type is used). If no username is available a generic username, configurable on a per APN basis, shall be present. If the User-Name has been sent in the Access-Accept message, this user-name shall be used in preference to the above | String | Optional | +| 8 | Framed-IP-Address | User IPv4 address | IPv4 | Conditional
Note 2 | + +| | | | | | +|----------|----------------------|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------|---------------------------| +| 97 | Framed-IPv6-Prefix | User IPv6 prefix | IPv6 | Conditional Note 2 | +| 96 | Framed-Interface-Id | User IPv6 Interface Identifier | IPv6 | Conditional Notes 1 and 2 | +| 44 | Acct-Session-Id | User session identifier. | GGSN/P-GW IP address (IPv4 or IPv6) and Charging-ID concatenated in a UTF-8 encoded hexadecimal characters. (Note 3) | Mandatory | +| 26/10415 | 3GPP Vendor-Specific | Sub-attributes according to subclause 16.4.7. | See subclause 16.4.7 | Optional | + +NOTE 1: Included if the prefix alone is not unique for the user. This may be the case, for example, if a static IPv6 address is assigned. + +NOTE 2: If the 3GPP-PDP-Type is IPv4, IPv6, or IPv4v6, either IPv4 or IPv6 address/prefix attribute shall be present. See subclause 16.3.4. + +NOTE 3: The GGSN/P-GW IP address is the same one that is used in the CDRs created by the GGSN/P-GW. + +## 16a Usage of Diameter on Gi/Sgi interface + +As an operator option, it is also possible to use the Diameter protocol in order to provide Authentication, Authorization and Accounting services. + +A GGSN/P-GW may, on a per APN basis, use Diameter authentication to authenticate a user and Diameter accounting to provide information to a Diameter server. + +### 16a.1 Diameter Authentication and Authorization + +Diameter Authentication and Authorization shall be used according to RFC 7155 [120]. + +The GGSN/P-GW and the Diameter server shall advertise the support of the Diameter NASREQ Application by including the value of the appropriate application identifier in the Capability-Exchange-Request and Capability-Exchange-Answer commands as specified in IETF RFC 6733 [111]. + +The Diameter client function may reside in a GGSN/P-GW. When the GGSN/P-GW receives an initial attach (e.g. Create PDP Context) request message the Diameter client function may send the authentication information to an authentication server, which is identified during the APN provisioning. + +The authentication server checks that the user can be accepted. The response (when positive) may contain network information, such as an IPv4 address and/or IPv6 prefix for the user when the GGSN/P-GW is interworking with the AAA server. + +The information delivered during the Diameter authentication can be used to automatically correlate the users identity (the MSISDN or IMSI) to the IPv4 address and/or IPv6 prefix, if applicable, assigned/confirmed by the GGSN/P-GW or the authentication server respectively. The same procedure applies, in case of sending the authentication to a 'proxy' authentication server. + +Diameter Authentication is applicable to the initial access (e.g. primary PDP context or the default bearer). When the GGSN/P-GW receives a positive response from the authentication server it shall complete the initial access (e.g. PDP context activation) procedure. If a failure or no response is received, the GGSN/P-GW shall reject the initial access (e.g. PDP Context Activation) attempt with a suitable cause code, e.g. User Authentication failed. + +The GGSN may also use the Diameter re-authorization procedure for the purpose of IPv4 address allocation to the UE for PDP type of IPv4v6 after establishment of a PDN connection. + +For EPS, the P-GW may also use the Diameter re-authorization procedure for the purpose of IPv4 address allocation to the UE for PDN type of IPv4v6 after establishment of a PDN connection. The use cases that may lead this procedure are: + +- Deferred IPv4 address allocation via DHCPv4 procedure after successful attach on 3GPP accesses. +- Deferred IPv4 address allocation after successful attach in trusted non-3GPP IP access on S2a. +- Deferred IPv4 home address allocation via DSMIPv6 Re-Registration procedure via S2c. + +## 16a.2 Diameter Accounting + +Diameter Accounting shall be used according to RFC 7155 [120]. + +The Diameter accounting client function may reside in a GGSN/P-GW. The Diameter accounting client may send information to an accounting server, which is identified during the APN provisioning. The accounting server may store this information and use it to automatically identify the user. This information can be trusted because the PS access network has authenticated the subscriber (i.e. SIM card and possibly other authentication methods). + +Diameter Accounting messages may be used during both primary and secondary PDP context activation for non-EPC based packet domain (both the default bearer and dedicated bearer for the EPC based packet domain) and deactivation procedures respectively. + +If the AAA server is used for IPv4 address and/or IPv6 prefix assignment, then, upon reception of a Diameter Accounting-Request STOP message for all IP-CAN bearers associated to an IP-CAN session defined by APN and IMSI or MSISDN, the AAA server may make the associated IPv4 address and/or IPv6 prefix available for assignment. + +For PDN/PDP type IPv4v6 and deferred IPv4 address allocation, when the IPv4 address is allocated or re-allocated, the accounting session that was established for the IPv6 prefix allocation shall be used to inform the accounting server about the allocated IPv4 address by sending Diameter Accounting-Request Interim-Update with Framed-IP-Address AVP and its value field containing the allocated IPv4 address. Similarly, the release of IPv4 address shall be indicated to the accounting server by sending Diameter Accounting-Request Interim-Update without the Framed-IP-Address AVP. + +## 16a.3 Authentication and accounting message flows on Gi interface + +### 16a.3.1 IP PDP type + +Figure 25a represents the Diameter message flows between a GGSN and a Diameter server. + +![Sequence diagram showing Diameter message flows for IP PDP type activation and deactivation between MT, SGSN, GGSN, Diameter Server, and PDN.](29997432244f81212ee1e6c94f308f1b_img.jpg) + +``` + +sequenceDiagram + participant MT + participant SGSN + participant GGSN + participant DiameterServer as Diameter Server + participant PDN + + Note right of DiameterServer: (Note 2) + + MT->>SGSN: PDP Context Activate Request + SGSN->>GGSN: Create PDP Context Request + GGSN-->>DiameterServer: AA-Request + Note right of DiameterServer: (Note 3) + DiameterServer-->>GGSN: AA-Answer + GGSN->>DiameterServer: Accounting-Request (start) + Note right of DiameterServer: (Note 4) + DiameterServer-->>GGSN: Accounting-Answer (start) + GGSN->>SGSN: Create PDP Context Response + Note left of GGSN: (Note 1) + SGSN->>MT: Activate PDP Context Accept + Note right of GGSN: User Data + MT->>SGSN: Deactivate PDP Context Request + SGSN->>GGSN: Delete PDP Context Request + GGSN->>DiameterServer: Accounting-Request (stop) + DiameterServer-->>GGSN: Accounting-Answer (stop) + GGSN->>SGSN: Delete PDP Context Response + SGSN->>MT: Deactivate PDP Context Accept + +``` + +The diagram illustrates the sequence of messages for IP PDP type activation and deactivation. + **Activation:** The MT sends a 'PDP Context Activate Request' to the SGSN. The SGSN sends a 'Create PDP Context Request' to the GGSN. The GGSN sends an 'AA-Request' to the Diameter Server (Note 3). The Diameter Server responds with an 'AA-Answer'. The GGSN then sends an 'Accounting-Request (start)' (Note 4) to the Diameter Server, which responds with an 'Accounting-Answer (start)'. The GGSN sends a 'Create PDP Context Response' to the SGSN (Note 1), which in turn sends an 'Activate PDP Context Accept' to the MT. User data flow begins between the GGSN and PDN. + **Deactivation:** The MT sends a 'Deactivate PDP Context Request' to the SGSN. The SGSN sends a 'Delete PDP Context Request' to the GGSN. The GGSN sends an 'Accounting-Request (stop)' to the Diameter Server, which responds with an 'Accounting-Answer (stop)'. The GGSN sends a 'Delete PDP Context Response' to the SGSN, which in turn sends a 'Deactivate PDP Context Accept' to the MT. + +Sequence diagram showing Diameter message flows for IP PDP type activation and deactivation between MT, SGSN, GGSN, Diameter Server, and PDN. + +NOTE 1: If some external applications require Diameter Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Answer (START) is received from the Diameter server. The GGSN may wait for the Accounting Answer (START) before sending the CreatePDPContextResponse. The GGSN may reject the PDP context if the Accounting Answer (START) is not received. + +NOTE 2: Separate accounting and authentication servers may be used. + +NOTE 3: The AA-Request message shall be used for primary PDP context only. + +NOTE 4: The Accounting-Request (Start) message may be sent at a later stage, e.g. after IPv4 address has been assigned and PDP Context updated, in case of IP address allocation via DHCPv4 after successful PDP context activation signalling. + +**Figure 25a: Diameter message flow for PDP type IP (successful user authentication case)** + +When a GGSN receives a Create PDP Context Request message for a given APN, the GGSN may (depending on the configuration for this APN) send a Diameter AA-Request to a Diameter server. The Diameter server authenticates and authorizes the user. If Diameter is also responsible for IPv4 address and/or IPv6 prefix allocation the Diameter server + +shall return the allocated IPv4 address and/or IPv6 prefix in the AA-Answer message. The AA-Request and AA-Answer messages are only used for the primary PDP context. + +When PDP type is IPv4v6 and deferred IPv4 addressing via IPv4 address pool in the AAA server is used, the GGSN may initiate Diameter re-authorization procedures after successful initial attach for the purpose of IPv4 address allocation or to renew the lease for a previously allocated IPv4 address. In this case, the GGSN shall set the Session-Id to the value used in the initial access request, the Auth-Request-Type AVP to "AUTHORIZE\_ONLY" and the 3GPP-Allocate-IP-Type AVP to the type of IP address to be allocated in the AA-Request message sent to the AAA server. See subclause 16.4.7.2 for the conditions to use 3GPP-Allocate-IP-Type AVP in AA-Request messages. If the GGSN is using DHCPv4 signalling towards the MS and the Diameter server includes the Session-Timeout attribute in the Access-Accept, the GGSN may use the Session-Timeout value as the DHCP lease time. The GGSN shall not set the DHCPv4 lease time value higher than the Session-Timeout value. The GGSN may renew the DHCP lease to the MS without re-authorization towards the AAA server providing that the new lease expiry is no later than the Session-Timeout timer expiry. If the GGSN wishes to extend the lease time beyond the current Session-Timeout expiry, it shall initiate a new AAA re-authorization. + +Even if the GGSN was not involved in user authentication (e.g. transparent network access mode), it may send a Diameter Accounting-Request (START) message to a Diameter server. If no Diameter session is already open for the user a Diameter session needs to be activated, otherwise the existing Diameter session is used to send the Accounting-Request (START). The NSAPI will identify the particular PDP context this accounting refers to. The Accounting-Request message also indicates to the Diameter server that the user session has started. This message contains parameters, e.g. the tuple which includes the user-id, IPv4 address and/or IPv6 prefix, and the MSISDN to be used by application servers (e.g. WAP gateway) in order to identify the user. + +If some external applications require Diameter Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Answer (START) is received from the Diameter server. The GGSN may wait for the Accounting Answer (START) before sending the CreatePDPContextResponse. The GGSN may reject the PDP context if the Accounting Answer (START) is not received. The authentication and accounting servers may be separately configured for each APN. + +For PDP type IPv4, at IPv4 address allocation via DHCPv4 signalling between the TE and the PDN, no IPv4 address is available at PDP context activation. In that case the GGSN may wait to send the Accounting-Request (START) message until the TE receives its IP address in a DHCPACK. + +For PDP type IPv4v6 and deferred IPv4 addressing, when the IPv4 address is allocated or re-allocated, the accounting session that was established for the IPv6 prefix allocation shall be used to inform the accounting server about the allocated IPv4 address by sending Diameter Accounting-Request Interim-Update with the Framed-IP-Address AVP and its value field containing the allocated IPv4 address. + +When the GGSN receives a Delete PDP Context Request message and providing a Diameter Accounting-Request (START) message was sent previously, the GGSN shall send a Diameter Accounting-Request (STOP) message to the Diameter server, which indicates the termination of this particular user accounting session. The NSAPI will identify the particular PDP context this accounting refers to. The GGSN shall immediately send a Delete PDP context response, without waiting for an Accounting-Answer (STOP) message from the Diameter server. + +If this was the last PDP context for that PDP address, the GGSN shall additionally send an STR message to the Diameter server. The Diameter server shall reply with an STA and shall deallocate the IP address or IPv6 prefix (if any) initially allocated to the subscriber. + +For PDP type IPv4v6 and deferred IPv4 addressing, when the GGSN receives a message from the MS or the network indicating the release of the IPv4 address (e.g. receiving DHCPRELEASE) or decides to release the IPv4 address on its own (e.g. due to DHCP lease timer expiry for GGSN assigned IPv4 address), the GGSN shall inform the accounting server about the deallocation of the IPv4 address by sending Diameter Accounting-Request Interim-Update without the Framed-IP-Address AVP. + +### 16a.3.2 PPP PDP type + +Figure 25b describes the Diameter message flows between a GGSN and a Diameter server for the case where PPP is terminated at the GGSN. The case where PPP is relayed to an LNS is beyond the scope of the present document. + +![Sequence diagram showing Diameter message flow for PDP type PPP. Lifelines: TE, MT, SGSN, GGSN, Diameter Server, PDN. The sequence includes PDP Context Activate Request, Create PDP Context Request/Response, Activate PDP Context Accept, LCP Negotiation, Challenge, Authentication Request, AA-Request/Answer, Authentication Response, NCP Negotiation, Accounting-Request/Answer (start), User Data Session, LCP Termination, Delete PDP Context Request/Response, Deactivate PDP Context Request/Response, and Accounting-Request/Answer (stop).](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +**Diameter message flow for PDP type PPP (successful user authentication case)** + +``` + +sequenceDiagram + participant TE + participant MT + participant SGSN + participant GGSN + participant DiameterServer as Diameter Server + participant PDN + + Note right of DiameterServer: (Note 1) + + MT->>SGSN: PDP Context Activate Request + SGSN->>GGSN: Create PDP Context Request + GGSN->>SGSN: Create PDP Context Response + SGSN->>MT: Activate PDP Context Accept + MT->>GGSN: LCP Negotiation + GGSN-->>MT: Challenge + MT->>GGSN: Authentication Request + GGSN->>DiameterServer: AA-Request + Note left of GGSN: (Note 2) + DiameterServer-->>GGSN: AA-Answer + Note right of DiameterServer: (Note 5) + GGSN->>MT: Authentication Response + MT->>GGSN: NCP Negotiation + GGSN->>DiameterServer: Accounting-Request (start) + DiameterServer-->>GGSN: Accounting-Answer (start) + Note left of GGSN: (Note 3) + Note right of GGSN: User Data Session + MT->>GGSN: LCP Termination + Note left of GGSN: (Note 4) + GGSN->>DiameterServer: Accounting-Request (stop) + Note right of DiameterServer: (Note 6) + DiameterServer-->>GGSN: Accounting-Answer (stop) + GGSN-->>MT: Delete PDP Context Request + MT->>GGSN: Deactivate PDP Context Request + GGSN->>DiameterServer: Accounting-Request (stop) + Note right of DiameterServer: (Note 7) + DiameterServer-->>GGSN: Accounting-Answer (stop) + GGSN-->>MT: Delete PDP Context Response + MT->>GGSN: Deactivate PDP Context Accept + +``` + +Sequence diagram showing Diameter message flow for PDP type PPP. Lifelines: TE, MT, SGSN, GGSN, Diameter Server, PDN. The sequence includes PDP Context Activate Request, Create PDP Context Request/Response, Activate PDP Context Accept, LCP Negotiation, Challenge, Authentication Request, AA-Request/Answer, Authentication Response, NCP Negotiation, Accounting-Request/Answer (start), User Data Session, LCP Termination, Delete PDP Context Request/Response, Deactivate PDP Context Request/Response, and Accounting-Request/Answer (stop). + +NOTE 1: Separate accounting and Authentication servers may be used. + +NOTE 2: Actual messages depend on the used authentication protocol (e.g. PAP, CHAP). + +NOTE 3: If some external applications require Diameter Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Answer (START) is received from the AAA server. The GGSN may delete the PDP context if the Accounting Response (START) is not received. + +NOTE 4: An LCP termination procedure may be performed. Either the MS or the GGSN may initiate the context deactivation. + +NOTE 5: The AA-Request message shall be used for primary PDP context only. + +NOTE 6: Network Initiated deactivation. + +NOTE 7: User Initiated deactivation. + +**Figure 25b: Diameter message flow for PDP type PPP (successful user authentication case)** + +When a GGSN receives a Create PDP Context Request message for a given APN, the GGSN shall immediately send a Create PDP context response back to the SGSN. After PPP link setup, the authentication phase may take place. During Authentication phase, the GGSN sends a Diameter AA-Request to a Diameter server. The Diameter server authenticates and authorizes the user. If Diameter is also responsible for IP address allocation the Diameter server shall return the allocated IP address or IPv6 prefix in the AA-answer message (if the user was authenticated). + +If the user is not authenticated, the GGSN shall send a Delete PDP context request to the SGSN. The AA-Request and AA-Answer messages are only used for the primary PDP context. + +Even if the GGSN was not involved in user authentication (e.g. for PPP no authentication may be selected), it may send a Diameter Accounting-Request (START) message to a Diameter server. If no Diameter session is already open for the user a Diameter session needs to be activated, otherwise the existing Diameter session is used to send the Accounting-Request (START). The NSAPI will identify the particular PDP context this accounting refers to. The Accounting-Request message also indicates to the Diameter server that the user session has started, and the QoS parameters associated to the session. This message contains parameters, e.g. a tuple which includes the user-id, IP address or IPv6 prefix, and the MSISDN to be used by application servers (e.g. WAP gateway) in order to identify the user. + +If some external applications require Diameter Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Answer (START) is received from the Diameter server. The GGSN may delete the PDP context if the Accounting Answer (START) is not received. The Authentication and Accounting servers may be separately configured for each APN. + +When the GGSN receives a Delete PDP Context Request message and providing a Diameter Accounting-Request (START) message was sent previously, the GGSN shall send a Diameter Accounting-Request (STOP) message to the Diameter server, which indicates the termination of this particular user session. The NSAPI will identify the particular PDP context this accounting refers to. The GGSN shall immediately send a Delete PDP context response, without waiting for an Accounting-Answer (STOP) message from the Diameter server. + +If this was the last PDP context for that PDP address, the GGSN shall additionally send an STR message to the Diameter server. The Diameter server shall reply with an STA and shall deallocate the IP address or IPv6 prefix (if any) initially allocated to the subscriber. + +### 16a.3.3 Accounting Update + +During the life of a PDP context some information related to this PDP context may change (i.e. SGSN address if an Inter-SGSN RA update occurs). Upon reception of an UpdatePDPContextRequest from the SGSN, the GGSN may send an Accounting Request (Interim) to the Diameter server to update the necessary information related to this PDP context (see figure 25c). Interim updates are also used when the IPv4 address is allocated/released/re-allocated for deferred IPv4 addressing for the PDP type IPv4v6. + +If the GGSN receives an UpdatePDPContextRequest from the SGSN that specifically indicates a direct tunnel establishment or a direct tunnel teardown (switching the user plane tunnel end back to the SGSN), and only the GTP user plane address or the GTP-U TEID have changed, then the GGSN should not send the Accounting Request (Interim) message to the Diameter server. In such cases, the GGSN need not wait for the Diameter Accounting Answer from the Diameter server message before sending the UpdatePDPContextResponse to the SGSN. The GGSN may delete the PDP context if the Accounting Answer is not received from the Diameter server. + +![Sequence diagram for Diameter for PDP context Update. The diagram shows three entities: SGSN, GGSN, and Diameter Server. The sequence of messages is: 1. SGSN sends UpdatePDPContextReq to GGSN. 2. GGSN sends AccountingReq (Interim) to Diameter Server. 3. GGSN sends UpdatePDPContextRes to SGSN. 4. Diameter Server sends AccountingAns to GGSN. A note indicates that the GGSN does not wait for the AccountingAns before sending the UpdatePDPContextRes.](d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg) + +``` + +sequenceDiagram + participant SGSN + participant GGSN + participant DiameterServer as Diameter Server + Note right of GGSN: (Note) + SGSN->>GGSN: UpdatePDPContextReq + GGSN->>DiameterServer: AccountingReq (Interim) + GGSN->>SGSN: UpdatePDPContextRes + DiameterServer->>GGSN: AccountingAns + +``` + +Sequence diagram for Diameter for PDP context Update. The diagram shows three entities: SGSN, GGSN, and Diameter Server. The sequence of messages is: 1. SGSN sends UpdatePDPContextReq to GGSN. 2. GGSN sends AccountingReq (Interim) to Diameter Server. 3. GGSN sends UpdatePDPContextRes to SGSN. 4. Diameter Server sends AccountingAns to GGSN. A note indicates that the GGSN does not wait for the AccountingAns before sending the UpdatePDPContextRes. + +NOTE: As shown the GGSN need not wait for the Diameter Accounting Answer message from the Diameter server to send the UpdatePDPContextResponse to the SGSN. The GGSN may delete the PDP context if the Accounting Answer is not received from the Diameter server. + +Figure 25c: Diameter for PDP context Update + +### 16a.3.4 Server-Initiated PDP context termination + +Diameter is used as the protocol between the GGSN and a Diameter server or proxy for applications (e.g. MMS) to deliver information related to GPRS user session. However some IP applications could need to interwork with the GGSN to terminate a particular PDP context. For this purpose, the Diameter server or proxy may send a Diameter ASR to the GGSN along with the NSAPI necessary to identify the particular PDP context to be terminated. As depicted in figure 25d, the GGSN should react by deleting the corresponding PDP context. If the GGSN deletes the corresponding PDP context, it need not wait for the DeletePDPContextResponse from the SGSN before sending the ASA to the server. + +The absence of the NSAPI in the Diameter ASR message indicates to the GGSN that all PDP contexts for this particular user and sharing the same user session shall be deleted. The PDP contexts belonging to the same IP-CAN session are identified by the Diameter Session-Id. If a user has the same user IP address for different sets of PDP contexts towards different networks, only the PDP contexts linked to the one identified by the Diameter Session-Id shall be deleted. + +![Sequence diagram showing PDP Context deletion with Diameter. The diagram involves three entities: SGSN, GGSN, and Diameter Server. The sequence of messages is: 1. GGSN sends an ASR (Account-Stop-Request) to the Diameter Server. 2. Diameter Server sends a DeletePDPContextReq to the GGSN. 3. GGSN sends a DeletePDPContextRes to the SGSN. 4. GGSN sends an ASA (Account-Start-Request) to the Diameter Server, with a note indicating this happens without waiting for the response from the SGSN.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +``` + +sequenceDiagram + participant SGSN + participant GGSN + participant Diameter Server + Note right of GGSN: (Note) + GGSN->>Diameter Server: ASR + Diameter Server->>GGSN: DeletePDPContextReq + GGSN->>SGSN: DeletePDPContextRes + GGSN->>Diameter Server: ASA + +``` + +Sequence diagram showing PDP Context deletion with Diameter. The diagram involves three entities: SGSN, GGSN, and Diameter Server. The sequence of messages is: 1. GGSN sends an ASR (Account-Stop-Request) to the Diameter Server. 2. Diameter Server sends a DeletePDPContextReq to the GGSN. 3. GGSN sends a DeletePDPContextRes to the SGSN. 4. GGSN sends an ASA (Account-Start-Request) to the Diameter Server, with a note indicating this happens without waiting for the response from the SGSN. + +NOTE: As showed on figure 25d, the GGSN need not wait for the DeletePDPContextResponse from the SGSN to send the ASA to the Diameter server. + +Figure 25d: PDP Context deletion with Diameter + +## 16a.3a Authentication and accounting message flows on Sgi interface + +### 16a.3a.1 Authentication, Authorization and Accounting procedures + +When a P-GW receives an initial access request (e.g. Create Session Request or Proxy Binding Update) message for a given APN, the P-GW may (depending on the configuration for this APN) send a Diameter AA-Request to a Diameter server. The Diameter server authenticates and authorizes the user. If the Diameter server is also responsible for IPv4 address and/or IPv6 prefix allocation the Diameter server shall return the allocated IPv4 address and/or IPv6 prefix in the AA-Answer message. + +When PDN type is IPv4v6 and deferred IPv4 addressing via IPv4 address pool in the AAA server is used, the P-GW may initiate Diameter re-authorization procedures after successful initial attach for the purpose of IPv4 address allocation or to renew the lease for a previously allocated IPv4 address. In this case, the P-GW shall set the Session-Id to the value used in the initial access request, the Auth-Request-Type AVP to "AUTHORIZE\_ONLY" and the 3GPP-Allocate-IP-Type AVP to the type of IP address to be allocated in the AA-Request message sent to the AAA server. See subclause 16.4.7.2 for the conditions to use 3GPP-Allocate-IP-Type AVP in AA-Request messages. If the P-GW is using DHCPv4 signalling towards the UE and the Diameter server includes the Session-Timeout attribute in the Access-Accept, the P-GW may use the Session-Timeout value as the DHCP lease time. The P-GW shall not set the DHCPv4 lease time value higher than the Session-Timeout value. The P-GW may renew the DHCP lease to the UE without re-authorization towards the AAA server providing that the new lease expiry is no later than the Session-Timeout timer expiry. If the P-GW wishes to extend the lease time beyond the current Session-Timeout expiry, it shall initiate a new AAA re-authorization. + +Even if the P-GW was not involved in user authentication, it may send a Diameter Accounting-Request (START) message to a Diameter server. If no Diameter session is already open for the same PDN connection a Diameter session needs to be activated, otherwise the existing Diameter session is used to send the Accounting-Request (START). For GTP-based S5/S8/S2a/S2b, if accounting is used per IP-CAN bearer, the EPS bearer ID will identify the particular bearer this accounting message refers to. The Accounting-Request message also indicates to the Diameter server that the user session has started. This message contains parameters, e.g. the tuple which includes the user-id and IPv4 address and/or IPv6 prefix, to be used by application servers (e.g. WAP gateway) in order to identify the user. This message also indicates to the Diameter server that the user session has started. + +If some external applications require Diameter Accounting Request (START) information before they can process user packets, then the selected APN (P-GW) may be configured in such a way that the P-GW drops user data until an Accounting-Answer (START) indicating success is received from the Diameter server. The P-GW may wait for the Accounting-Answer (START) before sending the initial access response (e.g. Create Session Response or Proxy + +Binding Acknowledgement). The P-GW may reject the initial access request if the Accounting-Answer (START) is not received. The authentication and accounting servers may be separately configured for each APN. + +For PDN type IPv4, at IPv4 address allocation via DHCPv4 signalling between the UE and the PDN, no IPv4 address is available at initial access. In that case the P-GW may wait to send the Accounting-Request START message until the UE receives its IPv4 address in a DHCPACK. + +For PDN type IPv4v6 and deferred IPv4 addressing, when the IPv4 address is allocated or re-allocated, the accounting session that was established for the IPv6 prefix allocation shall be used to inform the accounting server about the allocated IPv4 address by sending Diameter Accounting-Request Interim-Update with the Framed-IP-Address AVP and its value field containing the allocated IPv4 address. + +When the P-GW receives a message indicating a bearer deactivation request or PDN disconnection request or detach request (e.g. Delete Bearer Command or Proxy Binding Update with lifetime equal 0) and providing a Diameter Accounting-Request START message was sent previously, the P-GW shall send a Diameter Accounting-Request (STOP) message to the Diameter server, which indicates the termination of this particular bearer or user session. The P-GW shall immediately send the corresponding response (e.g. Delete Bearer Request or Proxy Binding Ack with lifetime equal 0) to the peer node (e.g. S-GW) in the Packet Domain, without waiting for an Accounting-Answer (STOP) message from the Diameter server. + +If the last bearer of an IP-CAN session is deactivated, the P-GW shall additionally send an STR message to the Diameter server. The Diameter server shall reply with an STA and shall deallocate the IPv4 address and/or IPv6 prefix (if any) initially allocated to the subscriber. + +For PDN type IPv4v6 and deferred IPv4 addressing, when the P-GW receives a message from the UE or the network indicating the release of the IPv4 address (e.g. receiving DHCPRELEASE) or decides to release the IPv4 address on its own (e.g. due to DHCP lease timer expiry for P-GW assigned IPv4 address), the P-GW shall inform the accounting server about the deallocation of the IPv4 address by sending Diameter Accounting-Request Interim-Update without the Framed-IP-Address AVP. + +The following Figure 25d.1 is an example message flow to show the procedure of Diameter Authentication and Accounting, which is applicable for GTP based S5/S8: + +![Sequence diagram showing Diameter Authentication and Accounting on Sgi for GTP-based S5/S8. Lifelines: S-GW, P-GW, Diameter Server (note 2), and PDN. The diagram illustrates the message flow for session creation and deletion, including authentication (AA-Request/Answer) and accounting (Accounting-Request/Answer) messages.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +``` + +sequenceDiagram + participant S-GW + participant P-GW + participant DS as Diameter Server (note 2) + participant PDN + + Note left of S-GW: (note 1) + + S-GW->>P-GW: Create Session Request + P-GW-->>DS: AA-Request + DS-->>P-GW: AA-Answer + P-GW->>DS: Accounting-Request (start) + P-GW->>S-GW: Create Session Response + DS-->>P-GW: Accounting- Answer (start) + P-GW->>PDN: User data + S-GW->>P-GW: Delete Session Request + P-GW->>DS: Accounting-Request (stop) + P-GW->>S-GW: Delete Session Response + DS-->>P-GW: Accounting- Answer (stop) + +``` + +Sequence diagram showing Diameter Authentication and Accounting on Sgi for GTP-based S5/S8. Lifelines: S-GW, P-GW, Diameter Server (note 2), and PDN. The diagram illustrates the message flow for session creation and deletion, including authentication (AA-Request/Answer) and accounting (Accounting-Request/Answer) messages. + +NOTE 1: If some external applications require Diameter Accounting request (Start) information before they can process user packets, then the selected APN (P-GW) may be configured in such a way that the P-GW drops user data until the Accounting Answer (START) is received from the Diameter server. The P-GW may wait for the Accounting Answer (START) before sending the Create Session Response. The P-GW may reject the bearer if the Accounting Answer (START) is not received. + +NOTE 2: Separate accounting and authentication servers may be used. + +**Figure 25d.1: An example of Diameter Authentication and Accounting on Sgi for GTP-based S5/S8** + +### 16a.3a.2 Accounting Update + +During the life of a bearer some information related to this bearer may change. Upon occurrence of the following events the P-GW may send an Accounting Request (Interim) to the Diameter server: RAT change, S-GW address change and QoS change. Interim updates are also used when the IPv4 address is allocated/released/re-allocated for deferred IPv4 addressing for the PDN type IPv4v6. + +When the P-GW receives a signalling request (e.g. Modify Bearer Request in case of GTP-based S5/S8) that indicates the occurrence of one of these chargeable events, the P-GW may send an Accounting Request (Interim) to the Diameter server to update the necessary information related to this bearer. The P-GW need not wait for the Diameter Accounting Answer message from the Diameter server before sending the response for the triggering signalling message (e.g. Modify Bearer Response). The P-GW may delete the bearer if the Accounting Answer is not received from the Diameter server. + +The P-GW may also send interim updates at the expiry of an operator configured time limit. + +The message flow in figure 25d.2 provides an example for Diameter Accounting Update procedure on Sgi interface, which is applicable for GTP based S5/S8: + +![Sequence diagram for Diameter accounting update for bearer modification. The diagram shows three entities: S-GW, P-GW, and Diameter Server. The S-GW sends a 'Modify Bearer Req' to the P-GW. The P-GW then sends an 'AccountingReq (Interim)' to the Diameter Server. The Diameter Server responds with 'AccountingAns' to the P-GW, which in turn sends a 'Modify Bearer Res' back to the S-GW.](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +``` + +sequenceDiagram + participant S-GW + participant P-GW + participant Diameter Server + S-GW->>P-GW: Modify Bearer Req + P-GW->>Diameter Server: AccountingReq (Interim) + Diameter Server-->>P-GW: AccountingAns + P-GW-->>S-GW: Modify Bearer Res + +``` + +Sequence diagram for Diameter accounting update for bearer modification. The diagram shows three entities: S-GW, P-GW, and Diameter Server. The S-GW sends a 'Modify Bearer Req' to the P-GW. The P-GW then sends an 'AccountingReq (Interim)' to the Diameter Server. The Diameter Server responds with 'AccountingAns' to the P-GW, which in turn sends a 'Modify Bearer Res' back to the S-GW. + +Figure 25d.2: Diameter accounting update for bearer modification + +### 16a.3a.3 Server-Initiated Bearer termination + +Diameter is used as the protocol between the P-GW and a Diameter server or proxy for applications (e.g. MMS) to deliver information related to the user session. However some IP applications could need to interwork with the P-GW to release the corresponding resource (e.g. terminate a particular bearer or Resource Allocation Deactivation procedures as defined in TS 23.402 [78]). For this purpose, the Diameter server or proxy may send a Diameter ASR along with the EPS bearer ID, if available, to identify the particular bearer to be terminated to the P-GW. The P-GW should react by deleting the corresponding bearer. If the P-GW deletes the corresponding bearer, it need not wait for the response from the S-GW or trusted non-3GPP IP access or ePDG before sending the ASA to the server. + +The absence of the EPS bearer ID in the Diameter ASR message indicates to the P-GW that all bearers/resources for this particular user and sharing the same user session shall be deleted. The bearer(s)/resources belonging to the same IP-CAN session are identified by the Diameter Session-Id. If a user has the same user IP address(es) for different sets of bearers towards different networks, only the bearers linked to the one identified by the Diameter Session-Id shall be deleted. + +The message flow in figure 25d.3 provides an example for Server-initiated Bearer Termination procedure on Sgi interface, which is applicable for GTP based S5/S8: + +![Sequence diagram for Server-initiated Bearer Termination with Diameter. The diagram shows three entities: S-GW, P-GW, and Diameter Server. The Diameter Server sends a 'Diameter ASR' to the P-GW. The P-GW then sends a 'Delete Bearer Request' to the S-GW. The S-GW responds with a 'Delete Bearer Response' to the P-GW, which in turn sends a 'Diameter ASA' back to the Diameter Server.](f0e3f79f8b55cbaba4a467e762854eae_img.jpg) + +``` + +sequenceDiagram + participant S-GW + participant P-GW + participant Diameter Server + Diameter Server->>P-GW: Diameter ASR + P-GW->>S-GW: Delete Bearer Request + S-GW-->>P-GW: Delete Bearer Response + P-GW-->>Diameter Server: Diameter ASA + +``` + +Sequence diagram for Server-initiated Bearer Termination with Diameter. The diagram shows three entities: S-GW, P-GW, and Diameter Server. The Diameter Server sends a 'Diameter ASR' to the P-GW. The P-GW then sends a 'Delete Bearer Request' to the S-GW. The S-GW responds with a 'Delete Bearer Response' to the P-GW, which in turn sends a 'Diameter ASA' back to the Diameter Server. + +Figure 25d.3: Server-initiated Bearer Termination with Diameter + +## 16a.4 Gi/Sgi Diameter messages + +This clause describes the Gi and the Sgi interface Diameter messages. + +The relevant AVPs that are of use for the Gi/Sgi interface are detailed in this clause. Other Diameter NASREQ (IETF RFC 7155 [120]) AVPs, even if their AVP flag rules is marked with "M", are not required for being compliant with the current specification. + +### 16a.4.1 AAR Command + +The AAR command, defined in Diameter NASREQ (IETF RFC 7155 [120]), is indicated by the Command-Code field set to 265 and the 'R' bit set in the Command Flags field. It may be sent by the GGSN to a Diameter server, during Primary PDP Context activation only, in order to request user authentication and authorization. In the case of P-GW, the AAR may be sent upon reception of an initial access request (e.g. Create Session Request or Proxy Binding Update) message for a given APN to request user authentication and authorization. + +The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. + +The bold marked AVPs in the message format indicate optional AVPs for Gi/Sgi, or modified existing AVPs. For Sgi, some of the optional 3GPP vendor-specific AVPs listed in the message format below are not applicable. See table 9a in subclause 16a.5 to see the list of vendor-specific AVPs that are applicable to the GGSN and the P-GW. + +Message Format: + +``` + ::= < Diameter Header: 265, REQ, PXY > + < Session-Id > + { Auth-Application-Id } + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Request-Type } + [ Destination-Host ] + [ NAS-Port ] + [ NAS-Port-Id ] + [ NAS-Port-Type ] + [ Origin-State-Id ] + [ Port-Limit ] + [ User-Name ] + [ User-Password ] + [ Service-Type ] + [ Authorization-Lifetime ] + [ Auth-Grace-Period ] + [ Auth-Session-State ] + [ Callback-Number ] + [ Called-Station-Id ] + [ Calling-Station-Id ] + [ Originating-Line-Info ] + [ Connect-Info ] + [ CHAP-Auth ] + [ CHAP-Challenge ] + * [ Framed-Compression ] + [ Framed-Interface-Id ] + [ Framed-IP-Address ] + * [ Framed-IPv6-Prefix ] + * [ Delegated-IPv6-Prefix ] + [ Framed-IP-Netmask ] + [ Framed-MTU ] + [ Framed-Protocol ] + * [ Login-IP-Host ] + * [ Login-IPv6-Host ] + [ Login-LAT-Group ] + [ Login-LAT-Node ] + [ Login-LAT-Port ] + [ Login-LAT-Service ] + * [ Tunneling ] + * [ Proxy-Info ] + * [ Route-Record ] + [ 3GPP-IMSI ] + [ External-Identifier ] + [ 3GPP-Charging-ID ] +``` + +``` + +[ 3GPP-PDP-Type ] +[ 3GPP-CG-Address ] +[ 3GPP-GPRS-Negotiated-QoS-Profile ] +[ 3GPP-SGSN-Address ] +[ 3GPP-GGSN-Address ] +[ 3GPP-IMSI-MCC-MNC ] +[ 3GPP-GGSN-MCC-MNC ] +[ 3GPP-NSAPI ] +[ 3GPP-Selection-Mode ] +[ 3GPP-Charging-Characteristics ] +[ 3GPP-CG-IPv6-Address ] +[ 3GPP-SGSN-IPv6-Address ] +[ 3GPP-GGSN-IPv6-Address ] +[ 3GPP-SGSN-MCC-MNC ] +[ 3GPP-User-Location-Info ] +[ 3GPP-RAT-Type ] +[ 3GPP-CAMEL-Charging-Info ] +[ 3GPP-Negotiated-DSCP ] +[ 3GPP-Allocate-IP-Type ] +[ TWAN-Identifier ] +[ 3GPP-UE-Local-IP-Address ] +[ 3GPP-UE-Source-Port ] +* [ AVP ] + +``` + +## 16a.4.2 AAA Command + +The AAA command, defined in Diameter NASREQ (IETF RFC 7155 [120]), is indicated by the Command-Code field set to 265 and the 'R' bit cleared in the Command Flags field., It is sent by the Diameter server to the GGSN/P-GW in response to the AAR command. + +The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. + +The "Tunneling" AVP may include the "Tunnel-Type" with value 3 to represent L2TP tunnel type, "Tunnel-Medium-Type" and "Tunnel-Server-Endpoint" AVPs. If more than one set of these "Tunneling" AVPs are provided, the optional "Tunnel-Preference" AVP may be provided in each set to identify the relative preference. The Tunnel-Password AVP may be used to authenticate to a remote server. + +NOTE: The other optional AVPs within the "Tunneling" AVPs not listed in the above description, can be referred to the IETF RFC 7155 [120] with implementation specific. + +The bold marked AVPs in the message format indicate optional AVPs for Gi/Sgi, or modified existing AVPs. + +Message Format: + +``` + + ::= < Diameter Header: 265, PXY > + < Session-Id > + { Auth-Application-Id } + { Auth-Request-Type } + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + [ Service-Type ] + * [ Class ] + [ Acct-Interim-Interval ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ Failed-AVP ] + [ Idle-Timeout ] + [ Authorization-Lifetime ] + [ Auth-Grace-Period ] + [ Auth-Session-State ] + [ Re-Auth-Request-Type ] + [ Multi-Round-Time-Out ] + [ Session-Timeout ] + * [ Reply-Message ] + [ Origin-State-Id ] + * [ Filter-Id ] + [ Port-Limit ] + [ Prompt ] + [ Callback-Id ] + [ Callback-Number ] + +``` + +``` + +* [ Framed-Compression ] +[ Framed-Interface-Id ] +[ Framed-IP-Address ] +* [ Framed-IPv6-Prefix ] +[ Framed-IPv6-Pool ] +* [ Framed-IPv6-Route ] +* [ Delegated-IPv6-Prefix ] +[ Framed-IP-Netmask ] +* [ Framed-Route ] +[ Framed-Pool ] +[ Framed-IPX-Network ] +[ Framed-MTU ] +[ Framed-Protocol ] +[ Framed-Routing ] +* [ Login-IP-Host ] +* [ Login-IPv6-Host ] +[ Login-LAT-Group ] +[ Login-LAT-Node ] +[ Login-LAT-Port ] +[ Login-LAT-Service ] +[ Login-Service ] +[ Login-TCP-Port ] +* [ NAS-Filter-Rule ] +* [ QoS-Filter-Rule ] +* [ Tunneling ] +* [ Redirect-Host ] +[ Redirect-Host-Usage ] +[ Redirect-Max-Cache-Time ] +* [ Proxy-Info ] +[ 3GPP-IPv6-DNS-Servers ] +* [ External-Identifier ] +* [ AVP ] + +``` + +### 16a.4.3 ACR Command + +The ACR command, defined in IETF RFC 6733 (Diameter Base) [111], is indicated by the Command-Code field set to 271 and the 'R' bit set in the Command Flags field. It is sent by the GGSN/P-GW to the Diameter server to report accounting information for a certain IP-CAN bearer (e.g. PDP context) or an IP-CAN session of a certain user. + +The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. + +The bold marked AVPs in the message format indicate optional AVPs for Gi/Sgi, or modified existing AVPs. For Sgi, some of the optional 3GPP vendor-specific AVPs listed in the message format below are not applicable. See table 9a in subclause 16a.5 to see the ones that are applicable. + +#### Message Format: + +``` + + ::= < Diameter Header: 271, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Accounting-Record-Type } + { Accounting-Record-Number } + [ Acct-Application-Id ] + [ User-Name ] + [ Origin-State-Id ] + [ Destination-Host ] + [ Event-Timestamp ] + [ Acct-Delay-Time ] + [ NAS-Identifier ] + [ NAS-IP-Address ] + [ NAS-IPv6-Address ] + [ NAS-Port ] + [ NAS-Port-Id ] + [ NAS-Port-Type ] + * [ Class ] + [ Service-Type ] + [ Accounting-Input-Octets ] + [ Accounting-Input-Packets ] + [ Accounting-Output-Octets ] + [ Accounting-Output-Packets ] + [ Acct-Authentic ] + +``` + +``` +[ Accounting-Auth-Method ] +[ Acct-Session-Time ] +[ Acct-Tunnel-Connection ] +[ Acct-Tunnel-Packets-Lost ] +[ Callback-Id ] +[ Callback-Number ] +[ Called-Station-Id ] +[ Calling-Station-Id ] +* [ Connection-Info ] +[ Originating-Line-Info ] +[ Authorization-Lifetime ] +[ Session-Timeout ] +[ Idle-Timeout ] +[ Port-Limit ] +[ Accounting-Realtime-Required ] +[ Acct-Interim-Interval ] +* [ Filter-Id ] +* [ NAS-Filter-Rule ] +* [ Qos-Filter-Rule ] +[ Framed-Compression ] +[ Framed-Interface-Id ] +[ Framed-IP-Address ] +[ Framed-IP-Netmask ] +* [ Framed-IPv6-Prefix ] +[ Framed-IPv6-Pool ] +* [ Framed-IPv6-Route ] +* [ Delegated-IPv6-Prefix ] +[ Framed-IPX-Network ] +[ Framed-MTU ] +[ Framed-Pool ] +[ Framed-Protocol ] +* [ Framed-Route ] +[ Framed-Routing ] +* [ Login-IP-Host ] +* [ Login-IPv6-Host ] +[ Login-LAT-Group ] +[ Login-LAT-Node ] +[ Login-LAT-Port ] +[ Login-LAT-Service ] +[ Login-Service ] +[ Login-TCP-Port ] +* [ Tunneling ] +* [ Proxy-Info ] +* [ Route-Record ] +[ 3GPP-IMSI ] +[ External-Identifier ] +[ 3GPP-Charging-ID ] +[ 3GPP-PDP-Type ] +[ 3GPP-CG-Address ] +[ 3GPP-GPRS-Negotiated-QoS-Profile ] +[ 3GPP-SGSN-Address ] +[ 3GPP-GGSN-Address ] +[ 3GPP-IMSI-MCC-MNC ] +[ 3GPP-GGSN-MCC-MNC ] +[ 3GPP-NSAPI ] +[ 3GPP-Selection-Mode ] +[ 3GPP-Charging-Characteristics ] +[ 3GPP-CG-IPv6-Address ] +[ 3GPP-SGSN-IPv6-Address ] +[ 3GPP-GGSN-IPv6-Address ] +[ 3GPP-SGSN-MCC-MNC ] +[ 3GPP-IMEISV ] +[ 3GPP-RAT-Type ] +[ 3GPP-User-Location-Info ] +[ 3GPP-MS-Time-Zone ] +[ 3GPP-CAMEL-Charging-Info ] +[ 3GPP-Packet-Filter ] +[ 3GPP-Negotiated-DSCP ] +[ TWAN-Identifier ] +[ 3GPP-User-Location-Info-Time ] +* [ 3GPP-Secondary-RAT-Usage ] +[ 3GPP-UE-Local-IP-Address ] +[ 3GPP-UE-Source-Port ] +* [ AVP ] +``` + +### 16a.4.4 ACA Command + +The ACA command, defined in Diameter Base (IETF RFC 6733 [111]), is indicated by the Command-Code field set to 271 and the 'R' bit cleared in the Command Flags field. It is sent by the Diameter server to the GGSN/P-GW in response to the ACR command. + +The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. + +Message Format: + +``` + ::= < Diameter Header: 271, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + { Accounting-Record-Type } + { Accounting-Record-Number } + [ Acct-Application-Id ] + [ User-Name ] + [ Event-Timestamp ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ Failed-AVP ] + [ Origin-State-Id ] + [ NAS-Identifier ] + [ NAS-IP-Address ] + [ NAS-IPv6-Address ] + [ NAS-Port ] + [ NAS-Port-Id ] + [ NAS-Port-Type ] + [ Service-Type ] + [ Accounting-Realtime-Required ] + [ Acct-Interim-Interval ] + * [ Class ] + * [ Proxy-Info ] + * [ Route-Record ] + * [ AVP ] +``` + +### 16a.4.5 STR Command + +The STR command, defined in IETF RFC 6733 (Diameter Base) [111], is indicated by the Command-Code field set to 275 and the 'R' bit set in the Command Flags field. It is sent by the GGSN/P-GW to the Diameter server to terminate a DIAMETER session corresponding to an IP-CAN session of a certain user. + +The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. + +Message Format: + +``` + ::= < Diameter Header: 275, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Application-Id } + { Termination-Cause } + [ User-Name ] + [ Destination-Host ] + * [ Class ] + [ Origin-State-Id ] + * [ Proxy-Info ] + * [ Route-Record ] + * [ AVP ] +``` + +### 16a.4.6 STA Command + +The STA command, defined in IETF RFC 6733 (Diameter Base) [111], is indicated by the Command-Code field set to 275 and the 'R' bit cleared in the Command Flags field. It is sent by the Diameter server to the GGSN/P-GW in response to an STR command. + +The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. + +Message Format: + +``` + ::= < Diameter Header: 275, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ User-Name ] + * [ Class ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ Failed-AVP ] + [ Origin-State-Id ] + * [ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + * [ Proxy-Info ] + * [ AVP ] +``` + +#### 16a.4.7 ASR Command + +The Abort-Session-Request (ASR) command, defined in IETF RFC 6733 (Diameter Base) [111], is indicated by the Command-Code set to 274 and the message flags' 'R' bit set, is sent by the Diameter server to the GGSN to request that the PDP Context identified by the 3GPP-NSAPI AVP is to be terminated. The absence of the 3GPP-NSAPI AVP will indicate to the GGSN that all the PDP contexts for this particular user and sharing the same user session need to be deleted. Similarly, for P-GW, the ASR command is sent by the Diameter server to the P-GW to request that the EPS bearer identified by the 3GPP-NSAPI AVP is to be terminated. In the absence of the 3GPP-NSAPI AVP or if the value of 3GPP-NSAPI AVP points to the default EPS bearer, the P-GW shall terminate the IP-CAN session associated with the same user session. + +The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. + +The bold marked AVPs in the message format indicate optional AVPs for Gi/Sgi, or modified existing AVPs. + +Message Format: + +``` + ::= < Diameter Header: 274, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Destination-Host } + { Auth-Application-Id } + [ Origin-State-Id ] + * [ Proxy-Info ] + * [ 3GPP-NSAPI ] + * [ Route-Record ] + * [ AVP ] +``` + +#### 16a.4.8 ASA Command + +The Abort-Session-Answer (ASA) command, defined in IETF RFC 6733 (Diameter Base) [111], is indicated by the Command-Code set to 274 and the message flags' 'R' bit clear, is sent in response to the ASR. + +The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. + +The bold marked AVPs in the message format indicate optional AVPs for Gi/Sgi or modified existing AVPs. + +Message Format: + +``` + ::= < Diameter Header: 274, PXY > + < Session-Id > + { Result-Code } +``` + +``` +{ Origin-Host } +{ Origin-Realm } +[ User-Name ] +[ Origin-State-Id ] +[ Experimental-Result ] +[ Error-Message ] +[ Error-Reporting-Host ] +[ Failed-AVP ] +* [ Redirected-Host ] +[ Redirected-Host-Usage ] +[ Redirect-Max-Cache-Time ] +* [ Proxy-Info ] +* [ AVP ] +``` + +The Experimental-Result AVP contains an Experimental-Result-Code AVP and will signal to the Diameter server that the IP-CAN bearer (e.g. PDP context) has been successfully terminated as requested. See subclause 16a.6 for the description of the Experimental-Result-Code AVP. + +## 16a.5 Gi/Sgi specific AVPs + +The following table lists the Gi/Sgi specific Diameter AVPs. The Vendor-Id header of all Gi/Sgi specific AVPs defined in the present specification shall be set to 3GPP (10415). + +**Table 9a: Gi/Sgi specific AVPs** + +| AVP Flag rules | +|-----------------------| +|-----------------------| + +| Attribute Name | AVP Code | Section defined | Value Type | Must | May | Should not | Must not | May Encr. | Applicable Reference Points | +|----------------------------------|----------|----------------------|-------------|------|-----|------------|----------|-----------|-----------------------------| +| 3GPP-IMSI | 1 | 16.4.7
(see Note) | UTF8String | V | P | | M | Y | Gi, Sgi | +| 3GPP-Charging-Id | 2 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-PDP-Type | 3 | 16.4.7
(see Note) | Enumerated | V | P | | M | Y | Gi, Sgi | +| 3GPP-CG-Address | 4 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-GPRS-Negotiated-QoS-Profile | 5 | 16.4.7
(see Note) | UTF8String | V | P | | M | Y | Gi, Sgi | +| 3GPP-SGSN-Address | 6 | 16.4.7
(see note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-GGSN-Address | 7 | 16.4.7
(see note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-IMSI-MCC-MNC | 8 | 16.4.7
(see note) | UTF8String | V | P | | M | Y | Gi, Sgi | +| 3GPP-GGSN-MCC-MNC | 9 | 16.4.7
(see note) | UTF8String | V | P | | M | Y | Gi, Sgi | +| 3GPP-NSAPI | 10 | 16.4.7
(see note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-Selection-Mode | 12 | 16.4.7
(see note) | UTF8String | V | P | | M | Y | Gi, Sgi | +| 3GPP-Charging-Characteristics | 13 | 16.4.7
(see note) | UTF8String | V | P | | M | Y | Gi, Sgi | +| 3GPP-CG-IPv6-Address | 14 | 16.4.7
(see note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-SGSN-IPv6-Address | 15 | 16.4.7
(see note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-GGSN-IPv6-Address | 16 | 16.4.7
(see note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-IPv6-DNS-Servers | 17 | 16.4.7
(see note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-SGSN-MCC-MNC | 18 | 16.4.7
(see note) | UTF8String | V | P | | M | Y | Gi, Sgi | +| 3GPP-IMEISV | 20 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-RAT-Type | 21 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-User-Location-Info | 22 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-MS-TimeZone | 23 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-CAMEL-Charging-Info | 24 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Gi | +| 3GPP-Packet-Filter | 25 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-Negotiated-DSCP | 26 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-Allocate-IP-Type | 27 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Gi, Sgi | +| TWAN-Identifier | 29 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Sgi | +| 3GPP-User-Location-Info-Time | 30 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Gi, Sgi | +| 3GPP-Secondary-RAT-Usage | 31 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Sgi | +| 3GPP-UE-Local-IP-Address | 32 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Sgi | +| 3GPP-UE-Source-Port | 33 | 16.4.7
(see Note) | OctetString | V | P | | M | Y | Sgi | + +NOTE: The use of Radius VSA as a Diameter vendor AVP is described in Diameter NASREQ (IETF RFC 7155 [m]) and the P flag may be set. + +The information represented by some of the Sgi AVPs may not be available to the P-GW depending on the UE's radio access and the S5/S8 protocol type (GTP or PMIP). For example, the P-GW will be aware of the User Location Info (e.g. TAI) if the user is in LTE access and GTP based S5/S8 is used. + +However, such information is not passed to the P-GW when PMIP based S5/S8 is utilised. In such scenarios, if an Sgi specific AVP is configured in the P-GW to be transferred to the Diameter AAA server, but the information in the P-GW is not up to date or not available; the P-GW shall not send the corresponding AVP, unless otherwise stated in the AVP definitions in subclause 16.4.7.2. + +## 16a.6 Gi/Sgi specific Experimental-Result-Code AVP + +Diameter Base IETF RFC 6733 [111] defines a number of Result-Code AVP values that are used to report protocol errors and how those are used. Those procedures and values apply for the present specification. + +Due to the Gi/Sgi specific AVPs, new application results can occur and the Experimental-Result AVP is used to transfer the 3GPP-specific result codes. The Experimental-Result AVP is a grouped AVP containing the Vendor-Id AVP set to the value of 3GPP's vendor identifier (10415) and an Experimental-Result-Code AVP. + +The following Gi/Sgi specific Experimental-Result-Code value is defined: + +DIAMETER\_PDP\_CONTEXT\_DELETION\_INDICATION (2021) + +For GGSN this is an indication to the server that the requested PDP Context or IP-CAN session has been deleted. + +For P-GW this is an indication to the server that the requested bearer or IP-CAN session has been deleted. + +## 16a.7 Gi/Sgi re-used AVPs + +Table 9b lists the Diameter AVPs re-used by the Gi/Sgi reference point from existing Diameter Applications, reference to the respective specifications and a short description of the usage within the Gi/Sgi reference point. + +**Table 9b: Gi/Sgi re-used Diameter AVPs** + +| Attribute Name | Reference | Description | +|---------------------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| External-Identifier | 3GPP
TS 29.336 [101] | A globally unique identifier of a UE used towards external servers instead of IMSI and MSISDN, refer to 3GPP TS 23.682 [100] and 3GPP TS 23.003 [40]. | + +# 17 Usage of Diameter on Gmb interface + +Signalling between GGSN and BM-SC is exchanged at Gmb reference point. BM-SC functions for different MBMS bearer services may be provided by different physical network elements. To allow this distribution of BM-SC functions, the Gmb protocol must support the use of proxies to correctly route the different signalling interactions in a manner which is transparent to the GGSN. + +The GGSN uses the Gmb interface + +- to request authorisation/deactivation of a user for a multicast MBMS service, +- to register/de-register the GGSN for receiving a multicast MBMS service. +- to receive indication of session start, session update and session stop messages, which shall cause the GGSN, SGSN and RAN to set up/tear down the appropriate resources for the service. For further details, see 3GPP TS 23.246 [65]. +- to receive indication if IP multicast distribution to UTRAN should be used for the MBMS user plane data. + +The support of Gmb within the GGSN is optional, and needed for MBMS. + +The Gmb application is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP () is 10415. The Gmb application identifier value assigned by IANA is 16777223. + +The Gmb application identifier value shall be included in the Auth-Application-Id AVP. + +The BM-SC and the GGSN shall advertise the support of the Gmb application by including the value of the application identifier in the Auth-Application-Id AVP and the value of the 3GPP (10415) in the Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands as specified in IETF RFC 6733 [111], i.e. as part of the Vendor-Specific-Application-Id AVP. The Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands are specified in the Diameter Base Protocol. + +## 17.1 MBMS user authorisation + +Upon reception of an IGMP (IPv4) or MLD (IPv6) Join message for an IP multicast address allocated to MBMS services, the GGSN shall request authorisation of the user for this multicast MBMS bearer service (identified by the PDP context over which the IGMP join is received). + +The GGSN shall support pre-configuration of a BM-SC or Gmb proxy server for authorisation purposes to which the request shall be sent. The GGSN may support a list of pre-configured BM-SC servers based on the MBMS bearer service requested, for authorisation purposes. + +Upon receipt of an MBMS UE Context Establishment Request for a user who has not already been authorised for the MBMS bearer service, the GGSN shall request authorisation of the user for this service. + +## 17.2 MBMS service registration / de-registration + +The MBMS service registration of the GGSN at the BM-SC shall be performed after authorisation of the first user on a particular GGSN, for a particular multicast MBMS Bearer service. The MBMS service de-registration of the GGSN shall be performed when the last user leaves a particular GGSN, for a particular multicast MBMS bearer service. + +The MBMS de-registration procedure shall be initiated by BM-SC when the specific multicast MBMS service is terminated. + +The GGSN shall support pre-configuration of a BM-SC or Gmb proxy server for registration/de-registration purposes. The GGSN may support a list of pre-configured BM-SC servers based on the MBMS bearer service requested for bearer registration purposes. + +## 17.3 MBMS session start / update/ stop + +The MBMS session start shall be used by the BM-SC to trigger the bearer resource establishment and announce the arrival of data for a MBMS bearer service (along with the attributes of the data to be delivered e.g. QoS or MBMS service area) to every GGSN that will deliver the MBMS bearer service. The MBMS session start shall also be used by the BM-SC to indicate to GGSN if IP multicast mechanism should be used for user plane data distribution to UTRAN. + +The MBMS session update shall be used by the BM-SC to trigger the update of MBMS session attributes in the affected GGSNs. + +The MBMS session stop shall be used by the BM-SC to indicate the end of the data stream for an MBMS bearer service to every GGSN that has been delivering the MBMS bearer service. + +## 17.4 MBMS user deactivation + +The MBMS user deactivation is a procedure that removes the MBMS UE context from the GGSN for a particular multicast MBMS bearer service (also called "leaving procedure"). This procedure can be initiated by the GGSN or the BM-SC over the Gmb interface. + +When the last user leaves a particular GGSN, for a particular MBMS multicast service, a de-registration process shall be initiated. + +## 17.5 Message flows + +### 17.5.1 Service activation + +The multicast MBMS bearer service activation procedure registers the user in the network to enable the reception of data from a specific multicast MBMS bearer service + +![Sequence diagram showing the activation of an MBMS multicast service between a UE, GGSN, and BMSC. The process involves IGMP/MLD Join, AA-Request/Answer, MBMS notification, and Create MBMS Context messages, with User Authorization and Conditional Registration steps.](93699fb71e95b4df5a3871fdcf818982_img.jpg) + +``` + +sequenceDiagram + participant UE + participant GGSN + participant BMSC + + Note right of BMSC: User Authorisation + UE->>GGSN: 1. IGMP/MLD Join Message + GGSN->>BMSC: 2. AA-Request [user/service] + BMSC-->>GGSN: 3. AA-Answer [user/service] + GGSN->>UE: 4. MBMS notification Req. + UE-->>GGSN: 5. MBMS Notification Resp. + + Note right of BMSC: User Authorization + Note right of BMSC: Conditional Registration procedure (if the GGSN was not yet registered) + + GGSN->>GGSN: 6. Create MBMS Ctxt + GGSN->>BMSC: 7. AA-Request [user/service] + BMSC-->>GGSN: 8. AA-Answer [user/service] + GGSN-->>BMSC: 9. AA-Request [service] + BMSC-->>GGSN: 10. AA-Answer [service] + GGSN->>GGSN: 11. Create MBMS Ctxt Resp + +``` + +Sequence diagram showing the activation of an MBMS multicast service between a UE, GGSN, and BMSC. The process involves IGMP/MLD Join, AA-Request/Answer, MBMS notification, and Create MBMS Context messages, with User Authorization and Conditional Registration steps. + +**Figure 26; Activation of an MBMS multicast service** + +1. The GGSN receives an IGMP (IPv4) or MLD (IPv6) Join message from a UE, over the default PDP context to signal its interest in receiving a particular multicast MBMS bearer service identified by an IP multicast address. +2. The GGSN sends an AAR seeking authorization for the activating UE to receive data from a particular service. +3. The authorization decision is provided in the AAA together with the APN to be used for creation of the MBMS UE context. If the AAA indicates that the UE is not authorized to receive the MBMS data the process terminates with no additional message exchange. +4. The GGSN sends an MBMS Notification Request (IP multicast address, APN, Linked NSAPI) to the SGSN. Linked NSAPI is set equal to the NSAPI of the PDP context over which the Join request was received. The IP multicast address is the one requested by the UE in the Join request. The APN may be different from the APN to + +which the default PDP context has been activated. In any case, the APN may resolve to a GGSN that is different from the GGSN receiving the IGMP/MLD Join request. The GGSN starts a MBMS Activation Timer as GGSN may receive no response, e.g. in case SGSN or UE does not support MBMS. + +5. The SGSN sends a MBMS Notification Response (Cause) to the GGSN that sent the MBMS Notification Request, where Cause shall indicate successful or unsuccessful MBMS context activation for the reason of SGSN or UE . Upon reception of the response message with Cause indicating unsuccessful operation or time-out of the MBMS Activation Timer in the GGSN, the GGSN may fallback to IP multicast access as defined in clause 11.7. +6. The SGSN creates an MBMS UE context and sends a Create MBMS Context Requests (IP multicast address, APN, RAI) to the GGSN. That GGSN may be different from the GGSN receiving the IGMP/MLD Join request. +7. The GGSN sends an AAR seeking authorization for the activating UE. +8. The authorization decision is provided in the AAA +9. If the GGSN does not have the MBMS Bearer Context information for this MBMS bearer service, i.e. the GGSN was not yet registered, the GGSN sends a AAR to the BM-SC. See subclause 17.5.4 "Registration Procedure". + +If no TMGI has been allocated for this MBMS bearer service, the BM-SC will allocate a new TMGI. This TMGI will be passed to GGSN via the AAA message. + +10. The BM-SC responds with a AAA containing the MBMS Bearer Context information for this MBMS bearer service and adds the identifier of the GGSN to the "list of downstream nodes" parameter in its MBMS Bearer Context. See subclause 17.5.4 "Registration Procedure". +11. The GGSN creates an MBMS UE context and sends a Create MBMS Context Response to the SGSN + +## 17.5.2 Session start procedure + +The BM-SC initiates the MBMS session start procedure when it is ready to send data. This informs the GGSN of the imminent start of the transmission and MBMS session attributes are provided to the GGSNs included in the list of downstream nodes in BM-SC. For a multicast MBMS service these are the GGSNs that have previously registered for the corresponding MBMS bearer service. The bearer plane is allocated. + +BM-SC and GGSN shall at least support IP unicast encapsulation of IP multicast datagrams, which shall be default mode of sending user plane data. BM-SC may support sending user plane IP multicast datagrams to GGSN, and GGSN also may support this mode of operation. + +![Sequence diagram of the MBMS Session Start procedure between GGSN and BM-SC.](c71fd22661fbd344a66043940bbd84fc_img.jpg) + +``` + +sequenceDiagram + participant GGSN + participant BM-SC + Note right of BM-SC: 1. RAR (Start) + BM-SC->>GGSN: RAR (Start) + Note left of GGSN: 2. RAA (Start) + GGSN->>BM-SC: RAA (Start) + +``` + +The diagram illustrates the interaction between the GGSN and the BM-SC for the MBMS Session Start procedure. It consists of two steps: 1. The BM-SC sends a RAR (Start) message to the GGSN. 2. The GGSN responds with a RAA (Start) message to the BM-SC. + +Sequence diagram of the MBMS Session Start procedure between GGSN and BM-SC. + +**Figure 27: MBMS Session Start procedure** + +1. The BM-SC sends a RAR message to indicate the impending start of the transmission and to provide the session attributes to the GGSNs listed in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context. BM-SC may indicate to GGSN that BM-SC supports sending the user plane IP multicast data without IP unicast encapsulation. In such case BM-SC shall send multicast source address as specified by IETF RFC 4604 [73] and IETF RFC 4607 [74]. The BM-SC sets the state attribute of its MBMS Bearer Context to 'Active'. By sending "CN IP Multicast Distribution" parameter to GGSN, the BM-SC indicates if IP multicast mechanism should be used for user plane data distribution to UTRAN. "MBMS HC Indicator" parameter, if present, indicates that a header compression is used for MBMS user plane data. + +2. For a broadcast MBMS bearer service the GGSN creates an MBMS Bearer Context. The GGSN stores the session attributes in the MBMS Bearer Context, sets the state attribute of its MBMS Bearer Context to 'Active' and sends a RAA message to the BM-SC. In case GGSN receives BM-SC multicast source address, which indicates BM-SC support for both modes of sending user plane data, GGSN decides in which mode GGSN shall receive the user plane data. In case GGSN decides to receive unicast encapsulated data, then GGSN shall send own IP address and UDP port for the encapsulating unicast IP and UDP layer of the user plane to BM-SC. In case GGSN decides to receive IP multicast packets, then GGSN shall join the multicast group as specified by IETF RFC 4604 [73] and IETF RFC 4607 [74], and indicate to BM-SC about the decision. + +### 17.5.3 Session stop procedure + +The BM-SC initiates the MBMS session stop procedure when it considers the MBMS session terminated. Typically this will happen when there is no more MBMS data expected to be transmitted for a sufficiently long period of time to justify the release of bearer plane resources in the network. + +![Sequence diagram for MBMS Session Stop procedure](ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg) + +``` +sequenceDiagram + participant BM-SC + participant GGSN + Note right of BM-SC: 1. RAR (Stop) + BM-SC->>GGSN: RAR (Stop) + Note left of GGSN: 2. RAA (Stop) + GGSN->>BM-SC: RAA (Stop) +``` + +The diagram illustrates the MBMS Session Stop procedure between a BM-SC and a GGSN. The BM-SC sends a RAR (Stop) message to the GGSN, and the GGSN responds with a RAA (Stop) message. + +Sequence diagram for MBMS Session Stop procedure + +Figure 28: MBMS Session Stop procedure + +1. The BM-SC sends a RAR message to all GGSNs listed in the "list of downstream nodes" parameter of the affected MBMS Bearer Context to indicate that the MBMS session is terminated and the bearer plane resources can be released. +2. The GGSN sets the state attribute of its MBMS Bearer Context to 'Standby' and sends a RAA message to the BM-SC. An AAR message is not mandated for the Gmb application in response to a RAR- RAA command exchange. + +### 17.5.4 Registration procedure + +The registration procedure occurs when the GGSN indicates the BM-SC that it would like to receive session attributes and data for a particular multicast MBMS bearer service, in order to be distributed further downstream. A corresponding MBMS Bearer Context is established as a result between the GGSN and the BM-SC. + +![Sequence diagram for MBMS Registration procedure](e0774c1e190583a6c13ea92ada80aa9e_img.jpg) + +``` +sequenceDiagram + participant GGSN + participant BM-SC + Note left of BM-SC: 1. AA-Request [service] + GGSN->>BM-SC: AA-Request [service] + Note right of GGSN: 2. AA-Answer [service] + BM-SC->>GGSN: AA-Answer [service] +``` + +The diagram illustrates the MBMS Registration procedure between a GGSN and a BM-SC. The GGSN sends an AA-Request [service] message to the BM-SC, and the BM-SC responds with an AA-Answer [service] message. + +Sequence diagram for MBMS Registration procedure + +Figure 29: MBMS Registration procedure + +1. When the GGSN has no MBMS Bearer Context for an MBMS bearer service and the GGSN receives an MBMS Registration from an SGSN for this MBMS bearer service, or when the first MBMS UE Context is created in the GGSN for an MBMS bearer service for which the GGSN has no MBMS Bearer Context, the GGSN sends a AAR message (containing the IP multicast address and the APN) to the BM-SC. +2. Upon reception of an AAR from a GGSN, the BM-SC adds the identifier of the GGSN to the "list of downstream nodes" parameter in its MBMS Bearer Context and responds with an AAA message (containing TMGI, and Required Bearer Capabilities). If the MBMS Bearer Context is in the 'Active' state, the BM-SC initiates the Session Start procedure with the GGSN, as described in clause 17.5.2 "Session Start Procedure". + +### 17.5.5 De-registration procedure (GGSN initiated) + +The MBMS de-registration is the procedure by which the GGSN informs the BM-SC that it does not need to receive signalling, session attributes and data for a particular multicast MBMS bearer service anymore and therefore would like to be removed from the corresponding distribution tree. + +![Sequence diagram for MBMS De-Registration procedure (GGSN initiated). The diagram shows two vertical lifelines: GGSN on the left and BM-SC on the right. A solid arrow labeled '1. ST-Request [service]' points from the GGSN lifeline to the BM-SC lifeline. A solid arrow labeled '2. ST-Answer [service]' points from the BM-SC lifeline back to the GGSN lifeline.](eea0bd1826a6e1bdcadff03936a7b20a_img.jpg) + +``` +sequenceDiagram + participant GGSN + participant BM-SC + Note left of GGSN: GGSN initiates de-registration + GGSN->>BM-SC: 1. ST-Request [service] + BM-SC-->>GGSN: 2. ST-Answer [service] +``` + +Sequence diagram for MBMS De-Registration procedure (GGSN initiated). The diagram shows two vertical lifelines: GGSN on the left and BM-SC on the right. A solid arrow labeled '1. ST-Request [service]' points from the GGSN lifeline to the BM-SC lifeline. A solid arrow labeled '2. ST-Answer [service]' points from the BM-SC lifeline back to the GGSN lifeline. + +Figure 30: MBMS De-Registration procedure + +1. When the "list of downstream nodes" of a particular MBMS Bearer Context in the GGSN becomes empty and the GGSN has no MBMS UE Contexts linked to that MBMS Bearer Context, the GGSN sends a STR message to the BM-SC. If a bearer plane had been established over Gi for this MBMS bearer service, the bearer plane is released. +2. The BM-SC removes the identifier of the GGSN from the "list of downstream nodes" parameter of the affected MBMS Bearer Context and confirms the operation by sending a STA message to the GGSN. + +### 17.5.6 De-registration procedure (BM-SC initiated) + +This MBMS de-registration procedure is initiated by BM-SC when the specific multicast MBMS bearer service is terminated. This procedure tears down the distribution tree for the delivery of session attributes and MBMS data. This procedure results in releasing of all MBMS Bearer Contexts. + +![Sequence diagram for MBMS De-Registration procedure (BM-SC initiated). The diagram shows two vertical lifelines: GGSN on the left and BM-SC on the right. A solid arrow labeled '1. AS-Request [service]' points from the BM-SC lifeline to the GGSN lifeline. A solid arrow labeled '2. AS-Answer [service]' points from the GGSN lifeline back to the BM-SC lifeline.](e4aab374983ba0fc24496fe7cd11c06c_img.jpg) + +``` +sequenceDiagram + participant GGSN + participant BM-SC + Note right of BM-SC: BM-SC initiates de-registration + BM-SC->>GGSN: 1. AS-Request [service] + GGSN-->>BM-SC: 2. AS-Answer [service] +``` + +Sequence diagram for MBMS De-Registration procedure (BM-SC initiated). The diagram shows two vertical lifelines: GGSN on the left and BM-SC on the right. A solid arrow labeled '1. AS-Request [service]' points from the BM-SC lifeline to the GGSN lifeline. A solid arrow labeled '2. AS-Answer [service]' points from the GGSN lifeline back to the BM-SC lifeline. + +Figure 31: MBMS De-Registration procedure BM-SC initiated + +1. The BM-SC sends a ASR message to all GGSNs contained in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context to indicate that a specific MBMS bearer service is terminated. +2. The GGSN returns a ASA message to the BM-SC. The BM-SC releases all MBMS UE Contexts and removes the identifier of the GGSN from the "list of downstream nodes" parameter of the corresponding MBMS Bearer context. + +## 17.5.7 Service deactivation + +The multicast service deactivation is a signalling procedure that will terminate the user registration to a particular MBMS multicast service. The multicast service deactivation can be initiated by the GGSN, when indicated so by the UE, or by the BM-SC, for service specific reasons. + +![Sequence diagram of MBMS Service deactivation procedure between UE, GGSN, and BM-SC.](5efe6377e22b9ab76a19a70da29976b9_img.jpg) + +``` + +sequenceDiagram + participant UE + participant GGSN + participant BM-SC + + Note right of BM-SC: User Leave + UE->>GGSN: 1. UE Leave indication + GGSN->>BM-SC: 2. Session-Termination-Request [user/service] + BM-SC-->>GGSN: 3. Session-Termination-Answer [user/service] + GGSN->>UE: 4. MBMS UE Ctxt + Note right of BM-SC: User Deactivation + UE->>GGSN: 5. Delete MBMS Ctxt Req. + GGSN->>BM-SC: 6. Session-Termination-Request [user/service] + BM-SC-->>GGSN: 7. Session-Termination-Answer[user/service] + GGSN->>BM-SC: 8. Session-Termination-Request [service] + Note right of BM-SC: Conditional de-registration procedure (if it was the last user in this GGSN for this MBMS service) + BM-SC-->>GGSN: 9. Session-Termination-Answer[service] + +``` + +The diagram illustrates the MBMS Service deactivation procedure. It starts with a 'UE Leave indication' (1) from the UE to the GGSN. The GGSN sends a 'Session-Termination-Request [user/service]' (2) to the BM-SC. The BM-SC responds with a 'Session-Termination-Answer [user/service]' (3). The GGSN then sends an 'MBMS UE Ctxt' (4) to the UE. Next, the UE sends a 'Delete MBMS Ctxt Req.' (5) to the GGSN. The GGSN sends another 'Session-Termination-Request [user/service]' (6) to the BM-SC. The BM-SC responds with a 'Session-Termination-Answer[user/service]' (7). The GGSN then sends a 'Session-Termination-Request [service]' (8) to the BM-SC. Finally, the BM-SC responds with a 'Session-Termination-Answer[service]' (9). The diagram is divided into three phases: 'User Leave' (steps 1-4), 'User Deactivation' (steps 5-7), and 'Conditional de-registration procedure (if it was the last user in this GGSN for this MBMS service)' (steps 8-9). + +Sequence diagram of MBMS Service deactivation procedure between UE, GGSN, and BM-SC. + +Figure 32: MBMS Service deactivation procedure + +1. The UE sends an IGMP (IPv4) or MLD (IPv6) Leave message over the default PDP context to leave a particular multicast service identified by an IP multicast address. +2. The GGSN sends a STR to the BM-SC, indicating that the UE is requesting to leave the multicast service. The session to be terminated is uniquely identified by the Diameter session-id. +3. Upon reception of the STR, the BM-SC verifies that the IP multicast address corresponds to a valid MBMS bearer service and sends a STA to the GGSN that originated the Leave Indication. The APN shall be the same that was provided during service activation (see " Service Activation" procedure). + +4. Upon reception of the STA the GGSN sends an MBMS UE Context Deactivation Request to the SGSN. The IP multicast address, APN and IMSI together identify the MBMS UE Context to be deleted by the SGSN. The APN is the one received in step 3. +5. The GGSN receives a Delete MBMS Context Request (NSAPI). This GGSN may be different from the GGSN that receives IGMP Leave request in step 1. +6. The GGSN deletes the MBMS UE Context and sends a STR to the BM-SC to confirm the successful deactivation of the MBMS UE Context. +7. The BM-SC, then, deletes the MBMS UE Context and sends a confirmation to the GGSN in a STA message. +8. If the GGSN does not have any more users interested in this MBMS bearer service and the "list of downstream nodes" in the corresponding MBMS Bearer Context is empty, the GGSN initiates a De-Registration procedure as specified in 17.5.5. +9. The BM-SC confirms the operation by sending a STA message to the GGSN as specified in 17.5.5. + +### 17.5.7.1 BM-SC Initiated Multicast Service Deactivation + +This section defines the BM-SC initiated Multicast Service Deactivation procedure. + +![Sequence diagram for BM-SC initiated MBMS Service deactivation procedure. The diagram shows three messages between the GGSN and the BM-SC. 1. AS-Request [user/service] from BM-SC to GGSN. 2. AS-Answer [user/service] from GGSN to BM-SC. 3. MBMS UE Ctxt from GGSN to the left (towards SGSN). A dashed box labeled 'User Leave' is positioned to the right of the BM-SC, with a bracket grouping the first two messages.](629606c93e8d5f98d72a90044ef4b15a_img.jpg) + +``` + +sequenceDiagram + participant GGSN + participant BM-SC + Note right of BM-SC: User Leave + BM-SC->>GGSN: 1. AS-Request [user/service] + GGSN-->>BM-SC: 2. AS-Answer [user/service] + GGSN->>SGSN: 3. MBMS UE Ctxt + +``` + +Sequence diagram for BM-SC initiated MBMS Service deactivation procedure. The diagram shows three messages between the GGSN and the BM-SC. 1. AS-Request [user/service] from BM-SC to GGSN. 2. AS-Answer [user/service] from GGSN to BM-SC. 3. MBMS UE Ctxt from GGSN to the left (towards SGSN). A dashed box labeled 'User Leave' is positioned to the right of the BM-SC, with a bracket grouping the first two messages. + +**Figure 32a: BM-SC initiated MBMS Service deactivation procedure** + +1. The BM-SC sends an ASR to the GGSN, indicating that the UE shall be removed from the multicast service. The session to be terminated is uniquely identified by the Diameter session-id. +2. Upon reception of the ASR, the GGSN sends an ASA to the BM-SC +3. Upon reception of the ASR the GGSN sends an MBMS UE Context Deactivation Request to the SGSN. The IP multicast address, APN and IMSI together identify the MBMS UE Context to be deleted by the SGSN. + +Steps from 5 to 9 of figure 32 in section 17.5.7 follow. + +### 17.5.8 Trace Session Activation procedure + +The Trace Session Activation procedure occurs when the GGSN indicates to the BM-SC that a Trace Session needs to be activated. + +![Sequence diagram for Trace Session Activation procedure between GGSN and BM-SC.](93bd00a00fa28558486f0664550699b1_img.jpg) + +``` +sequenceDiagram + participant GGSN + participant BM-SC + Note right of GGSN: 1. AA-Request [Trace] + GGSN->>BM-SC: 1. AA-Request [Trace] + Note left of BM-SC: 2. AA-Answer [Trace] + BM-SC-->>GGSN: 2. AA-Answer [Trace] +``` + +Sequence diagram for Trace Session Activation procedure between GGSN and BM-SC. + +**Figure 33: Trace Session Activation procedure** + +1. When the GGSN has received a Trace Activation message from the SGSN, in a Create MBMS Context Request/Update MBMS Context Request, that requires the activation of a Trace Session in the BM-SC, the GGSN sends an AAR message (containing the IMSI and the Additional MBMS Trace Info AVPs) to activate a trace session in the BM-SC. +2. Upon reception of an AAR from a GGSN to activate a Trace Session, the BM-SC responds with an AAA message. + +### 17.5.9 Trace Session Deactivation procedure + +The Trace Session Deactivation procedure occurs when the GGSN indicates to the BM-SC that a Trace Session, previously activated, needs to be deactivated. + +![Sequence diagram for Trace Session Deactivation procedure between GGSN and BM-SC.](db184eff73ec14dc2dde56126813517f_img.jpg) + +``` +sequenceDiagram + participant GGSN + participant BM-SC + Note right of GGSN: 1. ST-Request [Trace] + GGSN->>BM-SC: 1. ST-Request [Trace] + Note left of BM-SC: 2. ST-Answer [Trace] + BM-SC-->>GGSN: 2. ST-Answer [Trace] +``` + +Sequence diagram for Trace Session Deactivation procedure between GGSN and BM-SC. + +**Figure 34: Trace Session Deactivation procedure** + +1. When the GGSN has received a Trace Deactivation message from the SGSN, in a Create MBMS Context Request/Update MBMS Context Request, that requires the deactivation of a Trace Session in the BM-SC, the GGSN sends a STR message (containing the Additional MBMS Trace Info AVP) to deactivate a trace session in the BM-SC and to tear down the corresponding Diameter Session previously established to activate the Trace Session. +2. Upon reception of an STR from a GGSN to deactivate a Trace Session, the BM-SC responds with an STA message. + +### 17.5.10 MBMS UE Context Modification Procedure + +During the multicast MBMS bearer service activation, the MBMS UE Context is stored in the BM-SC. Later, the MBMS UE Context shall be updated when the UE enters a new Routeing Area (RA) served by a new SGSN or the UE is transitioning between UTRAN and A/Gb mode GERAN or vice versa (Inter-system Intra-SGSN change). See 3GPP TS 23.246 [65] and 3GPP TS 29.060 [24]. GGSN shall pass the relevant data via the Gmb interface to enable the BM-SC to update its MBMS UE context accordingly. + +![Sequence diagram showing the modification of an MBMS UE Context in BM-SC. The diagram involves two entities: GGSN and BM-SC. The sequence of messages is: 1. Update MBMS Context Request from GGSN to BM-SC; 2. Update MBMS Context Response from BM-SC to GGSN; 3. AA-Request [user] from GGSN to BM-SC; 4. AA-Answer [user] from BM-SC to GGSN.](d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg) + +``` + +sequenceDiagram + participant GGSN + participant BM-SC + Note left of GGSN: 1. Update MBMS Context Request + GGSN->>BM-SC: 1. Update MBMS Context Request + Note right of BM-SC: 1. Update MBMS Context Response + BM-SC-->>GGSN: 1. Update MBMS Context Response + Note right of GGSN: 2. AA-Request [user] + GGSN->>BM-SC: 2. AA-Request [user] + Note right of BM-SC: 3. AA-Answer [user] + BM-SC-->>GGSN: 3. AA-Answer [user] + +``` + +Sequence diagram showing the modification of an MBMS UE Context in BM-SC. The diagram involves two entities: GGSN and BM-SC. The sequence of messages is: 1. Update MBMS Context Request from GGSN to BM-SC; 2. Update MBMS Context Response from BM-SC to GGSN; 3. AA-Request [user] from GGSN to BM-SC; 4. AA-Answer [user] from BM-SC to GGSN. + +**Figure 35; Modification of an MBMS UE Context in BM-SC** + +1. On request from SGSN, the MBMS UE Context is updated in the GGSN. +2. The GGSN sends updated MBMS UE Context parameters (RAI, and CGI/SAI as specified in clause 17.6.1) to BM-SC in an AAR message. +3. The BM-SC updates its MBMS UE Context fields and responds with an AAA message. + +If the GGSN receives new or updated trace information in step 1, then the above procedure may be followed by a Trace Session Activation procedure (see clause 17.5.8) or a Trace Session Deactivation procedure (see clause 17.5.9). + +## 17.5.11 Session Update Procedure + +The BM-SC initiates the MBMS session update procedure when the service area for an ongoing MBMS session shall be modified. This procedure is defined only for MBMS broadcast services. The MBMS session update procedure is initiated towards one or more of the GGSNs in the list of downstream nodes in the BM-SC, according to the changes in the service area. + +**NOTE:** In addition, when the MBMS Service Area for an ongoing broadcast session is changed in the BM-SC, then GGSN(s) may be added to, or removed from, the list of downstream nodes in the BM-SC. The BM-SC will initiate MBMS session start procedures or MBMS session stop procedures towards these GGSNs accordingly. + +The attributes that can be modified by the session update procedure are the MBMS Service Area, and the list of downstream nodes for GGSN. + +When a session update message is received, GGSN will update its MBMS Bearer Context accordingly and inform its downstream SGSNs of the changed MBMS service area. If a list of downstream SGSNs is included in the session update message, GGSN shall initiate a session start procedure towards the new downstream SGSNs, and a session stop procedure towards the SGSNs that have been removed from the list. + +![Sequence diagram for MBMS Session Update procedure. It shows two lifelines: GGSN and BM-SC. The BM-SC sends a '1. RAR (Update)' message to the GGSN. The GGSN responds with a '2. RAA (Update)' message to the BM-SC.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) + +``` + +sequenceDiagram + participant BM-SC + participant GGSN + Note left of BM-SC: 1. RAR (Update) + BM-SC->>GGSN: 1. RAR (Update) + Note right of GGSN: 2. RAA (Update) + GGSN->>BM-SC: 2. RAA (Update) + +``` + +Sequence diagram for MBMS Session Update procedure. It shows two lifelines: GGSN and BM-SC. The BM-SC sends a '1. RAR (Update)' message to the GGSN. The GGSN responds with a '2. RAA (Update)' message to the BM-SC. + +**Figure 27a: MBMS Session Update procedure** + +1. The BM-SC sends a RAR message to the GGSNs that need to update its session attributes. +2. GGSN stores the updated session attributes in the MBMS Bearer Context, initiates session start, session stop or session update procedures towards the SGSNs in its list of downstream nodes and sends an RAA message to the BM-SC. An AAR message is not mandated for the Gmb application in response to a RAR-RAA command exchange. + +### 17.5.12 MBMS broadcast session termination (GGSN initiated) + +![Sequence diagram for Broadcast session termination (GGSN initiated). It shows two lifelines: GGSN and BM-SC. The GGSN sends a '1. ST-Request [service]' message to the BM-SC. The BM-SC responds with a '2. ST-Answer [service]' message to the GGSN.](bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg) + +``` + +sequenceDiagram + participant GGSN + participant BM-SC + Note left of GGSN: 1. ST-Request [service] + GGSN->>BM-SC: 1. ST-Request [service] + Note right of BM-SC: 2. ST-Answer [service] + BM-SC->>GGSN: 2. ST-Answer [service] + +``` + +Sequence diagram for Broadcast session termination (GGSN initiated). It shows two lifelines: GGSN and BM-SC. The GGSN sends a '1. ST-Request [service]' message to the BM-SC. The BM-SC responds with a '2. ST-Answer [service]' message to the GGSN. + +**Figure 36: Broadcast session termination** + +1. In exceptional cases (e.g. resource pre-emption or timeout of the MBMS session), the GGSN may send an STR command to the BM-SC to initiate the termination of the Diameter session related to a broadcast MBMS bearer service. If a bearer plane had been established over Gi for this MBMS bearer service, the bearer plane is released. +2. The BM-SC removes the Diameter session and confirms the operation by sending an STA message to the GGSN. + +## 17.6 Gmb Messages + +This clause defines the Gmb interface Diameter messages. + +The relevant AVPs that are of use for the Gmb interface are detailed in this clause. Other Diameter NASREQ (IETF RFC 7155 [120]) AVPs, even if their AVP flag rules is marked with "M", are not required for being compliant with the current specification. + +All Gmb specific AVPs for Gmb are needed to be compliant to the Gmb interface unless otherwise stated. + +## 17.6.1 AAR Command + +The AAR command, defined in Diameter NASREQ (IETF RFC 7155 [120]), is indicated by the Command-Code field set to 265 and the 'R' bit set in the Command Flags field. It, is sent by the GGSN to the BM-SC to request user authorization (authorize the activating UE to receive Data) , to modify an MBMS UE Context in the BM-SC or to register the GGSN for a particular multicast MBMS bearer service. When used for these purposes, the Additional-MBMS-Trace-Info AVP shall not be included. + +When the AAR command is used by the GGSN to modify an MBMS UE context in the BM-SC, it shall include all the parameters that have been changed according to the triggering Update MBMS Context Request, ref. fig. 35. The inclusion of CGI/SAI in the 3GPP-User-Location-Info AVP shall be according to the rules detailed in subclause 15.1.1a in 3GPP TS 23.060 [3]. The Called-Station-Id AVP, Calling-Station-Id AVP, Framed-IP-Address AVP, Framed-IPv6-Prefix AVP and Framed-Interface-Id AVP shall not be included, + +The AAR command is also used when the GGSN needs to activate a Trace Session in the BM-SC. In this case the Called-Station-Id AVP, Calling-Station-Id AVP, Framed-IP-Address AVP, Framed-IPv6-Prefix AVP, Framed-Interface-Id AVP, and RAI AVP shall not be included. For more detailed description of Trace Session activation/deactivation procedures see 3GPP TS 32.422 [69]. + +The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +The bold marked AVPs in the message format indicate new optional AVPs for Gmb, or modified existing AVPs. + +Message Format: + +``` + ::= < Diameter Header: 265, REQ, PXY > + < Session-Id > + { Auth-Application-Id } + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Request-Type } + [ Destination-Host ] + [ Called-Station-Id ] + [ Calling-Station-Id ] + [ Framed-IP-Address ] + [ Framed-IPv6-Prefix ] + [ Framed-Interface-Id ] + * [ Proxy-Info ] + * [ Route-Record ] + [ 3GPP-IMSI ] + [ RAI ] + [ 3GPP-IMEISV ] + [ 3GPP-RAT-Type ] + [ 3GPP-User-Location-Info ] + [ 3GPP-MS-TimeZone ] + [ Additional-MBMS-Trace-Info ] +``` + +The GGSN shall allocate a new Session-Id each time an AAR command is sent, except for the case when the AAR is sent to modify an existing MBMS UE Context in the BM-SC. + +A request for user authorisation for an MBMS bearer service is indicated by the presence of the MSISDN within the Calling-Station-Id AVP and the 3GPP-IMSI. Otherwise the request is for the GGSN to be authorised (i.e. registered) to receive the MBMS bearer service. The Framed-IPv6-Prefix AVP contains the IPv6 prefix of the multicast address identifying the MBMS bearer service. + +The Framed-Interface-Id AVP contains the IPv6 interface identifier of the multicast address identifying the MBMS bearer service. + +The Framed-IP-Address AVP contains the IPv4 multicast address identifying the MBMS bearer service. + +The Called-Station-Id AVP contains the Access Point Name (APN) on which the MBMS bearer service authorisation request was received. + +## 17.6.2 AAA Command + +The AAA command, defined in Diameter NASREQ (IETF RFC 7155 [120]), is indicated by the Command-Code field set to 265 and the 'R' bit cleared in the Command Flags field., It is sent by the BM-SC to the GGSN in response to the AAR command. + +When the AAA command is used to acknowledge an AAR that activated a Trace Session, the only Gmb specific AVP that shall be included is the 3GPP-IMSI AVP. + +The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +The bold marked AVPs in the message format indicate new optional AVPs for Gmb, or modified existing AVPs. + +Message Format: + +``` + ::= < Diameter Header: 265, PXY > + < Session-Id > + { Auth-Application-Id } + { Origin-Host } + { Origin-Realm } + [ Result-Code ] + [ Experimental-Result ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ Failed-AVP ] + * [ Proxy-Info ] + [ Alternative-APN ] + [ 3GPP-IMSI ] + [ TMGI ] + [ Required-MBMS-Bearer-Capabilities ] +``` + +## 17.6.3 STR Command + +The STR command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code field set to 275 and the 'R' bit set in the Command Flags field, It is sent by the GGSN to the BM-SC to terminate a DIAMETER session. + +A DIAMETER session for a multicast MBMS service is terminated when the last MBMS UE context for the MBMS bearer service is deleted. This informs the BM-SC that the GGSN would like to be deleted from the distribution tree of a particular MBMS bearer service (De-registration procedure). + +A DIAMETER session for an individual UE's multicast MBMS service authorisation is terminated when the UE has requested to the GGSN to leave the MBMS bearer service. + +A DIAMETER session for a broadcast MBMS service may be terminated by the GGSN in exceptional cases. + +The STR command is also used to deactivate a Trace Session previously activated in the BM-SC and to terminate the associated Diameter Session initiated by the AAR that activated the Trace session. The Gmb specific AVP Additonal-MBMS-Trace-Info shall be included in the STR command only in the case of a Trace Session deactivation. For more detailed description of Trace Session activation/deactivation procedures see 3GPP TS 32.422 [69]. + +The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +Message Format: + +``` + ::= < Diameter Header: 275, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Application-Id } + { Termination-Cause } + [ Destination-Host ] + * [ Class ] + [ Origin-State-Id ] + * [ Proxy-Info ] +``` + +``` +* [ Route-Record ] +[ Additional-MBMS-Trace-Info ] +``` + +## 17.6.4 STA Command + +The STA command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code field set to 275 and the 'R' bit cleared in the Command Flags field, is sent in response to an STR command (e.g. De-registration procedure). + +The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +Message Format: + +``` + ::= < Diameter Header: 275, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + * [ Class ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ Failed-AVP ] + [ Origin-State-Id ] + * [ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + * [ Proxy-Info ] +``` + +## 17.6.5 Re-Auth-Request Command + +The Re-Auth-Request (RAR) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 258 and the message flags' 'R' bit set. + +The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +The bold marked AVPs in the message format indicate new optional AVPs for Gmb, or modified existing AVPs. + +Message Format: + +``` + ::= < Diameter Header: 258, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Destination-Host } + { Auth-Application-Id } + { Re-Auth-Request-Type } + [ Called-Station-Id ] + [ Framed-IP-Address ] + [ Framed-IPv6-Prefix ] + [ Framed-Interface-Id ] + [ MBMS-StartStop-Indication ] + [ MBMS-Service-Area ] + [ MBMS-Required-QoS ] + [ MBMS-Session-Duration ] + [ MBMS-Service-Type ] + [ MBMS-Counting-Information ] + [ MBMS-Session-Identity ] + [ MBMS-Session-Repetition-number ] + [ TMGI ] + * [ 3GPP-SGSN-Address ] ; broadcast case only + * [ 3GPP-SGSN-IPv6-Address ] ; broadcast case only + [ MBMS-2G-3G-Indicator ] + [ MBMS-Time-To-Data-Transfer ] + [ MBMS-User-Data-Mode-Indication ] + [ MBMS-BMSC-SSM-IP-Address ] + [ MBMS-BMSC-SSM-IPv6-Address ] + [ MBMS-Flow-Identifier ] + [ CN-IP-Multicast-Distribution ] + [ MBMS-HC-Indicator ] +``` + +``` +[ Origin-State-Id ] +* [ Proxy-Info ] +* [ Route-Record ] +``` + +The MBMS-StartStop-Indication AVP will indicate if the command is indicating an MBMS Session Start procedure, an MBMS Session Update procedure or an MBMS Session Stop procedure. + +The Diameter Session-Id is used in subsequent procedures to identify the corresponding MBMS session. + +In the multicast case, the BM-SC shall use the Diameter Session-Id that was received during the GGSN Registration procedure. In the broadcast case, the BM-SC shall allocate a Diameter Session-Id for the first RAR message that is used for the first MBMS Session Start procedure of the MBMS bearer service. Then this Diameter Session-Id will be used for the subsequent MBMS sessions of the same MBMS bearer service. The BM-SC will create a new Diameter Session-Id for a subsequent Session Start procedure if, in exceptional cases, the Diameter session for the MBMS bearer service has been deleted. + +BM-SC shall not initiate a new Session Start procedure for a certain MBMS bearer service until the previous MBMS session for that service has been stopped. + +For the MBMS Session Start procedure, RAR is sent by the BM-SC to the GGSN(s) that will deliver the MBMS service (e.g. in the multicast case these are the GGSNs that have previously registered for the corresponding multicast MBMS bearer service), when it is ready to send data. This is a request to activate all necessary bearer resources in the network for the transfer of MBMS data and to notify interested UEs of the imminent start of the transmission. For broadcast MBMS bearer services the RAR message contains either an IPv4 address or an IPv6 address for each participating SGSN. + +For the MBMS Session Update procedure, RAR is sent by the BM-SC in order for the GGSN(s) to update their session attributes. The updated MBMS-Service-Area AVP shall be included. The MBMS-StartStop-Indication AVP with the value UPDATE shall be included. The MBMS-Time-To-Data-Transfer with the value set to 0 shall be included. The MBMS-Session-Duration AVP shall be included to indicate the duration of the remaining part of the MBMS session. The 3GPP-SGSN-Address AVP and the 3GPP-SGSN-IPv6-Address AVP shall be included if the related lists of downstream nodes in the GGSN(s) have changed. The other bold marked AVPs shall be included as given by the previous, corresponding MBMS Session Start procedure. + +For the MBMS Session Stop procedure, RAR is sent by the BM-SC to the GGSN(s) when it considers the MBMS session to be terminated. The session is typically terminated when there is no more MBMS data expected to be transmitted for a sufficiently long period of time to justify a release of bearer plane resources in the network. + +For the MBMS Session Start procedure, the MBMS-Required-QoS indicates the QoS that is required for the MBMS bearer service for the actual MBMS session. The information of the MBMS-2G-3G-Indicator, the MBMS-Service-Area and the MBMS-Counting-Information is passed from BM-SC transparently through GGSN to the SGSN(s) that are relevant for the actual MBMS bearer service. + +According to 3GPP TS 23.246 [65], a specific MBMS bearer service is uniquely identified by its IP multicast address and an APN. For the MBMS Session Start procedure for broadcast MBMS bearer services, the following AVPs are included (either IPv4 or IPv6 address) to enable GGSN to relate incoming payload packets to the actual MBMS bearer service and distribute the packets to the downstream SGSNs related to this service: + +- The Framed-IPv6-Prefix AVP contains the IPv6 prefix of the multicast address. +- The Framed-Interface-Id AVP contains the IPv6 interface identifier of the multicast address. +- The Framed-IP-Address AVP contains the IPv4 multicast address. +- The Called-Station-Id AVP contains the Access Point Name (APN) for which the MBMS bearer service is defined. + +According to 3GPP TS 23.246 [65], the MBMS-Flow-Identifier is optional, used only for broadcast services with location dependent content. For such services, several sessions with the same TMGI, but different MBMS-Flow-Identifiers, may be going on in parallel. However, at any specific location only one version of the content may be available at any point in time. Hence, the MBMS-Service-Areas of the related MBMS bearer contexts shall not overlap. + +## 17.6.6 RE-Auth-Answer Command + +The Re-Auth-Answer (RAA) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 258 and the message flags' 'R' bit clear, is sent in response to the RAR. + +The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +The bold marked AVPs in the message format indicate new optional AVPs for Gmb, or modified existing AVPs. + +Message Format: + +``` + ::= < Diameter Header: 258, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + [ Result-Code ] + [ Experimental-Result ] + [ MBMS-StartStop-Indication ] + [ MBMS-GGSN-Address ] ; for unicast encapsulated user data + [ MBMS-GGSN-IPv6-Address ] ; for unicast encapsulated user data + [ MBMS-GW-UDP-Port ] ; for unicast encapsulated user data + [ MBMS-User-Data-Mode-Indication ] + [ Origin-State-Id ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ Failed-AVP ] + * [ Redirected-Host ] + [ Redirected-Host-Usage ] + [ Redirected-Host-Cache-Time ] + * [ Proxy-Info ] +``` + +If multicast user plane data are to be sent to the GGSN using IP unicast, the GGSN shall allocate an IP transport address and a separate UDP port for each MBMS bearer ( i.e the service uniquely identified by its TMGI and Flow ID and provided by the GPRS to deliver the same IP datagrams to multiple receivers in a designated location). The GGSN shall then use the destination unicast IP address and destination UDP port of user plane packets received over the Gi interface to determine on which MBMS bearer to forward the received user plane packet. + +## 17.6.7 Abort-Session-Request Command + +The Abort-Session-Request (ASR) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 274 and the message flags' 'R' bit set, is sent by the BM-SC to the GGSN to request that the session identified by the Session-Id be stopped. + +The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +Message Format + +``` + ::= < Diameter Header: 274, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Destination-Host } + { Auth-Application-Id } + [ Origin-State-Id ] + * [ Proxy-Info ] + * [ Route-Record ] +``` + +## 17.6.8 Abort-Session-Answer Command + +The Abort-Session-Answer (ASA) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 274 and the message flags' 'R' bit clear, is sent in response to the ASR. + +The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +#### Message Format + +``` + ::= < Diameter Header: 274, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ Origin-State-Id ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ Failed-AVP ] + * [ Redirected-Host ] + [ Redirected-Host-Usage ] + [ Redirect-Max-Cache-Time ] + * [ Proxy-Info ] +``` + +## 17.7 Gmb specific AVPs + +### 17.7.0 General + +Table 10 describes the Gmb specific Diameter AVPs. The Vendor-Id header of all Gmb specific AVPs defined in the present specification shall be set to 3GPP (10415). + +The Gmb specific AVPs require to be supported to be compliant to the present specification. All AVPs in table 10 are mandatory within Gmb interface unless otherwise stated. + +Table 10: Gmb specific AVPs + +| Attribute Name | AVP Code | Section defined | Value Type | AVP Flag rules | | | | | +|-----------------------------------|----------|----------------------|-------------|----------------|-----|------------|----------|-----------| +| | | | | Must | May | Should not | Must not | May Encr. | +| TMGI | 900 | 17.7.2 | OctetString | M,V | P | | | Y | +| Required-MBMS-Bearer-Capabilities | 901 | 17.7.3 | UTF8String | M,V | P | | | Y | +| MBMS-StartStop-Indication | 902 | 17.7.5 | Enumerated | M,V | P | | | Y | +| MBMS-Service-Area | 903 | 17.7.6 | OctetString | M,V | P | | | Y | +| MBMS-Session-Duration | 904 | 17.7.7 | OctetString | M,V | P | | | Y | +| 3GPP-IMSI | 1 | 16.4.7
(see Note) | UTF8String | M,V | P | | | Y | +| Alternative-APN | 905 | 17.7.8 | UTF8String | M,V | P | | | Y | +| MBMS-Service-Type | 906 | 17.7.9 | Enumerated | M,V | P | | | Y | +| 3GPP-SGSN-Address | 6 | 16.4.7
(see note) | OctetString | M, V | P | | | Y | +| 3GPP-SGSN-IPv6-Address | 15 | 16.4.7
(see note) | OctetString | M, V | P | | | Y | +| MBMS-2G-3G-Indicator | 907 | 17.7.10 | Enumerated | M, V | P | | | Y | +| MBMS-Session-Identity | 908 | 17.7.11 | OctetString | M,V | P | | | Y | +| RAI | 909 | 17.7.12 | UTF8String | M, V | P | | | Y | +| 3GPP-IMEISV | 20 | 16.4.7
(see Note) | OctetString | M,V | P | | | Y | +| 3GPP-RAT-Type | 21 | 16.4.7
(see Note) | OctetString | M,V | P | | | Y | +| 3GPP-User-Location-Info | 22 | 16.4.7
(see Note) | OctetString | M,V | P | | | Y | +| 3GPP-MS-TimeZone | 23 | 16.4.7
(see Note) | OctetString | M,V | P | | | Y | +| Additional-MBMS-Trace-Info | 910 | 17.7.13 | OctetString | M,V | P | | | Y | +| MBMS-Time-To-Data-Transfer | 911 | 17.7.14 | OctetString | M,V | P | | | Y | +| MBMS-Session-Repetition-Number | 912 | 17.7.15 | OctetString | M,V | P | | | Y | +| MBMS-Required-QoS | 913 | 17.7.16 | UTF8String | M,V | P | | | Y | +| MBMS-Counting-Information | 914 | 17.7.17 | Enumerated | M,V | P | | | Y | +| MBMS-User-Data-Mode-Indication | 915 | 17.7.18 | Enumerated | M,V | P | | | Y | +| MBMS-GGSN-Address | 916 | 17.7.19 | OctetString | M,V | P | | | Y | +| MBMS-GGSN-IPv6-Address | 917 | 17.7.20 | OctetString | M,V | P | | | Y | +| MBMS-BMSC-SSM-IP-Address | 918 | 17.7.21 | OctetString | M,V | P | | | Y | +| MBMS-BMSC-SSM-IPv6-Address | 919 | 17.7.22 | OctetString | M,V | P | | | Y | +| MBMS-Flow-Identifier | 920 | 17.7.23 | OctetString | M,V | P | | | Y | +| CN-IP-Multicast-Distribution | 921 | 17.7.24 | Enumerated | M,V | P | | | Y | +| MBMS-HC-Indicator | 922 | 17.7.25 | Enumerated | M,V | P | | | Y | + +NOTE: The use of Radius VSA as a Diameter vendor AVP is described in Diameter NASREQ (IETF RFC 7155 [120]) and the P flag may be set. + +Table 11 lists the set of Diameter AVPs that are not Gmb specific, but are reused from other Diameter applications by the Gmb interface. A reference is done to the specifications where the AVPs are specified. This set of AVPs requires to be supported to be compliant to the present specification. + +**Table 11: Gmb reused AVPs from other Diameter applications.** + +| AVP Name | Reference | +|---------------------|-----------------------------| +| Called-Station-Id | NASREQ, IETF RFC 7155 [120] | +| Calling-Station-Id | NASREQ, IETF RFC 7155 [120] | +| Framed-Interface-Id | NASREQ, IETF RFC 7155 [120] | +| Framed-IP-Address | NASREQ, IETF RFC 7155 [120] | +| Framed-IPv6-Prefix | NASREQ, IETF RFC 7155 [120] | + +NOTE: Diameter Base AVPs are not listed as support of them is mandated by IETF RFC 6733 [111]. + +### 17.7.1 3GPP-Vendor-Specific AVP + +Void. + +### 17.7.2 TMGI AVP + +The TMGI AVP (AVP code 900) is of type OctetString, and contains the Temporary Mobile Group Identity allocated to a particular MBMS bearer service. It is allocated by the BM-SC. The encoding of TMGI is specified in 3GPP TS 24.008 [54]. When allocating the TMGI, BM-SC shall always include the MCC and MNC in the TMGI. + +### 17.7.3 Required-MBMS-Bearer-Capabilities AVP + +The Required-MBMS-Bearer-Capabilities AVP (AVP code 901) is of type UTF8String, and contains the minimum bearer capabilities the UE needs to support. The information contained in this AVP is UTF-8 encoded MBMS bearer capabilities as defined in 3GPP TS 24.008 [54]. + +### 17.7.4 Void + +### 17.7.5 MBMS-StartStop-Indication AVP + +The MBMS-StartStop-Indication AVP (AVP code 902) is of type Enumerated. The following values are supported: + +START (0) + +The message containing this AVP is indicating an MBMS session start procedure. + +STOP (1) + +The message containing this AVP is indicating an MBMS session stop procedure. + +UPDATE (2) + +The message containing this AVP is indicating an MBMS session update procedure. + +HEARTBEAT (3) + +The message containing this AVP is indicating an MBMS heartbeat procedure. + +## 17.7.6 MBMS-Service-Area AVP + +The MBMS-Service-Area AVP (AVP code 903) is of type OctetString, and indicates the area over which the MBMS bearer service has to be distributed. The AVP consists of the following parts: + +| Octet | | +|----------|-----------------------------------------------------------------------------------------------------------------| +| 1 | Number N of MBMS service area codes coded as:
1 binary value is '00000000'
256 binary value is '11111111' | +| 2-(2N+1) | A consecutive list of N MBMS service area codes | + +The MBMS service area code represents the coding for the MBMS Service Area Identity. + +The MBMS Service Area Identity and its semantics are defined in subclause 15.3 of 3GPP TS 23.003 [40]. + +The length of an MBMS service area code is 2 octets. + +Each MBMS service area code shall only be present once in the list. + +## 17.7.7 MBMS-Session-Duration AVP + +The MBMS-Session-Duration AVP (AVP code 904) is of type OctetString with a length of three octets and indicates the estimated session duration (MBMS Service data transmission). Bit 8 of octet 1 to bit 8 of octet 3 (17 bits) express seconds, for which the maximum allowed value is 86400 seconds. Bits 7 to 1 of octet 3 (7 bits) express days, for which the maximum allowed value is 18 days. The coding is as follows (the 's' bits represent the seconds, the 'd' bits represent the days): + +| Octets | Bits | | | | | | | | +|--------|------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | s | s | s | s | s | s | s | s | +| 2 | s | s | s | s | s | s | s | s | +| 3 | s | d | d | d | d | d | d | d | + +For the whole session duration the seconds and days are added together and the maximum session duration is 19 days. + +The lowest value of this AVP (i.e. all 0's), is reserved to indicate an indefinite value to denote sessions that are expected to be always-on. + +## 17.7.8 Alternative-APN AVP + +The Alternative-APN AVP (AVP code 905) is of type UTF8String, and contains the value of a new APN. This AVP is optional within the Gmb interface. BM-SC only includes it if the UE must use a different APN for the MBMS PDP Context from the one used in the Join message. + +## 17.7.9 MBMS-Service-Type AVP + +The MBMS-Service-Type AVP (AVP code 906) is of type Enumerated, and contains explicit information about the type of service that the BM-SC Start Procedure is about to start. + +MULTICAST (0) + +The Start Procedure signalled by the BM-SC is for a Multicast Service. + +BROADCAST (1) + +The Start Procedure signalled by the BM-SC is for a Broadcast Service. + +## 17.7.10 MBMS-2G-3G-Indicator AVP + +The MBMS-2G-3G-Indicator AVP (AVP code 907) is of type Enumerated. It indicates whether the MBMS bearer service will be delivered in 2G- only, 3G- only or both coverage areas. The following values are supported: + +2G (0) + +The MBMS bearer service shall only be delivered in 2G only coverage areas. + +3G (1) + +The MBMS bearer service shall only be delivered in 3G only coverage areas. + +2G-AND-3G (2) + +The MBMS bearer service shall be delivered both in 2G and 3G coverage areas. + +## 17.7.11 MBMS-Session-Identity AVP + +The MBMS-Session-Identity AVP (AVP code 908) is of type OctetString. Its length is one octet. It is allocated by the BM-SC. Together with TMGI it identifies a transmission of a specific MBMS session. The initial transmission and subsequent retransmissions of the MBMS session will use the same values of these parameters. This AVP is optional within the Gmb interface. + +## 17.7.12 RAI AVP + +The RAI AVP (AVP Code 909) is of type UTF8String, and contains the Routing Area Identity of the SGSN where the UE is registered. RAI use and structure is specified in 3GPP TS 23.003 [40]. + +Its value shall be encoded as a UTF-8 string on either 11 (if the MNC contains two digits) or 12 (if the MNC contains three digits) octets as follows: + +- The MCC shall be encoded first using three UTF-8 characters on three octets, each character representing a decimal digit starting with the first MCC digit. +- Then, the MNC shall be encoded as either two or three UTF-8 characters on two or three octets, each character representing a decimal digit starting with the first MNC digit. +- The Location Area Code (LAC) is encoded next using four UTF-8 characters on four octets, each character representing a hexadecimal digit of the LAC which is two binary octets long. +- The Routing Area Code (RAC) is encoded last using two UTF-8 characters on two octets, each character representing a hexadecimal digit of the RAC which is one binary octet long. + +NOTE: As an example, a RAI with the following information: MCC=123, MNC=45, LAC=41655(0xA2C1) and RAC=10(0x0A) is encoded within the RAI AVP as a UTF-8 string of "12345A2C10A". + +## 17.7.13 Additional-MBMS-Trace-Info AVP + +The Additional-MBMS-Trace-Info AVP (AVP Code 910) is of type OctetString. This AVP contains Trace Reference2, Trace Recording Session Reference, Triggering Events in BM-SC, Trace Depth for BM-SC, List of interfaces in BM-SC, Trace Activity Control For BM-SC which are all part of the Additional MBMS Trace Info IE as specified in TS 29.060 [24]. + +## 17.7.14 MBMS-Time-To-Data-Transfer AVP + +The MBMS-Time-To-Data-Transfer AVP (AVP code 911) is of type OctetString. Its length is one octet. It indicates the expected time between reception of the MBMS Session Start (RAR(Start) command) and the commencement of the MBMS Data flow. The coding is specified as per the Time to MBMS Data Transfer Value Part Coding of the Time to MBMS Data Transfer IE in 3GPP TS 48.018 [70]. + +## 17.7.15 MBMS-Session-Repetition-Number AVP + +The MBMS-Session-Repetition-Number AVP (AVP code 912) is of type OctetString with a length of one octet. It contains the session identity repetition number of the MBMS transmission session on the Gmb interface. The value 0 indicates the first transmission of a session. The values 1 to 255 represents the retransmission sequence number of a session. When the optional MBMS-Session-Identity AVP is included in the MBMS Session Start RAR (Start) command by the BM-SC, the BM-SC shall also provide the corresponding MBMS-Session-Repetition-Number AVP, and vice versa. + +## 17.7.16 MBMS-Required-QoS AVP + +The MBMS-Required-QoS AVP (AVP code 913) is the quality of service required for the MBMS bearer service. It is specified as UTF8String with the following encoding: + +| Octet | | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Allocation/Retention Priority as specified in 3GPP TS 23.107 [71]. This octet encodes each priority level defined in 3GPP TS 23.107 [71] as the binary value of the priority level. It specifies the relative importance of the actual MBMS bearer service compared to other MBMS and non-MBMS bearer services for allocation and retention of the MBMS bearer service. | +| 2-N | QoS Profile as specified by the Quality-of-Service information element, from octet 3 onwards, in 3GPP TS 24.008 [54]. | + +## 17.7.17 MBMS-Counting-Information AVP + +The MBMS-Counting-Information AVP (AVP code 914) is of type Enumerated, and contains explicit information about whether the MBMS Counting procedures are applicable for the MBMS Service that is about to start. See 3GPP TS 25.346 [72]. + +This AVP is only valid for UTRAN access type. + +The following values are supported: + +### COUNTING-NOT-APPLICABLE (0) + +The MBMS Session Start Procedure signalled by the BM-SC is for a MBMS Service where MBMS Counting procedures are not applicable. + +### COUNTING-APPLICABLE (1) + +The MBMS Session Start Procedure signalled by the BM-SC is for a MBMS Service where MBMS Counting procedures are applicable. + +## 17.7.18 MBMS-User-Data-Mode-Indication AVP + +The MBMS-User-Data-Mode-Indication AVP (AVP code 915) is of type Enumerated. The meaning of the message containing this AVP depends on the sending entity. The absence of this AVP indicates unicast mode of operation. + +The following values are supported: + +### Unicast (0) + +When BM-SC sends this value, that indicates to GGSN that BM-SC supports only unicast mode (IP multicast packets encapsulated over UDP by IP unicast header). + +When GGSN sends this value, that indicates to BM-SC that BM-SC shall send user plane data with unicast mode (IP multicast packets encapsulated over UDP by IP unicast header). + +### Multicast and Unicast (1) + +When BM-SC sends this value, that indicates to GGSN that BM-SC supports both modes of operation. + +When GGSN sends this value, that indicates to BM-SC that BM-SC shall send user plane data with multicast mode. + +### 17.7.19 MBMS-GGSN-Address AVP + +The MBMS-GGSN-Address AVP (AVP code 916) is of type OctetString, and contains the value of GGSN's IPv4 address for user plane data. IPv4 only or dual stack GGSN includes this AVP in case BM-SC requests GGSN's user plane unicast address. + +### 17.7.20 MBMS-GGSN-IPv6-Address AVP + +The MBMS-GGSN-IPv6-Address AVP (AVP code 917) is of type OctetString, and contains the value of GGSN's IPv6 address for user plane data. Dual stack GGSN includes this AVP in case BM-SC requests GGSN's user plane unicast address. + +### 17.7.21 MBMS-BMSC-SSM-IP-Address AVP + +The MBMS-BMSC-SSM-IP-Address AVP (AVP code 918) is of type OctetString, and contains the value of BM-SC's IPv4 address for Source Specific Multicasting. IPv4 only or dual stack BM-SC includes this AVP. + +### 17.7.22 MBMS-BMSC-SSM-IPv6-Address AVP + +The MBMS-BMSC-SSM-IPv6-Address AVP (AVP code 919) is of type OctetString, and contains the value of BM-SC's IPv6 address for Source Specific Multicasting. Dual stack BM-SC includes this AVP. + +### 17.7.23 MBMS-Flow-Identifier AVP + +The MBMS-Flow-Identifier AVP (AVP code 920) is of type OctetString. Its length is two octets. It represents a location dependent subflow of a broadcast MBMS bearer service. When present, the MBMS-Flow-Identifier together with the TMGI uniquely identify an MBMS Bearer Context. + +### 17.7.24 CN-IP-Multicast-Distribution AVP + +CN-IP-Multicast-Distribution AVP (AVP code 921) is of type Enumerated. It represents an indication if IP multicast distribution to UTRAN should be used for the MBMS user plane data. The following values are supported: + +NO-IP-MULTICAST (0) + +Value 0 indicates that IP multicast distribution of MBMS user plane data to UTRAN shall not be used. + +IP-MULTICAST (1) + +Value 1 indicates that MBMS user plane data to UTRAN should be delivered by IP multicast mechanism. + +### 17.7.25 MBMS-HC-Indicator AVP + +MBMS-HC-Indicator AVP (AVP code 922) is of type Enumerated. It represents an indication if header compression is used by BM-SC when sending for MBMS user plane data. The enumeration values are defined in 3GPP TS 25.413 [92]. + +## 17.7a Gmb re-used AVPs + +Table 17.7a.1 lists the Diameter AVPs re-used by the Gmb reference point from other existing Diameter Application, reference to their respective specifications and short description of their usage within the Gmb reference point. Other AVPs from existing Diameter Applications, except for the AVPs from Diameter base protocol, do not need to be supported. The AVPs from Diameter base protocol are not included in table 17.7a.1, but they are re-used for the Gmb reference point. Unless otherwise stated, re-used AVPs shall maintain their 'M', 'P' and 'V' flag settings. Where RADIUS VSAs are re-used, they shall be translated to Diameter AVPs as described in IETF RFC 7155 [120] with the exception that the 'M' flag shall be set and the 'P' flag may be set. + +**Table 17.7a.1: Gmb re-used Diameter AVPs** + +| Attribute Name | Reference | Description | +|------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------| +| MBMS-GW-UDP-Port | Clause 20.5a.5 | A transport layer UDP port allocated at the GGSN to receive multicast datagrams encapsulated in unicast IP/UDP encapsulation. | + +## 17.8 Gmb specific Experimental-Result-Code AVP values + +### 17.8.0 General + +There are two different types of errors in Diameter; protocol and application errors. A protocol error is one that occurs at the base protocol level, those are covered in the Diameter Base IETF RFC 6733 [111] specific procedures. Application errors, on the other hand, generally occur due to a problem with a function specified in a Diameter application. + +Diameter Base IETF RFC 6733 [111] defines a number of Result-Code AVP values that are used to report protocol errors and how those are used. Those procedures and values apply for the present specification. + +Due to the Gmb specific AVPs, new applications errors can occur. The Gmb specific errors are described by the Experimental-Result-Code AVP in this clause, below. Note that according to IETF RFC 6733 [111], the Diameter node reports only the first error encountered and only one Result-Code AVP or one Experimental-Result AVP is included in the Diameter answer. + +### 17.8.1 Success + +Resulting codes that fall within the Success category are used to inform a peer that a request has been successfully completed. + +The Result-Code AVP values defined in Diameter Base IETF RFC 6733 [111] are applicable. + +### 17.8.2 Permanent Failures + +Errors that fall within the Permanent Failures category are used to inform the peer that the request failed, and should not be attempted again. + +The Result-Code AVP values defined in Diameter Base IETF RFC 6733 [111] are applicable. Also the following specific Gmb Experimental-Result-Code values are defined for permanent failures: + +#### DIAMETER\_ERROR\_START\_INDICATION (5120) + +This error covers the case when a MBMS Session Start procedure could not be performed due to some of the required session attributes that are necessary to activate the bearer resources are missing (QoS, MBMS Service Area...). The Failed-AVP AVP must contain the missing AVP. + +#### DIAMETER\_ERROR\_STOP\_INDICATION (5121) + +An indication of session stop has been received with no session start procedure running. + +#### DIAMETER\_ERROR\_UNKNOWN\_MBMS\_BEARER\_SERVICE (5122) + +The requested MBMS service is unknown at the BM-SC. + +#### DIAMETER\_ERROR\_SERVICE\_AREA (5123) + +The MBMS service area indicated for a specific MBMS Bearer Service is unknown or not available. + +### 17.8.3 Transient Failures + +Errors that fall within the transient failures category are used to inform a peer that a request could not be satisfied at the time it was received, but it may be satisfied in the future. + +The Result-Code AVP values defined in Diameter Base IETF RFC 6733 [111] are applicable. Also the following specific Gmb Experimental-Result-Code value is defined for transient failures: + +DIAMETER\_ERROR\_OUT\_OF\_RESOURCES (4121) + +This error covers the case when a MBMS Session Start procedure could not be performed due to a temporary resource shortage in the GGSN. The BM-SC may re-try later. + +--- + +## 18 Usage of RADIUS at the Pk Reference Point + +### 18.1 General + +The Pk Reference Point is defined in 3GPP TS 23.141 [68] and allows the GGSN to report presence relevant events to the Presence Network Agent (such as PDP context activation/de-activation). This reference point is implemented using the mechanisms for Accounting of the RADIUS interface on the Gi reference point as defined in Clause 16. + +### 18.2 Radius Profile for Pk Reference Point + +The RADIUS interface on Gi reference point as defined in Clause 16 is used for the Pk Reference Point as clarified in the Profile in this Clause. + +Only the following messages are required for the Radius Profile for the Pk reference Point: + +- Accounting-Request START +- Accounting-Response START +- Accounting-Request STOP +- Accounting-Response STOP + +For the Radius Profile for the Pk Reference Point, only the mandatory Parameters within the Accounting-Request START and Accounting-Request STOP messages according to Clauses 16.4.3 and 16.4.4, respectively, and the Parameter "Calling-Station-Id" need to be supported. The usage of other parameters is optional. They may be ignored by the Presence Network Agent. + +### 18.3 Interconnecting the Presence Network Agent and the GGSN + +The Presence Network Agent may be directly attached to the GGSN or via a Radius Proxy. + +If the GGSN needs to connect both to an AAA server and a Presence Network Agent for the same APN, but supports only a single RADIUS interface, the GGSN can be directly attached to the AAA server. The Presence Network Agent can in turn be attached to the AAA server, which acts as a RADIUS proxy. If the AAA server is configured as a RADIUS Proxy between the Presence Network Agent and the GGSN, the Radius Profile for the Pk Reference Point shall be applicable on the interface between the Presence Network Agent and the AAA server. + +# 19 Usage of Diameter on Mz interface + +## 19.1 Introduction + +3GPP TS 23.246 [65] specifies that when MBMS bearers are used to provide MBMS user services to roaming users, three specific scenarios are used. + +One uses a GGSN in the Home PLMN, which is not related to Mz interface. The other two are enabled by use of the Mz interface for multicast services and are further described below. + +Mz is the roaming variant of the Gmb reference point with the same functionality as described under Gmb, i.e. with MBMS bearer and user specific signalling. The support of Mz with in BM-SC is needed for MBMS roaming scenario. Mz interface is defined between the visited BM-SC and the home BM-SC. + +MBMS bearer and user specific Mz signalling is used between a BM-SC in the visited PLMN and a BM-SC in the home PLMN when MBMS services from the home PLMN are offered by the visited PLMN. + +User specific signalling is used between a BM-SC in the visited PLMN and a BM-SC in the home PLMN when the visited PLMN offers MBMS user service to roaming users. This user specific Mz signalling provides home PLMN authorisation for MBMS user service that are provided by the visited PLMN. + +Mz may use proxy capabilities as described for Gmb, e.g. to proxy signalling between BM-SCs. + +## 19.2 Call flows in roaming scenarios + +The procedures described in clause 17 of the present specification: Session Start procedure (clause 17.5.2), Session Stop procedure (clause 17.5.3), Registration procedure (clause 17.5.4), De-registration procedure (GGSN initiated) (clause 17.5.5), De-registration procedure (BM-SC initiated) (clause 17.5.6), Trace Session Activation procedure (clause 17.5.8), Trace Session Deactivation procedure (clause 17.5.9), MBMS UE Context Modification procedure (clause 17.5.10), and Session Update procedure (clause 17.5.11) work exactly the same in roaming scenarios, i.e. when the GGSN is in a visited PLMN and the BM-SC is in the home PLMN, and they are Gmb procedures only and are not needed over Mz interface. + +Service activation procedures and Service deactivation procedures are the only procedures over Mz interface, and are described in detail in the following subclauses. + +### 19.2.1 Service activation + +#### 19.2.1.1 Service Provided by the BM-SC in Home PLMN + +A visited PLMN may offer to roaming users MBMS user services from their home PLMN. For this case, the PDP connection, which will be used for the JOIN step, may be from the UE to the visited GGSN due to operator policy or routing optimization. Then the authorization is done in the BM-SC in visited PLMN with the authorization information retrieved from the BM-SC in home PLMN. + +Whether GGSN of home or visited PLMN would be used is based on the operator policy, or agreement between PLMNs. + +The MBMS user traffic is provided by the BM-SC in home PLMN and proxied. + +![Sequence diagram showing the activation of an MBMS multicast service in a roaming scenario. The diagram involves four main entities: Visited GGSN, BM-SC in Visited PLMN, BM-SC in Home PLMN, and GGSN. The process starts with an IGMP/MLD Join Message to the Visited GGSN. The Visited GGSN sends an AA-Request [user/service] to the BM-SC in Visited PLMN. The BM-SC in Visited PLMN sends an AA-Request [user/service] to the BM-SC in Home PLMN. The BM-SC in Home PLMN sends an AA-Answer [user/service] back to the BM-SC in Visited PLMN. The BM-SC in Visited PLMN sends an AA-Answer [user/service] back to the Visited GGSN. A dashed box labeled 'User Authorization' groups the AA-Request and AA-Answer messages between the two BM-SCs. Next, a 'Create MBMS Ctxt' message is sent to the GGSN. The GGSN sends an AA-Request [user/service] to the BM-SC in Home PLMN. The BM-SC in Home PLMN sends an AA-Answer [user/service] back to the GGSN. Another dashed box labeled 'User Authorization' groups the AA-Request and AA-Answer messages between the GGSN and the BM-SC in Home PLMN.](c15cb6383bc35906e6b3c7c3aac621ed_img.jpg) + +``` + +sequenceDiagram + participant Visited GGSN + participant BM-SC in Visited PLMN + participant BM-SC in Home PLMN + participant GGSN + + Note left of Visited GGSN: IGMP/MLD Join Message + Visited GGSN->>BM-SC in Visited PLMN: 1. AA-Request [user/service] + BM-SC in Visited PLMN->>BM-SC in Home PLMN: 2. AA-Request [user/service] + Note right of BM-SC in Home PLMN: User Authorization + BM-SC in Home PLMN-->>BM-SC in Visited PLMN: 3. AA-Answer [user/service] + BM-SC in Visited PLMN-->>Visited GGSN: 4. AA-Answer [user/service] + + Note left of GGSN: Create MBMS Ctxt + GGSN->>BM-SC in Home PLMN: 5. AA-Request [user/service] + Note right of BM-SC in Home PLMN: User Authorization + BM-SC in Home PLMN-->>GGSN: 6. AA-Answer [user/service] + +``` + +Sequence diagram showing the activation of an MBMS multicast service in a roaming scenario. The diagram involves four main entities: Visited GGSN, BM-SC in Visited PLMN, BM-SC in Home PLMN, and GGSN. The process starts with an IGMP/MLD Join Message to the Visited GGSN. The Visited GGSN sends an AA-Request [user/service] to the BM-SC in Visited PLMN. The BM-SC in Visited PLMN sends an AA-Request [user/service] to the BM-SC in Home PLMN. The BM-SC in Home PLMN sends an AA-Answer [user/service] back to the BM-SC in Visited PLMN. The BM-SC in Visited PLMN sends an AA-Answer [user/service] back to the Visited GGSN. A dashed box labeled 'User Authorization' groups the AA-Request and AA-Answer messages between the two BM-SCs. Next, a 'Create MBMS Ctxt' message is sent to the GGSN. The GGSN sends an AA-Request [user/service] to the BM-SC in Home PLMN. The BM-SC in Home PLMN sends an AA-Answer [user/service] back to the GGSN. Another dashed box labeled 'User Authorization' groups the AA-Request and AA-Answer messages between the GGSN and the BM-SC in Home PLMN. + +**Figure 28: Activation of an MBMS multicast service in roaming scenario with service provided in the home PLMN** + +1. The GGSN sends an AAR to the BM-SC in visited PLMN seeking authorization for the activating roaming UE to receive data from a particular service. +2. The BM-SC in visited PLMN finds the BM-SC in home PLMN which will serve the roaming UE based on the multicast IP address, and identity of the user, and sends the AAR to it for the roaming UE to receive data from a particular service. +3. The authorization decision is provided from BM-SC in home PLMN in the AAA to BM-SC in visited PLMN. An APN may be included in the signalling between BM-SCs, which indicates a GGSN in home PLMN which will serve the UE for the specific MBMS service. The BM-SC in the visit network may modify the APN based on the operator policy or agreement between PLMNs. +4. The authorization decision, as received from BM-SC in home PLMN, is provided in the AAA to GGSN together with the APN to be used for creation of the MBMS UE Context If the AAA indicates that the roaming UE is not authorized to receive the MBMS data the process terminates with no additional message exchange. + +Whether GGSN of home or visited PLMN would be used is based on the operator policy, or agreement between PLMNs, for example, the visited BM-SC may modify the APN from the home BM-SC according to configuration of operator policy. + +5. The GGSN sends an AAR seeking authorization for the activating UE to BM-SC in home PLMN. This GGSN may be different from the GGSN that receives IGMP join message. +6. The authorization decision is provided in the AAA to GGSN. + +### 19.2.1.2 Service Provided by the BM-SC in visited PLMN + +When visited and home PLMN support the same classes of MBMS user services, a visited PLMN may offer its own MBMS user services to roaming users. In this case, the authorization is done in the BM-SC in visited PLMN with the authorization information retrieved from the BM-SC in home PLMN. Then the MBMS user traffic is provided by the BM-SC in visited PLMN. + +![Sequence diagram showing the activation of an MBMS multicast service in a roaming scenario with service provided in the visited PLMN. The diagram involves three main entities: Visited GGSN, BM-SC in Visited PLMN, and BM-SC in Home PLMN. The process starts with an IGMP/MLD Join Message from an external source to the Visited GGSN. The Visited GGSN then sends an AA-Request [user/service] to the BM-SC in Visited PLMN. The BM-SC in Visited PLMN sends an AA-Request [user/service] to the BM-SC in Home PLMN. The BM-SC in Home PLMN responds with an AA-Answer [user/service] to the BM-SC in Visited PLMN, which in turn sends an AA-Answer [user/service] to the Visited GGSN. A dashed box labeled 'User Authorization' groups the interaction between the two BM-SCs. Below this, a 'Create MBMS Ctxt' message is sent to the Visited GGSN. The Visited GGSN sends another AA-Request [user/service] to the BM-SC in Visited PLMN, which responds with an AA-Answer [user/service]. Another dashed box labeled 'User Authorization' groups this interaction.](2f108a589e99e93fd7aa8fac626398c7_img.jpg) + +``` + +sequenceDiagram + participant External + participant VisitedGGSN as Visited GGSN + participant BMSC_Visited as BM-SC in Visited PLMN + participant BMSC_Home as BM-SC in Home PLMN + + Note right of BMSC_Home: User Authorization + External->>VisitedGGSN: IGMP/MLD Join Message + VisitedGGSN->>BMSC_Visited: 1. AA-Request [user/service] + BMSC_Visited->>BMSC_Home: 2. AA-Request [user/service] + BMSC_Home-->>BMSC_Visited: 3. AA-Answer [user/service] + BMSC_Visited-->>VisitedGGSN: 4. AA-Answer [user/service] + + Note right of BMSC_Home: User Authorization + External->>VisitedGGSN: Create MBMS Ctxt + VisitedGGSN->>BMSC_Visited: 5. AA-Request [user/service] + BMSC_Visited-->>VisitedGGSN: 6. AA-Answer [user/service] + +``` + +Sequence diagram showing the activation of an MBMS multicast service in a roaming scenario with service provided in the visited PLMN. The diagram involves three main entities: Visited GGSN, BM-SC in Visited PLMN, and BM-SC in Home PLMN. The process starts with an IGMP/MLD Join Message from an external source to the Visited GGSN. The Visited GGSN then sends an AA-Request [user/service] to the BM-SC in Visited PLMN. The BM-SC in Visited PLMN sends an AA-Request [user/service] to the BM-SC in Home PLMN. The BM-SC in Home PLMN responds with an AA-Answer [user/service] to the BM-SC in Visited PLMN, which in turn sends an AA-Answer [user/service] to the Visited GGSN. A dashed box labeled 'User Authorization' groups the interaction between the two BM-SCs. Below this, a 'Create MBMS Ctxt' message is sent to the Visited GGSN. The Visited GGSN sends another AA-Request [user/service] to the BM-SC in Visited PLMN, which responds with an AA-Answer [user/service]. Another dashed box labeled 'User Authorization' groups this interaction. + +**Figure 29a: Activation of an MBMS multicast service in roaming scenario with service provided in the visited PLMN** + +1. The GGSN sends an AAR to the BM-SC in visited PLMN seeking authorization information for the activating roaming UE to receive data from a particular service. +2. The BM-SC in visited PLMN finds the BM-SC in home PLMN which have the authorization information for the roaming UE based on the multicast IP address, and identity of the user, and sends the AAR to it for the roaming UE to receive authorization from a particular service. +3. The authorization decision is provided from BM-SC in home PLMN in the AAA to BM-SC in visited PLMN. +4. The authorization decision, as received from BM-SC in home PLMN, is provided in the AAA to GGSN together with the APN to be used for creation of the MBMS UE Context If the AAA indicates that the roaming UE is not authorized to receive the MBMS data the process terminates with no additional message exchange. +5. The GGSN sends an AAR seeking authorization for the activating UE to BM-SC in visited PLMN. This GGSN may be different from the GGSN that receives IGMP join message. +6. The authorization decision is provided in the AAA to GGSN. + +## 19.2.2 Service deactivation + +### 19.2.2.1 Service Provided by the BM-SC in home PLMN + +![Sequence diagram for MBMS service deactivation in a roaming scenario. The diagram shows three main entities: GGSN, BM-SC in Visited PLMN, and BM-SC in Home PLMN. The process starts with a 'UE Leave indication' from the UE to the GGSN. The GGSN sends an 'ST-Request [user/service]' to the BM-SC in Visited PLMN. This BM-SC then sends an 'ST-Request [user/service]' to the BM-SC in Home PLMN. The Home PLMN BM-SC responds with an 'ST-Answer [user/service]' to the Visited PLMN BM-SC, which in turn sends an 'ST-Answer [user/service]' back to the GGSN. This sequence is grouped as 'User Leave'. Next, the GGSN sends a 'Delete MBMS Ctx Req.' to the BM-SC in Visited PLMN. The Visited PLMN BM-SC sends an 'ST-Request [user/service]' to the Home PLMN BM-SC, which responds with an 'ST-Answer [user/service]'. This second sequence is grouped as 'User Deactivation'.](cdcbafff3cef7d54a001e3d0a4d9841e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant GGSN + participant BM-SC_Visited as BM-SC in Visited PLMN + participant BM-SC_Home as BM-SC in Home PLMN + + Note right of BM-SC_Home: User Leave + UE->>GGSN: UE Leave indication + GGSN->>BM-SC_Visited: 1. ST-Request [user/service] + BM-SC_Visited->>BM-SC_Home: 2. ST-Request [user/service] + BM-SC_Home-->>BM-SC_Visited: 3. ST-Answer [user/service] + BM-SC_Visited-->>GGSN: 4. ST-Answer [user/service] + + Note right of BM-SC_Home: User Deactivation + GGSN->>BM-SC_Visited: Delete MBMS Ctx Req. + BM-SC_Visited->>BM-SC_Home: 5. ST-Request [user/service] + BM-SC_Home-->>BM-SC_Visited: 6. ST-Answer [user/service] + +``` + +Sequence diagram for MBMS service deactivation in a roaming scenario. The diagram shows three main entities: GGSN, BM-SC in Visited PLMN, and BM-SC in Home PLMN. The process starts with a 'UE Leave indication' from the UE to the GGSN. The GGSN sends an 'ST-Request [user/service]' to the BM-SC in Visited PLMN. This BM-SC then sends an 'ST-Request [user/service]' to the BM-SC in Home PLMN. The Home PLMN BM-SC responds with an 'ST-Answer [user/service]' to the Visited PLMN BM-SC, which in turn sends an 'ST-Answer [user/service]' back to the GGSN. This sequence is grouped as 'User Leave'. Next, the GGSN sends a 'Delete MBMS Ctx Req.' to the BM-SC in Visited PLMN. The Visited PLMN BM-SC sends an 'ST-Request [user/service]' to the Home PLMN BM-SC, which responds with an 'ST-Answer [user/service]'. This second sequence is grouped as 'User Deactivation'. + +**Figure 30a: Deactivation of an MBMS multicast service in roaming scenario with service provided in the home PLMN** + +1. Upon receiving the leave indication, the GGSN sends an STR to the BM-SC in visited PLMN, indicating that the roaming UE is requesting to leave the multicast service. The session to be terminate is uniquely identified by the Diameter session-id. +2. Upon reception of the STR, the BM-SC in visited PLMN finds the BM-SC in home PLMN which serves the roaming UE, and sends an STR to it for the roaming UE to deactivate a particular service. +3. Upon reception of the STR, the BM-SC in home PLMN verifies that the IP multicast address corresponds to a valid MBMS bearer service and responds the BM-SC in visited PLMN with an ST-Answer. The APN shall be the same that was provided during service activation. +4. Upon reception of the STA, the BM-SC in visited PLMN sends an STA to the GGSN that originated the Leave Indication. +5. The GGSN which is used to establish the MBMS bearer service deletes the MBMS UE Context and sends an STR to the BM-SC in home PLMN to confirm the successful deactivation of the MBMS UE Context. +6. The BM-SC in home PLMN then, deletes the MBMS UE Context and sends a confirmation to the GGSN in an STA message. + +## 19.2.2.2 Service Provided by the BM-SC in visited PLMN + +![Sequence diagram showing the deactivation of an MBMS multicast service in a roaming scenario. The diagram involves three main entities: Visited GGSN, BM-SC in Visited PLMN, and BM-SC in Home PLMN. The process starts with a 'UE Leave indication' to the Visited GGSN. The Visited GGSN sends an 'ST-Request [user/service]' to the BM-SC in Visited PLMN. This BM-SC then sends an 'ST-Request [user/service]' to the BM-SC in Home PLMN. The BM-SC in Home PLMN responds with an 'ST-Answer [user/service]' to the BM-SC in Visited PLMN, which in turn sends an 'ST-Answer [user/service]' to the Visited GGSN. A dashed box labeled 'User Leave' groups the messages between the Visited GGSN and the BM-SC in Visited PLMN. After a break in the sequence (indicated by double slashes), the Visited GGSN sends a 'Delete MBMS Ctxt Req.' to the BM-SC in Visited PLMN. The BM-SC in Visited PLMN sends an 'ST-Request [user/service]' to the BM-SC in Home PLMN, which responds with an 'ST-Answer [user/service]'. A dashed box labeled 'User Deactivation' groups the messages between the Visited GGSN and the BM-SC in Visited PLMN.](18b87e4ce7ef441f5620b8d6539a2939_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Visited GGSN + participant BM-SC in Visited PLMN + participant BM-SC in Home PLMN + + Note right of BM-SC in Home PLMN: User Leave + UE->>Visited GGSN: UE Leave indication + Visited GGSN->>BM-SC in Visited PLMN: 1. ST-Request [user/service] + BM-SC in Visited PLMN->>BM-SC in Home PLMN: 2. ST-Request [user/service] + BM-SC in Home PLMN-->>BM-SC in Visited PLMN: 3. ST-Answer [user/service] + BM-SC in Visited PLMN-->>Visited GGSN: 4. ST-Answer [user/service] + + Note right of BM-SC in Home PLMN: User Deactivation + Visited GGSN->>BM-SC in Visited PLMN: Delete MBMS Ctxt Req. + Visited GGSN->>BM-SC in Visited PLMN: 5. ST-Request [user/service] + BM-SC in Visited PLMN->>BM-SC in Home PLMN: 5. ST-Request [user/service] + BM-SC in Home PLMN-->>BM-SC in Visited PLMN: 6. ST-Answer [user/service] + BM-SC in Visited PLMN-->>Visited GGSN: 6. ST-Answer [user/service] + +``` + +Sequence diagram showing the deactivation of an MBMS multicast service in a roaming scenario. The diagram involves three main entities: Visited GGSN, BM-SC in Visited PLMN, and BM-SC in Home PLMN. The process starts with a 'UE Leave indication' to the Visited GGSN. The Visited GGSN sends an 'ST-Request [user/service]' to the BM-SC in Visited PLMN. This BM-SC then sends an 'ST-Request [user/service]' to the BM-SC in Home PLMN. The BM-SC in Home PLMN responds with an 'ST-Answer [user/service]' to the BM-SC in Visited PLMN, which in turn sends an 'ST-Answer [user/service]' to the Visited GGSN. A dashed box labeled 'User Leave' groups the messages between the Visited GGSN and the BM-SC in Visited PLMN. After a break in the sequence (indicated by double slashes), the Visited GGSN sends a 'Delete MBMS Ctxt Req.' to the BM-SC in Visited PLMN. The BM-SC in Visited PLMN sends an 'ST-Request [user/service]' to the BM-SC in Home PLMN, which responds with an 'ST-Answer [user/service]'. A dashed box labeled 'User Deactivation' groups the messages between the Visited GGSN and the BM-SC in Visited PLMN. + +**Figure 31a: Deactivation of an MBMS multicast service in roaming scenario with service provided in the visited PLMN** + +1. Upon receiving the leave indication, the GGSN sends an STR to the BM-SC in visited PLMN, indicating that the roaming UE is requesting to leave the multicast service. The session to be terminate is uniquely identified by the Diameter session-id. +2. Upon reception of the STR, the BM-SC in visited PLMN verifies that the IP multicast address corresponds to a valid MBMS bearer service and sends an STR to the BM-SC in home PLMN. +3. The BM-SC in home PLMN responds the BM-SC in visited PLMN with an ST-Answer. +4. Upon reception of the STA, the BM-SC in visited PLMN sends an STA to the GGSN that originated the Leave Indication. The APN shall be the same that was provided during service activation. +5. The GGSN deletes the MBMS UE Context and sends an STR to the BM-SC in visited PLMN to confirm the successful deactivation of the MBMS UE Context. +6. The BM-SC in visited PLMN, then, deletes the MBMS UE Context and sends a confirmation to the GGSN in an STA message. + +### 19.2.2.3 BM-SC in the home PLMN initiated multicast service deactivation + +This section defines the BM-SC in the home PLMN initiated multicast service deactivation procedure. + +![Sequence diagram for BM-SC in the home PLMN initiated MBMS multicast service deactivation procedure. The diagram shows three main entities: Visited GGSN, BM-SC in Visited PLMN, and BM-SC in Home PLMN. The sequence of messages is: 1. AS-Request [user/service] from Home PLMN to Visited PLMN; 2. AS-Request [user/service] from Visited PLMN to Visited GGSN; 3. AS-Answer [user/service] from Visited GGSN to Visited PLMN; 4. AS-Answer [user/service] from Visited PLMN to Home PLMN; 5. MBMS UE Context Deactivation Request from Visited GGSN to Visited PLMN. A bracket on the right side of the diagram, spanning steps 1 through 4, is labeled 'User Leave'.](8fce89f02626b8a0c50e2245bc3e7ce7_img.jpg) + +Sequence diagram for BM-SC in the home PLMN initiated MBMS multicast service deactivation procedure. The diagram shows three main entities: Visited GGSN, BM-SC in Visited PLMN, and BM-SC in Home PLMN. The sequence of messages is: 1. AS-Request [user/service] from Home PLMN to Visited PLMN; 2. AS-Request [user/service] from Visited PLMN to Visited GGSN; 3. AS-Answer [user/service] from Visited GGSN to Visited PLMN; 4. AS-Answer [user/service] from Visited PLMN to Home PLMN; 5. MBMS UE Context Deactivation Request from Visited GGSN to Visited PLMN. A bracket on the right side of the diagram, spanning steps 1 through 4, is labeled 'User Leave'. + +**Figure 32b: BM-SC in the home PLMN initiated MBMS multicast service deactivation procedure** + +1. The BM-SC in home PLMN sends an ASR to the BM-SC in visited PLMN, indicating that the UE shall be removed from a specific multicast service. The session to be terminated is uniquely identified by the Diameter session-id. +2. The BM-SC in the visited PLMN sends an ASR to the GGSN indicating that the UE shall be removed from the multicast service. The session to be terminated is uniquely identified by the Diameter session-id. +3. Upon reception of the ASR, the GGSN sends an ASA to the BM-SC in visited PLMN. +4. Upon reception of the ASA, the BM-SC in visited PLMN sends an ASA to the BM-SC in home PLMN. +5. Upon reception of the ASR in step 3, the GGSN sends an MBMS UE Context Deactivation Request to the SGSN. The IP multicast address, APN and IMSI together identify the MBMS UE Context to be deleted by the SGSN. + +Steps 5 and 6 of Figure 30a in section 19.2.2.1 follows in roaming scenarios where service was provided in the home PLMN. + +Steps 5 and 6 of Figure 31a in section 19.2.2.2 follows in roaming scenarios where service was provided in the visited PLMN. + +## 19.3 Mz messages + +This clause defines the Mz interface Diameter messages. + +The Diameter messages used in the Mz protocol, are the same as specified for Gmb interface described in Clause 17 of the present specification: AAR Command (clause 17.6.1), AAA Command (clause 17.6.2), STR Command (clause 17.6.3), STA Command (clause 17.6.4), Abort-Session-Request Command (clause 17.6.7) and Abort-Session-Answer Command (17.6.8). + +To route Diameter messages from the visited PLMN to the home PLMN, the BM-SC in the visited PLMN shall derive the realm of the home PLMN from the user's IMSI. The way to derive the realm of the home PLMN from IMSI is specified in 3GPP TS 23.003 [40] subclause 15.4. + +The derived realm of the home PLMN shall be filled in the Destination-Realm AVP of messages sent from the visited PLMN to the home PLMN, i.e. AAR command, STR command. + +## 19.4 Mz specific AVPs + +The Mz specific AVPs are the same as specified in Table 10 and Table 11. The Vendor-Id header of all Mz specific AVPs defined in the present specification shall be set to 3GPP (10415). + +## 19.5 Mz specific Experimental-Result-Code AVP values + +There are two different types of errors in Diameter; protocol and application errors. A protocol error is one that occurs at the base protocol level, those are covered in the Diameter Base IETF RFC 6733 [111] specific procedures. Application errors, on the other hand, generally occur due to a problem with a function specified in a Diameter application. + +Diameter Base IETF RFC 6733 [111] defines a number of Result-Code AVP values that are used to report protocol errors and how those are used. Those procedures and values apply for the present specification. + +Note that according to IETF RFC 6733 [111], the Diameter node reports only the first error encountered and only one Result-Code AVP or one Experimental-Result AVP is included in the Diameter answer. + +### 19.5.1 Success + +The success result codes specified in clause 17.8.1 of the present specification are applicable for Mz. + +### 19.5.2 Permanent Failures + +The Result-Code AVP values defined in Diameter Base IETF RFC 6733 [111] are applicable. Also the following specific Gmb Experimental-Result-Code value defined in clause 17.8.2 is applicable for Mz: + +DIAMETER\_ERROR\_UNKNOWN\_MBMS\_BEARER\_SERVICE (5122) + +The requested MBMS service is unknown at the BM-SC. + +### 19.5.3 Transient Failures + +Errors that fall within the transient failures category are used to inform a peer that a request could not be satisfied at the time it was received, but it may be satisfied in the future. + +The Result-Code AVP values defined in Diameter Base IETF RFC 6733 [111] are applicable. + +--- + +## 20 Usage of Diameter on SGmb interface + +### 20.1 General + +Signalling between MBMS GW and BM-SC is exchanged at SGmb reference point. + +The MBMS GW uses the SGmb interface: + +- to receive indication of session start, session update and session stop messages, which shall cause the MBMS GW, MME/SGSN and E-UTRAN/UTRAN to set up/tear down the appropriate resources for the service. For further details, see 3GPP TS 23.246 [65]; +- to enable the BM-SC and MBMS GW to detect an SGmb path failure or the restart of the peer MBMS node. For further details, see 3GPP TS 23.007 [104]. +- to enable the BM-SC to transfer the M1 interface information of local MBMS information. For further details, see 3GPP TS 23.285 [112]. + +NOTE: The localized MBMS architecture refers to Annex B of 3GPP TS 23.285 [112]. + +The SGmb application is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP () is 10415. The SGmb application identifier value assigned by IANA is 16777292. + +The SGmb application identifier value shall be included in the Auth-Application-Id AVP. + +The BM-SC and the MBMS GW shall advertise the support of the SGmb application by including the value of the application identifier in the Auth-Application-Id AVP and the value of the 3GPP (10415) in the Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands as specified in IETF RFC 6733 [111], i.e. as part of the Vendor-Specific-Application-Id AVP. The Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands are specified in the Diameter Base Protocol. + +## 20.2 MBMS session start / update/ stop + +The MBMS session start shall be used by the BM-SC to trigger the bearer resource establishment and announce the arrival of data for a MBMS bearer service (along with the attributes of the data to be delivered e.g. QoS, MBMS service area, or MBMS-Cell-List) to every MBMS GW that will deliver the MBMS bearer service. + +The MBMS session update shall be used by the BM-SC to trigger the update of MBMS session attributes in the affected MBMS GWs. The attributes that can be modified are the MBMS service area, the MBMS-Cell-List and the list of MBMS control plane nodes (MMEs, SGSNs). + +The MBMS session stop shall be used by the BM-SC to indicate the end of the data stream for an MBMS bearer service to every MBMS GW that has been delivering the MBMS bearer service. + +## 20.2A MBMS heartbeat + +The MBMS heartbeat procedure enables the BM-SC and MBMS GW to detect an SGmb path failure or the restart of the peer MBMS node, as specified in 3GPP TS 23.007 [104]. + +The use of this procedure shall be negotiated between the BM-SC and MBMS GW upon contacting the peer node for the first time. + +NOTE: The MBMS Heartbeat procedure however applies per (BM-SC, MBMS GW) pair, i.e. not per MBMS session. + +When this procedure is applied, the BM-SC and MBMS GW shall detect an SGmb path failure or the restart of the peer MBMS node as specified in clause 29 of 3GPP TS 23.007 [104]. + +The BM-SC and MBMS GW shall maintain a local restart counter which shall be incremented monotonically whenever the MBMS node restarts with loss of previous states. + +The MBMS heartbeat message shall include the Restart Counter AVP set to the local restart counter of the sending node. The Restart-Counter AVP may also be included in any other SGmb messages e.g. if contacting the peer node for the first time or if the local restart counter has been incremented. + +## 20.3 Message flows + +### 20.3.1 Session start procedure + +The BM-SC initiates the MBMS session start procedure when it is ready to send data. This informs the MBMS GW of the imminent start of the transmission and MBMS session attributes are provided to the MBMS GWs included in the list of downstream nodes in BM-SC. The bearer plane is allocated. + +BM-SC and MBMS GW shall at least support IP unicast encapsulation of IP multicast datagrams, which shall be default mode of sending user plane data. BM-SC may support IP multicast encapsulation of user plane IP multicast datagrams and MBMS GW also may support this mode of operation. + +![Sequence diagram of MBMS Session Start procedure. It shows two lifelines: MBMS GW and BM-SC. Step 1: BM-SC sends a RAR (Start) message to MBMS GW. Step 2: MBMS GW sends a RAA (Start) message to BM-SC.](e01c6273c4177746475715ee9c17a882_img.jpg) + +``` + +sequenceDiagram + participant BM-SC + participant MBMS_GW as MBMS GW + Note right of BM-SC: 1. RAR (Start) + BM-SC->>MBMS_GW: RAR (Start) + Note left of MBMS_GW: 2. RAA (Start) + MBMS_GW->>BM-SC: RAA (Start) + +``` + +Sequence diagram of MBMS Session Start procedure. It shows two lifelines: MBMS GW and BM-SC. Step 1: BM-SC sends a RAR (Start) message to MBMS GW. Step 2: MBMS GW sends a RAA (Start) message to BM-SC. + +**Figure 20.3.1.1: MBMS Session Start procedure** + +1. The BM-SC sends an RAR message to indicate the impending start of the transmission and to provide the session attributes to the MBMS GWs listed in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context. BM-SC may indicate to MBMS GW that BM-SC supports sending the user plane IP multicast data without IP unicast encapsulation. In such case BM-SC shall send multicast source address as specified by IETF RFC 4604 [73] and IETF RFC 4607 [74] and the user plane multicast destination address. + +If IP unicast mode is used, the BM-SC shall also require the MBMS GW to select one UDP port for the reception of the user plane data for the related MBMS service (identified by TMGI and Flow ID). + +The BM-SC may also indicate its intent to use IP multicast encapsulation of IP multicast datagrams across Sgi-mb. In this case, the BM-SC shall specify an Sgi-mb (transport) destination multicast IP address associated with the MBMS bearer context, as well as the source UDP port. The inclusion of these data shall mean IP multicast encapsulation of IP multicast datagram is the only offered multicast mode over Sgi-mb. The destination UDP port for IP multicast transport shall be fixed as port number 927. The BM-SC shall also specify the (transport) multicast source address. + +The BM-SC shall indicate the M1 interface information of local MBMS information as specified in 3GPP TS 23.285 [112] if the BM-SC determines to use the local MBMS information. + +2. The MBMS GW creates an MBMS Bearer Context, stores the session attributes in the MBMS Bearer Context, initiates session start procedure towards the MMEs/SGSNs in its list of MBMS control plane nodes and sends an RAA message to the BM-SC. In case MBMS GW receives BM-SC multicast source address, which indicates BM-SC support for both modes of sending user plane data, MBMS GW decides in which mode MBMS GW shall receive the user plane data. In case MBMS GW decides to receive unicast encapsulated data, then MBMS GW shall send own IP address for user plane to BM-SC and the MBMS GW shall also indicate the UDP port on which the user plane data shall be received. In case MBMS GW decides to receive IP multicast packets, then MBMS GW shall join the multicast group as specified by IETF RFC 4604 [73] and IETF RFC 4607 [74], and indicate to BM-SC about the decision. In case MBMS GW decides to use M1 interface information of local MBMS information, the MBMS GW skips the allocation procedure for IP multicast distribution. + +If configured, the MBMS GW sends the RAA message after receiving the first session start response (when positive) message from any MME. + +## 20.3.2 Session update procedure + +The BM-SC initiates the MBMS session update procedure when service attributes (e.g. Service Area, MBMS cell list, Access indicator or ARP) for an ongoing MBMS session shall be modified. The MBMS session update procedure is initiated towards one or more of the MBMS GWs in the list of downstream nodes in the BM-SC, according to the changes in the service area. + +**NOTE:** In addition, when the MBMS Service Area for an ongoing broadcast session is changed in the BM-SC, then MBMS GW(s) may be added to, or removed from, the list of downstream nodes in the BM-SC. The BM-SC will initiate MBMS session start procedures or MBMS session stop procedures towards these MBMS GWs accordingly. + +The attributes that can be modified by the RAR message are the MBMS Service Area, the MBMS-Cell-List, the ARP, the Access indicator and the list of MBMS control plane nodes (MMEs, SGSNs). + +When a session update message is received, the MBMS GW updates its MBMS Bearer Context accordingly and informs its downstream MMEs/SGSNs of the changed service attributes. If a list of MBMS control plane nodes (MMEs, SGSNs) is included in the session update message, MBMS GW shall initiate a session start procedure towards the new MMEs/SGSNs, and a session stop procedure towards the MMEs/SGSNs that have been removed from the list. + +![Sequence diagram for MBMS Session Update procedure](3adb4bad764bde2c7c001c4e7fed57ad_img.jpg) + +``` +sequenceDiagram + participant BM-SC + participant MBMS_GW as MBMS GW + Note right of BM-SC: 1. RAR (Update) + BM-SC->>MBMS_GW: RAR (Update) + Note left of MBMS_GW: 2. RAA (Update) + MBMS_GW->>BM-SC: RAA (Update) +``` + +The diagram shows a sequence of two messages between the BM-SC and the MBMS GW. The BM-SC sends a '1. RAR (Update)' message to the MBMS GW, and the MBMS GW responds with a '2. RAA (Update)' message. + +Sequence diagram for MBMS Session Update procedure + +**Figure 20.3.2.1: MBMS Session Update procedure** + +1. The BM-SC sends an RAR message to all MBMS GWs listed in the "list of downstream nodes" parameter of the affected MBMS Bearer Context to indicate that the MBMS session is updated. +2. The MBMS GW stores the new session attributes in the MBMS Bearer Context, initiates session start, session stop or session update procedure towards the MMEs/SGSNs in its list of MBMS control plane nodes and sends an RAA message to the BM-SC. An AAR message is not mandated for the SGmb application in response to an RAR- RAA command exchange. + +### 20.3.3 Session stop procedure + +The BM-SC initiates the MBMS session stop procedure when it considers the MBMS session terminated. Typically this will happen when there is no more MBMS data expected to be transmitted for a sufficiently long period of time to justify the release of bearer plane resources in the network. + +![Sequence diagram for MBMS Session Stop procedure](c879d6feb77f5e629e8feb3b42d5a139_img.jpg) + +``` +sequenceDiagram + participant BM-SC + participant MBMS_GW as MBMS GW + Note right of BM-SC: 1. RAR (Stop) + BM-SC->>MBMS_GW: RAR (Stop) + Note left of MBMS_GW: 2. RAA (Stop) + MBMS_GW->>BM-SC: RAA (Stop) +``` + +The diagram shows a sequence of two messages between the BM-SC and the MBMS GW. The BM-SC sends a '1. RAR (Stop)' message to the MBMS GW, and the MBMS GW responds with a '2. RAA (Stop)' message. + +Sequence diagram for MBMS Session Stop procedure + +**Figure 20.3.3.1: MBMS Session Stop procedure** + +1. The BM-SC sends an RAR message to all MBMS GWs listed in the "list of downstream nodes" parameter of the affected MBMS Bearer Context to indicate that the MBMS session is terminated and the bearer plane resources can be released. +2. The MBMS GW releases the resources regarding the session and sends an RAA message to the BM-SC. An AAR message is not mandated for the SGmb application in response to an RAR- RAA command exchange. + +### 20.3.4 MBMS session termination (MBMS GW initiated) + +![Sequence diagram for MBMS session termination](c0438093a10a593c42106b1e5dbb4331_img.jpg) + +``` +sequenceDiagram + participant MBMS GW + participant BM-SC + Note left of MBMS GW: 1. ST-Request [service] + MBMS GW->>BM-SC: 1. ST-Request [service] + Note right of BM-SC: 2. ST-Answer [service] + BM-SC-->>MBMS GW: 2. ST-Answer [service] +``` + +A sequence diagram showing the interaction between an MBMS GW and a BM-SC for session termination. The MBMS GW sends a message labeled '1. ST-Request [service]' to the BM-SC. The BM-SC responds with a message labeled '2. ST-Answer [service]' back to the MBMS GW. + +Sequence diagram for MBMS session termination + +**Figure 20.3.4.1: MBMS session termination** + +1. In exceptional cases (e.g. resource pre-emption or timeout of the MBMS session), the MBMS GW may send an STR command to the BM-SC to initiate the termination of the Diameter session related to an MBMS bearer service. If a bearer plane had been established over SGi-mb for this MBMS bearer service, the bearer plane is released. If the MBMS GW detects the SGi-mb path failure as specified in subclause 20.3.2.1 of 3GPP TS 23.007 [104], the MBMS GW shall set the Termination-Cause to "DIAMETER\_LINK\_BROKEN" (see IETF RFC 6733 [111]) and shall include the Diagnostic-Info AVP set to "User Plane Failure" if it tears down the MBMS session as a result of detecting an SGi-mb path failure. +2. The BM-SC removes the Diameter session and confirms the operation by sending an STA message to the MBMS GW. + +## 20.3.5 MBMS heartbeat procedure + +The BM-SC initiates the MBMS heartbeat procedure to detect a SGmb path failure or the restart of the MBMS GW as specified in 3GPP TS 23.007 [104]. + +![Sequence diagram for MBMS heartbeat procedure initiated by the BM-SC](7f950d8071cc74c5c726756baed72584_img.jpg) + +``` +sequenceDiagram + participant MBMS GW + participant BM-SC + Note right of BM-SC: 1. RAR (Heartbeat) + BM-SC-->>MBMS GW: 1. RAR (Heartbeat) + Note left of MBMS GW: 2. RAA (Heartbeat) + MBMS GW->>BM-SC: 2. RAA (Heartbeat) +``` + +A sequence diagram showing the interaction between a BM-SC and an MBMS GW for a heartbeat procedure initiated by the BM-SC. The BM-SC sends a message labeled '1. RAR (Heartbeat)' to the MBMS GW. The MBMS GW responds with a message labeled '2. RAA (Heartbeat)' back to the BM-SC. + +Sequence diagram for MBMS heartbeat procedure initiated by the BM-SC + +**Figure 20.3.5.1: MBMS Heartbeat procedure initiated by the BM-SC** + +1. The BM-SC sends an RAR message to the MBMS GW and indicates this is a heartbeat request. The BM-SC also includes the Restart-Counter AVP set to its local restart counter. +2. The MBMS GW sends an RAA message to the BM-SC to acknowledge the heartbeat request. The MBMS GW also includes the Restart-Counter AVP set to its local restart counter. + +The MBMS GW initiates the MBMS heartbeat procedure to detect a SGmb path failure or the restart of the BM-SC as specified in 3GPP TS 23.007 [104]. + +![Sequence diagram showing the MBMS Heartbeat procedure initiated by the MBMS GW. The diagram shows two lifelines: MBMS GW and BM-SC. Step 1: MBMS GW sends a RAR (Heartbeat) message to BM-SC. Step 2: BM-SC sends a RAA (Heartbeat) message back to MBMS GW.](0eb348bf17d67bf96326e07011d1c1ad_img.jpg) + +``` + +sequenceDiagram + participant MBMS GW + participant BM-SC + Note right of MBMS GW: 1. RAR (Heartbeat) + MBMS GW->>BM-SC: RAR (Heartbeat) + Note left of BM-SC: 2. RAA (Heartbeat) + BM-SC-->>MBMS GW: RAA (Heartbeat) + +``` + +Sequence diagram showing the MBMS Heartbeat procedure initiated by the MBMS GW. The diagram shows two lifelines: MBMS GW and BM-SC. Step 1: MBMS GW sends a RAR (Heartbeat) message to BM-SC. Step 2: BM-SC sends a RAA (Heartbeat) message back to MBMS GW. + +**Figure 20.3.5.2: MBMS Heartbeat procedure initiated by the MBMS GW** + +1. The MBMS GW sends an RAR message to the BM-SC and indicates this is a heartbeat request. The MBMS GW also includes the Restart-Counter AVP set to its local restart counter. +2. The BM-SC sends an RAA message to the MBMS GW to acknowledge the heartbeat request. The BM-SC also includes the Restart-Counter AVP set to its local restart counter. + +In the context of this procedure, the Diameter session shall be implicitly terminated, i.e. the client (server) shall behave as if the Auth-Session-State AVP was set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [111]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. + +NOTE: The Auth-Session-State AVP is not included in the RAR/RAA message as this is not permitted by the Diameter base protocol. See IETF RFC 6733 [111]. + +## 20.4 SGmb Messages + +This clause defines the SGmb interface Diameter message. + +The relevant AVPs that are of use for the SGmb interface are detailed in this clause. Other Diameter NASREQ (IETF RFC 7155 [120]) AVPs, even if their AVP flag rules is marked with "M", are not required for being compliant with the current specification. + +All SGmb specific AVPs for SGmb are needed to be compliant to the SGmb interface unless otherwise stated. + +### 20.4.1 Re-Auth-Request Command + +The Re-Auth-Request (RAR) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 258 and the message flags' 'R' bit set. + +The relevant AVPs that are of use for the SGmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for SGmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +The bold marked AVPs in the message format indicate new optional AVPs for SGmb, or modified existing AVPs. + +Message Format: + +``` + + ::= < Diameter Header: 258, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Destination-Host } + { Auth-Application-Id } + { Re-Auth-Request-Type } + [ Called-Station-Id ] + [ Framed-IP-Address ] + [ Framed-IPv6-Prefix ] + [ Framed-Interface-Id ] + [ MBMS-Access-Indicator ] + +``` + +``` + +[ MBMS-StartStop-Indication ] +[ MBMS-Service-Area ] +[ QoS-Information ] +[ MBMS-Session-Duration ] +[ MBMS-Session-Identity ] +[ MBMS-Session-Repetition-number ] +[ TMGI ] +* [ 3GPP-SGSN-Address ] +* [ 3GPP-SGSN-IPv6-Address ] +[ MBMS-Time-To-Data-Transfer ] +[ MBMS-Data-Transfer-Start ] +[ MBMS-Data-Transfer-Stop ] +[ MBMS-Flags ] +[ MBMS-User-Data-Mode-Indication ] +[ MBMS-BMSC-SSM-IP-Address ] +[ MBMS-BMSC-SSM-IPv6-Address ] +[ MBMS-Flow-Identifier ] +[ CN-IP-Multicast-Distribution ] +[ MBMS-HC-Indicator ] +[ MBMS-GW-UDP-Port-Indicator ] ; for IP unicast encapsulated user data +[ MBMS-GW-SSM-IP-Address ] ; for IP multicast encapsulated user data +[ MBMS-GW-SSM-IPv6-Address ] ; for IP multicast encapsulated user data +[ MBMS-BMSC-SSM-UDP-Port ] ; for IP multicast encapsulated user data +[ MBMS-Cell-List ] +[ Local-M1-Information ] +[ Origin-State-Id ] +* [ Proxy-Info ] +* [ Route-Record ] +* [ Supported-Features ] +[ Restart-Counter ] + +``` + +For the MBMS Session Start procedure, RAR is sent by the BM-SC to the MBMS GW(s) that will deliver the MBMS service when it is ready to send data. This is a request to activate all necessary bearer resources in the network for the transfer of MBMS data. The RAR message contains either an IPv4 address included in 3GPP-SGSN-Address AVP or an IPv6 address included in 3GPP-SGSN-IPv6-Address AVP for each participating MBMS control plane nodes (MMEs, SGSNs). The MBMS-Time-to-Data-Transfer AVP shall be included to indicate the expected time between the reception of the MBMS Session Start and the transmission of MBMS data flows. For E-UTRAN access, the RAR message may also contain the MBMS-Data-Transfer-Start AVP containing the absolute time stamp of the data delivery start. The RAR message shall also contain the MBMS-Service-Area AVP. If the MBMS Cell List feature is supported, or if the BM-SC does not yet know whether the MBMS-GW supports this feature, the RAR may contain the MBMS-Cell-List AVP. For the distributed MCE architectures, i.e. when the MCE is part of eNB as described in clause 15.1.1 in TS 36.300 [98], the MBMS-Data-Transfer-Start AVP should be used at MBSFN operation mode to ensure synchronized session control and to facilitate a graceful reallocation of resources for the MBSFN when needed. The RAR message shall also contain the Local-M1-Information AVP if the BM-SC determines to use the local MBMS information as specified in 3GPP TS 23.285 [112]. + +The MBMS-Flags AVP may provide specific control indications in relation to MBMS, e.g. whether the MBMS Session Start procedure is used to re-establish an MBMS session. + +For the MBMS Session Update procedure, RAR is sent by the BM-SC in order for the MBMS GW(s) to update their session attributes. If the MBMS service area or the MBMS cell list needs to be changed, the MBMS-Service-Area AVP shall be included in the RAR. If the MBMS Cell List feature is supported and the MBMS cell list needs to be changed, the MBMS-Cell-List AVP shall also be included. If the MBMS-Service-Area AVP but no MBMS-Cell-List AVP is included, this shall indicate that any MBMS Cell List included in a previous RAR does no longer apply. If the Access indicator needs to be updated, it shall be included in the MBMS-Access-Indicator AVP. For E-UTRAN access, the RAR message may also contain the MBMS-Data-Transfer-Start AVP containing the absolute time stamp of the data delivery start. For the distributed MCE architectures, i.e. when the MCE is part of eNB as described in clause 15.1.1 in TS 36.300 [98], the MBMS-Data-Transfer-Start AVP should be used at MBSFN operation mode to ensure synchronized session control and to facilitate a graceful reallocation of resources for the MBSFN when needed. The MBMS-StartStop-Indication AVP with the value UPDATE shall be included. The MBMS-Time-To-Data-Transfer AVP with the value set to 0 shall be included. The MBMS-Session-Duration AVP shall be included to indicate the duration of the remaining part of the MBMS session. The 3GPP-SGSN-Address AVP and the 3GPP-SGSN-IPv6-Address AVP shall be included if the related lists of MBMS control plane nodes (MMEs, SGSNs) in the MBMS GW(s) have changed. If the ARP needs to be changed, the QoS-Information AVP shall be included. The other bold marked AVPs shall be included as given by the previous, corresponding MBMS Session Start procedure. + +For the MBMS Session Stop procedure, RAR is sent by the BM-SC to the MBMS GW(s) when it considers the MBMS session to be terminated. The session is typically terminated when there is no more MBMS data expected to be transmitted for a sufficiently long period of time to justify a release of bearer plane resources in the network. For E- + +UTRAN access, the RAR message may also contain the MBMS-Data-Transfer-Stop AVP containing the absolute time stamp of the data delivery stop. The MBMS-Flags AVP may provide specific control indications, e.g. whether the MBMS Session Stop procedure is used to release the MBMS bearer context locally. + +For the MBMS Session Start procedure, the Qos-Information AVP indicates the QoS that is required for the MBMS bearer service for the actual MBMS session. Only the QoS-Class-Identifier AVP, Max-Requested-Bandwidth-DL AVP, Guaranteed-Bitrate-DL AVP and Allocation-Retention-Priority AVP within the QoS-Information AVP are applicable for the MBMS bearer service. The MBMS-Service-Area AVP is passed from BM-SC transparently through MBMS GW to the MMEs/SGSN(s) that are relevant for the actual MBMS bearer service. The MBMS-Cell-List AVP is also passed transparently through MBMS GW to the MMEs. The MBMS-Access-Indicator AVP indicates in which radio access types the MBMS bearer service shall be broadcasted, i.e. UTRAN, or E-UTRAN, or both. + +The usage of MBMS-StartStop-Indication AVP, Session-Id AVP, Framed-IP-Address AVP, Framed-IPv6-Prefix AVP, Framed-Interface-Id AVP, Called-Station-Id AVP and MBMS-Flow-Identifier AVP can refer to Gmb interface as described in clause 17.6.5. + +If unicast mode is used, the MBMS GW shall select an IP unicast address and a destination UDP port that is unique within the MBMS GW or that IP unicast address. + +If IP multicast encapsulation of application IP multicast datagram is used over Sgi-mb, the BM-SC shall select a source UDP port that is unique within the BM-SC for that IP multicast address. + +For the MBMS Heartbeat procedure, RAR is sent by the BM-SC to the MBMS GW, or vice-versa. The RAR message shall contain the following AVPs: + +- the MBMS-StartStop-Indication AVP set to the value "heartbeat"; +- the Restart-Counter AVP set to the local restart counter of the sender. + +## 20.4.2 RE-Auth-Answer Command + +The Re-Auth-Answer (RAA) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 258 and the message flags' 'R' bit clear, is sent in response to the RAR. + +The relevant AVPs that are of use for the SGmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for SGmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +The bold marked AVPs in the message format indicate new optional AVPs for SGmb, or modified existing AVPs. + +Message Format: + +``` + ::= < Diameter Header: 258, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + [ Result-Code ] + [ Experimental-Result ] + [ MBMS-StartStop-Indication ] + [ MBMS-GGSN-Address ] ; for unicast encapsulated user data + [ MBMS-GGSN-Ipv6-Address ] ; for unicast encapsulated user data + [ MBMS-User-Data-Mode-Indication ] + [ MBMS-GW-UDP-Port ] ; for unicast encapsulated user data + [ Origin-State-Id ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ Failed-AVP ] + * [ Redirected-Host ] + [ Redirected-Host-Usage ] + [ Redirected-Host-Cache-Time ] + [ Proxy-Info ] + * [ Supported-Features ] + [ Restart-Counter ] +``` + +For the MBMS Heartbeat procedure, RAA is sent by the BM-SC to the MBMS GW, or vice-versa. The RAA message shall contain the following AVPs: + +- the MBMS-StartStop-Indication AVP set to the value "heartbeat"; +- the Restart-Counter AVP set to the local restart counter of the sender. + +### 20.4.3 Session-Termination-Request Command + +A DIAMETER session may be terminated by the MBMS GW in exceptional cases. + +The relevant AVPs that are of use for the SGmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for SGmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +Message Format: + +``` + ::= < Diameter Header: 275, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Auth-Application-Id } + { Termination-Cause } + [ Destination-Host ] + * [ Class ] + [ Origin-State-Id ] + * [ Proxy-Info ] + * [ Route-Record ] + [ Diagnostic-Info ] + [ Restart-Counter ] +``` + +### 20.4.4 Session-Termination-Answer Command + +The STA command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code field set to 275 and the 'R' bit cleared in the Command Flags field, is sent in response to an STR command. + +The relevant AVPs that are of use for the SGmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for SGmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +Message Format: + +``` + ::= < Diameter Header: 275, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + * [ Class ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ Failed-AVP ] + [ Origin-State-Id ] + * [ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + * [ Proxy-Info ] + [ Restart-Counter ] +``` + +### 20.4.5 Abort-Session-Request Command + +The Abort-Session-Request (ASR) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 274 and the message flags' 'R' bit set, is sent by the BM-SC to the MBMS GW to request that the session identified by the Session-Id be stopped. + +The relevant AVPs that are of use for the SGmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for SGmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +Message Format + +``` + + ::= < Diameter Header: 274, REQ, PXY > + < Session-Id > + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Destination-Host } + { Auth-Application-Id } + [ Origin-State-Id ] + * [ Proxy-Info ] + * [ Route-Record ] + [ Restart-Counter ] + +``` + +## 20.4.6 Abort-Session-Answer Command + +The Abort-Session-Answer (ASA) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 274 and the message flags' 'R' bit clear, is sent in response to the ASR. + +The relevant AVPs that are of use for the SGmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for SGmb purposes and should be ignored by the receiver or processed according to the relevant specifications. + +### Message Format + +``` + + ::= < Diameter Header: 274, PXY > + < Session-Id > + { Result-Code } + { Origin-Host } + { Origin-Realm } + [ Origin-State-Id ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ Failed-AVP ] + * [ Redirected-Host ] + [ Redirected-Host-Usage ] + [ Redirect-Max-Cache-Time ] + * [ Proxy-Info ] + [ Restart-Counter ] + +``` + +## 20.5 SGmb re-used AVPs + +Table 20.5.1 lists the Diameter AVPs re-used by the SGmb reference point from the Gmb reference point and other existing Diameter Application, reference to their respective specifications and short description of their usage within the SGmb reference point. When reused from Gmb reference point, the specific clause in the present specification is referred. Other AVPs from existing Diameter Applications, except for the AVPs from Diameter base protocol, do not need to be supported. The AVPs from Diameter base protocol are not included in table 20.5.1, but they are re-used for the SGmb reference point. Where RADIUS VSAs are re-used, they shall be translated to Diameter AVPs as described in RFC 7155 [120] with the exception that the 'M' flag shall be set and the 'P' flag may be set. + +**Table 20.5.1 : SGmb re-used Diameter AVPs** + +| Attribute Name | Reference | Description | +|--------------------------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TMGI | 17.7.2 | Contains the Temporary Mobile Group Identity allocated to a particular MBMS bearer service. | +| MBMS-StartStop-Indication | 17.7.5 | Indicates the type of MBMS Session procedure. | +| MBMS-Service-Area | 17.7.6 | Indicates the area over which the MBMS bearer service has to be distributed. | +| MBMS-Session-Duration | 17.7.7 | Indicates the estimated session duration (MBMS Service data transmission). | +| MBMS-Session-Identity | 17.7.11 | Together with TMGI it identifies a transmission of a specific MBMS session. | +| MBMS-Time-To-Data-Transfer | 17.7.14 | Indicates the expected time between reception of the MBMS Session Start (RAR (Start) command) or the MBMS Session Update (RAR (Update) command) and the commencement of the MBMS Data flow. A value of 0 (1 sec.) shall be used in the Session Update. | +| MBMS-Session-Repetition-Number | 17.7.15 | Contains the session identity repetition number of the MBMS transmission session on the SGmb interface. | +| MBMS-User-Data-Mode-Indication | 17.7.18 | When sent from the BM-SC to the MBMS GW, it indicates the mode that BM-SC supports. When sent from the MBMS GW to the BM-SC, it indicates the mode that BM-SC shall send user plane data with.
Two modes apply:
- Unicast mode: IP multicast packets over UDP encapsulated by IP unicast header.
- Multicast mode: IP multicast packets encapsulated over UDP by IP multicast header. | +| MBMS-GGSN-Address | 17.7.19 | Contains the value of MBMS GW's IPv4 address for user plane data. | +| MBMS-GGSN-IPv6-Address | 17.7.20 | Contains the value of MBMS GW's IPv6 address for user plane data. | +| MBMS-BMSC-SSM-IP-Address | 17.7.21 | Contains the value of BM-SC's IPv4 address of Source Specific Multicasting. | +| MBMS-BMSC-SSM-IPv6-Address | 17.7.22 | Contains the value of BM-SC's IPv6 address of Source Specific Multicasting. | +| MBMS-Flow-Identifier | 17.7.23 | Represents a location dependent subflow of an MBMS bearer service. | +| CN-IP-Multicast-Distribution | 17.7.24 | Indicates if IP multicast distribution to UTRAN should be used for the MBMS user plane data. | +| MBMS-HC-Indicator | 17.7.25 | Indicates if header compression is used by BM-SC when sending for MBMS user plane data.(NOTE 1) | +| 3GPP-SGSN-Address | 16.4.7 | Represents the SGSN or MME's IPv4 address that is used by the GTP control plane for the handling of control messages. | +| 3GPP-SGSN-IPv6-Address | 16.4.7 | Represents the SGSN or MME's IPv6 address that is used by the GTP control plane for the handling of control messages. | +| Called-Station-Id | NASREQ, IETF RFC 7155 [120] | Contains the Access Point Name (APN) for which the MBMS bearer service is defined | +| Framed-Interface-Id | NASREQ, IETF RFC 7155 [120] | Contains the IPv6 interface identifier of the multicast address | +| Framed-IP-Address | NASREQ, IETF RFC 7155 [120] | Contains the IPv4 multicast address. | +| Framed-IPv6-Prefix | NASREQ, IETF RFC 7155 [120] | Contains the IPv6 prefix of the multicast address. | +| Local-M1-Information | 3GPP TS 29.468 [113] | Contains the M1 interface information of the local MBMS information, i.e., transport network IP Multicast Address, IP address of multicast source and C-TEID. | +| QoS-Information | 3GPP TS 29.212 [75] | Contains the QoS that is required for the MBMS bearer service for the MBMS session.
Only the QoS-Class-Identifier AVP, Max-Requested-Bandwidth-DL, Guaranteed-Bitrate-DL AVP and Allocation-Retention-Priority AVP within the QoS-Information AVP are applicable for the MBMS bearer service. | +| Supported-Features | 3GPP TS 29.229 [105] | If present, this AVP informs the destination host about the features that the origin host requires to successfully complete this command exchange | + +| Attribute Name | Reference | Description | +|-----------------------------------------------------------------------|-----------|-------------| +| NOTE 1: Header Compression only supported for UTRAN for this Release. | | | + +## 20.5a SGmb specific AVPs + +Table 20.5a.1 describes the SGmb specific Diameter AVPs. The Vendor-Id header of all SGmb specific AVPs defined in the present specification shall be set to 3GPP (10415). + +The SGmb specific AVPs require to be supported to be compliant with the present specification. All AVPs in table 20.5a.1 are mandatory within SGmb interface unless otherwise stated. + +**Table 20.5a.1: SGmb specific AVPs** + +| Attribute Name | AVP Code | Section defined | Value Type | AVP Flag rules | | | | May Encr. | Applicability (NOTE) | +|----------------------------|----------|-----------------|-------------|----------------|-----|------------|----------|-----------|----------------------| +| | | | | Must | May | Should not | Must not | | | +| MBMS-Access-Indicator | 923 | 20.5a.1 | Enumerated | M.V | P | | | Y | | +| MBMS-GW-SSM-IP-Address | 924 | 20.5a.2 | OctetString | V | P | | M | Y | | +| MBMS-GW-SSM-IPv6-Address | 925 | 20.5a.3 | OctetString | V | P | | M | Y | | +| MBMS-BMSC-SSM-UDP-Port | 926 | 20.5a.4 | OctetString | V | P | | M | Y | | +| MBMS-GW-UDP-Port | 927 | 20.5a.5 | OctetString | V | P | | M | Y | | +| MBMS-GW-UDP-Port-Indicator | 928 | 20.5a.6 | Enumerated | V | P | | M | Y | | +| MBMS-Data-Transfer-Start | 929 | 20.5a.7 | Unsigned64 | V | P | | M | Y | | +| MBMS-Data-Transfer-Stop | 930 | 20.5a.8 | Unsigned64 | V | P | | M | Y | | +| MBMS-Flag | 931 | 20.5a.9 | Unsigned32 | V | P | | M | Y | | +| Restart-Counter | 932 | 20.5a.10 | Unsigned32 | V | P | | M | Y | MBMS Heartbeat | +| Diagnostic-Info | 933 | 20.5a.11 | Unsigned32 | V | P | | M | Y | | +| MBMS-Cell-List | 934 | 20.5a.12 | OctetString | V | P | | M | Y | MBMS Cell List | + +NOTE: AVPs marked with a supported feature are applicable as described in subclause 20.7. + +### 20.5a.1 MBMS-Access-Indicator AVP + +The MBMS-Access-Indicator AVP (AVP code 923) is of type Enumerated. It indicates whether the MBMS bearer service will be delivered in UTRAN-only, E-UTRAN-only or both coverage areas. The following values are supported: + +UTRAN (0) + +The MBMS bearer service shall only be delivered in UTRAN only coverage areas. + +E-UTRAN (1) + +The MBMS bearer service shall only be delivered in E-UTRAN only coverage areas. + +UTRAN-AND-E-UTRAN (2) + +The MBMS bearer service shall be delivered both in UTRAN and E-UTRAN coverage areas. + +## 20.5a.2 MBMS-GW-SSM-IP-Address AVP + +The MBMS-GW-SSM-IP-Address AVP (AVP code 924) is of type OctetString and contains the Sgi-mb (transport) plane IPv4 destination multicast address used by BM-SC for IP multicast encapsulation of application IP multicast datagrams. + +## 20.5a.3 MBMS-GW-SSM-IPv6-Address AVP + +The MBMS-GW-SSM-IPv6-Address AVP (AVP code 925) is of type OctetString and contains the Sgi-mb (transport) plane IPv6 prefix of the destination multicast address used by BM-SC for IP multicast encapsulation of application IP multicast datagrams. + +## 20.5a.4 MBMS-BMSC-SSM-UDP-Port AVP + +The MBMS-BMSC-SSM-UDP-Port AVP (AVP code 926) is of type OctetString and contains the Sgi-mb (transport) plane source UDP port number at the BM-SC for IP multicast encapsulation of IP multicast datagrams. + +## 20.5a.5 MBMS-GW-UDP-Port AVP + +The MBMS-GW-UDP-Port AVP (AVP code 927) is of type OctetString, and contains the value of the UDP port from which the user plane data will be received in the MBMS-GW. + +## 20.5a.6 MBMS-GW-UDP-Port-Indicator AVP + +MBMS-GW-UDP-Port-Indicator AVP (AVP code 928) is of type Enumerated. It indicates that the payload related to the MBMS service is required to be delivered in the MBMS UDP Port assigned by the MBMS-GW. + +UDP-PORT-REQUIRED (1) + +Value 1 indicates that the user plane data corresponding to the MBMS service shall be delivered on the UDP Port provided by the MBMS-GW. + +## 20.5a.7 MBMS-Data-Transfer-Start AVP + +The MBMS-Data-Transfer-Start AVP (AVP code 929) is of type Unsigned64. + +This value indicates the time in seconds for the radio resources set up relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The fraction part is expressed with a granularity of $1/2^{32}$ second. + +This AVP is only valid for E-UTRAN access type. + +## 20.5a.8 MBMS-Data-Transfer-Stop AVP + +The MBMS-Data-Transfer-Stop AVP (AVP code 930) is of type Unsigned64. + +This value indicates the time in seconds for the release of resources relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The fraction part is expressed with a granularity of $1/2^{32}$ second. + +This AVP is only valid for E-UTRAN access type. + +## 20.5a.9 MBMS-Flags AVP + +The MBMS-Flags AVP (AVP code 931) is of type Unsigned32. It provides control indications. + +It shall contain a bit mask. The meaning of the bits shall be as defined in table 20.5a.9.1: + +**Table 20.5a.9.1 : MBMS-Flags** + +| Bit | Name | Description | +|------------------------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | MSRI | MBMS Session Re-establishment Indication :

This bit, when set, indicates that the MBMS Session Start Request message is used to re-establish an MBMS session (see 3GPP TS 23.007 [104]). | +| 1 | LMBCRI | Local MBMS Bearer Context Release Indication :

This bit, when set, indicates that the MBMS Session Stop Request message is used to locally release the MBMS bearer context in the MBMS-GW and in the associated MME/SGSNs (see 3GPP TS 23.007 [104]). | +| NOTE: Bits not defined in this table shall be cleared by the sending BM-SC and ignored by the receiving MBMS GW. | | | + +## 20.5a.10 Restart-Counter AVP + +The Restart-Counter AVP (AVP code 932) is of type Unsigned32. This is a monotonically increasing value that is advanced whenever the MBMS entity restarts with loss of previous state, for example upon restart. The Restart-Counter AVP may be included in any Diameter message over the SGmb reference point, including CER/CEA. + +## 20.5a.11 Diagnostic-Info AVP + +The Diagnostic-Info AVP (AVP code 933) is of type Unsigned32. + +It shall contain a bit mask. The meaning of the bits shall be as defined in table 20.5a.11.1: + +**Table 20.5a.11.1 : Diagnostic-Info** + +| Bit | Name | Description | +|------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | UPFAIL | User Plane Failure:

This bit, when set, indicates the detection of a User Plane Failure by the MBMS GW (see subclause 20.3.2.1 of 3GPP TS 23.007 [104]). | +| NOTE: Bits not defined in this table shall be cleared by the sending MBMS GW and ignored by the receiving BM-SC. | | | + +## 20.5a.12 MBMS-Cell-List AVP + +The MBMS-Cell-List AVP (AVP code 934) is of type OctetString. It contains the MBMS Cell List that the E-UTRAN uses to determine a set of radio resources to be used for the broadcast. Based on the cell ID list, the set of radio resources selected may be reduced from the full set of resources defined by the MBMS service area. + +The AVP shall consist of two octets indicating the number of cell identifiers in the list, followed by a sequence of maximum 4096 cell identifiers, coded as E-CGIs. + +| Bits | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------| +| 1-16 | Number N of ECGI codes coded as:
1 binary value is '0000 0000 0000 0000'

4096 binary value is '0000 1111 1111 1111' | +| 17-(56*N+16) | A consecutive list of N ECGI codes, each encoded according to subclause 8.21.5 of 3GPP TS 29.274 [81]. | + +The ECGI and its semantics are defined in subclause 19.6 of 3GPP TS 23.003 [40]. + +## 20.6 SGmb specific Experimental-Result-Code AVP values + +The same codes specified in clause 17.8 apply here except +DIAMETER\_ERROR\_UNKNOWN\_MBMS\_BEARER\_SERVICE (5122) + +## 20.7 Use of the Supported-Features AVP on the SGmb reference point + +The Supported-Features AVP is used during session establishment to inform the destination host about the required and optional features that the origin host supports. The client shall, in the first request in a Diameter session indicate the set of supported features. The server shall, in the first answer within the Diameter session indicate the set of features that it has in common with the client and that the server shall support within the same Diameter session. Any further command messages shall always be compliant with the list of supported features indicated in the Supported-Features AVPs during session establishment. Features that are not advertised as supported shall not be used to construct the command messages for that Diameter session. Unless otherwise stated, the use of the Supported-Features AVP on the SGmb reference point shall be compliant with the requirements for dynamic discovery of supported features and associated error handling on the Cx reference point as defined in clause 7.2.1 of 3GPP TS 29.229 [105]. + +The base functionality for the SGmb reference point is the 3GPP Rel-11 standard and a feature is an extension to that functionality. If the origin host does not support any features beyond the base functionality, the Supported-Features AVP may be absent from the SGmb commands. As defined in clause 7.1.1 of 3GPP TS 29.229 [105], when extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF. + +As defined in 3GPP TS 29.229 [105], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the SGmb reference point, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the SGmb reference point, the Feature-List-ID AVP shall differentiate those lists from one another. + +On receiving an initial request application message, the destination host shall act as defined in clause 7.2.1 of 3GPP TS 29.229 [105]. The following exceptions apply to the initial RAR/RAA command pair: + +- If the BM-SC supporting post-Rel-11 SGmb functionality is able to interoperate with a MBMS GW supporting Rel-11, the RAR shall include the features supported by the BM-SC within Supported-Features AVP(s) with the 'M' bit cleared. Otherwise, the RAR shall include the supported features within the Supported-Features AVP(s) with the M-bit set. + +NOTE 1: One instance of Supported-Features AVP is needed per Feature-List-ID. + +- If the RAR command does not contain any Supported-Features AVP(s) and the MBMS GW supports Rel-11 SGmb functionality, the RAA command shall not include the Supported-Features AVP. In this case, both BM-SC and MBMS GW shall behave as specified in the Rel-11 version of this document. +- If the RAR command contains the Supported-Features AVP, the MBMS GW shall include the Supported-Features AVP in the RAA command, with the 'M' bit cleared, indicating only the features that both the BM-SC and MBMS GW support. + +NOTE 2: The client will always declare all features that are supported according to table 20.7.1. When more than one feature identifying a release is supported by both BM-SC and MBMS GW, the BM-SC will work according to the latest common supported release. + +Once the BM-SC and MBMS GW have negotiated the set of supported features during session establishment, the set of common features shall be used during the lifetime of the Diameter session. + +The table below defines the features applicable to the SGmb interface for the feature list with a Feature-List-ID of 1. + +**Table 20.7.1: Features of Feature-List-ID 1 used in SGmb** + +| Feature bit | Feature | M/O | Description | +|-------------|----------------|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | MBMS Heartbeat | O | This feature indicates the support of the MBMS Heartbeat functionality, including the AVPs and corresponding procedures. | +| 1 | MBMS Cell List | O | This feature indicates the support of providing a MBMS-Cell-List AVP in the MBMS Session Start and MBMS Session Update procedures. For deployments with E-UTRAN access, this feature shall be supported. | + +Feature bit: The order number of the bit within the Feature-List AVP where the least significant bit is assigned number "0". + +Feature: A short name that can be used to refer to the bit and to the feature, e.g. "EPS". + +M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O") in this 3GPP Release. + +Description: A clear textual description of the feature. + +--- + +## Annex A (informative): Interworking PCS1900 with PSDNs + +Void. + +--- + +## Annex B (normative): Rate control related to Cellular Internet Of Things (CIoT) optimisations + +### B.1 General + +The present annex defines specific requirements for rate control related to CIoT optimisations. + +--- + +### B.2 Support of rate control of user data + +#### B.2.0 General + +The rate of user data sent to and from a UE (e.g. a UE using CIoT EPS Optimizations) can be controlled in two different ways: + +- Serving PLMN rate control +- APN rate control + +Serving PLMN rate control is further described in 3GPP TS 23.401 [77]. + +The APN rate control parameters are a part of the configuration data stored in the GGSN/PGW and is configured on per APN basis. + +APN rate control allows HPLMN operators on per APN and user to control the amount of user data sent DL and UL. This is done with help of policing user data on a maximum number of user data packets per time unit both DL and UL. APN rate control DL policing is done in the GGSN/PGW or the SCEF and the APN rate control policing UL is done in the UE. The GGSN/PGW or SCEF can also do APN rate control UL policing. + +For further information on APN rate control UL in the UE, see 3GPP TS 24.301 [84]. + +For further information on APN rate control in the SCEF, see 3GPP TS 29.128 [110]. + +NOTE: Existing AMBR mechanisms are not suitable for such a service since, for radio efficiency and UE battery life reasons, an AMBR of e.g. > 100kbit/s is desirable and such an AMBR translates to a potentially large daily data volume. + +#### B.2.1 APN Rate Control in the PGW + +To enable APN rate control it shall be configured in the PGW per APN. + +The APN rate control parameters, if configured, shall consist of: + +- the maximum number of DL user data packets per time unit, +- the maximum number of UL user data packets per time unit, +- an indication whether the UE is allowed to send additional exception reports when the limit for the UL APN rate control has been reached , and +- if UE supports it, the maximum number of additional UL exception reports per time unit. + +Possible time units shall be, minute, hour, day or week. + +If the UE does not indicate APN rate control support, the GGSN/PGW may refrain from providing APN rate control information to the UE. + +NOTE 1: The UE indicates support for APN rate control with help of an indicator in the Protocol Configuration Options IE (PCO IE) or the Extended Protocol Configuration Options IE (ePCO IE), see 3GPP TS 24.008 [54] or 3GPP TS 24.301 [84] for IE definition. The APN rate control indicator within the PCO/ePCO IE is received at IP-CAN session establishment. + +NOTE 2: The UE and network support of the ePCO IE, is indicated with help of the Indication IE. The ePCO support indication within the Indication IE can be received at IP-CAN session establishment or at IP-CAN session modification. See 3GPP TS 29.274 [81] for IE definition. + +If the APN rate control is supported by the UE and the Indication IE is received indicating support of ePCO IE at the IP-CAN session establishment request and the PGW supports the ePCO IE, the PGW shall in the reply, if configured for the APN used, include APN UL rate control parameters in the ePCO IE, see 3GPP TS 24.008 [54] for IE definition. If the ePCO IE is not supported the PGW shall use the PCO IE. + +The GGSN shall use the PCO IE. + +If the APN rate control UL parameter(s) is modified and the ePCO IE is supported, the PGW shall initiate an IP-CAN session modification procedure and include the APN UL rate control parameters in the ePCO IE. + +If the ePCO IE is not supported the PGW shall use the PCO IE. + +The GGSN shall use the PCO IE. + +The GGSN/PGW shall enforce the APN rate control per UE and APN according to the configuration for DL and may enforce APN rate control for UL, e.g. when the PGW have indicated to the UE that the UE is not allowed to send exception reports when the limit for the UL APN rate control has been reached. + +NOTE 3: The UE locally enforces this uplink APN rate control instruction. The UE considers this APN rate control instruction as valid until it receives a new one from the GGSN/PGW. + +## B.2.2 Serving PLMN Rate Control information handling in the PGW + +If Serving PLMN rate control information is received in the Serving PLMN Rate Control IE from the MME, the PGW shall store this information and use that for rate control enforcement DL for this UE. + +If the PGW previously have received Serving PLMN rate control information, the PGW shall behave as follows: + +- If the PGW receives new Serving PLMN rate control information in the Serving PLMN Rate Control IE from the MME, the PGW shall replace the old Serving PLMN rate control information with the new Serving PLMN rate control information and use that for rate control enforcement DL for this UE. +- If the PGW receives no Serving PLMN rate control information in the Serving PLMN Rate Control IE from the MME in an IP-CAN session establishment or an IP-CAN session modification , the PGW shall still consider the latest received Serving PLMN rate control information from the MME as valid. +- If PGW receives an indication that Serving PLMN rate control does not apply in the Serving PLMN Rate Control IE, the PGW shall remove the rate control information based on Serving PLMN rate control information. + +See 3GPP TS 29.274 [81] for Serving PLMN Rate Control IE definition. + +APN rate control, if configured, also applies for the same IP-CAN session, see subclause B.2.1. + +--- + +## Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2015-03 | CT#67 | CP-150126 | 0444 | 2 | | Paging policy differentiation for IMS voice | 13.0.0 | +| 2015-09 | CT#69 | CP-150464 | 0450 | 1 | A | Usage of the UDP port for default unicast encapsulation mode at the SGmb interface is required to support SYNC protocol. | 13.1.0 | +| 2015-09 | CT#69 | CP-150468 | 0453 | | A | 3GPP Type of RADIUS 3GPP-User-Location-Info-Time sub-attribute | 13.1.0 | +| 2015-09 | CT#69 | CP-150472 | 0455 | 1 | A | Correction of SGmb L4 Transport protocol | 13.1.0 | +| 2015-12 | CT#70 | CP-150658 | 0456 | 1 | B | MBMS bearer establishment and update with cell ID list | 13.2.0 | +| 2015-12 | CT#70 | CP-150669 | 0459 | 1 | A | Transport protocols of Diameter for signalling plane of non transparent case | 13.2.0 | +| 2016-03 | CT#71 | CP-160108 | 0460 | | B | Support for Non-IP data for CIoT over Sgi | 13.3.0 | +| 2016-03 | CT#71 | CP-160089 | 0465 | 2 | B | Usage of the UDP port for default unicast encapsulation mode at the Gmb interface is required to support SYNC protocol | 13.3.0 | +| 2016-06 | CT#72 | CP-160252 | 0466 | 1 | B | Support of Non-IP delivery data | 13.4.0 | +| 2016-06 | CT#72 | CP-160252 | 0469 | | B | RAT-Type extension for NB-IoT | 13.4.0 | +| 2016-06 | CT#72 | CP-160252 | 0471 | 1 | B | Non-IP Transport | 13.4.0 | +| 2016-06 | CT#72 | CP-160277 | 0472 | 1 | B | Support for rate control of CIoT datat | 13.4.0 | +| 2016-06 | CT#72 | CP-160281 | 0468 | 1 | B | Support of Non-IP delivery data | 14.0.0 | +| 2016-09 | CT#73 | CP-160441 | 0474 | 1 | A | PDP type extension with Non-IP value | 14.1.0 | +| 2016-09 | CT#73 | CP-160441 | 0476 | 1 | A | Support of Exception Reports for CIoT | 14.1.0 | +| 2016-09 | CT#73 | CP-160459 | 0477 | | B | APN rate control support in GPRS | 14.1.0 | +| 2016-09 | CT#73 | CP-160441 | 0479 | | A | APN rate control DL correction | 14.1.0 | +| 2016-09 | CT#73 | CP-160452 | 0480 | 2 | B | Modify the 3GPP-User-Location-Info to support eNB ID Information | 14.1.0 | +| 2016-12 | CT#74 | CP-160632 | 0481 | 1 | B | Local MBMS related MBMS data delivery | 14.2.0 | +| 2016-12 | CT#74 | CP-160613 | 0483 | 1 | A | Correction to SGi PTP tunnelling based on UDP/IP | 14.2.0 | +| 2016-12 | CT#74 | CP-160616 | 0484 | 1 | F | Diameter base protocol specification update | 14.2.0 | +| 2017-03 | CT#75 | CP-170076 | 0486 | 1 | F | Handling of Vendor-Specific-Application-Id AVP | 14.3.0 | +| 2017-03 | CT#75 | CP-170086 | 0487 | 1 | F | Support of long and short Macro eNodeB IDs | 14.3.0 | +| 2017-03 | CT#75 | CP-170075 | 0489 | 2 | A | Correction in APN rate control | 14.3.0 | +| 2017-03 | CT#75 | CP-170076 | 0492 | 1 | F | Update instance number for the Failed-AVP in answer commands | 14.3.0 | +| 2017-09 | CT#77 | CP-172052 | 0493 | | F | Correction of signalling server address request | 15.0.0 | +| 2017-09 | CT#77 | CP-172052 | 0496 | 1 | F | Correction for QoS modification in MBMS Update Request | 15.0.0 | +| 2017-12 | CT#78 | CP-173088 | 0498 | 2 | F | Rate control for MO exception data | 15.1.0 | +| 2017-12 | CT#78 | CP-173105 | 0499 | | B | Clarification for MBMS session start procedure | 15.1.0 | +| 2018-03 | CT#79 | CP-180049 | 0500 | | F | Addition of a note that input-packets / output-packets are not reported in SGi signalling with CUPS | 15.2.0 | +| 2018-06 | CT#80 | CP-181023 | 0501 | | B | Data Volume Reporting for Secondary RAT usage | 15.3.0 | +| 2018-06 | CT#80 | CP-181013 | 0502 | 2 | B | Updates to 3GPP-User-Location-Info AVP | 15.3.0 | +| 2018-06 | CT#80 | CP-181012 | 0503 | | B | Updates to 3GPP-PDP-Type AVP | 15.3.0 | +| 2018-06 | CT#80 | CP-181183 | 0504 | 3 | B | Updates to 3GPP-RAT-Type AVP | 15.3.0 | +| 2018-06 | CT#80 | CP-181012 | 0505 | 1 | B | Updates to 3GPP-GPRS-Negotiated-QoS-Profile AVP | 15.3.0 | +| 2018-06 | CT#80 | CP-181014 | 0506 | | F | Extended accounting octets for RADIUS | 15.3.0 | +| 2018-06 | CT#80 | CP-181023 | 0506 | | B | Differentiation of LTE-M (eMTC) | 15.3.0 | +| 2018-09 | CT#81 | CP-182015 | 0508 | | F | 3GPP-User-Location-Info AVP extension for 5G | 15.4.0 | +| 2018-09 | CT#81 | CP-182015 | 0509 | | F | Correction to 3GPP-GPRS-Negotiated-QoS-Profile AVP | 15.4.0 | +| 2018-12 | CT#82 | CP-183122 | 0510 | | F | Correct 3GPP-PDP-Type description in RADIUS VSA | 15.5.0 | +| 2020-06 | CT#88e | CP-201214 | 0511 | | F | Correct RAT type | 15.6.0 | +| 2020-06 | CT#88e | CP-201248 | 0511 | | F | Support secondary RAT data usage report | 16.0.0 | +| 2020-09 | CT#89e | CP-202060 | 0526 | | F | RAT Type extension for 5WWC | 16.1.0 | +| 2020-09 | CT#89e | CP-202078 | 0525 | | F | Corrections to Framed IPv6 | 17.0.0 | +| 2020-12 | CT#90e | CP-203144 | 0527 | | F | Corrections to IPv4 and IPv6 | 17.1.0 | +| 2020-12 | CT#90e | CP-203138 | 0529 | 1 | A | Corrections to Delegated-IPv6-Prefix | 17.1.0 | +| 2021-03 | CT#91e | CP-210216 | 0530 | | D | Correct figure number | 17.2.0 | +| 2021-06 | CT#92e | CP-211203 | 0533 | 1 | A | Correction to Framed IP | 17.3.0 | +| 2021-06 | CT#92e | CP-211233 | 0534 | | D | Editorial fix | 17.3.0 | +| 2021-06 | CT#92e | CP-211247 | 0535 | | B | Updates to support CUPS | 17.3.0 | +| 2021-06 | CT#92e | CP-211278 | 0536 | 3 | B | Updates to support L2TP for CUPS | 17.3.0 | +| 2021-06 | CT#92e | CP-211279 | 0537 | 2 | B | Updates to support L2TP in RADIUS message flow | 17.3.0 | +| 2021-06 | CT#92e | CP-211279 | 0538 | 2 | B | Updates to support L2TP in Diameter message flow | 17.3.0 | +| 2021-06 | CT#92e | CP-211212 | 0539 | 1 | B | Reporting UE local IP to Diameter DN-AAA server | 17.3.0 | +| 2021-06 | CT#92e | CP-211212 | 0540 | 1 | B | Reporting UE local IP to RADIUS DN-AAA server | 17.3.0 | +| 2021-06 | CT#92e | CP-211249 | 0541 | | D | Remove duplicated text for 3GPP-User-Location-Info | 17.3.0 | +| 2021-09 | CT#93e | CP-212197 | 0542 | | D | Fix L2TP procedure | 17.4.0 | +| 2021-09 | CT#93e | CP-212224 | 0543 | | D | Editorial fix for unrecognized word | 17.4.0 | +| 2021-09 | CT#93e | CP-212224 | 0544 | | F | Obsolete RFC4005 by RFC7155 | 17.4.0 | +| 2021-09 | CT#93e | CP-212197 | 0545 | | F | Fix editor notes for Tunnel-Password | 17.4.0 | +| 2021-12 | CT#94e | CP-213241 | 0547 | 1 | A | Correction of the applicability of the counted number of packets | 17.5.0 | +| 2021-12 | CT#94e | CP-213244 | 0548 | 1 | F | Clarification about the usage of Geographic Location Type values | 17.5.0 | +| 2022-03 | CT#95e | CP-220208 | 0549 | 1 | B | Update the 3GPP-RAT-Type AVP to support NR RedCap access type | 17.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------|--------| +| 2023-03 | CT#99 | CP-230175 | 0551 | 1 | F | P-GW setting DSCP | 18.0.0 | +| 2023-03 | CT#99 | CP-230174 | 0552 | | F | Format handling for 3GPP-User-Location-Info attribute | 18.0.0 | +| 2023-03 | CT#99 | CP-230174 | 0553 | | B | Updates on 3GPP-Packet-Filter | 18.0.0 | +| 2023-06 | CT#100 | CP-231133 | 0554 | | F | Handling of 3GPP User Location | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29108/raw.md b/marked/Rel-18/29_series/29108/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b111be9ebfa7a934ef0adef1a90a36ea4596ebd7 --- /dev/null +++ b/marked/Rel-18/29_series/29108/raw.md @@ -0,0 +1,431 @@ + + +# 3GPP TS 29.108 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Application of the Radio Access Network Application Part (RANAP) on the E-interface (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|------------------------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Abbreviations ..... | 5 | +| 4 Principles for the use of RANAP on the E-interface ..... | 6 | +| 4.1 General ..... | 6 | +| 4.2 Transfer of RANAP layer 3 messages on the E-interface..... | 6 | +| 4.3 Roles of 3G_MSC-A, 3G_MSC-I and 3G_MSC-T ..... | 6 | +| 5 Use of the RANAP on the E-interface ..... | 7 | +| 5.1 RAB Assignment..... | 7 | +| 5.2 RAB Release Request ..... | 7 | +| 5.3 Iu Release Request ..... | 8 | +| 5.4 Relocation Resource Allocation..... | 8 | +| 5.5 Relocation Cancel ..... | 8 | +| 5.6 Relocation Detect and Relocation Complete ..... | 8 | +| 5.7 CN Trace invocation ..... | 9 | +| 5.8 Security mode control ..... | 9 | +| 5.9 Location Reporting Control ..... | 9 | +| 5.10 Location Report..... | 9 | +| 5.11 Direct Transfer ..... | 9 | +| 5.12 Error Indication ..... | 10 | +| 5.13 CN Deactivate Trace ..... | 10 | +| 5.14 Common ID..... | 10 | +| 5.15 Location Related Data..... | 10 | +| 5.16 UE Specific Information ..... | 10 | +| 5.17 RAB Modification Request..... | 10 | +| 6 RANAP messages transferred on the E-interface ..... | 11 | +| 7 Exceptions for RANAP message contents and information element coding when transferred on the E-interface ..... | 12 | +| 7.1 Message Contents..... | 12 | +| 8 RANAP message error handling when transferred on the E-interface ..... | 12 | +| Annex A (informative): Change history..... | 13 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the subset of Radio Access Network Application Part (RANAP) messages and procedures, defined in 3GPP TS 25.413 [4], which is used on the E-interface. A general description can be found in 3GPP TS 23.002 [7] and 3GPP TS 23.009 [2]. + +For the initiation and execution of relocation of SRNS (relocation for short, throughout the whole document) between MSCs a subset of RANAP procedures are used. For the subsequent control of resources allocated to the User Equipment (UE) RANAP procedures are used. The Direct Transfer Elementary Procedure (EP) of RANAP, is used for the transfer of connection management and mobility management messages between the UE and the controlling 3G\_MSC. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary". +- [2] 3GPP TS 23.009: "Handover procedures". +- [3] Void +- [4] 3GPP TS 25.413: "UTRAN Iu Interface Radio Access Network Application Part (RANAP) signalling". +- [5] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [6] 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling procedures and the Mobile Application Part (MAP)". +- [7] 3GPP TS 23.002: "Network architecture". +- [8] Void + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations defined in TR 21.905 [1] and the following apply: + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------| +| 3G_MSC | A third generation Mobile services Switching Centre that supports the Iu interface (and possibly also the A-interface) | +| 3G_MSC-A | The controlling 3G_MSC on which the call was originally established | +| 3G_MSC-B | The 3G_MSC to which the UE is handed over in a Basic Handover | +| 3G_MSC-B' | The 3G_MSC to which the UE is handed over in a Subsequent Handover | +| 3G_MSC-I | Interworking 3G_MSC | +| 3G_MSC-T | Target 3G_MSC | +| EP | Elementary Procedure | +| NNSF | NAS Node Selection Function | +| RNC | Radio Network Controller | + +# 4 Principles for the use of RANAP on the E-interface + +## 4.1 General + +The mechanism for the transfer of the RANAP messages on the E-interface is defined in TS 29.002 [5]. The operation of the relocation procedures between 3G\_MSCs and the use of the RANAP messages for those procedures is described in TS 23.009 [2] and TS 29.010 [6]. + +RANAP is defined to connect the RNS to both, the cs and ps domain of an UMTS CN. Procedures, messages and IEs, only defined for communication between the RNS and the ps domain of an UMTS CN will, of course, never appear on the E-interface. + +In the same way as a the connection oriented service of SCCP is used for the messages relating to one UE on the 3G\_MSC-RNS interface a TCAP dialogue is used on the E-interface for messages relating to one UE. As no correspondence to the connectionless service on the 3G\_MSC-RNS interface is used on the E-interface none of the global procedures are applicable. + +The management of the terrestrial circuits between the 3G\_MSCs is outside the scope of the E-interface (see TS 23.009 [2]), therefore all procedures, messages and information elements relating to terrestrial circuits are also excluded from the RANAP procedures and messages used on the E-interface. + +## 4.2 Transfer of RANAP layer 3 messages on the E-interface + +The RANAP data which on the 3G\_MSC-RNS interface is contained in the user data field of the exchanged SCCP frames is on the E-interface transferred as the contents of the access network signalling info in the AN-APDU parameter as described in TS 29.002 [5], indicating the access network protocol identification "ts3G-25413". + +## 4.3 Roles of 3G\_MSC-A, 3G\_MSC-I and 3G\_MSC-T + +For the description in the present document, the 3G\_MSC's functionality related to the relocation between 3G\_MSCs has been split into three logical parts, 3G\_MSC-A, 3G\_MSC-T and 3G\_MSC-I. The different roles need not necessarily be performed by different 3G\_MSCs. + +3G\_MSC-A is the call/connection controlling part of the 3G\_MSC where the call/connection was originally established and the switching point for relocation between 3G\_MSCs. (This corresponds to 3G\_MSC-A as defined in TS 23.009 [2] and TS 29.002 [5]). The 3G\_MSC that is the 3G\_MSC-A will not be changed during the duration of a call/connection. + +3G\_MSC-T is the part relating to the transitory state during the relocation for the 3G\_MSC controlling the RNS the serving RNS functionality is relocated to, when basic relocation or subsequent relocation (see TS 23.009) take place. (This corresponds, depending on the type of relocation to 3G\_MSC-A, 3G\_MSC-B or 3G\_MSC-B' in TS 23.009 [2] and TS 29.002 [5]). + +3G\_MSC-I is the part of a 3G\_MSC through which the 3G\_MSC-A, via an E-interface (or an internal interface) is in contact with the UE. (This corresponds, depending on the type of relocation to 3G\_MSC-A, 3G\_MSC-B or 3G\_MSC-B' in TS 23.009 [2] and TS 29.002 [5]). + +The 3G\_MSC that is the 3G\_MSC-A can also have the role of either the 3G\_MSC-I or the 3G\_MSC-T during a period of the call/connection. + +The following is applicable for the involved 3G\_MSCs concerning the exchange of RANAP data on an E-interface before and after a successful inter 3G\_MSC relocation: + +- 1) At basic relocation, two 3G\_MSCs are involved, one 3G\_MSC being 3G\_MSC-A and one being 3G\_MSC-T. When this relocation has been performed, the two 3G\_MSCs interworking on the E-interface have the roles of 3G\_MSC-A and 3G\_MSC-I respectively, i.e. the 3G\_MSC that is the 3G\_MSC-T during the relocation is now the 3G\_MSC-I. +- 2) At subsequent relocation back to 3G\_MSC-A, two 3G\_MSCs are involved. The 3G\_MSC having the role of 3G\_MSC-A has also the role of 3G\_MSC-T. The other 3G\_MSC involved has the role of 3G\_MSC-I. When this + +relocation has been completed, there is no exchange of RANAP data on the E-interface, i.e. the 3G\_MSC being the 3G\_MSC-I before and during the relocation is now no longer taking part. + +- 3) At subsequent relocation of SRNS to an 3G\_MSC not being 3G\_MSC-A, three 3G\_MSCs are involved. The roles of these 3G\_MSCs are 3G\_MSC-A, 3G\_MSC-I, and 3G\_MSC-T respectively. When this relocation has been performed, the two 3G\_MSCs interworking on an E-interface have the roles of 3G\_MSC-A and 3G\_MSC-I respectively, i.e. the 3G\_MSC that is the 3G\_MSC-T during the relocation is now the 3G\_MSC-I and the 3G\_MSC being 3G\_MSC-I during the relocation is now no longer taking part. + +# --- 5 Use of the RANAP on the E-interface + +The dedicated RANAP procedures used on the E-interface to some extent are: + +- RAB assignment; +- RAB Release Request; +- Iu Release Request; +- Relocation resource allocation; +- Relocation Detect; +- Relocation Complete; +- Relocation Cancel; +- CN Invoke Trace; +- Security mode control; +- Location Reporting Control; +- Location Report; +- Direct Transfer; +- Error Indication; +- Common ID; +- Location Related Data; +- UE Specific Information; +- RAB Modification Request. + +## 5.1 RAB Assignment + +The RAB Assignment procedure (TS 25.413 [4] subclause 8.2) is applied on the E-interface with following conditions: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +The handling of terrestrial resources is not applicable, i.e. the RANAP IEs *Transport Layer Address* and *Iu Transport Association* will be assigned by the 3G\_MSC-I. + +## 5.2 RAB Release Request + +For the RAB Release Request procedure (TS 25.413 [4] subclauses 8.3) the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-I acts as the RNS; +- the 3G\_MSC-A acts as the 3G\_MSC. + +## 5.3 Iu Release Request + +For the Iu Release Request procedure (TS 25.413 [4] subclause 8.4) the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-I acts as the RNS; +- the 3G\_MSC-A acts as the 3G\_MSC. + +Additionally, at basic Inter-3G\_MSC relocation and at subsequent Inter-3G\_MSC relocation (TS 23.009 [2]), if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, the Iu Release Request procedure (TS 25.413 [4] subclause 8.4) is applied on the E-interface with the following conditions: + +- the 3G\_MSC-T acts as the RNS; +- the 3G\_MSC-A acts as the 3G\_MSC. + +## 5.4 Relocation Resource Allocation + +At basic Inter-3G\_MSC relocation (TS 23.009 [2]) the Relocation Resource Allocation procedure (TS 25.413 [4] subclause 8.7) is applied on the E-interface with the following conditions: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the target RNS. + +At subsequent Inter-3G\_MSC relocation the Relocation Resource Allocation procedure is applied on the E-interface with the following conditions: + +- the 3G\_MSC-I acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the target RNS; +- if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, then this 3G\_MSC shall act as the target RNS towards the 3G\_MSC-I and as the 3G\_MSC towards the 3G\_MSC-T. + +The handling of terrestrial resources is not applicable, i.e. the RANAP IEs *Transport Layer Address* and *Iu Transport Association* will be assigned by the 3G\_MSC-T. + +In case NNSF is active, the *Iu Signalling Connection Identifier* IE and the *Global CN ID* IE shall be set by the 3G\_MSC-T towards Target RNC. + +## 5.5 Relocation Cancel + +For subsequent Inter-3G\_MSC relocation the Relocation Cancel procedure (TS 25.413 [4] subclause 8.10) is applied on the E-interface with the following conditions. + +- the 3G\_MSC-A, acts as the 3G\_MSC; +- the 3G\_MSC-I, acts as the serving RNS. + +## 5.6 Relocation Detect and Relocation Complete + +For the Relocation Detect and Relocation Complete procedure (TS 25.413 [4] subclauses 8.8 and 8.9) the applicable parts on the E-interface are the transfer of RELOCATION DETECT, RELOCATION COMPLETE messages at inter 3G\_MSC relocation. For those parts, the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; + +- the 3G\_MSC-T acts as the target RNS. + +## 5.7 CN Trace invocation + +For the CN Trace invocation procedure (TS 25.413 [4], subclause 8.17), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +Additionally, at basic Inter-3G\_MSC relocation and at subsequent Inter-3G\_MSC relocation (TS 23.009 [2]), if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, the CN Trace invocation procedure (TS 25.413 [4], subclause 8.17) is applied on the E-interface with the following conditions: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the RNS. + +## 5.8 Security mode control + +For the Security mode control procedure (TS 25.413 [4], subclause 8.18), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.9 Location Reporting Control + +For the Location Reporting Control procedure (TS 25.413 [4], subclause 8.19), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +Additionally, at basic Inter-3G\_MSC relocation and at subsequent Inter-3G\_MSC relocation (3GPP TS 23.009 [2]), if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, the Location Reporting Control procedure (TS 25.413 [4] subclause 8.19) is applied on the E-interface with the following conditions: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the RNS. + +## 5.10 Location Report + +For the Location Report procedure (TS 25.413 [4], subclause 8.20), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.11 Direct Transfer + +For the Direct Transfer procedure (TS 25.413 [4], subclause 8.23), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; + +- the 3G\_MSC-I acts as the RNS. + +## 5.12 Error Indication + +For the Error Indication procedure (TS 25.413 [4], subclause 8.27), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.13 CN Deactivate Trace + +For the CN Deactivate Trace procedure procedure (TS 25.413 [4], subclause 8.28), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.14 Common ID + +For the Common ID procedure (TS 25.413 [4], subclause 8.16), the involved 3G MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.15 Location Related Data + +For the Location Related Data procedure (TS 25.413 [4], subclause 8.31), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.16 UE Specific Information + +For the UE Specific Information procedure (TS 25.413 [4], subclause 8.33), the involved 3G MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.17 RAB Modification Request + +For the RAB Modification Request procedure (TS 25.413 [4], subclause 8.30), the involved 3G MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +# 6 RANAP messages transferred on the E-interface + +The list given below shows the RANAP messages, defined in TS 25.413 [4] subclause 9.1(tabular format) and 9.3 (ASN.1 notation) that are transferred on the E-interface. + +| | | +|------------------------------------|-------------------------------------------------| +| RAB ASSIGNMENT REQUEST | (3G_MSC-A -> 3G_MSC-I) | +| RAB ASSIGNMENT RESPONSE | (3G_MSC-I -> 3G_MSC-A) | +| RAB RELEASE REQUEST | (3G_MSC-I -> 3G_MSC-A) | +| IU RELEASE REQUEST | (3G_MSC-I -> 3G_MSC-A and 3G_MSC-T -> 3G_MSC-A) | +| * RELOCATION REQUEST | (3G_MSC-A -> 3G_MSC-T and 3G_MSC-I -> 3G_MSC-A) | +| * RELOCATION REQUEST ACKNOWLEDGE | (3G_MSC-T -> 3G_MSC-A and 3G_MSC-A -> 3G_MSC-I) | +| * RELOCATION DETECT | (3G_MSC-T -> 3G_MSC-A) | +| * RELOCATION COMPLETE | (3G_MSC-T -> 3G_MSC-A) | +| * RELOCATION FAILURE | (3G_MSC-T -> 3G_MSC-A and 3G_MSC-A -> 3G_MSC-I) | +| * RELOCATION CANCEL | (3G_MSC-I -> 3G_MSC-A) | +| * RELOCATION CANCEL ACKNOWLEDGE | (3G_MSC-A -> 3G_MSC-I) | +| # CN INVOKE TRACE | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-A -> 3G_MSC-T) | +| SECURITY MODE COMMAND | (3G_MSC-A -> 3G_MSC-I) | +| SECURITY MODE COMPLETE | (3G_MSC-I -> 3G_MSC-A) | +| SECURITY MODE REJECT | (3G_MSC-I -> 3G_MSC-A) | +| LOCATION REPORTING CONTROL | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-A -> 3G_MSC-T) | +| LOCATION REPORT | (3G_MSC-I -> 3G_MSC-A) | +| DIRECT TRANSFER | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-I -> 3G_MSC-A) | +| ERROR INDICATION | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-I -> 3G_MSC-A) | +| # CN DEACTIVATE TRACE | (3G_MSC-A -> 3G_MSC-I) | +| COMMON ID | (3G_MSC-A -> 3G_MSC-I) | +| LOCATION RELATED DATA REQUEST | (3G_MSC-A -> 3G_MSC-I) | +| LOCATION RELATED DATA RESPONSE | (3G_MSC-I -> 3G_MSC-A) | +| LOCATION RELATED DATA FAILURE | (3G_MSC-I -> 3G_MSC-A) | +| UE SPECIFIC INFORMATION INDICATION | (3G_MSC-A -> 3G_MSC-I) | +| RAB MODIFY REQUEST | (3G_MSC-I -> 3G_MSC-A) | + +All other RANAP messages shall be considered as non-existent on the E-interface. + +Some of the messages above are qualified by \* or #. This indicates whether the message, when sent on the E interface, is considered as: + +- relocation related message (\*); or +- trace related message (#). + +# --- 7 Exceptions for RANAP message contents and information element coding when transferred on the E-interface + +## 7.1 Message Contents + +For the applicable RANAP messages transferred on the E-interface the following exceptions to the descriptions in TS 25.413 [4] are valid: + +### RAB ASSIGNMENT REQUEST message + +- Transport Layer Address IE: + - if received, this IE shall be ignored; +- Iu Transport Association IE: + - if received, this IE shall be ignored; +- UP Mode Versions IE: + - the information given within this IE is only useful in case of TrFO. + +### RELOCATION REQUEST message + +- Transport Layer Address IE: + - if received, this IE shall be ignored; +- Iu Transport Association IE: + - if received, this IE shall be ignored; +- UP Mode Versions IE: + - the information given within this IE is only useful in case of TrFO; +- Iu Signalling Connection Identifier IE: + - if received, this IE shall be ignored; +- Global CN ID IE: + - if received, this IE shall be ignored. + +# --- 8 RANAP message error handling when transferred on the E-interface + +The RANAP error handling (TS 25.413 [4], clause 10) is applicable. The handling of faults concerning the use of SCCP is not applicable. + +The RANAP error messages sent on the E-interface shall only be sent as response to RANAP messages received on the same interface. \ No newline at end of file diff --git a/marked/Rel-18/29_series/29139/raw.md b/marked/Rel-18/29_series/29139/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b5a789a0c68947cd2a72002a43a4496edf090144 --- /dev/null +++ b/marked/Rel-18/29_series/29139/raw.md @@ -0,0 +1,344 @@ + + +# 3GPP TS 29.139 V18.0.0 (2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP system - fixed broadband access network interworking; Home (e)Node B - security gateway interface (Release 18)** + +![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase font. Above the "e" is the text "Advanced Pro" in a smaller font. To the right of the "e" is a green signal icon consisting of three curved lines. + +LTE Advanced Pro logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo. It features the letters "3GPP" in a stylized, bold font. Below the "P" is a red signal icon consisting of three curved lines. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, uppercase font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 General..... | 6 | +| 4.1 Protocol Stack ..... | 6 | +| 4.1.1 Control Plane for H(e)NB – SeGW ..... | 6 | +| 4.1.2 User Plane for H(e)NB – SeGW ..... | 7 | +| 5 Supporting QoS..... | 8 | +| 5.1 General ..... | 8 | +| 5.2 H(e)NB procedures ..... | 8 | +| 5.2.1 General ..... | 8 | +| 5.2.2 QCI mapping ..... | 8 | +| 5.2.3 Reflective QoS..... | 8 | +| 5.3 SeGW procedures..... | 8 | +| 6 Tunnel Management ..... | 8 | +| 6.1 General ..... | 8 | +| 6.2 H(e)NB procedures ..... | 9 | +| 6.2.1 Tunnel establishment..... | 9 | +| 6.2.1.1 IP address allocation ..... | 9 | +| 6.2.1.2 NAT Traversal ..... | 9 | +| 6.2.1.3 H(e)NB NATed Tunnel-IP address discovery..... | 9 | +| 6.2.2 Tunnel modification ..... | 9 | +| 6.2.3 Tunnel disconnection..... | 9 | +| 6.3 SeGW procedures..... | 9 | +| 6.3.1 Tunnel establishment..... | 9 | +| 6.3.1.1 IP address allocation ..... | 9 | +| 6.3.1.2 NAT Traversal ..... | 10 | +| 6.3.1.3 H(e)NB NATed Tunnel-IP address discovery..... | 10 | +| 6.3.2 Tunnel modification ..... | 10 | +| 6.3.3 Tunnel disconnection..... | 10 | +| 7 PDUs and parameters specific to the present document..... | 10 | +| 7.1 IETF RFC coding information defined within present document..... | 10 | +| 7.1.1 IKEv2 Configuration Payloads attributes..... | 10 | +| 7.1.1.1 EXTERNAL_SOURCE_IP4_NAT_INFO attribute ..... | 10 | +| Annex A (informative): Change history..... | 12 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the H(e)NB – SeGW interface. The interface is used for the interworking between a 3GPP system and a Fixed Broadband Access network defined by Broadband Forum. The interworking procedure provides the IP connectivity to a 3GPP UE using a H(e)NB connected to a Fixed Broadband Access network as specified in 3GPP TS 23.139 [2]. + +The specification covers the QoS aspects and Tunnel management procedures. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.139: "3GPP System-Fixed Broadband Access Network Interworking; Stage 2". +- [3] 3GPP TS 24.139: "3GPP System-Fixed Broadband Access Network Interworking; Stage 3". +- [4] IETF RFC 2474 (December 1998): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [5] IETF RFC 5996: "Internet Key Exchange Protocol Version 2 (IKEv2)". +- [6] IETF RFC 3948: "UDP Encapsulation of IPsec ESP Packets". +- [7] 3GPP TS 33.320: "Security of Home Node B (HNB) / Home evolved Node B (HeNB)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**H(e)NB Reflective QoS function:** H(e)NB Reflective QoS function is a H(e)NB function in order to support QoS for uplink traffic over a Fixed Broadband Access network as specified in 3GPP TS 23.139 [2]. + +**H(e)NB local IP address Info:** H(e)NB local IP address Info is defined as either the public IPv4 address or IPv6 address assigned to the H(e)NB by the Fixed Broadband Access Network domain, or the public IPv4 address and the UDP port number used by the NATed RG that is used for this H(e)NB. The public IPv4 address used by the NATed RG is assigned by the Fixed Broadband Access Network domain. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|--------|------------------------------------| +| DSCP | Differentiated Services Code Point | +| H(e)NB | Home (e)NodeB | +| NAT | Network Address Translation | +| NAT-T | NAT Traversal | +| SeGW | Security Gateway | + +# 4 General + +## 4.1 Protocol Stack + +### 4.1.1 Control Plane for H(e)NB – SeGW + +![Protocol stack diagram for Control Plane for H(e)NB - SeGW Interface over IPv4 transport network. It shows three main components: H(e)NB, NAT, and SeGW. H(e)NB and SeGW have identical protocol stacks: IKEv2, UDP, IPv4, L2, L1. The NAT component is shown as a dashed box containing two parallel paths, each with UDP, IPv4, L2, and L1 layers. Lines connect the layers between H(e)NB and NAT, and between NAT and SeGW, showing the flow of the control plane traffic.](5d76c2e9976aaf97001ee189908830fb_img.jpg) + +Protocol stack diagram for Control Plane for H(e)NB - SeGW Interface over IPv4 transport network. It shows three main components: H(e)NB, NAT, and SeGW. H(e)NB and SeGW have identical protocol stacks: IKEv2, UDP, IPv4, L2, L1. The NAT component is shown as a dashed box containing two parallel paths, each with UDP, IPv4, L2, and L1 layers. Lines connect the layers between H(e)NB and NAT, and between NAT and SeGW, showing the flow of the control plane traffic. + +#### **Legend:** + +- **IKEv2 Protocol:** This protocol is used to between H(e)NB and SeGW. The IKEv2 protocol is defined in IETF RFC 5996 [5]. + +**Figure 4.1.1-1: Control Plane for H(e)NB - SeGW Interface over IPv4 transport network** + +![Control Plane for H(e)NB - SeGW Interface over IPv6 transport network](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +This diagram illustrates the control plane protocol stack for the H(e)NB - SeGW interface over an IPv6 transport network. It shows two vertical protocol stacks, one for H(e)NB on the left and one for SeGW on the right, connected by horizontal lines representing the interface. Both stacks consist of five layers: IKEv2 at the top, followed by UDP, IPv6, L2, and L1 at the bottom. The layers are aligned across the interface. + +Control Plane for H(e)NB - SeGW Interface over IPv6 transport network + +##### **Legend:** + +- **IKEv2 Protocol:** This protocol is used to between H(e)NB and SeGW. The IKEv2 protocol is defined in RFC 5996 [5]. + +**Figure 4.1.1-2: Control Plane for H(e)NB - SeGW Interface over IPv6 transport network** + +### 4.1.2 User Plane for H(e)NB – SeGW + +![User Plane for H(e)NB - SeGW Interface over IPv4 transport network](9791722d75115ddcc599b07d7bc35d73_img.jpg) + +This diagram illustrates the user plane protocol stack for the H(e)NB - SeGW interface over an IPv4 transport network. It shows two vertical protocol stacks, one for H(e)NB on the left and one for SeGW on the right, connected by a central NAT (Network Address Translation) block. The H(e)NB stack has five layers: Payload, IPsec, UDP, IPv4, L2, and L1. The SeGW stack also has five layers: Payload, IPsec, UDP, IPv4, L2, and L1. The NAT block, enclosed in a dashed box, contains two columns of four layers: UDP, IPv4, L2, and L1. The UDP layers in the H(e)NB and SeGW stacks are connected to the corresponding UDP layers in the NAT block. + +User Plane for H(e)NB - SeGW Interface over IPv4 transport network + +#### **Legend:** + +- **UDP:** UDP encapsulation is used if NAT is detected between the H(e)NB and the SeGW. + +**Figure 4.1.2-1: User Plane for H(e)NB - SeGW Interface over IPv4 transport network** + +![User Plane for H(e)NB - SeGW Interface over IPv6 transport network](78d5774278a3f4a614f8c0ae485ce8d9_img.jpg) + +This diagram illustrates the user plane protocol stack for the H(e)NB - SeGW interface over an IPv6 transport network. It shows two vertical protocol stacks, one for H(e)NB on the left and one for SeGW on the right, connected by horizontal lines representing the interface. Both stacks consist of five layers: Payload at the top, followed by IPsec, IPv6, L2, and L1 at the bottom. The layers are aligned across the interface. + +User Plane for H(e)NB - SeGW Interface over IPv6 transport network + +**Figure 4.1.2-2: User Plane for H(e)NB - SeGW Interface over IPv6 transport network** + +# --- 5 Supporting QoS + +## 5.1 General + +At interworking with a Fixed Broadband Access network, QoS is provided by DSCP marking as specified in IETF RFC 2474 [4]. + +## 5.2 H(e)NB procedures + +### 5.2.1 General + +The H(e)NB shall support DSCP marking on the IPsec header when forwarding the UE uplink traffic. + +Based on H(e)NB configuration either the QCI mapping or the Reflective QoS may be used. + +### 5.2.2 QCI mapping + +The QCI mapping table contains a one-to-one mapping from QCI value to DSCP marking value. The QCI mapping table is configured in the H(e)NB by the operator. + +When forwarding an uplink IP packet, the H(e)NB shall perform a lookup in the QCI mapping table based on the QCI value of the EPS bearer/PDP context before the IPsec tunnel encapsulation. The H(e)NB shall set the DSCP marking value of the IPsec header according to the matched QCI mapping table entry. + +### 5.2.3 Reflective QoS + +To support the H(e)NB Reflective QoS function for uplink traffic, the H(e)NB shall create and maintain the uplink DSCP marking rules for each active PDN connection as specified for UE Reflective QoS function in 3GPP TS 24.139 [3]. + +When forwarding an uplink IP packet, the H(e)NB shall perform a lookup in the DSCP marking table based on the n-tuple of the IP header before the IPsec tunnel encapsulation. If a matching entry is found, the H(e)NB shall set the DSCP marking value of the IPsec header according to the matched DSCP marking rule. If no matching entry is found, the H(e)NB shall copy the DSCP field of the outer IP header into the IPsec header before forwarding to the SeGW. + +## 5.3 SeGW procedures + +When receiving a downlink data packet, the SeGW shall copy the DSCP marking value from the outer IP header into the IPsec header before forwarding to the H(e)NB using the IPsec tunnel, as specified in 3GPP TR 23.139 [2]. + +# --- 6 Tunnel Management + +## 6.1 General + +The tunnel is an IPsec tunnel established via an IKEv2 protocol exchange IETF RFC 5996 [5] between the H(e)NB and the SeGW which is through the Fixed Broadband Access Network. + +In an IPv4 Fixed Broadband Access Network, NAT can be deployed between the H(e)NB and the SeGW, e.g. in a Residence Gateway. A H(e)NB behind the NAT shall invoke the NAT traversal procedure for IKEv2. The IPsec tunnel is encapsulated over UDP in the Tunnel-Mode as specified in IETF RFC 5996 [5]. + +## 6.2 H(e)NB procedures + +### 6.2.1 Tunnel establishment + +#### 6.2.1.1 IP address allocation + +The SeGW shall provide the IP address to the H(e)NB for the communication with the EPC network. + +For dynamic IP address allocation, the H(e)NB shall include the requested IP address type (IPv4 address or IPv6 address) that needs to be configured in an IKEv2 CFG\_REQUEST Configuration Payload in the IKE\_AUTH request message as defined in IETF RFC 5996 [5] after reception of the IKE\_SA\_INIT response from the SeGW. + +#### 6.2.1.2 NAT Traversal + +NAT can be deployed in an IPv4 Fixed Broadband Access Network. IKEv2 NAT Traversal specified in section 2.23 of IETF RFC 5996 [5] shall be supported by H(e)NB. + +If NAT is detected between the H(e)NB and SeGW, the following procedures shall be performed: + +- UDP-Encapsulated ESP as defined in IETF RFC 5996 [5]; +- sending the NAT-keepalive packet to keep NAT mapping alive if no other packet to the SeGW has been sent in M seconds as defined in the IETF RFC 3948 [6]; + +NOTE: M is a locally configurable parameter with a default value of 20 seconds as defined in the IETF RFC 3948 [6]. + +#### 6.2.1.3 H(e)NB NATed Tunnel-IP address discovery + +If NAT is detected between the H(e)NB and SeGW, the H(e)NB shall request the SeGW to return the H(e)NB local IP address information by including the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute as defined in subclause 7.1.1.1 in the CFG\_REQUEST Configuration Payload within the IKE\_AUTH request message. The length field of the attribute shall be set to zero. The NATed IPv4 Address field and UDP Port number field shall be absent. + +If the H(e)NB subsequently receives the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute in the CFG\_REPLY configuration payload from the SeGW, the H(e)NB shall report the IP address received in EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute as the H(e)NB local IP address to the MME/SGSN. + +### 6.2.2 Tunnel modification + +NAT mappings can change when the UDP port number is reassigned by the NAT, and/or H(e)NB local IP address is reallocated due to NAT restart. + +Upon NAT remapping, the SeGW initiates the tunnel disconnection procedure as specified in subclause 6.3.3. Then the H(e)NB shall re-initiate the tunnel establishment procedure as specified in sub-clause 6.2.1. + +### 6.2.3 Tunnel disconnection + +The H(e)NB shall use the procedures defined in IETF RFC 5996 [5] to disconnect an IPsec tunnel to the SeGW. + +## 6.3 SeGW procedures + +### 6.3.1 Tunnel establishment + +#### 6.3.1.1 IP address allocation + +For dynamic IP address allocation, upon receipt of an IKE\_AUTH request message from the H(e)NB requesting the IP address, the SeGW shall include the remote IP address information in the IKEv2 Configuration Payload (CFG\_REPLY) + +of the final IKE\_AUTH response message to the H(e)NB. The SeGW shall assign either an IPv4 or an IPv6 address to the H(e)NB via a single CFG\_REPLY Configuration Payload. + +#### 6.3.1.2 NAT Traversal + +NAT can be deployed in an IPv4 Fixed Broadband Access Network. IKEv2 NAT Traversal specified in section 2.23 of IETF RFC 5996 [5] shall be supported by SeGW. + +If NAT is detected between the H(e)NB and SeGW, the SeGW shall use UDP-Encapsulated ESP as defined in IETF RFC 5996 [5]. + +#### 6.3.1.3 H(e)NB NATed Tunnel-IP address discovery + +If the SeGW receives the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute as defined in subclause 7.1.1.1 in the CFG\_REQUEST configuration payload within IKE\_AUTH request message, the SeGW shall provide the H(e)NB local IP address information (i.e. NATed IPv4 address and UDP port number) to the H(e)NB by including the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute in the CFG\_REPLY configuration payload within the IKE\_AUTH response message. + +### 6.3.2 Tunnel modification + +NAT mappings can change when the UDP port number is reassigned by the NAT, and/or H(e)NB local IP address is reallocated due to NAT restart. + +If NAT remapping is detected by the SeGW, the SeGW shall initiate the tunnel disconnection procedure (see subclause 6.3.3). + +NOTE: No procedures are defined in current release of specification to enable the SeGW to send the modified H(e)NB local IP address information to the H(e)NB during the lifetime of IKEv2 security association. + +### 6.3.3 Tunnel disconnection + +The SeGW shall use the procedures defined in IETF RFC 5996 [5] to disconnect an IPsec tunnel to the H(e)NB. + +# --- 7 PDUs and parameters specific to the present document + +## 7.1 IETF RFC coding information defined within present document + +### 7.1.1 IKEv2 Configuration Payloads attributes + +#### 7.1.1.1 EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute + +The format of the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute follows the definition of Configuration Attributes as specified in IETF RFC 5996 [5], section 3.15.1. The format is shown in figure 7.1.1.1-1 as below. The length of the EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute is 0 or 6 bytes. + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Octets | | | | | | | | +|--------------------|----------------|---|---|---|---|---|---|--------|--|--|--|--|--|--|--| +| R | Attribute Type | | | | | | | 1 | | | | | | | | +| Attribute Type | | | | | | | | 2 | | | | | | | | +| Length | | | | | | | | 3, 4 | | | | | | | | +| NATed IPv4 Address | | | | | | | | 5 - 8 | | | | | | | | +| UDP Port number | | | | | | | | 9 - 10 | | | | | | | | + +**Figure 7.1.1.1-1: EXTERNAL\_SOURCE\_IP4\_NAT\_INFO attribute** + +The R bit in the first octet is as defined in IETF RFC 5996 [5]. + +The Attribute Type indicating EXTERNAL\_SOURCE\_IP4\_NAT\_INFO is of the value 23. \ No newline at end of file diff --git a/marked/Rel-18/29_series/29155/raw.md b/marked/Rel-18/29_series/29155/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ac498fddda1e648d7a70d0f4916cd43679b7033d --- /dev/null +++ b/marked/Rel-18/29_series/29155/raw.md @@ -0,0 +1,1799 @@ + + +# 3GPP TS 29.155 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Traffic steering control; Representational State Transfer (REST) over St reference point (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +## --- **Keywords** + +--- + +HTTP,TSSF,PCRF,JASON + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + +--- + + + +## --- **Copyright Notification** + +--- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 St reference point ..... | 7 | +| 4.1 Overview ..... | 7 | +| 4.2 Reference model..... | 7 | +| 4.3 Functional elements..... | 8 | +| 4.3.1 TSSF ..... | 8 | +| 4.3.2 PCRF ..... | 8 | +| 4.4 Procedures over St reference point..... | 8 | +| 4.4.1 General ..... | 8 | +| 4.4.2 Traffic Steering Policy Provisioning over St..... | 8 | +| 4.4.3 Traffic Steering Rule Error Handling..... | 9 | +| 4.4.4 UE IPv4 address provisioning ..... | 9 | +| 5 St protocol..... | 10 | +| 5.1 Introduction ..... | 10 | +| 5.2 Transport layer ..... | 10 | +| 5.3 Application delivery layer..... | 11 | +| 5.3.1 Methods ..... | 11 | +| 5.3.2 Resources and URI design..... | 11 | +| 5.3.3 HTTP request/response formats ..... | 12 | +| 5.3.3.1 General..... | 12 | +| 5.3.3.2 POST /stapplication/sessions..... | 13 | +| 5.3.3.3 PUT /stapplication/sessions/{stsessionid} ..... | 15 | +| 5.3.3.4 PATCH /stapplication/sessions/{stsessionid} ..... | 16 | +| 5.3.3.5 DELETE /stapplication/sessions/{stsessionid} ..... | 17 | +| 5.3.3.6 GET /stapplication/sessions/{stsessionid}..... | 18 | +| 5.3.3.7 POST /{notificationbaseurl}/{stsessionid} ..... | 19 | +| 5.3.4 St session ID..... | 20 | +| 5.3.5 HTTP status codes..... | 21 | +| 5.3.6 Feature negotiation ..... | 22 | +| 5.3.6.1 General..... | 22 | +| 5.3.7 HTTP custom headers ..... | 22 | +| 5.3.7.1 3gpp-Optional-Features ..... | 22 | +| 5.3.7.2 3gpp-Required-Features..... | 22 | +| 5.3.7.3 3gpp-Accepted-Features ..... | 23 | +| 5.3.7.4 3gpp-Notification-Base-URL ..... | 23 | +| 5.4 Specific application communication ..... | 23 | +| 5.4.1 General ..... | 23 | +| 5.4.2 Content type..... | 23 | +| 5.4.3 JSON session fields..... | 23 | +| 5.4.3.1 General ..... | 23 | +| 5.4.3.2 session-id ..... | 24 | +| 5.4.3.3 ue-ipv4 ..... | 24 | +| 5.4.3.4 ue-ipv6-prefix ..... | 24 | +| 5.4.3.5 tsrules..... | 24 | +| 5.4.3.6 ts-rule-name ..... | 25 | +| 5.4.3.7 precedence ..... | 25 | +| 5.4.3.8 tdf-application-identifier..... | 25 | +| 5.4.3.9 flow-information..... | 25 | +| 5.4.3.10 flow-description..... | 26 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| 5.4.3.11 | tos-traffic-class ..... | 26 | +| 5.4.3.12 | security-parameter-index ..... | 26 | +| 5.4.3.13 | flow-label..... | 26 | +| 5.4.3.14 | flow-direction ..... | 26 | +| 5.4.3.15 | ts-policy-identifier-dl..... | 26 | +| 5.4.3.16 | ts-policy-identifier-ul..... | 26 | +| 5.4.3.17 | predefined-tsrules ..... | 26 | +| 5.4.3.18 | predefined-group-of-tsrules ..... | 27 | +| 5.4.3.19 | ts-rule-base-name ..... | 27 | +| 5.4.3.20 | called-station-id ..... | 27 | +| 5.4.4 | JSON errors and informational response fields..... | 27 | +| 5.4.4.1 | General ..... | 27 | +| 5.4.4.2 | errors..... | 28 | +| 5.4.4.3 | error-type ..... | 28 | +| 5.4.4.4 | error-message ..... | 28 | +| 5.4.4.5 | error-tag ..... | 28 | +| 5.4.4.6 | error-path ..... | 28 | +| 5.4.4.7 | error-info..... | 28 | +| 5.4.4.6 | success-message ..... | 29 | +| 5.4.4.7 | success-path..... | 29 | +| 5.4.4.8 | success-info ..... | 29 | +| | The success-info field is defined as an object type. It may include any additional information under the root level of the JSON content for an informational response. .... | 29 | +| 5.4.5 | JSON report fields..... | 29 | +| 5.4.5.1 | General ..... | 29 | +| 5.4.5.2 | ts-rule-reports ..... | 29 | +| 5.4.5.3 | resource-paths..... | 30 | +| 5.4.5.4 | rule-status ..... | 30 | +| 5.4.5.5 | rule-failure-code ..... | 30 | +| 5.4.6 | JSON notification fields ..... | 31 | +| 5.4.6.1 | General ..... | 31 | +| 5.4.6.2 | notifications ..... | 31 | +| 5.4.6.3 | notification-type ..... | 31 | +| 5.4.6.4 | notification-message..... | 32 | +| 5.4.6.5 | notification-tag ..... | 32 | +| 5.4.6.6 | notification-info ..... | 32 | +| 5.5 | TSSF discovery ..... | 32 | +| 6 | Secure communication..... | 32 | +| Annex A (informative): | Call Flows..... | 32 | +| A.1 | General..... | 32 | +| A.2 | Traffic Steering Control Information Provisioning ..... | 32 | +| A.3 | Traffic Steering Control Information Update ..... | 33 | +| A.4 | Traffic Steering Control Information Removal ..... | 34 | +| A.5 | Traffic Steering Control Notification..... | 34 | +| Annex B (normative): | JSON Schema ..... | 35 | +| B.1 | Session body schema ..... | 35 | +| B.2 | Error and Informational response schema ..... | 37 | +| B.3 | Report schema..... | 39 | +| B.4 | Notification schema ..... | 40 | +| Annex C (informative): | Change history..... | 42 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the Representational State Transfer (REST) protocol-based St reference point, which is used to provision the traffic steering control information to the TSSF from the PCRF. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.203: "Policy and charging control architecture". +- [3] IETF RFC 793: "Transmission Control Protocol". +- [4] Void. +- [5] 3GPP TS 29.201: "Representational State Transfer (REST) reference point between Application Function (AF) and Protocol Converter (PC)". +- [6] IETF RFC 1786: "Uniform Resource Locators (URL)". +- [7] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security". +- [8] IETF RFC 1983: "Internet Users' Glossary". +- [9] Void. +- [10] IETF RFC 7159: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [11] Void. +- [12] IETF RFC 5789: "PATCH Method for HTTP". +- [13] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". +- [14] IETF RFC 6902: "JavaScript Object Notation (JSON) Patch". +- [15] IETF RFC 6901: "JavaScript Object Notation (JSON) Pointer". +- [16] IETF draft-newton-json-content-rules-09: "A Language for Rules Describing JSON Content". + +NOTE: This individual draft will not further progress in IETF. It is available from the following link: +. + +- [17] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [18] 3GPP TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping". +- [19] IETF RFC 2818: "HTTP Over TLS". +- [20] 3GPP TS 23.003: "Numbering, addressing and identification". + +- [21] IETF RFC 6733: "Diameter Base Protocol". +- [22] IETF RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". +- [23] IETF RFC 7231: "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content". +- [24] IETF RFC 7232: "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests". +- [25] IETF RFC 7233: "Hypertext Transfer Protocol (HTTP/1.1): Range Requests". +- [26] IETF RFC 7234: "Hypertext Transfer Protocol (HTTP/1.1): Caching". +- [27] IETF RFC 7235: "Hypertext Transfer Protocol (HTTP/1.1): Authentication". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +(S)Gi-LAN: The network infrastructure connected to the 3GPP network over the SGi or Gi reference point that provides various IP-based services. + +(S)Gi-LAN service function: A function located in the (S)Gi-LAN that provides value-added IP-based services e.g. NAT, anti-malware, parental control, DDoS protection. + +JSON Content Rules: JSON Content Rules (JCR), as defined in IETF draft-newton-json-content-rules [16] is a language specifying the interchange of data in JSON as defined in RFC 7159 [10]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|------|------------------------------------| +| JCR | JSON Content Rules | +| JSON | JavaScript Object Notation | +| PCRF | Policy and Charging Rules Function | +| TSSF | Traffic Steering Support Function | + +# --- 4 St reference point + +## 4.1 Overview + +The St reference point resides between the PCRF and TSSF. St reference point is used to provision the traffic steering control information from the PCRF to the TSSF. + +## 4.2 Reference model + +The St reference point resides between the PCRF and TSSF as depicted in figure 4.2.1. The overall PCC architecture is depicted in subclause 3a of 3GPP TS 29.213 [18]. + +![Diagram of the St reference model showing the PCRF and TSSF connected by the St interface.](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates the St reference model. It consists of two light green rectangular boxes, labeled 'PCRF' on the left and 'TSSF' on the right. A horizontal black line connects the two boxes. Above this line, the label 'St' is centered, with a small vertical tick mark on the line directly below it. + +Diagram of the St reference model showing the PCRF and TSSF connected by the St interface. + +Figure 4.2.1: St reference model + +## 4.3 Functional elements + +### 4.3.1 TSSF + +The TSSF is a function that receives traffic steering control information from the PCRF and ensures that the related traffic steering policy is enforced in the (S)Gi-LAN. + +A traffic steering policy is locally configured in TSSF and can be used for uplink, downlink or for both directions. To ensure that the traffic steering policy is enforced, the TSSF performs deployment specific actions as configured for that traffic steering policy. + +### 4.3.2 PCRF + +The PCRF functionality defined in 3GPP TS 23.203 [2] is applicable. In addition, the PCRF shall be able to make a decision of traffic steering policies used to control the steering of the subscriber's traffic to appropriate (S)Gi-LAN service functions. + +NOTE: In order to allow the PCRF to select and provision an application based traffic steering policy, the reporting of detected applications to the PCRF or any other information can be used. + +## 4.4 Procedures over St reference point + +### 4.4.1 General + +The procedures which can be operated at the St interface are described in the following subclauses. + +### 4.4.2 Traffic Steering Policy Provisioning over St + +When the PCRF determines the traffic steering control information needed for the IP-CAN session; the PCRF shall send an HTTP POST message to the TSSF to create a new session resource. The PCRF shall provide the representation of the session resource within the body of the HTTP POST. Within the body of the HTTP POST, the PCRF shall provide the St Session ID, the PDN information if required by the operator policies, the UE IPv4 address and/or UE IPv6 prefix and one or more sets of traffic steering control information to the TSSF. + +The PCRF may modify or remove traffic steering control information at any time (e.g. due to subscription change or network status change) by sending either an HTTP PUT or HTTP PATCH message to the TSSF including the St session ID within the request URL. When using an HTTP PUT to modify the session resource, the PCRF shall provide the entire state of the session resource within the body of the HTTP PUT. In this case, the TSSF shall replace the existing session information associated with this resource with the information provided in the body of the HTTP PUT. When using an HTTP PATCH to modify the session resource, the PCRF shall provide the modifications within the body of the HTTP PATCH as defined in subclause 5.3.3.3. In this case, the TSSF shall update the existing session resource based on the content of the body of the HTTP PATCH. + +In order to remove all of the traffic steering control information associated with an IP-CAN session when the IP-CAN session is terminated, the PCRF shall send to the TSSF an HTTP DELETE message including the St Session ID within the request URL. + +Once the PCRF has requested the creation of a session resource, the PCRF may request the state of the session at any time by sending an HTTP GET request to the TSSF including the Session ID within the request URL. Upon receipt of an HTTP GET from the PCRF, the TSSF shall provide the session representation within the body of the response. Based on the received information, the PCRF may decide whether re-installation, modification, removal of the traffic steering control information or any other action applies. + +When a combination of PCEF/TDF with traffic steering control feature and TSSF is deployed, the TSSF shall behave as specified in subclause 6.1.17 of 3GPP TS 23.203 [2]. In this case, the PCRF shall provide the traffic detection information as part of the service data flow information included in the tos-traffic-class within the flow-information field or within the tdf-application-identifier field. If traffic detection is performed using the flow-information field, the PCRF shall ensure that the relevant value of the tos-traffic-class field included within the flow-information field used for traffic detection is the same as the value provided in the traffic steering policy identifier(s) provided over Gx or Sd reference point. If traffic detection is performed using the tdf-application-identifier field, the PCRF shall ensure that the identifier included within the tdf-application-identifier refers to the configured value(s) in the TSSF that correspond to the value provided in the traffic steering policy identifier(s) over Gx or Sd reference point. See 3GPP TS 29.212 [17]. + +NOTE 1: The PCRF and TSSF are configured with the traffic detection mechanism to be applied when the tdf-application-identifier field is used for traffic detection. + +NOTE 2: The tdf-application-identifier can refer to the configured traffic detection information for uplink and/or downlink traffic. + +### 4.4.3 Traffic Steering Rule Error Handling + +If the installation/activation of one or more traffic steering rules fails, the TSSF shall inform the PCRF of the failed traffic steering rules in the corresponding JSON body of the HTTP response, by including a ts-rule-reports field, and by setting the error-tag to TS\_RULE\_EVENT. The ts-rule-reports field is an array of rule failure reports. Within each rule failure report, the TSSF shall identify the failed traffic steering rule(s) by including the resource-paths field containing a list of JSON pointer(s) to the relevant traffic steering rule resource(s), shall specify the failed reason code by including a rule-failure-code field and a rule-status as described below: + +- If the installation/activation of one or more new traffic steering rules (i.e., rules which were not previously successfully installed) fails, the TSSF shall set the rule-status field to INACTIVE. +- If the modification of a currently active traffic steering rule fails, the TSSF shall retain the existing traffic steering rule as active without modification unless the reason for the failure also has an impact on the existing traffic steering rule. + +Depending on the value of the rule-failure-code field, the PCRF may decide whether retaining of the old traffic steering rule, re-installation, modification, removal of the traffic steering rule or any other action applies. + +If a traffic steering rule was successfully installed/activated, but can no longer be enforced by the TSSF, and if the notification supported feature is supported by the TSSF and PCRF, the TSSF shall notify the PCRF of the rule enforcement failure by sending an HTTP POST request to the notification URL provided by the PCRF as defined in subclause 5.3.3.2. The JSON body of this HTTP POST shall include a notification-info field containing a ts-rule-reports field and a notification-tag field set to a value of TS\_RULE\_EVENT filled. Each item of the ts-rule-reports shall include the corresponding rule-failure-code field and rule-status field to INACTIVE. + +Note that the PCRF may poll the session state from the TSSF at any time via the HTTP GET method as described in subclause 4.4.2; and take further decisions based on the status of the traffic steering rules reported in the session state. + +### 4.4.4 UE IPv4 address provisioning + +When the PCRF is notified by the PCEF that either a UE\_IP\_ADDRESS\_ALLOCATE or a UE\_IP\_ADDRESS\_RELEASE event of the IP-CAN session occurred in the PCEF, the PCRF shall send an HTTP PATCH or PUT message to the TSSF including the St session ID within the request URL. + +If the PCRF uses HTTP PUT to update the St session, the PCRF shall provide the entire state of the session resource including the new IPv4 in case a new IPv4 was allocated or omitting the IPv4 in case the IPv4 was released. If the PCRF uses the HTTP PATCH method to update the St session, and if the IPv4 was allocated, the PCRF shall use the "add" operation within the body of the HTTP PATCH to include the new IPv4 as specified in subclause 5.3.3.4; otherwise if the IPv4 was released, the PCRF shall use the "remove" operation within the body of the HTTP PATCH to remove the IPv4 as specified in subclause 5.3.3.4. If the PCRF provides the new UE IPv4 address to the TSSF, the + +TSSF shall additionally apply the traffic steering rules to the user plane traffic with the IP address matching the new UE IPv4 address. If the PCRF notifies to the TSSF that the UE IPv4 address has been released, the TSSF shall stop applying the traffic steering rule to the user plane traffic with the IP address matching the released UE IPv4 address. + +# 5 St protocol + +## 5.1 Introduction + +The following layers of the protocol stack for the St reference point between PCRF and TSSF are described in subclauses: + +- TCP as defined in IETF RFC 793 [3] provides the communication service at the transport layer. +- An optional communication security layer can be added between the transport and the application delivery layer (see clause 6). +- The application delivery layer provides the transport of the specific application communication data using HTTP/1.1 as defined in IETF RFC 7230 [22], IETF RFC 7231 [23], IETF RFC 7232 [24], IETF RFC 7233 [25], IETF RFC 7234 [26] and IETF RFC 7235 [27]. +- The specific application communication layer constitutes the transport of the JSON content type. + +Figure 5.1.1 illustrates the protocol stack of the RESTful St reference point. + +![Diagram of the protocol stack for the RESTful St reference point between PCRF and TSSF. The stack consists of six layers: Specific application communication (JSON), Application delivery (HTTP), Transport layer (TCP), Network layer (IP), Data link layer (L2), and Physical layer (L1). The layers are mirrored between the PCRF and TSSF, with a vertical line representing the REST-St reference point between them.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +| | | | | +|------------------------------------|------|---------|------| +| Specific application communication | JSON | | JSON | +| Application delivery | HTTP | | HTTP | +| Transport layer | TCP | | TCP | +| Network layer | IP | | IP | +| Data link layer | L2 | | L2 | +| Physical layer | L1 | | L1 | +| | PCRF | REST-St | TSSF | + +Diagram of the protocol stack for the RESTful St reference point between PCRF and TSSF. The stack consists of six layers: Specific application communication (JSON), Application delivery (HTTP), Transport layer (TCP), Network layer (IP), Data link layer (L2), and Physical layer (L1). The layers are mirrored between the PCRF and TSSF, with a vertical line representing the REST-St reference point between them. + +Figure 5.1.1: Protocol stack of the RESTful St reference point + +## 5.2 Transport layer + +HTTP is layered over TCP, which provides a reliable transport. + +For traffic steering policy provisioning and querying, the PCRF acts as an HTTP client and the TSSF acts as an HTTP server. As a result, the PCRF shall initiate a TCP connection with the TSSF. + +If the notification feature is supported by TSSF and PCRF, then the TSSF and PCRF shall also respectively act as HTTP client and server. In this case, the TSSF shall initiate a TCP connection with the PCRF. + +## 5.3 Application delivery layer + +The application delivery layer shall use RESTful HTTP. + +The application delivery layer provides the following services: + +- session establishment including the creation of the session resource. +- session modification and termination procedures. +- session notification procedures. + +In order to establish an St session, the PCRF shall send an HTTP POST message to the TSSF including all session information required. The PCRF shall assign a globally and eternally unique St Session ID and shall include it as part of the session resource representation within the body of the HTTP POST. The St Session ID is defined in subclause 5.3.4. If the session resource is successfully created at the TSSF, the TSSF shall provide the session resource URI within the Location header of the HTTP response. + +In order to modify an St session, the PCRF shall send an HTTP PUT (full replacement of the St session resource) or an HTTP PATCH message, which includes the St session ID as a path element of the URI. + +In order to query the state of an St session, the PCRF shall send an HTTP GET message including the St Session ID as a path element of the request URI. + +In order to delete an St session, the PCRF shall send an HTTP DELETE message including the St session ID as a path element of the request URI. + +In order to report traffic steering rule enforcement failures for an St session, if the notification feature is supported by both the PCRF and TSSF, the TSSF shall send an HTTP POST message including the St session ID as a path element of the notification URI. + +Every HTTP message contains the specific communication information required for this case in its body. + +### 5.3.1 Methods + +Methods indicate to the server what action has to be performed. Every HTTP request message has a method. The following HTTP methods as defined in IETF RFC 7231 [23] and IETF RFC 5789 [12] can be used: + +- POST: + - Used to create a resource state. The request URI defines the address responsible for the creation of the resource. + - Used to report traffic steering rule enforcement failures from the TSSF to the PCRF. The notification report is provided in the body of the message. The request URI defines the address of the impacted resource. +- PUT: Used to replace a resource state. The full state of the resource is provided in the body of the message. The request URI defines the resource which will be replaced. +- PATCH: The PATCH method applies partial modifications to a resource. The request URI defines the resource which will be modified. +- GET: Used to retrieve a resource state. The request URI defines the resource which is queried. The server returns the resource state representation within the body of the response. +- DELETE: Used to delete a resource state. The request URI defines the resource which will be deleted. + +Every HTTP request results in a response message that comes back with a status code and further information in its body, if required. The PCRF waits for this response before initiating a further request for the same resource. + +### 5.3.2 Resources and URI design + +The St session is a RESTful resource that shall be identified by a URI. + +The URI design shall be based on the structure defined in IETF RFC 3986 [13]: + +``` +scheme ":" hier-part [ "?" query ] [ "#" fragment ] +hier-part = "//" authority path-abempty +/ path-absolute +/ path-rootless +/ path-empty +``` + +The scheme may be HTTP or HTTPS for the REST St interface. Within a scheme the definition of names shall follow the rules of HTTP URIs. Host and port are the main parts of the authority. The path element identifies the resources. + +For the REST St interface, the following required parts of the URI shall be used as follows: + +- scheme: The application delivery layer protocol "http" or "https". +- authority: It includes the server address and optionally a port as follows: host [":" port] +- path-absolute: The path-absolute should have the following ABNF: "/" mainapp "/" mainresource ["/" resourcepath], where for this release, "mainapp" is "stapplication", "mainresource" is "sessions" and "resourcepath" contains the path to identify a session resource, which in this release is the St Session ID as defined in subclause 5.3.4. + +NOTE: A different path can be used when the Resource URI is preconfigured in the PCRF. + +An example of the URI to identify the "sessions" main resource is: . + +### 5.3.3 HTTP request/response formats + +#### 5.3.3.1 General + +Session establishment, modification, termination and query procedures are performed through HTTP transactions consisting of a request initiated by the PCRF and its corresponding response provided by the TSSF. + +Table 5.3.3.1-1 summarizes the content of the requests and responses. More detailed information is specified in the corresponding subclauses as indicated in the table. + +Table 5.3.3.1-1: St requests/response summary table + +| Method | Resource URI's path
(NOTE 1) | Clause
Defined | Request body | Response body | +|--------|---------------------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| POST | /stapplication/sessions | 5.3.3.2 | Content-Type: application/json
The PCRF shall include the state of the session resource using the schema defined in Annex B.1. | Successful response: The TSSF may include informational data in the body of the response as per Annex B.2
Error response: The TSSF should include error data in the body of the response as per Annex B.2 | +| PUT | /stapplication/sessions/{stsessionid} | 5.3.3.3 | Content-Type: application/json
The PCRF shall include the state of the session resource using the schema defined in Annex B.1. | Successful response: The TSSF may include informational data in the body of the response as per Annex B.2
Error response: The TSSF should include error data in the body of the response as per Annex B.2 | +| PATCH | /stapplication/sessions/{stsessionid} | 5.3.3.4 | Content-Type: application/json-patch+json
The PCRF shall include the partial modifications to the state of the session resource using the schema defined in Annex B.1. | Successful response: The TSSF may include informational data in the body of the response as per Annex B.2
Error response: The TSSF should include error data in the body of the response as per Annex B.2 | +| DELETE | /stapplication/sessions/{stsessionid} | 5.3.3.5 | None | Successful response: The TSSF may include informational data in the body of the response as per Annex B.2
Error response: The TSSF should include error data in the body of the response as per Annex B.2 | +| GET | /stapplication/sessions/{stsessionid} | 5.3.3.6 | None | Successful response: The TSSF shall include the representation of the corresponding session resource in the body of the response as per Annex B.2
Error response: The TSSF should include error data in the body of the response as per Annex B.2 | +| POST | /{notificationbaseurl}/{stsessionid} | 5.3.3.7 | Content-Type: application/json
The TSSF shall report traffic steering rule enforcement failures to the PCRF using the JSON format definition in Annex B.4 | Successful response: The PCRF may include informational data in the body of the response as per Annex B.2
Error response: The PCRF should include error data in the body of the response as per Annex B.2 | + +NOTE: A different path from /stapplication/sessions/ may be used when it is configured in the PCRF. In that case the "path" part set in the different methods should use the configured one. + +#### 5.3.3.2 POST /stapplication/sessions + +The establishment of a session shall be performed by the PCRF by using the POST method as follows: + +- the request URI formatted as defined in subclause 5.3.2 with the "path" part set to: /stapplication/sessions. +- the Content-Type header field set to "application/json" + +- the body of the message encoded in JSON format as defined in Annex B.1, including the "session-id" field allocated by the PCRF. + +The PCRF sets the URI based on the pre-configuration at the PCRF. + +If the PCRF supports the Notification feature, it shall follow the procedures defined in subclause 5.3.6.1 to advertise support of the feature. In addition, the PCRF shall include the 3gpp-Notification-Base-URL header as defined in subclause 5.3.7.4. + +Upon receipt of the HTTP POST, the TSSF shall respond to the PCRF indicating whether the creation of the resource was successful or not using one of the HTTP status codes as defined in subclause 5.3.5. If the resource creation is successful, the TSSF shall respond with an HTTP 201 (Created) status code, including a Location header field containing the URI for the created session resource based on the St Session ID as defined in subclause 5.3.4. If the creation of the session resource was not successful, the TSSF shall indicate the reason using an appropriate HTTP status code for the St interface as defined in subclause 5.3.5 and optionally additional information in the body of the response as defined in Annex B.2. + +If both the PCRF and TSSF support the Notification feature, the TSSF shall remember the value of the 3gpp-Notification-Base-URL for the lifetime of the corresponding St session and shall initiate a TCP connection towards the PCRF (if it is not already established) based on the hostname and optional port elements of the 3gpp-Notification-Base-URL. + +NOTE: Network deployment scenario with overlapping IP address assignment where the PCRF connects to multiple PCEFs connecting to the same PDN and where these multiple PCEFs connect to the same TSSF is not supported in this release. + +Below is an example of an HTTP POST and a corresponding successful response: + +POST /stapplication/sessions HTTP/1.1 + +Host: tssfserver.example.com + +3gpp-Notification-Base-URL: + +3gpp-Optional-Features: Notification + +Content-Type: application/json + +Content-Length: ... + +``` +{ + "session-id": "pcrf.example.com;378388838383;123232", + "ue-ipv4": "10.0.0.2", + "called-station-id": "apncompany.com", + "tsrules": { + "ts-rule-3": { + "ts-rule-name": "ts-rule-3", + "tdf-application-identifier": "ftp-download", + "precedence": 1, + "ts-policy-identifier-dl": "firewall" + } + } +} +``` + +Here is an example of a successful response: + +HTTP/1.1 201 Created + +Location: http:// tssfserver.example.com/stapplication/sessions/pcrf.example.com;3783888838383;123232 + +Date: Mon, 23 Apr 2012 17:10:00 GMT + +Server: tssf.example.com + +3gpp-Accepted-Features: Notification + +Content-Type: application/json + +``` +{ + "success-message": "Session was created successfully.", +} +``` + +#### 5.3.3.3 PUT /stapplication/sessions/{stsessionid} + +The full modification of a session resource may be performed by the PCRF using the PUT method. In this case, the PCRF shall send an HTTP PUT request as follows: + +- the request URI formatted as defined in subclause 5.3.2 with the "path" part set to: /stapplication/sessions/{stsessionid}, where the stsessionid is the St Session ID as defined in subclause 5.3.4. +- the Content-Type header field set to "application/json" +- the body of the message encoded in JSON format as defined in Annex B.1 specifying the full representation of the session resource + +Upon receipt of the HTTP PUT, the TSSF shall respond to the PCRF indicating whether the modification of the resource was successful or not using one of the HTTP status codes as defined in subclause 5.3.5. If the resource modification is successful, the TSSF shall respond with an HTTP 200 OK status code if it includes optional informational data in the body of the response as per Annex B.2 or HTTP 204 No Content status code otherwise. If the modification of the session resource was not successful, the TSSF shall indicate the reason using an appropriate HTTP status code for the St interface as defined in subclause 5.3.5 and optionally additional information in the body of the response as defined in Annex B.2. + +Below is an example of an HTTP PUT: + +PUT /stapplication/sessions/pcrf.example.com;3783888838383;123232 HTTP/1.1 + +Host: tssfserver.example.com + +Content-Type: application/json + +Content-Length: ... + +``` +{ + "session-id": "pcrf.example.com;3783888838383;123232", + "ue-ipv4": "10.0.0.2", + "tsrules": { + "ts-rule-1": { + "ts-rule-name": "ts-rule-1", + "tdf-application-identifier": "ftp-download", + } + } +} +``` + +``` + "precedence": 1, + "ts-policy-identifier-dl": "firewall" +}, +"ts-rule-2": { + "ts-rule-name": "ts-rule-2", + "tdf-application-identifier": "application-x", + "precedence": 2, + "ts-policy-identifier-dl": "firewall" +} +} +} +``` + +Here is an example of a successful response: + +HTTP/1.1 200 OK + +Date: Mon, 23 Apr 2012 17:11:00 GMT + +Server: tssf.example.com + +Content-Type: application/json + +``` +{ + "success-message": "Session was updated successfully.", +} +``` + +#### 5.3.3.4 PATCH /stapplication/sessions/{stsessionid} + +The partial modification of a session resource may be performed by the PCRF using the PATCH method as defined in IETF RFC 5789 [12]. In this case, the PCRF shall send an HTTP PATCH request as follows: + +- the request URI formatted as defined in subclause 5.3.2 with the "path" part set to: /stapplication/sessions/{stsessionid}, where the stsessionid is the St Session ID as defined in subclause 5.3.4. +- the Content-Type header field set to "application/json-patch+json" +- the body of the message shall be encoded using the JSON Patch format as defined in IETF RFC 6902 [14]. The following operations from [14] may be used: + - add: to create a new traffic steering rule. + - remove: to delete a traffic steering rule. + - replace: to replace an existing rule with a new definition. + +Upon receipt of the HTTP PATCH, the TSSF shall respond to the PCRF indicating whether the modification of the resource was successful or not using one of the HTTP status codes as defined in subclause 5.3.5. If the resource modification is successful, the TSSF shall respond with an HTTP 200 OK status code if it includes optional informational data in the body of the response as per Annex B.2 or HTTP 204 No Content status code otherwise. If the modification of the session resource was not successful, the TSSF shall indicate the reason using an appropriate HTTP + +status code for the St interface as defined in subclause 5.3.5 and optionally additional information in the body of the response as defined in Annex B.2. + +Below is an example of an HTTP PATCH that modifies a traffic steering rule and deletes another one: + +PATCH /stapplication/sessions/pcrf.example.com;378388838383;123232 HTTP/1.1 + +Host: tssfserver.example.com + +Content-Type: application/json-patch+json + +Content-Length: ... + +``` +[ + { + "op": "replace", + "path": "/tsrules/ts-rule-1", + "value": { + "ts-rule-name": "ts-rule-1", + "tdf-application-identifier": "ftp-download", + "precedence": 1, + "ts-policy-identifier-dl": "firewall2" + } + }, + { + "op": "remove", + "path": "/tsrules/ts-rule-2", + } +] +``` + +Here is an example of a successful response:HTTP/1.1 200 OK + +Date: Mon, 23 Apr 2012 17:12:00 GMT + +Server: tssf.example.com + +Content-Type: application/json + +``` +{ + "success-message": "Session was patched successfully.", +} +``` + +#### 5.3.3.5 DELETE /stapplication/sessions/{stsessionid} + +To delete an St session, the PCRF shall send an HTTP DELETE request to the TSSF as follows: + +- the request URI formatted as defined in subclause 5.3.2 with the "path" part set to: `/stapplication/sessions/{stsessionid}`, where the `stsessionid` is the St Session ID as defined in subclause 5.3.4. + +Upon receipt of the HTTP DELETE, the TSSF shall respond to the PCRF indicating whether the deletion of the resource was successful or not using one of the HTTP status codes as defined in subclause 5.3.5. If the resource deletion is successful, the TSSF shall respond with an HTTP 200 OK status code if it includes optional informational data in the body of the response as per Annex B.2 or HTTP 204 No Content status code otherwise. If the deletion of the session resource was not successful, the TSSF shall indicate the reason using an appropriate HTTP status code for the St interface as defined in subclause 5.3.5 and optionally additional information in the body of the response as defined in Annex B.2. + +Below is an example of an HTTP DELETE: + +DELETE /stapplication/sessions/pcrf.example.com;3783888838383;123232 HTTP/1.1 + +Host: tssfserver.example.com + +Here is an example of a successful response: + +HTTP/1.1 204 No Content + +Date: Mon, 23 Apr 2012 17:15:00 GMT + +Server: tssf.example.com + +#### 5.3.3.6 GET /stapplication/sessions/{stsessionid} + +To query the state of an St session resource, the PCRF shall send an HTTP GET request to the TSSF as follows: + +- the request URI formatted as defined in subclause 5.3.2 with the "path" part set to: `/stapplication/sessions/{stsessionid}`, where the `stsessionid` is the St Session ID as defined in subclause 5.3.4. + +Upon receipt of the HTTP GET, the TSSF shall respond to the PCRF indicating whether the querying of the resource was successful or not using one of the HTTP status codes as defined in subclause 5.3.3. If the resource exists, the TSSF shall respond with an HTTP 200 OK status code and include the session representation state within the body of the response as defined in Annex B.2. The TSSF shall also include the Content-Type header field set to "application/json". + +The TSSF shall also include the set of features it supports in common with the PCRF within the "3gpp-Accepted-Features" HTTP header in the response to the HTTP GET. + +Below is an example of an HTTP GET: + +GET /stapplication/sessions/pcrf.example.com;3783888838383;123232 HTTP/1.1 + +Host: tssfserver.example.com + +Here is an example of a successful response : + +HTTP/1.1 200 OK + +Server: tssfserver.example.com + +Content-Type: application/json + +Content-Length: ... + +``` +{ + "session-id": "pcrf.example.com;3783888838383;123232", +``` + +``` +"ue-ipv4": "10.0.0.2", +"called-station-id": "apncompany.com", +"tsrules": { + "ts-rule-1": { + "ts-rule-name": "ts-rule-1", + "tdf-application-identifier": "ftp-download", + "precedence": 1, + "ts-policy-identifier-dl": "firewall" + }, + "ts-rule-2": { + "ts-rule-name": "ts-rule-2", + "tdf-application-identifier": "application-x", + "precedence": 2, + "ts-policy-identifier-dl": "firewall" + } +} +} +``` + +#### 5.3.3.7 POST /{notificationbaseurl}/{stsessionid} + +If the notification feature is supported, the TSSF shall inform the PCRF of state changes related to a session resource or sub resources (e.g. traffic steering rules). The TSSF does so by sending an HTTP POST request as follows: + +- the request URI formatted as defined in subclause 5.3.2 with the "path" part set to: /{notificationbaseurl}/{stsessionid}, where the "stsessionid" is the St Session ID as defined in subclause 5.3.4, and the "notificationbaseurl" is set to the value of the 3gpp-Notification-Base-URL provided by the PCRF. +- the Content-Type header field set to "application/json" +- the body of the message encoded in JSON format as defined in Annex B.4 specifying the representation of the notification report. + +Upon receipt of the notification HTTP POST, the PCRF shall respond to the TSSF with one of the HTTP status codes as defined in subclause 5.3.5. If the PCRF is able to successfully process the request, the PCRF shall answer with an HTTP 200 OK status code if it includes optional informational data in the body of the response as per Annex B.2 or HTTP 204 No Content status code otherwise. If the PCRF cannot successfully process the request, the PCRF shall indicate the reason using an appropriate HTTP status code for the St interface as defined in subclause 5.3.5 and optionally include additional information in the body of the response as defined in Annex B.2. + +Below is an example of an HTTP POST used for notification of traffic steering rule enforcement failure. + +``` +POST /stapplication/notification/pcrf.example.com;378388838383;123232 HTTP/1.1 +``` + +``` +Host: perfserver.example.com +``` + +``` +Content-Type: application/json +``` + +``` +Content-Length: ... +``` + +``` +{ + "notifications": [ + { + "notification-message": "Traffic steering rules became inactive.", + "notification-type": "application", + "notification-tag": "TS_RULE_EVENT", + "notification-info": { + "ts-rule-reports": [ + { + "resource-paths": [ + "/tsrules/ts-rule-1", + "/predefined-tsrules/ts-rule-2", + "/predefined-group-of-tsrules/group-rules-1" + ], + "rule-status": "INACTIVE", + "rule-failure-code": "RESOURCES_LIMITATION" + } + ] + } + } + ] +} +``` + +Here is an example of a successful response: + +HTTP/1.1 200 OK + +Date: Mon, 23 Apr 2012 17:11:00 GMT + +Server: perfserver.example.com + +Content-Type: application/json + +``` +{ + "success-message": "Notification was processed successfully.", +} +``` + +### 5.3.4 St session ID + +The PCRF shall allocate an St Session ID that is used to uniquely identify the St session resource between the PCRF and TSSF. The St Session ID is provided as part of the session resource representation within the body of the HTTP message and shall remain unmodified during the lifetime of the St session resource. If the session resource is successfully created at the TSSF, the TSSF shall include the St session ID in the path element of an HTTP request URI to address the corresponding session resource. + +NOTE: The PCRF allocates the St Session ID as opposed to the TSSF to avoid creating duplicate sessions at the TSSF in case an HTTP POST message is received twice by the TSSF (e.g. due to a retry by the PCRF). The PCRF ensures that the St Session ID is globally unique as described in this subclause to avoid conflicts at the TSSF. + +The Session ID shall be globally and eternally unique. The Session ID includes a mandatory portion and an implementation specific portion. + +The mandatory portion shall start with the PCRF's FQDN [8]. The remainder of the Session ID is delimited by a ';' character and may be any sequence that the PCRF can guarantee to be eternally unique as follows: + +; + +The implementation specific sequence should follow the recommended implementation specific portion of the Session-Id AVP as defined in section 8.8 of IETF RFC 6733 [21]. + +Here is an example of the Session ID: pcrf123.acme.com;1876543210;523. Here is an example of a corresponding session URI: http://tssfserver.example.com/stapplication/sessions/pcrf123.acme.com;1876543210;523 + +Because the Session ID is included as a path element of the request URI, it shall follow the implementation-specific syntax standardized for path elements of URLs as defined in [6]. + +NOTE: Characters in the reserved set are protected from normalization and are therefore safe to be used by scheme-specific and producer-specific algorithms for delimiting data subcomponents within a URI [6]. + +### 5.3.5 HTTP status codes + +A subset of the HTTP status codes as defined in IETF RFC 7231 [23] are applicable to the REST based St interface. Table 5.3.5-1 lists the applicable status codes for the St interface for the current release. Note that if the PCRF or TSSF receive a response with a status code not listed in the table below, they shall treat it based on the class of the status code as defined in IETF RFC 7231 [23]. + +**Table 5.3.5-1: St HTTP status codes** + +| Status Code | Description | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 200 OK | The HTTP request has succeeded. The information returned with the response is dependent on the method used in the request. | +| 201 Created | The HTTP POST request has been fulfilled and resulted in a new resource being created at the TSSF. | +| 204 No Content | The recipient has fulfilled the request but does not need to return an entity-body. | +| 400 Bad Request | The request could not be processed due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing). | +| 403 Forbidden | The recipient understood the request, but is refusing to fulfill it. | +| 404 Not Found | The recipient has not found any resources matching the Request-URI. | +| 405 Method Not Allowed | The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. | +| 408 Request Timeout | The recipient did not respond to the request within the time that the sender is prepared to wait. The sender may repeat the request without modifications at any later time. | +| 412 Precondition Failed | The precondition given in one or more of the request-header fields evaluated to false when it was tested on the recipient. | +| 413 Payload Too Large | The recipient is refusing to process a request because the request entity is larger than the recipient is willing or able to process. | +| 414 URI Too Long | The recipient is refusing to service the request because the Request-URI is longer than the recipient is willing to interpret. | +| 500 Internal Server Error | The recipient encountered an unexpected condition which prevented it from fulfilling the request. | +| 501 Not Implemented | The recipient does not support the functionality required to fulfill the request. | +| 503 Service Unavailable | The recipient is currently out of service. | + +### 5.3.6 Feature negotiation + +#### 5.3.6.1 General + +The REST based St interface needs to provide a mechanism to advertise required and optional features supported by both the PCRF and TSSF for interoperability reasons as the functionality of the REST St based interface is augmented. + +The PCRF shall include in the HTTP POST the set of supported features as follows: + +- if a feature is required for the proper operation of the St session, it shall be included within the 3gpp-Required-Features header; +- if a feature is optional for the proper operation of the St session, it shall be included within the 3gpp-Optional-Features header. + +The TSSF shall include, within the 3gpp-Accepted-Features header in the response to the HTTP POST, the set of features it supports in common with the PCRF. + +If the TSSF does not support any of the required features advertised by the PCRF within the 3gpp-Required-Features header, the TSSF shall reject the HTTP POST with an HTTP 412 Precondition Failed status code and shall include the commonly supported features with the PCRF within the 3gpp-Accepted-Features. + +If the TSSF requires certain features to be supported that aren't advertised by the PCRF, the TSSF shall reject the HTTP POST with an HTTP 412 Precondition Failed status code and shall include the commonly supported features with the PCRF within the 3gpp-Accepted-Features and the required features in the 3gpp-required-features. + +If the PCRF and TSSF successfully negotiate supported features, the list of commonly supported features shall be applicable for the lifetime of the St session. Features that are not advertised as supported shall not be used within the lifetime of the St session. + +The table below defines the features applicable to the REST St interface. + +**Table 5.3.6.1-1: Features used in REST St Protocol** + +| Feature | M/O | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------------------------------------------------------------------------------------------------| +| Notification | O | This feature indicates the support of the HTTP notification procedure from the TSSF to the PCRF. | +| Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification".
M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O") in this 3GPP Release.
Description: A clear textual description of the feature. | | | + +### 5.3.7 HTTP custom headers + +This subclause defines any new HTTP custom headers introduced by this specification. + +#### 5.3.7.1 3gpp-Optional-Features + +This header is used by the PCRF to advertise the optional features that are supported by the PCRF. + +The encoding of the header follows the ABNF as defined in IETF RFC 7231 [23]. + +3gpp-Optional-Features = "3gpp-Optional-Features" ":" 1#token + +An example is: 3gpp-Optional-Features: feature1, feature2 + +#### 5.3.7.2 3gpp-Required-Features + +This header is used by the PCRF to announce the mandatory features that must be supported in TSSF. + +This header is also used by the TSSF to indicate the missing features that must be supported in PCRF. + +The encoding of the header follows the ABNF as defined in IETF RFC 7231 [23]. + +3gpp-Required-Features = "3gpp-Required-Features" ":" 1#token + +An example is: 3gpp-Required-Features: feature1, feature2 + +#### 5.3.7.3 3gpp-Accepted-Features + +The header is used by the TSSF to confirm the commonly supported set of features with the PCRF. + +The encoding of the header follows the ABNF as defined in IETF RFC 7231 [23]. + +3gpp-Accepted-Features = "3gpp-Accepted-Features" ":" 1#token + +An example is: 3gpp-Accepted-Features: feature1, feature2 + +#### 5.3.7.4 3gpp-Notification-Base-URL + +This header is used by the PCRF to provide the notification base URL. + +The encoding of the header follows the ABNF as defined in IETF RFC 7231 [23]. + +3gpp-Notification-Base-URL = "3gpp-Notification-Base-URL" ":" 1#token + +An example is: 3gpp-Notification-Base-URL: http://pcrfserver.example.com:8080/stapplication/notification + +## 5.4 Specific application communication + +### 5.4.1 General + +Specific application communication represents the presentation of application data structures by transforming data into the form that the application accepts. It establishes the context between application-layer entities. + +Note: This release only supports the content type JSON + +### 5.4.2 Content type + +The body of HTTP messages shall be in JSON format. The content of the JSON text is defined in subclause 5.4.3 and Annex B. + +The MIME media type that shall be used within the Content-Type header field is "application/json" as defined in IETF RFC 7159 [10]. + +### 5.4.3 JSON session fields + +#### 5.4.3.1 General + +Table 5.4.3.1.1 describes the JSON fields used within the body of the HTTP messages representing the session information. The table includes the information about the name of the field, the type of the fields and the applicability of the JSON field. + +Table 5.4.3.1.1: St Specific JSON fields + +| Field Name | Subclause defined | JSON Value Type (NOTE 1) | JCR Type (NOTE 2) | Applicability (NOTE 3) | +|-----------------------------|-------------------|--------------------------|-------------------------------------------------------|------------------------| +| called-station-id | 5.4.3.20 | string | string | | +| session-id | 5.4.3.2 | string | string | | +| ue-ipv4 | 5.4.3.3 | string | ipv4 | | +| ue-ipv6-prefix | 5.4.3.4 | string | ipv6 | | +| tsrules | 5.4.3.5 | object | object | | +| ts-rule-name | 5.4.3.6 | string | string | | +| Precedence | 5.4.3.7 | number | number:
0..4294967295 | | +| tdf-application-identifier | 5.4.3.8 | string | string | | +| flow-information | 5.4.3.9 | array | array | | +| flow-description | 5.4.3.10 | string | string | | +| tos-traffic-class | 5.4.3.11 | string | /'^[0-9A-Fa-f]{4}\$/'
(NOTE 4) | | +| security-parameter-index | 5.4.3.12 | string | /'^[0-9A-Fa-f]{8}\$/'
(NOTE 4) | | +| flow-label | 5.4.3.13 | string | /'^[0-9A-Fa-f]{6}\$/'
(NOTE 4) | | +| flow-direction | 5.4.3.14 | string | "BIDIRECTIONAL"
"UPLINK"
"DOWNLINK"
(NOTE 5) | | +| ts-policy-identifier-dl | 5.4.3.15 | string | string | | +| ts-policy-identifier-ul | 5.4.3.16 | string | string | | +| predefined-tsrules | 5.4.3.17 | object | object | | +| predefined-group-of-tsrules | 5.4.3.18 | object | object | | +| ts-rule-base-name | 5.4.3.19 | string | string | | + +NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [15]. +NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [16]. +NOTE 3: Fields marked with a supported feature are applicable as described in subclause 5.3.6. +NOTE 4: The regular expression for a string type. +NOTE 5: The quoted strings for a string type. + +#### 5.4.3.2 session-id + +The session-id field is of type string, and contains the session id allocated by the PCRF. The session id format is defined in subclause 5.3.4. + +#### 5.4.3.3 ue-ipv4 + +The ue-ipv4 field is of type string and ip4 literal as defined in IETF draft-newton-json-content-rules [16]. + +#### 5.4.3.4 ue-ipv6-prefix + +The ue-ipv6-prefix field is of type string and ipv6 literal as defined in IETF draft-newton-json-content-rules [16]. The PCRF uses it to indicate the IPv6 prefix allocated for the user. + +#### 5.4.3.5 tsrules + +The tsrules field is of type object. It contains all of the dynamic traffic steering rules defined in the JSON body. + +The following defines the content of the dynamic traffic steering rule: + +The ts-rule-name field shall be included within the dynamic traffic steering rule. + +A precedence value may be included. + +Either flow-information(s) or the tdf-application-identifier field shall be included within the dynamic traffic steering rule. + +The ts-policy-identifier-ul field and/or the ts-policy-identifier-dl field shall be included. If the traffic steering policies are identical in both downlink and uplink directions, the values of the ts-policy-identifier-ul field and the ts-policy-identifier-dl field shall be identical. + +Below are the JCR for the dynamic traffic steering rule: + +``` +$tsrule = // : { + $ts-rule-name, + $precedence ?, + ( $flow-information | $tdf-application-identifier ), + ( $ts-policy-identifier-ul | $ts-policy-identifier-dl | ( $ts-policy-identifier-ul, $ts-policy-identifier-dl ) ) +} +``` + +#### 5.4.3.6 ts-rule-name + +The ts-rule-name is of type string, and it defines a name for traffic steering rule. For traffic steering rules provisioned by the PCRF, it uniquely identifies a traffic steering rule within one St session. For traffic steering rules pre-defined at the TSSF, it uniquely identifies a traffic steering rule within the TSSF. + +#### 5.4.3.7 precedence + +The precedence is of type number. Its value ranges from 0 to 4294967295. + +Within the tsrule JSON content, the precedence field determines the order for the service data flow detection/the application detection at the TSSF to perform traffic steering. A traffic steering rule with a lower precedence value shall be applied prior to a traffic steering rule with a higher precedence value. + +NOTE: The precedence value range defined within the traffic steering rule is operator configurable. + +#### 5.4.3.8 tdf-application-identifier + +The tdf-application-identifier is of type string. It references the application detection filter defined at the TSSF. + +#### 5.4.3.9 flow-information + +The flow-information field is of type array. It is sent from the PCRF to the TSSF and contains the information for a single IP flow packet filter. + +The flow-description, a tos-traffic-class, security-parameter-index and flow-label specify the parameters to be used for matching payload packets. One of these fields shall be present in the object. The flow-direction field shall also be included. + +The JCR for the flow-information is as follows: + +``` +$flow-information = "flow-information" : [ +{ + $flow-description ?, + $tos-traffic-class ?, + $security-parameter-index ?, + $flow-label ?, + $flow-direction +``` + +} + + +] + +#### 5.4.3.10 flow-description + +The flow-description field is of type string, it defines a packet filter for an IP flow. + +The content has the same encoding as the IPFilterRule AVP value as defined in IETF RFC 6733 [21]. All limitations applicable to the Flow-Description AVP in subclause 5.4.2 of 3GPP TS 29.212 [17] apply to this field. + +#### 5.4.3.11 tos-traffic-class + +The tos-traffic-class field is of type string. It is encoded on two octets, and represented as a hex string. The first octet contains the IPv4 Type-of-Service or the IPv6 Traffic-Class field and the second octet contains the ToS/Traffic Class mask field. When used for traffic detection, it defines the packet marking information used for traffic detection in the TSSF. + +#### 5.4.3.12 security-parameter-index + +The security-parameter-index field is of type string, and it contains the security parameter index of the IPSec packet. + +#### 5.4.3.13 flow-label + +The flow-label field is of type string, and it contains the IPv6 flow label header field. + +#### 5.4.3.14 flow-direction + +The flow-direction field is of type string with three enumerations. It indicates the direction(s) that a filter is applicable, downlink only, uplink only or both down- and uplink (bidirectional). + +##### DOWNLINK + +The corresponding filter applies for traffic to the UE. + +##### UPLINK + +The corresponding filter applies for traffic from the UE. + +##### BIDIRECTIONAL + +The corresponding filter applies for traffic both to and from the UE. + +#### 5.4.3.15 ts-policy-identifier-dl + +The ts-policy-identifier-dl is of type string and contains a reference to a pre-configured traffic steering policy at the TSSF in the downlink direction. + +#### 5.4.3.16 ts-policy-identifier-ul + +The ts-policy-identifier-ul is of type string and contains a reference to a pre-configured traffic steering policy at the TSSF in the uplink direction. + +#### 5.4.3.17 predefined-tsrules + +The predefined-tsrules contains all of the predefined traffic steering rules in the session. + +The ts-rule-name field uniquely identifies the traffic steering rule defined at the TSSF. + +The JCR definition for the predefined traffic steering rule is as follows: + +\$predefined-tsrule = // : { + +``` + + ts-rule-name + } + +``` + +#### 5.4.3.18 predefined-group-of-tsrules + +The predefined-group-of-tsrules field is of type object and contains the groups of the predefined traffic steering rules in the session. + +The ts-rule-base-name field uniquely identifies the group of predefined traffic steering rules at the TSSF. + +The JCR definition for the group of the dynamic traffic steering rules: + +``` + +$predefined-group-of-tsrule = // : { + ts-rule-base-name +} + +``` + +#### 5.4.3.19 ts-rule-base-name + +The ts-rule-base-name field is of type string, and it indicates the name of a predefined group of traffic steering rules residing at the TSSF. + +#### 5.4.3.20 called-station-id + +The called-station-id is of type string, and it defines the address the user is connected to (i.e. the PDN identifier). For GPRS and EPS the APN. When used to contain the APN, the APN is composed of the APN Network Identifier only, or the APN Network Identifier and the APN Operator Identifier as specified in 3GPP TS 23.003 [20], subclause 9.1. The inclusion of the APN Operator Identifier can be configurable. + +### 5.4.4 JSON errors and informational response fields + +#### 5.4.4.1 General + +Table 5.4.4.1.1 describes the JSON fields defined for the errors and informational responses including their types and the field names. + +**Table 5.4.4.1.1: JSON fields for errors and informational response** + +| Field Name | Subclause defined | JSON Value Type (NOTE 1) | JCR Type (NOTE 2) | +|-----------------|-------------------|--------------------------|-----------------------------------------------------------------| +| errors | 5.4.4.2 | array | array | +| error-type | 5.4.4.3 | string | "application"
"interface"
"server"
"other"
(NOTE 3) | +| error-message | 5.4.4.4 | string | string | +| error-tag | 5.4.4.5 | string | string | +| error-path | 5.4.4.6 | string | string | +| error-info | 5.4.4.7 | object | object | +| success-message | 5.4.4.8 | string | string | +| success-path | 5.4.4.9 | string | string | +| success-info | 5.4.3.10 | object | object | + +NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [10]. +NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [16]. +NOTE 3: The quoted strings for a string type. + +#### 5.4.4.2 errors + +The errors field is of type array, and it contains a list of errors. Each error is defined as an object in the array. This field shall be present when the TSSF responds with error(s) back to an HTTP request initiated by the PCRF. + +An error object shall contain the error-type field and the error-message. + +Optionally, it may include the error-tag field, error-path field and error-info field for further details. The error tag is used to classify a special error from other errors. The error-path is used to identify which resource has the error. The error-info is provided for additional information. + +The JCR format: + +``` +e + +$errors = "errors" : [ + { + $error-type, + $error-message, + $error-tag ?, + $error-path ?, + $error-info ? + } + +] +``` + +#### 5.4.4.3 error-type + +The error-type field is of type string. It can be one of 'application', 'interface', 'server' and 'other'. + +When an error is related to the application processing in the TSSF, the error type shall be specified as 'application'. When the error is a protocol compliance error, 'interface' shall be used. A server failure is represented with the 'server' error type. For all other errors, the 'other' error type shall be used. + +#### 5.4.4.4 error-message + +The error-message field is of type string. It is a textual description of the error. + +#### 5.4.4.5 error-tag + +The error-tag field is of type string. It defines a tag for a particular error. + +##### TS\_RULE\_EVENT + +This error-tag shall be used when the traffic steering rules cannot be installed/activated at the TSSF. Affected traffic steering rules shall be provided in the error-info with a sub field named ts-rule-reports including the reason and status of the rules as described in subclause 5.4.5. + +#### 5.4.4.6 error-path + +The error-path field is of type string. It shall contain a JSON pointer as defined in IETF RFC 6901 [15] pointing to a resource where the error occurs. + +#### 5.4.4.7 error-info + +The error-info field is defined as an object type. It represents informational details regarding the error. + +#### 5.4.4.6 success-message + +The success-message is of type string. When included in the JSON body of an HTTP response, it shall be included under the root level of the JSON content. + +#### 5.4.4.7 success-path + +The success-path field is of type string. It is a JSON pointer as defined in IETF RFC 6901 [15] pointing to the resource that was successfully operated on. It is an optional root level field provided along with a success-message field. + +#### 5.4.4.8 success-info + +The success-info field is defined as an object type. It may include any additional information under the root level of the JSON content for an informational response. + +### 5.4.5 JSON report fields + +#### 5.4.5.1 General + +Table 5.4.5.1.1 describes the JSON fields defined for the report information objects which are included in the error-info field or the notification-info field. + +**Table 5.4.5.1.1: JSON fields for Report from the TSSF** + +| Field Name | Subclause defined | JSON Value Type (NOTE 1) | JCR Type (NOTE 2) | +|---------------------------------------------------------------------------------|-------------------|--------------------------|-------------------| +| ts-rule-reports | 5.4.5.2 | array | array | +| resource-paths | 5.4.5.3 | array | array | +| rule-status | 5.4.5.4 | string | string | +| rule-failure-code | 5.4.5.5 | string | string | +| NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [10]. | | | | +| NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [16]. | | | | + +#### 5.4.5.2 ts-rule-reports + +The ts-rule-reports field is of type array and it contains a list of traffic steering rule reports. + +The ts-rule-reports field can be used in an HTTP response to report failures in the installation/activation of traffic steering rules. In this case, it shall be provided as a sub field of the error-info field. + +The ts-rule-reports field can also be used in a HTTP request from the TSSF to notify the PCRF about enforcement failures of traffic steering rules. In this case, it shall be provided as a sub field of the notification-info field. + +Multiple traffic steering rule report instances shall be provided within the ts-rule-reports field if different rule-status or rule-failure-code values are applicable within the same HTTP response or notification. + +A report instance shall contain the resource-paths, rule-status and rule-failure-code fields. + +The JCR format for the ts-rule-reports is: + +\$ts-rule-reports = "ts-rule-reports" : [ + +``` +{ + $resource-paths, + $rule-status, + $rule-failure-code +``` + +} + + +] + +#### 5.4.5.3 resource-paths + +The resource-paths field is of type array of strings. Each string shall be a JSON pointer as defined in IETF RFC 6901 [15]. + +Each JSON pointer within the resource-paths field shall be a reference to a specific traffic steering rule or to a group of traffic steering rules which cannot be installed/activated or enforced at the TSSF. + +#### 5.4.5.4 rule-status + +The rule-status is of type string and shall contain one of the string representations of the PCC-Rule-Status AVP values as defined in subclause 5.3.19 of 3GPP TS 29.212 [17]. + +NOTE: For the current release, only the INACTIVE value is used. + +#### 5.4.5.5 rule-failure-code + +The rule-failure-code is of type string. + +The following values defined in the Rule-Failure-Code AVP in subclause 5.3.38 of 3GPP TS 29.212 [17] are applicable for traffic steering rule errors. + +UNKNOWN\_RULE\_NAME + +GW/PCEF\_MALFUNCTION + +RESOURCES\_LIMITATION + +MISSING\_FLOW\_INFORMATION + +INCORRECT\_FLOW\_INFORMATION + +TDF\_APPLICATION\_IDENTIFIER\_ERROR + +FILTER\_RESTRICTIONS + +The following value defined in the Rule-Failure-Code AVP is reused for traffic steering rule errors, however with a different explanation: + +RESOURCE\_ALLOCATION\_FAILURE + +This value is used to indicate that the traffic steering rule could not be successfully installed or maintained since the resources or services of the traffic steering control specified by the rule cannot be reserved in the TSSF and/or the (S)Gi-LAN; or those resources or services were released in the TSSF and/or the (S)Gi-LAN, for example, due to the switch eviction mechanism. + +In addition, the following values are added: + +RESOURCE\_TIMEOUT + +This value is used to indicate that the traffic steering rule could not be successfully installed or maintained since the booked resources or services of the traffic steering control specified by the rule have expired in the TSSF and/or the (S)Gi-LAN; for example, due to the flow expiry mechanism in the switches. + +TS\_POLICY\_IDENTIFIER\_ERROR + +This value is used to indicate that the rule could not be successfully installed or enforced because both the ts-policy-identifier-dl and ts-policy-identifier-ul are invalid, unknown, or not applicable to the downlink and uplink traffic flows for the traffic steering control. + +##### TS\_POLICY\_IDENTIFIER\_DL\_ERROR + +This value is used to indicate that the rule could not be successfully installed or enforced because the ts-policy-identifier-dl is invalid, unknown, or not applicable to the downlink traffic flows for the traffic steering control. + +##### TS\_POLICY\_IDENTIFIER\_UL\_ERROR + +This value is used to indicate that the rule could not be successfully installed or enforced because the ts-policy-identifier-ul is invalid, unknown, or not applicable to the uplink traffic flows for the traffic steering control. + +### 5.4.6 JSON notification fields + +#### 5.4.6.1 General + +Table 5.4.6.1.1 describes the JSON fields defined for the notification HTTP messages from the TSSF to the PCRF, including their JSON value types, and JCR types as well. + +**Table 5.4.6.1.1: JSON fields for notifications from the TSSF** + +| Field Name | Subclause defined | JSON Value Type (NOTE 1) | JCR Type (NOTE 2) | +|----------------------|-------------------|--------------------------|--------------------------------------| +| notifications | 5.4.6.2 | array | array | +| notification-type | 5.4.6.3 | string | "application"
"other"
(NOTE 3) | +| notification-message | 5.4.6.4 | string | String | +| notification-tag | 5.4.6.5 | string | String | +| notification-info | 5.4.6.6 | object | Object | + +NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [10]. +NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [16]. +NOTE 3: The quoted strings for a string type. + +#### 5.4.6.2 notifications + +The notifications field is of type array, and it contains a list of notifications provided by the TSSF. Each notification is defined as an object in the array. + +A notification object shall contain the notification-type and the notification-message fields. + +Optionally, it may include the notification-tag and notification-info fields. The notification-tag is used to distinguish a specific notification from others. The notification-info is provided for additional information. + +The JCR format of the notifications is as follows: + +``` +$notifications = "notifications" : [ +{ + $notification-type, + $notification-message, + $notification-tag ?, + $notification-info ? +} + +``` + +#### 5.4.6.3 notification-type + +The notification-type field is of type string. It can be one of 'application' or 'other'. + +When a notification is due to a change to one of the St session resources/sub-resources, the type shall be specified as 'application'. For all other notifications, the 'other' type shall be used. + +#### 5.4.6.4 notification-message + +The notification-message field is of type string. It is a textual description of the notification. + +#### 5.4.6.5 notification-tag + +The notification-tag field is of type string. It defines a tag for a particular notification. + +##### TS\_RULE\_EVENT + +This notification-tag value shall be used when the traffic steering rules cannot be enforced at the TSSF. Affected traffic steering rules shall be provided by the TSSF in the notification-info with a sub field named ts-rule-reports including the report reason and status of the rules. + +#### 5.4.6.6 notification-info + +The notification-info field is defined as an object type. It represents informational details regarding the notification. + +## 5.5 TSSF discovery + +The TSSF URI is pre-configured on the PCRF, e.g. per PCEF. + +# --- 6 Secure communication + +Either the NDS/IP network layer security defined in 3GPP TS 33.210 [7] or HTTP over TLS as defined in [19] should be used to secure communication over the REST based St interface. + +# --- Annex A (informative): Call Flows + +## A.1 General + +This annex describes the procedures for the interactions between the PCRF and the TSSF + +## --- A.2 Traffic Steering Control Information Provisioning + +This subclause describes the signalling flow for the traffic steering control information provisioning. + +![Sequence diagram for Traffic Steering Control Information Provisioning](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` +sequenceDiagram + participant PCRF + participant TSSF + Note right of PCRF: 1. HTTP POST + PCRF->>TSSF: 1. HTTP POST + Note left of TSSF: 2. HTTP 201 CREATED + TSSF-->>PCRF: 2. HTTP 201 CREATED +``` + +A sequence diagram showing the interaction between PCRF and TSSF for provisioning traffic steering control information. The PCRF sends an HTTP POST message to the TSSF, and the TSSF responds with an HTTP 201 CREATED message. + +Sequence diagram for Traffic Steering Control Information Provisioning + +**Figure A.2.1: Traffic Steering Control Information Provisioning** + +1. The PCRF sends the HTTP POST to the TSSF to initiate the creation of a resource state to provision the traffic steering control information including the parameters defined in subclause 4.4.2. +2. The TSSF sends the HTTP 201 CREATED response to the PCRF including the parameters defined in subclause 4.4.2. + +## A.3 Traffic Steering Control Information Update + +This subclause describes the signalling flow for the traffic steering control information update or the allocation/release notification of the UE IPv4 address. + +![Sequence diagram for Traffic Steering Control Information Update](1b893df61c2b73b7a85e65fc1f58e203_img.jpg) + +``` +sequenceDiagram + participant PCRF + participant TSSF + Note right of PCRF: 1. HTTP PUT/PATCH + PCRF->>TSSF: 1. HTTP PUT/PATCH + Note left of TSSF: 2. HTTP 200 OK + TSSF-->>PCRF: 2. HTTP 200 OK +``` + +A sequence diagram showing the interaction between PCRF and TSSF for updating traffic steering control information. The PCRF sends an HTTP PUT/PATCH message to the TSSF, and the TSSF responds with an HTTP 200 OK message. + +Sequence diagram for Traffic Steering Control Information Update + +**Figure A.3.1: Traffic Steering Control Information Update** + +1. The PCRF sends the HTTP PUT/PATCH to the TSSF to initiate the traffic steering control information update including the parameters defined in subclause 4.4.2. The PCRF also sends the HTTP PUT/PATCH to the TSSF to notify the UE IPv4 address allocation or release including the parameters defined in subclause 4.4.4. +2. The TSSF sends the HTTP 200 OK to the PCRF. + +## A.4 Traffic Steering Control Information Removal + +This subclause describes the signalling flow for the traffic steering control information removal. + +![Sequence diagram for Traffic Steering Control Information Removal](a4b963a07cc368283154762c4b156fe7_img.jpg) + +``` +sequenceDiagram + participant PCRF + participant TSSF + Note right of PCRF: 1. HTTP DELETE + PCRF->>TSSF: 1. HTTP DELETE + Note left of TSSF: 2. HTTP 200 OK + TSSF->>PCRF: 2. HTTP 200 OK +``` + +A sequence diagram showing the interaction between PCRF and TSSF for traffic steering control information removal. The PCRF sends an HTTP DELETE message to the TSSF, and the TSSF responds with an HTTP 200 OK message. + +Sequence diagram for Traffic Steering Control Information Removal + +**Figure A.4.1: Traffic Steering Control Information Removal** + +1. The PCRF sends the HTTP DELETE to the TSSF to initiate the traffic steering control information removal including the parameters defined in subclause 4.4.2. +2. The TSSF removes/deactivates all the ADC rules and sends the HTTP 200 OK to the PCRF including the parameters defined in subclause 4.4.2. + +## A.5 Traffic Steering Control Notification + +This subclause describes the signalling flow for the traffic steering control notification. + +![Sequence diagram for Traffic Steering Control Notification](f732d3320afe06d979aabbd366184254_img.jpg) + +``` +sequenceDiagram + participant PCRF + participant TSSF + Note right of TSSF: 1. HTTP POST + TSSF->>PCRF: 1. HTTP POST + Note left of PCRF: 2. HTTP 200 OK + PCRF->>TSSF: 2. HTTP 200 OK +``` + +A sequence diagram showing the interaction between TSSF and PCRF for traffic steering control notification. The TSSF sends an HTTP POST message to the PCRF, and the PCRF responds with an HTTP 200 OK message. + +Sequence diagram for Traffic Steering Control Notification + +**Figure A.5.1: Traffic Steering Control Notification** + +1. The TSSF sends an HTTP POST to the PCRF to inform it of changes to the state of traffic steering control rules as defined in subclause 4.4.3. + +2. The PCRF acknowledges the notification and sends an HTTP 200 OK to the TSSF. + +# --- Annex B (normative): JSON Schema + +## B.1 Session body schema + +This subclause defines the JSON schema for the body of HTTP requests and responses providing the state of a session resource. The schema is based on IETF draft-newton-json-content-rules [16] and is defined below: + +``` +# jcr-version 0.7 + +# ruleset-id 3gpp.stapplication.session + +; A JCR representing the session resource +$session-root = @{root} { + $session-id, + ( $ue-ipv4 | $ue-ipv6-prefix | ( $ue-ipv4 , $ue-ipv6-prefix ) ), + $called-station-id ?, + $tsrules ?, + $predefined-tsrules ?, + $predefined-group-of-tsrules ? +} + +; Resource fields definitions +; Session ID allocated by the PCRF +$session-id = "session-id" : string + +; The UE IPv4 address +$ue-ipv4 = "ue-ipv4" : ipv4 + +; The UE IPv6 prefix +$ue-ipv6-prefix = "ue-ipv6-prefix" : ipv6 + +; The PDN the UE accesses +$called-station-id = "called-station-id" : string +``` + +; The dynamic traffic steering rules + +\$tsrules = "tsrules" : { \$tsrule + } + +; The traffic steering rule + +\$tsrule = // : { + +    \$ts-rule-name, + +    \$precedence ?, + +    ( \$flow-information | \$tdf-application-identifier ), + +    ( \$ts-policy-identifier-ul | \$ts-policy-identifier-dl | ( \$ts-policy-identifier-ul, \$ts-policy-identifier-dl ) ) + +} + +; The name of the traffic steering rule in the TSSF + +\$ts-rule-name = "ts-rule-name" : string + +; The precedence of the traffic steering rule. From 0 to 4294967295. + +\$precedence = "precedence" : 0..4294967295 + +; The flow traffic information + +\$flow-information = "flow-information" : [ + +{ + +    \$flow-description ?, + +    \$tos-traffic-class ?, + +    \$security-parameter-index ?, + +    \$flow-label ?, + +    \$flow-direction + +} + +] + +; The IP filter rule for a service data flow + +\$flow-description = "flow-description" : string + +; The ToS traffic class is encoded on two octets, and represented in hex string display. + +\$tos-traffic-class = "tos-traffic-class" : /^[0-9A-Fa-f]{4}\$/ + +; The security parameter index is encoded on four octets, and represented in hex string display. + +\$security-parameter-index = "security-parameter-index" : /^[0-9A-Fa-f]{8}\$/ + +; The flow label is encoded on three octets, and represented in hex string display. + +\$flow-label = "flow-label" : /^[0-9A-Fa-f]{6}\$/ + +; The direction of the flow traffic + +\$flow-direction = "flow-direction" : ( "BIDIRECTIONAL" | "UPLINK" | "DOWNLINK" ) + +; The detected application traffic id in the TSSF + +\$tdf-application-identifier = "tdf-application-identifier" : string + +; The traffic steering policy id for uplink data + +\$ts-policy-identifier-ul = "ts-policy-identifier-ul" : string + +; The traffic steering policy id for downlink data + +\$ts-policy-identifier-dl = "ts-policy-identifier-dl" : string + +; The predefined traffic steering rules + +\$predefined-tsrules = "predefined-tsrules" : { \$predefined-tsrule + } + +; The predefined traffic steering rule + +\$predefined-tsrule = // : { \$ts-rule-name } + +; The predefined traffic steering group rules + +\$predefined-group-of-tsrules = "predefined-group-of-tsrules" : { \$predefined-group-of-tsrule + } + +; The predefined traffic steering group rule + +\$predefined-group-of-tsrule = // : { \$ts-rule-base-name } + +; The name of the traffic steering group rule in the TSSF + +\$ts-rule-base-name = "ts-rule-base-name" : string + +## --- B.2 Error and Informational response schema + +This subclause defines the JSON schema for the body of HTTP responses in case of errors or success. The schema is based on IETF draft-newton-json-content-rules [16] and is defined below: + +``` +# jcr-version 0.7 +# ruleset-id 3gpp.stapplication.info +# import 3gpp.stapplication.report as report +; A JCR for the error/successful response body +; Errors information +$errors-root = @{root} { $errors } + +; Success information +$success-root = @{root} { + $success-message, + $success-path ?, + $success-info ? +} + +; Resource fields definitions +; The list of errors returned in responses sent by the PCRF or TSSF +$errors = "errors" : [ +{ + $error-type, + $error-message, + $error-tag ?, + $error-path ?, + $error-info ? +} + +] + +; The error type for an error. It can be one of 'application', 'interface', 'server' and 'other'. +$error-type = "error-type" : ( "application" | "interface" | "server" | "other" ) + +; The error text message +$error-message = "error-message" : string + +; The error tag for a specific error +$error-tag = "error-tag" : string +``` + +; A JSON pointer path to the error resource + +\$error-path = "error-path" : string + +; Any additional information for the error + +\$error-info = "error-info" : { + +\$report.ts-rule-reports ?, + +// : any \* + +} + +; The successful text message + +\$success-message = "success-message" : string + +; A JSON pointer path to the success resource + +\$success-path = "success-path" : string + +; Any additional information for the success. + +\$success-info = "success-info" : { // : any \* } + +## --- B.3 Report schema + +This clause defines the JSON schema for reports provided by the TSSF to the PCRF. The schema is based on IETF draft-newton-json-content-rules [16] and is defined below: + +# jcr-version 0.7 + +# ruleset-id 3gpp.stapplication.report + +; A JCR for the notification body + +; Report fields definitions + +; The list of ts rule reports sent to the PCRF + +\$ts-rule-reports = "ts-rule-reports" : [ + +{ + +\$resource-paths, + +\$rule-status, + +\$rule-failure-code + +} + + +] + +``` +; The list of JSON pointers to the resources +$resource-paths = "resource-paths" : [ string + ] + +; The status for a traffic steering rule. It can be 'INACTIVE'. +$rule-status = "rule-status" : $rule-status-type + +; The string format for the traffic steering rule status +$rule-status-type =: ("INACTIVE") + +; The failure code for a traffic steering rule +$rule-failure-code = "rule-failure-code" : $rule-failure-code-type + +; The string format for the traffic steering rule failure code +$rule-failure-code-type =: ( + "UNKNOWN_RULE_NAME" | + "GW/PCEF_MALFUNCTION" | + "RESOURCES_LIMITATION" | + "MISSING_FLOW_INFORMATION" | + "INCORRECT_FLOW_INFORMATION" | + "TDF_APPLICATION_IDENTIFIER_ERROR" | + "FILTER_RESTRICTIONS" | + "RESOURCE_ALLOCATION_FAILURE" | + "RESOURCE_TIMEOUT" | + "TS_POLICY_IDENTIFIER_ERROR" | + "TS_POLICY_IDENTIFIER_DL_ERROR" | + "TS_POLICY_IDENTIFIER_UL_ERROR" +) +``` + +## --- B.4 Notification schema + +This clause defines the JSON schema for the body of the notification from the TSSF to the PCRF via the HTTP POST request. The schema is based on IETF draft-newton-json-content-rules [16] and is defined below: + +``` +# jcr-version 0.7 +# ruleset-id 3gpp.stapplication.notification +# import 3gpp.stapplication.report as report + +; A JCR for the notification body +``` + +``` +$notification-root = @{root} { $notifications } + +; Resource fields definitions +; The list of notifications notified to the PCRF +$notifications = "notifications" : [ +{ + $notification-type, + $notification-message, + $notification-tag ?, + $notification-info ? +} + +] + +; The notification type for a notification. It can be one of 'application' or 'other'. +$notification-type = "notification-type" : ( "application" | "other" ) + +; The notification text message +$notification-message = "notification-message" : string + +; The notification tag for a specific notification +$notification-tag = "notification-tag" : string + +; Any additional information for the notification +$notification-info = "notification-info" : { $report.ts-rule-reports ?, // : any *} +``` + +# Annex C (informative): Change history + +| Change history | | | | | | | | | +|----------------|------------|-----------|------|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|-------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | | Old | New | +| 2015-08 | CT3#82 | | | | TS skeleton of St reference point stage 3. | | | 0.0.0 | +| 2015-08 | CT3#82 | C3-153467 | | | Inclusion of documents agreed in CT3#82. C3-153291, C3-153416, C3-153444, C3-153455, C3-153445, C3-153420, C3-153439, C3-153290.
Added reference to IETF RFC 1786: "Uniform Resource Locators (URL)." | | 0.0.0 | 0.1.0 | +| 2015-10 | CT3#82-Bis | C3-154345 | | | Inclusion of documents agreed in CT3#82bis. C3-154231, C3-154049, C3-154231, C3-154217, C3-154218, C3-154319, C3-154139 | | 0.1.0 | 0.2.0 | +| 2015-11 | CT3#83 | C3-155420 | | | Inclusion of documents agreed in CT3#83. C3-155227, C3-155229, C3-155365, C3-155235, C3-155284 | | 0.2.0 | 1.0.0 | +| 2015-11 | CT#70 | CP-150824 | | | TS presented for presentation and approval | | 1.0.0 | 1.0.1 | +| 2015-12 | CT#70 | CP-150824 | | | TS 29.155 upgraded to 13.0.0 after approval | | 1.0.1 | 13.0.0 | +| Change history | | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +| 2016-03 | CT#71 | CP-160091 | 0001 | 2 | B | Traffic Steering Rule Error handling over the REST based St interface | | 13.1.0 | +| 2016-03 | CT#71 | CP-160091 | 0002 | 1 | F | Miscellaneous corrections related to the REST based St | | 13.1.0 | +| 2016-03 | CT#71 | CP-160091 | 0003 | 3 | B | Updates to JSON content rules for the notification procedures from the TSSF to the PCRF | | 13.1.0 | +| 2016-03 | CT#71 | CP-160091 | 0004 | 1 | B | JSON content rules updates for error responses with traffic steering rule reports over the REST based St interface | | 13.1.0 | +| 2016-03 | CT#71 | CP-160091 | 0005 | 3 | B | Traffic steering rule report JSON Content Rules over St | | 13.1.0 | +| 2016-12 | CT#74 | CP-160619 | 0008 | 4 | F | Overlapping IP Addresses with FMSS | | 13.2.0 | +| 2016-12 | CT#74 | CP-160619 | 0009 | 3 | F | Support of deployments with both PCEF/TDF and TSSF | | 13.2.0 | +| 2016-12 | CT#74 | CP-160619 | 0010 | 1 | F | Correction of IETF newton json content rule draft version and relevant JCR schemas | | 13.2.0 | +| 2016-12 | CT#74 | CP-160619 | 0013 | 2 | F | UE IPv4 address provisioning | | 13.2.0 | +| 2016-12 | CT#74 | CP-160616 | 0012 | 1 | F | Diameter base protocol specification update | | 14.0.0 | +| 2017-03 | CT#75 | CP-170076 | 0014 | 1 | F | Correction of Diameter base protocol specification update | | 14.1.0 | +| 2017-06 | CT#76 | CP-171133 | 0015 | 1 | D | Remove the Void reference | | 14.2.0 | +| 2017-06 | CT#76 | CP-171120 | 0017 | 1 | A | Correction of IETF newton json content rule draft version | | 14.2.0 | +| 2017-09 | CT#77 | CP-172038 | 0021 | - | A | Correction of resource path | | 14.3.0 | +| 2018-06 | CT#80 | | | | | Automatic upgrade from previous Release | | 15.0.0 | +| 2019-06 | CT#84 | CP-191091 | 0024 | - | A | Reference update: draft-newton-json-content-rules | | 15.1.0 | +| 2020-07 | SA#88e | - | - | - | | Update to Rel-16 version (MCC) | | 16.0.0 | +| 2021-12 | CT#94e | CP-213220 | 0025 | - | B | Reference update for HTTP/1.1 protocol | | 17.0.0 | +| 2024-03 | SA#103 | - | - | - | | Update to Rel-18 version (MCC) | | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29164/raw.md b/marked/Rel-18/29_series/29164/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6a52e7e0f9de520d776c308140b2837f67bcce1c --- /dev/null +++ b/marked/Rel-18/29_series/29164/raw.md @@ -0,0 +1,600 @@ + + +# 3GPP TS 29.164 V18.0.0 (2024-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interworking between the 3GPP CS Domain with BICC or ISUP as Signalling Protocol and external SIP-I Networks (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## --- **Keywords** + +CS Domain, LTE, Interworking, SIP-I, BICC, ISUP + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|-----------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Network characteristics..... | 8 | +| 4.1 Key characteristics of ISUP/BICC based CS Domain..... | 8 | +| 4.2 Key characteristics of external SIP-I network..... | 8 | +| 5 Interworking reference model..... | 9 | +| 6 Control plane interworking ..... | 9 | +| 6.1 General ..... | 9 | +| 6.2 Interworking between CS Domain using ISUP signalling and external network using SIP-I signalling ..... | 10 | +| 6.2.1 Control Plane Interworking ..... | 10 | +| 6.2.2 Services performed by network entities in the control plane ..... | 11 | +| 6.2.2.1 Services of the IWU..... | 11 | +| 6.2.2.2 Services of the external SIP-I signalling function ..... | 11 | +| 6.2.3 Signalling interactions between network entities in the control plane ..... | 11 | +| 6.2.3.1 Signalling between the IWU and SIP-I signalling function ..... | 11 | +| 6.2.4 SIP-ISUP protocol interworking ..... | 11 | +| 6.2.4.1 Incoming call interworking from SIP-I to ISUP at I-IWU ..... | 11 | +| 6.2.4.1.0 General ..... | 11 | +| 6.2.4.1.1 Interworking of received ISUP messages to SIP messages ..... | 11 | +| 6.2.4.1.2 Receipt of encapsulated ISUP information within SIP ..... | 12 | +| 6.2.4.1.3 Special Procedures for the Reception of SIP INVITE request..... | 12 | +| 6.2.4.1.3.1 Propagation of overlap signalling toward the 3GPP CS domain ..... | 12 | +| 6.2.4.1.3.2 Derivation of TMR, USI and HLC parameters within send IAM message ..... | 12 | +| 6.2.4.1.3.3 Receipt of SIP INVITE without SDP offer ..... | 12 | +| 6.2.4.2 Outgoing Call Interworking from ISUP to SIP-I at O-IWU..... | 13 | +| 6.2.4.2.1 General ..... | 13 | +| 6.2.4.2.2 Sending of ISUP information to adjacent SIP nodes ..... | 13 | +| 6.2.4.2.3 Receipt of encapsulated ISUP information within SIP-I ..... | 13 | +| 6.2.4.2.4 Special procedures related to outgoing INVITE ..... | 14 | +| 6.2.4.2.4.1 Overlap Signalling..... | 14 | +| 6.2.4.2.4.2 Coding of encapsulated ISUP IAM parameters in outgoing INVITE..... | 14 | +| 6.2.4.2.4.3 Media offered in SDP of outgoing INVITE ..... | 14 | +| 6.3 Interworking between CS Domain using BICC signalling and external network using SIP-I signalling ..... | 14 | +| 6.3.1 Control Plane Interworking ..... | 14 | +| 6.3.2 SIP-BICC protocol interworking..... | 15 | +| 6.3.2.1 General..... | 15 | +| 6.3.2.2 Incoming call interworking from SIP to BICC at I-IWU ..... | 15 | +| 6.3.2.3 Outgoing Call Interworking from BICC to SIP at O-IWU..... | 15 | +| 6.4 Supplementary services..... | 15 | +| 6.4.1 Special procedures for supplementary service interworking..... | 15 | +| 6.4.2 Interworking of CLIP/CLIR supplementary service ..... | 16 | +| 6.4.3 Interworking of Call Hold (HOLD) supplementary service..... | 16 | +| 6.4.4 Interworking of Completion of Calls to Busy Subscriber (CCBS) supplementary service to SIP networks ..... | 16 | +| 7 User plane Interworking..... | 16 | +| 7.1 ISUP based CS Domain ..... | 16 | +| 7.2 BICC based CS Domain..... | 16 | + +| | | | +|-------------------------------|--------------------------------------------------------------------------------------------|-----------| +| 8 | Interactions between control node and MGW ..... | 17 | +| 8.1 | Overview ..... | 17 | +| 8.2 | Signalling interactions ..... | 17 | +| 8.2.1 | Backward through-connection for outgoing call interworking from BICC to SIP at O-IWU. .... | 17 | +| 8.2.2 | Handling of RTP telephone events ..... | 17 | +| 8.3 | Signalling procedures ..... | 18 | +| Annex A (normative): | Codec Negotiation between a BICC based CS Domain and an external SIP-I network..... | 19 | +| Annex B (informative): | Change history ..... | 20 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document defines interworking procedures between a 3GPP CS domain (see 3GPP TS 23.205 [2]) which applies either BICC or ISUP as signalling protocol, and external networks that use SIP-I (see ITU-T Q.1912.5 [20], Profile C) as signalling protocol. The document also describes the related interworking architecture. The control plane interworking is performed by an interworking unit at the interconnection between the 3GPP CS domain and an external SIP-I network. The user plane interworking is performed by an MGW. The present document defines stage 2 procedures for the control of the MGW. + +The present specification reuses existing interworking procedures of 3GPP TS 29.163 [4] and ITU-T Q.1912.5 [20], Profile C, as far as possible. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.205: "Bearer-independent circuit-switched core network; Stage 2". +- [3] 3GPP TS 26.102: "Adaptive Multi-Rate (AMR) speech codec; Interface to Iu and Uu". +- [4] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks". +- [5] 3GPP TS 29.205: "Application of Q.1900 series to Bearer Independent CS Network architecture; Stage 3". +- [6] 3GPP TS 29.332: "Media Gateway Control Function (MGCF) – IM-Media Gateway (IM-MGW) interface, Stage 3". +- [7] 3GPP TS 29.414: "Core network Nb data transport and transport signalling". +- [8] 3GPP TS 29.415: "Core network Nb interface user plane protocols". +- [9] ITU-T Recommendation E.164 (05/1997): "The international public telecommunication numbering plan". +- [10] ITU-T Recommendation G.711 (11/98): "Pulse Code Modulation (PCM) of voice frequencies". +- [11] ITU-T Recommendation H.248.1 (05/02): "Gateway control protocol: Version 2". +- [12] ITU-T Recommendation I.363.5 (1996): "B-ISDN ATM Adaptation Layer specification: Type 5 AAL". +- [13] ITU-T Recommendation Q.701 (03/93), Q.702 (11/88), Q.703 (07/96), Q.704 (07/96), Q.705 (03/93), Q.706 (03/93), Q.707 (11/88), Q.708 (03/99), Q.709 (03/93): "Functional description of the message transfer part (MTP) of Signalling System No. 7". + +- [14] ITU-T Recommendation Q.730 (12/99), Q.731.1 (07/96), Q.731.3 (03/93), Q.731.4 (03/93), Q.731.5 (03/93), Q.731.6 (03/93), Q.731.7 (06/97), Q.731.8 (02/92), Q.732.5-2 (12/99), Q.732.7 (07/96), Q.733.1 (02/92), Q.733.2 (03/93), Q.733.3 (06/97), Q.733.4 (03/93), Q.733.5 (12/99), Q.734.1 (03/93), Q.734.2 (07/96), Q.735.1 (03/93), Q.735.3 (03/93), Q.735.6 (07/93), Q.736.1 (10/95), Q.736.3 (10/95), Q.737.1 (06/97): "ISDN user part supplementary services". +- [15] ITU-T Recommendations Q.761to Q.764 (12/99): "Signalling System No.7 ISDN User Part". +- [16] ITU-T Recommendation Q.765 (2000): "Signalling System No. 7 – Application transport mechanism". +- [17] ITU-T Recommendation Q.765.5 (2000): "Signalling system No. 7 – Application transport mechanism: Bearer Independent Call Control (BICC)". +- [18] ITU-T Recommendation 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". +- [19] ITU-T Recommendations Q.1902.1 to Q.1902.6 (07/2001): "Bearer Independent Call Control". +- [20] ITU-T Recommendation Q.1912.5 (03/04): "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol or ISDN User Part". +- [21] ITU-T Recommendation Q.2110 (1994): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)". +- [22] ITU-T Recommendation Q.2140 (1995): "B-ISDN ATM adaptation layer - Service specific coordination function for signalling at the network node interface (SSCF AT NNI)". +- [23] ITU-T Recommendation Q.2210 (1996): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140". +- [24] IETF RFC 791: "Internet Protocol". +- [25] IETF RFC 768: "User Datagram Protocol". +- [26] IETF RFC 793: "Transmission Control Protocol". +- [27] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification" +- [28] IETF RFC 4733: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals". +- [29] IETF RFC 2960: "Stream Control Transmission Protocol". +- [30] IETF RFC 2976: "The SIP INFO Method". +- [31] IETF RFC 3204: "MIME media types for ISUP and QSIG Objects". +- [32] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [33] IETF RFC 3262: "Reliability of provisional responses". +- [34] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)". +- [40] IETF RFC 3311: "SIP UPDATE method". +- [35] IETF RFC 3312: "Integration of Resource Management and Session Initiation Protocol (SIP)". +- [36] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". +- [37] 3GPP TS 29.202: "Core Signalling System No. 7 (SS7) signalling transport in core network; Stage 3". +- [38] 3GPP TS 29.231: "Application of SIP-I Protocols to Circuit Switched (CS) core network architecture; Stage 3". +- [39] 3GPP TS 29.235: "Interworking between the 3GPP CS domain with SIP-I as signalling protocol and other networks". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1], in 3GPP TS 29.163 [4], in ITU-T E.164 [9], in ITU-T Q.1912.5 [20] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in any other of the specifications listed above. + +**Interworking Unit (IWU):** Logical entity that interworks SIP-I signalling with BICC or ISUP signalling in the 3GPP CS Domain. + +**Incoming Interworking Unit (I-IWU):** Logical entity that terminates incoming calls from the external SIP-I network side and originates outgoing calls towards the CS Domain side using the BICC or ISUP protocols. + +**Outgoing Interworking Unit (O-IWU):** Logical entity that terminates incoming BICC or ISUP calls from the CS Domain side and originates outgoing calls towards external SIP-I network. + +**External SIP-I signalling function:** function in the external network, which has the capabilities to process SIP with encapsulated ISUP messages. + +For references to 3GPP TS 29.163 [4] procedures within the present specification, the MGCF in 3GPP TS 29.163 [4] is to be understood as IWU. The IM-MGW is to be understood as MGW. The Mn interface is to be understood as interface between IWU and MGW. The IM CN subsystem is to be understood as external SIP-I network. The CS network is to be understood as 3GPP CS domain. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1], in 3GPP TS 29.163 [4], in ITU-T E.164 [9], in ITU-T Q.1912.5 [20], and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in any other of the specification listed above. + +| | | +|--------|-------------------------------------| +| IW-MGW | Interworking Media Gateway Function | +|--------|-------------------------------------| + +# --- 4 Network characteristics + +## 4.1 Key characteristics of ISUP/BICC based CS Domain + +The 3GPP CS domain uses either BICC Capability Set 2 (see ITU-T Q.1902.1 to Q.1902.6 [19] and Q.765.5 [17]) with 3GPP specific extensions, as specified for the 3GPP Nc interface in 3GPP TS 29.205 [5], or ISUP (see ITU-T Q.761 to Q.764 [15]), as signalling protocol. + +If BICC is used as signalling protocol, the 3GPP Nb interface, as specified in 3GPP TS 29.414 [7] and 3GPP TS 29.415 [8], is used for the user plane transport. If ISUP is applied as signalling protocol, TDM transport of the user plane is applied. + +## 4.2 Key characteristics of external SIP-I network + +The external SIP-I network applies SIP, IETF RFC 3261 [32], with ISUP encapsulated according to IETF RFC 3204 [31], as specified in ITU-T Q.1912.5 [20] Profile C. The SIP Signalling Profile defined for Profile C in Annex C of Q.1912.5 is applied. + +The network uses either IPv4 (IETF RFC 791 [24]) or IPv6 (IETF RFC 2460 [27]). + +For the transport of most media, RTP (IETF RFC 3550 [36]) over UDP (IETF RFC 768 [25]) is applied. + +For the transport of control signalling, UDP (IETF RFC 768 [25]), TCP (IETF RFC 793 [26]) or SCTP (IETF RFC 2960 [29]) can be used. + +# 5 Interworking reference model + +Figure 5.1 details the interworking reference model for the present specification + +![Figure 5.1: Interworking reference model diagram showing the connection between an External SIP-I Network and the 3GPP CS Domain via an IWU and IW-MGW.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +The diagram illustrates the interworking reference model between an External SIP-I Network and the 3GPP CS Domain. On the left, an oval labeled 'External SIP-I Network' is connected to a central box labeled 'IWU' (Interworking Unit) via a dashed line labeled 'SIP-I'. Below this, a solid line labeled 'E.g. media/ RTP/ UDP/IP/' connects the network to a box labeled 'IW-MGW' (Interworking Media Gateway). The IWU and IW-MGW are enclosed in a light blue shaded area labeled 'Scope Of this TS'. Above the IWU, a dashed line labeled 'BICC/ISUP over M3UA/SCTP/IP' connects to a box labeled 'SGW' (Serving Gateway). From the SGW, a dashed line labeled 'Nc/ISUP over TDM' connects to a box labeled '(G)MSC Server'. Below the (G)MSC Server, a dashed line labeled 'Mc' connects to a box labeled 'MGW' (Media Gateway). A solid line labeled 'Nb/TDM' connects the IW-MGW to the MGW. A dashed line labeled 'BICC/ISUP over SCTP/IP' also connects the IWU to the (G)MSC Server. A legend at the bottom left indicates that solid lines represent the 'User Plane' and dashed lines represent the 'Control Plane'. + +Figure 5.1: Interworking reference model diagram showing the connection between an External SIP-I Network and the 3GPP CS Domain via an IWU and IW-MGW. + +NOTE 1: If needed a SGW is applied for conversion (both ways) of the transport level between the IWU and the (G)MSC. The SGW may be implemented as a stand-alone entity or it may be located in another entity of the CS Domain. A SGW function is not required for certain signalling transports, where M3UA+SCTP+IP is used in CS network and IWU. The implementation options are not further discussed in the present document. + +NOTE 2: The IWU is a logical function that may reside with other 3GPP logical functions in the same physical nodes, e.g. in an (G)MSC Server. The figure shows only the logical separation. + +Figure 5.1: interworking reference model + +# 6 Control plane interworking + +## 6.1 General + +The following sub-clauses define the signalling interworking between the Bearer Independent Call Control (BICC) or ISDN User Part (ISUP) protocols and Session Initiation Protocol (SIP) with its associated Session Description Protocol (SDP) and encapsulated ISUP at an IWU. + +The IWU shall act as a Type A or Type B exchange (ITU-T Q.764 [15]) for the purposes of ISUP and BICC compatibility procedures. + +The BICC/ISUP capabilities or signalling information defined for national use are outside the scope of the present document. + +The interworking procedures are based on ITU-T Recommendation Q.1912.5 [20] profile C. Clarifications are made within this specification on the application of Q.1912.5 profile C. + +NOTE: An IWU may apply additional procedures to support interworking for national-specific capabilities. + +The services that can be supported through the use of the signalling interworking are limited to the services that are supported both within the BICC or ISUP based 3GPP CS domain and the external SIP-I network. The IWU will originate and/or terminate services or capabilities that do not interwork seamlessly across domains according to the relevant protocol recommendation or specification. + +Table 6.1.1 lists the services seamlessly interworked within the scope of the present document. + +**Table 6.1.1: Service Interworking Capabilities** + +| Service | +|------------------------------------------------------------------| +| Speech/3.1 kHz audio | +| Data Calls (optional) | +| En bloc address signalling | +| Out of band transport of DTMF tones and information. (BICC only) | +| Inband transport of DTMF tones and information. (BICC and ISUP) | +| Multiple Subscriber Number (MSN) | +| Calling Line Identification Presentation (CLIP) | +| Calling Line Identification Restriction (CLIR) | +| Connected line presentation (COLP) | +| Connected line restriction (COLR) | +| Call Hold | +| Call Forwarding | +| Explicit Call Transfer (ECT) | +| User-to-User Signalling (UUS) | +| Call Deflection (CD) | +| Closed User Group (CUG) | +| Completion of Calls to Busy Subscriber (CCBS) | +| Multi-Level Precedence and Pre-emption (MLPP) | +| Call Waiting | + +The Clause 5.3.2 of ITU-T Q.1912.5 [20] describes additional general principles specific to SIP-I. + +## 6.2 Interworking between CS Domain using ISUP signalling and external network using SIP-I signalling + +### 6.2.1 Control Plane Interworking + +The control plane between CS networks supporting ISUP and the external network using SIP-I, where the underlying network is TDM or ATM and IP respectively, is as shown in figure 6.2.1. + +![Figure 6.2.1: Control plane interworking between CS networks supporting ISUP and an external network using SIP-I signalling. The diagram shows three main entities: (G)MSC, Interworking Unit (IWU), and External SIP-I signalling function. The (G)MSC contains ISUP, MTP3, MTP2, and L1 layers. The IWU contains ISUP, MTP3, MTP2, and L1 layers, plus SIP-I, TCP/UDP/SCTP, and IP layers. The External SIP-I signalling function contains SIP-I, TCP/UDP/SCTP, and IP layers. Arrows show ISUP and TDM connections between (G)MSC and IWU. A dashed line labeled NNI separates the IWU from the External SIP-I signalling function. SIP-I and IP connections are shown between the IWU and the External SIP-I signalling function.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the control plane interworking between a (G)MSC and an external network via an Interworking Unit (IWU). The (G)MSC is part of the 3GPP PLMN and contains layers ISUP, MTP3, MTP2, and L1. The IWU contains layers ISUP, MTP3, MTP2, and L1, as well as SIP-I, TCP/UDP/SCTP, and IP layers. The External SIP-I signalling function contains layers SIP-I, TCP/UDP/SCTP, and IP layers. Arrows indicate ISUP and TDM connections between the (G)MSC and the IWU. A dashed line labeled NNI separates the IWU from the External SIP-I signalling function. SIP-I and IP connections are shown between the IWU and the External SIP-I signalling function. + +Figure 6.2.1: Control plane interworking between CS networks supporting ISUP and an external network using SIP-I signalling. The diagram shows three main entities: (G)MSC, Interworking Unit (IWU), and External SIP-I signalling function. The (G)MSC contains ISUP, MTP3, MTP2, and L1 layers. The IWU contains ISUP, MTP3, MTP2, and L1 layers, plus SIP-I, TCP/UDP/SCTP, and IP layers. The External SIP-I signalling function contains SIP-I, TCP/UDP/SCTP, and IP layers. Arrows show ISUP and TDM connections between (G)MSC and IWU. A dashed line labeled NNI separates the IWU from the External SIP-I signalling function. SIP-I and IP connections are shown between the IWU and the External SIP-I signalling function. + +Figure 6.2.1: Control plane interworking between CS networks supporting ISUP and an external network using SIP-I signalling + +### 6.2.2 Services performed by network entities in the control plane + +#### 6.2.2.1 Services of the IWU + +The IWU shall provide the interaction, through the use of its interworking function, between the SS7 MTP3-User part information (as detailed in ITU-T Q.701 to 709 [13]) and SIP-I. The IWU shall also provide the encapsulation from the SS7 MTP3-User part information to the SIP-I ISUP MIME and de-encapsulation from this ISUP MIME to the SS7 MTP3-User part information. + +#### 6.2.2.2 Services of the external SIP-I signalling function + +The external SIP-I signalling function is a remote SIP User Agent capable of processing ISUP. + +### 6.2.3 Signalling interactions between network entities in the control plane + +#### 6.2.3.1 Signalling between the IWU and SIP-I signalling function + +Signalling between the SIP-I signalling function and the IWU uses the services of IPv4 (IETF RFC 791 [24]) or IPv6 (IETF RFC 2460 [27]), transport protocol such as TCP (IETF RFC 793 [26]) or UDP (IETF RFC 768 [25]) or SCTP (IETF RFC 2960 [29]), and SIP-I. + +### 6.2.4 SIP-ISUP protocol interworking + +#### 6.2.4.1 Incoming call interworking from SIP-I to ISUP at I-IWU + +##### 6.2.4.1.0 General + +The procedures for Profile C in Clause 6 of ITU-T Q.1912.5 [20] shall be applied with the modifications provided in this Clause. + +##### 6.2.4.1.1 Interworking of received ISUP messages to SIP messages + +The I-IWU receiving backwards ISUP information shall apply any interworking procedures detailed in Clause 6 of ITU-T Q.1912.5 [20] affecting parameters within the ISUP, and then proceed to encapsulate any ISUP information received (with the exception of the excluded messages detailed in 5.4.3 of ITU-T Q.1912.5 [20]) in a SIP message in a MIME body according to IETF RFC 3204 [31]. The selected SIP Header fields relating to the handling of the ISUP body shall be set as specified in Clause 5.4.1.2 of ITU-T Q.1912.5 [20]. + +##### 6.2.4.1.2 Receipt of encapsulated ISUP information within SIP + +On receipt of a SIP message containing encapsulated ISUP, the IWU shall de-encapsulate the ISUP message from the SIP message body. The received SIP message shall be mapped to an ISUP message and merged with the de-encapsulated ISUP message according to the rules for Profile C in Clause 6 of ITU-T Q.1912.5 [20]. + +NOTE 1: These precedence rules have been derived from the following principles, which can also be applied for any ISUP information not covered by the present specification: + +- 1 Where a SIP header mapping to ISUP field(s) is possible (for example the mapping of Request-URI to Called Party Number), the SIP header is given precedence over the encapsulated ISUP value in the alignment process. (Conflicts can be caused by a possible service invocation within the external SIP-I network.) +- 2 De-encapsulated ISUP information overrides ISUP information derived from default values (rather than SIP information). +- 3 Local ISUP procedures may modify information derived from SIP or default values. + +This note has been derived from text in ITU-T Q.1912.5 [20], Clause 5.4.2. + +NOTE 2: There is a certain change against ITU-T Q.1912.5 [20], where the above note is formulated as normative procedures. However, this is very high level and not required if you look at the real interworking procedures later on. Therefore formulating this as a note makes much more sense. + +##### 6.2.4.1.3 Special Procedures for the Reception of SIP INVITE request + +###### 6.2.4.1.3.1 Propagation of overlap signalling toward the 3GPP CS domain + +The procedures in Clause 6 of ITU-T Q.1912.5 [20] related to the propagation of overlap signalling across the I-IWU shall not be applied. + +NOTE: A G-MSC acting as IWU will collect all digits required to identify the callee and not propagate the overlap signalling further. Therefore, it will not apply procedures from ITU-T Q.1912.5 [20] Clause 6 related to the propagation of overlap signalling. + +###### 6.2.4.1.3.2 Derivation of TMR, USI and HLC parameters within send IAM message + +The I-IWU may choose to transcode media and shall then set the parameters according to the coding applied within the CS Domain. Otherwise, the I-IWU shall select a codec for the SIP side termination using SDP offer-answer procedures, IETF RFC 3264 [34], and shall map the SDP information of this codec to the TMR/USI/HLC parameters according to table 2a of 3GPP TS 29.163 [4]. If the information derived from this mapping matches the information in the TMR/USI/HLC parameters in the encapsulated ISUP, the TMR/USI/HLC parameters from the encapsulated ISUP should be used as they may contain additional information. If the information derived from this mapping contradicts the information in the TMR/USI/HLC parameters in the encapsulated ISUP, the TMR/USI/HLC parameters derived by the mapping shall be used. + +NOTE: The procedures in this note are an amendment compared to ITU-T Q.1912.5 [20], which simply states the TMR parameters in encapsulated ISUP shall take precedence, However this is inappropriate if an incompatible codec is selected. + +###### 6.2.4.1.3.3 Receipt of SIP INVITE without SDP offer + +An IWU may reject receipt of SIP INVITE without SDP offer, otherwise the procedures in this paragraph shall be followed. + +Upon receipt of the first INVITE with sufficient digits for an IAM to be sent, but without an SDP offer (see IETF RFC3264 [34]), the I-IWU shall construct the SDP offer with contents according to local policy, e.g. SDP for a G.711 speech call. The IWU may use the TMR and USI parameters of the encapsulated IAM to determine the desired service and construct the SDP offer accordingly. + +- 1) If reliable provisional responses (see IETF RFC 3262 [33]) are supported in the external SIP-I network, the I-IWU should immediately send the SDP offer within a 183 Session Progress message. The I-IWU should send the IAM upon receipt of the SDP answer and may take into account the media selected in the answer when constructing the IAM. +- 2) If reliable provisional responses are not supported, the I-IWU should immediately send out the IAM. The I-IWU will also include the SDP offer in the 200 OK(INVITE) SIP message according to SIP procedures. + +NOTE: The text in the preceding paragraph has been derived from ITU-T Q.1912.5 [20], Clause 6.1.1. Compared to ITU-T Q.1912.5 [20], the recommendation has been added that for an incoming INVITE without media the TMR/USI is considered to select media. Furthermore, bullet 1 recommends to wait for the SDP answer to construct TMR, USI and BICC codec list accordingly. + +#### 6.2.4.2 Outgoing Call Interworking from ISUP to SIP-I at O-IWU + +##### 6.2.4.2.1 General + +The procedures for Profile C in Clause 7 of ITU-T Q-1912-5 [20] shall be applied with the modifications provided in this Clause. + +##### 6.2.4.2.2 Sending of ISUP information to adjacent SIP nodes + +The I-IWU receiving ISUP information shall apply any interworking procedures detailed in Clause 7 of ITU-T Q-1912-5 [20] affecting parameters within the ISUP, and then proceed to encapsulate any ISUP information received (with the exception of the excluded messages detailed in 5.4.3 of ITU-T Q-1912-5 [20]) in a SIP message in a MIME body according to IETF RFC 3204 [31]. SIP Header fields relating to the handling of the ISUP body shall be set as specified in 5.4.1.2 of ITU-T Q-1912-5 [20]. + +NOTE: The text in the preceding paragraph has been derived from ITU-T Q.1912.5 [20], Clause 5.4.1. + +For a basic call setup, the SIP message used to encapsulate the ISUP message shall be the SIP message that was first triggered to be sent from the IWU as a result of the interworking specified in Clause 7 of ITU-T Q-1912-5 [20]. As an example, this means that an ISUP IAM will be encapsulated within the INVITE message that is sent out from the O-IWU. For the ISUP messages listed in Table 1 of ITU-T Q.1912.5 [20], the special procedures in Clause 5.4.3 of ITU-T Q.1912.5 are applicable. + +NOTE: The text in the preceding paragraph has been derived from ITU-T Q.1912.5 [20], Clause 5.4.1.3. + +##### 6.2.4.2.3 Receipt of encapsulated ISUP information within SIP-I + +On receipt of a SIP message containing encapsulated ISUP, the IWU shall de-encapsulate the ISUP message from the SIP message body. The received SIP message shall be mapped to an ISUP message and merged with the de-encapsulated ISUP information according to the rules in in Clause 7 of ITU-T Q-1912-5 [20]. + +NOTE: The text in the preceding paragraph has been derived from ITU-T Q.1912.5 [20], Clause 5.4.2. + +NOTE: These precedence rules have been derived from the following principles, which can also be applied for any ISUP information not covered by the present specification: + +- 1 Where a SIP header mapping to ISUP field(s) is possible (for example the mapping of Request-URI to Called Party Number), the SIP header is given precedence over the encapsulated ISUP value in the alignment process. (Conflicts can be caused by a possible service invocation within the SIP network.) +- 2 De-encapsulated ISUP information overrides ISUP information derived from default values (rather than SIP information). +- 3 Local ISUP procedures may modify information derived from SIP or default values. + +This Note has been derived from text in ITU-T Q.1912.5 [20], Clause 5.4.2 + +NOTE There is a certain change against Q.1912.5, where the above note is formulated as normative procedures. However, this is very high level and not required if you look at the real interworking procedures later on. Therefore formulating this as a Note makes much more sense. + +##### 6.2.4.2.4 Special procedures related to outgoing INVITE + +###### 6.2.4.2.4.1 Overlap Signalling + +The O-IWU does not need to support procedures related to overlap signalling in Clause 7 of ITU-T Q-1912-5 [20]. + +NOTE: No overlap signalling is used in a 3GPP CS domain. + +###### 6.2.4.2.4.2 Coding of encapsulated ISUP IAM parameters in outgoing INVITE + +The O-IWU may choose to transcode media, or attempt to interwork media without transcoding. If the O-IWU transcodes, it should set the TMR/USI/HLC parameters according to the codec applied in the SIP-I network. Otherwise, it should provide the TMR/USI/HLC parameters as received in the incoming IAM. If the I-IWU offers several codecs within SDP, it should set the TMR/USI/HLC parameters according to the preferred codec, applying the rules above for this codec. + +NOTE: ITU-T Q.1912.5 [20] does not describe the relationship between TMR/USI/HLC and SDP codec negotiation. + +###### 6.2.4.2.4.3 Media offered in SDP of outgoing INVITE + +The O-IWU should offer codecs known to be supported within the external SIP-I network. + +## 6.3 Interworking between CS Domain using BICC signalling and external network using SIP-I signalling + +### 6.3.1 Control Plane Interworking + +The control plane between CS networks supporting BICC and the external network using SIP-I, where the underlying network is SS7 and IP respectively, is shown in figures 6.3.1 and 6.3.2 in accordance to TS 29.202 [37]. + +![Diagram of control plane interworking between a 3GPP PLMN (G)MSC and an external SIP-I network via an Interworking Unit (IWU).](7c836a1c6836ec9b57b35aa4b2b66375_img.jpg) + +The diagram illustrates the control plane interworking between a 3GPP PLMN (G)MSC and an external network. On the left, the (G)MSC is shown with a protocol stack: BICC, STCMTP, M3UA, SCTP, and IP. The BICC layer connects to the BICC layer of the Interworking Unit (IWU). The IP layer connects to the IP layer of the IWU. The IWU is shown with two protocol stacks: one for BICC/STCMTP/M3US/SCTP/IP and another for SIP-I/TCP/UDP/SCTP/IP. The IWU connects to the External SIP-I Network via the NNI (Network-to-Network Interface). The NNI is shown with two connections: one for SIP-I and another for IP. The External SIP-I Network is shown with a protocol stack: SIP-I, TCP/UDP/SCTP, and IP. The External SIP-I Network contains the External SIP-I signalling function. + +Diagram of control plane interworking between a 3GPP PLMN (G)MSC and an external SIP-I network via an Interworking Unit (IWU). + +Figure 6.3.1: Control plane interworking between CS networks supporting BICC/IP and an external network using SIP-I signalling + +![Figure 6.3.2: Control plane interworking between CS networks supporting BICC/ATM and an external network using SIP-I signalling. The diagram shows three main components: (G)MSC, Interworking Unit (IWU), and External SIP-I Network. The (G)MSC contains layers: BICC, STC, MTP3B, SSCF, SSCOP, and AAL5. The IWU contains layers: BICC, STC, MTP3B, SSCF, SSCOP, and AAL5, plus a stack of SIP-I, TCP/UDP/SCTP, and IP. The External SIP-I Network contains layers: SIP-I, TCP/UDP/SCTP, and IP. Arrows indicate the flow of BICC and ATM signals between the (G)MSC and the IWU. A dashed line labeled NNI separates the IWU from the External SIP-I Network. SIP-I and IP signals are shown crossing the NNI between the IWU and the External SIP-I Network.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Figure 6.3.2: Control plane interworking between CS networks supporting BICC/ATM and an external network using SIP-I signalling. The diagram shows three main components: (G)MSC, Interworking Unit (IWU), and External SIP-I Network. The (G)MSC contains layers: BICC, STC, MTP3B, SSCF, SSCOP, and AAL5. The IWU contains layers: BICC, STC, MTP3B, SSCF, SSCOP, and AAL5, plus a stack of SIP-I, TCP/UDP/SCTP, and IP. The External SIP-I Network contains layers: SIP-I, TCP/UDP/SCTP, and IP. Arrows indicate the flow of BICC and ATM signals between the (G)MSC and the IWU. A dashed line labeled NNI separates the IWU from the External SIP-I Network. SIP-I and IP signals are shown crossing the NNI between the IWU and the External SIP-I Network. + +**Figure 6.3.2: Control plane interworking between CS networks supporting BICC/ATM and an external network using SIP-I signalling** + +For signalling interactions between network entities in the control plane see Clause 6.2.3. + +### 6.3.2 SIP-BICC protocol interworking + +#### 6.3.2.1 General + +Specific rules for handling of the APM mechanism have been added, which are not specified in ITU-T Q.1912.5 [20]. + +The procedures in Clause 6.2.4 shall be applied with the modifications provided the present Clause. + +The text in Clause 6.2.4 is to be understood as follows: + +- Where "ISUP" is mentioned, this shall be understood as BICC. As an exception, references to ISUP encapsulated within SIP-I shall be understood without modification, i.e. they still refer to ISUP rather than BICC. + +#### 6.3.2.2 Incoming call interworking from SIP to BICC at I-IWU + +An APM messages received from the CS side (see ITU-T Q.765 [16]) that relates to the BICC APM user (see ITU-T Q.765.5 [17]) shall not be encapsulated in any triggered SIP message. + +#### 6.3.2.3 Outgoing Call Interworking from BICC to SIP at O-IWU + +If an IAM message is received, the APM information elements (see ITU-T Q.765 [16]) relating to the BICC APM user (see ITU-T Q.765.5 [17]) shall be removed before the IAM message is encapsulated in the triggered SIP INVITE message. + +An APM messages received from the CS side (see ITU-T Q.765 [16]) that relates to the BICC APM user (see ITU-T Q.765.5 [17]) shall not be encapsulated in any triggered SIP message. + +## 6.4 Supplementary services + +### 6.4.1 Special procedures for supplementary service interworking + +The supplementary services described in Table 6.1.1 are interworked by using the parameters of the (de)encapsulated ISUP. No other interworking is required, except if otherwise described within the clauses below. + +### 6.4.2 Interworking of CLIP/CLIR supplementary service + +At the O-IWU: the service shall be supported by encapsulation. + +At the I-IWU: ITU-T Q.1912.5 [20], Annex B.1, shall apply. + +### 6.4.3 Interworking of Call Hold (HOLD) supplementary service + +The Profile C procedures in ITU-T Q.1912.5 [20], Clause B.10, shall be followed. + +### 6.4.4 Interworking of Completion of Calls to Busy Subscriber (CCBS) supplementary service to SIP networks + +The Profile C procedures of ITU-T Q.1912.5 [20], Clause B.11 shall be applied. + +# 7 User plane Interworking + +## 7.1 ISUP based CS Domain + +Figure 7.1.1 shows the user plane protocol stacks within the SIP-I network and an ISUP based CS Domain. + +Apart from speech codecs, data call related codecs, e.g. as listed in Table 2a of 3GPP TS 29.163 [4], may be used. + +![Diagram of User Plane Interworking and ISUP based CS Domain. It shows a SIP-I network on the left and a CS Domain on the right, connected via an MGW. The MGW contains a protocol stack with layers L1, L2, IP, UDP, RTP, and Codec (e.g., G.711). Above the stack, 'Transcoding or Relay' is indicated with a double-headed arrow. To the right of the stack, 'TDM' is shown, and another 'e.g. G.711' is listed next to the Codec layer.](69f52512bb7387a5dc9f952279513019_img.jpg) + +The diagram illustrates the user plane protocol stack for interworking between a SIP-I network and an ISUP based CS Domain. On the left, a cloud labeled 'SIP-I network' is connected to a central box labeled 'MGW'. On the right, a cloud labeled 'CS Domain' is also connected to the 'MGW'. Inside the 'MGW', there is a vertical stack of protocol layers. From bottom to top, they are: L1, L2, IP, UDP, RTP, and Codec (e.g., G.711). Above this stack, a double-headed arrow labeled 'Transcoding or Relay' spans across. To the right of the stack, the label 'TDM' is present, and another instance of 'e.g. G.711' is listed next to the Codec layer. + +Diagram of User Plane Interworking and ISUP based CS Domain. It shows a SIP-I network on the left and a CS Domain on the right, connected via an MGW. The MGW contains a protocol stack with layers L1, L2, IP, UDP, RTP, and Codec (e.g., G.711). Above the stack, 'Transcoding or Relay' is indicated with a double-headed arrow. To the right of the stack, 'TDM' is shown, and another 'e.g. G.711' is listed next to the Codec layer. + +Figure 7.1.1: User Plane Interworking and ISUP based CS Domain + +## 7.2 BICC based CS Domain + +Figure 7.2.1 shows the user plane protocol stacks within the SIP-I network and an BICC based CS Domain. + +Apart from speech codecs, data call related codecs, e.g. as listed in Table 2a of 3GPP TS 29.163 [4], may be used. + +Within the CS domain, the Nb interface as specified in 3GPP TS 29.414 [7] and 3GPP TS 29.415 [8] is used. + +If the same codec is used on both sides, no transcoding is required. If no transcoding is performed, the procedures in Clause 8.1.1 of 3GPP TS 29.163 [4] shall be applied to interwork the Nb framing Protocol, as specified in 3GPP TS 29.415 [8], with RTP, as specified in IETF RFC 3550 [36]. + +![Figure 7.2.1: User Plane Interworking for BICC based CS Domain. The diagram shows a central MGW (Media Gateway) box. Above the MGW box is a table representing protocol stacks. The table has two columns. The left column contains: 'Codec, e.g. G.711', 'RTP', 'UDP', 'IP', 'L2', 'L1'. The right column contains: 'Codec, e.g. AMR', 'NbFP', 'TNL', 'L1'. Above the table, a bracket labeled 'Transcoding or Relay' spans both columns. To the left of the table, a cloud labeled 'SIP-I network' is connected to the 'L1' layer. To the right of the table, a cloud labeled 'CS Domain' is connected to the 'L1' layer via a line labeled 'Nb'.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Figure 7.2.1: User Plane Interworking for BICC based CS Domain. The diagram shows a central MGW (Media Gateway) box. Above the MGW box is a table representing protocol stacks. The table has two columns. The left column contains: 'Codec, e.g. G.711', 'RTP', 'UDP', 'IP', 'L2', 'L1'. The right column contains: 'Codec, e.g. AMR', 'NbFP', 'TNL', 'L1'. Above the table, a bracket labeled 'Transcoding or Relay' spans both columns. To the left of the table, a cloud labeled 'SIP-I network' is connected to the 'L1' layer. To the right of the table, a cloud labeled 'CS Domain' is connected to the 'L1' layer via a line labeled 'Nb'. + +**Figure 7.2.1: User Plane Interworking for BICC based CS Domain** + +# 8 Interactions between control node and MGW + +## 8.1 Overview + +ITU-T H.248.1 [11] with 3GPP specific extensions as detailed in 3GPP TS 29.332 [6] shall be applied as signalling protocol between IWU and MGW. + +The present specification describes the signalling procedures between IWU and MGW and their interaction with BICC/ISUP and SIP signalling in the control plane, and with user plane procedures. 3GPP TS 29.332 [6] maps these signalling procedures to H.248 messages and defines the required packages and parameters. + +## 8.2 Signalling interactions + +The procedures in Clause 9.2 of TS 29.163 shall be applied with modifications provided in the present Clause. + +### 8.2.1 Backward through-connection for outgoing call interworking from BICC to SIP at O-IWU. + +For the outgoing call interworking from BICC to SIP at O-IWU, the IWU shall not request the MGW to provide an awaiting answer indication (ringing tone) to the calling party, as specified in Clauses 9.2.3.1.5, 9.2.3.2.5 and 9.2.3.3.5 of 3GPP TS 29.163 [4]. The O-IWU shall instead request the MGW to backward-through connect using the "Change-IMS Through-Connection" procedure when the trigger conditions in those clauses apply. + +### 8.2.2 Handling of RTP telephone events + +The procedures in Clause 9.2.8 of 3GPP TS 29.163 [4], are applicable with the following modifications: + +It depends on the characteristics of the external SIP-I network if DTMF is transported within the codec or according to IETF RFC 4733 [28]. SIP-I transports DTMF within the RTP telephony event according to RFC 4733 [28] if the RTP telephony event payload type is negotiated between the peer SIP-I entities; alternatively, if the RTP telephony event payload has not been negotiated, SIP-I may transport the DTMF in-band ("within the codec") when the selected codec allows transparent DTMF transport. + +The control node indicates the transport mode of DTMF to the MGW as follows in the "Configure IMS Resources" procedure or "Reserve IMS Connection Point and Configure Remote Resources" procedure (signal 1 in figure 48 or figure 49 of 3GPP TS 29.163 [4]): + +- If the control node does not configure the RTP telephony event payload at the MGW, then the Detect DTMF procedure means in-band ("within the codec") detection and sending of DTMF. +- If the control node configures the RTP telephony event payload at the MGW, then the Detect DTMF procedure means extracting and sending DTMF within the RTP payload type according to IETF RFC 4733 [28]. + +**Editor's Note:** The above reference contains sequences that require the MGW to forward partial digits to the Server. It is not yet agreed if this shall be permitted or if the MGW shall only forward complete and valid digits. + +## 8.3 Signalling procedures + +The procedures in Clause 9.3 of 3GPP TS 29.163 shall be applied with modifications provided in the present Clause. + +The support of the "Send TDM Tone", "Stop TDM Tone", "Send Tone" and "Stop Tone" procedures is optional. + +# --- Annex A (normative): Codec Negotiation between a BICC based CS Domain and an external SIP-I network + +The procedures in Annex B of TS 29.163 [4] are applicable when the IWU receives from the external SIP-I based network an SDP offer without the 3GPP\_OoBTC\_Indicator as defined in 3GPP TS 29.231 [38]. + +If the IWU receives from the external SIP-I based network a SIP request with an SDP offer containing a codec list with the 3GPP\_OoBTC\_Indicator, the IWU may apply the procedures in accordance to subclause 6.6.2 of 3GPP TS 29.235 [39]. + +When the IWU sends a SIP request with an SDP offer towards the external SIP-I based network, the IWU may include the 3GPP\_OoBTC\_Indicator in accordance to subclause 6.6.3 of 3GPP TS 29.235 [39]. + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|-----------|-----------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 01/09/2006 | CT3#41 | C3-060509 | | | Agreed Skeleton of TR | | 0.0.0 | +| 15/10/2006 | | | | | Proposed update of the TR on CT3 email reflector NOT discussed or agreed by CT3, but put onto the 3GPP web server drafts folder by mistake. | 0.0.0 | 0.1.0 | +| 08/11/2006 | CT3#42 | C3-060877 | | | Includes the following TDOCs agreed by CT3:
C3-060761, C3-060667, C3-060837, C3-060763, C3-060765, C3-060860, C3-040840, C3-040841, C3-040769, C3-060861, C3-060847, C3-060813, C3-060678, C3-060679 | 0.0.0 | 0.2.0 | +| 22/02/2007 | CT3#43 | C3-070274 | | | Includes the following TDOCs agreed by CT3:
C3-070105, C3-070106, C3-070249, C3-070258 | 0.2.0 | 0.3.0 | +| 28/02/2007 | TSG#35 | CP-070100 | | | Editorial update by MCC for presentation to TSG CT for information | 0.3.0 | 1.0.0 | +| 19/04/2007 | CT3#43bis | | | | Includes the following TDOCs agreed by CT3:
C3-070355, C3-070373, C3-070374 | 1.0.0 | 1.1.0 | +| 15/05/2007 | CT3#44 | | | | Includes the following TDOC agreed by CT3: C3-070523 | 1.1.0 | 1.2.0 | +| 23/05/2007 | TSG#36 | CP-070427 | | | Editorial update by MCC for presentation to TSG CT for approval | 1.2.0 | 2.0.0 | +| 06/2007 | TSG#36 | CP-070427 | | | Approved to be made v7.0.0 and put under change control | 2.0.0 | 7.0.0 | +| 12/2008 | TSG#42 | | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | 7.0.0 | 8.0.0 | +| 05/2009 | TSG#44 | CP-090350 | 001 | 2 | Codec negotiation when interworking with BICC based CS CN | 8.0.0 | 8.1.0 | +| 12/2009 | TSG#46 | | | | Automatic upgrade from previous Release | 8.1.0 | 9.0.0 | +| 06/2010 | TSG#48 | CP-100323 | 003 | 1 | Renumbering of duplicated subclauses | 9.0.0 | 9.1.0 | +| 10/2010 | TSG#49 | CP-100556 | 004 | | Correcting unspecific external reference | 9.1.0 | 9.2.0 | +| 03/2011 | TSG#51 | | | | Automatic upgrade from previous Release version 9.2.0 | 9.2.0 | 10.0.0 | +| 03/2011 | TSG#51 | | | | Correction of heading and numbering made by MCC | 10.0.0 | 10.0.1 | +| 09/2012 | TSG#57 | | | | Automatic upgrade from previous Release version 10.0.1 | 10.0.1 | 11.0.0 | +| 2014-10 | | | | | Automatic upgrade from previous Release | 11.0.0 | 12.0.0 | +| 2015-12 | | | | | Automatic upgrade from previous Release | 12.0.0 | 13.0.0 | +| Change history | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 2017-03 | CT#75 | | | | | Automatic upgrade from previous Release | 14.0.0 | +| 2018-06 | CT#80 | | | | | Automatic upgrade from previous Release | 15.0.0 | +| 2020-07 | SA#88e | - | - | - | | Update to Rel-16 version (MCC) | 16.0.0 | +| 2022-03 | SA#95e | - | - | - | | Update to Rel-17 version (MCC) | 17.0.0 | +| 2024-03 | SA#103 | - | - | - | | Update to Rel-18 version (MCC) | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29171/raw.md b/marked/Rel-18/29_series/29171/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..061dcc2c792d7731e4c2a85d964f5246c382c77a --- /dev/null +++ b/marked/Rel-18/29_series/29171/raw.md @@ -0,0 +1,3142 @@ + + +# 3GPP TS 29.171 V18.1.0 (2026-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Location Services (LCS); LCS Application Protocol (LCS-AP) between the Mobile Management Entity (MME) and Evolved Serving Mobile Location Centre (E-SMLC); SLs interface (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2026, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Functional Overview..... | 9 | +| 4.1 General ..... | 9 | +| 5 LCS-AP Message Transport ..... | 9 | +| 5.1 General ..... | 9 | +| 5.2 Protocol Layering..... | 9 | +| 5.3 Usage of SCTP Associations..... | 10 | +| 6 LCS-AP Procedures ..... | 10 | +| 6.1 General ..... | 10 | +| 6.2 Procedures Applicable to LCS-AP..... | 11 | +| 6.2.1 Location Service Request..... | 11 | +| 6.2.1.1 General..... | 11 | +| 6.2.1.2 Successful Operation ..... | 11 | +| 6.2.1.3 Unsuccessful Operation ..... | 12 | +| 6.2.2 Location Information Exchange ..... | 13 | +| 6.2.2.1 Connection Oriented Information Transfer ..... | 13 | +| 6.2.2.1.1 General ..... | 13 | +| 6.2.2.1.2 Successful Operation..... | 13 | +| 6.2.2.1.3 Abnormal Conditions ..... | 14 | +| 6.2.2.2 Connectionless Information Transfer ..... | 14 | +| 6.2.2.2.1 General ..... | 14 | +| 6.2.2.2.2 Successful Operation..... | 14 | +| 6.2.2.2.3 Unsuccessful Operation..... | 14 | +| 6.2.2.2.4 Abnormal Conditions ..... | 15 | +| 6.2.3 Ciphering Keys Delivery ..... | 15 | +| 6.2.3.1 General..... | 15 | +| 6.2.3.2 Successful Operation ..... | 15 | +| 6.2.3.3 Unsuccessful Operation ..... | 15 | +| 6.3 Exception Procedures..... | 16 | +| 6.3.1 Location Abort..... | 16 | +| 6.3.1.1 General..... | 16 | +| 6.3.1.2 Normal Operation ..... | 16 | +| 6.3.1.3 Abnormal Conditions..... | 16 | +| 6.3.2 Reset ..... | 16 | +| 6.3.2.1 General..... | 16 | +| 6.3.2.2 Normal Operation ..... | 17 | +| 6.3.2.3 Abnormal Conditions..... | 17 | +| 6.4 Error Handling..... | 17 | +| 6.4.1 Abnormal Conditions ..... | 17 | +| 6.4.2 Overload ..... | 17 | +| 7 LCS-AP Messages and Message Formats ..... | 18 | +| 7.1 General ..... | 18 | +| 7.2 Message Formats..... | 18 | +| 7.3 LCS-AP Messages..... | 18 | +| 7.3.1 LCS-AP Location Request message..... | 19 | +| 7.3.2 LCS-AP Location Response message ..... | 19 | +| 7.3.3 LCS-AP Location Abort Request message ..... | 20 | +| 7.3.4 LCS-AP Connection Oriented Information message ..... | 20 | + +| | | | +|--------|------------------------------------------------------------------|----| +| 7.3.5 | LCS-AP Connectionless Information message ..... | 20 | +| 7.3.6 | LCS-AP Reset Request message ..... | 21 | +| 7.3.7 | LCS-AP Reset Acknowledge message..... | 21 | +| 7.3.8 | LCS-AP Ciphering Key Data message..... | 21 | +| 7.3.9 | LCS-AP Ciphering Key Data Result message ..... | 21 | +| 7.4 | Information Elements..... | 22 | +| 7.4.1 | General ..... | 22 | +| 7.4.2 | Message Type..... | 22 | +| 7.4.3 | Location Type..... | 22 | +| 7.4.4 | E-CGI ..... | 22 | +| 7.4.5 | LCS Client Type..... | 23 | +| 7.4.6 | LCS Priority..... | 23 | +| 7.4.7 | LCS QoS..... | 23 | +| 7.4.8 | UE Positioning Capability ..... | 24 | +| 7.4.9 | Include Velocity ..... | 24 | +| 7.4.10 | IMSI..... | 24 | +| 7.4.11 | IMEI ..... | 25 | +| 7.4.12 | Geographic Area..... | 26 | +| 7.4.13 | Positioning Data ..... | 29 | +| 7.4.14 | Velocity Estimate ..... | 32 | +| 7.4.15 | Accuracy Fulfilment Indicator..... | 32 | +| 7.4.16 | LCS Cause ..... | 33 | +| 7.4.17 | Payload Type..... | 34 | +| 7.4.18 | APDU ..... | 34 | +| 7.4.19 | Network Element..... | 34 | +| 7.4.20 | Return Error Request..... | 34 | +| 7.4.21 | Return Error Cause ..... | 34 | +| 7.4.22 | Altitude and direction ..... | 35 | +| 7.4.23 | Geographical Coordinates ..... | 35 | +| 7.4.24 | Uncertainty Ellipse ..... | 36 | +| 7.4.25 | Horizontal Speed and Bearing..... | 36 | +| 7.4.26 | Vertical Velocity ..... | 36 | +| 7.4.27 | PLMN Identity..... | 37 | +| 7.4.28 | Correlation ID..... | 37 | +| 7.4.29 | eNB ID..... | 38 | +| 7.4.30 | LCS Service Type ID ..... | 38 | +| 7.4.31 | Cell Portion ID ..... | 38 | +| 7.4.32 | Civic Address ..... | 38 | +| 7.4.33 | Barometric Pressure..... | 39 | +| 7.4.34 | RAT Type..... | 39 | +| 7.4.35 | Coverage Level..... | 39 | +| 7.4.36 | Ciphering Data..... | 39 | +| 7.4.37 | Ciphering Data Ack..... | 40 | +| 7.4.38 | Ciphering Data Error Report ..... | 40 | +| 7.4.39 | Ciphering Data Set ..... | 41 | +| 7.4.40 | Ciphering Data Error Report Contents ..... | 44 | +| 7.4.41 | High Accuracy Geographical Coordinates..... | 44 | +| 7.4.42 | High Accuracy Uncertainty Ellipse..... | 45 | +| 7.4.43 | High Accuracy Altitude..... | 45 | +| 7.4.44 | High Accuracy Extended Uncertainty Ellipse..... | 46 | +| 7.4.45 | High Accuracy Scalable Uncertainty Ellipse ..... | 46 | +| 7.4.46 | High Accuracy Scalable Uncertainty Altitude ..... | 46 | +| 7.4.47 | UE Country Determination Indication ..... | 47 | +| 7.4.48 | UE Area Indication..... | 47 | +| 7.5 | Message and information element abstract syntax..... | 47 | +| 7.5.1 | General ..... | 47 | +| 7.5.2 | Usage of protocol extension mechanism for non-standard use ..... | 48 | +| 7.5.3 | Elementary procedure definitions..... | 48 | +| 7.5.4 | PDU definitions ..... | 50 | +| 7.5.5 | Information element definitions ..... | 55 | +| 7.5.6 | Common definitions ..... | 64 | +| 7.5.7 | Constant definitions..... | 65 | + +7.5.8 Container Definitions ..... 66 +7.5.9 Message transfer syntax ..... 68 +7.6 Handling of unknown, unforeseen and erroneous protocol data..... 68 +8 LCS-AP Timers..... 68 +8.1 General ..... 68 +8.2 Timers of LCS-AP ..... 68 +**Annex A (informative): Change history..... 69** + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document specifies the procedures and information coding for LCS Application Protocol (LCS-AP) that is needed to support the location services in E-UTRAN. The LCS-AP message set is applicable to the SLs interface between the E-SMLC and the MME. LCS-AP is developed in accordance to the general principles stated in TS 23.271 [3]. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 36.305: "Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN". +- [3] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)". +- [4] IETF RFC 4960: "Stream Control Transmission Protocol". +- [5] TTA/EIA/IS-J-STD-036 (2000): "Wireless Enhanced Emergency Services". +- [6] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [7] 3GPP TS 36.413: "S1 Application Protocol (S1AP)". +- [8] ITU-T Recommendation X.680 (07/2002): "Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [9] ITU-T Recommendation X.681 (07/2002): "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification". +- [10] 3GPP TS 22.071: "Location Services (LCS); Service Description; Stage1". +- [11] 3GPP TS 23.003: "Numbering, addressing and identification". +- [12] ITU-T Recommendation X.691 (07/2002): "Information Technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)". +- [13] IETF RFC 4119: "A Presence-based GEOPRIV Location Object Format". + +- [14] IETF RFC 5139: "Revised Civic Location Format for Presence Information Data Format Location Object". +- [15] IETF RFC 6848: "Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)". +- [16] IETF RFC 5905: "Network Time Protocol Version 4: Protocol and Algorithms Specification". +- [17] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [18] IETF RFC 4776: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information". + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Elementary Procedure:** LCS-AP protocol consists of Elementary Procedures (EPs). An LCS-AP Elementary Procedure is a unit of interaction between the MME and the E-SMLC. An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used: + +- **Class 1:** Elementary Procedures with response (success or failure), +- **Class 2:** Elementary Procedures without response. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|---------|----------------------------------------------------| +| CID | Cell-ID (positioning method) | +| E-CID | Enhanced Cell-ID (positioning method) | +| E-SMLC | Enhanced Serving Mobile Location Centre | +| E-UTRAN | Evolved Universal Terrestrial Radio Access Network | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| LCS | LoCation Services | +| LCS-AP | LCS Application Protocol | +| LPP | LTE Positioning Protocol | +| LPPa | LTE Positioning Protocol Annex | +| LTE | Long Term Evolution | +| MBS | Metropolitan Beacon System | +| MO-LR | Mobile Originated Location Request | +| MT-LR | Mobile Terminated Location Request | +| NI-LR | Network Induced Location Request | +| MME | Mobility Management Entity | +| OTDOA | Observed Time Difference Of Arrival | +| PDU | Protocol Data Unit | +| SCTP | Stream Control Transmission Protocol | +| SET | SUPL Enabled Terminal | +| SLP | SUPL Location Platform | +| SUPL | Secure User Plane Location | +| TA | Timing Advanced | + +| | | +|--------|-----------------------------------| +| UE | User Equipment | +| U-TDOA | Uplink Time Difference Of Arrival | + +# 4 Functional Overview + +## 4.1 General + +Figure 4.1-1 below shows the architecture applicable to the positioning of a UE with E-UTRAN access. The SLs interface is used to convey LCS-AP messages and parameters between the MME to the E-SMLC. It is also used for tunnelling LTE Positioning Protocols (LPP between the E-SMLC and the target UE, LPPa between the E-SMLC and the eNB), which are transparent to the MME as described in TS 36.305 [2]. + +![Diagram of positioning interfaces in E-UTRAN showing UE, Serving eNB, Neighbor eNB, MME, and E-SMLC connected via LTE-Uu, S1, and SLs interfaces.](0b87abe67b21a93777287649c33e755d_img.jpg) + +The diagram illustrates the network architecture for positioning. On the left, a 'UE' (User Equipment) icon is shown. A double-line arrow labeled 'LTE-Uu' connects the UE to a 'Serving eNB' (base station) box. The 'Serving eNB' is connected to an 'MME' (Mobility Management Entity) box via a horizontal line labeled 'S1'. Below the 'Serving eNB' is a 'Neighbor eNB' box, which is also connected to the 'MME' via a diagonal line labeled 'S1'. The 'MME' is connected to an 'E-SMLC' (Evolved SMLC) box located above it via a vertical line labeled 'SLs'. + +Diagram of positioning interfaces in E-UTRAN showing UE, Serving eNB, Neighbor eNB, MME, and E-SMLC connected via LTE-Uu, S1, and SLs interfaces. + +Figure 4.1-1 Positioning Interfaces in E-UTRAN + +# 5 LCS-AP Message Transport + +## 5.1 General + +The LCS-AP is a logical interface between the MME and the E-SMLC. This clause specifies the standards for signaling transport to be used across LCS-AP. + +## 5.2 Protocol Layering + +Figure 5.2-1 below shows the protocol layering used to support the transfer of LCS-AP PDUs between an E-SMLC and a MME. The LTE Positioning Protocols (LPP and LPPa) can be carried in LCS-AP messages which are transparent to the MME. + +![Figure 5.2-1: Protocol Layering for LCS-AP. The diagram shows two protocol stacks. The left stack is for the MME, with layers from top to bottom: NAS (labeled 'Relay'), S1-AP, SCTP, IP, L2, and L1. The right stack is for the E-SMLC, with layers from top to bottom: LPP/LPPa, LCS-AP, SCTP, IP, L2, and L1. A vertical dashed line labeled 'SLs' separates the two stacks. Horizontal dashed lines connect corresponding layers between the MME and E-SMLC: NAS to LCS-AP, SCTP to SCTP, IP to IP, L2 to L2, and L1 to L1.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 5.2-1: Protocol Layering for LCS-AP. The diagram shows two protocol stacks. The left stack is for the MME, with layers from top to bottom: NAS (labeled 'Relay'), S1-AP, SCTP, IP, L2, and L1. The right stack is for the E-SMLC, with layers from top to bottom: LPP/LPPa, LCS-AP, SCTP, IP, L2, and L1. A vertical dashed line labeled 'SLs' separates the two stacks. Horizontal dashed lines connect corresponding layers between the MME and E-SMLC: NAS to LCS-AP, SCTP to SCTP, IP to IP, L2 to L2, and L1 to L1. + +Figure 5.2-1 Protocol Layering for LCS-AP + +## 5.3 Usage of SCTP Associations + +SCTP (see IETF RFC 4960 [4]) shall be supported as the transport layer of LCS-AP messages. + +Semi-permanent SCTP associations shall be established between MME and E-SMLC, i.e. the SCTP associations shall remain up under normal circumstances. + +Local multi-homing should be supported. Remote multi-homing shall be supported. + +Multiple local SCTP endpoints may be supported. Multiple remote SCTP endpoints shall be supported. When multiple local or remote SCTP endpoints are configured, several simultaneous SCTP associations shall be supported between MME and E-SMLC. + +The MME shall establish the SCTP association. Since under normal operation there should always be an SCTP association established between an MME and an E-SMLC, if the E-SMLC needs to initiate a message towards an MME it shall do so over an existing SCTP association already established with that MME. + +When an entity detects that an SCTP association has been lost, all resources for transactions open on that association shall be released. + +The registered port number for LCS-AP is 9082. The registered payload protocol identifier for LCS-AP is 29. + +# 6 LCS-AP Procedures + +## 6.1 General + +The LCS-AP interface can be divided into the following procedures: + +- Location service request procedure +- Location information exchange procedure + +The E-UTRAN positioning capabilities are intended to be forward compatible to other access types and other position methods, in an effort to reduce the amount of additional positioning support needed in the future. + +## 6.2 Procedures Applicable to LCS-AP + +### 6.2.1 Location Service Request + +#### 6.2.1.1 General + +The purpose of the location service request procedure is to obtain the location estimate for a target UE in E-UTRAN. + +#### 6.2.1.2 Successful Operation + +![Sequence diagram showing the Location Service Request Procedure, Successful Operation. The MME sends a LOCATION REQUEST to the E-SMLC, and the E-SMLC responds with a LOCATION RESPONSE.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +``` +sequenceDiagram + participant MME + participant E-SMLC + Note left of MME: Initiator + MME->>E-SMLC: LOCATION REQUEST + Note right of E-SMLC: Responder + E-SMLC-->>MME: LOCATION RESPONSE +``` + +Sequence diagram showing the Location Service Request Procedure, Successful Operation. The MME sends a LOCATION REQUEST to the E-SMLC, and the E-SMLC responds with a LOCATION RESPONSE. + +Figure 6.2.1.2-1 Location Service Request Procedure, Successful Operation + +The initiator (MME) of the location service request procedure sends a LCS-AP Location Request message to the E-SMLC associated with the current or last known serving cell for the target UE and starts the timer T3x01. The message contains the following mandatory (M), conditional (C) and optional (O) information, where conditional parameters are required if available. + +- Correlation ID (M) +- Location Type (M) +- Cell Identifier (M) +- LCS Client Type (C) +- LCS Priority (C) +- LCS Service Type ID (C) +- LCS QoS (C) +- UE Positioning Capability (O) +- Include Velocity (O) +- IMSI of target UE (O) +- IMEI of target UE (O) +- APDU (O) +- RAT Type (O) +- Coverage Level (O) +- UE Country Determination Indication (O) + +The Correlation ID is assigned by the MME and enables association of the location response with the location request when more than one location service request procedure is ongoing for the UE with the same E-SMLC. + +The Location Type IE indicates the type of Location Information being requested. The following types are supported: + +- Current geographic location estimate +- Location assistance data for the target UE +- Last known location estimate + +If the location estimate is requested, the E-SMLC performs positioning procedure on the target UE using a particular position method or a combination of more than one positioning method based on the UE capability. If UE capability is unknown, the E-SMLC may request UE position capability through LPP as defined in TS 36.305 [2]. If the location estimate is requested and the UE Country Determination Indication is set to "required", the E-SMLC shall map the location estimate to the country or the area in the country or international area. + +Alternatively, if assistance data was requested, the E-SMLC may provide positioning assistance data to the UE. The E-SMLC may invoke the following LCS-AP procedures to get assistance data: + +- Connection Oriented Information Transfer +- Connectionless Information Transfer + +Otherwise, if a last known location estimate is requested, the E-SMLC obtains a geographic location estimate using only the information provided in the LCS-AP Location Request message. The E-SMLC shall not attempt to obtain location information for the target UE from either the E-UTRAN or the target UE (e.g. because the UE may not be currently reachable). + +If a location estimate or a last known location estimate was requested and was subsequently obtained, the E-SMLC shall return a LCS-AP Location Response to the initiator of the location request using the same SCTP association as the location request. This message contains the following mandatory (M), conditional (C) and optional parameters (O). + +- Correlation ID (M) +- Location Estimate (M). +- Accuracy Fulfilment Indicator (O). +- Velocity estimate (C). +- Positioning Data (C). +- E-UTRAN Cell Identifier (O). +- Cell Portion ID (O). +- Civic Address (O). +- Barometric Pressure (O). +- UE Area Indication (O). + +If assistance data was instead requested for an UE and the E-SMLC was able successfully to transfer this to the UE, the E-SMLC shall return a LCS-AP Location Response to the initiator of the location request (MME). This message shall contain no parameters. The absence of a LCS Cause parameter in this case implies that the transfer was successful. + +If the MME receives the LCS-AP Location Response for corresponding request message, the MME shall stop the timer T3x01. + +#### 6.2.1.3 Unsuccessful Operation + +If the E-SMLC is unable to obtain any of the location information requested or if requested LCS assistance data could not be transferred, the E-SMLC shall return a LCS-AP Location Response to the initiator of the Location Request carrying the following parameters: + +- Correlation ID (M) +- LCS Cause (M) + +- Positioning Data (O) + +The E-SMLC shall use the same SCTP association for the Location Response as was used for the request. + +If the MME receives the LCS-AP Location Response for corresponding request message, the MME shall stop the timer T3x01. + +On the expiry of the timer T3x01, the MME shall abort the procedure, release any resources allocated for this location request procedure and notify the node that triggered the Location Request about the error. + +### 6.2.2 Location Information Exchange + +#### 6.2.2.1 Connection Oriented Information Transfer + +##### 6.2.2.1.1 General + +The Connection Oriented Information transfer procedure enables two-way transfer of LPP and LPPa messages between an E-SMLC and a MME. The procedure is only valid while a location request procedure for the target UE is ongoing. This procedure makes use of the same SCTP association as the location request procedure for the particular target UE. + +##### 6.2.2.1.2 Successful Operation + +![Diagram illustrating the successful operation of Connection Oriented Information transfer. Endpoint A sends a message labeled 'CONNECTION ORIENTED INFORMATION' to Endpoint B.](5dfc130b129ace4df375839020a5700d_img.jpg) + +The diagram shows two vertical lifelines, 'Endpoint A' and 'Endpoint B', each with a rectangular box at the top and a thick horizontal bar at the bottom. A single horizontal arrow points from the lifeline of Endpoint A to the lifeline of Endpoint B. Above this arrow, the text 'CONNECTION ORIENTED INFORMATION' is written in all caps. + +Diagram illustrating the successful operation of Connection Oriented Information transfer. Endpoint A sends a message labeled 'CONNECTION ORIENTED INFORMATION' to Endpoint B. + +**Figure 6.2.2.1.2-1 Connection Oriented Information, Successful Operation** + +The initiator of the procedure (E-SMLC or MME) with a LPP or LPPa message to transfer concerning a particular target UE sends a LCS-AP Connection Oriented Information message to a recipient carrying the following parameters: + +- Correlation ID (M) +- Payload Type (M) +- APDU (M); + +The Correlation ID in this message is the Correlation ID used for the Location Request. It shall be present for a message transfer from the E-SMLC to the MME and for a message transfer from the MME to the E-SMLC. + +The Payload Type shall be present to indicate the type of the APDU. The supported information types are LPP and LPPa. + +The APDU shall contain an LPP APDU when communicating between the E-SMLC and the target UE or an LPPa APDU when communicating between the E-SMLC and serving eNB. The MME shall forward this to the serving eNB for the target UE. + +If the intended recipient is the E-SMLC for a target UE, the message is terminated in the E-SMLC. The E-SMLC shall then perform interpretation of the APDU. + +##### 6.2.2.1.3 Abnormal Conditions + +At an intermediate entity, if a received LCS-AP Connection Oriented Information message contains unrecognized information or if the message cannot be sent on, the message shall be discarded. + +#### 6.2.2.2 Connectionless Information Transfer + +##### 6.2.2.2.1 General + +The Connectionless Information transfer procedure enables two-way transfer of LPPa messages between an E-SMLC and a MME when there is no existing signalling connection association. This procedure can be used to query eNBs for the information not related to a UE connection, such as Timing information on the eNB. + +##### 6.2.2.2.2 Successful Operation + +![Sequence diagram showing the successful operation of the Connectionless Information Procedure between Endpoint A and Endpoint B. Endpoint A sends a CONNECTIONLESS INFORMATION message to Endpoint B, and Endpoint B responds with a CONNECTIONLESS INFORMATION message.](c036e2540a94b31357ceb0002f0cacab_img.jpg) + +``` +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note left of Endpoint A: + Endpoint A->>Endpoint B: CONNECTIONLESS INFORMATION + Note right of Endpoint B: + Endpoint B->>Endpoint A: CONNECTIONLESS INFORMATION + Note left of Endpoint A: + Note right of Endpoint B: +``` + +Sequence diagram showing the successful operation of the Connectionless Information Procedure between Endpoint A and Endpoint B. Endpoint A sends a CONNECTIONLESS INFORMATION message to Endpoint B, and Endpoint B responds with a CONNECTIONLESS INFORMATION message. + +**Figure 6.2.2.2.2-1 Connectionless Information Procedure, Successful Operation** + +The initiator of the procedure (either E-SMLC or MME) sends a LCS-AP Connectionless Information message to a recipient carrying the following parameters: + +- Source Entity (M) +- Destination Entity (M) +- APDU (M) +- Return Error Request (O) + +The source entity identifies the sender. The recipient entity identifies the final destination. The APDU contains a LPPa APDU to be transferred. The Return Error Request may be included to request notification in the event of unsuccessful transfer and indicate the type of notification needed. If the recipient entity is not the final destination, the recipient shall transfer the LCS-AP Connectionless Information message to either the final destination or an intermediate entity capable of forwarding it to the final destination. + +##### 6.2.2.2.3 Unsuccessful Operation + +If the message cannot be transferred by an intermediate entity or destination entity and the Return Error Request is not included, the message shall be discarded. If the Return Error Request is included, the intermediate or destination entity shall, depending on the Return Error Request type, send a LCS-AP Connectionless Information message to, or towards, the original source containing the following parameters: + +- Source Entity (M) +- Destination Entity (M) +- APDU (M) +- Return Error Cause (M) + +The Source entity shall indicate the Destination Entity in the original received message. The Destination Entity shall indicate the Source Entity in the original message. The Return Error cause shall indicate the reason for unsuccessful transfer. The APDU shall contain any originally received APDU. + +If a received LCS-AP Connectionless Information message containing a Return Error Cause cannot be transferred by an intermediate entity, it shall be discarded with no return error message. + +##### 6.2.2.2.4 Abnormal Conditions + +At an intermediate entity, if a received LCS-AP Connectionless Information message contains unrecognized or invalid information, the message shall be discarded. + +At the recipient entity, if a received LCS-AP Connectionless Information message contains invalid or unrecognized information as defined for LCS-AP, the message shall be discarded. + +### 6.2.3 Ciphering Keys Delivery + +#### 6.2.3.1 General + +The purpose of the ciphering keys delivery procedure is to enable the E-SMLC to send ciphering keys for broadcast assistance data to the MME so that the MME can then distribute the ciphering keys to suitably subscribed UEs. + +#### 6.2.3.2 Successful Operation + +![Sequence diagram of the Ciphering Keys Delivery Procedure, Successful Operation. The diagram shows two entities: MME and E-SMLC. The E-SMLC sends a 'CIPHERING KEY DATA' message to the MME. The MME responds with a 'CIPHERING KEY DATA RESULT' message to the E-SMLC.](3f1987804d7d78bc3b3bc560e974280a_img.jpg) + +``` +sequenceDiagram + participant E-SMLC + participant MME + Note left of MME: + E-SMLC->>MME: CIPHERING KEY DATA + MME-->>E-SMLC: CIPHERING KEY DATA RESULT + Note right of E-SMLC: +``` + +Sequence diagram of the Ciphering Keys Delivery Procedure, Successful Operation. The diagram shows two entities: MME and E-SMLC. The E-SMLC sends a 'CIPHERING KEY DATA' message to the MME. The MME responds with a 'CIPHERING KEY DATA RESULT' message to the E-SMLC. + +**Figure 6.2.3.2-1 Ciphering Keys Delivery Procedure, Successful Operation** + +The initiator (E-SMLC) of the ciphering keys delivery procedure sends a Ciphering Key Data message to the MME and starts the timer T3x03. The message contains the following mandatory (M) information: + +- Ciphering Data (M): + +If the MME is able to successfully store all ciphering data sets included in the Ciphering Key Data message, the MME sends a Ciphering Key Data Result message. The message contains the following mandatory (M) information: + +- Ciphering Data Ack (M) + +If the E-SMLC receives the Ciphering Key Data Result message, the E-SMLC shall stop the timer T3x03. + +#### 6.2.3.3 Unsuccessful Operation + +If the MME is unable to successfully store one or more ciphering data sets included in the Ciphering Key Data message, the MME shall return a Ciphering Key Data Result message carrying the following mandatory (M) information: + +- Ciphering Data Error Report (M) + +If the E-SMLC receives the Ciphering Key Data Result message message, the E-SMLC shall stop the timer T3x03. + +On the expiry of the timer T3x03, the E-SMLC shall abort the procedure and release any resources allocated for this ciphering keys delivery procedure. + +## 6.3 Exception Procedures + +### 6.3.1 Location Abort + +#### 6.3.1.1 General + +The purpose of the Location Abort procedure is to cancel an ongoing positioning attempt or the request for assistance data. This message can be sent from the MME to the E-SMLC. This procedure makes use of the same SCTP association as the location request procedure for the particular target UE. + +#### 6.3.1.2 Normal Operation + +![Sequence diagram of the Location Abort Procedure, Normal Operation. The MME sends a LOCATION ABORT REQUEST message to the E-SMLC, and the E-SMLC responds with a LOCATION RESPONSE message.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +``` +sequenceDiagram + participant MME + participant E-SMLC + Note left of MME: + MME->>E-SMLC: LOCATION ABORT REQUEST + Note right of E-SMLC: + E-SMLC-->>MME: LOCATION RESPONSE + Note left of MME: + Note right of E-SMLC: +``` + +Sequence diagram of the Location Abort Procedure, Normal Operation. The MME sends a LOCATION ABORT REQUEST message to the E-SMLC, and the E-SMLC responds with a LOCATION RESPONSE message. + +**Figure 6.3.1.2-1 Location Abort Procedure, Normal Operation** + +The MME sends a LCS-AP Location Abort Request message to the E-SMLC across the SLs interface. The message contains a LCS Cause parameter indicating the reason of cancellation. + +On receipt of this message, the E-SMLC shall stop the positioning transactions of the target UE and may release any resources previously allocated. The E-SMLC shall return a LCS-AP Location Response message containing the LCS Cause received in Location Abort Request and, optionally, positioning data. The E-SMLC may also optionally include in this response any "best-effort" location estimate that it has already determined prior to receiving the LCS-AP Location Abort Request. + +#### 6.3.1.3 Abnormal Conditions + +At the recipient entity, if no ongoing location transaction for the target UE is found, the recipient entity shall discard the received LCS-AP Location Abort Request message with no return error message. + +### 6.3.2 Reset + +#### 6.3.2.1 General + +The Reset procedure is an optional procedure applicable to the LCS-AP. It enables an E-SMLC or a MME that has undergone a failure with loss of location service transactions to indicate this to a partner entity. The recipient entity can then release its own connection and transaction resources. The Reset procedure may not be applicable when only a limited part of an E-SMLC or a MME has suffered a failure, since error recovery procedures specific to individual connections and transactions may then be used. The Reset procedure applies to all transactions initiated on a single SCTP association. + +#### 6.3.2.2 Normal Operation + +![Sequence diagram illustrating the Reset Procedure, Normal Operation between Endpoint A and Endpoint B.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` +sequenceDiagram + participant Endpoint A + participant Endpoint B + Note left of Endpoint A: + Endpoint A->>Endpoint B: RESET REQUEST + Note right of Endpoint B: + Endpoint B-->>Endpoint A: RESET ACKNOWLEDGE + Note left of Endpoint A: + Note right of Endpoint B: +``` + +The diagram shows a sequence of messages between two entities, Endpoint A and Endpoint B. Endpoint A sends a 'RESET REQUEST' message to Endpoint B. Endpoint B receives the request and responds with a 'RESET ACKNOWLEDGE' message back to Endpoint A. Both endpoints have a vertical line extending downwards from their message interaction point, ending in a thick horizontal bar, representing the lifeline of the entity. + +Sequence diagram illustrating the Reset Procedure, Normal Operation between Endpoint A and Endpoint B. + +**Figure 6.3.2.2-1 Reset Procedure, Normal Operation** + +In the event of a failure at an E-SMLC or a MME that results in the loss of location service transactions, a LCS-AP Reset Request message may be sent to the partner entity across the SLs interface. The message contains a LCS Cause parameter indicating the reason for the reset. The sending entity shall ensure that all information on location service transactions for the SCTP association on which the Reset Request was sent is reinitialized to indicate no existing transactions. + +On receiving a LCS-AP Reset Request message, the recipient entity (E-SMLC or MME) shall clear all references and state information for the location service transactions on the SCTP association on which the Reset Request was received and shall release any associated resources. The recipient entity shall then return a LCS-AP Reset Acknowledge message using the same SCTP association as the Reset Request. + +If the initiating entity (E-SMLC or MME) received the LCS-AP Reset Acknowledge message, it shall stop the timer T3x02. + +#### 6.3.2.3 Abnormal Conditions + +On the first expiry of the timer T3x02, the Source entity (E-SMLC or MME) shall resend the LCS-AP Reset Request message and shall reset and restart timer T3x02. This retransmission is repeated a maximum of "n" times, where "n" is an O&M administered parameter. Following "n" unsuccessful reset attempts, the procedure shall be terminated and maintenance shall be informed. + +## 6.4 Error Handling + +### 6.4.1 Abnormal Conditions + +If an ongoing location request is pre-empted at the initiator by an inter-eNB handover and MME relocation, or if the main signalling link to the target UE is released by the MME, or if a main signalling link failure indicated by the serving eNodeB persists for more than a certain timeout interval or if there is a timeout waiting for the positioning response, or any other abnormal conditions for which the positioning procedure cannot be maintained, the MME shall send a LCS-AP Location Abort message to the E-SMLC to terminate the positioning procedure. + +For Intra-MME handovers, the location session between the MME and E-SMLC is not affected. Application layer impacts on these handovers are handled by higher protocol layers. + +If the E-SMLC cannot proceed with positioning due to some protocol violation or error condition (e.g. inter-eNB handover), it shall return a LCS-AP Location Response message to the initiator containing a LCS cause and, optionally, positioning data. + +### 6.4.2 Overload + +If an E-SMLC is in overload condition, it may reject a LCS-AP Location Request by returning a LCS-AP Location Response containing a LCS Cause parameter indicating congestion. The initiator of the location requests (i.e. MME) may reduce the frequency of later location requests until rejection due to overload has ceased. In reducing the frequency + +of location service requests, the MME shall reduce lower priority requests, to zero if necessary, before reducing the frequency of higher priority requests. An E-SMLC shall similarly reject location requests of a lower priority, to zero if necessary, due to overload before rejecting location requests of a higher priority. An E-SMLC in overload condition may optionally employ the following procedures to alleviate overload: + +- a) Allow higher priority location service requests to pre-empt lower priority requests for which location service procedures are already in progress. +- b) Abort lower priority location service requests already in progress. +- c) Reduce the supported QoS for lower priority requests for a location estimate – e.g. by reducing accuracy or increasing response time. +- d) Employ UE based positioning methods, where supported by the target UE and the E-SMLC, rather than UE assisted or network based methods (except TA). + +The priority of a location request shall be defined according to the value in the LCS Priority parameter. If this parameter is absent in a LCS-AP Location Request, the lowest priority shall be assumed. + +# --- 7 LCS-AP Messages and Message Formats + +## 7.1 General + +This clause describes the structure of the messages and information elements required for the LCS-AP messages. + +## 7.2 Message Formats + +LCS-AP ASN.1 definition conforms to ITU-T Recommendations ITU-T Recommendation X.680 (07/2002) [8] and ITU-T Recommendation X.681 (07/2002) [9]. The ASN.1 definition specifies the structure and content of LCS-AP messages. The LCS-AP messages may contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a LCS-AP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids): + +- IEs shall be ordered (in an IE container) in the order they appear in object set definitions. +- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. + +If a LCS-AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error. + +For the handling of unknown, unforeseen and erroneous protocol data, please refer to TS 36.413 [7]. + +## 7.3 LCS-AP Messages + +The following attributes are used for the tabular description of the messages and information elements: Presence, Range Criticality and Assigned Criticality. Their definition and use can be found in TS 36.413 [7]. + +### 7.3.1 LCS-AP Location Request message + +This message is sent by the MME to request a location estimate for a target UE and contains sufficient information to enable location according to the required QoS using any positioning method supported. The message is also used to request LCS assistance data transfer to an UE. + +Direction: MME → E-SMLC + +**Table 7.3.1-1: Location Request message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| Correlation ID | M | | 7.4.28 | | YES | reject | +| Location Type | M | | 7.4.3 | | YES | reject | +| E-UTRAN Cell Identifier | M | | E-CGI / 7.4.4 | | YES | ignore | +| LCS Client Type | O | | 7.4.5 | | YES | reject | +| LCS Priority | O | | 7.4.6 | | YES | reject | +| LCS QoS | O | | 7.4.7 | | YES | reject | +| LCS Service Type ID | O | | 7.4.30 | | YES | ignore | +| UE Positioning Capability | O | | 7.4.8 | | YES | reject | +| Include Velocity | O | | 7.4.9 | | YES | reject | +| IMSI | O | | 7.4.10 | | YES | ignore | +| IMEI | O | | 7.4.11 | | YES | ignore | +| Multiple APDUs | | 0..3 | | | | | +| APDU | M | | 7.4.18 | | YES | reject | +| RAT Type | O | | 7.4.34 | | YES | ignore | +| Coverage Level | O | | 7.4.35 | | YES | ignore | +| UE Country Determination Indication | O | | 7.4.47 | | YES | ignore | + +NOTE: The IMSI should be sent preferably if known. The IMEI may be sent if the IMSI is not known, or in addition to the IMSI for the purpose of allowing correlation between the two identities. + +### 7.3.2 LCS-AP Location Response message + +This message is sent in response to a LCS-AP Location Request to return a successful location estimate for a target UE or to indicate some failure in obtaining this. The message is also sent in response to a LCS-AP Location Request to return an indication that LCS assistance data has been successfully delivered to an UE. + +Direction: E-SMLC → MME + +**Table 7.3.2-1: Location Response message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|--------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| Correlation ID | M | | 7.4.28 | | YES | reject | +| Location Estimate | O | | Geographic Area / 7.4.12 | | YES | reject | +| Positioning Data | O | | 7.4.13 | | YES | reject | +| Velocity Estimate | O | | 7.4.14 | | YES | reject | +| Accuracy Fulfilment Indicator | O | | 7.4.15 | | YES | reject | +| LCS Cause | O | | 7.4.16 | | YES | ignore | +| E-UTRAN Cell Identifier | O | | E-CGI / 7.4.4 | | YES | ignore | +| Cell Portion ID | O | | 7.4.31 | | YES | ignore | +| Civic Address | O | | 7.4.32 | | YES | ignore | +| Barometric Pressure | O | | 7.4.33 | | YES | ignore | +| UE Area Indication | O | | 7.4.48 | | YES | ignore | + +### 7.3.3 LCS-AP Location Abort Request message + +This message is sent by the MME to abort the positioning attempt or the request for assistance data. + +Direction: MME → E-SMLC + +**Table 7.3.3-1: Location Abort Request message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| Correlation ID | M | | 7.4.28 | | YES | reject | +| LCS Cause | M | | 7.4.16 | | YES | ignore | + +### 7.3.4 LCS-AP Connection Oriented Information message + +This message is sent in association with an existing signalling connection between an E-SMLC and another entity to transfer information between the E-SMLC and other entity belonging to a higher level protocol. + +Direction: E-SMLC → MME or MME → E-SMLC + +**Table 7.3.4-1: Connection Oriented Information message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| Correlation ID | M | | 7.4.28 | | YES | reject | +| Payload Type | M | | 7.4.17 | | YES | reject | +| APDU | M | | 7.4.18 | | YES | reject | + +### 7.3.5 LCS-AP Connectionless Information message + +This message conveys signalling information associated with a higher protocol level between an E-SMLC and another entity when there is no existing signalling connection association. + +Direction: E-SMLC → MME or MME → E-SMLC + +**Table 7.3.5-1: Connectionless Information message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|--------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| Source Identity | M | | Network Element / 7.4.19 | | YES | reject | +| Destination Identity | M | | Network Element / 7.4.19 | | YES | reject | +| APDU | M | | 7.4.18 | | YES | reject | +| Return Error Request | O | | 7.4.20 | | YES | reject | +| Return Error Cause | O | | 7.4.21 | | YES | ignore | + +### 7.3.6 LCS-AP Reset Request message + +This message is sent to indicate a failure in the sending entity with loss of location service transactions that were established or were being established. + +Direction: E-SMLC → MME or MME → E-SMLC + +**Table 7.3.6-1: Reset Request message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| LCS Cause | M | | 7.4.16 | | YES | ignore | + +### 7.3.7 LCS-AP Reset Acknowledge message + +This message is sent in response to a LCS-AP Reset message to indicate that references and resources associated with location service transactions towards the entity sending the LCS-AP Reset have been released. + +Direction: E-SMLC → MME or MME → E-SMLC + +**Table 7.3.7-1: Reset Acknowledge message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | + +### 7.3.8 LCS-AP Ciphering Key Data message + +This message is used by the E-SMLC to send ciphering keys for broadcast assistance data to the MME. + +Direction: E-SMLC → MME + +**Table 7.3.8-1: Ciphering Key Data message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| Ciphering Data | M | | 7.4.36 | | YES | reject | + +### 7.3.9 LCS-AP Ciphering Key Data Result message + +This message is used by the MME to indicate to the E-SMLC whether the MME was able to successfully store the ciphering data sets received from the E-SMLC in a Ciphering Data Key message. + +Direction: MME → E-SMLC + +**Table 7.3.9-1: Ciphering Key Data Result message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 7.4.2 | | YES | reject | +| Ciphering Data Ack | C | | 7.4.37 | | YES | reject | +| Ciphering Data Error Report | C | | 7.4.38 | | YES | reject | + +## 7.4 Information Elements + +### 7.4.1 General + +When specifying information elements which are to be represented by bit strings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits: + +- The first bit (leftmost bit) contains the most significant bit (MSB) +- The last bit (rightmost bit) contains the least significant bit (LSB) +- When importing bit strings from other specifications, the first bit of the bit string contains the first bit of the concerned information + +### 7.4.2 Message Type + +The *Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages. + +**Table 7.4.2-1: Message Type** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure Code | M | | INTEGER (0..255) | "0" = LCS-AP LOCATION SERVICE REQUEST
"1" = LCS-AP CONNECTION ORIENTED INFORMATION TRANSFER
"2" = LCS-AP CONNECTIONLESS INFORMATION TRANSFER
"3" = LCS-AP LOCATION ABORT
"4" = LCS-AP RESET
"5" = LCS-AP CIPHERING KEY DATA | +| Type of Message | M | | ENUMERATED (Initiating Message, Successful Outcome, Unsuccessful Outcome, ...) | | + +### 7.4.3 Location Type + +This parameter defines the type of location information being requested. + +**Table 7.4.3-1: Location Type** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------------------------------------------------------------------|-----------------------| +| Location Type | M | | ENUMERATED (geographic location, assistance information, ..., last known location) | | + +### 7.4.4 E-CGI + +This parameter gives the current cell location of the target UE or the last known cell location for the case when the Location Type IE is set to last known location. The E-UTRAN Cell Global Identifier (ECGI) is used to globally identify a cell. + +Table 7.4.4-1: ECGI + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------| +| PLMN Identity | M | | 7.4.27 | | +| Cell Identity | M | | BIT STRING (28) | The leftmost bits of the Cell Identity correspond to the eNB ID (defined in 7.4.19). | + +### 7.4.5 LCS Client Type + +This parameter defines the type of the originating LCS Client. It shall be included if the Location Type indicates a request for a location estimate and may be included in other cases to assist an SMLC to appropriately prioritize a location request. + +Table 7.4.5-1: LCS Client Type + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Client Type | M | | ENUMERATED
(Emergency Services,
Value Added Services,
PLMN Operator
Services, Lawful
Intercept Services,
PLMN Operator -
broadcast services,
PLMN Operator - O&M,
PLMN Operator -
anonymous statistics,
PLMN Operator - Target
MS service support,
...) | Identifies the category of LCS client. | + +### 7.4.6 LCS Priority + +This parameter defines the priority of the location request. + +Table 7.4.6-1: LCS Priority + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------|---------------------------------------------------------------------------------------------------------------------| +| LCS Priority | M | | OCTET STRING
(SIZE(1)) | 0= highest priority
1= normal priority
all other values treated as 1
For details, refer to TS 22.071 [10]. | + +### 7.4.7 LCS QoS + +This parameter provides the required Quality of Service for the LCS Request. Quality of Service may include horizontal accuracy, vertical accuracy and allowed response time. + +Table 7.4.7-1: LCS QoS + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|---------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Horizontal Accuracy | O | | INTEGER(0..127) | bit 8 = 0
bits 7-1 = 7 bit Uncertainty Code defined in TS 23.032 [6].
The horizontal location error should be less than the error indicated by the uncertainty code with 67% confidence. | +| Vertical Requested | O | | ENUMERATED(Vertical Coordinate Is Not Requested (0), Vertical Coordinate Is Requested (1) ) | Default value if this IE is not present is: Vertical Coordinate Is Not Requested (0). | +| Vertical Accuracy | O | | INTEGER(0..127) | bit 8 = 0
bits 7-1 = 7 bit Vertical Uncertainty Code defined in TS 23.032 [6].
The vertical location error should be less than the error indicated by the uncertainty code with 67% confidence.
If the vertical requested IE is not present or present with a value of 0, then this vertical accuracy will be ignored, if present. | +| Response Time | O | | ENUMERATED(Low Delay(0), Delay Tolerant (1), ...) | For details, refer to TS 22.071 [10]. | + +### 7.4.8 UE Positioning Capability + +This parameter provides information about the LCS capabilities of the target UE. + +Table 7.4.8-1: UE Positioning Capability + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|--------------------------------------------------------------|-------------|----------------------| +| LPP Support | M | | BOOLEAN | Defines if the UE supports LPP or not. TRUE means supported. | – | | + +### 7.4.9 Include Velocity + +This parameter indicates if the Velocity of the target UE is requested in the Location Response. + +Table 7.4.9-1: Include Velocity + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-------------------------------------------|-----------------------------------------| +| Velocity Indicator | O | | ENUMERATED(requested, not requested, ...) | Specify if Velocity of UE is requested. | + +### 7.4.10 IMSI + +This parameter identifies the IMSI of the target UE. + +Table 7.4.10-1: IMSI + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | | OCTET STRING (SIZE (3..8)) | The number of decimal digits shall be from 6 to 15 starting with the digits from the PLMN identity. It is encoded with TBCD String, two digits per octet. | + +### 7.4.11 IMEI + +This parameter identifies the IMEI of the target UE. + +Table 7.4.11-1: IMEI + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMEI | M | | OCTET STRING (SIZE (8)) |

Refers to International Mobile Station Equipment Identity and Software Version Number (SVN) defined in TS TS 23.003 [11].

This IE is 16 digits encoded with TBCD String, two digits per octet.

If the SVN is not present the last octet shall contain the digit 0 as filler.
If present the SVN shall be included in the last octet.

| + +### 7.4.12 Geographic Area + +This parameter provides a location estimate for the target UE in the case of a successful location attempt. + +**Table 7.4.12-1: Geographic Area** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------------|----------|--------------------|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE Geographical Area | | | | | +| >Point | | | | Ellipsoid point | +| >>Geographical Coordinates | M | | 7.4.23 | | +| >Point With Uncertainty | | | | Ellipsoid point with uncertainty circle | +| >>Geographical Coordinates | M | | 7.4.23 | | +| >>Uncertainty Code | M | | INTEGER ( 0..127) | The uncertainty "r" expressed in meters is derived from the "Uncertainty Code" k by $r = 10 \times (1.1^k - 1)$ | +| >Ellipsoid point with uncertainty Ellipse | | | | | +| >>Geographical Coordinates | M | | 7.4.23 | | +| >>Uncertainty Ellipse | M | | 7.4.24 | | +| >>Confidence | M | | INTEGER ( 0..100) | In percentage | +| >Polygon | | | | List of Ellipsoid points | +| >>Polygon Point | | 1.. | | The minimum number of points allowed is 3. | +| >>>Geographical Coordinates | M | | 7.4.23 | | +| >Ellipsoid point with altitude | | | | | +| >>Geographical Coordinates | M | | 7.4.23 | | +| >>Altitude and direction | M | | 7.4.22 | | +| >Ellipsoid point with altitude and uncertainty Ellipsoid | | | | | +| >>Geographical Coordinates | M | | 7.4.23 | | +| >>Altitude and direction | M | | 7.4.22 | | +| >>Uncertainty Ellipse | M | | 7.4.24 | | +| >>Uncertainty Altitude | M | | INTEGER ( 0..127) | The uncertainty altitude "h" expressed in metres is derived from the "Uncertainty Altitude" k, by: $h = 45 \times (1.025^k - 1)$ | +| >>Confidence | M | | INTEGER ( 0..100) | In percentage | +| >Ellipsoid Arc | | | | | +| >>Geographical Coordinates | M | | 7.4.23 | | +| >>Inner radius | M | | INTEGER ( 0..2 16 -1) | The relation between the value (N) and the radius (r) in meters it describes is $5N \leq r < 5(N+1)$ , except for $N = 2^{16} - 1$ for which the range is extended to include all greater values of (r). | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| >>Uncertainty radius | M | | INTEGER ( 0..127) | The uncertainty "r" is derived from the "Uncertainty radius" k by $r = 10 \times (1.1^k - 1)$ | +| >>Offset angle | M | | INTEGER ( 0..179) | The relation between the value (N) and the angle (a) in degrees it describes is $2N \leq a < 2(N+1)$ | +| >>Included angle | M | | INTEGER ( 0..179) | The relation between the value (N) and the angle (a) in degrees it describes is $2N < a \leq 2(N+1)$ | +| >>Confidence | M | | INTEGER ( 0..100) | | +| >High Accuracy Ellipsoid point with uncertainty Ellipse | | | | | +| >>High Accuracy Geographical Coordinates | M | | 7.4.41 | | +| >>High Accuracy Uncertainty Ellipse | M | | 7.4.42 | | +| >>Confidence | M | | INTEGER ( 0..100) | In percentage | +| >High Accuracy Ellipsoid point with Scalable uncertainty Ellipse | | | | | +| >>High Accuracy Geographical Coordinates | M | | 7.4.41 | | +| >>High Accuracy Scalable Uncertainty Ellipse | M | | 7.4.45 | | +| >>Confidence | M | | INTEGER ( 0..100) | In percentage | +| >High Accuracy Ellipsoid point with altitude and uncertainty Ellipsoid | | | | | +| >>High Accuracy Geographical Coordinates | M | | 7.4.41 | | +| >>High Accuracy Altitude | M | | 7.4.43 | | +| >>High Accuracy Uncertainty Ellipse | M | | 7.4.42 | | +| >>Confidence | M | | INTEGER ( 0..100) | In percentage | +| >>High Accuracy Uncertainty Altitude | M | | INTEGER ( 0..255) | The high accuracy uncertainty altitude "h" expressed in metres is derived from the high accuracy uncertainty code "k", by: $h = 0.3 \times (1.02^k - 1)$ | +| >>Vertical Confidence | M | | INTEGER ( 0..100) | In percentage | +| >High Accuracy Ellipsoid point with altitude and scalable uncertainty Ellipsoid | | | | | +| >>High Accuracy Geographical Coordinates | M | | 7.4.41 | | +| >>High Accuracy Altitude | M | | 7.4.43 | | +| >>High Accuracy Scalable Uncertainty Ellipse | M | | 7.4.45 | | +| >>Confidence | M | | INTEGER ( 0..100) | In percentage | +| >>High Accuracy Scalable Uncertainty Altitude | M | | 7.4.46 | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-----------------------|-----------------------| +| >>Vertical Confidence | M | | INTEGER ( 0..100) | In percentage | + +**Table 7.4.12-2: Range bound** + +| Range bound | Explanation | +|---------------|------------------------------------------------| +| maxnoofPoints | Maximum no. of points in polygon. Value is 15. | + +### 7.4.13 Positioning Data + +This parameter provides additional information for the positioning attempt from the E-SMLC. + +**Table 7.4.13-1: Positioning Data** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Position Data | M | | | | +| >Positioning Data Set | O | | | | +| >>Positioning Method and Usage | | 1.. | OCTET STRING (1) |

Coding of positioning method (bits 8-4):

  • 00000 Cell ID
  • 00001 Reserved
  • 00010 E-CID
  • 00011 Reserved
  • 00100 OTDOA
  • 00101 Reserved
  • 00110 Reserved
  • 00111 Reserved
  • 01000 U-TDOA
  • 01001 Reserved
  • 01010 Reserved
  • 01011 Reserved
  • 01100 to 01111 reserved for other location technologies
  • 10000 to 11111 reserved for network specific positioning methods

Coding of usage (bits 3-1):

  • 000 Attempted unsuccessfully due to failure or interruption - not used.
  • 001 Attempted successfully: results not used to generate location - not used.
  • 010 Attempted successfully: results used to verify but not generate location - not used.
  • 011 Attempted successfully: results used to generate location.
  • 100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined.
| +| >GNSS Positioning Data Set | O | | | | + +| | | | | | +|-------------------------------------------|---|-------------------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >>GNSS
Positioning Method
and Usage | O | 1..xGNS
SSet> | OCTET
STRING (1) | Coding of Method (Bits 8-7) :
00 : UE-Based
01 : UE-Assisted
10 : Conventional
11 : Reserved

Coding of GNSS ID (Bits 6-4) :
000 : GPS
001 : Galileo
010 : SBAS
011 : Modernized GPS
100 : QZSS
101 : GLONASS
110 : BDS
111 : NavIC

Coding of usage (bits 3-1):

000 Attempted unsuccessfully due to failure or interruption
001 Attempted successfully: results not used to generate location
010 Attempted successfully: results used to verify but not generate location
011 Attempted successfully: results used to generate location
100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined. | +| >Additional
Positioning Data
Set | O | | | | + +| | | | | | +|-------------------------------------------|--|---------------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >>Additional Positioning Method and Usage | | 1 to | OCTET STRING (SIZE(1)) |

Coding of positioning method (bits 8-7):
00 UE-Based;
01 UE-Assisted;
10 Standalone;
11 Reserved.

Coding of Additional Positioning ID (bits 6-4):
000 Barometric Pressure;
001 WLAN;
010 Bluetooth;
011 MBS;
100 Motion-Sensor(s);
other values reserved.

Coding of usage (bits 3-1):

000 Attempted unsuccessfully due to failure or interruption
001 Attempted successfully: results not used to generate location
010 Attempted successfully: results used to verify but not generate location
011 Attempted successfully: results used to generate location
100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined.

| +|-------------------------------------------|--|---------------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Table 7.4.13-2: Range bound + +| Range bound | Explanation | +|--------------|-------------------------------------------| +| maxSet | Maximum size of the data set. Value is 9. | +| maxGNSSSet | Maximum size of the data. Value is 9. | +| maxAddPosSet | Maximum size of the data Value is 8. | + +### 7.4.14 Velocity Estimate + +This parameter provides the velocity estimate for the target UE. + +**Table 7.4.14-1: Velocity Estimate** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Choice Velocity Estimate | | | | | +| >Horizontal Velocity | | | | Horizontal speed and bearing (the direction of travel). | +| >>Horizontal Speed and Bearing | M | | 7.4.25 | | +| >Horizontal with Vertical Velocity | | | | Horizontal speed and bearing (the direction of travel) as well as vertical speed and the direction (upward or downward) | +| >>Horizontal Speed and Bearing | M | | 7.4.25 | | +| >>Vertical Velocity | M | | 7.4.26 | | +| >Horizontal Velocity with Uncertainty | | | | Horizontal speed, bearing (the direction of travel), and the uncertainty of the reported speed. | +| >>Horizontal Speed and Bearing | M | | 7.4.25 | | +| >>Uncertainty Speed | M | | INTEGER (0..255) | Uncertainty speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified | +| >Horizontal with Vertical Velocity and Uncertainty | | | | Horizontal speed and bearing (the direction of travel) as well as vertical speed and the direction (upward or downward) and the uncertainty of the reported speed. | +| >>Horizontal Speed and Bearing | M | | 7.4.25 | | +| >>Vertical Velocity | M | | 7.4.26 | | +| >>Horizontal Uncertainty Speed | M | | INTEGER (0..255) | Horizontal Uncertainty Speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified | +| >>Vertical Uncertainty Speed | M | | INTEGER (0..255) | Vertical Uncertainty Speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified | + +### 7.4.15 Accuracy Fulfilment Indicator + +This parameter whether the returned position estimate satisfies the requested accuracy or not. + +Table 7.4.15-1: Accuracy Fulfilment Indicator + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|-------------------------------------------------------------------------------------------|----------------------------------------------------------| +| Accuracy Fulfilment Indicator | O | | ENUMERATED
(requested accuracy fulfilled,
requested accuracy not fulfilled,
...) | Indicates if the requested accuracy is fulfilled or not. | + +### 7.4.16 LCS Cause + +The LCS Cause is included if and only if a requested location estimate was not successfully obtained (e.g. location estimate not available), requested LCS assistance data was not successfully transferred to the UE or location-related data has been lost. The parameter provides the reason for the failure. + +Table 7.4.16-1: LCS Cause + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| CHOICE Cause Group | | | | | +| >Radio Network Layer | | | | | +| >>Radio Network Layer Cause | M | | ENUMERATED
(
Unspecified
...) | | +| >Transport Layer | | | | | +| >>Transport Layer Cause | M | | ENUMERATED
(Transport Resource Unavailable,
Unspecified,
...) | | +| >Protocol | | | | | +| >>Protocol Cause | M | | ENUMERATED
(Transfer Syntax Error,
Abstract Syntax Error (Reject),
Abstract Syntax Error (Ignore and
Notify),
Message not Compatible with
Receiver State,
Semantic Error,
Unspecified,
Abstract Syntax Error (Falsely
Constructed Message),
...) | | +| >Misc | | | | | +| >>Misc Cause | M | | ENUMERATED
(Processing Overload,
Hardware Failure,
O&M Intervention,
Unspecified,
...,
Ciphering Key Data Lost) | | + +### 7.4.17 Payload Type + +This parameter indicates the type of APDU included in LCS-AP Connected Oriented Information message. The supported information types are LPP and LPPa. + +**Table 7.4.17-1: Payload Type** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|--------------------------------------|-----------------------| +| Payload Type | M | | ENUMERATED
(LPP,
LPPa,
...) | | + +### 7.4.18 APDU + +This parameter contains an embedded APDU. For information transfer between an E-SMLC and an eNB this shall be an LPPa APDU. For information transfer between an E-SMLC and a target UE, this shall be an LPP APDU. + +**Table 7.4.18-1: APDU** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------| +| APDU | M | | OCTET STRING | This IE contains a message whose content and encoding are defined according to the Payload Type. | + +### 7.4.19 Network Element + +This parameter identifies the source or destination of the message. The network element is identified by association with either an eNB ID or the identity of an E-SMLC. + +**Table 7.4.19-1: Network Element** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------| +| CHOICE Network Element | M | | | | +| >Global eNB ID | | | | The global identity of the eNB | +| >>PLMN Identity | | | 7.4.27 | | +| >>eNB ID | | | 7.4.29 | | +| >E-SMLC Identity | | | INTEGER (0..255) | The identity of the E-SMLC (an index to identify an specific E-SMLC among all the available E-SMLCs in the network) | + +### 7.4.20 Return Error Request + +This parameter may be included to request an error response if LCS-AP message cannot be delivered successfully to its final destination. This parameter shall not be included if the Return Error cause is present. + +**Table 7.4.20-1: Return Error Type** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|---------------------------------|-----------------------| +| Return Error Type | M | | ENUMERATED (
Yes,
No
) | | + +### 7.4.21 Return Error Cause + +This parameter indicates an error response for a LCS-AP connectionless information message that could not be delivered to its final destination. The APDU should be present and the same as the APDU in the original undelivered + +message. The source and destination identities shall be included and the same as the destination and source identities, respectively, in the original undelivered message. + +**Table 7.4.21-1: Return Error Cause** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------|-----------------------| +| Return Error Cause | M | | ENUMERATED
(systemfailure,
protocolerror,
destinationunkown,
destinationunreachable,
congestion,...) | | + +### 7.4.22 Altitude and direction + +**Table 7.4.22-1: Altitude and direction** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Direction of Altitude | M | | ENUMERATED
(Height, Depth) | | +| Altitude | M | | INTEGER (
0..2 15 -1) | The relation between the value (N) and the altitude (a) in meters it describes is $N \leq a < N+1$ , except for $N=2^{15}-1$ for which the range is extended to include all greater values of (a). | + +### 7.4.23 Geographical Coordinates + +This IE contains the geographical coordinates. + +**Table 7.4.23-1: Geographical Coordinates** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| Latitude Sign | M | | ENUMERATED
(North, South) | | +| Degrees Of Latitude | M | | INTEGER (
0..2 23 -1) | The IE value (N) is derived by this formula: $N \leq 2^{23} \times X / 90 < N+1$ X being the latitude in degree (0°.. 90°) | +| Degrees Of Longitude | M | | INTEGER (
-2 23 ..2 23 -1) | The IE value (N) is derived by this formula: $N \leq 2^{24} \times X / 360 < N+1$ X being the longitude in degree (-180°..+180°) | + +### 7.4.24 Uncertainty Ellipse + +This IE contains the uncertainty ellipse of a geographical area. + +**Table 7.4.24-1: Uncertainty Ellipse** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------| +| Uncertainty semi-major | M | | INTEGER (0..127) | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10 \times (1.1^k - 1)$ | +| Uncertainty semi-minor | M | | INTEGER (0..127) | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10 \times (1.1^k - 1)$ | +| Orientation of major axis | M | | INTEGER (0..89) | The relation between the IE value (N) and the angle (a) in degrees it describes is $2N \leq a < 2(N+1)$ | + +### 7.4.25 Horizontal Speed and Bearing + +This IE contains the two components of horizontal velocity: speed and bearing + +**Table 7.4.25-1: Horizontal Speed and Bearing** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bearing | M | | INTEGER (0..359) | The direction of movement is given in degrees where '0' represents North, '90' represents East, etc. | +| Horizontal Speed | M | | INTEGER (0..2 11 -1) | The relationship between (N) and the horizontal speed (h) in kilometers per hour it describes is:
$N \leq h < N + 0.5$ (N=0)
$N - 0.5 \leq h < N + 0.5$ (0 < N < 2 11 -1)
$N - 0.5 \leq h$ (N = 2 11 -1) | + +### 7.4.26 Vertical Velocity + +This IE contains the two components of vertical velocity: speed and direction + +**Table 7.4.26-1: Vertical Velocity** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Vertical Speed | M | | INTEGER (0..2 8 -1) | The relationship between (N) and the vertical speed (v) in kilometers per hour it describes is:
$N \leq v < N + 0.5$ (N = 0)
$N - 0.5 \leq v < N + 0.5$ (0 < N < 2 8 -1)
$N - 0.5 \leq v$ (N = 2 8 -1) | +| Vertical Speed Direction | | | ENUMERATED (upward, downward) | | + +### 7.4.27 PLMN Identity + +This information element indicates the PLMN Identity. + +**Table 7.4.27-1: PLMN Identity** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PLMN identity | M | | OCTET STRING (SIZE (3)) |
  • - digits 0 to 9, encoded 0000 to 1001,
  • - 1111 used as filler digit, two digits per octet,
  • - bits 4 to 1 of octet n encoding digit 2n-1
  • - bits 8 to 5 of octet n encoding digit 2n

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

  • -a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or
  • -3 digits from MNC (in case of a 3 digit MNC).
| + +### 7.4.28 Correlation ID + +This IE indicates a specific location session. It is used in order to correlate request/response and an ongoing location session. + +**Table 7.4.28-1: Correlation ID** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| Correlation ID | M | | OCTET STRING (SIZE (4)) | The identifier of a location session in E-UTRAN. It should be unique for all concurrently active location sessions in a particular MME. | + +### 7.4.29 eNB ID + +This information element is used to identify an eNB. + +**Table 7.4.29-1: eNB ID** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE eNB ID | | | | | +| >Macro eNB ID | | | BIT STRING (20) | Equal to the 20 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see clause 7.4.4) of each cell served by the eNB | +| >Home eNB ID | | | BIT STRING (28) | Equal to the Cell Identity IE contained in the E-UTRAN CGI IE (see clause 7.4.4) of the cell served by the eNB | +| >Short Macro eNB ID | | | BIT STRING (18) | Equal to the 18 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see clause 7.4.4) of each cell served by the eNB | +| >Long Macro eNB ID | | | BIT STRING (21) | Equal to the 21 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see clause 7.4.4) of each cell served by the eNB | + +### 7.4.30 LCS Service Type ID + +This parameter defines the service type ID for the location request. + +**Table 7.4.30-1: LCS Service Type ID** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------| +| LCS Service Type ID | O | | INTEGER(0..127) | Identifies the type of service requested. The meaning of the different service types is defined in TS 22.071 [10]. | + +### 7.4.31 Cell Portion ID + +This parameter gives the current Cell Portion location of the target UE. The Cell Portion ID is the unique identifier for a cell portion within a cell. + +**Table 7.4.31-1: Cell Portion** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|-------------------------------|-----------------------| +| Cell Portion ID | M | | INTEGER(0..255,...,256..4095) | | + +### 7.4.32 Civic Address + +This information element contains a location estimate for the target UE expressed as a Civic address. + +Table 7.4.32-1: Civic Address + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Civic Address | O | | OCTET STRING | This IE contains a UTF-8 encoded PIDF-LO XML document as defined in IETF RFC 4119 [13]. The document shall only contain a civic address using the namespaces "urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" per IETF RFC 5139 [14] and "urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr:ext" per IETF RFC 6848 [15]. | + +### 7.4.33 Barometric Pressure + +This information element contains the barometric pressure measurement as reported by the target UE. + +Table 7.4.33-1: Barometric Pressure + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-------------------------|--------------------------------------------------------------------------------------------| +| Barometric Pressure | O | | INTEGER (30000..115000) | This IE specifies the measured uncompensated atmospheric pressure in units of Pascal (Pa). | + +### 7.4.34 RAT Type + +This parameter provides the serving RAT type for the target UE or the last known serving RAT type for the case when the Location Type IE is set to last known location. + +Table 7.4.34-1: RAT Type + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------------------------|----------------------------------------| +| RAT Type | O | | ENUMERATED (lte-wb, nb-iot, lte-m, ...) | This IE provides the serving RAT type. | + +### 7.4.35 Coverage Level + +This parameter defines the type of coverage level being requested. + +Table 7.4.35-1: Coverage Level + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-------------------------------------|-----------------------| +| Coverage Level | O | | ENUMERATED (Extended Coverage, ...) | | + +### 7.4.36 Ciphering Data + +This parameter contains the ciphering data sets sent by the E-SMLC to the MME. + +Table 7.4.36-1: Ciphering Data + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------------------|-----------------------|-----------------------| +| Ciphering Data | M | | | | +| >Ciphering Data Set | M | 1.. | 7.4.39 | | + +Table 7.4.36-2: Range bound + +| Range bound | Explanation | +|--------------|-------------------------------------------| +| maxCipherSet | Maximum size of the data set. Value is 16 | + +### 7.4.37 Ciphering Data Ack + +This parameter contains the ciphering data acknowledgement information sent by the MME to the E-SMLC. + +Table 7.4.37-1: Ciphering Data Ack + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------------------|-----------------------|------------------------------------------------------------------------------------------------| +| Ciphering Data Ack | M | | | This IE contains the list of ciphering set IDs for which the MME is sending an acknowledgement | +| >Ciphering Set ID | M | 1.. | INTEGER (0..65535) | | + +Table 7.4.37-2: Range bound + +| Range bound | Explanation | +|--------------|-------------------------------------------| +| maxCipherSet | Maximum size of the data set. Value is 16 | + +### 7.4.38 Ciphering Data Error Report + +This parameter contains a list of ciphering data sets with the associated outcome of storage attempt at the MME. + +Table 7.4.38-1: Ciphering Data Error Report + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------------------|-----------------------|-----------------------| +| Ciphering Data Error Report | M | | | | +| >Ciphering Data Error Report Contents | M | 1.. | 7.4.40 | | + +Table 7.4.38-2: Range bound + +| Range bound | Explanation | +|--------------|-------------------------------------------| +| maxCipherSet | Maximum size of the data set. Value is 16 | + +### 7.4.39 Ciphering Data Set + +This parameter contains a ciphering data set sent by the E-SMLC to the MME. + +**Table 7.4.39-1: Ciphering Data Set** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|----------------------------------|-----------------------| +| Ciphering Data Set | M | | | | +| >Ciphering Set ID | M | | INTEGER
(0..65535) | | +| >Ciphering Key | M | | OCTET
STRING
(SIZE(16)) | | +| >c0 | M | | BIT STRING
(SIZE
(1..128)) | | + +| | | | | | +|------------|---|--|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >SIB Types | M | | OCTET
STRING
(SIZE(4)) |

This IE contains a bitmap indicating the positioning SIB types for which the ciphering data set is applicable:

  • -- a bit set to 0 indicates that the ciphering data set is not applicable to the corresponding positioning SIB type
  • - a bit set to 1 indicates that the ciphering data set is applicable to the corresponding positioning SIB type

The mapping of the bits to the positioning SIB types is as follows:

  • -- bit 8 in the first octet maps to positioning SIB Type 1-1
  • -- bit 7 in the first octet maps to positioning SIB Type 1-2
  • -- bit 6 in the first octet maps to positioning SIB Type 1-3
  • -- bit 5 in the first octet maps to positioning SIB Type 1-4
  • -- bit 4 in the first octet maps to positioning SIB Type 1-5
  • -- bit 3 in the first octet maps to positioning SIB Type 1-6
  • -- bit 2 in the first octet maps to positioning SIB Type 1-7
  • -- bit 1 in the first octet maps to positioning SIB Type 2-1
  • -- bit 8 in the second octet maps to positioning SIB Type 2-2
  • -- bit 7 in the second octet maps to positioning SIB Type 2-3
  • -- bit 6 in the second octet maps to positioning SIB Type 2-4
  • -- bit 5 in the second octet maps to positioning SIB Type 2-5
  • -- bit 4 in the second octet maps to positioning SIB Type 2-6
  • -- bit 3 in the second octet maps to positioning SIB Type 2-7
  • -- bit 2 in the second octet maps to positioning SIB Type 2-8
  • -- bit 1 in the second octet maps to positioning SIB Type 2-9
  • -- bit 8 in the third octet maps to positioning SIB Type 2-10
  • -- bit 7 in the third octet maps to positioning SIB
| +|------------|---|--|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|----------------|---|--|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >SIB Types Ext | O | | OCTET
STRING
(SIZE(4)) |

This IE contains extension of the bitmap SIB Types indicating the positioning SIB types for which the ciphering data set is applicable:

  • -- a bit set to 0 indicates that the ciphering data set is not applicable to the corresponding positioning SIB type
  • -- a bit set to 1 indicates that the ciphering data set is applicable to the corresponding positioning SIB type

The mapping of the bits to the positioning SIB types is as follows:

  • -- bit 8 in the first octet maps to positioning SIB Type 1-8
  • -- bit 7 in the first octet maps to positioning SIB Type 2-20
  • -- bit 6 in the first octet maps to positioning SIB Type 2-21
  • -- bit 5 in the first octet maps to positioning SIB Type 2-22
  • -- bit 4 in the first octet maps to positioning SIB Type 2-23
  • -- bit 3 in the first octet maps to positioning SIB Type 2-24
  • -- bit 2 in the first octet maps to positioning SIB Type 2-25

Any unassigned bits are spare and shall be coded as zero. In the absence of this IE, the ciphering data set is not applicable for any of the positioning SIB types mapped by this IE.

| +|----------------|---|--|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | +|----------------------|---|--|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >Validity Start time | M | | OCTET STRING (SIZE(4)) | This IE contains the UTC time when the ciphering data set becomes valid, encoded in the same format as the first four octets of the 64-bit timestamp format as defined in clause 6 of IETF RFC 5905 [16]. | +| >Validity Duration | M | | INTEGER (0..65535) | In minutes | +| >TAIs List | O | | OCTET STRING (SIZE (7..97)) | This IE contains the TAIs of the tracking areas for which the ciphering data set is applicable. It is encoded as octets 2 to n of the Tracking area identity list IE specified in clause 9.9.3.33 of TS 24.301 [17].

If this IE is omitted, the ciphering data set is valid in the entire PLMN. | + +### 7.4.40 Ciphering Data Error Report Contents + +This parameter contains a ciphering data set ID with the associated outcome of storage attempt at the MME. + +**Table 7.4.40-1: Ciphering Data Error Report Contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|-------|-----------------------------------|------------------------------------------------------------------------------------------------| +| Ciphering Data Error Report Contents | M | | | | +| >Ciphering Set ID | M | | INTEGER (0..65535) | This IE contains the list of ciphering set IDs for which the MME is sending an acknowledgement | +| >Storage outcome | M | | ENUMERATED ( Successful, Failed ) | | + +### 7.4.41 High Accuracy Geographical Coordinates + +This IE contains the high accuracy geographical coordinates. + +**Table 7.4.41-1: High Accuracy Geographical Coordinates** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| High Accuracy Degrees Of Latitude | M | | INTEGER ( $-2^{31}..2^{31}-1$ ) | The IE value (N) is derived by this formula:
$N = 2^{31} \times X / 90$
X being the latitude in degree ( $-90^\circ..+90^\circ$ ) | +| High Accuracy Degrees Of Longitude | M | | INTEGER ( $-2^{31}..2^{31}-1$ ) | The IE value (N) is derived by this formula:
$N = 2^{31} \times X / 180$
X being the longitude in degree ( $-180^\circ..+180^\circ$ ) | + +### 7.4.42 High Accuracy Uncertainty Ellipse + +This IE contains the high accuracy uncertainty ellipse of a geographical area, using the range (0..255) for high-accuracy uncertainty code "k", as specified in TS 23.032 [6]. + +**Table 7.4.42-1: High Accuracy Uncertainty Ellipse** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------| +| High Accuracy Uncertainty semi-major | M | | INTEGER (0..255) | The high accuracy uncertainty "r" is derived from the high accuracy uncertainty code "k" by:
$r = 0.3 \times (1.02^k - 1)$ | +| High Accuracy Uncertainty semi-minor | M | | INTEGER (0..255) | The high accuracy uncertainty "r" is derived from the high accuracy uncertainty code "k" by:
$r = 0.3 \times (1.02^k - 1)$ | +| Orientation of major axis | M | | INTEGER (0..179) | Angle in degrees between the major axis and north | + +### 7.4.43 High Accuracy Altitude + +**Table 7.4.43-1: High Accuracy Altitude** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------|----------|-------|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| High Accuracy Altitude | M | | INTEGER ( $-64000..1280000$ ) | The relation between the IE value (N) and the altitude a (in metres) it encodes is described by the following equation:
$a = N \times 2^{-7}$ | + +### 7.4.44 High Accuracy Extended Uncertainty Ellipse + +This IE contains the high accuracy extended uncertainty ellipse of a geographical area, using the range (0..255) for High Accuracy Extended Uncertainty code "k", as specified in TS 23.032 [6]. + +**Table 7.4.44-1: High Accuracy Extended Uncertainty Ellipse** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| High Accuracy Extended Uncertainty semi-major | M | | INTEGER (0..255) | The high accuracy extended uncertainty "r" is derived from the high accuracy extended uncertainty code "k", as specified in TS 23.032 [6] | +| High Accuracy Extended Uncertainty semi-minor | M | | INTEGER (0..255) | The high accuracy extended uncertainty "r" is derived from the high accuracy extended uncertainty code "k", as specified in TS 23.032 [6] | +| Orientation of major axis | M | | INTEGER (0..179) | Angle in degrees between the major axis and north | + +### 7.4.45 High Accuracy Scalable Uncertainty Ellipse + +**Table 7.4.45-1: High Accuracy Scalable Uncertainty Ellipse** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE High Accuracy Scalable Uncertainty Ellipse | | | | | +| >High Accuracy Uncertainty Ellipse | | | 7.4.42 | | +| >High Accuracy Extended Uncertainty Ellipse | | | 7.4.44 | | + +### 7.4.46 High Accuracy Scalable Uncertainty Altitude + +**Table 7.4.46-1: High Accuracy Scalable Uncertainty Altitude** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE High Accuracy Scalable Uncertainty Altitude | | | | | +| >High Accuracy Uncertainty Altitude | | | INTEGER (0..255) | The high accuracy uncertainty altitude "h" expressed in metres is derived from the high accuracy uncertainty code "k", by:
$h=0.3 \times (1.02^k - 1)$ | +| >High Accuracy Extended Uncertainty Altitude | | | INTEGER (0..255) | The high accuracy extended uncertainty "r" is derived from the high accuracy extended uncertainty code "k", as specified in TS 23.032 [6] | + +### 7.4.47 UE Country Determination Indication + +This parameter indicates whether the determining of geographical area identified by the country, area within a country or international area where UE is located for PLMN selection verification is required or not. + +**Table 7.4.47-1: UE Country Determination Indication** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE Country Determination Indication | O | | ENUMERATED
(required,
not required,
...) | Indicates if the determining of geographical area identified by the country, area within a country or international area where UE is located for PLMN selection verification is required or not. | + +### 7.4.48 UE Area Indication + +This parameter contains a country, area within a country or international area indication where UE is located. + +**Table 7.4.48-1: UE Area Indication** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------------------------------------|----------|-------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Country | O | | OCTET STRING | Includes the country or the area of country where the UE is located. This IE contains two-letter ISO 3166 country code in capital ASCII letters, e.g., DE or US. IETF RFC 4776 [18] | +| International Area Indication | O | | ENUMERATED (
Yes,
...) | Indicates the UE is located in international area. | +| NOTE: Either Country or International Area Indication shall be present. | | | | | + +## 7.5 Message and information element abstract syntax + +### 7.5.1 General + +LCS-AP ASN.1 definition conforms to [8] and [9]. + +The ASN.1 definition specifies the structure and content of LCS-AP messages. LCS-AP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a LCS-AP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids): + +- IEs shall be ordered (in an IE container) in the order they appear in object set definitions. +- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. + +If a LCS-AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error in clause 10 of [7]. + +### 7.5.2 Usage of protocol extension mechanism for non-standard use + +The protocol extension mechanism for non-standard use may be used: + +- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multi-vendor interoperability. +- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation. + +The extension mechanism shall not be used for basic functionality. Such functionality shall be standardised. + +### 7.5.3 Elementary procedure definitions + +``` + +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** + +LCS-AP-PDU-Descriptions { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-PDU-Descriptions (0)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + ProcedureCode +FROM LCS-AP-CommonDataTypes + + Location-Request, + Location-Response, + Location-Abort-Request, + Connection-Oriented-Information, + Connectionless-Information, + Reset-Request, + Reset-Acknowledge, + Ciphering-Key-Data, + Ciphering-Key-Data-Result +FROM LCS-AP-PDU-Contents + + id-Location-Service-Request, + id-Connection-Oriented-Information-Transfer, + id-Connectionless-Information-Transfer, + id-Location-Abort, + id-Reset, + id-Ciphering-Key-Data-Delivery +FROM LCS-AP-Constants; + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +LCS-AP-ELEMENTARY-PROCEDURE ::= CLASS { + &InitiatingMessage , + &SuccessfulOutcome OPTIONAL, + &UnsuccessfulOutcome OPTIONAL, + &procedureCode ProcedureCode UNIQUE, + &criticality Criticality DEFAULT ignore +} +WITH SYNTAX { + +``` + +``` + + INITIATING MESSAGE &InitiatingMessage + [SUCCESSFUL OUTCOME &SuccessfulOutcome] + [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] + PROCEDURE CODE &procedureCode + [CRITICALITY &criticality] + } + + -- ***** + -- + -- Interface PDU Definition + -- + -- ***** + + LCS-AP-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + ... + } + + InitiatingMessage ::= SEQUENCE { + procedureCode LCS-AP-ELEMENTARY-PROCEDURE.&procedureCode ({LCS-AP-ELEMENTARY-PROCEDURES}), + criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value LCS-AP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}) + } + + SuccessfulOutcome ::= SEQUENCE { + procedureCode LCS-AP-ELEMENTARY-PROCEDURE.&procedureCode ({LCS-AP-ELEMENTARY-PROCEDURES}), + criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value LCS-AP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}) + } + + UnsuccessfulOutcome ::= SEQUENCE { + procedureCode LCS-AP-ELEMENTARY-PROCEDURE.&procedureCode ({LCS-AP-ELEMENTARY-PROCEDURES}), + criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value LCS-AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}) + } + + -- ***** + -- + -- Interface Elementary Procedure List + -- + -- ***** + + LCS-AP-ELEMENTARY-PROCEDURES LCS-AP-ELEMENTARY-PROCEDURE ::= { + LCS-AP-ELEMENTARY-PROCEDURES-CLASS-1 | + LCS-AP-ELEMENTARY-PROCEDURES-CLASS-2 , + ... + } + + LCS-AP-ELEMENTARY-PROCEDURES-CLASS-1 LCS-AP-ELEMENTARY-PROCEDURE ::= { + location-Service-Request | + connectionless-Information-Transfer | + location-Abort | + reset | + ciphering-Key-Data-Delivery , + ... + } + + LCS-AP-ELEMENTARY-PROCEDURES-CLASS-2 LCS-AP-ELEMENTARY-PROCEDURE ::= { + connection-Oriented-Information-Transfer , + ... + } + + -- ***** + -- + -- Interface Elementary Procedures + -- + -- ***** + +``` + +``` + +location-Service-Request LCS-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Location-Request + SUCCESSFUL OUTCOME Location-Response + UNSUCCESSFUL OUTCOME Location-Response + PROCEDURE CODE id-Location-Service-Request + CRITICALITY reject +} + +connection-Oriented-Information-Transfer LCS-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Connection-Oriented-Information + PROCEDURE CODE id-Connection-Oriented-Information-Transfer + CRITICALITY reject +} + +connectionless-Information-Transfer LCS-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Connectionless-Information + UNSUCCESSFUL OUTCOME Connectionless-Information + PROCEDURE CODE id-Connectionless-Information-Transfer + CRITICALITY reject +} + +location-Abort LCS-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Location-Abort-Request + SUCCESSFUL OUTCOME Location-Response + PROCEDURE CODE id-Location-Abort + CRITICALITY reject +} + +reset LCS-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Reset-Request + SUCCESSFUL OUTCOME Reset-Acknowledge + PROCEDURE CODE id-Reset + CRITICALITY reject +} + +ciphering-Key-Data-Delivery LCS-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Ciphering-Key-Data + SUCCESSFUL OUTCOME Ciphering-Key-Data-Result + UNSUCCESSFUL OUTCOME Ciphering-Key-Data-Result + PROCEDURE CODE id-Ciphering-Key-Data-Delivery + CRITICALITY reject +} + +END + +``` + +### 7.5.4 PDU definitions + +``` + +-- ************************************************************** +-- +-- PDU definitions for LCS-AP. +-- +-- ************************************************************** + +LCS-AP-PDU-Contents { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-PDU-Contents (1) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ************************************************************** +-- +-- IE parameter types from other modules. +-- +-- ************************************************************** + +IMPORTS + + APDU, + Accuracy-Fulfillment-Indicator, + Barometric-Pressure, + Cell-Portion-ID, + Ciphering-Data, + Ciphering-Data-Ack, + Ciphering-Data-Error-Report, + +``` + +``` + +Civic-Address, +Correlation-ID, +Coverage-Level, +E-CGI, +Geographical-Area, +IMSI, +IMEI, +Include-Velocity, +LCS-Cause, +LCS-Client-Type, +LCS-Service-Type-ID, +LCS-Priority, +LCS-QoS, +Location-Type, +MultipleAPDUs, +Network-Element, +Payload-Type, +Positioning-Data, +RAT-Type, +Return-Error-Type, +Return-Error-Cause, +UE-Positioning-Capability, +Velocity-Estimate, +UE-Country-Determination-Indication, +UE-Area-Indication +FROM LCS-AP-IEs + +``` + +``` + +ProtocolExtensionContainer{}, +ProtocolIE-Container{}, +LCS-AP-PROTOCOL-EXTENSION, +LCS-AP-PROTOCOL-IEs +FROM LCS-AP-Containers + +``` + +``` + +id-Accuracy-Fulfillment-Indicator, +id-APDU, +id-Barometric-Pressure, +id-Cell-Portion-ID, +id-Ciphering-Data, +id-Ciphering-Data-Ack, +id-Ciphering-Data-Error-Report, +id-Civic-Address, +id-Correlation-ID, +id-Coverage-Level, +id-Destination-ID, +id-E-UTRAN-Cell-Identifier, +id-Include-Velocity, +id-IMEI, +id-IMSI, +id-LCS-Client-Type, +id-LCS-Priority, +id-LCS-QoS, +id-LCS-Cause, +id-LCS-Service-Type-ID, +id-Location-Estimate, +id-Location-Type, +id-MultipleAPDUs, +id-Payload-Type, +id-Positioning-Data, +id-RAT-Type, +id-Return-Error-Request, +id-Return-Error-Cause, +id-Source-Identity, +id-UE-Positioning-Capability, +id-Velocity-Estimate, +id-UE-Country-Determination-Indication, +id-UE-Area-Indication +FROM LCS-AP-Constants; + +``` + +``` + +-- ***** +-- +-- Location-Request +-- +-- ***** + +``` + +``` + +Location-Request ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { Location-Request-IEs} }, + protocolExtensions ProtocolExtensionContainer { { Location-Request-Extensions} } OPTIONAL, +} + +``` + +``` + + ... + } + + Location-Request-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE mandatory } | + { ID id-Location-Type CRITICALITY reject TYPE Location-Type PRESENCE mandatory } | + { ID id-E-UTRAN-Cell-Identifier CRITICALITY ignore TYPE E-CGI PRESENCE mandatory } | + { ID id-LCS-Client-Type CRITICALITY reject TYPE LCS-Client-Type PRESENCE optional } | + { ID id-LCS-Priority CRITICALITY reject TYPE LCS-Priority PRESENCE optional } | + { ID id-LCS-QoS CRITICALITY reject TYPE LCS-QoS PRESENCE optional } | + { ID id-UE-Positioning-Capability CRITICALITY reject TYPE UE-Positioning-Capability PRESENCE +optional } | + { ID id-Include-Velocity CRITICALITY reject TYPE Include-Velocity PRESENCE optional } | + { ID id-IMSI CRITICALITY ignore TYPE IMSI PRESENCE optional } | + { ID id-IMEI CRITICALITY ignore TYPE IMEI PRESENCE optional } | + { ID id-MultipleAPDUs CRITICALITY reject TYPE MultipleAPDUs PRESENCE optional } | + { ID id-RAT-Type CRITICALITY ignore TYPE RAT-Type PRESENCE optional } | + { ID id-Coverage-Level CRITICALITY ignore TYPE Coverage-Level PRESENCE optional}, + ... + } + + Location-Request-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + { ID id-LCS-Service-Type-ID CRITICALITY ignore EXTENSION LCS-Service-Type-ID PRESENCE +optional } | + { ID id-UE-Country-Determination-Indication CRITICALITY ignore EXTENSION UE-Country- +Determination-Indication PRESENCE optional}, + ... + } + + -- ***** + -- + -- Location-Response + -- + -- ***** + + Location-Response ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Location-Response-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Location-Response-Extensions} } OPTIONAL, + ... + } + + Location-Response-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE mandatory } | + { ID id-Location-Estimate CRITICALITY reject TYPE Geographical-Area PRESENCE optional } +| + { ID id-Positioning-Data CRITICALITY reject TYPE Positioning-Data PRESENCE optional } +| + { ID id-Velocity-Estimate CRITICALITY reject TYPE Velocity-Estimate PRESENCE optional } +| + { ID id-Accuracy-Fulfillment-Indicator CRITICALITY reject TYPE Accuracy-Fulfillment-Indicator +PRESENCE optional } | + { ID id-LCS-Cause CRITICALITY ignore TYPE LCS-Cause PRESENCE optional } , + ... + } + + Location-Response-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + { ID id-E-UTRAN-Cell-Identifier CRITICALITY ignore EXTENSION E-CGI PRESENCE optional } | + { ID id-Cell-Portion-ID CRITICALITY ignore EXTENSION Cell-Portion-ID PRESENCE optional } | + { ID id-Civic-Address CRITICALITY ignore EXTENSION Civic-Address PRESENCE optional } | + { ID id-Barometric-Pressure CRITICALITY ignore EXTENSION Barometric-Pressure PRESENCE +optional } | + { ID id-UE-Area-Indication CRITICALITY ignore EXTENSION UE-Area-Indication PRESENCE +optional }, + ... + } + + -- ***** + -- + -- Location-Abort + -- + -- ***** + + Location-Abort-Request ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Location-Abort-Request-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Location-Abort-Request-Extensions} } OPTIONAL, + ... + } + +``` + +``` + +} + +Location-Abort-Request-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE mandatory } | + { ID id-LCS-Cause CRITICALITY ignore TYPE LCS-Cause PRESENCE mandatory } , + ... +} + +Location-Abort-Request-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Connection-Oriented-Information +-- +-- ***** + +Connection-Oriented-Information ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Connection-Oriented-Information-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Connection-Oriented-Information-Extensions} } + OPTIONAL, + ... +} + +Connection-Oriented-Information-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE optional } | + { ID id-Payload-Type CRITICALITY reject TYPE Payload-Type PRESENCE optional } | + { ID id-APDU CRITICALITY reject TYPE APDU PRESENCE optional } , + ... +} + +Connection-Oriented-Information-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Connectionless-Information +-- +-- ***** + +Connectionless-Information ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Connectionless-Information-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Connectionless-Information-Extensions} } + OPTIONAL, + ... +} + +Connectionless-Information-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-Source-Identity CRITICALITY reject TYPE Network-Element PRESENCE mandatory } | + { ID id-Destination-ID CRITICALITY reject TYPE Network-Element PRESENCE mandatory } | + { ID id-APDU CRITICALITY reject TYPE APDU PRESENCE mandatory } | + { ID id-Return-Error-Request CRITICALITY reject TYPE Return-Error-Type PRESENCE optional } + | + { ID id-Return-Error-Cause CRITICALITY ignore TYPE Return-Error-Cause PRESENCE optional } , + ... +} + +Connectionless-Information-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Reset-Request +-- +-- ***** + +Reset-Request ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Reset-Request-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Reset-Request-Extensions} } OPTIONAL, + ... +} + +Reset-Request-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-LCS-Cause CRITICALITY ignore TYPE LCS-Cause PRESENCE mandatory } , + +``` + +``` + ... +} + +Reset-Request-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Reset-Acknowledge +-- +-- ***** + +Reset-Acknowledge ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { Reset-Acknowledge-IEs } }, + protocolExtensions ProtocolExtensionContainer { { Reset-Acknowledge-Extensions } } OPTIONAL, + ... +} + +Reset-Acknowledge-IEs LCS-AP-PROTOCOL-IES ::= { + ... +} + +Reset-Acknowledge-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Ciphering-Key-Data +-- +-- ***** + +Ciphering-Key-Data ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { Ciphering-Key-Data-IEs } }, + protocolExtensions ProtocolExtensionContainer { { Ciphering-Key-Data-Extensions } } OPTIONAL, + ... +} + +Ciphering-Key-Data-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-Ciphering-Data CRITICALITY reject TYPE Ciphering-Data PRESENCE mandatory } , + ... +} + +Ciphering-Key-Data-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Ciphering-Key-Data-Result +-- +-- ***** + +Ciphering-Key-Data-Result ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { Ciphering-Key-Data-Result-IEs } }, + protocolExtensions ProtocolExtensionContainer { { Ciphering-Key-Data-Result-Extensions } } +OPTIONAL, + ... +} + +Ciphering-Key-Data-Result-IEs LCS-AP-PROTOCOL-IES ::= { + { ID id-Ciphering-Data-Ack CRITICALITY reject TYPE Ciphering-Data-Ack PRESENCE conditional } | + { ID id-Ciphering-Data-Error-Report CRITICALITY reject TYPE Ciphering-Data-Error-Report + PRESENCE conditional } , + ... +} + +Ciphering-Key-Data-Result-Extensions LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +END + +### 7.5.5 Information element definitions + +``` + +-- ***** +-- +-- Information Element Definitions +-- +-- ***** + +LCS-AP-IEs { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-IEs (2)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + + max-No-Of-Points, + max-Set, + max-GNSS-Set, + max-Add-Pos-Set, + max-Cipher-Set, + id-Additional-PositioningDataSet +FROM LCS-AP-Constants + + Criticality, + ProcedureCode, + TriggeringMessage, + ProtocolIE-ID +FROM LCS-AP-CommonDataTypes + + ProtocolExtensionContainer{}, + LCS-AP-PROTOCOL-EXTENSION +FROM LCS-AP-Containers; + +-- A + +APDU ::= OCTET STRING + +Accuracy-Fulfillment-Indicator ::= ENUMERATED { + requested-accuracy-fulfilled, + requested-accuracy-not-fulfilled, + ... +} + +Additional-PositioningDataSet ::= SEQUENCE (SIZE (1..max-Add-Pos-Set)) OF Additional- +PositioningMethodAndUsage + +Additional-PositioningMethodAndUsage ::= OCTET STRING (SIZE (1)) + +Altitude ::= INTEGER (0..65535) +-- The valid value for this IE is 0 to 32767. +-- Reception of value greater than 32767 shall be mapped to the value 32767. + +Altitude-And-Direction ::= SEQUENCE { + direction-Of-Altitude Direction-Of-Altitude, + altitude Altitude, + ... +} + +Angle ::= INTEGER (0..179) + +-- B + +Barometric-Pressure ::= INTEGER (30000..115000) + +Bearing ::= INTEGER (0..359) + +``` + +-- C + +C0 := BIT STRING (SIZE (1..128)) + +CellIdentity := BIT STRING (SIZE (28)) + +Cell-Portion-ID := INTEGER (0..255,..., 256..4095) + +Ciphering-Data := SEQUENCE(SIZE(1..max-Cipher-Set)) OF Ciphering-Data-Set + +Ciphering-Data-Ack := SEQUENCE(SIZE(1..max-Cipher-Set)) OF Ciphering-Set-ID + +Ciphering-Data-Error-Report := SEQUENCE(SIZE(1..max-Cipher-Set)) OF Ciphering-Data-Error-Report-Contents + +Ciphering-Data-Set := SEQUENCE { +    ciphering-Set-ID    Ciphering-Set-ID, +    ciphering-Key    Ciphering-Key, +    C0    C0, +    sib-Types    SIB-Types, +    validity-Start-Time    Validity-Start-Time, +    validity-Duration    Validity-Duration, +    tais-List    TAIs-List, +    ... +} + +Ciphering-Data-Error-Report-Contents := SEQUENCE { +    ciphering-Set-ID    Ciphering-Set-ID, +    storage-Outcome    Storage-Outcome, +    ... +} + +Ciphering-Set-ID := INTEGER (0..65535) + +Ciphering-Key := OCTET STRING (SIZE (16)) + +Civic-Address := OCTET STRING + +Confidence := INTEGER (0..100) + +Correlation-ID := OCTET STRING (SIZE (4)) + +Country := OCTET STRING + +-- D + +DegreesLatitude := INTEGER (0..8388607)    -- 23 bit field + +DegreesLongitude := INTEGER (-8388608..8388607)    -- 24 bit field + +Direction-Of-Altitude := ENUMERATED { +    height, +    depth +} + +-- E + +E-CGI := SEQUENCE { +    pLMNIdentity    PLMN-ID, +    cell-ID    CellIdentity, +    iE-Extensions    ProtocolExtensionContainer { { E-CGI-ExtIEs} } OPTIONAL, +    ... +} + +E-CGI-ExtIEs LCS-AP-PROTOCOL-EXTENSION := { +    ... +} + +Coverage-Level := ENUMERATED { +    extendedcoverage, +    ... +} + +Ellipsoid-Point-With-Uncertainty-Ellipse := SEQUENCE { +    geographical-Coordinates    Geographical-Coordinates, + +``` + uncertainty-Ellipse Uncertainty-Ellipse, + confidence Confidence, + iE-Extensions ProtocolExtensionContainer { { Ellipsoid-Point-With-Uncertainty-Ellipse-ExtIEs} + } OPTIONAL, + ...} + +Ellipsoid-Point-With-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Ellipsoid-Point-With-Altitude ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + altitude-And-Direction Altitude-And-Direction, + iE-Extensions ProtocolExtensionContainer { { Ellipsoid-Point-With-Altitude-ExtIEs} } OPTIONAL, + ...} + +Ellipsoid-Point-With-Altitude-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + altitude-And-Direction Altitude-And-Direction, + uncertainty-Ellipse Uncertainty-Ellipse, + uncertainty-Altitude Uncertainty-Altitude, + confidence Confidence, + iE-Extensions ProtocolExtensionContainer { { Ellipsoid-Point-With-Altitude-And-Uncertainty- +Ellipsoid-ExtIEs} } OPTIONAL, + ...} + +Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Ellipsoid-Arc ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + inner-Radius Inner-Radius, + uncertainty-Radius Uncertainty-Code, + offset-Angle Angle, + included-Angle Angle, + confidence Confidence, + iE-Extensions ProtocolExtensionContainer { { Ellipsoid-Arc-ExtIEs} } OPTIONAL, + ... +} + +Ellipsoid-Arc-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +ENB-ID ::= CHOICE { + macro-eNB-ID Macro-eNB-ID, + home-eNB-ID Home-eNB-ID, + ..., + short-macro-eNB-ID Short-Macro-eNB-ID, + long-macro-eNB-ID Long-Macro-eNB-ID +} + +E-SMLC-ID ::= INTEGER (0..255) + +-- F +-- G + +Geographical-Area ::= CHOICE { + point Point, + point-With-Uncertainty Point-With-Uncertainty, + ellipsoidPoint-With-Uncertainty-Ellipse Ellipsoid-Point-With-Uncertainty-Ellipse, + polygon Polygon, + ellipsoid-Point-With-Altitude Ellipsoid-Point-With-Altitude, + ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid Ellipsoid-Point-With-Altitude-And- +Uncertainty-Ellipsoid, + ellipsoid-Arc Ellipsoid-Arc, +} +``` + +``` +.... + high-Accuracy-Ellipsoid-Point-With-Uncertainty-Ellipse High-Accuracy-Ellipsoid-Point-With- + Uncertainty-Ellipse, + high-Accuracy-Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid High-Accuracy-Ellipsoid- + Point-With-Altitude-And-Uncertainty-Ellipsoid, + high-Accuracy-Ellipsoid-Point-With-Scalable-Uncertainty-Ellipse High-Accuracy-Ellipsoid-Point- + With-Scalable-Uncertainty-Ellipse, + high-Accuracy-Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid High-Accuracy- + Accuracy-Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid +} + +Geographical-Coordinates := SEQUENCE { + latitudeSign LatitudeSign, + degreesLatitude DegreesLatitude, + degreesLongitude DegreesLongitude, + iE-Extensions ProtocolExtensionContainer { {Geographical-Coordinates-ExtIEs} } OPTIONAL, + ... +} + +Geographical-Coordinates-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Global-eNB-ID := SEQUENCE { + pLMN-ID PLMN-ID, + eNB-ID ENB-ID +} + +GNSS-Positioning-Method-And-Usage ::= OCTET STRING (SIZE (1)) + +GNSS-Positioning-Data-Set ::= SEQUENCE (SIZE (1..max-GNSS-Set)) OF GNSS-Positioning-Method-And-Usage + +-- H + +High-Accuracy-Altitude ::= INTEGER (-64000..1280000) + +High-Accuracy-DegreesLatitude ::= INTEGER(-2147483648..2147483647) + +High-Accuracy-DegreesLongitude ::= INTEGER(-2147483648..2147483647) + +High-Accuracy-Ellipsoid-Point-With-Uncertainty-Ellipse ::= SEQUENCE { + high-Accuracy-Geographical-Coordinates High-Accuracy-Geographical-Coordinates, + high-Accuracy-Uncertainty-Ellipse High-Accuracy-Uncertainty-Ellipse, + confidence Confidence, + iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Ellipsoid-Point-With-Uncertainty- + Ellipse-ExtIEs} } OPTIONAL, + ... +} + +High-Accuracy-Ellipsoid-Point-With-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +High-Accuracy-Ellipsoid-Point-With-Scalable-Uncertainty-Ellipse ::= SEQUENCE { + high-Accuracy-Geographical-Coordinates High-Accuracy-Geographical-Coordinates, + high-Accuracy-Scalable-Uncertainty-Ellipse High-Accuracy-Scalable-Uncertainty-Ellipse, + confidence Confidence, + iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Ellipsoid-Point-With-Scalable- + Uncertainty-Ellipse-ExtIEs} } OPTIONAL, + ... +} + +High-Accuracy-Ellipsoid-Point-With-Scalable-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= +{ + ... +} + +High-Accuracy-Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid ::= SEQUENCE { + high-Accuracy-Geographical-Coordinates High-Accuracy-Geographical-Coordinates, + high-Accuracy-Altitude High-Accuracy-Altitude, + high-Accuracy-Uncertainty-Ellipse High-Accuracy-Uncertainty-Ellipse, + confidence Confidence, + high-Accuracy-Uncertainty-Altitude High-Accuracy-Uncertainty-Code, +} +``` + +``` + vertical-Confidence Confidence, + iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Ellipsoid-Point-With-Altitude-And- + Uncertainty-Ellipsoid-ExtIEs} } OPTIONAL, + ...} + +High-Accuracy-Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid-ExtIEs LCS-AP-PROTOCOL- +EXTENSION ::= { + ... +} + +High-Accuracy-Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid ::= SEQUENCE { + high-Accuracy-Geographical-Coordinates High-Accuracy-Geographical-Coordinates, + high-Accuracy-Altitude High-Accuracy-Altitude, + high-Accuracy-Scalable-Uncertainty-Ellipse High-Accuracy-Scalable-Uncertainty-Ellipse, + confidence Confidence, + high-Accuracy-Scalable-Uncertainty-Altitude High-Accuracy-Scalable-Uncertainty-Altitude, + vertical-Confidence Confidence, + iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Ellipsoid-Point-With-Altitude-And- + Scalable-Uncertainty-Ellipsoid-ExtIEs} } OPTIONAL, + ...} + +High-Accuracy-Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid-ExtIEs LCS-AP- +PROTOCOL-EXTENSION ::= { + ... +} + +High-Accuracy-Geographical-Coordinates ::= SEQUENCE { + high-Accuracy-DegreesLatitude High-Accuracy-DegreesLatitude, + high-Accuracy-DegreesLongitude High-Accuracy-DegreesLongitude, + iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Geographical-Coordinates-ExtIEs} } + OPTIONAL, + ... +} + +High-Accuracy-Geographical-Coordinates-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +High-Accuracy-Uncertainty-Code ::= INTEGER (0..255) + +High-Accuracy-Extended-Uncertainty-Code ::= INTEGER (0..255) + +High-Accuracy-Uncertainty-Ellipse ::= SEQUENCE { + high-Accuracy-Uncertainty-SemiMajor High-Accuracy-Uncertainty-Code, + high-Accuracy-Uncertainty-SemiMinor High-Accuracy-Uncertainty-Code, + orientation-Major-Axis INTEGER (0..179), + iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Uncertainty-Ellipse-ExtIEs} } + OPTIONAL, + ... +} + +High-Accuracy-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +High-Accuracy-Extended-Uncertainty-Ellipse ::= SEQUENCE { + high-Accuracy-Extended-Uncertainty-SemiMajor High-Accuracy-Extended-Uncertainty-Code, + high-Accuracy-Extended-Uncertainty-SemiMinor High-Accuracy-Extended-Uncertainty-Code, + orientation-Major-Axis INTEGER (0..179), + iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Extended-Uncertainty-Ellipse- + ExtIEs} } OPTIONAL, + ... +} + +High-Accuracy-Extended-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +High-Accuracy-Scalable-Uncertainty-Ellipse ::= CHOICE { + high-Accuracy-Uncertainty-Ellipse High-Accuracy-Uncertainty-Ellipse, + high-Accuracy-Extended-Uncertainty-Ellipse High-Accuracy-Extended-Uncertainty-Ellipse +} + +High-Accuracy-Scalable-Uncertainty-Altitude ::= CHOICE { + high-Accuracy-Uncertainty-Altitude High-Accuracy-Uncertainty-Code, +} +``` + +``` +high-Accuracy-Extended-Uncertainty-Altitude High-Accuracy-Extended-Uncertainty-Code +} + +Home-eNB-ID ::= BIT STRING (SIZE (28)) + +Horizontal-Accuracy ::= INTEGER (0..127) + +Horizontal-Speed-And-Bearing ::= SEQUENCE { + bearing INTEGER (0..359), + horizontal-Speed INTEGER (0..2047) +} + +Horizontal-Velocity ::= SEQUENCE { + horizontal-Speed-And-Bearing Horizontal-Speed-And-Bearing, + iE-Extensions ProtocolExtensionContainer { { Horizontal-Velocity-ExtIEs} } OPTIONAL, + ... +} + +Horizontal-Velocity-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Horizontal-With-Vertical-Velocity ::= SEQUENCE { + horizontal-Speed-And-Bearing Horizontal-Speed-And-Bearing, + vertical-Velocity Vertical-Velocity, + iE-Extensions ProtocolExtensionContainer { { Horizontal-With-Vertical-Velocity-ExtIEs} } + OPTIONAL, + ... +} + +Horizontal-With-Vertical-Velocity-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Horizontal-Velocity-With-Uncertainty ::= SEQUENCE { + horizontal-Speed-And-Bearing Horizontal-Speed-And-Bearing, + uncertainty-Speed INTEGER (0..255), + iE-Extensions ProtocolExtensionContainer { { Horizontal-Velocity-With-Uncertainty-ExtIEs} } + OPTIONAL, + ... +} + +Horizontal-Velocity-With-Uncertainty-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Horizontal-With-Vertical-Velocity-And-Uncertainty ::= SEQUENCE { + horizontal-Speed-And-Bearing Horizontal-Speed-And-Bearing, + vertical-Velocity Vertical-Velocity, + horizontal-Uncertainty-Speed INTEGER (0..255), + vertical-Uncertainty-Speed INTEGER (0..255), + iE-Extensions ProtocolExtensionContainer { { Horizontal-With-Vertical-Velocity-And- + Uncertainty-ExtIEs} } OPTIONAL, + ... +} + +Horizontal-With-Vertical-Velocity-And-Uncertainty-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- I + +IMSI ::= OCTET STRING (SIZE (3..8)) + +IMEI ::= OCTET STRING (SIZE (8)) + +Include-Velocity ::= ENUMERATED { + requested, + not-Requested, + ... +} +``` + +``` +Inner-Radius := INTEGER (0..65535) -- 16 bit field + +International-Area-Indication := ENUMERATED { + yes, + ... +} + +-- J +-- K +-- L + +LatitudeSign := ENUMERATED { + north, + south +} + +Location-Type := ENUMERATED { + geographic-Information, + assistance-Information, + ..., + last-known-location +} + +LCS-Cause := CHOICE { + radio-Network-Layer Radio-Network-Layer-Cause, + transport-Layer Transport-Layer-Cause, + protocol Protocol-Cause, + misc Misc-Cause +} + +LCS-Client-Type := ENUMERATED { + emergency-Services, + value-Added-Services, + pLMN-Operator-Services, + lawful-Intercept-Services, + pLMN-Operator-broadcast-Services, + pLMN-Operator-OM, + pLMN-Operator-Anonymous-Statistics, + pLMN-Operator-Target-MS-Service-Support, + ... +} + +LCS-Priority := OCTET STRING (SIZE (1)) + +LCS-QoS := SEQUENCE { + horizontal-Accuracy Horizontal-Accuracy OPTIONAL, + vertical-Requested Vertical-Requested OPTIONAL, + vertical-Accuracy Vertical-Accuracy OPTIONAL, + response-Time Response-Time OPTIONAL, + ... +} + +LCS-Service-Type-ID := INTEGER (0..127) + +Long-Macro-eNB-ID := BIT STRING (SIZE (21)) + +-- M + +Macro-eNB-ID := BIT STRING (SIZE (20)) + +Message-Identifier := BIT STRING (SIZE (16)) + +Misc-Cause := ENUMERATED { + processing-Overload, + hardware-Failure, + o-And-M-Intervention, + unspecified, + ..., + ciphering-key-data-lost +} + +MultipleAPDUs := SEQUENCE (SIZE (1.. 3)) OF APDU +``` + +``` +-- N + +Network-Element ::= CHOICE { + global-eNB-ID Global-eNB-ID, + e-SMLC-ID E-SMLC-ID +} + +-- O + +Orientation-Major-Axis ::= INTEGER (0..89) + +-- P + +Payload-Type ::= ENUMERATED { + lPP, + lPPa, + ... +} + +PLMN-ID ::= TBCD-STRING + +Point ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + iE-Extensions ProtocolExtensionContainer { {Point-ExtIEs} } OPTIONAL, + ... +} + +Point-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Point-With-Uncertainty ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + uncertainty-Code Uncertainty-Code, + iE-Extensions ProtocolExtensionContainer { {Point-With-Uncertainty-ExtIEs} } OPTIONAL, + ... +} + +Point-With-Uncertainty-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Polygon ::= SEQUENCE (SIZE (1..max-No-Of-Points)) OF Polygon-Point + +Polygon-Point ::= SEQUENCE { + geographical-Coordinates Geographical-Coordinates, + iE-Extensions ProtocolExtensionContainer { {Polygon-Point-ExtIEs} } OPTIONAL, + ... +} + +Polygon-Point-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Positioning-Data ::= SEQUENCE { + positioning-Data-Set Positioning-Data-Set OPTIONAL, + gNSS-Positioning-Data-Set GNSS-Positioning-Data-Set OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Positioning-Data-ExtIEs} } OPTIONAL, + ... +} + +Positioning-Data-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= { + { ID id-Additional-PositioningDataSet CRITICALITY ignore EXTENSION Additional- + PositioningDataSet PRESENCE optional }, + ... +} + +Positioning-DataSet ::= SEQUENCE (SIZE (1..max-Set)) OF Positioning-Method-And-Usage + +Positioning-Method-And-Usage ::= OCTET STRING (SIZE (1)) + +Protocol-Cause ::= ENUMERATED { + transfer-Syntax-Error, + abstract-Syntax-Error-Reject, +} +``` + +``` +abstract-Syntax-Error-Ignore-And-Notify, +message-Not-Compatible-With-Receiver-State, +semantic-Error, +unspecified, +abstract-Syntax-Error, +... +} + +-- Q +-- R + +Radio-Network-Layer-Cause ::= ENUMERATED { +unspecified, +... +} + +RAT-Type ::= ENUMERATED { +lte-wb, +nb-iot, +..., +lte-m +} + +Response-Time ::= ENUMERATED { +low-Delay(0), +delay-Tolerant(1), +... +} + +Return-Error-Type ::= ENUMERATED { +yes, +no +} + +Return-Error-Cause ::= ENUMERATED { +system-Failure, +protocol-Error, +destination-Unknown, +destination-Unreachable, +congestion, +... +} + +-- S + +Short-Macro-eNB-ID ::= BIT STRING (SIZE (18)) + +SIB-Types ::= OCTET STRING (SIZE (4)) + +Storage-Outcome ::= ENUMERATED { +successful, +failed +} + +-- T + +TAIs-List ::= OCTET STRING (SIZE (7..97)) + +TBCD-STRING ::= OCTET STRING (SIZE (3)) + +Transport-Layer-Cause ::= ENUMERATED { +transport-Resource-Unavailable, +unspecified, +... +} + +-- U + +Uncertainty-Altitude ::= INTEGER (0..127) + +Uncertainty-Code ::= INTEGER (0..127) + +Uncertainty-Ellipse ::= SEQUENCE { +uncertainty-SemiMajor Uncertainty-Code, +uncertainty-SemiMinor Uncertainty-Code, +orientation-Major-Axis Orientation-Major-Axis +} +``` + +``` + +UE-Positioning-Capability ::= SEQUENCE { + lpp BOOLEAN, + ... +} + +UE-Country-Determination-Indication ::= ENUMERATED { + required, + not-required, + ... +} + +UE-Area-Indication ::= SEQUENCE { + country Country, + international-area-indication International-Area-Indication +} + +-- V + +Validity-Duration ::= INTEGER (0..65535) + +Validity-Start-Time ::= OCTET STRING (SIZE (4)) + +Velocity-Estimate ::= CHOICE { + horizontal-Velocity Horizontal-Velocity, + horizontal-With-Vertical-Velocity Horizontal-With-Vertical-Velocity, + horizontal-Velocity-With-Uncertainty Horizontal-Velocity-With-Uncertainty, + horizontal-With-Vertical-Velocity-And-Uncertainty Horizontal-With-Vertical-Velocity-And- +Uncertainty, + ... +} + +Vertical-Requested ::= ENUMERATED { + vertical-coordinate-Is-Not-Requested(0), + vertical-coordinate-Is-Requested(1) +} + +Vertical-Accuracy ::= INTEGER (0..127) + +Vertical-Velocity ::= SEQUENCE { + vertical-Speed INTEGER (0..255), + vertical-Speed-Direction Vertical-Speed-Direction +} + +Vertical-Speed-Direction ::= ENUMERATED { + upward, + downward +} + +-- W +-- X +-- Y + +END + +``` + +### 7.5.6 Common definitions + +``` + +-- ****************************************************************************** +-- +-- Common definitions +-- +-- ****************************************************************************** + +LCS-AP-CommonDataTypes { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-CommonDataTypes (3)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +Criticality ::= ENUMERATED { reject, ignore, notify } + +Presence ::= ENUMERATED { optional, conditional, mandatory } + +ProcedureCode ::= INTEGER (0..255) + +``` + +``` + +ProtocolExtensionID ::= INTEGER (0..65535) + +ProtocolIE-ID ::= INTEGER (0..65535) + +TriggeringMessage ::= ENUMERATED {initiating-message, successful-outcome, unsuccessful-outcome, +outcome} + +END + +``` + +### 7.5.7 Constant definitions + +``` + +-- **************************************************************************** +-- +-- Constant definitions +-- +-- **************************************************************************** + +LCS-AP-Constants { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-Constants (4)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- **************************************************************************** +-- +-- Elementary Procedures +-- +-- **************************************************************************** + +id-Location-Service-Request INTEGER ::= 0 +id-Connection-Oriented-Information-Transfer INTEGER ::= 1 +id-Connectionless-Information-Transfer INTEGER ::= 2 +id-Location-Abort INTEGER ::= 3 +id-Reset INTEGER ::= 4 +id-Ciphering-Key-Data-Delivery INTEGER ::= 5 + +-- **************************************************************************** +-- +-- IEs +-- +-- **************************************************************************** + +id-Accuracy-Fulfillment-Indicator INTEGER ::= 0 +id-APDU INTEGER ::= 1 +id-Correlation-ID INTEGER ::= 2 +id-Destination-ID INTEGER ::= 3 +id-E-UTRAN-Cell-Identifier INTEGER ::= 4 +id-Include-Velocity INTEGER ::= 5 +id-IMEI INTEGER ::= 6 +id-IMSI INTEGER ::= 7 +id-LCS-Client-Type INTEGER ::= 8 +id-LCS-Priority INTEGER ::= 9 +id-LCS-QOS INTEGER ::= 10 +id-LCS-Cause INTEGER ::= 11 +id-Location-Estimate INTEGER ::= 12 +id-Location-Type INTEGER ::= 13 +id-MultipleAPDUs INTEGER ::= 14 +id-Payload-Type INTEGER ::= 15 +id-Positioning-Data INTEGER ::= 16 +id-Return-Error-Request INTEGER ::= 17 +id-Return-Error-Cause INTEGER ::= 18 +id-Source-Identity INTEGER ::= 19 +id-UE-Positioning-Capability INTEGER ::= 20 +id-Velocity-Estimate INTEGER ::= 21 +id-LCS-Service-Type-ID INTEGER ::= 22 +id-Cell-Portion-ID INTEGER ::= 23 +id-Civic-Address INTEGER ::= 24 +id-Barometric-Pressure INTEGER ::= 25 +id-Additional-PositioningDataSet INTEGER ::= 26 +id-RAT-Type INTEGER ::= 27 + +``` + +``` + +id-Ciphering-Data INTEGER ::= 28 +id-Ciphering-Data-Ack INTEGER ::= 29 +id-Ciphering-Data-Error-Report INTEGER ::= 30 +id-Coverage-Level INTEGER ::= 31 +id-UE-Country-Determination-Indication INTEGER ::= 32 +id-UE-Area-Indication INTEGER ::= 33 + +-- ************************************************************** +-- +-- Extension constants +-- +-- ************************************************************** + +-- ************************************************************** +-- +-- Lists +-- +-- ************************************************************** + +max-No-Of-Points INTEGER ::= 15 +max-Set INTEGER ::= 9 +max-GNSS-Set INTEGER ::= 9 +max-Add-Pos-Set INTEGER ::= 8 +max-Cipher-Set INTEGER ::= 16 + +maxProtocolExtensions INTEGER ::= 65535 +maxProtocolIEs INTEGER ::= 65535 + +END + +``` + +### 7.5.8 Container Definitions + +``` + +-- ************************************************************** +-- +-- Container definitions +-- +-- ************************************************************** + +LCS-AP-Containers { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-Containers (5)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ************************************************************** +-- +-- IE parameter types from other modules. +-- +-- ************************************************************** + +IMPORTS + Criticality, + Presence, + ProtocolExtensionID, + ProtocolIE-ID +FROM LCS-AP-CommonDataTypes + + maxProtocolExtensions, + maxProtocolIEs +FROM LCS-AP-Constants; + +-- ************************************************************** +-- +-- Class Definition for Protocol IEs +-- +-- ************************************************************** + +LCS-AP-PROTOCOL-IES ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality DEFAULT ignore, + +``` + +``` + + &Value, + &presence Presence + } + WITH SYNTAX { + ID &id + CRITICALITY &criticality + TYPE &Value + PRESENCE &presence + } + + -- ***** + -- + -- Class Definition for Protocol Extensions + -- + -- ***** + + LCS-AP-PROTOCOL-EXTENSION ::= CLASS { + &id ProtocolExtensionID UNIQUE, + &criticality Criticality DEFAULT ignore, + &Extension, + &presence Presence + } + WITH SYNTAX { + ID &id + CRITICALITY &criticality + EXTENSION &Extension + PRESENCE &presence + } + + -- ***** + -- + -- Container for Protocol IEs + -- + -- ***** + + ProtocolIE-Container {LCS-AP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + + ProtocolIE-Field {LCS-AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id LCS-AP-PROTOCOL-IES.&id {{IEsSetParam}}, + criticality LCS-AP-PROTOCOL-IES.&criticality {{IEsSetParam}{@id}}, + value LCS-AP-PROTOCOL-IES.&Value {{IEsSetParam}{@id}} + } + + -- ***** + -- + -- Container Lists for Protocol IE Containers + -- + -- ***** + + ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, LCS-AP-PROTOCOL-IES : + IEsSetParam} ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-Container {{IEsSetParam}} + + -- ***** + -- + -- Container for Protocol Extensions + -- + -- ***** + + ProtocolExtensionContainer {LCS-AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + ProtocolExtensionField {{ExtensionSetParam}} + + ProtocolExtensionField {LCS-AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { + id LCS-AP-PROTOCOL-EXTENSION.&id {{ExtensionSetParam}}, + criticality LCS-AP-PROTOCOL-EXTENSION.&criticality {{ExtensionSetParam}{@id}}, + extensionValue LCS-AP-PROTOCOL-EXTENSION.&Extension {{ExtensionSetParam}{@id}} + } + +END + +``` + +### 7.5.9 Message transfer syntax + +LCS-AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ITU-T Recommendation X.691 [12]. + +## 7.6 Handling of unknown, unforeseen and erroneous protocol data + +Clause 10 of TS 36.413 [7] is applicable for the purposes of the present document. + +# 8 LCS-AP Timers + +## 8.1 General + +The description of timers in the following tables should be considered a brief summary. + +## 8.2 Timers of LCS-AP + +**Table 8.2.1: LCS-AP timers** + +| TIMER NUM. | TIMER VALUE | CAUSE OF START | NORMAL STOP | ON EXPIRY | +|-------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------|-----------------------------------------------|----------------------------------------------------------------------------------------| +| T3x01 | This value can be operator configurable, based on the received QoS response time. | A Location Request procedure started in the MME. | Location Response message is received | MME shall send Abort message to E-SMLC and return error to the requesting entity | +| T3x02 | 3 seconds | A Reset message is sent | Reset Acknowledge message is received | Retransmission of the Reset message | +| T3x03 | This value can be operator configurable | A Ciphering Keys Delivery procedure started in the E-SMLC | Ciphering Key Data Result message is received | E-SMLC shall abort the procedure and release any resources allocated for the procedure | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29176/raw.md b/marked/Rel-18/29_series/29176/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..686cd335bf6f8f88811f126a182c3d9864a6de5e --- /dev/null +++ b/marked/Rel-18/29_series/29176/raw.md @@ -0,0 +1,1328 @@ + + +# 3GPP TS 29.176 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia Subsystems (IMS); Media Function (MF) Services; Stage 3 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis + +Valbonne - FRANCE + +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members + +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 Overview..... | 8 | +| 5 Services offered by the MF..... | 9 | +| 5.1 Introduction ..... | 9 | +| 5.2 Nmf_MediaResourceManagement (MRM) Service ..... | 9 | +| 5.2.1 Service Description ..... | 9 | +| 5.2.2 Service Operations..... | 9 | +| 5.2.2.1 Introduction..... | 9 | +| 5.2.2.2 Nmf_MRM_Create Service Operation..... | 9 | +| 5.2.2.2.1 General ..... | 9 | +| 5.2.2.2.2 Creation of a new media context..... | 10 | +| 5.2.2.3 Nmf_MRM_Update Service Operation..... | 11 | +| 5.2.2.3.1 General ..... | 11 | +| 5.2.2.3.2 Updating an existing media context..... | 11 | +| 5.2.2.4 Nmf_MRM_Delete Service Operation..... | 12 | +| 5.2.2.4.1 General ..... | 12 | +| 5.2.2.4.2 Deleting an existing media context..... | 12 | +| 6 API Definitions ..... | 13 | +| 6.1 Nmf_MRM Service API ..... | 13 | +| 6.1.1 Introduction ..... | 13 | +| 6.1.2 Usage of HTTP..... | 13 | +| 6.1.2.1 General..... | 13 | +| 6.1.2.2 HTTP standard headers..... | 13 | +| 6.1.2.2.1 General ..... | 13 | +| 6.1.2.2.2 Content type ..... | 13 | +| 6.1.2.3 HTTP custom headers..... | 13 | +| 6.1.3 Resources..... | 14 | +| 6.1.3.1 Overview..... | 14 | +| 6.1.3.2 Resource: Contexts Collection..... | 14 | +| 6.1.3.2.1 Description ..... | 14 | +| 6.1.3.2.2 Resource Definition..... | 14 | +| 6.1.3.2.3 Resource Standard Methods..... | 15 | +| 6.1.3.2.4 Resource Custom Operations..... | 16 | +| 6.1.3.3 Resource: Individual Context ..... | 16 | +| 6.1.3.3.1 Description ..... | 16 | +| 6.1.3.3.2 Resource Definition..... | 16 | +| 6.1.3.3.3 Resource Standard Methods..... | 16 | +| 6.1.3.3.4 Resource Custom Operations..... | 18 | +| 6.1.4 Custom Operations without associated resources ..... | 18 | +| 6.1.5 Notifications ..... | 19 | +| 6.1.6 Data Model ..... | 19 | +| 6.1.6.1 General..... | 19 | +| 6.1.6.2 Structured data types..... | 19 | +| 6.1.6.2.1 Introduction ..... | 19 | +| 6.1.6.2.2 Type: MediaContext..... | 20 | +| 6.1.6.2.3 Type: TerminationInfo ..... | 20 | +| 6.1.6.2.4 Type: MediaInfo..... | 21 | + +| | | | +|-------------------------------|-----------------------------------------|-----------| +| 6.1.6.2.5 | Type: DcMedia..... | 22 | +| 6.1.6.2.6 | Type: ArMedia..... | 24 | +| 6.1.6.3 | Simple data types and enumerations..... | 24 | +| 6.1.6.3.1 | Introduction ..... | 24 | +| 6.1.6.3.2 | Simple data types ..... | 24 | +| 6.1.7 | Error Handling ..... | 24 | +| 6.1.7.1 | General ..... | 24 | +| 6.1.7.2 | Protocol Errors ..... | 24 | +| 6.1.7.3 | Application Errors..... | 25 | +| 6.1.8 | Feature negotiation ..... | 25 | +| 6.1.9 | Security ..... | 25 | +| 6.1.10 | HTTP redirection..... | 25 | +| Annex A (normative): | OpenAPI specification ..... | 26 | +| A.1 | General..... | 26 | +| A.2 | Ndcmf_MRM API ..... | 26 | +| Annex B (informative): | Change history..... | 31 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document specifies the stage 3 protocol and data model for the Nmf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the Media Function (MF). + +The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]. + +The IP Multimedia Subsystem (IMS) Data Channel (DC) architecture and procedures are specified in annex AC of 3GPP TS 23.228 [14]. + +The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". +- [6] OpenAPI: "OpenAPI Specification Version 3.0.0", . +- [7] 3GPP TR 21.900: "Technical Specification Group working methods". +- [8] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". +- [10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3". +- [11] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)". +- [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [13] IETF RFC 7807: "Problem Details for HTTP APIs". +- [14] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [15] IETF RFC 6902: " JavaScript Object Notation (JSON) Patch". +- [16] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +*Definition format (Normal)* + +****: . + +**example:** text used to clarify abstract rules by applying them literally. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-----|---------------------------------------| +| DC2 | Reference point between MF and IMS AS | +|-----|---------------------------------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------|--------------------------------------------| +| AR | Augmented Reality | +| DC | Data Channel | +| MF | Media Function | +| IMS AS | IP Multimedia Subsystem Application Server | + +# 4 Overview + +Within the IMS DC architecture, the MF offers services to the IMS AS via the Nmf service based interface (see 3GPP TS 23.228 [14]). + +Figure 4.1-1 provides the reference model (in service-based interface representation and in reference point representation), with focus on the MF services. + +![Diagram of the reference model showing the IMS AS connected to the MF via the DC2 reference point and the Nmf service-based interface.](98a45dd7d474e067b7533cc966c11e95_img.jpg) + +The diagram illustrates the reference model for the Media Function (MF). On the left, a white rectangular box is labeled 'IMS AS'. A horizontal line connects this box to a green rectangular box on the right, which is labeled 'MF'. The connection line is labeled 'DC2' near the IMS AS and 'Nmf' near the MF. The 'Nmf' label is positioned next to a small circle on the left side of the MF box, indicating a service-based interface. + +Diagram of the reference model showing the IMS AS connected to the MF via the DC2 reference point and the Nmf service-based interface. + +**Figure 4.1-1: Reference model – MF** + +DC2 is the reference point between MF and IMS AS. + +# 5 Services offered by the MF + +## 5.1 Introduction + +The MF offers the following services via the Nmf interface: + +- Nmf\_MediaResourceManagement (MRM) Service + +Table 5.1-1 summarizes the corresponding APIs defined for this specification. + +**Table 5.1-1: API Descriptions** + +| Service Name | Clause | Description | OpenAPI Specification File | apiName | Annex | +|--------------|--------|---------------------------------------|----------------------------|---------|-------| +| Nmf_MRM | 6.1 | Nmf Media Resource Management Service | TS29176_Nmf_MRM.yaml | nmf-mrm | A.2 | + +## 5.2 Nmf\_MediaResourceManagement (MRM) Service + +### 5.2.1 Service Description + +The Nmf\_MRM service as defined in 3GPP TS 23.228 [14] is provided by the Media Function (MF). This service enables the consumer to create, update and delete media resources. Data Channel (DC) and Augmented Reality (AR) are two capabilities supported by MF. + +The media resource represents a media context including one or multiple media terminations. A media termination includes media resources for one or multiple medias on the Mb interface. When a media pass through the MF, there is one termination for the input stream and one termination for the output stream. + +### 5.2.2 Service Operations + +#### 5.2.2.1 Introduction + +The Nmf\_MRM service supports the following service operation. + +**Table 5.2.2.1-1: Service operations supported by the Nmf\_MRM service** + +| Service Operations | Description | Operation Semantics | Example Consumer(s) | +|--------------------|--------------------------------------------------------------------------------------|---------------------|---------------------| +| Create | Create a new media context including one or multiple media terminations. | Request/Response | IMS AS | +| Update | Update the one or multiple existing media resources within a specific media context. | Request/Response | IMS AS | +| Delete | Delete a specific media context including all the existing terminations and medias. | Request/Response | IMS AS | + +#### 5.2.2.2 Nmf\_MRM\_Create Service Operation + +##### 5.2.2.2.1 General + +The Nmf\_MRM\_Create service operation is used by an NF service consumer to create a media context including one or multiple terminations and reserve media resources for anchoring one or multiple medias of Mb interface in each + +termination on MF. The consumer NF may also include application function (e.g. DCSF, DC AS) specification information requested by the application layer to be applied on the media by the MF. + +##### 5.2.2.2.2 Creation of a new media context + +The NF service consumer shall request a new context by using HTTP method POST with "{apiRoot}/nmf//contexts" as resource URI representing the "Contexts Collection", see clause 6.1.3.2. + +![Sequence diagram showing the creation of a media context. The NF Service Consumer sends a POST request to the MF. The MF responds with either a 201 Created (MediaContext) or a 4xx/5xx (ProblemDetails) or 3xx response.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant MF + Note left of NF Service Consumer: POST ../contexts (MediaContext) + NF Service Consumer->>MF: 1. POST ../contexts (MediaContext) + Note right of MF: -2a. 201 Created (MediaContext) + MF-->>NF Service Consumer: -2a. 201 Created (MediaContext) + Note right of MF: -2b. 4xx/5xx (ProblemDetails) or 3xx + MF-->>NF Service Consumer: -2b. 4xx/5xx (ProblemDetails) or 3xx + +``` + +Sequence diagram showing the creation of a media context. The NF Service Consumer sends a POST request to the MF. The MF responds with either a 201 Created (MediaContext) or a 4xx/5xx (ProblemDetails) or 3xx response. + +Figure 5.2.2.2.2-1 Creation of a media context + +1. The NF Service Consumer shall send a POST request to create an "Individual Context" resource in the MF. The payload body of the POST request shall contain a representation of the individual context resource to be created. + +The NF service consumer shall include list of termination descriptors in the HTTP message body. Each termination descriptor shall include list of media stream descriptors. Each media stream descriptor shall include: + +- Media ID, i.e. a unique identity of the media stream within the media context instance; +- Remote Mb specifications, i.e. the media stream IP address and port allocated at the remote endpoint, i.e. remote UE, remote network. +- Media resource description, which includes + - 1) Media resource type, e.g. DC, AR. + - 2) If media resource type is set to "DC", the DC media specification shall be included. The DC media specification shall include: + - a) Data Channel Mapping and Configuration information when originating/terminating data channel media flows on the Mb interface. It shall include the SCTP stream Id for the DC, and may include subprotocol, order, maxRetry, maxTime and priority may be included. + - b) Maximum Message Size, which represents the maximum size to be expected. + - c) Data Channel Port, which represents the port of SCTP port for the Data Channel. + - d) Security Setup, which identifies the security setup of the DTLS connection. + - e) Security Certificate Fingerprint, which identifies the security certificate fingerprint. + - f) Security Transport Identity, which identifies transport layer identity. + +For establishing bootstrap data channel or P2A/A2P application data channel, the following parameters shall be included: + +- a) media proxy configuration applicable to the media flow; +- b) remote MDC1/MDC2 media specification information to be applied on the media by the MF; +- c) Replacement HTTP URL for each streamId allocated by the application layer representing the application list (e.g. graphical user interface) offered to the IMS subscriber via the MDC1 interface. + +3) If media resource type is set to "AR", the AR media resource description shall be included, which includes: + +a) Media processing specification. + +2a. Upon the reception of the HTTP POST request, if the request is accepted and no error occur, the MF shall: + +- create a new media context; +- assign a media contextId; +- assign a terminationId for each termination descriptor; and +- reserve media resources for each mediaId. + +The MF shall include a HTTP Location header to provide the location of a newly created resource (MediaContext) together with the status code 201 indicating the requested resource is created in the response message. + +2b. On failure, one of the HTTP status code listed in Table 6.1.3.2.3.1-3 shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.3.2.3.1-3. + +On redirection, the MF shall include 3xx status code, which shall contain a Location header with an URI pointing to the endpoint to another MF (service) instance. + +#### 5.2.2.3 Nmf\_MRM\_Update Service Operation + +##### 5.2.2.3.1 General + +The Nmf\_MRM\_Update service operation is used by an NF service consumer to update one or multiple existing media resources within a specific media context on MF. Terminations and/or Medias can be added, modified, or deleted within an Update request. + +##### 5.2.2.3.2 Updating an existing media context + +The NF Service Consumer shall modify the context by using HTTP method PATCH with the URI "{apiRoot}/nmf//contexts/{contextId}" as resource URI representing the "Individual Context ", see clause 6.1.3.3. + +![Sequence diagram showing the interaction between an NF Service Consumer and an MF for updating a media context. The consumer sends a PATCH request to the MF. The MF responds with one of three options: 2a. 204 No Content, 2b. 200 OK (MediaContext), or 2c. 4xx/5xx (ProblemDetails) or 3xx.](ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant MF + Note left of NF Service Consumer: Update a media context + NF Service Consumer->>MF: 1. PATCH .../contexts/{contextId} (PatchData) + MF-->>NF Service Consumer: 2a. 204 No Content + MF-->>NF Service Consumer: 2b. 200 OK (MediaContext) + MF-->>NF Service Consumer: 2c. 4xx/5xx (ProblemDetails) or 3xx + +``` + +Sequence diagram showing the interaction between an NF Service Consumer and an MF for updating a media context. The consumer sends a PATCH request to the MF. The MF responds with one of three options: 2a. 204 No Content, 2b. 200 OK (MediaContext), or 2c. 4xx/5xx (ProblemDetails) or 3xx. + +Figure 5.2.2.3.2-1 Update a media context + +1. The NF Service Consumer shall send a PATCH request to modify a context resource in the MF. The modification may be for adding, updating or deleting terminations of the existing media context. + +For adding, removing or updating a termination in an existing MediaContext, the payload body of the PATCH request shall contain an "add", "remove" or "replace" PATCH operation respectively, with one item of the attribute "terminations" of the MediaContext. + +- 2a. On success, if the change is to delete the existing termination and MF accepts the request change, the MF shall return the status code 204 No Content. +- 2b. On success, if the change is to add a new termination or to update the existing termination and DCMF accepts the request change, the MF shall return the status code 200 OK. The response shall contain the new resource representation of the resource Individual Context, which includes the added and modified resource or its sub-resource. +- 2c On failure, one of the HTTP status code listed in Table 6.1.3.3.3.1-3 indicating the error shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.3.3.3.1-3. + +On redirection, the MF shall return 3xx status code, which shall contain a Location header with an URI pointing to the endpoint to another MF (service) instance. + +#### 5.2.2.4 Nmf\_MRM\_Delete Service Operation + +##### 5.2.2.4.1 General + +The Nmf\_MRM\_Delete service operation is used by an NF service consumer to delete an existing media context including all existing terminations and medias on MF previously created by itself. + +##### 5.2.2.4.2 Deleting an existing media context + +The NF Service Consumer shall delete an existing context by using HTTP method DELETE with the URI "{apiRoot}/nmf//contexts/{contextId}" as resource URI representing the "Individual Context ", see clause 6.1.3.3. + +![Sequence diagram showing the interaction between an NF Service Consumer and an MF for deleting a media context. The consumer sends a DELETE request to the MF. The MF responds with either a 204 No Content (success) or a 4xx/5xx (ProblemDetails) or 3xx (redirection) response.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +``` + +sequenceDiagram + participant NF Service Consumer + participant MF + Note left of NF Service Consumer: 1. DELETE .../contexts/{contextId} + NF Service Consumer->>MF: 1. DELETE .../contexts/{contextId} + Note right of MF: -2a. 204 No Content + MF-->>NF Service Consumer: -2a. 204 No Content + Note right of MF: 2b. 4xx/5xx (ProblemDetails) or 3xx + MF-->>NF Service Consumer: 2b. 4xx/5xx (ProblemDetails) or 3xx + +``` + +Sequence diagram showing the interaction between an NF Service Consumer and an MF for deleting a media context. The consumer sends a DELETE request to the MF. The MF responds with either a 204 No Content (success) or a 4xx/5xx (ProblemDetails) or 3xx (redirection) response. + +Figure 5.2.2.4.2-1 Delete a media context + +- 1. The NF Service Consumer shall send a DELETE request to delete an existing context resource in the MF. +- 2a. On success, the request is accepted, the MF shall reply with the status code 204 No Content indicating the resource identified by context ID is successfully deleted in the response message. +- 2b. On failure, one of the HTTP status code listed in Table 6.1.3.3.3.2-3 indicating the error shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.3.3.3.2-3. + +On redirection, the MF shall return 3xx status code, which shall contain a Location header with an URI pointing to the endpoint to another MF (service) instance. + +# 6 API Definitions + +## 6.1 Nmf\_MRM Service API + +### 6.1.1 Introduction + +The Nmf\_MRM service shall use the Ndcmf\_MRM API. + +The API URI of the Nmf\_MRM API shall be: + +**{apiRoot}** + +The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.: + +**{apiRoot}** + +with the following components: + +- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5]. +- The shall be " nmf\_mrm". +- The shall be "v1". +- The shall be set as described in clause 6.1.3. + +### 6.1.2 Usage of HTTP + +#### 6.1.2.1 General + +HTTP/2, IETF RFC 7540 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4]. + +HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4]. + +The OpenAPI [6] specification of HTTP messages and content bodies for the Nmf\_MRM API is contained in Annex A. + +#### 6.1.2.2 HTTP standard headers + +##### 6.1.2.2.1 General + +See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers. + +##### 6.1.2.2.2 Content type + +JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json". + +"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 7807 [13]. + +The use of JSON Patch (IETF RFC 6902 [15]) format in a HTTP request body shall be signaled by the content type "application/json-patch+json". + +#### 6.1.2.3 HTTP custom headers + +The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be supported, and the optional HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4] may be supported. + +### 6.1.3 Resources + +#### 6.1.3.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 6.1.3.1-1 depicts the resource URIs structure for the Nmf\_MRM API. + +![Diagram showing the resource URI structure for the Nmf_MRM API. The root is {apiRoot}/nmf-mrm/. It branches to /contexts, which then branches to /{contextId}.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +``` + +graph TD + Root["{apiRoot}/nmf-mrm/"] --> Contexts["/contexts"] + Contexts --> ContextId["/{contextId}"] + +``` + +Diagram showing the resource URI structure for the Nmf\_MRM API. The root is {apiRoot}/nmf-mrm/. It branches to /contexts, which then branches to /{contextId}. + +**Figure 6.1.3.1-1: Resource URI structure of the Nmf\_MRM API** + +Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 6.1.3.1-1: Resources and methods overview** + +| Resource purpose/name | Resource URI (relative path after API URI) | HTTP method or custom operation | Description (service operation) | +|-----------------------|--------------------------------------------|---------------------------------|----------------------------------------------------------------------------| +| Contexts Collection | /contexts | POST | Creates a new Individual Context resource. | +| Individual Context | /contexts/{contextId} | PATCH | Updates an existing Individual Context resource identified by {contextId} | +| | | DELETE | Deletes an existing Individual Context resource identified by {contextId}. | + +#### 6.1.3.2 Resource: Contexts Collection + +##### 6.1.3.2.1 Description + +The Contexts Collection resource represents a collection of contexts created by NF service consumers of Nmf\_MRM service at a given MF. The resource is modelled as Collection resource archetype (see clause C.2 of 3GPP TS 29.501 [2]). + +##### 6.1.3.2.2 Resource Definition + +Resource URI: {apiRoot}/ nmf\_mrm//contexts + +This resource shall support the resource URI variables defined in table 6.1.3.2.2-1. + +**Table 6.1.3.2.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|---------|-----------|------------------| +| apiRoot | string | See clause 6.1.1 | + +##### 6.1.3.2.3 Resource Standard Methods + +###### 6.1.3.2.3.1 POST + +This method shall support the URI query parameters specified in table 6.1.3.2.3.1-1. + +**Table 6.1.3.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 6.1.3.2.3.1-2 and the response data structures and response codes specified in table 6.1.3.2.3.1-3. + +**Table 6.1.3.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|--------------|---|-------------|-------------------------------------------| +| MediaContext | M | 1 | Creates a new Individual Context resource | + +**Table 6.1.3.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|---------------------------|----------------------------------------------------------------------------------------------------------------------| +| MediaContext | M | 1 | 201
Created | The creation of an Individual Media Context resource is confirmed and a representation of that resource is returned. | +| RedirectResponse | O | 0..1 | 307
Temporary Redirect | Temporary redirection. (NOTE 2) | +| RedirectResponse | O | 0..1 | 308
Permanent Redirect | Permanent redirection. (NOTE 2) | + +NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. +NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +**Table 6.1.3.2.3.1-4: Headers supported by the 201 response code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure: {apiRoot}/nfmf-mrm//contexts/{contextId}. | + +**Table 6.1.3.2.3.1-5: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative MF (service) instance.
Or the same URI, if a request is redirected to the same target resource via a different SCP. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target MF instance ID towards which the request is redirected. | + +**Table 6.1.3.2.3.1-6: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative MF (service) instance.
Or the same URI, if a request is redirected to the same target resource via a different SCP. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target MF instance ID towards which the request is redirected. | + +##### 6.1.3.2.4 Resource Custom Operations + +None in the release of this specification. + +#### 6.1.3.3 Resource: Individual Context + +##### 6.1.3.3.1 Description + +The Individual Context resource represents an individual context created by the NF service consumers of Nmf\_MRM service at a given MF. This resource is modelled as the Document resource archetype (see clause C.1 of 3GPP TS 29.501 [2]). + +##### 6.1.3.3.2 Resource Definition + +Resource URI: {apiRoot}/nmf\_mrm//contexts/{contextId} + +The shall be set as described in clause 6.3.1. + +This resource shall support the resource URI variables defined in table 6.1.3.3.2-1. + +**Table 6.1.3.3.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|-----------|-----------|----------------------------------------------------------| +| apiRoot | string | See clause 6.1.1 | +| contextId | string | Identifies an individual context to the Nmf_MRM service. | + +##### 6.1.3.3.3 Resource Standard Methods + +###### 6.1.3.3.3.1 PATCH + +This method shall support the URI query parameters specified in table 6.1.3.3.3.1-1. + +**Table 6.1.3.3.3.1-1: URI query parameters supported by the PATCH method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 6.1.3.3.3.1-2 and the response data structures and response codes specified in table 6.1.3.3.3.1-3. + +**Table 6.1.3.3.3.1-2: Data structures supported by the PATCH Request Body on this resource** + +| Data type | P | Cardinality | Description | +|------------------|---|-------------|---------------------------------------------------------------------------| +| array(PatchItem) | M | 1..N | Document describes the modification(s) to an Individual Context resource. | + +**Table 6.1.3.3.3.1-3: Data structures supported by the PATCH Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MediaContext | M | 1..N | 200 OK | Represents a successful update on the media context. | +| n/a | | | 204 No Content | | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection. (NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection. (NOTE 2) | +| ProblemDetails | O | 0..1 | 403 Forbidden | Indicates the modification of media context has failed due to application error.

The "cause" attribute may be used to indicate one of the following application errors:
- MEDIA_ID_CONFLICT
- MEDIA_CONNECTION_CHANGED | +| ProblemDetails | O | 0..1 | 404 Not Found | Indicates the modification of media context has failed due to application error.

The "cause" attribute may be used to indicate one of the following application errors:
- CONTEXT_NOT_FOUND | + +NOTE 1: The mandatory HTTP error status code for the PATCH method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. +NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +**Table 6.1.3.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative MF (service) instance.
Or the same URI, if a request is redirected to the same target resource via a different SCP. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target MF instance ID towards which the request is redirected. | + +**Table 6.1.3.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative MF (service) instance.
Or the same URI, if a request is redirected to the same target resource via a different SCP. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target MF instance ID towards which the request is redirected. | + +###### 6.1.3.3.3.2 DELETE + +This method shall support the URI query parameters specified in table 6.1.3.3.3.2-1. + +**Table 6.1.3.3.3.2-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|------|-----------|---|-------------|-------------|---------------| +| n/a | | | | | | + +This method shall support the request data structures specified in table 6.1.3.3.3.2-2 and the response data structures and response codes specified in table 6.1.3.3.3.2-3. + +**Table 6.1.3.3.3.2-2: Data structures supported by the DELETE Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 6.1.3.3.3.2-3: Data structures supported by the DELETE Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No content | | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection. (NOTE 2) | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection. (NOTE 2) | +| Problem Details | O | 0..1 | 404 Not Found | Indicates the deletion of the context has failed due to application error.

The "cause" attribute may be used to indicate one of the following application errors:
- CONTEXT NOT FOUND | + +NOTE 1: The mandatory HTTP error status code for the DELETE method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. +NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +**Table 6.1.3.3.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative MF (service) instance.
Or the same URI, if a request is redirected to the same target resource via a different SCP. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target MF instance ID towards which the request is redirected. | + +**Table 6.1.3.3.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located on an alternative MF (service) instance.
Or the same URI, if a request is redirected to the same target resource via a different SCP. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target MF instance ID towards which the request is redirected. | + +##### 6.1.3.3.4 Resource Custom Operations + +None in the release of specification. + +### 6.1.4 Custom Operations without associated resources + +None in this release of specification. + +### 6.1.5 Notifications + +None in this release of specification. + +### 6.1.6 Data Model + +#### 6.1.6.1 General + +This clause specifies the application data model supported by the API. + +Table 6.1.6.1-1 specifies the data types defined for the Nmf\_MRM service based interface protocol. + +**Table 6.1.6.1-1: Nmf\_MRM specific Data Types** + +| Data type | Clause defined | Description | Applicability | +|-----------------|----------------|--------------------------------------------------|---------------| +| MediaContext | 6.1.6.2.2 | Represents an individual context resource on MF. | | +| TerminationInfo | 6.1.6.2.3 | Represents the termination information. | | +| MediaInfo | 6.1.6.2.4 | Represents the media Information. | | +| DcMedia | 6.1.6.2.5 | Represents the DC media descriptor. | | +| ArMedia | 6.1.6.2.6 | Represents the AR media descriptor. | | + +Table 6.1.6.1-2 specifies data types re-used by the Nmf\_MRM service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Nmf\_MRM service based interface. + +**Table 6.1.6.1-2: Nmf\_MRM re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|-----------------------------------------------------------|---------------| +| ProblemDetails | 3GPP TS 29.571 [16] | Problem Details | | +| MediaId | 3GPP TS 29.571 [16] | Uniquely identifies one media flow within an IMS session. | | +| MaxMessageSize | 3GPP TS 29.571 [16] | Max SCTP user message size. | | +| MediaResourceType | 3GPP TS 29.571 [16] | Media resource types. | | +| MediaProxy | 3GPP TS 29.571 [16] | Media proxy configuration applicable to the media flow | | +| SecuritySetup | 3GPP TS 29.571 [16] | Security setup of the DTLS association. | | +| DcEndpoint | 3GPP TS 29.571 [16] | DC endpoint | | +| DcStream | 3GPP TS 29.571 [16] | Data channel stream information. | | +| ReplaceHttpUrl | 3GPP TS 29.571 [16] | Replacement HTTP URL allocated by the application layer. | | +| Uri | 3GPP TS 29.571 [16] | Uri | | +| Endpoint | 3GPP TS 29.571 [16] | Represents the IP endpoint. | Endpoint | + +#### 6.1.6.2 Structured data types + +##### 6.1.6.2.1 Introduction + +This clause defines the structures to be used in resource representations. + +##### 6.1.6.2.2 Type: MediaContext + +Table 6.1.6.2.2-1: Definition of type MediaContext + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------|---------------| +| contextId | string | C | 0..1 | Identifies a specific context. It is assigned by the MF when creating a new context, i.e. Nmf_MRM_Create operation. | | +| terminations | array(TerminationInfo) | M | 1..N | Represents the media terminations | | + +##### 6.1.6.2.3 Type: TerminationInfo + +Table 6.1.6.2.3-1: Definition of type TerminationInfo + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| terminationId | string | C | 0..1 | Identifies a specific media termination. It is assigned by the MF when creating a new termination. It shall be included in the response of adding a new media termination, i.e., the Nmf_MRM_Create operation and in the Nmf_MRM_Update operation with adding a new termination. | | +| medias | array(MediaInfo) | M | 1..N | Represent the list of media resources for one or multiple medias on the Mb interface. | | + +##### 6.1.6.2.4 Type: MediaInfo + +Table 6.1.6.2.4-1: Definition of type MediaInfo + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|--------------------|-------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| mediaId | string | M | 1 | Identifies a media stream, e.g. data channel. | | +| mediaResourceType | MediaResourceType | M | 1 | Represents the media resource type, e.g. DC, AR. | | +| localMbEndpoint | Endpoint | C | 0..1 | Represents the local IP address and port number of the local endpoint of MF on the Mb interface.
It will be allocated by MF.
It shall be contained in the response when creating a new media stream, i.e. Nmf_MRM_Create operation or Nmf_MRM_Update operation with adding a new termination or adding a media in an existing termination. (NOTE 1, NOTE 2) | | +| remoteMbEndpoint | Endpoint | C | 0..1 | Represents the IP address and port number of the remote endpoint on the Mb interface, e.g. remote UE.
It shall be contained in the request of creating a new media stream, i.e. Nmf_MRM_Create operation or Nmf_MRM_Update operation with adding a new termination or adding a media in an existing termination. It can be Null when originating a new media. (NOTE 1, NOTE 2) | | +| dcMedia | DcMedia | C | 0..1 | Represents the data channel media descriptors. It shall be contained if the mediaResourceType is set to "DC". | | +| arMedia | ArMedia | C | 0..1 | Represents the AR media descriptors. It shall be contained if the mediaResourceType is set to "AR". | | +| mediaProcessingURL | Uri | C | 0..1 | The mediaProcessingURL indicates the address where MF receive service-related media instructions. It shall be contained in the response when creating a new media stream, i.e. Nmf_MRM_Create operation or Nmf_MRM_Update operation with adding a new termination or adding a media in an existing termination. (NOTE 1) | | + +NOTE 1: The IE cannot be changed once the media has been established. + +NOTE 2: The attribute "transport" inside Endpoint data type shall be set to value only "UDP". + +##### 6.1.6.2.5 Type: DcMedia + +**Table 6.1.6.2.5-1: Definition of type DcMedia** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|--------------------|-------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| mediaProxyConfig | MediaProxy | C | 0..1 | Represents the media proxy configuration. It shall be included if the mediald represents bootstrap or P2A/A2P application data channels. | | +| replaceHttpUrl | Map(ReplacementHttpUrl) | C | 0..1 | A map (list of key-value pairs where streamId is used as key of the map) of ReplacementHttpUrl.
Represents URL for the specific IMS subscriber when requesting the application list (e.g. graphical user interface) via the MDC1 interface. It shall be included if the mediald represents bootstrap data channel and streamId is 0 and 100. | | +| remoteMdc1Endpoint | Endpoint | C | 0..1 | Represents the remote MDC1 media endpoint information, i.e. the IP address and port number of DCSF. It shall be included if the mediald represents a bootstrap data channel. | | +| remoteMdc2Endpoint | Endpoint | C | 0..1 | Represents the remote MDC2 media endpoint address, i.e. the IP address and port number of DC AS. It shall be included if the mediald represents a P2A/A2P application data channel and the mediaProxyConfig is set to "HTTP". | | +| localMdc1Endpoint | Endpoint | C | 0..1 | Represents the local MF MDC1 media endpoint information. It will be allocated by MF and contained in the response when the mediald represents a bootstrap data channel. | | +| localMdc2Endpoint | Endpoint | C | 0..1 | Represents the local MF MDC2 media endpoint information. It will be allocated by MF and contained in the response when the mediald represents a P2A/A2P application data channel. | | +| mdc2Protocol | string | O | 0..1 | Represents the transport layer protocols for MDC2 interface. It may be included when mediaProxyConfig is set "HTTP" and remoteMdc2Endpoint is present. This IE is formatted as the following pattern, for example:
'UDP/DTLS/SCTP' | | +| streams | map(DcStream) | M | 1..N | A map (list of key-value pairs where streamId is used as key of the map) of DcStream.
Represents the data channel mapping and configuration information when originating/terminating data channel media flows on the Mb interface. | | +| maxMessageSize | MaxMessageSize | O | 0..1 | Represents the maximum size of to be expected. | | +| localDcEndpoint | DcEndpoint | C | 0..1 | Represents the DC endpoint for the Data Channel.
It will be allocated by MF.
It shall be contained in the response when creating a new media stream, i.e. Nmf_MRM_Create operation or Nmf_MRM_Update operation with adding a new termination or adding a media in an existing termination. (NOTE) | | + +| | | | | | | +|---------------------------------------------------------------------|---------------|---|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| remoteDcEndpoint | DcEndpoint | C | 0..1 | Represents the DC Endpoint for the Data Channel on the Mb interface. It shall be contained in the request of creating a new media stream, i.e. Nmf_MRM_Create operation or Nmf_MRM_Update operation with adding a new termination or adding a media in an existing termination. It can be NULL when originating a data channel media. (NOTE) | | +| securitySetup | SecuritySetup | O | 0..1 | Represents the security set up of the DTLS association. | | +| NOTE: The IE cannot be changed once the media has been established. | | | | | | + +##### 6.1.6.2.6 Type: ArMedia + +**Table 6.1.6.2.6-1: Definition of type ArMedia** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------|---|-------------|-------------|---------------| +| | | | | | | + +Editor's note: The definition of ArMedia is FFS. + +#### 6.1.6.3 Simple data types and enumerations + +##### 6.1.6.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +##### 6.1.6.3.2 Simple data types + +The simple data types defined in table 6.1.6.3.2-1 shall be supported. + +**Table 6.1.6.3.2-1: Simple data types** + +| Type Name | Type Definition | Description | Applicability | +|-----------|-----------------|-------------|---------------| +| | | | | + +### 6.1.7 Error Handling + +#### 6.1.7.1 General + +For the Nmf\_MRM API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4]. + +In addition, the requirements in the following clauses are applicable for the Nmf\_MRM API. + +#### 6.1.7.2 Protocol Errors + +No specific procedures for the Nmf\_MRM service are specified. + +#### 6.1.7.3 Application Errors + +The application errors defined for the Nmf\_MRM service are listed in Table 6.1.7.3-1. + +**Table 6.1.7.3-1: Application errors** + +| Application Error | HTTP status code | Description | +|--------------------------|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CONTEXT_NOT_FOUND | 404 Not Found | Indicates that the requested context is not found in the MF. | +| MEDIA_ID_CONFLICT | 403 Forbidden | Indicates that mediald which identifies the newly added media has existed within the specific termination. | +| MEDIA_CONNECTION_CHANGED | 403 Forbidden | Indicates that the connection information which has been marked that cannot be changed once the media has established is changed in the request. including the remoteMbEndpoint, localMbEndpoint etc. | + +### 6.1.8 Feature negotiation + +The optional features in table 6.1.8-1 are defined for the Nmf\_MRM API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4]. + +**Table 6.1.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|-------------| +| | | | + +### 6.1.9 Security + +As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Nmf\_MRM API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server. + +If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Nmf\_MRM API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2. + +NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Nmf\_MRM service. + +The Nmf\_MRM API defines a single scope "nmf-mrm" for the entire service, and it does not define any additional scopes at resource or operation level. + +### 6.1.10 HTTP redirection + +An HTTP request may be redirected to a different MF service instance when using direct or indirect communications (see 3GPP TS 29.500 [4]). + +An SCP that reselects a different MF producer instance will return the NF Instance ID of the new MF producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.10.3.4 of 3GPP TS 29.500 [4]. + +If an MF redirects a service request to a different MF using an 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new MF towards which the service request is redirected shall be indicated in the 3gpp-Sbi-Target-Nf-Id header of the 307 Temporary Redirect or 308 Permanent Redirect response as specified in clause 6.10.9.1 of 3GPP TS 29.500 [4]. + +# Annex A (normative): OpenAPI specification + +## A.1 General + +This Annex specifies the formal definition of the API(s) defined in the present specification. It consists of OpenAPI specifications in YAML format. + +This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s). + +NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply. + +Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5.3.1 of 3GPP TS 29.501 [5] and clause 5B of 3GPP TR 21.900 [7]). + +## A.2 Ndcnf\_MRM API + +``` +openapi: 3.0.0 + +info: + title: 'MF Media Resource Management (MRM) Service' + version: 1.0.0-alpha.1 + description: | + MF Media Resource Management (MRM) Service. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + +externalDocs: + description: > + 3GPP TS 29.176 V18.0.0; IP Multimedia Subsystem (IMS); Media Function (MF) Services; Stage 3. + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.176/ + +servers: + - url: '{apiRoot}/nmf-mrm/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501 + +security: + - {} + - oAuth2ClientCredentials: + - nmf-mrm + +paths: + + /contexts: + post: + summary: Create a new media context. + operationId: CreateMediaContext + tags: + - MediaContext(Collection) + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/MediaContext' + responses: + '201': + description: Success + content: +``` + +``` + + application/json: + schema: + $ref: '#/components/schemas/MediaContext' + headers: + Location: + description: > + Contains the URI of the newly created resource, according to the structure: + {apiRoot}/nmf-mrm//contexts/{contextId} + required: true + schema: + type: string + '307': + description: Temporary Redirect + content: + application/json: + schema: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RedirectResponse' + headers: + Location: + description: The URI pointing to the resource located on the redirect target MF. + required: true + schema: + type: string + '308': + description: Permanent Redirect + content: + application/json: + schema: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RedirectResponse' + headers: + Location: + description: The URI pointing to the resource located on the redirect target MF. + required: true + schema: + type: string + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +/contexts/{contextId}: + + patch: + summary: Update Media Context + operationId: UpdateMediaContext + tags: + - Media Context ID (Document) + parameters: + - name: contextId + in: path + required: true + description: Unique ID of the Media Context to update. + schema: + type: string + requestBody: + content: + application/json-patch+json: + schema: + type: array + items: + +``` + +``` + $ref: 'TS29571_CommonData.yaml#/components/schemas/PatchItem' + minItems: 1 + required: true + responses: + '200': + description: Expected response to a valid request. + content: + application/json: + schema: + $ref: '#/components/schemas/MediaContext' + '204': + description: Expected response with empty body + '307': + description: Temporary Redirect + content: + application/json: + schema: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RedirectResponse' + headers: + Location: + description: The URI pointing to the resource located on the redirect target MF. + required: true + schema: + type: string + '308': + description: Permanent Redirect + content: + application/json: + schema: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RedirectResponse' + headers: + Location: + description: The URI pointing to the resource located on the redirect target MF. + required: true + schema: + type: string + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '409': + $ref: 'TS29571_CommonData.yaml#/components/responses/409' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '412': + $ref: 'TS29571_CommonData.yaml#/components/responses/412' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '501': + $ref: 'TS29571_CommonData.yaml#/components/responses/501' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +delete: + summary: Deletes a given Media Context + operationId: DeleteMediaContext + tags: + - Media Context ID (Document) + parameters: + - name: contextId + in: path + required: true + description: Unique ID of the Media Context to delete. + schema: + type: string + responses: + '204': + description: Expected response to a successful deletion. +``` + +``` +'307': + description: Temporary Redirect + content: + application/json: + schema: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RedirectResponse' + headers: + Location: + description: The URI pointing to the resource located on the redirect target NRF. + required: true + schema: + type: string +'308': + description: Permanent Redirect + content: + application/json: + schema: + $ref: 'TS29571_CommonData.yaml#/components/schemas/RedirectResponse' + headers: + Location: + description: The URI pointing to the resource located on the redirect target NRF. + required: true + schema: + type: string +'400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' +'411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' +'429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' +'501': + $ref: 'TS29571_CommonData.yaml#/components/responses/501' +'503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' +``` + +### components: + +``` +securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{nrfApiRoot}/oauth2/token' + scopes: + nmf-mrm: Access to the Nmf_MRM API. +``` + +### schemas: + +``` +MediaContext: + description: Information of a Media Context in a MF. + type: object + required: + - terminations + properties: + contextId: + type: string + terminations: + type: array + items: + $ref: '#/components/schemas/TerminationInfo' + minItems: 1 + +TerminationInfo: + description: Represents the termination information. + type: object + required: + - medias + properties: +``` + +``` + terminationId: + type: string + medias: + type: array + items: + $ref: '#/components/schemas/MediaInfo' + minItems: 1 + +MediaInfo: + description: Represents the media information. + type: object + required: + - mediaId + - mediaResourceType + properties: + mediaId: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MediaId' + mediaResourceType: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MediaResourceType' + localMbEndpoint: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Endpoint' + remoteMbEndpoint: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Endpoint' + dcMedia: + $ref: '#/components/schemas/DcMedia' + mediaProcessingUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + +DcMedia: + description: Represents the DC media descriptor. + type: object + required: + - streams + properties: + mediaProxyConfig: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MediaProxy' + replaceHttpUrl: + type: object + description: > + Contains a list of replacement HTTP URLs. The streamId attribute + within the ReplaceHttpUrl data type is the key of the map. + additionalProperties: + $ref: 'TS29571_CommonData.yaml#/components/schemas/ReplaceHttpUrl' + minProperties: 1 + remoteMdc1Endpoint: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Endpoint' + remoteMdc2Endpoint: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Endpoint' + localMdc1Endpoint: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Endpoint' + localMdc2Endpoint: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Endpoint' + mdc2Protocol: + type: string + streams: + type: object + description: > + Contains a data channel mapping and configuration information. The streamId + attribute within the DcStream data type is the key of the map. + additionalProperties: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DcStream' + minProperties: 1 + maxMessageSize: + $ref: 'TS29571_CommonData.yaml#/components/schemas/MaxMessageSize' + localDcEndpoint: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DcEndpoint' + remoteDcEndpoint: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DcEndpoint' + securitySetup: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SecuritySetup' +``` + +# Annex B (informative): Change history + +| Change history | | | | | | | | | +|----------------|--------------|-----------|----|-----|-----|-----------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2023-04 | CT4#115
e | C4-231552 | | | | Version 0.1.0 | | 0.1.0 | +| 2023-05 | CT4#116 | C4-232178 | | | | Clause 4 Overview | | 0.2.0 | +| 2023-05 | CT4#116 | C4-232224 | | | | Clause 5.1 Introduction of DCMF services | | 0.2.0 | +| 2023-05 | CT4#116 | C4-232506 | | | | Service description and service operation introduction of MRM service | | 0.2.0 | +| 2023-05 | CT4#116 | C4-232607 | | | | MRM API definition | | 0.2.0 | +| 2023-05 | CT4#116 | C4-232637 | | | | MRM service operations | | 0.2.0 | +| 2023-08 | CT4#117 | C4-233707 | | | | Change DCMF to MF | | 0.3.0 | +| 2023-08 | CT4#117 | C4-233307 | | | | Update the data channel related data types | | 0.3.0 | +| 2023-08 | CT4#117 | C4-233306 | | | | Update MF service to support AR | | 0.3.0 | +| 2023-10 | CT4#118 | C4-234539 | | | | Update the scope | | 0.4.0 | +| 2023-10 | CT4#118 | C4-234540 | | | | Support of Redirection | | 0.4.0 | +| 2023-10 | CT4#118 | C4-234575 | | | | Clarification on the DC media | | 0.4.0 | +| 2023-10 | CT4#118 | C4-234543 | | | | Editorial Corrections | | 0.4.0 | +| 2023-10 | CT4#118 | C4-234544 | | | | Update the data model for AR remote cooperation | | 0.4.0 | +| 2023-10 | CT4#118 | C4-234341 | | | | Usage of the apiVersion placeholder | | 0.4.0 | +| 2023-11 | CT4#119 | C4-235576 | | | | Move the Endpoint to Common Data | | 0.5.0 | +| 2023-11 | CT4#119 | C4-235473 | | | | OpenAPI of Nmf_MRM Service | | 0.5.0 | +| 2023-12 | CT#102 | CP-233022 | | | | Presented for information and approval | | 1.0.0 | +| 2023-12 | CT#102 | CP-233022 | | | | Approved in TSC CT#102 | | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29213/raw.md b/marked/Rel-18/29_series/29213/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..37c4a52fc6791aee8e57caa1f863eee90c6e8739 --- /dev/null +++ b/marked/Rel-18/29_series/29213/raw.md @@ -0,0 +1,7318 @@ +# 3GPP TS 29.213 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control signalling flows and Quality of Service (QoS) parameter mapping (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +## --- **Keywords** + +UMTS, LTE, QoS, Charging, Policy + +--- + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles – Sophia Antipolis +Valbonne – France +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +--- + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|----------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 9 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions and abbreviations ..... | 12 | +| 3.1 Definitions..... | 12 | +| 3.2 Abbreviations ..... | 13 | +| 3a Reference architecture..... | 14 | +| 4 Signalling Flows over Gx, Gxx, Rx, Sd, Sy, Np, Nt, St and S9 ..... | 17 | +| 4.0 General ..... | 17 | +| 4.1 IP-CAN Session Establishment..... | 18 | +| 4.2 IP-CAN Session Termination..... | 22 | +| 4.2.1 UE-Initiated ..... | 22 | +| 4.2.1.1 AF located in the HPLMN..... | 22 | +| 4.2.1.2 AF located in the VPLMN..... | 25 | +| 4.2.2 PCEF-Initiated..... | 27 | +| 4.2.2.1 AF located in the HPLMN..... | 27 | +| 4.2.2.2 AF located in the VPLMN..... | 29 | +| 4.2.3 PCRF-Initiated..... | 30 | +| 4.2.3.1 AF located in the HPLMN..... | 30 | +| 4.2.3.2 AF located in the VPLMN..... | 32 | +| 4.3 IP-CAN Session Modification ..... | 34 | +| 4.3.1 Network-Initiated IP-CAN Session Modification..... | 34 | +| 4.3.1.1 Interactions between BBERF, PCEF, TDF, OCS, TSSF and PCRF(PCC/QoS/ADC Rule Provisioning in PUSH mode) ..... | 34 | +| 4.3.1.2 Interactions between PCRF, AF and SPR ..... | 39 | +| 4.3.1.2.1 AF Session Establishment..... | 39 | +| 4.3.1.2.2 AF session modification..... | 42 | +| 4.3.1.2.2.1 AF located in the HPLMN ..... | 42 | +| 4.3.1.2.2.2 AF located in the VPLMN ..... | 44 | +| 4.3.1.2.3 AF session termination..... | 45 | +| 4.3.1.2.3.1 AF located in the HPLMN ..... | 45 | +| 4.3.1.2.3.2 AF located in the VPLMN ..... | 47 | +| 4.3.2 PCEF –Initiated IP-CAN Session Modification (PCC Rule Provisioning in PULL Mode) ..... | 48 | +| 4.3.2.1 PCEF-initiated IP-CAN Session Modification. AF located in HPLMN. .... | 48 | +| 4.3.2.2 PCEF-initiated IP-CAN Session Modification, AF located in the VPLMN ..... | 53 | +| 4.4 Gateway Control Session Procedures ..... | 54 | +| 4.4.1 Gateway Control Session Establishment..... | 55 | +| 4.4.2 Gateway Control and QoS Rules Request..... | 59 | +| 4.4.2.1 Non-Roaming and Home Routed cases ..... | 59 | +| 4.4.2.2 Visited access cases ..... | 61 | +| 4.4.3 Gateway Control and QoS Rules Provision ..... | 62 | +| 4.4.4 Gateway Control Session Termination..... | 63 | +| 4.4.4.1 BBERF-Initiated Gateway Control Session Termination..... | 63 | +| 4.4.4.2 PCRF-Initiated Gateway Control Session Termination..... | 65 | +| 4.5 Multiple BBERF Signalling Flows ..... | 66 | +| 4.5.1 Non-Roaming and Home Routed cases..... | 66 | +| 4.5.1.1 New Gateway Control Session Establishment..... | 66 | +| 4.5.1.2 PCEF IP-CAN session modification – Handover..... | 69 | +| 4.5.1.3 PCEF IP-CAN session modification – S2c-based IP flow mobility..... | 70 | +| 4.5.1.4 Gateway Control Session Establishment and PCEF IP-CAN session modification – S2c-based IP flow mobility..... | 72 | +| 4.5.2 Visited access case ..... | 73 | +| 4.5.2.1 New Gateway Control Session Establishment..... | 73 | +| 4.5.2.2 PCEF-Initiated IP-CAN session modification-Handover..... | 75 | + +| | | | +|---------|--------------------------------------------------------------------------------------------------------------------|-----| +| 4.5.2.3 | PCEF-Initiated IP-CAN session modification - S2c-based IP flow mobility..... | 77 | +| 4.5.2.4 | Gateway Control Session Establishment and PCEF IP-CAN session modification – S2c-based IP flow mobility..... | 79 | +| 4.6 | Application Detection and Enforcement Procedures ..... | 81 | +| 4.6.1 | TDF Session Establishment in case of solicited reporting ..... | 81 | +| 4.6.1A | TDF Session Establishment in case of unsolicited reporting ..... | 82 | +| 4.6.2 | TDF Session termination..... | 82 | +| 4.6.3 | TDF Session modification..... | 84 | +| 4.6.3.1 | Application Detection, Reporting and Control Rules Request..... | 84 | +| 4.6.3.2 | Application Detection and Control Rules Provision..... | 85 | +| 4.7 | Spending limits Procedures over Sy reference point ..... | 86 | +| 4.7.1 | Initial Spending Limit Report Request..... | 86 | +| 4.7.2 | Intermediate Spending Limit Report Request ..... | 86 | +| 4.7.3 | Final Spending Limit Report Request ..... | 87 | +| 4.7.4 | Spending Limit Report ..... | 88 | +| 4.8 | Call flows for User Plane Congestion Management..... | 88 | +| 4.8.1 | General ..... | 88 | +| 4.8.2 | RUCI reporting ..... | 89 | +| 4.8.2.1 | Non-aggregated RUCI report procedure..... | 89 | +| 4.8.2.2 | Aggregated RUCI report procedure..... | 89 | +| 4.8.3 | Np reporting restriction provisioning ..... | 90 | +| 4.8.4 | UE mobility between RCAFs..... | 90 | +| 4.8.5 | Removal of UE context ..... | 91 | +| 4.9 | Traffic Steering Control Procedures over St reference point..... | 91 | +| 4.9.1 | St Session Establishment..... | 91 | +| 4.9.2 | St Session Modification..... | 92 | +| 4.9.3 | St Session Termination..... | 93 | +| 4.9.4 | St notification initiated by the TSSF ..... | 93 | +| 4.10 | Negotiation for future background data transfer procedure over Nt reference point..... | 94 | +| 5 | Binding Mechanism ..... | 94 | +| 5.1 | Overview ..... | 94 | +| 5.2 | Session Binding..... | 95 | +| 5.3 | PCC Rule Authorization and QoS Rule Generation ..... | 96 | +| 5.4 | Bearer Binding ..... | 97 | +| 6 | QoS Parameters Mapping ..... | 98 | +| 6.1 | Overview ..... | 98 | +| 6.1.1 | UE-Initiated IP-CAN bearers ..... | 100 | +| 6.1.2 | Network-Initiated IP-CAN bearers..... | 101 | +| 6.2 | QoS parameter mapping Functions at AF ..... | 102 | +| 6.3 | QoS parameter mapping Functions at PCRF ..... | 115 | +| 6.4 | QoS parameter mapping Functions at PCEF..... | 124 | +| 6.4.1 | GPRS ..... | 124 | +| 6.4.1.1 | Authorized IP QoS parameters per PDP Context to Authorized UMTS QoS parameters mapping in GGSN ..... | 124 | +| 6.4.1.2 | Comparing UMTS QoS Parameters against the Authorized UMTS QoS parameters in GGSN for UE initiated PDP context..... | 126 | +| 6.4.2 | 3GPP- EPS..... | 126 | +| 6.4.2.1 | Authorized IP QoS parameters per PDP Context to Authorized UMTS QoS parameters mapping in P-GW..... | 126 | +| 6.4.2.2 | Comparing UMTS QoS Parameters against the Authorized UMTS QoS parameters in P-GW for UE initiated PDP context..... | 129 | +| 6.5 | QoS parameter mapping Functions at UE for a UE-initiated GPRS PDP Context..... | 129 | +| 6.5.1 | SDP to UMTS QoS parameter mapping in UE..... | 131 | +| 6.5.2 | SDP parameters to Authorized UMTS QoS parameters mapping in UE..... | 131 | +| 7 | PCRF addressing..... | 137 | +| 7.1 | General ..... | 137 | +| 7.2 | DRA Definition..... | 137 | +| 7.3 | DRA Procedures..... | 137 | +| 7.3.1 | General ..... | 137 | +| 7.3.2 | DRA Information Storage ..... | 137 | + +| | | | +|--------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|------------| +| 7.3.3 | Capabilities Exchange ..... | 138 | +| 7.3.4 | Redirect DRA ..... | 138 | +| 7.3.4.1 | Redirecting Diameter Requests ..... | 138 | +| 7.3.4.2 | DRA binding removal..... | 139 | +| 7.3.5 | Proxy DRA ..... | 139 | +| 7.3.6 | PCRF selection by BBERF/PCEF (non-roaming case)..... | 139 | +| 7.3.7 | PCRF selection by AF ..... | 140 | +| 7.3.8 | PCRF selection in a roaming scenario..... | 140 | +| 7.3.9 | PCRF selection by TDF for unsolicited application reporting ..... | 141 | +| 7.3.10 | PCRF selection by RCAF..... | 141 | +| 7.4 | DRA flows..... | 141 | +| 7.4.1 | Proxy DRA ..... | 141 | +| 7.4.1.1 | Establishment of Diameter Sessions..... | 141 | +| 7.4.1.1.1 | Non-roaming cases..... | 141 | +| 7.4.1.1.2 | Roaming cases..... | 142 | +| 7.4.1.2 | Modification of Diameter Sessions..... | 143 | +| 7.4.1.2.1 | Non-roaming cases..... | 143 | +| 7.4.1.2.2 | Roaming cases..... | 145 | +| 7.4.1.2.2.2 | H-PCRF initiated ..... | 146 | +| 7.4.1.3 | Termination of Diameter Sessions..... | 147 | +| 7.4.1.3.1 | Non-roaming cases..... | 147 | +| 7.4.1.3.2 | Roaming cases..... | 148 | +| 7.4.2 | Redirect DRA ..... | 149 | +| 7.4.2.1 | Establishment of Diameter Sessions..... | 149 | +| 7.4.2.1.1 | Non-roaming cases..... | 149 | +| 7.4.2.1.2 | Roaming cases..... | 150 | +| 7.4.2.2 | Modification of Diameter sessions ..... | 151 | +| 7.4.2.3 | Termination of Diameter Sessions..... | 151 | +| 7.4.2.3.1 | Non-roaming cases..... | 151 | +| 7.4.2.3.2 | Roaming cases..... | 152 | +| 8 | Diameter race condition handling ..... | 154 | +| 8.1 | Overview ..... | 154 | +| 8.2 | Procedures for Gx, Gxx, Sd and S9 ..... | 154 | +| Annex A (informative): Examples of deriving the Maximum Authorized parameters from the SDP parameters ..... | | 156 | +| Annex B (normative): Signalling Flows for IMS..... | | 157 | +| B.0 | General..... | 157 | +| B.1 | Subscription to Notification of Signalling Path Status at IMS Registration..... | 157 | +| B.1a | Subscription to Notification of Change of IP-CAN Type at IMS Registration..... | 158 | +| B.1b | Provisioning of SIP signalling flow information at IMS Registration..... | 159 | +| B.1c | Subscription to Notification of Change of PLMN Identifier at IMS Registration..... | 160 | +| B.2 | IMS Session Establishment..... | 162 | +| B.2.1 | Provisioning of service information at Originating P-CSCF and PCRF..... | 162 | +| B.2.2 | Provisioning of service information at terminating P-CSCF and PCRF..... | 165 | +| B.3 | IMS Session Modification ..... | 169 | +| B.3.1 | Provisioning of service information..... | 169 | +| B.3.2 | Enabling of IP Flows..... | 173 | +| B.3.3 | Disabling of IP Flows..... | 174 | +| B.3.4 | Media Component Removal..... | 175 | +| B.4 | IMS Session Termination..... | 176 | +| B.4.1 | Mobile initiated session release / Network initiated session release..... | 176 | +| B.4.2 | IP-CAN Bearer Release/Loss..... | 178 | +| B.5 | P-CSCF Restoration ..... | 179 | + +| | | | +|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|------------| +| B.6 | IMS Restricted Local Operator Services ..... | 180 | +| B.7 | Retrieval of Network Provided Location Information for SMS over IP at Originating side..... | 180 | +| B.8 | Retrieval of Network Provided Location Information for SMS over IP at Terminating side ..... | 181 | +| Annex C (normative): NAT Related Procedures ..... | | 183 | +| C.1 | Support for media traversal of NATs using ICE..... | 183 | +| C.2 | P-CSCF procedures..... | 183 | +| C.2.1 | General ..... | 183 | +| C.2.2 | Deriving the Ues IP address..... | 184 | +| C.2.3 | Deriving flow descriptions ..... | 184 | +| C.2.4 | Gating control..... | 184 | +| C.2.5 | Bandwidth impacts..... | 184 | +| C.3 | PCRF procedures ..... | 185 | +| C.3.1 | General ..... | 185 | +| C.3.2 | Deriving additional flow descriptions ..... | 185 | +| C.3.3 | Gating control..... | 185 | +| C.3.4 | Bandwidth impacts..... | 185 | +| C.4 | P_CSCF procedures to support media traversal through hosted NAT without ICE..... | 185 | +| Annex D (normative): Access specific procedures for GPRS..... | | 187 | +| D.1 | General..... | 187 | +| D.2 | Binding Mechanisms..... | 187 | +| D.3 | PCC Procedures ..... | 188 | +| D.3.1 | IP-CAN Session Modification ..... | 188 | +| D.3.1.1 | Network-initiated IP-CAN Session Modification ..... | 188 | +| D.3.1.2 | PCEF-initiated IP-CAN Session Modification..... | 188 | +| D.3.1.2.1 | UE-initiated IP-CAN Bearer Establishment or IP-CAN Bearer Modification..... | 188 | +| D.3.1.2.2 | UE-initiated IP-CAN Bearer Termination..... | 191 | +| Annex E (normative): Fixed Broadband Access Interworking with EPC..... | | 194 | +| E.1 | General..... | 194 | +| E.2 | Definitions and abbreviations ..... | 194 | +| E.2.1 | Definitions..... | 194 | +| E.2.2 | Abbreviations ..... | 194 | +| E.3 | Binding Mechanisms..... | 194 | +| E.3.1 | EPC-routed traffic ..... | 194 | +| E.3.2 | NSWO traffic ..... | 194 | +| E.4 | PCC Procedures ..... | 195 | +| E.4.1 | Introduction ..... | 195 | +| E.4.2 | IP-CAN Session Establishment..... | 196 | +| E.4.2.1 | IP-CAN Session Establishment for EPC- routed traffic..... | 196 | +| E.4.2.2 | IP-CAN Session Establishment for NSWO traffic..... | 200 | +| E.4.3 | IP-CAN Session Termination..... | 202 | +| E.4.3.1 | IP-CAN Session Termination for EPC- routed traffic ..... | 202 | +| E.4.3.2 | IP-CAN Session Termination for NSWO traffic..... | 206 | +| E.4.3.2.1 | BPCF-initiated IP-CAN Session Termination for NSWO traffic..... | 206 | +| E.4.3.2.2 | PCRF-initiated IP-CAN Session Termination for NSWO traffic..... | 208 | +| E.4.4 | IP-CAN Session Modification ..... | 209 | +| E.4.4.1 | IP-CAN Session Modification for EPC-routed traffic ..... | 209 | +| E.4.4.1.1 | PCRF-initiated IP-CAN Session Modification..... | 209 | +| E.4.4.1.2 | BPCF-initiated IP-CAN Session Modification..... | 210 | +| E.4.4.1.3 | PCEF-initiated IP-CAN Session Modification..... | 212 | +| E.4.4.1.4 | BBERF-initiated IP-CAN Session Modification..... | 213 | +| E.4.4.2 | IP-CAN Session Modification for NSWO traffic ..... | 215 | + +| | | | +|-------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|------------| +| E.4.4.2.1 | PCRF-initiated IP-CAN Session Modification..... | 215 | +| E.4.4.2.2 | BPCF-initiated IP-CAN Session Modification..... | 217 | +| E.5 | 3GPP HNB Procedures – CS Support..... | 219 | +| E.5.1 | S9a CS Session Establishment..... | 219 | +| E.5.2 | PCRF initiated S9a CS Session Modification..... | 220 | +| E.5.2a | BPCF initiated S9a CS Session Modification..... | 221 | +| E.5.3 | S9a CS Session Termination..... | 221 | +| E.6 | PCRF Addressing..... | 222 | +| E.6.1 | General ..... | 222 | +| E.6.2 | DRA Definition..... | 223 | +| E.6.3 | DRA Procedure ..... | 223 | +| E.6.3.1 | DRA Information Storage ..... | 223 | +| E.6.3.2 | Capabilities Exchange ..... | 223 | +| E.6.3.3 | Redirect DRA ..... | 224 | +| E.6.3.4 | Proxy DRA ..... | 224 | +| E.6.3.5 | PCRF selection by BPCF ..... | 224 | +| E.6.3.6 | PCRF selection by AF and TDF in Unsolicited application reporting mode for NSWO traffic..... | 225 | +| E.6.3.7 | PCRF selection in a roaming scenario..... | 225 | +| E.6.3.8 | PCRF selection for the HNB CS Service ..... | 225 | +| E.6.4 | DRA flows..... | 226 | +| E.6.4.1 | General ..... | 226 | +| E.6.4.2 | Proxy DRA ..... | 226 | +| E.6.4.2.1 | S9 session establishment trigger ..... | 226 | +| E.6.4.2.2 | S9 session termination notification..... | 227 | +| E.6.4.3 | Redirect DRA ..... | 228 | +| E.6.4.3.1 | S9 session establishment trigger ..... | 228 | +| E.6.4.3.2 | S9 session termination notification..... | 228 | +| E.7 | BPCF Addressing..... | 229 | +| E.7.1 | General ..... | 229 | +| E.8 | Session Linking Function..... | 229 | +| Annex F (normative): Access specific aspects, Fixed Broadband Access network convergence ..... | | 230 | +| F.1 | General..... | 230 | +| F.2 | Definitions and abbreviations ..... | 230 | +| F.2.1 | Definitions..... | 230 | +| F.2.2 | Abbreviations ..... | 230 | +| F.3 | Binding Mechanisms..... | 230 | +| F.3.1 | NSWO traffic ..... | 230 | +| F.3.2 | Traffic from fixed devices..... | 231 | +| F.4 | PCC procedures..... | 231 | +| F.4.1 | Introduction ..... | 231 | +| F.4.2 | IP-CAN Session Establishment..... | 231 | +| F.4.3 | IP-CAN Session Termination..... | 231 | +| F.4.3.1 | UE-Initiated ..... | 231 | +| F.4.3.2 | PCEF-Initiated ..... | 232 | +| F.4.3.3 | PCRF-Initiated..... | 232 | +| F.4.4 | IP-CAN Session Modification ..... | 232 | +| F.4.4.1 | PCRF-Initiated IP-CAN Session Modification ..... | 232 | +| F.4.4.2 | PCEF-Initiated IP-CAN Session Modification ..... | 232 | +| F.5 | PCRF Addressing..... | 232 | +| F.5.1 | General ..... | 232 | +| F.5.2 | DRA Definition..... | 232 | +| F.5.3 | DRA Procedure ..... | 232 | +| F.5.3.1 | Redirect DRA ..... | 232 | +| F.5.3.2 | Proxy DRA ..... | 232 | +| F.5.3.3 | PCRF selection by AF and TDF in unsolicited application reporting mode..... | 233 | + +| | | | +|-------------------------------|-----------------------------------------------------|------------| +| F.5.3.4 | PCRF selection in a roaming scenario..... | 233 | +| F.5.4 | DRA flows..... | 233 | +| Annex G (normative): | Diameter overload control mechanism..... | 234 | +| G.1 | General..... | 234 | +| G.2 | Reporting Node..... | 234 | +| G.3 | Reacting Node..... | 234 | +| G.4 | DRA Diameter Overload Behavior..... | 234 | +| G.4.1 | DRA reacting to Host Reports ..... | 234 | +| Annex H (normative): | Access specific procedures for 3GPP EPS..... | 236 | +| H.1 | General..... | 236 | +| H.2 | Binding Mechanisms..... | 236 | +| Annex I (normative): | APN matching procedures ..... | 237 | +| Annex J (normative): | Diameter message priority mechanism..... | 237 | +| J.1 | General..... | 237 | +| J.2 | PCC functional element behaviour ..... | 237 | +| J.3 | Interactions..... | 238 | +| Annex K (normative): | Diameter load control mechanism ..... | 238 | +| K.1 | General..... | 238 | +| K.2 | Endpoint or Agent Reporting Node ..... | 238 | +| K.3 | Reacting Node..... | 238 | +| K.4 | DRA Behaviour..... | 239 | +| Annex L (informative): | Change history ..... | 240 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present specification adds detailed flows of Policy and Charging Control (PCC) over the Diameter-based Rx, Gx, Gxx, Sd, Sy, S9, Nt, Diameter-based St and Np reference points and their relationship with the bearer level signalling flows over the Gn/Gp, S4, S5/S8, S2a and S2c interfaces. + +The calls flows depicted in this Technical Specification represent usual cases, i.e. not all situations are covered. Detailed information provided in 3GPP TS 29.212 [9], 3GPP TS 29.214 [10], 3GPP TS 29.215 [22], 3GPP TS 29.217 [36], 3GPP TS 29.154 [56] and 3GPP TS 29.219 [28] shall be taken into consideration. + +The present specification also describes the PCC reference architectures for non-roaming and roaming scenarios. + +The present specification also describes the binding and the mapping of QoS parameters among SDP, UMTS QoS parameters, and QoS authorization parameters. + +The present specification also describes the PCRF addressing using DRA. + +The present specification also describes Diameter race condition handling for Gx based applications, i.e Gx, Gxx, Sd and S9. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication and/or edition number or version number) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”. +- [2] 3GPP TS 23.203: “Policy Control and charging architecture”. +- [3] 3GPP TS 23.060: “General Packet Radio Service (GPRS); Service description; Stage 2”. +- [4] 3GPP TS 23.107: “Quality of Service (QoS) concept and architecture”. +- [5] 3GPP TS 24.229: “IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3”. +- [6] 3GPP TS 26.234: “End-to-end transparent streaming service; Protocols and codecs”. + +- [7] Void. +- [8] Void +- [9] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [10] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point". +- [11] IETF RFC 2327: "SDP: Session Description Protocol". +- [12] IETF RFC 3264: "An Offer/Answer model with the Session Description Protocol (SDP)". +- [13] IETF RFC 3556: "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". +- [14] Void. +- [15] Void. +- [16] IETF RFC 4145: "TCP-Based Media Transport in the Session Description Protocol (SDP)". +- [17] IETF RFC 4975: "The Message Session Relay Protocol (MSRP)". +- [18] 3GPP2 C.S0046-0 v1.0: "3G Multimedia Streaming Services". +- [19] 3GPP2 C.S0055-A v1.0: "Packet Switched Video Telephony Services (PSVT/MCS)". +- [20] Void +- [21] 3GPP TS 23.402: "Architecture Enhancements for non-3GPP accesses". +- [22] 3GPP TS 29.215: "Policy and Charging Control over S9 reference point". +- [23] IETF RFC 3890: "A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP) ". +- [24] 3GPP TS 24.292: "IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3". +- [27] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2". +- [28] 3GPP TS 29.219: "Policy and Charging Control over Sy reference point". +- [29] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction" +- [30] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS) Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH) ". +- [31] Void. +- [32] Broadband Forum WT-134: "Policy Control Framework" (work in progress). +- [33] IETF RFC 7683: "Diameter Overload Indication Conveyance". +- [34] 3GPP TS 23.468: "Group Services and System Aspects; Group Communication System Enablers for LTE (GCSE LTE)". +- [35] 3GPP TS 23.380: "IMS Restoration Procedures". +- [36] 3GPP TS 29.217: "Policy and Charging Control: Congestion Reporting over Np reference point". +- [37] 3GPP TS 23.003: "Numbering, addressing and identification". +- [38] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [39] IETF RFC 5761: "Multiplexing RTP Data and Control Packets on a Single Port". + +- [40] IETF RFC 7944: "Diameter Routing Message Priority". +- [51] 3GPP TS 23.335: "User Data Convergence (UDC); Technical realization and information flows; Stage 2". +- [52] 3GPP TS 29.335: "User Data Convergence (UDC); User Data Repository Access Protocol over the Ud interface; Stage 3". +- [53] 3GPP TS 29.201: "Representational State Transfer (REST) reference point between Application Function (AF) and Protocol Converter (PC)". +- [54] 3GPP TS 29.155: "Traffic Steering Control; Representational State Transfer (REST) over St reference point". +- [55] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles". +- [56] 3GPP TS 29.154: "Service Capability Exposure Function over Nt reference point". +- [57] Void. +- [58] 3GPP TS 22.153: "Multimedia Priority Service". +- [59] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [60] IETF RFC 8583: "Diameter Load Information Conveyance". +- [61] IETF RFC 6733: "Diameter Base Protocol". +- [62] 3GPP TS 29.250: "Nu reference point between SCEF and PFDF for sponsored data connectivity". +- [63] 3GPP TS 29.251: "Gw and Gwn reference points for sponsored data connectivity". +- [64] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2". +- [65] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane of EPC Nodes; Stage 3". +- [66] 3GPP TS 23.221: "Architectural requirements". +- [67] IETF RFC 8445: "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal". +- [68] IETF RFC 8839: "Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)". +- [69] IETF RFC 8864: "Negotiation Data Channels Using the Session Description Protocol (SDP)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply: + +**DRA binding:** The PCRF routing information stored per UE or per PDN in the DRA, which include the user identity (UE NAI), the UE Ipv4 address and/or Ipv6 prefix, the APN (if available) and the selected PCRF identity for a certain IP-CAN Session. + +**Gateway Control Session:** An association between a BBERF and a PCRF (when GTP is not used in the EPC), used for transferring access specific parameters, BBERF events and QoS rules between the PCRF and BBERF. In the context of this specification this is implemented by use of the Gxx procedures. + +**IP-CAN session:** association between a UE and an IP network. + +The association is identified by one or more UE Ipv4 addresses/ and/or Ipv6 prefix together with a UE identity information, if available, and a PDN represented by a PDN ID (e.g. an APN). An IP-CAN session incorporates one or more IP-CAN bearers. Support for multiple IP-CAN bearers per IP-CAN session is IP-CAN specific. An IP-CAN session exists as long as the related UE Ipv4 address and/or Ipv6 prefix are assigned and announced to the IP network. + +**Policy counter:** A mechanism within the OCS to track spending applicable for a subscriber. + +**Policy counter status:** A label whose values are not standardized and that is associated with a policy counter's value relative to the spending limit(s) (the number of possible policy counter status values for a policy counter is one greater than the number of thresholds associated with that policy counter, i.e policy counter status values describe the status around the thresholds). This is used to convey information relating to subscriber spending from OCS to PCRF. Specific labels are configured jointly in OCS and PCRF. + +**RAN user plane congestion:** RAN user plane congestion occurs when the demand for RAN resources exceeds the available RAN capacity to deliver the user data for a prolonged period of time. + +NOTE: Short-duration traffic bursts is a normal condition at any traffic load level, and is not considered to be RAN user plane congestion. Likewise, a high-level of utilization of RAN resources (based on operator configuration) is considered a normal mode of operation and might not be RAN user plane congestion. + +**Restricted local operator services:** communication services provided by an operator that involve either automated or human assistance (e.g. credit card billing, directory assistance, customer care) for which successful authentication is not necessary. + +**Spending limit:** A spending limit is the usage limit of a policy counter (e.g. monetary, volume, duration) that a subscriber is allowed to consume. + +**Spending limit report:** a notification, containing the current policy counter status generated from the OCS to the PCRF via the Sy reference point. + +**TDF session:** An association between an IP-CAN session and the assigned TDF for the purpose of application detection and control by the PCRF . The association is identified by one UE Ipv4 address and/or Ipv6 prefix together with optionally a PDN represented by a PDN ID and a set of ADC rules to be applied by the TDF. + +## 3.2 Abbreviations + +For the purpose of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply: + +| | | +|--------|-----------------------------------------------------------------------------| +| ADC | Application Detection and Control | +| AF | Application Function | +| ARA | Aggregated RUCI Report Answer | +| ARP | Allocation and Retention Priority | +| ARR | Aggregated RUCI Report Request | +| AVP | Attribute-Value Pair | +| BBERF | Bearer Binding and Event Reporting Function | +| CHEM | Coverage and Handoff Enhancements using Multimedia error robustness feature | +| CSG | Closed Subscriber Group | +| CSG ID | Closed Subscriber Group Identity | +| CoA | Care of Address | +| DRA | Diameter Routing Agent | +| DRMP | Diameter Routing Message Priority | +| DSCP | Differentiated Services Code Point | +| DTS | Data Transport Service | +| GBR | Guaranteed Bitrate | +| GCS | Group Communication Service | +| GCS AS | Group Communication Service Application Server | +| H-AF | Home AF | +| H-DRA | Home DRA | +| H-PCRF | Home PCRF | +| HPLMN | Home PLMN | +| MBR | Maximum Bitrate | +| MUA | Modify UE context Answer | + +| | | +|--------|------------------------------------------| +| MUR | Modify UE context Request | +| MPS | Multimedia Priority Service | +| NBIFOM | Network-based IP flow mobility | +| NRA | Non-Aggregated RUCI Report Answer | +| NRR | Non-Aggregated RUCI Report Request | +| PA | Proxy Agent | +| PCC | Policy and Charging Control | +| PCEF | Policy and Charging Enforcement Function | +| PCRF | Policy and Charging Rule Function | +| PGW | PDN-Gateway | +| PFDF | Packet Flow Description Function | +| RLOS | Restricted Local Operator Services | +| QCI | QoS Class Identifier | +| RCAF | RAN Congestion Awareness Function | +| RUCI | RAN User Plane Congestion Information | +| SCEF | Service Capability Exposure Function | +| SDF | Service Data Flow | +| SLA | Spending Limit Answer | +| SLR | Spending Limit Request | +| SNA | Spending-Status Notification Answer | +| SSD | Source Statistics Descriptor | +| SNR | Spending-Status Notification Request | +| STA | Session Termination Answer | +| TSSF | Traffic Steering Support Function | +| STR | Session Termination Request | +| TDF | Traffic Detection Function | +| UDC | User Data Convergence | +| UDR | User Data Repository | +| V-AF | Visited AF | +| V-DRA | Visited DRA | +| V-PCRF | Visited PCRF | +| VPLMN | Visited PLMN | + +# --- 3a Reference architecture + +The PCC functionality is provided by the functions of the Policy and Charging Rules Function (PCRF), the Policy and Charging Enforcement Function (PCEF), the Bearer Binding and Event Reporting Function (BBERF), the Application Function (AF), the Traffic Detection Function (TDF), the Traffic Steering Support Function (TSSF), the RAN Congestion Awareness Function (RCAF), the Service Capability Exposure Function (SCEF), the Packet Flow Description Function (PFDF), the Online Charging System (OCS), the Offline Charging System (OFCS) and the Subscription Profile Repository (SPR) or the User Data Repository (UDR). UDR replaces SPR when the UDC architecture as defined in 3GPP TS 23.335 [51] is applied to store PCC related subscription data. In this deployment scenario Ud interface as defined in 3GPP TS 29.335 [52] between PCRF and UDR is used to access subscription data in the UDR. 3GPP TS 23.203 [2] specifies the PCC stage 2 functionality. + +![Overall PCC architecture for non-roaming scenario diagram](aa81b9b80bd1e3d723922b3a033564a2_img.jpg) + +The diagram illustrates the overall PCC architecture for a non-roaming scenario. At the top, four functional blocks are arranged horizontally: **RAN Congestion Awareness Function (RCAF)**, **Subscription Profile Repository (SPR)/ User Data Repository (UDR)**, **Application Function (AF)**, and **Service Capability Exposure Function (SCEF)**. These are connected to a central **Policy and Charging Rules Function (PCRF)** via interfaces **Np**, **Sp/Ud**, **Rx**, and **Nt** respectively. The **PCRF** is connected to an **Online Charging System (OCS)** via the **Sy** interface. Below the PCRF, there are three main components: **Bearer Binding and Event Reporting Function (BBERF)** (part of an **AN-Gateway**), **Policy and Charging Enforcement Function (PCEF)** (part of a **Gateway**), and **Traffic Detection Function (TDF)**. The **PCRF** connects to the **BBERF** via **Gxx**, to the **PCEF** via **Gx**, and to the **TDF** via **Sd**. The **TDF** is connected to a **Packet Flow Description Function (PFDF)** via **Gy**. The **PFDF** is connected to the **OCS** via **Gwn** and to an **Offline Charging System (OFCS)** via **Gzn**. The **PCEF** is connected to the **PFDF** via **Gw** and to the **OFCS** via **Gz**. Additionally, the **SCEF** is connected to the **PCRF** via **Nu**, and to a **Traffic Steering Support Function (TSSF)** via **St**. The **TSSF** is connected to the **PFDF** via **Gyn**. + +Overall PCC architecture for non-roaming scenario diagram + +Figure 3a.1: Overall PCC architecture for non-roaming scenario + +![Overall PCC architecture for roaming with home routed access scenario diagram showing VPLMN and HPLMN components and their interfaces.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +The diagram illustrates the Overall PCC architecture for a roaming with home routed access scenario, divided into two main domains: VPLMN (Visited PLMN) and HPLMN (Home PLMN). + +**VPLMN Components:** + +- RAN Congestion Awareness Function (RCAF)** +- Policy and Charging Rules Function (V-PCRF)** +- AN-Gateway** containing the **Bearer Binding and Event Reporting Function (BBERF)** + +**HPLMN Components:** + +- Application Function (AF)** +- Service Capability Exposure Function (SCEF)** +- Subscription Profile Repository (SPR)/User Data Repository (UDR)** (represented as a cylinder) +- Policy and Charging Rules Function (H-PCRF)** +- Packet Flow Description Function (PFDF)** +- Traffic Steering Support Function (TSSF)** +- Policy and Charging Enforcement Function (PCEF)** (part of the **Gateway**) +- Traffic Detection Function (TDF)** +- Online Charging System (OCS)** +- Offline Charging System (OFCS)** + +**Interfaces:** + +- Np**: Interface between RCAF and H-PCRF. +- S9**: Interface between V-PCRF and H-PCRF. +- Gxx**: Interface between V-PCRF and BBERF. +- Rx**: Interface between AF and H-PCRF. +- Nt**: Interface between SCEF and H-PCRF. +- Nu**: Interface between SCEF and PFDF. +- Sp/Ud**: Interface between SPR/UDR and PFDF. +- St**: Interface between H-PCRF and TSSF. +- Gx**: Interface between H-PCRF and PCEF. +- Sd**: Interface between H-PCRF and TDF. +- Gw**: Interface between H-PCRF and OCS. +- Gwn**: Interface between H-PCRF and OFCS. +- Gy**: Interface between PCEF and OCS. +- Gyn**: Interface between TDF and OCS. +- Gzn**: Interface between TDF and OFCS. +- Gz**: Interface between PCEF and OFCS. + +Overall PCC architecture for roaming with home routed access scenario diagram showing VPLMN and HPLMN components and their interfaces. + +Figure 3a.2: Overall PCC architecture for roaming with home routed access scenario + +![Figure 3a.3: Overall PCC architecture for roaming with visited access scenario. The diagram shows the interaction between various network functions in the VPLMN (Visited PLMN) and HPLMN (Home PLMN).](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +The diagram illustrates the overall PCC architecture for a roaming with visited access scenario, divided into VPLMN (Visited PLMN) and HPLMN (Home PLMN) by a vertical dashed line. + +- VPLMN (Visited PLMN):** + - RAN Congestion Awareness Function (RCAF)** connects to **Policy and Charging Rules Function (V-PCRF)** via the **Np** reference point. + - Application Function (AF)** connects to **V-PCRF** via the **Rx** reference point. + - Bearer Binding and Event Reporting Function (BBERF)** (part of **AN-Gateway**) connects to **V-PCRF** via the **Gxx** reference point. + - Policy and Charging Enforcement Function (PCEF)** (part of **Gateway**) connects to **V-PCRF** via the **Gx** reference point. + - Traffic Detection Function (TDF)** connects to **V-PCRF** via the **Sd** reference point. +- HPLMN (Home PLMN):** + - Application Function (AF)** connects to **Policy and Charging Rules Function (H-PCRF)** via the **Rx** reference point. + - Service Capability Exposure Function (SCEF)** connects to **H-PCRF** via the **Nt** reference point. + - Subscription Profile Repository (SPR)/User Data Repository (UDR)** connects to **H-PCRF** via the **Sp/Ud** reference point. + - Online Charging System (OCS)** connects to **H-PCRF** via the **Sy** reference point. + - Offline Charging System (OFCS)** connects to **H-PCRF** via the **Gy** reference point. +- Interconnections:** + - V-PCRF** and **H-PCRF** are connected via the **S9** reference point. + - H-PCRF** connects to **OCS** via the **Gyn** reference point. + - H-PCRF** connects to **OFCS** via the **Gzn** and **Gz** reference points. + +Figure 3a.3: Overall PCC architecture for roaming with visited access scenario. The diagram shows the interaction between various network functions in the VPLMN (Visited PLMN) and HPLMN (Home PLMN). + +**Figure 3a.3: Overall PCC architecture for roaming with visited access scenario** + +NOTE 1: The Sp reference point is located between PCRF and SPR, The Ud interface is located between PCRF and UDR. + +NOTE 2: The UDC Application Informational Model related to the PCRF is not specified in this Release. + +NOTE 3: AF can be located in both VPLMN and HPLMN for the visited access. + +NOTE 4: The H-PCRF can optionally send the addresses of the OCS to the V-PCRF in the visited access. + +NOTE 5: Use of TSSF in roaming scenarios is in this release only specified for the home routed access. + +NOTE 6: The SCEF acts as an AF (using Rx) in some service capability exposure use cases as described in 3GPP TS 23.682 [38]. + +NOTE 7: Gw and Gwn reference points are not supported in the visited access. + +NOTE 8: The PCEF and TDF can each be decomposed into a User Plane Function and a Control Plane Function connected via the Sx reference point specified in 3GPP TS 29.244 [65]. + +The protocols for the Gx reference point, the Gxx reference point and the Sd reference point are specified in 3GPP TS 29.212 [9]. + +The protocols for the St reference point are specified in 3GPP TS 29.212 [9] and 3GPP TS 29.155 [54]. + +The protocols for the Rx reference point are specified in 3GPP TS 29.214 [10] and 3GPP TS 29.201 [53]. + +The protocol for the S9 reference point is specified in 3GPP TS 29.215 [22]. + +The protocol for the Sy reference point is specified in 3GPP TS 29.219 [28]. + +The protocol for the Np reference point is specified in 3GPP TS 29.217 [36]. + +The protocol for the Nt reference point is specified in 3GPP TS 29.154 [56]. + +The protocol for the Nu reference point is specified in 3GPP TS 29.250 [62]. + +The protocols for the Gw and Gwn reference points are specified in 3GPP TS 29.251 [63]. + +More information about the protocols on the Gy reference point, the Gyn reference point, the Gz reference point and the Gzn reference point are provided in 3GPP TS 32.240 [55]. + +The details associated with the Sp reference point are not specified in this Release. The SPR's relation to existing subscriber databases is not specified in this Release. + +The UDR replaces the SPR when the UDC architecture as defined in 3GPP TS 23.335 [51] is applied to store PCC related subscription data. In this deployment scenario Ud interface as defined in 3GPP TS 29.335 [52] between PCRF and UDR is used to access subscription data in the UDR. + +# --- 4 Signalling Flows over Gx, Gxx, Rx, Sd, Sy, Np, Nt, St and S9 + +## 4.0 General + +There are three distinct network scenarios for an IP-CAN Session: + +Case 1. No Gateway Control Session is required, no Gateway Control Establishment occurs at all (e.g. 3GPP Access where GTP-based S5/S8 are employed, and Non-3GPP access where GTP-based S2a or GTP-based S2b is employed). + +Case 2. A Gateway Control Session is required. There are two subcases: + +2a) The BBERF assigns a Care of Address (CoA) to the UE and establishes a Gateway Control Session prior to any IP-CAN session establishment that will apply for all IP-CAN sessions using that CoA. + +2b) At IP-CAN session establishment a Gateway Control Session is required before the PCEF announces the IP-CAN Session to the PCRF. At BBERF change and pre-registration the Gateway Control Session shall match an IP-CAN session that the PCEF has already announced. Each IP-CAN session is handled in a separate Gateway Control Session. + +The PCRF shall select whether case 2a or case 2b applies based on the information received in the Gateway Control Session Establishment. For a user identified with a Subscription-Id AVP, when the PDN identifier included as part of the Called-Station-Id AVP is received, case 2b applies. If not received, case 2a applies. + +The following considerations shall be taken into account when interpreting the signalling flows: + +- V-PCRF is included to also cover the roaming scenarios. +- H-PCRF will act as a PCRF for non-roaming Ues. +- The steps numbered as “number+letter” (e.g. “3a”) will be executed, for the roaming case, instead of steps numbered as “number” (e.g. “3”), as indicated in the explanatory text below the signalling flows. +- Emergency services and RLOS are handled locally in the serving network, therefore the S9 reference point does not apply. + +NOTE: For the Visited Access case, the operator can by roaming agreement decide not to use S9 reference point. + +The procedure to detect that the Gx session or a Gateway Control Session is restricted to Emergency Services is described in 3GPP TS 29.212 [9]. + +- The procedure to detect that the Gx session is restricted to RLOS is described in 3GPP TS 29.212 [9]. +- Subscription-related information is not relevant for the policy control of Emergency Sessions and RLOS; therefore Sp reference point does not apply in that case. +- With the UDC-based architecture as defined in 3GPP TS 23.203 [2] and 3GPP TS 23.335 [51], SPR, whenever mentioned in the present specification, refers to UDR. The Ud interface as defined in 3GPP TS 29.335 [52] is the interface between the PCRF and the UDR. +- When monitoring event reporting via PCRF applies as defined in 3GPP TS 23.682 [38], the SCEF is acting as an AF. In this case, only the flows where the AF is located in the home network apply. Support of this functionality is detailed in 3GPP TS 29.214 [10], Annex D. +- If the PCEF/BBERF/TDF needs to send an IP-CAN session/ Gateway Control Session/ TDF session modification request towards a PCRF which is known to have restarted since the IP-CAN session/ Gateway Control Session/ TDF session establishment, the PCEF/BBERF/TDF shall follow the PCRF Failure and Restoration procedure as defined in 3GPP TS 29.212 [9]. + +NOTE: Only the interaction with OCS for spending limits reporting over Sy interface is introduced in this document. + +- The PCEF and TDF are depicted as monolithic entities in the signalling flows, but each of those can be decomposed into a User Plane Function and a Control Plane Function connected via the Sx reference point. Signalling on the Sx reference point is not shown. + +## 4.1 IP-CAN Session Establishment + +This subclause is applicable if a new IP-CAN Session is being established. + +![Sequence diagram for IP-CAN Session Establishment showing interactions between BBERF, PCEF, TDF, TSSF, V-PCRF, H-PCRF, SPR, and OCS. The diagram is divided into two 'VISITED ACCESS CASE' sections. It details steps like Gateway Control Session Establishment, IP-CAN Session Request, Diameter CCR/CCA messages, Profile Requests/Responses, Spending Limit Reports, PCC/ADC Rules Decisions, and TDF/St session establishments.](e6df2733626a85205c1db682e6259c46_img.jpg) + +The sequence diagram illustrates the IP-CAN Session Establishment process. The lifelines involved are BBERF, PCEF, TDF, TSSF, V-PCRF, H-PCRF, SPR, and OCS. The process is organized into two 'VISITED ACCESS CASE' blocks. + +- 1. Gateway Control Session Establishment (case 2a and 2b):** Initiated by BBERF. +- 2. Establish IP-CAN Session:** BBERF sends a Request to PCEF. +- 3. Diameter CCR:** PCEF sends to TDF, which then sends to V-PCRF. +- 3b. Store Information:** V-PCRF stores information. +- 3c. Diameter CCR:** V-PCRF sends to H-PCRF. +- 4. Store Information:** H-PCRF stores information. +- 5. Profile Request / 6. Profile Response:** H-PCRF sends a Profile Request to SPR, which responds. +- 7. Initial/intermediate Spending Limit Report Request:** H-PCRF sends to OCS. +- 8. PCC Rules Decision; Policy Decision:** OCS makes a decision. +- 9. Store PCC Rules:** OCS stores rules. +- 10. ADC Rules Decision; Store ADC Rules:** OCS makes another decision. +- 11. TDF session establishment:** TDF initiates session establishment. +- 12. St session establishment:** TSSF initiates session establishment. +- 13. Diameter CCA:** TDF sends CCA to PCEF. +- 13a. Diameter CCA:** V-PCRF sends CCA to H-PCRF. +- 13b. Policy Enforcement:** V-PCRF enforces policy. +- 13c. Store ADC Rules; Policy Decision:** V-PCRF stores rules. +- 13d. Diameter CCR:** V-PCRF sends CCR to H-PCRF. +- 13e. Diameter CCA:** V-PCRF sends CCA to H-PCRF. +- 13f. TDF session establishment:** TDF completes session establishment. +- 13g. Diameter CCA:** TDF sends CCA to PCEF. +- 14. Gateway Control and QoS Rules Provision (case 2a and 2b):** BBERF initiates rules provision. +- 15. Install PCC Rules, Policy Enforcement:** BBERF installs rules. +- 16. Establish IP-CAN session Response:** BBERF sends response to PCEF. + +Sequence diagram for IP-CAN Session Establishment showing interactions between BBERF, PCEF, TDF, TSSF, V-PCRF, H-PCRF, SPR, and OCS. The diagram is divided into two 'VISITED ACCESS CASE' sections. It details steps like Gateway Control Session Establishment, IP-CAN Session Request, Diameter CCR/CCA messages, Profile Requests/Responses, Spending Limit Reports, PCC/ADC Rules Decisions, and TDF/St session establishments. + +**Figure 4.1.1: IP-CAN Session Establishment** + +1. The BBERF may initiate a Gateway Control Session Establishment procedure as defined in subclause 4.4.1 (applicable for cases 2a during initial attach and 2b, as defined in subclause 4.0), if appropriate. In this step, the PCRF determines whether the cases 2a or 2b applies, as defined in subclause 4.0. +2. The PCEF receives an Establish IP-CAN Session Request. The form of the Establish IP-CAN Session Request depends upon the type of the IP-CAN. + +3. For the non-roaming case, and for the case when the UE is roaming in a Home Routed scenario, the PCEF informs the H-PCRF of the IP-CAN Session establishment. The PCEF starts a new Gx session by sending a CCR to the H-PCRF using the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The PCEF provides UE identity information, PDN identifier, the UE Ipv4 address and/or UE Ipv6 prefix and, if available, the PDN connection identifier, IP-CAN type, RAT type and/or the default charging method and additional charging parameters as defined in subclause 4.5.1 of 3GPP TS 29.212 [9] and may send charging characteristics if available. The PCEF provides, when available, the Default-EPS-Bearer-QoS and the APN-AMBR to the PCRF. The PCEF may provide the applicable TDF routing information in TDF-Information AVP. If the UE has declared support for the extended TFT filter format and the PCEF does not prevent the use thereof, the PCEF shall indicate that the support for extended TFT filters is available in the IP-CAN session. For types of IP-CAN, where the H-PCRF can be in control of IP-CAN Bearers, e.g. GPRS, the PCEF also provides a new bearer identifier and information about the requested bearer, such as QoS. If applicable for the IP-CAN type, it will also provide information to indicate whether NW-initiated bearer control procedures are supported, if available. The PCRF links the Gx session for the new IP-CAN session with the corresponding Gateway Control Session as defined in subclause 4.0. The PCRF maintains aligned set of PCC and QoS rules in the PCEF and BBERF(s) as applicable for the case. For case 2a and if IP flow mobility is supported, the PCEF provides, when available, the IP flow mobility routing rules. For case 1 and if NBIFOM is supported, the PCEF provides, when available, the NBIFOM support and NBIFOM mode information. If available, the PCEF provides a timestamp corresponding to the time at which the request was initiated by the originating node, and additionally the PCEF can include the maximum wait time as defined in subclause 4.5.1 of 3GPP TS 29.212 [9]. + +For the case when the UE is roaming in a Visited Access scenario, steps 3a~3c are executed instead of step 3. + +- 3a. The PCEF informs the V-PCRF of the establishment of the IP-CAN session. The PCEF starts a new Gx session by sending a CCR to the V-PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The parameters for CCR as listed in step 3 are applicable here. +- 3b. The V-PCRF determines that the request is for a roaming user and concludes the IP-CAN session uses visited access. V-PCRF stores the received information. +- 3c. If there is not an already established S9 session for this roaming user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this IP-CAN session within the Subsession-Id AVP, and the Subsession-Operation AVP set to the value ESTABLISHMENT. + +If there is an already established S9 session for this roaming user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this IP-CAN session within the Subsession-Id AVP, and the Subsession-Operation AVP set to the value ESTABLISHMENT. + +4. The H-PCRF stores the information received in the CCR. For cases 2a and 2b, the H-PCRF links the Gx session with the Gateway Control Session(s). + +NOTE 1: In the case 2a, when an additional PDN connection is established, the Gx session is linked with the already established Gateway Control Session. + +5. If the H-PCRF requires subscription-related information and does not have it, the H-PCRF sends a request to the SPR in order to receive the information. +6. The SPR replies with the subscription related information containing the information about the allowed service(s), QoS information, PCC Rules information and may include MPS EPS Priority, MPS Priority Level and IMS Signalling Priority for establishing a PS session with priority. + +NOTE 2: For steps 5 and 6: The details associated with the Sp reference point are not specified in this Release. The SPR's relation to existing subscriber databases is not specified in this Release. + +7. If the PCRF determines that the policy decision depends on the status of the policy counters available at the OCS and no Sy session yet has been established for this subscriber, the PCRF sends an Initial Spending Limit Report Request as defined in subclause 4.7.1. If the Sy session is already established for this subscriber, the PCRF may send, if required, an Intermediate Spending Limit Report Request as defined in subclause 4.7.2. + +8. The H-PCRF selects or generates PCC Rule(s) to be installed. The H- PCRF may also make a policy decision by deriving an authorized QoS and by deciding whether service flows described in the PCC Rules are to be enabled or disabled. If MPS EPS Priority, MPS Priority Level, and IMS Signalling Priority are present for the user, the PCRF takes the information into account. If NBIFOM is supported, the PCRF determines whether the NBIFOM applies to the IP-CAN session and selects the NBIFOM mode. +9. The H-PCRF stores the selected PCC Rules. The H-PCRF selects the Bearer Control Mode that will apply during the IP-CAN session if applicable for the particular IP-CAN. If the H-PCRF controls the binding of IP-CAN Bearers, the H-PCRF stores information about the IP-CAN Bearer to which the PCC Rules have been assigned. If the BBERF/PCEF controls the binding of IP-CAN bearers, the H-PCRF may derive the QoS information per QCI applicable to that IP-CAN session for non-GBR bearers. +10. When user profile configuration indicates that Application Detection and Control function is enabled, the H-PCRF makes the policy decision for the application detection and control. For the non-roaming case, or for the case when the UE is roaming in a Home Routed scenario, the H-PCRF selects the applicable PCC Rules to be provided for application detection and control for the PCEF supporting ADC feature, or the applicable ADC rules for the solicited application reporting with a TDF. For the case when the UE is roaming in a Visited Access scenario, the H-PCRF selects the applicable PCC Rules to be provided for application detection and control. For solicited application reporting with a TDF, the H-PCRF finds the TDF by using the TDF-Information AVP received from the PCEF in step 3, or, if not received, using a pre-configured TDF address. +11. Only applicable for non-roaming case, and for the case when the UE is roaming in a home routed case, In case of solicited application reporting with a TDF, the PCRF initiates a TDF Session Establishment procedure, according to subclause 4.6.1, with the selected TDF. +12. If traffic steering control over St applies and the H-PCRF determines that traffic steering control information is needed for the IP-CAN session, the PCRF initiates an St session establishment procedure according to subclause 4.9.1 with the TSSF. The TSSF identifier is pre-configured on the PCRF per e.g. PCEF. +13. For the non-roaming case, and for the case when the UE is roaming in a Home Routed scenario, the H-PCRF provisions the PCC Rules to the PCEF using CCA. The H-PCRF also provides the selected Bearer Control Mode if applicable for the particular IP-CAN and if available, the QoS information per QCI. If the PCEF has indicated that the support for extended TFT filters is available in the IP-CAN session, then the PCRF may, by indicating the PCRF support for extended TFT filters, enable the use of the extended TFT filter format in the IP-CAN session. The PCRF may also provide event triggers listing events for which the PCRF desires PCC Rule Requests. Furthermore, the PCRF may provide authorized QoS including the APN-AMBR and the Default-EPS-Bearer-QoS, User Location Information, user CSG information (if received from the BBERF) and Presence Reporting Area Information. If usage monitoring is enabled, the H-PCRF may provide the applicable thresholds for usage monitoring control at PCEF within the Usage-Monitoring-Information AVP. If NBIFOM is supported, the H-PCRF provides the decision on whether the NBIFOM is supported and the selected NBIFOM mode if applicable. + +For types of IP-CAN, where the PCRF controls IP-CAN Bearers, e.g. GPRS, the PCRF indicates the IP-CAN Bearer where the PCC Rules are to be installed and that the authorized QoS refers to. Otherwise, the PCRF operates without any further reference to any specific bearer. + +If the PCEF supports Application Detection and Control feature, the PCRF provisions the applicable PCC Rules to the PCEF for the corresponding IP-CAN session. + +If online charging is applicable then the PCEF requests credit information from the OCS over the Gy interface. If the PCEF receives credit re-authorisation triggers from the OCS then, for case 2b, it requests the PCRF via a CCR message to provision the triggers at the BBERF. The triggers to be provisioned are specified in the Event-Report-Indication AVP in the CCR message. + +For the case when the UE is roaming in a Visited Access scenario, steps 13a -13g are executed. + +- 13a. The PCC Rules, if they were selected in step 9, are provisioned by the H-PCRF to the V-PCRF by using a CCA. The H-PCRF includes PCC Rules in the Subsession-Decision-Info AVP of the CCA, along with the S9 subsession identifier as received in step 3c within the Subsession-Id AVP. Other parameters listed in step 9 are also applicable here. +- 13b. The V-PCRF enforces visited operator policies regarding QoS authorization requested by the H-PCRF as indicated by the roaming agreements. + +- 13c. In case of TDF, if Application Detection and Control function is enabled for the IP-CAN session, the V-PCRF extracts ADC rules from the received PCC rules from the H-PCRF and stores the ADC rules. +- 13d. The V-PCRF informs the H-PCRF when a request has been denied and may provide the acceptable QoS Information for the service. +- 13e. The H-PCRF acknowledges the CCR and may additionally include new or modified PCC rules to the V-PCRF. When user profile configuration indicates that Application Detection and Control function is enabled, some of those PCC Rules may be dedicated for application detection and control. +- 13f. In case of solicited application reporting with a TDF, the V-PCRF initiates a TDF Session Establishment procedure, according to subclause 4.6.1, with the selected TDF and provides ADC Rules extracted from the corresponding PCC Rules. +- 13g. The V-PCRF provisions PCC rules received from the H-PCRF to the PCEF by using CCA. The parameters listed in step 11a are applicable here, User Location Information and user CSG information (if received from the BBERF). + +NOTE 3: From this point and onward, the PCRF is responsible for keeping the active PCC, ADC and QoS rules aligned. + +- 14. If case 2a or 2b applies, the PCRF aligns the set of QoS rules at the BBERF with the set of active rules at the PCEF. +- 15. The PCEF installs the received PCC Rules. The PCEF also enforces the authorized QoS and enables or disables service flows according to the flow status of the corresponding PCC Rules. If QoS information is received per QCI, PCEF sets the upper limit accordingly for the MBR that the PCEF assigns to the non-GBR bearer(s) for that QCI. In case of PCEF supporting Application Detection and Control feature, the PCEF enforces the application detection and control. +- 16. The PCEF sends a response to the Establish IP-CAN Session Request. +For GPRS, the GGSN accepts the PDP Context Request based on the results of the authorisation policy decision enforcement. If the requested QoS parameters do not correspond to the authorized QoS, the GGSN adjusts (downgrades /upgrades) the requested UMTS QoS parameters to the authorized values. + +NOTE 4: The PCRF can reject the IP-CAN session establishment, e.g. the PCRF cannot obtain the subscription-related information from the SPR and the PCRF cannot make the PCC rule decisions, as described in 3GPP TS 29.212 [9]. + +PCEF can also enforce active preconfigured PCC rules which are not known to the PCRF. + +The PCEF can also reject the IP-CAN session establishment, e.g. there is no active PCC rule for the IP-CAN session as specified in 3GPP TS 23.203 [2]. + +## 4.2 IP-CAN Session Termination + +### 4.2.1 UE-Initiated + +#### 4.2.1.1 AF located in the HPLMN + +This clause is applicable if an IP-CAN Session is being released by the UE and the AF is located in the HPLMN. + +![Sequence diagram for UE-Initiated IP-CAN Session Termination – AF located in the HPLMN. The diagram shows interactions between BBERF, PCEF, RCAF, TDF, TSSF, V-PCRF, H-PCRF, H-AF, SPR, and OCS. It is divided into two 'VISITED ACCESS CASE' sections. The process involves removing the IP-CAN session, terminating gateway control sessions, Diameter CCR/CCA exchanges, TDF session termination for roaming UEs, UE context removal, AF session identification, final spending limit reports, and PCRF-initiated gateway control session termination.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The sequence diagram illustrates the interaction for UE-Initiated IP-CAN Session Termination where the AF is located in the HPLMN. The lifelines are BBERF, PCEF, RCAF, TDF, TSSF, V-PCRF, H-PCRF, H-AF, SPR, and OCS. The process is as follows: + +- 1. Remove IP-CAN Session Request**: BBERF sends a request to PCEF. +- 2. BBERF-initiated Gateway Control Session Termination (case 2b)**: BBERF initiates this procedure. +- 3. Diameter CCR**: PCEF sends a CCR to H-PCRF. +- 3a. Diameter CCR**: PCEF sends a CCR to V-PCRF (Visited Access Case). +- 3b. TDF session termination for roaming UE with visited access**: Conditional message from V-PCRF to TDF. +- 3c. UE context removal**: Conditional message from V-PCRF to TSSF. +- 3d. Diameter CCR**: V-PCRF sends a CCR to H-PCRF. +- 4. Identify AF Sessions bound to the removed IP-CAN Session**: H-PCRF sends this message to H-AF. +- 5. Diameter CCA**: H-PCRF sends a CCA to PCEF. +- 5a. Diameter CCA**: H-PCRF sends a CCA to V-PCRF (Visited Access Case). +- 5b. removes the information related to the terminated IP-CAN Session**: V-PCRF performs internal processing. +- 5c. Diameter CCA**: V-PCRF sends a CCA to PCEF. +- 6. Remove IP-CAN Session Response**: PCEF sends a response to BBERF. +- 7. TDF session termination for roaming UE with home-routed access**: Conditional message from H-PCRF to TDF. +- 8. UE context removal**: Conditional message from H-PCRF to TSSF. +- 9. Diameter ASR**: H-PCRF sends an ASR to H-AF for each affected AF session. +- 10. Diameter ASA**: H-AF sends an ASA to H-PCRF. +- 11. Diameter STR**: H-PCRF sends an STR to H-AF. +- 12. Diameter STA**: H-AF sends a STA to H-PCRF. +- 13. Final Spending Limit Report Request/Intermediate Spending Limit Report Request**: H-PCRF sends this message to OCS. +- 14. Gateway Control and Qos Rules provision (case 2a) Or PCRF-initiated Gateway Control Session Termination (case 2a)**: H-PCRF initiates this procedure. +- 15. Cancel Subscribed Notification request**: H-PCRF sends this message to SPR. +- 16. Cancel Subscribed Notification Response**: SPR sends a response to H-PCRF. +- 17. St session termination**: Conditional message from H-PCRF to TSSF. + +**Legend:** + +- Mandatory**: Solid line with arrowhead +- Conditional**: Dashed line with arrowhead + +Sequence diagram for UE-Initiated IP-CAN Session Termination – AF located in the HPLMN. The diagram shows interactions between BBERF, PCEF, RCAF, TDF, TSSF, V-PCRF, H-PCRF, H-AF, SPR, and OCS. It is divided into two 'VISITED ACCESS CASE' sections. The process involves removing the IP-CAN session, terminating gateway control sessions, Diameter CCR/CCA exchanges, TDF session termination for roaming UEs, UE context removal, AF session identification, final spending limit reports, and PCRF-initiated gateway control session termination. + +**Figure 4.2.1.1.1: UE-Initiated IP-CAN Session Termination – AF located in the HPLMN** + +In the following procedures, the V-PCRF is included to depict the roaming scenarios. H-PCRF acts as the PCRF for non-roaming UEs. + +- If case 2b applies (as defined in clause 4.0), the BBERF receives a request to remove the IP-CAN session. In case 2a, the request goes transparently through the BBERF. In all cases, the PCEF receives a request to remove the IP-CAN Session. The form of the Remove IP-CAN Session Request depends upon the type of the IP-CAN. +- If case 2b applies (as defined in clause 4.0), the BBERF-initiated Gateway Control Session Termination procedure as defined in clause 4.4.4 (BBERF-Initiated Gateway Control Session Termination) is initiated. + +3. For the non-roaming case, and for the case when the UE is roaming in a Home Routed scenario, the PCEF sends a CCR to the H-PCRF, indicating the IP-CAN Session termination. The PCEF requests the termination of the Gx session using the CC-Request-Type AVP set to the value TERMINATION\_REQUEST. If the usage monitoring is enabled, the PCEF informs the H-PCRF about the resources that have been consumed by the user since the last report. If the Required-Access-Info AVP is included in any PCC Rule, the PCEF informs the H-PCRF about the access network information. If NAS-RAN-Cause feature is supported the PCEF informs the H-PCRF about the access network information and the failure cause(s), if available. + +For the case when the UE is roaming in a Visited Access scenario, steps 3a~3b are executed instead of step 3: + +- 3a. The PCEF sends a CCR to the V-PCRF, indicating the IP-CAN Session termination. The PCEF requests the termination of the Gx session using the CC-Request-Type AVP set to the value TERMINATION\_REQUEST. If the usage monitoring is enabled, the PCEF informs the V-PCRF about the resources that have been consumed by the user since the last report. If the Required-Access-Info AVP is included in any PCC Rule, the PCEF informs the V-PCRF about access network information. +- 3b If there is an active TDF session between the TDF and the V-PCRF, for roaming UE with visited access, the TDF Session termination is initiated as defined in Section 4.6.2. For this case, the PCRF described in Section 4.6.2 acts as a V-PCRF. +- 3c. If congestion reporting is active for the user id and PDN id, for roaming UE with visited access, the V-PCRF initiates a UE context removal as defined in clause 4.8.5. +- 3d. The V-PCRF sends the CCR to the H-PCRF. If case 2b or case 1 applies and this is the last subsession associated with the S9 session, the V-PCRF sends a CCR to the H-PCRF to request the termination of the S9 session using the CC-Request-Type AVP set to the value TERMINATION\_REQUEST. Otherwise, the V-PCRF sends a CCR to the H-PCRF with a CC-Request-Type AVP set to the value UPDATE\_REQUEST and a Subsession-Enforcement-Info within which the Subsession-Operation AVP set to value TERMINATION to request the termination of the corresponding S9 subsession. + +NOTE 1: If the usage monitoring is enabled on PCEF and/or TDF, the V-PCRF gathers the reports and provides them all to H-PCRF in the single CCR message. + +4. The H-PCRF identifies the AF sessions that are bound to IP flows of the removed IP-CAN Session. +5. For the non-roaming case, and for the case when the UE is roaming in a Home Routed scenario, the H-PCRF acknowledges the Gx session termination by sending a CCA to the PCEF. + +For the case when the UE is roaming in a Visited Access scenario, steps 5a~5c are executed instead of step 5: + +- 5a. The H-PCRF acknowledges the S9 session or subsession termination by sending a CCA to the V-PCRF. + - 5b. The V-PCRF removes the information related to the terminated IP-CAN Session. + - 5c. The V-PCRF acknowledges the Gx session termination by sending a CCA to the PCEF. +6. The PCEF sends a response to the Remove IP-CAN Session Request. The form of the Remove IP-CAN Session Response depends upon the type of the IP-CAN. Step 6 may be executed in parallel with step 3 or 3a (as applicable). + 7. If there is an active TDF session between the TDF and the H-PCRF, for non-roaming UE/roaming UE with home routed access, the TDF Session termination is initiated as defined in Section 4.6.2. + +NOTE 2: Step 7 can occur anytime after step 3. + +For each AF session identified in step 4 as bound to the IP-CAN Session being removed, steps 7-11 are executed: + +8. If congestion reporting is active for the user id and PDN id, for non-roaming UE or UE is roaming in home routed case, the H-PCRF initiates a UE context removal as defined in clause 4.8.5. + +NOTE 3: Step 8 can occur anytime after step 3. + +9. The H-PCRF indicates the session abort to the H-AF by sending an ASR to the H-AF. +10. The H-AF responds by sending an ASA to the H-PCRF. + +11. The H-AF sends an STR to the H-PCRF to indicate that the session has been terminated. +12. The H-PCRF responds by sending an STA to the H-AF. If the provided PCC rules are related to an AF session associated with a sponsor, usage thresholds were provided by the H-AF earlier, and the H-PCRF has usage data that has not yet been reported to the H-AF, the H-PCRF informs the H-AF about the resources that have been consumed by the user since the last report. If the BBERF in step 2 or PCEF in step 3 reports the access network information and if the AF requested the H-PCRF to report access network information previously and/or the RAN-NAS-Cause feature is supported, the H-PCRF informs the H-AF about the access network information and/or RAN/NAS/TWAN/Untrusted WLAN failure cause(s) if available. +13. If this is the last IP-CAN session for this subscriber the Final Spending Limit Report Request as defined in clause 4.7.3 is sent. If any existing IP-CAN sessions for this subscriber require policy counter status reporting, the Intermediate Spending Limit Report Request as defined in clause 4.7.2 can be sent to alter the list of subscribed policy counters. +14. If case 2a applies (as defined in clause 4.0), the Gateway Control and QoS Rules Provision procedure as defined in clause 4.4.3 (Gateway Control and QoS Rules Provision) may be initiated to remove the QoS rules associated with the IP-CAN session being terminated. This applies e.g. in case the Gateway Control Session remains to serve other IP-CAN sessions. + +Alternatively, if UE acquires a care of address (CoA) that is used for the S2c reference point and the H-PCRF determines that all QoS rules are to be removed and the Gateway Control Session to be terminated, the PCRF-initiated Gateway Control Session Termination procedure as defined in clause 4.4.4 (PCRF-Initiated Gateway Control Session Termination) is initiated. This applies e.g. in case the UE is detached and the CoA acquired by the UE is not used for any other IP-CAN session. + +15. The H-PCRF sends a cancellation notification request to the SPR if it has subscribed such notification. The H-PCRF stores the remaining usage allowance in the SPR if all IP-CAN sessions of the user to the same APN are terminated. Step 14 may be initiated any time after step 5 or 5a (as applicable). +16. The SPR sends a response to the H-PCRF. + +NOTE 4: For steps 14 and 15: The details associated with the Sp reference point are not specified in this Release. The SPR's relation to existing subscriber databases is not specified in this Release. + +17. If the H-PCRF has provided traffic steering control information to the TSSF for the IP-CAN session, the H-PCRF initiates the St session termination procedure to the TSSF to remove the traffic steering control information associated to the UE IPv4 address and/or to the UE IPv6 prefix for the terminated IP-CAN session according to the subclause 4.9.3. + +NOTE 5: Step 17 can be initiated any time after step 5. + +#### 4.2.1.2 AF located in the VPLMN + +This clause is applicable only for the Visited Access scenario for the case when an IP-CAN Session is being released by the UE and the AF is located in the VPLMN. + +![Sequence diagram for UE-Initiated IP-CAN Session Termination – AF located in the VPLMN. Lifelines: BBERF, PCEF, V-PCRF, H-PCRF, V-AF, SPR. The process starts with Step 1 (UE Initiated IP-CAN Session Termination - AF Located in the HPLMN). A 'VISITED ACCESS CASE' box highlights steps 2-9. Step 2: H-PCRF sends Diameter ASR to V-PCRF. Step 3: V-PCRF proxies ASR to V-AF. Step 4: V-AF sends Diameter ASA to V-PCRF. Step 5: V-PCRF proxies ASA to H-PCRF. Step 6: V-AF sends Diameter STR to V-PCRF. Step 7: V-PCRF proxies STR to H-PCRF. Step 8: V-AF sends Diameter STA to V-PCRF. Step 9: V-PCRF proxies STA to H-PCRF. A bracket on the right indicates steps 2-9 are 'For each affected AF session (if any)'. Step 10: UE Initiated IP-CAN Session Termination - AF Located in the HPLMN. Legend: Solid arrow = Mandatory, Dashed arrow = Conditional.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Sequence diagram illustrating UE-Initiated IP-CAN Session Termination – AF located in the VPLMN. + +The diagram shows interactions between BBERF, PCEF, V-PCRF, H-PCRF, V-AF, and SPR. + +Step 1: Perform Step 1 through Step 8: as specified in Figure 4.2.1.1.1 : UE Initiated IP-CAN Session Termination - AF Located in the HPLMN + +Step 2: Diameter ASR (Conditional) from H-PCRF to V-PCRF + +Step 3: Diameter ASR (Conditional) from V-PCRF to V-AF + +Step 4: Diameter ASA (Conditional) from V-AF to V-PCRF + +Step 5: Diameter ASA (Conditional) from V-PCRF to H-PCRF + +Step 6: Diameter STR (Conditional) from V-AF to V-PCRF + +Step 7: Diameter STR (Conditional) from V-PCRF to H-PCRF + +Step 8: Diameter STA (Conditional) from V-AF to V-PCRF + +Step 9: Diameter STA (Conditional) from V-PCRF to H-PCRF + +For each affected AF session (if any) + +Step 10: Perform Step 13 through Step 16: as specified in Figure 4.2.1.1.1 : UE Initiated IP-CAN Session Termination - AF Located in the HPLMN + +Legend: + +- Mandatory (Solid arrow) +- Conditional (Dashed arrow) + +Sequence diagram for UE-Initiated IP-CAN Session Termination – AF located in the VPLMN. Lifelines: BBERF, PCEF, V-PCRF, H-PCRF, V-AF, SPR. The process starts with Step 1 (UE Initiated IP-CAN Session Termination - AF Located in the HPLMN). A 'VISITED ACCESS CASE' box highlights steps 2-9. Step 2: H-PCRF sends Diameter ASR to V-PCRF. Step 3: V-PCRF proxies ASR to V-AF. Step 4: V-AF sends Diameter ASA to V-PCRF. Step 5: V-PCRF proxies ASA to H-PCRF. Step 6: V-AF sends Diameter STR to V-PCRF. Step 7: V-PCRF proxies STR to H-PCRF. Step 8: V-AF sends Diameter STA to V-PCRF. Step 9: V-PCRF proxies STA to H-PCRF. A bracket on the right indicates steps 2-9 are 'For each affected AF session (if any)'. Step 10: UE Initiated IP-CAN Session Termination - AF Located in the HPLMN. Legend: Solid arrow = Mandatory, Dashed arrow = Conditional. + +**Figure 4.2.1.2.1: UE-Initiated IP-CAN Session Termination – AF located in the VPLMN** + +If the AF resides in the VPLMN, the V-PCRF proxies AF session signalling over S9 between the V-AF and the H-PCRF. + +- 1 In order to perform UE initiated IP-CAN Session Termination Procedures, step 1 through step 8: as specified in Figure 4.2.1.1.1: UE Initiated IP-CAN Session Termination – AF Located in the HPLMN are executed. + +For each AF session identified in step 4 (Figure 4.2.1.1.1) as bound to the IP-CAN Session being removed steps 2-10 are executed: + +2. The H-PCRF indicates the session abort to the V-AF in VPLMN by sending an ASR to the V-PCRF. +3. The V-PCRF proxies the ASR to the V-AF. +4. The V-AF responds by sending an ASA to the V-PCRF. +5. The V-PCRF proxies the ASA to the H-PCRF. +6. The V-AF sends an STR to the V-PCRF to indicate that the session has been terminated. +7. The V-PCRF proxies the STR to the H-PCRF. +8. The H-PCRF responds by sending an STA to the V-PCRF. + +9. The V-PCRF proxies the STA to the V-AF. + +10. Step 13 through step 16: as specified in Figure 4.2.1.1.1: UE Initiated IP-CAN Session Termination – AF Located in the HPLMN are executed, as needed. + +NOTE: For steps 15 and 16: the details associated with the Sp reference point are not specified in this Release. The SPR's relation to existing subscriber databases is not specified in this Release. + +### 4.2.2 PCEF-Initiated + +#### 4.2.2.1 AF located in the HPLMN + +This clause is applicable if an IP-CAN Session is being released by the PCEF and the AF is located in the HPLMN. + +![Sequence diagram for PCEF-initiated IP-CAN Session Termination. Lifelines: BBERF, PCEF, RCAF, TDF, TSSF, V-PCRF, H-PCRF, H-AF, SPR, OCS. The diagram shows the interaction between these elements for session termination, with specific steps for visited and home access cases.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The sequence diagram illustrates the PCEF-initiated IP-CAN Session Termination process. The lifelines involved are BBERF, PCEF, RCAF, TDF, TSSF, V-PCRF, H-PCRF, H-AF, SPR, and OCS. The process is divided into two main scenarios: 'VISITED ACCESS CASE' and 'non-roaming UE/roaming UE with home routed access'. + +**Sequence of Messages:** + +- Detection that IP-CAN Session Termination is required (PCEF internal step). +- Remove IP-CAN Session Request (PCEF to BBERF). +- BBERF-initiated Gateway Control Session Termination (case 2b) (BBERF to PCEF, conditional). +- Remove IP-CAN Session Response (BBERF to PCEF). +- Diameter CCR (PCEF to H-PCRF). +- Diameter CCA (H-PCRF to PCEF). +- For the 'VISITED ACCESS CASE': + - 5a. Diameter CCR (PCEF to V-PCRF). + - 5b. TDF session termination for roaming UE with visited access (V-PCRF to TDF, conditional). + - 5c. UE context removal (V-PCRF to TSSF, conditional). + - 5d. Diameter CCR (V-PCRF to H-PCRF). + - 6. Identify AF Sessions bound to the removed IP-CAN Session (H-PCRF to H-AF). + - 7a. Diameter CCA (H-PCRF to V-PCRF). + - 7b. Removes the information related to the terminated IP-CAN Session (H-AF internal step). + - 7c. Diameter CCA (V-PCRF to PCEF). +- For the 'non-roaming UE/roaming UE with home routed access' case: + - 8. TDF session termination for non-roaming UE/roaming UE with home routed access (PCEF to TDF, conditional). + - 9. UE context removal (PCEF to TSSF, conditional). + - 10. Diameter ASR (H-PCRF to H-AF, for each affected AF session if any). + - 11. Diameter ASA (H-AF to H-PCRF, for each affected AF session if any). + - 12. Diameter STR (H-PCRF to H-AF, for each affected AF session if any). + - 13. Diameter STA (H-AF to H-PCRF, for each affected AF session if any). + - 14. Final Spending Limit Report Request (H-PCRF to OCS, conditional). + - 15. Gateway Control and QoS Rules provision (case 2a) or PCRF-initiated Gateway Control Session Termination (case 2a) (PCEF to BBERF, conditional). + - 16. Cancel Subscribed Notification request (H-PCRF to SPR). + - 17. Cancel Subscribed Notification Response (SPR to H-PCRF). + - 18. St session termination (PCEF internal step, conditional). + +**Legend:** + +- Mandatory: Solid line with arrowhead. +- Conditional: Dashed line with arrowhead. + +Sequence diagram for PCEF-initiated IP-CAN Session Termination. Lifelines: BBERF, PCEF, RCAF, TDF, TSSF, V-PCRF, H-PCRF, H-AF, SPR, OCS. The diagram shows the interaction between these elements for session termination, with specific steps for visited and home access cases. + +**Figure 4.2.2.1.1 : PCEF-initiated IP-CAN Session Termination – AF located in the HPLMN** + +In the following procedures, the V-PCRF is included to depict the roaming scenarios. H-PCRF acts as the PCRF for non-roaming UEs. + +- The PCEF detects that the termination of an IP-CAN Session or bearer is required. +- If case 2b applies (as defined in clause 4.0), PCEF sends the Remove IP-CAN Session Request to the BBERF. If case 2a applies (as defined in clause 4.0), the request goes transparently through the BBERF. In all cases, the PCEF sends a Remove IP-CAN Session Request to remove the IP-CAN Session. The form of the Remove IP-CAN Session Request depends upon the type of the IP-CAN. It can consist of separate requests for each IP-CAN Bearer within an IP-CAN Session. + +- 3 If case 2b applies (as defined in clause 4.0), the BBERF-initiated Gateway Control Session Termination procedure as defined in clause 4.4.4 (BBERF-Initiated Gateway Control Session Termination) is initiated. +4. The PCEF receives a response to the Remove IP-CAN Session Request. +- 5 – 7. Same as Steps 3~5 in figure 4.2.1.1.1. +- 8 – 18. Same as Steps 7~17 in figure 4.2.1.1.1. + +NOTE 1: Steps 2 and 5 may be executed in parallel. + +#### 4.2.2.2 AF located in the VPLMN + +This clause is applicable only for the Visited Access scenario for the case when an IP-CAN Session is being released by the PCEF and the AF is located in the VPLMN + +![Sequence diagram for PCEF-Initiated IP-CAN Session Termination – AF located in the VPLMN. The diagram shows interactions between BBERF, PCEF, V-PCRF, H-PCRF, V-AF, and SPR. A vertical bar on the left is labeled 'VISITED ACCESS CASE'. The sequence starts with a block '1. Perform Step 1 through Step 9: as specified in Figure 4.2.2.1.1 : PCEF Initiated IP-CAN Session Termination - AF Located in the HPLMN'. This is followed by a loop for each affected AF session (if any) containing steps 2 through 9: 2. Diameter ASR (V-PCRF to H-PCRF), 3. Diameter ASR (H-PCRF to V-PCRF), 4. Diameter ASA (V-PCRF to H-PCRF), 5. Diameter ASA (H-PCRF to V-PCRF), 6. Diameter STR (V-PCRF to H-PCRF), 7. Diameter STR (H-PCRF to V-PCRF), 8. Diameter STA (V-PCRF to H-PCRF), and 9. Diameter STA (H-PCRF to V-PCRF). This is followed by a block '10. Perform Step 14 through Step 17: as specified in Figure 4.2.2.1.1 : PCEF Initiated IP-CAN Session Termination - AF Located in the HPLMN'. A legend at the bottom left shows a solid arrow for 'Mandatory' and a dashed arrow for 'Conditional'.](e636d7ccca0ad14c6b95201404324823_img.jpg) + +Sequence diagram for PCEF-Initiated IP-CAN Session Termination – AF located in the VPLMN. The diagram shows interactions between BBERF, PCEF, V-PCRF, H-PCRF, V-AF, and SPR. A vertical bar on the left is labeled 'VISITED ACCESS CASE'. The sequence starts with a block '1. Perform Step 1 through Step 9: as specified in Figure 4.2.2.1.1 : PCEF Initiated IP-CAN Session Termination - AF Located in the HPLMN'. This is followed by a loop for each affected AF session (if any) containing steps 2 through 9: 2. Diameter ASR (V-PCRF to H-PCRF), 3. Diameter ASR (H-PCRF to V-PCRF), 4. Diameter ASA (V-PCRF to H-PCRF), 5. Diameter ASA (H-PCRF to V-PCRF), 6. Diameter STR (V-PCRF to H-PCRF), 7. Diameter STR (H-PCRF to V-PCRF), 8. Diameter STA (V-PCRF to H-PCRF), and 9. Diameter STA (H-PCRF to V-PCRF). This is followed by a block '10. Perform Step 14 through Step 17: as specified in Figure 4.2.2.1.1 : PCEF Initiated IP-CAN Session Termination - AF Located in the HPLMN'. A legend at the bottom left shows a solid arrow for 'Mandatory' and a dashed arrow for 'Conditional'. + +**Figure 4.2.2.2.1: PCEF-Initiated IP-CAN Session Termination – AF located in the VPLMN** + +If the AF resides in the VPLMN, the V-PCRF proxies AF session signalling over S9 between the V-AF and the H-PCRF. + +1. In order to perform PCEF initiated IP-CAN Session Termination Procedures, step 1 through step 9: as specified in Figure 4.2.2.1.1: PCEF Initiated IP-CAN Session Termination – AF Located in the HPLMN are executed. + +For each AF session identified in step 6 (Figure 4.2.2.1.1) as bound to the IP-CAN Session being removed, steps 2-9 are executed: + +2. The H-PCRF indicates the session abort to the V-AF in VPLMN by sending an ASR to the V-PCRF. + +3. The V-PCRF proxies the ASR to the V-AF. +4. The V-AF responds by sending an ASA to the V-PCRF. +5. The V-PCRF proxies the ASA to the H-PCRF. +6. The V-AF sends an STR to the V-PCRF to indicate that the session has been terminated. +7. The V-PCRF proxies the STR to the H-PCRF. +8. The H-PCRF responds by sending an STA to the V-PCRF. +9. The V-PCRF proxies the STA to the V-AF. +10. Step 14 through step 17: as specified in Figure 4.2.2.1.1: PCEF Initiated IP-CAN Session Termination – AF Located in the HPLMN are executed, as needed. + +NOTE: For steps 16 and 17: the details associated with the Sp reference point are not specified in this Release. The SPR's relation to existing subscriber databases is not specified in this Release. + +### 4.2.3 PCRF-Initiated + +#### 4.2.3.1 AF located in the HPLMN + +This clause is applicable if an IP-CAN Session is being released by the PCRF and the AF is located in the HPLMN. + +![Sequence diagram for PCRF-initiated IP-CAN Session Termination. Lifelines: BBERF, PCEF, RCAF, TDF, TSSF, V-PCRF, H-PCRF, H-AF, SPR, OCS. The diagram shows the interaction between these elements to terminate an IP-CAN session, with various Diameter messages like RAR, RAA, CCR, CCA, ASR, ASA, STR, STA, and final reporting steps. It includes 'VISITED ACCESS CASE' labels and a legend for mandatory and conditional messages.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The sequence diagram illustrates the PCRF-initiated IP-CAN Session Termination process. The lifelines involved are BBERF, PCEF, RCAF, TDF, TSSF, V-PCRF, H-PCRF, H-AF, SPR, and OCS. The process is divided into several steps, with some steps occurring within 'VISITED ACCESS CASE' blocks. + +- Detection that IP-CAN Session termination is required (H-PCRF) +- Diameter RAR (H-PCRF to PCEF) +- 2a. Diameter RAR (H-PCRF to V-PCRF) +- 2b. Diameter RAR (V-PCRF to PCEF) +- Removal of all PCC Rules (PCEF) +- Diameter RAA (PCEF to H-PCRF) +- 4a. Diameter RAA (H-PCRF to V-PCRF) +- 4b. Diameter RAA (V-PCRF to H-PCRF) +- Remove IP-CAN Session Request (H-PCRF to BBERF) +- BBERF-initiated Gateway Control Session Termination(case 2b) (BBERF to PCEF) +- Remove IP-CAN Session Response (PCEF to H-PCRF) +- Diameter CCR (H-PCRF to PCEF) +- 8a. Diameter CCR (PCEF to V-PCRF) +- 8b. TDF session termination for roaming UE with visited access (Conditional, V-PCRF to TDF) +- 8c. UE context removal (Conditional, V-PCRF to TDF) +- 8d. Diameter CCR (V-PCRF to H-PCRF) +- Identify AF Sessions bound to the removed IP-CAN Session (H-PCRF) +- Diameter CCA (H-PCRF to PCEF) +- 10a. Diameter CCA (PCEF to V-PCRF) +- 10b. removes the information related to the terminated IP-CAN Session (Conditional, V-PCRF to TDF) +- 10c. Diameter CCA (V-PCRF to PCEF) +11. TDF session termination for roaming UE with visited access (Conditional, TDF to TSSF) +12. UE context removal (Conditional, TDF to TSSF) +- For each affected AF session (if any): + - Diameter ASR (H-PCRF to H-AF) + - Diameter ASA (H-AF to H-PCRF) + - Diameter STR (H-PCRF to H-AF) + - Diameter STA (H-AF to H-PCRF) +- Final Spending Limit Report Request (Conditional, H-PCRF to OCS) +- Gateway Control and Qos Rules provision (case 2a) Or PCRF-initiated Gateway Control Session Termination(case 2a) (H-PCRF to BBERF) +- Cancel Subscribed Notification request (H-PCRF to OCS) +- Cancel Subscribed Notification response (OCS to H-PCRF) +- St session termination (Conditional, H-PCRF to TSSF) + +**Legend:** + +- Solid arrow: Mandatory +- Dashed arrow: Conditional + +Sequence diagram for PCRF-initiated IP-CAN Session Termination. Lifelines: BBERF, PCEF, RCAF, TDF, TSSF, V-PCRF, H-PCRF, H-AF, SPR, OCS. The diagram shows the interaction between these elements to terminate an IP-CAN session, with various Diameter messages like RAR, RAA, CCR, CCA, ASR, ASA, STR, STA, and final reporting steps. It includes 'VISITED ACCESS CASE' labels and a legend for mandatory and conditional messages. + +Figure 4.2.3.1.1: PCRF-initiated IP-CAN Session Termination – AF located in HPLMN + +In the following procedures, the V-PCRF is included to depict the roaming scenarios. H-PCRF acts as the PCRF for non-roaming Ues. + +1. The H-PCRF detects that the termination of an IP-CAN Session is required. +2. For the non-roaming case, and for the case when the UE is roaming in a Home Routed scenario, the H-PCRF sends a RAR including the Session-Release-Cause AVP to request that the PCEF terminates the IP CAN session. + +For the case when the UE is roaming in a Visited Access scenario, steps 2a~2b are executed instead of step 2: + +- 2a. If case 2b or case 1 applies and the subsession being terminated is the last subsession over S9, the H-PCRF sends a RAR including the Session-Release-Cause AVP to the V-PCRF to indicate the termination of the S9 session. Otherwise, the H-PCRF sends a RAR to the V-PCRF including the Subsession-Decision-Info AVP with the Session-Release-Cause AVP to indicate the request for terminating the S9 subsession corresponding to the IP-CAN session. +- 2b. The V-PCRF sends a RAR including the Session-Release-Cause AVP to the PCEF. +3. The PCEF removes all the PCC Rules which are applied to the IP-CAN session. +4. For the non-roaming case, and for the case when the UE is roaming in a Home Routed scenario, the PCEF sends a RAA to acknowledge the RAR. + +For the case when the UE is roaming in a Visited Access scenario, steps 4a~4b are executed instead of step 4: + +- 4a. The PCEF sends a RAA to the V-PCRF. +- 4b. The V-PCRF sends a RAA to the H-PCRF and acknowledges the request for terminating the S9 session or the S9 subsession corresponding to the IP-CAN session. +5. The PCEF applies IP CAN specific procedures to terminate the IP CAN session. +6. – 21. Same as Steps 3-18 in figure 4.2.2.1.1. + +#### 4.2.3.2 AF located in the VPLMN + +This clause is applicable only for the Visited Access scenario for the case when an IP-CAN Session is being released by the PCRF and the AF is located in the VPLMN + +![Sequence diagram for PCRF-Initiated IP-CAN Session Termination – AF located in the VPLMN. Lifelines: BBERF, PCEF, V-PCRF, H-PCRF, V-AF, SPR. The diagram shows two main steps: Step 1 (PCRF Initiated IP-CAN Session Termination - AF Located in the HPLMN) and Step 10 (PCRF Initiated IP-CAN Session Termination - AF Located in the HPLMN). Between steps 1 and 10, a 'VISITED ACCESS CASE' loop occurs for each affected AF session. This loop involves Diameter ASR, ASA, STR, and STA messages between the H-PCRF, V-PCRF, and V-AF. A legend indicates solid arrows are Mandatory and dashed arrows are Conditional.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +The diagram illustrates the sequence of messages for PCRF-Initiated IP-CAN Session Termination when the AF is located in the VPLMN. The lifelines are BBERF, PCEF, V-PCRF, H-PCRF, V-AF, and SPR. The process starts with Step 1: Perform Step 1 through Step 12: as specified in Figure 4.2.3.1.1 : PCRF Initiated IP-CAN Session Termination - AF Located in the HPLMN. This is followed by a 'VISITED ACCESS CASE' loop for each affected AF session (if any). Inside this loop, the following messages are exchanged: 2. Diameter ASR (H-PCRF to V-PCRF), 3. Diameter ASR (V-PCRF to V-AF), 4. Diameter ASA (V-AF to V-PCRF), 5. Diameter ASA (V-PCRF to H-PCRF), 6. Diameter STR (V-AF to V-PCRF), 7. Diameter STR (V-PCRF to H-PCRF), 8. Diameter STA (H-PCRF to V-PCRF), and 9. Diameter STA (V-PCRF to V-AF). After the loop, Step 10: Perform Step 17 through Step 20: as specified in Figure 4.2.3.1.1 : PCRF Initiated IP-CAN Session Termination - AF Located in the HPLMN is executed. A legend indicates that solid arrows represent Mandatory messages and dashed arrows represent Conditional messages. + +Sequence diagram for PCRF-Initiated IP-CAN Session Termination – AF located in the VPLMN. Lifelines: BBERF, PCEF, V-PCRF, H-PCRF, V-AF, SPR. The diagram shows two main steps: Step 1 (PCRF Initiated IP-CAN Session Termination - AF Located in the HPLMN) and Step 10 (PCRF Initiated IP-CAN Session Termination - AF Located in the HPLMN). Between steps 1 and 10, a 'VISITED ACCESS CASE' loop occurs for each affected AF session. This loop involves Diameter ASR, ASA, STR, and STA messages between the H-PCRF, V-PCRF, and V-AF. A legend indicates solid arrows are Mandatory and dashed arrows are Conditional. + +**Figure 4.2.3.2.1: PCRF-Initiated IP-CAN Session Termination – AF located in the VPLMN** + +If the AF resides in the VPLMN, the V-PCRF proxies AF session signalling over S9 between the V-AF and the H-PCRF. + +1. In order to perform PCRF initiated IP-CAN Session Termination Procedures, step 1 through step 12: as specified in Figure 4.2.3.1.1: PCRF Initiated IP-CAN Session Termination – AF Located in the HPLMN are executed. + +For each AF session identified in step 6 (Figure 4.2.3.1.1) as bound to the IP-CAN Session being removed, steps 2-9 are executed: + +2. The H-PCRF indicates the session abort to the V-AF in VPLMN by sending an ASR to the V-PCRF. +3. The V-PCRF proxies the ASR to the V-AF. +4. The V-AF responds by sending an ASA to the V-PCRF. +5. The V-PCRF proxies the ASA to the H-PCRF. +6. The V-AF sends an STR to the V-PCRF to indicate that the session has been terminated. +7. The V-PCRF proxies the STR to the H-PCRF. + +8. The H-PCRF responds by sending an STA to the V-PCRF. +9. The V-PCRF proxies the STA to the V-AF. +10. Step 17 through step 20: as specified in Figure 4.2.3.1.1: PCRF Initiated IP-CAN Session Termination – AF Located in the HPLMN are executed, as needed. + +NOTE: For steps 19 and 20: the details associated with the Sp reference point are not specified in this Release. The SPR's relation to existing subscriber databases is not specified in this Release. + +## 4.3 IP-CAN Session Modification + +### 4.3.1 Network-Initiated IP-CAN Session Modification + +- 4.3.1.1 Interactions between BBERF, PCEF, TDF, OCS, TSSF and PCRF(PCC/QoS/ADC Rule Provisioning in PUSH mode) + +This flow shows the provisioning of PCC/QoS/ADC Rules and/or authorized QoS triggered by an event in the PCRF. + +![Sequence diagram showing interactions between BBERF, PCEF, TDF, TSSF, V-PCRF, H-PCRF, and OCS for PCRF-Initiated IP-CAN Session Modification. The diagram includes lifelines for each entity and numbered messages indicating mandatory and conditional interactions. Two 'VISITED ACCESS CASE' regions are highlighted in light blue.](820515db47ded68f5e0b625f4ec7d2c1_img.jpg) + +The sequence diagram illustrates the following interactions: + +- 1. Trigger:** OCS to H-PCRF (Mandatory) +- 2. PCC Rules decision, Policy Decision:** H-PCRF to V-PCRF (Mandatory) +- 3. Store PCC and ADC Rules:** H-PCRF to V-PCRF (Mandatory) +- 4. Timer:** H-PCRF internal (Conditional) +- 5. Gateway Control & QoS Rule Provision (case 2a & 2b):** V-PCRF to BBERF (Conditional) +- 6. Diameter RAR:** V-PCRF to PCEF (Mandatory) +- 6a. Diameter RAR:** V-PCRF to TSSF (Mandatory) +- 6b. PCC Rules validation, Local Policy Decision:** TSSF to V-PCRF (Mandatory) +- 6c. TDF session establishment/ modification/ termination:** V-PCRF to TDF (Conditional) +- 6d. Diameter RAR:** V-PCRF to BBERF (Conditional) +- 6e. Install, modify or remove QoS rules:** BBERF internal (Conditional) +- 6f. Diameter RAR:** V-PCRF to PCEF (Mandatory) +- 7. Install, modify or remove PCC rules:** PCEF internal (Conditional) +- 8. Diameter RAA:** PCEF to H-PCRF (Mandatory) +- 8a. Diameter RAA:** PCEF to V-PCRF (Conditional) +- 8b. Diameter RAA:** PCEF to V-PCRF (Mandatory) +- 8c. Store Result:** V-PCRF internal (Conditional) +- 8d. Diameter RAA:** V-PCRF to H-PCRF (Mandatory) +- 9. TDF session establishment/ modification/ termination for non-roaming/HR:** H-PCRF to TDF (Conditional) +- 10. St establishment /modification/termination for non-roaming/HR:** H-PCRF to TSSF (Conditional) +- 11. Initial/ Intermediate/ Final Spending Limit Report Request:** H-PCRF to OCS (Conditional) +- 12. IP - CAN session modification:** H-PCRF to PCEF (Conditional) +- 13. IP - CAN session signalling:** PCEF to BBERF (Conditional) +- 14. IP - CAN session modification:** PCEF to BBERF (Conditional) + +**Legend:** + +- Mandatory:** Solid line with arrowhead +- Conditional:** Dashed line with arrowhead + +Sequence diagram showing interactions between BBERF, PCEF, TDF, TSSF, V-PCRF, H-PCRF, and OCS for PCRF-Initiated IP-CAN Session Modification. The diagram includes lifelines for each entity and numbered messages indicating mandatory and conditional interactions. Two 'VISITED ACCESS CASE' regions are highlighted in light blue. + +Figure 4.3.1.1.1: Interactions between BBERF, PCEF, TDF, OCS, TSSF and PCRF for PCRF-Initiated IP-CAN Session Modification + +1. The H-PCRF receives an internal or external trigger to re-evaluate PCC Rules and policy decision for an IP-CAN Session. Possible external trigger events are described in clause 4.3.1.2. In addition, this procedure is triggered by + - PCEF subscribed event + - SPR subscription data modification (e.g. change in MPS EPS Priority, MPS Priority Level and/or IMS Signalling Priority, or change in user profile configuration indicating whether supporting application detection and control). + - OCS status of a policy counter identifier(s) has changed and the PCRF requested notification for spending limits apply. + - Application detection information report from TDF. +2. The H-PCRF selects the PCC Rule(s) to be installed, modified or removed for the IP-CAN Session. In case of PCEF supporting Application Detection and Control feature, some of those PCC rules may be used for application detection and control. The H-PCRF may also update the policy decision by defining an authorized QoS and enable or disable the service flow(s) of PCC Rules. If the PCEF controls the binding of IP-CAN bearers, the H-PCRF may add or change QoS information per QCI applicable to that IP-CAN session. In case of TDF, the H-PCRF selects the applicable ADC rules for the solicited application reporting with a TDF. If NBIFOM applies to the IP-CAN session and Network-initiated mode is selected, the H-PCRF determines the access that is to be used for the transfer of traffic and include the allowed access type in the PCC rules. If NBIFOM applies to the IP-CAN session, the H-PCRF determines one access is to be removed from multi access IP-CAN session. +3. The H-PCRF stores the updated PCC Rules, and ADC rules if available. +4. Step 4 is only applicable if the Bearer Control Mode (BCM) selected is UE-only or, for UE/NW the H-PCRF determines that UE mode applies for the affected PCC Rules, and the PCRF receives an external trigger from the AF. + +The PCRF may start a timer to wait for a UE requested bearer resource initiation, modification or removal procedure initiated by the UE, as depicted in figure 4.3.2.1.1. + +If a UE requested bearer resource initiation, modification or termination procedure initiated by the terminal is received for the affected PCC rules while the timer is running, all subsequent steps in the present figure shall not be executed and, for case 1, the steps in figure 4.3.2.1.1 (on provisioning based on PULL procedure at PCEF – initiated IP-CAN session modification when the AF is located in the HPLMN), 4.3.2.2.1 (on provisioning based on PULL procedure at PCEF-initiated IP-CAN session modification when the AF is located in the VPLMN) and for cases 2a and 2b, the steps in figure 4.4.2.1.1 (Home Routed case) or 4.4.2.2.1 (Visited Access case) shall be executed instead. + +Otherwise, if the BCM selected is UE/NW, the PCRF shall proceed with the subsequent steps (provisioning based on PUSH procedure) in the present figure after timer expiry. + +NOTE 1: For IMS Emergency session and RLOS session step 4 is not applicable. + +5. For case 2a and 2b, if Gxx applies for the IP-CAN session and the user is not roaming, or the user is roaming in a Home Routed scenario or a Visited Access scenario for case 2a when the available QoS rule are not related to any IP-CAN session, the H-PCRF may initiate Gateway Control and QoS rules provisioning procedures described in clause 4.4.3. + +NOTE 2: This step is not executed if this procedure is triggered by PCEF subscribed events and/or credit re-authorisation triggers reported by the BBERF. + +6. The H-PCRF sends a Diameter RAR to request that the PCEF installs, modifies or removes PCC Rules and updates the policy decision, or to report PCEF subscribed events reported by the BBERF. The report includes the User Location Information and the User CSG Information (If received from the BBERF). If the provided PCC rules are related to an AF session associated with a sponsor that has requested sponsoring the service, the H-PCRF includes, in the Charging-Rule-Definition AVP, the Sponsor-Identity AVP and the Application-Service-Provider-Identity AVP that it received from the AF if the Reporting-Level AVP is set to the value SPONSORED\_CONNECTIVITY\_LEVEL and, if AF provided the application usage thresholds, the Usage-Monitoring-Information AVP. If the AF requests the access network information, the H-PCRF includes Required-Access-Info AVP in the Charging-Rule-Definition AVP and/or Charging-Rule-Remove AVP. In + +addition, the H-PCRF includes the Event-Trigger set to the value "ACCESS\_NETWORK\_INFO\_REPORT" if not provided yet. If the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP are provided within the Media-Component-Description AVP, the PCRF may apply the mechanisms for resource sharing as specified at 3GPP TS 29.212 [9]. The PCRF includes the Removal-Of-Access AVP set to the value REMOVAL\_OF\_ACCESS (0) and the IP-CAN-Type AVP set to the value of removed access to remove one access from the multi access IP-CAN session. If the H-PCRF subscribes the change of UE presence in Presence Reporting Area, the H-PCRF may provide the Presence Reporting Area Information to the PCEF. If the RAN-Support-Info feature is enabled and local policy allows, for PCC rules with QCI of 1, the PCRF can provide the Charging-Rule-Definition AVP including the maximum packet loss rate(s) for uplink and/or downlink direction(s) in the Max-PLR-UL/DL AVP(s) respectively. + +When the UE is roaming in a Visited Access scenario, steps 6a ~ 6e are executed instead of step 6: + +- 6a. The H-PCRF sends a Diameter RAR to the V-PCRF to request that the PCEF installs, modifies or removes PCC Rules and updates the policy decision. In the case of VPLMN supporting Application Detection and Control feature for solicited application reporting, some of those PCC Rules may be used for application detection and control. If the provided PCC rules are related to an AF session associated with a sponsor that has requested sponsoring the service, the H-PCRF includes, in the Charging-Rule-Definition AVP, the Sponsor-Identity AVP and the Application-Service-Provider-Identity AVP that it received from the AF if the Reporting-Level AVP is set to the value SPONSORED\_CONNECTIVITY\_LEVEL and, if AF provided the application usage thresholds, the Usage-Monitoring-Information AVP. If the AF requests the access network information, the H-PCRF includes Required-Access-Info AVP in the Charging-Rule-Definition AVP and/or Charging-Rule-Remove AVP. In addition, the H-PCRF includes the Event-Trigger set to the value "ACCESS\_NETWORK\_INFO\_REPORT" if not provided yet. +- 6b. The V-PCRF enforces visited operator policies regarding PCC rules requested by the H-PCRF based on roaming agreements or locally configured policy. In case of TDF, V-PCRF extracts the ADC rules from the PCC Rules received from the H-PCRF and stores them. + +NOTE 3: If the V-PCRF rejects provisioned PCC rules received from the H-PCRF, the remaining steps in this call flow are not followed. Instead, the V-PCRF shall notify the H-PCRF by sending a Diameter RAA, including the Experimental-Result-Code AVP set to the value PCC\_RULE\_EVENT, identify the failed PCC rules as specified in 3GPP TS 29.212 [9], and additionally may provide the acceptable QoS Information for the service. + +- 6c. In case of TDF, solicited application reporting, for roaming UE with visited access, the V-PCRF initiates the TDF session establishment, modification, or termination. If the provided ADC rules are related to an AF session associated with a sponsor that has requested sponsoring the service, the H-PCRF includes, in the ADC-Rule-Definition AVP, the Sponsor-Identity AVP and the Application-Service-Provider-Identity AVP that are received from the AF if the Reporting-Level AVP is set to the value SPONSORED\_CONNECTIVITY\_LEVEL. Additionally, if the AF provided the application usage thresholds, the H-PCRF includes the Usage-Monitoring-Information AVP. If the last ADC rule is deactivated, the V-PCRF requests the TDF to terminate the TDF session toward the V-PCRF as defined in clause 4.6.2. If there is no active TDF session between the TDF and the V-PCRF, the V-PCRF requests the TDF to establish the TDF session towards V-PCRF and provides ADC Rules to the TDF as defined in clause 4.6.1. If there is already an active TDF session between the TDF and the V-PCRF, the V-PCRF provides the ADC rules to the TDF as defined in clause 4.6.3.2. + - 6d. For case 2a and 2b, V-PCRF will derive the QoS rules from the PCC rules. The V-PCRF will initiate a Gateway Control and QoS Rule procedure as described in clause 4.4.3 to install, modify or remove QoS rules and optionally subscribe to new events in the BBERF. + - 6e. The BBERF installs, modifies or removes the identified QoS Rules. The BBERF also enforces the authorized QoS of the corresponding QoS Rules. + - 6f. The V-PCRF sends a Diameter RAR to request that the PCEF installs, modifies or removes PCC Rules. +7. The PCEF installs, modifies or removes the identified PCC Rules. The PCEF also enforces the authorized QoS and enables or disables service flow according to the flow status of the corresponding PCC Rules. If QoS information is received per QCI, PCEF shall set/update the upper limit for the MBR that the PCEF assigns to the non-GBR bearer for that QCI. In the case of PCEF supporting Application Detection and Control feature, the PCEF may also enforce application detection and control. The PCEF may perform resource sharing among PCC rules if requested from the PCRF. If allowed access type information is included in the PCC rules, the PCEF generates the NBIFOM routing rules based on the PCC rules. If the RAN-Support-Info feature is supported, the + +PCEF sets the UL/DL maximum packet loss rate value(s) as described in subclause B.3.18 of 3GPP TS 29.212 [9]. + +The following applies for emergency sessions only: + +When the PCEF receives an IP-CAN Session Modification Request from the PCRF requesting the removal of the PCC rules of an emergency session, the PCEF starts an inactivity timer to enable the PSAP to request a callback session with the UE. + +When the timer expires, the PCEF initiates an IP-CAN Session Termination Request (per clause 4.2.2.1) to terminate the emergency session. + +If, before the timer expires, the PCEF receives an IP-CAN Session Modification Request from the PCRF with PCC rules for an emergency session the PCEF cancels the timer. + +8. The PCEF sends a Diameter RAA to acknowledge the RAR. The PCEF informs the H-PCRF about the outcome of the PCC rule operation + +When the UE is roaming in a Visited Access scenario, steps 8a ~ 8d are executed instead of step 8: + +- 8a. The BBERF informs the V-PCRF about the outcome of the operation by sending a Diameter RAA command. +- 8b. The PCEF informs the V-PCRF about the outcome of the PCC rule operation by sending a Diameter RAA command. +- 8c. The V-PCRF stores the received information. +- 8d. The V-PCRF informs the H-PCRF about the outcome of the operation by sending a Diameter RAA command. + +9. In case of TDF, solicited application reporting, for non-roaming UE/roaming UE with home routed access, H-PCRF initiates the TDF session establishment, modification, or termination. If the provided ADC rules are related to an AF session associated with a sponsor that has requested sponsoring the service, the H-PCRF includes, in the ADC-Rule-Definition AVP, the Sponsor-Identity AVP and the Application-Service-Provider-Identity AVP that are received from the AF if the Reporting-Level AVP is set to the value SPONSORED\_CONNECTIVITY\_LEVEL. Additionally, if the AF provided the application usage thresholds, the H-PCRF includes the Usage-Monitoring-Information AVP. If the last ADC rule is deactivated, the H-PCRF requests the TDF to terminate the TDF session toward the H-PCRF as defined in clause 4.6.2. If there is no active TDF session between the TDF and the H-PCRF, the H-PCRF requests the TDF to establish the TDF session towards H-PCRF and provides ADC Rules to the TDF as defined in clause 4.6.1. If there is already an active TDF session between the TDF and the H-PCRF, H-PCRF provides the ADC rules to the TDF as defined in clause 4.6.3.2. + +NOTE 4: Step 9 can occur anytime after step 6. + +10. If traffic steering control over St applies, if the PCRF determines that the traffic steering control information needs to be provisioned for the IP-CAN session; the PCRF initiates the St session establishment procedure according to the subclause 4.9.1. If the PCRF determines that the traffic steering control information provisioned to the TSSF needs to be updated, the PCRF initiates the St session modification procedure according to the subclause 4.9.2. If the PCRF determines that the traffic steering control information is not needed for the IP-CAN session any more, the PCRF initiates the St session termination procedure according to the subclause 4.9.3. +11. In case of spending limits, for non-roaming/roaming UE with both home routed and visited access, H-PCRF initiates Initial/ Intermediate/ Final Spending Limit Report Request. The H-PCRF sends an Initial Spending Limit Report Request if this is the first time a status notification of policy counter is requested for the user as defined in clause 4.7.1. If the H-PCRF decides to modify the list of subscribed policy counters the H-PCRF sends an Intermediate Spending Limit Report Request as defined in clause 4.7.2. If the H-PCRF decides to unsubscribe any future status notification of policy counters, it sends a Final Spending Limit Report Request to cancels the request for reporting the change of the status of the policy counters available at the OCS as defined in clause 4.7.3. + +NOTE 5: Step 11 can occur anytime after step 2. + +12. If usage monitoring is enabled and the H-PCRF either removed the last PCC rule applicable for certain monitoring key, or disabled usage monitoring or requested usage report, the PCEF shall initiate an IP-CAN session modification procedure. +13. When Gxx does not apply for the IP-CAN session, IP-CAN bearer signalling is executed separately for each IP-CAN bearer under the following conditions: + - If all PCC rules bound to a bearer have been removed or deactivated (bearer deactivation is applicable) + - If one or more bearers have to be modified + - If the PCEF needs to establish a new bearer (bearer establishment is applicable). + - If the PCEF needs to request access network information. + - if the PCEF needs to send the NBIFOM routing rules to the UE in the corresponding access. +14. If the AF, in step 1, has requested notifications from the PCRF, e.g. in the case of access network information the PCEF initiates an IP-CAN session modification procedure to provide the requested information as described in clause 4.3.2. + +NOTE 6: If the conditions of both step 14 and step 12 apply the PCEF can make use of only one IP-CAN session modification procedure in step 14. + +#### 4.3.1.2 Interactions between PCRF, AF and SPR + +##### 4.3.1.2.1 AF Session Establishment + +###### 4.3.1.2.1.1 AF located in HPLMN + +![Sequence diagram showing AF session establishment triggers PCRF-Initiated IP-CAN Session Modification (AF in HPLMN).](d980a3f9608055996a07f31788baf827_img.jpg) + +The sequence diagram illustrates the interaction between BBERF, PCEF, V-PCRF, H-PCRF, AF, and SPR. The sequence of messages is as follows: + +1. Trigger (AF to H-PCRF) +2. Diameter AAR (H-PCRF to V-PCRF) +3. Store Service Information (V-PCRF to H-PCRF) +4. Profile Request (H-PCRF to SPR) +5. Profile Response (SPR to H-PCRF) - Conditional (dashed line) +6. Identify affected IP CAN session(s) (H-PCRF to V-PCRF) +7. Diameter AAA (V-PCRF to H-PCRF) +8. Interactions in Figure 4.3.1.1.1 (H-PCRF to PCEF) + +**Legend:** + +- Mandatory +- - - - -> Conditional + +*Note: Step 5 is conditional if the PCRF needs subscription-related information and does not have it.* + +Sequence diagram showing AF session establishment triggers PCRF-Initiated IP-CAN Session Modification (AF in HPLMN). + +**Figure 4.3.1.2.1.1.1: AF session establishment triggers PCRF-Initiated IP-CAN Session Modification (AF in HPLMN)** + +1. The AF receives an internal or external trigger to set-up a new AF session and provides Service Information. The AF identifies the Service Information needed (e.g. IP address of the IP flow (s), port numbers to be used, information on media types, etc). + +2. The AF provides the Service Information to the H-PCRF by sending a Diameter AAR for a new Rx Diameter session. If this AF session is associated with a sponsor, Sponsor-Identity AVP, optionally the Sponsoring-Action AVP set to applicable value and the Application-Service-Provider-Identity AVP are included in Sponsored-Connectivity-Data AVP. If usage thresholds are to be associated with this sponsored AF session, then Granted-Service-Unit AVP is included in Sponsored-Connectivity-Data AVP. The AF can request access network information within the AAR by adding Required-Access-Info AVP(s) and Specific-Action AVP set to the value "ACCESS\_NETWORK\_INFO\_REPORT". If the Service can be subject to resource sharing, the AF includes the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP within the Media-Component-Description AVP. If PrioritySharing feature is supported and the service is allowed to use the same Allocation and Retention Priority (ARP) as media flows belonging to other AF sessions, the AF includes the Priority-Sharing-Indicator AVP set to PRIORITY\_SHARING\_ENABLED within the Media-Component-Description AVP. If the CHEM feature is supported, the AF may also include the maximum packet loss rate(s) for uplink and/or downlink direction(s) in the Max-PLR-UL/DL AVP(s) respectively within the Media-Component-Description AVP. If the service has negotiated the background data transfer policy, the AF includes the reference id of the transfer policy within the Reference-Id AVP. To invoke MPS for DTS, the AF includes the MPS-Action AVP within the AAR, as specified in clause 5.3. +3. The H-PCRF stores the received Service Information. +4. If the H-PCRF requires subscription related information and does not have it, the PCRF sends a request to the SPR in order to receive the information. If the Reference-Id AVP is received, the PCRF retrieves the corresponding transfer policy from the SPR and derives the PCC rules for the background data transfer according to the transfer policy. + +If the AF session is for MPS for DTS invocation, the PCRF performs MPS subscription checks if and only if requested by the AF, as described in subclause 4.4.11 of 3GPP TS 29.214 [10]. + +5. The SPR replies with the subscription related information containing the information about the allowed service(s), QoS information and PCC Rules information. + +NOTE: For steps 4 and 5: The details associated with the Sp reference point are not specified in this Release. The SPR's relation to existing subscriber databases is not specified in this Release. + +6. If the AF session is associated with a sponsor and sponsored service is enabled, + - if the UE is in the non-roaming case or UE is roaming with the home routed case and operator policies allow accessing the sponsored data connectivity with this roaming case, the H-PCRF authorizes the request based on sponsored data connectivity profile obtained from the SPR; + - if the UE is roaming with the home routed case and operator policies do not allow accessing the sponsored data connectivity with this roaming case or the UE is roaming with the visited access case, the H-PCRF rejects the request. + +The H-PCRF identifies the affected established IP-CAN Session(s) using the information previously received from the PCEF/V-PCRF and the Service Information received from the AF. + +7. The H-PCRF sends a Diameter AAA to the AF. The PCRF indicates whether the support for UE IP address/mask in the TFT filter is available in the IP-CAN session. +8. The H-PCRF interacts with the PCEF/BBERF/V-PCRF according to figure 4.3.1.1.1 (Interactions between BBERF/PCEF and PCRF for PCRF-Initiated IP-CAN Session Modification). + +###### 4.3.1.2.1.2 + +###### AF located in VPLMN + +![Sequence diagram for AF session establishment triggers PCRF-initiated IP-CAN Session Modification (AF in VPLMN). The diagram shows interactions between BBERF, PCEF, V-PCRF, H-PCRF, AF, and SPR. The AF sends a trigger to the V-PCRF, which stores service information and forwards it to the H-PCRF. The H-PCRF may request profile information from the SPR. The V-PCRF then identifies affected IP CAN sessions and sends Diameter AAA messages to the PCEF and BBERF. A callout indicates that if the PCRF needs subscription-related information and does not have it, it sends a profile request to the SPR. A legend indicates that solid arrows are mandatory and dashed arrows are conditional.](d793cf7c174b89eb024d132f00679787_img.jpg) + +``` + +sequenceDiagram + participant AF + participant V-PCRF + participant H-PCRF + participant SPR + participant PCEF + participant BBERF + + Note left of BBERF: ROAMING CASE + + AF->>V-PCRF: 1. Trigger + V-PCRF->>AF: 2. Diameter AAR + Note right of V-PCRF: 3. Store Service Information + V-PCRF->>H-PCRF: 4. Diameter AAR + Note right of H-PCRF: 5. Store Service information Policy Decision + H-PCRF-->>SPR: 6. Profile Request + Note right of SPR: If the PCRF needs subscription-related information and does not have it + SPR-->>H-PCRF: 7. Profile Response + Note right of H-PCRF: 8. Identify affected IP CAN session(s) + H-PCRF->>V-PCRF: 9. Diameter AAA + V-PCRF->>AF: 10. Diameter AAA + Note right of BBERF: 11. Interactions in Figure 4.3.1.1.1 + +``` + +Sequence diagram for AF session establishment triggers PCRF-initiated IP-CAN Session Modification (AF in VPLMN). The diagram shows interactions between BBERF, PCEF, V-PCRF, H-PCRF, AF, and SPR. The AF sends a trigger to the V-PCRF, which stores service information and forwards it to the H-PCRF. The H-PCRF may request profile information from the SPR. The V-PCRF then identifies affected IP CAN sessions and sends Diameter AAA messages to the PCEF and BBERF. A callout indicates that if the PCRF needs subscription-related information and does not have it, it sends a profile request to the SPR. A legend indicates that solid arrows are mandatory and dashed arrows are conditional. + +**Figure 4.3.1.2.1.2.1: AF session establishment triggers PCRF-initiated IP-CAN Session Modification (AF in VPLMN)** + +- The AF receives an internal or external trigger to set-up a new AF session and provides Service Information. The AF identifies the Service Information needed (e.g. IP address of the IP flow (s), port numbers to be used, information on media types, etc). +- The AF provides the Service Information to the V-PCRF by sending a Diameter AAR for a new Rx Diameter session. If the AF session is associated with a sponsor, Sponsor-Identity AVP and Application-Service-Provider-Identity are included in Sponsored-Connectivity-Data AVP. If usage thresholds are to be associated with this sponsored AF session, then Granted-Service-Unit AVP is included in Sponsored-Connectivity-Data AVP. The AF can request access network information within the AAR by adding Required-Access-Info AVP(s) and Specific-Action AVP set to the value "ACCESS\_NETWORK\_INFO\_REPORT". If the Service can be subject to resource sharing, the AF includes the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP within the Media-Component-Description AVP. If PrioritySharing feature is supported and the service is allowed to use the same Allocation and Retention Priority (ARP) as media flows belonging to other AF sessions, the AF includes the Priority-Sharing-Indicator AVP set to PRIORITY\_SHARING\_ENABLED within the Media-Component-Description AVP. To invoke MPS for DTS, the AF includes the MPS-Action AVP within the AAR, as specified in clause 5.3. +- The V-PCRF stores the Service Information. +- The V-PCRF forwards the Diameter AAR to the H-PCRF. +- The H-PCRF stores the received Service Information. +- If the H-PCRF requires subscription-related information and does not have it, the H-PCRF sends a request to the SPR in order to receive the information. + +NOTE 1: The V-PCRF may employ operator policies and reject the AAR from the AF if the provided Service Information is not acceptable. If this happens, the V-PCRF replies immediately to the AF, includes an unsuccessful Result-Code or Experimental-Result-Code in the AAA, and the remaining steps of this call flow are not carried out. + +If the AF session is for MPS for DTS invocation, the PCRF performs MPS subscription checks if and only if requested by the AF, as described in subclause 4.4.11 of 3GPP TS 29.214 [10]. + +7. The SPR replies with the subscription related information containing the information about the allowed service(s), QoS information and PCC Rules information. + +NOTE 2: For steps 6 and 7: The details associated with the Sp reference point are not specified in this Release. The SPR's relation to existing subscriber databases is not specified in this Release. + +8. If the AF session is associated with a sponsor, the H-PCRF rejects the request. Otherwise, the H-PCRF stores the Service Information and identifies the affected established IP-CAN Session(s) using the information previously received from the PCEF via the V-PCRF and the Service Information received from the AF. +9. The H-PCRF responds to the V-PCRF with a Diameter AAA. The H-PCRF indicates whether the support for UE IP address/mask in the TFT filter is available in the IP-CAN session. +10. The V-PCRF forwards the Diameter AAA to the AF. +11. The H-PCRF interacts with the PCEF/BBERF via the V-PCRF according to figure 4.3.1.1.1 (Interactions between BBERF/PCEF and PCRF for PCRF-Initiated IP-CAN Session Modification). + +##### 4.3.1.2.2 AF session modification + +###### 4.3.1.2.2.1 AF located in the HPLMN + +![Sequence diagram for AF session modification triggers PCRF-Initiated IP-CAN Session Modification (AF in HPLMN).](e1a0d046fbe7f28f5e93a47091851747_img.jpg) + +The diagram illustrates a sequence of interactions between five network elements: BBERF, PCEF, V-PCRF, H-PCRF, and AF. The sequence is as follows: + +- The AF sends a "Trigger" message to the H-PCRF. +- The AF sends "Define service information" to the H-PCRF. +- The H-PCRF sends a "Diameter AAR" message to the V-PCRF. +- The V-PCRF performs "Store Service Information" internally. +- The V-PCRF performs "Identify affected IP CAN session(s)" internally. +- The H-PCRF sends a "Diameter AAA" message to the AF. +- A large box labeled "7. Interactions in Figure 4.3.1.1.1" spans across the bottom of the diagram, indicating further interactions between the BBERF, PCEF, and V-PCRF. + +Sequence diagram for AF session modification triggers PCRF-Initiated IP-CAN Session Modification (AF in HPLMN). + +**Figure 4.3.1.2.2.1.1: AF session modification triggers PCRF-Initiated IP-CAN Session Modification (AF in HPLMN)** + +1. The AF receives an internal or external trigger to modify an existing AF session and provide related Service Information. +2. The AF identifies the Service Information needed (e.g. IP address of the IP flow(s), port numbers to be used, information on media types, etc.). + +3. The AF provides the Service Information to the H-PCRF by sending a Diameter AAR for the existing Rx Diameter session corresponding to the modified AF session. If this AF session is associated with a sponsor, Sponsor-Identity AVP, optionally if the AF wants to enable sponsored dataconnectivity the Sponsoring-Action AVP set to the value "ENABLE\_SPONSORING" and Application-Service-Provider-Identity are included in Sponsored-Connectivity-Data AVP. If application usage thresholds are to be associated with this sponsored AF session, then Granted-Service-Unit AVP is included in Sponsored-Connectivity-Data AVP. If this AF session is associated with a sponsor and the AF wants to disable sponsored data connectivity the AF includes the Sponsoring-Action AVP set to the value "DISABLE\_SPONSORING" within the Sponsored-Connectivity-Data AVP. The AF can request access network information within the AAR by adding Required-Access-Info AVP(s) and Specific-Action AVP set to the value "ACCESS\_NETWORK\_INFO\_REPORT". If resource sharing conditions have been changed, the AF includes the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP within the Media-Component-Description AVP. If the service has negotiated the background data transfer policy, the AF includes the reference id of the transfer policy within the Reference-Id AVP. If PrioritySharing feature is supported and the service is allowed to use the same Allocation and Retention Priority (ARP) as media flows belonging to other AF sessions, the AF includes the Priority-Sharing-Indicator AVP within the Media-Component-Description AVP to indicate if priority sharing is enabled or disabled. The AF may also include the Pre-emption-Capability AVP and the Pre-emption-Vulnerability AVP within the Media-Component-Description AVP for the PCRF to determine the ARP values and include the Pre-emption-Control-Info AVP at the command level for the PCRF to perform the pre-emption control. If the CHEM feature is supported, the AF may also include the maximum packet loss rate(s) for uplink and/or downlink direction(s) in the Max-PLR-UL/DL AVP(s) respectively within the Media-Component-Description AVP. To invoke/revoke MPS for DTS, the AF includes the MPS-Action AVP within the AAR as specified in clause 5.3. +4. The H-PCRF stores the received Service Information. If the Reference-Id AVP is received, the PCRF retrieves the corresponding transfer policy from the SPR and derives the PCC rules for the background data transfer according to the transfer policy. + +If the AF session is for MPS for DTS invocation, the PCRF performs MPS subscription checks if and only if requested by the AF, as described in subclause 4.4.11 of 3GPP TS 29.214 [10]. + +5. If the AF session is associated with a sponsor and sponsored service is enabled, + - if the UE is in the non-roaming case or UE is roaming with the home routed case and operator policies allow accessing the sponsored data connectivity with this roaming case, the H-PCRF authorizes the request based on sponsored data connectivity profile obtained from the SPR; + - if the UE is roaming with the home routed case and operator policies do not allow accessing the sponsored data connectivity with this roaming case or the UE is roaming with the visited access case, the H-PCRF rejects the request. + +The H-PCRF identifies the affected established IP-CAN Session(s) using the information previously received from the PCEF/V-PCRF and the Service Information received from the AF. + +6. The H-PCRF sends a Diameter AAA to the AF. +7. The H-PCRF interacts with the BBERF/PCEF/V-PCRF according to figure 4.3.1.1.1. + +###### 4.3.1.2.2.2 + +###### AF located in the VPLMN + +![Sequence diagram for AF session modification triggers PCRF-Initiated IP-CAN Session Modification (AF in VPLMN).](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +The diagram illustrates a sequence of interactions between five network elements: BBERF, PCEF, V-PCRF, H-PCRF, and AF, under the heading "ROAMING CASE". + +- The AF sends a "1. Trigger" message to itself. +- The AF sends a "2. Define service information" message to itself. +- The AF sends a "3. Diameter AAR" message to the V-PCRF. +- The V-PCRF performs an internal action "4. Store Service Information". +- The V-PCRF sends a "5. Diameter AAR" message to the H-PCRF. +- The H-PCRF performs an internal action "6. Store Service Information". +- The H-PCRF performs an internal action "7. Identify affected IP CAN session(s)". +- The H-PCRF sends a "8. Diameter AAA" message to the V-PCRF. +- The V-PCRF sends a "9. Diameter AAA" message to the H-PCRF. +- A final box labeled "10. Interactions in Figure 4.3.1.1.1" spans across the bottom of the diagram, indicating further interactions. + +Sequence diagram for AF session modification triggers PCRF-Initiated IP-CAN Session Modification (AF in VPLMN). + +**Figure 4.3.1.2.2.2.1 AF session modification triggers PCRF-Initiated IP-CAN Session Modification (AF in VPLMN)** + +- The AF receives an internal or external trigger to modify an existing AF session and provide related Service Information. +- The AF identifies the Service Information needed (e.g. IP address of the IP flow(s), port numbers to be used, information on media types, etc.). If resource sharing conditions have been changed, the AF includes the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP within the Media-Component-Description AVP. If PrioritySharing feature is supported and the service is allowed to use the same Allocation and Retention Priority (ARP) as media flows belonging to other AF sessions, the AF may include the Priority-Sharing-Indicator AVP within the Media-Component-Description AVP to indicate if priority sharing is enabled or disabled. +- The AF provides the Service Information to the V-PCRF by sending a Diameter AAR for the existing Rx Diameter session corresponding to the modified AF session. If this AF session is associated with a sponsor, Sponsor-Identity AVP and Application-Service-Provider-Identity AVP are included in Sponsored-Connectivity-Data AVP. If usage thresholds are to be associated with this sponsored AF session, then Granted-Service-Unit AVP is included in Sponsored-Connectivity-Data AVP. The AF can request access network information within the AAR by adding Required-Access-Info AVP(s) and Specific-Action AVP set to the value "ACCESS\_NETWORK\_INFO\_REPORT". To invoke/revoke MPS for DTS, the AF includes the MPS-Action AVP within the AAR, as specified in clause 5.3. + +4. The V-PCRF stores the received Service Information. + +NOTE: The V-PCRF may employ operator policies and reject the AAR from the AF if the provided Service Information is not acceptable. If this happens, the V-PCRF replies immediately to the AF, includes an unsuccessful Result-Code or Experimental-Result-Code in the AAA, and the remaining steps of this call flow are not carried out. + +5. The V-PCRF forwards the Diameter AAR to the H-PCRF. + +6. The H-PCRF stores the received Service Information. + +If the AF session is for MPS for DTS invocation, the PCRF performs MPS subscription checks if and only if requested by the AF, as described in subclause 4.4.11 of 3GPP TS 29.214 [10]. + +7. The H-PCRF identifies the affected established IP-CAN Session(s) using the information previously received from the PCEF/V-PCRF and the Service Information received from the AF. + +8. The H-PCRF responds with a Diameter AAA. + +9. The V-PCRF forwards the Diameter AAA to the AF. + +10. The H-PCRF interacts with the BBERF/PCEF via the V-PCRF according to figure 4.3.1.1.1. + +##### 4.3.1.2.3 AF session termination + +###### 4.3.1.2.3.1 AF located in the HPLMN + +![Sequence diagram showing the removal of PCC/QoS rules at AF session release (AF in HPLMN).](536951b2bbd94325ae266d8d1363df8f_img.jpg) + +``` + +sequenceDiagram + participant AF + participant H-PCRF + participant V-PCRF + participant PCEF + participant BBERF + + Note right of AF: 1. Trigger + AF->>H-PCRF: 2. Diameter STR + Note right of H-PCRF: 3. Identify affected IP CAN session where PCC/QoS rules need to be removed. + H-PCRF->>AF: 4a. Diameter STA + Note left of BBERF: 5. Interactions in Figure 4.3.1.1.1 + H-PCRF->>AF: 4b. Diameter STA + +``` + +The diagram illustrates the sequence of interactions for AF session termination when the AF is located in the HPLMN. It involves five entities: BBERF, PCEF, V-PCRF, H-PCRF, and AF. The sequence starts with the AF sending a 'Trigger' (1) to the H-PCRF. The H-PCRF responds with a 'Diameter STR' (2). The H-PCRF then identifies the affected IP CAN session where PCC/QoS rules need to be removed (3). The H-PCRF sends a 'Diameter STA' (4a) to the AF. A callout box labeled '5. Interactions in Figure 4.3.1.1.1' spans across the bottom of the diagram, indicating further interactions between the H-PCRF and the BBERF/PCEF via the V-PCRF. Finally, the H-PCRF sends another 'Diameter STA' (4b) to the AF. + +Sequence diagram showing the removal of PCC/QoS rules at AF session release (AF in HPLMN). + +**Figure 4.3.1.2.3.1.1: Removal of PCC/QoS Rules at AF session release (AF in HPLMN)** + +1. The AF receives an internal or external trigger for a session release. + +2. The AF sends a session termination request, Diameter STR, to the H-PCRF to request the removal of the session. The AF can request access network information within the STR by adding a Required-Access-Info AVP. +3. The H-PCRF identifies the affected IP-CAN Session where PCC Rules and, if available, QoS Rules for the IP flow(s) of this AF session are installed. These PCC/QoS Rules need to be removed. + +If the AF session being terminated corresponds to a session that included the Priority-Sharing-Indicator AVP set to PRIORITY\_SHARING\_ENABLED within the Media-Component-Description AVP, if the related media flow(s) was in priority sharing with other media flows, the PCRF should readjust the Allocation and Retention Priority for the remaining services sharing priority. These PCC/QoS Rules may need to be modified. + +If the AF did not request access network information, and if no usage thresholds due to an AF session associated with a sponsor were provided that relate to the installed PCC rules and RAN-NAS-Cause feature is not supported, step 4a applies. If AF requested access network information, or usage thresholds due to an AF associated with a sponsor were provided that relate to the installed PCC rules, step 4b applies. If RAN-NAS-Cause is supported but Enh-RAN-NAS-Cause is not supported over Gx and the previous conditions do not apply, step 4a applies. Otherwise step 4b applies. + +- 4a. The H-PCRF sends Diameter STA, session termination answer, to the AF. +- 4b. The H-PCRF sends Diameter STA, session termination answer, to the AF and includes access network information and/or information about the resources that have been consumed by the user since the last report or RAN/NAS/TWAN/Untrusted WLAN release cause(s) if available obtained in step 5. +5. The H-PCRF interacts with the BBERF/PCEF/V-PCRF according to figure 4.3.1.1.1. + +###### 4.3.1.2.3.2 AF located in the VPLMN + +![Sequence diagram for the removal of PCC/QoS rules at AF session release (AF in VPLMN). The diagram shows interactions between BBERF, PCEF, V-PCRF, H-PCRF, and AF. The process starts with a trigger from the AF, followed by Diameter STR messages to the V-PCRF and then H-PCRF. The H-PCRF identifies the affected session. Diameter STA messages are then sent from the H-PCRF to the V-PCRF and from the V-PCRF to the AF. A callout box indicates that steps 5a, 5b, 6a, and 6b are part of the interactions shown in Figure 4.3.1.1.1. The diagram is labeled 'ROAMING CASE' on the left.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +``` + +sequenceDiagram + participant AF + participant H-PCRF + participant V-PCRF + participant PCEF + participant BBERF + + Note left of BBERF: ROAMING CASE + + AF->>AF: 1. Trigger + AF->>V-PCRF: 2. Diameter STR + V-PCRF->>H-PCRF: 3. Diameter STR + H-PCRF->>H-PCRF: 4. Identify affected IP CAN session where PCC/ QoS rules need to be removed + H-PCRF->>V-PCRF: 5a. Diameter STA + V-PCRF->>AF: 6a. Diameter STA + Note right of BBERF: 7. Interactions in Figure 4.3.1.1.1 + H-PCRF->>V-PCRF: 5b Diameter STA + V-PCRF->>AF: 6b Diameter STA + +``` + +Sequence diagram for the removal of PCC/QoS rules at AF session release (AF in VPLMN). The diagram shows interactions between BBERF, PCEF, V-PCRF, H-PCRF, and AF. The process starts with a trigger from the AF, followed by Diameter STR messages to the V-PCRF and then H-PCRF. The H-PCRF identifies the affected session. Diameter STA messages are then sent from the H-PCRF to the V-PCRF and from the V-PCRF to the AF. A callout box indicates that steps 5a, 5b, 6a, and 6b are part of the interactions shown in Figure 4.3.1.1.1. The diagram is labeled 'ROAMING CASE' on the left. + +**Figure 4.3.1.2.3.2.1: Removal of PCC/QoS Rules at AF session release (AF in VPLMN)** + +1. The AF receives an internal or external trigger for a session release. +2. The AF sends a session termination request, Diameter STR, to the V-PCRF to request the removal of the session. The AF can request access network information within the STR by adding a Required-Access-Info AVP. +3. The V-PCRF forwards the Diameter STR to the H-PCRF. +4. The H-PCRF identifies the affected IP-CAN Session where PCC Rules and, if available, QoS Rules for the IP flow(s) of this AF session are installed. These PCC/QoS Rules need to be removed. + +If the AF session being terminated corresponds to a session that included the Priority-Sharing-Indicator AVP set to PRIORITY\_SHARING\_ENABLED within the Media-Component-Description AVP, if the related media flow(s) was in priority sharing with other media flows, the PCRF should readjust the Allocation and Retention Priority for the remaining services sharing priority. These PCC/QoS Rules may need to be modified. + +Steps 5a and 6a apply if the AF did not request access network information + +- 5a. The H-PCRF sends Diameter STA, session termination answer, to the V-PCRF. + +6a. The V-PCRF forwards the Diameter STA to the AF. + +7. The H-PCRF interacts with the BBERF/PCEF via the V-PCRF according to figure 4.3.1.1.1. + +Steps 5b and 6b apply if the AF requested access network information + +5b. The H-PCRF sends Diameter STA, session termination answer, to the V-PCRF and includes access network information obtained in step 7. + +6b. The V-PCRF forwards the Diameter STA to the AF. + +### 4.3.2 PCEF –Initiated IP-CAN Session Modification (PCC Rule Provisioning in PULL Mode) + +#### 4.3.2.1 PCEF-initiated IP-CAN Session Modification. AF located in HPLMN. + +This flow shows the provisioning of PCC Rules and/or authorized QoS triggered by the PCEF. + +![Sequence diagram for PCEF-initiated IP-CAN Session Modification. Lifelines: BBERF, PCEF, TDF, TSSF, V-PCRF, H-PCRF, AF, SPR, OCS. The diagram shows a series of messages between these entities, with two 'VISITED ACCESS CASE' blocks highlighted in light blue. The process involves gateway control, QoS rule requests, session modifications, diameter messages (CCR, CCA, RAR, RAA, ASR, ASA, STR, STA), profile requests, spending limit reports, PCC/ADC rule decisions, and resource allocation confirmations.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +The sequence diagram illustrates the interaction for a PCEF-initiated IP-CAN Session Modification. The lifelines are BBERF, PCEF, TDF, TSSF, V-PCRF, H-PCRF, AF, SPR, and OCS. The process begins with a 'Gateway control and QoS Rule request (case 2a & case 2b)' from PCEF to BBERF. This is followed by an 'IP-CAN Session Modification' from BBERF to PCEF. The first 'VISITED ACCESS CASE' block (highlighted in light blue) includes: 'Diameter CCR' from PCEF to H-PCRF; 'Diameter CCR' from PCEF to V-PCRF; 'Store Information' (self-call on V-PCRF); 'Diameter CCR' from V-PCRF to H-PCRF; 'Profile Request' from H-PCRF to SPR; 'Profile Response' from SPR to H-PCRF; a group of messages (RAR, RAA, ASR, ASA, STR, STA) between H-PCRF and AF, with a note 'If a specific action is triggered for the AF session'; and another group of messages (STR, STA) between H-PCRF and AF, with a note 'If all session info for an AF session is decided'. Next is an 'Initial/Intermediate/Final Spending limit Report Request' from H-PCRF to OCS. Then 'PCC/ADC Rule Decision' from V-PCRF to H-PCRF, followed by 'Diameter CCA' from H-PCRF to V-PCRF. The second 'VISITED ACCESS CASE' block (highlighted in light blue) includes: 'Diameter CCA' from V-PCRF to H-PCRF; 'PCC/ADC Rules validation' (self-call on V-PCRF); 'Diameter CCA' from V-PCRF to PCEF; 'TDF session modification' (self-call on TDF); 'TDF session modification' from TDF to PCEF; 'Install, modify or remove PCC/ADC Rules' (self-call on TDF); 'St session establishment/modification/termination' (self-call on TDF); and 'IP-CAN Session modification signalling' from TDF to BBERF. The sequence concludes with 'Resource allocation confirmation (case 1)' from BBERF to PCEF and 'Gateway control & QoS Rule Provision (case 2a & case 2b)' from PCEF to BBERF. + +Sequence diagram for PCEF-initiated IP-CAN Session Modification. Lifelines: BBERF, PCEF, TDF, TSSF, V-PCRF, H-PCRF, AF, SPR, OCS. The diagram shows a series of messages between these entities, with two 'VISITED ACCESS CASE' blocks highlighted in light blue. The process involves gateway control, QoS rule requests, session modifications, diameter messages (CCR, CCA, RAR, RAA, ASR, ASA, STR, STA), profile requests, spending limit reports, PCC/ADC rule decisions, and resource allocation confirmations. + +Figure 4.3.2.1.1: PCEF-initiated IP-CAN Session Modification. AF in HPLMN. + +1. For case 2a and 2b, the BBERF may initiate Gateway Control and QoS rules request procedure described in subclause 4.4.2. +2. The PCEF may receive a request for IP-CAN Session modification. The IP-CAN session modification can be initiated upon receiving UE-initiated resource modification request (case 1), a new IP-CAN bearer establishment signalling (case 1), due to a specific event (e.g. UE requested PDN connectivity in all cases) or an internal trigger(e.g. if the PCEF supports Application Detection and Control feature, the start/stop of application traffic event that matches with one or more activated PCC rules for application detection and control that do not contain the Mute-Notification AVP has been detected by the PCEF). +3. The PCEF informs the H-PCRF about the IP-CAN session modification for non-roaming case and Home Routed roaming scenario. The PCEF sends a CCR command to the H-PCRF including the CC-Request-Type AVP set to the value “UPDATE\_REQUEST”. For an IP-CAN Session modification where an existing IP-CAN bearer is modified, the PCEF supplies the specific event that caused the IP-CAN Session modification within the Event-Trigger AVP and the PCC rule name(s) and their status within the Charging-Rule-Report AVP. For an IP-CAN Session modification where an existing IP-CAN bearer is terminated, the PCEF supplies the affected PCC rule name(s), their status set to inactive, the rule failure code and, if available, the RAN/NAS/TWAN/Untrusted WLAN cause(s) within the Charging-Rule-Report AVP. In the case where the UE initiates a resource modification request procedure, the PCEF includes the Packet-Filter-Information AVP, Packet-Filter-Operation AVP and QoS-Information AVP, if applicable. In the case of PCEF supporting Application Detection and Control feature, when the start or stop of the application’s traffic, identified by TDF-Application-Identifier, is detected, if PCRF has previously subscribed to the APPLICATION\_START/APPLICATION\_STOP Event-Triggers, the PCEF shall report the information regarding the detected application’s traffic in the Application-Detection-Information AVP in the CCR command. If NBIFOM applies to the IP-CAN session, if one of the conditions specified in subclause 4.5.25.2 of 3GPP TS 29.212 [9] applies, the PCEF informs the PCRF accordingly making use of the applicable event trigger, i.e. "ADDITION\_OF\_ACCESS", "REMOVAL\_OF\_ACCESS", "UNAVAILIBILITY\_OF\_ACCESS", "AVAILIBILITY\_OF\_ACCESS" or "ROUTING\_RULE\_CHANGE". + +When the UE is roaming in a Visited Access case, steps 3a ~ 3c are executed instead of step 3: + +- 3a. The PCEF sends a Diameter CCR to the V-PCRF to request PCC/ADD Rules for the roaming user. The parameters listed in step 3 are applicable here. + - 3b. The V-PCRF stores the information received in the Diameter CCR from the PCEF. + - 3c. The V-PCRF sends a CCR command with the CC-Request-Type AVP set to “UPDATE\_REQUEST” to the H-PCRF. The V-PCRF includes the Subsession-Enforcement-Info AVP and the assigned S9 subsession identifier within Subsession-Id AVP. The Subsession-Operation AVP is set to the value “MODIFICATION”. +4. If the H-PCRF requires subscription-related information and does not have it, the PCRF sends a request to the SPR in order to receive the information. + +5. The SPR replies with the subscription related information containing the information about the allowed service(s) and PCC Rules information. + +NOTE 1: For steps 4 and 5: The details associated with the Sp reference point are not specified in this Release. The SPR’s relation to existing subscriber databases is not specified in this Release. + +6. If the AF requested a notification of the corresponding event, the H-PCRF sends a Diameter RAR with the Specific-Action AVP set to indicate the event that caused the request. If the session modification affected a sponsored data flow and the H-PCRF detects that the usage threshold provided by the AF has been reached, this message includes the accumulated usage in the Used-Service-Unit AVP within the Sponsored-Connectivity-Data AVP and the Specific-Action AVP set to the value USAGE\_REPORT. + 7. If step 6 takes place, the AF may take the application specific procedure (e.g. for IMS refer to 3GPP TS 23.228 [59], replies with a Diameter RAA and may provide updated service information within. Additionally, the AF may terminate the Rx session as per subclause 4.3.1.2.3. +- 8-11.If all service data flows for an AF session are deleted, the AF session is terminated. If the session modification affected a sponsored data flow and the H-PCRF detects the UE is roaming with home routed case, the H-PCRF initiates the AF session termination. + +If the IP-CAN session is associated with a sponsor, usage thresholds were provided by the AF earlier, and the H-PCRF has usage data that has not yet been reported to the AF, the H-PCRF informs the AF2 in step 11, about the resources that have been consumed by the user since the last report. + +If RAN-NAS-Cause feature is supported and RAN/NAS/TWAN/Untrusted WLAN cause(s) and/or access network information were received in step 3, the H-PCRF sends this information to the AF in step 11. + +NOTE 2: Initial/intermediate/Final Spending Limit Report Request can be triggered at any time after this if PCRF, based on policy decisions, find the need to initialize, modify, or deactivate spending limit reporting for the subscriber according to subclause 4.7.1/2/3 respectively. + +12. The H-PCRF selects or generates PCC Rule(s) to be installed. The H-PCRF may also identify existing PCC rules that need to be modified or removed. In the case of VPLMN supporting Application Detection and Control feature for solicited application reporting, some of those PCC Rules may be used for application detection and control. The PCC Rules may relate to any of the matching AF sessions or may exist in the PCRF without matching to any AF session. The H-PCRF may also make a policy decision by deriving an authorized QoS and by deciding whether service data flows described in the PCC Rules are to be enabled or disabled. The H-PCRF may also update the ADC decisions and select the ADC rules to be installed, modified or removed for the IP-CAN session in the non-roaming case. If the NBIFOM applies to the IP-CAN session, the PCRF can also make a decision of NBIFOM as defined in subclause 4.5.25.2 of 3GPP TS 29.212 [9]. +13. For the non-roaming case, and for the case when the UE is roaming in a Home Routed scenario, the H-PCRF provisions the PCC Rules to the PCEF using CCA command. The H-PCRF also provides the selected Bearer Control Mode, if changed and applicable for the IP-CAN type. The PCRF may also provide a new list of event triggers for which the PCRF requires to be notified. The PCRF may provide QoS information within the APN-AMBR AVP and the Default-EPS-Bearer-QoS AVP. In the case of PCEF supporting Application Detection and Control feature, the H-PCRF may provision the PCC rules for application detection and control to the PCEF. + +When the UE is roaming in a Visited Access, steps 13a ~13c are executed instead of step 13: + +- 13a. The H-PCRF sends a Diameter CCA to the V-PCRF including the PCC Rules to be provisioned within the Subsession-Decision AVP, along with the S9 subsession identifier as received in step 3b within the Subsession-Id AVP. Other parameters listed in step 9 are also applicable here. + +- 13b. The V-PCRF validates the QoS parameters requested within the PCC Rules and enforces visited operator policies regarding QoS authorization requested by the H-PCRF as indicated by the roaming agreements. In case of TDF, the V-PCRF extracts and validates the ADC rules from the PCC rules received from the H-PCRF according to the local policy and roaming agreements if provided by the H-PCRF. + +NOTE: If the V-PCRF rejects provisioned PCC rules received from the H-PCRF, the remaining steps in this call flow are not followed. Instead, the V-PCRF shall notify the H-PCRF by sending a Diameter CCR, including the Experimental-Result-Code AVP set to the value PCC\_RULE\_EVENT, identify the failed PCC rules as specified in 3GPP TS 29.215 [22], and additionally may provide the acceptable QoS Information for the service. + +- 13c. The V-PCRF provisions PCC rules to the PCEF by using CCA command. The parameters listed in step 13a are applicable here. + +- 13d. In case of TDF, solicited application reporting, the V-PCRF provisions the ADC rules to the TDF as defined in subclause 4.6.3.2. In case of TDF, unsolicited application reporting, the V-PCRF initiates the TDF session termination as defined in clause 4.6.2 if the PCEF reported the UE\_IP\_ADDRESS\_RELEASE to the V-PCRF and there is an active Ipv4 address related TDF session for that IP-CAN session. + +14. In case of TDF, solicited application reporting, the H-PCRF provisions the ADC rules to the TDF as defined in subclause 4.6.3.2. In case of TDF, unsolicited application reporting, the H-PCRF initiates the TDF session termination as defined in subclause 4.6.2 if the PCEF reported the UE\_IP\_ADDRESS\_RELEASE to the H-PCRF and there is an active Ipv4 address related TDF session for that IP-CAN session. + +15. The PCEF installs, modifies or removes the provided PCC Rules. The PCEF also enforces the authorized QoS and enables or disables service flows according to the flow status of the corresponding PCC Rules. In the case of PCEF supporting Application Detection and Control feature, the PCEF enforces application detection and control. + +16. If traffic steering control over St applies, if the PCRF determines that the traffic steering control information needs to be provisioned for the IP-CAN session; the PCRF initiates the St session establishment procedure according to the subclause 4.9.2. If the PCRF determines that the traffic steering control information provisioned to the TSSF needs to be updated, the PCRF initiates the St session modification procedure according to the subclause 4.9.3. If the PCRF determines that the traffic steering control information is not needed for the IP-CAN session any more, the PCRF initiates the St session termination procedure according to the subclause 4.9.2. +17. The PCEF may initiate IP-CAN session signalling or acknowledges any IP-CAN Session signalling for IP-CAN Session modification received in step 2. +18. If the PCRF requested to confirm that the resources associated to a PCC Rule have been successfully allocated or the resource release procedure has concluded, the PCEF-initiated IP-CAN session modification procedure is performed again starting from step 3. +19. For case 2a and 2b, the PCRF may initiate Gateway Control and QoS rules Provision procedure described in subclause 4.4.3. + +#### 4.3.2.2 PCEF-initiated IP-CAN Session Modification, AF located in the VPLMN + +![Sequence diagram for PCEF-initiated IP-CAN Session Modification, AF located in the VPLMN. The diagram shows interactions between BBERF, PCEF, TDF, V-PCRF, H-PCRF, V-AF, and SPR. It includes steps 1-5, 2-9, 10-13, and 12-18 as specified in figure 4.3.2.1.1. A legend indicates that solid arrows are Mandatory and dashed arrows are Conditional.](10781f43062bf3e9601a1e086710556c_img.jpg) + +The sequence diagram illustrates the interaction between network elements for PCEF-initiated IP-CAN Session Modification. The lifelines are BBERF, PCEF, TDF, V-PCRF, H-PCRF, V-AF, and SPR. The process is divided into four main steps: + +- 1. Steps 1 to 5 as specified in figure 4.3.2.1.1.** +- 2. Diameter ASR:** A conditional message from H-PCRF to V-PCRF. +- 3. Diameter ASR:** A conditional message from V-PCRF to V-AF. +- 4. Diameter ASA:** A conditional message from V-AF to V-PCRF. +- 5. Diameter ASA:** A conditional message from V-PCRF to H-PCRF. +- 6. Diameter STR:** A conditional message from H-PCRF to V-PCRF. +- 7. Diameter STR:** A conditional message from V-PCRF to V-AF. +- 8. Diameter STA:** A conditional message from V-AF to V-PCRF. +- 9. Diameter STA:** A conditional message from V-PCRF to H-PCRF. +- 10. Diameter RAR:** A conditional message from H-PCRF to V-PCRF. +- 11. Diameter RAR:** A conditional message from V-PCRF to V-AF. +- 12. Diameter RAA:** A conditional message from V-AF to V-PCRF. +- 13. Diameter RAA:** A conditional message from V-PCRF to H-PCRF. +- 14. Steps 12 to 18 as specified in figure 4.3.2.1.1.** + +Annotations on the right side of the diagram: + +- For steps 2-9: "If all session info for an AF session is deleted" +- For steps 10-13: "If a specific action is triggered for the AF session" + +**Legend:** + +- Solid arrow: **Mandatory** +- Dashed arrow: **Conditional** + +Sequence diagram for PCEF-initiated IP-CAN Session Modification, AF located in the VPLMN. The diagram shows interactions between BBERF, PCEF, TDF, V-PCRF, H-PCRF, V-AF, and SPR. It includes steps 1-5, 2-9, 10-13, and 12-18 as specified in figure 4.3.2.1.1. A legend indicates that solid arrows are Mandatory and dashed arrows are Conditional. + +**Figure 4.3.2.2.1: PCEF-initiated IP-CAN Session Modification, AF in VPLMN. If the AF resides in the VPLMN, the V-PCRF proxies the AF session signalling over S9 between the V-AF and the H-PCRF.** + +1. Steps 1 to 5 in figure 4.3.2.1.1 are executed. + +When all PCC Rules related to a particular AF session are removed, the H-PCRF initiates the AF session termination procedure. For each AF session bound to the modified IP-CAN session that is being removed, steps 2-9 are executed instead of steps 10-13: + +2. The H-PCRF indicates the session abort to the V-PCRF by sending a Diameter ASR to the V-PCRF. +3. The V-PCRF proxies the Diameter ASR command to the V-AF. +4. The V-AF responds by sending a Diameter ASA command to the V-PCRF. + +5. The V-PCRF proxies the ASA command to the H-PCRF. +6. The V-AF sends a Diameter STR command to the V-PCRF to indicate that the session has been terminated. +7. The V-PCRF proxies the Diameter STR command to the H-PCRF. +8. The V-PCRF proxies the Diameter STA command to the V-AF. +9. The H-PCRF responds by sending a Diameter STA command. + +When the H-PCRF receives event triggers related to specific actions that the AF has subscribed to, the H-PCRF initiates the AF session modification procedure to notify the AF of these specific actions. For each Afssession bound to the modified IP-CAN session that has subscribed to these specific actions, steps 10-13 are executed instead of steps 2-9: + +10. If the H-PCRF is notified of an event in the access network that has to be notified to the V-AF for an AF session, the H-PCRF informs of the event by sending a RAR command to the V-PCRF. +11. The V-PCRF proxies the RAR command to the V-AF. +12. The V-AF responds by sending a RAA command to the V-PCRF. +13. The V-PCRF proxies the RAA to the H-PCRF. +14. Steps 12 to 18 in figure 4.3.2.1.1 are executed. + +## 4.4 Gateway Control Session Procedures + +There are two kinds of Gateway Control (GC) sessions: + +- A Gateway Control session that serves a single IP-CAN session (e.g. S-GW/BBERF connecting to PDN-GW using S5/S8 PMIP according to 3GPP TS 23.402 [21]). +- A Gateway Control session that serves all the IP-CAN sessions from the same Care-of address of the UE (e.g. a UE connecting to PDN-GW using S2c according to 3GPP TS 23.402 [21]). + +These Gateway Control sessions are initiated in connection with IP-CAN session establishment and Initial Attach respectively. For the first case, the PCRF will identify that the GC session serves a single IP-CAN session based on the PDN Identifier received in the request. + +An access network may support mobility with BBERF change. The new BBERF shall establish new Gateway Control sessions according to the procedures defined for the new access type and the PCRF shall correlate those sessions with ongoing IP-CAN sessions as part of the handover procedure. + +These scenarios are shown separately in different flows. + +In the following procedures, the V-PCRF is included to depict the roaming scenarios. H-PCRF will act as a PCRF for non-roaming Ues. The procedure to detect that the IP-CAN Session is restricted to Emergency Services is described in 3GPP TS 29.212 [9]. + +### 4.4.1 Gateway Control Session Establishment + +![Sequence diagram for Gateway Control Session Establishment. Lifelines: BBERF, PCEF, V-PCRF, H-PCRF, SPR. The diagram shows two main cases: non-roaming and roaming. In the non-roaming case, BBERF sends a CCR to H-PCRF, which responds with a CCA. In the roaming case, BBERF sends a CCR to V-PCRF, which then forwards it to H-PCRF via another CCR. H-PCRF may interact with SPR for profile information. Responses are passed back through the chain. A legend indicates solid arrows are 'Mandatory' and dashed arrows are 'Conditional'. A note indicates that steps 4 and 5 are conditional if the PCRF needs subscription-related information and does not have it.](a3472689858b068ef469213682965325_img.jpg) + +The sequence diagram illustrates the Gateway Control Session Establishment process between the BBERF, PCEF, V-PCRF, H-PCRF, and SPR. The process is divided into two main scenarios: non-roaming and roaming. + +- Non-roaming Case:** + - The BBERF receives a message or indication to establish a Gateway Control session (Step 1). + - It sends a Diameter CCR to the H-PCRF (Step 2). + - The H-PCRF responds with a Diameter CCA (Step 8). + - The BBERF then installs QoS rules and policy enforcement (Step 9). + - Finally, it sends an Establish Gateway Control Session Response (Step 10). +- Roaming Case:** + - The BBERF sends a Diameter CCR to the V-PCRF (Step 2a). + - The V-PCRF stores information (Step 2b) and sends a Diameter CCR to the H-PCRF (Step 2c). + - The H-PCRF stores information (Step 3) and may send a Profile Request to the SPR (Step 4). + - The SPR responds with a Profile Response (Step 5). + - The H-PCRF then makes a PCC Rules Decision and Policy Decision (Step 6) and stores PCC Rules (Step 7). + - It sends a Diameter CCA back to the V-PCRF (Step 8). + - The V-PCRF stores PCC Rules and Policy decision (Step 8b) and sends a Diameter CCA back to the BBERF (Step 8e). + - The BBERF then installs QoS rules and policy enforcement (Step 9). + - Finally, it sends an Establish Gateway Control Session Response (Step 10). + +**Legend:** + +- Mandatory:** Solid arrow +- Conditional:** Dashed arrow + +*Note: If the PCRF needs subscription-related information and does not have it, steps 4 and 5 are conditional.* + +Sequence diagram for Gateway Control Session Establishment. Lifelines: BBERF, PCEF, V-PCRF, H-PCRF, SPR. The diagram shows two main cases: non-roaming and roaming. In the non-roaming case, BBERF sends a CCR to H-PCRF, which responds with a CCA. In the roaming case, BBERF sends a CCR to V-PCRF, which then forwards it to H-PCRF via another CCR. H-PCRF may interact with SPR for profile information. Responses are passed back through the chain. A legend indicates solid arrows are 'Mandatory' and dashed arrows are 'Conditional'. A note indicates that steps 4 and 5 are conditional if the PCRF needs subscription-related information and does not have it. + +**Figure 4.4.1.1 Gateway Control Session Establishment.** + +- The BBERF receives a message or indication that it needs to establish a Gateway Control session. + For case 2a, as defined in clause 4.0, the BBERF detects that a UE has been assigned a Local IP address that the UE may use as a Care-of Address in MIP registrations (see 3GPP TS 23.402 [21], clause 6.3). + For case 2b, as defined in clause 4.0, the BBERF detects that the UE requests an IP-CAN session to be established (see 3GPP TS 23.402 [21], clauses 4.5.2 and 5.6.1) or, at BBERF relocation, to be resumed with a certain APN (see 3GPP TS 23.402 [21], clauses 5.7.1 and 5.7.2) or the UE requests a pre-registration with this BBERF (see 3GPP TS 23.402 [21], clause 9.3.1). +- For the non-roaming case, the BBERF initiates a Gateway Control session with the H-PCRF by sending a CCR to the H-PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The BBERF provides UE identity information and the IP-CAN type, User Location Information, User CSG Information (if received from the access network) and the indication of the BBERF support for the extended TFT filters. + For case 2a, as defined in clause 4.0, the BBERF provides the CoA assigned to the UE. + For case 2b, as defined in clause 4.0, the BBERF provides the PDN identifier and PDN connection identifier, if + +multiple PDN connections for the same APN are supported and, if applicable, a Session-Linking-Indicator to indicate if the session linking has to be deferred. The BBERF provides, when available, the APN-AMBR and Default-EPS-Bearer-QoS. + +NOTE: The BBERF support is a prerequisite for the PCRF enabling the possibility for usage of the extended TFT filter in the IP-CAN session(s). + +If applicable for the IP-CAN type, the BBERF additionally provides Network-Request-Support AVP to indicate whether NW-initiated procedures are supported. + +When the UE is roaming, the steps 2a-2c are executed instead of step 2: + +2a. The BBERF initiates a Gateway Control session with the V-PCRF by sending a CCR to the V-PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The BBERF provides UE identity information and the IP-CAN type, User Location Information and User CSG Information (if received from the access network). + +For case 2a, as defined in clause 4.0, the BBERF provides the CoA assigned to the UE. + +For case 2b, as defined in clause 4.0, the BBERF provides the PDN identifier and, if applicable, a Session-Linking-Indicator AVP to indicate if the session linking has to be deferred. The BBERF provides, when available, the APN-AMBR and Default-EPS-Bearer-QoS. + +If applicable for the IP-CAN type, the BBERF additionally provides Network-Request-Support AVP to indicate whether NW-initiated procedures are supported. + +2b. The V-PCRF determines based on the UE identity information that the request is for a roaming user. The V-PCRF checks whether the V-PCRF needs to send the CCR to the H-PCRF based on the roaming agreements. For the Visited Access case, the V-PCRF does not send the CCR to the H-PCRF if the Session-Linking-Indicator AVP was received indicating that the session linking has to be deferred. + +NOTE: If the V-PCRF does not send the CCR to the H-PCRF, the PCRF may generate QoS rules based on VPLMN roaming agreements. + +2c. For case 2a: + +- If there is not an already established S9 session for this roaming user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The V-PCRF includes in the CCR the information received in step 2a. +- If there is an already established S9 session for this roaming user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes in the CCR the information received in step 2a. + +For case 2b and for the visited case or for the home routed case and if the Session-Linking-Indicator AVP is not received or it indicates SESSION\_LINKING\_IMMEDIATE, the following procedures apply: + +- If there is not an already established S9 session for this roaming user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this Gateway Control Session within the Subsession-Id AVP, and the Subsession-Operation AVP set to the value ESTABLISHMENT. +- If there is an already established S9 session for this roaming user and not an already established S9 subsession for the PDN connection corresponding to the Gateway Control Session, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this Gateway Control Session within the Subsession-Id AVP, and the Subsession-Operation AVP set to the value ESTABLISHMENT. +- If there is an already established S9 session for this roaming user and an already established S9 subsession for the PDN connection corresponding to the Gateway Control Session, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR command with the S9 subsession identifier assigned by the V-PCRF for this Gateway Control Session within the Subsession-Id AVP, the Subsession-Operation AVP set to the value MODIFICATION, and the BBERF identity within AN-GW-Address AVP. + +For case 2b and for the home routed case and if the Session-Linking-Indicator AVP was received indicating that the session linking has to be deferred, following procedure applies: + +- The V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this Gateway Control Session within the Subsession-Id AVP, the Subsession-Operation AVP set to the value ESTABLISHMENT and the Session-Linking-Indicator AVP set to the value "SESSION\_LINKING\_DEFERRED". +3. The H-PCRF stores the information received in the CCR. The H-PCRF determines the network scenario that applies (case 2a or 2b) as described in clause 4.0. + +For case 2a, the H-PCRF may correlate the UE identity information with already established Gx sessions for the same UE. + +For case 2b, for non roaming case, the H-PCRF links the Gateway Control session with the already established Gx Session and acts as follows: + +- if the Session-Linking-Indicator was received indicating that the session linking has to be deferred, defers the session linking till the associated IP-CAN session establishment or modification is received. + - if the Session-Linking-Indicator was not received or indicates that the session linking has to be performed immediately, links the Gateway Control session with the already established Gx Session. +4. If the H-PCRF requires subscription-related information and does not have it, the H-PCRF sends a request to the SPR in order to receive the information. +5. The SPR replies with the subscription related information containing the information about the allowed service(s), QoS information, PCC Rules information and may include MPS EPS Priority, MPS Priority Level and IMS Signalling Priority of establishment a PS session with priority. + +NOTE: For steps 4 and 5: The details associated with the Sp reference point are not specified in this Release. The SPR's relation to existing subscriber databases is not specified in this Release. + +6. For case 2a, the H-PCRF may prepare for the installation of QoS rules if available; + +For case 2b, the H-PCRF may + +- At IP-CAN session establishment, if the session linking was not deferred, select or generate and store PCC Rule(s) in preparation for the anticipated Gx session and derive the QoS rules from them. If MPS EPS Priority, MPS Priority Level, and IMS Signalling Priority are present for the user, the PCRF takes the information into account. If the session linking was deferred, the PCC rules are not generated; + - At BBERF relocation and at pre-registration, if the Session-Linking-Indicator was not received or indicates that the session linking has to be performed immediately, prepare for the installation of QoS rules, derived from the active PCC rules, at the target BBERF; +7. The H-PCRF stores the selected QoS Rules and PCC Rules. If applicable the H-PCRF selects the Bearer Control Mode that will apply during the Gateway Control session. +8. For the non-roaming case, the H-PCRF acknowledges the Gateway Control Session by sending a CCA to the BBERF. The H-PCRF includes: +- The selected BCM, if applicable for the IP-CAN type + - If NW-initiated procedures are available, the available QoS rules + - If BCM is UE-only, the QoS rules that correspond to the request from the BBERF + - Default-EPS-Bearer-QoS and APN-AMBR when applicable + - The event triggers + +When the UE is roaming, the steps 8a-8e are executed instead of step 8: + +- 8a. The H-PCRF acknowledges the Gateway Control Session by sending a CCA to the V-PCRF. The H-PCRF includes + +- The selected BCM, if applicable for the IP-CAN type + - If NW-initiated procedures are available, the available QoS rules for the home routed case or the available PCC rules for the visited access case + - If BCM is UE-only, the QoS rules that correspond to the request from the V-PCRF for the home routed case or the PCC rules that correspond to the request from the V-PCRF for the visited access case + - For the case 2a, the QoS rules when the available QoS rules are not related to any IP-CAN session + - Default-EPS-Bearer-QoS and APN-AMBR when applicable + - Event triggers +- 8b. The V-PCRF enforces visited operator policies regarding QoS authorization requested by the H-PCRF as indicated by the roaming agreements. +- 8c. If the V-PCRF denies an authorization, it informs the H-PCRF and may provide the acceptable QoS Information for the service. +- 8d. The H-PCRF may provide new or modified QoS rules to the V-PCRF +- 8e. If V-PCRF receives the PCC rules from the H-PCRF, the V-PCRF extracts the QoS rules from the PCC rules. The V-PCRF acknowledges the Gateway Control Session establishment by sending a CCA to the BBERF. The V-PCRF includes the selected BCM if applicable for the IP-CAN type, any applicable QoS rules and event triggers. +9. The BBERF installs and enforces the received QoS Rules. +10. The BBERF sends an Establish Gateway Session Control Response to ack the Gateway Control Session Request. + +### 4.4.2 Gateway Control and QoS Rules Request + +#### 4.4.2.1 Non-Roaming and Home Routed cases + +![Sequence diagram for Gateway Control and QoS Rules Request for non-roaming and home routed cases. The diagram shows interactions between BBERF, PCEF, V-PCRF, and H-PCRF. It is divided into two shaded regions: 'Roaming case (home routed)' and 'Non-Roaming and Home Routed cases' (implied by the title).](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +``` + +sequenceDiagram + participant BBERF + participant PCEF + participant V-PCRF + participant H-PCRF + + Note left of BBERF: 1. Trigger to request QoS rules or report event + BBERF->>H-PCRF: 2. Diameter CCR + Note right of V-PCRF: 2b. Store information + Note left of BBERF: Roaming case (home routed) + BBERF->>V-PCRF: 2a. Diameter CCR + V-PCRF->>H-PCRF: 2c. Diameter CCR + Note right of H-PCRF: 3. Store information and update QoS rules + H-PCRF->>BBERF: 4. Diameter CCA + Note right of V-PCRF: 4b. Extract QoS rules + Note left of BBERF: Roaming case (home routed) + V-PCRF->>H-PCRF: 4a. Diameter CCA + V-PCRF->>BBERF: 4c. Diameter CCA + Note left of BBERF: 5. Install and update QoS rules + +``` + +Sequence diagram for Gateway Control and QoS Rules Request for non-roaming and home routed cases. The diagram shows interactions between BBERF, PCEF, V-PCRF, and H-PCRF. It is divided into two shaded regions: 'Roaming case (home routed)' and 'Non-Roaming and Home Routed cases' (implied by the title). + +**Figure 4.4.2.1.1: Gateway Control and QoS Rules Request for non-roaming and home routed** + +1. The BBERF is triggered to either report an event or obtain QoS rules or both for a gateway control session. +2. The BBERF sends a Diameter CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST to report event or request QoS rules. + +When the UE is roaming (home routed traffic), steps 2a ~ 2c are executed instead of step 2: + +- 2a. The BBERF sends a Diameter CCR to the V-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST to report event or request QoS rules. +- 2b. The V-PCRF stores the information received. +- 2c. For case 2a, The V-PCRF sends a Diameter CCR to the H-PCRF within the information received in step 2a at command level. + +For case 2b, The V-PCRF sends a Diameter CCR to the H-PCRF within the information received in step 2a at Subsession-Enforcement-Info AVP. + +3. The H-PCRF stores the received information in the Diameter CCR and derives updated QoS rules and event triggers. +4. The H-PCRF provisions the updated QoS rules and event triggers to the BBERF using Diameter CCA. The CCA may also only acknowledge that the event report has been received successfully. + +When the UE is roaming (home routed traffic), steps 4a ~ 4c are executed instead of step 4: + +- 4a. The H-PCRF sends the updated QoS rules and event triggers to the V-PCRF using Diameter CCA. The CCA may also only acknowledge that the event report has been received successfully. + - 4b. The V-PCRF may also perform further authorization of the rules based on local policies. + - 4c. The V-PCRF sends the updated QoS rules and event triggers to the BBERF using Diameter CCA. +5. The BBERF installs the received QoS Rules and event triggers. This may result in bearer binding being performed according to the rules. The BBERF also enables or disables service flow according to the flow status of the corresponding QoS Rules. The result of the QoS rule activation may trigger the BBERF to send an additional Diameter CCR as described above to the PCRF, for example, to indicate that QoS rule activation has failed. + +#### 4.4.2.2 Visited access cases + +![Sequence diagram for Gateway Control and QoS Rules Request for visited access. The diagram shows interactions between BBERF, PCEF, V-PCRF, and H-PCRF. The process starts with a trigger at the BBERF, followed by a Diameter CCR to the V-PCRF. The V-PCRF stores information and updates QoS rules. It then sends a Diameter CCR to the H-PCRF (conditional), which stores information and updates PCC rules. The H-PCRF sends a Diameter CCA back to the V-PCRF (conditional). The V-PCRF then stores information and extracts QoS rules. Finally, the V-PCRF sends a Diameter CCA back to the BBERF, which installs and updates QoS rules. A legend indicates that solid lines are mandatory and dashed lines are conditional.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +``` + +sequenceDiagram + participant BBERF + participant PCEF + participant V-PCRF + participant H-PCRF + + Note left of BBERF: 1. Trigger to request QoS rules or report event + BBERF->>V-PCRF: 2. Diameter CCR + Note right of V-PCRF: 3. Store information and update QoS rules + Note right of V-PCRF: 3a. Diameter CCR + V-PCRF-->>H-PCRF: 3a. Diameter CCR + Note right of H-PCRF: 3b. Store information and update PCC rules + Note right of H-PCRF: 3c. Diameter CCA + H-PCRF-->>V-PCRF: 3c. Diameter CCA + Note right of V-PCRF: 3d. Store information and Extract QoS rules + V-PCRF->>BBERF: 4. Diameter CCA + Note left of BBERF: 5. Install and update QoS rules + +``` + +**Legend** + +- Mandatory** (solid line) +- Conditional** (dashed line) + +Sequence diagram for Gateway Control and QoS Rules Request for visited access. The diagram shows interactions between BBERF, PCEF, V-PCRF, and H-PCRF. The process starts with a trigger at the BBERF, followed by a Diameter CCR to the V-PCRF. The V-PCRF stores information and updates QoS rules. It then sends a Diameter CCR to the H-PCRF (conditional), which stores information and updates PCC rules. The H-PCRF sends a Diameter CCA back to the V-PCRF (conditional). The V-PCRF then stores information and extracts QoS rules. Finally, the V-PCRF sends a Diameter CCA back to the BBERF, which installs and updates QoS rules. A legend indicates that solid lines are mandatory and dashed lines are conditional. + +**Figure 4.4.2.2.1: Gateway Control and QoS Rules Request for visited access** + +1. The BBERF is triggered to either report an event or obtain QoS rules or both for a gateway control session. +2. The BBERF sends a Diameter CCR to the V-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST to report event or request QoS rules. +3. The V-PCRF stores the information received in the Diameter CCR and derives updated QoS rules and event triggers according to local policies and roaming agreements. + +When the report event is subscribed by H-PCRF, the steps 3a~3d are executed instead of step3: + +- 3a. The V-PCRF sends a Diameter CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST to report event. + +For case 2a, the information received in step 2 is send to H-PCRF at command level. + +For case 2b, the CCR is send with the information provided at subsession level within the Subsession-Enforcement-Info AVP. + +- 3b. The H-PCRF stores the received information in the Diameter CCR and derives event triggers. +- 3c. The H-PCRF sends the event triggers to the V-PCRF using Diameter CCA. The CCA may also only acknowledge that the event report has been received successfully. +- 3d. The V-PCRF may also perform further authorization of the rules based on local policies. +- 4. The V-PCRF provisions the updated QoS rules and event triggers to the BBERF using Diameter CCA. +- 5. The BBERF installs the received QoS Rules and event triggers. This may result in bearer binding being performed according to the rules. The BBERF also enables or disables service flow according to the flow status of the corresponding QoS Rules. The result of the QoS rule activation may trigger the BBERF to send an additional Diameter CCR as described above to the PCRF, for example, to indicate that QoS rule activation has failed. + +### 4.4.3 Gateway Control and QoS Rules Provision + +Since the PCRF is required to keep QoS rules aligned with the active PCC rules for a certain IP-CAN session, it shall initiate the Gateway Control and QoS Rules Provision whenever there is a change to the corresponding PCC rules for a Gx session that is linked with the Gateway Control Session. + +![Sequence diagram for Gateway Control and QoS Rules Provision showing interactions between BBERF, PCEF, V-PCRF, and H-PCRF. The diagram includes steps for triggering updates, sending Diameter RAR/RAA messages, and handling roaming cases.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` + +sequenceDiagram + participant BBERF + participant PCEF + participant V-PCRF + participant H-PCRF + + Note right of H-PCRF: 1. Trigger to update QoS rules + H-PCRF->>BBERF: 2. Diameter RAR + Note right of V-PCRF: 2b. Identify the gateway control session and perform authorization + Note over BBERF, PCEF, V-PCRF: Roaming case + V-PCRF->>V-PCRF: 2a. Diameter RAR + V-PCRF->>BBERF: 2c. Diameter RAR + Note left of BBERF: 3. Install/Update QoS rules + BBERF->>H-PCRF: 4. Diameter RAA + Note over BBERF, PCEF, V-PCRF: Roaming case + BBERF->>V-PCRF: 4a. Diameter RAA + V-PCRF->>H-PCRF: 4b. Diameter RAA + Note left of BBERF: 5. Access specific procedures to modify bearers + +``` + +Sequence diagram for Gateway Control and QoS Rules Provision showing interactions between BBERF, PCEF, V-PCRF, and H-PCRF. The diagram includes steps for triggering updates, sending Diameter RAR/RAA messages, and handling roaming cases. + +**Figure 4.4.3.1: Gateway Control and QoS Rules Provision** + +- 1. The H-PCRF receives an internal or external trigger to update QoS Rules and event triggers for a gateway control session. If the trigger is from the AF and the AF requests the access network information, the H-PCRF applies the procedure as defined in clause 4a.5.16 of 3GPP TS 29.212 [9] to request the access network + +information. If the trigger is from the AF and the AF provided the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP within the Media-Component-Description AVP, the H-PCRF may apply the procedures as defined in clause 4a.5.10.6 of 3GPP TS 29.212 [9] to request the resource sharing. + +2. The H-PCRF sends a Diameter RAR to request that the BBERF installs, modifies or removes QoS Rules and/or updates the event triggers. + +If the UE is roaming, then steps 2a ~ 2c are executed instead of step 2: + +- 2a. The H-PCRF sends a Diameter RAR to the V-PCRF to provision updated QoS Rules and updated event triggers. + +For case 2a, the RAR provides the updated QoS Rules and updated event triggers with the information included at command level. + +For case 2b, The H-PCRF sends a Diameter RAR to the V-PCRF within the information at Subsession-Decision-Info AVP. + +- 2b. The V-PCRF identifies the gateway control session if needed and performs local authorization of the updated QoS rules when necessary. + +- 2c. The V-PCRF sends a Diameter RAR to the BBERF to provision updated QoS rules and updated event triggers. + +3. The BBERF installs, modifies or removes the identified QoS Rules. The BBERF also enforces the authorized QoS and enables or disables service flow according to the flow status of the corresponding QoS Rules. +4. The BBERF sends RAA to the H-PCRF to acknowledge the RAR and informs the H-PCRF about the outcome of the QoS rule operation. If network initiated resource allocation procedures apply for the QoS rules and the corresponding IP-CAN bearer can not be established or modified to satisfy the bearer binding, then the BBERF rejects the activation of a PCC rule. + +If the UE is roaming, then steps 4a ~ 4b are executed instead of step 4: + +- 4a. The BBERF sends RAA to the V-PCRF to acknowledge the RAR and informs the V-PCRF about the outcome of the QoS rule operation. If network initiated resource allocation procedures apply for the QoS rules and the corresponding IP-CAN bearer can not be established or modified to satisfy the bearer binding, then the BBERF rejects the activation of a PCC rule. + - 4b. The V-PCRF forwards the RAA to the H-PCRF to acknowledge the RAR and informs the H-PCRF about the outcome of the QoS rule operation. +5. If needed, the BBERF initiates the access specific procedures to create or modify existing IP-CAN bearers. When the procedure in step 5 is completed and requires of notifications from the BBERF to the PCRF, e.g. in the case of access network information, the steps described as in clause 4.4.2 are additionally executed. + +### 4.4.4 Gateway Control Session Termination + +#### 4.4.4.1 BBERF-Initiated Gateway Control Session Termination + +This procedure applies for case 2b, as defined in clause 4.0, whenever the BBERF detects a request for a PDN disconnection, mobility to other access or the termination of a pre-registration at the BBERF. + +![Sequence diagram showing the interaction between BBERF, PCEF, V-PCRF, and H-PCRF for a Gxx session removal. The process involves Diameter CCR and CCA messages, with specific steps for roaming cases involving IP-CAN session updates.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` +sequenceDiagram + participant External + participant BBERF + participant PCEF + participant V-PCRF + participant H-PCRF + + Note left of BBERF: Roaming case + External->>BBERF: 1. Remove Gxx Session Request + BBERF->>H-PCRF: 2. Diameter CCR + H-PCRF->>V-PCRF: 2a. Diameter CCR + V-PCRF->>H-PCRF: 2b. Diameter CCR + Note right of H-PCRF: 3. Identify related IP-CAN session and perform update as needed. + H-PCRF->>BBERF: 4. Diameter CCA + Note left of BBERF: Roaming case + H-PCRF->>V-PCRF: 4a. Diameter CCA + Note right of V-PCRF: 4b. Identify related IP-CAN session and perform update if needed + V-PCRF->>BBERF: 4c. Diameter CCA + BBERF->>External: 5. Remove Gxx Session Reply +``` + +The sequence diagram illustrates the interaction between four network elements: BBERF, PCEF, V-PCRF, and H-PCRF. The process begins with an external 'Remove Gxx Session Request' sent to the BBERF. The BBERF then sends a 'Diameter CCR' (2.) to the H-PCRF. This is followed by a 'Diameter CCR' (2a.) from the H-PCRF to the V-PCRF. The V-PCRF sends a 'Diameter CCR' (2b.) back to the H-PCRF. The H-PCRF then performs an internal step to 'Identify related IP-CAN session and perform update as needed.' (3.). The H-PCRF sends a 'Diameter CCA' (4.) back to the BBERF. In a 'Roaming case', the H-PCRF also sends a 'Diameter CCA' (4a.) to the V-PCRF. The V-PCRF then performs an internal step to 'Identify related IP-CAN session and perform update if needed' (4b.). Finally, the V-PCRF sends a 'Diameter CCA' (4c.) to the BBERF, which then sends the 'Remove Gxx Session Reply' (5.) to the external entity. + +Sequence diagram showing the interaction between BBERF, PCEF, V-PCRF, and H-PCRF for a Gxx session removal. The process involves Diameter CCR and CCA messages, with specific steps for roaming cases involving IP-CAN session updates. + +###### Figure 4.4.4.1.1: BBERF-Initiated Gateway Control Session Termination + +1. The BBERF is requested to terminate its gateway control session. The form of the request to remove the gateway control session depends upon the type of the IP-CAN. +2. The BBERF sends a Diameter CCR message to the H-PCRF, indicating the gateway control session termination. The BBERF requests the termination of the DCC session using the CC-Request-Type AVP set to the value TERMINATION\_REQUEST. + +If the UE is roaming, then steps in 2a ~ 2b are executed instead of step 2: + +- 2a. The BBERF sends a Diameter CCR message to the V-PCRF, indicating the gateway control session termination. The BBERF requests the termination of the DCC session using the CC-Request-Type AVP set to the value TERMINATION\_REQUEST. +- 2b. For the case 2a or if this is the last subsession associated with the S9 session for the case 2b, the V-PCRF sends a Diameter CCR message to the H-PCRF to request the termination of the S9 session. Otherwise, if the gateway control session is locally handled at the V-PCRF, the V-PCRF continues from step 4b; if the gateway control session has a corresponding S9 subsession, then the V-PCRF sends a Diameter CCR message to the H-PCRF to request the termination of the corresponding S9 subsession. + +3. The H-PCRF identifies the related IP-CAN session and performs update as necessary. +4. The H-PCRF acknowledges the session termination by sending a Diameter CCA message. + +If the UE is roaming, then steps 4a ~ 4c are executed instead of step 4: + +- 4a. If the H-PCRF receives the Diameter CCR message in step 2b, the H-PCRF acknowledges the session or subsession termination request by sending a Diameter CCA message to the V-PCRF. + - 4b. The V-PCRF identifies the related IP-CAN session and performs update as necessary. + - 4c. The V-PCRF acknowledges the session termination by sending a Diameter CCA message to the BBERF. +5. The BBERF sends a reply to the request to remove the gateway control session. The form of the reply depends upon the type of the IP-CAN. + +#### 4.4.4.2 PCRF-Initiated Gateway Control Session Termination + +This procedure applies for case 2a, as defined in clause 4.0, when the PCRF detects that there is no remaining IP-CAN session at the PCRF. + +![Sequence diagram illustrating PCRF-Initiated Gateway Control Session Termination. The diagram shows four lifelines: BBERF, PCEF, V-PCRF, and H-PCRF. The process starts with an external 'Remove Gxx Session Request' to the H-PCRF. The H-PCRF sends a 'Diameter RAR' (Step 2) to the BBERF. If the UE is roaming, the H-PCRF sends a 'Diameter RAR' (Step 2a) to the V-PCRF, which then sends a 'Diameter RAR' (Step 2b) to the BBERF. The BBERF sends a 'Diameter RAA' (Step 3) to the H-PCRF. If the UE is roaming, the BBERF sends a 'Diameter RAA' (Step 3a) to the V-PCRF, which then sends a 'Diameter RAA' (Step 3b) to the H-PCRF. Finally, the BBERF terminates the Gateway control session (Step 4).](4792a2ccd62226861fadc22117edb7b1_img.jpg) + +``` + +sequenceDiagram + participant BBERF + participant PCEF + participant V-PCRF + participant H-PCRF + + Note right of H-PCRF: 1. Remove Gxx Session Request + H-PCRF->>BBERF: 2. Diameter RAR + Note left of BBERF: Roaming case + H-PCRF->>V-PCRF: 2a. Diameter RAR + V-PCRF->>BBERF: 2b. Diameter RAR + BBERF->>H-PCRF: 3. Diameter RAA + Note left of BBERF: Roaming case + BBERF->>V-PCRF: 3a. Diameter RAA + V-PCRF->>H-PCRF: 3b. Diameter RAA + Note right of BBERF: 4. The BBERF terminates the Gateway control session based on the BBERF-initiated termination procedures. + +``` + +Sequence diagram illustrating PCRF-Initiated Gateway Control Session Termination. The diagram shows four lifelines: BBERF, PCEF, V-PCRF, and H-PCRF. The process starts with an external 'Remove Gxx Session Request' to the H-PCRF. The H-PCRF sends a 'Diameter RAR' (Step 2) to the BBERF. If the UE is roaming, the H-PCRF sends a 'Diameter RAR' (Step 2a) to the V-PCRF, which then sends a 'Diameter RAR' (Step 2b) to the BBERF. The BBERF sends a 'Diameter RAA' (Step 3) to the H-PCRF. If the UE is roaming, the BBERF sends a 'Diameter RAA' (Step 3a) to the V-PCRF, which then sends a 'Diameter RAA' (Step 3b) to the H-PCRF. Finally, the BBERF terminates the Gateway control session (Step 4). + +**Figure 4.4.4.2.1: PCRF-Initiated Gateway Control Session Termination** + +1. The H-PCRF is requested to terminate the gateway control session. +2. The H-PCRF sends a Diameter RAR message to the BBERF including a Session-Release-Cause AVP to indicate request for terminating the gateway control session. + +If the UE is roaming, then steps in 2a ~ 2b are executed instead of Step 2: + +2a. The H-PCRF sends a Diameter RAR message to the V-PCRF to indicate the termination of the S9 session including the Session-Release-Cause AVP. + +2b. The V-PCRF sends a Diameter RAR message to the BBERF based on the termination request received from the H-PCRF to indicate the gateway control session termination. + +3. The BBERF acknowledges the gateway control session termination request by sending a Diameter RAA message. + +If the UE is roaming, then steps 3a ~ 3b are executed instead of Step 3: + +3a. The BBERF acknowledges the gateway control session termination request by sending a Diameter RAA message to the V-PCRF. + +3b. The V-PCRF sends a Diameter RAA message to the H-PCRF and acknowledges the request for terminating the S9 session corresponding to the gateway control session. + +4. The BBERF follows the BBERF-initiated gateway control session termination procedures described in clause 4.4.4.1 to terminate the gateway control session. + +## 4.5 Multiple BBERF Signalling Flows + +### 4.5.1 Non-Roaming and Home Routed cases + +#### 4.5.1.1 New Gateway Control Session Establishment + +The following signalling flow describes an example of a new BBERF initiating a GW control session establishment associated with an existing IP-CAN session. + +![Sequence diagram showing Gateway Control Session Establishment during BBERF relocation. Lifelines: Source BBERF, Target BBERF, PCEF, V-PCRF, H-PCRF. The process involves a request from Source BBERF to Target BBERF, followed by Diameter CCR messages to H-PCRF and V-PCRF. The H-PCRF performs internal steps (store info, identify BBERF, PCC/QoS decision) and returns a Diameter CCA. The V-PCRF then performs its own steps (store info, identify home routed access) and returns a Diameter CCA to the Target BBERF. The Target BBERF then installs QoS rules and sends a response back to the Source BBERF. The diagram is divided into 'ROAMING CASE' sections for the V-PCRF interactions.](7a1dee155822446f7828dcb055c465c3_img.jpg) + +``` + +sequenceDiagram + participant Source BBERF + participant Target BBERF + participant PCEF + participant V-PCRF + participant H-PCRF + + Note left of Source BBERF: 1. Establish Gateway Control Session Request + Source BBERF->>Target BBERF: + Note right of Target BBERF: 2. Diameter CCR + Target BBERF->>H-PCRF: + Note right of H-PCRF: ROAMING CASE + Note right of V-PCRF: 2a. Diameter CCR + V-PCRF->>V-PCRF: 2b. Store Information and identify home routed access + Note right of V-PCRF: + V-PCRF->>H-PCRF: 2c. Diameter CCR + Note right of H-PCRF: + H-PCRF->>H-PCRF: 3. Store Information + H-PCRF->>H-PCRF: 4. Identify multiple BBERF(s) + H-PCRF->>H-PCRF: 5. PCC/QoS Rules decision based on BCM of GW control session + H-PCRF->>H-PCRF: 6. Store PCC/QoS Rules + Note right of H-PCRF: + H-PCRF->>Target BBERF: 7. Diameter CCA + Note right of H-PCRF: ROAMING CASE + H-PCRF->>V-PCRF: 7a. Diameter CCA + Note right of V-PCRF: + V-PCRF->>V-PCRF: 7b. Store PCC/QoS Rules. Policy decision + Note right of V-PCRF: + V-PCRF->>H-PCRF: 7c. Diameter CCR + H-PCRF-->>V-PCRF: 7d. Diameter CCA + Note right of V-PCRF: + V-PCRF->>Target BBERF: 7e. Diameter CCA + Note right of Target BBERF: + Target BBERF->>Target BBERF: 8. Install QoS Rules. Policy enforcement + Note right of Target BBERF: + Target BBERF->>Source BBERF: 9. Establish Gateway Control Session Response + +``` + +**Legend:** + → **Mandatory** + -.-> **Conditional** + +Sequence diagram showing Gateway Control Session Establishment during BBERF relocation. Lifelines: Source BBERF, Target BBERF, PCEF, V-PCRF, H-PCRF. The process involves a request from Source BBERF to Target BBERF, followed by Diameter CCR messages to H-PCRF and V-PCRF. The H-PCRF performs internal steps (store info, identify BBERF, PCC/QoS decision) and returns a Diameter CCA. The V-PCRF then performs its own steps (store info, identify home routed access) and returns a Diameter CCA to the Target BBERF. The Target BBERF then installs QoS rules and sends a response back to the Source BBERF. The diagram is divided into 'ROAMING CASE' sections for the V-PCRF interactions. + +Figure 4.5.1.1.1: Gateway Control Session Establishment during BBERF relocation + +1. The target BBERF receives a message or indication to establish a Gateway Control session + +2. The target BBERF initiates a Gateway Control session with the H-PCRF by sending a CCR using the CC-Request-Type AVP set to the value INITIAL\_REQUEST to the H-PCRF. The target BBERF provides information as detailed in clause 4a.5.1 of 3GPP TS 29.212 [9]. + +When the UE is roaming, the following steps are executed instead of step 2: + +- 2a. The target BBERF initiates a Gateway Control session with the V-PCRF by sending a CCR using the CC-Request-Type AVP set to the value INITIAL\_REQUEST to the V-PCRF. The target BBERF provides information as detailed in clause 4a.5.1 of 3GPP TS 29.212 [9]. +- 2b. The V-PCRF determines based on the UE identity information that the request is for a roaming user. The V-PCRF checks whether the V-PCRF is required to send the request to the H-PCRF based on the roaming agreements. +- 2c. For case 2a: + - The V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes in the CCR the information received in step 2a. The V-PCRF includes the BBERF identity by including the AN-GW-Address AVP at command level. + +For case 2b: + +- If the Session-Linking-Indicator AVP is not received, or it indicates SESSION\_LINKING\_IMMEDIATE, the V-PCRF sends the CCR command to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR command with allocated S9 subsession identifier assigned by the V-PCRF for this PDN connection within the Subsession-Id AVP, the Subsession-Operation AVP set to the value MODIFICATION, the BBERF identity within AN-GW-Address AVP. + - If the Session-Linking-Indicator AVP is received indicating that the session linking has to be deferred, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this Gateway Control Session within the Subsession-Id AVP, the Subsession-Operation AVP set to the value ESTABLISHMENT and the Session-Linking-Indicator AVP set to the value "SESSION\_LINKING\_DEFERRED". +3. The H-PCRF stores the information received in the Diameter CCR. + 4. If the Session-Linking-Indicator AVP was received indicating that the session linking has to be deferred, the linking between the Gateway Control Session and the Gx session shall be deferred. Otherwise, based on the information received the H-PCRF identifies multiple BBERF sessions for a particular IP-CAN session. + 5. The H-PCRF derives applicable PCC/QoS rules based on the BCM mode as defined in clause 4a.5.7 of 3GPP TS 29.212 [9]. + 6. The H-PCRF stores the selected QoS Rules and PCC Rules. For non-roaming users the H-PCRF selects the Bearer Control Mode that will apply during the Gateway Control session. + 7. The H-PCRF acknowledges the Gateway Control Session by sending a Diameter CCA. The H-PCRF includes the selected BCM if applicable, the QoS rules and event triggers. + +When the UE is roaming, the following steps are executed instead of step 7: + +- 7a. The H-PCRF acknowledges the Gateway Control Session by sending a Diameter CCA to the V-PCRF. The H-PCRF includes applicable QoS rules and also event triggers. The H-PCRF also includes the AN-GW-Address AVP if the QoS rules are applicable for a single BBERF. +- 7b. The V-PCRF enforces visited operator policies regarding QoS authorization requested by the H-PCRF as indicated by the roaming agreements. +- 7c. If the V-PCRF denies an authorization, it informs the H-PCRF and may provide the acceptable QoS Information for the service. +- 7d. The H-PCRF may provide new or modified QoS rules to the V-PCRF. + +- 7e. The V-PCRF acknowledges the Gateway Control Session and provisions, when applicable, the selected BCM, policy decisions and event triggers to the target BBERF. +8. The BBERF installs the received QoS Rules. +9. The target BBERF establishes an indication for a Gateway control session response. + +#### 4.5.1.2 PCEF IP-CAN session modification – Handover + +The following signalling flow describe the case when an indication of handover is received by the PCEF and the H-PCRF derives QoS rules based on the type of BBERF (primary/non-primary). + +![Sequence diagram for PCEF IP-CAN session modification – Handover involving Source BBERF, Target BBERF, PCEF, V-PCRF, and H-PCRF.](ca5566458a134032dd860e88fdaa0d2b_img.jpg) + +``` + +sequenceDiagram + participant S_BBERF as Source BBERF + participant T_BBERF as Target BBERF + participant PCEF + participant V_PCRF as V-PCRF + participant H_PCRF as H-PCRF + + Note over S_BBERF, PCEF: 1. Indication of handover + S_BBERF->>PCEF: + PCEF->>H_PCRF: 2. Diameter CCR + Note right of H_PCRF: 3. Store Information + Note right of H_PCRF: 4. Derive primary/non-primary BBERF(s) + Note right of H_PCRF: 5. PCC/QoS Rules decision based on BCM of GW control session + Note right of H_PCRF: 6. Store PCC/QoS Rules + H_PCRF->>PCEF: 7. Diameter CCA + H_PCRF->>T_BBERF: 8. Diameter RAR + + rect rgb(220, 255, 255) + Note left of V_PCRF: ROAMING CASE + H_PCRF-->>V_PCRF: 8a. Diameter RAR + Note over V_PCRF: 8b. Store PCC/QoS Rules. Policy decision + V_PCRF-->>H_PCRF: 8c. Diameter RAA + H_PCRF-->>V_PCRF: 8d. Diameter RAR + V_PCRF->>T_BBERF: 8e. Diameter RAR + end + + Note over T_BBERF: 9. Install QoS Rules. Policy enforcement + T_BBERF->>H_PCRF: 10. Diameter RAA + + rect rgb(220, 255, 255) + Note left of V_PCRF: ROAMING CASE + T_BBERF-->>V_PCRF: 10a. Diameter RAA + V_PCRF-->>H_PCRF: 10b. Diameter RAA + end + +``` + +**Legend:** +——> Mandatory +- - - -> Conditional + +Sequence diagram for PCEF IP-CAN session modification – Handover involving Source BBERF, Target BBERF, PCEF, V-PCRF, and H-PCRF. + +**Figure 4.5.1.2.1: PCEF IP-CAN session modification – Handover** + +1. The PCEF receives a message or indication that a handover occurred +2. The PCEF initiates an IP-CAN Session Modification procedure by sending a CCR using the CC-Request-Type AVP set to the value UPDATE\_REQUEST to the H-PCRF. The PCEF includes the AN\_GW\_CHANGE event trigger, and if applicable the IP-CAN\_CHANGE event trigger as well, to indicate that handover has occurred. + +3. The H-PCRF stores the information received in the Diameter CCR. +4. If there is a pending gateway control session to be linked to a Gx session, the H-PCRF shall perform the session linking according to clause 4a.5.6 of 3GPP TS 29.212 [9] for the non-roaming case. Based on the information received the H-PCRF reclassifies primary/non-primary BBERFs according to the procedures defined in clause 4a.5.7 of 3GPP TS 29.212 [9]. +5. The H-PCRF derives PCC rules for the PCEF, and QoS rules for the new reclassified primary BBERF, based on the BCM mode of the GW control session as defined in clause 4a.5.7 of 3GPP TS 29.212 [9]. +6. The H-PCRF stores the selected QoS Rules and PCC Rules. +7. The H-PCRF acknowledges the IP-CAN session modification request by sending a Diameter CCA to the PCEF. The H-PCRF includes updated PCC rules and event triggers (if applicable). +8. The H-PCRF initiates a Gateway Control and QoS Rules Provision procedure by sending a Diameter RAR. The H-PCRF includes the selected BCM if applicable, the QoS rules and event triggers. + +When the UE is roaming, the following steps are executed instead of step 8: + +- 8a. The H-PCRF initiates a Gateway Control and QoS Rules Provision procedure to the V-PCRF by sending a Diameter RAR to the V-PCRF. The H-PCRF sends applicable QoS rules based on the BBERF type (primary/non-primary) and BCM mode selected as defined in clause 4a.5.9 of 3GPP TS 29.212 [9]. The H-PCRF includes the AN-GW-Address AVP if the QoS rules are applicable only for a single BBERF. If the QoS rules are applicable for all BBERF sessions this AVP is omitted. + - 8b. The V-PCRF enforces visited operator policies regarding QoS authorization requested by the H-PCRF as indicated by the roaming agreements. + - 8c. If the V-PCRF denies an authorization, it informs the H-PCRF and may provide the acceptable QoS Information for the service by including in the RAA command the QoS-Rule-Report AVP to indicate the QoS Rules that were not accepted, the Rule-Failure-Code AVP set to UNSUCCESSFUL-QoS-VALIDATION, and the QoS-Information AVP. + - 8d. The H-PCRF may provide new or modified QoS rules to the V-PCRF. + - 8e. The V-PCRF initiates the Gateway Control Session and QoS rules provisions, when applicable, the selected BCM, policy decisions and event triggers to the target BBERF. +9. The BBERF installs the received QoS Rules. + 10. The target BBERF acknowledges the RAR command by sending a Diameter RAA command to the PCRF. + +When the UE is roaming, the following steps are executed instead of step 10: + +- 10a. The BBERF acknowledges the Gateway Control and QoS Rules Provision request by sending a Diameter RAA to the V-PCRF. +- 10b. The V-PCRF acknowledges the Gateway Control and QoS Rules Provision request by sending a Diameter RAA to the H-PCRF. + +#### 4.5.1.3 PCEF IP-CAN session modification – S2c-based IP flow mobility + +The following signalling flow describes an example of S2c-based IP flow mobility. In this case, the H-PCRF receives an IP flow mobility event by the PCEF and derives QoS rules based on the IP flow mobility routing rules. + +![Sequence diagram for PCEF IP-CAN session modification – S2c-based IP flow mobility. Lifelines: BBERF #1, BBERF #2, PCEF, V-PCRF, H-PCRF. The diagram shows a non-roaming case (steps 1-8) and a roaming case (steps 7a-7e). A legend indicates solid arrows are mandatory and dashed arrows are conditional.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +``` + +sequenceDiagram + participant BBERF1 as BBERF #1 + participant BBERF2 as BBERF #2 + participant PCEF + participant V-PCRF + participant H-PCRF + + Note left of BBERF1: 1. Indication of IP flow mobility + PCEF->>H-PCRF: 2. Diameter CCR + H-PCRF->>H-PCRF: 3. Store Information + H-PCRF->>H-PCRF: 4. PCC/QoS Rules decision based on BCM of GW control session and received IP flow mobility routing rules + H-PCRF->>H-PCRF: 5. Store PCC/QoS Rules + H-PCRF->>PCEF: 6. Diameter CCA + H-PCRF->>V-PCRF: 7. Diameter RAR + Note right of V-PCRF: ROAMING CASE + alt Roaming Case: 7a. Diameter RAR (H-PCRF to V-PCRF), 7b. Store PCC/QoS Rules. Policy decision (V-PCRF internal), 7c. Diameter RAA (V-PCRF to H-PCRF), 7d. Diameter RAR (H-PCRF to V-PCRF), 7e. Diameter RAR (V-PCRF to BBERF #2) + Note left of BBERF1: 8. Perform Step 9-10b: as specified in Figure 4.5.1.2.1: PCEF-initiated IP-CAN session modification – Handover. + +``` + +**Legend:** + +- **Mandatory** +- **Conditional** + +Sequence diagram for PCEF IP-CAN session modification – S2c-based IP flow mobility. Lifelines: BBERF #1, BBERF #2, PCEF, V-PCRF, H-PCRF. The diagram shows a non-roaming case (steps 1-8) and a roaming case (steps 7a-7e). A legend indicates solid arrows are mandatory and dashed arrows are conditional. + +**Figure 4.5.1.3.1: PCEF IP-CAN session modification – S2c-based IP flow mobility** + +1. The PCEF receives a message or indication that an IP flow mobility event occurred +2. The PCEF initiates an IP-CAN Session Modification procedure by sending a CCR using the CC-Request-Type AVP set to the value UPDATE\_REQUEST to the H-PCRF. The PCEF includes the ROUTING\_RULE\_CHANGE event trigger to indicate that a change in the IP flow mobility routing rules has occurred. The PCEF includes in the CCR the Routing-Rule-Install and/or Routing-Rule-Removal AVPs. +3. The H-PCRF stores the information received in the Diameter CCR. +4. The H-PCRF derives PCC rules for the PCEF, and QoS rules for the BBERF(s), based on the BCM mode of the GW control session and the IP flow mobility routing rules as defined in clause 4a.5.7 of 3GPP TS 29.212 [9] +5. The H-PCRF stores the selected PCC/QoS Rules. +6. The H-PCRF acknowledges the IP-CAN session modification request by sending a Diameter CCA to the PCEF. The H-PCRF includes updated PCC rules and event triggers (if applicable). +7. The H-PCRF initiates a Gateway Control and QoS Rules Provision procedure by sending a Diameter RAR. The H-PCRF includes the QoS rules and event triggers. + +When the UE is roaming, the following steps are executed instead of step 7: + +- 7a. The H-PCRF initiates a Gateway Control and QoS Rules Provision procedure to the V-PCRF by sending a Diameter RAR to the V-PCRF. The H-PCRF sends applicable QoS rules based on BCM mode selected as defined in clause 4a.5.9 of 3GPP TS 29.212 [9]. The H-PCRF includes the AN-GW-Address AVP identifying the BBERF involved in the exchange of the IP flows described by the received IP flow mobility routing rules + +- 7b. The V-PCRF enforces visited operator policies regarding QoS authorization requested by the H-PCRF as indicated by the roaming agreements. +- 7c. If the V-PCRF denies an authorization, it informs the H-PCRF and may provide the acceptable QoS Information for the service by including in the RAA command the QoS-Rule-Report AVP to indicate the QoS Rules that were not accepted, the Rule-Failure-Code AVP set to UNSUCCESSFUL-QoS-VALIDATION, and the QoS-Information AVP. +- 7d. The H-PCRF may provide new or modified QoS rules to the V-PCRF. +- 7e. The V-PCRF initiates the Gateway Control Session and QoS rules provisions, when applicable, policy decisions and event triggers to BBERF. +- 8 Step 9 through step 10b: as specified in Figure 4.5.1.2.1: PCEF-initiated IP-CAN session modification- Handover are executed, as needed. If the IP flows were moved from one access to another (e.g. 3GPP to WLAN, or vice versa), the PCRF may also initiate a RAR command towards BBERF#1 to modify or release the related resources associated with the flows that were moved to BBERF#2. + +#### 4.5.1.4 Gateway Control Session Establishment and PCEF IP-CAN session modification – S2c-based IP flow mobility + +The following signalling flow describes an example of S2c-based IP flow mobility. In this case, the H-PCRF receives a Gateway Control session establishment by a BBERF and an IP flow mobility event by the PCEF. H-PCRF associates the IP-CAN session to multiple Gateway Control Sessions and derives QoS rules based on the IP flow mobility routing rules. + +![Sequence diagram for Gateway Control Session Establishment and PCEF IP-CAN session modification – S2c-based IP flow mobility. The diagram shows interactions between BBERF #1, BBERF #2, PCEF, V-PCRF, and H-PCRF. Step 1: Gateway Control Session Establishment for BBERF #2. Step 2: Indication of IP flow mobility from PCEF to H-PCRF. Step 3: Diameter CCR from H-PCRF to V-PCRF. Step 4: Store Information at V-PCRF. Step 5: PCC/QoS Rules decision at V-PCRF. Step 6: PCEF-initiated IP-CAN session modification.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +``` + +sequenceDiagram + participant BBERF1 as BBERF #1 + participant BBERF2 as BBERF #2 + participant PCEF + participant V-PCRF + participant H-PCRF + + Note over BBERF1, BBERF2: 1. Perform Step 1-10: as specified in Figure 4.4.1.1: Gateway Control Session Establishment. + Note over PCEF: 2. Indication of IP flow mobility + PCEF->>H-PCRF: 3. Diameter CCR + Note over H-PCRF: 4. Store Information. + Note over H-PCRF: 5. PCC/QoS Rules decision based on BCM of GW control session and received IP flow mobility routing rules + Note over PCEF: 6. Perform Step 5-8: as specified in Figure 4.5.1.x.1: PCEF-initiated IP-CAN session modification – IP Flow mobility. + +``` + +**Legend:** + + *Mandatory* + +Sequence diagram for Gateway Control Session Establishment and PCEF IP-CAN session modification – S2c-based IP flow mobility. The diagram shows interactions between BBERF #1, BBERF #2, PCEF, V-PCRF, and H-PCRF. Step 1: Gateway Control Session Establishment for BBERF #2. Step 2: Indication of IP flow mobility from PCEF to H-PCRF. Step 3: Diameter CCR from H-PCRF to V-PCRF. Step 4: Store Information at V-PCRF. Step 5: PCC/QoS Rules decision at V-PCRF. Step 6: PCEF-initiated IP-CAN session modification. + +**Figure 4.5.1.4.1: Gateway Control Session Establishment and PCEF IP-CAN session modification – S2c-based IP flow mobility** + +1. Step 1 through step 10: as specified in Figure 4.4.1.1: Gateway Control Session Establishment are executed, as needed. The Gateway Control Session is established for BBERF #2. The Gateway Control Session for BBERF #1 was previously established. + +NOTE: If the Gateway Control Session is established for WLAN access, only case 2a is possible. + +2. The PCEF receives a message or indication that an IP flow mobility event occurred. +3. The PCEF initiates an IP-CAN Session Modification procedure by sending a CCR using the CC-Request-Type AVP set to the value UPDATE\_REQUEST to the H-PCRF. The PCEF includes the ROUTING\_RULE\_CHANGE event trigger to indicate that a change in the IP flow mobility routing rules has occurred. The PCEF includes in the CCR the Routing-Rule-Install and/or Routing-Rule-Removal AVPs. +4. The H-PCRF stores the information received in the Diameter CCR. +5. The H-PCRF does not differentiate between primary and non-primary BBFs. H-PCRF derives PCC rules for the PCEF, and QoS rules for the BBERF(s), based on the BCM mode of the GW control session and the IP flow mobility routing rules as defined in clause 4a.5.7 of 3GPP TS 29.212 [9] +6. Step 5 through step 8: as specified in Figure 4.5.1.3.1: PCEF-initiated IP-CAN session modification- IP Flow mobility are executed, as needed. + +### 4.5.2 Visited access case + +#### 4.5.2.1 New Gateway Control Session Establishment + +The following signalling flow describes an example of a new BBERF initiating a GW control session establishment associated with an existing IP-CAN session. + +![Sequence diagram illustrating Gateway Control Session Establishment during BBERF relocation. The diagram shows interactions between Source BBERF, Target BBERF, PCEF, V-PCRF, and H-PCRF. The process starts with the Source BBERF sending an 'Establish Gateway Control Session Request' to the Target BBERF. The Target BBERF then sends a 'Diameter CCR' to the V-PCRF. The V-PCRF performs internal steps: 'Store Information and identify visited access' and 'Identify multiple BBERF(s). Derive and Store QoS Rules. Policy decision'. It then sends a 'Diameter CCR' to the H-PCRF. The H-PCRF performs 'Store Information, PCC Rules decision and store'. The V-PCRF then sends 'Diameter CCA' (step 7) and 'Diameter CCA' (step 8b) to the Target BBERF. The Target BBERF performs 'Install QoS Rules. Policy enforcement' and finally sends an 'Establish Gateway Control Session Response' back to the Source BBERF. A vertical label 'ROAMING CASE (Visited access)' is present on the left side of the diagram.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +sequenceDiagram + participant Source BBERF + participant Target BBERF + participant PCEF + participant V-PCRF + participant H-PCRF + + Note left of Source BBERF: ROAMING CASE (Visited access) + + Source BBERF->>Target BBERF: 1. Establish Gateway Control Session Request + Target BBERF->>V-PCRF: 2. Diameter CCR + Note right of V-PCRF: 3. Store Information and identify visited access + Note right of V-PCRF: 4. Identify multiple BBERF(s). Derive and Store QoS Rules. Policy decision + V-PCRF->>H-PCRF: 5. Diameter CCR + Note right of H-PCRF: 6. Store Information, PCC Rules decision and store + H-PCRF-->>V-PCRF: 7. Diameter CCA + Note right of V-PCRF: 8. Store PCC/QoS Rules. Policy decision + V-PCRF->>H-PCRF: 8a. Diameter CCR + H-PCRF-->>V-PCRF: 8b. Diameter CCA + V-PCRF->>Target BBERF: 9. Diameter CCA + Note right of Target BBERF: 10. Install QoS Rules. Policy enforcement + Target BBERF->>Source BBERF: 11. Establish Gateway Control Session Response + +``` + +Sequence diagram illustrating Gateway Control Session Establishment during BBERF relocation. The diagram shows interactions between Source BBERF, Target BBERF, PCEF, V-PCRF, and H-PCRF. The process starts with the Source BBERF sending an 'Establish Gateway Control Session Request' to the Target BBERF. The Target BBERF then sends a 'Diameter CCR' to the V-PCRF. The V-PCRF performs internal steps: 'Store Information and identify visited access' and 'Identify multiple BBERF(s). Derive and Store QoS Rules. Policy decision'. It then sends a 'Diameter CCR' to the H-PCRF. The H-PCRF performs 'Store Information, PCC Rules decision and store'. The V-PCRF then sends 'Diameter CCA' (step 7) and 'Diameter CCA' (step 8b) to the Target BBERF. The Target BBERF performs 'Install QoS Rules. Policy enforcement' and finally sends an 'Establish Gateway Control Session Response' back to the Source BBERF. A vertical label 'ROAMING CASE (Visited access)' is present on the left side of the diagram. + +**Figure 4.5.2.1.1: Gateway Control Session Establishment during BBERF relocation** + +1. The target BBERF receives a message or indication to establish a Gateway Control Session. +2. The target BBERF initiates a Gateway Control Session with the V-PCRF by sending a CCR using the CC-Request-Type AVP set to the value INITIAL\_REQUEST to the V-PCRF. The target BBERF provides information as detailed in clause 4a.5.1 of 3GPP TS 29.212 [9]. +3. The V-PCRF stores the information received in the Diameter CCR and determines based on the UE identity information that the request is for a roaming user. The V-PCRF checks whether the V-PCRF is required to send the request to the H-PCRF based on the roaming agreements. The V-PCRF does not send the CCR to the H-PCRF to update the S9 session immediately if the Session-Linking-Indicator AVP was received indicating that the session linking has to be deferred. +4. If the Session-Linking-Indicator AVP was received indicating that the session linking has to be deferred, the linking between the Gateway Control Session and the Gx session shall be deferred. Otherwise, based on the information received the V-PCRF identifies multiple BBERF sessions for a particular IP-CAN session. The V-PCRF derives applicable QoS rules according to local policies and stores them. + +For case 2a or if either the AN\_GW\_CHANGE or the IP-CAN\_CHANGE event is subscribed by H-PCRF and this event trigger is received steps 5~8 are executed. Otherwise steps 5~8 are skipped. + +5. The V-PCRF initiates an IP-CAN Session Modification procedure by sending a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes in the CCR the information received in step 2. +6. The H-PCRF stores the information received in the Diameter CCR. And the H-PCRF decides PCC rules for the BBERF and stores PCC rules. +7. The H-PCRF sends a Diameter CCA to the V-PCRF to provide the PCC rules. The H-PCRF sends applicable PCC rules. The H-PCRF includes the AN-GW-Address AVP if the PCC rules are applicable only for a single BBERF. If the PCC rules are applicable for all BBERF sessions this AVP is omitted. +8. If the steps 5~7 are executed, the V-PCRF enforces visited operator policies regarding QoS authorization requested by the H-PCRF as indicated by the roaming agreements. + +Steps 8a and 8b are executed if the V-PCRF denies authorisation for one or more PCC rules. + +- 8a. If V-PCRF denies authorization, it informs the H-PCRF by sending a CCR command including the Charging-Rule-Report AVP to indicate the PCC Rules that were not accepted, the Rule-Failure-Code AVP set to UNSUCCESSFUL-QoS-VALIDATION, and the acceptable QoS Information for the service. +- 8b. The H-PCRF may provide new modified PCC rules to the V-PCRF. +9. The V-PCRF acknowledges the Gateway Control Session and provisions policy decisions and event triggers to the target BBERF. +10. The BBERF installs the received QoS rules. +11. The target BBERF responds to the Gateway control session establishment request in step 1. + +#### 4.5.2.2 PCEF-Initiated IP-CAN session modification-Handover + +The following signalling flow describe the case when an indication of handover is received by the PCEF and the H-PCRF derives QoS rules based on the type of BBERF (primary/non-primary) + +![Sequence diagram for PCEF-initiated IP-CAN session modification – Handover. The diagram shows interactions between Source BBERF, Target BBERF, PCEF, V-PCRF, and H-PCRF. The process starts with an indication of handover from Source BBERF to PCEF. PCEF sends a Diameter CCR to V-PCRF. V-PCRF stores information, identifies multiple BBERF(s), and derives primary/non-primary BBERF(s). V-PCRF sends a Diameter CCR to H-PCRF. H-PCRF stores information, makes a PCC Rules decision, and stores it. H-PCRF sends a Diameter CCA to V-PCRF. V-PCRF stores PCC/QoS Rules and makes a policy decision. V-PCRF sends a Diameter CCR to H-PCRF. H-PCRF sends a Diameter CCA to V-PCRF. V-PCRF sends a Diameter CCA to PCEF. PCEF sends a Diameter RAR to Target BBERF. Target BBERF installs QoS Rules and policy enforcement. Target BBERF sends a Diameter RAA to V-PCRF. A legend indicates that solid arrows are Mandatory and dashed arrows are Conditional. A vertical label on the left indicates 'ROAMING CASE (Visited access)'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +sequenceDiagram + participant Source BBERF + participant Target BBERF + participant PCEF + participant V-PCRF + participant H-PCRF + + Note left of Source BBERF: ROAMING CASE (Visited access) + + Source BBERF->>PCEF: 1. Indication of handover + PCEF->>V-PCRF: 2. Diameter CCR + Note right of V-PCRF: 3. Store Information + Note right of V-PCRF: 4. Identify multiple BBERF(s) + Note right of V-PCRF: 5. Derive primary/non-primary BBERF(s) + V-PCRF-->>H-PCRF: 6. Diameter CCR + Note right of H-PCRF: 7. Store Information + Note right of H-PCRF: 8. PCC Rules decision and store + H-PCRF-->>V-PCRF: 9. Diameter CCA + Note right of V-PCRF: 10. Store PCC/QoS Rules. Policy decision + V-PCRF-->>H-PCRF: 10a. Diameter CCR + H-PCRF-->>V-PCRF: 10b. Diameter CCA + V-PCRF->>PCEF: 11. Diameter CCA + PCEF->>Target BBERF: 12. Diameter RAR + Note right of Target BBERF: 13. Install QoS Rules Policy enforcement + Target BBERF->>V-PCRF: 14. Diameter RAA + + Note right of H-PCRF: Legend: + Note right of H-PCRF: Mandatory (solid arrow) + Note right of H-PCRF: Conditional (dashed arrow) + +``` + +Sequence diagram for PCEF-initiated IP-CAN session modification – Handover. The diagram shows interactions between Source BBERF, Target BBERF, PCEF, V-PCRF, and H-PCRF. The process starts with an indication of handover from Source BBERF to PCEF. PCEF sends a Diameter CCR to V-PCRF. V-PCRF stores information, identifies multiple BBERF(s), and derives primary/non-primary BBERF(s). V-PCRF sends a Diameter CCR to H-PCRF. H-PCRF stores information, makes a PCC Rules decision, and stores it. H-PCRF sends a Diameter CCA to V-PCRF. V-PCRF stores PCC/QoS Rules and makes a policy decision. V-PCRF sends a Diameter CCR to H-PCRF. H-PCRF sends a Diameter CCA to V-PCRF. V-PCRF sends a Diameter CCA to PCEF. PCEF sends a Diameter RAR to Target BBERF. Target BBERF installs QoS Rules and policy enforcement. Target BBERF sends a Diameter RAA to V-PCRF. A legend indicates that solid arrows are Mandatory and dashed arrows are Conditional. A vertical label on the left indicates 'ROAMING CASE (Visited access)'. + +**Figure 4.5.2.2.1: PCEF-initiated IP-CAN session modification – Handover** + +1. The PCEF receives a message or indication that a handover occurred. +2. The PCEF initiates an IP-CAN Session Modification procedure by sending a CCR using the CC-Request-Type AVP set to the value UPDATE\_REQUEST to the V-PCRF. The PCEF includes the AN\_GW\_CHANGE event trigger, and if applicable the IP-CAN\_CHANGE event trigger as well, to indicate that handover has occurred. +3. The V-PCRF stores the information received in the Diameter CCR. +4. If there is a pending Gateway Control Session to be linked to a Gx session, the V-PCRF links Gateway Control Session with the Gx session according to clause 4a.5.6 of 3GPP TS 29.212 [9]. Otherwise based on the information received the V-PCRF identifies multiple BBERF sessions for a particular IP-CAN session. +5. Based on the information received the V-PCRF reclassifies primary/non-primary BBERFs according to the procedures defined in clause 4a.5.7 of 3GPP TS 29.212 [9]. + +If either the AN\_GW\_CHANGE or the IP-CAN\_CHANGE event is subscribed by H-PCRF and this event trigger is received steps 6~9 are executed. Otherwise steps 6~9 are skipped. + +6. The V-PCRF initiates an IP-CAN Session Modification procedure by sending a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes in the CCR the information received in step 2. +7. The H-PCRF stores the information received in the Diameter CCR. +8. The H-PCRF decides PCC rules for the PCEF and stores PCC rules. +9. The H-PCRF sends a Diameter CCA to the V-PCRF to provide the PCC Rules. The H-PCRF sends applicable PCC rules. The H-PCRF includes the AN-GW-Address AVP if the PCC rules are applicable only for a single BBERF. If the PCC rules are applicable for all BBERF sessions this AVP is omitted. +10. If the steps 6~9 are executed, the V-PCRF enforces visited operator policies regarding QoS authorization requested by the H-PCRF as indicated by the roaming agreements. + +Steps 10a and 10b are executed if the V-PCRF denies authorisation for one or more PCC rules. + +- 10a. If V-PCRF denies authorization, it informs the H-PCRF by sending a CCR command including the Charging-Rule-Report AVP to indicate the PCC Rules that were not accepted, the Rule-Failure-Code AVP set to UNSUCCESSFUL-QoS-VALIDATION, and the acceptable QoS Information for the service. +- 10b. The H-PCRF may provide new modified PCC rules to the V-PCRF. +11. The V-PCRF acknowledges the IP-CAN session modification request by sending a Diameter CCA to the PCEF. The V-PCRF includes updated PCC rules and event triggers (if applicable) +12. The V-PCRF initiates the Gateway Control Session and QoS rules provisions by sending a Diameter RAR to the BBERF policy decisions and event triggers to the target BBERF. +13. The BBERF installs the received QoS Rules. +14. The BBERF acknowledges the Gateway Control and QoS Rules Provision request by sending a Diameter RAA to the V-PCRF. + +#### 4.5.2.3 PCEF-Initiated IP-CAN session modification - S2c-based IP flow mobility + +The following signalling flow describes an example of S2c-based IP flow mobility. In this case, the H-PCRF receives an IP flow mobility event by the PCEF and derives QoS rules based on the IP flow mobility routing rules. + +![Sequence diagram for PCEF-initiated IP-CAN session modification – S2c-based IP flow mobility. The diagram shows interactions between BBERF #1, BBERF #2, PCEF, V-PCRF, and H-PCRF. The process starts with an indication of IP flow mobility from BBERFs to PCEF. PCEF sends a Diameter CCR to V-PCRF. V-PCRF stores information and changes IP flow mobility routing rules. V-PCRF then sends a Diameter CCR to H-PCRF. H-PCRF stores information, makes a PCC rules decision, and stores it. H-PCRF sends a Diameter CCA back to V-PCRF. V-PCRF extracts QoS rules based on PCC rules and IP flow mobility rules. V-PCRF sends Diameter CCR and CCA messages to H-PCRF. Finally, PCEF performs steps 11-14 as specified in Figure 4.5.2.2.1: PCEF-initiated IP-CAN session modification – Handover. A legend indicates that solid arrows are Mandatory and dashed arrows are Conditional. A light blue shaded area on the left is labeled 'ROAMING CASE (Visited access)'.](54a53f959bb7758332532c1cd5f0ad75_img.jpg) + +Sequence diagram for PCEF-initiated IP-CAN session modification – S2c-based IP flow mobility. The diagram shows interactions between BBERF #1, BBERF #2, PCEF, V-PCRF, and H-PCRF. The process starts with an indication of IP flow mobility from BBERFs to PCEF. PCEF sends a Diameter CCR to V-PCRF. V-PCRF stores information and changes IP flow mobility routing rules. V-PCRF then sends a Diameter CCR to H-PCRF. H-PCRF stores information, makes a PCC rules decision, and stores it. H-PCRF sends a Diameter CCA back to V-PCRF. V-PCRF extracts QoS rules based on PCC rules and IP flow mobility rules. V-PCRF sends Diameter CCR and CCA messages to H-PCRF. Finally, PCEF performs steps 11-14 as specified in Figure 4.5.2.2.1: PCEF-initiated IP-CAN session modification – Handover. A legend indicates that solid arrows are Mandatory and dashed arrows are Conditional. A light blue shaded area on the left is labeled 'ROAMING CASE (Visited access)'. + +**Figure 4.5.2.3.1: PCEF-initiated IP-CAN session modification – S2c-based IP flow mobility** + +1. The PCEF receives a message or indication that a handover occurred. +2. The PCEF initiates an IP-CAN Session Modification procedure by sending a CCR using the CC-Request-Type AVP set to the value UPDATE\_REQUEST to the V-PCRF. The PCEF includes the ROUTING\_RULE\_CHANGE event trigger to indicate that a change in the IP flow mobility routing rules has occurred. The PCEF includes in the CCR Routing-Rule-Install and/or Routing-Rule-Removal AVPs. +3. The V-PCRF stores the information received in the Diameter CCR. +4. Based on the information received the V-PCRF determines that there is a change in the IP flow routing in the multiple BBERF(s) as described in clause 4a.5.7 of 3GPP TS 29.212 [9]. + +If either the AN\_GW\_CHANGE or the IP-CAN\_CHANGE event is subscribed by H-PCRF and this event trigger is received steps 5~8 are executed. Otherwise steps 5~8 are skipped. + +5. The V-PCRF initiates an IP-CAN Session Modification procedure by sending a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes in the CCR the information received in step 2. +6. The H-PCRF stores the information received in the Diameter CCR. +7. The H-PCRF decides PCC rules for the PCEF and stores PCC rules. Based on the IP flow mobility routing rule as defined in clause 4a.5.7 of 3GPP TS 29.212 [9] +8. The H-PCRF sends a Diameter CCA to the V-PCRF to provide the PCC Rules. The H-PCRF sends applicable PCC rules. +9. If the steps 5~8 are executed, the V-PCRF establishes QoS Rules based on received IP flow mobility routing rules and enforces visited operator policies regarding QoS authorization requested by the H-PCRF as indicated by the roaming agreements. + +Steps 9a and 9b are executed if the V-PCRF denies authorisation for one or more PCC rules. + +- 9a. If V-PCRF denies authorization, it informs the H-PCRF by sending a CCR command including the Charging-Rule-Report AVP to indicate the PCC Rules that were not accepted, the Rule-Failure-Code AVP set to UNSUCCESSFUL-QoS-VALIDATION, and the acceptable QoS Information for the service. + - 9b. The H-PCRF may provide new modified PCC rules to the V-PCRF. +10. Step 11 through step 14: as specified in Figure 4.5.2.2.1: PCEF-initiated IP-CAN session modification- Handover are executed, as needed. If the IP flows were moved from one access to another (e.g. 3GPP to WLAN, or vice versa), the PCRF may also initiate a RAR command towards BBERF#1 to modify or release the related resources associated with the flows that were moved to BBERF#2. + +#### 4.5.2.4 Gateway Control Session Establishment and PCEF IP-CAN session modification – S2c-based IP flow mobility + +The following signalling flow describes an example of IP flow mobility. In this case, the V-PCRF receives a Gateway Control session establishment by a BBERF and an IP flow mobility event by the PCEF. V-PCRF associates the IP-CAN session to multiple Gateway Control Sessions and derives QoS rules based on the IP flow mobility routing rules. + +![Sequence diagram for Gateway Control Session Establishment and PCEF IP-CAN session modification – S2c-based IP flow mobility. Lifelines: BBERF #1, BBERF #2, PCEF, V-PCRF, H-PCRF. The diagram shows a 'ROAMING CASE (Visited access)'. Step 1: Gateway Control Session Establishment. Step 2: Indication of IP flow mobility from BBERF #2 to PCEF. Step 3: Diameter CCR from PCEF to V-PCRF. Step 4: Store Information in V-PCRF. Step 5: Evaluate IP flow mobility routing rules in V-PCRF. Step 6: Diameter CCR from V-PCRF to H-PCRF (conditional). Step 7: Store Information in H-PCRF (conditional). Step 8: PCC Rules decision and store in H-PCRF (conditional). Step 9: Diameter CCA from H-PCRF to V-PCRF (conditional). Step 10: PCEF-initiated IP-CAN session modification.](69edc2887e907309499ac95b47ab6905_img.jpg) + +The diagram illustrates the interaction between network elements for S2c-based IP flow mobility. It begins with a common step (1) for Gateway Control Session Establishment. The main sequence starts with an indication of IP flow mobility (2) from BBERF #2 to PCEF. The PCEF then sends a Diameter CCR (3) to the V-PCRF, which stores the information (4) and evaluates routing rules (5). Depending on whether the H-PCRF is subscribed to the event, a conditional sequence of Diameter CCR (6), Store Information (7), PCC Rules decision and store (8), and Diameter CCA (9) occurs between the V-PCRF and H-PCRF. Finally, the PCEF initiates an IP-CAN session modification (10). + +**Legend:** + +- Mandatory**: Solid line with arrow +- Conditional**: Dashed line with arrow + +Sequence diagram for Gateway Control Session Establishment and PCEF IP-CAN session modification – S2c-based IP flow mobility. Lifelines: BBERF #1, BBERF #2, PCEF, V-PCRF, H-PCRF. The diagram shows a 'ROAMING CASE (Visited access)'. Step 1: Gateway Control Session Establishment. Step 2: Indication of IP flow mobility from BBERF #2 to PCEF. Step 3: Diameter CCR from PCEF to V-PCRF. Step 4: Store Information in V-PCRF. Step 5: Evaluate IP flow mobility routing rules in V-PCRF. Step 6: Diameter CCR from V-PCRF to H-PCRF (conditional). Step 7: Store Information in H-PCRF (conditional). Step 8: PCC Rules decision and store in H-PCRF (conditional). Step 9: Diameter CCA from H-PCRF to V-PCRF (conditional). Step 10: PCEF-initiated IP-CAN session modification. + +**Figure 4.5.2.4.1: Gateway Control Session Establishment and PCEF IP-CAN session modification – S2c-based IP flow mobility** + +1. Step 1 through step 10: as specified in Figure 4.4.1.1: Gateway Control Session Establishment are executed, as needed. The Gateway Control Session is established for BBERF #2. The Gateway Control Session for BBERF #1 was previously established. + +NOTE: If the Gateway Control Session is established for WLAN access, only case 2a is possible. + +2. The PCEF receives a message or indication that an IP flow mobility event occurred. +3. The PCEF initiates an IP-CAN Session Modification procedure by sending a CCR using the CC-Request-Type AVP set to the value UPDATE\_REQUEST to the V-PCRF. The PCEF includes the ROUTING\_RULE\_CHANGE event trigger to indicate that a change in the IP flow mobility routing rules has occurred. The PCEF includes in the CCR Routing-Rule-Install and/or Routing-Rule-Removal AVPs. +4. The V-PCRF stores the information received in the Diameter CCR. +5. Based on the received information, the V-PCRF does not differentiate between primary and non-primary BBFs and determines that there are IP flows routed through multiple BBERF(s) as described in clause 4a.5.7 of 3GPP TS 29.212 [9]. + +If either the AN\_GW\_CHANGE or the IP-CAN\_CHANGE event is subscribed by H-PCRF and this event trigger is received steps 6~9 are executed. Otherwise steps 6~9 are skipped. + +6. The V-PCRF initiates an IP-CAN Session Modification procedure by sending a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes in the CCR the information received in step 2. +7. The H-PCRF stores the information received in the Diameter CCR. +8. The H-PCRF decides PCC rules for the PCEF and stores PCC rules. Based on the IP flow mobility routing rule as defined in clause 4a.5.7 of 3GPP TS 29.212 [9]. +9. The H-PCRF sends a Diameter CCA to the V-PCRF to provide the PCC Rules. The H-PCRF sends applicable PCC rules. +10. Step 9 through step 10: as specified in Figure 4.5.2.3.1: PCEF-initiated IP-CAN session modification- IPFlow mobility are executed, as needed. + +## 4.6 Application Detection and Enforcement Procedures + +### 4.6.1 TDF Session Establishment in case of solicited reporting + +In the following procedure, the PCRF is the H-PCRF for the roaming UE with home routed access and the V-PCRF for the roaming UE with visited access. + +As part of the IP-CAN Session Establishment or Modification procedure, in case of solicited application reporting with a TDF, the PCRF initiates a TDF Session Establishment with the selected TDF. The TDF is selected based on data received from the PCEF or a local configuration at the PCRF. + +![Sequence diagram showing TDF Session Establishment in case of solicited reporting. The diagram involves two main entities: TDF and PCRF. The sequence of messages is: 1. PCRF sends a Diameter TSR to TDF. 2. TDF performs '1a. Credit session establishment with the OCS.' 3. TDF sends a Diameter TSA to PCRF.](6324b252294c0f5d4e34dad4a1202075_img.jpg) + +``` +sequenceDiagram + participant PCRF + participant TDF + Note left of TDF: 1a. Credit session establishment with the OCS. + PCRF->>TDF: 1. Diameter TSR + TDF->>PCRF: 2. Diameter TSA +``` + +Sequence diagram showing TDF Session Establishment in case of solicited reporting. The diagram involves two main entities: TDF and PCRF. The sequence of messages is: 1. PCRF sends a Diameter TSR to TDF. 2. TDF performs '1a. Credit session establishment with the OCS.' 3. TDF sends a Diameter TSA to PCRF. + +**Figure 4.6.1.1: TDF Session Establishment in case of solicited reporting** + +1. PCRF initiates a session towards the TDF. The PCRF provisions the applicable ADC Rules for the corresponding TDF session by sending a Diameter TS-Request to the TDF, including user identity information, the UE Ipv4 address and/or UE Ipv6 prefix and, if available, PDN identifier, IP-CAN type, RAT type and additional parameters as defined in clause 4b.5.1.1 of 3GPP TS 29.212 [9]. PCRF may also subscribe to the Event Triggers (e.g. APPLICATION\_START and APPLICATION\_STOP). + +**NOTE:** For PDN type Ipv4v6, in case the UE Ipv4 address is not available in the PCRF, the PCRF initiates the TDF session establishment providing the UE Ipv6 prefix, and will subsequently provide UE Ipv4 address to the TDF using Event-Report-Indication AVP to the TDF. + +- 1a. This step applies to the IP-CAN Session Establishment procedure. If online charging is applicable for the TDF, and at least one ADC rule with charging parameters was activated, then the TDF requests credit information from the OCS over the Gyn interface. If the TDF receives credit re-authorisation triggers from + +the OCS then it requests the PCRF via a TSA message to provision the triggers at the PCEF and/or BBERF. The triggers to be provisioned are specified in the Event-Report-Indication AVP in the TSA message. + +2. The TDF acknowledges the session establishment by sending a Diameter TS-Answer. The TDF may include Event-Report-Indication in the response. + +### 4.6.1A TDF Session Establishment in case of unsolicited reporting + +In the following procedure, the PCRF is the H-PCRF for the roaming UE with home routed access and the V-PCRF for the roaming UE with visited access. + +When the TDF detects for an Ipv4 address or Ipv6 address the first application start, the TDF shall initiate the TDF Session Establishment procedure with the PCRF. + +![Sequence diagram showing TDF Session Establishment in case of unsolicited reporting. The diagram shows two vertical lifelines: TDF on the left and PCRF on the right. A horizontal arrow labeled '1. Diameter CCR' points from the TDF lifeline to the PCRF lifeline. A return horizontal arrow labeled '2. Diameter CCA' points from the PCRF lifeline back to the TDF lifeline.](d980a3f9608055996a07f31788baf827_img.jpg) + +``` + +sequenceDiagram + participant TDF + participant PCRF + Note left of TDF: TDF detects first application start + TDF->>PCRF: 1. Diameter CCR + PCRF-->>TDF: 2. Diameter CCA + +``` + +Sequence diagram showing TDF Session Establishment in case of unsolicited reporting. The diagram shows two vertical lifelines: TDF on the left and PCRF on the right. A horizontal arrow labeled '1. Diameter CCR' points from the TDF lifeline to the PCRF lifeline. A return horizontal arrow labeled '2. Diameter CCA' points from the PCRF lifeline back to the TDF lifeline. + +**Figure 4.6.1A.1: TDF Session Establishment in case of unsolicited reporting** + +1. The TDF initiates a session by sending a CCR to the PCRF using the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The TDF provides the full UE IP address using either Framed-IP-Address AVP or Framed-Ipv6-Prefix AVP and, if available, the PDN identifier. The TDF also includes the TDF-Application-Identifier AVP, the Flow-Information AVP of the detected application when service data flow descriptions are deducible, within the Application-Detection-Information AVP and sets the event trigger value with APPLICATION\_START. If Flow-Information AVP is included, the TDF-Application-Instance-Identifier shall also be included within the Application-Detection-Information AVP in order to allow correlation of APPLICATION\_START. +- 2 The PCRF stores the information and acknowledges the session establishment by sending a CCA. The PCRF may include the Ipv6 prefix within the Framed-Ipv6-Prefix AVP if the established TDF session is Ipv6 address related. + +NOTE 1: The TDF handles each Ipv4 address and Ipv6 prefix within a separate TDF session. + +NOTE 2: In the scenario where the TDF performs initial Application Detection on 5vailable simultaneous traffic flows for the same Ipv6 prefix (i.e. two or more from Ipv6 addresses of the same IP-CAN session) the TDF could not be aware that those flows belong to the same IP-CAN session until a response is received from the PCRF, containing the Ipv6 prefix. This leads to using separate TDF sessions for the Ipv6 addresses for the same IP-CAN session. The TDF reports new application detection information related to that Ipv6 prefix via any of the TDF sessions at a later stage. + +### 4.6.2 TDF Session termination + +In the following procedures, the PCRF is the H-PCRF for the roaming UE with home routed access and the V-PCRF for the roaming UE with visited access. + +This procedure applies in any of the following cases: + +- the corresponding IP-CAN session is terminated; + +- the Ipv4 address of a dual stack IP-CAN session is released and there is an active Ipv4 address related TDF session for the IP-CAN session (only for unsolicited application reporting); +- at any point of time when the PCRF decides that the session with TDF is to be terminated (e.g. subscriber profile changes). + +![Sequence diagram for TDF Session Termination between TDF and PCRF.](f6d72d7c790e7f585532140f3971639a_img.jpg) + +``` +sequenceDiagram + participant PCRF + participant TDF + Note right of TDF: 2. Removal/deactivation of all ADC Rules. + PCRF->>TDF: 1. Diameter RAR + TDF-->>PCRF: 3. Diameter RAA + TDF->>PCRF: 4. Diameter CCR + PCRF-->>TDF: 5. Diameter CCA +``` + +The diagram illustrates the sequence of messages for TDF Session Termination. It starts with the PCRF sending a Diameter RAR (1) to the TDF. The TDF then performs the removal/deactivation of all ADC Rules (2). Following this, the TDF sends a Diameter RAA (3) to acknowledge the RAR. Next, the TDF sends a Diameter CCR (4) to the PCRF, indicating the session termination and reporting resource usage. Finally, the PCRF sends a Diameter CCA (5) to acknowledge the termination. + +Sequence diagram for TDF Session Termination between TDF and PCRF. + +**Figure 4.6.2.1: TDF Session Termination** + +1. The PCRF sends a RAR including the Session-Release-Cause AVP to request that the TDF terminates the TDF session. +2. For the solicited application reporting, the TDF removes/deactivates all the ADC Rules which are applied to the TDF session. +3. The TDF sends a RAA to acknowledge the RAR. +4. The TDF sends a CCR to the PCRF, indicating the TDF Session termination. The TDF requests the termination of the Sd session using the CC-Request-Type AVP set to the value TERMINATION\_REQUEST. For solicited application reporting, if the usage monitoring is enabled, the TDF informs the PCRF about the resources that have been consumed by the user since the last report in the same request. +5. The PCRF acknowledges the TDF session termination by sending a CCA to the TDF. + +### 4.6.3 TDF Session modification + +#### 4.6.3.1 Application Detection, Reporting and Control Rules Request + +In the following procedure, the PCRF is the H-PCRF for the roaming UE with home routed access and the V-PCRF for the roaming UE with visited access. + +![Sequence diagram for Application Detection, Reporting and Control Rules Request](0236eff05bcb8f3a343ea7933aaa306b_img.jpg) + +``` +sequenceDiagram + participant TDF + participant PCRF + Note left of TDF: 1. Trigger to report the events. + TDF->>PCRF: 2. Diameter CCR + Note right of PCRF: 3. Makes the PCC/QoS/ADC decisions + PCRF->>TDF: 4. Diameter CCA + Note left of TDF: 5. Installation, modification and removal of the ADC Rules. +``` + +The diagram illustrates a sequence of interactions between a TDF (Traffic Detection Function) and a PCRF (PDN Gateway Control Function). The sequence starts with the TDF triggering an event (1). It then sends a Diameter CCR (Credit Control Request) to the PCRF (2). The PCRF makes PCC/QoS/ADC decisions (3) and responds with a Diameter CCA (Credit Control Answer) (4). Finally, the TDF performs the installation, modification, and removal of the ADC Rules (5), which is shown in a dashed box. + +Sequence diagram for Application Detection, Reporting and Control Rules Request + +**Figure 4.6.3.1.1 Application Detection, Reporting and Control Rules Request** + +1. TDF is triggered to report an event(s) (e.g. The TDF detects the start/stop of an application traffic that matches with one or more activated ADC rules that do not contain the Mute-Notification AVP) for a TDF session. For the start of traffic detection, in case the enforcement actions were provided as a part of ADC rules, the TDF enforces corresponding actions for solicited application reporting. +2. The TDF sends a Diameter CCR to the PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST to report an event. For the start of traffic detection, if PCRF has previously subscribed to the APPLICATION\_START/APPLICATION\_STOP Event-Triggers, the TDF includes TDF-Application-Identifier AVP, the Flow-Information AVP of the detected application when service data flow descriptions are deducible, within the Application-Detection-Information AVP and sets the event trigger value with + +APPLICATION\_START. If Flow-Information AVP is included, the TDF-Application-Instance-Identifier shall also be included within the Application-Detection-Information AVP in order to allow correlation of APPLICATION\_START. For the stop of traffic detection, if PCRF has previously subscribed to the APPLICATION\_START/APPLICATION\_STOP Event-Triggers, the TDF includes TDF-Application-Identifier AVP, the TDF-Application-Instance-Identifier AVP, if provided in the report of the start of application traffic detection within the Application-Detection-Information AVP and sets the event trigger value with APPLICATION\_STOP. For the solicited application reporting, if usage monitoring is enabled and the usage threshold is reached or the PCRF removes the last ADC rule applicable for certain monitoring key or disables usage monitoring or requests usage report, the TDF may inform the PCRF about the corresponding usage that have been consumed by the user since the last report. + +3. The PCRF stores the information, received in the Diameter CCR and makes the PCC/QoS and – in the solicited reporting case – ADC decisions. +4. The PCRF acknowledges to the TDF by sending a Diameter CCA. For the solicited application reporting, the PCRF may provide a new ADC decisions by including the ADC-Rule-Install AVP and/or ADC-Rule-Remove AVP to the TDF within this acknowledge. +5. For the solicited application reporting, the TDF installs, modifies and removes the ADC rules according the new ADC decisions provided in step 4. + +NOTE: If the installation or modification of one or more ADC rules fails, the TDF reports the failure to the PCRF as defined in clause 4b.5.5 of 3GPP TS 29.212 [9]. + +#### 4.6.3.2 Application Detection and Control Rules Provision + +In the following procedure, the PCRF is the H-PCRF for the roaming UE with home routed access and the V-PCRF for the roaming UE with visited access. This procedure is applicable only for the solicited application reporting. + +![Sequence diagram for Application Detection and Control Rules Provision between TDF and PCRF.](e1a0d046fbe7f28f5e93a47091851747_img.jpg) + +``` +sequenceDiagram + participant TDF + participant PCRF + Note right of PCRF: 1. Trigger to update the ADC decisions. + PCRF->>TDF: 2. Diameter RAR + Note left of TDF: 3. Installation, modification and removal of the ADC Rules. + TDF->>PCRF: 4. Diameter RAA +``` + +The diagram is a sequence diagram illustrating the interaction between a TDF (Traffic Detection Function) and a PCRF (PDN Gateway Control Function). It consists of four numbered steps: 1. A trigger to update the ADC decisions occurs at the PCRF. 2. The PCRF sends a Diameter RAR (Re-Auth-Request) message to the TDF. 3. The TDF performs the installation, modification, and removal of the ADC Rules. 4. The TDF sends a Diameter RAA (Re-Auth-Answer) message back to the PCRF. + +Sequence diagram for Application Detection and Control Rules Provision between TDF and PCRF. + +**Figure 4.6.3.2.1 Application Detection and Control Rules Provision** + +1. The PCRF receives an internal or external trigger (e.g. the subscriber's profile configuration is changed) to update the ADC rule or notify the event occurred at the PCEF/BBERF for a TDF session. +2. The PCRF sends a Diameter RAR to provide a new ADC decision by including the ADC-Rule-Install AVP and/or ADC-Rule-Remove AVP or notify the event occurred at the PCEF/BBERF by including the Event-Report-Indication AVP. + +3. The TDF stores the information, received in the Diameter RAR. The TDF installs, modifies and removes the ADC rules according to the new ADC decisions provided in step 2. +4. The TDF acknowledges to the PCRF by sending a Diameter RAA to inform the PCRF about the outcome of the actions related to the decision(s). + +## 4.7 Spending limits Procedures over Sy reference point + +### 4.7.1 Initial Spending Limit Report Request + +In the following procedure, the signalling flow for the H-PCRF to request the status of the policy counters available at the OCS, and to subscribe to updates of these policy counters by the OCS. If the H-PCRF provides the list of policy counter identifier(s), the OCS returns the policy counter status per policy counter identifier provided by the PCRF. If the H-PCRF does not provide the list of policy counter identifier(s), the OCS returns the policy counter status for all policy counter identifier(s), which are available for this subscriber. + +![Sequence diagram showing the Initial Spending Limit Report Request procedure between H-PCRF and OCS. The H-PCRF sends a Diameter SLR (Step 2) to the OCS, and the OCS responds with a Diameter SLA (Step 3). A box labeled '1. Policy decision depends on spending info' is shown above the SLR message.](0b87abe67b21a93777287649c33e755d_img.jpg) + +``` + +sequenceDiagram + participant H-PCRF + participant OCS + Note left of H-PCRF: 1. Policy decision depends on spending info + H-PCRF->>OCS: 2. Diameter SLR + OCS-->>H-PCRF: 3. Diameter SLA + +``` + +Sequence diagram showing the Initial Spending Limit Report Request procedure between H-PCRF and OCS. The H-PCRF sends a Diameter SLR (Step 2) to the OCS, and the OCS responds with a Diameter SLA (Step 3). A box labeled '1. Policy decision depends on spending info' is shown above the SLR message. + +**Figure 4.7.1: Initial Spending Limit Report Request** + +1. The H-PCRF retrieves subscription information that indicates that policy decisions depend on policy counter(s) held at the OCS and optionally the list of policy counter identifier(s). +2. The H-PCRF sends a Diameter SLR command if no Sy session yet has been established for this subscriber. The Diameter SLR command includes the Subscription-Id AVP (e.g. IMSI) and optionally the list of policy counter identifier(s) within Policy-Counter-Identifier AVPs. The request also includes the SL-Request-Type AVP which set to the value INITIAL\_REQUEST (0). +3. The OCS sends a Diameter SLA command to the PCRF. The Diameter SLA includes a Policy-Counter-Status-Report AVP for each requested policy counter identifier containing the policy counter identifier and the current status value, optionally pending policy counter statuses with the activation times, and Result-Code AVP contains the result of the operation. When no policy counter identifier(s) was provided, the Diameter SLA includes a Policy-Counter-Status-Report AVP for all policy counter identifiers applicable to the subscriber. The OCS stores the H-PCRF's subscription to changes in the status of all policy counter identifiers provided to the H-PCRF in the Diameter SLA. + +### 4.7.2 Intermediate Spending Limit Report Request + +This clause describes the signalling flow for the H-PCRF to request the status of additional policy counters available at the OCS or to remove the request for the status of policy counters available at OCS. If the H-PCRF provides the list of policy counter identifier(s), the OCS returns the policy counter status per policy counter identifier provided by the PCRF. + +![Sequence diagram for Intermediate Spending Limit Report Request](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` +sequenceDiagram + participant H-PCRF + participant OCS + Note left of H-PCRF: 1. Additional or fewer policy counters are determined to be relevant for policy decision + H-PCRF->>OCS: 2. Diameter SLR + OCS-->>H-PCRF: 3. Diameter SLA + Note left of H-PCRF: 4. Policy Decision +``` + +The diagram illustrates the interaction between H-PCRF and OCS for an Intermediate Spending Limit Report Request. It starts with a note on the H-PCRF side indicating that additional or fewer policy counters are determined to be relevant for a policy decision. The H-PCRF then sends a Diameter SLR (Spending Limit Report) message to the OCS. The OCS responds with a Diameter SLA (Spending Limit Answer) message. Finally, a note on the H-PCRF side indicates a policy decision is made. + +Sequence diagram for Intermediate Spending Limit Report Request + +**Figure 4.7.2: Intermediate Spending Limit Report Request** + +1. The H-PCRF decides to modify the list of subscribed policy counters, e.g. PCRF determines that policy decisions depend on additional policy counter identifier(s) held at the OCS or that notifications of policy counter status changes for some policy counters are no longer required. +2. The H-PCRF sends a Diameter SLR command, optionally including the list of policy counter identifier(s) within Policy-Counter-Identifier(s) AVPs. The request also includes the SL-Request-Type AVP which set to the value INTERMEDIATE\_REQUEST (1). +3. The OCS sends the Diameter SLA command to the PCRF including Policy-Counter-Status-Report AVP(s) containing the policy counter identifier, the current status value and optionally pending policy counter statuses with the activation times. Result-Code contains the result of the operation is also included in the response. +4. The PCRF makes the policy decision based on the information provided by the OCS. + +### 4.7.3 Final Spending Limit Report Request + +This clause describes the signalling flow for the H-PCRF to unsubscribe to any future updates of policy counters for a given subscriber by the OCS. It cancels the request for reporting the change of the status of the policy counters available at the OCS. + +![Sequence diagram for Final Spending Limit Report Request](54fabc351eda5228d2fa28cd9ba07971_img.jpg) + +``` +sequenceDiagram + participant H-PCRF + participant OCS + Note left of H-PCRF: 1. Decision to unsubscribe to changes in the PolicyCounter-Status + H-PCRF->>OCS: 2. Diameter STR + OCS-->>H-PCRF: 3. Diameter STA +``` + +The diagram illustrates the interaction between H-PCRF and OCS for a Final Spending Limit Report Request. It starts with a note on the H-PCRF side indicating a decision to unsubscribe to changes in the PolicyCounter-Status. The H-PCRF then sends a Diameter STR (Spending Limit Termination Request) message to the OCS. The OCS responds with a Diameter STA (Spending Limit Termination Answer) message. + +Sequence diagram for Final Spending Limit Report Request + +**Figure 4.7.3: Final Spending Limit Report Request** + +1. The PCRF decides that policy decisions for a given user no longer depend on policy counter(s) to which the PCRF has existing subscriptions for status change notification. + +2. The H-PCRF sends the Diameter STR command to the OCS to cancel the notification request from the OCS on policy counter status. The request includes the Termination-Cause which contains the reason why the session was terminated set to "DIAMETER\_LOGOUT". +3. The OCS sends the Diameter STA command to the H-PCRF with Result-Code contains the result of the operation. + +### 4.7.4 Spending Limit Report + +This clause describes the signalling flow for the OCS to notify the changes of the status of a subscribed policy counter(s) available at the OCS for that subscriber. Alternatively, the signalling flow can be re-used by the OCS to provide one or more pending statuses for a subscribed policy counter together with the time that have to be applied. + +![Sequence diagram for Spending Limit Report showing interactions between H-PCRF and OCS.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +``` + +sequenceDiagram + participant H-PCRF + participant OCS + Note right of OCS: 1. Policy Counter Status change (e.g. Threshold reached) + OCS->>H-PCRF: 2. Diameter SNR + H-PCRF->>OCS: 3. Diameter SNA + +``` + +The diagram illustrates the signalling flow for the Spending Limit Report. It features two vertical lifelines: H-PCRF on the left and OCS on the right. + 1. A message box on the OCS lifeline indicates the initial event: "1. Policy Counter Status change (e.g. Threshold reached)". + 2. A thick horizontal arrow labeled "2. Diameter SNR" points from the OCS lifeline to the H-PCRF lifeline. + 3. A thick horizontal arrow labeled "3. Diameter SNA" points from the H-PCRF lifeline back to the OCS lifeline. + +Sequence diagram for Spending Limit Report showing interactions between H-PCRF and OCS. + +**Figure 4.7.4: Spending Limit Report** + +1. The OCS detects that status of a policy counter identifier(s) has changed and the PCRF requested notification of changes in the status of a policy counter(s). Alternatively, if the OCS detects a policy counter status will change at a future point in time, the OCS shall be able to instruct the PCRF to apply one or more pending statuses for a requested policy counter. +2. When the status of a specific policy counter changes, or the OCS detects that a policy counter status will change at a future point in time and decides to instruct the PCRF to apply one or more pending statuses for a requested policy counter, the OCS shall determine the Sy sessions impacted by the change (i.e. those Sy sessions that have subscribed to status change notifications for the changed policy counter) and send the Diameter SNR command to the PCRF associated with each affected Sy session including one Policy-Counter-Status-Report AVP. If several counters change status at the same time, the OCS may group the status change notifications into a single Spending Limit Report request to the PCRF by sending multiple Policy-Counter-Status-Report AVPs in the request. + +NOTE: Sy session is per UE. And more than one Sy session will exist when the UE has IP-CAN session connection with more than one PCRF. + +3. The H-PCRF acknowledges the request by sending a Diameter SNA command with a Result-Code AVP set to DIAMETER\_SUCCESS and use the status of the received policy counter(s) as input to its policy decision to apply operator defined actions, e.g. downgrade the QoS. The PCRF shall ignore an unknown policy counter status report for all unknown policy counter identifiers in the SNR from the OCS. + +## 4.8 Call flows for User Plane Congestion Management + +### 4.8.1 General + +The call flows for User Plane Congestion Management (UPCON) over Np reference point are specified as follows: + +- RAN User Plane Congestion Information (RUCI) reporting, in which non-aggregated RUCI reporting and aggregated RUCI reporting are included. + +- Reporting restriction provisioning +- UE mobility between RAN Congestion Awareness Functions (RCAF) +- Removal of UE context + +### 4.8.2 RUCI reporting + +#### 4.8.2.1 Non-aggregated RUCI report procedure + +![Sequence diagram for Non-aggregated RUCI reporting between RCAF and PCRF.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +``` +sequenceDiagram + participant RCAF + participant PCRF + Note left of RCAF: RUCI reporting + RCAF->>PCRF: 1. Diameter NRR + PCRF-->>RCAF: 2. Diameter NRA +``` + +The diagram shows a sequence of two messages between RCAF and PCRF. RCAF sends a '1. Diameter NRR' message to PCRF, and PCRF responds with a '2. Diameter NRA' message. + +Sequence diagram for Non-aggregated RUCI reporting between RCAF and PCRF. + +**Figure 4.8.2.1.1: Non-aggregated RUCI reporting** + +1. The RCAF sends a diameter NR-Request command to the PCRF, including the user id, PDN ID, the congestion level info and additional parameters as defined in clause 4.4.1.2 of 3GPP TS 29.217 [36]. +2. The PCRF stores the related information and acknowledges the RUCI reporting by sending a Diameter NR-Answer including the PCRF id. + +#### 4.8.2.2 Aggregated RUCI report procedure + +![Sequence diagram for Aggregated RUCI reporting between RCAF and PCRF.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +``` +sequenceDiagram + participant RCAF + participant PCRF + Note left of RCAF: Aggregated RUCI reporting + RCAF->>PCRF: 1. Diameter ARR + PCRF-->>RCAF: 2. Diameter ARA +``` + +The diagram shows a sequence of two messages between RCAF and PCRF. RCAF sends a '1. Diameter ARR' message to PCRF, and PCRF responds with a '2. Diameter ARA' message. + +Sequence diagram for Aggregated RUCI reporting between RCAF and PCRF. + +**Figure 4.8.2.2.1: Aggregated RUCI reporting** + +1. The RCAF sends a Diameter AR-Request command to the PCRF, including one or more Aggregated-RUCI-Report AVP and additional parameters as defined in clause 4.4.1.3 of 3GPP TS 29.217 [36]. The PCRF is the common destination PCRF for a set of user id and PDN ID and identified by the PCRF id returned in the previous non-aggregating RUCI reporting. +2. The PCRF stores the related information and acknowledges the RUCI reporting by sending a Diameter AR-Answer back to the RCAF. + +### 4.8.3 Np reporting restriction provisioning + +The Np reporting restriction provisioning is used by the PCRF to stop RUCI reporting for a specific user id and PDN ID. It is also used by the PCRF to specify, modify or disable restrictions for RUCI reporting. + +![Sequence diagram for Np reporting restriction provisioning between RCAF and PCRF.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +``` +sequenceDiagram + participant RCAF + participant PCRF + Note right of PCRF: 1. Diameter MUR + PCRF->>RCAF: 1. Diameter MUR + Note left of RCAF: 2. Diameter MUA + RCAF->>PCRF: 2. Diameter MUA +``` + +The diagram shows a sequence of two messages between RCAF and PCRF. The PCRF sends a '1. Diameter MUR' message to the RCAF, and the RCAF responds with a '2. Diameter MUA' message to the PCRF. + +Sequence diagram for Np reporting restriction provisioning between RCAF and PCRF. + +**Figure 4.8.3.1: Np reporting restriction provisioning** + +1. The PCRF sends a Diameter MUR command to the RCAF for the provisioning of RUCI reporting restriction including the parameters as defined in clause 4.4.2 of 3GPP TS 29.217 [36]. +2. The RCAF responds a Diameter MUA command to the PCRF including the parameters as defined in clause 4.4.2 of 3GPP TS 29.217 [36]. + +### 4.8.4 UE mobility between RCAFs + +This signalling flow describes the mobility handling of a UE from one RCAF to another RCAF. The UE is affected by congestion for both RCAFs. + +![Sequence diagram for UE mobility from RCAF1 to RCAF2.](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg) + +``` +sequenceDiagram + participant RCAF1 + participant RCAF2 + participant PCRF + Note right of RCAF1: 1. Diameter NRR + RCAF1->>PCRF: 1. Diameter NRR + Note left of RCAF1: 2. Diameter NRA + PCRF->>RCAF1: 2. Diameter NRA + Note right of RCAF1: ... + Note left of RCAF2: ... + Note right of PCRF: ... + Note left of RCAF2: UE moves to RCAF2 + Note right of RCAF2: 3. Diameter NRR + RCAF2->>PCRF: 3. Diameter NRR + Note left of RCAF2: 4. Diameter NRA + PCRF->>RCAF2: 4. Diameter NRA + Note right of RCAF2: 5. Removal of UE context in RCAF1 + RCAF2->>RCAF1: 5. Removal of UE context in RCAF1 +``` + +The diagram illustrates the signalling flow for UE mobility from RCAF1 to RCAF2. It starts with RCAF1 sending a '1. Diameter NRR' to the PCRF and receiving a '2. Diameter NRA' in response. After a period of time (indicated by dots), the UE moves to RCAF2. RCAF2 then sends a '3. Diameter NRR' to the PCRF and receives a '4. Diameter NRA'. Finally, RCAF2 sends a '5. Removal of UE context in RCAF1' message to RCAF1. + +Sequence diagram for UE mobility from RCAF1 to RCAF2. + +**Figure 4.8.4.1: UE mobility from RCAF1 to RCAF2 (the UE is affected by congestion at RCAF2 after the UE was earlier affected by congestion at RCAF1)** + +1. The UE is located in the RCAF1 which is affected by congestion. The RCAF1 sends a Diameter NRR command to the PCRF for reporting RUCI including the parameters as defined in clause 4.4.1.2 of 3GPP TS 29.217 [36]. +2. The PCRF stores the identity of RCAF1 for the given UE and responds a Diameter NRA command to the RCAF1 including the parameters as defined in clause 4.4.1.2 of 3GPP TS 29.217 [36]. +3. The UE moves to the RCAF2 which is also affected by congestion. The RCAF2 sends a Diameter NRR command to the PCRF for reporting RUCI of the same UE including the parameters as defined in clause 4.4.1.2 of 3GPP TS 29.217 [36]. +4. The PCRF stores the identity of RCAF2 for the given UE and responds a Diameter NRA command to the RCAF2 including the parameters as defined in clause 4.4.1.2 of 3GPP TS 29.217 [36]. +5. The PCRF initiates a removal of the UE context to RCAF1 to release the context of the given user id and PDN ID, including the parameters as defined in clause 4.4.4 of 3GPP TS 29.217 [36]. + +### 4.8.5 Removal of UE context + +This signalling flow describes the removal of a UE context from the RCAF. + +![Sequence diagram showing UE context removal in RCAF. The diagram consists of two vertical lifelines labeled RCAF and PCRF. A horizontal arrow labeled '1. Diameter MUR' points from the PCRF lifeline to the RCAF lifeline. A horizontal arrow labeled '2. Diameter MUA' points from the RCAF lifeline to the PCRF lifeline.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +``` +sequenceDiagram + participant PCRF + participant RCAF + Note right of PCRF: 1. Diameter MUR + PCRF->>RCAF: 1. Diameter MUR + Note left of RCAF: 2. Diameter MUA + RCAF->>PCRF: 2. Diameter MUA +``` + +Sequence diagram showing UE context removal in RCAF. The diagram consists of two vertical lifelines labeled RCAF and PCRF. A horizontal arrow labeled '1. Diameter MUR' points from the PCRF lifeline to the RCAF lifeline. A horizontal arrow labeled '2. Diameter MUA' points from the RCAF lifeline to the PCRF lifeline. + +**Figure 4.8.5.1: UE context removal in RCAF** + +1. The PCRF sends a Diameter MUR command to the RCAF to release the context of the given user id and PDN ID, including the parameters as defined in clause 4.4.4 of 3GPP TS 29.217 [36]. +2. The RCAF responds with a Diameter MUA command to the PCRF including the parameters as defined in clause 4.4.4 of 3GPP TS 29.217 [36]. The RCAF releases the context corresponding to the given user id and PDN ID, including any reporting restriction. + +## 4.9 Traffic Steering Control Procedures over St reference point + +### 4.9.1 St Session Establishment + +In the following procedure, the PCRF initiates the St session establishment procedure and provides the traffic steering control information to the TSSF due to the PCRF determines that the traffic steering control is needed for the IP-CAN session. + +![Sequence diagram for St Session Establishment between PCRF and TSSF.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` +sequenceDiagram + participant PCRF + participant TSSF + Note right of PCRF: 1. Diameter TSR + PCRF->>TSSF: 1. Diameter TSR + Note left of TSSF: 2. Diameter TSA + TSSF->>PCRF: 2. Diameter TSA +``` + +A sequence diagram illustrating the St Session Establishment between a PCRF and a TSSF. The PCRF sends a '1. Diameter TSR' message to the TSSF, and the TSSF responds with a '2. Diameter TSA' message. + +Sequence diagram for St Session Establishment between PCRF and TSSF. + +**Figure 4.9.1.1: St Session Establishment** + +1. The PCRF initiates session between the PCRF and TSSF and provisions the applicable ADC Rules for the corresponding IP-CAN session by sending a Diameter TSR to the TSSF, including the Request-Type AVP set to the value "0" and other parameters as defined in subclause 4c.4.1 of 3GPP TS 29.212 [9]. +2. The TSSF installs and/or activates the ADC rules and acknowledges to the PCRF by sending a Diameter TSA command. + +### 4.9.2 St Session Modification + +In the following procedure, the PCRF updates the traffic steering control information at the TSSF due to the PCRF determines that the traffic steering control information needs to be updated for the IP-CAN session (e.g. Subscription is changed) or notifies the TSSF that the IPv4 address is allocated/released. + +![Sequence diagram for St Session Modification between PCRF and TSSF.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +``` +sequenceDiagram + participant PCRF + participant TSSF + Note right of PCRF: 1. Diameter TSR + PCRF->>TSSF: 1. Diameter TSR + Note left of TSSF: 2. Diameter TSA + TSSF->>PCRF: 2. Diameter TSA +``` + +A sequence diagram illustrating the St Session Modification between a PCRF and a TSSF. The PCRF sends a '1. Diameter TSR' message to the TSSF, and the TSSF responds with a '2. Diameter TSA' message. + +Sequence diagram for St Session Modification between PCRF and TSSF. + +**Figure 4.9.2.1: St Session Modification** + +1. The PCRF provisions the new, updated and/or requests to remove ADC rules for the corresponding IP-CAN session or notifies the TSSF that the IPv4 address is allocated/released by sending a Diameter TSR command to the TSSF, including the Request-Type AVP set to the value "1" and other parameters as defined in subclause 4c.4.1 or 4c.4.4 of 3GPP TS 29.212 [9]. +2. The TSSF installs, modifies and/or removes the ADC rules or activates and/or deactivates the ADC rules and acknowledges to the PCRF by sending a Diameter TSA commands. + +### 4.9.3 St Session Termination + +In the following procedure, the the PCRF initiates the St session termination procedure and removes all the traffic steering control information to the TSSF due to the corresponding IP-CAN session is terminated or the H-PCRF determines that the traffic steering control information is not needed for the IP-CAN session any longer (e.g. Subscription has changed). + +![Sequence diagram for St Session Termination](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` +sequenceDiagram + participant PCRF + participant TSSF + Note right of TSSF: 2. Removes/deactivates all the ADC rules + PCRF->>TSSF: 1. Diameter STR + TSSF->>PCRF: 3. Diameter STA +``` + +The diagram illustrates the St Session Termination procedure. It features two vertical lifelines: PCRF on the left and TSSF on the right. The sequence of messages is as follows: 1. A 'Diameter STR' message is sent from the PCRF to the TSSF. 2. Upon receiving the STR, the TSSF performs an internal action labeled 'Removes/deactivates all the ADC rules'. 3. Finally, a 'Diameter STA' message is sent from the TSSF back to the PCRF to acknowledge the termination. + +Sequence diagram for St Session Termination + +**Figure 4.9.3.1: St Session Termination** + +1. The PCRF sends an STR to the TSSF to terminate the session between the PCRF and the TSSF. +2. The TSSF removes/deactivates all the ADC Rules which are applied to the session. +3. The TSSF sends an STA to acknowledge the STR. + +### 4.9.4 St notification initiated by the TSSF + +In the following procedure, the TSSF reports the ADC rule error when the ADC rule can't be enforced any longer. + +![Sequence diagram for St notification initiated by the TSSF](f57a881fcbcaf494a7dedc4f61224991_img.jpg) + +``` +sequenceDiagram + participant TSSF + participant PCRF + TSSF->>PCRF: 1. Diameter TNR + PCRF->>TSSF: 2. Diameter TNA +``` + +The diagram illustrates the St notification initiated by the TSSF. It features two vertical lifelines: TSSF on the left and PCRF on the right. The sequence of messages is as follows: 1. A 'Diameter TNR' message is sent from the TSSF to the PCRF. 2. Upon receiving the TNR, the PCRF responds with a 'Diameter TNA' message back to the TSSF. + +Sequence diagram for St notification initiated by the TSSF + +**Figure 4.9.4.1: St notification initiated by the TSSF** + +1. The TSSF reports the ADC rules error by sending a Diameter TNR command to the PCRF as defined in subclause 4c.4.3 of 3GPP TS 29.212 [9]. +2. The PCRF acknowledges to the TSSF by sending a Diameter TNA command. + +## 4.10 Negotiation for future background data transfer procedure over Nt reference point + +The following procedure shows the signaling flow for the SCEF to request the transfer policy for future background data transfer determined by the H-PCRF. + +![Sequence diagram showing the negotiation for future background data transfer over the Nt reference point between H-PCRF and SCEF.](21ad58fee90f2be50708ff541d225507_img.jpg) + +``` +sequenceDiagram + participant SCEF + participant H-PCRF + Note left of H-PCRF: 2.H-PCRF determines the transfer policies + SCEF->>H-PCRF: 1. Diameter BTR + H-PCRF->>SCEF: 3. Diameter BTA + SCEF-->>H-PCRF: 4. Diameter BTR + H-PCRF-->>SCEF: 5. Diameter BTA +``` + +The diagram illustrates a sequence of five messages between the SCEF and the H-PCRF. The SCEF sends a Diameter BTR command (1) to the H-PCRF. The H-PCRF then determines the transfer policies (2). The H-PCRF sends a Diameter BTA command (3) to the SCEF. The SCEF sends a Diameter BTR command (4) to the H-PCRF. The H-PCRF sends a Diameter BTA command (5) to the SCEF. The messages 4 and 5 are shown as dashed arrows. + +Sequence diagram showing the negotiation for future background data transfer over the Nt reference point between H-PCRF and SCEF. + +**Figure 4.10.1: Negotiation for future background data transfer** + +1. Based on the SCS/AS request, the SCEF sends a Diameter BTR command to the H-PCRF for the request of transfer policy including the parameters as defined in subclause 4.4.1 of 3GPP TS 29.154 [56]. +2. The H-PCRF determines one or more transfer policies based on the information received from the SCEF and other available information (e.g. network policy, existing transfer policies). +3. The H-PCRF sends a Diameter BTA command to the SCEF including the parameters as defined in subclause 4.4.1 of 3GPP TS 29.154 [56]. +4. If there is more than one transfer policy provided from the H-PCRF to the SCEF in the BTA command, when the SCEF receives the selected transfer policy from the SCS/AS, the SCEF sends a Diameter BTR command to the H-PCRF with the selected transfer policy. +5. The H-PCRF acknowledges the BTR command by sending BTA command. + +# 5 Binding Mechanism + +## 5.1 Overview + +The binding mechanism associates the session information with the IP-CAN bearer that is intended to carry the service data flow. + +For PCC rules with application identifier, and for certain IP-CAN types, up-link traffic can be received on other/additional IP-CAN bearers than the one determined by the binding mechanism (further details provided in clause 6.2.2.2 and the IP-CAN specific annexes of 3GPP TS 23.203 [2]). + +The binding mechanism includes three steps as defined in 3GPP TS 23.203 [2]: + +1. Session binding. +2. PCC Rule authorization and QoS Rule generation. +3. Bearer binding. + +The Session Binding function receives the Session Information and determines the relevant IP-CAN session. With this information the PCC Rule Authorization and QoS Rule generation function runs the policy rules and constructs the PCC rule(s) and if applicable, the QoS rule(s) if the authorization is granted. Finally the Bearer Binding function selects the IP-CAN bearer where the PCC rule(s) or QoS rule(s) should be installed within the IP-CAN session already known. + +PCC Rule Authorization and QoS Rule generation function and Bearer Binding function can take place without Session Binding at certain IP-CAN Session events (e.g. IP-CAN Session Establishment). + +## 5.2 Session Binding + +Session binding is the association of the AF session information to an IP-CAN session. + +When the PCRF accepts an AA-Request from the AF over the Rx interface with service information, the PCRF shall perform session binding and associate the described service IP flows within the AF session information (and therefore the applicable PCC rules) to one and only one existing IP-CAN session. When the PCRF receives an AA-Request from the P-CSCF acting as an AF over the Rx interface for P-CSCF Restoration, the PCRF shall perform session binding and associate the request to the existing IMS PDN connection and perform P-CSCF Restoration for that impacted IMS PDN connection. This association is done comparing the user IP address received via the Rx interface in either the Framed-IP-Address AVP or the Framed-Ipv6-Prefix AVP with the Ipv4 address or Ipv6 prefix received via the Gx interface. The UE Identity if present in the Subscription-Id AVP and the PDN information if available in the Called-Station-Id AVP may also assist on this association. The Domain identity if available in the IP-Domain-Id AVP may also assist on this association, e.g. if other user identity information than the UE IP address is unavailable and the UE IP addresses is not unique for a certain APN. + +NOTE 1: The UE IP address is unique per Domain identity. + +NOTE 2: The IP-Domain-Id AVP is helpful in the following scenario: Within a PLMN, there are several separate IP address domains, with PCEF(s) that allocate Ipv4 IP addresses out of the same private address range to Ues. The same IP address can thus be allocated to Ues served by PCEFs in different address domains. If one PCRF controls several PCEFs in different IP address domains, the UE IP address is thus not sufficient for the session binding. An AF can serve Ues in different IP address domains, either by having direct IP interfaces to those domains, or by having interconnections via NATs in the user plane between PCEFs and the AF. If a NAT is used, the AF obtains the IP address allocated to the UE via application level signalling and supplies it for the session binding as Framed-IP-Address to the PCRF. The AF supplies an IP-Domain-Id value denoting the IP address domain behind the NAT in addition. The AF can derive the appropriate value from the source address (allocated by the NAT) of incoming user plane packets. + +NOTE 3: When the scenario described in NOTE 2 applies and the AF is a P-CSCF it is assumed that the P-CSCF has direct IP interfaces to the different IP address domains and that no NAT is located between P-GW and P-CSCF. How a non-IMS AF obtains the UE private IP address to be provided to the PCRF is out of scope of the present release; it is unspecified how to support applications that use a protocol that does not retain the original UE's private IP address. + +If the Domain identity is not used to assist association, the PCRF will determine that the UE has an IP-CAN session if the IP address (Ipv4 or Ipv6) received over the Rx interface matches the Ipv4 address or Ipv6 prefix received via one or more of the following interfaces: Gx interface and S9 interface, and if the UE identity is used to assist the association, the UE identity received over the Rx interface matches the UE identity received via one or more of the following interfaces: Gx interface and S9 interface. + +If the Domain identity is used to assist association, the PCRF will determine that the UE has an IP-CAN session if the Domain identity received over the Rx interface matches the PCEF Identity received via the Gx interface, and the IP address (Ipv4) received over the Rx interface matches the Ipv4 address received via the Gx interface. + +For the roaming scenario, the Domain identity may be used for session binding when the AF and PCEF are located in same PLMN, i.e. for the home routed case, the Domain identity may be used by the (H-)PCRF for session binding, and for the visited case, Domain identity could be used by the V-PCRF for session binding. + +For an IP-CAN session associated to a dedicated APN for the purpose of offering services to remote UEs via a ProSe UE-to-network relay UE, the PCRF shall use the UE IPv6 prefix alone in the session binding. + +- NOTE 4: In case the UE identity in the IP-CAN and the application level identity for the user are of different kinds, the PCRF needs to maintain, or have access to, the mapping between the identities. Such mapping is not subject to specification within this TS. +- NOTE 5: An IPv6 address provided over Rx matches an IPv6 prefix provided over Gx or S9 if the IPv6 address belongs to the IPv6 (sub-)network prefix. +- NOTE 6: The PCRF derives the PCEF identity from the Origin-Host AVP of the CCR command received from the PCEF. In order to correlate the PCEF Identity and the domain identity received over the Rx interface, the PCRF uses configured mapping between those identities. The Domain Identity is useful for assistance in session binding if the Origin-Host of the Gx CCR command is not modified by intermediate Diameter proxies deployed between the PCEF and the PCRF. +- NOTE 7: The PCEF identity is not transported over S9 reference point in the present release. So for the visited access with AF located in HPLMN case, session binding assisted with Domain identity is not supported in the present release. Session binding is still possible based on other available information in addition to the IP address when provided by the AF, according to the current procedures. + +If the PCRF uses the Called-Station-Id AVP to assist the association, the PCRF shall apply the procedures in Annex I to match APN information. + +As a result from the session binding function, the PCRF identifies what IP-CAN session the current AF session is related with. If the PCRF is not capable of executing the Session Binding, the PCRF shall issue an AA-Answer command to the AF with a negative response. + +## 5.3 PCC Rule Authorization and QoS Rule Generation + +The PCRF shall perform the PCC rule authorization and QoS rule generation when the PCRF receives session information from an AF over Rx interface, when the PCRF receives notification of IP-CAN session events (e.g. establishment, modification) from the PCEF over Gx or S9 interface, when the PCRF receives IP-CAN events from the BBERF over Gxa/Gxc interface, or the PCRF receives a notification from the SPR that calls for a policy decision. The PCRF shall also perform PCC Rule Authorization and QoS Rule generation for dynamic PCC Rules already provisioned to the PCEF and dynamic QoS rules already provisioned to the BBERF due to internal PCRF triggers (e.g. policies are included or modified within PCRF). + +If the PCRF receives any traffic mapping information from the BBF that does not match any service data flow filter, the PCRF shall also perform PCC and/or QoS rule authorization when the UE's subscriber profile allows subscription based authorization. In this case, the PCRF shall treat the received traffic mapping information as if it is service data flow filter information. + +If the PCRF receives from the AF a reference ID together with the AF session information, the PCRF may provide it to the SPR in order to retrieve the corresponding transfer policy. The PCRF shall derive the PCC rules for the background data transfer according to the retrieved transfer policy. + +- NOTE 1: A transfer policy is only valid within its time window. The removal of outdated transfer policies from the SPR is up to implementation. + +If the PCRF receives information from the SPR for the invocation/revocation of a Priority EPS Bearer service (i.e. the MPS EPS Priority is set/removed or the MPS Priority Level changes while the MPS EPS Priority is set), then the PCRF should change the QCI/ARP of the dynamic PCC/QoS rules that have the same QCI/ARP as for the present default EPS bearer with the new QCI/ARP assigned to the default EPS bearer unless those PCC rules contain an indication that they have to be bound to the default EPS bearer. If there are active non-MPS services, the QCI/ARP of the PCC/QoS rules related to the non-MPS services shall also be changed. + +If the PCRF receives a request from the AF for the invocation/revocation of MPS for DTS (i.e., the MPS-Action AVP is set to enabled or to disabled, see 3GPP TS 29.214 [10]), then the PCRF shall behave according to clause 4.5.19.1 of 3GPP TS 29.212 [9]. + +If the PCRF receives information from the SPR that invokes/revokes the IMS Signalling Priority or changes the MPS Priority Level while IMS Signaling Priority is enabled, then the PCRF should + +- change the ARP of the dynamic PCC/QoS rules applicable to the IM CN signalling +- replace the predefined PCC rules applicable to the IM CN signalling by predefined rules that apply when the IMS Signalling Priority is set according to operator policies + +When IMS Signalling Priority is set, the PCRF should keep the ARP assigned to the default EPS bearer higher than the ARP related to the IM CN signalling bearer. + +NOTE 2. IMS Signalling Priority only applies to an APN enabled for IMS. + +The PCRF assigns appropriate QoS parameters (QCI, ARP, GBR, MBR, etc.) to each PCC or QoS rule. The PCRF takes the information received over Rx into account for determining the appropriate QCI/ARP. If the Rx authorization indicates IMS Multimedia Priority Service, then the PCRF shall allow the prioritization of the MPS session according to clauses 4.5.19.1.3 and 4a.5.14.1.3 in 3GPP TS 29.212 [9] for Gx/Gxx respectively. If the Rx authorization indicates Group Communication Service prioritization as described in 3GPP TS 23.468 [34], then the PCRF shall allow the prioritization of the Group Communication session according to clause 4.5.19 in 3GPP TS 29.212 [9]. + +The PCRF authorizes the affected PCC rules and /or QoS rules after successful Session Binding. By the authorization process the PCRF will determine whether the user can have access to the requested services and under what constraints. If so, the PCC rules and QoS rules are created or modified. If the Session Information is not authorized, a negative answer shall be issued to the AF by sending an AA-Answer command. + +The PCRF assigns an appropriate QCI to each PCC or QoS rule. IP-CAN specific restrictions and other information available to the PCRF (e.g. users subscription information, operator policies) shall be taken into account. Each PCC or QoS rule shall receive a QCI that can be supported by the IP-CAN. The PCRF shall ensure consistency between the QoS rules and PCC rules authorized for the same service data flow when QoS rules are derived from corresponding PCC rules. + +If PrioritySharing feature is supported over Rx reference point as described in 3GPP TS 29.214 [10], the PCRF shall apply the priority sharing procedures as described in 3GPP TS 29.212 [9], subclauses 4.5.27 and 4a.5.17, if applicable. + +In roaming scenarios, the V-PCRF may further authorize the rules received from the H-PCRF based on local operator policy. Depending on the local policy, the V-PCRF may change the authorized QoS for the affected rules. If local authorization of the rules fails, the V-PCRF shall issue a negative answer to the H-PCRF. + +## 5.4 Bearer Binding + +The Bearer Binding function is responsible for associating a PCC rule and QoS rule (if applicable) to an IP-CAN bearer within the IP-CAN session. The QoS demand in the rule, as well as the service data flow template, is input to the bearer binding. The selected bearer shall have the same QCI and ARP as the one indicated by the PCC or QoS rule. + +When Rule-Bound-to-Default-Bearer feature is supported as described in 3GPP TS 29.212 [9], the value included within the Default-Bearer-Indication AVP shall be used as input for the bearer binding instead of the QoS demand in the rule. + +NOTE 1: The PCRF provides the appropriate ARP/QCI for both PCC Rules and default bearer QoS so that the PCEF can perform a valid bearer binding. Alternatively, when Rule-Bound-to-Default-Bearer feature is supported, the PCRF can provide the Default-Bearer-Indication AVP within the PCC Rules to indicate that these PCC Rules have to be bound to the default bearer regardless of the provisioned ARP/QCI. + +The Bearer Binding Function (BBF) is located either at the BBERF or at the PCEF. + +The PCRF shall supply the PCC rules to be installed, modified or removed over Gx interface to PCEF. If there are gateway controls sessions associated with the Gx session, the PCRF shall also supply the QoS rules to be installed, modified, or removed over Gxa/Gxc interface to the BBERF. + +When Rule-Bound-to-Default-Bearer feature is supported, the BBF located at the PCEF shall bind to the default bearer the PCC rules that have indicated so. + +For the rules that do not contain an indication that they have to be bound to the default bearer, the BBF shall then check the QoS class identifier and ARP indicated by the rule and bind the rule with an IP-CAN bearer that has the same QoS class identifier and ARP. The BBF shall evaluate whether it is possible to use one of the existing IP-CAN bearers or not and, if applicable, whether to initiate IP-CAN bearer modification or not. If none of the existing bearers are possible to use, the BBF should initiate the establishment of a suitable IP-CAN bearer. The BBF should not bind rules with the PS to CS session continuity indicator to the same bearer as the rules without the PS to CS session continuity indicator. + +NOTE 2: For an IP-CAN, limited to a single IP-CAN bearer per IP-CAN session, the bearer is implicit, so finding the IP-CAN session is sufficient for successful bearer binding. + +NOTE 3: The handling of a rule with MBR>GBR is up to operator policy (e.g. an independent IP-CAN bearer may be maintained for that SDF to prevent unfairness between competing SDFs). + +NOTE 4: The QCI and ARP (including the Priority-Level, Pre-emption-Capability and Pre-emption-Vulnerability) are used for the bearer binding. Depending on operator policy, only the QCI and ARP Priority-Level can be used for bearer binding. In such a case, it is left to operator policy to determine whether different PCC rules with the same QCI and ARP Priority-Level but different Pre-emption-Capability and Pre-emption-Vulnerability can be bound to the same bearer. + +For an IP-CAN, where the BBF gains no information on what IP-CAN bearer the UE selects to send an uplink IP flow on, the binding mechanism shall assume that, for bi-directional service data flows, both downlink and uplink packets travel on the same IP-CAN bearer. + +Whenever the service data flow template, the QoS authorization of a PCC/QoS rule or the negotiated traffic mapping information change, the existing bearer bindings shall be re-evaluated. The re-evaluation may, for a service data flow, require a new binding with another IP-CAN bearer. The BBF should, if the PCRF requests the same change to the ARP/QCI for all PCC/QoS Rules bound to the same bearer, modify the bearer ARP/QCI as requested. + +NOTE 5: A QoS change of the default EPS bearer causes the bearer binding for PCC/QoS rules previously bound to the default EPS bearer to be re-evaluated. + +During PCC/QoS rules enforcement, if packet filters are provided to the UE, the BBF shall provide packet filters with the same content as that in the SDF template filters received over the Gx/Gxx interface from the PCRF within the Flow-Description or the Flow-Information AVP. The representation/format of the packet filters provided by the network to the UE is access-system dependent and may vary between accesses and also may be different from that of the SDF template filter on the Gx/Gxx interface. The PCRF may control the provisioning of packet filters to the UE, i.e. which filters are required to be sent to the UE, as described in 3GPP TS 29.212 [9]. + +If PCC rule(s) with application identifier(s) are the only PCC rule(s) that are bound to a bearer which requires traffic mapping information, the PCEF shall derive traffic mapping information based on implementation specific logic (e.g. traffic mapping information that effectively disallows any useful packet flows in uplink direction as described in clause 15.3.3.4 of 3GPP TS 23.060 [3]) and provides it to the UE. + +NOTE 6: For GPRS and EPS, the state of TFT packet filters, as defined in 3GPP TS 23.060 [3], for an IP-CAN session requires that there is at most one bearer with no TFT packet filter for the uplink direction. + +Requirements specific for each type of IP-CAN are defined in the IP-CAN specific Annex. The Bearer Binding Function may also be located in the PCRF (e.g. as specified in Annex D for GPRS running UE only IP-CAN bearer establishment mode). Selection of the Bearer Binding location shall be based on the Bearer Control Mode selected by the PCRF. + +# --- 6 QoS Parameters Mapping + +## 6.1 Overview + +Several QoS parameters mapping functions are needed during PCC interaction. These functions are located at the AF, PCRF, PCEF and UE. The main purpose of these mapping functions is the conversion of QoS parameters from one format to another. Examples of QoS information are: + +- Parts of a session description language (SDI), e.g. SDP, MPD. +- IP QoS parameters. +- Access specific QoS parameters. + +One QoS mapping function is located at the AF, which maps the application specific information into the appropriate AVPs that are carried over the Rx interface. The AF derives information about the service from the SDI or from other sources. The mapping is application specific. If SDP (IETF RFC 2327 [11]) is used as SDI, the AF should apply the mapping described in clause 6.2. If MPD (3GPP TS 26.247 [30]) is used, the AF may apply the mapping described in Annex X in 3GPP TS 26.247 [30]. For IMS, the mapping rules in clause 6.2 shall be used at the P-CSCF. The AF passes service information to the PCRF over the Rx interface. Subclause 6.2 specifies the QoS parameter mapping functions at the AF applicable for all IMS P-CSCFs regardless of the access technology. + +One QoS mapping function is located at the PCRF, which maps the service information received over the Rx interface into IP QoS parameters (e.g. QCI, GBR, MBR, ARP, ...). This mapping is access independent. Subclause 6.3 specifies the QoS mapping functions at the PCRF applicable for all accesses. + +The other mapping functions located at PCEF, BBERF, and UE are implementation dependent and are not specified within this specification except for GPRS case. + +The PCRF notes and authorizes the IP flows described within this service information by mapping from service information to Authorized IP QoS parameters for transfer to the PCEF/BBERF via the Gx/Gxx interface. Both the PCEF and BBERF will map from the Authorized IP QoS parameters to the access specific QoS parameters. For GPRS, the GGSN acting as PCEF will map from the Authorized IP QoS parameters to the Authorized UMTS QoS parameters. + +The general QoS mapping framework is shown in figure 6.1.1. + +![Figure 6.1.1: Framework for QoS mapping. This diagram illustrates the interaction between the User Equipment (UE), the Application Function (AF), the Policy and Charging Rules Function (PCRF), and the Gateway (GW) for QoS mapping. The UE (3) contains an Application, IP BS Manager, Translation / Mapping function, and Access-Specific BS Manager. The AF (1) contains an SDI Mapping function. The PCRF (2) contains a Policy Engine. The GW contains a PCEF/BBERF block with IP BS Manager, Translation / Mapping function (4), and Access-Specific BS Manager (5). Signalling paths are shown between the Application and AF (AF session signalling, possibly with SDI), between the AF and PCRF (Rx, Service information), between the PCRF and GW (Gx/Gxx, Authz IP QoS parameters), and between the GW and UE (Access-specific QoS parameters). A legend indicates that double-headed arrows represent signalling paths.](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) + +Figure 6.1.1: Framework for QoS mapping. This diagram illustrates the interaction between the User Equipment (UE), the Application Function (AF), the Policy and Charging Rules Function (PCRF), and the Gateway (GW) for QoS mapping. The UE (3) contains an Application, IP BS Manager, Translation / Mapping function, and Access-Specific BS Manager. The AF (1) contains an SDI Mapping function. The PCRF (2) contains a Policy Engine. The GW contains a PCEF/BBERF block with IP BS Manager, Translation / Mapping function (4), and Access-Specific BS Manager (5). Signalling paths are shown between the Application and AF (AF session signalling, possibly with SDI), between the AF and PCRF (Rx, Service information), between the PCRF and GW (Gx/Gxx, Authz IP QoS parameters), and between the GW and UE (Access-specific QoS parameters). A legend indicates that double-headed arrows represent signalling paths. + +**Figure 6.1.1: Framework for QoS mapping** + +NOTE 1: The AF can derive the Service information from the AF session signalling. + +NOTE 2: Service Information on Rx interface to Authorized IP QoS parameters mapping. + +NOTE 3: For the UE initiated bearer setup, the UE may derive IP QoS parameters, requested Access-Specific QoS parameters mapping and Authorized Access-Specific QoS parameters from the AF session signalling. + +NOTE 4: Authorized IP QoS parameters to Authorized Access-Specific QoS parameters mapping. + +NOTE 5: Access Specific QoS parameters with Authorized Access-Specific QoS parameters comparison. + +### 6.1.1 UE-Initiated IP-CAN bearers + +This clause covers the case where the UE is capable to initiate/modify the IP-CAN bearers sending requests to the PCEF/BBERF. When a UE desires to establish/modify an IP-CAN bearer the following steps are followed: + +1. The AF can map from SDI within the AF session signalling to service information passed to the PCRF over the Rx interface. (see clause 6.2 if SDP is used as SDI). +2. The PCRF shall map from the service information received over the Rx interface to the Authorized IP QoS parameters that shall be passed to the PCEF/BBERF via the Gx/Gxx interface. The mapping is performed for each IP flow. Upon a request from the PCEF/BBERF, the PCRF combines per direction the individual Authorized IP QoS parameters per flow (see clause 6.3). +3. The UE derives access specific QoS parameters, e.g. UMTS QoS parameters, and, if an IP BS manager is present, IP QoS parameters from the AF session signalling in an application specific manner. The IP and access specific QoS parameters should be generated according to application demands. + +For GPRS, the recommendations for conversational (3GPP TS 26.114 [29]) or streaming applications (3GPP TS 26.234 [6]) should also be taken into account when the UE derives the IP and UMTS QoS parameters. If SDP is used as SDI, e.g. for IMS, the UE should apply clause 6.5.1. and should also apply mapping rules for the authorised QoS parameters in clause 6.5.2 to derive the maximum values for the different requested bit rates and traffic classes. In case the UE multiplexes several IP flows onto the same PDP Context, it has to combine their IP and UMTS QoS parameters. If an IP BS manager is present, the Translation/Mapping function maps the IP QoS parameters to the corresponding UMTS QoS parameters. + +4. The PCEF/BBERF shall map from the Authorized IP QoS parameters received from PCRF to the Authorized access specific QoS parameters. + +For GPRS. The GGSN shall map to the Authorized UMTS QoS parameters (see clause 6.4.1.1). + +5. The PCEF/BBERF shall compare the requested access specific QoS parameters against the authorized access specific QoS parameters. + +For GPRS, the GGSN shall compare the UMTS QoS parameters of the PDP context against the Authorized UMTS QoS parameters (see clause 6.4.1.2). + +The mapping that takes place in the UE and the network should be compatible in order to ensure that the PCEF will be able to correctly authorize the session. + +Figure 6.1.1.1 shows the different kind of QoS parameters in the different points of QoS mapping figure. Due to the UE requests, there are bidirectional flows between the UE and the PCRF. + +![Diagram of QoS mapping for UE initiated IP CAN bearers showing interactions between UE, GW, AF, and PCRF.](68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg) + +The diagram illustrates the QoS mapping process for UE initiated IP CAN bearers across three main entities: UE (User Equipment), GW (Gateway), and AF (Application Function) / PCRF (PDN Gateway Control and Policy Function). + +- 3) UE:** Contains an **Application**, an **IP BS Manager** (dashed box), a **Translation / Mapping function**, and an **Access-Specific BS Manager**. + - The **Application** sends *AF session signalling, possibly with SDI* to the **AF**. + - There is a bidirectional signalling path between the **Application** and the **IP BS Manager**. + - The **IP BS Manager** sends *Authorized IP QoS parameters* to the **Translation / Mapping function** and receives *IP QoS parameters* from it. + - The **Translation / Mapping function** sends *Authorized Access-Specific QoS parameters* to the **Access-Specific BS Manager** and receives *Access-Specific QoS parameters* from it. +- GW:** Contains a sub-block **PCEF/BBRF** which includes an **IP BS Manager**, a **Translation / Mapping function** (labeled 4), and an **Access-Specific BS Manager** (labeled 5). + - The **IP BS Manager** in the GW sends *IP QoS parameters* to the **PCRF** and receives *Gx/Gxx* and *Authorized IP QoS parameters* from it. + - There is a bidirectional signalling path between the **IP BS Manager** and the **Translation / Mapping function** (4). + - The **Translation / Mapping function** (4) sends *Authorized IP QoS parameters* to the **Access-Specific BS Manager** (5) and receives *Access-Specific QoS parameters* from it. + - The **Access-Specific BS Manager** (5) sends *Access-specific QoS parameters* to the **Access-Specific BS Manager** in the UE and receives *Authorized Access-specific QoS parameters* from it. +- AF:** Contains **1) SDI Mapping function**. It receives *AF session signalling, possibly with SDI* from the UE and sends *Service information* to the **PCRF** via an **Rx** interface. +- PCRF:** Contains **2) Policy Engine**. It receives *Service information* from the **AF** and exchanges *IP QoS parameters* and *Gx/Gxx* / *Authorized IP QoS parameters* with the **GW**. + +**LEGEND:** A dashed box with a double-headed arrow indicates a **Signalling path**. + +Diagram of QoS mapping for UE initiated IP CAN bearers showing interactions between UE, GW, AF, and PCRF. + +Figure 6.1.1.1: QoS mapping for UE initiated IP CAN bearers + +### 6.1.2 Network-Initiated IP-CAN bearers + +When the IP-CAN session supports Network-Initiated bearers, the network sets up IP CAN bearer(s) with a suitable QoS. If the type of IP CAN supports such an indication, the network indicates to the terminal the QoS characteristics of those IP-CAN bearer(s). Therefore the flow of QoS related information will be unidirectional as indicated in the figure 6.1.2.1. + +![Figure 6.1.2.1: QoS mapping for network initiated IP CAN bearers. The diagram shows the flow of QoS parameters from the AF through the PCRF and PCEF/BBERF to the UE. The AF contains an SDI Mapping function (1) and a Policy Engine (2). The PCRF contains the Policy Engine. The PCEF/BBERF contains an IP BS Manager, a Translation/Mapping function (3), and an Access-Specific BS Manager. The UE contains an Application, an IP BS Manager, a Translation/Mapping function, and an Access-Specific BS Manager. Arrows indicate the flow of 'Authorized IP QoS parameters' and 'Authorized Access-Specific QoS parameters'. A legend indicates that dashed boxes represent components 'Only for some IP CAN Types and terminals'.](4792a2ccd62226861fadc22117edb7b1_img.jpg) + +The diagram illustrates the QoS mapping process for network-initiated IP CAN bearers across three main entities: UE, GW, and AF. + +- UE (User Equipment):** Contains an **Application**, a dashed **IP BS Manager**, a dashed **Translation / Mapping function**, and a dashed **Access-Specific BS Manager**. The Application sends *AF session signalling, possibly with SDI* to the AF. The IP BS Manager receives *Authorized IP QoS parameters* from the Translation / Mapping function. The Translation / Mapping function receives *Authorized Access-Specific QoS parameters* from the Access-Specific BS Manager. The Access-Specific BS Manager receives *Authorized Access-specific QoS parameters* from the GW. +- GW (Gateway):** Contains a **PCEF/BBERF** block. Inside PCEF/BBERF, there is an **IP BS Manager**, a **Translation / Mapping function (3)**, and an **Access-Specific BS Manager**. The IP BS Manager receives *Service information* from the PCRF and sends *Authorized IP QoS parameters* to the Translation / Mapping function (3). The Translation / Mapping function (3) sends *Authorized IP QoS parameters* to the IP BS Manager and *Authorized Access-Specific QoS parameters* to the Access-Specific BS Manager. The Access-Specific BS Manager sends *Authorized Access-specific QoS parameters* to the UE. +- AF (Application Function):** Contains **1) SDI Mapping function** and **2) Policy Engine**. The SDI Mapping function sends *Service information* over the **Rx** interface to the PCRF. +- PCRF (PDN Gateway Control Function):** Contains the **2) Policy Engine**. It receives *Service information* from the AF and sends *Authorized IP QoS parameters* over the **Gx/Gxx** interface to the PCEF/BBERF. + +**LEGEND** + +- Signalling path:** Represented by a solid double-headed arrow. +- Only for some IP CAN Types and terminals:** Represented by a dashed box. + +Figure 6.1.2.1: QoS mapping for network initiated IP CAN bearers. The diagram shows the flow of QoS parameters from the AF through the PCRF and PCEF/BBERF to the UE. The AF contains an SDI Mapping function (1) and a Policy Engine (2). The PCRF contains the Policy Engine. The PCEF/BBERF contains an IP BS Manager, a Translation/Mapping function (3), and an Access-Specific BS Manager. The UE contains an Application, an IP BS Manager, a Translation/Mapping function, and an Access-Specific BS Manager. Arrows indicate the flow of 'Authorized IP QoS parameters' and 'Authorized Access-Specific QoS parameters'. A legend indicates that dashed boxes represent components 'Only for some IP CAN Types and terminals'. + +**Figure 6.1.2.1: QoS mapping for network initiated IP CAN bearers** + +1. The AF can map from SDI within the AF session signalling to service information passed to the PCRF over the Rx interface (see subclause 6.2 if SDP is used as SDI). +2. The PCRF shall map from the service information received over the Rx interface to the Authorized IP QoS parameters that shall be passed to the PCEF/BBERF via the Gx/Gxx interface. The mapping is performed for each IP flow. Upon a request from the PCEF/BBERF, the PCRF combines per direction the individual Authorized IP QoS parameters per flow (see subclause 6.3). +3. The PCEF/BBERF shall map from the Authorized IP QoS parameters received from PCRF to the access specific QoS parameters. For GPRS, the GGSN shall map to the UMTS QoS parameters (see clause 6.4.1.1). + +## 6.2 QoS parameter mapping Functions at AF + +The mapping described in this clause is mandatory for the P-CSCF and should also be applied by other AFs, if the SDI is SDP. + +When a session is initiated or modified the P-CSCF shall use the mapping rules in table 6.2.1 for each SDP media component to derive a Media-Component-Description AVP from the SDP Parameters. The mapping shall not apply to media components where the SDP payload is proposing to use a circuit-switched bearer (i.e. "c=" line set to "PSTN" and an "m=" line set to "PSTN", refer to 3GPP TS 24.292 [24]). Circuit-switched bearer related media shall not be included in the service information sent to the PCRF. + +**Table 6.2.1: Rules for derivation of service information within +Media-Component-Description AVP from SDP media component** + +| service information per Media-Component-Description AVP (see notes 1 and 7) | Derivation from SDP Parameters
(see Note 2) | +|------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Media-Component-Number | ordinal number of the position of the "m=" line in the SDP | +| AF-Application-Identifier | The AF-Application-Identifier AVP may be supplied or omitted, depending on the application.
For IMS, if the AF-Application-Identifier AVP is supplied, its value should not demand application specific bandwidth or QoS class handling unless the IMS application is capable of handling a QoS downgrading. | +| Media-Type | The Media Type AVP shall be included with the same value as supplied for the media type in the "m=" line. | +| Flow-Status | 
 IF port in m-line = 0 THEN   Flow-Status:= REMOVED; ELSE   IF Transport in m-line is "TCP" or "TCP/MSRP" or "UDP/DTLS/SCTP" THEN (NOTE 9)     Flow-Status := ENABLED;   ELSE /* UDP or RTP/AVP transport     IF a=rtcp-mux is negotiated THEN       Flow-Status :=ENABLED; (NOTE 12 and 13)     ELSE       IF a=recvonly THEN         IF <SDP direction> = UE originated (NOTE 8) THEN           Flow-Status := ENABLED_DOWNLINK; (NOTE 4)         ELSE /* UE terminated (NOTE 8) */           Flow-Status := ENABLED_UPLINK; (NOTE 4)         ENDIF;       ELSE         IF a=sendonly THEN           IF <SDP direction> = UE originated (NOTE 8) THEN             Flow-Status := ENABLED_UPLINK; (NOTE 4)           ELSE /* UE terminated (NOTE 8) */             Flow-Status := ENABLED_DOWNLINK; (NOTE 4)           ENDIF;         ELSE           IF a=inactive THEN             Flow-Status :=DISABLED;           ELSE /* a=sendrecv or no direction attribute */             Flow-Status := ENABLED (NOTE 4)           ENDIF;         ENDIF;       ENDIF;     ENDIF;   ENDIF; ENDIF; (NOTE 5)
| + +| service information per
Media-Component-
Description AVP
(see notes 1 and 7) | Derivation from SDP Parameters
(see Note 2) | +|---------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Max-Requested-Bandwidth-UL | 
 IF <SDP direction> = UE terminated (NOTE 8) THEN   IF Transport in m-line is "TCP" or "TCP/MSRP" or "UDP/DTLS/SCTP" THEN     (NOTE 9)     IF a=recvonly or a=sendrecv or no direction attribute THEN       IF b=AS:<bandwidth> is present and         ( b=TIAS:<Tibandwidth> is not           present or is present but not supported ) THEN         Max-Requested-Bandwidth-UL:= <bandwidth> * 1000; /* Unit bit/s       ELSE         IF b=TIAS:<Tibandwidth> is present and supported THEN           Max-Requested-Bandwidth-UL:= <Transport-dependent bandwidth>           (NOTE 11) /* Unit bit/s         ELSE           Max-Requested-Bandwidth-UL:= <Operator specific setting>;         ENDIF;       ENDIF;     ELSE       Max-Requested-Bandwidth-UL:= <Operator specific setting>,       (NOTE 10)     ENDIF;   ELSE /* UDP or RTP/AVP transport     IF b=AS:<bandwidth> is present and       ( b=TIAS:<Tibandwidth> is not         present or is present but not supported ) THEN       IF a=rtcp-mux is negotiated (NOTE 13) THEN         IF b=RR:<rrbandwidth> is present           OR b=RS:<rsbandwidth> is present THEN           Max-Requested-Bandwidth-UL:= <bandwidth> * 1000 +           <rrbandwidth> + <rsbandwidth>; (NOTE 3; NOTE 6)         ELSE           Max-Requested-Bandwidth-UL:= <bandwidth> * 1050;           /* Unit is bit/s         ENDIF       ELSE         Max-Requested-Bandwidth-UL:= <bandwidth> * 1000;         /* Unit is bit/s       ENDIF;     ELSE       IF b=TIAS:<Tibandwidth> is present and supported THEN         IF a=rtcp-mux is negotiated (NOTE 13) THEN           IF b=RR:<rrbandwidth> is present             OR b=RS:<rsbandwidth> is present THEN             Max-Requested-Bandwidth-UL:=             <Transport-dependent bandwidth> (NOTE 11) +             <rrbandwidth> + <rsbandwidth>; (NOTE 3; NOTE 6)           ELSE             Max-Requested-Bandwidth-UL:=             <Transport-dependent bandwidth>             * 1.05 (NOTE 11) /* Unit bit/s           ENDIF         ELSE           Max-Requested-Bandwidth-UL:= <Transport-dependent bandwidth>           (NOTE 11) /* Unit bit/s         ENDIF;       ELSE         Max-Requested-Bandwidth-UL:= <Operator specific setting>,         or AVP not supplied;       ENDIF;     ENDIF;   ENDIF ELSE   Consider SDP in opposite direction ENDIF
| + +| service information per
Media-Component-
Description AVP
(see notes 1 and 7) | Derivation from SDP Parameters
(see Note 2) | +|---------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Max-Requested-Bandwidth-DL
(NOTE 17) | 
 IF <SDP direction> = UE originated (NOTE 8) THEN   IF Transport in m-line is "TCP" or "TCP/MSRP" or "UDP/DTLS/SCTP" THEN     (NOTE 9)     IF a=recvonly or a=sendrecv or no direction attribute THEN       IF b=AS:<bandwidth> is present and         ( b=TIAS:<Tibandwidth> is not present or           is present but not supported ) THEN         Max-Requested-Bandwidth-DL:= <bandwidth> * 1000; /* Unit bit/s       ELSE         IF b=TIAS:<Tibandwidth> is present and supported THEN           Max-Requested-Bandwidth-DL:= <Transport-dependant bandwidth>           /* Unit bit/s (see NOTE 11)         OR Operator specific setting       ELSE         Max-Requested-Bandwidth-DL:= <Operator specific setting>;       ENDIF;     ELSE       Max-Requested-Bandwidth-DL:= <Operator specific setting>,       (NOTE 10)     ENDIF;   ELSE /* UDP or RTP/AVP transport     IF b=AS:<bandwidth> is present and b=TIAS:<Tibandwidth> is not       present THEN       IF a=rtcp-mux is negotiated(NOTE 13) THEN         IF b=RR:<rrbandwidth> is present           OR b=RS:<rsbandwidth> is present THEN           Max-Requested-Bandwidth-DL:= <bandwidth> * 1000 +           <rrbandwidth> + <rsbandwidth>; (NOTE 3; NOTE 6)         ELSE           Max-Requested-Bandwidth-DL:= <bandwidth> * 1050;           /* Unit is bit/s         ENDIF       ELSE         Max-Requested-Bandwidth-DL:= <bandwidth> * 1000         ;/* Unit is bit/s       ENDIF;     ELSE       IF b=TIAS:<Tibandwidth> is present THEN         IF a=rtcp-mux is negotiated (NOTE 13) THEN           IF b=RR:<rrbandwidth> is present             OR b=RS:<rsbandwidth> is present THEN             Max-Requested-Bandwidth-DL:=             <Transport-dependent bandwidth> (NOTE 11) +             <rrbandwidth> + <rsbandwidth>; (NOTE 3; NOTE 6)           ELSE             Max-Requested-Bandwidth-DL:=             <Transport-dependent bandwidth>             * 1.05 (NOTE 11) /* Unit bit/s           ENDIF         ELSE           Max-Requested-Bandwidth-DL:= <Transport-dependent bandwidth>           (NOTE 11) /* Unit bit/s         ENDIF;       ELSE         Max-Requested-Bandwidth-DL:= <Operator specific setting>,         or AVP not supplied;       ENDIF;     ENDIF;   ENDIF   ELSE     Consider SDP in opposite direction   ENDIF
| +| Max-Supported-Bandwidth-UL
(NOTE 18) | 
 IF a=bw-info is present and includes MaxSupBw: <bandwidth> and direction: recv (UE terminated) or send (UE originated) or sendrecv (NOTE 14) THEN   Max-Supported-Bandwidth-UL:= [supplied <bandwidth>] * 1000 /Unit bit/s/   (NOTE 16) ELSE /* a=bw-info is not present or is present but MaxSupBw is not   included or direction is the opposite   AVP not supplied ENDIF; (NOTE 15)
| + +| service information per
Media-Component-
Description AVP
(see notes 1 and 7) | Derivation from SDP Parameters
(see Note 2) | +|---------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Max-Supported-Bandwidth-DL
(NOTE 18) | IF a=bw-info is present and includes MaxSupBw : and direction:
send (UE terminated) or recv (UE originated) or sendrecv (NOTE 14) THEN
Max-Supported-Bandwidth-DL:= [supplied ] * 1000 /Unit bit/s/

(NOTE 16)
ELSE /* a=bw-info is not present or is present but MaxSupBw is not
included or direction is the opposite
AVP not supplied
ENDIF;
(NOTE 15) | +| Min-Desired-Bandwidth-UL
(NOTE 19) | IF a=bw-info is present and includes MinDesBw : and direction:
recv (UE terminated) or send (UE originated) or sendrecv (NOTE 14) THEN
Min-Desired-Bandwidth-UL:= supplied * 1000 /Unit bit/s/

(NOTE 16)
ELSE /* a=bw-info is not present or is present but MinDesBw is not
included or direction is the opposite
AVP not supplied
ENDIF; | +| Min-Desired-Bandwidth-DL
(NOTE 19) | IF a=bw-info is present and includes MinDesBw : and direction:
send (UE terminated) or recv (UE originated) or sendrecv (NOTE 14) THEN
Min-Desired-Bandwidth-DL:= [supplied ] * 1000 /Unit bit/s/

(NOTE 16)
ELSE /* a=bw-info is not present or is present but MinDesBw is not
included or direction is the opposite
AVP not supplied
ENDIF; | +| RR-Bandwidth | IF b=RR: is present THEN
RR-Bandwidth:= ;
ELSE
AVP not supplied
ENDIF;
(NOTE 3; NOTE 6) | +| RS-Bandwidth | IF b=RS: is present THEN
RS-Bandwidth:= ;
ELSE
AVP not supplied
ENDIF;
(NOTE 3, NOTE 6) | + +| service information per
Media-Component-
Description AVP
(see notes 1 and 7) | Derivation from SDP Parameters
(see Note 2) | +|---------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Media-Sub-Component | Supply one AVP for bidirectional combination of two corresponding IP flows, if available, and for each single IP flow without a corresponding IP flow in opposite direction.
If a media component comprises separate IP flows for RTP and RTCP, they are described in two separate Media-Sub-Component AVPs. However, if a=rtcp-mux is negotiated, RTP and RTCP use the same IP flow and shall be described in a single Media-Sub-Component AVP.
The encoding of the AVP is described in Table 6.2.2 | +| Reservation-Priority | The AF may supply or omit this AVP. | +| Codec-Data | Codec Data AVP(s) are provisioned as specified in clause 5.3.16 of 3GPP TS 29.214 [10], including the codec-related information detailed in clause 5.3.7 of 3GPP TS 29.214 [10]. | +| Max-PLR-DL | 
 IF a= PLR adapt line is NOT present in both SDP OFFER and ANSWER THEN   /* As UE don't support CHEM feature, AF should not use packet loss rates      in either the uplink or downlink direction */   Max-PLR-DL AVP not supplied ELSE   IF P-CSCF serving the OFFERER THEN     FOR each RTP payload type of the same media line       IF MAXimum-e2e-PLR line is present in the SDP OFFER THEN         IF maxUL-PLR is present in the SDP ANSWER           Max-PLR-DL = value of maxe2e-PLR in the SDP OFFER - maxUL-PLR                            in the SDP ANSWER         ELSE /* maxUL-PLR is not present in the SDP ANSWER */           Max-PLR-DL = the default value is ½ maxe2e-PLR value present                            in the SDP OFFER         ELSE /* MAXimum-e2e-PLR line is not present in the SDP OFFER */           IF maxUL-PLR is present in the SDP ANSWER THEN             Max-PLR-DL = (the default value is end-to-end Maximum                              End-to-End Packet Loss Rate for the decoder of                              the RTP payload type as recommended in 3GPP                              TS 26.114 [29] clause X.1.2 for application                              layer redundancy or X.1.1 for partial redundancy)                              - maxUL-PLR in the SDP ANSWER           ELSE /* maxUL-PLR is not present in the SDP ANSWER */             Max-PLR-DL = the default value is ½ end-to-end Maximum End-to-End                              Packet Loss Rate for the decoder of the RTP payload                              type as recommended in 3GPP TS 26.114 [29]                              clause X.1.2 for application layer redundancy                              or X.1.1 for partial redundancy           ENDIF;         ENDIF;       END FOR LOOP of each RTP payload type of the same media       Max-PLR-DL = maximum value of Max-PLR-DL among all the RTP payload                    types     ELSE /* For P-CSCF serving the ANSWERER */       FOR each RTP payload type of the same media line         IF MAXimum-e2e-PLR line is present in the SDP ANSWER THEN           IF maxDL-PLR is present in the SDP ANSWER             Max-PLR-DL = value of maxDL-PLR in the SDP ANSWER           ELSE /* maxDL-PLR is not present in the SDP ANSWER */             Max-PLR-DL = the default value is ½ maxe2e-PLR value present                              in the SDP ANSWER           ELSE /* MAXimum-e2e-PLR line is not present in the SDP ANSWER */             Max-PLR-DL = the default value is ½ end-to-end Maximum End-to-End                              Packet Loss Rate for the decoder of the RTP payload                              type as recommended in 3GPP TS 26.114 [29]                              clause X.1.2 for application layer redundancy                              or X.1.1 for partial redundancy           ENDIF;         END FOR LOOP of each RTP payload type of the same media         Max-PLR-DL = maximum value of Max-PLR-DL among all the RTP payload                    types       ENDIF;     ENDIF;   ENDIF; ENDIF;
| + +| service information per
Media-Component-
Description AVP
(see notes 1 and 7) | Derivation from SDP Parameters
(see Note 2) | +|---------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Max-PLR-UL | 
 IF a= PLR_adapt line is NOT present in both SDP OFFER and ANSWER THEN   /* As UE don't support CHEM feature, AF should not use packet loss rates      in either the uplink or downlink direction */   Max-PLR-UL AVP not supplied ELSE   IF P-CSCF serving the OFFERER THEN     FOR each RTP payload type of the same media line       IF MAXimum-e2e-PLR line is present in the SDP ANSWER THEN         IF maxDL-PLR is present in the SDP ANSWER           Max-PLR-UL = value of maxe2e-PLR in the SDP ANSWER - maxDL-PLR           in the SDP ANSWER         ELSE /* maxDL-PLR is not present in the SDP ANSWER */           Max-PLR-UL = the default value is ½ maxe2e-PLR value present           in the SDP ANSWER         ELSE /* MAXimum-e2e-PLR line is not present in the SDP ANSWER */           Max-PLR-UL = the default value is ½ end-to-end Maximum End-to-End           Packet Loss Rate for the decoder of the RTP payload           type as recommended in 3GPP TS 26.114 [29]           clause X.1.2 for Application layer redundancy           or X.1.1 for partial redundancy         ENDIF;       END FOR LOOP of each RTP payload type of the same media       Max-PLR-UL = maximum value of Max-PLR-UL among all the RTP payload       types     ELSE /* For P-CSCF serving the ANSWERER */       FOR each RTP payload type of the same media line         IF MAXimum-e2e-PLR line is present in the SDP OFFER THEN           IF maxUL-PLR is present in the SDP ANSWER             Max-PLR-UL = value of maxUL-PLR in the SDP ANSWER           ELSE /* maxUL-PLR is not present in the SDP ANSWER */             Max-PLR-UL = the default value is ½ maxe2e-PLR value present             in the SDP OFFER           ELSE /* MAXimum-e2e-PLR line is not present in the SDP OFFER */             Max-PLR-UL = the default value is ½ end-to-end Maximum End-to-End             Packet Loss Rate for the decoder of the RTP payload             type as recommended in 3GPP TS 26.114 [29]             clause X.1.2 for Application layer redundancy             or X.1.1 for partial redundancy           ENDIF;         END FOR LOOP of each RTP payload type of the same media         Max-PLR-UL = maximum value of Max-PLR-UL among all the RTP payload         types       ENDIF;     ENDIF;   ENDIF; ENDIF;
| +| Desired-Max-Latency | 
 IF <SDP direction> = UE originated (NOTE 8) THEN   IF a=3gpp-qos-hint is present and includes a qos-hint-property that   indicates "latency"     IF qos-hint-split-value for "local" is not present       Desired-Max-Latency = <qos-hint-end-to-end-value>*0.5     ELSE /* qos-hint-split-value for "local" is present       Desired-Max-Latency = <qos-hint-split-value>     ENDIF   ELSE     AVP not supplied   ENDIF ELSE /* <SDP direction> = UE terminated (NOTE 8)/   IF a=3gpp-qos-hint is present and includes a qos-hint-property that   indicates "latency"     IF qos-hint-split-value for "local" is not present       Desired-Max-Latency = <qos-hint-end-to-end-value>*0.5     ELSE /* qos-hint-split-value for "local" is present/       Desired-Max-Latency = <qos-hint-end-to-end-value> - <qos-hint-split- value>     ENDIF   ELSE     AVP not supplied   ENDIF ENDIF
| + +| service information per
Media-Component-
Description AVP
(see notes 1 and 7) | Derivation from SDP Parameters
(see Note 2) | +|---------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Desired-Max-Loss | 
 IF <SDP direction> = UE originated (NOTE 8) THEN   IF a=3gpp-qos-hint is present and includes a qos-hint-property that indicates "loss"     IF qos-hint-split-value for "local" is not present       Desired-Max-Loss = <qos-hint-end-to-end-value>*0.5     ELSE /* qos-hint-split-value for "local" is present/       Desired-Max-Loss = <qos-hint-split-value>     ENDIF   ELSE     AVP not supplied   ENDIF ELSE /* <SDP direction> = UE terminated (NOTE 8)/   IF a=3gpp-qos-hint is present and includes a qos-hint-property that indicates "loss"     IF qos-hint-split-value for "local" is not present       Desired-Max-Loss = < qos-hint-end-to-end-value>*0.5     ELSE /* qos-hint-split-value for "local" is present/       Desired-Max-Loss = <qos-hint-end-to-end-value> - <qos-hint-split- value>     ENDIF   ELSE     AVP not supplied   ENDIF ENDIF
| + +| service information per
Media-Component-
Description AVP
(see notes 1 and 7) | Derivation from SDP Parameters
(see Note 2) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------| +| NOTE 1: The encoding of the service information is defined in 3GPP TS 29.214 [10].
NOTE 2: The SDP parameters are described in IETF RFC 2327 [11].
NOTE 3: The "b=RS:" and "b=RR:" SDP bandwidth modifiers are defined in IETF RFC 3556 [13].
NOTE 4: As an operator policy to disable forward and/or backward early media, for media with UDP as transport protocol only the Flow-Status AVP may be downgraded by using the gate control procedures defined in the annex A of 3GPP TS 29.214 [10] before a SIP confirmed dialogue is established, i.e. until a 200 (OK) response to an INVITE request is received.
NOTE 5: If the SDP answer is available when the session information is derived, the direction attributes and port number from the SDP answer shall be used to derive the flow status. However, to enable interoperability with SIP clients that do not understand the inactive SDP attribute, if "a=inactive" was supplied in the SDP offer, this shall be used to derive the flow status. If the SDP answer is not available when the session information is derived, the direction attributes from the SDP offer shall be used.
NOTE 6: Information from the SDP answer is applicable, if available.
NOTE 7: The AVPs may be omitted if they have been supplied in previous service information and have not changed, as detailed in 3GPP TS 29.214 [10].
NOTE 8: "Uplink SDP" indicates that the SDP was received from the UE and sent to the network. This is equivalent to = UE originated.
"Downlink SDP" indicates that the SDP was received from the network and sent to the UE. This is equivalent to = UE terminated.
NOTE 9: Support for TCP at a P-CSCF acting as AF is only required if services with TCP transport are used in the corresponding IMS system.
As an operator policy to disable forward and/or backward early media, for media with TCP as transport protocol, the Max-Requested-Bandwidth-UL/DL values may be downgraded before a SIP confirmed dialogue is established, i.e. until a 200 (OK) response to an INVITE request is received. Only a small bandwidth in both directions is required in this case in order for TCP control packets to flow.
NOTE 10: TCP uses IP flows in the directionality opposite to the transferred media for feedback. To enable these flows, a small bandwidth in this direction is required.
NOTE 11: TIAS is defined in IETF RFC 3890 [23]. IETF RFC 3890 clause 6.4 provides procedures for converting TIAS to transport-dependant values. This procedure relies on the presence of maxprate (also defined in IETF RFC 3890).
NOTE 12: Multiplexed RTP/RTCP flows need to have Flow-Status set to "ENABLED" in order to always permit the RTCP traffic.
NOTE 13: RTP/RTCP multiplexing is defined in IETF RFC 5761 [39].
NOTE 14: This AVP is derived from the SDP answer information and is omitted if E2EQOSMTSI feature is not supported.
NOTE 15: When both "b =" line and "a=bw-info" including MaxSupBw are present when sending the SDP, it is expected that the values are aligned.
NOTE 16: When the supplied bandwidth does not correspond to the bandwidth applicable to the IP version used by the UE, the AF shall re-compute it considering the IP version used by the UE as defined in 3GPP TS 26.114 [29].
NOTE 17: When the Extended-Max-Requested-BW-NR feature is supported and if the bandwidth values are higher than 2^32-1 bps, Extended-Max-Requested-BW-UL/DL shall be derived instead of Max-Requested-Bandwidth-UL/DL. The same derivation procedure shall apply, with the exception that the units for the derived bandwidth shall be kbit per second instead of bit per second.
NOTE 18: When the Extended-BW-E2EQOSMTSI-NR feature is supported and if the bandwidth values are higher than 2^32-1 bps, Extended-Max-Supported-BW-UL/DL shall be derived instead of Max-Supported-Bandwidth-UL/DL. The same derivation procedure shall apply, with the exception that the units for the derived bandwidth shall be kbit per second instead of bit per second.
NOTE 19: When the Extended-BW-E2EQOSMTSI-NR feature is supported and if the bandwidth values are higher than 2^32-1 bps, Extended-Min-Desired-BW-UL/DL shall be derived instead of Min-Desired-Bandwidth-UL/DL. The same derivation procedure shall apply, with the exception that the units for the derived bandwidth shall be kbit per second instead of bit per second. | | + +###### **Table 6.2.2: Rules for derivation of Media-Sub-Component AVP from SDP media component** + +| service information per
Media-Sub-Component
AVP
(see notes 1 and 5) | Derivation from SDP Parameters
(see Note 2) | +|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Flow-Number |

The AF shall assign a number to the media-subcomponent AVP that is unique within the surrounding media component AVP and for the entire lifetime of the AF session. The AF shall select the ordinal number of the IP flow(s) within the "m=" line assigned in the order of increasing downlink destination port numbers, if downlink destination port numbers are available. For uplink or inactive unicast media IP flows, a downlink destination port number is nevertheless available, if SDP offer-answer according to IETF RFC 3264 is used.

The AF shall select the ordinal number of the IP flow(s) within the "m=" line assigned in the order of increasing uplink destination port numbers, if no downlink destination port numbers are available.

| +| Flow-Status | AVP not supplied | +| Max-Requested-Bandwidth-UL | AVP not supplied | +| Max-Requested-Bandwidth-DL | AVP not supplied | + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Flow-Description |

For uplink and downlink direction, a Flow-Description AVP shall be provided unless no IP Flows in this direction are described within the media component.

If UDP is used as transport protocol, the SDP direction attribute (NOTE 4) indicates the direction of the media IP flows within the media component as follows:

 IF a=recvonly THEN (NOTE 3)   IF <SDP direction> = UE originated (NOTE 7) THEN     Provide only downlink Flow-Description AVP   ELSE /* UE terminated (NOTE 7) */     Provide only uplink Flow-Description AVP   ENDIF; ELSE   IF a=sendonly THEN (NOTE 3)     IF <SDP direction> = UE originated (NOTE 7) THEN       Provide only uplink Flow-Description AVP     ELSE /* UE terminated (NOTE 7) */       Provide only downlink Flow-Description AVP     ENDIF;   ELSE /* a=sendrecv or a=inactive or no direction attribute */     Provide uplink and downlink Flow-Description AVPs   ENDIF; ENDIF;

However, for RTCP and RTP/RTCP multiplexed IP flows uplink and downlink Flow-Description AVPs shall be provided irrespective of the SDP direction attribute.

If TCP is used as transport protocol (NOTE 8), IP flows in uplink and downlink direction are described in SDP irrespective of the SDP direction attribute, as TCP uses an IP flow for feedback even if contents are transferred only in the opposite direction. Thus, both uplink and downlink Flow-Description AVPs shall be provided.

The uplink destination address shall be copied from the "c=" line of downlink SDP. (NOTE 6) (NOTE 7)

The uplink destination port shall be derived from the "m=" line of downlink SDP. (NOTE 6) (NOTE 7) However, for TCP transport the uplink destination port shall be wildcarded, if the local UE is the passive endpoint (NOTE 9)

The downlink destination address shall be copied from the "c=" line of uplink SDP. (NOTE 6) However, a P-CSCF acting as AF and applying NAT traversal procedures in Annex C shall derive the downlink destination address using those procedures.

The downlink destination port shall be derived from the "m=" line of uplink SDP. (NOTE 6) (NOTE 7) However, for TCP transport the downlink destination port shall be wildcarded, if the local UE is the active endpoint (NOTE 9). A P-CSCF acting as AF and applying NAT traversal procedures in Annex C shall derive the downlink destination port using those procedures.

For IPv6, uplink and downlink source addresses shall either be derived from the prefix of the destination address or be wildcarded by setting to "any", as specified in 3GPP TS 29.214 [10]. However, a P-CSCF acting as AF and applying NAT traversal procedures in Annex C shall derive the uplink source address using those procedures.

If IPv4 is being utilized, the uplink source address shall either be set to the address contained in the "c=" line of the uplink SDP or be wildcarded, and the downlink source address shall either be set to the address contained in the "c=" line of the downlink SDP or be wildcarded. However, for TCP transport, if the local UE is the passive endpoint (NOTE 9), the uplink source address shall not be wildcarded. If the local UE is the active endpoint (NOTE 9), the downlink source address shall not be wildcarded. A P-CSCF acting as AF and applying NAT traversal procedures in Annex C shall derive the uplink source address using those procedures.

Source ports shall not be supplied. However, for TCP transport, if the local UE is the passive end point (NOTE 9), the uplink source port shall be derived from the "m=" line of the uplink SDP. If the local UE is the active end point (NOTE 9), the downlink source port shall be derived from the "m=" line of the downlink SDP. A P-CSCF acting as AF and applying NAT traversal procedures in Annex C shall derive the downlink source ports using those procedures.

Proto shall be derived from the transport of the "m=" line. For "UDP/DTLS/SCTP" as defined in IETF RFC 8864 [69] or "RTP/AVP", proto is 17(UDP). For "TCP", as defined in IETF RFC 4145 [16], or "TCP/MSRP", as defined in IETF RFC 4975 [17], proto is 6(TCP).

| +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| service information per
Media-Sub-Component
AVP
(see notes 1 and 5) | Derivation from SDP Parameters
(see Note 2) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Flow-Usage | The Flow-Usage AVP shall be supplied with value "RTCP" if the IP flow(s) described in the Media-Sub-Component AVP are used to transport RTCP only. Otherwise the Flow-Usage AVP shall not be supplied. IETF RFC 2327 [11] specifies how RTCP flows are described within SDP. If the IP flows(s) are used to transport signalling the value should be "AF-SIGNALLING". | +| NOTE 1: The encoding of the service information is defined in 3GPP TS 29.214 [10].
NOTE 2: The SDP parameters are described in IETF RFC 2327 [11].
NOTE 3: If the SDP direction attribute for the media component negotiated in a previous offer-answer exchange was sendrecv, or if no direction attribute was provided, and the new SDP direction attribute sendonly or recvonly is negotiated in a subsequent SDP offer-answer exchange, uplink and downlink Flow-Description AVPs shall be supplied.
NOTE 4: If the SDP answer is available when the session information is derived, the direction attributes from the SDP answer shall be used to derive the flow description. However, to enable interoperability with SIP clients that do not understand the inactive SDP attribute, if "a=inactive" was supplied in the SDP offer, this shall be used. If the SDP answer is not available when the session information is derived, the direction attributes from the SDP offer shall be used.
NOTE 5: The AVPs may be omitted if they have been supplied in previous service information and have not changed, as detailed in 3GPP TS 29.214 [10].
NOTE 6: If the session information is derived from an SDP offer, the required SDP may not yet be available. The corresponding Flow Description AVP shall nevertheless be included and the unavailable fields (possibly all) shall be wildcarded.
NOTE 7: "Uplink SDP" indicates that the SDP was received from the UE and sent to the network. This is equivalent to = UE originated.
"Downlink SDP" indicates that the SDP was received from the network and sent to the UE. This is equivalent to = UE terminated.
NOTE 8: Support for TCP at a P-CSCF acting as AF is only required if services with TCP transport are used in the corresponding IMS system.
NOTE 9: For TCP transport, the passive endpoints is derived from the SDP "a=setup" attribute according to the rules in IETF RFC 4145 [16], or, if that attribute is not present, from the rules in IETF RFC 4975 [17]. | | + +## 6.3 QoS parameter mapping Functions at PCRF + +The QoS authorization process consists of the derivation of the parameters Authorized QoS Class Identifier (QCI), Allocation and Retention Priority (ARP), and Authorized Maximum/Guaranteed Data Rate UL/DL. + +When a session is initiated or modified the PCRF shall derive Authorized IP QoS parameters (i.e. QCI, Authorized Maximum/Guaranteed Data Rate DL/UL (if bandwidth values are lower or equal to $2^{32}-1$ bps), Extended Authorized Maximum/Guaranteed Data Rate DL/UL (if bandwidth values are higher than $2^{32}-1$ bps and if the Extended-BW-NR feature is supported), ARP) from the service information. If the selected Bearer Control Mode (BCM) is UE-only this process shall be performed according to the mapping rules in table 6.3.1 to avoid undesired misalignments with the UE QoS parameters mapping. + +In the case of forking, the various forked responses may have different QoS requirements for the IP flows of the same media component. Each Authorized IP QoS Parameter should be set to the highest value requested for the IP flow(s) of that media component by any of the active forked responses. + +**Table 6.3.1: Rules for derivation of the Maximum Authorized Data Rates, Authorized Guaranteed Data Rates and Maximum Authorized QoS Class per IP flow or bidirectional combination of IP flows in the PCRF** + +| Authorized IP QoS
Parameter | Derivation from service information
(see Note 4) | +|----------------------------------------|-------------------------------------------------------------| +|----------------------------------------|-------------------------------------------------------------| + +### **Maximum Authorized Data Rate DL (Max\_DR\_DL) and UL (Max\_DR\_UL) (NOTE 21)** + +``` + +IF operator special policy exists THEN + + Max_DR_UL:= as defined by operator specific algorithm; + Max_DR_DL:= as defined by operator specific algorithm; + +ELSE + + IF AF-Application-Identifier AVP demands application specific data rate + handling THEN + Max_DR_UL:= as defined by application specific algorithm; + Max_DR_DL:= as defined by application specific algorithm; + + ELSE IF Codec-Data AVP provides Codec information for a codec that is + supported by a specific algorithm (NOTE 19,20) THEN + Max_DR_UL:= as defined by specific algorithm; + Max_DR_DL:= as defined by specific algorithm; + + ELSE + IF not RTCP flow(s) according to Flow-Usage AVP THEN + IF Flow-Status = REMOVED THEN + Max_DR_UL:= 0; + Max_DR_DL:= 0; + ELSE + IF uplink Flow Description AVP is supplied THEN + IF Max-Supported-Bandwidth-UL is present and supported THEN + Max_DR_UL:= Max-Supported-Bandwidth-UL; + ELSE IF Max-Requested-Bandwidth-UL is present THEN + Max_DR_UL:= Max-Requested-Bandwidth-UL; + ELSE + Max_DR_UL:= as set by the operator; + ENDIF; + ELSE + Max_DR_UL:= 0; + ENDIF; + + IF downlink Flow Description AVPs is supplied THEN + IF Max-Supported-Bandwidth-DL is present and supported THEN + Max_DR_DL:= Max-Supported-Bandwidth-DL; + ELSE IF Max-Requested-Bandwidth-DL is present THEN + Max_DR_DL:= Max-Requested-Bandwidth-DL; + ELSE + Max_DR_DL:= as set by the operator; + ENDIF; + ELSE + Max_DR_DL:= 0; + ENDIF; + ENDIF; + + ELSE /* RTCP IP flow(s) */ + IF RS-Bandwidth is present and RR-Bandwidth is present THEN + Max_DR_UL:= (RS-Bandwidth + RR-Bandwidth); + Max_DR_DL:= (RS-Bandwidth + RR-Bandwidth); + ELSE + IF Max-Requested-Bandwidth-UL is present THEN + IF RS-Bandwidth is present and RR-Bandwidth is not present THEN + Max_DR_UL:= MAX[0.05 * Max-Requested-Bandwidth-UL,RS-Bandwidth]; + ENDIF; + + IF RS-Bandwidth is not present and RR-Bandwidth is present THEN + Max_DR_UL:= MAX[0.05 * Max-Requested-Bandwidth-UL,RR-Bandwidth]; + ENDIF; + + IF RS-Bandwidth and RR-Bandwidth are not present THEN + Max_DR_UL:= 0.05 * Max-Requested-Bandwidth-UL; + ENDIF; + } + ELSE + Max_DR_UL:= as set by the operator; + ENDIF; + + IF Max-Requested-Bandwidth-DL is present THEN + IF RS-Bandwidth is present and RR-Bandwidth is not present THEN + Max_DR_DL:= MAX[0.05 * Max-Requested-Bandwidth-DL,RS-Bandwidth]; + ENDIF; + + IF RS-Bandwidth is not present and RR-Bandwidth is present THEN + Max_DR_DL:= MAX[0.05 * Max-Requested-Bandwidth-DL,RR-Bandwidth]; + ENDIF; + } + ENDIF; + ENDIF; + ENDIF; +} + +``` + +| Authorized IP QoS
Parameter | Derivation from service information
(see Note 4) | +|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 
        IF RS-Bandwidth and RR-Bandwidth are not present THEN             Max_DR_DL:= 0.05 * Max-Requested-Bandwidth-DL;         ENDIF;          ELSE             Max_DR_DL:= as set by the operator;         ENDIF;      ENDIF; ENDIF; ENDIF;  ENDIF;  IF SIP-Forking-Indication AVP indicates SEVERAL DIALOGUES THEN     Max_DR_UL = MAX[Max_DR_UL, previous Max_DR_UL]     Max_DR_DL = MAX[Max_DR_DL, previous Max_DR_DL] ENDIF;
| + +| Authorized IP QoS Parameter | Derivation from service information
(see Note 4) | +|--------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Authorized Guaranteed Data Rate DL (Gua_DR_DL) and UL (Gua_DR_UL) (see NOTE 11, 13, 15, 16. 21) | 
 IF operator special policy exists THEN   Gua_DR_UL:= as defined by operator specific algorithm;   Gua_DR_DL:= as defined by operator specific algorithm;  ELSE   IF AF-Application-Identifier AVP demands application specific data rate handling THEN     Gua_DR_UL:= as defined by application specific algorithm;     Gua_DR_DL:= as defined by application specific algorithm;    ELSE IF Codec-Data AVP provides Codec information for a codec that is supported by a specific algorithm (NOTE 5,19,20) THEN     Gua_DR_UL:= as defined by specific algorithm;     Gua_DR_DL:= as defined by specific algorithm;    ELSE     IF uplink Flow-Description AVP is supplied THEN       IF Min-Desired-Bandwidth-UL is present and supported THEN         Gua_DR_UL:= Min-Desired-Bandwidth-UL ;       ELSE IF Min-Requested-Bandwidth-UL is present THEN         Gua_DR_UL:= Min-Requested-Bandwidth-UL ;       ELSE         Gua_DR_UL:= as set by the operator;       ENDIF;     ELSE       Gua_DR_UL:= Max DR UL;     ENDIF;      IF downlink Flow-Description AVP is supplied THEN       IF Min-Desired-Bandwidth-DL is present and supported THEN         Gua_DR_DL:= Min-Desired-Bandwidth-DL       ELSE IF Min-Requested-Bandwidth-DL is present THEN         Gua_DR_DL:= Min-Requested-Bandwidth-DL ;       ELSE         Gua_DR_DL:= as set by the operator;       ENDIF;     ELSE       Gua_DR_DL:= Max DR DL;     ENDIF;   ENDIF; ENDIF;  IF SIP-Forking-Indication AVP indicates SEVERAL DIALOGUES THEN   Gua_DR_UL = MAX[Gua_DR_UL, previous Gua_DR_UL]   Gua_DR_DL = MAX[Gua_DR_DL, previous Gua_DR_DL] ENDIF;
| + +| Authorized IP QoS Parameter | Derivation from service information
(see Note 4) | +|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Authorized QoS Class Identifier [QCI]
(see NOTE 1, 2, 7, 12, 14 and 23) | 
 IF an operator special policy exists THEN   QCI:= as defined by operator specific algorithm;  ELSE IF MPS-Identifier AVP demands MPS specific QoS Class handling THEN   QCI:= as defined by MPS specific algorithm (NOTE 18); ELSE IF GCS-Identifier AVP demands Group Communication specific handling THEN   QCI:= as defined by GCS specific algorithm (NOTE 17); ELSE IF AF-Application-Identifier AVP demands application specific QoS Class handling THEN   QCI:= as defined by application specific algorithm;  ELSE IF Codec-Data AVP provides Codec information for a codec that is supported by a specific algorithm THEN   QCI:= as defined by specific algorithm; (NOTE 5)  ELSE IF FLUS-Identifier AVP demands specific QoS Class handling THEN   QCI:= as defined by specific algorithm; (NOTE 22)  ELSE   /* The following QCI derivation is an example of how to obtain the QCI values in a GPRS network */   IF Media-Type is present THEN     /* for GPRS: streaming */     IF (only uplink Flow Description AVPs are supplied for all IP flows of the AF session, which have media type "audio" or "video" and no flow usage "RTCP", or only downlink Flow Description AVPs are supplied for all IP flows of the AF session, which have media type "audio" or "video" and no flow usage "RTCP") THEN       CASE Media-Type OF         "audio":      MaxClassDerivation := 3 OR 4; (NOTE 9)         "video":      MaxClassDerivation := 4       END;        /* for GPRS: conversational */       ELSE         CASE Media-Type OF           "audio":      MaxClassDerivation:= 1 OR 2; (NOTE 6)           "video":      MaxClassDerivation:= 2         END;        ENDIF;        CASE Media-Type OF         "audio":      QCI := MaxClassDerivation         "video":      QCI := MaxClassDerivation         "application": QCI := 1 OR 2; (NOTE 6)         /*e.g. for GPRS: conversational*/         "data":      QCI := 6 OR 7 OR 8; (NOTE 8)         /*e.g. for GPRS: interactive with prio 1, 2 AND 3 respectively*/         "control":  QCI := 6;         /*e.g. for GPRS: interactive with priority 1*/        /* NOTE: include new media types here */        OTHERWISE:  QCI := 9;       /*e.g. for GPRS: background*/        END;     ENDIF;   ENDIF;    IF SIP-Forking-Indication AVP indicates SEVERAL_DIALOGUES THEN     QCI = MAX[QCI, previous QCI] (NOTE 10)   ENDIF ;
| + +| Authorized IP QoS Parameter | Derivation from service information
(see Note 4) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| NOTE 1: The QCI assigned to a RTCP IP flow is the same as for the corresponding RTP media IP flow.
NOTE 2: When audio or video IP flow(s) are removed from a session, the parameter MaxClassDerivation shall keep the originally assigned value.
NOTE 3: When audio or video IP flow(s) are added to a session, the PCRF shall derive the parameter MaxClassDerivation taking into account the already existing media IP flow(s) within the session.
NOTE 4: The encoding of the service information is defined in 3GPP TS 29.214 [10]. Possible Bandwidth information and Flow-Status information provided within the Media-Sub-Component AVP takes precedence over information within the encapsulating Media-Component-Description AVP as specified in 3GPP TS 29.214 [10]. If AVPs are omitted within a Media-Component-Description AVP or Media-Sub-Component AVP of the service information, the corresponding information from previous service information shall be used, as specified in 3GPP TS 29.214 [10].
NOTE 5: 3GPP TS 26.234 [6], 3GPP TS 26.114 [29], 3GPP2 C.S0046 [18], and 3GPP2 C.S0055 [19] contain examples of QoS parameters for codecs of interest. The support of any codec specific algorithm in the PCRF is optional.
NOTE 6: For GPRS, the final QCI value will depend on the value of SSD (speech/unknown) according to 3GPP TS 23.107 [4] and table A.3 of 3GPP TS 23.203 [2]. If the PCRF is not able to determine the SSD, it should use the QCI value 2 that corresponds to SSD unknown. For UE-init and mixed mode, the PCRF may derive from the requested QoS of an IP CAN bearer which SSD is applicable.
NOTE 7: The numeric value of the QCI are based on 3GPP TS 29.212 [9].
NOTE 8: The QCI value also encodes the traffic handling priority for GPRS. If the PCRF is not able to determine a traffic handling priority, it should choose QCI 8 that corresponds to priority 3. Also, for UE-initiated bearers the PCRF should only use QCI 8 in order to have the same mapping rules in both UE and PCRF.
NOTE 9: For GPRS, the final QCI value will depend on the value of SSD (speech/unknown) according to 3GPP TS 23.107 [4] and table A.3 of 3GPP TS 23.203 [2]. If the PCRF is not able to determine the SSD, it should use the QCI value 4 that corresponds to SSD unknown. For UE-init and mixed mode, the PCRF may derive from the requested QoS of an IP CAN bearer which SSD is applicable.
NOTE 10: The Max function shall use the following precedence order for the QCI values: $2 > 1 > 4 > 3 > 5 > 6 > 7 > 8 > 9$
NOTE 11: Authorized Guaranteed Data Rate DL and UL shall not be derived for QCI values 5, 6, 7, 8 and 9.
NOTE 12: Recommended QCI values for standardised QCI characteristics are shown in table 6.1.7 in 3GPP TS 23.203 [2].
NOTE 13: The PCRF may be configured with operator specific preconditions for setting the Authorized Guaranteed Data Rate lower than the corresponding Maximum Authorized Data Rate.
NOTE 14: In a network where SRVCC is enabled, the QCI=1 shall be used for IMS services in accordance to 3GPP TS 23.216 [27]. Non-IMS services using QCI=1 may suffer service interruption and/or inconsistent service experience if SRVCC is triggered. Triggering SRVCC for WebRTC IMS session will cause service interruption and/or inconsistent service experience when using QCI=1. Operator policy (e.g. use of specific AF application identifier) may be used to avoid using QCI 1 for a voice service, e.g. WebRTC IMS session.
NOTE 15: For certain services (e.g. DASH services according to 3GPP TS 26.247 [30]), the AF may also provide a minimum required bandwidth so that the PCRF can derive an Authorized Guaranteed Data Rate lower than the Maximum Authorized Data Rate.
NOTE 16: For GPRS and EPS, the PCRF shall assign an Authorized Guaranteed Data Rate UL/DL value within the limit supported by the serving network.
NOTE 17: The GCS specific algorithm shall consider various inputs, including the received Reservation-Priority AVP, for deriving the QCI.
NOTE 18: The MPS specific algorithm shall consider various inputs, including the received MPS-Identifier AVP and Reservation-Priority AVP, for deriving the QCI.
NOTE 19: When multiple codecs are supported per media stream (e.g. as part of multi-stream multiparty conferencing media handling are negotiated as described in 3GPP TS 26.114 [29]) the codec specific algorithm shall consider the bandwidth related to each codec when calculating the total bandwidth.
NOTE 20: 3GPP TS 26.114 [29] contains examples of how the Authorized Guaranteed Data Rate and Maximum Authorized Data Rate are assumed to be derived for multi-party multimedia conference media handling support. The support of this behaviour is optional.
NOTE 21: For bandwidth values higher than $2^{32}-1$ bps and if the Extended-BW-NR feature is supported over Gx/Gxx interface, Extended-Max_DR_DL/UL and Extended-Gua_DR_DL/UL shall be derived instead of Max_DR_DL/UL and Gua_DR_DL/UL.
NOTE 22: The "live" uplink streaming algorithm may consider various inputs, including the received FLUS-Identifier AVP, Desired-Max-Latency AVP, Desired-Max-Loss AVP, AF-Application-Identifier AVP and Media-Type AVP for deriving the QCI. When Desired-Max-Latency AVP and/or Desired-Max-Loss AVP are present, non-authority QCI mapping may be done according to table 6.1.7-A in 3GPP TS 23.203 [2].
NOTE 23: The algorithm to support applications with specific QoS hints (e.g. loss and/or latency demands) may consider various inputs, including the received Desired-Max-Latency AVP, Desired-Max-Loss AVP and AF-Application-Identifier AVP for deriving the QCI, as shown in table E.0 in 3GPP TS 26.114 [29]. Non-authority QCI mapping may be done according to table 6.1.7-A in 3GPP TS 23.203 [2]. | | + +The PCRF should per ongoing session store the Authorized IP QoS parameters per for each IP flow or bidirectional combination of IP flows (as described within a Media Subcomponent AVP). + +If the PCRF provides a QoS-Information AVP within a Charging-Rule-Definition AVP it may apply the rules in table 6.3.2 to combine the Authorized QoS per IP flow or bidirectional combination of IP flows (as derived according to table 6.3.1) for all IP flows described by the corresponding PCC rule. + +If the PCRF provides a QoS-Information AVP for an entire IP CAN bearer (for a UE-initiated IP-CAN bearer in the GPRS case) or IP CAN session, it may apply the rules in table 6.3.2 to combine the Authorized QoS per IP flow or bidirectional combination of IP flows (as derived according to table 6.3.1) for all IP flows allowed to be transported within the IP CAN bearer or session. It is recommended that the rules in table 6.3.2 are applied for all IP flows with corresponding AF session. The PCRF may increase the authorized QoS further to take into account the requirements of predefined PCC rules without ongoing AF sessions. + +NOTE 1: QoS-Information AVP provided at IP-CAN session level is not derived based on mapping tables, but based on subscription and operator specific policies. + +NOTE 2: Allocation-Retention-Priority AVP is always calculated at PCC rule level according to table 6.3.2. + +For a UE initiated PDP context within GPRS, the PCRF applies the binding mechanism described in clause 5 to decide which flows are allowed to be transported within the IP CAN bearer. + +**Table 6.3.2: Rules for calculating the Maximum Authorized/Guaranteed Data Rates, QCI and ARP in the PCRF** + +| Authorized IP QoS Parameter | Calculation Rule | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Maximum Authorized Data Rate DL and UL (see NOTE 6) |

Maximum Authorized Data Rate DL/UL is the sum of all Maximum Authorized Data Rate DL/UL for all the IP flows or bidirectional combinations of IP flows (as according to table 6.3.1).

 IF Network = GPRS AND Maximum Authorized Data Rate DL/UL > 256 Mbps THEN   Maximum Authorized Data Rate DL/UL = 256 Mbps /* See 3GPP TS 23.107 [4] */ ENDIF;
| +| Guaranteed Authorized Data Rate DL and UL (see NOTE 3,6) |

Guaranteed Authorized Data Rate DL/UL is the sum of all Guaranteed Authorized Data Rate DL/UL for all the IP flows or bidirectional combinations of IP flows (as according to table 6.3.1).

| +| QCI |

QCI = MAX [needed QoS parameters per IP flow or bidirectional combination of IP flows (as operator's defined criteria) among all the IP flows or bidirectional combinations of IP flows.]

| +| ARP (see NOTE 1) | 
 IF an operator special policy exists THEN   ARP:= as defined by operator specific algorithm;  ELSE IF MPS-Identifier AVP demands MPS specific ARP handling THEN   ARP:= as defined by MPS specific algorithm (NOTE 2); ELSE IF GCS-Identifier AVP demands Group Communication Service specific ARP handling THEN   ARP:= as defined by GCS specific algorithm (NOTE 4); ELSE IF MCPTT-Identifier AVP demands MCPTT specific ARP handling THEN   ARP:= as defined by MCPTT specific algorithm (NOTE 5); ELSE IF MCVideo-Identifier AVP demands MCVideo specific ARP handling THEN   ARP:= as defined by MCVideo specific algorithm (NOTE 7); ELSE IF AF-Application-Identifier AVP demands application specific ARP handling THEN   ARP:= as defined by application specific algorithm; ELSE IF Reservation-Priority AVP demands application specific ARP handling THEN   ARP:= as defined by application specific algorithm; ENDIF;
| +|

NOTE 1: The ARP priority levels 1-8 should only be assigned to resources for services that are authorized to receive prioritized treatment within an operator domain.

NOTE 2: The MPS specific algorithm shall consider various inputs, including the received MPS-Identifier AVP and Reservation-Priority AVP, for deriving the ARP.

NOTE 3: For GPRS and EPS, the PCRF may check that the Guaranteed Authorized Data Rate DL/UL does not exceed the limit supported by the serving network to minimize the risk of rejection of the bearer by the serving network.

NOTE 4: The GCS specific algorithm shall consider various inputs, including the received Reservation-Priority AVP, for deriving the ARP.

NOTE 5: The MCPTT specific algorithm shall consider the value of the MCPTT-Identifier AVP and the value of the Reservation-Priority AVP.

NOTE 6: For bandwidth values higher than 232-1 bps and if the Extended-BW-NR feature is supported, Extended Guaranteed Authorized Data Rate DL/UL and Extended Maximum Data Rate DL/UL shall be used instead of Maximum Authorized Data Rate DL/UL and Guaranteed Authorized Data Rate DL/UL.

NOTE 7: The MCVideo specific algorithm shall consider the value of the MCVideo-Identifier AVP and the value of the Reservation-Priority AVP.

| | + +## 6.4 QoS parameter mapping Functions at PCEF + +### 6.4.1 GPRS + +#### 6.4.1.1 Authorized IP QoS parameters per PDP Context to Authorized UMTS QoS parameters mapping in GGSN + +The Translation/Mapping function in the GGSN shall derive the Authorized UMTS QoS parameters from the Authorized IP QoS parameters received from the PCRF according to the rules in table 6.4.1. + +**Table 6.4.1: Rules for derivation of the Authorized UMTS QoS Parameters per PDP context from the Authorized IP QoS Parameters in GGSN** + +| Authorized UMTS QoS Parameter per PDP context | Derivation from Authorized IP QoS Parameters | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Maximum Authorized Bandwidth DL and UL per PDP context (see NOTE 2) | Maximum Authorized Bandwidth DL/UL per PDP context = Maximum Authorized Data Rate DL/UL | +| Guaranteed Authorized Data Rate DL and UL per PDP context | Guaranteed Authorized Data Rate DL/UL per PDP context = Guaranteed Authorized Data Rate DL/UL | +| Maximum Authorized Traffic Class per PDP context | 
 IF QCI = 1 OR 2 THEN     Maximum Authorized Traffic Class = "Conversational" ELSEIF QCI = 3 OR 4 THEN     Maximum Authorized Traffic Class = "Streaming" ELSEIF QCI = 5 OR 6 OR 7 OR 8 THEN     Maximum Authorized Traffic Class = "Interactive"; ELSE Maximum Authorized Traffic Class = "Background" ENDIF ;
| +| Traffic Handling Priority | 
 IF QCI = 5 OR 6 THEN     Maximum Authorized Traffic Handling Priority = "1"; ELSE IF QCI = 7 THEN     Maximum Authorized Traffic Handling Priority = "2"; ELSE IF QCI = 8 THEN     Maximum Authorized Traffic Handling Priority = "3"; ELSE the GGSN shall not derive Traffic Handling Priority ENDIF ;
| +| Signalling Indication | 
 IF QCI = 5 THEN     Signalling Indication = "Yes"; ELSE IF QCI = 6 OR 7 OR 8 THEN     Signalling Indication = "No"; ELSE the GGSN shall not derive Signalling Indication ENDIF ;
| +| Source Statistics Descriptor | 
 IF QCI = (1 OR 3) THEN     Source Statistics Descriptor = "speech"; ELSE IF QCI = 2 OR 4 THEN     Source Statistics Descriptor = "unknown"; ELSE the GGSN shall not derive Source Statistics Descriptor ENDIF ;
| +| Evolved Allocation/Retention Priority (see NOTE 1) | 
 Evolved Allocation/Retention Priority = Allocation-Retention-Priority as follows :      PL := Priority-Level ;     PVI := Pre-emption-Vulnerability ;     PCI := Pre-emption-Capability ;
| +| APN-AMBR UL and DL | For non-GBR PDP Contexts, APN-AMBR DL/UL = APN-Aggregate-Max-Bitrate DL/UL | +| NOTE 1: Evolved Allocation/Retention Priority is derived only if supported by the SGSN.
NOTE 2: When APN-AMBR is supported in GPRS and the PCEF performs the bearer binding, the MBR for non-GBR PDP-Contexts is not derived | | + +#### 6.4.1.2 Comparing UMTS QoS Parameters against the Authorized UMTS QoS parameters in GGSN for UE initiated PDP context + +Upon receiving a PDP context activation, the GGSN requests PCC rules from the PCRF (see 3GPP TS 29.212 [9] for details). The PCRF may supply Authorized IP QoS Parameters per PDP context together with the PCC rules. The GGSN maps the Authorized IP QoS parameters per PDP Context to Authorized UMTS QoS parameters according to subclause 6.4.1.1 and then compares the requested UMTS QoS parameters against the corresponding Authorized UMTS QoS parameters. The following criteria shall be fulfilled: + +- If the requested Guaranteed Bitrate DL/UL (if the requested Traffic Class is Conversational or Streaming) is equal to the Authorized Guaranteed data rate DL/UL; and +- if received, the requested Maximum Bitrate DL/UL (if the requested Traffic Class is Interactive or Background) is equal to Maximum Authorized data rate DL/UL; and +- the requested Traffic Class is equal to Maximum Authorized Traffic Class; and +- if received, the requested Evolved Allocation/Retention Priority is equal to Allocation-Retention-Priority. +- if received, the requested APN-AMBR DL/UL is equal to the APN-Aggregate-Max-Bitrate DL/UL. + +Then, the GGSN shall accept the PDP context activation or modification with the UE requested parameters. Otherwise, the GGSN is adjusted (downgrade or upgrade) the requested UMTS QoS parameters to the values that were authorized. + +### 6.4.2 3GPP- EPS + +#### 6.4.2.1 Authorized IP QoS parameters per PDP Context to Authorized UMTS QoS parameters mapping in P-GW. + +This Translation/Mapping function in the P-GW applies when the P-GW interacts with a Gn/Gp SGSN. + +The Translation/Mapping function in the P-GW shall derive the Authorized UMTS QoS parameters from the Authorized IP QoS parameters derived for the bearer applying the rules in table 6.4.2. + +**Table 6.4.2: Rules for derivation of the Authorized UMTS QoS Parameters per PDP context from the Authorized IP QoS Parameters in P-GW.** + +| Authorized UMTS QoS Parameter per PDP context | Derivation from Authorized IP QoS Parameters | +|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Maximum Authorized Bandwidth DL and UL per PDP context (see NOTE 2) | For non-GBR bearers, Maximum Authorized Bandwidth DL/UL per PDP context = APN-Aggregate-Max-Bitrate DL/UL
For GBR bearers, Maximum Authorized Bandwidth DL/UL per PDP context = Sum of Maximum Authorized Data Rate DL/UL for all PCC Rules bound to that bearer | +| Guaranteed Authorized Data Rate DL and UL per PDP context | Guaranteed Authorized Data Rate DL/UL per PDP context = Sum of Guaranteed Authorized Data Rate DL/UL for all PCC Rules bound to that bearer | +| Maximum Authorized Traffic Class per PDP context | 
 IF QCI = 1 OR 2 OR 3 THEN     Maximum Authorized Traffic Class = "Conversational" ELSEIF QCI = 4 THEN     Maximum Authorized Traffic Class = "Streaming" ELSEIF QCI = 5 OR 6 OR 7 OR 8 THEN     Maximum Authorized Traffic Class = "Interactive"; ELSE Maximum Authorized Traffic Class = "Background" ENDIF ;
| +| Traffic Handling Priority | 
 IF QCI = 5 OR 6 THEN     Maximum Authorized Traffic Handling Priority = "1"; ELSE IF QCI = 7 THEN     Maximum Authorized Traffic Handling Priority = "2"; ELSE IF QCI = 8 THEN     Maximum Authorized Traffic Handling Priority = "3"; ELSE the P-GW shall not derive Traffic Handling Priority ENDIF ;
| +| Signalling Indication | 
 IF QCI = 5 THEN     Signalling Indication = "Yes"; ELSE IF QCI = 6 OR 7 OR 8 THEN     Signalling Indication = "No"; ELSE the P-GW shall not derive Signalling Indication ENDIF ;
| +| Source Statistics Descriptor | 
 IF QCI = 1 THEN     Source Statistics Descriptor = "speech"; ELSE IF QCI = 2 OR 3 OR 4 THEN     Source Statistics Descriptor = "unknown"; ELSE the P-GW shall not derive Source Statistics Descriptor ENDIF ;
| +| APN-AMBR DL and UL (see NOTE 3) | For non-GBR bearers, APN-AMBR = APN-Aggregate-Max-Bitrate DL/UL | +| Transfer Delay (see NOTE 1) | 
 IF QCI = 2 THEN     Transfer Delay = 150 ms ELSE IF QCI = 3 THEN     Transfer Delay >= 80 ms ELSE IF QCI = 1 OR 4 the P-GW shall set the Transfer Delay as the Packet Delay Budget for that QCI ELSE the P-GW shall not derive Transfer Delay. ENDIF ;
| + +| | | +|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Evolved Allocation/Retention Priority (see NOTE 4) |

Evolved Allocation/Retention Priority = Allocation-Retention-Priority as follows :

PL := Priority-Level ;
PVI := Pre-emption-Vulnerability ;
PCI := Pre-emption-Capability ;

| +| NOTE 1: Recommended Packet Delay Budget values for the different QCI values are defined in subclause 6.1.7, 3GPP TS 23.203 [2]. | | +| NOTE 2: For non-GBR bearers, applicable only if APN-AMBR is not supported by the SGSN. | | +| NOTE 3: Applicable to all non-GBR PDP-Contexts when supported by the SGSN. | | +| NOTE 4: Evolved Allocation/Retention Priority is derived only if supported by the SGSN. | | + +#### 6.4.2.2 Comparing UMTS QoS Parameters against the Authorized UMTS QoS parameters in P-GW for UE initiated PDP context + +Upon receiving a PDP context activation, the P-GW requests PCC rules from the PCRF (see 3GPP TS 29.212 [9] for details). The PCRF may supply Authorized IP QoS Parameters applicable for the provided PCC rules. The P-GW calculates the Authorized IP QoS parameters per bearer and maps the Authorized IP QoS parameters per bearer to Authorized UMTS QoS parameters according to subclause 6.4.2.1 and then compares the requested UMTS QoS parameters against the corresponding Authorized UMTS QoS parameters. The following criteria shall be fulfilled: + +- If the requested Guaranteed Bitrate DL/UL (if the requested Traffic Class is Conversational or Streaming) is equal to the Authorized Guaranteed data rate DL/UL; and +- the requested Maximum Bitrate DL/UL (if the requested Traffic Class is Interactive or Background) is equal to Maximum Authorized data rate DL/UL; and +- the requested Traffic Class is equal to Maximum Authorized Traffic Class; and +- if received, the requested Evolved Allocation/Retention Priority is equal to Allocation-Retention-Priority. + +Then, the P-GW shall accept the PDP context activation with the UE requested parameters. Otherwise, the P-GW shall accept the request and adjust (downgrade or upgrade) the requested UMTS QoS parameters to the values that were authorized. + +## 6.5 QoS parameter mapping Functions at UE for a UE-initiated GPRS PDP Context + +Figure 6.5.1 indicates the entities participating in the generation of the requested QoS parameters when the UE activates or modifies a PDP Context. The steps are: + +1. The Application provides the UMTS BS Manager, possibly via the IP BS Manager and the Translation/Mapping function, with relevant information to perform step 2 or step 4. (Not subject to standardization within 3GPP). +2. If needed, information from step 1 is used to access a proper set of UMTS QoS Parameters. See 3GPP TS 26.114 [29] for Conversational Codec Applications and 3GPP TS 26.234 [6] for Streaming Codec Applications. +3. If SDP is available then the SDP Parameters should give guidance for the UMTS BS Manager (possibly via the IP Manager and the Translation/Mapping function), according to the rules in clause 6.5.1, to set the Maximum Bitrate UL/DL and the Guaranteed Bitrate UL/DL. Furthermore the Maximum Authorized Bandwidth UL/DL and Maximum Authorised Traffic Class should be derived according to the rules in clause 6.5.2. +4. A set of UMTS QoS Parameters values from step 2 (or directly from step 1) is possibly merged together with the Maximum Bitrate UL/DL and the Guaranteed Bitrate UL/DL from step 3. The result should constitute the requested UMTS QoS Parameters. The UE should check that the requested Guaranteed Bitrate UL/DL or requested Maximum Bitrate UL/DL (depending on the requested Traffic Class) does not exceed the Maximum Authorized Bandwidth UL/DL derived in step 3. Furthermore, if the UE has implemented the mapping rule for Maximum Authorized Traffic Class, as defined in clause 6.5.2, the UE should check that the requested Traffic Class does not exceed the Maximum Authorised Traffic Class derived in step 3. + +![A block diagram showing the framework for generating requested QoS parameters in the UE. The UE contains an Application, SDP Handler, IP BS Manager, Translation/Mapping, UMTS BS Manager, and Session Manager. The SDP Handler receives (SDP) from outside. Arrows 1) and 3) go from Application to IP BS Manager. Arrows 2) and 4) go from IP BS Manager to UMTS BS Manager and Session Manager respectively. A stack of boxes labeled 'UMTS QoS Param. Per Applic Type' is connected to the UMTS BS Manager. The Session Manager sends 'PDP Context Activation and Modification' to the SGSN's Session Manager.](dd5771673aececa53d42ece89218299d_img.jpg) + +The diagram illustrates the internal components of a User Equipment (UE) and its interaction with an SGSN. Inside the UE, an **Application** sends data to an **SDP Handler** (labeled 1)). The **SDP Handler** receives external **(SDP)** data and sends it to the **IP BS Manager** (labeled 3)). The **IP BS Manager** passes data to **Translation / Mapping**, which then sends it to the **UMTS BS Manager** (labeled 2)). The **UMTS BS Manager** interacts with a stack of boxes representing **UMTS QoS Param. Per Applic Type** and sends data to the **Session Manager** (labeled 4)). Finally, the **Session Manager** sends a **PDP Context Activation and Modification** message to the **Session Manager** inside the **SGSN**. + +A block diagram showing the framework for generating requested QoS parameters in the UE. The UE contains an Application, SDP Handler, IP BS Manager, Translation/Mapping, UMTS BS Manager, and Session Manager. The SDP Handler receives (SDP) from outside. Arrows 1) and 3) go from Application to IP BS Manager. Arrows 2) and 4) go from IP BS Manager to UMTS BS Manager and Session Manager respectively. A stack of boxes labeled 'UMTS QoS Param. Per Applic Type' is connected to the UMTS BS Manager. The Session Manager sends 'PDP Context Activation and Modification' to the SGSN's Session Manager. + +Figure 6.5.1: Framework for generating requested QoS parameters in the UE + +### 6.5.1 SDP to UMTS QoS parameter mapping in UE + +If SDP Parameters are available, then before activating or modifying a PDP Context the UE should check if the SDP Parameters give guidance for setting the requested UMTS QoS Parameters. The UE should use the mapping rule in table 6.5.1.1 to derive the Maximum and Guaranteed Bitrate DL/UL from the SDP Parameters. + +**Table 6.5.1.1: Recommended rules for derivation of the requested Maximum and Guaranteed Bitrate DL/UL per media component in the UE** + +| UMTS QoS Parameter per media component | Derivation from SDP Parameters | +|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Maximum Bitrate DL/UL and Guaranteed Bitrate DL/UL per media component | 
 /* Check if the media use codec(s) */ IF [<media> = ("audio" or "video")] and [<transport> = "RTP/AVP"] THEN     /* Check if Streaming */     IF a= ("sendonly" or "recvonly") THEN         Maximum Bitrate DL/UL and Guaranteed Bitrate DL/UL per media component as specified in 3GPP TS 26.234 [6] ;         /* Conversational as default !*/     ELSE         Maximum Bitrate DL/UL and Guaranteed Bitrate DL/UL per media component as specified in reference 3GPP TS 26.114 [29] ;     ENDIF ;      /* Check for presence of bandwidth attribute for each media component */ ELSEIF b=AS:<bandwidth-value> is present THEN     IF media stream only downlink THEN         Maximum Bitrate DL = Guaranteed Bitrate DL =<bandwidth-value> ;     ELSEIF mediastream only uplink THEN         Maximum Bitrate UL = Guaranteed Bitrate UL =<bandwidth-value> ;     ELSEIF mediastreams both downlink and uplink THEN         Maximum Bitrate DL = Guaranteed Bitrate DL =<bandwidth-value> ;         Maximum Bitrate UL = Guaranteed Bitrate UL =<bandwidth-value> ;     ENDIF; ELSE     /* SDP does not give any guidance ! */     Maximum Bitrate DL/UL and Guaranteed Bitrate DL/UL per media component as specified by the UE manufacturer; ENDIF ;
| + +### 6.5.2 SDP parameters to Authorized UMTS QoS parameters mapping in UE + +If the PDP Context is activated or modified the UE should use the mapping rules in table 6.5.2.1 for all applications using SDP to derive the Maximum Authorized Bandwidth UL/DL per IP flow or bidirectional combinations of IP flows. + +Table 6.5.2.1 also has a mapping rule for derivation of Maximum Authorized Traffic Class per IP flow or bidirectional combinations of IP flows which applies for session initiation and modification. + +In future releases this mapping rule may change. + +In the case of forking, the various forked responses may have different QoS requirements for the same IP flows of a media component. When the Authorized UMTS QoS Parameters are used by the UE, they shall be set equal to the highest values requested for the IP flows of that media component by any of the active forked responses. The UE should use the mapping rule in table 6.5.2.1 for each forked response. + +**Table 6.5.2.1: Rules for derivation of the Maximum Authorized Bandwidth DL/UL and the Maximum Authorized Traffic Class per IP flow or bidirectional combination of IP flows in the UE** + +| Authorized UMTS QoS
Parameter | Derivation from SDP Parameters
(see Note 4) | +|------------------------------------------|--------------------------------------------------------| +|------------------------------------------|--------------------------------------------------------| + +### **Maximum Authorized Bandwidth DL (Max\_BW\_DL) and UL (Max\_BW\_UL) (see NOTE 5)** + +``` + +IF a=recvonly THEN + IF = mobile originated THEN + Direction:= downlink; + + ELSE /* mobile terminated */ + Direction:= uplink; + ENDIF; + + ELSE /* a!= recvonly */ + IF a=sendonly THEN + IF = mobile originated THEN + Direction:= uplink; + ELSE /* mobile terminated */ + Direction:= downlink; + ENDIF; + ELSE /*sendrecv, inactive or no direction attribute*/ + Direction:=both; + ENDIF; + ENDIF; + + /* Max_BW_UL and Max_BW_DL */ + + IF media IP flow(s) THEN + IF bAS=AS: is present and + ( bTIAS=TIAS: is not present or + is present but not supported ) THEN + IF Direction=downlink THEN + Max_BW_UL:= 0; + Max_BW_DL:= bAS; + ELSE + IF Direction=uplink THEN + Max_BW_UL := bAS ; + Max_BW_DL := 0 ; + ELSE /*Direction=both*/ + Max_BW_UL:= bAS; + Max_BW_DL := bAS ; + ENDIF ; + ENDIF; + ELSE + IF bTIAS=TIAS: is present and supported THEN + bTDBW= bTIAS + transport-overhead; (NOTE 6) + + IF Direction=downlink THEN + Max_BW_UL:= 0; + Max_BW_DL:= bTDBW; (NOTE 6) + + ELSE + IF Direction=uplink THEN + Max_BW_UL:= bTDBW; (NOTE 6) + Max_BW_DL:= 0; + + ELSE /*Direction=both*/ + Max_BW_UL:= bTDBW; (NOTE 6) + Max_BW_DL:= bTDBW; (NOTE 6) + ENDIF; + ENDIF; + ELSE /* bTIAS=TIAS: is NOT present or is present but not supported*/ + bw:= as set by the UE manufacturer; + IF Direction=downlink THEN + Max_BW_UL:= 0; + Max_BW_DL:= bw; + ELSE + IF Direction=uplink THEN + Max_BW_UL:= bw; + Max_BW_DL:= 0; + + ELSE /*Direction=both*/ + Max_BW_UL:= bw; + Max_BW_DL:= bw; + ENDIF; + ENDIF; + ENDIF; + ENDIF; + ENDIF; + +``` + +| Authorized UMTS QoS Parameter | Derivation from SDP Parameters
(see Note 4) | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 
         ENDIF;          ENDIF;         ENDIF;         ENDIF;          ELSE /* RTCP IP flow(s) */         IF bRS=RS:<bandwidth> and bRR=RR:<bandwidth> is present THEN           Max_BW_UL:= (bRS + bRR) / 1000;           Max_BW_DL:= (bRS + bRR) / 1000;         ELSE           IF bAS=AS:<bandwidth> is present and             ( bTIAS=TIAS:<Tibandwidth> is not present or               is present but not supported ) THEN             IF bRS=RS:<bandwidth> is present and bRR=RR:<bandwidth> is not present             THEN               Max_BW_UL := MAX[0.05 * bAS, bRS / 1000] ;               Max_BW_DL := MAX[0.05 * bAS, bRS / 1000] ;             ENDIF;              IF bRS=RS:<bandwidth> is not present and bRR=RR:<bandwidth> is present             THEN               Max_BW_UL:= MAX[0.05 * bAS, bRR / 1000];               Max_BW_DL:= MAX[0.05 * bAS, bRR / 1000];             ENDIF;              IF bRS=RS:<bandwidth> and bRR=RR:<bandwidth> is not present THEN               Max_BW_UL := 0.05 * bAS ;               Max_BW_DL := 0.05 * bAS ;             ENDIF;           ELSE             IF bTIAS=TIAS:<Tibandwidth> is present and supported THEN               bTDBW= bTIAS + transport-overhead; (NOTE 6)                IF bRS=RS:<bandwidth> is present and                 bRR=RR:<bandwidth> is not present THEN                   Max_BW_UL:= MAX[0.05 * bTDBW, bRS]/1000;                   Max_BW_DL:= MAX[0.05 * bTDBW, bRS]/1000;                 ENDIF;                  IF bRS=RS:<bandwidth> is not present and                   bRR=RR:<bandwidth> is present THEN                     Max_BW_UL:= MAX[0.05 * bTDBW, bRR]/1000;                     Max_BW_DL:= MAX[0.05 * bTDBW, bRR]/1000;                   ENDIF;                    IF bRS=RS:<bandwidth> and                     bRR=RR:<bandwidth> is not present THEN                       Max_BW_UL:= 0.05 * bTDBW /1000;                       Max_BW_DL:= 0.05 * bTDBW /1000;                     ENDIF;                  ELSE                   Max_BW_UL:= as set by the UE manufacture;                   Max_BW_DL:= as set by the UE manufacture;                  ENDIF;               ENDIF;             ENDIF;           ENDIF;         ENDIF;
| + +| Authorized UMTS QoS Parameter | Derivation from SDP Parameters
(see Note 4) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Maximum Authorized Traffic Class [MaxTrafficClass] (see NOTE 1, 2 and 3) | 
 IF (all media IP flows of media type "audio" or "video" for the session are     unidirectional and have the same direction) THEN     MaxService:= streaming; ELSE     MaxService:= conversational; ENDIF;  CASE <media> OF     "audio":      MaxTrafficClass:= MaxService;     "video":      MaxTrafficClass:= MaxService;     "application": MaxTrafficClass:=conversational;     "data":       MaxTrafficClass:=interactive with priority 3;     "control":    MaxTrafficClass:=interactive with priority 1;     /*new media type*/     OTHERWISE:    MaxTrafficClass:=background; END;
| +| NOTE 1: The Maximum Authorized Traffic Class for a RTCP IP flow is the same as for the corresponding RTP media IP flow. | | +| NOTE 2: When audio or video IP flow(s) are removed from a session, the parameter MaxService shall keep the originally assigned value. | | +| NOTE 3: When audio or video IP flow(s) are added to a session, the UE shall derive the parameter MaxService taking into account the already existing media IP flows within the session. | | +| NOTE 4: The SDP parameters are described in RFC 2327 [11]. | | +| NOTE 5: The 'b=RS:' and 'b=RR:' SDP bandwidth modifiers are defined in RFC 3556 [13]. | | +| NOTE 6: TIAS is defined in IETF RFC 3890 [23]. RFC 3890 clause 6.4 provides procedures for converting TIAS to transport-dependant values. This procedure relies on the presence of maxprate (also defined in RFC 3890). | | + +The UE should per ongoing session store the Authorized UMTS QoS parameters per IP flow or bidirectional combination of IP flows. + +Before activating or modifying a PDP context the UE should check that the requested Guaranteed Bitrate UL/DL (if the Traffic Class is Conversational or Streaming) or the requested Maximum Bitrate UL/DL (if the Traffic Class is Interactive or Background) does not exceed the Maximum Authorized Bandwidth UL/DL per PDP context (calculated according to the rule in table 6.5.2.2). If the requested Guaranteed Bitrate UL/DL or the requested Maximum Bitrate UL/DL exceeds the Maximum Authorized Bandwidth UL/DL per PDP context, the UE should reduce the requested Guaranteed Bitrate UL/DL or the requested Maximum Bitrate UL/DL to the Maximum Authorized Bandwidth UL/DL per PDP context. Furthermore, if the rule in table 6.5.2.1 for calculating Traffic Class per IP flow or bidirectional combination of IP flows is implemented, the UE should check that the requested UMTS QoS parameter Traffic Class does not exceed the Maximum Authorized Traffic Class per PDP context (calculated according to the rule in table 6.5.2.2). If the requested UMTS QoS parameter Traffic Class exceeds the Maximum Authorized Traffic Class per PDP context, the UE should reduce the requested UMTS QoS parameter Traffic Class to the Maximum Authorized Traffic Class per PDP context. + +**Table 6.5.2.2: Rules for calculating the Maximum Authorized Bandwidths and Maximum Authorized Traffic Class per PDP Context in the UE** + +| Authorized UMTS QoS Parameter per PDP Context | Calculation Rule | +|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Maximum Authorized Bandwidth DL and UL per PDP Context |

Maximum Authorized Bandwidth DL/UL per PDP Context is the sum of all Maximum Authorized Bandwidth DL/UL for all the IP flows or bidirectional combinations of IP flows (as derived according to table 6.5.2.1) associated with that PDP Context ;

 IF Maximum Authorized Bandwidth DL/UL per PDP Context > 256 Mbps THEN     Maximum Authorized Bandwidth DL/UL per PDP Context = 256 Mbps     /* See 3GPP TS 23.107 [4] */ END;
| +| Maximum Authorized Traffic Class per PDP Context |

Maximum Authorized Traffic Class per PDP Context = MAX [Maximum Authorized QoS Class per IP flow or bidirectional combination of IP flows (as derived according to table 6.5.2.1) among all the IP flows or bidirectional combinations of IP flows associated with that PDP Context] ;

(The MAX function ranks the possible Maximum Authorized Traffic Class values as follows: Conversational > Streaming > Interactive with priority 1 > Interactive with priority 2 > Interactive with priority 3 > Background)

| + +# 7 PCRF addressing + +## 7.1 General + +The PCRF discovery procedures are needed where more than one PCRF is present in an operator's network realm. Within such a deployment, an additional functional element, called DRA, is needed. PCRF discovery procedures include all the procedures that involve a DRA functional element. + +Routing of Diameter messages from a network element towards the right Diameter realm in a PLMN is based on standard Diameter realm-based routing, as specified in IETF RFC 6733 [61] using the UE-NAI domain part. If PLMN is separated into multiple realms based on PDN information or IP address range (if applicable); the PDN information available in the Called-Station-Id AVP, or the UE's Ipv4 address available in the Framed-IP-Address AVP or the UE's Ipv6 address or prefix provided within the Framed-Ipv6-Prefix AVP may be used to assist routing PCC message to the appropriate Diameter realm. + +The DRA keeps status of the assigned PCRF for a certain UE and IP-CAN session across all reference points, e.g. Gx, Gxx, S9, Rx and for unsolicited application reporting, the Sd interfaces. + +The DRA shall support the functionality of a proxy agent and a redirect agent as defined in IETF RFC 6733 [61]. The mode in which it operates (i.e. proxy or redirect) shall be based on operator's requirements. + +Diameter clients of the DRA, i.e. AF, PCEF, BBERF, RCAF and PCRF in roaming scenarios shall support all procedures required to properly interoperate with the DRA in both the proxy and redirect modes. + +NOTE: The proxy mode includes two variants: + +PA1: Proxy agent based on the standard Diameter proxy agent functionality. All the messages need to go through the DRA. + +PA2: Proxy agent based on the standard Diameter proxy agent functionality. Session establishment messages always go through the DRA. Gx, Gxx and S9 session termination messages always go through the DRA. All other messages bypass the DRA. + +## 7.2 DRA Definition + +The DRA (Diameter Routing Agent) is a functional element that ensures that all Diameter sessions established over the Gx, S9, Gxx, Rx interfaces and for unsolicited application reporting, the Sd interface for a certain IP-CAN session reach the same PCRF when multiple and separately addressable PCRFs have been deployed in a Diameter realm. The DRA also ensures that the NRR commands over Np interface reach the same PCRF for a certain IP-CAN session. The DRA is not required in a network that deploys a single PCRF per Diameter realm. + +## 7.3 DRA Procedures + +### 7.3.1 General + +A DRA implemented as a Diameter Redirect Agent or a Diameter Proxy Agent shall be compliant to IETF RFC 6733 [61], except when noted otherwise in this document. + +### 7.3.2 DRA Information Storage + +The DRA shall maintain PCRF routing information per IP-CAN session or per UE-NAI, depending on the operator's configuration. + +The DRA shall select the same PCRF for all the Diameter sessions established for the same UE in case 2a. + +As there's only one S9 session per UE, the V-DRA/H-DRA shall select the same V-PCRF/H-PCRF respectively for the same UE in the roaming case. + +The DRA has information about the user identity (UE NAI), the UE IPv4 address and/or IPv6 prefix, the APN (if available), the PCEF identity (if available) and the selected PCRF identity for a certain IP-CAN Session. + +NOTE 1: The DRA derives the PCEF identity from the Origin-Host AVP of the CCR command received from the PCEF. + +The DRA finds the correct PCRF by matching the user identity (if available), IPv4 address or IPv6 address/prefix (if available) and APN (if available) received in the message from the BBERF/PCEF/AF/TDF/ RCAf/V-PCRF with the corresponding information stored the DRA. + +NOTE 2: If the DRA does not use the IP address to find the PCRF and the user identity in the IP-CAN and the application level identity for the user are of different kinds (e.g. user identity is the IP-CAN is IMSI and application level identity for the user is SIPURI), the DRA needs to maintain, or have access to, the mapping between the identities. Such mapping is not subject to specification within this TS. + +NOTE 3: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. + +When matching the APNs to each other, the DRA shall apply the procedures in Annex I. + +For the PCRF selection over the Rx reference point, the DRA may additionally match the IP domain Id received in the message from the AF with the PCEF identity stored in the DRA to find the correct PCRF. + +NOTE 4: In order to correlate the PCEF Identity and the domain identity, the DRA uses configured mapping between those identities. + +For the PCRF selection over the Rx reference point, when the APN related to the IP-CAN session is dedicated for the purpose of offering services to remote UEs via a ProSe UE-to-network relay UE, the DRA shall use the UE IPv6 prefix alone to find the correct PCRF. + +The PCRF routing information stored for an IP-CAN session in the DRA shall be removed after the IP-CAN session is terminated. In case of DRA change (e.g. inter-operator handover), the information about the IP-CAN session stored in the old DRA shall be removed. + +The PCRF routing information stored per UE in the DRA may be removed when no more IP-CAN and gateway control sessions are active for the UE. + +### 7.3.3 Capabilities Exchange + +In addition to the capabilities exchange procedures defined in IETF RFC 6733 [61], the Redirect DRA and Proxy DRA shall advertise the specific applications it supports (e.g., Gx, Gxx, Rx, Np,S9 and for unsolicited application reporting, Sd) by including the value of the application identifier in the Auth-Application-Id AVP and the value of the 3GPP (10415) in the Vendor-Id AVP of the Vendor-Specific-Application-Id AVP contained in the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +### 7.3.4 Redirect DRA + +#### 7.3.4.1 Redirecting Diameter Requests + +A DRA implemented as a Diameter redirect agent shall redirect the received Diameter request message by carrying out the procedures defined in clause 6.1.7 of IETF RFC 6733 [61]. The Client shall use the value within the Redirect-Host AVP of the redirect response in order to obtain the PCRF identity. The DRA may provide the Redirect-Host-Usage AVP in the redirect response to provide a hint to the Client about how the cached route table entry created from the Redirect-Host AVP is to be used as described in clause 6.13 of IETF RFC 6733 [61]. + +The two most relevant redirect host usage scenarios for PCC from IETF RFC 6733 [61] are: + +- If the PCRF routing information is per UE-NAI, the DRA shall set the Redirect-Host-Usage AVP to ALL\_USER. The DRA client may contact the DRA on IP-CAN session termination. +- If the PCRF routing information is per IP-CAN session, the DRA shall set the Redirect-Host-Usage AVP to ALL\_SESSION. The DRA client shall contact the DRA on IP-CAN session termination. + +The DRA may also provide the Redirect-Max-Cache-Time AVP in the redirect response to indicate to the Client the lifetime of the cached route table entry created from the Redirect-Host and Redirect-Host-Usage AVP values as described in clause 6.14 of IETF RFC 6733 [61]. + +If the DRA is maintaining PCRF routing information per IP-CAN session, the DRA shall be aware of Gx and Gxx Diameter termination requests as defined in 3GPP TS 29.212 [9] in order to detect whether release of DRA bindings is required. Otherwise the DRA clients shall use cached route table entry created from the Redirect-Host, Redirect-Host-Usage and Redirect-Max-Cache-Time AVPs to determine whether DRA interaction is required. + +The DRA shall be aware of IP-CAN Session modification requests over Gx which is to update the Ipv4 address of the UE by the PCEF. + +If the client is the AF, the DRA (redirect) does not need to maintain Diameter sessions and Diameter Base redirect procedures are applicable. Therefore, an AF should not send an AF session termination request to the DRA. + +#### 7.3.4.2 DRA binding removal + +If the DRA binding is per IP-CAN session and the IP-CAN session is terminated or if the DRA binding is per UE and the last IP-CAN session is terminated (eg. From an indication by the BBERF/PCEF) the Redirect DRA shall remove the associated DRA binding information and responds with a Diameter redirect answer message. + +### 7.3.5 Proxy DRA + +The DRA shall support the functionality of a Diameter proxy agent as defined in IETF RFC 6733 [61]. + +When the DRA receives a request from a client, it shall check whether it already has selected a PCRF for the UE or the UE's IP-CAN session; if it does have a PCRF already selected for that UE or UE's IP-CAN session, it shall proxy the request to the corresponding PCRF. If the request is an IP-CAN session termination or gateway control session termination, the DRA shall check whether PCRF routing information shall be removed as specified in clause 7.3.3. If the DRA does not have a PCRF already selected, it shall follow one of the procedures below: + +- If the request is an IP-CAN session establishment or gateway control session establishment, it shall select a PCRF to handle all sessions for that UE or UE's IP-CAN session. It shall then proxy the request to the selected PCRF. +- Otherwise, if the request is not an IP-CAN session establishment or gateway control session establishment, it shall reject the request by returning a DIAMETER\_UNABLE\_TO\_COMPLY error code. + +If a DRA is deployed in a PCRF's realm, clients of the DRA shall send the first request of a session to the DRA handling the PCRF's realm. Clients of the DRA shall as well send IP-CAN session termination and gateway control termination requests to the DRA. A client of the DRA shall be capable of sending every message of a session to the DRA. A client of the DRA may be configured to bypass the DRA on session modification messages and AF session termination messages by sending these types of messages directly to the PCRF. + +### 7.3.6 PCRF selection by BBERF/PCEF (non-roaming case) + +The PCEF (e.g. P-GW) or BBERF (e.g. Non-3GPP Access, S-GW) shall provide the DRA of the PCRF realm with identity parameters upon the first interaction between the access entity and the PCRF realm. + +If the redirect agent is used for DRA, the DRA shall use the redirecting requests procedure as specified in IETF RFC 6733 [61], and include the PCRF identity in the Redirect-Host AVP in the Diameter reply sent to the PCEF or the BBERF. + +If proxy agent is used for DRA, the DRA should use the proxy procedure as specified in IETF RFC 6733 [61]. For PA2 solution (described in clause 7.1), only session establishment, session modification with the UE's Ipv4 address updated and session termination messages shall be sent through the DRA. + +The identity parameters from the PCEF or BBERF may comprise the UE's Ipv4 address in the Framed-IP-Address AVP and/or the UE's Ipv6 prefix in the Framed-Ipv6-Prefix AVP, PDN information in the Called-Station-Id AVP and user identity in the Subscription-Id AVP. + +### 7.3.7 PCRF selection by AF + +If the AF has the realm identification (i.e. FQDN from a UE NAI) and is located in the HPLMN, the AF sends the user identity in the Subscription-Id AVP and PDN information (i.e. APN) if available in the Called-Station-Id AVP in a Diameter request to the DRA which acts as a Diameter agent. + +For an AF serving mission critical communication services (e.g. MCPTT), the AF shall derive the realm of the PCRF based on the IP address and, based on the PLMN ID, construct the Diameter destination realm and use that destination realm in the initial request to address the DRA. + +NOTE 1: An AF serving mission critical communication services as defined in 3GPP TS 23.280 [64] can be independent from a PLMN and is not guaranteed to have any realm identification. + +If the AF does not have proper knowledge about the user identity and the AF is located in the HPLMN, the AF may use pre-configured information to find the DRA. + +NOTE 1A: How the AF which is a third party or non-IMS application server finds the DRA if it does not have the proper knowledge about the user identity is out of scope of this specification. + +The AF shall provide the DRA of the PCRF realm with identity parameters upon the first interaction between the AF and the PCRF realm. + +If redirect agent is used for DRA, the DRA shall use the redirecting requests procedure as specified in IETF RFC 6733 [61], and include the PCRF identity in the Redirect-Host AVP in the Diameter reply sent to the AF. + +If proxy agent is used for DRA, the DRA should use the proxy procedure as specified in IETF RFC 6733 [61]. For PA2 solution (described in clause 7.1), only AF session establishment messages shall be sent through the DRA. + +The parameters from the AF may comprise the UE IP address in either the Framed-IP-Address AVP or the Framed-Ipv6-Prefix AVP, PDN information in the Called-Station-Id AVP, user identity in the Subscription-Id AVP and domain Identity in the IP-Domain-Id AVP (3GPP TS 23.203 [2]). + +NOTE 2: In case the user identity in the IP-CAN and the application level identity for the user are of different kinds (e.g. user identity in the IP-CAN is IMSI and application level identity for the user is SIPURI), the DRA needs to maintain, or have access to, the mapping between the identities. Such mapping is not subject to specification within this TS. + +### 7.3.8 PCRF selection in a roaming scenario + +In the roaming case, a V-DRA is needed in the visited PLMN when there are more than one PCRFs per realm. The V-DRA will ensure that all the related Diameter sessions for a UE are handled by the same V-PCRF. + +The BBERF in the visited access and home routed cases, the PCEF in the case of visited access and the AF when located in the visited PLMN may use pre-configured information (e.g. based on PDN) to find the V-DRA, and then find the V-PCRF. Other possible options are Dynamic peer discovery, or DNS-based. + +The V-PCRF can find the H-DRA based on the UE NAI, and then find the H-PCRF by the H-DRA. + +The V-PCRF shall provide the H-DRA of the H-PCRF realm with identity parameters upon the first interaction between the V-PCRF and the H-PCRF realm. + +If redirect agent is used for H-DRA, the H-DRA shall use the redirecting requests procedure as specified in IETF RFC 6733 [61], and include the H-PCRF identity in the Redirect-Host AVP in the Diameter reply sent to the V-PCRF. + +If proxy agent is used for H-DRA, the H-DRA should use the proxy procedure as specified in IETF RFC 6733 [61]. For PA2 solution (described in clause 7.1), only session establishment, session modification with the UE's Ipv4 address updated and, only for the Gx, Gxx and S9 interfaces, termination messages shall be sent through the H-DRA. + +The identity parameters from the V-PCRF may comprise the same parameters sent by the PCEF or the BBERF to the V-PCRF, i.e. the user identity (UE NAI), APN, the UE's Ipv4 address and/or Ipv6 prefix (3GPP TS 23.203 [2]). + +If redirect agent or PA2 is used for H-DRA, and the V-PCRF receives establishment message from the AF in the VPLMN, the V-PCRF may send the message to the H-PCRF directly (e.g. based on the stored information provided by H-DRA during the IP-CAN session establishment). + +### 7.3.9 PCRF selection by TDF for unsolicited application reporting + +The TDF uses pre-configured information to find the DRA. + +The TDF shall provide the DRA of the PCRF realm with identity parameters upon the first interaction between the TDF and the PCRF realm. + +If redirect agent is used for DRA, the DRA shall use the redirecting requests procedure as specified in IETF RFC 6733 [61], and include the PCRF identity in the Redirect-Host AVP in the Diameter reply sent to the TDF. + +If proxy agent is used for DRA, the DRA should use the proxy procedure as specified in IETF RFC 6733 [61]. For PA2 solution (described in subclause 7.1), only TDF session establishment messages shall be sent through the DRA. + +The parameters from the TDF may comprise the UE IP address in either the Framed-IP-Address AVP or the Framed-Ipv6-Prefix AVP and PDN information in the Called-Station-ID AVP. + +NOTE: The TDF located in the HPLMN finds the H-PCRF for the roaming UE with home routed access case. +The TDF located in the VPLMN finds the V-PCRF for the roaming UE with visited access case. + +### 7.3.10 PCRF selection by RCAF + +For initial Non-Aggregated RUCI reporting, the RCAF shall provide the identity parameters to the DRA of the PCRF realm. + +The identity parameters from the RCAF may comprise PDN information in the Called-Station-Id AVP and user identity in the Subscription-Id AVP. + +In the roaming with home-routed access case, the RCAF can find the H-DRA based on the IMSI, and then find the H-PCRF by the H-DRA. The RCAF shall provide the H-DRA of the H-PCRF realm with identity parameters upon the first interaction between the RCAF and the H-PCRF realm. + +In the roaming with visited case, the RCAF shall provide the V-DRA of the V-PCRF realm with identity parameters upon the first interaction between the RCAF and the V-PCRF realm. + +If the redirect agent is used for DRA, the DRA shall use the redirecting requests procedure as specified in IETF RFC 6733 [61], and include the PCRF identity in the Redirect-Host AVP in the Diameter reply sent to the RCAF. + +If proxy agent is used for DRA, the DRA should use the proxy procedure as specified in IETF RFC 6733 [61]. + +For subsequent non-aggregated or aggregated RUCI reporting, the RCAF shall include the PCRF identity within the Destination-Host AVP for direct PCRF selection. The PCRF identity shall be responded by the PCRF within the PCRF-Address AVP in the initial non-aggregated RUCI reporting, for identifying the same destination PCRF in the subsequent non-aggregated or aggregated RUCI reporting. + +## 7.4 DRA flows + +### 7.4.1 Proxy DRA + +#### 7.4.1.1 Establishment of Diameter Sessions + +##### 7.4.1.1.1 Non-roaming cases + +Establishment of Diameter sessions may occur at any of the following cases: + +- Gateway control establishment +- IP-CAN session establishment + +- AF session establishment +- For unsolicited application reporting, TDF session establishment + +![Sequence diagram showing the establishment of Diameter sessions using a DRA (proxy). The diagram involves four main entities: Client (AF/BBERF/PCEF/TDF), DRA (proxy), PCRF-1, and PCRF-2. The sequence starts with an external trigger to the Client. The Client sends a Diameter Request (Rx/Gx/Gxx/Sd) to the DRA. The DRA performs a binding creation/retrieval. The DRA proxies the request to PCRF-1. PCRF-1 returns a Diameter Answer to the DRA. The DRA proxies the answer back to the Client. A shaded region labeled PA2 contains step 7, 'PCRF address storage', which is a conditional step. A legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages.](838c31609fac483fa2c01c7896a2fd6d_img.jpg) + +``` + +sequenceDiagram + participant Client as Client (AF/BBERF/PCEF/TDF) + participant DRA as DRA (proxy) + participant PCRF1 as PCRF-1 + participant PCRF2 as PCRF-2 + + Note left of Client: External trigger + Client->>DRA: 2. Rx/Gx/Gxx/Sd Diameter Request + Note right of DRA: 3. DRA binding creation/retrieval + DRA->>PCRF1: 4. Proxy Rx/Gx/Gxx/Sd Diameter Request + PCRF1-->>DRA: 5. Rx/Gx/Gxx/Sd Diameter Answer + DRA-->>Client: 6. Proxy Rx/Gx/Gxx/Sd Diameter Answer + Note right of Client: 7. PCRF address storage + Note right of PCRF2: Legend: + Note right of PCRF2: --> Mandatory + Note right of PCRF2: -.-> Conditional + +``` + +Sequence diagram showing the establishment of Diameter sessions using a DRA (proxy). The diagram involves four main entities: Client (AF/BBERF/PCEF/TDF), DRA (proxy), PCRF-1, and PCRF-2. The sequence starts with an external trigger to the Client. The Client sends a Diameter Request (Rx/Gx/Gxx/Sd) to the DRA. The DRA performs a binding creation/retrieval. The DRA proxies the request to PCRF-1. PCRF-1 returns a Diameter Answer to the DRA. The DRA proxies the answer back to the Client. A shaded region labeled PA2 contains step 7, 'PCRF address storage', which is a conditional step. A legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages. + +**Figure 7.4.1.1.1.1: Establishment of Diameter sessions using DRA (proxy)** + +1. A Client receives an external trigger (e.g. IP-CAN session establishment request) that requires the establishment of a Diameter session with a PCRF. +2. A Diameter Request (e.g. a Diameter CCR sent by PGW to indicate establishment of an IP-CAN session as defined in clauses 4.5.1, 4a.5.1 of 3GPP TS 29.212 [9]) is sent by the Client and received by a DRA (proxy). +3. The DRA (proxy) stores the user information (e.g. UE-NAI) and checks whether an active DRA binding exists. If not, the DRA creates a dynamic DRA binding (assignment of a PCRF node per UE or per IP-CAN session). + +NOTE 1: When the AF establishes an Rx session or TDF establishes a TDF session with the DRA, there is already a DRA binding active. + +4. The DRA (proxy) proxies the Diameter Request to the target PCRF. The proxied Diameter Request maintains the same Session-Id AVP value. +5. PCRF-1 returns a Diameter Answer as defined in clauses 4.5, 4a.5 of 3GPP TS 29.212 [9] to the DRA (proxy). +6. DRA (proxy) proxies the Diameter Answer to the Client. The proxied Diameter Answer maintains the same Session-Id AVP value. + +7. If PA2 option is implemented, the Client uses the Origin-Host AVP value provided in the Diameter Answer of step 6. This value is the identity of the target PCRF. The client populates the Destination-Host AVP with this address and sends any subsequent Diameter messages directly to this PCRF bypassing the DRA (proxy). + +NOTE 2: Figure 7.4.1.1.1.1 is also applicable when the AF/BBERF/PCEF/TDF in the VPLMN contacts the V-DRA to locate the V-PCRF. + +##### 7.4.1.1.2 Roaming cases + +Establishment of Diameter sessions may occur at any of the following cases: + +- V-PCRF initiates S9 Diameter session to H-PCRF + +- V-PCRF proxies Rx Diameter session to H-PCRF + +![Sequence diagram illustrating the establishment of Diameter sessions using DRA (proxy) in a roaming case. The diagram shows interactions between V-PCRF, H-DRA (proxy), H-PCRF-1, and H-PCRF-2. Steps include: 1. External trigger to V-PCRF; 2. Rx/S9 Diameter Request from V-PCRF to H-DRA; 3. DRA binding creation/retrieval at H-DRA; 4. Proxy Rx/S9 Diameter Request from H-DRA to H-PCRF-1; 5. Rx/S9 Diameter Answer from H-PCRF-1 to H-DRA; 6. Proxy Rx/S9 Diameter Answer from H-DRA to V-PCRF; 7. PCRF address storage at V-PCRF (conditional, PA2 option). A legend indicates solid arrows are Mandatory and dashed arrows are Conditional.](ddee3e67e0dfc22e25188fa635a19558_img.jpg) + +``` + +sequenceDiagram + participant External + participant V-PCRF + participant H-DRA as H-DRA (proxy) + participant H-PCRF-1 + participant H-PCRF-2 + + Note left of V-PCRF: PA2 + External->>V-PCRF: 1. External trigger + V-PCRF->>H-DRA: 2. Rx/S9 Diameter Request + H-DRA->>H-DRA: 3. DRA binding creation/retrieval + H-DRA->>H-PCRF-1: 4. Proxy Rx/S9 Diameter Request + H-PCRF-1->>H-DRA: 5. Rx/S9 Diameter Answer + H-DRA->>V-PCRF: 6. Proxy Rx/S9 Diameter Answer + V-PCRF-->>V-PCRF: 7. PCRF address storage + +``` + +**Legend:** + → *Mandatory* + - - - - → *Conditional* + +Sequence diagram illustrating the establishment of Diameter sessions using DRA (proxy) in a roaming case. The diagram shows interactions between V-PCRF, H-DRA (proxy), H-PCRF-1, and H-PCRF-2. Steps include: 1. External trigger to V-PCRF; 2. Rx/S9 Diameter Request from V-PCRF to H-DRA; 3. DRA binding creation/retrieval at H-DRA; 4. Proxy Rx/S9 Diameter Request from H-DRA to H-PCRF-1; 5. Rx/S9 Diameter Answer from H-PCRF-1 to H-DRA; 6. Proxy Rx/S9 Diameter Answer from H-DRA to V-PCRF; 7. PCRF address storage at V-PCRF (conditional, PA2 option). A legend indicates solid arrows are Mandatory and dashed arrows are Conditional. + +**Figure 7.4.1.1.2.1: Establishment of Diameter sessions using DRA (proxy) – Roaming case** + +1. V-PCRF receives a trigger to establish a Diameter session to H-PCRF (e.g. S9 session establishment request). +2. A Diameter Request involving either the Rx or S9 protocol is sent by the V-PCRF and received by a H-DRA (proxy) in the home PLMN. +3. The H-DRA (proxy) stores the user information (e.g. UE-NAI) and checks whether an active DRA binding exists. If not, the H-DRA creates a dynamic DRA binding (assignment of a PCRF node per UE or per IP-CAN session). +4. The H-DRA (proxy) proxies the Diameter Request to the target PCRF in the home PLMN. The proxied Diameter Request maintains the same Session-Id AVP value. +5. H-PCRF-1 returns a Diameter Answer to the H-DRA (proxy). +6. H-DRA (proxy) proxies the Diameter Answer to the V-PCRF. The proxied Diameter Answer maintains the same Session-Id AVP value. +7. If PA2 option is implemented, the V-PCRF uses the Origin-Host AVP value provided in the Diameter Answer of step 6. This value is the identity of the target H-PCRF. The V-PCRF populates the Destination-Host AVP with this address and sends any subsequent Diameter messages directly to this H-PCRF bypassing the H-DRA. + +#### 7.4.1.2 Modification of Diameter Sessions + +##### 7.4.1.2.1 Non-roaming cases + +###### 7.4.1.2.1.1 Client-initiated + +Modification of Diameter sessions may occur in any of the following cases: + +- Gateway control session modification +- IP-CAN session modification +- AF session modification +- For unsolicited application reporting, TDF session modification + +If PA1 option is implemented, only steps 2, 3, 4, 5, 6 are carried out. If PA2 option is implemented, only steps 2a, 5a are carried out. + +![Sequence diagram showing the modification of Diameter sessions through DRA (proxy) for AF/BBERF/PCEF/TDF interaction. The diagram involves four lifelines: Client (AF/BBERF/PCEF/TDF), DRA (proxy), PCRF-1, and PCRF-2. The process starts with an external trigger to the Client. The Client sends a Subsequent Diameter Request to the DRA (step 2). If the PA2 option is implemented, the Client also sends a Subsequent Diameter Request directly to PCRF-1 (step 2a). The DRA then verifies its binding (step 3) and proxies the request to PCRF-1 (step 4). PCRF-1 returns a Diameter Answer to the DRA (step 5). If the PA2 option is implemented, PCRF-1 also returns a Diameter Answer directly to the Client (step 5a). Finally, the DRA proxies the Diameter Answer to the Client (step 6). A legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages.](cf8bd014a50b7c69435e804f67f9617f_img.jpg) + +``` + +sequenceDiagram + participant Client as Client (AF/BBERF/PCEF/TDF) + participant DRA as DRA (proxy) + participant PCRF1 as PCRF-1 + participant PCRF2 as PCRF-2 + + Note left of Client: 1. External trigger + Client->>DRA: 2. Subsequent Rx/Gx/Gxx/Sd Diameter Request + Note right of Client: PA2 + Client->>PCRF1: 2a. Subsequent Rx/Gx/Gxx/Sd Diameter Request + Note right of DRA: 3. Verify DRA Binding + DRA->>PCRF1: 4. Proxy Rx/Gx/Gxx/Sd Diameter Request + PCRF1->>DRA: 5. Rx/Gx/Gxx/Sd Diameter Answer + Note right of PCRF1: PA2 + PCRF1->>Client: 5a. Rx/Gx/Gxx/Sd Diameter Answer + DRA->>Client: 6. Proxy Rx/Gx/Gxx/Sd Diameter Answer + + Note right of PCRF2: Legend: + Note right of PCRF2: --> Mandatory + Note right of PCRF2: -.-> Conditional + +``` + +Sequence diagram showing the modification of Diameter sessions through DRA (proxy) for AF/BBERF/PCEF/TDF interaction. The diagram involves four lifelines: Client (AF/BBERF/PCEF/TDF), DRA (proxy), PCRF-1, and PCRF-2. The process starts with an external trigger to the Client. The Client sends a Subsequent Diameter Request to the DRA (step 2). If the PA2 option is implemented, the Client also sends a Subsequent Diameter Request directly to PCRF-1 (step 2a). The DRA then verifies its binding (step 3) and proxies the request to PCRF-1 (step 4). PCRF-1 returns a Diameter Answer to the DRA (step 5). If the PA2 option is implemented, PCRF-1 also returns a Diameter Answer directly to the Client (step 5a). Finally, the DRA proxies the Diameter Answer to the Client (step 6). A legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages. + +**Figure 7.4.1.2.1.1.1: Modification of Diameter sessions through DRA (proxy)- AF/BBERF/PCEF/TDF interaction** + +1. A Client receives an external trigger (e.g. IP-CAN session modification) that requires a subsequent Diameter message to be sent to the PCRF. +2. A subsequent Diameter Request (e.g. a Diameter CCR sent by PGW to indicate modification of an IP-CAN session) as defined in clauses 4.5.1, 4a.5.1 of 3GPP TS 29.212 [9] or clause 4.4 of 3GPP TS 29.214 [10]) is sent by the Client and received by the DRA (proxy). +- 2a If PA2 option is implemented, based on Client configuration and operator policy, the Client communicates directly to the PCRF, bypassing the DRA (proxy), by using the PCRF identity obtained through the Origin-Host AVP (see step 7 in clause 5.2.5.7.1.1). The Client uses the same active Session-Id AVP value on the Diameter Request sent to the PCRF. In such a case steps 2, 3, 4, 5, 6 are not carried out. +3. After receiving a Diameter Request (Step 2), the DRA (proxy) verifies that there is an active DRA binding for the session identified in the request. +4. The DRA (proxy) proxies the Diameter Request to the target PCRF. +5. PCRF-1 returns a Diameter Answer as defined in clauses 4.5, 4a.5 of 3GPP TS 29.212 [9] or clause 4.4 of 3GPP TS 29.214 [10]) to the DRA (proxy). +- 5a Upon receiving a Diameter Request (Step 2a), PCRF-1 returns a Diameter Answer directly to the Client, bypassing the DRA (proxy). +6. DRA (proxy) proxies the Diameter Answer to the Client. + +NOTE: Figure 7.4.1.2.1.1.1 is also applicable when the AF/BBERF/PCEF/TDF in the VPLMN modifies the Diameter session through the V-DRA. + +###### 7.4.1.2.1.2 PCEF-initiated + +Modification of Diameter sessions occur on PCEF initiated session modifications towards the clients (AF/BBERF/PCEF). + +If PA1 option is implemented, only steps 2, 3, 4, 5, 6 are carried out. If PA2 option is implemented, only steps 2a, 5a are carried out. + +![Sequence diagram showing the modification of Diameter sessions through DRA (proxy)- PCRF interaction. The diagram involves four lifelines: Client (AF/BBERF/PCEF), DRA (proxy), PCRF-1, and PCRF-2. The interaction starts with a 'Trigger' from PCRF-1 to PCRF-2. PCRF-2 sends a 'PCRF initiated Rx/Gx/Gxx Diameter Request' to PCRF-1. PCRF-1 then sends the same request to the DRA (proxy). The DRA (proxy) performs a 'Verify DRA Binding' step. It then proxies the request to the Client. The Client returns a 'Rx/Gx/Gxx Diameter Answer' to the DRA (proxy), which in turn proxies it back to PCRF-1. A 'Legend' box indicates that solid arrows represent 'Mandatory' messages and dashed arrows represent 'Conditional' messages. Two shaded regions labeled 'PA2' indicate optional paths where PCRF-1 communicates directly with the Client, bypassing the DRA (proxy).](8e80de0cac529b2c3775d677c5203133_img.jpg) + +Sequence diagram showing the modification of Diameter sessions through DRA (proxy)- PCRF interaction. The diagram involves four lifelines: Client (AF/BBERF/PCEF), DRA (proxy), PCRF-1, and PCRF-2. The interaction starts with a 'Trigger' from PCRF-1 to PCRF-2. PCRF-2 sends a 'PCRF initiated Rx/Gx/Gxx Diameter Request' to PCRF-1. PCRF-1 then sends the same request to the DRA (proxy). The DRA (proxy) performs a 'Verify DRA Binding' step. It then proxies the request to the Client. The Client returns a 'Rx/Gx/Gxx Diameter Answer' to the DRA (proxy), which in turn proxies it back to PCRF-1. A 'Legend' box indicates that solid arrows represent 'Mandatory' messages and dashed arrows represent 'Conditional' messages. Two shaded regions labeled 'PA2' indicate optional paths where PCRF-1 communicates directly with the Client, bypassing the DRA (proxy). + +**Figure 7.4.1.2.1.2.1: Modification of Diameter sessions through DRA (proxy)- PCRF interaction** + +1. PCRF receives an internal or external trigger that requires a Diameter message to be sent to the clients (either AF, BBERF, PCEF) +2. A PCRF-initiated Diameter Request (e.g. a Diameter RAR request sent to the PGW) is sent to the Clients and received by the DRA (proxy). +- 2a If PA2 option is implemented, the PCRF communicates directly to the client, bypassing the DRA (proxy). In such a case steps 2, 3, 4, 5, 6 are not carried out. +3. After receiving a Diameter Request (Step 2), the DRA (proxy) verifies that there is an active DRA binding for the session identified in the request. +4. The DRA (proxy) proxies the Diameter Request to the Client. The proxied Diameter Request maintains the same Session-Id AVP value. +5. Clients returns a Diameter Answer as defined in clauses 4.5, 4a.5 of 3GPP TS 29.212 [9] or clause 4.4 of 3GPP TS 29.214 [10]) to the DRA (proxy). +- 5a Upon receiving a Diameter Request (Step 2a), Client returns a Diameter Answer directly to the PCRF, bypassing the DRA (proxy). +6. DRA (proxy) proxies the Diameter Answer to the PCRF. + +NOTE: Figure 7.4.1.2.1.2.1 is also applicable when the V-PCRF modifies the Diameter session through the V-DRA. + +##### 7.4.1.2.2 Roaming cases + +###### 7.4.1.2.2.1 V-PCRF initiated + +In roaming scenarios modification of Diameter sessions may occur at any of the following cases: + +- V-PCRF S9 Diameter session modification to H-PCRF +- V-PCRF proxies Rx Diameter session modification to H-PCRF + +If PA1 option is implemented, only steps 2, 3, 4, 5, 6 are carried out. If PA2 option is implemented, only steps 2a, 5a are carried out. + +![Sequence diagram showing modification of Diameter sessions through DRA (proxy) on roaming scenarios – V-PCRF initiated. The diagram involves four lifelines: V-PCRF, H-DRA (proxy), H-PCRF-1, and H-PCRF-2. The sequence starts with a 'Trigger' (1) at V-PCRF. V-PCRF sends an 'Rx/S9 Diameter session update' (2) to H-DRA (proxy). A conditional path (dashed line) labeled '2a' shows V-PCRF sending the update directly to H-PCRF-1. H-DRA (proxy) performs 'Verify DRA Binding' (3) and then proxies the update (4) to H-PCRF-1. H-PCRF-1 returns an 'Rx/S9 Diameter Answer' (5) to H-DRA (proxy). A conditional path (dashed line) labeled '5a' shows H-PCRF-1 returning the answer directly to V-PCRF. Finally, H-DRA (proxy) proxies the answer (6) to V-PCRF. A legend indicates that solid arrows are 'Mandatory' and dashed arrows are 'Conditional'. Two light blue shaded regions are labeled 'PA2'.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +Sequence diagram showing modification of Diameter sessions through DRA (proxy) on roaming scenarios – V-PCRF initiated. The diagram involves four lifelines: V-PCRF, H-DRA (proxy), H-PCRF-1, and H-PCRF-2. The sequence starts with a 'Trigger' (1) at V-PCRF. V-PCRF sends an 'Rx/S9 Diameter session update' (2) to H-DRA (proxy). A conditional path (dashed line) labeled '2a' shows V-PCRF sending the update directly to H-PCRF-1. H-DRA (proxy) performs 'Verify DRA Binding' (3) and then proxies the update (4) to H-PCRF-1. H-PCRF-1 returns an 'Rx/S9 Diameter Answer' (5) to H-DRA (proxy). A conditional path (dashed line) labeled '5a' shows H-PCRF-1 returning the answer directly to V-PCRF. Finally, H-DRA (proxy) proxies the answer (6) to V-PCRF. A legend indicates that solid arrows are 'Mandatory' and dashed arrows are 'Conditional'. Two light blue shaded regions are labeled 'PA2'. + +**Figure 7.4.1.2.2.1.1: Modification of Diameter sessions through DRA (proxy) on roaming scenarios – V-PCRF initiated** + +1. V-PCRF receives an internal or external trigger that requires a Diameter message to be sent to H-PCRF over the S9 reference point +2. V-PCRF sends a Diameter session update (e.g. an S9 session modification request) over the S9 reference point that is received by the DRA (proxy) in the home PLMN. +- 2a If PA2 option is implemented, the V-PCRF communicates directly to the H-PCRF, bypassing the H-DRA (proxy). In such a case steps 2, 3, 4, 5, 6 are not carried out. +3. After receiving a Diameter Request (Step 2), the H-DRA (proxy) verifies that there is an active DRA binding for the session identified in the request. +4. The H-DRA (proxy) proxies the Diameter Request to the H-PCRF. The proxied Diameter Request maintains the same Session-Id AVP value. +5. H-PCRF returns a Diameter Answer to the H-DRA (proxy) in the home PLMN. +- 5a Upon receiving a Diameter Request (Step 2a), Client returns a Diameter Answer directly to the PCRF, bypassing the H-DRA (proxy). +6. H-DRA (proxy) proxies the Diameter Answer to the PCRF. + +###### 7.4.1.2.2.2 H-PCRF initiated + +In roaming scenarios modification of Diameter sessions may occur at any of the following cases: + +- H-PCRF S9 Diameter session modification to V-PCRF + +If PA1 option is implemented, only steps 2, 3, 4, 5, 6 are carried out. If PA2 option is implemented, only steps 2a, 5a are carried out. + +![Sequence diagram showing modification of Diameter sessions through DRA (proxy) on roaming scenarios – H-PCRF initiated. The diagram involves four entities: V-PCRF, H-DRA (proxy), H-PCRF-1, and H-PCRF-2. The sequence starts with H-PCRF-1 sending a 'Trigger' (1) to H-DRA (proxy). H-DRA (proxy) sends an 'S9 Diameter Request' (2) to H-PCRF-1. H-PCRF-1 then sends an 'S9 Diameter Request' (2a) to V-PCRF. H-DRA (proxy) performs a 'Verify DRA Binding' (3). H-DRA (proxy) sends a 'Proxy S9 Diameter Request' (4) to V-PCRF. V-PCRF returns an 'S9 Diameter Answer' (5) to H-DRA (proxy). H-DRA (proxy) then sends a 'Proxy S9 Diameter Answer' (6) to H-PCRF-1. A 'Legend' box indicates that solid arrows represent 'Mandatory' messages and dashed arrows represent 'Conditional' messages. The diagram is divided into two sections labeled PA2.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` + +sequenceDiagram + participant H-PCRF-1 + participant H-DRA as H-DRA (proxy) + participant V-PCRF + participant H-PCRF-2 + + Note left of H-PCRF-1: PA2 + H-PCRF-1->>H-DRA: 1. Trigger + H-DRA->>H-PCRF-1: 2. S9 Diameter Request + H-PCRF-1->>V-PCRF: 2a. S9 Diameter Request + Note right of H-DRA: 3. Verify DRA Binding + H-DRA->>V-PCRF: 4. Proxy S9 Diameter Request + V-PCRF->>H-DRA: 5. S9 Diameter Answer + Note left of H-PCRF-1: PA2 + V-PCRF->>H-PCRF-1: 5a. S9 Diameter Answer + H-DRA->>H-PCRF-1: 6. Proxy S9 Diameter Answer + + Note right of H-PCRF-2: Legend: + solid arrow --> Mandatory + dashed arrow --> Conditional + +``` + +Sequence diagram showing modification of Diameter sessions through DRA (proxy) on roaming scenarios – H-PCRF initiated. The diagram involves four entities: V-PCRF, H-DRA (proxy), H-PCRF-1, and H-PCRF-2. The sequence starts with H-PCRF-1 sending a 'Trigger' (1) to H-DRA (proxy). H-DRA (proxy) sends an 'S9 Diameter Request' (2) to H-PCRF-1. H-PCRF-1 then sends an 'S9 Diameter Request' (2a) to V-PCRF. H-DRA (proxy) performs a 'Verify DRA Binding' (3). H-DRA (proxy) sends a 'Proxy S9 Diameter Request' (4) to V-PCRF. V-PCRF returns an 'S9 Diameter Answer' (5) to H-DRA (proxy). H-DRA (proxy) then sends a 'Proxy S9 Diameter Answer' (6) to H-PCRF-1. A 'Legend' box indicates that solid arrows represent 'Mandatory' messages and dashed arrows represent 'Conditional' messages. The diagram is divided into two sections labeled PA2. + +**Figure 7.4.1.2.2.2.1: Modification of Diameter sessions through DRA (proxy) on roaming scenarios – H-PCRF initiated** + +1. H-PCRF receives an internal or external trigger that requires a Diameter message to be sent to V-PCRF over the S9 reference point. +2. H-PCRF sends a Diameter session update (e.g. an S9 session modification request) over the S9 reference point that is received by the H-DRA (proxy) in the home PLMN. +- 2a If PA2 option is implemented, the H-PCRF communicates directly to the V-PCRF, bypassing the H-DRA (proxy). In such a case steps 2, 3, 4, 5, 6 are not carried out. +3. After receiving a Diameter Request (Step 2), the H-DRA (proxy) verifies that there is an active DRA binding for the session identified in the request. +4. The H-DRA (proxy) proxies the Diameter Request to the V-PCRF. The proxied Diameter Request maintains the same Session-Id AVP value. +5. V-PCRF returns a Diameter Answer to the H-DRA (proxy) in the home PLMN. +- 5a Upon receiving a Diameter Request (Step 2a), V-PCRF returns a Diameter Answer directly to the H-PCRF, bypassing the H-DRA (proxy). +6. H-DRA (proxy) proxies the Diameter Answer to the H-PCRF. + +#### 7.4.1.3 Termination of Diameter Sessions + +##### 7.4.1.3.1 Non-roaming cases + +The procedures required are identical for both PA1 and PA2 options + +Termination of Diameter sessions occur at the following cases: + +- Gateway control session termination +- IP-CAN session termination +- AF session termination +- For unsolicited application reporting, TDF session termination + +![Sequence diagram showing the termination of Diameter sessions through a DRA (proxy). The diagram involves four main entities: Client (AF/BBERF/PCEF/TDF), DRA (proxy), PCRF-1, and PCRF-2. The sequence of messages is: 1. External trigger to Client; 2. Rx/Gx/Gxx/Sd Diameter Termination Request from Client to DRA; 3. Verify DRA binding (conditional) from DRA; 4. Proxy Rx/Gx/Gxx/Sd Diameter Termination Request from DRA to PCRF-1; 5. Rx/Gx/Gxx/Sd Diameter Answer from PCRF-1 to DRA; 6. Remove DRA binding (conditional) from DRA; 7. Proxy Rx/Gx/Gxx/Sd Diameter Answer from DRA to Client. A legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +sequenceDiagram + participant Client as Client (AF/BBERF/PCEF/TDF) + participant DRA as DRA (proxy) + participant PCRF1 as PCRF-1 + participant PCRF2 as PCRF-2 + + Note left of Client: 1. External trigger + Client->>DRA: 2. Rx/Gx/Gxx/Sd Diameter Termination Request + Note right of DRA: 3. Verify DRA binding + DRA->>PCRF1: 4. Proxy Rx/Gx/Gxx/Sd Diameter Termination Request + PCRF1-->>DRA: 5. Rx/Gx/Gxx/Sd Diameter Answer + Note right of DRA: 6. Remove DRA binding + DRA-->>Client: 7. Proxy Rx/Gx/Gxx/Sd Diameter Answer + + Note right of PCRF2: Legend: + Note right of PCRF2: --> Mandatory + Note right of PCRF2: -.-> Conditional + +``` + +Sequence diagram showing the termination of Diameter sessions through a DRA (proxy). The diagram involves four main entities: Client (AF/BBERF/PCEF/TDF), DRA (proxy), PCRF-1, and PCRF-2. The sequence of messages is: 1. External trigger to Client; 2. Rx/Gx/Gxx/Sd Diameter Termination Request from Client to DRA; 3. Verify DRA binding (conditional) from DRA; 4. Proxy Rx/Gx/Gxx/Sd Diameter Termination Request from DRA to PCRF-1; 5. Rx/Gx/Gxx/Sd Diameter Answer from PCRF-1 to DRA; 6. Remove DRA binding (conditional) from DRA; 7. Proxy Rx/Gx/Gxx/Sd Diameter Answer from DRA to Client. A legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages. + +**Figure 7.4.1.3.1.1: Termination of Diameter sessions through DRA (proxy)** + +1. A Client receives an external trigger (e.g. an IP-CAN session termination is initiated by the UE or PCRF) that requires the sending of a Diameter Termination Request. +2. A Diameter Termination Request (e.g., a Diameter CCR sent by PGW to indicate termination of an IP-CAN session) as defined in clauses 4.5, 4a.5 of 3GPP TS 29.212 [9]) is sent by the Client to the DRA (proxy). The message uses the same Session-Id AVP value of the active Diameter session established between the Client and PCRF-1. +3. The DRA (proxy) verifies that there is an active DRA binding for the IP-CAN session based on the Session-Id AVP in the request. +4. The DRA (proxy) proxies the Diameter Termination Request to the target PCRF. The proxied Diameter Request maintains the same Session-Id AVP value. +5. PCRF-1 acknowledges termination of the session. PCRF-1 sends a Diameter Answer, (e.g., as defined in clauses 4.5, 4a.5 of 3GPP TS 29.212 [9]) to DRA (proxy). +6. The DRA marks the Diameter session terminated. If the DRA binding is per IP-CAN session and all the Diameter sessions (i.e. the Gx session or the Gxx session) of the IP-CAN session are terminated or if the DRA binding is per UE and all the Diameter sessions (i.e. the Gx session or the Gxx session) of that UE are terminated the DRA (proxy) removes the DRA binding. +7. DRA (proxy) proxies the Diameter Answer to the Client. The proxied Diameter Answer maintains the same Session-Id AVP value. + +NOTE 1: Figure 7.4.1.3.1.1 is also applicable when the AF/BBERF/PCEF/TDF in the VPLMN terminates the Diameter sessions through the V-DRA. + +NOTE 2: AF/TDF is not required to send Diameter session termination request to DRA (PA2). + +##### 7.4.1.3.2 Roaming cases + +In roaming cases (over S9 reference point) termination of Diameter sessions occur at the following cases: + +- S9 session termination +- AF session termination + +![Sequence diagram illustrating the termination of Diameter sessions through H-DRA (proxy) in roaming cases. The diagram shows four lifelines: V-PCRF, H-DRA (proxy), H-PCRF-1, and H-PCRF-2. The sequence of messages is: 1. External trigger (solid arrow) to V-PCRF; 2. S9/Rx Diameter Termination Request (solid arrow) from V-PCRF to H-DRA (proxy); 3. Verify DRA binding (dashed arrow) from H-DRA (proxy) to itself; 4. Proxy S9/Rx Diameter Termination Request (solid arrow) from H-DRA (proxy) to H-PCRF-1; 5. S9/Rx Diameter Answer (solid arrow) from H-PCRF-1 to H-DRA (proxy); 6. Remove DRA binding (dashed arrow) from H-DRA (proxy) to itself; 7. Proxy S9/Rx Diameter Answer (solid arrow) from H-DRA (proxy) to V-PCRF. A legend indicates that solid arrows represent 'Mandatory' messages and dashed arrows represent 'Conditional' messages.](68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg) + +Sequence diagram illustrating the termination of Diameter sessions through H-DRA (proxy) in roaming cases. The diagram shows four lifelines: V-PCRF, H-DRA (proxy), H-PCRF-1, and H-PCRF-2. The sequence of messages is: 1. External trigger (solid arrow) to V-PCRF; 2. S9/Rx Diameter Termination Request (solid arrow) from V-PCRF to H-DRA (proxy); 3. Verify DRA binding (dashed arrow) from H-DRA (proxy) to itself; 4. Proxy S9/Rx Diameter Termination Request (solid arrow) from H-DRA (proxy) to H-PCRF-1; 5. S9/Rx Diameter Answer (solid arrow) from H-PCRF-1 to H-DRA (proxy); 6. Remove DRA binding (dashed arrow) from H-DRA (proxy) to itself; 7. Proxy S9/Rx Diameter Answer (solid arrow) from H-DRA (proxy) to V-PCRF. A legend indicates that solid arrows represent 'Mandatory' messages and dashed arrows represent 'Conditional' messages. + +**Figure 7.4.1.3.2.1: Termination of Diameter sessions through H-DRA (proxy) – Roaming cases** + +1. The V-PCRF receives an external trigger (e.g., session termination request from the BBERF or the PCEF) that requires the sending of a Diameter Termination Request. +2. A Diameter Termination Request (e.g., an S9 termination request) is sent by the V-PCRF and received by the H-DRA (proxy) in the home PLMN. The message uses the same Session-Id AVP value of the active Diameter session established between V-PCRF and H-PCRF-1. +3. The H-DRA (proxy) verifies that there is an active DRA binding for the IP-CAN session based on the Session-Id AVP in the request. +4. The H-DRA (proxy) proxies the Diameter Termination Request to the target H-PCRF-1. The proxied Diameter Request maintains the same Session-Id AVP value. +5. H-PCRF-1 acknowledges termination of the session. H-PCRF-1 sends a Diameter Answer to H-DRA (proxy) in the home PLMN. +6. The H-DRA marks the Diameter session terminated. If all the Diameter sessions (i.e. the S9 session, the Gxx session, and the Gx session) of that UE are terminated the H-DRA (proxy) removes the DRA binding. +7. H-DRA (proxy) proxies the Diameter Answer to the V-PCRF. The proxied Diameter Answer maintains the same Session-Id AVP value. + +NOTE: V-PCRF does not need to send Rx Diameter termination messages to proxy H-DRA (PA2 option) since Rx Diameter termination messages do not affect the DRA binding. + +### 7.4.2 Redirect DRA + +#### 7.4.2.1 Establishment of Diameter Sessions + +##### 7.4.2.1.1 Non-roaming cases + +Establishment of Diameter sessions may occur at the following cases: + +- Gateway control session establishment +- IP-CAN session establishment + +- AF session establishment +- For unsolicited application reporting, TDF session establishment + +The DRA client (AF/BBERF/PCEF/TDF) shall follow the procedure below if an appropriate cached route table entry created from previous DRA (redirect) interactions does not exist. Cached route table entries are created from the Redirect-Host, Redirect-Host-Usage and Redirect-Max-Cache-Time AVPs as described in sections 6.12, 6.13 and 6.14 of IETF RFC 6733 [61]. + +![Sequence diagram showing the establishment of a Diameter session through DRA (redirect). The diagram involves four main entities: Client (AF/BBERF/PCEF/TDF), DRA (redirect), PCRF-1, and PCRF-2. The process starts with an external trigger to the Client. The Client sends a Diameter Establishment Request to the DRA. The DRA performs a binding creation/retrieval. The DRA sends a Diameter Answer (redirect) to the Client. The Client then re-sends the Diameter Establishment Request to PCRF-1. PCRF-1 sends a Diameter Answer back to the Client. A legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages.](6d6670b8e65d3ff8126e5ab9aeaffbd8_img.jpg) + +``` + +sequenceDiagram + participant Client as Client (AF/BBERF/PCEF/TDF) + participant DRA as DRA (redirect) + participant PCRF1 as PCRF-1 + participant PCRF2 as PCRF-2 + + Note left of Client: 1. External trigger + Client->>DRA: 2. Rx/Gx/Gxx/Sd Diameter Establishment Request + Note right of DRA: 3. DRA binding creation/retrieval + DRA-->>Client: 4. Diameter Answer (redirect) + Client->>PCRF1: 5. Rx/Gx/Gxx/Sd Diameter Establishment Request + PCRF1-->>Client: 6. Rx/Gx/Gxx/Sd Diameter Answer + +``` + +Sequence diagram showing the establishment of a Diameter session through DRA (redirect). The diagram involves four main entities: Client (AF/BBERF/PCEF/TDF), DRA (redirect), PCRF-1, and PCRF-2. The process starts with an external trigger to the Client. The Client sends a Diameter Establishment Request to the DRA. The DRA performs a binding creation/retrieval. The DRA sends a Diameter Answer (redirect) to the Client. The Client then re-sends the Diameter Establishment Request to PCRF-1. PCRF-1 sends a Diameter Answer back to the Client. A legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages. + +**Figure 7.4.2.1.1.1: Establishment of Diameter session through DRA (redirect)** + +1. A Client receives an external trigger (e.g., IP-CAN session establishment request) that requires the establishment of a Diameter session with a PCRF. +2. A Diameter Establishment request (e.g., a Diameter CCR sent by PGW to indicate establishment of an IP-CAN session as defined in clauses 4.5.1, 4a.5.1 of 3GPP TS 29.212 [9]) with user information (e.g., UE-NAI) is sent by the Client and received by the DRA (redirect). +3. The DRA (redirect) stores the user information (e.g., UE-NAI) and checks whether an active DRA binding exists. If not the DRA creates a dynamic DRA binding (assignment of a PCRF node per UE or per IP-CAN session); if the DRA (redirect) find there has been a DRA binding for the user, the DRA shall select the PCRF from the binding for the client. +4. The DRA (redirect) sends a Diameter Answer indicating redirection as defined in IETF RFC 6733 [61]. The target PCRF identity is included in the Redirect-Host AVP. +5. The Client re-sends the Diameter Establishment Request of step 2 to the target PCRF. +6. PCRF-1 returns a Diameter Answer, as defined in clauses 4.5, 4a.5 of 3GPP TS 29.212 [9], to the Client. + +NOTE: Figure 7.4.2.1.1.1 is also applicable when the AF/BBERF/PCEF/TDF in the VPLMN contacts the V-DRA to locate the V-PCRF. + +##### 7.4.2.1.2 Roaming cases + +Establishment of Diameter sessions may occur at the following cases: + +- S9 session availability +- AF session establishment + +The DRA client (AF/BBERF/PCEF) shall follow the procedure below if an appropriate cached route table entry created from previous DRA (redirect) interactions does not exist. Cached route table entries are created from the Redirect-Host, Redirect-Host-Usage and Redirect-Max-Cache-Time AVPs as described in clause 6.12, 6.13 and 6.14 of IETF RFC 6733 [61]. + +![Sequence diagram showing the establishment of a Diameter session through DRA (redirect) in a roaming scenario. The diagram involves four main entities: V-PCRF, H-DRA (redirect), H-PCRF-1, and H-PCRF-2. The sequence of messages is: 1. External trigger to V-PCRF; 2. Rx/S9 Diameter Establishment Request from V-PCRF to H-DRA; 3. DRA binding creation/retrieval at H-DRA; 4. Diameter Answer (redirect) from H-DRA to V-PCRF; 5. Rx/S9 Diameter Establishment Request from V-PCRF to H-PCRF-1; 6. Rx/S9 Diameter Answer from H-PCRF-1 to V-PCRF. A legend indicates that solid arrows represent 'Mandatory' messages and dashed arrows represent 'Conditional' messages.](163688ca8da9787f5d48edd68d8cc75b_img.jpg) + +``` + +sequenceDiagram + participant External + participant V-PCRF + participant H-DRA as H-DRA (redirect) + participant H-PCRF-1 + participant H-PCRF-2 + + Note right of H-PCRF-2: Legend: + + -->> Mandatory + + -.->> Conditional + + External->> V-PCRF: 1. External trigger + V-PCRF->> H-DRA: 2. Rx/S9 Diameter Establishment Request + Note right of H-DRA: 3. DRA binding creation/retrieval + H-DRA-->> V-PCRF: 4. Diameter Answer (redirect) + V-PCRF->> H-PCRF-1: 5. Rx/S9 Diameter Establishment Request + H-PCRF-1-->> V-PCRF: 6. Rx/S9 Diameter Answer + +``` + +Sequence diagram showing the establishment of a Diameter session through DRA (redirect) in a roaming scenario. The diagram involves four main entities: V-PCRF, H-DRA (redirect), H-PCRF-1, and H-PCRF-2. The sequence of messages is: 1. External trigger to V-PCRF; 2. Rx/S9 Diameter Establishment Request from V-PCRF to H-DRA; 3. DRA binding creation/retrieval at H-DRA; 4. Diameter Answer (redirect) from H-DRA to V-PCRF; 5. Rx/S9 Diameter Establishment Request from V-PCRF to H-PCRF-1; 6. Rx/S9 Diameter Answer from H-PCRF-1 to V-PCRF. A legend indicates that solid arrows represent 'Mandatory' messages and dashed arrows represent 'Conditional' messages. + +**Figure 7.4.2.1.2.1: Establishment of Diameter session through DRA (redirect) – Roaming scenario** + +1. The V-PCRF receives an external trigger (e.g., IP-CAN session establishment request) that requires the establishment of a Diameter session with an H-PCRF over the S9 reference point. +2. A Rx/S9 Diameter Establishment Request with user information (e.g., UE-NAI) is sent by the V-PCRF and received by the H-DRA (redirect) in the home PLMN. +3. The H-DRA (redirect) stores the user information (e.g., UE-NAI) and checks whether an active DRA binding exists. If not the H-DRA creates a dynamic DRA binding (assignment of a PCRF node per UE); if the DRA (redirect) find there has been a DRA binding for the user, the DRA shall select the PCRF from the binding for the client. +4. The H-DRA (redirect) sends a Diameter Answer indicating redirection as defined in IETF RFC 6733 [61]. The target PCRF identity is included in the Redirect-Host AVP. +5. The V-PCRF re-sends the Rx/S9 Diameter Establishment Request of step 2 to the target H-PCRF. +6. H-PCRF-1 returns a corresponding Diameter Answer to the V-PCRF. + +NOTE: The V-PCRF may proxy the Rx Diameter Establishment Request to the H-PCRF directly (e.g. based on the stored information provided by H-DRA during the S9 Diameter session establishment). + +#### 7.4.2.2 Modification of Diameter sessions + +The PCEF shall send the Diameter session modification message to the DRA to update the DRA binding information only if the UE's address(es) is updated and the DRA (redirect) is maintaining PCRF routing information per IP-CAN session. For visited access case, the V-PCRF shall send the Diameter session modification message to the H-DRA to update the DRA binding information only if the UE's address(es) is updated. The detailed procedure is similar to the Establishment of Diameter sessions, which is described in the clause 7.4.2.1. + +#### 7.4.2.3 Termination of Diameter Sessions + +##### 7.4.2.3.1 Non-roaming cases + +Termination of Diameter sessions that impact the DRA binding occur at the following cases: + +- Gateway control session termination +- IP-CAN session termination + +The DRA client (BBERF/PCEF) shall follow the procedure below if the DRA (redirect) is maintaining PCRF routing information per IP-CAN session or an appropriate cached route table entry created from previous DRA (redirect) interactions does not exist. Cached route table entries are created from the Redirect-Host, Redirect-Host-Usage and Redirect-Max-Cache-Time AVPs as described in clause 6.12, 6.13 and 6.14 of IETF RFC 6733 [61]. + +![Sequence diagram showing the termination of Diameter sessions through DRA (redirect). The diagram involves four entities: Client (BBERF/PCEF), DRA (redirect), PCRF-1, and PCRF-2. The process starts with an external trigger to the Client. The Client sends a Gx/Gxx Diameter Termination Request to the DRA (step 2) and another to PCRF-1 (step 3). The DRA performs a binding verification/release (step 4) and sends a Diameter Redirect Answer to the Client (step 5). Finally, PCRF-1 sends a Gx/Gxx Diameter Answer to the Client (step 6). A legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages.](6324b252294c0f5d4e34dad4a1202075_img.jpg) + +``` + +sequenceDiagram + participant Client as Client (BBERF/PCEF) + participant DRA as DRA (redirect) + participant PCRF1 as PCRF-1 + participant PCRF2 as PCRF-2 + + Note left of Client: 1. External trigger + Client->>DRA: 2. Gx/Gxx Diameter Termination Request + Client->>PCRF1: 3. Gx/Gxx Diameter Termination Request + Note right of DRA: 4. DRA binding verification/release + DRA-->>Client: 5. Diameter Redirect Answer + PCRF1-->>Client: 6. Gx/Gxx Diameter Answer + +``` + +Sequence diagram showing the termination of Diameter sessions through DRA (redirect). The diagram involves four entities: Client (BBERF/PCEF), DRA (redirect), PCRF-1, and PCRF-2. The process starts with an external trigger to the Client. The Client sends a Gx/Gxx Diameter Termination Request to the DRA (step 2) and another to PCRF-1 (step 3). The DRA performs a binding verification/release (step 4) and sends a Diameter Redirect Answer to the Client (step 5). Finally, PCRF-1 sends a Gx/Gxx Diameter Answer to the Client (step 6). A legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages. + +**Figure 7.4.2.3.1.1: Termination of Diameter sessions through DRA (redirect)** + +1. Client receives an external trigger (e.g. an IP-CAN session termination is initiated by the UE or PCRF) that triggers the client to terminate Diameter session with server (i.e. PCRF) +- 2 A Diameter Termination Request (e.g., as defined in clauses 4.5.7 (Gx) and 4a.5.3 (Gxx) of 3GPP TS 29.212 [9]) is sent by the Client to the DRA (redirect). +3. A Diameter Termination Request (e.g., as defined in clauses 4.5.7 (Gx) and 4a.5.3 (Gxx) of 3GPP TS 29.212 [9]) is sent by the Client to PCRF-1. The message uses the same Session-Id AVP value of the active Diameter session established between the Client and PCRF-1. + +NOTE: Steps 2, 3 may be carried out in parallel. Otherwise, the client after step 2 may need to wait for the redirect answer before sending the Diameter termination request to the PCRF. + +4. DRA (redirect) verifies that there is an active DRA binding for the IP-CAN session based on the Session-Id AVP and marks the Diameter session terminated. If the DRA binding is per IP-CAN session and all the Diameter sessions (i.e. Gx session or Gxx session) of that IP-CAN session are terminated or if the DRA binding is per UE and all the Diameter sessions (i.e. Gx session or Gxx session) of that UE are terminated the DRA removes the DRA binding. +- 5 DRA (redirect) acknowledges termination of the session by sending a Diameter redirect answer to the client. +- 6 PCRF-1 acknowledges termination of session. PCRF-1 sends a Diameter Answer (e.g., as defined in clauses 4.5.7 (Gx) and 4a.5.3 (Gxx) of 3GPP TS 29.212 [9]) to the Client. + +**NOTE:** Figure 7.4.2.3.1.1 is also applicable when the BBERF/PCEF in the VPLMN terminates the Diameter sessions through the V-DRA. + +##### 7.4.2.3.2 Roaming cases + +Termination of Diameter sessions occur at the following cases: + +- S9 session termination + +The DRA client (AF/BBERF/PCEF) shall follow the procedure below) if the DRA (redirect) is maintaining PCRF routing information per IP-CAN session or an appropriate cached route table entry created from previous DRA (redirect) interactions does not exist. Cached route table entries are created from the Redirect-Host, Redirect-Host-Usage and Redirect-Max-Cache-Time AVPs as described in clause 6.12, 6.13 and 6.14 of IETF RFC 6733 [61]. + +![Sequence diagram showing the termination of Diameter sessions through DRA (redirect) in a roaming case. Lifelines: V-PCRF, H-DRA (redirect), H-PCRF-1, H-PCRF-2. 1. External trigger at V-PCRF. 2. V-PCRF sends S9 Diameter Termination Request to H-DRA. 3. V-PCRF sends S9 Diameter Termination Request to H-PCRF-1. 4. H-DRA performs DRA binding verification/release. 5. H-DRA sends Diameter Redirect Answer to V-PCRF. 6. H-PCRF-1 sends S9 Diameter Answer to V-PCRF.](d980a3f9608055996a07f31788baf827_img.jpg) + +``` + +sequenceDiagram + participant V-PCRF + participant H-DRA as H-DRA (redirect) + participant H-PCRF-1 + participant H-PCRF-2 + + Note left of V-PCRF: 1. External trigger + V-PCRF->>H-DRA: 2. S9 Diameter Termination Request + V-PCRF->>H-PCRF-1: 3. S9 Diameter Termination Request + Note over H-DRA: 4. DRA binding verification/release + H-DRA->>V-PCRF: 5. Diameter Redirect Answer + H-PCRF-1->>V-PCRF: 6. S9 Diameter Answer + +``` + +**Legend:** + → Mandatory + - - → Conditional + +Sequence diagram showing the termination of Diameter sessions through DRA (redirect) in a roaming case. Lifelines: V-PCRF, H-DRA (redirect), H-PCRF-1, H-PCRF-2. 1. External trigger at V-PCRF. 2. V-PCRF sends S9 Diameter Termination Request to H-DRA. 3. V-PCRF sends S9 Diameter Termination Request to H-PCRF-1. 4. H-DRA performs DRA binding verification/release. 5. H-DRA sends Diameter Redirect Answer to V-PCRF. 6. H-PCRF-1 sends S9 Diameter Answer to V-PCRF. + +**Figure 7.4.2.3.2.1: Termination of Diameter sessions through DRA (redirect) – Roaming case** + +1. V-PCRF receives an external trigger (e.g. session termination request from the BBERF, PCEF) that requires the sending of a Diameter Termination Reqeust. +- 2 A Diameter Termination Request is sent by the V-PCRF and received by the H-DRA (redirect) in the home PLMN. +3. A Diameter Termination Request is sent by the V-PCRF to H-PCRF-1. The message uses the same Session-Id AVP value of the active Diameter session established between theV-PCRF and H-PCRF-1. + +**NOTE:** Steps 2, 3 may be carried out in parallel. Otherwise, the V-PCRF after step2 may need to wait for the redirect answer before sending the Diameter termination request to the H-PCRF + +4. H-DRA (redirect) verifies that there is an active DRA binding for the IP-CAN session based on the Session-Id AVP and marks the Diameter session terminated. If all the Diameter sessions (i.e. S9 session, Gxx session, Gx session) of that UE are terminated the H-DRA removes the DRA binding. +- 5 H-DRA (redirect) acknowledges termination of the session by sending a Diameter redirect answer to the V-PCRF. +- 6 H-PCRF-1 acknowledges termination of the session by sending a Diameter answer to the V-PCRF. + +**NOTE:** Rx Diameter termination messages are not required to be sent to H-DRA (redirect) since such messages do not affect the DRA binding + +# 8 Diameter race condition handling + +## 8.1 Overview + +Certain Diameter PCC applications (Gx, Gxx, Sd, S9) allow the server (PCRF for Gx, Gxx, Sd, H-PCRF for S9) to update a session in two ways: unsolicited and solicited. The PCRF can push policy decisions and provision event triggers in an unsolicited fashion using an RAR. It can also install policy decisions in a solicited manner by responding to a CCR sent by the client (BBERF for Gxx, PCEF for Gx, TDF for Sd, V-PCRF for S9). + +The client and the server can initiate transactions that modify the state of the session independently (e.g. CCR from the client and RAR from the server) and potentially concurrently. Additionally, there may be Diameter agents in between the client and server (e.g. DRA or in general Diameter relays/proxies) that could cause messages to be delivered out of order. This can lead to race conditions that may result in the wrong information maintained by the client and/or server for a session. + +Note that race conditions occur in different ways based on the application. Also, their impact is specific to the application. For example, even though Gx is based on DCCA (RFC 4006), Gx is much more vulnerable to race conditions as Gx allows sessions to be updated based on RARs and CCAs whereas DCCA only allows the server to update the session based on a CCA. The RAR is merely used to solicit the client to send a CCR. + +## 8.2 Procedures for Gx, Gxx, Sd and S9 + +This clause describes the optional procedures for handling Diameter race conditions in a deterministic manner for the following interfaces: Gx, Gxx, Sd and S9. These procedures apply to the PCEF (Gx), BBERF (Gxx), TDF (Sd) and PCRF (Gx, Gxx, Sd and S9). + +In this clause, the terms “client” and “server” are relative to the session context. As an example, for the Gx interface, the client is the PCEF and the server is the PCRF. The term “node” can refer to either a client or a server. The term “transaction” refers to a Diameter request and its associated answer. The term “ongoing transaction” refers to a transaction that has an outstanding answer. + +A node that supports the procedures defined in this clause and is configured to comply with them, shall advertise such support by setting the corresponding PendingTransaction feature bit in the Supported-Features AVP during session establishment as defined in 3GPP TS 29.212 [9] for Gx, Gxx and Sd and 3GPP TS 29.215 [22] for S9. + +On receipt of a Diameter request for an existing Diameter session, the recipient Diameter node shall check if it has an ongoing transaction on that session: + +1. If there are no ongoing transactions on the session, the node shall process the incoming request normally. +2. If there is an ongoing transaction on the session and optionally, if the recipient node cannot determine that the incoming request can be safely handled without creating a state mismatch: + - a. The client shall reject the incoming request with a Diameter experimental result code of DIAMETER\_PENDING\_TRANSACTION as defined in 3GPP TS 29.212 [9]. + - b. The server shall either reject the incoming request with a Diameter experimental result code of DIAMETER\_PENDING\_TRANSACTION or shall wait for one of the following conditions to occur: + - i. The ongoing transaction completes. In this case, the session is updated at the server based on the completion of the ongoing transaction and afterwards, the incoming request (e.g. CCR) is processed normally based on the updated session state. + - ii. The waiting period has exceeded its allotted time. In this case, the server shall reject the incoming request with a Diameter experimental result code of DIAMETER\_PENDING\_TRANSACTION. + +NOTE 1: If there is an ongoing transaction on the session and optionally, if the recipient node can determine that the incoming request can be safely handled without creating a state mismatch, the client and the server could handle the incoming request normally. + +3. On receipt of a DIAMETER\_PENDING\_TRANSACTION result code, a client shall retry the request. On the other hand, if a server had rejected a request from the client with a DIAMETER\_PENDING\_TRANSACTION, the server should not retry the failed request until it responds to the re-attempted request from the client. This is to avoid having both the client and server concurrently retry their requests. In all other cases, if the session on the client still needs to be updated, the server shall retry the request. + +NOTE 2: The server retries the request either by resending the command (e.g. RAR) or by including the initial requested information in the command (e.g. CCA) answering the re-attempted request from the client. However, including the initial requested information in the command (e.g. CCA) answering the re-attempted request is only possible if the server does not require a response to the command. + +4. Nodes should limit the number of times they re-attempt the same request due to receipt of a DIAMETER\_PENDING\_TRANSACTION. +5. The only exception to the rules above is a session termination request (e.g. CCR with a CC-Request-Type AVP set to TERMINATION\_REQUEST) or a request for session release (e.g. RAR with Session-Release-Cause AVP). In both cases, the request should be handled as follows: + - a. When receiving a request for a session release that requires new transactions to be initiated, a client shall acknowledge the request immediately (e.g. a RAR command with Session-Release-Cause AVP shall be acknowledged with a RAA command). The client shall wait for the current transaction to complete (either by the server acknowledging the request or rejecting it with DIAMETER\_PENDING\_TRANSACTION) before completing the session termination procedure (e.g. before sending the CCR command with the CC-Request-Type set to TERMINATION\_REQUEST). + +NOTE 3: The client needs to wait for the outcome of the session modification to determine if the session termination procedure will be used to report information that could not be reported as part of the session modification procedure. + +NOTE 4: After having sent a request for session termination, the server acknowledges any unrelated incoming request immediately (either by the server acknowledging the request or rejecting it with DIAMETER\_PENDING\_TRANSACTION) without a waiting period. + +- b. When receiving a session termination request the server shall handle it immediately. + +# --- Annex A (informative): Examples of deriving the Maximum Authorized parameters from the SDP parameters + +# --- Annex B (normative): Signalling Flows for IMS + +The signalling flows in clause 4 are also applicable for IMS. This Annex adds flows that show interactions with SIP/SDP signalling of the IMS. + +## --- B.0 General + +The following is applicable for Emergency Services and PSAP call back request: + +- The P-CSCF includes an Emergency indication when service information is sent over Rx and when required by the IMS deployment, the P-CSCF may also indicate that it requires EPC-level user information as defined in 3GPP TS 29.214 [10]. +- The PCRF only allows Emergency Sessions that are bound to an IP-CAN session established to an Emergency APN. +- Upon request from the P-CSCF, the PCRF provides the P-CSCF with EPC-level user information corresponding to the established IP-CAN session. + +The following is not applicable for Emergency Services and PSAP call back request: + +- Pre-authorization for a UE terminated IMS session establishment with UE initiated resource reservation. +- Subscription to notification of Signalling Path Status at IMS Registration, subscription to notification of changes of IP-CAN type at IMS Registration and Provisioning of SIP Signalling flow information at IMS Registration procedures. + +### --- B.1 Subscription to Notification of Signalling Path Status at IMS Registration + +This clause covers the optional Subscription to Notifications of IMS Signalling Path Status upon an initial successful IMS Registration procedure. + +![Sequence diagram showing the subscription to notification of IMS signaling path status at initial IMS registration. The diagram involves three entities: UE, PCRF, and P-CSCF. The sequence of messages is: 1. SIP REGISTER (UE to P-CSCF), 2. SIP REGISTER (P-CSCF to external), 3. 200 OK (external to P-CSCF), 4. 200 OK (P-CSCF to UE), 5. Diameter AAR (P-CSCF to PCRF), 6. Session Binding (PCRF internal), 7. Diameter AAA (PCRF to P-CSCF), 8. Subscribe to Bearer Level Event (PCRF internal, optional). A legend indicates that solid arrows are mandatory and dashed arrows are optional. Solid arrow Dashed arrow](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PCRF + participant P-CSCF + + UE->>P-CSCF: 1. SIP REGISTER + P-CSCF->>External: 2. SIP REGISTER + External->>P-CSCF: 3. 200 OK + P-CSCF->>UE: 4. 200 OK + P-CSCF->>PCRF: 5. Diameter AAR + Note over PCRF: 6. Session Binding + PCRF->>P-CSCF: 7. Diameter AAA + Note over PCRF: 8. Subscribe to Bearer Level Event + +``` + +Legend: + +Mandatory + Optional + +Sequence diagram showing the subscription to notification of IMS signaling path status at initial IMS registration. The diagram involves three entities: UE, PCRF, and P-CSCF. The sequence of messages is: 1. SIP REGISTER (UE to P-CSCF), 2. SIP REGISTER (P-CSCF to external), 3. 200 OK (external to P-CSCF), 4. 200 OK (P-CSCF to UE), 5. Diameter AAR (P-CSCF to PCRF), 6. Session Binding (PCRF internal), 7. Diameter AAA (PCRF to P-CSCF), 8. Subscribe to Bearer Level Event (PCRF internal, optional). A legend indicates that solid arrows are mandatory and dashed arrows are optional. Solid arrow Dashed arrow + +**Figure B.1.1: Subscription to Notification of IMS Signaling Path Status at initial IMS Registration** + +- 1-4. The user initiates an initial SIP Registration procedure. The SIP Registration procedure is completed successfully (user has been authenticated and registered within the IMS Core NW). +5. The P-CSCF requests the establishment of a new Diameter Rx session with the intention to subscribe to the status of the IMS Signaling path. The P-CSCF sends a Diameter AAR command to the PCRF. +6. The PCRF performs session binding and identifies corresponding PCC Rules related to IMS Signalling. +7. The PCRF confirms the subscription to IMS Signaling path status and replies with a Diameter AAA command back to the P-CSCF. +8. If the PCRF had not previously subscribed to the required bearer level events from the IP-CAN for the affected PCC/QoS Rules, then the PCRF shall do so now. The PCRF initiates procedures according to figure 4.3.1.1.1. + +#### B.1a Subscription to Notification of Change of IP-CAN Type at IMS Registration + +This clause covers the optional Subscription to Notifications of change in the type of IP-CAN upon an initial IMS Registration procedure. + +![Sequence diagram showing the subscription to notification of change of IP-CAN Type at initial IMS Registration. The diagram involves three main entities: UE, PCRF, and P-CSCF. The sequence of messages is: 1. SIP REGISTER (UE to P-CSCF), 2. Diameter AAR (P-CSCF to PCRF), 3. Session Binding (internal PCRF process), 4. Diameter AAA (PCRF to P-CSCF), 5. SIP REGISTER (P-CSCF to external server), 6. 200 OK (external server to P-CSCF), 7. 200 OK (P-CSCF to UE), and 8. Subscribe to Bearer Level Event (PCRF to P-CSCF, optional). A legend indicates that solid arrows represent mandatory messages and dashed arrows represent optional messages.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PCRF + participant P-CSCF + + UE->>P-CSCF: 1. SIP REGISTER + P-CSCF->>PCRF: 2. Diameter AAR + Note over PCRF: 3. Session Binding + PCRF->>P-CSCF: 4. Diameter AAA + P-CSCF->>External: 5. SIP REGISTER + External-->>P-CSCF: 6. 200 OK + P-CSCF-->>UE: 7. 200 OK + PCRF-->>P-CSCF: 8. Subscribe to Bearer Level Event + +``` + +Legend: + +- > Mandatory +- - - -> Optional + +Sequence diagram showing the subscription to notification of change of IP-CAN Type at initial IMS Registration. The diagram involves three main entities: UE, PCRF, and P-CSCF. The sequence of messages is: 1. SIP REGISTER (UE to P-CSCF), 2. Diameter AAR (P-CSCF to PCRF), 3. Session Binding (internal PCRF process), 4. Diameter AAA (PCRF to P-CSCF), 5. SIP REGISTER (P-CSCF to external server), 6. 200 OK (external server to P-CSCF), 7. 200 OK (P-CSCF to UE), and 8. Subscribe to Bearer Level Event (PCRF to P-CSCF, optional). A legend indicates that solid arrows represent mandatory messages and dashed arrows represent optional messages. + +**Figure B.1.2: Subscription to Notification of change of IP-CAN Type at initial IMS Registration** + +- 1.- The user initiates an initial SIP Registration procedure. + 2. The P-CSCF requests the establishment of a new Diameter Rx session with the intention to subscribe to the notification of IP-CAN Type Change. The P-CSCF sends a Diameter AAR command to the PCRF. +- NOTE: It should be possible for the P-CSCF to request the subscription to notification of IMS Signalling path status and PLMN changes also in this step. +3. The PCRF performs session binding and identifies corresponding PCC Rules related to IMS Signalling. + 4. The PCRF confirms the subscription to notification of change of IP-CAN type and replies with a Diameter AAA command back to the P-CSCF. The PCRF includes in the response the type of IP-CAN currently in use. + - 5-7. The SIP Registration procedure is completed successfully (user has been authenticated and registered within the IMS Core NW). + 8. If the PCRF had not previously subscribed to the required bearer level event from the IP-CAN (i.e. IP-CAN type change and RAT type change, if applicable), then the PCRF shall do so now. The PCRF initiates procedures according to figure 4.3.1.1.1. + +#### B.1b Provisioning of SIP signalling flow information at IMS Registration + +This clause covers the optional Provisioning of SIP signalling flow information upon an initial successful IMS Registration procedure. + +![Sequence diagram showing the provisioning of SIP signalling flow information at initial IMS registration between UE, PCRF, and P-CSCF.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` +sequenceDiagram + participant UE + participant PCRF + participant P-CSCF + + UE->>P-CSCF: 1. SIP REGISTER + P-CSCF->>+P-CSCF: 2. SIP REGISTER + P-CSCF-->>-P-CSCF: 3. 200 OK + P-CSCF->>UE: 4. 200 OK + P-CSCF->>PCRF: 5. Diameter AAR + Note over PCRF: 6. Session Binding + PCRF->>P-CSCF: 7. Diameter AAA + Note over PCRF: 8. Provisioning of PCC/QoS Rules +``` + +Legend: + ——> Mandatory + - - - -> Optional + +Sequence diagram showing the provisioning of SIP signalling flow information at initial IMS registration between UE, PCRF, and P-CSCF. + +**Figure B.1.3: Provisioning of SIP Signalling Flow Information at initial IMS Registration** + +- 1-4. The user initiates an initial SIP Registration procedure. The SIP Registration procedure is completed successfully (user has been authenticated and registered within the IMS Core NW). +5. The P-CSCF requests the establishment of a new Diameter Rx session with the intention to provision the information about the SIP signalling flows established between the UE and the P-CSCF. The P-CSCF sends a Diameter AAR command to the PCRF. +6. The PCRF performs session binding and identifies corresponding PCC Rules related to IMS Signalling. +7. The PCRF replies to the P-CSCF with a Diameter AAA. +8. If the PCRF had not previously provisioned PCC/QoS rules corresponding to the received SIP signalling flows, then the PCRF executes interactions according to figure 4.3.1.1.1. This step implies provisioning of PCC/QoS rules. + +#### B.1c Subscription to Notification of Change of PLMN Identifier at IMS Registration + +This clause covers the optional Subscription to Notifications of change in the PLMN identifier upon an initial IMS Registration procedure. + +![Sequence diagram showing the subscription to notification of change of PLMN Identifier at initial IMS Registration. The diagram involves three main entities: UE, PCRF, and P-CSCF. The sequence of messages is: 1. SIP REGISTER (UE to P-CSCF), 2. Diameter AAR (P-CSCF to PCRF), 3. Session Binding (internal to PCRF), 4. Diameter AAA (PCRF to P-CSCF), 5. SIP REGISTER (P-CSCF to UE), 6. 200 OK (UE to P-CSCF), 7. 200 OK (P-CSCF to UE), and 8. Subscribe to Bearer Level Event (PCRF to P-CSCF). Step 8 is optional, indicated by a dashed box and dashed arrow.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PCRF + participant P-CSCF + Note right of PCRF: 3. Session Binding + UE->>P-CSCF: 1. SIP REGISTER + P-CSCF->>PCRF: 2. Diameter AAR + PCRF->>P-CSCF: 4. Diameter AAA + P-CSCF->>UE: 5. SIP REGISTER + UE->>P-CSCF: 6. 200 OK + P-CSCF->>UE: 7. 200 OK + Note right of PCRF: 8. Subscribe to Bearer Level Event + PCRF-->>P-CSCF: + +``` + +Legend: + +- Mandatory +- - - - → Optional + +Sequence diagram showing the subscription to notification of change of PLMN Identifier at initial IMS Registration. The diagram involves three main entities: UE, PCRF, and P-CSCF. The sequence of messages is: 1. SIP REGISTER (UE to P-CSCF), 2. Diameter AAR (P-CSCF to PCRF), 3. Session Binding (internal to PCRF), 4. Diameter AAA (PCRF to P-CSCF), 5. SIP REGISTER (P-CSCF to UE), 6. 200 OK (UE to P-CSCF), 7. 200 OK (P-CSCF to UE), and 8. Subscribe to Bearer Level Event (PCRF to P-CSCF). Step 8 is optional, indicated by a dashed box and dashed arrow. + +**Figure B.1.4: Subscription to Notification of change of PLMN Identifier at initial IMS Registration** + +- The user initiates an initial SIP Registration procedure. + - The P-CSCF requests the establishment of a new Diameter Rx session with the intention to subscribe to the notification of PLMN Identifier Change. The P-CSCF sends a Diameter AAR command to the PCRF. +- NOTE 1: It should be possible for the P-CSCF to request the subscription to notification of IMS Signalling path status and IP-CAN Type changes also in this step. +- The PCRF performs session binding and identifies corresponding PCC Rules related to IMS Signalling. + - The PCRF confirms the subscription to notification of change of PLMN identifier and replies with a Diameter AAA command back to the P-CSCF. The PCRF includes in the response the PLMN Identifier currently in use, if available. +- 5-7. The SIP Registration procedure is completed successfully (user has been authenticated and registered within the IMS Core NW). +- If the PCRF had not previously subscribed to the required bearer level event from the PLMN where the UE is located (i.e. PLMN change event), then the PCRF shall do so now. The PCRF initiates procedures according to figure 4.3.1.1.1. +- NOTE 2: If the PLMN identifier is not available in step 4, the P-CSCF will wait to get it in step 8 before progressing the SIP Register, i.e. steps 5, 6 and 7 will occur after step 8. + +### B.2 IMS Session Establishment + +#### B.2.1 Provisioning of service information at Originating P-CSCF and PCRF + +This clause covers the PCC procedures at the originating P-CSCF and PCRF at IMS session establishment. + +In figure B.2.1.1 the P-CSCF derives the provisioning of service information to the PCRF from the SDP offer/answer exchange. + +![Sequence diagram of PCC Procedures for IMS Session Establishment at originating P-CSCF and PCRF. The diagram shows interactions between UE, PCRF, and P-CSCF. UE sends an SDP offer to P-CSCF. P-CSCF defines downlink connection info and forwards the SDP offer. PCRF defines uplink connection info and stores session information. P-CSCF sends Diameter AAR to PCRF. PCRF sends Diameter AAA to P-CSCF. P-CSCF sends an SDP answer to UE. PCRF provisions PCC/QoS Rules to P-CSCF. P-CSCF sends Diameter RAR to PCRF. PCRF sends Diameter RAA to P-CSCF. P-CSCF sends SIP with NPLI to UE. A legend indicates that solid arrows are Mandatory and dashed arrows are Conditional. A note indicates that steps 11 and 12 are conditional if access network information is requested.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PCRF + participant P-CSCF + + Note left of UE: NPLI: user location and/or UE timezone information + + UE->>P-CSCF: 1. SDP offer + P-CSCF->>P-CSCF: 2. Define downlink connection info + P-CSCF->>P-CSCF: 3. SDP offer + P-CSCF->>P-CSCF: 4. SDP answer + P-CSCF->>P-CSCF: 5. Define up link connection info + P-CSCF->>PCRF: 6. Diameter AAR + PCRF->>PCRF: 7. Store Session Information and identify IP CAN Session + PCRF->>P-CSCF: 8. Diameter AAA + PCRF->>UE: 9. SDP answer + PCRF->>P-CSCF: 10. PCC/QoS Rules provisioning + P-CSCF-->>PCRF: 11. Diameter RAR + PCRF-->>P-CSCF: 12. Diameter RAA + P-CSCF-->>UE: 13. SIP with NPLI + + Note right of P-CSCF: If access network information is requested + + Note right of UE: Legend + Note right of UE: --> Mandatory + Note right of UE: -.-> Conditional + +``` + +Sequence diagram of PCC Procedures for IMS Session Establishment at originating P-CSCF and PCRF. The diagram shows interactions between UE, PCRF, and P-CSCF. UE sends an SDP offer to P-CSCF. P-CSCF defines downlink connection info and forwards the SDP offer. PCRF defines uplink connection info and stores session information. P-CSCF sends Diameter AAR to PCRF. PCRF sends Diameter AAA to P-CSCF. P-CSCF sends an SDP answer to UE. PCRF provisions PCC/QoS Rules to P-CSCF. P-CSCF sends Diameter RAR to PCRF. PCRF sends Diameter RAA to P-CSCF. P-CSCF sends SIP with NPLI to UE. A legend indicates that solid arrows are Mandatory and dashed arrows are Conditional. A note indicates that steps 11 and 12 are conditional if access network information is requested. + +**Figure B.2.1.1: PCC Procedures for IMS Session Establishment at originating P-CSCF and PCRF** + +1. The P-CSCF receives the SDP parameters defined by the originator within an SDP offer in SIP signalling. +2. The P-CSCF identifies the connection information needed (IP address of the down link IP flow(s), port numbers to be used etc...). +3. The P-CSCF forwards the SDP offer in SIP signalling. +4. The P-CSCF gets the negotiated SDP parameters from the terminating side through SIP signalling interaction. + +5. The P-CSCF identifies the connection information needed (IP address of the up-link media IP flow(s), port numbers to be used etc...). +6. The P-CSCF forwards the derived session information to the PCRF by sending a Diameter AAR over a new Rx Diameter session. +7. The PCRF stores the received session information, and performs session binding. +8. The PCRF replies to the P-CSCF with a Diameter AAA. +9. Upon reception of the acknowledgement from the PCRF, the SDP parameters are passed to the UE in SIP signalling. +10. The PCRF executes interactions according to figure 4.3.1.1.1 . This step implies provisioning of PCC/QoS rules and is executed in parallel with steps 8 and 9. +11. If the P-CSCF requested access network information in step 6, the PCRF forwards the access network information received in step 10 in a Diameter RAR. +12. If step 11 occurs, the P-CSCF acknowledges the receipt of Diameter RAR. +13. If step 11 occurs, the P-CSCF forwards the access network information as the network provided location information when a suitable SIP message is received. + +Optionally, the provisioning of service information may be derived already from the SDP offer to enable that a possible rejection of the service information by the PCRF is obtained by the P-CSCF in time to reject the service with appropriate SIP signalling, to allow the P-CSCF to request network provided location information for inclusion in the SDP offer, to support authentication of roaming users in deployments with no IMS-level roaming interfaces or to support PSAP callback functionality for anonymous IMS emergency sessions. This is described in figure B.2.1.2. + +![Sequence diagram showing PCC Procedures for IMS Session Establishment at originating P-CSCF and PCRF. The diagram involves three main entities: UE, PCRF, and P-CSCF. The sequence starts with an SDP offer from the UE to the P-CSCF. The P-CSCF extracts down-link service information and sends a Diameter AAR to the PCRF. The PCRF responds with AuthorizeService Information and a Diameter AAA. The P-CSCF then sends an SDP offer (without NPLI) to the UE. A conditional block for provisioning PCC/QoS rules is shown. The P-CSCF extracts up-link service information and sends another Diameter AAR to the PCRF. The PCRF stores session information and responds with a Diameter AAA. Finally, the PCRF provisions PCC/QoS rules and the P-CSCF sends an SDP answer to the UE. A legend indicates that solid arrows are mandatory and dashed arrows are conditional. A note defines NPLI as user location and/or UE timezone information.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PCRF + participant P-CSCF + + Note right of P-CSCF: If access network information is requested + Note left of UE: NPLI: user location and/or UE timezone information + + UE->>P-CSCF: 1. SDP offer + P-CSCF->>P-CSCF: 2. Extractdown- link service information + P-CSCF->>PCRF: 3. Diameter AAR + PCRF->>PCRF: 4. AuthorizeService Information + PCRF->>P-CSCF: 5. Diameter AAA + P-CSCF->>UE: 6. SDP offer (without NPLI) + Note right of PCRF: 7. Provisioning of PCC/QoS Rules + PCRF->>P-CSCF: 8. Diameter RAR + P-CSCF->>PCRF: 9. Diameter RAA + Note right of P-CSCF: SDP offer + Note right of P-CSCF: 10a. (With NPLI) + Note right of P-CSCF: 10b. SIP (With NPLI) + P-CSCF->>UE: 11. SDP answer + P-CSCF->>P-CSCF: 12. Extractup- link service information + P-CSCF->>PCRF: 13. Diameter AAR + PCRF->>PCRF: 14. Store Session Information + PCRF->>P-CSCF: 15. Diameter AAA + Note right of PCRF: 16. Provisioning of PCC/QoS Rules + PCRF->>P-CSCF: 17. SDP answer + P-CSCF->>UE: + +``` + +**Legend** + +- Mandatory** +- Conditional** + +**NPLI:** +user location and/or UE +timezone information + +Sequence diagram showing PCC Procedures for IMS Session Establishment at originating P-CSCF and PCRF. The diagram involves three main entities: UE, PCRF, and P-CSCF. The sequence starts with an SDP offer from the UE to the P-CSCF. The P-CSCF extracts down-link service information and sends a Diameter AAR to the PCRF. The PCRF responds with AuthorizeService Information and a Diameter AAA. The P-CSCF then sends an SDP offer (without NPLI) to the UE. A conditional block for provisioning PCC/QoS rules is shown. The P-CSCF extracts up-link service information and sends another Diameter AAR to the PCRF. The PCRF stores session information and responds with a Diameter AAA. Finally, the PCRF provisions PCC/QoS rules and the P-CSCF sends an SDP answer to the UE. A legend indicates that solid arrows are mandatory and dashed arrows are conditional. A note defines NPLI as user location and/or UE timezone information. + +**Figure B.2.1.2: PCC Procedures for IMS Session Establishment at originating P-CSCF and PCRF, provisioning of service information derived from SDP offer and answer** + +1. The P-CSCF receives the first SDP offer for a new SIP dialogue within a SIP INVITE request. +2. The P-CSCF extracts service information from the SDP offer (IP address of the down link IP flow(s), port numbers to be used etc...). +3. The P-CSCF forwards the derived service information to the PCRF by sending a Diameter AAR over a new Rx Diameter session. It indicates that only an authorization check of the service information is requested. +4. The PCRF checks and authorizes the service information, performs session binding, but does not provision PCC/QoS rules at this stage. +5. The PCRF replies to the P-CSCF with a Diameter AAA. +6. If the P-CSCF did not request access network information in step 3, or if the P-CSCF requested access network information but does not require the access network information for inclusion in the SDP offer, or the P-CSCF requested EPC-level user information in step 3 the P-CSCF forwards the SDP offer in SIP signalling. + +7. If the P-CSCF requested access network information in step 3, the PCRF executes interactions according to Figure 4.3.1.1.1. This step implies provisioning of PCC/QoS rules. +8. If the P-CSCF requested access network information in step 3, the PCRF forwards the access network information received in step 7 in a Diameter RAR. +9. If step 8 occurs, the P-CSCF acknowledges the receipt of Diameter RAR. +- 10a. If step 8 occurs, and if the P-CSCF requires the access network information for inclusion in the SDP offer, the P-CSCF forwards the SDP offer and adds the access network information as the network provided location information to the corresponding SIP message. +- 10b. If step 8 occurs, and if the P-CSCF does not require the access network information for inclusion in the SDP offer, the P-CSCF forwards the access network information as the network provided location information in a suitable SIP message. This step normally occurs only after step 17. +11. The P-CSCF receives the negotiated SDP parameters from the terminating side within a SDP answer in SIP signalling. +12. The P-CSCF extracts service information from the SDP answer (IP address of the up-link media IP flow(s), port numbers to be used etc...). +13. The P-CSCF forwards the derived service information to the PCRF by sending a Diameter AAR over the existing Rx Diameter session. Access network information is not requested if done in step 7. +14. The PCRF stores the received session information. +15. The PCRF replies to the P-CSCF with a Diameter AAA. +16. The PCRF authorizes the session information. The PCRF executes interactions according to Figure 4.3.1.1.1. This step implies provisioning of PCC/QoS rules and authorized QoS. +17. Upon successful authorization of the session, the SDP parameters are passed to the UE in SIP signalling. This step is executed in parallel with step 16. + +#### B.2.2 Provisioning of service information at terminating P-CSCF and PCRF + +This clause covers the PCC procedures at the terminating P-CSCF and PCRF at IMS session establishment. + +In figure B.2.2.1 the P-CSCF derives the provisioning of service information to the PCRF from the SDP offer/answer exchange. + +![Sequence diagram showing PCC Procedures for IMS Session Establishment at terminating P-CSCF and PCRF. The diagram involves three main entities: P-CSCF, PCRF, and UE. The sequence starts with an SDP offer from an external source to the P-CSCF. The P-CSCF then defines up-link connection info and sends an SDP offer to the UE. The UE responds with an SDP answer. The P-CSCF then defines down-link connection info and sends a Diameter AAR to the PCRF. The PCRF stores session information and identifies an IP CAN session, then sends a Diameter AAA back to the P-CSCF. The P-CSCF sends an SDP answer (without NPLI) to the external source. The PCRF then provisions PCC/QoS rules and sends a Diameter RAR to the P-CSCF. The P-CSCF sends a Diameter RAA back to the PCRF. Finally, the P-CSCF sends an SDP answer (with NPLI) to the external source. A legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages. A note indicates that if access network information is requested, the PCRF will include NPLI in the SDP answer.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +**Legend** + +- Mandatory** (Solid arrow) +- Conditional** (Dashed arrow) + +**NPLI:** +user location and/or UE +timezone information + +*If access network information is requested* + +Sequence diagram showing PCC Procedures for IMS Session Establishment at terminating P-CSCF and PCRF. The diagram involves three main entities: P-CSCF, PCRF, and UE. The sequence starts with an SDP offer from an external source to the P-CSCF. The P-CSCF then defines up-link connection info and sends an SDP offer to the UE. The UE responds with an SDP answer. The P-CSCF then defines down-link connection info and sends a Diameter AAR to the PCRF. The PCRF stores session information and identifies an IP CAN session, then sends a Diameter AAA back to the P-CSCF. The P-CSCF sends an SDP answer (without NPLI) to the external source. The PCRF then provisions PCC/QoS rules and sends a Diameter RAR to the P-CSCF. The P-CSCF sends a Diameter RAA back to the PCRF. Finally, the P-CSCF sends an SDP answer (with NPLI) to the external source. A legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages. A note indicates that if access network information is requested, the PCRF will include NPLI in the SDP answer. + +**Figure B.2.2.1: PCC Procedures for IMS Session Establishment at terminating P-CSCF and PCRF** + +1. The P-CSCF receives the SDP parameters defined by the originator. +2. The P-CSCF identifies the connection information needed (IP address of the up-link IP flow(s), port numbers to be used etc...). +3. The P-CSCF sends the SDP offer to the UE. +4. The P-CSCF receives the negotiated SDP parameters from the UE. +5. The P-CSCF identifies the connection information needed (IP address of the down-link IP flow(s), port numbers to be used etc...). +6. The P-CSCF forwards the derived service information to the PCRF by sending a Diameter AAR over a new Rx Diameter session. +7. The PCRF stores the received session information, and performs session binding. +8. The PCRF sends a Diameter AAA to the P-CSCF. + +9. If the P-CSCF did not request access network information in step 6, upon reception of the acknowledgement from the PCRF, the SDP parameters in the SDP answer are passed to the originator. +10. The PCRF executes interactions according to clause 4.3.1.1.1. This step implies provisioning of PCC/QoS rules and is executed in parallel with steps 8 and 9. +11. If the P-CSCF requested access network information in step 6, the PCRF forwards the access network information received in step 10 in a Diameter RAR. +12. If step 11 occurs, the P-CSCF acknowledges the receipt of Diameter RAR. +13. If step 11 occurs, the P-CSCF forwards the SDP answer and adds the access network information as the network provided location information to the corresponding SIP message. + +Optionally, the provisioning of service information may be derived already from the SDP offer to enable that a possible rejection of the service information by the PCRF is obtained by the P-CSCF in time to reject the service with appropriate SIP signalling or to enable pre-authorization for a UE terminated IMS session establishment with UE initiated resource reservation. This is described in figure B.2.2.2. + +![Sequence diagram showing PCC Procedures for IMS Session Establishment at terminating P-CSCF and PCRF. Lifelines: P-CSCF, PCRF, UE. The diagram shows the flow of SDP offers, Diameter messages (AAR, AAA, RAR, RAA), and provisioning of PCC/QoS rules. A legend indicates mandatory (solid line) and conditional (dashed line) messages. A note defines NPLI as user location and/or UE timezone information. A bracket indicates that steps 14 and 15 are conditional if access network information is requested.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant External + participant P-CSCF + participant PCRF + participant UE + + Note left of P-CSCF: NPLI: user location and/or UE timezone information + + External->>P-CSCF: 1. SDP offer + P-CSCF->>P-CSCF: 2. Extract up link service information + P-CSCF->>PCRF: 3. Diameter AAR + PCRF->>P-CSCF: 4. Authorize Service Information + PCRF->>P-CSCF: 5. Diameter AAA + PCRF->>UE: 6. SDP offer + Note right of PCRF: 7. Provisioning of PCC/QoS Rules + UE->>PCRF: 8. SDP answer + P-CSCF->>P-CSCF: 9. Extract downlink service information + P-CSCF->>PCRF: 10. Diameter AAR + PCRF->>P-CSCF: 10a. Store Session Information + PCRF->>P-CSCF: 11. Diameter AAA + Note right of PCRF: 12. Provisioning of PCC/QoS Rules + P-CSCF->>External: 13. SDP answer (without NPLI) + Note right of PCRF: If access network information is requested + PCRF->>P-CSCF: 14. Diameter RAR + P-CSCF->>PCRF: 15. Diameter RAA + P-CSCF->>External: 16. SDP answer (With NPLI) + + Note right of UE: Legend + Note right of UE: --> Mandatory + Note right of UE: -.-> Conditional + +``` + +Sequence diagram showing PCC Procedures for IMS Session Establishment at terminating P-CSCF and PCRF. Lifelines: P-CSCF, PCRF, UE. The diagram shows the flow of SDP offers, Diameter messages (AAR, AAA, RAR, RAA), and provisioning of PCC/QoS rules. A legend indicates mandatory (solid line) and conditional (dashed line) messages. A note defines NPLI as user location and/or UE timezone information. A bracket indicates that steps 14 and 15 are conditional if access network information is requested. + +**Figure B.2.2.2: PCC Procedures for IMS Session Establishment at terminating P-CSCF and PCRF, provisioning of service information derived from SDP offer and answer** + +1. The P-CSCF receives the first SDP offer for a new SIP dialogue within SIP signalling, e.g. within a SIP INVITE request. +2. The P-CSCF extracts the service information from the SDP offer (IP address of the up-link IP flow(s), port numbers to be used etc...). + +3. The P-CSCF forwards the derived session information to the PCRF by sending a Diameter AAR over a new Rx Diameter session. It indicates that the service information that the AF has provided to the PCRF is preliminary and needs to be further negotiated between the two ends. +4. The PCRF checks and authorizes the session information, performs session binding, but does not provision PCC/QoS Rules at this stage. +5. The PCRF replies to the P-CSCF with a Diameter AAA. +6. The P-CSCF sends the SDP offer to the UE. +7. If the UE initiates a bearer resource modification request, the PCRF provides the PCEF/BBERF with PCC/QoS rules according to figure 4.3.1.1.1 based on the SDP offer. + +NOTE: Step 7 is not applicable for IMS Emergency Sessions. + +8. The P-CSCF receives the negotiated SDP parameters from the UE within an SDP answer in SIP signalling. +9. The P-CSCF extracts service information from the SDP answer (IP address of the down-link IP flow(s), port numbers to be used etc...). +10. The P-CSCF forwards the derived service information to the PCRF by sending a Diameter AAR over the existing Rx Diameter session. +- 10a. The PCRF stores the received session information. +11. The PCRF sends a Diameter AAA to the P-CSCF. +12. The PCRF authorizes the session information. The PCRF executes interactions according to Figure 4.3.1.1.1. This step implies provisioning of PCC/QoS rules and authorized QoS. +13. If the P-CSCF did not request access network information in step 3 or 10, upon successful authorization of the session the SDP parameters in the SDP answer are passed to the originator. This step is executed in parallel with step 12. +14. If the P-CSCF requested access network information in step 3 or 10, the PCRF forwards the access network information received in step 12 in a Diameter RAR. +15. If step 14 occurs, the P-CSCF acknowledges the receipt of Diameter RAR. +16. If step 14 occurs, the P-CSCF forwards the SDP answer and adds the access network information as the network provided location information to the corresponding SIP message. + +### --- B.3 IMS Session Modification + +#### B.3.1 Provisioning of service information + +This clause covers the provisioning of service information at IMS session modification both at the originating and terminating side. + +In figure B.3.1.1 the P-CSCF derives the provisioning of service information to the PCRF from the SDP offer/answer exchange. + +![Sequence diagram showing the provisioning of service information at IMS session modification between PCRF and P-CSCF. The diagram includes 13 numbered steps, a legend for mandatory and conditional messages, and a note about NPLI (user location and/or UE timezone information).](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram illustrates the interaction between a PCRF and a P-CSCF for provisioning service information during an IMS session modification. The sequence of messages is as follows: + +1. SDP offer (Mandatory) +2. extract changes in service information from SDP offer (Internal P-CSCF action) +3. SDP offer (Mandatory) +4. SDP answer (Mandatory) +5. extract changes in service information from SDP answer (Internal P-CSCF action) +6. Diameter AAR (Mandatory) +7. Store Session Info and Identify IP-CAN Session (Internal PCRF action) +8. Diameter AAA (Mandatory) +9. SDP answer (without NPLI) (Conditional) +10. Interactions in Figure 4.3.1.1.1 (Internal PCRF action) +11. Diameter RAR (Conditional) +12. Diameter RAA (Conditional) +13. SDP answer (with NPLI) (Conditional) + +**NPLI:** +user location and/or UE +timezone information + +**Legend** + +- Mandatory (solid line) +- Conditional (dashed line) + +*If access network Information is requested* + +Sequence diagram showing the provisioning of service information at IMS session modification between PCRF and P-CSCF. The diagram includes 13 numbered steps, a legend for mandatory and conditional messages, and a note about NPLI (user location and/or UE timezone information). + +Figure B.3.1.1: Provisioning of service information at IMS session modification + +1. The P-CSCF receives the SDP parameters defined by the originator within an SDP offer in SIP signalling. +2. The P-CSCF identifies the relevant changes in the SDP. +3. The P-CSCF forwards the SDP offer in SIP signalling. +4. The P-CSCF gets the negotiated SDP parameters from the terminating side through SIP signalling interaction. +5. The P-CSCF identifies the relevant changes in the SDP. +6. The P-CSCF sends a Diameter AAR for an existing Diameter session and includes the derived updated service information. + +7. The PCRF stores the received updated session information and identifies the affected established IP-CAN Session(s). +8. The PCRF answers with a Diameter AAA. +9. If the P-CSCF did not request access network information in step 6, the P-CSCF forwards the SDP answer in SIP signalling. +10. The PCRF executes interactions according to figure 4.3.1.1.1. Due to the updated service information, this step may imply provisioning of PCC/QoS rules or the need to enable or disable IP Flows (see clauses B.3.2 and B.3.3, respectively). +11. If the P-CSCF requested access network information in step 6, the PCRF forwards the access network information received in step 10 in a Diameter RAR. +12. If step 11 occurs, the P-CSCF acknowledges the receipt of Diameter RAR. +13. If step 11 occurs, the P-CSCF forwards the SDP answer and adds the access network information as the network provided location information to the corresponding SIP message. + +Optionally, the provisioning of service information may be derived already from the SDP offer to enable that a possible rejection of the service information by the PCRF is obtained by the P-CSCF in time to reject the service with appropriate SIP signalling or to enable pre-authorization for a UE terminated IMS session establishment with UE initiated resource reservation. This is described in figure B.3.1.2. + +![Sequence diagram showing the provisioning of service information derived from SDP offer and answer at IMS session modification between PCRF and P-CSCF. The diagram includes 16 numbered steps, process boxes for 'authorize service information', 'Provisioning of PCC/QoS Rules', and 'extract changes in service information'. It also features a legend for 'Mandatory' (solid line) and 'Conditional' (dashed line) messages, and a box defining NPLI as user location and/or UE timezone information.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +**Sequence Diagram: Provisioning of service information derived from SDP offer and answer at IMS session modification** + +**Participants:** PCRF, P-CSCF + +**Legend:** + +- Mandatory:** Solid line with arrowhead +- Conditional:** Dashed line with arrowhead + +**NPLI:** user location and/or UE timezone information + +**Sequence of Messages:** + +- SDP offer (Mandatory) from UE to P-CSCF +- extract changes in service information from SDP offer (Process) at P-CSCF +- Diameter AAR (Mandatory) from P-CSCF to PCRF +- authorize service information (Process) at PCRF +- Diameter AAA (Mandatory) from PCRF to P-CSCF +- Provisioning of PCC/QoS Rules (Process) at PCRF +- SDP offer (Mandatory) from P-CSCF to UE +- SDP answer (Mandatory) from UE to P-CSCF +- extract changes in service information from SDP answer (Process) at P-CSCF +- Diameter AAR (Mandatory) from P-CSCF to PCRF +- Diameter AAA (Mandatory) from PCRF to P-CSCF +- Provisioning of PCC/QoS Rules (Process) at PCRF +- SDP answer (without NPLI) (Conditional) from PCRF to UE +- Diameter RAR (Conditional) from PCRF to P-CSCF +- Diameter RAA (Conditional) from P-CSCF to PCRF +- SDP answer (With NPLI) (Conditional) from PCRF to UE + +*Note: Steps 14 and 15 are grouped by a bracket indicating they occur "If access network information is requested".* + +Sequence diagram showing the provisioning of service information derived from SDP offer and answer at IMS session modification between PCRF and P-CSCF. The diagram includes 16 numbered steps, process boxes for 'authorize service information', 'Provisioning of PCC/QoS Rules', and 'extract changes in service information'. It also features a legend for 'Mandatory' (solid line) and 'Conditional' (dashed line) messages, and a box defining NPLI as user location and/or UE timezone information. + +Figure B.3.1.2: Provisioning of service information derived from SDP offer and answer at IMS session modification + +1. The P-CSCF receives an SDP offer in SIP signalling for an exiting SIP dialogue. +2. The P-CSCF identifies the relevant changes in the SDP and extracts the corresponding service information. + +3. The P-CSCF forwards the derived service information to the PCRF by sending a Diameter AAR over the existing Rx Diameter session for the corresponding SIP session. It indicates that the service information that the AF has provided to the PCRF is preliminary and needs to be further negotiated between the two ends. +4. The PCRF checks and authorizes the session information, but does not provision PCC/QoS rules at this stage. +5. The PCRF replies to the P-CSCF with a Diameter AAA. +6. If the UE initiates a bearer resource modification request, the PCRF provides the PCEF/BBERF with PCC/QoS rules according to figure 4.3.1.1.1 based on the SDP offer. + +NOTE: Step 6 is not applicable for IMS Emergency Sessions. + +7. The P-CSCF forwards the SDP offer in SIP signalling. +8. The P-CSCF receives the negotiated SDP parameters within an SDP answer in SIP signalling from the terminating side. +9. The P-CSCF identifies the relevant changes in the SDP and extracts the corresponding service information. +10. The P-CSCF sends a Diameter AAR for an existing Diameter session and includes the derived updated service information. +11. The PCRF answers with a Diameter AAA. +12. The PCRF interacts with the GW according to figure 4.3.1.1.1. This step may imply provisioning of PCC/QoS rules and authorized QoS. The PCRF may need to enable or disable IP Flows (see clauses B.3.2 and B.3.3, respectively) due to the updated service information. +13. If the P-CSCF did not request access network information in step 3 or 10, the P-CSCF forwards the SDP answer in SIP signalling. This step is executed in parallel with step 12. +14. If the P-CSCF requested access network information in step 3 or 10, the PCRF forwards the access network information received in step 12 in a Diameter RAR. +15. If step 14 occurs, the P-CSCF acknowledges the receipt of Diameter RAR. +16. If step 14 occurs, the P-CSCF forwards the SDP answer and adds the access network information as the network provided location information to the corresponding SIP message. + +#### B.3.2 Enabling of IP Flows + +The PCRF makes a final decision to enable the allocated QoS resource for the authorized IP flows of the media component(s) if the QoS resources are not enabled at the time they are authorized by the PCRF or if the media IP flow(s) previously placed on hold are resumed, i.e. the media IP flow(s) of the media component that was placed on hold at the time of the resource authorization or at a later stage is reactivated (with SDP direction sendrecv, sendonly, recvonly or none direction). + +The Enabling of IP Flows procedure is triggered by the P-CSCF receiving any 2xx success response to an INVITE request or a 2xx success response to an UPDATE request within a confirmed dialogue that is not embedded as part of another INVITE Transaction (in both cases a 200 OK response is usually received). When receiving such responses, the PCRF shall take the SDP direction attribute in the latest received SDP (either within the 2xx success or a previous SIP message) into account when deciding, which gates shall be opened: + +- For a unidirectional SDP media component, IP flows in the opposite direction shall not be enabled. +- For an inactive SDP media component, no IP flows shall be enabled. + +Figure B.3.2.1 is applicable to the Mobile Originating (MO) side and the Mobile Terminating (MT) side. + +![Sequence diagram for Enabling of IP Flows](68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg) + +The diagram is a sequence diagram illustrating the 'Enabling of IP Flows' procedure. It features three lifelines: UE, PCRF, and P-CSCF. The sequence of messages is as follows: 1. An external '2xx Success' message is received by the P-CSCF. 2. The P-CSCF sends a 'Diameter AAR' message to the PCRF. 3. The PCRF performs an internal action: 'PCRF updates flow status of affected PCC rules'. 4. The PCRF sends a 'Diameter AAA' message to the P-CSCF. 5. The P-CSCF sends a '2xx Success' message to the UE. 6. The PCRF performs another internal action: 'PCRF opens the gates'. A legend at the bottom left shows a solid arrow pointing right, labeled 'Mandatory'. + +Sequence diagram for Enabling of IP Flows + +**Figure B.3.2.1: Enabling of IP Flows** + +1. The P-CSCF receives the 2xx Success message complying with the conditions specified in the paragraphs above. +2. The P-CSCF sends a Diameter AAR message to the PCRF, requesting that gates shall be opened. +3. The PCRF approves the enabling of IP flows and PCRF updates flow status of affected PCC rules. +4. The PCRF sends a Diameter AAA to the P-CSCF. +5. The P-CSCF forwards the 2xx Success message. +6. The PCRF executes interactions according to figure 4.3.1.1.1. This step implies opening the 'gates' by updating the flow status of PCC rules. + +### B.3.3 Disabling of IP Flows + +The “Disabling of IP Flows” procedure is used when media IP flow(s) of a session are put on hold (e.g. in case of a media re-negotiation or call hold). + +Media is placed on hold as specified in RFC 3264 [12]. Media modified to become inactive (SDP direction attribute) shall also be considered to be put on hold. + +If a bidirectional media component is placed on hold by making it unidirectional, the IP flows shall only be disabled in the deactivated direction. If a media component is placed on hold by making it inactive, the IP flows shall be disabled in both directions. + +Figure B.3.3.1 presents the “Disabling of IP Flows” procedure at media on hold for both the Mobile Originating (MO) side and the Mobile Terminating (MT) side. + +![Sequence diagram showing the disabling of IP flows at media on hold. Lifelines: UE, PCRF, P-CSCF. The sequence starts with an external SDP answer to the P-CSCF. The P-CSCF sends a Diameter AAR to the PCRF. The PCRF updates flow status and sends a Diameter AAA back. The P-CSCF then sends an SDP answer to the UE. Finally, the PCRF closes the related gate.](4792a2ccd62226861fadc22117edb7b1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PCRF + participant P-CSCF + Note right of P-CSCF: 1. SDP answer putting media on hold + P-CSCF->>PCRF: 2. Diameter AAR + Note over PCRF: 3. PCRF updates flow status of affected PCC rules + PCRF->>P-CSCF: 4. Diameter AAA + P-CSCF->>UE: 5. SDP answer putting media on hold + Note over PCRF: 7. PCRF closes the related gate + +``` + +Legend: + → Mandatory + +Sequence diagram showing the disabling of IP flows at media on hold. Lifelines: UE, PCRF, P-CSCF. The sequence starts with an external SDP answer to the P-CSCF. The P-CSCF sends a Diameter AAR to the PCRF. The PCRF updates flow status and sends a Diameter AAA back. The P-CSCF then sends an SDP answer to the UE. Finally, the PCRF closes the related gate. + +**Figure B.3.3.1: Disabling of IP Flows at Media on Hold** + +1. The P-CSCF receives an SDP answer putting media on hold within a SIP message. (NOTE) +2. The P-CSCF sends a Diameter AAR request to the PCRF, requesting that gates shall be closed. +3. The PCRF updates flow status of affected PCC rules for the media on hold. +4. The PCRF sends a Diameter AAA message back to the P-CSCF. +5. The P-CSCF forwards the SDP answer putting media on hold within a SIP message. +6. The PCRF executes interactions according to figure 4.3.1.1.1. This step implies closing the relevant media IP flow gate(s), leaving the possible related RTCP gate(s) open to keep the connection alive. + +NOTE: This procedure occurs whenever a bidirectional media is made unidirectional or when a media is changed to inactive. + +### B.3.4 Media Component Removal + +Figure B.3.4.1 presents the flows of PCC procedures at the removal of media component(s) from an IMS session which is not being released for both the Mobile Originating (MO) side and the Mobile Terminating (MT) side. + +![Sequence diagram showing the interaction between UE, PCRF, and P-CSCF for revoking authorization for IP resources at media component removal. The diagram includes six steps: 1. SDP answer removing media component (received by P-CSCF), 2. Diameter AAR (P-CSCF to PCRF), 3. Store Session Information and Identify IP-CAN session (internal to PCRF), 4. Diameter AAA (PCRF to P-CSCF), 5. SDP answer removing media component (P-CSCF to UE), and 6. Remove/Modify PCC/QoS Rules (internal to PCRF). A legend indicates that solid arrows represent mandatory actions.](69edc2887e907309499ac95b47ab6905_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PCRF + participant P-CSCF + Note right of P-CSCF: 1. SDP answer removing media component + P-CSCF->>PCRF: 2. Diameter AAR + Note right of PCRF: 3. Store Session Information and Identify IP-CAN session + PCRF->>P-CSCF: 4. Diameter AAA + P-CSCF->>UE: 5. SDP answer removing media component + Note right of PCRF: 6. Remove/Modify PCC/QoS Rules + +``` + +Legend: +→ Mandatory + +Sequence diagram showing the interaction between UE, PCRF, and P-CSCF for revoking authorization for IP resources at media component removal. The diagram includes six steps: 1. SDP answer removing media component (received by P-CSCF), 2. Diameter AAR (P-CSCF to PCRF), 3. Store Session Information and Identify IP-CAN session (internal to PCRF), 4. Diameter AAA (PCRF to P-CSCF), 5. SDP answer removing media component (P-CSCF to UE), and 6. Remove/Modify PCC/QoS Rules (internal to PCRF). A legend indicates that solid arrows represent mandatory actions. + +**Figure B.3.4.1: Revoke authorization for IP resources at media component removal for both Mobile Originating (MO) and Mobile Terminating (MT) side** + +1. A SIP message containing SDP indicating the removal of media component(s) is received by the P-CSCF. +2. The P-CSCF sends Diameter AAR to the PCRF with modified service information. +3. The PCRF stores the Session information and identifies the affected IP-CAN Session(s). +4. The PCRF sends a Diameter AAA message back to the P-CSCF. +5. The P-CSCF forwards the SDP answer removing a media component. +6. The PCRF makes a decision on what PCC/QoS rules need to be modified or removed and executes interactions according to figure 4.3.1.1.1. + +## B.4 IMS Session Termination + +### B.4.1 Mobile initiated session release / Network initiated session release + +Figure B.4.1.1 presents the mobile or network initiated IMS session release without access network information retrieval. The session release may be signalled by a SIP BYE message, or any SIP 3xx redirect response, or any 4xx, 5xx, or 6xx SIP final error response to an initial INVITE request. If any 4xx, 5xx, or 6xx SIP final error response to Re-INVITE or UPDATE request just terminates the transaction, then the session is not released, otherwise if the error response terminates the dialog then the session is released. + +Figures B.4.1.2 and B.4.1.3 presents the network initiated and the mobile initiated IMS session release with access network information retrieval, respectively. + +![Sequence diagram for IMS session termination without access network information retrieval. Lifelines: UE, PCRF, P-CSCF. Step 1: BYE message from P-CSCF to UE. Step 2: BYE, 3xx, 4xx, 5xx, or 6xx response from P-CSCF to UE. Step 3: Removal of PCC/QoS Rules at AF session release (parallel interaction with PCRF).](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +``` +sequenceDiagram + participant UE + participant PCRF + participant P-CSCF + Note right of P-CSCF: 1. BYE, 3xx, 4xx, 5xx, or 6xx + P-CSCF->>UE: 2. BYE, 3xx, 4xx, 5xx, or 6xx + Note over PCRF, P-CSCF: 3. Removal of PCC/QoS Rules at AF session release +``` + +Sequence diagram for IMS session termination without access network information retrieval. Lifelines: UE, PCRF, P-CSCF. Step 1: BYE message from P-CSCF to UE. Step 2: BYE, 3xx, 4xx, 5xx, or 6xx response from P-CSCF to UE. Step 3: Removal of PCC/QoS Rules at AF session release (parallel interaction with PCRF). + +**Figure B.4.1.1: IMS session termination without access network information retrieval** + +1. SIP BYE message, a SIP 3xx redirect response, or any 4xx, 5xx, or 6xx SIP final error response to an initial INVITE or any 4xx, 5xx, or 6xx SIP final error response to Re-INVITE or UPDATE which terminates the dialog is received by the P-CSCF. +2. P-CSCF forwards the BYE message, or the SIP 3xx redirect response, or any 4xx, 5xx, or 6xx SIP final error response. +3. The Interactions in in Figure 4.3.1.2.3.1.1 or Figure 4.3.1.2.3.2.1 are applicable. + +![Sequence diagram for network initiated IMS session termination with access network information retrieval. Lifelines: UE, PCRF, P-CSCF. Step 1: BYE message from P-CSCF to UE. Step 2: BYE message from P-CSCF to UE. Step 3: Removal of PCC/QoS Rules at AF session release (parallel interaction with PCRF). Step 4: 200 OK (BYE) response from UE to P-CSCF. Step 5: 200 OK (BYE) response from P-CSCF to UE.](12a6537c92844d5b393104c02e8dfc2f_img.jpg) + +``` +sequenceDiagram + participant UE + participant PCRF + participant P-CSCF + Note right of P-CSCF: 1. BYE + P-CSCF->>UE: 2. BYE + Note over PCRF, P-CSCF: 3. Removal of PCC/QoS Rules at AF session release + UE->>P-CSCF: 4. 200 OK (BYE) + P-CSCF->>UE: 5. 200 OK (BYE) +``` + +Sequence diagram for network initiated IMS session termination with access network information retrieval. Lifelines: UE, PCRF, P-CSCF. Step 1: BYE message from P-CSCF to UE. Step 2: BYE message from P-CSCF to UE. Step 3: Removal of PCC/QoS Rules at AF session release (parallel interaction with PCRF). Step 4: 200 OK (BYE) response from UE to P-CSCF. Step 5: 200 OK (BYE) response from P-CSCF to UE. + +**Figure B.4.1.2: network initiated IMS session termination with access network information retrieval** + +1. SIP BYE message is received by the P-CSCF. +2. The P-CSCF forwards the BYE message. +3. In parallel to step 2, the Interactions in Figure 4.3.1.2.3.1.1 or Figure 4.3.1.2.3.2.1 take place. Within those interactions, the P-CSCF requests and receives the access network information. +4. The P-CSCF receives the SIP 200 OK (BYE) SIP message. +5. The P-CSCF forwards the SIP 200 OK (BYE) SIP message. It includes the access networking information obtained in step 3 as the network provided location information. + +![Sequence diagram for mobile initiated IMS session termination with access network information retrieval. Lifelines: PCRF, P-CSCF, UE. Step 1: UE sends BYE to P-CSCF. Step 2: P-CSCF sends a request to PCRF for removal of PCC/QoS Rules at AF session release. Step 3: P-CSCF forwards the BYE message to the UE.](aa81b9b80bd1e3d723922b3a033564a2_img.jpg) + +``` +sequenceDiagram + participant UE + participant P-CSCF + participant PCRF + Note right of UE: 1. BYE + UE->>P-CSCF: 1. BYE + Note right of P-CSCF: 2. Removal of PCC/QoS Rules at AF session release + P-CSCF->>PCRF: 2. Removal of PCC/QoS Rules at AF session release + Note left of PCRF: 3. BYE + PCRF->>P-CSCF: 3. BYE +``` + +Sequence diagram for mobile initiated IMS session termination with access network information retrieval. Lifelines: PCRF, P-CSCF, UE. Step 1: UE sends BYE to P-CSCF. Step 2: P-CSCF sends a request to PCRF for removal of PCC/QoS Rules at AF session release. Step 3: P-CSCF forwards the BYE message to the UE. + +**Figure B.4.1.3: mobile initiated IMS session termination with access network information retrieval** + +1. SIP BYE message is received by the P-CSCF. +2. The Interactions in Figure 4.3.1.2.3.1.1 or Figure 4.3.1.2.3.2.1 are applicable. Within those interactions, the P-CSCF requests and receives the access network information. +3. The P-CSCF forwards the BYE message. It includes the access network information obtained in step 2 as the network provided location information. + +### B.4.2 IP-CAN Bearer Release/Loss + +An IP-CAN Bearer Release or Loss event may affect all IP-Flows within an IMS Session. Flows in clause 4.3.2.2.1 (AF located in the HPLMN) or 4.3.2.2.2 (AF located in the VPLMN) apply for case 1. Flows in clause 4.4.2.1.1 (Home Routed case) or 4.4.2.2.1 (Visited Access case) apply for case 2a and case 2b. + +## B.5 P-CSCF Restoration + +This clause is applicable if P-CSCF Restoration is to be performed. + +![Sequence diagram for P-CSCF Restoration showing interactions between UE, PCEF, V-PCRF, H-PCRF, and P-CSCF. The diagram shows Diameter AAR/AAA and RAR/RAA exchanges for both non-roaming and roaming with local breakout scenarios.](573c8f9e728e343b6864e1070c14b8cf_img.jpg) + +``` + +sequenceDiagram + participant UE + participant PCEF + participant V-PCRF + participant H-PCRF + participant P-CSCF + + Note right of P-CSCF: SIP message + P-CSCF->>H-PCRF: 1. Diameter AAR + H-PCRF-->>P-CSCF: 2. Diameter AAA + H-PCRF->>PCEF: 3. Diameter RAR + PCEF-->>H-PCRF: 4. Diameter RAA + + rect rgb(220, 255, 255) + Note over PCEF, P-CSCF: Roaming with local breakout when the P-CSCF is located in the VPLMN + P-CSCF->>V-PCRF: 1a. Diameter AAR + V-PCRF-->>P-CSCF: 2a. Diameter AAA + V-PCRF->>PCEF: 3a. Diameter RAR + PCEF-->>V-PCRF: 4a. Diameter RAA + end + + Note over UE, PCEF: P-CSCF Restoration Procedure + +``` + +Sequence diagram for P-CSCF Restoration showing interactions between UE, PCEF, V-PCRF, H-PCRF, and P-CSCF. The diagram shows Diameter AAR/AAA and RAR/RAA exchanges for both non-roaming and roaming with local breakout scenarios. + +**Figure B.5.1: P-CSCF Restoration** + +1. The P-CSCF sends an AAR command to PCRF to initiate a P-CSCF Restoration procedure, as defined in the 3GPP TS 23.380 [35]. The AAR command contains a Rx-Request-Type AVP with value set to PCSCF\_RESTORATION and can contain the IP address of the UE within Framed-IP-Address AVP (if available) or the Framed-IPv6-Prefix AVP (if available), IMSI (if available) within the Subscription-Id AVP, the IMS APN (if available) within the Called-Station-Id AVP and/or the IP address domain (if available) within the IP-Domain-Id AVP. + +For the non-roaming case and the home routed case, the H-PCRF receives the AAR command, i.e. step 1 is executed. + +- 1a. For the roaming case with visited access, when the P-CSCF is located in the VPLMN, step 1 is executed with the exception that the V-PCRF receives the AAR command and responds with the AAA command +2. When receiving the AAR command for P-CSCF Restoration from the P-CSCF, the PCRF acknowledges the AAR by sending an AAA command to the P-CSCF. + +For the non-roaming case and the home routed case, the H-PCRF sends an AAA command to the P-CSCF, i.e. step 2 is executed. + +- 2a. For the roaming case with visited access, when the P-CSCF is located in the VPLMN, step 2 is executed with the exception that the V-PCRF sends an AAA command to the P-CSCF. + +For the roaming case with local breakout when the P-CSCF is located in the HPLMN, when the H-PCRF receives the AAR command from the P-CSCF, the H-PCRF sends an RAR command to the V-PCRF, i.e. step 1b is executed. + +3. When receiving the AAR command for P-CSCF Restoration, the PCRF finds the corresponding IP-CAN session according to the received information within the AAR command, and sends an RAR command for the corresponding IP-CAN session (IMS PDN connection) to the PCEF for P-CSCF Restoration. The RAR contains a PCSCF-Restoration-Indication AVP with value set to PCSCF\_RESTORATION. + +For the non-roaming case and the home routed case, when receiving the AAR command from the P-CSCF, the H-PCRF sends the RAR command to the PCEF, i.e. step 3 is executed. + +- 3a. For the roaming case with visited access, when the P-CSCF is located in the VPLMN, step 3 is executed with the exception that when receiving the AAR command from the P-CSCF, the V-PCRF sends the RAR command to the PCEF. + +For the roaming case with local breakout when the P-CSCF is located in the HPLMN, when receiving the RAR command from the H-PCRF, the V-PCRF sends an RAR command to the PCEF, i.e. step 2a is executed. + +4. When receiving the RAR command for P-CSCF Restoration, the PCEF acknowledges the RAR by sending an RAA command to the PCRF and performs the subsequent P-CSCF Restoration procedure as specified in 3GPP TS 23.380 [35]. + +NOTE 1: If the IMS PDN disconnection is performed for P-CSCF Restoration, the PCEF sends a CCR command to the PCRF to terminate the corresponding Gx session. + +For the non-roaming case and the home routed case, when receiving the RAR command from the H-PCRF, the PCEF acknowledges this message by sending an RAA command to the H-PCRF, i.e. step 4 is executed. + +- 4a. For the roaming case with visited access, when the P-CSCF is located in the VPLMN, step 4 is executed with the exception that when receiving the RAR command from the V-PCRF, the PCEF acknowledges this message by sending an RAA command to the V-PCRF. + +NOTE 2: This P-CSCF Restoration procedure is applicable to the cases that both the P-CSCF and the PCEF are located in the same PLMN. + +## --- B.6 IMS Restricted Local Operator Services + +RLOS may be supported as described in subclause B.0 with the following differences: + +- emergency service is replaced by RLOS; +- emergency indication is replaced by RLOS indication; +- emergency session is replaced by RLOS session; +- emergency APN is replaced by RLOS APN; and +- the call back functionality is not applicable to RLOS. + +Subclause B.2.2 is not supported for RLOS, because only UE originated RLOS requests are supported and there is no support for mobile terminated services as specified in 3GPP TS 23.221 [66]. + +## --- B.7 Retrieval of Network Provided Location Information for SMS over IP at Originating side + +This clause covers the optional request of access network information for SMS over IP. + +![Sequence diagram showing the retrieval of access network information for SMS over IP at the originating side. The diagram involves three main entities: UE, PCRF, and P-CSCF. The sequence of messages is: 1. SIP MESSAGE from UE to P-CSCF; 2. Diameter AAR from P-CSCF to PCRF; 3. Session Binding (internal to PCRF); 4. Diameter AAA from PCRF to P-CSCF; 5. Request Access Network Info (internal to PCRF); 6. Diameter RAR from PCRF to P-CSCF; 7. Diameter RAA from P-CSCF to PCRF; 8. SIP MESSAGE from P-CSCF to the right (out of the diagram).](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` +sequenceDiagram + participant UE + participant PCRF + participant P-CSCF + Note right of PCRF: 3. Session Binding + Note right of PCRF: 5. Request Access Network Info + UE->>P-CSCF: 1. SIP MESSAGE + P-CSCF->>PCRF: 2. Diameter AAR + PCRF-->>P-CSCF: 4. Diameter AAA + PCRF->>P-CSCF: 6. Diameter RAR + P-CSCF-->>PCRF: 7. Diameter RAA + P-CSCF->>Note right of P-CSCF: 8. SIP MESSAGE +``` + +Sequence diagram showing the retrieval of access network information for SMS over IP at the originating side. The diagram involves three main entities: UE, PCRF, and P-CSCF. The sequence of messages is: 1. SIP MESSAGE from UE to P-CSCF; 2. Diameter AAR from P-CSCF to PCRF; 3. Session Binding (internal to PCRF); 4. Diameter AAA from PCRF to P-CSCF; 5. Request Access Network Info (internal to PCRF); 6. Diameter RAR from PCRF to P-CSCF; 7. Diameter RAA from P-CSCF to PCRF; 8. SIP MESSAGE from P-CSCF to the right (out of the diagram). + +**Figure B.7.1: Retrieval of Access Network Information for SMS over IP at originating side** + +- 1.- The UE sends a SIP MESSAGE request to IMS. +2. The P-CSCF requests the establishment of a new Diameter Rx session with the intention of retrieval the access network information. The P-CSCF sends a Diameter AAR command to the PCRF. +3. The PCRF performs session binding. +4. The PCRF replies with a Diameter AAA command back to the P-CSCF. +5. The PCRF requires access network information according to figure 5.2.2.2.1-1. +6. The PCRF forwards the access network information received in step 5 in a Diameter RAR. +7. The P-CSCF acknowledges the receipt of Diameter RAR. +8. IMS sends a SIP MESSAGE to the terminating side including the network provided location information. + +After, the P-CSCF terminates the AF session as described in subclause 4.3.1.2.3. + +## --- B.8 Retrieval of Network Provided Location Information for SMS over IP at Terminating side + +This clause covers the optional request of access network information for SMS over IP. + +![Sequence diagram showing the retrieval of access network information for SMS over IP at the terminating side. Entities: UE, PCRF, P-CSCF. 1. UE to P-CSCF: 200 OK. 2. P-CSCF to PCRF: Diameter AAR. 3. PCRF internal: Session Binding. 4. PCRF to P-CSCF: Diameter AAA. 5. PCRF internal: Request Access Network Info. 6. PCRF to P-CSCF: Diameter RAR. 7. P-CSCF to PCRF: Diameter RAA. 8. P-CSCF to external: 200 OK.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` +sequenceDiagram + participant UE + participant PCRF + participant P-CSCF + UE->>P-CSCF: 1. 200 OK + P-CSCF->>PCRF: 2. Diameter AAR + Note over PCRF: 3. Session Binding + PCRF->>P-CSCF: 4. Diameter AAA + Note over PCRF: 5. Request Access Network Info + PCRF->>P-CSCF: 6. Diameter RAR + P-CSCF->>PCRF: 7. Diameter RAA + P-CSCF->>External: 8. 200 OK +``` + +Sequence diagram showing the retrieval of access network information for SMS over IP at the terminating side. Entities: UE, PCRF, P-CSCF. 1. UE to P-CSCF: 200 OK. 2. P-CSCF to PCRF: Diameter AAR. 3. PCRF internal: Session Binding. 4. PCRF to P-CSCF: Diameter AAA. 5. PCRF internal: Request Access Network Info. 6. PCRF to P-CSCF: Diameter RAR. 7. P-CSCF to PCRF: Diameter RAA. 8. P-CSCF to external: 200 OK. + +**Figure B.8.1: Retrieval of Access Network Information for SMS over IP at terminating side** + +- 1.- The P-CSCF receives the 200 OK message on SIP MESSAGE request. +2. The P-CSCF requests the establishment of a new Diameter Rx session with the intention of retrieval the access network information. The P-CSCF sends a Diameter AAR command to the PCRF. +3. The PCRF performs session binding. +4. The PCRF replies with a Diameter AAA command back to the P-CSCF. +5. The PCRF requires access network information according to figure 5.2.2.2.1-1. +6. PCRF forwards the access network information received in step 5 in a Diameter RAR. +7. The P-CSCF acknowledges the receipt of Diameter RAR. +8. The P-CSCF forwards the 200 OK including the network provided location information. + +After, the P-CSCF terminates the AF session as described in subclause 4.3.1.2.3. + +# --- Annex C (normative): NAT Related Procedures + +## C.1 Support for media traversal of NATs using ICE + +The IMS calls out procedures for NAT traversal for media and signalling within IMS. One of the methods supported by IMS for media traversal of NATs is a UE controlled NAT traversal solution based on the IETF Interactive Connectivity Establishment (ICE) protocol, IETF RFC 8445 [67]. When a UE uses the ICE protocol for media traversal of NATs, additional enhancements to the existing PCC procedures are necessary to allow for proper ICE operation. + +This annex presents a set of rules that PCC network elements use to build flow descriptors, identify the proper UE IP addresses used by the PCRF for session and bearer binding, and gating control when the ICE procedures are invoked by the UE. + +In order for the ICE procedures to work a static, preconfigured PCC rule needs to be in place at the PCEF which allows the UE to perform STUN binding requests prior to offering or answering an SDP. + +- NOTE 1: Predefined PCC rules can be created to allow the UE to communicate with the STUN relay much in the same way the UE is allowed to communicate with the IMS network for session management. +- NOTE 2: Given that a STUN relay is a forwarding server under the direction of the UE, necessary precaution needs to be taken by the operator in how it chooses to craft these rules. It is recommended that such predefined rules only guarantee the minimal amount of bandwidth necessary to accomplish the necessary UE to STUN relay communication. Such an approach helps reduce the resources required to support NAT traversal mechanisms. Finally, such an approach allows the preconfigured rule to be over-ridden by dynamic rules which allow for the necessary bandwidth needed by the session. +- NOTE 3: The dynamic PCC rule will need to differentiate between different media traffic between UE and STUN relay (e.g. voice vs. video), which can be identified by the different ports assigned by the residential NAT. Session bindings need to take into account that the relevant terminal IP address may be contained within the ICE candidates contained in the session description, rather than in the normal media description. +- NOTE 4: It is assumed that the NAT device is located between the UE and the PCEF. NAT traversal outside of IMS in FBI services is considered FFS in the current 3GPP stage 2 specifications. +- NOTE 5: When a NAT device is located between the UE and the PCEF, it is assumed that the IP CAN session signalling will contain the IP address assigned by the residential NAT, rather than the UE IP address. +- NOTE 6: It is assumed that NAT devices that assign multiple IP addresses for the UE are outside the scope of release 7. +- NOTE 7: In this release, only one IP address per subscription is supported by session binding at the PCRF. Multiple Ues behind a NAT will use the same IP CAN session and IP address. + +## --- C.2 P-CSCF procedures + +### C.2.1 General + +The procedures in clause C.2 are only invoked in the case where the local UE (uplink SDP) has utilized the ICE protocol for media traversal of NATs. The P-CSCF can determine this by inspecting the UE provided SDP (uplink) for the "a=candidate" attribute(s). If such attributes are present this is an indication that the UE has invoked the ICE procedures as defined in IETF RFC 8445 [67] and IETF RFC 8839 [68] for media traversal of NATs and the P-CSCF shall follow the requirements in clause C.2. + +### C.2.2 Deriving the Ues IP address + +The P-CSCF shall set the Framed-IP-Address AVP or Framed-Ipv6-Prefix AVP to the source IP address of SIP messages received from the UE. + +### C.2.3 Deriving flow descriptions + +In the case where STUN Relay and ICE are used for NAT traversal, the UE is required to place the STUN Relay provided address in the “m=” and “c=” lines of its SDP. Given that these addresses cannot be used by the P-CSCF for building a valid flow description, the P-CSCF will need to determine if a STUN Relay address has been provided in the “m=” and “c=” lines of the UE provided SDP (uplink only). The P-CSCF shall make this determination by inspecting the uplink SDP for “a=candidate” attributes and compare the candidate address with that contained in the “c=” line. If a match is found, the P-CSCF shall then look at the candidate type. If the candidate type is “relay” then the address in the “c=” line is that of a STUN Relay server. In this case, the P-CSCF shall derive the Flow-Description AVP within the service information from the SDP candidate type of “relay” as follows: + +#### Uplink Flow-Description + +- Destination Address and Port: If the P-CSCF knows the destination address and port of the STUN Relay allocation that the UE is sending media to, it should use that information. If the P-CSCF does not know this address and port, it shall wildcard the uplink destination address and port. +- Source Address and Port: The P-CSCF shall populate the uplink source address with the “rel-addr” address and the uplink source port with the “rel-port” port contained within the “a=candidate” attribute. + +#### Downlink Flow-Description + +- Destination Address and Port: The P-CSCF shall populate the downlink destination address with the “rel-addr” address and the downlink destination port with the “rel-port” port contained within the “a=candidate” attribute. +- Source Address and Port: If the P-CSCF knows the source address and port of the STUN Relay allocation that the UE is receiving media from, it should use that information. If the P-CSCF does not know this address and port, it shall wildcard the downlink source address and port. + +For the other candidate types, the address in the “c=” and “m=” SDP attributes can be used for building the flow descriptor and the P-CSCF shall follow the rules to derive the Flow-Description AVP as described in table 6.2.2 of clause 6.2 of this TS. + +### C.2.4 Gating control + +If both endpoints have indicated support for ICE (both the SDP offer and answer contain SDP attributes of type “a=candidate”) ICE connectivity checks will take place between the two Ues. In order to allow these checks to pass through the PCEF, the P-CSCF shall enable each flow description for each media component upon receipt of the SDP answer. + +### C.2.5 Bandwidth impacts + +ICE has been designed such that connectivity checks are paced inline with RTP data (sent no faster than 20ms) and thus consumes a lesser or equal amount of bandwidth compared to the media itself (given the small packet size of a STUN connectivity check it is expected that the STUN connectivity checks will always have a smaller payload than the media stream itself). Thus, there are no additional requirements on the P-CSCF for bandwidth calculations for a given media flow. + +## --- C.3 PCRF procedures + +### C.3.1 General + +The procedures in clause C.3 are only invoked when the following two conditions are met: + +1. Both the local and remote UE have utilized the ICE protocol for media traversal of NATs (see clause C.2.1 for details on how this is determined); and +2. The IP-CAN which is servicing the IMS session does not support the concept of a default bearer. + +### C.3.2 Deriving additional flow descriptions + +The PCRF may need to develop additional flow descriptions (beyond those provided by the P-CSCF) for a media component based on additional candidate addresses present in the SDP offer/answer exchange. The PCRF shall follow the procedures defined in IETF RFC 8445 [67] and IETF RFC 8839 [68] for forming candidate pairs based on the data contained within the received Codec-Data AVP. For each candidate pair created based on the ICE procedures and not already present in the received flow descriptions, the PCRF shall add an uplink and downlink flow description for each media component. + +NOTE 1: The uplink SDP represents the local candidates while the downlink SDP represents the remote candidates. + +Following the ICE procedures for forming candidate pairs will result in some flow descriptions which would never be exercised. In particular, while the UE will send connectivity checks (and ultimately its media stream) from its host candidate, from the PCEF perspective, this will appear as being from the server reflexive address. Given this, the PCRF should not form flow descriptions using host candidate addresses and should only form additional flows based on server reflexive addresses and relay addresses. + +As candidates are removed from the SDP via subsequent offer/answer exchanges, the PCRF shall update its candidate pair list and shall remove any flow descriptors no longer being used. + +NOTE 2: If the default candidate (the candidate used to populate the "c=" and "m=" lines of both the uplink and downlink SDP) is chosen, then an updated SDP offer/answer will not be done, and any extra flow descriptions not being used by the session will not be removed. + +### C.3.3 Gating control + +For each additional flow description the PCRF adds to a media component (per clause C.3.2), the PCRF shall enable the flow in order to allow connectivity checks to pass. + +### C.3.4 Bandwidth impacts + +Per clause C.2.5 ICE is designed to have minimal impact on bandwidth policy control. However, it is possible that media will begin flowing while the ICE connectivity checks are still in progress. Given the possibility that no session update will be made (the default candidates will be chosen by the ICE protocol), it is not recommended that the PCRF adjust the bandwidth parameters provided by the P-CSCF. + +## --- C.4 P\_CSCF procedures to support media traversal through hosted NAT without ICE + +Both the media flows and the SIP signalling can traverse a NA(P)T device located in the customer premises domain, or “hosted NAT”, as described in Annex F of 3GPP TS 24.229 [5]. The hosted NAT will modify the source IP address and source port of uplink IP packets, and the destination IP address and port of downlink IP packets. The IP address and port information provided by the UE are thus not appropriate to configure PCC rules. + +The UE may use ICE procedures for hosted NAT traversal, and related PCC procedures are described in clauses C.1 to C.3. The present clause provides procedures to cover the case where ICE is not used. + +If the P-CSCF determines that the UE is located behind a hosted NAT (using procedures in Annex F of 3GPP TS 24.229 [5]) and that ICE is not used (using procedures in clause C.2.1), the P-CSCF shall, within the service information sent to the PCRF: + +- provide the source IP address of IP packets transporting incoming SIP messages from the UE as destination IP address of downlink media streams; +- for IPv4, provide the source IP address of IP packets transporting incoming SIP messages from the UE as source address of uplink media streams; +- for IPv6, derive the source address of uplink media streams from the prefix of the source IP address of IP packets transporting incoming SIP messages from the UE; +- wildcard source ports of uplink media streams; and +- wildcard destination ports of downlink media streams. +- provide the port information within SDP sent towards the served UE as source ports of corresponding downlink media streams. +- provide the port information within SDP sent towards the served UE as destination ports of corresponding uplink media streams. + +# --- Annex D (normative): Access specific procedures for GPRS + +## D.1 General + +The present annex defines IP-CAN specific requirements for General Packet Radio Service (GPRS). + +## --- D.2 Binding Mechanisms + +Depending on the bearer control mode, bearer binding can be executed either by PCRF, PCEF or both PCRF and PCEF. + +- For “UE-only” IP-CAN bearer establishment mode, the PCRF performs bearer binding. +- For “UE/NW” IP-CAN bearer establishment mode, the PCRF performs the binding of the PCC rules for user controlled services while the PCEF performs the binding of the PCC rules for the network controlled services. + +If the PCEF performs the bearer binding, the PCRF shall follow the procedures as described in clause 5.4 with the exceptions described in this subclause. + +If the Bearer Binding function is located at the PCEF, the PCEF shall check the QCI and ARP indicated by the PCC Rule(s) and bind the PCC rule with an IP-CAN bearer that has the same QCI and Evolved ARP (if this is supported by the SGSN). + +If there is no suitable PDP-Context to accommodate a PCC rule when PCEF performs the bearer binding, the PCEF shall initiate the establishment of PDP-Contexts as specified in 3GPP TS 23.060 [3]. + +The PCEF shall not combine PCC rules with different ARP to the same bearer. If the Evolved ARP parameter is not supported by the SGSN, the PCEF shall map the Evolved ARP to Rel-99 ARP as specified in clause B.3.3.3 of 3GPP TS 29.212 [9]. + +NOTE: If Evolved ARP is not supported by the SGSN then this enables a modification of the PDP context ARP without impacting the bearer binding after relocation to a SGSN that supports Evolved ARP. + +If the Bearer Binding function is located at the PCRF, the PCRF shall compare the TFT(s) of all IP-CAN bearer(s) within the IP-CAN session received via PCEF from the UE with the existing service data flow filter information. The PCRF shall indicate to the PCEF the IP-CAN bearer within the IP-CAN session where the PCC Rules shall be installed, modified or removed. This is done including the Bearer-Identifier AVP together with the associated PCC Rules within the corresponding RAR and/or CCA commands. + +- When the PCRF does not require additional filter information coming from the UE in order to decide on bearer binding, the PCRF shall supply the PCC rules to be installed over the Gx interface to the PCEF within a RAR command. +- Otherwise, the PCRF shall wait for the PCEF requesting a policy decision for the establishment of a new IP-CAN bearer or the modification of an existing one within a CCR command over the Gx interface. +- When the PCEF reports the bearer event, it shall include within the CCR command a bearer reference together with the new or modified TFT information, the QCI and associated bitrates for new or modified PDP-Contexts. + +## --- D.3 PCC Procedures + +### D.3.1 IP-CAN Session Modification + +#### D.3.1.1 Network-initiated IP-CAN Session Modification + +Network-initiated IP-CAN session modification is executed according to clause 4.3.1.1 with the following differences: + +- The timer in step 4 will also be activated waiting for one of the following cases: + - If the authorized QoS for an IP-CAN bearer is changed or + - If one or more Flow Descriptions need to be added, deactivated or removed in any of the PCC rules bound to an IP-CAN bearer +- If the timer in step 4 expires and the PCRF still requires additional filter information coming from the UE in order to decide on bearer binding for new PCC rules to be installed, all subsequent steps in figure 4.3.1.1.1 shall not be executed, and further reactions of the PCRF are left unspecified. As a possible option, the PCRF could abort the AF session. +- When the PCRF performs the bearer binding, once the PCC rules are selected, the PCRF identifies the IP-CAN bearer for each of the PCC rules and the authorized QoS. The PCRF may provision PCC Rules and authorized QoS for several IP-CAN Bearers within the same RAR command. +- For step 9, IP-CAN session signalling, the subsequent steps are executed separately for each IP-CAN bearer under the following conditions: + - if all PCC rules bound to a PDP context have been removed or deactivated (PDP Context deactivation is applicable) + - if one or more PDP contexts have to be modified + - if in UE/NW Bearer Control Mode, the GGSN needs to establish a new PDP context(PDP Context establishment is applicable) if the bearer binding is located at the PCEF. + +The GGSN initiates the procedure to Create/Update or Terminate PDP Context Request message to the SGSN. If in the case of updating the PDP Context the authorized QoS for the bearer has changed, the GGSN will modify the UMTS QoS parameters accordingly. + +When the procedure in step 9 is completed and requires notifications from the GW, for an IP-CAN Bearer termination in UE-Only Bearer Control Mode, the GGSN sends a Diameter CCR with the Bearer-Identifier and Bearer-Operation AVPs to indicate “Termination”. + +#### D.3.1.2 PCEF-initiated IP-CAN Session Modification + +PCEF-initiated IP-CAN Session Modification procedure shall take place according to clauses 4.3.2.1 and 4.3.2.2 except for those procedures initiated by the UE, as described in the clauses below. + +##### D.3.1.2.1 UE-initiated IP-CAN Bearer Establishment or IP-CAN Bearer Modification + +This clause is applicable for the establishment of a new IP-CAN Bearer (other than the one which created the IP-CAN session) and for the modification of an already established IP-CAN Bearer. The signalling flows for these cases are as per Figure 4.3.1.2.1. + +A bearer-event-initiated Request of PCC Rules occurs when a new bearer is established or when an existing bearer is modified. For GPRS, these are PDP Context Modification(s) or secondary PDP context Activation(s). An IP-CAN Session modification triggers a PCC Rule request only if the PCRF has previously requested a PCC Rule request for the given modification event. + +![Sequence diagram for UE-initiated IP-CAN Bearer Establishment and Modification. Lifelines: GW, PCRF, SPR, AF. The diagram shows 15 steps of interaction between these entities. Solid arrows represent mandatory messages, and dashed arrows represent conditional messages. Annotations explain the conditions for steps 5, 7, 14, and 15.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant UE + participant GW + participant PCRF + participant SPR + participant AF + + Note left of GW: 1. IP-CAN Bearer signalling + GW->>PCRF: 2. Diameter CCR + Note right of PCRF: 3. Store Bearer Information + Note right of PCRF: 4. Bind IP CAN session to any existing AF session(s) + Note right of PCRF: 5. Profile Request (Conditional: If the PCRF needs subscription-related information and does not have it) + PCRF-->>SPR: 6. Profile Response + Note right of PCRF: 7. Diameter RAR (Conditional: For IP CAN session modification, if requested by AF at initial authorisation) + PCRF-->>AF: 8. Diameter RAA + Note right of PCRF: 9. PCC Rules Decision, Policy Decision + Note right of PCRF: 10. Store PCC Rules + PCRF->>GW: 11. Diameter CCA + Note right of GW: 12. Installation Modification or Removal of PCC Rules, Policy Enforcement + Note left of GW: 13. IP CAN Bearer signalling response + Note right of PCRF: 14. Start of Timer. (Conditional: For GPRS, for each affected other bearer where previous authorized QoS is modified) + Note right of PCRF: 15. Interactions in Figure 4.3.1.1.1 (Conditional) + +``` + +**Legend:** + +- **Mandatory** +- **Conditional** + +Sequence diagram for UE-initiated IP-CAN Bearer Establishment and Modification. Lifelines: GW, PCRF, SPR, AF. The diagram shows 15 steps of interaction between these entities. Solid arrows represent mandatory messages, and dashed arrows represent conditional messages. Annotations explain the conditions for steps 5, 7, 14, and 15. + +**Figure D.3.1.2.1: UE-initiated IP-CAN Bearer Establishment and Modification.** + +- The GW receives IP-CAN Bearer signalling that is a trigger for a PCC Rule request. For GPRS, the GGSN receives a secondary Establish PDP Context Request or an Update PDP Context Request. +- The GW informs the PCRF of the modification of the IP-CAN Session due to the IP-CAN Bearer signalling in step 1, using a Diameter CCR with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The GW reuses the existing Gx DCC session corresponding to the IP-CAN Session. + +If the IP-CAN Bearer signalling in step 1 established a new IP-CAN Bearer, the GW assigns a new bearer identifier to this IP-CAN Bearer. The GW provides information about the new or modified bearer, e.g. requested QoS and TFT filters. If the event that caused the bearer modification applies uniquely to that bearer and PCRF performs the bearer binding, then, the bearer identifier should be provided within the CCR. If no bearer identifier is provided, the event trigger will apply to the IP-CAN session. + +3. The PCRF stores the received information in the Diameter CCR. +4. The PCRF binds the IP-CAN Session to existing AF session(s) using the information received from the GW and the Service Information included in the stored PCC rules, which was previously received from the AF(s) , as depicted in figure 4.3.1.1.1. +The PCRF also binds the IP-CAN Bearers within the IP-CAN Session to all matching IP flow(s) of existing AF session(s) using the bearer information received from the GW and the Service Information received from the AF(s). If IP flow(s), which have previously been bound to other bearers, have been bound to the modified bearer, PCC Rules in other bearer(s) may need to be removed. For GPRS, an IP flow may need to be removed if a matching higher priority TFT filter in the newly established PDP context takes precedence over a matching lower priority TFT filter in another PDP context. Furthermore, if IP Flow(s), which have previously been bound to the modified bearer are bound to other bearer(s), PCC Rules may need to be installed in other bearers. For GPRS, an IP flow may be bound to another PDP context if it was previously bound to the modified PDP context due to a removed higher priority TFT filter, and a lower priority TFT filter in the other PDP context matches the IP flow. +5. If the PCRF requires subscription-related information and does not have it, the PCRF sends a request to the SPR in order to receive the information. +6. The SPR replies with the subscription related information containing the information about the allowed service(s) and PCC Rules information. + +NOTE: For steps 5 and 6: The details associated with the Sp reference point are not specified in this Release. The SPR's relation to existing subscriber databases is not specified in this Release. + +7. For IP CAN session modification, if the AF requested a notification of the corresponding event at the initial authorisation of the AF session, the PCRF shall sent a Diameter RAR with the Specific-Action AVP set to indicate the trigger event that caused the request. +8. If step 7 happens, the AF replies with a Diameter RAA and may provide updated service information within. +9. The PCRF selects the new PCC Rule(s) to be installed. The PCRF can also identify existing PCC Rules that need to be modified or removed. The PCC Rules may relate to any of the matching AF sessions identified in step 4 or may exist in the PCRF without matching to any AF session. The PCRF may also make a policy decision by defining an authorized QoS and by deciding whether service flows described in the PCC Rules are to be enabled or disabled. + +For types of IP-CAN, where the PCRF controls IP-CAN Bearers, e.g. GPRS, the PCC Rules may affect the IP-CAN Bearer identified in the CCR of step 2 or any other IP-CAN Bearer identified in step 4. + +10. The PCRF stores the modified PCC Rules. +11. The PCC Rules are provisioned by the PCRF to the GW using Diameter CCA. The PCRF may also provide authorized QoS. The PCRF identifies the affected IP-CAN Bearer for each of the PCC Rules and the authorized QoS. The PCRF may provision PCC Rules and authorized QoS for several IP-CAN Bearers within the same CCA. +12. The GW installs the received PCC Rules. The GW also enforces the authorized QoS and enables or disables service flow according to the flow status of the corresponding PCC Rules. +13. The GW sends a response to the IP-CAN Bearer signalling in step 1. +For GPRS, the GGSN accepts the secondary Establish PDP Context Request or the Update PDP Context Request based on the results of the authorisation policy decision enforcement and sends an Establish PDP Context Response or Update PDP Context Response. If the requested QoS parameters do not correspond to the authorized QoS, the GGSN adjusts (downgrades/upgrades) the requested UMTS QoS parameters to the authorized values. + +The PCRF may have decided in step 4 to modify PCC Rules and/or authorized QoS of other IP CAN bearers than the IP-CAN Bearer identified in the CCR of step 2. For each such other IP-CAN Bearer identified in step 4, the GGSN executes the following steps. + +14. The PCRF may start a timer to wait for PDP context modification requests from the UE. +15. The PCRF interacts with the GW according to figure 4.3.1.1.1. + +##### D.3.1.2.2 UE-initiated IP-CAN Bearer Termination + +This clause is applicable if an IP-CAN Bearer is being released while other IP-CAN Bearers and thus the IP-CAN Session are not released. + +For the termination of IP-CAN Bearers, three cases are covered: + +- Bearer release that does not cause service data flow(s) within an AF session to be disabled; +- Bearer release that causes at least one but not all the service data flow(s) within an AF session to be disabled; and +- Bearer release that causes all the service data flows within an AF session to be disabled. + +A Bearer release may not cause a service data flow within this bearer to be disabled if the IP flow can be bound to another bearer. For GPRS, an IP flow can be bound to another PDP context if a lower precedence TFT filter matching the IP flow is installed at the other PDP context. + +![Sequence diagram for UE-Initiated IP-CAN Bearer Termination showing interactions between GW, PCRF, and AF.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The sequence diagram illustrates the interaction between the Gateway (GW), Policy and Charging Rules Function (PCRF), and Application Function (AF) for UE-Initiated IP-CAN Bearer Termination. The process begins with an external 'Remove IP-CAN Bearer Request' to the GW. The GW sends a 'Diameter CCR' to the PCRF. The PCRF identifies IP flows, makes a PCC rule decision, and stores PCC rules. The PCRF sends a 'Diameter CCA' back to the GW. The GW then removes PCC rules and sends a 'Remove IP-CAN Bearer Response' back to the requester. The PCRF also installs PCC rules for policy enforcement. There are two conditional branches: one if IP flows were moved to other bearers, and another if all service data flows within the AF session are affected. The legend indicates that solid arrows represent mandatory messages and dashed arrows represent conditional messages. + +``` +sequenceDiagram + participant UE + participant GW + participant PCRF + participant AF + + Note left of UE: Remove IP-CAN Bearer Request + UE->>GW: 1. Remove IP-CAN Bearer Request + GW->>PCRF: 2. Diameter CCR + Note right of PCRF: 3. Identify the IP flows bound to the session or bearer. + Note right of PCRF: 4. PCC Rules Decision. Policy Decision + Note right of PCRF: 5. Store PCC Rules + PCRF->>GW: 6. Diameter CCA + Note right of GW: 7. Remove PCC Rules + GW->>UE: 8. Remove IP-CAN Bearer Response + Note right of GW: 9. Install PCC Rules. Policy Enforcement + + Note right of PCRF: If IP Flow(s) were moved to other bearer(s) + Note right of AF: If IP Flow(s) were moved to other bearer(s) + + Note right of PCRF: If all the service data flows within AF session are affected + PCRF->>AF: 10. Diameter ASR + AF->>PCRF: 11. Diameter ASA + PCRF->>AF: 12. Diameter STR + AF->>PCRF: 13. Diameter STA + + Note right of PCRF: If not all the service data flows within AF session are affected + PCRF->>AF: 10a. Diameter RAR + AF->>PCRF: 11a. Diameter RAA + PCRF->>AF: 12a. Diameter AAR + AF->>PCRF: 13a. Diameter AAA +``` + +**Legend:** + +- > **Mandatory** +- - - - -> **Conditional** + +Sequence diagram for UE-Initiated IP-CAN Bearer Termination showing interactions between GW, PCRF, and AF. + +Figure D.3.1.2.2: UE-Initiated IP-CAN Bearer Termination + +1. The GW receives a Remove IP-CAN Bearer Request that request the deactivation of an IP-CAN Bearer while other IP-CAN Bearers and thus the IP-CAN Session are not released. The form of the Remove IP-CAN Bearer Request depends upon the type of the IP-CAN. For GPRS, the GGSN receives a Delete PDP Context Request. +2. The GW sends a Diameter CCR message with the CC-Request-Type AVP set to the value UPDATE\_REQUEST to the PCRF, indicating the IP-CAN Bearer termination. +3. The PCRF identifies the IP flows bound to the removed bearer and updates the stored bearer information. The PCRF re-evaluates the binding of IP flows, as IP flows may now be bound to other bearers. For GPRS, an IP flow may be bound to another PDP Context if it was previously bound to the removed PDP context due to a higher priority TFT filter, and a lower priority TFT filter in another PDP context matches the IP flow. + +The following steps 4 and 5 are performed for each of the other bearers identified in step 3: + +4. The PCRF selects the PCC Rule(s) to be installed or modified for the affected bearer. The PCRF may also update the policy decision for this bearer. +5. The PCRF stores the updated PCC Rules for the affected bearer. +6. The PCRF acknowledges the bearer termination by sending a Diameter CCA message. +The PCRF provides PCC Rules and possibly updated authorized QoS for each of the other bearers identified in step 3. The PCRF identifies the affected IP-CAN Bearer for each of the PCC Rules and the authorized QoS. +7. The GW removes those PCC Rules, which have not been moved to other IP CAN bearers by the CCA message and are installed in the IP-CAN bearer, for which a termination has been requested in step 1. +8. The GW sends a Remove IP-CAN Bearer Response. For GPRS, the GGSN sends the Delete PDP Context Response message. +9. If the PCRF has provided PCC Rules and possibly updated authorized QoS for other bearers in step 6, the GW installs or modifies the identified PCC Rules. The GW also enforces the authorized QoS and enables or disables service flow according to the flow status of the corresponding PCC Rules. + +The following steps 10 to 13 or 10a to 13a apply for the case where at least one IP Flow within an AF session is being disabled, i.e. if the IP Flow is not bound to any other bearer that is still established. The steps shall be performed separately for each ongoing AF session that is affected by the bearer release as explained below. + +If all IP flow(s) within the AF session are disabled by the bearer release: + +10. The PCRF indicates the session abort to the AF by sending a Diameter ASR message to the AF. +11. The AF responds by sending a Diameter ASA message to the PCRF. +12. The AF sends a Diameter STR message to the PCRF to indicate that the session has been terminated. +13. The PCRF responds by sending a Diameter STA message to the AF. + +If at least one but not all of the IP flow(s) within the AF session are disabled by the bearer release, and the AF has requested notification of bearer removal: + +- 10a. The PCRF indicates the release of the bearer by sending a Diameter RAR to the AF. +- 11a. The AF responds by sending a Diameter RAA to the PCRF. +- 12a. The AF may send an AAR to the PCRF to update the session information. +- 13a. If step 12a occurs, the PCRF responds by sending a AAA to the AF. + +# --- Annex E (normative): Fixed Broadband Access Interworking with EPC + +## E.1 General + +The present annex defines specific requirements for Fixed Broadband Access Interworking with EPC. + +## --- E.2 Definitions and abbreviations + +### E.2.1 Definitions + +**UE local IP address** is defined as: either the public Ipv4 address and/or Ipv6 address/Ipv6 network prefix assigned to the UE by the BBF domain in the no-NAT case, or the public Ipv4 address assigned by the BBF domain to the NATed RG that is used for this UE. + +**H(e)NB local IP address** is defined as: either the public Ipv4 address and/or Ipv6 address/Ipv6 network prefix assigned to the H(e)NB by the BBF domain in the no-NAT case, or the public Ipv4 address assigned by the BBF domain to the NATed RG that is used for this H(e)NB. + +**Non-seamless WLAN offload (NSWO)** is defined as: a capability of routing specific IP flows over the WLAN access without traversing the EPC as defined in clause 4.1.5 of 3GPP TS 23.402 [21]. + +**Non-seamless WLAN offload APN (NSWO-APN)** is defined as: an APN allowing the BPCF to indicate to PCRF that for subscribers of a certain HPLMN the IP-CAN session is related to NSWO traffic. + +**EPC-routed traffic** is defined as: User plane traffic that is routed via a PDN GW in EPC as part of a PDN Connection. EPC-routed traffic applies to non-roaming, roaming with home routed and roaming with visited access cases. + +### E.2.2 Abbreviations + +The following abbreviations are relevant for this annex only: + +| | | +|----------|------------------------------------| +| BBF | Broadband Forum | +| BPCF | Broadband Policy Control Function | +| NA(P)T | Network Address (Port) Translation | +| NSWO | Non-Seamless WLAN offload | +| NSWO-APN | Non-Seamless WLAN offload APN | +| RG | Residential Gateway | + +## --- E.3 Binding Mechanisms + +### E.3.1 EPC-routed traffic + +For EPC- routed traffic, binding mechanisms apply as defined insub clause 5.1 by PCRF, PCEF and BBERF. In addition, if both a Gx and associated S9a session exist for the same IP-CAN session, the PCRF shall generate QoS Rules for all the authorized PCC rules. + +### E.3.2 NSWO traffic + +The binding mechanism includes two steps for the NSWO traffic: + +1. Session binding. +2. PCC rule authorization. + +For NSWO traffic, session binding of AF session to an IP-CAN session is performed by the PCRF for the purpose of policy control in the Fixed Broadband access network. + +When the PCRF accepts an AA-Request from the AF over the Rx interface with service information, the PCRF shall perform session binding and associate the described service IP flows within the AF session information (and therefore the applicable PCC rules) to one and only one existing IP-CAN session. This association is done comparing the user IP address received via the Rx interface in either the Framed-IP-Address AVP or the Framed-Ipv6-Prefix AVP with the Ipv4 address or Ipv6 address/Ipv6 prefix received via the S9a or S9 interface. The user identity if present in the Subscription-Id AVP and the PDN information if available in the Called-Station-Id AVP may also assist on this association. + +The PCRF determines that the UE has an IP-CAN session if the IP address (Ipv4 or Ipv6) received over the Rx interface matches the Ipv4 address or Ipv6 address/Ipv6 prefix received via one or more of the following interfaces: S9a interface and S9 interface, and if the user identity is used to assist the association, the user identity received over the Rx interface matches the user identity received via one or more of the following interfaces: S9a interface and S9 interface. + +NOTE 1: In case the user identity in the IP-CAN and the application level identity for the user are of different kinds, the PCRF needs to obtain the mapping between the identities. Such mapping is not subject to specification within this TS. + +NOTE 2: An Ipv6 address provided over Rx matches an Ipv6 prefix provided over S9a or S9 if the Ipv6 address belongs to the Ipv6 (sub-)network prefix. + +As a result from the session binding function, the PCRF identifies what IP-CAN session the current AF session is related with. If the PCRF is not capable of executing the Session Binding, the PCRF shall issue an AA-Answer command to the AF with a negative response. + +NOTE: For roaming cases, the H-PCRF performs session binding of the AF session to an IP-CAN session. + +The PCRF derives and authorises PCC rules as described in clause 5. + +## --- E.4 PCC Procedures + +### E.4.1 Introduction + +From the network scenarios listed in clause 4.0, in order to support interworking with Fixed Broadband access network, three distinct network scenarios are defined as follows: + +- the Case 1 (no Gateway Control Session over Gxx reference point) applies to GTP-based S2a or GTP-based S2b, trusted S2c and GTP-based S5/S8 H(e)NB scenarios. +- the Case 2a (the same Gateway Control Session over Gxx reference point) applies to untrusted S2c. +- the Case 2b (a Gateway Control Session over Gxx reference point per IP-CAN Session) applies to PMIP-based S2b and PMIP-based S5/S8 H(e)NB scenarios. + +NOTE: No policy interworking solution based on S9a is defined for Fixed Broadband access interworking via S2a in this Release. + +Additionally, for case 1, the PCRF checks whether the CoA information is included in the CC-Request command to differentiate the GTP-based S2b case and trusted S2c case. If it is included, the trusted S2c case applies; otherwise, the GTP-based S2b case applies. + +### E.4.2 IP-CAN Session Establishment + +#### E.4.2.1 IP-CAN Session Establishment for EPC- routed traffic + +This procedure is applicable for WLAN and H(e)NB scenarios for EPC-routed traffic. This procedure is same as described in clause 4.1 with the exceptions described in this clause. + +![Sequence diagram for IP-CAN Session Establishment for EPC-routed traffic. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, SPR, OCS. The diagram shows two main phases: Step 1-6 and Step 7-15. Step 1-6 involves Diameter messages (TER/RAR, TEA/RAA, CCR, CCA) between BPCF, V-PCRF, and H-PCRF, with internal processing steps like 'Store information'. Background shading indicates different roaming cases: Roaming case (Home Routed, case 1), Roaming case (Visited Access, case 2a or case 2b).](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +The diagram illustrates the IP-CAN Session Establishment for EPC-routed traffic across various roaming scenarios. The lifelines involved are BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, SPR, and OCS. + +**Phase 1: Perform step 1 through step 6: as specified in Figure 4.1.1: IP-CAN session establishment** + +- Roaming case (Home Routed, case 1):** + - BPCF sends 2. Diameter TER/RAR to H-PCRF. + - H-PCRF sends 2a. Diameter TER/RAR to V-PCRF. + - V-PCRF sends 2b. Diameter TER/RAR to BPCF. + - BPCF sends 3. Diameter TEA/RAA to H-PCRF. + - H-PCRF sends 3a. Diameter TEA/RAA to V-PCRF. + - V-PCRF sends 3b. Diameter TEA/RAA to BPCF. + - BPCF sends 4. Diameter CCR to H-PCRF. + - H-PCRF sends 4a. Diameter CCR to V-PCRF. + - V-PCRF performs 4b. Store information. + - V-PCRF sends 4c. Diameter CCR to H-PCRF. + - H-PCRF sends 6. Diameter CCA to BPCF. + - H-PCRF sends 6a. Diameter CCA to V-PCRF. + - V-PCRF sends 6b. Diameter CCA to BPCF. +- Roaming case (Visited Access, case 2a or case 2b):** + - BPCF sends 2c. Diameter TER/RAR to H-PCRF. + - BPCF sends 3c. Diameter TEA/RAA to H-PCRF. + - BPCF sends 4d. Diameter CCR to H-PCRF. + - H-PCRF performs 4e. Store information. + - H-PCRF performs 5. Store information. + - H-PCRF sends 6c. Diameter CCA to BPCF. + +**Phase 2: Perform step 7 through step 15: as specified in Figure 4.1.1: IP-CAN session establishment** + +Sequence diagram for IP-CAN Session Establishment for EPC-routed traffic. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, SPR, OCS. The diagram shows two main phases: Step 1-6 and Step 7-15. Step 1-6 involves Diameter messages (TER/RAR, TEA/RAA, CCR, CCA) between BPCF, V-PCRF, and H-PCRF, with internal processing steps like 'Store information'. Background shading indicates different roaming cases: Roaming case (Home Routed, case 1), Roaming case (Visited Access, case 2a or case 2b). + +**Figure E.4.2.1.1 IP-CAN Session Establishment for EPC-routed traffic** + +1. Step 1 through step 6: as specified in Figure 4.1.1: IP-CAN session establishment are executed towards the H-PCRF (non-roaming case or home routed case) or towards the V-PCRF (roaming case). + +For case 2a and case 2b of the WLAN scenario and for case 2b of the H(e)NB scenario, the BBERF provides the data as described in 3GPP TS 29.212 [9], clause E.5.2. + +For case 1, the PCEF provides the data as described in 3GPP TS 29.212 [9], clause E.5.1. + +For case 1 (visited access), case 2a and case 2b (home routed and visited access) the V-PCRF forwards the data towards the H-PCRF. + +NOTE: For the roaming case, the V-PCRF omits the UE Local IP address (WLAN scenario), the H(e)NB Local IP address and the UDP port in the S9 reference point. + +2. For GTP/PMIP-based S2b of the WLAN scenario (non-roaming case) the PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure triggered by the Gateway Control session establishment or Indication of IP-CAN session establishment in step 1. + +For trusted and untrusted S2c of the WLAN scenario (non roaming case), when there is not an already established S9a session for the user, the PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure triggered by the Gateway Control session establishment in step 1; otherwise, the PCRF may send a RAR command to BPCF to provide the QoS rules to the BPCF. + +For H(e)NB scenario (non roaming case), when there is not an already established S9a session for the H(e)NB Local IP address, the PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure triggered by the Gateway Control session establishment or Indication of IP-CAN session establishment in step 1; otherwise, the PCRF may send a RAR command to BPCF to provide the QoS rules to the BPCF. + +The PCRF provides the data as described in 3GPP TS 29.215 [22], clause A.5.1.1 + +For case 1 (roaming with home routed case), the steps 2a and step 2b are executed instead of step 2. + +- 2a. If there is not an already established S9 session for the user, the H-PCRF sends a TER command to V-PCRF to trigger an S9 session establishment procedure triggered by the Indication of IP-CAN session establishment in step 1; otherwise, the H-PCRF sends a RAR command to V-PCRF to trigger an S9 subsession establishment procedure. + +The H-PCRF trigger an S9 session/subsession establishment procedure as described in 3GPP TS 29.215 [22], clause A.6.1.1.1 or A.6.3.1.0. + +- 2b. For GTP-based S2b of the WLAN scenario, the V-PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure. + +For trusted S2c of the WLAN scenario, if there is not an already established S9a session for the user, the V-PCRF sends a TER command to BPCF; otherwise, the PCRF may send a RAR command to BPCF to provide the QoS rules to the BPCF. + +For the H(e)NB scenario and if there is not an already established S9a session for the H(e)NB local IP address, the V-PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure; otherwise the V-PCRF may send a RAR command to BPCF to provide the QoS rules to the BPCF. + +The V-PCRF provides the data as described in 3GPP TS 29.215 [22], clause A.5.1.1. + +For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), step 2c is executed instead of step 2. + +- 2c. For trusted and untrusted S2c of the WLAN scenario when there is not an already established S9a session for the user, the V-PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure; otherwise, the PCRF may send a RAR command to BPCF to provide the QoS rules to the BPCF. + +For GTP/PMIP-based S2b of the WLAN scenario the V-PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure. + +For case 1 and case 2b of the H(e)NB scenario when there is not an already established S9a session for the H(e)NB local IP address, the V-PCRF sends a TER command to BPCF to trigger an S9a session establishment procedure; otherwise, the V-PCRF may send a RAR command to provide the QoS rules to the BPCF. + +The V-PCRF provides the data as described in 3GPP TS 29.215 [22], clause A.5.1.1. + +3. The BPCF acknowledges to the PCRF by sending the TEA /RAA command. + +For case 1(roaming with home routed case), steps 3a and step 3b are executed instead of step 3. + +- 3a. The BPCF acknowledges to the V-PCRF by sending the TEA /RAA command. + +- 3b. The V-PCRF acknowledges to the H-PCRF by sending the TEA/RAA command. + +For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), step 3c is executed instead of step 3. + +- 3c. The BPCF acknowledges to the V-PCRF by sending the TEA/RAA command. + +4. For the non-roaming case, triggered by step 2, the BPCF initiates an S9a session establishment with the PCRF by sending a CCR to the PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The BPCF provides the data as described in 3GPP TS 29.215 [22], clause A.5.1.2. + +For case 1 (roaming with home routed case), the steps 4a~4c are executed instead of step 4. + +- 4a. Triggered by step 2b, the BPCF initiates an S9a session establishment with the V-PCRF by sending a CCR to the V-PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The BPCF provides the data as described in 3GPP TS 29.215 [22], clause A.5.1.2. + +- 4b. The V-PCRF determines that the request is for a roaming user and stores the received information. + +- 4c. If there is not an already established S9 session for the user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this IP-CAN session within the Subsession-Id AVP, and the Subsession-Operation AVP set to the value ESTABLISHMENT. If there is an already established S9 session for this roaming user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this IP-CAN session within the Subsession-Id AVP, and the Subsession-Operation AVP set to the value ESTABLISHMENT. + +For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), the steps 4d~step 4e are executed instead of step 4. + +4d. Triggered by step 2c, the BPCF initiates an S9a session establishment with the V-PCRF by sending a CCR to the V-PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The BPCF provides the data as described in 3GPP TS 29.215 [22], clause A.5.1.2. + +4e. The V-PCRF determines that the request is for a roaming user and stores the received information. + +5. The H-PCRF stores the information received in the CCR. + +6. For the non-roaming case, the H-PCRF acknowledges the S9a session establishment by sending a CCA to the BPCF. + +For case 1 (roaming with home routed case), steps 6a~6b are executed instead of step 6. + +6a. The H-PCRF acknowledges the S9 session establishment/modification by sending a CCA to the V-PCRF. + +6b. The V-PCRF acknowledges the S9a session establishment by sending a CCA to the BPCF. + +For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), the step 6c is executed instead of step 6. + +6c. The V-PCRF acknowledges the S9a session establishment by sending a CCA to the BPCF. + +7. Step 7 through step 15: as specified in Figure 4.1.1: IP-CAN session establishment are executed. Step 13 is only applicable to case 2b of H(e)NB scenario. + +#### E.4.2.2 IP-CAN Session Establishment for NSWO traffic + +![Sequence diagram for IP-CAN Session Establishment for NSWO traffic. Lifelines: BPCF, V-PCRF, H-PCRF, TDF, SPR. The diagram shows a non-roaming case and two roaming cases. The non-roaming case involves BPCF sending a Diameter CCR to H-PCRF, which then performs steps 5-11. The first roaming case involves BPCF sending a Diameter CCR to V-PCRF, which stores information and sends a Diameter CCR to H-PCRF. The second roaming case involves H-PCRF sending a Diameter CCA to V-PCRF, which stores PCC rules and sends a Diameter CCR to H-PCRF. A legend indicates that solid arrows are Mandatory and dashed arrows are Conditional.](164d1b48231be457522b31965610ea3b_img.jpg) + +``` + +sequenceDiagram + participant BPCF + participant V-PCRF + participant H-PCRF + participant TDF + participant SPR + + Note left of BPCF: 1. Trigger + BPCF->>H-PCRF: 2. Diameter CCR + Note right of BPCF: ROAMING CASE + BPCF->>V-PCRF: 2a. Diameter CCR + V-PCRF->>V-PCRF: 2b. Store Information + V-PCRF->>H-PCRF: 2c. Diameter CCR + H-PCRF->>H-PCRF: 3. Store Information + H-PCRF->>TDF: 4. Perform step 5 through 11: as specified in Figure 4.1.1: IP-CAN session establishment + H-PCRF->>BPCF: 5. Diameter CCA + Note right of BPCF: ROAMING CASE + H-PCRF->>V-PCRF: 5a. Diameter CCA + V-PCRF->>V-PCRF: 5b. Store PCC Rules, if available, Policy Decision + V-PCRF->>H-PCRF: 5c. Diameter CCR + H-PCRF->>V-PCRF: 5d. Diameter CCA + V-PCRF->>TDF: 5e. TDF session establishment + V-PCRF->>BPCF: 5f. Diameter CCA + + Note right of SPR: Legend + solid arrow: Mandatory + dashed arrow: Conditional + +``` + +Sequence diagram for IP-CAN Session Establishment for NSWO traffic. Lifelines: BPCF, V-PCRF, H-PCRF, TDF, SPR. The diagram shows a non-roaming case and two roaming cases. The non-roaming case involves BPCF sending a Diameter CCR to H-PCRF, which then performs steps 5-11. The first roaming case involves BPCF sending a Diameter CCR to V-PCRF, which stores information and sends a Diameter CCR to H-PCRF. The second roaming case involves H-PCRF sending a Diameter CCA to V-PCRF, which stores PCC rules and sends a Diameter CCR to H-PCRF. A legend indicates that solid arrows are Mandatory and dashed arrows are Conditional. + +Figure E.4.2.2.1: IP-CAN Session Establishment for NSWO traffic + +1. The broadband access network becomes aware of the IMSI of the 3GPP UE if 3GPP-based access authentication (EAP-AKA/AKA') is performed. The BPCF also becomes aware of the UE local IP address. +2. For the non-roaming case, the BPCF initiates an S9a\* session establishment procedure with the H-PCRF by sending a CCR using the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The BPCF shall provide the data as described in 3GPP TS 29.215 [22], clause A.5.1.2.1. + +For the roaming case, steps 2a~2c are executed instead of step 2. + +- 2a. The BPCF initiates an S9a\* session establishment procedure with the V-PCRF by sending a CCR to the V-PCRF using the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The BPCF shall provide the data as described in 3GPP TS 29.215 [22], clause A.5.1.2.1. +- 2b. The V-PCRF determines that the request is for a roaming user and stores the received information. +- 2c. If there is not an already established S9 session for this roaming user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this IP-CAN session within the Subsession-Id AVP, and the Subsession-Operation AVP set to the value ESTABLISHMENT. + +If there is an already established S9 session for this roaming user, the V-PCRF sends a CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The V-PCRF includes the Subsession-Enforcement-Info AVP within the CCR with a new S9 subsession identifier assigned by the V-PCRF to this IP-CAN session within the Subsession-Id AVP, and the Subsession-Operation AVP set to the value ESTABLISHMENT. + +3. The H-PCRF stores the information received in the CCR. +4. Perform step 5 through 11: as specified in Figure 4.1.1: IP-CAN session establishment. Additionally, an indication on whether policy control for NSWO traffic should be performed for the UE may be retrieved from the SPR. The H-PCRF enables policy control for NSWO traffic for that UE based on operator policies and user profile information that may depend on e.g. NSWO-APN being used by the UE. +5. For the non-roaming case, the H-PCRF provisions the PCC Rules to the BPCF using CCA if policy control is enabled. + +For the roaming case, steps 5a~5f are executed instead of step 5. + +- 5a. The H-PCRF provisions the PCC Rules if available to the V-PCRF using CCA if policy control is enabled. The H-PCRF includes PCC Rules and ADC Rules if available in the Subsession-Decision AVP of the CCA, along with the S9 subsession identifier as received in step 2c within the Subsession-Id AVP. +- 5b. If policy control is enabled in step 5a, the V-PCRF stores the received PCC rules if available. The V-PCRF enforces visited operator policies regarding QoS authorization requested by the H-PCRF as indicated by the roaming agreements. +- 5c. The V-PCRF informs the H-PCRF when a request has been denied and may provide the acceptable QoS information for the service. +- 5d. The H-PCRF acknowledges the CCR and may additionally include new or modified PCC rules to the V-PCRF. When user profile configuration indicates that Application Detection and Control function is enabled, the H-PCRF may additionally include new or modified PCC rules for application detection and control. +- 5e. In case of solicited application reporting with a TDF, the V-PCRF initiates a TDF Session Establishment procedure, according to clause 4.6.1, with the selected TDF. +- 5f. The V-PCRF provisions PCC rules received from the H-PCRF to the BPCF by using CCA. + +### E.4.3 IP-CAN Session Termination + +#### E.4.3.1 IP-CAN Session Termination for EPC- routed traffic + +![Sequence diagram for IP-CAN Session Termination for EPC-routed traffic. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, H/V-AF, SPR, OCS. The diagram shows message exchanges for various roaming cases (Home Routed, Visited Access) and initiation types (UE-initiated, PCEF-initiated, PCRF-initiated).](aa81b9b80bd1e3d723922b3a033564a2_img.jpg) + +The diagram illustrates the interaction between network elements for IP-CAN session termination. The lifelines are BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, H/V-AF, SPR, and OCS. + +**Step 1:** Perform the step 1 through step 3: as defined in Figure 4.2.1.1: UE-initiated IP-CAN session termination-AF located in HPLMN, step 1 through step 5: as defined in Figure 4.2.2.1: PCEF-initiated IP-CAN session termination-AF located in HPLMN or step 1 through step 8: as defined in Figure 4.2.3.1: PCRF-initiated IP-CAN session termination-AF located in HPLMN + +**Roaming case (Home Routed and case 1):** + +- 2. Diameter RAR (BPCF to V-PCRF) +- 2a. Diameter RAR (V-PCRF to H-PCRF) +- 2b. Diameter RAR (H-PCRF to BPCF) +- 3. Diameter RAA (V-PCRF to BPCF) +- 3a. Diameter RAA (BPCF to V-PCRF) +- 3b. Diameter RAA (V-PCRF to H-PCRF) + +**Roaming case (Visited Access, case 2a or case 2b):** + +- 2c. Diameter RAR (BPCF to V-PCRF) +- 3c. Diameter RAA (V-PCRF to BPCF) + +**Roaming case (Home Routed and case 1):** + +- 4. Diameter CCR (BPCF to V-PCRF) +- 4a. Diameter CCR (V-PCRF to BPCF) +- 4b. Diameter CCR (V-PCRF to H-PCRF) + +**Roaming case (Visited Access, case 2a or case 2b):** + +- 5. Diameter CCA (BPCF to V-PCRF) +- 5a. Diameter CCA (V-PCRF to BPCF) +- 5b. Diameter CCA (V-PCRF to H-PCRF) +- 5c. Diameter CCA (BPCF to V-PCRF) + +**Step 6:** Perform the step 3 through step 7 :as specified in Figure 4.2.1.1: UE-initiated IP-CAN session termination-AF located in HPLMN + +**Step 7:** Perform the step 8 through step 11 :As Specified in Figure 4.2.1.1 for AF located in HPLMN or step 2 through step 9 :as specified in Figure 4.2.1.2 for AF located in VPLMN + +**Step 8:** Perform the step 12 through step 15 :as specified in Figure 4.2.1.1: UE-initiated IP-CAN session termination-AF located in HPLMN + +Sequence diagram for IP-CAN Session Termination for EPC-routed traffic. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, H/V-AF, SPR, OCS. The diagram shows message exchanges for various roaming cases (Home Routed, Visited Access) and initiation types (UE-initiated, PCEF-initiated, PCRF-initiated). + +Figure E.4.3.1.1: IP-CAN Session Termination for EPC-routed traffic + +1. Perform the step 1 through step 3: as defined in Figure 4.2.1.1: UE-initiated IP-CAN session termination-AF located in HPLMN, step 1 through step 5: as defined in Figure 4.2.2.1: PCEF-initiated IP-CAN session termination-AF located in HPLMN or step 1 through step 8: as defined in Figure 4.2.3.1: PCRF-initiated IP-CAN session termination-AF located in HPLMN. +2. For GTP/PMIP-based S2b of the WLAN scenario (non-roaming case), triggered by a Gateway control session termination from BBERF(ePDG) or by an Indication of IP-CAN session termination from PCEF, the H-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a session. + +For trusted and untrusted S2c of the WLAN scenario (non-roaming case), triggered by the Indication of IP-CAN session termination, the H-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a session when the last PDN connection is released for this user; otherwise, the H-PCRF sends a RAR to BPCF to remove all the QoS rules related to the released PDN connection. + +For H(e)NB scenario (non-roaming case), triggered by a Gateway control session termination from BBERF(S-GW) or by an indication of IP-CAN session termination, the H-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a session when last PDN connection is released for this H(e)NB Local IP address; otherwise, the H-PCRF sends a RAR to BPCF to remove all the QoS rules related to the released PDN connection. + +For case 1 (roaming with home routed case), the steps 2a and step 2b are executed instead of step 2. + +- 2a. If the subsession being terminated is the last subsession over S9, the H-PCRF sends a RAR including the Session-Release-Cause AVP to the V-PCRF to indicate the termination of the S9 session. Otherwise, the H-PCRF sends a RAR to the V-PCRF including the Subsession-Decision-Info AVP with the Session-Release-Cause AVP to indicate the request for terminating the S9 subsession corresponding to the IP-CAN session. +- 2b. For GTP-based S2b of the WLAN scenario, the V-PCRF sends a RAR including the Session-Release-Cause AVP to the BPCF to indicate the request for terminating the S9a session. + +For trusted S2c of the WLAN scenario, the V-PCRF sends a RAR including the Session-Release-Cause AVP to the BPCF to indicate the request for terminating the S9a session when the last PDN connection is released for this user; otherwise, the V-PCRF sends a RAR to BPCF to remove all the QoS rules related to the released PDN connection. + +For the H(e)NB scenario, the V-PCRF sends a RAR including the Session-Release-Cause AVP to the BPCF to indicate the request for terminating the S9a session when the last PDN connection is released for this H(e)NB Local IP address; otherwise, the V-PCRF sends a RAR to BPCF to remove all the QoS rules related to the released PDN connection. + +For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), step 2c is executed instead of step 2. + +- 2c. For GTP/PMIP-based S2b of the WLAN scenario, triggered by a Gateway control session termination from BBERF(ePDG) or by an Indication of IP-CAN session termination, the V-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a session. + +For trusted and untrusted S2c of the WLAN scenario, triggered by the Indication of IP-CAN session termination or S9 session/subsession termination request from the H-PCRF, the V-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a session when the last PDN connection is released for this user; otherwise, the V-PCRF sends a RAR to BPCF to remove all the QoS rules related to the released PDN connection + +For case 1 and case 2b of H(e)NB scenario, triggered by a Gateway control session termination from the BBERF(S-GW) or by an Indication of IP-CAN session termination, the V-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a session when the last PDN connection is released for this H(e)NB Local IP address; otherwise, the H-PCRF sends a RAR to BPCF to remove all the QoS rules related to the released PDN connection. + +3. For the non-roaming case, the BPCF sends a RAA to acknowledge the RAR. + +For case 1 (roaming with home routed case), the steps 3a and 3b are executed instead of step 3. + +- 3a. The BPCF sends a RAA to the V-PCRF. + +3b. The V-PCRF sends a RAA to the H-PCRF. + +For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), step 2c is executed instead of step 2. + +3c. The BPCF sends a RAA to the V-PCRF. + +4. For the non-roaming case, the BPCF sends a CCR to the H-PCRF to indicate the S9a session termination if the H-PCRF requests that the BPCF terminates the S9a session in step 2. The BPCF requests the termination of the S9a session using the CC-Request-Type set to the value TERMINATION\_REQUEST. + +For case 1(roaming with home routed case), the steps 4a and 4b are executed instead of step 4 + +4a. The BPCF sends a CCR to the V-PCRF to indicate the S9a session termination if the V-PCRF requests that the BPCF terminates the S9a session in step 2b. The BPCF requests the termination of the S9a session using the CC-Request-Type set to the value TERMINATION\_REQUEST. + +4b. The V-PCRF sends a CCR to the H-PCRF to indicate the S9 session termination if the H-PCRF requests that the V-PCRF terminates the S9 session in step 2a. The V-PCRF requests the termination of the S9 session using the CC-Request-Type set to the value TERMINATION\_REQUEST. + +For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), step 4c is executed instead of step 4. + +4c. The BPCF sends a CCR to the V-PCRF to indicate the S9a session termination if the V-PCRF request that the BPCF terminates the S9a session in step 2c. The BPCF requests the termination of the S9a session using the CC-Request-Type set to the value TERMINATION\_REQUEST. + +5. For the non-roaming case, the H-PCRF sends a CCA to acknowledge the CCR. + +For case 1 (roaming with home routed case), the steps 5a and 5b are executed instead of step 5 + +5a. The H-PCRF sends a CCA to acknowledge the CCR. + +5b. The V-PCRF sends a CCA to acknowledge the CCR. + +For case 1 (visited access) and for case 2a and case 2b (visited access or home routed case), step 5c is executed instead of step 5. + +5c. The V-PCRF sends a CCA to acknowledge the CCR. + +6. Perform the step 3 through step 7: as defined in Figure 4.2.1.1: UE-initiated IP-CAN session termination-AF located in HPLMN, +7. Perform the step 8 through step 11 :As Specified in Figure 4.2.1.1 for AF located in HPLMN or step 2 through step 9 :as specified in Figure 4.2.1.2 for AF located in VPLMN +8. Perform the step 12 through step 15: as defined in Figure 4.2.1.1: UE-initiated IP-CAN session termination-AF located in HPLMN. + +#### E.4.3.2 IP-CAN Session Termination for NSWO traffic + +##### E.4.3.2.1 BPCF-initiated IP-CAN Session Termination for NSWO traffic + +![Sequence diagram for BPCF-initiated IP-CAN Session Termination for NSWO Traffic. Lifelines: BPCF, V-PCRF, H-PCRF, TDF, H-AF, SPR. The diagram shows a non-roaming case and two roaming cases. The non-roaming case involves BPCF sending a Diameter CCR to H-PCRF, H-PCRF identifying the AF session, and returning Diameter CCA messages. The roaming cases involve BPCF sending Diameter CCR to V-PCRF, which then forwards it to H-PCRF. Conditional steps include TDF session termination and removing information related to the terminated session. A legend indicates solid arrows for mandatory messages and dashed arrows for conditional messages.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +``` + +sequenceDiagram + participant BPCF + participant V-PCRF + participant H-PCRF + participant TDF + participant H-AF + participant SPR + + Note left of BPCF: 1. Trigger + BPCF->>H-PCRF: 2. Diameter CCR + Note right of V-PCRF: ROAMING CASE + BPCF->>V-PCRF: 2a. Diameter CCR + V-PCRF-->>TDF: 2b. TDF session termination + V-PCRF->>H-PCRF: 2c. Diameter CCR + Note right of H-PCRF: 3. Identify AF Session bound to the remove IP-CAN session + H-PCRF->>BPCF: 4. Diameter CCA + Note right of V-PCRF: ROAMING CASE + H-PCRF->>V-PCRF: 4a. Diameter CCA + Note right of BPCF: 4b. Removes the information related to the terminated IP-CAN session + V-PCRF->>BPCF: 4c. Diameter CCA + Note right of TDF: 5. TDF session termination + Note right of SPR: 6. Perform step 8 through 12: as specified in Figure 4.2.1.1: UE-Initiated IP-CAN Session Termination – AF located in the HPLMN + +``` + +Sequence diagram for BPCF-initiated IP-CAN Session Termination for NSWO Traffic. Lifelines: BPCF, V-PCRF, H-PCRF, TDF, H-AF, SPR. The diagram shows a non-roaming case and two roaming cases. The non-roaming case involves BPCF sending a Diameter CCR to H-PCRF, H-PCRF identifying the AF session, and returning Diameter CCA messages. The roaming cases involve BPCF sending Diameter CCR to V-PCRF, which then forwards it to H-PCRF. Conditional steps include TDF session termination and removing information related to the terminated session. A legend indicates solid arrows for mandatory messages and dashed arrows for conditional messages. + +Figure E.4.3.2.1.1: BPCF-initiated IP-CAN Session Termination for NSWO Traffic + +1. The Fixed Broadband Access network is aware of the UE is detached from the broadband access network +2. For the non-roaming case, the BPCF sends a CCR to the H-PCRF to indicate the S9a\* session termination. The BPCF requests the termination of the S9a\* session using the CC-Request-Type set to the value TERMINATION\_REQUEST. + +For the roaming case, the steps 2a and 2c are executed instead of step 2. + +- 2a. The BPCF sends a CCR to the V-PCRF to indicate the S9a\* session termination. The BPCF requests the termination of the S9a\* session using the CC-Request-Type set to the value TERMINATION\_REQUEST. +- 2b. If there is an active TDF session between TDF and V-PCRF, the TDF session termination is initiated as defined in clause 4.6.2. For this case, the PCRF described in clause 4.6.2 acts as a V-PCRF. + +- 2c. The V-PCRF sends the CCR to the H-PCRF. If this is the last subsession associated with the S9 session, the V-PCRF sends a CCR to the H-PCRF to request the termination of the S9 session using the CC-Request-Type AVP set to the value TERMINATION\_REQUEST. Otherwise, the V-PCRF sends a CCR to the H-PCRF with a CC-Request-Type AVP set to the value UPDATE\_REQUEST and a Subsession-Enforcement-Info within which the Subsession-Operation AVP set to value TERMINATION to request the termination of the corresponding S9 subsession. +3. The H-PCRF identifies the AF sessions that are bound to IP flows of the removed IP-CAN Session. +4. For the non-roaming case, the H-PCRF acknowledges the S9a\* session termination by sending a CCA to the BPCF. + +For the roaming case, steps 4a~4c are executed instead of step 4: + +- 4a. The H-PCRF acknowledges the S9 session or subsession termination by sending a CCA to the V-PCRF. + - 4b. The V-PCRF removes the information related to the terminated IP-CAN Session. + - 4c. The V-PCRF acknowledges the S9a\* session termination by sending a CCA to the BPCF. +5. If there is an active TDF session between TDF and H-PCRF, the TDF session termination is initiated as defined in clause 4.6.2. + 6. Perform step 8 through step 12: as specified in Figure 4.2.1.1: UE-Initiated IP-CAN Session Termination – AF located in the HPLMN + +##### E.4.3.2.2 PCRF-initiated IP-CAN Session Termination for NSWO traffic + +![Sequence diagram for PCRF-initiated IP-CAN Session Termination for NSWO traffic. Lifelines: BPCF, V-PCRF, H-PCRF, TDF, H-AF, SPR. The diagram shows a non-roaming case and two roaming cases. Step 1: H-PCRF detects termination. Step 2: H-PCRF sends Diameter RAR to BPCF (non-roaming) or V-PCRF (roaming). Step 2a: H-PCRF sends Diameter RAR to V-PCRF (roaming). Step 2b: V-PCRF sends Diameter RAR to BPCF (roaming). Step 3: BPCF removes PCC rules. Step 4: BPCF sends Diameter RAA to H-PCRF (non-roaming) or V-PCRF (roaming). Step 4a: BPCF sends Diameter RAA to V-PCRF (roaming). Step 4b: V-PCRF sends Diameter RAA to H-PCRF (roaming). Step 5: BPCF performs steps 2 through 6 as specified in Figure E.4.3.2.1.1.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +``` + +sequenceDiagram + participant BPCF + participant V-PCRF + participant H-PCRF + participant TDF + participant H-AF + participant SPR + + Note right of H-PCRF: 1. Detection that IP-CAN session termination is required + H-PCRF->>BPCF: 2. Diameter RAR + Note left of BPCF: ROAMING CASE + H-PCRF->>V-PCRF: 2a. Diameter RAR + V-PCRF->>BPCF: 2b. Diameter RAR + Note left of BPCF: 3. Remove all the PCC rules + BPCF->>H-PCRF: 4. Diameter RAA + Note left of BPCF: ROAMING CASE + BPCF->>V-PCRF: 4a. Diameter RAA + V-PCRF->>H-PCRF: 4b. Diameter RAA + Note right of BPCF: 5. Perform step 2 through 6: as specified in Figure E.4.3.2.1.1: BPCF-initiated IP-CAN session Termination for NSWO traffic + +``` + +**Legend** + → **Mandatory** + - - - - → **Conditional** + +Sequence diagram for PCRF-initiated IP-CAN Session Termination for NSWO traffic. Lifelines: BPCF, V-PCRF, H-PCRF, TDF, H-AF, SPR. The diagram shows a non-roaming case and two roaming cases. Step 1: H-PCRF detects termination. Step 2: H-PCRF sends Diameter RAR to BPCF (non-roaming) or V-PCRF (roaming). Step 2a: H-PCRF sends Diameter RAR to V-PCRF (roaming). Step 2b: V-PCRF sends Diameter RAR to BPCF (roaming). Step 3: BPCF removes PCC rules. Step 4: BPCF sends Diameter RAA to H-PCRF (non-roaming) or V-PCRF (roaming). Step 4a: BPCF sends Diameter RAA to V-PCRF (roaming). Step 4b: V-PCRF sends Diameter RAA to H-PCRF (roaming). Step 5: BPCF performs steps 2 through 6 as specified in Figure E.4.3.2.1.1. + +**Figure E.4.3.2.2.1: PCRF-initiated IP-CAN Session Termination for NSWO Traffic** + +1. The H-PCRF detects that the termination of an IP-CAN Session is required. +2. For the non-roaming case, the H-PCRF sends a RAR including the Session-Release-Cause AVP to request that the BPCF terminates the S9a\* session. + +For the roaming case, steps 2a~2b are executed instead of step 2: + +- 2a. If the subsession being terminated is the last subsession over S9, the H-PCRF sends a RAR including the Session-Release-Cause AVP to the V-PCRF to indicate the termination of the S9 session. Otherwise, the H-PCRF sends a RAR to the V-PCRF including the Subsession-Decision-Info AVP with the Session-Release-Cause AVP to indicate the request for terminating the S9 subsession corresponding to the IP-CAN session. + +- 2b. The V-PCRF sends a RAR including the Session-Release-Cause AVP to the BPCF. + +3. The Fixed Broadband access network removes all the PCC rules which are applied to the IP-CAN session. + +4. For the non-roaming case, the BPCF sends a RAA to acknowledge the RAR. + +For the roaming case, steps 4a~4b are executed instead of step 4: + +- 4a. The BPCF sends a RAA to the V-PCRF. + +- 4b. The V-PCRF sends a RAA to the H-PCRF and acknowledges the request for terminating the S9 session or the S9 subsession corresponding to the IP-CAN session. +5. Step 2 through 6: as specified in Figure E.4.3.2.1.1:BPCF-initiated IP-CAN session termination for NSWO traffic. + +### E.4.4 IP-CAN Session Modification + +#### E.4.4.1 IP-CAN Session Modification for EPC-routed traffic + +##### E.4.4.1.1 PCRF-initiated IP-CAN Session Modification + +This procedure is applicable both for WLAN and H(e)NB scenario. + +![Sequence diagram for PCRF-initiated IP-CAN Session Modification for EPC routed traffic. The diagram shows interactions between BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, and OCS. It includes steps 1-3, 2a-2c, 3, 4a-4b, and 5-12. A legend indicates solid arrows are Mandatory and dashed arrows are Conditional. Roaming cases are highlighted for steps 2 and 4.](c78c2eefd86269d1740ab85a916f24f2_img.jpg) + +The sequence diagram illustrates the PCRF-initiated IP-CAN Session Modification for EPC routed traffic. The participants are BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, and OCS. + +The sequence of messages is as follows: + +- 1. Steps 1 to 3 as specified in figure 4.3.1.1.1**: Initial setup and trigger. +- 2. Diameter RAR**: V-PCRF sends a Diameter RAR to H-PCRF. + - 2a. Diameter RAR**: Conditional message from H-PCRF to V-PCRF. + - 2b. Perform authorization**: Internal process within H-PCRF. + - 2c. Diameter RAR**: Conditional message from V-PCRF to BPCF. +- 3. Translates QoS rule into access specific QoS**: Internal process within BPCF. +- 4. Diameter RAA**: H-PCRF sends a Diameter RAA to V-PCRF. + - 4a. Diameter RAA**: Conditional message from V-PCRF to BPCF. + - 4b. Diameter RAA**: Conditional message from BPCF to H-PCRF. +- 5. Steps 5 to 12 as specified in figure 4.3.1.1.1**: Finalization and response. + +**Legend:** + +- Mandatory**: Solid arrow +- Conditional**: Dashed arrow + +**Roaming Case:** The diagram highlights two roaming cases with light blue background shading: + + +- One for step 2 (Diameter RAR and its sub-messages). +- Another for step 4 (Diameter RAA and its sub-messages). + +Sequence diagram for PCRF-initiated IP-CAN Session Modification for EPC routed traffic. The diagram shows interactions between BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, and OCS. It includes steps 1-3, 2a-2c, 3, 4a-4b, and 5-12. A legend indicates solid arrows are Mandatory and dashed arrows are Conditional. Roaming cases are highlighted for steps 2 and 4. + +Figure E.4.4.1.1.1: PCRF-Initiated IP-CAN Session Modification for EPC routed traffic + +- 1 Step 1 to 3 as specified in figure 4.3.1.1.1 are executed. The H-PCRF receives an internal or external trigger to update PCC/QoS Rules. External trigger in Step 1 in figure 4.3.1.1.1 only applies to AF session interactions (as described in clause 4.3.1.2) and TDF session interactions (as described in clause 4.3.1.2). For V-PCRF initiated IP-CAN session modification, the V-PCRF always asks the H-PCRF for policy decision. + +NOTE: If the AF/TDF is located in the V-PLMN, upon a request from the AF/TDF, the V-PCRF will proxy the request to the H-PCRF, this may also trigger the PCRF-Initiated IP-CAN Session Modification for EPC routed traffic. + +- 2 The H-PCRF sends a Diameter RAR to update the QoS information to the BPCF. + +If the UE is roaming, then steps 2a ~ 2c are executed instead of step 2: + +- 2a. The H-PCRF sends a Diameter RAR to the V-PCRF to install, modify or remove PCC rules for Visited Access scenario, or QoS Rules for Home Routed scenario. + - 2b. The V-PCRF performs local authorization of the received PCC rules or QoS rules when necessary. + - 2c. The V-PCRF sends a Diameter RAR to the BPCF to update the QoS information. +3. The BPCF shall perform QoS validation and translates the QoS rule as received (i.e. SDF template, QCI, MBR, GBR and ARP) into access specific QoS parameters applicable in the BBF domain (the details of the mapping from 3GPP QoS parameters on S9a to QoS parameters applicable in the BBF domain is out of 3GPP scope). + 4. The BPCF sends RAA to the H-PCRF to acknowledge the RAR and informs the H-PCRF about the outcome of the QoS rule operation. If the BPCF cannot provide the requested QoS by the H-PCRF, the BPCF may respond with the acceptable QoS. + +If the UE is roaming, then steps 4a ~ 4b are executed instead of step 4: + +- 4a. The BPCF sends RAA to the V-PCRF to acknowledge the RAR and informs the V-PCRF about the outcome of the QoS rule operation. If the BPCF cannot provide the QoS requested by the V-PCRF, the BPCF may respond with the acceptable QoS. +- 4b. The V-PCRF forwards the RAA to the H-PCRF to acknowledge the RAR and informs the H-PCRF about the outcome of the QoS rule operation. + +NOTE: If the H-PCRF is informed that the BPCF cannot provide the requested QoS, the H-PCRF can decide to install, modify or remove QoS rules. In that case, the same flow as described in this clause will be executed. + +5. Step 5 to 12 as specified in figure 4.3.1.1.1 are executed. + +##### E.4.4.1.2 BPCF-initiated IP-CAN Session Modification + +This procedure is applicable both for WLAN and H(e)NB scenario. + +![Sequence diagram for BPCF-Initiated IP-CAN Session Modification. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, OCS. The diagram shows a trigger from TDF to BPCF, followed by Diameter CCR messages from BPCF to H-PCRF (step 2) or V-PCRF (step 2a). In a roaming case, V-PCRF stores info (2b) and forwards CCR to H-PCRF (2c). H-PCRF sends CCA to BPCF (step 3) or V-PCRF (step 3a). In a roaming case, V-PCRF then sends CCA to BPCF (step 3b). Finally, a PCRF-initiated IP-CAN session modification is performed (step 4). A legend indicates solid arrows are mandatory and dashed arrows are conditional.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant BBERF + participant PCEF + participant TDF + participant BPCF + participant V-PCRF + participant H-PCRF + participant AF + participant OCS + + Note right of TDF: 1. Trigger + TDF->>BPCF: 1. Trigger + BPCF->>H-PCRF: 2. Diameter CCR + Note right of BPCF: 2a. Diameter CCR + BPCF->>V-PCRF: 2a. Diameter CCR + Note right of V-PCRF: 2b. Store Information + V-PCRF->>H-PCRF: 2c. Diameter CCR + Note right of H-PCRF: 3. Diameter CCA + H-PCRF->>BPCF: 3. Diameter CCA + Note right of H-PCRF: 3a. Diameter CCA + H-PCRF->>V-PCRF: 3a. Diameter CCA + Note right of V-PCRF: 3b. Diameter CCA + V-PCRF->>BPCF: 3b. Diameter CCA + Note right of BPCF: 4. PCRF-initiated IP-CAN Session Modification as described in E.4.4.1.1 + +``` + +Sequence diagram for BPCF-Initiated IP-CAN Session Modification. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, OCS. The diagram shows a trigger from TDF to BPCF, followed by Diameter CCR messages from BPCF to H-PCRF (step 2) or V-PCRF (step 2a). In a roaming case, V-PCRF stores info (2b) and forwards CCR to H-PCRF (2c). H-PCRF sends CCA to BPCF (step 3) or V-PCRF (step 3a). In a roaming case, V-PCRF then sends CCA to BPCF (step 3b). Finally, a PCRF-initiated IP-CAN session modification is performed (step 4). A legend indicates solid arrows are mandatory and dashed arrows are conditional. + +**Figure E.4.4.1.2.1: BPCF-Initiated IP-CAN Session Modification** + +1. The trigger for this procedure is that the Fixed Broadband Access has pre-empted some resources and wants to report a QoS rule failure to the PCRF, or when the Fixed Broadband Access network cannot sustain the bandwidth allocated to a particular traffic class/DSCP aggregate. +2. The BPCF sends a Diameter CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST to report QoS Rule failure. + +When the UE is in roaming case, steps 2a ~ 2c are executed instead of step 2: + +- 2a. The BPCF sends a Diameter CCR to the V-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST to report QoS Rule failure. +- 2b. The V-PCRF stores the information received. +- 2c. For Visited Access scenario, the V-PCRF sends a Diameter CCR to the H-PCRF to report PCC Rule failure. For Home Routed scenario, the V-PCRF sends a Diameter CCR to the H-PCRF to report QoS Rule failure. + +- 3 The H-PCRF sends a Diameter CCA to the BPCF to acknowledge the CCR command. + +When the UE is in roaming case, steps 3a ~ 3b are executed instead of step 3: + +- 3a. The H-PCRF sends a Diameter CCA to the V-PCRF to acknowledge the CCR command. + +3b. The V-PCRF forwards the Diameter CCA to the BPCF to acknowledge the CCR. + +4. The PCRF-initiated IP-CAN Session Modification as described in E.4.4.1.1 may take place. + +##### E.4.4.1.3 PCEF-initiated IP-CAN Session Modification + +This procedure is applicable both for WLAN and H(e)NB scenario. + +![Sequence diagram for PCEF-initiated IP-CAN Session Modification. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, OCS. The diagram shows a sequence of messages between these entities, with specific steps for roaming cases. A legend indicates solid arrows for mandatory messages and dashed arrows for conditional messages.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +The sequence diagram illustrates the PCEF-initiated IP-CAN Session Modification procedure. The lifelines are BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, and OCS. The process is divided into two main phases: Steps 1 to 3 and Steps 4 to 18. + +- Steps 1 to 3:** This phase is common to both non-roaming and roaming cases. It involves the PCEF sending a Diameter RAR to the BPCF (Step 2). In a roaming case, the BPCF sends a Diameter RAR to the V-PCRF (Step 2a), which then performs QoS rule validation (Step 2b) and sends a Diameter RAR to the BPCF (Step 2c). The PCEF then translates the QoS rule into access specific QoS (Step 3). +- Steps 4 to 18:** This phase is also common. The BPCF sends a Diameter RAA to the PCEF (Step 4). In a roaming case, the PCEF sends a Diameter RAA to the BPCF (Step 4a), which then sends a Diameter RAA to the V-PCRF (Step 4b). + +**Legend:** + +- Solid arrow: **Mandatory** +- Dashed arrow: **Conditional** + +Sequence diagram for PCEF-initiated IP-CAN Session Modification. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, OCS. The diagram shows a sequence of messages between these entities, with specific steps for roaming cases. A legend indicates solid arrows for mandatory messages and dashed arrows for conditional messages. + +**Figure E.4.4.1.3.1: PCEF-Initiated IP-CAN Session Modification** + +1. Step 1 to 3 (3a-3c for the Visited Access case) is the same as specified in figure 4.3.2.1.1. In step 3 (3c for the Visited Access case), when the UE Local IP address, H(e)NB Local IP address or the UDP port number is changed, the PCEF may provide the updated UE local IP address, the updated H(e)NB IP address, and/or UDP port number if available, to the PCRF; or the PCEF cannot enforce the PCC rule(s) and need report the PCC rule failure to the PCRF. +2. The H-PCRF sends a Diameter RAR to request that the BPCF installs, modifies or removes QoS Rules (i.e. SDF template, QCI, ARP, MBR and GBR). + +When the UE is in roaming case, steps 2a ~ 2c are executed instead of step 2: + +- 2a. For Visited Access scenario, the H-PCRF may provision the PCC rule(s) to the V-PCRF. For Home Routed scenario the H-PCRF may provision the QoS rule(s) to the V-PCRF. The H-PCRF may provision for WLAN case the UE local IP address, and UDP port number (if available) and for H(e)NB case the H(e)NB local IP address, and UDP port number (if available) to the V-PCRF. + - 2b. The V-PCRF performs local authorization of the QoS Rules or PCC rules when necessary. + - 2c. The V-PCRF may provision QoS rules to the BPCF by using RAR command. The V-PCRF may provision for WLAN case the UE local IP address, and UDP port number (if available) and for H(e)NB case the H(e)NB local IP address, and UDP port number (if available) to the BPCF. + - 3 The BPCF shall perform QoS validation and translates the QoS information as received (i.e. QCI, MBR, GBR and ARP) into access specific QoS parameters applicable in the Fixed Broadband Access. +- NOTE The detail of the mapping from 3GPP QoS parameters on S9a to QoS parameters applicable in the Fixed Broadband Access is out of 3GPP scope. +4. The BPCF sends RAA to the H-PCRF to acknowledge the RAR command. If the QoS validation for admission control fails, the BPCF may include the acceptable QoS in the Fixed Broadband Access using 3GPP QoS parameters on S9a interface. +- When the UE is in roaming case, steps 4a ~ 4b are executed instead of step 2: +- 4a. The BPCF sends RAA to the V-PCRF to acknowledge the RAR command. + - 4b. The V-PCRF forwards the RAA to the H-PCRF to acknowledge the RAR command. +5. Step 4 to 18 is the same as specified in figure 4.3.2.1.1. + +##### E.4.4.1.4 BBERF-initiated IP-CAN Session Modification + +This procedure is applicable for both WLAN and H(e)NB scenario. + +![Sequence diagram for BBERF-Initiated IP-CAN Session Modification. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, OCS. The diagram shows a sequence of messages between these entities, with steps 1-3 and 4-18 referenced from figure 4.3.2.1.1. It includes a 'Roaming Case' section with sub-steps 2a, 2b, and 2c, and a legend indicating mandatory and conditional messages.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The diagram illustrates the BBERF-Initiated IP-CAN Session Modification process. It features nine lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, and OCS. The sequence is divided into two main parts: '1. Steps 1 to 3 as specified in figure 4.3.2.1.1' and '5. Steps 4 to 18 as specified in figure 4.3.2.1.1'. A 'Roaming Case' is highlighted in the middle section. Within this case, step 2 is expanded into 2a (Diameter RAR from H-PCRF to V-PCRF), 2b (QoS Rule Validation in V-PCRF), and 2c (Diameter RAR from V-PCRF to BPCF). Step 3 involves translating a QoS rule into access-specific QoS. Step 4 shows Diameter RAA messages from BPCF to H-PCRF, with 4a and 4b being conditional responses. A legend at the bottom right indicates that solid arrows represent 'Mandatory' messages and dashed arrows represent 'Conditional' messages. + +Sequence diagram for BBERF-Initiated IP-CAN Session Modification. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, OCS. The diagram shows a sequence of messages between these entities, with steps 1-3 and 4-18 referenced from figure 4.3.2.1.1. It includes a 'Roaming Case' section with sub-steps 2a, 2b, and 2c, and a legend indicating mandatory and conditional messages. + +**Figure E.4.4.1.4.1: BBERF-Initiated IP-CAN Session Modification** + +- 1 Step 1 to 3(3a-3c for the Visited Access case) is the same as specified in figure 4.3.2.1.1. + +In step 1, in case 2b and case 2a for WLAN scenario, when the UE Local IP address, and/or the UDP port number is changed, the BBERF (ePDG) may provide these information to the PCRF. For H(e)NB scenario, when the H(e)NB local IP address and the UDP port number is changed, the BBERF (S-GW) may provide these information to the PCRF. + +- 2 The H-PCRF sends a Diameter RAR to request that the BPCF installs, modifies or removes QoS Rules (e.g. SDF template, QCI, ARP, MBR and GBR). + +When the UE is in roaming case, steps 2a ~ 2c are executed instead of step 2: + +- 2a. For Visited Access scenario, the H-PCRF may provision the PCC rule(s) to the V-PCRF. For Home Routed scenario the H-PCRF may provision the QoS rule(s) to the V-PCRF. The H-PCRF provisions for WLAN case the UE local IP address and/or UDP port number, and for H(e)NB case the H(e)NB local IP address and UDP port number to the V-PCRF. +- 2b. The V-PCRF performs local authorization of the QoS Rules or PCC rules when necessary. +- 2c. The V-PCRF may provision QoS rules to the BPCF by using RAR command. The V-PCRF provisions for WLAN case the UE local IP address and/or UDP port number, and for H(e)NB case the H(e)NB local IP address and/or UDP port number to the BPCF. + +- 3 The BPCF shall perform QoS validation and translates the QoS information as received (i.e. QCI, MBR, GBR and ARP) into access specific QoS parameters applicable in the Fixed Broadband Access. + +NOTE: The detail of the mapping from 3GPP QoS parameters on S9a to QoS parameters applicable in the Fixed Broadband Access is out of 3GPP scope. + +4. The BPCF sends RAA to the H-PCRF to acknowledge the RAR command. If the QoS validation for admission control fails, the BPCF may include the acceptable QoS in the Fixed Broadband Access using 3GPP QoS parameters on S9a interface. + +When the UE is in roaming case, steps 4a ~ 4b are executed instead of step 4: + +- 4a. The BPCF sends RAA to the V-PCRF to acknowledge the RAR. + +- 4b. The V-PCRF forwards the RAA to the H-PCRF to acknowledge the RAR. + +5. Step 4 to 18 is the same as specified in figure 4.3.2.1.1. + +#### E.4.4.2 IP-CAN Session Modification for NSWO traffic + +##### E.4.4.2.1 PCRF-initiated IP-CAN Session Modification + +This procedure is applicable for WLAN scenario. + +![Sequence diagram for PCRF-Initiated IP-CAN Session Modification for NSWO traffic. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, OCS. The diagram shows steps 1 to 5, with steps 2a-2c and 4a-4b representing roaming cases. A legend indicates solid arrows are mandatory and dashed arrows are conditional.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant BBERF + participant PCEF + participant TDF + participant BPCF + participant V-PCRF + participant H-PCRF + participant AF + participant SPR + participant OCS + + Note right of H-PCRF: 1. Steps 1 to 3 as specified in figure 4.3.1.1.1 + H-PCRF->>BPCF: 2. Diameter RAR + Note left of BPCF: 2b. Perform authorization + BPCF->>V-PCRF: 2a. Diameter RAR + V-PCRF->>BPCF: 2c. Diameter RAR + Note right of BPCF: 3. Translates QoS rule into access specific QoS + BPCF->>H-PCRF: 4. Diameter RAA + H-PCRF->>V-PCRF: 4a. Diameter RAA + V-PCRF->>H-PCRF: 4b. Diameter RAA + Note right of V-PCRF: 5. PCRF notifies the AF + +``` + +**Legend:** + +- Solid arrow: **Mandatory** +- Dashed arrow: **Conditional** + +Sequence diagram for PCRF-Initiated IP-CAN Session Modification for NSWO traffic. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, OCS. The diagram shows steps 1 to 5, with steps 2a-2c and 4a-4b representing roaming cases. A legend indicates solid arrows are mandatory and dashed arrows are conditional. + +**Figure E.4.4.2.1.1.1: PCRF-Initiated IP-CAN Session Modification for NSWO traffic** + +- 1 Step 1 to 3 as specified in figure 4.3.1.1.1 are executed. The H-PCRF receives an internal or external trigger to update PCC Rules for NSWO traffic (e.g. upon a request from the AF, a request from the TDF in the non roaming case or due to operator policies). External trigger in Step 1 in figure 4.3.1.1.1 only applies to AF session interactions (as described in clause 4.3.1.2), TDF session interactions (as described in clause 4.3.1.1) and SPR subscription data modification (as described in clause 4.3.1.1). + +NOTE: In the roaming case, the TDF is located in the V-PLMN, upon a request from the TDF, the V-PCRF will proxy the request to the H-PCRF, this may also trigger the PCRF-Initiated IP-CAN Session Modification for NSWO traffic. + +- 2 The H-PCRF sends a Diameter RAR to update the QoS information to the BPCF. + +If the UE is roaming, then steps 2a ~ 2c are executed instead of step 2: + +- 2a. The H-PCRF sends a Diameter RAR to the V-PCRF to install, modify or remove PCC Rules. + +- 2b. The V-PCRF performs local authorization of the received PCC rules when necessary. + +- 2c. The V-PCRF sends a Diameter RAR to the BPCF to update the QoS information. + +- 3 The BPCF shall perform QoS validation and translates the PCC rule as received (i.e. SDF template, QCI, MBR, GBR and ARP) into access specific QoS parameters applicable in the Fixed Broadband Access. + +NOTE: The detail of the mapping from 3GPP QoS parameters on S9a to QoS parameters applicable in the Fixed Broadband Access is out of 3GPP scope. + +4. The BPCF sends RAA to the H-PCRF to acknowledge the RAR and informs the H-PCRF about the outcome of the PCC rule operation. If the BPCF cannot provide the requested QoS from the PCRF, the BPCF may respond with the acceptable QoS. + +If the UE is roaming, then steps 4a ~ 4b are executed instead of step 4: + +- 4a. The BPCF sends RAA to the V-PCRF to acknowledge the RAR and informs the V-PCRF about the outcome of the PCC rule operation. If the BPCF cannot provide the QoS requested by the H-PCRF, the BPCF may respond with the acceptable QoS. + +- 4b. The V-PCRF forwards the RAA to the H-PCRF to acknowledge the RAR and informs the H-PCRF about the outcome of the PCC rule operation. + +NOTE: If the H-PCRF is informed that the BPCF cannot provide the requested QoS, the H-PCRF may decide to install, modify or remove PCC rules. In that case, the same flow as described in this clause will be executed. + +5. If the AF requested it, the PCRF notifies the AF as described in steps 6-11 in clause 4.3.2.1.1. + +##### E.4.4.2.2 BPCF-initiated IP-CAN Session Modification + +This procedure is applicable for WLAN scenario. + +![Sequence diagram for BPCF-Initiated IP-CAN Session Modification for NSWO traffic. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, OCS. The diagram shows a trigger from TDF to BPCF, followed by Diameter CCR messages from BPCF to H-PCRF (step 2) or V-PCRF (step 2a). In a roaming case, V-PCRF stores info (2b) and forwards CCR to H-PCRF (2c). H-PCRF sends Diameter CCA to BPCF (step 3) or V-PCRF (step 3a). In a roaming case, V-PCRF forwards CCA to BPCF (step 3b). Finally, a PCRF-initiated IP-CAN session modification is performed (step 4). A legend indicates solid arrows are mandatory and dashed arrows are conditional.](68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg) + +``` + +sequenceDiagram + participant BBERF + participant PCEF + participant TDF + participant BPCF + participant V-PCRF + participant H-PCRF + participant AF + participant SPR + participant OCS + + Note right of TDF: 1. Trigger + TDF->>BPCF: 1. Trigger + BPCF->>H-PCRF: 2. Diameter CCR + Note right of BPCF: 2a. Diameter CCR + BPCF->>V-PCRF: 2a. Diameter CCR + Note right of V-PCRF: 2b. Store information + V-PCRF->>H-PCRF: 2c. Diameter CCR + Note right of H-PCRF: 3. Diameter CCA + H-PCRF->>BPCF: 3. Diameter CCA + Note right of H-PCRF: 3a. Diameter CCA + H-PCRF->>V-PCRF: 3a. Diameter CCA + Note right of V-PCRF: 3b. Diameter CCA + V-PCRF->>BPCF: 3b. Diameter CCA + Note right of BPCF: 4. PCRF-initiated IP-CAN Session Modification as described in E.4.4.2.1 + +``` + +Sequence diagram for BPCF-Initiated IP-CAN Session Modification for NSWO traffic. Lifelines: BBERF, PCEF, TDF, BPCF, V-PCRF, H-PCRF, AF, SPR, OCS. The diagram shows a trigger from TDF to BPCF, followed by Diameter CCR messages from BPCF to H-PCRF (step 2) or V-PCRF (step 2a). In a roaming case, V-PCRF stores info (2b) and forwards CCR to H-PCRF (2c). H-PCRF sends Diameter CCA to BPCF (step 3) or V-PCRF (step 3a). In a roaming case, V-PCRF forwards CCA to BPCF (step 3b). Finally, a PCRF-initiated IP-CAN session modification is performed (step 4). A legend indicates solid arrows are mandatory and dashed arrows are conditional. + +**Figure E.4.4.2.2.1: BPCF-Initiated IP-CAN Session Modification for NSWO traffic** + +1. The trigger for this procedure is that the Fixed Broadband Access network has pre-empted some resources and wants to report a PCC rule failure to the PCRF, or when the Fixed Broadband Access network cannot sustain the bandwidth allocated to a particular traffic class/DSCP aggregate. +2. The BPCF sends a Diameter CCR to the H-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST to report PCC Rule failure. + +When the UE is roaming, steps 2a ~ 2c are executed instead of step 2: + +2a. The BPCF sends a Diameter CCR to the V-PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST to report PCC Rule failure. + +2b. The V-PCRF stores the information received. + +2c. The V-PCRF sends a Diameter CCR to the H-PCRF within the information received in step 2a to report PCC Rule failure. The V-PCRF shall link the S9a\* session to S9 session. + +- 3 The H-PCRF sends a Diameter CCA to the BPCF to acknowledge the CCR command. + +When the UE is roaming, steps 3a ~ 3b are executed instead of step 3: + +- 3a. The H-PCRF sends a Diameter CCA to the BPCF to acknowledge the CCR command.. +- 3b. The V-PCRF sends a Diameter CCA to the BPCF to acknowledge the CCR command. +4. The PCRF-initiated IP-CAN Session Modification as described in E.4.4.2.1 may take place. + +## E.5 3GPP HNB Procedures – CS Support + +### E.5.1 S9a CS Session Establishment + +In the following procedure, the PCRF is the V-PCRF for the roaming UE. + +![Sequence diagram for S9a CS session Establishment showing interactions between BPCF, HNB GW, and PCRF.](715219db84ec2a5622d09f9d822b4550_img.jpg) + +``` +sequenceDiagram + participant BPCF + participant HNB GW + participant PCRF + Note right of HNB GW: 1. Trigger + HNB GW->>PCRF: 2.Diameter CCR + Note right of PCRF: 3. Store information + PCRF->>HNB GW: 4.Diameter CCA + PCRF->>BPCF: 5.Diameter TER + BPCF->>PCRF: 6.Diameter TEA + BPCF->>PCRF: 7.Diameter CCR + PCRF->>BPCF: 8.Diameter CCA +``` + +The diagram illustrates the S9a CS session establishment procedure. It features three main entities: BPCF, HNB GW, and PCRF. The sequence of events is as follows: 1. A 'Trigger' is received by the HNB GW. 2. The HNB GW sends a 'Diameter CCR' message to the PCRF. 3. The PCRF performs a 'Store information' action. 4. The PCRF sends a 'Diameter CCA' message back to the HNB GW. 5. The PCRF sends a 'Diameter TER' message to the BPCF. 6. The BPCF sends a 'Diameter TEA' message to the PCRF. 7. The BPCF sends a 'Diameter CCR' message to the PCRF. 8. The PCRF sends a 'Diameter CCA' message back to the BPCF. + +Sequence diagram for S9a CS session Establishment showing interactions between BPCF, HNB GW, and PCRF. + +**Figure E.5.1.1: S9a CS session Establishment** + +1. The HNB GW receives a trigger to establish an S15 session with the PCRF when the HNB performs the registration to the HNB GW. +2. The HNB GW initiates an S15 session with the PCRF by sending a CCR to the PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The HNB GW provides the HNB Local IP address and the UDP source port number of IPSec tunnel if NA(P)T is detected. +3. The PCRF stores the information received in the CCR. +4. The PCRF acknowledges the session establishment by sending a CCA message. +5. The PCRF shall send a TER command to BPCF to trigger an S9a session establishment procedure. The PCRF provides HNB Local IP address and UDP source port number if available. The PCRF shall include the Auth-Session-State AVP set to NO\_STATE\_MAINTAINED. + +NOTE: When the HNB performs the registration to the HNB GW, there is no PS service handled by the HNB. So there is no already established S9a session for the HNB. + +6. The BPCF acknowledges the TER command by sending a TEA command. +7. The BPCF initiates an S9a session establishment with the PCRF by sending a CCR to the PCRF with the CC-Request-Type AVP set to the value INITIAL\_REQUEST. The BPCF provides HNB local IP address and UDP source port number if available. +8. The PCRF acknowledges the S9a Session establishment by sending a CCA to the BPCF. + +### E.5.2 PCRF initiated S9a CS Session Modification + +In the following procedure, the PCRF is the V-PCRF for the roaming UE. + +![Sequence diagram for S9a CS session Modification showing interactions between BPCF, HNB GW, and PCRF.](7a1dee155822446f7828dcb055c465c3_img.jpg) + +``` +sequenceDiagram + participant BPCF + participant HNB_GW as HNB GW + participant PCRF + Note right of HNB_GW: 1. Trigger + HNB_GW->>PCRF: 2.Diameter CCR + PCRF->>BPCF: 3.Diameter RAR + BPCF->>PCRF: 4.Diameter RAA + PCRF->>HNB_GW: 5.Diameter CCA + Note right of HNB_GW: 6. Complete the procedure for CS service +``` + +The diagram illustrates the sequence of messages for S9a CS session modification. It involves three main entities: BPCF, HNB GW, and PCRF. The process starts with a 'Trigger' at the HNB GW. The HNB GW sends a 'Diameter CCR' to the PCRF. The PCRF responds with a 'Diameter RAR' to the BPCF. The BPCF then sends a 'Diameter RAA' back to the PCRF. The PCRF sends a 'Diameter CCA' to the HNB GW. Finally, the HNB GW completes the procedure for the CS service. + +Sequence diagram for S9a CS session Modification showing interactions between BPCF, HNB GW, and PCRF. + +Figure E.5.2.1: S9a CS session Modification + +This procedure is performed when the first UE or a subsequent UE connected to a HNB requesting a CS service. + +1. The HNB GW receives RAB assignment message to request the resource for the CS service. +2. The HNB GW initiates an S15 session modification with the PCRF by sending a CCR to the PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The HNB GW provides QoS information derived from the RAB assignment message by the HNB GW. +3. The PCRF initiates an S9a session modification procedure to the BPCF by sending a RAR to the BPCF. The PCRF provides QoS rule generated by the PCRF based on the QoS information received in step 2. +4. Fixed Broadband access network performs the admission control based on the QoS rule received in step 3 and responds with the outcome of the admission control by sending a RAA to the PCRF. +5. The PCRF responds with outcome of the admission control to the HNB GW by sending a CCA. +6. The HNB GW complete the procedure for the CS service. + +### E.5.2a BPCF initiated S9a CS Session Modification + +In the following procedure, the PCRF is the V-PCRF for the roaming UE. + +![Sequence diagram for S9a CS session Modification. Lifelines: BPCF, HNB GW, and PCRF. The sequence starts with a '1. Trigger' on the BPCF lifeline. Step 2: BPCF sends a 'Diameter CCR' to the PCRF. Step 3: PCRF sends a 'Diameter CCA' back to the BPCF. Step 4: PCRF sends a 'Diameter RAR' to the HNB GW. Step 5: HNB GW sends a 'Diameter RAA' back to the PCRF. Step 6: A box labeled 'Complete the procedure for CS service' is shown on the HNB GW lifeline.](f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg) + +``` +sequenceDiagram + participant BPCF + participant HNB GW + participant PCRF + Note left of BPCF: 1. Trigger + BPCF->>PCRF: 2. Diameter CCR + PCRF-->>BPCF: 3. Diameter CCA + PCRF->>HNB GW: 4. Diameter RAR + HNB GW-->>PCRF: 5. Diameter RAA + Note right of HNB GW: 6. Complete the procedure for CS service +``` + +Sequence diagram for S9a CS session Modification. Lifelines: BPCF, HNB GW, and PCRF. The sequence starts with a '1. Trigger' on the BPCF lifeline. Step 2: BPCF sends a 'Diameter CCR' to the PCRF. Step 3: PCRF sends a 'Diameter CCA' back to the BPCF. Step 4: PCRF sends a 'Diameter RAR' to the HNB GW. Step 5: HNB GW sends a 'Diameter RAA' back to the PCRF. Step 6: A box labeled 'Complete the procedure for CS service' is shown on the HNB GW lifeline. + +**Figure E.5.2a.1: S9a CS session Modification** + +This procedure is performed when the first UE or a subsequent UE is connected to a HNB requesting a CS service. + +1. The BPCF receives the report of the QoS rule failure +2. The BPCF initiates an S9a session modification with the PCRF by sending a CCR to the PCRF with the CC-Request-Type AVP set to the value UPDATE\_REQUEST. The BPCF includes QoS-Rule-Report AVP to identify the QoS rules that failed and PCC-Rule-Status AVP set to the value “INACTIVE”. +3. The PCRF acknowledges to the BPCF by sending a CCA. +4. The PCRF initiates the S15 session modification procedure by sending a RAR command to the HNB GW and includes the information as defined in clause E.5.3.2.2 of 3GPP TS 29.212 [9]. +5. The HNB GW acknowledges to the PCRF by sending a RAA. +6. The HNB GW completes the procedure for the CS service. + +### E.5.3 S9a CS Session Termination + +In the following procedure, the PCRF is the V-PCRF for the roaming UE. + +![Sequence diagram for S9a CS Session Termination showing interactions between BPCF, HNB GW, and PCRF.](aa81b9b80bd1e3d723922b3a033564a2_img.jpg) + +``` +sequenceDiagram + participant BPCF + participant HNB_GW as HNB GW + participant PCRF + Note right of HNB_GW: 1. Trigger + HNB_GW->>PCRF: 2. Diameter CCR + PCRF-->>HNB_GW: 3. Diameter CCA + PCRF-->>BPCF: 4. Diameter RAR + BPCF-->>PCRF: 5. Diameter RAA + BPCF->>PCRF: 6. Diameter CCR + PCRF-->>BPCF: 7. Diameter CCA +``` + +The diagram illustrates the sequence of messages for S9a CS Session Termination. It involves three main entities: BPCF, HNB GW, and PCRF. The process begins with a 'Trigger' at the HNB GW. The HNB GW sends a 'Diameter CCR' (2) to the PCRF. The PCRF responds with a 'Diameter CCA' (3). The PCRF then sends a 'Diameter RAR' (4) to the BPCF. The BPCF acknowledges with a 'Diameter RAA' (5). The BPCF sends a 'Diameter CCR' (6) to the PCRF. Finally, the PCRF sends a 'Diameter CCA' (7) to the BPCF. + +Sequence diagram for S9a CS Session Termination showing interactions between BPCF, HNB GW, and PCRF. + +**Figure E.5.3.1: S9a CS Session Termination** + +1. The HNB GW initiates deregistration for the HNB or receives a deregistration request from the HNB. +2. The HNB GW initiates an S15 session termination with the PCRF by sending a CCR to the PCRF with the CC-Request-Type AVP set to the value TERMINATION\_REQUEST. +3. The PCRF acknowledges the session termination by sending a Diameter CCA message to HNB GW. +4. The PCRF sends a Diameter RAR message to the BPCF including a Session-Release-Cause AVP to indicate request for terminating the S9a session. + +NOTE: When the HNB is deregistered, there is no PS service which can be handled by the HNB any more. So S9a session for the HNB can be terminated. + +5. The BPCF acknowledges the S9a session termination request by sending a Diameter RAA message. +6. The BPCF initiates the S9a session termination with the PCRF by sending a CCR to the PCRF with the CC-Request-Type AVP set to the value TERMINATION\_REQUEST. +7. The PCRF acknowledges the session termination by sending a Diameter CCA message to BPCF. + +## E.6 PCRF Addressing + +### E.6.1 General + +PCRF discovery at the DRA shall be done according to clause 7.1 with the additions described in this clause. + +For EPC-routed scenario, the DRA keeps status of the assigned PCRF for a certain UE for the applicable reference points, i.e. Gx, Gxx, Rx, Sd (Unsolicited application reporting), S9a and S9 (for roaming cases). + +For NSWO scenario, the DRA keeps status of the assigned PCRF for a certain UE for the applicable references points, i.e. Rx, Sd (Unsolicited application reporting) and S9a. The H-DRA keeps status of the assigned H-PCRF for a certain UE for Rx and S9 reference points. The V-DRA keeps the status of the assigned V-PCRF for a certain UE for the S9a and Sd (Unsolicited application reporting) reference points. + +The BPCF, as a Diameter client of the DRA, shall support all procedures required to properly interoperate with the DRA in both the proxy and redirect modes. + +### E.6.2 DRA Definition + +For the EPC-routed scenario, DRA is defined as specified in clause 7.2 with the additions described in this clause. + +The DRA is a functional element that ensures that all Diameter sessions established over the Gx, S9, Gxx, Rx, S9a and for unsolicited application reporting, the Sd reference points for a certain IP-CAN session reach the same PCRF when multiple and separately addressable PCRFs have been deployed in a Diameter realm. + +For the NSWO scenario, the DRA shall ensure that all Diameter sessions established over the Rx, S9a and for unsolicited application reporting, the Sd reference points for a certain UE reach the same PCRF. The H-DRA shall ensure that all Diameter sessions established over Rx and S9 reference points for a certain UE reach the same PCRF. The V-DRA shall ensure that all Diameter sessions established over S9a and for unsolicited application reporting, the Sd reference points for a certain UE reach the same V-PCRF. + +### E.6.3 DRA Procedure + +#### E.6.3.1 DRA Information Storage + +For EPC-routed traffic, DRA Information Storage shall be done according to clause 7.3.1 with the additions described in this subclause. The V-PCRF routing information (i.e. DRA binding) in the V-DRA is created when the S9 session establishment trigger is received. + +The V-PCRF routing information stored in the V-DRA shall be removed when the S9 session termination notification is received. + +The DRA has information about the user identity (UE NAI), the UE Local IP address/H(e)NB Local IP address, the PDN Id (if available) and the selected PCRF identity for a certain IP-CAN Session or a certain user. + +For NSWO traffic, the DRA Information Storage shall be done as specified below: + +- The DRA shall maintain PCRF routing information per UE-NAI and APN. +- The DRA has information about the user identity (UE NAI), the local UE Ipv4 address and/or the local UE Ipv6 address/prefix, the APN (i.e. NSWO\_APN) and the selected PCRF identity for a certain UE. +- The PCRF routing information stored for an S9a\* session in the DRA shall be removed after the S9a\* session is terminated. + +When both EPC-routed and NSWO traffic exist, the DRA Information Storage shall be done as specified below: + +- The DRA shall maintain PCRF routing information per UE-NAI or per UE-NAI and APN. +- The DRA has information received for both EPC-Routed and NSWO scenarios and the selected PCRF identity per UE-NAI or per UE-NAI and APN. +- The PCRF routing information stored per UE in the DRA shall be removed when no more S9a sessions and S9a\* sessions are active for the UE. + +#### E.6.3.2 Capabilities Exchange + +For EPC-routed traffic, capabilities exchange shall be done according to clause 7.3.2. + +For NSWO traffic, the Redirect DRA and Proxy DRA shall advertise the support of S9a\*, Rx and Sd (for unsolicited application reporting) applications according to clause 7.3.3. + +#### E.6.3.3 Redirect DRA + +Redirect DRA is specified in clause 7.3.4 with the additions described in this subclause. + +For EPC-routed traffic, for case 1 (home routed case), the V-DRA shall behave as follows: + +- If the request is an S9 session establishment trigger from the H-PCRF, it shall select a V-PCRF to handle the S9 session for that UE. It shall then send the redirect message including selected V-PCRF to the H-PCRF. +- If the request is an S9 session termination notification from H-PCRF, the V-DRA shall remove the PCRF routing information (i.e. DRA binding). If the V-DRA does not have a V-PCRF already selected, it shall reject the request. + +The S9 session establishment trigger and the S9 session termination notification request shall have the same information of user identity (UE NAI), the UE Local IP address/H(e)NB Local IP address, the PDN Id(if available). The DRA shall remove the DRA binding based on the above information when the DRA receives the S9 session termination notification (i.e. a TER command including DRA- Binding AVP set to the value DRA\_BINDING\_DELETION). + +For NSWO traffic, the DRA is maintaining PCRF routing information per UE-NAI and APN. The DRA shall be aware of the S9a\* Diameter termination request as defined in 3GPP TS 29.215 [22] in order to release the DRA binding information. + +#### E.6.3.4 Proxy DRA + +Proxy DRA is specified in clause 7.3.5 with the additions described in this subclause. + +For EPC-routed traffic for case 1 (home routed case), when the V-DRA receives a message from the H-PCRF, it shall behave as follows: + +- If the message is an S9 session establishment trigger from the H-PCRF, it shall select a V-PCRF to handle the S9 session for that UE. It shall then proxy the request to the selected V-PCRF. The V-DRA indicates that there is a V-DRA deployed in the visited PLMN by including the DRA-Deployment AVP in TEA command. +- If the message is an S9 session termination notification from the H-PCRF, the V-DRA shall remove the PCRF routing information (i.e. DRA binding). If the V-DRA does not have a V-PCRF already selected, it shall reject the request. + +The S9 session establishment trigger and the S9 session termination notification shall have the same information of user identity (UE NAI), the UE Local IP address/H(e)NB Local IP address and the PDN Id (if available). The DRA shall remove the DRA binding based on the above information when the DRA receives the S9 session termination notification (i.e. a TER command including DRA-Binding AVP set to the value DRA\_BINDING\_DELETION). + +Proxy DRA is specified in clause 7.3.5 with the additions described in this subclause. + +For NSWO traffic in both non-roaming and roaming cases, when the (V-) DRA receives an S9a\* request from the BPCF, it shall behave as follows: + +- If the request is an S9a\* session establishment, it shall select a V-PCRF to handle the S9 session for that UE and APN. It shall then proxy the request to the selected V-PCRF. +- If the request is an S9a\* session termination, the (V-) DRA shall remove the PCRF routing information and proxy the request to the (V-) PCRF. If the (V-) DRA does not have a (V-) PCRF already selected, it shall reject the request. +- If the request is an S9a\* session modification, the (V-) DRA shall proxy the request. + +The BPCF shall be capable of sending every message of a session to the DRA. The BPCF may be configured to bypass the (V-) DRA on S9a\* session modification messages by sending these types of messages directly to the (V-) PCRF. + +#### E.6.3.5 PCRF selection by BPCF + +For EPC-routed traffic, when the S9a Session Establishment request is triggered by the (V-) PCRF, the BPCF may use the (V-) PCRF identity provided within the PCRF-Address AVP in the S9a Session Establishment Trigger. + +The BPCF may also use the DRA procedures as described in clause 7.3. In order to do so, the BPCF shall provide the DRA of the PCRF realm with identity parameters during the S9a Session Establishment procedure. The identity parameters from the BPCF may comprise the UE Local Ipv4 or UE local Ipv6 address in the UE-Local-IP-Address AVP (WLAN scenario), H(e)NB Local IP address in the HeNB-Local-IP-Address AVP (H(e)NB scenario), PDN information in the Called-Station-Id AVP if available and user identity in the Subscription-Id AVP. The BPCF obtains these data from the S9a Session Establishment Trigger procedure initiated by the (V-) PCRF. + +For NSWO traffic, the BPCF finds the PCRF using the DRA procedures as described in clause 7.3. In order to do so, the BPCF shall provide the DRA of the PCRF realm with identity parameters during the S9a\* Session Establishment procedure. The identity parameters from the BPCF shall comprise the UE local Ipv4 address or UE local Ipv6 prefix/address in the UE-Local-IP-Address AVP or UE-Local-IP-Prefix AVP, the APN in the Called-Station-Id AVP and user identity in the Subscription-Id AVP. + +For both EPC-routed traffic and NSWO traffic, if the redirect agent is used for DRA, the DRA shall use the redirecting requests procedure as specified in IETF RFC 6733 [61], and include the PCRF identity in the Redirect-Host AVP in the Diameter reply sent to the BPCF. + +If proxy agent is used for DRA, the DRA should use the proxy procedure as specified in IETF RFC 6733 [61]. For PA2 solution (described in clause 7.1) only S9a/S9a\* session establishment and S9a/S9a\* session termination messages shall be sent through the DRA. + +For NSWO traffic in a roaming scenario the selected V-PCRF shall belong to the same VPLMN selected during the 3GPP –based authentication procedure. The BPCF uses the VPLMN-Id to find the V-DRA in the VPLMN. The V-PCRF finds the DRA in the HPLMN according to clause 7.3.8. + +NOTE: The BPCF will use the VPLMN-Id to obtain the Destination-Realm AVP used to find the V-DRA and then to find the V-PCRF using Diameter based procedures as described in IETF RFC 6733 [61]. + +#### E.6.3.6 PCRF selection by AF and TDF in Unsolicited application reporting mode for NSWO traffic + +PCRF selection by the AF shall be done according to clause 7.3.7. + +PCRF selection by the TDF shall be done according to clause 7.3.9. + +NOTE: The DRA matches the received UE IP address received in either the Framed-IP-Address AVP or the Framed-Ipv6-Prefix AVP in the Rx and Sd reference point with the UE Local IP Address received in UE-Local-IP-Address AVP or UE Local Ipv6 Prefix in the UE-Local-IP-Prefix AVP in the S9a reference point in order to select the same PCRF. + +#### E.6.3.7 PCRF selection in a roaming scenario + +For both EPC-routed traffic and NSWO traffic, the V-PCRF uses the DRA procedures as described in clause 7.3.8 to address the H-PCRF. In order to do so, the V-PCRF shall provide the DRA of the H-PCRF realm with identity parameters during the S9 Session Establishment procedure. + +For EPC-routed traffic, the identity parameters from the V-PCRF may comprise the UE Local Ipv4 or UE local Ipv6 address in the UE-Local-IP-Address AVP (WLAN scenario), H(e)NB Local IP address in the HeNB-Local-IP-Address AVP (H(e)NB scenario), PDN information in the Called-Station-Id AVP if available and user identity in the Subscription-Id AVP obtained from the S9 Session Establishment Trigger procedure initiated by the H-PCRF. + +For NSWO traffic, the identity parameters from the V-PCRF may comprise the UE Local Ipv4 or Ipv6 address in the UE-Local-IP-Address AVP or UE local Ipv6 prefix in the UE-Local-IP-Prefix AVP, PDN information in the Called-Station-Id AVP and user identity in the Subscription-Id AVP obtained from the S9a\* Session Establishment procedure. + +#### E.6.3.8 PCRF selection for the HNB CS Service + +When the DRA receives a request for a certain S15 Session establishment from the HNB GW, the DRA selects a suitable PCRF for the S15 Session based on the HNB local IP address within the HeNB-Local-IP-Address AVP. When the S15 Session is terminated, the DRA shall remove the information about the S15 Session. + +### E.6.4 DRA flows + +#### E.6.4.1 General + +For the EPC-routed traffic case and for the non-roaming case, the flows for the non-roaming case in the clauses 7.4.1 and 7.4.2 are applied with the following exception: + +- BPCF acts as a client and messages are S9a Diameter messages; +- The external trigger in the Establishment of Diameter Sessions is an S9a session establishment trigger message from the PCRF + +For the EPC-routed traffic case and for the roaming case, the flows for the roaming case in clauses 7.4.1 and 7.4.2 are applied with the following exception: + +- The external trigger in the Establishment of Diameter Sessions is an S9 session establishment trigger message from the PCRF for case 1 and home routed case. + +The flows in clauses E.6.4.2 and E.6.4.3 are applicable to the EPC-routed traffic and for case 1 and UE roaming in the home routed scenario. + +For the NSWO traffic case and for the non-roaming case, the flows for the non-roaming and roaming case in the clauses 7.4.1 and 7.4.2 are applied with following exception: + +- BPCF acts as a client and messages are S9a\* Diameter messages for the non-roaming case. + +#### E.6.4.2 Proxy DRA + +##### E.6.4.2.1 S9 session establishment trigger + +![Sequence diagram illustrating the S9 session establishment trigger using DRA (proxy) for a roaming case. The diagram shows four lifelines: H-PCRF, V-DRA (proxy), V-PCRF-1, and V-PCRF-2. The sequence of messages is: 1. External trigger (arrow to H-PCRF), 2. TER (H-PCRF to V-DRA), 3. DRA binding creation (internal message on V-DRA), 4. Proxy TER (V-DRA to V-PCRF-1), 5. TEA (V-PCRF-1 to V-DRA), 6. Proxy TEA (V-DRA to H-PCRF).](5a24ac755b962fd5f0183f13de0726de_img.jpg) + +``` + +sequenceDiagram + participant External + participant H-PCRF + participant V-DRA as V-DRA (proxy) + participant V-PCRF-1 + participant V-PCRF-2 + + External->>H-PCRF: 1. External trigger + H-PCRF->>V-DRA: 2. TER + Note right of V-DRA: 3. DRA binding creation + V-DRA->>V-PCRF-1: 4. Proxy TER + V-PCRF-1->>V-DRA: 5. TEA + V-DRA->>H-PCRF: 6. Proxy TEA + +``` + +Sequence diagram illustrating the S9 session establishment trigger using DRA (proxy) for a roaming case. The diagram shows four lifelines: H-PCRF, V-DRA (proxy), V-PCRF-1, and V-PCRF-2. The sequence of messages is: 1. External trigger (arrow to H-PCRF), 2. TER (H-PCRF to V-DRA), 3. DRA binding creation (internal message on V-DRA), 4. Proxy TER (V-DRA to V-PCRF-1), 5. TEA (V-PCRF-1 to V-DRA), 6. Proxy TEA (V-DRA to H-PCRF). + +**Figure E.6.4.2.1.1: S9 session establishment trigger using DRA (proxy) – Roaming case** + +1. The H-PCRF receives an external trigger (e.g. IP-CAN session establishment request) and determines that an S9 session shall be established. +2. A TER command including user identity, PDN ID if available, UE Local IP address/H(e)NB Local IP address and UDP source port number(if NA(P)T is detected) is sent by the H-PCRF and received by a V-DRA (proxy) in + +the visited PLMN. The Auth-Session-State AVP set to NO\_STATE\_MAINTAINED shall be included in the TER. + +3. The V-DRA (proxy) stores the user identity and creates a dynamic DRA binding for this user. (assignment of a PCRF node per UE). +4. The V-DRA (proxy) proxies the TER to the target PCRF in the visited PLMN. +5. V-PCRF-1 returns a TEA to the V-DRA (proxy). +6. V-DRA (proxy) proxies the TEA to the H-PCRF and indicates there is a DRA deployed in the visited PLMN by including the DRA-Deployment AVP in the TEA. + +NOTE: The H-PCRF is aware that there is a V-DRA (proxy) deployed in the network at this stage. + +##### E.6.4.2.2 S9 session termination notification + +![Sequence diagram for S9 session termination notification using V-DRA (proxy) in roaming cases. The diagram shows four lifelines: H-PCRF, V-DRA (proxy), V-PCRF-1, and V-PCRF-2. The sequence of messages is: 1. H-PCRF initiates S9 session termination; 2. H-PCRF sends a TER message to V-DRA (proxy); 3. V-DRA (proxy) performs DRA binding verification and release; 4. V-DRA (proxy) sends a TEA message back to H-PCRF.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +``` +sequenceDiagram + participant H-PCRF + participant V-DRA as V-DRA (proxy) + participant V-PCRF-1 + participant V-PCRF-2 + Note left of H-PCRF: 1. H-PCRF initiated S9 session termination + H-PCRF->>V-DRA: 2. TER + Note right of V-DRA: 3. DRA binding verification and release + V-DRA->>H-PCRF: 4. TEA +``` + +Sequence diagram for S9 session termination notification using V-DRA (proxy) in roaming cases. The diagram shows four lifelines: H-PCRF, V-DRA (proxy), V-PCRF-1, and V-PCRF-2. The sequence of messages is: 1. H-PCRF initiates S9 session termination; 2. H-PCRF sends a TER message to V-DRA (proxy); 3. V-DRA (proxy) performs DRA binding verification and release; 4. V-DRA (proxy) sends a TEA message back to H-PCRF. + +**Figure E.6.4.2.2.1: S9 session termination notification using V-DRA (proxy) – Roaming cases** + +1. The H-PCRF receives an external trigger (e.g. IP-CAN session termination request from the BBERF or the PCEF) and initiates S9 session termination procedure. +2. If the V-DRA is deployed in the VPLMN as indicated in step 6 of clause E.6.4.2.1, a TER command including DRA-Binding AVP set to the value DRA\_BINDING\_DELETION is sent by the H-PCRF and received by the V-DRA (proxy) in the visited PLMN. The message includes the same user identity as the S9 session establishment trigger message. +3. The V-DRA (proxy) verifies that there is an active DRA binding for the user based on the user identity in the request and removes the DRA binding. +4. V-DRA (proxy) returns the TEA to the H-PCRF. + +#### E.6.4.3 Redirect DRA + +##### E.6.4.3.1 S9 session establishment trigger + +![Sequence diagram for S9 session establishment trigger using DRA (Redirect) – Roaming case. The diagram shows four lifelines: H-PCRF, V-DRA (Redirect), V-PCRF-1, and V-PCRF-2. The sequence of messages is: 1. External trigger to H-PCRF; 2. TER from H-PCRF to V-DRA; 3. DRA binding creation (internal to V-DRA); 4. TEA(redirect) from V-DRA to H-PCRF; 5. TER from H-PCRF to V-PCRF-1; 6. TEA from V-PCRF-1 to H-PCRF.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +``` + +sequenceDiagram + participant External + participant H-PCRF + participant V-DRA as V-DRA (Redirect) + participant V-PCRF-1 + participant V-PCRF-2 + + External->>H-PCRF: 1. External trigger + H-PCRF->>V-DRA: 2. TER + Note right of V-DRA: 3. DRA binding creation + V-DRA->>H-PCRF: 4. TEA(redirect) + H-PCRF->>V-PCRF-1: 5. TER + V-PCRF-1->>H-PCRF: 6. TEA + +``` + +Sequence diagram for S9 session establishment trigger using DRA (Redirect) – Roaming case. The diagram shows four lifelines: H-PCRF, V-DRA (Redirect), V-PCRF-1, and V-PCRF-2. The sequence of messages is: 1. External trigger to H-PCRF; 2. TER from H-PCRF to V-DRA; 3. DRA binding creation (internal to V-DRA); 4. TEA(redirect) from V-DRA to H-PCRF; 5. TER from H-PCRF to V-PCRF-1; 6. TEA from V-PCRF-1 to H-PCRF. + +**Figure E.6.4.3.1.1: S9 session establishment trigger using DRA (Redirect) – Roaming case** + +1. The H-PCRF receives an external trigger (e.g. IP-CAN session establishment request) and determines that an S9 session shall be established. +2. A TER command including user identity, PDN ID if available, UE Local IP address/H(e)NB Local IP address, UDP source port number(if NA(P)T is detected) and the FQDN of Fixed Broadband network where the H(e)NB is connected to if available is sent by the H-PCRF and received by a V-DRA (proxy) in the visited PLMN. The Auth-Session-State AVP set to NO\_STATE\_MAINTAINED shall be included in the TER. +3. The V-DRA (redirect) stores the user identity and creates a dynamic DRA binding for this user. (assignment of a PCRF node per UE). +4. The V-DRA (redirect) sends a TEA command indicating redirection as defined in IETF RFC 6733 [61]. The target V-PCRF identity is included in the Redirect-Host AVP. + +NOTE: The H-PCRF is aware that there is a V-DRA (redirect) deployed in the network at this stage. + +5. The H-PCRF re-sends the TER command of step 2 to the target V-PCRF-1. +6. The V-PCRF-1 returns a TEA 11vailab. + +##### E.6.4.3.2 S9 session termination notification + +The detailed procedure is the same as the S9 session termination notification using DRA (Proxy), which is described in clause E.6.4.2.2. + +If the H-PCRF was aware that there is a V-DRA deployed in the V-PLMN (step 4 of S9 session establishment procedure according to clause E.6.4.3.1), this procedure shall apply. + +## --- E.7 BPCF Addressing + +### E.7.1 General + +For S9a session establishment trigger procedure initiated by the (V-)PCRF, the PCRF (for non-roaming case) and the V-PCRF (for roaming case) is configured with IP address range mappings { (Ipx..Ipy) -> BBF network entry point}. The PCRF (for non-roaming) and the V-PCRF (for roaming cases) selects the correct BBF network entry point based on UE Local IP address for WLAN scenario and based on H(e)NB IP address and FQDN if available for H(e)NB case received from the PCEF/BBERF/HNB GW for H(e)NB scenario. The implementation of a BBF network entry point is out-of-scope for 3GPP e.g. be a BPCF or a DRA. + +For case 1 and roaming with home routed, for S9 session establishment trigger procedure initiated by the H-PCRF, H-PCRF finds the VPLMN according to the PLMN Id of the visited network in 3GPP-SGSN-MCC-MNC AVP if received at IP-CAN session establishment received over Gx reference point, and then discovers V-PCRF by V-DRA if there are more than one PCRF deployed in the visited network. The H-PCRF sends the H(e)NB Local IP address within HeNB-Local-IP-Address AVP and optionally the FQDN of BBF access network within the HeNB-BBF-FQDN AVP for H(e)NB scenario or the UE local IP address within the UE-Local-IP-Address AVP for WLAN scenario to the V-PCRF over the S9 reference point. + +## --- E.8 Session Linking Function + +PCRF and BPCF needs to support session linking function. The PCRF shall be able to perform the linking between multiple Gx and Gateway Control Session to the same S9a session. + +When receiving an IP-CAN Session Establishment request or an IP-CAN Session modification request with an UE local IP address or H(e)NB local IP address, the PCRF shall perform the session linking between the S9a session and the corresponding Gx session according to the UE Local IP address/ H(e)NB local IP address. + +When receiving a Gateway Control Session Establishment Request or a Gateway Control and QoS Rule Request with UE local IP Address or a H(e)NB local IP Address change, the PCRF shall perform the session linking between the S9a session and the Gateway Control Session according to the UE Local IP address/ H(e)NB local IP address. + +If there is not an established S9a session which could be linked to the Gx or Gateway Control Session, the PCRF shall initiate the S9a Session Establishment trigger procedure. + +For 3GPP HNB Procedures with CS support, the PCRF shall be able to perform the linking between S15 sessions and the S9a session. + +NOTE 1: There is a single S15 session per HNB for CS calls for all Ues connected to the HNB in order to improve performance. In addition, for CS calls there are no UE specific policies and therefore a single PCRF can handle CS calls for all Ues. + +# --- Annex F (normative): Access specific aspects, Fixed Broadband Access network convergence + +## F.1 General + +This annex defines the enhancement to PCC framework for supporting policy and charging control in the fixed broadband access network in the convergent scenario where the PCRF controls directly the network element(s) in the fixed broadband access without the mediation of a different policy server, such as the Broadband Policy Control Function (BPCF). + +Policy and charging control is provided for both Non-seamless WLAN offload traffic from a 3GPP UE and the traffic from fixed devices. + +## --- F.2 Definitions and abbreviations + +### F.2.1 Definitions + +The definitions in the following are relevant for this Annex only. + +**UE local IP address** is defined as either the public IP address assigned to the UE by the Broadband Forum domain in the no-NAT case, or the public IP address assigned by the Broadband Forum domain to the NATed RG. + +**IP-CAN session** as defined in clause 3.1 applies with the following clarifications for fixed broadband access. The term UE corresponds to the device that accesses the services provided by the network (i.e. either RG, or 3GPP UE or fixed end-device), the PDN identifies the IP network where the device gets IP connectivity and the UE identity information may be the IMSI, the user-name or the access line identifier (if available). In a Fixed Broadband Access an IP-CAN session corresponds to a Subscriber IP Session defined in Broadband Forum TR-146. + +NOTE: The PDN connection concept and APN are not applicable to a Subscriber IP session for a fixed device. + +### F.2.2 Abbreviations + +The following abbreviations are relevant for this annex only: + +| | | +|----------|-----------------------------------| +| BBF | Broadband Forum | +| BPCF | Broadband Policy Control Function | +| NSWO | Non-Seamless WLAN offload | +| NSWO-APN | Non-Seamless WLAN offload APN | +| RG | Residential Gateway | + +## --- F.3 Binding Mechanisms + +### F.3.1 NSWO traffic + +The binding mechanism in clause 5 applies, except that the QoS rule generation as described in clause 5.4 and the bearer binding as described in clause 5.4 do not apply since the Fixed Broadband Access network does not support the concept of a bearer and multiple bearers as defined in 3GPP network. + +The following exceptions or modifications in PCC rule authorization also apply: + +- The PCRF does not authorize traffic mapping information from the UE. + +- The PCEF in the IP Edge would map the received QoS information over Gx into the relevant data as specified in Broadband Forum. +- MPS, RLOS and emergency services are not supported. +- BCM concept is not applied. + +### F.3.2 Traffic from fixed devices + +The binding mechanism as described in Annex F.3.1 applies to the scenario of traffic from fixed devices with the following exceptions or modifications: + +- S9 reference point is not applicable. +- The Subscriber Identifier used by fixed device at establishment of Subscriber IP session in Fixed Broadband Access network can be the Access Line Identifier (Physical-Access-ID AVP and Logical-Access-ID AVP) or the username (Subscription-Id AVP), for example when the Subscriber IP session is a PPP Session. + +NOTE: In case the Subscriber Identifier in the IP-CAN and the application level identity for the fixed device are of different kinds, the PCRF needs to map between them. Such mapping is not subject to specification within this TS. + +## --- F.4 PCC procedures + +### F.4.1 Introduction + +The PCC procedures specified in clause 4.1, 4.2 and 4.3 apply to the Fixed Broadband Access network convergence with the following exceptions or restrictions: + +- Roaming scenarios are not applicable to fixed devices and RGs. +- Gxx reference point is not used. +- UE requested bearer resource initiation, modification or termination procedure is not supported. +- Bearer procedures are not supported in the fixed network. +- Bearer Control Mode (BCM) concept does not apply. +- Authorized QoS per bearer and authorized MBR per QCI are not applicable +- MPS Services, RLOS and IMS Emergency Services are not supported. + +### F.4.2 IP-CAN Session Establishment + +The PCEF in the IP Edge initiates the IP-CAN session establishment as specified in clause 4.1, with the exceptions as described in Annex F.4.1. The PCRF shall provide parameters to the PCEF in the IP Edge at IP-CAN session establishment as described in 3GPP TS 29.212 [9] Annex G.5.2. + +### F.4.3 IP-CAN Session Termination + +#### F.4.3.1 UE-Initiated + +UE-initiated IP-CAN session termination is not applicable to convergent scenario. + +#### F.4.3.2 PCEF-Initiated + +For PCEF-Initiated IP-CAN session termination the procedures described in clause 4.2.2 apply, with the exceptions described in clause F.4.1. + +#### F.4.3.3 PCRF-Initiated + +For PCRF-Initiated IP-CAN session termination the procedures described in clause 4.2.3 apply, with the exceptions described in clause F.4.1. + +### F.4.4 IP-CAN Session Modification + +#### F.4.4.1 PCRF-Initiated IP-CAN Session Modification + +For PCRF-Initiated IP-CAN session modification, the procedures described in clause 4.3.1 apply, with the exceptions described in clause F.4.1. The PCRF shall provide parameters to the PCEF in the IP Edge at IP-CAN session modification as described in 3GPP TS 29.212 [9] Annex G.5.4.2. + +#### F.4.4.2 PCEF-Initiated IP-CAN Session Modification + +For PCEF-Initiated IP-CAN session modification, the procedures described in clause 4.3.2 apply, with the exceptions described in clause F.4.1. The PCRF shall provide parameters to the PCEF in the IP Edge at IP-CAN session modification as described in 3GPP TS 29.212 [9] Annex G.5.4.1. + +## --- F.5 PCRF Addressing + +### F.5.1 General + +PCRF discovery and selection shall be done according to clause 7.1 with the modifications or exceptions described in this subclause. + +- Gxx reference point is not used. +- The Subscriber Identifier specified in 3GPP TS 23.203 [2] clause S.5.1.2 is used as user identity. +- For a 3GPP UE, the NSWO-APN is also available. +- The IPv6 address within the Framed-IPv6-Prefix may be included in the CCR command in the case of bridge-mode RG. + +### F.5.2 DRA Definition + +The DRA definition in clause 7.2 applies with the modifications or exceptions as described in Annex F.5.1. + +### F.5.3 DRA Procedure + +#### F.5.3.1 Redirect DRA + +Redirect DRA is specified in clause 7.3.4 with the adaptions listed in F.5.1. + +#### F.5.3.2 Proxy DRA + +Proxy DRA is specified in clause 7.3.5 with the adaptions listed in F.5.1. + +#### F.5.3.3 PCRF selection by AF and TDF in unsolicited application reporting mode + +PCRF selection by the AF shall be done according to clause 7.3.7 with the modifications or exceptions as described in Annex F.5.1. PCRF selection by the TDF shall be done according to clause 7.3.9 with the modifications or exceptions as described in Annex F.5.1. + +#### F.5.3.4 PCRF selection in a roaming scenario + +The procedures as described in clause 7.3.8 for the V-PCRF to select the H-PCRF apply with the modifications or exceptions as described in Annex F.5.1. + +### F.5.4 DRA flows + +The DRA procedures specified in clause 7.4.1 and 7.4.2 apply to the Fixed Broadband Access network convergence with the following exceptions or restrictions: + +- Gxx reference point is not used. +- Roaming scenarios are not applicable to fixed devices and RGs. + +# --- Annex G (normative): Diameter overload control mechanism + +## G.1 General + +Support for Diameter overload control by PCC functional elements is optional. Unless otherwise stated, the procedures defined in this Annex assume that a PCC functional element supports the Diameter overload control mechanism. + +IETF RFC 7683 [33] specifies the Diameter overload control mechanism. This includes the definition of Diameter overload related AVPs and the Diameter overload related behavior. + +To indicate support of the Diameter overload control mechanism, each PCC functional element shall include the OC-Supported-Features AVP in every Diameter request and answer as defined in IETF RFC 7683 [33]. + +Each PCC functional element (e.g. PCRF, PCEF, AF, etc) shall act as a reacting node and as a reporting node as defined in IETF RFC 7683 [33]. + +## --- G.2 Reporting Node + +When a PCC functional element determines the need to request a reduction in the traffic it is handling due to an overload condition, it shall include the OC-OLR AVP in answer messages, as defined in IETF RFC 7683 [33]. + +How it determines that it is in an overload situation and the severity of the overload is implementation dependent and based on operator policy. + +How it determines the specific contents of the OC-OLR AVP is implementation dependent and based on operator policy. + +## --- G.3 Reacting Node + +A PCC functional element acting as a reacting node applies the requested traffic reduction received in OC-OLR AVPs in answer messages to corresponding applicable requests, as per IETF RFC 7683 [33]. + +How it achieves the requested traffic reduction is implementation dependent. + +Diameter requests related to priority traffic (e.g. MPS) as described in 3GPP TS 22.153 [58] and emergency have the highest priority. If required by the regional/national regulatory and operator policies, and when the reacting node is able to detect priority traffic, priority traffic shall be exempted from throttling due to Diameter overload control up to the point where requested traffic reduction cannot be achieved without throttling the priority traffic. Relative priority amongst various priority traffic (e.g. MPS) and emergency traffic is subject to regional/national regulatory and operator policies. + +## --- G.4 DRA Diameter Overload Behavior + +The DRA may optionally incorporate agent behavior specified in IETF RFC 7683 [33]. + +### G.4.1 DRA reacting to Host Reports + +The procedures defined in this clause are only applicable to the proxy DRA (PA1 and PA2) as the redirect DRA is not in the path of application answers and as such does not have access to overload reports from other nodes. + +The proxy DRA shall use host reports as one of the inputs when making routing decisions for realm-routed requests, i.e. requests that do not contain a Destination-Host AVP. This is needed because entities sending such requests are not aware of the final recipient of the request (e.g. specific PCRF instance). + +The following scenarios shall be addressed: + +- No binding exists for the request and the request can result in a new binding (e.g. IP-CAN session establishment); in this case the DRA is selecting the PCRF that will handle the binding. The DRA should use any active and relevant Diameter overload host reports as one of the inputs to the selection of the PCRF. If all PCRFs are in an overload state, the DRA should reduce traffic sent to each of the PCRFs based on the individual host requested traffic reduction. This may result in the DRA rejecting the request. +- A binding already exists for the request – In this case the DRA should reduce the traffic sent to the overloaded node by the host requested traffic reduction. This may result in the DRA rejecting the request. + +NOTE: Result-Code when rejecting a request in the above cases need to be used according to the IETF RFC 7683 [33]. + +How the DRA achieves any requested traffic reduction is implementation dependent and/or based on operator policy. + +# --- Annex H (normative): Access specific procedures for 3GPP EPS + +## H.1 General + +The present annex defines IP-CAN specific requirements for 3GPP Evolved Packet System (EPS). + +## --- H.2 Binding Mechanisms + +The procedures defined in clause 5.4 apply. + +Whenever the PCRF modifies the Authorized QoS of the default bearer, the BBF shall re-evaluate the bearer binding taking into account the default bearer QoS change the default bearer binding indication in the PCC Rule if applicable and any PCC Rule/QoS Rule operation requested by the PCRF. + +# --- Annex I (normative): APN matching procedures + +A PCRF or DRA needs to compare APN information received over different interfaces, for instance within the Called-Station-Id AVP, for certain purposes such as session binding. To do so, the PCRF or DRA shall apply the procedures in the present Annex. + +The PCRF or DRA shall consider the different possible encoding formats of the APN defined in 3GPP TS 23.003 [37], clause 9.1. When the PCRF or DRA needs to compare an APN only containing the APN Network Identifier, with an APN containing both APN Network Identifier and APN Operator Identifier, the PCRF shall consider those APNs as matching if their APN Network Identifiers match. The PCRF shall perform a case-insensitive comparison for APN Network Identifiers and APN Operator Identifiers. + +# --- Annex J (normative): Diameter message priority mechanism + +## J.1 General + +The support of the Diameter message priority mechanism by PCC functional elements is optional. PCC functional elements that support Diameter message priority mechanism shall comply with the procedures specified in this annex. + +IETF RFC 7944 [40] specifies the Diameter message priority mechanism that allows Diameter nodes to indicate the relative priority of Diameter messages. With this information, other Diameter nodes can leverage the relative priority of Diameter messages into routing, resource allocation, set the DSCP marking for transport of the associated Diameter message, and also abatement decisions when overload control is applied. This includes the definition of Diameter message priority related AVPs and the Diameter message priority related behaviour. + +## --- J.2 PCC functional element behaviour + +A PCC functional entity supporting the Diameter message priority mechanism shall comply with IETF RFC 7944 [40]. + +A PCC functional element sending a request shall determine the required priority according to its policies. When priority is required, the PCC functional element shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request according to the required priority level + +When the PCC functional element receives the corresponding response, it shall prioritise the received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request. + +When a PCC functional element receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, it may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, it shall include the DRMP AVP in the response. + +If: + +- a PCC functional element supports using the Diameter message priority mechanism for DSCP marking purposes, +- the transport network utilizes DSCP marking, and +- message-dependant DSCP marking is possible for the protocol stack transporting Diameter, + +then the PCC functional element shall set the DSCP marking for transport of the request or response according to the required priority level. + +The PCC functional element decisions for a required priority and the priority level value are implementation specific. + +Diameter requests related to high priority traffic (e.g. MPS, emergency) shall contain a DRMP AVP with a high priority of which the level is operator dependent. + +## --- J.3 Interactions + +If the PCC entity supporting the Diameter message priority mechanism receives the request message containing both the Reservation-Priority AVP and DRMP AVP, the PCC entity shall prioritise the request according to priority level received within the DRMP AVP. This procedure also applies for MPS. + +NOTE: Upon receipt of the request message containing the DRMP AVP, the PCRF will use the DRMP AVP to prioritize other PCC interfaces related to that IP-CAN session. + +# --- Annex K (normative): Diameter load control mechanism + +## K.1 General + +IETF RFC 8583 [60] specifies the Diameter load control mechanism. This includes the definition of Diameter Load AVP and the Diameter load related behaviour. + +Whether Diameter load control mechanism is applicable for a specific interface is specified in the 3GPP specification for that interface. For PCC related interfaces where the Diameter load control mechanism is applicable, the procedures in this Annex apply. + +Support for Diameter load control is optional for all PCC functional elements. + +NOTE: The Diameter Load AVP will simply be ignored by peers not supporting Diameter load control. + +If a PCC functional element supports the Diameter load control mechanism, it shall apply the procedures in the present Annex. + +The PCC functional elements that are recipients of realm-routed requests (e.g. PCRF, H-PCRF, TDF for solicited application reporting, TSSF, OCS) shall for that interface act as Endpoint Reporting Node as defined in IETF RFC 8583 [60]. + +The PCC functional elements that send realm-routed requests (e.g. PCRF, V-PCRF, PCEF, AF) shall for that interface act as Reacting Node as defined in IETF RFC 8583 [60]. + +## --- K.2 Endpoint or Agent Reporting Node + +The reporting shall include load information in the Load AVP as defined in IETF RFC 8583 [60] in Diameter answer messages. + +When and in which frequency to include the Load AVP is implementation dependent and based on operator policy. + +How the reporting node determines the specific contents of the Load-Value AVP within the Load AVP is also implementation dependent and based on operator policy. + +## --- K.3 Reacting Node + +A PCC functional element acting as a Reacting Node may use the load information in implementation dependent manner, e.g. when deciding where to route requests for new Diameter sessions. + +## --- K.4 DRA Behaviour + +The DRA may optionally incorporate Reacting Node behaviour as defined in IETF RFC 8583 [60]. Support of Agent Reporting Node behaviour as defined in IETF RFC 8583 [60] is not required. + +NOTE: Only one logical DRA is specified in the PCC architecture. The Agent Reporting Node behaviour as defined in IETF RFC 8583 [60] is only useful if several Diameter routing agents are deployed. i.e. not in the PCC architecture. + +The procedures defined in this clause are only applicable to the proxy DRA (PA1 and PA2) as the redirect DRA is not in the path of application answers and as such does not have access to load reports from other nodes. + +The proxy DRA should use load reports as one of the inputs when making routing decisions and selection of the PCRF for realm-routed requests, i.e. requests that do not contain a Destination-Host AVP. This is needed because entities sending such requests are not aware of the final recipient of the request (e.g. specific PCRF instance). If no binding exists for the request and the request can result in a new binding (e.g. IP-CAN session establishment), the DRA is selecting the PCRF that will handle the binding. + +# Annex L (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +|---------|-------|-----------|------|-----|-------------------------------------------------------------------------------------|--------|--------| +| 12-2014 | CT-66 | CP-140922 | 0575 | 2 | Call flows over Np reference point | 12.5.0 | 13.0.0 | +| 12-2014 | CT-66 | CP-140935 | 0576 | 2 | Double Resource Reuse procedures | 12.5.0 | 13.0.0 | +| 03-2015 | CT-67 | CP-150131 | 0579 | | IPCAN Session modification after bearer procedure | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150134 | 0580 | | P-CSCF Restoration Procedure for Local Breakout | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150136 | 0581 | | Priority Consideration for Diameter Overload Control | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150132 | 0582 | | Correction to the Gateway Control Session establishment procedure | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150136 | 0583 | | PCRF discovery for the HNB CS Service | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150094 | 0590 | | Corrections to the Gateway Control and QoS rules Provision procedure | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150125 | 0592 | | Add missing definition of RAN user plane congestion | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150125 | 0593 | 2 | DRA procedure to support PCRF selection by the RCAF | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150111 | 0595 | | Remove editor's Note on access line identifier | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150125 | 0596 | 2 | UE context removal in IP-CAN session termination procedure | 13.0.0 | 13.1.0 | +| 06-2015 | CT-68 | CP-150342 | 0601 | 1 | Remove the user identity from the intermediate spending limit report request | 13.1.0 | 13.2.0 | +| 06-2015 | CT-68 | CP-150342 | 0604 | 2 | Correction to the IP-CAN session termination for spending limit report | 13.1.0 | 13.2.0 | +| 06-2015 | CT-68 | CP-150355 | 0605 | 1 | Alignment with the changes of 29.217 | 13.1.0 | 13.2.0 | +| 06-2015 | CT-68 | CP-150355 | 0606 | 1 | Reference update to align with new title of TS 29.217 | 13.1.0 | 13.2.0 | +| 06-2015 | CT-68 | CP-150361 | 0607 | 1 | Correction of the editorial errors in Network-initiated IP-CAN session modification | 13.1.0 | 13.2.0 | +| 06-2015 | CT-68 | CP-150354 | 0609 | 2 | QoS change of default bearer | 13.1.0 | 13.2.0 | +| 06-2015 | CT-68 | CP-150362 | 0610 | 3 | APN matching procedures | 13.1.0 | 13.2.0 | +| 09-2015 | CT-69 | CP-150480 | 0612 | - | Procedures for monitoring when using the PCC architecture | 13.2.0 | 13.3.0 | +| 09-2015 | CT-69 | CP-150482 | 0614 | 1 | Procedures to allow changing the chargeable party when sponsor connectivity applies | 13.2.0 | 13.3.0 | +| 09-2015 | CT-69 | CP-150490 | 0616 | 2 | Correction on bearer binding on QoS rules | 13.2.0 | 13.3.0 | +| 09-2015 | CT-69 | CP-150477 | 0617 | 5 | Clarification of the PCRF addressing for UPON | 13.2.0 | 13.3.0 | +| 09-2015 | CT-69 | CP-150491 | 0618 | 2 | PCC signalling update to support NBIFOM | 13.2.0 | 13.3.0 | +| 09-2015 | CT-69 | CP-150485 | 0619 | 2 | Clarification of PCRF address | 13.2.0 | 13.3.0 | +| 12-2015 | CT-70 | CP-150649 | 0620 | 1 | Authorized QCI value in PCRF to avoid SRVCC | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150650 | 0621 | 6 | Update the procedures to support traffic steering control | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150809 | 0622 | 3 | Include the PCC architecture figures in 29.213l | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150632 | 0625 | 2 | Overlapping transactions over Gx | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150666 | 0626 | - | RTP/RTCP transport multiplexing | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150730 | 0629 | 6 | Diameter message priority for PCC | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150663 | 0630 | 4 | Support of new bandwidth information over Rx | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150631 | 0633 | 1 | Update the reference of draft-ietf-dime-ovli | 13.3.0 | 13.4.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-03 | CT#71 | CP-160107 | 0638 | - | F | Network-initiated removal of one access from the PDN connection | 13.5.0 | +| 2016-03 | CT#71 | CP-160091 | 0639 | 2 | B | ADC rule error handling report initiated by the TSSF | 13.5.0 | +| 2016-03 | CT#71 | CP-160091 | 0640 | - | F | IPv4 address provisioning | 13.5.0 | +| 2016-03 | CT#71 | CP-160095 | 0641 | 2 | F | Update the scope to include the Nt interface | 13.5.0 | +| 2016-03 | CT#71 | CP-160091 | 0645 | 2 | F | Update the scope to include the St interface | 13.5.0 | +| 2016-03 | CT#71 | CP-160101 | 0646 | - | D | Correction of command name for Rx session termination | 13.5.0 | +| 2016-03 | CT#71 | CP-160101 | 0648 | 2 | F | Completion of RAN-NAS cause handling procedures | 13.5.0 | +| 2016-03 | CT#71 | CP-160095 | 0650 | - | B | Support of background data transfer per UE in the PCRF | 13.5.0 | +| 2016-03 | CT#71 | CP-160092 | 0651 | 1 | B | UE-to-network relay PCC handling | 13.5.0 | +| 2016-03 | CT#71 | CP-160106 | 0652 | - | D | Removal of the reference to draft-ietf-dime-ovli | 13.5.0 | +| 2016-03 | CT#71 | CP-160095 | 0653 | - | B | Rx impact for background data transfer | 13.5.0 | +| 2016-03 | CT#71 | CP-160093 | 0654 | 2 | B | Reservation-Priority AVP and DRMP AVP Interaction | 13.5.0 | +| 2016-03 | CT#71 | CP-160101 | 0656 | 1 | F | Removal of references to TS 26.236 | 13.5.0 | +| 2016-03 | CT#71 | CP-160087 | 0657 | 1 | B | The value of ARP for MCPTT emergency | 13.5.0 | +| 2016-03 | CT#71 | CP-160101 | 0658 | - | F | Correction to eMPS algorithm | 13.5.0 | +| 2016-06 | CT#72 | CP-160270 | 0660 | 2 | F | Support of enhanced bandwidth mechanisms in MTSI sessions | 13.6.0 | +| 2016-06 | CT#72 | CP-160265 | 0661 | 1 | F | Editorial corrections | 13.6.0 | +| 2016-06 | CT#72 | CP-160278 | 0662 | 2 | F | Priority sharing for concurrent sessions | 13.6.0 | +| 2016-06 | CT#72 | CP-160267 | 0665 | - | A | P-CSCF restoration indication by Rx-Request-Type AVP | 13.6.0 | +| 2016-06 | CT#72 | CP-160251 | 0666 | - | F | Correction to sponsor status change | 13.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------|--------| +| 2016-06 | CT#72 | CP-160265 | 0667 | 2 | F | Delete the Editor's Note in subclause of DRA diameter overload behavior | 13.6.0 | +| 2016-06 | CT#72 | CP-160253 | 0669 | 2 | A | Diameter requests for priority traffic during overload control mechanism | 13.6.0 | +| 2016-06 | CT#72 | CP-160274 | 0659 | 2 | B | Adding the reference to the gate control procedure over Rx interface | 14.0.0 | +| 2016-06 | CT#72 | CP-160265 | 0661 | 1 | F | Editorial corrections | 14.0.0 | +| 2016-09 | CT#73 | CP-160442 | 0671 | - | A | Correction of IETF drmp draft version | 14.1.0 | +| 2016-09 | CT#73 | CP-160443 | 0676 | - | A | Correction to eMPS Algorithm | 14.1.0 | +| 2016-09 | CT#73 | CP-160445 | 0678 | - | A | Update the AF session procedures to support priority sharing | 14.1.0 | +| 2016-09 | CT#73 | CP-160453 | 0680 | 1 | A | Correction to the PCRF addressing by RCAF | 14.1.0 | +| 2016-09 | CT#73 | CP-160456 | 0681 | 3 | B | Flows for Subscription to notification of PLMN id change in IMS | 14.1.0 | +| 2016-09 | CT#73 | CP-160457 | 0682 | 2 | B | Correction to the PCRF addressing by RCAF | 14.1.0 | +| 2016-12 | CT#74 | CP-160615 | 0683 | 4 | B | Diameter Load Control Mechanism | 14.2.0 | +| 2016-12 | CT#74 | CP-160614 | 0685 | - | A | Correction to change IETF drmp draft version to official RFC 7944 | 14.2.0 | +| 2016-12 | CT#74 | CP-160633 | 0686 | 3 | B | Provision of EPC-level identities for IMS emergency sessions over Rx | 14.2.0 | +| 2016-12 | CT#74 | CP-160625 | 0687 | 1 | B | PCC impacts due to multi-stream multiparty conferencing media handling | 14.2.0 | +| 2016-12 | CT#74 | CP-160630 | 0688 | 5 | F | Handling of pending transactions for session termination requests | 14.2.0 | +| 2016-12 | CT#74 | CP-160619 | 0690 | - | A | Correction to St session description in PCEF-initiated IP-CAN Session Modification | 14.2.0 | +| 2016-12 | CT#74 | CP-160628 | 0691 | 1 | B | Signalling for the sponsored data connectivity supported by the TDF | 14.2.0 | +| 2016-12 | CT#74 | CP-160612 | 0692 | 2 | B | Support of Multiple PRAs | 14.2.0 | +| 2016-12 | CT#74 | CP-160616 | 0693 | 1 | F | Diameter base protocol specification update | 14.2.0 | +| 2016-12 | CT#74 | CP-160627 | 0695 | - | A | Correction to information flow of PCEF-initiated IP-CAN Session Modification with AF located in HPLMN | 14.2.0 | +| 2016-12 | CT#74 | CP-160628 | 0697 | 1 | B | Add specification references of Nu, Gw, Gwn | 14.2.0 | +| 2017-03 | CT#75 | CP-170086 | 0699 | 1 | F | Bearer binding for PCC rules that have indicated to be bound to the default bearer | 14.3.0 | +| 2017-03 | CT#75 | CP-170083 | 0700 | 1 | B | QoS guidelines for MMCMH sessions | 14.3.0 | +| 2017-03 | CT#75 | CP-170081 | 0701 | 1 | C | Pre-emption control for priority sharing | 14.3.0 | +| 2017-03 | CT#75 | CP-170086 | 0702 | 1 | F | Correction in IP-CAN session termination procedure | 14.3.0 | +| 2017-03 | CT#75 | CP-170086 | 0703 | 2 | F | Correction in DRA procedures | 14.3.0 | +| 2017-06 | CT#76 | CP-171119 | 0704 | 1 | F | Reference update for draft-ietf-dime-load | 14.4.0 | +| 2017-06 | CT#76 | CP-171132 | 0707 | 2 | A | References update | 14.4.0 | +| 2017-06 | CT#76 | CP-171133 | 0714 | 2 | A | Support for signaling transport level packet marking | 14.4.0 | +| 2017-06 | CT#76 | CP-171126 | 0715 | 1 | F | Updating references to align with rel-14 MCPTT stage 1 and stage 2 restructuring | 14.4.0 | +| 2017-06 | CT#76 | CP-171117 | 0716 | 1 | F | Impacts of CUPS to PCC reference model | 14.4.0 | +| 2017-06 | CT#76 | CP-171118 | 0717 | - | F | Corrections of DRMP procedures | 14.4.0 | +| 2017-06 | CT#76 | CP-171136 | 0709 | 2 | F | Corrections in IP-CAN Session Establishment | 15.0.0 | +| 2017-06 | CT#76 | CP-171136 | 0710 | 1 | F | Update scope of 29.213 | 15.0.0 | +| 2017-06 | CT#76 | CP-171136 | 0711 | 3 | F | Clarifications on Diameter race condition | 15.0.0 | +| 2017-09 | CT#77 | CP-172038 | 0718 | 1 | B | Extension of QoS values | 15.1.0 | +| 2017-09 | CT#77 | CP-172043 | 0721 | 2 | A | Clarification of Max-Requested-Bandwidth | 15.1.0 | +| 2018-03 | CT#79 | CP-180056 | 0722 | 3 | B | Update procedures to enhance VoLTE performance | 15.2.0 | +| 2018-06 | CT#80 | CP-181023 | 0723 | - | D | Correcting heading levels | 15.3.0 | +| 2018-06 | CT#80 | CP-181171 | 0726 | 1 | A | Support priority for MCVideo services | 15.3.0 | +| 2018-09 | CT#81 | CP-182026 | 0727 | 1 | F | Correction of abbreviation "SSID" to "SSD" | 15.4.0 | +| 2018-12 | CT#82 | CP-183119 | 0735 | - | A | Removal of editor's notes | 15.5.0 | +| 2019-09 | CT#85 | CP-192154 | 0739 | 1 | A | draft-ietf-dime-load published as RFC 8583 | 15.6.0 | +| 2019-09 | CT#85 | CP-192164 | 0737 | 1 | B | Support for Restricted Local Operator Services | 16.0.0 | +| 2019-12 | CT#86 | CP-193221 | 0740 | 6 | B | Coverage and Handover Enhancements for Media (CHEM) | 16.1.0 | +| 2020-03 | CT#87e | CP-200215 | 0741 | - | B | Impacts on QoS mapping to support FLUS functionality | 16.2.0 | +| 2020-06 | CT#88e | CP-201246 | 0742 | - | B | Support of applications with specific QoS hints | 16.3.0 | +| 2021-06 | CT#92e | CP-211226 | 0743 | 1 | B | PCRF control of MPS for DTS | 17.0.0 | +| 2021-09 | CT#93e | CP-212212 | 0744 | 1 | B | 29.213 MPS for DTS note fix | 17.1.0 | +| 2022-03 | CT#95e | CP-220209 | 0745 | - | B | Update of IETF references for ICE | 17.2.0 | +| 2022-03 | CT#95e | CP-220196 | 0747 | - | F | Correction to enable retrieval of Network Provided Location information in a MESSAGE request | 17.2.0 | +| 2023-12 | CT#102 | CP-233275 | 0748 | - | B | Data channel update for Rx interface | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29214/raw.md b/marked/Rel-18/29_series/29214/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bc449086c458b1039d8b00b507e769cdf4434613 --- /dev/null +++ b/marked/Rel-18/29_series/29214/raw.md @@ -0,0 +1,3930 @@ + + +# 3GPP TS 29.214 V18.1.0 (2023-06) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control over Rx reference point (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a small red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +## --- **Keywords** + +UMTS, LTE, QoS, Charging, Policy + +--- + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles – Sophia Antipolis +Valbonne – France +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +--- + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 11 | +| 3.1 Definitions..... | 11 | +| 3.2 Abbreviations ..... | 12 | +| 4 Rx reference point..... | 13 | +| 4.1 Overview ..... | 13 | +| 4.2 Rx reference model ..... | 13 | +| 4.3 Functional elements..... | 13 | +| 4.3.1 AF ..... | 13 | +| 4.3.2 PCRF ..... | 14 | +| 4.4 PCC procedures over Rx reference point..... | 14 | +| 4.4.1 Initial Provisioning of Session Information ..... | 14 | +| 4.4.2 Modification of Session Information..... | 19 | +| 4.4.3 Gate Related Procedures..... | 22 | +| 4.4.4 AF Session Termination ..... | 23 | +| 4.4.5 Subscription to Notification of Signalling Path Status ..... | 23 | +| 4.4.5A Provisioning of AF Signalling Flow Information ..... | 24 | +| 4.4.6 Traffic Plane Events ..... | 25 | +| 4.4.6.1 IP-CAN Session Termination ..... | 25 | +| 4.4.6.2 Service Data Flow Deactivation and Resource Allocation Failure ..... | 25 | +| 4.4.6.3 Notification of Signalling Path Status ..... | 25 | +| 4.4.6.4 IP-CAN type change Notification..... | 26 | +| 4.4.6.5 Access Network Charging Information Notification ..... | 26 | +| 4.4.6.6 Reporting Usage for Sponsored Data Connectivity..... | 26 | +| 4.4.6.7 Reporting Access Network Information ..... | 27 | +| 4.4.6.8 Temporary Network Failure handling ..... | 28 | +| 4.4.6.9 PLMN information change Notification ..... | 28 | +| 4.4.7 P-CSCF Restoration Enhancement Support ..... | 28 | +| 4.4.8 Priority Sharing Request..... | 29 | +| 4.4.9 Support for media component versioning ..... | 29 | +| 4.4.10 Extended bandwidth support for EPC supporting Dual Connectivity (E-UTRAN and 5G NR) ..... | 30 | +| 4.4.11 MPS for DTS Control..... | 30 | +| 4.4.12 Provisioning of MPS for DTS AF Signalling Flow Information ..... | 31 | +| 5 Rx protocol..... | 32 | +| 5.1 Protocol support ..... | 32 | +| 5.2 Initialization, maintenance and termination of connection and session..... | 32 | +| 5.3 Rx specific AVPs ..... | 32 | +| 5.3.0 General ..... | 32 | +| 5.3.1 Abort-Cause AVP..... | 35 | +| 5.3.2 Access-Network-Charging-Address AVP..... | 36 | +| 5.3.3 Access-Network-Charging-Identifier AVP ..... | 36 | +| 5.3.4 Access-Network-Charging-Identifier-Value AVP ..... | 36 | +| 5.3.5 AF-Application-Identifier AVP..... | 36 | +| 5.3.6 AF-Charging-Identifier AVP..... | 37 | +| 5.3.7 Codec-Data AVP ..... | 37 | +| 5.3.8 Flow-Description AVP..... | 37 | +| 5.3.9 Flow-Number AVP ..... | 38 | +| 5.3.10 Flows AVP ..... | 38 | +| 5.3.11 Flow-Status AVP..... | 38 | +| 5.3.12 Flow-Usage AVP..... | 39 | +| 5.3.13 Specific-Action AVP..... | 39 | +| 5.3.14 Max-Requested-Bandwidth-DL AVP ..... | 43 | + +| | | | +|---------|-----------------------------------------------------------------------------|----| +| 5.3.15 | Max-Requested-Bandwidth-UL AVP ..... | 43 | +| 5.3.16 | Media-Component-Description AVP ..... | 43 | +| 5.3.17 | Media-Component-Number AVP ..... | 45 | +| 5.3.18 | Media-Sub-Component AVP ..... | 45 | +| 5.3.19 | Media-Type AVP ..... | 46 | +| 5.3.20 | RR-Bandwidth AVP ..... | 46 | +| 5.3.21 | RS-Bandwidth AVP ..... | 46 | +| 5.3.22 | SIP-Forking-Indication AVP ..... | 46 | +| 5.3.23 | Service-URN AVP ..... | 47 | +| 5.3.24 | Acceptable-Service-Info AVP ..... | 47 | +| 5.3.25 | Service-Info-Status-AVP ..... | 47 | +| 5.3.26 | AF-Signalling-Protocol-AVP ..... | 47 | +| 5.3.27 | Sponsored-Connectivity-Data AVP ..... | 48 | +| 5.3.28 | Sponsor-Identity AVP ..... | 48 | +| 5.3.29 | Application-Service-Provider-Identity AVP ..... | 48 | +| 5.3.30 | MPS-Identifier AVP ..... | 48 | +| 5.3.31 | Rx-Request-Type AVP ..... | 48 | +| 5.3.32 | Min-Requested-Bandwidth-DL AVP ..... | 49 | +| 5.3.33 | Min-Requested-Bandwidth-UL AVP ..... | 49 | +| 5.3.34 | Required-Access-Info AVP ..... | 49 | +| 5.3.35 | IP-Domain-Id AVP ..... | 49 | +| 5.3.36 | GCS-Identifier AVP ..... | 49 | +| 5.3.37 | Sharing-Key-DL AVP ..... | 50 | +| 5.3.38 | Sharing-Key-UL AVP ..... | 50 | +| 5.3.39 | Retry-Interval AVP ..... | 50 | +| 5.3.40 | Sponsoring-Action AVP ..... | 50 | +| 5.3.41 | Max-Supported-Bandwidth-DL AVP ..... | 50 | +| 5.3.42 | Max-Supported-Bandwidth-UL AVP ..... | 51 | +| 5.3.43 | Min-Desired-Bandwidth-DL AVP ..... | 51 | +| 5.3.44 | Min-Desired-Bandwidth-UL AVP ..... | 51 | +| 5.3.45 | MCPTT-Identifier AVP ..... | 51 | +| 5.3.45A | MCVideo-Identifier AVP ..... | 51 | +| 5.3.46 | Service-Authorization-Info AVP ..... | 51 | +| 5.3.47 | Priority-Sharing-Indicator AVP ..... | 51 | +| 5.3.48 | Media-Component-Status AVP ..... | 52 | +| 5.3.49 | Content-Version AVP ..... | 52 | +| 5.3.50 | AF-Requested-Data AVP ..... | 52 | +| 5.3.51 | Pre-emption-Control-Info AVP ..... | 52 | +| 5.3.52 | Extended-Max-Requested-BW-DL AVP ..... | 53 | +| 5.3.53 | Extended-Max-Requested-BW-UL AVP ..... | 53 | +| 5.3.54 | Extended-Max-Supported-BW-DL AVP ..... | 53 | +| 5.3.55 | Extended-Max-Supported-BW-UL AVP ..... | 53 | +| 5.3.56 | Extended-Min-Desired-BW-DL AVP ..... | 53 | +| 5.3.57 | Extended-Min-Desired-BW-UL AVP ..... | 53 | +| 5.3.58 | Extended-Min-Requested-BW-DL AVP ..... | 54 | +| 5.3.59 | Extended-Min-Requested-BW-UL AVP ..... | 54 | +| 5.3.60 | IMS-Content-Identifier AVP ..... | 54 | +| 5.3.61 | IMS-Content-Type AVP ..... | 54 | +| 5.3.62 | Callee-Information AVP ..... | 54 | +| 5.3.63 | FLUS-Identifier AVP ..... | 54 | +| 5.3.64 | Desired-Max-Latency AVP ..... | 55 | +| 5.3.65 | Desired-Max-Loss AVP ..... | 55 | +| 5.3.66 | MA-Information AVP ..... | 55 | +| 5.3.67 | MA-Information-Action AVP ..... | 55 | +| 5.3.68 | NID AVP ..... | 55 | +| 5.3.69 | 5GS-RAN-NAS-Release-Cause AVP (3GPP-5GS and Non-3GPP-5GS access type) ..... | 55 | +| 5.3.70 | 5GMM-Cause AVP ..... | 56 | +| 5.3.71 | 5GSM-Cause AVP ..... | 56 | +| 5.3.72 | NGAP-Cause AVP ..... | 56 | +| 5.3.73 | NGAP-Group AVP ..... | 56 | +| 5.3.74 | NGAP-Value AVP ..... | 56 | +| 5.3.75 | Wireline-User-Location-Info AVP ..... | 56 | + +| | | | +|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|-----------| +| 5.3.76 | HFC-Node-Identifier AVP ..... | 57 | +| 5.3.77 | GLI-Identifier AVP ..... | 57 | +| 5.3.78 | Line-Type AVP ..... | 57 | +| 5.3.79 | MPS-Action AVP ..... | 57 | +| 5.4 | Rx re-used AVPs..... | 58 | +| 5.4.0 | General ..... | 58 | +| 5.4.1 | Use of the Supported-Features AVP on the Rx reference point..... | 62 | +| 5.5 | Rx specific Experimental-Result-Code AVP values..... | 67 | +| 5.5.1 | Permanent Failures ..... | 67 | +| 5.5.2 | Transient Failures ..... | 68 | +| 5.6 | Rx messages ..... | 68 | +| 5.6.0 | General ..... | 68 | +| 5.6.1 | AA-Request (AAR) command ..... | 68 | +| 5.6.2 | AA-Answer (AAA) command ..... | 69 | +| 5.6.3 | Re-Auth-Request (RAR) command ..... | 69 | +| 5.6.4 | Re-Auth-Answer (RAA) command..... | 70 | +| 5.6.5 | Session-Termination-Request (STR) command..... | 70 | +| 5.6.6 | Session-Termination-Answer (STA) command..... | 71 | +| 5.6.7 | Abort-Session-Request (ASR) command..... | 71 | +| 5.6.8 | Abort-Session-Answer (ASA) command ..... | 72 | +| Annex A (normative): IMS Related P-CSCF Procedures over Rx..... | | 73 | +| A.1 | Provision of Service Information at P-CSCF..... | 73 | +| A.2 | Enabling of IP Flows..... | 75 | +| A.2.0 | General ..... | 75 | +| A.2.1 | Gate control procedures considering the P-Early-Media header field ..... | 75 | +| A.2.2 | Gate control procedures based on the configuration in the P-CSCF..... | 77 | +| A.3 | Support for SIP forking..... | 77 | +| A.3.0 | General ..... | 77 | +| A.3.1 | PCC rule provisioning for early media for forked responses..... | 77 | +| A.3.2 | Updating the provisioned PCC rules at the final answer ..... | 78 | +| A.4 | Notification of AF Signalling Transmission Path Status ..... | 79 | +| A.5 | Indication of Emergency Registration and Session Establishment..... | 79 | +| A.6 | Notification IP-CAN Type Change..... | 80 | +| A.7 | Support for Early Session disposition SDP..... | 80 | +| A.7.1 | General ..... | 80 | +| A.7.2 | Service Information Provisioning for Early Media..... | 80 | +| A.7.3 | Updating the Provisioned Service Information when Dialogue is established ..... | 81 | +| A.8 | Provision of Signalling Flow Information at P-CSCF ..... | 82 | +| A.9 | Handling of MPS Session ..... | 82 | +| A.10 | Retrieval of network provided location information..... | 82 | +| A.10.1 | General ..... | 82 | +| A.10.2 | Retrieval of network provided location information at originating P-CSCF for inclusion in SIP Request..... | 83 | +| A.10.3 | Retrieval of network provided location information at originating P-CSCF for inclusion in SIP response confirmation ..... | 83 | +| A.10.4 | Retrieval of network provided location information at terminating P-CSCF ..... | 84 | +| A.10.5 | Provisioning of network provided location information at SIP session release..... | 85 | +| A.10.6 | Provisioning of network provided location information at mid call ..... | 85 | +| A.11 | Handling of RAN/NAS release cause values..... | 86 | +| A.12 | Resource Sharing ..... | 86 | +| A.13 | Handling of MCPTT priority call ..... | 86 | +| A.13.1 | General ..... | 86 | +| A.13.2 | Determination of MCPTT priority parameter values..... | 87 | + +| | | +|----------------------------------------------------------------------------------------------|------------| +| A.14 Notification of PLMN Change..... | 87 | +| A.15 Handling of MCVideo priority call..... | 87 | +| A.15.1 General ..... | 87 | +| A.15.2 Determination of MCVideo priority parameter values ..... | 88 | +| A.16 Support for volume based charging of IMS services..... | 88 | +| A.17 Indication of Restricted Local Operator Services Support ..... | 89 | +| A.18 Coverage and Handoff Enhancements using Multimedia error robustness feature (CHEM)..... | 89 | +| A.19 Handling of a FLUS session ..... | 90 | +| A.20 QoS hint support for data channel media..... | 91 | +| Annex B (normative): Flow identifiers: Format definition and examples..... | 92 | +| B.1 Format of a flow identifier ..... | 92 | +| B.1.1 General ..... | 92 | +| B.1.2 Derivation of Flow Identifiers from SDP..... | 93 | +| B.1.2.1 Standard Procedure..... | 93 | +| B.1.2.2 SDP with "early session" disposition type ..... | 93 | +| B.2 Example 1 ..... | 93 | +| B.3 Example 2 ..... | 94 | +| B.4 Example 3 without media components..... | 95 | +| B.5 Example 4 ..... | 96 | +| Annex C (informative): Void..... | 98 | +| Annex D (normative): Monitoring Related SCEF Procedures over Rx..... | 99 | +| D.1 Monitoring events support, using SCEF procedures over Rx..... | 99 | +| Annex E (normative): Interworking with 5GS via Rx interface..... | 99 | +| E.1 General..... | 99 | +| E.2 Mapping table for IP-CAN types and Access types ..... | 100 | +| E.3 Reporting EPS Fallback..... | 100 | +| E.4 IP-CAN type change Notification for a MA PDU session ..... | 101 | +| E.5 Reporting serving network identity..... | 101 | +| E.6 Trusted non-3GPP Access Network Information ..... | 102 | +| E.7 Untrusted non-3GPP Access Network Information..... | 103 | +| E.8 Wireline non-3GPP Access Network Information..... | 103 | +| E.9 5GS-Level Identities report..... | 104 | +| E.10 Reporting Access Network Information ..... | 104 | +| E.11 Access Network Charging Information Notification..... | 104 | +| E.12 3GPP Access Network Information..... | 104 | +| Annex F (informative): Change history ..... | 106 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document provides the stage 3 specification of the Rx reference point for the present release. The functional requirements and the stage 2 specifications of the Rx reference point are contained in 3GPP TS 23.203 [2]. + +The Rx reference point lies between the Application Function (AF) and the Policy and Charging Rule Function (PCRF). In the 5GS the Rx reference point resides between the AF and the Policy Control Function (PCF) as specified in 3GPP TS 23.501 [55] and 3GPP TS 23.503 [56]. + +NOTE: Interactions between the PCF and the AF using the 5GS Npcf\_PolicyAuthorization service (the N5 reference point) are defined in 3GPP TS 29.514 [57]. + +The Rx interface which is based on RESTful HTTP and XML is specified in 3GPP TS 29.201 [37]. + +Whenever it is possible the present document specifies the requirements for the protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication and/or edition number or version number) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.203: "Policy and Charging Control architecture". +- [3] Void. +- [4] Void. +- [5] 3GPP TS 29.209: "Policy control over Gq interface", latest Rel-6 version. +- [6] Void. +- [7] 3GPP TS 29.211: "Rx Interface and Rx/Gx signalling flows", latest Rel-6 version. +- [8] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [9] 3GPP TS 29.213: "Policy and Charging Control signalling flows and Quality of Service (QoS) parameter mapping". +- [10] Void. +- [11] IETF RFC 3556: "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". +- [12] IETF RFC 4005: "Diameter Network Access Server Application". +- [13] IETF RFC 4566: "SDP: Session Description Protocol". +- [14] Void. + +- [15] ETSI TS 183 017 v3.2.1: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for session based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification". +- [16] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [17] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3". +- [18] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)". +- [19] Void. +- [20] IETF RFC 3162: "Radius and IPv6". +- [21] IETF RFC 5031: "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services". +- [22] Void. +- [23] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles". +- [24] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications". +- [25] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; Protocol details" +- [26] 3GPP TS 24.292: "IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3". +- [27] IETF RFC 3959 (December 2004): "The Early Session Disposition Type for the Session Initiation Protocol (SIP)". +- [28] 3GPP TS 23.380: "IMS Restoration Procedures". +- [29] Void. +- [30] Void. +- [31] 3GPP TS 22.153: "Multimedia Priority Service". +- [32] Void. +- [33] 3GPP TS 29.274: "3GPP Evolved Packet System. Evolved GPRS Tunnelling Protocol for EPS (GTPv2)". +- [34] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)". +- [35] IETF RFC 7683: "Diameter Overload Indication Conveyance". +- [36] 3GPP TS 23.468: "Group Services and System Aspects; Group Communication System Enablers for LTE (GCSE LTE)". +- [37] 3GPP TS 29.201: "Representational State Transfer (REST) reference point between Application Function (AF) and Protocol Converter (PC)". +- [38] 3GPP TS 23.003: "Numbering, addressing and identification". +- [39] 3GPP TS 29.273: "3GPP EPS AAA interfaces". +- [40] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [41] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction". + +- [42] IETF RFC 5761: "Multiplexing RTP Data and Control Packets on a Single Port". +- [43] IETF RFC 7944: "Diameter Routing Message Priority". +- [44] Void. +- [45] IETF RFC 8101: "IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk service". +- [46] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2". +- [47] 3GPP TS 29.154: "Service capability exposure functionality over Nt reference point". +- [48] IETF RFC 5009: "Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media". +- [49] IETF RFC 3948: "UDP Encapsulation of IPsec ESP Packets". +- [50] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; stage 3". +- [51] IETF RFC 8583: "Diameter Load Information Conveyance". +- [52] IETF RFC 6733: "Diameter Base Protocol". +- [53] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions". +- [54] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2". +- [55] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [56] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2". +- [57] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3". +- [58] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3". +- [59] 3GPP TS 29.513: "5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3". +- [60] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2". +- [61] 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2". +- [62] 3GPP TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification". +- [63] 3GPP TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3". +- [64] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". +- [65] 3GPP TS 22.101: "Service aspects; Service principles". +- [66] 3GPP TS 23.221: "Architectural requirements". +- [67] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [68] IETF RFC 4574: "The Session Description Protocol (SDP) Label Attribute". +- [69] 3GPP TS 26.238: "Uplink Streaming". +- [70] 3GPP TS 24.501: "Non-Access-Stratum (NAS) Protocol for 5G System (5GS); Stage 3". +- [71] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". + +- [72] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)". +- [73] CableLabs WR-TR-5WWC-ARCH: "5G Wireless Wireline Converged Core Architecture". +- [74] BBF WT-470: "5G FMC Architecture". +- [75] IETF RFC 8506: "Diameter Credit Control Application". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply: + +**Application Function (AF):** element offering application(s) that use IP bearer resources + +NOTE: One example of an AF is the P-CSCF of the IM CN subsystem. + +**AF Session:** application level session established by an application level signalling protocol offered by the AF that requires a session set-up with explicit session description before the use of the service. + +NOTE: One example of an application session is an IMS session. + +**Attribute-Value Pair (AVP):** See IETF RFC 6733 [52], corresponds to an Information Element in a Diameter message. + +**Binding:** PCRF process of associating IP flows described in AF Service Information with IP-CAN bearers. + +**Bit rate:** The number of bits (denoted in units of bits, kbits, etc.) that are conveyed or processed per unit of time. The bit rate in bit/s can be abbreviated with bps. This specification uses SI (International System of Units) prefixes as unit prefixes, which strictly refer to the power of 10, and shall not be used for the power of 2. For example, 1 kbit/s represents 1000 bit/s or 1 Mbit/s represents 1000 kbit/s and so on. + +**IP-CAN bearer:** IP transmission path of defined capacity, delay and bit error rate, etc. +See 3GPP TR 21.905 [1] for the definition of bearer. + +**IP-CAN session:** association between a UE and an IP network (for GPRS, APN). + +The association is identified by one UE Ipv4 address and/or one Ipv6 prefix together with a UE identity information, if available, and a PDN represented by a PDN ID (e.g. an APN). An IP-CAN session incorporates one or more IP-CAN bearers. Support for multiple IP-CAN bearers per IP-CAN session is IP-CAN specific. An IP-CAN session exists as long as the related UE Ipv4 address and/or Ipv6 prefix are assigned and announced to the IP network. + +**IP flow:** unidirectional flow of IP packets with the same source IP address and port number and the same destination IP address and port number and the same transport protocol +Port numbers are only applicable if used by the transport protocol. + +**MPS session:** A session for which priority treatment is applied for allocating and maintaining radio and network resources to support the Multimedia Priority Service (MPS). MPS is defined in 3GPP TS 22.153 [31]. + +**Packet flow:** A specific user data flow carried through the PCEF. A packet flow can be an IP flow. + +**PCC rule:** set of information enabling the detection of a service data flow and providing parameters for policy control and/or charging control. + +**RESTful HTTP:** is an architectural style consisting of a coordinated set of architectural constraints applied to components, connectors, and data elements, within a distributed hypermedia system applied to the development of web services. + +**Restricted local operator services:** communication services provided by an operator that involve either automated or human assistance (e.g. credit card billing, directory assistance, customer care) for which successful authentication is not necessary. + +**service information:** set of information conveyed from the AF to the PCRF over the Rx interface to be used as a basis for PCC decisions at the PCRF, including information about the AF session (e.g. application identifier, type of media, bandwidth, IP address and port number). + +**service data flow:** An aggregate set of packet flows. + +## 3.2 Abbreviations + +For the purpose of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply: + +| | | +|--------|-----------------------------------------------------------------------------| +| 5GMM | 5G Mobility Management protocol | +| 5GS | 5G System | +| 5GSM | 5G Session Management protocol | +| ADC | Application Detection and Control | +| AF | Application Function | +| AS | Application Server | +| ASP | Application Service Provider | +| ATSSS | Access Traffic Steering, Switching and Splitting | +| AVP | Attribute Value Pair | +| BBF | Broadband Forum | +| CHEM | Coverage and Handoff Enhancements using Multimedia error robustness feature | +| CRF | Charging Rules Function | +| DRMP | Diameter Routing Message Priority | +| DSCP | Differentiated Services Code Point | +| DTS | Data Transport Service | +| DSL | Digital Subscriber Line | +| FLUS | Framework for Live Uplink Streaming | +| GCS | Group Communication Service | +| GCS AS | Group Communication Service Application Server | +| HFC | Hybrid Fiber Coax | +| IP-CAN | IP Connectivity Access Network | +| MA | Multi-Access | +| MPS | Multimedia Priority Service | +| N3IWF | Non-3GPP Interworking Function | +| N5CW | Non-5G-Capable over WLAN | +| NGAP | NG Application Protocol | +| NID | Network Identifier | +| PCC | Policy and Charging Control | +| PCEF | Policy and Charging Enforcement Function | +| PCF | Policy Control Function | +| PCRF | Policy and Charging Rule Function | +| PDF | Policy Decision Function | +| P-CSCF | Proxy-Call Session Control Function | +| PON | Passive Optical Network | +| PSAP | Public Safety Answering Point | +| QoS | Quality of Service | +| RCAF | RAN Congestion Awareness Function | +| RLOS | Restricted Local Operator Services | +| SCEF | Service Capability Exposure Function | +| SCS | Service Capability Server | +| SDF | Service Data Flow | +| SMF | Session Management Function | +| SNPN | Stand-alone Non-Public Network | +| SPR | Subscriber Profile Repository | +| TDF | Traffic Detection Function | +| TNAP | Trusted Non-3GPP Access Point | +| TNGF | Trusted Non-3GPP Gateway Function | +| TWAP | Trusted WLAN Access Point | +| TWIF | Trusted WLAN Interworking Function | +| UDC | User Data Convergence | +| UE | User Equipment | + +UDR User Data Repository +XML Extensible Markup Language + +# 4 Rx reference point + +## 4.1 Overview + +The Rx reference point is used to exchange application level session information: + +- and the Application Function (AF); and +- in the 5GS, between the Policy Control Function (PCF) between + +the Policy and Charging Rules Function (PCRF) and the Application Function (AF). As defined in the stage 2 specifications (3GPP TS 23.203 [2]), this information is part of the input used by the PCRF for the Policy and Charging Control (PCC) decisions. The PCRF exchanges the PCC rules with the Policy and Charging Enforcement Function (PCEF) and QoS rules with the Bearer Binding and Event Reporting Function (BBERF) as specified in 3GPP TS 29.212 [8]. + +Policy and Charging Control over Rx interface in the 5GS is specified in annex E. + +Signalling flows related to the both Rx and Gx interfaces are specified in 3GPP TS 29.213 [9]. + +Refer to Annex G of 3GPP TS 29.213 [9] for Diameter overload control procedures over the Rx interface. + +Refer to Annex J of 3GPP TS 29.213 [9] for Diameter message priority mechanism procedures over the Rx interface. + +Refer to Annex K of 3GPP TS 29.213 [9] for Diameter load control procedures over the Rx interface. + +## 4.2 Rx reference model + +The Rx reference point is defined between the PCRF and the AF. The relationships between the different functional entities involved are depicted in figure 4.2.1. The overall PCC architecture is depicted in clause 3a of 3GPP TS 29.213 [9]. + +![Figure 4.2.1: Rx reference model diagram showing the AF and PCRF connected via the Rx interface.](ea37ab05b033e59cfdf7b074161aaf5a_img.jpg) + +The diagram shows two rectangular boxes, 'AF' on the left and 'PCRF' on the right, both filled with a light green color. A horizontal line connects the two boxes. Above this line, the label 'Rx' is centered. There is a small vertical tick mark on the line between the two boxes. + +Figure 4.2.1: Rx reference model diagram showing the AF and PCRF connected via the Rx interface. + +Figure 4.2.1: Rx reference model + +Figure 4.2.2: Void + +## 4.3 Functional elements + +### 4.3.1 AF + +The AF is an element offering applications that require the Policy and Charging Control of traffic plane resources (e.g. UMTS PS domain/GPRS domain resources). One example of an application function is the P-CSCF. The AF shall use the Rx reference point to provide session information to the PCRF. + +NOTE: The AFs may be deployed by the same operator offering the IP-CAN or may be provided by external third party service provider. + +### 4.3.2 PCRF + +The PCRF (Policy Control and Charging Rules Function) is a functional element that encompasses policy control decision and flow based charging control functionalities. These 2 functionalities are the heritage of the release 6 logical entities PDF and CRF respectively. The PCRF provides network control regarding the service data flow detection, gating, QoS and flow based charging (except credit management) towards the PCEF. The PCRF receives session and media related information from the AF and informs AF of traffic plane events. + +The PCRF may check that the service information provided by the AF is consistent with the operator defined policy rules before storing the service information. The service information shall be used to derive the QoS for the service. The PCRF may reject the request received from the AF and as a result the PCRF shall indicate, in the response to the AF, the service information that can be accepted by the PCRF. + +The PCRF may temporarily not be able to provide the service delivery that AF requested (e.g. due to RAN user plane congestion). In this case, the PCRF may send a re-try interval information to the AF. The re-try interval indicates when service delivery may be retried by the AF over Rx. + +NOTE 1: Additionally, existing bandwidth limitation parameters (e.g. Max-Requested-Bandwidth-DL AVP, Max-Requested-Bandwidth-UL AVP within the Acceptable-Service-Info AVP) provided by the PCRF to the AF in AA-Answer command during the Rx session establishment are available in order to mitigate RAN user plane congestion. + +The PCRF may use the subscription information as basis for the policy and charging control decisions. The subscription information may apply for both session based and non-session based services. The subscription specific information for each service may contain e.g. max QoS class and max bit rate. + +If the AF requests it, the PCRF shall report IP-CAN session events (including bearer events and events on AF signalling transport) to the AF via the Rx reference point. + +The PCRF PCC/QoS Rule decisions may be based on one or more of the following: + +- the session and media related information obtained from the AF via the Rx reference point; +- the bearer and subscriber related information obtained from the PCEF over the Gx reference point; +- the bearer and subscriber related information obtained from the BBERF over the Gxx reference point; +- subscriber and service related data the PCRF may be aware of by configuration or through the Sp reference point; +- pre-configured information in the PCRF. + +NOTE 2: The details associated with the Sp reference point are not specified in this Release. The SPR's relation to existing subscriber databases is not specified in this Release. + +The PCRF shall provision PCC/QoS Rules to the PCEF/BBERF via the Gx/Gxx reference point. + +## 4.4 PCC procedures over Rx reference point + +### 4.4.1 Initial Provisioning of Session Information + +When a new AF session is being established and media information for this AF session is available at the AF and the related media require PCC supervision, the AF shall open an Rx Diameter session with the PCRF for the AF session using an AA-Request command, unless an Rx session has already been established for the AF session (e.g. as per clause 4.4.6.7). If an Rx Diameter session already exists for the AF session, the AF uses the existing Rx Diameter session. The AF shall provide the full IP address of the UE using either Framed-IP-Address AVP or Framed-Ipv6-Prefix AVP, and the corresponding Service Information within Media-Component-Description AVP(s). The AF shall not include circuit-switched bearer related media in the service information sent to the PCRF. The AF shall indicate to the PCRF as part of the Media-Component-Description whether the media IP flow(s) should be enabled or disabled with the Flow-Status AVP. + +NOTE 1: The AF does not need to open an Rx Diameter session with the PCRF, if the SDP payload is only proposing to use a circuit-switched bearer (i.e. "c=" line set to "PSTN" and an "m=" line set to "PSTN", refer to 3GPP TS 24.292 [26]). + +NOTE 2: The Rx Diameter session used for an AF session is different from the Rx Diameter session possibly used for the notifications of the status of the AF signalling transmission path. A new Rx Diameter session is established for each new AF session. + +The AF may include the AF-Application-Identifier AVP into the AA-Request in order to indicate the particular service that the AF session belongs to. This AVP can be provided at both AF session level, and Media-Component-Description level. When provided at both levels, the AF-Application Identifier provided within the Media-Component-Description AVP will have precedence. The AF may also include an AF application identifier within the AF-Application-Identifier AVP at the AF session level to trigger the PCRF to indicate to the PCEF/TDF to perform the application detection based on the operator's policy as defined in 3GPP TS 29.212 [8]. + +The AF may include the AF-Charging-Identifier AVP into the AA-Request for charging correlation purposes. The AF may also include the Specific-Action AVP to request notification for certain user plane events, e.g. bearer termination. + +The AF may include the Service-URN AVP in order to indicate that the new AF session relates to emergency or RLOS traffic and additionally it may include the AF-Requested-Data AVP to indicate the information required by the AF. If the PCRF receives the Service-URN AVP indicating an emergency session, the PCRF may apply special policies, for instance prioritising service flows relating to the new AF session or allowing these service flows free of charge. If the Service-URN AVP indicates that the new AF session relates to emergency traffic and the AF-Requested-Data AVP is received, the PCRF shall provide the requested available user information as part of the AA-Answer command. + +The AF may include the MPS-Identifier AVP in order to indicate that the new AF session relates to an MPS session. If the PCRF receives the MPS-Identifier AVP indicating an MPS session, the PCRF may take specific actions on the corresponding IP-CAN to ensure that the MPS session is prioritized as specified in 3GPP TS 29.212 [8]. For Multimedia Priority Service handling for IMS, see Annex A.9. + +The AF may include the MCPTT-Identifier AVP in order to indicate that the new AF session relates to an MCPTT session with priority call. If the PCRF receives the MCPTT-Identifier AVP related to that MCPTT session, the PCRF may take specific actions on the corresponding IP-CAN to ensure that the MCPTT session is prioritized. For the handling of MCPTT session with priority call, see Annex A.13. + +The AF may include the MCVideo-Identifier AVP in order to indicate that the new AF session relates to an MCVideo session with priority call. If the PCRF receives the MCVideo-Identifier AVP related to that MCVideo session, the PCRF may take specific actions on the corresponding IP-CAN to ensure that the MCVideo session is prioritized. For the handling of MCVideo session with priority call, see Annex A.15. + +If the QoSHint feature is supported by the AF, the AF may include the Desired-Max-Latency AVP and/or Desired-Max-Loss AVP within the Media-Component-Description AVP to indicate to the PCRF that the related application media has specific latency and/or loss demands. + +The AF may include the FLUS-Identifier AVP within the Media-Component-Description AVP in order to indicate to the PCRF that the media flow(s) correspond to a FLUS media stream. Additional QoS information for the treatment of FLUS media may be provided within Desired-Max-Latency AVP and/or Desired-Max-Loss AVP. + +The AF may include the Priority-Sharing-Indicator AVP set to PRIORITY\_SHARING\_ENABLED within the Media-Component-Description AVP in order to indicate to the PCRF that the related media flow is allowed to use the same Allocation and Retention Priority (ARP) as media flows belonging to other AF sessions as described in clause 4.4.8. In this case, if the MCPTT-Preemption is supported, the AF may also include the Pre-emption-Capability AVP containing the suggested pre-emption capability value and the Pre-emption-Vulnerability AVP containing the suggested pre-emption vulnerability value within the Media-Component-Description AVP for the PCRF to determine the ARP values. The AF may also include the Pre-emption-Control-Info AVP containing the pre-emption control information at the AAR command level for the PCRF to perform the pre-emption control as defined in clause 4.5.27 or 4a.5.17 of 3GPP TS 29.212 [8]. + +The AF may include the Sharing-Key-UL and/or Sharing-Key-DL AVP within the Media-Component-Description AVP in order to indicate that the related media of the new AF session may share resources with other media components in the related direction that include the same value for the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP. + +When the AF is a GCS AS, it may include the GCS-Identifier AVP at command level and Reservation-Priority AVP at command level or media component level in order to indicate that the new AF session relates to a prioritized Group + +Communication session. Based on this information, the PCRF may take specific actions on the corresponding IP-CAN to ensure that the Group Communication session is prioritized as specified in 3GPP TS 29.212 [8]. + +If the AF provides service information that has been fully negotiated (e.g. based on the SDP answer), the AF may include the Service-Info-Status AVP set to FINAL\_SERVICE\_INFORMATION. In this case the PCRF shall authorize the session and provision the corresponding PCC/QoS rules to the PCEF/BBERF. + +The AF may additionally provide preliminary service information not fully negotiated yet (e.g. based on the SDP offer) at an earlier stage. To do so, the AF shall include the Service-Info-Status AVP with the value set to PRELIMINARY SERVICE INFORMATION. Upon receipt of such preliminary service information, the PCRF shall perform an early authorization check of the service information. For GPRS, the PCRF shall not provision PCC rules towards the PCEF unsolicitedly. However, the PCRF may authorize a PCC/QoS rule request received from the PCEF/BBERF as per 3GPP TS 29.212 [8]. Further, if the AF requests the PCRF to report the access network information together with preliminary service information, the PCRF shall immediately configure the PCEF (or BBERF) to provide the access network information. + +For sponsored data connectivity and if SponsoredConnectivity is supported, the AF shall provide the application service provider identity and the sponsor identity to the PCRF by including the Application-Service-Provider-Identity AVP and the Sponsor-Identity AVP in the Sponsored-Connectivity-Data AVP in the AA-Request. Additionally if SponsorChange is supported the AF shall provide an indication whether to enable or not enable sponsored data connectivity to the PCRF by including the Sponsoring-Action AVP set to the applicable value. + +NOTE 3: The relationship between the AF and Sponsor is out of scope of this specification. A single AF can serve multiple ASPs and multiple sponsors, An ASP can also be a sponsor. + +To support the usage monitoring of sponsored data connectivity, the AF may also include the Granted-Service-Unit AVP in the Sponsored-Connectivity-Data AVP and the Specific-Action AVP set to the value USAGE\_REPORT in the AA-Request to request notification when the usage threshold has been reached. + +NOTE 4: If the AF is in the user plane, the AF can handle the usage monitoring and therefore it is not required to provide a usage threshold to the PCRF as part of the sponsored data connectivity information. + +When SponsoredConnectivity is supported or when SponsorChange is supported and the AF indicated to enable sponsored data connectivity, the following procedures apply: + +- If the UE is roaming with the visited access case and the AF is located in the HPLMN or roaming with the home routed case and operator policies do not allow accessing the sponsored data connectivity with this roaming case, the H-PCRF shall reject the service request indicating UNAUTHORIZED\_SPONSORED\_DATA\_CONNECTIVITY to the AF. +- If the UE is roaming with the visited access case and the AF is located in the VPLMN, the V-PCRF shall reject the service request indicating UNAUTHORIZED\_SPONSORED\_DATA\_CONNECTIVITY to the AF. + +When SponsoredConnectivity is supported or when SponsorChange is supported and the AF indicated to enable sponsored data connectivity, if the UE is in the non-roaming case or roaming with the home routed case and the operator policies allow accessing the sponsored data connectivity with this roaming case, the following procedures apply: + +- If the PCEF/TDF does not support sponsored connectivity and the required reporting level for that service indicates a sponsored connectivity level according to 3GPP TS 29.212 [8], then the PCRF shall reject the request indicating REQUESTED\_SERVICE\_NOT\_AUTHORIZED. +- If the PCEF/TDF supports sponsored data connectivity feature or the required reporting level is different from sponsored connectivity level as described in 3GPP TS 29.212 [8], then the PCRF, based on operator policies, shall check whether it is required to validate the sponsored connectivity data. If it is required, it shall perform the authorizations based on sponsored data connectivity profiles. If the authorization fails, the PCRF responds to the AF with an AA-Answer including the Experimental-Result-Code AVP set to the value UNAUTHORIZED\_SPONSORED\_DATA\_CONNECTIVITY. The profile may include a list of Application Service Providers and their applications per sponsor. + +NOTE 5: If the AF is in the operator's network and is based on the OSA/Parlay-X GW, the PCRF is not required to verify that a trust relationship exists between the operator and the sponsors. + +When CHEM feature is supported, the AF includes the Max-PLR-DL AVP and/or Max-PLR-UL AVP within the Media-Component-Description AVP, to indicate the downlink maximum packet loss rate and/or uplink maximum packet loss rate for each payload type. For CHEM feature, see Annex A.18. + +When the PCRF receives an initial AA-Request from the AF, the PCRF shall perform session binding as described in 3GPP TS 29.213 [9]. To allow the PCRF to identify the IP-CAN session for which this request applies, the AF shall provide either the Framed-IP-Address or the Framed-Ipv6-Prefix containing the full IP address applicable to an IP flow or IP flows towards the UE. In case of private IP address being used, the AF may provide PDN information if available in the Called-Station-Id AVP for session binding. The AF may provide the domain identity in the IP-Domain-Id AVP for session binding. + +NOTE 6: The IP-Domain-Id AVP is helpful in the following scenario: Within a PLMN, there are several separate IP address domains, with PCEF(s) that allocate Ipv4 IP addresses out of the same private address range to UEs. The same IP address can thus be allocated to UEs served by PCEFs in different address domains. If one PCRF controls several PCEFs in different IP address domains, the UE IP address is thus not sufficient for the session binding. An AF can serve UEs in different IP address domains, either by having direct IP interfaces to those domains, or by having interconnections via NATs in the user plane between PCEFs and the AF. If a NAT is used, the AF obtains the IP address allocated to the UE via application level signalling and supplies it for the session binding as Framed-IP-Address to the PCRF. The AF supplies an IP-Domain-Id value denoting the IP address domain behind the NAT in addition. The AF can derive the appropriate value from the source address (allocated by the NAT) of incoming user plane packets. The value provided in the IP-Domain-Id AVP is operator configurable. + +NOTE 7: When the scenario described in NOTE 6 applies and the AF is a P-CSCF it is assumed that the P-CSCF has direct IP interfaces to the different IP address domains and that no NAT is located between P-GW and P-CSCF. How a non-IMS AF obtains the UE private IP address to be provided to the PCRF is out of scope of the present release; it is unspecified how to support applications that use a protocol that does not retain the original UE's private IP address. + +If the PCRF fails in executing session binding, the PCRF responds to the AF with an AA-Answer including the Experimental-Result-Code AVP set to the value IP-CAN\_SESSION\_NOT\_AVAILABLE. Further details on how the PCRF identifies suitable IP-CAN sessions can be found in the binding mechanism described in 3GPP TS 29.213 [9]. + +If the request contains Media-Component-Description Attribute-Value Pair(s) (AVP(s)) the PCRF shall store the received Service Information. The PCRF shall process the received Service Information according to the operator policy and may decide whether the request is accepted or not. The PCRF may take the priority information within the Reservation-Priority AVP into account when making this decision. + +For an IP-CAN session associated to a dedicated APN for the purpose of offering services to remote UEs via a ProSe UE-to-network relay UE, as defined in 3GPP TS 23.303 [46], the PCRF shall validate the service information based on the service/roaming agreement and the operator policies related to that PDN information. + +NOTE 8: The PCRF is not required to be aware of the remote UE. + +If the service information provided in the AA-Request command is rejected (e.g. the subscribed guaranteed bandwidth for a particular user is exceeded), the PCRF shall indicate in the AA-Answer command the cause for the rejection with the Experimental-Result-Code AVP set to the value REQUESTED\_SERVICE\_NOT\_AUTHORIZED. If the service information provided in the AA-Request command is rejected by the PCRF due to a temporary condition in the network (e.g. the user plane in the cell the user is located is congested), the PCRF may indicate in the AA-Answer the cause for the rejection with the Experimental-Result-Code AVP set to the value REQUESTED\_SERVICE\_TEMPORARILY\_NOT\_AUTHORIZED (4261). The PCRF may also provide a retry-interval within the Retry-Interval AVP in the AA-Answer command to the AF. When the AF receives the re-try interval within the Retry-Interval AVP, the AF shall not send the same service information to the PCRF again (for the same IP-CAN session) until the re-try interval has elapsed. The PCRF may additionally provide the acceptable bandwidth within the Acceptable-Service-Info AVP in AA-Answer command. + +NOTE 9: How the PCRF derives the re-try interval is up to implementation. + +To allow the PCRF and PCEF to perform PCC rule authorization and bearer binding for the described service IP flows, the AF shall supply both source and destination IP addresses and port numbers within the Flow-Description AVP, if such information is available. + +NOTE 10: In SDP source port information is usually not available. + +The AF may specify the ToS-Traffic-Class AVP for the described service data flows together with the Flow-Description AVP. + +NOTE 11: The ToS-Traffic-Class AVP can be useful when another packet filter attribute is needed to differentiate between flows. For example, (when EPS bearers are used for group communication services) flows encapsulated and encrypted by a tunneling protocol and thus having their IP five-tuple attributes obscured can be differentiated by the Type of Service (or Traffic Class) value of the outer header. + +NOTE 12: The use of ToS-Traffic-Class AVP by the AF assumes that no DSCP re-marking is applied from the application to the PGW. + +The AF may specify the Reservation-Priority AVP at request level in the AA-Request in order to assign a priority to the AF Session as well as specify the Reservation-Priority AVP at the media-component-description AVP level to assign a priority to the IP flow. The presence of the Reservation-Priority in both levels does not constitute a conflict as they each represent different types of priority. Specifically the Reservation-Priority at the AA-Request level provides the relative priority for a session while the Reservation-Priority at the media-component-description level provides the relative priority for an IP flow within a session. If the Reservation-Priority AVP is not specified the requested priority is DEFAULT (0). + +The AF may request notifications of specific IP-CAN session events through the usage of the Specific-Action AVP in the AA-Request command. The PCRF shall make sure to inform the AF of the requested notifications in the event that they take place. + +The AF may include the Rx-Request-Type AVP set to INITIAL\_REQUEST in the AAR. + +The AF may include a Reference Id within the Reference-Id AVP related to a transfer policy negotiated for background data transfer via the Nt reference point as described in 3GPP TS 29.154 [47]. The PCRF shall retrieve the corresponding transfer policy from the SPR based on the Reference Id. If the PCRF can not retrieve the transfer policy, the PCRF shall include in the AA-Answer the Service-Authorization-Info AVP with the bit 0 set to indicate that the transfer policy is unknown. If the time window of the received transfer policy has expired, the PCRF shall include in the AA-Answer the Service-Authorization-Info AVP with the bit 1 set to indicate that the transfer policy has expired. Otherwise, if the time window of the received transfer policy has not yet occurred, the PCRF shall include in the AA-Answer the Service-Authorization-Info AVP with the bit 2 set to indicate that the time window of the transfer policy has not yet occurred. + +NOTE 13: In the case that the PCRF can not retrieve the transfer policy or the transfer policy expired, the PCRF makes the decision without considering the transfer policy. + +NOTE 14: When receiving the reference id from the 3rd party SCS/AS as described in 3GPP TS 23.682 [40], the SCEF (acting as an AF) can provide the reference id together with the sponsored data connectivity information if SponsorChange is supported as described in this clause. + +The AF may include the IMS-Content-Type AVP into the AA-Request in order to indicate the type of IMS communication service (e.g. CAT service, 3PTY conference) the AF session refers to. + +The AF may include the IMS-Content-Identifier AVP into the AA-Request in order to indicate the particular IMS communication service or communication dialogue that the AF session refers to. + +The AF may include the Calling-Party-Address AVP and the Callee-Information AVP into the AA-Request in order to indicate the caller and the callee information that the AF session refers to. + +The PCRF shall check whether the received Service Information requires PCC/QoS Rules to be created and provisioned and/or authorized QoS to be provisioned as specified in 3GPP TS 29.213 [9]. Provisioning of PCC/QoS Rules and Authorized QoS to the PCEF/BBRF shall be carried out as specified at 3GPP TS 29.212 [8]. + +If the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP are provided within the Media-Component-Description AVP, the PCRF may apply the mechanisms for resource sharing as specified at 3GPP TS 29.212 [8]. + +The PCRF shall reply with an AA-Answer to the AF. The acknowledgement towards the AF should take place before or in parallel with any required PCC Rule provisioning towards the PCEF and shall include the Access-Network-Charging-Identifier(s) and may include the Access-Network-Charging-Address AVP, if they are available. The AA- + +Answer message shall also include the AN-GW-Address AVP, if the PCRF has previously requested to be updated with this information in the PCEF. The AA-Answer message shall also include the PLMN identifier within the 3GPP-SGSN-MCC-MNC AVP if the PCRF has previously requested to be updated with this information in the PCEF/BBERF. The AA-Answer message shall also include the IP-CAN-Type AVP, if the PCRF has previously requested to be updated with this information in the PCEF/BBERF. In that case, the AA-Answer message shall also include the RAT type information within the RAT-Type AVP and AN-Trusted AVP when applicable for the specific IP-CAN Type. In addition, if IP flow mobility applies to service data flows as specified in 3GPP TS 29.212 [8], such that a subset of the flows within the AF session are affected, the PCRF shall also include IP-CAN-type and RAT type information (if applicable) to IP flow mobility related flows, if such information is available. The IP flow mobility affected service data flows are included within the Flows AVP at command level. If the PCRF needs to terminate the Rx session before it has sent the AA Answer, the PCRF shall send the AA Answer immediately and before the AS Request. + +The behaviour when the AF does not receive the AA Answer, or when it arrives after the internal timer waiting for it has expired, or when it arrives with an indication different than DIAMETER\_SUCCESS, are outside the scope of this specification and based on operator policy. + +If the PCRF fails in installing PCC/QoS rules based on the provided service information due to resource allocation failure as specified in 3GPP TS 29.212 [8] and if requested by the AF, the PCRF shall send an RAR command to the AF with the Specific-Action AVP set to the value INDICATION\_OF\_FAILED\_RESOURCES\_ALLOCATION to report the resource allocation failure, the Flows AVP containing the service data flows corresponding to the resources that could not be allocated, and the content version within the Content-Version AVP if it was included when the corresponding media component was provisioned. The AF shall send an RAA command to acknowledge the RAR command. + +### 4.4.2 Modification of Session Information + +The AF may modify the session information at any time (e.g. due to an AF session modification or internal AF trigger) by sending an AA-Request command to the PCRF containing the Media-Component-Description AVP(s) with the updated Service Information. The AF shall send an AA-Request command to the PCRF, only after the previous AA-Request has been acknowledged. + +If the AF provides service information that has been fully negotiated (e.g. based on the SDP answer), the AF may include the Service-Info-Status AVP set to FINAL\_SERVICE\_INFORMATION. In this case the PCRF shall authorize the session and provision the corresponding PCC rules to the PCEF. + +The AF may additionally provide preliminary service information not fully negotiated yet (e.g. based on the SDP offer) at an earlier stage. To do so, the AF shall include the Service-Info-Status AVP with the value set to PRELIMINARY SERVICE INFORMATION. Upon receipt of such preliminary service information, the PCRF shall perform an early authorization check of the service information. For GPRS, the PCRF shall not provision PCC rules towards the PCEF unsolicitedly. However, the PCRF may authorize a PCC/QoS rule request received from the PCEF/BBERF as per 3GPP TS 29.212 [8]. Further, if the AF requests the PCRF to report the access network information together with preliminary service information, the PCRF shall immediately configure the PCEF (or BBERF) to provide the access network information. + +The AF may include the Rx-Request-Type AVP set to UPDATE\_REQUEST in the AAR. + +The AF may include a Reference Id within the Reference-Id AVP related to a transfer policy negotiated for background data transfer via the Nt reference point as described in 3GPP TS 29.154 [47]. The AF shall retrieve the corresponding transfer policy from the SPR based on the Reference Id. If the PCRF can not retrieve the transfer policy, the PCRF shall include in the AA-Answer the Service-Authorization-Info AVP with the bit 0 set to indicate that the transfer policy is unknown. If the time window of the received transfer policy has expired, the PCRF shall include in the AA-Answer the Service-Authorization-Info AVP with the bit 1 set to indicate that the transfer policy has expired. Otherwise, if the time window of the received transfer policy has not yet occurred, the PCRF shall include in the AA-Answer the Service-Authorization-Info AVP with the bit 2 set to indicate that the time window of the transfer policy has not yet occurred. + +NOTE 1: In the case that the PCRF can not retrieve the transfer policy or the transfer policy expired, the PCRF makes the decision without considering the transfer policy. + +NOTE 2: When receiving the reference id from the 3rd party SCS/AS as described in 3GPP TS 23.682 [40], the SCEF (acting as an AF) can provide the reference id together with the sponsored data connectivity information if SponsorChange is supported as described in this clause. + +The AF may include the MPS-Identifier AVP in order to indicate that the modified AF session relates to an MPS session. If the PCRF receives the MPS-Identifier AVP, it may take specific actions on the corresponding IP-CAN to ensure that the MPS session is prioritized as defined in 3GPP TS 29.212 [8]. For Multimedia Priority Service handling for IMS, see Annex A.9. + +The AF may include the MCPTT-Identifier AVP in order to indicate that the modified AF session relates to the priority adjustment of an MCPTT session. If the PCRF receives the MCPTT-Identifier AVP related to that MCPTT session, the PCRF may take specific actions on the corresponding IP-CAN to ensure that the MCPTT session is prioritized. For the handling of MCPTT session with priority call, see Annex A.13. + +The AF may include the MCVideo-Identifier AVP in order to indicate that the modified AF session relates to the priority adjustment of an MCVideo session. If the PCRF receives the MCVideo-Identifier AVP related to that MCVideo session, the PCRF may take specific actions on the corresponding IP-CAN to ensure that the MCVideo session is prioritized. For the handling of MCVideo session with priority call, see Annex A.15. + +If the QoSHint feature is supported by the AF, the AF may include the Desired-Max-Latency AVP and/or Desired-Max-Loss AVP within the Media-Component-Description AVP to indicate to the PCRF that the related application media has specific latency and/or loss demands. + +The AF may include the FLUS-Identifier AVP within the Media-Component-Description AVP in order to indicate to the PCRF that the media flow(s) correspond to a FLUS media stream. Additional QoS information for the treatment of FLUS media may be provided within Desired-Max-Latency AVP and/or Desired-Max-Loss AVP. + +The AF may include the Priority-Sharing-Indicator AVP set to PRIORITY\_SHARING\_ENABLED within the Media-Component-Description AVP in order to indicate to the PCRF that the related media flow is allowed to use the same Allocation and Retention Priority (ARP) as media flows belonging to other AF sessions as described in clause 4.4.8. In this case, if the MCPTT-Preemption is supported, the AF may also include the Pre-emption-Capability AVP containing the suggested pre-emption capability value and the Pre-emption-Vulnerability AVP containing the suggested pre-emption vulnerability value within the Media-Component-Description AVP for the PCRF to determine the ARP values. The AF may also include the Pre-emption-Control-Info AVP containing the pre-emption control information at the AAR command level for the PCRF to perform the pre-emption control as defined in clause 4.5.27 or 4a.5.17 of 3GPP TS 29.212 [8]. + +The AF may include the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP within the Media-Component-Description AVP in order to indicate that the related media of the modified AF session may share resources with other media components in the related direction that include the same Sharing-Key-UL and or Sharing-Key-DL AVP. The AF may modify the conditions for resource sharing by including a new value of the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP for that media component. + +When the AF is a GCS AS, it may include the GCS-Identifier AVP at command level and Reservation-Priority AVP at command level or media component level in order to modify the priority of an AF session that relates to a prioritized Group Communication session. Based on this information, the PCRF may take specific actions on the corresponding IP-CAN to ensure that the Group Communication session is prioritized as specified in 3GPP TS 29.212 [8]. + +For sponsored data connectivity and if SponsoredConnectivity is supported, the AF shall provide the application service provider identity and the sponsor identity to the PCRF by including Application-Service-Provider-Identity AVP and the Sponsor-Identity AVP in the Sponsored-Connectivity-Data AVP in the AA-Request. + +If SponsorChange is supported and the AF requests to enable sponsored data connectivity the AF shall provide the application service provider identity, the sponsor identity and an indication to enable sponsored data connectivity to the PCRF by including Application-Service-Provider-Identity AVP, the Sponsor-Identity AVP and the Sponsoring-Action AVP set to the value ENABLE\_SPONSORING (1) in the Sponsored-Connectivity-Data AVP in the AA-Request. + +If the AF requests to disable sponsored data connectivity the AF shall provide an indication to disable sponsored data connectivity to the PCRF by including the Sponsoring-Action AVP set to the value DISABLE\_SPONSORING (0) in the Sponsored-Connectivity-Data AVP in the AA-Request. + +To support the usage monitoring of sponsored data connectivity, the AF may also include the Granted-Service-Unit AVP in the Sponsored-Connectivity-Data AVP in the AA-Request. + +NOTE 3: If the AF is in the user plane, the AF can handle the usage monitoring and therefore it is not required to provide a usage threshold to the PCRF as part of the sponsored data connectivity information. + +When sponsored data connectivity is requested to be enabled the following procedures apply: + +- If the UE is roaming with the visited access case and the AF is located in the HPLMN or roaming with the home routed case and operator policies do not allow accessing the sponsored data connectivity with this roaming case, the H-PCRF shall reject the service request indicating UNAUTHORIZED\_SPONSORED\_DATA\_CONNECTIVITY to the AF. +- If the UE is roaming with the visited access case and the AF is located in the VPLMN, the V-PCRF shall reject the service request indicating UNAUTHORIZED\_SPONSORED\_DATA\_CONNECTIVITY to the AF. + +When sponsored data connectivity is requested to be enabled, if the UE is in the non-roaming case or roaming with the home routed case and the operator policies allow accessing the sponsored data connectivity with this roaming case, the following procedures apply: + +- If the PCEF/TDF does not support sponsored connectivity and the required reporting level for that service indicates a sponsored connectivity level according to 3GPP TS 29.212 [8], then the PCRF shall reject the request indicating REQUESTED\_SERVICE\_NOT\_AUTHORIZED. +- If the PCEF/TDF supports sponsored data connectivity feature or the required reporting level is different from sponsored connectivity level as described in 3GPP TS 29.212 [8], then the PCRF, based on operator policies, shall check whether it is required to validate the sponsored connectivity data. If it is required, it shall perform the authorizations based on sponsored data connectivity profiles. If the authorization fails, the PCRF responds to the AF with an AA-Answer including the Experimental-Result-Code AVP set to the value UNAUTHORIZED\_SPONSORED\_DATA\_CONNECTIVITY. The profile may include a list of Application Service Providers and their applications per sponsor. + +NOTE 4: If the AF is in the operator's network and is based on the OSA/Parlay-X GW, the PCRF is not required to verify that a trust relationship exists between the operator and the sponsors. + +When CHEM feature is supported, the AF includes the Max-PLR-DL AVP and/or Max-PLR-UL AVP within the Media-Component-Description AVP, to indicate the downlink maximum packet loss rate and/or uplink maximum packet loss rate for each payload type. For CHEM feature, see Annex A.18. + +The AF may include an AF application identifier within the AF-Application-Identifier AVP at the session level to trigger the PCRF to indicate to the PCEF/TDF to perform the application detection based on the operator's policy as defined in 3GPP TS 29.212 [8]. + +The AF may include the IMS-Content-Type AVP into the AA-Request in order to indicate the type of IMS communication service (e.g. CAT service, 3PTY conference) the AF session refers to. + +The AF may include the IMS-Content-Identifier AVP into the AA-Request in order to indicate the particular IMS communication service or communication dialogue that the AF session refers to. + +The AF may include the Callee-Information AVP into the AA-Request in order to indicate the callee information that the AF session refers to. + +The PCRF shall process the received Service Information according the operator policy and may decide whether the request is accepted or not. If the updated Service Information is not acceptable (e.g. subscribed guaranteed bandwidth for a particular user is exceeded), the PCRF shall indicate in the AA-Answer command the cause for the rejection with the Experimental-Result-Code AVP set to the value REQUESTED\_SERVICE\_NOT\_AUTHORIZED. If the service information provided in the AA-Request command is rejected by the PCRF due to a temporary condition in the network (e.g. the user plane in the cell the user is located is congested), the PCRF may indicate in the AA-Answer the cause for the rejection with the Experimental-Result-Code AVP set to the value REQUESTED\_SERVICE\_TEMPORARILY\_NOT\_AUTHORIZED (4261). The PCRF may also provide a retry-interval within the Retry-Interval AVP in the AA-Answer command to the AF. When the AF receives the re-try interval within the Retry-Interval AVP, the AF shall not send the same service information to the PCRF again (for the same IP-CAN session) until the re-try interval has elapsed. The PCRF may additionally provide the acceptable bandwidth within the Acceptable-Service-Info AVP in the AA-Answer command. + +NOTE 5: How the PCRF derives the re-try interval is up to implementation. + +If accepted, the PCRF shall update the Service Information with the new information received. Due to the updated Service Information, the PCRF may need to create, modify or delete the related PCC rules as specified in 3GPP TS 29.213 [9] and provide the updated information towards the PCEF following the corresponding procedures + +specified at 3GPP TS 29.212 [8]. The procedures to update the Authorized QoS for the affected IP-CAN bearer are also specified at 3GPP TS 29.212 [8]. + +If the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP are provided within the Media-Component-Description AVP, the PCRF may apply the mechanisms for resource sharing as specified at 3GPP TS 29.212 [8]. + +The PCRF shall reply with an AA-Answer to the AF. The acknowledgement towards the AF should take place before or in parallel with any required PCC Rule provisioning towards the PCEF and shall include the Access-Network-Charging-Identifier(s) and may include the Access-Network-Charging-Address AVP, if they are available at this moment and have not been yet supplied earlier to the AF. The AA-Answer message shall include the AN-GW-Address AVP if the PCRF has previously requested to be updated with this information in the PCEF. The AA-Answer message shall also include the PLMN identifier within the 3GPP-SGSN-MCC-MNC AVP if the PCRF has previously requested to be updated with this information in the PCEF/BBERF. The AA-Answer message shall also include the IP-CAN-Type AVP if the PCRF has previously requested to be updated with this information in the PCEF/BBERF. In that case, the AA-Answer message shall also include the RAT type information within the RAT-Type AVP and AN-Trusted AVP when applicable for the specific IP-CAN Type. In addition, if IP flow mobility applies to service data flows as specified in 3GPP TS 29.212 [8], such that a subset of the flows within the AF session are affected, the PCRF shall also include IP-CAN-type and RAT type information (if applicable) to IP flow mobility related flows, if the PCRF has previously requested to be updated with this information in the PCEF. The IP flow mobility affected service data flows are included within the Flows AVP at command level. If the PCRF needs to terminate the Rx session before it has sent the AA Answer, the PCRF shall send the AA Answer immediately and before the AS Request. If the PCRF does not have an existing session for the Rx session being modified (such as after a PCRF failure), the PCRF may reject the request with an AA-Answer with the result code set to DIAMETER\_UNKNOWN\_SESSION\_ID. + +If the PCRF installs PCC/QoS rules or modifies existing PCC/QoS rules based on the updated service information and the installation or modification fails due to resource allocation failure as specified in 3GPP TS 29.212 [8] and if requested by the AF, the PCRF shall send an RAR command to the AF with the Specific-Action AVP set to the value INDICATION\_OF\_FAILED\_RESOURCES\_ALLOCATION to report the modification failure, the Flows AVP containing the service data flows corresponding to the resources that could not be allocated, and the content version(s) within the Content-Version AVP(s) if it was included when the corresponding media component was provisioned. If the modification of the existing PCC/QoS rules fails, the PCRF may also provide the status of the service information within the Media-Component-Status AVP. The AF shall send an RAA command to acknowledge the RAR command. + +NOTE 6: The PCRF will report the Media-Component-Status AVP according to the status reported for the related PCC/QoS rules when the modification fails over the Gx/Gxx reference points as described in 3GPP TS 29.212 [8]. + +### 4.4.3 Gate Related Procedures + +Depending on the application, in the Service Information provision, the AF may instruct the PCRF when the IP flow(s) are to be enabled or disabled to pass through the IP-CAN. The AF does this by sending the AA-Request message containing the Media-Component- Description AVP(s) that contains the flow status information (in the Flow-Status AVP) for the flows to be enabled or disabled. + +In response to this action the PCRF shall set the appropriate gate status for the corresponding active PCC rule(s). + +If a Media-Sub-Component AVP under a Media-Component-Description AVP contains a Flow-Usage AVP with the value RTCP, then the corresponding RTCP IP Flows in both directions shall be enabled even if the Flow-Status AVP under the Media-Sub-Component AVP is set to ENABLED-UPLINK, ENABLED-DOWNLINK, ENABLED, or DISABLED. + +The PCRF shall reply with an AA-Answer and shall include the Access-Network-Charging-Identifier(s) available at this moment. The PCRF forwards the AF decision to enable or disable the authorized IP flows. + +The behaviour when the AF does not receive the AAA, or when it arrives after the internal timer waiting for it has expired, or when it arrives with an indication different than DIAMETER\_SUCCESS, are outside the scope of this specification and based on operator policy. + +### 4.4.4 AF Session Termination + +When an AF session is terminated, if the AF had received a successful AA-Answer for the initial AA-Request, the AF shall send a Session-Termination-Request command to the PCRF. Otherwise, the AF shall wait for the initial AA-Answer to be received prior to sending the Session-Termination-Request command to the PCRF. + +When the PCRF receives a ST-Request from the AF, indicating an AF session termination, it shall acknowledge that request by sending a ST-Answer to the AF. Afterwards, it shall free the resources allocated for the corresponding Service Data Flow(s). In order to do that, the PCRF shall initiate the request for the removal of any related PCC/QoS rules from the PCEF/BBRF and for the update of the Authorized QoS for the affected IP-CAN bearer following the corresponding procedures specified at 3GPP TS 29.212 [8]. However, if the AF requests the reporting of access network information within the ST-Request or if the AF provided a threshold for the sponsored data connectivity, the PCRF shall defer sending the ST-Answer. + +If the AF session being terminated corresponds to an MPS session, the PCRF may revoke the actions related to the prioritization of the MPS session in the corresponding IP-CAN as defined in 3GPP TS 29.212 [8]. For Multimedia Priority Service handling for IMS, see Annex A.9. + +If the AF session being terminated corresponds to the last Group Communication session for the IP-CAN session, the PCRF may revoke the actions related to the prioritization of the Group Communication session as specified in 3GPP TS 29.212 [8]. + +If the AF session being terminated corresponds to a session that included the Priority-Sharing-Indicator AVP set to PRIORITY\_SHARING\_ENABLED within the Media-Component-Description AVP, the PCRF should readjust the Allocation and Retention Priority for the remaining services sharing priority as described in clause 4.4.8. + +For sponsored data connectivity, and if a usage threshold was provided for the sponsored data connection at initial provisioning of session information (clause 4.4.1) or modification of session information (clause 4.4.2) procedures, the PCRF shall provide the usage consumed to the AF. For such purpose, the PCRF shall initiate the IP-CAN session modification procedure according 3GPP TS 29.212 [8] in order to obtain the consumed usage. The PCRF shall send then the ST-Answer to the AF including the Used-Service-Unit AVP for reporting accumulated usage within the Sponsored-Connectivity-Data AVP. + +If the AF requires access network information at this step, the AF shall include the Required-Access-Info AVP within the ST-Request command, indicating the required information. In this case, the PCRF shall initiate the IP-CAN session modification procedure according to 3GPP TS 29.212 [8]. The PCRF shall send then the ST-Answer to the AF including the required data within the 3GPP-User-Location-Info AVP (if available), TWAN-Identifier AVP (if available), User-Location-Info-Time AVP (if available), UE-Local-IP-Address AVP (if available), UDP-Source-Port AVP (if available), TCP-Source-Port AVP (if available), 3GPP-SGSN-MCC-MNC AVP (if location info is not available) and/or 3GPP-MS-TimeZone AVP (if available). + +If the RAN-NAS-Cause feature is supported and the AF initiated the termination of the AF session, upon reception of the ST-Request command, the PCRF shall initiate the IP-CAN session modification procedure according to 3GPP TS 29.212 [8]. + +If the RAN-NAS-Cause feature is supported , in all the AF session termination cases , t he PCRF shall send the ST-Answer to the AF including the access network information within the 3GPP-User-Location-Info AVP (if available), TWAN-Identifier (if available and Netloc-Trusted-WLAN feature is supported) User-Location-Info-Time AVP (if available), 3GPP-SGSN-MCC-MNC AVP (if location info is not available) and/or 3GPP-MS-TimeZone AVP (if available). Additionally, if the PCRF received from the PCEF the RAN cause and/or NAS cause, TWAN cause or untrusted WLAN cause, the PCRF shall provide the received cause(s) in the RAN-NAS-Release-Cause AVP in the ST-Answer command. + +NOTE: The PCRF will apply the procedures described in 3GPP TS 29.212 [8] to get updated about the outcome of the resource release over Gx reference point in order to get the location and failure cause(s) when applicable. + +### 4.4.5 Subscription to Notification of Signalling Path Status + +An AF may subscribe to notifications of the status of the AF Signalling transmission path. To do so, the AF shall open an Rx Diameter session with the PCRF for the AF signalling using an AA-Request command. The AF shall provide the UE's IP address (using either the Framed-IP-Address AVP or the Framed-Ipv6-Prefix AVP) and the Specific-Action + +AVP requesting the subscription to "INDICATION\_OF\_LOSS\_OF\_BEARER" and/or "INDICATION\_OF\_RELEASE\_OF\_BEARER". The AF shall additionally provide a Media-Component-Description AVP including a single Media-Sub-Component AVP with the Flow-Usage AVP set to the value "AF\_SIGNALLING". The Media-Component-Description AVP shall contain the Media-Component-Number AVP set to "0". + +If the procedures in Clause 4.4.5A are not applied, the Media-Sub-Component AVP shall contain the Flow-Number AVP set to "0", and the rest of AVPs within the Media-Component-Description and Media-Sub-Component AVPs shall not be used in this case. + +When the PCRF receives an AA-Request as described in the preceding paragraph from the AF, the PCRF shall perform session binding as described in 3GPP TS 29.213 [9] and acknowledges the AAR command by sending an AA-Answer command to the AF. + +PCC/QoS Rules related to AF Signalling IP Flows should be provisioned to PCEF/BBERF using the corresponding procedures specified at 3GPP TS 29.212 [8] at an earlier stage (e.g. typically at the establishment of the IP-CAN bearer dedicated for AF Signalling IP Flows). The PCRF may install the corresponding dynamic PCC/QoS rule for the AF signalling IP flows if none has been installed before. + +NOTE 1: Well-known ports (e.g. 3GPP TS 24.229 [17] for SIP) or wildcard ports can be used by PCRF to derive the dynamic PCC/QoS rule for the AF signalling IP flows. + +If the Rx Diameter Session is only used for subscription to Notification of Signalling Path Status, the AF may cancel the subscription to notifications of the status of the AF Signalling transmission path. In that case, the AF shall use a Session-Termination-Request (STR) command to the PCRF, which shall be acknowledged with a Session-Termination-Answer (STA) command. + +NOTE 2: The Rx Diameter Session created for the AF signalling can also be used when the AF requests notifications of IP-CAN type change, PLMN change, access network information for SMS over IP and/or when the AF provisions AF Signalling Flow Information. + +### 4.4.5A Provisioning of AF Signalling Flow Information + +This clause is applicable when IMS restoration is supported according to supported feature ProvAFsignalFlow as described in clause 5.4.1. + +An AF may provision information about the AF signalling IP flows between the UE and the AF. To do so, the AF shall make use of an Rx Diameter session already opened with the PCRF if an Rx Diameter session related to the AF signalling is already established. The AF may modify an already open Rx Diameter session related to the AF signalling (e.g. an Rx Diameter session established for the purpose of subscription to notification of signalling path status as described in 4.4.5) or it may open a new Rx Diameter session related to the AF signalling if none exists. + +To provision the AF signalling flow information the AF shall provide the UE's IP address using either Framed-IP-Address AVP or Framed-Ipv6-Prefix AVP. The AF shall additionally provide a Media-Component-Description AVP including one or more Media-Sub-Component AVP(s) representing the AF signalling IP flows. The Media-Component-Description AVP shall contain the Media-Component-Number AVP set to "0". Each Media-Sub-Component AVP representing an AF signalling IP flow shall contain the Flow-Number AVP set according to the rules described in Annex B and one or two Flow-Description AVP(s) set to the IP flows of the AF signalling. Additionally, the Media-Sub-Component AVP shall include the Flow-Usage AVP set to the value "AF\_SIGNALLING", the Flow-Status AVP set to "ENABLED" and the AF-Signalling-Protocol AVP set to the value corresponding to the signalling protocol used between the UE and the AF. + +When the PCRF receives from the AF an AA-Request as described in the preceding paragraph, the PCRF shall perform session binding as described in 3GPP TS 29.213 [9] and shall acknowledge the AAR command by sending an AA-Answer command to the AF. + +PCC/QoS Rules related to the AF signalling IP flows could have been provisioned to PCEF/BBERF using the corresponding procedures specified in 3GPP TS 29.212 [8] at an earlier stage (e.g. typically at the establishment of the IP-CAN bearer dedicated for AF Signalling IP Flows). The PCRF shall install the corresponding dynamic PCC/QoS rule for the AF signalling IP flows. + +The AF may de-provision the information about the AF signalling IP flows at any time. To do that, if the Rx Diameter session is only used to provide information about the AF Signalling IP flows, the AF shall close the Rx Diameter + +session by sending a Session-Termination-Request (STR) command to the PCRF, which shall be acknowledged with a Session-Termination-Answer (STA) command. Otherwise, the AF shall remove the IP flows within the Media-Sub-Component AVP by supplying the Flow-Status AVP with value "REMOVED". In both cases, the PCRF shall remove the corresponding dynamic PCC/QoS rule for the AF signalling IP flows. + +### 4.4.6 Traffic Plane Events + +#### 4.4.6.1 IP-CAN Session Termination + +When an IP-CAN session is terminated, the PCRF shall inform the AF about the IP-CAN session termination by sending an ASR (abort session request) command to the AF on each active Rx Diameter session. + +When the AF receives the ASR command, it shall acknowledge the command by sending an ASA (abort session answer) command to the PCRF. After that the AF shall initiate an AF session termination procedure as defined in clause 4.4.4. + +Signalling flows for IP-CAN session termination cases are presented in 3GPP TS 29.213 [9]. + +#### 4.4.6.2 Service Data Flow Deactivation and Resource Allocation Failure + +It may happen that one or more PCC/QoS Rules (i.e. Service Data Flows) are deactivated at the PCEF/BBERF at a certain time, either permanently or temporarily or resource allocation for one or more PCC rules is unsuccessful at the PCEF/BBERF when the PCC rule(s) are installed. When the PCRF gets the knowledge that one or more SDFs have been deactivated, (e.g. due to a bearer release or loss of bearer or out of credit condition), or the resource allocation failed the PCRF shall inform the AF accordingly if the AF has previously subscribed using the Specific-Action AVP in the AAR command. + +When not all the service data flows within the AF session are affected, the PCRF shall inform the AF by sending an RAR (re-authorization request) command. The RAR command shall include the affected IP Flows encoded in the Flows AVP, the cause encoded in the Specific-Action AVP and the content version of a media component within the Content-Version AVP if it was included when the media component was provisioned. + +If the RAN-NAS-Cause feature is supported and the PCRF received the access network information from the PCEF/BBERF due to bearer termination or unsuccessful bearer establishment/modification, the PCRF shall include in the RAR command the access network information within the 3GPP-User-Location-Info AVP (if available), TWAN-Identifier (if available and Netloc-Trusted-WLAN feature is supported) User-Location-Info-Time AVP (if available), 3GPP-SGSN-MCC-MNC AVP (if location info is not available) and/or 3GPP-MS-TimeZone AVP (if available). Additionally, if the PCRF received from the PCEF the RAN cause and/or NAS cause, TWAN cause or untrusted WLAN cause due to bearer termination, the PCRF shall provide the received cause(s) in the RAN-NAS-Release-Cause AVP in the RAR command. + +When the AF receives the RAR command, it shall acknowledge the command by sending an RAA (re-authorization answer) command to the PCRF. The AF may also update the session information by sending an AAR (AA-request) command to the PCRF. + +If the PCRF receives the AAR command, it shall acknowledge the command by sending an AAA (AA-answer) command to the AF. + +When all the service data flows within the AF session are affected, the PCRF shall inform the AF by sending an ASR command on the Rx Diameter session related to the AF session. When the AF receives the ASR command, it shall acknowledge the command by sending an ASA (abort session answer) command to the PCRF. After that the AF shall initiate an AF session termination procedure as defined in clause 4.4.4. + +Signalling flows for Service Data Flow Deactivation and Resource Allocation Failure cases are presented in 3GPP TS 29.213 [9]. + +#### 4.4.6.3 Notification of Signalling Path Status + +In the event that the PCRF is notified of the loss or release of resources associated to the PCC/QoS Rules corresponding with AF Signalling IP Flows, the PCRF shall inform the AF about the Loss of the Signalling Transmission path by sending a Re-Authorization Request (RAR) command to the AF. The RAR shall include the Specific-Action AVP set to + +the value "INDICATION\_OF\_LOSS\_OF\_BEARER" or "INDICATION\_OF\_RELEASE\_OF\_BEARER" and the deactivated IP Flow encoded in the Flows AVP. + +NOTE: According to the standardized QCI characteristics as defined in 3GPP TS 23.203 [2], the IMS signalling specific PCC rules include a QCI corresponding to a non-GBR bearer. When these guidelines are followed, the INDICATION\_OF\_LOSS\_OF\_BEARER will not be reported. + +If the RAN-NAS-Cause feature is supported and the PCRF received the access network information from the PCEF/BBERF due to bearer termination, the PCRF shall include in the RAR command the access network information within the 3GPP-User-Location-Info AVP (if available), TWAN-Identifier (if available and Netloc-Trusted-WLAN feature is supported) User-Location-Info-Time AVP (if available), 3GPP-SGSN-MCC-MNC AVP (if location info is not available) and/or 3GPP-MS-TimeZone AVP (if available). Additionally, if the PCRF received from the PCEF the RAN cause and/or NAS cause, TWAN cause or untrusted WLAN cause due to bearer termination, the PCRF shall provide the received cause(s) in the RAN-NAS-Release-Cause AVP in the RAR command. + +When the AF receives the RAR command, it shall acknowledge the command by sending an RAA command to the PCRF. + +The AF may then decide to terminate the Rx Diameter session used for the notification of the status of the AF Signalling transmission path. The AF may also decide to terminate any other active Rx Diameter session with the PCRF related to the AF Signalling which is not available any longer. In that case, the AF shall then initiate the AF Termination procedure towards the PCRF as defined in clause 4.4.4. + +#### 4.4.6.4 IP-CAN type change Notification + +If the AF has successfully subscribed to change notifications in UE's IP-CAN type and RAT type, the PCRF shall send an RAR command when the corresponding event occurs, i.e. when the UE's IP-CAN type or RAT type changes or becomes available. In this case the RAR from the PCRF shall include the Specific-Action AVP for the subscribed event and include the IP-CAN-Type AVP, RAT-Type AVP (if applicable) and AN-Trusted AVP (if applicable) and AN-GW-Address AVP (if applicable) for the UE's new IP-CAN/RAT. If the PCRF is informed of an IP-CAN type change due to IP flow mobility as specified in 3GPP TS 29.212 [8], where a subset of the flows within the AF session are affected, the PCRF shall include IP-CAN type and RAT type information (if applicable) to IP flow mobility affected service data flows. The IP flow mobility affected service data flows are included within the Flows AVP at command level. + +#### 4.4.6.5 Access Network Charging Information Notification + +If the AF has subscribed to a notification about Access Network Charging Information, the PCRF shall provide the Access Network Charging Information in the response, if already known by the PCRF. If not available, the PCRF shall provide the Access Network Charging Information by sending a Re-Authorization-Request (RAR) command when the Access Network Charging Information is received from the PCEF. If different Access Network Charging Information is applicable to the IP-CAN session, the PCRF shall notify the AF about the Access Network Charging Information that applies to each authorized flow. The RAR shall include the Specific-Action AVP set to the value "CHARGING\_CORRELATION\_EXCHANGE" and shall include the assigned Access-Network-Charging-Identifier(s) and may include the Access-Network-Charging-Address AVP. + +#### 4.4.6.6 Reporting Usage for Sponsored Data Connectivity + +When SponsoredConnectivity is supported or when SponsorChange is supported and the AF indicated to enable sponsored data connectivity and the AF provided usage monitoring thresholds for such sponsor to the PCRF when the Rx Diameter session was established or modified, the PCRF shall report accumulated usage to the AF, when + +- the PCRF detects that the usage threshold provided by the AF has been reached; or +- the AF session is terminated by the AF; +- the AF disables the sponsored data connectivity; or +- the AF session is terminated by the PCRF due to the IP-CAN session termination, the termination of all the service data flows of the AF session or the home operator policy disallowing the UE accessing the sponsored data connectivity in the roaming case. + +When the PCRF detects that the usage threshold has been reached or the AF disables the sponsored data connectivity, the PCRF shall report the accumulated usage as provided by the PCEF/TDF to the AF in a RA-Request (RAR) + +command with the Specific-Action AVP set to the value USAGE\_REPORT; Otherwise, when the AF session is terminated by the AF or the PCRF, the PCRF shall report the accumulated usage as provided by the PCEF/TDF to the AF in ST-Answer (STA) command. The accumulated usage reported by the PCRF corresponds to the usage since the last report to the AF. + +The accumulated usage shall be reported in the Used-Service-Unit AVP within the Sponsored-Connectivity-Data AVP. + +If the AF receives a RAR command indicating the usage threshold is reached, the AF may terminate the AF session or provide a new usage threshold in the Granted-Service-Unit AVP within the Sponsored-Connectivity-Data AVP to the PCRF in the AAR command. Alternatively, the AF may allow the session to continue without providing new usage threshold in the AAR command. + +NOTE: After the PCRF reports the accumulated usage to the AF, the AF can provide a new usage threshold to the PCRF. The monitoring will not start until the PCRF receives the new threshold from the AF and provide it to the PCEF + +#### 4.4.6.7 Reporting Access Network Information + +If the AF requests the PCRF to report the access network information (i.e. user location and/or user timezone information), the AF shall subscribe to the "ACCESS\_NETWORK\_INFO\_REPORT" within the Specific-Action AVP and shall include the required access network information within the Required-Access-Info AVP. The AF may request the PCRF to report the access network information in conjunction with providing the PCRF with the AF session information, refer to clause 4.4.1. Optionally, the AF may request the PCRF to report the access network information without providing service information (see clause A.10.2). In the latter case the AF establishes an Rx session for the AF session upon requesting the access network information from the PCRF with an AA-Request command, containing information required for the session binding in the Framed-IP-Address AVP, the Framed-Ipv6-Prefix AVP Subscription-Id AVP, the Called-Station-Id AVP and/or the IP-Domain-Id AVP. + +The AF may also request the PCRF to report the access network information at Rx session termination. To do so, the AF shall include the required access network information within the Required-Access-Info AVP in the corresponding ST-Request. + +When the PCRF receives a request to report the access network information from the AF in an AAR command or in an STR command triggered by the AF, if the PCRF determines that the access network does not support the access network information reporting based on the currently used IP-CAN type or the values of the RAT-Type AVP or the PCEF/BBERF does not support the NetLoc feature as described in clause 5.4.1, the PCRF shall respond to AF with an AAA or STA command including the NetLoc-Access-Support AVP set to the value of 0 (NETLOC\_ACCESS\_NOT\_SUPPORTED); otherwise, it shall immediately configure the PCEF or BBERF to provide such access network information. + +When the PCRF then receives the access network information from the PCEF/BBERF, the PCRF shall provide the corresponding access network information to the AF within the 3GPP-User-Location-Info AVP (if available), TWAN-Identifier AVP (if available), User-Location-Info-Time AVP (if available), UE-Local-IP-Address AVP (if available), UDP-Source-Port AVP (if available), TCP-Source-Port AVP (if available), 3GPP-SGSN-MCC-MNC AVP (if location info is not available) and/or 3GPP-MS-TimeZone AVP in the RAR command if the Rx session is not being terminated or in the STA command if the Rx session is being terminated. If the information is provided in the RAR command, PCRF shall also provide the ACCESS\_NETWORK\_INFO\_REPORT within Specific-Action AVP. + +NOTE 1: The PCRF receives the access network information from the PCEF/BBERF if it is requested by the AF previously or the IP-CAN bearer/IP-CAN session is terminated. + +When the PCRF receives the NetLoc-Access-Support AVP set to the value of 0 (NETLOC\_ACCESS\_NOT\_SUPPORTED) from the PCEF/BBERF, the PCRF shall send a RAR command including the Specific-Action AVP set to INDICATION\_OF\_ACCESS\_NETWORK\_INFO\_REPORTING\_FAILURE and the NetLoc-Access-Support AVP set to the value of 0 (NETLOC\_ACCESS\_NOT\_SUPPORTED) if the AF requested the access network information in an AAR command or send an STA command including the NetLoc-Access-Support AVP set to the value of 0 (NETLOC\_ACCESS\_NOT\_SUPPORTED) if the AF requested the access network information in an STR command. + +NOTE 2: The 3GPP GPRS, 3GPP EPS, Untrusted WLAN and Trusted WLAN support access network information reporting in this release. + +The PCRF shall not send an RAR command with the ACCESS\_NETWORK\_INFO\_REPORT value within a Specific-Action AVP to report any subsequently received access network information to the AF, unless the AF sends a new request for access network information. + +#### 4.4.6.8 Temporary Network Failure handling + +If the PCRF detects that a temporary network failure has occurred (e.g. the SGW has failed for 3GPP-EPS access as defined in clause B.3.14 of 3GPP TS 29.212 [8]) and the AF requests an AF session establishment or modification in an AA-Request command, the PCRF shall respond to the AF with an AA-Answer including the Experimental-Result-Code AVP set to the value TEMPORARY\_NETWORK\_FAILURE. + +If the PCRF detects that a temporary network failure has occurred (e.g. the SGW has failed for 3GPP-EPS access) and the AF requests an AF session termination in a ST-Request command, the PCRF shall respond with successful Result-Code AVP to the AF. + +NOTE 1: If the AF includes the Required-Access-Info AVP in the ST-Request command to request the access network information, the PCRF will not include the access network information in the ST-Answer command. + +NOTE 2: Actions over Gx/Gxx reference point when there is a temporary network failure are described in 3GPP TS 29.212 [8]. For example, for S-GW Restoration procedures the PCRF will wait for the SGW recovery before deleting the corresponding PCC/QoS rules, according to clause B.3.14 in that specification. + +If the PCRF detects that the PCC/QoS rules related to an AF session cannot be installed or modified because there is a temporary network failure (e.g. SGW failed according to clause B.3.14 in 3GPP TS 29.212 [8]) and if requested by the AF, the PCRF shall send a RA-Request command to the AF with the Specific-Action AVP set to INDICATION\_OF\_FAILED\_RESOURCES\_ALLOCATION and the content version of a media component within the Content-Version AVP if it was included when the media component was provisioned. If the modification of the PCC/QoS rules fails, the PCRF may provide the status of the related service information within the Media-Component-Status AVP. + +#### 4.4.6.9 PLMN information change Notification + +If the AF has successfully subscribed to PLMN\_CHANGE notification, the PCRF shall send an RAR command when the corresponding event occurs, i.e. when the PLMN where the UE is located has been updated or becomes available. In this case the RAR from the PCRF shall include the Specific-Action AVP set to PLMN\_CHANGE and include the 3GPP-SGSN-MCC-MNC AVP for the PLMN where the UE is located. + +### 4.4.7 P-CSCF Restoration Enhancement Support + +This clause is applicable when the PCRF-based P-CSCF Restoration Enhancement, as defined in 3GPP TS 23.380 [28], is supported by both P-CSCF and PCRF. + +The P-CSCF acting as AF shall send an AAR command including the Rx-Request-Type AVP set to the value PCSCF\_RESTORE (2) to the PCRF in the case P-CSCF Restoration needs to be performed. This AAR shall include the following information required by the DRA or PCRF to find the corresponding IP-CAN session: + +- The UE's IP address as applicable in the Framed-IP-Address AVP or in the Framed-Ipv6-Prefix AVP. If the IP address is not unique (e.g. private IPv4 case), the P-CSCF shall also include the IP-Domain-ID AVP if available. +- If the IP address is not available or if the IP address is not unique and the IP-Domain-ID is not available, the P-CSCF shall include the IMSI in the Subscription-Id AVP and the APN in the Called-Station-Id AVP. + +The AF shall also include the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1) in the AAR command, as described in IETF RFC 6733 [52]. As a consequence, the PCRF shall not maintain any state information about this session. + +The PCRF shall acknowledge the AAR command by sending an AAA command to the P-CSCF acting as AF and shall include the Auth-Session-State AVP set to NO\_STATE\_MAINTAINED (1). The PCRF shall send a request for P-CSCF Restoration to the PCEF for the corresponding IP-CAN session. + +### 4.4.8 Priority Sharing Request + +If PrioritySharing feature is supported, the AF may include the Priority-Sharing-Indicator AVP set to PRIORITY\_SHARING\_ENABLED within the Media-Component-Description AVP in order to indicate to the PCRF that the related media flow is allowed to use the same Allocation and Retention Priority as media flows which are assigned the same QCI in the PCRF belonging to other AF sessions for the same IP-CAN session that also contain the Priority-Sharing-Indicator AVP set to PRIORITY\_SHARING\_ENABLED. If the MCPTT-Preemption feature is supported, the AF may also include the Pre-emption-Capability AVP containing the suggested pre-emption capability value and the Pre-emption-Vulnerability AVP containing the suggested pre-emption vulnerability value within the Media-Component-Description AVP for the PCRF to determine ARP values and include the Pre-emption-Control-Info AVP containing the pre-emption control information at the AAR command level for the PCRF to perform pre-emption control. The AF may also include the INDICATION\_OF\_FAILED\_RESOURCES\_ALLOCATION within Specific-Action AVP to request notification for resource allocation failure. Upon reception of this information, the PCRF shall behave as described in 3GPP TS 29.212 [8], clauses 4.5.27 and 4a.5.17. For the handling of MCPTT sessions, see Annex A.13. + +NOTE 1: Service data flow deactivation procedures will apply according to clause 4.4.6.2. + +NOTE 2: This enhancement avoids the risk that a bearer establishment request is rejected if the maximum number of active bearers is exceeded. + +If the AF earlier has indicated a media flow priority sharing to the PCRF by setting the Priority-Sharing-Indicator AVP to PRIORITY\_SHARING\_ENABLED, the AF may include the Priority-Sharing-Indicator AVP set to PRIORITY\_SHARING\_DISABLED within the Media-Component-Description AVP in order to indicate to the PCRF that the related media flow shall not be part of the mechanism for sharing the Allocation and Retention Priority with other media flows any longer. + +If this media flow was in priority sharing with other media flows the PCRF should readjust the Allocation and Retention Priority for the remaining services sharing priority as described in 3GPP TS 29.212 [8], clauses 4.5.27 and 4a.5.17 and handle the media flow excluded from priority sharing according to normal PCC/QoS rule provisioning procedures described in 3GPP TS 29.212 [8], clauses 4.5.2 and 4a.5.2. + +If the AF earlier has indicated media flow priority sharing to the PCRF by setting the Priority-Sharing-Indicator AVP to PRIORITY\_SHARING\_ENABLED for media flows and the AF indicates to remove one or more of the media flows in priority sharing with other media flows, the PCRF should readjust the Allocation and Retention Priority for the remaining services sharing priority as described in 3GPP TS 29.212 [8], clauses 4.5.27 and 4a.5.17 and handle the media flow removed according to normal PCC/QoS rule provisioning procedures described in 3GPP TS 29.212 [8], clauses 4.5.2 and 4a.5.2. + +If the AF session being terminated corresponds to a session that included the Priority-Sharing-Indicator AVP set to PRIORITY\_SHARING\_ENABLED within the Media-Component Description AVP, if the related media flow(s) was in priority sharing with other media flows the PCRF should readjust the Allocation and Retention Priority for the remaining services sharing Allocation and Retention Priority as described in 3GPP TS 29.212 [8], clauses 4.5.27 and 4a.5.17 and handle the media flow removed according to normal PCC/QoS rule provisioning procedures described in 3GPP TS 29.212 [8], clauses 4.5.2 and 4a.5.2. + +### 4.4.9 Support for media component versioning + +The support of the media component versioning is optional. When the MediaComponentVersioning feature is supported, the AF and the PCRF shall comply with the procedures specified in this clause. + +If required by operator policies, the AF shall assign a content version to the media component related to certain service and provide the PCRF within the Content-Version AVP as part of the Media-Component-Description AVP. Upon each media component modification, if the content version was assigned to a media component, the AF shall assign a new content version. In this case, all the content related to that media component shall be included. The content version shall be unique for the lifetime of the media component. + +NOTE 1: The AF will include all the content of the media component in each media component modification in order to ensure that the media component is installed with the proper information regardless of the outcome of the bearer procedure related to previous interactions that are not reported to the PCRF yet. + +If the PCRF receives the Content-Version AVP including an content version for certain media component, the PCRF will follow the procedures described in 3GPP TS 29.212 [8], clause 4.5.28 and clause 4a.5.18. + +When the PCRF is notified about the outcome of the resource allocation related to one content version of a media component as described in clause 4.5.28 or clause 4a.5.18 in 3GPP TS 29.212 [8] and if the PCRF is required to notify the AF, the PCRF shall provide the content version of the media component within the Content-Version AVP corresponding to the value of content version of the PCC/QoS rule and the status of the media component within the Media-Component-Status AVP corresponding to the status of the PCC/QoS rule to the AF as part of the Flows AVP. + +The PCRF shall include more than one Content-Version AVPs for the same media component within the Flows AVP in a RAR command if it has received multiple content versions as described in clause 4.5.28 or clause 4a.5.18 in 3GPP TS 29.212 [8]. + +NOTE 2: The AF will use the content version to identify the media component version that failed or succeed when multiple provisions of the same media component occur in a short period of time. How the AF handles such situations is not specified. + +### 4.4.10 Extended bandwidth support for EPC supporting Dual Connectivity (E-UTRAN and 5G NR) + +When the Extended-Max-Requested-BW-NR feature, the Extended-Min-Requested-BW-NR feature, and/or the Extended-BW-E2EQOSMTSI-NR features are supported, extended bandwidth AVPs representing bitrates in kbps shall be used to represent bandwidth values higher than $2^{32}-1$ bps instead of the bandwidth AVPs with a maximum value of $2^{32}-1$ bps that represent bitrates in bps. + +For the Extended-Max-Requested-BW-NR feature: + +- Extended-Max-Requested-BW-DL/UL AVPs shall be used instead of Max-Requested-Bandwidth-DL/UL AVPs. + +For the Extended-BW-E2EQOSMTSI-NR feature: + +- Extended-Max-Supported-BW-DL/UL AVPs shall be used instead of Max-Supported-Bandwidth-DL/UL AVPs. +- Extended-Min-Desired-BW-DL/UL AVPs shall be used instead of Min-Desired-Bandwidth-DL/UL AVPs. + +For the Extended-Min-Requested-BW-NR feature: + +- Extended-Min-Requested-BW-DL/UL AVPs shall be used instead of Min-Requested-Bandwidth-DL/UL AVPs. + +For values lower or equal to $2^{32}-1$ bps AVPs representing bitrates in bps shall be used. + +When the Rx session is being established, if the AF supports the corresponding feature (as listed above) and needs to indicate bandwidth values higher than $2^{32}-1$ bps, AVPs representing bitrate in bps shall be provided with value set to $2^{32}-1$ bps and bandwidth AVPs representing bitrate in kbps shall be provided with the actual required bandwidth. + +NOTE: When the Diameter session is being established, the originator node does not know yet the features supported by the peer node. + +### 4.4.11 MPS for DTS Control + +The support of the MPSforDTS feature is optional. When the MPSforDTS feature is supported as described in clause 5.4.1, the AF and the PCRF shall comply with the procedures specified in this clause. + +MPS for DTS is the means for an AF to invoke/revoke the Priority EPS Bearer Service for the default bearer only, i.e. without designating a particular service data flow for priority service. MPS for DTS applies only to non-IMS APNs. + +To invoke/revoke MPS for DTS, the AF shall include the MPS-Action AVP in the AAR command. The MPS-Action AVP signals a change to the default bearer and IP flows mapped to the default bearer. + +When the MPS-Action AVP is set to ENABLE\_MPS\_FOR\_DTS (1) and included in the AAR command, and if allowed by local policy, the PCRF does not check the user's MPS subscription details and shall upgrade the QoS of the default bearer to MPS, as specified in 3GPP TS 29.212 [8]. + +When the MPS-Action AVP is set to AUTHORIZE\_AND\_ENABLE\_MPS\_FOR\_DTS (2) and included in the AAR command, and if allowed by local policy, the PCRF shall check the user's MPS subscription details and if valid, shall upgrade the QoS of the default bearer to MPS, as specified in 3GPP TS 29.212 [8]. If the request is not allowed, the PCRF shall reject the request indicating REQUESTED\_SERVICE\_NOT\_AUTHORIZED. + +When the MPS-Action AVP is set to DISABLE\_MPS\_FOR\_DTS (0) and included in the AAR command, and if allowed by local policy, the PCRF does not check the user's MPS subscription details and shall downgrade the QoS of the default bearer to non-MPS priority, as specified in 3GPP TS 29.212 [8]. + +NOTE: How the AF authorizes the request is out of scope of the present document. + +The AF may also include in the AAR command the Specific-Action AVP with the value SUCCESSFUL\_QOS\_UPDATE to request notification when the PCRF has successfully acted upon the invocation/revocation request indicated in the MPS-Action AVP. The PCRF shall inform the AF of successful MPS for DTS invocation/revocation with a RAR command with the Specific-Action AVP with the value SUCCESSFUL\_QOS\_UPDATE. + +The AF may also include in the AAR command the Specific-Action AVP with the value FAILED\_QOS\_UPDATE to request notification when the invocation/revocation request indicated in the MPS-Action AVP has failed. The PCRF shall inform the AF of the failure of the MPS for DTS invocation/revocation with a RAR command with the Specific-Action AVP with the value FAILED\_QOS\_UPDATE. + +When the PCRF receives from the AF an AA-Request as described in the preceding paragraphs, the PCRF shall perform session binding as described in 3GPP TS 29.213 [9] and shall acknowledge the AAR command by sending an AA-Answer command to the AF. + +The PCRF shall install the event trigger for the MPS for DTS request using the corresponding procedures specified in 3GPP TS 29.212 [8] if the AF requests the notification. + +The AF may use the procedure specified in clause 4.4.12 to establish a priority signalling IP flow between the UE and AF. + +### 4.4.12 Provisioning of MPS for DTS AF Signalling Flow Information + +This clause is applicable when MPS for DTS is supported according to the supported feature MPSforDTS as described in clause 5.4.1. + +An AF may provision information about the AF signalling IP flows between the UE and the AF. To do so, the AF may modify an already open Rx Diameter session related to the AF signalling (e.g. an Rx Diameter session established for the purpose of DTS control as described in clause 4.4.11) or it may open a new Rx Diameter session related to the AF signalling if none exists. + +To provision the AF signalling flow information, the AF shall provide the UE's IP address using either Framed-IP-Address AVP or Framed-Ipv6-Prefix AVP. The AF shall additionally provide the MPS-Identifier AVP and a Media-Component-Description AVP containing a Media-Component-Number AVP set to "0", and including a Media-Sub-Component AVP that contains the Flow-Description AVP set to the AF signalling IP flow. If the AuthorizationForMpsSignalling feature is supported, the AF shall provide the MPS-Action AVP set to value AUTHORIZE\_AND\_ENABLE\_MPS\_FOR\_AF\_SIGNALLING (3). The Media-Sub-Component AVP shall include the Flow-Number AVP set according to the rules described in Annex B and the Flow-Usage AVP set to the value "AF\_SIGNALLING" and the Flow-Status AVP set to "ENABLED". + +When the PCRF receives from the AF an AA-Request as described in the preceding paragraph, the PCRF shall determine whether the request is accepted or not. If accepted, the PCRF shall perform session binding as described in 3GPP TS 29.213 [9] and shall acknowledge the AAR command by sending an AA-Answer command to the AF. If rejected, the PCRF shall indicate the cause for the rejection with the Experimental-Result-Code AVP set to the value REQUESTED\_SERVICE\_NOT\_AUTHORIZED. + +The PCRF shall set appropriate QoS values for the AF signalling IP flow and install the corresponding dynamic PCC rule at the PCEF and the QoS rule at BBERF if applicable. + +The AF may de-provision the information about the AF signalling IP flows at any time. To do that, if the Rx Diameter session is only used to provide information about the AF Signalling IP flows, the AF shall close the Rx Diameter session by sending a Session-Termination-Request (STR) command to the PCRF, which shall be acknowledged with a Session-Termination-Answer (STA) command. Otherwise, the AF shall remove the IP flows within the Media-Sub-Component AVP by supplying the Flow-Status AVP with value "REMOVED". In both cases, the PCRF shall remove the corresponding dynamic PCC and QoS rule if applicable for the AF signalling IP flows. + +NOTE: Combining the request for the AF signalling flow with an MPS for DTS invocation/revocation request is not supported in this release. + +# 5 Rx protocol + +## 5.1 Protocol support + +The Rx interface in the present release is based on Rx and Gq protocols defined for Release 6 as specified in 3GPP TS 29.211 [7] and 3GPP TS 29.209 [5] respectively. However, to be able to separate the policy and charging rules function (PCRF) of the present release from the policy decision function (PDF) and charging rules function (CRF) of Release 6, the Rx application in the present release has an own vendor specific Diameter application. + +The Rx application is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP and the Application-ID for the Rx application in the present release is 16777236. The vendor identifier assigned by IANA to 3GPP () is 10415. + +NOTE: A route entry can have a different destination based on the application identification AVP of the message. Therefore, Diameter agents (relay, proxy, redirection, translation agents) must be configured appropriately to identify the 3GPP Rx application within the Auth-Application-Id AVP in order to create suitable routing tables. + +The Rx application identification shall be included in the Auth-Application-Id AVP. + +With regard to the Diameter protocol defined over the Rx reference point, the PCRF acts as a Diameter server, in the sense that it is the network element that handles AF session authorization requests for a particular realm. The AF acts as the Diameter client, in the sense that it is the network element requesting the authorization of resources for an AF session. + +## 5.2 Initialization, maintenance and termination of connection and session + +The initialization and maintenance of the connection between each AF and PCRF pair is defined by the underlying protocol. Establishment and maintenance of connections between Diameter nodes is described in IETF RFC 6733 [52]. + +After establishing the transport connection, the PCRF and the AF shall advertise the support of the Rx specific Application by including the value of the application identifier in the Auth-Application-Id AVP and the value of the 3GPP (10415) in the Vendor-Id AVP of the Vendor-Specific-Application-Id AVP contained in the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. The Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands are specified in the Diameter Base Protocol (IETF RFC 6733 [52]). + +The termination of the Diameter user session is specified in IETF RFC 6733 [52] in clauses 8.4 and 8.5. The description of how to use of these termination procedures in the normal cases is embedded in the procedures description (clause 4.4). + +## 5.3 Rx specific AVPs + +### 5.3.0 General + +Table 5.3.0.1 describes the Diameter AVPs defined for the Rx interface protocol, their AVP Code values, types, possible flag values, whether or not the AVP may be encrypted and which supported feature the AVP is applicable to. The Vendor-Id header of all AVPs defined in the present document shall be set to 3GPP (10415). + +NOTE: Most of these AVPs have already been defined in 3GPP TS 29.209 [5] for Rel-6. Their definition is based on the one used for Rel-6 with some possible modifications to be applied to the Rel-7 protocols. + +**Table 5.3.0.1: Rx specific Diameter AVPs** + +| Attribute Name | AVP Code | Clause defined | Value Type (Note 2) | AVP Flag rules (Note 1) | | | | | Applicability (Note 3) | +|------------------------------------------|----------|----------------|---------------------|-------------------------|-----|------------|----------|-----------|------------------------------| +| | | | | Must | May | Should not | Must not | May Encr. | | +| 5GMM-Cause | 573 | 5.3.70 | Unsigned32 | V | P | | M | Y | RAN-NAS-Cause | +| 5GS-RAN-NAS-Release-Cause | 572 | 5.3.69 | Grouped | V | P | | M | Y | RAN-NAS-Cause | +| 5GSM-Cause | 574 | 5.3.71 | Unsigned32 | V | P | | M | Y | RAN-NAS-Cause | +| Abort-Cause | 500 | 5.3.1 | Enumerated | M,V | P | | | Y | | +| Access-Network-Charging-Address | 501 | 5.3.2 | Address | M,V | P | | | Y | | +| Access-Network-Charging-Identifier | 502 | 5.3.3 | Grouped | M,V | P | | | Y | | +| Access-Network-Charging-Identifier-Value | 503 | 5.3.4 | OctetString | M,V | P | | | Y | | +| Acceptable-Service-Info | 526 | 5.3.24 | Grouped | M,V | P | | | Y | | +| AF-Application-Identifier | 504 | 5.3.5 | OctetString | M,V | P | | | Y | | +| AF-Charging-Identifier | 505 | 5.3.6 | OctetString | M,V | P | | | Y | | +| AF-Requested-Data | 551 | 5.3.50 | Unsigned32 | V | P | | M | Y | | +| AF-Signalling-Protocol | 529 | 5.3.26 | Enumerated | V | P | | M | Y | ProvAFsignalFlow | +| Application-Service-Provider-Identity | 532 | 5.3.29 | UTF8String | V | P | | M | Y | SponsoredConnectivity | +| Callee-Information | 565 | 5.3.62 | Grouped | V | P | | M | Y | VBCLTE | +| Codec-Data | 524 | 5.3.7 | OctetString | M,V | P | | | Y | | +| Content-Version | 552 | 5.3.49 | Unsigned64 | V | P | | M | Y | MediaComponentVersioning | +| Desired-Max-Latency | 567 | 5.3.64 | Float32 | V | P | | M | Y | FLUS
QoSHint | +| Desired-Max-Loss | 568 | 5.3.65 | Float32 | V | P | | M | Y | FLUS
QoSHint | +| Extended-Max-Requested-BW-DL | 554 | 5.3.52 | Unsigned32 | V | P | | M | Y | Extended-Max-Requested-BW-NR | +| Extended-Max-Requested-BW-UL | 555 | 5.3.53 | Unsigned32 | V | P | | M | Y | Extended-Max-Requested-BW-NR | +| Extended-Max-Supported-BW-DL | 556 | 5.3.54 | Unsigned32 | V | P | | M | Y | Extended-BW-E2EQOSMTSI-NR | +| Extended-Max-Supported-BW-UL | 557 | 5.3.55 | Unsigned32 | V | P | | M | Y | Extended-BW-E2EQOSMTSI-NR | +| Extended-Min-Desired-BW-DL | 558 | 5.3.56 | Unsigned32 | V | P | | M | Y | Extended-BW-E2EQOSMTSI-NR | +| Extended-Min-Desired-BW-UL | 559 | 5.3.57 | Unsigned32 | V | P | | M | Y | Extended-BW-E2EQOSMTSI-NR | +| Extended-Min-Requested-BW-DL | 560 | 5.3.58 | Unsigned32 | V | P | | M | Y | Extended-Min-Requested-BW-NR | +| Extended-Min-Requested-BW-UL | 561 | 5.3.59 | Unsigned32 | V | P | | M | Y | Extended-Min-Requested-BW-NR | +| Flow-Description | 507 | 5.3.8 | IPFilterRule | M,V | P | | | Y | | +| Flow-Number | 509 | 5.3.9 | Unsigned32 | M,V | P | | | Y | | +| Flows | 510 | 5.3.10 | Grouped | M,V | P | | | Y | | +| Flow-Status | 511 | 5.3.11 | Enumerated | M,V | P | | | Y | | +| Flow-Usage | 512 | 5.3.12 | Enumerated | M,V | P | | | Y | | +| FLUS-Identifier | 566 | 5.3.63 | OctetString | V | P | | M | Y | FLUS | +| GCS-Identifier | 538 | 5.3.36 | OctetString | V | P | | M | Y | GroupComService | +| GLI-Identifier | 580 | 5.3.77 | OctetString | V | P | | M | Y | NetLoc-Wireline | +| HFC-Node-Identifier | 579 | 5.3.76 | OctetString | V | P | | M | Y | NetLoc-Wireline | +| IMS-Content-Identifier | 563 | 5.3.60 | OctetString | V | P | | | Y | VBC | +| IMS-Content-Type | 564 | 5.3.61 | Enumerated | V | P | | | Y | VBC | +| IP-Domain-Id | 537 | 5.3.35 | OctetString | V | P | | M | Y | | +| Line-Type | 581 | 5.3.78 | Unsigned32 | V | P | | M | Y | NetLoc-Wireline | +| MA-Information | 570 | 5.3.66 | Grouped | V | P | | M | Y | ATSSS | +| MA-Information-Action | 571 | 5.3.67 | Unsigned32 | V | P | | M | Y | ATSSS | +| Max-Requested-Bandwidth-DL | 515 | 5.3.14 | Unsigned32 | M,V | P | | | Y | | +| Max-Requested-Bandwidth-UL | 516 | 5.3.15 | Unsigned32 | M,V | P | | | Y | | + +| | | | | | | | | | | +|--------------------------------------|-----|---------|-------------|-----|---|--|---|---|----------------------------------------| +| Max-Supported-Bandwidth-DL | 543 | 5.3.41 | Unsigned32 | V | P | | M | Y | E2EQOSMTSI | +| Max-Supported-Bandwidth-UL | 544 | 5.3.42 | Unsigned32 | V | P | | M | Y | E2EQOSMTSI | +| MCPPT-Identifier | 547 | 5.3.45 | OctetString | V | P | | M | Y | MCPPT | +| MCVideo-Identifier | 562 | 5.3.45A | OctetString | V | P | | M | Y | MCVideo | +| Media-Component-Description | 517 | 5.3.16 | Grouped | M,V | P | | | Y | | +| Media-Component-Number | 518 | 5.3.17 | Unsigned32 | M,V | P | | | Y | | +| Media-Component-Status | 549 | 5.3.48 | Unsigned32 | V | P | | M | Y | | +| Media-Sub-Component | 519 | 5.3.18 | Grouped | M,V | P | | | Y | | +| Media-Type | 520 | 5.3.19 | Enumerated | M,V | P | | | Y | | +| MPS-Identifier | 528 | 5.3.30 | OctetString | V | P | | M | Y | Rel10 | +| Min-Desired-Bandwidth-DL | 545 | 5.3.43 | Unsigned32 | V | P | | M | | E2EQOSMTSI | +| Min-Desired-Bandwidth-UL | 546 | 5.3.44 | Unsigned32 | V | P | | M | | E2EQOSMTSI | +| Min-Requested-Bandwidth-DL | 534 | 5.3.32 | Unsigned32 | V | P | | M | Y | Rel10 | +| Min-Requested-Bandwidth-UL | 535 | 5.3.33 | Unsigned32 | V | P | | M | Y | Rel10 | +| MPS-Action | 582 | 5.3.79 | Enumerated | V | P | | M | Y | MPSforDTS | +| NGAP-Cause | 575 | 5.3.72 | Grouped | V | P | | M | Y | RAN-NAS-Cause | +| NGAP-Group | 576 | 5.3.73 | Unsigned32 | V | P | | M | Y | RAN-NAS-Cause | +| NGAP-Value | 577 | 5.3.74 | Unsigned32 | V | P | | M | Y | RAN-NAS-Cause | +| NID | 569 | 5.3.68 | OctetString | V | P | | M | Y | | +| Priority-Sharing-Indicator | 550 | 5.3.47 | Enumerated | V | P | | M | Y | PrioritySharing | +| Pre-emption-Control-Info | 553 | 5.3.51 | Unsigned32 | V | P | | M | Y | MCPPT-Preemption | +| Required-Access-Info | 536 | 5.3.34 | Enumerated | V | P | | M | Y | NetLoc | +| Retry-Interval | 541 | 5.3.39 | Unsigned32 | V | P | | M | Y | DeferredService | +| Rx-Request-Type | 533 | 5.3.31 | Enumerated | V | P | | M | Y | | +| RR-Bandwidth | 521 | 5.3.20 | Unsigned32 | M,V | P | | | Y | | +| RS-Bandwidth | 522 | 5.3.21 | Unsigned32 | M,V | P | | | Y | | +| Service-Authorization-Info | 548 | 5.3.46 | Unsigned32 | V | P | | M | Y | | +| Service-URN | 525 | 5.3.23 | OctetString | M,V | P | | | Y | | +| Service-Info-Status | 527 | 5.3.25 | Enumerated | M,V | P | | | Y | | +| Sharing-Key-DL | 539 | 5.3.37 | Unsigned32 | V | P | | M | Y | ResShare | +| Sharing-Key-UL | 540 | 5.3.38 | Unsigned32 | V | P | | M | Y | ResShare | +| Specific-Action | 513 | 5.3.13 | Enumerated | M,V | P | | | Y | | +| SIP-Forking-Indication | 523 | 5.3.22 | Enumerated | M,V | P | | | Y | | +| Sponsor-Identity | 531 | 5.3.28 | UTF8String | V | P | | M | Y | SponsoredConnectivity | +| Sponsored-Connectivity-Data (NOTE 4) | 530 | 5.3.27 | Grouped | V | P | | M | Y | SponsoredConnectivity
SCTimeBasedUM | +| Sponsoring-Action | 542 | 5.3.40 | Enumerated | V | P | | M | Y | SponsorChange | +| Wireline-User-Location-Info | 578 | 5.3.75 | Grouped | V | P | | M | Y | NetLoc-Wireline | + +NOTE 1: The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [52]. + +NOTE 2: The value types are defined in IETF RFC 6733 [52]. + +NOTE 3: AVPs marked with a supported feature (e.g. "ProvAFsignalFlow", "SponsoredConnectivity", "Rel10" or "NetLoc") are applicable as described in clause 5.4.1 + +NOTE 4: Volume Usage monitoring control functionality is applicable for SponsoredConnectivity supported feature. Time Based Usage monitoring control is applicable for SCTimeBasedUM supported feature. + +### 5.3.1 Abort-Cause AVP + +The Abort-Cause AVP (AVP code 500) is of type Enumerated, and determines the cause of an abort session request (ASR) or of a RAR indicating a bearer release. The following values are defined: + +BEARER\_RELEASED (0) + +This value is used when the bearer has been deactivated as a result from normal signalling handling. For GPRS the bearer refers to the PDP Context. It is also used when all the resource allocation corresponding to an AF session fails. + +#### **INSUFFICIENT\_SERVER\_RESOURCES (1)** + +This value is used to indicate that the server is overloaded and needs to abort the session. + +#### **INSUFFICIENT\_BEARER\_RESOURCES (2)** + +This value is used when the bearer has been deactivated due to insufficient bearer resources at a transport gateway (e.g. GGSN for GPRS). + +#### **PS\_TO\_CS\_HANDOVER (3)** + +This value is used when the PCRF needs to initiate the AF session termination due to PS to CS handover. + +#### **SPONSORED\_DATA\_CONNECTIVITY\_DISALLOWED (4)** + +This value is used in the ASR when the PCRF needs to initiate the AF session termination due to the operator policy (e.g. disallowing the UE accessing the sponsored data connectivity in the roaming case). + +### 5.3.2 Access-Network-Charging-Address AVP + +The Access-Network-Charging-Address AVP (AVP code 501) is of type Address, and it indicates the IP Address of the network entity within the access network performing charging (e.g. the GGSN IP address). The Access-Network-Charging-Address AVP should not be forwarded over an inter-operator interface. + +### 5.3.3 Access-Network-Charging-Identifier AVP + +The Access-Network-Charging-Identifier AVP (AVP code 502) is of type Grouped, and contains a charging identifier (e.g. GCID) within the Access-Network-Charging-Identifier-Value AVP along with information about the flows transported within the corresponding bearer within the Flows AVP. If no Flows AVP is provided, the Access-Network-Charging-Identifier-Value applies for all flows within the AF session. + +The Access-Network-Charging-Identifier AVP can be sent from the PCRF to the AF. The AF may use this information for charging correlation with session layer. + +AVP Format: + +``` +Access-Network-Charging-Identifier ::= < AVP Header: 502 > + { Access-Network-Charging-Identifier-Value } + *[ Flows ] +``` + +### 5.3.4 Access-Network-Charging-Identifier-Value AVP + +The Access-Network-Charging-Identifier-Value AVP (AVP code 503) is of type OctetString, and contains a charging identifier (e.g. GCID). + +### 5.3.5 AF-Application-Identifier AVP + +The AF-Application-identifier AVP (AVP code 504) is of type OctetString, and it contains information that identifies the particular service that the AF service session belongs to. This information may be used by the PCRF to differentiate QoS for different application services. + +For example the AF-Application-Identifier may be used as additional information together with the Media-Type AVP when the QoS class for the bearer authorization at the Gx interface is selected. The AF-Application-Identifier may be used also to complete the QoS authorization with application specific default settings in the PCRF if the AF does not provide full service information. + +The AF-Application-Identifier AVP may also be used to trigger the PCRF to indicate to the PCEF/TDF to perform the application detection based on the operator's policy. + +### 5.3.6 AF-Charging-Identifier AVP + +The AF-Charging-Identifier AVP (AVP code 505) is of type OctetString, contains the AF Charging Identifier that is sent by the AF. This information may be used for charging correlation with bearer layer. + +### 5.3.7 Codec-Data AVP + +The Codec-Data AVP (AVP code 524) is of type OctetString. + +The Codec-Data AVP shall contain codec related information known at the AF. This information shall be encoded as follows: + +- The first line of the value of the Codec-Data AVP shall consist of either the word "uplink" or the word "downlink" (in ASCII, without quotes) followed by a new-line character. The semantics of these words are the following: + - "uplink" indicates that the SDP was received from the UE and sent to the network. + - "downlink" indicates that the SDP was received from the network and sent to the UE. + +NOTE 1: The first line indicates the direction of the source of the SDP used to derive the information. The majority of the information within the Codec-Data AVP indicating "downlink" describes properties, for instance receiver capabilities, of the sender of the SDP, the network in this case and is therefore applicable for IP flows in the uplink direction. Similarly, the majority of the information within the Codec-Data AVP indicating "uplink" describes properties, for instance receiver capabilities, of the sender of the SDP, the UE in this case and is therefore applicable for IP flows in the downlink direction. + +- The second line of the value of the Codec-Data AVP shall consist of either the word "offer" or the word "answer", or the word "description" (in ASCII, without quotes) followed by a new-line character. The semantics of these words are the following: + - "offer" indicates that SDP lines from an SDP offer according to RFC 3264 [18] are being provisioned in the Codec-Data AVP; + - "answer" indicates that SDP lines from an SDP answer according to RFC 3264 [18] are being provisioned in the Codec-Data AVP; + - "description" indicates that SDP lines from a SDP session description in a scenario where the offer-answer mechanism of RFC 3264 [18] is not being applied are being provisioned in the Codec-Data AVP. For instance, SDP from an RTSP "Describe" reply may be provisioned. +- The rest of the value shall consist of SDP line(s) in ASCII encoding separated by new-line characters, as specified in IETF RFC 4566 [13]. The first of these line(s) shall be an "m" line. The remaining lines shall be any available SDP "a" and "b" lines related to that "m" line. However, to avoid duplication of information, the SDP "a=sendrecv", "a=recvonly", "a=sendonly", "a=inactive", "a=bw-info", "b:AS", "b:RS" and "b:RR" lines do not need to be included. + +NOTE 2: For backwards compatibility, it is expected that the codec algorithms in the PCRF described in 3GPP TS 29.213 [9] allow the introduction of new SDP lines without rejecting the request when Codec-Data AVP is provided as part of the Media-Component-Description AVP. The QoS derivation in that case will not take the new SDP line(s) into account. + +### 5.3.8 Flow-Description AVP + +The Flow-Description AVP (AVP code 507) is of type IPFilterRule, and defines a packet filter for an IP flow with the following information: + +- Direction (in or out). The direction "in" refers to uplink IP flows, and the direction "out" refers to downlink IP flows. +- Source and destination IP address (possibly masked). + +- Protocol. +- Source and destination port. + +NOTE 1: When "ip" as key word is used in the protocol, the port(s) are used to describe the port(s) of any protocol if available. + +The IPFilterRule type shall be used over Rx interface with the following restrictions: + +- The Source Port may be omitted to indicate that any source port is allowed. Lists or ranges shall not be used. +- Only the Action "permit" shall be used. +- No "options" shall be used. +- The invert modifier "!" for addresses shall not be used. +- The keyword "assigned" shall not be used. + +NOTE 2: For TCP protocol, destination port can also be omitted. + +If any of these restrictions is not observed by the AF, the server shall send an error response to the AF containing the Experimental-Result-Code AVP with value FILTER\_RESTRICTIONS. + +For the Rx interface, the Flow description AVP shall be used to describe a single IP flow. + +### 5.3.9 Flow-Number AVP + +The Flow-Number AVP (AVP code 509) is of type Unsigned32, and it contains the ordinal number of the IP flow(s), assigned according to the rules in Annex B. + +### 5.3.10 Flows AVP + +The Flows AVP (AVP code 510) is of type Grouped, and it indicates IP flows via their flow identifiers. + +When reporting an out of credit condition, the Final-Unit-Action AVP indicates the termination action applied to the impacted flows. + +If no Flow-Number AVP(s) are supplied, the Flows AVP refers to all Flows matching the media component number. + +When reporting a resource allocation failure related to the modification of session information, the Media-Component-Status AVP may be included to report the status of the PCC/QoS rules related to the media component. + +The Content-Version AVP(s) shall be included if it was included in the Media-Component-Description AVP when the corresponding media component was provisioned. + +AVP Format: + +``` +Flows ::= < AVP Header: 510 > + {Media-Component-Number} + * [Flow-Number] + * [ Content-Version ] + [Final-Unit-Action] + [Media-Component-Status] + * [AVP] +``` + +### 5.3.11 Flow-Status AVP + +The Flow-Status AVP (AVP code 511) is of type Enumerated, and describes whether the IP flow(s) are enabled or disabled. The following values are defined: + +ENABLED-UPLINK (0) + +This value shall be used to enable associated uplink IP flow(s) and to disable associated downlink IP flow(s). + +ENABLED-DOWNLINK (1) + +This value shall be used to enable associated downlink IP flow(s) and to disable associated uplink IP flow(s). + +#### ENABLED (2) + +This value shall be used to enable all associated IP flow(s) in both directions. + +#### DISABLED (3) + +This value shall be used to disable all associated IP flow(s) in both directions. + +#### REMOVED (4) + +This value shall be used to remove all associated IP flow(s). The IP Filters for the associated IP flow(s) shall be removed. The associated IP flows shall not be taken into account when deriving the authorized QoS. + +NOTE 1: The interpretation of values for the RTCP flows in the Rx interface is described within the procedures in clause 4.4.3. + +NOTE 2: The interpretation of values for IMS flows when SIP Forking is supported is described within the procedures in Annex A.3.1. + +### 5.3.12 Flow-Usage AVP + +The Flow-Usage AVP (AVP code 512) is of type Enumerated, and provides information about the usage of IP Flows. The following values are defined: + +#### NO\_INFORMATION (0) + +This value is used to indicate that no information about the usage of the IP flow is being provided. + +#### RTCP (1) + +This value is used to indicate that an IP flow is used to transport RTCP. + +#### AF\_SIGNALLING (2) + +This value is used to indicate that the IP flow is used to transport AF Signalling Protocols (e.g. SIP/SDP). + +NO\_INFORMATION is the default value. + +NOTE: An AF may choose not to identify RTCP flows, e.g. in order to avoid that RTCP flows are always enabled by the server. + +### 5.3.13 Specific-Action AVP + +The Specific-Action AVP (AVP code 513) is of type Enumerated. + +Within a PCRF initiated Re-Authorization Request, the Specific-Action AVP determines the type of the action. + +Within an initial AA request the AF may use the Specific-Action AVP to request any specific actions from the server at the bearer events and to limit the contact to such bearer events where specific action is required. If the Specific-Action AVP is omitted within the initial AA request, no notification of any of the events defined below is requested at this time. + +For one time specific actions, as identified in the value descriptions below, the AF may also provide the Specific-Action AVP with the applicable one-time-specific-action value(s) in subsequent AA-Requests. Non-one-time-specific-action value(s) may only be provided in the initial AA-Request and shall then be applicable for the entire lifetime of the Rx session. + +NOTE 1: One time specific actions are reported once the required action is fulfilled and are not reported again unless the AF sends a new request. + +NOTE 2: Unless otherwise stated in the definition of the specific action value, when the AF requests specific actions in the initial AA-Request, the PCRF reports that action whenever new related information is available during the lifetime of the Rx session. + +NOTE 2a: Whether the PCRF decides to report INDICATION\_OF\_RELEASE\_OF\_BEARER (4) or INDICATION\_OF\_FAILED\_RESOURCES\_ALLOCATION (9) upon receipt of a bearer failure from the PCEF is left to the implementation. + +The following values are defined: + +Void (0) + +#### CHARGING\_CORRELATION\_EXCHANGE (1) + +Within a RAR, this value shall be used when the server reports the access network charging identifier to the AF. The Access-Network-Charging-Identifier AVP shall be included within the request. In the AAR, this value indicates that the AF requests the server to provide the access network charging identifier to the AF for each authorized flow, when the access network charging identifier becomes known at the PCRF. + +#### INDICATION\_OF\_LOSS\_OF\_BEARER (2) + +Within a RAR, this value shall be used when the server reports a loss of a bearer (in the case of GPRS PDP context bandwidth modification to 0 kbit for GBR bearers) to the AF. The SDFs that are deactivated as a consequence of this loss of bearer shall be provided within the Flows AVP. In the AAR, this value indicates that the AF requests the server to provide a notification at the loss of a bearer. + +#### INDICATION\_OF\_RECOVERY\_OF\_BEARER (3) + +Within a RAR, this value shall be used when the server reports a recovery of a bearer (in the case of 3GPP-GPRS or 3GPP-EPS when PGW interoperates with a Gn/Gp SGSN, PDP context bandwidth modification from 0 kbit to another value for GBR bearers) to the AF. The SDFs that are re-activated as a consequence of the recovery of bearer shall be provided within the Flows AVP. In the AAR, this value indicates that the AF requests the server to provide a notification at the recovery of a bearer. + +#### INDICATION\_OF\_RELEASE\_OF\_BEARER (4) + +Within a RAR, this value shall be used when the server reports the release of a bearer (e.g. PDP context removal for 3GPP-GPRS or bearer/PDP context removal for 3GPP-EPS) to the AF. The SDFs that are deactivated as a consequence of this release of bearer shall be provided within the Flows AVP. In the AAR, this value indicates that the AF requests the server to provide a notification at the removal of a bearer. The content version corresponding to the affected media component may be provided in the Content-Version AVP included within the Flows AVP. + +Void (5) + +#### IP-CAN\_CHANGE (6) + +This value shall be used in RAR command by the PCRF to indicate a change in the IP-CAN type or RAT type (if applicable). When used in an AAR command, this value indicates that the AF is requesting subscription to IP-CAN change and RAT change notification. When used in RAR it indicates that the PCRF generated the request because of an IP-CAN or RAT change. IP-CAN-Type AVP, RAT-Type AVP (if applicable), AN-Trusted AVP (if applicable) and AN-GW-Address AVP (if applicable) shall be provided in the same request with the new/valid value(s). + +If an IP-CAN type or RAT type change is due to IP flow mobility and a subset of the flows within the AF session is affected, the affected service data flows shall be provided in the same request. + +If ATSSS feature is supported, and the PDU session is a MA PDU session, the PCF may include the MA-Information AVP in the RAR command with the additional/released IP-CAN type and RAT type (if applicable), with the new/valid values as described in clause E.4. + +#### INDICATION\_OF\_OUT\_OF\_CREDIT (7) + +Within a RAR, this value shall be used when the PCRF reports to the AF that SDFs have run out of credit, and that the termination action indicated by the corresponding Final-Unit-Action AVP applies (3GPP TS 32.240 [23] and 3GPP TS 32.299 [24]). The SDFs that are impacted as a consequence of the out of credit condition shall be provided within the Flows AVP. In the AAR, this value indicates that the AF requests the PCRF to provide a notification of SDFs for which credit is no longer available. Applicable to functionality introduced with the Rel8 feature as described in clause 5.4.1. + +#### INDICATION\_OF\_SUCCESSFUL\_RESOURCES\_ALLOCATION (8) + +Within a RAR, this value shall be used by the PCRF to indicate that the resources requested for particular service information have been successfully allocated. The SDFs corresponding to the resources successfully allocated shall be provided within the Flows AVP and the content version within the Content-Version AVP as included when the corresponding media component was provisioned. + +In the AAR, this value indicates that the AF requests the PCRF to provide a notification when the resources associated to the corresponding service information have been allocated. + +Applicable to functionality introduced with the Rel8 feature as described in clause 5.4.1. + +NOTE 3: This value applies to applications for which the successful resource allocation notification is required for their operation since subscription to this value impacts the resource allocation signalling overhead towards the PCEF/BBERF. + +#### INDICATION\_OF\_FAILED\_RESOURCES\_ALLOCATION (9) + +Within a RAR, this value shall be used by the PCRF to indicate that the resources requested for a particular service information cannot be successfully allocated. The SDFs corresponding to the resources that could not be allocated shall be provided within the Flows AVP. In case of session modification failure, the status of the related service information may be reported in the Media-Component-Status AVP included within the Flows AVP and the content version within the Content-Version AVP as included when the corresponding media component was provisioned. + +In the AAR, this value indicates that the AF requests the PCRF to provide a notification when the resources associated to the corresponding service information cannot be allocated. Applicable to functionality introduced with the Rel8 feature as described in clause 5.4.1. + +NOTE 4: This value applies to applications for which the unsuccessful resource allocation notification is required for their operation since subscription to this value impacts the resource allocation signalling overhead towards the PCEF/BBERF. + +#### INDICATION\_OF\_LIMITED\_PCC\_DEPLOYMENT (10) + +Within a RAR, this value shall be used when the PCRF reports the limited PCC deployment (i.e. dynamically allocated resources are not applicable) as specified at Annex K and Annex L in 3GPP TS 23.203 [2] to the AF. In the AAR, this value indicates that the AF requests the PCRF to provide a notification for the limited PCC deployment. Applicable to functionality introduced with the Rel8 feature as described in clause 5.4.1. + +#### USAGE\_REPORT (11) + +In the RA-Request (RAR), this value shall be used by the PCRF to report accumulated usage volume and/or time of usage when the usage threshold provided by the AF has been reached. + +In the AA-Request (AAR), this value indicates that the AF requests PCRF to report accumulated usage volume and /or time of usage when it reaches the threshold. + +Applicable to functionality introduced with the SponsoredConnectivity feature for volume usage reporting and with SCTimeBased UM feature for time usage reporting as described in clause 5.4.1. + +#### ACCESS\_NETWORK\_INFO\_REPORT (12) + +In the RA-Request (RAR), this value shall be used by the PCRF to report access network information (i.e. user location and/or user timezone information) when the PCRF receiving an Access Network Information report corresponding to the AF session from the PCEF/BBERF. + +In the AA-Request (AAR), this value indicates that the AF requests PCRF to report one time access network information when the PCRF receives the first Access Network Information report corresponding to the AF session from the PCEF/BBERF after the AF request for the access network information. The required access information is provided within the Required-Access-Info AVP. Applicable to functionality introduced with the NetLoc feature as described in clause 5.4.1. + +The Specific-Action AVP with this value indicates a one time specific action. + +##### INDICATION\_OF\_RECOVERY\_FROM\_LIMITED\_PCC\_DEPLOYMENT (13) + +Within a RAR, this value shall be used when the PCRF reports the recovery from limited PCC deployment (i.e. the UE moves from the VPLMN to the HPLMN as specified at Annex K in 3GPP TS 23.203 [2]) to the AF. In the AAR, this value indicates that the AF requests the PCRF to provide a notification for the recovery from limited PCC deployment. Applicable to functionality introduced with the Rel8 feature as described in clause 5.4.1. + +NOTE 5: This value is optional and only applicable to the scenario where PCC is deployed in the HPLMN but not in the VPLMN and dynamic policy provisioning only occurs in the home routed roaming cases if no BBERF is employed. + +#### INDICATION\_OF\_ACCESS\_NETWORK\_INFO\_REPORTING\_FAILURE (14) + +In the RAR, this value shall be used when the PCRF reports the access network information reporting failure. When applicable, the NetLoc-Access-Support AVP may be provided as well to indicate the reason for the access network information reporting failure. This specific action does not require to be provisioned by the AF. Applicable to functionality introduced with the NetLoc feature as described in clause 5.4.1. + +#### INDICATION\_OF\_TRANSFER\_POLICY\_EXPIRED (15) + +In the RAR, this value shall be used when the PCRF determines that the transfer policy has expired. This specific action does not require to be provisioned by the AF. + +#### PLMN\_CHANGE (16) + +In the AA-Request (AAR), this value indicates that the AF requests PCRF to report changes of PLMN. In the RA-Request (RAR), this value shall be used by the PCRF to indicate that there was a change of PLMN. 3GPP-SGSN-MCC-MNC AVP shall be provided in the same RAR command with the new value and, if available, the NID AVP. Applicable to functionality introduced with the PLMNInfo feature as described in clause 5.4.1. + +The NID AVP is only applicable in 5GS when the serving network is an SNPN, as described in Annex E. + +#### EPS\_FALLBACK (17) + +In the RA-Request (RAR), this value shall be used to report EPS Fallback for the resources requested for a particular service information (media type voice). + +In the AA-Request (AAR), this value indicates that the AF requests to provide a notification when the access network initiates EPS Fallback for the requested resources associated to service information for voice media type. + +Applicable to functionality introduced with the EPSFallbackReport feature as described in clause 5.4.1. + +This value is only applicable to 5GS as described in Annex E. + +#### INDICATION\_OF\_REALLOCATION\_OF\_CREDIT (18) + +Within a RAR, this value shall be used to report to the AF the SDFs for which credit has been reallocated after the former out of credit indication (3GPP TS 32.240 [23] and 3GPP TS 32.299 [24]). The SDFs that are impacted as a consequence of the reallocation of credit condition shall be provided within the Flows AVP. In the AAR, this value indicates the AF requests to provide a notification of SDFs for which credit has been reallocated after the former out of credit indication. Applicable to functionality introduced with the ReallocationOfCredit feature as described in clause 5.4.1. + +This value is only applicable to 5GS as described in Annex E. + +#### SUCCESSFUL\_QOS\_UPDATE (19) + +Within a RAR, this value shall be used by the PCRF to indicate that the QoS of the default bearer has been successfully updated. + +In the AAR, this value indicates that the AF requests the PCRF to provide a notification when the QoS of the default bearer has been successfully updated. + +Applicable to functionality introduced with the MPSforDTS feature as described in clause 5.4.1. + +##### FAILED\_QOS\_UPDATE (20) + +Within a RAR, this value shall be used by the PCRF to indicate that the QoS of the default bearer has failed to update. + +In the AAR, this value indicates that the AF requests the PCRF to provide a notification when the QoS of the default bearer has failed to update. + +Applicable to functionality introduced with the MPSforDTS feature as described in clause 5.4.1. + +### 5.3.14 Max-Requested-Bandwidth-DL AVP + +The Max-Requested-Bandwidth-DL AVP (AVP code 515) is of type Unsigned32, and it indicates the maximum bandwidth in bits per second for a downlink IP flow. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. + +When provided in an AA-Request, it indicates the maximum requested bandwidth. When provided in an AA-Answer, it indicates the maximum bandwidth acceptable by PCRF. + +When the Extended-Max-Requested-BW-NR feature is supported and the value to be transmitted exceeds $2^{32}-1$ , the Extended-Max-Requested-Bandwidth-DL AVP shall be used, see clause 4.4.10 and clause 5.3.52. + +### 5.3.15 Max-Requested-Bandwidth-UL AVP + +The Max -Bandwidth-UL AVP (AVP code 516) is of type Unsigned32, and it indicates the maximum requested bandwidth in bits per second for an uplink IP flow. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. + +When provided in an AA-Request, it indicates the maximum requested bandwidth. When provided in an AA-Answer, it indicates the maximum bandwidth acceptable by PCRF. + +When the Extended-Max-Requested-BW-NR feature is supported and the value to be transmitted exceeds $2^{32}-1$ , the Extended-Max-Requested-Bandwidth-UL AVP shall be used, see clause 4.4.10 and clause 5.3.53. + +### 5.3.16 Media-Component-Description AVP + +The Media-Component-Description AVP (AVP code 517) is of type Grouped, and it contains service information for a single media component within an AF session or the AF signalling information. The service information may be based on the SDI exchanged between the AF and the AF session client in the UE. The information may be used by the PCRF to determine authorized QoS and IP flow classifiers for bearer authorization and PCC rule selection. + +Within one Diameter message, a single IP flow shall not be described by more than one Media-Component-Description AVP. + +Bandwidth information and Flow-Status information provided within the Media-Component-Description AVP applies to all those IP flows within the media component, for which no corresponding information is being provided within Media-Sub-Component AVP(s). As defined in 3GPP TS 29.213 [9], the bandwidth information within the media component level Max-Requested-Bandwidth-DL and Max-Requested-Bandwidth-UL AVPs applies separately to each media subcomponent except for RTCP media subcomponent. + +The mapping of bandwidth information for RTCP media subcomponent is defined in 3GPP TS 29.213 [9] clause 6.2. + +If CHEM feature is supported, Max-PLR-DL AVP and Max-PLR-UL AVP information is provided within the Media-Component-Description AVP as defined in 3GPP TS 29.213 [9]. + +If the QoSHint feature is supported the Desired-Max-Latency AVP and/or Desired-Max-Loss AVP may be provided within the Media-Component-Description AVP as defined in 3GPP TS 29.213 [9]. + +If FLUS feature is supported the FLUS-Identifier AVP may be provided within the Media-Component-Description AVP. Additionally, the Desired-Max-Latency AVP and/or the Desired-Max-Loss AVP may be provided as defined in 3GPP TS 29.213 [9]. + +The Max-Requested-Bandwidth-UL, Max-Requested-Bandwidth-DL, Max-Supported-Bandwidth-UL, Max-Supported-Bandwidth-DL, Min-Desired-Bandwidth-UL, Min-Desired-Bandwidth-DL, Min-Requested-Bandwidth-UL and Min-Requested-Bandwidth-DL AVPs only represent bandwidth values up $2^{32}-1$ bps. To represent higher values, the + +Extended-Max-Requested-Bandwidth-UL, Extended-Max-Requested-Bandwidth-DL, Extended-Max-Supported-Bandwidth-UL, Extended-Max-Supported-Bandwidth-DL, Extended-Min-Desired-Bandwidth-UL, Extended-Min-Desired-Bandwidth-DL, Extended-Min-Requested-Bandwidth-UL and Extended-Min-Requested-Bandwidth-DL AVPs may be used as described in clause 4.4.10. + +If a Media-Component-Description AVP is not supplied by the AF, or if optional AVP(s) within a Media-Component-Description AVP are omitted, but corresponding information has been provided in previous Diameter messages, the previous information for the corresponding IP flow(s) remains valid. + +All IP flows within a Media-Component-Description AVP are permanently disabled by supplying a Flow Status AVP with value "REMOVED". The server may delete corresponding filters and state information. + +Reservation-Priority provided within the Media-Component-Description AVP in the request from the AF applies to all those IP flows within the media component and describes the relative importance of the IP flow as compared to other IP flows. The PCRF may use this value to implement priority based admission. If the Reservation-Priority AVP is not specified the IP flow priority is DEFAULT (0). + +Each Media-Component-Description AVP shall contain either zero, or one, or two Codec-Data AVPs. In the case of conflicts, information contained in other AVPs either within this Media-Component-Description AVP, or within the corresponding Media-Component-Description AVP in a previous message, shall take precedence over information within the Codec-Data AVP(s). The AF shall provision all the available information in other applicable AVPs in addition to the information in the Codec-Data AVP, if such other AVPs are specified. + +If the SDP offer-answer procedures of IETF RFC 3264 [18] are applicable for the session negotiation between the two ends taking part in the communication (e.g. for IMS), the following applies: + +- The AF shall provision information derived from an SDP answer and shall also provision information derived from the corresponding SDP offer. +- If the Media-Component-Description AVP contains two Codec-Data AVPs, one of them shall represent an SDP offer and the other one the corresponding SDP answer. +- If the Media-Component-Description AVP contains one Codec-Data AVP, and this AVP represents an SDP offer, the AF shall provision the corresponding SDP answer information in a Codec-Data AVP within a subsequent Rx message. + +NOTE 1: Some SDP parameters for the same codec in the SDP offer and answer are independent of each other and refer to IP flows in opposite directions, for instance some MIME parameters conveyed within "a=fmtp" SDP lines and the packetization time within the "a=ptime" line. Other parameters within the SDP answer take precedence over corresponding parameters within the SDP offer. + +If SDP is applied without using the offer-answer procedures, zero or one Codec-Data AVP shall be provisioned. + +Sharing-Key-DL AVP and/or Sharing-Key-UL AVP provided within the Media-Component-Description AVP indicates that the media components that include the same value of the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP may share resources in the related direction. + +NOTE 2: RTCP traffic is not subject to resource sharing. + +The Content-Version AVP may be included in order to indicate the content version of a media component. + +The Priority-Sharing-Indicator AVP may be included to indicate that the media component can use the same Allocation and Retention Priority as media flows which are assigned the same QCI in the PCRF belonging to other AF sessions for the same IP-CAN session that also contain the Priority-Sharing-Indicator AVP. + +The Pre-emption-Capability AVP and Pre-emption-Vulnerability AVP may be included together with Priority-Sharing-Indicator AVP for PCRF Allocation and Retention Priority decision. + +The PCRF may provide the Media-Component-Description AVP(s) within the Acceptable-Service-Info AVP in the AA-Answer command if the service information received from the AF is rejected. For this usage, the Media-Component-Description AVP shall only include the appropriate Media-Component-Number AVP and the Max-Requested-Bandwidth-UL and/or Max-Requested-Bandwidth-DL AVPs and/ or the Extended-Max-Requested-BW-UL AVP and/or the Extended-Max-Requested-BW-DL AVP (see clause 4.4.10) indicating the maximum acceptable bandwidth. + +AVP format: + +``` +Media-Component-Description ::= < AVP Header: 517 > + { Media-Component-Number } ; Ordinal number of the media comp. + *[ Media-Sub-Component ] ; Set of flows for one flow identifier + [ AF-Application-Identifier ] + [ FLUS-Identifier ] + [ Media-Type ] + [ Max-Requested-Bandwidth-UL ] + [ Max-Requested-Bandwidth-DL ] + [ Max-Supported-Bandwidth-UL ] + [ Max-Supported-Bandwidth-DL ] + [ Min-Desired-Bandwidth-UL ] + [ Min-Desired-Bandwidth-DL ] + [ Min-Requested-Bandwidth-UL ] + [ Min-Requested-Bandwidth-DL ] + [ Extended-Max-Requested-BW-UL ] + [ Extended-Max-Requested-BW-DL ] + [ Extended-Max-Supported-BW-UL ] + [ Extended-Max-Supported-BW-DL ] + [ Extended-Min-Desired-BW-UL ] + [ Extended-Min-Desired-BW-DL ] + [ Extended-Min-Requested-BW-UL ] + [ Extended-Min-Requested-BW-DL ] + [ Flow-Status ] + [ Priority-Sharing-Indicator ] + [ Pre-emption-Capability ] + [ Pre-emption-Vulnerability ] + [ Reservation-Priority ] + [ RS-Bandwidth ] + [ RR-Bandwidth ] + 0*2[ Codec-Data ] + [ Sharing-Key-DL ] + [ Sharing-Key-UL ] + [ Content-Version ] + [ Max-PLR-DL ] + [ Max-PLR-UL ] + [ Desired-Max-Latency ] + [ Desired-Max-Loss ] + *[ AVP ] +``` + +### 5.3.17 Media-Component-Number AVP + +The Media-Component-Number AVP (AVP code 518) is of type Unsigned32, and it contains the ordinal number of the media component, assigned according to the rules in Annex B. + +When this AVP refers to AF signalling, this is indicated by using the value 0 according to the rules in Annex B. + +### 5.3.18 Media-Sub-Component AVP + +The Media-Sub-Component AVP (AVP code 519) is of type Grouped, and it contains the requested bitrate and filters for the set of IP flows identified by their common Flow-Identifier. The Flow-Identifier is defined in Annex B. + +Possible Bandwidth information and Flow-Status information provided within the Media-Sub-Component AVP takes precedence over information within the encapsulating Media Component Description AVP. If a Media-Sub-Component AVP is not supplied, or if optional AVP(s) within a Media-Sub-Component AVP are omitted, but corresponding information has been provided in previous Diameter messages, the previous information for the corresponding IP flow(s) remains valid, unless new information is provided within the encapsulating Media-Component-Description AVP. If Flow-Description AVP(s) are supplied, they replace all previous Flow-Description AVP(s), even if a new Flow-Description AVP has the opposite direction as the previous Flow-Description AVP. The AF may also include the ToS-Traffic-Class AVP for requesting Type of Service or Traffic Class (for IPv4 and IPv6 respectively) based packet filter for the related flow. + +The AF-Signalling-Protocol AVP may be included only if the Flow-Usage AVP has a value of 'AF\_SIGNALLING'. + +All IP flows within a Media-Sub-Component AVP are permanently disabled by supplying a Flow Status AVP with value "REMOVED". The server may delete corresponding filters and state information. + +AVP format: + +``` + +Media-Sub-Component ::= < AVP Header: 519 > + { Flow-Number } ; Ordinal number of the IP flow + 0*2 [ Flow-Description ] ; UL and/or DL + [ Flow-Status ] + [ Flow-Usage ] + [ Max-Requested-Bandwidth-UL ] + [ Max-Requested-Bandwidth-DL ] + [ Extended-Max-Requested-BW-UL ] + [ Extended-Max-Requested-BW-DL ] + [ AF-Signalling-Protocol ] + [ ToS-Traffic-Class ] + *[ AVP ] + +``` + +### 5.3.19 Media-Type AVP + +The Media-Type AVP (AVP code 520) is of type Enumerated, and it determines the media type of a session component. The media types indicate the type of media in the same way as the SDP media types with the same names defined in RFC 4566 [13]. The following values are defined: + +- AUDIO (0) +- VIDEO (1) +- DATA (2) +- APPLICATION (3) +- CONTROL (4) +- TEXT (5) +- MESSAGE (6) +- OTHER (0xFFFFFFFF) + +### 5.3.20 RR-Bandwidth AVP + +The RR-Bandwidth AVP (AVP code 521) is of type Unsigned32, and it indicates the maximum required bandwidth in bits per second for RTCP receiver reports within the session component, as specified in IETF RFC 3556 [11]. The bandwidth contains all the overhead coming from the IP-layer and the layers above, i.e. IP, UDP and RTCP. + +### 5.3.21 RS-Bandwidth AVP + +The RS-Bandwidth AVP (AVP code 522) is of type Unsigned32, and it indicates the maximum required bandwidth in bits per second for RTCP sender reports within the session component, as specified in RFC 3556 [11]. The bandwidth contains all the overhead coming from the IP-layer and the layers above, i.e. IP, UDP and RTCP. + +### 5.3.22 SIP-Forking-Indication AVP + +The SIP-Forking-Indication AVP (AVP code 523) is of type Enumerated, and describes if several SIP dialogues are related to one Diameter session: + +SINGLE\_DIALOGUE (0) + +This value is used to indicate that the Diameter session relates to a single SIP dialogue. +This is the default value applicable if the AVP is omitted. + +SEVERAL\_DIALOGUES (1) + +This value is used to indicate that the Diameter session relates to several SIP dialogues. + +### 5.3.23 Service-URN AVP + +The Service-URN AVP (AVP code 525) is of type OctetString, and it indicates that an AF session is used for emergency or RLOS traffic. + +It contains values of the service URN and it may include subservices, as defined in [21] for emergency and other well-known services or registered at IANA. The string "urn:service:" in the beginning of the URN shall be omitted in the AVP and all subsequent text shall be included. Examples of valid values of the AVP are "sos", "sos.fire", "sos.police" and "sos.ambulance". + +### 5.3.24 Acceptable-Service-Info AVP + +The Acceptable-Service-Info AVP (AVP code 526) is of type Grouped, and contains the maximum bandwidth for an AF session and/or for specific media components that will be authorized by the PCRF. The Max-Requested-Bandwidth-DL AVP, the Max-Requested-Bandwidth-UL AVP, the Extended-Max-Requested-BW-DL AVP and the Extended-Max-Requested-BW-UL AVP (see clause 4.4.10) directly within the Acceptable-Service-Info AVP indicate the acceptable bandwidth for the entire AF session. The Max-Requested-Bandwidth-DL AVP, Max-Requested-Bandwidth-UL AVP, Extended-Max-Requested-BW-DL AVP and Extended-Max-Requested-BW-UL AVP within a Media-Component-Description AVP included in the Acceptable-Service-Info AVP indicate the acceptable bandwidth for the corresponding media component. + +If the acceptable bandwidth applies to one or more media components, only the Media-Component-Description AVP will be provided. If the acceptable bandwidth applies to the whole AF session, only the Max-Requested-Bandwidth-DL AVP, the Max-Requested-Bandwidth-UL AVP, the Extended-Max-Requested-BW-DL AVP and the Extended-Max-Requested-BW-UL AVP will be included. + +``` +Acceptable-Service-Info ::= < AVP Header: 526 > + *[ Media-Component-Description ] + [ Max-Requested-Bandwidth-DL ] + [ Max-Requested-Bandwidth-UL ] + [ Extended-Max-Requested-BW-DL ] + [ Extended-Max-Requested-BW-UL ] + *[ AVP ] +``` + +### 5.3.25 Service-Info-Status-AVP + +The Service-Info-Status AVP (AVP code 527) is of type Enumerated, and indicates the status of the service information that the AF is providing to the PCRF. If the Service-Info-Status AVP is not provided in the AA request, the value FINAL SERVICE INFORMATION shall be assumed. + +#### FINAL SERVICE INFORMATION (0) + +This value is used to indicate that the service has been fully negotiated between the two ends and service information provided is the result of that negotiation. + +#### PRELIMINARY SERVICE INFORMATION (1) + +This value is used to indicate that the service information that the AF has provided to the PCRF is preliminary and needs to be further negotiated between the two ends (e.g. for IMS when the service information is sent based on the SDP offer). + +### 5.3.26 AF-Signalling-Protocol-AVP + +The AF-Signalling-Protocol AVP (AVP code 529) is of type Enumerated, and indicates the protocol used for signalling between the UE and the AF. If the AF-Signalling-Protocol AVP is not provided in the AA-Request, the value NO\_INFORMATION shall be assumed. + +#### NO\_INFORMATION (0) + +This value is used to indicate that no information about the AF signalling protocol is being provided. + +#### SIP (1) + +This value is used to indicate that the signalling protocol is Session Initiation Protocol. + +### 5.3.27 Sponsored-Connectivity-Data AVP + +The Sponsored-Connectivity-Data AVP (AVP code 530) is of type Grouped, and contains the data associated with the sponsored data connectivity. + +The Sponsor-Identity AVP identifies the sponsor. It shall be included by the AF in the Sponsored-Connectivity-Data AVP except for the case of disabling sponsored data connectivity. + +The Application-Service-Provider-Identity AVP identifies the application service provider. It shall be included by the AF in the Sponsored-Connectivity-Data AVP except for the case of disabling sponsored data connectivity. + +The Granted-Service-Unit AVP shall be used by the AF to provide usage threshold to the PCRF if the volume and/or time of traffic allowed during the sponsored data connectivity is to be monitored. + +The Used-Service-Unit AVP shall be used by the PCRF to provide the measured usage to the AF. Reporting shall be done, as requested by the AF, in CC-Total-Octets, CC-Input-Octets, CC-Output-Octets or CC-Time of the Used-Service-Unit AVP. + +Sponsoring-Action AVP shall be used by the AF to provide the indication to the PCRF if sponsored data connectivity is to be enabled or disabled. + +AVP format: + +``` +Sponsored-Connectivity-Data ::= < AVP Header: 530 > + [ Sponsor-Identity ] + [ Application-Service-Provider-Identity ] + [ Granted-Service-Unit ] + [ Used-Service-Unit ] + [ Sponsoring-Action ] + *[ AVP ] +``` + +### 5.3.28 Sponsor-Identity AVP + +The Sponsor-Identity AVP (AVP code 531) is of type UTF8String and is used for sponsored data connectivity purposes as an identifier of the sponsor. + +### 5.3.29 Application-Service-Provider-Identity AVP + +The Application-Service-Provider-Identity AVP (AVP code 532) is of type UTF8String and is used for sponsored data connectivity purposes as an identifier of the application service provider. + +### 5.3.30 MPS-Identifier AVP + +The MPS-Identifier AVP (AVP code 528) is of type OctetString, and it indicates that an AF session relates to an MPS session. It contains the national variant for MPS service name (e.g., NGN GETS). + +### 5.3.31 Rx-Request-Type AVP + +The Rx-Request-Type AVP (AVP code 533) is of type Enumerated, and contains the reason for sending the AA-Request message. + +The following values are defined: + +INITIAL\_REQUEST (0) + +An initial request is used to initiate an Rx session and contains information that is relevant to initiation. + +UPDATE\_REQUEST (1) + +An update request is used to update an existing Rx session. + +PCSCF\_RESTORATION (2) + +A P-CSCF Restoration is requested. This value is only applicable to the PCSCF-Restoration-Enhancement feature defined in clause 5.4.1. + +### 5.3.32 Min-Requested-Bandwidth-DL AVP + +The Min-Requested-Bandwidth-DL AVP (AVP code 534) is of type Unsigned32, and it indicates the minimum requested bandwidth in bits per second for a downlink IP flow. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, TCP, UDP, HTTP, RTP and RTP payload. + +When provided in an AA-Request, it indicates the minimum requested bandwidth. + +When the Extended-Min-Requested-BW-NR feature is supported and the value to be transmitted exceeds $2^{32}-1$ , the Extended-Min-Requested-Bandwidth-DL AVP shall be used, see clause 4.4.10 and clause 5.3.58. + +### 5.3.33 Min-Requested-Bandwidth-UL AVP + +The Min-Requested-Bandwidth-UL AVP (AVP code 535) is of type Unsigned32, and it indicates the minimum requested bandwidth in bits per second for an uplink IP flow. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, TCP, UDP, HTTP, RTP and RTP payload. + +When provided in an AA-Request, it indicates the minimum requested bandwidth. + +When the Extended-Min-Requested-BW-NR feature is supported and the value to be transmitted exceeds $2^{32}-1$ , the Extended-Min-Requested-Bandwidth-UL AVP shall be used, see clause 4.4.10 and clause 5.3.59. + +### 5.3.34 Required-Access-Info AVP + +The Required-Access-Info AVP (AVP code 536) is of type Enumerated, and contains the access network information required for that AF session. + +The following values are defined: + +#### USER\_LOCATION (0) + +Indicates that the user location information shall be reported, the PCRF shall report the user location information within the 3GPP-User-Location-Info AVP (if available), the serving network identifier containing PLMN identifier within the 3GPP-SGSN-MCC-MNC AVP (if available) and NID AVP (if available), the user location information within the TWAN-Identifier (if available) , UE-Local-IP-Address AVP (if available) , UDP-Source-Port AVP (if available), TCP-Source-Port AVP (if available) and User-Location-Info-Time AVP (if available). + +The NID AVP is only applicable in 5GS when the serving network is an SNPn, as described in Annex E. + +#### MS\_TIME\_ZONE (1) + +Indicates that the user timezone information shall be reported, the PCRF shall report the user timezone information within the 3GPP-MS-TimeZone AVP. + +### 5.3.35 IP-Domain-Id AVP + +The IP-Domain-Id AVP (AVP code 537) is of type (OctetString), and indicates the domain information which assists session binding. + +### 5.3.36 GCS-Identifier AVP + +The GCS-Identifier AVP (AVP code 538) is of type OctetString, and it indicates that an AF session relates to a Group Communication session that requires prioritization. The values that identify the Group Communication session are not specified. + +### 5.3.37 Sharing-Key-DL AVP + +The Sharing-Key-DL AVP (AVP code 539) is of type Unsigned32 and is used to identify what media components may share resource in the downlink direction. + +The Sharing-Key-DL AVP shall be used as follows: + +- If resource sharing applies between media components across AF sessions for the same user, the same value of the Sharing-Key-DL AVP shall be used; +- If resource sharing does not apply between media components across AF sessions for the same user, a different value of the Sharing-Key-DL AVP shall be used for each media component. + +### 5.3.38 Sharing-Key-UL AVP + +The Sharing-Key-UL AVP (AVP code 540) is of type Unsigned32 and is used to identify what media components may share resource in the uplink direction. + +The Sharing-Key-UL AVP shall be used as follows: + +- If resource sharing applies between media components across AF sessions for the same user, the same value of the Sharing-Key-UL AVP shall be used; +- If resource sharing does not apply between media components across AF sessions for the same user, a different value of the Sharing-Key-UL AVP shall be used for each media component. + +### 5.3.39 Retry-Interval AVP + +The Retry-Interval AVP (AVP code 541) is of type Unsigned32, and it indicates a time interval in seconds to wait until which the AF retries to send the same service information to the PCRF (for the same IP-CAN session) when the service information is temporarily rejected by the PCRF (e.g. due to the detected congestion status of the cell the user is located in). + +### 5.3.40 Sponsoring-Action AVP + +The Sponsoring-Action AVP (AVP code 542) is of type Enumerated, and contains the indication whether to enable or disable/not enable sponsored data connectivity. + +The following values are defined: + +DISABLE\_SPONSORING (0) + +Disable sponsored data connectivity or not enable sponsored data connectivity + +ENABLE\_SPONSORING (1) + +Enable sponsored data connectivity. + +NOTE: The use of value DISABLE\_SPONSORING (0) to "not enable" sponsored data connectivity is used at initial provisioning of session information to provide sponsor information but not enable it at that point in time and to "disable" sponsored data connectivity is used at modification of session information when disabling sponsored data connectivity previously enabled. + +### 5.3.41 Max-Supported-Bandwidth-DL AVP + +The Max-Supported-Bandwidth-DL AVP (AVP code 543) is of type Unsigned32, and it indicates the maximum supported bandwidth in bits per second for a downlink IP flow as defined in 3GPP TS 26.114 [41]. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. + +When the Extended-BW-E2EQOSMTSI-NR feature is supported and the value to be transmitted exceeds $2^{32}-1$ , the Extended-Max-Supported-Bandwidth-DL AVP shall be used, see clause 4.4.10 and clause 5.3.54. + +### 5.3.42 Max-Supported-Bandwidth-UL AVP + +The Max-Supported-Bandwidth-UL AVP (AVP code 544) is of type Unsigned32, and it indicates the maximum supported bandwidth in bits per second for an uplink IP flow as defined in 3GPP TS 26.114 [41]. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. + +When the Extended-BW-E2EQOSMTSI-NR feature is supported and the value to be transmitted exceeds $2^{32}-1$ , the Extended-Max-Supported-Bandwidth-UL AVP shall be used, see clause 4.4.10 and clause 5.3.55. + +### 5.3.43 Min-Desired-Bandwidth-DL AVP + +The Min-Desired-Bandwidth-DL AVP (AVP code 545) is of type Unsigned32, and it indicates the minimum desired bandwidth in bits per second for a downlink IP flow as defined in 3GPP TS 26.114 [41]. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. + +When the Extended-BW-E2EQOSMTSI-NR feature is supported and the value to be transmitted exceeds $2^{32}-1$ , the Extended-Min-Desired-Bandwidth-DL AVP shall be used, see clause 4.4.10 and clause 5.3.56. + +### 5.3.44 Min-Desired-Bandwidth-UL AVP + +The Min-Desired-Bandwidth-DL AVP (AVP code 546) is of type Unsigned32, and it indicates the minimum desired bandwidth in bits per second for an uplink IP flow as defined in 3GPP TS 26.114 [41]. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. + +When the Extended-BW-E2EQOSMTSI-NR feature is supported and the value to be transmitted exceeds $2^{32}-1$ , the Extended-Min-Desired-Bandwidth-UL AVP shall be used, see clause 4.4.10 and clause 5.3.57. + +### 5.3.45 MCPTT-Identifier AVP + +The MCPTT-Identifier AVP (AVP code 547) is of type OctetString, and it includes either one of the namespace values used for MCPTT (see IETF RFC 8101 [45]) and it may include the name of the MCPTT service provider. + +### 5.3.45A MCVideo-Identifier AVP + +The MCVideo-Identifier AVP (AVP code 562) is of type OctetString, and it includes the name of the MCVideo service provider. + +### 5.3.46 Service-Authorization-Info AVP + +The Service-Authorization-Info AVP (AVP code 548) is of type Unsigned32, it shall contain a bit mask and indicate the result of the authorization for the service request from the AF. The bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x0001 should be used. The meaning of the bits shall be as defined below: + +**Table 5.3.46: Service-Authorization-Info** + +| Bit | Name | Description | +|-----|--------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| 0 | The transfer policy is known/unknown. | This bit, when set, indicates that the transfer policy is unknown. | +| 1 | The transfer policy has expired/has not expired | This bit, when set, indicates that the transfer policy has expired. | +| 2 | The time window of the transfer policy has occurred/has not yet occurred | This bit, when set, indicates that the time window of the transfer policy has not yet occurred. | + +### 5.3.47 Priority-Sharing-Indicator AVP + +The Priority-Sharing-Indicator AVP (AVP code 550) is of type Enumerated and is used to indicate that the related media component can use the same Allocation and Retention Priority as media component(s) which are assigned the same QCI in the PCRF belonging to other AF sessions for the same IP-CAN session that also contain the Priority-Sharing-Indicator AVP set to PRIORITY\_SHARING\_ENABLED. + +The following values are defined: + +#### **PRIORITY\_SHARING\_ENABLED (0)** + +This value indicates that the related media component is allowed to share the Allocation and Retention Priority with media components belonging to other AF sessions that have also indicated that priority sharing is enabled. + +#### **PRIORITY\_SHARING\_DISABLED (1)** + +This value indicates that the related media component is not allowed to share the Allocation and Retention Priority with media components belonging to other AF sessions. This is the default value applicable if this AVP is not supplied. + +### 5.3.48 Media-Component-Status AVP + +The Media-Component-Status AVP (AVP code 549) is of type Unsigned32, and it describes the status of the PCC/QoS rule(s) related to a media component. + +The following values are defined in this specification: + +#### **0 (ACTIVE):** + +This value shall be used to indicate that the PCC/QoS rule(s) related to certain media component are active. + +##### **1 (INACTIVE):** + +This value shall be used to indicate that the PCC/QoS rule(s) related to certain media component are inactive. This is the default value applicable if this AVP is not supplied. + +**NOTE:** It is assumed that the AF considers the PCC/QoS rule(s) related to the media component(s) for which the Media-Component-Status AVP(s) are not received as inactive when the *Specific-Action AVP* set to **INDICATION\_OF\_FAILED\_RESOURCES\_ALLOCATION (9)** is received. + +### 5.3.49 Content-Version AVP + +The Content-Version AVP (AVP code 552) is of type Unsigned64, and it indicates the version of some content, e.g. of the content of a media component included within the Media-Component-Description AVP. The content version shall be unique for the content and for the lifetime of that content. + +**NOTE:** The method of assigning content versions within the Content-Version AVPs is implementation specific. Example implementations are a monotonically increasing number or a value based on a timestamp. + +### 5.3.50 AF-Requested-Data AVP + +The AF-Requested-Data AVP (AVP code 551) is of type Unsigned32 and indicates the information that the AF requested to be exposed, it shall contain a bit mask. The bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x0001 should be used. The meaning of the bits shall be as defined below: + +**Table 5.3.50.1: AF-Requested-Data** + +| Bit | Name | Description | +|-----|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | EPC-level identities required | This bit, when set, indicates that the AF requests the PCRF to provide the EPC-level identities (MSISDN, IMSI, IMEI(SV)) available for that IP-CAN session. | + +### 5.3.51 Pre-emption-Control-Info AVP + +The Pre-emption-Control-Info (AVP code 553) is of type Unsigned32, it shall contain a bit mask and indicate that how the PCRF to perform pre-emption among multiple potential media flow candidates of same priority. Pre-emption-Control-Info AVP is provided at the AAR command level and the latest provided value within the Pre-emption-Control-Info AVP shall be applied to all potential media flow candidates. The bit 0 shall be the least significant bit. For + +example, to get the value of bit 0, a bit mask of 0x0001 should be used. The meaning of the bits shall be as defined below: + +The following values are defined, only one bit shall be set at the same time: + +**Table 5.3.51: Pre-emption-Control-Info** + +| Bit | Name | Description | +|-----|-------------------------|-------------------------------------------------------------------------------------| +| 0 | Most recent added flow | This bit, when set, indicates that the most recent added flow is to be pre-empted. | +| 1 | Least recent added flow | This bit, when set, indicates that the least recent added flow is to be pre-empted. | +| 2 | Highest bandwidth flow | This bit, when set, indicates that the highest bandwidth flow is to be pre-empted. | + +### 5.3.52 Extended-Max-Requested-BW-DL AVP + +The Extended-Max-Requested-BW-DL AVP (AVP code 554) is of type Unsigned32, and it indicates the maximum requested bandwidth in kbit per second for a downlink IP flow. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. + +When provided in an AA-Request, it indicates the maximum requested bandwidth. When provided in an AA-Answer, it indicates the maximum bandwidth acceptable by PCRF. + +### 5.3.53 Extended-Max-Requested-BW-UL AVP + +The Extended-Max-Requested-BW-UL AVP (AVP code 555) is of type Unsigned32, and it indicates the maximum requested bandwidth in kbit per second for an uplink IP flow. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. + +When provided in an AA-Request, it indicates the maximum requested bandwidth. When provided in an AA-Answer, it indicates the maximum bandwidth acceptable by PCRF. + +### 5.3.54 Extended-Max-Supported-BW-DL AVP + +The Extended-Max-Supported-BW-DL AVP (AVP code 556) is of type Unsigned32, and it indicates the maximum supported bandwidth in kbit per second for a downlink IP flow as defined in 3GPP TS 26.114 [41]. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. + +### 5.3.55 Extended-Max-Supported-BW-UL AVP + +The Extended-Max-Supported-BW-UL AVP (AVP code 557) is of type Unsigned32, and it indicates the maximum supported bandwidth in kbit per second for an uplink IP flow as defined in 3GPP TS 26.114 [41]. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. + +### 5.3.56 Extended-Min-Desired-BW-DL AVP + +The Extended-Min-Desired-BW-DL AVP (AVP code 558) is of type Unsigned32, and it indicates the minimum desired bandwidth in kbit per second for a downlink IP flow as defined in 3GPP TS 26.114 [41]. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. + +### 5.3.57 Extended-Min-Desired-BW-UL AVP + +The Extended-Min-Desired-BW-UL AVP (AVP code 559) is of type Unsigned32, and it indicates the minimum desired bandwidth in kbit per second for an uplink IP flow as defined in 3GPP TS 26.114 [41]. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTP payload. + +### 5.3.58 Extended-Min-Requested-BW-DL AVP + +The Extended-Min-Requested-BW-DL AVP (AVP code 560) is of type Unsigned32, and it indicates the minimum requested bandwidth in kbit per second for a downlink IP flow. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, TCP, UDP, HTTP, RTP and RTP payload. + +When provided in an AA-Request, it indicates the minimum requested bandwidth. + +### 5.3.59 Extended-Min-Requested-BW-UL AVP + +The Extended-Min-Requested-Bandwidth-UL AVP (AVP code 561) is of type Unsigned32, and it indicates the minimum requested bandwidth in kbit per second for an uplink IP flow. The bandwidth contains all the overhead coming from the IP-layer and the layers above, e.g. IP, TCP, UDP, HTTP, RTP and RTP payload. + +When provided in an AA-Request, it indicates the minimum requested bandwidth. + +### 5.3.60 IMS-Content-Identifier AVP + +The IMS-Content-Identifier AVP (AVP code 563) is of type OctetString, and it contains information that identifies the particular IMS communication service or communication dialogue that the AF service session belongs to. This information may be used by the PCRF, for example, to differentiate Charging for different communication dialogs in the IMS session. + +### 5.3.61 IMS-Content-Type AVP + +The IMS-Content-Type AVP (AVP code 564) is of type Enumerated, and it indicates the type of IMS communication service the AF session refers to. The following values are defined: + +NO\_CONTENT\_DETAIL (0) + +This value is used to indicate that no information about the type of IMS communication service is being provided + +CAT (1) + +This value is used to indicate that the type of IMS communication service is Customized Alerting Tones + +CONFERENCE (2) + +This value is used to indicate that the type of IMS communication service is 3PTY conference + +### 5.3.62 Callee-Information AVP + +The Callee-Information AVP (AVP code 565) is of type Grouped, and it contains information that identifies the callee information of the AF service session. This information may be used by the PCRF, for example, to provide the callee information in the PCC rule decision for further volume based charging. + +AVP Format: + +``` +Callee-Information ::= < AVP Header: 565 > + [Called-Party-Address] + * [Requested-Party-Address] + * [Called-Asserted-Identity] + * [AVP] +``` + +### 5.3.63 FLUS-Identifier AVP + +The FLUS-Identifier AVP (AVP code 566) is of type OctetString, and it indicates that a media component is used for FLUS media. + +It is derived from the media level attribute "a=label:" (see IETF RFC 4574 [68]) obtained from the SDP body. It contains the string after "a=label:" starting with "flus" and may be followed by more characters as described in 3GPP TS 26.238 [69]. + +### 5.3.64 Desired-Max-Latency AVP + +The Desired-Max-Latency AVP (AVP code 567) is of type Float32 and describes the maximum desirable end to end transport level packet latency in milliseconds as a zero-based integer or as a non-zero real value. The value excludes any application level processing in the sender and receivers, such as e.g. application-level retransmission or encoding/decoding. + +### 5.3.65 Desired-Max-Loss AVP + +The Desired-Max-Loss AVP (AVP code 568) is of type Float32 and describes the maximum desirable end to end transport level packet loss rate in percent (without "%" sign) as a zero-based integer or as a non-zero real value. + +### 5.3.66 MA-Information AVP + +The MA-Information AVP (AVP code 570) is of type Grouped, and contains the additional or released IP-CAN type and RAT type for a MA PDU session. + +``` +MA-Information ::= < AVP Header: 570 > + [ IP-CAN-Type ] + [ RAT-Type ] + [ MA-Information-Action ] + *[ AVP ] +``` + +### 5.3.67 MA-Information-Action AVP + +The MA-Information-Action AVP (AVP code 571) is of type Unsigned32, and it indicates the action to apply to the IP-CAN type and RAT type values included in the MA-Information AVP. + +The following values are defined in this specification: + +0 (ADD): + +This value shall be used to indicate that the IP-CAN Type/RAT Type included in the MA-Information AVP are available for the MA PDU session. + +1 (RELEASE): + +This value shall be used to indicate that the IP-CAN Type/RAT Type included in the MA-Information AVP are released and not available for the MA PDU session. + +0 (ADD) is the default value. + +### 5.3.68 NID AVP + +The NID AVP (AVP code 569) is of type OctetString, and it indicates Network Identifier (NID) consisting on 44 bits (11 hexadecimal digits), as specified in 3GPP TS 23.003 [38], clause 12.7. + +The NID AVP is only applicable in 5GS when the serving network is an SNPN, as described in Annex E. + +### 5.3.69 5GS-RAN-NAS-Release-Cause AVP (3GPP-5GS and Non-3GPP-5GS access type) + +The 5GS-RAN-NAS-Release-Cause AVP (AVP code 572) is of type Grouped, and indicates the RAN or NAS release cause code information in 3GPP-5GS and non-3GPP-5GS access types. + +AVP Format: + +``` +5GS-RAN-NAS-Release-Cause ::= < AVP Header: 572 > + [5GMM-Cause] + [5GSM-Cause] + [NGAP-Cause] + *[ AVP ] +``` + +### 5.3.70 5GMM-Cause AVP + +The 5GMM-Cause AVP (AVP code 573) is of type Unsigned32 and indicates the 5GMM cause code information. The AVP shall be coded as per the 5GMM Cause in clause 9.11.3.2 of 3GPP TS 24.501 [70]. + +### 5.3.71 5GSM-Cause AVP + +The 5GSM-Cause AVP (AVP code 574) is of type Unsigned32 and indicates the 5GSM cause code information. The AVP shall be coded as per the 5GSM Cause in clause 9.11.4.2 of 3GPP TS 24.501 [70]. + +### 5.3.72 NGAP-Cause AVP + +The NGAP-Cause AVP (AVP code 575) is of type Grouped and indicates the NG Application Protocol cause value as specified in clause 9.4.5 of 3GPP TS 38.413 [71]. + +AVP Format: + +``` +NGAP-Cause ::= < AVP Header: 575 > + {NGAP-Group} + {NGAP-Value} +``` + +### 5.3.73 NGAP-Group AVP + +The NGAP-Group AVP (AVP code 576) is of type Unsigned32, and it indicates the group of the NGAP cause. The value of this IE shall equal to the ASN.1 value of the specified NGAP cause group + +NGAP supports cause groups defined as separate enumerations, as specified in clause 9.4.5 of 3GPP TS 38.413 [71]. The following values are defined in this specification: + +0: + +This value indicates the NGAP cause group is "radioNetwork". + +1: + +This value indicates the NGAP cause group is "transport". + +2: + +This value indicates the NGAP cause group is "nas". + +3: + +This value indicates the NGAP cause group is "protocol". + +4: + +This value indicates the NGAP cause group is "misc". + +### 5.3.74 NGAP-Value AVP + +The NGAP-Value AVP (AVP code 577) is of type Unsigned32 and indicates the NG AP cause value in specific cause group identified by the NGAP-Group AVP, as specified in clause 9.4.5 of 3GPP TS 38.413 [71]. + +### 5.3.75 Wireline-User-Location-Info AVP + +The Wireline-User-Location-Info AVP (AVP code 578) is of type Grouped and contains either wireline Cable or wireline BBF user location information. + +The HFC-Node-Identifier AVP indicates wireline cable location and contains an HFC Node Identifier. + +The GLI-Identifier AVP indicates wireline BBF location and contains a Global Line Identifier. The Line-Type AVP indicates the type of line included in the GLI-Identifier AVP. + +AVP Format: + +``` +Wireline-User-Location-Info ::= < AVP Header: 578 > + [ HFC-Node-Identifier ] + [ GLI-Identifier ] + [ Line-Type ] + *[ AVP ] +``` + +### 5.3.76 HFC-Node-Identifier AVP + +The HFC-Node-Identifier AVP (AVP code 579) is of type OctetString and contains an HFC Node Identifier as specified in CableLabs WR-TR-5WWC-ARCH [73]. + +### 5.3.77 GLI-Identifier AVP + +The GLI-Identifier AVP (AVP code 580) is of type OctetString and contains a Global Line Identifier (see clause 28.16.3 of 3GPP TS 23.003 [38]) encoded as base64-encoded characters, representing the GLI value (up to 150 bytes) as specified in BBF WT-470 [74]. + +### 5.3.78 Line-Type AVP + +The Line-Type AVP (AVP code 581) is of type Unsigned32 and it indicates the type of wireline (DSL or PON) for the wireline BBF access. + +The following values are defined in this specification: + +0 (DSL): + +This value shall be used to indicate DSL line. + +1 (PON): + +This value shall be used to indicate PON line. + +### 5.3.79 MPS-Action AVP + +The MPS-Action AVP (AVP code 582) is of type Enumerated, and contains the indication whether to enable or disable MPS for DTS. + +The following values are defined: + +DISABLE\_MPS\_FOR\_DTS (0) + +Disable MPS for DTS. + +ENABLE\_MPS\_FOR\_DTS (1) + +Enable MPS for DTS. + +AUTHORIZE\_AND\_ENABLE\_MPS\_FOR\_DTS (2) + +The PCRF shall check the user's MPS subscription and enable MPS for DTS. + +AUTHORIZE\_AND\_ENABLE\_MPS\_FOR\_AF\_SIGNALLING (3) + +The PCRF shall check the user's MPS subscription and enable MPS for AF signalling. + +## 5.4 Rx re-used AVPs + +### 5.4.0 General + +Table 5.4.0.1 lists the Diameter AVPs re-used by the Rx reference point from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their usage within the Rx reference point. Other AVPs from existing Diameter Applications, except for the AVPs from Diameter Base Protocol, do not need to be supported. The AVPs from Diameter Base Protocol are not included in table 5.4.0.1, but they are re-used for the Rx protocol. Unless otherwise stated, re-used AVPs shall maintain their 'M', 'P' and 'V' flag settings. Where 3GPP Radius VSAs are re-used, unless otherwise stated, they shall be translated to Diameter AVPs as described in RFC 4005 [12] with the exception that the 'M' flag shall be set and the 'P' flag may be set. + +**Table 5.4.0.1: Rx re-used Diameter AVPs** + +| Attribute Name | Reference | Comments | Applicability (notes 1, 2) | +|--------------------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 3GPP-MS-TimeZone | 3GPP TS 29.061 [34] | Indicates the offset between universal time and local time in steps of 15 minutes of where the MS currently resides.
This AVP shall have the 'M' bit cleared. | NetLoc
RAN-NAS-Cause | +| 3GPP-SGSN-MCC-MNC | 3GPP TS 29.061 [34] | Indicates the serving core network operator ID. For GPRS accesses the MCC and the MNC of the SGSN.
For EPS 3GPP/non-3GPP accesses, the MCC and the MNC provided by the SGW, ePDG or TWAG.
This AVP shall have the 'M' bit cleared. | NetLoc, RAN-NAS-Cause | +| 3GPP-User-Location-Info | 3GPP TS 29.061 [34] | Indicates details of where the UE is currently located (e.g. SAI or CGI), Coding for type values between 0 and 134 shall be done as defined in 3GPP TS 29.274 [33]. The values 135 and 137 corresponding to "NCGI" and "5GS TAI and NCGI" (which are not applicable in some specification using this AVP) shall be applicable. Coding for these type values shall be done as defined in 3GPP TS 29.061 [34]
This AVP shall have the 'M' bit cleared. | NetLoc
RAN-NAS-Cause | +| AN-GW-Address | 3GPP TS 29.212 [8] | Carries the IP address of the ePDG used as IPSec tunnel endpoint with the UE.
This AVP shall have the 'M' bit cleared. | | +| AN-Trusted | 3GPP TS 29.273 [39] | Indicates whether the access network is trusted or untrusted for the Non-3GPP access network. This AVP shall have the 'M' bit cleared. | | +| Called-Asserted-Identity | 3GPP TS 32.299 [24] | The address (Public User ID: SIP URI, E.164, etc.) of the finally asserted called party. | VBCLTE | +| Called-Party-Address | 3GPP TS 32.299 [24] | The address (SIP URI, Tel URI or URN) of the party to whom the call is addressed. | VBCLTE | +| Called-Station-Id | IETF RFC 4005 [12] | The PDN the user is connected to. For GPRS and EPS the APN. When used to contain the APN, the APN is composed of the APN Network Identifier only, or the APN Network Identifier and the APN Operator Identifier as specified in TS 23.003 [38], clause 9.1. The inclusion of the APN Operator Identifier can be configurable. | Rel8 | +| Calling-Party-Address | 3GPP TS 32.299 [24] | The address (SIP URI or Tel URI) which identifies the party (Public User Identity or Public Service Identity) initiating a SIP transaction.
This information may be used by the PCRF, for example, to provide the caller information in the PCC rule decision for further volume based charging. | VBCLTE | +| DRMP | IETF RFC 7944 [43] | Allows Diameter endpoints to indicate the relative priority of Diameter transactions. | | +| Final-Unit-Action | IETF RFC 8506 [75] | The action applied by the PCEF when the user's account cannot cover the service cost. | Rel8 | +| Framed-IP-Address | IETF RFC 4005 [12] | The valid routable IPv4 address that is applicable for the IP Flows towards the UE at the PCEF. The PCRF shall use this address to identify the correct IP-CAN session (session binding). For example, the IP address may actually be that of the network interface of a NAT device between the UE and the GW. The values 0xFFFFFFFF and 0x00000000 are not applicable as described in RFC 4005 [12]. | | + +| Attribute Name | Reference | Comments | Applicability (notes 1, 2) | +|-------------------------------|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------| +| Framed-Ipv6-Prefix | IETF RFC 4005 [12] | A valid full Ipv6 address that is applicable to an IP flow or IP flows towards the UE at the PCEF. The PCRF shall use this address to identify the correct IP-CAN session (session binding, refer to TS 29.213 [9]). For example, the IP address may actually be that of the network interface of a NAT device between the UE and the GW. The encoding of the value within this Octet String type AVP shall be as defined in RFC 3162 [20], clause 2.3. The "Reserved", "Prefix-Length" and "Prefix" fields shall be included in this order. The AF shall set the "Prefix Length" to 128 and encode the Ipv6 address of the UE within the "Prefix" field. | | +| Granted-Service-Unit (NOTE 3) | IETF RFC 8506 [75] | The volume and/or time thresholds for sponsored data connectivity. Only CC-Total-Octets, one of the CC-Input-Octets and CC-Output-Octets, or CC-Time AVPs are reused. This AVP shall have the 'M' bit cleared. | SponsoredConnectivity, SCTimeBase dUM | +| IP-CAN-Type | 3GPP TS 29.212 [8] | IP-CAN type of the user. | | +| Load | IETF RFC 8583 [51] | The AVP used to convey load information between Diameter nodes. This AVP and all AVPs within this grouped AVP shall have the 'M' bit cleared. | | +| Max-PLR-DL | 3GPP TS 29.212 [8] | indicates ratio of lost packets per number of packets sent in unit of tenth of percent for a downlink voice service data flow. | CHEM | +| Max-PLR-UL | 3GPP TS 29.212 [8] | indicates ratio of lost packets per number of packets sent in unit of tenth of percent for an uplink voice service data flow. | CHEM | +| NetLoc-Access-Support | 3GPP TS 29.212 [8] | Indicates the level of support for NetLoc procedures provided by the current access network. | NetLoc | +| OC-OLR | IETF RFC 7683 [35] | Contains the necessary information to convey an overload report. | | +| OC-Supported-Features | IETF RFC 7683 [35] | Defines the support for the Diameter overload indication conveyance by the sending node. | | +| Pre-emption-Capability | 3GPP TS 29.212 [8] | Indicates whether a service data flow can get resources that were already assigned to another service data flow with a lower priority level. | MCPTT-Preemption | +| Pre-emption-Vulnerability | 3GPP TS 29.212 [8] | Indicates whether a service data flow can lose the resources assigned to it in order to admit a service data flow with higher priority level. | MCPTT-Preemption | +| RAN-NAS-Release-Cause | 3GPP TS 29.212 [8] | Indicates RAN and/or NAS release cause code information. TWAN release cause code information or untrusted WLAN release cause code information. | RAN-NAS-Cause | +| RAT-Type | 3GPP TS 29.212 [8] | Indicate which Radio Access Technology is currently serving the UE. | Rel8 | +| Requested-Party-Address | 3GPP TS 32.299 [24] | The address (SIP URI, Tel URI or URN) of the party to whom the call was originally addressed. | VBCLTE | +| Reference-Id | 3GPP TS 29.154 [47] | Indicates the transfer policy stored in the SPR. | | +| Reservation-Priority | 3GPP TS 183.017 [15] | The vendor-id shall be set to ETSI (13019) [15]. The support of this AVP shall be advertised in the capabilities exchange mechanisms (CER/CEA) by including the ETSI parameter in the Supported-Vendor-Id AVP. | | +| Subscription-Id | IETF RFC 8506 [75] | The identification of the subscription (IMSI, MSISDN, etc.). | | +| Supported-Features | 3GPP TS 29.229 [25] | If present, this AVP informs the destination host about the features that the origin host requires to successfully complete this command exchange. | Rel8 | + +| Attribute Name | Reference | Comments | Applicability (notes 1, 2) | +|-------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| TCP-Source-Port | 3GPP TS 29.212 [8] | Contains the TCP source port number in the case that a NAT and firewall are detected and the IKEv2 messages exchanged between the UE and the ePDG are transported using the firewall traversal tunnel as described in 3GPP TS 24.302 [50]. This AVP shall have the 'M' bit cleared. | NetLoc-Untrusted-WLAN | +| TWAN-Identifier | 3GPP TS 29.061 [34] | Indicates the UE location in a Trusted WLAN or Untrusted WLAN Access Network. This AVP shall have the 'M' bit cleared. | NetLoc-Trusted-WLAN
RAN-NAS-Cause
NetLoc-Untrusted-WLAN | +| ToS-Traffic-Class | 3GPP TS 29.212 [8] | Indicates the DSCP code to be used for packet filter. The first octet contains the DSCP code and the second octet contains the mask field set to 11111100. | DSCP | +| UDP-Source-Port | 3GPP TS 29.212 [8] | Contains the UDP source port number in the case that NAT is detected and the IKEv2 messages exchanged between the UE and the ePDG are encapsulated in the UDP messages according to IETF RFC 3948 [49]. This AVP shall have the 'M' bit cleared. | NetLoc-Untrusted-WLAN | +| UE-Local-IP-Address | 3GPP TS 29.212 [8] | Indicates the local IP address of the UE. This AVP shall have the 'M' bit cleared. | NetLoc-Untrusted-WLAN | +| Used-Service-Unit (NOTE 3) | IETF RFC 8506 [75] | The measured volume and/or time for sponsored data connectivity. Only CC-Total-Octets, one of the CC-Input-Octets and CC-Output-Octets, or CC-Time AVPs are reused. This AVP shall have the 'M' bit cleared. | SponsoredConnectivity
SCTimeBasedUM | +| User-Equipment-Info | IETF RFC 8506 [75] | The identification and capabilities of the terminal (IMEISV, etc.) When the User-Equipment-Info-Type is set to IMEISV(0), the value within the User-Equipment-Info-Value shall be a UTF-8 encoded decimal. | | +| User-Equipment-Info-Extension | IETF RFC 8506 [75] | The identification and capabilities of the terminal (IMEISV, IMEI, etc.) When the User-Equipment-Info-IMEISV or the User-Equipment-Info-IMEI is used, it shall be a UTF-8 encoded decimal. | User-Equipment-Info-Extension | +| User-Location-Info-Time | 3GPP TS 29.212 [8] | Indicates the time the UE was last known to be in the location. | NetLoc
RAN-NAS-Cause | + +NOTE 1: AVPs marked with "Rel8" are applicable as described in clause 5.4.1. +NOTE 2: AVPs marked with "SponsoredConnectivity" are applicable for sponsored data connectivity. +NOTE 3: Volume Usage monitoring control functionality is applicable for SponsoredConnectivity supported feature. Time Based Usage monitoring control is applicable for SCTimeBasedUM supported feature. + +### 5.4.1 Use of the Supported-Features AVP on the Rx reference point + +The Supported-Features AVP is used during session establishment to inform the destination host about the required and optional features that the origin host supports. The client shall, in the first request of a Diameter session indicate the set of supported features. The server shall, in the first answer within the Diameter session indicate the set of features that it has in common with the client and that the server shall support within the same Diameter session. Any further command messages shall always be compliant with the list of supported features indicated in the Supported-Features AVPs during session establishment. Features that are not advertised as supported shall not be used to construct the command messages for that Diameter session. Unless otherwise stated, the use of the Supported-Features AVP on the Rx reference point shall be compliant with the requirements for dynamic discovery of supported features and associated error handling on the Cx reference point as defined in clause 7.2.1 of 3GPP TS 29.229 [25]. + +The base functionality for the Rx reference point is the 3GPP Rel-7 standard and a feature is an extension to that functionality. If the origin host does not support any features beyond the base functionality, the Supported-Features AVP may be absent from the Rx commands. As defined in clause 7.1.1 of 3GPP TS 29.229 [25], when extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF. + +As defined in 3GPP TS 29.229 [25], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the Rx reference point, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the Rx reference point, the Feature-List-ID AVP shall differentiate those lists from one another. + +On receiving an initial request application message, the destination host shall act as defined in clause 7.2.1 of 3GPP TS 29.229 [25]. The following exceptions apply to the initial and stateless AAR/AAA command pair: + +- If the AF supporting post-Rel-7 Rx functionality is able to interoperate with a PCRF supporting Rel-7, the AAR shall include the features supported by the AF within Supported-Features AVP(s) with the 'M' bit cleared. Otherwise, the AAR shall include the supported features within the Supported-Features AVP(s) with the M-bit set. + +NOTE 1: One instance of Supported-Features AVP is needed per Feature-List-ID. + +- If the AAR command does not contain any Supported-Features AVP(s) and the PCRF supports Rel-7 Rx functionality, the AAA command shall not include the Supported-Features AVP. In this case, both AF and PCRF shall behave as specified in the Rel-7 version of this document. +- If the AAR command contains the Supported-Features AVP(s), the PCRF shall include the Supported-Features AVP(s) in the AAA command, with the 'M' bit cleared, indicating only the features that both the PCRF and AF support. In this case, the PCRF should not use the 'M' bit setting of the Supported-Features AVP(s) to determine if the AAR is accepted or rejected. + +NOTE 2: The client will always declare all features that are supported according to table 5.4.1.1. When more than one feature identifying a release is supported by both AF and PCRF, the AF will work according to the latest common supported release. + +Once the PCRF and AF have negotiated the set of supported features during session establishment, the set of common features shall be used during the lifetime of the Diameter session. + +The table below defines the features applicable to the Rx interfaces for the feature list with a Feature-List-ID of 1. + +**Table 5.4.1.1: Features of Feature-List-ID 1 used in Rx** + +| Feature bit | Feature | M/O | Description | +|-------------|--------------------------|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Rel8 | M | This feature indicates the support of the base 3GPP Rel-8 functionality, including the AVPs and corresponding procedures supported by the base 3GPP Rel-7 Rx standard, but excluding those features represented by separate feature bits. AVPs introduced with this feature are marked with "Rel8" in Table 5.4.0.1. | +| 1 | Rel9 | M | This feature indicates the support of the base 3GPP Rel-9 functionality, including the AVPs and corresponding procedures supported by the Rel8 feature bit, but excluding those features represented by separate feature bits. | +| 2 | ProvAFsignalFlow | O | This indicates support for the feature of provisioning of AF signalling flow information as described in clause 4.4.5A. If the PCRF supports this feature the AF may provision AF signalling flow information.
NOTE: This feature is used by the IMS Restoration Procedures to provide to the PDN-Gateway the address of the P-CSCF selected by the UE, refer to TS 23.380 [28]. | +| 3 | SponsoredConnectivity | O | This feature indicates support for sponsored data connectivity feature. If the PCRF supports this feature, the AF may provide sponsored data connectivity to the subscriber. | +| 4 | Rel10 | M | This feature indicates the support of the base 3GPP Rel-10 functionality, including the AVPs and corresponding procedures supported by the Rel8 and Rel9 feature bit, but excluding those features represented by separate feature bits. AVPs introduced with this feature are marked with "Rel10" in table 5.3.0.1. | +| 5 | NetLoc | O | This feature indicates the support of the Access Network Information Reporting. | +| 6 | ExtendedFilter | O | This feature indicates the support for the local (i.e. UE) address and mask being present in filters signalled between network and UE. | +| 7 | SCTimeBasedUM | O | This feature indicates support for sponsored data connectivity feature with time-based usage monitoring control required. If the PCRF supports this feature, the AF may provide time threshold for the usage monitoring control. | +| 8 | Netloc-Trusted-WLAN | O | This feature indicates the support for the Trusted WLAN access. It requires that NetLoc feature is also supported. | +| 9 | RAN-NAS-Cause | O | This feature indicates the support for the release cause code information (NOTE 1) from the access network. | +| 10 | GroupComService | O | This feature indicates the support of Group Communication services as described in TS 23.468 [36] for unicast services. | +| 11 | ResShare | O | This feature indicates the support of resource sharing among several AF sessions. | +| 12 | DeferredService | O | This feature indicates the support of deferred transfer of service information from the AF. | +| 13 | DSCP | O | This feature indicates that the AF may provide a DSCP value when describing a service flow by supplying the ToS-Traffic-Class AVP. | +| 14 | SponsorChange | O | This feature indicates that the AF provides information on whether it wants to enable or disable/not enable sponsoring a service. It requires that SponsoredConnectivity is also supported. | +| 15 | E2EQOSMTSI | O | This feature indicates that the AF supports QoS End-to-end MTSI extensions as defined in 3GPP TS 26.114 [41] | +| 16 | NetLoc-Untrusted-WLAN | O | This feature indicates the support of the Untrusted WLAN access as described in 3GPP TS 23.203 [2]. It requires that NetLoc feature is also supported. | +| 17 | MCPTT | O | This feature indicates the support of Mission Critical Push To Talk services as described in 3GPP TS 23.179 [44] | +| 18 | PrioritySharing | O | This feature indicates that Priority Sharing is supported as described in 3GPP TS 23.203 [2], clause 6.1.19. | +| 19 | PLMNInfo | O | This feature indicates that reporting on changes of PLMN info is supported. | +| 20 | MediaComponentVersioning | O | This feature indicates the support of media component versioning as defined in clause 4.4.9. | +| 21 | MCPTT-Preemption | O | This feature indicates the support of service pre-emption based on the information provided by the AF. It requires that both PrioritySharing and MCPTT features are also supported. | +| 22 | MCVideo | O | This feature indicates the support of Mission Critical Video services as described in 3GPP TS 23.281 [61]. | + +Feature bit: The order number of the bit within the Feature-List AVP where the least significant bit is assigned number "0". + +Feature: A short name that can be used to refer to the bit and to the feature, e.g. "EPS". + +M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O"). + +Description: A clear textual description of the feature. + +NOTE 1: In this release, 5GS and EPS release cause code information is supported. The 3GPP-EPS and Non-3GPP EPS release cause code information from the access network is encoded in the RAN-NAS-Release-Cause AVP and can include RAN/NAS release cause(s), a TWAN release cause or an untrusted WLAN release cause. The 3GPP 5GS and Non-3GPP 5GS release cause code is encoded in the 5GS-RAN-NAS-Release-Cause AVP and is only applicable to Rx interworking with N7 as specified in Annex E. + +**Table 5.4.1.2: Features of Feature-List-ID 2 used in Rx** + +| Feature bit | Feature | M/O | Description | +|-------------|-------------------------------|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | PCSCF-Restoration-Enhancement | O | This feature indicates support of P-CSCF Restoration Enhancement. It is used for the PCRF and the P-CSCF to indicate if they support P-CSCF Restoration Enhancement. | +| 1 | Extended-Max-Requested-BW-NR | O | This feature indicates the support of the extended Max-Requested-Bandwidth for NR. | +| 2 | Extended-Min-Requested-BW-NR | O | This feature indicates the support of the extended Min-Requested-Bandwidth for NR. It requires that Rel-10 feature is also supported. | +| 3 | Extended-BW-E2EQOSMTSI-NR | O | This feature indicates the support of the extended E2EQOSMTSI bandwidth values for NR. It requires that E2EQOSMTSI feature and the Extended-Max-Requested-BW-NR are also supported. | +| 4 | VBC | O | This feature indicates the support of Volume Based Charging of IMS services as defined in clause A.16. | +| 5 | CHEM | O | This feature indicates the support of Coverage and Handover Enhancements for Media (CHEM) | +| 6 | VBCLTE | O | This feature indicates the support of providing the caller and callee information as defined in clause A.16. | +| 7 | FLUS | O | This feature indicates the support of FLUS functionality as described in 3GPP TS 26.238 [69]. | +| 8 | EPSFallbackReport | O | This feature indicates the support of the report of EPS Fallback as defined in clause E.3. | +| 9 | ATSSS | O | This feature indicates the support of the report of multiple IP-CAN types for a MA PDU session as defined in clause E.4. | +| 10 | QoSHint | O | This feature indicates the support of specific QoS hint parameters as described in 3GPP TS 26.114 [41], clause 6.2.10. | +| 11 | ReallocationOfCredit | O | This feature indicates the support of the report of reallocation of credit. It only applies to 5GS as defined in Annex E. | +| 12 | Netloc-Trusted-N3GA | O | This feature indicates the support for the Trusted N3GA access. It requires that NetLoc-Trusted-WLAN feature is also supported. | +| 13 | NetLoc-Wireline | O | This feature indicates the support for the Wireline access as specified in 3GPP TS 23.316 [72]. It only applies to 5GS as defined in Annex E. It requires that NetLoc feature is also supported. | +| 14 | MPSforDTS | O | This feature indicates the support of MPS for DTS as defined in clauses 4.4.11. and 4.4.12 | +| 15 | User-Equipment-Info-Extension | O | This feature indicates the support of the User-Equipment-Info-Extension AVP as defined in IETF RFC 8506 [75]. | +| 16 | AuthorizationForMpsSignalling | O | This feature indicates support for use of the MPS-Action AVP to signal that the UE's MPS subscription shall be checked by the PCRF prior to enabling MPS for AF signalling. | + +Feature bit: The order number of the bit within the Feature-List AVP where the least significant bit is assigned number "0". + +Feature: A short name that can be used to refer to the bit and to the feature, e.g. "EPS". + +M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O"). + +Description: A clear textual description of the feature. + +## 5.5 Rx specific Experimental-Result-Code AVP values + +### 5.5.1 Permanent Failures + +Errors that fall within the Permanent Failures category shall be used to inform the peer that the request failed, and should not be attempted again. + +IETF RFC 6733 [52] specifies the Experimental-Result AVP containing Vendor-ID AVP and Experimental-Result-Code AVP. The Experimental-Result-Code AVP (AVP Code 298) is of type Unsigned32 and contains a vendor-assigned value representing the result of processing a request. The Vendor-ID AVP shall be set to 3GPP (10415). + +Specific values of the Rx specific Experimental-Result-Code AVP are: + +#### INVALID\_SERVICE\_INFORMATION (5061) + +The PCRF rejects new or modified service information the service information provided by the AF is invalid or insufficient for the server to perform the requested action. + +#### FILTER\_RESTRICTIONS (5062) + +The PCRF rejects new or modified service information because the Flow-Description AVP(s) cannot be handled by the server because restrictions defined in clause 5.3.8 are not observed. + +#### REQUESTED\_SERVICE\_NOT\_AUTHORIZED (5063) + +The PCRF rejects new or modified service information because the requested service, as described by the service information provided by the AF, is not consistent with either the related subscription information, operator defined policy rules and/or the supported features in the IP-CAN network. + +#### DUPLICATED\_AF\_SESSION (5064) + +The PCRF rejects a new Rx session setup because the new Rx session relates to an AF session with another related active Rx session, e.g. if the AF provided the same AF charging identifier for this new Rx session that is already in use for the other ongoing Rx session. + +#### IP-CAN\_SESSION\_NOT\_AVAILABLE (5065) + +The PCRF rejects a new Rx session setup when it fails to associate the described service IP flows within the session information received from the AF to an existing IP-CAN session. + +#### UNAUTHORIZED\_NON\_EMERGENCY\_SESSION (5066) + +The PCRF rejects a new Rx session setup because the session binding function associated a non-Emergency IMS session to an IP-CAN session established to an Emergency APN. + +#### UNAUTHORIZED\_SPONSORED\_DATA\_CONNECTIVITY (5067) + +The PCRF rejects a new Rx session setup because the PCRF can't authorize the sponsored data connectivity based on the sponsored data connectivity profile or the operator policy (e.g. the sponsored data connectivity not authorized in the roaming case). + +#### TEMPORARY\_NETWORK\_FAILURE (5068) + +The PCRF rejects new or modified service information because there is a temporary failure in the access network (e.g. the SGW has failed). + +#### UNAUTHORIZED\_NON\_RLOS\_SESSION (5069) + +The PCRF rejects a new Rx session setup because the session binding function associated a non-RLOS IMS session to an IP-CAN session established to an RLOS APN. + +### 5.5.2 Transient Failures + +Errors that fall within the transient failures category are used to inform a peer that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. + +The Result-Code AVP values defined in Diameter Base IETF RFC 6733 [52] are applicable. Also the following specific Rx Experimental-Result-Code value is defined for transient failures: + +REQUESTED\_SERVICE\_TEMPORARILY\_NOT\_AUTHORIZED (4261) + +The PCRF temporarily rejects new or modified service information because the network is temporarily not able to provide the service delivery that the AF requested, e.g. due to the service information is not consistent with the operator defined policy rules for the congestion status of the user. + +## 5.6 Rx messages + +### 5.6.0 General + +Existing Diameter command codes from the Diameter base protocol IETF RFC 6733 [52] and the NASREQ Diameter application (RFC 4005 [12]) are used with the Rx specific AVPs. An Rx specific Auth-Application id is used together with the command code to identify the Rx messages. + +NOTE 1: The notion of NAS (Network Access Server) is not used here, NASREQ is just used for protocol purposes, not for its functional meaning. + +NOTE 2: Some of the AVPs included in the messages formats below are in bold to highlight that these AVPs are used by this specific protocol and do not belong to the original Diameter Base Protocol IETF RFC 6733 [52]. + +NOTE3: Multiple instances of the Subscription-Id AVP in the AAR or RAR command correspond to multiple types of identifier for the same subscriber, for example IMSI and MSISDN. + +### 5.6.1 AA-Request (AAR) command + +The AAR command, indicated by the Command-Code field set to 265 and the 'R' bit set in the Command Flags field, is sent by an AF to the PCRF in order to provide it with the Session Information. + +Message Format: + +``` + ::= < Diameter Header: 265, REQ, PXY > + < Session-Id > + [ DRMP ] + { Auth-Application-Id } + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + [ Destination-Host ] + [ IP-Domain-Id ] + [ Auth-Session-State ] + [ AF-Application-Identifier ] + *[ Media-Component-Description ] + [ Service-Info-Status ] + [ AF-Charging-Identifier ] + [ SIP-Forking-Indication ] + *[ Specific-Action ] + *[ Subscription-Id ] + [ OC-Supported-Features ] + *[ Supported-Features ] + [ Reservation-Priority ] + [ Framed-IP-Address ] + [ Framed-Ipv6-Prefix ] + [ Called-Station-Id ] + [ Service-URN ] + [ Sponsored-Connectivity-Data ] + [ MPS-Identifier ] + [ GCS-Identifier ] + [ MCPTT-Identifier ] +``` + +``` + + [ MCVVideo-Identifier ] + [ IMS-Content-Identifier ] + [ IMS-Content-Type ] +* [ Calling-Party-Address ] + [ Callee-Information ] + [ Rx-Request-Type ] +* [ Required-Access-Info ] + [ AF-Requested-Data ] + [ Reference-Id ] + [ Pre-emption-Control-Info ] + [ MPS-Action ] + [ Origin-State-Id ] +* [ Proxy-Info ] +* [ Route-Record ] +* [ AVP ] + +``` + +### 5.6.2 AA-Answer (AAA) command + +The AAA command, indicated by the Command-Code field set to 265 and the 'R' bit cleared in the Command Flags field, is sent by the PCRF to the AF in response to the AAR command. + +Message Format: + +``` + + ::= < Diameter Header: 265, PXY > + < Session-Id > + [ DRMP ] + { Auth-Application-Id } + { Origin-Host } + { Origin-Realm } + [ Result-Code ] + [ Experimental-Result ] + [ Auth-Session-State ] + * [ Access-Network-Charging-Identifier ] + [ Access-Network-Charging-Address ] + [ Acceptable-Service-Info ] + 0*2 [ AN-GW-Address ] + [ AN-Trusted ] + [ Service-Authorization-Info ] + [ IP-CAN-Type ] + [ MA-Information ] + [ NetLoc-Access-Support ] + [ RAT-Type ] + * [ Flows ] + [ OC-Supported-Features ] + [ OC-OLR ] + * [ Supported-Features ] + * [ Subscription-Id ] + [ User-Equipment-Info ] + [ User-Equipment-Info-Extension ] + [ 3GPP-SGSN-MCC-MNC ] + [ NID ] + * [ Class ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ Failed-AVP ] + [ Retry-Interval ] + [ Origin-State-Id ] + * [ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + * [ Proxy-Info ] + * [ Load ] + * [ AVP ] + +``` + +### 5.6.3 Re-Auth-Request (RAR) command + +The RAR command, indicated by the Command-Code field set to 258 and the 'R' bit set in the Command Flags field, is sent by the PCRF to the AF in order to indicate an Rx specific action. + +Message Format: + +``` + + ::= < Diameter Header: 258, REQ, PXY > + < Session-Id > + [ DRMP ] + { Origin-Host } + { Origin-Realm } + +``` + +``` + + { Destination-Realm } + { Destination-Host } + { Auth-Application-Id } + *{ Specific-Action } + [ OC-Supported-Features ] + *{ Access-Network-Charging-Identifier } + [ Access-Network-Charging-Address ] + 0*2[ AN-GW-Address ] + [ AN-Trusted ] + *{ Flows } + *{ Subscription-Id } + [ Abort-Cause ] + [ IP-CAN-Type ] + [ MA-Information ] + [ NetLoc-Access-Support ] + [ RAT-Type ] + [ Sponsored-Connectivity-Data ] + [ 3GPP-User-Location-Info ] + [ User-Location-Info-Time ] + [ 3GPP-MS-TimeZone ] + *{ RAN-NAS-Release-Cause } + *{ 5GS-RAN-NAS-Release-Cause } + [ 3GPP-SGSN-MCC-MNC ] + [ NID ] + [ TWAN-Identifier ] + [ TCP-Source-Port ] + [ UDP-Source-Port ] + [ UE-Local-IP-Address ] + [ Wireline-User-Location-Info ] + [ Origin-State-Id ] + *{ Class } + *{ Proxy-Info } + *{ Route-Record } + *{ AVP } + +``` + +### 5.6.4 Re-Auth-Answer (RAA) command + +The RAA command, indicated by the Command-Code field set to 258 and the 'R' bit cleared in the Command Flags field, is sent by the AF to the PCRF in response to the RAR command. + +Message Format: + +``` + + ::= < Diameter Header: 258, PXY > + < Session-Id > + [ DRMP ] + { Origin-Host } + { Origin-Realm } + [ Result-Code ] + [ Experimental-Result ] + [ OC-Supported-Features ] + [ OC-OLR ] + *{ Media-Component-Description } + [ Service-URN ] + [ Origin-State-Id ] + *{ Class } + [ Error-Message ] + [ Error-Reporting-Host ] + *{ Redirect-Host } + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + [ Failed-AVP ] + *{ Proxy-Info } + *{ AVP } + +``` + +### 5.6.5 Session-Termination-Request (STR) command + +The STR command, indicated by the Command-Code field set to 275 and the 'R' bit set in the Command Flags field, is sent by the AF to inform the PCRF that an established session shall be terminated. + +Message Format: + +``` + + ::= < Diameter Header: 275, REQ, PXY > + < Session-Id > + [ DRMP ] + { Origin-Host } + { Origin-Realm } + +``` + +``` + + { Destination-Realm } + { Auth-Application-Id } + { Termination-Cause } + [ Destination-Host ] + [ OC-Supported-Features ] + *[ Required-Access-Info ] + *[ Class ] + [ Origin-State-Id ] + *[ Proxy-Info ] + *[ Route-Record ] + *[ AVP ] + +``` + +### 5.6.6 Session-Termination-Answer (STA) command + +The STA command, indicated by the Command-Code field set to 275 and the 'R' bit cleared in the Command Flags field, is sent by the PCRF to the AF in response to the STR command. + +Message Format: + +``` + + ::= < Diameter Header: 275, PXY > + < Session-Id > + [ DRMP ] + { Origin-Host } + { Origin-Realm } + [ Result-Code ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ OC-Supported-Features ] + [ OC-OLR ] + [ Failed-AVP ] + [ Sponsored-Connectivity-Data ] + [ Origin-State-Id ] + [ 3GPP-User-Location-Info ] + [ User-Location-Info-Time ] + [ 3GPP-MS-TimeZone ] + *[ RAN-NAS-Release-Cause ] + *[ 5GS-RAN-NAS-Release-Cause ] + [ 3GPP-SGSN-MCC-MNC ] + [ NID ] + [ TWAN-Identifier ] + [ TCP-Source-Port ] + [ UDP-Source-Port ] + [ UE-Local-IP-Address ] + [ Netloc-Access-Support ] + [ Wireline-User-Location-Info ] + *[ Class ] + *[ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + *[ Proxy-Info ] + *[ Load ] + *[ AVP ] + +``` + +### 5.6.7 Abort-Session-Request (ASR) command + +The ASR command, indicated by the Command-Code field set to 274 and the 'R' bit set in the Command Flags field, is sent by the PCRF to inform the AF that bearer for the established session is no longer available. + +Message Format: + +``` + + ::= < Diameter Header: 274, REQ, PXY > + < Session-Id > + [ DRMP ] + { Origin-Host } + { Origin-Realm } + { Destination-Realm } + { Destination-Host } + { Auth-Application-Id } + [ OC-Supported-Features ] + { Abort-Cause } + [ Origin-State-Id ] + *[ Proxy-Info ] + *[ Route-Record ] + *[ AVP ] + +``` + +### 5.6.8 Abort-Session-Answer (ASA) command + +The ASA command, indicated by the Command-Code field set to 274 and the 'R' bit cleared in the Command Flags field, is sent by the AF to the PCRF in response to the ASR command. + +Message Format: + +``` + ::= < Diameter Header: 274, PXY > + < Session-Id > + [ DRMP ] + { Origin-Host } + { Origin-Realm } + [ Result-Code ] + [ OC-Supported-Features ] + [ OC-OLR ] + [ Origin-State-Id ] + [ Error-Message ] + [ Error-Reporting-Host ] + [ Failed-AVP ] + *[ Redirect-Host ] + [ Redirect-Host-Usage ] + [ Redirect-Max-Cache-Time ] + *[ Proxy-Info ] + *[ AVP ] +``` + +# Annex A (normative): IMS Related P-CSCF Procedures over Rx + +## A.1 Provision of Service Information at P-CSCF + +The P-CSCF shall send service information to the PCRF upon every SIP message that includes an SDP answer payload for the purpose of authorizing the IP flows and the QoS resources required for a negotiated IMS session, unless the SDP payload only relates to a circuit-switched bearer (i.e. "c=" line set to "PSTN" and an "m=" line set to "PSTN", refer to 3GPP TS 24.292 [26]). The service information shall be derived both from the SDP offer and the SDP answer. This ensures that the PCRF receives proper information to perform media authorization for all possible IMS session set-up scenarios, and that the PCRF is also capable of handling session modifications. The P-CSCF may include the Service-Info-Status AVP with the value set to FINAL\_SERVICE\_INFORMATION. + +Additionally, the P-CSCF may send service information to the PCRF when receiving a SIP message that includes an SDP offer payload for the purpose of performing an early bandwidth authorization check, or for enabling pre-authorization for a UE terminated IMS session establishment or modification with UE initiated resource reservation, or for the retrieval of network provided access network information (see clause A.10.2). The P-CSCF shall send service information to the PCRF when receiving a SIP message that includes an SDP offer payload when the IMS session is an MPS session that requires priority treatment. For a UE terminated session the P-CSCF may send the service information derived from the SDP offer when the SDP offer either does not include any preconditions information or includes preconditions information indicating that the local preconditions (i.e. the preconditions related to the remote peer) are already met. In this case, the P-CSCF shall derive the service information only from the SDP offer and shall include the Service-Info-Status AVP with the value set to PRELIMINARY SERVICE INFORMATION. + +NOTE 1: For a UE terminated session setup, when the SDP offer either does not include any preconditions information or includes preconditions information indicating that the local preconditions (i.e. the preconditions related to the remote peer) are already met, the terminating UE can request a resource modification prior to sending the SDP answer. Even if the IP address and port information in the session information derived from the SDP offer can be insufficient for PCC rule authorization, the policy to handle such UE initiated requests at the PCRF can take into account the fact that an IMS session establishment is ongoing, for instance in deciding whether to authorize the request and in selecting an appropriate charging key and a gating policy. + +The P-CSCF shall derive Flow-Description AVP within the service information from the SDP as follows: + +- An uplink Flow-Description AVP shall be formed as follows: The destination address shall be taken from the SDP information received by the P-CSCF in downlink direction, while the source IP address may be formed from the address present in the SDP received by the P-CSCF in uplink direction (taking into account only the 64 bit prefix of the Ipv6 address) Source and destination ports shall be derived according to rules provided in 3GPP TS 29.213 [9] clause 6.2. + +EXAMPLE 1: Assuming UE A sends an SDP to UE B, the PCRF of UE B uses the address present in this SDP for the destination address of UE B's uplink Flow-Description AVP, while the PCRF of the UE A uses the 64 bit prefix of the same address for the source address of UE A's uplink Flow-Description AVP. If the source address is not formed from the 64 bit prefix, the source address shall be wildcarded. + +- A downlink Flow-Description AVP shall be formed as follows: The destination address shall be taken from the SDP information received by the P-CSCF in uplink direction, while the source IP address may be formed (in order to reduce the possibilities of bearer misuse) from the destination address in the SDP received by the P-CSCF in downlink direction (taking into account only the 64 bit prefix of the Ipv6 address) Source and destination ports shall be derived according to rules provided in 3GPP TS 29.213 [9] clause 6.2. + +EXAMPLE 2: Assuming UE A sends an SDP to UE B, the PCRF of UE A uses the address present in this SDP for the destination address of UE A's downlink Flow-Description AVP, while the PCRF of UE B uses the 64 bit prefix of the same address for the source address of UE B's downlink Flow-Description AVP. If the source address is not formed from the 64 bit prefix, the source address shall be wildcarded. + +The P-CSCF shall derive the bandwidth information within the service information, from the "b=AS" SDP parameter and "a=bw-info" SDP parameter, if available and if the E2EMTSIQOS feature is supported. If "a=bw-info" is used for bandwidth derivation, the P-CSCF shall use the SDP attribute line that contains the bandwidth properties for the IP version used by the UE, as detailed in 3GPP TS 29.213 [9] clause 6.2. If the received "a=bw-info" SDP attribute line(s) contain only bandwidth properties for an IP version that is not used by the UE, the P-CSCF shall re-compute the bandwidth properties for the used IP version and use that value for the bandwidth derivation as defined in 3GPP TS 26.114 [41]. + +NOTE 2: If no IP version is included for any of the "a=bw-info" SDP attribute lines related to a certain payload type and direction then IPv6 is assumed for all bandwidth properties related to the same direction and payload type, on all of the related "a=bw-info" SDP attribute lines, see clause 19 of 3GPP TS 26.114 [41]. + +If "a=bw-info" is used for bandwidth derivation and it includes both known and unknown bandwidth properties, the P-CSCF shall only consider the known bandwidth properties to derive the bandwidth information and ignore the unknown ones. If the "a=bw-info" line is received with an unknown directionality, then the entire "a=bw-info" line shall be ignored. + +For the possibly associated RTCP IP flows, the P-CSCF shall use the SDP "b=RR" and "b=RS" parameters, if present, as specified in 3GPP TS 29.213 [9] clause 6.2. The "b=AS", "b=RR" and "b=RS" parameters in the SDP contain all the overhead coming from the IP-layer and the layers above, e.g. IP, UDP, RTP and RTCP payload, or IP, UDP and RTCP. + +For multiplexed RTP/RTCP flows (as negotiated using the "a=rtcp-mux" SDP attribute defined in IETF RFC 5761 [42], a P-CSCF supporting RTP/RTCP transport multiplexing shall derive the bandwidth information within the service information as specified in 3GPP TS 29.213 [9] clause 6.2. + +However, if service information is received containing the "b=TIAS" SDP parameter that corresponds to an SDP answer payload, and if the P-CSCF supports this parameter, the P-CSCF may derive the bandwidth from this parameter rather than from the "b=AS" SDP parameter, as detailed in 3GPP TS 29.213 [9] clause 6.2. + +When available, the P-CSCF shall also indicate to PCRF, as a complement to the Service Information, the IMS Communication Service Identifier within the AF-Application-Identifier AVP. The originating P-CSCF shall take the IMS Communication Service Identifier value from the SIP response. The terminating P-CSCF shall take the IMS Communication Service Identifier value from the SIP request. Otherwise, the P-CSCF may not be able to provide an IMS Communication Service Identifier value to the PCRF. The format and specific headers where IMS communication service identifiers are transported within SIP are defined in 3GPP TS 24.229 [17]. + +NOTE 3: In order to indicate the IMS Communication Service Identifier to the PCRF, the originating P-CSCF sets the AF-Application-Identifier AVP to the ICSI contained in the topmost occurrence of the "+g.3gpp.icsi-ref" header field parameter of the Feature-Caps header field(s) of 18x or 2xx SIP response (Feature-Caps: \*;+g.3gpp.icsi-ref="urn%Aurn-7%A3gpp-service.ims.icsi.mmtel") and the terminating P-CSCF sets the AF-Application-Identifier AVP to the ICSI of the P-Asserted-Service header information received in the SIP request (e.g. P-Asserted-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel). Since the headers and the format of the ICSI can vary depending on the case, the PCRF has to be prepared to accept the complete ICSI information received in different formats, as described in clause 7.2A.8.2 in 3GPP TS 24.229 [17]. + +Additionally, the P-CSCF may include the Sharing-Key-DL AVP and/or Sharing-Key-UL AVP within the Media-Component-Description AVP in order to indicate the PCRF that resource sharing should apply for the media components in the related direction with the same value for the Sharing-Key-DL AVP and/or Sharing-Key-UL AVP. + +Additionally, if PrioritySharing feature is supported, the P-CSCF may provide the Priority-Sharing-Indicator AVP within the Media-Component-Description AVP as described in clause 4.4.47. + +NOTE 4: The P-CSCF obtains this information from the Application Server as described in 3GPP TS 23.228 [16], clause 5.4.7.9. + +NOTE 5: RTCP flows are not subject to resource sharing. This requirement cannot be met for multiplexed RTP/RTCP flows as in this case there is no mechanism in the current release to distinguish between RTP and RTCP flows. + +If the Service-URN AVP does not include an emergency service URN, i.e. a top-level service type of "sos" as specified in IETF RFC 5031 [21] and possibly additional sub-service information on the type of the emergency service and the PCRF binds the IMS service session to an IP-CAN session established to an Emergency APN, the PCRF shall return an AAA command with Experimental-Result-Code AVP set to the value UNAUTHORIZED\_NON\_EMERGENCY\_SESSION to the P-CSCF. Upon receiving an AAA with Experimental-Result-Code AVP set to the value UNAUTHORIZED\_NON\_EMERGENCY\_SESSION the P-CSCF shall apply the procedures defined in 3GPP TS 24.229 [17]. + +NOTE 6: The PCRF determines whether an IP-CAN session is established to an Emergency APN based on the information received over Gx and operator configuration. + +If the AF-Requested-Data AVP is provided in the AA-Request command indicating "EPC-level Identities required", the PCRF shall provide the available user information for the IP-CAN session within the Subscription-Id AVP(s) and/or User-Equipment-Info AVP or User-Equipment-Info-Extension AVP if the User-Equipment-Info-Extension feature is supported. + +The PCRF may decide not to authorize requested service information. The PCRF will indicate it to the P-CSCF by sending an AA-Answer with Experimental-Result-Code AVP set to the value REQUESTED\_SERVICE\_NOT\_AUTHORIZED. Upon receiving an AA-Answer with Experimental-Result-Code AVP set to the value REQUESTED\_SERVICE\_NOT\_AUTHORIZED the P-CSCF shall apply the procedures defined in 3GPP TS 24.229 [17]. + +## --- A.2 Enabling of IP Flows + +### A.2.0 General + +Prior to the completion of the SIP session set-up, i.e. until the 2xx response to the INVITE request is received, the P-CSCF may enable or disable media IP flows depending on operator policy, thus allowing or forbidding early media in forward and/or backward direction. The P-CSCF may set the values of the Flow-Status AVPs derived from the SDP direction attributes as defined in 3GPP TS 29.213 [9] clause 6.2 or set the values of the Flow-Status AVPs considering the em-param of the P-Early-Media header field according to clause A.2.1 or downgrade the values of the Flow-Status AVPs derived from the SDP direction attribute based on the configuration in the P-CSCF according to clause A.2.2. However for multiplexed RTP/RTCP flows (as negotiated using the "a=rtcp-mux" SDP attribute defined in IETF RFC 5761 [42]), a P-CSCF supporting RTP/RTCP transport multiplexing shall set the Flow-Status set to "ENABLED" to prevent that RTCP is blocked. If the P-CSCF chooses to modify the values of the Flow-Status AVPs as received from the SDP direction attribute, the P-CSCF shall store the last received SDP. + +When a 2xx response is received, the P-CSCF shall enable all media IP flows according to the direction attribute within the last received SDP, as specified in 3GPP TS 29.213 [9] clause 6.2. When a 2xx response is received and the P-CSCF previously provided the values of the Flow-Status AVPs different from the value derived from the SDP direction attribute in the session information, the P-CSCF shall provide service information with values of the Flow-Status AVPs corresponding to the last received SDP. + +NOTE: In most cases a 2xx response is a 200 (OK) response. + +If the P-CSCF receives SDP answers after the completion of the SIP session set-up, i.e. after the 2xx response to the INVITE request is received, the P-CSCF shall provide the Flow-Status AVP, based on the last received SDP answer. The Flow-Status AVP shall be derived from the SDP according to 3GPP TS 29.213 [9] clause 6.2. + +#### A.2.1 Gate control procedures considering the P-Early-Media header field + +Prior to the completion of the SIP session set-up, the P-CSCF may use the em-param of the P-Early-Media header field defined in IETF RFC 5009 [48] in order to enable or disable early media in forward and/or backward direction. If the P-CSCF uses the em-param of the P-Early-Media header field for the gate control of early media, the P-CSCF shall perform the following procedures. + +In the terminating P-CSCF, when a SIP message with the P-Early-Media header field is received from the UE and the policies configured in the P-CSCF indicate that the UE is authorized to send early media, then: + +- 1) the P-CSCF shall set the Flow-Status AVP to "ENABLED" if: + - the received em-param(s) in the P-Early-Media header field includes "sendrecv" and the last received SDP direction attribute from the UE is "sendrecv" or no SDP direction attribute has been received; or +- 2) the P-CSCF shall set the Flow-Status AVP to "ENABLED-UPLINK" if: + - the received em-param(s) in the P-Early-Media header field includes "sendrecv" and the last received SDP direction attribute from the UE is "sendonly"; or + - the received em-param(s) in the P-Early-Media header field includes "sendonly" and the last received SDP direction attribute from the UE is "sendrecv" or "sendonly" or no SDP direction attribute has been received; or +- 3) the P-CSCF shall set the Flow-Status AVP to "ENABLED-DOWNLINK" if: + - the received em-param(s) in the P-Early-Media header field includes "sendrecv" and the last received SDP direction attribute from the UE is "recvonly"; or + - the received em-param(s) in the P-Early-Media header field includes "recvonly" and the last received SDP direction attribute from the UE is "sendrecv" or "recvonly" or no SDP direction attribute has been received; or +- 4) the P-CSCF shall set the Flow-Status AVP to "DISABLED" if either the received em-param(s) in the P-Early-Media header field or the last received SDP direction attribute from the UE includes "inactive"; or +- 5) the P-CSCF may set the Flow-Status AVP to "DISABLED" or apply the rules defined in clause A.2.2 if the received em-param(s) in the P-Early-Media header field includes "sendonly" or "recvonly" and the last received SDP direction attribute from the UE is "recvonly" or "sendonly" respectively. + +NOTE 1: If the UE is authorized to send early media, the P-CSCF will not remove or modify the P-Early-Media header field according to 3GPP TS 24.229 [17]. + +When a SIP message with the P-Early-Media header field is received from the functional entity within the trust domain, and if: + +- the P-Early-Media header field includes the "gated" parameter, then the P-CSCF may decide not to perform the gate control of early media; or +- the P-Early-Media header field does not include the "gated" parameter, then the P-CSCF shall perform the following procedures: + - 1) the P-CSCF shall set the Flow-Status AVP to "ENABLED" if: + - the received em-param(s) in the P-Early-Media header field includes "sendrecv" and the last received SDP direction attribute from the functional entity is "sendrecv" or no SDP direction attribute has been received; or + - 2) the P-CSCF shall set the Flow-Status AVP to "ENABLED-DOWNLINK" if: + - the received em-param(s) in the P-Early-Media header field includes "sendrecv" and the last received SDP direction attribute from the functional entity is "sendonly"; or + +- the received em-param(s) in the P-Early-Media header field includes "sendonly" and the last received SDP direction attribute from the functional entity is "sendrecv" or "sendonly" or no SDP direction parameter has been received; or +- 3) the P-CSCF shall set the Flow-Status AVP to "ENABLED-UPLINK" if: +- the received em-param(s) in the P-Early-Media header field includes "sendrecv" and the last received SDP direction attribute from the functional entity is "recvonly"; or + - the received em-param(s) in the P-Early-Media header field includes "recvonly" and the last received SDP direction attribute from the functional entity is "sendrecv" or "recvonly" or no SDP direction parameter has been received ; or +- 4) the P-CSCF shall set the Flow-Status AVP to "DISABLED" if either the received em-param(s) in the P-Early-Media header field or the last received SDP direction attribute from the functional entity includes "inactive"; or +- 5) the P-CSCF may set the Flow-Status AVP to "DISABLED" or apply the rules defined in clause A.2.2 if the received em-param(s) in the P-Early-Media header field includes "sendonly" or "recvonly" and the last received SDP direction attribute from the functional entity is "recvonly" or "sendonly" respectively. + +NOTE 2: According to IETF RFC 5009 [48], the non-direction parameter "gated" can be included after the direction parameter (e.g. "sendrecv") in the parameter list. The proxy performing gating of early media can add the parameter before forwarding the SIP message. + +When a SIP message without the P-Early-Media header field is received from either the functional entity within the trust domain or the UE that is authorized to send early media, then the P-CSCF may set the Flow-Status AVP to "DISABLED" or apply the rules defined in clause A.2.2 or apply the rules defined in 3GPP TS 29.213 [9] clause 6.2. + +NOTE 3: As indicated in IETF RFC 5009 [48] the applicable preconditions need to be met in order to allow early media in a particular direction. + +When a SIP message is received from the functional entity other than the functional entity within the trust domain or the UE that is authorized to send early media, then the P-CSCF shall not use the received em-param(s) in the P-Early-Media header field and may apply the rules defined in clause A.2.2 or apply the rules defined in 3GPP TS 29.213 [9] clause 6.2. + +NOTE 4: The P-CSCF will remove or modify the P-Early-Media header field in the above case. + +#### A.2.2 Gate control procedures based on the configuration in the P-CSCF + +Prior to the completion of the SIP session set-up, the P-CSCF may downgrade the values of the Flow-Status AVPs derived from the SDP direction attributes based on the configuration in the P-CSCF. If the P-CSCF has the configuration for the gate control of early media, the P-CSCF shall perform the following procedures. + +NOTE: The gate control of early media can be configured in the P-CSCF per UE basis. + +When the Flow-Status AVP derived from the SDP direction attribute is "ENABLED", then the P-CSCF may downgrade the value of the Flow-Status AVP to the value "DISABLED", "ENABLED\_UPLINK", or "ENABLED\_DOWNLINK" based on the configuration in the P-CSCF. + +When the Flow-Status AVP derived from the SDP direction attribute is "ENABLED\_UPLINK" or "ENABLED\_DOWNLINK", then the P-CSCF may downgrade the value of the Flow-Status AVP to the value "DISABLED" based on the configuration in the P-CSCF. + +## A.3 Support for SIP forking + +### A.3.0 General + +The P-CSCF shall be able to handle forking when PCC is applied. Forking can occur as specified in 3GPP TS 23.228 [16]. The related UE procedures are described in 3GPP TS 24.229 [17]. + +#### A.3.1 PCC rule provisioning for early media for forked responses + +When a SIP session has been originated by a connected UE, the P-CSCF may receive multiple provisional responses due to forking before the first final answer is received. Multiple early media session may be established during this process. + +The UE and the P-CSCF become aware of the forking only when a subsequent provisional response arrives for a new early dialogue. After the first early media session is established, for each subsequent provisional response establishing an additional early media session,, the P-CSCF shall use an AA request within the existing Diameter session containing the SIP-Forking-Indication AVP with value SEVERAL\_DIALOGUES and include the service information derived from the latest provisional response. + +The P-CSCF shall also provision the service information derived from any subsequent SDP offer-answer exchange within an early dialogue (e.g. in PRACK and OK(PRACK), or UPDATE and OK(UPDATE) ) using an AA request within the existing Diameter session containing the SIP-Forking-Indication AVP with value SEVERAL\_DIALOGUES and the derived service information. + +When receiving an AA request containing the SIP-Forking-Indication AVP with value SEVERAL\_DIALOGUES, the PCRF shall identify the existing authorization information for that AF session. The PCRF shall send additional PCC Rules or individual service data flow filters to already provide PCC rules as required by the Flow Description AVPs within the session information to the PCEF. The PCRF shall authorize any additional media components and any increased QoS requirements for the previously authorized media components, as requested within the service information. The PCRF shall authorize the maximum bandwidth required by any of the dialogues, but not the sum of the bandwidths required by all dialogues. Thus, the QoS authorized for a media component is equal to the highest QoS requested for that media component by any of the forked responses. The PCRF shall open or close the gates for service flows depending on the flow status that is being provisioned. However, if a flow ID has been enabled in uplink or downlink direction or both way within previous service information, it shall remain enabled even if the PCRF receives service information that disable this flow ID within an AA request containing the SIP-Forking-Indication AVP with value SEVERAL\_DIALOGUES. + +If the P-CSCF provides one or more Media-Component-Description AVP with the Flow-Status AVP set to "REMOVED" for previously authorized media component(s) the media component shall remain as authorized and the PCRF shall not take any action on that media component(s). + +**NOTE:** There can be cases where a forked response could not support some of the media components included in the SDP Offer (e.g. when early session disposition SDP as described in Annex A.7 applies, the forked response related to the early session could include the port set to zero for those media components not related to the early session or when a subsequent SDP Offer-Answer to indicate that some media is disabled). For those cases the P-CSCF will indicate the PCRF about the removal of the corresponding media component. However this media component is already supported by other UEs and the PCRF needs to maintain the corresponding PCC rules until the final SDP answer is received in the P-CSCF in order to avoid the release of resources in the network. + +#### A.3.2 Updating the provisioned PCC rules at the final answer + +The P-CSCF shall store the SDP information for each early dialogue separately till the first final SIP answer is received. Then the related early dialogue is progressed to an established dialogue to establish the final SIP session. All the other early dialogues are terminated. The service information for the SIP session is updated to match the requirements of the remaining early dialogue only. + +When receiving the first final SIP response, the P-CSCF shall send an AA request without the SIP-Forking-Indication AVP and include the service information derived from the SDP corresponding to the dialogue of the final response. The P-CSCF shall provision the full service information including the applicable Flow-Description AVP(s) and Flow-Status AVP(s). + +When receiving an AA request with no SIP-Forking-Indication AVP or with a SIP-Forking-Indication AVP with value SINGLE\_DIALOGUE, the PCRF shall update installed PCC Rules information and Authorized-QoS information to match only the requirements of the service information within this AA request. The PCRF should immediately remove PCC Rule(s) or individual service data flow filters not matching IP flow(s) in the updated Service Information, to reduce the risk for initial clipping of the media stream, and to minimize possible misuse of resources. The PCRF shall also open or close the gates for service flows according to the flow status in the received service information. + +## --- A.4 Notification of AF Signalling Transmission Path Status + +When the P-CSCF receives an initial REGISTER SIP message from an attached UE, the P-CSCF may subscribe to notifications of the status of the AF Signalling transmission path using the procedures specified in clause 4.4.5. Once the P-CSCF has subscribed, the P-CSCF may receive notifications from the PCRF according to clause 4.4.6.3. + +NOTE 1: When the Standardised QCI characteristics as defined in 3GPP TS 23.203 [2] are followed, the QCI for IMS signalling will correspond to a non-GBR bearer. In this case, the P-CSCF will not receive notifications related to the Specific-Action with value "INDICATION\_OF\_LOSS\_OF\_BEARER". + +NOTE 2: This procedure is not applicable for IMS registrations for Emergency sessions. + +The P-CSCF shall cancel the subscription to notification of the status of the AF Signalling transmission path when the AF Signalling to that particular user is terminated (i.e. when the user is de-REGISTERED from the IM CN subsystem). + +When the P-CSCF receives a notification of loss of signalling connectivity from the PCRF, the P-CSCF shall behave as defined in 3GPP TS 24.229 [17]. + +## --- A.5 Indication of Emergency Registration and Session Establishment + +When the P-CSCF receives an initial REGISTER SIP message for an IMS emergency registration or an INVITE SIP message for an emergency session and the P-CSCF determines that there are no IMS-level roaming interfaces, the P-CSCF may request the PCRF to provide the EPC-level identities (MSISDN, IMSI, IMEI(SV)) available for that IP-CAN session using the procedure as specified in this clause (for an IMS emergency registration) or A.1 (for an IMS emergency session establishment). An P-CSCF may request the PCRF to provide the EPC-level identities (MSISDN, IMSI, IMEI(SV)) available for that IP-CAN session when no service information is available in the AF. To do so, the P-CSCF shall open an Rx Diameter session with the PCRF for the AF signalling using an AA-Request command. The P-CSCF shall provide the UE's IP address (using either the Framed-IP-Address AVP or the Framed-Ipv6-Prefix AVP) and the AF-Requested-Data AVP set to "EPC-level identities required". The AF shall include the Service-URN AVP set to the value "sos", in order to indicate that the new AF session relates to emergency traffic that is not related to a specific emergency service. + +When the PCRF receives an AA-Request command as described in the preceding paragraphs from the P-CSCF, the PCRF shall perform session binding as described in 3GPP TS 29.213 [9]. When the PCRF receives the Service-URN AVP indicating an emergency session, the PCRF may apply special policies, for instance prioritising service flows relating to the AF session or allowing these service flows free of charge. When the Service-URN AVP indicates that the AF session relates to emergency traffic and the AF-Requested-Data AVP is received indicating "EPC-level Identities required", the PCRF shall provide the requested available user information (MSISDN, IMSI) for the IP-CAN session within the Subscription-Id AVP(s) and/or the IMEI(SV) within the User-Equipment-Info AVP or the User-Equipment-Info-Extension AVP if the User-Equipment-Info-Extension feature is supported, in the AA-Answer command. + +When the P-CSCF receives the AA-Answer with the EPC-level identities from the PCRF, the P-CSCF stores the information received within the Subscription-Id AVP(s) and/or User-Equipment-Info AVP or User-Equipment-Info- + +Extension AVP if the User-Equipment-Info-Extension feature is supported, provided by the PCRF and behaves as defined in 3GPP TS 24.229 [17]. + +NOTE: The user information received within the User-Equipment-Info AVP or the User-Equipment-Info-Extension AVP if the User-Equipment-Info-Extension feature is supported, and/or Subscription-Id AVP(s) can be used to support PSAP callback functionality for anonymous IMS emergency sessions. See 3GPP TS 23.167 [53] for further information. + +The P-CSCF may decide to terminate the Rx session at any time. In that case, the AF shall use a Session-Termination-Request (STR) command to the PCRF, which shall be acknowledged with a Session-Termination-Answer (STA) command. + +A SIP INVITE request can contain a service URN as defined in IETF RFC 5031 [21] within the request URI. If the service within this URN is "sos", possibly with additional sub-service information, the P-CSCF shall provision this service and sub-service information within the Service-URN AVP towards the PCRF. The P-CSCF may also provision possible information about other services received within the service URN. + +## --- A.6 Notification IP-CAN Type Change + +When the P-CSCF receives an initial REGISTER SIP message or an INVITE SIP message from an attached UE, the P-CSCF may request from the PCRF the information about the type of IP-CAN the UE is attached to using the procedure specified in clause 4.4.1. + +NOTE 1: This procedure is not applicable for IMS registrations for Emergency sessions. + +NOTE 2: The P-CSCF can request information about the type of IP-CAN as part of the SIP session setup when it is only interested in the related information when the IMS session is ongoing. + +If the P-CSCF requests information about the type of IP-CAN, the P-CSCF shall also subscribe within the same AAR command operation to notifications for changes of the IP-CAN type used by the UE. The P-CSCF shall include a Specific-Action AVP in the AAR that is set to the value of IP-CAN\_CHANGE. + +When the P-CSCF receives the AA-Answer or RA-Request from the PCRF, the P-CSCF stores the IP-CAN type information received within the IP-CAN-Type AVP and the RAT type information received within the RAT-Type AVP and AN-Trusted AVP (if also provided by the PCRF) and behaves as defined in 3GPP TS 24.229 [17]. + +The P-CSCF may receive notifications for changes of the IP-CAN type from the PCRF according to clause 4.4.6.4. When the P-CSCF receives a notification of the change of the IP-CAN used by the UE, the P-CSCF stores the new IP-CAN type information and RAT type information and behaves as defined in 3GPP TS 24.229 [17]. + +NOTE 3: The subscription to receive information about the type of IP-CAN will be cancelled when the corresponding Rx session is terminated by the AF (i.e. when the UE is de-REGISTERED or the related SIP call is torn down). + +## --- A.7 Support for Early Session disposition SDP + +### A.7.1 General + +As a network option, the P-CSCF may support the PCC procedures in the present Clause to handle "early session" disposition type SDP, as standardised in IETF RFC 3959 [27]. + +### A.7.2 Service Information Provisioning for Early Media + +The P-CSCF can receive "early session" disposition SDP in addition to "session" disposition SDP in SIP early dialogues. + +The P-CSCF shall then provision service information derived both from the "early session" disposition SDP and "session" disposition SDP applying the procedures in Clauses A.1, A.2, and A.3, and in the present Clause. + +The P-CSCF shall apply the mapping rules in Annex B.1.2.2.2 to derive the flow identifiers from "early session" disposition SDP. + +If a single media line with one media type (e.g. "audio" or "video") is contained in "early session" disposition SDP and a single media line with the same media type is contained in the "session" disposition SDP of the same SIP dialogue, and both media lines describe service flows of the same directionality (uplink, downlink, or bidirectional), the P-CSCF should describe those SDP media lines in the same session information media component (with the same flow ID). + +The "early session" disposition SDP can also contain media lines of a type not included in the "session" disposition SDP, or several media lines of the same type. Such media components shall be described in own media components in the service information. + +If the P-CSCF desires to invoke special policies or separate event notifications for an "early session" disposition media line, it may choose to provision a separate session information media component even if a media line with the same media type and directionality is contained in "session" disposition SDP. + +NOTE 1: A PCRF is then likely to supply separate PCC rules for early media and the corresponding final media. This may lead to an over provisioning of resources during call establishment and a subsequent reconfiguration of the radio bearer, or even to a call failure if the extra resources are not authorized or available. + +If the P-CSCF receives "early session" disposition SDP before any "session" disposition SDP and supplies service information derived from the "early session" disposition SDP at this point of time, it shall use dedicated media components relating only to the "early session" disposition SDP in the service information. + +NOTE 2: The "session" disposition SDP offer will frequently occur before the "early session" disposition SDP offer, but can also occur in parallel or in exceptional cases afterwards. The "session" disposition SDP answer can be contained in the same SIP message as the "early session" disposition SDP offer, or can be sent in a 200 OK (INVITE), i.e. after the "early session" disposition SDP answer. + +If the P-CSCF includes any media component relating both to "early session" disposition SDP and "session" disposition SDP in the service information, the P-CSCF shall: + +- provision the service information derived from "early session" disposition SDP and the service information derived from "session" disposition SDP in separate Rx AA-Requests, and shall send a new Rx AA-Request only after any previous Rx AA-Request has been acknowledged; and +- provision the first service information (either derived from "early session" disposition SDP or "session" disposition SDP) without the SIP-Forking-Indication AVP, or with the SIP-Forking-Indication AVP with value SINGLE\_DIALOGUE; and +- provision all subsequent service information during ongoing call establishment with the SIP-Forking-Indication AVP with value SEVERAL\_DIALOGUES; and +- if an SDP answer has been received and Codec-Data AVPs are provisioned within a Media-Component-Description AVP, provision a Codec-Data AVP derived from the corresponding offer together with a Codec-Data AVP derived from the SDP answer. + +NOTE 3: The P-CSCF needs to provision the service information derived from "early session" disposition SDP and the service information derived from "session" disposition SDP in separate Rx AA-Requests because the encoding of the media-component does not allow for the simultaneous provisioning of two corresponding filters. + +NOTE 4: The PCRF will treat service information containing the SIP-Forking-Indication AVP as described in Clause A.3. + +### A.7.3 Updating the Provisioned Service Information when Dialogue is established + +The P-CSCF shall store the SDP information for the "session" disposition type until the first final SIP answer is received. Then the early media described in the "early session" disposition type SDP are terminated. + +The P-CSCF shall then update the service information to match the requirements of the media described in the "session" disposition type SDP only: + +- If the P-CSCF included any media component relating both to "early session" disposition SDP and "session" disposition SDP in the service information, the P-CSCF shall send an AA request without the SIP-Forking-Indication AVP or with a SIP-Forking-Indication AVP with value SINGLE\_DIALOGUE and shall include the service information derived from the "session" disposition SDP. The P-CSCF shall provision the full service information including the applicable Flow-Description AVP(s) and Flow-Status AVP(s). +- The P-CSCF shall disable any media component(s) in the service information that relate to early media only by setting their flow status to "removed". + +## --- A.8 Provision of Signalling Flow Information at P-CSCF + +When the P-CSCF has successfully concluded the initial registration of an attached UE, i.e., when the P-CSCF has sent to the UE a SIP 200 (OK) response to the SIP REGISTER request, the P-CSCF may provision information about the SIP signalling flows between the UE and itself using the procedure specified in clause 4.4.5A. If the P-CSCF already has an open Rx Diameter session with the PCRF related to the signalling with the UE, e.g. one that has been opened according to the procedure described in clause A.6 and/or in clause A.4, the P-CSCF shall reuse the already open session to provision the SIP Signalling IP Flow information. + +NOTE: This procedure is not applicable for IMS registrations for Emergency sessions. + +If the P-CSCF provisions information about SIP signalling flows, the P-CSCF shall ensure that for each signalling IP flow information it provides, the Flow-Description AVP shall accurately reflect the IP flow information as seen in the IP header 'on the wire'. The P-CSCF shall set the value of the AF-Signalling-Protocol AVP to 'SIP'. + +When the P-CSCF de-registers the UE and terminates SIP Signalling to the UE, the P-CSCF shall de-provision the SIP Signalling IP flow information from the PCRF as described in clause 4.4.5A. + +## --- A.9 Handling of MPS Session + +When the P-CSCF receives an authorised Resource-Priority header field or a temporarily authorised Resource-Priority header field containing an appropriate namespace and priority value in SIP signaling, and recognizes the need for priority treatment as specified in 3GPP TS 24.229 [17], the P-CSCF shall include the MPS-Identifier AVP and Reservation-Priority AVP in the AAR command towards the PCRF. The MPS-Identifier AVP shall contain the national variant for MPS service name indicating an MPS session. The Reservation-Priority AVP shall include the priority value of the related priority service. The Reservation-Priority AVP shall be populated with a default value if the priority value is unknown. + +NOTE 1: Various mechanisms can be applied to recognize the need for priority treatment in the P-CSCF (e.g., based on the dialled digits), according to national regulation and network configuration, as stated in 3GPP TS 24.229 [17]. + +NOTE 2: Lowest user priority value is mapped in the corresponding lowest enumerated value of the Reservation-Priority AVP. + +If the P-CSCF supports the Diameter message priority mechanism for an MPS session, it shall include the DRMP AVP towards the PCRF as described in 3GPP TS 29.213 [9], Annex J. + +NOTE 3: If the P-CSCF supports the Diameter message priority mechanism for an MPS session, it includes the DRMP AVP with a priority value equivalent to the Reservation-Priority AVP priority value. Highest user priority value is mapped in the corresponding lowest enumerated value of the DRMP AVP. + +Upon reception of a request that requires MPS treatment, the PCRF shall derive the PCC/QoS Rules corresponding to the MPS session, as appropriate. The PCRF shall take specific actions on the corresponding IP-CAN to ensure that the MPS session is prioritized, as described in 3GPP TS 29.212 [8], clause 4.5.19.1.3. + +When the P-CSCF terminates the MPS session, the PCRF shall delete the PCC/QoS Rules corresponding to the MPS session. The PCRF shall revoke the actions related to the prioritization of the MPS session in the corresponding IP-CAN, as described in 3GPP TS 29.212 [8], clause 4.5.19.1.3. + +## --- A.10 Retrieval of network provided location information + +### A.10.1 General + +According to Annex E.7 of 3GPP TS 23.228 [16], the P-CSCF can use PCC to retrieve network provided location information. Information flows related to the distribution of network provided location information within the IMS are provided in Annex R of 3GPP TS 23.228 [16]. + +This subclause provides optional PCC procedures to support the retrieval of network provided location information. + +The originating P-CSCF can, depending on operator policy, retrieve the user location and/or UE Time Zone information either before sending the INVITE or MESSAGE towards the terminating side or upon reception of the SDP answer from the terminating side. + +The terminating P-CSCF can, depending on operator policy, retrieve the user location and/or UE Time Zone information either upon reception of a SIP INVITE or upon reception of a SIP response. + +The originating and terminating P-CSCF can, depending on operator policy, retrieve the user location and/or UE Time Zone information at mid call, e.g., when the P-CSCF learns about IP-CAN type change. + +### A.10.2 Retrieval of network provided location information at originating P-CSCF for inclusion in SIP Request + +If the originating P-CSCF is required by operator policy to retrieve network provided location information before forwarding a SIP INVITE request, upon reception of an INVITE/UPDATE request, the P-CSCF shall send an AA-Request according to clause 4.4.1 (SIP INVITE request) or 4.4.2 (SIP INVITE/UPDATE request) including: + +- the "ACCESS\_NETWORK\_INFO\_REPORT" value within the Specific-Action AVP; and +- the required access network information within the Required-Access-Info AVP. + +If the SIP INVITE request is an initial SIP INVITE request, the P-CSCF shall establish an Rx session for the new SIP session with the AA-Request according to clause 4.4.6.7 (if no session information is included) or 4.4.1 (if preliminary session information is included). + +The P-CSCF will receive the access network information from the PCRF in an RAR, and should include this access network information in the SIP INVITE/UPDATE requests that it forwards. When the retrieved access network information corresponds to the TWAN-Identifier AVP, the P-CSCF may also map the retrieved access network information to a Geographical Identifier for routing, as specified in Annex E.8 of 3GPP TS 23.228 [16]. + +### A.10.3 Retrieval of network provided location information at originating P-CSCF for inclusion in SIP response confirmation + +If an originating P-CSCF is required by operator policy to retrieve network provided location information before forwarding an SDP answer, the P-CSCF shall apply the following procedures: + +Upon reception of an SDP offer, the P-CSCF may send an AA-Request to the PCRF according to clause A.1 and may include in this AA-request: + +- the "ACCESS\_NETWORK\_INFO\_REPORT" value within the Specific-Action AVP; and +- the required access network information within the Required-Access-Info AVP. + +Upon reception of an SDP answer, the P-CSCF will send an AA-Request to the PCRF according to clause A.1. If the P-CSCF has not requested access network information upon reception of the SDP offer, the P-CSCF shall include in this AA-request: + +- the "ACCESS\_NETWORK\_INFO\_REPORT" value within the Specific-Action AVP; and +- the required access network information within the Required-Access-Info AVP. + +The P-CSCF will receive the access network information from the PCRF in an RAR, and should include this access network information in the SIP message with the response confirmation before forwarding it. When the retrieved access network information corresponds to the TWAN-Identifier AVP, the P-CSCF may also map the retrieved access network information to a Geographical Identifier for routing, as specified in Annex E.8 of 3GPP TS 23.228 [16]. + +If the originating P-CSCF is required by operator policy to retrieve network provided location information before forwarding a SIP MESSAGE request, upon reception of a MESSAGE request, the P-CSCF shall send an AA-Request including: + +- the UE's IP address (using either the Framed-IP-Address AVP or the Framed-Ipv6-Prefix AVP); +- a Media-Component-Description AVP including a single Media-Sub-Component AVP with the Flow-Usage AVP set to the value "AF\_SIGNALLING". The Media-Component-Description AVP shall contain the Media-Component-Number AVP set to "0". The Media-Sub-Component AVP shall contain the Flow-Number AVP set to "0", and the rest of AVPs within the Media-Component-Description and Media-Sub-Component AVPs shall not be used in this case; +- the "ACCESS\_NETWORK\_INFO\_REPORT" value within the Specific-Action AVP; and +- the required access network information within the Required-Access-Info AVP. + +The P-CSCF will receive the access network information from the PCRF in an RAR and should include this access network information in the SIP MESSAGE requests that it forwards. When the retrieved access network information corresponds to the TWAN-Identifier AVP, the P-CSCF may also map the retrieved access network information to a Geographical Identifier for routing, as specified in Annex E.8 of 3GPP TS 23.228 [16]. + +If the Rx Diameter Session is only used for retrieval of network provided location information, at reception of this information, the AF may terminate the AF session sending a Session-Termination-Request (STR) command to the PCRF, which shall be acknowledged with a Session-Termination-Answer (STA) command. + +### A.10.4 Retrieval of network provided location information at terminating P-CSCF + +If a terminating P-CSCF is required by operator policy to retrieve network provided location information at session establishment and/or modification, the P-CSCF shall apply the following procedures: + +The terminating P-CSCF may request network provided location information upon reception of a SIP INVITE request : in the following manner: + +- If the SIP INVITE request is an initial SIP INVITE request, the P-CSCF shall establish an Rx session for the new SIP session with the AA-Request according to clause 4.4.6.7 (if no session information is included) or 4.4.1 (if preliminary session information is included). +- If the SIP INVITE includes an SDP offer, the P-CSCF shall send an AA-Request including: + - the "ACCESS\_NETWORK\_INFO\_REPORT" value within the Specific-Action AVP; + - the required access network information within the Required-Access-Info AVP; + - service information derived from the SDP offer; and + - the Service-Info-Status AVP with the value set to PRELIMINARY SERVICE INFORMATION. +- If the SIP INVITE includes no SDP offer, the P-CSCF shall send an AA-Request including: + - the "ACCESS\_NETWORK\_INFO\_REPORT" value within the Specific-Action AVP; and + - the required access network information within the Required-Access-Info AVP. + +Upon reception of a SIP response that requires the inclusion of access network information, if the P-CSCF has not already requested network provided location information upon reception of the corresponding SIP INVITE, the P-CSCF shall request network provided location information in the following manner: + +- If an Rx session related to service data has not yet been established, the P-CSCF shall establish an Rx session for the new SIP session with the AA-Request according to clause 4.4.6.7 (if no session information is included) or 4.4.1 (if session information is included). +- If the SIP response includes an SDP answer, the P-CSCF will send an AA-Request to the PCRF according to clause A.1; the P-CSCF shall include in this AA-request: + - the "ACCESS\_NETWORK\_INFO\_REPORT" value within the Specific-Action AVP; and + - the required access network information within the Required-Access-Info AVP. +- If the SIP response includes no SDP, the P-CSCF shall send an AA-Request including: + - the "ACCESS\_NETWORK\_INFO\_REPORT" value within the Specific-Action AVP; and + - the required access network information within the Required-Access-Info AVP. +- If the SIP response includes an SDP offer, the P-CSCF shall send an AA-Request including: + - the "ACCESS\_NETWORK\_INFO\_REPORT" value within the Specific-Action AVP; + - the required access network information within the Required-Access-Info AVP; + - service information derived from an SDP offer within the SIP response; and + - the Service-Info-Status AVP with the value set to PRELIMINARY SERVICE INFORMATION. + +The P-CSCF will receive the access network information from the PCRF in an RAR, and should include this access network information in the appropriate SIP response before forwarding it. When the retrieved access network information corresponds to the TWAN-Identifier AVP, the P-CSCF may also map the retrieved access network information to a Geographical Identifier for routing, as specified in Annex E.8 of 3GPP TS 23.228 [16]. + +If the terminating P-CSCF is required by operator policy to retrieve network provided location information upon reception of a SIP MESSAGE response, the P-CSCF shall behave according to A.10.2. + +### A.10.5 Provisioning of network provided location information at SIP session release + +If a P-CSCF is required by operator policy to include network provided location information in SIP session release signalling, the P-CSCF shall apply the following procedures: + +Upon reception of a SIP session release request that requires the inclusion of network provided location information, the P-CSCF will send an ST-Request and shall include in this request the required access network information within the Required-Access-Info AVP. + +The P-CSCF will receive the access network information from the PCRF in the corresponding ST-Answer, and should include this access network information either in the SIP session termination request (at the originating side) or a reply to the SIP session termination request (at the terminating side). When the retrieved access network information corresponds to the TWAN-Identifier AVP, the P-CSCF may also map the retrieved access network information to a Geographical Identifier for routing, as specified in Annex E.8 of 3GPP TS 23.228 [16]. + +### A.10.6 Provisioning of network provided location information at mid call + +If a P-CSCF is required by operator policy to include network provided location information at mid call, the P-CSCF shall apply the following procedures: + +Upon reception of a trigger (e.g., when the P-CSCF learns about the access change) that requires the inclusion of network provided location information in a SIP message, the P-CSCF shall include in the AA-request: + +- the "ACCESS\_NETWORK\_INFO\_REPORT" value within the Specific-Action AVP; +- the required access network information within the Required-Access-Info AVP; and +- the service information related to the service according to clause 4.4.2. + +The P-CSCF will receive the access network information from the PCRF in an RAR, and should include this access network information in the appropriate SIP message before forwarding it. When the retrieved access network information corresponds to the TWAN-Identifier AVP, the P-CSCF may also map the retrieved access network information to a Geographical Identifier for routing, as specified in Annex E.8 of 3GPP TS 23.228 [16]. + +## --- A.11 Handling of RAN/NAS release cause values + +If the P-CSCF is required by operator policy to provide the RAN/NAS release cause information, it includes this information in the corresponding SIP message as specified in 3GPP TS 24.229 [17] when received from the PCRF (see clause 4.4.4, 4.4.6.1, 4.4.6.2, 4.4.6.3 and 4.4.6.7). + +## --- A.12 Resource Sharing + +The P-CSCF may indicate to the PCRF that media of an AF session may share resources with media belonging to other AF sessions according to 3GPP TS 23.228 [16]. + +If the P-CSCF determines that resource sharing is possible, it may at establishment of a new AF session, include the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP indicating that media resources may be shared in the related direction. The P-CSCF shall assign a distinct value for the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP for each media component identified by the Media-Component-Description AVP for the AF session. + +NOTE 1: When resource sharing applies to both directions for a certain media component, the P-CSCF can assign the same value for Sharing-Key-UL AVP and Sharing-Key-DL AVP within the same media component. + +The P-CSCF shall not include the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP within the Media-Component-Description AVP when the AF session relates to an Emergency Session. + +The PCRF shall not include the Sharing-Key-DL AVP and/or Sharing-Key-UL AVP for those PCC/QoS Rules related to the RTCP traffic. + +Trigger conditions that require applying or stopping resource sharing are described in 3GPP TS 24.229 [17]. + +NOTE 2: When P-CSCF needs to stop sharing according to the procedures described in 3GPP TS 24.229 [17], the P-CSCF will provide new values for the Sharing-Key-UL AVP and/or Sharing-Key-DL AVP that are not being used by any other AF sessions for the same user. + +## --- A.13 Handling of MCPTT priority call + +### A.13.1 General + +Within the framework of MCPTT, when the SIP Core (3GPP TS 23.379 [54]) is implemented by an IMS core network, if the P-CSCF receives a SIP request message including a Resource-Priority header field with a namespace field and priority value defined for MCPTT for adjusting the priority of an MCPTT session, the P-CSCF shall provide the Reservation-Priority AVP and the MCPTT-Identifier AVP in the AA-Request command as defined in clause A.13.2 to allow the PCRF to set the corresponding PCC rule(s) according to the prioritized MCPTT service. Additionally, if PrioritySharing feature is supported, the P-CSCF may provide the Priority-Sharing-Indicator AVP within the Media-Component-Description AVP as described in clause A.1. For MCPTT the service priority and the priority sharing indicator are defined in 3GPP TS 23.379 [54]. + +NOTE 1: The process of adjusting priority may occur several times during the course of one session, e.g. a normal MCPTT group call elevated to an MCPTT emergency group call, returned to a normal priority MCPTT group call, elevated to an MCPTT imminent peril group call and returned to a normal priority MCPTT group call. + +NOTE 2: Upon reception of a request that requires the adjustment of the MCPTT priority, the PCRF is expected to derive the PCC Rules corresponding to the this MCPTT session, as appropriate according to operator policies. + +NOTE 3: The PCRF can identify an MCPTT call using the IMS Communication Service Identifier specific to MCPTT, which is provided by the P-CSCF in the AF-Application-Identifier AVP in the AA-Request sent to PCRF. + +### A.13.2 Determination of MCPTT priority parameter values + +When the P-CSCF receives an authorized Resource-Priority header field containing an appropriate namespace and priority value used for MCPTT in SIP signaling, the P-CSCF shall include the MCPTT-Identifier AVP and Reservation-Priority AVP in the AAR command towards the PCRF. + +The MCPTT-Identifier AVP shall include the namespace defined for MCPTT as received within the Resource-Priority header field. + +NOTE: Two different values are defined for the MCPTT-Identifier AVP, one for each namespace value defined for MCPTT (see IETF RFC 8101 [45]). + +The Reservation-Priority AVP shall contain the priority value of the Resource-Priority header; the lowest priority shall be mapped to to DEFAULT (0), the next after the lowest to PRIORITY-ONE (1), and so on up to the highest priority which shall be mapped to PRIORITY-FIFTEEN (15). + +Additionally, when the P-CSCF receives information about priority sharing from an MCPTT server that supports simultaneous sessions and that needs to share a common priority for several MCPTT sessions and if PrioritySharing feature is supported, the P-CSCF may include the Priority-Sharing-Indicator AVP within the Media-Component-Description AVP in the AAR command. See 3GPP TS 23.379 [54] for further information. + +## --- A.14 Notification of PLMN Change + +When the P-CSCF receives an initial REGISTER SIP message from an attached UE, the P-CSCF may subscribe to notifications of PLMN ID changes corresponding to the PLMN where the UE is located using the procedure specified in clause 4.4.6.9. + +When the P-CSCF receives the AA-Answer or RA-Request from the PCRF, the P-CSCF stores the PLMN identifier received within 3GPP-SGSN-MCC-MNC AVP and behaves as defined in 3GPP TS 24.229 [17]. + +The P-CSCF shall cancel the subscription to notification for changes of the PLMN used by the UE when the user is de-registered from the IM CN subsystem. + +## --- A.15 Handling of MCVideo priority call + +### A.15.1 General + +Within the framework of MCVideo, when the SIP Core (3GPP TS 23.281 [61]) is implemented by an IMS core network, if the P-CSCF receives a SIP request message including a Resource-Priority header field with a namespace field and priority value defined for MCVideo for adjusting the priority of an MCVideo session, the P-CSCF shall provide the Reservation-Priority AVP and the MCVideo-Identifier AVP in the AA-Request command as defined in clause A.15.2 to allow the PCRF to set the corresponding PCC rule(s) according to the prioritized MCVideo service. + +- NOTE 1: The process of adjusting priority may occur several times during the course of one session, e.g. a normal MCVideo group call elevated to an MCVideo emergency group call and returned to a normal priority MCVideo group call, elevated to an MCVideo imminent peril group call and returned to a normal priority MCVideo group call. +- NOTE 2: Upon reception of a request that requires the adjustment of the MCVideo priority, the PCRF is expected to derive the PCC Rules corresponding to the this MCVideo session, as appropriate according to operator policies. +- NOTE 3: The PCRF can identify an MCVideo call using the IMS Communication Service Identifier specific to MCVideo, which is provided by the P-CSCF in the AF-Application-Identifier AVP in the AA-Request sent to PCRF. + +### A.15.2 Determination of MCVideo priority parameter values + +When the P-CSCF receives an authorized Resource-Priority header field containing an appropriate namespace and priority value used for MCVideo in SIP signaling, the P-CSCF shall include the MCVideo-Identifier AVP and Reservation-Priority AVP in the AAR command towards the PCRF. + +The MCVideo-Identifier AVP shall include the namespace defined for MCVideo as received within the Resource-Priority header field. + +The Reservation-Priority AVP shall contain the priority value of the Resource-Priority header; the lowest priority shall be mapped to to DEFAULT (0), the next after the lowest to PRIORITY-ONE (1), and so on up to the highest priority which shall be mapped to PRIORITY-FIFTEEN (15). + +## --- A.16 Support for volume based charging of IMS services + +As a network option, when VBC feature is supported, the P-CSCF may be able to indicate to the PCRF the establishment and termination of specific IMS communication services (e.g. CAT and voice calls, 3PTY conference) or the establishment and termination of different communication dialogues to separate parties. This enables PCC to apply different Policy and Charging control. During AF session establishment, the P-CSCF may include the IMS-Content-Identifier AVP and the IMS-Content-Type AVP in the AAR command towards the PCRF. The PCRF derives the PCC rules to categorise the service data flows by rating group or combination of rating group and service id. + +During AF session modification, the P-CSCF may include the IMS-Content-Identifier AVP and the IMS-Content-Type AVP in the AAR command towards the PCRF. The PCRF updates the PCC rules to categorise the service data flows by rating group or combination of rating group and service id. + +The IMS-Content-Type AVP indicates the type of IMS content of a session component. The P-CSCF determines the type of IMS content as follows: + +- If the SDP payload refers to the Customized Alerting Tones (CAT) service (i.e. SDP body contains a media-level "a=content" SDP attribute with a value "g.3gpp.cat" defined in 3GPP TS 24.182 [62]), the P-CSCF sets the IMS-Content-Type AVP with the value "CAT". +- If the SDP payload refers to the 3PTY conference service (i.e. SDP body contains an "a=content" media-level attribute line with value of "g.3gpp.conf" defined in 3GPP TS 24.147 [63]), the P-CSCF sets the IMS-Content-Type AVP with the value "CONFERENCE". +- Otherwise, the P-CSCF sets the IMS-Content-Type AVP with the value "NO\_CONTENT\_DETAIL". + +The IMS-Content-Identifier AVP contains information that identifies a particular IMS communication service or a particular communication dialogue in the IMS session. This information may be used by the PCRF to apply different charging characteristics to the different parties in a 3PTY conference scenario. + +As a network option, if VBCLTE feature is further supported, the P-CSCF shall be able to indicate to the PCRF caller and callee information. + +During AF session establishment, the P-CSCF may include the Calling-Party-Address AVP and the Callee-Information AVP in the AAR command towards the PCRF. The PCRF derives the PCC rules including the information of caller and callee. + +During AF session modification, the P-CSCF may include the Callee-Information AVP in the AAR command towards the PCRF. The PCRF updates the PCC rules to categorise the service data flows by rating group or combination of rating group and service id. + +The Calling-Party-Address AVP indicates the caller of the IMS service. The P-CSCF determines the caller as defined in clause 7.2.33 of 3GPP TS 32.299 [24]. + +The Callee-Information AVP indicates the callee of the IMS service. The P-CSCF determines the callee as follows: + +- The Called-Party-Address holds the address of the party (Public User ID or Public Service ID) to whom the SIP transaction is posted in the context of an end-to-end SIP transaction as defined in clause 7.2.32 in 3GPP TS 32.299 [24]. +- The Requested-Party-Address holds the address of the party (Public User ID or Public Service ID) to whom the SIP transaction was originally posted as defined in clause 7.2.176 in 3GPP TS 32.299 [24]. + +NOTE: This AVP is only applicable when the ATCF is collocated with the P-CSCF. + +- The Called-Asserted-Identity holds the address or addresses (SIP URI and/or Tel URI) of the party (Public User ID or Public Service ID) of the finally asserted called party as defined in clause 7.2.31 of 3GPP TS 32.299 [24]. + +## --- A.17 Indication of Restricted Local Operator Services Support + +RLOS is an optional feature supported in certain countries. Service requirements of RLOS are defined in 3GPP TS 22.101 [65] and the architectural requirements are defined in 3GPP TS 23.221 [66]. The RLOS stage 2 services description for the Evolved Packet System (EPS) is specified in 3GPP TS 23.401 [67]. The policy and charging control architecture is described in 3GPP TS 23.203 [2]. + +RLOS may be supported as described in clause A.5 with the following differences: + +- emergency registration is replaced by RLOS registration; +- emergency session is replaced by RLOS session; +- emergency traffic is replaced by RLOS traffic; +- value "sos" is replaced by "g.3gpp.rlos"; +- UNAUTHORIZED\_NON\_RLOS\_SESSION session is returned when the service-URN AVP does not include an RLOS value, and the PCRF binds the IMS session to an IP-CAN established to an RLOS APN; + +- RLOS services are not prioritized services; and +- the call back functionality is not required. + +## --- A.18 Coverage and Handoff Enhancements using Multimedia error robustness feature (CHEM) + +As a network option, the P-CSCF may support the PCC procedures in the present clause to handle the Coverage and Handoff Enhancements using Multimedia error robustness feature (CHEM) + +NOTE 1: When the CHEM feature is supported, improved error robustness can be enabled by packet-loss handling procedures of the codec, codec mode, or codec configuration to avoid, delay, or reduce the need to handoff a terminal due to degradation in the media quality. Communicating the level of robustness of the media to the network enables the eNB to use this information to determine a threshold for when the terminal should be handed off to another cell, domain (circuit-switched vs. packet-switched), or radio access technology. + +When a session is initiated or modified the P-CSCF supporting the CHEM feature shall derive the Max-PLR-DL AVP and Max-PLR-UL AVP based on the PLR\_adapt and maxe2e-PLR attribute values in both the SDP offer and/or SDP answer to determine the maximum tolerable end-to-end PLR budget distributed across the uplink and downlink in a media transport path as described in 3GPP TS 29.213 [9] clause 6.2. + +Upon reception of SDP offer and answer, P-CSCF should check whether a= PLR\_adapt line is present in both SDP offer and answer to derive Max-PLR-DL and Max-PLR-UL AVP in Media-Component-Description AVP else downlink and uplink maximum packet loss are not included by AF. + +The originating P-CSCF should derive Max-PLR-DL AVP to the maximum value of Max-PLR-DL among all the RTP payload types. For each RTP payload type Max-PLR-DL is computed as described in 3GPP TS 29.213 [9] clause 6.2. + +- If maxe2e-PLR is included in the SDP offer then Max-PLR-DL for a payload type is derived as value of maxe2e-PLR in the SDP offer - maxUL-PLR in the SDP answer if present else the default value is $\frac{1}{2}$ maxe2e-PLR value present in the SDP offer. +- If maxe2e-PLR is not included in the SDP offer then then Max-PLR-DL for a payload type is derived from the default value in end-to-end Maximum End-to-End Packet Loss Rate for the decoder of the RTP payload type as recommended in 3GPP TS 26.114 [41] clause X.1.2 for application layer redundancy or X.1.1 for partial redundancy - maxUL-PLR in the SDP answer if present else the default value is $\frac{1}{2}$ default value in end-to-end Maximum End-to-End Packet Loss Rate for the decoder of the RTP payload type as recommended in 3GPP TS 26.114 [41]. + +The originating P-CSCF should derive Max-PLR-UL AVP to the maximum value of Max-PLR-UL among all the RTP payload types. For each RTP payload type Max-PLR-UL is computed as described in 3GPP TS 29.213 [9] clause 6.2. + +- If maxe2e-PLR is included in the SDP answer then Max-PLR-UL for a payload type is derived as value of maxe2e-PLR in the SDP answer - maxDL-PLR in the SDP ANSWER if present else the default value is $\frac{1}{2}$ maxe2e-PLR value present in the SDP answer. +- If maxe2e-PLR is not included in the SDP answer then then Max-PLR-UL for a payload type is derived as the $\frac{1}{2}$ default value in end-to-end Maximum End-to-End Packet Loss Rate for the decoder of the RTP payload type as recommended in 3GPP TS 26.114 [41] clause X.1.2 for application layer redundancy or X.1.1 for partial redundancy. + +The terminating P-CSCF should derive Max-PLR-DL AVP to the maximum value of Max-PLR-DL among all the RTP payload types. For each RTP payload type Max-PLR-DL is computed as described in 3GPP TS 29.213 [9] clause 6.2. + +- If maxe2e-PLR is included in the SDP answer then Max-PLR-DL for a payload type is derived as value of value of maxDL-PLR in the SDP answer if present else the default value is $\frac{1}{2}$ maxe2e-PLR value present in the SDP answer. +- If maxe2e-PLR is not included in the SDP answer then then Max-PLR-DL for a payload type is derived as the $\frac{1}{2}$ default value in end-to-end Maximum End-to-End Packet Loss Rate for the decoder of the RTP payload type as + +recommended in 3GPP TS 26.114 [41] clause X.1.2 for application layer redundancy or X.1.1 for partial redundancy. + +The terminating P-CSCF should derive Max-PLR-UL AVP to the maximum value of Max-PLR-UL among all the RTP payload types. For each RTP payload type Max-PLR-UL is computed as described in 3GPP TS 29.213 [9] clause 6.2. + +- If maxe2e-PLR is included in the SDP offer then Max-PLR-UL for a payload type is derived as value of value of maxUL-PLR in the SDP answer if present else the default value is $\frac{1}{2}$ maxe2e-PLR value present in the SDP offer. +- If maxe2e-PLR is not included in the SDP offer then then Max-PLR-UL for a payload type is derived as the $\frac{1}{2}$ default value in end-to-end Maximum End-to-End Packet Loss Rate for the decoder of the RTP payload type as recommended in 3GPP TS 26.114 [41] clause X.1.2 for application layer redundancy or X.1.1 for partial redundancy. + +## --- A.19 Handling of a FLUS session + +If the P-CSCF receives a SIP request that requires provisioning of service information to the PCRF, the "FLUS" feature is supported and an SDP attribute "a=label:flus..." is included in one or more of the received SDP media descriptions, the P-CSCF shall provide the string after "a=label:" starting with "flus" within the FLUS-Identifier AVP within the affected Media-Component-Description AVP(s) in the AA-Request to the PCRF. + +NOTE: During the first interaction with the PCRF, the P-CSCF does not know if the "FLUS" feature is supported by the PCRF. In this case the P-CSCF will include the information as if supported. + +If additionally the P-CSCF receives the "a=3gpp-qos-hint" media-level SDP attribute in the SIP request, the P-CSCF shall provide the PCRF with the Desired-Max-Latency AVP and/or Desired-Max-Loss AVP as described in 3GPP TS 29.213 [9], clause 6.2. + +Upon receiving the information from the P-CSCF and if the "FLUS" feature is supported, the PCRF shall derive the QoS information as described in 3GPP TS 29.213 [9], clause 6.3. + +## --- A.20 QoS hint support for data channel media + +If the P-CSCF receives a SIP request that requires provisioning of a service information to the PCRF, the QoSHint feature is supported and an SDP attribute "a=3gpp-qos-hint" is included in one or more of the received data channel media descriptions, the P-CSCF may provide the Desired-Max-Latency AVP and/or Desired-Max-Loss AVP for each affected application media component within the Media-Component-Description AVP(s) in the AA-Request to the PCRF. + +NOTE: During the first interaction with the PCRF, the P-CSCF does not know if the QoSHint feature is supported by the PCRF. In this case the P-CSCF will include the information as if supported. + +Upon receiving the information from the P-CSCF and if the QoSHint feature is supported, the PCRF shall derive the QoS information as described in 3GPP TS 29.213 [9], clause 6.3. + +# Annex B (normative): Flow identifiers: Format definition and examples + +## B.1 Format of a flow identifier + +### B.1.1 General + +A flow identifier is expressed as a 2-tuple as follows: + + + +where both are numbered starting from 1. The encoding of the flow identifier is as indicated in 3GPP TS 24.008 [12]. + +If UE and AF share an algorithm for a given application, which guarantees that UE and AF assign the same ordinal number to each media component, the ordinal numbers of the IP Flows within a media component shall be assigned according to the following rules: + +- All IP flow(s) or bidirectional combinations of two IP flow(s) within the media component, for which a downlink destination port number is available, shall be assigned ordinal numbers in the order of downlink destination port numbers. +- All IP flows, where no downlink destination port number is available, shall be assigned the next higher ordinal numbers in the order of uplink destination port numbers. + +The ordinal number of a media component shall not be changed when the session description information is modified. + +If no SDI with fixed and unique positions for media components is exchanged between UE and AF, the UE and AF may assign the ordinal numbers of the media components in another application-dependent algorithm which guarantees that UE and AF assign the same ordinal number to each media component. + +If UE and AF do not share an algorithm for a given application, which guarantees that UE and AF assign the same ordinal number to each media component, the ordinal number of the media component shall be set to zero and the ordinal number of the IP flows shall be assigned according to the following rules: + +1. If ordinal numbers for several IP flows are assigned at the same time, all uplink IP flows shall be assigned lower ordinal number than all downlink IP flows. +2. If ordinal numbers for several IP flows are assigned at the same time, all uplink and all downlink IP flows shall separately be assigned ordinal numbers according to increasing internet protocol number assigned by IANA (e.g. 6 for TCP and 17 for UDP) +3. If ordinal numbers for several IP flows are assigned at the same time, for each internet protocol with a port concept, all uplink and all downlink IP flows of this internet protocol shall separately be assigned ordinal numbers according to increasing port numbers. +4. If IP flows are removed from an existing session, the previously assigned binding info shall remain unmodified for the remaining IP flows. +5. If IP flows are added to an existing session, the previously assigned binding info shall remain unmodified and the new IP flows shall be assigned ordinal numbers following the rules 1. To 3., starting with the first previously unused ordinal number. The numbers freed in step 4. Shall not be reused. + +If the IP flows correspond to AF signalling (e.g. SIP signalling IP Flows), and no IP flow information is provided both the ordinal number of the media component and the IP flows shall be set to zero. In the case when the IP flow information of the AF signalling is provided, the ordinal number of the media component will be set to zero, and the ordinal number(s) of the IP flows shall follow the rules set above for the case when the UE and AF do not share an algorithm for a given application. + +### B.1.2 Derivation of Flow Identifiers from SDP + +#### B.1.2.1 Standard Procedure + +The procedure in Table B.1.2.1.1 shall be applied for SDP of "session" disposition type within SIP and for all SDP outside SIP. + +**Table B.1.2.1.1: Standard Procedure to derive Flow Identifiers from SDP** + +| The ordinal number of the position of the media component | The ordinal number of the IP flow(s) within the media component description | +|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| The ordinal number of the position of the "m=" line in the SDP |

The ordinal number of the IP flow(s) within the "m=" line assigned in the order of increasing downlink destination port numbers, if downlink destination port numbers are available. For uplink or inactive unicast media IP flows, a downlink destination port number is nevertheless available, if SDP offer-answer according to RFC 3264 is used.

The ordinal number of the IP flow(s) within the "m=" line assigned in the order of increasing uplink destination port numbers, if no downlink destination port numbers are available.

| + +#### B.1.2.2 SDP with "early session" disposition type + +The procedure in Table B.1.2.2.1 shall be applied for SDP of "early session" disposition type within SIP. The "early session" disposition type is specified within IETF RFC 3959 [27]. + +**Table B.1.2.2.1: Procedure to derive Flow Identifiers from "early session" disposition SDP** + +| The ordinal number of the position of the media component | The ordinal number of the IP flow(s) within the media component description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +|

If a single media component with one media type (e.g. "audio" or "video") is contained in "early session" disposition SDP and a single media component with the same media type is contained in the "session" disposition SDP of the same SIP dialogue, and if both SDP media components are described in a single Rx service information media component, that Rx service information media component shall obtain the media component number derived from "session" disposition SDP following the rules in table B.1.2.1.1.

Otherwise each media component shall obtain the ordinal number of the position of the "m=" line in the "early session" disposition SDP plus 1000 as media component ordinal number.

| As in table B.1.2.1.1. | + +## B.2 Example 1 + +An UE, as the offerer, sends a SDP session description, as shown in table B.2.1, to an application server (only relevant SDP parameters are shown): + +**Table B.2.1: The values of the SDP parameters sent by the UE in example 1.** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| V=0
o=ecsreid 3262464865 3262464868 IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A
s=MM01
i=One unidirectional audio media and one unidirectional video media and one bidirectional application | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +``` + +media +t=3262377600 3262809600 +m=video 50230 RTP/AVP 31 +c=IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A +a=recvonly +m=audio 50330 RTP/AVP 0 +c=IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A +a=sendonly +m=application 50430 udp wb +c=IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A +a=sendrecv + +``` + +and receives the SDP parameters, as shown in table B.2.2, from the application server: + +**Table B.2.2: The values of the SDP parameters sent by the application server in example 1.** + +``` + +V=0 +o=ecsreid 3262464865 3262464868 IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A +s=MM01 +i=One unidirectional audio media and one unidirectional video media and one bidirectional application +media +t=3262377600 3262809600 +m=video 51372 RTP/AVP 31 +c=IN IP6 2001:0646:000A:03A7:02D0:59FF:FE40:2014 +a=sendonly +m=audio 49170 RTP/AVP 0 +c=IN IP6 2001:0646:000A:03A7:02D0:59FF:FE40:2014 +a=recvonly +m=application 32416 udp wb +c=IN IP6 2001:0646:000A:03A7:0250:DAFF:FE0E:C6F2 +a=sendrecv + +``` + +From this offer-answer exchange of SDP parameters the UE and the PCRF each creates a list of flow identifiers comprising the IP flows as shown in table B.2.3: + +**Table B.2.3: Flow identifiers in example 1.** + +| Order of 'm='-line | Type of IP flows | Destination IP address / Port number of the IP flows | Flow identifier | +|--------------------|----------------------|------------------------------------------------------|-----------------| +| 1 | RTP (Video) DL | 2001:0646:00F1:0045:02D0:59FF:FE14:F33A / 50230 | <1,1> | +| 1 | RTCP DL | 2001:0646:00F1:0045:02D0:59FF:FE14:F33A / 50231 | <1,2> | +| 1 | RTCP UL | 2001:0646:000A:03A7:02D0:59FF:FE40:2014 / 51373 | <1,2> | +| 2 | RTP (Audio) UL | 2001:0646:000A:03A7:02D0:59FF:FE40:2014 / 49170 | <2,1> | +| 2 | RTCP DL | 2001:0646:00F1:0045:02D0:59FF:FE14:F33A / 50331 | <2,2> | +| 2 | RTCP UL | 2001:0646:000A:03A7:02D0:59FF:FE40:2014 / 49171 | <2,2> | +| 3 | UDP (application) DL | 2001:0646:00F1:0045:02D0:59FF:FE14:F33A / 50430 | <3,1> | +| 3 | UDP (application) UL | 2001:0646:000A:03A7:0250:DAFF:FE0E:C6F2 / 32416 | <3,1> | + +## B.3 Example 2 + +In the general case, multiple ports may be specified with a "number of ports" qualifier as follows, RFC 2327 [17]: + +``` + +m= / + +``` + +An UE, as the offerer, sends a SDP session description, as shown in table B.3.1, to an application server (only relevant SDP parameters are shown): + +**Table B.3.1: The values of the SDP parameters sent by the UE in example 2.** + +``` + +v=0 +o=ecsreid 3262464321 3262464325 IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A +s=MM02 +i=One unidirectional audio media consisting of two media IP flows described by one media +component +t=3262377600 3262809600 +m=audio 50330/2 RTP/AVP 0 +c=IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A +a=recvonly + +``` + +and receives the SDP parameters, as shown in table B.3.2, from the application server: + +**Table B.3.2: The values of the SDP parameters sent by the application server in example 2.** + +``` + +v=0 +o=ecsreid 3262464321 3262464325 IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A +s=MM02 +i=One unidirectional audio media consisting of two media IP flows described by one media +component +t=3262377600 3262809600 +m=audio 49170/2 RTP/AVP 0 +c=IN IP6 2001:0646:000A:03A7:02D0:59FF:FE40:2014 +a=sendonly + +``` + +From this offer-answer exchange of SDP parameters the UE and the PCRF each creates a list of flow identifiers comprising the IP flows as shown in table B.3.3: + +**Table B.3.3: Flow identifiers in example 2.** + +| Order of 'm='-line | Type of IP flows | Destination IP address / Port number of the IP flows | Flow identifier | +|--------------------|------------------|------------------------------------------------------|-----------------| +| 1 | RTP (audio) DL | 2001:0646:00F1:0045:02D0:59FF:FE14:F33A / 50330 | <1,1> | +| 1 | RTCP DL | 2001:0646:00F1:0045:02D0:59FF:FE14:F33A / 50331 | <1,2> | +| 1 | RTCP UL | 2001:0646:000A:03A7:02D0:59FF:FE40:2014 / 49171 | <1,2> | +| 1 | RTP (audio) DL | 2001:0646:00F1:0045:02D0:59FF:FE14:F33A / 50332 | <1,3> | +| 1 | RTCP DL | 2001:0646:00F1:0045:02D0:59FF:FE14:F33A / 50333 | <1,4> | +| 1 | RTCP UL | 2001:0646:000A:03A7:02D0:59FF:FE40:2014 / 49173 | <1,4> | + +## B.4 Example 3 without media components. + +The UE and AF do not exchange SDP for an application and do not share an algorithm, which guarantees that UE and AF assign the same ordinal number to each media component. + +At the AF session initiation, the UE and AF agree to set up the following IP flows: + +- Uplink UDP flow with destination port 100. +- Downlink UDP flow with destination port 100. +- Downlink TCP flow with destination port 100. +- Uplink TCP flow with destination port 100. +- Uplink UDP flow with destination port 200. + +The following binding info is assigned to these IP flows. + +- Uplink UDP flow with destination port 100: (0, 2) +- Downlink UDP flow with destination port 100: (0, 5) +- Downlink TCP flow with destination port 100: (0, 4) +- Uplink TCP flow with destination port 100: (0, 1) +- Uplink UDP flow with destination port 200: (0, 3) + +At a later stage in the session, the TCP IP flows are removed and the following IP flows are added: + +- Uplink UDP flow with destination port 150. +- Downlink UDP flow with destination port 50. + +The following binding info is assigned to the IP flows existing at this stage: + +- Uplink UDP flow with destination port 100: (0, 2) +- Downlink UDP flow with destination port 100: (0, 5) +- Uplink UDP flow with destination port 200: (0, 3) +- Uplink UDP flow with destination port 150: (0, 6) +- Downlink UDP flow with destination port 50: (0, 7) + +## B.5 Example 4 + +In this example, the SDP "a=rtcp" attribute defined in IETF RFC 3605 is used. + +An UE, as the offerer, sends a SDP session description, as shown in table B.5.1, to an application server (only relevant SDP parameters are shown): + +**Table B.5.1: The values of the SDP parameters sent by the UE in example 1.** + +``` +V=0 +o=ecsreid 3262464865 3262464868 IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A +s=MM01 +i=One unidirectional video media +t=3262377600 3262809600 +m=video 50230 RTP/AVP 31 +c=IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A +a=recvonly +a=rtcp: 49320 +``` + +and receives the SDP parameters, as shown in table B.5.2, from the application server: + +**Table B.5.2: The values of the SDP parameters sent by the application server in example 1.** + +``` +V=0 +o=ecsreid 3262464865 3262464868 IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A +s=MM01 +i=One unidirectional video media +t=3262377600 3262809600 +m=video 51372 RTP/AVP 31 +c=IN IP6 2001:0646:000A:03A7:02D0:59FF:FE40:2014 +``` + +| | +|----------------------------| +| a=sendonly
a=rtcp:53020 | +|----------------------------| + +From this offer-answer exchange of SDP parameters the UE and the PCRF each creates a list of flow identifiers comprising the IP flows as shown in table B.5.3: + +**Table B.5.3: Flow identifiers in example 4.** + +| Order of 'm='-line | Type of IP flows | Destination IP address / Port number of the IP flows | Flow identifier | +|--------------------|------------------|------------------------------------------------------|-----------------| +| 1 | RTP (Video) DL | 2001:0646:00F1:0045:02D0:59FF:FE14:F33A / 50230 | <1,2> | +| 1 | RTCP DL | 2001:0646:00F1:0045:02D0:59FF:FE14:F33A / 49320 | <1,1> | +| 1 | RTCP UL | 2001:0646:000A:03A7:02D0:59FF:FE40:2014 / 53020 | <1,1> | + +--- + +Annex C (informative): +Void + +# --- Annex D (normative): Monitoring Related SCEF Procedures over Rx + +## D.1 Monitoring events support, using SCEF procedures over Rx + +If SCS/AS has requested monitoring of events and operator policies in the SCEF indicate that monitoring shall be performed via PCRF, the SCEF shall initiate the applicable Rx procedures acting as an AF as described in 3GPP TS 23.682 [40]. + +The following monitoring events are supported; + +- Location reporting according to the Access Network Information Report procedures described in clause 4.4.6.7. This functionality requires the support of NetLoc, NetLoc-Untrusted-WLAN and/or NetLoc-Trusted-WLAN supported features. +- Communication Failure reporting as described in clauses 4.4.4, 4.4.6.2 and 4.4.6.3. This functionality requires the support of RAN-NAS-Cause supported feature. + +# --- Annex E (normative): Interworking with 5GS via Rx interface + +## E.1 General + +In the 5GS the Rx reference point is defined between the the PCF and the AF. The relationship between the involved functional entities is depicted in figure E.1.1. The overall PCC architecture is depicted in clause 4 of 3GPP TS 29.513 [59]. + +![Diagram of the Rx reference model in 5GS. It shows two rectangular boxes, 'AF' on the left and 'PCF' on the right, connected by a horizontal line labeled 'Rx' above it.](cdd0f1dd36631f2c4b17d7ca0f174d80_img.jpg) + +``` +graph LR; AF[AF] ---|Rx| PCF[PCF] +``` + +Diagram of the Rx reference model in 5GS. It shows two rectangular boxes, 'AF' on the left and 'PCF' on the right, connected by a horizontal line labeled 'Rx' above it. + +**Figure E.1.1: Rx reference model in 5GS** + +5GS supports an interworking with AFs via the Rx interface. Interworking with AFs related to existing IMS services is described in 3GPP TS 23.228 [16]. Interworking with AFs related to existing Mission Critical services is described in TS 23.280 [60]. The PCF in 5GS supports the corresponding Rx procedures and requirements defined in 3GPP TS 23.203 [2]. The stage 2 requirements for 5GS supporting Rx interface are described in 3GPP TS 23.503 [56]. + +The PCF exchanges PCC rules with the SMF over the N7 interface as specified in 3GPP TS 29.512 [57]. + +Signalling flows related to the both Rx and N7 interfaces are specified in 3GPP TS 29.513 [59]. + +The generic mechanisms for interaction between the AF and the PCF are described in main clauses in this specification and with the following clarifications: + +- description of the PCRF and the PCEF applies to the PCF and the SMF respectively; +- description of the SPR applies to the UDR; +- BBERF is not applicable in 5GS; +- an IP-CAN bearer in this specification shall be interpreted as a 5GS QoS flow; + +- an IP-CAN session in this specification shall be interpreted as a 5GS PDU session of type IP; +- APN is equivalent to DNN; +- the following values of the Specific-Action AVP defined in clause 5.3.13 are applicable only to a PCF: EPS\_FALLBACK (17) and INDICATION\_OF\_REALLOCATION\_OF\_CREDIT (18); +- when the serving network is an SNPN and the serving network information is provided to the AF, the NID may optionally be part of the serving network identifier, as specified in clause E.5; and +- the 5G-RAN-NAS-Release-Cause AVP defined in clause 5.3.69 is applicable only to a PCF. When the RAN-NAS-Cause feature is supported, it encodes the 5GS RAN cause and/or NAS cause, when available. + +The specific mechanisms for the interaction between the AF and the PCF are described in the subclauses below. + +## E.2 Mapping table for IP-CAN types and Access types + +Table E.2-1 maps the values of the Access types and RAT types used for N7 interface in 3GPP TS 29.512 [58] with the values of the IP-CAN types and RAT types used in this specification. + +**Table E.2-1: Mapping table for IP-CAN types and Access types values** + +| AccessType specified for N7, see 3GPP TS 29.571 [64] clause 5.4.3.1 | RatType specified for N7, see 3GPP TS 29.571 [64] clause 5.4.3.2 (NOTE 1) | RAT-Type, see 3GPP TS 29.212 [8] clause 5.3.31 | | IP-CAN-Type, see 3GPP TS 29.212 [8] clause 5.3.27 | | +|---------------------------------------------------------------------|---------------------------------------------------------------------------|------------------------------------------------|-----------------|---------------------------------------------------|--------------| +| | | Value | Description | Value | Description | +| 3GPP_ACCESS | NR | 1006 | NR | 8 | 3GPP-5GS | +| | EUTRA | 1004 | EUTRAN | | | +| | NBIOT | 1005 | EUTRAN-NB-IoT | | | +| | LTE M | 1007 | LTE-M | | | +| | NR U | 1008 | NR-U | | | +| | NR LEO | 1035 | NR(LEO) | | | +| | NR MEO | 1036 | NR(MEO) | | | +| | NR GEO | 1037 | NR(GEO) | | | +| | NR_OTHER_SAT | 1038 | NR(OTHERSAT) | | | +| | NR REDCAP | 1039 | NR-REDCAP | | | +| NON_3GPP_ACCESS | WLAN | 0 | WLAN (NOTE 2) | 9 | Non-3GPP-5GS | +| | VIRTUAL | 1 | VIRTUAL | | | +| | TRUSTED_N3GA | 2 | TRUSTED-N3GA | | | +| | TRUSTED_WLAN | 0 | WLAN (NOTE 2) | | | +| | WIREDLINE | 3 | WIREDLINE | | | +| | WIREDLINE_CABLE | 4 | WIREDLINE-CABLE | | | +| | WIREDLINE_BBF | 5 | WIREDLINE-BBF | | | + +NOTE 1: Other values of RAT Types specified in 3GPP TS 29.571 [64] and not shown in this table are not applicable to this specification. + +NOTE 2: When the received RAT Type in N7 indicates "WLAN", the AN-Trusted AVP set to "Untrusted" indicates the access type is not trusted. When the received RAT Type in N7 indicates "TRUSTED\_WLAN", the AN-Trusted AVP set to "Trusted" indicates the access type is trusted. + +## E.3 Reporting EPS Fallback + +When the feature "EPSFallbackReport" is supported, if the AF requests the PCF to report EPS Fallback, the AF shall subscribe to the "EPS\_FALLBACK" within the Specific-Action AVP as described in clause 5.3.13. The AF shall request the PCF to report the EPS Fallback in conjunction with providing the PCF with the AF session information as described in clause 4.4.1 for the initial provisioning of session information, and the subscription to "EPS\_FALLBACK" shall apply for voice media type requests along the AF session lifetime. + +When the PCF then receives the EPS Fallback indication from the SMF, the PCF shall provide the corresponding EPS Fallback indication to the AF by sending an RAR (re-authorization request) command. The RAR command shall include the EPS\_FALLBACK cause encoded in the Specific-Action AVP. + +When the AF receives the RAR command, it shall acknowledge the command by sending an RAA (re-authorization answer) command to the PCF. + +## --- E.4 IP-CAN type change Notification for a MA PDU session + +If the AF has successfully subscribed to change notifications in UE's IP-CAN type and RAT type, the ATSSS feature is supported and the PDU session is a MA PDU session: + +- if the PCF previously requested to the SMF to be updated with access type changes, the PCF shall include in the AAA command: + - i. the IP-CAN-Type AVP, RAT-Type AVP (if applicable) for the UE's IP-CAN/RAT type values; and + - ii. if both, 3GPP and non-3GPP access information is available, the additional IP-CAN type information and RAT type information (if available) in the MA-Information AVP; +- otherwise, the PCF shall subscribe to access type changes as described in clause 4.2.6.4 of 3GPP TS 29.512 [57] and shall send an RAR command when the corresponding IP-CAN event occurs, i.e.: + - a) when a UE's IP-CAN type or RAT type (if applicable) changes; or + - b) a new IP-CAN type and RAT type (if applicable) become available for the UE and the MA PDU session; or + - c) an IP-CAN type and RAT type (if applicable) become unavailable (are released) for the UE and the MA PDU session. + +The RAR from the PCF shall include the Specific-Action AVP for the subscribed event and: + +- a. if it is the first IP-CAN change report: + - i. the IP-CAN-Type AVP, RAT-Type AVP (if applicable) for the UE's IP-CAN/RAT type values; and + - ii. if both, 3GPP and non-3GPP access information is available, the additional IP-CAN type information and RAT type information (if available) in the MA-Information AVP; +- b. if it is a subsequent IP-CAN change report: + - i. if a new IP-CAN type is added to the MA PDU session, the MA-Information AVP with the added IP-CAN type information encoded in the IP-CAN-Type AVP and the RAT type information encoded within the RAT-Type AVP if applicable; + - ii. if an IP-CAN type is released in the MA PDU session, the MA-Information AVP with the released IP-CAN type information encoded in the IP-CAN-Type AVP, the RAT type information encoded within the RAT-Type AVP, if applicable, and the MA-Information-Action AVP set to 1 (RELEASE). + +NOTE: For a MA PDU session, if the ATSSS feature is not supported by the AF the PCF includes the IP-CAN-Type AVP and the RAT-Type AVP with a currently active combination of IP-CAN type and RAT type (if applicable for the notified access type). When both 3GPP and non-3GPP accesses are available, the PCF includes the information corresponding to the 3GPP access. + +## --- E.5 Reporting serving network identity + +When a new AF session is being established as described in clause 4.4.1 or is being modified as described in clause 4.4.2, the AAA command shall also contain the PLMN identifier within the 3GPP-SGSN-MCC-MNC AVP and, if available, the NID within the NID AVP if the PCF has previously requested the SMF to be updated with the serving network identity. + +NOTE: The combination of a PLMN identifier and a NID identifies an SNPN, as specified in 3GPP TS 23.501 [55] clause 5.30.2. + +When the AF initiates a session termination, the PCF shall include in the STA command the PLMN identifier within the 3GPP-SGSN-MCC-MNC AVP and, if available, the NID within the NID AVP: + +- if the PCF received an ST-Request from the AF, indicating an AF session termination and if location info is not available, as specified in clause 4.4.4; and +- if the AF requested the PCF to report the access network information, the Rx session is being terminated and if location info is not available, as specified in clause 4.4.6.7. + +When the PCF needs to inform the AF about a traffic plane event, the PCF shall include in the RAR command the PLMN identifier within the 3GPP-SGSN-MCC-MNC AVP and, if available, the NID within the NID AVP: + +- when the PCF gets the knowledge that one or more SDFs have been deactivated, if the RAN-NAS-Cause feature is supported and if location info is not available, as specified in clause 4.4.6.2; +- when the PCF is notified of the loss or release of resources associated to the PCC rules corresponding with AF signalling IP flows, if the RAN-NAS-Cause feature is supported and if location info is not available, as specified in clause 4.4.6.3; +- if the AF requested the PCF to report the access network information, the Rx session is not being terminated and if location info is not available, as specified in clause 4.4.6.7; and +- when the PCF gets the knowledge that the service network where the UE is located has been updated or becomes available and the AF subscribed to PLMN\_CHANGE has described in clause 4.4.6.9. + +## --- E.6 Trusted non-3GPP Access Network Information + +The PCF provides the AF with the access network information as described in clause 4.4.1, with the following differences: + +- The RAT-Type AVP shall be set to "WLAN" and AN-Trusted AVP shall be set to "Trusted" when over the N7 reference point: + - a) the received "ratType" attribute is "TRUSTED\_WLAN"; or + - b) the received "ratType" attribute is "TRUSTED\_N3GA" and the "Netloc-Trusted-N3GA" feature is not supported. +- The RAT-Type AVP shall be set to "TRUSTED-N3GA" when the "Netloc-Trusted-N3GA" feature is supported and the received "ratType" attribute over the N7 reference point is "TRUSTED\_N3GA". + +If the NetLoc-Trusted-WLAN is supported, the procedure described in clauses 4.4.4 and 4.4.6.7 shall apply with the exceptions specified in clause E.1 and with the exception of the user location information that is encoded as follows: + +- a) The TNAP/TWAP Identifier received over the N7 reference point in the "tnapId"/"twapId" attributes of the "n3gaLocation" attribute, if available, is encoded in the TWAN-Identifier AVP. + +NOTE 1: The received SSID, BSSID and Civic Address values, if available, are encoded within the TWAN-Identifier AVP as specified in 3GPP TS 29.061 [34]. + +- b) The UE/N5CW device local IP address (used to reach the TNGF/TWIF) received over the N7 reference point in the "ueIpv4Addr" or "ueIpv6Addr" attribute of the "n3gaLocation" attribute, if available, is encoded in the UE-Local-IP-Address AVP. +- c) The UDP source port number received over the N7 reference point in the "portNumber" attribute if available, is encoded within the UDP-Source-Port AVP + +NOTE 2: The UDP protocol can be used between the UE and TNGF to enable NAT traversal. When reporting IP-CAN\_CHANGE specific action, the PCF shall, in addition to the IP-CAN-Type AVP and RAT-Type AVP, provide the AN-Trusted AVP set to "Trusted" when the provided RAT-Type AVP value is "WLAN". + +## E.7 Untrusted non-3GPP Access Network Information + +The PCF provides the AF with the access network information as described in clause 4.4.1, with the following differences: + +- The RAT-Type AVP shall be set to "WLAN" and AN-Trusted AVP shall be set to "Untrusted" when over the N7 reference point the received "ratType" attribute is "WLAN". +- The ePDG address used as IPSec tunnel endpoint with the UE, received over the N7 reference point within the "anGwAddr" attribute included in the "servNfId" attribute, is encoded in the AN-GW-Address AVP. +- The serving network identifier received over the N7 reference point within the "servingNetwork" attribute is encoded in the 3GPP-SGSN-MCC-MNC AVP. + +If the NetLoc-Untrusted-WLAN feature is supported, reporting access network information procedure described in clauses 4.4.4 and 4.4.6.7 shall apply with the exceptions specified in clause E.1 and with the exception of: + +- The user location information is encoded as follows: + - a) The UE local IP address (used to reach the N3IWF or ePDG) received over the N7 reference point in the "ueIpv4Addr" or "ueIpv6Addr" attribute of the "n3gaLocation" attribute, if available, is encoded in the UE-Local-IP-Address AVP. + - b) The UDP source port or the TCP source port received over the N7 reference point in the "portNumber" attribute if available, is encoded within the UDP-Source-Port AVP or the TCP-Source-Port AVP as indicated by the "protocol" attribute, if available. + +NOTE 1: When the UE reaches the ePDG via a NAT, the combination of UE local IP address and the UE source port is needed for lawful interception purposes. The UE source port may be either a UDP or a TCP port, and it is indicated in the "protocol" attribute received over the N7 reference point. + +- c) The WLAN location information received in the "twapId" attribute of the "n3gaLocation" attribute, if available, is encoded in the TWAN-Identifier AVP. +- The UE time zone information is included within 3GPP-MS-TimeZone AVP, if available. + +NOTE 2: EPC does not support time zone reporting when the access network is untrusted WLAN. + +When reporting IP-CAN\_CHANGE specific action, the PCF shall, in addition to the IP-CAN-Type AVP and RAT-Type AVP, provide the AN-Trusted AVP set to "Untrusted". The PCF provides also the AF with the ePDG IP address used as IPSec tunnel endpoint with the UE, if received, encoded in the AN-GW-Address AVP. + +## E.8 Wireline non-3GPP Access Network Information + +The PCF provides the AF with the wireline access network information as described in clause 4.4.1, with the following differences: + +- The RAT-Type AVP shall be set to "WIRELINE", "WIRELINE\_CABLE" or "WIRELINE\_BBF" according to the received "ratType" attribute. + +If the NetLoc-Wireline is supported, the procedure described in clauses 4.4.4 and 4.4.6.7 shall apply with the exceptions specified in clause E.1 and the exception of the user location information that is encoded as follows: + +- The wireline location is encoded in the Wireline-User-Location-Info AVP, where: + - a) The HFC Node Identifier received over NGAP in the "hfcNodeId" attribute of the "n3gaLocation", if available, is encoded in the HFC-Node-Identifier AVP. + - b) The Global Line Identifier in the "gli" attribute of the "n3gaLocation", if available, is encoded in the GLI-Identifier AVP. + - c) The type of wireline access in the "w5gbnLineType" attribute of the "n3gaLocation", if available, is encoded in the Line-Type AVP. + +## E.9 5GS-Level Identities report + +The PCF provides 5GS-Level Identities as defined in annex A.1 and A.5 with the following differences: + +- the IMSI is included within the Subscription-Id AVP if the IMSI is received within the "supi" attribute; +- the MSISDN is included within the Subscription-Id AVP if the MSISDN is received within the "gpsi" attribute; +- the NAI is included within the Subscription-Id AVP if the NAI is received within the "supi" attribute; +- the IMEISV is included with the User-Equipment-Info AVP if the IMEISV is received within the "pei" attribute; +- the IMEI is included with the the User-Equipment-Info-Extension AVP if the User-Equipment-Info-Extension feature is supported and the IMEI is received within the "pei" attribute. + +NOTE 1: UE identities for wireless and wireline convergence access are not considered to be used for the IMS. + +NOTE 2: When the UE accesses a PLMN, the PCF provides the IMSI and the MSISDN within the Subscription-Id AVP(s), if available. When the UE accesses a SNPN, the PCF provides the IMSI or the NAI, and the MSISDN within the Subscription-Id AVP(s), if available. For both, SNPN and PLMN accesses, the PCF provides the IMEI(SV) in the concerned AVP(s) as specified above. + +## E.10 Reporting Access Network Information + +When the PCF receives the access network information, the PCF shall provide the corresponding access network information to the AF as defined in clause 4.4.6.7, + +When the AF requested UE location, the PCF shall forward both, the received 3GPP access (NR or E-UTRA) and non-3GPP access (Trusted, Untrusted, or Wireline network) UE location, if available. + +The PCF encodes 3GPP UE location received in the "eutraLocation" or "nrLocation" attribute into the 3GPP-User-Location-Info AVP as described in 3GPP TS 29.061 [34]. + +The PCF encodes the non-3GPP Trusted, Untrusted or Wireline access UE location as described in clauses E.6, E.7 and E.8. When the PCF received the "userLocationInfoTime" attribute, the PCF includes the User-Location-Info-Time AVP in the access network report to the AF to indicate when the UE location was last known. + +NOTE: When the PCF receives both, the 3GPP and non-3GPP access UE locations, the "userLocationInfoTime" attribute, if received, indicates the last known 3GPP access UE location, and consequently, the User-Location-Info-Time AVP also indicates the last known 3GPP access UE location. + +## E.11 Access Network Charging Information Notification + +When the PCF receives the access network charging information, the PCF shall provide the corresponding access network information to the AF as defined in clause 4.4.6.5. + +If the PCF received from the SMF both, the IPv4 and IPv6 addresses within the "anChargIpv4Addr" and "anChargIpv6Addr" attributes respectively, the PCF may select, based on local configuration, one of the received addresses and report it within the Access-Network-Charging-Address AVP. + +## E.12 3GPP Access Network Information + +The PCF provides the AF with the access network information as described in clause 4.4.1 by including the mapped RAT Type within the RAT-Type AVP according to Table E.2-1. + +If the NetLoc is supported, the procedure described in clauses 4.4.4 and 4.4.6.7 shall apply with the exceptions specified in clause E.1 and with the exception of the user location information that is encoded as follows: + +- a) The TAI and NCGI received over the N7 reference point in the "tai" attribute and "ncgi" attribute of the "nrLocation" attribute respectively, if available, are encoded in the 3GPP-User-Location AVP; or +- b) The TAI and ECGI received over the N7 reference point in the "tai" attribute and "ecgi" attribute of the "eutraLocation" attribute respectively, if available, are encoded in the 3GPP-User-Location AVP. + +## Annex F (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +|---------|-------|-----------|------|-----|---------------------------------------------------------------------------------------|--------|--------| +| 12-2014 | CT-66 | CP-140922 | 0361 | 1 | UPCON related update about definition, abbreviation and architecture part | 12.5.0 | 13.0.0 | +| 12-2014 | CT-66 | CP-140935 | 0364 | 3 | Double resource reuse support over Rx | 12.5.0 | 13.0.0 | +| 12-2014 | CT-66 | CP-140934 | 0365 | 2 | Mitigating RAN user plane congestion over Rx | 12.5.0 | 13.0.0 | +| 03-2015 | CT-67 | CP-150131 | 0370 | | Reporting RAN/NAS cause during bearer creation/modification failure scenarios | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150134 | 0371 | | Removal of Editor's Note | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150131 | 0372 | | Access network information reporting during the IP-CAN session termination | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150136 | 0373 | | Introduction of a reference to the Rest-Rx interface | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150131 | 0374 | | Inclusion of RAN/NAS cause values into SIP signalling by P-CSCF | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150101 | 0380 | | Correction to the usage monitoring control for sponsored data connectivity | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150104 | 0383 | 2 | Access network information report in case of IP-CAN bearer/IP-CAN session termination | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150136 | 0386 | 1 | Correction to temporary network failure handling | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150114 | 0388 | | TWAN supports access network information report | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150127 | 0389 | 2 | Uniqueness of Sharing Key for resource sharing over Rx | 13.0.0 | 13.1.0 | +| 03-2015 | CT-67 | CP-150133 | 0394 | 2 | Add the ToS-Traffic-Class AVP to the Rx to be sent by AF | 13.0.0 | 13.1.0 | +| 06-2015 | CT-68 | CP-150362 | 0390 | 3 | Clarification of the Called-Station-Id | 13.1.0 | 13.2.0 | +| 06-2015 | CT-68 | CP-150361 | 0395 | 1 | Removing restrictions to report RAT type to the AF | 13.1.0 | 13.2.0 | +| 06-2015 | CT-68 | CP-150356 | 0396 | 2 | Alignment with SDP procedures for resource sharing | 13.1.0 | 13.2.0 | +| 06-2015 | CT-68 | CP-150363 | 0398 | 1 | Adding TWAN and untrusted WLAN release cause | 13.1.0 | 13.2.0 | +| 06-2015 | CT-68 | CP-150356 | 0399 | - | Sharing-Key-UL | 13.1.0 | 13.2.0 | +| 06-2015 | CT-68 | CP-150344 | 0405 | 2 | Non-3GPP access for 3GPP-SGSN-MCC-MNC | 13.1.0 | 13.2.0 | +| 06-2015 | CT-68 | CP-150362 | 0406 | - | Correcting Hanging Paragraphs | 13.1.0 | 13.2.0 | +| 09-2015 | CT-69 | CP-150485 | 0401 | 4 | Clarification of the IP-Domain-Id | 13.2.0 | 13.3.0 | +| 09-2015 | CT-69 | CP-150476 | 0408 | 2 | Corrections to the PCRF-based P-CSCF Restoration Enhancement | 13.2.0 | 13.3.0 | +| 09-2015 | CT-69 | CP-150472 | 0410 | - | AVPs applicability for RAN-NAS-Cause | 13.2.0 | 13.3.0 | +| 09-2015 | CT-69 | CP-150480 | 0411 | 1 | Events applicability to support monitoring | 13.2.0 | 13.3.0 | +| 09-2015 | CT-69 | CP-150482 | 0412 | 2 | Change of chargeable party when sponsor connectivity applies | 13.2.0 | 13.3.0 | +| 09-2015 | CT-69 | CP-150476 | 0415 | 1 | Correction to the P-CSCF restoration enhancement | 13.2.0 | 13.3.0 | +| 09-2015 | CT-69 | CP-150468 | 0421 | 2 | Fixing Ambiguous Flag Rules for AVPs reused from TS 29.061 | 13.2.0 | 13.3.0 | +| 12-2015 | CT-70 | CP-150797 | 0422 | 1 | Update the PCC architecture figures in 29.214 | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150666 | 0423 | 1 | RTP/RTCP transport multiplexing | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150663 | 0424 | 2 | Support of new bandwidth information over Rx | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150789 | 0425 | - | Incorrect command name to request access network information | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150631 | 0427 | 1 | Update the reference of draft-ietf-dime-ovli | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150730 | 0428 | 1 | Diameter message priority for PCC i | 13.3.0 | 13.4.0 | +| 12-2015 | CT-70 | CP-150668 | 0432 | 2 | Location report to support emergency service in Untrusted WLAN access | 13.3.0 | 13.4.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-03 | CT#71 | CP-160095 | 0435 | 2 | F | Rx impact for background data transfer | 13.5.0 | +| 2016-03 | CT#71 | CP-160101 | 0436 | - | F | ICSI format specification over Rx | 13.5.0 | +| 2016-03 | CT#71 | CP-160100 | 0437 | 3 | A | Reporting of NAS/RAN cause in the STA command | 13.5.0 | +| 2016-03 | CT#71 | CP-160101 | 0438 | 2 | F | RAN-NAS-Cause handling upon unsuccessful bearer termination over Rx | 13.5.0 | +| 2016-03 | CT#71 | CP-160092 | 0441 | 1 | B | UE-to-network relay PCC handling over Rx | 13.5.0 | +| 2016-03 | CT#71 | CP-160101 | 0442 | 1 | F | Support of removed filters when SIP Forking applies over Rx | 13.5.0 | +| 2016-03 | CT#71 | CP-160094 | 0443 | - | F | Missing experimental result code value | 13.5.0 | +| 2016-03 | CT#71 | CP-160104 | 0444 | - | F | Location reporting for IMS sessions over S2b | 13.5.0 | +| 2016-03 | CT#71 | CP-160093 | 0446 | 2 | B | Reservation-Priority AVP and DRMP AVP Interaction | 13.5.0 | +| 2016-03 | CT#71 | CP-160087 | 0448 | 2 | B | New clause to Appendix A for the handling of MCPTT emergency calls | 13.5.0 | +| 2016-06 | CT#72 | CP-160282 | 0450 | 2 | F | Support of IP version as part of the enhanced bandwidth mechanisms for MTSI sessions | 13.6.0 | +| 2016-06 | CT#72 | CP-160287 | 0451 | 4 | F | Priority sharing for concurrent sessions | 13.6.0 | +| 2016-06 | CT#72 | CP-160271 | 0453 | 1 | F | Reuse of TWAN-Identifier AVP in the Untrusted WLAN Access | 13.6.0 | +| 2016-06 | CT#72 | CP-160275 | 0455 | - | A | Correction to the time-based usage monitoring for sponsored data connectivity | 13.6.0 | +| 2016-06 | CT#72 | CP-160251 | 0456 | 4 | F | Authorization based on transfer policy | 13.6.0 | +| 2016-06 | CT#72 | CP-160251 | 0457 | 1 | F | Correction to the usage monitoring when the sponsoring is disabled | 13.6.0 | +| 2016-06 | CT#72 | CP-160251 | 0458 | 2 | F | Code of Sponsoring-Action AVP | 13.6.0 | +| 2016-06 | CT#72 | CP-160263 | 0459 | 1 | F | Correction to MCPTT priority call handling | 13.6.0 | +| 2016-06 | CT#72 | CP-160276 | 0461 | - | F | Inclusion of Transient failure code | 13.6.0 | +| 2016-06 | CT#72 | CP-160274 | 0449 | 3 | B | Clarification on the gate control procedure over Rx interface | 14.0.0 | +| 2016-06 | CT#72 | CP-160274 | 0452 | 2 | B | Report of modification failure over Rx reference point | 14.0.0 | +| 2016-09 | CT#73 | CP-160461 | 0463 | 2 | A | Addition of UDP/TCP port and ePDG address as untrusted WLAN location information | 14.1.0 | +| 2016-09 | CT#73 | CP-160445 | 0467 | 1 | A | Disabling/removing priority sharing for media flow | 14.1.0 | +| 2016-09 | CT#73 | CP-160442 | 0469 | - | A | Correction of IETF drmp draft version | 14.1.0 | +| 2016-09 | CT#73 | CP-160458 | 0471 | 2 | A | IP-CAN type and RAT type report over Rx | 14.1.0 | +| 2016-09 | CT#73 | CP-160452 | 0472 | - | F | Correction of the reference name for UMTS | 14.1.0 | +| 2016-09 | CT#73 | CP-160452 | 0473 | - | F | Gate control procedures based on the configuration in the P-CSCF | 14.1.0 | +| 2016-09 | CT#73 | CP-160444 | 0475 | 1 | A | PCRF authorization when the transfer policy has not been valid | 14.1.0 | +| 2016-09 | CT#73 | CP-160444 | 0477 | 1 | A | Transfer policy expires when the session is ongoing | 14.1.0 | +| 2016-09 | CT#73 | CP-160456 | 0480 | 1 | B | Subscription to notification of PLMN id change over Rx | 14.1.0 | +| 2016-09 | CT#73 | CP-160463 | 0481 | 1 | B | Support of sponsored data connectivity for TDF | 14.1.0 | +| 2016-12 | CT#74 | CP-160636 | 0484 | 4 | A | Remove "same media type" requirement for Priority Sharing | 14.2.0 | +| 2016-12 | CT#74 | CP-160615 | 0487 | 1 | B | Diameter Load Control Mechanism | 14.2.0 | +| 2016-12 | CT#74 | CP-160630 | 0488 | 1 | B | Support for subscription to changes to IP-CAN by P-CSCF for session setup | 14.2.0 | +| 2016-12 | CT#74 | CP-160630 | 0489 | 5 | B | Provision of EPC-level identities for IMS emergency sessions over Rx | 14.2.0 | +| 2016-12 | CT#74 | CP-160633 | 0490 | 1 | F | Inclusion of 3GPP-SGSN-MCC-MNC AVP in the AAA command | 14.2.0 | +| 2016-12 | CT#74 | CP-160625 | 0491 | 2 | B | PCC impacts due to multi-stream multiparty conferencing media handling | 14.2.0 | +| 2016-12 | CT#74 | CP-160622 | 0494 | 1 | A | Reference update draft-holmberg-dispatch-mcptt-rp-namespace | 14.2.0 | +| 2016-12 | CT#74 | CP-160628 | 0495 | 2 | B | AF triggers the activation of PCC/ADC rule with application identifier | 14.2.0 | +| 2016-12 | CT#74 | CP-160630 | 0497 | - | F | Enhance the description about Permanent Failures | 14.2.0 | +| 2016-12 | CT#74 | CP-160614 | 0500 | - | A | Correction to change IETF drmp draft version to official RFC 7944 | 14.2.0 | +| 2016-12 | CT#74 | CP-160616 | 0501 | 1 | F | Diameter base protocol specification update | 14.2.0 | +| 2016-12 | CT#74 | CP-160630 | 0502 | 6 | B | Handling of multiple Rx interactions for the same media component | 14.2.0 | +| 2016-12 | CT#74 | CP-160630 | 0503 | 1 | F | Correction to the usage of Media-Component-Status AVP | 14.2.0 | +| 2017-03 | CT#75 | CP-170081 | 0506 | - | A | Reference update draft-holmberg-dispatch-mcptt-rp-namespace | 14.3.0 | +| 2017-03 | CT#75 | CP-170076 | 0507 | 1 | F | Handling of Vendor-Specific-Application-Id AVP | 14.3.0 | +| 2017-03 | CT#75 | CP-170086 | 0509 | 3 | F | Network provided location information retrieval at SDP offer time for mobile terminating call | 14.3.0 | +| 2017-03 | CT#75 | CP-170086 | 0510 | 2 | F | Correction to the Media-Component-Status AVP | 14.3.0 | +| 2017-03 | CT#75 | CP-170081 | 0511 | 2 | C | Pre-emption control for priority sharing | 14.3.0 | +| 2017-03 | CT#75 | CP-170076 | 0512 | - | F | Update instance number for the Failed-AVP in answer commands | 14.3.0 | +| 2017-06 | CT#76 | CP-171119 | 0514 | 1 | F | Reference update for draft-ietf-dime-load | 14.4.0 | +| 2017-06 | CT#76 | CP-171133 | 0517 | 1 | F | Network provided location information retrieval at SDP offer time for mobile terminating call | 14.4.0 | +| 2017-06 | CT#76 | CP-171138 | 0518 | 1 | F | PCC Support of emergency IMS registration for S8HR cases | 14.4.0 | +| 2017-06 | CT#76 | CP-171128 | 0520 | - | A | Reference update draft-holmberg-dispatch-mcptt-rp-namespace | 14.4.0 | +| 2017-06 | CT#76 | CP-171133 | 0530 | 1 | F | Correction to pre-emption control for priority sharing | 14.4.0 | +| 2017-06 | CT#76 | CP-171133 | 1573 | 1 | F | Correction to the priority sharing | 14.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------|--------| +| 2017-06 | CT#76 | CP-171126 | 1576 | 2 | F | Updating references to align with rel-14 MCPTT stage 2 restructuring | 14.4.0 | +| 2017-06 | CT#76 | CP-171133 | 1577 | 2 | F | Correction to the supported feature value for MCPTT Pre-emption | 14.4.0 | +| 2017-06 | CT#76 | CP-171138 | 1579 | 2 | F | PCC Support of emergency IMS registration for S8HR cases | 14.4.0 | +| 2017-06 | CT#76 | CP-171136 | 1578 | 2 | F | Activate the transfer policy via chargeable party change procedure | 15.0.0 | +| 2017-09 | CT#77 | CP-172038 | 1580 | 1 | B | Extension of QoS values. | 15.1.0 | +| 2017-09 | CT#77 | CP-172042 | 1584 | - | A | NetLoc corrections in trusted WLAN. | 15.1.0 | +| 2017-09 | CT#77 | CP-172048 | 1587 | 1 | A | NetLoc corrections in untrusted WLAN. | 15.1.0 | +| 2017-09 | CT#77 | CP-172041 | 1590 | - | A | Correction for Monitoring Event support. | 15.1.0 | +| 2017-09 | CT#77 | CP-172051 | 1593 | 2 | F | Some corrections of 29.214. | 15.1.0 | +| 2017-12 | CT#78 | CP-173101 | 1596 | - | A | AN-GW-Address correction. | 15.2.0 | +| 2017-12 | CT#78 | CP-173103 | 1602 | - | F | Correction on Codec-Data AVP | 15.2.0 | +| 2018-03 | CT#79 | CP-180047 | 1602 | 3 | A | Clarification of Max-Requested-Bandwidth | 15.3.0 | +| 2018-03 | CT#79 | CP-180043 | 1607 | - | A | Timezone correction for NetLoc in untrusted WLAN | 15.3.0 | +| 2018-03 | CT#79 | CP-180037 | 1608 | 1 | B | Extending the TS scope to cover 5GS impacts | 15.3.0 | +| 2018-03 | CT#79 | CP-180037 | 1609 | 1 | B | Policy and Charging Control over Rx interface in the 5GS | 15.3.0 | +| 2018-03 | CT#79 | CP-180045 | 1612 | 2 | A | Erroneous M bit setting on Supported-Features | 15.3.0 | +| 2018-06 | CT#80 | CP-181023 | 1613 | 1 | F | Definition of Bit Rate | 15.4.0 | +| 2018-06 | CT#80 | CP-181019 | 1614 | 3 | B | Support for volume based charging of IMS services | 15.4.0 | +| 2018-06 | CT#80 | CP-181013 | 1616 | 1 | B | Updates to 3GPP-User-Location-Info AVP | 15.4.0 | +| 2018-06 | CT#80 | CP-181171 | 1618 | 1 | A | Support priority for MCVideo services | 15.4.0 | +| 2018-12 | CT#82 | CP-183118 | 1622 | 1 | F | Removal of editor's note on Volume Based Charging | 15.5.0 | +| 2019-03 | CT#83 | CP-190118 | 1623 | 2 | F | The mapping of Access-Type with IP-CAN-Type | 15.6.0 | +| 2019-09 | CT#85 | CP-192154 | 1626 | 1 | A | draft-ietf-dime-load published as RFC 8583 | 15.7.0 | +| 2019-09 | CT#85 | CP-192164 | 1624 | 1 | B | Support for Restricted Local Operator Services | 16.0.0 | +| 2019-12 | CT#86 | CP-193215 | 1628 | 6 | B | Coverage and Handover Enhancements for Media (CHEM) | 16.1.0 | +| 2019-12 | CT#86 | CP-193221 | 1631 | 5 | B | Adding Caller and Callee information | 16.1.0 | +| 2020-03 | CT#87e | CP-200215 | 1632 | 1 | B | Support of Framework for Live Uplink Streaming (FLUS) in Rx interface | 16.2.0 | +| 2020-03 | CT#87e | CP-200231 | 1635 | 1 | B | Report of EPS Fallback | 16.2.0 | +| 2020-03 | CT#87e | CP-200201 | 1636 | 2 | B | 5G SRVCC impacts on Rx | 16.2.0 | +| 2020-06 | CT#88e | CP-201245 | 1639 | - | A | Missing annex A.10.5 (network provided location information at SIP session release) | 16.3.0 | +| 2020-06 | CT#88e | CP-201229 | 1640 | 3 | B | Access Type Report for a MA PDU session | 16.3.0 | +| 2020-06 | CT#88e | CP-201245 | 1642 | 2 | A | Clarification on FlowDescription | 16.3.0 | +| 2020-06 | CT#88e | CP-201246 | 1643 | 1 | B | Support of applications with specific QoS hints | 16.3.0 | +| 2020-06 | CT#88e | CP-201269 | 1644 | 1 | B | Reallocation of credit reporting to the AF | 16.3.0 | +| 2020-06 | CT#88e | CP-201252 | 1646 | 2 | B | Providing NID to the P-CSCF | 16.3.0 | +| 2020-09 | CT#89e | CP-202051 | 1648 | 1 | A | Correction to RAN-NAS Release Cause feature | 16.4.0 | +| 2020-09 | CT#89e | CP-202059 | 1649 | 1 | F | Correction to E.2 | 16.4.0 | +| 2020-09 | CT#89e | CP-202059 | 1650 | 1 | F | Support of 5GS non-3GPP Trusted Access | 16.4.0 | +| 2020-09 | CT#89e | CP-202059 | 1651 | 1 | F | Support of 5GS Wireline Access | 16.4.0 | +| 2021-06 | CT#92e | CP-211253 | 1653 | 3 | B | IMEI over Rx reference point | 17.0.0 | +| 2021-06 | CT#92e | CP-211226 | 1654 | 3 | B | AF Session for Control of MPS for DTS | 17.0.0 | +| 2021-06 | CT#92e | CP-211254 | 1655 | - | F | Correction to Netloc-Untrusted-WLAN | 17.0.0 | +| 2021-09 | CT#93e | CP-211254 | 1656 | 1 | B | 29.214 Authorization for MPS for DTS | 17.1.0 | +| 2021-09 | CT#93e | CP-212201 | 1657 | 1 | B | 5GS-Level UE identities | 17.1.0 | +| 2021-09 | CT#93e | CP-212224 | 1658 | - | F | Clarification of resource allocation failure | 17.1.0 | +| 2021-09 | CT#93e | CP-212224 | 1661 | 1 | F | Report of 3GPP and non-3GPP user location | 17.1.0 | +| 2021-09 | CT#93e | CP-212200 | 1663 | 1 | A | Support of TCP and UDP ports in non-3GPP UE location | 17.1.0 | +| 2021-12 | CT#94e | CP-213225 | 1664 | 1 | B | 5GS-Level Identify for NAI | 17.2.0 | +| 2021-12 | CT#94e | CP-213215 | 1669 | - | A | Correction of an invalid 3GPP-User-Location-Info value | 17.2.0 | +| 2021-12 | CT#94e | CP-213229 | 1671 | 1 | B | 5GS Level Identities in SNPN scenarios | 17.2.0 | +| 2022-03 | CT#95e | CP-220196 | 1673 | 1 | F | Correction to enable retrieval of Network Provided Location information in a MESSAGE request | 17.3.0 | +| 2022-03 | CT#95e | CP-220171 | 1675 | - | A | Correction to EPS Fallback | 17.3.0 | +| 2022-03 | CT#95e | CP-220195 | 1676 | 1 | B | Correction to enable retrieval of Network Provided Location information at mid-call access change | 17.3.0 | +| 2022-09 | CT#97e | CP-222125 | 1677 | 1 | F | Untrusted WLAN location information | 17.4.0 | +| 2022-09 | CT#97e | CP-222115 | 1678 | - | F | Allocate the value to FAILED_QOS_UPDATE | 17.4.0 | +| 2022-09 | CT#97e | CP-222125 | 1679 | - | F | Report of Access Network Charging Address | 17.4.0 | +| 2023-03 | CT#99 | CP-230175 | 1680 | 1 | F | EPC AF signalling note | 18.0.0 | +| 2023-03 | CT#99 | CP-230174 | 1681 | - | F | Flow Description for MPS for DTS AF signalling flow | 18.0.0 | +| 2023-03 | CT#99 | CP-230174 | 1682 | - | F | Format handling for 3GPP-User-Location-Info AVP | 18.0.0 | +| 2023-06 | CT#100 | CP-231133 | 1683 | 1 | F | Handling of 3GPP User Location | 18.1.0 | +| 2023-06 | CT#100 | CP-231170 | 1686 | - | A | Corrections for the RAT types | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29222/raw.md b/marked/Rel-18/29_series/29222/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3decedac0d3b08edb40d403fa4cab332cd61eee2 --- /dev/null +++ b/marked/Rel-18/29_series/29222/raw.md @@ -0,0 +1,10083 @@ + + +# 3GPP TS 29.222 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Common API Framework for 3GPP Northbound APIs; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above it and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. + +Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices + +Keywords +5G System + +**3GPP** + +Postal address + +3GPP support office address +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + + +**3GPP** + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword..... | 14 | +| 1 Scope..... | 15 | +| 2 References..... | 15 | +| 3 Definitions and abbreviations..... | 16 | +| 3.1 Definitions..... | 16 | +| 3.2 Abbreviations..... | 16 | +| 4 Overview..... | 17 | +| 4.1 Introduction..... | 17 | +| 4.2 Service Architecture..... | 17 | +| 4.3 Functional Entities..... | 17 | +| 4.3.1 API invoker..... | 17 | +| 4.3.2 CAPIF core function..... | 17 | +| 4.3.3 API exposing function..... | 17 | +| 4.3.4 API publishing function..... | 17 | +| 4.3.5 API management function..... | 17 | +| 5 Services offered by the CAPIF Core Function..... | 17 | +| 5.1 Introduction of Services..... | 17 | +| 5.2 CAPIF_Discover_Service_API..... | 19 | +| 5.2.1 Service Description..... | 19 | +| 5.2.1.1 Overview..... | 19 | +| 5.2.2 Service Operations..... | 19 | +| 5.2.2.1 Introduction..... | 19 | +| 5.2.2.2 Discover_Service_API..... | 20 | +| 5.2.2.2.1 General..... | 20 | +| 5.2.2.2.2 Consumer discovering service API using Discover_Service_API service operation..... | 20 | +| 5.3 CAPIF_Publish_Service_API..... | 20 | +| 5.3.1 Service Description..... | 20 | +| 5.3.1.1 Overview..... | 20 | +| 5.3.2 Service Operations..... | 21 | +| 5.3.2.1 Introduction..... | 21 | +| 5.3.2.2 Publish_Service_API..... | 21 | +| 5.3.2.2.1 General..... | 21 | +| 5.3.2.2.2 API publishing function publishing service APIs on CAPIF core function using Publish_Service_API service operation..... | 21 | +| 5.3.2.2.3 CAPIF core function publishing service APIs on other CAPIF core function using Publish_Service_API service operation..... | 22 | +| 5.3.2.3 Unpublish_Service_API..... | 23 | +| 5.3.2.3.1 General..... | 23 | +| 5.3.2.3.2 Consumer un-publishing service APIs from CAPIF core function using Unpublish_Service_API service operation..... | 23 | +| 5.3.2.4 Get_Service_API..... | 23 | + +# Copyright Notification + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +| | | | +|-----------|-----------------------------------------------------------------------------------------------------------------|----| +| 5.3.2.4.1 | General..... | 23 | +| 5.3.2.4.2 | Consumer retrieving service APIs from CAPIF core function using Get_Service_API service operation..... | 23 | +| 5.3.2.5 | Update_Service_API..... | 24 | +| 5.3.2.5.1 | General..... | 24 | +| 5.3.2.5.2 | Consumer updating published service APIs on CAPIF core function using Update_Service_API service operation..... | 24 | +| 5.4 | CAPIF_Events_API..... | 25 | +| 5.4.1 | Service Description..... | 25 | +| 5.4.1.1 | Overview..... | 25 | +| 5.4.2 | Service Operations..... | 25 | +| 5.4.2.1 | Introduction..... | 25 | +| 5.4.2.2 | Subscribe_Event..... | 25 | +| 5.4.2.2.1 | General..... | 25 | +| 5.4.2.2.2 | Subscribing to CAPIF events using Subscribe_Event service operation..... | 25 | +| 5.4.2.3 | Unsubscribe_Event..... | 26 | +| 5.4.2.3.1 | General..... | 26 | +| 5.4.2.3.2 | Unsubscribing from CAPIF events using Unsubscribe_Event service operation..... | 26 | +| 5.4.2.4 | Notify_Event..... | 27 | +| 5.4.2.4.1 | General..... | 27 | +| 5.4.2.4.2 | Notifying CAPIF events using Notify_Event service operation..... | 27 | +| 5.4.2.5 | Update_Event_Subscription..... | 27 | +| 5.4.2.5.1 | General..... | 27 | +| 5.4.2.5.2 | Update Subscription to CAPIF events using Update_Event_Subscription service operation..... | 27 | +| 5.5 | CAPIF_API_Invoker_Management_API..... | 28 | +| 5.5.1 | Service Description..... | 28 | +| 5.5.1.1 | Overview..... | 28 | +| 5.5.2 | Service Operations..... | 28 | +| 5.5.2.1 | Introduction..... | 28 | +| 5.5.2.2 | Onboard_API_Invoker..... | 28 | +| 5.5.2.2.1 | General..... | 28 | +| 5.5.2.2.2 | API invoker on-boarding itself as a recognized user of CAPIF using Onboard_API_Invoker service operation..... | 28 | +| 5.5.2.3 | Offboard_API_Invoker..... | 29 | +| 5.5.2.3.1 | General..... | 29 | +| 5.5.2.3.2 | API invoker off-boarding itself as a recognized user of CAPIF using Offboard_API_Invoker service operation..... | 29 | +| 5.5.2.4 | Notify_Onboarding_Completion..... | 30 | +| 5.5.2.4.1 | General..... | 30 | +| 5.5.2.4.2 | Notifying Onboarding completion using Notify_Onboarding_Completion service operation..... | 30 | +| 5.5.2.5 | Update_API_Invoker_Details..... | 30 | +| 5.5.2.5.1 | General..... | 30 | +| 5.5.2.5.2 | API invoker updating its details on CAPIF using Update_API_Invoker_Details service operation..... | 30 | +| 5.5.2.6 | Notify_Update_Completion..... | 31 | +| 5.5.2.6.1 | General..... | 31 | +| 5.5.2.6.2 | Notifying API invoker update completion using Notify_Update_Completion service operation..... | 31 | +| 5.6 | CAPIF_Security_API..... | 32 | +| 5.6.1 | Service Description..... | 32 | +| 5.6.1.1 | Overview..... | 32 | +| 5.6.2 | Service Operations..... | 32 | +| 5.6.2.1 | Introduction..... | 32 | +| 5.6.2.2 | Obtain_Security_Method..... | 32 | +| 5.6.2.2.1 | General..... | 32 | +| 5.6.2.2.2 | Request service API security method from CAPIF using Obtain_Security_Method service operation..... | 33 | +| 5.6.2.3 | Obtain_Authorization..... | 33 | +| 5.6.2.3.1 | General..... | 33 | +| 5.6.2.3.2 | Obtain authorization using Obtain_Authorization service operation..... | 33 | +| 5.6.2.3.3 | Obtain authorization code using Obtain_Authorization service operation..... | 34 | + +| | | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 5.6.2.4 | Obtain_API_Invoker_Info..... | 34 | +| 5.6.2.4.1 | General..... | 34 | +| 5.6.2.4.2 | Obtain API invoker's security information using Obtain_API_Invoker_Info service operation..... | 34 | +| 5.6.2.5 | Revoke_Authentication..... | 35 | +| 5.6.2.5.1 | General..... | 35 | +| 5.6.2.5.2 | Invalidate authorization using Revoke_Authorization service operation..... | 35 | +| 5.7 | CAPIF_Monitoring_API..... | 35 | +| 5.8 | CAPIF_Logging_API_Invocation_API..... | 35 | +| 5.8.1 | Service Description..... | 35 | +| 5.8.1.1 | Overview..... | 35 | +| 5.8.2 | Service Operations..... | 36 | +| 5.8.2.1 | Introduction..... | 36 | +| 5.8.2.2 | Log_API_Invocation_API..... | 36 | +| 5.8.2.2.1 | General..... | 36 | +| 5.8.2.2.2 | Logging service API invocations using Log_API_Invocation service operation..... | 36 | +| 5.9 | CAPIF_Auditing_API..... | 36 | +| 5.9.1 | Service Description..... | 36 | +| 5.9.1.1 | Overview..... | 36 | +| 5.9.2 | Service Operations..... | 37 | +| 5.9.2.1 | Introduction..... | 37 | +| 5.9.2.2 | Query_Invocation_Logs_API..... | 37 | +| 5.9.2.2.1 | General..... | 37 | +| 5.9.2.2.2 | Query API invocation information logs using Query_Invocation_Logs service operation..... | 37 | +| 5.10 | CAPIF_Access_Control_Policy_API..... | 37 | +| 5.10.1 | Service Description..... | 37 | +| 5.10.1.1 | Overview..... | 37 | +| 5.10.2 | Service Operations..... | 38 | +| 5.10.2.1 | Introduction..... | 38 | +| 5.10.2.2 | Obtain_Access_Control_Policy..... | 38 | +| 5.10.2.2.1 | General..... | 38 | +| 5.10.2.2.2 | API exposing function obtaining access control policy from the CAPIF core function using Obtain_Access_Control_Policy service operation..... | 38 | +| 5.10.3 | Related Events..... | 38 | +| 5.11 | CAPIF_API_Provider_Management_API..... | 38 | +| 5.11.1 | Service Description..... | 38 | +| 5.11.1.1 | Overview..... | 38 | +| 5.11.2 | Service Operations..... | 39 | +| 5.11.2.1 | Introduction..... | 39 | +| 5.11.2.2 | Register_API_Provider..... | 39 | +| 5.11.2.2.1 | General..... | 39 | +| 5.11.2.2.2 | API provider domain functions registering as a recognized API provider domain function of CAPIF using Register_API_Provider service operation..... | 39 | +| 5.11.2.3 | Update_API_Provider..... | 39 | +| 5.11.2.3.1 | General..... | 39 | +| 5.11.2.3.2 | API management function updating API provider domain function details on CAPIF using Update_API_Provider service operation..... | 40 | +| 5.11.2.4 | Deregister_API_Provider..... | 40 | +| 5.11.2.4.1 | General..... | 40 | +| 5.11.2.4.2 | API provider domain functions deregistering as a recognized API provider domain function of CAPIF using Deregister_API_Provider service operation..... | 40 | +| 5.12 | CAPIF_Routing_Info_API..... | 41 | +| 5.12.1 | Service Description..... | 41 | +| 5.12.1.1 | Overview..... | 41 | +| 5.12.2 | Service Operations..... | 41 | +| 5.12.2.1 | Introduction..... | 41 | +| 5.12.2.2 | Obtain_Routing_Info..... | 41 | +| 5.12.2.2.1 | General..... | 41 | +| 5.12.2.2.2 | API exposing function obtaining API routing information from the CAPIF core function using Obtain_Routing_Info service operation..... | 41 | +| 6 | Services offered by the API exposing function..... | 42 | +| 6.1 | Introduction of Services..... | 42 | + +| | | | +|-------------|---------------------------------------------------------------------------------------------|----| +| 6.2 | AEF_Security_API..... | 42 | +| 6.2.1 | Service Description..... | 42 | +| 6.2.1.1 | Overview..... | 42 | +| 6.2.2 | Service Operations..... | 42 | +| 6.2.2.1 | Introduction..... | 42 | +| 6.2.2.2 | Initiate_Authentication..... | 43 | +| 6.2.2.2.1 | General..... | 43 | +| 6.2.2.2.2 | API invoker initiating authentication using Initiate_Authentication service operation..... | 43 | +| 6.2.2.3 | Revoke_Authorization..... | 43 | +| 6.2.2.3.1 | General..... | 43 | +| 6.2.2.3.2 | CAPIF core function initiating revocation using Revoke_Authorization service operation..... | 43 | +| 7 | CAPIF Design Aspects Common for All APIs..... | 43 | +| 7.1 | General..... | 43 | +| 7.2 | Data Types..... | 44 | +| 7.2.1 | General..... | 44 | +| 7.2.2 | Referenced structured data types..... | 44 | +| 7.2.3 | Referenced Simple data types and enumerations..... | 44 | +| 7.3 | Usage of HTTP..... | 45 | +| 7.4 | Content type..... | 45 | +| 7.5 | URI structure..... | 45 | +| 7.6 | Notifications..... | 46 | +| 7.7 | Error handling..... | 46 | +| 7.8 | Feature negotiation..... | 46 | +| 7.9 | HTTP headers..... | 46 | +| 7.10 | Conventions for Open API specification files..... | 46 | +| 7.11 | CAPIF vendor-specific extensions..... | 46 | +| 8 | CAPIF API Definition..... | 47 | +| 8.1 | CAPIF_Discover_Service_API..... | 47 | +| 8.1.1 | API URI..... | 47 | +| 8.1.2 | Resources..... | 47 | +| 8.1.2.1 | Overview..... | 47 | +| 8.1.2.2 | Resource: All published service APIs..... | 48 | +| 8.1.2.2.1 | Description..... | 48 | +| 8.1.2.2.2 | Resource Definition..... | 48 | +| 8.1.2.2.3 | Resource Standard Methods..... | 48 | +| 8.1.2.2.3.1 | GET..... | 48 | +| 8.1.2.2.4 | Resource Custom Operations..... | 50 | +| 8.1.2A | Custom Operations without associated resources..... | 50 | +| 8.1.3 | Notifications..... | 50 | +| 8.1.4 | Data Model..... | 50 | +| 8.1.4.1 | General..... | 50 | +| 8.1.4.2 | Structured data types..... | 51 | +| 8.1.4.2.1 | Introduction..... | 51 | +| 8.1.4.2.2 | Type: DiscoveredAPIs..... | 51 | +| 8.1.4.2.3 | Void..... | 51 | +| 8.1.4.2.4 | Type: IpAddrInfo..... | 51 | +| 8.1.4.3 | Simple data types and enumerations..... | 52 | +| 8.1.5 | Error Handling..... | 52 | +| 8.1.5.1 | General..... | 52 | +| 8.1.5.2 | Protocol Errors..... | 52 | +| 8.2.5.3 | Application Errors..... | 52 | +| 8.1.6 | Feature negotiation..... | 52 | +| 8.2 | CAPIF_Publish_Service_API..... | 52 | +| 8.2.1 | API URI..... | 52 | +| 8.2.2 | Resources..... | 53 | +| 8.2.2.1 | Overview..... | 53 | +| 8.2.2.2 | Resource: APF published APIs..... | 53 | +| 8.2.2.2.1 | Description..... | 53 | +| 8.2.2.2.2 | Resource Definition..... | 54 | +| 8.2.2.2.3 | Resource Standard Methods..... | 54 | + +| | | | +|-------------|-----------------------------------------------------|----| +| 8.2.2.2.3.1 | POST..... | 54 | +| 8.2.2.2.3.2 | GET..... | 54 | +| 8.2.2.2.4 | Resource Custom Operations..... | 55 | +| 8.2.2.3 | Resource: Individual APF published API..... | 55 | +| 8.2.2.3.1 | Description..... | 55 | +| 8.2.2.3.2 | Resource Definition..... | 56 | +| 8.2.2.3.3 | Resource Standard Methods..... | 56 | +| 8.2.2.3.3.1 | GET..... | 56 | +| 8.2.2.3.3.2 | PUT..... | 57 | +| 8.2.2.3.3.3 | DELETE..... | 58 | +| 8.2.2.3.3.4 | PATCH..... | 58 | +| 8.2.2.3.4 | Resource Custom Operations..... | 59 | +| 8.2.2A | Custom Operations without associated resources..... | 59 | +| 8.2.3 | Notifications..... | 59 | +| 8.2.4 | Data Model..... | 60 | +| 8.2.4.1 | General..... | 60 | +| 8.2.4.2 | Structured data types..... | 62 | +| 8.2.4.2.1 | Introduction..... | 62 | +| 8.2.4.2.2 | Type: ServiceAPIDescription..... | 62 | +| 8.2.4.2.3 | Type: InterfaceDescription..... | 63 | +| 8.2.4.2.4 | Type: AefProfile..... | 63 | +| 8.2.4.2.5 | Type: Version..... | 64 | +| 8.2.4.2.6 | Type: Resource..... | 64 | +| 8.2.4.2.7 | Type: CustomOperation..... | 65 | +| 8.2.4.2.8 | Type: ShareableInformation..... | 65 | +| 8.2.4.2.9 | Type: PublishedApiPath..... | 65 | +| 8.2.4.2.10 | Type: AefLocation..... | 65 | +| 8.2.4.2.11 | Type: ServiceAPIDescriptionPatch..... | 66 | +| 8.2.4.2.12 | Type: ApiStatus..... | 66 | +| 8.2.4.2.13 | Type: ServiceKpi..... | 67 | +| 8.2.4.2.14 | Type: IpAddrRange..... | 68 | +| 8.2.4.3 | Simple data types and enumerations..... | 68 | +| 8.2.4.3.1 | Introduction..... | 68 | +| 8.2.4.3.2 | Simple data types..... | 68 | +| 8.2.4.3.3 | Enumeration: Protocol..... | 68 | +| 8.2.4.3.4 | Enumeration: DataFormat..... | 69 | +| 8.2.4.3.5 | Enumeration: CommunicationType..... | 69 | +| 8.2.4.3.6 | Enumeration: SecurityMethod..... | 69 | +| 8.2.4.3.7 | Enumeration: Operation..... | 69 | +| 8.2.5 | Error Handling..... | 69 | +| 8.2.5.1 | General..... | 69 | +| 8.2.5.2 | Protocol Errors..... | 70 | +| 8.2.5.3 | Application Errors..... | 70 | +| 8.2.6 | Feature negotiation..... | 70 | +| 8.3 | CAPIF_Events_API..... | 70 | +| 8.3.1 | API URI..... | 70 | +| 8.3.2 | Resources..... | 71 | +| 8.3.2.1 | Overview..... | 71 | +| 8.3.2.2 | Resource: CAPIF Events Subscriptions..... | 72 | +| 8.3.2.2.1 | Description..... | 72 | +| 8.3.2.2.2 | Resource Definition..... | 72 | +| 8.3.2.2.3 | Resource Standard Methods..... | 72 | +| 8.3.2.2.3.1 | POST..... | 72 | +| 8.3.2.2.4 | Resource Custom Operations..... | 73 | +| 8.3.2.3 | Resource: Individual CAPIF Events Subscription..... | 73 | +| 8.3.2.3.1 | Description..... | 73 | +| 8.3.2.3.2 | Resource Definition..... | 73 | +| 8.3.2.3.3 | Resource Standard Methods..... | 73 | +| 8.3.2.3.3.1 | DELETE..... | 73 | +| 8.3.2.3.3.2 | PUT..... | 74 | +| 8.3.2.3.3.3 | PATCH..... | 75 | + +| | | | +|-------------|-----------------------------------------------------|----| +| 8.3.2.3.4 | Resource Custom Operations..... | 76 | +| 8.3.2A | Custom Operations without associated resources..... | 76 | +| 8.3.3 | Notifications..... | 76 | +| 8.3.3.1 | General..... | 76 | +| 8.3.3.2 | Event Notification..... | 76 | +| 8.3.3.2.1 | Description..... | 76 | +| 8.3.3.2.2 | Notification definition..... | 76 | +| 8.3.4 | Data Model..... | 77 | +| 8.3.4.1 | General..... | 77 | +| 8.3.4.2 | Structured data types..... | 78 | +| 8.3.4.2.1 | Introduction..... | 78 | +| 8.3.4.2.2 | Type: EventSubscription..... | 79 | +| 8.3.4.2.3 | Type: EventNotification..... | 79 | +| 8.3.4.2.4 | Type: CAPIFEventFilter..... | 80 | +| 8.3.4.2.5 | Type: CAPIFEventDetail..... | 80 | +| 8.3.4.2.6 | Type: AccessControlPolicyListExt..... | 80 | +| 8.3.4.2.7 | Type: TopologyHiding..... | 80 | +| 8.3.4.2.8 | Type: EventSubscriptionPatch..... | 81 | +| 8.3.4.3 | Simple data types and enumerations..... | 81 | +| 8.3.4.3.1 | Introduction..... | 81 | +| 8.3.4.3.2 | Simple data types..... | 81 | +| 8.3.4.3.3 | Enumeration: CAPIFEvent..... | 82 | +| 8.3.5 | Error Handling..... | 82 | +| 8.3.5.1 | General..... | 82 | +| 8.3.5.2 | Protocol Errors..... | 82 | +| 8.3.5.3 | Application Errors..... | 82 | +| 8.3.6 | Feature negotiation..... | 83 | +| 8.4 | CAPIF_API_Invoker_Management_API..... | 83 | +| 8.4.1 | API URI..... | 83 | +| 8.4.2 | Resources..... | 83 | +| 8.4.2.1 | Overview..... | 83 | +| 8.4.2.2 | Resource: On-boarded API invokers..... | 84 | +| 8.4.2.2.1 | Description..... | 84 | +| 8.4.2.2.2 | Resource Definition..... | 84 | +| 8.4.2.2.3 | Resource Standard Methods..... | 85 | +| 8.4.2.2.3.1 | POST..... | 85 | +| 8.4.2.2.4 | Resource Custom Operations..... | 85 | +| 8.4.2.3 | Resource: Individual On-boarded API Invoker..... | 86 | +| 8.4.2.3.1 | Description..... | 86 | +| 8.4.2.3.2 | Resource Definition..... | 86 | +| 8.4.2.3.3 | Resource Standard Methods..... | 86 | +| 8.4.2.3.3.1 | DELETE..... | 86 | +| 8.4.2.3.3.2 | PUT..... | 87 | +| 8.4.2.3.3.3 | PATCH..... | 88 | +| 8.4.2.3.4 | Resource Custom Operations..... | 89 | +| 8.4.2A | Custom Operations without associated resources..... | 89 | +| 8.4.3 | Notifications..... | 89 | +| 8.4.3.1 | General..... | 89 | +| 8.4.3.2 | Notify_Onboarding_Completion..... | 90 | +| 8.4.3.2.1 | Description..... | 90 | +| 8.4.3.2.2 | Notification definition..... | 90 | +| 8.4.3.3 | Notify_Update_Completion..... | 91 | +| 8.4.3.3.1 | Description..... | 91 | +| 8.4.3.3.2 | Notification definition..... | 91 | +| 8.4.4 | Data Model..... | 92 | +| 8.4.4.1 | General..... | 92 | +| 8.4.4.2 | Structured data types..... | 94 | +| 8.4.4.2.1 | Introduction..... | 94 | +| 8.4.4.2.2 | Type: APIInvokerEnrolmentDetails..... | 94 | +| 8.4.4.2.3 | Type: Void..... | 94 | +| 8.4.4.2.4 | Type: APIList..... | 94 | + +| | | | +|---------------|-----------------------------------------------------|-----| +| 8.4.4.2.5 | Type: OnboardingInformation..... | 95 | +| 8.4.4.2.6 | Type: Void..... | 95 | +| 8.4.4.2.7 | Type: OnboardingNotification..... | 95 | +| 8.4.4.2.8 | Type: APIInvokerEnrolmentDetailsPatch..... | 96 | +| 8.4.4.3 | Simple data types and enumerations..... | 96 | +| 8.4.5 | Error Handling..... | 96 | +| 8.4.5.1 | General..... | 96 | +| 8.4.5.2 | Protocol Errors..... | 96 | +| 8.4.5.3 | Application Errors..... | 96 | +| 8.4.6 | Feature negotiation..... | 96 | +| 8.5 | CAPIF_Security_API..... | 97 | +| 8.5.1 | API URI..... | 97 | +| 8.5.2 | Resources..... | 97 | +| 8.5.2.1 | Overview..... | 97 | +| 8.5.2.2 | Resource: Trusted API invokers..... | 98 | +| 8.5.2.2.1 | Description..... | 98 | +| 8.5.2.2.2 | Resource Definition..... | 98 | +| 8.5.2.2.3 | Resource Standard Methods..... | 98 | +| 8.5.2.2.3.1 | Void..... | 98 | +| 8.5.2.2.4 | Resource Custom Operations..... | 98 | +| 8.5.2.3 | Resource: Individual trusted API invokers..... | 99 | +| 8.5.2.3.1 | Description..... | 99 | +| 8.5.2.3.2 | Resource Definition..... | 99 | +| 8.5.2.3.3 | Resource Standard Methods..... | 99 | +| 8.5.2.3.3.1 | GET..... | 99 | +| 8.5.2.3.3.2 | DELETE..... | 100 | +| 8.5.2.3.3.3 | PUT..... | 101 | +| 8.5.2.3.4 | Resource Custom Operations..... | 102 | +| 8.5.2.3.4.1 | Overview..... | 102 | +| 8.5.2.3.4.2 | Operation: update..... | 102 | +| 8.5.2.3.4.2.1 | Description..... | 102 | +| 8.5.2.3.4.2.2 | Operation Definition..... | 102 | +| 8.5.2.3.4.3 | Operation: delete..... | 103 | +| 8.5.2.3.4.3.1 | Description..... | 103 | +| 8.5.2.3.4.3.2 | Operation Definition..... | 103 | +| 8.5.2.3.4.4 | Operation: token..... | 104 | +| 8.5.2.3.4.4.1 | Description..... | 104 | +| 8.5.2.3.4.4.2 | Operation Definition..... | 104 | +| 8.5.2.3.4.5 | Operation: code..... | 106 | +| 8.5.2.3.4.5.1 | Description..... | 106 | +| 8.5.2.3.4.5.2 | Operation Definition..... | 106 | +| 8.5.2A | Custom Operations without associated resources..... | 107 | +| 8.5.3 | Notifications..... | 107 | +| 8.5.3.1 | General..... | 107 | +| 8.5.3.2 | Authorization revoked notification..... | 107 | +| 8.5.3.2.1 | Description..... | 107 | +| 8.5.3.2.2 | Notification definition..... | 107 | +| 8.5.4 | Data Model..... | 108 | +| 8.5.4.1 | General..... | 108 | +| 8.5.4.2 | Structured data types..... | 110 | +| 8.5.4.2.1 | Introduction..... | 110 | +| 8.5.4.2.2 | Type: ServiceSecurity..... | 110 | +| 8.5.4.2.3 | Type: SecurityInformation..... | 110 | +| 8.5.4.2.4 | Void..... | 111 | +| 8.5.4.2.5 | Type: SecurityNotification..... | 111 | +| 8.5.4.2.6 | Type: AccessTokenReq..... | 112 | +| 8.5.4.2.7 | Type: AccessTokenRsp..... | 113 | +| 8.5.4.2.8 | Type: AccessTokenClaims..... | 114 | +| 8.5.4.2.9 | Type: AccessTokenErr..... | 115 | +| 8.5.4.2.10 | Type: AuthorizationCodeRsp..... | 115 | +| 8.5.4.3 | Simple data types and enumerations..... | 115 | + +| | | | +|-------------|-----------------------------------------------------|-----| +| 8.5.4.3.1 | Introduction..... | 115 | +| 8.5.4.3.2 | Simple data types..... | 115 | +| 8.5.4.3.3 | Enumeration: Cause..... | 116 | +| 8.5.4.3.4 | Enumeration: AuthorizationFlow..... | 116 | +| 8.5.5 | Error Handling..... | 116 | +| 8.5.5.1 | General..... | 116 | +| 8.5.5.2 | Protocol Errors..... | 116 | +| 8.5.5.3 | Application Errors..... | 116 | +| 8.5.6 | Feature negotiation..... | 117 | +| 8.6 | CAPIF_Access_Control_Policy_API..... | 117 | +| 8.6.1 | API URI..... | 117 | +| 8.6.2 | Resources..... | 117 | +| 8.6.2.1 | Overview..... | 117 | +| 8.6.2.2 | Resource: Access Control Policy List..... | 118 | +| 8.6.2.2.1 | Description..... | 118 | +| 8.6.2.2.2 | Resource Definition..... | 118 | +| 8.6.2.2.3 | Resource Standard Methods..... | 119 | +| 8.6.2.2.3.1 | GET..... | 119 | +| 8.6.2.2.4 | Resource Custom Operations..... | 119 | +| 8.6.2A | Custom Operations without associated resources..... | 120 | +| 8.6.3 | Notifications..... | 120 | +| 8.6.4 | Data Model..... | 120 | +| 8.6.4.1 | General..... | 120 | +| 8.6.4.2 | Structured data types..... | 120 | +| 8.6.4.2.1 | Introduction..... | 120 | +| 8.6.4.2.2 | Type: AccessControlPolicyList..... | 120 | +| 8.6.4.2.3 | Type: ApiInvokerPolicy..... | 121 | +| 8.6.4.2.4 | Type: TimeRangeList..... | 121 | +| 8.6.4.3 | Simple data types and enumerations..... | 121 | +| 8.6.5 | Error Handling..... | 121 | +| 8.6.5.1 | General..... | 121 | +| 8.6.5.2 | Protocol Errors..... | 121 | +| 8.6.5.3 | Application Errors..... | 121 | +| 8.6.6 | Feature negotiation..... | 122 | +| 8.7 | CAPIF_Logging_API_Invocation_API..... | 122 | +| 8.7.1 | API URI..... | 122 | +| 8.7.2 | Resources..... | 122 | +| 8.7.2.1 | Overview..... | 122 | +| 8.7.2.2 | Resource: Logs..... | 123 | +| 8.7.2.2.1 | Description..... | 123 | +| 8.7.2.2.2 | Resource Definition..... | 123 | +| 8.7.2.2.3 | Resource Standard Methods..... | 123 | +| 8.7.2.2.3.1 | POST..... | 123 | +| 8.7.2.2.4 | Resource Custom Operations..... | 124 | +| 8.7.2A | Custom Operations without associated resources..... | 124 | +| 8.7.3 | Notifications..... | 124 | +| 8.7.4 | Data Model..... | 124 | +| 8.7.4.1 | General..... | 124 | +| 8.7.4.2 | Structured data types..... | 125 | +| 8.7.4.2.1 | Introduction..... | 125 | +| 8.7.4.2.2 | Type: InvocationLog..... | 125 | +| 8.7.4.2.3 | Type: Log..... | 126 | +| 8.7.4.3 | Simple data types and enumerations..... | 126 | +| 8.7.4.3.1 | Introduction..... | 126 | +| 8.7.4.3.2 | Simple data types..... | 126 | +| 8.7.5 | Error Handling..... | 127 | +| 8.7.5.1 | General..... | 127 | +| 8.7.5.2 | Protocol Errors..... | 127 | +| 8.7.5.3 | Application Errors..... | 127 | +| 8.7.6 | Feature negotiation..... | 127 | +| 8.8 | CAPIF_Auditing_API..... | 127 | + +| | | | +|-------------|---------------------------------------------------------------------------------|-----| +| 8.8.1 | API URI..... | 127 | +| 8.8.2 | Resources..... | 128 | +| 8.8.2.1 | Overview..... | 128 | +| 8.8.2.2 | Resource: All service API invocation logs..... | 128 | +| 8.8.2.2.1 | Description..... | 128 | +| 8.8.2.2.2 | Resource Definition..... | 128 | +| 8.8.2.2.3 | Resource Standard Methods..... | 129 | +| 8.8.2.2.3.1 | GET..... | 129 | +| 8.8.2.2.4 | Resource Custom Operations..... | 130 | +| 8.8.2A | Custom Operations without associated resources..... | 130 | +| 8.8.3 | Notifications..... | 130 | +| 8.8.4 | Data Model..... | 130 | +| 8.8.4.1 | General..... | 130 | +| 8.8.4.2 | Structured data types..... | 131 | +| 8.8.4.2.1 | Introduction..... | 131 | +| 8.8.4.2.2 | Type: InvocationLogs..... | 131 | +| 8.8.4.3 | Simple data types and enumerations..... | 131 | +| 8.8.4.4 | Data types describing alternative data types or combinations of data types..... | 131 | +| 8.8.4.4.1 | Type: InvocationLogsRetrieveRes..... | 131 | +| 8.8.5 | Error Handling..... | 131 | +| 8.8.5.1 | General..... | 131 | +| 8.8.5.2 | Protocol Errors..... | 132 | +| 8.8.5.3 | Application Errors..... | 132 | +| 8.8.6 | Feature negotiation..... | 132 | +| 8.9 | CAPIF_API_Provider_Management_API..... | 132 | +| 8.9.1 | API URI..... | 132 | +| 8.9.2 | Resources..... | 132 | +| 8.9.2.1 | Overview..... | 132 | +| 8.9.2.2 | Resource: All API Provider Domains Registrations..... | 133 | +| 8.9.2.2.1 | Description..... | 133 | +| 8.9.2.2.2 | Resource Definition..... | 133 | +| 8.9.2.2.3 | Resource Standard Methods..... | 134 | +| 8.9.2.2.3.1 | POST..... | 134 | +| 8.9.2.2.4 | Resource Custom Operations..... | 134 | +| 8.9.2.3 | Resource: Individual API Provider Domain Registration..... | 134 | +| 8.9.2.3.1 | Description..... | 134 | +| 8.9.2.3.2 | Resource Definition..... | 134 | +| 8.9.2.3.3 | Resource Standard Methods..... | 135 | +| 8.9.2.3.3.1 | PUT..... | 135 | +| 8.9.2.3.3.2 | DELETE..... | 136 | +| 8.9.2.3.3.3 | PATCH..... | 137 | +| 8.9.2.3.4 | Resource Custom Operations..... | 138 | +| 8.9.2A | Custom Operations without associated resources..... | 138 | +| 8.9.3 | Notifications..... | 138 | +| 8.9.4 | Data Model..... | 138 | +| 8.9.4.1 | General..... | 138 | +| 8.9.4.2 | Structured data types..... | 139 | +| 8.9.4.2.1 | Introduction..... | 139 | +| 8.9.4.2.2 | Type: APIProviderEnrolmentDetails..... | 139 | +| 8.9.4.2.3 | Type: APIProviderFunctionDetails..... | 140 | +| 8.9.4.2.4 | Type: RegistrationInformation..... | 140 | +| 8.9.4.2.5 | Type: APIProviderEnrolmentDetailsPatch..... | 141 | +| 8.9.4.3 | Simple data types and enumerations..... | 141 | +| 8.9.4.3.1 | Introduction..... | 141 | +| 8.9.4.3.2 | Simple data types..... | 141 | +| 8.9.4.3.3 | Enumeration: ApiProviderFuncRole..... | 141 | +| 8.9.5 | Error Handling..... | 141 | +| 8.9.5.1 | General..... | 141 | +| 8.9.5.2 | Protocol Errors..... | 141 | +| 8.9.5.3 | Application Errors..... | 142 | +| 8.9.6 | Feature negotiation..... | 142 | + +| | | | +|--------------|-------------------------------------------------------------|-----| +| 8.10 | CAPIF_Routing_Info_API..... | 142 | +| 8.10.1 | API URI..... | 142 | +| 8.10.2 | Resources..... | 142 | +| 8.10.2.1 | Overview..... | 142 | +| 8.10.2.2 | Resource: Individual Service API routing info..... | 143 | +| 8.10.2.2.1 | Description..... | 143 | +| 8.10.2.2.2 | Resource Definition..... | 143 | +| 8.10.2.2.3 | Resource Standard Methods..... | 143 | +| 8.10.2.2.3.1 | GET..... | 143 | +| 8.10.2.2.4 | Resource Custom Operations..... | 144 | +| 8.10.2A | Custom Operations without associated resources..... | 144 | +| 8.10.3 | Notifications..... | 145 | +| 8.10.4 | Data Model..... | 145 | +| 8.10.4.1 | General..... | 145 | +| 8.10.4.2 | Structured data types..... | 145 | +| 8.10.4.2.1 | Introduction..... | 145 | +| 8.10.4.2.2 | Type: RoutingInfo..... | 145 | +| 8.10.4.2.3 | Type: RoutingRule..... | 146 | +| 8.10.4.2.4 | Type: Ipv6AddressRange..... | 146 | +| 8.10.4.3 | Simple data types and enumerations..... | 146 | +| 8.10.5 | Error Handling..... | 146 | +| 8.10.5.1 | General..... | 146 | +| 8.10.5.2 | Protocol Errors..... | 146 | +| 8.10.5.3 | Application Errors..... | 146 | +| 8.10.6 | Feature negotiation..... | 146 | +| 9 | AEF API Definition..... | 147 | +| 9.1 | AEF_Security_API..... | 147 | +| 9.1.1 | API URI..... | 147 | +| 9.1.2 | Resources..... | 147 | +| 9.1.2A | Custom Operations without associated resources..... | 147 | +| 9.1.2A.1 | Overview..... | 147 | +| 9.1.2A.2 | Operation: check-authentication..... | 147 | +| 9.1.2A.2.1 | Description..... | 147 | +| 9.1.2A.2.2 | Operation Definition..... | 148 | +| 9.1.2A.3 | Operation: revoke-authorization..... | 148 | +| 9.1.2A.3.1 | Description..... | 148 | +| 9.1.2A.3.2 | Operation Definition..... | 149 | +| 9.1.3 | Notifications..... | 149 | +| 9.1.4 | Data Model..... | 150 | +| 9.1.4.1 | General..... | 150 | +| 9.1.4.2 | Structured data types..... | 150 | +| 9.1.4.2.1 | Introduction..... | 150 | +| 9.1.4.2.2 | Type: CheckAuthenticationReq..... | 150 | +| 9.1.4.2.3 | Type: CheckAuthenticationRsp..... | 150 | +| 9.1.4.2.4 | Type: RevokeAuthorizationReq..... | 151 | +| 9.1.4.2.5 | Type: RevokeAuthorizationRsp..... | 151 | +| 9.1.4.3 | Simple data types and enumerations..... | 151 | +| 9.1.5 | Error Handling..... | 151 | +| 9.1.5.1 | General..... | 151 | +| 9.1.5.2 | Protocol Errors..... | 151 | +| 9.1.5.3 | Application Errors..... | 151 | +| 9.1.6 | Feature negotiation..... | 151 | +| 10 | Security..... | 152 | +| 10.1 | General..... | 152 | +| 10.2 | CAPIF-1/1e security..... | 152 | +| 10.3 | CAPIF-2/2e security and securely invoking service APIs..... | 152 | + +| | | +|--------------------------------------------------------|------------| +| Annex A (normative): OpenAPI specification..... | 152 | +| A.1 General..... | 152 | +| A.2 CAPIF_Discover_Service_API..... | 152 | +| A.3 CAPIF_Publish_Service_API..... | 155 | +| A.4 CAPIF_Events_API..... | 165 | +| A.5 CAPIF_API_Invoker_Management_API..... | 171 | +| A.6 CAPIF_Security_API..... | 176 | +| A.7 CAPIF_Access_Control_Policy_API..... | 183 | +| A.8 CAPIF_Logging_API_Invocation_API..... | 185 | +| A.9 CAPIF_Auditing_API..... | 188 | +| A.10 AEF_Security_API..... | 190 | +| A.11 CAPIF_API_Provider_Management_API..... | 192 | +| A.12 CAPIF_Routing_Info_API..... | 196 | +| Annex B (informative): Change history..... | 199 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present specification describes the protocol for the Common API Framework (CAPIF) for 3GPP Northbound APIs. The CAPIF and the related stage 2 architecture and functional requirements are defined in 3GPP TS 23.222 [2]. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2". +- [3] Open API: "OpenAPI Specification Version 3.0.0", . +- [4] IETF RFC 9112: "HTTP/1.1". +- [5] IETF RFC 9110: "HTTP Semantics". +- [6] Void. +- [7] Void. +- [8] IETF RFC 9111: "HTTP Caching". +- [9] Void. +- [10] IETF RFC 9113: "HTTP/2". +- [11] Void. +- [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [13] IETF RFC 6455: "The Websocket Protocol". +- [14] 3GPP TS 29.122: "T8 reference point for northbound Application Programming Interfaces (APIs)". +- [15] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3". +- [16] 3GPP TS 33.122: "Security Aspects of Common API Framework for 3GPP Northbound APIs". +- [17] Void. +- [18] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". +- [19] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3". +- [20] IETF RFC 7239: "Forwarded HTTP Extension". +- [21] Void. + +- [22] W3C HTML 4.01 Specification, . +- [23] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". +- [24] IETF RFC 7519: "JSON Web Token (JWT)". +- [25] IETF RFC 7515: "JSON Web Signature (JWS)". +- [26] 3GPP TS 29.523: "5G System; Policy Control Event Exposure Service; Stage 3". +- [27] 3GPP TR 21.900: "Technical Specification Group working methods". +- [28] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3" +- [29] IETF RFC 5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". +- [30] 3GPP TS 29.572: "5G System; Location Management Services; Stage 3". + +--- + +## 3 Definitions and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +For the purposes of the present document, the terms and definitions given in clause 3 of 3GPP TS 23.222 [2] shall also apply: + +**API registry:** API registry is a registry maintained by the CAPIF core function to store information about the service APIs based on the data models defined in this specification. The structure of the API registry is out of scope of this specification. + +**Subscriber:** A functional entity that subscribes to another functional entity for notifications. + +### 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------|--------------------------------------------| +| AEF | API Exposing Function | +| AMF | API Management Function | +| APF | API Publishing Function | +| AS | Application Server | +| CAPIF | Common API Framework | +| CCF | CAPIF Core Function | +| JSON | JavaScript Object Notation | +| REST | Representational State Transfer | +| RNAA | Resource owner-aware Northbound API Access | +| SCEF | Service Capability Exposure Function | +| SCS | Service Capability Server | +| SNPN | Stand-alone Non-Public Network | + +--- + +## 4 Overview + +### 4.1 Introduction + +In 3GPP, there are multiple northbound API-related specifications. To avoid duplication and inconsistency of approaches between different API specifications and to specify common services (e.g. authorization), 3GPP has considered in 3GPP TS 23.222 [2] the development of a common API framework (CAPIF) that includes common aspects applicable to any northbound service APIs. + +The present document specifies the APIs needed to support CAPIF. + +### 4.2 Service Architecture + +3GPP TS 23.222 [2] clause 6 specifies the functional entities and domains of the functional model. + +### 4.3 Functional Entities + +#### 4.3.1 API invoker + +The API invoker is typically provided by a 3rd party application provider who has service agreement with PLMN operator or SNPN. The API invoker may reside within the same trust domain as the PLMN operator network or SNPN. + +The API invoker supports several capabilities as defined in 3GPP TS 23.222 [2]. + +#### 4.3.2 CAPIF core function + +The CAPIF core function (CCF) supports the capabilities as defined in 3GPP TS 23.222 [2]. + +#### 4.3.3 API exposing function + +The API exposing function (AEF) is the provider of the Service APIs and is also the service communication entry point of the service API to the API invokers as defined in 3GPP TS 23.222 [2]. + +#### 4.3.4 API publishing function + +The API publishing function (APF) enables the API provider to publish the Service APIs information as defined in 3GPP TS 23.222 [2]. + +#### 4.3.5 API management function + +The API management function (AMF) enables the API provider to perform administration of the Service APIs. The API capabilities are defined in 3GPP TS 23.222 [2]. + +--- + +## 5 Services offered by the CAPIF Core Function + +### 5.1 Introduction of Services + +The table 5.1-1 lists the CAPIF Core Function APIs below the service name. A service description clause for each API gives a general description of the related API. + +**Table 5.1-1: List of CAPIF Services** + +| Service Name | Service Operations | Operation Semantics | Consumer(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---------------------|--------------------------------------------------------------------------------------| +| CAPIF_Discover_Service_API | Discover_Service_API | Request/ Response | API Invoker, CAPIF core function | +| | Event operations (NOTE) | (NOTE) | API Invoker | +| CAPIF_Publish_Service_API | Publish_Service_API | Request/ Response | API Publishing Function, CAPIF core function | +| | Unpublish_Service_API | Request/ Response | API Publishing Function, CAPIF core function | +| | Update_Service_API | Request/ Response | API Publishing Function, CAPIF core function | +| | Get_Service_API | Request/ Response | API Publishing Function, CAPIF core function | +| CAPIF_Events_API | Subscribe_Event | Subscribe/Notify | API Invoker, API Publishing Function, API Management Function, API Exposing Function | +| | Update_Event_Subscription | Subscribe/Notify | API Invoker, API Publishing Function, API Management Function, API Exposing Function | +| | Notify_Event | Subscribe/Notify | API Invoker, API Publishing Function, API Management Function, API Exposing Function | +| | Unsubscribe_Event | Subscribe/Notify | API Invoker, API Publishing Function, API Management Function, API Exposing Function | +| CAPIF_API_Invoker_Management_API | Onboard_API_Invoker | Request/ Response | API Invoker | +| | Offboard_API_Invoker | Request/ Response | API Invoker | +| | Notify_Onboarding_Completion | Subscribe/Notify | API Invoker | +| | Update_API_Invoker_Details | Request/Response | API Invoker | +| | Notify_Update_Completion | Subscribe/Notify | API Invoker | +| CAPIF_Security_API | Obtain_Security_Method | Request/ Response | API Invoker | +| | Obtain_Authorization | Request/ Response | API Invoker | +| | Obtain_API_Invoker_Info | Request/ Response | API exposing function | +| | Revoke_Authorization | Request/ Response | API exposing function | +| CAPIF_Monitoring_API | Event operations (NOTE) | (NOTE) | API Management Function | +| CAPIF_Logging_API_Invocation_API | Log_API_Invocation | Request/ Response | API exposing function | +| CAPIF_Auditing_API | Query_API_Invocation_Log | Request/ Response | API management function | +| CAPIF_Access_Control_Policy_API | Obtain_Access_Control_Policy | Request/Response | API Exposing Function | +| CAPIF_API_Provider_Management_API | Register_API_Provider | Request/Response | API Management Function | +| | Update_API_Provider | Request/Response | API Management Function | +| | Deregister_API_Provider | Request/Response | API Management Function | +| CAPIF_Routing_Info_API | Obtain_Routing_Info | Request/Response | API exposing function | +| NOTE: The service operations of CAPIF Events API are reused by the CAPIF_Discover_Service_API, CAPIF_Publish_Service_API and CAPIF_Monitoring_API for events related services. | | | | + +Table 5.1-2 summarizes the corresponding APIs defined in this specification. + +**Table 5.1-2: API Descriptions** + +| Service Name | Clause | Description | OpenAPI Specification File | apiName | Annex | +|--------------|--------|-------------|----------------------------|---------|-------| +|--------------|--------|-------------|----------------------------|---------|-------| + +| CAPIF_Discover_Service_API | 8.1 | CAPIF API discovery service | TS29222_CAPIF_Discover_Service_API.yaml | service-apis | A.2 | +|-----------------------------------|------|-------------------------------------------|------------------------------------------------|-------------------------|------| +| CAPIF_Publish_Service_API | 8.2 | CAPIF API Publish Service | TS29222_CAPIF_Publish_Service_API.yaml | published-apis | A.3 | +| CAPIF_Events_API | 8.3 | CAPIF event service | TS29222_CAPIF_Events_API.yaml | capif-events | A.4 | +| CAPIF_API_Invoker_Management_API | 8.4 | CAPIF API Invoker Management Service | TS29222_CAPIF_API_Invoker_Management_API.yaml | api-invoker-management | A.5 | +| CAPIF_Security_API | 8.5 | CAPIF Security Service | TS29222_CAPIF_Security_API.yaml | capif-security | A.6 | +| CAPIF_Access_Control_Policy_API | 8.6 | CAPIF Access Control Policy API Service | TS29222_CAPIF_Access_Control_Policy_API.yaml | access-control-policy | A.7 | +| CAPIF_Logging_API_Invocation_API | 8.7 | CAPIF Logging API Invocation Service | TS29222_CAPIF_Logging_API_Invocation_API.yaml | api-invocation-logs | A.8 | +| CAPIF_Auditing_API | 8.8 | CAPIF Auditing API Service | TS29222_CAPIF_Auditing_API.yaml | logs | A.9 | +| CAPIF_API_Provider_Management_API | 8.9 | CAPIF API Provider Management API Service | TS29222_CAPIF_API_Provider_Management_API.yaml | api-provider-management | A.11 | +| CAPIF_Routing_Info_API | 8.10 | CAPIF Routing Information API Service | TS29222_CAPIF_Routing_Info_API.yaml | capif-routing-info | A.12 | + +## 5.2 CAPIF\_Discover\_Service\_API + +### 5.2.1 Service Description + +#### 5.2.1.1 Overview + +The CAPIF discover service APIs, as defined in 3GPP TS 23.222 [2], allow API invokers via CAPIF-1/1e reference points to discover service API available at the CAPIF core function, and allow CAPIF core function via CAPIF-6 and CAPIF-6e reference points to discover service API available at other CAPIF core function. + +### 5.2.2 Service Operations + +#### 5.2.2.1 Introduction + +The service operation defined for CAPIF\_Discover\_Service\_API is shown in table 5.2.2.1-1. + +**Table 5.2.2.1-1: Operations of the CAPIF\_Discover\_Service\_API** + +| Service operation name | Description | Initiated by | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------| +| Discover_Service_API | This service operation is used by an API invoker to discover service API available at the CAPIF core function. This service operation is also used by CAPIF core function to discover service APIs available at other CAPIF core function. | API invoker, CAPIF core function | + +## 5.2.2.2 Discover\_Service\_API + +### 5.2.2.2.1 General + +This service operation is used by: + +- an API invoker to discover service API available at the CAPIF core function; or +- a CAPIF core function to discover service API available at other CAPIF core function in interconnection scenario. + +### 5.2.2.2.2 Consumer discovering service API using Discover\_Service\_API service operation + +To discover service APIs available at the CAPIF core function, the consumer (e.g. API invoker) shall send an HTTP GET message with the API invoker Identifier or CAPIF core function Identifier and query parameters to the CAPIF core function as specified in clause 8.1.2.2.3.1. + +Upon receiving the above described HTTP GET message, the CAPIF core function shall: + +1. verify the identity of the consumer (e.g. API invoker) and check if the consumer is authorized to discover the service APIs; +2. if the consumer is authorized to discover the service APIs, the CAPIF core function shall: + - a. search the CAPIF core function (API registry) for APIs matching the query criteria; + - b. apply the discovery policy, if any, on the search results and filter the search results to obtain the list of service API description or the information of the CAPIF core function which is required to be contacted further for discovering the service APIs; and + - c. return the filtered search results or the information of the CAPIF core function in the response message. The shareableInformation for each of serviceAPIDescription is not provided in the filtered search results; + +NOTE: The {apiRoot} part of the URI structure (defined in clause 5.2.4 of 3GPP TS 29.122 [14]) for the discovered APIs can be constructed by the API invoker based on either the "domainName" attribute (which contains all the required information, e.g. FQDN or IP address, port, a deployment specific string in the form of a sequence of path segments) or the "interfaceDescriptions" attribute of the AefProfile data type. + +and + +3. if errors occur when processing the request, the CAPIF core function shall respond to the consumer with an appropriate error status code as defined in clause 8.1.5. + +## 5.3 CAPIF\_Publish\_Service\_API + +### 5.3.1 Service Description + +#### 5.3.1.1 Overview + +The CAPIF publish service APIs, as defined in 3GPP TS 23.222 [2], allow API publishing function via CAPIF-4 and CAPIF-4e reference points to publish and manage published service APIs at the CAPIF core function, and allow CAPIF core function via CAPIF-6 and CAPIF-6e reference points to publish and manage published service APIs at other CAPIF core function. + +NOTE: Functions from 3rd party API provider domain can also access this API with sufficient permissions. + +## 5.3.2 Service Operations + +### 5.3.2.1 Introduction + +The service operations defined for the CAPIF\_Publish\_Service API are shown in table 5.3.2.1-1. + +**Table 5.3.2.1-1: Operations of the CAPIF\_Publish\_Service\_API** + +| Service operation name | Description | Initiated by | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| Publish_Service_API | This service operation is used by an API publishing function to publish service APIs on the CAPIF core function. This service operation is also used by CAPIF core function to publish service APIs on other CAPIF core function. | API publishing function, CAPIF core function | +| Unpublish_Service_API | This service operation is used by an API publishing function to un-publish service APIs from the CAPIF core function. This service operation is also used by CAPIF core function to un-publish service APIs on other CAPIF core function. | API publishing function, CAPIF core function | +| Get_Service_API | This service operation is used by an API publishing function to retrieve service APIs from the CAPIF core function. This service operation is also used by CAPIF core function to retrieve service APIs on other CAPIF core function. | API publishing function, CAPIF core function | +| Update_Service_API | This service operation is used by an API publishing function to update published service APIs on the CAPIF core function. This service operation is also used by CAPIF core function to update published service APIs on other CAPIF core function. | API publishing function, CAPIF core function | + +### 5.3.2.2 Publish\_Service\_API + +#### 5.3.2.2.1 General + +This service operation is used by: + +- an API publishing function to publish service APIs on the CAPIF core function; or +- a CAPIF core function to publish service APIs on other CAPIF core function in interconnection scenario. + +#### 5.3.2.2.2 API publishing function publishing service APIs on CAPIF core function using Publish\_Service\_API service operation + +To publish service APIs at the CAPIF core function, the API publishing function shall send an HTTP POST message to the CAPIF core function. The body of the HTTP POST message shall include API Information as specified in clause 8.2.2.2.3.1. + +Upon receiving the above described HTTP POST message, the CAPIF core function shall: + +1. verify the identity of the API publishing function and check if the API publishing function is authorized to publish service APIs; +2. if the API publishing function is authorized to publish service APIs, the CAPIF core function shall: + - a. verify the API Information present in the HTTP POST message and add the service APIs in the CAPIF core function (API registry); + - b. If topology hiding is enabled as per policy, the CAPIF core function shall: + - i. determine the service APIs which require topology hiding as per policy; + - ii. determine the API exposing function(s) responsible for the topology hiding for each service API which requires topology hiding; + +- iii. create a API topology hiding information for each service API which requires topology hiding by extracting the API identification information and the API exposing function(s) information from the service API information added to the CAPIF core function (API registry); + - iv. replace the API exposing function(s) information in the service API information added to the CAPIF core function (API registry) with the corresponding API exposing function(s) information responsible for the topology hiding for service API; + - v. send a notification message with the API topology hiding information to the API exposing function(s) which is responsible for the topology hiding for a service API and that has subscribed to the API\_TOPOLOGY HIDING\_CREATED event; and + - vi. store the API topology hiding information in the CAPIF core function; +- c. create a new resource using the service API information in the CAPIF core function (API registry) as specified in clause 8.2.2.1; + - d. send a notification message with the updated service API, to all API Invokers that subscribed to the Service API Update event; and + - e. return the CAPIF Resource URI in the response message; +- and +3. if errors occur when processing the request, the CAPIF core function shall respond to the API publishing function with an appropriate error status code as defined in clause 8.2.5. + +### 5.3.2.2.3 CAPIF core function publishing service APIs on other CAPIF core function using Publish\_Service\_API service operation + +To publish service APIs at other CAPIF core function, the requesting CAPIF core function shall send an HTTP POST message to the peer CAPIF core function. The body of the HTTP POST message shall include API Information as specified in clause 8.2.2.2.3.1. For service API publishing on CAPIF-6 reference point, the requesting CAPIF core function shall also include the published API path "pubApiPath" as specified in clause 8.2.4.2.2. The "pubApiPath" includes a list of CAPIF core function Identifiers within the same CAPIF provider domain, such list includes own CAPIF core function identifier of the requesting CAPIF core function and received CAPIF core function identifier(s) from other CAPIF core function. + +If the requesting CAPIF core function knows the peer CAPIF core function identifier, it shall not send the HTTP POST message to the peer CAPIF core function if the peer CAPIF core function identifier is included in the published API path. + +Upon receiving the above described HTTP POST message, the peer CAPIF core function shall: + +1. verify the identity of the requesting CAPIF core function in the URI and check if the requesting CAPIF core function is authorized to publish service APIs; + 2. if the requesting CAPIF core function is authorized to publish service APIs, the peer CAPIF core function shall check if own CAPIF core function identifier is within the published API path (if received). If it is not within the path, the peer CAPIF core function shall add its own identifier in the path; otherwise reject the HTTP POST request and skip step 3; + 3. then the peer CAPIF core function shall: + - a. verify the rest API Information present in the HTTP POST message and add the service APIs in the peer CAPIF core function (API registry); + - b. create a new resource as specified in clause 8.2.2.1; + - c. send a notification message with the updated service API, to all API Invokers that subscribed to the Service API Update event; and + - d. return the CAPIF Resource URI in the response message; +- and + +4. if errors occur when processing the request, the peer CAPIF core function shall respond to the peer CAPIF core function with an appropriate error status code as defined in clause 8.2.5. + +### 5.3.2.3 Unpublish\_Service\_API + +#### 5.3.2.3.1 General + +This service operation is used by: + +- an API publishing function to un-publish service APIs from the CAPIF core function; or +- a CAPIF core function to un-publish service APIs on other CAPIF core function in interconnection scenario. + +#### 5.3.2.3.2 Consumer un-publishing service APIs from CAPIF core function using Unpublish\_Service\_API service operation + +To un-publish service APIs from the CAPIF core function, the consumer (e.g. API publishing function) shall send an HTTP DELETE message using the CAPIF Resource URI received during the publish operation to the CAPIF core function as specified in clause 8.2.2.3.3.3. + +Upon receiving the above described HTTP DELETE message, the CAPIF core function shall + +1. verify the identity of the consumer (e.g. API publishing function) and check if the consumer is authorized to un-publish service APIs; +2. if the consumer is authorized to un-publish service APIs, the CAPIF core function shall: + - a. delete the resource pointed by the CAPIF Resource URI; + - b. delete the relevant service APIs from the CAPIF core function (API registry); + - c. If topology hiding is enabled as per policy, the CAPIF core function shall: + - i. determine the API topology hiding information associated with the service API and delete the corresponding API topology hiding information in the CAPIF core function; and + - ii. send a notification message with the deleted API topology hiding information to the corresponding API exposing function(s) which were responsible for the topology hiding of the service API and that subscribed to the API\_TOPOLOGY HIDING\_REVOKED event; and + - d. send a notification message with the deleted service API, to all API Invokers that subscribed to the Service API Update event; + +and + +3. if errors occur when processing the request, the CAPIF core function shall respond to the consumer with an appropriate error status code as defined in clause 8.2.5. + +### 5.3.2.4 Get\_Service\_API + +#### 5.3.2.4.1 General + +This service operation is used by: + +- an API publishing function to retrieve service APIs from the CAPIF core function; or +- a CAPIF core function to retrieve service APIs from other CAPIF core function in interconnection scenario. + +#### 5.3.2.4.2 Consumer retrieving service APIs from CAPIF core function using Get\_Service\_API service operation + +To retrieve information about the published service APIs from the CAPIF core function, the consumer (e.g. API publishing function) shall send an HTTP GET message to the CAPIF core function. For retrieving the entire list of + +service APIs, the HTTP GET message shall be sent to the collection of service APIs resource representation URI as specified in clause 8.2.2.3.3.2. For retrieving a specific service API, the HTTP GET message shall be sent to that service API's resource representation URI as described in clause 8.2.2.3.3.1. + +Upon receiving the above described HTTP GET message, the CAPIF core function shall: + +1. verify the identity of the consumer (e.g. API publishing function) and check if the consumer is authorized to retrieve information about the published service APIs; +2. if the consumer is authorized to retrieve information about the published service APIs, the CAPIF core function shall: + - a. respond with the requested API Information;and +3. if errors occur when processing the request, the CAPIF core function shall respond to the consumer with an appropriate error status code as defined in clause 8.2.5. + +### 5.3.2.5 Update\_Service\_API + +#### 5.3.2.5.1 General + +This service operation is used by: + +- an API publishing function to update published service APIs on the CAPIF core function; or +- a CAPIF core function to update published service APIs on other CAPIF core function in interconnection scenario. + +#### 5.3.2.5.2 Consumer updating published service APIs on CAPIF core function using Update\_Service\_API service operation + +To update information of published service APIs, the consumer (e.g. API publishing function) shall send an HTTP PUT message to that service API's resource representation URI in the CAPIF core function. The body of the HTTP PUT message shall include updated API Information as specified in clause 8.2.2.3.3.2; otherwise, if the "PatchUpdate" feature defined in clause 8.2.6 is supported, the consumer (e.g. API publishing function) may send an HTTP PATCH request message to the concerned service API resource URI in the CAPIF core function. The body of the HTTP PATCH request message shall include the requested modifications as specified in clause 8.2.2.3.3.4. + +Upon receiving the above described HTTP PUT or PATCH request message, the CAPIF core function shall: + +1. verify the identity of the consumer (e.g. API publishing function) and check if the consumer is authorized to update information of published service APIs; +2. if the consumer is authorized to update information of published service APIs, the CAPIF core function shall: + - a. verify the API Information present in the HTTP PUT or PATCH request message and replace/modify the service APIs in the CAPIF core function (API registry); + - b. if topology hiding is enabled as per policy, the CAPIF core function shall: + - i. if the service API being updated has a corresponding API topology hiding information in the CAPIF core function, then update the API topology hiding information with any updated API exposing function(s) information from the service API information replaced at the CAPIF core function (API registry); + - ii. replace/modify the API exposing function(s) information in the service API information added to the CAPIF core function (API registry) with the corresponding API exposing function(s) information responsible for the topology hiding for service API; + - iii. send a notification message with the API topology hiding information to the API exposing function(s) which is responsible for the topology hiding for a service API and that has subscribed to the API\_TOPOLOGY HIDING\_CREATED event; and + +- iv. update the API topology hiding information in the CAPIF core function; + - c. replace/modify the existing resource accordingly using the updated service API information in the CAPIF core function (API registry); and + - d. send a notification message with the updated service API, to all API Invokers that subscribed to the Service API Update event; +- and +- 3. if errors occur when processing the request, the CAPIF core function shall respond to the consumer with an appropriate error status code as defined in clause 8.2.5. + +## 5.4 CAPIF\_Events\_API + +### 5.4.1 Service Description + +#### 5.4.1.1 Overview + +The CAPIF events APIs, as defined in 3GPP TS 23.222 [2], allow an API invoker via CAPIF-1/1e reference points, API exposure function via CAPIF-3/3e reference points, API publishing function via CAPIF-4/4e reference points and API management function via CAPIF-5/5e reference points to subscribe to and unsubscribe from CAPIF events and to receive notifications from CAPIF core function. + +NOTE: The functional elements listed above are referred to as Subscriber in the service operations described in the clauses below. + +### 5.4.2 Service Operations + +#### 5.4.2.1 Introduction + +The service operations defined for the CAPIF\_Events\_API are shown in table 5.4.2.1-1. + +**Table 5.4.2.1-1: Operations of the CAPIF\_Events\_API** + +| Service operation name | Description | Initiated by | +|---------------------------|----------------------------------------------------------------------------------------------|---------------------| +| Subscribe_Event | This service operation is used by a Subscriber to subscribe to CAPIF events. | Subscriber | +| Unsubscribe_Event | This service operation is used by a Subscriber to unsubscribe from CAPIF events | Subscriber | +| Notify_Event | This service operation is used by CAPIF core function to send a notification to a Subscriber | CAPIF core function | +| Update_Event_Subscription | This service operation is used by a Subscriber to update the subscription to CAPIF events | Subscriber | + +#### 5.4.2.2 Subscribe\_Event + +##### 5.4.2.2.1 General + +This service operation is used by a Subscriber to subscribe to CAPIF events. + +##### 5.4.2.2.2 Subscribing to CAPIF events using Subscribe\_Event service operation + +To subscribe to CAPIF events, the Subscriber shall send an HTTP POST message to the CAPIF core function. The body of the HTTP POST message shall include Subscriber's Identifier, Event Type and a Notification Destination URI as specified in clause 8.3.2.2.3.1. + +For all events included in the HTTP POST message, if the Enhanced\_event\_report feature is supported, the Subscriber may include an event report requirement in the "eventReq" attribute including: + +- event notification method (periodic, one time, on event detection) in the "notifMethod" attribute; +- maximum Number of Reports in the "maxReportNbr" attribute; +- monitoring duration in the "monDur" attribute; +- repetition period for periodic reporting in the "repPeriod" attribute; and/or +- immediate reporting indication in the "immRep" attribute. + +If the Enhanced\_event\_report feature is supported, the Subscriber may also include an event filter in the "eventFilters" attribute. The "eventFilters" attribute shall include: + +- if the event is SERVICE\_API\_AVAILABLE, SERVICE\_API\_UNAVAILABLE or SERVICE\_API\_UPDATE, the API IDs in the "apiIds" attribute; +- if the event is API\_INVOKER\_ONBOARDED or API\_INVOKER\_OFFBOARDED or API\_INVOKER\_UPDATED, the API invoker IDs in the "apiInvokerIds" attribute; +- if the event is ACCESS\_CONTROL\_POLICY\_UPDATE, the API invoker IDs in the "apiInvokerIds" attribute and/or API identifications in the "apiIds" attribute; and/or +- if the event is SERVICE\_API\_INVOCATION\_SUCCESS or SERVICE\_API\_INVOCATION\_FAILURE, the API invoker IDs in the "apiInvokerIds" attribute, AEF identifiers in the "aefIds" attribute and/or API IDs in the "apiIds" attribute. + +Upon receiving the above described HTTP POST message, the CAPIF core function shall: + +1. verify the identity of the Subscriber and check if the Subscriber is authorized to subscribe to the CAPIF events mentioned in the HTTP POST message; +2. if the Subscriber is authorized to subscribe to the CAPIF events, the CAPIF core function shall: + - a. create a new resource as specified in clause 8.3.2.1; and + - b. return the CAPIF Resource URI in the response message;and +3. if errors occur when processing the request, the CAPIF core function shall respond to the Subscriber with an appropriate error status code as defined in clause 8.3.5. + +### 5.4.2.3 Unsubscribe\_Event + +#### 5.4.2.3.1 General + +This service operation is used by a Subscriber to un-subscribe from CAPIF events. + +#### 5.4.2.3.2 Unsubscribing from CAPIF events using Unsubscribe\_Event service operation + +To unsubscribe from CAPIF events, the Subscriber shall send an HTTP DELETE message to the resource representing the event in the CAPIF core function as specified in clause 8.3.2.3.1.1. + +Upon receiving the HTTP DELETE message, the CAPIF core function shall: + +1. verify the identity of the Unsubscribing functional entity and check if the Unsubscribing functional entity is authorized to Unsubscribe from the CAPIF event associated with the CAPIF Resource URI; +2. if the Unsubscribing functional entity is authorized to unsubscribe from the CAPIF events, the CAPIF core function shall delete the resource pointed by the CAPIF Resource URI; and + +3. if errors occur when processing the request, the CAPIF core function shall respond to the Subscriber with an appropriate error status code as defined in clause 8.3.5. + +#### 5.4.2.4 Notify\_Event + +##### 5.4.2.4.1 General + +This service operation is used by CAPIF core function to send a notification to a Subscriber. + +##### 5.4.2.4.2 Notifying CAPIF events using Notify\_Event service operation + +To notify CAPIF events, the CAPIF core function shall send an HTTP POST message using the Notification Destination URI received in the subscription request. The body of the HTTP POST message shall include an Event Notification and CAPIF Resource URI. + +If the Enhanced\_event\_report feature is supported, the CAPIF core function may include an event detail in the "eventDetail" attribute. The "eventDetail" attribute shall include: + +- if the event is SERVICE\_API\_AVAILABLE or SERVICE\_API\_UNAVAILABLE, the API IDs in the "apiIds" attribute and, if the "ApiStatusMonitoring" feature is supported, additionally, the service API descriptions in the "serviceAPIDescriptions" attribute; +- if the event is SERVICE\_API\_UPDATE, the API descriptions in the "serviceAPIDescriptions" attribute; +- if the event is API\_INVOKER\_ONBOARDED or API\_INVOKER\_OFFBOARDED or API\_INVOKER\_UPDATED, the API invoker IDs in the "apiInvokerIds" attribute; +- if the event is ACCESS\_CONTROL\_POLICY\_UPDATE, the access control policy information in the "accCtrlPolList" attribute; +- if the event is SERVICE\_API\_INVOCATION\_SUCCESS or SERVICE\_API\_INVOCATION\_FAILURE, the API invocation logs in the "invocationLogs" attribute; or +- if the event is API\_TOPOLOGY HIDING\_CREATED or API\_TOPOLOGY HIDING\_REVOKED, the API topology hiding information in the "apiTopoHide" attribute. + +Upon receiving the HTTP POST message, the Subscriber shall process the Event Notification. + +#### 5.4.2.5 Update\_Event\_Subscription + +##### 5.4.2.5.1 General + +This service operation is used by a Subscriber to update the subscription to CAPIF events. + +##### 5.4.2.5.2 Update Subscription to CAPIF events using Update\_Event\_Subscription service operation + +To update the subscription details to CAPIF events, the Subscriber shall send an HTTP PUT/PATCH request message to the CAPIF core function. The body of the HTTP PUT request message shall include the EventSubscription data structure specified in clause 8.3.4.2.2. The body of the HTTP PATCH request message shall include the EventSubscriptionPatch data structure specified in clause 8.3.4.2.8. + +Upon receiving the HTTP PUT or PATCH message described above, the CAPIF core function shall: + +1. verify the identity of the Subscriber and check if the Subscriber is authorized to update/modify the subscription; +2. update the resource and respond to the CAPIF core function with either a "200 OK" status code with the response body containing an updated representation of the resource within the EventSubscription data structure, or a "204 No Content" status code. + +## 5.5 CAPIF\_API\_Invoker\_Management\_API + +### 5.5.1 Service Description + +#### 5.5.1.1 Overview + +The CAPIF API invoker management APIs, as defined in 3GPP TS 23.222 [2], allow API invokers via CAPIF-1/1e reference points to on-board and off-board itself as a recognized user of the CAPIF or update the API invoker's details on the CAPIF core function. + +### 5.5.2 Service Operations + +#### 5.5.2.1 Introduction + +The service operations defined for the CAPIF API Invoker Management API are shown in table 5.5.2.1-1. + +**Table 5.5.2.1-1: Operations of the CAPIF\_API\_Invoker\_Management\_API** + +| Service operation name | Description | Initiated by | +|------------------------------|---------------------------------------------------------------------------------------------------------------|---------------------| +| Onboard_API_Invoker | This service operation is used by an API invoker to on-board itself as a recognized user of CAPIF | API invoker | +| Offboard_API_Invoker | This service operation is used by an API invoker to off-board itself as a recognized user of CAPIF | API invoker | +| Notify_Onboarding_Completion | This service operation is used by CAPIF core function to send an on-boarding notification to the API invoker. | CAPIF core function | +| Update_API_Invoker_Details | This service operation is used by an API invoker to update API invoker's details in the CAPIF core function. | API Invoker | +| Notify_Update_Completion | This service operation is used by CAPIF core function to send an update notification to the API invoker | CAPIF core function | + +#### 5.5.2.2 Onboard\_API\_Invoker + +##### 5.5.2.2.1 General + +This service operation is used by an API invoker to on-board itself as a recognized user of CAPIF + +##### 5.5.2.2.2 API invoker on-boarding itself as a recognized user of CAPIF using Onboard\_API\_Invoker service operation + +To on-board itself as a recognized user of the CAPIF, the API invoker shall send an HTTP POST message to the CAPIF core function. The body of the HTTP POST message shall include API invoker Enrolment Details, API List and a Notification Destination URI for on-boarding notification as specified in clause 8.4.2.2.3.1. + +Upon receiving the above described HTTP POST message, the CAPIF core function shall check if it can determine authorization of the request and on-board the API invoker automatically. If the CAPIF core function: + +1. can determine authorization of the request and on-board the API invoker automatically, the CAPIF core function: + - a. shall process the API invoker Enrolment Details and the API List received in the HTTP POST message and determine if the request sent by the API invoker is authorized or not; and + - b. if the API invoker's request is authorized, the CAPIF core function shall: + - i. create the API invoker Profile consisting of an API invoker Identifier, Authentication Information, Authorization Information and CAPIF Identity Information; + +- ii. verify the API List present in the HTTP POST message and create a API List of APIs the API invoker is allowed to access; + - iii. create a new resource as defined in clause 8.4.2.1; + - iv. return the API invoker Profile, API List of APIs the API invoker is allowed to access and the CAPIF Resource URI in the response message. + - 2. cannot determine authorization of the request to on-board the API invoker automatically, the CAPIF core function: + - a. shall acknowledge the receipt of the on-boarding request to the API invoker. + - b. shall request the CAPIF administrator to validate the on-boarding request or the API management to validate the on-boarding request by sharing the API invoker Enrolment Details and the API List received in the HTTP POST message; + - c. on receiving confirmation of successful validation of the on-boarding request from the CAPIF administrator or the API management, the CAPIF core function shall: + - i. create the API invoker Profile consisting of an API invoker Identifier, Authentication Information, Authorization Information and CAPIF Identity Information; + - ii. create a new resource as defined in clause 8.4.3; and + - iii. deliver the API invoker Profile, API List of APIs the API invoker is allowed to access and the CAPIF Resource URI to the API invoker in a notification; +- and +- 3. if errors occur when processing the request, the CAPIF core function shall respond to the API invoker with an appropriate error status code as defined in clause 8.4.5. + +NOTE 1: How the CAPIF core function determines that the CAPIF core function can process the request and on-board the API invoker automatically is out-of-scope of this specification. + +NOTE 2: How the CAPIF core function determines that the API invoker's request to on-board is authorized is specified in 3GPP TS 33.122 [16]. + +NOTE 3: Interactions between the CAPIF core function and the CAPIF administrator or the API management is out-of-scope of this specification. + +NOTE 4: The onboarding credential received by the API invoker from the service provider as specified in 3GPP TS 33.122 [16] is included in the Authorization header field of the HTTP request message as described in IETF RFC 9110 [5]. + +NOTE 5: After the onboarding operation is completed the API Invoker no longer needs to maintain the Notification Destination URI and may delete it. + +### 5.5.2.3 Offboard\_API\_Invoker + +#### 5.5.2.3.1 General + +This service operation is used by an API invoker to stop being as a recognized user of CAPIF + +#### 5.5.2.3.2 API invoker off-boarding itself as a recognized user of CAPIF using Offboard\_API\_Invoker service operation + +To off-board itself as a recognized user of the CAPIF, the API invoker shall send an HTTP DELETE message to its resource representation in the CAPIF core function as specified in clause 8.4.2.3.3.1. + +Upon receiving the HTTP DELETE message, the CAPIF core function shall: + +- 1. determine if the request sent by the API invoker is authorized or not; + +2. if the API invoker's request is authorized, the CAPIF core function shall: + - a. delete the resource representation pointed by the CAPIF Resource Identifier; and + - b. delete the related API invoker profile; +- and +3. if errors occur when processing the request, the CAPIF core function shall respond to the API invoker with an appropriate error status code as defined in clause 8.4.5. + +#### 5.5.2.4 Notify\_Onboarding\_Completion + +##### 5.5.2.4.1 General + +This service operation is used by the CAPIF core function to send a notification about the completion of the Onboarding operation to the API Invoker. + +##### 5.5.2.4.2 Notifying Onboarding completion using Notify\_Onboarding\_Completion service operation + +When the CAPIF core function cannot immediately authorize the API invoker that issued an Onboarding request (see clause 5.5.2.2.2) it will send a response acknowledging the request and begin processing it. After completion, the CAPIF core function shall send an HTTP POST message using the Notification Destination URI received in the Onboarding request. The body of the HTTP POST message shall include the API Invoker Profile, API List of the APIs the API invoker is allowed to access and the CAPIF Resource URI. + +Upon receiving the HTTP POST message, the API invoker shall process the message in the same manner it would have processed an immediate response to the Onboarding request, and respond to the HTTP POST message with an acknowledgement and no body. + +#### 5.5.2.5 Update\_API\_Invoker\_Details + +##### 5.5.2.5.1 General + +This service operation is used by an API invoker to update the API invoker's profile details on the CAPIF core function. + +##### 5.5.2.5.2 API invoker updating its details on CAPIF using Update\_API\_Invoker\_Details service operation + +To update the API invoker's profile details on the CAPIF core function, the API invoker shall send a HTTP PUT message to the CAPIF core function to its resource representation, requesting to replace all properties in the existing resource, addressed by the URI received in the response to the request that has created the API invoker profile resource. The properties "apiInvokerId" and "onboardingInformation" shall remain unchanged from the previously provided values. The body of the HTTP PUT message shall include the APIInvokerEnrolmentDetails data structure with API invoker identity information, API invoker details that need to be updated and a Notification Destination URI for update notification as specified in clause 8.4.2.3.3.2. API invoker details may include API invoker information and API List. Otherwise, if the "PatchUpdate" feature defined in clause 8.4.6 is supported, the consumer (e.g. API invoker function) may send an HTTP PATCH request message to the concerned service API resource URI in the CAPIF core function to modify the API invoker's profile. The body of the HTTP PATCH request message shall include the APIInvokerEnrolmentDetailsPatch data structure. + +Upon receiving the above described HTTP PUT or PATCH request message: + +1. if the CAPIF core function decides to update the API list of the API invoker without validation by CAPIF administrator, then the CAPIF core function: + - a. shall determine if the request in the HTTP PUT or PATCH request message by the API invoker is authorized or not; + +- b. verify that the "apiInvokerId" and "onboardingInformation" properties are same as in API invoker resource on CAPIF core function; + - c. if the API invoker's request is authorized and the properties "apiInvokerId" and "onboardingInformation" match, the CAPIF core function shall: + - i. if the request contains an API list: + - create a list of APIs the API invoker is allowed to access; and + - update the resource identified by the CAPIF Resource URI of the API invoker's HTTP PUT or PATCH request with the updated information in the request and the API list created in step A; + - ii. if the request does not contain an API list, update the resource identified by the CAPIF Resource URI of the API invoker's HTTP PUT or PATCH request with the updated information in the request; and + - iii. return the updated API invoker details; +2. otherwise, the CAPIF core function: +- a. shall acknowledge the receipt of the update API invoker details request to the API invoker; + - b. verify that the "apiInvokerId" and "onboardingInformation" properties are same as in API invoker resource on CAPIF core function; + - c. if the properties "apiInvokerId" and "onboardingInformation" match, then shall request the CAPIF administrator to validate the request or the API management to validate the request by sharing the API invoker identity information and the updated information received in the HTTP PUT message or PATCH request; + - d. on receiving confirmation of successful validation of the request from the CAPIF administrator or the API management, the CAPIF core function shall: + - i. update the resource identified by the CAPIF Resource URI of the API invoker's HTTP PUT or PATCH request, with validated information; and + - ii. return the updated API invoker details; + +and + +- 3. if errors occur when processing the request, the CAPIF core function shall respond to the API invoker with an appropriate error status code as defined in clause 8.4.5. + +NOTE 1: How the CAPIF core function determines that the CAPIF core function can process the request and update the API list of the API invoker automatically is out-of-scope of this specification. + +NOTE 2: Interactions between the CAPIF core function and the CAPIF administrator or the API management is out-of-scope of this specification. + +NOTE 3: After the operation is completed the API Invoker no longer needs to maintain the Notification Destination URI and may delete it. + +## 5.5.2.6 Notify\_Update\_Completion + +### 5.5.2.6.1 General + +This service operation is used by the CAPIF core function to send a notification about the completion of the update of API invoker's details. + +### 5.5.2.6.2 Notifying API invoker update completion using Notify\_Update\_Completion service operation + +When the CAPIF core function cannot immediately grant the update request (see clause 5.5.2.5.2) it will send a response acknowledging the request and begin processing it. After completion, the CAPIF core function shall send an + +HTTP POST message using the Notification Destination URI received in the update details request. The body of the HTTP POST message shall include the updated API Invoker details. + +Upon receiving the HTTP POST message, the API invoker shall process the message in the same manner it would have processed an immediate response to the update the details of the API invoker request, and respond to the HTTP POST message with HTTP response 204 No content. + +## 5.6 CAPIF\_Security\_API + +### 5.6.1 Service Description + +#### 5.6.1.1 Overview + +The CAPIF security APIs, as defined in 3GPP TS 23.222 [2], allow: + +- API invokers via CAPIF-1/1e reference points to (re-)negotiate the service security method and obtain authorization for invoking service APIs; and +- API exposing function via CAPIF-3/3e reference points to obtain authentication information of the API invoker for authentication of the API invoker and revoke the authorization for service APIs. + +### 5.6.2 Service Operations + +#### 5.6.2.1 Introduction + +The service operations defined for CAPIF\_Security\_API are shown in table 5.6.2.1-1. + +**Table 5.6.2.1-1: Operations of the CAPIF\_Security\_API** + +| Service operation name | Description | Initiated by | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Obtain_Security_Method | This service operation is used by an API invoker to negotiate and obtain service API security methods from the CAPIF core function. This information is used by the API invoker for service API invocations at the API Exposing Function. | API invoker | +| Obtain_Authorization | This service operation is used by an API invoker to obtain authorization to access service APIs. | API invoker | +| Obtain_API_Invoker_Info | This service operation is used by an API exposing function to obtain the authentication or authorization information related to an API invoker. | API exposing function | +| Revoke_Authorization | This service operation is used by an API exposing function to invalidate the authorization of an API invoker. | API exposing function | + +Security information is generated when requested by an API invoker, and is stored in the CAPIF Core function. The information can be accessed via a resource representation URI using the API invoker ID as described in clause 8.5.2.3. The URI is provided to the API invoker in the HTTP response to the creation request (via the Obtain\_Security\_Method service operation name). + +Refer to clause 9.1.2a.2 for details about verifying that the API Exposing function has the ability to authorize API invokers prior to invoking service APIs. + +#### 5.6.2.2 Obtain\_Security\_Method + +##### 5.6.2.2.1 General + +This service operation is used by an API invoker to negotiate and obtain service API security method from the CAPIF core function. The information received by API invoker shall be used for authentication with the API exposing function. + +### 5.6.2.2.2 Request service API security method from CAPIF using Obtain\_Security\_Method service operation + +To negotiate and obtain service API security method information from the CAPIF core function, the API invoker shall send an HTTP PUT message to the CAPIF core function. The body of the HTTP PUT message shall include Security Method Request and a Notification Destination URI for security related notifications. The Security Method Request from the API invoker contains the unique interface details of the service APIs and may contain a preferred method for each unique service API interface as specified in clause 8.5.2.3.3.3. + +Upon receiving the above described HTTP PUT message, the CAPIF core function shall: + +1. determine the security method for each service API interface as specified in 3GPP TS 33.122 [16]; +2. store the Notification Destination URI for security related notification; +3. create a new resource as defined in clause 8.5.2.1; +4. return the security method information and the CAPIF Resource URI in the response message; and +5. if errors occur when processing the request, the CAPIF core function shall respond to the API invoker with an appropriate error status code as defined in clause 8.5.5. + +### 5.6.2.3 Obtain\_Authorization + +#### 5.6.2.3.1 General + +This service operation is used by an API invoker to negotiate and obtain authorization information from the CAPIF core function. The information received by API invoker shall be used for authorization to invoke service APIs exposed by the API exposing function. + +#### 5.6.2.3.2 Obtain authorization using Obtain\_Authorization service operation + +To obtain authorization information from the CAPIF core function to invoke service APIs, the API invoker shall perform the functions of the resource owner, client and redirection endpoints as described in clause 6.5.2.3 of 3GPP TS 33.122 [16]. + +The API invoker shall send a POST request to the "Token Endpoint", as described in IETF RFC 6749 [23], clause 3.2. The "Token Endpoint" URI shall be: + +`{apiRoot}/capif-security/v1/securities/{securityId}/token` + +where {securityId} is the API invoker identifier and represents the "Individual trusted API invoker" resource created during obtain security method, as described in clause 5.6.2.2. + +The body of the HTTP POST request shall indicate that the required OAuth2 grant must be of type "client\_credentials" or "authorization\_code". The grant type shall be set as "authorization\_code" when API invoker uses authorization code flow. **The grant type shall be set as "client\_credentials" when API invoker uses client credentials flow.** The "scope" parameter (if present) shall include a list of AEF identifiers and its associated API names the API invoker is trying to access (i.e., the API invoker expected scope). If the request is sent for authorization code flow, the request shall include the authorization code obtained through interaction with the "Authorization Endpoint" as specified in clause 5.6.2.3.3. If the request is sent for client credentials flow in RNAA scenarios, the request may include the resource owner ID (i.e. the GPSI as defined in clause 6.5.3.1 of TS 33.122 [16]). + +**Editor's Note: It is FFS to clarify the scenarios where client credential may be used for RNAA use cases.** + +The API invoker may use HTTP Basic authentication towards this endpoint, using the API invoker identifier as "username" and the onboarding secret as "password". Such username and password may be included in the header or body of the HTTP POST request. + +On success, "200 OK" shall be returned. The content of the POST response shall contain the requested access token, the token type and the expiration time for the token. The access token shall be a JSON Web Token (JWT) as specified in IETF RFC 7519 [24]. The access token returned by the CAPIF core function shall include the claims encoded as a + +JSON object as specified in clause 8.5.4.2.8 and then digitally signed using JWS as specified in IETF RFC 7515 [25] and in Annex C.1 of 3GPP TS 33.122 [16]. + +The digitally signed access token shall be converted to the JWS Compact Serialization encoding as a string as specified in clause 7.1 of IETF RFC 7515 [25]. + +If the access token request fails at the CAPIF core function, the CAPIF core function shall return "400 Bad Request" status code, including a JSON object in the response content, that includes details about the specific error that occurred. + +### 5.6.2.3.3 Obtain authorization code using Obtain\_Authorization service operation + +This service operation is used by the API invoker to obtain the authorization code from the CAPIF core function. + +If the API invoker uses the authorization code flow, the API invoker shall send a GET request to the "Authorization Endpoint", as described in IETF RFC 6749 [23], clause 4.1. The "Authorization Endpoint" URI shall be: + +`{apiRoot}/capif-security/v1/securities/{securityId}/code` + +where {securityId} is the API invoker identifier and represents the "Individual trusted API invoker" resource created during obtain security method, as described in clause 5.6.2.2. + +As per clause 4.1 of IETF RFC 6749 [23], the HTTP GET request shall indicate the response type as type "code" and other required parameters within query parameters. The "resource\_owner\_id" parameter shall include the resource owner ID. + +The API invoker may use HTTP Basic authentication towards this endpoint, using the API invoker identifier as "username" and the onboarding secret as "password". Such username and password may be included in the header or body of the HTTP GET request. + +On success, "302 Found" shall be returned. The payload body of the GET response shall contain the requested authorization code, as described in clause 4.1 IETF RFC 6749 [23]. + +**Editor's Note:** Whether this Obtain\_Authorization\_Code operation is needed or not and the corresponding details are FFS. + +### 5.6.2.4 Obtain\_API\_Invoker\_Info + +#### 5.6.2.4.1 General + +This service operation is used by an API exposing function to obtain the security information of API Invokers to be able to authenticate them and authorize each service API invocation by them. + +#### 5.6.2.4.2 Obtain API invoker's security information using Obtain\_API\_Invoker\_Info service operation + +To obtain authentication or authorization information from the CAPIF core function to authenticate or authorize an API invoker, the API exposing function shall send an HTTP GET message to that API invoker's resource representation URI in the CAPIF core function with an indication to request authentication and/or authorization information, as specified in clause 8.5.2.3.3.1. + +Upon receiving the above described HTTP GET message, the CAPIF core function shall: + +1. determine the security information of API invoker for all the service API interfaces of the API exposing function; +2. return the security information in the response message; and + +NOTE: Functions from 3rd party API provider domain can also access this service operation with sufficient permissions. + +3. if errors occur when processing the request, the CAPIF core function shall respond to the API invoker with an appropriate error status code as defined in clause 8.5.5. + +## 5.6.2.5 Revoke\_Authentication + +### 5.6.2.5.1 General + +This service operation is used by an API exposing function to invalidate the authorization of a specified API Invoker to invoke service APIs exposed by the calling API exposing function. + +### 5.6.2.5.2 Invalidate authorization using Revoke\_Authorization service operation + +To invalidate authorization of an API invoker for all service APIs, the API exposing function shall send an HTTP DELETE message to that API invoker's resource representation URI in the CAPIF core function using the API invoker ID as specified in clause 8.5.2.3.3.2. + +Upon receiving the HTTP DELETE message, the CAPIF core function shall delete the resource representation and shall notify the API invoker of the authorization invalidation using the Notification Destination URI received in the Obtain\_Security\_Method message. + +The CAPIF core function shall also invalidate the previously assigned access token when the authorization of all service APIs are revoked for the API invoker. + +To invalidate authorization of an API invoker for some service APIs, the API exposing function shall send an HTTP POST message to that API invoker's "delete" custom resource representation URI in the CAPIF core function with a list of the service APIs that should be revoked. + +Upon receiving the HTTP POST message, the CAPIF core function shall revoke the authorization of the API invoker for the indicated service APIs (e.g. it may update the list of unauthorized APIs locally); and shall notify the API invoker of the authorization invalidation using the Notification Destination URI received in the Obtain\_Security\_Method message. + +In both alternatives, the CAPIF core function shall acknowledge the HTTP request from the API exposing function. + +NOTE: Functions from 3rd party API provider domain can also access this service operation with sufficient permissions. + +## 5.7 CAPIF\_Monitoring\_API + +The CAPIF monitoring API as defined in 3GPP TS 23.222 [2], allow the API management function via CAPIF-5/5e reference points to monitor service API invocations and receive such monitoring events from the CAPIF core function. + +The CAPIF\_Monitoring\_API shall use the CAPIF\_Events\_API as described in clause 8.3 by setting the CAPIFEvent to one of the events as described in clause 8.3.4.3.3. + +## 5.8 CAPIF\_Logging\_API\_Invocation\_API + +### 5.8.1 Service Description + +#### 5.8.1.1 Overview + +The Logging API invocations APIs, as defined in 3GPP TS 23.222 [2], allow API exposing functions via CAPIF-3/3e reference points to log the information related to service API invocations on the CAPIF core function. + +NOTE: Functions from 3rd party API provider domain can also access this API with sufficient permissions. + +## 5.8.2 Service Operations + +### 5.8.2.1 Introduction + +**Table 5.8.2.1-1: Operations of the CAPIF\_Logging\_API\_Invocation\_API** + +| Service operation name | Description | Initiated by | +|------------------------|----------------------------------------------------------------------------------------------------------------------|-----------------------| +| Log_API_Invocation | This service operation is used by an API exposing function to log API invocation information on CAPIF core function. | API exposing function | + +### 5.8.2.2 Log\_API\_Invocation\_API + +#### 5.8.2.2.1 General + +This service operation is used by an API exposing function to log API invocation information on CAPIF core function. + +#### 5.8.2.2.2 Logging service API invocations using Log\_API\_Invocation service operation + +To log service API invocations at the CAPIF core function, the API exposing function shall send an HTTP POST message to the CAPIF core function. The body of the HTTP POST message shall include API exposing function identity information and API invocation log information as specified in clause 8.7.2.2.3.1. + +Upon receiving the above described HTTP POST message, the CAPIF core function shall: + +1. verify the identity of the API exposing function and check if the API exposing function is authorized to create service API invocation logs; +2. if the API exposing function is authorized to create service API invocation logs, the CAPIF core function shall: + - a. process the API invocation log information received in the HTTP POST message and store the API invocation log information in the API repository; + - b. create a new resource as defined in clause 8.7.2.1; and + - c. return the CAPIF Resource Identifier in the response message; + and +3. if errors occur when processing the request, the CAPIF core function shall respond to the API exposing function with an appropriate error status code as defined in clause 8.7.5. + +## 5.9 CAPIF\_Auditing\_API + +### 5.9.1 Service Description + +#### 5.9.1.1 Overview + +The Auditing API, as defined in 3GPP TS 23.222 [2], allows API management functions via CAPIF-5/5e reference points to query the log information stored on the CAPIF core function. + +NOTE: Functions from 3rd party API provider domain can also access this API with sufficient permissions. + +## 5.9.2 Service Operations + +### 5.9.2.1 Introduction + +**Table 5.9.2.1-1: Operations of the CAPIF\_Auditing\_API** + +| Service operation name | Description | Initiated by | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Query_Invocation_Logs | This service operation is used by an API management function to query API invocation information logs stored on CAPIF core function. | API management function | + +### 5.9.2.2 Query\_Invocation\_Logs\_API + +#### 5.9.2.2.1 General + +This service operation is used by an API management function to query API invocation information logs stored on CAPIF core function. + +#### 5.9.2.2.2 Query API invocation information logs using Query\_Invocation\_Logs service operation + +To query service API invocation logs at the CAPIF core function, the API management function shall send an HTTP GET message with the API management function identity information and optionally a set of log query parameters to the CAPIF core function as specified in clause 8.8.2.2.3.1. + +Upon receiving the above described HTTP GET message, the CAPIF core function shall: + +1. verify the identity of the API management function and check if the API management function is authorized to query the service API invocation logs; + 2. if the API management function is authorized to query the service API invocation logs, the CAPIF core function shall: + - a. search the API invocation logs for logs matching the log query parameters, if any; and + - b. return the search results in the response message; +- and +3. if errors occur when processing the request, the CAPIF core function shall respond to the API management function with an appropriate error status code as defined in clause 8.8.5. + +## 5.10 CAPIF\_Access\_Control\_Policy\_API + +### 5.10.1 Service Description + +#### 5.10.1.1 Overview + +The CAPIF access control policy APIs allow API exposing function via CAPIF-3/3e reference points to obtain the service API access policy from the CAPIF core function. + +NOTE: Functions from 3rd party API provider domain can also access this API with sufficient permissions. + +## 5.10.2 Service Operations + +### 5.10.2.1 Introduction + +**Table 5.3.2.1-1: Operations of the CAPIF\_Access\_Control\_Policy\_API** + +| Service operation name | Description | Initiated by | +|------------------------------|------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Obtain_Access_Control_Policy | This service operation is used by an API exposing function to obtain the access control policy from the CAPIF core function. | API exposing function | + +### 5.10.2.2 Obtain\_Access\_Control\_Policy + +#### 5.10.2.2.1 General + +This service operation is used by an API exposing function to obtain the access control policy from the CAPIF core function. + +#### 5.10.2.2.2 API exposing function obtaining access control policy from the CAPIF core function using Obtain\_Access\_Control\_Policy service operation + +To obtain the access control policy from the CAPIF core function, the API exposing function shall send an HTTP GET message to the CAPIF core function with the API exposing function Identifier and API identification. The GET message may include API invoker ID for retrieving access control policy of the requested API invoker as specified in clause 8.6.2.2.3.1. + +Upon receiving the above described HTTP GET message, the CAPIF core function shall: + +1. verify the identity of the API exposing function and check if the API exposing function is authorized to obtain the access control policy corresponding to the API identification; +2. if the API exposing function is authorized to obtain the access control policy, the CAPIF core function shall respond with the access control policy information corresponding to the API identification and API invoker ID (if present) in the HTTP GET message; and +3. if errors occur when processing the request, the CAPIF core function shall respond to the API exposing function with an appropriate error status code as defined in clause 8.6.5. + +## 5.10.3 Related Events + +The CAPIF\_Access\_Control\_Policy\_API supports the subscription and notification of the status of access control information via the CAPIF\_Events\_API. The related events are specified in clause 8.3.4.3.3. + +# 5.11 CAPIF\_API\_Provider\_Management\_API + +## 5.11.1 Service Description + +### 5.11.1.1 Overview + +The CAPIF API provider management APIs, as defined in 3GPP TS 23.222 [2], allow API management functions via CAPIF-5 and CAPIF-5e reference points to register, deregister and update registration information of API provider domain functions (API Exposing Function, API Publishing Function, API management Function) as a recognized API provider domain of the CAPIF domain. + +## 5.11.2 Service Operations + +### 5.11.2.1 Introduction + +The service operations defined for the CAPIF API Provider Management API are shown in table 5.11.2.1-1. + +**Table 5.11.2.1-1: Operations of the CAPIF\_API\_Provider\_Management\_API** + +| Service operation name | Description | Initiated by | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Register_API_Provider | This service operation is used by an API management function to register API provider domain functions as a recognized API provider domain of the CAPIF domain. | API Management Function | +| Update_API_Provider | This service operation is used by an API management function to update the API provider domain functions details in the CAPIF domain. | API Management Function | +| Deregister_API_Provider | This service operation is used by an API management function to deregister API provider domain functions as a recognized API provider domain of the CAPIF domain. | API Management Function | + +### 5.11.2.2 Register\_API\_Provider + +#### 5.11.2.2.1 General + +This service operation is used by an API management function to register API provider domain functions as a recognized API provider of CAPIF domain. + +#### 5.11.2.2.2 API provider domain functions registering as a recognized API provider domain function of CAPIF using Register\_API\_Provider service operation + +To register API provider domain as a recognized API provider of the CAPIF, the API management function shall send a HTTP POST message to the CAPIF core function. The body of the HTTP POST message shall include API provider Enrolment Details, consisting of details of all API provider domain functions and security information for CAPIF core function to validate the registration request. + +Upon receiving the above described HTTP POST message, the CAPIF core function validates the security information and determine if the request sent by API management function is authorized or not. If the API management function is authorized, CAPIF core function shall: + +- create the API provider domain profile consisting of API provider domain ID, API provider domain functions profiles as per the request. CAPIF core function shall assign the identities for the API provider domain functions; +- create a new resource as defined in clause 8.9.2.2.3.1; +- return the API provider domain profile, the CAPIF Resource URI in the response message and registration failure information specific to individual API provider domain functions; and +- if errors occur when processing the request, the CAPIF core function shall respond to the API management function with an appropriate error status code as defined in clause 8.9.5. + +### 5.11.2.3 Update\_API\_Provider + +#### 5.11.2.3.1 General + +This service operation is used by an API management function to update API provider domain function details on the CAPIF domain. + +### 5.11.2.3.2 API management function updating API provider domain function details on CAPIF using Update\_API\_Provider service operation + +To update the API provider domain profile and its individual functions details on CAPIF domain, the API management function shall send a HTTP PUT message to its resource representation in the CAPIF core function as specified in clause 8.9.2.3.3.1, requesting to replace all properties in the existing resource, addressed by the URI received in the response to the request that has created the API provider domain profile resource. The property "apiProviderDomainId", shall remain unchanged from the previously provided values. The body of the HTTP PUT message shall include the APIProviderEnrolmentDetails data structure that need to be updated. If the "PatchUpdate" feature defined in clause 8.9.6 is supported for modification of the API provider domain profile, the consumer (e.g. API publishing function) may send an HTTP PATCH request message to the concerned service API resource URI in the CAPIF core function. The body of the HTTP PATCH request message shall include the APIProviderEnrolmentDetailsPatch data structure. + +Upon receiving the described HTTP PUT or PATCH request message: + +1. the CAPIF core function shall process the updates received in the HTTP PUT or PATCH request message and determine if the request sent by API management function is authorized or not; + 2. verify that the "apiProviderDomainId" property is same as in the API provider domain resource on CAPIF Core Function; + 3. if the API management function is authorized and the property "apiProviderDomainId" matches, then the CAPIF core function shall: + - a. replace/modify the representation of the resource identified by the CAPIF Resource URI of the API management function's HTTP PUT or PATCH request with updated information in the request; + - b. update the individual API provider domain function profiles as per the request. CAPIF core function shall create new API provider domain function profiles along with assignment of identities, if the API provider domain functions profiles in the request do not exist in CAPIF; and + - c. return a "200 OK" status code with the updated API provider domain information, or a "204 No Content" status code; +- and +4. if errors occur when processing the request, the CAPIF core function shall respond to the API management function with an appropriate error status code as defined in clause 8.9.5. + +### 5.11.2.4 Deregister\_API\_Provider + +#### 5.11.2.4.1 General + +This service operation is used by an API management function to deregister the API provider domain function as a recognized API provider of the CAPIF domain. + +#### 5.11.2.4.2 API provider domain functions deregistering as a recognized API provider domain function of CAPIF using Deregister\_API\_Provider service operation + +To deregister API provider domain as a recognized API provider of the CAPIF domain, the API management function shall send an HTTP DELETE message to its resource representation in the CAPIF core function as specified in clause 8.9.2.3.3.2. + +Upon receiving the HTTP DELETE message, the CAPIF core function shall: + +1. determine if the request sent by the API management functions is authorized or not; +2. if the API management function's request is authorized, the CAPIF core function shall: + - a. delete the resource representation pointed by the CAPIF Resource Identifier; and + - b. delete the related API provider domain profile; + +and + +3. if errors occur when processing the request, the CAPIF core function shall respond to the API management function with an appropriate error status code as defined in clause 8.9.5. + +## 5.12 CAPIF\_Routing\_Info\_API + +### 5.12.1 Service Description + +#### 5.12.1.1 Overview + +The CAPIF routing info API allows an API exposing function via CAPIF-3/3e reference point to obtain the API routing information from the CAPIF core function. + +NOTE: Functions from 3rd party API provider domain can also access this API routing information with sufficient permissions. + +### 5.12.2 Service Operations + +#### 5.12.2.1 Introduction + +**Table 5.12.2.1-1: Operations of the CAPIF\_Routing\_Info\_API** + +| Service operation name | Description | Initiated by | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Obtain_Routing_Info | This service operation is used by an API exposing function to obtain the API routing information from the CAPIF core function. | API exposing function | + +#### 5.12.2.2 Obtain\_Routing\_Info + +##### 5.12.2.2.1 General + +This service operation is used by an API exposing function to obtain the API routing information from the CAPIF core function. + +##### 5.12.2.2.2 API exposing function obtaining API routing information from the CAPIF core function using Obtain\_Routing\_Info service operation + +To obtain the API routing information from the CAPIF core function, the API exposing function shall send an HTTP GET request message to the CAPIF core function with the API exposing function Identifier and API identification as specified in clause 8.10.2.2.3.1. + +Upon receiving the above described HTTP GET message, the CAPIF core function shall + +1. verify the identity of the API exposing function and check if the API exposing function is authorized to obtain the API routing information corresponding to the API identification; +2. if the API exposing function is authorized to obtain the API routing information, the CAPIF core function shall respond with the API routing information corresponding to the API identification in the HTTP GET response message; and +3. if errors occur when processing the request, the CAPIF core function shall respond to the API exposing function with an appropriate error status code as defined in clause 8.10.5. + +## 6 Services offered by the API exposing function + +### 6.1 Introduction of Services + +The table 6.1-1 lists the API exposing function APIs below the service name. A service description clause for each API gives a general description of the related API. + +**Table 6.1-1: List of AEF Services** + +| Service Name | Service Operations | Operation Semantics | Consumer(s) | +|------------------|-------------------------|---------------------|---------------------| +| AEF_Security_API | Initiate_Authentication | Request/ Response | API Invoker | +| | Revoke_Authorization | Request/ Response | CAPIF core function | + +Table 6.1-2 summarizes the corresponding APIs defined in this specification. + +**Table 6.1-2: API Descriptions** + +| Service Name | Clause | Description | OpenAPI Specification File | apiName | Annex | +|------------------|--------|--------------------------|-------------------------------|--------------|-------| +| AEF_Security_API | 9.1 | AEF Security API Service | TS29222_AEF_Security_API.yaml | aef-security | A.10 | + +## 6.2 AEF\_Security\_API + +### 6.2.1 Service Description + +#### 6.2.1.1 Overview + +The AEF security API, allows an API invokers via CAPIF-2/2e reference points to request API exposing function to ensure that authentication parameters necessary for authentication of the API invoker are available with the API exposing function. If the necessary authentication parameters are not available, the API exposing function fetches necessary authentication parameters from CAPIF core function to authenticate the API invoker. + +The AEF security API, also allows the CAPIF core function via CAPIF-3/3e reference points to request API exposing function to revoke the authorization of service APIs for an API invoker. + +### 6.2.2 Service Operations + +#### 6.2.2.1 Introduction + +The service operation defined for AEF\_Security\_API is shown in table 6.2.2.1-1. + +**Table 6.2.2.1-1: Operations of the AEF\_Security\_API** + +| Service operation name | Description | Initiated by | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| Initiate_Authentication | This service operation is used by an API invoker to request API exposing function to confirm necessary authentication data is available to authenticate the API invoker | API invoker | +| Revoke_Authorization | This service operation is used by the CAPIF core function to request the API exposing function to revoke the authorization of service APIs for an API invoker. | CAPIF core function | + +## 6.2.2.2 Initiate\_Authentication + +### 6.2.2.2.1 General + +This service operation is used by an API invoker to initiate authentication with the API exposing function. On receiving the Initiate\_Authentication the API exposing function fetches the authentication information of the API invoker from the CAPIF core function, if required. + +### 6.2.2.2.2 API invoker initiating authentication using Initiate\_Authentication service operation + +To initiate authentication with the API exposing function, the API invoker shall send an HTTP POST message to the API exposing function with the API invoker ID to the URI "{apiRoot}/aef-security/v1/check-authentication". + +Upon receiving the above described HTTP POST message, the API exposing function shall check if the credentials of the API invoker for authentication are available with the API exposing function. If the credentials of the API invoker for authentication are not available, the API exposing function shall use the service defined in clause 5.6.2.4.2 to fetch the credentials from the CAPIF core function. + +The API exposing function shall store the received credentials and respond to the API invoker with 200 OK status code. + +## 6.2.2.3 Revoke\_Authorization + +### 6.2.2.3.1 General + +This service operation is used by CAPIF core function to revoke authorization of service APIs (e.g. due to policy change in the CAPIF core function). On receiving the Revoke\_Authorization the API exposing function revokes authorization of the API invoker for the service APIs indicated in the request. + +### 6.2.2.3.2 CAPIF core function initiating revocation using Revoke\_Authorization service operation + +To revoke authorization, the CAPIF core function shall send an HTTP POST message to the API exposing function with the API invoker ID and a list of service API IDs on the URI "{apiRoot}/aef-security/v1/revoke-authorization". + +Upon receiving the HTTP POST message, the API exposing function shall revoke the authorization of the API invoker for the indicated service APIs (e.g. it may update the list of unauthorized APIs locally), and then respond to the CAPIF core function with 200 OK status code. + +The CAPIF core function shall also notify the API invoker of the authorization invalidation using the Notification Destination URI received in the Obtain\_Security\_Method message. + +--- + +# 7 CAPIF Design Aspects Common for All APIs + +## 7.1 General + +CAPIF APIs are RESTful APIs that allow secure access to the capabilities provided by CAPIF. + +This document specifies the procedures triggered at different functional entities as a result of API invocation requests and event notifications. The stage-2 level requirements and signalling flows are defined in 3GPP TS 23.222 [2]. + +Several design aspects, as mentioned in the following clauses, are specified in 3GPP TS 29.122 [14] and referenced by this specification. + +## 7.2 Data Types + +### 7.2.1 General + +This clause defines structured data types, simple data types and enumerations that are applicable to several APIs defined in the present specification and can be referenced from data structures defined in the subsequent clauses. + +In addition, data types that are defined in OpenAPI Specification [3] can also be referenced from data structures defined in the subsequent clauses. + +NOTE: As a convention, data types in the present specification are written with an upper-case letter in the beginning. Parameters are written with a lower-case letter in the beginning. Enumerations are written using UPPER\_WITH\_UNDERSCORE case convention. As an exception, data types that are also defined in OpenAPI Specification [3] can use a lower-case case letter in the beginning for consistency. + +Table 7.2.1-1 specifies data types re-used by the CAPIF from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the CAPIF. + +**Table 7.2.1-1: Re-used Data Types** + +| Data type | Reference | Comments | +|--------------------|---------------------|------------------------------------------------------------------------------------------------------------------| +| Uri | 3GPP TS 29.122 [14] | | +| TestNotification | 3GPP TS 29.122 [14] | Following clarifications apply:
- The SCEF is the CAPIF core function; and
- The SCS/AS is the Subscriber. | +| WebsockNotifConfig | 3GPP TS 29.122 [14] | Following clarifications apply:
- The SCEF is the CAPIF core function; and
- The SCS/AS is the Subscriber. | + +### 7.2.2 Referenced structured data types + +Table 7.2.2-1 lists structured data types defined in this specification referenced by multiple services: + +**Table 7.2.2-1: Referenced Structured Data Types** + +| Data type | Reference | Description | +|-----------------------|------------------|----------------------------------| +| Log | Clause 8.7.4.2.3 | Individual log entries | +| InterfaceDescription | Clause 8.2.4.2.3 | Description of the API interface | +| ServiceAPIDescription | Clause 8.2.4.2.2 | Description of the service API | + +### 7.2.3 Referenced Simple data types and enumerations + +Following simple data types defined in Table 7.2.3.1-1 are applicable to several APIs in this document: + +**Table 7.2.3.1-1: Simple data types applicable to several APIs** + +| Type name | Reference | Description | +|-----------------|------------------|------------------------------------------------------------------------------------| +| CAPIFResourceId | n/a | string chosen by the CAPIF core function to serve as identifier in a resource URI. | +| DataFormat | Clause 8.2.4.3.4 | Data format used by the API | +| Protocol | Clause 8.2.4.3.3 | Protocol used by the API | + +## 7.3 Usage of HTTP + +For CAPIF APIs, support of HTTP/1.1 (IETF RFC 9112 [4], IETF RFC 9110 [5], and IETF RFC 9111 [8]) over TLS is mandatory and support of HTTP/2 (IETF RFC 9113 [10]) over TLS is recommended. TLS shall be used as specified in 3GPP TS 33.122 [16]. + +A functional entity desiring to use HTTP/2 shall use the HTTP upgrade mechanism to negotiate applicable HTTP version as described in IETF RFC 9113 [10]. + +## 7.4 Content type + +The bodies of HTTP request and successful HTTP responses shall be encoded in JSON format (see IETF RFC 8259 [12]). + +The MIME media type that shall be used within the related Content-Type header field is "application/json", as defined in IETF RFC 8259 [12], unless specified otherwise in the API definition. + +The JSON objects defined in clause 5.2.3 of 3GPP TS 29.122 [14] for the HTTP PATCH request shall be supported. + +## 7.5 URI structure + +### 7.5.1 Resource URI structure + +All API URIs of CAPIF APIs shall be: + +**{apiRoot}** + +"apiRoot" is configured by means outside the scope of the present document. It includes the scheme ("https"), host and optional port, and an optional prefix string. "apiName" and "apiVersion" shall be set dependent on the API, as defined in the corresponding clauses below. + +All resource URIs in the clauses below are defined relative to the above root API URI. + +NOTE 1: The "apiVersion" will only be increased if the new API version contains backward incompatible changes. Otherwise, the supported feature mechanism defined in clause 7.8 can be used to negotiate extensions. + +NOTE 2: A different root structure can be used when the resource URI is preconfigured in the API invoking entity. + +The root structure may be followed by "apiSpecificSuffixes" that are dependent on the API and are defined separately for each API as resource URI where they apply: + +**{apiRoot}** + +The naming conventions defined in subclause 5.2.4 of 3GPP TS 29.122 [14] shall apply. + +### 7.5.2 Custom operations URI structure + +The custom operation definition is in Annex C of 3GPP TS 29.501 [18]. + +The URI of a custom operation which is associated with a resource shall have the following structure: + +**{apiRoot}** + +Custom operations can also be associated with the service instead of a resource. The URI of a custom operation which is not associated with a resource shall have the following structure: + +**{apiRoot}** + +In the above URI structures, "apiRoot", "apiName", "apiVersion" and "apiSpecificResourceUriPart" are as defined in clause 7.5.1 and "custOpName" represents the name of the custom operation as defined in clause 5.1.3.2 of 3GPP TS 29.501 [18]. + +## 7.6 Notifications + +The functional entities + +- shall support the delivery of notifications using a separate HTTP connection towards an address; +- may support testing delivery of notifications; and +- may support the delivery of notification using WebSocket protocol (see IETF RFC 6455 [13]), + +as described in 3GPP TS 29.122 [14], with the following clarifications: + +- the SCEF is the CAPIF core function; and +- the SCS/AS is the Subscriber. + +## 7.7 Error handling + +HTTP error handling described in clause 5.2.6 of 3GPP TS 29.122 [14] is applicable to all APIs in the present specification unless specified otherwise, with the following clarifications: + +- the SCEF is the CAPIF core function; and +- the SCS/AS is the functional entity invoking an API. + +## 7.8 Feature negotiation + +The functional entity invoking an API (i.e. the API invoker, the API exposing function, the API publishing function or the API management function) and the CAPIF core function use feature negotiation procedures defined in 3GPP TS 29.122 [14] to negotiate the supported features, with the following clarifications: + +- description of the SCEF applies to the CAPIF core function; +- description of the SCS/AS applies to the functional entity invoking an API; +- the CAPIF Core Function should not register any feature in the NRF; and +- the AEF should not register any feature for AEF\_Security\_API in the NRF. + +## 7.9 HTTP headers + +The HTTP headers and the HTTP custom headers described in 3GPP TS 29.122 [14] are applicable to all APIs in this document. + +## 7.10 Conventions for Open API specification files + +The conventions for Open API specification files as specified in clause 5.2.9 of 3GPP TS 29.122 [14] shall be applicable for all APIs in this document. + +## 7.11 CAPIF vendor-specific extensions + +Information elements exchanged on the CAPIF APIs shall be extensible with vendor-specific data as specified in clause 5.2.13.2 of 3GPP TS 29.122 [14]. + +## 8 CAPIF API Definition + +### 8.1 CAPIF\_Discover\_Service\_API + +#### 8.1.1 API URI + +The CAPIF\_Discover\_Service\_API service shall use the CAPIF\_Discover\_Service\_API. + +The request URIs used in HTTP requests from the API invoker towards the CAPIF core function shall have the Resource URI structure defined in clause 7.5 with the following clarifications: + +- The shall be "service-apis". +- The shall be "v1". +- The shall be set as described in clause 8.1.2.\ + +All the resource URIs and the custom operation URIs specified in the clauses below are defined relative to the above API URI. + +#### 8.1.2 Resources + +##### 8.1.2.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 8.1.2.1-1 depicts the resource URIs structure for the CAPIF\_Discover\_Service\_API. + +![Diagram showing the resource URI structure for the CAPIF_Discover_Service_API. It consists of two boxes connected by a line. The top box contains the base URI path: {apiRoot}/service-apis/. The bottom box contains the specific resource path: /allServiceAPIs. A line connects the bottom box to the top box, indicating that the resource path is relative to the base URI path.](fc07df3b799d63e7e6c7760ca077ee99_img.jpg) + +``` + +graph TD + A["{apiRoot}/service-apis/"] --- B["/allServiceAPIs"] + +``` + +Diagram showing the resource URI structure for the CAPIF\_Discover\_Service\_API. It consists of two boxes connected by a line. The top box contains the base URI path: {apiRoot}/service-apis/. The bottom box contains the specific resource path: /allServiceAPIs. A line connects the bottom box to the top box, indicating that the resource path is relative to the base URI path. + +**Figure 8.1.2.1-1: Resource URI structure of the CAPIF\_Discover\_Service\_API** + +Table 8.1.2.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 8.1.2.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------| +| All published service APIs (Store) | /allServiceAPIs
(NOTE) | GET | Discover published service APIs and retrieve a collection of APIs according to certain filter criteria. | +| NOTE: The path segment "allServiceAPIs" does not follow the related naming convention defined in subclause 7.5.1. The path segment is however kept as currently defined in this specification for backward compatibility considerations. | | | | + +## 8.1.2.2 Resource: All published service APIs + +### 8.1.2.2.1 Description + +The All published service APIs resource represents a collection of published service APIs on a CAPIF core function. The resource is modelled as a Store resource archetype (see Annex C.3 of 3GPP TS 29.501 [18]) + +### 8.1.2.2.2 Resource Definition + +Resource URI: {apiRoot}/service-apis//allServiceAPIs + +This resource shall support the resource URI variables defined in table 8.1.2.2.2-1. + +**Table 8.1.2.2.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|---------|-----------|----------------| +| apiRoot | string | See clause 7.5 | + +### 8.1.2.2.3 Resource Standard Methods + +#### 8.1.2.2.3.1 GET + +This operation enables to retrieve a list of APIs currently registered in the CAPIF core function, satisfying a number of filter criteria. + +**Table 8.1.2.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | Applicability | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| api-invoker-id | string | M | 1 | It represents the identifier (assigned by the CCF) of the API invoker that is sending the request. It may also represent the identifier of the CCF that is sending the request if the request is sent over the CAPIF-6/6e reference point. (NOTE 1) | | +| api-name | string | O | 0..1 | Contains the API name as {apiName} part of the URI structure as defined in clause 5.2.4 of 3GPP TS 29.122 [14]. | | +| api-version | string | O | 0..1 | Contains the API major version conveyed in the URI (e.g. v1). | | +| comm-type | CommunicationType | O | 0..1 | Communication type used by the API (e.g. REQUEST_RESPONSE). | | +| protocol | Protocol | O | 0..1 | Protocol used by the API. | | +| aef-id | string | O | 0..1 | AEF identifier. | | +| data-format | DataFormat | O | 0..1 | Data format used by the API (e.g. serialization protocol JSON). | | +| api-cat | string | O | 0..1 | The service API category to which the service API belongs. | | +| preferred-aef-loc | AefLocation | O | 0..1 | The preferred AEF location. If this parameter is present, the CCF shall try to discover a matched AEF location the service API supports. This parameter is ignored by the CCF if there is no matching record found. | | +| req-api-prov-name | string | O | 0..1 | Represents the required API provider name. | RNAA | +| supported-features | SupportedFeatures | O | 0..1 | To filter irrelevant responses related to unsupported features. | | +| api-supported-features | SupportedFeatures | C | 0..1 | Features supported by the discovered service API indicated by api-name parameter. This may only be present if the api-name query parameter is present. | ApiSupportedFeatureQuery | +| ue-ip-addr | IpAddrInfo | O | 0..1 | Represents the UE IP address information. | RNAA | +| service-kpis | ServiceKpis | O | 0..1 | Contains information about service characteristics provided by the targeted service API(s). | EdgeApp_2 | +| NOTE 1: This parameter is not part of API filter criteria so that it is not used in matching APIs published in the CCF. | | | | | | +| NOTE 2: In addition to the standardized query parameters defined in table 8.1.2.2.3.1-1 above, the service consumer may also provide vendor-specific query parameters as specified in clause 5.2.13.3 of 3GPP TS 29.122 [14]. The CCF shall use any received vendor-specific query parameters in the filtering process of the results to be returned in the response in a similar way and in addition to the standardized query parameters defined in this table. This capability may be signalled by the feature VendSpecQueryParams. | | | | | | + +This method shall support the request data structures specified in table 8.1.2.2.3.1-2 and the response data structures and response codes specified in table 8.1.2.2.3.1-3. + +**Table 8.1.2.2.3.1-2: Data structures supported by the GET Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.1.2.2.3.1-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DiscoveredAPIs | M | 1 | 200 OK | The response body contains the result of the search over the list of registered APIs. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| ProblemDetails | O | 0..1 | 414 URI Too Long | Indicates that the server refuses to process the request because the request-target is too long. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.1.2.2.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.1.2.2.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.1.2.2.4 Resource Custom Operations + +None. + +### 8.1.2A Custom Operations without associated resources + +There are no custom operations without associated resources defined for this API in this release of the specification. + +### 8.1.3 Notifications + +There are no notifications defined for this API in this release of the specification. + +### 8.1.4 Data Model + +#### 8.1.4.1 General + +This clause specifies the application data model supported by the API. Data types listed in clause 7.2 also apply to this API. + +Table 8.1.4.1-1 specifies the data types defined specifically for the CAPIF\_Discover\_Service\_API. + +**Table 8.1.4.1-1: CAPIF\_Discover\_Service\_API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|----------------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| DiscoveredAPIs | Clause 8.1.4.2.2 | Represents a list of APIs currently registered in the CAPIF core function and satisfying a number of filter criteria provided by the API consumer. | | +| IpAddrInfo | Clause 8.1.4.2.4 | Represents the UE IP address information. | RNAA | + +Table 8.1.4.1-2 specifies data types re-used by the CAPIF\_Discover\_Service\_API service. + +**Table 8.1.4.1-2: Re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|-------------------------------------------------------------------------------------|---------------| +| AefLocation | Clause 8.2.4.2.10 | Used to indicate the AEF location. | | +| CommunicationType | Clause 8.2.4.3.5 | Used to indicate the communication type used by the API. | | +| Ipv4Addr | 3GPP TS 29.122 [14] | Used to indicate an IPv4 address. | RNAA | +| Ipv6Addr | 3GPP TS 29.122 [14] | Used to indicate an IPv6 address. | RNAA | +| ProblemDetails | 3GPP TS 29.122 [14] | Used to represent additional information and details on an error response. | | +| ServiceKpis | Clause 8.2.4.2.13 | Represents information about the service characteristics provided by a service API. | | +| SupportedFeatures | 3GPP TS 29.571 [19] | Used to negotiate the applicability of optional features defined in table 8.1.6-1. | | + +## 8.1.4.2 Structured data types + +### 8.1.4.2.1 Introduction + +This clause defines the structured data types to be used in resource representations of the CAPIF\_Discover\_Service\_API. + +### 8.1.4.2.2 Type: DiscoveredAPIs + +**Table 8.1.4.2.2-1: Definition of type DiscoveredAPIs** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------------|------------------------------|---|-------------|--------------------------------------------------------------------|---------------| +| serviceAPIDescriptions | array(ServiceAPIDescription) | O | 1..N | Description of the service API as published by the service. (NOTE) | | + +NOTE: For the CAPIF\_Discover\_Service\_API, the supportedFeatures attribute of the ServiceAPIDescription data type shall be provided in the HTTP GET response of a successful query. In addition, the supportedFeatures attribute may include one or more supported feature(s) as defined in clause 8.1.6. + +8.1.4.2.3 Void + +8.1.4.2.4 Type: IpAddrInfo + +**Table 8.1.4.2.4-1: Definition of type IpAddrInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------|---|-------------|--------------------------------------------------|---------------| +| ipv4Addr | Ipv4Addr | C | 0..1 | Represents the IPv4 address of the UE.
(NOTE) | | +| ipv6Addr | Ipv6Addr | C | 0..1 | Represents the IPv6 address of the UE.
(NOTE) | | + +NOTE: These attributes are mutually exclusive. Either one of them shall be present. + +### 8.1.4.3 Simple data types and enumerations + +None. + +## 8.1.5 Error Handling + +### 8.1.5.1 General + +HTTP error handling shall be supported as specified in clause 7.7. + +In addition, the requirements in the following clauses shall apply. + +### 8.1.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the CAPIF\_Discover\_Service\_API. + +### 8.2.5.3 Application Errors + +The application errors defined for the CAPIF\_Publish\_Service\_API are listed in table 8.2.5.3-1. + +**Table 8.2.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 8.1.6 Feature negotiation + +General feature negotiation procedures are defined in clause 7.8. + +**Table 8.1.6-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | ApiSupportedFeatureQuery | Indicates the support of the query filter indicating the supported feature(s) of a service API. | +| 2 | VendSpecQueryParams | Indicates the support of vendor specific API discovery query filter parameters. | +| 3 | RNAA | Indicates the support of the RNAA functionality.

This feature enables the following functionality:
  • - provisioning the API provider name and the related filtering criteria enhancement.
  • - provisioning the UE IP address information and the related filtering criteria enhancement.
| + +## 8.2 CAPIF\_Publish\_Service\_API + +### 8.2.1 API URI + +The CAPIF\_Publish\_Service\_API service shall use the CAPIF\_Publish\_Service\_API. + +The request URIs used in HTTP requests from the API publishing function towards the CAPIF core function shall have the Resource URI structure as defined in clause 7.5 with the following clarifications: + +- The shall be "published-apis". +- The shall be "v1". +- The shall be set as described in clause 8.2.2. + +All the resource URIs and the custom operation URIs specified in the clauses below are defined relative to the above API URI. + +### 8.2.2 Resources + +#### 8.2.2.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 8.2.2.1-1 depicts the resource URIs structure for the CAPIF\_Publish\_Service\_API. + +![Figure 8.2.2.1-1: Resource URI structure of the CAPIF_Publish_Service_API. The diagram shows a hierarchical tree structure starting with {apiRoot}/published-apis/. A branch from this root leads to /{apfId}, which then leads to /service-apis (shown in a box). From /service-apis, a branch leads to /{serviceApiId} (also shown in a box).](0a73b03fba21af142d619a9a662e6490_img.jpg) + +``` + +graph TD + Root["{apiRoot}/published-apis/"] --> apfId["/{apfId}"] + apfId --> serviceApis["/service-apis"] + serviceApis --> serviceApiId["/{serviceApiId}"] + +``` + +Figure 8.2.2.1-1: Resource URI structure of the CAPIF\_Publish\_Service\_API. The diagram shows a hierarchical tree structure starting with {apiRoot}/published-apis/. A branch from this root leads to /{apfId}, which then leads to /service-apis (shown in a box). From /service-apis, a branch leads to /{serviceApiId} (also shown in a box). + +**Figure 8.2.2.1-1: Resource URI structure of the CAPIF\_Publish\_Service\_API** + +Table 8.2.2.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 8.2.2.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|------------------------------|--------------------------------------|---------------------------------|-------------------------------------| +| APF published APIs | /{apfId}/service-apis | POST | Publish a new API | +| | | GET | Retrieve all published service APIs | +| Individual APF published API | /{apfId}/service-apis/{serviceApiId} | GET | Retrieve a published service API | +| | | PUT | Update a published service API | +| | | PATCH | Modify a published service API. | +| | | DELETE | Unpublish a published service API. | + +## 8.2.2.2 Resource: APF published APIs + +### 8.2.2.2.1 Description + +The APF published APIs resource represents all published service APIs of a API publishing function. + +### 8.2.2.2.2 Resource Definition + +Resource URI: {apiRoot}/published-apis//{apfId}/service-apis + +This resource shall support the resource URI variables defined in table 8.2.2.2-1. + +**Table 8.2.2.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|---------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| apiRoot | string | See clause 7.5 | +| apfId | string | Identifies the API publishing function; for CAPIF interconnection case, this string also identifies the CCF which is publishing the service API. | + +### 8.2.2.2.3 Resource Standard Methods + +#### 8.2.2.2.3.1 POST + +This method shall support the URI query parameters specified in table 8.2.2.2.3.1-1. + +**Table 8.2.2.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.2.2.2.3.1-2 and the response data structures and response codes specified in table 8.2.2.2.3.1-3. + +**Table 8.2.2.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------------|---|-------------|-----------------------------------------------| +| ServiceAPIDescription | M | 1 | Definition of the service API being published | + +**Table 8.2.2.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|----------------------------------------------------------------------------------------------------------------------------| +| ServiceAPIDescription | M | 1 | 201
Created | Service API published successfully.

The URI of the created resource shall be returned in the "Location" HTTP header | +| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. | | | | | + +**Table 8.2.2.2.3.1-4: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/published-apis///service-apis/{serviceApId} | + +#### 8.2.2.2.3.2 GET + +This method shall support the URI query parameters specified in table 8.2.2.2.3.2-1. + +**Table 8.2.2.2.3.2-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.2.2.2.3.2-2 and the response data structures and response codes specified in table 8.2.2.2.3.2-3. + +**Table 8.2.2.2.3.2-2: Data structures supported by the GET Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.2.2.2.3.2-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| array(ServiceAPIDescription) | O | 0..N | 200 OK | Definition of all service API(s) published by the API publishing function. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.2.2.2.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.2.2.2.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.2.2.2.4 Resource Custom Operations + +None. + +#### 8.2.2.3 Resource: Individual APF published API + +##### 8.2.2.3.1 Description + +The Individual APF published API resource represents an individual published service API. + +##### 8.2.2.3.2 Resource Definition + +Resource URI: {apiRoot}/published-apis/{apiVersion}/{apfId}/service-apis/{serviceApiId} + +This resource shall support the resource URI variables defined in table 8.2.2.3.2-1. + +**Table 8.2.2.3.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|--------------|-----------|------------------------------------------------| +| apiRoot | string | See clause 7.5 | +| apfId | string | Identifies the API publishing function | +| serviceApiId | string | Identifies an individual published service API | + +### 8.2.2.3.3 Resource Standard Methods + +#### 8.2.2.3.3.1 GET + +This method shall support the URI query parameters specified in table 8.2.2.3.3.1-1. + +**Table 8.2.2.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.2.2.3.3.1-2 and the response data structures and response codes specified in table 8.2.2.3.3.1-3. + +**Table 8.2.2.3.3.1-2: Data structures supported by the GET Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.2.2.3.3.1-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceAPIDescription | M | 1 | 200 OK | Definition of individual service API published by the API publishing function. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.2.2.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.2.2.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.2.2.3.3.2 PUT + +This method shall support the URI query parameters specified in table 8.2.2.3.3.2-1. + +**Table 8.2.2.3.3.2-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.2.2.3.3.2-2 and the response data structures and response codes specified in table 8.2.2.3.3.2-3. + +**Table 8.2.2.3.3.2-2: Data structures supported by the PUT Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------------|---|-------------|----------------------------------------| +| ServiceAPIDescription | M | 1 | Updated definition of the service API. | + +**Table 8.2.2.3.3.2-3: Data structures supported by the PUT Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceAPIDescription | M | 1 | 200 OK | Definition of the service API updated successfully and the updated service API definition is returned. | +| n/a | | | 204 No Content | Definition of the service API updated successfully. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.2.2.3.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.2.2.3.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +### 8.2.2.3.3.3 DELETE + +This method shall support the URI query parameters specified in table 8.2.2.3.3.3-1. + +**Table 8.2.2.3.3.3-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.2.2.3.3.3-2 and the response data structures and response codes specified in table 8.2.2.3.3.3-3. + +**Table 8.2.2.3.3.3-2: Data structures supported by the DELETE Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.2.2.3.3.3-3: Data structures supported by the DELETE Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | The individual published service API matching the serviceApiId is deleted. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.2.2.3.3.3-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.2.2.3.3.3-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.2.2.3.3.4 PATCH + +This method shall support the URI query parameters specified in table 8.2.2.3.3.4-1. + +**Table 8.2.2.3.3.4-1: URI query parameters supported by the PATCH method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.2.2.3.3.4-2 and the response data structures and response codes specified in table 8.2.2.3.3.4-3. + +**Table 8.2.2.3.3.4-2: Data structures supported by the PATCH Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------------------|---|-------------|--------------------------------------------------------------------------------------------------| +| ServiceAPIDescriptionPatch | M | 1 | Contains the modifications to be applied to the concerned Individual APF published API resource. | + +**Table 8.2.2.3.3.4-3: Data structures supported by the PATCH Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------------------------------------------------------------------------------------------------------------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceAPIDescription | M | 1 | 200 OK | The definition of the service API is updated successfully and a representation of the modified service API definition is returned. | +| n/a | | | 204 No Content | The definition of the service API is updated successfully. | +| n/a | | | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| NOTE: The mandatory HTTP error status codes for the HTTP PATCH method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. | | | | | + +**Table 8.2.2.3.3.4-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.2.2.3.3.4-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +### 8.2.2.3.4 Resource Custom Operations + +None. + +## 8.2.2A Custom Operations without associated resources + +There are no custom operations without associated resources defined for this API in this release of the specification. + +## 8.2.3 Notifications + +There are no notifications defined for this API in this release of the specification. + +## 8.2.4 Data Model + +### 8.2.4.1 General + +This clause specifies the application data model supported by the API. Data types listed in clause 7.2 also apply to this API. + +Table 8.2.4.1-1 specifies the data types defined specifically for the CAPIF\_Publish\_Service\_API service. + +specifies the data types defined specifically for the CAPIF\_Publish\_Service\_API service. + +**Table 8.2.4.1-1: CAPIF\_Publish\_Service\_API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|----------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| ApiStatus | Clause 8.2.4.2.12 | Represents the API status. | ApiStatusMonitoring | +| AefLocation | Clause 8.2.4.2.10 | Represents the location information (e.g. civic address, GPS coordinates, data center ID) where the AEF providing the service API is located. | | +| AefProfile | Clause 8.2.4.2.4 | Represents the AEF profile data. | | +| CommunicationType | Clause 8.2.4.3.5 | Indicates a communication type of the resource or a custom operation. | | +| CustomOperation | Clause 8.2.4.2.7 | Represents the description of a custom operation. | | +| DateFormat | Clause 8.2.4.3.4 | Indicates a data format, e.g., JSON. | | +| InterfaceDescription | Clause 8.2.4.2.3 | Represents the description of the API interface. | | +| IpAddrRange | Clause 8.2.4.2.14 | Represents the list of IP address ranges information. | | +| Operation | Clause 8.2.4.3.7 | Indicates an HTTP method (e.g. PUT). | | +| Protocol | Clause 8.2.4.3.3 | Indicates a protocol and protocol version used by the API. | | +| PublishedApiPath | Clause 8.2.4.2.9 | Represents the published API path within the same CAPIF provider domain. | | +| Resource | Clause 8.2.4.2.6 | Represents the API resource data. | | +| SecurityMethod | Clause 8.2.4.3.6 | Indicates the security method (e.g. PKI). | | +| ServiceAPIDescription | Clause 8.2.4.2.2 | Represents the description of a service API as published by the APF. | | +| ServiceAPIDescriptionPatch | Clause 8.2.4.2.11 | Represents the parameters to request the modification of an APF published API resource. | PatchUpdate | +| ServiceKpis | Clause 8.2.4.2.13 | Represents information about the service characteristics provided by a service API. | | +| ShareableInformation | Clause 8.2.4.2.8 | Indicates whether the service API and/or the service API category can be shared to the list of CAPIF provider domains. | | +| Version | Clause 8.2.4.2.5 | Represents the API version information | | + +Table 8.2.4.1-2 specifies data types re-used by the CAPIF\_Publish\_Service\_API service: + +**Table 8.2.4.1-2: Re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|----------------------------------------------------------------------------------------|-------------------------------| +| CivicAddress | 3GPP TS 29.572 [30] | Used to indicate a civic address. | | +| DateTime | 3GPP TS 29.122 [14] | Used to indicate an expiration timer. | | +| DurationSec | 3GPP TS 29.122 [14] | Indicates the duration in seconds. | | +| Fqdn | 3GPP TS 29.571 [19] | Used to indicate a FQDN. | | +| GeographicArea | 3GPP TS 29.572 [30] | Used to indicate a geographic area. | | +| Ipv4Addr | 3GPP TS 29.122 [14] | Used to indicate an IPv4 address. | | +| Ipv6Addr | 3GPP TS 29.122 [14] | Used to indicate an IPv6 address. | | +| Ipv4AddressRange | 3GPP TS 29.571 [19] | Used to indicate the IPv4 address range. | RNAA | +| Ipv6AddressRange | 3GPP TS 29.571 [19] | Used to indicate the IPv6 address range. | RNAA | +| Port | 3GPP TS 29.122 [14] | Used to indicate a port. | | +| SupportedFeatures | 3GPP TS 29.571 [19] | Used to negotiate the applicability of optional features defined in table 8.2.6-1. | ApiSupportedFeaturePublishing | +| Uinteger | 3GPP TS 29.571 [19] | Unsigned Integer, i.e. only value 0 and integers above 0 are permissible. Minimum = 0. | | + +## 8.2.4.2 Structured data types + +### 8.2.4.2.1 Introduction + +### 8.2.4.2.2 Type: ServiceAPIDescription + +**Table 8.2.4.2.2-1: Definition of type ServiceAPIDescription** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|--------------------|-----------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| apiName | string | M | 1 | API name, it is set as {apiName} part of the URI structure as defined in clause 5.2.4 of 3GPP TS 29.122 [14]. | | +| apiId | string | O | 0..1 | API identifier assigned by the CAPIF core function to the published service API. Shall not be present in the HTTP POST request from the API publishing function to the CAPIF core function. Shall be present in the HTTP POST response from the CAPIF core function to the API publishing function and in the HTTP GET response from the CAPIF core function to the API invoker (discovery API). | | +| apiStatus | ApiStatus | O | 0..1 | Indicates the API status.
If this attribute is omitted, the Service API is active at all AEF(s) present in the "aefProfiles" attribute. | ApiStatusMonitoring | +| aefProfiles | array(AefProfile) | C | 1..N | AEF profile information, which includes the exposed API details (e.g. protocol). For CAPIF-4/4e interface, API publishing function shall provide this attribute to the CAPIF core function in service API publishing. For CAPIF-1/1e interface, the CAPIF core function shall provide this attribute to the API Invoker during service API discovery. (NOTE 2) | | +| description | string | O | 0..1 | Text description of the API | | +| supportedFeatures | Supported Features | O | 0..1 | The supported optional features of the CAPIF API. (NOTE 1) | | +| shareableInfo | Shareable Information | O | 0..1 | Represents whether the service API and/or the service API category can be published to other CCFs. | | +| serviceAPICategory | string | C | 0..1 | The service API category to which the service API belongs to. This attribute is only applicable for CAPIF-6/6e interface. (NOTE 2) | | +| ccfId | string | C | 0..1 | CAPIF core function identifier which can be contacted further for discovering the details of service API information. This attribute is only applicable for CAPIF-6/6e interface and shall be provided with serviceAPICategory. (NOTE 2) | | +| apiSuppFeats | Supported Features | O | 0..1 | Provided by the consumer to indicate the features supported by the service API. | ApiSupportedFeaturePublishing | +| pubApiPath | Published ApiPath | C | 0..1 | It contains the published API path within the same CAPIF provider domain. it shall be provided by the CCF when publishing the service API to other CCF via the CAPIF-6 reference point. | | + +NOTE 1: For CAPIF\_Publish\_Service\_API, the supported features attribute shall be provided in the HTTP POST request and in the response of successful resource creation. In addition, the supportedFeatures attribute may include one or more the supported features as defined in clause 8.2.6. + +NOTE 2: For CAPIF-6/6e interface, at least one of aefProfiles or serviceAPICategory and the corresponding ccfId shall be provided. + +### 8.2.4.2.3 Type: InterfaceDescription + +**Table 8.2.4.2.3-1: Definition of type InterfaceDescription** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------|-----------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------| +| ipv4Addr | Ipv4Addr | C | 0..1 | String identifying an IPv4 address (NOTE 1, NOTE 2) | | +| ipv6Addr | Ipv6Addr | C | 0..1 | String identifying an IPv6 address (NOTE 1, NOTE 2) | | +| fqdn | Fqdn | C | 0..1 | String containing a Fully Qualified Domain Name. (NOTE 1, NOTE 2) | ExtendedIntfDesc | +| port | Port | O | 0..1 | Port (NOTE 2) | | +| apiPrefix | string | O | 0..1 | A string representing an optional deployment-specific string (API prefix) in the form of a sequence of path segments that starts with a "/" character. (NOTE 2) | ExtendedIntfDesc | +| securityMethods | array(SecurityMethod) | M | 1..N | Security methods supported by the interface. It takes precedence over the security methods provided in AefProfile, for this specific interface | | + +NOTE 1: Exactly one of the attributes "ipv4Addr", "ipv6Addr" and "fqdn" shall be included. +NOTE 2: When the contents of this data type are used to construct the apiRoot of an API, they are used as described in clause 4.4.1 of 3GPP TS 29.501 [18]. + +### 8.2.4.2.4 Type: AefProfile + +**Table 8.2.4.2.4-1: Definition of type AefProfile** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------------|-------------------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| aefId | string | M | 1 | AEF identifier | | +| versions | array(Vers ion) | M | 1..N | API version | | +| protocol | Protocol | O | 0..1 | Protocol used by the API.
(NOTE 3) | | +| dataFormat | DataForm at | O | 0..1 | Data format used by the API
(NOTE 3) | | +| securityMethods | array(SecurityMethod) | O | 1..N | Security methods supported by the AEF for all interfaces. Certain interfaces may have different security methods supported in the attribute interfaceDescriptions. | | +| domainName | string | O | 0..1 | Domain to which API belongs to (NOTE 1) | | +| interfaceDescriptions | array(Inter faceDescr iption) | O | 1..N | Interface details (NOTE 1) | | +| aefLocation | AefLocatio n | O | 0..1 | The location information (e.g. civic address, GPS coordinates, data center ID) where the AEF providing the service API is located. | | +| serviceKpis | ServiceKpi s | O | 0..1 | Contains information about the service characteristics provided by the service API. | EdgeApp_2 | +| ueIpRange | IpAddrRan ge | O | 0..1 | The list of public IP ranges of UEs. | RNAA | + +NOTE 1: Only one of the attributes "domainName" or "interfaceDescriptions" shall be included. +NOTE 2: Notification or callback type of resource is not included. +NOTE 3: The protocol and/or data format to be used for AEFs defined outside 3GPP (e.g. by other SDOs) may alternatively be indicated via vendor-specific extensions to the AefProfile data structure using the mechanism defined in clause 7.11. + +## 8.2.4.2.5 Type: Version + +Table 8.2.4.2.5-1: Definition of type Version + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| apiVersion | string | M | 1 | API major version in URI (e.g. v1) | | +| expiry | DateTime | O | 0..1 | Expiry date and time of the AEF service. This represents the planned retirement date as specified in clause 4.3.1.5 of 3GPP TS 29.501 [18]. | | +| resources | array(Resource) | O | 1..N | Resources supported by the API. It may include the custom operations with resource association. | | +| custOperations | array(CustomOperation) | O | 1..N | Custom operations without resource association. | | + +## 8.2.4.2.6 Type: Resource + +Table 8.2.4.2.6-1: Definition of type Resource + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| resourceName | string | M | 1 | Resource name. | | +| commType | CommunicationType | M | 1 | Communication type used by the API resource. (NOTE 1) | | +| uri | string | M | 1 | Relative URI of the API resource, it is set as {apiSpecificSuffixes} part of the URI structure as defined in clause 5.2.4 of 3GPP TS 29.122 [14]. | | +| custOpName | string | O | 0..1 | it is set as {custOpName} part of the URI structure for the case where there is only a single custom operation associated with this resource as defined in clause 5.2.4 of 3GPP TS 29.122 [14]. (NOTE 2) | | +| custOperations | array(CustomOperation) | O | 1..N | List of custom operations associated to this resource. (NOTE 2) | MultipleCustomOperations | +| operations | array(Operation) | C | 1..N | Supported HTTP methods for the API resource. Only applicable when the protocol in AefProfile indicates HTTP. | | +| description | string | O | 0..1 | Text description of the API resource. | | + +NOTE 1: The communication type refers to the semantics of the resource or custom operation and is independent of the HTTP methods that are supported (e.g. if a resource is used for subscriptions then its CommunicationType shall be SUBSCRIBE\_NOTIFY even if it supports also the GET method for retrieving the subscriptions). + +NOTE 2: The attributes "custOpName" and "custOperations" are mutually exclusive. + +## 8.2.4.2.7 Type: CustomOperation + +Table 8.2.4.2.7-1: Definition of type CustomOperation + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| commType | CommunicationType | M | 1 | Communication type used by the custom operation. | | +| custOpName | string | M | 1 | it is set as {custOpName} part of the URI structure for a custom operation without resource association as defined in clause 5.2.4 of 3GPP TS 29.122 [14]. | | +| operations | array(Operation) | C | 1..N | Supported HTTP methods for the custom operation. Only applicable when the protocol in AefProfile indicates HTTP. | | +| description | string | O | 0..1 | Text description of the custom operation. | | + +## 8.2.4.2.8 Type: ShareableInformation + +Table 8.2.4.2.8-1: Definition of type ShareableInformation + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|---------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| isShareable | boolean | M | 1 | Set to "true" indicates that the service API and/or the service API category can be shared to the list of CAPIF provider domain information. Otherwise set to "false". Default value is "false" if omitted. | | +| capifProvDoms | array(string) | O | 1..N | List of CAPIF provider domains to which the service API information to be shared.
(NOTE) | | + +NOTE: Only one CAPIF provider domain information shall be provided via the CAPIF-6e interface. + +## 8.2.4.2.9 Type: PublishedApiPath + +Table 8.2.4.2.9-1: Definition of type PublishedApiPath + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|---------------|---|-------------|-----------------------------------------------------------------------|---------------| +| ccfIds | array(string) | O | 1..N | A list of CCF identifiers where the service API is already published. | | + +## 8.2.4.2.10 Type: AefLocation + +Table 8.2.4.2.10-1: Definition of type AefLocation + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|----------------|---|-------------|----------------------------------------------------------------------------------------------|---------------| +| civicAddr | CivicAddress | O | 0..1 | Identifies the civic address where the AEF providing the service API is located.
(NOTE) | | +| geoArea | GeographicArea | O | 0..1 | Identifies the geographic area where the AEF providing the service API is located.
(NOTE) | | +| dcId | string | O | 0..1 | Identifies the data center where the AEF providing the service API is located.
(NOTE) | | + +NOTE: At least one of the attributes shall be included. + +## 8.2.4.2.11 Type: ServiceAPIDescriptionPatch + +Table 8.2.4.2.11-1: Definition of type ServiceAPIDescriptionPatch + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| apiStatus | ApiStatus | O | 0..1 | Indicates the API status. | ApiStatusMonitoring | +| aefProfiles | array(AefProfile) | O | 1..N | AEF profile information, which includes the exposed API details (e.g. protocol). | | +| description | string | O | 0..1 | Text description of the API | | +| shareableInfo | Shareable Information | O | 0..1 | Represents whether the service API and/or the service API category can be published to other CCFs. | | +| serviceAPICategory | string | O | 0..1 | The service API category to which the service API belongs. This attribute is only applicable for CAPIF-6/6e interface. (NOTE) | | +| ccfld | string | C | 0..1 | CAPIF core function identifier which can be contacted further for discovering the details of service API information. This attribute is only applicable for CAPIF-6/6e interface and shall be provided if the "serviceAPICategory" attribute is provided. (NOTE) | | +| apiSuppFeats | Supported Features | O | 0..1 | Indicates the features supported by the service API. | ApiSupportedFeaturePublishing | +| pubApiPath | Published ApiPath | O | 0..1 | It contains the published API path within the same CAPIF provider domain. It is applicable only for the CAPIF-6 reference point. | | +| NOTE: For CAPIF-6/6e interface, either the "aefProfiles" attribute or the "serviceAPICategory" attribute and the corresponding "ccfld" attribute may be provided. | | | | | | + +## 8.2.4.2.12 Type: ApiStatus + +Table 8.2.4.2.12-1: Definition of type ApiStatus + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|---------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| aefIds | array(string) | M | 0..N | Indicates the list of AEF ID(s) where the API is active. If an empty array is provided, it indicates that the API is inactive in all AEF(s). | | + +## 8.2.4.2.13 Type: ServiceKpi + +**Table 8.2.4.2.13-1: Definition of type ServiceKpi** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| maxReqRate | UInteger | O | 0..1 | Contains the maximum request rate (i.e., number of requests per second) from the API Invoker that is supported by any service producer of the service API. | | +| maxRestime | DurationSec | O | 0..1 | Contains the maximum response time (expressed in seconds) supported for the API Invoker's service requests. | | +| availability | UInteger | O | 0..1 | Contains the advertised percentage of time any service producer of the service API is available for the API Invoker's use.

Minimum: 0
Maximum: 100 | | +| avalComp | string | O | 0..1 | Contains the maximum compute resource available for the API Invoker.

It is encoded as a string representing a compute resource in FLOPS that shall be formatted as follows:
Pattern: '^d+(\.\d+)? (kFLOPS MFLOPS GFLOPS TFLOPS PFLOPS EFLOPS ZFLOPS)\$'

Examples:
"125 PFLOPS", "0.125 EFLOPS",
"125000 TFLOPS" | | +| avalGraComp | string | O | 0..1 | Contains the maximum graphical compute resource available for the API Invoker.

It is encoded as a string representing a graphical compute resource in FLOPS that shall be formatted as follows:
Pattern: '^d+(\.\d+)? (kFLOPS MFLOPS GFLOPS TFLOPS PFLOPS EFLOPS ZFLOPS)\$'

Examples:
"1250 TFLOPS", "1.25 PFLOPS",
"1250000 GFLOPS" | | +| avalMem | string | O | 0..1 | Contains the maximum memory resource available for the API Invoker.

It is encoded as a string representing a memory resource that shall be formatted as follows:
Pattern: '^d+(\.\d+)? (KB MB GB TB PB EB ZB YB)\$'

Examples:
"128 GB", "0.128 TB", "128000 MB" | | +| avalStor | string | O | 0..1 | Contains the maximum storage resource available for the API Invoker.

It is encoded as a string representing a storage resource that shall be formatted as follows:
Pattern: '^d+(\.\d+)? (KB MB GB TB PB EB ZB YB)\$'

Examples:
"128 TB", "0.128 PB", "128000 GB" | | +| conBand | UInteger | O | 0..1 | Contains the connection bandwidth (expressed in kbps) advertised for the API Invoker's use. | | + +NOTE: At least one of the attributes of this data structure shall be present. + +## 8.2.4.2.14 Type: IpAddrRange + +Table 8.2.4.2.14-1: Definition of type IpAddrRange + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------|-------------------------|---|-------------|----------------------------------------------------------------|---------------| +| ueIpv4AddrRanges | array(Ipv4AddressRange) | C | 1..N | Represents the IPv4 Address ranges of the UE(s).

(NOTE) | | +| ueIpv6AddrRanges | array(Ipv6AddressRange) | C | 1..N | Represents the IPv6 Address ranges of the UE(s).

(NOTE) | | + +NOTE: At least one of these attributes shall be provided. + +## 8.2.4.3 Simple data types and enumerations + +## 8.2.4.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +## 8.2.4.3.2 Simple data types + +The simple data types defined in table 8.2.4.3.2-1 shall be supported. + +Table 8.2.4.3.2-1: Simple data types + +| Type Name | Type Definition | Description | Applicability | +|-----------|-----------------|-------------|---------------| +| n/a | | | | + +## 8.2.4.3.3 Enumeration: Protocol + +Table 8.2.4.3.3-1: Enumeration Protocol + +| Enumeration value | Description | Applicability | +|-------------------|-----------------------------------------------------------------------------------|------------------------| +| HTTP_1_1 | Indicates that the protocol is HTTP version 1.1. | | +| HTTP_2 | Indicates that the protocol is HTTP version 2. | | +| MQTT | Indicates that the protocol is Message Queuing Telemetry Transport.

(NOTE) | ProtocDataFormats_Ext1 | +| WEBSOCKET | Indicates that the protocol is Websocket.

(NOTE) | ProtocDataFormats_Ext1 | + +NOTE: In this release of the specification, this enumeration value shall not be provided for AEFs defined by 3GPP (e.g. SCEF, NEF). It may only be provided for AEFs defined outside 3GPP (e.g. by other SDOs). + +#### 8.2.4.3.4 Enumeration: DataFormat + +**Table 8.2.4.3.4-1: Enumeration DataFormat** + +| Enumeration value | Description | Applicability | +|-------------------|-------------------------------------------------------------------------|------------------------| +| JSON | Indicates that the data format is JSON (JavaScript Object Notation). | | +| XML | Indicates that the data format is Extensible Markup Language.
(NOTE) | ProtocDataFormats_Ext1 | +| PROTOBUF3 | Indicates that the data format is Protocol buffers version 3.
(NOTE) | ProtocDataFormats_Ext1 | + +NOTE: In this release of the specification, this enumeration value shall not be provided for AEFs defined by 3GPP (e.g. SCEF, NEF). It may only be provided for AEFs defined outside 3GPP (e.g. by other SDOs). + +#### 8.2.4.3.5 Enumeration: CommunicationType + +**Table 8.2.4.3.5-1: Enumeration CommunicationType** + +| Enumeration value | Description | Applicability | +|-------------------|----------------------------------------------------|---------------| +| REQUEST_RESPONSE | The communication is of the type request-response. | | +| SUBSCRIBE_NOTIFY | The communication is of the type subscribe-notify | | + +#### 8.2.4.3.6 Enumeration: SecurityMethod + +**Table 8.2.4.3.6-1: Enumeration SecurityMethod** + +| Enumeration value | Description | Applicability | +|-------------------|-------------------------------------------------------------------------------|---------------| +| PSK | Security method 1 (Using TLS-PSK) as described in 3GPP TS 33.122 [16]. | | +| PKI | Security method 2 (Using PKI) as described in 3GPP TS 33.122 [16]. | | +| OAUTH | Security method 3 (TLS with OAuth token) as described in 3GPP TS 33.122 [16]. | | + +#### 8.2.4.3.7 Enumeration: Operation + +**Table 8.2.4.3.7-1: Enumeration Operation** + +| Enumeration value | Description | Applicability | +|-------------------|--------------------|---------------| +| GET | HTTP GET method | | +| POST | HTTP POST method | | +| PUT | HTTP PUT method | | +| PATCH | HTTP PATCH method | | +| DELETE | HTTP DELETE method | | + +### 8.2.5 Error Handling + +#### 8.2.5.1 General + +HTTP error handling shall be supported as specified in clause 7.7. + +In addition, the requirements in the following clauses shall apply. + +### 8.2.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the CAPIF\_Publish\_Service\_API. + +### 8.2.5.3 Application Errors + +The application errors defined for the CAPIF\_Publish\_Service\_API are listed in table 8.2.5.3-1. + +**Table 8.2.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 8.2.6 Feature negotiation + +General feature negotiation procedures are defined in clause 7.8. + +**Table 8.2.6-1: Supported Features** + +| Feature number | Feature Name | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | ApiSupportedFeaturePublishing | Indicates the support of publishing with supported feature for a service API. | +| 2 | PatchUpdate | Indicates the support of the PATCH method for updating an APF published API resource. | +| 3 | ExtendedIntfDesc | Indicates the support of extended interface descriptions. | +| 4 | MultipleCustomOperations | Indicates the support of modelling multiple custom operations associated with a resource. | +| 5 | ProtocDataFormats_Ext1 | Indicates the support of additional protocols and data formats with standardized values.

(NOTE) | +| 6 | ApiStatusMonitoring | Indicates the support of the API status monitoring in CAPIF layer as a part of enhancement of SEAL framework.

This feature enables the following functionality:
- support API status information management. | +| 7 | EdgeApp_2 | This feature indicates the support of the enhancements to the Edge Applications. Within this feature, the following enhancements are covered:
- support of Service KPI. | +| 8 | RNAA | Indicates the support of the RNAA functionality.

This feature enables the following functionality:
- provisioning the list of public IP ranges of UEs for service API publish and update enhancements. | +| NOTE: In this release of the specification, this feature is only applicable for AEFs defined outside 3GPP (e.g. by other SDOs). It does not apply to AEFs defined by 3GPP (e.g. SCEF, NEF). | | | + +## 8.3 CAPIF\_Events\_API + +### 8.3.1 API URI + +The CAPIF\_Events\_API service shall use the CAPIF\_Events\_API. + +The request URIs used in HTTP requests from the Subscriber towards the CAPIF core function shall have the Resource URI structure as defined in clause 7.5 with the following clarifications: + +- The shall be "capif-events". +- The shall be "v1". +- The shall be set as described in clause 8.3.2. + +All the resource URIs and the custom operation URIs specified in the clauses below are defined relative to the above API URI. + +### 8.3.2 Resources + +#### 8.3.2.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 8.3.2.1-1 depicts the resource URIs structure for the CAPIF\_Events\_API. + +![A hierarchical diagram showing the resource URI structure for the CAPIF_Events_API. The root is {apiRoot}/capif-events/. A line descends from this root to a branch labeled /{subscriberId}. From /{subscriberId}, a line descends to a rounded rectangular box containing /subscriptions. From this box, a line descends to another rounded rectangular box containing /{subscriptionId}.](a6f9ef297168667527ab18da412f917d_img.jpg) + +``` + +graph TD + Root["{apiRoot}/capif-events/"] --> SubId["/{subscriberId}"] + SubId --> Subs["/subscriptions"] + Subs --> SubId2["/{subscriptionId}"] + +``` + +A hierarchical diagram showing the resource URI structure for the CAPIF\_Events\_API. The root is {apiRoot}/capif-events/. A line descends from this root to a branch labeled /{subscriberId}. From /{subscriberId}, a line descends to a rounded rectangular box containing /subscriptions. From this box, a line descends to another rounded rectangular box containing /{subscriptionId}. + +**Figure 8.3.2.1-1: Resource URI structure of the CAPIF\_Events\_API** + +Table 8.3.2.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 8.3.2.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|--------------------------------------|------------------------------------------------|---------------------------------|---------------------------------------------------------------------------------| +| CAPIF Events Subscriptions | /{subscriberId}/subscriptions | POST | Creates a new individual CAPIF Event Subscription | +| Individual CAPIF Events Subscription | /{subscriberId}/subscriptions/{subscriptionId} | DELETE | Deletes an individual CAPIF Event Subscription identified by the subscriptionId | + +### 8.3.2.2 Resource: CAPIF Events Subscriptions + +#### 8.3.2.2.1 Description + +The CAPIF Events Subscriptions resource represents all subscriptions of aSubscriber. + +#### 8.3.2.2.2 Resource Definition + +Resource URI: {apiRoot}/capif-events//{subscriberId}/subscriptions + +This resource shall support the resource URI variables defined in table 8.3.2.2.2-1. + +**Table 8.3.2.2.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|--------------|-----------|----------------------| +| apiRoot | string | See clause 7.5 | +| subscriberId | string | ID of the Subscriber | + +#### 8.3.2.2.3 Resource Standard Methods + +##### 8.3.2.2.3.1 POST + +This method shall support the URI query parameters specified in table 8.3.2.2.3.1-1. + +**Table 8.3.2.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.3.2.2.3.1-2 and the response data structures and response codes specified in table 8.3.2.2.3.1-3. + +**Table 8.3.2.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-------------------|---|-------------|-------------------------------------------------------------| +| EventSubscription | M | 1 | Create a new individual CAPIF Events Subscription resource. | + +**Table 8.3.2.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| EventSubscription | M | 1 | 201
Created | CAPIF Events Subscription resource created successfully.
The URI of the created resource shall be returned in the "Location" HTTP header | +| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. | | | | | + +**Table 8.3.2.2.3.1-4: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/capif-events//{subscriberId}/subscriptions/{subscriptionId} | + +#### 8.3.2.2.4 Resource Custom Operations + +None. + +#### 8.3.2.3 Resource: Individual CAPIF Events Subscription + +##### 8.3.2.3.1 Description + +The Individual CAPIF Events Subscription resource represents an individual event subscription of aSubscriber. + +##### 8.3.2.3.2 Resource Definition + +Resource URI: {apiRoot}/capif-events//{subscriberId}/subscriptions/{subscriptionId} + +This resource shall support the resource URI variables defined in table 8.3.2.3.2-1. + +**Table 8.3.2.3.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|----------------|-----------|----------------------------------------------| +| apiRoot | string | See clause 7.5 | +| subscriberId | string | ID of the Subscriber | +| subscriptionId | string | Identifies an individual Events Subscription | + +##### 8.3.2.3.3 Resource Standard Methods + +###### 8.3.2.3.3.1 DELETE + +This method shall support the URI query parameters specified in table 8.3.2.3.3.1-1. + +**Table 8.3.2.3.3.1-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.3.2.3.3.1-2 and the response data structures and response codes specified in table 8.3.2.3.3.1-3. + +**Table 8.3.2.3.3.1-2: Data structures supported by the DELETE Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.3.2.3.3.1-3: Data structures supported by the DELETE Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | The individual CAPIF Events Subscription matching the subscriptionId is deleted. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.3.2.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.3.2.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +### 8.3.2.3.3.2 PUT + +The PUT method is used to update an existing subscription resource. + +The subscribing entity shall initiate the HTTP PUT request message and the CAPIF core function shall respond to the message. + +This method shall support the request data structures specified in table 8.3.2.3.3.2-1 and the response data structures and response codes specified in table 8.3.2.3.3.2-2. + +**Table 8.3.2.3.3.2-1: Data structures supported by the PUT Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-------------------|---|-------------|----------------------------------------------------------------------------------------------------| +| EventSubscription | M | 1 | Contains the updated representation of the existing individual CAPIF Events Subscription resource. | + +**Table 8.3.2.3.3.2-2: Data structures supported by the PUT Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EventSubscription | M | 1 | 200 OK | The event subscription was successfully updated, and a representation of the updated resource is returned. | +| N/A | | | 204 No Content | The event subscription was successfully updated and no content is returned in the response body. | +| N/A | | | 307 Temporary Redirect | Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------|--|--|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | +| N/A | | | 308
Permanent Redirect | Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | +| NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. | | | | | + +**Table 8.3.2.3.3.2-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.3.2.3.3.2-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +### 8.3.2.3.3.3 PATCH + +The PATCH method allows to modify an existing subscription. + +The subscribing entity shall initiate the HTTP PATCH request message and the CAPIF core function shall respond to the message. + +This method shall support the request data structures specified in table 8.3.2.3.3.3-1 and the response data structures and response codes specified in table 8.3.2.3.3.3-2. + +**Table 8.3.2.3.3.3-1: Data structures supported by the PATCH Request Body on this resource** + +| Data type | P | Cardinality | Description | +|------------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------| +| EventSubscriptionPatch | M | 1 | Contains the parameters to request the modification of the existing individual CAPIF Events Subscription resource. | + +**Table 8.3.2.3.3.3-2: Data structures supported by the PATCH Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EventSubscription | M | 1 | 200 OK | The subscription was successfully modified and a representation of the updated resource is returned in the response body. | +| N/A | | | 204 No Content | The subscription was successfully modified and no content was returned in the response body. | +| N/A | | | 307 Temporary Redirect | Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | +| N/A | | | 308 Permanent Redirect | Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------|--|--|--|---------------------------------------------------------------------------------------------| +| | | | | core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | +| NOTE: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. | | | | | + +**Table 8.3.2.3.3.3-3: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.3.2.3.3.3-4: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +### 8.3.2.3.4 Resource Custom Operations + +None. + +## 8.3.2A Custom Operations without associated resources + +There are no custom operations without associated resources defined for this API in this release of the specification. + +## 8.3.3 Notifications + +### 8.3.3.1 General + +The delivery of notifications shall conform to clause 7.6. + +**Table 8.3.3.1-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|--------------------|---------------------------|---------------------------------|--------------------------------------| +| Event notification | {notificationDestination} | POST | Notifies Subscriber of a CAPIF Event | + +### 8.3.3.2 Event Notification + +#### 8.3.3.2.1 Description + +Event Notification is used by the CAPIF core function to notify a Subscriber of an Event. The Subscriber shall be subscribed to such Event Notification via the Individual CAPIF Events Subscription Resource. + +#### 8.3.3.2.2 Notification definition + +The POST method shall be used for Event notification and the URI shall be the one provided by the Subscriber during the subscription to the event. + +Callback URI: {notificationDestination} + +This method shall support the URI query parameters specified in table 8.3.3.2.2.1-1. + +**Table 8.3.3.2.2-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.3.3.2.2-2 and the response data structures and response codes specified in table 8.3.3.2.2-3. + +**Table 8.3.3.2.2-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-------------------|---|-------------|-------------------------------------------| +| EventNotification | M | 1 | Notification information of a CAPIF Event | + +**Table 8.3.3.2.2-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | The receipt of the Notification is acknowledged. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative notification destination where the notification should be sent.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative notification destination where the notification should be sent.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.3.3.2.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative notification destination towards which the notification should be redirected. | + +**Table 8.3.3.2.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative notification destination towards which the notification should be redirected. | + +## 8.3.4 Data Model + +### 8.3.4.1 General + +This clause specifies the application data model supported by the API. Data types listed in clause 7.2 also apply to this API. + +Table 8.3.4.1-1 specifies the data types defined specifically for the CAPIF\_Events\_API service. + +**Table 8.3.4.1-1: CAPIF\_Events\_API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|----------------------------|------------------|-----------------------------------------------------------------|-----------------------| +| AccessControlPolicyListExt | Clause 8.3.4.2.6 | Represents the extension for access control policies. | | +| CAPIFEvent | Clause 8.3.4.3.2 | Describes the CAPIF event. | | +| CAPIFEventDetail | Clause 8.3.4.2.5 | Represents the CAPIF event detail. | Enhanced_event_report | +| CAPIFEventFilter | Clause 8.3.4.2.4 | Represents the CAPIF event filter. | Enhanced_event_report | +| EventNotification | Clause 8.3.4.2.3 | Represents an individual CAPIF Event Subscription Notification. | | +| EventSubscription | Clause 8.3.4.2.2 | Represents an individual CAPIF Event Subscription resource. | | +| TopologyHiding | Clause 8.3.4.2.7 | Represents the routing rules information of a service API. | | + +Table 8.3.4.1-2 specifies data types re-used by the CAPIF\_Events\_API service: + +**Table 8.3.4.1-2: Re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|----------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| ReportingInformation | 3GPP TS 29.523 [26] | Used to indicate the reporting requirement, only the following information are applicable for CAPIF:
  • - immRep
  • - notifMethod
  • - maxReportNbr
  • - monDur
  • - repPeriod
| Enhanced_event_report | +| SupportedFeatures | 3GPP TS 29.571 [19] | Used to negotiate the applicability of optional features defined in table 8.3.6-1. | | + +## 8.3.4.2 Structured data types + +### 8.3.4.2.1 Introduction + +This clause defines the structures to be used in resource representations. + +## 8.3.4.2.2 Type: EventSubscription + +Table 8.3.4.2.2-1: Definition of type EventSubscription + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------------|-------------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| events | array(CAPIFEvent) | M | 1..N | Subscribed events | | +| eventFilters | array(CAPIFEventFilter) | O | 1..N | Subscribed event filters.
The n th entry in the "eventFilters" attribute shall correspond to the n th entry in the "events" attribute. For event not having event filter, an empty event filter entry without any sub-attribute shall be provided. | Enhanced_event_report | +| eventReq | ReportingInformation | O | 0..1 | Represents the reporting requirements of the event subscription. | Enhanced_event_report | +| notificationDestination | Uri | M | 1 | URI where the notification should be delivered to. | | +| requestTestNotification | boolean | O | 0..1 | Set to "true" by Subscriber to request the CAPIF core function to send a test notification as defined in clause 7.6. Set to "false" not request the CAPIF core function to send a test notification. Default value is "false" if omitted. | Notification_test_event | +| websocketNotifConfig | WebsocketNotifConfig | O | 0..1 | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 7.6. | Notification_websocket | +| supportedFeatures | SupportedFeatures | C | 0..1 | Used to negotiate the supported optional features of the API as described in clause 7.8.
This attribute shall be provided in the HTTP POST request and in the response of successful resource creation. | | + +## 8.3.4.2.3 Type: EventNotification + +Table 8.3.4.2.3-1: Definition of type EventNotification + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|------------------|---|-------------|----------------------------------------------------------------------------------------------------------|-----------------------| +| subscriptionId | string | M | 1 | Identifier of the subscription resource to which the notification is related – CAPIF resource identifier | | +| events | CAPIFEvent | M | 1 | Notifications of individual events | | +| eventDetail | CAPIFEventDetail | C | 0..1 | Detailed information for the event.
(NOTE) | Enhanced_event_report | + +**NOTE:** Within the CAPIFEventDetail data type, the "serviceAPIDescriptions" attribute shall be provided if the event is SERVICE\_API\_UPDATE, the "apiIds" attribute shall be provided if the event is SERVICE\_API\_AVAILABLE, SERVICE\_API\_UNAVAILABLE, the "apiInvokerIds" attribute shall be provided only if the event is API\_INVOKER\_ONBOARDED or API\_INVOKER\_OFFBOARDED, or API\_INVOKER\_UPDATED, the "accCtrlPolList" attribute shall be provided if the event is ACCESS\_CONTROL\_POLICY\_UPDATE, the "invocationLogs" attribute shall be provided if the event is SERVICE\_API\_INVOCATION\_SUCCESS or SERVICE\_API\_INVOCATION\_FAILURE, the "apiTopoHide" attribute shall be provided if the event is API\_TOPOLOGY HIDING\_CREATED or API\_TOPOLOGY HIDING\_REVOKED. + +## 8.3.4.2.4 Type: CAPIEventFilter + +**Table 8.3.4.2.4-1: Definition of type CAPIEventFilter** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|---------------|---|-------------|----------------------------------------------------------------------------------|---------------| +| apiIds | array(string) | O | 1..N | API identifiers that the event subscriber wants to know in the interested event. | | +| apiInvokerIds | array(string) | O | 1..N | API invokers that the event subscriber wants to know in the interested event. | | +| aefIds | array(string) | O | 1..N | String identifying the AEF. | | + +## 8.3.4.2.5 Type: CAPIEventDetail + +**Table 8.3.4.2.5-1: Definition of type CAPIEventDetail** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------------|------------------------------|---|-------------|---------------------------------------------------------|---------------| +| serviceAPIDescriptions | array(ServiceAPIDescription) | O | 1..N | Description of the service API as published by the APF. | | +| apiIds | array(string) | O | 1..N | API identifiers. | | +| apiInvokerIds | array(string) | O | 1..N | API invokers that are onboarded/offboarded. | | +| accCtrlPolList | AccessControlPolicyListExt | O | 0..1 | Access control policy updated list. | | +| invocationLogs | array(InvocationLog) | O | 1..N | Invocation logs | | +| apiTopoHide | TopologyHiding | O | 0..1 | Topology hiding information for a service API | | + +## 8.3.4.2.6 Type: AccessControlPolicyListExt + +**Table 8.3.4.2.6-1: Definition of type AccessControlPolicyListExt** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------------------------------------------------------------------------------------------|-----------|---|-------------|-------------------------------|---------------| +| apiId | string | M | 1 | Identifier of the service API | | +| NOTE: This data type also contains all the properties defined for AccessControlPolicyList data type. | | | | | | + +## 8.3.4.2.7 Type: TopologyHiding + +**Table 8.3.4.2.7-1: Definition of type TopologyHiding** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|--------------------|---|-------------|-------------------------------|---------------| +| apiId | string | M | 1 | Identifier of the service API | | +| routingRules | array(RoutingRule) | M | 1..N | Routing rules | | + +### 8.3.4.2.8 Type: EventSubscriptionPatch + +**Table 8.3.4.2.8-1: Definition of type EventSubscriptionPatch** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------------------|----------------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| events | array(CAP
IFEEvent) | O | 1..N | Subscribed events (NOTE). | | +| eventFilters | array(CAP
IFEEventFilt
er) | O | 1..N | Subscribed event filters.
The n th entry in the "eventFilters" attribute shall correspond to the n th entry in the "events" attribute. For event not having event filter, an empty event filter entry without any sub-attribute shall be provided (NOTE). | | +| eventReq | ReportingI
nformation | O | 0..1 | Represents the reporting requirements of the event subscription (NOTE). | | +| notificationDesti
nation | Uri | O | 0..1 | URI where the notification should be delivered to (NOTE). | | + +NOTE: At least one attribute shall be present. + +**Editor's Note:** Whether the list of subscribed events can be updated is FFS. + +### 8.3.4.3 Simple data types and enumerations + +#### 8.3.4.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +#### 8.3.4.3.2 Simple data types + +None. + +The simple data types defined in table 8.3.4.3.2-1 shall be supported. + +**Table 8.3.4.3.2-1: Simple data types** + +| Type Name | Type Definition | Description | Applicability | +|-----------|-----------------|-------------|---------------| +| n/a | | | | + +### 8.3.4.3.3 Enumeration: CAPIFEvent + +**Table 8.3.4.3.3-1: Enumeration CAPIFEvent** + +| Enumeration value | Description | Applicability | +|-------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|---------------| +| SERVICE_API_AVAILABLE | Events related to the availability of service APIs after the service APIs are published. | | +| SERVICE_API_UNAVAILABLE | Events related to the unavailability of service APIs after the service APIs are unpublished. | | +| SERVICE_API_UPDATE | Events related to change in service API information | | +| API_INVOKER_ONBOARDED | Events related to API invoker onboarded to CAPIF | | +| API_INVOKER_OFFBOARDED | Events related to API invoker offboarded from CAPIF | | +| SERVICE_API_INVOCATION_SUCCESS | Events related to the successful invocation of service APIs | | +| SERVICE_API_INVOCATION_FAILURE | Events related to the failed invocation of service APIs | | +| ACCESS_CONTROL_POLICY_UPDATE | Events related to the update for the access control policy related to the service APIs | | +| ACCESS_CONTROL_POLICY_UNAVAILABLE | Events related to the unavailability of the access control policy related to the service APIs (NOTE) | | +| API_INVOKER_AUTHORIZATION_REVOKED | Events related to the revocation of the authorization of API invokers to access the service APIs. (NOTE) | | +| API_INVOKER_UPDATED | Events related to API invoker profile updated to CAPIF. | | +| API_TOPOLOGY HIDING_CREATED | Events related to the creation or update of the API topology hiding information of the service API after the service APIs are published | | +| API_TOPOLOGY HIDING_REVOKED | Events related to the revocation of the API topology information of the service API after the service APIs are unpublished | | +| NOTE: The present release does not specify further details (e.g. event filters) for this event. | | | + +## 8.3.5 Error Handling + +### 8.3.5.1 General + +HTTP error handling shall be supported as specified in clause 7.7. + +In addition, the requirements in the following clauses shall apply. + +### 8.3.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the CAPIF\_Events\_API. + +### 8.3.5.3 Application Errors + +The application errors defined for the CAPIF\_Events\_API are listed in table 8.3.5.3-1. + +**Table 8.3.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 8.3.6 Feature negotiation + +General feature negotiation procedures are defined in clause 7.8. Table 8.3.6-1 lists the supported features for CAPIF\_Events\_API. + +**Table 8.3.6-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Notification_test_event | Testing of notification connection is supported according to clause 7.6. | +| 2 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 7.6. This feature requires that the Notification_test_event feature is also supported. | +| 3 | Enhanced_event_report | This feature supports the enhanced event report including event reporting requirement and event reporting details as defined in clause 5.4.2.2.2. | +| 4 | ApiStatusMonitoring | Indicates the support of the API status monitoring in CAPIF layer as a part of enhancement of SEAL framework.

This feature enables the following functionality:
- enhancement of the CAPIF event notification. | + +## 8.4 CAPIF\_API\_Invoker\_Management\_API + +### 8.4.1 API URI + +The CAPIF\_API\_Invoker\_Management\_API service shall use the CAPIF\_API\_Invoker\_Management\_API. + +The request URIs used in HTTP requests from the API invoker towards the CAPIF core function shall have the Resource URI structure as defined in clause 7.5 with the following clarifications: + +- The shall be "api-invoker-management". +- The shall be "v1". +- The shall be set as described in clause 8.4.2. + +All the resource URIs and the custom operation URIs specified in the clauses below are defined relative to the above API URI. + +### 8.4.2 Resources + +#### 8.4.2.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 8.4.2.1-1 depicts the resource URIs structure for the CAPIF\_API\_Invoker\_Management\_API. + +![Diagram showing the resource URI structure. A root URI '{apiRoot}/api-invoker-management/' has a line pointing to a box containing '/onboardedInvokers'. From this box, another line points to a second box containing '/{onboardingId}'.](c07e21a8d65991db04263322f859c94f_img.jpg) + +{apiRoot}/api-invoker-management/ + +``` + +graph TD + Root["{apiRoot}/api-invoker-management/"] --> Box1["/onboardedInvokers"] + Box1 --> Box2["/{onboardingId}"] + +``` + +Diagram showing the resource URI structure. A root URI '{apiRoot}/api-invoker-management/' has a line pointing to a box containing '/onboardedInvokers'. From this box, another line points to a second box containing '/{onboardingId}'. + +**Figure 8.4.2.1-1: Resource URI structure of the CAPIF\_API\_Invoker\_Management\_API** + +Table 8.4.2.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 8.4.2.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|-----------------------------------|---------------------------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------| +| On-boarded API Invokers | /onboardedInvokers
(NOTE) | POST | On-boards a new API invoker by creating an API invoker profile | +| Individual On-boarded API Invoker | /onboardedInvokers/{onboardingId}
(NOTE) | DELETE | Off-boards an individual API invoker by deleting the associated API invoker profile identified by {onboardingId} | +| | | PATCH | Modifies the API invoker details of an individual API invoker identified by the {onboardingId} | +| | | PUT | Updates the API invoker details of an individual API invoker identified by the {onboardingId} | + +NOTE: The path segment "onboardedInvokers" does not follow the related naming convention defined in subclause 7.5.1. The path segment is however kept as currently defined in this specification for backward compatibility considerations. + +## 8.4.2.2 Resource: On-boarded API invokers + +### 8.4.2.2.1 Description + +The On-boarded API Invokers resource represents all the API invokers that are on-boarded at a given CAPIF core function. + +### 8.4.2.2.2 Resource Definition + +Resource URI: {apiRoot}/api-invoker-management//onboardedInvokers + +This resource shall support the resource URI variables defined in table 8.4.2.2.2-1. + +**Table 8.4.2.2.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|---------|-----------|----------------| +| apiRoot | string | See clause 7.5 | + +### 8.4.2.2.3 Resource Standard Methods + +#### 8.4.2.2.3.1 POST + +This method shall support the URI query parameters specified in table 8.4.2.2.3.1-1. + +**Table 8.4.2.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.4.2.2.3.1-2 and the response data structures and response codes specified in table 8.4.2.2.3.1-3. + +**Table 8.4.2.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APIInvokerEnrolmentDetails | M | 1 | Enrolment details of the API invoker including notification destination URI for any on-boarding related notifications and an optional list of APIs the API invoker intends to invoke while on-board. | + +**Table 8.4.2.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------------------|---|-------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APIInvokerEnrolmentDetails | M | 1 | 201
Created | API invoker on-boarded successfully

The URI of the created resource shall be returned in the "Location" HTTP header. A list of APIs the API invoker is allowed to invoke while on-board may also be included as part of the APIInvokerEnrolmentDetails which is provided in the response body, if requested in the POST request. | +| n/a | | | 202
Accepted | The CAPIF core has accepted the Onboarding request and is processing it. When processing is completed, the CAPIF core function will send a Notify_Onboarding_Completion notification to the requesting API invoker. See clause 8.4.3.2. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.4.2.2.3.1-4: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/api-invoker-management//onboardedInvokers/{onboardingId} | + +### 8.4.2.2.4 Resource Custom Operations + +None. + +## 8.4.2.3 Resource: Individual On-boarded API Invoker + +### 8.4.2.3.1 Description + +The Individual On-boarded API Invokers resource represents an individual API invoker that is on-boarded at a given CAPIF core function. + +### 8.4.2.3.2 Resource Definition + +Resource URI: {apiRoot}/api-invoker-management//onboardedInvokers/{onboardingId} + +This resource shall support the resource URI variables defined in table 8.4.2.3.2-1. + +**Table 8.4.2.3.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|--------------|-----------|------------------------------------------------------------------| +| apiRoot | string | See clause 7.5 | +| onboardingId | string | String identifying an individual on-boarded API invoker resource | + +### 8.4.2.3.3 Resource Standard Methods + +#### 8.4.2.3.3.1 DELETE + +This method shall support the URI query parameters specified in table 8.4.2.3.3.1-1. + +**Table 8.4.2.3.3.1-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the response codes specified in table 8.4.2.3.3.1-2 and the response data structures and response codes specified in table 8.4.2.3.3.1-3. + +**Table 8.4.2.3.3.1-2: Data structures supported by the DELETE Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.4.2.3.3.1-3: Data structures supported by the DELETE Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | The individual on-boarded API invoker matching the onboardingId is deleted | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.4.2.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.4.2.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.4.2.3.3.2 PUT + +The PUT method allows updating the API invoker details of the onboarded API invoker. This method shall support the URI query parameters specified in table 8.4.2.3.3.2-1. + +**Table 8.4.2.3.3.2-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in the table 8.4.2.3.3.2-2 and the response data structures and response codes specified in the table 8.4.2.3.3.2-3. + +**Table 8.4.2.3.3.2-2: Data structures supported by the PUT Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------| +| APIInvokerEnrollmentDetails | M | 1 | Updated details of the API invoker and a notification destination URI for any update request related notifications. | + +**Table 8.4.2.3.3.2-3: Data structures supported by the PUT Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APIInvokerEnrolmentDetails | M | 1 | 200 OK | API invoker's information updated successfully.

Updated details of the API invoker as part of the APIInvokerEnrolmentDetails, which is provided in the response body. | +| n/a | | | 202 Accepted | The CAPIF core has accepted the Update details request and is processing it. When processing is completed, the CAPIF core function will send a Notify_Update_Completion notification to the requesting API invoker. See clause 8.4.3.3. | +| n/a | | | 204 No Content | API invoker's information updated successfully, with no content to be sent in the response body. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.4.2.3.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.4.2.3.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.4.2.3.3.3 PATCH + +This method shall support the URI query parameters specified in table 8.4.2.3.3.3-1. + +**Table 8.4.2.3.3.3-1: URI query parameters supported by the PATCH method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.4.2.3.3.3-2 and the response data structures and response codes specified in table 8.4.2.3.3.3-3. + +**Table 8.4.2.3.3.3-2: Data structures supported by the PATCH Request Body on this resource** + +| Data type | P | Cardinality | Description | +|---------------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------| +| APIInvokerEnrolmentDetailsPatch | M | 1 | Modified details of the API invoker and a notification destination URI for any modify request related notifications. | + +**Table 8.4.2.3.3.3-3: Data structures supported by the PATCH Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APIInvokerEnrolmentDetails | M | 1 | 200 OK | API invoker's information modified successfully.

Modified details of the API invoker as part of the APIInvokerEnrolmentDetails, which is provided in the response body. | +| n/a | | | 202 Accepted | The CAPIF core has accepted the modify details request and is processing it. When processing is completed, the CAPIF core function will send a Notify_Update_Completion notification to the requesting API invoker. See sub clause 8.4.3.3. | +| n/a | | | 204 No Content | API invoker's information modified successfully, with no content to be sent in the response body. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the HTTP PATCH method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.4.2.3.3.3-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | String | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.4.2.3.3.3-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | String | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.4.2.3.4 Resource Custom Operations + +None. + +### 8.4.2A Custom Operations without associated resources + +There are no custom operations without associated resources defined for this API in this release of the specification. + +## 8.4.3 Notifications + +### 8.4.3.1 General + +The delivery of notifications shall conform to clause 7.6. + +**Table 8.4.3.1-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|------------------------------|---------------------------|---------------------------------|----------------------------------------------| +| Notify_Onboarding_Completion | {notificationDestination} | POST | Notify API invoker of on-boarding result | +| Notify_Update_Completion | {notificationDestination} | POST | Notify API invoker of update result details. | + +### 8.4.3.2 Notify\_Onboarding\_Completion + +#### 8.4.3.2.1 Description + +Notify\_Onboarding\_Completion is used by the CAPIF core function to notify an API invoker of the on-boarding result. + +#### 8.4.3.2.2 Notification definition + +The POST method shall be used for Notify\_Onboarding\_Completion and the URI shall be the one provided by the API invoker during the on-boarding request. + +Callback URI: {notificationDestination} + +This method shall support the URI query parameters specified in table 8.4.3.2.2-1. + +**Table 8.4.3.2.2-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.4.3.2.2-2 and the response data structures and response codes specified in table 8.4.3.2.2-3. + +**Table 8.4.3.2.2-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|------------------------|---|-------------|--------------------------------------| +| OnboardingNotification | M | 1 | Notification with on-boarding result | + +**Table 8.4.3.2.2-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | The receipt of the Notification is acknowledged. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative notification destination where the notification should be sent.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative notification destination where the notification should be sent.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.4.3.2.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative notification destination towards which the notification should be redirected. | + +**Table 8.4.3.2.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative notification destination towards which the notification should be redirected. | + +### 8.4.3.3 Notify\_Update\_Completion + +#### 8.4.3.3.1 Description + +Notify\_Update\_Completion is used by the CAPIF core function to notify of the update of API Invoker's details result. + +#### 8.4.3.3.2 Notification definition + +The POST method shall be used for Notify\_Update\_Completion and the URI shall be the one provided by the API invoker during the API invoker details update request. + +Callback URI: {notificationDestination} + +This method shall support the URI query parameters specified in table 8.4.3.3.2-1. + +**Table 8.4.3.3.2-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.4.3.3.2-2 and the response data structures and response codes specified in table 8.4.3.3.2-3. + +**Table 8.4.3.3.2-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|------------------------|---|-------------|--------------------------------------------------------| +| OnboardingNotification | M | 1 | Notification with API Invoker's details update result. | + +**Table 8.4.3.3.2-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | The receipt of the Notification is acknowledged. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative notification destination where the notification should be sent.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative notification destination where the notification should be sent.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.4.3.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative notification destination towards which the notification should be redirected. | + +**Table 8.4.3.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative notification destination towards which the notification should be redirected. | + +## 8.4.4 Data Model + +### 8.4.4.1 General + +This clause specifies the application data model supported by the API. Data types listed in clause 7.2 also apply to this API. + +Table 8.4.4.1-1 specifies the data types defined specifically for the CAPIF\_API\_Invoker\_Management\_API service. + +**Table 8.4.4.1-1: CAPIF\_API\_Invoker\_Management\_API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|---------------------------------|------------------------|-------------------------------------------------------------------------|----------------------| +| APIInvokerEnrolmentDetails | Clause 8.4.4.2.2 | Represents information about the API Invoker that requested to onboard. | | +| APIInvokerEnrolmentDetailsPatch | Clause 8.4.4.2.8 | Represents an API Invoker's enrolment details to be updated. | PatchUpdate | +| APIList | Clause 8.4.4.2.4 | The list of service APIs that the API Invoker is allowed to invoke. | | +| OnboardingInformation | Clause 8.4.4.2.5 | Represents on-boarding information of the API invoker. | | +| OnboardingNotification | Clause 8.4.4.2.7 | Represents the notification with on-boarding or update result. | | + +Table 8.4.4.1-2 specifies data types re-used by the CAPIF\_API\_Invoker\_Management\_API service. + +**Table 8.4.4.1-2: Re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|------------------------------------------------------------------------------------|----------------------| +| SupportedFeatures | 3GPP TS 29.571 [19] | Used to negotiate the applicability of optional features defined in table 8.4.6-1. | | + +## 8.4.4.2 Structured data types + +### 8.4.4.2.1 Introduction + +### 8.4.4.2.2 Type: APIInvokerEnrolmentDetails + +**Table 8.4.4.2.2-1: Definition of type APIInvokerEnrolmentDetails** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------------|-----------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| apiInvokerId | string | O | 0..1 | API invoker ID assigned by the CAPIF core function to the API invoker while on-boarding the API invoker. Shall not be present in the HTTP POST request from the API invoker to the CAPIF core function, to on-board itself. Shall be present in all other HTTP requests and responses. | | +| onboardingInformation | OnboardingInformation | M | 1 | On-boarding information about the API invoker necessary for the CAPIF core function to on-board the API invoker. | | +| notificationDestination | Uri | M | 1 | URI where the notification should be delivered to. | | +| requestTestNotification | boolean | O | 0..1 | CAPIF core function to send a test notification as defined in in clause 7.6. Set to "false" to request the CAPIF core function not to send a test notification.Default value is "false" if omitted. | Notification_test_event | +| websocketNotifConfig | WebsockNotifConfig | O | 0..1 | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 7.6. | Notification_websocket | +| apiList | APIList | O | 0..1 | A list of APIs. When included by the API invoker in the HTTP request message, it lists the APIs that the API invoker intends to invoke while onboard or API invoker update. When included by the CAPIF core function in the HTTP response message, it lists the APIs that the API invoker is allowed to invoke while onboard or API invoker update. | | +| apiInvokerInformation | string | O | 0..1 | Generic information related to the API invoker such as details of the device or the application. | | +| supportedFeatures | SupportedFeatures | C | 0..1 | Used to negotiate the supported optional features of the API as described in clause 7.8.
This attribute shall be provided in the HTTP POST request and in the response of successful resource creation. | | + +### 8.4.4.2.3 Type: Void + +### 8.4.4.2.4 Type: APIList + +**Table 8.4.4.2.4-1: Definition of type APIList** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------------|------------------------------|---|-------------|--------------------------------|---------------| +| serviceAPIDescriptions | array(ServiceAPIDescription) | O | 1..N | Definition of the service API. | | + +## 8.4.4.2.5 Type: OnboardingInformation + +Table 8.4.4.2.5-1: Definition of type OnboardingInformation + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| apiInvokerPublicKey | string | M | 1 | Public Key of API Invoker | | +| apiInvokerCertificate | string | O | 0..1 | API invoker's generic client certificate. The subject field in the certificate shall be encoded with API invoker ID as Common Name as specified in IETF RFC 5280 [29]. | | +| onboardingSecret | string | O | 0..1 | API invoker's onboarding secret, provided by the CAPIF core function. | | + +## 8.4.4.2.6 Type: Void + +## 8.4.4.2.7 Type: OnboardingNotification + +Table 8.4.4.2.7-1: Definition of type OnboardingNotification + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------------------|----------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| result | boolean | M | 1 | Set to "true" indicate successful onboarding. Set to "false" indicate unsuccessful onboarding. Default value is "false" if omitted. | | +| resourceLocation | Uri | C | 0..1 | URI pointing to the new CAPIF resource created as a result of successful onboarding. This attribute shall be present if 'result' attribute is set to "true". Otherwise it shall not be present. | | +| apiInvokerEnrolmentDetails | APIInvokerEnrolmentDetails | C | 0..1 | Enrolment details of the API invoker which are verified by the CAPIF administrator or API management. This attribute shall be present if 'result' attribute is set to "true". Otherwise it shall not be present. | | +| apiList | APIList | O | 0..1 | List of APIs API invoker is allowed to access. This attribute may be present if 'result' attribute is set to "true". Otherwise it shall not be present. | | + +## 8.4.4.2.8 Type: APIInvokerEnrolmentDetailsPatch + +Table 8.4.4.2.8-1: Definition of type APIInvokerEnrolmentDetailsPatch + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------------|-----------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| onboardingInformation | OnboardingInformation | O | 0..1 | On-boarding information about the API invoker necessary for the CAPIF core function to on-board the API invoker. | | +| notificationDestination | Uri | O | 0..1 | URI where the notification should be delivered to. | | +| apiList | APIList | O | 0..1 | A list of APIs. When included by the API invoker in the HTTP request message, it lists the APIs that the API invoker intends to invoke while onboard or API invoker update. | | +| apiInvokerInformation | string | O | 0..1 | Generic information related to the API invoker such as details of the device or the application. | | + +#### 8.4.4.3 Simple data types and enumerations + +None. + +### 8.4.5 Error Handling + +#### 8.4.5.1 General + +HTTP error handling shall be supported as specified in clause 7.7. + +In addition, the requirements in the following clauses shall apply. + +#### 8.4.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the CAPIF\_API\_Invoker\_Management\_API. + +#### 8.4.5.3 Application Errors + +The application errors defined for the CAPIF\_API\_Invoker\_Management\_API are listed in table 8.4.5.3-1. + +**Table 8.4.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +### 8.4.6 Feature negotiation + +General feature negotiation procedures are defined in clause 7.8. Table 8.4.6-1 lists the supported features for CAPIF\_API\_Invoker\_Management\_API. + +**Table 8.4.6-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Notification_test_event | Testing of notification connection is supported according to clause 7.6. | +| 2 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 7.6. This feature requires that the Notification_test_event feature is also supported. | +| 3 | PatchUpdate | Indicates the support of the PATCH method for updating an On-boarded API Invoker resource. | + +## 8.5 CAPIF\_Security\_API + +### 8.5.1 API URI + +The CAPIF\_Security\_API service shall use the CAPIF\_Security\_API. + +The request URIs used in HTTP requests from the API invoker or the API exposing function towards the CAPIF core function shall have the Resource URI structure as defined in clause 7.5 with the following clarifications: + +- The shall be "capif-security". +- The shall be "v1". + +- The shall be set as described in clause 8.5.2. + +All the resource URIs and the custom operation URIs specified in the clauses below are defined relative to the above API URI. + +## 8.5.2 Resources + +### 8.5.2.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 8.5.2.1-1 depicts the resource URIs structure for the CAPIF\_Security\_API. + +![Resource URI structure of the CAPIF_Security_API diagram](896f6ec457b6252d4af32a634299218c_img.jpg) + +``` +graph TD; Root["{apiRoot}/capif-security/{apiVersion}"] --- T["/trustedInvokers"]; Root --- S["/securities/{securityId}"]; T --- Id["/{apiInvokerId}"]; Id --- Update["/update"]; Id --- Delete["/delete"]; S --- Token["/token"]; +``` + +The diagram illustrates the hierarchical structure of resource URIs for the CAPIF\_Security\_API. It starts with a root path: {apiRoot}/capif-security/{apiVersion}. From this root, two main branches emerge: /trustedInvokers and /securities/{securityId}. The /trustedInvokers branch further leads to a specific invoker resource: /{apiInvokerId}, which in turn has two associated operations: /update and /delete. The /securities/{securityId} branch leads to a token resource: /token. + +Resource URI structure of the CAPIF\_Security\_API diagram + +**Figure 8.5.2.1-1: Resource URI structure of the CAPIF\_Security\_API** + +Table 8.5.2.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 8.5.2.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|--------------------------------|--------------------------------------------------|---------------------------------|-----------------------------------------------------------------------| +| Trusted API invokers | /trustedInvokers
(NOTE) | n/a | | +| Individual trusted API invoker | /trustedInvokers/{apiInvokerId}
(NOTE) | GET | Retrieve authentication information of an API invoker | +| | | PUT | Create a security context for individual API invoker | +| | | DELETE | Revoke the authorization of the API invoker | +| | /trustedInvokers/{apiInvokerId}/update
(NOTE) | update (POST) | Update the security context (e.g. re-negotiate the security methods). | +| | /trustedInvokers/{apiInvokerId}/delete
(NOTE) | delete (POST) | Revoke the authorization of the API invoker for some APIs | +| | /securities/{securityId}/token
(NOTE) | token (POST) | Obtain the OAuth 2.0 authorization information | + +NOTE: The path segment "trustedInvokers" does not follow the related naming convention defined in subclause 7.5.1. The path segment is however kept as currently defined in this specification for backward compatibility considerations. + +## 8.5.2.2 Resource: Trusted API invokers + +### 8.5.2.2.1 Description + +The Trusted API Invokers resource represents all the API invokers that are trusted by the CAPIF core function and have received authentication information from the CAPIF core function. + +### 8.5.2.2.2 Resource Definition + +Resource URI: {apiRoot}/capif-security//trustedInvokers + +This resource shall support the resource URI variables defined in table 8.5.2.2.2-1. + +**Table 8.5.2.2.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|---------|-----------|----------------| +| apiRoot | string | See clause 7.5 | + +### 8.5.2.2.3 Resource Standard Methods + +#### 8.5.2.2.3.1 Void + +### 8.5.2.2.4 Resource Custom Operations + +None. + +### 8.5.2.3 Resource: Individual trusted API invokers + +#### 8.5.2.3.1 Description + +The Individual trusted API Invokers resource represents an individual API invokers that is trusted by the CAPIF core function and have received security related information from the CAPIF core function. + +#### 8.5.2.3.2 Resource Definition + +Resource URI: {apiRoot}/capif-security//trustedInvokers/{apiInvokerId} + +This resource shall support the resource URI variables defined in table 8.5.2.3.2-1. + +**Table 8.5.2.3.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|--------------|-----------|--------------------------------------| +| apiRoot | string | See clause 7.5 | +| apiInvokerId | string | Identifies an individual API invoker | + +#### 8.5.2.3.3 Resource Standard Methods + +##### 8.5.2.3.3.1 GET + +This method shall support the URI query parameters specified in table 8.5.2.3.3.1-1. + +**Table 8.5.2.3.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | +|--------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| authenticationInfo | boolean | O | 0..1 | When set to "true", it indicates the CAPIF core function to send the authentication information of the API invoker. Set to "false" or omitted.
(NOTE) | +| authorizationInfo | boolean | O | 0..1 | When set to "true", it indicates the CAPIF core function to send the authorization information of the API invoker. Set to "false" indicates the CAPIF core function not to send the authorization information of the API invoker. Default value is "false" if omitted.
(NOTE) | + +NOTE: The query parameters "authenticationInfo" and "authorizationInfo" do not follow the related naming convention defined in subclause 7.5.1. These query parameters are however kept as currently defined in this specification for backward compatibility considerations. + +This method shall support the request data structures specified in table 8.5.2.3.3.1-2 and the response data structures and response codes specified in table 8.5.2.3.3.1-3. + +**Table 8.5.2.3.3.1-2: Data structures supported by the GET Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.5.2.3.3.1-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceSecurity | M | 1 | 200 OK | The security related information of the API Invoker based on the request from the API exposing function. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.5.2.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.5.2.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.5.2.3.3.2 DELETE + +This method shall support the URI query parameters specified in table 8.5.2.3.3.2-1. + +**Table 8.5.2.3.3.2-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.5.2.3.3.2-2 and the response data structures and response codes specified in table 8.5.2.3.3.2-3. + +**Table 8.5.2.3.3.2-2: Data structures supported by the DELETE Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.5.2.3.3.2-3: Data structures supported by the DELETE Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | Authorization of the API invoker revoked, and a notification is sent to the API invoker as specified in clause 8.5.3.2 | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.5.2.3.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.5.2.3.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.5.2.3.3.3 PUT + +This method shall support the URI query parameters specified in table 8.5.2.3.3.3-1. + +**Table 8.5.2.3.3.3-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.5.2.3.3.3-2 and the response data structures and response codes specified in table 8.5.2.3.3.3-3. + +**Table 8.5.2.3.3.3-2: Data structures supported by the PUT Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceSecurity | M | 1 | Security method request from the API invoker to the CAPIF core function. The request indicates a list of service APIs and a preferred method of security for the service APIs.

The request also includes a notification destination URI for security related notifications. | + +**Table 8.5.2.3.3.3-3: Data structures supported by the PUT Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|---------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceSecurity | M | 1 | 201
Created | Security method from the CAPIF core function to the API invoker is based on the received request. The response indicates the security method to be used for the service APIs

The URI of the created resource shall be returned in the "Location" HTTP header. | +| NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. | | | | | + +**Table 8.5.2.3.3.3-4: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/capif-security/v1/trustedInvokers/{apiInvokerId} | + +## 8.5.2.3.4 Resource Custom Operations + +### 8.5.2.3.4.1 Overview + +**Table 8.5.2.3.4.1-1: Custom operations** + +| Operation name | Custom operation URI | Mapped HTTP method | Description | +|----------------|----------------------------------------|--------------------|------------------------------------------------------------------------| +| update | /trustedInvokers/{apiInvokerId}/update | POST | Update the security instance (e.g. re-negotiate the security methods). | +| delete | /trustedInvokers/{apiInvokerId}/delete | POST | Revoke the authorization of the API invoker for some APIs | +| token | /securities/{securityId}/token | POST | Obtain the OAuth 2.0 authorization information | + +### 8.5.2.3.4.2 Operation: update + +#### 8.5.2.3.4.2.1 Description + +This custom operation updates an existing Individual security instance resource in the CAPIF core function. + +#### 8.5.2.3.4.2.2 Operation Definition + +This method shall support the URI query parameters specified in table 8.5.2.3.4.2.2-1. + +**Table 8.5.2.3.4.2.2-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This operation shall support the request data structures specified in table 8.5.2.3.4.2.2-2 and the response data structure and response codes specified in table 8.5.2.3.4.2.2-3. + +**Table 8.5.2.3.4.2.2-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceSecurity | M | 1 | Security method request from the API invoker to the CAPIF core function. The request indicates a list of service APIs and a preferred method of security for the service APIs.

The request also includes a notification destination URI for security related notifications. | + +**Table 8.5.2.3.4.2.2-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ServiceSecurity | M | 1 | 200 OK | Security method from the CAPIF core function to the API invoker is based on the received request. The response indicates the security method to be used for the service APIs | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during security instance modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during security instance modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.5.2.3.4.2.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.5.2.3.4.2.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +8.5.2.3.4.3 Operation: delete + +8.5.2.3.4.3.1 Description + +This custom operation revokes authorization for some service APIs of an existing Individual security instance resource in the CAPIF core function. + +8.5.2.3.4.3.2 Operation Definition + +This method shall support the URI query parameters specified in table 8.5.2.3.4.3.2-1. + +**Table 8.5.2.3.4.3.2-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This operation shall support the request data structures specified in table 8.5.2.3.4.3.2-2 and the response data structure and response codes specified in table 8.5.2.3.4.3.2-3. + +**Table 8.5.2.3.4.3.2-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------------|---|-------------|-------------------------------------------------------------------------------------------------------| +| SecurityNotification | M | 1 | It includes a list of API identifiers for which authorization needs to be revoked for an API invoker. | + +**Table 8.5.2.3.4.3.2-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | Successful case.
The CAPIF core function revoked the authorization of the API invoker for the requested APIs. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during authorization revocation.
The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during authorization revocation.
The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.5.2.3.4.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.5.2.3.4.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.5.2.3.4.4 Operation: token + +##### 8.5.2.3.4.4.1 Description + +This custom operation obtains OAuth 2.0 authorization information from an existing Individual security instance resource in the CAPIF core function. + +##### 8.5.2.3.4.4.2 Operation Definition + +This method shall support the URI query parameters specified in table 8.5.2.3.4.4.2-1. + +**Table 8.5.2.3.4.4.2-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This operation shall support the request data structures specified in table 8.5.2.3.4.4.2-2 and the response data structure and response codes specified in table 8.5.2.3.4.4.2-3. + +**Table 8.5.2.3.4.4.2-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------|---|-------------|-----------------------------------------------------------------------------| +| AccessTokenReq | M | 1 | This IE shall contain the request information for the access token request. | + +**Table 8.5.2.3.4.4.2-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AccessTokenRsp | M | 1 | 200 OK | This IE shall contain the access token response information. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during obtaining authorization information. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during obtaining authorization information. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| AccessTokenErr | M | 1 | 400 Bad Request | See IETF RFC 6749 [23] clause 5.2.
The specific error shall be indicated in the "error" attribute of the AccessTokenErr data type, containing any of the values:
- invalid_request
- invalid_client
- invalid_grant
- unauthorized_client
- unsupported_grant_type
- invalid_scope | +| AccessTokenErr | M | 1 | 401 Unauthorized | See IETF RFC 6749 [23] clause 5.2.
The specific error shall be indicated in the "error" attribute of the AccessTokenErr data type, containing value:
- invalid_client | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.5.2.3.4.4.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.5.2.3.4.4.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +## 8.5.2.3.4.5 Operation: code + +## 8.5.2.3.4.5.1 Description + +This custom operation obtains authorization code from an existing Individual security instance resource in the CAPIF core function. + +## 8.5.2.3.4.5.2 Operation Definition + +This method shall support the URI query parameters specified in table 8.5.2.3.4.5.2-1. + +**Table 8.5.2.3.4.5.2-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | +|-------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------| +| response-type | string | M | 1 | The response type shall be set as "code" as defined in clause 4.1.1 of IETF 6749 [23] | +| api-invoker-id | string | M | 1 | String identifying the API invoker as defined as client_id in clause 4.1.1 of IETF 6749 [23] | +| resource-owner-id | string | O | 0..1 | String identifying resource owner as defined in clause 6.5.3.3 of TS 33.122 [16] | + +This method shall support the request data structures specified in table 8.5.2.3.4.5.2-2 and the response data structures and response codes specified in table 8.5.2.3.4.5.2-3. + +**Table 8.5.2.3.4.5.2-2: Data structures supported by the GET Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.5.2.3.4.5.2-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AuthorizationCodeRsp | M | 1 | 302 Found | Authorization code requested by the API invoker. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.5.2.3.4.5.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.5.2.3.4.5.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +## 8.5.2A Custom Operations without associated resources + +There are no custom operations without associated resources defined for this API in this release of the specification. + +## 8.5.3 Notifications + +### 8.5.3.1 General + +The delivery of notifications shall conform to clause 7.6. + +**Table 8.5.3.1-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|------------------------------------|---------------------------|---------------------------------|--------------------------------------------------------------------------------------------| +| Authorization revoked notification | {notificationDestination} | POST | Notify API invoker that the authorization rights are revoked by the API exposing function. | + +### 8.5.3.2 Authorization revoked notification + +#### 8.5.3.2.1 Description + +Authorization revoked notification is used by the CAPIF core function to notify an API invoker that the authorization rights are revoked by the API exposing function. + +#### 8.5.3.2.2 Notification definition + +The POST method shall be used for Authorization revoked notification and the URI shall be the one provided by the API invoker during the Obtain\_Security\_Method service operation. + +Callback URI: {**notificationDestination**} + +This method shall support the URI query parameters specified in table 8.5.3.2.2-1. + +**Table 8.5.3.2.2-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.5.3.2.2-2 and the response data structures and response codes specified in table 8.5.3.2.2-3. + +**Table 8.5.3.2.2-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------------|---|-------------|-----------------------------------------------------------------| +| SecurityNotification | M | 1 | Notification with information related to revoked authorization. | + +**Table 8.5.3.2.2-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | The receipt of the Notification is acknowledged. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative notification destination where the notification should be sent.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative notification destination where the notification should be sent.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.5.3.2.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative notification destination towards which the notification should be redirected. | + +**Table 8.5.3.2.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative notification destination towards which the notification should be redirected. | + +## 8.5.4 Data Model + +### 8.5.4.1 General + +This clause specifies the application data model supported by the API. Data types listed in clause 7.2 also apply to this API. + +Table 8.5.4.1-1 specifies the data types defined specifically for the CAPIF\_Security\_API service. + +**Table 8.5.4.1-1: CAPIF\_Security\_API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|----------------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| AccessTokenClaims | Clause 8.5.4.2.8 | Represents the claims data structure for the access token. | | +| AccessTokenErr | Clause 8.5.4.2.9 | Represents an error in the access token request. | | +| AccessTokenReq | Clause 8.5.4.2.6 | Represents the access token request information. | | +| AccessTokenRsp | Clause 8.5.4.2.7 | Represents the access token response information. | | +| Cause | Clause 8.5.4.3.3 | Indicates the cause for revoking the API invoker's authorization to the service API. | | +| SecurityInformation | Clause 8.5.4.2.3 | Represents the interface details and the security method. | | +| SecurityNotification | Clause 8.5.4.2.5 | Represents the revoked authorization notification details. | | +| ServiceSecurity | Clause 8.5.4.2.2 | Represents the details of the security method for each service API interface. When included by the API invoker, it shall indicate the preferred method of security. When included by the CAPIF core function, it shall indicate the security method to be used for the service API interface. | | +| AuthorizationCodeRsp | Clause 8.5.4.2.10 | Represents the authorization code response information. | RNAA | +| AuthorizationFlow | Clause 8.5.4.3.4 | Represents the authorization flows to support RNAA | RNAA | + +Editor's Note: Details on AuthorizationCodeRsp are FFS. + +Table 8.5.4.1-2 specifies data types re-used by the CAPIF\_Security\_API service based interface: + +**Table 8.5.4.1-2: Re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|------------------------------------------------------------------------------------|----------------------| +| DurationSec | 3GPP TS 29.122 [14] | Indicates the duration in seconds. | | +| SecurityMethod | Clause 8.2.4.3.6 | Indicates the security method (e.g. PKI). | | +| SupportedFeatures | 3GPP TS 29.571 [19] | Used to negotiate the applicability of optional features defined in table 8.5.6-1. | | + +## 8.5.4.2 Structured data types + +### 8.5.4.2.1 Introduction + +### 8.5.4.2.2 Type: ServiceSecurity + +**Table 8.5.4.2.2-1: Definition of type ServiceSecurity** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------------|----------------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| securityInfo | array(SecurityInformation) | M | 1..N | Security information for each API interface. | | +| notificationDestination | Uri | M | 1 | URI where the notification should be delivered to. | | +| requestTestNotification | boolean | O | 0..1 | Set to "true" by API invoker to request the CAPIF core function to send a test notification as defined in clause 7.6. Set to "false" not to request the CAPIF core function to send a test notification. Default value is "false" if omitted. | Notification_test_event | +| websocketNotifConfig | WebsockNotifConfig | O | 0..1 | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 7.6. | Notification_websocket | +| supportedFeatures | SupportedFeatures | C | 0..1 | Used to negotiate the supported optional features of the API as described in clause 7.8. This attribute shall be provided in the HTTP POST request and in the response of successful resource creation. | | + +### 8.5.4.2.3 Type: SecurityInformation + +**Table 8.5.4.2.3-1: Definition of type SecurityInformation** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------|--------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| interfaceDetails | InterfaceDescription | O | 0..1 | Details of the interface (NOTE) | | +| aefId | string | O | 0..1 | AEF identifier (NOTE) | | +| apiId | string | C | 0..1 | API identifier. If API invoker supplies this IE in the PUT request, CCF shall respond back with this IE and its associated security information. | SecurityInfoPerAPI | +| prefSecurityMethods | array(SecurityMethod) | M | 1..N | Security methods preferred by the API invoker for the API interface | | +| selSecurityMethod | SecurityMethod | O | 0..1 | Supplied by the CAPIF core function, it indicates the selected security method for the API interface. If it is not provided, it means no common supported security method by the API invoker and the AEF, or the selected security method is not allowed by the local policy in the CAPIF core function. | | +| authenticationInfo | string | O | 0..1 | Authentication related information | | +| authorizationInfo | string | O | 0..1 | Authorization related information | | +| authorizationFlow | array(AuthorizationFlow) | O | 1..N | The authorization flows to support RNAA as defined in clause 6.5.3 of TS 33.122 [16]. | RNAA | + +NOTE: Only one of the attributes "aefId" or "interfaceDetails" shall be included. + +8.5.4.2.4 Void + +8.5.4.2.5 Type: SecurityNotification + +**Table 8.5.4.2.5-1: Definition of type SecurityNotification** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|---------------|---|-------------|-------------------------------------------------------------------------|---------------| +| apiInvokerId | string | M | 1 | String identifying the API invoker assigned by the CAPIF core function | | +| aefId | string | O | 0..1 | String identifying the AEF. | | +| apiIds | array(string) | M | 1..N | Identifier of the service API | | +| cause | Cause | M | 1 | The cause for revoking the API invoker authorization to the service API | | + +## 8.5.4.2.6 Type: AccessTokenReq + +Table 8.5.4.2.6-1: Definition of type AccessTokenReq + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| grant_type | string | M | 1 | This IE shall contain the grant type as "client_credentials", or when the "RNAA" feature is supported, either "client_credentials" or "authorization_code".
(NOTE 3, NOTE 4) | | +| client_id | string | M | 1 | This IE shall contain the API invoker Identifier.
(NOTE 3) | | +| resOwnerId | string | O | 0..1 | This attribute shall contain the resource owner ID. | RNAA | +| client_secret | string | O | 0..1 | This IE when present shall contain the onboarding secret which is got during API invoker onboarding.
(NOTE 3) | | +| scope | string | O | 0..1 | This IE when present shall contain a list of AEF identifiers and its associated API names for which the access_token is authorized for use.

It takes the format of
3gpp#aefld1:apiName1,apiName2,...
apiNameX;aefld2:apiName1,apiName2,...
apiNameY;...aefldN:apiName1,apiName2,...
apiNameZ

Using delimiter "#" after the discriminator "3gpp", ":" after AEF identifier, "," between API names and ";" between the last API name of the previous AEF identifier and the next AEF identifier.
(NOTE 2)

Example: '3gpp#aef-jiangsu-nanjing:3gpp-monitoring-event,3gpp-as-session-with-qos;aef-zhejiang-hangzhou:3gpp-cp-parameter-provisioning,3gpp-pfd-management' | | +| authCode | string | O | 0..1 | This attribute shall be included If the authorization code flow is selected in RNAA scenarios. This attribute, when present, shall contain authorization code. | RNAA | +| NOTE 1: This data structure shall not be treated as a JSON object. It shall be treated as a key, value pair data structure to be encoded using x-www-urlencoded format as specified in clause 17.13.4.1 of W3C HTML 4.01 Specification [22]. | | | | | | +| NOTE 2: The scope may contain more space-delimited strings which further add additional access ranges to the scope, the definition of those additional strings is out of the scope of the present document. | | | | | | +| NOTE 3: The "grant_type", "client_id" and "client_secret" attributes do not follow the related naming convention defined in subclause 7.2.1. These attributes are however kept as currently defined in this specification for backward compatibility considerations. | | | | | | +| NOTE 4: The enumeration value "client_credentials" of the "grant_type" attribute does not follow the related naming convention defined in subclause 7.2.1. This enumeration is however kept as currently defined in this specification for backward compatibility considerations. | | | | | | + +## 8.5.4.2.7 Type: AccessTokenRsp + +Table 8.5.4.2.7-1: Definition of type AccessTokenRsp + +| Attribute name | Data type | P | Cardinality | Description | +|----------------|-------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| access_token | string | M | 1 | This IE shall contain JWS Compact Serialized representation of the JWS signed JSON object containing AccessTokenClaims (see clause 8.5.4.2.8).

(NOTE 2) | +| token_type | string | M | 1 | This IE shall contain the token type (i.e. "Bearer").

(NOTE 2, NOTE 3) | +| expires_in | DurationSec | M | 1 | This IE when present shall contain the number of seconds after which the access_token is considered to be expired.

(NOTE 2) | +| scope | string | O | 0..1 | This IE when present shall contain a list of AEF identifiers and its associated API names for which the access_token is authorized for use.

It takes the format of
3gpp#aefld1:apiName1,apiName2,...
apiNameX:aefld2:apiName1,apiName2,...
apiNameY:...aefldN:apiName1,apiName2,...
apiNameZ

Using delimiter "#" after the discriminator "3gpp", ":" after AEF identifier, "," between API names and ";" between the last API name of the previous AEF identifier and the next AEF identifier. (NOTE 1)

Example: '3gpp#aef-jiangsu-nanjing:3gpp-monitoring-event,3gpp-as-session-with-qos;aef-zhejiang-hangzhou:3gpp-cp-parameter-provisioning,3gpp-pfd-management' | + +NOTE 1: The scope may contain more space-delimited strings which further add additional access ranges to the scope, the definition of those additional strings is out of the scope of the present document. + +NOTE 2: The "access\_token", "token\_type" and "expires\_in" attributes do not follow the related naming convention defined in clause 7.2.1. These attributes are however kept as currently defined in this specification for backward compatibility considerations. + +NOTE 3: The enumeration value "Bearer" of the "token\_type" attribute does not follow the related naming convention defined in clause 7.2.1. This enumeration is however kept as currently defined in this specification for backward compatibility considerations. + +## 8.5.4.2.8 Type: AccessTokenClaims + +Table 8.5.4.2.8-1: Definition of type AccessTokenClaims + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| iss | string | M | 1 | This IE shall contain the API invoker Identifier. | | +| scope | string | M | 1 | This IE shall contain a list of AEF identifiers and its associated API names for which the access_token is authorized for use.

It takes the format of
3gpp#aefId1:apiName1,apiName2,...
apiNameX;aefId2:apiName1,apiName2,...
apiNameY;...aefIdN:apiName1,apiName2,...
apiNameZ

Using delimiter "#" after the discriminator "3gpp", ":" after AEF identifier, "," between API names and ";" between the last API name of the previous AEF identifier and the next AEF identifier. (NOTE)

Example: '3gpp#aef-jiangsu-nanjing:3gpp-monitoring-event,3gpp-as-session-with-qos;aef-zhejiang-hangzhou:3gpp-cp-parameter-provisioning,3gpp-pfd-management' | | +| exp | DurationSec | M | 1 | This IE shall contain the number of seconds after which the access_token is considered to be expired. | | +| resOwnerId | string | O | 0..1 | This attribute shall contain the resource owner ID. | RNAA | +| NOTE: The scope may contain more space-delimited strings which further add additional access ranges to the scope, the definition of those additional strings is out of the scope of the present document. | | | | | | + +## 8.5.4.2.9 Type: AccessTokenErr + +Table 8.5.4.2.9-1: Definition of type AccessTokenErr + +| Attribute name | Data type | P | Cardinality | Description | +|-------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| error | string | M | 1 | This IE shall contain the error described in IETF RFC 6749 [23], clause 5.2.
Enum:
"invalid_request"
"invalid_client"
"invalid_grant"
"unauthorized_client"
"unsupported_grant_type"
"invalid_scope"

(NOTE 1) | +| error_description | string | O | 0..1 | When present, this IE shall contain the human-readable additional information to indicate the error that occurred, as described in IETF RFC 6749 [23], clause 5.2.

(NOTE 2) | +| error_uri | string | O | 0..1 | When present, this IE shall contain the URI identifying a human-readable additional information about the error, as described in IETF RFC 6749 [23], clause 5.2.

(NOTE 2) | + +NOTE 1: The enumeration values "invalid\_request", "invalid\_client", "invalid\_grant", "unauthorized\_client", "unsupported\_grant\_type" and "invalid\_scope" of the "error" attribute do not follow the related naming convention defined in clause 7.2.1. These enumeration values are however kept as currently defined in this specification for alignment with definitions in IETF RFC 6749 [23] and backward compatibility considerations. + +NOTE 2: The "error\_description" and "error\_uri" attributes do not follow the related naming convention defined in clause 7.2.1. These attributes are however kept as currently defined in this specification for alignment with definitions in IETF RFC 6749 [23] and backward compatibility considerations. + +## 8.5.4.2.10 Type: AuthorizationCodeRsp + +Table 8.5.4.2.10-1: Definition of type AuthorizationCodeRsp + +| Attribute name | Data type | P | Cardinality | Description | +|----------------|-----------|---|-------------|-------------------------------------------| +| authCode | string | M | 1 | This IE shall contain authorization code. | + +## 8.5.4.3 Simple data types and enumerations + +## 8.5.4.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +## 8.5.4.3.2 Simple data types + +The simple data types defined in table 8.5.4.3.2-1 shall be supported. + +Table 8.5.4.3.2-1: Simple data types + +| Type Name | Type Definition | Description | Applicability | +|-----------|-----------------|-------------|---------------| +| n/a | | | | + +### 8.5.4.3.3 Enumeration: Cause + +**Table 8.5.4.3.3-1: Enumeration Cause** + +| Enumeration value | Description | Applicability | +|-------------------|---------------------------------------------------------------------------------------------------------|---------------| +| OVERLIMIT_USAGE | The revocation of the authorization of the API invoker is due to the overlimit usage of the service API | | +| UNEXPECTED_REASON | The revocation of the authorization of the API invoker is due to unexpected reason. | | + +### 8.5.4.3.4 Enumeration: AuthorizationFlow + +**Table 8.5.4.3.4-1: Enumeration AuthorizationFlow** + +| Enumeration value | Description | Applicability | +|-----------------------------------|------------------------------------------------------------------------------|---------------| +| CLIENT_CREDENTIALS_FLOW | Client credentials flow as described in clause 6.5.2 of TS 33.122 [16]. | | +| AUTHORIZATION_CODE_FLOW | Authorization code flow defined in clause 6.5.3 of TS 33.122 [16]. | | +| AUTHORIZATION_CODE_FLOW_WITH_PKCE | Authorization code flow with PKCE defined in clause 6.5.3 of TS 33.122 [16]. | | + +**Editor's Note:** The AuthorizationFlow enumeration is FFS. + +## 8.5.5 Error Handling + +### 8.5.5.1 General + +General error responses are defined in clause 7.7. + +In addition, the requirements in the following subclauses shall apply. + +### 8.5.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the CAPIF\_Security\_API. + +### 8.5.5.3 Application Errors + +The application errors defined for the Obtain\_Authorization service operation are listed in Table 8.5.5.3-1, and correspond to the values of the "error" attribute (see clause 8.5.4.2.9). + +**Table 8.5.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|------------------------| +| invalid_request | 400 Bad Request | See IETF RFC 6749 [23] | +| invalid_client | 400 Bad Request,
401 Unauthorized | See IETF RFC 6749 [23] | +| invalid_grant | 400 Bad Request | See IETF RFC 6749 [23] | +| unauthorized_client | 400 Bad Request | See IETF RFC 6749 [23] | +| unsupported_grant_type | 400 Bad Request | See IETF RFC 6749 [23] | +| invalid_scope | 400 Bad Request | See IETF RFC 6749 [23] | +| NOTE: These enumeration values defined in this table do not follow the related naming convention defined in clause 7.2.1. These enumeration values are however kept as currently defined in this specification for alignment with definitions in IETF RFC 6749 [23]. | | | + +## 8.5.6 Feature negotiation + +General feature negotiation procedures are defined in clause 7.8. Table 8.5.6-1 lists the supported features for CAPIF\_Security\_API. + +**Table 8.5.6-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Notification_test_event | Testing of notification connection is supported according to clause 7.6. | +| 2 | Notification_websocket | The delivery of notifications over Websocket is supported according to clause 7.6. This feature requires that the Notification_test_event feature is also supported. | +| 3 | SecurityInfoPerAPI | Indicates the support of negotiating and obtaining service API security method information per API. | +| 4 | RNAA | Indicates the support of resource owner awareness authorization. | + +## 8.6 CAPIF\_Access\_Control\_Policy\_API + +### 8.6.1 API URI + +The CAPIF\_Access\_Control\_Policy\_API service shall use the CAPIF\_Access\_Control\_Policy\_API. + +The request URIs used in HTTP requests from the API exposing function towards the CAPIF core function shall have the Resource URI structure as defined in clause 7.5 with the following clarifications: + +- The shall be "access-control-policy". +- The shall be "v1". +- The shall be set as described in clause 8.6.2. + +All the resource URIs and the custom operation URIs specified in the clauses below are defined relative to the above API URI. + +### 8.6.2 Resources + +#### 8.6.2.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 8.6.2.1-1 depicts the resource URIs structure for the CAPIF\_Access\_Control\_Policy\_API. + +This resource is created by the CAPIF administrator on the CAPIF core function. + +NOTE: The details of the mechanisms used to create the Access Control Policy List resource on the CAPIF core function is out of the scope of the present document. + +![Figure 8.6.2.1-1: Resource URI structure of the CAPIF Access Control Policy API. The diagram shows a hierarchical URI structure. The root is {apiRoot}/access-control-policy/. A line descends from this root to a segment /accessControlPolicyList. From /accessControlPolicyList, another line descends to a segment /{serviceApiId}, which is enclosed in a rounded rectangular box.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +``` + +graph TD + Root["{apiRoot}/access-control-policy/"] --> List["/accessControlPolicyList"] + List --> ServiceId["/{serviceApiId}"] + style ServiceId stroke-width:2px,rx:10,ry:10 + +``` + +Figure 8.6.2.1-1: Resource URI structure of the CAPIF Access Control Policy API. The diagram shows a hierarchical URI structure. The root is {apiRoot}/access-control-policy/. A line descends from this root to a segment /accessControlPolicyList. From /accessControlPolicyList, another line descends to a segment /{serviceApiId}, which is enclosed in a rounded rectangular box. + +**Figure 8.6.2.1-1: Resource URI structure of the CAPIF Access Control Policy API** + +Table 8.6.2.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 8.6.2.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|---------------------------------|-----------------------------------------------------------------------| +| Access Control Policy List | /accessControlPolicyList/{serviceApiId}
(NOTE) | GET | Retrieves the access control policy list for a published service API. | +| NOTE: The path segment "accessControlPolicyList" does not follow the related naming convention defined in clause 7.5.1. The path segment is however kept as currently defined in this specification for backward compatibility considerations. | | | | + +## 8.6.2.2 Resource: Access Control Policy List + +### 8.6.2.2.1 Description + +The Access Control Policy List resource represents the access control information for all the service APIs per API invoker. + +### 8.6.2.2.2 Resource Definition + +Resource URI: {apiRoot}/access-control-policy//accessControlPolicyList/{serviceApiId} + +This resource shall support the resource URI variables defined in table 8.6.2.2.2-1. + +**Table 8.6.2.2.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|--------------|-----------|------------------------------------------------| +| apiRoot | string | See clause 7.5 | +| serviceApiId | string | Identifies an individual published service API | + +### 8.6.2.2.3 Resource Standard Methods + +#### 8.6.2.2.3.1 GET + +This method shall support the URI query parameters specified in table 8.6.2.2.3.1-1. + +**Table 8.6.2.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | +|--------------------|-------------------|---|-------------|-----------------------------------------------------------------| +| aef-id | string | M | 1 | AEF identifier | +| api-invoker-id | string | O | 1 | String identifying the API invoker | +| supported-features | SupportedFeatures | O | 0..1 | To filter irrelevant responses related to unsupported features. | + +This method shall support the request data structures specified in table 8.6.2.2.3.1-2 and the response data structures and response codes specified in table 8.6.2.2.3.1-3. + +**Table 8.6.2.2.3.1-2: Data structures supported by the GET Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.6.2.2.3.1-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-------------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AccessControlPolicyList | M | 1 | 200 OK | List of the access control policy applicable for the service API requested. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.6.2.2.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.6.2.2.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +### 8.6.2.2.4 Resource Custom Operations + +There are no notifications defined for this API in this release of the specification. + +## 8.6.2A Custom Operations without associated resources + +There are no custom operations without associated resources defined for this API in this release of the specification. + +## 8.6.3 Notifications + +None. + +## 8.6.4 Data Model + +### 8.6.4.1 General + +This clause specifies the application data model supported by the API. Data types listed in clause 7.2 also apply to this API. + +Table 8.6.4.1-1 specifies the data types defined specifically for the CAPIF\_Access\_Control\_Policy\_API service. + +**Table 8.6.4.1-1: CAPIF\_Access\_Control\_Policy\_API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|-------------------------|------------------|-------------------------------------------------------------------------------------------------------|---------------| +| AccessControlPolicyList | Clause 8.6.4.2.2 | Represents the access control policy list for a published service API. | | +| ApiInvokerPolicy | Clause 8.6.4.2.3 | Represents the policy of an API Invoker. | | +| TimeRangeList | Clause 8.6.4.2.4 | Represents the time range during which the invocation of a service API is allowed by the API invoker. | | + +Table 8.6.4.1-2 specifies data types re-used by the CAPIF\_Access\_Control\_Policy\_API service. + +**Table 8.6.4.1-2: Re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|------------------------------------------------------------------------------------|---------------| +| DateTime | 3GPP TS 29.122 [14] | Used to indicate start and end times. | | +| SupportedFeatures | 3GPP TS 29.571 [19] | Used to negotiate the applicability of optional features defined in table 8.6.6-1. | | + +### 8.6.4.2 Structured data types + +#### 8.6.4.2.1 Introduction + +This clause defines data structures to be used in resource representations. + +#### 8.6.4.2.2 Type: AccessControlPolicyList + +**Table 8.6.4.2.2-1: Definition of type AccessControlPolicyList** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|--------------------|-------------------------|---|-------------|-----------------------------|---------------| +| apiInvokerPolicies | array(ApiInvokerPolicy) | O | 0..N | Policy of each API invoker. | | + +### 8.6.4.2.3 Type: ApiInvokerPolicy + +**Table 8.6.4.2.3-1: Definition of type ApiInvokerPolicy** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------------------|----------------------|---|-------------|-------------------------------------------------------------------------------------------------|---------------| +| apiInvokerId | string | M | 1 | API invoker ID assigned by the CAPIF core function | | +| allowedTotalInvocations | integer | O | 0..1 | Total number of invocations allowed on the service API by the API invoker. | | +| allowedInvocationsPerSecond | integer | O | 0..1 | Invocations per second allowed on the service API by the API invoker. | | +| allowedInvocationsTimeRangeList | array(TimeRangeList) | O | 0..N | The time ranges during which the invocations are allowed on the service API by the API invoker. | | + +### 8.6.4.2.4 Type: TimeRangeList + +**Table 8.6.4.2.4-1: Definition of type TimeRangeList** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------|---|-------------|-----------------------------------------------------------------------------------------|---------------| +| startTime | DateTime | M | 1 | The start time for the invocations to be allowed on the service API by the API invoker. | | +| stopTime | DateTime | M | 1 | The end time for the invocations to be allowed on the service API by the API invoker. | | + +## 8.6.4.3 Simple data types and enumerations + +None. + +## 8.6.5 Error Handling + +### 8.6.5.1 General + +HTTP error handling shall be supported as specified in clause 7.7. + +In addition, the requirements in the following clauses shall apply. + +### 8.6.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the CAPIF\_Access\_Control\_Policy\_API. + +### 8.6.5.3 Application Errors + +The application errors defined for the CAPIF\_Access\_Control\_Policy\_API are listed in table 8.6.5.3-1. + +**Table 8.6.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 8.6.6 Feature negotiation + +General feature negotiation procedures are defined in clause 7.8. + +**Table 8.6.6-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|-------------| +| n/a | | | + +## 8.7 CAPIF\_Logging\_API\_Invocation\_API + +### 8.7.1 API URI + +The CAPIF\_Logging\_API\_Invocation\_API service shall use the CAPIF\_Logging\_API\_Invocation\_API. + +The request URIs used in HTTP requests from the API exposing function towards the CAPIF core function shall have the Resource URI structure as defined in clause 7.5 with the following clarifications: + +- The shall be "api-invocation-logs". +- The shall be "v1". +- The shall be set as described in clause 8.7.2 + +All the resource URIs and the custom operation URIs specified in the clauses below are defined relative to the above API URI. + +### 8.7.2 Resources + +#### 8.7.2.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 8.7.2.1-1 depicts the resource URIs structure for the CAPIF\_Logging\_API\_Invocation\_API. + +![Diagram showing the resource URI structure for the CAPIF_Logging_API_Invocation_API. The root URI is {apiRoot}/api-invocation-logs/. It branches into /{aeFId}, which then branches into /logs (shown in a box), which finally branches into /{logId} (shown in a box).](9a7872f64558de06ee8b85b87e920b7e_img.jpg) + +``` + +graph TD + Root["{apiRoot}/api-invocation-logs/"] --> aeFId["/{aeFId}"] + aeFId --> logs["/logs"] + logs --> logId["/{logId}"] + style logs stroke-width:2px + style logId stroke-width:2px + +``` + +Diagram showing the resource URI structure for the CAPIF\_Logging\_API\_Invocation\_API. The root URI is {apiRoot}/api-invocation-logs/. It branches into /{aeFId}, which then branches into /logs (shown in a box), which finally branches into /{logId} (shown in a box). + +**Figure 8.7.2.1-1: Resource URI structure of the CAPIF\_Logging\_API\_Invocation\_API** + +Table 8.7.2.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 8.7.2.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|----------------|------------------------|---------------------------------|-----------------------------------------------------| +| Logs | /{aeflId}/logs | POST | Creates a new log entry for service API invocations | +| Individual log | /{aeflId}/logs/{logId} | n/a | Individual log entry | + +## 8.7.2.2 Resource: Logs + +### 8.7.2.2.1 Description + +The Logs resource represents all the log entries created by a API exposing function at CAPIF core function. + +### 8.7.2.2.2 Resource Definition + +Resource URI: {apiRoot}/api-invocation-logs//{aeflId}/logs + +This resource shall support the resource URI variables defined in table 8.7.2.2.2-1. + +**Table 8.7.2.2.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|---------|-----------|-----------------------------------------| +| apiRoot | string | See clause 7.5 | +| aeflId | string | Identifies of the API exposing function | + +### 8.7.2.2.3 Resource Standard Methods + +#### 8.7.2.2.3.1 POST + +This method shall support the URI query parameters specified in table 8.7.2.2.3.1-1. + +**Table 8.7.2.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.7.2.2.3.1-2 and the response data structures and response codes specified in table 8.7.2.2.3.1-3. + +**Table 8.7.2.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|---------------|---|-------------|-------------------------------------------------------------------------------------------------------| +| InvocationLog | M | 1 | Log of service API invocations provided by API exposing function to store on the CAPIF core function. | + +**Table 8.7.2.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| InvocationLog | M | 1 | 201
Created | Log of service API invocations provided by API exposing function successfully stored on the CAPIF core function.

The URI of the created resource shall be returned in the "Location" HTTP header. | +| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. | | | | | + +**Table 8.7.2.2.3.1-4: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/api-invocation-logs///logs/ | + +#### 8.7.2.2.4 Resource Custom Operations + +None. + +### 8.7.2A Custom Operations without associated resources + +There are no custom operations without associated resources defined for this API in this release of the specification. + +### 8.7.3 Notifications + +There are no notifications defined for this API in this release of the specification. + +### 8.7.4 Data Model + +#### 8.7.4.1 General + +This clause specifies the application data model supported by the API. Data types listed in clause 7.2 also apply to this API. + +Table 8.7.4.1-1 specifies the data types defined specifically for the CAPIF\_Logging\_API\_Invocation\_API service. + +**Table 8.7.4.1-1: CAPIF\_Logging\_API\_Invocation\_API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|---------------|------------------|----------------------------------------------------------------------------------------|---------------| +| DurationMs | Clause 8.7.4.3.2 | Represents the period of time in units of milliseconds. | | +| InvocationLog | Clause 8.7.4.2.2 | Represents the set of Service API invocation logs to be stored on CAPIF core function. | | +| Log | Clause 8.7.4.2.3 | Represents the individual service API invocation log entry. | | + +Table 8.7.4.1-2 specifies data types re-used by the CAPIF\_Logging\_API\_Invocation\_API service. + +**Table 8.7.4.1-2: Re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|------------------------------------------------------------------------------------|---------------| +| DateTime | 3GPP TS 29.122 [14] | Used to indicate the invocation time. | | +| Operation | Clause 8.2.4.3.7 | Used to indicate the HTTP operation | | +| SupportedFeatures | 3GPP TS 29.571 [19] | Used to negotiate the applicability of optional features defined in table 8.7.6-1. | | + +## 8.7.4.2 Structured data types + +### 8.7.4.2.1 Introduction + +This clause defines the structured data types to be used in resource representations of the CAPIF\_Logging\_API\_Invocation\_API. + +### 8.7.4.2.2 Type: InvocationLog + +**Table 8.7.4.2.2-1: Definition of type InvocationLog** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|--------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| aefId | string | M | 1 | Identity information of the API exposing function requesting logging of service API invocations | | +| apiInvokerId | string | M | 1 | Identity of the API invoker which invoked the service API | | +| logs | array(Log) | M | 1..N | Service API invocation log | | +| supportedFeatures | Supported Features | O | 0..1 | Used to negotiate the supported optional features of the API as described in clause 7.8.
This attribute shall be provided in the HTTP POST request and in the response of successful resource creation. | | + +### 8.7.4.2.3 Type: Log + +**Table 8.7.4.2.3-1: Definition of type Log** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|----------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| apiId | string | M | 1 | String identifying the API invoked. | | +| apiName | string | M | 1 | Name of the API which was invoked, it is set as {apiName} part of the URI structure as defined in clause 5.2.4 of 3GPP TS 29.122 [14]. | | +| apiVersion | string | M | 1 | Version of the API which was invoked | | +| resourceName | String | M | 1 | Name of the specific resource invoked | | +| uri | Uri | O | 0..1 | Full URI of the API resource as defined in clause 5.2.4 of 3GPP TS 29.122 [14]. | | +| protocol | Protocol | M | 1 | Protocol invoked. | | +| operation | Operation | C | 0..1 | Operation that was invoked on the API, only applicable for HTTP protocol. | | +| result | string | M | 1 | For HTTP protocol, it contains HTTP status code of the invocation | | +| invocationTime | DateTime | O | 0..1 | Date on which it was invoked | | +| invocationLatency | DurationMs | O | 0..1 | Latency for the API invocation. | | +| inputParameters | ANY TYPE (NOTE) | O | 0..1 | List of input parameters | | +| OutputParameters | ANY TYPE (NOTE) | O | 0..1 | List of output parameters | | +| srcInterface | InterfaceDescription | O | 0..1 | Interface description of the API invoker. | | +| destInterface | InterfaceDescription | O | 0..1 | Interface description of the API invoked. | | +| fwdInterface | string | O | 0..1 | It includes the node identifier (as defined in IETF RFC 7239 [20] of all forwarding entities between the API invoker and the AEF, concatenated with comma and space, e.g. 192.0.2.43:80, unknown:_OBFport, 203.0.113.60 | | + +NOTE: Any basic data type defined in OpenAPI Specification [3] may be used. + +### 8.7.4.3 Simple data types and enumerations + +#### 8.7.4.3.1 Introduction + +This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. + +#### 8.7.4.3.2 Simple data types + +The simple data types defined in table 8.7.4.3.2-1 shall be supported. + +**Table 8.7.4.3.2-1: Simple data types** + +| Type Name | Type Definition | Description | Applicability | +|------------|-----------------|-------------------------------------------------------------------------|---------------| +| DurationMs | integer | Unsigned integer identifying a period of time in units of milliseconds. | | + +## 8.7.5 Error Handling + +### 8.7.5.1 General + +HTTP error handling shall be supported as specified in clause 7.7. + +In addition, the requirements in the following clauses shall apply. + +### 8.7.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the CAPIF\_Logging\_API\_Invocation\_API. + +### 8.7.5.3 Application Errors + +The application errors defined for the CAPIF\_Logging\_API\_Invocation\_API are listed in table 8.7.5.3-1. + +**Table 8.7.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 8.7.6 Feature negotiation + +**Table 8.7.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|-------------| +| n/a | | | + +## 8.8 CAPIF\_Auditing\_API + +### 8.8.1 API URI + +The CAPIF\_Auditing\_API service shall use the CAPIF\_Auditing\_API. + +The request URIs used in HTTP requests from the API management function towards the CAPIF core function shall have the Resource URI structure as defined in clause 7.5 with the following clarifications: + +- The shall be "logs". +- The shall be "v1". +- The shall be set as described in clause 8.8.2. + +All the resource URIs and the custom operation URIs specified in the clauses below are defined relative to the above API URI. + +## 8.8.2 Resources + +### 8.8.2.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 8.8.2.1-1 depicts the resource URIs structure for the CAPIF\_Auditing\_API. + +![Diagram showing the resource URI structure for the CAPIF_Auditing_API. The base URI is {apiRoot}/logs/. A callout box points to the path segment /apiInvocationLogs, indicating it is a sub-resource under the logs directory.](471c91d9988fb84924ddb6b71bb16fa1_img.jpg) + +``` + + {apiRoot}/logs/ + | + +-- /apiInvocationLogs + +``` + +Diagram showing the resource URI structure for the CAPIF\_Auditing\_API. The base URI is {apiRoot}/logs/. A callout box points to the path segment /apiInvocationLogs, indicating it is a sub-resource under the logs directory. + +**Figure 8.8.2.1-1: Resource URI structure of the CAPIF\_Auditing\_API** + +Table 8.8.2.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 8.8.2.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---------------------------------|----------------------------------------------------------------------------------| +| All service API invocation logs (Store) | /apiInvocationLogs
(NOTE) | GET | Query and retrieve service API invocation logs stored on the CAPIF core function | +| NOTE: The path segment "apiInvocationLogs" does not follow the related naming convention defined in clause 7.5.1. The path segment is however kept as currently defined in this specification for backward compatibility considerations. | | | | + +### 8.8.2.2 Resource: All service API invocation logs + +#### 8.8.2.2.1 Description + +The All service API invocation logs resource represents a collection of service API invocation logs stored on the CAPIF core function. The resource is modelled as a Store resource archetype (see annex C.3 of 3GPP TS 29.501 [18]) + +#### 8.8.2.2.2 Resource Definition + +Resource URI: {apiRoot}/logs//apiInvocationLogs + +This resource shall support the resource URI variables defined in table 8.8.2.2-1. + +**Table 8.8.2.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|---------|-----------|----------------| +| apiRoot | string | See clause 7.5 | + +### 8.8.2.2.3 Resource Standard Methods + +#### 8.8.2.2.3.1 GET + +This method shall support the URI query parameters specified in table 8.8.2.2.3.1-1. + +**Table 8.8.2.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | +|--------------------|----------------------|---|-------------|---------------------------------------------------------------------------------------------------------------| +| aef-id | string | O | 0..1 | String identifying the API exposing function | +| api-invoker-id | string | O | 0..1 | String identifying the API invoker which invoked the service API | +| time-range-start | DateTime | O | 0..1 | Start time of the invocation time range | +| time-range-end | DateTime | O | 0..1 | End time of the invocation time range | +| api-id | string | O | 0..1 | String identifying the API invoked. | +| api-name | string | O | 0..1 | API name, it is set as {apiName} part of the URI structure as defined in clause 5.2.4 of 3GPP TS 29.122 [14]. | +| api-version | string | O | 0..1 | Version of the API which was invoked | +| protocol | Protocol | O | 0..1 | Protocol invoked | +| operation | Operation | O | 0..1 | Operation that was invoked on the API | +| result | string | O | 0..1 | HTTP status code of the invocation | +| resource-name | string | O | 0..1 | Name of the specific resource invoked | +| src-interface | InterfaceDescription | O | 0..1 | Interface description of the API invoker. | +| dest-interface | InterfaceDescription | O | 0..1 | Interface description of the API invoked. | +| supported-features | SupportedFeatures | O | 0..1 | To filter irrelevant responses related to unsupported features. | + +This method shall support the request data structures specified in table 8.8.2.2.3.1-2 and the response data structures and response codes specified in table 8.8.2.2.3.1-3. + +**Table 8.8.2.2.3.1-2: Data structures supported by the GET Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.8.2.2.3.1-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|---------------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| InvocationLogsRetrieveRes | O | 0..1 | 200 OK | Result of the query operation along with fetched service API invocation log data. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| ProblemDetails | O | 0..1 | 414 URI Too Long | Indicates that the server is refusing to service the request because the request-target is too long. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.8.2.2.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.8.2.2.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.8.2.2.4 Resource Custom Operations + +None. + +### 8.8.2A Custom Operations without associated resources + +There are no custom operations without associated resources defined for this API in this release of the specification. + +## 8.8.3 Notifications + +There are no notifications defined for this API in this release of the specification. + +## 8.8.4 Data Model + +### 8.8.4.1 General + +This clause specifies the application data model supported by the API. Data types listed in clause 7.2 also apply to this API. + +Table 8.8.4.1-1 specifies the data types defined specifically for the CAPIF\_Auditing\_API service. + +**Table 8.8.4.1-1: CAPIF\_Auditing\_API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|-------------------------------|-----------------|--------------------------------------------------------------|------------------| +| InvocationLogs | 8.8.4.2.2 | Contains multiple invocation logs. | EnQueryInvokeLog | +| InvocationLogsRetrieveResults | 8.8.4.2.3 | Contains the result of an invocation logs retrieval request. | | + +Table 8.8.4.1-2 specifies data types re-used by the CAPIF\_Auditing\_API service: + +**Table 8.8.4.1-2: Re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|--------------------------------------------------------------------------------------|---------------| +| DateTime | 3GPP TS 29.122 [14] | Used to indicate the start and end times. | | +| InvocationLog | Clause 8.7.4.2.2 | Used to represent logs of service API invocations stored on the CAPIF core function. | | +| Operation | Clause 8.2.4.3.7 | Used to indicate the HTTP operation. | | +| ProblemDetails | 3GPP TS 29.122 [14] | Used to represent the problem details in an error message. | | +| SupportedFeatures | 3GPP TS 29.571 [19] | Used to negotiate the applicability of optional features defined in table 8.8.6-1. | | + +## 8.8.4.2 Structured data types + +### 8.8.4.2.1 Introduction + +This clause defines the structured data types to be used in resource representations of the CAPIF\_Auditing\_API. + +### 8.8.4.2.2 Type: InvocationLogs + +**Table 8.8.4.2.2-1: Definition of type InvocationLogs** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------------|----------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| multipleInvocationLogs | array(InvocationLog) | M | 1..N | Contains a multiple API invocation logs.

The "supportedFeatures" attribute within the InvocationLog data type shall not be provided. | | +| supportedFeatures | SupportedFeatures | C | 0..1 | Used to negotiate the supported optional features of the API as described in clause 8.8.6.
This parameter shall be included in HTTP GET response, if the consumer includes "supported-features" in the GET request. | | + +## 8.8.4.3 Simple data types and enumerations + +None. + +## 8.8.4.4 Data types describing alternative data types or combinations of data types + +### 8.8.4.4.1 Type: InvocationLogsRetrieveRes + +**Table 8.8.4.4.1-1: Definition of type InvocationLogsRetrieveRes as a list of mutually exclusive alternatives** + +| Data type | P | Cardinality | Description | Applicability | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------------------------------------------------------------|------------------| +| InvocationLog | C | 0..1 | Contains a single API invocation log.

(NOTE) | | +| InvocationLogs | C | 0..1 | Contains multiple (more than one) API invocation logs.

(NOTE) | EnQueryInvokeLog | +| NOTE: The InvocationLogs attribute shall be provided if the EnQueryInvokeLog feature is supported and requested by the API invoker, otherwise only the InvocationLog data type shall be provided. | | | | | + +## 8.8.5 Error Handling + +### 8.8.5.1 General + +HTTP error handling shall be supported as specified in clause 7.7. + +In addition, the requirements in the following clauses shall apply. + +### 8.8.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the CAPIF\_Auditing\_API. + +### 8.8.5.3 Application Errors + +The application errors defined for the CAPIF\_Auditing\_API are listed in table 8.8.5.3-1. + +**Table 8.8.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 8.8.6 Feature negotiation + +General feature negotiation procedures are defined in clause 7.8. + +**Table 8.8.6-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|------------------|------------------------------------------------------------------------------| +| 1 | EnQueryInvokeLog | This feature indicates support for the enhancements of query invocation log. | + +## 8.9 CAPIF\_API\_Provider\_Management\_API + +### 8.9.1 API URI + +The CAPIF\_API\_Provider\_Management\_API service shall use the CAPIF\_API\_Provider\_Management\_API. + +The request URIs used in HTTP requests from the API management function towards the CAPIF core function shall have the Resource URI structure as defined in clause 7.5 with the following clarifications: + +- The shall be "api-provider-management". +- The shall be "v1". +- The shall be set as described in clause 8.9.2. + +All the resource URIs and the custom operation URIs specified in the clauses below are defined relative to the above API URI. + +### 8.9.2 Resources + +#### 8.9.2.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 8.9.2.1-1 depicts the resource URIs structure for the CAPIF\_API\_Provider\_Management\_API. + +![Diagram showing the resource URI structure. A root URI '{apiRoot}/api-provider-management/' branches to a box containing '/registrations'. This box further branches to another box containing '/{registrationId}'.](8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg) + +{apiRoot}/api-provider-management/ + +``` + +graph TD + Root["{apiRoot}/api-provider-management/"] --> Regs["/registrations"] + Regs --> RegId["/{registrationId}"] + +``` + +Diagram showing the resource URI structure. A root URI '{apiRoot}/api-provider-management/' branches to a box containing '/registrations'. This box further branches to another box containing '/{registrationId}'. + +**Figure 8.9.2.1-1: Resource URI structure of the CAPIF\_API\_Provider\_Management\_API** + +Table 8.9.2.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 8.9.2.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|---------------------------------------------|---------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| All API Provider Domains Registrations | /registrations | POST | Registers a new API provider domain by creating an API provider domain with API provider domain functions profiles. | +| Individual API Provider Domain Registration | /registrations/{registrationId} | PUT | Updates an individual API provider domain identified by {registrationId} | +| | | PATCH | Modifies an individual API provider domain identified by {registrationId} | +| | | DELETE | Deregisters an API provider domain by deleting the API provider domain and functions, identified by {registrationId}. | + +## 8.9.2.2 Resource: All API Provider Domains Registrations + +### 8.9.2.2.1 Description + +The All API provider domains registrations resource represents all the API provider domains that are registered at a given CAPIF core function. + +### 8.9.2.2.2 Resource Definition + +Resource URI: {apiRoot}/api-provider-management//registrations + +This resource shall support the resource URI variables defined in table 8.9.2.2.2-1. + +**Table 8.9.2.2.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|---------|-----------|----------------| +| apiRoot | string | See clause 7.5 | + +### 8.9.2.2.3 Resource Standard Methods + +#### 8.9.2.2.3.1 POST + +This method shall support the URI query parameters specified in table 8.9.2.2.3.1-1. + +**Table 8.9.2.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.9.2.2.3.1-2 and the response data structures and response codes specified in table 8.9.2.2.3.1-3. + +**Table 8.9.2.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------------------|---|-------------|---------------------------------------------------------------------------------------------------------| +| APIProviderEnrolmentDetails | M | 1 | Enrolment details of the API provider domain including individual API provider domain function details. | + +**Table 8.9.2.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APIProviderEnrolmentDetails | M | 1 | 201
Created | API provider domain registered successfully

The URI of the created resource shall be returned in the "Location" HTTP header.
The list of successfully registered individual API provider domain functions, registration specific failure information of failed API provider domain function registrations, are included in APIProviderEnrolmentDetails which is provided in the response body. | +| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. | | | | | + +**Table 8.9.2.2.3.1-4: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/api-provider-management//registrations/{registrationId} | + +### 8.9.2.2.4 Resource Custom Operations + +None. + +## 8.9.2.3 Resource: Individual API Provider Domain Registration + +### 8.9.2.3.1 Description + +The Individual API Provide Domain Registration resource represents an individual API provider domain that is registered at a given CAPIF core function. + +### 8.9.2.3.2 Resource Definition + +Resource URI: {apiRoot}/api-provider-management//registrations/{registrationId} + +This resource shall support the resource URI variables defined in table 8.9.2.3.2-1. + +**Table 8.9.2.3.2-1: Resource URI variables for this resource** + +| Name | Data Type | Definition | +|----------------|-----------|------------------------------------------------------------------| +| apiRoot | string | See clause 7.5 | +| registrationId | string | Identifies an individual registered API Provider domain resource | + +### 8.9.2.3.3 Resource Standard Methods + +#### 8.9.2.3.3.1 PUT + +The PUT method allows updating the registered API provider domain's detail. The properties "apiProviderDomainId", and "supportedFeatures" shall remain unchanged from previously provided values. This method shall support the URI query parameters specified in table 8.9.2.3.3.1-1. + +**Table 8.9.2.3.3.1-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in the table 8.9.2.3.3.1-2 and the response data structures and response codes specified in the table 8.9.2.3.3.1-3. + +**Table 8.9.2.3.3.1-2: Data structures supported by the PUT Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------------------|---|-------------|---------------------------------------------| +| APIProviderEnrolmentDetails | M | 1 | Updated details of the API provider domain. | + +**Table 8.9.2.3.3.1-3: Data structures supported by the PUT Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|---------------------------------------------------------------------------------------------------------------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APIProviderEnrolmentDetails | M | 1 | 200 OK | API provider domain's information updated successfully.

Updated details of the API provider domain is part of the APIProviderEnrolmentDetails, which is provided in the response body. The list of successfully updated individual API provider domain functions, registration update specific failure information of failed API provider domain function registration updates, are included in APIProviderEnrolmentDetails which is provided in the response body. | +| n/a | | | 204 No Content | API provider domain's information updated successfully. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. | | | | | + +**Table 8.9.2.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.9.2.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.9.2.3.3.2 DELETE + +This method shall support the URI query parameters specified in table 8.9.2.3.3.2-1. + +**Table 8.9.2.3.3.2-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the response codes specified in table 8.9.2.3.3.2-2 and the response data structures and response codes specified in table 8.9.2.3.3.2-3. + +**Table 8.9.2.3.3.2-2: Data structures supported by the DELETE Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.9.2.3.3.2-3: Data structures supported by the DELETE Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|-----------|---|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | The individual registered API provider domain matching the registrationId is deleted. All the individual API provider domain functions of the API provider domain are deleted. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.9.2.3.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.9.2.3.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.9.2.3.3.3 PATCH + +This method shall support the URI query parameters specified in table 8.9.2.3.3.3-1. + +**Table 8.9.2.3.3.3-1: URI query parameters supported by the PATCH method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 8.9.2.3.3.3-2 and the response data structures and response codes specified in table 8.9.2.3.3.3-3. + +**Table 8.9.2.3.3.3-2: Data structures supported by the PATCH Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------------------------|---|-------------|----------------------------------------------| +| APIProviderEnrolmentDetailsPatch | M | 1 | Modified details of the API provider domain. | + +**Table 8.9.2.3.3.3-3: Data structures supported by the PATCH Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|----------------------------------------------------------------------------------------------------------------------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| APIProviderEnrolmentDetails | M | 1 | 200 OK | API provider domain's information updated successfully.

Updated details of the API provider domain is part of the APIProviderEnrolmentDetails, which is provided in the response body. The list of successfully updated individual API provider domain functions, registration update specific failure information of failed API provider domain function registration updates, are included in APIProviderEnrolmentDetails which is provided in the response body. | +| n/a | | | 204 No Content | API provider domain's information modified successfully. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| NOTE: The mandatory HTTP error status codes for the HTTP PATCH method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. | | | | | + +**Table 8.9.2.3.3.3-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.9.2.3.3.3-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +#### 8.9.2.3.4 Resource Custom Operations + +None. + +### 8.9.2A Custom Operations without associated resources + +There are no custom operations without associated resources defined for this API in this release of the specification. + +### 8.9.3 Notifications + +There are no notifications defined for this API in this release of the specification. + +### 8.9.4 Data Model + +#### 8.9.4.1 General + +This clause specifies the application data model supported by the API. Data types listed in clause 7.2 also apply to this API. + +Table 8.9.4.1-1 specifies the data types defined specifically for the CAPIF\_API\_Provider\_Management\_API service. + +**Table 8.9.4.1-1: CAPIF\_API\_Provider\_Management\_API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|----------------------------------|------------------|---------------------------------------------------------------------------------------|---------------| +| APIProviderEnrolmentDetails | Clause 8.9.4.2.2 | Represents the API provider domain's enrolment details. | | +| APIProviderEnrolmentDetailsPatch | Clause 8.9.4.2.5 | Represents the list of modifications for the API provider domain's enrolment details. | PatchUpdate | +| ApiProviderFuncRole | Clause 8.9.4.3.3 | Indicates the role (e.g. AEF, APF, etc.) of an API provider domain function. | | +| APIProviderFunctionDetails | Clause 8.9.4.2.3 | Represents the API provider domain function's details. | | +| RegistrationInformation | Clause 8.9.4.2.4 | Represents registration information of an individual API provider domain function. | | + +Table 8.9.4.1-2 specifies data types re-used by the CAPIF\_API\_Provider\_Management\_API service. + +**Table 8.9.4.1-2: Re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|------------------------------------------------------------------------------------|---------------| +| SupportedFeatures | 3GPP TS 29.571 [19] | Used to negotiate the applicability of optional features defined in table 8.9.6-1. | | + +## 8.9.4.2 Structured data types + +### 8.9.4.2.1 Introduction + +### 8.9.4.2.2 Type: APIProviderEnrolmentDetails + +**Table 8.9.4.2.2-1: Definition of type APIProviderEnrolmentDetails** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|------------------------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| apiProvDomId | string | O | 0..1 | API provider domain ID assigned by the CAPIF core function to the API management function while registering the API provider domain. Shall not be present in the HTTP POST request from the API management function to the CAPIF core function, to on-board itself. Shall be present in all other HTTP requests and responses. | | +| regSec | string | M | 1 | Security information necessary for the CAPIF core function to validate the registration of the API provider domain. Shall be present in HTTP request from API management function to CAPIF core function for API provider domain registration. | | +| apiProvFuncs | array(API ProviderFunctionDetails) | O | 1..N | A list of individual API provider domain functions details. When included by the API management function in the HTTP request message, it lists the API provider domain functions that the API management function intends to register/update in registration or update registration procedure. When included by the CAPIF core function in the HTTP response message, it lists the API domain functions details that are registered or updated successfully. | | +| apiProvDomInfo | string | O | 0..1 | Generic information related to the API provider domain such as details of the API provider applications. | | +| suppFeat | Supported Features | C | 0..1 | Used to negotiate the supported optional features of the API as described in clause 7.8.
This attribute shall be provided in the HTTP POST request and in the response of successful resource creation. | | +| failReason | string | C | 0..1 | Registration or update specific failure information of failed API provider domain function registrations.
Shall be present in the HTTP response body if atleast one of the API provider domain function registration or update registration fails. | | + +## 8.9.4.2.3 Type: APIProviderFunctionDetails + +**Table 8.9.4.2.3-1: Definition of type APIProviderFunctionDetails** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------|-------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| apiProvFuncId | string | C | 0..1 | API provider domain functionID assigned by the CAPIF core function to the API provider domain function while registering/updating the API provider domain. Shall not be present in the HTTP POST request from the API management function to the CAPIF core function, to register itself. Shall be present in all other HTTP requests and responses. | | +| regInfo | RegistrationInformation | M | 1 | Information necessary for the CAPIF core function to register the API provider domain function.

This information shall be present in HTTP POST/PUT request from API management function to CAPIF core function for API provider domain registration. In the HTTP response message from CAPIF core function, shall include the updated registration information for API provider domain function. | | +| apiProvFuncRole | ApiProviderFuncRole | M | 1 | Role of API provider domain function.

The role shall be present in the HTTP POST/PUT request that the API management function intends to register/update the API provider domain function as. CAPIF core function shall register the role of API provider domain function as per the request. | | +| apiProvFuncInfo | string | O | 0..1 | Generic information related to the API provider domain function such as details of the API provider applications. | | + +## 8.9.4.2.4 Type: RegistrationInformation + +**Table 8.9.4.2.4-1: Definition of type RegistrationInformation** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------|---|-------------|-----------------------------------------------------------|---------------| +| apiProvPubKey | string | M | 1 | Public Key of API Provider domain function. | | +| apiProvCert | string | O | 0..1 | API provider domain function's generic client certificate | | + +#### 8.9.4.2.5 Type: APIProviderEnrolmentDetailsPatch + +**Table 8.9.4.2.5-1: Definition of type APIProviderEnrolmentDetailsPatch** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|------------------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| apiProvFuncs | array(API ProviderFunctionDetails) | O | 1..N | A list of individual API provider domain functions details. When included by the API management function in the HTTP request message, it lists the API provider domain functions that the API management function intends to register/update in registration or update registration procedure. | | +| apiProvDomInfo | string | O | 0..1 | Generic information related to the API provider domain such as details of the API provider applications. | | + +#### 8.9.4.3 Simple data types and enumerations + +##### 8.9.4.3.1 Introduction + +This clause defines simple data types and enumerations that will be referenced from data structures defined in the previous clauses. + +##### 8.9.4.3.2 Simple data types + +The simple data types defined in table 8.9.4.3.2-1 shall be supported. + +**Table 8.9.4.3.2-1: Simple data types** + +| Type Name | Type Definition | Description | Applicability | +|-----------|-----------------|-------------|---------------| +| n/a | | | | + +##### 8.9.4.3.3 Enumeration: ApiProviderFuncRole + +**Table 8.9.4.3.3-1: Enumeration ApiProviderFuncRole** + +| Enumeration value | Description | Applicability | +|-------------------|---------------------------------------------------|---------------| +| AEF | API provider function is API Exposing Function. | | +| APF | API provider function is API Publishing Function. | | +| AMF | API provider function is API Management Function. | | + +#### 8.9.5 Error Handling + +##### 8.9.5.1 General + +HTTP error handling shall be supported as specified in clause 7.7. + +In addition, the requirements in the following clauses shall apply. + +##### 8.9.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the CAPIF\_API\_Provider\_Management\_API. + +### 8.9.5.3 Application Errors + +The application errors defined for the CAPIF\_API\_Provider\_Management\_API are listed in table 8.9.5.3-1. + +**Table 8.9.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +### 8.9.6 Feature negotiation + +General feature negotiation procedures are defined in clause 7.8. Table 8.9.6-1 lists the supported features for CAPIF\_API\_Invoker\_Management\_API. + +**Table 8.9.6-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|------------------------------------------------------------------------------------------------------| +| 1 | PatchUpdate | Indicates the support of the PATCH method for updating an API Provider Domain Registration resource. | + +## 8.10 CAPIF\_Routing\_Info\_API + +### 8.10.1 API URI + +The CAPIF\_Routing\_Info\_API service shall use the CAPIF\_Routing\_Info\_API. + +The request URIs used in HTTP requests from the API exposing function towards the CAPIF core function shall have the Resource URI structure as defined in clause 7.5 with the following clarifications: + +- The shall be "capif-routing-info". +- The shall be "v1". +- The shall be set as described in clause 8.10.2. + +All the resource URIs and the custom operation URIs specified in the clauses below are defined relative to the above API URI. + +### 8.10.2 Resources + +#### 8.10.2.1 Overview + +This clause describes the structure for the Resource URIs and the resources and methods used for the service. + +Figure 8.10.2.1-1 depicts the resource URIs structure for the CAPIF\_Routing\_Info\_API. + +![Figure 8.10.2.1-1: Resource URI structure of the CAPIF_Routing_Info_API. The diagram shows a hierarchical tree structure starting with {apiRoot}/capif-routing-info/. A vertical line descends from this root to a horizontal line that branches to /service-apis. From /service-apis, another vertical line descends to a horizontal line that branches to a rounded rectangle containing /{serviceApiId}.](b02ba0b73e95416eb547976f6145b169_img.jpg) + +``` + +graph TD + Root["{apiRoot}/capif-routing-info/"] --> SApis[/service-apis/] + SApis --> ServiceApiId[/{serviceApiId}] + +``` + +Figure 8.10.2.1-1: Resource URI structure of the CAPIF\_Routing\_Info\_API. The diagram shows a hierarchical tree structure starting with {apiRoot}/capif-routing-info/. A vertical line descends from this root to a horizontal line that branches to /service-apis. From /service-apis, another vertical line descends to a horizontal line that branches to a rounded rectangle containing /{serviceApiId}. + +**Figure 8.10.2.1-1: Resource URI structure of the CAPIF\_Routing\_Info\_API** + +Table 8.10.2.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 8.10.2.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|-------------------------------------|------------------------------|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| Individual Service API routing info | /service-apis/{serviceApiId} | GET | Retrieves the API routing information for a published service API and API exposing function which applies the topology hiding. | + +## 8.10.2.2 Resource: Individual Service API routing info + +### 8.10.2.2.1 Description + +The API Routing Information resource represents the API routing information for the service API per API Exposing Function. + +### 8.10.2.2.2 Resource Definition + +Resource URI: {apiRoot}/capif-routing-info//service-apis/{serviceApiId} + +This resource shall support the resource URI variables defined in table 8.10.2.2.2-1. + +**Table 8.10.2.2.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|--------------|-----------|------------------------------------------------| +| apiRoot | string | See clause 7.5 | +| serviceApiId | string | Identifies an individual published service API | + +### 8.10.2.2.3 Resource Standard Methods + +#### 8.10.2.2.3.1 GET + +This method shall support the URI query parameters specified in table 8.10.2.2.3.1-1. + +**Table 8.10.2.2.3.1-1: URI query parameters supported by the GET method on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------|-------------------|---|-------------|-----------------------------------------------------------------| +| aef-id | string | M | 1 | AEF identifier | +| supp-feat | SupportedFeatures | O | 0..1 | To filter irrelevant responses related to unsupported features. | + +This method shall support the request data structures specified in table 8.10.2.2.3.1-2 and the response data structures and response codes specified in table 8.10.2.2.3.1-3. + +**Table 8.10.2.2.3.1-2: Data structures supported by the GET Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 8.10.2.2.3.1-3: Data structures supported by the GET Response Body on this resource** + +| Data type | P | Cardinality | Response Codes | Description | +|-------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RoutingInfo | M | 1 | 200 OK | The Routing information applicable for the service API requested. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during resource retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CAPIF core function. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 8.10.2.2.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +**Table 8.10.2.2.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-----------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CAPIF core function. | + +## 8.10.2.2.4 Resource Custom Operations + +None. + +## 8.10.2A Custom Operations without associated resources + +There are no custom operations without associated resources defined for this API in this release of the specification. + +### 8.10.3 Notifications + +There are no notifications defined for this API in this release of the specification. + +### 8.10.4 Data Model + +#### 8.10.4.1 General + +This clause specifies the application data model supported by the API. Data types listed in clause 7.2 also apply to this API. + +Table 8.10.4.1-1 specifies the data types defined specifically for the CAPIF\_Routing\_Info\_API service. + +**Table 8.10.4.1-1: CAPIF\_Routing\_Info\_API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|------------------|-------------------|-------------------------------------|---------------| +| Ipv6AddressRange | Clause 8.10.4.2.4 | Represents IPv6 address range. | | +| RoutingInfo | Clause 8.10.4.2.2 | Represents API routing information. | | +| RoutingRule | Clause 8.10.4.2.3 | Represents API routing rule. | | + +Table 8.10.4.1-2 specifies data types re-used by the CAPIF\_Routing\_Info\_API service. + +**Table 8.10.4.1-2: Re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|-------------------------------------------------------------------------------------|---------------| +| AefProfile | Clause 8.2.4.2.4 | Used to indicate the AEF profile. | | +| Ipv4AddressRange | 3GPP TS 29.510 [28] | Used to indicate the IPv4 address range. | | +| Ipv6Addr | 3GPP TS 29.122 [14] | Used to indicate the IPv6 address. | | +| SupportedFeatures | 3GPP TS 29.571 [19] | Used to negotiate the applicability of optional features defined in table 8.10.6-1. | | + +#### 8.10.4.2 Structured data types + +##### 8.10.4.2.1 Introduction + +This clause defines data structures to be used in resource representations. + +##### 8.10.4.2.2 Type: RoutingInfo + +**Table 8.10.4.2.2-1: Definition of type RoutingInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|--------------------|---|-------------|---------------|---------------| +| routingRules | array(RoutingRule) | M | 1..N | Routing rules | | + +### 8.10.4.2.3 Type: RoutingRule + +**Table 8.10.4.2.3-1: Definition of type RoutingRule** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-------------------------|---|-------------|-------------------------------------------------------------------------|---------------| +| ipv4AddrRanges | array(Ipv4AddressRange) | O | 1..N | The IPv4 address range for the API invocation source IP address. (NOTE) | | +| ipv6AddrRanges | array(Ipv6AddressRange) | O | 1..N | The IPv6 address range for the API invocation source IP address. (NOTE) | | +| aefProfile | AefProfile | M | 1 | The target AEF profile | | + +NOTE: If no IP address range is provided, it means the service API invocation from any source IP address can be routed to the target AEF. + +### 8.10.4.2.4 Type: Ipv6AddressRange + +**Table 8.10.4.2.4-1: Definition of type Ipv6AddressRange** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|-----------|---|-------------|------------------------------------------------------------|---------------| +| start | Ipv6Addr | M | 1 | First value identifying the start of an IPv6 address range | | +| end | Ipv6Addr | M | 1 | Last value identifying the end of an IPv6 address range | | + +### 8.10.4.3 Simple data types and enumerations + +None. + +## 8.10.5 Error Handling + +### 8.10.5.1 General + +HTTP error handling shall be supported as specified in clause 7.7. + +In addition, the requirements in the following clauses shall apply. + +### 8.10.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the CAPIF\_Routing\_Info\_API. + +### 8.10.5.3 Application Errors + +The application errors defined for the CAPIF\_Routing\_Info\_API are listed in table 8.10.5.3-1. + +**Table 8.10.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +## 8.10.6 Feature negotiation + +General feature negotiation procedures are defined in clause 7.8. + +**Table 8.10.6-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|-------------| +| n/a | | | + +## 9 AEF API Definition + +### 9.1 AEF\_Security\_API + +#### 9.1.1 API URI + +The AEF\_Security\_API service shall use the AEF\_Security\_API. + +The request URIs used in HTTP requests from the API invoker towards the API exposing function shall have the Resource URI structure defined in clause 7.5 with the following clarifications: + +- The shall be "aef-security". +- The shall be "v1". +- The shall be set as described in clause 9.1.2a. + +All the resource URIs and the custom operation URIs specified in the clauses below are defined relative to the above API URI. + +#### 9.1.2 Resources + +There is no resource defined for this API. + +#### 9.1.2A Custom Operations without associated resources + +##### 9.1.2A.1 Overview + +Custom operations used for this API are summarized in table 9.1.2A.1-1. "{apiRoot}" and "" are set as described in clause 7.5 and clause 9.1.1 respectively. + +**Table 9.1.2A.1-1: Custom operations without associated resources** + +| Operation name | Custom operation URI | Mapped HTTP method | Description | +|-----------------------|-----------------------|--------------------|----------------------------------------| +| check-authentication | /check-authentication | POST | Check authentication request. | +| revoke-authentication | /revoke-authorization | POST | Revoke authorization for service APIs. | + +##### 9.1.2A.2 Operation: check-authentication + +###### 9.1.2A.2.1 Description + +This custom operation allows the API invoker to confirm from the API exposing function, that necessary authentication data is available to authenticate the API invoker on API invocation. + +### 9.1.2A.2.2 Operation Definition + +This method shall support the URI query parameters specified in table 9.1.2A.2.2-1. + +**Table 9.1.2A.2.2-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This operation shall support the request and response data structures, and response codes specified in tables 9.1.2A.2.2-2 and 9.1.2A.2.2-3. + +**Table 9.1.2A.2.2-2: Data structures supported by the POST Request Body on this operation** + +| Data type | P | Cardinality | Description | +|------------------------|---|-------------|-----------------------------------| +| CheckAuthenticationReq | M | 1 | Authentication check request data | + +**Table 9.1.2A.2.2-3: Data structures supported by the POST Response Body on this operation** + +| Data type | P | Cardinality | Response codes | Description | +|------------------------|---|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CheckAuthenticationRsp | M | 1 | 200 OK | The request was successful. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during authentication confirmation. The response shall include a Location header field containing an alternative URI of the resource located in an alternative API exposing function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during authentication confirmation. The response shall include a Location header field containing an alternative URI of the resource located in an alternative API exposing function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 9.1.2A.2.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative API exposing function. | + +**Table 9.1.2A.2.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative API exposing function. | + +### 9.1.2A.3 Operation: revoke-authorization + +#### 9.1.2A.3.1 Description + +This custom operation allows the CAPIF core function to request the API exposing function to revoke the authorization of the API invoker for the indicated service APIs. + +### 9.1.2A.3.2 Operation Definition + +This method shall support the URI query parameters specified in table 9.1.2A.3.2-1. + +**Table 9.1.2A.3.2-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This operation shall support the request and response data structures, and response codes specified in tables 9.1.2A.3.2-2 and 9.1.2A.3.2-3. + +**Table 9.1.2A.3.2-2: Data structures supported by the POST Request Body on this operation** + +| Data type | P | Cardinality | Description | +|------------------------|---|-------------|---------------------------------------| +| RevokeAuthorizationReq | M | 1 | Authorization revocation request data | + +**Table 9.1.2A.3.2-3: Data structures supported by the POST Response Body on this operation** + +| Data type | P | Cardinality | Response codes | Description | +|------------------------|---|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RevokeAuthorizationRsp | M | 1 | 200 OK | The request was successful. | +| n/a | | | 307 Temporary Redirect | Temporary redirection, during authorization revocation. The response shall include a Location header field containing an alternative URI of the resource located in an alternative API exposing function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | +| n/a | | | 308 Permanent Redirect | Permanent redirection, during authorization revocation. The response shall include a Location header field containing an alternative URI of the resource located in an alternative API exposing function.
Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [14]. | + +NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [14] also apply. + +**Table 9.1.2A.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative API exposing function. | + +**Table 9.1.2A.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|-------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative API exposing function. | + +### 9.1.3 Notifications + +There are no notifications defined for this API in this release of the specification. + +## 9.1.4 Data Model + +### 9.1.4.1 General + +This clause specifies the application data model supported by the API. Data types listed in clause 7.2 apply to this API. + +Table 9.1.4.1-1 specifies the data types defined specifically for the AEF\_Security\_API service. + +**Table 9.1.4.1-1: AEF\_Security\_API specific Data Types** + +| Data type | Section defined | Description | Applicability | +|------------------------|------------------|----------------------------------------------------|---------------| +| CheckAuthenticationReq | Clause 9.1.4.2.2 | Represents authentication check request data. | | +| CheckAuthenticationRsp | Clause 9.1.4.2.3 | Represents authentication check response data. | | +| RevokeAuthorizationReq | Clause 9.1.4.2.4 | Represents authorization revocation request data. | | +| RevokeAuthorizationRsp | Clause 9.1.4.2.5 | Represents authorization revocation response data. | | + +Table 9.1.4.1-2 specifies data types re-used by the AEF\_Security\_API service. + +**Table 9.1.4.1-2: Re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|----------------------|---------------------|------------------------------------------------------------------------------------|---------------| +| SecurityNotification | Clause 8.5.4.2.5 | Used to indicate information about the revoked APIs. | | +| SupportedFeatures | 3GPP TS 29.571 [19] | Used to negotiate the applicability of optional features defined in table 9.1.6-1. | | + +### 9.1.4.2 Structured data types + +#### 9.1.4.2.1 Introduction + +This clause defines the structures to be used in resource representations for the AEF\_Security\_API. + +#### 9.1.4.2.2 Type: CheckAuthenticationReq + +**Table 9.1.4.2.2-1: Definition of type CheckAuthenticationReq** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|--------------------|---|-------------|---------------------------------------------------------------------------------------------------------|---------------| +| apiInvokerId | string | M | 1 | API invoker ID assigned by the CAPIF core function to the API invoker while onboarding the API invoker. | | +| supportedFeatures | Supported Features | M | 1 | Used to negotiate the supported optional features of the API as described in clause 7.8. | | + +#### 9.1.4.2.3 Type: CheckAuthenticationRsp + +**Table 9.1.4.2.3-1: Definition of type CheckAuthenticationRsp** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|--------------------|---|-------------|------------------------------------------------------------------------------------------|---------------| +| supportedFeatures | Supported Features | M | 1 | Used to negotiate the supported optional features of the API as described in clause 7.8. | | + +#### 9.1.4.2.4 Type: RevokeAuthorizationReq + +**Table 9.1.4.2.4-1: Definition of type RevokeAuthorizationReq** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|----------------------|---|-------------|------------------------------------------------------------------------------------------|---------------| +| revokeInfo | SecurityNotification | M | 1 | It contains detailed revocation information. | | +| supportedFeatures | Supported Features | M | 1 | Used to negotiate the supported optional features of the API as described in clause 7.8. | | + +#### 9.1.4.2.5 Type: RevokeAuthorizationRsp + +**Table 9.1.4.2.5-1: Definition of type RevokeAuthorizationRsp** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|--------------------|---|-------------|------------------------------------------------------------------------------------------|---------------| +| supportedFeatures | Supported Features | M | 1 | Used to negotiate the supported optional features of the API as described in clause 7.8. | | + +#### 9.1.4.3 Simple data types and enumerations + +None. + +### 9.1.5 Error Handling + +#### 9.1.5.1 General + +HTTP error handling shall be supported as specified in clause 7.7. + +In addition, the requirements in the following clauses shall apply. + +#### 9.1.5.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the AEF\_Security\_API. + +#### 9.1.5.3 Application Errors + +The application errors defined for the AEF\_Security\_API are listed in table 9.1.5.3-1. + +**Table 9.1.5.3-1: Application errors** + +| Application Error | HTTP status code | Description | Applicability | +|-------------------|------------------|-------------|---------------| +| | | | | + +### 9.1.6 Feature negotiation + +General feature negotiation procedures are defined in clause 7.8. + +**Table 9.1.6-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|--------------|-------------| +| n/a | | | + +--- + +## 10 Security + +### 10.1 General + +Security methods for CAPIF are specified in 3GPP TS 33.122 [16]. + +### 10.2 CAPIF-1/1e security + +Secure communication between API invoker and CAPIF core function over CAPIF-1/1e reference points, using a TLS protocol based connection is defined in 3GPP TS 33.122 [16]. + +For Onboard\_API\_Invoker service operation of the CAPIF\_API\_Invoker\_Management\_API, the TLS protocol based connection shall be established using server certificate as defined in 3GPP TS 33.122 [16]. + +For rest of the CAPIF APIs, the TLS protocol based connection shall be established with certificate based mutual authentication as defined in 3GPP TS 33.122 [16]. + +### 10.3 CAPIF-2/2e security and securely invoking service APIs + +For secure communication between API invoker and API exposing function and ensuring secure invocations of service APIs, the API invoker: + +- shall negotiate the security method with the CAPIF core function using the Obtain\_Security\_Method service operation of the CAPIF\_Security\_API; +- shall initiate the authentication with the API exposing function using the Initiate\_Authentication service operation of the AEF\_Security\_API; and +- shall establish a secure connection with the API exposing function as defined in 3GPP TS 33.122 [16], using the method negotiated with the CAPIF core function. + +--- + +## Annex A (normative): OpenAPI specification + +### A.1 General + +This Annex is based on the OpenAPI Specification [3] and provides corresponding representations of all APIs defined in the present specification, in YAML format. + +This Annex shall take precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API. + +- NOTE: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply. + +Informative copies of the OpenAPI specification file contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5B of 3GPP TR 21.900 [27] and clause 5.3.1 of 3GPP TS 29.501 [18] for further information). + +--- + +### A.2 CAPIF\_Discover\_Service\_API + +openapi: 3.0.0 + +``` +info: + title: CAPIF_Discover_Service_API + description: | + API for discovering service APIs. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + version: "1.3.0-alpha.2" + +externalDocs: + description: 3GPP TS 29.222 V18.4.0 Common API Framework for 3GPP Northbound APIs + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.222/ + +servers: + - url: '{apiRoot}/service-apis/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 7.5 of 3GPP TS 29.222. + +paths: + /allServiceAPIs: + get: + description: > + Discover published service APIs and retrieve a collection of APIs according + to certain filter criteria. + parameters: + - name: api-invoker-id + in: query + description: > + String identifying the API invoker assigned by the CAPIF core function. + It also represents the CCF identifier in the CAPIF-6/6e interface. + required: true + schema: + type: string + - name: api-name + in: query + description: > + API name, it is set as {apiName} part of the URI structure as defined + in clause 5.2.4 of 3GPP TS 29.122. + schema: + type: string + - name: api-version + in: query + description: API major version the URI (e.g. v1). + schema: + type: string + - name: comm-type + in: query + description: Communication type used by the API (e.g. REQUEST_RESPONSE). + schema: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/CommunicationType' + - name: protocol + in: query + description: Protocol used by the API. + schema: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/Protocol' + - name: aef-id + in: query + description: AEF identifier. + schema: + type: string + - name: data-format + in: query + description: Data formats used by the API (e.g. serialization protocol JSON used). + schema: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/DataFormat' + - name: api-cat + in: query + description: The service API category to which the service API belongs to. + schema: + type: string + - name: preferred-aef-loc + in: query + description: The preferred AEF location. + content: + application/json: + schema: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/AefLocation' +``` + +``` + +- name: req-api-prov-name + in: query + description: Represents the required API provider name. + schema: + type: string +- name: supported-features + in: query + description: Features supported by the NF consumer for the CAPIF Discover Service API. + schema: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' +- name: api-supported-features + in: query + description: > + Features supported by the discovered service API indicated by api-name parameter. + This may only be present if api-name query parameter is present. + schema: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' +- name: ue-ip-addr + in: query + description: Represents the UE IP address information. + schema: + $ref: '#/components/schemas/IpAddrInfo' +- name: service-kpis + in: query + description: > + Contains information about service characteristics provided by the targeted + service API(s). + schema: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/ServiceKpis' +responses: + '200': + description: > + The response body contains the result of the search over the list of registered APIs. + content: + application/json: + schema: + $ref: '#/components/schemas/DiscoveredAPIs' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '414': + $ref: 'TS29122_CommonData.yaml#/components/responses/414' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + schemas: + DiscoveredAPIs: + type: object + description: > + Represents a list of APIs currently registered in the CAPIF core function + and satisfying a number of filter criteria provided by the API consumer. + properties: + serviceAPIDescriptions: + type: array + items: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/ServiceAPIDescription' + minItems: 1 + description: > + Description of the service API as published by the service. Each service + API description shall include AEF profiles matching the filter criteria. + +``` + +``` + +IpAddrInfo: + type: object + description: Represents the UE IP address information. + properties: + ipv4Addr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv4Addr' + ipv6Addr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv6Addr' + oneOf: + - required: [ipv4Addr] + - required: [ipv6Addr] + +``` + +## A.3 CAPIF\_Publish\_Service\_API + +openapi: 3.0.0 + +``` + +info: + title: CAPIF_Publish_Service_API + description: | + API for publishing service APIs. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + version: "1.3.0-alpha.4" + +``` + +``` + +externalDocs: + description: 3GPP TS 29.222 V18.4.0 Common API Framework for 3GPP Northbound APIs + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.222/ + +``` + +``` + +servers: + - url: '{apiRoot}/published-apis/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 7.5 of 3GPP TS 29.222. + +``` + +``` + +paths: + # APF published API + /{apfId}/service-apis: + post: + description: Publish a new API. + parameters: + - name: apfId + in: path + required: true + schema: + type: string + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceAPIDescription' + responses: + '201': + description: > + Service API published successfully The URI of the created resource + shall be returned in the "Location" HTTP header. + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceAPIDescription' + headers: + Location: + description: > + Contains the URI of the newly created resource, according to the structure + {apiRoot}/published-apis/v1/{apfId}/service-apis/{serviceApiId} + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + +``` + +``` + + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +get: + description: Retrieve all published APIs. + parameters: + - name: apfId + in: path + required: true + schema: + type: string + responses: + '200': + description: Definition of all service API(s) published by the API publishing function. + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/ServiceAPIDescription' + minItems: 0 + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +# Individual APF published API +/{apfId}/service-apis/{serviceApiId}: + get: + description: Retrieve a published service API. + parameters: + - name: serviceApiId + in: path + required: true + schema: + type: string + - name: apfId + in: path + required: true + schema: + type: string + responses: + '200': + description: > + Definition of individual service API published by the API publishing function. + content: + application/json: + +``` + +``` + + schema: + $ref: '#/components/schemas/ServiceAPIDescription' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +put: + description: Update a published service API. + parameters: + - name: serviceApiId + in: path + required: true + schema: + type: string + - name: apfId + in: path + required: true + schema: + type: string + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceAPIDescription' + responses: + '200': + description: Definition of service API updated successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceAPIDescription' + '204': + description: No Content + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +``` + +``` + +patch: + description: Modify an existing published service API. + operationId: ModifyIndAPFPubAPI + tags: + - Individual APF published API + parameters: + - name: serviceApiId + in: path + required: true + schema: + type: string + - name: apfId + in: path + required: true + schema: + type: string + requestBody: + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/ServiceAPIDescriptionPatch' + responses: + '200': + description: > + The definition of the service API is modified successfully and a + representation of the updated service API is returned in the request body. + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceAPIDescription' + '204': + description: No Content. The definition of the service API is modified successfully. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +delete: + description: Unpublish a published service API. + parameters: + - name: serviceApiId + in: path + required: true + schema: + type: string + - name: apfId + in: path + required: true + schema: + type: string + responses: + '204': + description: The individual published service API matching the serviceApiId is deleted. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + +``` + +``` +$ref: 'TS29122_CommonData.yaml#/components/responses/308' +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +# Components + +components: + schemas: +# Data Type for representations + ServiceAPIDescription: + type: object + description: Represents the description of a service API as published by the APF. + properties: + apiName: + type: string + description: > + API name, it is set as {apiName} part of the URI structure as defined in + clause 5.2.4 of 3GPP TS 29.122. + apiId: + type: string + description: > + API identifier assigned by the CAPIF core function to the published service API. + Shall not be present in the HTTP POST request from the API publishing function + to the CAPIF core function. Shall be present in the HTTP POST response from the + CAPIF core function to the API publishing function and in the HTTP GET response + from the CAPIF core function to the API invoker (discovery API). + apiStatus: + $ref: '#/components/schemas/ApiStatus' + aefProfiles: + type: array + items: + $ref: '#/components/schemas/AefProfile' + minItems: 1 + description: > + AEF profile information, which includes the exposed API details (e.g. protocol). + description: + type: string + description: Text description of the API + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + shareableInfo: + $ref: '#/components/schemas/ShareableInformation' + serviceAPICategory: + type: string + description: The service API category to which the service API belongs to. + apiSuppFeats: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + pubApiPath: + $ref: '#/components/schemas/PublishedApiPath' + ccfId: + type: string + description: CAPIF core function identifier. + required: + - apiName + + InterfaceDescription: + type: object + description: Represents the description of an API's interface. + properties: + ipv4Addr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv4Addr' + ipv6Addr: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv6Addr' + fqdn: +``` + +``` +$ref: 'TS29571_CommonData.yaml#/components/schemas/Fqdn' +port: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Port' +apiPrefix: + type: string + description: > + A string representing a sequence of path segments that starts with the slash character. +securityMethods: + type: array + items: + $ref: '#/components/schemas/SecurityMethod' + minItems: 1 + description: > + Security methods supported by the interface, it take precedence over + the security methods provided in AefProfile, for this specific interface. +oneOf: +- required: [ipv4Addr] +- required: [ipv6Addr] +- required: [fqdn] + +AefProfile: + type: object + description: Represents the AEF profile data. + properties: + aefId: + type: string + description: Identifier of the API exposing function + versions: + type: array + items: + $ref: '#/components/schemas/Version' + minItems: 1 + description: API version + protocol: + $ref: '#/components/schemas/Protocol' + dataFormat: + $ref: '#/components/schemas/DataFormat' + securityMethods: + type: array + items: + $ref: '#/components/schemas/SecurityMethod' + minItems: 1 + description: Security methods supported by the AEF + domainName: + type: string + description: Domain to which API belongs to + interfaceDescriptions: + type: array + items: + $ref: '#/components/schemas/InterfaceDescription' + minItems: 1 + description: Interface details + aefLocation: + $ref: '#/components/schemas/AefLocation' + serviceKpis: + $ref: '#/components/schemas/ServiceKpis' + ueIpRange: + $ref: '#/components/schemas/IpAddrRange' + required: + - aefId + - versions + oneOf: + - required: [domainName] + - required: [interfaceDescriptions] + +Resource: + type: object + description: Represents the API resource data. + properties: + resourceName: + type: string + description: Resource name + commType: + $ref: '#/components/schemas/CommunicationType' + uri: + type: string + description: > + Relative URI of the API resource, it is set as {apiSpecificSuffixes} part +``` + +``` + + of the URI structure as defined in clause 5.2.4 of 3GPP TS 29.122. +custOpName: + type: string + description: > + it is set as {custOpName} part of the URI structure for a custom operation + associated with a resource as defined in clause 5.2.4 of 3GPP TS 29.122. +custOperations: + type: array + items: + $ref: '#/components/schemas/CustomOperation' + minItems: 1 + description: > + Custom operations associated with this resource. +operations: + type: array + items: + $ref: '#/components/schemas/Operation' + minItems: 1 + description: > + Supported HTTP methods for the API resource. Only applicable when the + protocol in AefProfile indicates HTTP. +description: + type: string + description: Text description of the API resource +required: +- resourceName +- commType +- uri + +CustomOperation: + type: object + description: Represents the description of a custom operation. + properties: + commType: + $ref: '#/components/schemas/CommunicationType' + custOpName: + type: string + description: > + it is set as {custOpName} part of the URI structure for a custom operation + without resource association as defined in clause 5.2.4 of 3GPP TS 29.122. + operations: + type: array + items: + $ref: '#/components/schemas/Operation' + minItems: 1 + description: > + Supported HTTP methods for the API resource. Only applicable when the + protocol in AefProfile indicates HTTP. + description: + type: string + description: Text description of the custom operation + required: + - commType + - custOpName + +Version: + type: object + description: Represents the API version information. + properties: + apiVersion: + type: string + description: API major version in URI (e.g. v1) + expiry: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + resources: + type: array + items: + $ref: '#/components/schemas/Resource' + minItems: 1 + description: Resources supported by the API. + custOperations: + type: array + items: + $ref: '#/components/schemas/CustomOperation' + minItems: 1 + description: Custom operations without resource association. + required: + - apiVersion + +``` + +``` +ShareableInformation: + type: object + description: > + Indicates whether the service API and/or the service API category can be shared + to the list of CAPIF provider domains. + properties: + isShareable: + type: boolean + description: > + Set to "true" indicates that the service API and/or the service API + category can be shared to the list of CAPIF provider domain information. + Otherwise set to "false". + capifProvDoms: + type: array + items: + type: string + minItems: 1 + description: > + List of CAPIF provider domains to which the service API information to be shared. + required: + - isShareable + +PublishedApiPath: + type: object + description: Represents the published API path within the same CAPIF provider domain. + properties: + ccfIds: + type: array + items: + type: string + minItems: 1 + description: A list of CCF identifiers where the service API is already published. + +AefLocation: + description: > + Represents the location information (e.g. civic address, GPS coordinates, data center ID) + where the AEF providing the service API is located. + type: object + properties: + civicAddr: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/CivicAddress' + geoArea: + $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea' + dcId: + type: string + description: > + Identifies the data center where the AEF providing the service API is located. + +ServiceAPIDescriptionPatch: + type: object + description: > + Represents the parameters to request the modification of an APF published API resource. + properties: + apiStatus: + $ref: '#/components/schemas/ApiStatus' + aefProfiles: + type: array + items: + $ref: '#/components/schemas/AefProfile' + description: AEF profile information, which includes the exposed API details. + minItems: 1 + description: + type: string + description: Text description of the API + shareableInfo: + $ref: '#/components/schemas/ShareableInformation' + serviceAPICategory: + type: string + description: The service API category to which the service API belongs to. + apiSuppFeats: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + pubApiPath: + $ref: '#/components/schemas/PublishedApiPath' + ccfId: + type: string + description: CAPIF core function identifier. +``` + +``` + +ApiStatus: + type: object + description: > + Represents the API status. + properties: + aefIds: + type: array + items: + type: string + description: > + Indicates the list of AEF ID(s) where the API is active. + If this attribute is omitted, the API is inactive at all AEF(s) + defined in the "aefProfiles" attribute within + the ServiceAPIDescription data structure. + required: + - aefIds + +ServiceKpis: + type: object + description: > + Represents information about the service characteristics provided by a service API. + properties: + maxReqRate: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + description: > + Unsigned integer identifying maximum request rate per second from the API Invoker + supported by the server. + maxRestime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + availability: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + avalComp: + type: string + pattern: '^\\d+(\\.\\d+)? (kFLOPS|MFLOPS|GFLOPS|TFLOPS|PFLOPS|EFLOPS|ZFLOPS)$' + description: > + The maximum compute resource available in FLOPS for the API Invoker. + avalGraComp: + type: string + pattern: '^\\d+(\\.\\d+)? (kFLOPS|MFLOPS|GFLOPS|TFLOPS|PFLOPS|EFLOPS|ZFLOPS)$' + description: > + The maximum graphical compute resource in FLOPS available for the API Invoker. + avalMem: + type: string + pattern: '^\\d+(\\.\\d+)? (KB|MB|GB|TB|PB|EB|ZB|YB)$' + description: > + The maximum memory resource available for the API Invoker. + avalStor: + type: string + pattern: '^\\d+(\\.\\d+)? (KB|MB|GB|TB|PB|EB|ZB|YB)$' + description: > + The maximum storage resource available for the API Invoker. + conBand: + $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger' + description: > + The connection bandwidth in kbps advertised for the API Invoker's use. + +IpAddrRange: + description: Represents the list of public IP ranges + type: object + properties: + ueIpv4AddrRanges: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4AddressRange' + description: Represents the IPv4 Address ranges of the UE(s). + minItems: 1 + ueIpv6AddrRanges: + type: array + items: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6AddressRange' + description: Represents the Ipv6 Address ranges of the UE(s). + minItems: 1 + anyOf: + - required: [ueIpv4AddrRanges] + - required: [ueIpv6AddrRanges] + +Protocol: + anyOf: + +``` + +``` +- type: string +enum: + - HTTP_1_1 + - HTTP_2 + - MQTT + - WEBSOCKET +- type: string +description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Indicates a protocol and protocol version used by the API. + Possible values are: + - HTTP_1_1: Indicates that the protocol is HTTP version 1.1. + - HTTP_2: Indicates that the protocol is HTTP version 2. + - MQTT: Indicates that the protocol is Message Queuing Telemetry Transport. + - WEBSOCKET: Indicates that the protocol is Websocket. + +CommunicationType: +anyOf: +- type: string +enum: + - REQUEST_RESPONSE + - SUBSCRIBE_NOTIFY +- type: string +description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Indicates a communication type of the resource or the custom operation. + Possible values are: + - REQUEST_RESPONSE: The communication is of the type request-response. + - SUBSCRIBE_NOTIFY: The communication is of the type subscribe-notify. + +DataFormat: +anyOf: +- type: string +enum: + - JSON + - XML + - PROTOBUF3 +- type: string +description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Indicates a data format. + Possible values are: + - JSON: Indicates that the data format is JSON. + - XML: Indicates that the data format is Extensible Markup Language. + - PROTOBUF3: Indicates that the data format is Protocol buffers version 3. + +SecurityMethod: +anyOf: +- type: string +enum: + - PSK + - PKI + - OAUTH +- type: string +description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Indicates the security method. + Possible values are: + - PSK: Security method 1 (Using TLS-PSK) as described in 3GPP TS 33.122. + - PKI: Security method 2 (Using PKI) as described in 3GPP TS 33.122. + - OAUTH: Security method 3 (TLS with OAuth token) as described in 3GPP TS 33.122. + +Operation: +anyOf: +- type: string +enum: +``` + +``` + + - GET + - POST + - PUT + - PATCH + - DELETE +- type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. +description: | + Indicates an HTTP method. +Possible values are: +- GET: HTTP GET method. +- POST: HTTP POST method. +- PUT: HTTP PUT method. +- PATCH: HTTP PATCH method. +- DELETE: HTTP DELETE method. + +``` + +## A.4 CAPIF\_Events\_API + +openapi: 3.0.0 + +``` + +info: + title: CAPIF_Events_API + description: | + API for event subscription management. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + version: "1.3.0-alpha.4" + +externalDocs: + description: 3GPP TS 29.222 V18.4.0 Common API Framework for 3GPP Northbound APIs + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.222/ + +servers: +- url: '{apiRoot}/capif-events/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 7.5 of 3GPP TS 29.222 + +paths: + /{subscriberId}/subscriptions: + post: + description: Creates a new individual CAPIF Event Subscription. + parameters: + - name: subscriberId + in: path + description: Identifier of the Subscriber + required: true + schema: + type: string + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/EventSubscription' + callbacks: + notificationDestination: + '{request.body#/notificationDestination}': + post: + requestBody: # contents of the callback message + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/EventNotification' + responses: + '204': + description: No Content (successful notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + +``` + +``` + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +responses: + '201': + description: Created (Successful creation of subscription) + content: + application/json: + schema: + $ref: '#/components/schemas/EventSubscription' + headers: + Location: + description: > + Contains the URI of the newly created resource, according to the structure + {apiRoot}/capif-events/v1/{subscriberId}/subscriptions/{subscriptionId} + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/{subscriberId}/subscriptions/{subscriptionId}: + delete: + description: Deletes an individual CAPIF Event Subscription. + parameters: + - name: subscriberId + in: path + description: Identifier of the Subscriber + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Identifier of an individual Events Subscription + required: true + schema: + type: string + responses: +``` + +``` + +'204': + description: > + The individual CAPIF Events Subscription matching the subscriptionId is deleted. +'307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' +'308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +put: + description: Update of an existing individual CAPIF Event Subscription. + parameters: + - name: subscriberId + in: path + description: Identifier of the Subscriber + required: true + schema: + type: string + - name: subscriptionId + in: path + description: Identifier of the individual Subscriber + required: true + schema: + type: string + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/EventSubscription' + responses: + '200': + description: OK (Successful update of the subscription). + content: + application/json: + schema: + $ref: '#/components/schemas/EventSubscription' + '204': + description: No Content + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +patch: + +``` + +``` +description: Modification of an existing individual CAPIF Event Subscription. +parameters: +- name: subscriberId + in: path + description: Identifier of the Subscriber + required: true + schema: + type: string +- name: subscriptionId + in: path + description: Identifier of the individual Subscriber + required: true + schema: + type: string +requestBody: + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/EventSubscriptionPatch' +responses: + '200': + description: OK (Successful update of the subscription) + content: + application/json: + schema: + $ref: '#/components/schemas/EventSubscription' + '204': + description: No Content + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + schemas: + EventSubscription: + type: object + description: Represents an individual CAPIF Event Subscription resource. + properties: + events: + type: array + items: + $ref: '#/components/schemas/CAPIFEvent' + minItems: 1 + description: Subscribed events + eventFilters: + type: array + items: + $ref: '#/components/schemas/CAPIFEventFilter' + minItems: 1 + description: Subscribed event filters + eventReq: + $ref: 'TS29523_Npcf_EventExposure.yaml#/components/schemas/ReportingInformation' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + requestTestNotification: + type: boolean + description: > + Set to true by Subscriber to request the CAPIF core function to send a +``` + +``` + test notification as defined in in clause 7.6. Set to false or omitted otherwise. + websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - events + - notificationDestination + +EventNotification: + type: object + description: Represents an individual CAPIF Event notification. + properties: + subscriptionId: + type: string + description: > + Identifier of the subscription resource to which the notification + is related - CAPIF resource identifier + events: + $ref: '#/components/schemas/CAPIFEvent' + eventDetail: + $ref: '#/components/schemas/CAPIFEventDetail' + required: + - subscriptionId + - events + +CAPIFEventFilter: + type: object + description: Represents a CAPIF event filter. + properties: + apiIds: + type: array + items: + type: string + minItems: 1 + description: Identifier of the service API + apiInvokerIds: + type: array + items: + type: string + minItems: 1 + description: Identity of the API invoker + aefIds: + type: array + items: + type: string + minItems: 1 + description: Identifier of the API exposing function + +CAPIFEventDetail: + type: object + description: Represents a CAPIF event details. + properties: + serviceAPIDescriptions: + type: array + items: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/ServiceAPIDescription' + minItems: 1 + description: Description of the service API as published by the APF. + apiIds: + type: array + items: + type: string + minItems: 1 + description: Identifier of the service API + apiInvokerIds: + type: array + items: + type: string + minItems: 1 + description: Identity of the API invoker + accCtrlPolList: + $ref: '#/components/schemas/AccessControlPolicyListExt' + invocationLogs: + type: array + items: + $ref: 'TS29222_CAPIF_Logging_API_Invocation_API.yaml#/components/schemas/InvocationLog' + minItems: 1 +``` + +``` + + description: Invocation logs. + apiTopoHide: + $ref: '#/components/schemas/TopologyHiding' + +AccessControlPolicyListExt: + description: Represents the extension for access control policies. + allOf: + - $ref: 'TS29222_CAPIF_Access_Control_Policy_API.yaml#/components/schemas/AccessControlPolicyList' + - type: object + properties: + apiId: + type: string + required: + - apiId + +TopologyHiding: + type: object + description: Represents the routing rules information of a service API. + properties: + apiId: + type: string + routingRules: + type: array + items: + $ref: 'TS29222_CAPIF_Routing_Info_API.yaml#/components/schemas/RoutingRule' + minItems: 1 + required: + - apiId + - routingRules + +EventSubscriptionPatch: + type: object + description: > + Represents the parameters to request the updated of an individual CAPIF Event + Subscription resource. + properties: + events: + type: array + items: + $ref: '#/components/schemas/CAPIFEvent' + minItems: 1 + description: Subscribed events + eventFilters: + type: array + items: + $ref: '#/components/schemas/CAPIFEventFilter' + minItems: 1 + description: Subscribed event filters + eventReq: + $ref: 'TS29523_Npcf_EventExposure.yaml#/components/schemas/ReportingInformation' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + +CAPIFEvent: + anyOf: + - type: string + enum: + - SERVICE_API_AVAILABLE + - SERVICE_API_UNAVAILABLE + - SERVICE_API_UPDATE + - API_INVOKER_ONBOARDED + - API_INVOKER_OFFBOARDED + - SERVICE_API_INVOCATION_SUCCESS + - SERVICE_API_INVOCATION_FAILURE + - ACCESS_CONTROL_POLICY_UPDATE + - ACCESS_CONTROL_POLICY_UNAVAILABLE + - API_INVOKER AUTHORIZATION_REVOKED + - API_INVOKER_UPDATED + - API_TOPOLOGY HIDING_CREATED + - API_TOPOLOGY HIDING_REVOKED + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Describes the CAPIF event. + +``` + +Possible values are: + +- SERVICE\_API\_AVAILABLE: +Events related to the availability of service APIs after the service APIs are published. +- SERVICE\_API\_UNAVAILABLE: +Events related to the unavailability of service APIs after the service APIs are unpublished. +- SERVICE\_API\_UPDATE: Events related to change in service API information. +- API\_INVOCKER\_ONBOARDED: Events related to API invoker onboarded to CAPIF. +- API\_INVOCKER\_OFFBOARDED: Events related to API invoker offboarded from CAPIF. +- SERVICE\_API\_INVOCATION\_SUCCESS: +Events related to the successful invocation of service APIs. +- SERVICE\_API\_INVOCATION\_FAILURE: Events related to the failed invocation of service APIs. +- ACCESS\_CONTROL\_POLICY\_UPDATE: +Events related to the update for the access control policy related to the service APIs. +- ACCESS\_CONTROL\_POLICY\_UNAVAILABLE: +Events related to the unavailability of the access control policy related to the service APIs. +- API\_INVOCKER\_AUTHORIZATION\_REVOKED: Events related to the revocation of the authorization of API invokers to access the service APIs. +- API\_INVOCKER\_UPDATED: Events related to API invoker profile updated to CAPIF. +- API\_TOPOLOGY HIDING\_CREATED: +Events related to the creation or update of the API topology hiding information of the service APIs after the service APIs are published. +- API\_TOPOLOGY HIDING\_REVOKED: +Events related to the revocation of the API topology hiding information of the service APIs after the service APIs are unpublished. + +## A.5 CAPIF\_API\_Invoker\_Management\_API + +openapi: 3.0.0 + +``` + +info: + title: CAPIF_API_Invoker_Management_API + description: | + API for API invoker management. + © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + version: "1.3.0-alpha.1" + +externalDocs: + description: 3GPP TS 29.222 V18.0.0 Common API Framework for 3GPP Northbound APIs + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.222/ + +servers: + - url: '{apiRoot}/api-invoker-management/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 7.5 of 3GPP TS 29.222 + +paths: + /onboardedInvokers: + post: + description: Creates a new individual API Invoker profile. + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/APIInvokerEnrolmentDetails' + callbacks: + notificationDestination: + '{request.body#/notificationDestination}': + post: + description: Notify the API Invoker about the onboarding completion + requestBody: # contents of the callback message + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/OnboardingNotification' + responses: + '204': + description: No Content (successful onboarding notification) + +``` + +``` + + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +responses: + '201': + description: API invoker on-boarded successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/APIInvokerEnrolmentDetails' + headers: + Location: + description: > + Contains the URI of the newly created resource, according to the structure + {apiRoot}/api-invoker-management/v1/onboardedInvokers/{onboardingId} + required: true + schema: + type: string + '202': + description: The CAPIF core has accepted the Onboarding request and is processing it. + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/onboardedInvokers/{onboardingId}: + delete: + description: Deletes an individual API Invoker. + parameters: + - name: onboardingId + in: path + description: String identifying an individual on-boarded API invoker resource + required: true + schema: + type: string + responses: + '204': + +``` + +``` + + description: The individual API Invoker matching onboardingId was offboarded. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +put: + description: Updates an individual API invoker details. + parameters: + - name: onboardingId + in: path + description: String identifying an individual on-boarded API invoker resource + required: true + schema: + type: string + requestBody: + description: representation of the API invoker details to be updated in CAPIF core function + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/APIInvokerEnrolmentDetails' + callbacks: + notificationDestination: + '{request.body#/notificationDestination}': + post: + description: Notify the API Invoker about the API invoker update completion + requestBody: # contents of the callback message + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/OnboardingNotification' + responses: + '204': + description: No Content (successful API invoker update notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +responses: + +``` + +``` +'200': + description: API invoker details updated successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/APIInvokerEnrolmentDetails' +'202': + description: > + The CAPIF core has accepted the API invoker update details request and is processing it. +'204': + description: > + API invoker's information updated successfully, with no content to be + sent in the response body. +'307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' +'308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' +'400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' +'401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' +'403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +patch: + description: Modify an individual API invoker details. + operationId: ModifyIndApiInvokeEnrolment + tags: + - Individual API Invoker enrolment details + parameters: + - name: onboardingId + in: path + required: true + schema: + type: string + requestBody: + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/APIInvokerEnrolmentDetailsPatch' + responses: + '200': + description: > + The definition of the service API is modified successfully and a + representation of the updated service API is returned in the request body. + content: + application/json: + schema: + $ref: '#/components/schemas/APIInvokerEnrolmentDetails' + '202': + description: The request is accepted and under processing. + '204': + description: No Content. The definition of the service API is modified successfully. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': +``` + +``` + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +components: + schemas: + OnboardingInformation: + type: object + description: Represents on-boarding information of the API invoker. + properties: + apiInvokerPublicKey: + type: string + description: The API Invoker's public key + apiInvokerCertificate: + type: string + description: > + The API Invoker's generic client certificate, provided by the CAPIF core function. + onboardingSecret: + type: string + description: > + The API Invoker's onboarding secret, provided by the CAPIF core function. + required: + - apiInvokerPublicKey + + APIList: + type: object + description: Represents a list of APIs. + properties: + serviceAPIDescriptions: + type: array + items: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/ServiceAPIDescription' + minItems: 1 + description: Represents the list of service APIs that the API Invoker is allowed to +invoke. + + APIInvokerEnrolmentDetails: + type: object + properties: + apiInvokerId: + type: string + description: > + API invoker ID assigned by the CAPIF core function to the API invoker while + on-boarding the API invoker. Shall not be present in the HTTP POST request + from the API invoker to the CAPIF core function, to on-board itself. Shall be + present in all other HTTP requests and responses. + readOnly: true + onboardingInformation: + $ref: '#/components/schemas/OnboardingInformation' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + requestTestNotification: + type: boolean + description: > + Set to true by Subscriber to request the CAPIF core function to send a + test notification as defined in in clause 7.6. Set to false or omitted otherwise. + websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' + apiList: + $ref: '#/components/schemas/APIList' + apiInvokerInformation: + type: string + description: > + Generic information related to the API invoker such as details of + the device or the application. +``` + +``` + + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - onboardingInformation + - notificationDestination + description: Represents information about the API Invoker that requested to onboard. + +OnboardingNotification: + type: object + description: Represents a notification of on-boarding or update result. + properties: + result: + type: boolean + description: Set to "true" indicate successful on-boarding. Otherwise set to "false" + resourceLocation: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + apiInvokerEnrolmentDetails: + $ref: '#/components/schemas/APIInvokerEnrolmentDetails' + apiList: + $ref: '#/components/schemas/APIList' + required: + - result + +APIInvokerEnrolmentDetailsPatch: + type: object + description: Represents an API Invoker's enrolment details to be updated. + properties: + onboardingInformation: + $ref: '#/components/schemas/OnboardingInformation' + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + apiList: + $ref: '#/components/schemas/APIList' + apiInvokerInformation: + type: string + description: > + Generic information related to the API invoker such as details of + the device or the application. + +``` + +## A.6 CAPIF\_Security\_API + +openapi: 3.0.0 + +``` + +info: + title: CAPIF_Security_API + description: | + API for CAPIF security management. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + version: "1.3.0-alpha.3" + +externalDocs: + description: 3GPP TS 29.222 V18.4.0 Common API Framework for 3GPP Northbound APIs + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.222/ + +servers: +- url: '{apiRoot}/capif-security/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 7.5 of 3GPP TS 29.222. + +paths: +/trustedInvokers/{apiInvokerId}: + get: + parameters: + - name: apiInvokerId + in: path + description: Identifier of an individual API invoker + required: true + schema: + type: string + - name: authenticationInfo + in: query + description: > + +``` + +``` + + When set to 'true', it indicates the CAPIF core function to send the + authentication information of the API invoker. Set to false or omitted otherwise. + schema: + type: boolean +- name: authorizationInfo + in: query + description: > + When set to 'true', it indicates the CAPIF core function to send the + authorization information of the API invoker. Set to false or omitted otherwise. + schema: + type: boolean +responses: + '200': + description: > + The security related information of the API Invoker based on the request + from the API exposing function. + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceSecurity' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '414': + $ref: 'TS29122_CommonData.yaml#/components/responses/414' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +put: + parameters: + - name: apiInvokerId + in: path + description: Identifier of an individual API invoker + required: true + schema: + type: string + requestBody: + description: create a security context for an API invoker + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceSecurity' + callbacks: + notificationDestination: + '{request.body#/notificationDestination}': + post: + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SecurityNotification' + responses: + '204': + description: No Content (successful notification) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + +``` + +``` + + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +responses: + '201': + description: Successful created. + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceSecurity' + headers: + Location: + description: > + Contains the URI of the newly created resource, according to the structure + {apiRoot}/capif-security/v1/trustedInvokers/{apiInvokerId} + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '414': + $ref: 'TS29122_CommonData.yaml#/components/responses/414' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +delete: + parameters: + - name: apiInvokerId + in: path + description: Identifier of an individual API invoker + required: true + schema: + type: string + responses: + '204': + description: No Content (Successful deletion of the existing subscription) + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + +``` + +``` +'404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' +'429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/trustedInvokers/{apiInvokerId}/update: + post: + parameters: + - name: apiInvokerId + in: path + description: Identifier of an individual API invoker + required: true + schema: + type: string + requestBody: + description: Update the security context (e.g. re-negotiate the security methods). + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceSecurity' + responses: + '200': + description: Successful updated. + content: + application/json: + schema: + $ref: '#/components/schemas/ServiceSecurity' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/trustedInvokers/{apiInvokerId}/delete: + post: + parameters: + - name: apiInvokerId + in: path + description: Identifier of an individual API invoker + required: true + schema: + type: string + requestBody: + description: Revoke the authorization of the API invoker for APIs. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SecurityNotification' + responses: + '204': +``` + +``` + description: Successful revoked. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/securityId/token: + post: + parameters: + - name: securityId + in: path + description: Identifier of an individual API invoker + required: true + schema: + type: string + requestBody: + required: true + content: + application/x-www-form-urlencoded: + schema: + $ref: '#/components/schemas/AccessTokenReq' + responses: + '200': + description: Successful Access Token Request + content: + application/json: + schema: + $ref: '#/components/schemas/AccessTokenRsp' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + description: Error in the Access Token Request + content: + application/json: + schema: + $ref: '#/components/schemas/AccessTokenErr' + '401': + description: Unauthorized + content: + application/json: + schema: + $ref: '#/components/schemas/AccessTokenErr' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' +``` + +``` + + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + +components: + schemas: + ServiceSecurity: + type: object + description: > + Represents the details of the security method for each service API interface. + When included by the API invoker, it indicates the preferred method of security. + When included by the CAPIF core function, it indicates the security method to be + used for the service API interface. + properties: + securityInfo: + type: array + items: + $ref: '#/components/schemas/SecurityInformation' + minimum: 1 + notificationDestination: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + requestTestNotification: + type: boolean + description: > + Set to true by API invoker to request the CAPIF core function to send a + test notification as defined in in clause 7.6. Set to false or omitted otherwise. + websocketNotifConfig: + $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - securityInfo + - notificationDestination + + SecurityInformation: + type: object + description: Represents the interface details and the security method. + properties: + interfaceDetails: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/InterfaceDescription' + aefId: + type: string + description: Identifier of the API exposing function + apiId: + type: string + description: API identifier + prefSecurityMethods: + type: array + items: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/SecurityMethod' + minItems: 1 + description: Security methods preferred by the API invoker for the API interface. + selSecurityMethod: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/SecurityMethod' + authenticationInfo: + type: string + description: Authentication related information + authorizationInfo: + type: string + description: Authorization related information + authorizationFlow: + type: array + items: + $ref: '#/components/schemas/AuthorizationFlow' + minItems: 1 + required: + - prefSecurityMethods + oneOf: + - required: [interfaceDetails] + - required: [aefId] + + SecurityNotification: + type: object + description: Represents the revoked authorization notification details. + properties: + +``` + +``` +apiInvokerId: + type: string + description: String identifying the API invoker assigned by the CAPIF core function. +aeId: + type: string + description: String identifying the AEF. +apiIds: + type: array + items: + type: string + minItems: 1 + description: Identifier of the service API +cause: + $ref: '#/components/schemas/Cause' +required: +- apiInvokerId +- apiIds +- cause + +AccessTokenReq: + format: x-www-form-urlencoded + description: Represents the access token request information. + properties: + grant_type: + type: string + enum: + - client_credentials + client_id: + type: string + resOwnerId: + type: string + client_secret: + type: string + scope: + type: string + authCode: + type: string + required: + - grant_type + - client_id + +AccessTokenRsp: + type: object + description: Represents the access token response information. + properties: + access_token: + type: string + description: > + JWS Compact Serialized representation of JWS signed JSON object (AccessTokenClaims) + token_type: + type: string + enum: + - Bearer + expires_in: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + scope: + type: string + required: + - access_token + - token_type + - expires_in + +AccessTokenClaims: + type: object + description: Represents the claims data structure for the access token. + properties: + iss: + type: string + resOwnerId: + type: string + scope: + type: string + exp: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' + required: + - iss + - scope + - exp +``` + +``` + +AccessTokenErr: + type: object + description: Represents an error in the access token request. + properties: + error: + type: string + enum: + - invalid_request + - invalid_client + - invalid_grant + - unauthorized_client + - unsupported_grant_type + - invalid_scope + error_description: + type: string + error_uri: + type: string + required: + - error + +AuthorizationCodeRsp: + type: object + description: Represents the authorization code response information. + properties: + authCode: + type: string + required: + - authCode + +Cause: + anyOf: + - type: string + enum: + - OVERLIMIT_USAGE + - UNEXPECTED_REASON + - type: string + description: > + This string provides forward-compatibility with future + extensions to the enumeration but is not used to encode + content defined in the present version of this API. + description: | + Indicates the cause for revoking the API invoker's authorization to the service API. + Possible values are: + - OVERLIMIT_USAGE: + The revocation of the authorization of the API invoker is due to the overlimit + usage of the service API + - UNEXPECTED_REASON: + The revocation of the authorization of the API invoker is due to unexpected reason. + +AuthorizationFlow: + anyOf: + - type: string + enum: + - CLIENT_CREDENTIALS_FLOW + - AUTHORIZATION_CODE_FLOW + - AUTHORIZATION_CODE_FLOW_WITH_PKCE + - type: string + description: > + This string provides forward-compatibility with future extensions to the enumeration and + is not used to encode content defined in the present version of this API. + description: | + Indicates the supported authorization flow (e.g. client credentials flow, authorization code + flow, etc.) to the API invoker. + Possible values are: + - CLIENT_CREDENTIALS_FLOW: + The supported authorization flow is client credentials flow. + - AUTHORIZATION_CODE_FLOW: + The supported authorization flow is authorization code flow. + - AUTHORIZATION_CODE_FLOW_WITH_PKCE: + The supported authorization flow is authorization code flow with PKCE. + +``` + +## A.7 CAPIF Access Control Policy API + +openapi: 3.0.0 + +``` +info: + title: CAPIF_Access_Control_Policy_API + description: | + API for access control policy. + © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + version: "1.3.0-alpha.1" + +externalDocs: + description: 3GPP TS 29.222 V18.0.0 Common API Framework for 3GPP Northbound APIs + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.222/ + +servers: + - url: '{apiRoot}/access-control-policy/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 7.5 of 3GPP TS 29.222 + +paths: + /accessControlPolicyList/{serviceApiId}: + get: + description: Retrieves the access control policy list. + parameters: + - name: serviceApiId + in: path + description: Identifier of a published service API + required: true + schema: + type: string + - name: aef-id + in: query + required: true + description: Identifier of the AEF + schema: + type: string + - name: api-invoker-id + in: query + description: Identifier of the API invoker + schema: + type: string + - name: supported-features + in: query + description: To filter irrelevant responses related to unsupported features + schema: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + responses: + '200': + description: OK. + content: + application/json: + schema: + $ref: '#/components/schemas/AccessControlPolicyList' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '414': + $ref: 'TS29122_CommonData.yaml#/components/responses/414' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +``` + +``` + +components: + schemas: + AccessControlPolicyList: + type: object + description: Represents the access control policy list for a published service API. + properties: + apiInvokerPolicies: + type: array + items: + $ref: '#/components/schemas/ApiInvokerPolicy' + minItems: 0 + description: Policy of each API invoker. + + ApiInvokerPolicy: + type: object + description: Represents the policy of an API Invoker. + properties: + apiInvokerId: + type: string + description: API invoker ID assigned by the CAPIF core function + allowedTotalInvocations: + type: integer + description: Total number of invocations allowed on the service API by the API invoker. + allowedInvocationsPerSecond: + type: integer + description: Invocations per second allowed on the service API by the API invoker. + allowedInvocationTimeRangeList: + type: array + items: + $ref: '#/components/schemas/TimeRangeList' + minItems: 0 + description: > + The time ranges during which the invocations are allowed on the service API + by the API invoker. + required: + - apiInvokerId + + TimeRangeList: + type: object + description: > + Represents the time range during which the invocation of a service API is allowed + by the API invoker. + properties: + startTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + stopTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + +``` + +## A.8 CAPIF\_Logging\_API\_Invocation\_API + +openapi: 3.0.0 + +``` + +info: + title: CAPIF_Logging_API_Invocation_API + description: | + API for invocation logs. + © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + version: "1.3.0-alpha.1" + +externalDocs: + description: 3GPP TS 29.222 V18.0.0 Common API Framework for 3GPP Northbound APIs + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.222/ + +servers: + - url: '{apiRoot}/api-invocation-logs/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 7.5 of 3GPP TS 29.222 + +paths: + /{aefId}/logs: + post: + +``` + +``` + +description: Creates a new log entry for service API invocations. +parameters: +- name: aefId + in: path + description: Identifier of the API exposing function + required: true + schema: + type: string +requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/InvocationLog' +responses: + '201': + description: > + Log of service API invocations provided by API exposing function successfully + stored on the CAPIF core function. + content: + application/json: + schema: + $ref: '#/components/schemas/InvocationLog' + headers: + Location: + description: > + Contains the URI of the newly created resource, according to the structure + {apiRoot}/api-invocation-logs/v1/{aefId}/logs/{logId} + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +/{aefId}/logs/{logId}: + description: Creates a new log entry for service API invocations. + parameters: + - name: aefId + in: path + description: Identifier of the API exposing function + required: true + schema: + type: string + - name: logId + in: path + description: Identifier of individual log entry + required: true + schema: + type: string +components: + schemas: + InvocationLog: + type: object + description: > + Represents a set of Service API invocation logs to be stored in a CAPIF core function. + properties: + aefId: + type: string + description: > + +``` + +``` +Identity information of the API exposing function requesting logging of +service API invocations +apiInvokerId: + type: string + description: Identity of the API invoker which invoked the service API +logs: + type: array + items: + $ref: '#/components/schemas/Log' + minItems: 1 + description: Service API invocation log +supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' +required: +- aefId +- apiInvokerId +- logs + +Log: + type: object + description: Represents an individual service API invocation log entry. + properties: + apiId: + type: string + description: String identifying the API invoked. + apiName: + type: string + description: > + Name of the API which was invoked, it is set as {apiName} part of the URI + structure as defined in clause 5.2.4 of 3GPP TS 29.122. + apiVersion: + type: string + description: Version of the API which was invoked + resourceName: + type: string + description: Name of the specific resource invoked + uri: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri' + protocol: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/Protocol' + operation: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/Operation' + result: + type: string + description: For HTTP protocol, it contains HTTP status code of the invocation + invocationTime: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + invocationLatency: + $ref: '#/components/schemas/DurationMs' + inputParameters: + description: > + List of input parameters. Can be any value - string, number, boolean, array or object. + outputParameters: + description: > + List of output parameters. Can be any value - string, number, boolean, array or object. + srcInterface: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/InterfaceDescription' + destInterface: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/InterfaceDescription' + fwdInterface: + type: string + description: > + It includes the node identifier (as defined in IETF RFC 7239 of all forwarding + entities between the API invoker and the AEF, concatenated with comma and space, + e.g. 192.0.2.43:80, unknown_OBFport, 203.0.113.60 + required: + - apiId + - apiName + - apiVersion + - resourceName + - protocol + - result + +DurationMs: + type: integer + description: Represents a period of time in units of milliseconds. + minimum: 0 +``` + +## A.9 CAPIF\_Auditing\_API + +``` +openapi: 3.0.0 + +info: + title: CAPIF_Auditing_API + description: | + API for auditing. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + version: "1.3.0-alpha.2" + +externalDocs: + description: 3GPP TS 29.222 V18.1.0 Common API Framework for 3GPP Northbound APIs + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.222/ + +servers: + - url: '{apiRoot}/logs/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 7.5 of 3GPP TS 29.222. + +paths: + /apiInvocationLogs: + get: + description: Query and retrieve service API invocation logs stored on the CAPIF core function. + parameters: + - name: aef-id + in: query + description: String identifying the API exposing function. + schema: + type: string + - name: api-invoker-id + in: query + description: String identifying the API invoker which invoked the service API. + schema: + type: string + - name: time-range-start + in: query + description: Start time of the invocation time range. + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + - name: time-range-end + in: query + description: End time of the invocation time range. + schema: + $ref: 'TS29122_CommonData.yaml#/components/schemas/DateTime' + - name: api-id + in: query + description: String identifying the API invoked. + schema: + type: string + - name: api-name + in: query + description: > + API name, it is set as {apiName} part of the URI structure as defined in + clause 5.2.4 of 3GPP TS 29.122. + schema: + type: string + - name: api-version + in: query + description: Version of the API which was invoked. + schema: + type: string + - name: protocol + in: query + description: Protocol invoked. + schema: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/Protocol' + - name: operation + in: query + description: Operation that was invoked on the API. + schema: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/Operation' + - name: result + in: query +``` + +``` + +description: Result or output of the invocation. +schema: + type: string +- name: resource-name + in: query + description: Name of the specific resource invoked. + schema: + type: string +- name: src-interface + in: query + description: Interface description of the API invoker. + content: + application/json: + schema: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/InterfaceDescription' +- name: dest-interface + in: query + description: Interface description of the API invoked. + content: + application/json: + schema: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/InterfaceDescription' +- name: supported-features + in: query + description: To filter irrelevant responses related to unsupported features + schema: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' +responses: + '200': + description: > + Result of the query operation along with fetched service API invocation log data. + content: + application/json: + schema: + $ref: '#/components/schemas/InvocationLogsRetrieveRes' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '414': + $ref: 'TS29122_CommonData.yaml#/components/responses/414' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + schemas: + InvocationLogs: + type: object + description: > + Represents several (more than one) invocation logs. + properties: + multipleInvocationLogs: + type: array + items: + $ref: 'TS29222_CAPIF_Logging_API_Invocation_API.yaml#/components/schemas/InvocationLog' + minItems: 1 + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - multipleInvocationLogs + +``` + +``` +InvocationLogsRetrieveRes: + description: > + Represents the result of an invocation logs retrieval request. + oneOf: + - $ref: 'TS29222_CAPIF_Logging_API_Invocation_API.yaml#/components/schemas/InvocationLog' + - $ref: '#/components/schemas/InvocationLogs' +``` + +--- + +## A.10 AEF\_Security\_API + +``` +openapi: 3.0.0 + +info: + title: AEF_Security_API + description: | + API for AEF security management. + © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + version: "1.3.0-alpha.1" + +externalDocs: + description: 3GPP TS 29.222 V18.0.0 Common API Framework for 3GPP Northbound APIs + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.222/ + +servers: + - url: '{apiRoot}/aeF-security/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 7.5 of 3GPP TS 29.222. + +paths: + /check-authentication: + post: + summary: Check authentication. + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/CheckAuthenticationReq' + responses: + '200': + description: The request was successful. + content: + application/json: + schema: + $ref: '#/components/schemas/CheckAuthenticationRsp' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +``` + +``` +/revoke-authorization: + post: + summary: Revoke authorization. + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/RevokeAuthorizationReq' + responses: + '200': + description: The request was successful. + content: + application/json: + schema: + $ref: '#/components/schemas/RevokeAuthorizationRsp' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + schemas: + CheckAuthenticationReq: + type: object + description: Represents authentication check request data. + properties: + apiInvokerId: + type: string + description: > + API invoker ID assigned by the CAEIF core function to the API invoker + while on-boarding the API invoker. + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - apiInvokerId + - supportedFeatures + + CheckAuthenticationRsp: + type: object + description: Represents authentication check response data. + properties: + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - supportedFeatures + + RevokeAuthorizationReq: + type: object + description: Represents authorization revocation request data. + properties: + revokeInfo: + $ref: 'TS29222_CAEIF_Security_API.yaml#/components/schemas/SecurityNotification' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' +``` + +``` + + required: + - revokeInfo + - supportedFeatures + +RevokeAuthorizationRsp: + type: object + description: Represents authorization revocation response data. + properties: + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + required: + - supportedFeatures + +``` + +## A.11 CAPIF\_API\_Provider\_Management\_API + +openapi: 3.0.0 + +``` + +info: + title: CAPIF_API_Provider_Management_API + description: | + API for API provider domain functions management. + © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + version: "1.2.0-alpha.2" + +externalDocs: + description: 3GPP TS 29.222 V18.1.0 Common API Framework for 3GPP Northbound APIs + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.222/ + +servers: + - url: '{apiRoot}/api-provider-management/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 7.5 of 3GPP TS 29.222 + +paths: + /registrations: + post: + description: Registers a new API Provider domain with API provider domain functions profiles. + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/APIProviderEnrolmentDetails' + responses: + '201': + description: API provider domain registered successfully + content: + application/json: + schema: + $ref: '#/components/schemas/APIProviderEnrolmentDetails' + headers: + Location: + description: > + Contains the URI of the newly created resource, according to the structure + {apiRoot}/api-provider-management/v1/registrations/{registrationId} + required: true + schema: + type: string + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + +``` + +``` + + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +/registrations/{registrationId}: + delete: + description: Deregisters API provider domain by deleting API provider domain and functions. + parameters: + - name: registrationId + in: path + description: String identifying an registered API provider domain resource. + required: true + schema: + type: string + responses: + '204': + description: The API provider domain matching registrationId is deleted. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + put: + description: Updates an API provider domain's registration details. + parameters: + - name: registrationId + in: path + description: String identifying an registered API provider domain resource. + required: true + schema: + type: string + requestBody: + description: > + Representation of the API provider domain registration details to be updated + in CAPIF core function. + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/APIProviderEnrolmentDetails' + responses: + '200': + description: API provider domain registration details updated successfully. + content: + application/json: + schema: + $ref: '#/components/schemas/APIProviderEnrolmentDetails' + '204': + description: No Content + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + +``` + +``` + + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' +patch: + description: Modify an individual API provider details. + operationId: ModifyIndApiProviderEnrolment + tags: + - Individual API Provider enrolment details + parameters: + - name: registrationId + in: path + required: true + schema: + type: string + requestBody: + required: true + content: + application/merge-patch+json: + schema: + $ref: '#/components/schemas/APIProviderEnrolmentDetailsPatch' + responses: + '200': + description: > + The definition of the service API is modified successfully and a + representation of the updated service API is returned in the request body. + content: + application/json: + schema: + $ref: '#/components/schemas/APIProviderEnrolmentDetails' + '204': + description: No Content. The definition of the service API is modified successfully. + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29122_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29122_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29122_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + schemas: + APIProviderEnrolmentDetails: + type: object + description: Represents an API provider domain's enrolment details. + properties: + +``` + +``` +apiProvDomId: + type: string + description: > + API provider domain ID assigned by the CAPIF core function to the API management + function while registering the API provider domain. Shall not be present in the + HTTP POST request from the API Management function to the CAPIF core function, + to on-board itself. Shall be present in all other HTTP requests and responses. + readOnly: true +regSec: + type: string + description: > + Security information necessary for the CAPIF core function to validate the + registration of the API provider domain. Shall be present in HTTP POST request + from API management function to CAPIF core function for API provider domain + registration. +apiProvFuncs: + type: array + items: + $ref: '#/components/schemas/APIProviderFunctionDetails' + minItems: 1 + description: > + A list of individual API provider domain functions details. When included by + the API management function in the HTTP request message, it lists the API + provider domain functions that the API management function intends to + register/update in registration or update registration procedure. When + included by the CAPIF core function in the HTTP response message, it lists + the API domain functions details that are registered or updated successfully. +apiProvDomInfo: + type: string + description: > + Generic information related to the API provider domain such as details + of the API provider applications. +suppFeat: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' +failReason: + type: string + description: > + Registration or update specific failure information of failed API provider + domain function registrations. Shall be present in the HTTP response + body if atleast one of the API provider domain function registration or update + registration fails. +required: + - regSec + +APIProviderFunctionDetails: + type: object + description: Represents an API provider domain function's details. + properties: + apiProvFuncId: + type: string + description: > + API provider domain functionID assigned by the CAPIF core function to the + API provider domain function while registering/updating the API provider domain. + Shall not be present in the HTTP POST request from the API management function to + the CAPIF core function, to register itself. Shall be present in all other HTTP + requests and responses. + regInfo: + $ref: '#/components/schemas/RegistrationInformation' + apiProvFuncRole: + $ref: '#/components/schemas/ApiProviderFuncRole' + apiProvFuncInfo: + type: string + description: > + Generic information related to the API provider domain function such as details + of the API provider applications. + required: + - regInfo + - apiProvFuncRole + +RegistrationInformation: + type: object + description: > + Represents registration information of an individual API provider domain function. + properties: + apiProvPubKey: + type: string + description: Public Key of API Provider domain function. + apiProvCert: +``` + +``` + + type: string + description: API provider domain function's client certificate + required: + - apiProvPubKey + +APIProviderEnrolmentDetailsPatch: + type: object + description: > + Represents a list of modifications for the API provider domain's enrolment details. + properties: + apiProvFuncs: + type: array + items: + $ref: '#/components/schemas/APIProviderFunctionDetails' + minItems: 1 + description: > + A list of individual API provider domain functions details. When included by + the API management function in the HTTP request message, it lists the API + provider domain functions that the API management function intends to + register/update in registration or update registration procedure. + apiProvDomInfo: + type: string + description: > + Generic information related to the API provider domain such as details + of the API provider applications. + +# Simple data types and enumerations +ApiProviderFuncRole: + anyOf: + - type: string + enum: + - AEF + - APF + - AMF + - type: string + description: > + This string provides forward-compatibility with future extensions to the enumeration + but is not used to encode content defined in the present version of this API. + description: | + Indicates the role (e.g. AEF, APF, etc.) of an API provider domain function. + Possible values are: + - AEF: API provider function is API Exposing Function. + - APF: API provider function is API Publishing Function. + - AMF: API Provider function is API Management Function. + +``` + +## A.12 CAPIF\_Routing\_Info\_API + +openapi: 3.0.0 + +``` + +info: + title: CAPIF_Routing_Info_API + description: | + API for Routing information. + © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. + version: "1.2.0-alpha.1" + +externalDocs: + description: 3GPP TS 29.222 V18.0.0 Common API Framework for 3GPP Northbound APIs + url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.222/ + +servers: +- url: '{apiRoot}/capif-routing-info/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in clause 7.5 of 3GPP TS 29.222 + +paths: +/service-apis/{serviceApiId}: + get: + description: Retrieves the API routing information. + parameters: + - name: serviceApiId + in: path + +``` + +``` + description: Identifier of a published service API + required: true + schema: + type: string +- name: aef-id + in: query + required: true + description: Identifier of the AEF + schema: + type: string +- name: supp-feat + in: query + required: false + description: To filter irrelevant responses related to unsupported features + schema: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' +responses: + '200': + description: OK. + content: + application/json: + schema: + $ref: '#/components/schemas/RoutingInfo' + '307': + $ref: 'TS29122_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29122_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29122_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29122_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29122_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29122_CommonData.yaml#/components/responses/404' + '406': + $ref: 'TS29122_CommonData.yaml#/components/responses/406' + '414': + $ref: 'TS29122_CommonData.yaml#/components/responses/414' + '429': + $ref: 'TS29122_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29122_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29122_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29122_CommonData.yaml#/components/responses/default' + +components: + schemas: + RoutingInfo: + type: object + description: Represents an API routing information. + properties: + routingRules: + type: array + items: + $ref: '#/components/schemas/RoutingRule' + minItems: 1 + required: + - routingRules + + RoutingRule: + type: object + description: Represents an API routing rule. + properties: + ipv4AddrRanges: + type: array + items: + $ref: 'TS29510_Nnrf_NFManagement.yaml#/components/schemas/Ipv4AddressRange' + minItems: 1 + ipv6AddrRanges: + type: array + items: + $ref: '#/components/schemas/Ipv6AddressRange' + minItems: 1 + aefProfile: + $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/AefProfile' +``` + +``` +required: + - aefProfile + +Ipv6AddressRange: + type: object + description: Represents IPv6 address range. + properties: + start: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv6Addr' + end: + $ref: 'TS29122_CommonData.yaml#/components/schemas/Ipv6Addr' + required: + - start + - end +``` + +--- + +## Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-03 | CT3#95 | C3-181278 | | | | TS skeleton of Common API Framework for 3GPP Northbound APIs | 0.0.0 | +| 2018-03 | CT3#95 | C3-181378 | | | | Inclusion of documents agreed in CT3#95:
C3-181281, C3-181282, C3-181283, C3-181284, C3-181285, C3-181286, C3-181287, C3-181321, C3-181322, Rapporteur changes | 0.1.0 | +| 2018-04 | CT3#96 | C3-182527 | | | | Inclusion of documents agreed in CT3#96:
C3-182204, C3-182387, C3-182393, C3-182395, C3-182468, C3-182469, C3-182470, C3-182483, C3-182484, C3-182485 | 0.2.0 | +| 2018-05 | CT3#97 | | | | | Inclusion of documents agreed in CT3#97:
C3-183271, C3-183274, C3-183275, C3-183372, C3-183376, C3-183377, C3-183378, C3-183379, C3-183598, C3-183599, C3-183602, C3-183603, C3-183604, C3-183798, C3-183799, C3-183809, C3-183841, C3-183842 | 0.3.0 | +| 2018-06 | CT#80 | CP-181037 | | | | TS sent to plenary for approval | 1.0.0 | +| 2018-06 | CT#80 | CP-181037 | | | | TS approved by plenary | 15.0.0 | +| 2018-09 | CT#81 | CP-182016 | 0001 | 1 | F | Changes to clause 4 – Overview | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0003 | 2 | F | Changes to CAPIF Publish Service API clause | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0004 | 2 | F | Changes to CAPIF Events API clause | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0005 | 4 | F | Changes to CAPIF API Invoker Management API clause | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0006 | 4 | F | Changes to CAPIF Authentication Authorization API clause | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0007 | 3 | F | Update to data types for ServiceAPIDescription and APIQuery | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0008 | 5 | F | Definition of CAPIF_Access_Control_Policy_API, and OpenAPI schema | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0009 | 4 | F | CAPIF_Events_API OpenAPI schema | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0010 | 4 | F | AEF_Authentication_API OpenAPI schema | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0011 | 1 | F | CAPIF_Discover_Service API - Corrections | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0012 | 3 | F | CAPIF_discovery_service API OpenAPI file | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0013 | 4 | F | CAPIF_Publish_Service API - Corrections and OpenAPI file | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0014 | 4 | F | AEF_Authentication API - Editor's notes | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0015 | 4 | F | Corrections to data type | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0016 | 1 | F | API Invoker's Information in APIInvokerEnrolmentDetails | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0017 | 1 | F | Corrections to OnboardingInformation data type | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0018 | 2 | F | Security method preference | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0019 | 1 | F | Clarifications to Obtain_API_Invoker_Info service operation | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0020 | 1 | F | Subscribed and Subscribing functional entity | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0021 | 1 | F | Miscellaneous corrections | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0023 | 1 | F | Definitions and abbreviations | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0024 | 1 | F | Referenced data types and enumerations | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0025 | 2 | F | CAPIF_Security_API OpenAPI schema | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0026 | 1 | F | CAPIF discovery service API – API invoker retrieves API information using GET | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0028 | 2 | F | CAPIF_Auditing_API – API management function retrieves API information logs using GET – OpenAPI document | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0029 | 3 | F | API Names changes in clause 5 | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0030 | | F | Change security-related API names in clause 8 and 10 | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0031 | 2 | F | Describe response code 202 for Onboard_API_Invoker POST method | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0032 | | F | Correct cardinality for onboardingNotificationDestination | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0033 | | F | Correct cardinality for securityNotificationDestination | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0034 | 1 | F | Correct protocol type in Interface Description | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0036 | 1 | F | Query parameter in retrieving access control | 15.1.0 | +| 2018-09 | CT#81 | CP-182037 | 0037 | 1 | F | Authorization endpoint and token request | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0038 | 1 | F | CAPIF Events | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0040 | 1 | F | Corrections to resource figures | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0041 | 1 | F | CAPIF_Auditing_API - 'query' custom operation | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0042 | 2 | F | OpenAPI - CAPIF_API_Invoker_Management API | 15.1.0 | +| 2018-09 | CT#81 | CP-182016 | 0043 | 2 | F | OpenAPI - CAPIF_Logging_API_Invocation API | 15.1.0 | +| 2018-12 | CT#82 | CP-183109 | 0047 | | F | Correct server definition | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0027 | 2 | F | Security adaptation for Nnef northbound APIs with CAPIF | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0045 | 1 | F | Correct security API name in clause 5.6.2.1 | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0046 | 1 | F | Remove Event operations from CAPIF_Publish_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0048 | | F | Correct CAPIF services | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0049 | 2 | F | Correct api name and service name for CAPIF_Publish_Service_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0050 | 2 | F | Correct api name and service name for CAPIF_Discover_Service_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0051 | 4 | F | Correct CAPIF_Publish_Service_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0052 | 1 | F | Correct CAPIF_Discover_Service_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0053 | 4 | F | Correct CAPIF_Logging_API_Invocation_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0054 | 3 | F | Correct CAPIF_Auditing_API | 15.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------|--------| +| 2018-12 | CT#82 | CP-183109 | 0055 | 2 | F | Correct CAPIF_Security_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0055 | 3 | F | Correct CAPIF_Security_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0057 | | F | Correct CAPIF_Access_Control_Policy_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0058 | 2 | F | supportedFeatures - CAPIF_Discover_Service_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0059 | | F | supportedFeatures 002 - CAPIF_Publish_Service_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0060 | 1 | F | supportedFeatures 003 - CAPIF_Events_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0061 | | F | supportedFeatures 004 - CAPIF_API_Invoker_Management_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0062 | | F | supportedFeatures 005 - CAPIF_Security_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0063 | 2 | F | supportedFeatures - CAPIF_Access_Control_Policy_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0064 | | F | supportedFeatures 007 - CAPIF_Logging_API_Invocation_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0065 | 2 | F | supportedFeatures - CAPIF_Auditing_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0067 | | F | Redundant Editor's note | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0068 | 1 | F | Correct CAPIF_API_Invoker_Management_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0070 | | F | Missing general description in A.1 | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0071 | 1 | F | Update mandatory error status code | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0072 | 3 | F | Correct resource model and add missing functions in CAPIF_Security_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0074 | 2 | F | Correct resource model and add missing function in AEF_Authentication_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0075 | 1 | F | externalDocs field in OpenAPI documents | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0076 | 3 | F | location header in OpenAPI documents | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0077 | 1 | F | version number in OpenAPI documents | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0078 | 2 | F | corrections to CAPIF_Access_Control_Policy_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0079 | 1 | F | corrections to CAPIF_Logging_API_Invocation_API | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0079 | 2 | F | Security adaptation for T8 APIs with CAPIF | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0080 | | F | corrections to EventNotification | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0081 | | F | corrections to theSubscriber | 15.2.0 | +| 2018-12 | CT#82 | CP-183109 | 0082 | | F | remove 'OnboardingRequestAck' data type | 15.2.0 | +| 2019-03 | CT#83 | CP-190119 | 0083 | 1 | F | Correct GET description for retrieving service API information | 15.3.0 | +| 2019-03 | CT#83 | CP-190119 | 0084 | 1 | F | Correct PUT message for updating service APIs | 15.3.0 | +| 2019-03 | CT#83 | CP-190119 | 0085 | 2 | F | Correct AEF operations related to obtaining security info or revoking API invokers | 15.3.0 | +| 2019-03 | CT#83 | CP-190119 | 0086 | 1 | F | Correction of definition of obtaining the correct resource in Security APIs | 15.3.0 | +| 2019-03 | CT#83 | CP-190119 | 0089 | 1 | F | Correct several descriptions in clause 8 tables | 15.3.0 | +| 2019-06 | CT#84 | CP-191088 | 0090 | 1 | F | Correct CAPIF_Logging_API yaml file | 15.4.0 | +| 2019-06 | CT#84 | CP-191221 | 0091 | 1 | F | Copyright notice in the YAML files | 15.4.0 | +| 2019-06 | CT#84 | CP-191222 | 0092 | 1 | F | API version update | 15.4.0 | +| 2019-09 | CT#85 | CP-192158 | 0093 | 3 | F | Northbound API registration and discovery | 16.0.0 | +| 2019-12 | CT#86 | CP-193194 | 0095 | 1 | A | Correct cardinality in event API | 16.1.0 | +| 2019-12 | CT#86 | CP-193199 | 0096 | 4 | B | Reference update: RFC 8259 | 16.1.0 | +| 2019-12 | CT#86 | CP-193199 | 0097 | | F | Detailed information in CAPIF event notification | 16.1.0 | +| 2019-12 | CT#86 | CP-193195 | 0101 | 4 | B | Updates to Service Architecture and functional entities | 16.1.0 | +| 2019-12 | CT#86 | CP-193194 | 0103 | 1 | A | Clause reference corrections | 16.1.0 | +| 2019-12 | CT#86 | CP-193194 | 0105 | 1 | A | Conventions for Open API specification files | 16.1.0 | +| 2019-12 | CT#86 | CP-193195 | 0106 | 1 | B | Update-to-Service-Architecture | 16.1.0 | +| 2019-12 | CT#86 | CP-193195 | 0107 | 2 | B | Update-to-Service-API-Publish | 16.1.0 | +| 2019-12 | CT#86 | CP-193195 | 0108 | 1 | B | Interconnection-Service-API-Publish | 16.1.0 | +| 2019-12 | CT#86 | CP-193195 | 0109 | 2 | B | Update-to-Discover-Service-API | 16.1.0 | +| 2019-12 | CT#86 | CP-193199 | 0111 | 1 | B | Supported feature in API publish service | 16.1.0 | +| 2019-12 | CT#86 | CP-193195 | 0112 | 1 | B | API invoker details update – Service Definition | 16.1.0 | +| 2019-12 | CT#86 | CP-193195 | 0113 | 1 | B | API invoker details update – API Definition | 16.1.0 | +| 2019-12 | CT#86 | CP-193195 | 0114 | 1 | B | API Provider Registration and Update – Service Definition | 16.1.0 | +| 2019-12 | CT#86 | CP-193195 | 0115 | 3 | B | API Provider Registration and Update – API Definition | 16.1.0 | +| 2019-12 | CT#86 | CP-193195 | 0116 | 1 | B | Support for 3rd party API provider domain | 16.1.0 | +| 2019-12 | CT#86 | CP-193194 | 0118 | 1 | A | Correct the notificationDestination of ServiceSecurity object in yaml file | 16.1.0 | +| 2019-12 | CT#86 | CP-193194 | 0120 | 1 | A | Align the API name of Initiate_Authentication | 16.1.0 | +| 2019-12 | CT#86 | CP-193212 | 0121 | | F | Update of API version and TS version in OpenAPI file | 16.1.0 | +| 2020-03 | CT#87e | CP-200205 | 0123 | 1 | B | Published API path | 16.2.0 | +| 2020-03 | CT#87e | CP-200205 | 0124 | | B | API Invoker Update – Event Updates | 16.2.0 | +| 2020-03 | CT#87e | CP-200205 | 0125 | 2 | B | API Provider Management – Open API | 16.2.0 | +| 2020-03 | CT#87e | CP-200216 | 0126 | | F | 29.222 Rel-16 Update of OpenAPI version and TS version in externalDocs field | 16.2.0 | +| 2020-06 | CT#88e | CP-201277 | 0128 | 3 | B | Service description and operations for CAPIF_API_Routing_Policy_API | 16.3.0 | +| 2020-06 | CT#88e | CP-201277 | 0129 | 3 | B | API definition for CAPIF_API_Routing_Policy_API | 16.3.0 | +| 2020-06 | CT#88e | CP-201278 | 0130 | 3 | B | API Topology hiding | 16.3.0 | +| 2020-06 | CT#88e | CP-201230 | 0133 | | A | Correct API publish procedure | 16.3.0 | +| 2020-06 | CT#88e | CP-201231 | 0131 | 1 | F | API Provider management API attribute name optimization | 16.3.0 | +| 2020-06 | CT#88e | CP-201231 | 0135 | 1 | F | Correct ServiceAPIDescription | 16.3.0 | +| 2020-06 | CT#88e | CP-201231 | 0136 | 2 | F | Correct service API discovery in interconnection | 16.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------|--------| +| 2020-06 | CT#88e | CP-201231 | 0137 | 1 | F | Correct shareable information | 16.3.0 | +| 2020-06 | CT#88e | CP-201235 | 0138 | 1 | F | Correct the supported features in the published API | 16.3.0 | +| 2020-06 | CT#88e | CP-201235 | 0139 | 1 | F | Update general clause for OpenAPI specification | 16.3.0 | +| 2020-06 | CT#88e | CP-201256 | 0140 | 1 | F | URI of the CAPIF APIs | 16.3.0 | +| 2020-06 | CT#88e | CP-201231 | 0141 | 1 | B | Add API category in discovery | 16.3.0 | +| 2020-06 | CT#88e | CP-201235 | 0142 | | F | Optionality of ProblemDetails | 16.3.0 | +| 2020-06 | CT#88e | CP-201230 | 0144 | 1 | A | Clause and reference point correction | 16.3.0 | +| 2020-06 | CT#88e | CP-201231 | 0145 | 1 | F | Align interface names | 16.3.0 | +| 2020-06 | CT#88e | CP-201235 | 0146 | 1 | F | Supported headers, Resource Data type, Operation Name and yaml mapping | 16.3.0 | +| 2020-06 | CT#88e | CP-201255 | 0147 | | F | Update of OpenAPI version and TS version in externalDocs field | 16.3.0 | +| 2020-06 | CT#88e | CP-201319 | 0149 | | A | Required attribute corrections to CAPIF Open APIs | 16.3.0 | +| 2020-09 | CT#89e | CP-202064 | 0151 | 1 | F | Missing and inconsistent "apiVersion" notations and Location header | 16.4.0 | +| 2020-09 | CT#89e | CP-202064 | 0152 | 1 | F | CAPIF Routing Info API corrections | 16.4.0 | +| 2020-09 | CT#89e | CP-202064 | 0153 | | F | CAPIF topology hiding correction | 16.4.0 | +| 2020-09 | CT#89e | CP-202233 | 0155 | 3 | A | Correct CAPIF security API | 16.4.0 | +| 2020-09 | CT#89e | CP-202063 | 0157 | 1 | A | Correct api invoker certificate in onboarding | 16.4.0 | +| 2020-09 | CT#89e | CP-202084 | 0158 | | F | Update of OpenAPI version and TS version in externalDocs field | 16.4.0 | +| 2020-12 | CT#90e | CP-203139 | 0160 | 1 | F | Essential corrections and alignments | 16.5.0 | +| 2020-12 | CT#90e | CP-203126 | 0162 | 1 | A | Correct inconsistency in SecurityNotification | 16.5.0 | +| 2020-12 | CT#90e | CP-203139 | 0163 | 1 | F | Storage of YAML files in 3GPP Forge | 16.5.0 | +| 2021-03 | CT#91e | CP-210239 | 0164 | 1 | F | CAPIF_Security API externalDocs version correction | 16.6.0 | +| 2021-03 | CT#91e | CP-210221 | 0165 | 1 | F | Corrections to HTTP custom headers handling for Northbound APIs | 17.0.0 | +| 2021-03 | CT#91e | CP-210220 | 0166 | | F | OpenAPI reference | 17.0.0 | +| 2021-06 | CT#92e | CP-211239 | 0177 | 1 | F | Missing data type in the CAPIF_API_Provider_Management_API Data Types tables | 17.1.0 | +| 2021-06 | CT#92e | CP-211239 | 0178 | 2 | F | Missing data type in the CAPIF_Routing_Info_API Data Types tables | 17.1.0 | +| 2021-06 | CT#92e | CP-211123 | 0179 | 1 | F | Missing data type in the CAPIF_Security_API Data Types tables | 17.1.0 | +| 2021-06 | CT#92e | CP-211239 | 0180 | 1 | F | Missing data types in the CAPIF_Access_Control_Policy_API Data Types tables | 17.1.0 | +| 2021-06 | CT#92e | CP-211124 | 0181 | 3 | F | Missing data types in the CAPIF_Publish_Service_API Data Types tables | 17.1.0 | +| 2021-06 | CT#92e | CP-211216 | 0185 | | A | SecurityMethod data type incorrectly written some parts of the CAPIF_Publish_Service_API description clause | 17.1.0 | +| 2021-06 | CT#92e | CP-211241 | 0186 | 1 | F | DiscoverService: Unbreakable spaces and missing "description" field | 17.1.0 | +| 2021-06 | CT#92e | CP-211241 | 0187 | 1 | F | PublishService API: Unbreakable spaces and missing "description" fields | 17.1.0 | +| 2021-06 | CT#92e | CP-211241 | 0188 | 1 | F | Events API: Unbreakable spaces and missing "description" fields | 17.1.0 | +| 2021-06 | CT#92e | CP-211241 | 0189 | 1 | F | InvokerManagement API: Unbreakable spaces and missing "description" fields | 17.1.0 | +| 2021-06 | CT#92e | CP-211241 | 0190 | 1 | F | Security API: Unbreakable space and missing "description" fields | 17.1.0 | +| 2021-06 | CT#92e | CP-211241 | 0191 | 1 | F | AccessControlPolicy API: Unbreakable spaces and missing "description" fields | 17.1.0 | +| 2021-06 | CT#92e | CP-211241 | 0192 | 1 | F | LoggingAPIInvocation API: Unbreakable spaces and missing "description" fields | 17.1.0 | +| 2021-06 | CT#92e | CP-211241 | 0193 | 1 | F | Auditing API: Unbreakable spaces | 17.1.0 | +| 2021-06 | CT#92e | CP-211241 | 0194 | 1 | F | AEFSecurity API: Unbreakable spaces and missing "description" fields | 17.1.0 | +| 2021-06 | CT#92e | CP-211241 | 0195 | 1 | F | API_Provider_Management API: Missing "description" fields | 17.1.0 | +| 2021-06 | CT#92e | CP-211241 | 0196 | 1 | F | RoutingInfo API: Unbreakable spaces and missing "description" fields | 17.1.0 | +| 2021-06 | CT#92e | CP-211239 | 0197 | | F | Correction of the clause clause terminology | 17.1.0 | +| 2021-06 | CT#92e | CP-211239 | 0198 | | F | Corrections to the CAPIF_API_Invoker_Management_API Data Model clause | 17.1.0 | +| 2021-06 | CT#92e | CP-211240 | 0199 | 1 | F | Corrections to the CAPIF_Auditing_API Data Model clause | 17.1.0 | +| 2021-06 | CT#92e | CP-211239 | 0200 | | F | Corrections to the CAPIF_Events_API Data Model clause | 17.1.0 | +| 2021-06 | CT#92e | CP-211239 | 0201 | | F | Corrections to the CAPIF_Logging_API_Invocation_API Data Model clause | 17.1.0 | +| 2021-06 | CT#92e | CP-211239 | 0202 | | F | Corrections to the CAPIF_Publish_Service_API Data Model clause | 17.1.0 | +| 2021-06 | CT#92e | CP-211239 | 0203 | | F | Corrections to the CAPIF_Security_API Data Model clause | 17.1.0 | +| 2021-06 | CT#92e | CP-211240 | 0204 | 1 | F | Miscellaneous corrections to the CAPIF_Discover_Service_API | 17.1.0 | +| 2021-06 | CT#92e | CP-211240 | 0205 | 1 | F | Miscellaneous corrections to the AEF_Security_API | 17.1.0 | +| 2021-06 | CT#92e | CP-211240 | 0206 | 1 | B | Support of 204 No content response code for service API definition update(NB17) | 17.1.0 | +| 2021-06 | CT#92e | CP-211240 | 0207 | 1 | F | Support redirection and mandatory error codes for CAPIF APIs | 17.1.0 | +| 2021-06 | CT#92e | CP-211265 | 0208 | | F | Update of OpenAPI version and TS version in externalDocs field | 17.1.0 | +| 2021-09 | CT#93e | CP-212224 | 0209 | | F | Correction of cardinality of InvocationLogs in POST request | 17.2.0 | +| 2021-09 | CT#93e | CP-212214 | 0210 | | F | Resource URI correction on CAPIF APIs | 17.2.0 | +| 2021-09 | CT#93e | CP-212214 | 0211 | | F | 204 No Content during modification procedure on CAPIF_API_Provider_Management_API | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------|--------| +| 2021-09 | CT#93e | CP-212214 | 0212 | | F | Correction of some remaining invalid characters in OpenAPI specification files | 17.2.0 | +| 2021-09 | CT#93e | CP-212214 | 0213 | | F | Updates 204 No Content in CAPIF_API_Invoker_Management_API | 17.2.0 | +| 2021-09 | CT#93e | CP-212223 | 0214 | | F | Update of OpenAPI version and TS version in externalDocs field | 17.2.0 | +| 2021-12 | CT#94e | CP-213221 | 0215 | 2 | B | AEF location support | 17.3.0 | +| 2021-12 | CT#94e | CP-213220 | 0216 | | B | Alignment with SA3 supported TLS profiles | 17.3.0 | +| 2021-12 | CT#94e | CP-213246 | 0217 | | F | Update of OpenAPI version and TS version in externalDocs field | 17.3.0 | +| 2022-03 | CT#95e | CP-220203 | 0218 | 1 | F | Clarify the query logic for API invoker id | 17.4.0 | +| 2022-03 | CT#95e | CP-220168 | 0221 | | A | Correct inconsistencies | 17.4.0 | +| 2022-03 | CT#95e | CP-220204 | 0222 | 1 | B | Obtain security info with API ID | 17.4.0 | +| 2022-03 | CT#95e | CP-220204 | 0223 | 1 | F | Clarification about building the apiRoot of a discovered API | 17.4.0 | +| 2022-03 | CT#95e | CP-220323 | 0224 | 2 | B | Support PATCH for the update of an API Provider Domain Registration resource. | 17.4.0 | +| 2022-03 | CT#95e | CP-220350 | 0225 | 3 | B | Support PATCH for the update of an On-boarded API resource | 17.4.0 | +| 2022-03 | CT#95e | CP-220204 | 0226 | | B | Support PATCH for the update of an APF published API resource | 17.4.0 | +| 2022-03 | CT#95e | CP-220194 | 0227 | | F | Update of info and externalDocs fields | 17.4.0 | +| 2022-06 | CT#96 | CP-221147 | 0230 | 3 | F | Resolving the naming convention issues | 17.5.0 | +| 2022-06 | CT#96 | CP-221275 | 0231 | 2 | F | Token request error | 17.5.0 | +| 2022-06 | CT#96 | CP-221147 | 0232 | | F | CAPIF_Discover_Service_API: formatting of preferred-aef-loc query parameter | 17.5.0 | +| 2022-06 | CT#96 | CP-221147 | 0233 | | F | Resource URI overview and apiVersion placeholder | 17.5.0 | +| 2022-06 | CT#96 | CP-221148 | 0234 | 1 | F | OpenAPI long descriptions | 17.5.0 | +| 2022-06 | CT#96 | CP-221124 | 0237 | 1 | A | Correcting the data type of the APF identifier | 17.5.0 | +| 2022-06 | CT#96 | CP-221124 | 0240 | 1 | A | Correcting the data type of the service API Identifier | 17.5.0 | +| 2022-06 | CT#96 | CP-221124 | 0243 | | A | Correcting query parameters names in the CAPIF_Security_API | 17.5.0 | +| 2022-06 | CT#96 | CP-221263 | 0244 | 2 | F | Missing definition of the AccessTokenErr data type in the main body | 17.5.0 | +| 2022-06 | CT#96 | CP-221124 | 0247 | 1 | A | Correct token request content type | 17.5.0 | +| 2022-06 | CT#96 | CP-221151 | 0248 | | F | Update of info and externalDocs fields | 17.5.0 | +| 2022-09 | CT#97e | CP-222118 | 0251 | 2 | F | Corrections to the references for URI structure from TS 29.501 to TS 29.122. | 17.6.0 | +| 2022-09 | CT#97e | CP-222121 | 0252 | | F | Update of info and externalDocs fields | 17.6.0 | +| 2022-12 | CT#98e | CP-223235 | 0262 | 2 | A | Corrections for CAPIF_API_Invoker_Management_API | 17.7.0 | +| 2022-12 | CT#98e | CP-223184 | 0266 | | F | Add the missing status code for CAPIF_API_Invoker_Management_API | 17.7.0 | +| 2022-12 | CT#98e | CP-223169 | 0267 | 1 | A | Corrections for data type of CAPIF services | 17.7.0 | +| 2022-12 | CT#98e | CP-223169 | 0270 | | A | Corrections on Enumeration Protocol for CAPIF_Publish_Service_API | 17.7.0 | +| 2022-12 | CT#98e | CP-223169 | 0273 | | A | Corrections on POST request body for CAPIF_Logging_API_Invocation_API | 17.7.0 | +| 2022-12 | CT#98e | CP-223169 | 0276 | | A | Corrections on resource URI for CAPIF_Discover_Service_API | 17.7.0 | +| 2022-12 | CT#98e | CP-223169 | 0279 | | A | Corrections on Time Range List for CAPIF_Access_Control_Policy_API | 17.7.0 | +| 2022-12 | CT#98e | CP-223188 | 0284 | | F | Update of info and externalDocs fields | 17.7.0 | +| 2022-12 | CT#98e | CP-223185 | 0253 | 1 | B | Completing the interface descriptions | 18.0.0 | +| 2022-12 | CT#98e | CP-223185 | 0254 | 1 | B | Custom Operations modelling | 18.0.0 | +| 2022-12 | CT#98e | CP-223185 | 0256 | 1 | F | Correction of the tables for the re-used, API-specific data structures in CAPIF APIs | 18.0.0 | +| 2022-12 | CT#98e | CP-223185 | 0257 | | F | Correction of the OpenAPI file formatting and descriptions in the CAPIF APIs | 18.0.0 | +| 2022-12 | CT#98e | CP-223185 | 0258 | | F | "Error handling" clause: alignment with other NBI and 5GS APIs | 18.0.0 | +| 2022-12 | CT#98e | CP-223185 | 0259 | | F | Corrections on CAPIF_API_Provider_Management_API | 18.0.0 | +| 2022-12 | CT#98e | CP-223189 | 0285 | | F | Update of info and externalDocs fields | 18.0.0 | +| 2023-03 | CT#99 | CP-230156 | 0286 | 1 | F | Correction of the description fields in enumerations | 18.1.0 | +| 2023-03 | CT#99 | CP-230157 | 0287 | 1 | B | Vendor specific extensions | 18.1.0 | +| 2023-03 | CT#99 | CP-230157 | 0290 | 1 | B | Support of CAPIF extensibility requirements | 18.1.0 | +| 2023-03 | CT#99 | CP-230157 | 0294 | 1 | B | Update for CAPIF_Auditing_API to support carrying multiple invocation logs and feature negotiation | 18.1.0 | +| 2023-03 | CT#99 | CP-230156 | 0295 | | F | Update the description field of CAPIF_Publish_Service_API | 18.1.0 | +| 2023-03 | CT#99 | CP-230161 | 0296 | | F | Update of info and externalDocs fields | 18.1.0 | +| 2023-06 | CT#100 | CP-231140 | 0297 | 3 | B | Completing the support of CAPIF protocol and data formats extensibility requirements | 18.2.0 | +| 2023-06 | CT#100 | CP-231139 | 0298 | | F | Corrections on presence of the attributes in CAPIF APIs | 18.2.0 | +| 2023-06 | CT#100 | CP-231139 | 0299 | | F | Support CAPIF model in SNPN | 18.2.0 | +| 2023-06 | CT#100 | CP-231141 | 0305 | | F | Update of info and externalDocs fields | 18.2.0 | +| 2023-09 | CT#101 | CP-232091 | 0306 | 1 | F | CAPIF security method clarification | 18.3.0 | +| 2023-09 | CT#101 | CP-232091 | 0307 | 1 | B | Update definitions of CAPIF provider domain and SNPN trust domain | 18.3.0 | +| 2023-09 | CT#101 | CP-232091 | 0308 | 1 | F | Clarify CCF role in service publish | 18.3.0 | +| 2023-09 | CT#101 | CP-232086 | 0309 | 1 | B | CAPIF Events API update subscription | 18.3.0 | +| 2023-09 | CT#101 | CP-232091 | 0310 | 1 | F | Various corrections | 18.3.0 | +| 2023-09 | CT#101 | CP-232085 | 0311 | | F | Update of info and externalDocs fields | 18.3.0 | +| 2023-12 | CT#102 | CP-233231 | 0300 | 4 | B | Supporting query parameters extensibility for the | 18.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------|--------| +| | | | | | | CAPIF_Discover_Service_API | | +| 2023-12 | CT#102 | CP-233261 | 0312 | 2 | B | Authorization code flow for resource owner-aware northbound api access | 18.4.0 | +| 2023-12 | CT#102 | CP-233261 | 0313 | 2 | B | Update authorization obtaining part to support resource owner-aware northbound API access | 18.4.0 | +| 2023-12 | CT#102 | CP-233261 | 0314 | 2 | B | Update securitymethod data type for Resource owner-aware northbound API access | 18.4.0 | +| 2023-12 | CT#102 | CP-233243 | 0316 | 1 | B | Service API status monitoring in the CAPIF APIs | 18.4.0 | +| 2023-12 | CT#102 | CP-233231 | 0317 | 2 | F | Error handling in the CAPIF layer | 18.4.0 | +| 2023-12 | CT#102 | CP-233232 | 0318 | 2 | F | Update of the CAPIF layer architecture description | 18.4.0 | +| 2023-12 | CT#102 | CP-233261 | 0319 | 1 | B | Discovering of APIs based on the API provider name in the CAPIF_Discover_Service_API | 18.4.0 | +| 2023-12 | CT#102 | CP-233231 | 0320 | 1 | F | HTTP RFC uplifting | 18.4.0 | +| 2023-12 | CT#102 | CP-233231 | 0321 | 1 | F | Correction of the InterfaceDescription data structure | 18.4.0 | +| 2023-12 | CT#102 | CP-233261 | 0322 | 1 | B | Discovering of APIs based on the IP address of UE in the CAPIF_Discover_Service_API | 18.4.0 | +| 2023-12 | CT#102 | CP-233232 | 0325 | 2 | F | Corrections to boolean type definitions | 18.4.0 | +| 2023-12 | CT#102 | CP-233231 | 0326 | | F | Corrections on the CAPIF service | 18.4.0 | +| 2023-12 | CT#102 | CP-233232 | 0327 | 1 | F | CAPIFEventDetail data type clarification | 18.4.0 | +| 2023-12 | CT#102 | CP-233232 | 0328 | 1 | D | Correcting an incorrect clause number | 18.4.0 | +| 2023-12 | CT#102 | CP-233241 | 0331 | 1 | B | New IE(Service KPI) in Service API publish request | 18.4.0 | +| 2023-12 | CT#102 | CP-233261 | 0332 | 1 | B | CAPIF_Publish_Service_API – Publish the Public IP ranges information | 18.4.0 | +| 2023-12 | CT#102 | CP-233237 | 0333 | | F | Update of info and externalDocs fields | 18.4.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29230/raw.md b/marked/Rel-18/29_series/29230/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c2218c36f2cf30b1785a79b402764f1ee37be956 --- /dev/null +++ b/marked/Rel-18/29_series/29230/raw.md @@ -0,0 +1,2864 @@ + + +# 3GPP TS 29.230 V18.2.0 (2023-09) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Diameter applications; 3GPP specific codes and identifiers (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font. The 'P' has a red signal wave icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|----------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Application identifiers..... | 7 | +| 4.1 3GPP specific application identifiers ..... | 7 | +| 5 Command codes..... | 9 | +| 5.1 Command codes allocated for 3GPP..... | 9 | +| 6 Vendor identifier..... | 11 | +| 6.1 3GPP's vendor identifier ..... | 11 | +| 7 Attribute-Value-Pair codes ..... | 12 | +| 7.1 3GPP specific AVP codes..... | 13 | +| 8 Experimental result codes ..... | 38 | +| 8.1 3GPP specific result codes ..... | 38 | +| 8.1.1 Informational ..... | 38 | +| 8.1.2 Success ..... | 39 | +| 8.1.3 Transient Failures ..... | 39 | +| 8.1.4 Permanent Failures ..... | 40 | +| Annex A (informative): Assignment of the Diameter codes and identifiers in 3GPP ..... | 44 | +| A.1 Application identifiers..... | 44 | +| A.2 Command codes..... | 44 | +| A.3 AVP codes..... | 44 | +| A.4 Result codes ..... | 44 | +| Annex B (informative): Change history..... | 46 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document lists the 3GPP specific Diameter protocol codes, including the AVP codes and Experimental result codes. + +This document lists also the application identifiers assigned to 3GPP specific Diameter applications by IANA and the Diameter command code range which is assigned to 3GPP by IANA. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signalling flows and message contents". +- [2] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; Protocol details". +- [3] 3GPP TS 29.328: "IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents". +- [4] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol; Protocol details". +- [5] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications". +- [6] 3GPP TS 29.234, Release 11: "3GPP system to Wireless Local Area Network (WLAN) interworking; Stage 3". +- [7] 3GPP TS 29.109: "Generic Authentication Architecture (GAA); Zh and Zn Interfaces based on the Diameter protocol; Stage 3". +- [8] 3GPP TS 29.209, Release 6: "Policy control over Gq interface". +- [9] IETF RFC 3588: "Diameter Base Protocol". +- [10] IETF RFC 3589: "Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5". +- [11] IANA's Enterprise-Numbers: +- [12] IANA's AAA parameters register: + +- [13] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)". +- [14] 3GPP TS 32.296: "Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces". +- [15] 3GPP TS 29.210, Release 6: "Charging rule provisioning over Gx interface". +- [16] 3GPP TS 29.140, Release 6: "Multimedia Messaging Service (MMS); MM10 interface based on Diameter protocol; Stage 3". +- [17] 3GPP TS 29.211, Release 6: "Rx Interface and Rx/Gx signalling flows". +- [18] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point". +- [19] 3GPP TS 29.212: "Policy and Charging Control (PCC);Reference points". +- [20] 3GPP TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces". +- [21] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [22] 3GPP TS 29.215: "Policy and Charging Control (PCC) over S9 reference point; Stage 3". +- [23] IETF RFC 5516: "Diameter Command Code Registration for Third Generation Partnership Project (3GPP) Evolved Packet System (EPS)". +- [24] 3GPP TS 29.172: "Location Services (LCS); Evolved Packet Core (EPC) LCS Protocol (ELP) between the Gateway Mobile Location Centre (GMLC) and the Mobile Management Entity (MME); SLg interface". +- [25] 3GPP TS 29.173: "Location Services (LCS); Diameter-based SLh interface for Control Plane LCS". +- [26] 3GPP TS 29.219: "Policy and Charging Control: Spending Limit Reporting over Sy reference point". +- [27] 3GPP TS 29.368: "Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS)". +- [28] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications". +- [29] 3GPP TS 29.337: "Diameter-based T4 interface for communications with packet data networks and applications". +- [30] 3GPP TS 29.338: "Diameter based protocols to support SMS capable MMEs". +- [31] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE)". +- [32] 3GPP TS 29.343: "Proximity-services (ProSe) function to ProSe application server aspects (PC2)". +- [33] 3GPP TS 29.344: "Proximity-services (ProSe) Function to Home Subscriber Server (HSS) aspects". +- [34] 3GPP TS 29.345: "Inter-Proximity-services (Prose) function signalling aspects; Stage 3". +- [35] 3GPP TS 29.217: "Policy and Charging Control over Np reference point". +- [36] 3GPP TS 29.128: "Diameter based T6a/T6b interface between the MME/SGSN and the SCEF". +- [37] 3GPP TS 29.153: "Service exposure functionality between SCEF and RCAF reference point". +- [38] 3GPP TS 29.154: "Service capability exposure functionality over Nt Reference point". +- [39] 3GPP TS 29.283: "Diameter Data Management applications". + +- [40] 3GPP TS 29.388: "V2X Control Function to V2X Control Function to Home Subscriber Server (HSS) aspects (V4)". +- [41] 3GPP TS 29.389: "Inter-V2X Control Function Signalling aspects (V6)". +- [42] 3GPP TS 29.561: "Interworking between 5G Network and external Data Networks; Stage 3". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**3GPP specific:** A definition which is used in conjunction with the 3GPP's vendor identifier. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|-------------------------------------| +| AVP | Attribute-Value-Pair | +| CR | Change Request | +| IANA | Internet Assigned Numbers Authority | +| IETF | Internet Engineering Task Force | +| LS | Liaison Statement | + +# --- 4 Application identifiers + +The Diameter applications are identified with the application identifiers as specified in the RFC 3588 [9]. There are two kind of applications: IETF standards track applications and vendor specific applications. All application identifiers are assigned by IANA [12]. This chapter lists the application identifiers assigned by IANA to all 3GPP Diameter applications. + +The application identifiers are transferred in Diameter command's header in the Application-ID field. + +## 4.1 3GPP specific application identifiers + +The 3GPP specific application identifiers allocated by IANA are listed in the following table. + +Table 4.1: 3GPP specific application identifiers + +| Application identifier | Application | 3GPP TS | +|------------------------|-------------------------------|---------------------------| +| 16777216 | 3GPP Cx/Px | 29.228 [1] and 29.229 [2] | +| 16777217 | 3GPP Sh/Ph | 29.328 [3] and 29.329 [4] | +| 16777218 | 3GPP Re | 32.296 [14] | +| 16777219 | 3GPP Wx | 29.234 [6] | +| 16777220 | 3GPP Zn | 29.109 [7] | +| 16777221 | 3GPP Zh | 29.109 [7] | +| 16777222 | 3GPP Gq | 29.209 [8] | +| 16777223 | 3GPP Gmb | 29.061 [13] | +| 16777224 | 3GPP Gx | 29.210 [15] | +| 16777225 | 3GPP Gx over Gy | 29.210 [15] | +| 16777226 | 3GPP MM10 | 29.140 [16] | +| 16777229 | 3GPP Rx | 29.211 [17] | +| 16777230 | 3GPP Pr | 29.234 [6] | +| 16777236 | 3GPP Rx | 29.214 [18] | +| 16777238 | 3GPP Gx | 29.212 [19] | +| 16777250 | 3GPP STa | 29.273 [20] | +| 16777251 | 3GPP S6a | 29.272 [21] | +| 16777252 | 3GPP S13/S13' | 29.272 [21] | +| 16777255 | 3GPP SLg | 29.172 [24] | +| 16777264 | 3GPP SWm | 29.273 [20] | +| 16777265 | 3GPP SWx | 29.273 [20] | +| 16777266 | 3GPP Gxx | 29.212 [19] | +| 16777267 | 3GPP S9 | 29.215 [22] | +| 16777268 | 3GPP Zpn | 29.109 [7] | +| 16777272 | 3GPP S6b | 29.273 [20] | +| 16777291 | 3GPP SLh | 29.173 [25] | +| 16777292 | 3GPP SGmb | 29.061 [13] | +| 16777302 | 3GPP Sy | 29.219 [26] | +| 16777303 | 3GPP Sd | 29.212 [19] | +| 16777308 | 3GPP S7a | 29.272 [21] | +| 16777309 | 3GPP Tsp | 29.368 [27] | +| 16777310 | 3GPP S6m | 29.336 [28] | +| 16777311 | 3GPP T4 | 29.337 [29] | +| 16777312 | 3GPP S6c | 29.338 [30] | +| 16777313 | 3GPP SGd | 29.338 [30] | +| 16777318 | 3GPP S15 | 29.212 [19] | +| 16777319 | 3GPP S9a | 29.215 [22] | +| 16777320 | 3GPP S9a* | 29.215 [22] | +| 16777335 | 3GPP MB2-C | 29.468 [31] | +| 16777336 | 3GPP PC4a | 29.344 [33] | +| 16777337 | 3GPP PC2 | 29.343 [32] | +| 16777340 | 3GPP PC6/PC7 | 29.345 [34] | +| 16777342 | 3GPP Np | 29.217 [35] | +| 16777345 | 3GPP S6t | 29.336 [28] | +| 16777346 | 3GPP T6a/T6b | 29.128 [36] | +| 16777347 | 3GPP Ns | 29.153[37] | +| 16777348 | 3GPP Nt | 29.154[38] | +| 16777349 | 3GPP St | 29.212 [19] | +| 16777350 | 3GPP PC2 | 29.343 [32] | +| 16777351 | 3GPP Diameter Data Management | 29.283 [39] | +| 16777355 | 3GPP V4 | 29.388 [40] | +| 16777356 | 3GPP V6 | 29.389 [41] | +| 16777358 | 3GPP Nta | 29.154 [38] | + +# 5 Command codes + +The command codes are used for communicating the command associated with the Diameter message. The command code is carried in the Diameter header's Command-Code field. The command codes can be divided into standard command codes allocated by IANA and experimental command codes for testing purposes only. + +## 5.1 Command codes allocated for 3GPP + +Based on the IETF RFC 3589 [10] the IANA has allocated a standard command code range 300 - 313 for 3GPP. The command codes are presented in the following table. + +**Table 5.1/1: Command code values allocated for 3GPP** + +| Command code value | Command name | Abbreviation | Specified in 3GPP TS | +|--------------------|------------------------------------------|--------------|----------------------| +| 300 | User-Authorization-Request/-Answer | UAR/UAA | 29.229 [2] | +| 301 | Server-Assignment-Request/-Answer | SAR/SAA | | +| 302 | Location-Info-Request/-Answer | LIR/LIA | | +| 303 | Multimedia-Auth-Request/-Answer | MAR/MAA | | +| 304 | Registration-Termination-Request/-Answer | RTR/RTA | | +| 305 | Push-Profile-Request/-Answer | PPR/PPA | | +| 306 | User-Data-Request/-Answer | UDR/UDA | 29.329 [4] | +| 307 | Profile-Update-Request/-Answer | PUR/PUA | | +| 308 | Subscribe-Notifications-Request/-Answer | SNR/SNA | | +| 309 | Push-Notification-Request/-Answer | PNR/PNA | | +| 310 | Boostrapping-Info-Request/Answer | BIR/BIA | 29.109 [7] | +| 311 | Message-Process-Request/Answer | MPR/MPA | 29.140 [16] | +| 312 | GBAPush-Info-Request/Answer | GPR/GPI | 29.109 [7] | + +**Editor's Note:** The following command codes have been allocated to 3GPP, but they have not been used yet. + +**Table 5.1/2: Command codes allocated for 3GPP** + +| Command code value | Command name | Abbreviation | Specified in 3GPP TS | +|--------------------|--------------|--------------|----------------------| +| 313 | | | | + +As defined in the IETF RFC 5516 [23], IANA has allocated the following command code values for the S6a/S6d interface application and S13/S13' interface application. + +**Table 5.1/3: SAE related Standard Command code values allocated for 3GPP** + +| Command code value | Command name | Abbreviation | Specified in 3GPP TS | +|--------------------|----------------------------------------------|--------------|----------------------| +| 316 | Update-Location-Request/Answer | ULR/ULA | 29.272 [21] | +| 317 | Cancel-Location-Request/Answer | CLR/CLA | | +| 318 | Authentication- Information - Request/Answer | AIR/AIA | | +| 319 | Insert Subscriber Data-Request/Answer | IDR/IDA | | +| 320 | Delete-Subscriber-Data-Request/Answer | DSR/DSA | | +| 321 | Purge-UE-Request/Answer | PUR/PUA | | +| 322 | Reset-Request/Answer | RSR/RSA | | +| 323 | Notify-Request/Answer | NOR/NOA | | +| 324 | ME-Identity-Check-Request/Answer | ECR/ECA | | + +Besides the standard command code values allocated for 3GPP, IANA has allocated the following vendor-specific command code values for 3GPP vendor-specific Diameter applications: + +Table 5.1/4: Vendor-specific command codes allocated for 3GPP + +| Command code value | Command name | Abbreviation | Specified in 3GPP TS | +|--------------------|---------------------------------------------------|--------------|----------------------| +| 8388620 | Provide-Location-Request/Answer | PLR/PLA | 29.172 [24] | +| 8388621 | Location-Report-Request/Answer | LRR/LRA | | +| 8388622 | LCS-Routing-Info-Request/Answer | RIR/RIA | 29.173 [25] | +| 8388635 | Spending-Limit-Request/Answer | SLR/SLA | 29.219 [26] | +| 8388636 | Spending-Status-Notification-Request/Answer | SNR/SNA | | +| 8388637 | TDF-Session-Request/Answer | TSR/TSA | 29.212 [19] | +| 8388731 | TSSF-Notification-Request/Answer | TNR/TNA | | +| 8388638 | Update-VCSG-Location-Request/Answer | UVR/UVA | 29.272 [21] | +| 8388642 | Cancel-VCSG-Location-Request/Answer | CVR/CVA | | +| 8388639 | Device-Action-Request/Answer | DAR/DAA | 29.368 [27] | +| 8388640 | Device-Notification-Request/Answer | DNR/DNA | | +| 8388641 | Subscriber-Information-Request/Answer | SIR/SIA | 29.336 [28] | +| 8388718 | Configuration-Information-Request/Answer | CIR/CIA | 29.336 [28] | +| 8388719 | Reporting-Information-Request/Answer | RIR/RIA | | +| 8388726 | NIDD-Information-Request/Answer | NIR/NIA | | +| 8388643 | Device-Trigger-Request/Answer | DTR/DTA | 29.337 [29] | +| 8388644 | Delivery-Report-Request/Answer | DRR/DRA | | +| 8388645 | MO-Forward-Short-Message Request/Answer | OFR/OFA | 29.338 [30] | +| 8388646 | MT-Forward-Short-Message Request/Answer | TFR/TFA | | +| 8388647 | Send-Routing-Info-for-SM-Request/Answer | SRR/SRA | | +| 8388648 | Alert-Service-Centre-Request/Answer | ALR/ALA | | +| 8388649 | Report-SM-Delivery-Status-Request/Answer | RDR/RDA | | +| 8388656 | Trigger-Establishment-Request/Answer | TER/TEA | 29.215 [30] | +| 8388662 | GCS-Action-Request/Answer | GAR/GAA | 29.468 [31] | +| 8388663 | GCS-Notification-Request/Answer | GNR/GNA | | +| 8388664 | ProSe-Subscriber-Information-Request/Answer | PIR/PIA | 29.344 [33] | +| 8388665 | Update-ProSe-Subscriber-Data-Request/Answer | UPR/UPA | | +| 8388666 | ProSe-Notify-Request/Answer | PNR/PNA | | +| 8388713 | ProSe-Initial-Location-Information-Request/Answer | PSR/PSA | | +| 8388668 | ProSe-Authorization-Request/Answer | PAR/PAA | 29.345 [34] | +| 8388669 | ProSe-Discovery-Request/Answer | PDR/PDA | | + +| | | | | +|---------|-------------------------------------------------|---------|-------------| +| 8388670 | ProSe-Match-Request/Answer | PMR/PMA | | +| 8388671 | ProSe-Match-Report-Info-Request/Answer | PIR/PIA | | +| 8388672 | ProSe-Proximity-Request/Answer | PRR/PRA | | +| 8388673 | ProSe-Location-Update-Request/Answer | PLR/PLA | | +| 8388674 | ProSe-Alert-Request/Answer | ALR/ALA | | +| 8388675 | ProSe-Cancellation-Request/Answer | RPR/RPA | | +| 8388676 | ProXimity-Action-Request/Answer | PXR/PXA | | +| 8388727 | ProXimity-Application-Request/Answer | XAR/XAA | 29.343 [32] | +| 8388720 | Non-Aggregated-RUCI-Report-Request/Answer | NRR/NRA | | +| 8388721 | Aggregated-RUCI-Report-Request/Answer | ARR/ARA | 29.217 [35] | +| 8388722 | Modify-Uecontext-Request/Answer | MUR/MUA | | +| 8388724 | Network-Status-Request/Answer | NSR/NSA | | +| 8388725 | Network-Status-Continuous-Report-Request/Answer | NCR/NCA | 29.153 [37] | +| 8388723 | Background-Data-Transfer-Request/Answer | BTR/BTA | 29.154 [38] | +| 8388728 | Data-Pull-Request/Answer | DPR/DPA | | +| 8388729 | Data-Update-Request/Answer | DUR/DUA | 29.283 [39] | +| 8388730 | Notification-Data-Request/Answer | NDR/NDA | | +| 8388732 | Connection-Management-Request/Answer | CMR/CMA | | +| 8388733 | MO-Data-Request/Answer | ODR/ODA | 29.128 [36] | +| 8388734 | MT-Data-Request/Answer | TDR/TDA | | +| 8388735 | Event-Configuration-Request/Answer | ECR/ECA | | +| 8388736 | Event-Reporting-Request/Answer | ERR/ERA | 29.154 [38] | + +# 6 Vendor identifier + +The vendor identifier (also known as Enterprise number) indicates the vendor specific attributes, result codes and application identifiers in Diameter commands. The vendor identifier is used in the Vendor-ID field of the AVP header and in the Vendor-Id AVP. The Vendor-Id AVP is used to identify the vendor in the Vendor-Specific-Application-Id and Experimental-Result-Code grouped AVPs. + +## 6.1 3GPP's vendor identifier + +The IANA has allocated a vendor identifier value 10415 for 3GPP [11]. + +# --- 7 Attribute-Value-Pair codes + +The AVP codes are used together with the vendor identifier to identify each attribute uniquely. There are multiple AVP namespaces. The IETF IANA namespace, that is, the AVPs with vendor identifier zero or without vendor identifier, is controlled by IANA. Each vendor controls the AVP codes within their AVP namespaces. + +## 7.1 3GPP specific AVP codes + +The 3GPP specific AVPs have the Vendor-Specific bit ('V' bit) set in the AVP header and they carry the 3GPP's vendor identifier in the Vendor-ID field of the AVP header. The 3GPP specific AVP codes are presented in the following table. + +**Table 7.1: 3GPP specific AVP codes** + +| AVP Code | Attribute Name | Data Type | Specified in the 3GPP TS | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|------------------|--------------------------| +| 100 | 3GPP-WLAN-APN-Id | OctetString | | +| 101 | 3GPP-WLAN-QoS-Filter-Rule | UTF8String | 29.234 [6] | +| 102 | 3GPP-WLAN-QoS-Filter-Support | OctetString | | +| Note: The AVP codes from 1 to 255 are reserved for backwards compatibility with 3GPP RADIUS Vendor Specific Attributes (See 3GPP TS 29.061 [13], 3GPP TS 29.561 [42] and 3GPP TS 29.234 [6]) | | | | +| Note: The AVP codes from 256 to 299 are reserved for future use. | | | | +| 300 | Authentication-Method | Enumerated | | +| 301 | Authentication-Information-SIM | OctetString | | +| 302 | Authorization -Information-SIM | OctetString | | +| 303 | WLAN-User-Data | Grouped | | +| 304 | Charging-Data | Grouped | | +| 305 | WLAN-Access | Enumerated | | +| 306 | WLAN- 3GPP-IP-Access | Enumerated | | +| 307 | APN-Authorized | Grouped | | +| 308 | APN-Id | | | +| 309 | APN-Barring-Type | Enumerated | | +| 310 | WLAN-Direct-IP-Access | Enumerated | 29.234 [6] | +| 311 | Session-Request-Type | Enumerated | | +| 312 | Routing-Policy | IPFilterRule | | +| 313 | Max-Requested-Bandwidth | OctetString | | +| 314 | Charging-Characteristics | Integer | | +| 315 | Charging-Nodes | Grouped | | +| 316 | Primary-OCS-Charging-Function-Name | DiameterIdentity | | +| 317 | Secondary-OCS-Charging-Function-Name | DiameterIdentity | | +| 318 | 3GPP-AAA-Server-Name | DiameterIdentity | | +| 319 | Maximum-Number-Accesses | Unsigned32 | | +| Note 1: The AVP codes from 320 to 399 are reserved for TS 29.234 | | | | +| Note 2: The 3GPP-AAA-Server-Name definition is moved to TS 29.273 starting from Rel-12. | | | | +| 400 | GBA-UserSecSettings | OctetString | | +| 401 | Transaction-Identifier | OctetString | | +| 402 | NAF-Hostname | OctetString | | +| 403 | GAA-Service-Identifier | OctetString | | +| 404 | Key-ExpiryTime | Time | | +| 405 | ME-Key-Material | OctetString | | +| 406 | UICC-Key-Material | OctetString | | +| 407 | GBA_U-Awareness-Indicator | Enumerated | | +| 408 | BootstrapInfoCreationTime | Time | | +| 409 | GUSS-Timestamp | Time | | +| 410 | GBA-Type | Enumerated | 29.109 [7] | +| 411 | UE-Id | OctetString | | +| 412 | UE-Id-Type | Enumerated | | +| 413 | UICC-App-Label | OctetString | | +| 414 | UICC-ME | Enumerated | | +| 415 | Requested-Key-Lifetime | Time | | +| 416 | Private-Identity-Request | Enumerated | | +| 417 | GBA-Push-Info | OctetString | | +| 418 | NAF-SA-Identifier | OctetString | | +| 419 | Security-Feature-Request | OctetString | | +| 420 | Security-Feature-Response | OctetString | | +| Note: The AVP codes from 421 to 499 are reserved for TS 29.109 | | | | +| 500 | Abort-Cause | Enumerated | | +| 501 | Access-Network-Charging-Address | Address | 29.209 [8], | +| 502 | Access-Network-Charging-Identifier | Grouped | 29.211 | +| 503 | Access-Network-Charging-Identifier-Value | OctetString | [17] , | +| 504 | AF-Application-Identifier | OctetString | 29.214 | +| 505 | AF-Charging-Identifier | OctetString | [18] | +| 506 | Authorization-Token | OctetString | | + +| | | | +|-----|---------------------------------------|--------------| +| 507 | Flow-Description | IPFilterRule | +| 508 | Flow-Grouping | Grouped | +| 509 | Flow-Number | Unsigned32 | +| 510 | Flows | Grouped | +| 511 | Flow-Status | Enumerated | +| 512 | Flow-Usage | Enumerated | +| 513 | Specific-Action | Enumerated | +| 514 | Max-Requested-Bandwidth | Unsigned32 | +| 515 | Max-Requested-Bandwidth-DL | Unsigned32 | +| 516 | Max-Requested-Bandwidth-UL | Unsigned32 | +| 517 | Media-Component-Description | Grouped | +| 518 | Media-Component-Number | Unsigned32 | +| 519 | Media-Sub-Component AVP | Grouped | +| 520 | Media-Type | Enumerated | +| 521 | RR-Bandwidth | Unsigned32 | +| 522 | RS-Bandwidth | Unsigned32 | +| 523 | SIP-Forking-Indication | Enumerated | +| 524 | Codec-Data | OctetString | +| 525 | Service-URN | OctetString | +| 526 | Acceptable-Service-Info | Grouped | +| 527 | Service-Info-Status | Enumerated | +| 528 | MPS-Identifier | OctetString | +| 529 | AF-Signalling-Protocol | Enumerated | +| 530 | Sponsored-Connectivity-Data | Grouped | +| 531 | Sponsor-Identity | OctetString | +| 532 | Application-Service-Provider-Identity | OctetString | +| 533 | Rx-Request-Type | Enumerated | +| 534 | Min-Requested-Bandwidth-DL | Unsigned32 | +| 535 | Min-Requested-Bandwidth-UL | Unsigned32 | +| 536 | Required-Access-Info | Enumerated | +| 537 | IP-Domain-Id | OctetString | +| 538 | GCS-Identifier | OctetString | +| 539 | Sharing-Key-DL | Unsigned32 | +| 540 | Sharing-Key-UL | Unsigned32 | +| 541 | Retry-Interval | Unsigned32 | +| 542 | Sponsoring-Action | Enumerated | +| 543 | Max-Supported-Bandwidth-DL | Unsigned32 | +| 544 | Max-Supported-Bandwidth-UL | Unsigned32 | +| 545 | Min-Desired-Bandwidth-DL | Unsigned32 | +| 546 | Min-Desired-Bandwidth-UL | Unsigned32 | +| 547 | MCPTT-Identifier | OctetString | +| 548 | Service-Authorization-Info | Unsigned32 | +| 549 | Media-Component-Status | Unsigned32 | +| 550 | Priority-Sharing-Indicator | Enumerated | +| 551 | AF-Requested-Data | Unsigned32 | +| 552 | Content-Version | Unsigned64 | +| 553 | Pre-emption-Control-Info | Unsigned32 | +| 554 | Extended-Max-Requested-BW-DL | Unsigned32 | +| 555 | Extended-Max-Requested-BW-UL | Unsigned32 | +| 556 | Extended-Max-Supported-BW-DL | Unsigned32 | +| 557 | Extended-Max-Supported-BW-UL | Unsigned32 | +| 558 | Extended-Min-Desired-BW-DL | Unsigned32 | +| 559 | Extended-Min-Desired-BW-UL | Unsigned32 | +| 560 | Extended-Min-Requested-BW-DL | Unsigned32 | +| 561 | Extended-Min-Requested-BW-UL | Unsigned32 | +| 562 | MCVideo-Identifier | OctetString | +| 563 | IMS-Content-Identifier | OctetString | +| 564 | IMS-Content-Type | Enumerated | +| 565 | Callee-Information | Grouped | +| 566 | FLUS-Identifier | OctetString | +| 567 | Desired-Max-Latency | Float32 | +| 568 | Desired-Max-Loss | Float32 | +| 569 | NID | OctetString | +| 570 | MA-Information | Grouped | +| 571 | MA-Information-Action | Unsigned32 | + +| | | | | +|-----------------------------------------------------------------------------------------|---------------------------------------------|-------------|------------| +| 572 | 5GS-RAN-NAS-Release-Cause | Grouped | | +| 573 | 5GMM-Cause | Unsigned32 | | +| 574 | 5GSM-Cause | Unsigned32 | | +| 575 | NGAP-Cause | Grouped | | +| 576 | NGAP-Group | Unsigned32 | | +| 577 | NGAP-Value | Unsigned32 | | +| 578 | Wireline-User-Location-Info | Grouped | | +| 579 | HFC-Node-Identifier | OctetString | | +| 580 | GLI-Identifier | OctetString | | +| 581 | Line-Type | Unsigned32 | | +| Note: The AVP codes from 582 to 599 are reserved for TS 29.209, TS 29.211 and TS 29.214 | | | | +| 600 | Visited-Network-Identifier | OctetString | | +| 601 | Public-Identity | UTF8String | | +| 602 | Server-Name | UTF8String | | +| 603 | Server-Capabilities | Grouped | | +| 604 | Mandatory-Capability | Unsigned32 | | +| 605 | Optional-Capability | Unsigned32 | | +| 606 | User-Data | OctetString | | +| 607 | SIP-Number-Auth-Items | Unsigned32 | | +| 608 | SIP-Authentication-Scheme | UTF8String | | +| 609 | SIP-Authenticate | OctetString | | +| 610 | SIP-Authorization | OctetString | | +| 611 | SIP-Authentication-Context | OctetString | | +| 612 | SIP-Auth-Data-Item | Grouped | | +| 613 | SIP-Item-Number | Unsigned32 | | +| 614 | Server-Assignment-Type | Enumerated | | +| 615 | Deregistration-Reason | Grouped | | +| 616 | Reason-Code | Enumerated | | +| 617 | Reason-Info | UTF8String | | +| 618 | Charging-Information | Grouped | | +| 619 | Primary-Event-Charging-Function-Name | DiameterURI | | +| 620 | Secondary-Event-Charging-Function-Name | DiameterURI | | +| 621 | Primary-Charging-Collection-Function-Name | DiameterURI | | +| 622 | Secondary-Charging-Collection-Function-Name | DiameterURI | | +| 623 | User-Authorization-Type | Enumerated | | +| 624 | User-Data-Already-Available | Enumerated | | +| 625 | Confidentiality-Key | OctetString | | +| 626 | Integrity-Key | OctetString | | +| 627 | User-Data-Request-Type | Enumerated | 29.229 [2] | +| 628 | Supported-Features | Grouped | | +| 629 | Feature-List-ID | Unsigned32 | | +| 630 | Feature-List | Unsigned32 | | +| 631 | Supported-Applications | Grouped | | +| 632 | Associated-Identities | Grouped | | +| 633 | Originating-Request | Enumerated | | +| 634 | Wildcarded-Public-Identity | UTF8String | | +| 635 | SIP-Digest-Authenticate | Grouped | | +| 636 | Wildcarded-IMPU | UTF8String | | +| 637 | UAR-Flags | Unsigned32 | | +| 638 | Loose-Route-Indication | Enumerated | | +| 639 | SCSCF-Restoration-Info | Grouped | | +| 640 | Path | OctetString | | +| 641 | Contact | OctetString | | +| 642 | Subscription-Info | Grouped | | +| 643 | Call-ID-SIP-Header | OctetString | | +| 644 | From-SIP-Header | OctetString | | +| 645 | To-SIP-Header | OctetString | | +| 646 | Record-Route | OctetString | | +| 647 | Associated-Registered-Identities | Grouped | | +| 648 | Multiple-Registration-Indication | Enumerated | | +| 649 | Restoration-Info | Grouped | | +| 650 | Session-Priority | Enumerated | | +| 651 | Identity-with-Emergency-Registration | Grouped | | +| 652 | Privileged-Sender-Indication | Enumerated | | +| 653 | LIA-Flags | Unsigned32 | | + +| | | | | +|-----------------------------------------------------------------|-------------------------------------------|------------------|------------| +| 654 | Initial-CSeq-Sequence-Number | Unsigned32 | | +| 655 | SAR-Flags | Unsigned32 | | +| 656 | Allowed-WAF-WWSF-Identities | Grouped | | +| 657 | WebRTC-Authentication-Function-Name | UTF8String | | +| 658 | WebRTC-Web-Server-Function-Name | UTF8String | | +| 659 | RTR-Flags | Unsigned32 | | +| 660 | P-CSCF-Subscription-Info | Grouped | | +| 661 | Registration-Time-Out | Time | | +| 662 | Alternate-Digest-Algorithm | UTF8String | | +| 663 | Alternate-Digest-HA1 | UTF8String | | +| 664 | Failed-PCSCF | Grouped | | +| 665 | PCSCF-FQDN | DiameterIdentity | | +| 666 | PCSCF-IP-Address | Address | | +| Note: The AVP codes from 667 to 699 are reserved for TS 29.229. | | | | +| 700 | User-Identity | Grouped | | +| 701 | MSISDN | OctetString | | +| 702 | User-Data | OctetString | | +| 703 | Data-Reference | Enumerated | | +| 704 | Service-Indication | OctetString | | +| 705 | Subs-Req-Type | Enumerated | | +| 706 | Requested-Domain | Enumerated | | +| 707 | Current-Location | Enumerated | | +| 708 | Identity-Set | Enumerated | | +| 709 | Expiry-Time | Time | | +| 710 | Send-Data-Indication | Enumerated | | +| 711 | DSAI-Tag | OctetString | 29.329 [4] | +| 712 | One-Time-Notification | Enumerated | | +| 713 | Requested-Nodes | Unsigned32 | | +| 714 | Serving-Node-Indication | Enumerated | | +| 715 | Repository-Data-ID | Grouped | | +| 716 | Sequence-Number | Unsigned32 | | +| 717 | Pre-paging-Supported | Enumerated | | +| 718 | Local-Time-Zone-Indication | Enumerated | | +| 719 | UDR-Flags | Unsigned32 | | +| 720 | Call-Reference-Info | Grouped | | +| 721 | Call-Reference-Number | OctetString | | +| 722 | AS-Number | OctetString | | +| Note: The AVP codes from 723 to 799 are reserved for TS 29.329. | | | | +| Note: The AVP codes from 800 to 822 are reserved for TS 32.299. | | | | +| 823 | Event-Type | Grouped | | +| 824 | SIP-Method | UTF8String | | +| 825 | Event | UTF8String | | +| 826 | Content-Type | UTF8String | | +| 827 | Content-Length | Unsigned32 | | +| 828 | Content-Disposition | UTF8String | | +| 829 | Role-of-Node | Enumerated | | +| 830 | User-Session-Id | UTF8String | | +| 831 | Calling-Party-Address | UTF8String | | +| 832 | Called-Party-Address | UTF8String | | +| 833 | Time-Stamps | Grouped | | +| 834 | SIP-Request-Timestamp | Time | | +| 835 | SIP-Response-Timestamp | Time | | +| 836 | Application-Server | UTF8String | 32.299 [5] | +| 837 | Application-provided-called-party-address | UTF8String | | +| 838 | Inter-Operator-Identifier | Grouped | | +| 839 | Originating-IOI | UTF8String | | +| 840 | Terminating-IOI | UTF8String | | +| 841 | IMS-Charging-Identifier | UTF8String | | +| 842 | SDP-Session-Description | UTF8String | | +| 843 | SDP-Media-Component | Grouped | | +| 844 | SDP-Media-Name | UTF8String | | +| 845 | SDP-Media-Description | UTF8String | | +| 846 | CG-Address | Address | | +| 847 | GGSN-Address | Address | | +| 848 | Served-Party-IP-Address | Address | | + +| | | | | +|-----|-----------------------------------------|-------------|----------------| +| 849 | Authorized-QoS | UTF8String | | +| 850 | Application-Server-Information | Grouped | | +| 851 | Trunk-Group-Id | Grouped | | +| 852 | Incoming-Trunk-Group-Id | UTF8String | | +| 853 | Outgoing-Trunk-Group-Id | UTF8String | | +| 854 | Bearer-Service | OctetString | | +| 855 | Service-Id | UTF8String | | +| 856 | Associated-URI | UTF8String | | +| 857 | Charged-Party | UTF8String | | +| 858 | PoC-Controlling-Address | UTF8String | | +| 859 | PoC-Group-Name | UTF8String | | +| 860 | Cause | Grouped | | +| 861 | Cause-Code | Integer32 | | +| 862 | Node-Functionality | Enumerated | | +| 863 | Service-Specific-Data | UTF8String | | +| 864 | Originator | Enumerated | | +| 865 | PS-Furnish-Charging-Information | Grouped | | +| 866 | PS-Free-Format-Data | OctetString | | +| 867 | PS-Append-Free-Format-Data | Enumerated | | +| 868 | Time-Quota-Threshold | Unsigned32 | | +| 869 | Volume-Quota-Threshold | Unsigned32 | | +| 870 | Trigger-Type | Enumerated | | +| 871 | Quota-Holding-Time | Unsigned32 | | +| 872 | Reporting-Reason | Enumerated | | +| 873 | Service-Information | Grouped | | +| 874 | PS-Information | Grouped | | +| 875 | Reserved | - | | +| 876 | IMS-Information | Grouped | | +| 877 | MMS-Information | Grouped | | +| 878 | LCS-Information | Grouped | | +| 879 | PoC-Information | Grouped | | +| 880 | MBMS-Information | Grouped | | +| 881 | Quota-Consumption-Time | Unsigned32 | | +| 882 | Media-Initiator-Flag | Enumerated | | +| 883 | PoC-Server-Role | Enumerated | | +| 884 | PoC-Session-Type | Enumerated | | +| 885 | Number-Of-Participants | Unsigned32 | | +| 886 | Originator-Address | Grouped | | +| 887 | Participants-Involved | UTF8String | | +| 888 | Expires | Unsigned32 | | +| 889 | Message-Body | Grouped | | +| 890 | Reserved | - | | +| 891 | Reserved | - | | +| 892 | Reserved | - | | +| 893 | Reserved | - | | +| 894 | Reserved | - | | +| 895 | Reserved | - | | +| 896 | Reserved | - | | +| 897 | Address-Data | UTF8String | | +| 898 | Address-Domain | Grouped | | +| 899 | Address-Type | Enumerated | | +| | | | | +| 900 | TMGI | OctetString | 29.061
[13] | +| 901 | Required-MBMS-Bearer-Capabilities | UTF8String | | +| 902 | MBMS-StartStop-Indication | Enumerated | | +| 903 | MBMS-Service-Area | OctetString | | +| 904 | MBMS-Session-Duration | Unsigned32 | | +| 905 | Alternative-APN | UTF8String | | +| 906 | MBMS-Service-Type | Enumerated | | +| 907 | MBMS-2G-3G-Indicator | Enumerated | | +| 908 | MBMS-Session-Identity | OctetString | | +| 909 | RAI | UTF8String | | +| 910 | Additional-MBMS-Trace-Info | OctetString | | +| 911 | MBMS-Time-To-Data-Transfer | Unsigned32 | | +| 912 | MBMS-Session-Identity-Repetition-Number | Unsigned32 | | + +| | | | +|-----|--------------------------------|-------------| +| 913 | MBMS-Required-QoS | UTF8String | +| 914 | MBMS-Counting-Information | Enumerated | +| 915 | MBMS-User-Data-Mode-Indication | Enumerated | +| 916 | MBMS-GGSN-Address | UTF8String | +| 917 | MBMS-GGSN-IPv6-Address | UTF8String | +| 918 | MBMS-BMSC-SSM-IP-Address | UTF8String | +| 919 | MBMS-BMSC-SSM-IPv6-Address | UTF8String | +| 920 | MBMS-Flow-Identifier | OctetString | +| 921 | CN-IP-Multicast-Distribution | Enumerated | +| 922 | MBMS-HC-Indicator | Enumerated | +| 923 | MBMS-Access-Indicator | Enumerated | +| 924 | MBMS-GW-SSM-IP-Address | OctetString | +| 925 | MBMS-GW-SSM-IPv6-Address | OctetString | +| 926 | MBMS-BMSC-SSM-UDP-Port | OctetString | +| 927 | MBMS-GW-UDP-Port | OctetString | +| 928 | MBMS-GW-UDP-Port-Indicator | Enumerated | +| 929 | MBMS-Data-Transfer-Start | Unsigned64 | +| 930 | MBMS-Data-Transfer-Stop | Unsigned64 | +| 931 | MBMS-Flags | Unsigned32 | +| 932 | Restart-Counter | Unsigned32 | +| 933 | Diagnostic-Info | Unsigned32 | +| 934 | MBMS-Cell-List | OctetString | + +Note: The AVP codes from 935 to 999 are reserved for TS 29.061 + +| | | | | +|------|---------------------------------------|--------------|-------------| +| 1000 | Bearer-Usage | Enumerated | | +| 1001 | Charging-Rule-Install | Grouped | | +| 1002 | Charging-Rule-Remove | Grouped | | +| 1003 | Charging-Rule-Definition | Grouped | | +| 1004 | Charging-Rule-Base-Name | UTF8String | | +| 1005 | Charging-Rule-Name | OctetString | | +| 1006 | Event-Trigger | Enumerated | | +| 1007 | Metering-Method | Enumerated | | +| 1008 | Offline | Enumerated | | +| 1009 | Online | Enumerated | | +| 1010 | Precedence | Unsigned32 | | +| 1011 | Reporting-Level | Enumerated | | +| 1012 | TFT-Filter | IPFilterRule | | +| 1013 | TFT-Packet-Filter-Information | Grouped | | +| 1014 | ToS-Traffic-Class | OctetString | | +| 1016 | QoS-Information | Grouped | | +| 1018 | Charging-Rule-Report | Grouped | | +| 1019 | PCC-Rule-Status | Enumerated | | +| 1020 | Bearer-Identifier | OctetString | | +| 1021 | Bearer-Operation | Enumerated | | +| 1022 | Access-Network-Charging-Identifier-Gx | Grouped | | +| 1023 | Bearer-Control-Mode | Enumerated | 29.212 [19] | +| 1024 | Network-Request-Support | Enumerated | | +| 1025 | Guaranteed-Bitrate-DL | Unsigned32 | | +| 1026 | Guaranteed-Bitrate-UL | Unsigned32 | | +| 1027 | IP-CAN-Type | Enumerated | | +| 1028 | QoS-Class-Identifier | Enumerated | | +| 1029 | QoS-Negotiation | Enumerated | | +| 1030 | QoS-Upgrade | Enumerated | | +| 1031 | Rule-Failure-Code | Enumerated | | +| 1032 | RAT-Type | Enumerated | | +| 1033 | Event-Report-Indication | Grouped | | +| 1034 | Allocation-Retention-Priority | Grouped | | +| 1035 | CoA-IP-Address | Address | | +| 1036 | Tunnel-Header-Filter | IPFilterRule | | +| 1037 | Tunnel-Header-Length | Unsigned32 | | +| 1038 | Tunnel-Information | Grouped | | +| 1039 | CoA-Information | Grouped | | +| 1040 | APN-Aggregate-Max-Bitrate-DL | Unsigned32 | | +| 1041 | APN-Aggregate-Max-Bitrate-UL | Unsigned32 | | +| 1042 | Revalidation-Time | Time | | +| 1043 | Rule-Activation-Time | Time | | + +| | | | | +|------------------------------------------------------------------|-----------------------------------|------------------|-------------| +| 1044 | Rule-DeActivation-Time | Time | | +| 1045 | Session-Release-Cause | Enumerated | | +| 1046 | Priority-Level | Unsigned32 | | +| 1047 | Pre-emption-Capability | Enumerated | | +| 1048 | Pre-emption-Vulnerability | Enumerated | | +| 1049 | Default-EPS-Bearer-QoS | Grouped | | +| 1050 | AN-GW-Address | Address | | +| 1051 | QoS-Rule-Install | Grouped | | +| 1052 | QoS-Rule-Remove | Grouped | | +| 1053 | QoS-Rule-Definition | Grouped | | +| 1054 | QoS-Rule-Name | OctetString | | +| 1055 | QoS-Rule-Report | Grouped | | +| 1056 | Security-Parameter-Index | OctetString | | +| 1057 | Flow-Label | OctetString | | +| 1058 | Flow-Information | Grouped | | +| 1059 | Packet-Filter-Content | IPFilterRule | | +| 1060 | Packet-Filter-Identifier | OctetString | | +| 1061 | Packet-Filter-Information | Grouped | | +| 1062 | Packet-Filter-Operation | Enumerated | | +| 1063 | Resource-Allocation-Notification | Enumerated | | +| 1064 | Session-Linking-Indicator | Enumerated | | +| 1065 | PDN-Connection-ID | OctetString | | +| 1066 | Monitoring-Key | OctetString | | +| 1067 | Usage-Monitoring-Information | Grouped | | +| 1068 | Usage-Monitoring-Level | Enumerated | | +| 1069 | Usage-Monitoring-Report | Enumerated | | +| 1070 | Usage-Monitoring-Support | Enumerated | | +| 1071 | CSG-Information-Reporting | Enumerated | | +| 1072 | Packet-Filter-Usage | Enumerated | | +| 1073 | Charging-Correlation-Indicator | Enumerated | | +| 1074 | QoS-Rule-Base-Name | UTF8String | | +| 1075 | Routing-Rule-Remove | Grouped | | +| 1076 | Routing-Rule-Definition | Grouped | | +| 1077 | Routing-Rule-Identifier | OctetString | | +| 1078 | Routing-Filter | Grouped | | +| 1079 | Routing-IP-Address | Address | | +| 1080 | Flow-Direction | Enumerated | | +| 1081 | Routing-Rule-Install | Grouped | | +| 1082 | Credit-Management-Status | Unsigned32 | | +| 1085 | Redirect-Information | Grouped | | +| 1086 | Redirect- Support | Enumerated | | +| 1087 | TDF-Information | Grouped | | +| 1088 | TDF-Application-Identifier | OctetString | | +| 1089 | TDF-Destination-Host | DiameterIdentity | | +| 1090 | TDF-Destination-Realm | DiameterIdentity | | +| 1091 | TDF-IP-address | Address | | +| 1092 | ADC-Rule-Install | Grouped | | +| 1093 | ADC-Rule-Remove | Grouped | | +| 1094 | ADC-Rule-Definition | Grouped | | +| 1095 | ADC-Rule-Base-Name | UTF8String | | +| 1096 | ADC-Rule-Name | OctetString | | +| 1097 | ADC-Rule-Report | Grouped | | +| 1098 | Application-Detection-Information | Grouped | | +| 1099 | PS-to-CS-Session-Continuity | Enumerated | | +| Note: The AVP codes from 1083 to 1084 are reserved for TS 29.212 | | | | +| 1100 | Served-User-Identity | Groupe | 29.140 [16] | +| 1101 | VASP-ID | UTF8Str | | +| 1102 | VAS-ID | UTF8String | | +| 1103 | Trigger-Event | Enumerated | | +| 1104 | Sender-Address | UTF8String | | +| 1105 | Initial-Recipient-Address | Grouped | | +| 1106 | Result-Recipient-Address | Grouped | | +| 1107 | Sequence-Number | Unsigned32 | | +| 1108 | Recipient-Address | UTF8String | | +| 1109 | Routeing-Address | UTF8String | | + +| | | | | +|------------------------------------------------------------------|--------------------------------|-------------|------------| +| 1110 | Originating-Interface | Enumerated | | +| 1111 | Delivery-Report | Enumerated | | +| 1112 | Read-Reply | Enumerated | | +| 1113 | Sender-Visibility | Enumerated | | +| 1114 | Service-Key | UTF8String | | +| 1115 | Billing-Information | UTF8String | | +| 1116 | Status | Grouped | | +| 1117 | Status-Code | UTF8String | | +| 1118 | Status-Text | UTF8String | | +| Note: The AVP codes from 1119 to 1199 are reserved for TS 29.140 | | | | +| 1200 | Domain-Name | UTF8String | | +| 1201 | Recipient-Address | Grouped | | +| 1202 | Submission-Time | Time | | +| 1203 | MM-Content-Type | Grouped | | +| 1204 | Type-Number | Enumerated | | +| 1205 | Additional-Type-Information | UTF8String | | +| 1206 | Content-Size | Unsigned32 | | +| 1207 | Additional-Content-Information | Grouped | | +| 1208 | Addressee-Type | Enumerated | | +| 1209 | Priority | Enumerated | | +| 1210 | Message-ID | UTF8String | | +| 1211 | Message-Type | Enumerated | | +| 1212 | Message-Size | Unsigned32 | | +| 1213 | Message-Class | Grouped | | +| 1214 | Class-Identifier | Enumerated | | +| 1215 | Token-Text | UTF8String | | +| 1216 | Delivery-Report-Requested | Enumerated | | +| 1217 | Adaptations | Enumerated | | +| 1218 | Applic-ID | UTF8String | | +| 1219 | Aux-Applic-Info | UTF8String | | +| 1220 | Content-Class | Enumerated | | +| 1221 | DRM-Content | Enumerated | | +| 1222 | Read-Reply-Report-Requested | Enumerated | | +| 1223 | Reply-Applic-ID | UTF8String | | +| 1224 | File-Repair-Supported | Enumerated | | +| 1225 | MBMS-User-Service-Type | Enumerated | | +| 1226 | Unit-Quota-Threshold | Unsigned32 | | +| 1227 | PDP-Address | Address | 32.299 [5] | +| 1228 | SGSN-Address | Address | | +| 1229 | PoC-Session-Id | UTF8String | | +| 1230 | Deferred-Location-Even-Type | UTF8String | | +| 1231 | LCS-APN | UTF8String | | +| 1232 | LCS-Client-Id | Grouped | | +| 1233 | LCS-Client-Dialed-By-MS | UTF8String | | +| 1234 | LCS-Client-External-ID | UTF8String | | +| 1235 | LCS-Client-Name | Grouped | | +| 1236 | LCS-Data-Coding-Scheme | UTF8String | | +| 1237 | LCS-Format-Indicator | Enumerated | | +| 1238 | LCS-Name-String | UTF8String | | +| 1239 | LCS-Requestor-Id | Grouped | | +| 1240 | LCS-Requestor-Id-String | UTF8String | | +| 1241 | LCS-Client-Type | Enumerated | | +| 1242 | Location-Estimate | OctetString | | +| 1243 | Location-Estimate-Type | Enumerated | | +| 1244 | Location-Type | Grouped | | +| 1245 | Positioning-Data | UTF8String | | +| 1246 | Reserved | - | | +| 1247 | PDP-Context-Type | Enumerated | | +| 1248 | MMBox-Storage-Requested | Enumerated | | +| 1249 | Service-Specific-Info | Grouped | | +| 1250 | Called-Asserted-Identity | UTF8String | | +| 1251 | Requested-Party-Address | UTF8String | | +| 1252 | PoC-User-Role | Grouped | | +| 1253 | PoC-User-Role-IDs | UTF8String | | +| 1254 | PoC-User-Role-info-Units | Enumerated | | + +| | | | | +|-------------------------------------------------------------------|--------------------------------------|-------------|-------------| +| 1255 | Talk-Burst-Exchange | Grouped | | +| 1256 | Service-Generic-Information | Grouped | | +| 1257 | Service-Specific-Type | Unsigned32 | | +| 1258 | Event-Charging-TimeStamp | Time | | +| 1259 | Participant-Access-Priority | Enumerated | | +| 1260 | Participant-Group | Grouped | | +| 1261 | PoC-Change-Conditions | Enumerated | | +| 1262 | PoC-Change-Time | Time | | +| 1263 | Access-Network-Information | OctetString | | +| 1264 | Trigger | Grouped | | +| 1265 | Base-Time-Interval | Unsigned32 | | +| 1266 | Envelope | Grouped | | +| 1267 | Envelope-End-Time | Time | | +| 1268 | Envelope-Reporting | Enumerated | | +| 1269 | Envelope-Start-Time | Time | | +| 1270 | Time-Quota-Mechanism | Grouped | | +| 1271 | Time-Quota-Type | Enumerated | | +| 1272 | Early-Media-Description | Grouped | | +| 1273 | SDP-TimeStamps | Grouped | | +| 1274 | SDP-Offer-Timestamp | Time | | +| 1275 | SDP-Answer-Timestamp | Time | | +| 1276 | AF-Correlation-Information | Grouped | | +| 1277 | PoC-Session-Initiation-type | Enumerated | | +| 1278 | Offline-Charging | Grouped | | +| 1279 | User-Participating-Type | Enumerated | | +| 1280 | Alternate-Charged-Party-Address | UTF8String | | +| 1281 | IMS-Communication-Service-Identifier | UTF8String | | +| 1282 | Number-Of-Received-Talk-Bursts | Unsigned32 | | +| 1283 | Number-Of-Talk-Bursts | Unsigned32 | | +| 1284 | Received-Talk-Burst-Time | Unsigned32 | | +| 1285 | Received-Talk-Burst-Volume | Unsigned32 | | +| 1286 | Talk-Burst-Time | Unsigned32 | | +| 1287 | Talk-Burst-Volume | Unsigned32 | | +| 1288 | Media-Initiator-Party | UTF8String | | +| Note: The AVP codes from 1289 to 1299 are reserved for TS 32.299 | | | | +| 1300 | PC5-Radio-Technology | Enumerated | | +| 1301 | RAN-End-Time | Time | | +| 1302 | RAN-Secondary-RAT-Usage-Report | Grouped | | +| 1303 | RAN-Start-Time | Time | | +| 1304 | Secondary-RAT-Type | OctetString | | +| 1305 | Civic-Address-Information | UTF8String | | +| 1306 | WLAN-Operator-Id | Grouped | | +| 1307 | WLAN-Operator-Name | UTF8String | | +| 1308 | WLAN-PLMN-Id | UTF8String | | +| 1309 | API-Content | UTF8String | | +| 1310 | API-Direction | Enumerated | | +| 1311 | API-Identifier | OctetString | | +| 1312 | API-Invocation-Timestamp | Time | | +| 1313 | API-Result-Code | Unsigned32 | | +| 1314 | API-Size | Unsigned64 | | +| 1315 | API-Network-Service-Node | Enumerated | | +| 1316 | Exposure-Function-API-Information | Grouped | | +| 1317 | SCEF-Address | Address | | +| 1318 | TLTRI | Unsigned32 | | +| 1319 | TTRI | Unsigned32 | | +| 1320 | 3GPP-OC-Specific-Reduction | Grouped | | +| 1321 | 3GPP-OC-Rating-Group | Unsigned32 | | +| 1322 | 3GPP-OC-Request-Type | Enumerated | | +| 1323 | VoLTE-Information | Grouped | | +| Note: The AVP codes from 1324 to 1399 are reserved for TS 32.229. | | | | +| 1400 | Subscription-Data | Grouped | | +| 1401 | Terminal-Information | Grouped | | +| 1402 | IMEI | UTF8String | 29.272 [21] | +| 1403 | Software-Version | UTF8String | | +| 1404 | QoS-Subscribed | UTF8String | | + +| | | | +|------|-----------------------------------------------|-------------| +| 1405 | ULR-Flags | Unsigned32 | +| 1406 | ULA-Flags | Unsigned32 | +| 1407 | Visited PLMN Id | OctetString | +| 1408 | Requested-EUTRAN-Authentication-Info | Grouped | +| 1409 | Requested-UTRAN- GERAN-Authentication-Info | Grouped | +| 1410 | Number-Of-Requested-Vectors | Unsigned32 | +| 1411 | Re-Synchronization-Info | OctetString | +| 1412 | Immediate-Response-Preferred | Unsigned32 | +| 1413 | Authentication-Info | Grouped | +| 1414 | E-UTRAN-Vector | Grouped | +| 1415 | UTRAN-Vector | Grouped | +| 1416 | GERAN-Vector | Grouped | +| 1417 | Network-Access-Mode | Enumerated | +| 1418 | HPLMN-ODB | Enumerated | +| 1419 | Item-Number | Unsigned32 | +| 1420 | Cancellation-Type | Enumerated | +| 1421 | DSR-Flags | Unsigned32 | +| 1422 | DSA-Flags | Unsigned32 | +| 1423 | Context-Identifier | Unsigned32 | +| 1424 | Subscriber-Status | Enumerated | +| 1425 | Operator-Determined-Barring | Unsigned32 | +| 1426 | Access-Restriction-Data | Unsigned32 | +| 1427 | APN-OI-Replacement | UTF8String | +| 1428 | All-APN-Configurations-Included-Indicator | Enumerated | +| 1429 | APN-Configuration-Profile | Grouped | +| 1430 | APN-Configuration | Grouped | +| 1431 | EPS-Subscribed-QoS-Profile | Grouped | +| 1432 | VPLMN-Dynamic-Address-Allowed | Enumerated | +| 1433 | STN-SR | OctetString | +| 1434 | Alert-Reason | Enumerated | +| 1435 | AMBR | Grouped | +| 1436 | CSG-Subscription-Data | Grouped | +| 1437 | CSG-Id | Unsigned32 | +| 1438 | PDN-GW-Allocation-Type | Enumerated | +| 1439 | Expiration-Date | Time | +| 1440 | RAT-Frequency-Selection-Priority-ID | Unsigned32 | +| 1441 | IDA-Flags | Unsigned32 | +| 1442 | PUA-Flags | Unsigned32 | +| 1443 | NOR-Flags | Unsigned32 | +| 1444 | User-Id | UTF8String | +| 1445 | Equipment-Status | Enumerated | +| 1446 | Regional-Subscription-Zone-Code | OctetString | +| 1447 | RAND | OctetString | +| 1448 | XRES | OctetString | +| 1449 | AUTN | OctetString | +| 1450 | KASME | OctetString | +| 1451 | Reserved | - | +| 1452 | Trace-Collection-Entity | Address | +| 1453 | Kc | OctetString | +| 1454 | SRES | OctetString | +| 1455 | Reserved | - | +| 1456 | PDN-Type | Enumerated | +| 1457 | Roaming-Restricted-Due-To-Unsupported-Feature | Enumerated | +| 1458 | Trace-Data | Grouped | +| 1459 | Trace-Reference | OctetString | +| 1460 | Reserved | - | +| 1461 | Reserved | - | +| 1462 | Trace-Depth | Enumerated | +| 1463 | Trace-NE-Type-List | OctetString | +| 1464 | Trace-Interface-List | OctetString | +| 1465 | Trace-Event-List | OctetString | +| 1466 | OMC-Id | OctetString | +| 1467 | GPRS-Subscription-Data | Grouped | +| 1468 | Complete-Data-List-Included-Indicator | Enumerated | +| 1469 | PDP-Context | Grouped | + +| | | | | +|------|---------------------------------------------------|-------------|-------------| +| 1470 | PDP-Type | OctetString | | +| 1471 | 3GPP2-MEID | OctetString | | +| 1472 | Specific-APN-Info | Grouped | | +| 1473 | LCS-Info | Grouped | | +| 1474 | GMLC-Number | OctetString | | +| 1475 | LCS-PrivacyException | Grouped | | +| 1476 | SS-Code | OctetString | | +| 1477 | SS-Status | OctetString | | +| 1478 | Notification-To-UE-User | Enumerated | | +| 1479 | External-Client | Grouped | | +| 1480 | Client-Identity | OctetString | | +| 1481 | GMLC-Restriction | Enumerated | | +| 1482 | PLMN-Client | Enumerated | | +| 1483 | Service-Type | Grouped | | +| 1484 | ServiceTypeIdentity | Unsigned32 | | +| 1485 | MO-LR | Grouped | | +| 1486 | Teleservice-List | Grouped | | +| 1487 | TS-Code | Enumerated | | +| 1488 | Call-Barring-Info | Grouped | | +| 1489 | SGSN-Number | OctetString | | +| 1490 | IDR-Flags | Unsigned32 | | +| 1491 | ICS-Indicator | Enumerated | | +| 1492 | IMS-Voice-Over-PS-Sessions-Supported | Enumerated | | +| 1493 | Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions | Enumerated | | +| 1494 | Last-UE-Activity-Time | Time | | +| 1495 | EPS-User-State | Grouped | | +| 1496 | EPS-Location-Information | Grouped | | +| 1497 | MME-User-State | Grouped | | +| 1498 | SGSN-User-State | Grouped | | +| 1499 | User-State | Enumerated | | +| | | | | +| 1500 | Non-3GPP-User-Data | Grouped | 29.273 [20] | +| 1501 | Non-3GPP-IP-Access | Enumerated | | +| 1502 | Non-3GPP-IP-Access-APN | Enumerated | | +| 1503 | AN-Trusted | Enumerated | | +| 1504 | ANID | UTF8String | | +| 1505 | Trace-Info | Grouped | | +| 1506 | MIP-FA-RK | OctetString | | +| 1507 | MIP-FA-RK-SPI | Unsigned32 | | +| 1508 | PPR-Flags | Unsigned32 | | +| 1509 | WLAN-Identifier | Grouped | | +| 1510 | TWAN-Access-Info | Grouped | | +| 1511 | Access-Authorization-Flags | Unsigned32 | | +| 1512 | TWAN-Default-APN-Context-Id | Unsigned32 | | +| 1513 | Reserved | - | | +| 1514 | Reserved | - | | +| 1515 | Reserved | - | | +| 1516 | Full-Network-Name | OctetString | | +| 1517 | Short-Network-Name | OctetString | | +| 1518 | AAA-Failure-Indication | Unsigned32 | | +| 1519 | Transport-Access-Type | Enumerated | | +| 1520 | DER-Flags | Unsigned32 | | +| 1521 | DEA-Flags | Unsigned32 | | +| 1522 | RAR-Flags | Unsigned32 | | +| 1523 | DER-S6b-Flags | Unsigned32 | | +| 1524 | SSID | UTF8String | | +| 1525 | HESSID | UTF8String | | +| 1526 | Access-Network-Info | Grouped | | +| 1527 | TWAN-Connection-Mode | Unsigned32 | | +| 1528 | TWAN-Connectivity-Parameters | Grouped | | +| 1529 | Connectivity-Flags | Unsigned32 | | +| | | | | +| 1530 | TWAN-PCO | OctetString | | +| 1531 | TWAG-CP-Address | Address | | +| 1532 | TWAG-UP-Address | UTF8String | | +| 1533 | TWAN-S2a-Failure-Cause | Unsigned32 | | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|------------------|--| +| 1534 | SM-Back-Off-Timer | Unsigned32 | | +| 1535 | WLCP-Key | OctetString | | +| 318 | 3GPP-AAA-Server-Name | DiameterIdentity | | +| 1536 | Origination-Time-Stamp | Unsigned64 | | +| 1537 | Maximum-Wait-Time | Unsigned32 | | +| 1538 | Emergency-Services | Unsigned32 | | +| 1539 | AAR-Flags | Unsigned32 | | +| 1540 | IMEI-Check-In-VPLMN-Result | Unsigned32 | | +| 1541 | ERP-Authorization | Unsigned32 | | +| 1542 | High-Priority-Access-Info | Unsigned32 | | +| Note 1: The AVP codes from 1543 to 1599 are reserved for TS 29.273 | | | | +| Note 2: The AVP 3GPP-AAA-Server-Name was originally defined in 3GPP TS 29.234 and is now defined in 3GPP TS 29.273 from Rel-12. | | | | +| 1600 | MME-Location-Information | Grouped | | +| 1601 | SGSN-Location-Information | Grouped | | +| 1602 | E-UTRAN-Cell-Global-Identity | OctetString | | +| 1603 | Tracking-Area-Identity | OctetString | | +| 1604 | Cell-Global-Identity | OctetString | | +| 1605 | Routing-Area-Identity | OctetString | | +| 1606 | Location-Area-Identity | OctetString | | +| 1607 | Service-Area-Identity | OctetString | | +| 1608 | Geographical-Information | OctetString | | +| 1609 | Geodetic-Information | OctetString | | +| 1610 | Current-Location-Retrieved | Enumerated | | +| 1611 | Age-Of-Location-Information | Unsigned32 | | +| 1612 | Active-APN | Grouped | | +| 1613 | SIPTO-Permission | Enumerated | | +| 1614 | Error-Diagnostic | Enumerated | | +| 1615 | UE-SRVCC-Capability | Enumerated | | +| 1616 | MPS-Priority | Unsigned32 | | +| 1617 | VPLMN-LIPA-Allowed | Enumerated | | +| 1618 | LIPA-Permission | Enumerated | | +| 1619 | Subscribed-Periodic-RAU-TAU-Timer | Unsigned32 | | +| 1620 | Ext-PDP-Type | OctetString | | +| 1621 | Ext-PDP-Address | Address | | +| 1622 | MDT-Configuration | Grouped | | +| 1623 | Job-Type | Enumerated | | +| 1624 | Area-Scope | Grouped | | +| 1625 | List-Of-Measurements | Unsigned32 | | +| 1626 | Reporting-Trigger | Unsigned32 | | +| 1627 | Report-Interval | Enumerated | | +| 1628 | Report-Amount | Enumerated | | +| 1629 | Event-ThresholdRSRP | Unsigned32 | | +| 1630 | Event-ThresholdRSRQ | Unsigned32 | | +| 1631 | Logging-Interval | Enumerated | | +| 1632 | Logging-Duration | Enumerated | | +| 1633 | Relay-Node-Indicator | Enumerated | | +| 1634 | MDT-User-Consent | Enumerated | | +| 1635 | PUR-Flags | Unsigned32 | | +| 1636 | Subscribed-VSRVCC | Enumerated | | +| 1637 | Equivalent-PLMN-List | Grouped | | +| 1638 | CLR-Flags | Unsigned32 | | +| 1639 | UVR-Flags | Unsigned32 | | +| 1640 | UVA-Flags | Unsigned32 | | +| 1641 | VPLMN-CSG-Subscription-Data | Grouped | | +| 1642 | Time-Zone | UTF8String | | +| 1643 | A-MSISDN | OctetString | | +| 1644 | Reserved | - | | +| 1645 | MME-Number-for-MT-SMS | OctetString | | +| 1646 | Reserved | - | | +| 1647 | Reserved | - | | +| 1648 | SMS-Register-Request | Enumerated | | +| 1649 | Local-Time-Zone | Grouped | | +| 1650 | Daylight-Saving-Time | Enumerated | | +| 1651 | GMLC-Info | Grouped | | + +29.272 +[21] + +| | | | +|------|------------------------------------------|------------------| +| 1652 | GMLC-Name | DiameterIdentity | +| 1653 | GMLC-Realm | DiameterIdentity | +| 1654 | Subscription-Data-Flags | Unsigned32 | +| 1655 | Measurement-Period-LTE | Enumerated | +| 1656 | Measurement-Period-UMTS | Enumerated | +| 1657 | Collection-Period-RRM-LTE | Enumerated | +| 1658 | Collection-Period-RRM-UMTS | Enumerated | +| 1659 | Positioning-Method | OctetString | +| 1660 | Measurement-Quantity | OctetString | +| 1661 | Event-Threshold-Event-1F | Integer32 | +| 1662 | Event-Threshold-Event-1I | Integer32 | +| 1663 | Restoration-Priority | Unsigned32 | +| 1664 | SGs-MME-Identity | UTF8String | +| 1665 | SIPTO-Local-Network-Permission | Unsigned32 | +| 1666 | Coupled-Node-Diameter-ID | DiameterIdentity | +| 1667 | WLAN-offloadability | Grouped | +| 1668 | WLAN-offloadability-EUTRAN | Unsigned32 | +| 1669 | WLAN-offloadability-UTRAN | Unsigned32 | +| 1670 | Reset-ID | OctetString | +| 1671 | MDT-Allowed-PLMN-Id | OctetString | +| 1672 | Adjacent-PLMNs | Grouped | +| 1673 | Adjacent-Access-Restriction-Data | Grouped | +| 1674 | DL-Buffering-Suggested-Packet-Count | Integer32 | +| 1675 | IMSI-Group-Id | Grouped | +| 1676 | Group-Service-Id | Unsigned32 | +| 1677 | Group-PLMN-Id | OctetString | +| 1678 | Local-Group-Id | OctetString | +| 1679 | AIR-Flags | Unsigned32 | +| 1680 | UE-Usage-Type | Unsigned32 | +| 1681 | Non-IP-PDN-Type-Indicator | Enumerated | +| 1682 | Non-IP-Data-Delivery-Mechanism | Unsigned32 | +| 1683 | Additional-Context-Identifier | Unsigned32 | +| 1684 | SCEF-Realm | DiameterIdentity | +| 1685 | Subscription-Data-Deletion | Grouped | +| 1686 | Preferred-Data-Mode | Unsigned32 | +| 1687 | Emergency-Info | Grouped | +| 1688 | V2X-Subscription-Data | Grouped | +| 1689 | V2X-Permission | Unsigned32 | +| 1690 | PDN-Connection-Continuity | Unsigned32 | +| 1691 | eDRX-Cycle-Length | Grouped | +| 1692 | eDRX-Cycle-Length-Value | OctetString | +| 1693 | UE-PC5-AMBR | Unsigned32 | +| 1694 | MBSFN-Area | Grouped | +| 1695 | MBSFN-Area-ID | Unsigned32 | +| 1696 | Carrier-Frequency | Unsigned32 | +| 1697 | RDS-Indicator | Enumerated | +| 1698 | Service-Gap-Time | Unsigned32 | +| 1699 | Aerial-UE-Subscription-Information | Unsigned32 | +| 1700 | Broadcast-Location-Assistance-Data-Types | Unsigned64 | +| 1701 | Paging-Time-Window | Grouped | +| 1702 | Operation-Mode | Unsigned32 | +| 1703 | Paging-Time-Window-Length | OctetString | +| 1704 | Core-Network-Restrictions | Unsigned32 | +| 1705 | eDRX-Related-RAT | Grouped | +| 1706 | Interworking-5GS-Indicator | Enumerated | +| 1707 | Ethernet-PDN-Type-Indicator | Enumerated | +| 1708 | Subscribed-ARPI | Unsigned32 | +| 1709 | IAB-Operation-Permission | Enumerated | +| 1710 | V2X-Subscription-Data-Nr | Grouped | +| 1711 | UE-PC5-QoS | Grouped | +| 1712 | PC5-QoS-Flow | Grouped | +| 1713 | 5QI | Integer32 | +| 1714 | PC5-Flow-Bitrates | Grouped | +| 1715 | Guaranteed-Flow-Bitrates | Integer32 | +| 1716 | Maximum-Flow-Bitrates | Integer32 | + +| | | | | +|-------------------------------------------------------------------|----------------------------------------|-------------|------------| +| 1717 | PC5-Range | Integer32 | | +| 1718 | PC5-Link-AMBR | Integer32 | | +| 1719 | Third-Context-ID | Unsigned32 | | +| Note: The AVP codes from 1720 to 1799 are reserved for TS 29.272. | | | | +| 2000 | SMS-Information | Grouped | | +| 2001 | Data-Coding-Scheme | Integer32 | | +| 2002 | Destination-Interface | Grouped | | +| 2003 | Interface-Id | UTF8String | | +| 2004 | Interface-Port | UTF8String | | +| 2005 | Interface-Text | UTF8String | | +| 2006 | Interface-Type | Enumerated | | +| 2007 | SM-Message-Type | Enumerated | | +| 2008 | Originating-SCCP-Address | Address | | +| 2009 | Originator-Interface | Grouped | | +| 2010 | Recipient-SCCP-Address | Address | | +| 2011 | Reply-Path-Requested | Enumerated | | +| 2012 | SM-Discharge-Time | Time | | +| 2013 | SM-Protocol-ID | OctetString | | +| 2014 | SM-Status | OctetString | | +| 2015 | SM-User-Data-Header | OctetString | | +| 2016 | SMS-Node | Enumerated | | +| 2017 | SMSC-Address | Address | | +| 2018 | Client-Address | Address | | +| 2019 | Number-of-Messages-Sent | Unsigned32 | | +| 2020 | Low-Balance-Indication | Enumerated | | +| 2021 | Remaining-Balance | Grouped | | +| 2022 | Refund-Information | OctetString | | +| 2023 | Carrier-Select-Routing-Information | UTF8String | | +| 2024 | Number-Portability-Routing-Information | UTF8String | | +| 2025 | PoC-Event-Type | Enumerated | | +| 2026 | Recipient-Info | Grouped | | +| 2027 | Originator-Received-Address | Grouped | | +| 2028 | Recipient-Received-Address | Grouped | | +| 2029 | SM-Service-Type | Enumerated | | +| 2030 | MMTel-Information | Grouped | 32.299 [5] | +| 2031 | MMTel-Sservice-Type | Unsigned32 | | +| 2032 | Service-Mode | Unsigned32 | | +| 2033 | Subscriber-Role | Enumerated | | +| 2034 | Number-Of-Divertions | Unsigned32 | | +| 2035 | Associated-Party-Address | UTF8String | | +| 2036 | SDP-Type | Enumerated | | +| 2037 | Change-Condition | Integer32 | | +| 2038 | Change-Time | Time | | +| 2039 | Diagnostics | Integer32 | | +| 2040 | Service-Data-Container | Grouped | | +| 2041 | Start-Time | Time | | +| 2042 | Stop-Time | Time | | +| 2043 | Time-First-Usage | Time | | +| 2044 | Time-Last-Usage | Time | | +| 2045 | Time-Usage | Unsigned32 | | +| 2046 | Traffic-Data-Volumes | Grouped | | +| 2047 | Serving-Node-Type | Enumerated | | +| 2048 | Supplementary-Service | Grouped | | +| 2049 | Participant-Action-Type | Enumerated | | +| 2050 | PDN-Connection-Charging-ID | Unsigned32 | | +| 2051 | Dynamic-Address-Flag | Enumerated | | +| 2052 | Accumulated-Cost | Grouped | | +| 2053 | AoC-Cost-Information | Grouped | | +| 2054 | AoC-Information | Grouped | | +| 2055 | AoC-Request-Type | Enumerated | | +| 2056 | Current-Tariff | Grouped | | +| 2057 | Next-Tariff | Grouped | | +| 2058 | Rate-Element | Grouped | | +| 2059 | Scale-Factor | Grouped | | +| 2060 | Tariff-Information | Grouped | | + +| | | | | +|-------------------------------------------------------------------|------------------------------------------|------------------|------------| +| 2061 | Unit-Cost | Grouped | | +| 2062 | Incremental-Cost | Grouped | | +| 2063 | Local-Sequence-Number | Unsigned32 | | +| 2064 | Node-Id | UTF8String | | +| 2065 | SGW-Change | Enumerated | | +| 2066 | Charging-Characteristic-Selection-Mode | Enumerated | | +| 2067 | SGW-Address | Address | | +| 2068 | Dynamic-Address-Flag-Extension | Enumerated | | +| Note: The AVP codes from 2069 to 2099 are reserved for TS 32.299. | | | | +| 2100 | reserved | - | | +| 2101 | Application-Server-ID | UTF8String | | +| 2102 | Application-Service-Type | Enumerated | | +| 2103 | Application-Session-ID | Unsigned32 | | +| 2104 | Delivery-Status | UTF8String | | +| 2105 | reserved | - | | +| 2106 | reserved | - | | +| 2107 | reserved | - | | +| 2108 | reserved | - | | +| 2109 | reserved | - | 32.299 [5] | +| 2110 | IM-Information | Grouped | | +| 2111 | Number-Of-Messages-Successfully-Exploded | Unsigned32 | | +| 2112 | Number-Of-Messages-Successfully-Sent | Unsigned32 | | +| 2113 | Total-Number-Of-Messages-Exploded | Unsigned32 | | +| 2114 | Total-Number-Of-Messages-Sent | Unsigned32 | | +| 2115 | DCD-Information | Grouped | | +| 2116 | Content-ID | UTF8String | | +| 2117 | Content-provider-ID | UTF8String | | +| 2118 | Charge-Reason-Code | Enumerated | | +| Note: The AVP codes from 2119 to 2199 are reserved for TS 32.299. | | | | +| 2200 | Subsession-Decision-Info | Grouped | | +| 2201 | Subsession-Enforcement-Info | Grouped | | +| 2202 | Subsession-Id | Unsigned32 | | +| 2203 | Subsession-Operation | Enumerated | | +| 2204 | Multiple-BBERF-Action | Enumerated | | +| 2205 | UE-Local-IPv6-Prefix | OctetString | | +| 2206 | DRA-Deployment | Enumerated | | +| 2207 | PCRF-Address | DiameterIdentity | | +| 2208 | DRA-Binding | Enumerated | | +| Note: The AVP codes from 2209 to 2299 are reserved for TS 29.215. | | | | +| 2300 | reserved | - | | +| 2301 | SIP-Request-Timestamp-Fraction | Unsigned32 | | +| 2302 | SIP-Response-Timestamp-Fraction | Unsigned32 | | +| 2303 | Online-Charging-Flag | Enumerated | | +| 2304 | CUG-Information | OctetString | | +| 2305 | Real-Time-Tariff-Information | Grouped | | +| 2306 | Tariff-XML | UTF8String | | +| 2307 | MBMS GW-Address | Address | | +| 2308 | IMSI-Unauthenticated-Flag | Enumerated | | +| 2309 | Account-Expiration | Time | | +| 2310 | AoC-Format | Enumerated | | +| 2311 | AoC-Service | Enumerated | | +| 2312 | AoC-Service-Obligatory-Type | Grouped | | +| 2313 | AoC-Service-Type | Enumerated | | +| 2314 | AoC-Subscription-Information | Grouped | | +| 2315 | Preferred-AoC-Currency | Unsigned32 | | +| 2316 | Reserved | - | | +| 2317 | CSG-Access-Mode | Enumerated | | +| 2318 | CSG-Membership-Indication | Enumerated | | +| 2319 | User-CSG-Information | Grouped | | +| 2320 | Outgoing-Session-Id | UTF8String | | +| 2321 | Initial-IMS-Charging-Identifier | UTF8String | | +| 2322 | IMS-Emergency-Indicator | Enumerated | | +| 2323 | MBMS-Charged-Party | Enumerated | | +| Note: The AVP codes from 2324 to 2399 are reserved for TS 32.299. | | | | +| 2400 | LMSI | OctetString | 29.173 | + +| | | | | +|-------------------------------------------------------------------|-------------------------------------|------------------|----------------| +| 2401 | Serving-Node | Grouped | [25] | +| 2402 | MME-Name | DiameterIdentity | | +| 2403 | MSC-Number | OctetString | | +| 2404 | LCS-Capabilities-Sets | Unsigned32 | | +| 2405 | GMLC-Address | Address | | +| 2406 | Additional-Serving-Node | Grouped | | +| 2407 | PPR-Address | Address | | +| 2408 | MME-Realm | DiameterIdentity | | +| 2409 | SGSN-Name | DiameterIdentity | | +| 2410 | SGSN-Realm | DiameterIdentity | | +| 2411 | RIA-Flags | Unsigned32 | | +| Note: The AVP codes from 2412 to 2499 are reserved for TS 29.173. | | | | +| 2500 | SLG-Location-Type | Enumerated | 29.172
[24] | +| 2501 | LCS-EPS-Client-Name | Grouped | | +| 2502 | LCS-Requestor-Name | Grouped | | +| 2503 | LCS-Priority | Unsigned32 | | +| 2504 | LCS-QoS | Grouped | | +| 2505 | Horizontal-Accuracy | Unsigned32 | | +| 2506 | Vertical-Accuracy | Unsigned32 | | +| 2507 | Vertical-Requested | Enumerated | | +| 2508 | Velocity-Requested | Enumerated | | +| 2509 | Response-Time | Enumerated | | +| 2510 | Supported-GAD-Shapes | Unsigned32 | | +| 2511 | LCS-Codeword | UTF8String | | +| 2512 | LCS-Privacy-Check | Enumerated | | +| 2513 | Accuracy-Fulfilment-Indicator | Enumerated | | +| 2514 | Age-Of-Location-Estimate | Unsigned32 | | +| 2515 | Velocity-Estimate | OctetString | | +| 2516 | EUTRAN-Positioning-Data | OctetString | | +| 2517 | ECGI | OctetString | | +| 2518 | Location-Event | Enumerated | | +| 2519 | Pseudonym-Indicator | Enumerated | | +| 2520 | LCS-Service-Type-ID | Unsigned32 | | +| 2521 | LCS-Privacy-Check-Non-Session | Grouped | | +| 2522 | LCS-Privacy-Check-Session | Grouped | | +| 2523 | LCS-QoS-Class | Enumerated | | +| 2524 | GERAN-Positioning-Info | Grouped | | +| 2525 | GERAN-Positioning-Data | OctetString | | +| 2526 | GERAN-GANSS-Positioning-Data | OctetString | | +| 2527 | UTRAN-Positioning-Info | Grouped | | +| 2528 | UTRAN-Positioning-Data | OctetString | | +| 2529 | UTRAN-GANSS-Positioning-Data | OctetString | | +| 2530 | LRR-Flags | Unsigned32 | | +| 2531 | LCS-Reference-Number | OctetString | | +| 2532 | Deferred-Location-Type | Unsigned32 | | +| 2533 | Area-Event-Info | Grouped | | +| 2534 | Area-Definition | Grouped | | +| 2535 | Area | Grouped | | +| 2536 | Area-Type | Unsigned32 | | +| 2537 | Area-Identification | Grouped | | +| 2538 | Occurrence-Info | Enumerated | | +| 2539 | Interval-Time | Unsigned32 | | +| 2540 | Periodic-LDR-Information | Grouped | | +| 2541 | Reporting-Amount | Unsigned32 | | +| 2542 | Reporting-Interval | Unsigned32 | | +| 2543 | Reporting-PLMN-List | Grouped | | +| 2544 | PLMN-ID-List | Grouped | | +| 2545 | PLR-Flags | Unsigned32 | | +| 2546 | PLA-Flags | Unsigned32 | | +| 2547 | Deferred-MT-LR-Data | Grouped | | +| 2548 | Termination-Cause | Unsigned32 | | +| 2549 | LRA-Flags | Unsigned32 | | +| 2550 | Periodic-Location-Support-Indicator | Enumerated | | +| 2551 | Prioritized-List-Indicator | Enumerated | | +| 2552 | ESMLC-Cell-Info | Grouped | | + +| | | | | +|-------------------------------------------------------------------|---------------------------------------|-------------|-------------| +| 2553 | Cell-Portion-ID | Unsigned32 | | +| 2554 | 1xRTT-RCID | OctetString | | +| 2555 | Delayed-Location-Reporting-Data | Grouped | | +| 2556 | Civic-Address | UTF8String | | +| 2557 | Barometric-Pressure | Unsigned32 | | +| 2558 | UTRAN-Additional-Positioning-Data | OctetString | | +| 2559 | Motion-Event-Info | Grouped | | +| 2560 | Linear-Distance | Unsigned32 | | +| 2561 | Maximum-Interval | Unsigned32 | | +| 2562 | Sampling-Interval | Unsigned32 | | +| 2563 | Reporting-Duration | Unsigned32 | | +| 2564 | Reporting-Location-Requirements | Unsigned32 | | +| 2565 | Additional-Area | Grouped | | +| 2566 | AMF-Instance-Id | UTF8String | | +| Note: The AVP codes from 2567 to 2599 are reserved for TS 29.172. | | | | +| 2600 | reserved | - | | +| 2601 | IMS-Application-Reference-Identifier | UTF8String | | +| 2602 | Low-Priority-Indicator | Enumerated | | +| 2603 | IP-Realm-Default-Indicator | Enumerated | 32.299 [5] | +| 2604 | Local-GW-Inserted-Indicator | Enumerated | | +| 2605 | Transcoder-Inserted-Indicator | Enumerated | | +| 2606 | PDP-Address-Prefix-Length | Unsigned32 | | +| Note: The AVP codes from 2607 to 2699 are reserved for TS 32.299. | | | | +| 2700 | Reserved | - | | +| 2701 | Transit-IOI-List | UTF8String | | +| 2702 | Status-AS-Code | Enumerated | | +| 2703 | NNI-Information | Grouped | | +| 2704 | NNI-Type | Enumerated | | +| 2705 | Neighbour-Node-Address | Address | | +| 2706 | Relationship-Mode | Enumerated | | +| 2707 | Session-Direction | Enumerated | | +| 2708 | From-Address | UTF8String | 32.299 [5] | +| 2709 | Access-Transfer-Information | Grouped | | +| 2710 | Access-Transfer-Type | Enumerated | | +| 2711 | Related-IMS-Charging-Identifier | UTF8String | | +| 2712 | Related-IMS-Charging-Identifier-Node | Address | | +| 2713 | IMS-Visited-Network-Identifier | UTF8String | | +| 2714 | TWAN-User-Location-Info | Grouped | | +| 2715 | Reserved | - | | +| 2716 | BSSID | UTF8String | | +| 2717 | TAD-Identifier | Enumerated | | +| Note: The AVP codes from 2718 to 2799 are reserved for TS 32.299. | | | | +| 2800 | Reserved | - | | +| 2801 | ADC-Revalidation-Time | Time | | +| 2802 | TDF-Application-Instance-Identifier | OctetString | | +| 2803 | HeNB-BBF-FQDN | UTF8String | | +| 2804 | HeNB-Local-IP-Address | Address | | +| 2805 | UE-Local-IP-Address | Address | | +| 2806 | UDP-Source-Port | Unsigned32 | | +| 2807 | CS-Service-QoS-Request-Identifier | OctetString | | +| 2808 | CS-Service-QoS-Request-Operation | Enumerated | | +| 2809 | Mute-Notification | Enumerated | | +| 2810 | Monitoring-Time | Time | | +| 2811 | AN-GW-Status | Enumerated | 29.212 [19] | +| 2812 | User-Location-Info-Time | Grouped | | +| 2813 | CS-Service-Resource-Report | Time | | +| 2814 | CS-Service-Resource-Failure-Cause | Enumerated | | +| 2815 | CS-Service-Resource-Result-Operation | Enumerated | | +| 2816 | Default-QoS-Information | Grouped | | +| 2817 | Default-QoS-Name | UTF8String | | +| 2818 | Conditional-APN-Aggregate-Max-Bitrate | Grouped | | +| 2819 | RAN-NAS-Release-Cause | OctetString | | +| 2820 | Presence-Reporting-Area-Elements-List | OctetString | | +| 2821 | Presence-Reporting-Area-Identifier | OctetString | | +| 2822 | Presence-Reporting-Area-Information | Grouped | | + +| | | | | +|-------------------------------------------------------------------|---------------------------------------|------------------|----------------| +| 2823 | Presence-Reporting-Area-Status | Unsigned32 | | +| 2824 | NetLoc-Access-Support | Unsigned32 | | +| 2825 | Fixed-User-Location-Info | Grouped | | +| 2826 | PCSCF-Restoration-Indication | Unsigned32 | | +| 2827 | IP-CAN-Session-Charging-Scope | Enumerated | | +| 2828 | Monitoring-Flags | Unsigned32 | | +| 2829 | Default-Access | Enumerated | | +| 2830 | NBIFOM-Mode | Enumerated | | +| 2831 | NBIFOM-Support | Enumerated | | +| 2832 | RAN-Rule-Support | Unsigned32 | | +| 2833 | Access-Availability-Change-Reason | Unsigned32 | | +| 2834 | Routing-Rule-Failure-Code | Unsigned32 | | +| 2835 | Routing-Rule-Report | Grouped | | +| 2836 | Traffic-Steering-Policy-Identifier-DL | OctetString | | +| 2837 | Traffic-Steering-Policy-Identifier-UL | OctetString | | +| 2838 | Request-Type | Unsigned32 | | +| 2839 | Execution-Time | Time | | +| 2840 | Conditional-Policy-Information | Grouped | | +| 2841 | Resource-Release-Notification | Enumerated | | +| 2842 | Removal-Of-Access | Enumerated | | +| 2843 | TCP-Source-Port | Unsigned32 | | +| 2844 | Default-Bearer-Indication | Enumerated | | +| 2845 | PRA-Install | Grouped | | +| 2846 | PRA-Remove | Grouped | | +| 2847 | 3GPP-PS-Data-Off-Status | Enumerated | | +| 2848 | Extended-APN-AMBR-DL | Unsigned32 | | +| 2849 | Extended-APN-AMBR-UL | Unsigned32 | | +| 2850 | Extended-GBR-DL | Unsigned32 | | +| 2851 | Extended-GBR-UL | Unsigned32 | | +| 2852 | Max-PLR-DL | Unsigned32 | | +| 2853 | Max-PLR-UL | Unsigned32 | | +| 2854 | UE-Status | Unsigned32 | | +| Note: The AVP codes from 2855 to 2899 are reserved for TS 29.212. | | | | +| 2900 | reserved | - | | +| 2901 | Policy-Counter-Identifier | Grouped | 29.219
[26] | +| 2902 | Policy-Counter-Status | UTF8String | | +| 2903 | Policy-Counter-Status-Report | Grouped | | +| 2904 | SL-Request-Type | Enumerated | | +| 2905 | Pending-Policy-Counter-Information | Grouped | | +| 2906 | Pending-Policy-Counter-Change-Time | Time | | +| 2907 | SN-Request-Type | Unsigned32 | | +| Note: The AVP codes from 2908 to 2999 are reserved for TS 29.219. | | | | +| 3000 | reserved | - | | +| 3001 | Device-Action | Grouped | 29.368
[27] | +| 3002 | Device-Notification | Grouped | | +| 3003 | Trigger-Data | Grouped | | +| 3004 | Payload | OctetString | | +| 3005 | Action-Type | Enumerated | | +| 3006 | Priority-Indication | Enumerated | | +| 3007 | Reference-Number | Unsigned32 | | +| 3008 | Request-Status | Enumerated | | +| 3009 | Delivery-Outcome | Enumerated | | +| 3010 | Application-Port-Identifier | Unsigned32 | | +| 3011 | Old-Reference-Number | Unsigned32 | | +| 3012 | Feature-Supported-In-Final-Target | Unsigned32 | | +| Note: The AVP codes from 3013 to 3099 are reserved for TS 29.368. | | | | +| 3100 | IP-SM-GW-Number | OctetString | 29.336
[28] | +| 3101 | IP-SM-GW-Name | DiameterIdentity | | +| 3102 | User-Identifier | Grouped | | +| 3103 | Service-ID | Enumerated | | +| 3104 | SCS-Identity | OctetString | | +| 3105 | Service-Parameters | Grouped | | +| 3106 | T4-Parameters | Grouped | | +| 3107 | Service-Data | Grouped | | +| 3108 | T4-Data | Grouped | | + +| | | | +|------|------------------------------------------|------------------| +| 3109 | HSS-Cause | Unsigned32 | +| 3110 | SIR-Flags | Unsigned32 | +| 3111 | External-Identifier | UTF8String | +| 3112 | IP-SM-GW-Realm | DiameterIdentity | +| 3113 | AESE-Communication-Pattern | Grouped | +| 3114 | Communication-Pattern-Set | Grouped | +| 3115 | Periodic-Communication-Indicator | Unsigned32 | +| 3116 | Communication-Duration-Time | Unsigned32 | +| 3117 | Periodic-Time | Unsigned32 | +| 3118 | Scheduled-Communication-Time | Grouped | +| 3119 | Stationary-Indication | Unsigned32 | +| 3120 | AESE-Communication-Pattern-Config-Status | Grouped | +| 3121 | AESE-Error-Report | Grouped | +| 3122 | Monitoring-Event-Configuration | Grouped | +| 3123 | Monitoring-Event-Report | Grouped | +| 3124 | SCEF-Reference-ID | Unsigned32 | +| 3125 | SCEF-ID | DiameterIdentity | +| 3126 | SCEF-Reference-ID-for-Deletion | Unsigned32 | +| 3127 | Monitoring-Type | Unsigned32 | +| 3128 | Maximum-Number-of-Reports | Unsigned32 | +| 3129 | UE-Reachability-Configuration | Grouped | +| 3130 | Monitoring-Duration | Time | +| 3131 | Maximum-Detection-Time | Unsigned32 | +| 3132 | Reachability-Type | Unsigned32 | +| 3133 | Maximum-Latency | Unsigned32 | +| 3134 | Maximum-Response-Time | Unsigned32 | +| 3135 | Location-Information-Configuration | Grouped | +| 3136 | MONTE-Location-Type | Unsigned32 | +| 3137 | Accuracy | Unsigned32 | +| 3138 | Association-Type | Unsigned32 | +| 3139 | Roaming-Information | Unsigned32 | +| 3140 | Reachability-Information | Unsigned32 | +| 3141 | IMEI-Change | Unsigned32 | +| 3142 | Monitoring-Event-Config-Status | Grouped | +| 3143 | Supported-Service | Grouped | +| 3144 | Supported-Monitoring-Event | Unsigned64 | +| 3145 | CIR-Flags | Unsigned32 | +| 3146 | Service-Result | Grouped | +| 3147 | Service-Result-Code | Unsigned32 | +| 3148 | Reference-ID-Validity-Time | Time | +| 3149 | Event-handling | Unsigned32 | +| 3150 | NIDD-Authorization-Request | Grouped | +| 3151 | NIDD-Authorization-Response | Grouped | +| 3152 | Service-Report | Grouped | +| 3153 | Node-Type | Unsigned32 | +| 3154 | S6t-HSS-Cause | Unsigned32 | +| 3155 | Enhanced-Coverage-Restriction | Grouped | +| 3156 | Enhanced-Coverage-Restriction-Data | Grouped | +| 3157 | Restricted-PLMN-List | Grouped | +| 3158 | Allowed-PLMN-List | Grouped | +| 3159 | Requested-Validity-Time | Time | +| 3160 | Granted-Validity-Time | Time | +| 3161 | NIDD-Authorization-Update | Grouped | +| 3162 | Loss-Of-Connectivity-Reason | Unsigned32 | +| 3163 | Group-Reporting-Guard-Timer | Unsigned32 | +| 3164 | CIA-Flags | Unsigned32 | +| 3165 | Group-Report | Grouped | +| 3166 | Group-Report-Item | Grouped | +| 3167 | RIR-Flags | Unsigned32 | +| 3168 | Type-Of-External-Identifier | Unsigned32 | +| 3169 | APN-Validity-Time | Grouped | +| 3170 | Suggested-Network-Configuration | Grouped | +| 3171 | Monitoring-Event-Report-Status | Grouped | +| 3172 | PLMN-ID-Requested | Enumerated | +| 3173 | AdditionalIdentifiers | Grouped | + +| | | | | +|-------------------------------------------------------------------|-------------------------------------------|------------------|----------------| +| 3174 | NIR-Flags | Unsigned32 | | +| 3175 | Reporting-Time-Stamp | Time | | +| 3176 | Group-User-Identifier | Grouped | | +| 3177 | NIA-Flags | Unsigned32 | | +| 3178 | MTC-Provider-Info | Grouped | | +| 3179 | MTC-Provider-ID | UTF8String | | +| 3180 | PDN-Connectivity-Status-Configuration | Grouped | | +| 3181 | PDN-Connectivity-Status-Report | Grouped | | +| 3182 | PDN-Connectivity-Status-Type | Unsigned32 | | +| 3183 | Traffic-Profile | Unsigned32 | | +| 3184 | Updated-Network-Configuration | Grouped | | +| 3185 | Battery-Indicator | Unsigned32 | | +| 3186 | SCEF-Reference-ID-Ext | Unsigned64 | | +| 3187 | SCEF-Reference-ID-for-Deletion-Ext | Unsigned64 | | +| 3188 | Exclude-Identifiers | Grouped | | +| 3189 | Include-Identifiers | Grouped | | +| Note: The AVP codes from 3190 to 3199 are reserved for TS 29.336. | | | | +| 3200 | SM-Delivery-Outcome-T4 | Enumerated | 29.337
[29] | +| 3201 | Absent-Subscriber-Diagnostic-T4 | Enumerated | | +| 3202 | Trigger-Action | Unsigned32 | | +| 3203 | MTC-Error-Diagnostic | Unsigned32 | | +| Note: The AVP codes from 3204 to 3299 are reserved for TS 29.337. | | | | +| 3300 | SC-Address | OctetString | 29.338
[30] | +| 3301 | SM-RP-UI | OctetString | | +| 3302 | TFR-Flags | Unsigned32 | | +| 3303 | SM-Delivery- Failure-Cause | Grouped | | +| 3304 | SM-Enumerated-Delivery-Failure-Cause | Enumerated | | +| 3305 | SM-Diagnostic-Info | OctetString | | +| 3306 | SM-Delivery-Timer | Unsigned32 | | +| 3307 | SM-Delivery-Start-Time | Time | | +| 3308 | SM-RP-MTI | Enumerated | | +| 3309 | SM-RP-SMEA | OctetString | | +| 3310 | SRR-Flags | Unsigned32 | | +| 3311 | SM-Delivery-Not-Intended | Enumerated | | +| 3312 | MWD-Status | Unsigned32 | | +| 3313 | MME-Absent-User-Subscriber-Diagnostic-SM | Unsigned32 | | +| 3314 | MSC-Absent-User-Subscriber-Diagnostic-SM | Unsigned32 | | +| 3315 | SGSN-Absent-User-Subscriber-Diagnostic SM | Unsigned32 | | +| 3316 | SM-Delivery-Outcome | Grouped | | +| 3317 | MME-SM-Delivery-Outcome | Grouped | | +| 3318 | MSC-SM-Delivery-Outcome | Grouped | | +| 3319 | SGSN-SM-Delivery-Outcome | Grouped | | +| 3320 | IP-SM-GW-SM-Delivery-Outcome | Grouped | | +| 3321 | SM-Delivery-Cause | Enumerated | | +| 3322 | Absent-User-Diagnostic-SM | Unsigned32 | | +| 3323 | RDR-Flags | Unsigned32 | | +| 3324 | SMSMI-Correlation-ID | Unsigned32 | | +| 3325 | HSS-ID | UTF8String | | +| 3326 | Originating-SIP-URI | UTF8String | | +| 3327 | Destination-SIP-URI | UTF8String | | +| 3328 | OFR-Flags | Unsigned32 | | +| 3329 | Maximum-UE-Availability-Time | Time | | +| 3330 | Maximum-Retransmission-Time | Time | | +| 3331 | Requested-Retransmission-Time | Time | | +| 3332 | SMS-GMSC-Address | OctetString | | +| 3333 | SMS-GMSC-Alert-Event | Unsigned32 | | +| 3334 | SMSF-3GPP-Absent-User-Diagnostic-SM | Unsigned32 | | +| 3335 | SMSF-Non-3GPP-Absent-User-Diagnostic-SM | Unsigned32 | | +| 3336 | SMSF-3GPP-SM-Delivery-Outcome | Grouped | | +| 3337 | SMSF-Non-3GPP-SM-Delivery-Outcome | Grouped | | +| 3338 | SMSF-3GPP-Number | OctetString | | +| 3339 | SMSF-Non-3GPP-Number | OctetString | | +| 3340 | SMSF-3GPP-Name | DiameterIdentity | | +| 3341 | SMSF-Non-3GPP-Name | DiameterIdentity | | +| 3342 | SMSF-3GPP-Realm | DiameterIdentity | | + +| | | | | +|-------------------------------------------------------------------|--------------------------------------------------------|------------------|------------| +| 3343 | SMSF-Non-3GPP-Realm | DiameterIdentity | | +| 3344 | SMSF-3GPP-Address | Grouped | | +| 3345 | SMSF-Non-3GPP-Address | Grouped | | +| 3346 | SMSF-3GPP-SBI-Support-Indicator | Enumerated | | +| 3347 | SMSF-Non-3GPP-SBI-Support-Indicator | Enumerated | | +| 3348 | IP-SM-GW-SBI-Support-Indicator | Enumerated | | +| Note: The AVP codes from 3349 to 3399 are reserved for TS 29.338. | | | | +| 3400 | reserved | - | | +| 3401 | Reason-Header | UTF8String | | +| 3402 | Instance-Id | UTF8String | | +| 3403 | Route-Header-Received | UTF8String | | +| 3404 | Route-Header-Transmitted | UTF8String | | +| 3405 | SM-Device-Trigger-Information | Grouped | | +| 3406 | MTC-IWF-Address | Address | | +| 3407 | SM-Device-Trigger-Indicator | Enumerated | | +| 3408 | SM-Sequence-Number | Unsigned32 | | +| 3409 | SMS-Result | Unsigned32 | | +| 3410 | VCS-Information | Grouped | | +| 3411 | Basic-Service-Code | Grouped | | +| 3412 | Bearer-Capability | OctetString | | +| 3413 | Teleservice | OctetString | | +| 3414 | ISUP-Location-Number | OctetString | | +| 3415 | Forwarding-Pending | Enumerated | | +| 3416 | ISUP-Release-Cause | Unsigned32 | | +| 3417 | MSC-Address | OctetString | | +| 3418 | Network-Call-Reference-Number | OctetString | | +| 3419 | Start-of-Charging | Time | | +| 3420 | VLR-Number | OctetString | | +| 3421 | CN-Operator-Selection-Entity | Enumerated | | +| 3422 | ISUP-Cause-Diagnostics | OctetString | | +| 3423 | ISUP-Cause-Location | Unsigned32 | | +| 3424 | ISUP-Cause-Value | Unsigned32 | | +| 3425 | EPDG-Address | Address | | +| 3426 | Announcing-UE-HPLMN-Identifier | UTF8String | | +| 3427 | Announcing-UE-VPLMN-Identifier | UTF8String | | +| 3428 | Coverage-Status | Enumerated | | +| 3429 | Layer-2-Group-ID | OctetString | 32.299 [5] | +| 3430 | Monitored-PLMN-Identifier | UTF8String | | +| 3431 | Monitoring-UE-HPLMN-Identifier | UTF8String | | +| 3432 | Monitoring-UE-Identifier | UTF8String | | +| 3433 | Monitoring-UE-VPLMN-Identifier | UTF8String | | +| 3434 | ProSe-PC3-Control-Protocol-Cause | Integer32 | | +| 3435 | ProSe-PC3-EPC-Control-Protocol-Cause | Integer32 | | +| 3436 | Requested-PLMN-Identifier | UTF8String | | +| 3437 | Requestor-PLMN-Identifier | UTF8String | | +| 3438 | Role-Of-ProSe-Function | Enumerated | | +| 3439 | Usage-Information-Report-Sequence-Number | Integer32 | | +| 3440 | ProSe-3rd-Party-Application-ID | UTF8String | | +| 3441 | ProSe-Direct-Communication-Transmission-Data-Container | Grouped | | +| 3442 | ProSe-Direct-Discovery-Model | Enumerated | | +| 3443 | ProSe-Event-Type | Enumerated | | +| 3444 | ProSe-Function-IP-Address | Address | | +| 3445 | ProSe-Functionality | Enumerated | | +| 3446 | ProSe-Group-IP-Multicast-Addresses | Address | | +| 3447 | ProSe-Information | Grouped | | +| 3448 | ProSe-Range-Class | Enumerated | | +| 3449 | ProSe-Reason-For-Cancellation | Enumerated | | +| 3450 | ProSe-Request-Timestamp | Time | | +| 3451 | ProSe-Role-Of-UE | Enumerated | | +| 3452 | ProSe-Source-IP-Address | Address | | +| 3453 | ProSe-UE-ID | OctetString | | +| 3454 | Proximity-Alert-Indication | Enumerated | | +| 3455 | Proximity-Alert-Timestamp | Time | | +| 3456 | Proximity-Cancellation-Timestamp | Time | | +| 3457 | ProSe-Function-PLMN-Identifier | UTF8String | | + +| | | | | +|-------------------------------------------------------------------|-----------------------------------------------------|-------------|-------------| +| 3458 | Application-Specific-Data | OctetString | | +| 3459 | Coverage-Info | Grouped | | +| 3460 | Location-Info | Grouped | | +| 3461 | ProSe-Direct-Communication-Reception-Data-Container | Grouped | | +| 3462 | Radio-Frequency | OctetString | | +| 3463 | Radio-Parameter-Set-Info | Grouped | | +| 3464 | Radio-Parameter-Set-Values | OctetString | | +| 3465 | Radio-Resources-Indicator | Integer32 | | +| 3466 | Time-First-Reception | Time | | +| 3467 | Time-First-Transmission | Time | | +| 3468 | Transmitter-Info | Grouped | | +| Note: The AVP codes from 3469 to 3499 are reserved for TS 32.299. | | | | +| 3500 | BMSC-Address | Address | | +| 3501 | BMSC-Port | Unsigned32 | | +| 3502 | MBMS-Bearer-Event | Unsigned32 | | +| 3503 | MBMS-Bearer-Event-Notification | Grouped | | +| 3504 | MBMS-Bearer-Request | Grouped | | +| 3505 | MBMS-Bearer-Response | Grouped | | +| 3506 | MBMS-Bearer-Result | Unsigned32 | | +| 3507 | MBMS-Start-Time | Time | | +| 3508 | Radio-Frequency | Unsigned32 | | +| 3509 | TMGI-Allocation-Request | Grouped | | +| 3510 | TMGI-Allocation-Response | Grouped | | +| 3511 | TMGI-Allocation-Result | Unsigned32 | | +| 3512 | TMGI-Deallocation-Request | Grouped | | +| 3513 | TMGI-Deallocation-Response | Grouped | | +| 3514 | TMGI-Deallocation-Result | Unsigned32 | | +| 3515 | TMGI-Expiry | Grouped | | +| 3516 | TMGI-Number | Unsigned32 | | +| 3517 | MB2U-Security | Unsigned32 | | +| 3518 | Local-M1-Information | Grouped | | +| 3519 | Local-MB2-U-Information | Grouped | | +| 3520 | MBMS-eNB-IP-Multicast-Address | Address | | +| 3521 | MBMS-eNB-IPv6-Multicast-Address | Address | | +| 3522 | MBMS-GW-SSM-IP-Address | Address | | +| 3523 | MBMS-GW-SSM-IPv6-Address | Address | | +| 3524 | Common-Tunnel-Endpoint-Identifier | OctetString | | +| 3525 | FEC-Request | OctetString | | +| 3526 | ROHC-Request | Grouped | | +| 3527 | ROHC-Full-Header-Periodicity | Float32 | | +| 3528 | ROHC-Profile | Unsigned32 | | +| 3529 | Userplane-Protocol-Result | Grouped | | +| 3530 | ROHC-Result | Unsigned32 | | +| 3531 | FEC-Result | Unsigned32 | | +| 3532 | ROHC-Max-CID | Unsigned32 | | +| 3533 | MBMS-Bearer-Event-Diagnostic-Info | Unsigned32 | 29.468 [31] | +| Note: The AVP codes from 3534 to 3599 are reserved for TS 29.468. | | | | +| 3600 | Origin-App-Layer-User-Id | UTF8String | | +| 3601 | Target-App-Layer-User-Id | UTF8String | | +| 3602 | ProSe-Function-ID | OctetString | | +| 3603 | ProSe-Request-Type | Unsigned32 | | +| 3604 | PDUID | OctetString | | +| 3605 | Application-Data | UTF8String | | +| 3606 | Allowed-Suffixes-Number | Unsigned32 | | +| 3607 | Monitor-Target | Grouped | | +| 3608 | ProSe-Code-Suffix-Mask | Grouped | | +| 3609 | Suffix-Code | OctetString | | +| 3610 | Suffix-Mask | OctetString | | +| 3611 | Banned-User-Target | Grouped | | +| 3612 | Metadata-Indicator | Unsigned32 | 29.343 [32] | +| Note: The AVP codes from 3613 to 3699 are reserved for TS 29.343. | | | | +| 3701 | ProSe-Subscription-Data | Grouped | | +| 3702 | ProSe-Permission | Unsigned32 | | +| 3703 | ProSe-Allowed-PLMN | Grouped | | +| 3704 | ProSe-Direct-Allowed | Unsigned32 | 29.344 [33] | + +| | | | | +|-------------------------------------------------------------------|------------------------------------|-------------|--| +| 3705 | UPR-Flags | Unsigned32 | | +| 3706 | PNR-Flags | Unsigned32 | | +| 3707 | ProSe-Initial-Location-Information | Grouped | | +| 3708 | Authorized-Discovery-Range | Unsigned32 | | +| Note: The AVP codes from 3709 to 3799 are reserved for TS 29.344. | | | | +| 3800 | Reserved | | | +| 3801 | App-Layer-User-Id | UTF8String | | +| 3802 | Assistance-info | Grouped | | +| 3803 | Assistance-Info-Validity-Timer | Unsigned32 | | +| 3804 | Discovery-Type | Unsigned32 | | +| 3805 | Filter-Id | OctetString | | +| 3806 | MAC-Address | UTF8String | | +| 3807 | Match-Report | Grouped | | +| 3808 | Operating-Channel | Unsigned32 | | +| 3809 | P2P-Features | Unsigned32 | | +| 3810 | ProSe-App-Code | UTF8String | | +| 3811 | ProSe-App-Id | UTF8String | | +| 3812 | ProSe-App-Mask | UTF8String | | +| 3813 | ProSe-Discovery-Filter | Grouped | | +| 3814 | PRR-Flags | Unsigned32 | | +| 3815 | ProSe-Validity-Timer | Unsigned32 | | +| 3816 | Requesting-EPUID | UTF8String | | +| 3817 | Targeted-EPUID | UTF8String | | +| 3818 | Time-Window | Unsigned32 | | +| 3819 | WiFi-P2P-Assistance-Info | Grouped | | +| 3820 | WLAN-Assistance-Info | Grouped | | +| 3821 | WLAN-Link-Layer-Id | OctetString | | +| 3822 | WLAN-Link-Layer-Id-List | Grouped | | +| 3823 | Location-Update-Trigger | Grouped | | +| 3824 | Location-Update-Event-Type | Unsigned32 | | +| 3825 | Change-Of-Area-Type | Grouped | | +| 3826 | Location-Update-Event-Trigger | Unsigned32 | | +| 3827 | Report-Cardinality | Enumerated | | +| 3828 | Minimum-Interval-Time | Unsigned32 | | +| 3829 | Periodic-Location-Type | Grouped | | +| 3830 | Location-Report-Interval-Time | Unsigned32 | | +| 3831 | Total-Number-Of-Reports | Unsigned32 | | +| 3832 | Validity-Time-Announce | Unsigned32 | | +| 3833 | Validity-Time-Monitor | Unsigned32 | | +| 3834 | Validity-Time-Communication | Unsigned32 | | +| 3835 | ProSe-App-Code-Info | Grouped | | +| 3836 | MIC | OctetString | | +| 3837 | UTC-based-Counter | Unsigned32 | | +| 3838 | ProSe-Match-Refresh-Timer | Unsigned32 | | +| 3839 | ProSe-Metadata-Index-Mask | OctetString | | +| 3840 | App-Identifier | Grouped | | +| 3841 | OS-ID | OctetString | | +| 3842 | OS-App-ID | UTF8String | | +| 3843 | Requesting-RPAUID | UTF8String | | +| 3844 | Target-RPAUID | UTF8String | | +| 3845 | Target-PDUID | OctetString | | +| 3846 | ProSe-Restricted-Code | OctetString | | +| 3847 | ProSe-Restricted-Code-Suffix-Range | OctetString | | +| 3848 | Beginning-Suffix | OctetString | | +| 3849 | Ending-Suffix | OctetString | | +| 3850 | Discovery-Entry-ID | Unsigned32 | | +| 3851 | Match-Timestamp | Time | | +| 3852 | PMR-Flags | Unsigned32 | | +| 3853 | ProSe-Application-Metadata | UTF8String | | +| 3854 | Discovery-Auth-Request | Grouped | | +| 3855 | Discovery-Auth-Response | Grouped | | +| 3856 | Match-Request | Grouped | | +| 3857 | Match-Report-Info | Grouped | | +| 3858 | Banned-RPAUID | UTF8String | | +| 3859 | Banned-PDUID | OctetString | | + +29.345 +[34] + +| | | | | +|-------------------------------------------------------------------|-----------------------------------------|------------------|-------------| +| 3860 | Code-Receiving-Security-Material | Grouped | | +| 3861 | Code-Sending-Security-Material | Grouped | | +| 3862 | DUSK | OctetString | | +| 3863 | DUIK | OctetString | | +| 3864 | DUCK | OctetString | | +| 3865 | MIC-Check-indicator | Unsigned32 | | +| 3866 | Encrypted-Bitmask | OctetString | | +| 3867 | ProSe-App-Code-Suffix-Range | OctetString | | +| 3868 | PC5-tech | OctetString | | +| Note: The AVP codes from 3869 to 3899 are reserved for TS 29.345. | | | | +| 3900 | Reserved | | | +| 3901 | Enhanced-Diagnostics | Grouped | | +| 3902 | Inter-UE-Transfer | Enumerated | | +| 3903 | TWAG-Address | Address | | +| 3904 | Announcement-Information | Grouped | | +| 3905 | Announcement-Identifier | Unsigned32 | | +| 3906 | Announcement-Order | Unsigned32 | | +| 3907 | Variable-Part | Grouped | | +| 3908 | Variable-Part-Order | Unsigned32 | | +| 3909 | Variable-Part-Type | Unsigned32 | | +| 3910 | Variable-Part-Value | UTF8String | | +| 3911 | Time-Indicator | Unsigned32 | | +| 3912 | Quota-Indicator | Enumerated | | +| 3913 | Play-Alternative | Enumerated | | +| 3914 | Language | UTF8String | | +| 3915 | Privacy-Indicator | Enumerated | | +| 3916 | Called-Identity | UTF8String | | +| 3917 | Called-Identity-Change | Grouped | | +| 3918 | UWAN-User-Location-Info | Grouped | | +| 3919 | Monitoring-Event-Configuration-Activity | Integer32 | | +| 3920 | Monitoring-Event-Report-Data | Grouped | | +| 3921 | Monitoring-Event-Information | Grouped | 32.299 [5] | +| 3922 | Monitoring-Event-Functionality | Integer32 | | +| 3923 | Monitoring-Event-Report-Number | Unsigned32 | | +| 3924 | Cellular-Network-Information | OctetString | | +| 3925 | Related-Change-Condition-Information | Grouped | | +| 3926 | Related-Trigger | Grouped | | +| 3927 | CPDT-Information | Grouped | | +| 3928 | NIDD-Submission | Grouped | | +| 3929 | Serving-Node-Identity | DiameterIdentity | | +| 3930 | CP-CIoT-EPS-Optimisation-Indicator | Enumerated | | +| 3931 | SGi-PtP-Tunnelling-Method | Enumerated | | +| 3932 | UNI-PDU-CP-Only-Flag | Enumerated | | +| 3933 | APN-Rate-Control | Grouped | | +| 3934 | APN-Rate-Control-Downlink | Grouped | | +| 3935 | APN-Rate-Control-Uplink | Grouped | | +| 3936 | Additional-Exception-Reports | Enumerated | | +| 3937 | Rate-Control-Max-Message-Size | Unsigned32 | | +| 3938 | Rate-Control-Max-Rate | Unsigned32 | | +| 3939 | Rate-Control-Time-Unit | Unsigned32 | | +| 3940 | SCS-AS-Address | Grouped | | +| 3941 | SCS-Address | Address | | +| 3942 | SCS-Realm | DiameterIdentity | | +| Note: The AVP codes from 3943 to 3999 are reserved for TS 32.299. | | | | +| 4000 | Aggregated-Congestion-Info | Grouped | | +| 4001 | Aggregated-RUCI-Report | Grouped | | +| 4002 | Congestion-Level-Definition | Grouped | | +| 4003 | Congestion-Level-Range | Unsigned32 | | +| 4004 | Congestion-Level-Set-Id | Unsigned32 | | +| 4005 | Congestion-Level-Value | Unsigned32 | | +| 4006 | Congestion-Location-Id | Grouped | | +| 4007 | Conditional-Restriction | Unsigned32 | | +| 4008 | eNodeB-Id | OctetString | | +| 4009 | IMSI-List | OctetString | | +| 4010 | RCAF-Id | DiameterIdentity | 29.217 [35] | + +| | | | | +|-------------------------------------------------------------------|-----------------------------------------|-------------|----------------| +| 4011 | Reporting-Restriction | Unsigned32 | | +| 4012 | RUCI-Action | Unsigned32 | | +| 4013 | Extended-eNodeB-ID | OctetString | | +| Note: The AVP codes from 4014 to 4099 are reserved for TS 29.217. | | | | +| 4101 | Network-Congestion-Area-Report | Grouped | 29.153
[37] | +| 4102 | Ns-Request-Type | Unsigned32 | | +| Note: The AVP codes from 4103 to 4199 are reserved for TS 29.153. | | | | +| 4201 | Network-Area-Info-List | OctetString | 29.154
[38] | +| 4202 | Reference-Id | OctetString | | +| 4203 | Transfer-Request-Type | Unsigned32 | | +| 4204 | Time-Window | Grouped | | +| 4205 | Transfer-End-Time | Time | | +| 4206 | Transfer-Start-Time | Time | | +| 4207 | Transfer-Policy | Grouped | | +| 4208 | Transfer-Policy-Id | Unsigned32 | | +| 4209 | Number-Of-UEs | Unsigned32 | | +| 4210 | Access-Network-Reports | Grouped | | +| 4211 | Event-Configuration | Grouped | | +| 4212 | Event-Configuration-State | Unsigned32 | | +| 4213 | Event-Configuration-Status | Grouped | | +| 4214 | Event-Reporting-Results | Unsigned32 | | +| 4215 | Event-Reports | Grouped | | +| 4216 | Extended-SCEF-Reference-ID | Unsigned64 | | +| Note: The AVP codes from 4217 to 4299 are reserved for TS 29.154. | | | | +| 4300 | Communication-Failure-Information | Grouped | 29.128
[36] | +| 4301 | Cause-Type | Unsigned32 | | +| 4302 | S1AP-Cause | Unsigned32 | | +| 4303 | RANAP-Cause | Unsigned32 | | +| 4304 | GMM-Cause | Unsigned32 | | +| 4305 | SM-Cause | Unsigned32 | | +| 4306 | Number-of-UE-Per-Location-Configuration | Grouped | | +| 4307 | Number-of-UE-Per-Location-Report | Grouped | | +| 4308 | UE-Count | Unsigned32 | | +| 4309 | BSSGP-Cause | Unsigned32 | | +| 4310 | Serving-PLMN-Rate-Control | Grouped | | +| 4311 | Uplink-Rate-Limit | Unsigned32 | | +| 4312 | Downlink-Rate-Limit | Unsigned32 | | +| 4313 | Extended-PCO | OctetString | | +| 4314 | Connection-Action | Unsigned32 | | +| 4315 | Non-IP-Data | OctetString | | +| 4316 | SCEF-Wait-Time | Time | | +| 4317 | CMR-Flags | Unsigned32 | | +| 4318 | RRC-Cause-Counter | Grouped | | +| 4319 | Counter-Value | Unsigned32 | | +| 4320 | RRC-Counter-Timestamp | Time | | +| 4321 | TDA-Flags | Unsigned32 | | +| 4322 | Idle-Status-Indication | Grouped | | +| 4323 | Idle-Status-Timestamp | Time | | +| 4324 | Active-Time | Unsigned32 | | +| 4325 | Reachability-Cause | Unsigned32 | | +| 4326 | APN-Rate-Control-Status | Grouped | | +| 4327 | Uplink-Number-Of-Packets-Allowed | Unsigned32 | | +| 4328 | Number-Of-Additional-Exception-Reports | Unsigned32 | | +| 4329 | Downlink-Number-Of-Packets-Allowed | Unsigned32 | | +| 4330 | APN-Rate-Control-Status-Validity-Time | Unsigned64 | | +| Note: The AVP codes from 4331 to 4399 are reserved for TS 29.128. | | | | +| 4400 | Charging-Per-IP-CAN-Session-Indicator | Enumerated | 32.299 [5] | +| 4401 | Access-Network-Info-Change | Enumerated | | +| 4402 | Discoveree-UE-HPLMN-Identifier | UTF8String | | +| 4403 | Discoveree-UE-VPLMN-Identifier | UTF8String | | +| 4404 | Discoverer-UE-HPLMN-Identifier | UTF8String | | +| 4405 | Discoverer-UE-VPLMN-Identifier | UTF8String | | +| 4406 | 3GPP-PS-Data-Off-Status | Enumerated | | +| 4407 | Unused-Quota-Timer | Unsigned32 | | +| 4408 | Announcing-PLMN-ID | UTF8String | | + +| | | | | +|--------------------------------------------------------------------------|---------------------------------|-------------|----------------| +| 4409 | ProSe-UE-to-Network-Relay-UE-ID | OctetString | | +| 4410 | ProSe-Target-Layer-2-ID | OctetString | | +| 4411 | Relay-IP-address | Address | | +| 4412 | Target-IP-Address | Address | | +| 4413 | FE-Identifier-List | UTF8String | | +| Note: The AVP codes from 4414 to 4499 are reserved for TS 32.299 | | | | +| 4500 | MCPTT-ID | UTF8String | | +| 4501 | Data-Identification | Grouped | | +| 4502 | Data-Identification-Prefix | Unsigned32 | | +| 4503 | Data-Identification-Flags | Unsigned64 | | +| 4504 | DPR-Flags | Unsigned32 | | +| 4505 | DPA-Flags | Unsigned32 | | +| 4506 | DUR-Flags | Unsigned32 | | +| 4507 | DUA-Flags | Unsigned32 | | +| 4508 | NDR-Flags | Unsigned32 | | +| 4509 | NDA-Flags | Unsigned32 | | +| 4510 | User-Data-Id | Unsigned32 | | +| 4511 | MC-Service-User-Profile-Data | Grouped | | +| 4512 | Sequence-Number | Unsigned32 | | +| 4513 | MCVideo-ID | UTF8String | | +| 4514 | MC-Data-ID | UTF8String | | +| Note: The AVP codes from 4515 to 4599 are reserved for TS 29.283. | | | | +| 4600 | V2X-PC5-Allowed-PLMN | Grouped | | +| 4601 | V2X-Update-Flags | Unsigned32 | | +| 4602 | V2X-Notify-Flags | Unsigned32 | | +| 4603 | PLMN-Allowed-PC5-RATs | Grouped | | +| 4604 | PC5-RAT-Type | Enumerated | | +| Note: The AVP codes from 4605 to 4799 are reserved for TS 29.388. | | | | +| 4700 | V2X-Authorization-Data | Grouped | | +| 4701 | V2X-Permission-in-VPLMN | Unsigned32 | | +| 4702 | V2X-Application-Server | Grouped | | +| Note: The AVP codes from 4703 to 4799 are reserved for TS and TS 29.389. | | | | +| | | | 29.561
[42] | +| Note: The AVP codes from 4800 to 4999 are reserved for TS and TS 29.561. | | | | + +# 8 Experimental result codes + +The Diameter answer messages must carry either Result-Code AVP or Experimental-Result AVP. The values of Result-Code AVP are controlled by IANA. The Experimental-Result AVP is a grouped AVP containing the Vendor-Id AVP and Experimental-Result-Code AVP, thus the experimental result codes are controlled in a vendor-specific manner. + +## 8.1 3GPP specific result codes + +The 3GPP specific result codes are always transferred in the Experimental-Result AVP, which has the Vendor-Id with value of 3GPP's vendor identifier. The 3GPP specific result codes shall follow the same classification as defined for the values of Result-Code AVP in IETF RFC 3588 [9]. That means, the result codes are grouped to following ranges: + +- 1xxx (Informational) +- 2xxx (Success) +- 4xxx (Transient Failures) +- 5xxx (Permanent Failures) + +### 8.1.1 Informational + +The Informational result codes shall use the values from 1001 to 1999 in the Experimental-Result-Code AVP. + +Editor's note: No informational result codes have been yet defined in 3GPP. + +### 8.1.2 Success + +The Success result codes shall use the values from 2001 to 2999 in the Experimental-Result-Code AVP. The reserved 3GPP specific Success result codes are presented in the following table. + +**Table 8.1.2: 3GPP specific Success result codes** + +| Experimental Result Code | Result text | Specified in the TS | +|---------------------------------------------------------------------------------------|------------------------------------------|---------------------| +| 2001 | DIAMETER_FIRST_REGISTRATION | 29.229 [2] | +| 2002 | DIAMETER_SUBSEQUENT_REGISTRATION | | +| 2003 | DIAMETER_UNREGISTERED_SERVICE | | +| 2004 | DIAMETER_SUCCESS_SERVER_NAME_NOT_STORED | | +| 2005 | Deprecated value | | +| Note: The Experimental Result Codes from 2006 to 2020 are reserved for the TS 29.229. | | | +| 2021 | DIAMETER_PDP_CONTEXT_DELETION_INDICATION | 29.061 [13] | +| Note: The Experimental Result Codes from 2022 to 2040 are reserved for the TS 29.061 | | | +| | | 29.109 [7] | +| Note: The Experimental Result Codes from 2401 to 2420 are reserved for the TS 29.109. | | | +| 2421 | DIAMETER_QOS_FLOW_DELETION_INDICATION | 29.561 [42] | +| Note: The Experimental Result Codes from 2422 to 2440 are reserved for the TS 29.561. | | | + +### 8.1.3 Transient Failures + +The Transient Failure result codes shall use the values from 4001 to 4999 in the Experimental-Result-Code AVP. The reserved 3GPP specific Transient Failure result codes are presented in the following table. + +Table 8.1.3: 3GPP specific Transient Failure result codes + +| Experimental Result Code | Result text | Specified in the TS | +|---------------------------------------------------------------------------------------|-----------------------------------------------|---------------------| +| 4100 | DIAMETER_USER_DATA_NOT_AVAILABLE | 29.329 [4] | +| 4101 | DIAMETER_PRIOR_UPDATE_IN_PROGRESS | | +| Note: The Experimental Result Codes from 4102 to 4120 are reserved for the TS 29.329. | | | +| 4121 | DIAMETER_ERROR_OUT_OF_RESOURCES | 29.061 [13] | +| Note: The Experimental Result Codes from 4122 to 4140 are reserved for the TS 29.061. | | | +| 4141 | DIAMETER_PCC_BEARER_EVENT | 29.212 [19] | +| 4142 | DIAMETER_BEARER_EVENT | | +| 4143 | DIAMETER_AN_GW_FAILED | | +| 4144 | DIAMETER_PENDING_TRANSACTION | | +| 4145 | DIAMETER_UE_STATUS_SUSPEND | | +| Note: The Experimental Result Codes from 4146 to 4160 are reserved for the TS 29.212 | | | +| | | 32.299 [5] | +| Note: The Experimental Result Codes from 4161 to 4180 are reserved for the TS 32.299. | | | +| 4181 | DIAMETER_AUTHENTICATION_DATA_UNAVAILABLE | 29.272 [21] | +| 4182 | DIAMETER_ERROR_CAMEL_SUBSCRIPTION_PRESENT | | +| Note: The Experimental Result Codes from 4182 to 4200 are reserved for the TS 29.272. | | | +| 4201 | DIAMETER_ERROR_ABSENT_USER | 29.173 [25] | +| Note: The Experimental Result Codes from 4202 to 4220 are reserved for the TS 29.173. | | | +| 4221 | DIAMETER_ERROR_UNREACHABLE_USER | 29.172 [24] | +| 4222 | DIAMETER_ERROR_SUSPENDED_USER | | +| 4223 | DIAMETER_ERROR_DETACHED_USER | | +| 4224 | DIAMETER_ERROR_POSITIONING_DENIED | | +| 4225 | DIAMETER_ERROR_POSITIONING_FAILED | | +| 4226 | DIAMETER_ERROR_UNKNOWN_UNREACHABLE_LCS_CLIENT | | +| Note: The Experimental Result Codes from 4227 to 4240 are reserved for the TS 29.172. | | | +| 4241 | DIAMETER_ERROR_NO_AVAILABLE_POLICY_COUNTERS | 29.219 [26] | +| Note: The Experimental Result Codes from 4242 to 4260 are reserved for the TS 29.219. | | | +| 4261 | REQUESTED_SERVICE_TEMPORARILY_NOT_AUTHORIZED | 29.214 [18] | +| Note: The Experimental Result Codes from 4262 to 4280 are reserved for the TS 29.214. | | | + +### 8.1.4 Permanent Failures + +The Permanent Failure result codes shall use the values from 5001 to 5999 in the Experimental-Result-Code AVP. The reserved 3GPP specific Permanent Failure result codes are presented in the following table. + +Table 8.1.4: 3GPP specific Permanent Failure result codes + +| Experimental Result Code | Result text | Specified in the TS | +|------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|--------------------------------------------| +| 5001 | DIAMETER_ERROR_USER_UNKNOWN | 29.229 [2] | +| 5002 | DIAMETER_ERROR_IDENTITIES_DONT_MATCH | | +| 5003 | DIAMETER_ERROR_IDENTITY_NOT_REGISTERED | | +| 5004 | DIAMETER_ERROR_ROAMING_NOT_ALLOWED | | +| 5005 | DIAMETER_ERROR_IDENTITY_ALREADY_REGISTERED | | +| 5006 | DIAMETER_ERROR_AUTH_SCHEME_NOT_SUPPORTED | | +| 5007 | DIAMETER_ERROR_IN_ASSIGNMENT_TYPE | | +| 5008 | DIAMETER_ERROR_TOO_MUCH_DATA | | +| 5009 | DIAMETER_ERROR_NOT_SUPPORTED_USER_DATA | | +| 5010 | unassigned | | +| 5011 | DIAMETER_ERROR_FEATURE_UNSUPPORTED | | +| 5012 | DIAMETER_ERROR_SERVING_NODE_FEATURE_UNSUP
PORTED | | +| Note: The Experimental Result Codes from 5013 to 5020 are reserved for the TS 29.229. | | 32.299 [5] | +| Note: The Experimental Result Codes from 5021 to 5040 are reserved for the TS 32.299. | | | +| 5041 | DIAMETER_ERROR_USER_NO_WLAN_SUBSCRIPTION | 29.234 [6] | +| 5042 | DIAMETER_ERROR_W-APN_UNUSED_BY_USER | | +| 5043 | DIAMETER_ERROR_NO_ACCESS_INDEPENDENT_SUBS
CRIPTION | | +| 5044 | DIAMETER_ERROR_USER_NO_W-APN_SUBSCRIPTION | | +| 5045 | DIAMETER_ERROR_UNSUITABLE_NETWORK | | +| Note: The Experimental Result Codes from 5046 to 5060 are reserved for the TS 29.234. | | | +| 5061 | INVALID_SERVICE_INFORMATION | 29.209 [8],
29.211 [17],
29.214 [18] | +| 5062 | FILTER_RESTRICTIONS | | +| 5063 | REQUESTED_SERVICE_NOT_AUTHORIZED | | +| 5064 | DUPLICATED_AF_SESSION | | +| 5065 | IP-CAN_SESSION_NOT_AVAILABLE | | +| 5066 | UNAUTHORIZED_NON_EMERGENCY_SESSION | | +| 5067 | UNAUTHORIZED_SPONSORED_DATA_CONNECTIVITY | | +| 5068 | TEMPORARY_NETWORK_FAILURE | | +| Note: The Experimental Result Codes from 5069 to 5080 are reserved for TS 29.209, TS 29.211 and TS 29.214. | | | +| 5100 | DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED | 29.329 [4] | +| 5101 | DIAMETER_ERROR_OPERATION_NOT_ALLOWED | | +| 5102 | DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ | | +| 5103 | DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIE
D | | +| 5104 | DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIE
D | | +| 5105 | DIAMETER_ERROR_TRANSPARENT_DATA
OUT_OF_SYNC | | +| 5106 | DIAMETER_ERROR_SUBS_DATA_ABSENT | | +| 5107 | DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA | | +| 5108 | DIAMETER_ERROR_DSAI_NOT_AVAILABLE | | +| Note: The Experimental Result Codes from 5109 to 5119 are reserved for the TS 29.329. | | | +| 5120 | DIAMETER_ERROR_START_INDICATION | 29.061 [13] | +| 5121 | DIAMETER_ERROR_STOP_INDICATION | | +| 5122 | DIAMETER_ERROR_UNKNOWN_MBMS_BEARER_SERVI
CE | | +| 5123 | DIAMETER_ERROR_SERVICE_AREA | | +| Note: The Experimental Result Codes from 5124 to 5139 are reserved for the TS 29.061. | | | +| 5140 | DIAMETER_ERROR_INITIAL_PARAMETERS | 29.212 [19] | +| 5141 | DIAMETER_ERROR_TRIGGER_EVENT | | +| 5142 | DIAMETER_PCC_RULE_EVENT | | +| 5143 | DIAMETER_ERROR_BEARER_NOT_AUTHORIZED | | +| 5144 | DIAMETER_ERROR_TRAFFIC_MAPPING_INFO_REJECTE
D | | +| 5145 | DIAMETER_QOS_RULE_EVENT | | +| 5146 | reserved | | +| 5147 | DIAMETER_ERROR_CONFLICTING_REQUEST | | +| 5148 | DIAMETER_ADC_RULE_EVENT | | + +| | | | +|---------------------------------------------------------------------------------------|-----------------------------------------------------------|-------------| +| 5149 | DIAMETER_ERROR_NBIFOM_NOT_AUTHORIZED | | +| Note: The Experimental Result Codes from 5150 to 5159 are reserved for the TS 29.212. | | | +| 5401 | DIAMETER_ERROR_IMPI_UNKNOWN | 29.109 [7] | +| 5402 | DIAMETER_ERROR_NOT_AUTHORIZED | | +| 5403 | DIAMETER_ERROR_TRANSACTION_IDENTIFIER_INVALID | | +| Note: The Experimental Result Codes from 5404 to 5419 are reserved for the TS 29.109. | | | +| 5420 | DIAMETER_ERROR_UNKNOWN_EPS_SUBSCRIPTION | 29.272 [21] | +| 5421 | DIAMETER_ERROR_RAT_NOT_ALLOWED | | +| 5422 | DIAMETER_ERROR_EQUIPMENT_UNKNOWN | | +| 5423 | DIAMETER_ERROR_UNKNOWN_SERVING_NODE | | +| Note: The Experimental Result Codes from 5424 to 5449 are reserved for the TS 29.272. | | | +| 5450 | DIAMETER_ERROR_USER_NO_NON_3GPP_SUBSCRIPTION | 29.273 [20] | +| 5451 | DIAMETER_ERROR_USER_NO_APN_SUBSCRIPTION | | +| 5452 | DIAMETER_ERROR_RAT_TYPE_NOT_ALLOWED | | +| 5453 | DIAMETER_ERROR_LATE_OVERLAPPING_REQUEST | | +| 5454 | DIAMETER_ERROR_TIMED_OUT_REQUEST | | +| 5455 | DIAMETER_ERROR_TRUSTED_NON_3GPP_ACCESS_NOT_ALLOWED | | +| 5456 | DIAMETER_ERROR_UNTRUSTED_NON_3GPP_ACCESS_NOT_ALLOWED | | +| Note: The Experimental Result Codes from 5455 to 5469 are reserved for the TS 29.273. | | | +| 5470 | DIAMETER_ERROR_SUBSESSION | 29.215 [22] | +| 5471 | DIAMETER_ERROR_ONGOING_SESSION_ESTABLISHMENT | | +| Note: The Experimental Result Codes from 5472 to 5489 are reserved for the TS 29.215. | | | +| 5490 | DIAMETER_ERROR_UNAUTHORIZED_REQUESTING_NETWORK | 29.173 [25] | +| Note: The Experimental Result Codes from 5491 to 5509 are reserved for the TS 29.173. | | | +| 5510 | DIAMETER_ERROR_UNAUTHORIZED_REQUESTING_ENTITY | 29.336 [28] | +| 5511 | DIAMETER_ERROR_UNAUTHORIZED_SERVICE | | +| 5512 | DIAMETER_ERROR_REQUESTED_RANGE_IS_NOT_ALLOWED | | +| 5513 | DIAMETER_ERROR_CONFIGURATION_EVENT_STORAGE_NOT_SUCCESSFUL | | +| 5514 | DIAMETER_ERROR_CONFIGURATION_EVENT_NON_EXISTANT | | +| 5515 | DIAMETER_ERROR_SCEF_REFERENCE_ID_UNKNOWN | | +| 5516 | DIAMETER_ERROR_UNAUTHORIZED_MTC_PROVIDER | | +| Note: The Experimental Result Codes from 5517 to 5529 are reserved for the TS 29.336. | | | +| 5530 | DIAMETER_ERROR_INVALID_SME_ADDRESS | 29.337 [29] | +| 5531 | DIAMETER_ERROR_SC_CONGESTION | | +| 5532 | DIAMETER_ERROR_SM_PROTOCOL | | +| 5533 | DIAMETER_ERROR_TRIGGER_REPLACE_FAILURE | | +| 5534 | DIAMETER_ERROR_TRIGGER_RECALL_FAILURE | | +| 5535 | DIAMETER_ERROR_ORIGINAL_MESSAGE_NOT_PENDIN G | | +| Note: The Experimental Result Codes from 5536 to 5549 are reserved for the TS 29.337. | | | +| 5550 | DIAMETER_ERROR_ABSENT_USER | 29.338 [30] | +| 5551 | DIAMETER_ERROR_USER_BUSY_FOR_MT_SMS | | +| 5552 | DIAMETER_ERROR_FACILITY_NOT_SUPPORTED | | +| 5553 | DIAMETER_ERROR_ILLEGAL_USER | | +| 5554 | DIAMETER_ERROR_ILLEGAL_EQUIPMENT | | +| 5555 | DIAMETER_ERROR_SM_DELIVERY_FAILURE | | +| 5556 | DIAMETER_ERROR_SERVICE_NOT_SUBSCRIBED | | +| 5557 | DIAMETER_ERROR_SERVICE_BARRED | | +| 5558 | DIAMETER_ERROR_MWD_LIST_FULL | | +| Note: The Experimental Result Codes from 5559 to 5569 are reserved for the TS 29.338. | | | +| 5570 | DIAMETER_ERROR_UNKNOWN_POLICY_COUNTERS | 29.219 [26] | +| Note: The Experimental Result Codes from 5571 to 5589 are reserved for the TS 29.219. | | | +| 5590 | DIAMETER_ERROR_ORIGIN_ALUID_UNKNOWN | 29.343 [32] | +| 5591 | DIAMETER_ERROR_TARGET_ALUID_UNKNOWN | | +| 5592 | DIAMETER_ERROR_PPID_UNKNOWN | | +| 5593 | DIAMETER_ERROR_APP_REGISTER_REJECT | | + +| | | | +|---------------------------------------------------------------------------------------|--------------------------------------------------|-------------| +| 5594 | DIAMETER_ERROR_PROSE_MAP_REQUEST_DISALLOWED | | +| 5595 | DIAMETER_ERROR_MAP_REQUEST_REJECT | | +| 5596 | DIAMETER_ERROR_REQUESTING_RPAUID_UNKNOWN | | +| 5597 | DIAMETER_ERROR_UNKNOWN_OR_INVALID_TARGET_SET | | +| 5598 | DIAMETER_ERROR_MISSING_APPLICATION_DATA | | +| 5599 | DIAMETER_ERROR_AUTHORIZATION_REJECT | | +| 5600 | DIAMETER_ERROR_DISCOVERY_NOT_PERMITTED | | +| 5601 | DIAMETER_ERROR_TARGET_RPAUID_UNKNOWN | | +| 5602 | DIAMETER_ERROR_INVALID_APPLICATION_DATA | | +| Note: The Experimental Result Codes from 5603 to 5609 are reserved for the TS 29.343. | | | +| 5610 | DIAMETER_ERROR_UNKNOWN_PROSE_SUBSCRIPTION | 29.344 [33] | +| 5611 | DIAMETER_ERROR_PROSE_NOT_ALLOWED | | +| 5612 | DIAMETER_ERROR_UE_LOCATION_UNKNOWN | | +| Note: The Experimental Result Codes from 5613 to 5629 are reserved for the TS 29.344. | | | +| 5630 | DIAMETER_ERROR_NO_ASSOCIATED_DISCOVERY_FILTER | 29.345 [34] | +| 5631 | DIAMETER_ERROR_ANNOUNCING_UNAUTHORIZED_IN_PLMN | | +| 5632 | DIAMETER_ERROR_INVALID_APPLICATION_CODE | | +| 5633 | DIAMETER_ERROR_PROXIMITY_UNAUTHORIZED | | +| 5634 | DIAMETER_ERROR_PROXIMITY_REJECTED | | +| 5635 | DIAMETER_ERROR_NO_PROXIMITY_REQUEST | | +| 5636 | DIAMETER_ERROR_UNAUTHORIZED_SERVICE_IN_THIS_PLMN | | +| 5637 | DIAMETER_ERROR_PROXIMITY_CANCELLED | | +| 5638 | DIAMETER_ERROR_INVALID_TARGET_PDUID | | +| 5639 | DIAMETER_ERROR_INVALID_TARGET_RPAUID | | +| 5640 | DIAMETER_ERROR_NO_ASSOCIATED_RESTRICTED_CODE | | +| 5641 | DIAMETER_ERROR_INVALID_DISCOVERY_TYPE | | +| Note: The Experimental Result Codes from 5642 to 5649 are reserved for the TS 29.345. | | | +| 5650 | DIAMETER_ERROR_REQUESTED_LOCATION_NOT_SERVED | 29.128 [36] | +| 5651 | DIAMETER_ERROR_INVALID_EPS_BEARER | | +| 5652 | DIAMETER_ERROR_NIDD_CONFIGURATION_NOT_AVAILABLE | | +| 5653 | DIAMETER_ERROR_USER_TEMPORARILY_UNREACHABLE | | +| Note: The Experimental Result Codes from 5654 to 5669 are reserved for the TS 29.128. | | | +| 5670 | DIAMETER_ERROR_UNKNOWN_DATA | 29.283 [39] | +| 5671 | DIAMETER_ERROR_REQUIRED_KEY_NOT_PROVIDED | | +| Note: The Experimental Result Codes from 5672 to 5689 are reserved for the TS 29.128. | | | +| 5690 | DIAMETER_ERROR_UNKNOWN_V2X_SUBSCRIPTION | 29.388 [40] | +| 5691 | DIAMETER_ERROR_V2X_NOT_ALLOWED | | +| Note: The Experimental Result Codes from 5692 to 5709 are reserved for the TS 29.388. | | | + +# --- Annex A (informative): Assignment of the Diameter codes and identifiers in 3GPP + +This annex defines the recommended assignment procedure of Diameter codes and identifiers within the 3GPP. + +## --- A.1 Application identifiers + +If a working group detects it will require a new application identifier, it should contact the 3GPP TSG-CN WG 4 via a Liaison Statement. The LS shall contain the name of the Diameter application and a reference to the corresponding 3GPP TS. The 3GPP TSG-CN WG 4 will then request the application identifier from IANA. When the application identifier is received, the corresponding working group will be informed by 3GPP TSG-CN WG 4 and the table 4.1 in this specification will be updated. + +According to RFC 3588 the creation of a new application should be avoided if at all possible and therefore it is recommended to use the existing application identifiers whenever possible. + +## --- A.2 Command codes + +If a working group detects there is a need for a new command code(s) from the 3GPP's range, it should contact the 3GPP TSG-CN WG 4 via an LS. The LS shall contain the reference to the 3GPP TS, which specifies the command(s). The 3GPP TSG-CN WG 4 will inform the assigned command code(s) to the corresponding working group and the table 5.1 in this specification will be updated. + +It should be noted that the standard command codes allocated for 3GPP are scarce resource and getting new ones would require IETF specification work to be done. Therefore it is recommended to use the existing command codes whenever possible. + +## --- A.3 AVP codes + +If a working group detects a Diameter application needs new 3GPP specific AVP codes, it should contact the 3GPP TSG-CN WG 4 via an LS. The LS shall contain the name of the Diameter application and a reference to the corresponding 3GPP TS. The 3GPP TSG-CN WG 4 will allocate a range of 100 AVP codes for the application. The range will be informed to the corresponding working group and the table 7.1 will be updated in this specification to show the reserved range. The working group can use the allocated range as a working assumption when defining the actual AVPs. + +When the corresponding working group has specified the AVPs, and the specification has been approved and is under CR control, it should inform the AVPs to the 3GPP TSG-CN WG 4 via an LS. The LS should list the used AVP codes in the form of the table 7.1. + +If there will be defined new AVPs for a Diameter application through the CR procedure, the assigned AVP range can be used, but the 3GPP TSG-CN WG 4 should be also informed about the new AVP codes via an LS. + +Re-using of the existing AVPs is recommended, but special attention should be paid on the use of enumerated AVPs. Defining new values for an enumerated AVP should be agreed case by case with the working group responsible of the particular enumerated AVP. 3GPP TSG-CN WG 4 shall be informed via an LS about the new values assigned to the enumerated AVP. + +## --- A.4 Result codes + +If a working group detects a Diameter application needs new 3GPP specific result codes, it should contact the 3GPP TSG-CN WG 4 via an LS. The LS shall contain the name of the Diameter application and a reference to the corresponding 3GPP TS. The 3GPP TSG-CN WG 4 will allocate a range of 20 result codes from each required result + +code group for the application. The ranges will be informed to the corresponding working group and the tables in the chapter 8 of this specification will be updated to show the reserved ranges. The working group can use the allocated ranges as a working assumption when defining the actual result codes. + +When the corresponding working group has specified the result codes, and the specification has been approved and is under CR control, it should convey the codes to the 3GPP TSG-CN WG 4 via an LS. The LS should list the used result codes in the form of the tables in chapter 8. + +If there will be defined new result codes for a Diameter application through the CR procedure, the assigned result code ranges can be used, but the 3GPP TSG-CN WG 4 should be also informed about the new result codes via an LS. + +Re-using of the existing result codes is recommended. + +# Annex B (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Ca
t | Subject/Comment | New | +|---------|-------|-----------|------|-----|---------|-----------------------------------------------------------------------------------------------------------|-------| +| 2004-06 | CN#24 | NP-040292 | | | | Version 2.0.0 presented for information and approval | 6.0.0 | +| 2004-09 | CN#25 | NP-040401 | 001 | | | Correction of Charging application reference | 6.1.0 | +| 2004-09 | CN#25 | NP-040401 | 002 | | | Correction of the Application-Id code | 6.1.0 | +| 2004-09 | CN#25 | NP-040401 | 003 | | | Removal of User Data Request Type AVP | 6.1.0 | +| 2004-09 | CN#25 | NP-040412 | 004 | 1 | | Re-numbering of 3GPP specific AVP codes. | 6.1.0 | +| 2004-12 | CN#26 | NP-040579 | 006 | | | Inclusion of missing Cx AVPs | 6.2.0 | +| 2004-12 | CN#26 | NP-040580 | 007 | 1 | | Reservation of command code 310 | 6.2.0 | +| 2004-12 | CN#26 | NP-040579 | 009 | 1 | | Addition of Gmb interface | 6.2.0 | +| 2004-12 | CN#26 | NP-040600 | 010 | 2 | | Documenting the Reuse of the 3GPP specific application identifier of Ro for Re on the Charging Interfaces | 6.2.0 | +| 2004-12 | CN#26 | NP-040579 | 011 | | | Gq interface allocations | 6.2.0 | +| 2004-12 | CN#26 | NP-040579 | 012 | | | Addition of Gx interface | 6.2.0 | +| 2005-03 | CN#27 | NP-050047 | 040 | 1 | | WLAN Diameter AVP and result codes | 6.3.0 | +| | | NP-050039 | 043 | | | Allocations for Gx interface | | +| | | NP-050039 | 045 | | | Allocations for Gmb interface | | +| | | NP-050039 | 046 | | | Allocations for MMS, MM10 Interface | | +| 2005-06 | CT#28 | CP-050088 | 0050 | | | Gx interface allocation correction | 6.4.0 | +| | | CP-050196 | 0051 | 1 | | Addition of Maximum-Number-Accesses AVP | | +| 2005-09 | CT#29 | CP-050440 | 0052 | 1 | | Private identities on the Cx | 6.5.0 | +| | | CP-050310 | 0053 | | | Addition of Pr reference point to TS 29.230 | | +| | | CP-050310 | 0054 | | | Error code cleanup | | +| | | CP-050310 | 0056 | | | Addition of Rx ref. point and renaming of Experimental Result Codes | | +| 2005-09 | CT#29 | CP-050317 | 0055 | | | Addition of GUSS timestamp AVP | 7.0.0 | +| 2005-12 | CT#30 | CP-050624 | 0058 | | | Addition of GBA-Type AVP | 7.1.0 | +| | | CP-050612 | 0063 | | | Additional Gmb AVP Allocation | | +| | | CP-050612 | 0065 | | | Reservation of AVP codes for 32.299 | | +| | | CP-050625 | 0066 | | | Management of Sh subscriptions | | +| 2006-03 | CT#31 | CP-060073 | 0069 | | | Adding data type of some of WLAN-related AVPs | 7.2.0 | +| | | CP-060084 | 0071 | | | User-Data in the response to Sh-Subs-Notif | | +| | | CP-060084 | 0072 | 1 | | New error indications for the Sh-Subs-Notif procedure | | +| 2006-06 | CT#32 | CP-060302 | 0075 | | | S-CSCF reselection removal | 7.3.0 | +| 2006-09 | CT#33 | CP-060417 | 0077 | 3 | | New AVP Code | 7.4.0 | +| | | CP-060417 | 0080 | | | Errors to be sent in response to Sh-Notif | | +| | | CP-060417 | 0081 | | | Definition of specific Diameter codes for DSAI | | +| 2006-12 | CT#34 | CP-060566 | 0085 | 1 | | Optimization of handling of Wildcarded PSIs | 7.5.0 | +| | | CP-060562 | 0086 | | | Addition of Diameter Error Code for Emergency Purposes | | +| | | CP-060555 | 0087 | | | Allocation of new AVP codes for Gmb | | +| | | CP-060555 | 0089 | | | AVP code allocations for Rf and Ro interfaces | | +| | | CP-060566 | 0091 | | | Allocation of Success Result Code Range for Gi Interface | | +| 2007-03 | CT#35 | CP-070020 | 0093 | | | C3 requested addition of new AVP code values to 3GPP TS 29.230 | 7.6.0 | +| | | CP-070020 | 0093 | | | Allocation of new AVP code for DSAI-Tag AVP | | +| | | CP-070020 | 0093 | | | Allocation of Experimental-Result-Code AVP for Gi Interface | | +| 2007-06 | CT#36 | CP-070318 | 0096 | | | Diameter application ID for the Rel-7 Rx interface | 7.7.0 | +| | | CP-070312 | 0098 | | | Experimental-Result-Codes for Gmb interface | | +| | | CP-070312 | 0100 | | | Correction of Diameter AVP code allocation | | +| 2007-09 | CT#37 | CP-070527 | 0102 | | | Application ID for Gx protocol | 7.8.0 | +| 2007-12 | CT#38 | CP-070743 | 0104 | | | AVP code reservation for 32.299 in Rel-7 | 7.9.0 | +| | | | 0105 | | | Allocation of 3GPP specific AVP codes and Experimental Result Codes for Gx protocol | | +| 2007-12 | CT#38 | CP-070755 | 0101 | 4 | | AVP assignments to support SIP Digest Authentication | 8.0.0 | +| | | | 0103 | | | AVP code reservation for 32.299 in Rel-8 | | +| 2008-03 | CT#39 | CP-080015 | 0109 | | | Correction of reference to TS 29.140 | 8.1.0 | +| | | CP-080019 | 0111 | | | AVP code reservation for TS 32.299 in Rel-8 | | +| | | CP-080019 | 0107 | | | Wildcarded Public User Identities | | +| | | CP-080191 | 0112 | 1 | | Correction on AVP code allocation reservation for TS 32.299 in Rel-7 | | +| | | CP-080204 | 0113 | 1 | | Correction on AVP code allocation reservation for TS 32.299 | | +| 2008-06 | CT#40 | CP-080267 | 0117 | 1 | | A new Diameter Permanent Failure Code for Gx | 8.2.0 | +| 2008-09 | CT#41 | CP-080456 | 0119 | | | Emergency Public User Identity Removal | 8.3.0 | +| 2008-09 | CT#41 | CP-080460 | 0121 | 1 | | Support of "Loose-Route" indication from HSS | | +| 2008-09 | CT#41 | CP-080460 | 0122 | 1 | | STaMIP Application Id | | + +| | | | | | | | | +|---------|-------|-----------|------|---|--|----------------------------------------------------------------------------|--------| +| 2008-09 | CT#41 | CP-080463 | 0123 | | | Cx Impacts of IMS Restoration Procedures (New AVP Codes Assignment) | | +| 2008-09 | CT#41 | CP-080463 | 0124 | | | New AVP Code Assignment for Forking Service Restoration | 8.3.0 | +| 2008-12 | CT#42 | CP-080691 | 0127 | 2 | | Diameter Protocol Codes Assignments for S6a/S6d/S13 | 8.4.0 | +| 2008-12 | CT#42 | CP-080691 | 0128 | 1 | | Diameter code assignments for 3GPP TS 29.273 | 8.4.0 | +| 2009-03 | CT#43 | CP-090044 | 0130 | 1 | | Update for ReadyForSM | 8.5.0 | +| 2009-03 | CT#43 | CP-090044 | 0131 | 1 | | Handling LCS Subscription Data | 8.5.0 | +| 2009-03 | CT#43 | CP-090026 | 0132 | | | Update for Restoration | 8.5.0 | +| 2009-03 | CT#43 | CP-090024 | 0133 | | | AppIds for Gxx and S9 | 8.5.0 | +| 2009-03 | CT#43 | CP-090033 | 0134 | 2 | | AppId and command code for Zpn | 8.5.0 | +| 2009-03 | CT#43 | CP-090024 | 0137 | 1 | | AVP codes for S9 protocol | 8.5.0 | +| 2009-03 | CT#43 | CP-090024 | 0138 | 1 | | Diameter AVP Code allocation | 8.5.0 | +| 2009-03 | CT#43 | CP-090024 | 0140 | 1 | | Location of Permanent Failure result code range for the S9 application | 8.5.0 | +| 2009-03 | CT#43 | CP-090024 | 0141 | | | AVPs for TS 29.273 | 8.5.0 | +| 2009-03 | CT#43 | CP-090024 | 0142 | 1 | | Error code allocation for authentication failure | 8.5.0 | +| 2009-06 | CT#44 | CP-090299 | 0129 | 4 | | Update of the AVP Codes | 8.6.0 | +| | | CP-090299 | 0143 | | | AVP code reservation for TS 32.299 | | +| | | CP-090299 | 0145 | | | Diameter Command Codes for S6a/S6d/S13/S13' | | +| | | CP-090299 | 0146 | | | Removal of Requesting Node Type from AIR | | +| | | CP-090299 | 0147 | | | S6b Application ID | | +| 2009-09 | CT#45 | CP-090530 | 0149 | | | Allocation of Experimental-Result-Codes for S9 protocol | 8.7.0 | +| | | CP-090530 | 0152 | | | AVP code allocation for TS 29.212 | | +| | | CP-090531 | 0150 | | | Update of the AVP type for the User-Id | | +| | | CP-090531 | 0153 | | | Trace Depth per session | | +| 2009-09 | CT#45 | CP-090557 | 0148 | | | AVP code range for charging | 9.0.0 | +| 2009-12 | CT#46 | CP-090800 | 0154 | 1 | | ICS-Flag | 9.1.0 | +| | | CP-091032 | 0156 | | | From GMLC-Address to GMLC-Number | | +| | | | 0160 | | | Session-Priority AVP | | +| | | | 0163 | 2 | | Introduction of SLh application related AVPs and Experimental Result codes | | +| | | | 0166 | | | Missing AVP error codes | | +| | | CP-090797 | 0167 | 1 | | Introduction of SLg application related AVPs and Application Identifier | | +| 2010-03 | CT#47 | CP-100031 | 0158 | 1 | | Wildcarded Public Identity | 9.2.0 | +| | | CP-100034 | 0168 | 1 | | Correction on AVP code allocation reservation for TS 32.299 in Rel-9 | | +| | | CP-100046 | 0169 | 1 | | AVP code allocation for 29.172 | | +| | | CP-100036 | 0172 | | | GPL_U support in TS 29.109 | | +| | | CP-100046 | 0173 | | | Error codes in 29.172 for SLg | | +| | | CP-100048 | 0174 | 1 | | AVPs in 29.272 for TADS support | | +| | | CP-100040 | 0175 | | | Error codes in 29.272 for Unknown MME | | +| | | CP-100236 | 0176 | 4 | | EPS Subscriber State and Location Information Request | | +| | | CP-100033 | 0180 | | | One time notification AVP allocation | | +| | | CP-100046 | 0181 | | | Addition of the LCS-QoS-Class attribute value | | +| 2010-06 | CT#48 | CP-100175 | 0182 | | | Introduction of the LCS-Capabilities-Sets AVP in SLh interface | 9.3.0 | +| | | CP-100263 | 0188 | 1 | | AVP Codes for PCC | | +| | | | 0183 | | | EPS state and location retrieval | | +| | | CP-100287 | 0186 | | | SGmb Application ID | | +| 2010-09 | CT#49 | CP-100277 | 0190 | 1 | | New APVs in S6a protocol | 9.4.0 | +| | | CP-100463 | 0197 | 1 | | Addition of Diameter codes and identifiers for the SLg and SLh interfaces | | +| 2010-09 | CT#49 | CP-100464 | 0196 | | | AVP Codes Allocation for PCC | 10.0.0 | +| | | CP-100465 | 0193 | 1 | | SIPTO Permission Indicator | | +| | | CP-100466 | 0198 | 2 | | Location data including only serving node address | | +| 2010-12 | CT#50 | CP-100466 | 0199 | 1 | | AVP for Update-Eff feature | 10.1.0 | +| | | CP-100699 | 0205 | | | Enhanced SRVCC Subscriber Data | | +| | | CP-100687 | 0201 | 1 | | Allocate codes for AVPs on eMPS | | +| | | CP-100683 | 0200 | 1 | | Allocate codes for AVPs on LIPA | | +| | | CP-100688 | 0206 | 1 | | Periodic TAU/RAU timer in HSS subscription | | +| 2011-03 | CT#51 | CP-100846 | 0203 | 1 | | S6a Error Diagnostic | 10.2.0 | +| | | CP-110051 | 0212 | | | PDP-Address correction | | +| | | CP-110054 | 0215 | | | Essential correction on the value type of the ELP Application AVPs | | +| | | CP-110087 | 0207 | 2 | | Minimization of Drive Tests (MDT) | | +| 2011-06 | CT#52 | CP-110088 | 0209 | 1 | | Relay Node Indicator AVPs | 10.3.0 | +| | | CP-110349 | 0219 | 2 | | Handling of RTR for Emergency Registration | | +| | | CP-110347 | 0231 | 1 | | Add AVPs from QSPEC cleanup | | +| | | CP-110359 | 0226 | | | MIPv4 security parameters on the STa and S6b interfaces | | +| | | CP-110380 | 0216 | | | MDT user consent | | +| | | CP-110370 | 0223 | | | AVP Code Allocation for Pre-paging | | +| 2011-09 | CT#53 | CP-110375 | 0227 | 1 | | PUR-Flags AVP | 10.4.0 | +| | | CP-110559 | 0236 | 1 | | AVP code alignment with 29.212 | | +| | | CP-110555 | 0239 | 1 | | AVP code alignment with 32.299 | | +| | | CP-110554 | 0244 | 1 | | AVP code alignment with 29.214 | | + +| | | | | | | | | +|---------|-------|-----------|------|---|--|-----------------------------------------------------------------------------------|--------| +| | | CP-110552 | 0249 | | | Experimental Result Code Alignment with 29.061 | | +| | | CP-110555 | 0252 | | | Failure code and AVP code alignment with 29.212 | | +| | | CP-110722 | 0257 | 2 | | Privileged sender | | +| 2011-09 | CT#53 | CP-110584 | 0234 | 1 | | Add vSRVCC updates to the Diameter AVP code table | 11.0.0 | +| | | CP-110579 | 0240 | | | AVP code alignment with 32.299 | | +| | | CP-110555 | 0253 | | | AVP code reservation for 29.212 | | +| 2011-12 | CT#54 | CP-110812 | 0258 | 1 | | SWx Restoration AVPs | 11.1.0 | +| | | CP-110812 | 0259 | | | Sy and Sd Application IDs | | +| | | CP-110775 | 0262 | | | New AVP codes for MBMS IP unicast encapsulation | | +| | | CP-110775 | 0265 | | | New AVP codes for MBMS IP multicast encapsulation | | +| | | CP-110786 | 0271 | 1 | | MME-Realm AVP code allocation | | +| | | CP-110811 | 0277 | | | Equivalent PLMN CSG Subscription Request | | +| | | CP-110781 | 0281 | 1 | | Restoration of Wildcarded-IMPU AVP | | +| 2012-03 | CT#55 | CP-120025 | 0286 | 1 | | Codes Allocation for AVPs on Initial Attach | 11.2.0 | +| | | CP-120038 | 0288 | | | New AVP codes for Absolute Time of MBMS Data Transfer over SGmb | | +| | | CP-120038 | 0291 | 1 | | Allocating Diameter AVP codes for TS 29.219 and TS 29.212 | | +| 2012-06 | CT#56 | CP-120240 | 0287 | 5 | | Codes Allocation for AVPs on NPLI | 11.3.0 | +| | | CP-120238 | 0294 | 1 | | Adding new Diameter AVPs to Diameter table to support Trusted WLAN Access feature | | +| | | CP-120225 | 0296 | 1 | | Trust Relationship Indication | | +| | | CP-120251 | 0297 | 1 | | Corrections to reference titles | | +| | | CP-120251 | 0298 | 1 | | Diameter Code Allocation for TS 29.219 | | +| | | CP-120247 | 0300 | - | | Network Name AVP codes | | +| | | CP-120219 | 0304 | - | | Duplicated AVP names | | +| 2012-09 | CT#57 | CP-120481 | 0289 | 3 | | PS additional number allocation | 11.4.0 | +| | | CP-120473 | 0293 | 4 | | SMS in MME/SGSN | | +| | | CP-120461 | 0299 | 2 | | AAA Failure Recovery AVP codes | | +| | | CP-120474 | 0305 | - | | Transport Access Type AVP for BBAI | | +| | | CP-120480 | 0307 | 1 | | Local Time Zone | | +| | | CP-120472 | 0308 | - | | Allocating Application Identifier and command code for Tsp interface | | +| | | CP-120472 | 0309 | - | | Application Identifier, Command Codes and AVP range for S6m interface | | +| | | CP-120667 | 0312 | 1 | | GMLC-Name | | +| | | CP-120667 | 0313 | 1 | | Reference list correction to align with the corrected TS 29.212 title | | +| 2012-12 | CT#58 | CP-120731 | 0315 | 2 | | T4 device triggering via IMS | 11.5.0 | +| | | CP-120731 | 0318 | 1 | | Codes and Identifier Allocation for T4 Specification | | +| | | CP-120731 | 0324 | - | | AVP Code Allocation for 29.336 | | +| | | CP-120731 | 0329 | - | | Diameter AVP code value allocation in TS 29.368 | | +| | | CP-120732 | 0319 | 2 | | Application Identifier, Command Codes and AVP codes for SGd, S6c | | +| | | CP-120716 | 0324 | 1 | | AVP name modification in TS 32.299 | | +| | | CP-120742 | 0325 | - | | UE Time Zone AVP | | +| | | CP-120741 | 0328 | 1 | | Use of Flag instead of Enumerated AVPs | | +| | | CP-120741 | 0332 | - | | Use of Flag instead of Enumerated AVPs | | +| | | CP-120743 | 0330 | - | | PSI direct routing with restoration procedures | | +| | | CP-120743 | 0333 | - | | EPS LocationInformation Support | | +| 2013-03 | CT#59 | CP-130026 | 0334 | 1 | | Diameter error code for TS 29.219 | 11.6.0 | +| | | CP-130026 | 0336 | - | | MDT parameters | | +| 2013-03 | CT#59 | CP-130156 | 0337 | 1 | | New AVPs for Lgd interface | 12.0.0 | +| | | CP-130030 | 0341 | - | | Validity Time of Short Message | | +| 2013-06 | CT#60 | CP-130288 | 0362 | 1 | | Add new DER-S6b-flag AVP | 12.1.0 | +| | | CP-130298 | 0360 | - | | Failure Result Codes Allocation for TS 29.219 | | +| | | CP-130292 | 0358 | - | | Diameter AVP codes for new TS 32.299 AVPs | | +| | | CP-130279 | 0354 | 1 | | Definition of SS Status for Call Barring | | +| | | CP-130380 | 0363 | - | | New SGs-MME-Identity AVP | | +| | | CP-130291 | 0348 | 2 | | New AVPs for deferred MT-LR and periodic MO-LR TTTP procedures over Lgd interface | | +| | | CP-130297 | 0347 | 1 | | Application Port Identifier | | +| | | CP-130374 | 0345 | 1 | | MTRR on Sh | | +| | | CP-130295 | 0344 | - | | Restoration Priority during SGW and PGW restoration procedures | | +| | | CP-130378 | 0349 | 1 | | SIPTO permission for Local Network enhancements | | +| | | CP-130454 | 0364 | 2 | | New MBMS flag for eMBMS restoration | | +| | | CP-130461 | 0366 | - | | AVP code reservation for TS 32.299 Rel-12 | | +| | | CP-130460 | 0368 | - | | Allocation of Diameter codes and identifiers for 29.212 and 29.215 | | +| 2013-09 | | | | - | | Vendor-specific command code for Trigger-Establishment-Request/Answer corrected | 12.2.1 | +| 2013-12 | CT#62 | CP-130624 | 0369 | - | | New AVP for optimized LCS procedure for combined MME/SGSN | 12.3.0 | +| | | CP-130631 | 0370 | 1 | | Adding E-SMLC provided Cell info and Cell Portion | | +| | | CP-130800 | 0371 | - | | New AVPs for SMS for IMS UE without MSISDN in TS 29.338 | | +| | | CP-130600 | 0376 | 1 | | Allocation of Diameter codes for 32.299 | | +| | | CP-130605 | 0378 | - | | Allocation of Diameter codes for 29.212 | | +| | | CP-130639 | 0380 | - | | SGSN CAMEL Subscription Indication | | +| 2014-03 | CT#63 | CP-140180 | 0381 | 2 | | Protocol enhancements for the support of device replace | 12.4.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|--|-----------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | procedure | | +| | | CP-140035 | 0384 | - | | New AVP for the support of combined MME/SGSN | | +| | | CP-140023 | 0383 | 1 | | Definition of WLAN-related AVPs | | +| 2014-06 | CT#64 | CP-140211 | 0385 | 1 | | Protocol enhancements to indicate support of device recall and replace by SMS-SC | 12.5.0 | +| | | CP-140251 | 0402 | 1 | | AVP allocation for Error handling, MTC error diagnostic | | +| | | CP-140257 | 0391 | 1 | | SS-Status AVP Definition | | +| | | CP-140252 | 0392 | - | | Definition of AVPs for Network Location in TWLAN | | +| | | CP-140236 | 0399 | - | | TWAN-BSSID AVP re-naming | | +| | | CP-140247 | 0397 | - | | New AVPs for Trusted WLAN access | | +| | | CP-140231 | 0390 | 1 | | Adding Codes for 29.214 | | +| 2014-09 | CT#65 | CP-140515 | 0403 | 1 | | T-GRUU restoration | 12.6.0 | +| | | CP-140517 | 0404 | 1 | | MB2-C codes | | +| | | CP-140505 | 0405 | 1 | | New AVPs for Trusted WLAN access | | +| | | CP-140506 | 0406 | 1 | | P-CSCF Restoration indication | | +| | | CP-140516 | 0407 | 2 | | Closing TS 29.234 and reused AVP in TS 29.273 | | +| | | CP-140513 | 0408 | - | | Identification of the HSS | | +| | | | | | | Editorial: WLAN-offloadability AVP codes added as in CR C4-141648. | | +| 2014-12 | CT#66 | CP-140785 | 0409 | 1 | | New AVP for MBMS restoration | 12.7.0 | +| | | | 0430 | - | | New Diagnostic-Info AVP for MBMS restoration | | +| | | | 0410 | 1 | | WLCP key for WLCP signalling protection | | +| | | | 0411 | - | | Reset-ID | | +| | | | 0416 | 1 | | Code definitions for 32.299 | | +| | | | 0428 | - | | Removal of I-WLAN AVPs | | +| | | | 0429 | 1 | | Reference correction | | +| | | | 0433 | - | | Code allocation for 29.212 | | +| | | | 0418 | - | | MDT PLMN List | | +| | | | 0422 | 1 | | Codes Allocation for PC2 Protocol | | +| | | | 0423 | 4 | | Codes Allocation for PC4a Protocol | | +| | | | 0431 | 3 | | Allocation of values for Application ID, Command codes, AVP codes and Experimental-Result codes used in the TS 29.345 | | +| | | | 0434 | 1 | | Command Code and Error Code for ProSe Initial Location Information Retrieval | | +| | | | 0425 | - | | Corrections of the type of some AVPs | | +| | | | 0426 | 1 | | OFR-Flags AVP code | | +| | | | 0427 | 1 | | P-CSCF Restoration mechanism new error | | +| 2015-03 | CT#67 | CP-150015 | 0447 | - | | Renaming of Location-Type AVP | 12.8.0 | +| | | | 0437 | 1 | | Location reporting in emergency 1xSRVCC | | +| | | | 0435 | - | | AVP codes for GCSE MB2-C | | +| | | | 0442 | 1 | | New AVPs and range of transient failure result codes in TS 29.214 | | +| | | | 0438 | 1 | | Allocation of code for Authorized-Discovery-Range AVP (TS 29.344) | | +| | | | 0440 | 2 | | Location Update Trigger | | +| | | | 0441 | 1 | | AVP codes allocation for Validity related AVPs for TS 29.345 | | +| | | | 0443 | - | | Allocation of codes for the Integrity Checks. Aspect AVPs | | +| 2015-03 | CT#67 | CP-150039 | 0439 | 1 | | Diameter Application Identifier for Np protocol | 13.0.0 | +| 2015-06 | CT#68 | CP-150257 | 0450 | 1 | | AVP code allocation for Match Refresh Timer AVP in TS 29.345 | 13.1.0 | +| | | CP-150247 | 0457 | - | | Wrong CR implementation of CR 0416r1 | | +| | | CP-150249 | 0459 | 1 | | AVP code allocation for 32.299 | | +| | | CP-150263 | 0452 | 1 | | AVP codes for Access Restriction Data per PLMN | | +| | | CP-150372 | 0461 | - | | IP-SM-GW-Realm | | +| 2015-09 | CT#69 | CP-150454 | 0462 | - | | Subscription data for extended buffering at the SGW | 13.2.0 | +| | | CP-150442 | 0463 | - | | Overlapping transaction over S6b | | +| | | CP-150453 | 0464 | 2 | | Addition of IMSI Group Id AVP definition | | +| | | CP-150449 | 0465 | 3 | | Addition of CP parameter AVP definition | | +| | | CP-150431 | 0470 | 1 | | AVP codes for TS 29.212 | | +| | | CP-150456 | 0471 | 3 | | AVP definition for S6t | | +| 2015-12 | CT#70 | CP-150761 | 0473 | - | | Addition of MBMS-Cell-List AVP | 13.3.0 | +| | | CP-150778 | 0474 | - | | S6t Application ID and Command Codes | | +| | | CP-150778 | 0474 | 1 | | Bitmask to inform the SCEF of the Monitoring capabilities | | +| | | CP-150778 | 0490 | 1 | | AVP codes for MONTE T6a/b interface | | +| | | CP-150778 | 0491 | 1 | | Correction to SCEF-Reference-ID and SCEF-Reference-ID-For-Deletion data types | | +| | | CP-150778 | 0494 | 2 | | Definition of AVP for deletion of all Monitoring events assigned to a subscriber (UE) | | +| | | CP-150778 | 0501 | 1 | | Definition of AVP SCEF-ID | | +| | | CP-150778 | 0502 | 2 | | Service result per Event configuration | | +| | | CP-150770 | 0475 | 1 | | Emergency PDN connection over untrusted WLAN access | | +| | | CP-150776 | 0476 | - | | EPC-MT-LR and PS-MT-LR procedure for UEs transiently not reachable due to power saving | | +| | | CP-150776 | 0497 | 1 | | Mobile Terminating SMS handling for extended Idle mode DRX | | +| | | CP-150776 | 0498 | 1 | | Mobile Terminating SMS handling for extended Idle mode DRX – Additional Option | | + +| | | | | | | | | +|---------|-------|-----------|------|---|--|--------------------------------------------------------------------------------------------------------------------------------|--------| +| | | CP-150777 | 0477 | 3 | | Commands and codes for Np protocol | | +| | | CP-150772 | 0479 | 1 | | Definition of ProSe-Metadata-Index-Mask | | +| | | CP-150772 | 0489 | - | | Addition of AVPs and result-codes | | +| | | CP-150772 | 0500 | - | | Addition of AVP used in match report procedure for eProSe-Ext-CT | | +| | | CP-150754 | 0481 | 1 | | Allowed WAF and/or WWSF Identities | | +| | | CP-150773 | 0482 | - | | Add the default access type to 3GPP specific AVP | | +| | | CP-150781 | 0484 | 1 | | AVP code allocation for "UE Usage Type" | | +| | | CP-150755 | 0486 | - | | Metadata in Match-Report | | +| | | CP-150755 | 0488 | - | | New Group AVP for ProSe direct discovery procedures | | +| | | CP-150771 | 0492 | 1 | | Definition of AVP for AESE-CT | | +| | | CP-150771 | 0496 | 1 | | Command codes and AVP range for TS 29.154 and TS 29.153 | | +| | | CP-150776 | 0495 | 1 | | AVP codes for Indoor Positioning support in SLg/Lgd | | +| 2016-03 | CT#71 | CP-160041 | 0503 | - | | Application ID for St | 13.4.0 | +| | | CP-160041 | 0506 | 1 | | Correction on TS numbers | | +| | | CP-160041 | 0510 | - | | AVPs for the Rx Diameter application | | +| | | CP-160041 | 0514 | 2 | | AVP code reservation for 32.299 | | +| | | CP-160041 | 0518 | 1 | | Codes for 29.212 | | +| | | CP-160029 | 0505 | 3 | | New AVP assignment for MONTE | | +| | | CP-160029 | 0509 | - | | Change of type of Monitoring-Duration AVP to represent an absolute time | | +| | | CP-160035 | 0507 | - | | Remove the default access AVP | | +| | | CP-160035 | 0508 | - | | Specific AVP codes for NBIFOM | | +| | | CP-160030 | 0511 | - | | Alert procedure from MME/SGSN to SMS-GMSC for MT SMS to UE using eDRX | | +| | | CP-160037 | 0512 | - | | ePDG retrieval of WLAN Location Information | | +| | | CP-160033 | 0513 | 2 | | Definition of AVP Authorization of NIDD | | +| | | CP-160033 | 0520 | 2 | | New PDN-Type for Cellular IoT | | +| | | CP-160036 | 0517 | 1 | | Monitoring update and Reporting of update result | | +| | | CP-160036 | 0519 | 3 | | Allocation of new Diameter Application ID and commands code for PC2 protocol | | +| 2016-03 | CT#71 | CP-160018 | 0515 | 1 | | AVP code reservation for 32.299 | 14.0.0 | +| 2016-06 | CT#72 | CP-160236 | 0526 | 1 | | Command Codes for 29.212 | 14.1.0 | +| 2016-06 | CT#72 | CP-160236 | 0543 | - | | AVP code range 3900-3999 | 14.1.0 | +| 2016-06 | CT#72 | CP-160236 | 0557 | 1 | | New AVPs in TS 29.214 | 14.1.0 | +| 2016-06 | CT#72 | CP-160236 | 0565 | - | | AVP codes for 29.212 | 14.1.0 | +| 2016-06 | CT#72 | CP-160232 | 0528 | 2 | | AVP Codes for 29.343 | 14.1.0 | +| 2016-06 | CT#72 | CP-160232 | 0533 | 3 | | Addition of new AVPs for ProSe direct discovery security and open ProSe direct discovery with application-controlled extension | 14.1.0 | +| 2016-06 | CT#72 | CP-160232 | 0540 | - | | Reserved Experimental Result Codes for TS 29.343 | 14.1.0 | +| 2016-06 | CT#72 | CP-160232 | 0549 | - | | Assignment of application ID and command code for PC2 reference point | 14.1.0 | +| 2016-06 | CT#72 | CP-160228 | 0531 | - | | IANA Command Code Registration | 14.1.0 | +| 2016-06 | CT#72 | CP-160228 | 0541 | 1 | | CloT new commands and Diameter error | 14.1.0 | +| 2016-06 | CT#72 | CP-160228 | 0550 | - | | NIDD authorisation update | 14.1.0 | +| 2016-06 | CT#72 | CP-160228 | 0560 | 3 | | Serving PLMN Rate Control | 14.1.0 | +| 2016-06 | CT#72 | CP-160228 | 0563 | - | | New AVP for APN Rate Control | 14.1.0 | +| 2016-06 | CT#72 | CP-160233 | 0537 | 1 | | Renaming of Validity-Time AVP | 14.1.0 | +| 2016-06 | CT#72 | CP-160233 | 0562 | 1 | | New AVPs allocated for 29.153 and 29.154 | 14.1.0 | +| 2016-06 | CT#72 | CP-160225 | 0545 | 3 | | SCEF Realm | 14.1.0 | +| 2016-06 | CT#72 | CP-160225 | 0548 | - | | Cleanup up on MONTE AVP's | 14.1.0 | +| 2016-06 | CT#72 | CP-160227 | 0546 | - | | IANA assigned application Id and command code values | 14.1.0 | +| 2016-06 | CT#72 | CP-160227 | 0547 | 2 | | Allocation of AVP codes and Experimental Result codes for Diameter Data Management application | 14.1.0 | +| 2016-06 | CT#72 | CP-160231 | 0553 | 1 | | 3GPP specific AVP for NBIFOM | 14.1.0 | +| 2016-06 | CT#72 | CP-160222 | 0555 | 1 | | Shared Subscription data update | 14.1.0 | +| 2016-09 | CT#73 | CP-160424 | 0570 | 1 | | Missing AVP codes and Experimental-Result codes for T6a | 14.2.0 | +| 2016-09 | CT#73 | CP-160424 | 0574 | 1 | | Allocate of AVP Handling of Exception Reports in the Core Network | 14.2.0 | +| 2016-09 | CT#73 | CP-160419 | 0572 | 1 | | AVP codes for 32.299 | 14.2.0 | +| 2016-09 | CT#73 | CP-160419 | 0576 | 1 | | AVP code for 29.214 | 14.2.0 | +| 2016-09 | CT#73 | CP-160419 | 0578 | 1 | | AVP code for 29.212 | 14.2.0 | +| 2016-09 | CT#73 | CP-160436 | 0568 | 1 | | STa and SWm extensions for IMEI check | 14.2.0 | +| 2016-12 | CT#74 | CP-160650 | 0582 | - | | AVP code alignment with 29.272 | 14.3.0 | +| 2016-12 | CT#74 | CP-160679 | 0579 | 1 | | AVPs for Handover of Emergency PDN Connections | 14.3.0 | +| 2016-12 | CT#74 | CP-160678 | 0583 | 1 | | New Diameter Application Code, AVP and Result Code for V2X | 14.3.0 | +| 2016-12 | CT#74 | CP-160653 | 0585 | 1 | | Renaming of Emergency-Indication AVP | 14.3.0 | +| 2016-12 | CT#74 | CP-160670 | 0586 | 2 | | New AVPs for TS 29.214 | 14.3.0 | +| 2016-12 | CT#74 | CP-160660 | 0590 | - | | S6t-HSS-Cause | 14.3.0 | +| 2016-12 | CT#74 | CP-160669 | 0591 | - | | AVP codes for 29.468 | 14.3.0 | +| 2017-03 | CT#75 | CP-170039 | 0592 | 1 | | Enhanced Coverage | 14.4.0 | +| 2017-03 | CT#75 | CP-170039 | 0593 | 1 | | Inter-RAT PDN-Continuity | 14.4.0 | +| 2017-03 | CT#75 | CP-170039 | 0595 | 1 | | NIDD Authorization revocation | 14.4.0 | +| 2017-03 | CT#75 | CP-170036 | 0594 | 1 | | Loss Of Connectivity Reason | 14.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|--|---------------------------------------------------------------|--------| +| 2017-03 | CT#75 | CP-170036 | 0602 | 1 | | Subscription parameters for eDRX | 14.4.0 | +| 2017-03 | CT#75 | CP-170036 | 0607 | 1 | | Support of long and short Macro eNodeB IDs | 14.4.0 | +| 2017-03 | CT#75 | CP-170025 | 0597 | - | | AVP codes for 32.299 | 14.4.0 | +| 2017-03 | CT#75 | CP-170043 | 0598 | 1 | | New AVP for UE-PC5-AMBR | 14.4.0 | +| 2017-03 | CT#75 | CP-170043 | 0603 | 1 | | Correct Diameter Result Code Allocated for V2X | 14.4.0 | +| 2017-03 | CT#75 | CP-170049 | 0601 | 1 | | AVPs for ERP in 29.273 | 14.4.0 | +| 2017-03 | CT#75 | CP-170052 | 0605 | - | | Update of the name of MCPTT-User-Profile-Data AVP | 14.4.0 | +| 2017-03 | CT#75 | CP-170045 | 0606 | - | | Support of MCVideo and MCData Services | 14.4.0 | +| 2017-06 | CT#76 | CP-171029 | 0600 | 4 | | New AVP for Group Based MONTE Event Configuration via HSS | 14.5.0 | +| 2017-06 | CT#76 | CP-171017 | 0609 | - | | New AVPs in 29.272 for MBSFN MDT | 14.5.0 | +| 2017-06 | CT#76 | CP-171026 | 0610 | - | | AVP codes for 29.212 | 14.5.0 | +| 2017-06 | CT#76 | CP-171026 | 0611 | - | | AVP codes for 29.214 | 14.5.0 | +| 2017-06 | CT#76 | CP-171030 | 0612 | 1 | | AVP code allocation for 29.172 for Location Services for CioT | 14.5.0 | +| 2017-06 | CT#76 | CP-171030 | 0613 | - | | Addition of APN-Validity-Time AVP | 14.5.0 | +| 2017-06 | CT#76 | CP-171026 | 0615 | - | | AVP codes for 32.299 | 14.5.0 | +| 2017-09 | CT#77 | CP-172018 | 0616 | 1 | | Reliable Data Service Success cause | 14.6.0 | +| 2017-09 | CT#77 | CP-172018 | 0617 | 1 | | Reliable Data Service | 14.6.0 | +| 2017-09 | CT#77 | CP-172026 | 0618 | 1 | | Enhancements for NAPPS | 15.0.0 | +| 2017-12 | CT#78 | CP-173011 | 0625 | - | | AVP codes for TS 29.219, TS 29.212 and TS 29.214 | 15.1.0 | +| 2017-12 | CT#78 | CP-173033 | 0619 | 1 | | Suggested Network Configuration Request | 15.1.0 | +| 2017-12 | CT#78 | CP-173028 | 0620 | - | | Monitoring Event Report Status | 15.1.0 | +| 2017-12 | CT#78 | CP-173028 | 0626 | - | | AVP code for PLMN-ID-Requested in S6t | 15.1.0 | +| 2017-12 | CT#78 | CP-173032 | 0627 | - | | New AVP for PC5-tech for WLAN based ProSe Direct Discovery | 15.1.0 | +| 2018-03 | CT#79 | CP-180021 | 0628 | 1 | | Service Gap Time AVP | 15.2.0 | +| 2018-03 | CT#79 | CP-180020 | 0629 | 1 | | AVP codes for 32.299 | 15.2.0 | +| 2018-03 | CT#79 | CP-180025 | 0630 | - | | IMSI-Group-Id retrieval | 15.2.0 | +| 2018-06 | CT#80 | CP-181120 | 0631 | 1 | | Supported-Services and Supported-Monitoring-Events | 15.3.0 | +| 2018-06 | CT#80 | CP-181120 | 0632 | 1 | | New AVPs in TS 29.212 for eVoLP | 15.3.0 | +| 2018-06 | CT#80 | CP-181120 | 0633 | 1 | | Reserve Diameter codes for TS 29.561 | 15.3.0 | +| 2018-06 | CT#80 | CP-181120 | 0635 | - | | Application ID for Diameter Nta | 15.3.0 | +| 2018-06 | CT#80 | CP-181120 | 0636 | 1 | | AVP codes for TS 29.154 | 15.3.0 | +| 2018-06 | CT#80 | CP-181120 | 0637 | 1 | | New AVP for subscription for Aerial UE in 3GPP system | 15.3.0 | +| 2018-06 | CT#80 | CP-181120 | 0639 | 1 | | AVP codes for 32.299 | 15.3.0 | +| 2018-06 | CT#80 | CP-181124 | 0640 | 1 | | Subscription data for ciphering keys | 15.3.0 | +| 2018-06 | CT#80 | CP-181127 | 0634 | - | | AVP code for NIR-Flags | 15.3.0 | +| 2018-09 | CT#81 | CP-182080 | 0642 | - | | AVP code for TS 29.214 | 15.4.0 | +| 2018-09 | CT#81 | CP-182073 | 0643 | - | | AVP codes for TS 29.468 | 15.4.0 | +| 2018-09 | CT#81 | CP-182073 | 0644 | - | | Update tables due to N6 | 15.4.0 | +| 2018-09 | CT#81 | CP-182073 | 0645 | 1 | | Change of value type of Maximum Packet Loss Rate | 15.4.0 | +| 2018-09 | CT#81 | CP-182073 | 0646 | 1 | | Subscribed PTW length | 15.4.0 | +| 2018-09 | CT#81 | CP-182073 | 0647 | 1 | | Policy Update when UE suspends | 15.4.0 | +| 2018-09 | CT#81 | CP-182073 | 0648 | 1 | | Command Codes for Nta Diameter Application | 15.4.0 | +| 2018-09 | CT#81 | CP-182084 | 0649 | - | | Core Network Restrictions | 15.4.0 | +| 2018-09 | CT#81 | CP-182071 | 0651 | - | | DSR-Flag for eDRX-Cycle-Length | 15.4.0 | +| 2018-12 | CT#82 | CP-183092 | 0653 | 1 | | Interworking-5GS-Indicator AVP definition | 15.5.0 | +| 2018-12 | CT#82 | CP-183095 | 0652 | 1 | | Monitoring event report | 15.5.0 | +| 2018-12 | CT#82 | CP-183102 | 0654 | - | | Wrong AVP type in Access-Restriction-Data | 15.5.0 | +| 2018-12 | CT#82 | CP-183102 | 0655 | - | | NIDD group authorization | 15.5.0 | +| 2019-03 | CT#83 | CP-190036 | 0656 | 1 | | New AVP for MB2 | 15.6.0 | +| 2019-03 | CT#83 | CP-190036 | 0657 | 1 | | RTR-Flags | 15.6.0 | +| 2019-03 | CT#83 | CP-190037 | 0658 | 1 | | Handling of multiple external IDs for the same UE | 15.6.0 | +| 2019-09 | CT#85 | CP-192125 | 0662 | - | | Add P-CSCF subscription info to Restoration information | 16.0.0 | +| 2019-09 | CT#85 | CP-192122 | 0661 | 1 | | Event type PDN Connectivity Status | 16.0.0 | +| 2019-09 | CT#85 | CP-192122 | 0664 | - | | Ethernet PDN Type AVP | 16.0.0 | +| 2019-09 | CT#85 | CP-192121 | 0663 | 1 | | Communication pattern enhancement | 16.0.0 | +| 2019-12 | CT#86 | CP-193035 | 0669 | 1 | | UE Status Suspend | 16.1.0 | +| 2019-12 | CT#86 | CP-103038 | 0666 | 1 | | New Error Code for TS 29.336 | 16.1.0 | +| 2019-12 | CT#86 | CP-103038 | 0671 | - | | Subscribed ARPI AVP | 16.1.0 | +| 2019-12 | CT#86 | CP-103038 | 0672 | - | | Network Parameter Configuration Reporting AVP | 16.1.0 | +| 2019-12 | CT#86 | CP-103038 | 0673 | 2 | | New AVP defined in TS 29.214 for Callee-Information | 16.1.0 | +| 2019-12 | CT#86 | CP-193040 | 0667 | - | | S-CSCF restoration after registration timer expiry | 16.1.0 | +| 2019-12 | CT#86 | CP-193052 | 0665 | 1 | | Battery Indication for Communication pattern enhancement | 16.1.0 | +| 2020-03 | CT#87e | CP-200041 | 0676 | 1 | | AVP codes for 32.299 | 16.2.0 | +| 2020-03 | CT#87e | CP-200041 | 0678 | - | | New AVPs in TS 29.214 | 16.2.0 | +| 2020-03 | CT#87e | CP-200027 | 0677 | 3 | | Addition of AVP code for IAB-Node-Information AVP | 16.2.0 | +| 2020-03 | CT#87e | CP-200036 | 0679 | - | | Subscription data for NR V2X | 16.2.0 | +| 2020-03 | CT#87e | CP-200050 | 0680 | - | | Reachability Cause | 16.2.0 | +| 2020-06 | CT#88e | CP-201016 | 0685 | - | | SMSF Address | 16.3.0 | +| 2020-06 | CT#88e | CP-201049 | 0681 | - | | Authorized PLMNs and RATs for V2X | 16.3.0 | +| 2020-06 | CT#88e | CP-201049 | 0682 | - | | Subscribed PC5 QoS Parameters for NR V2X | 16.3.0 | +| 2020-09 | CT#89e | CP-202094 | 0687 | 1 | | AVP Codes for TS 29.214 | 16.4.0 | +| 2020-12 | CT#90e | CP-203032 | 0688 | - | | Extended Reference ID | 16.5.0 | +| 2021-03 | CT#90e | CP-210057 | 0689 | - | | Default APN for Ethernet PDN types | 16.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------|--------| +| 2021-09 | CT#93e | CP-212073 | 0690 | 1 | F | APN Rate Control Status | 16.7.0 | +| 2021-09 | CT#93e | CP-212037 | 0691 | 1 | B | New AVP Exclude-Identifiers | 17.0.0 | +| 2021-12 | CT#94e | CP-213128 | 0692 | 1 | F | AVP code for TS 29.468 | 17.1.0 | +| 2021-12 | CT#94e | CP-213110 | 0694 | 1 | B | New AVP Include-Identifiers | 17.1.0 | +| 2022-03 | CT#95e | CP-220052 | 0697 | 2 | B | Adding new Alternate-Digest AVPs | 17.2.0 | +| 2022-03 | CT#95e | CP-220054 | 0695 | - | B | Failed P-CSCF AVPs | 17.2.0 | +| 2022-12 | CT#98e | CP-223038 | 0702 | - | F | Experimental Result Codes for TS 29.273 | 18.0.0 | +| 2023-06 | CT#100 | CP-231039 | 0703 | - | B | Add SBI support indicator AVPs for S6c | 18.1.0 | +| 2023-09 | CT#101 | CP-232035 | 0705 | 1 | F | Add AMF-Instance-Id AVP | 18.2.0 | +| 2023-09 | CT#101 | CP-232055 | 0706 | - | B | AVP for MPS for WLAN | 18.2.0 | \ No newline at end of file diff --git a/marked/Rel-18/29_series/29231/raw.md b/marked/Rel-18/29_series/29231/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a9fc77f78cfbdf737015475b574f9bd6f7dfcc62 --- /dev/null +++ b/marked/Rel-18/29_series/29231/raw.md @@ -0,0 +1,758 @@ + + +# 3GPP TS 29.231 V18.0.0 (2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Application of SIP-I Protocols to Circuit Switched (CS) Core Network Architecture; Stage 3 (Release 18)** + +![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase font. Above the "e" is the text "Advanced Pro" in a smaller font. To the right of the "e" is a green signal icon consisting of three curved lines of increasing height. + +LTE Advanced Pro logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo. It features the letters "3GPP" in a stylized, bold font. The "3" and "G" are connected at the top. Below the "P" is a red signal icon consisting of three curved lines of increasing height. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 8 | +| 4 Protocols..... | 8 | +| 4.1 Introduction ..... | 8 | +| 4.2 Call control protocol (Nc interface) ..... | 9 | +| 4.3 Resource control protocol (G)MSC and MGW (Mc Interface) ..... | 9 | +| 4.4 Bearer Framing Protocol between MGWs (Nb interface) ..... | 10 | +| 4.5 Signalling Transport..... | 10 | +| 4.5.1 Call Control protocols ..... | 10 | +| 4.5.2 Resource control protocol (G)MSC and MGW (Mc Interface) ..... | 10 | +| 4.5.3 IP Transport between MGWs (Nb interface) ..... | 10 | +| 4.6 Payload Types ..... | 10 | +| 5 Amendments and Endorsements to Referenced Specifications ..... | 11 | +| 5.1 ITU-T Q.1912.5 (Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part) ..... | 11 | +| 5.2 IETF RFC 2046 (Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types)..... | 11 | +| 5.3 IETF RFC 4566 (SDP: Session Description Protocol) ..... | 11 | +| 5.4 IETF RFC 3966 (The tel URI for Telephone Numbers)..... | 12 | +| 5.5 IETF RFC 2976 (The SIP INFO method)..... | 12 | +| 5.6 IETF RFC 3204 (MIME media types for ISUP and QSIG Objects) ..... | 12 | +| 5.7 IETF RFC 3261(SIP: Session Initiation Protocol)..... | 12 | +| 5.8 IETF RFC 3262 (Reliability of Provisional Responses in the Session Initiation Protocol) ..... | 13 | +| 5.9 IETF RFC 3264 (An Offer/Answer Model with the Session Description Protocol) ..... | 13 | +| 5.9.1 Multicast Streams ..... | 13 | +| 5.9.2 3GPP Node Generating the Offer ..... | 13 | +| 5.9.3 3GPP Node Generating the Answer ..... | 13 | +| 5.9.4 3GPP Node as Offerer Processing of the Answer ..... | 13 | +| 5.9.5 Modifying the session..... | 14 | +| 5.9.6 Unspecified Connection Address ..... | 14 | +| 5.10 IETF RFC 3311 (The Session Initiation Protocol (SIP) UPDATE Method)..... | 14 | +| 5.11 IETF RFC 3312 (Integration of Resource Management and Session Initiation Protocol) ..... | 14 | +| 5.12 IETF RFC 3323 (A Privacy Mechanism for the Session Initiation Protocol) ..... | 14 | +| 5.13 IETF RFC 3325 (Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks) ..... | 15 | +| 5.14 IETF RFC 3326 (The Reason Header Field for the Session Initiation Protocol) ..... | 15 | +| 5.15 IETF RFC 4028 (Session Timers in the Session Initiation Protocol) ..... | 15 | +| 5.16 IETF RFC 4960 (Stream Control Transmission Protocol)..... | 15 | +| 5.17 Void..... | 15 | +| 5.18 IETF RFC 4168 (The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol) ..... | 15 | +| 5.19 IETF RFC 791 (Internet Protocol, Version 4)..... | 16 | +| 5.20 IETF RFC 2460 (Internet Protocol, Version 6)..... | 16 | +| 5.21 IETF RFC 4715 (The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI)..... | 16 | +| 5.22 IETF RFC 4320 (Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction) ..... | 16 | +| 5.23 IETF RFC 5079 (Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)) ..... | 16 | + +| | | | +|-------------------------------|-------------------------------------------------------------|-----------| +| 6 | 3GPP Extensions..... | 17 | +| 6.1 | Codec Negotiation..... | 17 | +| 6.1.1 | Encoding of 3GPP_OoBTC_Indicator..... | 17 | +| 6.1.2 | Encoding of SDP answer including 3GPP OoBTC Indicator ..... | 17 | +| 6.2 | MGW Identifier..... | 17 | +| 6.2.1 | Semantic and Usage of the MGW_Identifier ..... | 17 | +| 6.2.2 | Encoding of MGW_Identifier ..... | 17 | +| 6.2.3 | Procedures related to MGW_Identifier ..... | 18 | +| 6.3 | Additional MGW Ids..... | 18 | +| 6.3.1 | Semantic and Usage of the Additional_MGW_Ids ..... | 18 | +| 6.3.2 | Encoding of Additional_MGW_Ids ..... | 18 | +| 6.3.3 | Procedures related to Additional_MGW_Ids ..... | 18 | +| Annex A (informative): | IANA Registration of OoBTC Indicator ..... | 19 | +| A.1 | Introduction ..... | 19 | +| A.2 | Contact name, email address, and telephone number ..... | 19 | +| A.3 | Attribute Name (as it will appear in SDP) ..... | 19 | +| A.4 | Long-form Attribute Name in English ..... | 19 | +| A.5 | Type of Attribute..... | 19 | +| A.6 | Is Attribute Value subject to the Charset Attribute? ..... | 19 | +| A.7 | Purpose of the attribute ..... | 19 | +| A.8 | Appropriate Attribute Values for this Attribute ..... | 19 | +| Annex B (informative): | IANA Registration of MGW Identifier ..... | 20 | +| B.1 | Introduction ..... | 20 | +| B.2 | Contact name, email address, and telephone number ..... | 20 | +| B.3 | Attribute Name (as it will appear in SDP) ..... | 20 | +| B.4 | Long-form Attribute Name in English ..... | 20 | +| B.5 | Type of Attribute..... | 20 | +| B.6 | Is Attribute Value subject to the Charset Attribute? ..... | 20 | +| B.7 | Purpose of the attribute ..... | 20 | +| B.8 | Appropriate Attribute Values for this Attribute ..... | 20 | +| Annex C (informative): | IANA Registration of Additional MGW Ids..... | 21 | +| C.1 | Introduction ..... | 21 | +| C.2 | Contact name, email address, and telephone number ..... | 21 | +| C.3 | Attribute Name (as it will appear in SDP) ..... | 21 | +| C.4 | Long-form Attribute Name in English ..... | 21 | +| C.5 | Type of Attribute..... | 21 | +| C.6 | Is Attribute Value subject to the Charset Attribute? ..... | 21 | +| C.7 | Purpose of the attribute ..... | 21 | +| C.8 | Appropriate Attribute Values for this Attribute ..... | 21 | +| Annex D (informative): | Change history..... | 22 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document describes the protocols to be used when SIP-I is optionally used as call control protocol in a 3GPP CS core network on Nc interface, see 3GPP TS 23.231 [1]. The SIP-I protocol operates between (G)MSC servers. The SIP-I architecture consists of a number of protocols. The following types of protocols are described: call control protocol, resource control protocols and user plane protocol for this architecture. The architecture complies with the requirements imposed by 3GPP TS 23.231 [1] and TS 23.153 [2]. + +Interworking of SIP-I on Nc to external networks is described by TS 29.235 [3]. + +The present document is valid for a 3rd generation PLMN (UMTS) complying with Release 8 and later. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 23.231: "SIP-I based Circuit Switched Core Network ; Stage 2". +- [2] 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2". +- [3] 3GPP TS 29.235: "Interworking between the 3GPP CS domain with SIP-I as signalling protocol and other networks". +- [4] ITU-T Recommendation Q.1912.5: "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part". +- [5] IETF RFC 2046: "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types". +- [6] IETF RFC 3966: "The tel URI for Telephone Numbers". +- [7] IETF RFC 2976: "The SIP INFO method". +- [8] IETF RFC 3204: "MIME media types for ISUP and QSIG Objects". +- [9] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [10] IETF RFC 3262: "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)". +- [11] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)". +- [12] IETF RFC 3311: "The Session Initiation Protocol (SIP) UPDATE Method". +- [13] IETF RFC 3312: "Integration of Resource Management and Session Initiation Protocol (SIP)". +- [14] IETF RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)". +- [15] IETF RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks". +- [16] IETF RFC 3326: "The Reason Header Field for the Session Initiation Protocol (SIP)". +- [17] IETF RFC 4566: "SDP: Session Description Protocol". + +- [18] 3GPP TS 29.232: "Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3". +- [19] 3GPP TS 29.415: "Core network Nb data transport and transport signalling". +- [20] 3GPP TS 29.414: "Core Network Nb data transport and transport signalling". +- [21] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [22] IETF RFC 3389: "Real-time Transport Protocol (RTP) Payload for Comfort Noise". +- [23] IETF RFC 4733: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals". +- [24] IETF RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)". +- [25] IETF RFC 4960: "Stream Control Transmission Protocol". +- [26] Void +- [27] IETF RFC 4168: "The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)". +- [28] IETF RFC 5407: "Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP)". +- [29] IETF RFC 791: "Internet Protocol (IP)". +- [30] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6)". +- [31] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". +- [31] 3GPP TS 26.102: "Mandatory speech codec; Adaptive Multi-Rate (AMR) speech codec;Interface to Iu, Uu and Nb". +- [32] 3GPP TS 26.103: "Speech codec list for GSM and UMTS". +- [33] 3GPP TS 23.003: "Numbering, addressing and identification". +- [34] IETF RFC 4715: " The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI ". +- [35] IETF RFC 4320: "Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction". +- [36] IETF RFC 5079: "Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|-----------------------------------------------------| +| Nc | Interface between the(G)MSC servers. | +| Mc | Interface between the server and the media gateway. | +| Nb | Interface between media gateways (MGW). | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [21] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [21]. + +| | | +|-------|----------------------------------------| +| BCU | Bearer Control Unit | +| BICC | Bearer Independent Call Control | +| MGC | Media Gateway Controller | +| MIME | Multi-purpose Internet Mail Extensions | +| OoBTC | Out of Band Transcoder Control | + +# --- 4 Protocols + +## 4.1 Introduction + +Implementations providing any of the interfaces or protocols identified in the subclauses below shall implement the requirements of the specifications identified in those subclauses. + +## 4.2 Call control protocol (Nc interface) + +**Table 4.2.1: Call Control Protocol Specifications** + +| Identification | Protocol Name | Amendments and Endorsements to referenced specifications | Support | +|--------------------|-----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|-----------| +| Q.1912.5 [4] | Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part | See Clause 5.1 | Mandatory | +| IETF RFC 2046 [5] | Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types | See Clause 5.2 | Mandatory | +| IETF RFC 3966 [6] | URLs for Telephone Calls | See Clause 5.4 | Mandatory | +| IETF RFC 2976 [7] | The SIP INFO Method | See Clause 5.5 | Mandatory | +| IETF RFC 3204 [8] | MIME media types for ISUP and QSIG Objects | See Clause 5.6 | Mandatory | +| IETF RFC 3261 [9] | SIP: Session Initiation Protocol | See Clause 5.7 | Mandatory | +| IETF RFC 3262 [10] | Reliability of Provisional Responses in the Session Initiation Protocol (SIP) | See Clause 5.8 | Mandatory | +| IETF RFC 3264 [11] | An Offer/Answer Model with the Session Description Protocol (SDP) | See Clause 5.9 | Mandatory | +| IETF RFC 3311 [12] | The Session Initiation Protocol UPDATE Method | See Clause 5.10 | Mandatory | +| IETF RFC 3312 [13] | Integration of Resource Management and Session Initiation Protocol (SIP) | See Clause 5.11 | Mandatory | +| IETF RFC 3323 [14] | A Privacy Mechanism for the Session Initiation Protocol (SIP) | See Clause 5.12 | Mandatory | +| IETF RFC 3325 [15] | Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks | See Clause 5.13 | Mandatory | +| IETF RFC 3326 [16] | The Reason Header Field for the Session Initiation Protocol (SIP) | See Clause 5.14 | Mandatory | +| IETF RFC 4566 [17] | SDP: Session Description Protocol | See Clause 5.3 | Mandatory | +| IETF RFC 4028 [24] | Session Timers in the Session Initiation Protocol (SIP) | See Clause 5.15 | Optional | +| IETF RFC 4715 [34] | The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI | See Clause 5.21 | Optional | +| IETF RFC 4320 [35] | Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction | See Clause 5.22 | Mandatory | +| IETF RFC 5079 [36] | Rejecting Anonymous Requests in the Session Initiation Protocol (SIP) | See Clause 5.23 | Optional | + +## 4.3 Resource control protocol (G)MSC and MGW (Mc Interface) + +**Table 4.3.1: Resource Control Protocol Specifications** + +| Identification | Protocol Name | Amendments and Endorsements to referenced specifications | Support | +|--------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|----------------------------------------------------------|-----------| +| 3GPP TS 29.232. [18] | Media Gateway Controller (MGC) – Media Gateway (MGW) Interface; Stage 3 | None (NOTE) | Mandatory | +| NOTE: IPv4 (IETF RFC 791 [29]) shall be supported on the Mc interface. IPv6 (IETF RFC 2460 [30]) may be supported. | | | | + +## 4.4 Bearer Framing Protocol between MGWs (Nb interface) + +**Table 4.4.1: Framing Protocol Specifications** + +| Identification | Protocol Name | Amendments and Endorsements to referenced specifications | Support | +|------------------------------------------------|------------------------------------------------------|----------------------------------------------------------|-----------| +| IETF RFC 3550[31] | RTP: A Transport Protocol for Real-Time Applications | None | Mandatory | +| NOTE: Further specified by 3GPP TS 29.414 [20] | | | | + +## 4.5 Signalling Transport + +### 4.5.1 Call Control protocols + +**Table 4.5.1.1: Call Control Signalling Transport** + +| Identification | Protocol Name | Amendments and Endorsements to referenced specifications | Support | +|--------------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------|-----------| +| IETF RFC 791 [29] | Internet Protocol, Version 4 (IPv4) | See clause 5.19 | Mandatory | +| IETF RFC 2460 [30] | Internet Protocol, Version 6 (IPv6)" | See clause 5.20 | Optional | +| IETF RFC 4960 [25] | Stream Control Transmission Protocol | See clause 5.16 | Mandatory | +| IETF RFC 4168 [27] | The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP) | See clause 5.18 | Mandatory | + +### 4.5.2 Resource control protocol (G)MSC and MGW (Mc Interface) + +**Table 4.5.2.1: Resource Control Signalling Transport** + +| Identification | Protocol Name | Amendments and Endorsements to referenced specifications | Support | +|---------------------|------------------------------------------------------------------------|----------------------------------------------------------|-----------| +| 3GPP TS 29.232 [18] | Media Gateway Controller (MGC) – Media Gateway (MGW) Interface;Stage 3 | None | Mandatory | + +### 4.5.3 IP Transport between MGWs (Nb interface) + +**Table 4.5.3.1: Nb Interface Signalling Transport** + +| Identification | Protocol Name | Amendments and Endorsements to referenced specifications | Support | +|---------------------|---------------------------------------------------------|----------------------------------------------------------|-----------| +| 3GPP TS 29.414 [20] | Core Network Nb Data Transport and Transport Signalling | None | Mandatory | + +## 4.6 Payload Types + +The details of which payload types shall be supported for the SIP-I application are defined in 3GPP TS 26.102 [31] and the RTP attributes for each specific codecs are defined in 3GPP TS 26.103 [32]. + +# 5 Amendments and Endorsements to Referenced Specifications + +## 5.1 ITU-T Q.1912.5 (Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part) + +Only Profile C shall apply. + +## 5.2 IETF RFC 2046 (Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types) + +The "multipart" MIME type with the sub-type of "mixed" shall be supported as per IETF RFC 2046 [5] to allow exchange of multiple bodies in a single SIP message (e.g. initial INVITE message with ISUP IAM encapsulation and SDP bodies) between (G)MSC-Servers. Nested MIME message is not supported in the SIP-I based Nc interface. + +The following MIME types only shall be supported in the SIP-I based Nc interface: + +- The "application" MIME type as per IETF RFC 2046 [5] with the sub-type of "ISUP" as per IETF RFC 3204 [8] to allow exchange of ISUP encapsulation in SIP messages between (G)MSC-Servers. +- The "application" MIME type as per IETF RFC 2046 [5] with the sub-type of "SDP" as per IETF RFC 4566 [17] to allow exchange of SDP in SIP messages between (G)MSC-Servers. + +## 5.3 IETF RFC 4566 (SDP: Session Description Protocol) + +The following SDP properties are described for SIP-I call control procedures; use of SDP within H.248 MGW control protocol interface is described in the relevant profile specification, e.g. 3GPP TS 29.232 [18]. + +**Table 5.3.1: Support of SDP Fields** + +| field | Meaning | Support | Comments | +|------------|--------------------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| v | Protocol Version | Mandatory | The value shall be "v=0" | +| o | Origin | Mandatory | | +| s | Session Name | Mandatory | | +| c | Connection Data | Mandatory | | +| t | Timing | Mandatory | The value shall be "t=0 0" | +| a | Attributes | Conditional | See table 5.3.2. | +| m | Media Descriptions | Mandatory | | +| b=RS, b=RR | RTCP bandwidth modifiers | Conditional | A (G)MSC wishing to deactivate RTCP or using RTCP only to negotiate the use of RTP bearer multiplexing and RTP header compression (see 3GPP TS 29.414 [20]) shall set the RTCP bandwidth modifiers to zero.
If a (G)MSC receives SDP bandwidth modifiers for RTCP equal to zero, it should reply by setting its RTCP bandwidth using SDP bandwidth modifiers with values equal to zero. | + +NOTE: Fields not listed in the table may be ignored by the (G)MSC Server on receipt of the SDP. + +**Table 5.3.2: Support of Attributes** + +| attr | Meaning | Support | Comments | +|----------|----------------------------|-------------------------|------------------------------------------------------------------------------------------| +| rtpmap | RTP map | Conditional | Mandatory for dynamic payload type and optional for static payload type. | +| recvonly | Receive only | Mandatory | | +| sendrecv | Send and receive | Mandatory | | +| sendonly | Send only | Mandatory | | +| inactive | Inactive | Mandatory | | +| fmtp | format specific parameters | Conditional | It is dependent upon the payload type if format specific parameters are required or not. | +| maxptime | Maximum packet size in ms | See 3GPP TS 26.102 [31] | | +| ptime | Packetisation length | See 3GPP TS 26.102 [31] | | + +NOTE: Attributes not listed in the table may be ignored by the (G)MSC Server on receipt of the SDP. + +## 5.4 IETF RFC 3966 (The tel URI for Telephone Numbers) + +The Tel-URI, in both global and local telephone formats, shall be supported as defined in IETF RFC 3966 [6]. + +The "isub" parameter defined within IETF RFC 3966 [6] may be used to include the ISDN sub-address as may be required within the MSISDN. See 3GPP TS 23.003 [33]. When the "isub" parameter is present, the "isub-encoding" parameter defined within IETF RFC 4715 [34] shall be used to define the ISDN subaddress encoding type. The procedures specified within ITU-T Q.1912.5 [4] Annex B.5 for profile C shall be applied for Sub-addressing. + +## 5.5 IETF RFC 2976 (The SIP INFO method) + +The SIP INFO method shall be supported as per IETF RFC 2976 [7] to allow exchange of ISUP signalling between (G)MSC-Servers. The contents of the message body shall not be encrypted. The SIP INFO method shall not be used to carry any other kind of information, e.g. DTMF digits. + +## 5.6 IETF RFC 3204 (MIME media types for ISUP and QSIG Objects) + +Only ISUP Media Type is supported in the SIP-I based Nc interface, see ITU-T Q.1912.5 [4] Clause 5.4.1.2. + +The "version" parameter is used to signal the ISUP version, as per ITU-T Q.1912.5 [4], sub-clause 5.4.1.2. + +## 5.7 IETF RFC 3261(SIP: Session Initiation Protocol) + +SIP-I initial and any subsequent INVITEs shall always include SDP. + +3GPP SIP-I entities shall apply loose routing on SIP-I based Nc. + +SIP forking is not supported in the SIP-I Nc interface. + +Race conditions for call clearing should be solved as described in clause 3.1.2 of the IETF RFC 5407 [28]. + +Non-INVITE transaction shall be implemented as specified in subclause 5.22 of the present specification. + +## 5.8 IETF RFC 3262 (Reliability of Provisional Responses in the Session Initiation Protocol) + +IETF RFC 3262 [10] specifies an extension to SIP in order to provide reliable provisional response messages. As support for PRACK's is required for a SIP-I based Nc interface to support preconditions, the support of 100rel is mandatory for the 3GPP SIP-I profile on the Nc interface. + +Procedures in clauses 3 and 4 of IETF RFC 3262 [10] apply on the Nc interface according to the following rules: + +- A (G)MSC Server originating a SIP INVITE shall advertise its preference of provisional reliable responses via a SUPPORTED header containing the tag "100Rel". +- A (G)MSC Server receiving a SIP INVITE will receive a SUPPORTED header containing the tag "100rel" and shall include a REQUIRE header with tag "100rel" and RSeq header field when sending a response in the range 101-199. +- A (G)MSC Server receiving a response in the range 101-199 with a REQUIRE header present with tag "100rel" shall generate a PRACK request for this provisional response. + +Authentication procedures are not required to be supported for PRACK (and any other) messages. + +## 5.9 IETF RFC 3264 (An Offer/Answer Model with the Session Description Protocol) + +### 5.9.1 Multicast Streams + +Procedures in Clauses 5.2 and 6.2 of IETF RFC 3264 do not need to be supported. + +### 5.9.2 3GPP Node Generating the Offer + +Procedures in Clause 5.1 of IETF RFC 3264 apply with the following modifications: + +- An MSC-S initiating an offer with multiple speech codec payload types in one m-line shall apply the related procedures in Clause 9 of 3GPP TS 23.153 [2], in particular the following requirement from IETF RFC 3264 Clause 5.1 is overruled: + +*"Once the offerer has sent the offer, it MUST be prepared to receive media for any recvonly streams described by that offer. It MUST be prepared to send and receive media for any sendrecv streams in the offer, and send media for any sendonly streams in the offer (ofcourse, it cannot actually send until the peer provides an answerwith the needed address and port information)."* + +### 5.9.3 3GPP Node Generating the Answer + +Procedures in Clause 6 of IETF RFC 3264 apply with the following modifications: + +- If the 3GPP MSC-S terminating the codec negotiation supports multiple speech codec payload types it shall apply the related procedures in Clause 9 of 3GPP TS 23.153 [2]. It does not need to be prepared to receive media encoded by speech codec payload types within the answered Available Codec List (see Clause 6.1.1). + +### 5.9.4 3GPP Node as Offerer Processing of the Answer + +Procedures in Clause 7 of IETF RFC 3264 apply with the following modifications: + +- If the offering MSC supports multiple speech codecs and the MSC-S receives an answer with multiple speech codec payload types in one m-line, it shall apply the related procedures in Clause 9 of 3GPP TS 23.153 [2]. It does not need to be prepared to receive media encoded by speech codec payload types within the Available Codec List (see Clause 6.1.1) received in the answer. + +### 5.9.5 Modifying the session + +Procedures in Clause 8 of IETF RFC 3264 apply with the same modifications as described in Clauses 5.9.2, 5.9.3, and 5.9.4. + +### 5.9.6 Unspecified Connection Address + +The use of an "unspecified connection address" may be used during initial call establishment, for deferred MGW selection where no user plane connection has been seized by the Offerer. + +No further applications for the use of an "unspecified connection address" are defined in SIP-I on Nc. + +The "unspecified connection address" shall not be sent within a re-INVITE message. + +For IPv6 implementations the "unspecified connection address" shall be defined by a domain name within the ".invalid" DNS top-level domain. + +For IPv4 implementations if the "unspecified connection address" shall be defined by the IPv4 unspecified address (c= IN IP4 0.0.0.0). + +## 5.10 IETF RFC 3311 (The Session Initiation Protocol (SIP) UPDATE Method) + +The SIP UPDATE method shall be supported to allow updating of session parameters (media streams, codecs) during early and confirmed dialog, and allow the support of preconditions. + +The support of the UPDATE method shall be negotiated on SIP-I based Nc according to the following rules: + +- A (G)MSC Server originating a SIP INVITE request shall advertise its support of the UPDATE method via the ALLOW header listing the UPDATE method. +- A (G)MSC Server receiving a SIP INVITE request shall include an ALLOW header listing the UPDATE method when sending a response in the range 101-199. The MSC-S is then allowed to generate the UPDATE method, for the purpose of session modification during early dialog. In addition the MSC-S shall include an ALLOW header listing the UPDATE method when sending a 2xx final response. +- A (G)MSC Server receiving a response to a SIP INVITE request with an ALLOW header present listing the UPDATE method is then allowed to generate the UPDATE method. + +Authentication and Integrity protection procedures are not required to be supported for the UPDATE message. + +## 5.11 IETF RFC 3312 (Integration of Resource Management and Session Initiation Protocol) + +Precondition type QoS only shall be supported using the segmented status type (therefore end-to-end status type e.g. Clause 13.1 does not apply) and the strength-tag value "mandatory" for the local segment and the strength-tag value "optional" for the remote segment. Precondition tag may be included in either REQUIRE or SUPPORTED header; the use of the SUPPORTED header is a deviation from this RFC when the strength-tag contains a "mandatory" value. + +## 5.12 IETF RFC 3323 (A Privacy Mechanism for the Session Initiation Protocol) + +IETF RFC 3323 [14] provides privacy requirements and mechanisms for SIP. + +The Privacy header shall be supported to signal privacy of the P-Asserted-Identity and allow or restrict the presentation of the network asserted identity, as specified in 3GPP TS 23.231 [1]. The following privacy values may be used: header, none, critical, id. + +## 5.13 IETF RFC 3325 (Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks) + +IETF RFC 3325 [15] provides for the existence and trust of an asserted identity within a trust domain. It shall be supported on the SIP-I based Nc interface with the following modifications: + +- a (G)MSC Server shall consider that neighbouring (G)MSC Servers connected via a Nc interface are trusted; +- the P-Preferred-Identity header and related requirements shall not be used. + +## 5.14 IETF RFC 3326 (The Reason Header Field for the Session Initiation Protocol) + +The SIP Reason header provides a means of transporting SIP or ISUP/BICC cause value in the SIP message; this is especially useful in SIP message without encapsulated ISUP information. + +The SIP Reason header shall be supported as specified by IETF RFC 3326 [16] and by ITU-T Q.1912.5 [4] (as endorsed by sub-clause 5.1 of the present specification), with the following modifications: + +- a Reason header field containing a Q.850 cause value shall be added to the SIP CANCEL message sent by the (G)MSC Server if the value is known; if unknown, the Q.850 cause value 31 (normal unspecified) shall be sent. +- the header field shall not be protected by any integrity mechanism. + +## 5.15 IETF RFC 4028 (Session Timers in the Session Initiation Protocol) + +SIP session continuity may be supported through the use of SIP Session Timer as per IETF RFC 4028 [24] with the following amendments. + +- Clause 4 indicates that the minimum value of the *Session-Expires* header field should not be less than 30 minutes. Since the vast majority of mobile calls are significantly less than 30 minutes, it may be desirable to use a minimum *Session-Expires* of less than 30 minutes within the 3GPP CS core network. The RFC states that the value SHOULD NOT be less than 30 minutes. That statement is modified to "...MAY choose values of less than 30 minutes but greater than the absolute minimum of 90 seconds." +- Clause 8 "Proxy Behavior" is not applicable to MSC Servers. + +## 5.16 IETF RFC 4960 (Stream Control Transmission Protocol) + +See sub-clause 5.18. + +## 5.17 Void + +## 5.18 IETF RFC 4168 (The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol) + +SCTP shall be the transport protocol for a SIP-I based Nc interface as per IETF RFC 4168 [27]. + +Semi-permanent SCTP associations shall be established between peer 3GPP SIP-I entities, i.e. the SCTP associations shall remain up under normal circumstances. + +Local multi-homing should be supported. Remote multi-homing shall be supported. + +Multiple local SCTP endpoints may be supported. Multiple remote SCTP endpoints shall be supported. When multiple local or remote SCTP endpoints are configured, several simultaneous SCTP associations shall be supported between peer 3GPP SIP-I entities. + +Published IP addresses and ports for SCTP associations are supported as specified below: + +- The (G)MSC Server shall support SCTP association setup, where an SCTP association request is performed to a published IP address and port. +- The (G)MSC Server may initiate SCTP association requests from a local published IP address and port. +- The (G)MSC Server shall accept incoming SCTP association requests from remote published IP address and port. +- When two endpoints are configured for a specific SCTP association between two published IP addresses and ports, one endpoint shall be configured as "server" and the peer endpoint as the "client" with respect to SCTP association setup. + +NOTE: Published IP addresses or ports can be configured via O&M or they can be obtained through a DNS enquiry. + +Dynamically assigned ports for SCTP associations are supported as specified below: + +- The (G)MSC Server may initiate a SCTP association from an ephemeral (non-published) port. +- The (G)MSC Server shall accept incoming SCTP association requests from remote ephemeral (non-published) ports. + +## 5.19 IETF RFC 791 (Internet Protocol, Version 4) + +IPv4 (IETF RFC 791 [29]) shall be supported on the Nc interface. + +## 5.20 IETF RFC 2460 (Internet Protocol, Version 6) + +IPv6 (IETF RFC 2460 [30]) may be supported on the Nc interface. + +## 5.21 IETF RFC 4715 (The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI) + +The "isub-encoding" parameter defined within IETF RFC 4715 [yy] shall be present and include the ISDN subaddress encoding type when the "isub" parameter of the Tel-URI is present as defined in Clause 5.4. + +## 5.22 IETF RFC 4320 (Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction) + +The actions specified in clause 4 of the IETF RFC 4320 [35] shall be supported with following modifications: + +- Actions which are not applicable for SCTP transport are not required to be supported. +- Actions specified for proxy are not applicable to MSC-S. + +## 5.23 IETF RFC 5079 (Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)) + +The response code 433 (Anonymity Disallowed) defined by IETF RFC 5079 [36] shall be supported on SIP-I on Nc. + +# 6 3GPP Extensions + +## 6.1 Codec Negotiation + +### 6.1.1 Encoding of 3GPP\_OoBTC\_Indicator + +3GPP OoBTC Indicator shall be encoded as the following media-level SDP attribute with the following syntax (ABNF definition): + +3GPP\_OoBTC\_Indicator = "a=3gOoBTC" + +No attribute values to this SDP attribute are defined in the present Release. If attribute values for the attribute are received, they shall be ignored. + +The SDP offer and SDP answer signalling procedures for OoBTC Indicator are described in Clause 9 of 3GPP TS 23.153 [2]. + +**Editor's Note: The 3GPP\_OoBTC\_Indicator will be registered at IANA.** + +### 6.1.2 Encoding of SDP answer including 3GPP OoBTC Indicator + +If the 3GPP OoBTC Indicator is included in an SDP answer, the corresponding SDP m-line shall be encoded as follows: + +- The first codec in the m-line (indicated by RTP payload type) shall indicate the Selected Codec. +- Any subsequent codecs in the m-line (indicated by RTP payload type), which are not of "auxiliary" payload type (see next bullet), shall indicate the Available Codec List (ACL) +- Codecs of "auxiliary" payload type, i.e. RTP Telephony Event payload type (IETF RFC 4733 [23]) or the comfort noise codec (IETF RFC 3389 [22]), may be included as the last codecs in the m-line (indicated by RTP payload type). + +## 6.2 MGW Identifier + +### 6.2.1 Semantic and Usage of the MGW\_Identifier + +The MGW\_Identifier shall be used to encode a MGW Identity as used for the optional "optimised MGW selection" and "deferred MGW selection" procedures in Clauses 4.4.2 and 4.4.3 of TS 23.231 [3]. + +Additional MGW identities may be proposed in the Additional\_MGW\_IDs attribute (see subclause 6.3) for the deferred MGW selection procedure. + +The support of the MGW\_Identifier attribute is only required for a (G)MSC Server that supports at least one of the optional "optimised MGW selection" and "deferred MGW selection" procedures. + +### 6.2.2 Encoding of MGW\_Identifier + +The MGW Identifier shall be encoded as the following "session-level" value attribute with the following syntax (ABNF definition): + +MGW\_Identifier = "a=MGW\_Identifier: " + = Octet string containing any octet value except 0x00 (Nul), 0x0A (LF), and 0x0D (CR). +Values are to be interpreted as in ISO-10646 character set with UTF-8 encoding. + +NOTE: The sub-field may be encoded for example in the same manner as BCU-ID in BICC, i.e. 4 Octets for representing Network ID field and Local BCU-ID field. + + shall contain an operator-defined unique identifier for a MGW. + +Attribute values of the SDP MGW\_Identifier attribute shall not be subject to the SDP "charset" attribute. + +**Editor's Note:** The MGW\_Identifier will be registered at IANA. + +### 6.2.3 Procedures related to MGW\_Identifier + +Provided that the (G)MSC Server supports the MGW Identifier attribute, it shall apply the following procedures: + +- For the optimised MGW selection, the (G)MSC Server shall apply the MGW Identity related procedures in Clause 4.4.2 of TS 23.231 [3]. +- For the deferred MGW selection, the (G)MSC Server shall apply the MGW Identity related procedures in Clause 4.4.3 of TS 23.231 [3]. + +## 6.3 Additional MGW Ids + +### 6.3.1 Semantic and Usage of the Additional\_MGW\_Ids + +The Additional\_MGW\_Ids shall be used to encode a list of MGW Identities that may be proposed in addition to the MGW Identity signalled in the MGW\_Identifier (see subclause 6.2.1), as used for the optional "deferred MGW selection" procedure in clause 4.4.3 of 3GPP TS 23.231 [3]. + +The support of the Additional\_MGW\_Ids attribute is only required for a (G)MSC Server that supports the "deferred MGW selection" procedure. + +### 6.3.2 Encoding of Additional\_MGW\_Ids + +The Additional MGW Ids shall be encoded as the following "session-level" value attribute with the following syntax (ABNF definition): + +Additional\_MGW\_Ids = "a=Additional\_MGW\_Ids: , , ..." + + = *Octet string containing any octet value except 0x00 (Nul), 0x0A (LF), and 0x0D (CR). Values are to be interpreted as in ISO-10646 character set with UTF-8 encoding.* + +NOTE: The sub-field may be encoded for example in the same manner as BCU-ID in BICC, i.e. 4 Octets for representing Network ID field and Local BCU-ID field. + + shall contain an operator-defined unique identifier for a MGW. + +Attribute values of the SDP Additional\_MGW\_Ids attribute shall not be subject to the SDP "charset" attribute. + +**Editor's Note:** The Additional\_MGW\_Ids will be registered at IANA. + +### 6.3.3 Procedures related to Additional\_MGW\_Ids + +Provided that the (G)MSC Server supports the Additional MGW Ids attribute, it shall apply the following procedures: + +- For the deferred MGW selection, the (G)MSC Server shall apply the Deferred MGW Ids related procedures in clause 4.4.3 of TS 23.231 [3]. + +# --- Annex A (informative): IANA Registration of OoBTC Indicator + +## A.1 Introduction + +This Annex describes information required for the IANA registration of the OoBTC Indicator SDP attribute, as required according to Clause 8.2.4 of IETF RFC 4566 [17] + +## A.2 Contact name, email address, and telephone number + +3GPP Specifications Manager + +[3gppContact@etsi.org](mailto:3gppContact@etsi.org) + ++33 (0)492944200 + +## A.3 Attribute Name (as it will appear in SDP) + +3gOoBTC + +## A.4 Long-form Attribute Name in English + +3GPP Out-of-band Transcoder Control Indicator + +## A.5 Type of Attribute + +Media level + +## A.6 Is Attribute Value subject to the Charset Attribute? + +Not applicable, as no attribute values are defined. + +## A.7 Purpose of the attribute + +The semantics of the 3GPP OoBTC Indicator are defined in Clause 9.4 of 3GPP TS 23.153 [2]. + +## A.8 Appropriate Attribute Values for this Attribute + +No attribute values are defined. + +# --- Annex B (informative): IANA Registration of MGW Identifier + +## B.1 Introduction + +This Annex describes information required for the IANA registration of the MGW Identifier SDP attribute, as required according to Clause 8.2.4 of IETF RFC 4566 [17] + +## B.2 Contact name, email address, and telephone number + +3GPP Specifications Manager + +[3gppContact@etsi.org](mailto:3gppContact@etsi.org) + ++33 (0)492944200 + +## B.3 Attribute Name (as it will appear in SDP) + +MGW\_Identifier + +## B.4 Long-form Attribute Name in English + +Media GateWay Identifier + +## B.5 Type of Attribute + +Session level + +## B.6 Is Attribute Value subject to the Charset Attribute? + +No + +## B.7 Purpose of the attribute + +As defined in Clause 6.2.1 + +## B.8 Appropriate Attribute Values for this Attribute + +As defined in Clauses 6.2.2 and 6.2.3 + +# --- Annex C (informative): IANA Registration of Additional MGW Ids + +## C.1 Introduction + +This Annex describes information required for the IANA registration of the Additional MGW Ids SDP attribute, as required according to clause 8.2.4 of IETF RFC 4566 [17] + +## C.2 Contact name, email address, and telephone number + +3GPP Specifications Manager + +[3gppContact@etsi.org](mailto:3gppContact@etsi.org) + ++33 (0)492944200 + +## C.3 Attribute Name (as it will appear in SDP) + +Additional\_MGW\_Ids + +## C.4 Long-form Attribute Name in English + +Additional Media GateWay Identifiers + +## C.5 Type of Attribute + +Session level + +## C.6 Is Attribute Value subject to the Charset Attribute? + +No + +## C.7 Purpose of the attribute + +As defined in clause 6.3.1 + +## C.8 Appropriate Attribute Values for this Attribute + +As defined in clauses 6.3.2 and 6.3.3 \ No newline at end of file diff --git a/marked/Rel-18/29_series/29238/raw.md b/marked/Rel-18/29_series/29238/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a7c7f9c4abcd76cee5c5cfa6fdcd81b89dbb0b07 --- /dev/null +++ b/marked/Rel-18/29_series/29238/raw.md @@ -0,0 +1,2589 @@ + + +# 3GPP TS 29.238 V18.2.0 (2024-09) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interconnection Border Control Functions (IBCF) - Transition Gateway (TrGW) interface, Ix interface; Stage 3 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|---------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 5 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Symbols..... | 10 | +| 3.3 Abbreviations ..... | 10 | +| 4 Applicability..... | 11 | +| 4.1 Architecture ..... | 11 | +| 5 Profile Description ..... | 11 | +| 5.1 Profile Identification ..... | 11 | +| 5.2 Summary ..... | 12 | +| 5.3 Gateway Control Protocol Version ..... | 12 | +| 5.4 Connection model ..... | 13 | +| 5.5 Context attributes ..... | 13 | +| 5.6 Terminations..... | 13 | +| 5.6.1 Termination names ..... | 13 | +| 5.6.1.1 IP Termination ..... | 13 | +| 5.6.1.1.1 ABNF Coding Overview and prose specification..... | 13 | +| 5.6.1.1.2 ASN.1 Coding Overview and prose specification ..... | 14 | +| 5.6.2 Multiplexed terminations..... | 15 | +| 5.7 Descriptors ..... | 15 | +| 5.7.1 TerminationState Descriptor ..... | 15 | +| 5.7.2 Stream Descriptor..... | 16 | +| 5.7.2.0 General..... | 16 | +| 5.7.2.1 LocalControl Descriptor ..... | 16 | +| 5.7.3 Events descriptor ..... | 17 | +| 5.7.4 EventBuffer descriptor ..... | 18 | +| 5.7.5 Signals descriptor ..... | 18 | +| 5.7.6 DigitMap descriptor..... | 19 | +| 5.7.7 Statistics descriptor..... | 19 | +| 5.7.8 ObservedEvents descriptor..... | 20 | +| 5.7.9 Topology descriptor..... | 20 | +| 5.7.10 Error descriptor..... | 20 | +| 5.8 Command API..... | 22 | +| 5.8.1 Add ..... | 22 | +| 5.8.2 Modify ..... | 22 | +| 5.8.3 Subtract..... | 23 | +| 5.8.4 Move..... | 23 | +| 5.8.5 AuditValue ..... | 23 | +| 5.8.6 AuditCapabilities ..... | 24 | +| 5.8.7 Notify..... | 24 | +| 5.8.8 ServiceChange..... | 24 | +| 5.8.9 Manipulating and auditing context attributes ..... | 26 | +| 5.9 Generic command syntax and encoding..... | 26 | +| 5.10 Transactions ..... | 26 | +| 5.11 Messages ..... | 27 | +| 5.12 Transport ..... | 28 | +| 5.13 Security..... | 28 | +| 5.14 Packages..... | 29 | +| 5.14.1 Mandatory Packages..... | 29 | +| 5.14.2 Optional Packages ..... | 30 | + +| | | | +|-----------|---------------------------------------------------------------------------|----| +| 5.14.3 | Package usage information ..... | 31 | +| 5.14.3.1 | Generic (g) ..... | 31 | +| 5.14.3.2 | Base root (root) ..... | 32 | +| 5.14.3.3 | Differentiated Services (ds) ..... | 33 | +| 5.14.3.4 | Gate Management (gm) ..... | 34 | +| 5.14.3.5 | Traffic management (tman) ..... | 35 | +| 5.14.3.6 | Inactivity Timer (it) ..... | 36 | +| 5.14.3.7 | IP Domain Connection (ipdc) ..... | 36 | +| 5.14.3.8 | Media Gateway Overload Control Package (ocp) ..... | 37 | +| 5.14.3.9 | Hanging Termination Detection (hangterm) ..... | 37 | +| 5.14.3.10 | Media Gateway Resource Congestion handling Package (chp) ..... | 38 | +| 5.14.3.11 | IP Realm Availability (ipra) ..... | 38 | +| 5.14.3.12 | 3G Interface Type package (threegint) ..... | 39 | +| 5.14.3.13 | RTCP Handling Package (rtcph) ..... | 39 | +| 5.14.3.14 | Application Data Inactivity Detection (adid) ..... | 40 | +| 5.14.3.15 | Explicit Congestion Notification for RTP-over-UDP Support (ecnrous) ..... | 41 | +| 5.14.3.16 | MG Act-as STUN Server (mgastuns) ..... | 42 | +| 5.14.3.17 | Originate STUN Continuity Check (ostunce) ..... | 43 | +| 5.14.3.18 | MG located Bearer Level ALG (mgbalg) ..... | 44 | +| 5.14.3.19 | Enhanced Revised Offer/Answer SDP Support (eroas) ..... | 44 | +| 5.15 | Mandatory support of SDP and Annex C information elements ..... | 45 | +| 5.16 | Optional support of SDP and Annex C information elements ..... | 48 | +| 5.17 | Procedures ..... | 50 | +| 5.17.1 | Formats and Codes ..... | 50 | +| 5.17.2 | Call Related Procedures ..... | 54 | +| 5.17.2.1 | General ..... | 54 | +| 5.17.2.2 | Reserve TrGW Connection Point ..... | 54 | +| 5.17.2.3 | Configure TrGW Connection Point ..... | 57 | +| 5.17.2.4 | Reserve and Configure TrGW Connection Point ..... | 62 | +| 5.17.2.5 | Release TrGW Termination ..... | 67 | +| 5.17.2.6 | Termination Heartbeat Indication ..... | 67 | +| 5.17.2.7 | IP Bearer Released ..... | 68 | +| 5.17.2.8 | Media Inactivity Notification ..... | 68 | +| 5.17.2.9 | Change Through Connection ..... | 69 | +| 5.17.2.10 | ECN FailureIndication ..... | 69 | +| 5.17.2.11 | Change Flow Direction ..... | 70 | +| 5.17.2.12 | ICE Connectivity Check Result Notification ..... | 70 | +| 5.17.2.13 | ICE New Peer Reflexive Candidate Notification ..... | 71 | +| 5.17.3 | Non-Call Related Procedures ..... | 71 | +| 5.17.3.1 | General ..... | 71 | +| 5.17.3.2 | TrGW Out Of Service ..... | 72 | +| 5.17.3.3 | TrGW Communication Up ..... | 73 | +| 5.17.3.4 | TrGW Restoration ..... | 73 | +| 5.17.3.9 | IBCF Out of Service ..... | 76 | +| 5.17.3.10 | Audit Value ..... | 76 | +| 5.17.3.11 | Command Rejected ..... | 78 | +| 5.17.3.12 | TrGW Capability Change ..... | 78 | +| 5.17.3.13 | TrGW Resource Congestion Handling – Activate ..... | 78 | +| 5.17.3.14 | TrGW Resource Congestion Handling – Indication ..... | 79 | +| 5.17.3.15 | Inactivity Timeout – Activation ..... | 79 | +| 5.17.3.16 | Inactivity Timeout – Indication ..... | 80 | +| 5.17.3.17 | Realm Availability Change – Activation ..... | 80 | +| 5.17.3.18 | Realm Availability Change – Indication ..... | 81 | +| 5.17.3.19 | Termination Out Of Service ..... | 81 | + +| | | | +|-------------------------------|----------------------------------------------------|-----------| +| Annex A (informative): | Illustration of Gate/Pinhole Concept..... | 82 | +| A.1 | General..... | 82 | +| A.2 | Relationships between gates and H.248 Streams..... | 82 | +| Annex B (informative): | Void..... | 84 | +| Annex C (informative): | Change history..... | 85 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document describes the protocol to be used on the Interconnection Border Control Function (IBCF) – Transition Gateway (TrGW) interface and the CS-IBCF – CS-TrGW interface. The basis for this protocol is the H.248 protocol as specified in ITU-T. The Profile provides MG control function for IMS and CS Border Control. The IMS architecture is described in 3GPP TS 23.228 [2]. The underlying reference model and stage 2 information is described in Annex I of 3GPP TS 23.228 [2] and in 3GPP TS 29.162 [18]. The CS architecture is described in Annex A of 3GPP TS 29.235 [17]. + +This specification describes the application of H.248 Ix profile for both Ix and CS-Ix interfaces (see Figure 1.1 and Figure 1.2). Required extensions use the H.248 standard extension mechanism. In addition certain aspects of the base protocol H.248 are not needed for this interface and thus excluded by this profile. + +![Figure 1.1: Reference model for IMS Border Control Functions. The diagram illustrates the IMS network architecture. A legend defines dashed lines as 'Signalling' and solid lines as 'Bearer'. A UE connects to an IP-CAN. The IP-CAN has a bearer connection to a TrGW and a signalling connection to a P-CSCF. The P-CSCF connects via signalling (Mx interface) to an S-CSCF and an IBCF. The S-CSCF connects to DNS, HSS, I-CSCF, and IBCF (Mx interface). The I-CSCF connects to BGCF and IBCF (Mx interface). The IBCF contains IMS-ALG and THIG sub-functions and connects via an Ix interface to the TrGW. The IBCF and TrGW are enclosed in a dashed box labeled 'Border Control Functions'. The TrGW and IBCF connect to an 'Other IMS/SIP network'.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +Figure 1.1: Reference model for IMS Border Control Functions. The diagram illustrates the IMS network architecture. A legend defines dashed lines as 'Signalling' and solid lines as 'Bearer'. A UE connects to an IP-CAN. The IP-CAN has a bearer connection to a TrGW and a signalling connection to a P-CSCF. The P-CSCF connects via signalling (Mx interface) to an S-CSCF and an IBCF. The S-CSCF connects to DNS, HSS, I-CSCF, and IBCF (Mx interface). The I-CSCF connects to BGCF and IBCF (Mx interface). The IBCF contains IMS-ALG and THIG sub-functions and connects via an Ix interface to the TrGW. The IBCF and TrGW are enclosed in a dashed box labeled 'Border Control Functions'. The TrGW and IBCF connect to an 'Other IMS/SIP network'. + +**Figure 1.1: Reference model for IMS Border Control Functions** + +![Figure 1.2: Reference model for CS Border Control Functions. The diagram shows the CS network architecture. A legend defines dashed lines as 'Signalling' and solid lines as 'Bearer'. An IWU (Interworking Unit) has a SIP-I signalling connection to a CS-IBCF and an Mc interface connection to a UP-IWU. The UP-IWU has a bearer connection (Media/RTP/UDP/IP) to a CS-TrGW. The CS-IBCF contains ALG and THIG sub-functions and connects via a CS-Ix interface to the CS-TrGW. Both CS-IBCF and CS-TrGW are enclosed in a dashed box labeled 'border control logical functions'. These functions connect to a large oval representing the 'SIP-I based 3GPP CS domain/External SIP-I Network'.](573c8f9e728e343b6864e1070c14b8cf_img.jpg) + +Figure 1.2: Reference model for CS Border Control Functions. The diagram shows the CS network architecture. A legend defines dashed lines as 'Signalling' and solid lines as 'Bearer'. An IWU (Interworking Unit) has a SIP-I signalling connection to a CS-IBCF and an Mc interface connection to a UP-IWU. The UP-IWU has a bearer connection (Media/RTP/UDP/IP) to a CS-TrGW. The CS-IBCF contains ALG and THIG sub-functions and connects via a CS-Ix interface to the CS-TrGW. Both CS-IBCF and CS-TrGW are enclosed in a dashed box labeled 'border control logical functions'. These functions connect to a large oval representing the 'SIP-I based 3GPP CS domain/External SIP-I Network'. + +**Figure 1.2: Reference model for CS Border Control Functions** + +The reference model for the IBCF and the TrGW supporting the ATCF/ATGW function is shown in Figure 1.x below. + +![Figure 1.3: Reference model for IBCF/TrGW with ATCF/ATGW function. The diagram shows a UE connected to CS access and IP-CAN. CS access connects to an MSC Server and MGW. IP-CAN connects to the IMS network. The IMS network contains P-CSCF, S-CSCF, I-CSCF, and BGCF. DNS and HSS are connected to the IMS network. The IBCF (IMS-ALG (ATCF) and THIG) and TrGW (ATGW) are part of the Border Control Functions. The IBCF connects to the BGCF via an Ix interface. The TrGW connects to the Other IMS/SIP network. Red arrows indicate 'Access Transfer' from the MGW to the IBCF and from the IP-CAN to the TrGW. A legend indicates that dashed lines represent Signalling and solid lines represent Bearer.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +Figure 1.3: Reference model for IBCF/TrGW with ATCF/ATGW function. The diagram shows a UE connected to CS access and IP-CAN. CS access connects to an MSC Server and MGW. IP-CAN connects to the IMS network. The IMS network contains P-CSCF, S-CSCF, I-CSCF, and BGCF. DNS and HSS are connected to the IMS network. The IBCF (IMS-ALG (ATCF) and THIG) and TrGW (ATGW) are part of the Border Control Functions. The IBCF connects to the BGCF via an Ix interface. The TrGW connects to the Other IMS/SIP network. Red arrows indicate 'Access Transfer' from the MGW to the IBCF and from the IP-CAN to the TrGW. A legend indicates that dashed lines represent Signalling and solid lines represent Bearer. + +**Figure 1.3: Reference model for IBCF/TrGW with ATCF/ATGW function** + +See 3GPP TS 23.237 [38] clause 5.2 for a comprehensive description of the reference model. + +NOTE: The Ix profile is applied over both IMS and CS Ix interfaces. + +In the following text the terms IBCF and TrGW also include respectively the CS-IBCF and CS-TrGW functionalities. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [3] ITU-T Recommendation H.248.1 (2002): "Gateway Control Protocol: Version 2" including the Corrigendum 1 for Version 2 (03/04). +- [4] ETSI TS 183 018 V3.5.1(2009-07): "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". +- [5] ITU-T Recommendation H.248.57 (06/2008): "Gateway control protocol: RTP Control Protocol Package". +- [6] ITU-T Recommendation H.248.43 (06/2008): "Gateway control protocol: Gate Management and Gate Control packages". +- [7] IETF RFC 3605 (2003): "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)". +- [8] IETF RFC 4566 (2006): "SDP: Session Description Protocol". + +- [9] IETF RFC 4975 (2007): "The Message Session Relay Protocol (MSRP)". +- [10] IETF RFC 3551 (2003): "RTP Profile for Audio and Video Conferences with Minimal Control". +- [11] IETF RFC 4145 (2005): "TCP-Based Media Transport in the Session Description Protocol (SDP)". +- [12] ITU-T Recommendation H.248.52 (06/2008): "Gateway control protocol: QoS support packages ". +- [13] ITU-T Recommendation H.248.53 (06/2008) inclusive *Revision 1* (03/2009): "Gateway control protocol: Traffic management packages". +- [14] ITU-T Recommendation H.248.41 Amendment 1 (06/2008): "Gateway control protocol: IP domain connection package: IP Realm Availability Package". +- [15] ITU-T Recommendation H.248.36 (09/2005): "Gateway control protocol: Hanging Termination Detection package". +- [16] ITU-T Recommendation H.248.11 (11/2002): "Gateway control protocol: Media gateway overload control package". +Inclusive Corrigendum 1 (06/2008) to H.248.11 "Gateway control protocol: Media gateway overload control package: Clarifying MG-overload event relationship to ADD commands". +- [17] 3GPP TS 29.235: "Interworking between SIP-I based circuit-switched core network and other networks". +- [18] 3GPP TS 29.162: "Interworking between the IM CN subsystem and IP networks". +- [19] ITU-T Recommendation H.248.14 (03/2009): "Gateway control protocol: Inactivity timer package". +- [20] ITU-T Recommendation H.248.10 (07/2001): "Media gateway resource congestion handling package". +- [21] 3GPP TS 29.232: "Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3". +- [22] 3GPP TS 33.210: "Technical Specification Group Services and System Aspects; 3G Security; Network Domain Security; IP Network Layer Security". +- [23] ITU-T Recommendation V.152 (01/2005): "Procedures for supporting voice-band data over IP networks". +- [24] ITU-T Supplement 7 to ITU-T H-series Recommendations H.Sup7 (05/2008): "Gateway control protocol: Establishment procedures for the H.248 MGC-MG control association". +- [25] IETF RFC 5234 (2008): "Augmented BNF for Syntax Specifications: ABNF ". +- [26] IETF RFC 4960 (2007): "Stream control transmission protocol". +- [27] ITU-T Recommendation H.248.40 (01/2007): "Gateway control protocol: Application Data Inactivity Detection package". +- [28] ITU-T Recommendation X.690 (11/2008): "ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)". +- [29] IETF RFC 3556 (2003): "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". +- [30] IETF RFC 4585 (2006): "Extended RTP Profile for Real-time Transport Control Protocol (RTCP) - Based Feedback (RTP/AVPF)". +- [31] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction". +- [32] IETF RFC 2216 (1997): "Network Element Service Specification Template". + +- [33] IETF RFC 3711 (2004): "The Secure Real-time Transport Protocol (SRTP)". +- [34] IETF RFC 5124 (2008): "Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)". +- [35] IETF RFC 6679 (2012): "Explicit Congestion Notification (ECN) for RTP over UDP". +- [36] IETF RFC 3611 (2003): "RTP Control Protocol Extended Reports (RTCP XR)". +- [37] IETF RFC 3168 (2001): "The Addition of Explicit Congestion Notification (ECN) to IP". +- [38] 3GPP TS 23.237: "IP Multimedia subsystem (IMS) Service Continuity; Stage 2". +- [39] 3GPP TS 22.153: "Multimedia Priority Service". +- [40] ITU-T Recommendation H.248.82 (03/2013): "Gateway control protocol: Explicit Congestion Notification Support". +- [41] IETF RFC 5285: "A General Mechanism for RTP Header Extensions". +- [42] IETF RFC 6236: "Negotiation of Generic Image Attributes in the Session Description Protocol (SDP)". +- [43] Void. +- [44] ITU-T Recommendation H.248.50 (09/2010) Corrigendum 1 (02/12): "Gateway control protocol: NAT traversal toolkit packages". +- [45] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP". +- [46] ITU-T Recommendation H.248.78 (11/2015): "Gateway control protocol: Bearer-level message backhauling and application level gateway". +- [47] IETF RFC 4573: "MIME Type Registration for RTP Payload Format for H.224". +- [48] ITU-T Recommendation H.224 (01/2005): "A real time control protocol for simplex applications using the H.221 LSD/HSD/MLP channels". +- [49] ITU-T Recommendation H.281 (11/1994): "A far end camera control protocol for videoconferences using H.224". +- [50] IETF RFC 5939: "Session Description Protocol (SDP) Capability Negotiation". +- [51] ITU-T Recommendation H.248.80 (01/2014): "Gateway control protocol: Usage of the revised SDP offer/answer model with ITU-T H.248". +- [52] ITU-T Recommendation H.248.88 (01/2014): "Gateway control protocol: RTP topology dependent RTCP handling by ITU-T H.248 media gateways with IP terminations". +- [53] IETF RFC 5104: "Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)". +- [54] IETF RFC 7728: "RTP Stream Pause and Resume". +- [55] IETF RFC 8445: "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal". +- [56] IETF RFC 8839: "Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Address:** term used for "network address" (IP address) + +**CS-TrGW:** packet-to-packet gateway for user plane media traffic. The CS-TrGW performs both policy enforcement functions and NA(P)T functions under the control of the CS-IBCF + +**Port:** term used for "transport port" (L4 port). + +**TRANSCODING:** transcoding in general is the translation from one type of encoded media format to another different media format, e.g. G.711 A-law to $\mu$ -law or vice versa, G.729 to AMR with 4.75 rate. + +NOTE 1: The definition of "transcoding" is according clause 3.10/ITU-T Recommendation V.152 [23]. + +NOTE 2: Transcoding belongs to the category of "media aware" IP-to-IP interworking. + +**Transparent Forwarding:** media gateway packet forwarding behaviour with the characteristic of Lx-PDU integrity. This is a unidirectional characteristic of an Lx-PDU flow. + +NOTE 3: The definition is according clause 3.2.10 of ITU-T Recommendation H.248.88 [52]. + +NOTE 4: The semantic covers both traffic directions when applied on H.248 Streams (due to their inherent characteristic of bidirectionality). + +**Transport Address:** term used for the combination of a *Network Address* and a *Transport Port*. + +**TrGW:** packet-to-packet gateway for user plane media traffic. The TrGW performs both policy enforcement functions and NA(P)T functions under the control of the IBCF + +NOTE 5: A Transition Gateway (TrGW) provides the interface between two IP-transport domains. The TrGW has the "H.248 MG" role in the scope of this Profile. + +For the purposes of the present document, the following terms and definitions as defined in 3GPP TS 29.162 [18] apply: + +**ICE lite** + +**Full ICE.** + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +Ix                      Interface between IBCF and TrGW or CS-IBCF and CS-TrGW. + +## 3.3 Abbreviations + +For the purposes of the present document the abbreviations defined in 3GPP TR 21.905 [1] apply, with the following additions. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|------|----------------------------------| +| ABNF | Augmented Backus-Naur Form | +| ATCF | Access Transfer Control Function | +| ATGW | Access Transfer Gateway | + +| | | +|-----------|------------------------------------------------------------------------------------------| +| B-ALG | Bearer Level Application-Level Gateway | +| BGF | Border Gateway Function | +| CCM | Codec Control Messages | +| CE | Congestion Experienced | +| CVO | Coordination of Video Orientation | +| DBI | Delay Budget Information | +| ECN | Explicit Congestion Notification | +| EVS | Enhanced Voice Services | +| FECC | Far End Camera Control | +| FIR | Full Intra Request | +| GCP | Gateway Control Protocol | +| IBCF | Interconnect Border Control Function | +| ICE | Interactive Connectivity Establishment | +| IVAS | Immersive Voice and Audio Services | +| LD | Local Descriptor (H.248 protocol element) | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MPS | Multimedia Priority Service | +| MSRP | Message Session Relay Protocol | +| NA | Not Applicable | +| NAPT | Network Address and Port Translation | +| NAPT-PT | NAPT and Protocol Translation | +| NAT | Network Address Translation | +| PCI | Protocol Control Information | +| RD | Remote Descriptor (H.248 protocol element) | +| ROI | Region of Interest | +| RTCP | RTP Control Protocol | +| SDP | Session Description Protocol | +| SDPCapNeg | SDP Capability Negotiation | +| SRVCC | Single Radio Voice Call Continuity | +| STUN | Session Traversal Utilities for NAT | +| TCP | Transmission Control Protocol | +| TMMBN | Temporary Maximum Media Stream Bit Rate Notification | +| TMMBR | Temporary Maximum Media Stream Bit Rate Request | +| ToS | Type-of-Service | +| TrGW | Transition Gateway | +| TISPAN | Telecommunications and Internet converged Services and Protocols for Advanced Networking | +| WebRTC | Web Real-Time Communication | + +# 4 Applicability + +The support of the IMS and CS Ix interfaces capability sets shall be identified by the H.248 Ix profile and support of this profile shall be indicated in H.248 ServiceChange procedure (during the (re-)registration phase(s)). + +## 4.1 Architecture + +See Annex I of 3GPP TS 23.228 [2], Annex A of 3GPP TS 29.235 [17] and 3GPP TS 29.162 [18]. + +# 5 Profile Description + +## 5.1 Profile Identification + +**Table 5.1.1: Profile Identification** + +| | | +|----------------------|-----------------| +| Profile name: | threeglx | +| Version: | 7 | + +## 5.2 Summary + +This profile supports the control of the following functionality in (IP-to-IP) Transition Gateways: + +- Allocation and translation of IP addresses and port numbers (NA(P)T and NA(P)T-PT); +- Hanging termination detection; +- IP realm/domain indication; +- Media inactivity detection; +- Opening and closing gates (i.e. packets filtering depending on "IP address / port"); +- Policing of incoming traffic; +- QoS packet marking for outgoing traffic (differentiated services); +- RTCP handling; +- Explicit Congestion Notification support; +- Multimedia Priority Service; +- application-aware MSRP interworking; +- application-agnostic upper layer protocol forwarding (such as for end-to-end WebRTC). + +and when ATCF/ATGW is supported: + +- Handover of bearer connections between PS and CS access networks; +- IP version interworking; +- Audio transcoding. + +In addition, optional settings and procedures are described which fulfil optional features. The minimum mandatory settings within the optional procedures and packages are identified that must be supported in order to support that feature. + +"Optional" or "O" means that it is optional for either the sender or the receiver to implement an element. If the receiving entity receives an optional element that it has not implemented it should send an Error Code (e.g. 445 "Unsupported or Unknown Property", 501 "Not Implemented", etc.). "Mandatory" or "M" means that it is mandatory for the receiver to implement an element. Whether it is mandatory for the sender to implement depends on specific functions; detail of whether elements of the core protocol are mandatory to be sent are defined in the stage 2 procedures, stage 3 procedures and/or the descriptions of individual packages. + +The setting or modification of elements described in the profile under the heading "Used in Command" has the meaning that the property can be set/modified with that command. The property may be present in other commands (in order to preserve its value in accordance with ITU-T Recommendation H.248.1 [3]) when those commands are used for other procedures that affect the same descriptor. + +## 5.3 Gateway Control Protocol Version + +Version 2 (ITU-T Recommendation H.248.1 [3]) shall be used as the minimum protocol version. + +## 5.4 Connection model + +**Table 5.4.1: Connection Model** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| +| Maximum number of contexts: | Provisioned | +| Maximum number of terminations per context: | 3 | +| Allowed termination type combinations in a context: | {(IP,IP) ;
{(IP,IP,IP) (NOTE)} | +| NOTE: This is only a temporary context configuration, occurring during bearer access transfer phase (between PS to CS access networks or vice versa) or during the reservation of two sets of transport addresses/resources towards the access network to support the functionalities related to the Alternate Connectivity functionality (see 3GPP TS 29.162 [18]). | | + +## 5.5 Context attributes + +**Table 5.5.1: Context Attributes** + +| Context Attribute | Supported | Values Supported | +|------------------------------------|-------------------|-------------------------| +| Topology | Yes (NOTE 1) | See clause 5.7.9 | +| Priority Indicator | Optional (NOTE 2) | 0-15 (NOTE 3) | +| Emergency Indicator | Yes | YES/NO | +| IEPS Indicator | No | NA | +| ContextAttribute Descriptor | No | NA | +| ContextIdList Parameter | No | NA | +| AND/OR Context Attribute | No | NA | + +NOTE 1: Stream ID in Topology Descriptor shall not be supported (because only used for SRVCC service support, which is a monomedia type of call ("voice call")). + +NOTE 2: This Context Attribute parameter is allowed in ETSI TISPAN Ia Profile version 3. It is also used for MPS as specified in 3GPP TS 22.153 [39]. + +NOTE 3: Priority values 11 – 15 of the Priority Indicator are reserved for MPS. + +## 5.6 Terminations + +### 5.6.1 Termination names + +#### 5.6.1.1 IP Termination + +##### 5.6.1.1.1 ABNF Coding Overview and prose specification + +The Termination ID structure shall follow the guidelines of H.248 and shall be based on four fields: + +- "ip///". + +The individual fields are described and defined in table 5.6.1.1.1.1. + +**Table 5.6.1.1.1.1: 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-65535) | Yes (NOTE 5) | Yes | +| Interface | Logical or physical interface to a network to/from which the termination will be sending/receiving media. (NOTE 1, NOTE 2). | String of max 51 alphanumeric characters | Yes (NOTE 4) | 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: 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 5: The CHOOSE wildcard on 'Group' is *not* allowed in ETSI TISPAN "Ia Profiles". + +NOTE: The IBCF has the ability to choose the address space in which the TrGW will allocate an IP address for the termination by using the *ipdc/realm* property defined in the ITU-T Recommendation H.248.41 [14] IP domain connection package. + +H.248 wildcarding may be applied on IP Termination Identifiers. Wildcarding is limited according the two columns on the right hand side. + +The corresponding ABNF grammar is given below: + +ABNF (IETF RFC 5234 [25]) is used for the syntax specification. The ABNF for TerminationID and relation to pathNAME is defined in Annex B.2 of ITU-T Recommendation H.248.1 [3]. + +###### **ABNF coding:** + +``` + +pathNAME = EphToken SLASH EPHsystem +EphToken = "ip" ; prefix +EPHsystem = WildcardALL + / WildcardALL SLASH Interface + / Group SLASH WildcardALL + / (Group / WildcardCHOOSE) SLASH (Interface / WildcardCHOOSE) SLASH (Identifier +/ WildcardALL / WildcardCHOOSE) +Group = %d0-65535 ; data type: INT16 +Interface = 1*51ALPHANUM +Identifier = %d1-4294967295 ; data type: INT32 +ALPHANUM = ALPHA / DIGIT +WildcardCHOOSE = "$" +WildcardALL = "*" + +``` + +##### 5.6.1.1.2 ASN.1 Coding Overview and prose specification + +The following general structure of termination ID shall be used: + +4 octets shall be used for the termination ID. The following defines the general structure for the termination ID: + +**Table 5.6.1.1.2.1: ASN.1 coding** + +| | | +|------------------|---| +| Termination type | X | +|------------------|---| + +Termination type: + +Length 3 bits + +Values: + +000 Reserved + +001 IP (Ephemeral) termination + +010 Reserved (in 3GPP Mc and Mn profile used for TDM termination) + +011 - 110 Reserved + +111 Reserved for ROOT termination Id (ROOT Termination ID = 0xFFFFFFFF) + +X: + +Length 29 bits. + +For IP termination, its usage is un-specified. + +### 5.6.2 Multiplexed terminations + +**Table 5.6.2.1: Multiplexed Terminations** + +| | | +|------------------------------------------|----| +| Multiplex Terminations Supported? | No | +|------------------------------------------|----| + +*If yes then:* + +**Table 5.6.2.2: Multiplex Types** + +| | | +|--------------------------------------------------------------|------| +| Multiplex Types Supported | None | +| Maximum Number of Terminations Connected to Multiplex | - | + +## 5.7 Descriptors + +### 5.7.1 TerminationState Descriptor + +**Table 5.7.1.1: ServiceState property** + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| ServiceState property used: | Yes (InService/OutOfService) NOTE 1, NOTE 2 | +| NOTE 1: This is restricted to the ROOT termination (for MGW audit). | | +| NOTE 2: Ephemeral H.248 Terminations have a ServiceState property according to ITU-T Recommendation H.248.1 [3], but explicit usage of the TerminationState Descriptor ServiceState property is not required by this Profile. ServiceState changes can still occur, however, and can be indicated in ServiceChange Commands (i.e. this means that the value of the ServiceState property may be implicitly changed by ServiceChange procedures). | | + +**Table 5.7.1.2: EventBufferControl property** + +| | | +|------------------------------------------|----| +| EventBufferControl property used: | No | +|------------------------------------------|----| + +**Table 5.7.1.3: SDPCapNeg Extensions property** + +| | | +|------------------------------------------------------------------------------------------------------------------------------------|-----| +| SDPCapNeg Extensions property used: | Yes | +| NOTE: The property is used in conjunction with the Enhanced Revised Offer/Answer SDP Support package, see clause 5.14.3.x1. | | + +### 5.7.2 Stream Descriptor + +#### 5.7.2.0 General + +**Table 5.7.2.1: Stream descriptor** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|--------------------| +| Maximum number of streams per termination type: | IP | Unspecified (NOTE) | +| NOTE: At least one stream for each media component (e.g. video+audio = 2 streams). If only one stream is applicable, then the IBCF may omit the Stream Descriptor and the TrGW shall assume that StreamID = 1. | | | + +**Table 5.7.2.2: Stream configuration** + +| | | +|------------------------------|--------------------------------| +| Stream Configuration: | ALL configurations are allowed | +|------------------------------|--------------------------------| + +#### 5.7.2.1 LocalControl Descriptor + +**Table 5.7.2.1.1: Reserve Group and Reserve Value** + +| | | Termination Type | Stream Type | +|----------------------------|-----|------------------|--------------| +| Reserve group used: | No | NA | NA | +| Reserve value used: | Yes | IP | Audio, Video | + +**Table 5.7.2.1.2: Stream Mode** + +| Termination Type | Stream Type | Allowed StreamMode Values | +|-----------------------------------------------------------------------------|-------------|----------------------------------------| +| IP | RTP/AVP | SendOnly, RecvOnly, SendRecv, Inactive | +| | RTP/SAVP | SendOnly, RecvOnly, SendRecv, Inactive | +| | RTP/AVPF | SendOnly, RecvOnly, SendRecv, Inactive | +| | RTP/SAVPF | SendOnly, RecvOnly, SendRecv, Inactive | +| | TCP | SendRecv, Inactive | +| | TCP/MSRP | SendRecv, Inactive | +| | udptl | SendRecv, Inactive | +| | udp | SendOnly, RecvOnly, SendRecv, Inactive | +| NOTE: See table 5.15.2 for the stream types applicable to IMS-Ix and CS-Ix. | | | + +### 5.7.3 Events descriptor + +**Table 5.7.3.1: Events Descriptor** + +| | | | | +|---------------------------------------------------------------|---------------------------------------------------------------------------------------|-------------------------|-----------------------------------| +| Events settable on termination types and stream types: | Yes | | | +| If yes | Event ID | Termination Type | Stream Type | +| | Cause (g/cause, 0x0001/0x0001) - See clause 5.14.3.1 | ALL except ROOT | ANY | +| | Inactivity Timeout (it/ito, 0x0045/0x0001) – See clause 5.14.3.6 | only ROOT | Not applicable | +| | MG_Overload (ocp/mg_overload, 0x0051/0x0001) – See clause 5.14.3.8 | only ROOT | Not applicable | +| | Termination Heartbeat (hangterm/thb, 0x0098/0x0001) – See clause 5.14.3.9 | ALL except ROOT | Not applicable | +| | MGCon (chp/mgcon, 0x0029/0x0001) – See clause 5.14.3.10 | only ROOT | Not applicable | +| | Available Realms Changed (ipra/arc, 0x00e0/0x0001) – See clause 5.14.3.11 | only ROOT | Not applicable | +| | IP Flow Stop Detection (adid/ipstop, 0x009c/0x0001) – See clause 5.14.3.14 | ALL except ROOT | ANY | +| | ECN Failure (ecnrous/fail, 0x010b/0x0001) – See clause 5.14.3.15 | IP | RTP Based | +| | ICE New Peer Reflexive Candidate (ostuncc/nprc, 0x00c3/0x0002) – see clause 5.14.3.17 | IP | Any, only applicable for full ICE | +| | ICE Connectivity Check Result (ostuncc/ccr, 0x00c3/0x0001) – see clause 5.14.3.17 | IP | Any, only applicable for full ICE | + +**Table 5.7.3.2: Event Buffer Control** + +| | | +|-----------------------------------|----| +| Event Buffer Control used: | No | +|-----------------------------------|----| + +**Table 5.7.3.3: Keep Active** + +| | | +|-----------------------------------|----| +| Keepactive used on events: | No | +|-----------------------------------|----| + +**Table 5.7.3.4: Embedding in event** + +| | | +|-------------------------------------------------|----| +| Embedded events in an event descriptor: | No | +| Embedded signals in an event descriptor: | No | + +**Table 5.7.3.5: Regulated Embedded Events** + +| | | +|----------------------------------------------------|------| +| Regulated Embedded events are triggered on: | None | +|----------------------------------------------------|------| + +**Table 5.7.3.6: Reset Events Descriptor Flag** + +| | | +|------------------------------------------------|------| +| ResetEventsDescriptor used with events: | None | +|------------------------------------------------|------| + +**Table 5.7.3.7: Notification Behaviour** + +| | | +|-------------------------|------------| +| NotifyImmediate: | ALL Events | +| NotifyRegulated: | None | +| NeverNotify: | None | + +NOTE: tables 5.7.3.4 – 5.7.3.7 apply to version 3 of ITU-T Recommendation H.248.1 [3]. + +### 5.7.4 EventBuffer descriptor + +**Table 5.7.4.1: Event Buffer** + +| | | +|--------------------------------------|-----------------| +| Event Buffer descriptor used: | No | +| If yes | EventIDs | + +### 5.7.5 Signals descriptor + +**Table 5.7.5.1: Signals dependant on termination or streams** + +| | | | | +|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------|-------------------------|-----------------------------------| +| The setting of signals is dependant on termination or streams types: | No
NOTE – "No" means that all signals can be played on any termination or stream. | | | +| If yes | Signal ID | Termination Type | Stream Type / ID | +| | Send Connectivity Check (ostuncc/scc, 0x00c3/0x0001) | IP | Any, only applicable for full ICE | +| | Send Additional Connectivity Check (ostuncc/sacc, 0x00c3/0x0002) | IP | Any, only applicable for full ICE | + +**Table 5.7.5.2: Signal Lists** + +| | | | +|---------------------------------|---------------------------------------------------|---| +| Signals Lists supported: | No | | +| If yes | Termination Type Supporting Lists | - | +| | Stream Type Supporting lists | - | +| | Maximum number of signals to a signal list | - | +| | Intersignal delay parameter supported: | - | + +**Table 5.7.5.3: Overriding Signal type and duration** + +| | | | +|--------------------------------------------|------------------|----------------------------------| +| Signal type and duration supported: | No | | +| If yes | Signal ID | Type or duration override | +| | - | - | + +Table 5.7.5.4: Signal Direction + +| | | +|------------------------------------|----| +| Signal Direction supported: | No | +|------------------------------------|----| + +Table 5.7.5.5: Notify completion + +| | | | +|------------------------------------|------------------|-------------------------------------| +| NotifyCompletion supported: | No | | +| If yes | Signal ID | Type of completion supported | +| | - | - | + +Table 5.7.5.6: RequestID Parameter + +| | | +|---------------------------------------|----| +| RequestID Parameter Supported: | No | +|---------------------------------------|----| + +Table 5.7.5.7: Signals played simultaneously + +| | | | +|---------------------------------------|-----------------------------------------------------|---| +| Signals played simultaneously: | No | | +| If yes | SignalIDs that can be played simultaneously: | - | +| | | | + +Table 5.7.5.8: Keep Active + +| | | +|------------------------------------|----| +| KeepActive used on signals: | No | +|------------------------------------|----| + +### 5.7.6 DigitMap descriptor + +Table 5.7.6.1: DigitMap Descriptor + +| | | | | +|-----------------------------|----------------------|------------------|---------------| +| DigitMaps supported: | No | | | +| If yes | DigitMap Name | Structure | Timers | +| | - | - | - | + +### 5.7.7 Statistics descriptor + +Table 5.7.7.1: Statistics Descriptor + +| | | +|---------------------------------|---| +| Statistics supported on: | - | +|---------------------------------|---| + +Table 5.7.7.2: Statistics reported on Subtract + +| | | | | +|-----------------------------------------|-------------------------------|-------------------------|--------------------| +| Statistics reported on Subtract: | No | | | +| If yes | Statistic IDs Reported | Termination Type | Stream Type | +| | - | - | - | + +### 5.7.8 ObservedEvents descriptor + +**Table 5.7.8.1: ObservedEvents Descriptor** + +| | | +|----------------------------------------|----| +| Event detection time supported: | No | +|----------------------------------------|----| + +### 5.7.9 Topology descriptor + +**Table 5.7.9.1: Topology descriptor** + +| | | +|------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Allowed triples: | (T1, T2, isolate)
(T1, T2, bothway) | +| NOTE: The Topology Descriptor shall be supported by the MGW and MGC for handover only, when PS-to-CS access transfer is supported. | | + +### 5.7.10 Error descriptor + +**Table 5.7.10.1: Error codes sent by the IBCF** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported H.248.8 Error Codes: | #400 "Syntax error in message"
#401 "Protocol Error"
#402 "Unauthorized"
#403 "Syntax Error in TransactionRequest"
#406 "Version Not Supported"
#410 "Incorrect identifier"
#411 "The transaction refers to an unknown ContextID"
#413 "Number of transactions in message exceeds maximum"
#421 "Unknown action or illegal combination of actions"
#422 "Syntax Error in Action"
#430 "Unknown TerminationID"
#431 "No TerminationID matched a wildcard"
#442 "Syntax Error in Command"
#443 "Unsupported or Unknown Command"
#444 "Unsupported or Unknown Descriptor"
#445 "Unsupported or Unknown property"
#446 "Unsupported or Unknown Parameter"
#447 "Descriptor not legal in this command"
#448 "Descriptor appears twice in a command"
#449 "Unsupported parameter or property value"
#450 "No such property in this package"
#451 "No such event in this package"
#454 "No such parameter value in this package"
#455 "Property illegal in this Descriptor"
#456 "Property appears twice in this Descriptor"
#457 "Missing parameter in signal or event"
#458 "Unexpected Event/RequestID"
#501 "Not Implemented"
#502 "Not ready"
#505 "Transaction Request Received before a ServiceChange Reply has been received"
#506 "Number of TransactionPendings Exceeded"
#533 "Response exceeds maximum transport PDU size" | +| Supported Error Codes defined in packages: | All error codes defined in supported packages are supported. | +| NOTE: the error codes listed need not be supplied by the IBCF to differentiate each and every error described by them. The TrGW shall be able to receive the error codes listed. | | + +**Table 5.7.10.2: Error codes sent by the TrGW** + +| | | +|------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported H.248.8 Error Codes: | #400 "Syntax error in message"
#401 "Protocol Error"
#402 "Unauthorized"
#403 "Syntax Error in TransactionRequest"
#406 "Version Not Supported"
#410 "Incorrect identifier"
#411 "The transaction refers to an unknown ContextID"
#412 "No ContextIDs available"
#413 "Number of transactions in message exceeds maximum"
#421 "Unknown action or illegal combination of actions"
#422 "Syntax Error in Action"
#430 "Unknown TerminationID"
#431 "No TerminationID matched a wildcard"
#432 "Out of TerminationIDs or No TerminationID available"
#433 "TerminationID is already in a Context"
#434 "Max number of Terminations in a Context exceeded"
#435 "Termination ID is not in specified Context"
#440 "Unsupported or unknown Package"
#441 "Missing Remote or Local Descriptor"
#442 "Syntax Error in Command"
#443 "Unsupported or Unknown Command"
#444 "Unsupported or Unknown Descriptor"
#445 "#Unsupported of Unknown property"
#446 "Unsupported or Unknown Parameter"
#447 "Descriptor not legal in this command"
#448 "Descriptor appears twice in a command"
#449 "Unsupported parameter or property value"
#450 "No such property in this package"
#451 "No such event in this package"
#452 "No such signal in this package"
#454 "No such parameter value in this package"
#455 "Property illegal in this Descriptor"
#456 "Property appears twice in this Descriptor"
#457 "Missing parameter in signal or event"
#471 "Implied Add for Multiplex failure"
#500 "Internal software Failure in MG or MGC"
#501 "Not Implemented"
#502 "Not ready"
#505 "Transaction Request Received before a ServiceChange Reply has been received"
#506 "Number of TransactionPendings Exceeded"
#510 "Insufficient resources"
#511 "Temporarily Busy"
#512 "Media Gateway unequipped to detect requested Event"
#513 "Media Gateway unequipped to generate requested Signals"
#515 "Unsupported Media Type"
#517 "Unsupported or invalid mode"
#522 "Functionality Requested in Topology Triple Not Supported"
#526 "Insufficient bandwidth"
#529 "Internal hardware failure in MG"
#530 "Temporary Network failure"
#531 "Permanent Network failure"
#532 "Audited Property, Statistic, Event or Signal does not exist"
#533 "Response exceeds maximum transport PDU size"
#534 "Illegal write of read only property"
#542 "Command is not allowed on this termination" | +| Supported Error Codes defined in packages: | All error codes defined in supported packages need to be supported. | +| NOTE: the error codes listed need not be supplied by the TrGW to differentiate each and every error described by | | + +them. The IBCF shall be able to receive the error codes listed. + +## 5.8 Command API + +### 5.8.1 Add + +**Table 5.8.1.1: Descriptors used by Add request** + +| | | +|-----------------------------------------|-------------------------------------------------------------| +| Descriptors used by Add request: | Media (Stream(LocalControl, Local, Remote)), Event, Signals | +|-----------------------------------------|-------------------------------------------------------------| + +**Table 5.8.1.2: Descriptors used by Add reply** + +| | | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Descriptors used by Add reply: |

Media (Stream (Local)), Error

When command request excludes an Audit Descriptor, the MGW response shall only include descriptors which contained underspecified or overspecified properties in the command request. Furthermore, only those properties that were underspecified or overspecified in the request shall be sent in the reply. Exceptions to this rule are:

  • - The Error Descriptor
  • - SDP properties returned in "Reserve TrGW Connection Point" and "Reserve and Configure TrGW Connection Point" procedures, as specified in 15.17.2.2 and 15.17.2.4
| +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.8.2 Modify + +**Table 5.8.2.1: Descriptors used by Modify request** + +| | | +|--------------------------------------------|--------------------------------------------------------------------------------| +| Descriptors used by Modify request: | Media (TerminationState, Stream (LocalControl, Local, Remote)), Signals, Event | +|--------------------------------------------|--------------------------------------------------------------------------------| + +**Table 5.8.2.2: Descriptors used by Modify reply** + +| | | +|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Descriptors used by Modify reply: |

Media (Stream(Local)), Error

When command request excludes an Audit Descriptor, the MGW response shall only include descriptors which contained underspecified or overspecified properties in the command request. Furthermore, only those properties that were underspecified or overspecified in the request shall be sent in the reply. Exceptions to this rule are:

  • - The Error Descriptor
  • - SDP properties returned in "Configure TrGW Connection Point" procedure as specified in 15.17.2.3.
| +|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.8.3 Subtract + +**Table 5.8.3.1: Descriptors used in Subtract request** + +| | | +|-------------------------------------------------------------|----------------------| +| Descriptors used by Subtract request: | None or Audit() NOTE | +| NOTE: this is to explicitly avoid reporting any statistics. | | + +**Table 5.8.3.2: Descriptors used in Subtract reply** + +| | | +|--------------------------------------------|-------------| +| Descriptors used by Subtract reply: | None, Error | +|--------------------------------------------|-------------| + +### 5.8.4 Move + +**Table 5.8.4.1: Command Move** + +| | | +|---------------------------|----| +| Move command used: | No | +|---------------------------|----| + +**Table 5.8.4.2: Descriptor used by Move command** + +| | | +|------------------------------------------|---| +| Descriptors used by Move Request: | - | +| Descriptors used by Move Reply: | - | + +### 5.8.5 AuditValue + +**Table 5.8.5.1: Descriptors used by AuditValue** + +| Audited Properties: | Property Name and Identity | Descriptor | +|--------------------------------|--------------------------------------------|-----------------------------| +| | Base root properties:
- root/* (ROOT) | TerminationState Descriptor | +| | TerminationState:
- Root (MGW Audit) | TerminationState Descriptor | +| | For Packages:
- Root | Packages Descriptor | +| | None (MGW Audit) :
- Root | Audit (empty) Descriptor | +| | IP Realm Availability :
- ipra/* (ROOT) | TerminationState Descriptor | +| | SDPCapNeg Extensions:
- sdpe/* | TerminationState Descriptor | +| Audited Statistics: | None | | +| Audited Signals: | None | | +| Audited Events: | None | | +| Package Audit possible: | Yes | | + +### 5.8.6 AuditCapabilities + +**Table 5.8.6.1: AuditCapabilities** + +| Audited Properties: | Property Name and Identity | Descriptor | +|----------------------------|-----------------------------------|-------------------| +| | None | - | +| Audited Statistics: | None | | +| Audited Signals: | None | | +| Audited Events: | None | | + +**Table 5.8.6.2: Scoped Auditing** + +| | | +|-------------------------------------------------------------------------|------| +| Audited Properties / ContextAttributes used for a scoped audit : | None | +|-------------------------------------------------------------------------|------| + +### 5.8.7 Notify + +**Table 5.8.7.1: Descriptors used by Notify** + +| | | +|--------------------------------------------|----------------| +| Descriptors used by Notify Request: | ObservedEvents | +| Descriptors used by Notify Reply: | None, Error | + +### 5.8.8 ServiceChange + +**Table 5.8.8.1: ServiceChangeMethods and ServiceChangeReasons sent by IBCF** + +| ServiceChangeMethods Supported: | ServiceChangeReasons supported: | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| Handoff (NOTE 2, NOTE 3) | "903 MGC Directed Change" (Optional, NOTE 4) | +| Restart (NOTE 2) | "901 Cold Boot" (Optional)
"902 Warm Boot" (Optional) | +| Forced (NOTE 2) | "905 Termination Taken Out Of Service" (Optional) | +| Graceful (NOTE 2) | "905 Termination Taken Out Of Service" (Optional) | +| NOTE 1: When a Service Change command on the Root termination with a method other than Graceful is sent, the command shall always be sent as the only command in a message. The sending node shall always wait for the reply to a Service Change command on the Root termination with a method other than Graceful before sending further command requests. A Service Change command on the Root termination with method Graceful may be combined with other commands in a single message. | | +| NOTE 2: ROOT Only. | | +| NOTE 3: Not involving more than 1 IBCF. This does not preclude the use of the MGCId in a ServiceChange (Handoff) scenario, nor does it change the expected TrGW behaviour upon receipt of such a message, as the TrGW has actually no means to differentiate whether the ServiceChangeMgcId parameter that may be received in a ServiceChange (handoff) message relates to a logical IBCF inside the same IBCF server or is part of another IBCF. | | +| NOTE 4: Support of this procedure is mandatory in the TrGW. | | + +**Table 5.8.8.2: Service Change Methods and Reason sent by TrGW** + +| Service Change Methods Supported: | ServiceChange Reasons supported: | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Forced | "904 Termination Malfunction", ALL except ROOT (Optional, NOTE 4)
"905 Termination Taken Out Of Service" , ALL(Mandatory)
"906 Loss Of Lower Layer Connectivity" , ALL except ROOT (Optional, NOTE 4)
"907 Transmission Failure" , ALL except ROOT (Optional, NOTE 4)
"908 MG Impending Failure" ROOT only (Mandatory)
"910 Media Capability Failure" , ALL except ROOT (Optional, NOTE 4)
"915 State Loss" ROOT only (Optional, NOTE 4) | +| Graceful | "905 Termination Taken Out Of Service" , (Optional, NOTE 4)
"908 MG Impending Failure" (Optional, NOTE 4) | +| Disconnected (NOTE 1) | "900 Service Restored" (Mandatory)
"916 Packages Change" (Optional)
"917 Capability Change" (Optional) | +| Restart (NOTE 1) | "900 Service Restored" (Mandatory)
"901 Cold Boot" (Mandatory)
"902 Warm Boot" (Mandatory)
"916 Packages Change" (Optional)
"917 Capability Change "(Optional) | +| Handoff (NOTE 1, NOTE 2) | "903 MGC Directed Change" (Mandatory) | +| NOTE 1: When a Service Change command on the Root termination with a method other than Graceful is sent, the command shall always be sent as the only command in a message. The sending node shall always wait for the reply to a Service Change command on the Root termination with a method other than Graceful before sending further command requests. A Service Change command on the Root termination with method Graceful may be combined with other commands in a single message.
NOTE 2: ROOT Only.
NOTE 3: In response to an IBCF Ordered Re-Register.
NOTE 4: Support of this procedure is mandatory in the IBCF. | | + +**Table 5.8.8.3: Service Change Address** + +| | | +|-----------------------------------|----| +| ServiceChangeAddress used: | No | +|-----------------------------------|----| + +**Table 5.8.8.4: Service Change Delay** + +| | | +|---------------------------------|-----------------------------| +| ServiceChangeDelay used: | No | +| If yes | Valid time period: - | + +**Table 5.8.8.5: Service Change Incomplete Flag** + +| | | +|--------------------------------------------|----| +| ServiceChange Incomplete Flag used: | No | +|--------------------------------------------|----| + +**Table 5.8.8.6: Service Change Version** + +| | | +|-------------------------------------------------------------------------------------|--------| +| Version used in ServiceChangeVersion: | 2 or 3 | +| NOTE: Version 2 shall be supported as the minimum protocol version. See clause 5.3. | | + +**Table 5.8.8.7: ServiceChangeProfile** + +| | | +|---------------------------------------------------------------------------------------------------|-----| +| ServiceChangeProfile mandatory: | Yes | +| NOTE: The ServiceChangeProfile is mandatory in the TrGW Register and TrGW Re-Register procedures. | | + +**Table 5.8.8.8: Profile negotiation** + +| | | +|---------------------------------------------|----| +| Profile negotiation as per H.248.18: | No | +|---------------------------------------------|----| + +**Table 5.8.8.9: ServiceChangeMGCId** + +| | | +|---------------------------------|-----| +| ServiceChangeMGCId used: | Yes | +|---------------------------------|-----| + +### 5.8.9 Manipulating and auditing context attributes + +**Table 5.8.9.1: Manipulating and Auditing Context Attributes** + +| | | +|----------------------------------------|-----------------------------------------| +| Context Attributes Manipulated: | Emergency Indicator, Priority Indicator | +| Context Attributes Audited: | None | + +## 5.9 Generic command syntax and encoding + +**Table 5.9.1: Command Encoding** + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| +| Supported Encodings: | Text (NOTE 1, NOTE 2, NOTE 3) and Binary. | +| NOTE 1: The receiver shall be capable of receiving both Short Token Notation and Long Token Notation on an H.248 control association. | | +| NOTE 2: The transmitter may select between long and short token forms per H.248 control association. | | +| NOTE 3: ETSI TISPAN "la Profile" [4] uses only text encoding. | | + +## 5.10 Transactions + +**Table 5.10.1: Transactions** + +| | | +|------------------------------------------------------------------------------------------------------------|-----------| +| Maximum number of Transaction Requests / Replies / TransResponseAcks / Segment Replies per message: | 10 (NOTE) | +| NOTE: ETSI TISPAN "la Profile" [4] maximum is "1", this is foreseen to be the typical case | | + +**Table 5.10.2: Commands per Transaction Request** + +| | | +|--------------------------------------------------------------------------------------------|--------------------| +| Maximum number of commands per Transaction request: | Unspecified (NOTE) | +| NOTE: ETSI TISPAN "la Profile" [4] maximum is "2", this is foreseen to be the typical case | | + +**Table 5.10.3: Commands per Transaction Reply** + +| | | +|--------------------------------------------------------------------------------------------|--------------------| +| Maximum number of commands per Transaction reply: | Unspecified (NOTE) | +| NOTE: ETSI TISPAN "la Profile" [4] maximum is "2", this is foreseen to be the typical case | | + +**Table 5.10.4: Optional Commands** + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| Commands able to be marked "Optional": | ALL | +| NOTE: The meaning of this table is that if one of the listed commands failed then the possibly present subsequent command within the same transaction will be processed. | | + +**Table 5.10.5: Commands marked for Wildcarded Responses** + +| | | +|---------------------------------------------------|----------| +| Wildcarded responses may be requested for: | Subtract | +|---------------------------------------------------|----------| + +**Table 5.10.6: Procedures for Wildcarded Responses** + +| | | +|----------------------------------------------------------|--------------------------| +| Procedures that make use of wildcarded responses: | Release TrGW Termination | +|----------------------------------------------------------|--------------------------| + +**Table 5.10.7: Transaction Timers** + +| Transaction Timer: | Value | +|------------------------------------------|--------------| +| NormalMGEExecutionTime | Provisioned | +| NormalMGCEExecutionTime | Provisioned | +| MGOriginatedPendingLimit | Provisioned | +| MGCOOriginatedPendingLimit | Provisioned | +| MGProvisionalResponseTimerValue | Provisioned | +| MGCPProvisionalResponseTimerValue | Provisioned | + +## 5.11 Messages + +It is recommended that TrGW and IBCF names are in the form of fully qualified domain name. For example the domain name of the IBCF may be of the form: "IBCF1.whatever.net." and the name of the TrGW may be of the form: "TrGW1.whatever.net." + +The fully qualified domain name will be used by the TrGW and IBCF as part of the "Message Identifier" in the H.248 messages which identifies the originator of the message. + +The IBCF domain name is provisioned in the TrGW or retrieved from the DNS using SRV records. + +The use of a domain name provides the following benefits: + +- TrGWs and IBCFs are identified by their domain name, not their network addresses. Several addresses can be associated with a domain name. If a command cannot be forwarded to one of the network addresses, implementations shall retry the transmission using another address. + +NOTE: There are then e.g. multiple numerical address entries per single MGC entity in the "MG database of MGC entries"; see Table 5 in ITU-T H.Sup7 [24]. + +- TrGWs and IBCFs may move to another platform. The association between a logical name (domain name) and the actual platform are kept in the Domain Name Service (DNS). TrGW and IBCF shall keep track of the record's time-to-live read from the DNS. They shall query the DNS to refresh the information if the time-to-live has expired. + +The domain name may be used by IBCF/TrGW for authentication purposes. + +## 5.12 Transport + +**Table 5.12.1: Transport** + +| | | +|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Transports: | 1. IPv4-based network control plane:
- SCTP/IPv4 (Recommended) NOTE1
- UDP/IPv4 (Optional)
2. IPv6-based network control plane:
- SCTP/IPv6 (Recommended) NOTE1
- UDP/IPv6 (Optional) | +| NOTE1: When using SCTP as defined in IETF RFC 4960 [26] the TrGW shall always be the node to perform the "Initiation". | | + +**Table 5.12.2: Segmentation** + +| | | +|--------------------------------|----------------------------------------| +| Segmentation Supported: | SCTP: Inherent in Transport
UDP: No | +|--------------------------------|----------------------------------------| + +**Table 5.12.3: Control Association** + +| | | +|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Control Association Monitoring Supported: | Monitoring mechanism is dependent on used H.248 transport (see above table 5.12.1):
SCTP:
inherent capability of SCTP.
UDP:
H.248.14 (MG-driven monitoring).
Empty AuditValue on ROOT (MGC-driven monitoring). | +|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 5.13 Security + +**Table 5.13.1: Security** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| Supported Security: | None | +| NOTE: IPsec shall not be used by the IBCF or TrGW for the Ix interface. Normally the Ix interface lies within a single operator's secure domain. If this is not the case then a Za interface (Security Gateway deploying IPsec) may be required, however this is a separate logical function/entity and thus is not applicable to the Ix profile, the IBCF or the TrGW; for further details see 3GPP TS 33.210 [22]. | | + +## 5.14 Packages + +### 5.14.1 Mandatory Packages + +**Table 5.14.1.1: Mandatory Packages** + +| Mandatory Packages | | | +|-----------------------------------------------------------------------------------------------------|--------------------|----------------| +| Package Name | Package ID | Version | +| Generic (ITU-T Recommendation H.248.1 [3], annex E.1) | g, (0x0001) | 1 | +| Base root (ITU-T Recommendation H.248.1 [3], annex E.2) | root, (0x0051) | 2 | +| RTP Control Protocol Package (ITU-T Recommendation H.248.57 [5]) | rtcph, (0x00b5) | 1 | +| Gate management Source Address/Port Filtering Package (ITU-T Recommendation H.248.43, Clause 7 [6]) | gm, (0x008c) | 2 | +| Traffic management (ITU-T Recommendation H.248.53 [13]) | tman, (0x008d) | 1 | +| IP Domain Connection (ITU-T Recommendation H.248.41 [14]) | ipdc, (0x009d) | 1 | +| Hanging Termination Detection (ITU-T Recommendation H.248.36 [15]) | hangterm, (0x0098) | 1 | +| Diffserv (ITU-T Recommendation H.248.52 [12]) | ds, (0x008b) | 2 | + +### 5.14.2 Optional Packages + +**Table 5.14.2.1: Optional Packages** + +| Optional Packages | | | | +|----------------------------------------------------------------------------------------------------|-------------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Package Name | Package ID | Version | Support dependent on | +| Inactivity Timer (ITU-T Recommendation H.248.14 [19]) | it, (0x0045) | 1 | MGC polling by MG.
Only applicable for UDP transport. | +| Media Gateway Overload Control (ITU-T Recommendation H.248.11 [16]) | ocp, (0x0051) | 1 | Support of message throttling, based on rate limitation, from MGC towards MG. | +| Media Gateway Resource Congestion Handling Package (see ITU-T Recommendation H.248.10 [20] ) | chp, (0x0029) | 1 | Support of message throttling, based on percentage limitation, from MGC towards MG. | +| IP realm availability (ITU-T Recommendation H.248.41 Amendment 1 [14]) | ipra (0x00e0) | 1 | Support of mechanisms allowing the MGC to discover the IP realms that are available at the MG at a certain time and allowing the MG to inform the MGC about any changes in the availability of realms. | +| 3G Interface Type package (see clause 15.2.11 of 3GPP TS 29.232 [21]) | threeint (0x00e3) | 1 | Indication of interface type for statistical purposes at the MG. | +| Application Data Inactivity Detection (ITU-T Recommendation H.248.40 [27]) | adid (0x009c) | 1 | MGC requires to be explicitly informed of a cessation of an application data flow. | +| Explicit Congestion Notification for RTP-over-UDP Support (ITU-T Recommendation H.248.82 see [40]) | ecnrous (0x010b) | 1 | Support of ECN feature | +| MG Act-as STUN Server (ITU-T Recommendation H.248.50 [44]) | mgastuns (0x00c2) | 1 | Support of incoming STUN connectivity checks.
Applicable for ICE lite and full ICE | +| Originate STUN Continuity Check (see ITU-T Recommendation H.248.50 [44]) | ostuncc (0x00c3) | 1 | Support of originating STUN connectivity checks.
Only applicable for full ICE | +| MG located Bearer Level ALG (ITU-T Recommendation H.248.78 [46]) | mgbalg (0x011d) | 1 | Support of a bearer level application gateway (B-ALG) function for application-aware MSRP interworking. | +| Enhanced Revised Offer/Answer SDP Support (ITU-T Recommendation H.248.80 [51]) | eroas, (0x0109) | 1 | Support of the SDP Capability Negotiation syntax | + +### 5.14.3 Package usage information + +#### 5.14.3.1 Generic (g) + +Table 5.14.3.1.1: 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, 0x0001/0x0001) | M | ADD, MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | General cause (Generalcause, 0x0001) | M | "NR" (0x0001)
Normal Release
"UR" (0x0002)
Unavailable Resources
"FT" (0x0003)
Failure, Temporary
"FP" (0x0004)
Failure, Permanent
"IW" (0x0005)
Interworking Error
"UN" (0x0006)
Unsupported | Not Applicable | | | +| Events | Failure cause (Failurecause, 0x0002) | O | Octet String | Not Applicable | | | +| | Mandatory/Optional | Used in command | | | | | +| Signal Completion. (g/sc, 0x0001/0x0002) | Not Used | - | | | | | +| | 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 | - | | | | | | + +#### 5.14.3.2 Base root (root) + +Table 5.14.3.2.1: Base root package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|--------------------------------------------------------------------------------------------|--------------------------|--------------------|------------------|----------------------------|--|--| +| MaxNrOfContexts
(root/maxNumberOfContexts, 0x0002/0x0001) | O | AUDITVALUE | ALL | YES | | | +| MaxTerminationsPerContext
(root/maxTerminationPerContext, 0x0002/0x0002) | O | AUDITVALUE | ALL | YES | | | +| normalMGExecutionTime
(root/normalMGExecutionTime, 0x0002/0x0003) | O | AUDITVALUE | ALL | YES | | | +| normalMGCEExecutionTime
(root/normalMGCEExecutionTime, 0x0002/0x0004) | O | AUDITVALUE | ALL | YES | | | +| MGProvisionalResponseTimerValue
(root/MGProvisionalResponseTimerValue, 0x0002/0x0005) | O | AUDITVALUE | ALL | YES | | | +| MGCProvisionalResponseTimerValue
(root/MGCProvisionalResponseTimerValue, 0x0002/0x0006) | O | AUDITVALUE | ALL | YES | | | +| MGCOriGINatedPendingLimit
(root/MGCOriGINatedPendingLimit, 0x0002/0x0007) | O | AUDITVALUE | ALL | YES | | | +| MGOrigiNatedPendingLimit
(root/MGOrigiNatedPendingLimit, 0x0002/0x0008) | O | 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 | - | | | | | | + +#### 5.14.3.3 Differentiated Services (ds) + +Table 5.14.3.3.1: Differentiated Services package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|-------------------------------------------------------------|---------------------------------|---------------------------|-------------------------|-----------------------------------|--|--| +| Differentiated Services Code Point (ds/dscp, 0x008b/0x0001) | M | ADD, MODIFY | ALL | Yes | | | +| Tagging Behaviour (ds/tb, 0x008b/0x0002) | 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 | | | +| None | - | - | - | - | | | +| | Statistics | Mandatory/Optional | Used in command | | | | +| | - | - | - | | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +#### 5.14.3.4 Gate Management (gm) + +Table 5.14.3.4.1: Gate Management Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|---------------------------------------------------------|--------------------------|--------------------|------------------|----------------------------|--|--| +| Remote Source Address Filtering (gm/saf,0x008c/0x0001) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Remote Source Address Mask (gm/sam,0x008c/0x0002) | O | ADD, MODIFY | ALL | Not Applicable | | | +| Remote Source Port Filtering (gm/spf,0x008c/0x0003) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Remote Source Port (gm/spr,0x008c/0x0004) | O | ADD, MODIFY | ALL | Not Applicable | | | +| Explicit Source Address Setting (gm/esas,0x008c/0x0005) | Not Supported | NONE | - | - | | | +| Local Source Address (gm/lsa,0x008c/0x0006) | Not Supported | NONE | - | - | | | +| Explicit Source Port Setting (gm/esps,0x008c/0x0007) | Not Supported | NONE | - | - | | | +| Local Source Port (gm/lsp,0x008c/0x0008) | Not Supported | NONE | - | - | | | +| Remote Source Port Range (gm/spr,0x008c/0x000A) | O | ADD, MODIFY | 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 | | | | +| Discarded Packets (gm/dp,0x008c/0x0001) | Not Supported | None | - | | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +NOTE : This package extends RTP Control Protocol package (ITU-T Recommendation H.248.57 [5]) and thus inherits RTCP Allocation Specific Behaviour property (rsb). + +#### 5.14.3.5 Traffic management (tman) + +Table 5.14.3.5.1: Traffic Management Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|-----------------------------------------------------|--------------------------|--------------------|------------------|----------------------------|--|--| +| Policing (tman/pol, 0x008d/0x0005) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Peak Data Rate (tman/pdr, 0x008d/0x0001) | O | ADD, MODIFY | ALL | Not Applicable | | | +| Delay Variation Tolerance (tman/dvt, 0x008d/0x0004) | O | ADD, MODIFY | ALL | ANY | | | +| Sustainable Data Rate (tman/sdr, 0x008d/0x0002) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Maximum burst size (tman/mbs, 0x008d/0x0003) | M | ADD, MODIFY | 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 | - | | | | | | + +NOTE: The data rate shall be calculated using the packet size from IP layer upwards. The Token Bucket method as described by ITU-T Recommendation H.248.53 [13] clause 9.4.3 (as per IETF RFC 2216 [32]) shall be followed where SDR = "r" and MBS = "b" (i.e. the additional "M" value does not apply). + +#### 5.14.3.6 Inactivity Timer (it) + +Table 5.14.3.6.1: 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 | +| | - | - | - | - | +| Events | Mandatory/Optional | Used in command | | | +| Inactivity Timeout (it/ito, 0x0045/0x0001) | M | MODIFY, NOTIFY | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | +| | Maximum Inactivity Time (mit, 0x0001) | 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 | - | | | | + +#### 5.14.3.7 IP Domain Connection (ipdc) + +Table 5.14.3.7.1: IP domain connection package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | +|-------------------------------------------------|---------------------------------|---------------------------|-------------------------|-----------------------------------| +| IP Realm Identifier (ipdc/realm, 0x009d/0x0001) | M | ADD, MODIFY (NOTE 2) | ALL (NOTE 1) | 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 1: If the MGC uses an *ipdc/realm* property exceeding the length limitation defined in ITU-T Recommendation H.248.41 [14], the MG shall reply with an error descriptor using error code #410: "Incorrect identifier". + +NOTE 2: The MODIFY command is listed due to the ETSI TISPAN "la profile" [4]: subsequent Streams may be "added" by MODIFY requests in case of multi-Stream-per-Termination structures. The subsequent Streams do then carry the same *ipdc/realm* property value as the very first Stream. + +#### 5.14.3.8 Media Gateway Overload Control Package (ocp) + +Table 5.14.3.8.1: 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,
0x0051/0x0001)
(NOTE 1) | M | MODIFY, NOTIFY (NOTE 1) | | | +| | 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 1 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 Recommendation H.248.11 [16] Corrigendum 1). +These two options result in different normalisations of the overload event rate as an indicator of the level of MG overload. + +#### 5.14.3.9 Hanging Termination Detection (hangterm) + +Table 5.14.3.9.1: 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
Heartbeat
(hangterm/thb,
0x0098/0x0001) | M | ADD, MODIFY, NOTIFY | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | +| | Timer X
(timerx, 0x0001) | M (NOTE1) | ALL (NOTE2) | YES | +| | ObservedEvent
Parameters | Mandatory/Optional | Supported Values | Provisioned Value | +| | - | - | - | - | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | +| None | - | - | - | - | +| Error Codes | Mandatory/Optional | | | | +| None | - | | | | + +NOTE1: Timer X is optional in the ETSI TISPAN Ia version 3 profile [4]. + +NOTE2: The heartbeat timer shall be configured to a value much greater than the mean call holding time. + +#### 5.14.3.10 Media Gateway Resource Congestion handling Package (chp) + +Table 5.14.3.10.1: Media Gateway Resource Congestion handling 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 | | | | | +| MGCon
(chp/mgcon,
0x0029/0x0001) | M | MODIFY, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | Reduction
(reduction,0x0001) | M | 0-100 | Not Applicable | | | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +#### 5.14.3.11 IP Realm Availability (ipra) + +Table 5.14.3.11.1: IP Realm Availability Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|-----------------------------------------------------------|-------------------------------------------|--------------------|-------------------|----------------------------|--|--| +| Available Realms,
(ipra/ar,
0x00e0/0x0001) | 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,
0x00e0/0x0001) | M | MODIFY, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | Newly Available Realms (nar,
0x0001) | M | ALL | Not applicable | | | +| | Newly Unavailable Realms (nur,
0x0002) | M | ALL | Not applicable | | | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +#### 5.14.3.12 3G Interface Type package (threegint) + +Table 5.14.3.12.1: 3G Interface Type Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|-------------------------------------------------------|--------------------------|--------------------|------------------------------------------------------------|----------------------------|--|--| +| IP Interface Type (threegint /ipint, (0x00e3/0x0001)) | M | ADD, MOD | "NboIP" (0x0001)
"MboIP" (0x0003)
"ExtSIPI" (0x0004) | 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 | - | - | | | | | +| | 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 | - | | | | | | + +#### 5.14.3.13 RTCP Handling Package (rtcph) + +Table 5.14.3.13.1: RTCP Handling Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|--------------------------------------------------------------|--------------------------|--------------------|------------------|----------------------------|--|--| +| RTCP Allocation Specific Behaviour (rtcph/rsb,0x00b5/0x0009) | M | ADD, MODIFY | ALL | OFF | | | +| 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 | - | | | | | | + +#### 5.14.3.14 Application Data Inactivity Detection (adid) + +Table 5.14.3.14.1: 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, 0x009c/0x0001) | M | ADD, MODIFY, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | Detection time (dt, 0x0001) | M | ALL | Yes | | | +| | Direction (dir, 0x002) | M | ALL | Yes | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command | Supported Values | | | | +| None | - | - | - | | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +#### 5.14.3.15 Explicit Congestion Notification for RTP-over-UDP Support (ecnrous) + +Table 5.14.3.15.1: Explicit Congestion Notification for RTP-over-UDP Support package + +| | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | +|----------------------------------------------------------------|----------------------------------|---------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| ECN Enabled (ecnrous/ecnen, 0x010b/0x0001) | M | ADD, MODIFY | True, False | - | +| Congestion Response Method (ecnrous/crm, 0x010b/0x0002) | O | ADD, MODIFY | "SDCC" (0x0001) (NOTE 2)
"RDCC" (0x0002) (NOTE 1) | "RDCC" (0x0002) | +| Initiation Method (ecnrous/initmethod, 0x010b/0x0003) | M | ADD, MODIFY | "rtp" (NOTE 2)
"leap",
"inactive" | "leap" | +| ECN Mode (ecnrous/mode, 0x010b/0x0004) | O | ADD, MODIFY | "setonly" (0x0001) (NOTE 2)
"readonly" (0x0002) (NOTE 2) | "setonly" (0x0001) in the Remote Descriptor and "readonly" (0x0002) in the Local Descriptor | +| ECT Marking (ecnrous/ectmark, 0x010b/0x0005) | O | ADD, MODIFY | "1" (0x0001) (NOTE 2)
"0" (0x0002)
"Random" (0x0003) (NOTE 2) | "0" (0x0002) | +| ECN Congestion Marking (ecnrous/congestmark, 0x010b/0x0006) | Not Signalled | - | - | "nomark" (0x0003) | +| ECN SDP Usage (ecnrous/ecnsdp, 0x010b/0x0007) | Not Signalled | - | - | "P" (0x0001) | +| 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 | | | +| ECN Failure (ecnrous/fail, 0x010b/0x0001) | M | ADD, MODIFY, NOTIFY | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | +| | - | - | - | - | +| | - | - | - | - | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | +| | Failure Type (type, 0x0001) | Mandatory | INIT, USE | - | +| | Media Sender SSRC (ssrc, 0x0002) | Not Supported | - | - | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | +| Source (ecnrous/ssrc, 0x010b/0x0001) | Not Supported | - | | - | +| CE Counter (ecnrous/cecount, 0x010b/0x0002) | Not Supported | - | | - | +| ECT0 Counter (ecnrous/ectzero, 0x010b/0x0003) | Not Supported | - | | - | +| ECT1 Counter (ecnrous/ectone, 0x010b/0x0004) | Not Supported | - | | - | +| Not-ECT Counter (ecnrous/notect, 0x010b/0x0005) | Not Supported | - | | - | +| Lost Packets Counter (ecnrous/lost, 0x010b/0x0006) | Not Supported | - | | - | +| Extended Highest Sequence number (ecnrous/ehsn, 0x010b/0x0007) | Not Supported | - | | - | + +| | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---|---|--|--|--| +| Duplication Counter (ecnrous/dup, 0x010b/0x0008) | Not Supported | - | - | | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | +| NOTE1: Application Specific Rate Adaptation shall be applied in accordance with 3GPP TS 26.114 [31]. For speech this requires support of CMR and TMMBR for video. | | | | | | | +| NOTE 2: This parameter is only supported for the termination towards the external IP network. | | | | | | | + +#### 5.14.3.16 MG Act-as STUN Server (mgastuns) + +Table 5.14.3.16.1: MG Act-as STUN Server + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|-----------------------------------------------------|---------------------------------|---------------------------|-------------------------|-----------------------------------|--|--| +| Act-as STUN Server (mgastuns/astuns, 0x00c2/0x0001) | M | ADD, MODIFY | ALL | - | | | +| 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 | - | | | | | | + +#### 5.14.3.17 Originate STUN Continuity Check (ostuncc) + +Table 5.14.3.17.1: Originate STUN Continuity Check Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | +|------------------------------------------------------------------|----------------------------------------|---------------------------|-----------------------------|-----------------------------------| +| Host Candidate Realm (ostuncc/hcr, 0x00c3/0x0001) | O | ADD, MODIFY | ALL | Yes | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | +| Send Connectivity Check (ostuncc/scc, 0x00c3/0x0001) | M | ADD, MODIFY | | Not Applicable | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | +| | Control (cntrl, 0x0001) | O | "controlling", "controlled" | Not Applicable | +| Send Additional Connectivity Check (ostuncc/sacc, 0x00c3/0x0002) | Mandatory/Optional | Used in command | | Duration Provisioned Value | +| | M | MODIFY | | Not Applicable | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | +| | Control (cntrl, 0x0001) | O | "controlling", "controlled" | Not Applicable | +| Events | Mandatory/Optional | Used in command | | | +| Connectivity Check Result (ostuncc/ccr, 0x00c3/0x0001) | M | ADD, MODIFY, NOTIFY | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | +| | - | - | - | - | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | +| | Candidate/Transport Pair (ctp, 0x0001) | M | ALL | Not applicable | +| New Peer Reflexive Candidate (ostuncc/nprc, 0x00c3/0x0002) | Mandatory/Optional | Used in command | | | +| | M | ADD, MODIFY, NOTIFY | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | +| | - | - | - | - | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | +| | Candidate (can, 0x0001) | M | ALL | Not applicable | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | +| None | - | - | | - | +| Error Codes | Mandatory/Optional | | | | +| None | - | | | | + +#### 5.14.3.18 MG located Bearer Level ALG (mgbalg) + +Table 5.14.3.18.1: MG located Bearer Level ALG package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|----------------------------------------------------------------------------------------|--------------------------|--------------------|------------------|----------------------------|--|--| +| Protocol type bearer level ALG (mgbalg/ptbalg, 0x011d/0x0001) | M | ADD, MODIFY | ALL | "OFF" | | | +| Upper layer protocol filter (mgbalg/ulpf, 0x011d/0x0002) | O (NOTE) | ADD, MODIFY | 0 | "0" | | | +| Source of replaced source address information part (mgbalg/sosaip, 0x011d/0x0003) | O (NOTE) | ADD, MODIFY | ALL | "SD" | | | +| Source of replaced destination address information part (mgbalg/sodaip, 0x011d/0x0004) | O (NOTE) | ADD, MODIFY | ALL | "SD" | | | +| 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: When B-ALG service configuration is provisioned in TrGW. + +#### 5.14.3.19 Enhanced Revised Offer/Answer SDP Support (eroas) + +Table 5.14.3.19.1: Enhanced Revised Offer/Answer SDP Support package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|--------------------------------------------------|--------------------------|--------------------|------------------|----------------------------|--|--| +| SDPCapNeg Extensions (eroas/sdpe, 0x0109/0x0001) | M | AuditValue | "cap-v0" | "cap-v0" | | | +| 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 | - | | | | | | + +## 5.15 Mandatory support of SDP and Annex C information elements + +Table 5.15.1: Mandatory Annex C and SDP information elements + +| Information Element | Annex C Support | SDP Support | +|---------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| v-line | "SDP_V " | The value must always be equal to zero: v=0 | +| c-line | "SDP_C " |

<nettype> <addrtype> and <connection address> are required.
The network type shall be set to "IN".
The address type may be IPv4 or IPv6.
The MGC may apply parameter underspecification to the <connection address> subfield.

| +| m-line | "SDP_M " |

There are four fields (or SDP values) <media>, <port>, <proto> and <fmt> in the "m=" line (see IETF RFC 4566 [8]; NOTE 1).
The "m=" line may be omitted from SDP.

<media>, <port>, <proto> and <fmt-list> are required if the "m=" line is included.

Media type <media> :
The <media> field shall be set to "audio" or "video" or "message" or "-", When "-" is used for the media value then no media resources are required to be reserved at this stage (NOTE 1). If the MG does not support the requested media value it shall reject the command with error code 515.

Transport port <port>
The port value may be underspecified with CHOOSE wildcard.

Transport protocol <proto>
As in table 5.15.2.

Media format <fmt>
Various values may be used for media-format, dependent on the related <media>.

"-" may be used for the format list value if no media reservation is required at this stage.

If the MG does not support the requested media format value the MG shall reject the command with error code 449.

| +| b-line | "SDP_B " |

Shall not be used without an "m=" line.

The modifier values shall be "AS", "RS" and "RR".
The "AS" modifier implies that the bandwidth-value represents the "maximum bandwidth" (see clause 5.8/IETF RFC 4566 [8]). The bandwidth-value relates therefore to the peak bitrate (NOTE 2).

The bandwidth-value value defines the IP layer bandwidth for the specific H.248 Stream.

For RTP flows, where RTCP resources are reserved together with the RTP resources using the "RTP Specific Behaviour" property of the Gate Management package (gm) property, the IBCF may also supply additional RTCP bandwidth modifiers (i.e. RR and RS, see IETF RFC 3556 [29]). The AS bandwidth value will include the bandwidth used by RTP. In the absence of the RTCP bandwidth modifiers, the TrGW shall allow an additional 5% of the AS bandwidth value for the bandwidth for RTCP, in accordance with IETF RFC 3556 [29].

| + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| o-line | "SDP_O" |

The origin line consists of six fields:
(<username>, <sess-id>, <sess-version>, <nettype>, <addrtype> and <unicast-address>).

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

The MG shall return the value received from the MGC or if there is no o-line sent by the MGC, the MG shall populate this line as follows:

  • - <user name> should contain an hyphen
  • - <session ID> and <version> should contain one or more digits as described in IETF RFC 4566 [8]
  • - <network type> shall be set to IN
  • - <address type> shall be set to IP4 or IP6 The Address Type shall be set to "IP4" or "IP6" depending on the addressing scheme used by the network to which the MG is connected.
  • - <address> should contain the fully qualified domain name or IP address of the gateway.
| +| s-line | "SDP_S" |

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

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

The MG shall return the value received from the MGC or if there is no s-line sent by the MGC, the MG shall populate this line as follows:

  • - "s=-"
| +| t-line | "SDP_T" |

The time "t=" line consists of two fields
t= <start time> and <stop time>.

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

The MG shall return the value received from the MGC or if there is no t-line sent by the MGC, the MG shall populate this line as follows:
"t=0 0"

| +|

NOTE 1: IETF RFC 4566 [8] enables "-" as a valid character (i.e. for both IMS-Ix and CS-Ix).

NOTE 2: The unit for the bandwidth-value (peak bitrate) is "kbit/s". The "b=" line is not providing any information about the traffic characteristic, i.e. whether the traffic flow has a Constant BitRate (CBR) or Variable BitRate (VBR). The bandwidth-value is thus independent of the traffic characteristic and relates to the peak bitrate for CBR and VBR traffic.

| | | + +Table 5.15.2: Transport Protocol + +| | | +|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transport Protocol <proto> in m-line: | If the MG does not support the requested transport protocol, it shall reject the command with error code 449. | +| RTP/AVP | RTP profile according IETF RFC 3551 [10]. Allow only L4 protocol = UDP (see NOTE 2) | +| RTP/AVPF | Extended RTP profile for RTCP-based Feedback (RTP/AVPF) according IETF RFC 4585 [30]. See 3GPP TS 26.114 [31]. Allow only L4 protocol = UDP (NOTE 2). | +| RTP/SAVP | SRTP profile according IETF RFC 3711 [33] (NOTE 4). Allow only L4 protocol = UDP (see NOTE 2) | +| RTP/SAVPF | Extended SRTP profile for RTCP-based Feedback (RTP/SAVPF) according IETF RFC 5124 [34] (NOTE 4). Allow only L4 protocol = UDP (see NOTE 2) | +| TCP | Allow only L4 protocol = TCP (NOTE 3) | +| TCP/MSRP | Message service using IETF RFC 4975 [9]. | +| udp | Allow only L4 protocol = UDP (NOTE 2, NOTE 5). | +| udptl | Allow only L4 protocol = UDP | + +- NOTE 1: For IMS-Ix the above transports are applicable but for CS-Ix only RTP/AVP, TCP and udptl are applicable. +- NOTE 2: Parameter "udp" is introduced by IETF RFC 4566 [8]. +- NOTE 3: Upper case TCP is defined by IETF RFC 4145 [11] and registered by IANA. . +- NOTE 4: Included for support of e2e security, in order to permit rtcph/rsb property to be applied. TrGW does not support associated SRTP/SRTCP stream handling per se. If either RTP/SAVP is signalled at any termination in a context, or if RTP/SAVPF is signalled at any termination in a context, the TrGW shall not terminate SRTP / SRTCP streams and therefore shall not reserve any associated resources, but shall pass media transparently, and shall also pass related RTCP streams (as indicated with the rtcph/rsb property) transparently (for end-to-end media security). +- NOTE 5: Codepoint used for e.g. "UDP payload transparent forwarding" (such as DTLS-encrypted end-to-end WebRTC bearer traffic). + +## 5.16 Optional support of SDP and Annex C information elements + +**Table 5.16.1: Optional SDP Information Elements** + +| Information Element | Annex C Support | SDP Support | +|---------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| a-line | "SDP_A " |

1) Application "RTCP transport address control":
The attribute "a=rtcp" line may either contain (a=rtcp: <port>) or (a=rtcp: <port> <network type> <address type> <connection address>) when the "a=" line is used for RTCP transport port and optionally network address transmission, see IETF RFC 3605 [7].
The MGC shall supply the "a=rtcp" line in the RD when non-default RTCP network address or transport port values are used by the peer media entity.
"RTCP transport address control" should be supported by MG.

2) Application " Media interworking (transcoding)":
The "a=" line provides the complementary information for the "m=" line with regards to a specified media type/format (e.g. an optional SDP „a=ptime" line for a particular media 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). For AVPF transport, the "rtcp-fb" SDP attribute defined in IETF RFC 4585 [30] may be used to provide the feedback message types the TrGW is allowed to send and to indicate RTCP timing information. For ECN interworking, the "rtcp-xr" SDP attribute defined in IETF RFC 3611 [36] may be used with "ecn-sum" value as defined in IETF RFC 6679 [35]. (NOTE)

3) Coordination of Video Orientation
The attribute "a=extmap" (see IETF RFC 5285 [41]) with CVO information may be provided for an m-line in the local and remote descriptor if the TrGW supports the extended RTP header with Coordination of Video Orientation information, see also 3GPP TS 26.114 [31].

4) Generic Image Attribute
The attribute "a=imageattr" (see IETF RFC 6236 [42]) may be provided for an m-line in the local and remote descriptor if the TrGW supports the generic image attributes, see also 3GPP TS 26.114 [31]. The local descriptor indicates the image sizes which the TrGW supports in the receiving direction for the selected payload type and corresponds to the "recv" keyword (see IETF RFC 6236 [42]) in the "a=imageattr" that the IBCF will send within the SDP body on the Mx interface. The remote descriptor indicates the image sizes which the TrGW supports in the sending direction for the selected payload type and corresponds to the "send" keyword (see IETF RFC 6236 [42]) in the "a=imageattr" that the IBCF will send within the SDP body on the Mx interface.

5) Interactive Connectivity Establishment support
The attributes "a=candidate", "a=ice-pwd", "a=ice-ufrag" and "a=ice-pacing" (see IETF RFC 8839 [56]) may be provided for an SDP m-line in the local and remote descriptor if the TrGW supports ICE, see also 3GPP TS 24.229 [45]. In the local descriptor, the IBCF shall provide "a=ice-pwd", and "a=ice-ufrag" with wildcard sign "\$" to request the allocation of a password and user name fragment, and the "a=candidate" of type "host" with the transport, port and priority parameters with wildcard sign "\$" to request the allocation of a host candidate, and "a=ice-pacing" with wildcard sign "\$" to request the desired pacing value for connectivity checks. The TrGW shall then reply with completed "a=ice-pwd", "a=ice-ufrag", "a=candidate" and "a=ice-pacing" attributes in the local descriptor, and shall include "a=ice-lite" if it only supports ICE lite. In the remote descriptor, the IBCF may provide the "a=candidate", "a=ice-pwd", "a=ice-ufrag" and "a=ice-pacing".

6) Handling of RTCP APP messages when transcoding between EVS and non EVS codecs, or between IVAS and non IVAS codecs:

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

The attribute "a=3gpp_mtsi_app_adapt" (see 3GPP TS 26.114 [31]) containing the allowed RTCP APP message types shall be provided when the TrGW is allowed to send RTCP APP messages.

7) Pre-defined Video Region-of-Interest (ROI):
The attribute "a=rtcp-fb" with the "Predefined ROI" type expressed by the parameter "3gpp-roi-predefined" may be provided for an m-line in the local and remote descriptor if the TrGW supports the Predefined ROI mode, see also 3GPP TS 26.114 [31]. In addition, the attribute "a=extmap" (see IETF RFC 5285 [41]) may be provided for an m-line in the local and remote descriptor if the TrGW supports the extended RTP header for carriage of predefined video Region of Interest (ROI) information in the sent video, see also 3GPP TS 26.114 [31].

8) Arbitrary Video Region of Interest (ROI):
The attribute "a=rtcp-fb" with the "Arbitrary ROI" type expressed by the parameter "3gpp-roi-arbitrary" may be provided for an m-line in the local and remote descriptor if the TrGW supports the Arbitrary ROI mode, see also 3GPP TS 26.114 [31]. In addition, the attribute "a=extmap" (see IETF RFC 5285 [41]) may be provided for an m-line in the local and remote descriptor if the TrGW supports the extended RTP header for carriage of arbitrary video Region of Interest (ROI) information in the sent video, see also 3GPP TS 26.114 [31].

9) SDP Capability Negotiation:
The attributes of "a=acap", "a=tcap", "a=pcfg" and "a=acfg" (see IETF RFC 5939 [50]) may be provided in the local descriptor and/or remote descriptor.

10) Rate adaptation for media endpoints:
If the TrGW performs media transcoding and if the rate adaptation for media endpoints using the enhanced bandwidth negotiation is supported by the TrGW, attribute(s) "a=bw-info" with direction "send" or "sendrecv" may be provided for an m-line and the selected IP payload type and applicable IP version in the remote descriptor.
The following bandwidth properties, as defined in 3GPP TS 26.114 [31], clause 19, may be included in "a=bw-info" line:
<payload type> <dir> <MaxSupBw>, <MaxDesBw>, <MinDesBw>, <MinSupBw> and <IpVer>.

11) "RTP-level pause and resume" signalling:
The "rtcp-fb" SDP attribute with the "ccm" feedback parameter and the "pause" ccm parameter as defined in IETF RFC 7728 [54] may be provided for an m-line in the local and remote descriptor to indicate that the TrGW shall forward RTCP feedback "CCM PAUSE-RESUME" messages transparently.

12) "RTCP Codec Control Commands and Indications" signalling:
The "rtcp-fb" SDP attribute with the "ccm" feedback parameter and the "fir" and/or "tmmbr" ccm parameters as defined in IETF RFC 5104 [53] may be provided for an m-line in the local and remote descriptor to indicate that the TrGW shall be prepared to receive and is allowed to send, respectively, the RTCP CCM feedback messages FIR, and/or TMMBR and TMMBN.

13) DBI signalling:
The "rtcp-fb" SDP attribute with the "3gpp-delay-budget" feedback parameter (as defined in 3GPP TS 26.114 [31] clause 6.2.8) may be provided for an m-line in the local and remote descriptor to indicate that the TrGW shall forward RTCP feedback messages for "DBI" signalling (as defined in 3GPP TS 26.114 [31] clause 7.3.8) transparently.

| +| NOTE: Media Interworking is optional for IMS-Ix and not required for CS-Ix. | | | + +## 5.17 Procedures + +### 5.17.1 Formats and Codes + +Table 5.17.1.1 shows the parameters which are required for the procedures defined in the following clauses. + +The coding rules applied in ITU-T Recommendation H.248.1 [3] for the applicable coding technique shall be followed for the UMTS capability set. + +The binary encoding rules which are applicable to the defined Abstract Syntaxes are the Basic Encoding Rules for Abstract Syntax Notation One, defined in ITU-T Recommendation X.690 [28]. Specifically in accordance with ITU-T Recommendation X.690 [28] clause 7.3, alternative encodings based on the definite and indefinite form of length are permitted by the basic encoding rules as a sender's option. Receivers shall support both alternatives. + +Unsupported values of parameters or properties may be reported by the TrGW and shall be supported by the IBCF as such by using H.248.1 error code #449 "Unsupported or Unknown Parameter or Property Value". The unsupported or unknown value is included in the error text in the error descriptor. + +**Table 5.17.1.1: Information Elements Used in Procedures** + +| Signalling Object | H.248 Descriptor | Coding | +|---------------------------------------------|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Additional Bandwidth Properties | Remote Descriptor | The "a=bw-info" SDP attribute defined in 3GPP TS 26.114 [31], see table 5.16.1. | +| Alternate MGC Id | ServiceChange | The MGCIIdToTry parameter in ITU-T Recommendation H.248.1 [3]. | +| Allowed RTCP APP message types | Remote Descriptor | The "a=3gpp_mtsi_app_adapt" SDP attribute defined in 3GPP TS 26.114 [31]. | +| Application-aware MSRP interworking request | LocalControl | This is the ptbalg property from ITU-T Recommendation H.248.78 [46] concerning the configuration of a B-ALG service (for MSRP traffic). | +| Arbitrary ROI | Local Descriptor or Remote Descriptor | The "rtcp-fb" SDP attribute defined in IETF RFC 4585 [30] to indicate the "Arbitrary ROI" RTCP feedback message expressed by the "3gpp-roi-arbitrary" parameter, as described in 3GPP TS 26.114 [31]. | +| Available Realms | Termination State | According to Available Realms property in ITU-T Recommendation H.248.41 [14]. | +| BNC Release | Events, ObservedEvents Descriptor | As for the Events/ObservedEvents Descriptor in clause E.1.2.1/ITU-T Recommendation H.248.1 [3] "Cause" | +| Cause | ObservedEvents Descriptor | As for the ObservedEventsDescriptor Parameter in clause E.1.2.1/ITU-T Recommendation H.248.1 [3] "General cause" | +| CCM BASE | Local Descriptor or Remote Descriptor | "rtcp-fb" SDP attribute (defined in IETF RFC 4585 [30]) with the "ccm" feedback parameter and the "fir" and/or "tmmbr" ccm parameters as defined in IETF RFC 5104 [53]. | +| CCM pause-resume | Local Descriptor or Remote Descriptor | "rtcp-fb" SDP attribute (defined in IETF RFC 4585 [30]) with the "ccm" feedback parameter (defined in IETF RFC 5104 [53]) and the "pause" ccm parameter as defined in IETF RFC 7728 [54]. | +| Changed Realms | Observed Events | According to Observed Events Parameters for Available Realms Changed event in ITU-T Recommendation H.248.41 [14]. | +| Codec List | Local Descriptor or Remote Descriptor | in a single SDP m-line.
For a static RTP payload type, the codec type should be implied by the RTP payload type, if not then each codec type shall be provided in a separate SDP "a=rtpmap"-line and possibly additional SDP "a=fmtp"-line(s).
For a dynamic RTP payload type, for each codec information on the codec type shall be provided in a separate SDP "a=rtpmap"-line and possibly additional SDP "a=fmtp"-line(s). | +| Connectivity Mode | Local Control | ITU-T Recommendation H.248.1 [3] Mode property.
Binary Encoding: Encoding as per ITU-T Recommendation H.248.1 Annex A [3] "streamMode"
Textual Encoding: Encoding as per ITU-T Recommendation H.248.1 Annex B [3]"streamMode". | +| Context ID | NA | Binary Encoding: As per ITU-T Recommendation H.248.1 [3] Annex A.
Textual Encoding: As per ITU-T Recommendation H.248.1 [3] Annex B. | +| DBI | Local Descriptor or Remote Descriptor | "rtcp-fb" SDP attribute defined in IETF RFC 4585 [30] with the "3gpp-delay-budget" feedback parameter (as defined in 3GPP TS 26.114 [31] clause 6.2.8). | +| Delay Variation Tolerance | Local Control | This is the tman/dvt property from ITU-T Recommendation H.248.53 [13] | +| Diffserv Code Point | Local Control | Defined according to the Differentiated Services Code Point property in ITU-T Recommendation H.248.52 [12]. | +| Diffserv Tagging Behaviour | Local Control | Defined according to the Tagging Behaviour property in ITU-T Recommendation H.248.52 [12]. | +| ECN Congestion Response | Local descriptor or Remote Descriptor | Defined according to "Congestion Response Method" property in ITU-T Recommendation H.248.82 [40]. (NOTE) | +| ECN ECT Marking | Local descriptor or Remote Descriptor | Defined according to "ECT Marking" property in ITU-T Recommendation H.248.82 [40]. (NOTE) | +| ECN Enabled | Local Descriptor or Remote Descriptor | Defined according to the "ECN Enabled" property in ITU-T Recommendation H.248.82 [40]. | +| ECN Failure | Events, Observed Events | Defined according to the "ECN Failure" Event in ITU-T Recommendation H.248.82 [40]. | +| ECN Failure Type | ObservedEvents Descriptor | As for the ObservedEventsDescriptor Parameter "Failure Type" in ITU-T Recommendation H.248.82 [40]. | + +| | | | +|----------------------------------------|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ECN Initiation Method | Local Descriptor or Remote Descriptor | Defined according to "Initiation Method" property in ITU-T Recommendation H.248.82 [40]. | +| ECN Mode | Local Descriptor or Remote Descriptor | Defined according to the "ECN Mode" property in ITU-T Recommendation H.248.82 [40].
(NOTE) | +| ECN RTCP Feedback | Local Descriptor or Remote Descriptor | "rtcp-fb" SDP attribute with the "nack" feedback parameter as defined in IETF RFC 4585 [30] and the "ecn" parameter value according to IETF RFC 6679 [35] | +| ECN XR Summary Report | Local Descriptor or Remote Descriptor | "ecn-sum" value as defined in IETF RFC 6679 [35] within a "rtcp-xr" SDP attribute in accordance with IETF RFC 3611 [36] | +| Emergency Call Indication | NA | ITU-T Recommendation H.248.1 [3] 6.1.1 Emergency Call Indicator
Binary Encoding: Encoding as per ITU-T Recommendation H.248.1 [3] Annex A "Emergency" context attribute
Textual Encoding: Encoding as per ITU-T Recommendation H.248.1 [3] Annex B "EmergencyToken" context attribute | +| Extended Header for CVO | Local Descriptor or Remote Descriptor | "extmap" attribute in SDP a-line as defined in IETF RFC 5285 [41], see table 5.16.1. | +| Extended RTP Header for Sent ROI | Local Descriptor or Remote Descriptor | "extmap" attribute in SDP a-line to pass on the ROI extended RTP header as defined by IETF RFC 5285 [41] for carriage of predefined and/or arbitrary ROI information, see 5.16 | +| Generic Image Attribute | Local Descriptor or Remote Descriptor | "imageattr" attribute in SDP a-line as defined in IETF RFC 6236 [42], see table 5.16.1. | +| ICE host candidate request | Local Descriptor | The "a=candidate" SDP attribute defined in IETF RFC 8839 [56] of type "host" with the transport, port and priority parameters with wildcard sign "\$" to request the allocation of a host candidate | +| ICE host candidate | Local Descriptor | The "a=candidate" SDP attribute defined in IETF RFC 8839 [56]. | +| ICE lite indication | Local Descriptor | The "a=ice-lite" SDP attribute defined in IETF RFC 8839 [56]. | +| ICE pacing | Local Descriptor | The "a=ice-pacing" SDP attribute defined in IETF RFC 8839 [56]. Only applicable for full ICE as specified in IETF RFC 8445 [55]. | +| ICE pacing request | Local Descriptor | The "a=ice-pacing" SDP attribute defined in IETF RFC 8839 [56] with wildcard sign "\$".
Only applicable for full ICE as specified in IETF RFC 8445 [55]. | +| ICE password request | Local Descriptor | The "a=ice-pwd" SDP attribute defined in IETF RFC 8839 [56] with wildcard sign "\$". | +| ICE password | Local Descriptor | The "a=ice-pwd" SDP attribute defined in IETF RFC 8839 [56]. | +| ICE received candidate | Remote Descriptor | The "a=candidate" SDP attribute defined in IETF RFC 8839 [56] | +| ICE received pacing | Remote Descriptor | The "a=ice-pacing" SDP attribute defined in IETF RFC 8839 [56]. Only applicable for full ICE as specified in IETF RFC 8445 [55]. | +| ICE received password | Remote Descriptor | The "a=ice-pwd" SDP attribute defined in IETF RFC 8839 [56]. | +| ICE received Ufrag | Remote Descriptor | The "a=ice-ufrag" SDP attribute defined in IETF RFC 8839 [56]. | +| ICE Ufrag request | Local Descriptor | The "a=ice-ufrag" SDP attribute defined in IETF RFC 8839 [56] with wildcard sign "\$". | +| ICE Ufrag | Local Descriptor | The "a=ice-ufrag" SDP attribute defined in IETF RFC 8839 [56]. | +| ICE Connectivity Check Result | Events, Observed Events | Defined according to Connectivity Check Result event in ITU-T Recommendation H.248.50 [44]. | +| ICE Send Connectivity Check | Signals | Defined as the ostuncc/scc signal in ITU-T Recommendation H.248.50 [44]. | +| ICE New Peer Reflexive Candidate | Events, Observed Events | Defined according to New Peer Reflexive Candidate event in ITU-T Recommendation H.248.50 [44], only applicable for full ICE. | +| ICE Send Additional Connectivity Check | Signals | Defined as the ostuncc/sacc signal in ITU-T Recommendation H.248.50 [44], only applicable for full ICE. | +| Inactivity Timeout | Events, Observed Events | Defined according to Inactivity Timeout event in ITU-T Recommendation H.248.14 [19]. | +| IP Address | Local Descriptor or Remote Descriptor | in SDP "c-line" | +| IP Interface | Local control | As for the property "IP interface type" in clause 15.2.11.1 in 3GPP TS 29.232 [21] | +| IP Realm Identifier | Local Control | According to IP Realm Identifier property in ITU-T Recommendation H.248.41 [14]. | +| IP Version | Local Descriptor or Remote Descriptor |
in SDP "c-line", see 5.15 | +| Maximum Burst Size | Local Control | This is the tman/mbs property from ITU-T Recommendation H.248.53 [13] | +| Media Inactivity Detection | Events, Observed Events | Defined according to IP Flow Stop Detection event in ITU-T Recommendation H.248.40 [27]. | +| Media Inactivity Detection Time | Events | As for the Event Parameter in ITU-T Recommendation H.248.40 [27] "Detection Time" | + +| | | | +|--------------------------------------|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Media Inactivity Detection Direction | Events | As for the Event Parameter in ITU-T Recommendation H.248.40 [27] "Direction" | +| Media Type | Local Descriptor or Remote Descriptor | in SDP m-line "audio", "video" or "-" | +| MSRP Path | Remote Descriptor | The "a=path" SDP attribute defined in IETF RFC 4975 [9]. | +| Overload Notification | Events, Observed Events | This is the chp/mgcon event from ITU-T Recommendation H.248.10 [20] or the ocp/mg_overload event from ITU-T Recommendation H.248.11 [16]. | +| Peak Data Rate | Local Control | This is the tman/pdr property from ITU-T Recommendation H.248.53 [13]. | +| Policing Required | Local Control | This is the tman/pol property from ITU-T Recommendation H.248.53 [13]. | +| Port | Local Descriptor or Remote Descriptor | in SDP m-line. | +| Predefined ROI | Local Descriptor or Remote Descriptor | The "rtcp-fb" SDP attribute defined in IETF RFC 4585 [30] to indicate the "Predefined ROI" RTCP feedback message expressed by the "3gpp-roi-predefined" parameter, as described in 3GPP TS 26.114 [31]. | +| Priority Information | NA | Priority Indicator (clause 6.1.1 of ITU-T Recommendation H.248.1 [3])
Binary Encoding: Encoding as per ITU-T Recommendation H.248.1 [3] Annex A "priority" context attribute
Textual Encoding: Encoding as per ITU-T Recommendation H.248.1 [3] Annex B "priority" context attribute | +| Realm Availability Change | Events, Observed Events | According to Available Realms Changed event in ITU-T Recommendation H.248.41 [14]. | +| Reduction | ObservedEvent Descriptor | As for the ObservedEventDescriptor in clause 4.2.1/ ITU-T Recommendation H.248.10 [20] "MGCongestion". | +| Remote Source Address Filtering | Local Control | Defined according to Remote Source Address Filtering property in ITU-T Recommendation H.248.43 [6]. | +| Remote Source Address Mask | Local Control | Defined according to Remote Source Address Mask property in ITU-T Recommendation H.248.43 [6]. | +| Remote Source Port Filtering | Local Control | Defined according to Remote Source Port Filtering property in ITU-T Recommendation H.248.43 [6]. | +| Remote Source Port | Local Control | Defined according to Remote Source Port property in ITU-T Recommendation H.248.43 [6]. | +| Remote Source Port Range | Local Control | Defined according to Remote Source Port Range property in ITU-T Recommendation H.248.43 [6]. | +| Reserve_Value | Local Control | ITU-T Recommendation H.248.1 [3] Reserve property.
Binary Encoding: Encoding as per ITU-T Recommendation H.248.1[3] Annex A "reserveValue"
Textual Encoding: Encoding as per ITU-T Recommendation H.248.1 [3] Annex B "reservedValueMode". | +| ROOT Properties | Termination State | The properties in clause E.2.1/ITU-T Recommendation H.248.1 [3] | +| RTCP allocation | Local Control | Defined according to RTCP Allocation Specific Behaviour property in ITU-T Recommendation H.248.57 [5]. | +| RtcpbwRR | Local Descriptor or Remote Descriptor | in SDP "b:RR"-line. see 5.15 | +| RtcpbwRS | Local Descriptor or Remote Descriptor | in SDP "b:RS"-line. see 5.15 | +| Rtpbw | Local Descriptor or Remote Descriptor | in SDP "b:AS"-line. see 5.15 | +| RTPpayload | Local Descriptor or Remote Descriptor | in SDP m-line. This may be set to CHOOSE (\$) in a LD sent from the IBCF toward the TrGW. | +| SDPCapNeg configuration | Local Descriptor or Remote Descriptor | The SDP attributes for SDP capability negotiation according to IETF RFC 5939 [50]. | +| SDPCapNeg Supported Capabilities | Termination State | Defined according to SDPCapNeg Extensions property in ITU-T Recommendation H.248.80 [51]. | +| Stream Number | Stream | Encoding as per ITU-T Recommendation H.248.1 [3]Annex B "Stream"/"ST".
For a single stream, this may be omitted by the CS-IBCF. | +| STUN server request | LocalControl | Encoding as per ITU-T Recommendation H.248.50 [44] "MG Act-as STUN Server" (mgastuns) package "Act-as STUN Server" (astuns, 0x0001) property. | +| Sustainable Data Rate | Local Control | This is the tman/sdr property from ITU-T Recommendation H.248.53 [13] | + +| | | | +|-----------------------|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| Termination heartbeat | Events ObservedEvents | As per Termination Heartbeat defined in ITU-T Recommendation H.248.36 [15] Clause 5.2.1. | +| Termination ID | NA | Binary Encoding: As per ITU-T Recommendation H.248.1 [3] Annex A.
Textual Encoding: As per ITU-T Recommendation H.248.1 [3] Annex B. | +| Transaction ID | NA | Binary Encoding: As per ITU-T Recommendation H.248.1 [3] Annex A.
Textual Encoding: As per ITU-T Recommendation H.248.1 [3] Annex B. | +| Transport | Local Descriptor or Remote Descriptor | in SDP m-line, see 5.15 | + +NOTE: This property is only signalled for IP terminations towards external IP network + +### 5.17.2 Call Related Procedures + +#### 5.17.2.1 General + +This clause describes the various call related procedures performed by the TrGW, which are listed in table 15.17.2.1.1 + +**Table 5.17.2.1.1: TrGW Call Related Procedures** + +| Transaction defined in 3GPP TS 29.235 [17] or 3GPP TS 29.162 [18] | Supported | Comment | +|-------------------------------------------------------------------|-----------|-----------------------------------------------------------| +| Reserve TrGW Connection Point | Mandatory | See 5.17.2.2 | +| Configure TrGW Connection Point | Mandatory | See 5.17.2.3 | +| Reserve and Configure TrGW Connection Point | Mandatory | See 5.17.2.4 | +| Release TrGW Termination | Mandatory | See 5.17.2.5 | +| Termination Heartbeat Indication | Mandatory | See 5.17.2.6 | +| IP Bearer Released | Mandatory | See 5.17.2.7 | +| Media Inactivity Notification | Optional | See 5.17.2.8 | +| Change Through Connection | Mandatory | See 5.17.2.9 | +| ECN Failure Indication | Optional | See 5.17.2.10 | +| Change Flow Direction | Optional | See 5.17.2.11 | +| ICE Connectivity Check Result Notification | Optional | See 5.17.2.12
Only applicable if full ICE is supported | +| ICE New Peer Reflexive Candidate Notification | Optional | See 5.17.2.13
Only applicable if full ICE is supported | + +#### 5.17.2.2 Reserve TrGW Connection Point + +The IBCF sends an ADD request command as in Table 5.17.2.2.1. + +**Table 5.17.2.2.1: Reserve TrGW Connection Point Request** + +| Address Information | Control information | Bearer information | +|--------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port = \$
IP Address = \$
IP Version = IPv4 or IPv6
} | Transaction ID = x
If Context Requested:
Context ID= \$
If Emergency Call:
Emergency Call Indication

If MPS call/session:
Priority Indicator = x

If Context Provided:
Context ID = c1

Termination ID = \$
If Stream Number specified:-
Stream Number
If Resources for multiple Codecs required:
Reserve_Value

If IP Interface Type:
IP interface = "IP interface type"

If indication on Bearer Released requested:
NotificationRequested (Event ID = x, "BNC Release ")

If diffserv required:-
Diffserv Code Point
If tagging behaviour
Diffserv Tagging Behaviour

If Remote Source Address Filtering required:-
Remote Source Address Filtering
If Remote Source Address range required:-
Remote Source Address Mask
If Remote Source Port Filtering required:-
Remote Source Port Filtering
If individual port:-
Remote Source Port
If range of ports:
Remote Source Port Range

NotificationRequested (Event ID = x, "termination heartbeat")

If multiple IP realms: IP realm
Identifier = required IP realm
identifier

If Media Inactivity Detection Required:
NotificationRequested (Event ID = x, "Media Inactivity Detection (Media Inactivity Detection Time, Media Inactivity Detection Direction) ") (NOTE 1)

If Sustainable Data Rate Policing Required:-
Policing Required
Sustainable Data Rate | Local Descriptor {
If media is "audio" or "video":
Codec List = Codec List
RTP Payloads = RTP Payload
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
If media is "video":
If CVO required:
Extended Header for CVO
(NOTE 4, NOTE 5)
If media is "video":
If imageattr negotiation:
Generic Image Attribute
(NOTE 6)
If Predefined ROI required:
RTCP feedback for Predefined ROI
Extended Header for Sent ROI
If Arbitrary ROI required:
RTCP feedback for Arbitrary ROI
Extended Header for Sent ROI

If ICE is applied:
ICE host candidate request
ICE password request
ICE Ufrag request
ICE pacing request

If SDPCapNeg is signalled to the gateway:
SDPCapNeg configuration

} | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| |

Maximum Burst Size

If peak data rate policing
Policing Required
Peak Data Rate
If Delay Variation required
Delay Variation Tolerance

If RTCP handling required:
RTCP allocation

If ECN transparent support required:
ECN Enable = "True"
Initiation Method = "inactive"

If ECN Endpoint support required
ECN Enable = "True"
Initiation Method = "ECN Initiation Method" NOTE 2

Congestion Response = "ECN Congestion Response"
NOTE 3
ECN Mode = "ECN mode"
NOTE 3
ECT Marking = "ECN ECT marking" NOTE 3

RTCP Feedback = "ECN RTCP Feedback" NOTE 3

XR Summary Report = "ECN XR Summary Report" NOTE 3
If notification of ECN Failure Report:
NotificationRequested (Event ID = x, "ECN Failure")

If ICE is applied:
STUN server request

If media is "message":
If B-ALG for MSRP required:
Application-aware MSRP interworking request

| | +|

NOTE 1: The event parameters "Media Inactivity Detection Time" and "Media Inactivity Detection Direction" are optional.

NOTE 2: This shall be set to a value other than "inactive"

NOTE 3: For the IMS side/3GPP ECN profile terminations this property does not need to be signalled; default provisioned values are defined for this profile. For procedures to handle interworking between different ECN property settings see 3GPP TS 29.162 [18].

NOTE 4: The support of the CVO feature is optional for the TrGW. The IBCF shall send the "extended RTP header for CVO" information element only with supported CVO URN(s) to the TrGW. If the TrGW does not support the CVO feature, the IBCF shall not send the "extended RTP header for CVO" information element to the TrGW.

NOTE 5: If the TrGW supports the extended RTP header with Coordination of Video Orientation information it shall pass any received extended RTP header with CVO bits on to outgoing RTP streams. If the TrGW transcodes between video payloads and it supports the extended RTP header with CVO bits it shall keep the video orientation unchanged during the transcoding and convey received RTP header bytes on the outgoing RTP stream after transcoding associated packets as specified in 3GPP TS 26.114 [31], clause 7.4.5.

NOTE 6: The support of the generic image attributes is optional for the TrGW. The list of image sizes per payload type supported by the TrGW is preconfigured in the IBCF. If none of the image sizes received within an SDP body on Mx interface is supported by the TrGW then the IBCF shall not send the generic image attribute parameter to the TrGW.

| | | + +Editor's Note: IP Interface Type needs to be further clarified in stage 2 – possible exclusion for IMS Ix. + +On reserving the termination, the TrGW responds as in Table 5.17.2.2.2. + +**Table 5.17.2.2.2: Reserve TrGW Connection Point Acknowledge** + +| Address Information | Control information | Bearer information | +|-------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port
IP Address
IP Version
} | Transaction ID = x
Context ID = C1
Termination ID = T1
Stream Number | Local Descriptor {
If media is "audio" or "video":

Codec List
RTP Payloads
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
If media is "video":
If CVO extension header
provided in the request:
Extended Header for CVO
If media is "video":
If image attribute negotiation:
Generic Image Attribute
If Predefined ROI provided in the
request:
RTCP feedback for Predefined
ROI
Extended Header for Sent ROI
If Arbitrary ROI provided in the
request:
RTCP feedback for Arbitrary ROI
Extended Header for Sent ROI

If ICE is applied:
ICE host candidate
ICE password
ICE Ufrag
ICE pacing
If ICE lite implementation
ICE lite indication

If SDPCapNeg is signalled to the
gateway:
SDPCapNeg configuration
} | + +#### 5.17.2.3 Configure TrGW Connection Point + +The IBCF sends a MODIFY request command as in Table 5.17.2.3.1. + +**Table 5.17.2.3.1: Configure TrGW Connection Point Request** + +| Address Information | Control information | Bearer information | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| If local resources are modified:
Local Descriptor {
Port
IP Address
IP Version
}
If remote resources are modified:
Remote Descriptor {
Port
IP Address
IP Version
} | Transaction ID = x
Context ID = C1
Termination ID = T1

If MPS priority is modified:
Priority Indicator = x (NOTE 5)

If Stream Number specified:
Stream Number

If Resources for multiple Codecs required:
Reserve_Value

If diffserv required:-
Diffserv Code Point
If tagging behaviour
Diffserv Tagging Behaviour

If Remote Source Address Filtering required:-
Remote Source Address Filtering
If Remote Source Address range required:-
Remote Source Address Mask
If Remote Source Port Filtering required:-
Remote Source Port Filtering
If individual port:-
Remote Source Port
If range of ports:
Remote Source Port Range

NotificationRequested (Event ID = x, "termination heartbeat")

If multiple IP realms: IP realm Identifier = required IP realm (NOTE 1)

If Media Inactivity Detection Required:
NotificationRequested (Event ID = x, "Media Inactivity Detection (Media Inactivity Detection Time, Media Inactivity Detection Direction) ") (NOTE 2)

If Sustainable Data Rate Policing Required:-
Policing Required
Sustainable Data Rate
Maximum Burst Size

If peak data rate policing
Policing Required
Peak Data Rate
If Delay Variation required
Delay Variation Tolerance

If RTCP handling required:
RTCP allocation

If ECN transparent support required:
ECN Enable = "True" | If local resources are modified:
Local Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
If RTP-level pause and resume:
CCM pause-resume
If RTCP Codec Control
Commands and Indications:
CCM BASE
If RTCP Delay Budget
Information:
DBI

If media is "video":
If CVO required:
Extended Header for CVO (NOTE 6, NOTE 7)
If media is "video":
If imageattr negotiation:
Generic Image Attribute (NOTE 8)
If Predefined ROI required:
RTCP feedback for Predefined ROI
Extended Header for Sent ROI
If Arbitrary ROI required:
RTCP feedback for Arbitrary ROI
Extended Header for Sent ROI

If SDPCapNeg is signalled to the gateway:
SDPCapNeg configuration
}

If remote resources are modified:
Remote Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If rate adaptation for media endpoints:
Additional Bandwidth Properties (NOTE 10)
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
If RTP-level pause and resume:
CCM pause-resume
If RTCP Codec Control
Commands and Indications:
CCM BASE
If RTCP Delay Budget
Information:
DBI

If media is "video":
If CVO required:
Extended Header for CVO (NOTE 6, NOTE 7) | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

Initiation Method = "inactive"

If ECN Endpoint support required
ECN Enable = "True"
Initiation Method = "ECN Initiation Method" NOTE 3

Congestion Response = "ECN Congestion Response"
NOTE 4

ECN Mode = "ECN mode"
NOTE 4

ECT Marking = "ECN ECT marking" NOTE 4

RTCP Feedback = "ECN RTCP Feedback" NOTE 4

XR Summary Report = "ECN XR Summary Report" NOTE 4

If notification of ECN Failure Report:
NotificationRequested (Event ID = x, "ECN Failure")

If full ICE is applied:
Send Connectivity Check ("Control")

If notification of ICE Connectivity Check Result Report:
NotificationRequested (Event ID= xx, "Connectivity Check Result")

If notification of New Peer Reflexive Candidate:
NotificationRequested (Event ID = xy, "New Peer Reflexive Candidate")

Send Additional Connectivity Check ("Control")

If media is "message":
If B-ALG for MSRP required:
Application-aware MSRP interworking request

|

If media is "video":
If imageattr negotiation:
Generic Image Attribute (NOTE 8)

If Predefined ROI required:
RTCP feedback for Predefined ROI
Extended Header for Sent ROI

If Arbitrary ROI required:
RTCP feedback for Arbitrary ROI
Extended Header for Sent ROI

If media is "message":
If B-ALG for MSRP required:
MSRP Path

If RTCP APP messages allowed
Allowed RTCP APP message types

If ICE is applied:
ICE received candidate
ICE received password
ICE received Ufrag (NOTE 9)
ICE received pacing (NOTE 11)

If SDPCapNeg is signalled to the gateway:
SDPCapNeg configuration

}

| +|

NOTE 1: This shall only be set to the same IP realm as at the reservation stage which is specified in Table 5.17.2.2.1. If a different IP realm is specified, the TrGW shall return error 501 "Not Implemented". Additional streams may be added by the Configure_TrGW_Connection_Point procedure. The additional streams shall then carry the same IP Realm Identifier as the first stream.

NOTE 2: The event parameters "Media Inactivity Detection Time" and "Media Inactivity Detection Direction" are optional.

NOTE 3: This shall be set to a value other than "inactive".

NOTE 4: For the IMS side/3GPP ECN profile terminations this property does not need to be signalled; default provisioned values are defined for this profile. For procedures to handle interworking between different ECN property settings see 3GPP TS 29.162 [18].

NOTE 5: The support of the modification of the Priority Indicator value is optional for the TrGW and depends on implementation solution for Priority call/session authorisation (see 3GPP TS 29.162 [18]).

NOTE 6: The support of the CVO feature is optional for the TrGW. The IBCF shall send the "extended RTP header for CVO" information element only with supported CVO URN(s) to the TrGW. If the TrGW does not support the CVO feature, the IBCF shall not send the "extended RTP header for CVO" information element to the TrGW.

NOTE 7: If the TrGW supports the extended RTP header with Coordination of Video Orientation information it shall pass any received extended RTP header with CVO bits on to outgoing RTP streams. If the TrGW shall pass any received extended RTP header with CVO bits on to outgoing RTP streams. If the TrGW

| | | + +transcodes between video payloads and it supports the extended RTP header with CVO bits it shall keep the video orientation unchanged during the transcoding and convey received RTP header bytes on the outgoing RTP stream after transcoding associated packets as specified in 3GPP TS 26.114 [31], clause 7.4.5. + +NOTE 8: The support of the generic image attributes is optional for the TrGW. The list of image sizes per payload type supported by the TrGW is preconfigured in the IBCF. If none of the image sizes received within an SDP body on Mx interface is supported by the TrGW then the IBCF shall not send the generic image attribute parameter to the TrGW. + +NOTE 9: The support of ICE received candidate, ICE received password, ICE received Ufrag are optional for ICE lite, as specified in 3GPP TS 29.162 [18]. + +NOTE 10: The support of rate adaptation for media endpoints using the additional bandwidth properties is optional for the TrGW. If media transcoding is required the IBCF may provide for the selected payload type and the used IP version the additional bandwidth properties. + +NOTE 11: The ICE received pacing is only applicable for full ICE, as specified in IETF RFC 8445 [55]. + +The TrGW responds as in Table 5.17.2.3.2. + +**Table 5.17.2.3.2: Configure TrGW Connection Point Request Acknowledge** + +| Address Information | Control information | Bearer information | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| If local resources were provided in request:
Local Descriptor {
Port
IP Address
IP Version
}
If remote resources are provided in request:
Remote Descriptor {
Port
IP Address
IP Version
} NOTE | Transaction ID = x
Context ID = C1
Termination ID = T1

If Stream Number Specified:
Stream Number | If local resources were provided in request:
Local Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
If RTP-level pause and resume:
CCM pause-resume
If RTCP Codec Control
Commands and Indications:
CCM BASE
If RTCP Delay Budget
Information:
DBI

If media is "video":
If CVO extension header provided in the request:
Extended Header for CVO
If media is "video":
If image attribute negotiation:
Generic Image Attribute
If Predefined ROI provided in the request:
RTCP feedback for Predefined ROI
Extended Header for Sent ROI
If Arbitrary ROI provided in the request:
RTCP feedback for Arbitrary ROI
Extended Header for Sent ROI
}

If remote resources are provided in request:
Remote Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If rate adaptation for media endpoints:
Additional Bandwidth
Properties
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
If RTP-level pause and resume:
CCM pause-resume
If RTCP Codec Control
Commands and Indications:
CCM BASE
If RTCP Delay Budget
Information:
DBI

If media is "video":
If CVO extension header provided in the request:
Extended Header for CVO | + +| | | | +|----------------------------------------------------|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | If media is "video":
If image attribute negotiation:
Generic Image Attribute
If Predefined ROI provided in the request:
RTCP feedback for Predefined ROI
Extended Header for Sent ROI
If Arbitrary ROI provided in the request:
RTCP feedback for Arbitrary ROI
Extended Header for Sent ROI
} NOTE | +| NOTE: Sending of the Remote Descriptor is optional | | | + +#### 5.17.2.4 Reserve and Configure TrGW Connection Point + +The IBCF sends an ADD request command as in Table 5.17.2.4.1. + +**Table 5.17.2.4.1: Reserve and Configure TrGW Connection Point Request** + +| Address Information | Control information | Bearer information | +|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port = \$
IP Address = \$
IP Version = IPv4 or IPv6
}
Remote Descriptor {
Port
IP Address
IP Version
} | Transaction ID = x
If Context Requested:
Context ID = \$
If Emergency Call:
Emergency Call Indication

If MPS call/session:
Priority Indicator = x

If Context Provided:
Context ID = c1

Termination ID = \$

If Stream Number Specified:
Stream Number
If Resources for multiple Codecs shall be reserved:
Reserve_Value

If IP Interface Type:
IP interface = "IP interface type"

If indication on Bearer Released requested:
NotificationRequested (Event ID = x, "BNC Release ")

If diffserv required:-
Diffserv Code Point
If tagging behaviour
Diffserv Tagging Behaviour

If Remote Source Address Filtering required:-
Remote Source Address Filtering
If Remote Source Address range required:-
Remote Source Address Mask

If Remote Source Port Filtering required:-
Remote Source Port Filtering
If individual port:-
Remote Source Port
If range of ports:
Remote Source Port Range

NotificationRequested (Event ID = x, "termination heartbeat")

If multiple IP realms: IP realm Identifier = required IP realm identifier

If Media Inactivity Detection Required:
NotificationRequested (Event ID = x, "Media Inactivity Detection (Media Inactivity Detection Time, Media Inactivity Detection Direction) ") (NOTE 1)

If Sustainable Data Rate Policing Required:- | Local Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
If RTP-level pause and resume:
CCM pause-resume
If RTCP Codec Control
Commands and Indications:
CCM BASE
If RTCP Delay Budget
Information:
DBI

If media is "video":
If CVO required:
Extended Header for CVO (NOTE 4, NOTE 5)
If media is "video":
If imageattr negotiation:
Generic Image Attribute (NOTE 6)
If Predefined ROI required:
RTCP feedback for Predefined ROI
Extended Header for Sent ROI
If Arbitrary ROI required:
RTCP feedback for Arbitrary ROI
Extended Header for Sent ROI

If ICE is applied:
ICE host candidate request
ICE password request
ICE Ufrag request
ICE pacing request

If SDPCapNeg is signalled to the gateway:
SDPCapNeg configuration
}

Remote Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If rate adaptation for media endpoints:
Additional Bandwidth Properties (NOTE 8)
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
If RTP-level pause and resume:
CCM pause-resume
If RTCP Codec Control
Commands and Indications:
CCM BASE
If RTCP Delay Budget
Information:
DBI | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

Policing Required
Sustainable Data Rate
Maximum Burst Size

If peak data rate policing
    Policing Required
    Peak Data Rate
    If Delay Variation required
        Delay Variation Tolerance

If RTCP handling required:
    RTCP allocation

If ECN transparent support required:
    ECN Enable = "True"
    Initiation Method = "inactive"

If ECN Endpoint support required
    ECN Enable = "True"
    Initiation Method = "ECN Initiation Method" NOTE 2

    Congestion Response = "ECN Congestion Response" NOTE 3
    ECN Mode = "ECN mode" NOTE 3
    ECT Marking = "ECN ECT marking" NOTE 3

    RTCP Feedback = "ECN RTCP Feedback" NOTE 3

    XR Summary Report = "ECN XR Summary Report" NOTE 3

    If notification of ECN Failure Report:
        NotificationRequested (Event ID = x, "ECN Failure")

If ICE is applied:
    STUN server request
    If full ICE is applied
        Send Connectivity Check ("Control")
    If notification of ICE Connectivity Check Result Report:
        NotificationRequested (Event ID = xx, "Connectivity Check Result")
    If notification of New Peer Reflexive Candidate:
        NotificationRequested (Event ID = xy, "New Peer Reflexive Candidate ")

If media is "message":
    If B-ALG for MSRP required:
        Application-aware MSRP interworking request

|

If media is "video":
    If CVO required:
        Extended Header for CVO (NOTE 4, NOTE 5)

If media is "video":
    If imageattr negotiation:
        Generic Image Attribute (NOTE 6)

    If Predefined ROI required:
        RTCP feedback for Predefined ROI
        ROI Extended Header for Sent ROI

    If Arbitrary ROI required:
        RTCP feedback for Arbitrary ROI
        Extended Header for Sent ROI

If media is "message":
    If B-ALG for MSRP required:
        MSRP Path

If RTCP APP messages allowed
    Allowed RTCP APP message types

If ICE is applied:
    ICE received candidate
    ICE received password
    ICE received Ufrag (NOTE 7)
    ICE received pacing (NOTE 9)

If SDPCapNeg is signalled to the gateway:
    SDPCapNeg configuration
    }

| +|

NOTE 1: The event parameters "Media Inactivity Detection Time" and "Media Inactivity Detection Direction" are optional.
NOTE 2: This shall be set to a value other than "inactive"
NOTE 3: For the IMS side/3GPP ECN profile terminations this property does not need to be signalled; default provisioned values are defined for this profile. For procedures to handle interworking between different ECN property settings see 3GPP TS 29.162 [18].

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

NOTE 4: The support of the CVO feature is optional for the TrGW. The IBCF shall send the "extended RTP header for CVO" information element only with supported CVO URN(s) to the TrGW. If the TrGW does not support the CVO feature, the IBCF shall not send the "extended RTP header for CVO" information element to the TrGW.

NOTE 5: If the TrGW supports the extended RTP header with Coordination of Video Orientation information it shall pass any received extended RTP header with CVO bits on to outgoing RTP streams. If the TrGW transcodes between video payloads and it supports the extended RTP header with CVO bits it shall keep the video orientation unchanged during the transcoding and convey received RTP header bytes on the outgoing RTP stream after transcoding associated packets as specified in 3GPP TS 26.114 [31], clause 7.4.5.

NOTE 6: The support of the generic image attributes is optional for the TrGW. The list of image sizes per payload type supported by the TrGW is preconfigured in the IBCF. If none of the image sizes received within an SDP body on Mx interface is supported by the TrGW then the IBCF shall not send the generic image attribute parameter to the TrGW.

NOTE 7: The support of ICE received candidate, ICE received password, ICE received Ufrag are optional for ICE lite, as specified in 3GPP TS 29.162 [18].

NOTE 8: The support of rate adaptation for media endpoints using the additional bandwidth properties is optional for the TrGW. If media transcoding is required the IBCF may provide for the selected payload type and the used IP version the additional bandwidth properties.

NOTE 9: The ICE received pacing is only applicable for full ICE, as specified in IETF RFC 8445 [55].

| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +The TrGW responds as in Table 5.17.2.4.2. + +**Table 5.17.2.4.2: Reserve and Configure TrGW Connection Point Request Acknowledge** + +| Address Information | Control information | Bearer information | +|----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port
IP Address
IP Version
}
Remote Descriptor {
Port
IP Address
IP Version
} NOTE | Transaction ID = x
Context ID = C1
Termination ID = T1
Stream Number | Local Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
If RTP-level pause and resume:
CCM pause-resume
If RTCP Codec Control
Commands and Indications:
CCM BASE
If RTCP Delay Budget
Information:
DBI

If media is "video":
If CVO extension header
provided in the request:
Extended Header for CVO
If media is "video":
If image attribute negotiation:
Generic Image Attribute
If Predefined ROI provided in the
request:
RTCP feedback for Predefined
ROI
Extended Header for Sent ROI
If Arbitrary ROI provided in the
request:
RTCP feedback for Arbitrary
ROI
Extended Header for Sent ROI

If ICE is applied:
ICE host candidate
ICE password
ICE Ufrag
ICE pacing
If ICE lite implementation
ICE lite indication

If SDPCapNeg is signalled to the
gateway:
SDPCapNeg configuration
}
Remote Descriptor {
If media is "audio" or "video":
Codec List
RTP Payloads
Rtpbw
If rate adaptation for media
endpoints:
Additional Bandwidth Properties
If RTCP bandwidth
RtcpbwRS
RtcpbwRR
If RTP-level pause and resume:
CCM pause-resume
If RTCP Codec Control
Commands and Indications:
CCM BASE
If RTCP Delay Budget
Information: | + +DBI + +If media is "video": + If CVO extension header + provided in the request: + Extended Header for CVO + If media is "video": + If image attribute negotiation: + Generic Image Attribute + If Predefined ROI provided in the + request: + RTCP feedback for Predefined + ROI + Extended Header for Sent ROI + If Arbitrary ROI provided in the + request: + RTCP feedback for Arbitrary + ROI + Extended Header for Sent ROI + +If SDPCapNeg is signalled to the + gateway: + SDPCapNeg configuration + +} NOTE + +NOTE: Sending of the Remote Descriptor is optional + +#### 5.17.2.5 Release TrGW Termination + +The IBCF sends a SUBTRACT command as in Table 5.17.2.5.1. + +**Table 5.17.2.5.1: Release TrGW Termination Request** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= C1/ALL
Termination ID = T1/ALL | | + +On releasing the termination, the TrGW responds as in Table 5.17.2.5.2 + +**Table 5.17.2.5.2: Release TrGW Termination Request Acknowledge** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1/ALL
Termination ID = T1/ALL | | + +#### 5.17.2.6 Termination Heartbeat Indication + +When the procedure "Termination heartbeat indication" is required the following procedure is initiated: the TrGW sends a NOT.req command with the following information. + +##### 5.17.2.6.1 NOT.req (Termination heartbeat) + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1

Event_ID (Event ID = x, "termination heartbeat") | | + +When processing of the command is complete, the IBCF initiates the following procedure. + +##### 5.17.2.6.2 NOT.resp (Termination heartbeat) + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +The IBCF is in charge of correcting any detected mismatch, by subtracting hanging terminations or clearing hanging contexts. + +#### 5.17.2.7 IP Bearer Released + +When the procedure "IP Bearer Released" is required the following procedure is initiated: the TrGW sends a NOT.req command with the following information. + +##### 5.17.2.7.1 NOT.req (IP Bearer Released) + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1

Event_ID (Event ID = x, "BNC Release (Cause)") | | + +When the processing of command is complete, the IBCF initiates the following procedure. + +##### 5.17.2.7.2 NOT.resp (IP Bearer Released) + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +#### 5.17.2.8 Media Inactivity Notification + +When the procedure "Media Inactivity Notification" is required the following procedure is initiated: the TrGW sends a NOT.req command with the following information. + +##### 5.17.2.8.1 NOT.req (Media Inactivity) + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1

Event_ID (Event ID = x, "Media Inactivity Detection") | | + +When the processing of command is complete, the IBCF initiates the following procedure. + +##### 5.17.2.8.2 NOT.resp (Media Inactivity) + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +#### 5.17.2.9 Change Through Connection + +The IBCF sends an ADD or a MODIFY request command as in Table 5.17.2.9.1. + +##### 5.17.2.9.1 Change Through Connection Request + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
If Context Requested:
Context ID = \$
If Context Provided:
Context ID = c1

If Termination Requested:
Termination ID = \$
If Termination Provided:
Termination ID = T1

Through-Connection = Connectivity Mode | | + +The TrGW responds as in Table 5.17.2.9.2. + +##### 5.17.2.9.2 Change Through Connection Request Acknowledge + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +#### 5.17.2.10 ECN FailureIndication + +The TrGW sends a NOTIFY request command as in Table 5.17.2.10.1. + +**Table 5.17.2.10.1: ECN Failure Indication** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= C1
Termination ID = T1

Event_ID (Event ID = x,
" ECN Failure (ECN Failure Type)") | | + +The IBCF responds as in Table 5.17.2.10.2 + +**Table 5.17.2.10.2: ECN Failure Indication Ack** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +#### 5.17.2.11 Change Flow Direction + +The TrGW sends an ADD or a MODIFY request command as in Table 5.17.2.11.1. + +**5.17.2.11.1 Change Flow Direction** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
If Context Requested:
Context ID = \$
If Context Provided:
Context ID = c1

If Termination Requested:
Termination ID = \$
If Termination Provided:
Termination ID = T1

Connection Configuration =
(TerminationID= x1,
TerminationID=x2, [type = x]) | | + +The IBCF responds as in Table 5.17.2.11.2. + +**5.17.2.11.2 Change Flow Direction Acknowledge** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +#### 5.17.2.12 ICE Connectivity Check Result Notification + +The TrGW sends a NOTIFY request command as defined in Table 5.17.2.12.1. + +**Table 5.17.2.12.1: ICE Connectivity Check Result Notification** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= C1
Termination ID = T1

Event_ID (Event ID = x,
" Connectivity Check Result
(Candidate/Transport Pair)") | | + +The IBCF responds as defined in Table 5.17.2.12.2 + +**Table 5.17.2.12.2: ICE Connectivity Check Result Notification Ack** + +| Address Information | Control information | Bearer information | +|----------------------------|--------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +#### 5.17.2.13 ICE New Peer Reflexive Candidate Notification + +The TrGW sends a NOTIFY request command as defined in Table 5.17.2.13.1. + +**Table 5.17.2.13.1: ICE New Peer Reflexive Candidate Notification** + +| Address Information | Control information | Bearer information | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID= C1
Termination ID = T1

Event_ID (Event ID = x,
" New Peer Reflexive Candidate
(Candidate)") | | + +The IBCF responds as defined in Table 5.17.2.13.2 + +**Table 5.17.2.13.2: ICE New Peer Reflexive Candidate Ack** + +| Address Information | Control information | Bearer information | +|----------------------------|--------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +### 5.17.3 Non-Call Related Procedures + +#### 5.17.3.1 General + +This clause describes the various non-call related procedures which are listed in Table 5.17.3.1.1 + +**Table 5.17.3.1.1: TrGW Non-Call Related Procedures** + +| Transaction defined in
3GPP TS 29.235 [17] or 3GPP TS
29.162 [18] | Support | Comment | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| TrGW Out of service | Mandatory | 5.17.3.2 | +| TrGW Communication Up | Mandatory | 5.17.3.3 | +| TrGW Restoration | Mandatory | 5.17.3.4 | +| TrGW Register | Mandatory | 5.17.3.5 | +| TrGW Re-register | Optional
(NOTE 3) | 5.17.3.6 | +| IBCF Ordered Re-register | Optional
(NOTE 3) | 5.17.3.7 | +| IBCF Restoration | Optional | 5.17.3.8 | +| IBCF Out of Service | Optional | 5.17.3.9 | +| Audit Value | Optional
(NOTE 3) | 5.17.3.10 | +| Command Rejected | Mandatory | The "Command Rejected" procedure may be used in response both to call-related and non-call-related ITU-T Recommendation H.248 Commands – 5.17.3.11 | +| TrGW Capability Change | Optional | 5.17.3.12 | +| TrGW Resource Congestion Handling – Activate | Optional | 5.17.3.13 | +| TrGW Resource Congestion Handling – Indication | Optional | 5.17.3.14 | +| Inactivity timeout activation | Optional
(NOTE 4) | 5.17.3.15 | +| Inactivity timeout indication | Optional
(NOTE 4) | 5.17.3.16 | +| Realm Availability Change activation | Optional | 5.17.3.17 | +| Realm Availability Change indication | Optional | 5.17.3.18 | +| Termination Out of Service | Optional
(NOTE 1) | 5.17.3.19 (NOTE 2) | +| NOTE 1: Support of this procedure is mandatory in the IBCF.
NOTE 2: The "Termination Out-of-Service procedure" is also used as a call-related H.248 command
NOTE 3: Support of this procedure is mandatory in the TrGW.
NOTE 4: Support of this procedure is mandatory in the TrGW if UDP transport is supported. | | | + +#### 5.17.3.2 TrGW Out Of Service + +The TrGW sends a SERVICE CHANGE request command as in Table 5.17.3.2.1. + +**Table 5.17.3.2.1: TrGW Out Of Service Request** + +| Address Information | Control information | Bearer information | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT
SC Method = FORCED or
GRACEFUL
SC Reason = 905 Termination
Taken OOS or 908 MG Impending
Failure or 915 State Loss | | + +The IBCF responds as in Table 5.17.3.2.2. + +**Table 5.17.3.2.2: TrGW Out Of Service Request Ack** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT | | + +#### 5.17.3.3 TrGW Communication Up + +The TrGW sends a SERVICE CHANGE request command as in Table 5.17.3.3.1 to the IBCF address to which the control link association was previously established. + +**Table 5.17.3.3.1: TrGW Communication Up** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT
SC Method = DISCONNECTED
SC Reason = 900 , Service Restored | | + +The IBCF may respond as in table 5.17.3.3.2. If a response is received, the control link association is re-established and the inactivity timer would be restarted. + +**Table 5.17.3.3.2: TrGW Communication Up Ack** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT
If required to register to new IBCF:
Alternate MGC Id | | + +#### 5.17.3.4 TrGW Restoration + +When the TrGW has recovered, the TrGW sends a SERVICE CHANGE as in Table 5.17.3.4.1, + +**Table 5.17.3.4.1: TrGW Restoration** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT
SC Method = RESTART
SC Reason = 900, Service Restored | | + +The IBCF responds as in Table 5.17.3.4.2. + +**Table 5.17.3.4.2: TrGW Restoration Ack** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT
If required to register to new IBCF :
Alternate MGC Id | | + +#### 5.17.3.5 TrGW Register + +The TrGW sends a SERVICE CHANGE request command as in Table 5.17.3.5.1. + +**Table 5.17.3.5.1: TrGW Register** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT
SC Method = RESTART
SC Reason =901, Cold Boot or 902, Warm Boot
H248 Profile Identity
H248 Protocol Version | | + +The IBCF responds as in Table 5.17.3.5.2. + +**Table 5.17.3.5.2: TrGW Register Ack** + +| Address Information | Control information | Bearer information | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT
If applicable (NOTE): H248 Protocol Version
If applicable:-
H248 Profile Identity
If required to register to new IBCF :
Alternate MGC Id | | +| NOTE: The IBCF shall include the H.248 Protocol Version if the protocol version it supports or offers is lower than that proposed by the TrGW. The IBCF may include the H.248 Protocol Version if the protocol version it supports or offers is the protocol version proposed by the TrGW. | | | + +#### 5.17.3.6 TrGW Re-Register + +The TrGW sends a SERVICE CHANGE request command as in Table 5.17.3.6.1. + +**Table 5.17.3.6.1: Re-Registration** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT
SC Method = Handoff
SC Reason = 903, MGC Directed Change
H248 Profile Identity
H248 Protocol Version | | + +The IBCF responds as in Table 5.17.3.6.2. + +**Table 5.17.3.6.2: Re-Registration Ack** + +| Address Information | Control information | Bearer information | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT
If applicable (NOTE 1):
H248 Protocol Version
If applicable:-
H248 Profile Identity
If required to register to a new IBCF:
Alternate MGC Id | | +| NOTE 1: The IBCF shall include the H.248 Protocol Version if the protocol version it supports or offers is lower than that proposed by the TrGW. The IBCF may include the H.248 Protocol Version if the protocol version it supports or offers is the protocol version proposed by the TrGW.
NOTE 2: The ServiceChangeMGCId parameter may be returned in the TrGW Re-register response. If present in the response, the TrGW shall not consider itself registered and should preferably attempt to re-register with the IBCF specified in the ServiceChangeMgcID before any further alternate IBCFs. | | | + +#### 5.17.3.7 IBCF Ordered Re-register + +The IBCF sends a SERVICE CHANGE request command as in Table 5.17.3.7.1. + +**Table 5.17.3.7.1: IBCF Ordered Re-Register** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT
SC Method = HANDOFF
SC Reason = 903, MGC Directed
Change
Alternate MGC Id | | + +The TrGW responds as in Table 5.17.3.7.2. + +**Table 5.17.3.7.2: IBCF Ordered Re-Register Ack** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT | | + +The TrGW then performs a TrGW Re-Register procedure according to Clause 5.17.3.6. + +#### 5.17.3.8 IBCF Restoration + +When the IBCF has recovered, the IBCF sends a SERVICE CHANGE as in Table 5.17.3.8.1, + +**Table 5.17.3.8.1: IBCF Restoration** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT
SC Method = RESTART
SC Reason = 901, Cold Boot OR
902, Warm Boot | | + +The TrGW responds as in Table 5.17.3.8.2. + +**Table 5.17.3.8.2: IBCF Restoration Ack** + +| Address Information | Control information | Bearer information | +|----------------------------|---------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT | | + +#### 5.17.3.9 IBCF Out of Service + +The IBCF sends a SERVICE CHANGE request command as in Table 5.17.3.9.1. + +**Table 5.17.3.9.1: BCF Out Of Service** + +| Address Information | Control information | Bearer information | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT
SC Method = FORCED or
GRACEFUL
SC Reason = 905, Termination
Taken OOS | | + +The TrGW responds as in Table 5.17.3.9.2. + +**Table 5.17.3.9.2: IBCF Out Of Service Ack** + +| Address Information | Control information | Bearer information | +|----------------------------|---------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT | | + +#### 5.17.3.10 Audit Value + +The IBCF sends an AUDIT VALUE request command as in Table 5.17.3.10.1. + +**Table 5.17.3.10.1: Audit Value** + +| Address Information | Control information | Bearer information | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID= -/ALL/C1
Termination ID =
ROOT/ALL/T1/PartialWildcard
(NOTE 4, NOTE5)

Audit Packages (NOTE 1)

Audit Descriptor =
IndAuditParameter:=
IndAudMediaDescriptor:=
IndAudTerminationStateDescriptor:=
serviceState
Audit Descriptor = Empty (NOTE 2)

Audit Descriptor =
IndAuditParameter:=
IndAudMediaDescriptor:=
IndAudTerminationStateDescriptor:=
Available Realms (NOTE 3)

Audit Descriptor =
IndAuditParameter:=
IndAudMediaDescriptor:=
IndAudTerminationStateDescriptor:=
ROOT properties (NOTE 6)

Audit Descriptor =
IndAuditParameter:=
IndAudMediaDescriptor:=
IndAudTerminationStateDescriptor:=
SDPCapNeg Supported Capabilities
(NOTE 7) | | +| NOTE 1: Packages is for Null/Root Combination.
NOTE 2: Used for control association monitoring.
NOTE 3: Used for auditing available IP realms
NOTE 4: The partial wildcard termination is used for the context audit (see table 5.17.3.10.3) and specifies the "group" part of the termination identity (e.g. "ip/5/*").
NOTE 5: Partial wildcard shall only be used when text encoding is used on the H.248 interface.
NOTE 6: Used for auditing ROOT properties.
NOTE 7: Used for auditing SDPCapNeg Extensions when SDPCapNeg signalling to the gateway is supported. | | | + +The TrGW responds as in Table 5.17.3.10.2. + +**Table 5.17.3.10.2: Audit Value Ack** + +| Address Information | Control information | Bearer information | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID = -/C1
Termination ID = ROOT/T1
Packages List
serviceState
Available Realms
ROOT Properties
SDPCapNeg Extensions | | + +Upon reception of the command in the TrGW: + +- The Service State returns the current Service State +- When Packages are requested, the Package Names and Versions are returned +- When realm availability is audited, the list of available realms is returned. + +- When root properties are audited, the values of root properties are returned. + +The following table illustrates the allowed combinations that can be obtained with the AuditValue Command: + +**Table 5.17.3.10.3: Combinations of AuditValue Command** + +| ContextID | TerminationID | Information Obtained | +|----------------------------------------------------------------------------------------------|------------------|-----------------------------------------------------------------------------------------------------------------------| +| Specific | Wildcard | Audit of matching Terminations in a Context | +| Specific | Specific | Audit of a single Termination in a Context | +| Null | Root | Audit of Media Gateway state and/or control association or available realms or supported packages or ROOT properties. | +| All | Specific | (Non-null) ContextID in which the Termination currently exists | +| All | Partial Wildcard | (Non-null) ContextIDs in which the Terminations currently exist | +| NOTE: Partial wildcard shall only be used when text encoding is used on the H.248 interface. | | | + +#### 5.17.3.11 Command Rejected + +When the procedure "Command Reject" is required the following procedure is initiated: + +The TrGW / IBCF sends a response to any command.req with the following information. + +**Table 5.17.3.11.1: ANYcommand.resp (command reject) TrGW/IBCF to IBCF/TrGW** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1 or no context
Termination ID = T1 or no termination ID

Reason=Error | | + +#### 5.17.3.12 TrGW Capability Change + +The TrGW sends a SERVICE CHANGE request command as in Table 5.17.3.12.1. + +**Table 5.17.3.12.1: Capability Update** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT
SC Method = RESTART or DISCONNECTED
SC Reason = 916, Packages Change or 917, Capability Change | | + +The IBCF responds as in table 5.17.3.12.2. + +**Table 5.17.3.12.2 Capability Update Ack** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT | | + +#### 5.17.3.13 TrGW Resource Congestion Handling – Activate + +The IBCF sends a MODIFY request command as in Table 5.17.3.13.1 + +**Table 5.17.3.13.1: TrGW Resource Congestion Handling – Activate** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT

NotificationRequested (Event ID = x, "Overload Notification") | | + +The TrGW responds as in Table 5.17.3.13.2. + +**Table 5.17.3.13.2: TrGW Resource Congestion Handling – Activate Ack** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT | | + +#### 5.17.3.14 TrGW Resource Congestion Handling – Indication + +The TrGW sends a NOTIFY request command as in Table 5.17.3.14.1 + +**Table 5.17.3.14.1: TrGW Resource Congestion Handling – Indication** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT

If H.248.11 used:
Event_ID (Event ID = x, "Overload Notification")

If H.248.10 used:
Event_ID (Event ID = x, "
Overload Notification
(Reduction)") | | + +The IBCF responds as in Table 5.17.3.14.2 + +**Table 5.17.3.14.2: TrGW Resource Congestion Handling – Indication Ack** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT | | + +#### 5.17.3.15 Inactivity Timeout – Activation + +The IBCF sends a MODIFY request command as in Table 5.17.3.15.1 + +**Table 5.17.3.15.1: Inactivity Timeout – Activation** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= NULL
Termination ID = ROOT

NotificationRequested (Event ID = x, "Inactivity Timeout") | | + +The TrGW responds as in Table 5.17.3.15.2. + +**Table 5.17.3.15.2: Inactivity Timeout – Activation Ack** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = NULL
Termination ID = ROOT | | + +#### 5.17.3.16 Inactivity Timeout – Indication + +The TrGW sends a NOTIFY request command as in Table 5.17.3.16.1. + +**Table 5.17.3.16.1: Inactivity Timeout – Indication** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= NULL
Termination ID = ROOT
Event_ID (Event ID = x, "Inactivity Timeout") | | + +The IBCF responds as in Table 5.17.3.16.2 + +**Table 5.17.3.16.2: Inactivity Timeout – Indication Ack** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = NULL
Termination ID = ROOT | | + +#### 5.17.3.17 Realm Availability Change – Activation + +The IBCF sends a MODIFY request command as in Table 5.17.3.17.1. + +**Table 5.17.3.17.1: Realm Availability Change – Activation** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT

NotificationRequested (Event ID = x, "Realm Availability Change") | | + +The TrGW responds as in Table 5.17.3.17.2. + +**Table 5.17.3.17.2: Realm Availability Change – Activation Ack** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT | | + +#### 5.17.3.18 Realm Availability Change – Indication + +The TrGW sends a NOTIFY request command as in Table 5.17.3.18.1. + +**Table 5.17.3.18.1: Realm Availability Change – Indication** + +| Address Information | Control information | Bearer information | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT

Event_ID (Event ID = x,
"Realm Availability Change
(Changed Realms)") | | +| NOTE: The ObservedEvent Parameters returned within the Changed Realms are defined as mandatory since it shall contain at minimum 1 parameter but may contain both Newly Available Realms and Newly Unavailable Realms. | | | + +The IBCF responds as in Table 5.17.3.18.2 + +**Table 5.17.3.18.2: Realm Availability Change – Indication Ack** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT | | + +#### 5.17.3.19 Termination Out Of Service + +This procedure only applies when text encoding is used on the H.248 interface. + +The TrGW sends a SERVICE CHANGE request command as in Table 5.17.3.19.1. + +**Table 5.17.3.19.1: Termination Out Of Service Request** + +| Address Information | Control information | Bearer information | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= C1/ALL
Termination ID = T1 or Wildcarded Termination (NOTE)
SC Method = FORCED
SC Reason = 904 ("Termination Malfunction") or 905 ("Termination Taken OOS") or 906 ("Loss of Lower Layer Connectivity"), or 907 ("Transmission Failure") or 910 ("Media Capability Failure") | | +| NOTE: This is set to a specific termination identity or a partially wildcarded identity (i.e. specifying the "interface" part of the termination ID and wildcarding the "group" and "ld" parts) or a wholly wildcarded identity (i.e. ip/*). | | | + +The IBCF responds as in Table 5.17.3.19.2. + +**Table 5.17.3.19.2: Termination Out Of Service Request Ack** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1/ALL
Termination ID = As received | | + +# --- Annex A (informative): Illustration of Gate/Pinhole Concept --- + +## A.1 General + +The purpose of this informative annex is the illustration of the H.248 Stream/Termination model by showing exemplary realisations of gates for unidirectional versus bidirectional media flows. + +Only point-to-point sessions are in scope of this H.248 Profile (see clause 5.4). Interconnection of individual H.248 Streams is based on the basic principle described in clause 7.1.6/ ITU-T Recommendation H.248.1 [3]. The H.248 Multiplex Descriptor is therefore not necessary (see clause 5.6.2). The H.248 Topology Descriptor definition includes individual H.248 Streams, but is also not necessary (see clause 5.7.8). + +NOTE: all sessions have unicast media flows. Potential multicast applications are transparent for MG point of view. + +## --- A.2 Relationships between gates and H.248 Streams + +The realization of a gate is illustrated in figure A.2.1. There is a unidirectional media flow in that example, and there is a single H.248 Stream per Termination. A **H.248 Stream** covers per definition a single **bidirectional** media flow (clause 7.1.6/ITU-T Recommendation H.248.1 [3]). Media flows are interconnected by using the same **StreamID** (here: StreamID equals to S1 for T1 and T2). + +![Diagram illustrating the H.248 Context with a Gate, Stream, and Terminations. It shows a unidirectional media flow from Termination T1 to Termination T2 through a Gate. Both terminations are labeled 'IP H.248 Termination' and the stream is labeled 'IP H.248 Stream' with StreamID 'S1'. The entire setup is enclosed in an 'H.248 Context' box.](99781d878388c3e0f359b1d6ce14119c_img.jpg) + +Example A1.1 + +The diagram shows a unidirectional media flow within an H.248 Context. On the left, an 'IP H.248 Termination' labeled 'T1' is connected to a stream labeled 'S1' and 'IP H.248 Stream'. This stream enters a 'Gate' (represented by a blue box with a right-pointing arrow). On the other side of the gate, the stream 'S1' and 'IP H.248 Stream' exits the gate and connects to another 'IP H.248 Termination' labeled 'T2' on the right. The flow is indicated by a blue line with an arrow pointing from T1 to T2. + +Diagram illustrating the H.248 Context with a Gate, Stream, and Terminations. It shows a unidirectional media flow from Termination T1 to Termination T2 through a Gate. Both terminations are labeled 'IP H.248 Termination' and the stream is labeled 'IP H.248 Stream' with StreamID 'S1'. The entire setup is enclosed in an 'H.248 Context' box. + +**Figure A.2.1: H.248 Context - Illustration of Gate, Stream and Terminations** + +The uni- or bidirectional application of an H.248 Streams is controlled via usage of Local Descriptor (LD) and Remote Descriptor (RD). Figure A.2.2 shows a bidirectional session. There is again a single H.248 Stream per Termination. Gates are direction-dependent, there are consequently two gates in this example. + +![Diagram of H.248 Context Bidirectional Session using single H.248 Streams](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +Example A2.1 + +The diagram, titled "Example A2.1", depicts an H.248 Context. It shows two terminals, T1 and T2, represented by large blue circles on the left and right respectively. Each terminal is connected to a smaller red circle labeled "S1". Between these two S1 points, there are two parallel paths representing gates. The upper path contains a blue box labeled "Gate" with a right-pointing arrow (⇒) inside, indicating flow from T1 towards T2. The lower path contains a blue box labeled "Gate" with a left-pointing arrow (⇐) inside, indicating flow from T2 towards T1. Green arrows show the directional flow through these gates. The entire assembly of S1 points and gates is enclosed in a rectangular box labeled "H.248 Context". + +Diagram of H.248 Context Bidirectional Session using single H.248 Streams + +**Figure A.2.2: H.248 Context Bidirectional Session using single H.248 Streams** + +# --- Annex B (informative): Void \ No newline at end of file diff --git a/marked/Rel-18/29_series/29240/raw.md b/marked/Rel-18/29_series/29240/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cca48efdb3e2a05e41fe4036d42982136e431357 --- /dev/null +++ b/marked/Rel-18/29_series/29240/raw.md @@ -0,0 +1,2980 @@ + + +# 3GPP TS 29.240 V18.0.0 (2024-03) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP Generic User Profile (GUP); Stage 3; Network (Release 18)** + +![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for LTE Advanced Pro. It features the word "lte" in a bold, lowercase font. Above the "e" is the text "Advanced Pro" in a smaller font. To the right of the "e" is a green signal strength icon consisting of four curved lines of increasing height. A small "TM" trademark symbol is located to the bottom right of the "e". + +LTE Advanced Pro logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo. It features the letters "3GPP" in a stylized, bold font. The "3" and "G" are connected at the top. Below the "P" is a red signal strength icon consisting of three curved lines of increasing height. To the right of the "P" is a small "TM" trademark symbol. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. +Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +--- + +## --- **Keywords** + +UMTS, user, network, management + +### **3GPP** + +### --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members + +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +LTET™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Main concept..... | 9 | +| 5 Definition methodology ..... | 9 | +| 5.1 Protocol layers..... | 10 | +| 6 General guidelines..... | 12 | +| 6.1 Reusing Liberty Alliance DST ..... | 12 | +| 6.2 Guidelines for XML usage..... | 12 | +| 6.3 GUP Specific Naming and Namespaces ..... | 12 | +| 6.4 GUP Profile schema..... | 13 | +| 6.4.1 Example ..... | 13 | +| 6.5 Data Referencing Language..... | 14 | +| 6.5.1 Language Syntax for GCL..... | 14 | +| 6.5.2 Semantics..... | 15 | +| 6.6 GUP metadata ..... | 15 | +| 7 GUP bindings ..... | 16 | +| 7.1 General principles ..... | 16 | +| 7.2 GUP headers..... | 16 | +| 7.2.1 Correlation header ..... | 17 | +| 7.2.1.1 Description..... | 17 | +| 7.2.1.2 Content..... | 17 | +| 7.2.2 Provider header..... | 17 | +| 7.2.2.1 Description..... | 17 | +| 7.2.2.2 Content..... | 17 | +| 7.2.3 ProcessingContext header ..... | 18 | +| 7.2.3.1 Description..... | 18 | +| 7.2.3.2 Content..... | 18 | +| 7.2.4 Consent header ..... | 18 | +| 7.2.4.1 Description..... | 18 | +| 7.2.4.2 Content..... | 18 | +| 7.2.5 UsageDirective header..... | 18 | +| 7.2.5.1 Description..... | 18 | +| 7.2.5.2 Content..... | 19 | +| 7.2.6 ServiceInstanceUpdate header..... | 19 | +| 7.2.6.1 Description..... | 19 | +| 7.2.6.2 Content..... | 19 | +| 7.2.7 Timeout header..... | 20 | +| 7.2.7.1 Description..... | 20 | +| 7.2.7.2 Content..... | 20 | +| 7.2.8 CredentialsContext header..... | 20 | +| 7.2.8.1 Description..... | 20 | +| 7.2.8.2 Content..... | 20 | +| 7.2.9 wsse:Security header ..... | 20 | +| 7.2.9.1 Description..... | 20 | +| 7.2.9.2 Content..... | 20 | +| 7.2.10 is:UserInteraction header..... | 21 | +| 7.2.10.1 Description..... | 21 | +| 7.2.10.2 Content..... | 21 | + +| | | | +|---------|------------------------------------|----| +| 7.3 | GUP Data types ..... | 21 | +| 7.3.1 | GUP Resource identifiers ..... | 21 | +| 7.3.2 | GUP SelectType ..... | 22 | +| 7.3.3 | Access control metadata type ..... | 22 | +| 7.3.4 | Mapping metadata type ..... | 23 | +| 7.4 | GUP error codes ..... | 24 | +| 7.5 | GUP Message Types ..... | 25 | +| 7.5.1 | Create messages ..... | 25 | +| 7.5.1.1 | Overview ..... | 25 | +| 7.5.1.2 | Create request type ..... | 25 | +| 7.5.1.3 | Create response type ..... | 25 | +| 7.5.1.4 | Create example ..... | 25 | +| 7.5.2 | Delete messages ..... | 26 | +| 7.5.2.1 | Overview ..... | 26 | +| 7.5.2.2 | Delete Request type ..... | 26 | +| 7.5.2.3 | Delete Response type ..... | 27 | +| 7.5.2.4 | Delete example ..... | 27 | +| 7.5.3 | Modify messages ..... | 27 | +| 7.5.3.1 | Overview ..... | 27 | +| 7.5.3.2 | Modify request type ..... | 27 | +| 7.5.3.3 | Modify response type ..... | 28 | +| 7.5.3.4 | Modify example ..... | 28 | +| 7.5.4 | Query messages ..... | 29 | +| 7.5.4.1 | Overview ..... | 29 | +| 7.5.4.2 | Query request type ..... | 29 | +| 7.5.4.3 | Query response type ..... | 29 | +| 7.5.4.4 | Query example ..... | 29 | +| 7.5.5 | Subscribe messages ..... | 30 | +| 7.5.5.1 | Overview ..... | 30 | +| 7.5.5.2 | Subscribe request type ..... | 30 | +| 7.5.5.3 | Subscribe example ..... | 30 | +| 7.5.6 | Unsubscribe message ..... | 30 | +| 7.5.6.1 | Overview ..... | 30 | +| 7.5.6.2 | UnSubscribe request type ..... | 30 | +| 7.5.6.3 | UnSubscribe example ..... | 30 | +| 7.5.7 | Notify message ..... | 31 | +| 7.5.7.1 | Overview ..... | 31 | +| 7.5.7.2 | Notify response type ..... | 31 | +| 7.5.7.3 | Notify example ..... | 31 | +| 7.5.8 | List message ..... | 31 | +| 7.5.8.1 | Overview ..... | 31 | +| 7.5.8.2 | List request type ..... | 31 | +| 7.5.8.3 | List response type ..... | 31 | +| 7.5.8.4 | List example ..... | 31 | +| 8 | Rp interface ..... | 33 | +| 8.1 | General Principles ..... | 33 | +| 8.2 | Procedures ..... | 33 | +| 8.2.1 | Create Component procedure ..... | 33 | +| 8.2.1.1 | General description ..... | 33 | +| 8.2.1.2 | Detailed Behaviour ..... | 33 | +| 8.2.1.3 | List of result codes ..... | 33 | +| 8.2.2 | Delete Component procedure ..... | 34 | +| 8.2.2.1 | General description ..... | 34 | +| 8.2.2.2 | Detailed Behaviour ..... | 34 | +| 8.2.2.3 | List of result codes ..... | 34 | +| 8.2.3 | Modify Data procedure ..... | 35 | +| 8.2.3.1 | General description ..... | 35 | +| 8.2.3.2 | Detailed Behavior ..... | 35 | +| 8.2.3.3 | List of result codes ..... | 35 | +| 8.2.4 | Read Data procedure ..... | 36 | +| 8.2.4.1 | General description ..... | 36 | + +| | | | +|----------|-------------------------------------------------------------------------|----| +| 8.2.4.2 | Detailed Behaviour ..... | 36 | +| 8.2.4.3 | List of result codes ..... | 36 | +| 8.2.5 | Subscribe To Data procedure ..... | 37 | +| 8.2.5.1 | General description ..... | 37 | +| 8.2.5.2 | Detailed Behavior ..... | 37 | +| 8.2.5.3 | List of result codes ..... | 37 | +| 8.2.6 | Unsubscribe To Data procedure ..... | 37 | +| 8.2.6.1 | General description ..... | 37 | +| 8.2.6.2 | Detailed Behavior ..... | 38 | +| 8.2.6.3 | List of result codes ..... | 38 | +| 8.2.7 | Notify Data procedure ..... | 38 | +| 8.2.7.1 | General description ..... | 38 | +| 8.2.7.2 | Detailed Behaviour ..... | 38 | +| 8.2.7.3 | List of result codes ..... | 39 | +| 9 | Rg interface ..... | 40 | +| 9.1 | General principles ..... | 40 | +| 9.2 | Procedures ..... | 40 | +| 9.2.1 | Create Component procedure ..... | 40 | +| 9.2.1.1 | General description ..... | 40 | +| 9.2.1.2 | Detailed Behaviour ..... | 40 | +| 9.2.1.3 | List of result codes ..... | 40 | +| 9.2.2 | Delete Component procedure ..... | 41 | +| 9.2.2.1 | General description ..... | 41 | +| 9.2.2.2 | Detailed Behaviour ..... | 41 | +| 9.2.2.3 | List of result codes ..... | 41 | +| 9.2.3 | Modify Data procedure ..... | 42 | +| 9.2.3.1 | General description ..... | 42 | +| 9.2.3.2 | Detailed Behavior ..... | 42 | +| 9.2.3.3 | List of result codes ..... | 42 | +| 9.2.4 | Read Data procedure ..... | 43 | +| 9.2.4.1 | General description ..... | 43 | +| 9.2.4.2 | Detailed Behaviour ..... | 43 | +| 9.2.4.3 | List of result codes ..... | 43 | +| 9.2.5 | Subscribe To Data procedure ..... | 44 | +| 9.2.5.1 | General description ..... | 44 | +| 9.2.5.2 | Detailed Behavior ..... | 44 | +| 9.2.5.3 | List of result codes ..... | 45 | +| 9.2.6 | Unsubscribe To Data procedure ..... | 45 | +| 9.2.6.1 | General description ..... | 45 | +| 9.2.6.2 | Detailed Behavior ..... | 45 | +| 9.2.6.3 | List of result codes ..... | 45 | +| 9.2.7 | Notify Data procedure ..... | 46 | +| 9.2.7.1 | General description ..... | 46 | +| 9.2.7.2 | Detailed Behaviour ..... | 46 | +| 9.2.7.3 | List of result codes ..... | 46 | +| 10 | Authentication, authorization and security ..... | 48 | +| 10.1 | Principles ..... | 48 | +| 10.2 | Security and Authentication ..... | 49 | +| 10.2.1 | Rg interface (client application / GUP server) ..... | 49 | +| 10.2.1.1 | Peer Entity Authentication and Transport Layer Channel Protection ..... | 49 | +| 10.2.1.2 | Message Authentication ..... | 49 | +| 10.2.2 | Rp interface (GUP server / RAF) ..... | 50 | +| 10.2.3 | Cryptographic requirements ..... | 50 | +| 10.2.4 | End-to-End Example (informative) ..... | 50 | +| 10.2.5 | Example of GUP wsse:Security header (informative) ..... | 51 | +| 10.3 | Authorization ..... | 53 | +| 10.3.1 | Principles ..... | 53 | +| 10.3.2 | Authorization related data ..... | 53 | +| 10.3.2.1 | Authorization attributes ..... | 53 | +| 10.3.2.2 | Authorization rules ..... | 54 | + +| | | | +|----------------------------------------------------------------|------------------------------------------------------------|-----------| +| 10.3.2.3 | Management of authorization related data..... | 54 | +| 10.3.3 | Execution of authorization logic ..... | 54 | +| 10.3.4 | Roles of GUP entities related to the authorization ..... | 54 | +| 10.3.4.1 | GUP Requestor ..... | 55 | +| 10.3.4.2 | GUP server and RAF ..... | 55 | +| 10.3.4.3 | Management entity ..... | 55 | +| Annex A (normative): Component Data Definitions ..... | | 57 | +| A.1 | HSS IMS GUP Component definition ..... | 57 | +| A.1.1 | General description ..... | 57 | +| A.1.1.1 | XML Schema files for HSS IMS GUP Components ..... | 58 | +| A.1.2 | Element addressing ..... | 59 | +| A.1.3 | Void..... | 59 | +| A.2 | HSS IMS GUP Component structure..... | 59 | +| A.2.1 | HSSIMSData GUP Component ..... | 59 | +| A.2.1.1 | SCSCFSelection ..... | 60 | +| A.2.1.2 | IMS Location ..... | 60 | +| A.2.1.3 | PrivateUserIdentity ..... | 60 | +| A.2.2 | AuthenticationAndCiphering GUP Component..... | 60 | +| A.2.3 | SubscriptionIdentificationAndNumbering GUP Component ..... | 60 | +| A.2.3.1 | RepositoryData ..... | 61 | +| A.2.4 | ServiceProfile GUP Component ..... | 61 | +| A.2.4.1 | CoreNetworkServiceAuthorization ..... | 61 | +| A.2.4.2 | InitialFilterCriteria ..... | 61 | +| A.2.4.2.1 | ApplicationServer ..... | 61 | +| A.2.4.2.2 | TriggerPoint ..... | 61 | +| A.2.4.2.2.1 | ServicePointTrigger ..... | 61 | +| A.3 | Common Data Types ..... | 62 | +| A.4 | Data Services Template Checklist tables ..... | 63 | +| Annex B (normative): WSDL Definitions ..... | | 67 | +| Annex C (normative): XML Schema Definitions ..... | | 68 | +| Annex D (informative): XML Schema Structure..... | | 69 | +| Annex E (normative): SOAP binding for GUP headers ..... | | 71 | +| E.1 | Correlation header..... | 71 | +| E.2 | Provider header ..... | 71 | +| E.3 | ProcessingContext header ..... | 71 | +| E.4 | Consent header ..... | 72 | +| E.5 | UsageDirective header ..... | 72 | +| E.6 | ServiceInstanceUpdate header ..... | 72 | +| E.7 | Timeout header ..... | 72 | +| E.8 | CredentialsContext header ..... | 72 | +| E.9 | Security header..... | 73 | +| E.10 | UserInteraction header ..... | 73 | +| Annex G (informative): Change history..... | | 74 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the stage 3 network protocol description to the 3GPP Generic User Profile (GUP), which includes the elements necessary to realise the stage 2 requirements in 3GPP TS 23.240 [1]. + +The fact of having several domains within the 3GPP mobile system (e.g. Circuit-Switched, Packet-Switched, IP Multimedia Subsystem) and access technologies (e.g. GERAN, UTRAN and WLAN) introduces a wide distribution of data associated with the user. Further, the new functions both in terminals and networks mean that the data related to users, services and user equipment will be increased greatly. This causes difficulties for users, subscribers, network operators and value added service providers to create, access and manage the user-related data located in different entities. + +The objective of specifying the 3GPP Generic User Profile is to provide a conceptual description to enable harmonised usage of the user-related information located in different entities. Technically the 3GPP Generic User Profile provides an architecture, data description and interface with mechanisms to handle the data. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TS 23.240: "3GPP Generic User Profile - Architecture; Stage 2". + +- [2] "Web Services Description Language (WSDL) 1.1," Christensen, Erik, Curbera, Francisco, Meredith, Greg, Weerawarana, Sanjiva, eds. World Wide Web Consortium W3C Note (15 March 2001). . +- [3] Thompson, H.S., Beech, D., Maloney, M., Mendleshon, N., eds. (May 2002). "XML Schema Part 1: Structures," Recommendation, World Wide Web Consortium. +- [4] Biron, P.V., Malhotra, A., eds. (May 2002). "XML Schema Part 2: Datatypes," Recommendation, World Wide Web Consortium . +- [5] "Simple Object Access Protocol (SOAP) 1.1," Box, Don, Ehnebuske, David , Kakivaya, Gopal, Layman, Andrew, Mendelsohn, Noah, Nielsen, Henrik Frystyk, Thatte, Satish, Winer, Dave, eds. World Wide Web Consortium W3C Note (08 May 2000). . +- [6] Void. +- [7] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signalling flows and message contents". +- [8] 3GPP TS 23.008: "Organization of subscriber data". +- [9] 3GPP TS 23.228: "IP Multimedia Subsystems (IMS); Stage 2". +- [10] 3GPP TS 29.328: "IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents". +- [11] 3GPP TS 33.102: "3G Security; Security architecture". +- [12] 3GPP TS 33.203: "3G security; Access security for IP-based services". +- [13] "Liberty ID-WSF Data Services Template Specification", Liberty Alliance Project. (draft) +- [14] "Liberty ID-WSF SOAP Binding Specification", Liberty Alliance Project. +- [15] "Liberty ID-WSF Security Mechanisms Specification", Liberty Alliance Project. +- [16] Void. +- [17] "Liberty ID-WSF Discovery Service Specification", Liberty Alliance Project. +- [18] IETF RFC 2396: "Uniform Resource Identifiers (URI): Generic Syntax". +- [19] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [20] IETF RFC 2486:" The Network Access Identifier". +- [21] 3GPP TS 23.003: "Numbering, addressing and identification". +- [22] IETF RFC 2821:"Simple Mail Transfer Protocol". +- [23] "Liberty ID-WSF Interaction Service Specification", Liberty Alliance Project. +- [24] Hallam-Baker, Phillip, Kaler, Chris, Monzillo, Ronald, Nadalin, Anthony, eds. (January, 2004). "Web Services Security: SOAP Message Security," OASIS Standard V1.0 [OASIS 200401], Organization for the Advancement of Structured Information Standards +- [25] IETF RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". +- [26] IETF RFC 7231: "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content". + +- [27] IETF RFC 7232: "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests". +- [28] IETF RFC 7233: "Hypertext Transfer Protocol (HTTP/1.1): Range Requests". +- [29] IETF RFC 7234: "Hypertext Transfer Protocol (HTTP/1.1): Caching". +- [30] IETF RFC 7235: "Hypertext Transfer Protocol (HTTP/1.1): Authentication". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document the following definitions apply: + +**3GPP Generic User Profile (GUP):** The 3GPP Generic User Profile is the collection of user related data which affects the way in which an individual user experiences services and which may be accessed in a standardised manner as described in this specification. + +**GUP Component:** A GUP component is logically an individual part of the Generic User Profile. + +**Data Element:** the indivisible unit of Generic User Profile information. + +**Data Element Group:** A pre-defined set of Data Elements and/or other Data Element Groups closely related to each other. One or more Data Element Groups can constitute the GUP Component. + +**Data Description Method:** A method describing how to define the data contained in the Generic User Profile + +## 3.2 Symbols + +For the purposes of the present document the following symbols apply: + +| | | +|----|-----------------------------------------------------------------------------------------------------------------------| +| Rg | Reference Point between Applications and the GUP Server. | +| Rp | Reference Point between the GUP Server and GUP Data Repositories, and between Applications and GUP Data Repositories. | + +## 3.3 Abbreviations + +For the purposes of the present document the following abbreviations apply: + +| | | +|------|-------------------------------| +| GUP | 3GPP Generic User Profile | +| SOAP | Simple Object Access Protocol | +| RAF | Repository Access Function | + +# --- 4 Main concept + +This specification defines the binding of the GUP interfaces and procedures to SOAP protocol (defined in "Simple Object Access Protocol (SOAP) 1.1" [5]). Each interface is defined in terms of the messages sent and received. The payload of each message is XML, defined using an XML schema language. The framework, procedures, SOAP binding and security solutions of GUP are based on the Liberty Alliance Project work. + +Throughout the rest of this specification the SOAP based binding of the 3GPP GUP is described + +# --- 5 Definition methodology + +The definition of the interfaces can be divided into the following clauses: + +Definition of the operations (WSDL/XML) + +Common functions like security, authentication and authorisation (WSDL/XML) + +Repository Access Function specific data contents for the operations (XML Schema) + +## 5.1 Protocol layers + +The protocol architecture of the Rg reference point is depicted in the figure 1. The essential contents of this specification describe the functionality, semantics and the WSDL/XML definitions of the interfaces. Additionally the special characteristics of the SOAP and http usage are defined. It is worth noting that part of the data is passed in the SOAP headers but the most GUP specific data is placed in the SOAP message body. + +![Figure 7.2.1 GUP Rg reference point protocol architecture diagram](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +The diagram illustrates the protocol stack for the Rg reference point. It consists of two vertical columns of four stacked boxes. The left column, labeled 'Application', has boxes for 'Application', 'SOAP', 'HTTP', and 'TCP/IP' from top to bottom. The right column, labeled 'GUP server', has boxes for 'GUP server', 'SOAP', 'HTTP', and 'TCP/IP' from top to bottom. A horizontal line connects the bottom 'TCP/IP' boxes of both columns. + +Figure 7.2.1 GUP Rg reference point protocol architecture diagram + +**Figure 7.2.1 GUP Rg reference point protocol architecture** + +The protocol architecture of the Rp reference point is depicted in the figure 2. + +![Figure 7.7.2 GUP Rp reference point protocol architecture diagram](b0211cee4b20034939d883ac0d70f696_img.jpg) + +The diagram illustrates the protocol stack for the Rp reference point. It consists of two vertical columns of four stacked boxes. The left column, labeled 'Application / GUP server', has boxes for 'Application / GUP server', 'SOAP', 'HTTP', and 'TCP/IP' from top to bottom. The right column, labeled 'RAF', has boxes for 'RAF', 'SOAP', 'HTTP', and 'TCP/IP' from top to bottom. A horizontal line connects the bottom 'TCP/IP' boxes of both columns. + +Figure 7.7.2 GUP Rp reference point protocol architecture diagram + +**Figure 7.7.2 GUP Rp reference point protocol architecture** + +The interface between Repository Access Function (RAF) and GUP Data Repository is not defined by the present specification because it is not required to be standardised in 3GPP TS 23.240: "3GPP Generic User Profile - Architecture; Stage 2 [1] The protocol contains following layers: + +- Application layer + - Application level interface specification. All the operations and data are described by XML elements and attributes in an XML Schema and WSDL. The WSDL is defined by W3C in Web Services Description Language (WSDL) 1.1 [2]. + - The standard XML Schema is defined by W3C in "XML Schema Part 1: Structures", Recommendation [3] and "XML Schema Part 2: Datatypes," Recommendation [4]. +- SOAP (Session layer) + +- SOAP is an XML based messaging protocol that provides support for remote procedure calls by messaging. The SOAP protocol is defined by W3C in "Simple Object Access Protocol (SOAP) 1.1" [5]. +- A few specific header types are defined for GUP e.g. for message IDs and time stamps. +- HTTP (Transport layer) + - HTTP defines how messages are transmitted and formatted. HTTP is a stateless protocol, i.e. each command is executed independently. HTTP/1.1 is defined by IETF RFC 7230 [25], IETF RFC 7231 [26], IETF RFC 7232 [27], IETF RFC 7233 [28], IETF RFC 7234 [29] and IETF RFC 7235 [30]. +- TCP/IP (Network layer) + - TCP/IP handles network communications between network nodes. GUP does not define any special requirements for this layer. + +# 6 General guidelines + +The GUP architecture has identified three kinds of entities: (1) client applications, (2) GUP servers and (3) data repositories [point to stage 2]. For the communication between these entities, two interfaces have been defined, namely Rp and Rg. + +Communication between GUP entities is performed via the exchange of messages expressed as XML documents. XML documents should include the XML declaration with the version and encoding attributes. The XML documents shall be well-formed and valid. The W3C XML Schema [3,4] is used in GUP to define the structure of valid XML documents. + +The implementation of the Rp and Rg interfaces follows the Liberty Alliance Data Service Template specification [Liberty Alliance]. + +From a Liberty Alliance point of view, GUP servers and data repositories will play the role of Liberty Alliance data services. + +## 6.1 Reusing Liberty Alliance DST + +Liberty Alliance Data Service Template [13] specification proposes a framework for web services that offer access to data in general. In the context of GUP, the data services should be restricted to GUP user profile data. + +The Data Service Template defines: (1) some abstract definitions about messages that are sent and received by the web service and (2) some guidelines regarding the structure of the data offered through the service. + +More concretely, the Liberty Alliance Data Service Template [13] specification offers a set of incomplete XML schemas with placeholders (for data types) that need to be filled based on the nature of the data offered by the data service. + +In the context of GUP, we will: + +- fill the place holders with some GUP specific data types, and +- add some new messages that are not offered by the Data Service Template specification + +The details of this instantiation of the Liberty Alliance Data Service Template for each GUP component are summarized in corresponding check list tables presented in Annex A together with the actual definition of the GUP component. + +The guidelines and naming conventions recommended by Liberty alliance when using XML and XML Schemas are directly applicable to GUP. + +## 6.2 Guidelines for XML usage + +As described in Liberty ID-WSF Data Services Template Specification [13], the schemas of the different data services, and GUP in particular, should follow a set of guidelines that are included in this specification with the purpose of completeness. + +## 6.3 GUP Specific Naming and Namespaces + +The namespace URI for GUP specific XML documents is a 3GPP specific namespace identifier 'http://3gpp' followed by a namespace specific string starting with 'gup' followed by 'ns' and a sub-namespace specific for a certain namespace. (The 'ns' is used to grouping instances of the namespace type of URIs together. Other types of usage of URIs may be defined later.) The sub-namespaces are defined in GUP specifications and/or implementations. + +Thus the syntax of the URI for all GUP specific namespaces is: 'http://3gpp/gup/ns/'. + +The sub-namespace for the GUP Component specific Profile Components consists of the common 'comp' part followed by the component name. + +The following namespaces are defined for GUP: + +- GUP Profile: 'http://3gpp/gup/ns/profile' +- Common Attributes: 'http://3gpp/gup/ns/common/' +- GUP procedures: 'http://3gpp/gup/ns/proc/' +- GUP Components: 'http://3gpp/gup/ns/comp/'. + +For example an HSS related component URN could be 'http://3gpp/gup/ns/comp/IMSSubscription'. + +**Editor's note:** This clause should go into 23.003 when the specification is getting to a stable condition. + +## 6.4 GUP Profile schema + +If the Liberty Alliance data service template specifies the interfaces that can be used to access this data, it does not specify the exact nature of the data. In the context of GUP, we need to explicitly define what the subscriber profile data consists of. + +3GPP GUP defines a global schema for the XML content of the user profile. + +This schema is unique and the same for every user. The schema is defined using W3C XML schemas. + +The GUP user profile consists of profile components. + +There are many manners to generate the schema for Generic User Profile. But irrespectively of the manner (e.g. one single XML schema vs many schema nested within each other), the schema can always be transformed into a single "canonical" XML schema. A user profile will be a valid instance of this "canonical" schema. + +way to define the global schema + +will be to define a set of sub-schemas, each with its own namespace. The schema defines a set a single rooted XML documents, each of them being a valid instance of one component defined by the schema. This fact enables easier schema management as applications should not have to worry about the whole schema, but only the parts they are interested in; when one schema component gets modified, only applications using this component should care about the change. Guidelines for the construction of the profile schema + +When designing the schema we want to achieve: + +- Modularity +- Extensibility +- Readability +- Easy support for versioning +- Isolation (only applications concerned by the schema component should be affected) + +The recommended way to design the GUP schema is to split the schema into schema components, each component being defined as a separate XML schema document, with its own namespace. + +Components are assembled together as optional content (minOccurs=0, maxOccurs=1) of an construct. + +Common attributes as defined in Liberty ID-WSF Data Services Template Specification [13] shall be used for GUP. + +### 6.4.1 Example + +To illustrate this, it is shown how the the top-level component of the GUP schema could be defined as the "concatenation" of four different sub-schemas. + +The component is defined by an XML schema document. The component namespace is defined by the targetNamespace of the schema. + +The sub-schemas used in the definition are referenced by (1) their namespace declaration in the element and (2) by importing their corresponding schema documents (). + +Finally, the top-level component is defined by a content-model that concatenates the four sub-schemas under an contract. We now illustrate how we can build components out of other components. Let it be assumed that there are four components (c1 ... c4), represented by four distinct namespaces (nsc1 ... nsc4), described in four different schema files; they can be put together as follows: + +``` + + + + + + + + + + + + + + + + + + + +``` + +Note the benefits that we achieve using this way of doing things: + +- Modularity: the GUP schema does not consist of a monolithic standalone document, but rather a collection of small schemas that can be designed and maintained independently. +- Extensibility: at every level, it is possible to extend the schema by simply adding one child to the . +- Readability +- Support for versioning + +## 6.5 Data Referencing Language + +For referencing components, the GUP Component Language (GCL) shall be used. + +The GCL is a subset of the XPath 1.0 language [XPath reference], as defined below. + +**Editor's note:** we only use the name "GCL" as a way to avoid confusion. In the final version of this document, the name will be skipped or replaced. + +**Editor's note:** we need to define the LA name to identify the GCL for the discovery service. Probably something like: `xpath-gup-gcl`. + +### 6.5.1 Language Syntax for GCL + +The following subset of XPath shall be supported by GCL: + +- only the `child::` and `attribute::` axis of XPath are supported +- predicates are supported + +- expressions inside predicates only apply to attribute nodes or element nodes with no children +- expressions inside predicates shall be of the form "node value" where ranges over the usual string and arithmetic operators. +- boolean negation is supported +- ordinal predicates are supported (e.g. [1], [last()], [position()<=2]) + +NOTE: AND and OR are not part of the syntax because they can be emulated by already existing language constructs: A[exp1 AND exp2] corresponds to A[exp1][exp2]; A[exp1 OR exp2] corresponds to A[exp1] | A[exp2]. + +### 6.5.2 Semantics + +The semantics of the GCL language can be defined as follows: + +1. we evaluate the GCL expression on the document using the XPath semantics leading to a set of nodes +2. for each node in the set, we also include its descendants and its ancestors + +This defines a new document, sub-document of the original document. + +## 6.6 GUP metadata + +The 3GPP Rp and Rg interfaces define the management of data and metadata for user profile components. For the sake of uniformity, Rp and Rg do not define special procedures for metadata management. Rather, we distinguish between user profile components (or data components) and metadata components. + +We define two kinds of metadata components: access control metadata and mapping metadata. The definition of other metadata components (e.g. billing, etc.) is beyond the scope of this specification. + +In the following definition, ResourceIDGroup and SelectType are defined by Liberty Alliance. + +# 7 GUP bindings + +Liberty messages are designed so that they can be mapped onto various transport or transfer protocols, however Liberty defines and recommends a specific binding to the SOAP protocol, in order to convey such messages. + +Following a similar approach, the following clause describes how to map GUP messages to the SOAP protocol. Another bindings are not precluded, but are not described in this specification. + +This specification defines the binding of the GUP interfaces and procedures to SOAP protocol (defined in "Simple Object Access Protocol (SOAP) 1.1" [5]). Identically to Liberty Alliance specifications, and as described in Liberty ID-WSF SOAP Binding Specification [14]. GUP procedures address specific aspects of message exchange (such as to which system entity the message is to be sent, message correlation, the mechanics of message exchange, or security context), mainly at the SOAP header part of the message + +In order to address the specific aspects of GUP procedures message exchange functionality this specification reuses a number of SOAP header blocks defined as part of the Liberty ID-WSF SOAP Binding Specification described in [14]. + +Another bindings are not precluded, but are not described in this specification. + +## 7.1 General principles + +SOAP provides a mechanism for exchanging structured and typed information between peers using XML. It is a generic protocol which can also be used to carry remote procedure calls. Each SOAP message has an element "Envelope" and its immediate child elements "Header" and "Body". SOAP carries the GUP procedure elements in its body part in compliance with the SOAP standard "Simple Object Access Protocol (SOAP) 1.1" [5]. The GUP Procedure elements are placed immediately below the Body element. If there are several requests or responses, the GUP Procedure elements are carried one after another. + +GUP SOAP messages are specified to run over standard http, see "Hypertext Transfer Protocol – HTTP/1.1" [6] as specified in "Simple Object Access Protocol (SOAP) 1.1" [5] but implementations may also support other transport mechanisms. If any SOAP level error is reported, no application data are returned. The used SOAP binding and error reporting mechanisms are defined in Liberty ID-WSF SOAP Binding Specification [14]. + +Liberty ID-WSF Data Services Template Specification [13] currently defines some generic XML attributes and data types. In general, it is recommended to make use of such information already in place, rather than defining GUP-specific elements to provide the same functionality + +**Editor's note:** we should mention that the "Document" style is preferred for SOAP messages. + +3GPP GUP SOAP messages will be declared according to the SOAP "document style" (I.e., 3GPP GUP messages will be placed directly into the body portion of the SOAP envelope, either as-is or encoded). This preference (versus the rpc option) provides a number of benefits as: + +- Full use of XML can be done, enabling description and validation of high-level business documents +- A rigid business relationship between Web Services consumers and providers is not required. +- Asynchronous processing is improved +- Object exchange becomes more flexible. + +**Editor's note:** we should provide the corresponding WSDL files in the appendix. + +**Editor's note:** we should mention how security is taken care of (work with SA3). + +## 7.2 GUP headers + +Liberty Alliance defines some headers needed when passing around messages. Since Liberty Alliance only defines a SOAP binding, these headers are defined in terms of the SOAP protocol. But this is NOT mandatory, as mentioned in [soap-binding], + +"Although this binding [SOAP binding] is the only one given in this specification, other protocols could be used to convey ID-\* messages, with appropriateness depending on the protocol selected and the target operational context. " + +In the context of GUP, a set of abstract headers are defined. They are needed by the messages exchanged between the various parties, against the Rp and Rg interfaces. The information contained in these headers will be described as XML data even though the binding may decide to map the information using a different syntax (e.g. ASCII, ASN.1, etc.). In the following clauses, namespace "S" corresponds to the SOAP namespace. + +Normative bindings for the GUP headers to SOAP are provided in the (Annex E). + +### 7.2.1 Correlation header + +#### 7.2.1.1 Description + +The **correlation** header block provides a means for correlating messages. Message correlation is achieved by using the messageID attribute to identify individual messages. Additionally, a message may refer to another message by setting its refToMessageID attribute to the value of the messageID of the message of interest. + +#### 7.2.1.2 Content + +The content of the correlation header can be defined using the following type. + +``` + + + + + + + + +``` + +### 7.2.2 Provider header + +#### 7.2.2.1 Description + +This header block provides a means for a sender to claim that it 545 + +is represented by a given providerID value. The sender may also claim that it is a member of a given affiliation. Such claims are generally verifiable by receivers by looking up these values in the sender's metadata. + +#### 7.2.2.2 Content + +``` + + + + + + + +``` + +### 7.2.3 ProcessingContext header + +#### 7.2.3.1 Description + +This header block may be employed by a sender to signal to a receiver that the latter should add a specific additional facet to the overall *processing context* in which any action(s) are invoked as a result of processing any message also conveyed in the overall message. + +#### 7.2.3.2 Content + +``` + + + + + + + + + +``` + +### 7.2.4 Consent header + +#### 7.2.4.1 Description + +The Consent header block element MAY be employed by either a requester or a receiver. For example, the Principal may be using a Liberty-enabled client or proxy (common in the wireless world), and in that sort of environment the mobile operator may cause the Principal's terminal (AKA: cell phone) to prompt the principal for consent for some interaction. + +#### 7.2.4.2 Content + +``` + + + + + + + +``` + +### 7.2.5 UsageDirective header + +#### 7.2.5.1 Description + +Participants in the ID-WSF framework may need to indicate the privacy policy associated with a message. To facilitate this, senders, acting as either a client or a server, may add one or more UsageDirective header blocks to the message being sent. A UsageDirective header appearing in a request message expresses *intended usage*. A UsageDirective header appearing in a response expresses *how* the receiver of the response is to use the response data. + +#### 7.2.5.2 Content + +``` + + + + + + + + + +``` + +### 7.2.6 ServiceInstanceUpdate header + +#### 7.2.6.1 Description + +It may be necessary for an entity receiving a message to indicate that messages from the sender should be directed to a different endpoint, or that they wish a different credential to be used than was originally specified by the entity for access to the requested resource. + +The ServiceInstanceUpdate header allows a message receiver to indicate that a new endpoint, new credentials, or new security mechanisms should be employed by the sender of the message. + +The use of this header block allows the sender of the message to convey updates to security tokens, essentially providing a token renewal mechanism. This is not discussed further in this specification. + +#### 7.2.6.2 Content + +``` + + + + + + + + + + + + + + + + + +``` + +### 7.2.7 Timeout header + +#### 7.2.7.1 Description + +A requesting entity may wish to indicate that they would like a request to be processed within some specified amount of time. Such an entity would indicate their wish via the Timeout header block. + +#### 7.2.7.2 Content + +``` + + + + + + +``` + +### 7.2.8 CredentialsContext header + +#### 7.2.8.1 Description + +The receiver of a GUP message might indicate that credentials supplied in the request did not meet its policy in allowing access to the requested resource. The header block allows such policies to be expressed to a GUP requester. + +#### 7.2.8.2 Content + +``` + + + + + + + + + +``` + +### 7.2.9 wsse:Security header + +#### 7.2.9.1 Description + +Relevant security information is communicated in the Security header. The details for the specific bindings are provided in the Annexes. + +#### 7.2.9.2 Content + +The details of the content for the specific binding are provided in the Annexes. + +### 7.2.10 is:UserInteraction header + +In some scenarios it might be necessary for GUP Servers and/or RAFs to interact with the owner of GUP component data exposed in order to e.g. ask for explicit end-user consent for the release of the requested information. To this end, GUP messages may include a header, which controls the possibilities that GUP Servers and/or RAFs have to engage in interactions with end-users when serving a request from a GUP Requestor. + +#### 7.2.10.1 Description + +#### 7.2.10.2 Content + +## 7.3 GUP Data types + +GCL: need to check how the namespaces are handled by XPath. We may need to provide some namespace declarations in the GCL to resolve namespaces. + +### 7.3.1 GUP Resource identifiers + +According to Liberty Discovery Service specification [17], the Liberty ResourceId element takes the format of a URI, and it could therefore host different types of identifiers. + +In general, the GUP ResourceId shall be used as the Liberty ResourceId and it shall take the form: + +"GUP:""/" + +Where: + +datavalue = The data value of the identifier as specified in the part. + +identifier = The identifier that is being used in the part of the subscriber identity. + +A definitive list of Identifiers are defined in table X below: + +**Table 9.3.1: Composition of the Subscriber Identity** + +| Identifier | Comment | Example (informative) | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| IMSI | Subscriber's IMSI as defined in 3GPP TS 23.003 [21]. | GUP:234150999999999/IMSI | +| MSISDN | Subscriber's MSISDN as defined in 3GPP TS 23.003 [21]. The number shall be specified in international format (excluding the "+" symbol). | GUP:447748000000/MSISDN | +| IMS Private Identity | Subscriber's IMS Private Identity as defined in 3GPP TS 23.003 [21]. | GUP:user.name@abc.examplemno.com/IMPI | +| IMS Public Identity | Subscriber's IMS Public Identity as defined in 3GPP TS 23.003 [21]. | GUP:user.name@xyz.examplemno.com/IMPU | +| E-mail Address | An e-mail address of the subscriber, in the format specified in IETF RFC 2821 [19]. | GUP:user.name@mail.examplemno.com/MAILTO | +| Generic Data Reference | A format which is locally defined by an HPLMN. | GUP:av23asd46fjh230dm/GEN | + +Editors note: There might be situations where these encoding schemes conflict with syntax of some identifiers (e.g. SIP addresses). This is FFS. + +Editors note: The content of this clause may be moved to the 3GPP TS 23.003 once this specification is under change control. + +In particular, the identifier named "Generic Data Reference" could host an identifier that is meaningless for the application (e.g., a binary piece of data or a pseudonym), but understood by the GUP server. This mechanism would allow that applications are able to reference a specific user, without revealing the user 's real identity to the application (such as his/her MSISDN etc). Such identifier could be also obfuscated for even better privacy protection, as stated in Liberty DST [13]. + +### 7.3.2 GUP SelectType + +The SelectType is the type that must be defined by any service willing to be instantiated as a data service template (see Annex A). For GUP, we need to distinguish two cases: simple queries (asking for a portion of one given user profile) and list queries (asking of the list of profiles available from data repository). The SelectType consists of a choice between the two cases. + +Case 1 (regular queries): the type permits to access portions of the user profile. It consists of a GCL and an optional component name. GCLType and ComponentType are defined as strings. + +Case 2 (list queries): the type represent the search filtering criteria, represented as a string. + +``` + + + + + + + + + + + + + + + + + + + + + +``` + +### 7.3.3 Access control metadata type + +The access control metadata component is defined by type authorizationType. It consists of a resource (defined using the ResourceIDGroup), the component defined by a GCL expression embedded in a SelectType, a list of requestors, an action (read or write) and a condition. + +The details of the condition language to be used for access control is left for further study. Therefore, it represented as in the authorizationType. + +``` + + + + + + + + + + +``` + +``` + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +**Editor's note: for the condition, we should try to align with already existing standards such as XACML.** + +An example of an authorization component is given below: + +``` + + + john.smith@3gpp.org + + /gup/identity + + + *@3gpp.org + + + true + + + + + +``` + +### 7.3.4 Mapping metadata type + +A mapping metadata component maps one or more user profile components expressed using the GCL into the RAF that manages this data. + +The GCL expression is defined using the of Liberty Alliance that we redefine for GUP. + +The RAF is defined using the . + +``` + + + + + + + + + + + + + + + + +``` + +An example of a mapping metadata component is given below: + +``` + + + john.smith@3gpp.org + + /gup/identity + + ids.3gpp.org + + +``` + +## 7.4 GUP error codes + +The following result codes are defined for GUP: + +| | | | | +|------------------------|--------------------------|------------------------|---------------------------| +| ActionNotAuthorized | ActionNotSupported | AllReturned | ChangeHistoryNotSupported | +| ChangedSinceReturnsAll | DataTooLong | ExistsAlready | ExtensionNotSupported | +| Failed | InvalidData | InvalidResourceID | InvalidSelect | +| MissingNewDataElement | MissingResourceIDElement | MissingSelect | ModifiedSince | +| NoMoreElements | NoMultipleAllowed | NoMultipleResources | OK | +| TimeOut | UnexpectedError | RequestorNotAuthorized | InvalidRequestorData | + +**Editor's note:** we should mention the ones that are not part of LA. + +RequestorNotAuthorized, InvalidRequestorData, InvokeID codes. + +For the next clause, we should use the table to identify which result codes can be used or not. Use ~~RequestorNotAuthorized~~ to show that the result code is not applicable. + +## 7.5 GUP Message Types + +### 7.5.1 Create messages + +#### 7.5.1.1 Overview + +The Create message is used by the application to add a new profile component. There may be more than one Create elements in one message. The CreateResponse message provides the result of the procedure. Create request type. + +#### 7.5.1.2 Create request type + +LA does not offer any message type for creation. We need to provide our own type. + +``` + + + + + + + + + + + + + + + + + + + + + +``` + +#### 7.5.1.3 Create response type + +``` + + + + + + + + + +``` + +#### 7.5.1.4 Create example + +Based on the above types, we can create and elements as follows: + +``` + + +``` + +We provide a simple example to illustrate how these elements will be used. + +``` + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +``` + + + +``` + +### 7.5.2 Delete messages + +#### 7.5.2.1 Overview + +#### 7.5.2.2 Delete Request type + +LA does not offer any message type for deletion. We need to provide our own type. + +``` + + + + + + +``` + +``` + + + + + + + + + + + + + +``` + +#### 7.5.2.3 Delete Response type + +``` + + + + + + + + + + + + +``` + +#### 7.5.2.4 Delete example + +``` + + + + + + + + + + + + +``` + +### 7.5.3 Modify messages + +#### 7.5.3.1 Overview + +#### 7.5.3.2 Modify request type + +This type is already defined by LA Data Service Template as ModifyType in liberty-idwsf-dst-v2.0-01.xsd. + +#### 7.5.3.3 Modify response type + +This type is already defined by LA Data Service Template as ModifyResponseType in liberty-idwsf-dst-v2.0-01.xsd. + +#### 7.5.3.4 Modify example + +``` + + sahuguet@lucent.com + + + + + + 12 + 12 + -1 + + + + + + + + + + 908 582 6491 + + + + + +``` + +A positive response for the first modification request. + +``` + + + +``` + +A negative response for the second modification request. + +``` + + + +``` + +**Editor's note:** This clause is to be written in a similar way than clause 8.3.1. + +### 7.5.4 Query messages + +#### 7.5.4.1 Overview + +#### 7.5.4.2 Query request type + +This type is already defined by LA Data Service Template as QueryType in liberty-idwsf-dst-v2.0-01.xsd. + +#### 7.5.4.3 Query response type + +This type is already defined by LA Data Service Template as QueryResponseType in liberty-idwsf-dst-v2.0-01.xsd. + +#### 7.5.4.4 Query example + +``` + + john.smith@3gpp.org + + + + + + + +``` + +The answer is: + +``` + + + + + + John + Smith + + + + + + + busy + + + + +``` + +### 7.5.5 Subscribe messages + +#### 7.5.5.1 Overview + +#### 7.5.5.2 Subscribe request type + +This type is already defined by LA Data Service Template as SubscribeType in liberty-idwsf-dst-v2.0-01.xsd. + +#### 7.5.5.3 Subscribe example + +``` + + + + + ChangedElements + gupServer@3gpp.org + gupServer@3gpp.org + type of subscription defined by the service + type of trigger defined by the service + + +``` + +### 7.5.6 Unsubscribe message + +#### 7.5.6.1 Overview + +#### 7.5.6.2 UnSubscribe request type + +This type is already defined by LA Data Service Template as SubscribeType in liberty-idwsf-dst-v2.0-01.xsd. + +#### 7.5.6.3 UnSubscribe example + +``` + + + + gupServer@3gpp.org + + +``` + +**Editor's note:** This clause is to be written in a similar way than clause 8.3.1 + +### 7.5.7 Notify message + +#### 7.5.7.1 Overview + +#### 7.5.7.2 Notify response type + +This type is already defined by LA Data Service Template as SubscribeResponseType in liberty-idwsf-dst-v2.0-01.xsd. + +#### 7.5.7.3 Notify example + +``` + + + + + + + not available + + + + + +``` + +### 7.5.8 List message + +#### 7.5.8.1 Overview + +#### 7.5.8.2 List request type + +This type is already defined by LA Data Service Template as QueryType in liberty-idwsf-dst-v2.0-01.xsd. + +#### 7.5.8.3 List response type + +This type is already defined by LA Data Service Template as QueryResponseType in liberty-idwsf-dst-v2.0-01.xsd. + +#### 7.5.8.4 List example + +``` + + + + + + + + +``` + +``` + +``` + +``` + + + + + ... + + + +``` + +Editor's note: the details of the result of a List query need to defined. What is the syntax, what is the information returned, etc.? + +# 8 Rp interface + +## 8.1 General Principles + +The Rp interface corresponds to the interaction between the GUP server and the GUP data repositories. + +## 8.2 Procedures + +The various procedures of the Rp interface are described in terms of the messages defined in clause 9. + +### 8.2.1 Create Component procedure + +#### 8.2.1.1 General description + +The Create Component procedure is used by the application to add a new profile component in the contacted repository. + +The procedure consists of a request and response defined by the Create and CreateResponse messages. + +#### 8.2.1.2 Detailed Behaviour + +The RAF entity checks the request element contents as described in clause 9.1. In particular the RAF entity checks whether the component can be created for the given subscriber based on the existing policies. There is no requirement for the user profile with the given subscriber identity to exist beforehand. However the subscriber identity (as well as other given data) shall be valid according to the operator's policies and subscriber addressing rules. If the component exists already, the error "InvalidResourceID" is returned. + +Next the RAF entity checks the correctness of the provided XML data against the XML Schema related to the given ComponentType. If the data are faulty or missing, the result code "InvalidData" or "MissingNewDataElement" is returned respectively. + +Finally, before creating the component instance, the RAF entity checks that the requestor data allow the operation based on the authorisation information attached to the component type and/or to the specific subscriber data. If any given part of the data cannot be created due to lack of authorisation, the Create Component procedure shall fail with the result code "ActionNotAuthorized" or "RequestorNotAuthorized". The latter result code is returned if the failure is caused by the given requestor information. The Create element processing shall also fail in other error cases, but the other Create elements may be handled normally. + +If the request message contains several Create elements, but the receiver implementation supports only one in a single message, the result code "NoMultipleResources" is returned. If a single Create element contains several CreateItems, but the receiver implementation supports only one, the result code "NoMultipleAllowed" is returned. + +CreateResponse is sent with the status information. If not otherwise stated above, the contents of the Status are as described in clause 9.1.10. + +#### 8.2.1.3 List of result codes + +The following result codes may appear in CreateResponse: + +- ActionNotAuthorized; +- ActionNotSupported; +- ExtensionNotSupported; +- Failed; +- InvalidData; + +- InvalidRequestorData; +- InvalidResourceID; +- MissingNewDataElement; +- MissingResourceIDElement; +- NoMultipleAllowed; +- NoMultipleResources; +- OK; +- RequestorNotAuthorized; +- TimeOut; +- UnexpectedError; + +### 8.2.2 Delete Component procedure + +#### 8.2.2.1 General description + +The Delete Component procedure is used by the application to delete one or more profile components. + +The procedure consists of a request and response defined by the Delete and DeleteResponse messages. + +#### 8.2.2.2 Detailed Behaviour + +If the referenced component exists and the deletion is authorized, the component is deleted. + +The RAF entity checks the request element contents as described in clause 9.1. In particular the RAF entity checks whether the component exists. If the component does not exist, the error "InvalidResourceID" is returned. + +Finally, before deleting the component instance, the RAF entity checks that the requestor data allow the operation based on the authorisation information attached to the component type and/or to the specific subscriber data. If not authorized, the whole Delete element processing shall fail with the result code "ActionNotAuthorized" or "RequestorNotAuthorized". The latter result code is returned if the failure is caused by the given requestor information. The Delete element processing shall also fail in other error cases, but the other Delete elements may be handled normally. + +If the request message contains several Delete elements, but the receiver implementation supports only one in a single message, the result code "NoMultipleResources" is returned. If a single Delete element contains several DeleteItems, but the receiver implementation supports only one, the result code "NoMultipleAllowed" is returned. + +DeleteResponse is sent with the status information. If not otherwise stated above, the contents of the Status are as described in clause 9.1.10. + +#### 8.2.2.3 List of result codes + +The following result codes may appear in DeleteResponse: + +- ActionNotAuthorized +- ActionNotSupported +- ExtensionNotSupported +- Failed +- InvalidRequestorData +- InvalidResourceID + +- MissingResourceIDElement +- NoMultipleAllowed +- NoMultipleResources +- OK +- RequestorNotAuthorized +- TimeOut +- UnexpectedError + +### 8.2.3 Modify Data procedure + +#### 8.2.3.1 General description + +The Modify Data procedure is used by the application to modify profile components. One message may contain several modification request elements and one such element may contain several changes to the profile data of the specific subscriber. + +The procedure consists of a request and response defined by the Modify and ModifyResponse messages. + +#### 8.2.3.2 Detailed Behavior + +This procedure is defined according to the Liberty ID-WSF Data Services Template Specification [13] and the functionality is exactly as defined by that specification for all those aspects that are clearly determined there. This document is just intending to profile such specification. Note however that the use of the DS is mandatory in GUP just for certain specific scenarios, being optional in another. + +The RAF entity checks the request element contents as described in clause 9.1. If no errors are found and the modification is authorized, the contents of NewData are stored in the place identified by the ResourceID and Select parameters. + +The RAF entity verifies that the given data matches with the data structure identified by the Select element. As a generic rule the upper level data structure need not be created beforehand when providing data for the leaf elements. However there may be profile component specific rules about which data are mandated to be provided. + +If the request message contains several Modify elements, but the receiver implementation supports only one in a single message, the result code "NoMultipleResources" is returned. If a single Modify element contains several Modification items, but the receiver implementation supports only one, the result code "NoMultipleAllowed" is returned. + +If any error is found in the request data, no modifications shall be made to any data as requested by this modification element. However the possible other modify elements in the message shall be processed normally. + +ModifyResponse is sent with the status information. If not otherwise stated above, the contents of the contents of the Status are as described in clause 9.1.10. + +#### 8.2.3.3 List of result codes + +The following result codes may appear in responses: + +| | | | | +|-----------------------------------|--------------------------|--------------------------|---------------------------| +| ActionNotAuthorized | ActionNotSupported | AllReturned | ChangeHistoryNotSupported | +| ChangedSinceReturnsAll | DataTooLong | ExistsAlready | ExtensionNotSupported | +| Failed | InvalidData | InvalidResourceID | InvalidSelect | +| MissingNewDataElement | MissingResourceIDElement | MissingSelect | ModifiedSince | +| NoMoreElements | NoMultipleAllowed | NoMultipleResources | OK | +| TimeOut | UnexpectedError | RequestorNotAuthorized | InvalidRequestorData | + +### 8.2.4 Read Data procedure + +#### 8.2.4.1 General description + +The Read Data procedure is used by the application to read profile data. One message may contain several Query elements. + +The procedure consists of a request and response defined by the Query and QueryResponse messages. + +#### 8.2.4.2 Detailed Behaviour + +This procedure is defined according to the Liberty ID-WSF Data Services Template Specification [13] and the functionality is exactly as defined by that specification for all those aspects that are clearly determined there. This document is just intending to profile such specification. Note however that the use of the DS is mandatory in GUP just for certain specific scenarios, being optional in another. + +The RAF entity checks the request element contents as described in clause 9.1. If the ResourceIDGroup and Select have appropriate values and the query is authorized, the requested data are returned in the response element. + +If the request message contains several Query elements, but the receiver implementation supports only one in a single message, the result code "NoMultipleResources" is returned. If a single Query element contains several Query Items, but the receiver implementation supports only one, the result code "NoMultipleAllowed" is returned. + +If any error is found in the request data when processing a QueryItem, the data already processed for the other QueryItem's may be returned, but the current QueryItem shall fail without any other results than the status element which shows the reason for the error and indicates the faulty QueryItem. In this case the remaining QueryItems in the Query element shall not be processed. However the previous and next Query elements (if they exist) shall be processed normally. + +QueryResponse elements are sent with the data and status information. If not otherwise stated above, the contents of the Status are as described in clause 9.1.10. + +#### 8.2.4.3 List of result codes + +The following result codes may appear in responses: + +| | | | | +|---------------------------|--------------------------|--------------------------|---------------------------| +| ActionNotAuthorized | ActionNotSupported | AllReturned | ChangeHistoryNotSupported | +| ChangedSinceReturnsAll | DataTooLong | ExistsAlready | ExtensionNotSupported | +| Failed | InvalidData | InvalidResourceID | InvalidSelect | +| MissingNewDataElement | MissingResourceIDElement | MissingSelect | ModifiedSince | +| NoMoreElements | NoMultipleAllowed | NoMultipleResources | OK | +| Timeout | UnexpectedError | RequestorNotAuthorized | InvalidRequestorData | + +### 8.2.5 Subscribe To Data procedure + +#### 8.2.5.1 General description + +The Subscribe To Data procedure is used by the application to request notifications about changes in the profile component data. + +The procedure consists of a request and response defined by the Subscribe message. + +#### 8.2.5.2 Detailed Behavior + +This procedure is defined according to the Liberty ID-WSF Data Services Template Specification [13] and the functionality is exactly as defined by that specification for all those aspects that are clearly determined there. This document is just intending to profile such specification. Note however that the use of the DS is mandatory in GUP just for certain specific scenarios, being optional in another. + +The RAF entity checks the request element contents as described in clause 9.1. If there is no authority to retrieve any data defined by the Select elements, the status shall indicate "Failed" with the second level status code "ActionNotAuthorized" or "RequestorNotAuthorized". + +If the FilterData indicates immediate notification, the Notify Data procedure carries the current values for the data defined by the Select element(s). If a time interval is specified in FilterData, the Notify Data procedure is invoked only after that time period has passed after the Subscribe element was received. In this case the Notify element shall contain the current values of all the changed data structures defined by the Select element(s). + +The RAF entity creates and returns an InvokeID that shall be unique within the RAF. Once an InvokeID has been deleted because it is no longer required, another InvokeID with the same value can be created, without failing the uniqueness test. The InvokeID is used by the Notify Data procedure to link the notification to the Subscribe element. + +A SubscribeResponse element is sent with the status information. If not otherwise stated above, the contents of the Status are as described in clause 9.1.10. + +#### 8.2.5.3 List of result codes + +The following result codes may appear in responses: + +| | | | | +|-----------------------------------|---------------------------|--------------------------|--------------------------------------| +| ActionNotAuthorized | ActionNotSupported | AllReturned | ChangeHistoryNotSupported | +| ChangedSinceReturnsAll | DataTooLong | ExistsAlready | ExtensionNotSupported | +| Failed | InvalidData | InvalidResourceID | InvalidSelect | +| MissingNewDataElement | MissingResourceIDEElement | MissingSelect | ModifiedSince | +| NoMoreElements | NoMultipleAllowed | NoMultipleResources | OK | +| Timeout | UnexpectedError | RequestorNotAuthorized | InvalidRequestorData | + +- InvalidFilterData where is defined. Not part of LA. + +### 8.2.6 Unsubscribe To Data procedure + +#### 8.2.6.1 General description + +The Unsubscribe To Data procedure is used by the application to cancel one or more existing subscriptions to notification of data change. + +The procedure consists of a request and response defined by the Unsubscribe message. + +#### 8.2.6.2 Detailed Behavior + +This procedure is defined according to the Liberty ID-WSF Data Services Template Specification [13] and the functionality is exactly as defined by that specification for all those aspects that are clearly determined there. This document is just intending to profile such specification. Note however that the use of the DS is mandatory in GUP just for certain specific scenarios, being optional in another. + +The RAF entity checks that whether there is an active subscription for the given InvokeID. If a subscription is active, it will be cancelled. In other cases the error InvalidInvokeID or MissingInvokeID is returned. + +An Unsubscribe response element is sent with the status information. If not otherwise stated above, the contents of the Status are as described in clause 9.1.10. + +#### 8.2.6.3 List of result codes + +The following result codes may appear in responses: + +| | | | | +|-----------------------------------|--------------------------------------|-----------------------------------|---------------------------| +| ActionNotAuthorized | ActionNotSupported | AllReturned | ChangeHistoryNotSupported | +| ChangedSinceReturnsAll | DataTooLong | ExistsAlready | ExtensionNotSupported | +| Failed | InvalidData | InvalidResourceID | InvalidSelect | +| MissingNewDataElement | MissingResourceIDEElement | MissingSelect | ModifiedSince | +| NoMoreElements | NoMultipleAllowed | NoMultipleResources | OK | +| Timeout | UnexpectedError | RequestorNotAuthorized | InvalidRequestorData | + +- InvalidInvokeID +- MissingInvokeID +- Not defined by LA. + +### 8.2.7 Notify Data procedure + +#### 8.2.7.1 General description + +The Notify Data procedure is invoked by the RAF when the data which was identified in Subscribe To Data Changes Notification procedure changes, or when the invoked Subscribe To Data procedure requested immediate sending of the current values of the referenced data. The procedure identifies the changed data and provides the new values. + +The procedure consists of a response defined by the SubscribeResponse message. + +#### 8.2.7.2 Detailed Behaviour + +This procedure is defined according to the Liberty ID-WSF Data Services Template Specification [13] and the functionality is exactly as defined by that specification for all those aspects that are clearly determined there. This document is just intending to profile such specification. Note however that the use of the DS is mandatory in GUP just for certain specific scenarios, being optional in another. + +The Notify Data procedure is executed when the data for which there is a subscription to change notification have changed in the GUP repository. The application can identify its subscription by the InvokeID element. The element named Data contains the changed data. + +When the application has processed this request, it shall immediately return a response message to the RAF. + +A NotifyResponse element is sent with the status information. If not otherwise stated above, the contents of the Status are as described in clause 9.1.10. + +**Editor's note: To be completed with the handling of error conditions** + +#### 8.2.7.3 List of result codes + +The following result codes may appear in responses: + +| | | | | +|-----------------------------------|-------------------------------------|-----------------------------------|--------------------------------------| +| ActionNotAuthorized | ActionNotSupported | AllReturned | ChangeHistoryNotSupported | +| ChangedSinceReturnsAll | DataTooLong | ExistsAlready | ExtensionNotSupported | +| Failed | InvalidData | InvalidResourceID | InvalidSelect | +| MissingNewDataElement | MissingResourceIDElement | MissingSelect | ModifiedSince | +| NoMoreElements | NoMultipleAllowed | NoMultipleResources | OK | +| Timeout | UnexpectedError | RequestorNotAuthorized | InvalidRequestorData | + +- InvalidInvokeID +- MissingInvokeID +- Not defined by LA + +# 9 Rg interface + +## 9.1 General principles + +The Rg interface corresponds to the interaction between the GUP client application and the GUP server. + +## 9.2 Procedures + +The various procedures of the Rg interface are described in terms of the messages defined in clause 9. + +### 9.2.1 Create Component procedure + +#### 9.2.1.1 General description + +The Create Component procedure is used by the application to add a new profile component in the contacted repository. + +The procedure consists of a request and response defined by the Create and CreateResponse messages. + +#### 9.2.1.2 Detailed Behaviour + +The GUP server entity checks the request element contents as described in clause 9.1. In particular the RAF entity checks whether the component can be created for the given subscriber based on the existing policies. There is no requirement for the user profile with the given subscriber identity to exist beforehand. However the subscriber identity (as well as other given data) shall be valid according to the operator's policies and subscriber addressing rules. If the component exists already, the error "InvalidResourceID" is returned. + +Next the RAF entity checks the correctness of the provided XML data against the XML Schema related to the given ComponentType. If the data are faulty or missing, the result code "InvalidData" or "MissingNewDataElement" is returned respectively. + +Finally, before creating the component instance, the RAF entity checks that the requestor data allow the operation based on the authorisation information attached to the component type and/or to the specific subscriber data. If any given part of the data cannot be created due to lack of authorisation, the Create Component procedure shall fail with the result code "ActionNotAuthorized" or "RequestorNotAuthorized". The latter result code is returned if the failure is caused by the given requestor information. The Create element processing shall also fail in other error cases, but the other Create elements may be handled normally. + +If the request message contains several Create elements, but the receiver implementation supports only one in a single message, the result code "NoMultipleResources" is returned. If a single Create element contains several CreateItems, but the receiver implementation supports only one, the result code "NoMultipleAllowed" is returned. + +CreateResponse is sent with the status information. If not otherwise stated above, the contents of the Status are as described in clause 9.1.10. + +#### 9.2.1.3 List of result codes + +The following result codes may appear in CreateResponse: + +- ActionNotAuthorized; +- ActionNotSupported; +- ExtensionNotSupported; +- Failed; +- InvalidData; + +- InvalidRequestorData; +- InvalidResourceID; +- MissingNewDataElement; +- MissingResourceIDElement; +- NoMultipleAllowed; +- NoMultipleResources; +- OK; +- RequestorNotAuthorized; +- TimeOut; +- UnexpectedError; + +### 9.2.2 Delete Component procedure + +#### 9.2.2.1 General description + +The Delete Component procedure is used by the application to delete one or more profile components. + +The procedure consists of a request and response defined by the Delete and DeleteResponse messages. + +#### 9.2.2.2 Detailed Behaviour + +If the referenced component exists and the deletion is authorized, the component is deleted. + +The GUP server entity checks the request element contents as described in clause 9.1. In particular the RAF entity checks whether the component exists. If the component does not exist, the error "InvalidResourceID" is returned. + +Finally, before deleting the component instance, the RAF entity checks that the requestor data allow the operation based on the authorisation information attached to the component type and/or to the specific subscriber data. If not authorized, the whole Delete element processing shall fail with the result code "ActionNotAuthorized" or "RequestorNotAuthorized". The latter result code is returned if the failure is caused by the given requestor information. The Delete element processing shall also fail in other error cases, but the other Delete elements may be handled normally. + +If the request message contains several Delete elements, but the receiver implementation supports only one in a single message, the result code "NoMultipleResources" is returned. If a single Delete element contains several DeleteItems, but the receiver implementation supports only one, the result code "NoMultipleAllowed" is returned. + +DeleteResponse is sent with the status information. If not otherwise stated above, the contents of the Status are as described in clause 9.1.10. + +#### 9.2.2.3 List of result codes + +The following result codes may appear in DeleteResponse: + +- ActionNotAuthorized +- ActionNotSupported +- ExtensionNotSupported +- Failed +- InvalidRequestorData +- InvalidResourceID + +- MissingResourceIDElement +- NoMultipleAllowed +- NoMultipleResources +- OK +- RequestorNotAuthorized +- TimeOut +- UnexpectedError + +### 9.2.3 Modify Data procedure + +#### 9.2.3.1 General description + +The Modify Data procedure is used by the application to modify profile components. One message may contain several modification request elements and one such element may contain several changes to the profile data of the specific subscriber. + +The procedure consists of a request and response defined by the Modify and ModifyResponse messages. + +#### 9.2.3.2 Detailed Behavior + +This procedure is defined according to the Liberty ID-WSF Data Services Template Specification [13] and the functionality is exactly as defined by that specification for all those aspects that are clearly determined there. This document is just intending to profile such specification. Note however that the use of the DS is mandatory in GUP just for certain specific scenarios, being optional in another. + +The GUP server entity checks the request element contents as described in clause 9.1. If no errors are found and the modification is authorized, the contents of NewData are stored in the place identified by the ResourceID and Select parameters. + +The RAF entity verifies that the given data matches with the data structure identified by the Select element. As a generic rule the upper level data structure need not be created beforehand when providing data for the leaf elements. However there may be profile component specific rules about which data are mandated to be provided. + +If the request message contains several Modify elements, but the receiver implementation supports only one in a single message, the result code "NoMultipleResources" is returned. If a single Modify element contains several Modification items, but the receiver implementation supports only one, the result code "NoMultipleAllowed" is returned. + +If any error is found in the request data, no modifications shall be made to any data as requested by this modification element. However the possible other modify elements in the message shall be processed normally. + +ModifyResponse is sent with the status information. If not otherwise stated above, the contents of the contents of the Status are as described in clause 9.1.10. + +#### 9.2.3.3 List of result codes + +The following result codes may appear in responses: + +- ActionNotAuthorized +- ActionNotSupported +- ChangeHistoryNotSupported +- ExtensionNotSupported +- Failed +- InvalidData + +- InvalidRequestorData +- InvalidResourceID +- InvalidSelect +- MissingNewDataElement +- MissingResourceIDElement +- MissingSelect +- ModifiedSince +- NoMultipleAllowed +- NoMultipleResources +- OK +- RequestorNotAuthorized +- TimeOut +- UnexpectedError + +### 9.2.4 Read Data procedure + +#### 9.2.4.1 General description + +The Read Data procedure is used by the application to read profile data. One message may contain several Query elements. + +The procedure consists of a request and response defined by the Query and QueryResponse messages. + +#### 9.2.4.2 Detailed Behaviour + +This procedure is defined according to the Liberty ID-WSF Data Services Template Specification [13] and where not otherwise stated the functionality is exactly as defined by that specification. Note however that GUP does not mandate the use of the Discovery service. + +The RAF entity checks the request element contents as described in clause 9.1. If the ResourceIDGroup and Select have appropriate values and the query is authorized, the requested data are returned in the response element. + +If the request message contains several Query elements, but the receiver implementation supports only one in a single message, the result code "NoMultipleResources" is returned. If a single Query element contains several Query Items, but the receiver implementation supports only one, the result code "NoMultipleAllowed" is returned. + +If any error is found in the request data when processing a QueryItem, the data already processed for the other QueryItem's may be returned, but the current QueryItem shall fail without any other results than the status element which shows the reason for the error and indicates the faulty QueryItem. In this case the remaining QueryItems in the Query element shall not be processed. However the previous and next Query elements (if they exist) shall be processed normally. + +QueryResponse elements are sent with the data and status information. If not otherwise stated above, the contents of the Status are as described in clause 9.1.10. + +#### 9.2.4.3 List of result codes + +The following result codes may appear in responses: + +- ActionNotAuthorized +- ActionNotSupported + +- AllReturned +- ChangeHistoryNotSupported +- ChangedSinceReturnsAll +- ExtensionNotSupported +- Failed +- InvalidRequestorData +- InvalidResourceID +- InvalidSelect +- MissingResourceIDEElement +- MissingSelect +- NoMultipleAllowed +- NoMultipleResources +- OK +- RequestorNotAuthorized +- TimeOut +- UnexpectedError + +### 9.2.5 Subscribe To Data procedure + +#### 9.2.5.1 General description + +The Subscribe To Data procedure is used by the application to request notifications about changes in the profile component data. + +The procedure consists of a request and response defined by the Subscribe message. + +#### 9.2.5.2 Detailed Behavior + +This procedure is defined according to the Liberty ID-WSF Data Services Template Specification [13] and the functionality is exactly as defined by that specification for all those aspects that are clearly determined there. This document is just intending to profile such specification. Note however that the use of the DS is mandatory in GUP just for certain specific scenarios, being optional in another. + +The GUP server entity checks the request element contents as described in clause 9.1. If there is no authority to retrieve any data defined by the Select elements, the status shall indicate "Failed" with the second level status code "ActionNotAuthorized" or "RequestorNotAuthorized". + +If the FilterData indicates immediate notification, the Notify Data procedure carries the current values for the data defined by the Select element(s). If a time interval is specified in FilterData, the Notify Data procedure is invoked only after that time period has passed after the Subscribe element was received. In this case the Notify element shall contain the current values of all the changed data structures defined by the Select element(s). + +The RAF entity creates and returns an InvokeID that shall be unique within the RAF. Once an InvokeID has been deleted because it is no longer required, another InvokeID with the same value can be created, without failing the uniqueness test. The InvokeID is used by the Notify Data procedure to link the notification to the Subscribe element. + +A SubscribeResponse element is sent with the status information. If not otherwise stated above, the contents of the Status are as described in clause 9.1.10. + +#### 9.2.5.3 List of result codes + +The following result codes may appear in responses: + +- ActionNotAuthorized +- ActionNotSupported +- ExtensionNotSupported +- Failed +- InvalidFilterData +- InvalidRequestorData +- InvalidResourceID +- InvalidSelect +- MissingResourceIDEElement +- MissingSelect +- NoMultipleAllowed +- NoMultipleResources +- OK +- RequestorNotAuthorized +- TimeOut +- UnexpectedError + +### 9.2.6 Unsubscribe To Data procedure + +#### 9.2.6.1 General description + +The Unsubscribe To Data procedure is used by the application to cancel one or more existing subscriptions to notification of data change. + +The procedure consists of a request and response defined by the Subscribe message. + +#### 9.2.6.2 Detailed Behavior + +This procedure is defined according to the Liberty ID-WSF Data Services Template Specification [13] and the functionality is exactly as defined by that specification for all those aspects that are clearly determined there. This document is just intending to profile such specification. Note however that the use of the DS is mandatory in GUP just for certain specific scenarios, being optional in another. + +The GUP server entity checks that whether there is an active subscription for the given InvokeID. If a subscription is active, it will be cancelled. In other cases the error InvalidInvokeID or MissingInvokeID is returned. + +An Unsubscribe response element is sent with the status information. If not otherwise stated above, the contents of the Status are as described in clause 9.1.10. + +#### 9.2.6.3 List of result codes + +The following result codes may appear in responses: + +- ActionNotSupported +- ExtensionNotSupported + +- Failed +- InvalidInvokeID +- InvalidRequestorData +- MissingInvokeID +- NoMultipleAllowed +- NoMultipleResources +- OK +- TimeOut +- UnexpectedError + +### 9.2.7 Notify Data procedure + +#### 9.2.7.1 General description + +The Notify Data procedure is invoked by the RAF when the data which was identified in Subscribe To Data Changes Notification procedure changes, or when the invoked Subscribe To Data procedure requested immediate sending of the current values of the referenced data. The procedure identifies the changed data and provides the new values. + +The procedure consists of a response defined by the SubscribeResponse message. + +#### 9.2.7.2 Detailed Behaviour + +This procedure is defined according to the Liberty ID-WSF Data Services Template Specification [13] and the functionality is exactly as defined by that specification for all those aspects that are clearly determined there. This document is just intending to profile such specification. Note however that the use of the DS is mandatory in GUP just for certain specific scenarios, being optional in another. + +The Notify Data procedure is executed when the data for which there is a subscription to change notification have changed in the GUP repository. The application can identify its subscription by the InvokeID element. The element named Data contains the changed data. + +When the application has processed this request, it shall immediately return a response message to the RAF. + +A NotifyResponse element is sent with the status information. If not otherwise stated above, the contents of the Status are as described in clause 9.1.10. + +**Editor's note: To be completed with the handling of error conditions** + +#### 9.2.7.3 List of result codes + +The following result codes may appear in responses: + +- ActionNotSupported +- ExtensionNotSupported +- Failed +- InvalidData +- InvalidInvokeID +- MissingInvokeID +- OK +- TimeOut + +- UnexpectedError + +# 10 Authentication, authorization and security + +## 10.1 Principles + +GUP Architecture and Protocols include secure mechanisms for the transfer of User Profile data to, from and between authorised entities. Access to User Profile data shall only be permitted in an authorised and secure manner. + +Security mechanisms to be applied over Rg and Rp reference points are defined by Liberty ID-WSF Security Mechanisms [15] specification. + +In addition to managing the registration and discovery of GUP Server and profile information a **Discovery Service (DS)** as defined in Liberty ID-WSF Discovery Service Specification [17] may also act as a centralized policy information and decision point issuing the necessary Authentication and/or Authorization statements. + +Interactions of GUP requestors towards the Discovery Service shall be as described in Liberty ID-WSF Discovery Service Specification [17]. + +The GUP architecture with respect to Authentication, Authorization and Security is summarized in Figure XXX. + +![Diagram of GUP Authentication, Authorization and Security architecture. A red dashed box labeled 'Scope of 3GPP GUP' contains three stacked components: 'Client Application' at the top, 'GUP server' in the middle, and 'RAF' at the bottom. The 'Client Application' is connected to the 'GUP server' via a vertical line labeled 'Rg'. The 'GUP server' is connected to the 'RAF' via a vertical line labeled 'Rp'. Outside the red box, to the right, is a 'Discovery Service (DS)' component. A horizontal line connects the 'Client Application' to the 'Discovery Service (DS)', with the text 'Client authenticates to DS and fetches security info required over Rg' above it. Another horizontal line connects the 'GUP server' to the 'Discovery Service (DS)', with the text 'Server registers security requirements over Rg' below it.](f943b07ab747bfd85e302e5a31c20ba8_img.jpg) + +``` +graph TD; subgraph Scope_of_3GPP_GUP [Scope of 3GPP GUP]; CA[Client Application] ---|Rg| GS[GUP server]; GS ---|Rp| RAF[RAF]; end; CA ---|Client authenticates to DS and fetches security info required over Rg| DS[Discovery Service (DS)]; GS ---|Server registers security requirements over Rg| DS; +``` + +Diagram of GUP Authentication, Authorization and Security architecture. A red dashed box labeled 'Scope of 3GPP GUP' contains three stacked components: 'Client Application' at the top, 'GUP server' in the middle, and 'RAF' at the bottom. The 'Client Application' is connected to the 'GUP server' via a vertical line labeled 'Rg'. The 'GUP server' is connected to the 'RAF' via a vertical line labeled 'Rp'. Outside the red box, to the right, is a 'Discovery Service (DS)' component. A horizontal line connects the 'Client Application' to the 'Discovery Service (DS)', with the text 'Client authenticates to DS and fetches security info required over Rg' above it. Another horizontal line connects the 'GUP server' to the 'Discovery Service (DS)', with the text 'Server registers security requirements over Rg' below it. + +**Figure 1: GUP Authentication, Authorization and Security architecture.** + +Liberty ID-WSF Security Mechanisms Specification [15], Liberty ID-WSF SOAP Binding Specification [14] and Liberty ID-WSF Discovery Service Specification [17] provide normative content for the implementation of the security mechanisms that apply to GUP. + +The following clauses under this clause of the specification define how the different security mechanisms described in the referred Liberty specifications shall be used in the context of GUP. + +The following clauses specify the required set of security mechanisms that shall be supported for GUP. + +## 10.2 Security and Authentication + +### 10.2.1 Rg interface (client application / GUP server) + +GUP specifications shall be applicable for multiple deployment scenarios where different security, privacy and trust considerations apply. The applications that may apply GUP Rg reference point may be targeted for different purposes e.g. third party applications for value added services or operator's own applications for subscription management. + +Liberty Alliance Security Mechanisms [15] specification defines a set of combinations of peer authentication and message authentication mechanisms necessary to accommodate various deployment scenarios. Each combination is defined by a URI with the form *urn:liberty:security:2003-08:peer mechanism:message mechanism*. It is up to the security policy of the operator to choose which combination of methods to apply taking into account the security domains where the client and server reside. + +#### 10.2.1.1 Peer Entity Authentication and Transport Layer Channel Protection + +The Peer entity authentication mechanisms required for GUP Rg reference point are based on the mechanisms prescribed by Liberty ID-WSF Security Mechanisms [15] specification, which rely upon the inherent security properties supplied by SSL 3.0 [SSL] or TLS (as specified in 3GPP TS 33.203 [12]) sometimes referred to as transport-level security (also including means for its confidentiality and integrity protection). + +Confidentiality and Integrity at the transport channel is ensured making use of suitable SSL/TLS cipher suites (see clause 12.2.3 for list of supported cipher suites). + +The server is authenticated to the client using a x.509 server-side certificate. In general the support of client-side certificates in the context of GUP is not mandated but mutual authentication of the communicating peers may be also supported. + +#### 10.2.1.2 Message Authentication + +Third party applications external to the Mobile Network Operator domain shall only apply Rg reference point. More precisely, third party applications external to the Mobile Network Operator domain acting as a GUP Requestor over the Rg reference point shall at least support *urn:liberty:security:2003-08:TLS:SAML* as defined by Liberty Alliance Security Mechanisms [15] Specification. The support of other message authentication mechanisms (e.g. *urn:liberty:security:2004-04:TLS:Bearer* and/or *urn:liberty:security:2003-08:TLS:X509*) is optional for third party applications external to the Mobile Network Operator domain. However the use of the *null* message authentication profile (e.g. *urn:liberty:security:2003-08:TLS:null*) is not recommended for the Rg reference point. + +Internal applications to the Mobile Network Operator domain acting as a GUP Requestor over the Rg reference point shall at least support *urn:liberty:security:2003-08:TLS:null* as defined by Liberty Alliance Security Mechanisms [15] Specification. The support of other message authentication mechanisms (e.g. *urn:liberty:security:2003-08:TLS:SAML*, *urn:liberty:security:2004-04:TLS:Bearer* and/or *urn:liberty:security:2003-08:TLS:X509*) is optional for Internal applications to the Mobile Network Operator domain. + +GUP Server shall at least support *urn:liberty:security:2003-08:TLS:null* and *urn:liberty:security:2003-08:TLS:SAML* as defined by Liberty Alliance Security Mechanisms [15] Specification. The support of other message authentication mechanisms (e.g. *urn:liberty:security:2004-04:TLS:Bearer* and/or *urn:liberty:security:2003-08:TLS:X509*) is optional for the GUP Server. + +GUP requestors over Rg reference point may utilise a discovery service as a Trusted Authority providing essential security related information (e.g. preferences in terms of peer entity and message authentication mechanism to be used and authentication and/or authorization assertions). Different policies may be followed in the use of the services of a discovery service. It may be used by different applications in different ways: per each operation, occasionally or not at all. In general terms, third party applications belonging to external security domains shall need to use the services of a discovery service as a normal step, but in operator's services it may not be needed at all. + +A Discovery Service as defined by Liberty Alliance Discovery Service [17] specification is able to inform GUP requestors of the peer entity and message authentication mechanisms to be used. Additionally, and in the event that a particular deployment of GUP requires the use of the Web Services SAML security profile (e.g. *urn:liberty:security:2003-08:TLS:SAML* or *urn:liberty:security:2003-08:ClientTLS:SAML*) the Discovery Service shall provide the necessary Authentication assertions as defined by Liberty Alliance Security Mechanisms [15] specification. + +A Discovery Service may also be capable of providing necessary bearer tokens in the event the Bearer token security profile (e.g. *urn:liberty:security:2004-04:TLS:Bearer* or *urn:liberty:security:2004-04:ClientTLS:Bearer*) is used. + +### 10.2.2 Rp interface (GUP server / RAF) + +The required security mechanism for the Rp interface is **urn:liberty:security:2003-08:ClientTLS:null**. + +- The server and the RAF communicate over a secure channel protected by SSL/TLS (see 12.2.3 for list of supported cipher suites). + +NOTE: Since the number of RAFs is limited and the connections between the server and the RAFs are long-lived (multiple requests sent on the same connections), this should not create too much overhead for either key management or cryptographic processing. + +The support of other message authentication mechanisms (e.g. *urn:liberty:security:2003-08:TLS:SAML*, *urn:liberty:security:2004-04:TLS:Bearer* and/or *urn:liberty:security:2003-08:TLS:X509*) is optional for the Rp reference point. + +### 10.2.3 Cryptographic requirements + +For signing and verification of protocol messages, communicating entities SHOULD use certificates and private keys that are distinct from the certificates and private keys applied for SSL or TLS channel protection (in accordance to Liberty Alliance Security Mechanisms [15] specification) + +The cipher suites to be used for peer-wise encryption are: + +- TLS\_RSA\_WITH\_RC4\_128\_SHA +- TLS\_RSA\_WITH\_3DES\_EDE\_CBC\_SHA +- TLS\_DHE\_DSS\_WITH\_3DES\_EDE\_CBC\_SHA +- TLS\_RSA\_WITH\_AES\_CBC\_SHA +- TLS\_DHE\_DSS\_WITH\_AES\_CBC\_SHA + +GUP entities shall at least support **TLS\_RSA\_WITH\_3DES\_EDE\_CBC\_SHA** and **TLS\_RSA\_WITH\_AES\_CBC\_SHA** cipher suites. The support of other cipher suites is optional. + +### 10.2.4 End-to-End Example (informative) + +The following diagram represents a possible interaction between a client application and a GUP server. + +![Sequence diagram of GUP security flow showing interactions between GUP Requestor, Discovery Service, GUP Server, and GUP Repository.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` + +sequenceDiagram + participant GUP Requestor + participant Discovery Service + participant GUP Server + participant GUP Repository + + Note left of GUP Requestor: 0. GUP Requestor requires a GUP Component + + GUP Requestor-->>Discovery Service: 1. [LAP ID-WSF Soap Bindings] +[LAP ID-WSF DS Lookup Request] + Discovery Service-->>GUP Requestor: 2. [LAP ID-WSF Soap Bindings] +[LAP ID-WSF DS Lookup Response] +[SAML assertion signed by DS] + GUP Requestor->>GUP Server: 3. [LAP ID-WSF Soap Bindings] +[LAP ID-WSF DST Query Request] +[SAML assertion signed by DS] + GUP Server->>GUP Repository: 4. [LAP ID-WSF Soap Bindings] +[LAP ID-WSF DST Query Request] + GUP Repository-->>GUP Server: 5. [LAP ID-WSF Soap Bindings] +[LAP ID-WSF DST Query Response] + GUP Server-->>GUP Requestor: 6. [LAP ID-WSF Soap Bindings] +[LAP ID-WSF DST Query Response] + + Note right of GUP Requestor: Rg + Note right of GUP Server: Rp + +``` + +Sequence diagram of GUP security flow showing interactions between GUP Requestor, Discovery Service, GUP Server, and GUP Repository. + +Figure 2: GUP security flow + +### 10.2.5 Example of GUP wsse:Security header (informative) + +The following header authenticates the application defined by application1@3gpp.org. + +``` + +< + + + + +``` + +``` + + + + +http://gupserver.com + + + + + + + + + + + + + +http:// application1@3gpp.org + + + + + + + + + +... + + + + + + + + + + + + +``` + +## 10.3 Authorization + +### 10.3.1 Principles + +Liberty ID-WSF Security Mechanisms Specification [15] defines OPTIONAL mechanisms to convey authorization and resource access information (supplied by a Trusted Authority), which may be necessary to access a service. Authentication and Authorization Authorities may be co-located. + +In the context of GUP and when the operator's policies so require, it is recommended that a Discovery Service as described by Liberty ID-WSF Discovery Service Specification [17] also acts as a Trusted Authority issuing Authorization assertions. + +In general, GUP authorization can be seen to consist of the following functional components: + +- Management of authorization related data (authorization rules) which also refer to actual authorized data +- Access/storage of the authorization rules +- Encapsulation of a set of authorization rules (privacy policy) together with the transported actual data. +- Execution of authorization logic based on the pre-defined authorization rules and information received in the request or otherwise related to the request + +The functional components are discussed more in the following clauses. + +### 10.3.2 Authorization related data + +#### 10.3.2.1 Authorization attributes + +Authorization attributes are defined to be used as basic input elements of the authorization rules and thus as a basis for the authorization decisions. It is not required that all the authorization attributes defined hereafter are included in a request. + +The following types of authorization attributes are considered: + +- Identity of the target subscriber (or a group of subscribers) – the GUP subscriber; +- Component type being accessed and more detailed data reference; +- Identity of the requestor (application ID and end-user ID) or group of requestors; +- The Web Services Security SAML Profile [wss-saml] shall be used as the means by which GUP requestor over Rg and/or Rp authenticate to the recipient (i.e. GUP Server and GUP Repository respectively). Each communicating peer performs message level authentication by demonstrating proof of possession of a subject confirmation key. The assertion issuer (i.e. Discovery Service) binds the subject confirmation key to the assertion by signing the assertion. This attestation assures the consumer of the assertion that the subject confirmation key is that of the intended sender. Thus the senders subject confirmation key can be recognized by the recipient as belonging to the remote peer. +- Requestor related data received in the request as Authorization Assertions + +The authorization model supports the issuance of assertions, which convey information regarding the resource to be accessed, the entity attempting to access the resource, the mechanism by which the accessing entity must use to demonstrate its identity to the recipient and the ability for the accessing entity to access the resource on behalf of another system entity. Thus the authorization model supports a constrained proxy mechanism, which permits a proxy (the sender) to access the resource on behalf of some other system entity. + +Processing rules for the generation of authorization assertions is normatively defined at Liberty ID-WSF Security Mechanisms Specification [15]. + +- Requested Operation (Query, Modify, Create, Delete, Subscribe, List); +- Other attributes (e.g. the time schedule) related to the request case; + +- Privacy Policy included in the request +- Liberty ID-WSF SOAP Binding Specification [14] defines a SOAP Header Block in which GUP requestors could express policy in terms of intent of usage of the requested data if released. +- Other data relevant for access control included in the request + - Liberty ID-WSF SOAP Binding Specification [14] defines a SOAP Header Block in which GUP requestors could indicate whether the end-user consented the request. + - Identity information related to active proxies in the communicating channel may be conveyed in , and schema elements within the SOAP Security Header as defined in Liberty ID-WSF Security Mechanisms Specification [15] specification. + - Session status of the communicating peers may be conveyed in and schema elements within the SOAP Security Header as defined in Liberty ID-WSF Security Mechanisms Specification [15] specification. + - Resource access information is captured in a schema elements within the SOAP Security Header as defined in Liberty ID-WSF Security Mechanisms Specification [15] specification. The purpose of this statement is to convey sufficient information regarding the accessing entity and the resource for which access is being attempted. + +#### 10.3.2.2 Authorization rules + +The basic set of authorization rules define to whom, to which part of data and for which purpose the authorization is given. All or some of the Authorization data considered above may be applicable. + +GUP requestors over Rg and/or Rp reference points shall include relevant authorization data in the SOAP message requests. In particular Authorization assertions shall be conveyed following the processing rules defined at Liberty ID-WSF Security Mechanisms Specification [15]. + +The authorization rules consist of the following built-in elements: + +- authorization attributes and/or references to pre-defined (commonly used) contents of attributes +- references to the actual GUP data +- actions (e.g. the decision, encapsulation of the privacy policy). + +#### 10.3.2.3 Management of authorization related data + +The GUP procedures defined for the Rp and Rg reference points (see the clauses 8 and 9) may be used for managing authorization related data (using GUP metadata components). + +### 10.3.3 Execution of authorization logic + +The authorization logic compares the information conveyed in the request (and possible additional information related to the moment when the request is received) with the information defined in the authorization rules. When the logic leads to a decision to accept the request in principle, the requested data is compared with the authorized set of data. If discrepancies are found a GUP authorization entity may either restrict to reply to the authorized content or deny the request. Note that this depends on the policy in the GUP authorization entity and the nature of the request. + +### 10.3.4 Roles of GUP entities related to the authorization + +Figure 10.1 shows the logical entities involved in GUP authorization. + +![Figure 12.3.4.1. Logical entities of GUP authorization. The diagram shows three main components: Application, Management Entity, and Authorisation Rules (represented as a cylinder). Arrows indicate data flow: 'Rp/Rg: requestor data' from Application to Authorisation Logic; 'Rp/Rg: management operations' from Management Entity to Authorisation Rules; a bidirectional 'Read, Response' between Authorisation Logic and Authorisation Rules; and an arrow from Authorisation Logic to a Decision diamond.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +``` + +graph TD + Application[Application] -- "Rp/Rg: requestor data" --> AL[Authorisation Logic] + ME[Management Entity] -- "Rp/Rg: management operations" --> AR[(Authorisation Rules)] + AL <--> |"Read, Response"| AR + AL --> D{Decision} + +``` + +Figure 12.3.4.1. Logical entities of GUP authorization. The diagram shows three main components: Application, Management Entity, and Authorisation Rules (represented as a cylinder). Arrows indicate data flow: 'Rp/Rg: requestor data' from Application to Authorisation Logic; 'Rp/Rg: management operations' from Management Entity to Authorisation Rules; a bidirectional 'Read, Response' between Authorisation Logic and Authorisation Rules; and an arrow from Authorisation Logic to a Decision diamond. + +**Figure 12.3.4.1. Logical entities of GUP authorization** + +#### 10.3.4.1 GUP Requestor + +GUP requestors over Rg and/or Rp reference points shall include relevant authorization data in the SOAP message requests. In particular, Authorization assertions issued and received from a Discovery Service as defined in Liberty ID-WSF Discovery Service Specification [17] shall be conveyed following the processing rules defined at Liberty ID-WSF Security Mechanisms Specification [15]. + +Other relevant authorization attributes as defined in clause 12.2.2.1 of this specification may be also present in the requests. + +#### 10.3.4.2 GUP server and RAF + +The GUP Server and RAF (including the Data Repository) have access to the authorization rules. The interface between the authorization related data storage and GUP Server (and RAF) is out of the scope of this specification. Note that the GUP Server and RAF may act as data storage entities. The GUP Server or the RAF (or both of them) are responsible for the execution of the authorization logic. + +The authorization issues handled by the GUP Server typically concern the GUP profile and GUP Component level issues; the authorization handled by RAF may be based on more detailed data references (items inside a GUP component). The set of authorization attributes specified for GUP can be used by both the GUP Server and the RAF. + +The GUP Server and the RAF may also add to the transported actual data, a SOAP Header Block as defined in Liberty ID-WSF SOAP Binding Specification [14] including privacy policies that the GUP requestor shall follow when using, storing and/or distributing the received data. If during the execution of the authorization logic, GUP Server or RAF find out that further authorization information from the end-user is required in order to decide whether or not the request shall be served, the user interaction mechanisms defined in Liberty Alliance Interaction Service [22] specification may be used. + +#### 10.3.4.3 Management entity + +The authorization rules can be managed by the authorized entities: e.g + +- the entity administrating the GUP Data Storage; +- the RAF and/or GUP Server; + +- the GUP Subscriber itself. + +The GUP Subscriber is normally allowed to manage a limited set of his own user profile data, e.g., certain GUP Components or certain data inside a GUP Component. Additionally, there might be restrictions on the allowed operations. + +The entity administering the GUP Data Storage may define common or default authorization rules for GUP Subscribers. The entity may also pre-define contents for authorization attributes, e.g. user groups, to which the authorization rules can refer. The entity administering the GUP Data Storage may also manage GUP Subscriber specific authorization rules (e.g., on behalf of the GUP Subscriber). + +# --- Annex A (normative): Component Data Definitions + +According to clause 5 of TS23.240 [1], a Generic User Profile consists of a number of independent GUP Components. This Annex defines the content, semantics and specific processing rules of the different GUP Data Components. + +Note: For Rel-6 only the HSS IMS GUP component is defined. Further releases of this specification will define additional components. + +## --- A.1 HSS IMS GUP Component definition + +The purpose of this annex is to provide GUP Profile Component definition for the IMS data of the HSS. + +### A.1.1 General description + +The following Figure A.3 gives an outline of the UML model of the logical view of the HSS IMS GUP Components. The main Component is called HSSIMSData. + +Each element in that figure represents a part of the XML Schema structure, either a GUP Component or a lower level block of data contained in a GUP Component. Elements marked with the same background colour make up an independently manageable GUP Component, whose root is marked with '<>'. + +All HSS IMS GUP Components can be managed with the procedures provided by GUP. + +Component and attribute naming has been taken mainly from 3GPP TS 23.008 [8] where appropriate. The details about the specific attributes shown in the picture are described in others specs. The ones related Cx protocol are described in the 3GPP TS 29.228 [7] and the ones related Sh interface are described in the 3GPP TS 29.328 [10]. + +The identified set of GUP data elements with regard to the IMS HSS component should receive different treatment (only read or both read/write access rights), depending on the nature of the data and the nature of the application requesting the data (e.g. provisioning application). In order to provide such differentiated treatment access control mechanisms shall be applied. These access control mechanisms should take into consideration the rights that can be offered over each attribute. + +![UML Class Diagram showing the logical data model of the HSS IMS GUP Components. The diagram includes classes: SCSCFSelection, HSSIMSData, Registration, PrivateUserIdentity, CoreNetworkServicesAuthorization, ServiceProfile, SubscriptionIdentificationAndNumbering, AuthenticationAndCiphering, ImplicitlyRegisteredIdSet, InitialFilterCriteria, ApplicationServer, RepositoryData, TriggerPoint, ServicePointTrigger, RequestURI, Method, SIPHeader, SessionCase, and SessionDescription. Relationships include associations and generalizations.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +classDiagram + class SCSCFSelection { + -MandatoryCapability: String + -OptionalCapability: String [] + -PreferredSCSCF: String [] + } + class HSSIMSData { + <> + -HSSIMSDataKey: Key + } + class Registration { + -SCSCFName: String + -DiameterClientAddressOfSCSCF: String + } + class PrivateUserIdentity { + -Identity: Key + -SubscriptionIdentificationAndNumberingReference: Ref + -AuthenticationAndCipheringReference: Ref + } + class CoreNetworkServicesAuthorization { + -SubscribedMediaProfileIdentifier: String + } + class ServiceProfile { + <> + -ServiceProfileKey: Key + -SubscriptionIdentificationAndNumberingReference: Ref [] + } + class SubscriptionIdentificationAndNumbering { + <> + -PublicUserIdentity: Key + -BarringIndication: String + -ListOfAuthorizedVisitedNetworkIdentifiers: String [] + -ServicesRelatedToUnregisteredState: String + -PrivateUserIdentityReference: Ref [] + -ServiceProfileReference: Ref + -ImplicitlyRegisteredIdSetReference: Ref + } + class AuthenticationAndCiphering { + <> + -AuthenticationAndCipheringKey: Key + -K: String + -Algorithm: String + -AMF: String + -PrivateUserIdentityReference: Ref + } + class ImplicitlyRegisteredIdSet { + <> + -ImplicitlyRegisteredIdSetKey: Key + -RegistrationStatus: String + -SubscriptionIdentificationAndNumberingReference: Ref + } + class InitialFilterCriteria { + -Priority: String + } + class ApplicationServer { + -ServerName: String + -DefaultHandling: String + -ServiceInfo: String + } + class RepositoryData { + -AdditionalShData: String + } + class TriggerPoint { + -ConditionTypeCNF: String + } + class ServicePointTrigger { + -ConditionNegated: String + -Group: String + } + class RequestURI { + -RequestURI: String + } + class Method { + -Method: String + } + class SIPHeader { + -Header: String + -Content: String + } + class SessionCase { + -SessionCase: String + } + class SessionDescription { + -Line: String + -Content: String + } + + SCSCFSelection "1" -- "1" HSSIMSData + HSSIMSData "1" -- "1" Registration + HSSIMSData "1" -- "0..*" PrivateUserIdentity + PrivateUserIdentity "1" -- "1" SubscriptionIdentificationAndNumbering + PrivateUserIdentity "1" -- "1" AuthenticationAndCiphering + CoreNetworkServicesAuthorization "0..1" -- "1" ServiceProfile + ServiceProfile "1" -- "0..*" SubscriptionIdentificationAndNumbering + SubscriptionIdentificationAndNumbering "1" -- "0..*" ImplicitlyRegisteredIdSet + ServiceProfile "1" -- "0..*" InitialFilterCriteria + InitialFilterCriteria "1" -- "1" ApplicationServer + InitialFilterCriteria "1" -- "0..1" TriggerPoint + TriggerPoint "1" -- "1..*" ServicePointTrigger + ServicePointTrigger <|-- RequestURI + ServicePointTrigger <|-- Method + ServicePointTrigger <|-- SIPHeader + ServicePointTrigger <|-- SessionCase + ServicePointTrigger <|-- SessionDescription + SubscriptionIdentificationAndNumbering "1" -- "0..*" RepositoryData + +``` + +UML Class Diagram showing the logical data model of the HSS IMS GUP Components. The diagram includes classes: SCSCFSelection, HSSIMSData, Registration, PrivateUserIdentity, CoreNetworkServicesAuthorization, ServiceProfile, SubscriptionIdentificationAndNumbering, AuthenticationAndCiphering, ImplicitlyRegisteredIdSet, InitialFilterCriteria, ApplicationServer, RepositoryData, TriggerPoint, ServicePointTrigger, RequestURI, Method, SIPHeader, SessionCase, and SessionDescription. Relationships include associations and generalizations. + +Figure A.3 Logical data model of the HSS IMS GUP Components + +#### A.1.1.1 XML Schema files for HSS IMS GUP Components + +XML Schema files attached to this specification combine together whole HSS IMS GUP Component data. XML Schema files are intended to be used by an XML parser. + +Table A.1 lists HSS IMS GUP Components and XML Schema files that include those. CommonDataTypes file contains common data types, i.e. it is not a stand alone GUP Component on its own. + +Table A.1 HSS IMS GUP Components in XML Schema files + +| HSS IMS GUP Component | XML Schema file | +|----------------------------|--------------------------------| +| AuthenticationAndCiphering | AuthenticationAndCiphering.xsd | + +| | | +|----------------------------------------|--------------------------------------------| +| HSSIMSData | HSSIMSData.xsd | +| ImplicitlyRegisteredIdSet | ImplicitlyRegisteredIdSet.xsd | +| SubscriptionIdentificationAndNumbering | SubscriptionIdentificationAndNumbering.xsd | +| ServiceProfile | ServiceProfile.xsd | +| Component independent data | XML Schema file | +| - | CommonDataTypes.xsd | + +### A.1.2 Element addressing + +Contents for HSS IMS GUP Components can be addressed with XPath representation format as an input parameter for select clauses. Each GUP Component has a unique key. + +#### Example + +Following Select element addresses the BarringIndication element in the SubscriptionIdentificationAndNumbering GUP Component. Public User Identity is specified by ResourceID in the procedure message element, e.g. Query. + +``` + +``` + +### A.1.3 Void + +## --- A.2 HSS IMS GUP Component structure + +HSS IMS GUP Component model includes following Components: + +- HSSIMSData +- AuthenticationAndCiphering +- SubscriptionIdentificationAndNumbering +- ServiceProfile + +This model is mainly based on the HSS data described in 3GPP TS 23.008 [8]. Authentication information is described in TS 33.203 [12] and TS 33.102 [11]. Data relationships are mainly based on descriptions from 3GPP TS 23.228 [9], 3GPP TS 29.328 [10] and 3GPP TS 29.228 [7]. + +### A.2.1 HSSIMSData GUP Component + +HSS IMS Data contains S-CSCF Selection-, IMS location, charging- and Private User Identity information. + +HSS IMS Data contains also following data for Component linking purposes. + +- HSSIMSDataKey + - HSS IMS Data Key is a primary key to uniquely identify HSS IMS Data Component. + - This value must be unique within all HSS IMS Data Components. + +#### A.2.1.1 SCSCFSelection + +S-CSCF Selection contains the following data, which are described in 3GPP TS 23.008 [8]. + +- MandatoryCapability +- OptionalCapability +- PreferredSCSCF (optional parameter) + +These data shall be offered only for provisioning purposes. + +#### A.2.1.2 IMS Location + +IMS Location contains the following data, which are described in 3GPP TS 23.008 [8]. + +- SCSCFName +- DiameterClientAddressOfSCSCF (optional parameter) + +#### A.2.1.3 PrivateUserIdentity + +Private User Identity contains the following data, which is described in 3GPP TS 23.008 [8]. + +- Identity (Private User Identity) + - This data shall be offered only for provisioning purposes. + +### A.2.2 AuthenticationAndCiphering GUP Component + +Authentication and Ciphering contains the following data, which are described in 3GPP TS 33.102 [11]. + +- K +- Algorithm +- AMF + +K parameter can contain either Secret Key or Encrypted Secret Key value. The encryption algorithm is implementation specific. + +These data shall be offered only for provisioning purposes. + +### A.2.3 SubscriptionIdentificationAndNumbering GUP Component + +Subscription Identification And Numbering Component contains the following data, which are described in 3GPP TS 23.008 [8]. + +- PublicUserIdentity +- BarringIndication (This data shall be offered only for provisioning purposes) +- ListOfAuthorizedVisitedNetworkIdentifiers (This data shall be offered only for provisioning purposes) +- ServicesRelatedToUnregisteredState + +Public User Identity is a primary key element for the Subscription Identification And Numbering Component. + +#### A.2.3.1 RepositoryData + +Repository Data contains additional Sh-interface data, which are described in 3GPP TS 29.328 [10]. + +- AdditionalShData + +### A.2.4 ServiceProfile GUP Component + +The present clause presents the Service Profile GUP Component contents, which are defined based on the 3GPP TS 29.228 [7]. + +#### A.2.4.1 CoreNetworkServiceAuthorization + +Core Network Service Authorization contains the following data, which are described in 3GPP TS 29.228 [7]. + +- SubscribedMediaProfileIdentifier + +This data shall be offered only for provisioning purposes + +#### A.2.4.2 InitialFilterCriteria + +Initial Filter Criteria contains the following data, which are described in 3GPP TS 29.228 [7]. All data under Initial Filter Criteria are described in 3GPP TS 29.228 [7]. + +- Priority + +##### A.2.4.2.1 ApplicationServer + +The present clause presents the Application Server element contents, which are defined based on the 3GPP TS 29.228 [7]. + +- ServerName +- DefaultHandling +- ServiceInfo + +##### A.2.4.2.2 TriggerPoint + +The present clause presents the Trigger Point element contents, which are defined based on the 3GPP TS 29.228 [7]. + +- ConditionTypeCNF + +###### A.2.4.2.2.1 ServicePointTrigger + +The present clause presents the Service Point Trigger element contents, which are defined based on the 3GPP TS 29.228 [7]. + +Corresponding data element in Cx reference point is SePoTri. + +- ConditionNegated +- Group + +Service Point Trigger contains one of the following data structures described below. + +###### A.2.4.2.2.1.1 RequestURI + +The present clause presents the Request URI element contents, which are defined based on the 3GPP TS 29.228 [7]. + +- RequestURI + +###### A.2.4.2.2.1.2 Method + +The present clause presents the Method element contents, which are defined based on the 3GPP TS 29.228 [7]. + +- Method + +###### A.2.4.2.2.1.3 SIPHeader + +The present clause presents the SIP Header element contents, which are defined based on the 3GPP TS 29.228 [7]. + +- Header +- Content + +###### A.2.4.2.2.1.4 SessionCase + +The present clause presents the Session Case element contents, which are defined based on the 3GPP TS 29.228 [7]. + +- SessionCase + +###### A.2.4.2.2.1.5 SessionDescription + +The present clause presents the Session Description element contents, which are defined based on the 3GPP TS 29.228 [7]. + +- Line +- Content + +## --- A.3 Common Data Types + +GUP Components share some common data types defined in the CommonDataTypes.xsd - XML Schema file. + +That XML Schema file includes the following elements or element types used by other GUP XML Schema files: + +- Extension + - Will be used as an extension element +- ExtensionType + - Extension element type +- GenericDataType + - Will be used as a generic data type +- GenericComponentReferenceType + - Will be used as a generic Component reference type + +## A.4 Data Services Template Checklist tables + +GUP is an instance of a data service as described by Liberty Alliance Data Services Template [13] specification and all its stipulations are hereby incorporated unless expressly waived or modified in this specification. + +This clause presents the checklist tables as defined in Liberty Alliance Data Service Template [13] specification filled-in with the values corresponding of the use of defined GUP Data component. + +**Table A.4.1/1: General Service Parameters (1/2)** + +| Parameter | Value | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | urn:3gpp:gup-hss-ims:2005-04 | +| Discovery Options |

Discovery Options MAY be supported
If a Discovery Service is employed, the following
Discovery Option Keywords as defined by Liberty ID-WSF
Data Services Template Specification [13] MAY be used:

urn:liberty:dst:allPaths
urn:liberty:dst:can:extend
urn:liberty:dst:changeHistoryS supported
urn:liberty:dst:extend
urn:liberty:dst:fullXPath
urn:liberty:dst:multipleResources
urn:liberty:dst:multipleQueryItems
urn:liberty:dst:multipleModification
urn:liberty:dst:noModify
urn:liberty:dst:noPagination
urn:liberty:dst:noQuery
urn:liberty:dst:noQuerySubscriptions
urn:liberty:dst:noSorting
urn:liberty:dst:noStatic
urn:liberty:dst:noSubscribe

No specific Discovery Option Keyword is defined for the HSS-IMS GUP Data Component.

| +| Data Schema | See Apendix C in this specification | +| SelectType Definition | The SelectType definition for the HSS-IMS GUP data component is described in the clause 9.3.2. | +| Semantics of the